Open Stack

You mean between what can be done as part of creating a VM vs what can be done to modify a VM after creation?

Consistency seems generally a positive thing, although from a GUI perspective there might be an argument to be made against making the GUI too confusing for simple tasks in order to allow for complicated/unusual special cases.

But with regard to attaching multiple vNICs to the same network we do need to be careful to protect the network from tenant mistakes. Does OpenvSwitch have a concept of BPDU guard and other related features to prevent a dual attached VM from looping the network?

--
Paul Carver
VO: 732-545-7377
Cell: 908-803-1656
E: pcarver at att.com<mailto:pcarver at att.com>
Q Instant Message<qto://talk/pc2929>

From: shihanzhang [mailto:ayshihanzhang at 126.com]
Sent: Monday, January 27, 2014 21:06
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network



Hi Paul:
  I am very glad to do the thing that puts together the practical use cases in which the same VM would benefit from multiple virtual connections to the same network, whatever it takes, I think we should at least guarantee the consistency of creating vms with nics and attaching nics.


在 2014-01-24 22:33:36，"CARVER, PAUL" <pc2929 at att.com<mailto:pc2929 at att.com>> 写道：

I agree that I’d like to see a set of use cases for this. This is the second time in as many days that I’ve heard about a desire to have such a thing but I still don’t think I understand any use cases adequately.

In the physical world it makes perfect sense, LACP, MLT, Etherchannel/Portchannel, etc. In the virtual world I need to see a detailed description of one or more use cases.

Shihanzhang, why don’t you start up an Etherpad or something and start putting together a list of one or more practical use cases in which the same VM would benefit from multiple virtual connections to the same network. If it really makes sense we ought to be able to clearly describe it.

--
Paul Carver
VO: 732-545-7377
Cell: 908-803-1656
E: pcarver at att.com<mailto:pcarver at att.com>
Q Instant Message<qto://talk/pc2929>

From: Day, Phil [mailto:philip.day at hp.com<mailto:philip.day at hp.com>]
Sent: Friday, January 24, 2014 09:11
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network

I agree its oddly inconsistent (you’ll get used to that over time ;-)  - but to me it feels more like the validation is missing on the attach that that the create should allow two VIFs on the same network.   Since these are both virtualised (i.e share the same bandwidth, don’t provide any additional resilience, etc) I’m curious about why you’d want two VIFs in this configuration ?

From: shihanzhang [mailto:ayshihanzhang at 126.com]
Sent: 24 January 2014 03:22
To: openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network

I am a beginer of nova, there is a problem which has confused me, in the latest version, it not allowed to create a vm directly with two VIF in the same network, but allowed to add a VIF that it network is same with a existed VIF'network, there is the use case that a vm with two VIF in the same network, but why not allow to create the vm directly with two VIF in the same network?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140128/7d3d9417/attachment.html>