Reference no: EM132699880

OPS335 Open System Application Server - Seneca College

Assignment 1

Part 1

Purpose

For this portion of assignment 1, 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.

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 172.28.105. 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 cloning-source.

Details for the cloning-source

The name of this cloning-source VM will be called: pangaea.
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 continents.earth.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
(5 GB should be enough for any cloning-source and clone VM that you create for this assignment).
The hostname for this server will be called: pangaea
Make certain that you can login to your cloning-source.
Configure your network interface for this cloning-source with a static configuration and is connected to the 335assign network. Refer to the table below for IP address and hostname.

Make certain your cloning-source can connect to the Internet using the newer static configuration.
Run a yum update for this cloning-source.
Make certain that SELinux is set to enforcing.
Set up an SSH server on this "cloning-source".
Make sure that PermitRootLogin is set to yes for this server.
Make certain that the root account is permitted to login only using key authentication. If other users are required to be created in a later assignment, they should be permitted to log in with their username and password.
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.
Test to make certain that you can login from root on your host machine to your root account on the cloning-course ("pangaea") without being prompted for a pass-phrase.
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!).
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:
All outgoing traffic is allowed.
Responses to any traffic the machine sends out are allowed.
Traffic on the loopback interface is allowed.
The host machine (and only the host machine) must be able to ssh to that cloning-source VM.
ICMP traffic is allowed if it originated with the local network only.
As this is acting as the secure basis for later machines, no other traffic should be allowed, and no response should be sent if any other traffic is received.
Create Full and Incremental Backups of cloning-source VM
Perform the following steps for this section:

This task is to be performed in your host machine.
Issue the command su -
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 each of any number of VM image files in the /var/lib/libvirt/images directory that has the extension ".qcow2". In this way, this shell script will safely backup any new VMs that are created later in this course, yet backup the existing labs and assignment VMs.
Perform a Net-search to use the pv (pipe-viewer) command to show a text-based indicator of backup for EACH VM image file. You need to add the EPEL repository 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 a crontab entry, an incremental backup of the /etc/ directory of your cloning-source to be performed every hour to the /backup/incremental/cloning-source directory.

Part 2

Purpose
In this assignment, you will use the 335assign virtual network and the pangaea cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: australinea) will be a master name server, and the other VM (hostname: antarctica) will be a slave name server. You will install and setup the master and slave servers in order to provide various domain name resolutions for existing servers, and for servers that will be created and used in assignment #2.

Set-up Master Name Server (australinea)
Perform the following steps for this section:

Create a clone virtual machine called australinea from the pangaea cloning-source. Refer to the table below for address and hostname.
Create a regular user for this virtual machine using your Seneca userID.
Setup a DNS server on your australinea virtual machine noting the following items below:
This virtual machine will be the Master DNS server for continents.earth.ops.
Only antarctica will be allowed to obtain zone transfers of this zone.
This machine will provide forward and reverse lookups of ALL virtual machines in the continents.earth.ops. zone, including resource records for virtual machines that do not currently exist.
You MUST use the following names for both the forward and reverse zone files in /var/named directory: mydb-for-continents.earth.ops and mydb-for-172.28.105
Any machine in the continents.earth.ops network may use this machine to perform queries of machines outside the network, however it will route all such queries through the DNS server you created in lab #3.
For machines outside the continents.earth.ops domain, it will only answer queries about machines inside the network. They may not use it to query other machines.
Set-up Slave Name Server (antarctica)
Perform the following steps for this section:

Create a clone virtual machine called antarctica from the pangaea cloning-source. Refer to the table below for address and hostname.
Create a regular user for this virtual machine using your Seneca userID.
Setup a DNS server on your antarctica virtual machine noting the following items below:
This virtual machine will be the Slave DNS server (in case the Master Name Server goes down).
This virtual machine will obtain its zone files by copying them from the Master Name Server.
This Slave DNS server will check for updated records from the Master DNS server every three days. If the initial attempt fails, then it will attempt every twenty-four hours until it succeeds, or three weeks have passed.
This machine will provide forward and reverse lookups of ALL machines in the continents.earth.ops zone, the zone files for which will be obtained from australinea.continents.earth.ops.
Only machines within the continents.earth.ops domain will be allowed to query this machine.
This machine will not provide recursive lookup capabilities for any machines.

