nova-k8s is an operator to manage the Nova API, Conductor and Scheduler services on a Kubernetes based environment.
nova-k8s is deployed using below command:
juju deploy nova-k8s nova --trust
Now connect the nova operator to existing database, messaging and keystone identity operators:
juju relate mysql:database nova:shared-db
juju relate rabbitmq:amqp nova:amqp
juju relate keystone:identity-service nova:identity-service
This section covers common and/or important configuration options. See file
config.yaml for the full list of options, along with their descriptions and
default values. See the Juju documentation for details
on configuring applications.
This section covers Juju actions supported by the charm.
Actions allow specific operations to be performed on a per-unit basis. To
display action descriptions run juju actions nova. If the charm is not
deployed then see file actions.yaml.
nova-k8s requires the following relations:
shared-db: To connect to MySQL
amqp: To connect to RabbitMQ
identity-service: To register endpoints in Keystone
ingress-internal: To expose service on underlying internal network
ingress-public: To expose service on public network
The charm by default uses following images:
`docker.io/kolla/ubuntu-binary-nova-api:xena`
`docker.io/kolla/ubuntu-binary-nova-scheduler:xena`
`docker.io/kolla/ubuntu-binary-nova-conductor:xena`
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Please report bugs on Launchpad.