These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: Ib7947ab8dfd4c4b18c482f4df1a7c6f5b5e3756f
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: I73c3ffa7632bbb2903b9c81d94af7dabae0b19da
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: I506c53b4956024066bc769665525cb022438a0ae
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
Change-Id: I62d95763a6283d8dc7f54b65b0474d48b20608f0
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I59840b672673aa4a8e253659300d9333c1b20a4b
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: I413684a56ec9ad198a68abe367c87c9e6d622617
Ensure that the 'migration' network space binding or the fallback
configuration option is passed to the nova-cloud-controller application
so that the correct IP address is SSH host scanned during setup of
live migration between hypervisors.
Change-Id: I6e20cd0b03f564ee9c110cf58fb0466f6a1f6c82
Closes-Bug: 1874235
This patch adds a focal-ussuri and bionic-ussuri bundles to the tests
for the charm. The linked bug is concerned with installing
nova-network, which is not available on Ussuri.
Closes-Bug: #1872770
Change-Id: Iea5a682aaebeb6f6941cf9d8f5780473f457e455
This commits adds a new extra binding (migration) and
its corresponding fallback configuration flag (libvirt-
migration-network) that allows to specify a space or an
existing CIDR formatted network (if the config flag is pre-
ferred) that will be seleced as the inbound address to be used
as a the live migration target.
For the case of any openstack release >= ocata,
the live_migration_inbound_addr variable will be set
as well as the libvirt_migration_scheme (set to SSH
by default).
For older releases, the behavior remains as before,
as the only remaining option is to setup libvirt
to bind in a insecure tcp connection, so we keep it
as the current live_migration_uri.
The reason of not using an extra-binding exclusively relies
on the back-compability of the change, this needs
to be applied on existing clouds where updating
the bindings on deployed application
isn't possible due to LP: #1796653.
For fresh/new deployments, the migration extra-binding
has been defined and used with precedence over the
libvirt-migration-network variable.
Change-Id: I2f8c0a1e822ad6a90e23cd8009e181b8f86d765a
Closes-Bug: #1680531
Signed-off-by: Jorge Niedbalski <jnr@metaklass.org>
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I54e5552b91ccb668528722bcf11ed5ed41dfa12e
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I0070f15e35080278e39154fec4649180a839ee97
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I20ebd183dc6758337e411574c75048143dadb09a
In a cells deployment the credentials for the nova-compute
application will no longer be available via the
nova-cloud-controller in the local cell. This change adds the
scaffolding for a cell to utilise a new cloud-credentials relation
to allow it to retrieve credentials directly from keystone.
Change-Id: I9d1a7353d730f7cb8e93cc9eea5b788f7c956c3d
Since Icehouse nova-compute does not need to access to a database, all
accesses are made through nova-conductor.
This patch removes shared-db relation and their hook handler.
Change-Id: I7c4f6a70785d7dad1727d52cf86508209849ca35
Closes-Bug: 1713807
Add support for encryption of the underlying block device providing
storage for local instances.
This commit introduces a new juju storage binding and configuration
option to provide a single block device for use for local instance
storage; this block device is formatted and mounted at
/var/lib/nova/instances. In a MAAS deployment, this could be a
bcache fronted device.
The configuration option is preferred over the Juju storage binding
if both are supplied.
This block device can optionally be encrypted using dm-crypt/LUKS
with encryption keys stored in Hashicorp Vault using vaultlocker.
vaultlocker ensures that keys are never persisted to local storage,
providing assurance around security of data at rest in the event
that disks/server are stolen.
Charm support is implemented using a new configuration option 'encrypt'
which when set enforces a mandatory relationship to an instance
of the vault application.
Copy the 'ephemeral-unmount' config option and assocaited code from
the ceph-osd and swift-storage charms to enable testing in cloudy
environments.
Change-Id: I772baa61f45ff430f706ec4864f3018488026148
Deprecated at 18.02, removal for 18.05 release; superceeded by
Neutron Designate Extension driver.
Change-Id: I5bd824027a7bca80176d08f310c4e43a983e6c45
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: I327a686a35edf9b6ff5c1c3cbc4165f8faeef688
Support for the ZeroMQ messaging driver has bit-rotted over the
last few years across the OpenStack charms; drop support for ZMQ
inline with deprecation notices issues in 17.02 charm release.
Change-Id: I66330dd29972e39e45e9bf81cb0570d5749b8312
Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.
Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.
Change-Id: Ie4189fab0c8ce04f60ada98ec94de98f2a79e302
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: Ib07bdddd6e79f73785105ba4844c7aca654231b0
As of Ocata, the ceph key used to access a specific Cinder
Ceph backend must match the name of the key used by cinder,
with an appropriate secret configured for libvirt use with
the cephx key used by the cinder-ceph charm.
Add support for the new ceph-access relation to allow
nova-compute units to communicate with multiple ceph
backends using different cephx keys and user names.
The side effect of this change is that nova-compute will
have a key for use with its own ephemeral backend ceph
access, and a key for each cinder ceph backend configured
in the deployment.
Change-Id: I638473fc46c99a8bfe301f9a0c844de9efd47a2a
Closes-Bug: 1671422
The charm store does not yet recognize this series, and errors
when it exists, thereby preventing push/release of dev charms
into the charm store.
Revisit after the following is resolved:
- https://github.com/juju/charmstore/issues/695
Change-Id: I61025fd4886ac9e33a919b610f11c9ca40a8a2f4
This optimizes the publication process to the charm store, and
ensures that the charm code and version is consistent across all
supported Ubuntu series.
Change-Id: Ie2b60d5f43fa2085f4e9aad0c379bd6a7786e365
Nova has configuration option to specify ephemeral storage - images_type
But right now this charm allows to specify only ceph via relation to ceph.
This changeset adds ability to specify any images_type and add ability
to provide configuration for the ephemeral backend via relation.
Same functionality implemented in cinder charm via storage-backend interface.
Change-Id: Id851e172aed53723d4d8fb6623ff1c4b4a03fefa