Email scenarios private cloud

Email Scenarios¶

Private Cloud¶

Scenario 1. Product Create Request¶

Description: A new or existing user submits a request via the registry to have a namespace for their product. This is assuming the user has already had an onboarding meeting, and meets the requirements for submitting a create request. Upon submitting the create request, the following emails may trigger.

Notification sent to admins containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s), Cluster)
2. Actioned by text (who submitted the request)
Notification sent to Product PO/TL(s) containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s), Cluster)
Decision: Create request Approval/Rejection by Admin
3a. Approval sent to PO/TLs containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Namespace Details (Cluster, Link to all four namespaces, Default values of namespaces)
3. Security Tools Info
4. Artifactory Info
5. Vault Info
6. ACS Info
7. Sysdig Info
3b. Rejection sent to PO/TLs containing:
1. Product Details (Name)
2. Admin review comments

flowchart LR
    A((User Submits <br> Create Request)) --> B(PrivateCloudAdminCreateRequest<br>PrivateCloudCreateRequest)
    B --> C{Admin decides on the create request}
    C -->|Create Request Approved and Provisioned| D(PrivateCloudRequestProvisioned)
    C -->|Create Request Rejected| E(PrivateCloudCreateRejected)

Scenario 2. Edit Request: Resource Quota Increase¶

Description: A PO/TLs of a product submits a request for more CPU, memory, and/or storage of 1 or more namepspaces. Upon submitting the edit resource request, the following emails will trigger.

Notification sent to admins containing:
1. Description Changes (Product Name, Description, Ministry)
2. Contact Changes (Product Owner, Primary Technical Lead, Secondary Technical Lead)
3. Comments by user if provided
4. Resource Quotas with Current and Requested
5. Actioned by text (who submitted the request)
Notification sent to PO/TL(s) containing:
1. Description Changes (Product Name, Description, Ministry)
2. Contact Changes (Product Owner, Primary Technical Lead, Secondary Technical Lead)
3. Comments by user if provided
4. Resource Quotas with Current and Requested
Decision: Resource Quota Edit Request Approval/Rejection by admins
3a. Approval sent to PO/TLs containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Namespace Details with Previous and Approved values (Cluster, Link to all four namespaces)
3b. Rejection Sub-Scenario containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Admin review comments
3. Namespace Details with Previous and Rejected values (Cluster, Link to all four namespaces)

flowchart LR
    A((User submits a <br>Edit Resource <br> Quota Request)) --> B(PrivateCloudResourceRequestAdmin<br>PrivateCloudResourceRequest)
    B --> C{Admin decision on Edit Resource Quota request}
    C -->|Request approved| D(PrivateCloudResourceRequestApproval)
    C -->|Request rejected| E(PrivateCloudResourceRequestRejection)
    D -->|Changes provisioned| F(PrivateCloudResourceRequestCompleted)

Scenario 3. Edit Request: No Resource Quota Increase¶

Description: When a PO/TLs of a product edit their product where there is no increase in resources requested, the following emails will trigger.

Summary of the changes provisioned sent to PO/TLs containing:
1. Updated Description Changes (Product Name, Description, Ministry)
2. Updated Contact Changes
3. Updated Resource Quota Downgrades
4. Description Changes (Product Name, Description, Ministry)
5. Contact Changes (Product Owner, Primary Technical Lead, Secondary Technical Lead)
6. Comments by user if provided
7. Resource Quotas with Current and Requested

flowchart LR
    A((User Submits Edit w/ <br> No Resource Increase)) -->|Request Automatically Approved and Provisioned| C(PrivateCloudEditApprovedAndProvisioned)

Scenario 4. Mixed Edit Request: Quota Increase and Contact Change¶

Description: When a PO/TLs of a product edit their product with both Quota Increase and Contact Change.

A notification sent to admins containing:
1. Comments by user if provided
2. Name, Description, Ministry, Cluster, Contacts (all can be with Current and Requested sections if they are changed)
3. Quota Changes with Current and Requested sections
Summary of changes submitted sent to PO/TLs containing:
1. Product Details that were changed, Current and Requested (Name, Description, Ministry, Contacts of PO/TL(s), Quota)
Decision: Mixed Quota Increase and Contact Change Request Approval/Rejection by admins
3a. Approval sent to PO/TLs containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Namespace Details with Previous and Approved values (with link to the namespace that changes were made on)
3b. Rejection Sub-Scenario containing:
1. Product Details that were changed with Current and Rejected Quota
2. Admin review comments

flowchart LR
    A((User submits a<br> Mixed Edit Request <br>Quota and Contacts)) --> B(PrivateCloudResourceRequestAdmin<br>PrivateCloudResourceRequest)
    B --> C{Admin decision on Mixed Edit Request}
    C -->|Request approved| D(PrivateCloudResourceRequestApproval)
    C -->|Request rejected| E(PrivateCloudResourceRequestRejection)
    D -->|Changes provisioned| F(PrivateCloudResourceRequestCompleted)

Scenario 5. Delete request is submitted¶

Description: When a PO/TLs of a product have removed all PVC's and resources deployed on their namespaces of a given product, then a user is eligible to submit a delete request. Upon a successful deletion check the user can submit the delete request and thus the following emails may trigger.

A notification sent to admins containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Actioned by text (who submitted the request)
A summary sent to PO/TLs containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Namespace Details (Cluster and Link to the 4 namespaces)
Decision: Product Deletion Approval/Rejecton by admins
3a. Approval confirmation sent to PO/TLs containing:
1. Product Details (Name, Description, Ministry, Contacts of PO/TL(s))
2. Namespace Details (Cluster and Link to the 4 namespaces)
3a. Rejection sent to PO/TLs containing:
1. Review comments

flowchart LR
    A((User submits a <br> delete request)) --> B(PrivateCloudAdminDeleteRequest<br>PrivateCloudDeleteRequest)
    B --> C{Admin decides on the request}
    C -->|Request approved| D(PrivateCloudDeleteApproved)
    C -->|Request rejected| E(PrivateCloudDeleteRejected)