You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs_user/modules/proc_configuring-networking-for-control-plane-services.adoc
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,19 +53,19 @@ spec:
53
53
"ipam": {
54
54
"type": "whereabouts",
55
55
"range": "172.17.0.0/24",
56
-
"range_start": "172.17.0.20", <1>
57
-
"range_end": "172.17.0.50", <2>
58
-
"exclude": [ <3>
56
+
"range_start": "172.17.0.20",
57
+
"range_end": "172.17.0.50",
58
+
"exclude": [
59
59
"172.17.0.24/32",
60
60
"172.17.0.44/31"
61
61
]
62
62
}
63
63
}
64
64
----
65
65
+
66
-
<1> Defines the start of the IP range.
67
-
<2> Defines the end of the IP range.
68
-
<3> Excludes part of the IP range. This example excludes IP addresses `172.17.0.24/32` and `172.17.0.44/31` from the allocation pool.
66
+
* `spec.config.ipam.range_start` defines the start of the IP range.
67
+
* `spec.config.ipam.range_end` defines the end of the IP range.
68
+
* `spec.config.ipam.exclude` excludes part of the IP range. This example excludes IP addresses `172.17.0.24/32` and `172.17.0.44/31` from the allocation pool.
69
69
70
70
. If your {OpenStackShort} services require load balancer IP addresses, define the pools for these services in an `IPAddressPool` CR. For example:
<1> Select an existing `<storage_class>` in your {OpenShiftShort} cluster.
330
-
<2> Replace `<loadBalancer_IP>` with the LoadBalancer IP address.
331
-
<3> This example provides the required infrastructure database and messaging services for 3 Compute cells named `cell1`, `cell2`, and `cell3`. Adjust the values for fields such as `replicas`, `storage`, or `storageRequest`, for each Compute cell as needed.
332
-
<4> If you enabled TLS-e in your {OpenStackShort} environment, in the `spec:tls` section set `tls` to the following:
329
+
where:
330
+
331
+
<storage_class>::
332
+
Specifies an existing storage class in your {OpenShiftShort} cluster.
333
+
334
+
<loadBalancer_IP>::
335
+
Specifies the LoadBalancer IP address. If you use IPv6, change the load balancer IPs to the IPs in your environment, for example:
* `galera.openstack-cell1` provides the required infrastructure database and messaging services for the Compute cells, for example, `cell1`, `cell2`, and `cell3`. Adjust the values for fields such as `replicas`, `storage`, or `storageRequest`, for each Compute cell as needed.
350
+
* `spec.tls` specifies whether TLS-e is enabled. If you enabled TLS-e in your {OpenStackShort} environment, set `tls` to the following:
333
351
+
334
352
----
335
353
spec:
@@ -351,22 +369,6 @@ spec:
351
369
customIssuer: rootca-internal
352
370
enabled: true
353
371
----
354
-
+
355
-
[NOTE]
356
-
====
357
-
If you use IPv6, change the load balancer IPs to the IPs in your environment, for example:
<1> Select an existing `<storage_class>` in your {OpenShiftShort} cluster.
571
-
<2> Replace `<address_pool>` with the name of your network definition.
572
-
<3> Replace `<loadBalancer_IP>` with the LoadBalancer IP address.
573
-
<4> This example provides the required infrastructure database and messaging services for 3 Compute cells named `cell1`, `cell2`, and `cell3`. Adjust the values for fields such as `replicas`, `storage`, or `storageRequest`, for each Compute cell as needed.
574
-
<5> Replace `<networkAttachment_name>` with the name of your network.
575
-
<6> If you enabled TLS-e in your {OpenStackShort} environment, in the `spec:tls` section set `tls` to the following:
572
+
where:
573
+
574
+
<storage_class>::
575
+
Specifies an existing storage class in your {OpenShiftShort} cluster.
576
+
577
+
<address_pool>::
578
+
Specifies name of your network definition.
579
+
580
+
<loadBalancer_IP>::
581
+
Specifies the LoadBalancer IP address. If you use IPv6, change the load balancer IPs to the IPs in your environment, for example:
* `galera.openstack-cell1` provides the required infrastructure database and messaging services for the Compute cells, for example, `cell1`, `cell2`, and `cell3`. Adjust the values for fields such as `replicas`, `storage`, or `storageRequest`, for each Compute cell as needed.
599
+
* `spec.tls` specifies whether TLS-e is enabled. If you enabled TLS-e in your {OpenStackShort} environment, set `tls` to the following:
576
600
+
577
601
----
578
602
spec:
@@ -594,22 +618,6 @@ spec:
594
618
customIssuer: rootca-internal
595
619
enabled: true
596
620
----
597
-
598
-
[NOTE]
599
-
====
600
-
If you use IPv6, change the load balancer IPs to the IPs in your environment, for example:
<1> If you use IPv6, change the load balancer IP to the load balancer IP in your environment, for example, `metallb.universe.tf/loadBalancerIPs: fd00:bbbb::80`.
116
-
<2> Ensure that the names of the back ends (`share_backend_name`) are the same as they were in {OpenStackShort} {rhos_prev_ver}.
117
-
<3> Ensure that you specify the appropriate storage management network in the `networkAttachments` section. For example, the `manilaShares` instance with the CephFS back-end driver is connected to the `storage` network.
118
-
<4> If you need to add extra files to any of the services, you can use `extraMounts`. For example, when using {Ceph}, you can add the {rhos_component_storage_file} Ceph user's keyring file as well as the `ceph.conf` configuration file.
115
+
* `metallb.universe.tf/loadBalancerIPs:<172.17.0.80>` specifies the load balancer IP in your environment. If you use IPv6, change the load balancer IP to the load balancer IP in your environment, for example, `metallb.universe.tf/loadBalancerIPs: fd00:bbbb::80`.
116
+
* `share_backend_name` specifies the names of the back ends to use in {rhos_long}. Ensure that the names of the back ends are the same as they were in {OpenStackShort} {rhos_prev_ver}.
117
+
* `networkAttachments` specifies the appropriate storage management network. For example, the `manilaShares` instance with the CephFS back-end driver is connected to the `storage` network.
118
+
* `extraMounts` specifies additional files to add to any of the services. For example, when using {Ceph}, you can add the {rhos_component_storage_file} Ceph user's keyring file as well as the `ceph.conf` configuration file.
119
119
+
120
120
The following example patch file uses CephFS through NFS:
<1> If you use IPv6, change the load balancer IP to the load balancer IP in your environment, for example, `metallb.universe.tf/loadBalancerIPs: fd00:bbbb::80`.
103
+
where:
104
+
105
+
<loadBalancer_IP>::
106
+
Specifies the load balancer IP in your environment. If you use IPv6, change the load balancer IP to the load balancer IP in your environment, for example, `metallb.universe.tf/loadBalancerIPs: fd00:bbbb::80`.
104
107
105
108
. Wait for the {bare_metal} control plane services CRs to become ready:
0 commit comments