Closed Bug 625533 Opened 15 years ago Closed 15 years ago

inventory needs for releng

Categories

(mozilla.org Graveyard :: Server Operations: Projects, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: rtucker)

Details

We have a bunch of data about slaves that's looking for a permanent home. In building the slave allocator (bug 618369), I've come up with the following list of attributes of a slave (see : - distro - bitlength - purpose (build or test) - datacenter - trustlevel (core or user/try - corresponds to hg permission levels) - environment (staging, preprod, production) From a brief conversation in the inventory meeting, I think it would make sense to split this data up - some of these attributes are intrinsic to the host or otherwise managed by IT (distro, bitlength, datacenter, purpose), while others are things that releng would change frequently (trustlevel and environment). It would be great if the New Improved Inventory could have: - a 'role' field which could be set to 'slave' for buildslaves, so my tools can filter out everything else - distro, bitlength, and purpose fields using the short names we're using elsewhere (e.g., darwin10, centos5, etc.) - a lightweight programmatic query API that can filter by role (among other fields, probably)
Adding cshields and rtucker (our new tools guy)
Moving & Reassigning.. I won't promise any improvements for about a month or so, we need to give Rob time to learn the infrastructure and set his priorities. That said, zandr, while he is in town next week can you set up a meeting with him to show some of these issues? His wed and thu afternoons should be open.
Assignee: dustin → nobody
Component: Server Operations: RelEng → Server Operations: Projects
QA Contact: zandr → mrz
Assignee: nobody → rtucker
I'm OOO tomorrow (Weds) but will be back in MV on Thurs. What time works for rtucker and :dustin to chat?
I've got no plans, aside from being buildduty, so schedule whenever is convenient for you both. I may need to cancel if the sky is falling..
I'll be available to discuss this later this afternoon.
If the tree is open by then, I will too.
My propsed solution is as follows: Create a section of the host details page for things specific to releng. This area will only be visible if the host is allocated to them. I will work with Dustin regarding the api. At this point we're pretty set on a json api. We'll come up with an authentication api to protect it. Once aravind works out the rest of the ldap build for REHL6 I should be good to go on my dev environment and I can start making these changes.
Zandr: I added the new components as we discussed to the inventory system. I'm proposing to create a separate bug for the API. I think that it's going to be a large enough project to warrant its own bug(s) I would like for you to test it before I push it to production, but it's on my own sandbox server to which I'll have to create you a new password. Let me know when you are available and we can do some QA.
I went ahead and pushed this to production this morning, there's some other things that I needed to get put up with this push. I'm going to close this bug out and create a new one for the api.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.