Skip to content

Commit df00ef9

Browse files
authored
DC to AZ change - EN-GB
Changed the text to match the AZ naming convention. Screenshots still need to be updated.
1 parent 7d680b6 commit df00ef9

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-gb.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -78,44 +78,44 @@ The `PoP configuration` menu will then appear.
7878

7979
You can also add a second PoP L3 configuration via the second `PoP configuration` menu.
8080

81-
### Step 3: Adding a data centre configuration
81+
### Step 3: Adding an availability zone configuration
8282

8383
#### Configuration
8484

85-
When your PoP configuration is active, click `Add a configuration`{.action} under the `DC configuration` menu. Select a data centre from the drop-down menu and confirm.
85+
When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm.
8686

8787
![add datacentre](images/l2dc1.png){.thumbnail}
8888

8989
![add datacentre](images/l2dc1-1.png){.thumbnail}
9090

91-
The DC configuration will then begin.
91+
The AZ configuration will then begin.
9292

9393
![add datacentre](images/l2dc1-2.png){.thumbnail}
9494

9595
#### Configuration L3
9696

97-
When your PoP configuration has been set, click `Add a configuration`{.action} under the `DC configuration` menu.
97+
When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu.
9898

9999
![add datacentre](images/l3dc0.png){.thumbnail}
100100

101-
Select a data centre from the drop-down menu, then enter the information required.
101+
Select an availability zone from the drop-down menu, then enter the information required.
102102

103103
| Information | Description |
104104
|:-------:|:------:|
105-
| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the DC. This number may be different from the ASN chosen for the PoP |
106-
| A /28 subnetwork | A private subnetwork configured in your vRack in the selected DC. This can be an IPv4 block of size /28 or higher |
105+
| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP |
106+
| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher |
107107

108108
![add datacentre](images/l3dc1.png){.thumbnail}
109109

110-
You can add additional data centre configurations by clicking on the `...`{.action} button, then `Add a configuration`{.action}.
110+
You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button.
111111

112112
![add datacentre](images/l3dc1-1.png){.thumbnail}
113113

114114
You must also add a routing configuration.
115115

116116
##### **Adding a routing configuration**
117117

118-
Click on the `(...)`{.action} button on the desired data centre then on `Add routing configuration`{.action} .
118+
Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action} .
119119

120120
![add routing configuration](images/l3dc2.png){.thumbnail}
121121

@@ -127,8 +127,8 @@ If you choose the type BGP, then enter the required information.
127127

128128
| Information | Description |
129129
|:-------:|:------:|
130-
| Customer ASN | Your AS BGP number, which is configured on your router located in the DC |
131-
| IP Neighbour | IP address of the BGP neighbour of your router in the DC. This address must be part of the subnetwork specified in the `DC Configuration` section |
130+
| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ |
131+
| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section |
132132

133133
![add routing configuration](images/l3dc5.png){.thumbnail}
134134

@@ -141,18 +141,18 @@ If you choose the Static type, enter the required information:
141141

142142
![add routing configuration](images/l3dc4.png){.thumbnail}
143143

144-
You can add multiple routing configurations within the same data centre. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same data centre.
144+
You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone.
145145

146146
![add routing configuration](images/l3dc6.png){.thumbnail}
147147

148148
### Deletion of vCenter resources
149149

150-
Each resource (PoP or DC) can be deleted individually, but deleting a parent resource such as DC or PoP will automatically delete all the subresources.
150+
Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources.
151151

152152
Recursive removal is slower than sequential removal of each resource.
153153

154154
> [!primary]
155-
> If a DC configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the DC resource.
155+
> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource.
156156
>
157157
158158
#### Deleting a routing Configuration
@@ -161,14 +161,14 @@ To delete a routing configuration, click the `...`{.action} button on the routin
161161

162162
![deleting routing configuration](images/deleterouting.png){.thumbnail}
163163

164-
#### Deleting a DC configuration
164+
#### Deleting a AZ configuration
165165

166-
To delete a DC configuration, click the `...`{.action} button on the DC configuration to delete, then click `Delete`{.action}.
166+
To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}.
167167

168168
![DC deletion](images/deletedc.png){.thumbnail}
169169

170170
> [!primary]
171-
> Deleting a DC configuration will delete the related routing configurations.
171+
> Deleting a AZ configuration will delete the related routing configurations.
172172
>
173173
174174
#### Deleting a PoP configuration
@@ -178,7 +178,7 @@ To delete a PoP configuration, click the `...`{.action} button on the PoP config
178178
![deleting PoP configuration](images/deletepop.png){.thumbnail}
179179

180180
> [!primary]
181-
> Deleting a PoP configuration will delete the related DC and routing configurations.
181+
> Deleting a PoP configuration will delete the related AZ and routing configurations.
182182
>
183183
184184
## Go further

0 commit comments

Comments
 (0)