Designate

  • By OpenStack Charmers
  • Cloud
Channel Revision Published Runs on
latest/edge 227 25 Mar 2024
Ubuntu 22.04
yoga/stable 244 04 Apr 2024
Ubuntu 22.04 Ubuntu 20.04
zed/stable 243 04 Apr 2024
Ubuntu 22.10 Ubuntu 22.04
xena/stable 208 14 Sep 2023
Ubuntu 20.04
wallaby/stable 202 13 Sep 2023
Ubuntu 20.04
victoria/stable 209 14 Sep 2023
Ubuntu 20.04
ussuri/stable 211 14 Sep 2023
Ubuntu 20.04 Ubuntu 18.04
train/candidate 116 28 Nov 2022
Ubuntu 18.04
train/edge 210 14 Sep 2023
Ubuntu 18.04
stein/candidate 116 28 Nov 2022
Ubuntu 18.04
stein/edge 210 14 Sep 2023
Ubuntu 18.04
rocky/candidate 116 28 Nov 2022
Ubuntu 18.04
rocky/edge 210 14 Sep 2023
Ubuntu 18.04
queens/candidate 116 28 Nov 2022
Ubuntu 18.04
queens/edge 210 14 Sep 2023
Ubuntu 18.04
2024.1/candidate 192 24 Jan 2024
Ubuntu 23.10
2023.2/stable 241 04 Apr 2024
Ubuntu 23.10
2023.1/stable 242 04 Apr 2024
Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04
juju deploy designate --channel yoga/stable
Show information

Platform:

Ubuntu
22.04 20.04

Overview

This charm provides Designate (DNSaaS) for an OpenStack Cloud.

Important: This documentation supports version 3.x of the Juju client. See the OpenStack Charm guide if you are using the 2.9.x client.

Usage

Designate relies on services from the mysql, rabbitmq-server and keystone charms:

juju deploy designate
juju deploy mysql
juju deploy rabbitmq-server
juju deploy keystone
juju deploy memcached
juju integrate designate memcached
juju integrate designate mysql
juju integrate designate rabbitmq-server
juju integrate designate keystone

To add support for DNS record auto-generation when Neutron ports and floating IPs are created the charm needs a relation with neutron-api charm:

juju deploy neutron-api
juju integrate designate neutron-api

The charm needs to store DNS records. This can be achieved by setting the dns-slave config option or by relating to the designate-bind charm:

juju deploy designate-bind
juju integrate designate designate-bind

For Queens and later, the nameservers config value must be set:

juju config designate nameservers="ns1.example.com. ns2.example.com."

Policy Overrides

Policy overrides is an advanced feature that allows an operator to override the default policy of an OpenStack service. The policies that the service supports, the defaults it implements in its code, and the defaults that a charm may include should all be clearly understood before proceeding.

Caution: It is possible to break the system (for tenants and other services) if policies are incorrectly applied to the service.

Policy statements are placed in a YAML file. This file (or files) is then (ZIP) compressed into a single file and used as an application resource. The override is then enabled via a Boolean charm option.

Here are the essential commands (filenames are arbitrary):

zip overrides.zip override-file.yaml
juju attach-resource designate policyd-override=overrides.zip
juju config designate use-policyd-override=true

See appendix Policy Overrides in the OpenStack Charms Deployment Guide for a thorough treatment of this feature.

Bugs

Please report bugs on Launchpad.

For general charm questions refer to the OpenStack Charm Guide.


Help improve this document in the forum (guidelines). Last updated 6 months ago.