ReleaseEngineering/How To/Manage AWS slaves: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 106: Line 106:
*** look at how the 'disable' command works in aws_manage_instances.py for an idea on how to do this
*** look at how the 'disable' command works in aws_manage_instances.py for an idea on how to do this


== Dealing with 'unknown types', 'unknown state' instances ==
== Unknown Types Or State Instances ==
* Most of these are created by us. Track down who made the instance and request either:
* Most of these are created by us. Track down who made the instance and request either:
** the instance be tagged properly via the [https://mozilla-releng.signin.aws.amazon.com/console AWS web console] and filling in the section called "tags"
** the instance be tagged properly via the [https://mozilla-releng.signin.aws.amazon.com/console AWS web console] and filling in the section called "tags"
** fix the reporting
** fix the reporting


== Dealing with 'stopped for a while' instances ==
== Stopped For A While Instances ==
* If loaners/releng-dev machines:
* If loaners/releng-dev machines:
** when it has been more than a ~2 weeks (say >300 hrs) poke the owner, querying if it is OK to terminate this instance.
** when it has been more than a ~2 weeks (say >300 hrs) poke the owner, querying if it is OK to terminate this instance.
* If it's one of our Buildbot CI machines:
* If it's one of our Buildbot CI machines:
** when it has been more than ~1 month (say >700 hrs) we should terminate the instance
** when it has been more than ~1 month (say >700 hrs) we should terminate the instance
Confirmed users
502

edits

Navigation menu