evangelism
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| evangelism [2013/10/12 20:02] – Text replace - "<div style="width:55%;margin:0 auto;border:2px solid;border-left:20px solid;border-color:#d9534f;text-align:center;padding:5px;font-weight:bold;">This page is out of date and needs rewriting.<br /> _hayden | evangelism [2026/09/29 05:35] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{OODNotice}} | ||
| - | |||
| - | |||
| - | |||
| - | ====== Draft Case ====== | ||
| - | |||
| - | |||
| - | |||
| - | ===== An overview of the project ===== | ||
| - | |||
| - | Instituted in 1987, the TARDIS Project is a student-operated computing facility, hosted by the Informatics Department at the University of Edinburgh. | ||
| - | |||
| - | The project provides free web hosting, e-mail accounts, mailing lists and other services to registered students and staff from the University. | ||
| - | |||
| - | |||
| - | ===== Our aims ===== | ||
| - | |||
| - | While we place great importance on the uninterrupted provision of service to our users, this in itself is only one goal of the project. | ||
| - | |||
| - | Students interested in system administration are welcomed and can join the discussion and development of the project, and those with some existing experience - though perhaps only in small-scale system administration - are able to work with a real, live computing facility with a large user base. | ||
| - | |||
| - | |||
| - | ===== Our requirements ===== | ||
| - | |||
| - | To assist recruitment of new members and day-to-day maintenance, | ||
| - | |||
| - | |||
| - | ===== Pros ===== | ||
| - | |||
| - | |||
| - | * Tardis used to provide training/ | ||
| - | This is a big point. We did have regular attendees and figures showing how many people came along. It | ||
| - | provides both experience to students for improving presentation skills, and demonstrates an enthusiasm | ||
| - | for people to learn off their own backs. | ||
| - | * We can provide a safe (Xen) introduction to new sys admins | ||
| - | * We provide a realistic environment for system administration with large numbers of users and large volumes of data | ||
| - | * We provide a realistic environment for learning and experimenting with real-world network technologies | ||
| - | * Skills users and admins can gain are not generally taught in Informatics courses, since they' | ||
| - | * We provide useful services for students (though people might potentially think it's wrong if these are provided long-term?) | ||
| - | * We provide useful services for societies with sys-admin capable members | ||
| - | * We have hardware such as the Cisco kit, the Suns, the Intel Xeon box and the rack, which students will not have access to elsewhere. | ||
| - | * A /24 | ||
| - | |||
| - | Tardis exists to: | ||
| - | |||
| - | * Gather and promote system administration talent in Informatics | ||
| - | * Help the effective use and management of computer technology amongst University societies | ||
| - | * Provide an environment for discussion regarding sysadmin technologies (established and new) | ||
| - | |||
| - | Probably would be worth pointing out: | ||
| - | * That people have blagged jobs through Tardis contacts or Timelords or something. | ||
| - | * Timelord types make good contacts in general (or at least, Steve likes to give us hardware). | ||
| - | * That people feel they' | ||
| - | * That we have a quite surprising number of active users and societies using us (quite potentially 3 figures) | ||
| - | * People have used our services and environment to do their projects/ | ||
| - | |||
| - | |||
| - | ===== Cons ===== | ||
| - | |||
| - | |||
| - | Counter arguements against tardis which we would expect to be presented with. If possible, a sensible rubuke to each argument would help in defending tardis' | ||
| - | |||
| - | * People have linux systems at home these days, they don't need tardis | ||
| - | |||
| - | Administering home-user linux systems is incomparable to running a shared multi-user installation | ||
| - | |||
| - | * Why can't tardis just use a mesh network/ | ||
| - | |||
| - | A mesh network does not represent any real world situation and suffers a number of drawbacks. Whilst such a deployment would be of interest in its own right, it does not cover the situation which tardis provides. | ||
| - | |||
| - | Project members have dabbled in such networking projects in the past, but have found they get easily neglected. | ||
| - | |||
| - | * People have suitable resources from the university, why do they need tardis? | ||
| - | |||
| - | The university runs all their own systems. The act of running the systems is kept transparent to the students who do not appreciate the amount of work which goes in to maintaining those systems or some of the complex challenges faced in this process. | ||
| - | |||
| - | |||
| - | ===== Requirements ===== | ||
| - | |||
| - | |||
| - | What do we really require? | ||
| - | |||
| - | * Xen hosts (how many?) | ||
| - | * What physical hardware currently exists to provide this | ||
| - | * Could an exchange be made, reducing space if additional hardware can be provided? | ||
| - | * Networking equipment | ||
| - | |||
| - | What would help us: | ||
| - | |||
| - | * A small amount of space (one rack) in an inf-student-accessible location | ||
| - | |||
| - | What we require, worst-case: | ||
| - | |||
| - | * A machine with network access, or funding for colo elsewhere | ||
| - | |||
| - | What we need to do: | ||
| - | |||
| - | * Get more people interested (ESSENTIAL!) | ||
| - | * Reduce our heat output and footprint | ||
| - | |||
| - | |||
evangelism.1381608173.txt.gz · Last modified: (external edit)
