66da01ee71
Configure TLS certificates with the right extensions to be used in an mTLS environment. (Used by Libvirt and QEMU for native TLS migration). Ask for new TLS certificate if it's missing the mTLS clientAuth and serverAuth extended key usages. Libvirt/QEMU fail to read CA certificate with chain, therefore it's templated without the chain. Add extra binding `migration`. Add extra configuration key `use-migration-binding`. It's false by default, since on current sunbeam installation, there's no space configuration, all ip addresses are part of the alpha space. Which makes selecting the right ip address impossible. Change-Id: Ia0622b12bcac6b90d7a9937695947c113f62d7fe |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| actions.yaml | ||
| charmcraft.yaml | ||
| config.yaml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| metadata.yaml | ||
| README.md | ||
| requirements.txt | ||
openstack-hypervisor
This charm deploys the openstack-hypervisor snap.
It is expected to be related to the control plane via cross model relations. To achieve this assuming the control plane is in a model called k8s.
juju offer k8s.rabbitmq-k8s:amqp
juju offer k8s.keystone:identity-credentials
juju offer k8s.certificate-authority:certificates
juju offer k8s.ovn-relay:ovsdb-cms-relay
juju relate -m hypervisor openstack-hypervisor admin/k8s.rabbitmq-k8s
juju relate -m hypervisor openstack-hypervisor admin/k8s.keystone
juju relate -m hypervisor openstack-hypervisor admin/k8s.certificate-authority
juju relate -m hypervisor openstack-hypervisor admin/k8s.ovn-relay