Process to Deploy PubSub+ Cloud in a Customer-Controlled Region

After your initial overview meeting with Solace about installing and deploying PubSub+ Cloud, you follow a five-step process to deploy it.

Prerequisites

Before starting this process ensure that you have:

  • Access to your account in PubSub+ Cloud. This access is provided to you as part of a Welcome letter that you receive when you purchase PubSub+ Cloud.
  • Received the Kubernetes requirements from Solace. These requirements are determined by the technical staff at Solace based on the Customer-Controlled Region Questionnaire you completed when you requested your deployment.

Deployment Steps

To deploy PubSub+ Cloud in your Customer-Controlled Region, you must coordinate with Solace to complete a five-step process:

Screenshot showing the five-step process described in this topic.

Step 5 establishes Messaging Connectivity and doesn’t impact the installation of the deployment of PubSub+ Cloud (Mission Control Agent). This advanced configuration may require multiple levels of approval from your organization’s security and IT teams. Therefore, we recommend that you start this configuration as early as possible.

The following describes the five steps in the process shown in the previous diagram:

  1. Review the Kubernetes Requirements You Received From Solace

    Solace sends you the technical requirements for the Kubernetes cluster to install PubSub+ Cloud in your Customer-Controlled Region. You must review these requirements to ensure they can be satisfied. These requirements result from the collaboration between Solace and your technical stakeholders and are also based on your completed questionnaires. These requirements describe:

    • resource sizing and other architectural details for creating your Kubernetes cluster

    • network details such as addresses and ports that must be configured to allow connectivity to various components of your deployment

    Expected Timeframe for Completion: One week1

  2. Set Up Single Sign-On

    (Optional) If your organization requires Single Sign On (SSO), you work with Solace to enable SSO with PubSub+ Cloud. For more information, see Configuring Single Sign-On with OpenID Connect. This step is not a requirement for subsequent steps but is often a requirement for organizations that require SSO for access to any applications.

    Expected Timeframe for Completion: Two days2

  3. Set Up and Validate Your Kubernetes Cluster

    You are responsible for setting your Kubernetes cluster based on the technical requirements you reviewed. You run a validation tool that’s provided by Solace to ensure that you have correctly configured your Kubernetes cluster. The validation tool lets you know whether your operational and management connectivity is correct. Typically, validation takes less than half an hour. If required, you can contact Solace for an understanding of the results from the validation tool.

    Expected Timeframe for Completion: One week1

  4. Install the Mission Control Agent

    In collaboration with Solace, you install the Mission Control Agent in your Customer-Controlled Region. Solaceis available during the installation to help resolve any issues you encounter. This installation is considered complete when you can successfully create event broker services.

    Expected Timeframe for Completion: One day2

  5. Configure Your Network for Messaging Connectivity

    You must configure the network connectivity between your client messaging applications and your Customer-Controlled Region. This advanced configuration may require multiple levels of approval from your organization’s security and IT teams. Therefore, we recommend that you start this configuration as early as possible.

    Expected Timeframe for Completion: One to Three weeks1

1 The timeframe is an estimate based on previous customer-driven deployments. The actual schedule depends on your team’s timely completion of the parts of the deployment for which you are solely responsible.

2 The timeframe is an estimate and subject to the availability of both parties to collaborate together.

For detailed information about Kubernetes installation, validation, and installing the Mission Control Agent, see Deploying PubSub+ Cloud with Kubernetes .