| 2017-09-26 16:20:16 |
Peter Matulis |
bug |
|
|
added bug |
| 2017-10-03 22:20:59 |
Anastasia |
tags |
docteam |
docteam juju-ssh ssh |
|
| 2017-10-03 22:21:54 |
Anastasia |
juju: status |
New |
Triaged |
|
| 2017-10-03 22:21:57 |
Anastasia |
juju: importance |
Undecided |
Wishlist |
|
| 2017-10-04 00:07:35 |
Peter Matulis |
description |
A user needs to go through all this in order to use `juju ssh`:
* Reminds/ensures the Juju admin to create a user and grant him/her 'admin' access to the model;
which probably confers other rights that the user should not have like destroying the model
('superuser' rights are actually needed but this may be a bug)
* One time stuff like install Juju and register the user
* Learning a new tool and concepts
* Needs to be logged in to the controller
* Ensures their private key is properly named (or use ssh-agent); see LP #1718775
This process is cumbersome and very easy to circumvent by using direct access with a standard SSH client.
1. Is there some way to enforce `juju ssh`?
2. Do we want the documentation to suggest that `juju ssh` is more of an administrator's convenient troubleshooting tool (which it is; it's great)? Otherwise, it all ends up looking a bit awkward on paper. |
A user needs to go through all this in order to use `juju ssh`:
* Reminds/ensures the Juju admin to create a user and grant him/her 'admin' access to the model;
which probably confers other rights that the user should not have like destroying the model
('superuser' rights are actually needed but this may be a bug)
* One time stuff like install Juju and register the user
* Learning a new tool and concepts
* Needs to be logged in to the controller
This process is cumbersome and very easy to circumvent by using direct access with a standard SSH client.
1. Is there some way to enforce `juju ssh`?
2. Do we want the documentation to suggest that `juju ssh` is more of an administrator's convenient troubleshooting tool (which it is; it's great)? Otherwise, it all ends up looking a bit awkward on paper. |
|
| 2019-01-30 15:31:13 |
Peter Matulis |
description |
A user needs to go through all this in order to use `juju ssh`:
* Reminds/ensures the Juju admin to create a user and grant him/her 'admin' access to the model;
which probably confers other rights that the user should not have like destroying the model
('superuser' rights are actually needed but this may be a bug)
* One time stuff like install Juju and register the user
* Learning a new tool and concepts
* Needs to be logged in to the controller
This process is cumbersome and very easy to circumvent by using direct access with a standard SSH client.
1. Is there some way to enforce `juju ssh`?
2. Do we want the documentation to suggest that `juju ssh` is more of an administrator's convenient troubleshooting tool (which it is; it's great)? Otherwise, it all ends up looking a bit awkward on paper. |
A user needs to go through all this in order to use `juju ssh`:
* Reminds/ensures the Juju admin to create a user and grant him/her 'admin' access to the model;
which probably confers other rights that the user should not have like destroying the model
('superuser' rights are actually needed but this may be a bug)
* Installs Juju and registers the controller
* Learns a new tool and concepts
* Logs in to the controller
This process is cumbersome and very easy to circumvent by using direct access with a standard SSH client.
1. Is there some way to enforce `juju ssh`?
2. Do we want the documentation to suggest that `juju ssh` is more of an administrator's convenient troubleshooting tool (which it is; it's great)? Otherwise, it all ends up looking a bit awkward on paper. |
|
| 2022-11-04 06:09:39 |
Canonical Juju QA Bot |
juju: importance |
Wishlist |
Low |
|
| 2022-11-04 06:09:40 |
Canonical Juju QA Bot |
tags |
docteam juju-ssh ssh |
docteam expirebugs-bot juju-ssh ssh |
|
