A representative of STORAGE and COMPUTE that maintains summaries of the involved objects.
Controller provides the ability to create and manipulate storage and compute instances.
Each of Storage and Compute provide their own controllers, accessed through the
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.
ComputeController documentation for more information
about each of these interfaces.
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.
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!
Whether one of the underlying controllers is ready for their
method to be called.