Browse Source

Merge "Fix: various documentation and URL fixes"

Zuul 6 months ago
parent
commit
1d0cdd288a

+ 1
- 1
specs/approved/k8s_update_node_labels_workflow.rst View File

@@ -241,4 +241,4 @@ References
241 241
 
242 242
 .. _Kubernetes: https://kubernetes.io/
243 243
 .. _Kubernetes node labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
244
-.. _Baremetal Nodes: https://airshipit.readthedocs.io/projects/drydock/en/latest/topology.html#host-profiles-and-baremetal-nodes
244
+.. _Baremetal Nodes: https://airship-drydock.readthedocs.io/en/latest/topology.html#host-profiles-and-baremetal-nodes

+ 7
- 7
specs/approved/workflow_node-teardown.rst View File

@@ -258,7 +258,7 @@ Query Parameters:
258 258
 
259 259
 Responses
260 260
 ~~~~~~~~~
261
-All responses will be form of the UCP Status response.
261
+All responses will be form of the Airship Status response.
262 262
 
263 263
 -  Success: Code: 200, reason: Success
264 264
 
@@ -293,7 +293,7 @@ Query Parameters:
293 293
 
294 294
 Responses
295 295
 ~~~~~~~~~
296
-All responses will be form of the UCP Status response.
296
+All responses will be form of the Airship Status response.
297 297
 
298 298
 -  Success: Code: 200, reason: Success
299 299
 
@@ -327,14 +327,14 @@ Query Parameters:
327 327
 
328 328
 Responses
329 329
 ~~~~~~~~~
330
-All responses will be form of the UCP Status response.
330
+All responses will be form of the Airship Status response.
331 331
 
332 332
 -  Success: Code: 200, reason: Success
333 333
 
334 334
    The status of each etcd in the site will be returned in the details section.
335 335
    Valid values for status are: Healthy, Unhealthy
336 336
 
337
-https://github.com/att-comdev/ucp-integration/blob/master/docs/source/api-conventions.rst#status-responses
337
+https://github.com/openstack/airship-in-a-bottle/blob/master/doc/source/api-conventions.rst#status-responses
338 338
 
339 339
 .. code:: json
340 340
 
@@ -395,7 +395,7 @@ label added, and then perform the kubelet teardown.
395 395
 
396 396
 Responses
397 397
 ~~~~~~~~~
398
-All responses will be form of the UCP Status response.
398
+All responses will be form of the Airship Status response.
399 399
 
400 400
 -  Success: Code: 200, reason: Success
401 401
 
@@ -428,7 +428,7 @@ respond with a 409 Conflict response.
428 428
 
429 429
 Responses
430 430
 ~~~~~~~~~
431
-All responses will be form of the UCP Status response.
431
+All responses will be form of the Airship Status response.
432 432
 
433 433
 -  Success: Code: 200, reason: Success
434 434
 
@@ -501,7 +501,7 @@ Enhancements
501 501
 
502 502
    The completion tags should only be applied upon failure if the site action
503 503
    gets past document validation successfully (i.e. gets to the point where it
504
-   can start making changes via the other UCP components)
504
+   can start making changes via the other Airship components)
505 505
 
506 506
    This could result in a single revision having both site-action-success and
507 507
    site-action-failure if a later re-invocation of a site action is successful.

+ 2
- 2
specs/implemented/deployment-grouping-baremetal.rst View File

@@ -50,7 +50,7 @@ update_site workflow (and perhaps other workflows in the future) invokes
50 50
 Drydock to verify the site, prepare the site, prepare the nodes, and deploy the
51 51
 nodes. Each of these steps is described in the `Drydock Orchestrator Readme`_
52 52
 
53
-.. _Drydock Orchestrator Readme: https://git.openstack.org/cgit/openstack/airship-drydock/plain/drydock_provisioner/orchestrator/readme.md
53
+.. _Drydock Orchestrator Readme: https://git.openstack.org/cgit/openstack/airship-drydock/tree/python/drydock_provisioner/orchestrator/readme.md
54 54
 
55 55
 The prepare nodes and deploy nodes steps each involve intensive and potentially
56 56
 time consuming operations on the target nodes, orchestrated by Drydock and
@@ -69,7 +69,7 @@ Some factors that advise this solution:
69 69
 3. Miswiring or configuration of network hardware.
70 70
 4. Incorrect site design causing a mismatch against the hardware.
71 71
 5. Criticality of particular nodes to the realization of the site design.
72
-6. Desired configurability within the framework of the UCP declarative site
72
+6. Desired configurability within the framework of the Airship declarative site
73 73
    design.
74 74
 7. Improved visibility into the current state of node deployment.
75 75
 8. A desire to begin the deployment of nodes before the finish of the

Loading…
Cancel
Save