'''Working Draft!!!'''== Purpose ==
== Introduction ==In this assignment, you will use the '''335assign virtual network''' and the '''seedling''' cloning-source that you created in assignment 1 (part 1) to create two e-mail servers: a '''Mail Transfer Agent''' called '''pine''' and a ''Message Store'' (IMAP) called '''fir'''. You will also use the '''seedling''' cloning source to create a Samba server called '''bristlecone'''. 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 at least the '''balsam''' Master Name server in order to resolve domain names to IP addresses.
This course is a project course, and the majority of your mark will come from work on a Mozilla development project. The primary goal of this project is to get you involved in the Mozilla development community and codebase. Through this experience you will learn about the processes, tools, and practices involved in developing software as part of a large open source community.== General Requirements ==
== The Rules '''Weight''': 10% of Engagement ==the overall grade
Many of the practices inherent '''Due Date''': During Week 13 (in open source development will seem to go against the structures often set in place for similar course work. For example, you are typically forbidden to collaborate with your peers, to copy from the web, etc. However, these rules must be re-evaluated in the context of proper and pragmatic open source development practices.class)
First, consider the typical rules around cheating and plagiarism. In this assignment, you are encouraged to work within the set of best practices natural to open source development. Open source developers do not write from scratch what already exists and is freely available for use. You too should be thinking in terms or code reuse. It is ok for you to use code from other open source projects, so long as the license is amenable to the use.== Detailed Requirements ==
Second, consider the typical restrictions on peer-collaboration. In {{Admon/important|It is YOUR responsibility to Backup all of your VMs for this assignment, you Assignment!|You are encouraged required to frequently backup your VMs prior to exiting a work together, session during this assignment. Your instructor will NOT accept the fact that your hard disk crashed and lost all of your work. If you properly backed up your VM images and xml configuration files to help one anothera USB, then you can purchase a new hard-disk or wipe and recreate your hard disk and restore your VMs. Students who fail to look at each other's code, etc. Open source collaboration is about leveraging submit their assignment #2 by the collective knowledge last day of a community scheduled classes will receive an INC grade (assuming they passed all of the other requirements for this course) and will be required to help solve show their instructor their working assignment #2 no later than 4PM on the problems first Tuesday of the individualnext semester; otherwise, they will fail the course. Students with accommodations should discuss arrangements regarding due dates / submission of assignment #2. Students that are missing both of assignment #1 and assignment #2 will fail this course.}}<br /><br />
Third, consider the sharp dividing line between student projects in most programming courses. For the most part, you are being evaluated on your ability to do a particular project or to solve a particular problem. Your outcome is measured against your peers’. However, in this course you are not in competition with your peers; rather, you are all working on one large project === Set-up Mail Transfer Agent (i.e., Mozilla'''pine''') with many sub-projects within it. As a result, there is no clean line to divide your work from that of your peers, your work from that of the Mozilla community. This means that collaboration with each other and even with other members of the Mozilla community is acceptable practice.===
To summarizePerform the following steps for this section:
* Help each other, contribute #Create a clone virtual machine called '''pine''' from the '''seedling''' cloning-source. Refer to the table below for '''address''' and '''hostname'''.#The normal user on your host machine must be able to ssh to the root account on each other’s projectsmachine without being prompted for a password.* Work with and #Create a '''regular user''' for this virtual machine using '''your Seneca userID'''.#Any machine within the Mozilla community'''coniferous.trees.ops''' domain will be able to route outgoing email through this server.* Give others encouragement and credit when they help you#Any mail sent directly from this machine will use the domain as the sending address (i.e. user@coniferous.trees.ops)* Use existing open source code whenever possible#You are NOT required to encrypt received email messages.* Be open to helping others and to being helped#This machine will relay received email messages for any user account in the '''coniferous.trees.ops''' domain.
== Requirements = Set-up Mail Delivery Agent / Message Store ('''fir''') ===
* Pick a project from Perform the [[Project List]]. If you want to work on something else, speak to Dave.* Create a project page based on the stubs in [[Project List]]--see [[Sample Project]] following steps for an example. If someone has already created a page for a project you want to work on, speak to that person to see if you can join him/her. If s/he says yes, add your name to the Project Leader(s) section; otherwise pick another project and become a Contributor instead.* Become a Contributor for one or more other projects. This is something that will just happen as you interact on IRC or in class. As people need help, you can choose to get involved with things. For example: helping to debug something, doing research into a problem, writing some tricky code. Over time your list of contributions to other peoples’ projects should grow. Keep track of this in a personal page. * Keep your project page updated. Add technical information to the Project Details section as you get a better understanding of the problem, and keep track of your project status in the Project News section. You should be updating this page at least once every two weeks and more likely every week. Remember that the more you write on your page the easier it will be to get help from other people: it is easier for people to understand your question with supporting documentation on the web.* Create a personal page (title should be your full name) and link it to a) [[People]] and b) your project page. On this page keep track of your contributions to other projects and your reflections on your on project and the course.
== Intellectual Property ==#Create a clone virtual machine called '''fir''' from the '''seedling''' cloning-source. 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.#This machine will accept incoming email for any user account in the '''coniferous.trees.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 postifx'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 '''pine''' and '''fir''' servers.
Given Add MX records to the forward lookup zone on your balsam DNS server so that this course all incoming mail addressed to the domain is focused on open source developmentsent to your IMAP server ('''fir''') first, and given that we are working on real pieces of the Mozilla codebase, all student work will become open source. The particular license used will be determined based on the other parts of Mozilla with which you are interactingMTA ('''pine''') as a fall-back.
== Grading = Set-up a Samba Server ('''bristlecone''')===
# 60 Marks - Final Project Deliverables (e.g., code, documents)# 20 Marks - Project Wiki Page and Updates# 20 Marks - Contributions to Other ProjectsPerform the following steps for this section:
More detailed grading information #Create a clone virtual machine called '''bristlecone''' from the '''seedling''' cloning-source. Refer to the table below for '''address''' and '''hostname'''.#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''.#It will run '''Samba''' (automatically on boot) to share files with machines in this network. You may reuse the Windows installation from the lab or create a new one for the assignment.#Create five <u>new</u> users on the Samba file server, call them '''yoursenecaid-1''', '''yoursenecaid-2''', '''yoursenecaid-3''', '''yoursenecaid-4''', '''yoursenecaid-admin'''. (replace "yoursenecaid" with your <u>actual</u> Seneca ID)#Create a directory /documents with the following subdirectories:<pre style="font-size: 14pt;margin-left:30px;">.├── private│ ├── yoursenecaid-1│ ├── yoursenecaid-2│ ├── yoursenecaid-3│ ├── yoursenecaid-4│ └── yoursenecaid-admin└── shared ├── readonly └── readwrite</pre><ol><li value="6">Set up permissions/ownership on those directories for your Linux users on the file server so that:<ol type="a"><li>'''yoursenecaid-1''' through '''yoursenecaid-4''' have '''read/write''' access to their own <u>private</u> directories.</li><li>'''yoursenecaid-admin''' has '''read/write''' access to <u>every</u> directory.</li><li>Everyone has '''read''' access to the '''readonly''' directory (but only the '''admin''' has '''write''' access too).</li><li>Everyone can both '''read''' and '''write''' to the '''readwrite''' directory.</li></ol></li><li>Set up '''five''' Samba users to mirror your new Linux users.</li><li>Configure '''seven''' shares (one for each directory above) with permissions as close as possible to the Linux permissions.</li></ol> === Set-up Windows Client to Test Samba server ('''windows''')=== Perform the following steps for this section: #Create a clone virtual machine called '''client''' from the '''seedling''' cloning-source. Refer to the table below for '''address''' and '''hostname'''.#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''.#The normal 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 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. === Network Configuration === As you will now have functioning primary and secondary DNS servers, modify your network configuration file for the '''pine''', '''fir''', and '''bristlecone''' servers specify the correct IPADDR. === Table of Virtual Machines / DNS Records === Below is network configuration for ALL virtual machines used in this assignment and previous assignments for this course: {| class="wikitable" | style="margin-left:0px;"! Hostname !! Address !! Purpose|-style="background-color:#66cccc;"| '''larch.coniferous.trees.ops''' (your existing host) || External Facing Address:''' DHCP assigned'''<br>Internal Virtual Bridge (virbr1):''' 172.30.20.1''' || Your '''host''' machine |-style="background-color:#66cccc;"| '''seedling.coniferous.trees.ops''' || '''172.30.20.100''' || '''Cloning-source''' used to create other servers for other assignments.|-style="background-color:#66cccc;"| '''balsam.coniferous.trees.ops''' || ''' 172.30.20.2''' || '''Master''' Name Server |-style="background-color:#66cccc;"| '''spruce.coniferous.trees.ops''' || '''172.30.20.3''' || '''Slave''' Name Server|- style="background-color:#66cccc;"| '''pine.coniferous.trees.ops''' || ''' 172.30.20.5''' || '''SMTP''' mail Server |- style="background-color:#66cccc;"| '''fir.coniferous.trees.ops''' || '''172.30.20.6''' || '''IMAP''' mail Server|- style="background-color:#66cccc;"|'''bristlecone.coniferous.trees.ops''' || '''172.30.20.8''' || '''Samba''' Server |- style="background-color:#66cccc;"| '''windows.coniferous.trees.ops''' || '''172.30.20.10''' || Client Linux or Windows Server |} ===Set-up Firewall Policies=== In addition to the basic firewall established in assignment 1, ensure the following restrictions are met: #All virtual machines will use iptables as their firewall.#Outgoing traffic is allowed. #Each virtual machine must be relesed later able to check for and install updates using yum.#Traffic on the loopback interface for each virtual machine is allowed.#The host machine (and only the host machine) must be able to ssh to them.#ICMP traffic is allowed if it originated within the local network only. #Other than that, only the traffic necessary to support their roles described above should be allowed. == Assignment Submission == The student is required to prove to their professor that their set-up works correctly during the regularly-scheduled lab period. ===Assignment Evaluation Details=== *'''Demonstrate working assignment to your instructor in class:'''<ol type="a"><li>Students need to demonstrate their assignment functionality to their professor during a lab period<br>(like you would for any lab for "sign-off").</li><li>Students are required to prepare everything ahead of time so that you can quickly demonstrate to your instructor that all required parts of your assignment are working.</li><li>Do do proceed to the semesternext step until you have demonstrated your assignment to your instructor to check for errors that may cause problems when running the checking script.<br><br></li></ol> *Download and run a shell script to check your work (Depending on your OPS335 Instructor): ::'''Peter Callaghan's Classes (Sections C & D):'''<ul><li>Refer to instruction on Moodle to download and run marking shell script.</li></ul> ::'''Murray Saul's Classes (Sections A & B):'''<ol><li>Login as '''root''' on your '''host''' machine.</li><li>Change to the '''/root/bin''' directory.</li><li>Make certain that at least your '''balsam''', '''pine''', '''fir''', '''bristlecone''' and '''client''' virtual machines are running.<li>Issue the command to download a checking script for your assignment to your '''host''' machine: <source>wget http://matrix.senecac.on.ca/~murray.saul/ops335/check-assn2.bash # Currently not available</source></li><li>Set execute permissions and run the command: '''/root/bin/check-assn2.bash'''<br>(You shell script contents will be mailed to your Seneca email and to your OPS335 instructor's Seneca email. If you do '''NOT''' receive an e-mail message in your Seneca email account, then there is a problem, and you '''MUST''' rerun or contact your OPS335 instructor immediately.<br><br></li></ol>*'''Additional Assignment Information:'''<ol type="a"><li>This assignment is to be completed individually. '''Group submissions are not allowed'''.</li><li>You are NOT allowed to use local hostname resolution (i.e. no entries in your '''/etc/hosts''' file).<li>Test your machine to make sure it works. If a machine is not accessible (e.g. will not boot, can not be accessed through ssh from your host, etc.), or is otherwise non-functional, you may be told to '''resubmit'''.</li><li>'''Late submissions are a subject to a penalty of 10% per day'''.</li><ol> ==Evaluation Rubric== Here is an evaluation rubric (in table form) showing you how you will be evaluated for this assignment.Part of the rubric is marked from professor observation from student demonstration of assignment in class, and the other part is based on output from the results of an assignment checking script that the student will download and run. {| class="wikitable" width=60%|-| colspan=2 style="text-align:center;background-color:#cccccc;" |'''Student Demonstration (in class)'''|-| style="font-weight:bold" | Evaluation Item | width=10% style="text-align:right;font-weight:bold" | Mark|-| colspan="2" | ::'''STMP and IMAP Servers:'''|-| :::Proof of SMTP Server Running on '''pine''' server| style="text-align:right" | /1|-| :::E-mails sent from '''pine''' and '''bristlecone''' servers to '''fir''' server (user@IP_ADDR)| style="text-align:right" | /1|-| :::E-mails sent from '''pine''' and '''bristlecone''' servers to '''fir''' server (user@DOMAIN_NAME)| style="text-align:right" | /1|-| colspan="2" | ::'''Samba Server Access via Windows OS:'''|-| :::'''yoursenecaid-1''' through '''yoursenecaid-4''' has '''read/write''' access| style="text-align:right" | /1|-| :::'''yoursenecaid-admin''' has '''read/write''' access to every directory| style="text-align:right" | /1|-| :::All accounts have '''read''' access to the '''read-only''' directory<br>(but only '''yoursenecaid-admin'' has '''write''' access)| style="text-align:right" | /1|-| :::All accounts can both '''read''' and '''write''' to the '''readwrite''' directory.| style="text-align:right" | /1|-| colspan=2 style="text-align:center;background-color:#cccccc;" |'''Configuration (Checking Script Output)'''|-| style="font-weight:bold;" | Evaluation Item | width=10% style="text-align:right;font-weight:bold" | Mark|-| colspan=2 | '''Mail Transfer Agent (pine) - General Configuration'''|-| :::Postfix MTA settings| style="text-align:right" | /5|-| colspan=2 | '''Mail Delivery Agent (MTA) / Message Store (MS) - General Configuration'''|-| :::Postfix MTA settings| style="text-align:right" | /3|-| :::LDA settings| style="text-align:right" | /1|-| :::AA settings| style="text-align:right" | /4|-| colspan=2 | '''DNS configuration'''|-| :::Correct MX records exist| style="text-align:right" | /2|-| :::MX records prioritize access to mail servers correctly| style="text-align:right" | /2 |-| colspan=2 | '''Samba Server - General Configuration'''|-| :::Directories shared with correct permissions| style="text-align:right" | /7|-| :::Samba accounts created (1/2 mark each)| style="text-align:right" | /2|-| :::Writing allowed to directories| style="text-align:right" | /1|-| colspan=2 | '''Firewall policies'''|-| :::MTAs allow SMTP traffic| style="text-align:right" | /2|-| :::AA allows IMAP traffic| style="text-align:right" | /1|-| :::IMAP traffic limited to local network| style="text-align:right" | /1|-| :::Samba server allows samba traffic| style="text-align:right" | /1|-| :::Samba traffic limited to local network| style="text-align:right" | /1|- |'''Less Deductions (half-mark for EACH VM)::*'''DOMAIN Name''' NOT Resolved:*'''VM hostname''' NOT set:*firewalld '''enabled''' / '''running''':*iptables '''disabled''' / '''not running''':*No '''Yum update''':*'''Services''' NOT active:*Local hostname resolution appears in '''/etc/hosts''' (1 mark per entry, per vm):*Neglecting major safeguards (e.g.no firewall present, firewall allowing all traffic, no active SELinux) ('''4 marks per issue''')| |-| '''TOTAL''' | style="text-align:right" | '''/40'''|}