Openstack configuration (Release TWO) - Revision history

Garciadeblas at 09:33, 7 September 2017

2017-09-07T09:33:24Z

← Older revision		Revision as of 09:33, 7 September 2017
Line 66:		Line 66:
	The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:		The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:
	--config='{use_floating_ip: True, availability_zone: controller}'		--config='{use_floating_ip: True, availability_zone: controller}'
	~~--config='{use_floating_ip: True, availability_zone: [zone1, zone2]}'~~

Mirabal: /* Add openstack to OSM */

2017-08-29T09:14:01Z

Add openstack to OSM

← Older revision		Revision as of 09:14, 29 August 2017
Line 66:		Line 66:
	The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:		The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:
	--config='{use_floating_ip: True, availability_zone: controller}'		--config='{use_floating_ip: True, availability_zone: controller}'
			--config='{use_floating_ip: True, availability_zone: [zone1, zone2]}'

Garciadeblas at 07:24, 29 June 2017

2017-06-29T07:24:41Z

← Older revision		Revision as of 07:24, 29 June 2017
Line 19:		Line 19:
	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:		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:

	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		openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public cirros034

	'''5. Modify default security group or create a new one'''		'''5. Modify default security group or create a new one'''

Tierno: /* Add openstack to OSM */

2017-06-22T15:38:58Z

Add openstack to OSM

← Older revision		Revision as of 15:38, 22 June 2017
Line 55:		Line 55:
	* '''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
	* '''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 v1.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)
	* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (experimental)		* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (experimental)

Line 61:		Line 61:

	* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of a openstack keypair		* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of a openstack keypair
	* '''dataplane_physical_net''': The configured network_vlan_ranges at neutron for SRIOV networks, e.g. 'physnet_sriov' in the above configuration		* '''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
	* '''use_floating_ip''': (By default false). When true a management interface of a VNFD is automatically asigned a floating_ip -if possible-. The prefered method is to use a provider network		* '''use_floating_ip''': (By default false). When true a management interface of a VNFD is automatically asigned a floating_ip -if possible-. The prefered method is to use a provider network

	The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:		The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:
	--config='{use_floating_ip: True, availability_zone: controller}'		--config='{use_floating_ip: True, availability_zone: controller}'

Garciadeblas: /* Add openstack to OSM */

2017-06-22T13:38:44Z

Add openstack to OSM

← Older revision		Revision as of 13:38, 22 June 2017
Line 45:		Line 45:
	=Add openstack to OSM=		=Add openstack to OSM=

	There is a parameter called '''--config''' used to ~~suply~~ general ~~guidelines~~ both at datacenter creation and datacenter ~~association~~ to openmano tenant (~~this later precedes~~)		There is a parameter called '''--config''' used to supply general configuration options both at datacenter creation and datacenter attachment to openmano tenant (the latter prevails).
	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-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}'		openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin --config='{availability_zone: one}'

Tierno: /* Add openstack to OSM */

2017-06-05T14:16:48Z

Add openstack to OSM

← Older revision		Revision as of 14:16, 5 June 2017
Line 55:		Line 55:
	* '''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
	* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (~~code on BETA~~)		* '''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 v1.0.2 version)
			* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (experimental)

	ADVANCED configuration:		ADVANCED configuration:

Garciadeblas: /* Add openstack at OSM */

2017-04-21T12:39:20Z

Add openstack at OSM

← Older revision		Revision as of 12:39, 21 April 2017
Line 43:		Line 43:
	pci_passthrough_whitelist = {"vendor_id":"8086", "product_id":"10ed","physical_network":"physnet_sriov"}		pci_passthrough_whitelist = {"vendor_id":"8086", "product_id":"10ed","physical_network":"physnet_sriov"}

	=Add openstack at OSM=		=Add openstack to OSM=

	There is a parameter called '''--config''' used to suply general guidelines both at datacenter creation and datacenter association to openmano tenant (this later precedes)		There is a parameter called '''--config''' used to suply general guidelines both at datacenter creation and datacenter association to openmano tenant (this later precedes)

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

2017-04-21T12:39:12Z

Configure openstack for OSM (basic)

← Older revision		Revision as of 12:39, 21 April 2017
Line 23:		Line 23:
	'''5. Modify default security group or create a new one'''		'''5. Modify default security group or create a new one'''

	By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#~~Add_openstack_at_OSM~~]] )		By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#Add_openstack_to_OSM\|Add openstack to OSM]] )

	=Configure openstack for OSM (EPA)=		=Configure openstack for OSM (EPA)=

Garciadeblas at 12:38, 21 April 2017

2017-04-21T12:38:16Z

← Older revision		Revision as of 12:38, 21 April 2017
Line 23:		Line 23:
	'''5. Modify default security group or create a new one'''		'''5. Modify default security group or create a new one'''

	By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#~~Add openstack at OSM~~]] )		By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#Add_openstack_at_OSM]] )

	=Configure openstack for OSM (EPA)=		=Configure openstack for OSM (EPA)=

Garciadeblas: Created page with "TOC =Configure openstack for OSM (basic)= '''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)''' '''2. Create a managem..."

