<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Hello folks,
<div><br>
</div>
<div>Here is the bug [1] which is currently not allowing a host to be part of two availability zones.</div>
<div>This bug was targeted for havana.</div>
<div><br>
</div>
<div>The fix in the bug was made because it was assumed </div>
<div>that openstack does not support adding hosts to two zones by design. </div>
<div><br>
</div>
<div>The assumption was based on the fact that ---</div>
<div>if hostX is added to zoneA as well as zoneB,</div>
<div>and if you boot a vm vmY passing zoneB in boot params,</div>
<div>nova show vmY still returns zoneA. </div>
<div><br>
</div>
<div>In my opinion, we should fix the case of nova show </div>
<div>rather than changing aggregate api to not allow addition of hosts to multiple zones.</div>
<div><br>
</div>
<div>I have added my comments in comments #7 and #9 on that bug.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Meghal</div>
<div><br>
</div>
<div>[1] Bug - <a href="https://bugs.launchpad.net/nova/+bug/1196893">https://bugs.launchpad.net/nova/+bug/1196893</a></div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div>On Apr 3, 2014, at 9:05 AM, Steve Gordon <<a href="mailto:sgordon@redhat.com">sgordon@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">----- Original Message -----<br>
<br>
<blockquote type="cite">Currently host aggregates are quite general, but the only ways for an<br>
end-user to make use of them are:<br>
<br>
1) By making the host aggregate an availability zones (where each host<br>
is only supposed to be in one availability zone) and selecting it at<br>
instance creation time.<br>
<br>
2) By booting the instance using a flavor with appropriate metadata<br>
(which can only be set up by admin).<br>
<br>
<br>
I would like to see more flexibility available to the end-user, so I<br>
think we should either:<br>
<br>
A) Allow hosts to be part of more than one availability zone (and allow<br>
selection of multiple availability zones when booting an instance), or<br>
</blockquote>
<br>
While changing to allow hosts to be in multiple AZs changes the concept from an operator/user point of view I do think the idea of being able to specify multiple AZs when booting an instance makes sense and would be a nice enhancement for users working with
multi-AZ environments - "I'm OK with this instance running in AZ1 and AZ2, but not AZ*".<br>
<br>
-Steve<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>