Open Stack

Only a small number of applications support clustering, so its very unreasonable to expect to be able to just add instances to resolve every resource limit issue. I obviously understand that when resizing, you are though limited to the resources of a single host for ram and CPU. I plan on using ceph for storage and no ephemeral storage as my compute nodes wont have any local storage. I see zero value in destroying a vm, then recreating it with a new size. That doesn't sound like a resize at all. Might as well tell the client its not possible and to cancel their product and order again, which is obviously something most people would find unreasonable.

You might be right that open nebula is a better fit for me design wise, but unfortunately, its a project that I see losing a lot of momentum due to the popularity of openstack.

- Mark

On Sep 1, 2013, at 12:58 PM, Martinx - ジェームズ <thiagocmartinsc at gmail.com> wrote:

> Hi Mark!
> 
> From what I know, "Cloud Computing" environments, like OpenStack, Eucalyptus or AWS EC2, differs a lot from "Virtual Data Centers" like OpenNebula or even pure XenServer, EXSi or Linux KVM...
> 
> Here at the Cloud, we have a different approach, when you want to "resize" your Instance, you'll need to destroy it, and then, recreate it again. That is why solutions like Puppet or Chef are heavily used within Cloud Computing environments, automation, automation and more automation...
> 
> Your data must/should be hosted within services like "Block Storage / Cinder" and your application within the Image (hosted at Glance) itself.
> 
> Mostly because your Instances is almost disposable, your focus must be at the images (a.k.a AMI) and on persistent storage (Cinder), not within the Instance itself, so, when you need to grow, just start a bigger Instance or add more Instances to your pool...
> 
> Your application image (AMI) must be up-to-date, your data is on Cinder and you can have automation (when you are dealing with basics AMIs like Ubuntu Cloud and needs to deploy your application using puppet / chef within it)...
> 
> Also, would be great to hear from more people about this topic...
> 
> Cheers!
> Thiago
> 
> 
> On 30 August 2013 04:43, Mark Chaney <mail at lists.macscr.com> wrote:
>> That sounds like I would then have to start maintaing my own templates. Does that sound right? Im quite surprised this type of functionality isnt just there by default. Why would someone NOT want it?
>> 
>> 
>> 
>> 
>> On 2013-08-30 02:03, Ritesh Nanda wrote:
>>> using cloud-initramfs-growroot might help you.
>>> This package adds functionality to an initramfs built by
>>> initramfs-tools.
>>>   When installed, the initramfs will repartition a disk to make the
>>> root volume consume all space that follows it.
>>> 
>>> On Fri, Aug 30, 2013 at 11:45 AM, Mark Chaney <mail at lists.macscr.com>
>>> wrote:
>>> 
>>>> I am going to be hosting mainly Ubuntu, CentOS, and some Debian
>>>> instances with my openstack "cloud". Can instances be resized when
>>>> it comes to their storage? Obviously not only does its disk need to
>>>> be resized, but its FS as well. I am hoping openstack can take care
>>>> of all of that.
>>>> 
>>>> Thanks,
>>>> Mark
>>>> 
>>>> _______________________________________________
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
>>>> Post to     : openstack at lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
>>> 
>>> --
>>> 
>>>  With Regards 
>>> 
>>>   Ritesh Nanda
>>> 
>>>  [2]
>>> 
>>> 
>>> 
>>> Links:
>>> ------
>>> [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> [2] http://www.ericsson.com/
>> 
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130901/f27ec573/attachment.html>