| Info |
|---|
Cloudaware offers a low-friction, high-value continuous patching. Cloudaware’s approach is to ensure a customer’s compute instances are patched in a timely manner without causing harm and interference to production applications. |
| Table of Contents |
|---|
Clouduaware Cloudaware patch management process supports capabilities such as automatically generated release notes, full and partial rollback, and deployment of emergency patches for critical security vulnerabilities.
Transparency
Cloudaware provides a detailed report indicating available upgradable packages, the machines that will be updated, and the scheduled patch installation date.
Consistency
Cloudaware generates a patching snapshot defining the patches and their versions to which they will be updated. Cloudaware guarantees that this snapshot to be implemented across all environments such as Dev, QA, Staging and Prod. If any patch is detected as manually upgraded or auto-installed, Cloudaware will skip it.
The Cloudaware patch process also supports patch groups, meaning that only members of one patch group will be rebooted at a time if necessary.
Rollback Mechanism
Rollback script is located on every patched instance in the following location: /opt/breeze-agent/os_updater/YYYYMMDDhhmmss.sh
In the event If rollback is requested, Cloudaware Breeze agent will set repo to the previous GUID, execute the rollback script and verify rollback using yum update against preview repo GUID. After the script execution is complete, the yum update should not introduce any changes to the packages on the host.
...
Cloudaware provides patch monitoring and patch eligibility information in CMDB. Along with OS level data, the information on patches becomes available in Cloudaware CMDB once Breeze agent is installed on a machine.
...