This patch removes the deprecated neutron-lbaasv2-agent service from
NRPE checks after an OpenStack upgrade to an OpenStack version greater
than Stein.
Depends-On: https://github.com/juju/charm-helpers/pull/409
Change-Id: I5f943941328f8a9cd0701e626e4557e243bf37f0
Signed-off-by: Aggelos Kolaitis <akolaitis@admin.grnet.gr>
ovsdb-timeout sets ovsdb_timeout in openvswitch_agent.ini, this option
is used to determine when ovsdb commands should be marked as fail. This
is helpful for large clouds or where the node is under pressure.
Change-Id: I0b0e397691c49d3fcebdd30bbe9b160789acf3c3
Closes-Bug: #1849732
This patch removes completely any lbaas related service when upgrading
to OpenStack Train.
Change-Id: I51a19e4890dfbc4c7cbb61b6d7fdfc7888ff9262
Closes-Bug: #1853868
Signed-off-by: Stamatis Katsaounis <skatsaounis@admin.grnet.gr>
This patch also updates the smoke test to run train.
Change-Id: Ic7ed2a3c12df08dac2a056bb08c5ef87768f8e47
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
* get a list of l3 plugins to enable based on relation data coming from
neutron-api;
* refactor adding fwaasv2 service plugins to the l3 agent to accommodate
the l3_extension_plugins change.
See https://github.com/juju/charm-helpers/pull/370
See LP: #1842353
Change-Id: Ic3a8e302942ed331bc3d80223e123c13d61db3b2
Closes-Bug: #1842353
Also clean up pre-existing pep8 violations in the
files/* dir which was previously not covered by lint testing.
Change-Id: I443a084681d5788c89cdadf2ff999030f4b4d735
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: I268df41f6f775560580b49fa60f717ba8da88def
This patchset removes the load-time mocking necessary due to load-time
function calls in 'constants'. The constants are changed to run-time
functions and and the lazy feature of restart_on_change is used, and the
harden disable for unit testing is switched on when needed.
Change-Id: I73e719ed082a7c8f9c477fd82094532bdbb8029b
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: If39fc59a251290aa34b11180616ed60768537f92
Reverting as this change causes existing qdhcp namespaces to become
inaccessible.
This reverts commit bbc20dbe49.
Change-Id: I91ec8b34bd531e48d00c48512a43921f97b6d9a2
Ensure "rabbit_use_ssl" is specified in the [oslo_messaging_rabbit]
config section instead of "ssl" for Ocata, since "ssl" was not yet
introduced.
Change-Id: I5c3776bf31603e93ba37e9de5a8516d1897f1935
Closes-Bug: #1838696
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that python35-charm-jobs is retained since this charm is supported
on Xenial.
Change-Id: I72638af28accb42482caf43e78d0418f1b722e89
Story: #2005924
Task: #34228
The pre-patch version of unit-testing tested the git-repo version of
charm-helpers instead of the version that was synced to the charm.
The git-repo version of charmhelpers is pip installed to obtain the
testing part of charm-helpers, for the unit tests. Whilst this is a bug
(really), it was compounded in that - due to how the paths worked - the
unit tests' git version of charm-helpers was in the path first, and thus
all unit tests were performed using that version of charm-helpers, and
not the version actually synced into the charm. This has led to all
sorts of 'odd' double mocking of config in the tests as there are
potentially two copies of charm-helpers (as was the case for py27). A
further commit will undo that madness.
This patchset moves the charm synced version of charm-helpers earlier
into the path so it gets picked first when the modules are loaded.
Change-Id: Iff0566c52a283ff0cd2fc7707d981d8c47f3e6b2
Enable support for configuration of FWaaS v2 firewall group
logging.
Configuration options mirror those for neutron-openvswitch
for security group logging.
This feature is currently only enabled for FWaaS v2 at Stein
for the charms (but is supported back to Queens in Neutron).
Change-Id: If1b332eb0f581e9acba111f79ba578a0b7081dd2
Partial-Bug: 1831972
veth pairs are currently being used to connect the qdhcp namespace
to the underlying bridge. This behaviour appears to only be needed
for old kernels with limited namespaces support (pre trusty).
Change-Id: I3b090f07c995cbf375dcc1dfdbadf0d7f10ec78e
Closes-Bug: #1832021
When an isolated provider network with no virtual routers metadata
access occurs in the qdhcp netns.
Without the force_metadata option in dhcp_agent.ini ns-metadata-proxy
is not enabled. ns-metdata-proxy sits in the ip netns and proxies
requests from 169.254.169.254 to the nova-api-metadata service
outside the netns.
This change adds the force_metadata option when
enable-isolated-metadata = True.
Related to LP Bug #1831935
Change-Id: I4fde7882be69772f168a1a1a201022bf9cf3cd06
Two generic contexts to handle nova vendor metadata have
been implemented in charm-helpers. So, replace the existing
one here in order to simplify and unify the implementation
across all charms that handle vendor metadata.
Change-Id: I2a802c763f2f4403a6dfb17575aa742ca8072e96
Related-Bug: #1777714
THe sysctls are not available inside of a container, so we
should not set them.
Change-Id: I93e1052958a8c8fb44c0589caf7cb5d6a6019ab8
Closes-Bug: #1829047
If you want to have vrrp watch the external networking interface
today, the option ha_vrrp_health_check_interval [1] detects a failure
it re-triggers the transitional change - which works if the external
physical interface fails because the ping will fail.
In fact, we've tried to enable it before [2], but then we had to
revert it [3] due to instability issues [4] in previous releases of
OpenStack. Maybe the previous instability issue [4] was caused by
another keepalived issue mentioned in the comment [5], now I have
tested this option again, it works.
This is how neutron allows monitoring southbound network today, so
I would suggest we add this capability into the charm again.
[1] https://docs.openstack.org/ocata/networking-guide/ \
deploy-ovs-ha-vrrp.html#keepalived-vrrp-health-check
[2] https://review.opendev.org/#/c/601533/
[3] https://review.opendev.org/#/c/603347/
[4] https://bugs.launchpad.net/neutron/+bug/1793102
[5] https://bugs.launchpad.net/neutron/+bug/1793102/comments/5
Change-Id: If2947e7640545cb9a48215afb9b2439fdc33c645
Closes-Bug: 1825966
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: I47ad064d1a183040d51b96ce474fb03e52e04588
Alex Kavanagh
Liam Young
David Ames
Corey Bryant
Aggelos Kolaitis
Zuul
Felipe Reyes
Jose Guedez
ShangXiao
Stamatis Katsaounis
Sahid Orentino Ferdjaoui
James Page
Dmitrii Shcherbakov
Ryan Beisner
jiasirui
Camille Rodriguez
Chris MacNaughton
Rodrigo Barbieri
Chris MacNaughton
Zhang Hua
OpenDev Sysadmins
Frode Nordahl