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
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
- added mising test-requirements.txt file
- updated testenv build to build in a tmp folder outside of src
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
Change-Id: I7985b07bb215ad43403a3e581197d5e139b603ac
Add action for running OpenStack upgrades. This enables a service
to be upgraded one unit at a time.
Depends-On: I33947c474b70c5cd4722688567ba55370b805f65
Change-Id: Ic290ac6fecff0eb9d0efd3fc8ac3f6ea923ee268
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I499030b8cc7747ef0169a69cef9927c5b50c1677
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I69ddbf6261893ab87b56a73b44aa91a0049bbad3
Story: #2002586
Task: #24317