OSM Public Wiki - User contributions [en]

OSM Release THREE

2017-10-25T11:01:28Z

Harperm: /* Install from source */

Open Source MANO (OSM) is the open source community that aims to deliver a production-quality MANO stack for NFV, capable of consuming openly published information models, available to everyone, suitable for all VNFs, operationally significant and VIM-independent. OSM is aligned to NFV ISG information models while providing first-hand feedback based on its implementation experience.

{{#evu:https://www.youtube.com/watch?v=yBWSKwms47E
|alignment=right
}}

__TOC__

=Interaction with VIMs and VNFs=
The following figure shows OSM interaction with VIM and VNFs.

[[File:OSMconnectivity1.png|400px|OSM Release 1 connectivity 1]]

In simpler setups, OSM only requires a single interface as long as both VIM and VNF IP addresses are reachable

[[File:OSMconnectivity2.png|400px|OSM Release 1 connectivity 2]]

=Install OSM=

==Install from binaries (Recommended) ==
All you need to run OSM Release THREE is a single server or VM with the following requirements:
* MINIMUM: 4 CPUs, 8 GB RAM, 40GB disk and a single interface with Internet access
* RECOMMENDED: 8 CPUs, 16 GB RAM, 80GB disk and a single interface with Internet access
* Ubuntu16.04 (64bit varient required) as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release TWO|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release TWO#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh

==Install from source==
To install OSM Release THREE from source, requirements are the following:
* 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access
* Ubuntu16.04 ((64bit varient required) ) as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release THREE|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release THREE#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh --source
If you need to install from latest master (recommended for advanced users only), please use:
./install_osm.sh -b master --source

==Checking your installation==

<pre style="color: red">Please note that in OSM 3, authentication is performed using OpenIDConnect and OAuth2.0.
An identity provider has been added to the platform and provided as a service in the SO container running on port 8009.
This means both the browser and the UI server components (that run on the SO container) need to be able to access the SO container using identical URIs.
In short, the tuple of scheme://location:port needs to be reachable via both the browser accessing the system and the UI server running on the SO container (e.g. https://10.66.202.206:8009 for a sample deployment).
This means that if your SO container is behind a NAT that cannot reach the public address of the host, authentication and authorization will not be possible and you will not be able to proceed using the UI.
</pre>

After some time, you will get a fresh OSM Release THREE installation. You can access to the UI in the following URL (user:admin, password: admin):

You can connect to the service via a web browser (Google Chrome version 50 or later is recommended). Open a browser and connect to https://1.2.3.4:8443 , replacing 1.2.3.4 with the IP address of your host. Note that it uses https, not http. Google Chrome is recommended. If you are using Firefox and plan to use the self-signed certificate provided in the installation, please follow instructions at [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using2 Using untrusted, self-signed certificates]
Alternatively, you can run Launchpad with trusted CA signed SSL certs as per [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using Using a certificate signed by a trusted CA]
or, run Launchpad with SSL disabled as per [http://open.riftio.com/documentation/riftware/4.3/a/user-guide/run-launchpad-with-ssl-disabled.htm?Highlight=disable Run Launchpad with SSL Disabled]

[[File:OSMloginWindow.png|400px|OSM login window]]

Make sure that port 8443 is accessible, as well as the following required ports: 8000, 4567, 8008, 80, 9090.

As a result of the installation, three LXD containers are created in the host: RO, VCA, and SO-ub (running the SO and the UI), as shown in the figure below.

[[File:OSMcontainers.png|400px|OSM Release THREE installation result]]

=Adding VIM accounts=
Before proceeding, make sure that you have a site with a VIM configured to run with OSM. Three different kinds of VIMs are currently supported by OSM:
*OpenVIM. Check the following link to know how to install and use openvim for OSM: [[OpenVIM installation (Release THREE)]]. Openvim must run in 'normal' mode (not test or fake) to have real virtual machines reachable from OSM.
*OpenStack. Check the following link to learn how to configure OpenStack to be used by OSM: [[Openstack configuration (Release THREE)]]
*VMware vCloud Director. Check the following link to learn how to configure VMware VCD to be used by OSM: [[Configuring VMware vCloud Director for OSM Release THREE]]
*Amazon Web Services (AWS). Check the following link to learn how to configure AWS (EC2 and Virtual Private Cloud) to be used by OSM: [[Configuring AWS for OSM Release THREE]]
OSM can manage external SDN controllers to perform the dataplane underlay network connectivity on behalve of the VIM. See [[Configure VIM SDN ]]

==OpenVIM site==
===Using OSM cli===
osm vim-create --name openvim-site --auth_url http://10.10.10.10:9080/openvim --account_type openvim --description "Openvim site" --user dummy --password dummy --tenant dummy
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openvim-site", IP address: 10.10.10.10, VIM tenant: "osm")
export OPENMANO_TENANT=osm
openmano datacenter-create openvim-site http://10.10.10.10:9080/openvim --type openvim --description "Openvim site"
openmano datacenter-attach openvim-site --vim-tenant-name=osm
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Openstack site==
===Using OSM cli===
osm vim-create --name openstack-site --user admin --password userpwd --auth_url http://10.10.10.11:5000/v2.0 --tenant admin --account_type openstack
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openstack-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"
openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==VMware vCloud Director site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "vmware-site", IP address: 10.10.10.12, VIM tenant: "vmware-tenant", user: "osm", password: "osm4u", admin user: "admin", admin password: "adminpwd", organization: "orgVDC")
openmano datacenter-create vmware-site https://10.10.10.12 --type vmware --description "VMware site" --config '{admin_password: adminpwd, admin_username: admin, orgname: orgVDC}'
openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==VMware Integrated Openstack (VIO) site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openstack-site-vio4", IP address: 10.10.10.12, VIM tenant: "admin", user: "admin", password: "passwd")

