Tenancy Network Isolation#

Note

Tenants, tenancies, and other features are available if you have paid for multi-tenant support. Contact Penguin Computing to learn more.

Each tenancy within a ICE ClusterWare ™ multi-tenant cluster is virtually isolated from other tenancies within the same super-cluster. No data is passed between tenancies. Network isolation is achieved via partition keys (PKeys) on InfiniBand networks and via VLAN, VXLAN, and virtual network identifiers (VNIs) on Ethernet networks. The ClusterWare software manages the network isolation configuration automatically when a tenancy is created, when tenancy membership changes (nodes are added or removed), and when a tenancy is decommissioned.

Configure Network Isolation#

Before creating your first tenancy, complete all of the steps in Configure Multi-Tenancy Ethernet Network, Configure Multi-Tenant Switches, and Add and Configure Multi-Tenant InfiniBand Network to set up the Ethernet and InfiniBand network configuration to be managed by the ClusterWare software.

Update InfiniBand and Ethernet Switch Configurations#

When nodes are added to or removed from a tenancy, either during tenancy creation or subsequent updates, the InfiniBand and Ethernet switch configurations are automatically updated by the ClusterWare software.

In rare cases, such as a network outage, the configuration changes may not be applied and the ClusterWare software shows an error. In this case, the superadministrator should fix the network issue and manually apply the configuration changes to the InfiniBand network or the Ethernet switches to ensure that network isolation is uninterrupted.

Manually Update InfiniBand Partition Configuration#

Use the cw-clusterctl ibnets tool to compare and update the InfiniBand PKey network configuration.

Compare the ClusterWare configuration (target) to the PKey configuration set in the subnet manager software (current) by running:
```
cw-clusterctl ibnets -i <name> diff
```
Where <name> is the InfiniBand network name.

If there are no differences between the target and current configuration, no further action is required.
If there are differences, apply the target configuration to the subnet manager software to update the PKey configuration:
```
cw-clusterctl ibnets -i <name> apply
```
A success message appears when the target configuration is applied.
[Optional] Compare the configuration again to verify the changes were made:
```
cw-clusterctl ibnets -i <name> diff
```

See cw-clusterctl for additional command options.

Manually Update the Ethernet Switch Configuration#

Use the cw-switchctl tool to compare and update the Ethernet switch configuration.

Compare the ClusterWare configuration (target) to the configuration set on the Ethernet switch (current) by running:
```
cw-switchctl -i <switch> diff --baseline current
```
Where <switch> is the switch name or UID.

If there are no differences between the target and current configuration, no further action is required.
If there are differences, apply the target configuration to the switch:
```
cw-switchctl -i <switch> apply --target
```
A success message appears when the target configuration is applied.
[Optional] Compare the configuration again to verify the changes were made:
```
cw-switchctl -i <switch> diff --baseline current
```

See cw-switchctl for additional command options.