OPS535-vl-lab-nfs

From CDOT Wiki
Revision as of 17:41, 30 May 2021 by Rchan (talk | contribs) (Created page with "'''DO NOT USE - Work in Progress''' <font color='red'>DO NOT USE - Work in Progress</font> Category: OPS535Category: OPS535-LabsCategory: rchan =OPS535 Lab 2 (usin...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

DO NOT USE - Work in Progress DO NOT USE - Work in Progress

OPS535 Lab 2 (using Virutal Lab)

Objectives

  • Setup and configure your assigned VMs in the OPS535 Virtual Lab for this lab, future labs, and assignments
  • Configure one of the VMs as your control workstation for remote administration tasks
  • Create and deploy remote administration scripts using bash/ansible

Pre-Requisites

  • Complete the collection of baseline information on your assigned VMs (VM1, VM2, VM3, and VM4)
  • Complete the NFS lab on your home VMs


Investigation 1: VMs Configuration

Perform the following steps on vm2:


Investigation 2: Control Workstation Configuration

Perform the following steps on VM1 as root:

Investigation 3: Scripts for remote administrations

Task 1

Using bash scripts

Task 2

Using Ansible Playbooks


Completing the Lab

You should now have a common part of the filesystem available to all three vms. Files you store there on one machine will be accessible for the other machines too. Note that this should only be available when using your internal, statically assigned addresses. You have also explored how access permissions are used between the machines, and since this service relies on UIDs accessed on each machine, keeping them synchronized between machines becomes vital. In a future lab we will explore a service that will manage that aspect of our networks.

Follow the instructions on blackboard to submit the lab.

Exploration Questions