Talk: OSM Release ONE: Difference between revisions
Garciadeblas (talk | contribs) No edit summary |
Garciadeblas (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
OSM is an ETSI-hosted project to develop an Open Source NFV Management and Orchestration (MANO) software stack aligned with ETSI NFV. | OSM is an ETSI-hosted project to develop an Open Source NFV Management and Orchestration (MANO) software stack aligned with ETSI NFV. | ||
All OSM needs to deploy VNFs is some VNF packages (you will find some in the examples below) and one or several VIMs (+ compute nodes). The following figure illustrate | All OSM needs to deploy VNFs is some VNF packages (you will find some in the examples below) and one or several VIMs (+ compute nodes). The following figure illustrate the connectivity of OSM to the | ||
__TOC__ | __TOC__ | ||
Line 11: | Line 11: | ||
All you need to run OSM Release One is a single server or VM with the following requirements: | All you need to run OSM Release One is a single server or VM with the following requirements: | ||
* 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access | * 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access | ||
* Ubuntu16.04 as base image, configured to run LXD containers (see [[LXD configuration for OSM release 1|LXD configuration]]) | * Ubuntu16.04 as base image, configured to run LXD containers. If you (see [[LXD configuration for OSM release 1|LXD configuration]]) | ||
Once you have prepared a server or VM with the requirements specified [[Release 1 Minimal infrastructure|here]], and you have [[LXD configuration for OSM release 1|configured LXD on it]], all you need to do is: | Once you have prepared a server or VM with the requirements specified [[Release 1 Minimal infrastructure|here]], and you have [[LXD configuration for OSM release 1|configured LXD on it]], all you need to do is: | ||
Line 21: | Line 21: | ||
https://your_local_ip:8443 | https://your_local_ip:8443 | ||
==Adding a VIM account to be used by OSM== | |||
Before proceeding, make sure that you have a VIM configured to run with OSM. Three different kinds of VIMs are currently supported by OSM: | |||
*OpenVIM | |||
==Adding a VIM to OSM== | |||
Three | |||
* | |||
*OpenStack | *OpenStack | ||
* | *VMware vCloud Director | ||
The following instructions are required to be executed in the host to add each kind | The following instructions are required to be executed in the host to add each kind a datacenter, depending on the DC type | ||
*OpenVIM DC (e.g. IP address: 10.10.10.10, VIM tenant "osm") | *OpenVIM DC (e.g. IP address: 10.10.10.10, VIM tenant "osm") | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create openvim-site http://10.10.10.10:9080/openvim --type openvim --description "Openvim Datacenter" | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openvim-site --vim-tenant-name=osm | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openvim-site --vim-tenant-name=osm | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | ||
*OpenStack DC (e.g. IP address: 10.10.10.11, VIM tenant "admin", user "admin", password "userpwd") | *OpenStack DC (e.g. IP address: 10.10.10.11, VIM tenant "admin", user "admin", password "userpwd") | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack Datacenter" | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | ||
*VMware DC (e.g. IP address: 10.10.10.12, VIM tenant "vmware-tenant", user "osm", password "osm4u", admin user "admin", admin password "adminpwd") | *VMware DC (e.g. IP address: 10.10.10.12, VIM tenant "vmware-tenant", user "osm", password "osm4u", admin user "admin", admin password "adminpwd") | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create vmware-site https://10.10.10.12" --type vmware --description "VMware Datacenter" --config '{admin_password: adminpwd, admin_username: admin}' | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant | ||
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list | ||
Note: | Note: The name of the datacenter "vmware-site" has to match the name of the organization of "vCloud Director". Inside this organization the tenant "vmware-tenant" must exist | ||
==Using OSM through a simple Network Service== | |||
In this example we will deploy the following Network Service, consisting of a single VNF connected to a network. | |||
[[File:cirros_ns.jpg]] | |||
Before going on, download the required VNF and NS packages from this URL: https://osm-download.etsi.org/ftp/examples/cirros_ns/ | |||
== | ===Uploading VNF image to the VIM=== | ||
*Get the cirros 0.3.4 image from the following link: http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img | |||
*Onboard the image into the VIM. The instruction differs from one VIM to another: | |||
**In Openstack: | |||
openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public --property location="/mnt/powervault/virtualization/osm/CirrOS/cirros-0.3.4-x86_64-disk.img" cirros034 | |||
**In openvim: | |||
openvim image-create --name cirros034 --path /mnt/powervault/virtualization/osm/CirrOS/cirros-0.3.4-x86_64-disk.img | |||
===Onboarding a VNF=== | ===Onboarding a VNF=== | ||
*Access to the UI, click on the catalog, click on the import button and drag the file | |||
===Onboarding a NS=== | ===Onboarding a NS=== | ||
Line 68: | Line 73: | ||
==Additional information== | ==Additional information== | ||
* | *[[Release ONE Additional NS examples|Additional NS examples]] | ||
*[[Release ONE Creating your Additional NS examples|Additional NS examples]] | |||
*[[Release ONE Logs and troubleshooting|Logs and troubleshooting]] | *[[Release ONE Logs and troubleshooting|Logs and troubleshooting]] | ||
*[[Release 1 Data Model details|Data Model Details]] | *[[Release 1 Data Model details|Data Model Details]] | ||
*[https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseONE-FINAL.pdf OSM White Paper - Release ONE Technical Overview] | *[https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseONE-FINAL.pdf OSM White Paper - Release ONE Technical Overview] | ||
*[[Release 1 Technical FAQ|Technical FAQ]] | *[[Release 1 Technical FAQ|Technical FAQ]] |
Revision as of 15:15, 24 October 2016
OSM is an ETSI-hosted project to develop an Open Source NFV Management and Orchestration (MANO) software stack aligned with ETSI NFV.
All OSM needs to deploy VNFs is some VNF packages (you will find some in the examples below) and one or several VIMs (+ compute nodes). The following figure illustrate the connectivity of OSM to the
Install OSM
Install from source
All you need to run OSM Release One is a single server or VM with the following requirements:
- 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access
- Ubuntu16.04 as base image, configured to run LXD containers. If you (see LXD configuration)
Once you have prepared a server or VM with the requirements specified here, and you have configured LXD on it, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-1.0-one/install_from_source.sh chmod +x install_from_source.sh ./install_from_source.sh
After some time, you will get a fresh OSM Release One installation. You can access to the UI in the following URL (user:admin, password: admin):
https://your_local_ip:8443
Adding a VIM account to be used by OSM
Before proceeding, make sure that you have a VIM configured to run with OSM. Three different kinds of VIMs are currently supported by OSM:
- OpenVIM
- OpenStack
- VMware vCloud Director
The following instructions are required to be executed in the host to add each kind a datacenter, depending on the DC type
- OpenVIM DC (e.g. IP address: 10.10.10.10, VIM tenant "osm")
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create openvim-site http://10.10.10.10:9080/openvim --type openvim --description "Openvim Datacenter" lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openvim-site --vim-tenant-name=osm lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list
- OpenStack DC (e.g. IP address: 10.10.10.11, VIM tenant "admin", user "admin", password "userpwd")
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack Datacenter" lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list
- VMware DC (e.g. IP address: 10.10.10.12, VIM tenant "vmware-tenant", user "osm", password "osm4u", admin user "admin", admin password "adminpwd")
lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-create vmware-site https://10.10.10.12" --type vmware --description "VMware Datacenter" --config '{admin_password: adminpwd, admin_username: admin}' lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant lxc exec RO --env OPENMANO_TENANT=osm -- openmano datacenter-list
Note: The name of the datacenter "vmware-site" has to match the name of the organization of "vCloud Director". Inside this organization the tenant "vmware-tenant" must exist
Using OSM through a simple Network Service
In this example we will deploy the following Network Service, consisting of a single VNF connected to a network.
Before going on, download the required VNF and NS packages from this URL: https://osm-download.etsi.org/ftp/examples/cirros_ns/
Uploading VNF image to the VIM
- Get the cirros 0.3.4 image from the following link: http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
- Onboard the image into the VIM. The instruction differs from one VIM to another:
- In Openstack:
openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public --property location="/mnt/powervault/virtualization/osm/CirrOS/cirros-0.3.4-x86_64-disk.img" cirros034
- In openvim:
openvim image-create --name cirros034 --path /mnt/powervault/virtualization/osm/CirrOS/cirros-0.3.4-x86_64-disk.img
Onboarding a VNF
- Access to the UI, click on the catalog, click on the import button and drag the file