Closed Bug 778221 Opened 10 years ago Closed 9 years ago

Agree on requirements for future panda chassis

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hwine, Unassigned)

References

Details

(Whiteboard: [reit-panda])

We know we want to improve the rev 1 chassis, at the very least as regards panda board density.

This chassis must meet the needs of IT, RelEng, and Ateam. This bug is to document those needs and sign off on the rev 2 chassis design.

I believe a reasonable target for the rev 2 chassis is to say it can support both mobile & b2g work at scale.
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
The hardware specs we've seen (we're really only involved in the power relay stuff) look good to us so far. As far as if anything is missing, I have two notes:

I can't think of anything here that we're missing. The one thing that I know we did talk about is not having the lid screwed down, but I think that is covered in your "easily removable" point. Perhaps you should specify "removable without a screw driver" to be more specific, I'll let Jake make that call.

Also the "remote imaging" piece is all software right now, and isn't really dependent on hardware or the chassis. There is a computer that is going to run a tftp server but that will not be inside the chassis.  It will merely be on an adjacent rack in the same datacenter.

Otherwise, this looks good to me.
(In reply to Clint Talbert ( :ctalbert ) from comment #2)
> I can't think of anything here that we're missing. The one thing that I know
> we did talk about is not having the lid screwed down, but I think that is
> covered in your "easily removable" point. Perhaps you should specify
> "removable without a screw driver" to be more specific, I'll let Jake make
> that call.

I'm hesitant to go as far as "removable without a screw driver" since it will most likely become time and cost prohibitive to meet that spec.  At this point the current chassis (rev1) uses screws to secure the top cover and is not much more than a slight inconvenience to open.  I opened Panda Chassis "2" yesterday and with the power screwdriver it only took a couple mins or so.  I will look into a more convenient design but if its going to block at all, I think we should stick with the current top cover design.  We could also simply use less screws.  I will talk offline with :dmoore since this affects his group primarily.
(In reply to Jake Watkins [:dividehex] from comment #3)
> I will look into a more convenient design but if its going to
> block at all, I think we should stick with the current top cover design.  We
> could also simply use less screws.  I will talk offline with :dmoore since
> this affects his group primarily.


"Less screws" is fine... if you're comfortable just using 1-3 screws on the lid in production (vs. a dozen), then we can work with that.
We're already on rev2 of the panda chassis.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.