<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I don't know if this is what you want,
but you can check the zone and hostname of your compute nodes with
the command<br>
<br>
> nova service-list<br>
<br>
and boot VMs on specific computes nodes with the following
command:<br>
<br>
> nova boot --image <id_of_image> --flavor m1.large
--availability-zone nova_zone:compute_hostname --key_name YourKey
Name_Of_New_VM<br>
<br>
However, you will most likely need administrative privileges for
something like this.<br>
<br>
<br>
Vangelis<br>
<br>
On 11/25/2014 06:36 PM, Phab Lucky wrote:<br>
</div>
<blockquote
cite="mid:CABOy+deEAz9wkSKR0Vzc0O7b0sBTXVYkNET8R3jVy3TVZogFew@mail.gmail.com"
type="cite">
<div>Hi, Narayan.</div>
<div> </div>
<div>Thanks for your reply. I think my requirements are not as
strict as for a fine-grained platform.</div>
<div> </div>
<div>Consider Hadoop as one instance of what we are willing to
support. The instantiation of a Hadoop cluster involve some
placement constraints, like not placing two Task Trackers on the
same physical host. Sahara accomplish that by defining
anti-affinity groups, so I was wondering if there would be a
more direct way to place VMs that wouldn`t even require hinting
simplistic policies to the scheduler. Can`t we simply say:
"create VM X on host Y"?</div>
<div> </div>
<div>Thanks again.</div>
<div> </div>
<div>Phab<br>
</div>
<div class="gmail_quote">On Mon, Nov 24, 2014 at 6:53 PM, Narayan
Desai <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:narayan.desai@gmail.com" target="_blank">narayan.desai@gmail.com</a>></span>
wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px
0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">This doesn't seem like a good match for
openstack's model. If you want data locality, you want
persistence of data and a resource allocation that has a
relatively long lifetime, but your tasks will be short.
Since openstack largely deals with coarse grained
allocations, you probably aren't in for a good time if you
want to build a fine-grained adaptive system on top of the
openstack scheduler.
<div><br>
</div>
<div>Have you looked at mesos? I think it might be better
infrastructure for your use case.</div>
<div> -nld</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 24, 2014 at 7:40 PM,
Phab Lucky <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:phab.lucky@gmail.com" target="_blank">phab.lucky@gmail.com</a>></span>
wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px
0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div class="gmail_quote">
<div>Hi, all.</div>
<div> </div>
<div>I'm new to OpenStack, so I apologize in advance
if my question lacks relevance or sense.</div>
<div> </div>
<div>We are trying to build a cluster orchestrator for
Big Data processing and one of the key requirements
is the ability to place each computing task in each
physical server. We have been trying to leverage
this development with OpenStack, but, as far as I
can see by the on-line documentation, the Nova
interface does not allow users to specify the
physical location (host) where VMs (servers) are
created. Instead, this task is performed by the
Scheduler, which has its own algorithms and
policies.</div>
<div> </div>
<div>Even though we can try to customize the
Scheduler, I was wondering if I could simply bypass
it and tell Nova to create a VM on host X. I know
this sounds like bad design, as we are violating the
location transparency that OpenStack attempts to
deliver, but this seems to me the only way to bring
the computation to where the data is.</div>
<div> </div>
<div>Any thoughts?</div>
<div> </div>
<div>Thanks a lot.</div>
<span><font color="#888888"><span><font
color="#888888">
<div> </div>
<div>Phab</div>
<div> </div>
</font></span></font></span></div>
<br>
<br>
_______________________________________________<br>
OpenStack-HPC mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-HPC@lists.openstack.org"
target="_blank">OpenStack-HPC@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-HPC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-HPC@lists.openstack.org">OpenStack-HPC@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc</a>
</pre>
</blockquote>
<br>
</body>
</html>