Hi Mark,
On Thu, Jul 14, 2011 at 05:18:59PM +0100, Mark McLoughlin wrote:
Hey Matt,
Thanks for the comments
Do you think these are still the top 5?
I think so. I'm not sure all of them represent new functionality, but I
think they probably represent the five biggest things we've done.
That said, I think I'd prefer that our mention of each of these features
focused more on benefits to the end-user. For example:
1) New UI design!
- Complete new theme
- Design & Deploy, Monitor and Administer tabs
- Pretty View and Filter View
- Breadcrumbs
- Monitor UI
- "Launch Deployable" and deployments UI
It's simplified / easier to use, and well-tested in a wide range of browsers.
2) RHEV-M, VMWare vSphere and CondorCloud support:
- Available as provider types in conductor
- Image build/upload support
- Audrey config server IP used to get addresses of RHEV-M VMs
RHEV and vSphere support is pretty self-explanatory, but it might be
good to clarify the state of RHEV support -- it's for 2.2, requires the
addition of the API, and arguably isn't as robust as it will be with 3.0.
3) Deployable concept:
- Launch multiple instances using a deployable definition which
lists the images to use
- Stop all the instances in a deployment in one click
Your first bullet point here captures this well -- it's now fairly easy
to launch a group of instances, such as a pool of webservers.
4) aeolus-image CLI:
- Build an image from a template
- Push it to multiple providers
- Import an image
- List images available for use in deployables
The new command-line tools give greater flexibility to define complex
configurations. (Anyone have a better way of putting this?) You can now
enable custom repositories and have multiple images in a deployable.
Similarly, we now support building for RHEL.
5) Reduced complexity:
- Template creation and image building UI removed
- condor_refreshd, the condor classad plugin, warehouse sync,
image factory connector and delayed job daemons all removed
This also has the effect of making for a smaller footprint. I might skip
the first bullet point in this context, as I'd argue that replacing the
web GUI with a command-line tool and a few XML files *increases*
complexity, although it provides much more functionality in the process.
-- Matt