Updated build-zone-setup-triton#269
Conversation
timfoster
left a comment
timfoster
left a comment
There was a problem hiding this comment.
Thanks for suggesting extra text here. Could you file a jira ticket to associate with this integration please?
| is provisioned on that headnode) | ||
| * Choose the "external" network | ||
| * Add the following Customer metadata, `{"user-script": "/usr/sbin/mdata-get root_authorized_keys > ~root/.ssh/authorized_keys ; /usr/sbin/mdata-get root_authorized_keys > ~admin/.ssh/authorized_keys; svcadm enable manifest-import"}` | ||
| * Add the following Customer metadata, `{"user-script": "/usr/sbin/mdata-get root_authorized_keys > ~root/.ssh/authorized_keys ; /usr/sbin/mdata-get root_authorized_keys > ~admin/.ssh/authorized_keys; svcadm enable manifest-import"}` along with supplying your public ssh key. |
There was a problem hiding this comment.
Could we say exactly where the public ssh key should be added, perhaps as a separate list item?
Could we also move the customer metadata section into a code-block rather than inlining it in the list of things to add?
| STATE STIME FMRI | ||
| online 20:42:28 svc:/system/manifest-import:default | ||
| ``` | ||
|
|
There was a problem hiding this comment.
This probably isn't the best for brand new users, since they won't have any context on how to access the compute-zone in order to zlogin into their zone. I'd be more inclined to leave out that section and perhaps use something along the lines of:
_
- Click "Provision machine"
During the build zone's first-boot as part of provisioning, the manifest-import service can take a few minutes to complete. Since the manifest-import service is responsible for importing and enabling the ssh service, you will have to wait for that to complete before being able to login to the zone.
_
2 participants
No description provided.