Expand description

A representative of STORAGE and COMPUTE that maintains summaries of the involved objects.

The Controller provides the ability to create and manipulate storage and compute instances. Each of Storage and Compute provide their own controllers, accessed through the storage() and compute(instance_id) methods. It is an error to access a compute instance before it has been created; a single storage instance is always available.

The controller also provides a recv() method that returns responses from the storage and compute layers, which may remain of value to the interested user. With time, these responses may be thinned down in an effort to make the controller more self contained.

Consult the StorageController and ComputeController documentation for more information about each of these interfaces.

Structs

An event describing a change in status of a compute process.

Resource allocations for a replica of a compute instance.

A client that maintains soft state and validates commands, in addition to forwarding them.

Configures a controller.

Enums

Describes the status of an orchestrated service.

Size or location of a replica

Logging configuration of a replica. Changing this type requires a catalog storage migration!

Responses that Controller can produce.

Readiness 🔒

Whether one of the underlying controllers is ready for their process method to be called.

Functions

Deterministically generates replica names based on inputs.

Parse a name generated by generate_replica_service_name, to extract the replica’s compute instance ID and replica ID values.