Process to Deploy PubSub+ Cloud in a Dedicated Region

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

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 and reviewed the requirements for the Dedicated Region. These requirements are determined by the technical staff at Solace based on the Dedicated Region Questionnaire you completed when you requested your deployment.

Deployment Steps

To deploy a Dedicated Region, you complete a four-step process with the expected timelines as shown in the following diagram . The timelines are based on typical conditions and good coordination between the Solace and your organization.

Step 4 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. For more information, see Networking Options for Dedicated Region Deployments.

The four steps in the process include:

  1. Review the Kubernetes Requirements You Received From Solace

    Solace sends the details of the Dedicated Region and the installation of PubSub+ Cloud that will be completed for you. You must review these requirements and confirm that they are correct. These requirements result from the collaboration between Solace and your technical stakeholders, and are also based on your completed questionnaires. These requirements define:

    • the region and architectural details of the Kubernetes cluster in the Dedicated Region

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

    • As part of the review, you must confirm:

      • the maximum number of event broker services required in the Kubernetes
      • the CIDR size fits into your network plan based on the CIDR calculator

      • the networking options that you want to use

    Expected Timeframe for Completion: Approximately 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: Approximately two days3

  3. Set Up and Validate Kubernetes Cluster, and Install PubSub+ Cloud for the Dedicated Region

    For a Dedicated Region, Solace sets up the requested Kubernetes cluster and region based on your requirements. Solace validates the operational and management connectivity is correct. In addition, installs the Mission Control Agent, and deploys PubSub+ Cloud to the region. As a last step, Solace verifies an event broker service can be created.

    Expected Timeframe for Completion: Approximately one day2

  4. Configure Network for Messaging Connectivity Between Your applications and the Dedicated Region

    Solace collaborates with you to configure the network connectivity between your client messaging applications and the Dedicated Region. This advanced configuration may require multiple levels of approval from your organization’s security and IT teams and that approval or changes are required, this may additional time. Therefore, we recommend that you start this configuration as early as possible and in ideal situations, this time is one week. For more information, see Networking Options for Dedicated Region Deployments.

    Expected Timeframe for Completion: Approximately one week3

1 The timeframe is an estimate based on previous Dedicated Region deployments and is dependent on the customer completing the action. Timeframes above the estimates are often due to customer-based delays.

2 The timeframe is an estimate based on previous Dedicated Region deployments.

3 The timeframe is a best-case estimate based on previous deployments and does not include the time elapsed for approvals within your organization. It's important for you to recognize that the timeframe is an estimate that is subject to the completion of necessary approvals and the availability of both parties to collaborate. If you require a networking configuration that requires multiple levels of approval in from the customer's security and IT teams, this timeframe may be extended.