Deploying Mirantis OpenStack 6.1 results in network configuration issues with br-aux
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Igor Zinovik |
Bug Description
From a configuration standpoint:
1. Fuel Master is a VMware Virtual Machine
2. The three Controller nodes are three VMware Virtual Machines sitting in separate clusters with compatible IP address schemes.
3. The Compute/Ceph Storage nodes (8 of them total I think) are Bare Metal Servers (Dell 820's). BIOS has been set up properly and the H710 controller has 8 disks each. Two for OS (RAID1), Two for Journal (RAID1), and four for Ceph-OSD.
4. Each Dell has one 1 Gbit NIC for Admin/PXE and a "trunk" of multiple 1 Gbit NICS for the other four networks.
Here is the Network, I setup:
**** Neutron with VLAN segmentation
** Public
IP Range 10.34.84.21 to 10.34.84.100
CIDR 10.34.84.0/22
Use VLAN tagging Yes, 1001
Gateway 10.34.84.1
Floating IP Range 10.34.84.101 to 10.34.84.199
** Storage
CIDR 192.168.1.0/24
Use VLAN tagging Yes, 102
** Management
CIDR 192.168.0.0/24
Use VLAN tagging Yes, 101
** Neutron L2 Configuration
VLAN ID Range 1002 to 1003
Base MAC Address fa:16:3e:00:00:00
** Neutron L3 Configuration
Internal Network CIDR 192.168.111.0/24
Internal Network Gateway 192.168.111.1
Guest OS DNS Servers 10.34.64.11 & 10.34.64.12
Network Verification was successful. However, when a deployment was attempted, Fuel Astute created the br-aux bridge on the root Network card (eth0), which removed br-mgmt, br-ext, etc from the other NICS and the deployment failed. This deployment with the same parameters works as expected when only Bare Metal servers are employed for the Controller nodes.
Changed in fuel: | |
assignee: | Fuel Partner Core (fuel-partner-core) → Igor Zinovik (izinovik) |
Bruce, please add fuel version and diagnostic snapshot?