It’s no secret that Cloud Application Manager performs deployments on your remote virtual machines using an agent. But what goes on behind the scenes? What makes the agent tick? Join me for a deep dive.
Though not visibly apparent, when you trigger deployments from the web or API, the agent is the software we install on every virtual machine you deploy from Cloud Application Manager. Its sole purpose is to handle box deployments on the VM or service. It executes event scripts and runs lifecycle operations from the web or API calls. By itself the agent does not contain any other logic. It executes whatever Cloud Application Manager tells it to do and sends back the logs of the output.
We built the agent based on three important principles of software architecture:
- To be platform interoperable, that is, work on any OS or platform.
- To be network interoperable, that is, communicate over any network configuration easily.
- To cover a small footprint, that is, consume the least amount of machine resources.
Platform interoperability is pretty important. The agent works across all platforms on any OS and runtime libraries. It works cross-platform because it’s written in Python, and doesn’t require any dependencies.
In recent times, we made...