Commit Graph

3 Commits

Author SHA1 Message Date
Corey Bryant 2541283a7f Add package-upgrade action
The package-upgrade action is similar to the openstack-upgrade action
except that it performs package upgrades within the current openstack
release. If a new openstack release is available, the package-upgrade
action will not perform any upgrades.

Sync common files from release-tools, with modifications specific
to this layer.

Change-Id: I4eaee81e05d44d9649c37d397672d263bc2a1025
2022-01-19 17:20:07 +00:00
Alex Kavanagh 8100de4b24 Ensure that Endpoints are discovered for openstack-upgrade
Charms that use the openstack-upgrade action have the option (by
default in charms.openstack) to re-render their configuration files
after the packages have been upgraded.  If that charm has interfaces
that are based on the charms.reactive Endpoint class, then they need to
be discovered by the charms.reactive framework so that they can be
'found' by the from_flag() function when constructing an adapters
instance for the render function in charms.openstack (and ultimately
charm-helpers as a context).,  This involves running the
hookenv._run_atstart() function.

Closes-Bug: #1908267
Change-Id: Idfeac39b6d9974bcbbe1891623ff09cc447d87bb
2020-12-17 12:19:18 +00:00
Liam Young 9938f45e9f Support action managed upgrades
Add action for running OpenStack upgrades. This enables a service
to be upgraded one unit at a time.

Depends-On: I33947c474b70c5cd4722688567ba55370b805f65
Change-Id: Ic290ac6fecff0eb9d0efd3fc8ac3f6ea923ee268
2018-11-06 09:00:25 +00:00