[Openstack] network issue
Andreas Scheuring
scheuran at linux.vnet.ibm.com
Tue Jun 16 13:41:21 UTC 2015
Hi,
to 1.
no this does not make sense. Physnet is always a name for your physical
network. You could pick any name so you also could pick bond0.45 - but
it would not create any relationship to your bond!!!!). So my advice,
leave it to default, physnet or whatever. It will be referenced when
creating provider networks via the api.
But this option is especially relevant for tenant networks and provider
networks that are not public.
For the public network, just create your provider network with the
following provider attributes:
provider:network_type vlan
provider:segmentation_id <vlan-id>
router:external True
If your l3.conf files specifies the following parameter, it should work
without specifying any physical network
external_network_bridge = br-ex
Plugging bond0.45 into br-ex you have to do on your own via
> ovs-vsctl add-port br-ex bond0.45
Run "neutron net-show public" (or however your public net is named) to
view the details of your current public network.
to 2.
yes, it's sufficient on the network node!
I can't answer your question regarding your bond configuration. But
running bond in promisc mode sounds good to me.
Andreas
(IRC: scheuran)
On Di, 2015-06-16 at 13:02 +0000, Yngvi Páll Þorfinnsson wrote:
> Hi
>
> For the file configuration,
> /etc/neutron/plugins/ml2/ml2_conf.ini
>
> I have to questions:
>
> 1. Does it make sense to define bond0.45 as the 'physnet' ?
> Thus the definiton would be:
>
> [ml2_type_vlan]
> network_vlan_ranges = bond0.45:1001:2000 ?
>
> 2. Also, is it enough to have this definition on the network node ?
> (i.e. not for compute or controller node).
>
> Thanks and regards,
>
> Yngvi
>
> -----Original Message-----
> From: Andreas Scheuring [mailto:scheuran at linux.vnet.ibm.com]
> Sent: 16. júní 2015 07:47
> To: Yngvi Páll Þorfinnsson
> Cc: openstack at lists.openstack.org
> Subject: Re: [Openstack] network issue
>
> Your setup should be fine.
>
> Ensure, that you have created your openstack external network as flat provider network (default with devstack). Then adding br-ex into the vlan device enforces vlan traffic on the external network.
> An alternative approach would be to add the bond interface into the br-ex (instead of its vlan device) and create your openstack external provider network as vlan network using vlan 45.
> Both should work!
>
> In general take be aware, all the vlans you're using have to be enabled in your hardware switch as well if it's not a 20$ device.
>
> Andreas
> (IRC: scheuran)
>
>
> On Mo, 2015-06-15 at 17:31 +0000, Yngvi Páll Þorfinnsson wrote:
> > Hi
> >
> > We‘re using Ubuntu 14.04 on all servers. Using 1 controller node, 2
> > network nodes, 4 compute nodes as well as 4 swift nodes.
> >
> >
> >
> > I‘ve been doing some changes on my network configuration and
> > introducing vlans ( also bonding).
> >
> > My goal is to have all networks running on one 10G interface, as
> > VLANs.
> >
> > I‘ve done this already for the management- and tunnel network.
> >
> > This is the setup:
> >
> >
> >
> > bond0.48 - mgmt interface
> >
> > bond0.47 – tunnel interface
> >
> >
> >
> > and then I would add this one as well
> >
> >
> >
> > bond0.45 – external interface
> >
> >
> >
> > and then add the bridge:
> >
> >
> >
> > # ovs-vsctl add-port br-ex
> >
> > # ovs-vsctl add-port br-ex bond0.45
> >
> >
> >
> > I could be wrong here, with the „bond0.45“ ...
> >
> > So does it make sense to go this path? Or more critical: is it
> > possible to configure openstack like this?
> >
> >
> >
> > On the previous setup, I did configure the external br-ex like this:
> >
> >
> >
> > # ovs-vsctl add-port br-ex
> >
> > # ovs-vsctl add-port br-ex em3
> >
> >
> >
> > And defined be-ex and em3 in the interfaces file
> >
> > /etc/network/interfaces
> >
> > .
> >
> > .
> >
> > auto br-ex
> >
> > iface br-ex inet static
> >
> > address ip-number
> >
> > netmask 255.255.255.0
> >
> > network xxxx
> >
> > dns-nameservers yyyy
> >
> > dns-search siminn.is
> >
> > gateway zzzz
> >
> >
> >
> > auto em3
> >
> > iface em3 inet manual
> >
> > up ifconfig $IFACE 0.0.0.0 up
> >
> > up ip link set $IFACE promisc on
> >
> > down ip link set $IFACE promisc off
> >
> > down ifconfig $IFACE down
> >
> > .
> >
> >
> >
> >
> >
> > Could I achive this and configure the external network bridge, br-ex,
> > as a vlan ?
> >
> >
> >
> > Best regards
> >
> > Yngvi
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack at lists.openstack.org
> > Unsubscribe :
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
--
Andreas
(IRC: scheuran)
More information about the Openstack
mailing list