Talk:Openstack configuration (Release THREE)

From OSM Public Wiki
Revision as of 09:39, 7 September 2017 by Garciadeblas (talk | contribs)
Jump to: navigation, search

Openstack for EPA: to be considered

1. The compute nodes need to have a whitelist for the interfaces with SRIOV and passthrough enabled, and those interface are associated to a physical network label e.g. “physnet” in the file /etc/nova/nova.conf : pci_passthrough_whitelist=[{"devname": "p3p1", "physical_network": "physnet"}, {"devname": "p3p2", "physical_network": "physnet"}]

2. Update in the controller the file “/etc/neutron/plugins/ml2/ml2_conf.ini” to add “sriovnicswitch” to the mechanism_drivers mechanism_drivers =openvswitch,sriovnicswitch

3. Update in the controller the file “/etc/neutron/plugins/ml2/ml2_conf.ini” to set the vlans (e.g. from 2000 to 3000) to be used for the defined physical network label in the case of SR-IOV interfaces: network_vlan_ranges =physnet:2000:3000

4. Update in the controller the file “/etc/neutron/plugins/ml2/ml2_conf.ini” to allow the supported NIC vendor’s product ID [ml2_sriov] supported_pci_vendor_devs = 8086:10ed

5. Update in the controller the file “/etc/nova/nova.conf” to allow proper scheduling of SR-IOV and Passthorugh devices, by adding the PciPassthroughFilter filter to the list of filters. scheduler_available_filters=nova.scheduler.filters.all_filters scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,CoreFilter, PciPassthroughFilter

Relevant links:


When adding Openstack to OSM, new things need to be considered:

  • How to use availability zones
   --config='{use_floating_ip: True, availability_zone: [zone1, zone2]}'
  • New parameter microversion for Device Role Tagging. Potential text below:

Allows specifiying an specific microversion to be used in nova. In order to allow 'Device Role Tagging' functionality use 'microversion: 2.32'. This functionality was introduced in Newton so it would not work for older vims. 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 an specific microversion.