<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 27/03/2014 00:16, Sangeeta Singh a
écrit :<br>
</div>
<blockquote cite="mid:CF58AC42.4DF2F%25singhs@yahoo-inc.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Hi,</div>
<div><br>
</div>
<div>To update the thread the initial problem that I mentioned
that when I add a host to multiple availability zone(AZ) and
then do a</div>
<div>“nova boot” without specifying a AZ expecting the default
zone to be picked up.</div>
<div><br>
</div>
<div>This is due to the bug [1] as mentioned by Vish. I have
updated the bug with the problem.</div>
<div><br>
</div>
<div>The validation fails during instance create due to the [1]</div>
<div><br>
</div>
</blockquote>
<br>
Yup, I understood the issue, as the name of the AZ is consequently
different from the default one.<br>
<br>
I still need to jump on unittests and see what needs to be changed,
but apart from that, the change by itself should be quick to do.<br>
<br>
-Sylvain<br>
<br>
<br>
<blockquote cite="mid:CF58AC42.4DF2F%25singhs@yahoo-inc.com"
type="cite">
<div>
</div>
<div>Thanks,</div>
<div>Sangeeta</div>
<div><br>
</div>
<div>[1] <a moz-do-not-send="true"
href="https://bugs.launchpad.net/nova/+bug/1277230">https://bugs.launchpad.net/nova/+bug/1277230</a></div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Sylvain Bauza
<<a moz-do-not-send="true"
href="mailto:sylvain.bauza@gmail.com">sylvain.bauza@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, March
26, 2014 at 1:34 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re:
[openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">I can't agree more on this. Although the name
sounds identical to AWS, Nova AZs are *not* for
segregating compute nodes, but rather exposing to users a
certain sort of grouping.
<div>Please see this pointer for more info if needed : <a
moz-do-not-send="true"
href="http://russellbryantnet.wordpress.com/2013/05/21/availability-zones-and-host-aggregates-in-openstack-compute-nova/">http://russellbryantnet.wordpress.com/2013/05/21/availability-zones-and-host-aggregates-in-openstack-compute-nova/</a></div>
<div><br>
</div>
<div>Regarding the bug mentioned by Vish [1], I'm the
owner of it. I took it a while ago, but things and
priorities changed so I can take a look over it this
week and hope to deliver a patch by next week.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-Sylvain</div>
<div><br>
</div>
<div>[1] <a moz-do-not-send="true"
href="https://bugs.launchpad.net/nova/+bug/1277230">https://bugs.launchpad.net/nova/+bug/1277230</a></div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-03-26 19:00 GMT+01:00 Chris
Friesen <span dir="ltr">
<<a moz-do-not-send="true"
href="mailto:chris.friesen@windriver.com"
target="_blank">chris.friesen@windriver.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 03/26/2014 11:17 AM, Khanh-Toan Tran
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't know why you need a<br>
compute node that belongs to 2 different
availability-zones. Maybe<br>
I'm wrong but for me it's logical that
availability-zones do not<br>
share the same compute nodes. The
"availability-zones" have the role<br>
of partition your compute nodes into "zones" that
are physically<br>
separated (in large term it would require
separation of physical<br>
servers, networking equipments, power sources,
etc). So that when<br>
user deploys 2 VMs in 2 different zones, he knows
that these VMs do<br>
not fall into a same host and if some zone falls,
the others continue<br>
working, thus the client will not lose all of his
VMs.<br>
</blockquote>
<br>
</div>
See Vish's email.<br>
<br>
Even under the original meaning of availability zones
you could realistically have multiple orthogonal
availability zones based on "room", or "rack", or
"network", or "dev" vs "production", or even
"has_ssds" and a compute node could reasonably be part
of several different zones because they're logically
in different namespaces.<br>
<br>
Then an end-user could boot an instance, specifying
"networkA", "dev", and "has_ssds" and only hosts that
are part of all three zones would match.<br>
<br>
Even if they're not used for orthogonal purposes,
multiple availability zones might make sense.
Currently availability zones are the only way an
end-user has to specify anything about the compute
host he wants to run on. So it's not entirely
surprising that people might want to overload them for
purposes other than physical partitioning of machines.<span
class="HOEnZb"><font color="#888888"><br>
<br>
Chris</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org"
target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>