Service and Unit Inspectors
[GOAL]
Let users work entirely within the environment view. This will mean rewriting all current detail views. When doing this, we plan to readdress the technical approach to this code to better handle concurrent changes.
As part of our work in improving the approach to concurrent changes, we hope that the Juju Core team will help us implement a SetUnit API call, replacing our use of AddUnit and RemoveUnit.
[RATIONALE]
User testing revealed the disconnect between the environment view and other views as a primary usability problem. This addresses the issue.
Also, the GUI does not work well when used concurrently with other users. Fix this problem as we build the new UX.
Blueprint information
- Status:
- Complete
- Approver:
- Gary Poster
- Priority:
- Essential
- Drafter:
- Gary Poster
- Direction:
- Approved
- Assignee:
- Juju GUI Hackers
- Definition:
- Approved
- Series goal:
- Accepted for saucy
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Gary Poster
- Completed by
- Gary Poster
Whiteboard
[RISKS]
- jujucharms.com work is not yet complete, and this work builds off of that effort. This may slow down our timeline.
Work Items
Work items:
[juju-gui] service and unit detail views can be used without leaving the environment view: TODO
[juju-gui] service and unit detail views are updated continuously to dynamically reflect changes in the environment: TODO
[juju-gui] service and unit detail views support edits while changes occur: TODO
[juju-gui] service and unit detail views communicate concurrent changes to edited data and invite the user to switch to the new value: TODO
[juju-gui] service and unit detail views support a restricted (readonly) mode: TODO
[juju-gui] service and unit detail views support a solid concurrency story for setting unit counts: TODO
[juju-gui] service and unit detail views can support having multiple services viewed simultaneously: TODO