Bug 1283812
Summary: | local_interface=bond0.120 in undercloud.conf create broken network configuration | |||
---|---|---|---|---|
Product: | [Community] RDO | Reporter: | Gonéri Le Bouder <goneri> | |
Component: | instack-undercloud | Assignee: | James Slagle <jslagle> | |
Status: | CLOSED EOL | QA Contact: | Shai Revivo <srevivo> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | Liberty | CC: | dsneddon, mcornea | |
Target Milestone: | --- | |||
Target Release: | Kilo | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1290568 (view as bug list) | Environment: | ||
Last Closed: | 2016-05-19 16:02:03 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1290568 |
Description
Gonéri Le Bouder
2015-11-20 00:20:44 UTC
This is the correct os-net-config configuration: {"network_config": [{"type": "ovs_bridge", "ovs_extra": ["br-set-external-id br-ctlplane bridge-id br-ctlplane"], "name": "br-ctlplane", "members": [{"type": "vlan", "name": "bond0", vlan_id: 120}], "addresses": [{"ip_netmask": "192.168.120.1/24"}]}]} Ok, it's more complicated than expected. the syntax above allow the creation of a internal OVS VLAN. That's not what we want. We just need the VLAN=true in /etc/sysconfig/network-scripts/ifcfg-bond0.120 and that's something os-net-config cannot do (yet?). I'd just submitted https://review.openstack.org/248246 upstream to fix the issue. (In reply to Gonéri Le Bouder from comment #1) > This is the correct os-net-config configuration: > {"network_config": [{"type": "ovs_bridge", "ovs_extra": ["br-set-external-id > br-ctlplane bridge-id br-ctlplane"], "name": "br-ctlplane", "members": > [{"type": "vlan", "name": "bond0", vlan_id: 120}], "addresses": > [{"ip_netmask": "192.168.120.1/24"}]}]} Actually, this isn't right. If you are adding VLAN 120 to the br-ctlplane interface, then you wouldn't want a VLAN also defined under the bridge. That is what is overwriting your ifcfg-vlan120. In that case, you want to add a VLAN interface to the bridge but put the IP address directly on br-ctlplane, not on the VLAN interface. We don't support that in os-net-config today. I see that your patch tries to add that functionality by overriding the interface object and allowing it to be specified as a VLAN. Here is what we support today in os-net-config: Rather than trying to add an existing VLAN interface to your bridge, you can add the bond to the bridge and create OVSIntPort interfaces as VLANs to talk over the desired VLAN. If you wanted to create the Linux bond outside of os-net-config, and have os-net-config create an OVS VLAN interface on top of that bond, you could use this configuration: network_config: - type: ovs_bridge name: br-ctlplane members: - type: vlan vlan_id: 120 ip_netmask: - 192.0.2.1/24 Then add the bond to the bridge by hand after creation. We do support the use case of creating the whole config with os-net-config: network_config: - type: ovs_bridge name: br-ctlplane members: - type: linux_bond name: bond0 members: - type: interface name: nic2 primary: true - type: interface name: nic3 - type: vlan vlan_id: 120 device: bond0 ip_netmask: - 192.0.2.1/24 Whether we use one of the above configs for os-net-config, or if we add the functionality to os-net-config to add a VLAN interface to the bridge, we will have to update instack to be able to produce these kinds of configs if we want the process automated. This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen. |