<br><br><div class="gmail_quote">On Sat, Aug 11, 2012 at 7:51 AM, Nachi Ueno <span dir="ltr"><<a href="mailto:nachi@nttmcl.com" target="_blank">nachi@nttmcl.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Dan<br>
<br>
How do you think current multi-host design?<br>
<br>
- Currently, a centralized dhcp agent hosts all dhcp networks as children.<br>
<br>
<a href="https://docs.google.com/presentation/d/1kisLDcWg_Mus5g8QzXMD4w7gWou-3t1drbOKTlYg6MU/edit#slide=id.p9" target="_blank">https://docs.google.com/presentation/d/1kisLDcWg_Mus5g8QzXMD4w7gWou-3t1drbOKTlYg6MU/edit#slide=id.p9</a><br>
<br>
Current Design<br>
- To know what network must be on the host where the agent running on,<br>
implement get_local_port_ids (Look at the doc page 9)<br>
- If an network must be on the host, spawn dhcp service process,<br>
otherwise don't do anything.<br></blockquote><div><br></div><div>Yes, a design like that makes more sense to me, as we can cut out a lof the complexity (I hope).</div><div><br></div><div>dan</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<a href="https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp</a><br>
<br>
2012/8/8 MURAOKA Yusuke <<a href="mailto:yusuke@jbking.org">yusuke@jbking.org</a>>:<br>
<div class="HOEnZb"><div class="h5">> Hi,<br>
><br>
> I've updated the bp to correspond with current design spec.<br>
>> <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp</a><br>
><br>
><br>
> I'd know the case of failure, improper, insane, by that.<br>
> Anyway, comments, discussions are welcome.<br>
><br>
> Thanks.<br>
><br>
> --<br>
> MURAOKA Yusuke<br>
><br>
> Mail: <a href="mailto:yusuke@jbking.org">yusuke@jbking.org</a><br>
><br>
><br>
> $BF|IU!'(B2012$BG/(B8$B7n(B7$BF|2PMKF|!";~9o!'(B2:47$B!":9=P?M!'(BNachi Ueno$B!'(B<br>
><br>
>> Hi Dan<br>
>><br>
>> Thank you for pointing this.<br>
>><br>
>> Yusuke updated design spec.<br>
>> <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp</a><br>
>><br>
>> 2012/8/6 Dan Wendlandt <<a href="mailto:dan@nicira.com">dan@nicira.com</a> (mailto:<a href="mailto:dan@nicira.com">dan@nicira.com</a>)>:<br>
>> > Hi Nachi,<br>
>> ><br>
>> > I've reviewed the code and added comments. I'd like to see at least a basic<br>
>> > spec describing the proposed approach (need only be a couple paragraphs,<br>
>> > perhaps with a diagram) linked to the blueprint so we can have a design<br>
>> > discussion around it. Thanks,<br>
>> ><br>
>> > Dan<br>
>> ><br>
>> ><br>
>> > On Fri, Aug 3, 2012 at 1:03 PM, Nachi Ueno <<a href="mailto:nachi@nttmcl.com">nachi@nttmcl.com</a> (mailto:<a href="mailto:nachi@nttmcl.com">nachi@nttmcl.com</a>)> wrote:<br>
>> > ><br>
>> > > Hi folks<br>
>> > ><br>
>> > > Sorry.<br>
>> > > I added <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a> (mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>) in this discussion.<br>
>> > ><br>
>> > > 2012/8/3 Nati Ueno <<a href="mailto:nati.ueno@gmail.com">nati.ueno@gmail.com</a> (mailto:<a href="mailto:nati.ueno@gmail.com">nati.ueno@gmail.com</a>)>:<br>
>> > > > Hi folks<br>
>> > > ><br>
>> > > > > Gary<br>
>> > > > Thank you for your comment. I wanna discuss your point on the mailing<br>
>> > > > list.<br>
>> > > ><br>
>> > > > Yusuke pushed Multi-host implementation for review.<br>
>> > > > <a href="https://review.openstack.org/#/c/10766/2" target="_blank">https://review.openstack.org/#/c/10766/2</a><br>
>> > > > This patch changes only quantum-dhcp-agent side.<br>
>> > > ><br>
>> > > > Gary's point is we should have host attribute on the port for<br>
>> > > > scheduling.<br>
>> > > > I agree with Gary.<br>
>> > > ><br>
>> > > > In the nova, vm has available_zone for scheduling.<br>
>> > > > So Instead of using host properties.<br>
>> > > > How about use available_zone for port?<br>
>> > > ><br>
>> > > > Format of availability_zone is something like this<br>
>> > > > available_zone="zone_name:host".<br>
>> > > ><br>
>> > > > We can also add availability_zone attribute for the network as a<br>
>> > > > default value of port.<br>
>> > > > We can write this until next Monday.<br>
>> > > > However I'm not sure quantum community will accept this or not, so I'm<br>
>> > > > asking here.<br>
>> > > ><br>
>> > > > If there are no objections, we will push zone version for review.<br>
>> > > > Thanks<br>
>> > > > Nachi<br>
>> > > ><br>
>> > > > _______________________________________________<br>
>> > > > Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> > > > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> (mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>)<br>
>> > > > Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> > > > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > _______________________________________________<br>
>> > > OpenStack-dev mailing list<br>
>> > > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a> (mailto:<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>)<br>
>> > > <a 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>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> > Dan Wendlandt<br>
>> > Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a> (<a href="http://www.nicira.com" target="_blank">http://www.nicira.com</a>)<br>
>> > twitter: danwendlandt<br>
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> ><br>
>> ><br>
>> > --<br>
>> > Mailing list: <a href="https://launchpad.net/~netstack" target="_blank">https://launchpad.net/~netstack</a><br>
>> > Post to : <a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a> (mailto:<a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a>)<br>
>> > Unsubscribe : <a href="https://launchpad.net/~netstack" target="_blank">https://launchpad.net/~netstack</a><br>
>> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> (mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>)<br>
>> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div><br>