Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip

Tip: The support and maintenance tasks discussed here are subjected to the WSO2 Managed Cloud Service Policy and Service Level Agreement.

...

Send weekly status updates

...

  • A summary of the hosting-related JIRAs raised for the Managed CloudService.
  • A summary of the maintenance tasks done during the current week.
  • A summary of the maintenance work scheduled for the next week, including any scheduled downtimes.

...

If an unplanned interruption that affects the availability, quality, or performance of the services managed by the WSO2 Managed Cloud Service team occurs, we call it a hosting incident. A hosting incident might occur in deployment, upgrade, maintenance, network configuration, startup, stopping, monitoring, and performance, and it has to be within the scope of the Managed CloudService's deployment architecture.

...

Note that the customer needs to either raise a support JIRA through  the support Website  or call the phone support numbers to report a hosting incident. As you need to be a WSO2 production support customer to receive WSO2 Managed Cloud services, we assume you already have a support account in the WSO2 support system. If not, please talk to your account's manager at WSO2.

...

Tip

Tip: Also see WSO2 Managed Cloud Service Production Support Guidelines .

...

A task is an action item that either the customer or WSO2 needs to perform to ensure that certain objectives are met. For example, the WSO2 Managed Cloud Service team may create a task for the customer to provide details on their production environment.

...

A deployment artifact is a program, config change, patch etc. that the customer or WSO2 deploys to the Managed CloudDeployment, either manually or via automated scripts.  Both the customer and WSO2 need to follow the below best practices to minimize the possibility of new artifact deployments causing issues in the Cloud setup:

...