View source for OPS335 Assignment 1 - 2016-1

= OPS335 Assignment 1 =

'''Weight''': 10% of the overall grade

'''Due Date''':

* If your professor is '''Andrew Smith''': 22 February, 2016
* If your professor is '''Murray Saul''': 26 February, 2016 (in class)

= Your tasks =

== Virtual Network ==

Create a new virtual network on your Host Machine.

* Assign the newly-created virtual network the name: '''asg1net''', and set '''forwarding to any physical device'''.
* 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 '''<u>NOT</u>''' be a DHCP server running for this network!
* All the machines for this assignment will be connected to your newly-created virtual network called: '''asg1net'''

== Create a "Cloning Source" VM (asg1net 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:

# 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<br>(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. The minimum commands required are: '''host''', '''dig''', '''netstat''', '''links'''.
# 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".
# Configure your network with a static configuration. Refer to the table below for IP address and hostname.
# Make certain that you have '''iptables''' services enabled and running instead of ''Firewalld''. The default rules should suffice.
# If you have created a regular user when you installed the machine, delete that regular user (you are to use only the root account).
# Set up an SSH server on this "cloning source". Make sure that the root account is only permitted to log in using key authentication. If user users are required to be created later, they should be permitted to log in with a their username and password.
# Generate a new key pair on your Host Machine (don't delete the existing one), called: '''id_rsa_asg1'''
# 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.

== Clone "ns1" VM from "Cloning Source" &amp; Perform Setup Tasks==

Perform the following steps for this section:

#Create a clone called: '''ns1''' from the "cloning source" that will act as your '''master DNS server''' on the '''asg1net''' network. Refer to the table below for address and hostname.<br><br>
#Make certain that your DNS server must has all the records for the zone called: '''ops335a1.org''' listed in that table, including records for machines that do not exist as of yet. It is important to understand that DNS records live independently from the machines that they are "pointing" to.<br><br>
#A default setup for a master DNS server should be sufficient, but make certain that the address of your '''admin contact''' is: '''yoursenecaid@ops335a1.org''', and that slave DNS servers will check for updated records from this master every 30 minutes.

== Clone "ns2" VM from "Cloning Source" &amp; Perform Setup Tasks ==

Perform the following steps for this section:

#Create a clone called '''ns2''' from the cloning source that will act as your '''slave DNS server''' on the '''asg1net''' network. Refer to the table below for address and hostname.<br><br>
#The '''ns2''' clone will serve the same records as the '''ns1''' clone.

== List of Machines / DNS Records ==

All the machines in the table need DNS records, but only the ones in bold need to be existing machines for this assignment.

{| class="wikitable"
! Name !! Address !! Purpose
|-
| '''host.ops335a1.org''' || 10.161.X.1 || Your host machine
|-
| '''ns1.ops335a1.org''' || 10.161.X.2 || Master name server
|-
| '''ns2.ops335a1.org''' || 10.161.X.3 || Slave name server
|-
| file.ops335a1.org || 10.161.X.4 || File server
|-
| www.ops335a1.org || 10.161.X.5 || Web server
|-
| source.ops335a1.org|| 10.161.X.254 || Disk image to clone from when creating new machines.
|}

== Test Plan ==

Write a test plan with at least 5 test cases to verify that you've completed the assignment according to specifications.It doesn't need to be exhaustive but the test cases you pick should represent successful completion of the majority of the requirements.

The document you submit in PDF format needs to look professional even though we're not using a dedicated testing platform. Hopefully you can start with the test plan you created for the lab.

= Submit =

Submit the following in Blackboard or Moodle (whatever your professor uses):

# Screenshots (of the entire screen, not just the VM console) that show you have accomplished the required tasks. This includes configuration files, service statuses, and basic tests of functionality.
# The test plan.

Also you need to show your assignment to the professor in a lab period, just as a lab but please prepare everything so you can immediately show that all required parts are working.