Author: Alex Kavanagh
Author Date: 2024-02-09 18:15:47 UTC

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: Ieb68946379d497db3ac385513c528b852dba88cd

Author: Alex Kavanagh
Author Date: 2024-02-09 18:15:47 UTC

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: Ieb68946379d497db3ac385513c528b852dba88cd

Author: Alex Kavanagh
Author Date: 2023-10-17 17:00:57 UTC

Updates for testing period for 23.10 release

* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* Locked requirements using pip-compile:
  * existing (test-)requirements.txt ->
    (test-)requirements.in
  * pip-compile to *-py3[8|10].txt using python3.8
    and python3.10.
  * Updated tox.ini to use the appropriate merged
    requirements-*.txt files.
* Removal of lunar from metadata, charmcraft.yaml
  osci.yaml, tests.yaml and associated bundles.
* Locked libs and tests to stable/bobcat branches for:
  * charm-helpers
  * charms.openstack
  * zaza
  * zaza-openstack-tests

Change-Id: I71db4ac5cc9eefe9ccc554a65cc728db9cf98e83

Author: Felipe Reyes
Author Date: 2023-06-08 19:33:37 UTC

Charm-helpers sync

Sync to the latest revision available in the stable/antelope branch, among the
most relevant patches are:

837a8b58 Support legacy cert requests (#799)
580c7764 Update Makefile to be consistent with CI (#777) (#795)
a2468260 Run CI on stable branches (#786) (#787)
ed014373 Update method for checking endpoint protocol (#769) (#775)

Change-Id: Ie17b9431d51e9989372d695f4077f5b034154422

Author: Zuul
Author Date: 2023-02-20 09:26:09 UTC

Merge "Use vault 1.6/edge channel." into stable/ussuri

Author: Corey Bryant
Author Date: 2023-01-13 20:06:41 UTC

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: I3d48e24a93645d18505adb67d84c11b5f602ec68

Author: Corey Bryant
Author Date: 2023-01-13 20:06:03 UTC

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: I8d9ca1ae1698597a4368093a35b5dc846918d355

Author: Corey Bryant
Author Date: 2023-01-13 20:05:53 UTC

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: If527832802f7da5061aed8b7a7ebc7a03acf0a39

Author: Corey Bryant
Author Date: 2023-01-13 20:04:20 UTC

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: I8ea7059db07b6afffadda2f4c6e4b7934e82ea09

Author: Bas de Bruijne
Author Date: 2022-12-02 17:30:41 UTC

Add juju-exec for juju 3 compatibility

In juju3, juju-run is moved to juju-exec
gsss should be able to handle both

Closes-bug: #1993652
Change-Id: I980306269a68c04735811324f6b826622bc6647c
(cherry picked from commit 9304d1543463ce65f1e2fae9cba1cea22184e3c0)

Author: Bas de Bruijne
Author Date: 2022-12-02 17:30:41 UTC

Add juju-exec for juju 3 compatibility

In juju3, juju-run is moved to juju-exec
gsss should be able to handle both

Closes-bug: #1993652
Change-Id: I980306269a68c04735811324f6b826622bc6647c
(cherry picked from commit 9304d1543463ce65f1e2fae9cba1cea22184e3c0)

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: I39fccb4410d461d6abc8df03995cc8734473ef0a

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: I39fccb4410d461d6abc8df03995cc8734473ef0a

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: I39fccb4410d461d6abc8df03995cc8734473ef0a

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: I39fccb4410d461d6abc8df03995cc8734473ef0a

Author: Dmitrii Shcherbakov
Author Date: 2021-08-30 13:17:32 UTC

Remove local apache2 install, rework use_swift

The functionality of use_swift where a local apache2 instance was set up
for metadata was deprecated for removal and this change actually removes
this. However, the option itself can still be used as an indicator
whether Swift is intended to be used for simplestreams metadata or not.
If the usage is explicitly requested, the charm but Swift endpoints are
not yet present, the charm will now will set the unit state to
maintenance in addition to local logging that was done previously.

Swift presence checking is now endpoint-based instead of being
service-based (no use for the case where endpoints are not set up while
the service is in the catalog).

The lack of swift presence is also ignored for the purposes of
generating proxy setting context - if the endpoint is not there there is
not point in trying to generate NO_PROXY rules for it.

This change also makes test bundles use ceph as a storage medium for
glance since out of space errors were encountered during testing as the
glance unit was running out of space for image storage.

Closes-Bug: #1942047
Closes-Bug: #1934563
Closes-Bug: #1938069

Change-Id: I6519b1449806ad19ee4545501bc4631c9f8e535f
(cherry picked from commit d1f8c4ba4cec4324ef9edc91c357672349176dfc)

Author: Aurelien Lourot
Author Date: 2021-02-10 19:06:15 UTC

Updates for stable branch creation 21.01

Set default branch for git review/gerrit.
Switch tests to stable.
Switch to using stable charm-helpers branch.
Switch to using stable charm.openstack branch.
Switch to using stable zaza branch.
Switch to using stable zaza-openstack-tests branch.

Change-Id: Ib61249349fed57a00aa500705b3a97309988c885

Author: Aurelien Lourot
Author Date: 2020-11-02 10:44:23 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch tests to stable.

Switch to using stable charm-helpers branch.

Switch to using stable charm.openstack branch.

Change-Id: I915914660e7bc389a07cc9fd27e6daae938d93ae

Author: Alex Kavanagh
Author Date: 2020-08-13 10:31:34 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch tests to stable.

Switch to using stable charm-helpers branch.

Switch to using stable charm.openstack branch.

Change-Id: Ia6a8cb5fb1a9928e5cf3995c86954b2be1cb36ea

Author: James Page
Author Date: 2020-06-18 14:43:45 UTC

Ensure ssl_ca is always installed to system certs

If an encoded SSL CA cert is provided via configuration ensure
it is installed to the system certificate store.

Add focal to list of default images to sync into glance. This
resolved zaza testing failures and ensures that all LTS releases
of Ubuntu are sync'ed by default.

Change-Id: I58f4b89996dc734c4253c2bc2237616434c8143c
Closes-Bug: 1851474
(cherry picked from commit 2dfcecf8d2fa76654a6f9773dadef2648c4db110)

Author: Liam Young
Author Date: 2020-02-17 15:44:40 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch zaza bundles to stable charms.

Switch to using stable charm-helpers branch.

Change-Id: I2a5056fad70cbb69c42205f54c5cab9da8f34885

Author: David Ames
Author Date: 2019-10-24 19:24:08 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch to using stable charm-helpers branch.

Change-Id: Ifeb8abf13b6d88608f57728e4046437d2c0a8c10

Author: David Ames
Author Date: 2019-08-12 16:40:07 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch to using stable charm-helpers branch.

Change-Id: Ib5582d78f6dae8f38c38aec910167c96c1421fdb

Author: David Ames
Author Date: 2019-05-06 23:14:31 UTC

Update stable charms to use stable CH in test reqs

In our test-requirements.txt we often pull in charm-helpers. As stable and
master branches of charm-helpers diverge this can lead to testing failures
on the stable branch charms.

Update tests-requirements.txt to point to the stable branch of charm-helpers.

Change-Id: I64ddb703205994ff4ab7b30633d26b04cde04ee1

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:40:14 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:40:14 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:40:14 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:40:14 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.