openmano datacenter-create openstack-site-vio4 http://10.10.10.12:5000/v3 --type openstack --description "VMware integrated openstack site vio4" --config '{insecure: true, vim_type: VIO}'
openmano datacenter-attach openstack-site-vio4 --user=admin --password=passwd --vim-tenant-name=admin
--config='{APIversion: v3.3, dataplane_physical_net: dvs-46, "use_internal_endpoint":true,"dataplane_net_vlan_range":["1-5","7-10"]}'

Additional configuration for VIO:
* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM
* '''use_internal_endpoint''': When true it allows use of private API endpoints
* '''dataplane_physical_net''': The configured network_vlan_ranges at neutron for the SRIOV (binding direct) and passthrough (binding direct-physical) networks, e.g. 'physnet_sriov' in the above configuration. In case of VMware Integrated Openstack (VIO) provide moref ID of distributed virtual switch, e.g 'dvs-46' in above configuration.
* '''dataplane_net_vlan_range''': In case of VMware Integrated Openstack (VIO) provide vlan ranges for the SRIOV (binding direct) networks in format ['start_ID - end_ID']
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Amazon Web Services (AWS) site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "aws-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create aws-site https://aws.amazon.com --type aws --description "AWS Site" --config '{region: us-west-2}'
openmano datacenter-attach aws-site --user=AWS_USER_SECRET_KEY --password=AWS_USER_SECRET_ACCESS_KEY --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

=Deploying your first Network Service=
In this example we will deploy the following Network Service, consisting of two simple VNFs based on CirrOS connected by a simple VLD.

[[File:cirros_2vnf_ns.png|500px|NS with 2 CirrOS VNF]]

Before going on, download the required VNF and NS packages from this URL: https://osm-download.etsi.org/ftp/osm-3.0-three/examples/cirros_2vnf_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

Then, 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 cirros034
*In openvim:
#copy your image to the NFS shared folder (e.g. /mnt/openvim-nfs)
cp ./cirros-0.3.4-x86_64-disk.img /mnt/openvim-nfs/
openvim image-create --name cirros034 --path /mnt/openvim-nfs/cirros-0.3.4-x86_64-disk.img

