Closed Bug 1462487 Opened 7 years ago Closed 6 years ago

[roller] store machine state data

Categories

(Infrastructure & Operations Graveyard :: RelOps: Roller, task)

Product:
Infrastructure & Operations Graveyard
Component:
RelOps: Roller
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: dhouse, Unassigned)

References

Details

User Story

We need to store metadata about machines:

MAC (to key with infoblox?)
IP (can be used as keyname for what image tftp serves)
hostname (useful as a key to correlate other data and services)
boot:
    next-server (tftp server)
    filename (OS image)
what images are available?

What needs to know?
something controlling pxeboot/tftp contents or dhcp data
    Our imaging server could use this data to decide what image to provide to an IP?
    Our controller, roller, could use this data to decide what image to use?
    Can the next_boot or image be specified from ilo/ssh/ipmi netboot?
    The pxeboot bootstrap environment could use this data to decide what image to load?
relops engineers

Where does the data come from?
Infoblox: MAC, IP, hostname
?? tftp server
?? pxeboot filename
    relops engineer
    automation/packer building a new image

Where is this data now?
Infoblox, kickstart configs, deploystudio

Where do we store this data?
InfoBlox
In something on the Roller machines
In a public repository (github)
In Pulse
In TaskCluster somewhere
For a future infra with multiple images and switching what image a system is running, we need to track that metadata somewhere. We currently store information about hardware machines in json in the roller module in releng puppet. This was a work-around while the data was moving to infoblox, and until we switched to pulling this data from infoblox's api. The previous system, slaveapi, pulled this information from inventory. Images have previously been manually configured either through performing the boot/kickstart in-person for linux, or hardcoded in dhcp settings for windows, or configured in deploystudio for macos.
User Story: (updated)
Jake, I started writing some notes here: https://docs.google.com/document/d/11LBLKoShVr_x6_8TKuFEv86GQlvxiVAQOd-QnOgtTtM/edit#heading=h.q8no8pnuwzca (I copied the high-level notes to the user-story field)
Assignee: relops → nobody
Component: RelOps: General → RelOps: Roller
QA Contact: klibby

Closing this for now as it is not part of a project/plan. We may need to still do this for a future imaging solution.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.