Commit Graph

1229 Commits

Author SHA1 Message Date
Alex Kavanagh 6647baa5e6 Updates for caracal tox.ini
Update the tox.ini file(s) to use the constraints file from
zaza-openstack-tests.

Change-Id: Ifac3b28fd2773e802a83135e7ff32ca4e8befeaf
2024-02-24 20:12:12 +00:00
Alex Kavanagh cc421e9719 Updates for caracal testing support
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: I121370811bec483cb026559cbd4b759d54f10c23
2024-02-12 18:21:03 +00:00
Alex Kavanagh 80dab0abd3 Improve platform mocking
Patch out charmhelpers.osplatform.get_platform() and
charmhelpers.core.host.lsb_release() globally in the unit tests to
insulate the unit tests from the platform that the unit tests are being
run on.

Change-Id: I3dd34ddb38141ec89896b1ce2d9dc6849f4faaa8
2023-10-24 18:36:33 +01:00
Jadon Naas 500a8bd029 Fix typo in actions.yaml
There was a typo in actions.yaml for the resume action that was breaking
builds. This change fixes that typo. The charm will build.

Closes-Bug: 2030677
Change-Id: I8c63674a9d0af597da139abf67ba929d39614311
2023-08-08 20:37:46 -04:00
Corey Bryant dd640651e3 Add 2023.2 Bobcat support
* sync charm-helpers to classic charms
* change openstack-origin/source default to bobcat
* add mantic to metadata series
* align testing with bobcat
* add new bobcat bundles
* add bobcat bundles to tests.yaml
* add bobcat tests to osci.yaml
* update build-on and run-on bases
* drop kinetic
* update charmcraft_channel to 2.x/stable

Change-Id: I449a35e6ba7783e53fd21231dfa4236fbb31b7ef
2023-08-02 14:23:14 -04:00
Jadon Naas 44f6190ee0 Add docs key and point at Discourse
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: I4ab7cd110208816df38c5c70736b69930bcfc086
2023-07-11 16:13:43 -04:00
Zuul 38dabad5c8 Merge "Enable jammy-antelope voting and drop kinetic-zed tests" 2023-04-14 22:58:33 +00:00
Corey Bryant b5193940b2 Fix comparison for Antelope wrap
Use CompareOpenStackReleases to ensure 'antelope' is greater
than 'zed', for example.

Change-Id: I3cf34dbf596c63484ada442c91aa51adab5a7fad
2023-04-13 13:59:46 +00:00
Corey Bryant cf83220246 Enable jammy-antelope voting and drop kinetic-zed tests
* 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: I73f8f0d538701779ad570bc7565982a6b7e4f7af
2023-03-29 21:01:50 +00:00
Corey Bryant a6de5f8d77 Add Antelope support
* sync charm-helpers to classic charms
* change openstack-origin/source default to antelope
* align testing with antelope
* add new antelope bundles
* add antelope bundles to tests.yaml
* add antelope tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases

Change-Id: Id93b0ee0999c7a23ef34e68646b03d910816c655
2023-03-07 20:30:33 +00:00
Liam Young 35896561c7 Fix charm for tox4 compatibility
Related-Bug: 2002788
Change-Id: I6ca5d9177be028ca24e84f455821560923fcad54
2023-01-16 14:28:16 +00:00
Felipe Reyes fabaa8aa22 Drop python-six
This charm doesn't need to support python 2.x anymore, and python-six
was dropped from the Ubuntu Archive on Kinetic (22.10)

Change-Id: Ibd7d373305b608ff0349986d17ecba7f9dfaeb3c
Closes-Bug: #1995285
2022-10-31 15:47:44 +01:00
Felipe Reyes f41c45ead5 Drop 'source' from mysql-innodb-cluster and rabbitmq-server
Change-Id: Ib468fb79ec5e00102a1a9fc43ab66078e37c1593
2022-10-31 15:46:58 +01:00
Alex Kavanagh 9e71e6f732 Ensure that kinetic/22.10 is enabled
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml

