* Update charm-neutron-api from branch 'master'
to b86c056961882153ece88938d648f449e04e4e62
- Updates for caracal tox.ini
Update the tox.ini file(s) to use the constraints file from
zaza-openstack-tests.
Change-Id: Ib5d0b909970754dac7ea1b274fdf72fc9b257455
* Update charm-neutron-api from branch 'master'
to a89394045098a0f0ea4de83d63d772e63a6c3cec
- 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: I6ac828e0784ae4466a6e5cbc85acd666c9c2f75c
* Update charm-neutron-api from branch 'master'
to 94cedb68404a94eed2b051e91fde6307eedf3654
- 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: I2cc91999ccad52c8e42797a3d5ffbf65f9cb36d2
* Update charm-neutron-api from branch 'master'
to a6c5567354175755762ec9a3e20fc628a06fcd43
- Drop hyperv mechanism driver and package
The networking-hyperv project is no longer maintained and
has been removed from Ubuntu in Mantic.
Closes-Bug: #2036953
Change-Id: Ib8e861377c9f691f31de0f707823dbf8ac0fde52
* Update charm-neutron-api from branch 'master'
to 7a0925af7b58df1bee987df0e8c9faa171934986
- Ensure get_requests_for_local_unit doesn't fail on incomplete relation
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: Ia03446f08c38057985f895fed2a5cdd78004aec8
* Update charm-neutron-api from branch 'master'
to d90b45c295f94ff0f7494d1c8e9bd3846742d650
- 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: I8050b03c9e4a1f801a60de516000467860a1a47a
* Update charm-neutron-api from branch 'master'
to 3141e839a150dd440c0655e2d69ee41f2635453f
- 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: Idb7ec6357e2ef7449cc77bff48d12102da72d822
* Update charm-neutron-api from branch 'master'
to f40243035356757e68700baf7ca5c945e48a44e9
- 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: I78b2e454009869b79cb27cfc15712a6b8ef8e286
* Update charm-neutron-api from branch 'master'
to 4dd4294a0f61e2e82590161b66a39f1fe4c9fe63
- Merge "Add support for HAProxy L7 checks"
- Add support for HAProxy L7 checks
This change add several configuration options to enable HTTP checks
to the HAProxy configuration, instead of the default TCP connection
checks (which continue to be the default). It also enables /healthcheck
endpoint for neutron-api.
Closes-Bug: #1880610
Change-Id: Ia820d8c2ca709d6b358b1c80d770624568d9a85b
* Update charm-neutron-api from branch 'master'
to 8e708a76b72fa66234f0ef7fd722ae315eae1b12
- Ensure openstack-release package is correct after install hook
The linked bug shows the install of the charm with openstack-origin set
to zed. This happens because configure_installation_source() causes the
openstack-release package to be installed *before* the zed cloud archive
sources are configured into /etc/apt and an apt update done. This means
that the openstack-release package says "yoga" despite the zed packages
actually being installed.
Then, on the config-changed hook, it sees that the installed version is
showing as yoga and tries to do an upgrade. This fails, as the charm
hasn't yet bootstrapped, and the charm tries to bootstrap after
upgrading the packages.
There's a few bugs here which are exposed, but the tactical fix is to
force the openstack-release to match the installed packages.
Closes-Bug: #1989538
Change-Id: Icaa2303d2dbbcfc883ea1cd44ce0a77af1ef7250
* Update charm-neutron-api from branch 'master'
to 1fa45762326093cdbae969ae25bffd77799eb696
- Update key for reverse DNS lookup in README
The configuration key is renamed some time ago
https://charmhub.io/neutron-api/configure?channel=edge#reverse-dns-lookup
Updating README.md to have it consistent.
Change-Id: I0c2bce037144d441b61c0d5549611dc3dd7e4b3e
* Update charm-neutron-api from branch 'master'
to fd47d723a94c99ab7c4e37080c875e3b389ba0bc
- 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: I84b915dd3b6896984fab40cdc93a5f0da9040491
* Update charm-neutron-api from branch 'master'
to e9f077c28bbc8bcb7b4768bac5cb923a5481818d
- 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: I5b04cd5a9d1dd8d62b129592bf8ae1339e9af58b
* Update charm-neutron-api from branch 'master'
to 88c3c9d5a43aef59ec0be8d667e3abb21df3e6d2
- 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
Change-Id: I9e03f8032c4e66586feec2bbf5f07e93b89355cc
* Update charm-neutron-api from branch 'master'
to c435106722372ef6e46f5174d4d49e50026cfa34
- Merge "Remove the charm artifact from the repository"
- Remove the charm artifact from the repository
Change-Id: I9cdbd0433f9723b0af96668f24ce2e4c1870f3aa
* Update charm-neutron-api from branch 'master'
to c411b90d2d14e7ad7678e0ce0b81ac82fdaffa3a
- Option to enable network-segment-range support
To let operators add an additional and optional service plugin into the
deployment configuration as "network_segment_range".
https://docs.openstack.org/neutron/latest/admin/config-network-segment-ranges.html
Closes-Bug: #1965229
Change-Id: Id0ac7c397874ad2c51935e8c0eab64f1ef4f6fd3
* Update charm-neutron-api from branch 'master'
to 1c88770e9b6c1b13bbbed4d0e889110c11969e44
- 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: I0febbbf7da990026b9578a3512c99539eb03bbc0
* Update charm-neutron-api from branch 'master'
to 59ce3d96cec1c61fb31b67bb0ba53e02d08e79ad
- Re-enable voting for wallaby tests
The pgrep behavior in test_901_pause_resume has been fixed in
zaza-openstack-tests.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/686
Closes-Bug: #1933338
Change-Id: I6e5a1384939e25f9bec4a019be6788432cea6b34
* Update charm-neutron-api from branch 'master'
to 48cdd1a86cc7a472c309b75dbc083814e5135182
- Use unittest.mock instead of mock
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I25d6d26f2a4169ddc30d8eeac193d768aa345058
* Update charm-neutron-api from branch 'master'
to 1561529e1270a7ec0bf2ec1ff9c0c9f584248953
- Use configure_installation_source instead of add_source
Use the configure_installation_source method from
ch.contrib.openstack.utils instead of add_source since it understands
the various openstack-origin permutations.
Change-Id: I3c0d8392c4b0c68687a36c9455fc7991fda215f1
Closes-Bug: 1928727
* Update charm-neutron-api from branch 'master'
to e18b89a3f0f61e88adbc3e82c90e6f43a1215927
- Fix removing fwaas when upgrading from Ussuri to Victoria
Without this fix, upgrading from Ussuri to Victoria won't
fully remove fwaas everywhere, leading to broken floating
IPs.
Fixes https://github.com/openstack-charmers/charmed-openstack-tester/issues/57
Change-Id: I959e8f8cafc6d4040895762c21f8ad8b6f190a3b
* Update charm-neutron-api from branch 'master'
to 3e387d591869b714be1c323f240fcaff289b3c10
- Adding uplink_status_propagation option
Add charm option uplink-status-propagation, which for releases >= stein
will add the ml2 plugin uplink_status_propagation, that enabled ports to
have the propagate_uplink_status attribute to allow instance VF to see the PF
link state change for SR-IOV ports.
Change-Id: I4f1ace630c74363057b0bbdbc759c482125ad015
Closes-Bug: 1949491
* Update charm-neutron-api from branch 'master'
to 15b3a727866e0e3e164caffe96356a1012478c4f
- 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: I97d4131670ae024b8bc84d5a13b1034e47d39445
* Update charm-neutron-api from branch 'master'
to c7d8ee4c86dd8d1da53f983083e778cf7eebcf37
- add internal endpoints to neutron-plugin-api relation data
The change [1] syncs the charmhelpers that has additional
context data to IdentityServiceContext - internal_host,
internal_port, internal_protocol.
This patch adds the internal_host, internal_port,
internal_protocol to neutron-plugin-api relation data.
Without this patch, any relations over neutron-plugin-api
will be incomplete if the charm holding the other end of
the relation has charmhelpers synced.
[1] https://review.opendev.org/c/openstack/charm-neutron-api/+/806676
Change-Id: Ic4abbd0a408949c0c752a1701db161e1cd5c4ff7
* Update charm-neutron-api from branch 'master'
to 69af89a6158679e87d9b6c2a437268b725fbcd80
- Add enable-fwaas to relation data
Add enable-fwaas to neutron-plugin-api relation data so
that neutron-openvswitch updates neutron-l3-agent
configuration accordingly.
Synced charmhelpers to get related changes
https://github.com/juju/charm-helpers/pull/635
Partial-Bug: #1934129
Change-Id: I5019c5ed3b8ab556d4900f1fe46dee69f5f09ee7
* Update charm-neutron-api from branch 'master'
to 3f0855a8d3d1ff8482f3385fcb9d3e4015b17c51
- Replace reference to 'juju set' with 'juju config'.
Change-Id: Id63e4f21c36299588364eb6de7806c8c753318ef
* Update charm-neutron-api from branch 'master'
to 2e0896c737eb09d6e8a89da02f5e4043d81c9c48
- Fixes disabling fwaas
Commit 00e7c8b added support for disabling fwaas but
forgot to remove the firewall plugin from service_plugins
once the fwaas package has been removed. This patch fixes
that.
Change-Id: I75fdd192144138fa5bf09c278d5507ca8c5366d1
Closes-Bug: #1934129
* Update charm-neutron-api from branch 'master'
to 00e7c8b6ad32108cf0d6f317e281c6090a588240
- Remove neutron-fwaas for >= V
Also adds config option enable-fwaas which defaults to
True to allow disabling fwaas for releases earlier than
Victoria.
Change-Id: Ic9251c5290f777f544a150a92702566474b264b8
Closes-Bug: 1934129
* Update charm-neutron-api from branch 'master'
to 0d4c5e139a127c05e19f33f2a6c46a19014ae607
- Add impish to metadata.yaml
Change-Id: I8baece928d4545c8849c9b69648cb154ad15f052
* Update charm-neutron-api from branch 'master'
to 3415c5e7da2a7130ad00ca759f667b9e75dcd32e
- Merge "setup.cfg: Replace dashes with underscores"
- 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: Ic682234b64c313cc09a6471f30f20dc1a7d49f37
* Update charm-neutron-api from branch 'master'
to 48f87deff37b6bf6a7c6b11059e077e8635294bd
- 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: If5d64191925c5b568c0224c59b0c851e3c8f3e50
* Update charm-neutron-api from branch 'master'
to 5a7dfeac7f1d95ec546896cdda05c51a971d5f5f
- Updates to flip all libraries back to master
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I4c38f3db7c7bcdbb993ffb27b8bf1473f8f0f3a6
* Update charm-neutron-api from branch 'master'
to 9442c0445db005433058e5c8e7e70df0a150748e
- 21.04 sync - add 'hirsute' in UBUNTU_RELEASES
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: I65d1d790f902d928cd0c4dc848121b1c7fd65071
* Update charm-neutron-api from branch 'master'
to ab2d2152b0c8eda8aede7357757d8b506c8db427
- 21.04 libraries freeze for charms on master branch
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: Ice0f02ee3724b1cf9f59efb59ef8b33e1bf54968
* Update charm-neutron-api from branch 'master'
to b65eea58646cb173c5d1dd035fc543056f9cbd90
- Update worker-multiplier config description
Based on the change in charm-helpers:
https://github.com/juju/charm-helpers/pull/553
Related-Bug: #1843011
Change-Id: I36fbd881fd6c805699f51cf9d52181e39ea8d8f2
* Update charm-neutron-api from branch 'master'
to 5bc7a321fd2659bf1ee26cf64d9c91c0369ffc3f
- Add hirsute and remove trusty from metadata.yaml
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I3ccae204adce2a0d0d2b2ef8d937b712bd7816d7
* Update charm-neutron-api from branch 'master'
to 3383832a7b121f3ee6a10fd11346df942019bf8d
- Merge "Add new osci.yaml"
- Add new osci.yaml
This change is preparatory to migration Ubuntu OpenStack CI
from Jenkins to Zuul
Change-Id: I1eb9a89d875539371357681d2b2b0ec7d8b8c3cf
* Update charm-neutron-api from branch 'master'
to d4e4eeb743fe8682b41af2b32cdfda01a8914139
- Hotfix charmhelpers sync for local_address() fix
The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().
Change-Id: I6268134218b6e3e9b96e5c0d25e02a2f473e19b6
* Update charm-neutron-api from branch 'master'
to 1bd71a1bed63cbcda3c0221d5668f8dd9c27ac2b
- Updates for testing period for 20.01 release
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
* Remove mock for unit_get as it's no longer in c-h context module
* Remove sections from subordinate context due to c-h change.
Change-Id: Idd0e4963823ec2ed915795fb04913f11ba305a2e
* Update charm-neutron-api from branch 'master'
to c052de69806de13a599837e32c846c55d863dadd
- Remove Disco and Eoan bits
Change-Id: I69822c14b2047dba17fafbd523fa301dc5eb4fa3
* Update charm-neutron-api from branch 'master'
to a475261db37dae66b57fe009da7e71fbff1b0237
- Add Groovy to the test gate
Change-Id: Id829cb4eeb97327a4657888e4309bcf2c217c8fe
* Update charm-neutron-api from branch 'master'
to 2ac53e951bd28baf36dff18e5c393679e371207f
- Merge "Use AZLeastRoutersScheduler by default"
- Use AZLeastRoutersScheduler by default
Neutron uses an AZ-unaware scheduler (LeastRoutersScheduler) by default
in its configuration and the neutron-api charm does not override it.
AZLeastRoutersScheduler inherits from LeastRoutersScheduler and does the
same, plus respects AZ hints when scheduling HA routers.
For --distributed --ha routers using AZLeastRoutersScheduler means that
snat namespaces will be scheduled with respect to the AZ hints specified
during router creation by an operator.
For --ha but not distributed routers using AZLeastRoutersScheduler means
that qrouter namespaces will be scheduled with respect to the AZ hints.
snat namespaces (--ha & --distributed) and qrouter namespaces (--ha
only) are placed by the scheduler to l3 agents that run in the dvr_snat
mode only so the scheduler change will affect both the deployments with
neutron-gateway units and the ones with neutron-openvswitch running with
use-dvr-snat=True.
Change-Id: I98cd67ff0cf5418a9699acc7aff96c3edb9b2341
Closes-Bug: #1886195
Alex Kavanagh