Introduction
The Swisscom virtual BNG and Edge SDN M&C for the ONAP BBS use-case is a demo system. It is a functional prototype and it is not meant for production use. The whole system is running in a single OpenStack VM and therefore only able to support a small number of subscribers. The forwarding dataplane is implemented fully inside the VMs Linux networking stack and therefore not designed to support high data rates. The system is able to interact with ONAP according the BBS use-case definition.
Installation by Heat Template
The Swisscom virtual BNG and Edge SDN M&C is installed and initially set up by a single Heat Orchestration Template. Therefore the OpenStack cloud you would like to use for testing should support Orchestration with Heat. The complete initial BNG and Edge SDN M&C configuration is provided as Heat stack parameters. The Heat stack creates all the required OpenStack infrastructure, e.g. router, network, security group, port and vbng instance.
Once the stack is created, the vBNG configuration file is deployed to the instance to '$HOME/vbng.conf' and latest vBNG code is directly pulled from specified upstream git repository (default is the Swisscom repository) by cloud-init user-data script. The stack output shows initial vBNG configuration, the floating IP and how to connect to the instance by SSH. To create a stack in OpenStack heat you first require the Heat template from here: https://git.swisscom.com/projects/ZTXGSPON/repos/opnfv/browse/heat/vbng.yaml (Drop a note to michail salichos, David Perez Caparros or dbalsige in case you do not have access)
Option A) Upload template in Horizon
The stack can be created directly in OpenStack Horizon by:
- Navigating to 'Orchestration -> Stacks' in the sidebar
- Pressing the 'Launch Stack' button
- In 'Template Source' select to upload the template file 'vbng.yaml' and press 'Next'.
- Now heat asks for the stack input parameters, they can be set by just entering the desired values in the Horizon form.
The template defines a hopefully useful default for each parameter, therefore not much has to be changed for the Swisscom Lab installation. However, some things like e.g. image, flavor and key have to be selected in the drop-down menus. Also all the initial configuration can be changed there. For a full list of the supported stack parameters see the appendix below.
Option B) OpenStack Commandline Client
Source the openrc.sh file of your OpenStack tenant and create the heat stack the following way:
source Downloads/vbng-openrc.sh Please enter your OpenStack Password for project vBNG as user bng: openstack stack create -t Downloads/vbng.yaml vbngstack
In case you would like to overwrite default parameters with your custom values, try adding '--parameter <key=value>', e.g.:
openstack stack create -t Downloads/vbng.yaml vbngstack --parameter key='your_key' --parameter flavor='your_flavor' --parameter image='your_image'
A full list of the supported stack parameter is shown in the following table:
Appendix: Stack Parameters
| Key | Default Value | Description | Notes |
|---|---|---|---|
| OpenStack Settings | |||
| key | vbng | Name of the SSH keypair for logging in into instances | constraint: nova.keypair |
| image | "CentOS 7 x86_64 GenericCloud 1901" | Name of the glance image (only CentOS7 supported) | constraint: glance.image |
| flavor | a1.tiny | Flavor to use for instances, can be a small one (1vCPU/4GB RAM/10GB disk) | constraint: nova.flavor |
| extnet | external | Name of external network | |
int_cidr | 192.168.1.0/24 | Internal Network IPv4 Addressing in CIDR notation | |
| dns1 | 8.8.8.8 | Upstream DNS server 1 (Also used for customers) | |
dns2 | 8.8.4.4 | Upstream DNS server 2 | |
| vBNG Git Repository Settings | |||
| git_repo | ssh://git@git.swisscom.com:7999/ztxgspon/vbng.git | Virtual BNG Git Repository URL (ssh://) | |
| git_sshkey | NOT SHOWN HERE | SSH Private Key for Git Repository (Read-Only Access) | |
| git_hostkey | NOT SHOWN HERE | SSH Host Key for Git Host (git.swisscom.com) | |
| vBNG Settings | |||
| cust_cidr | 10.66.0.0/16 | Customer IPv4 Network in CIDR notation | |
| cust_gw | 10.66.0.1 | Customer IPv4 Network Gateway | |
| cust_dns | 8.8.8.8 | Customer DNS Server | |
cust_start | 10.66.1.1 | Customer IPv4 Range Start Address | |
| cust_end | 10.66.1.254 | Customer IPv4 Range End Address | |
| dhcp_cidr | 172.24.24.0/24 | DHCP Server / Relay Network in CIDR notation | |
| dhcp_ip | 172.24.24.1 | DHCP Server IPv4 Address | |
| relay_ip | 172.24.24.2 | DHCP Relay IPv4 Address | |
| in_tun_port | 4789 | UDP Port for incoming VxLAN Tunnels (Security Group) | |
| onap_dcae_ves_collector_url | http://172.30.0.93:30235/eventListener/v7 | ONAP DCAE VES Collector URL | |
OLT Onboarding Configuration
TODO
ONAP Configuration
The installation and initial configuration of Edge SDN M&C + vBNG is done by an Heat stack template, see above. The parameters which must be modified in ONAP are the following:
- The IP of Edge SDN M&C in order to be accessed from SDN-C is currently hardcoded in the DG -> GENERIC-RESOURCE-API_bbs-internet-profile-network-topology-operation-common-huawei.json (<parameter name='prop.sdncRestApi.thirdpartySdnc.url' value='http://172.30.0.121:5000' />). The Edge SDN M&C external controller is not registered in ESR for this release. Note: The IP above is provided by Heat stack output, it is the Floating IP of the vBNG instance in Swisscoms Lab.
- To update the IP of Edge SDN M&C in the corresponding DG, one must export the relevant DG mentioned earlier, update the IP, import back and finally enable the DG.
