| 2015-06-23 13:55:01 |
Scott Moser |
description |
when a user starts a node, it comes up in ephemeral environment which has the user's ssh keys.
this is very useful for debugging curtin install failures, but not so useful if the user tries ssh'ing in.
its very unexpecdted for user to successfully ssh in and then have the system rebooted (when install is done) or have a iscsi-root.
One easy solution to this is for maas to instruct cloud-init to provision a different default user during the ephemeral environment.
2 options for this:
#cloud-config
user: ephemeral
The above is simpler, but will cause error on precise (which did not add users on boot, but required them added in system).
This form will be ignored on precise and supported on trusty+.
#cloud-config
system_info:
default_user:
name: ephemeral |
when a user starts a node, it comes up in ephemeral environment which has the user's ssh keys.
this is very useful for debugging curtin install failures, but not so useful if the user tries ssh'ing in.
its very unexpecdted for user to successfully ssh in and then have the system rebooted (when install is done) or have a iscsi-root.
One easy solution to this is for maas to instruct cloud-init to provision a different default user during the ephemeral environment.
2 options for this:
#cloud-config
user: ephemeral
The above is simpler, but will cause error on precise (which did not add users on boot, but required them added in system).
This form will be ignored on precise and supported on trusty+.
#cloud-config
system_info:
default_user:
name: ephemeral
Related bugs:
* bug 1460193: MAAS needs to inject the user's SSH key into the commissioning image for debugging |
|
