Skip to content

Latest commit

 

History

History
99 lines (71 loc) · 5.49 KB

README.md

File metadata and controls

99 lines (71 loc) · 5.49 KB
Raw

Tutorial: OpenIMSCore Network Service Record

This tutorial shows how to deploy a Network Service Record composed by 5 VNFs, a basic OpenIMSCore.

Compared to the Iperf-Server - Iperf-Client the example provided here is far more complex. So we assume you are fimiliar with the architecture.

Requirements

In order to execute this scenario, you need to have the following components up and running:

Store the VimInstance

Upload a VimInstance to the NFVO (e.g. this VimInstance).

Prepare the VNF Packages

Download the necessary files from the github repository and pack the VNF Packages for all 5 components ( scscf, icscf, pcscf, bind9, fhoss ).

Example for creating the Icscf Virtual Network Function Package

# Where to save the scripts
GIT_REPO_LOC=/opt/vnf_packages_example_openimscore_openbaton
# Clone the repository
git clone https://github.com/openbaton/opemimscore_example $GIT_REPO_LOC
# Create the .tar file which needs to be uploaded
cd $GIT_REPO_LOC/icscf
tar -cf icscf.tar *

For this example we assume the network used to interconnect the components is called "mgmt", if you want to modify this example ensure you are naming the network accordingly, the scripts from the github do not handle different network names yet. Also the vimInstanceName may be different to you, depending on your setup. The deployment_flavor is optional but should containg enough RAM for the default configuration of the components to be able to run, else some components may crash on start. This example setup has been successfuly tested on clean Ubuntu14.04 images with 2048 Mb RAM deployed on an Openstack Kilo (2015.1.3). Ensure that the image name defined in the Metadata.yaml of each package is existing.

Finally onboard the packages.

Store the Network Service Descriptor

Download the following NSD and upload it to the NFVO either using the dashboard or the cli. Take care to replace the vnfd ids with the ones you deployed.

Open the Dashboard (checkout the dashboard documentation for more information on how to use it), open it at the URL http://your-ip-here:8080 and log in (default username and password are admin and openbaton). Go to Catalogue -> NS Descriptors and choose the NSD of your choice by clicking on Upload NSD and selecting the Descriptor's json file.

Deploy the Network Service Descriptor

Deploy the stored NSD either using the dashboard.

You need to go again to the GUI, go to Catalogue -> NS Descriptors, and open the drop down menu by clicking on Action. Afterwards you need to press the Launch button in order to start the deployment of this NSD.

If you go to Orchestrate NS -> NS Records in the menu on the left side, you can follow the deployment process and check the current status of the deploying NSD.

Conclusions

Once the Network Service Record went to "ACTIVE" your OpenIMSCore - Bind9 - FHoSS deployment is finished.

ims-deployment

To test your OpenIMSCore you may use a Sip client of your choice. Be sure to use the realm defined in your Bind9 Virtual Network Function Descriptor while testing registration and call. By default the FHoSS conaints 2 users : alice and bob. The user is the same as the password, but you may also alter it to your needs modifying the FHoSS Virtual Network Function Descriptor ( You will find the users in "var_user_data.sql" file under the fhoss folder)

For Benchmarking we can use IMS Bench SIPp but then you should add more users to the FHoSS database since by default it only contains 2 users.

<script type="text/javascript" charset="utf-8"> // Creating custom :external selector $.expr[':'].external = function(obj){ return !obj.href.match(/^mailto\:/) && (obj.hostname != location.hostname); }; $(function(){ $('a:external').addClass('external'); $(".external").attr('target','_blank'); }) </script>