Fablab Wageningen Computers and Infra: Difference between revisions

From NURDspace
No edit summary
Line 6: Line 6:
}}
}}
== What is this project? ==
== What is this project? ==
We are going to setup a network and some workstations for Fablab Wageningen. To keep things maintainable we've come up with various possible solutions from which the following seems the most practical.
We are going to setup a network and some workstations for Fablab Wageningen. To keep things maintainable we've come up with various possible solutions from which the following (Plan A) seems the most practical.
=== Overview ===
=== Plan A ===
*Plaatje, todo
*Plaatje, todo
The server hosts an image which is deployed at the workstations every night.
The server hosts an image which gets deployed to the workstations every night.
=== Server ===
 
==== Server ====
* RAID1
* RAID1
* 2 NICS, 1 to internet and 1 to internal network switch
* 2 NICS, 1 to internet and 1 to internal network switch
Line 16: Line 17:
* TFTPd
* TFTPd
* Something to do nightly deploys with, e.g. Clonezilla
* Something to do nightly deploys with, e.g. Clonezilla
* Scripting and a daily cron job at night


=== Clients ===
===== Other functionality =====
* Network disk for users
 
==== Clients ====
* Netboot enabled
* Netboot enabled
* Local harddisk which is big enough for the image
* Local harddisk which is big enough for the image


=== The Image ===
==== The Image ====
* One 'fablab' user
* One 'fablab' user
* Lots of applications preinstalled
* Lots of applications preinstalled
* Possible to modify without too much hassle (automatic updates?)
* Possible to modify without too much hassle (automatic updates?)
==== Daily cycle ====
===== At night =====
Workstations will boot (Wake on LAN), load software from the server which puts a fresh image on the local disk.
===== Outside nightly window =====
When workstations are turned on (by hand, typically somewhere during the day) they will load some simple script which tells them to boot from local disk.
==== Thing to find out first ====
* What distro do we chose for the clients?
* Is it possible to put the server in the rack?
=== Plan B ===
We just pre-install the workstations and do regular maintenance on them.
=== Plan C ===
We run a server and use our workstations as thin clients (citrix like scheme). Linux Server Terminal Project (http://www.ltsp.org/) or alike.

Revision as of 18:22, 17 March 2013

NURDspace Project
link=File:{{{Name}}}.jpg
Participants Dennis, Fwd
Skills
Status
Niche
Purpose
Tool
Location
Cost
Tool category

{{{Name}}}Property "Tool Name" (as page type) with input value "{{{Name}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:{{{Tool}}} | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:{{{Tool}}} | [[Tool Cost::{{{Cost}}} | }}

What is this project?

We are going to setup a network and some workstations for Fablab Wageningen. To keep things maintainable we've come up with various possible solutions from which the following (Plan A) seems the most practical.

Plan A

  • Plaatje, todo

The server hosts an image which gets deployed to the workstations every night.

Server

  • RAID1
  • 2 NICS, 1 to internet and 1 to internal network switch
  • DHCP server
  • TFTPd
  • Something to do nightly deploys with, e.g. Clonezilla
  • Scripting and a daily cron job at night
Other functionality
  • Network disk for users

Clients

  • Netboot enabled
  • Local harddisk which is big enough for the image

The Image

  • One 'fablab' user
  • Lots of applications preinstalled
  • Possible to modify without too much hassle (automatic updates?)

Daily cycle

At night

Workstations will boot (Wake on LAN), load software from the server which puts a fresh image on the local disk.

Outside nightly window

When workstations are turned on (by hand, typically somewhere during the day) they will load some simple script which tells them to boot from local disk.

Thing to find out first

  • What distro do we chose for the clients?
  • Is it possible to put the server in the rack?

Plan B

We just pre-install the workstations and do regular maintenance on them.

Plan C

We run a server and use our workstations as thin clients (citrix like scheme). Linux Server Terminal Project (http://www.ltsp.org/) or alike.