February 3, 2015 | Written by: IBM Cloud Staff
Share this post:
By Thomas Andersen and Saumil Patel
The year is 2020. We are sitting here waiting for our cloud deployment request to complete. We go to the Cloud Control Center dashboard to see exactly where our request is.
There’s a green indicator for each step of the deployment process that has successfully completed. We can click on the indicator to get full details on actions taken for a particular step. As long as the deployment is not complete, we can roll back to any previous step in the process or pause the executing step and make any desired modifications for our active deployment. After we make the changes and resume deployment, the Cloud Intelligence Automation (CIA) will validate our selection, determine if there are any steps that need to be rolled back, implement desired modifications and continue with the deployment. Naturally it will skip completed steps that aren’t affected by our change.
Suddenly a yellow light catches our attention. When we click the yellow indicator, we can see that the CIA is suggesting the total disk space for our database instance should be 10 petabytes, based on previously deployed environments with similar usage. Normally the system would handle this situation by automatically adjusting the deployment parameters. But in this case, the system saw that we are online and notified us directly of the situation. If we do nothing in the next 30 seconds, the system will use its own recommended values. This time we decide to lean back and enjoy a cold beverage.
It is rumored that if a red indicator appears, a critical error has occurred and the CIA immediately starts searching its intergalactic knowledge base. If a solution is found and the system detects us online, we should be presented with the solution and have 30 seconds to reject it before it is automatically applied. If we are not online, the system should apply the solution automatically as with the yellow light situation. If a solution is not found in the intergalactic knowledge base, we should be contacted by support within 30 minutes to help resolve the issue and secure a permanent solution within 48 hours.
This is how we envision the future of cloud management. How about you? Leave a comment below or reach out to us on Twitter @PatSaum and @CloudyTHA to let us know your thoughts.