This section provides reference information about the Neutron network configuration files.
The Oracle Solaris zones OpenStack Nova driver uses the Neutron elastic virtual switch (EVS) core plugin at this time, which is not compatible with the Oracle VM Server for SPARC OpenStack Nova driver. Thus, an existing OpenStack controller environment that manages Oracle Solaris zones is not compatible with the Oracle VM Server for SPARC OpenStack Nova driver at this time.
This section provides reference information about Neutron configuration properties for the OpenStack cloud controller /etc/neutron/neutron.conf configuration file.
The following sample /etc/neutron/neutron.conf configuration file fragment shows the properties for Neutron:
[DEFAULT] core_plugin = ml2 service_plugins = router api_workers = 16 nova_url=http://IP-address:8774/v2 nova_admin_username = nova nova_admin_tenant_name = service nova_admin_password = services-password nova_admin_auth_url = http://IP-address:5000/v2.0 rabbit_host=IP-address [matchmaker_redis] host=IP-address [keystone_authtoken] auth_uri = http://IP-address:5000/v2.0 identity_uri = http://IP-address:35357 admin_tenant_name = service admin_user = neutron admin_password = services-password signing_dir = $state_path/keystone-signing [database] connection = mysql://neutron:services-password@FQDN-controller-hostname/neutron
The following sample /etc/neutron/api-paste.ini file shows the required properties for Neutron:
[filter:authtoken] paste.filter_factory = keystonemiddleware.auth_token:filter_factory admin_tenant_name = service admin_user = neutron admin_password = services-password auth_uri = http://IP-address:5000/v2.0 identity_uri = http://IP-address:35357
You might be able to use the default ml2_conf.ini file as-is. On the cloud controller, ensure that the [ml2] stanza of the ml2_conf.ini includes at least the following lines:
[ml2] type_drivers = flat,vlan tenant_network_types = flat,vlan mechanism_drivers = ldoms [ml2_type_flat] flat_networks = physnet1,physnet2,physnet3,physnet4 [ml2_type_vlan] network_vlan_ranges = physnet1:1:4096,physnet2:1:4096,physnet3:1:4096,physnet4:1:4096
This section provides reference information about ML2 networking configuration properties for the Oracle VM Server for SPARC OpenStack compute node /etc/neutron/plugins/ml2/ml2_conf.ini configuration file.
The following sample /etc/neutron/plugins/ml2/ml2_conf.ini configuration file fragment shows the properties for ML2 networking and the Oracle VM Server for SPARC virtual switch.
[ml2] path_mtu = 1500 physical_network_mtus = physnet1:MTU-value1,physnet2:MTU-value2 [ldomsvsw] physical_vsw_mapping=physnet1:primary-vsw0, physnet2:primary-vsw1 netboot_segments=1 default_vsw=primary-vsw0
The following are the configuration properties for the [ml2] and [ldomsvsw] stanzas of the /etc/neutron/plugins/ml2/ml2_conf.ini file:
default_vsw=primary-vsw0 specifies the default Oracle VM Server for SPARC virtual switch name.
netboot_segments=1,2,5:10,30:50 is a comma-separated list of netboot segments (individual, or ranges) by VLAN ID. These values specify the segments on which you set up a netboot server that the VMs can use to boot from the network. Range values are separated by a colon character (:).
path_mtu=1500 specifies the default MTU value for a physical network device. The default value is 1500.
physical_network_mtus=physnet1:1500,physnet2:9000 maps an ML2 physical network name to its associated MTU. Use commas to separate mappings.
physical_vsw_mapping=physnet1:primary-vsw1,physnet2:primary-vsw2 maps an ML2 physical network name to its associated Oracle VM Server for SPARC virtual network switch name. Use commas to separate mappings.
If you do not map a physical network name to an Oracle VM Server for SPARC OpenStack virtual switch name, the physical network falls back to using the virtual switch that is specified by the default_vsw property. If the default_vsw property is not specified, it falls back to using the default virtual switch, which is primary-vsw0.