On Mon, Feb 25, 2013 at 12:28:34PM -0600, Joe Brockmeier wrote: > On Fri, Feb 22, 2013, at 03:02 PM, Chip Childers wrote: > > > What happens if CloudStack starts to do more than manage large networks > > > of VMs ? > > > Pure theoretical speculation on my part. > > > > Very good point. We do bare-metal already. > > > > How about: > > > > "software to deploy and manage compute, storage and network services, as > > a highly available, highly scalable Infrastructure as a Service (IaaS) > > cloud computing platform" > > > > Thoughts? > > "software to provide Apache CloudStack, a highly available, scalable, > Infrastructure-as-a-Service (IaaS) cloud computing platform." > > or even > > "to provide Apache CloudStack, open source software that provides a > highly available, scalable, Infrastructure-as-a-Service (IaaS) cloud > computing platform." > > Looking at other charters, I don't think we need to get so specific as > to discuss compute, network, storage, etc.
How about: "software to provide and support an Infrastructure-as-a-Service (IaaS) cloud computing platform"? We shouldn't name "Apache CloudStack" as the only product IMO, since we may want to publish things like CloudMonkey as a separate package at some point. I also think we need to drop the qualitative measurements, given that someone could use it to provide a non-highly available and small cloud (if they were to be interested in doing so).
