Closed Bug 777393 Opened 8 years ago Closed 7 years ago

design a higher capacity panda chassis

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86_64
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dividehex, Assigned: dividehex)

References

Details

(Whiteboard: [2013Q2] u=panda c=it p=3)

We currently have a panda chassis design that will accommodate up to 12 pandas in a 4U rack space.  Since rack space is limited in our datacenters, we are going to work on a higher density design.
Assignee: server-ops-releng → jwatkins
Whiteboard: u=panda c=it p=3
We are still working out software details but these hardware requirements will help Jake get started on a design.

Hardware requirements for Android Panda Chassis:

- Proper airflow, cold aisle compatible
- Self-contained power supply that matches datacenter voltage requirements (208v)
- Stable mechanical mounting
- Ability to replace individual pieces of faulty internal hardware (FRUs)
- Modular internal design: power, networking, cooling
  - chassis on rails for easy access
  - chassis lid should be easily removable for maintenace
  - easily removable mounting brackets for pandaboards
  - RelEng does not have a requirement for hot swap
- Physical hardware management
  - Maximizing top-of-rack switch usage
  - Maximizing rack space usage/power density while still allowing for proper cable management
- Remote power management
- Remote imaging for a larger percentage of failure modes
- Adequate internal density for future growth within confined datacenter space
Those look good to me.
Whiteboard: u=panda c=it p=3 → [2013Q1] u=panda c=it p=3
Whiteboard: [2013Q1] u=panda c=it p=3 → [2013Q2] u=panda c=it p=3
Depends on: 882449
Design is completed

https://mana.mozilla.org/wiki/display/IT/HD+Panda+Chassis+System
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.