Resources/Noisecloud

From Noisebridge
< Resources(Difference between revisions)
Jump to: navigation, search
(Machines)
({{OutOfDate}})
 
(15 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{OutOfDate}}
 +
 
= Overview =
 
= Overview =
  
[[User:Dr_jesus|Dr. Jesus]] is running a project to use the endowment from OSDN/VA/geeknet to provide trade union style resources to Noisebridge members with a career in system and network administration.
+
[[User:Dr_jesus|Dr. Jesus]] is running a project to use the endowment from OSDN/VA/geeknet and other generous donors to provide trade union style resources to Noisebridge members with a career in system and network administration.
  
 
= Goals =
 
= Goals =
Line 17: Line 19:
 
= Machines =
 
= Machines =
  
Noisebridge has possession of many, many computers from OSDN and other donors.  About the first third of the machines have been colocated in Redwood CityTwo cabinets of machines have been set up and are connected to the InternetTalk to one of the people involved with the project to request access.
+
Noisebridge has possession of many, many computers from OSDN and other donors.  Talk to one of the people involved with the project to request access and/or volunteer for an ops shift or mentoring duty.
 +
 
 +
== Cloud Control ==
 +
 
 +
There is a bot named <tt>noisecloud</tt> in the #noisebridge IRC channel which provides some limited control over the machines.   
 +
 
 +
Machines are shut down every day at 3 AM and wipedMachines can be told to stay up persistently, see the cloud controller code for details.
 +
 
 +
== Running Services on Pilot Machines ==
 +
 
 +
For cost reasons, powering on the spare machines at each hosting site isn't done except in the case where Noisecloud is the only option available for hosting your project.  However, some non-dedicated capacity is available for noncommercial projects.
 +
 
 +
Each colocation site has one low power pilot machine which stays on 24x7 to provide local control over the other machines.  Although access to the pilot machine itself is restricted, most sites can run containers or virtual machines on their pilot machines.  To have a container or virtual machine started for you, send an SSH public key to [[User:Dr_jesus|Dr. Jesus]] and a brief description of what your needs are.  Only noncommercial uses of Noisecloud are permitted.
 +
 
 +
== Inventory ==
 +
 
 +
The current motherboard inventory is:
 +
 
 +
=== RWC ===
 +
    10 HDAMA-I   
 +
      2 S2721-533 Thunder i7501 Pro
 +
      1 S2735   
 +
      4 S2881 Thunder K8SR Mainboard
 +
      1 S5360   
 +
      2 S5360-1U   
 +
    11 SE7501BR2   
 +
      2 SE7501BR2S   
 +
    13 TYAN Tiger i7501 
 +
      1 Thunder I7520 
 +
      2 Thunder I7520R
 +
 
 +
There are also two Cyclades TS-1000 console servers, and one Cyclades TS-3000, one Foundry EdgeIron 9604 and one EdgeIron 4802.
 +
 
 +
=== AMT ===
 +
    13 Supermicro X7DCL
 +
      3 Dell PowerEdge 750
 +
    10 HP Proliant DL385
 +
      5 HP Proliant DL145
 +
 
 +
Connectivity is provided by a Foundry 24 port gigabit switch.
 +
 
 +
=== FMT ===
 +
 
 +
      9 Foundry EdgeIron II
 +
      6 HP Proliant DL380
 +
      2 HP Proliant DL380 G2
 +
      2 Rackable RaQ 3i
 +
      8 Rackable RaQ 2
 +
 
 +
=== HWD ===
 +
 
 +
      2 HP Proliant DL385 G5
 +
      1 Dell Poweredge T110
 +
      1 Dell Poweredge T100
 +
 
 +
=== Oakland ===
 +
 
 +
      1 HP Proliant DL585
 +
 
 +
=== Noisebridge ===
 +
 
 +
      1 Supermicro X7DCL
  
 +
== Additional Rackspace ==
 
Colocation for other Noisebridge projects is available for a limited number of machines subject to the following conditions:
 
Colocation for other Noisebridge projects is available for a limited number of machines subject to the following conditions:
  
 
* Servers must be used for non-commercial purposes only.   
 
* Servers must be used for non-commercial purposes only.   
  
* Services which do not have a reason to occupy an entire server are not allowed.  Such services can be containerized instead.
+
* Services which do not have a reason to occupy an entire server chassis by themselves are not allowed.  Such services can be containerized instead using lxc, UML, or any other technology supported by libvirt.
  
 
* Reliable ops contacts must be available for each server.
 
* Reliable ops contacts must be available for each server.

