Openstack configuration (Release ONE): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
Line 13: Line 13:
=Configure openstack for OSM (EPA)=
=Configure openstack for OSM (EPA)=


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.  
'''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:
'''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>
<p>Edit /etc/neutron/plugins/ml2/ml2_conf.ini with the tag and vlan ranges used by the dataplane network</p>


Line 21: Line 21:
   network_vlan_ranges = physnet_sriov:3000:3100
   network_vlan_ranges = physnet_sriov:3000:3100


3 Configure the compute nodes for using SR-IOV
'''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:
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"}  
  pci_passthrough_whitelist = {"vendor_id":"8086", "product_id":"10ed","physical_network":"physnet_sriov"}
 


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

Revision as of 08:35, 7 November 2016

Configure openstack for OSM (basic)

1. Create a valid tenant/user

You need to create a tenant/user with rights to create/delete images and flavors. One option is to use the admin tenant. Another option is to change the flavor/images management policies of your tenant/user at file /etc/nova/policy.json

2. 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

Configure openstack for OSM (EPA)

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

Edit /etc/neutron/plugins/ml2/ml2_conf.ini with the tag and vlan ranges used by the dataplane network

[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='availavolity_zone: one'

The following configuration can be added:

  • security_groups: to be used for the deployment
  • availavolity_zone: to be used for the deployment
  • keypair: to be added in addition to the keypair allocated on the VNF descriptor
  • dataplane_physical_net: The configured network_vlan_ranges at neutron for SRIOV networks, e.g. 'physnet_sriov' in the above configurition