ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Hey,

Landers and the landing team will notice some changes in the way to 
assign and reconfigure a silo.

For landers:
- reconfiguring a silo never has been so easy: just modify the 
spreadsheet, and run the "configure" job in the silo as before. The 
difference is that no parameter will be needed anymore (mps or sources) 
and those informations will be directly fetched from the spreadsheet.

For landing team:
- when you assign a silo, from now on, a request ID is generated. You 
copy/paste this request to the prepare-silo job (instead of the list of 
mps and sources).
If the job succeed, the request and attributed silo names will be synced 
back in a couple of minutes for the request to be synced back in the 
spreadsheet and all information will appear.
- when you need to reconfigure a silo instead of the landers because 
there are new sources/mps components, the same procedure is available. 
You will have the same request ID given back, just use it with 
"reconfigure silo" option (this is now a checkbox).
- overrides are still available as they used to be and the way to assign 
pre-production silo is done now through a new option (as reconfigure 
silo is not a string anymore).


Hope you will appreciate that change. Consequently, the spreadsheet is 
doing way less write requests and thanks to that, more information are 
now available on the backend. Some races have been fixed in case a silo 
was unassigned/reassigned in the same minute. Finally, in case of any 
breakage, the spreadsheet will be able to recover and resync the status 
back automatically.

This is now in production.

Cheers,
Didier