Open Stack

Nope, u can over provision on most all of the resources (CPU, ram, disk) u described there. Ram is the tricky one as the Linux oom killer may start to get involved when u push the ram limits to high. But there is nothing stopping u from running 8 or more vms on a box, depending on the over provision ratio u are ok with...

Sent from my really tiny device...

On Dec 23, 2013, at 3:55 AM, "Vikas Parashar" <para.vikas at gmail.com<mailto:para.vikas at gmail.com>> wrote:

Thanks Cristian,

Will elasticity  be limited to 4 Cores/4GB  (The max capacity of a physical host) ?


On Mon, Dec 23, 2013 at 5:00 PM, Cristian Falcas <cristi.falcas at gmail.com<mailto:cristi.falcas at gmail.com>> wrote:
Hi,

>From what I know you can resize a machine, but this involves
rebuilding the instance: openstack will create a snapshot of the
machine an recreate the instance with the new snapshot and a new
flavor. This is not very fast from my experience, so you will have a
considerable downtime doing this, depending on the size of the current
instance and how fast is your storage.

Best regards,
Cristian Falcas



On Mon, Dec 23, 2013 at 12:03 PM, Vikas Parashar <para.vikas at gmail.com<mailto:para.vikas at gmail.com>> wrote:
> Hi,
>
> IaaS is all about elastic computing. I can stretch resources as per my need
> - increasing/decreasing the number of cores, RAM allocated etc..
>
> My question is - how does openStack achieve this elasticity for both
> computation and RAM.
>
> If I create an image with 2 cores and 4 GB RAM (and one day I need to
> increase this to, lets say - 6 Cores and 12 GB RAM), but all the physical
> hosts that I currently have (for Compute and RAM) at my disposal have a max
> of 4 Cores and 4 GB RAM each..
>
> Using openStack -
>
> a) is this possible (as long as the total cores and total RAM required is
> less than the group-total) ? If yes, how is this achieved.
>
> b) or the elasticity will be limited to 4 Cores/4GB  (The max capacity of a
> physical host) ? If no, then is it possible to achieve it ?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto: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/20131223/39a1fc70/attachment.html>