Provide Maintenance Mode feature for Plattformupgrades That gracefully dry out the environment
Benefits / Value
currently you do a hard Stop to CSA or OO which means there could be lifecycle processes pending OO Flows running. this can cause several unexpected failures when shuting down the services in this mode
Benefit of implementing is controlled shutdown of a very utilizied environment to allow running jobs to finish but stop getting new ones.
currently all upgrade guides suggest you should finish all Flows /CSA processes before starting the upgrade. but very utilized environments dont have a period where nothing comes in
Explain how would you like this idea designed / implemented
This is mainly for OO and CSA. setting maintenance mode for the suite would mean you dont sshutdown services imeadiatly. active maintenance in OO means no new flows via UI/API/Scheduler . Running flows will continou until finished.
For CSA it could mean you either directly accept no new request or you accept request but dont start Lifecycles. probably for a start accepting nothing at all would be ok. also here waiting that at least open processes instances finishes. but then do not start next process instance.
please also take into account the cross product dependecies. When OO goes to maintenance CSA cant launch flows anymore. so probably CSA part should go first into Maintenance then OO
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.