Refer to the following community article which describes our Cloud Provisioning and Governance approach:
Here is a video scenario showing a cloud end user requesting a cloud service and a cloud operator responding to it:
What we intend to show in this video:
- On a cloud end user perspective:
Provide a self-service portal for end user to easily and quickly request some cloud services into the different cloud providers and improve the user experience by providing visibility on each provisioning and post provisioning step
- On a cloud operator perspective:
Provide an intuitive dashboard and scrum board to easily identify and assess the cloud manual tasks that need to be completed in order for the initial request to be provisioned
Sequence of the demo:
- Connection to the service portal
- Home page showing information on user quota and current spent
- Seeing the list of stacks by status (rejected, failed, in progress, provisioned)
- Drill down in the current spend dashboard to see what the corresponding stacks are
- Connecting to service catalog: Trying to provision a new stack while we don't have enough budget
- The Selected cloud item is delivered by terraform intoVsphere
- The form has been configured to simplify the user experience:
a. no metrics field (CPU, RAM…)
b. Section on type of VM with a dependence on the final item price
c. Dependence between the application and template fields to restrict the user choice
- Submitting the request
- User can see that the request failed and has the details of the failure in the comments: request rejected because of budget
- Two options are available from here:
a. Find the good request item in the catalog to ask for a budget increase
b. Deprovision an existing active stack to release some budget (this is the chosen option in this case)
- Going back into the home page
- Executing a deprovision day2 operation on a particular stack
- The current spend has now decreased and the deprovisioned stack has been terminated
- Request back the new stack
- User can follow the end to end process from the service portal
- We can now connect as a cloud operator into the back-office home page
- The homepage displays a dashboard showing:
a. Some metrics on cloud tasks
b. The list of all current open tasks
c. The list of tasks per stack
- The operator can choose to work efficiently on a visual task board
- During the progress of the provisioning, the end user visualizes the automatic completion of some steps while the cloud operator receives some manual tasks from the stack
- The cloud operator can assign a fulfiller to each task and complete them
- Once the tasks are completed a final one appears to close the request
- The stack is now provisioned, and the end user can observe all different actions managed by the cloud operators
- To finish a dashboard is available for the end user to see:
a. The statistics and status of its stacks
b. The distribution of type of tasks per request (manual vs automatic)
c. The average time for provisioning and post provisioning tasks
