Armen [:armenzg] Reporter
	Description • 10 years ago

This would remove the need to have to manually access a machine to deploy the keys.
This would speed up the time it takes to put a machine back into production.

The data is stored in the slavealloc DB, however, if a person in releng requests a re-image without updating the field properly it will fail.

There is another way that is less prone to human error which would be to load the values of WIN64_REV2 and TRY_WIN64_REV2 from http://hg.mozilla.org/build/buildbot-configs/file/production/mozilla/production_config.py

Another way would be once the machines are on SCL3 where they would either be inside of the try vlan OR not.

We should be watchful that moving a machine that is moved to the loaner OU will always remove the keys. I believe we have that in place but it would be great to verify it again.

	Amy Rich [:arr] [:arich]
	Comment 1 • 10 years ago

Since the windows machines should migrate to scl3 within the next couple months, this is best done by VLAN there.

	Chris Cooper [:coop] (he/him)
	Comment 2 • 10 years ago

All the Windows machines are in scl3 now, so we're good to proceed here, please.

	Q Assignee
	Comment 3 • 10 years ago

Keys are no

	Chris Cooper [:coop] (he/him)
	Comment 4 • 10 years ago

Q: we're done here?

	Q Assignee
	Comment 5 • 10 years ago

Yes we are done. The only caveat to this whole procedure is that we currently do not have an automated method of determining staging machines but those seem to be a small minority of build machines and can be managed by hand for now.