Overhaul the charm README.
The section on SSH host lookup caching in particular
received a lot of attention.
Apart from formatting, the Spaces section was deliberately
left untouched as improvements are part of a separate
documentation effort.
Improve the 'cache-known-hosts' option entry in config.yaml.
Change-Id: I14019ad38a9c4976026c607daca9d768c692535c
The appendix in the deploy-guide has recently been
refreshed. This is the seventh of the nine charms that
support overrides to receive a streamlining in order
to cut down on duplication.
Some driveby formatting improvements.
Added a Bugs section.
Change-Id: I8c7c86a0705b22f73a30475f4a5495d7fb40426f
This patchset implements policy overrides for nova-cloud-controler.
This change includes a charm-helpers sync to bring in the policyd helper
code.
Note there are no functional tests for this feature as the charm still
uses the old style non-zaza amulet framework. The Related-Bug below is
tracking this issue.
Change-Id: Ia5f3f8189d4a7b7b46a827707d964ebe40740aeb
Closes-Bug: #1741723
Related-Bug: #1845639
This change "flips the switch" by changing the default for caching
knownhosts to true. This means that during deployment host lookups are
only performed once for each related unit. This was experimental for
the previous charm release.
Release note is change-id: Ib3d17b4057dd7f671f123b1da7df21c9f3d7e182
Change-Id: I644df508563f93b661af6bfd5fb668f0e31d5e4d
Prior to this, the charm config did not support default quota
configurations for compute (ie. instances, compute, ram, etc.).
Default quota configuration changes will not impact existing
projects with modified quotas. Only new projects and projects with
unmodified quotas will adopt the defaults in the configuration file.
The following default quota settings were added:
instances
cores
ram
metadata_items
injected_files
injected_file_content_bytes
injected_file_path_length
key_pairs
server_groups
server_group_members
The functional test added checks that nova.conf quotas are set in
the correct section of the file.
Change-Id: Iae8c84dbfec97e1879d51963125f7674ea20ba22
Closes-Bug: 1386911
Remove postgresql DB support; This feature is untested as part
of the charms, is not in use and was deprecated as part of
the 1708 charms release.
Change-Id: I866559f519ace3476e0cc85661d99e5f5491227d
Implement DNS high availability. Pass the correct information to
hacluster to register a DNS entry with MAAS 2.0 or greater rather
than using a virtual IP.
Charm-helpers sync to bring in DNS HA helpers
Change-Id: I073770d3900b4948c4cceb440f90407128558c8f
openstack-origin-git currently only supports YAML that specifies
the git repositories to deploy from.
This adds support for default openstack-origin-git values. The
default values supported are: icehouse, kilo, liberty, mitaka,
and master. For example: openstack-origin-git=master
Change-Id: I6b737272deed067c2f71dbd36b201aea884265ee
To ensure that the charm presents the right IP address for
accessing the MySQL database over the shared-db relation,
ensure that any network space binding provided by the user
is preferred over the default of 'private-address'.
If network spaces is not supported (juju < 2.0), fallback to
using 'private-address'.
Change-Id: If91dd8e9a4f47c5455095532ed27433eaf0d47d4
Neutron functionality was deprecated last release; remove
direct support for managing the neutron-server process and
associated plugin support from this charm.
All neutron-server support is now provided by the neutron-api
charm.
Change-Id: Iec7bd5ec6d835b573a15f8163fa5f78842bd672b
Juju 2.0 provides support for network spaces, allowing
charm authors to support direct binding of relations and
extra-bindings onto underlying network spaces.
Resync charm-helpers to pickup support in API endpoint
resolution code and add API extra-bindings to the charm
metadata.
Change-Id: Ib9820251c6196c76c726a1854052a855ecb6ffbe
Peter Matulis