Openstack configuration - Revision history

Ramonsalguer at 16:58, 17 February 2021

2021-02-17T16:58:43Z

← Older revision		Revision as of 16:58, 17 February 2021
Line 1:		Line 1:
			'''THIS PAGE IS DEPRECATED'''. OSM User Guide has been moved to a new location: '''https://osm.etsi.org/docs/user-guide/'''

			---

	__TOC__		__TOC__

Anwars at 16:12, 23 May 2019

2019-05-23T16:12:14Z

← Older revision		Revision as of 16:12, 23 May 2019
Line 86:		Line 86:
	* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.		* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.
	* '''no_port_security_extension''': Use for those openstack that do not have the port_security_extension. This property allows neutron to disable the port security. If this option is set, port security will never be disabled regardless of the descriptor indication.		* '''no_port_security_extension''': Use for those openstack that do not have the port_security_extension. This property allows neutron to disable the port security. If this option is set, port security will never be disabled regardless of the descriptor indication.
			* '''disable_network_port_security''': Use for those openstack that do not support port security enabled at network level (although port_security_extension is present). This property allows neutron to disable the port security by default at the time of network creation for all ports created on the created networks.

	The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes. For instance, the following config is used to add a VMware Integrated Openstack where floating IP addresses will be assigned to VNF mgmt interfaces, all deployments must land in the availability_zone "controller", and the vlan ranges for the SRIOV networks will be 1-5 and 7-10:		The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes. For instance, the following config is used to add a VMware Integrated Openstack where floating IP addresses will be assigned to VNF mgmt interfaces, all deployments must land in the availability_zone "controller", and the vlan ranges for the SRIOV networks will be 1-5 and 7-10:

Garciadeblas: Garciadeblas moved page Openstack configuration (Release FOUR) to Openstack configuration: Single page for latest release

2018-12-05T12:42:08Z

Garciadeblas moved page Openstack configuration (Release FOUR) to Openstack configuration: Single page for latest release

← Older revision	Revision as of 12:42, 5 December 2018
(No difference)

Garciadeblas at 10:32, 17 September 2018

2018-09-17T10:32:30Z

← Older revision		Revision as of 10:32, 17 September 2018
Line 72:		Line 72:
	* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM		* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM
	* '''use_internal_endpoint''': Set to True to force using internal endpoints		* '''use_internal_endpoint''': Set to True to force using internal endpoints
	~~For openstack API v3. (It is needed to provide domain variables)~~

	* '''APIversion''': (By default it used v3 if the ~~keystone auth-url ends with "v3"). Set to "v3.3" or "3" to use this openstack API version~~		For openstack API v3, the following parameters are required:
	* '''project_domain_id''', '''project_domain_name''': If ~~non of them are~~ provided "default" is used for project_domain_id		* '''project_domain_id''', '''project_domain_name''': If not provided, "default" is used for project_domain_id
	* '''user_domain_id''', '''user_domain_name''': If ~~non of them are~~ provided "default" is used for user_domain_id		* '''user_domain_id''', '''user_domain_name''': If not provided, "default" is used for user_domain_id
			* '''APIversion'''. Only required if the auth-url URL does not end with "v3". Set it to "v3.3" or "3" to use this openstack API version.

	ADVANCED configuration:		ADVANCED configuration:

Ramonsalguer: /* Configure openstack for OSM (basic) */

2018-08-07T13:41:54Z

Configure openstack for OSM (basic)

← Older revision		Revision as of 13:41, 7 August 2018
Line 17:		Line 17:
	'''4. Upload images'''		'''4. Upload images'''

	~~OSM will create the needed images into openstack at deployment time, but~~ the ~~process takes a long~~ time ~~and the provided path at VNFD must be accesible by OSM. For this reason~~, it is ~~recommended~~ to upload the images of the VNFs manually at openstack, using the following command:		For the time being, it is required to upload the images of the VNFs manually at openstack, using the following command:

	openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public cirros034		openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public cirros034

Tierno: /* Add openstack to OSM */

2018-05-31T11:12:44Z

Add openstack to OSM

← Older revision		Revision as of 11:12, 31 May 2018
Line 61:		Line 61:

	The following configuration can be added:		The following configuration can be added:
	* '''management_network_id''', '''management_network_name''': ~~To indicate the vim~~ management network id/name to use for the management VLD of NS descriptors. By default it uses same vim network name as VLD name. It can be set also at instantiation time.		* '''management_network_id''', '''management_network_name''': VIM management network id/name to use for the management VLD of NS descriptors. By default it uses same vim network name as VLD name. It can be set also at instantiation time.
	* '''security_groups''': To be used for the deployment		* '''security_groups''': To be used for the deployment
	* '''availability_zone''': To be used for the deployment. It can be:		* '''availability_zone''': To be used for the deployment. It can be:

Tierno: /* Add openstack to OSM */

2018-05-31T11:06:41Z

Add openstack to OSM

