Reference no: EM132914632

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 called 335assign.

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 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

1. The name of this cloning-source VM will be called: pangaea.
2. 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.
3. The VM should have a command-line interface only.
4. 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.

5. Make certain your cloning-source can connect to the Internet using the newer static configuration.
6. Run a yum update for this cloning-source.
7. Make certain that SELinux is set to enforcing (unless you're in Andrew's sections - then have it disabled).
8. Set up an SSH server on this "cloning-source".
9. Make sure that PermitRootLogin is set to yes for this server.
10. 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.
11. 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.
12. 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.
13. 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:

1. This task is to be performed in your host machine.
2. Issue the command su -
3. 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/).
4. This shell script should read 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.
5. 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.
6. 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).
7. 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.