Hi,
I've updated the bp to correspond with current design spec.
> https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
I'd know the case of failure, improper, insane, by that.
Anyway, comments, discussions are welcome.
Thanks.
--
MURAOKA Yusuke
Mail: yusuke@jbking.org
日付:2012å¹´8月7æ—¥ç«æ›œæ—¥ã€æ™‚刻:2:47ã€å·®å‡ºäººï¼šNachi Ueno:
> Hi Dan
>
> Thank you for pointing this.
>
> Yusuke updated design spec.
> https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
>
> 2012/8/6 Dan Wendlandt <dan@nicira.com (mailto:dan@nicira.com)>:
> > Hi Nachi,
> >
> > I've reviewed the code and added comments. I'd like to see at least a basic
> > spec describing the proposed approach (need only be a couple paragraphs,
> > perhaps with a diagram) linked to the blueprint so we can have a design
> > discussion around it. Thanks,
> >
> > Dan
> >
> >
> > On Fri, Aug 3, 2012 at 1:03 PM, Nachi Ueno <nachi@nttmcl.com (mailto:nachi@nttmcl.com)> wrote:
> > >
> > > Hi folks
> > >
> > > Sorry.
> > > I added openstack-dev@lists.openstack.org (mailto:openstack-dev@lists.openstack.org) in this discussion.
> > >
> > > 2012/8/3 Nati Ueno <nati.ueno@gmail.com (mailto:nati.ueno@gmail.com)>:
> > > > Hi folks
> > > >
> > > > > Gary
> > > > Thank you for your comment. I wanna discuss your point on the mailing
> > > > list.
> > > >
> > > > Yusuke pushed Multi-host implementation for review.
> > > > https://review.openstack.org/#/c/10766/2
> > > > This patch changes only quantum-dhcp-agent side.
> > > >
> > > > Gary's point is we should have host attribute on the port for
> > > > scheduling.
> > > > I agree with Gary.
> > > >
> > > > In the nova, vm has available_zone for scheduling.
> > > > So Instead of using host properties.
> > > > How about use available_zone for port?
> > > >
> > > > Format of availability_zone is something like this
> > > > available_zone="zone_name:host".
> > > >
> > > > We can also add availability_zone attribute for the network as a
> > > > default value of port.
> > > > We can write this until next Monday.
> > > > However I'm not sure quantum community will accept this or not, so I'm
> > > > asking here.
> > > >
> > > > If there are no objections, we will push zone version for review.
> > > > Thanks
> > > > Nachi
> > > >
> > > > _______________________________________________
> > > > Mailing list: https://launchpad.net/~openstack
> > > > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net)
> > > > Unsubscribe : https://launchpad.net/~openstack
> > > > More help : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev@lists.openstack.org (mailto:OpenStack-dev@lists.openstack.org)
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> >
> > --
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Dan Wendlandt
> > Nicira, Inc: www.nicira.com (http://www.nicira.com)
> > twitter: danwendlandt
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >
> > --
> > Mailing list: https://launchpad.net/~netstack
> > Post to : netstack@lists.launchpad.net (mailto:netstack@lists.launchpad.net)
> > Unsubscribe : https://launchpad.net/~netstack
> > More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net)
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
I've updated the bp to correspond with current design spec.
> https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
I'd know the case of failure, improper, insane, by that.
Anyway, comments, discussions are welcome.
Thanks.
--
MURAOKA Yusuke
Mail: yusuke@jbking.org
日付:2012å¹´8月7æ—¥ç«æ›œæ—¥ã€æ™‚刻:2:47ã€å·®å‡ºäººï¼šNachi Ueno:
> Hi Dan
>
> Thank you for pointing this.
>
> Yusuke updated design spec.
> https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
>
> 2012/8/6 Dan Wendlandt <dan@nicira.com (mailto:dan@nicira.com)>:
> > Hi Nachi,
> >
> > I've reviewed the code and added comments. I'd like to see at least a basic
> > spec describing the proposed approach (need only be a couple paragraphs,
> > perhaps with a diagram) linked to the blueprint so we can have a design
> > discussion around it. Thanks,
> >
> > Dan
> >
> >
> > On Fri, Aug 3, 2012 at 1:03 PM, Nachi Ueno <nachi@nttmcl.com (mailto:nachi@nttmcl.com)> wrote:
> > >
> > > Hi folks
> > >
> > > Sorry.
> > > I added openstack-dev@lists.openstack.org (mailto:openstack-dev@lists.openstack.org) in this discussion.
> > >
> > > 2012/8/3 Nati Ueno <nati.ueno@gmail.com (mailto:nati.ueno@gmail.com)>:
> > > > Hi folks
> > > >
> > > > > Gary
> > > > Thank you for your comment. I wanna discuss your point on the mailing
> > > > list.
> > > >
> > > > Yusuke pushed Multi-host implementation for review.
> > > > https://review.openstack.org/#/c/10766/2
> > > > This patch changes only quantum-dhcp-agent side.
> > > >
> > > > Gary's point is we should have host attribute on the port for
> > > > scheduling.
> > > > I agree with Gary.
> > > >
> > > > In the nova, vm has available_zone for scheduling.
> > > > So Instead of using host properties.
> > > > How about use available_zone for port?
> > > >
> > > > Format of availability_zone is something like this
> > > > available_zone="zone_name:host".
> > > >
> > > > We can also add availability_zone attribute for the network as a
> > > > default value of port.
> > > > We can write this until next Monday.
> > > > However I'm not sure quantum community will accept this or not, so I'm
> > > > asking here.
> > > >
> > > > If there are no objections, we will push zone version for review.
> > > > Thanks
> > > > Nachi
> > > >
> > > > _______________________________________________
> > > > Mailing list: https://launchpad.net/~openstack
> > > > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net)
> > > > Unsubscribe : https://launchpad.net/~openstack
> > > > More help : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev@lists.openstack.org (mailto:OpenStack-dev@lists.openstack.org)
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> >
> > --
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Dan Wendlandt
> > Nicira, Inc: www.nicira.com (http://www.nicira.com)
> > twitter: danwendlandt
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >
> > --
> > Mailing list: https://launchpad.net/~netstack
> > Post to : netstack@lists.launchpad.net (mailto:netstack@lists.launchpad.net)
> > Unsubscribe : https://launchpad.net/~netstack
> > More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net)
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp