Hello Team,

Recently I came across the scenario from one of the customer where they had gone through our document [1] and [2] to create the OpenstackDataPlaneNodeSet CR and integrate with the Ceph Storage.

They end up creating their OpenstackDataPlaneNodeSet CR without some of the important services (redhat, bootstrap, download-cache, ssh-known-hosts, reboot-os, install-certs and neutron-metadata) like the one below,

~~~
 services:
   - configure-network
   - validate-network
   - install-os
   - configure-os
   - run-os
   - ceph-client
   - ovn
   - libvirt
   - nova
   - custom-ceph - telemetry
~~~

Because they used the above CR, they end up doing multiple things manually and leads to several inconsistencies in their cluster.

I would request we should mention about default "services" in our both deployment document [1]  and storage document [2], if not atleast from both the document we should redirect customer to the following document (section 3.3) to avoid such confusions.

https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/customizing_the_red_hat_openstack_services_on_openshift_deployment/index#con_data-plane-services_custom_dataplane 

[1]

Section 5.3

https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_red_hat_openstack_services_on_openshift/index#proc_creating-an-OpenStackDataPlaneNodeSet-CR-with-preprovisioned-nodes_dataplane 

Section 5.4.2

https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_red_hat_openstack_services_on_openshift/index#proc_creating-an-OpenStackDataPlaneNodeSet-CR-with-unprovisioned-nodes_dataplane 

[2]

Section 3.5.4

https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/configuring_persistent_storage/assembly_configuring-red-hat-ceph-storage-as-the-backend-for-rhosp-storage#proc_ceph-configuring-data-plane-to-use-ceph_ceph-back-end