Change-Id: I23408279d74aa33ba384e9bdff264248b1dad2ca
2022-08-31 20:23:07 +01:00
Corey Bryant 2604499010 Add Kinetic and Zed support
* 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: Ida68ffdab34c3136f3acf98629e4be6fda3bcea2
2022-08-26 18:40:40 +00:00
Alex Kavanagh c1bfec91b9 Add *.charm to gitignore
This patch adds *.charm to the .gitignore to ensure that any built
artifacts are ignored.

Change-Id: Iaa75568a5d928f62839e130416357caebfcf0747
2022-04-18 21:08:58 +01:00
Alex Kavanagh 08c823a9b4 Updates to enable jammy and finalise charmcraft builds
- 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
- charmhelpers sync

func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/747
Change-Id: I8bd5e6f5d002fbd1118f2c7fa54e50f1b31fc722
2022-04-11 20:28:05 -07:00
Zuul d373c46450 Merge "Update to classic charms to build using charmcraft in CI" 2022-02-22 09:40:42 +00:00
Alex Kavanagh 57a20ffb22 Update to classic charms to build using charmcraft in CI
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: Iee7fb24e06d23b3fbf35f05e7931dbdc25b37d64
2022-02-22 05:13:41 +00:00
Zuul f970260fb3 Merge "Add ovs-record-hostname to deferable service list" 2022-02-21 21:17:36 +00:00
Alex Kavanagh 46e9a675f2 Migrate charm to charmhub latest/edge track
Change-Id: I21152bef3813165a55c7f7d8a716e363c0aab273
2022-01-27 21:49:00 +00:00
Billy Olsen e72659126d Add ovs-record-hostname to deferable service list
The ovs-record-hostname service was introduced in the openvswitch SRU
for bug #1915829, however this service did not make the deferable
services list for the neutron-gateway charm. This causes package
upgrades to restart the openvswitch-switch service. Add the
ovs-record-hostname to the deferable services list in order to prevent
unintended restarts of openvswitch-switch.

Closes-Bug: #1955498
Change-Id: I24a32f6f5a5c51b8b8ee62f88a973a126106fcd9
2022-01-19 04:59:35 -07:00
Corey Bryant cdc744ee21 Re-enable gate voting
The yaml.safe_load() fix has landed in zaza-openstack-tests:
https://github.com/openstack-charmers/zaza-openstack-tests/pull/669

Closes-Bug: #1951650
Change-Id: Ibcee29b6644f3b92213b97705b8afdbdb15603b9
2021-11-22 09:33:09 -05:00
Corey Bryant 3b3c0ee32b Add yoga bundles and release-tool syncs
* 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: Id4a36b0f41d2644a94d266ca1990a270e4e7452f
2021-11-19 16:32:05 -05:00
Zuul d066f337bc Merge "Fix link formatting in README" 2021-10-05 23:42:12 +00:00
Alex Kavanagh 7228648506 Add xena bundles
- add non-voting focal-xena bundle
- add non-voting impish-xena bundle
- charm-helpers sync for new charm-helpers changes
- update tox/pip.sh to ensure setuptools<50.0.0
- disabled hirsute-wallaby due to
  https://bugs.launchpad.net/charm-neutron-gateway/+bug/1945746

Change-Id: I09f111993addbdaa87a1cd695dfebe78844ccd17
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
2021-10-01 12:20:31 +01:00
Liam Young 0f4c7e7aee Increase nova-cloud-controller RAM in func tests
Recent test run(s) have shown memory exhaustion on the nova
cloud controller units. This exhibits itself as the controller
dropping messages from the compute nodes and logging messages like:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 268, in _perform_action_on_threads
  File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 342, in <lambda>
    lambda x: x.wait(),
  File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 61, in wait
    return self.thread.wait()
  File "/usr/lib/python3/dist-packages/eventlet/greenthread.py", line 180, in wait
    return self._exit_event.wait()
  File "/usr/lib/python3/dist-packages/eventlet/event.py", line 125, in wait
    result = hub.switch()
  File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 298, in switch
    return self.greenlet.switch()
  File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 350, in run
    self.wait(sleep_time)
  File "/usr/lib/python3/dist-packages/eventlet/hubs/poll.py", line 80, in wait
    presult = self.do_poll(seconds)
  File "/usr/lib/python3/dist-packages/eventlet/hubs/epolls.py", line 31, in do_poll
    return self.poll.poll(seconds)
