13,420
edits
Changes
no edit summary
{{Admon/important|This is NOT Assignment 1 Part 1!|This is the '''ROUGH WORK''' for Murray Saul's section for OPS335 Assignment 1 - Part 1. These assignment specifications are NOT complete. <br><br>Once the assignment specifications are ready, then a link will appear in the [https://wiki.cdot.senecacollege.ca/wiki/OPS335 Main OPS335 WIKI] .}}<br><br>
== Purpose ==
== General Requirements ==
'''Weight''': 53% of the overall grade '''Due Date''': During Week 6 (in class)
'''Due Date''': During Week 5 (in class)
== Detailed Requirements ==
=== Set-up a Virtual Network (335assign) ===
* Assign a newly-created virtual network the name: '''335assign''', and set '''forwarding to any physical device'''<br>(refer to [http://zenit.senecac.on.ca/wiki/index.php/OPS335_Installation_Lab#INVESTIGATION_2:_VIRTUAL_MACHINE_INSTALLATION lab setup]. You can have have 2 different network names: "335assign" and "ops335" without causing any problems).
* Addresses in this network will start with '''10172.161''' followed by the '''last two digits of your student number30.20''' (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: '''335assign'''
=== Create a "Cloning-Source" VM (335assign Virtual Network) ===
# The name of this cloning-source VM will be called: '''seedling'''.#You should use the options that you used in your lab1 to setup the static network, plus you should use the DOMAIN parameter to set the '''coniferous.trees.ops''' domain for your cloning-source.#The VM should have a command-line interface only.#Configure it to be a good cloning-source, '''making certain that the cloning-source 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 SELinux is set to ::*The hostname for this server will be called: '''enforcingseedling'''.# ::*Make certain that you can login to your cloning -source. The minimum commands required are:: *Configure your network interface for this cloning-source with a '''hoststatic''', '''dig''', 'configuration and is connected to the ''netstat'335assign'', '''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.# 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.<br>
{| class="wikitable" | style="margin-left:50px;"
! Hostname !! Address !! Purpose
|-
| '''spruce.coniferous.trees.ops''' (your existing source) || External Facing Address:''' DHCP assigned'''<br>Internal Virtual Bridge (virbr1):''' 172.30.20.1''' || Your '''host''' machine
|-| '''seedling.coniferous.trees.ops''' || '''172.30.20.100''' || '''Cloning-source''' used to create other servers for other assignments.|} <ol><li value="5">Make certain your cloning-source can connect to the Internet using the newer static configuration.</li><li>Run a '''yum update''' for this cloning-source.</li><li>Make certain that SELinux is set to '''enforcing'''.</li><li>Set up an SSH server on this "cloning-source".</li><li> Make sure that '''PermitRootLogin''' is set to '''yes''' for this server.</li><li>Make ceratin 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.</li><li>Copy the same public key (already generated for your '''Host Machine''' for your '''root''' account in lab1) to the '''root''' account on your cloning-source.</li><li>Test to make certain that you can login from root on your host machine to your root account on the cloning-course ("seedling") without being prompted for a pass-phrase.</li><li>If you have created a '''regular user''' when you installed this machine, '''delete that regular user''' (make certain to '''remove the regular user's home directory!''').</li></ol> === 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''.
# Modify the iptables to meet the following conditions:::<ul>::<li>All outgoing traffic is allowed.</li>::<li>Responses to any traffic the machine sends out are allowed.</li>::<li>Traffic on the loopback interface is allowed.</li>::<li>The default iptables rules should host machine (and <b>only</b> the host machine) must be OK, so you are NOT required able to ssh to make any iptables rules for that cloning-source VM.</li>::<li>ICMP traffic is allowed if it originated with the <b>local network only</b>.</li>::<li>As this portion of is acting as the assignmentsecure basis for later machines, no other traffic should be allowed.</li>::</ul>
=== Create Full and Incremental Backups of cloning-source VM===