Re: [Openstack-xenapi] Multitenancy networking rules

2011-09-25 Thread Ewan Mellor
e intention is that this changes nothing for your use case - I'd appreciate a review just to check that that's the case. Cheers, Ewan. From: Ewan Mellor Sent: 23 September 2011 14:54 To: 'Antony Messerli' Cc: openstack-xenapi@lists.launchpad.net Subject: RE: [Openstack-xena

Re: [Openstack-xenapi] Multitenancy networking rules

2011-09-23 Thread Ewan Mellor
Using that removes the need to declare the bridges in /etc/sysconfig/openvswitch-nova too. Cheers, Ewan. From: Antony Messerli [mailto:amess...@rackspace.com] Sent: 22 September 2011 21:54 To: Ewan Mellor Cc: openstack-xenapi@lists.launchpad.net Subject: Re: [Openstack-xenapi] Multitenancy net

Re: [Openstack-xenapi] Multitenancy networking rules

2011-09-22 Thread Antony Messerli
Ewan, We don't utilize eth0 for our dom0 network but instead dedicate eth0 and eth1 for VM networks. We use another interface for Management/dom0. By default they are fully locked down and run networking restrictions as needed. We originally used the vif script but we decided to go down the

[Openstack-xenapi] Multitenancy networking rules

2011-09-22 Thread Ewan Mellor
Hi, I'd like to get a better understanding of Rackspace's use of the multitenancy network rules in nova's plugins/xenserver/networking directory. At the moment, as far as I can tell, the vSwitch version of the rules are set up to allow no traffic to leave domain 0 at all. This seems pretty ext