Skip to content

Commit 8e19cea

Browse files
Merge pull request #1056 from klgill/docs-removevariable
removed references to edpm_network_config_update
2 parents 78e1124 + 8ed28fc commit 8e19cea

File tree

2 files changed

+0
-4
lines changed

2 files changed

+0
-4
lines changed

docs_user/modules/proc_configuring-data-plane-nodes.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ Data plane nodes are configured by the OpenStack Operator and your `OpenStackDat
88

99
Your {rhos_long} network configuration should reflect the existing {rhos_prev_long} ({OpenStackShort}) network setup. You must pull the `network_data.yaml` files from each {OpenStackShort} node and reuse them when you define the `OpenStackDataPlaneNodeSet` CRs. The format of the configuration does not change, so you can put network templates under `edpm_network_config_template` variables, either for all nodes or for each node.
1010

11-
To ensure that the latest network configuration is used during the data plane adoption, you should also set `edpm_network_config_update: true` in the `nodeTemplate` field of the `OpenStackDataPlaneNodeSet` CR.
12-
1311
.Procedure
1412

1513
. Configure a `NetConfig` CR with your desired VLAN tags and IPAM configuration. For example:

docs_user/modules/proc_using-new-subnet-ranges.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,5 +141,3 @@ Do not change {OpenStackShort} node IP addresses during the adoption process. Li
141141
----
142142
+
143143
This provides SSH access from the new subnet to the {OpenStackShort} nodes as well as the {OpenStackShort} subnets.
144-
145-
. Set `edpm_network_config_update: true` to enforce the changes that you are applying to the nodes.

0 commit comments

Comments
 (0)