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: I6f8bd495a2078b5683a05a63124d7902d0a86f74
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: I367b12d6919747d987f30020575a467f1c473fef
* 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: I8f2c34f3a4a0601ee19aa694b323cc0f9ee65616
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: I7c695c77c67f43f02c72c3b50d949c451be53bc3
The sync_compute_availability_zones test was incorrectly enabled
for bionic queens in commit e0a38a63 . This looks to have been
a simple typo while working on thee tests.yaml. The
sync_compute_availability_zones action is only supported on
stein or greater.
Change-Id: I64df5b4e9742d2a8c17042a7909277c5e9aa46a4
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: I8f7e9ee598a5fc218ccd68f4af36ea323af08bbb
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libraries sync.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: Ia1a6def97294cf3e8435de3d6e8492027c8e761a
This action should be used to sync the Juju availability zones,
from the nova-compute units, with the OpenStack availability zones.
The action is meant to be used post-deployment by the operator.
It will setup OpenStack aggregates for each availability zone, and
add the proper compute hosts to them.
Co-Authored-By: Billy Olsen <billy.olsen@canonical.com>
Change-Id: Ibd71cd61e51b04599eadf21b3ef46e47544b8814
Note that part of this fix belongs in c-h, but let's add it here
as a tactical measure given we are practically frozen.
Enable TLS in the functional test for focal-ussuri and onwards.
Also switch to focal-ussuri as target for smoke.
Drop Trusty/Mitaka as it currently does not pass with symptoms
like https://bugs.launchpad.net/charm-nova-compute/+bug/1861094
Closes-Bug: #1911902
Change-Id: I7b12479ce3afb94a0fb21c26b1ac78736b81aba2
The charm requires a bundle force override for the focal bundle. This
patch adds test bundles for bionic-ussuri and focal-ussuri to the charm.
Change-Id: I6e6cbb30fe7b525a49b7c79181b5aaeb2e129cca
Zuul check openstack-tox-py35 fails with the following error
ERROR: Package 'python-heatclient' requires a different
Python: 3.5.2 not in '>=3.6'
openstack client packages in test-requirements are only
required for func-smoke tests. Also func-smoke tests are
executed on python 2.7 environment. So the fix pins the
exact versions of openstack client packages for python 2.7.
Keystone config parameter admin-token is removed from latest
keystone charm. Remove the param from the bundle generator.
Change-Id: I657e221c43ec9807fb1886089d7068727ffb9ed9
Essentially, Juju 2.7 changed the semantics of "juju run" in a way that
breaks Amulet. Amulet is no longer supported, and this charm will have
its tests migrated to zaza in the near future. This patch just
monkey-patches the file_contents() method of Amulet's Sentry() class so
that the memcache verify test can pass.
Change-Id: I046d9ee5fda4ca15a5824650d8aceb5d24741d94
The placement project has split from nova into its own project
in Train. This patch disables the nova placement API as of Stein
when the placement charm relatation joins, and discontinues
nova placement installation as of Train for new installs.
Change-Id: If7c37ef8936e418b5afd21d83c9322563348cbcf
Needed-By: https://review.opendev.org/#/c/687915/
Partial-Bug: 1811681
The bundle disco-stein was in the dev bundles because
a bug with the Python 3.7 syntax prevented the success of
the deployment of HA clusters. This bug is fixed, we can
reintegrate disco-stein in the gate bundles.
Other small additions:
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
LP Related-Bug: #1823718
Change-Id: Iaeca60d35c3f849fd69f7b3798d3a791c8635bae
When using DVR and L3HA neutron deployment options,
Nova API Metadata requests are served from compute nodes,
instead of from neutron-gateway nodes.
This change allows nova-cloud-controller to send vendor_data
configuration values to nova-compute charm relation so it
can write to nova-compute's nova.conf appropriately.
Replaced the existing context logic with inheritance
from a new context created in charm-helpers, so the
logic can be shared across several charms that write
vendor metadata to nova.conf and vendor_data.json.
Also, small fix in the vendor-data and vendor-data-url
descriptions, where it was incorrectly stating that such
configuration would be effective in nova-cloud-controller
on Queens release.
The values set in vendor-data and vendor-data-url config
options will always be propagated to nova-compute regardless
of the OpenStack release. Those values will continue to only
be effective in nova-cloud-controller nodes on Rocky release
or later.
Included sync of charm-helpers code in order to inherit
the refactored vendor metadata contexts.
Change-Id: If8373fc6b2d04dbc29ed07896d385ac920cae3f4
Depends-On: I0c79e1bfac9fbe7009a7e862ad010cfa2de8cfda
Closes-Bug: #1777714
Drop service check for ``glance-registry``. The service is
removed as of Stein, and it really is not this charm functional
tests job of checking this anyway. Any such detail should
be deferred to the ``charm-glance`` functional tests.
Change-Id: I10ff155730875fbc47f77bb900e30791e9bfdef0
In modern hyper-converged architectures the upstream default of
1.5 does not really fit.
Set to 0.98 to give some headroom on the compute nodes and add
a note about the potential need to adjust this value further.
Change-Id: I64e3379686128dd7f222bdfae133a6c90e8f3ef0
Closes-Bug: #1818234
Due to an issue in python3 oslo_cache+eventlet when using
memcached. As workaroud for Rocky it has been decided to run service
nova-api-os-compute from systemd to apache2.
Closes-Bug: #1812672
Depends-On: https://review.openstack.org/#/c/633218
Depends-On: https://review.openstack.org/#/c/633482
Change-Id: I3bf279638c5decf1020345f3d2e876e379144997
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
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
Allow json lists to be passed in via the pci-alias charm config
option so that multiple aliases can be set.
Increase amulet timeout due to gate failures
Change-Id: I3b5ea70224536f8d40f9c04482fa676c2b230bdd
Partial-Bug: #1735205
Switch package install to Python 3 for OpenStack Rocky or later.
When upgrading, remove any python-* packages that were explicitly
installated and then autoremove --purge any dependencies that are
no longer required.
Change-Id: I87ee4a0a854f88b931093f6245a3a1057bf56c57
Add a service for handling nova metadata api services. This was
previously handled by the neutron-gateway and still is for
deployemnts up to and including Pike, For the neutron metadata
service and the nova service to communicate they need a shared
secret. To achieve this, the change includes:
* A charmhelper sync to get support for multiple wsgi vhosts
* Rendering new wsgi vhost and corresponding haproxy config.
* Setting a shared-secret down the relation with the neutron
gateway.
* Remove fragile keystone authtoken checks as they are failing
after a ch sync and any issues will be caught by the instance
launch functional test.
Change-Id: I5ad15ba782cb87b6fdb3c0941a6482d201670bff
Previously the image virt type was qemu and the compute node virt
type was kvm. This works for deployments prior to rocky but in
rocky this causes the image type filter to return no valid hosts.
An update to charmhelpers has removed the default behaviour of
setting the virt type to 'qemu' by default.
Due to a bug in icehouse updating glance image properties using
the v2 api fails (See Bug #1371559) so for icehouse deploys
get a v1 client.
Change-Id: I20548118092a4480f37c7ab7e9d60e72e299989b
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: Ied8bebd941d9a8b023a070605fba7994e08d15f3
Add an amulet test to check pci-alias setting is propagated
properly into nova.conf. This is a prerequisite for work to support
setting multiple aliases.
Depends-On: I6ac49b0a2782df2ebc8f3d1fe299dec3cc078d7c
Change-Id: Ic8d51dfb3130670cd6810ca80378d6ef8c0d0346
Drop support for deployment from Git repositories, as deprecated
in the 17.02 charm release. This feature is unmaintained and has
no known users.
Change-Id: I2fe15b648d485e5b03965a00dee6324669ebe9fa
Keystone now orders the elements of the username when constructing
a username for multiple services. Update amulet to expect the
new username (only actually affects icehouse).
Change-Id: I6ac49b0a2782df2ebc8f3d1fe299dec3cc078d7c
Closes-Bug: #1739409
Depends-On: I0f857d7c2d5c4abf4843bc3fe1a9848164048fe2
Alex Kavanagh