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
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
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
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
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
* 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
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
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
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
The database pool size is per-worker and not shared among the workers.
Currently we incorrectly scale max_pool_size with the worker count,
resulting in an excessive number of database connections that are both
unnecessary and can exhaust the MySQL server max_connections.
With the previous formula max_pool_size = workers * 4, the resulting
connection count was exponential e.g. with 10 workers you get 400
connections but with 20 workers you get 1600. With the commonly deployed
setting of worker-multiplier=0.25 you get 20 workers on 40C/80T machines
and a 3 node HA setup was consuming 3 * 1600 = 4800 MySQL connections.
This customisation was added when rpc_workers support was added (commit
b6ff05ddfe) and I cannot find any evidence that a higher pool count is
needed, the upstream neutron project also removed it's own customisation
of 10 in deference to the oslo.db default of (LP: #1682307). So this
change appears safe and will result in only 100 connections for 20
workers instead of 1600.
Closes-Bug: #1905810
Change-Id: I39b0c17a9ca04c254b08331ac10198680ce1fa28
This change only replaced the deprecated function to add a new source
in the `do_openstack_upgrade` function. The original idea of this patch
was to fix an issue that was fixed in another patch.
Copy the new version of the requirements.txt and test-requirements.txt
files to avoid pip 20.3.
Change-Id: I523e2db35cfb0f7533831e5b5fbb802b628b0431
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
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I7c3e0a7e77e16b9bf318ca22c39f8220c5144ac7
Ensures that leader does not respond to db init
notifications to avoid infitinite looping after
leader switches to a different unit.
Also ensures that leader only restarts its neutron-server
once on db init.
Closes-Bug: #1893008
Change-Id: I59b9d5e0caab62b72380879bf16cb0fd8703bb32
This option is available on both OVS and OVN to
allow virtual switch to snoop into multicast IGMP
messages and learn which ports should be flooded.
This change adds igmp snooping option on neutron.conf.
Change-Id: I3a0e757e5afe6a77cc507ee01298961c16d41cb2
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: Ie20b6b52235a10c0911afd7bc870cb1f5ee3296f
At present the neutron-api charm executes four gate tests per
release combination to cover ML2, ML2+DVR, ML2+DVR+SNAT and OVN
deployment scenarios. This adds up to over 12 hours runtime for a
full test run.
Move execution of data plane test out to the data plane charms
(neutron-openvswitch, neutron-gateway and neutron-api-plugin-ovn)
Change-Id: I64b92042e2700f2795a5d26afc768f973b71f5c0
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/235
Main README.md file had a mix of 'DHCP' and 'dhcp'. Replace the
instance of 'dhcp' by 'DHCP' to keep consistency.
Change-Id: I05bc78c4e752afb706f9c3a6803320a9702b62c3
The new default will take effect on newly deployed units when
openstack-origin is set to 'ussuri' or newer.
Any existing units or newly deployed units with openstack-origin
set to prior versions will retain the existing default.
Change-Id: Ia38dd7882105c3adad1afbf754ba2ed047dd05e2