Allow charms to associate structured data with status

Bug #1483672 reported by Adam Collard on 2015-08-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

With Juju 1.24 I can set a unit's status to "maintenance" and associate a human-friendly message with that. I'd like to be able to associate computer-friendly data with it too. Here's my use-case:

OpenStack Autopilot wants to allow machines to be put into maintenance mode (i.e. stop all of the charm managed services and allow arbitrary maintenance). In order to do that it will use actions on the units on that machine to tell them to "pause". Once paused, the units will have stopped their (Unix) services and use `status-set maintenance "Paused. Use resume action to resume normal service"` to set the status of the unit.

Whilst paused, the services shouldn't be started as a result of any hooks running on the unit (only by the resume action). Most notably config-changed and *-relation changed will get some guards to prevent (Unix) service interactions whilst paused.

As of 1.24.4 I have to use `status-get --include-data` to get the message and then match against that. This feels a little clunky, because I have to match against a human-friendly string, when really I'd like to be able to use the little key-value store in status-data to have an easy programmatic way of identifying that I'm "paused".

Ian Booth (wallyworld) on 2015-08-11
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.25.0
Curtis Hovey (sinzui) on 2015-08-27
Changed in juju-core:
milestone: 1.25-alpha1 → 1.25-beta1
Changed in juju-core:
assignee: nobody → Horacio Durán (hduran-8)
status: Triaged → In Progress
Ian Booth (wallyworld) on 2015-09-03
Changed in juju-core:
milestone: 1.25-beta1 → 1.26.0
Ian Booth (wallyworld) on 2015-09-07
Changed in juju-core:
status: In Progress → Fix Committed
Changed in juju-core:
status: Fix Committed → Triaged
Ian Booth (wallyworld) on 2015-09-15
no longer affects: juju-core/1.25
Changed in juju-core:
milestone: 1.26.0 → 2.0-beta5
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.0
Changed in juju-core:
milestone: 2.0.0 → 2.1.0
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
Changed in juju:
assignee: Horacio Durán (hduran-8) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers