1,760
edits
Changes
no edit summary
<font color= LAB OBJECTIVES ='red'><u>'''This lab is currently being reviewed. The final version will be ready by November 11, 2019'''</u></font>
= LAB OBJECTIVES =
|}
== Topics to be reviewed ==
: sudo and sudoers
:* man page on sudo
:* the sudoers file: /etc/sudoers
= INVESTIGATION 1: Extra VM Setup =
:* The hostname of the system is '''worker1'''.
:* It has a static IP address appropriate for your virtual network.
:* Create a regular user using your Seneca email name as the user name. :* Add this new regular user to the '''wheel''' group using the following command:<source lang="bash"> usermod -a -G wheel [seneca_id]</source>This will allow the user to run the '''sudo''' command.
:* After installation ensure that you can access '''worker1''' from your main vm using the static IP address you've assigned to it.
: In order for an automated system to be able to connect to your VM and administer it - you will need to be able to connect to it using SSH keys. You've done this in both OPS235 and OPS335.
: Create a new SSH key on your main VM with your regular user. Please do not use root. Then set things up so that your regular user on your '''controller VM''' can SSH to the worker VM as root (the same regular user) without putting in a password.
== PART 3 - Clone the Workers ==
