On 07/15/2011 09:44 AM, Mike Orazi wrote:
On 07/15/2011 06:45 AM, Angus Thomas wrote:
> On 14/07/11 19:45, Hugh Brock wrote:
>> Aeolus mission: Give users tools to build and manage organized groups
>> of virtual machines across multiple clouds.
>>
> The whole doc looks good to me.
>
> The only amendment that springs to mind is to increase the emphasis on
> the fact that we're delivering a single set of tools and an API etc.,
> that works the same way across multiple cloud providers, and we're doing
> all that we can to avoid having the users carry out provider-specific
> tasks, so that they get maximum reusability out of their templates,
> scripts, etc..
>
+1 to this portion in particular. I think we want to emphasize the
multi-cloud angle and some of the things that it enables such as easy
migration to a new cloud provider, the ability to fairly easily pull
loads back into a set of local machines if needed, and eventually the
ability to do some fairly sophisticate decision making on where to
launch a deployable.
Also agree with this. The most important bits IMO are
- cloud management framework - deploy, manage, monitor, scale, migrate
- vendor-agnositic: use the same tooling to control all clouds
- platform independent: web based, used aeolus from any language
- simple: very easy to use tooling and api
- open source: vendor lockin = bad
> How about: Aeolus mission: Give users a single, consistent set of
tools
> to build and manage organized groups of virtual machines across multiple
> clouds.
IMHO I usually tend to use "instance" over "vm" in the context of the
cloud but I like the mission statement overall.
-Mo