openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #15762
Re: [Netstack] [openstack-dev] [Quantum] Multi-host implementation
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(张华) 地址:北京市海淀区东北旺西路8号 中关村
Staff Software Engineer 软件园28号楼 环宇大厦3层 邮编：100193
Travel&Transportation Standards Address: 3F Ring, Building 28
Emerging Technology Institute(ETI) Zhongguancun Software Park, 8
IBM China Software Development Lab Dongbeiwang West Road, Haidian
e-mail: zhuadl@xxxxxxxxxx District, Beijing, P.R.C.100193
Notes ID: Hua ZZ Zhang/China/IBM
Tel: 86-10-82450483
MURAOKA Yusuke
<yusuke@xxxxxxxxx
g> To
Sent by: Dan Wendlandt <dan@xxxxxxxxxx>
openstack-bounces cc
+zhuadl=cn.ibm.co OpenStack Development Mailing List
m@lists.launchpad <openstack-dev@xxxxxxxxxxxxxxxxxxx>
.net , netstack@xxxxxxxxxxxxxxxxxxx,
openstack@xxxxxxxxxxxxxxxxxxx
Subject
2012-08-09 00:19 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@xxxxxxxxxx
日付：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@xxxxxxxxxx (mailto:dan@xxxxxxxxxx)>:
> > 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@xxxxxxxxxx (
mailto:nachi@xxxxxxxxxx)> wrote:
> > >
> > > Hi folks
> > >
> > > Sorry.
> > > I added openstack-dev@xxxxxxxxxxxxxxxxxxx (
mailto:openstack-dev@xxxxxxxxxxxxxxxxxxx) in this discussion.
> > >
> > > 2012/8/3 Nati Ueno <nati.ueno@xxxxxxxxx (mailto:nati.ueno@xxxxxxxxx
)>:
> > > > 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@xxxxxxxxxxxxxxxxxxx (
mailto:openstack@xxxxxxxxxxxxxxxxxxx)
> > > > Unsubscribe : https://launchpad.net/~openstack
> > > > More help : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev@xxxxxxxxxxxxxxxxxxx (
mailto:OpenStack-dev@xxxxxxxxxxxxxxxxxxx)
> > > 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@xxxxxxxxxxxxxxxxxxx (
mailto:netstack@xxxxxxxxxxxxxxxxxxx)
> > Unsubscribe : https://launchpad.net/~netstack
> > More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx (
mailto:openstack@xxxxxxxxxxxxxxxxxxx)
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Follow ups
References
