http://wiki.freegeek.org/api.php?action=feedcontributions&user=Vagrant&feedformat=atomFreekiWiki - User contributions [en]2024-03-29T13:19:47ZUser contributionsMediaWiki 1.35.1http://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=68936Technical infrastructure checklist2013-10-24T19:27:51Z<p>Vagrant: /* Software and Systems */ updated expiration date.</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https (Sep 1st, 2016) and imaps/smtps (Sep 23rd, 2016) ssl certs<br />
*** openssl x509 -noout -text -in /path/to/FOO.crt<br />
** check apt signing key (expires February 1st, 2015; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (at least monthly, log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=68717Technical infrastructure checklist2013-10-03T18:00:26Z<p>Vagrant: /* Software and Systems */ updated ssl cert info</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https (Sep 1st, 2016) and imaps/smtps (Dec 28th, 2013) ssl certs<br />
*** openssl x509 -noout -text -in /path/to/FOO.crt<br />
** check apt signing key (expires February 1st, 2015; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (at least monthly, log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=67918Technical infrastructure checklist2013-07-11T20:25:45Z<p>Vagrant: /* Software and Systems */ updated apt signing key</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https (Feb 2nd, 2014) and imaps/smtps (Dec 28th, 2013) ssl certs<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires February 1st, 2015; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (at least monthly, log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=67330Technical infrastructure checklist2013-05-09T18:48:09Z<p>Vagrant: /* Software and Systems */ update ssl cert expiry</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https (Feb 2nd, 2014) and imaps/smtps (Dec 28th, 2013) ssl certs<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (at least monthly, log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=66317Technical infrastructure checklist2013-02-21T20:01:49Z<p>Vagrant: /* Servers & Security */ document frequency of cc network check.</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (at least monthly, log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=66316Technical infrastructure checklist2013-02-21T19:14:16Z<p>Vagrant: /* Software and Systems */ clarify what should be done with apt signing key</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014; Update 6 months before expiration)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Free_Geek_Email&diff=65581Free Geek Email2012-12-18T21:42:54Z<p>Vagrant: /* Misc. */ updated password changing documentation</p>
<hr />
<div>There are three different interfaces that can be used to access your Free Geek email: POP3, IMAP, and Squirrelmail. Each of them has its advantages and disadvantages.<br />
<br />
== Squirrelmail ==<br />
<br />
'''Squirrelmail''' is probably the easiest way to access your email, since it involves only a web browser and can be used from any location.<br />
<br />
Go to https://mail.freegeek.org and enter your username (whoyouis) '''or''' email address (whoyouis@freegeek.org) in the Name field and your email password in the Password field.<br />
<br />
== Client based email ==<br />
Use the following settings to connect from an email client such as Evolution or Thunderbird. The server port is included below for clarity, but is usually automatically set when you choose the encryption type.<br />
<br />
===Receiving email===<br />
==== IMAP ====<br />
<br />
IMAP allows you to access your email from anywhere and leave the email on a server, but requires a separate email program. Most email programs (even windows ones) can handle IMAP. The main disadvantage of IMAP (and webmail) <del>is</del> was that the messages are inaccessible when you are offline. Any decent modern mail client has an option to sync mail locally so this is no longer a real problem. (Fun Fact:Squirrel Mail users IMAP behind the scenes).<br />
<br />
*Protocol - IMAP<br />
*Server - mail.freegeek.org<br />
*username - the first part of your email before the @ symbol.<br />
*server port - 993<br />
*Encryption - SSL<br />
*Authentication - Plain Text<br />
<br />
==== POP3 ====<br />
The "old traditional" email system. POP downloads the email to your machine, making it inaccessible from other locations unless you choose to leave a copy of the email on the server (which does not always work well with all clients). There is no reason to use it and you should not do so. "I've always used it" is not a reason, never mind a good one. Use IMAP instead, and sync your mail locally.<br />
<br />
*Protocol - POP3<br />
*Server - mail.freegeek.org<br />
*username - the first part of your email before the @ symbol.<br />
*server port - 995<br />
*Encryption - SSL<br />
*Authentication - Plain Text<br />
<br />
=== Sending mail ===<br />
==== Inside the Free Geek network (plugged into the wired network) ====<br />
'''NOTE:''' Wireless access, even when you're physically at Free Geek, is actually "outside" the network. So for wireless access, see the next section instead.<br />
<br />
*Protocol - SMTP<br />
*Server - mail.freegeek.org<br />
*Server port - 25<br />
*Encryption - none<br />
*Authentication - none<br />
<br />
==== Outside the Free Geek network (or on FG wireless) ====<br />
Our SMTP server (mail.freegeek.org) is an authenticating SMTP server, this means you can send email from anywhere as log as you log in first. This works inside the network as well. You don't need to do anything special to login as your email program will take care of it as long as you give the correct username and password. N.B. this differs form the one you use to read your email. It needs the @freegeek.org part as well.<br />
<br />
*Protocol - SMTP<br />
*Server - mail.freegeek.org<br />
*username - username@freegeek.org<br />
*Server port - 465<br />
*Encryption - SSL<br />
*Authentication - Plain Text<br />
<br />
'''NOTES:''' <br />
<br />
You may receive a "greylisting" error message when sending to a freegeek address, even with your smtp server set to mail.freegeek.org. If this happens, just resend the message after 5 minutes have passed.<br />
<br />
If you go to a location that blocks outgoing SMTP, you may not be able to send email from a mail client, though using authenticated SMTP over SSL generally still works. In these cases, you man use the Squirrelmail web interface to send mail.<br />
<br />
== Misc. ==<br />
<br />
'''To change your password''', use the web interface:<br />
<br />
[https://mail.freegeek.org/password Email Password Change Web Interface]<br />
<br />
Or if that doesn't work, contact [[Technocrats]].<br />
<br />
'''your address plus''' - mail addressed to "whoyouis+stuff@freegeek.org" will get delivered just the same as mail to "whoyouis@freegeek.org". You might use this feature to give different addresses to different sign-up services. Note: You must use a "+" sign. More information on this can be found at the Wikipedia article [[wikipedia:E-mail address#Plus (or Minus) addressing]].<br />
<br />
<br />
[[Category:Tech support]]<br />
[[Category:howto]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Freegeek_repository&diff=65031Freegeek repository2012-11-14T21:18:58Z<p>Vagrant: encourage cutting and pasting.</p>
<hr />
<div>For systems installed via liveCD or other means you'll need to manually add the freegeek repository and keyring in order to install freegeek-extras<br />
<br />
==From the GUI==<br />
# Go to '''System >> Administration >> Software Sources'''<br />
# Select the '''Other Software''' tab<br />
# Click '''Add''' and type the following: <code>deb http://apt.freegeek.org/ubuntu lucid main</code><br />
# Add the Free Geek keyring <br />
#* Download the keyring from <code>http://apt.freegeek.org/freegeek-archive-keyring.gpg</code><br />
#* In the Software Sources window, click on the '''Authentication''' and add the keyring file<br />
# Go to '''Applications >> Ubuntu Software Center''' and search for ''freegeek-extras'' and install it<br />
# Go to '''System >> Administration >> Update Manager''' and click '''Check''', then '''Install Updates'''<br />
<br />
==From the CLI==<br />
Enter the following into a terminal (cut-and-paste for accuracy!):<br />
sudo su -c 'echo "deb http://apt.freegeek.org/ubuntu lucid main" >> /etc/apt/sources.list.d/fg.list'<br />
sudo wget http://apt.freegeek.org/freegeek-archive-keyring.gpg<br />
sudo apt-key add freegeek-archive-keyring.gpg<br />
sudo apt-get update <br />
sudo apt-get install freegeek-extras<br />
sudo apt-get upgrade<br />
<br />
[[Category:Tech support]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Freegeek_repository&diff=65030Freegeek repository2012-11-14T21:18:05Z<p>Vagrant: remove the $, so that it really can be cut-and-pasted.</p>
<hr />
<div>For systems installed via liveCD or other means you'll need to manually add the freegeek repository and keyring in order to install freegeek-extras<br />
<br />
==From the GUI==<br />
# Go to '''System >> Administration >> Software Sources'''<br />
# Select the '''Other Software''' tab<br />
# Click '''Add''' and type the following: <code>deb http://apt.freegeek.org/ubuntu lucid main</code><br />
# Add the Free Geek keyring <br />
#* Download the keyring from <code>http://apt.freegeek.org/freegeek-archive-keyring.gpg</code><br />
#* In the Software Sources window, click on the '''Authentication''' and add the keyring file<br />
# Go to '''Applications >> Ubuntu Software Center''' and search for ''freegeek-extras'' and install it<br />
# Go to '''System >> Administration >> Update Manager''' and click '''Check''', then '''Install Updates'''<br />
<br />
==From the CLI==<br />
Enter the following into a terminal:<br />
sudo su -c 'echo "deb http://apt.freegeek.org/ubuntu lucid main" >> /etc/apt/sources.list.d/fg.list'<br />
sudo wget http://apt.freegeek.org/freegeek-archive-keyring.gpg<br />
sudo apt-key add freegeek-archive-keyring.gpg<br />
sudo apt-get update <br />
sudo apt-get install freegeek-extras<br />
sudo apt-get upgrade<br />
<br />
[[Category:Tech support]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Freegeek_repository&diff=65029Freegeek repository2012-11-14T21:14:48Z<p>Vagrant: /* From the CLI */ fix instructions to be runnable from a script, or blindly cut-and-pasted.</p>
<hr />
<div>For systems installed via liveCD or other means you'll need to manually add the freegeek repository and keyring in order to install freegeek-extras<br />
<br />
==From the GUI==<br />
# Go to '''System >> Administration >> Software Sources'''<br />
# Select the '''Other Software''' tab<br />
# Click '''Add''' and type the following: <code>deb http://apt.freegeek.org/ubuntu lucid main</code><br />
# Add the Free Geek keyring <br />
#* Download the keyring from <code>http://apt.freegeek.org/freegeek-archive-keyring.gpg</code><br />
#* In the Software Sources window, click on the '''Authentication''' and add the keyring file<br />
# Go to '''Applications >> Ubuntu Software Center''' and search for ''freegeek-extras'' and install it<br />
# Go to '''System >> Administration >> Update Manager''' and click '''Check''', then '''Install Updates'''<br />
<br />
==From the CLI==<br />
Enter the following into a terminal:<br />
$ sudo su -c 'echo "deb http://apt.freegeek.org/ubuntu lucid main" >> /etc/apt/sources.list.d/fg.list'<br />
$ sudo wget http://apt.freegeek.org/freegeek-archive-keyring.gpg<br />
$ sudo apt-key add freegeek-archive-keyring.gpg<br />
$ sudo apt-get update <br />
$ sudo apt-get install freegeek-extras<br />
$ sudo apt-get upgrade<br />
<br />
[[Category:Tech support]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Freegeek_repository&diff=65026Freegeek repository2012-11-14T19:27:47Z<p>Vagrant: /* From the CLI */ updated instructions to remove deb-src, which is useless, and also remove complicated HEREDOC redirection</p>
<hr />
<div>For systems installed via liveCD or other means you'll need to manually add the freegeek repository and keyring in order to install freegeek-extras<br />
<br />
==From the GUI==<br />
# Go to '''System >> Administration >> Software Sources'''<br />
# Select the '''Other Software''' tab<br />
# Click '''Add''' and type the following: <code>deb http://apt.freegeek.org/ubuntu lucid main</code><br />
# Add the Free Geek keyring <br />
#* Download the keyring from <code>http://apt.freegeek.org/freegeek-archive-keyring.gpg</code><br />
#* In the Software Sources window, click on the '''Authentication''' and add the keyring file<br />
# Go to '''Applications >> Ubuntu Software Center''' and search for ''freegeek-extras'' and install it<br />
# Go to '''System >> Administration >> Update Manager''' and click '''Check''', then '''Install Updates'''<br />
<br />
==From the CLI==<br />
Enter the following into a terminal:<br />
$ sudo su<br />
# echo 'deb http://apt.freegeek.org/ubuntu lucid main' >> /etc/apt/sources.list.d/fg.list<br />
# wget http://apt.freegeek.org/freegeek-archive-keyring.gpg<br />
# apt-key add freegeek-archive-keyring.gpg<br />
# apt-get update <br />
# apt-get install freegeek-extras<br />
# apt-get upgrade<br />
<br />
[[Category:Tech support]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=64841Do we want it for a server?2012-10-30T21:58:21Z<p>Vagrant: dropped dell-specific questions</p>
<hr />
<div>this chart is meant to help instructors determine if systems should be recycled or sent to server build.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\nwe do not want it for a server\npull all hard drives\nsend to recycling, and\nmark it on the clipboard\nin the server section", shape="box", style="bold"]<br />
yes [label="YES\nwe want it for a server\nplace a Hard Drive Removed sticker\non it and take to server build", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
judge_no [label="Use your best judgement,\nbut we probably do not want it", shape="box", style="bold"]<br />
judge_yes [label="Use your best judgement,\nbut we probably want it", shape="box", style="bold"] <br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR2, DDR3 or DDR4 ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2"]<br />
sticker -> ddr [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> ddr [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> rackmount [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> sata [label="NO"]<br />
<br />
ddr -> pcie [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> judge_yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> judge_no [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=64840Do we want it for a server?2012-10-30T21:50:58Z<p>Vagrant: /* Instructor Chart */ dropped dell exclusion for *850, changed to DDR2+</p>
<hr />
<div>this chart is meant to help instructors determine if systems should be recycled or sent to server build.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\nwe do not want it for a server\npull all hard drives\nsend to recycling, and\nmark it on the clipboard\nin the server section", shape="box", style="bold"]<br />
yes [label="YES\nwe want it for a server\nplace a Hard Drive Removed sticker\non it and take to server build", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
judge_no [label="Use your best judgement,\nbut we probably do not want it", shape="box", style="bold"]<br />
judge_yes [label="Use your best judgement,\nbut we probably want it", shape="box", style="bold"] <br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 900,\n950 or 970?\n(i.e. 2970, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n850 or less?\n(i.e. 2450, 2650, 2800, 2850)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR2, DDR3 or DDR4 ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2"]<br />
sticker -> ddr [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> ddr [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> dell_poweredge [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> sata [label="NO"]<br />
<br />
ddr -> pcie [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [taillabel="NO"]<br />
<br />
dell_verynice -> yes [taillabel="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [taillabel="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [taillabel="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [taillabel="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> judge_yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> judge_no [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=64784Technical infrastructure checklist2012-10-25T23:52:58Z<p>Vagrant: /* Servers & Security */ mention new log for checking for wireless</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points<br />
** trace all cables connected to:<br />
*** credit card machine network (log in asssvm/docs/logs/credit-card-network)<br />
*** wireless network (is this needed? more we're looking for wireless where it shouldn't be)<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=64677Technical infrastructure checklist2012-10-18T20:28:30Z<p>Vagrant: /* Servers & Security */ traced cables.</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (at least quarterly: last done October 18th, 2012)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Server_Build_Checklist&diff=64459Server Build Checklist2012-10-03T20:00:56Z<p>Vagrant: /* RAID & LVM Setup (Build ONLY) */ update to wheezy, use ext4</p>
<hr />
<div>==Preliminaries==<br />
'''Check for blown caps''' - Examine all of the capacitors<br><br />
'''Check battery''' - Confirm that the CMOS battery is at least 3 volts<br><br />
'''Boot Process''' - Ensure that the server boots properly in the following ways:<br><br />
*'''Boots from CD''' - use an Ubuntu Live CD, leave Ubuntu running for next step<br><br />
*'''Boots automatically after power loss''' - while still in Ubuntu from the previous step, unplug all power cords (and the keyboard for the next step) from the server to simulate a sudden power loss. It should reboot automatically - if not, check BIOS settings.<br><br />
*'''Boots without keyboard''' - the server may report a "Keyboard failure" error - this is okay as long it boots successfully without human intervention, such as "press key X to continue..."<br><br />
<br />
<br />
==='''RAID & LVM Setup (Build ONLY)'''===<br />
<br />
'''Install Debian Wheezy''' - Boot to network and install Debian Wheezy to local disks, choose hostname, leave domain name as “fglan”<br />
<br />
===='''Setup Software RAID'''====<br />
<br />
'''Partition Disks:'''<br />
*Create small partition (400-500M) on each device<br />
**primary partition at the beginning of the drive<br />
**use as “physical volume for RAID”<br />
**set as bootable<br />
*Create large partition (all remaining space) on each device<br />
**primary, not bootable<br />
'''Setup RAID for small partitions:''' RAID1 (bootable) with the number of devices equal to number of disks<br><br />
'''Setup RAID for large partitions:'''<br />
*'''For 2-3 disks:'''Setup RAID1, with number of devices equal to number of disks<br />
*'''For 4+ disks:'''Setup RAID6, with number of devices equal to number of disks<br />
<br><br />
'''Configure LVM''' - configure larger RAID1 or RAID6 array as LVM volume<br />
*Create Logical Volume Group with same name as hostname<br />
*Select Large RAID array as LVM Volume<br />
**create volume (4G) named root (mounted at /, ext4 filesystem)<br />
**create volume (1G) named swap (use as swap)<br />
**create volume (remaining) named srv (mounted at /srv, ext4 filesystem)<br><br><br />
*Debian Wiki Guide to Software RAIDs: http://wiki.debian.org/DebianInstaller/SoftwareRaidRoot<br />
*Wikipedia RAID article: http://en.wikipedia.org/wiki/RAID<br />
<br />
==Diagnostics & Databases==<br />
* '''Boot from local disk(s)'''<br />
* '''Test USB ports''' (front and back),<br />
* '''Test video ports''' (front and back),<br />
* '''Test network ports''' - at terminal: <code>'''ifconfig eth0 up'''</code>, <code>'''ifconfig eth1 up'''</code>, then <code>'''tail -f /var/log/syslog'''</code>, and when you plug and unplug the ethernet cable, you should see reasonable printouts. Ctrl-C to stop the <code>'''tail'''</code> command.<br><br><br />
***'''QC Only:''' Remove any SATA/SAS drives and give them to your Instructor<br><br><br />
'''Run printme:'''<br />
*Boot from network<br />
** Select printme from the network boot menu<br />
** Log in as guest<br />
** Open a terminal<br />
** Run printme<br />
** Answer all questions and record anything else noteworthy in the notes section<br><br><br />
'''Fill out the Server Specs sticker''' based on whether you are doing Build or QC:<br />
* '''For BUILD:'''<br />
** Put System ID on server specs sticker<br />
** Number of physical processors and number of cores ''per'' processor<br />
** Processor speed (''GHz'') <br />
** Circle processor type (''Xeon, Opteron, Core 2, Other'')<br />
** Total amount of included RAM<br />
** Total number of RAM slots on board<br />
** Number of included RAM sticks with their speed and size<br />
** Circle type of RAM (''DDR, DDR2, DDR3'') <br />
** Circle type of DIMM (''ECC, FB-DIMM, etc.'')<br />
** Number of hard drive bays <br />
** Circle hard drive bay type (''IDE, SCSI, SATA, SAS'')<br />
** Number and size of included hard drives<br />
** Record anything notable, like Hardware RAID support, in the notes section<br />
** '''Do ''not'' print!''' Instead, put your Volunteer ID on a piece of tape on the system<br><br><br />
* '''For QC:'''<br />
** Confirm the accuracy of information already on the Server Specs sticker<br />
** Number and size of included hard drives<br />
** Circle whether an OS is installed (''none if hard drives removed!'')<br />
** Write the '''System ID#''' on a Server Tag sticker (small labels marked '''S1, S2, etc.''') and stick it to the front of the chassis.<br />
** '''Print the printme''' - Write the number from the Server Tag in the upper right-hand corner of the printme, and give it to your instructor.<br><br><br />
<br />
* Move the system to the Server Build KVM and run Memtest, if it hasn't already been done.<br />
* Consult your Instructor for a new project!<br />
<noinclude>[[Category:Server_Build]]</noinclude></div>Vagranthttp://wiki.freegeek.org/index.php?title=File:Recycle.glabels&diff=64446File:Recycle.glabels2012-10-02T22:30:27Z<p>Vagrant: uploaded a new version of "File:Recycle.glabels"</p>
<hr />
<div></div>Vagranthttp://wiki.freegeek.org/index.php?title=Incident_reports&diff=64396Incident reports2012-09-28T01:03:57Z<p>Vagrant: link to Injury Logging Procedure</p>
<hr />
<div>You probably should take a look at [[Injury Logging Procedure]] for a more detailed description, if applicable.<br />
<br />
Incidents (accidents, etc) should be reported in [http://todo.freegeek.org RT] in the Incident Reports queue.<br />
<br />
[[Category: Procedures]]<br />
[[Category: HR]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=64392Technical infrastructure checklist2012-09-27T18:40:56Z<p>Vagrant: /* Servers & Security */ rouge wireless checked today</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (at least quarterly: last done September 27th, 2012)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Talk:All_Staff_Meetings&diff=64331Talk:All Staff Meetings2012-09-21T00:02:12Z<p>Vagrant: Bargaining Unit Staff Scribe and Facilitators Proposal</p>
<hr />
<div>=Notes on facilitating the first BRAWL= <br />
[[User:Jashcraft|Jashcraft]] 14 April 2012<br />
*Start with a break<br />
**Unless we close the building earlier than 5:00 it seems unrealistic to start before 5:15. Some staff need a 15 minute break before the meeting and others were still closing their areas. Starting promptly at 5:15 worked well for me but left only an hour and 45 minutes for the agenda. <br />
<br />
*Check in with presenters beforehand<br />
** The day before the meeting I finalized the agenda after talking with each presenter. I had at least one item drop off of the agenda because the presenter lost interest and forgot to tell anyone. <br />
** This would be a good time to verify the AV needs of each presenter. With notice Darren should be able to set up the projector. <br />
<br />
*Work extra time into the agenda<br />
** I gave everyone 5 minutes more than they expected to need. This allowed a few people to continue productive lines of questioning without compromising the agenda.<br />
<br />
*Keep things moving<br />
** I ended many conversations in the interest of progressing the agenda. My strategy involved trying to acknowledge and redirect the enthusiasm for the topic by suggesting appropriate ways to continue the conversation. (over email or by talking to a coordinating individual)<br />
<br />
*Need two hours of preparation time before the meeting to set the agenda.<br />
*Should plan for food for the meeting<br />
*Facilitator should make sure the website shows any closing information<br />
<br />
=Bargaining Unit Staff Scribe and Facilitators Proposal=<br />
<br />
Generate a randomly sorted list of BU staff, the first person on the list will<br />
be the upcoming facilitator, the second on the list scribe. We cross a person's<br />
name off the list once they've served their respective role. New staff will be<br />
randomly added to the list amoungst the remaining uncrossed off people, but<br />
otherwise the order will remain unchanged.<br />
<br />
The following list was generated by writing a file with everyone's name in it, one per line, and running "sort -R" on the file, and cutting and pasting the output.<br />
<br />
<s>Example Strikethrough</s><br />
<br />
Omar Vargas<br />
<br />
Aradan Thompson<br />
<br />
Elizabeth Swager<br />
<br />
Liliana Gaitan<br />
<br />
Jake Taasevigen<br />
<br />
Kevin Wright<br />
<br />
Brian Keefer<br />
<br />
James Pella<br />
<br />
Patrick Sullivan<br />
<br />
Ryan Niebur<br />
<br />
Michael Westwind<br />
<br />
Cliff Fortune<br />
<br />
Ashley Sue Masoomian<br />
<br />
Santiago Carmona<br />
<br />
Misty Fall<br />
<br />
John Ashcraft<br />
<br />
Robert Taylor<br />
<br />
Eli Wisnievitz<br />
<br />
Lynnae Griffiths<br />
<br />
Austin Crouch<br />
<br />
Vagrant Cascadian</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=64316Technical infrastructure checklist2012-09-20T19:34:11Z<p>Vagrant: /* Servers & Security */ updated check for wireless</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (at least quarterly: last done September 2012)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Hard_Drive_Sorting&diff=64292Hard Drive Sorting2012-09-19T18:44:05Z<p>Vagrant: upped SCSI to 140GB+</p>
<hr />
<div>Hard drive sorting is done in [[System Evaluation]].<br />
<br />
== Sort ==<br />
<graphviz><br />
digraph D {<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START HERE", shape="box", style="bold"]<br />
ask [label="ASK", shape="box", style="bold"]<br />
ask2 [label="ASK", shape="box", style="bold"]<br />
keep [label="KEEP", shape="box", style="bold"]<br />
recycle [label="RECYCLE", shape="box", style="bold"]<br />
recycle2 [label="RECYCLE", shape="box", style="bold"]<br />
fiftypinscsi [label="Is it 50 pin SCSI?"]<br />
scsi [label="Is it SCSI?"]<br />
reg_size [label="Is it 3.5in?\n(regular sized)"]<br />
big_size [label="Is it 5.25in?\n(bigfoot sized)"]<br />
lap_size [label="Is it 2.5in?\n(laptop sized)"]<br />
sata [label="Is it SATA?"]<br />
ide [label="Is it IDE?"]<br />
scsi_cutoff [label="Is it 140 GB or greater?"]<br />
ide_cutoff [label="Is it 40 GB or greater?"]<br />
lap_cutoff [label="Is it 6 GB or greater?"]<br />
<br />
start -> sata<br />
<br />
sata -> keep [label="YES"]<br />
sata -> ide [ label="NO" ]<br />
<br />
fiftypinscsi -> scsi_cutoff [ label="NO" ]<br />
fiftypinscsi -> recycle [label="YES"]<br />
<br />
ide -> big_size [ label="YES" ]<br />
ide -> scsi [label="NO"]<br />
<br />
big_size -> reg_size [label="NO"]<br />
big_size -> recycle [label="YES"]<br />
<br />
scsi -> fiftypinscsi [ label="YES" ]<br />
scsi -> ask2 [ label="NO" ]<br />
<br />
lap_size -> lap_cutoff [label="YES"]<br />
lap_size -> ask [label="NO"]<br />
<br />
reg_size -> lap_size [label="NO"]<br />
reg_size -> ide_cutoff [label="YES"]<br />
<br />
scsi_cutoff -> recycle [label="NO"]<br />
scsi_cutoff -> keep [label="YES"]<br />
<br />
ide_cutoff -> recycle [label="NO"]<br />
ide_cutoff -> keep [label="YES"]<br />
<br />
lap_cutoff -> recycle2 [label="NO"]<br />
lap_cutoff -> keep [label="YES"]<br />
<br />
}<br />
</graphviz><br />
<br />
; List of drives to recycle:<br />
* 3 1/2 inch IDE hard drives marked less than '''40 GB'''<br />
* 2 1/2 inch IDE hard drives marked less than '''6 GB''' <br />
* 5 1/4 inch IDE hard drives, regardless of capacity ''(these are known as "Bigfoot" drives)''<br />
* SCSI drives marked less than '''72 GB'''<br />
* 50 pin SCSI drives<br />
* MFM hard drives ''(very old, see example)''<br />
<br />
; List of drives to keep:<br />
* 3 1/2 inch IDE hard drives marked '''40 GB or bigger'''<br />
* SCSI drives marked '''140 GB or bigger'''<br />
* 2 1/2 inch IDE hard drives marked '''6 GB or bigger''' <br />
<br />
; When in doubt keep the drive.<br />
<br />
; Steps when Sorting<br />
# First, check the '''recycle''' crate for drives that should be '''kept''':<br />
# Then check the '''incoming''' crate for drives that should be '''kept or recycled''':<br />
# Put any keepers in the TARDIS in the incoming drive area (near the door).<br />
# Destroy any recyclers using the '''hard drive crank'''.<br />
#* Ask someone in charge to check them before destroying the "recyclers" (even if you think you know how), and ask about the ones you think you want to keep.<br />
# Stack recyclers in the crates. When crates are 75% full, put them on the cart to go to the warehouse.<br />
<br />
== How to tell a hard drive's capacity ==<br />
Many hard drives are marked with their capacity. The words might be very small, but they're usually there. Look carefully for them. If that doesn't work:<br />
<br />
; Look for double labeled drives<br />
: Some drives have two labels. One generic label lists several different capacities and/or disk geometry. The other label is model specific and lists the model number. For instance one label might say:<br />
<br />
MPC3032AT (3.24GB)<br />
MPC3043AT (4.32GB)<br />
MPC3064AT (6.48GB)<br />
MPC3084AT (8.45GB)<br />
MPC3096AT (9.74GB)<br />
<br />
: The other label says:<br />
<br />
Model MPC3032AT<br />
<br />
: The drive is a 3.24 GB drive<br />
<br />
; Look for model number schemes<br />
: Some model numbers contain a hint as to the capacity of the drive. For instance, the western digital drives can usually be deduced by dropping the first digit in the model number. In the example above MPC3032AT is approximately a 3.2 GB drive and MPC3043AT is approximately a 4.3. Thus we can determine that the third and fourth digit in the four digit number is the drive size. By comparing similar models, you might be able to determine the probable sizes.<br />
<br />
; Google is your friend.<br />
: Try [http://google.com/ googling] the model number and see if anything turns up.<br />
<br />
== Where to put them ==<br />
* Hard drives in the Recycle bucket go straight to Recycling after they are signed off by the Eval instructor and suitably '''whacked, drilled or squished'''.<br />
* Good Hard Drives go into the TARDIS<br />
<br />
<br />
<br />
[[Category: System Evaluation]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Server_Identification&diff=63881Server Identification2012-08-18T20:27:44Z<p>Vagrant: /* GREY Chart */ add VGA/DVI and USB/keyboard connector question</p>
<hr />
<div>Servers are a special type of computer, but need to be tracked separately due to Oregon eCycles rules and similar constraints. For example, they are never (currently) covered by Oregon eCycles. We therefore need to be able to identify servers as distinct from other computers. These instructions are intended to make that possible.<br />
<br />
<br />
<br />
==GREY Chart==<br />
;Is it a server?<br />
<div style="border: 10px solid GREY; padding: .5em 1em; color: #000; margin: 3px 3px 0;"><br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START HERE", shape="box", style="bold"]<br />
ask [label="ASK YOUR\nINSTRUCTOR", shape="box", style="bold"]<br />
server [label="YES\nThis is a\nSERVER", shape="box", style="bold"]<br />
system [label="NO\nThis is not a\nSERVER", shape="box", style="bold"]<br />
<br />
computer [label="Is it a\nCOMPUTER?\n(has VGA or DVI ports?\nUSB or keyboard connectors?)"]<br />
rack_mount [label="Is it a\nRACK MOUNT\ncomputer?"]<br />
xeon [label="Does it have a\nXEON STICKER\non it?"]<br />
list [label="Is it on the\nLIST OF\nSERVER MODELS?"]<br />
<br />
start -> computer<br />
<br />
computer -> ask [label="NO"]<br />
computer -> rack_mount [label="YES"]<br />
<br />
rack_mount -> server [label="YES"]<br />
rack_mount -> xeon [label="NO"]<br />
<br />
xeon -> server [label="YES"]<br />
xeon -> list [label="NO"]<br />
<br />
list -> server [label="YES"]<br />
list -> system [label="NO"]<br />
<br />
}<br />
</graphviz><br />
<br />
</div><br />
<br />
== List of Server Models ==<br />
* DELL PowerEdge<br />
* Sun<br />
* Silicon Graphics<br />
<br />
<br />
[[Category: System Evaluation]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=63836Technical infrastructure checklist2012-08-16T18:01:48Z<p>Vagrant: /* Servers & Security */ mention checks for archived events, purging of old events</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
** check for old (over two weeks?) unarchived events<br />
** check for archived events ... then what?<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (at least quarterly: last done August 2012)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=63835Technical infrastructure checklist2012-08-16T17:59:01Z<p>Vagrant: /* Servers & Security */ update status of wireless audit</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (at least quarterly: last done August 2012)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' ([[Phone Extension List]])<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Candidate_Distro_List&diff=62637Candidate Distro List2012-06-07T18:40:38Z<p>Vagrant: /* Ubuntu */ derived from Debian</p>
<hr />
<div>=The Candidate Distro List=<br />
<br />
==About this list==<br />
Three key points for a candidate distribution:<br />
# easy to use<br />
# large hardware profile<br />
# acessibility<br />
<br />
''Note from Paul'':<br />
* Big five (Debian, Fedora, Mint, OpenSuSE, Ubuntu), and interesting others<br />
* List needs to be small and shrink<br />
<br />
Standardized info for each distro:<br />
* Distro Parent: (e.g., RedHat, Debian, etc)<br />
* Minimum System Requirements:<br />
* Package Manager:<br />
* Release Cycles (if applicable):<br />
* Standard Desktop Environment:<br />
* Documentation (links to wikis, forums, etc):<br />
''(kudos to Sean for the headway!)''<br />
<br />
Suggestions for commenting:<br />
* Think about the Key Points listed above (ease of use, supported hardware, accessibility)<br />
* Does stuff work out-of-the-box? (networking, video, sound, laptop devices, keyboard map, mounting external media)<br />
* Does it provide easy utilities for configuring the system?<br />
* How easy is the package manager to use?<br />
* Is the Desktop Environment clean/nice/easy/useful?<br />
* It may not be so useful to talk about ease of install (this can be automated)<br />
<br />
==Useful Links==<br />
<br />
http://tuxradar.com/content/best-distro-2011<br />
<br />
==The Top Five==<br />
<br />
===Mint===<br />
[[File:Linux_mint.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=mint<br />
<br />
http://linuxmint.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
this info comes from http://www.linuxmint.com/faq.php and it is the only place on the official website that I saw this info listed:<br />
<br />
Is Linux Mint suitable for companies?<br />
Yes. Although Linux Mint release new versions every 6 months, each release is supported for a year and a half. We also make periodic Long-Term Support (LTS) releases which are supported for a duration of 3 years and which are guaranteed to provide enough overlap to allow you to upgrade from one LTS release to the next.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Mint has a quality idea/feedback system at http://community.Linuxmint.com/ that uses roughly a ticket based system for advancing new ideas, rating them, and marking them as rejected or accepted.<br />
This is different than their bug tracking, which is handled through launchpad, and from the forums in general I gathered that fixes go upstream to ubuntu.<br />
<br />
Documentation is unfortunately almost non-existent (the word 'documentation' does not appear on their website) but there are a series of tutorials on a wide variety of topics that are not necessarily related to mint that can be found at http://community.linuxmint.com/tutorial/search<br />
<br />
Hardware support information: there is an extensibly searchable supported hardware catalog that can be found at http://community.linuxmint.com/hardware<br />
check out the Type: 'Wifi car/adapter/dongle' (long list) page for an example<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
Ubuntu/Debian<br />
<br />
'''Minimum System Requirements:'''<br />
* Recommended 1GHz 512MB RAM<br />
''from wikipedia''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Mint 12 and 9 supported until April 2013<br />
* Mint Debian: rolling distribution<br />
''from mint website''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* Mint 12 is based on ubuntu with a gnome environment. I installed and after a splash page comes up on the desktop that prompts you to download media and dvd codecs among other things like links to tutorials and other pages on the community website<br />
* Mint website says Mint Debian is neat because it is auto-updating - you never have to upgrade versions. but it is also therefore more unstable. It also reqs knowledge of the command line to enable one-touch-click on laptops and other similar things. They also says it is like ubuntu but rough around the edges.<br />
<br />
===Ubuntu===<br />
[[File:Ubuntu.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=ubuntu<br />
<br />
http://www.ubuntu.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
from http://www.ubuntu.com/project/about-ubuntu<br />
<br />
The Ubuntu team broke new ground in committing to a programme of scheduled releases on a predictable six-month basis. It was decided that every fourth release, issued on a two-year basis, would receive long-term support (LTS). LTS releases are typically used for large-scale deployments.<br />
<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Documentation seems unfortunately bloated and confusing; each page has many more pages linked, and it is difficult to find specific info. Official Documentation for 12.04 is four clicks in from main site in a difficult to navigat manner, and can be found at https://help.ubuntu.com/12.04/ubuntu-help/index.html.<br />
This is distinct from the 'community wiki' documentation, which is also hard to navigate, somewhat redundant with the official docs.<br />
<br />
Hardware: from either the official or community wiki docs, there are sections about hardware support, but I had a difficult time and found little useful information.<br />
<br />
There are many many ubuntu local chapters, but this user has been involved with our Oregon branch, and while I have met people who have worked with fg, I have not really met any fg end-users at the meetings (posted ~06/12)<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
Debian<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
===Debian===<br />
<br />
http://debian.org<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
<br />
Debian has three branches (stable, unstable, experimental) and do not have a set release cycle. <br />
Recent releases have occurred slightly under once every two years.<br />
<br />
The current testing branch, wheezy, has a freeze scheduled for end of June 2012, and a release <br />
is feasible by the end of 2012.<br />
<br />
Security support on the old stable release is maintained for 1 additional year beyond the <br />
current stable release.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Stability: In this users experience (John Parker), Debian 6.0 incredibly stable and is at least twice as stable in frequency of errors/conflicts compared to ubuntu, but sometimes it has been difficult setting processes up for the first time (wireless for example)<br />
<br />
Documentation: http://www.debian.org/doc/<br />
There are many manuals, howtos, faqs, and guides, but it seems that you have to know what section you are looking for more than what problem you are having.<br />
<br />
Community: There is a large developer community, but it may be difficult to approach from and end-user standpoint, though Debian goes to great lengths to allow it's users to feel encouraged to troubleshoot their own issues.<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent: None'''<br />
'''Minimum System Requirements:'''<br />
'''Package Manager:'''<br />
'''Release Cycles (if applicable):'''<br />
'''Standard Desktop Environment:'''<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
Support Cycle:<br />
* 1 year past previous release, new release approximately every 2 years.<br />
* freeze for next release(wheezy), June 2012, release hopefully by end of 2012.<br />
<br />
===Fedora===<br />
<br />
'''Distro Parent:''' RedHat<br />
<br />
'''Minimum System Requirements:'''<br />
* 10GB drive space<br />
* 1G RAM<br />
* 400MHz Pentium Pro or later (Also works on AMD, Cyrix and VIA<br />
<br />
'''Package Manager:''' Yum<br />
<br />
'''Release cycle:''' every 6 months. Last release (fedora 16) was on 11/08/2011<br />
<br />
'''Standard Desktop environment:''' Gnome <br />
Nisha: Actually during installation of Fedora 16, Gnome 3 gets natively installed. However, most probably the graphics cards or drivers that we would use would not support Gnome 3 so it will fail install and go to a "fallback" mode. At this point the CD goes live. We could probably get this to not happen during installation.<br />
<br />
'''Documentation:'''<br />
* http://fedoraproject.org/<br />
* https://fedoraproject.org/wiki/Fedora_Project_Wiki<br />
<br />
'''Comments:'''<br />
Nisha: <br />
* Some trouble installing it but did manage to install it. It comes with a minimal amount of extra software installed but comes with yum to install other packages as needed. From experience I know that it is not straightforward but I think it is customizable to our requirements if we write a script to make changes and install packages. For example, a user cannot use sudo unless they add their user name to the wheel group.<br />
Nisha: By default, SELinux is enabled which might be irritating to users. All the usual apps that you would expect to see are there under the Applications section. That means it's still difficult to find the software that you had just installed :P<br />
<br />
===OpenSuSe===<br />
[[File:OpenSUSE-icon.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=suse<br />
<br />
http://www.opensuse.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* ( Supported by Novell. )<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
[[File:Zed.png]]<br />
zed:<br />
<br />
<font size="-2">updated: 01/06/11</font><br />
<br />
<span style="background:#AFEEEE">'''+''': Install is very customizable and works with multiple monitor setups. Networking, sound and many other options can be configured at the time of installation. Gives the option to install either Gnome, KDE and few lesser known GUIs on installation. Most features work out of the box.<br />
</span><br />
<br />
<span style="background:#D3D3D3">'''-''': Software Package Management system not as easy to use as other distros. A few minor glitches on the GUI. Website can be difficult to navigate for help.<br />
</span><br />
<br />
== (rest of) The List==<br />
<br />
===Arch===<br />
[[File:Arch-linux.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=arch<br />
<br />
http://www.archlinux.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* (not listed)<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Rolling<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* For advanced users familiar with the CLI and the layout of their system. Installation is robust and ncurses based; user must make many specific choices. Also, once installed, boots to CLI first, no GUI installed by default, must install and start x manually. ''research from arch website''<br />
<br />
===CentOS===<br />
[[File:Centos_icon_60_normal.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=centos<br />
<br />
http://www.centos.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* Minimum v5 - 256MB Ram<br />
* Minimum v6 - 512MB Ram<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Version 5 - until March 2014<br />
* Version 6 - until November 2017<br />
''from centOS FAQ''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
=== PCLinuxOS===<br />
<br />
http://distrowatch.com/table.php?distribution=pclinuxos<br />
<br />
http://www.pclinuxos.com/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Puppy===<br />
<br />
http://distrowatch.com/table.php?distribution=puppy<br />
<br />
http://www.puppylinux.com/<br />
<br />
Support Cycle:<br />
* Wary and Racy puppy are both LTS (duration not stated)<br />
<br />
System Reqs:<br />
* (not listed) though Puppy is intended NOT TO BE INSTALLED TO HD<br />
* it is intended to run off of a LiveCD AND the process to install to HD is long and obscure<br />
<br />
Comments JP:<br />
* website is hard to follow<br />
* not much community support<br />
<br />
===Mageia===<br />
<br />
http://distrowatch.com/table.php?distribution=mageia<br />
<br />
http://www.mageia.org/<br />
<br />
Support Cycle: <br />
* (UNDECIDED)<br />
* Mageia is a Mandriva fork that is 9 months old (brand new)<br />
<br />
System Reqs: <br />
* 512MB RAM min - 2GB recommended<br />
* 6GB HD for full install<br />
<br />
===Mandriva===<br />
<br />
http://distrowatch.com/table.php?distribution=mandriva<br />
<br />
http://www.mandriva.com/<br />
<br />
Support Cycle:<br />
* Mandriva 2011 end support cycle is undecided, but will be after Dec 2012<br />
<br />
System Reqs:<br />
* Mandriva 2011 Reqs. min 1GB Ram<br />
<br />
===Lubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=lubuntu<br />
<br />
http://lubuntu.net/<br />
<br />
Support Cycle:<br />
* 11.10 will be supported until April 2013. It is the first official release as part of the Ubuntu cycle.<br />
<br />
System Reqs:<br />
* A Pentium II or Celeron system with 128 MB of RAM is probably a bottom-line configuration that may yield slow yet usable system with Lubuntu. It should be possible to install and run Lubuntu with less memory, but the result will likely not be suitable for practical use. ''from lubuntu website''<br />
<br />
===Kubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=kubuntu<br />
<br />
http://www.kubuntu.org/<br />
<br />
Support Cycle:<br />
* (not listed) it appears to follow Ubuntu's support cycle<br />
<br />
System Reqs:<br />
* (not listed) but it is ubuntu with KDE and some different applications<br />
<br />
===Sabayon===<br />
<br />
http://distrowatch.com/table.php?distribution=sabayon<br />
<br />
http://www.sabayon.org/<br />
<br />
Support Cycle:<br />
* Rolling Release ''from Sabayon wiki 'Info' Page''<br />
<br />
System Reqs:<br />
* 512 MB of RAM (1 GB suggested) ''from FAQ''<br />
* Minimum of 12 GB of free hard disk space for KDE and GNOME. ''from FAQ''<br />
<br />
Comments JP:<br />
* Based on Gentoo<br />
* Uses Entropy OR Portage Package Management<br />
* Robust website<br />
<br />
===Chakra===<br />
<br />
http://distrowatch.com/table.php?distribution=chakra<br />
<br />
http://chakra-linux.org/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Forked from Arch<br />
* KDE desktop<br />
<br />
===Zorin OS===<br />
<br />
http://distrowatch.com/table.php?distribution=zorin<br />
<br />
http://www.zorin-os.com/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Ubuntu-based<br />
* designed for linux new-comers ''-taken from distrowatch page''<br />
* windows-like GUI<br />
* Includes Wine-like functionality<br />
<br />
===Ultimate===<br />
<br />
http://distrowatch.com/table.php?distribution=ultimate<br />
<br />
http://ultimateedition.info/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Bodhi===<br />
<br />
http://distrowatch.com/table.php?distribution=bodhi<br />
<br />
http://www.bodhilinux.com/<br />
<br />
===Fuduntu===<br />
<br />
http://distrowatch.com/table.php?distribution=fuduntu<br />
<br />
http://www.fuduntu.org/<br />
<br />
Support Cycle:<br />
* (not stated on website)<br />
<br />
System Reqs: <br />
* 900MHz<br />
* 384 MB RAM<br />
* 5GB HD<br />
<br />
===ClearOS===<br />
<br />
http://distrowatch.com/table.php?distribution=clearos<br />
<br />
http://www.clearfoundation.com/<br />
<br />
''NOTE: This is a network server/gateway configurable from web<br />
<br />
===Joli OS===<br />
<br />
http://distrowatch.com/table.php?distribution=jolios<br />
<br />
http://www.jolicloud.com/<br />
<br />
[[Category:Distro]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Candidate_Distro_List&diff=62636Candidate Distro List2012-06-07T18:39:39Z<p>Vagrant: /* Mint */ derived from Ubuntu and directly/indirectly Debian</p>
<hr />
<div>=The Candidate Distro List=<br />
<br />
==About this list==<br />
Three key points for a candidate distribution:<br />
# easy to use<br />
# large hardware profile<br />
# acessibility<br />
<br />
''Note from Paul'':<br />
* Big five (Debian, Fedora, Mint, OpenSuSE, Ubuntu), and interesting others<br />
* List needs to be small and shrink<br />
<br />
Standardized info for each distro:<br />
* Distro Parent: (e.g., RedHat, Debian, etc)<br />
* Minimum System Requirements:<br />
* Package Manager:<br />
* Release Cycles (if applicable):<br />
* Standard Desktop Environment:<br />
* Documentation (links to wikis, forums, etc):<br />
''(kudos to Sean for the headway!)''<br />
<br />
Suggestions for commenting:<br />
* Think about the Key Points listed above (ease of use, supported hardware, accessibility)<br />
* Does stuff work out-of-the-box? (networking, video, sound, laptop devices, keyboard map, mounting external media)<br />
* Does it provide easy utilities for configuring the system?<br />
* How easy is the package manager to use?<br />
* Is the Desktop Environment clean/nice/easy/useful?<br />
* It may not be so useful to talk about ease of install (this can be automated)<br />
<br />
==Useful Links==<br />
<br />
http://tuxradar.com/content/best-distro-2011<br />
<br />
==The Top Five==<br />
<br />
===Mint===<br />
[[File:Linux_mint.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=mint<br />
<br />
http://linuxmint.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
this info comes from http://www.linuxmint.com/faq.php and it is the only place on the official website that I saw this info listed:<br />
<br />
Is Linux Mint suitable for companies?<br />
Yes. Although Linux Mint release new versions every 6 months, each release is supported for a year and a half. We also make periodic Long-Term Support (LTS) releases which are supported for a duration of 3 years and which are guaranteed to provide enough overlap to allow you to upgrade from one LTS release to the next.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Mint has a quality idea/feedback system at http://community.Linuxmint.com/ that uses roughly a ticket based system for advancing new ideas, rating them, and marking them as rejected or accepted.<br />
This is different than their bug tracking, which is handled through launchpad, and from the forums in general I gathered that fixes go upstream to ubuntu.<br />
<br />
Documentation is unfortunately almost non-existent (the word 'documentation' does not appear on their website) but there are a series of tutorials on a wide variety of topics that are not necessarily related to mint that can be found at http://community.linuxmint.com/tutorial/search<br />
<br />
Hardware support information: there is an extensibly searchable supported hardware catalog that can be found at http://community.linuxmint.com/hardware<br />
check out the Type: 'Wifi car/adapter/dongle' (long list) page for an example<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
Ubuntu/Debian<br />
<br />
'''Minimum System Requirements:'''<br />
* Recommended 1GHz 512MB RAM<br />
''from wikipedia''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Mint 12 and 9 supported until April 2013<br />
* Mint Debian: rolling distribution<br />
''from mint website''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* Mint 12 is based on ubuntu with a gnome environment. I installed and after a splash page comes up on the desktop that prompts you to download media and dvd codecs among other things like links to tutorials and other pages on the community website<br />
* Mint website says Mint Debian is neat because it is auto-updating - you never have to upgrade versions. but it is also therefore more unstable. It also reqs knowledge of the command line to enable one-touch-click on laptops and other similar things. They also says it is like ubuntu but rough around the edges.<br />
<br />
===Ubuntu===<br />
[[File:Ubuntu.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=ubuntu<br />
<br />
http://www.ubuntu.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
from http://www.ubuntu.com/project/about-ubuntu<br />
<br />
The Ubuntu team broke new ground in committing to a programme of scheduled releases on a predictable six-month basis. It was decided that every fourth release, issued on a two-year basis, would receive long-term support (LTS). LTS releases are typically used for large-scale deployments.<br />
<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Documentation seems unfortunately bloated and confusing; each page has many more pages linked, and it is difficult to find specific info. Official Documentation for 12.04 is four clicks in from main site in a difficult to navigat manner, and can be found at https://help.ubuntu.com/12.04/ubuntu-help/index.html.<br />
This is distinct from the 'community wiki' documentation, which is also hard to navigate, somewhat redundant with the official docs.<br />
<br />
Hardware: from either the official or community wiki docs, there are sections about hardware support, but I had a difficult time and found little useful information.<br />
<br />
There are many many ubuntu local chapters, but this user has been involved with our Oregon branch, and while I have met people who have worked with fg, I have not really met any fg end-users at the meetings (posted ~06/12)<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
===Debian===<br />
<br />
http://debian.org<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
<br />
Debian has three branches (stable, unstable, experimental) and do not have a set release cycle. <br />
Recent releases have occurred slightly under once every two years.<br />
<br />
The current testing branch, wheezy, has a freeze scheduled for end of June 2012, and a release <br />
is feasible by the end of 2012.<br />
<br />
Security support on the old stable release is maintained for 1 additional year beyond the <br />
current stable release.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Stability: In this users experience (John Parker), Debian 6.0 incredibly stable and is at least twice as stable in frequency of errors/conflicts compared to ubuntu, but sometimes it has been difficult setting processes up for the first time (wireless for example)<br />
<br />
Documentation: http://www.debian.org/doc/<br />
There are many manuals, howtos, faqs, and guides, but it seems that you have to know what section you are looking for more than what problem you are having.<br />
<br />
Community: There is a large developer community, but it may be difficult to approach from and end-user standpoint, though Debian goes to great lengths to allow it's users to feel encouraged to troubleshoot their own issues.<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent: None'''<br />
'''Minimum System Requirements:'''<br />
'''Package Manager:'''<br />
'''Release Cycles (if applicable):'''<br />
'''Standard Desktop Environment:'''<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
Support Cycle:<br />
* 1 year past previous release, new release approximately every 2 years.<br />
* freeze for next release(wheezy), June 2012, release hopefully by end of 2012.<br />
<br />
===Fedora===<br />
<br />
'''Distro Parent:''' RedHat<br />
<br />
'''Minimum System Requirements:'''<br />
* 10GB drive space<br />
* 1G RAM<br />
* 400MHz Pentium Pro or later (Also works on AMD, Cyrix and VIA<br />
<br />
'''Package Manager:''' Yum<br />
<br />
'''Release cycle:''' every 6 months. Last release (fedora 16) was on 11/08/2011<br />
<br />
'''Standard Desktop environment:''' Gnome <br />
Nisha: Actually during installation of Fedora 16, Gnome 3 gets natively installed. However, most probably the graphics cards or drivers that we would use would not support Gnome 3 so it will fail install and go to a "fallback" mode. At this point the CD goes live. We could probably get this to not happen during installation.<br />
<br />
'''Documentation:'''<br />
* http://fedoraproject.org/<br />
* https://fedoraproject.org/wiki/Fedora_Project_Wiki<br />
<br />
'''Comments:'''<br />
Nisha: <br />
* Some trouble installing it but did manage to install it. It comes with a minimal amount of extra software installed but comes with yum to install other packages as needed. From experience I know that it is not straightforward but I think it is customizable to our requirements if we write a script to make changes and install packages. For example, a user cannot use sudo unless they add their user name to the wheel group.<br />
Nisha: By default, SELinux is enabled which might be irritating to users. All the usual apps that you would expect to see are there under the Applications section. That means it's still difficult to find the software that you had just installed :P<br />
<br />
===OpenSuSe===<br />
[[File:OpenSUSE-icon.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=suse<br />
<br />
http://www.opensuse.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* ( Supported by Novell. )<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
[[File:Zed.png]]<br />
zed:<br />
<br />
<font size="-2">updated: 01/06/11</font><br />
<br />
<span style="background:#AFEEEE">'''+''': Install is very customizable and works with multiple monitor setups. Networking, sound and many other options can be configured at the time of installation. Gives the option to install either Gnome, KDE and few lesser known GUIs on installation. Most features work out of the box.<br />
</span><br />
<br />
<span style="background:#D3D3D3">'''-''': Software Package Management system not as easy to use as other distros. A few minor glitches on the GUI. Website can be difficult to navigate for help.<br />
</span><br />
<br />
== (rest of) The List==<br />
<br />
===Arch===<br />
[[File:Arch-linux.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=arch<br />
<br />
http://www.archlinux.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* (not listed)<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Rolling<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* For advanced users familiar with the CLI and the layout of their system. Installation is robust and ncurses based; user must make many specific choices. Also, once installed, boots to CLI first, no GUI installed by default, must install and start x manually. ''research from arch website''<br />
<br />
===CentOS===<br />
[[File:Centos_icon_60_normal.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=centos<br />
<br />
http://www.centos.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* Minimum v5 - 256MB Ram<br />
* Minimum v6 - 512MB Ram<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Version 5 - until March 2014<br />
* Version 6 - until November 2017<br />
''from centOS FAQ''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
=== PCLinuxOS===<br />
<br />
http://distrowatch.com/table.php?distribution=pclinuxos<br />
<br />
http://www.pclinuxos.com/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Puppy===<br />
<br />
http://distrowatch.com/table.php?distribution=puppy<br />
<br />
http://www.puppylinux.com/<br />
<br />
Support Cycle:<br />
* Wary and Racy puppy are both LTS (duration not stated)<br />
<br />
System Reqs:<br />
* (not listed) though Puppy is intended NOT TO BE INSTALLED TO HD<br />
* it is intended to run off of a LiveCD AND the process to install to HD is long and obscure<br />
<br />
Comments JP:<br />
* website is hard to follow<br />
* not much community support<br />
<br />
===Mageia===<br />
<br />
http://distrowatch.com/table.php?distribution=mageia<br />
<br />
http://www.mageia.org/<br />
<br />
Support Cycle: <br />
* (UNDECIDED)<br />
* Mageia is a Mandriva fork that is 9 months old (brand new)<br />
<br />
System Reqs: <br />
* 512MB RAM min - 2GB recommended<br />
* 6GB HD for full install<br />
<br />
===Mandriva===<br />
<br />
http://distrowatch.com/table.php?distribution=mandriva<br />
<br />
http://www.mandriva.com/<br />
<br />
Support Cycle:<br />
* Mandriva 2011 end support cycle is undecided, but will be after Dec 2012<br />
<br />
System Reqs:<br />
* Mandriva 2011 Reqs. min 1GB Ram<br />
<br />
===Lubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=lubuntu<br />
<br />
http://lubuntu.net/<br />
<br />
Support Cycle:<br />
* 11.10 will be supported until April 2013. It is the first official release as part of the Ubuntu cycle.<br />
<br />
System Reqs:<br />
* A Pentium II or Celeron system with 128 MB of RAM is probably a bottom-line configuration that may yield slow yet usable system with Lubuntu. It should be possible to install and run Lubuntu with less memory, but the result will likely not be suitable for practical use. ''from lubuntu website''<br />
<br />
===Kubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=kubuntu<br />
<br />
http://www.kubuntu.org/<br />
<br />
Support Cycle:<br />
* (not listed) it appears to follow Ubuntu's support cycle<br />
<br />
System Reqs:<br />
* (not listed) but it is ubuntu with KDE and some different applications<br />
<br />
===Sabayon===<br />
<br />
http://distrowatch.com/table.php?distribution=sabayon<br />
<br />
http://www.sabayon.org/<br />
<br />
Support Cycle:<br />
* Rolling Release ''from Sabayon wiki 'Info' Page''<br />
<br />
System Reqs:<br />
* 512 MB of RAM (1 GB suggested) ''from FAQ''<br />
* Minimum of 12 GB of free hard disk space for KDE and GNOME. ''from FAQ''<br />
<br />
Comments JP:<br />
* Based on Gentoo<br />
* Uses Entropy OR Portage Package Management<br />
* Robust website<br />
<br />
===Chakra===<br />
<br />
http://distrowatch.com/table.php?distribution=chakra<br />
<br />
http://chakra-linux.org/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Forked from Arch<br />
* KDE desktop<br />
<br />
===Zorin OS===<br />
<br />
http://distrowatch.com/table.php?distribution=zorin<br />
<br />
http://www.zorin-os.com/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Ubuntu-based<br />
* designed for linux new-comers ''-taken from distrowatch page''<br />
* windows-like GUI<br />
* Includes Wine-like functionality<br />
<br />
===Ultimate===<br />
<br />
http://distrowatch.com/table.php?distribution=ultimate<br />
<br />
http://ultimateedition.info/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Bodhi===<br />
<br />
http://distrowatch.com/table.php?distribution=bodhi<br />
<br />
http://www.bodhilinux.com/<br />
<br />
===Fuduntu===<br />
<br />
http://distrowatch.com/table.php?distribution=fuduntu<br />
<br />
http://www.fuduntu.org/<br />
<br />
Support Cycle:<br />
* (not stated on website)<br />
<br />
System Reqs: <br />
* 900MHz<br />
* 384 MB RAM<br />
* 5GB HD<br />
<br />
===ClearOS===<br />
<br />
http://distrowatch.com/table.php?distribution=clearos<br />
<br />
http://www.clearfoundation.com/<br />
<br />
''NOTE: This is a network server/gateway configurable from web<br />
<br />
===Joli OS===<br />
<br />
http://distrowatch.com/table.php?distribution=jolios<br />
<br />
http://www.jolicloud.com/<br />
<br />
[[Category:Distro]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Candidate_Distro_List&diff=62635Candidate Distro List2012-06-07T18:24:01Z<p>Vagrant: /* Debian */ fleshed out release cycle more</p>
<hr />
<div>=The Candidate Distro List=<br />
<br />
==About this list==<br />
Three key points for a candidate distribution:<br />
# easy to use<br />
# large hardware profile<br />
# acessibility<br />
<br />
''Note from Paul'':<br />
* Big five (Debian, Fedora, Mint, OpenSuSE, Ubuntu), and interesting others<br />
* List needs to be small and shrink<br />
<br />
Standardized info for each distro:<br />
* Distro Parent: (e.g., RedHat, Debian, etc)<br />
* Minimum System Requirements:<br />
* Package Manager:<br />
* Release Cycles (if applicable):<br />
* Standard Desktop Environment:<br />
* Documentation (links to wikis, forums, etc):<br />
''(kudos to Sean for the headway!)''<br />
<br />
Suggestions for commenting:<br />
* Think about the Key Points listed above (ease of use, supported hardware, accessibility)<br />
* Does stuff work out-of-the-box? (networking, video, sound, laptop devices, keyboard map, mounting external media)<br />
* Does it provide easy utilities for configuring the system?<br />
* How easy is the package manager to use?<br />
* Is the Desktop Environment clean/nice/easy/useful?<br />
* It may not be so useful to talk about ease of install (this can be automated)<br />
<br />
==Useful Links==<br />
<br />
http://tuxradar.com/content/best-distro-2011<br />
<br />
==The Top Five==<br />
<br />
===Mint===<br />
[[File:Linux_mint.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=mint<br />
<br />
http://linuxmint.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
this info comes from http://www.linuxmint.com/faq.php and it is the only place on the official website that I saw this info listed:<br />
<br />
Is Linux Mint suitable for companies?<br />
Yes. Although Linux Mint release new versions every 6 months, each release is supported for a year and a half. We also make periodic Long-Term Support (LTS) releases which are supported for a duration of 3 years and which are guaranteed to provide enough overlap to allow you to upgrade from one LTS release to the next.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Mint has a quality idea/feedback system at http://community.Linuxmint.com/ that uses roughly a ticket based system for advancing new ideas, rating them, and marking them as rejected or accepted.<br />
This is different than their bug tracking, which is handled through launchpad, and from the forums in general I gathered that fixes go upstream to ubuntu.<br />
<br />
Documentation is unfortunately almost non-existent (the word 'documentation' does not appear on their website) but there are a series of tutorials on a wide variety of topics that are not necessarily related to mint that can be found at http://community.linuxmint.com/tutorial/search<br />
<br />
Hardware support information: there is an extensibly searchable supported hardware catalog that can be found at http://community.linuxmint.com/hardware<br />
check out the Type: 'Wifi car/adapter/dongle' (long list) page for an example<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* Recommended 1GHz 512MB RAM<br />
''from wikipedia''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Mint 12 and 9 supported until April 2013<br />
* Mint Debian: rolling distribution<br />
''from mint website''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* Mint 12 is based on ubuntu with a gnome environment. I installed and after a splash page comes up on the desktop that prompts you to download media and dvd codecs among other things like links to tutorials and other pages on the community website<br />
* Mint website says Mint Debian is neat because it is auto-updating - you never have to upgrade versions. but it is also therefore more unstable. It also reqs knowledge of the command line to enable one-touch-click on laptops and other similar things. They also says it is like ubuntu but rough around the edges.<br />
<br />
===Ubuntu===<br />
[[File:Ubuntu.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=ubuntu<br />
<br />
http://www.ubuntu.com/<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
from http://www.ubuntu.com/project/about-ubuntu<br />
<br />
The Ubuntu team broke new ground in committing to a programme of scheduled releases on a predictable six-month basis. It was decided that every fourth release, issued on a two-year basis, would receive long-term support (LTS). LTS releases are typically used for large-scale deployments.<br />
<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Documentation seems unfortunately bloated and confusing; each page has many more pages linked, and it is difficult to find specific info. Official Documentation for 12.04 is four clicks in from main site in a difficult to navigat manner, and can be found at https://help.ubuntu.com/12.04/ubuntu-help/index.html.<br />
This is distinct from the 'community wiki' documentation, which is also hard to navigate, somewhat redundant with the official docs.<br />
<br />
Hardware: from either the official or community wiki docs, there are sections about hardware support, but I had a difficult time and found little useful information.<br />
<br />
There are many many ubuntu local chapters, but this user has been involved with our Oregon branch, and while I have met people who have worked with fg, I have not really met any fg end-users at the meetings (posted ~06/12)<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):'''<br />
<br />
===Debian===<br />
<br />
http://debian.org<br />
<br />
'''Info for refining distro selection: {'''<br />
<br />
'''release cycle:'''<br />
<br />
Debian has three branches (stable, unstable, experimental) and do not have a set release cycle. <br />
Recent releases have occurred slightly under once every two years.<br />
<br />
The current testing branch, wheezy, has a freeze scheduled for end of June 2012, and a release <br />
is feasible by the end of 2012.<br />
<br />
Security support on the old stable release is maintained for 1 additional year beyond the <br />
current stable release.<br />
<br />
'''maintainability(stability, community support for distro etc.):'''<br />
<br />
Stability: In this users experience (John Parker), Debian 6.0 incredibly stable and is at least twice as stable in frequency of errors/conflicts compared to ubuntu, but sometimes it has been difficult setting processes up for the first time (wireless for example)<br />
<br />
Documentation: http://www.debian.org/doc/<br />
There are many manuals, howtos, faqs, and guides, but it seems that you have to know what section you are looking for more than what problem you are having.<br />
<br />
Community: There is a large developer community, but it may be difficult to approach from and end-user standpoint, though Debian goes to great lengths to allow it's users to feel encouraged to troubleshoot their own issues.<br />
<br />
'''}'''<br />
<br />
<br />
'''Distro Parent: None'''<br />
'''Minimum System Requirements:'''<br />
'''Package Manager:'''<br />
'''Release Cycles (if applicable):'''<br />
'''Standard Desktop Environment:'''<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
Support Cycle:<br />
* 1 year past previous release, new release approximately every 2 years.<br />
* freeze for next release(wheezy), June 2012, release hopefully by end of 2012.<br />
<br />
===Fedora===<br />
<br />
'''Distro Parent:''' RedHat<br />
<br />
'''Minimum System Requirements:'''<br />
* 10GB drive space<br />
* 1G RAM<br />
* 400MHz Pentium Pro or later (Also works on AMD, Cyrix and VIA<br />
<br />
'''Package Manager:''' Yum<br />
<br />
'''Release cycle:''' every 6 months. Last release (fedora 16) was on 11/08/2011<br />
<br />
'''Standard Desktop environment:''' Gnome <br />
Nisha: Actually during installation of Fedora 16, Gnome 3 gets natively installed. However, most probably the graphics cards or drivers that we would use would not support Gnome 3 so it will fail install and go to a "fallback" mode. At this point the CD goes live. We could probably get this to not happen during installation.<br />
<br />
'''Documentation:'''<br />
* http://fedoraproject.org/<br />
* https://fedoraproject.org/wiki/Fedora_Project_Wiki<br />
<br />
'''Comments:'''<br />
Nisha: <br />
* Some trouble installing it but did manage to install it. It comes with a minimal amount of extra software installed but comes with yum to install other packages as needed. From experience I know that it is not straightforward but I think it is customizable to our requirements if we write a script to make changes and install packages. For example, a user cannot use sudo unless they add their user name to the wheel group.<br />
Nisha: By default, SELinux is enabled which might be irritating to users. All the usual apps that you would expect to see are there under the Applications section. That means it's still difficult to find the software that you had just installed :P<br />
<br />
===OpenSuSe===<br />
[[File:OpenSUSE-icon.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=suse<br />
<br />
http://www.opensuse.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* ( Supported by Novell. )<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
[[File:Zed.png]]<br />
zed:<br />
<br />
<font size="-2">updated: 01/06/11</font><br />
<br />
<span style="background:#AFEEEE">'''+''': Install is very customizable and works with multiple monitor setups. Networking, sound and many other options can be configured at the time of installation. Gives the option to install either Gnome, KDE and few lesser known GUIs on installation. Most features work out of the box.<br />
</span><br />
<br />
<span style="background:#D3D3D3">'''-''': Software Package Management system not as easy to use as other distros. A few minor glitches on the GUI. Website can be difficult to navigate for help.<br />
</span><br />
<br />
== (rest of) The List==<br />
<br />
===Arch===<br />
[[File:Arch-linux.png]]<br />
<br />
http://distrowatch.com/table.php?distribution=arch<br />
<br />
http://www.archlinux.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* (not listed)<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Rolling<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
'''Comments:'''<br />
<br />
John:<br />
* For advanced users familiar with the CLI and the layout of their system. Installation is robust and ncurses based; user must make many specific choices. Also, once installed, boots to CLI first, no GUI installed by default, must install and start x manually. ''research from arch website''<br />
<br />
===CentOS===<br />
[[File:Centos_icon_60_normal.jpg]]<br />
<br />
http://distrowatch.com/table.php?distribution=centos<br />
<br />
http://www.centos.org/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
* Minimum v5 - 256MB Ram<br />
* Minimum v6 - 512MB Ram<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
* Version 5 - until March 2014<br />
* Version 6 - until November 2017<br />
''from centOS FAQ''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
=== PCLinuxOS===<br />
<br />
http://distrowatch.com/table.php?distribution=pclinuxos<br />
<br />
http://www.pclinuxos.com/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Puppy===<br />
<br />
http://distrowatch.com/table.php?distribution=puppy<br />
<br />
http://www.puppylinux.com/<br />
<br />
Support Cycle:<br />
* Wary and Racy puppy are both LTS (duration not stated)<br />
<br />
System Reqs:<br />
* (not listed) though Puppy is intended NOT TO BE INSTALLED TO HD<br />
* it is intended to run off of a LiveCD AND the process to install to HD is long and obscure<br />
<br />
Comments JP:<br />
* website is hard to follow<br />
* not much community support<br />
<br />
===Mageia===<br />
<br />
http://distrowatch.com/table.php?distribution=mageia<br />
<br />
http://www.mageia.org/<br />
<br />
Support Cycle: <br />
* (UNDECIDED)<br />
* Mageia is a Mandriva fork that is 9 months old (brand new)<br />
<br />
System Reqs: <br />
* 512MB RAM min - 2GB recommended<br />
* 6GB HD for full install<br />
<br />
===Mandriva===<br />
<br />
http://distrowatch.com/table.php?distribution=mandriva<br />
<br />
http://www.mandriva.com/<br />
<br />
Support Cycle:<br />
* Mandriva 2011 end support cycle is undecided, but will be after Dec 2012<br />
<br />
System Reqs:<br />
* Mandriva 2011 Reqs. min 1GB Ram<br />
<br />
===Lubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=lubuntu<br />
<br />
http://lubuntu.net/<br />
<br />
Support Cycle:<br />
* 11.10 will be supported until April 2013. It is the first official release as part of the Ubuntu cycle.<br />
<br />
System Reqs:<br />
* A Pentium II or Celeron system with 128 MB of RAM is probably a bottom-line configuration that may yield slow yet usable system with Lubuntu. It should be possible to install and run Lubuntu with less memory, but the result will likely not be suitable for practical use. ''from lubuntu website''<br />
<br />
===Kubuntu===<br />
<br />
http://distrowatch.com/table.php?distribution=kubuntu<br />
<br />
http://www.kubuntu.org/<br />
<br />
Support Cycle:<br />
* (not listed) it appears to follow Ubuntu's support cycle<br />
<br />
System Reqs:<br />
* (not listed) but it is ubuntu with KDE and some different applications<br />
<br />
===Sabayon===<br />
<br />
http://distrowatch.com/table.php?distribution=sabayon<br />
<br />
http://www.sabayon.org/<br />
<br />
Support Cycle:<br />
* Rolling Release ''from Sabayon wiki 'Info' Page''<br />
<br />
System Reqs:<br />
* 512 MB of RAM (1 GB suggested) ''from FAQ''<br />
* Minimum of 12 GB of free hard disk space for KDE and GNOME. ''from FAQ''<br />
<br />
Comments JP:<br />
* Based on Gentoo<br />
* Uses Entropy OR Portage Package Management<br />
* Robust website<br />
<br />
===Chakra===<br />
<br />
http://distrowatch.com/table.php?distribution=chakra<br />
<br />
http://chakra-linux.org/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Forked from Arch<br />
* KDE desktop<br />
<br />
===Zorin OS===<br />
<br />
http://distrowatch.com/table.php?distribution=zorin<br />
<br />
http://www.zorin-os.com/<br />
<br />
Support Cycle:<br />
<br />
System Reqs:<br />
<br />
Notes:<br />
* Ubuntu-based<br />
* designed for linux new-comers ''-taken from distrowatch page''<br />
* windows-like GUI<br />
* Includes Wine-like functionality<br />
<br />
===Ultimate===<br />
<br />
http://distrowatch.com/table.php?distribution=ultimate<br />
<br />
http://ultimateedition.info/<br />
<br />
'''Distro Parent:'''<br />
<br />
'''Minimum System Requirements:'''<br />
<br />
'''Package Manager:'''<br />
<br />
'''Release Cycles (if applicable):'''<br />
<br />
'''Standard Desktop Environment:'''<br />
<br />
'''Documentation (links to wikis, forums, etc):''' <br />
<br />
===Bodhi===<br />
<br />
http://distrowatch.com/table.php?distribution=bodhi<br />
<br />
http://www.bodhilinux.com/<br />
<br />
===Fuduntu===<br />
<br />
http://distrowatch.com/table.php?distribution=fuduntu<br />
<br />
http://www.fuduntu.org/<br />
<br />
Support Cycle:<br />
* (not stated on website)<br />
<br />
System Reqs: <br />
* 900MHz<br />
* 384 MB RAM<br />
* 5GB HD<br />
<br />
===ClearOS===<br />
<br />
http://distrowatch.com/table.php?distribution=clearos<br />
<br />
http://www.clearfoundation.com/<br />
<br />
''NOTE: This is a network server/gateway configurable from web<br />
<br />
===Joli OS===<br />
<br />
http://distrowatch.com/table.php?distribution=jolios<br />
<br />
http://www.jolicloud.com/<br />
<br />
[[Category:Distro]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Winter/Spring_2012_Inservice_Trainings&diff=61626Winter/Spring 2012 Inservice Trainings2012-03-11T02:09:41Z<p>Vagrant: /* Workshops scheduled for 3:30-5:30pm March 13 */ added times and locations</p>
<hr />
<div>The Free Geek board, in conjunction with staff liaisons, are planning an In-service for Winter/Sring 2012 to conduct trainings, board/all-staff meetings, and generally facilitate open communication and strategic planning discussions (dates and related logistics TBA). Following is a list of proposed trainings, categorized by relevant department/committee. <br />
<br />
<br />
All paid workers should feel free to edit this page directly to add training topics that are required to fulfill their job descriptions and their general ability to navigate Free Geek processes, systems, policies and communication channels. (If you want to add something but lack the wiki editing training to do so, email your additions to alamb@freegeek.org.)<br />
<br />
<br />
=Administrative Services=<br />
;Closing the tills - Michael<br />
:All front desk and thrift store staff<br />
<br />
;IOU/Reimbursement and misc. cash-ins - Michael<br />
:All front desk and thrift store staff<br />
<br />
;Database training - Richard<br />
:Adrienna - Gregory - Misty - Mark - Patrick - Jake - Cliff F - Sarah - John M - Omar <br />
<br />
;Wiki Paul<br />
:Adrienna - Gregory - Misty - Patrick - Jake - Lynnae - Cliff F<br />
<br />
;RT Paul<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - Jake - Sarah - John M <br />
<br />
;Talon Paul<br />
:Misty - Mark - Patrick - Cliff F - Sarah - John M <br />
<br />
;Wordpress Paul <br />
:Adrienna - Greg - John McNamee - Misty - Sarah - Ebeth - Cliff F - Patrick - Jake - Liliana G - Elizabeth - Lynnae<br />
<br />
;Alarm system issues - Richard<br />
:Cliff F - John A - Liliana - Sarah<br />
<br />
;Closing training - Darren<br />
:Cliff F - Mark - Omar V<br />
<br />
;Routing the mail - Richard <br />
<br />
;Budget and spending - Richard<br />
:Everyone<br />
<br />
;Scheduling, How to request changes, etc. -- Mark will do<br />
:Everyone<br />
<br />
;Breaks how to make sure you get them -- Mark will do<br />
:Everyone<br />
<br />
;How to call in sick -- Mark will do<br />
:Everyone<br />
<br />
;Your rights at work and how to deal with them -- Mark will do<br />
:Everyone<br />
<br />
;Confidentiality -- Mark will do<br />
:Everyone<br />
<br />
;PTO -- Mark will do<br />
:Everyone<br />
<br />
;Understanding your benefits -- Mark will do<br />
:Everyone<br />
<br />
;FAQ from info@ (how to reply to info@ emails)<br />
:Misty<br />
<br />
;Free Geek elevator speeches (PR Committee will conduct this.)<br />
:Adrienna - Gregory - Mark - Sarah - Omar<br />
<br />
;Free Geek Website Redesign - PR Committee<br />
:Darren - Amelia - Misty - Omar<br />
<br />
;Decision-making; policy and management structure of FG<br />
:Everyone (this will be discussed during the all-staff meeting on the 28th.)<br />
<br />
;Meeting facilitation - led by Amelia<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - John A - Jake - Sarah - John M - Elizabeth - Lynnae - Omar<br />
<br />
;Meeting scribing - Sean<br />
:Patrick - Jake - Cliff F - Sarah - John M - Omar<br />
<br />
=Recycling & Receiving=<br />
;Oregon eCycles -Liane<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - Sarah - John M - Vagrant - Lynnae<br />
<br />
;Tallying and Inventory - Michael<br />
:Adrienna - Gregory - Misty - Darren - Cliff F - Sarah - John M <br />
<br />
;Data security - Vagrant<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Sarah - John M<br />
<br />
;Receiving support (how to best provide backup during a Receiving rush) - Misty, Sarah<br />
:Adrienna - Gregory - Darren - Mark - John A - John M - Lynnae - Cliff F<br />
<br />
=VETS (Volunteer, Education, Tech Support)=<br />
;86ing people (what's the process/policy) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - Patrick - John A - Sarah<br />
<br />
;Volunteer management training - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Patrick - John A - Sarah - John M - Elizabeth<br />
<br />
;Training on Training (Education) - Darren<br />
:Adrienna - Gregory - Misty - Patrick - Sarah - John M - Amelia<br />
<br />
;Tours - Stephen<br />
:Adrienna - Gregory - Mark - Liliana G - Sarah - Amelia<br />
<br />
;Accessibility (how to accomodate different abilities and needs) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Mark - John A - Sarah - John M<br />
<br />
;Discrimination (FG policies and procedures) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - John A - Sarah -John M - Lynnae<br />
<br />
;Diversity awareness/sensitivity training, volunteers with disabilities - Stephen and/or HR<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Sarah - John M<br />
<br />
=Safety Committee=<br />
;Safety training, including proper lifting techniques - Darryl<br />
:Everyone<br />
<br />
;Fire drill<br />
:Everyone<br />
<br />
;Emergency medical things<br />
:Everyone<br />
<br />
;mental health awareness<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - John A - Sarah - John M<br />
<br />
;CPR<br />
:Adrienna - Gregory - Misty - John M - Lynnae<br />
<br />
;De-escalation and ombudsman usage<br />
:Adrienna - Gregory - Cliff F - Misty - Mark - John A - Liliana G - Sarah - John M - Lynnae<br />
<br />
;First Aid stations (what's there, how to use them) - Liane<br />
:Everyone<br />
<br />
=Organizational issues=<br />
;Hiring goals/priorities<br />
:Everyone (this will be discussed at the all-staff meeting.)<br />
<br />
;Understanding the Union Contract (for both union and non-union folks) - Vagrant and Ebeth<br />
:Everyone<br />
<br />
=Area Check-Ins/Meetings=<br />
;Sales/Reuse/Production check-in: What the store (also online/bulk sales?) needs and wants. Maybe should involve Receiving as well.<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Liliana G - Sarah - John M - Elizabeth - Lynnae<br />
<br />
;Production identity investigation: What does this committee do, how is the Sales staff involved.<br />
:Adrienna - Gregory - Misty - Liliana G - John M - Elizabeth - Lynnae<br />
<br />
;Receiving flow: clarify gizmo flow between Receiving, Store and Warehouse.<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - John A - Liliana G - Sarah - John M - Lynnae<br />
<br />
=Admin Time=<br />
Template: [Name: # of hours requested]<br />
<br />
Amelia: 3 hours<br />
<br />
Mark: 2/21 4 hours for payroll | 3/6 4 hours for payroll | will be coming in for 8 AM, so maybe admin time will get calculated at a lower #<br />
<br />
Lynnae: 2.5 hours<br />
<br />
=Workshops scheduled for 3:30-5:30pm March 13=<br />
<br />
Group 1 (3:30-4:30, classroom). Decision-Making Processes at Free Geek: How the chart that the VETS group created at the All-Staff Meeting might play out in practice, and how it can be implemented in other areas and across the organization. <br />
*Attending: Sarah, Stephen, Paul, Richard, Adrienna, Brian, Gregory, Omar, John A., Misty, Patrick<br />
<br />
Group 2 (3:30-4:30, meeting room). 360-Degree Staff Reviews: How to incorporate Bargaining Unit member feedback into Collective-level reviews, and who should participate in which reviews, so that feedback is holistically and fairly represented. <br />
*Attending: Amelia, Darren, Mark, Aradan, Darryl, Santiago<br />
<br />
Group 3 (4:35-5:30, classroom). Major-Minor Supervisor Communications: Whether staff with both a "major" and a "minor" should have an official minor supervisor, and if so, how the major and minor supervisors should interact in order to avoid complications with scheduling, performance expectations, etc. <br />
*Attending: Stephen, Sean, Richard, Adrienna, Gregory, Liane, Brian, Cynthia, John A, Cliff.<br />
<br />
Group 4 (4:35-5:30, meeting room). Bargaining Unit Discipline Policy: Adopting a parallel policy to the discipline policy recently adopted within the Collective, with consideration to the agreements already set in the Collective Bargaining Agreement. <br />
*Attending: Sarah, Amelia, Darren, Mark, Aradan, Omar, Misty, Santiago<br />
<br />
[[Category:Inservice Trainings]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Winter/Spring_2012_Inservice_Trainings&diff=61191Winter/Spring 2012 Inservice Trainings2012-02-15T01:28:52Z<p>Vagrant: /* Recycling & Receiving */ sign myself up for some stuff</p>
<hr />
<div>The Free Geek board, in conjunction with staff liaisons, are planning an In-service for Winter/Sring 2012 to conduct trainings, board/all-staff meetings, and generally facilitate open communication and strategic planning discussions (dates and related logistics TBA). Following is a list of proposed trainings, categorized by relevant department/committee. <br />
<br />
<br />
All paid workers should feel free to edit this page directly to add training topics that are required to fulfill their job descriptions and their general ability to navigate Free Geek processes, systems, policies and communication channels. (If you want to add something but lack the wiki editing training to do so, email your additions to alamb@freegeek.org.)<br />
<br />
<br />
=Administrative Services=<br />
;Closing the tills - Michael<br />
:All front desk and thrift store staff<br />
<br />
;IOU/Reimbursement and misc. cash-ins - Michael<br />
:All front desk and thrift store staff<br />
<br />
;Database training - Richard<br />
:Adrienna - Gregory - Misty - Mark - Patrick - Jake - Cliff F - Sarah - John M<br />
<br />
;Wiki Paul<br />
:Adrienna - Gregory - Misty - Patrick - Jake<br />
<br />
;RT Paul<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - Jake - Sarah - John M <br />
<br />
;Talon Paul<br />
:Misty - Mark - Patrick - Cliff F - Sarah - John M <br />
<br />
;Wordpress Paul <br />
:Adrienna - Greg - John McNamee - Misty - Sarah - Ebeth - Cliff F - Patrick - Jake - Liliana G<br />
<br />
;Alarm system issues - Richard<br />
:Cliff F - John A - Liliana - Sarah<br />
<br />
;Closing training - Darren<br />
:Cliff F - Mark<br />
<br />
;Routing the mail - Richard <br />
<br />
;Budget and spending - Richard<br />
:Everyone<br />
<br />
;Scheduling, How to request changes, etc. -- Mark will do<br />
:Everyone<br />
<br />
;Breaks how to make sure you get them -- Mark will do<br />
:Everyone<br />
<br />
;How to call in sick -- Mark will do<br />
:Everyone<br />
<br />
;Your rights at work and how to deal with them -- Mark will do<br />
:Everyone<br />
<br />
;Confidentiality -- Mark will do<br />
:Everyone<br />
<br />
;PTO -- Mark will do<br />
:Everyone<br />
<br />
;Understanding your benefits -- Mark will do<br />
:Everyone<br />
<br />
;FAQ from info@ (how to reply to info@ emails)<br />
:Misty<br />
<br />
;Free Geek elevator speeches (PR Committee will conduct this.)<br />
:Adrienna - Gregory - Mark - Sarah<br />
<br />
;Decision-making; policy and management structure of FG<br />
:Everyone (this will be discussed during the all-staff meeting on the 28th.)<br />
<br />
;Meeting facilitation - led by Amelia<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - John A - Jake - Sarah - John M <br />
<br />
;Meeting scribing - Sean<br />
:Patrick - Jake - Cliff F - Sarah - John M<br />
<br />
=Recycling & Receiving=<br />
;Oregon eCycles -Liane<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - Sarah - John M - Vagrant<br />
<br />
;Tallying and Inventory - Michael<br />
:Adrienna - Gregory - Misty - Darren - Cliff F - Sarah - John M <br />
<br />
;Data security - Vagrant<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Sarah - John M<br />
<br />
;Receiving support (how to best provide backup during a Receiving rush) - Misty, Sarah<br />
:Adrienna - Gregory - Darren - Mark - John A - John M<br />
<br />
=VETS (Volunteer, Education, Tech Support)=<br />
;86ing people (what's the process/policy) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - Patrick - John A - Sarah<br />
<br />
;Volunteer management training - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Patrick - John A - Sarah - John M<br />
<br />
;Training on Training (Education) - Darren<br />
:Adrienna - Gregory - Misty - Patrick - Sarah - John M <br />
<br />
;Tours - Stephen<br />
:Adrienna - Gregory - Mark - Liliana G - Sarah<br />
<br />
;Accessibility (how to accomodate different abilities and needs) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Mark - John A - Sarah - John M<br />
<br />
;Discrimination (FG policies and procedures) - Stephen<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Mark - John A - Sarah -John M<br />
<br />
;Diversity awareness/sensitivity training, volunteers with disabilities - Stephen and/or HR<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Sarah - John M<br />
<br />
=Safety Committee=<br />
;Safety training, including proper lifting techniques - Darryl<br />
:Everyone<br />
<br />
;Fire drill<br />
:Everyone<br />
<br />
;Emergency medical things<br />
:Everyone<br />
<br />
;mental health awareness<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - John A - Sarah - John M<br />
<br />
;CPR<br />
:Adrienna - Gregory - Misty - John M <br />
<br />
;De-escalation and ombudsman usage<br />
:Adrienna - Gregory - Cliff F - Misty - Mark - John A - Liliana G - Sarah - John M<br />
<br />
;First Aid stations (what's there, how to use them) - Liane<br />
:Everyone<br />
<br />
=Organizational issues=<br />
;Hiring goals/priorities<br />
:Everyone (this will be discussed at the all-staff meeting.)<br />
<br />
;Understanding the Union Contract (for both union and non-union folks) - Vagrant and Ebeth<br />
:Everyone<br />
<br />
=Area Check-Ins/Meetings=<br />
;Sales/Reuse/Production check-in: What the store (also online/bulk sales?) needs and wants. Maybe should involve Receiving as well.<br />
:Adrienna - Gregory - Cliff F - Misty - John A - Liliana G - Sarah - John M <br />
<br />
;Production identity investigation: What does this committee do, how is the Sales staff involved.<br />
:Adrienna - Gregory - Misty - Liliana G - John M <br />
<br />
;Receiving flow: clarify gizmo flow between Receiving, Store and Warehouse.<br />
:Adrienna - Gregory - Cliff F - Misty - Darren - Patrick - John A - Liliana G - Sarah - John M<br />
<br />
<br />
=Admin Time=<br />
Template: [Name: # of hours requested]<br />
<br />
Amelia: 3 hours<br />
<br />
Mark: 2/21 4 hours for payroll | 3/6 4 hours for payroll | will be coming in for 8 AM, so maybe admin time will get calculated at a lower #<br />
<br />
<br />
[[Category:Inservice Trainings]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Education_Program_Ideas&diff=61176Education Program Ideas2012-02-11T00:58:05Z<p>Vagrant: /* Advanced tech classes grocery list */ add link to openpgp best practices</p>
<hr />
<div>==New Course Ideas==<br />
* '''Advanced Adoption Courses''' (Open Office, GIMP, Tech Support Courses)<br />
<br />
* '''Staff and Volunteer Teacher Training''' (Teaching the Teachers how to Teach!)<br />
<br />
* '''Keyboarding Classes Using Free Online Software''' (This could help to prepare for typing tests required for certain lines of work, and prepare students for various educational opportunities at FREE GEEK)<br />
<br />
* '''Problem-Based Command Line Course''' (To Follow Basic Command Line and Advanced Command Line...Rob Love said he would be interested in teaching a problem-based course every other time he is here) '''In Progress! Yes!'''<br />
<br />
<br />
==Advanced tech classes grocery list==<br />
Please prioritize level of interest/importance/need using exclamation points (!, !! or !!!=ultra important; for example: !!! Problem-based command line course)<br />
<br />
* '''Disk Management'''<br />
** RAID<br />
** LVM<br />
** Disk encryption<br />
<br />
* '''Security Best Practices'''<br />
** Secure passphrase hygiene and management (!!!)<br />
** SSH (!!)<br />
** [http://gnupg.org GnuPG] (!!) <br />
*** [https://we.riseup.net/riseuplabs+paow/openpgp-best-practices OpenPGP Best Practices]<br />
*** [http://web.monkeysphere.info monkeysphere]<br />
<br />
* '''Why secure web browsing is broken'''<br />
** [http://convergence.io convergence]<br />
** [http://networknotary.org perspectives]<br />
** [http://patrol.psyced.org/ certificate patrol]<br />
** [http://web.monkeysphere.info monkeysphere]<br />
<br />
* '''Miscellaneous'''<br />
** screen and byobu<br />
<br />
* '''Free Software Development'''<br />
** Bug reporting<br />
** [[Basic Debian Packaging]]<br />
** [[Debian_Package_Repositories]]<br />
** [[Nice_Version_Control|Version Control Systems]]<br />
*** [[Git_for_dummies|git]]<br />
*** [[Subversion_for_Coders|svn]]<br />
*** [[Bzr_Intro|bzr]]<br />
*** [http://mercurial.selenic.com/ hg]<br />
<br />
* '''Administration Basics'''<br />
** [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard (!!!)] I taught a workshop on this last year and have notes I believe [[User:Paulm|paulm]] 01:51, 26 January 2012 (UTC)<br />
** Intro to vi/vim (!)<br />
** User/Group Management, sudo, and sudoers (!!)<br />
** Reading and configuring system logs (!!)<br />
** Compiling from source (!)<br />
** Commands you should know (!!!)<br />
*** tar, du, df, mount, watch, find, shred, rsync, route, nslookup, host, ifconfig, iwconfig, dmesg, ps, pstree, pgrep, kill, pkill, w, lastlog, faillog, lspci, lsmod, modprobe<br />
** Intro to bash scripting (!!) (I taught this class a couple of years ago and still have it all ready to go again (see http://www.gatheringstorms.org/wiki/doku.php?id=bash_course) [[User:Paulm|paulm]] 01:51, 26 January 2012 (UTC)). <br />
** Scheduling events (at, cron, anacron) (!!)<br />
** Configuring Apache and Hosting your own Webpage (!!!)<br />
** Troubleshooting using logs & stderr (!!!)<br />
<br />
* '''Power User Goodies'''<br />
** Advanced vim usage (!)<br />
** Terminal multiplexers (screen, tmux) (!)<br />
** IRC (!!)<br />
** Life in the Console (e-mail clients, task managers, calendars, web-browsing, etc) (!)<br />
<br />
* '''Tech Support Trainings'''<br />
** Network backups and restores (!!!)<br />
** Fundamentals of Troubleshooting (!!!)<br />
*** Envisioning this as a multi-part training starting with concepts and then a series of example situations and problems, culminating in an exam-like session<br />
** How to Root a Box (Or 'Why We Never Need to Know a Password') (!!!)<br />
** User Relations (Or 'How I Learned to Stop Worrying and Love the Phone') (!!!)<br />
<br />
==I would like to Work on/Improve==<br />
<br />
* '''Follow-up:'''<br />
**'''Certifications/Graduation/Sense of Accomplishment for Students''' <br />
**'''Retention''' - we keep them coming back, and they keep the knowledge acquired<br />
**'''Surveys''' - I am interested in the response to the prompt: What did you learn? How do people explain what they have learned? How does Free Geek prepare people for different jobs/educational opportunities/hobbies?<br />
<br />
* '''Curriculum''' - Can our substitute teachers step in and teach a course with ease?<br />
<br />
* '''Classroom Space'''<br />
**'''Stock of Paper/Pens in classroom'''<br />
**'''Aesthetics and acoustics of classroom''' <br />
**'''Course Objectives in each learning area''' – The objectives posted in pre-build are wonderful. I want to post station-specific objectives throughout FREE GEEK. <br />
**'''Explanation of flow-charts and how to use them!''' For those who have NEVER used a flow chart before, mastering a new tool and new vocabulary at the same time can be overwhelming. If we teach the tool (flow-Charts) using familiar vocabulary, then the learner can plug new information into a familiar tool and feel less intimidated. (See Ali's sample flow chart on her wiki page...something along those lines could be helpful)<br />
**'''Spell out Colors on Color-Coded Flow-Charts''' This is just one more tool to help people know where they are supposed to be looking! I want to spell colors out because some people are color-blind and some people are just not very observant (example: I didn't notice charts were color-coded until it was pointed out to me).<br />
* '''Use Moodle for Course Syllabi''' <br />
<br />
==Some Questions==<br />
What do we have to offer people who finish build? How do we keep them at FREE GEEK and challenge them appropriately?<br />
* we currently have 4 options: (they all take there own type of special person)<br />
** Advanced testing, testing harddrives, memory, procs & mobos, cdburner & dvd players, and various cards.<br />
** laptops, set up just like build, the hardware is much more intricate <br />
** Macs (apple), also set up just like build, the hardware is easier to teach and deal with.<br />
** build teaching, assisting: this is an option in all the build areas.<br />
<br />
[[Category:Education]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Technical_infrastructure_checklist&diff=61101Technical infrastructure checklist2012-02-09T19:16:15Z<p>Vagrant: /* Software and Systems */ updated expire dates on imaps/https certs.</p>
<hr />
<div>Resources on this list should be checked regularly to see that they are in working order.<br />
= During "walkthrough" =<br />
== Services ==<br />
''italicized text is checked on a per room basis''<br />
=== Software and Systems ===<br />
* Check each server up and up-to-date? http://monitor/cgi-bin/nagios3/tac.cgi<br />
** HINT: A report is also emailed to asswatch every night at midnight. If you want to use the command line, there are three scripts: list_problems (lists everything that has a problem, and what that problem is), down (lists down servers), and needs_upgrading (lists servers that need to be "aptitude dist-upgrade"ed). These scripts live on monitor.<br />
* web services administration (wiki, todo, dev/svn, dev/projects, mail, www, others...)<br />
** clarification needed: what part of these services need checking?<br />
** integrate this with nagios? [[User:Ryan52|Ryan]] will look into what can and needs to be integrated. (any service marked with http seems to get checked by nagios)<br />
* check if there are any [http://todo.freegeek.org/Search/Results.html?Query=Requestor%20LIKE%20%27ass-security%27%20AND%20(Status%20=%20%27open%27%20OR%20Status%20=%20%27new%27) open security announcement tickets].<br />
** HINT: Search for open RT tickets created by ass-security@our_domain. If you like the command line, then you can use this (mainly self explanatory, just run it) script: ./ass/scripts/security/show_security<br />
* certificate and gpg key expiration dates<br />
** check the https and imaps ssl certs (renewed February 2012, expires February 2014)<br />
*** openssl x509 -in /path/to/certificate -noout -text<br />
** check apt signing key (expires January, 2014)<br />
* check to see if our mail server(s) have been blacklisted:<br />
** http://www.dnsbl.info/dnsbl-database-check.php<br />
** http://www.anti-abuse.org/multi-rbl-check-results/?host=67.51.72.37<br />
* off-site backups are current<br />
* on-site backups are current<br />
<br />
=== Servers & Security ===<br />
* [http://cameras.fglan/zm/ Security cameras]<br />
** Software set up correctly and running.<br />
** ''pointing in correct direction''<br />
* visual inspection<br />
** look for things like bad fans on servers<br />
** dust/vaccuum servers, switches<br />
** look dangerous cable tangles, stress/tension on punched-down cables<br />
* UPS check<br />
** Tests successfully<br />
** Balanced load<br />
** Battery installation within 3 years<br />
* kill-a-watt monitoring<br />
** log the current server's kilowatt's for the past cycle<br />
** move kill-a-watt to new server<br />
* Look for rogue wireless access points (quarterly: september 2011)<br />
** trace all cables connected to:<br />
*** credit card machine network<br />
*** wireless network<br />
** [http://todo.freegeek.org/Ticket/Display.html?id=20057#txn-254415 policy and procedure discussion]<br />
<br />
=== Phones ===<br />
* ''All listed phones working'' (listed where?)<br />
<br />
=== Printers ===<br />
* ''are there paper jams (walk around)''<br />
* ''are they free of non-standard paper''<br />
* ''are they all running under [[http://scribble:631 cups]]''<br />
<br />
=== hubs/switches/networking ===<br />
* ''check network ports around room''<br />
* ''check for bad fans''<br />
<br />
== Rooms ==<br />
=== Meeting Room ===<br />
* Projector<br />
* Network hub (plugged into wall correctly)<br />
* Phone (plugged in?)<br />
<br />
=== Classroom ===<br />
* All terminals<br />
* Printer<br />
* networking around room<br />
* Wireless access point<br />
<br />
=== Reception ===<br />
* Printer (toner low? paper?)<br />
* Terminals and monitors functioning well?<br />
<br />
=== upstairs and downstairs office ===<br />
* terminals<br />
* networking<br />
* phones<br />
<br />
=== Production ===<br />
* Advanced testing<br />
** lots of networking<br />
** testers functioning<br />
* build (+mac +laptop +enterprise)<br />
** networking<br />
** terminals and images.<br />
<br />
= Taken care of by somebody/something else =<br />
* watch all of the asswatch scripts, and makes sure that they are working. ([[User:Ryan52|Ryan]] does this)<br />
* rootmail cleanup/checkup ([[User:Ryan52|Ryan]]) and current owner of [http://todo.freegeek.org/Ticket/Display.html?id=10988 RT#10988]<br />
* check each server is listed in purpose (asswatch)<br />
* backups working on each server (asswatch)<br />
* check each server with maintenance notes and script, check rootmail is working ([[User:Ryan52|Ryan]] does this every so often, probably doesn't need to be done often)<br />
* Are all printers on, ready, and without stalled jobs?? (nagios)<br />
* mailing list moderation (handled by freegeek moderators)<br />
** reply to subscription requests to determine sentience<br />
* Outgoing Phone Message (handled by front desk)<br />
<br />
[[Category:Technocrats]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60852Do we want it for a server?2012-02-01T19:26:08Z<p>Vagrant: more explicit instructions</p>
<hr />
<div>this chart is meant to help instructors determine if systems should be recycled or sent to server build.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\nwe do not want it for a server\npull all hard drives\nsend to recycling, and\nmark it on the clipboard\nin the server section", shape="box", style="bold"]<br />
yes [label="YES\nwe want it for a server\nplace a Hard Drive Removed sticker\non it and take to server build", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
judge_no [label="Use your best judgement,\nbut we probably do not want it", shape="box", style="bold"]<br />
judge_yes [label="Use your best judgement,\nbut we probably want it", shape="box", style="bold"] <br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> pcie [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [taillabel="NO"]<br />
<br />
dell_verynice -> yes [taillabel="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [taillabel="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [taillabel="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [taillabel="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> judge_yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> judge_no [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60850Do we want it for a server?2012-02-01T19:20:44Z<p>Vagrant: /* Instructor Chart */ more nuanced judgement</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
judge_no [label="Use your best judgement,\nbut we probably don't want it", shape="box", style="bold"]<br />
judge_yes [label="Use your best judgement,\nbut we probably do want it", shape="box", style="bold"] <br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> pcie [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [taillabel="NO"]<br />
<br />
dell_verynice -> yes [taillabel="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [taillabel="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [taillabel="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [taillabel="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> judge_yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> judge_no [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60845Do we want it for a server?2012-02-01T19:08:16Z<p>Vagrant: /* Instructor Chart */ judgement</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
judge [label="Use your best judgement,\nbut we probably don't want it", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> pcie [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [taillabel="NO"]<br />
<br />
dell_verynice -> yes [taillabel="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [taillabel="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [taillabel="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [taillabel="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> judge [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60843Do we want it for a server?2012-02-01T19:02:33Z<p>Vagrant: /* Instructor Chart */ use taillabel liberally</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [taillabel="YES"]<br />
sata -> pcie [label="NO"]<br />
<br />
pcie -> yes [taillabel="YES"]<br />
pcie -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [taillabel="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [taillabel="NO"]<br />
<br />
dell_verynice -> yes [taillabel="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [taillabel="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [taillabel="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [taillabel="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> yes [taillabel="YES"]<br />
<br />
good_tower -> yes [taillabel="YES"]<br />
good_tower -> no [taillabel="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60838Do we want it for a server?2012-02-01T18:44:47Z<p>Vagrant: /* Instructor Chart */ add pci-e question</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
pcie [label="Does it have PCI-e slots?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> pcie [label="NO"]<br />
<br />
pcie -> yes [label="YES"]<br />
pcie -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
<br />
good_tower -> yes [label="YES"]<br />
good_tower -> no [label="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60709Do we want it for a server?2012-01-25T21:54:09Z<p>Vagrant: /* Instructor Chart */ added several other good tower brands</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
good_tower [label="Is it an HP, IBM\nor SuperMicro tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> good_tower [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
<br />
good_tower -> yes [label="YES"]<br />
good_tower -> no [label="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60700Do we want it for a server?2012-01-25T20:06:42Z<p>Vagrant: keep HP towers</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
hp_tower [label="Is it an HP tower?"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> hp_tower [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
<br />
hp_tower -> yes [label="YES"]<br />
hp_tower -> no [label="NO"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60696Do we want it for a server?2012-01-25T19:54:27Z<p>Vagrant: fix typo, formatting</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with\nR, T, C, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900,\n950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60695Do we want it for a server?2012-01-25T19:50:31Z<p>Vagrant: updated very nice dells</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with R, T, S, M or SC?\n(i.e. R300, T300, SC1435, C2100)"]<br />
dell_good [label="Model ending in 850, 900, 950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model matching 800, 830, 840,\n850, 860, 1800?"]<br />
dell_bad [label="Model ending in\n800 or less?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60694Do we want it for a server?2012-01-25T19:43:25Z<p>Vagrant: /* Instructor Chart */ add prettygood dell models</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with R, T or SC?\n(i.e. R300, T300, SC1435)"]<br />
dell_good [label="Model ending in 850, 900, 950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_prettygood [label="Model 800, 830, 840, 850, 860, 1800?"]<br />
dell_bad [label="Model ending in 450, 550,\n600, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_prettygood [label="NO"]<br />
<br />
dell_prettygood -> yes [label="YES"]<br />
dell_prettygood -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60692Do we want it for a server?2012-01-25T00:00:06Z<p>Vagrant: /* Instructor Chart */ dell poweredge 970 series are good, too</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with R, T or SC?\n(i.e. R300, T300, SC1435)"]<br />
dell_good [label="Model ending in 850, 900, 950 or 970?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550,\n600, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60691Do we want it for a server?2012-01-24T23:57:43Z<p>Vagrant: /* Instructor Chart */ formatting</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives\nhave been removed, then recycle it\nWITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with R, T or SC?\n(i.e. R300, T300, SC1435)"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550,\n600, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60690Do we want it for a server?2012-01-24T22:45:30Z<p>Vagrant: formatting</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker\nshowing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="Model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550,\n600, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA\nor SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60689Do we want it for a server?2012-01-24T22:34:52Z<p>Vagrant: /* Instructor Chart */ added poweredge 600 generation</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker showing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550,\n600, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA or SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60688Do we want it for a server?2012-01-24T21:38:53Z<p>Vagrant: </p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker showing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA or SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium\nII / III / IV"]<br />
sticker -> yes [label="Core2\nPentium D"]<br />
sticker -> sata [label="Xeon\nOpteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60687Do we want it for a server?2012-01-24T21:30:07Z<p>Vagrant: add ddr and sata questions</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker showing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
ddr [label="Does it use DDR ram?"]<br />
sata [label="Does it use SATA or SAS hard drives?"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium II / III / IV"]<br />
sticker -> yes [label="Core2, Pentium D"]<br />
sticker -> sata [label="Xeon / Opteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> sata [label="NO"]<br />
<br />
sata -> yes [label="YES"]<br />
sata -> ddr [label="NO"]<br />
<br />
ddr -> dell_poweredge [label="YES"]<br />
ddr -> no [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60686Do we want it for a server?2012-01-24T21:25:04Z<p>Vagrant: updated processors with stickers</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker showing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium II / III / IV"]<br />
sticker -> yes [label="Core2, Pentium D"]<br />
sticker -> dell_poweredge [label="Xeon / Opteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> dell_poweredge [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagranthttp://wiki.freegeek.org/index.php?title=Do_we_want_it_for_a_server%3F&diff=60685Do we want it for a server?2012-01-24T21:21:37Z<p>Vagrant: /* Instructor Chart */ add link to wikipedia article about dell poweredge models</p>
<hr />
<div>this chart is meant to help instructors determine if systems should get a hold for server or recycle label.<br />
<br />
== Instructor Chart ==<br />
<br />
<graphviz><br />
digraph D {<br />
<br />
node [fontname="Helvetica", fontsize="11"]<br />
edge [fontname="Helvetica"]<br />
<br />
start [label="START", shape="box", style="bold"]<br />
no [label="NO\n(we do not want it for a server)", shape="box", style="bold"]<br />
yes [label="YES\n(we want it for a server)\nPlace a HOLD FOR sticker and mark SERVER", shape="box", style="bold"]<br />
notcomp [label="Not a computer!\nMake sure all the hard drives have been removed,\nthen recycle it WITHOUT marking it on the cart", shape="box", style="bold"]<br />
<br />
sticker [label="Does it have a sticker showing what kind of processor it has?"]<br />
rackmount [label="Is it a Rackmount system?"]<br />
hdenc [label="Is it a hard drive enclosure?\n(Hard drive enclosures do not typically\nhave video, keyboard, or USB ports)"]<br />
dell_poweredge [label="Is it a Dell PowerEdge?"]<br />
dell_verynice [label="model starting with R, T or SC?\n(i.e. R300, T300, SC1435"]<br />
dell_good [label="Model ending in 850, 900 or 950?\n(i.e. 2850, 2900, 1950)"]<br />
dell_bad [label="Model ending in 450, 550, 650, 800?\n(i.e. 2450, 2650, 2800)"]<br />
<br />
start -> sticker<br />
<br />
sticker -> no [label="Pentium II / III"]<br />
sticker -> yes [label="Xeon / Opteron"]<br />
sticker -> hdenc [label="No sticker"]<br />
<br />
hdenc -> notcomp [label="YES"]<br />
hdenc -> dell_poweredge [label="NO"]<br />
<br />
dell_poweredge -> dell_verynice [label="YES"]<br />
dell_poweredge -> rackmount [label="NO"]<br />
<br />
dell_verynice -> yes [label="YES"]<br />
dell_verynice -> dell_good [label="NO"]<br />
<br />
dell_good -> yes [label="YES"]<br />
dell_good -> dell_bad [label="NO"]<br />
<br />
dell_bad -> no [label="YES"]<br />
dell_bad -> rackmount [label="NO"]<br />
<br />
rackmount -> no [label="NO"]<br />
rackmount -> yes [label="YES"]<br />
}<br />
</graphviz><br />
<br />
[http://en.wikipedia.org/wiki/List_of_Dell_PowerEdge_Servers List of Dell Poweredge Models]<br />
<br />
[[Category:Server Build]]</div>Vagrant