This is a work-around for charm build failures resulting in:
"Cargo download dependency failed "send: no filter connected".
This is documented in the following upstream issue:
https://github.com/rust-lang/cargo/issues/12202
This affects lunar builds where the curl version is 7.88.1.
Thanks to Colin Watson for help with figuring this out.
Closes-Bug: #2037589
Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com>
Change-Id: I7a01c7cf9e28d1b766d45b2dcc906d44b347b1d7
The OVN charms prepared for the upgrade from OVN 20.03 to newer
versions by enabling the version pinning by default.
Since then we have reached agreement with upstream that rolling
upgrades should work when upgrading within the previous upstream
LTS version and the next.
Having the pinning enabled by default causes unnecessary grief for
anyone already upgraded to OVN 22.03, so it's time to turn it off
by default.
We add a charm configuration option in case anyone wants to
upgrade across LTS boundaries in the future.
Closes-Bug: #2030944
Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com>
Change-Id: I21dc2dc6615d39ffaa88cc27dbe3b2ba9b3982c4
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.
Add charmhub-pop topic
Change-Id: I7ac6283884e85c319a634e210da8972d49abff8c
* 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
* 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: I1215592725d1941f214738ee86250c74a398ee9a
The ovs package in kinetic+ (zed+) uses dh_installsystemd with
--no-start for ovsdb-server, ovs-vswitchd, and ovs-record-hostname.
this results in stop events rather than restart events. This
change updates the restart-services actions for this charm to
handle stop events.
Closes-Bug: #2012553
Change-Id: If1dd5d0e5ca640a91893376366b23e78649d5772
Remove pins.
Properly format passenv list.
Drop the outer tox.ini func-target hack.
Drop the incepted tox in src/test-requirements.txt.
Drop pip.sh script.
Change-Id: I25dec5d1853a5aeb686df353d7c661f4a6eb5b69
The current description erronously refers to 'focal-ovn-22.03' as
a valid value, while the correct value is 'cloud:focal-ovn-22.03'.
Closes-Bug: #1992592
Change-Id: I569e03aba227f488aa5199b48b9cf6fa67d382df
Charmcraft 2.1 provides the required functionality to build the
charm using the reactive plugin.
Add missing `kinetic` series in src/metadata.yaml.
Drop the `build-rective` target, old charm-tools environment
variables and redundant minversion in tox.ini.
Fixup the bases configuration and make associated changes to test
bundles.
Change-Id: I559e49ab80ca6de8b42192e1b961448a4522ce86
Commit 1bdca14 added support for using the UCA
focal-ovn-22.03 pocket by default for new deployments on Focal.
Unfortunately the change missed some required changes for this
to work end to end.
Ensure charm works on Focal without any UCA pocket with the
`openstack-release` package already intalled. The behavior
of `charms.openstack` is quite different dependning on whether
that information is available or not.
Ensure charm is able to detect availability of and to perform
payload upgrade on change of source.
Ensure charm does not attempt payload upgrade on charm upgrade.
When upgrading from a charm that does not have the `ovn-source`
configuration option, the reactive automatic flag
`config.changed.ovn-source` will fire even though it has not
changed. Clear the flag in upgrade-charm hook.
Also drop bespoke reactive handler for change of source.
The layer change in openstack-charmers/charm-layer-ovn#73 adds
handling for the `source` and `ovn-source` configuration options,
as a consequence, the bespoke handler in this charm needs to be
removed.
Closes-Bug: #1991319
Change-Id: I5dd49c5ee0af741536fc1a2974d25f8521c5a581
Add `ovn-source` configuration option which should be used in
addition to the `source` configuration option.
The default of the `ovn-source` configuration option is
determined at runtime based on whether the end user has provided
config, whether its a fresh or upgraded charm deployment and which
series it is deployed on.
Change-Id: I3d55bafb598339b0b69ad0d65473d79bf9cdbe4c
* 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: I2cb698f719106e54b06009f24ea47259419e9cad
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
Change-Id: Ibfe317d1056e44baa32c414d33f54d656887d2a1
- charmcraft: build-on 20.04 -> run-on 20.04/22.04 [*archs]
- Refresh tox targets
- Drop impish bundles and OSCI testing
- Add jammy metadata
Drop NRPE from Jammy bundles as the charm is not updated to
support Python 3.10 yet.
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/742
Change-Id: Idd8a2e2387da0012ba78d50960630e7a1472dc8e
Rebuild pulls in updates to layer-ovn which enables use
of Netplan to configure SR-IOV and Hardware Offload.
Also drop past release specific classes. As part of the migration
to charmhub we have also changed the release strategy from having
every release support all previous supported os/release
combinations to only support current and previous version (to
ensure N+1 upgrades).
Change-Id: Idc7837fd5b939b05c3ae1c8007c3080c7f0192e3
Rebuild charm to pickup new feature in layer-ovn to support
installation of additional DPDK network drivers for less
well supports cards.
Closes-Bug: 1936850
Change-Id: I61c9b0b1b49b1604e070876ceed32965da193454
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: I3199f7dba089767d27638ec3ca2b126a083fbe82
* 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: I33a8831474633c5516a956fec86d13e333a03b76
The ovn-dedicated-chassis charm consumes the sriov-netplan-shim
Python package as a wheel for its `pci` module which is used to
render the `/etc/sriov-netplan-shim/interfaces.yaml` configuration
file used for boot time configuration of SR-IOV VFs.
The package was recently updated and the chages are required for
the charm to correctly interpret sysfs information when used with
recent versions of the mlx5_core driver.
Related-Bug: #1892132
Related-Bug: #1927125
Change-Id: I17792b718024d6ff7ff52394fe33f06db971e8b1
Setting the external_ids:ovn-match-northd-version value to
'true' will make the ovn-controller refrain from making updates to
the data plane tables in the event of a version mismatch.
This in combination with stopping the ovn-controller with the
ovn-ctl stop_controller --restart command will allow upgrades
to progress with little or no data plane downtime.
(Note that we will accomplish this by a separate proposal to the
OVN package itself in Ubuntu.)
As soon as the central components are upgraded ovn-controller will
notice and resume (re-)programming of the local Open vSwitch data
plane.
Closes-Bug: #1940043
Change-Id: I16fedbc455e25bec0de4a475a9daa55b700ab3a0
This is a boilerplate section that will eventually
be added to the README for every charm that supports
the deferred restart feature.
Change-Id: Ic5728b7254a2a48e672026345620780ac65bf8a9
By default the CMS will schedule HA chassis groups across all
chassis with bridge- and bridge interface mappings configured.
This configuration option would allow you to influence where
gateways are scheduled when all units have equal bridge- and
bridge interface mapping configuration.
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/599
Closes-Bug: #1908377
Closes-Bug: #1934678
Related-Bug: #1848757
Change-Id: Ifd8f6b29c4f117850b243e2fdb79067659242a0e
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Change-Id: I968788863d39248f2d1e401ac043bfffa3efb99a
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I1598633df7da16612aeb81a7c352977a523a83de
Recent fixes to layer ovn were not picked up because the build.lock
file was not updated. This updates the build.lock file so
the layer-ovn fixes are included.
Change-Id: Ifd49d81e16902c8094ddb9ac0f0b0b50e632a84b
* 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: Ia060b7ebef8585b0976afaf7b8c26f18abdd7b15
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I96af53cd88361253e2f683c4eb10dcd4a268d779
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: I716de45b98f97d19138d424fc0279a5a058b30c1
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: Ia4cf52bae72d1d561a253e4ec4e17703ac714cc7
Frode Nordahl