Deployment Roles and Responsibilities

Solace works with the customer to gather the technical requirements of the deployment.

For Kubernetes, you can determine many of the technical details by answering the questions in Questionnaire: Deploying in a Customer-Controlled Cluster.

In a Public Cluster, Solace is responsible for the cluster configuration, including ensuring that sufficient IaaS resources are available.

In a Customer-Controlled Cluster, the customer is responsible for cluster configuration, including ensuring that sufficient IaaS resources are available. Solace can assist with solution architecture.

In a Public Cluster or Dedicated Cluster, Solace installs and validates the Mission Control Agent.

In a Customer-Controlled Cluster, the customer is responsible for installing the Mission Control Agent, using a values.yaml configuration file (see Private Regions) with assistance from Solace.

Solace works with the customer to set up the first event broker service and validate end-to-end functioning. This step does not include validating customer applications.

Solace can create new data centers or regions at the customer's request. To request additional data centers or regions, contact Solace.

Customers create event broker services using Mission Control.

These system-level settings are configured automatically by Solace Cloud when you create your event broker service.

Customers directly configure application-level settings using Broker Manager or SEMP.

Certain functionality must be manually configured and enabled by the Solace Cloud team. To request this functionality, contact Solace.

You can configure VPN Bridges using Broker Manager or SEMP.

You can configure your event mesh using Mesh Manager.

If you are configuring event mesh with replication (for the proposes of disaster recovery), see Using Replication for Disaster Recovery of Event Broker Services.

If you require an internally-linked DMR cluster, it must be manually configured by Solace. To request this functionality, contact Solace

For the DMR clusters required for configuring replication, you are responsible. For more information, see Using Replication for Disaster Recovery of Event Broker Services.

After Solace Insights is enabled in your account, you can set up the email addresses that you want to use and tune the alerts that you want to receive.

Replication must be manually configured. To request this functionality, contact Solace. For more information, see Using Replication for Disaster Recovery of Event Broker Services.

After replication has been configured for your event broker services, you can modify the related application-level settings using Broker Manager.

Solace is responsible for monitoring, managing, and communicating incidents concerning Public Cluster and Dedicated Cluster infrastructure, including:

• Solace Home Cloud
• Mission Control
• Solace Event Portal
• Solace Insights
• Solace Cloud Console
• Event broker services and IaaS resources in Public Cluster and Dedicated Cluster

Solace follows internal Incident Management Procedures that comply with SOC2 standards.

The customer is responsible for monitoring IaaS resources in cloud regions that they control. Joint troubleshooting with Solace may be required to resolve some IaaS issues.

The customer is responsible for monitoring their applications using Insights. The default configuration provides this functionality for customers.

The customer must update certificates before they expire. To request assistance, contact Solace .

The customer is responsible for proactively monitoring their event mesh using Insights.

Solace can provide assistance to resolve issues.

The customer is responsible for monitoring their replication connectivity and status using SEMPv2 or Insights.

Solace can provide assistance to resolve issues. For more information, see Using Replication for Disaster Recovery of Event Broker Services.

In a Public Cluster or Dedicated Cluster, Solace is responsible for maintaining IaaS operations. See Upgrading Public Clusters and Dedicated Clusters.

In a Customer-Controlled Cluster, the customer is responsible for maintaining IaaS operations, including the health of the Kubernetes cluster. See Upgrading Customer-Controlled Clusters.

Solace can provide assistance to resolve issues.

The customer is responsible for troubleshooting and resolving application-level issues.

Solace can provide assistance to resolve issues.

The customer is responsible for keeping replication operationally up. Joint troubleshooting with Solace may be required to resolve some issues. For more information, see Using Replication for Disaster Recovery of Event Broker Services.

The customer is responsible for ensuring that the event broker services, are adequately scaled.

Solace can assist with solution architecture and capacity planning.

The customer is responsible for planning when to upscale their event broker services.

Upscaling may require additional configuration or activation in the Solace Home Cloud. Consult Solace for assistance with this activity. For more information about upscaling, see Upscaling Event Broker Services.

Solace Cloud currently does not support restoring event broker services after deletion.

Solace Cloud currently does not support restoring event broker services after deletion.

In a Solace-controlled region, Solace is responsible for restoring service after IaaS problems.

In a Customer-Controlled Cluster, the customer is responsible for restoring service after IaaS problems.

Solace can provide assistance to troubleshoot and resolve issues.

Event broker services are automatically configured as high availability (HA) services. Optionally, you can also configure disaster recovery (DR) using the replication feature. With both HA and DR configured, backing up and restoring the broker configuration should not be necessary.

Solace Cloud does not provide any built-in functionality to back up and restore broker configuration. The customer must configure an alternative solution if required. For more information, see Backing up Event Broker Services.

In a Public Cluster, Solace is responsible for the configuration, monitoring, and operation of the Kubernetes cluster.

In Public Clusters, Solace is responsible for configuring, monitoring and resolving issues with VPC peering.

Peering between Dedicated Clusters or Public Clusters and customer VPCs requires that the customer assist with configuration and provide Solace with the required access to the customer network. In this scenario, Solace is responsible for maintaining only the Public Cluster and Dedicated Cluster parts of the network.

Solace updates both the Solace Cloud platform and the Cloud Console.

In a Public Cluster, Solace is responsible for upgrading the Mission Control Agent.

In a Customer-Controlled Cluster, the Mission Control Agent is self-upgrading in Kubernetes deployments, and Solace is responsible for the upgrade.

Any upgrade issues are coordinated with the customer.

You are responsible for scheduling an upgrade slot after the full support phase ends.

When the technical support phase ends, if you have not yet scheduled an upgrade slot for your event broker services, Solace automatically upgrades them to the latest production release (that supports upgrades). For more information about scheduling an upgrade slot and upgrades, see Upgrading Event Broker Services in Solace Cloud.

Generally, customers don't need to be present on a call to coordinate the upgrade, but it is recommended to include contact information when booking an upgrade slot in Calendly in case issues arise. In some deployments to Customer-Controlled Clusters, the customer is required to be present on a call based on the network connectivity configuration.

For details about upgrades, availability, and release cadence, see Upgrading Event Broker Services in Solace Cloud.