github.com/openshift/installer@v1.4.17/docs/user/openstack/connect_nodes_to_manila_network.md (about)

     1  # Connecting worker nodes to a dedicated Manila network
     2  
     3  Depending on your OpenStack platform configuration, it is very likely that Manila uses a dedicated network for its shares. When that is the case, you need to attach your OpenShift compute nodes to this network otherwise pods might fail to mount the shares, as shown in the following example:
     4  
     5  ```txt
     6  Mounting command: mount
     7  Mounting arguments: -t nfs 172.16.32.1:/volumes/_nogroup/891cb5d9-a417-43a5-9d1c-5b160a16e7be /var/lib/kubelet/pods/c36e7573-853a-44f9-99bd-0de630edb3b9/volumes/kubernetes.io~csi/pvc-6b632043-2580-4ada-a634-ae696db4b96c/mount
     8  Output: mount.nfs: Connection timed out
     9  ```
    10  
    11  You will also see this error message on pods, which will be stuck in
    12  `ContainerCreating` state with the following warning:
    13  
    14  ```
    15  Warning  FailedMount  3m46s (x271 over 17h)  kubelet  MountVolume.SetUp failed for volume "<uuid>" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
    16  ```
    17  
    18  > **Note**
    19  > Consult with your OpenStack administrator to know what network ID Manila exposes its shares on.
    20  
    21  To connect your workers at the time of installation you can use [additionalNetworkIDs](https://github.com/openshift/installer/blob/master/docs/user/openstack/customization.md#additional-networks) parameter in the install config and set Manila network ID there:
    22  
    23  Example OpenShift install config:
    24  
    25  ```yaml
    26  ...
    27  compute:
    28  - name: worker
    29    platform:
    30      openstack:
    31        additionalNetworkIDs:
    32        - <manila_network_id>
    33  ...
    34  ```
    35  
    36  As day 2 operation you need to add new network at `networks` section of your machineset's [provider spec](https://github.com/openshift/installer/blob/master/docs/user/openstack/README.md#defining-a-machineset-that-uses-multiple-networks).
    37  After that Cluster API Provider OpenStack will automatically connect your workers to the network.
    38  
    39  Example of OpenStack Machine Spec:
    40  
    41  ```yaml
    42  networks:
    43    ...
    44    - noAllowedAddressPairs: true
    45      uuid: <manila_network_id>
    46    ...
    47  ```
    48  
    49  > **Note**
    50  > The `noAllowedAddressPairs` option ensures we do not configure allowed address
    51  > pairs when creating the port connected to this network. This is often
    52  > prevented by policy and is correct behavior as this network will not be used
    53  > for API access. This is behavior also seen for all networks specified via
    54  > `compute.*.platform.openstack.additionalNetworkIDs` in
    55  > `install-config.yaml`.