ReleaseEngineering/Mozpool: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "Mobile development boards are imaged and re-imaged by loading a live Linux distro via PXE boot, then downloading the required images and writing them to the board's storage. BMM...")
 
No edit summary
Line 49: Line 49:


Because development boards are not even vaguely reliable, the reimaging process has lots of timeouts and performs lots of retries.  This is implemented as a state machine, with the state stored in the database.  This state machine implements all of the timeouts and retires, and does so in such a way that it will pick up where it left off after a failure or restart of the imaging server itself.
Because development boards are not even vaguely reliable, the reimaging process has lots of timeouts and performs lots of retries.  This is implemented as a state machine, with the state stored in the database.  This state machine implements all of the timeouts and retires, and does so in such a way that it will pick up where it left off after a failure or restart of the imaging server itself.
See [[ReleaseEngineering/BlackMobileMagic/State Machine]]
canmove, Confirmed users
1,394

edits

Navigation menu