Difference between revisions of "OPS335 Assignment 1a - Murray Saul"
(→Create a "Cloning Source" VM (335assign Virtual Network)) |
(→Create a "Cloning Source" VM (335assign Virtual Network)) |
||
Line 36: | Line 36: | ||
|- | |- | ||
− | | '''source.ops335.org''' || 164.30.''' | + | | '''source.ops335.org''' || '''164.30.X.1''' ('''x''' represents the last 2 digits of your student number) || '''Cloning source''' used to create other servers for other assignments. |
|} | |} | ||
Revision as of 11:21, 20 January 2017
Purpose
In this assignment you will set up the basic functionality for a virtual machine to act as a cloning source to make it easier for the student to create other servers (VMs) in later assignments. Whenever you clone another server (in later assignments), you MUST make certain to configure the cloned server in order to make it function in the network correctly and meet the requirements of future assignments. All of the assignments for this course are interdependent of each other and belong to the same Virtual Private Network called 335assign.
General Requirements
Weight: 5% of the overall grade
Due Date: During Week 6 (in class)
Detailed Requirements
Set-up a Virtual Network (335assign)
Create a new virtual network on your Host Machine.
- Assign a newly-created virtual network the name: 335assign, and set forwarding to any physical device
(refer to lab setup. You can have have 2 different network names: "335assign" and "ops335" without causing any problems). - Addresses in this network will start with 10.161 followed by the last two digits of your student number (just as your main virtual network). The subnet mask must be 255.255.255.0
- There must NOT be a DHCP server running for this network!
- All the machines for this assignment will be connected to your newly-created virtual network called: 335assign
Create a "Cloning Source" VM (335assign Virtual Network)
Create a virtual machine that you will use as a template (i.e. a cloning source). It should have a command-line interface only. Configure it to be a good cloning source, making certain it has all the following elements prior to cloning:
- The hostname for this server will be called: source
- Don't make the virtual drive too big: you will need space for it as well as space for the clones you from your cloning source
(2GB should be enough for any cloning source and clone VM that you create for this assignment). - Make certain that you can login to your cloning source.
- Configure your network interface for this cloning-source with a static configuration. Refer to the table below for IP address and hostname.
Hostname | Address | Purpose |
---|---|---|
host.ops335.org | External Facing Address: DHCP assigned Internal Virtual Bridge (virbr1): 164.30.10.1 |
Your host machine |
source.ops335.org | 164.30.X.1 (x represents the last 2 digits of your student number) | Cloning source used to create other servers for other assignments. |
- Make certain your cloning source can connect to the Internet.
- Run a yum update for this cloning source.
- Make certain that SELinux is set to enforcing.
- Do not install software on your cloning source: you are expected to install other software on your "cloned" VMs instead.
(For example, if you are required to install bind in a clone, install it in the clone as opposed to the "cloning source") - If you have created a regular user when you installed this machine, delete that regular user (you are only to access this server via root account).
- Set up an SSH server on this "cloning source". Make sure that PermitRootLogin is set to yes for this server. Also make sure that only the root account is permitted to login using key authentication. If other users are required to be created in a later assignment, they should be permitted to log in with a their username and password.
- Generate a key pair on your Host Machine and leave the pass-phrase blank.
- Make sure you can log in from your regular user on your Host Machine to root on the "cloning source" virtual machine using specifically that key.
- Do not place that newly-generated private key on the "cloning source" VM.
Set-up Firewall Rules for your Cloning Source
Perform the following steps for this section:
- Make certain that you have iptables services enabled and running instead of Firewalld.
- The default iptables rules should be OK, so you are NOT required to make any iptables rules for this portion of the assignment.
Create Full and Incremental Backups to Host Machine
Perform the following steps for this section:
- This task is to be performed in your c7host machine.
- Issue the command su -
- Create the following directory: /root/bin
- Create a Bash shell script called /root/bin/assnBackup.bash to perform a full backup using the gzip command to backup the entire file system of your cloning-source VM to save the compressed copy to the directory path: /backup/full/).
- This shell script should store any VM image file in the "/var/lib/libvirt/images" directory that has the extension ".qcow2" as a positional parameter to be used with a for loop.
- Perform a Net-search to use the pv command to show a text-based indicator of backup for EACH VM image file. You need to add the EPEL repository (taught in OPS235) to install the pv command.
- Set execute permissions for this script, and run this Bash shell script prior to exiting your assignment work session to properly backup your cloning source. You should also make a copy of the backup on an external device (such as a USB key).
- Set-up via Cron for an incremental backup of the /etc/ directory of your cloning source to be performed every hour to the /backup/incremental/cloning-source directory.
Assignment Submission
The student is required to prove to their professor that their set-up works correctly during the regularly-scheduled lab period.
Assignment Evaluation Details
- Demonstrate working assignment to your instructor in class:
- Students need to demonstrate their assignment functionality to their professor during a lab period (like you would for any lab for "sign-off").
- Students are required to prepare everything ahead of time so that you can quickly demonstrate to your instructor that all required parts of your assignment are working.
- Download and run a shell script that will check your set-up:
- Login as root on your host machine.<.li>
- Issue the following command to install e-mail on your host machine:
yum install mailx
- Issue the command to download a checking script:
wget URL
- Set execute permissions and run the command: ./shellscriptname.bash
(You shell script contents will be mailed to your Seneca email and to your OPS335 instructor's Seneca email. If you do NOT receive an e-mail message in your Seneca email account, then there is a problem, and you MUST rerun or contact your OPS335 instructor immediately.
- Additional Assignment Information:
- This assignment is to be completed individually. Group submissions are not allowed.
- Test your machine to make sure it works. If a machine is not accessable (e.g. will not boot, can not be accessed through ssh from your host, etc.), or is otherwise non-functional, you may be told to resubmit.
- Late submissions are a subject to a penalty of 10% per day.
Evaluation Rubric
Here is an evaluation rubric (in table form) showing you how you will be evaluated for this assignment. Part of the rubric is marked from professor observation from student demonstration of assignment in class, and the other part is based on output from the results of an assignment checking script that the student will download and run.
Student Demonstration (in class) | |
Evaluation Item | Mark |
Created Virtual Network: 335assign (correct settings) |
/1 |
Can Ping source from host machine with correct IPADDR | /1 |
root account on host machine can connect to source VM via ssh application without password | /1 |
source VM can connect to the Internet (i.e. ping 8.8.8.8) |
/1 |
source can SSH to your Matrix account (i.e. your Matrix account) |
/1 |
Configuration (Checking Script Output) | |
Evaluation Item | Mark |
SELinux status set to: enforcing | /2 |
firewalld stopped and inactive | /2 |
iptables active and enabled | /2 |
correct static network configuration for source VM (half mark for each network config item) |
/5 |
source VM can connect to the Internet | /2 |
Public key properly copied to root account on each VM | /2 |
permitRootLogin set to yes for source VM | /2 |
Backup script assnBackup.bash exists on host machine and has been run | /2 |
Backup script uses pv command | /2 |
Incremental Backup of /etc/ directory of cloning-source to /backup/incremental/cloning-source directory | /2 |
Proof that VM backup were run | /2 |
TOTAL | /30 |