* more intelligent calculation of default port provider
* additional check of patchcord existing in the bridge
OVS provider should be used for fake (OVS) ports, inserted
into OVS bridge. OVS provider should be used for inserting
native linux interface into OVS bridge.
But if we try to add native linux subinterface into
OVS bridge we should use lnx provider for creating
such port correctly.
Change-Id: Ib76b3340eca1ea22095da1cfffe7c224a139fb71
Closes-bug: #1682835
interfaces members of bond
CI disabled, because next patch in the chain should be passed.
Whole chain should be merged at one moment.
Change-Id: Ie7804dac600b2ea4747d0117f4951f811ef834a1
Partial-bug: #1643920
Fuel-CI: disabled
New type of transformation 'override' was added, because hiera_hash()
function does not allow to override arrays. Arrays merged instead replace.
also fix sanitize_transformation for 'noop' transformations
Change-Id: Ic4c9c6c34d9e3a57392446b534d997666578d110
Related-bug: #1582898
If Port provider is not specified and Bridge provider is OVS, we need to
use OVS provider for Port instead of default one. Otherwise,
L23_stored_config would choose wrong provider.
Change-Id: I1213b70be19b6ce7324d69b1763d4bfd900fe3d9
Closes-Bug: #1555162
New provider `sriov` introduced for add-port action.
It accepts two vendor-specific arguments:
* sriov_numvfs: number of VF's to enable
* physnet: physnet to setup in nova-compute
virtfn network interfaces is ignored now.
Change-Id: Id42e09ef2cf955301cd64c28dcfcd60f61ae72af
Implements: blueprint support-sriov
This fix ensures that l3 route has been cleared
before we try to set default route. This is very
important for admin interface on the nodes that
do not have default gateway configured as they
need to go through admin node during deployment
stage.
This issue affects environments with subinterfaces
for admin interface as we cannot add new route
through new interface in runtime as we already
have default gateway through the different interface
which is eth0/eth1 almost each time.
E.g.
default via 10.109.17.1 dev eth1
should become
default via 10.109.17.1 dev br-fw-admin
But l3_clear_route does not understand that these routes
are different and thus does not clear the first one.
This in fact leads to inability to set default route
by puppet l3_ifconfig provider. Look into
https://bugs.launchpad.net/fuel/+bug/1447638 for more
details.
This fix adds 'interface' property into l3_clear_route
puppet type which is a hacky w/a for l23network ip route
management.
It also ensures that if route iface is changed we need to
recreate the route.
Change-Id: I44e45ce1e13a4836552b95440cdfb706a5c177c5
Closes-bug: #1492147
Related-bug: #1447638
Current implementation makes following order:
port(eth2)->port(eth2.102)->port(eth3)->port(eth3.103)
->ifconfig(eth2.102)->ifconfig(eth3.103)
Proposed changes modify prdering to:
port(eth2)->port(eth2.102)->ifconfig(eth2.102)->
port(eth3)->port(eth3.103)->ifconfig(eth3.103)
Change-Id: Ia9dcb3afdf9bad7cfc28ad8881d5c9b6e6473052
Closes-bug: #1452617
Hardcode 45s delay for LACP bonds and 15s for non-LACP. Only at node boot time.
System administrator can re-define this value by CLI
This patchset is a workaround and should be reverted in 7.0
after implementing this feature in UI
Change-Id: I329e26a0b4da1b2be676dd7f8e6eb39e89eb11f4
Related-bug: #1441435
Related-bug: #1456436
In some cases (for example slow LACP bonds or optical links)
system administrator need make delay between interface stay UP and
continue of boot process. This option allow make delay after interface UP.
Closes-bug: #1441435
Change-Id: I5013edc915b78687e1eebe5c61fe5a9befd222f6
Now l3_clear_route deletes route if routing tables
has the same route but with different gateway
Change-Id: If997b20243b29ad2f735c747d6fb12202433b90f
Closes-bug: #1453851
* Add simple puppet resource which clear all default gateways
before creating l3_ifconfig resources
* Add warnings to prevent from using 'ip route replace...'
command in context of interface setup
Change-Id: Ifa73c0a9a4f4df542ea8437b9894c3dce5cfee7e
Related-bug: #1447638
This fix contains two sub-fixes:
* old code contains wrong logical condition.
In some cases was called .empty? method for non-hash or nil objects
* while parsing transformations for bonds, 'disable-offloading' flag
should be passed to bond-members transparently.
Closes-bug: #1433462
Change-Id: I63920e964a2ef4d3eb26c7a6175d2a676b426de0
Old network configuration
(6.0 and early) has global flag for disabling offload.
New implementation has 'disable offloading' flag per interface.
This commit add default set of ethtool propertios for disabling
offloading if no ethtool properties given for corresponded interface
Change-Id: Ic1aab4a6cfd32a3211d9a5c449ba887b7dc05953
Closes-bug: #1431735
Partial-bug: #1431396
Blueprint: refactor-l23-linux-bridges
* Change conditions for prevent unnided execution chains of code.
* Prevent from multiple base interface autocreation for subinterface.
* Change order when transformation for base interface comes after
transformation for subinterface.
* fix "empty bond can't be added to bridge"
Fuel-CI: disable
Blueprint: refactor-l23-linux-bridges
Change-Id: Ib76fb7ef146416cad0d88fb6526a7ec7043fcd0b
if one not defined in transformations before
adding sub-interface.
Related blueprint fuel-library-modularization
Blueprint: refactor-l23-linux-bridges
Fuel-CI: disable
Change-Id: I68319eae0f125898d6a467546b40f39d1f479e8b
Squized 33 patchsets,
all changes detailed described in following blueprint.
Can't be merged without corresponded changes in Nailgun part.
Fuel-CI: disable
Change-Id: I3d7bf070ef6fc42ef82c14f30780672084db5e71
Blueprint: refactor-l23-linux-bridges
Some times patchcords was added bebore bond interface. In thos case full-text search may give
wrong positive answer. (substring 'bond0' found inside 'br-bond0').
Change-Id: Ie54d94ce83906a972b422c5a5bb048d61f26db7f
Closes-bug: #1375347
Creating linux native bonding in a "transformation" section of network_schema.
Also creates configuration records for all slave interfaces.
blueprint linux-bonding
Change-Id: Ifc69aab96555ae34fe9c0f0fe0c2789d538c8bfc
Add unordered interfaces and endpoints to the end of list in alphabetical order.
Closes-bug: #1278718
Change-Id: I0519de41c875d50758908974e8e04f014f27831c
This commit allow define MTU for interfaces and endpoints
Change-Id: I0038286fc75a6935cfcd6fefcfa6acd071a66f59
Blueprint: set-mtu-for-interfaces
BUG: 1274789
Andreas Jaeger