This section describes the steps to deploy the Controller Cluster for Write mode.

You can deploy the Controller Cluster for Write mode as follows:

  1. Access OpenStack CLI and list the OpenStack network list. This indicates the configured requisite networks.

    root@openstack-mitaka:/root# openstack network list
    +--------------------------------------+---------------+------------------------------------------------------+
    | id                                   | name          | subnets                                              |
    +--------------------------------------+---------------+------------------------------------------------------+
    | 10a514a3-d843-499d-80fd-28274d4a4912 | webserver-net | 3ebfb2ef-9b47-44f7-9da5-5245e1d0ed53 192.168.10.0/24 |
    | 5dd0b1cb-ebba-4ff9-84fd-74dcf13c7f86 | client-net    | a9a00d61-6ee8-4fac-80df-4e0bb8c8b4f3 192.168.11.0/24 |
    | c1c045f5-2d0f-43e3-ab43-55f990cde9b7 | provider1     | 1b65c0da-38c7-4c85-88a9-30c52c6a4558 10.130.128.0/18 |
    | dd9dab27-9228-4765-96f2-d56194136ba0 | avimgmt       | 5785c1cf-a222-4b0a-9343-003153f37a65 172.16.0.0/24   |
    +--------------------------------------+---------------+------------------------------------------------------+

  2. Create a floating IP, using openstack floating ip create provider1 command, where provider1 is the network used.

    root@openstack-mitaka:/root# openstack floating ip create provider1

  3. The new floating IP is created.

        +---------------------+--------------------------------------+
    | Field               | Value                                |
    +---------------------+--------------------------------------+
    | description         |                                      |
    | fixed_ip_address    |                                      |
    | floating_ip_address | 10.130.170.86                        |
    | floating_network_id | c1c045f5-2d0f-43e3-ab43-55f990cde9b7 |
    | id                  | 4ec57a12-7357-461a-80f6-d87ae7536335 |
    | port_id             |                                      |
    | router_id           |                                      |
    | status              | DOWN                                 |
    | tenant_id           | 904fb201a92f443297bffca3b354d52d     |
    +---------------------+--------------------------------------+

  4. Get the port-id for cluster IP as follows:

    openstack port list -c ID -c 'Fixed IP Addresses'|grep 172.16.0.65
     95665123-64a4-453a-abde-70fdb3d2ae2a| ip_address='172.16.0.65', subnet_id='5785c1cf-a222-4b0a-9343-003153f37a65'

  5. Associate the cluster IP with the floating IP. Using the port-id from the command above (95665123-64a4-453a-abde-70fdb3d2ae2a, in this case), associate it with the floating IP created above (step 2).

    root@openstack-mitaka:/root# openstack floating ip set --port 95665123-64a4-453a-abde-70fdb3d2ae2a 4ec57a12-7357-461a-80f6-d87ae7536335
    +--------------------------+--------------------------------------+
| Field                    | Value                                |
+--------------------------+--------------------------------------+
| description              |                                      |
| fixed_ip_address         | 172.16.0.65                          |
| floating_ip_address      | 10.130.170.86                        |
| floating_network_id      | c1c045f5-2d0f-43e3-ab43-55f990cde9b7 |
| id                       | 4ec57a12-7357-461a-80f6-d87ae7536335 |
| port_id                  | 95665123-64a4-453a-abde-70fdb3d2ae2a |
| router_id                | 2d3b93a2-7804-4841-90c4-be15b148d099 |
| status                   | ACTIVE                               |
| tenant_id                | 904fb201a92f443297bffca3b354d52d     |
+--------------------------+--------------------------------------+

  6. Add the cluster IP and the secondary IP for the cluster leader. For instance, 172.16.0.65 is the cluster IP which is added as the secondary IP for the cluster leader.

    root@172-16-0-66:~# ip a
    eth0: (BROADCAST,MULTICAST,UP,LOWER_UP) mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:bd:5a:0f brd ff:ff:ff:ff:ff:ff
    inet 172.16.0.66/24 brd 172.16.0.255 scope global eth0
    valid_lft forever preferred_lft forever
    inet 172.16.0.65/32 scope global eth0:1 Cluster IP

Restricting the number of Parallel creation of SEs

The parallel SE creation cannot be modified from CLI commands. However, this can be from the below-mentioned file:

/opt/avi/scripts/update_cc_ops_limit.py  --help
usage: update_cc_ops_limit.py [-h] --cloud-name CLOUD_NAME [--show] [--se-creations-limit SE_CREATIONS_LIMIT] [--vnic-ops-limit VNIC_OPS_LIMIT]

optional arguments:
-h, --help                                 show this help message and exit
--cloud-name CLOUD_NAME                    Name of cloud to be updated
--show                                     Show existing limits
--se-creations-limit SE_CREATIONS_LIMIT    Maximum number of concurrent SE creations. The default value of -1 means no limit. A value of 0 means this operation is currently disabled.
--vnic-ops-limit VNIC_OPS_LIMIT            Maximum number of concurrent vNIC (both add and delete) operations. The default value of -1 means no limit. A value of 0 means this operation is currently disabled.

SE Parallel Limit

The following are the steps to configure the OpenStack maximum SE limit:

show existing SE limit

======================
root@10-50-56-243:/opt/avi/scripts# python3 update_cc_ops_limit.py  --cloud-name 'openstack_cloud' --show
Existing max_concurrent_se_creations limit = -1
Existing max_concurrent_vnic_ops limit = -1

set creation limit to 2

======================
root@10-50-56-243:/opt/avi/scripts# python3 update_cc_ops_limit.py  --cloud-name 'openstack_cloud' --se-creations-limit '2'
updating concurrent SE creations limit to 2

show se creation limit

=====================
root@10-50-56-243:/opt/avi/scripts# python3 update_cc_ops_limit.py  --cloud-name 'openstack_cloud' --show
Existing max_concurrent_se_creations limit = 2
Existing max_concurrent_vnic_ops limit = -1