Skip to content

Setting up Openstack for OSM TNG Bench

Haydar Qarawlus edited this page Nov 25, 2019 · 1 revision

This page contains links and exerts from websites and other resources and guides to configure Openstack to work with OSM and the tng-bench setup. This does not include the VPN connection. It is in a separate guide.

Necessary steps:

From OSM website: Assuming there is a public network.

  1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)

  2. Create a management network, with DHCP enabled, reachable from OSM (particularly from VCA container)

You need to create a management network, with DHCP enabled, and guarantee that this management network is reachable from OSM. The network is used by the VCA (Juju) for configuring the VNFs once they are running. It is recommended to create a provider network, isolated from Openstack. For instance, in order to create a provider network using physical interface em1 and VLAN 500 and with CIDR 10.208.0.0/24, you should run the following commands:

neutron net-create mgmt --provider:network_type=vlan --provider:physical_network=<INSERT_PUBLIC_NET_HERE> --provider:segmentation_id=500 --shared
neutron subnet-create --name subnet-mgmt mgmt 10.208.0.0/24 --allocation-pool start=10.208.0.2,end=10.208.0.254

3- Create a router from mgmt network in Openstack to the public network. This allows to allocate floating IPs 4- Add 8.8.8.8 to the mgmt subnet as a DNS provider.

5- If not done already, change security groups to allow all TCP, UDP, ICMP traffic to the deployed instances in Openstack.

6- Change the floating IP quota and other quotas according to this guide: https://github.com/CN-UPB/tng-sdk-benchmark/wiki/Increasing-floating-IP-limit-in-Openstack

7- Add the images that you want to execute to Openstack. Modify the images as well to add the softwares that you want to benchmark according to this guide: https://github.com/CN-UPB/tng-sdk-benchmark/wiki/Create-Custom-Cloud-Image Upload the images after modifications.

8- Use the correct image names in OSM VNFD and NSD