Confirmed users
3,990
edits
ReleaseEngineering/Projects/PandaBoards: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Projects/PandaBoards (view source)
Revision as of 02:21, 9 February 2012
, 9 February 2012→What does IT need/know?
No edit summary |
|||
| Line 19: | Line 19: | ||
== 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 | * know: we don't have room for a production quantity of these in haxxor, only in real data-centers which necessitates a rackmount enclosure with proper remote management. | ||
** '''Q''': does this rackmount exist? would it allow to replace SD cards on panda boards? | |||
* need: blocked on the exact specs on the board(s) we're ordering/supporting | * need: blocked on the exact specs on the board(s) we're ordering/supporting | ||
** '''A''': ctalbert is going to let us know what he has. At the time there was only one model. | |||
* need: blocked on at least two physical boards/power supplies for enclosure prototyping | * need: blocked on at least two physical boards/power supplies for enclosure prototyping | ||
** '''A''': once ctalbert answers we can determine what to buy | |||
** 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? | ** 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? | ** how is imaging handled, will be able to do it remotely like we have planned with the tegras? | ||
** '''Q''': how different is tegra '''current''' management compared to SD card replacement for pandas? | |||
* 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 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). | ||
** '''A''': armenzg can help with estimates once we have timing on how fast unit/talos tests run on pandas VS tegras | |||
** '''A''': probably 15 of them to do staging will help to test that imaging has worked and that we can run them on the staging setup. | |||
** '''A''': blassey mentioned that having something running in March/April to get results going would be very useful to catch regressions | |||
* 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. | * 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. | ||
** '''A''': armenzg can help get a ballpark # once we have a machine running tests so we can time it. | |||
** how much space does this require in the dc | ** how much space does this require in the dc | ||
** how many buildbot masters does this require, and of what configuration | ** 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)? | ** 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 | *** '''A''': bear is going to get us Linux foopy VMs. | ||
** will these also connect to the tegra dashboard or something similar? Does that scale? what are the spec requirements for a machine/vm to make this work if this is the plan? | |||
*** '''TBD''' | |||
* 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? | * 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? | ||
** '''A''': I (armenzg) think that putting a subset on the side to verify it is good and then we can do rolling downtime. | |||
== What does releng need/know? == | == What does releng need/know? == | ||