<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>None of said features, cross host CPUs or cross host RAM (combining cross host resources to form a larger virtual one?) afaik exist (maybe they exist in prototypes since it is theoretically possible). Especially since this will likely be really slow to
perform. Afaik current virtualization isn't meant to replace openmp or mpi (or similar), does that answer your question?<br>
<br>
Sent from my really tiny device...</div>
<div><br>
On Dec 23, 2013, at 9:58 PM, "Vikas Parashar" <<a href="mailto:para.vikas@gmail.com">para.vikas@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Thanks everyone for your valuable point.
<div><br>
</div>
<div>Kindly allow me to put my Question in different way.</div>
<div><br>
</div>
<div>Shall any VM use distributed(for eg. RAM from the different host) resources at the same time?</div>
<div><br>
</div>
<div>or </div>
<div><br>
</div>
<div>Shall any VM use two cores(that lies on different hosts) at the same time?, in the distributed fashion. </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Dec 24, 2013 at 2:36 AM, Joshua Harlow <span dir="ltr">
<<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are much bigger differences for why u should not over-provision<br>
memory vs over-provision cpu.<br>
<br>
But agreed in general you shouldn't use swap either.<br>
<br>
There are many threads around how the OOM killer will get involved and why<br>
you should avoid this...<br>
<br>
- <a href="http://marc.info/?l=kvm&m=127375381631230&w=2" target="_blank">http://marc.info/?l=kvm&m=127375381631230&w=2</a><br>
- <a href="http://www.spinics.net/lists/kvm/msg84799.html" target="_blank">http://www.spinics.net/lists/kvm/msg84799.html</a><br>
- ...<br>
<div class="HOEnZb">
<div class="h5"><br>
On 12/23/13, 12:55 PM, "Cristian Falcas" <<a href="mailto:cristi.falcas@gmail.com">cristi.falcas@gmail.com</a>> wrote:<br>
<br>
>There is no point in using 8 virtual cores in compute node with 2<br>
>cores. The same is valid for using swap as memory to reach the desired<br>
>12gb.<br>
><br>
>Of course, if you don't plan on using that machine for any real work,<br>
>you can do it.<br>
><br>
><br>
><br>
>On Mon, Dec 23, 2013 at 6:39 PM, Joshua Harlow <<a href="mailto:harlowja@yahoo-inc.com">harlowja@yahoo-inc.com</a>><br>
>wrote:<br>
>> Nope, u can over provision on most all of the resources (CPU, ram,<br>
>>disk) u<br>
>> described there. Ram is the tricky one as the Linux oom killer may<br>
>>start to<br>
>> get involved when u push the ram limits to high. But there is nothing<br>
>> stopping u from running 8 or more vms on a box, depending on the over<br>
>> provision ratio u are ok with...<br>
>><br>
>> Sent from my really tiny device...<br>
>><br>
>> On Dec 23, 2013, at 3:55 AM, "Vikas Parashar" <<a href="mailto:para.vikas@gmail.com">para.vikas@gmail.com</a>><br>
>>wrote:<br>
>><br>
>> Thanks Cristian,<br>
>><br>
>> Will elasticity be limited to 4 Cores/4GB (The max capacity of a<br>
>>physical<br>
>> host) ?<br>
>><br>
>><br>
>> On Mon, Dec 23, 2013 at 5:00 PM, Cristian Falcas<br>
>><<a href="mailto:cristi.falcas@gmail.com">cristi.falcas@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> From what I know you can resize a machine, but this involves<br>
>>> rebuilding the instance: openstack will create a snapshot of the<br>
>>> machine an recreate the instance with the new snapshot and a new<br>
>>> flavor. This is not very fast from my experience, so you will have a<br>
>>> considerable downtime doing this, depending on the size of the current<br>
>>> instance and how fast is your storage.<br>
>>><br>
>>> Best regards,<br>
>>> Cristian Falcas<br>
>>><br>
>>><br>
>>><br>
>>> On Mon, Dec 23, 2013 at 12:03 PM, Vikas Parashar <<a href="mailto:para.vikas@gmail.com">para.vikas@gmail.com</a>><br>
>>> wrote:<br>
>>> > Hi,<br>
>>> ><br>
>>> > IaaS is all about elastic computing. I can stretch resources as per<br>
>>>my<br>
>>> > need<br>
>>> > - increasing/decreasing the number of cores, RAM allocated etc..<br>
>>> ><br>
>>> > My question is - how does openStack achieve this elasticity for both<br>
>>> > computation and RAM.<br>
>>> ><br>
>>> > If I create an image with 2 cores and 4 GB RAM (and one day I need to<br>
>>> > increase this to, lets say - 6 Cores and 12 GB RAM), but all the<br>
>>> > physical<br>
>>> > hosts that I currently have (for Compute and RAM) at my disposal<br>
>>>have a<br>
>>> > max<br>
>>> > of 4 Cores and 4 GB RAM each..<br>
>>> ><br>
>>> > Using openStack -<br>
>>> ><br>
>>> > a) is this possible (as long as the total cores and total RAM<br>
>>>required<br>
>>> > is<br>
>>> > less than the group-total) ? If yes, how is this achieved.<br>
>>> ><br>
>>> > b) or the elasticity will be limited to 4 Cores/4GB (The max<br>
>>>capacity<br>
>>> > of a<br>
>>> > physical host) ? If no, then is it possible to achieve it ?<br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > Mailing list:<br>
>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>>> > Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> > Unsubscribe :<br>
>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>>> ><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Mailing list:<br>
>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> Unsubscribe :<br>
>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</body>
</html>