The wasmCloud Application Deployment Manager (wadm) was created in response to this RFC. When deployed into a lattice, it is capable of managing a set of application deployment specifications, monitoring the current state of an entire lattice, and issuing the appropriate lattice control commands required to close the gap between observed and desired state.
wadm has a very small set of responsibilities, which actually contributes to its power.
- Manage Application Specifications - Manage models consisting of desired state. This includes the creation and deletion and rollback of models to previous versions. Application specifications are defined using the Open Application Model. For more information on wadm's specific OAM features, see our OAM README.
- Observe State - Observe the current, real-time state of a lattice (done via the lattice-observer library).
- Take Compensating Actions - When indicated, issue commands to the lattice control interface to bring about the changes necessary to make the desired and observed state match.
Interacting with wadm is done over NATS on the root topic wadm.{prefix} where prefix is the lattice namespace prefix. For more information on this API, please consult the wadm Reference.
- Autonomous Agents
- Autonomous Agent (Wikipedia)
- Control Loop
- Mascot logo at the top of this page is "Deeeeploy Jeeennnkinnns", an avatar used in a game demo for early versions of wasmCloud.