Note: there aren't actually any unit tests, but this at least moves it
away from the deprecated library.
Change-Id: Ic9bec4534bc200d427241cd60b5b90b0fd89102e
- 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: I6574937828a114add62a3417d30ec6541b124485
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: I0157a9abf9f2e5af7ad78a9baac9ff519edaae21
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: Id34caff5e692448a9b65b3ab573bb637a38e3df3
Story: #2002586
Task: #24317
The job --allow-unverified is obsolete, also python-apt cannot be
installed and is unneeded for current jobs.
Remove so that python installation works.
Change-Id: I41e6d91bc9ca0c40e29f05ba1eabfb87523f725d
When charms.reactive 0.5.0 was released, the reactive.bus.State and
reactive.bus.StateList were deprecated. This change removes them as the
manila and manila-generic charms will no longer function.
Change-Id: Ifc025d063d5fba5f2b8b20773b4a9543f883a0ea
Closes-Bug: #1718152
There is a strange bug where, randomly, and only with Juju 1.25.9 or 10,
the conversation for a relation doesn't exist, even though the relation
has been made. This is a workaround that appears to have no impact on
using charm's functionality.
The clear_changed() methods are to remove a {relation-name}.changed flag
that gets set when the data on the relation changes. However, not being
able to clear it, simply means that it will still be set the next time
the charm runs which might mean that some handlers run again. This
shouldn't be a problem as, by design, reactive handlers MUST be
idempotent.
Change-Id: I26ec730d88e04fb3942d0240bf4eba6c6642a168
Related-Bug: 1663633
The interface between the manila charm and manila configuration charms
has been simplified so that backend charms can render their
configuration section using, say, jinja2.
Change-Id: I76866007e3c89bb16bc7985a692fbd8f3e136a71
This commit contains the interface code to connect between the
manila charm and a backend plugin that will provide configuration
for the manila.
Plugin charms are subordinate because they need to be on the same
unit/machine as the manila file share service.
This interface also implements a 1-many interface and so contains code
to manage that. That code will be abstracted back to charms.openstack
at some point.
Change-Id: Ied0ad014ab7b1d4778113b0d3f2bbae08075372e