OSM Release ONE - Revision history

Garciadeblas: /* Install from source */

2017-03-23T11:04:47Z

Install from source

← Older revision		Revision as of 11:04, 23 March 2017
Line 23:		Line 23:
	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 (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~~ ONE\|LXD configuration]]).		* 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 ONE\|LXD configuration]]).

	Note: If you wish to install OSM Release One from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD within LXD\|Nested containers]]).		Note: If you wish to install OSM Release One from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD within LXD\|Nested containers]]).

Garciadeblas: /* Install from source */

2017-03-23T11:04:29Z

Install from source

← Older revision		Revision as of 11:04, 23 March 2017
Line 23:		Line 23:
	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 (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 1\|LXD configuration]]).		* 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 ONE\|LXD configuration]]).

	Note: If you wish to install OSM Release One from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD within LXD\|Nested containers]]).		Note: If you wish to install OSM Release One from inside a LXD container, you will need to enable nested containers following instructions here ([[LXD within LXD\|Nested containers]]).

Garciadeblas at 08:18, 8 March 2017

2017-03-08T08:18:25Z

← Older revision		Revision as of 08:18, 8 March 2017
Line 150:		Line 150:
	rift# show ns-instance-config nsr # Lists instantiated network service		rift# show ns-instance-config nsr # Lists instantiated network service
	rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data		rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data


	~~=Interacting with the System via the SO REST APIs=~~
	~~The following document describes how to interact with the systme using the SO REST APis.~~

	~~[[Media:Osm-r1-so-rest-api-guide.pdf]]~~

	=Additional information=		=Additional information=

Garciadeblas: Recovering an old version to remove a misleading comment

2017-03-06T16:14:04Z

Recovering an old version to remove a misleading comment

← Older revision		Revision as of 16:14, 6 March 2017
Line 68:		Line 68:
	lxc exec RO -- bash		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")		*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")
	~~'''This API of OpenStack is deprecated since [https://review.openstack.org/#/c/251530/ Nov 30, 2015]'''~~

	export OPENMANO_TENANT=osm		export OPENMANO_TENANT=osm
	openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"		openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"

Berpec at 14:46, 6 March 2017

2017-03-06T14:46:16Z

← Older revision		Revision as of 14:46, 6 March 2017
Line 68:		Line 68:
	lxc exec RO -- bash		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")		*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")
	'''This API of OpenStack is deprecated since [https://~~bugs~~.~~launchpad~~.~~net~~/~~openstack-manuals~~/~~+bug~~/~~1536422 2016-01-21~~]'''		'''This API of OpenStack is deprecated since [https://review.openstack.org/#/c/251530/ Nov 30, 2015]'''

	export OPENMANO_TENANT=osm		export OPENMANO_TENANT=osm

Berpec at 14:35, 6 March 2017

2017-03-06T14:35:44Z

← Older revision		Revision as of 14:35, 6 March 2017
Line 68:		Line 68:
	lxc exec RO -- bash		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")		*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")
			'''This API of OpenStack is deprecated since [https://bugs.launchpad.net/openstack-manuals/+bug/1536422 2016-01-21]'''

	export OPENMANO_TENANT=osm		export OPENMANO_TENANT=osm
	openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"		openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"

Garciadeblas: /* Instantiating the NS */

2017-03-03T14:15:47Z

Instantiating the NS

← Older revision		Revision as of 14:15, 3 March 2017
Line 134:		Line 134:
	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,		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 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.		* <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!		Wait for the message that the NS has been successfully deployed, and that's all!

Berpec: fix typo in a command

2017-03-03T14:08:02Z

fix typo in a command

← Older revision		Revision as of 14:08, 3 March 2017
Line 135:		Line 135:

	** <code>show nsd-catalog nsd </code> - Displays the nsds in the catalog. Find the id of the cirros_2vnf_nsd NSD		** <code>show nsd-catalog nsd </code> - Displays the nsds in the catalog. Find the id of the cirros_2vnf_nsd NSD
	** <code>show ~~data centers~~</code> - Displays the list of data centers configured in the RO. Choose the data center where the network service need to be instantiated.		** <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!		Wait for the message that the NS has been successfully deployed, and that's all!

Garciadeblas at 10:50, 21 February 2017

2017-02-21T10:50:35Z

← Older revision		Revision as of 10:50, 21 February 2017
Line 165:		Line 165:
	*[[Creating your own VNF package (Release ONE)\|Create your own VNF package]]		*[[Creating your own VNF package (Release ONE)\|Create your own VNF package]]
	*[[Reference VNF and NS Descriptors (Release ONE)\|Reference VNF and NS Descriptors]]		*[[Reference VNF and NS Descriptors (Release ONE)\|Reference VNF and NS Descriptors]]
			*[[Creating your own VNF charm (Release_ONE)\|Creating your own VNF charm]]
	*[[How to report issues (Release ONE)\|Have you detected any bug? Check this guide to see how to report issues]]		*[[How to report issues (Release ONE)\|Have you detected any bug? Check this guide to see how to report issues]]
	*[[Logs and troubleshooting (Release ONE)\|Logs and troubleshooting]]		*[[Logs and troubleshooting (Release ONE)\|Logs and troubleshooting]]

Harperm: Add reference the the SO REST APIs with examples

2017-02-19T18:57:36Z

Add reference the the SO REST APIs with examples

← Older revision		Revision as of 18:57, 19 February 2017
Line 150:		Line 150:
	rift# show ns-instance-config nsr # Lists instantiated network service		rift# show ns-instance-config nsr # Lists instantiated network service
	rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data		rift# show ns-instance-opdata nsr # Lists of instantiated network service op-data


			=Interacting with the System via the SO REST APIs=
			The following document describes how to interact with the systme using the SO REST APis.

			[[Media:Osm-r1-so-rest-api-guide.pdf]]

	=Additional information=		=Additional information=

← Older revision		Revision as of 10:50, 21 February 2017
Line 165:		Line 165:
	*[[Creating your own VNF package (Release ONE)\|Create your own VNF package]]		*[[Creating your own VNF package (Release ONE)\|Create your own VNF package]]
	*[[Reference VNF and NS Descriptors (Release ONE)\|Reference VNF and NS Descriptors]]		*[[Reference VNF and NS Descriptors (Release ONE)\|Reference VNF and NS Descriptors]]
			*[[Creating your own VNF charm (Release_ONE)\|Creating your own VNF charm]]
	*[[How to report issues (Release ONE)\|Have you detected any bug? Check this guide to see how to report issues]]		*[[How to report issues (Release ONE)\|Have you detected any bug? Check this guide to see how to report issues]]
	*[[Logs and troubleshooting (Release ONE)\|Logs and troubleshooting]]		*[[Logs and troubleshooting (Release ONE)\|Logs and troubleshooting]]