Hi, I successfully deployed RDO Manager Liberty HA with VLANS on some HP blades + in-chassis switches with trunked VLANs ports (call this OBM (Openstack Bare Metal)) I wanted to deploy a test Openstack environment within this (call this OV (Openstack Virtual)) So I created two instances in OBM, and used packstack to roll out one controller and one compute node configured with vxlan tenant networks. This all worked and I can fire up an instance in OV, and it gets an ip. I then created an external network in OV with a VLAN id that matches an OBM network. The plan was to access an instance in OV from an instance in OBM. Problem is that the OV external network gateway is down, and after assigning a floating ip to the OV instance I have no access to or from it. I can only get to it from the network namespace on the OV controller (ip netns exec....) I have previously got this Openstack nested visualization working in VMware (vCloud) by enabling promiscuous mode on dvs portgoup, and also enabling promisc on the virtual interfaces of the virtual Openstack controllers. I tried enabling promiscuous mode on the OV controllers interfaces (OBM instances), but this seemed to make no difference. Any tips? Is this possible? Thanks Charles -- Charles Short Cloud Engineer Virtualization and Cloud Team European Bioinformatics Institute (EMBL-EBI) Tel: +44 (0)1223 494205 _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com

Hi Marius, Would it work if the external network was the untagged vlan? Does this make sense? Thanks, David On 18/02/2016 20:39, Marius Cornea wrote: > > Hi Charles, > > If I understand it right - since you are creating the external network > with a vlan tag then the OV controller(nova instance in the OBM > openstack) needs to send tagged frames which afaik doesn't work since > ovs strips the tag. I see there's a blueprint[1] for vlan aware vms > but it's not implemented. > > [1] > http://specs.openstack.org/openstack/neutron-specs/specs/liberty/vlan-awa... > > On Thu, Feb 18, 2016 at 4:41 PM, Charles Short <cems(a)ebi.ac.uk&gt; wrote: >> >> Hi, >> >> I successfully deployed RDO Manager Liberty HA with VLANS on some HP >> blades >> + in-chassis switches with trunked VLANs ports (call this OBM (Openstack >> Bare Metal)) >> I wanted to deploy a test Openstack environment within this (call this OV >> (Openstack Virtual)) >> So I created two instances in OBM, and used packstack to roll out one >> controller and one compute node configured with vxlan tenant networks. >> This all worked and I can fire up an instance in OV, and it gets an ip. >> I then created an external network in OV with a VLAN id that matches an >> OBM >> network. The plan was to access an instance in OV from an instance in >> OBM. >> Problem is that the OV external network gateway is down, and after >> assigning >> a floating ip to the OV instance I have no access to or from it. I can >> only >> get to it from the network namespace on the OV controller (ip netns >> exec....) >> I have previously got this Openstack nested visualization working in >> VMware >> (vCloud) by enabling promiscuous mode on dvs portgoup, and also enabling >> promisc on the virtual interfaces of the virtual Openstack controllers. >> >> I tried enabling promiscuous mode on the OV controllers interfaces (OBM >> instances), but this seemed to make no difference. >> >> Any tips? Is this possible? >> >> Thanks >> >> Charles >> >> -- >> Charles Short >> Cloud Engineer >> Virtualization and Cloud Team >> European Bioinformatics Institute (EMBL-EBI) >> Tel: +44 (0)1223 494205 >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list(a)redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe(a)redhat.com > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com

Hi, I successfully deployed RDO Manager Liberty HA with VLANS on some HP blades + in-chassis switches with trunked VLANs ports (call this OBM (Openstack Bare Metal)) I wanted to deploy a test Openstack environment within this (call this OV (Openstack Virtual)) So I created two instances in OBM, and used packstack to roll out one controller and one compute node configured with vxlan tenant networks. This all worked and I can fire up an instance in OV, and it gets an ip. I then created an external network in OV with a VLAN id that matches an OBM network. The plan was to access an instance in OV from an instance in OBM. Problem is that the OV external network gateway is down, and after assigning a floating ip to the OV instance I have no access to or from it. I can only get to it from the network namespace on the OV controller (ip netns exec....) I have previously got this Openstack nested visualization working in VMware (vCloud) by enabling promiscuous mode on dvs portgoup, and also enabling promisc on the virtual interfaces of the virtual Openstack controllers. I tried enabling promiscuous mode on the OV controllers interfaces (OBM instances), but this seemed to make no difference. Any tips? Is this possible? Thanks Charles

From the information that I have, promiscuous mode is part of the