Managing exclusive traffic types

Exclusive traffic types can only be reassigned from one network to another and only one at a time. Reassignment can be performed even if the related services are already deployed. This can be useful, for example, if the initial network configuration is wrong but the storage cluster is already populated with data and running critical services; or after adding a network card, which requires changing network settings, adding a new network, and assigning traffic types to it.

Limitations

Exclusive traffic types cannot be edited or deleted.
You cannot manage access rules for exclusive traffic types.
If the management node high availability is enabled, you cannot reassign the Internal management and Compute API traffic types.

Prerequisites

All of the connected node interfaces are online.
Each network interface has only one IP address.
The number of interfaces on nodes connected to the source and target networks must be the same. Unassigned nodes are also taken into account.
The deployed related services are in the healthy state.
If you have restricted outbound traffic in your cluster, you need to manually add a rule that will allow outbound traffic on TCP and UDP ports 60000–60100, as described in Configuring outbound firewall rules.

To reassign an exclusive traffic type

Admin panel

On the Infrastructure > Networks screen, click Assign to network next to the Exclusive traffic types section, and then select the traffic type you want to reassign.
Reassign the traffic type to another network by selecting the corresponding radio button, and then click Save.
In the Reassign traffic type window, review the source and target networks, and important information about potential risks, and then click Continue to start the traffic type reassignment.
If the related services are already deployed, wait until the connected interfaces are tested and the new configuration is created. Then, click Apply.

While traffic type reassignment is in progress, users cannot perform other tasks in the admin panel. Moreover, the self-service users may not have access to the portal and will need to wait until the reassignment is complete.
If the connectivity checks fail, you can revert to your old network configuration by clicking Revert. Then, you need to fix the found issues and try again.
Wait until the reassignment is complete on all the connected interfaces, and then click Done.
If you reassign the Internal management or VM private traffic type, manually restart all running virtual machines, to be able to access them via VNC console.

Command-line interface

Start the traffic type reassignment by using the following command:

vinfra cluster traffic-type assignment start --traffic-type <traffic-type>
                                             --target-network <target-network>

--traffic-type <traffic-type>: Traffic type name
--target-network <target-network>: Target network ID or name

For example:

# vinfra cluster traffic-type assignment start --traffic-type Storage --target-network Public
+---------------+---------------------------------------------------------------+
| Field         | Value                                                         |
+---------------+---------------------------------------------------------------+
| configuration | target_network: 69ad1db5-512f-4994-ab08-7d643fdb7b39          |
|               | traffic_type: Storage                                         |
| link          | href: /api/v2/network/traffic-type-assignment/285be91b-<...>/ |
|               | method: GET                                                   |
|               | rel: traffic-type-assignment-details                          |
| operation     | traffic-type-assignment                                       |
| progress      | 0.0                                                           |
| state         | preparing                                                     |
| task_id       | 285be91b-77ee-4f8f-a118-8410ab792148                          |
| transitions   | 0                                                             |
+---------------+---------------------------------------------------------------+

View the traffic type reassignment details. For example:

# vinfra cluster traffic-type assignment show
+-------------+---------------------------------------------------------------+
| Field       | Value                                                         |
+-------------+---------------------------------------------------------------+
| link        | href: /api/v2/network/traffic-type-assignment/285be91b-<...>/ |
|             | method: GET                                                   |
|             | rel: traffic-type-assignment-details                          |
| operation   | traffic-type-assignment                                       |
| progress    | 1.0                                                           |
| state       | test-passed                                                   |
| task_id     | 285be91b-77ee-4f8f-a118-8410ab792148                          |
| transitions | 3                                                             |
+-------------+---------------------------------------------------------------+

The output shows that the new network configuration has been tested and can be applied.

Continue the traffic type reassignment and apply the new network configuration. For example:
```
# vinfra cluster traffic-type assignment apply
```
If you reassign the Internal management or VM private traffic type, manually restart all running virtual machines, to be able to access them via VNC console.

If the connectivity checks fail, you need to fix the found issues and try again by running:

# vinfra cluster traffic-type assignment retry

Alternatively, you can revert to your old network configuration with vinfra cluster traffic-type assignment revert, fix the issue, and try again.

To troubleshoot a failed reassignment

Connect to your cluster via SSH.
Investigate /var/log/vstorage-ui-backend/celery.log to find the root cause.
Fix the issue.
Go back to the wizard screen and click Retry.