Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated dataplane operator and databaseUser field #534

Merged
merged 2 commits into from
Jul 19, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs_user/modules/proc_adopting-autoscaling.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ ifeval::["{build}" == "downstream"]
listenerImage: "registry.redhat.io/rhosp-dev-preview/openstack-aodh-listener-rhel9:18.0"
endif::[]
passwordSelectors:
databaseUser: aodh
databaseAccount: aodh
databaseInstance: openstack
memcachedInstance: memcached
EOF
Expand Down
1 change: 0 additions & 1 deletion docs_user/modules/proc_adopting-key-manager-service.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,6 @@ spec:
template:
databaseInstance: openstack
databaseAccount: barbican
databaseUser: barbican
xek marked this conversation as resolved.
Show resolved Hide resolved
rabbitMqClusterName: rabbitmq
secret: osp-secret
simpleCryptoBackendSecret: osp-secret
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

Compute services rolling upgrade cannot be done during adoption,
there is in a lock-step with Compute control plane services, because those are managed independently by data plane ansible and Kubernetes Operators.
Compute service operator and Dataplane Operator ensure upgrading
The Compute service operator and OpenStack Operator ensure upgrading
is done independently of each other, by configuring
`[upgrade_levels]compute=auto` for Compute services. Compute control plane
services apply the change right after custom resource (CR) is patched. Compute data plane services will catch up the same config change with ansible deployment later on.
Expand Down
Loading