4a473da7fe
Currently the heat charm instance runs heat-api and heat-engine services or heat-api-cfn or heat-engine services. Change heat charm to deploy heat-api, heat-api-cfn, heat-engine containers. Change the ingress relation to use traefik-route interface instead of ingress interface so that the traefik configuration for heat-api and heat-api-cfn serive can be written by charm. Add heat-api-cfn pebble container handler and update service endpoints accordingly. Remove heat-config interface and corresponding handlers. Change-Id: I391f8d4ffefcebdb2423fcc1947590ca906d711a
heat-k8s
Description
heat-k8s is an operator to manage the orchestration services heat api, heat api cfn and heat engine on a Kubernetes based environment.
Usage
Deployment
heat-k8s is deployed using below command:
juju deploy heat-k8s heat --trust
Now connect the heat operator to existing database, keystone identity, keystone ops and rabbitmq operators:
juju relate mysql:database heat:database
juju relate keystone:identity-service heat:identity-service
juju relate keystone:identity-ops heat:identity-ops
juju relate rabbitmq:amqp heat:amqp
heat-api-cfn is deployed as separate instance of charm using below command:
juju deploy heat-k8s heat-cfn --trust --config api_service=heat-api-cfn
Configuration
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.
api_service
The api_service option determines whether to act as heat-api service or
heat-api-cfn service. Accepted values are heat-api or heat-api-service
and defaults to heat-api.
Actions
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 heat. If the charm is not
deployed then see file actions.yaml.
Relations
heat-k8s requires the following relations:
database: To connect to MySQL
identity-service: To register endpoints in Keystone
identity-ops: To create heat stack domain and users
ingress-internal: To expose service on underlying internal network
ingress-public: To expose service on public network
amqp: To connect to Rabbitmq
OCI Images
The charm by default uses following images:
ghcr.io/canonical/heat-consolidated:2023.2
Contributing
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Bugs
Please report bugs on Launchpad.