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
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
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
nova-cert was deprecated @ newton, and only supports ec2 services
which we dropped in the charms @ liberty so remove installation
and configuration of this service for >= newton.
Change-Id: I6d0ed6a1e058f38cb5d556a34b6f4299bf6d2055
Since >= liberty the url_for parameter endpoint_type was replaced by
interface d227f6d237
Change-Id: I98ebbf9f2c7582fae5f466dfc1d224bf66e38a24
Closes-Bug: #1698398
Signed-off-by: Jorge Niedbalski <jorge.niedbalski@canonical.com>
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
- fix tests which assumed mocks would just work on os_release()
Change-Id: I48b4853ed343bd3188c16f2bc432b4ca0badc473
Related-Bug: #1659575
This enables network spaces for the memcache relation. Essentially,
the charm tries to use the binding for the memcache, and if that doesn't
work falls back to the private address.
Change-Id: I831c4df22a698709fc0fa42ccea74f10b64a469b
When the percona-cluster charm sets an access-network but the default
unit-get address is not on that network extra shared-db relations get
executed. This is specifically a problem when running upgrades and
trying to avoid API downtime.
The root cause is that the access-network is not checked until the
SharedDBContext is consulted. But then db_joined function will
change it back to the wrong ip on subsequent runs.
This change adds a check for access-network on the relation during the
db_joined function and pushes IP selection off to get_relation_ip.
Charm helpers sync to pull in changes to get_relation_ip.
Partial-bug: #1677647
Change-Id: Ifd4e975d9abbb9f7a8b0f12c8f0a8cf8f78595b6
determine_ports() was not adding the nova-placement-api port to the
ports list because it is run under the apache2 service. This fix
enables determine_ports() to get 'nova-placement-api' from the list
of services rather than 'apache2', allowing it to determine the port
that nova-placement-api uses.
Also enable tests/gate-basic-xenial-ocata in this commit.
Change-Id: I8113e911272ee671026bace9f6e0e8c4ce072e6b
This change installs the nova-placement-api, runs it under
mod_wsgi with apache2, updates nova.conf accordingly, and
registers its endpoints.
Change-Id: I4af4afa591cf68964e6146ca0ca0c51d1ddb8a64
With the release of 4.2.0 of keystonemiddleware using the
in-process token cache is no longer recommended. It is recommended
that a memcache backend to store tokens is used instead,
This installs and configures memcache and configures neutron-server
to use memcache for token caching.
http://docs.openstack.org/releasenotes/keystonemiddleware/mitaka.html#id2
Change-Id: I747d107d28474d545e4a3612a927d46cae34e6b6
- Remove Precise-Icehouse Amulet test definitions if they exist.
- Add Xenial-Newton Amulet test definitions.
- Add Yakkety-Newton Amulet test definitions.
- Use the percona-cluster charm in tests instead of the mysql charm.
Change-Id: Idab48a7831008c5353eeb56da5deb49ce1305a41
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.
Rename amulet tests inline with gate-* and dfs-* naming standards.
Update README to refer to functional testing section of the charm
guide.
Change-Id: Id353b3a1c8a74d8b2bed7fe0490090b5273e228f
All contributors to this charm have agreed to the switch
from GPL v3 to Apache 2.0; switch to Apache-2.0 license
as agreed so we can move forward with official project status.
Change-Id: I20448e0370138e103a00c7fcf0f49949c82d33a9
The keystone_auth section has changed for Mitaka. The Liberty format
,which is currently being used, is incompatible with keystone v3 on
Mitaka as it assumes the id of the default domain is default where
as in Mitaka it is a uuid.
The install documentation for Mitaka dictates that domain name should
be used rather than id when setting project_domain and user_domain
Change-Id: Id79a3dc10f3f08f837e6efdfb446380bb00a5891
Partial-Bug: 1571347
Update api-paste.ini to align with the upstream Mitaka version.
Add nova.conf for Mitaka, dropping all EC2 config options as the
EC2 API was dropped from the nova source tree in Mitaka.
Change-Id: I341d0043d2580db2aa7974537321913dac70c3b7
This change adds a template for liberty or above that works with a keystone
v3 endpoint. It also removes the Mitaka template as it duplicated the liberty
one.
Change-Id: Ic0bd24c8516b541c44dac9c8a92357050e75fcf6
Partial-Bug: 1522397
Adds pause and resume unit to the charm such that the
charm stays paused during maintenance operations.
Change-Id: Ia422aa4077fbdd8cdb0353306c14f5633e2affb8
Partial-Bug: 1558642
Aurelien Lourot