Mailing List Archive: Re: [openstack-dev] [Openstack] [Quantum] Multi-host implementation

Re: [openstack-dev] [Openstack] [Quantum] Multi-host implementation

Aug 6, 2012, 10:00 AM

Post #1 of 3 (3938 views)

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> wrote:

> Hi folks
>
> Sorry.
> I added openstack-dev@lists.openstack.org in this discussion.
>
> 2012/8/3 Nati Ueno <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
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: [openstack-dev] [Openstack] [Quantum] Multi-host implementation [ In reply to ]

nachi at nttmcl

Aug 6, 2012, 10:47 AM

Post #2 of 3 (3831 views)

Permalink

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>:
> 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> wrote:
>>
>> Hi folks
>>
>> Sorry.
>> I added openstack-dev@lists.openstack.org in this discussion.
>>
>> 2012/8/3 Nati Ueno <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
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> --
> Mailing list: https://launchpad.net/~netstack
> Post to : netstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~netstack
> 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

Re: [openstack-dev] [Openstack] [Quantum] Multi-host implementation [ In reply to ]

arosen at nicira

Aug 13, 2012, 12:37 AM

Post #3 of 3 (3814 views)

Permalink

The dhcp agent now is able to use network namespaces so there is no longer
ip conflicts. Perhaps in the future the dhcp agent could implement some
kind of DHCP reply (ip helper) service . Though currently it allocates an
ip address in each subnet that you want dhcp enabled on.

Aaron

On Mon, Aug 13, 2012 at 12:02 AM, Hua ZZ Zhang <zhuadl@cn.ibm.com> wrote:

> hi,
>
> I have a question about the ip address consumed by the dhcp services. is
> it necessary to assign an individual ip for each dhcp daemon? can we
> reserve only one ip address for all dhcp deamons subject to one subnet
> since they won't run on the same host? since the dhcp service only need to
> communicate with local VM instances and local dhcp agent (don't know if it
> is true for this assumption), can we find a kind of isolation mechanism to
> avoid ip conflicts and extra consume of ip addresses to implement this
> feature?
>
> *Best Regards, *
>
> ------------------------------
>
> *Edward Zhang(ÕÅ»ª)*
> Staff Software Engineer
> Travel&Transportation Standards
> Emerging Technology Institute(ETI)
> IBM China Software Development Lab
> e-mail: zhuadl@cn.ibm.com
> Notes ID: Hua ZZ Zhang/China/IBM
> Tel: 86-10-82450483
>
>
> µØÖ·:±±¾©ÊÐº£µíÇø¶«±±ÍúÎ÷Â·8ºÅ ÖÐ¹Ø´åÈí¼þÔ°28ºÅÂ¥ »·Óî´óÏÃ3²ã ÓÊ±à£º100193
> Address: 3F Ring, Building 28 Zhongguancun Software Park, 8
> Dongbeiwang West Road, Haidian District, Beijing, P.R.C.100193
>
>
>
>
>
>
>
> [image: Inactive hide details for MURAOKA Yusuke ---2012-08-09
> 00:21:52---Hi,]MURAOKA Yusuke ---2012-08-09 00:21:52---Hi,
>
>
> *MURAOKA Yusuke <yusuke@jbking.org>*
> Sent by: openstack-bounces+zhuadl=cn.ibm.com@lists.launchpad.net
>
> 2012-08-09 00:19
>
>
> To
>
>
> Dan Wendlandt <dan@nicira.com>
>
>
> cc
>
>
> OpenStack Development Mailing List <openstack-dev@lists.openstack.org>,
> netstack@lists.launchpad.net, openstack@lists.launchpad.net
>
>
> Subject
>
>
> Re: [Openstack] [Netstack] [openstack-dev] [Quantum] Multi-host
> implementation
>
>
> 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ÈÕ»ðê×ÈÕ¡¢•r¿Ì£º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<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 <nachi@nttmcl.com>)> wrote:
> > > >
> > > > Hi folks
> > > >
> > > > Sorry.
> > > > I added openstack-dev@lists.openstack.org (
> mailto:openstack-dev@lists.openstack.org<openstack-dev@lists.openstack.org>)
> in this discussion.
> > > >
> > > > 2012/8/3 Nati Ueno <nati.ueno@gmail.com (mailto:nati.ueno@gmail.com<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 <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<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 <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 <openstack@lists.launchpad.net>)
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

Mailing List Archive

Mailing List Archive

Attached Files: