Bug 981470

Summary: Minimal requirements should include 2 NICs
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: doc-Getting_Started_GuideAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: low    
Version: 3.0CC: aortega, breeler, derekh, enakai, jkt, sgordon
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 981153 Environment:
Last Closed: 2013-07-25 21:39:09 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: 981153    
Bug Blocks: 1011085    

Description Stephen Gordon 2013-07-04 20:39:37 UTC
All in one installation with 1 NIC was a bit tenuous even under Nova networking though it did work. Issues are also being encountered with OpenStack networking in this setup (though again theoretically it shouldn't be impossible).

To guide users away from this complication it might be best to recommend 2 NICs.

+++ This bug was initially created as a clone of Bug #981153 +++

Document URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_OpenStack/3/html-single/Getting_Started_Guide/index.html#sect-Quick_Start_Deployment_using_PackStack

Section Number and Name: 
4.1. Quick Start Deployment using PackStack


Describe the issue: 
After the single node deployment with "packstack --allinone", the following OVS bridges are created for ovs-plugin agent.

===========
# ovs-vsctl show
ac567f64-8a31-4297-88a7-46369d8662c4
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "1.9.0"
===========

But a physical NIC used for the public network connection should be added to the br-ex by hand so that VM instances can access the public network.

# ovs-vsctl add-port br-ex eth1


In addition, this NIC should be different from the one used for API/management. (If you add API/management NIC to the bridge, it becomes inaccessible.)


Suggestions for improvement: 

1) Describe the following as a pre-req of single node deployment:

- The node needs to have at least two physical NICs connected to the same public network. We suppose they are eth0 and eht1 here.

- Assign IP address to eth0. This IP is used for API/management access.

- Bring up eth1 without assigning IP. Typically, this can be done with the following config file.

/etc/sysconfig/network-scripts/ifcfg-eth1
=============
DEVICE=eth1
HWADDR=00:40:26:BC:9A:AC
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
=============

2) Add the following step after "packstack --allinone".

# ovs-vsctl add-port br-ex eth1

Additional information: 

# rpm -qa | grep packstack
openstack-packstack-2013.1.1-0.20.dev632.el6ost.noarch

# rpm -qa | grep quantum
openstack-quantum-openvswitch-2013.1.2-3.el6ost.noarch
python-quantum-2013.1.2-3.el6ost.noarch
openstack-quantum-2013.1.2-3.el6ost.noarch
python-quantumclient-2.2.1-1.el6ost.noarch

--- Additional comment from Stephen Gordon on 2013-07-04 16:35:00 EDT ---

With the exception of confirming that we can no longer support all-in-one on a system with only 1 NIC this bug primarily seems to refer to tasks that PackStack should be performing.

Comment 2 Stephen Gordon 2013-07-25 21:39:09 UTC
Neutron team are working to ensure that this is not required.