1,885
edits
Changes
no edit summary
[[Category:CDOT]]{{Admon/obsolete}}These machines are in the CDOT area on the first floor of the TEL building.
= Ground Rules =
# Take responsibility for your actions.
# Don't blow up other people's stuff.
# Don't count on Expect other people not blowing to blow up your stuff.
# Don't turn these machines off.
# Before rebooting, check with the other logged-in users, and check on #seneca on IRCon both Freenode and Moznet.
# Work under your own account, using root as sparingly as possible. If you need additional accounts, create them, but put your name in the comment (GCOS) field.
# Don't create public services.
# '''These machines are never backed up. Backup your own stuff, frequently.'''
= IP Information =
Contact a CDOT faculty member or administrative support person for information on IP addresses.
= Disk Space =
Keep an eye on disk space -- both your own usage and the free space on the machine. Delete stuff you don't need (especially temp files and build debris).
Many of the CDOT Linux machines have unassigned storage within their volume group. If you need additional space in a filesystem and know how to use LVM safely, feel free to allocate additional space as needed, but do not assign more space than required for your work (it's easier to add space to a filesystem than to remove it to add it to another filesystem). '''If you do not know how to administer LVM safely, ask an experienced user to add space to the filesystem for you -- it's very easy to destroy a filesystem.''' Please experiment with and learn about LVM on your own systems or in a virtual machine.
= Virtual Machines =
Please feel free to configure KVM virtual machines on the PCs. Because virtualization technologies conflict, please discuss the use of other hypervisors before deploying them.
When using virtual machines, please:
* Shutdown the VM when not in use
<!-- = Connectivity Status =
The connectivity of the systems is tested every 5 minutes using ICMP echo (ping) and may be viewed on the [http://liberia.cdot.proximity.on.ca/uptime/ CDOT Development System Status] page.
######### Disabled 2010-05-03 - Liberia's installation has disabled the connectivity status display. ############
-->
= Machine names, IPs, and Status =
'''Tip:'''
search whatever.was.already.here.com '''cdot.proximity.on.ca'''
To configure this on a Linux/Unix/OSX system for which you do not have administrative rights, use the LOCALDOMAIN environment variable. For example, you could add this line to your <code>~/.bash_profile</code> or <code>~/.profile</code>:
export LOCALDOMAIN="cdot.proximity.on.ca senecac.on.ca senecacollege.ca"
Alternately, you can append the machine names and IPs to the '''hosts''' file (<code>/etc/hosts</code> on Linux and Mac OSX, <code>c:\windows\system32\drivers\etc\hosts</code> on Windows) -- do not delete the existing contents of that file, just add this text:
# CDOT host file - from http://zenit.senecac.on.ca/wiki/index.php?title=CDOT_Development_Systems - 2009.01.17 28 version: 142.204.133.24 7 canada 142.204.133.22 scotland 142.204.133.152 australia 142.204.133.34 25 russia 142.204.133.153 canadaireland 142.204.133.28 india 142.204.133.150 hongkong 142.204.133.36 china 142.204.133.121 easterisland
142.204.133.122 spain
142.204.133.123 liberia
142.204.133.124 newzealand
After doing this, you can access the machines by name: <code>ssh '''userid'''@liberia</code>
<!-- = CDOTnet =
A gigabit ethernet LAN connects the PCs in the south end of CDOT (Australia, India, China, Ireland, and Scotland). The IP addresses on this LAN are 172.30.30.''X'', where ''X'' is the same last octet as the machine's external interface. These machines have DNS entries within the cdot.proximity.on.ca subdomain which are the same as the hostname with "2" appended (e.g., india2.cdot.proximity.on.ca refers to the CDOTnet interface on the host "india").
CDOTnet has no external interface and is therefore only useful for communication between the machines directly connected to it.
### CDOTNet is no longer connected ###
-->
= Equipment =
* Four PCs - quad-core, 8GB RAM, 1TB disk
* Four PCs - quad-core, 4GB RAM, 500GB disk, dual 22" displays on each
* One PC - quad-core, 8GB RAM, 6*1.5TB disk
* Two Mac Minis - dual-core, 2GB RAM, 120GB disk + external drive, 24" displays
* On the 64-bit PCs:
** Install the current version of Fedora as the base OS
** Install Use virtual machines for(KVM) as necessary:*** Linux (Fedora or other)
*** Windows Vista
*** Windows XP SP3
* Some PCs will have Windows XP/Vista installed as the base OS (for high-performance video access, i.e., Canvas3D):** NewZealand
* Install the toolchain(s) required (e.g., for Mozilla development - [http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites Win]/[http://developer.mozilla.org/en/docs/Linux_Build_Prerequisites Linux]/[http://developer.mozilla.org/en/docs/Mac_OS_X_Build_Prerequisites Mac])
* 50 GB /var filesystem
* 8 GB swap filesystem
==2x2TB Drives==
*Drive 1
** Partition 1: 500M /boot
** Partition 2: 500G PV
** Partition 3: 500G PV
** Partition 4: 500G PV
** Partition 5: 500G PV
* Drive 2
** Partition 1: 500G PV
** Partition 2: 500G PV
** Partition 3: 500G PV
** Partition 4: 500G PV
'''Initial Linux LVM LV layout:'''
* 100G / ext4
* 1T /home ext4
= Software to be installed =
* Build tools required for Mozilla build ([http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites Win]/[http://developer.mozilla.org/en/docs/Linux_Build_Prerequisites Linux]/[http://developer.mozilla.org/en/docs/Mac_OS_X_Build_Prerequisites Mac]). NOTE: use VS.NET Pro on Win32 vs. Express
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] on WinXP/Vista
* Current version of FF2 FF and TB
=== Mac installed software ===