<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Yes, I've found this workaround.<br>
<br>
But it does not works as expected. I mean, if network node hosts
l3-agent for specific availability zone, it works. But all stuff in
internal networks is complete mess. dhcp-agents are selected in full
random without any correlation to external networks or AZ. So it
can be that some instance is served by 'own' AZ network node, but
dhcp-agent is belong to other AZ, and maintenance of 'other' AZ can
cause startup/lease-renew problems for 'own' AZ.<br>
<br>
I start to discuss this problem at work, seems we (may be - still in
discussion) can dedicate some resources to add AZ support to neutron
agents, f.e. declare agent response for specific AZs. But before
this I need to know that this feature:<br>
<br>
1. Is not implemented already (or in process)<br>
2. Is suited for upstream (I think this happens during blueprint
discussion).<br>
3. Get proper knowledge about all workflow<br>
4. Motivate programmers to dive into openstack<br>
<br>
On 01/27/2014 05:07 PM, Richard Boswell wrote:<br>
<blockquote
cite="mid:CAGOM_qTJnRH7mcaRq78XN__5MHcsYE1nru7tu==7OdTVLs4Wzw@mail.gmail.com"
type="cite">
<div dir="ltr">George, the only thing that I know that will limit
this is by assigning unique networks to an AZ.
<div class="gmail_extra"><br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Can't find any information: is any way group neutron
network nodes with<br>
hosts in nova availability zone?<br>
<br>
I really don't want to have instance from one AZ served by
l3 agent on<br>
other AZ's network node..<br>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>