Latest revision as of 16:49, 5 July 2012

Oldcomputer.png
This article seems to be really old or very much out of date, and may contain wrong info.

Wiki-tip: You can check its history to see when it was last edited.

Contents

[edit] Overview

Dr. Jesus is running a project to use the endowment from OSDN/VA/geeknet and other generous donors to provide trade union style resources to Noisebridge members with a career in system and network administration.

[edit] Goals

  • Provide useful technical services to peer non-profit organizations.
  • Provide members with a constructive outlet for operational talent.
  • Provide practical, hands-on operations training services to members and the general public.
  • Provide development services for ops-related open source projects.
  • Represent the interests of the operational community to the general public.

[edit] Machines

Noisebridge has possession of many, many computers from OSDN and other donors. Talk to one of the people involved with the project to request access and/or volunteer for an ops shift or mentoring duty.

[edit] Cloud Control

There is a bot named noisecloud in the #noisebridge IRC channel which provides some limited control over the machines.

Machines are shut down every day at 3 AM and wiped. Machines can be told to stay up persistently, see the cloud controller code for details.

[edit] Running Services on Pilot Machines

For cost reasons, powering on the spare machines at each hosting site isn't done except in the case where Noisecloud is the only option available for hosting your project. However, some non-dedicated capacity is available for noncommercial projects.

Each colocation site has one low power pilot machine which stays on 24x7 to provide local control over the other machines. Although access to the pilot machine itself is restricted, most sites can run containers or virtual machines on their pilot machines. To have a container or virtual machine started for you, send an SSH public key to Dr. Jesus and a brief description of what your needs are. Only noncommercial uses of Noisecloud are permitted.

[edit] Inventory

The current motherboard inventory is:

[edit] RWC

    10 HDAMA-I    
     2 S2721-533 Thunder i7501 Pro 
     1 S2735    
     4 S2881 Thunder K8SR Mainboard 
     1 S5360    
     2 S5360-1U    
    11 SE7501BR2    
     2 SE7501BR2S    
    13 TYAN Tiger i7501  
     1 Thunder I7520   
     2 Thunder I7520R 

There are also two Cyclades TS-1000 console servers, and one Cyclades TS-3000, one Foundry EdgeIron 9604 and one EdgeIron 4802.

[edit] AMT

    13 Supermicro X7DCL
     3 Dell PowerEdge 750
    10 HP Proliant DL385
     5 HP Proliant DL145

Connectivity is provided by a Foundry 24 port gigabit switch.

[edit] FMT

     9 Foundry EdgeIron II
     6 HP Proliant DL380
     2 HP Proliant DL380 G2
     2 Rackable RaQ 3i
     8 Rackable RaQ 2

[edit] HWD

     2 HP Proliant DL385 G5
     1 Dell Poweredge T110
     1 Dell Poweredge T100

[edit] Oakland

     1 HP Proliant DL585

[edit] Noisebridge

     1 Supermicro X7DCL

[edit] Additional Rackspace

Colocation for other Noisebridge projects is available for a limited number of machines subject to the following conditions:

  • Servers must be used for non-commercial purposes only.
  • Services which do not have a reason to occupy an entire server chassis by themselves are not allowed. Such services can be containerized instead using lxc, UML, or any other technology supported by libvirt.
  • Reliable ops contacts must be available for each server.
  • Bandwidth commitment is 1Mbit 95th percentile per month. Going over this may result in being rate limited and/or suddenly disconnected from the network without warning.
  • Equipment must be tagged with the organization's name, email and telephone number, and a unique ID number (serial number is fine). Tags must have text at least 1/4" (6mm) high, be in English, and must be on the front AND back of the machine. Tags must also be visible within the two 45 degree cones with their points at the center of the front and back plates of the machine.
  • For remote hands warranty support, I need the warranty data or the donor contact information.
  • If you want remote power switching, you can either provide your own 1U power switch or pay $10 / month into the ISP fund supporting this facility. Otherwise, remote reset is on a best effort basis.
  • Please provide a procedure and installation media for remote installation if you want fast turnaround on a reinstallation.
  • Any serial ports to be connected to the serial concentrator must have a Cisco style RJ-45 pinout.
  • Either 110V or 220V power can be provided, but power supplies must have an IEC C14 connector or an adapter so it can accept a C13 power cable.
  • If you need remote hands / crash cart support, please ensure the machine has either 1) VGA and USB keyboard ports, 2) VGA and PS/2 keyboard ports, or 3) serial console. For ADA reasons (one of the administrators is essentially blind), consoles must be configured to be text only.
Personal tools