Skip to content

Commit d120b74

Browse files
committed
added links to DCN modules
1 parent d7a37be commit d120b74

2 files changed

Lines changed: 15 additions & 1 deletion

File tree

docs_user/modules/con_adoption-process-overview.adoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,20 @@ endif::[]
2222
.. xref:migrating-ceph-rgw_migrating-ceph-monitoring[Migrate {Ceph} RGW to external RHEL nodes].
2323
.. xref:migrating-ceph-rbd_migrating-ceph-monitoring[Migrate {Ceph} RBD to external RHEL nodes].
2424

25+
Distributed Compute Node (DCN) architecture process::
26+
+
27+
. xref:dcn-adoption-overview_planning[Overview of Distributed Compute Node adoption]
28+
. xref:adopting-spine-leaf-networks_configuring-network[Configuring spine-leaf networks for the {rhos_long_noacro} deployment]
29+
. xref:configuring-control-plane-networking-for-spine-leaf_hsm-integration[Configuring control plane networking for spine-leaf topologies]
30+
. xref:configuring-dcn-data-plane-nodesets_data-plane[Configuring data plane node sets for DCN sites]
31+
+
32+
If you use a DCN architecture with storage, the following additional steps apply, depending on the services that are included in your deployment:
33+
+
34+
.. xref:adopting-image-service-with-dcn-backend_image-service[Adopting the {image_service} with multiple {Ceph} back ends (DCN)]
35+
.. xref:adopting-block-storage-service-with-dcn-backend_hsm-integration[Adopt the {block_storage} service with multiple {Ceph} back ends (DCN)]
36+
.. xref:adopting-compute-services-with-dcn-backend_data-plane[Adopting Compute services with multiple Red Hat Ceph Storage back ends (DCN)]
37+
.. xref:ceph-migration-dcn_migrating-ceph[{Ceph} migration for Distributed Compute Node deployments]
38+
2539
Post-adoption tasks::
2640
+
2741
* Optional: Run tempest to verify that the entire adoption process is working correctly. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud].

docs_user/modules/proc_adopting-compute-services-with-dcn-backend.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
:_mod-docs-content-type: PROCEDURE
22
[id="adopting-compute-services-with-dcn-backend_{context}"]
33

4-
= Adopting {compute_service} services with multiple {Ceph} back ends (DCN)
4+
= Adopting Compute services with multiple {Ceph} back ends (DCN)
55

66
[role="_abstract"]
77
In a Distributed Compute Node (DCN) deployment where {image_service_first_ref} and {block_storage_first_ref} services run on edge Compute nodes, each site has its own {CephCluster} cluster. The {compute_service_first_ref} nodes at each site must be configured with the {Ceph} connection details and {image_service} endpoint for their local site. Because the {image_service} has a separate API endpoint at each site, each site's `OpenStackDataPlaneNodeSet` custom resource (CR) must use a different `OpenStackDataPlaneService` CR that points to the correct {image_service}.

0 commit comments

Comments
 (0)