tree: 0122512f3ff4ec8a896f5eee4310765ef1ba9bf7 [path history] [tgz]
  1. go/
  2. images/
  3. modules/
  4. pages/
  5. secrets/
  6. .eslintrc.js
  7. .gitignore
  8. BUILD.bazel
  9. Makefile
  10. README.md
  11. test_machine_monitor_cipd.yml
machine/README.md

Machine Server

The machine state server is a centralized management application for device testing.

See the Design Doc.

Code structure

The main code is structure as:

go/machine/
    source/
    processor/
    store/

Where:

  • types contains the Go types used across the rest of the modules.
  • The source module contains source.Source, a way to get update events from machines.
  • The store module contains store.Store, a way to persist and retrieve each machine's state.
  • The processor module contains processor.Processor, a way to update a machine state from an incoming event.

The main loop of machine state server looks like:

for event := range eventCh {
	store.Update(ctx, event.Host.Name, func(previous machine.Description) machine.Description {
		return processor.Process(ctx, previous, event)
	})
}

test_machine_monitor

The application that runs on each switchboard test machine and feeds information into the machine state server.

See the Design Doc.

Current Data Flow

User triggers powercycle for a machine.

initiatormessagetargetnotes
machineserver>Set(ΔDescription)DBDescription.Powercycle=true
powercycle_server_ansible<WebAPI(ListPowerCycleResponse)machineserverGET on /json/v1/powercycle/list
powercycle_server_ansible>WebAPImachineserverPOST to /json/v1/powercycle/complete/{id:.+}

powercycle_server_ansible report availability on startup.

initiatormessagetargetnotes
powercycle_server_ansible>WebAPI(UpdatePowerCycleStateRequest)machineserverPOST to /json/v1/powercycle/state/update

How test_machine_monitor keeps machine.Description up to date.

initiatormessagetargetnotes
test_machine_monitor>PubSub(Event)machineserverSends results from interrogate.
test_machine_monitor<WebAPI(Description)machineserverGET to /json/v1/machine/description/{id:.+}

Legend

  • initiator - The entity that starts the action.
  • message - Shows the direction of the data flow, the transport, and the struct being moved.
    • Set - A database operation
    • WebAPI - An HTTP Request
    • PubSub - A PubSub message.
  • target - Who the iniator is talking to.
  • Δ is used before a struct if only a part of that struct is being changed.