52377e84cf
The status_compound by designed set the unit's status many times during
hook execution. The unit's status is directly published to the
controller. This leads to outside observers seeing active status (and
lot of chatter around statuses) when the unit is in fact not ready.
With this change, units will only publish an active status at the end of
the hook execution. All other levels are still directly published to the
controller.
Units will no longer publish the WaitingStatus("no status yet"). This
creates a lot of chatter and holds little value.
Re-organize keystone __init__ not to publish false `Service not
bootstrap` status.
Closes-Bug: #2067016
Change-Id: Ie73b95972a44833ba4509f8fd2c2f52ed476004d
sunbeam-clusterd
Description
sunbeam-clusterd is an operator to manage the clusterd service on a VM/Baremetal based environment.
Usage
Deployment
sunbeam-clusterd is deployed using below command:
juju deploy sunbeam-clusterd
Configuration
This section covers common and/or important configuration options. See file
charmcraft.yaml for the full list of options, along with their descriptions and
default values. See the Juju documentation for details
on configuring applications.
Actions
This section covers Juju actions supported by the charm.
Actions allow specific operations to be performed on a per-unit basis. To
display action descriptions run juju actions sunbeam-clusterd. If the charm is not
deployed then see file charmcraft.yaml.
Contributing
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Bugs
Please report bugs on Launchpad.