juju status of known powered down nodes
Bug #1989178 reported by
Ian Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
As a power saving exercise we have a requirement to power nodes down that aren't being used, the issue is that there is no way to exclude these nodes from "juju status" command and therefore no easy way to identify which are genuine issues against known powered down nodes
| tags: | added: aubergine |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: power-saving |
| tags: | added: status |
Revision history for this message
| Joseph Phillips (manadart) wrote | #1 |
To post a comment you must log in.
Juju is by design an agent-based system that works to realise declared state.
This breaks the model somewhat, requiring a new work-flow around the *controller* interpreting the state of machines, and invoking/revoking known down status.
Is there a reason that unused machines have been provisioned by Juju in these cases?