-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
None
-
None
-
2
-
False
-
-
False
-
?
-
None
-
-
-
2
-
Moderate
Adoption of multicell deployments requires creation of a cell specific custom osdp services as they need to provide dataSources for custom configmaps/secrets. Like in this OpenStackDataPlaneService snippet:
---
apiVersion: dataplane.openstack.org/v1beta1
kind: OpenStackDataPlaneService
...
spec:
dataSources:
- secretRef:
name: nova-migration-ssh-key
- secretRef:
name: nova-cell<X>-compute-config
- configReg:
name: nova-extra-config
edpmServiceType: nova
playbook: osp.edpm.nova
tlsCerts:...
During a single-cell adoption testing (also as documented in the guide), the creation of custom services no longer happens. This works for single-cell by a chance(?), but would not for a multiple cells case.
Alternatively, (and ideally) we should only specify "edpmServiceType: nova" for all cells, with no custom osdp services to be created as well. This simple auto-templating for dataSources should be covered in nova-operator and openstack-operator (the dataplane part of it), when it processes the cells templates perhaps.
- blocks
-
OSPRH-6548 As a cloud operator, I want to adopt my existing multi-cell 17.1 nova deployment from TripleO management to the new installer
-
- Closed
-
- clones
-
OSPRH-8651 Secrets are not discovered when deploying dataplane custom services
-
- Closed
-
- relates to
-
OSPRH-8651 Secrets are not discovered when deploying dataplane custom services
-
- Closed
-