914805 - Integrate slaveapi into slave heath

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Chris Cooper [:coop] (he/him)]

Wouldn't it be great to be able to reboot slaves directly from slave health? Yeah, it would.

Comment 1

[[e-mail] (:bhearsum)]

Indeed! Slave Health should be able to post to http://slaveapi-dev1.srv.releng.scl3.mozilla.com:8080/slaves/<SLAVE>/actions/reboot to do this already. Once bug 929584 is fixed we can point it at production.

Comment 2

[Chris Cooper [:coop] (he/him)]

Going to start poking at this today.

bhearsum: any reason not to use https://secure.pub.build.mozilla.org/slaveapi/ instead of the dev instance now?

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Chris Cooper [:coop] from comment #2)
> Going to start poking at this today.
> 
> bhearsum: any reason not to use
> https://secure.pub.build.mozilla.org/slaveapi/ instead of the dev instance
> now?

Nope! The production instance is the correct one to use.

Comment 4

[Chris Cooper [:coop] (he/him)]

Removing blockers.

New code reads history for slaveapi rather than kittenherder files. We'll lose that data every time we restart slaveapi until bug 913601 is fixed, but the kittenherder data hadn't been updated in months anyway.

Enough of bug 952264 is deployed already to make the history and timing parts of the code work now.

Comment 5

[Chris Cooper [:coop] (he/him)]

https://hg.mozilla.org/users/coop_mozilla.com/slave_health/rev/38e90b51cd41

I'm sure people will have issues with the notifications and timing, but we can fix those issues in follow-up bugs.