cc_staff
1,486
edits
Managing your cloud resources with OpenStack: Difference between revisions
Jump to navigation
Jump to search
Managing your cloud resources with OpenStack (view source)
Revision as of 18:23, 29 February 2016
, 8 years ago→Accessing a VM with Multiple Users
| Line 54: | Line 54: | ||
==Command Line Clients== | ==Command Line Clients== | ||
==Accessing a VM with Multiple Users== | ==Accessing a VM with Multiple Users== | ||
[[File:VM multi user cloud init.png|400px|thumb| Cloud init to add multiple users (Click for larger image)]] | |||
There are a number of ways to approach this, but basically what is needed is to add another public ssh key to the VM (see [[ssh keys]] about working with and creating keys). This could be done by adding to the <code>authorized_keys</code> of the primary user account provided for the VM, usually named after the operating system, or it could be added to a newly created user account. In Ubuntu, when logged in with the primary user's account this can be accomplished with the command <code>sudo adduser USERNAME</code>. Then add the supplied public key to that users <code>.ssh/authorized_keys</code> file as described in [[ssh keys]] and linked pages. | There are a number of ways to approach this, but basically what is needed is to add another public ssh key to the VM (see [[ssh keys]] about working with and creating keys). This could be done by adding to the <code>authorized_keys</code> of the primary user account provided for the VM, usually named after the operating system, or it could be added to a newly created user account. In Ubuntu, when logged in with the primary user's account this can be accomplished with the command <code>sudo adduser USERNAME</code>. Then add the supplied public key to that users <code>.ssh/authorized_keys</code> file as described in [[ssh keys]] and linked pages. | ||
Another alternative would be to do this during the creation of your VM using [http://cloudinit.readthedocs.org/en/latest/index.html# CloudInit]. The following example CloudInit YAML script (see [http://www.yaml.org/spec/1.2/spec.html#Preview YAML Preview]): | |||
#cloud-config | |||
users: | |||
- name: sysadmin | |||
shell: /bin/bash | |||
sudo: ALL=(ALL) NOPASSWD:ALL | |||
ssh_authorized_keys: | |||
- <Insert public key> | |||
- name: user | |||
shell: /bin/bash | |||
ssh_authorized_keys: | |||
- <Insert public key> | |||
adds two users <code>sysadmin</code> and <code>user</code> with and without sudo permissions respectively. The <code><Insert public key></code> must be replaced with the public key to use for that user. After the VM has finished spawning, take a look at the log to ensure that the public keys have been added correctly for those users. The log should show something like: | |||
ci-info: ++++++++Authorized keys from /home/sysadmin/.ssh/authorized_keys for user sysadmin++++++++ | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
ci-info: | Keytype | Fingerprint (md5) | Options | Comment | | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
ci-info: | ssh-rsa | ad:a6:35:fc:2a:17:c9:02:cd:59:38:c9:18:dd:15:19 | - | rsa-key-20160229 | | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
ci-info: ++++++++++++Authorized keys from /home/user/.ssh/authorized_keys for user user++++++++++++ | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
ci-info: | Keytype | Fingerprint (md5) | Options | Comment | | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
ci-info: | ssh-rsa | ad:a6:35:fc:2a:17:c9:02:cd:59:38:c9:18:dd:15:19 | - | rsa-key-20160229 | | |||
ci-info: +---------+-------------------------------------------------+---------+------------------+ | |||
Note that YAML is very picky about white space formatting, so that there must be a space after the "-" before your public key string. Also, this configuration overwrites the default user that is added when no CloudInit script is specified, so that the users listed in this configuration script will be all that are on the newly created VM so it is important to have at least one user with sudo permission. More users can be added by simply including another <code>- name: username</code> section. | |||