Reference no: EM132546091

Scenario

You are the sysadmin for a software development startup company, called cqunix, that is moving into a new building. The company has 10 full-time employees, as well as up to another 10 that either work part-time or perform short-term contract work at the company. Each full-time employee will have a dedicated workstation; most also have a laptop. The part-time/contract staff have their own or company-supplied laptops. There will also be several spare workstations. The company develops Unix and Linux software, and they are an (Ubuntu) Linux exclusive company for all their computers.

Workstations, Laptops and Servers
The company has grown quite quickly. Initially when there was just a few friends, they used all online services (e.g. Google Docs, GitHub, DropBox). But now as they move into the new building, they have decided to use their own infrastructure. Most of the employees work in a distributed mode, working on their own computers and sharing resources direct with colleagues, however there are several centralised services required. Specifically, they have identified the need for the following. Included are the selected names.

Part 1. Apache-based web server, called adelaide, to host a simple company website. The website is developed using HTML, CSS, Javascript and PHP by one full-time employee, with assistance by one contractor.

Part 2. Secure shell server, called sydney, to allow employees and contractors to login and compile code. All people involved in the company should have accounts, and be able to access the SSH server from both internal network and from external (public) networks.

Part 3. Git server, called gladstone, to store all code and documents. Everyone is experienced in using git on the command line on their own computers (they don't use the web i nterface), however in the past they used GitHub as the server. Now they will use this internal server, instead of GitHub. The access requirements are the same as for the SSH server.

Part 4. Backup server, called bundaberg, to store a backup of the web, SSH and Git servers. The backup requirements are described in detail below.

Part 5. DHCP server, called darwin, to provide dynamic IP addresses to workstations and laptops, and fixed IP addresses to other servers (based on MAC addresses). Only necessary full-time staff have access.

Part 6. "Gateway" server called rocky, configured as a router - see under Network

Task Description

In this project you need to consider the above scenario and:

Part 1. Design the internal network (including router) for the entire company.

Part 2. Implement the server portion of the network (i.e. adelaide, sydney, gladstone, bundaberg, darwin and rocky) within a virtual network.

Part 3. Test the network, demonstrating that the implementation meets the key requirements.

Part 4. Document the design, implementation and testing, submitting a report named cqunix-sysadmin-<student ID>.docx. Put your actual student ID in place of <student ID>.

Attachment:- Task Description.rar