← Older revision		Revision as of 11:06, 31 May 2018
Line 61:		Line 61:

	The following configuration can be added:		The following configuration can be added:
			* '''management_network_id''', '''management_network_name''': To indicate the vim management network id/name to use for the management VLD of NS descriptors. By default it uses same vim network name as VLD name. It can be set also at instantiation time.
	* '''security_groups''': To be used for the deployment		* '''security_groups''': To be used for the deployment
	* '''availability_zone''': To be used for the deployment. It can be:		* '''availability_zone''': To be used for the deployment. It can be:

Tierno: /* Add openstack to OSM */

2018-05-31T10:52:24Z

Add openstack to OSM

← Older revision		Revision as of 10:52, 31 May 2018
Line 68:		Line 68:
	* '''region_name''': The region where the VM must be deployed.		* '''region_name''': The region where the VM must be deployed.
	* '''insecure''': (By default false). When true it allows authorization over a non trusted certificate over https		* '''insecure''': (By default false). When true it allows authorization over a non trusted certificate over https
			* '''ca_cert''': (incompatible with insecure). root certificate file to use for validating the openstack certificate
	* '''use_existing_flavors''': (By default false). Set to "True" to use the closer flavor with enough resources instead of creating a new flavor with the exact requirements. This option does not work for EPA (cpu pinning, huge pages, ...) where openmano still tries to create a flavor with the needed extra expects. Use this options when you do not have admin credentials (Available from future v2.0.2 version)		* '''use_existing_flavors''': (By default false). Set to "True" to use the closer flavor with enough resources instead of creating a new flavor with the exact requirements. This option does not work for EPA (cpu pinning, huge pages, ...) where openmano still tries to create a flavor with the needed extra expects. Use this options when you do not have admin credentials (Available from future v2.0.2 version)
	* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM		* '''vim_type''': Set to "VIO" to use VMware Integrated openstack as VIM
Line 84:		Line 85:
	* '''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']		* '''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']
	* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.		* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.
			* '''no_port_security_extension''': Use for those openstack that do not have the port_security_extension. This property allows neutron to disable the port security. If this option is set, port security will never be disabled regardless of the descriptor indication.

	The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes. For instance, the following config is used to add a VMware Integrated Openstack where floating IP addresses will be assigned to VNF mgmt interfaces, all deployments must land in the availability_zone "controller", and the vlan ranges for the SRIOV networks will be 1-5 and 7-10:		The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes. For instance, the following config is used to add a VMware Integrated Openstack where floating IP addresses will be assigned to VNF mgmt interfaces, all deployments must land in the availability_zone "controller", and the vlan ranges for the SRIOV networks will be 1-5 and 7-10:

Tierno at 10:39, 31 May 2018

2018-05-31T10:39:56Z

← Older revision		Revision as of 10:39, 31 May 2018
Line 81:		Line 81:
	* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of an openstack keypair		* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of an openstack keypair
	* '''dataplane_physical_net''': The physical network label used in Openstack both to identify SRIOV and passthrough interfaces (nova configuration) and also to specify the VLAN ranges used by SR-IOV interfaces (neutron configuration). In case of VMware Integrated Openstack (VIO) provide moref ID of distributed virtual switch.		* '''dataplane_physical_net''': The physical network label used in Openstack both to identify SRIOV and passthrough interfaces (nova configuration) and also to specify the VLAN ranges used by SR-IOV interfaces (neutron configuration). In case of VMware Integrated Openstack (VIO) provide moref ID of distributed virtual switch.
	* '''use_floating_ip''': (By default false). When true a management interface of a VNFD is automatically assigned a floating_ip -if possible-. The prefered method is to use a provider network		* '''use_floating_ip''': (By default false). When boolean true, a management interface of a VNFD is automatically assigned a floating_ip -if possible-. If there is not any floating ip avalialble, it tries to get one if there is only one pool. You can use a string "pool_id" (public network id) instead of boolean true, to indicate the pool to use in case there are several. Note that deployment is not aborted if failing to asign a floating ip. The prefered method instead of this is to use a provider network
	* '''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']		* '''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']
	* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.		* '''microversion''': This is an Openstack-only parameter that allows to specify a specific microversion to be used in nova. When using 'microversion: 2.32', it enables the use of Virtual Device Role Tagging, which allows to identify each VM interface with a tag (the tag will be the name of the interface in the VNFD) and convey that information to the VM as metadata. This implementation approach is due to the warning message in https://developer.openstack.org/api-guide/compute/microversions.html where it is stated that microversion backwards compatibility is not guaranteed and clients should always require a specific microversion. This functionality was introduced would not work with Openstack versions previous to Newton.

Ramonsalguer at 15:05, 22 May 2018

2018-05-22T15:05:56Z

← Older revision		Revision as of 15:05, 22 May 2018
Line 90:		Line 90:
	==Using the OSM client==		==Using the OSM client==
	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 --config='{security_groups: default, keypair: mykey}'		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 --config='{security_groups: default, keypair: mykey}'

	~~==Adding directly in the RO==~~
	~~openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site" --config='{security_groups: default, keypair: mykey}'~~
	~~openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin --config='{availability_zone: one}'~~

	~~NOTE: In case of adding the datacenter to the RO, after doing it, go to the GUI:~~
	~~ACCOUNTS > OSMOPENMANO > Click 'REFRESH STATUS' button~~