==Onboarding a VNF==
*From the UI:
**Go to Catalog
**Click on the import button, then VNFD
**Drag and drop the VNF package file cirros_vnf.tar.gz in the importing area.
[[File:onboardingVNF.png|300px|Onboarding a VNF]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_vnf.tar.gz

==Onboarding a NS==
*From the UI:
**Go to Catalog
**Click on the import button, then NSD
**Drag and drop the NS package file cirros_2vnf_ns.tar.gz in the importing area.
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_2vnf_ns.tar.gz

==Instantiating the NS==
*From the UI:
**Go to Launchpad > Instantiate
**Select the NS descriptor to be instantiated, and click on Next
**Add a name to the NS instance, and click on Launch.
[[File:instantiatingNS.png|300px|Instantiating a NS (step 1)]] [[File:instantiatingNS-step2.png|400px|Instantiating a NS (step 2)]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:

/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -i <ns-instance-name> -d <nsd-id> -D <data-center-id>

Note: The nsd-id and data-center-id need to be replaced with the values from your setup.
Issue the following commands from the SO CLI(See the next section "Accessing CLI for viewing instantiated NS details" on how to access SO CLI) to determine the nsd-id and data-center-id,

* <code>show nsd-catalog nsd </code> - Displays the nsds in the catalog. Find the id of the cirros_2vnf_nsd NSD
* <code>show datacenters</code> - Displays the list of data centers configured in the RO. Choose the data center where the network service need to be instantiated.

Wait for the message that the NS has been successfully deployed, and that's all!

== Accessing CLI for viewing instantiated NS details ==

From the SO-ub container ("lxc exec SO-ub bash"), execute the following command to bring up SO CLI (username:admin password:admin)

/usr/rift/rift-shell -r -i /usr/rift -a /usr/rift/.artifacts -- rwcli

The CLI can be used to both configure the system and show operational-data from the system. For instance:
rift# show nsd-catalog # show the nsd catalog
rift# show vnfd-catalog # show vnfd catalog
rift# show ns-instance-config nsr # Lists instantiated network service
rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data

=Additional information=

*[[Deploying advanced Network Services (Release THREE)|Deploy advanced Network Services]]
*[[Creating your own VNF package (Release THREE)|Create your own VNF package]]
*[[Reference VNF and NS Descriptors (Release THREE)|Reference VNF and NS Descriptors]]
*[[Creating your own VNF charm (Release_THREE)|Creating your own VNF charm]]
*[[VIM emulator|VIM emulator]]
*[[How to report issues (Release THREE)|Have you detected any bug? Check this guide to see how to report issues]]
*[[Life Cycle Management of VNFs from the RO (Release THREE)|Life Cycle Management of VNFs from the RO]]
*[[Release THREE Data Model details|Data Model Details]]

*[[OSM Technical Videos|Technical and demonstration videos]]
*[[OSM workshops and events|Videos from workshops and events]]
*[[Software upgrade (Release THREE)|Software upgrade]]
*[[OSM MON Module Installation Guide (Release THREE)|OSM MON Module Installation Guide]]
*[[OSM MON Usage Guide (Release THREE)|OSM MON Usage Guide]]
*[[Logs and troubleshooting (Release THREE)|Logs and troubleshooting]]
*[[OSM E2E tests|E2E tests]]
*[[Technical FAQ|Technical FAQ]]

{{Feedback}}

OSM Release THREE

2017-10-25T11:00:54Z

Harperm: /* Install from binaries (Recommended) */

Open Source MANO (OSM) is the open source community that aims to deliver a production-quality MANO stack for NFV, capable of consuming openly published information models, available to everyone, suitable for all VNFs, operationally significant and VIM-independent. OSM is aligned to NFV ISG information models while providing first-hand feedback based on its implementation experience.

{{#evu:https://www.youtube.com/watch?v=yBWSKwms47E
|alignment=right
}}

__TOC__

=Interaction with VIMs and VNFs=
The following figure shows OSM interaction with VIM and VNFs.

[[File:OSMconnectivity1.png|400px|OSM Release 1 connectivity 1]]

In simpler setups, OSM only requires a single interface as long as both VIM and VNF IP addresses are reachable

[[File:OSMconnectivity2.png|400px|OSM Release 1 connectivity 2]]

=Install OSM=

==Install from binaries (Recommended) ==
All you need to run OSM Release THREE is a single server or VM with the following requirements:
* MINIMUM: 4 CPUs, 8 GB RAM, 40GB disk and a single interface with Internet access
* RECOMMENDED: 8 CPUs, 16 GB RAM, 80GB disk and a single interface with Internet access
* Ubuntu16.04 (64bit varient required) as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release TWO|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release TWO#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh

==Install from source==
To install OSM Release THREE from source, requirements are the following:
* 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access
* Ubuntu16.04 as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release THREE|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release THREE#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh --source
If you need to install from latest master (recommended for advanced users only), please use:
./install_osm.sh -b master --source

==Checking your installation==

<pre style="color: red">Please note that in OSM 3, authentication is performed using OpenIDConnect and OAuth2.0.
An identity provider has been added to the platform and provided as a service in the SO container running on port 8009.
This means both the browser and the UI server components (that run on the SO container) need to be able to access the SO container using identical URIs.
In short, the tuple of scheme://location:port needs to be reachable via both the browser accessing the system and the UI server running on the SO container (e.g. https://10.66.202.206:8009 for a sample deployment).
This means that if your SO container is behind a NAT that cannot reach the public address of the host, authentication and authorization will not be possible and you will not be able to proceed using the UI.
</pre>

After some time, you will get a fresh OSM Release THREE installation. You can access to the UI in the following URL (user:admin, password: admin):

You can connect to the service via a web browser (Google Chrome version 50 or later is recommended). Open a browser and connect to https://1.2.3.4:8443 , replacing 1.2.3.4 with the IP address of your host. Note that it uses https, not http. Google Chrome is recommended. If you are using Firefox and plan to use the self-signed certificate provided in the installation, please follow instructions at [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using2 Using untrusted, self-signed certificates]
Alternatively, you can run Launchpad with trusted CA signed SSL certs as per [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using Using a certificate signed by a trusted CA]
or, run Launchpad with SSL disabled as per [http://open.riftio.com/documentation/riftware/4.3/a/user-guide/run-launchpad-with-ssl-disabled.htm?Highlight=disable Run Launchpad with SSL Disabled]

[[File:OSMloginWindow.png|400px|OSM login window]]

Make sure that port 8443 is accessible, as well as the following required ports: 8000, 4567, 8008, 80, 9090.

As a result of the installation, three LXD containers are created in the host: RO, VCA, and SO-ub (running the SO and the UI), as shown in the figure below.

[[File:OSMcontainers.png|400px|OSM Release THREE installation result]]

=Adding VIM accounts=
Before proceeding, make sure that you have a site with a VIM configured to run with OSM. Three different kinds of VIMs are currently supported by OSM:
*OpenVIM. Check the following link to know how to install and use openvim for OSM: [[OpenVIM installation (Release THREE)]]. Openvim must run in 'normal' mode (not test or fake) to have real virtual machines reachable from OSM.
*OpenStack. Check the following link to learn how to configure OpenStack to be used by OSM: [[Openstack configuration (Release THREE)]]
*VMware vCloud Director. Check the following link to learn how to configure VMware VCD to be used by OSM: [[Configuring VMware vCloud Director for OSM Release THREE]]
*Amazon Web Services (AWS). Check the following link to learn how to configure AWS (EC2 and Virtual Private Cloud) to be used by OSM: [[Configuring AWS for OSM Release THREE]]
OSM can manage external SDN controllers to perform the dataplane underlay network connectivity on behalve of the VIM. See [[Configure VIM SDN ]]

==OpenVIM site==
===Using OSM cli===
osm vim-create --name openvim-site --auth_url http://10.10.10.10:9080/openvim --account_type openvim --description "Openvim site" --user dummy --password dummy --tenant dummy
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openvim-site", IP address: 10.10.10.10, VIM tenant: "osm")
export OPENMANO_TENANT=osm
openmano datacenter-create openvim-site http://10.10.10.10:9080/openvim --type openvim --description "Openvim site"
openmano datacenter-attach openvim-site --vim-tenant-name=osm
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Openstack site==
===Using OSM cli===
osm vim-create --name openstack-site --user admin --password userpwd --auth_url http://10.10.10.11:5000/v2.0 --tenant admin --account_type openstack
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openstack-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"
openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==VMware vCloud Director site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "vmware-site", IP address: 10.10.10.12, VIM tenant: "vmware-tenant", user: "osm", password: "osm4u", admin user: "admin", admin password: "adminpwd", organization: "orgVDC")
openmano datacenter-create vmware-site https://10.10.10.12 --type vmware --description "VMware site" --config '{admin_password: adminpwd, admin_username: admin, orgname: orgVDC}'
openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==VMware Integrated Openstack (VIO) site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openstack-site-vio4", IP address: 10.10.10.12, VIM tenant: "admin", user: "admin", password: "passwd")

openmano datacenter-create openstack-site-vio4 http://10.10.10.12:5000/v3 --type openstack --description "VMware integrated openstack site vio4" --config '{insecure: true, vim_type: VIO}'
openmano datacenter-attach openstack-site-vio4 --user=admin --password=passwd --vim-tenant-name=admin
--config='{APIversion: v3.3, dataplane_physical_net: dvs-46, "use_internal_endpoint":true,"dataplane_net_vlan_range":["1-5","7-10"]}'

Additional configuration for VIO:
* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM
* '''use_internal_endpoint''': When true it allows use of private API endpoints
* '''dataplane_physical_net''': The configured network_vlan_ranges at neutron for the SRIOV (binding direct) and passthrough (binding direct-physical) networks, e.g. 'physnet_sriov' in the above configuration. In case of VMware Integrated Openstack (VIO) provide moref ID of distributed virtual switch, e.g 'dvs-46' in above configuration.
* '''dataplane_net_vlan_range''': In case of VMware Integrated Openstack (VIO) provide vlan ranges for the SRIOV (binding direct) networks in format ['start_ID - end_ID']
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Amazon Web Services (AWS) site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "aws-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create aws-site https://aws.amazon.com --type aws --description "AWS Site" --config '{region: us-west-2}'
openmano datacenter-attach aws-site --user=AWS_USER_SECRET_KEY --password=AWS_USER_SECRET_ACCESS_KEY --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

=Deploying your first Network Service=
In this example we will deploy the following Network Service, consisting of two simple VNFs based on CirrOS connected by a simple VLD.

[[File:cirros_2vnf_ns.png|500px|NS with 2 CirrOS VNF]]

Before going on, download the required VNF and NS packages from this URL: https://osm-download.etsi.org/ftp/osm-3.0-three/examples/cirros_2vnf_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

Then, 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 cirros034
*In openvim:
#copy your image to the NFS shared folder (e.g. /mnt/openvim-nfs)
cp ./cirros-0.3.4-x86_64-disk.img /mnt/openvim-nfs/
openvim image-create --name cirros034 --path /mnt/openvim-nfs/cirros-0.3.4-x86_64-disk.img

==Onboarding a VNF==
*From the UI:
**Go to Catalog
**Click on the import button, then VNFD
**Drag and drop the VNF package file cirros_vnf.tar.gz in the importing area.
[[File:onboardingVNF.png|300px|Onboarding a VNF]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_vnf.tar.gz

==Onboarding a NS==
*From the UI:
**Go to Catalog
**Click on the import button, then NSD
**Drag and drop the NS package file cirros_2vnf_ns.tar.gz in the importing area.
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_2vnf_ns.tar.gz

==Instantiating the NS==
*From the UI:
**Go to Launchpad > Instantiate
**Select the NS descriptor to be instantiated, and click on Next
**Add a name to the NS instance, and click on Launch.
[[File:instantiatingNS.png|300px|Instantiating a NS (step 1)]] [[File:instantiatingNS-step2.png|400px|Instantiating a NS (step 2)]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:

/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -i <ns-instance-name> -d <nsd-id> -D <data-center-id>

Note: The nsd-id and data-center-id need to be replaced with the values from your setup.
Issue the following commands from the SO CLI(See the next section "Accessing CLI for viewing instantiated NS details" on how to access SO CLI) to determine the nsd-id and data-center-id,

* <code>show nsd-catalog nsd </code> - Displays the nsds in the catalog. Find the id of the cirros_2vnf_nsd NSD
* <code>show datacenters</code> - Displays the list of data centers configured in the RO. Choose the data center where the network service need to be instantiated.

Wait for the message that the NS has been successfully deployed, and that's all!

== Accessing CLI for viewing instantiated NS details ==

From the SO-ub container ("lxc exec SO-ub bash"), execute the following command to bring up SO CLI (username:admin password:admin)

/usr/rift/rift-shell -r -i /usr/rift -a /usr/rift/.artifacts -- rwcli

The CLI can be used to both configure the system and show operational-data from the system. For instance:
rift# show nsd-catalog # show the nsd catalog
rift# show vnfd-catalog # show vnfd catalog
rift# show ns-instance-config nsr # Lists instantiated network service
rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data

=Additional information=

*[[Deploying advanced Network Services (Release THREE)|Deploy advanced Network Services]]
*[[Creating your own VNF package (Release THREE)|Create your own VNF package]]
*[[Reference VNF and NS Descriptors (Release THREE)|Reference VNF and NS Descriptors]]
*[[Creating your own VNF charm (Release_THREE)|Creating your own VNF charm]]
*[[VIM emulator|VIM emulator]]
*[[How to report issues (Release THREE)|Have you detected any bug? Check this guide to see how to report issues]]
*[[Life Cycle Management of VNFs from the RO (Release THREE)|Life Cycle Management of VNFs from the RO]]
*[[Release THREE Data Model details|Data Model Details]]

*[[OSM Technical Videos|Technical and demonstration videos]]
*[[OSM workshops and events|Videos from workshops and events]]
*[[Software upgrade (Release THREE)|Software upgrade]]
*[[OSM MON Module Installation Guide (Release THREE)|OSM MON Module Installation Guide]]
*[[OSM MON Usage Guide (Release THREE)|OSM MON Usage Guide]]
*[[Logs and troubleshooting (Release THREE)|Logs and troubleshooting]]
*[[OSM E2E tests|E2E tests]]
*[[Technical FAQ|Technical FAQ]]

{{Feedback}}

OSM Release THREE

2017-10-18T14:32:03Z

Harperm: /* Install from binaries (Recommended) */

Open Source MANO (OSM) is the open source community that aims to deliver a production-quality MANO stack for NFV, capable of consuming openly published information models, available to everyone, suitable for all VNFs, operationally significant and VIM-independent. OSM is aligned to NFV ISG information models while providing first-hand feedback based on its implementation experience.

{{#evu:https://www.youtube.com/watch?v=yBWSKwms47E
|alignment=right
}}

__TOC__

=Interaction with VIMs and VNFs=
The following figure shows OSM interaction with VIM and VNFs.

[[File:OSMconnectivity1.png|400px|OSM Release 1 connectivity 1]]

In simpler setups, OSM only requires a single interface as long as both VIM and VNF IP addresses are reachable

[[File:OSMconnectivity2.png|400px|OSM Release 1 connectivity 2]]

=Install OSM=

==Install from binaries (Recommended) ==
All you need to run OSM Release THREE is a single server or VM with the following requirements:
* MINIMUM: 4 CPUs, 8 GB RAM, 40GB disk and a single interface with Internet access
* RECOMMENDED: 8 CPUs, 16 GB RAM, 80GB disk and a single interface with Internet access
* Ubuntu16.04 as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release TWO|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release TWO#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh

==Install from source==
To install OSM Release THREE from source, requirements are the following:
* 8 CPUs, 16 GB RAM, 100GB disk and a single interface with Internet access
* Ubuntu16.04 as base image (http://releases.ubuntu.com/16.04/), configured to run LXD containers. If you don't have LXD configured, you can follow the instructions here ([[LXD configuration for OSM Release THREE|LXD configuration]]).

Note: If you wish to install OSM Release THREE from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD configuration for OSM Release THREE#LXD within LXD (optional, only for advanced users)|Nested containers]]).

Once you have prepared the host with the previous requirements, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-3.0-three/install_osm.sh
chmod +x install_osm.sh
./install_osm.sh --source
If you need to install from latest master (recommended for advanced users only), please use:
./install_osm.sh -b master --source

==Checking your installation==

<pre style="color: red">Please note that in OSM 3, authentication is performed using OpenIDConnect and OAuth2.0.
An identity provider has been added to the platform and provided as a service in the SO container running on port 8009.
This means both the browser and the UI server components (that run on the SO container) need to be able to access the SO container using identical URIs.
In short, the tuple of scheme://location:port needs to be reachable via both the browser accessing the system and the UI server running on the SO container (e.g. https://10.66.202.206:8009 for a sample deployment).
This means that if your SO container is behind a NAT that cannot reach the public address of the host, authentication and authorization will not be possible and you will not be able to proceed using the UI.
</pre>

After some time, you will get a fresh OSM Release THREE installation. You can access to the UI in the following URL (user:admin, password: admin):

You can connect to the service via a web browser (Google Chrome version 50 or later is recommended). Open a browser and connect to https://1.2.3.4:8443 , replacing 1.2.3.4 with the IP address of your host. Note that it uses https, not http. Google Chrome is recommended. If you are using Firefox and plan to use the self-signed certificate provided in the installation, please follow instructions at [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using2 Using untrusted, self-signed certificates]
Alternatively, you can run Launchpad with trusted CA signed SSL certs as per [http://open.riftio.com/documentation/riftware/4.3/a/monitor/avoiding-selfsigned-certificate-warnings.htm#Using Using a certificate signed by a trusted CA]
or, run Launchpad with SSL disabled as per [http://open.riftio.com/documentation/riftware/4.3/a/user-guide/run-launchpad-with-ssl-disabled.htm?Highlight=disable Run Launchpad with SSL Disabled]

[[File:OSMloginWindow.png|400px|OSM login window]]

Make sure that port 8443 is accessible, as well as the following required ports: 8000, 4567, 8008, 80, 9090.

As a result of the installation, three LXD containers are created in the host: RO, VCA, and SO-ub (running the SO and the UI), as shown in the figure below.

[[File:OSMcontainers.png|400px|OSM Release THREE installation result]]

=Adding VIM accounts=
Before proceeding, make sure that you have a site with a VIM configured to run with OSM. Three different kinds of VIMs are currently supported by OSM:
*OpenVIM. Check the following link to know how to install and use openvim for OSM: [[OpenVIM installation (Release THREE)]]. Openvim must run in 'normal' mode (not test or fake) to have real virtual machines reachable from OSM.
*OpenStack. Check the following link to learn how to configure OpenStack to be used by OSM: [[Openstack configuration (Release THREE)]]
*VMware vCloud Director. Check the following link to learn how to configure VMware VCD to be used by OSM: [[Configuring VMware vCloud Director for OSM Release THREE]]
*Amazon Web Services (AWS). Check the following link to learn how to configure AWS (EC2 and Virtual Private Cloud) to be used by OSM: [[Configuring AWS for OSM Release THREE]]
OSM can manage external SDN controllers to perform the dataplane underlay network connectivity on behalve of the VIM. See [[Configure VIM SDN ]]

==OpenVIM site==
===Using OSM cli===
osm vim-create --name openvim-site --auth_url http://10.10.10.10:9080/openvim --account_type openvim --description "Openvim site" --user dummy --password dummy --tenant dummy
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openvim-site", IP address: 10.10.10.10, VIM tenant: "osm")
export OPENMANO_TENANT=osm
openmano datacenter-create openvim-site http://10.10.10.10:9080/openvim --type openvim --description "Openvim site"
openmano datacenter-attach openvim-site --vim-tenant-name=osm
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Openstack site==
===Using OSM cli===
osm vim-create --name openstack-site --user admin --password userpwd --auth_url http://10.10.10.11:5000/v2.0 --tenant admin --account_type openstack
===Adding it directly in the RO===
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "openstack-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"
openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==VMware site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "vmware-site", IP address: 10.10.10.12, VIM tenant: "vmware-tenant", user: "osm", password: "osm4u", admin user: "admin", admin password: "adminpwd", organization: "orgVDC")
openmano datacenter-create vmware-site https://10.10.10.12 --type vmware --description "VMware site" --config '{admin_password: adminpwd, admin_username: admin, orgname: orgVDC}'
openmano datacenter-attach vmware-site --user=osm --password=osm4u --vim-tenant-name=vmware-tenant
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

==Amazon Web Services (AWS) site==
*Go into the RO container:
lxc exec RO -- bash
*Execute the following commands, using the appropriate parameters (e.g. site name: "aws-site", IP address: 10.10.10.11, VIM tenant: "admin", user: "admin", password: "userpwd")
export OPENMANO_TENANT=osm
openmano datacenter-create aws-site https://aws.amazon.com --type aws --description "AWS Site" --config '{region: us-west-2}'
openmano datacenter-attach aws-site --user=AWS_USER_SECRET_KEY --password=AWS_USER_SECRET_ACCESS_KEY --vim-tenant-name=admin
openmano datacenter-list
exit #or Ctrl+D to get out of the RO container
* Go to the GUI:
ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button

=Deploying your first Network Service=
In this example we will deploy the following Network Service, consisting of two simple VNFs based on CirrOS connected by a simple VLD.

[[File:cirros_2vnf_ns.png|500px|NS with 2 CirrOS VNF]]

Before going on, download the required VNF and NS packages from this URL: https://osm-download.etsi.org/ftp/examples/cirros_2vnf_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

Then, 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 cirros034
*In openvim:
#copy your image to the NFS shared folder (e.g. /mnt/openvim-nfs)
cp ./cirros-0.3.4-x86_64-disk.img /mnt/openvim-nfs/
openvim image-create --name cirros034 --path /mnt/openvim-nfs/cirros-0.3.4-x86_64-disk.img

==Onboarding a VNF==
*From the UI:
**Go to Catalog
**Click on the import button, then VNFD
**Drag and drop the VNF package file cirros_vnf.tar.gz in the importing area.
[[File:onboardingVNF.png|300px|Onboarding a VNF]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_vnf.tar.gz

==Onboarding a NS==
*From the UI:
**Go to Catalog
**Click on the import button, then NSD
**Drag and drop the NS package file cirros_2vnf_ns.tar.gz in the importing area.
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:
/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -s 127.0.0.1 -u cirros_2vnf_ns.tar.gz

==Instantiating the NS==
*From the UI:
**Go to Launchpad > Instantiate
**Select the NS descriptor to be instantiated, and click on Next
**Add a name to the NS instance, and click on Launch.
[[File:instantiatingNS.png|300px|Instantiating a NS (step 1)]] [[File:instantiatingNS-step2.png|400px|Instantiating a NS (step 2)]]
*From the SO CLI:
**From the SO-ub container ("lxc exec SO-ub bash"), execute the following command:

/root/SO/rwlaunchpad/plugins/rwlaunchpadtasklet/scripts/onboard_pkg -i <ns-instance-name> -d <nsd-id> -D <data-center-id>

Note: The nsd-id and data-center-id need to be replaced with the values from your setup.
Issue the following commands from the SO CLI(See the next section "Accessing CLI for viewing instantiated NS details" on how to access SO CLI) to determine the nsd-id and data-center-id,

* <code>show nsd-catalog nsd </code> - Displays the nsds in the catalog. Find the id of the cirros_2vnf_nsd NSD
* <code>show datacenters</code> - Displays the list of data centers configured in the RO. Choose the data center where the network service need to be instantiated.

Wait for the message that the NS has been successfully deployed, and that's all!

== Accessing CLI for viewing instantiated NS details ==

From the SO-ub container ("lxc exec SO-ub bash"), execute the following command to bring up SO CLI (username:admin password:admin)

/usr/rift/rift-shell -r -i /usr/rift -a /usr/rift/.artifacts -- rwcli

The CLI can be used to both configure the system and show operational-data from the system. For instance:
rift# show nsd-catalog # show the nsd catalog
rift# show vnfd-catalog # show vnfd catalog
rift# show ns-instance-config nsr # Lists instantiated network service
rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data

=Additional information=

*[[Deploying advanced Network Services (Release THREE)|Deploy advanced Network Services]]
*[[Creating your own VNF package (Release THREE)|Create your own VNF package]]
*[[Reference VNF and NS Descriptors (Release THREE)|Reference VNF and NS Descriptors]]
*[[Creating your own VNF charm (Release_THREE)|Creating your own VNF charm]]
*[[VIM emulator|VIM emulator]]
*[[How to report issues (Release THREE)|Have you detected any bug? Check this guide to see how to report issues]]
*[[Life Cycle Management of VNFs from the RO (Release THREE)|Life Cycle Management of VNFs from the RO]]
*[[Release THREE Data Model details|Data Model Details]]

*[[OSM Technical Videos|Technical and demonstration videos]]
*[[OSM workshops and events|Videos from workshops and events]]
*[[Software upgrade (Release THREE)|Software upgrade]]
*[[Logs and troubleshooting (Release THREE)|Logs and troubleshooting]]
*[[OSM E2E tests|E2E tests]]
*[[Technical FAQ|Technical FAQ]]

{{Feedback}}

File:OSM R2 Information Model.pdf

2017-07-19T14:37:09Z

Harperm: Harperm uploaded a new version of File:OSM R2 Information Model.pdf

Release TWO Data Model details

2017-07-13T12:39:25Z

Harperm: /* OSM Release One Descriptor Documentation */

'''
== OSM Release One Descriptor Documentation ==
'''
The document below contains a very detailed description of the OSM Release TWO Models:

[[Media:OSM R2 Information Model.pdf]]

File:OSM R2 Information Model.pdf

2017-07-13T12:38:22Z

Harperm:

File:Osm-r1-so-rest-api-guide.pdf

2017-03-06T15:43:56Z

Harperm: Harperm uploaded a new version of File:Osm-r1-so-rest-api-guide.pdf

OSM Release ONE
SO REST API Guide with Examples

File:Osm-r1-so-rest-api-guide.pdf

2017-03-06T15:38:36Z

Harperm: Harperm uploaded a new version of File:Osm-r1-so-rest-api-guide.pdf

OSM Release ONE
SO REST API Guide with Examples

File:Osm-r1-so-rest-api-guide.pdf

2017-02-21T23:14:43Z

Harperm: Harperm uploaded a new version of File:Osm-r1-so-rest-api-guide.pdf

OSM Release ONE
SO REST API Guide with Examples

File:Osm-r1-so-rest-api-guide.pdf

2017-02-21T15:37:22Z

Harperm: Harperm uploaded a new version of File:Osm-r1-so-rest-api-guide.pdf

OSM Release ONE
SO REST API Guide with Examples

File:Osm-r1-so-rest-api-guide.pdf

2017-02-21T10:57:26Z

Harperm: Harperm uploaded a new version of File:Osm-r1-so-rest-api-guide.pdf

OSM Release ONE
SO REST API Guide with Examples

OSM Release ONE

2017-02-19T18:57:36Z

Harperm: Add reference the the SO REST APIs with examples

File:Osm-r1-so-rest-api-guide.pdf

2017-02-19T18:43:59Z

Harperm: OSM Release ONE SO REST API Guide with Examples

OSM Release ONE
SO REST API Guide with Examples

Release 1 Onboarding Questionnaire

2016-09-30T16:46:14Z

Harperm:

The OSM VNF Onboarding questionnaire is for VNF creators who intend to onboard one
or more VNFs to the OSM Platform.

Answers to these questions are used to inform and guide the onboarding process.

[[File:Osm-r1-vnf-onboarding-questionaire-v1.pdf]]

File:Osm-r1-vnf-onboarding-questionaire-v1.pdf

2016-09-30T16:45:37Z

Harperm: OSM Release ONE VNF Onboarding Questionaire

OSM Release ONE VNF Onboarding Questionaire

Release ONE Data Model details

2016-09-30T16:40:31Z

Harperm:

'''
== OSM Release ONE Descriptor Documentation ==
'''

The attached document contains a very detailed description of the OSM Release ONE Models

[[Media:Osm-r1-information-model-descriptors.pdf]]

'''
== Virtual Network Function Descriptor (VNFD) Model ==
'''

The Virtual Network Function Descriptor (VNFD) is a deployment template that describes attributes that comprise a VNF.

For example:
* Platform resource requirements, such as CPU, memory, interfaces, and network
* Connectivity and interface requirements that can be used to establish virtual links within the NFVI30 between its Virtual Network Function Component (VNFC) instances, or between a VNF instance and the endpoint interface to the other network functions
* Special characteristics related to EPA attributes and performance capabilities
* KPI requirements and auto-scaling properties

'''The VNFD Entity Relation Diagram'''

[[Media:Osm-r1-vnfd.png]]

'''
== Network Service Descriptor (NSD) Model ==
'''

The Network Service Descriptor (NSD) is the top-level construct used for designing the service chains.

'''The NSD Entity Relation Diagram'''

[[Media:Osm-r1-nsd.png]]

'''
== Entity Relationship Diagrams ==
'''

[[File:Osm-r1-nsd.png|200px|thumb|left|NSD Entity Relationship Diagram]]

[[File:Osm-r1-vnfd.png|200px|thumb|left|VNFD Entity Relationship Diagram]]

Release ONE Data Model details

2016-09-30T16:14:13Z

Harperm:

Release ONE Data Model details

2016-09-30T16:11:17Z

Harperm:

OSM Release ONE Data Model:

* OSM Release ONE Descriptor Documentation:

* VNF Descriptor Model Diagram:
* Network Service Descriptor Model Diagram
[[File:Osm-r1-nsd.png|200px|thumb|left|NSD ERD]]
[[Media:Osm-r1-nsd.png]]

Release ONE Data Model details

2016-09-30T16:07:05Z

Harperm:

OSM Release ONE Data Model:

* OSM Release ONE Descriptor Documentation:

[[File:Osm-r1-nsd.png]]
* VNF Descriptor Model Diagram:

* Network Service Descriptor Model Diagram

File:Osm-r1-information-model-descriptors.pdf

2016-09-30T16:01:55Z

Harperm: OSM Release ONE MANO Information Model

OSM Release ONE MANO Information Model

File:Osm-r1-nsd.png

2016-09-30T16:01:03Z

Harperm: OSM Release ONE NSD ERD

OSM Release ONE NSD ERD

File:Osm-r1-vnfd.png

2016-09-30T16:00:18Z

Harperm: OSM Release ONE VNF ERD

OSM Release ONE VNF ERD

Release ONE Data Model details

2016-09-30T15:03:09Z

Harperm: OSM Release ONE Descriptor Documentation

OSM Release ONE Data Model:

OSM Release ONE Descriptor Documentation:

VNF Descriptor Model Diagram:

Network Service Descriptor Model Diagram

Release 1 Onboarding Questionnaire

2016-09-21T20:14:37Z

Harperm:

Release 1 Onboarding Questionnaire

2016-09-21T18:00:52Z

Harperm: Created page with "File:OSM Onboarding questionare-v1.0.docx"

[[File:OSM Onboarding questionare-v1.0.docx]]

File:OSM Onboarding questionare-v1.0.docx

2016-09-21T17:58:45Z

Harperm: OSM Onboarding Questionnaire for Release 1 version 1.0

OSM Onboarding Questionnaire for Release 1 version 1.0

OSM Release ONE

2016-09-21T17:43:26Z

Harperm:

*[[Release 1 Change Log|Release 1 Change Log]]
*[[Release 1 Logical architecture|Logical architecture]]
*[[Release 1 Minimal infrastructure|Minimal infrastructure]]
*[[Release 1 Installation|Installation]]
*[[Release 1 Data Model details|Data Model Details]]
*[[Release 1 HowTo guide for users|HowTo Guide for Users]]
*[[Release 1 Onboarding Questionnaire |Onboarding Questionnaire]]
*[[Release 1 Technical FAQ|Technical FAQ]]

{{Feedback}}