MemoryError

to the nova-conductor log.

It seems very likely this issue is specific to Bionic Stein so it
may be a little wasteful to have increased the memory allocation
for all the bundles but I think consistancy between the bundles is
more important.

Change-Id: I2d45acadcd221786513c49256f087114a985e74f
2021-09-23 09:33:56 +00:00
Liam Young 115c34fadd Add AppArmor Rule for keepalived
A patch was introduced [0] "..which sets the backup gateway
device link down by default. When the VRRP sets the master state in
one host, the L3 agent state change procedure will
do link up action for the gate$way device.".

This change causes an issue when using keepalived 2.X (focal+) which
is fixed by patch [1] which adds a new 'no_track' option to all VIPs
and routes in keepalived's config file.

Patch [1] which fixed keepalived 2.X broke keepalived 1.X (<focal).
So patch [2] was added which adds a keepalived_use_no_track config
option which is set to True control whether the 'no_track' option
is added to the keepalived config.

Finally, patchset [3] introduces automatic detection of the
keepalived version by adding a call to `keepalived --version`
but this is denied by the packages apparmor rules.

[0] https://review.opendev.org/c/openstack/neutron/+/707406
[1] https://review.opendev.org/c/openstack/neutron/+/721799
[2] https://review.opendev.org/c/openstack/neutron/+/745641
[3] https://review.opendev.org/c/openstack/neutron/+/757620

Change-Id: I3eb1ef3fe29a8c4e5e26953844f303c8e985248a
2021-09-22 11:30:52 +00:00
Zuul e694359032 Merge "Add extension fwaas_v2 based on neutron-api relation data" 2021-09-13 12:23:36 +00:00
Zuul c7566f4e47 Merge "Actions that expose various neutron resources" 2021-09-13 10:00:23 +00:00
Edin Sarajlic c6f970673b Actions that expose various neutron resources
New actions:
  * show-routers
  * show-dhcp-networks
  * show-loadbalancers

Partial-Bug: #1916231
Closes-Bug: #1917401
Closes-Bug: #1917403
Closes-Bug: #1917405

Change-Id: Ie59c2a7d5c1ee9c51a0f7db4e8f38229812ac84a
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/611
2021-09-12 17:47:38 +02:00
Hemanth Nakkina de22d6cbe2 Add extension fwaas_v2 based on neutron-api relation data
fwaas_v2 extension is added in l3_agent.ini by default from stein.
However with the newly introduced neutron-api configuration parameter
enable-fwaas, the extension have to added only when it is set to true
on neutron-api charm.

neutron-api charm adds enabled-fwaas as relation data in the commit
https://review.opendev.org/c/openstack/charm-neutron-api/+/806676.
This patch removes special handling of fwaas_v2 as l3_extension_plugins
is already updated in relation data based on neutron-api enable-fwaas
configuration.

Remove python3-neutron-fwaas in package list from stein release. The
package is already part of dependency of neutron-l3-agent until Ussuri
release and the dependency will be removed from Victoria release in
package control files.

Synced charmhelpers to get related changes
https://github.com/juju/charm-helpers/pull/635

Partial-Bug: #1934129
Change-Id: I07db7fb7c2f00eaf4c0a5bcc082c73922b87d1c0
2021-09-12 06:53:34 +05:30
Peter Matulis 4702dc7588 Fix link formatting in README
The examples had headers that got turned into links
in the rendered HTML. This PR should fix that.

Change-Id: Id5515da9872d56308975ec197ca13f5dffe2d18a
2021-09-10 13:20:27 -04:00
Peter Matulis 19591c7727 Review README
* Apply README template

