[ Home ] [ Project Proposal ] [ Project Definition ] [ Notices ] [ Caligula Documentation ] [ FAQ ]
Project Scope
It is the intention of the project team to construct and configure a fully
functional UNIX-based network server. This server will be configured with the intention of
replacing the current UNIX server (Tiberius) in Lab H408. A secondary goal of the project
team is to document our progress towards the objective.
The transfer of data, such as student accounts, presently residing on
Tiberius is not within the scope of the project. Our goal is rather to properly configure
Caligula as an account server, and provide a recommendation for replacement based on an
evaluation of performance and reliability.
Starting Points, Milestones & Deliverables
There are four clearly identifiable summary tasks within Project Caligula, each with
its own starting point, and a deliverable outcome at its conclusion. Deliverables within
each summary task will also indicate the progress of Project Caligula. Each deliverable
will be reflected with a new posting in the Documentation
area of this website. Each milestone, resulting from the conclusion of a particular
phase of the project, will also result in a new document posted to the website. It is the
team's intention to conduct a status report meeting with our project supervisor and/or
client as each summary task concludes. Click here to
see a complete listing of tasks, and Project Caligula's Gantt Chart.
Project Caligula's starting points, deliverables, and milestones are explained below:
Summary Task: Project Preparation ( Task ID #1)
Starting Point:
This is the starting point for the entire project. Having gained approval to proceed
with Project Caligula, the first task is to determine the operational status of the server
hardware, and to decide upon an operating system.
Deliverables:
Hardware List:
A report listing the operational status of the components of Caligula, as well as
technical data related to each piece of equipment.
Configuration Plan:
This will document the proposed configuration of the server, including operating system
and utilities to be installed, planned drive partitions and RAID level. This will
also be considered a milestone.
Summary Task: Automated Services (Task ID #11)
Starting Point:
This summary task will be undertaken concurrently with Project Prep and Installation
& Configuration. The team will begin by searching the internet for scripts that
will automate much of the 'housekeeping' duties involved in server administration. Where
needed, scripts will be written by the team members to provide such services.
Deliverables:
Sample Scripts:
Published examples of the routines the team intends to write to automate network
services.
Planned Simulated Network Service:
A report detailing the environment and processes intended to test the server under
network conditions. A progress report is essential at this point in the project.
Summary Task: Installation & Configuration (Task ID #17)
Starting Point:
The next phase of the project begins with the installation of an operating system.
Deliverables:
Hardware Bench-test:
After a burn-in period, the robustness of the hardware will evaluated and documented.
Configuration Records:
This report is intended to document the process of installing and configuring network
services in the UNIX environment. Hopefully, it can serve as a guide to others who will
follow in Team Caligula's path. Also considered a milestone.
Summary Task: Proofing (Task ID #26)
Starting Point:
When the project team feels that Caligula is ready to act as a network server, it will
be tested under network operating conditions. The conditions of operations having been set
out as the deliverable element of summary task #11
Deliverables:
Test Results:
Statistics regarding network traffic & demand for services.
Recommendation Report:
The ultimate goal of Project Caligula. The team will deliver a recommendation for the
implementation of Caligula as a replacement for the present server Tiberius.
Budget
Project Caligula requires a modest budget. As the hardware has been donated by AMOCO
Resources Canada Ltd., and spare parts DO exist, little expense is foreseen in the
completion of the project. A preliminary inspection of the hardware indicates the
following parts may need to be purchased:
- One Wide - SCSI HVD interface cable - approximate cost: $120.00 Cdn.
- One Wide - SCSI passive termination device - approximate cost $100.00 Cdn.
Personnel costs for Project Caligula will be calculated using the following format:
2 team members @ $20.00/day for 70 days = $2800.00
Click here for a table tracking Project Caligula's baseline
costs.
Required Resources
The success of Project Caligula depends upon the availabilty of the following
resources, supplied by SAIT:
Access to the pool of parts, donated by AMOCO Resources Canada Ltd, and distributed
throughout various departments within SAIT. Access may be required for the duration of the
project.
The project team will require access to Lab H408 beginning October 25th, 2000, until
the scheduled conclusion of Project Caligula (December 6th, 2000). The Lab's internal
network is required to construct a self-contained network for testing purposes.
