Support for Downtimeless Upgrade/Update procedures

Support for Downtimeless Upgrade/Update procedures

0 Votes

Brief Description:
Support for Downtimeless Upgrade/Update procedures
Benefits / Value:
Support that even for Updates it is suggested to stop Both Nodes of a clustered CSA environment.
We want to be able to Upgrade/Update the Portal and Controller clusters without downtime impact the enviroments.
There must be a described update path that allows Controllers in a certain version to Work with MPPs in a different version while upgrading/updating.
Controllers must be possible to upgrade/update one node while the other node is still running and serving customers in older Version.

Design details:
Enterprise enviroment needs to be always up and running

Tags (3)
1 Comment
Not applicable

Hello, we are making rapid strides towards a modern scalable architecture, built on docker and containers in Hybrid Cloud Management suite. HCM is the successor and forward story of CSA, with far more capabilities and a strong roadmap.

If you are interested in knowing more, please reach out to me ramd <at> microfocus <dot> com for more info.

With this plan, we don't plan to make upgrade improvements in the classic (monolithic) CSA product.

Good news is with the conversion of our old applications to micro-services (docker containers running on kubernetes), we already ensure that your upgrade becomes easier and lesser downtime. read this to know more about micro-services - (a useful, short read).


Ram D [for HCM Product Management]

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.