juju ssh to some unit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
It happens countless times during normal cloud operations that I need to ssh to a unit, but don't really care which unit I'm going to end up into. This happens particularly often (as an example) with ceph-mon and hacluster applications (since cluster commands can be run from any unit), but can also occur with single-unit applications: in either case I have to first run juju status to figure our the unit IDs, and only then I can juju ssh to the unit I have (randomly) chosen.
As a way to improve the user experience for operators I propose having `juju ssh <application>` make you land on a random unit; logging into the leader could be accomplished with `juju ssh <application>
Also note the somewhat related bug 1313862.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
This one is a little worrying to me from a new user’s perspective. If I haven’t yet grokked the relationship between applications and units, landing on a random unit in an application might be confusing.
I’d support a syntax like `juju ssh application/any`.
I do love the /leader idea!