2017-04-21T12:37:00Z

Created page with "__TOC__ =Configure openstack for OSM (basic)= '''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)''' '''2. Create a managem..."

New page

__TOC__

=Configure openstack for OSM (basic)=

'''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)'''

'''2. Create a management network, with DHCP enabled, reachable from OSM (particularly from VCA container)'''

You need to create a management network, with DHCP enabled, and guarantee that this management network is reachable from OSM. The network is used by the VCA (Juju) for configuring the VNFs once they are running. It is recommended to create a provider network, isolated from Openstack. For instance, in order to create a provider network using physical interface em1 and VLAN 500 and with CIDR 10.208.0.0/24, you should run the following commands:
neutron net-create mgmt --provider:network_type=vlan --provider:physical_network=physnet_em1 --provider:segmentation_id=500 --shared
neutron subnet-create --name subnet-mgmt mgmt 10.208.0.0/24 --allocation-pool start=10.208.0.2,end=10.208.0.254

'''3. Create a valid tenant/user'''

You need to create a tenant/user with rights to create/delete flavors. The easiest way is to create a user and assign it the role "admin". Another option is to change the general flavor management policies at file ''/etc/nova/policy.json'' to allow flavor creation per user.

'''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:

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

'''5. Modify default security group or create a new one'''

By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#Add openstack at OSM]] )

=Configure openstack for OSM (EPA)=

Besides the instructions above for any Openstack, you should do extra configuration to configure openstack for running VNFs which use SRIOV interfaces.

'''1. Provide a mechanism to connect the SR-IOV interfaces'''. As they are physical ports connected to an external switch, Neutron will not be able to connect them. You can use a physical switch programmed to interconnect the vlan tags among them (not recommened for security reasons). Another solution is to use a ML2 plugin that programs the external switch.

'''2. Configure the Neutron controller for using SR-IOV ports'''
<p>Edit /etc/neutron/plugins/ml2/ml2_conf.ini with the tag and vlan ranges used by the dataplane network</p>

[ml2_type_vlan]
network_vlan_ranges = physnet_sriov:3000:3100

'''3. Configure the compute nodes for using SR-IOV'''

On each compute node you have to associate the VFs available to each physical network. That is performed by configuring pci_passthrough_whitelist in /etc/nova/nova.conf. So, for example:

pci_passthrough_whitelist = {"vendor_id":"8086", "product_id":"10ed","physical_network":"physnet_sriov"}

=Add openstack at OSM=

There is a parameter called '''--config''' used to suply general guidelines both at datacenter creation and datacenter association to openmano tenant (this later precedes)
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}'

The following configuration can be added:

* '''security_groups''': To be used for the deployment
* '''availability_zone''': To be used for the deployment
* '''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
* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (code on BETA)

ADVANCED configuration:

* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of a openstack keypair
* '''dataplane_physical_net''': The configured network_vlan_ranges at neutron for SRIOV networks, e.g. 'physnet_sriov' in the above configuration
* '''use_floating_ip''': (By default false). When true a management interface of a VNFD is automatically asigned a floating_ip -if possible-. The prefered method is to use a provider network

The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:
--config='{use_floating_ip: True, availability_zone: controller}'

Openstack configuration (Release TWO) - Revision history

Garciadeblas at 09:33, 7 September 2017

Mirabal: /* Add openstack to OSM */

Garciadeblas at 07:24, 29 June 2017

Tierno: /* Add openstack to OSM */

Garciadeblas: /* Add openstack to OSM */

Tierno: /* Add openstack to OSM */

Garciadeblas: /* Add openstack at OSM */

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

Garciadeblas at 12:38, 21 April 2017

Garciadeblas: Created page with "__TOC__ =Configure openstack for OSM (basic)= '''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)''' '''2. Create a managem..."

Garciadeblas: Created page with "TOC =Configure openstack for OSM (basic)= '''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)''' '''2. Create a managem..."