Part 3

Purpose
In this assignment, you will use the 335assign virtual network and the pangaea cloning-source that you created in assignment 1 (part 1) to create two e-mail servers: a Mail Transfer Agent called asia and a Message Store (IMAP) called europe. You will also use the pangaea cloning source to create a Samba server called southamerica. In addition to creating those Linux servers, you will also be required to create a virtual machine for an MS Windows operating system to test-out your Samba server. As you perform and submit this assignment, you MUST run the australinea Master Name server and antarctica Slave server in order to resolve domain names to IP addresses.

Set-up Mail Transfer Agent (asia)
Perform the following steps for this section:

Create a clone virtual machine called asia from the pangaea cloning-source. Refer to the table below for address and hostname.
Only root user on your host machine must be able to ssh to the root account on each machine without being prompted for a password.
Create a regular user for this virtual machine using your Seneca userID.
Any machine within the continents.earth.ops domain will be able to route outgoing email through this server.
Any mail sent directly from this machine will use the domain as the sending address (i.e. [email protected])
You are NOT required to encrypt received email messages.
This machine will relay received email messages for any user account in the continents.earth.ops domain to europe.continents.earth.ops.
Set-up Mail Delivery Agent / Message Store (europe)
Perform the following steps for this section:

Create a clone virtual machine called europe from the pangaea cloning-source. Refer to the table below for address and hostname.
Create a regular user for this virtual machine using your Seneca userID.
Only root user on your host machine must be able to ssh to the root account on each machine without being prompted for a password.
This machine will accept incoming email for any user account in the continents.earth.ops domain.
No other machine in this domain will accept incoming email.
This machine will be an IMAP server (i.e. NOT POP3 or LTMP).
This machine will NOT use encryption.
This machine will use postfix's built-in LDA to store received emails in maildir format in a sub-directory of each users' home directory called mailboxes.
Any mail sent to root will be automatically delivered into the mailbox of the regular user created above.
Configure your Thunderbird application (installed in Lab 4b) to allow the user to send and receive email messages using the asia and europe servers.
Add MX records to the forward lookup zone on your master DNS server so that all incoming mail addressed to the domain is sent to your IMAP server (europe) first, and the MTA (asia) as a fall-back.

Set-up a Samba Server (southamerica)
Perform the following steps for this section:

Create a clone virtual machine called southamerica from the pangaea cloning-source. Refer to the table below for address and hostname.
Create a regular user for this virtual machine using your Seneca userID.
Only root user on your host machine must be able to ssh to the root account on each machine without being prompted for a password.
It will run Samba (automatically on boot) to share files with machines in this network.
Create three new users on the Samba file server, call them sarmation-yoursenecaid, kaapvaal-yoursenecaid, and gawler-yoursenecaid. (replace "yoursenecaid" with your actual Seneca ID)
Create a directory /supercontinents with the following subdirectories:
/supercontinents
+-- cratons
¦ +-- sarmation
¦ +-- kaapvaal
¦ +-- gawler
+-- pangaeaic
+-- laurasia
+-- gondwana
Set up permissions/ownership on those directories for your Linux users on the file server so that:
sarmation-yoursenecaid and kaapvall-yoursenecaid have read/write access to their own private directories.
gawler-yoursenecaid has read/write access to every directory.
Everyone has read access to the laurasia directory (but only the gawler account has write access too).
Everyone can both read and write to the gondwana directory.
Set up three Samba users to mirror your new Linux users.
Configure five shares (one for each of sarmation, kaapvaal, gawler, laurasia, and gondwana) with permissions as close as possible to the Linux permissions.
Set-up Client to Test Samba server (southamerica)
Perform the following steps for this section:

Create another virtual machine to act as a client to the samba service. If using windows, you can obtain the MS Windows image from Seneca's MSDN section (trial version good for 30 days). Refer to the table below for address and hostname.
Create a regular user for this virtual machine using your Seneca userID.
The root user on your host machine must be able to ssh to the root account on each machine without being prompted for a password (not applicable on Windows).
This machine will use the master and slave DNS servers in your domain as the primary and secondary DNS servers. It will not have access to any other DNS servers.

Attachment:- Linux server.rar