This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We have the ability to create blackouts within UCD as part of the API offering. When setting a blackout period maintenance mode is automatically enabled, however when the blackout ends the maintenance mode is left on. I agree with this approach in case there are events in the schedule that causes a delay to the closure of the planned change.
To best execute automation functionality we are creating it would be good if we could have an ad hoc way of managing the maintenance mode via an API call for both enabling and disabling.
This will allow us to apply maintenance mode at short notice for unplanned outages where for example we need to stop a single node or take corrective action in the DB, it will also allow our comms to be automated at the end of planned and unplanned outages.
Although this is a nice to have we do not have a dedicated timeline for implementation.
We are looking at increasing automation of our comms, upgrade, patching and break fix processes, we are trying to reduce the number of manual hand offs/actions as part of our application management.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Discussed with team on 11/8/2023 and will do some testing.
actually the following is possible:
Enable maintenance mode through a cli endpoint.
curl 'https://yourucdserver:yourport/cli/systemConfiguration' -XPUT --data-binary '{ "maintenanceModeEnabled": true }' -H "Content-Type: application/json"
or using udclient command "setSystemConfiguration file.json" where file.json contains the same json body as above.
disable
curl 'https://yourucdserver:yourport/cli/systemConfiguration' -XPUT --data-binary '{ "maintenanceModeEnabled": false }' -H "Content-Type: application/json"
or using udclient command
Thank You for providing a new idea. Together with the development lead we are analyzing it.