|
|
| (5 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| =Add openstack to OSM=
| |
|
| |
|
| 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-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
| |
| * '''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)
| |
|
| |
| 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 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
| |
| * '''microversion''': 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.
| |
|
| |
| 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}'
| |