1655a2c9ee
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. |
||
---|---|---|
unit_tests | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
README.md | ||
__init__.py | ||
copyright | ||
interface.yaml | ||
requires.py | ||
test-requirements.txt | ||
tox.ini |
README.md
Overview
This interface is used for a charm to request a restart of a service managed by another charm.
Usage
The interface provides the {relation-name}.connected
state.
Requesting a restart of all remote services:
@reactive.when('service-control.connected')
def configure(service_control):
...
service_control.request_restart()
Requesting a restart of a specific type of remote services:
@reactive.when('service-control.connected')
def configure(service_control):
...
service_control.request_restart(service_type='neutron')
Metadata
To consume this interface in your charm or layer, add the following to
layer.yaml
:
includes: ['interface:service-control']
and add a requires interface of type service-control
to your charm or layers
metadata.yaml
eg:
requires:
neutron-control:
interface: service-control
Bugs
Please report bugs on Launchpad.
For development questions please refer to the OpenStack Charm Guide.