Commit Graph

14 Commits

Author SHA1 Message Date
Corey Bryant 13211f092c 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: I2c98ab0f82aa6d6d0a43365cee04d6da34a39ce4
2022-08-31 19:57:31 +01:00
Alex Kavanagh 19a65851c1 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

Change-Id: I3b005253025fa7ba2b0cdb918fe4134c44316cf0
2022-04-04 15:49:28 +01:00
Corey Bryant a0b16b9058 Add yoga bundles and release-tool syncs
* charm-helpers sync for classic charms
* pin pyparsing for aodhclient
* pin cffi for py35
* add non-voting focal-yoga bundle
* add non-voting jammy-yoga bundle
* add series metadata for jammy
* switch xena bundles to voting
* run focal-ussuri as smoke tests
* remove groovy bundles

Change-Id: Ia5771347736c27f3ebde2b08eec94252800dd91a
2021-11-09 10:27:03 -05:00
Aurelien Lourot 3f1ae3b8cc 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: Iae88c66fcb21f82bdce127f8cb405d8bb9ebc2e1
2021-07-22 14:53:49 +02:00
Alex Kavanagh 4a54e9b3e5 Updates to pin charm-tools to 2.8.3
* 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: Ic1d783ea841da5ffe331006af1ceeacf06dbcbb7
2021-02-17 12:09:48 +00:00
Alex Kavanagh 38c8fc48d2 Rebuild to use charm-tools pre 2.8 release
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.

Change-Id: I35600c4b7d60e0f03bc05e78cd1279a3b165e355
2021-02-02 17:07:01 +00:00
Aurelien Lourot c63467772c Sync release-tools
Sync release-tools boilerplate containing these changes
in order to pin pip < 20.3:
https://github.com/openstack-charmers/release-tools/pull/125
https://github.com/openstack-charmers/release-tools/pull/126

Change-Id: I5b1431991524d329aeef6af5cbd4b436a23a67fa
2020-12-11 13:55:42 +01:00
Alex Kavanagh c88adb9dd1 Sync libraries & common files prior to freeze
* 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: I5b232af01089555cbb80869ceee1e4bab90a79ea
2020-09-26 18:32:14 +01:00
Frode Nordahl 9671d176f3 Update charm build requirements
Change-Id: I7bff23d257f3682374dd1618d2366a2c8b9f4395
2020-03-03 09:54:36 +01:00
Ryan Beisner 0ba69ef3e1 Update requirements
Also remove tests/charm-helpers if present, in favor
of the pip-installed charm-helpers.

Change-Id: I5926a6f63e6308a75771ac6319abd576f453d20a
2018-10-04 10:51:40 -05:00
Liam Young a1d0b7aaa2 Render configs always needs the cluster relation
Render configs always needs the cluster relation if it is available.
There is logic in OpenStackAPIRelationAdapters that checks to see if
this unit is alone. If it is it creates a 'cluster' namespace and
populates it with data specific to this node.  If this unit has peers
then OpenStackAPIRelationAdapters populates the cluster namespace with
PeerHARelationAdapter *if* a cluster relation has been passed in. If
the unit has peers but the Peer relation has *not* been passed in
there is no cluster namespace and rendering of config that relies on
it (namely haproxy) fails.

To fix this, check if the relation exists and if it does add it to
the list of relations used to render configs

Change-Id: I6f34c28411db957d0b55155b8671bf981084bb6b
2016-07-27 15:24:14 +00:00
Liam Young be8cee7db2 Unit tests and lint fixes 2016-07-07 09:36:22 +01:00
James Page 7b7dc4d1ef Pin ruamel.yaml for now until charmtools is fixed 2016-02-11 10:25:37 +00:00
James Page 86ab342e02 Initial baseline 2016-02-11 10:03:13 +00:00