The OpenContrail deployment in MCP includes the following limitations:
OpenContrail does not support tenant renaming due to architecture limitations.
OpenContrail does not support parallel addition and removal of rules to and from security groups.
By default, one worker of the contrail-api
service is used.
If needed, you can enable multiple workers in your Reclass cluster model,
but this setting requires the keystone_sync_on_demand=false
option
that allows fixing the issue with the synchronization of the information
about the OpenStack projects. Be aware that with such a configuration,
you can start setting network entities in a newly created OpenStack project
only one minute after this project is created.
To set multiple workers with the keystone_sync_on_demand=false
option,
refer to MCP Operations Guide: Set multiple contrail-api
workers.
Fixed in 2019.2.3 In the MCP Build ID 2019.2.0, by default,
one worker of the contrail-api
service is used.
If needed, you can enable multiple workers in your Reclass cluster model,
but this setting requires the keystone_sync_on_demand=false
option
that allows fixing the issue with the synchronization of the information
about the OpenStack projects. Be aware that with such a configuration,
you can start setting network entities in a newly created OpenStack project
only one minute after this project is created.
To set multiple workers with the keystone_sync_on_demand=false
option,
refer to MCP Operations Guide: Set multiple contrail-api
workers.
Starting from the MCP 2019.2.3 update, by default, six workers
of the contrail-api
service are used and you do not need
the keystone_sync_on_demand=false
option to be enabled for multiple
workers. Therefore, the limitation described above is removed.