[sles-beta] wicked & openvswitch
Günther J. Niederwimmer
gjn at gjn.priv.at
Fri Aug 15 09:32:16 MDT 2014
Hello Karol,
so now i create your minimalist ifcfg-xxx files ;-) I create static configs
ifcfg-eth0
ifcfg-ovsbr0
ifcfg-eth1
ifcgf-ovsbr1
On this system are 4 NIC's
Two are in the moment not configured.
On start up the two ifcfg-ethX are known from wicked and configured.
the two ifcfg-ovsbrX are not known from wicked and NOT configured.
After the start up a "wicked ifreload all" bring up the two ifcfg-ovsbrX
The SUSEfirewal have also problems with this set this have to modify manual.
wicked I mean know the ifcfg-eth0.orig SuSEfirewall not.
In this situation I have no working network after boot and problem with nfs
and more
Now I have to test the KVM Clients for working with openvswitch and more ;)
I sent attached the original created configs from YaST2 and my modification what
I mean before this must be configured?.
You can have more Logs when you like :-).
Am Donnerstag, 14. August 2014, 10:54:21 schrieb Karol Mroz:
> On Thu, Aug 14, 2014 at 01:14:51PM +0200, Günther J. Niederwimmer wrote:
> > Hello Karol,
>
> Hello!
>
> > Am Dienstag, 12. August 2014, 19:46:33 schrieb Karol Mroz:
> > > Guenther et al,
> > >
> > > After some internal discussion, I wanted to address your queries
> > > regarding
> > > openvswitch (ovs) and Wicked, to hopefully clarify any confusion that
> > > may
> > > have arisen.
> > >
> > > Wicked is able to configure address, route and resolver settings of an
> > > ovs-style bridge. No more, no less. This means that the actual interface
> > > _needs_ to have been created and had a bridge port assigned by way of
> > > openvswitch itself (ie. ovs-vsctl. Wicked, currently, is _not_ able to
> > > create ovs-style bridges.
> > >
> > > To create and configure an ovs-style bridge on a SLES-12 system with
> > > openvswitch 2.1.2 and wicked-0.6.1, you may do the following:
> > >
> > > Assumptions:
> > > - eth0 will be the bridge port for ovs-style bridge called ovsbr0
> > > (adjust
> > > naming suit your needs/system)
> >
> > OK, I make all what you say but this is the most time not working. :-(
> >
> > a static configuration is not possible. I have ovsbr0, ovsbr1 ovsbr2
>
> I've applied both static and dhcp, and even a mixture to my ovsbrX through
> wicked successfully. Could you forward your ifcfg-ovsbrX files?
>
> My examples are as follows (ifcfg-ovsbr2 with ifcfg-eth2 as port interface
> config):
>
> 0. ifcfg-eth2
> BOOTPROTO='none'
> STARTMODE='auto'
>
> 1. pure dhcp
> BOOTPROTO='dhcp'
> STARTMODE='manual'
>
> 2. pure static
> BOOTPROTO='static'
> STARTMODE='manual'
> IPADDR='10.0.0.222/24'
>
> 3. mixture
> BOOTPROTO='dhcp'
> STARTMODE='manual'
> IPADDR='10.0.0.222/24'
>
> > With BOOTPROTO= 'dhcp' in ovsbr0 the network coming up AFTER boot
> > sometimes
> > with wicked ifreload all or ifup all? the most time not.
>
> Hrm, this is interesting behaviour
>
> `wicked ifup all` passes over interfaces with STARTMODE=manual
>
> Perhaps this is expected and correct behaviour, however, it
> contradicts with:
>
> `wicked ifreload all`
>
> which actually does bring up interfaces configured with STARTMODE=manual
>
> I will look into this. But in the meantime, please either reference
> the ovsbrX directly when doing an ifup:
>
> `wicked ifup ovsbrX`
>
> Or please use ifreload:
>
> `wicked ifreload all`
>
> Again, a manual STARTMODE is needed in the case of Wicked+ovs because
> Wicked can't yet create an ovs-style bridge. The bridge needs to be
> present (with port) before you try to configure. So, once booted, you
> need to manually bring up each ovsbrX interface directly.
>
> I hope thise helps,
> Karol
>
> PS. thanks for bringing the difference in ifup/ifreload behaviour with
> manual STARTMODE's to our attention!
>
> > But then I have a dhcp and a static address (configuration) I change only
> > "BOOTPROTO"
> >
> > The ovsbr1 is static configured (IPv6) this is working normal when the
> > ovsbr0 is coming up.
> >
> > > Procedure:
> > > 1. zypper in openvswitch && zypper in openvswitch-switch
> > >
> > > - this should pull in openvswitch-kmp-[default|desktop|etc]
> > >
> > > 2. systemctl enable openvswitch
> > >
> > > - allow openvswitch to start on reboot
> > >
> > > 3. systemctl start openvswitch
> > > 4. ovs-vsctl add-br ovsbr0
> > > 5. ovs-vsctl add-port ovsbr0 eth0
> > >
> > > 6. create /etc/sysconfig/network/ifcfg-eth0 to contain:
> > > BOOTPROTO='none'
> > > STARTMODE='auto'
> > >
> > > 7. create /etc/sysconfig/network/ifcfg-ovsbr0 to contain:
> > > BOOTPROTO='dhcp'
> > > STARTMODE='manual'
> > >
> > > 8. wicked ifup ovsbr0
> > >
> > > Verification:
> > > 1. ovs-vsctl show
> > >
> > > c1f92605-e9c2-4679-aa2a-20d7e55bf62d
> > >
> > > Bridge "ovsbr0"
> > >
> > > Port "eth0"
> > >
> > > Interface "eth0"
> > >
> > > Port "ovsbr0"
> > >
> > > Interface "ovsbr0"
> > >
> > > type: internal
> > >
> > > ovs_version: "2.1.2"
> > >
> > > 2. wicked ifstatus eth0 ovsbr0
> > >
> > > eth0 up
> > >
> > > link: #2, state up, mtu 1500
> > > type: ethernet, hwaddr 52:54:00:c4:23:89
> > > config: compat:/etc/sysconfig/network/ifcfg-eth0
> > >
> > > ovsbr0 up
> > >
> > > link: #6, state up, mtu 1500
> > > type: ethernet, hwaddr f6:43:72:fe:fd:40
> > > config: compat:/etc/sysconfig/network/ifcfg-ovsbr0
> > > leases: ipv4 dhcp granted
> > > leases: ipv6 dhcp granted
> > > addr: ipv4 10.0.0.233/24
> > > addr: ipv6 fd78:3b33:7892::2b6/64
> > > addr: ipv6 fd78:3b33:7892:0:39fb:22d6:9315:3f08/64
> > > addr: ipv6 fd78:3b33:7892:0:f443:72ff:fefe:fd40/64
> > >
> > > 3. No crash in Wicked was observed
> > >
> > > As you can see, Wicked treats the ovs-style bridge, ovsbr0, as an
> > > ethernet
> > > device. It _needs_ to be present in the system _before_ trying to
> > > configure
> > > the device by way of `wicked ifup`. Thus, the openvswitch service needs
> > > to
> > > running _before_ Wicked and the ovsbr0 bridge needs to be present in the
> > > ovs database with proper port interfaces added. If correctly configured
> > > this way, on reboot, you should be able to bring up ovsbr0 manually via
> > > a direct `wicked ifup ovsbr0`.
> > >
> > > To summarize the level of support for openvswitch in Wicked:
> > >
> > > Wicked can configure addressing/resolver/routing for an ovs-style
> > > bridge,
> > > but the bridge first needs to be created by openvswitch (for example
> > > manually via ovs-vsctl). Wicked currently does _not_ support ovs-style
> > > bridge _creation_. Creation, if deemed needed, would be a feature
> > > delivered
> > > via a Service Pack.
> > >
> > > Please try the above procedure and let us know how it works for you.
> > >
> > > Best Regards,
> > > Karol
--
mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network.tar.bz2
Type: application/x-bzip-compressed-tar
Size: 1075 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140815/43a90126/attachment.tbz2>
More information about the sles-beta
mailing list