Bug 1241689 - [Docs] [Director] Documentation on how to deploy tenant vlan network with network isolation
Summary: [Docs] [Director] Documentation on how to deploy tenant vlan network with net...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: Director
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: Director
Assignee: Dan Macpherson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1241148
TreeView+ depends on / blocked
 
Reported: 2015-07-09 19:50 UTC by Marius Cornea
Modified: 2016-01-04 01:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-04 01:44:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marius Cornea 2015-07-09 19:50:28 UTC
Description of problem:

We need to add to the docs instruction on how to deploy overcloud with vlan tenant network when using network isolation.

I got a successful deployment by using the following but we need some more details on how to do this based on the supported network configurations:

openstack overcloud deploy --plan-uuid c2a99e75-f9b7-49c4-bbdc-a658a52ef766 --control-scale 3 --compute-scale 1 --ceph-storage-scale 0 --block-storage-scale 0 --swift-storage-scale 0 -e /home/stack/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml --network-cidr 10.19.95.0/24 --neutron-bridge-mappings datacentre:br-ex,vlan:br-vlan --neutron-network-vlan-ranges vlan:183:185 --neutron-network-type vlan --neutron-disable-tunneling

controller.yaml:

   resources:
      OsNetConfigImpl:
        type: OS::Heat::StructuredConfig
        properties:
          group: os-apply-config
          config:
            os_net_config:
              network_config:
                -
                  type: ovs_bridge
                  name: {get_input: bridge_name}
                  use_dhcp: false
                  addresses:
                    -
                      ip_netmask: {get_param: ExternalIpSubnet}
                  routes:
                    -
                      ip_netmask: 0.0.0.0/0
                      next_hop: 10.19.184.254
                  members:
                    -
                      type: interface
                      name: nic1
                -
                  type: ovs_bridge
                  name: br-vlan
                  addresses:
                    -
                      ip_netmask: {get_param: InternalApiIpSubnet}
                  members:
                    -
                      type: interface
                      name: nic2
                      primary: true
                -
                  type: interface
                  name: nic4
                  addresses:
                    -
                      ip_netmask: {get_param: TenantIpSubnet}

Comment 3 Andrew Dahms 2015-07-13 01:32:03 UTC
Assigning to dmacpher for review.

Comment 6 Andrew Dahms 2015-08-16 02:51:06 UTC
Looks good to me; moving to VERIFIED.

Comment 7 Andrew Dahms 2016-01-04 01:44:58 UTC
This content is now live on the Customer Portal; closing.


Note You need to log in before you can comment on or make changes to this bug.