manual provisioning docs are out of date
Bug #1273927 reported by
Andrew Wilkins
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
juju-core | ||||||
Docs |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
The docs for manual provisioning are out of date, in the unstable release. The docs need updating for 1.18.0.
no longer affects: | juju-core |
To post a comment you must log in.
I think we can remove the first "Note:" now. The manual provider is now feature complete, and the critical issues have been ironed out.
"It is not necessary to have a password-less login, however it will improve the experience by reducing the need for repeated logins." -- this needs to be reworded. The first time Juju logs into the machine, it will check if there's an "ubuntu" user. If not, it is created. The ~ubuntu/ .ssh/authorized _keys file is updated so future ssh sessions are passwordless. Also, passwordless sudo for the ubuntu user is enabled. The effect of all this is that you only ever have to enter an ssh password at most once, and a sudo password at most once. The "bootstrap-user" is used only for the initial login to create the ubuntu user.
The fact that we add/modify the ubuntu user and enable passwordless ssh and sudo needs to be called out, as it will be of interest to people analysing security implications.
The provider is now called "manual", so please substitute for all cases of "null". The Note about null requiring quotes can be dropped, as it is no longer relevant.
The "storage-auth-key" and "admin-secret" attributes can be dropped from the example config. They are automatically generated at bootstrap.
The Note about automatic environment destruction should be changed, probably to a section. It is possible to destroy the environment, just like other providers, via juju destroy- environment. However, you must explicitly destroy each of the machines added to the environment first.
The final point under "Considerations and caveats" could be reworded. It *is* possible to add-machine ssh:.. into non-manual provider environments, however the machine added must be on the exact same network segment as the bootstrap machine. For example in Azure, the machines must be on the same Virtual Network. This is a current limitation that may be lifted in the future.