f218d87642
nova-scheduler errors out if placement service is not available even if the container healthchecks shows active. Add placement integration in nova-k8s to ensure placement is defined in the bundle/tf plan Add ServiceReadinessProviderHandler in placement-k8s and corresponding RequiresHandler in nova-k8s. Fixes: #2097327 Change-Id: Ica072b98c4668c6248702ca680b2885c4d542e23
23 lines
775 B
YAML
23 lines
775 B
YAML
external-libraries:
|
|
- charms.data_platform_libs.v0.data_interfaces
|
|
- charms.rabbitmq_k8s.v0.rabbitmq
|
|
- charms.traefik_k8s.v2.ingress
|
|
- charms.traefik_route_k8s.v0.traefik_route
|
|
- charms.certificate_transfer_interface.v0.certificate_transfer
|
|
- charms.loki_k8s.v1.loki_push_api
|
|
- charms.sunbeam_nova_compute_operator.v0.cloud_compute
|
|
- charms.tempo_k8s.v2.tracing
|
|
- charms.tempo_k8s.v1.charm_tracing
|
|
internal-libraries:
|
|
- charms.keystone_k8s.v1.identity_service
|
|
- charms.sunbeam_libs.v0.service_readiness
|
|
templates:
|
|
- parts/section-database
|
|
- parts/database-connection
|
|
- parts/database-connection-settings
|
|
- parts/section-identity
|
|
- parts/identity-data
|
|
- parts/section-oslo-messaging-rabbit
|
|
- parts/section-service-user
|
|
- ca-bundle.pem.j2
|