That's a good question. Multi-NIC support could be separated out from the rest of the network-service blueprint, but I don't know whether it would be useful to do so.
I assume that the tenant will not be able to configure any rich network topologies until network-service is done. If that is true, what else would you do with multi-NIC support? And how do you imagine that it would work? Thanks, Ewan. > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of [email protected] > Sent: 02 February 2011 06:34 > To: [email protected] > Subject: [Openstack] Multi-NIC support to Cactus > > Hello, > > Regarding to the blueprint to Cactus, > I found 2 blueprints that may be related to multi-NIC. > ( I expect instances can have multiple vnic. ) > > 1. <https://blueprints.launchpad.net/nova/+spec/multi-nic> > 2. <https://blueprints.launchpad.net/nova/+spec/multinic-libvirt> > > Q1. New network model topic and multi-nic support topic will be > discussed as different topics for Cactus. > A new netowk model is deferred to Diablo but multi-NIC support may be > included in Cactus, am I following to current discussion? > > Q2. If so, looking back to discussions till now, multi-nic might be > supported to Xenserver and KVM to Cactus? > I know we are not sure till any blueprint be approved, my team is > curious to KVM multi-nic support. > > Regards, > Kei Masumoto > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
