Skip to content

Mop for GSS new UI ΒΆ

  1. Deployment for Ohio(us-east-2)
    1. Deploy backend Ohio
    2. Health check for service: https://service-status-us-east-2.webex.com/ping and https://service-status-us-east-2.webex.com/customer/dashServices/891
    3. Call modifyHistoryIncidents api(https://service-status-us-east-2.webex.com/status/incidents/history/891 PUT) to set all history non-FedRAMP incidents to Commercial
    4. Deploy frontend Ohio
    5. Check customer page(https://us-east-2.globalservicestatus.com), should view all history components in Commercial Status page, no components in Government Status page
    6. Add help link for all commercial components 1. Webex Meetings: https://help.webex.com/en-us/article/xcwws1/What-s-New-for-the-Latest-Channel-of-Webex-Meetings 2. Webex App: https://help.webex.com/en-US/article/8dmbcr/Webex-%7C-What 3. Webex Control Hub: https://help.webex.com/en-us/article/u9dlxd/What-s-New-in-Control-Hub 4. Webex Cloud Registered Devices: https://help.webex.com/en-US/article/6ger7db/What 5. Webex Hybrid Services: https://help.webex.com/en-us/6vkj1i/What-s-New-With-Cisco-Webex-Hybrid-Services 6. Webex Calling: https://help.webex.com/en-us/landing/ld-nzid8xi-WebexCalling/Webex-Calling 7. Webex Contact Center: https://help.webex.com/en-us/a1gx3h/What-s-New-in-Cisco-Webex-Contact-Center 8. Webex for BroadWorks: https://help.webex.com/en-us/ne4v0oy/What-s-New-in-Webex-for-BroadWorks 9. UCM Cloud: https://help.webex.com/en-US/landing/ld-nm13dbe-UCMCloud/UCM-Cloud 10. Developer API: https://developer.webex.com/ 11. Webex for Government: https://help.webex.com/en-us/article/ycv8q3/What's-new-in-Webex-for-Government 12. Slido: https://help.webex.com/en-us/article/nmrk74x/Integrate-Slido-with-Webex-App#Cisco_Concept.dita_bc4be90b-f2f7-4f2a-b106-2187b0624943 13. Webex Events (formally Socio): https://help.webex.com/en-us/article/6xg8gd/Help-with-Webex-Events-(formerly-Socio)
  2. Deployment for California(us-west-1) 1. Deploy backend California 2. Health check for service: https://service-status-us-west-1.webex.com/ping and https://service-status-us-west-1.webex.com/customer/dashServices/891 3. Call modifyHistoryIncidents api(https://service-status-us-west-1.webex.com/status/incidents/history/891 PUT) to set all history non-FedRAMP incidents to Commercial 4. Deploy frontend California 5. Check customer page(https://us-west-1.globalservicestatus.com), should view all history components in Commercial Status page, no components in Government Status page 6. Add help link for all commercial components
  3. Deployment for Virginia(us-east-1) 1. Deploy backend Virginia 2. Check the current region: https://service-status.webex.com/ping 3. Health check for service: https://service-status.webex.com/customer/dashServices/891 4. Call modifyHistoryIncidents api(https://service-status.webex.com/status/incidents/history/891 PUT) to set all history non-FedRAMP incidents to Commercial 5. Deploy frontend Virginia 6. Check customer page(https://status.webex.com), should view all history components in Commercial Status page, no components in Government Status page 7. Add help link for all commercial components