ReleaseEngineering/Projects/PandaBoards: Difference between revisions

Jump to navigation Jump to search
Line 16: Line 16:


== What does IT need/know? ==
== What does IT need/know? ==
* know: we don't have room for a production quantity of these in haxxor, only in real datacenters which necessitates a rakcmount enclosure with proper remote management.
* need: blocked on the exact specs on the board(s) we're ordering/supporting
* need: blocked on at least two physical boards/power supplies for enclosure prototyping
** must determine: how many panda boards can we fit in a custom 4U chassis, and how do we connect them to relay boards for remote administration?
** how is imaging handled, will be able to do it remotely like we have planned with the tegras?
* need: a defined timeline/gantt chart that shows when we'll need each phase done by and what it's requirements are (e.g. one board to play with in haxxor, N boards to play with in a datacenter (where N needs to be defined)), and a full blown production setup).
* need: a good ballpark estimation of how many boards we will be putting into production and whether that is phased over several months or needs to be done all at once.
** how much space does this require in the dc
** how many buildbot masters does this require, and of what configuration
** how many foopies does this require, and of what type/configuration (minis are harder, linux is better, none is best)?
** will these also connect to the tegra dashboard or something similar?  Does that scale?  what are the spec requiremetns for a machine/vm to make this work if this is the plan?
* need: do 9 month cycle OS builds mean SD card swapouts/reimages every 9 months?  What's that process look like?  tree closure, rolling upgrades?


== What does releng need/know? ==
== What does releng need/know? ==
Confirmed users
72

edits

Navigation menu