... | @@ -2,23 +2,25 @@ |
... | @@ -2,23 +2,25 @@ |
|
|
|
|
|
**Introduction**
|
|
**Introduction**
|
|
|
|
|
|
We at Swisscom Innovations we are looking for solutions to deploy OpenAir-CN (the core network part) on an OpenStack cloud and having that procedure automated as much as possible. Therefore we created a Heat orchestration template, which can be used for this task. We think it might be useful for the community, thats why we share it here.
|
|
Swisscom Innovations is looking for a simple solution to deploy OpenAir-CN (the core network part) on an arbitrary OpenStack public cloud and having that procedure automated as much as possible. Therefore we created a Heat orchestration template, which can be used for this task. The goal is to compile install and configure openair-cn as vEPC in the cloud. Swisscom thinks it might be useful for the community, thats why it is shared here. Feel free to ask questions to the openair-cn mailinglist or directly to @dbalsige.
|
|
|
|
|
|
**Deployed Architecture**
|
|
**Deployed Architecture**
|
|
![tutorial-arch](/uploads/195c7b8d3cff6258f9590efb5b9c4380/tutorial-arch.png)
|
|
|
|
|
|
|
|
|
|
Since generic OpenStack clouds do not support transporting SCTP packets over Floating IPs yet, we use a simple VPN setup for carrying the S1 traffic between eNBs and MME/SPGW instances. Have a look at the following picture to understand which networks and instance interfaces are used for which traffic:
|
|
|
|
|
|
**Requirements**
|
|
![tutorial-arch](/uploads/195c7b8d3cff6258f9590efb5b9c4380/tutorial-arch.png)
|
|
|
|
|
|
This section outlines what you will need in order to deploy Openair-CN on your OpenStack cloud.
|
|
**Requirements**
|
|
|
|
|
|
* Access to an OpenStack tenant
|
|
* Access to an OpenStack tenant
|
|
The template creates a router, a floating IP, a network, volumes, security groups, ports and instances on OpenStack. Keep in mind that your tenant has suffcient quotas to create those ressources.
|
|
|
|
|
|
The template creates a router, a floating IP, a network, volumes, security groups, ports and instances on OpenStack. Keep in mind that your tenant has sufficient quotas to create those ressources. OpenStack version should be at least Kilo, the template needs neutron, nova, glance, cinder and heat OpenStack services.
|
|
* The HOT (Heat Orchestration Template)
|
|
* The HOT (Heat Orchestration Template)
|
|
The heat template is in openair-cn located here
|
|
|
|
* Ubuntu images with os-*config tools installed.
|
|
|
|
Since the heat template uses Heat::SoftwareDeployment the image for the VM needs to have os-collect-config/heat-config/os-apply-config installed. Such images can be created manually and uploaded to your cloud.
|
|
|
|
|
|
|
|
|
|
The heat template is in openair-cn git located here and can be uploaded to heat by command-line client or directly in horizon.
|
|
|
|
* Ubuntu images with os-*config tools installed
|
|
|
|
|
|
|
|
Since the heat template uses OS::Heat::SoftwareDeployment, the base image for the instances needs to have os-collect-config/heat-config/os-apply-config tools installed. Such images can be created manually and uploaded to your cloud easily.
|
|
|
|
|
|
|
|
|
|
**1. Create custom Ubuntu images**
|
|
**1. Create custom Ubuntu images**
|
... | @@ -42,7 +44,7 @@ diskimage-builder/bin/disk-image-create vm ubuntu os-collect-config os-refresh-c |
... | @@ -42,7 +44,7 @@ diskimage-builder/bin/disk-image-create vm ubuntu os-collect-config os-refresh-c |
|
|
|
|
|
Use the horizon GUI or the glance command-line client to upload the image you just created to your OpenStack cloud.
|
|
Use the horizon GUI or the glance command-line client to upload the image you just created to your OpenStack cloud.
|
|
|
|
|
|
**3. Create an SSH keypair for logging in to instances**
|
|
**3. Create or upload an SSH keypair for logging into instances**
|
|
|
|
|
|
You will need an SSH key to login to instances created by Heat. Therefore an SSH keypair needs to be defined for your tenant. There are several possibilities to achieve this:
|
|
You will need an SSH key to login to instances created by Heat. Therefore an SSH keypair needs to be defined for your tenant. There are several possibilities to achieve this:
|
|
|
|
|
... | | ... | |