Installing and configuring OpenStack (release 0)

Infrastructure

Below a reference architecture for Openstack deployment.

Openstack Controller needs to be accesible from Resource Orchestrator (openmano).

Besides, interfaces of compute nodes must be connected to two networks:

• Telco/VNF management network, used by Configuration Manager (Juju Server) to configure the VNFs
• Inter-DC network, used to interconnect this datacenter to other datacenters (e.g. in MWC'16 demo, to interconnect the two sites).

VMs will be connected to these two networks at deployment time if requested by openmano.

VM creation (Openstack controller)

• Requirements for Openstack controller (this is only an example):
  • 1 vCPU (2 recommended)
  • 2GB RAM (4 recommended)
  • 40GB disk
  • Interfaces to connect to:
    • OSM network (to interact with RO)
    • DC infrastructure network (to interact with the compute servers and switches)

Installing Openstack

Installation from packstack

(Detailed here as a reference - example with RHEL OSP7)

yum install -y openstack-packstack
packstack --answer-file=/root/osp7.answers

where the answer-file has the following relevant information:

CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex,physnet_eno3:br-eno3
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:eno0,br-eno3:eno3

The first configuration line associates the tag physnet_eno3 to the bridge br-eno3. The second line associates the bridge br-eno3 to the interface eno3. Interface eno3 is the interface in compute nodes that is connected to the Telco/VNF management network and to the interDC network. Different VLANs will be used for each of these networks.

Configuring

• Configure a provider network for telco/VNF management network. In MWC'16 demo setup, this provider network uses the physical interface eno3, as specified during Openstack installation, and VLAN 2199. Additionally, a subnet is created, where VNFs will be assigned IP addresses from a range (e.g. 10.250.251.2-250), separate from the ranges used in other datacenters.

neutron net-create net-vnfmgmt --provider:network_type=vlan --provider:physical_network=physnet_eno3 --provider:segmentation_id=2199 --shared
neutron subnet-create --name subnet-mgmtOS net-mgmtOS 10.250.251.0/24 --allocation-pool start=10.250.251.2,end=10.250.251.250

• In order to run MWC'16 demo, another provider network is required to connect VNFs in Openstack datacenter to other datacenters. In MWC'16 demo setup, this provider network uses the physical interface eno3, as specified during Openstack installation, and VLAN 108. Additionally, a subnet is created, where VNFs will be assigned IP addresses from a range (e.g. 10.0.4.20-21).

neutron net-create net-interDC --provider:network_type=vlan --provider:physical_network=physnet_eno3 --provider:segmentation_id=108 --shared
neutron subnet-create --name subnet-interDC interDC 10.0.4.0/24  --allocation-pool start=10.0.4.20,end=10.0.4.21