Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Zero Downtime Updates in Server Automation

Zero Downtime Updates in Server Automation

Currently the release Updates in Server Automation need huge downtimes of productive Environment.

In modern Automation scenarios / environments with customer Self Service this is not state of the art.

Expectation is to have a solution where a clustered Server Automation Core could be updated without Service Restriction of the Mesh.

4 Comments
Thomas_Blum Contributor.
Contributor.

I'm have been asking with my colleagues different people in opsware, hp, hpe and microfocus scince nearly 10 years and its becomming more and more  important. We are not able to rollout new releases to a multimaster mesh because of the huge downtimes.Every release update has been a big challange even with pso guy's onside support.

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
Micro Focus Expert
Micro Focus Expert

There is a known zero-downtime upgrade procedure with HP/HPE/Micro Focus Professional Services IP; but it's a complex and long procedure, requires quite a lot of infrastructure (like all servers behind Satellites), some times is carried in parallel with OS upgrades and/or HW changes.

I agree should be an easier and faster way to achieve the platform upgrade

Michael_it Honored Contributor.
Honored Contributor.

transfer of details from another idea:

https://community.softwaregrp.com/t5/Data-Center-Automation-Idea/Always-on-solution-for-Server-Automation/idi-p/1684228

 

Brief Description
Always on solution for Server Automation
Benefits / Value
A large shared autoamtion environment has the requirement to be always on. This applies for normal operations time as well for planned upgrades.
where SA in normal operations has a good shared nothing architecture allowing each Core to operate. currently there is large downtime when you want to perform an inplace upgrade to a newer software version.
This is currently a major blocker to use SA for continously available large automation projects.
as soon as a company achieved a level of autoamtion in all areas (Incident, Change, Request Fullfillment) it is impossible to bridge a larger time frame where automation platform is not available.
already due to the fact that there are no people in operations any more that can do this manually
So that means implicitly that automation platform must be continously available

Design details
Currently you can not upgrade Cores without impacting running Jobs. Firstly SA needs a mechanism to Dry out a core not taking new Jobs and allowing old jobs to be rerouted to another Core or having a clear indication that there is still an active job using a route to this Core (rerouting satellites would break jobs)
so probably a gracefull routing switch in satellites is needed
a more Product inbuild funtion to take a core into maintenance would be needed (currently you could only do this manually by loadbalancers taking core out of balancing)
Software upgrades must consistently allow different versions in a mesh to exist

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.