* Improve and correct wording

* Improve organisation/formatting

Change-Id: I93b5ef6384265c99480b87e3352761e9539f0935
2021-09-08 12:06:00 -04:00
Zuul 443ffbde88 Merge "Replace reference to 'juju set' with 'juju config'." 2021-08-17 05:36:50 +00:00
Zuul 655860f3c3 Merge "Make fw driver configurable" 2021-08-16 23:01:11 +00:00
James Troup db7c249581 Replace reference to 'juju set' with 'juju config'.
Change-Id: I220748339160984ce9b271c0ca9b7789acacba86
2021-08-06 17:58:16 +01:00
Aurelien Lourot 6a22df54a7 Sync release-tools
In order to fix ResolutionImpossible on tox invocation.

https://github.com/openstack-charmers/release-tools/issues/151
https://github.com/openstack-charmers/release-tools/pull/152

Change-Id: Ia525250e139ea0fd86cc0f19919a7739eda1cb09
2021-07-22 14:58:21 +02:00
Edward Hope-Morley 3de85d46c1 Make fw driver configurable
The neutron-gateway uses the firewall driver just as other nodes
do when running neutron-openvswitch-agent. It is currently
hardcoded to the deprecated iptables_hybrid driver. This patch
allows the driver to be changed to openvswitch same as with the
neutron-openvswitch driver with a firewall-driver config option
that defaults to iptables_hybrid so as to maintain backwards
compatibility.

Change-Id: I4f5482425c91b5ad556c384abba7c27137c1948f
2021-07-20 14:55:28 +01:00
Aurelien Lourot d29d295c32 Add impish to metadata.yaml
Change-Id: I9c3deef7a7cbc1085e72c2b7a25b32c964df6d5c
2021-07-05 12:41:18 +00:00
Aurelien Lourot 1cc3eba140 Fix Zaza deployment expectations
Fix Zaza's expected application status after
https://github.com/openstack-charmers/zaza/pull/451

Change-Id: I1a6f1316817a444d9cb82a4bc7e57d832a921eae
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/598
2021-07-05 11:43:48 +02:00
Zuul 77aa4b6326 Merge "Mention deferred service events in README" 2021-06-28 21:40:16 +00:00
Liam Young 10707801e6 Remove deferred-restart config for lbaasv2
When uninstalling the neutron lbaasv2 package remove the policyrcd
configuration for the service first. This allows dpkg to stop
the service.

Change-Id: Ib0ae0c2c66324edf018ba2fbd10ab4f27ef7f16a
Closes-Bug: 1931655
2021-06-15 14:55:41 +00:00
Zuul 3bcfa64aef Merge "c-h sync - restore proxy env vars for add-apt-repository" 2021-06-15 03:05:13 +00:00
Peter Matulis 80d390961d Mention deferred service events in README
This is a boilerplate section that will eventually
be added to the README for every charm that supports
the deferred restart feature.

Change-Id: I1226ee0039cca11dd8c341e0f511de125ae8c633
2021-06-14 12:39:44 -04:00
Zuul 2e816efe01 Merge "Disable vrrp healthchecks by default" 2021-06-11 21:42:06 +00:00
Zuul aff94fe2ed Merge "setup.cfg: Replace dashes with underscores" 2021-06-11 14:06:50 +00:00
Corey Bryant 0f7a2418cb c-h sync - restore proxy env vars for add-apt-repository
Change-Id: Ie18e3958c90a19a8a1f5ce4cd01aac3f204965aa
2021-05-13 08:47:01 -04:00
Alex Kavanagh 3394e71780 Test bundles for focal-wallaby and hirsute-wallaby
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: I26d558bc7f1847459a1d510c887a3128637a10ce
2021-05-06 10:26:31 +00:00
YuehuiLei 6ed2664d6c setup.cfg: Replace dashes with underscores
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I76232b791b7b4c64e903696dd2903d9196af5eb4
2021-05-04 15:45:24 +08:00