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
lijunjie