Agile Cloud Institute

Cross-Functional Architecture And Tools For Cloud-Based Operating Models

Operations with the Agile Cloud Manager

Project management and incident management can merge into one effort and can become better aligned with your enterprise IT strategy using the Agile Cloud Manager.

Project Management

The Agile Cloud Manager enables you to put all your infrastructure, system, and appliance templates for your entire platform under Agile project management.

This has the effect of making it easier to automate increasingly larger portions of the workflows and control loops by which your systems are managed.

As a result, Operations teams can increasingly focus on Agile project management of code definitions.

Increasingly Ephemeral And Resilient Systems

The instances of each component of your platforms can increasingly become ephemeral because it can become very easy to battle-test code, and to simply re-instantiate any aspect of your platform with an upgraded version.

Systems can also become more resilient because software-definitions make it a lot easier to implement High Availability HA.

Incident Management And Deployments Of Fixes

From an incident management standpoint, the Agile Cloud Manager can make it easier to isolate the points in your control loops where an unanticipated termination point was reached due to an unforeseen case emerging.

And it can become easier to simply redeploy a cloned version of whatever part of your platform broke.

If your organization ever finds itself in an extreme situation, entire cloned environments can be spun up and hot-swapped in place of a compromised environment.

Examples of a deeply compromised environment that could benefit from quick replacement by a clone might include the cases of:

Root Cause Analysis RCA Leading To Non-Terminating Control Loops

With the Agile Cloud Manager, the resolution of a Root Cause Analysis RCA would be some new code added into a software-definition that would handle the case that previously triggered the incident(s) so that the same manual step is no longer required in the control loop.

In other words, the termination point in the control loop would be removed, and you would be one step closer to having non-terminating control loops automatically managing your systems.

Pipeline Designs For Incident Management

Your Pipeline definitions need to take your incident management processes into consideration so that your operations engineers and your infrastructure engineers have automated tools that they can use to quickly diagnose and resolve incidents.

For example, the acm serviceInstance on and acm serviceInstance off CLI commands make it possible for you to surgically replace only one instance of one type of service if you are able to isolate the Root Cause of an incident to within only one instance of one type of service.

back to Site Home

back to Architecture section Home