Solace PubSub+ Service Plans

Solace PubSub+ for PCF offers multiple operator configurable service plans to support a variety of use cases. Each service plan configures the Solace PubSub+ message broker for a given scaling capacity.

As of release 2.2.0 the Preconfigured Service Plans are now editable by the operator. There are also additional Configurable Service Plans that can also be customized by the operator.

Service instances for any given Service Plan are hosted on VMs which can be created in two ways:

  • Operator Allocated which are controlled in Resource Config during tile installation.
  • On Demand which are triggered by service creation request, and controlled by the operator to set a quota per plan in Service Plan Configuration.

The combination of the operator allocated instances in Resource Config, and the On Demand quota per plan Service Plan Configuration is how an operator can control the maximum number of service instances for each plan.

Service Plan Configuration

Service Plans can be customized by the operator allowing to adjust the plans for both types of Solace PubSub+ message brokers:

  • Solace PubSub+ Enterprise or Enterprise Evaluation Edition message broker
  • Solace PubSub+ Standard message broker
Configurable Properties Applicability
Property Description On Demand Operator Allocated
Active/Inactive
  • An active plan will show up in the marketplace.
    • New service instances for this plan can be created.
  • An inactive plan will not show up in the marketplace.
    • New service instances for this plan cannot be created.
    • A plan can be made inactive only when there are either no service instances, or only operator allocated service instances. The plan will remain displayed in the marketplace in orgs and spaces if it has associated existing service instances, however, tile configurations changes will no longer be applied to these existing service instances.
    • A plan should not be made inactive when there are existing on-demand service instances, as tile deployment will fail.
Plan Name The name that appears in the PCF marketplace for this plan.
Plan Description The plan description that will appear in the CF marketplace.
Detailed Plan Description The description that will appear in Apps Manager.
High Availability If checked, deployment of Message Brokers on this plan will be done in triplets across all availability zones providing a High Availability deployment. The sizing of the Message Brokers will be based on the selected VM Type and Disk Type in this plan. The Sizing of the Monitor node which requires smaller VM Type and Disk Type is based on the General Settings
Service instances A Solace PubSub+ Service Instance represents a Message VPN on a Solace PubSub+ message broker. The ability to host multiple service instances a single Solace PubSub+ message broker for sharing the underlying resources is applicable on Enterprise and Enterprise Evaluation edition message brokers and is limited to a maximum of five service instances. The Standard message broker can only host one service instance. This choice is not dynamic and should not be adjusted after initial tile deployment when there are existing service instances.
Quota Sets the limit on the maximum number of Solace PubSub+ Message Broker deployments that may be created for this service plan across all orgs and spaces. Keeping in mind that this deployment is used to host one or more service instances as defined in the plan by Service instances.
  • This quota is only consulted at the time a service creation request is done.
  • Decreasing the quota will not have an effect on existing service instances if the quota was already exceeded.
VM Type The VM Type on which a service is created. Please see Service Plan Sizing to guide in this selection. The operator is cautioned not to adjust the VM Type without considering the effects on existing on-demand service instances.
  • Increasing the VM Type capacity in CPUs or RAM: New on-demand service instances will benefit. Existing on-demand service instances will not upscale.
  • Reducing the VM Type capacity in CPUs or RAM: Existing on-demand service instances may become inoperable.
1
Disk Type The persistent disk size used by the Message Broker. The size of the persistent disk can be changed both before and after deployment. Increasing the size of the persistent disks will impact the service of already bound apps. However, messages will not be lost. Reducing the size of the persistent disk post-deployment is not recommended and can result in message loss, inoperable Solace PubSub+ message broker, and/or undefined behaviors. 1
Availability Zones Select the availability zones in which deployment instances of this plan will be located. For high availability plans, consider using multiple availability zones for maximum fault tolerance. 2

1 Note: Please set the same matching VM Type and Disk Type if you have Operator Allocated instances in Resource Config.

2 Note: Please consider if using the same Network and AZs used in Assign AZs and Networks for Operator Allocated instances.

General Settings

The Monitor VM Type and Disk Type settings apply to all on-demand plans with High Availability enabled. A Monitor node requires 1 CPU and 1 GB of RAM, adjust the VM Type to match this requirement.

Service Plan Sizing

A deployment of Solace PubSub+ Message Broker will attempt to maximize the use of the underlying resources on any given VM Type.

The deployment will auto select a Scaling Tier based on detected number of CPUs and RAM. This configuration is done at service creation time.

All other plan limits will be auto calculated based on the scaling tier and the Solace PubSub+ message broker type.

Additional Configurable Service Plans

The Solace PubSub+ for PCF tile contains two additional unconfigured plans for both types of Solace PubSub+ message brokers:

  • Solace PubSub+ Standard message broker

    • Standard Plan 3
    • Standard Plan 4
  • Solace PubSub+ Enterprise or Enterprise Evaluation Edition message broker

    • Enterprise Plan 5
    • Enterprise Plan 6

Preconfigured Service Plans

Solace PubSub+ for PCF version 2.1.x and earlier contained these preconfigured service plans which were not operator configurable.

Each plan is supported by VM Type intended to match the plan name and descriptions. Without any modifications, the default settings of these plans will match the same settings for Solace PubSub+ for PCF version 2.1.x to ensure backwards compatibilities for deployments with existing service instances.

An operator is cautioned not to make these plans inactive or alter these plans without considering the effects on existing service instances.

If there are existing service instances on these plans, the operator should use the Additional Configurable Service Plans to create customized plans.

Standard Medium Plan

Description
A single message VPN on a dedicated Solace PubSub+ Standard message broker with associated properties set to moderate values.
VM Pool Standard Medium
Service Instances per VM 1
Property Max # per Service Instance
Bindings 500
Connections 1,000
Subscriptions 500,000
Transacted Sessions 1,000
Transactions 5,000
Endpoints 1,000

Standard Medium HA Plan

Description
A single message VPN spanning 3 Solace PubSub+ Standard message brokers in a high availability (HA) configuration with associated properties set to moderate values.
VM Pool Standard Medium-HA
Service Instances per VM 1
Property Max # per Service Instance
Bindings 500
Connections 1,000
Subscriptions 500,000
Transacted Sessions 1,000
Transactions 5,000
Endpoints 1,000


Enterprise Shared Plan

Description
A single Message VPN in a shared Solace PubSub+ Enterprise or Enterprise Evaluation Edition message broker. Useful for light traffic and development.
VM Pool Enterprise Shared
Service Instances per VM 5
Property Max # per Service Instance
Bindings 190
Connections 200
Subscriptions 100,000
Transacted Sessions 200
Transactions 1,000
Endpoints 200

Enterprise Large Plan

Description
A single message VPN on a dedicated Solace PubSub+ Enterprise or Enterprise Evaluation Edition message broker with associated properties set to high values.
VM Pool Enterprise Large
Service Instances per VM 1
Property Max # per Service Instance
Bindings 9,990
Connections 10,000 - ( REST Connections 6000 )
Subscriptions 500,000
Transacted Sessions 10,000
Transactions 50,000
Endpoints 10,000

Enterprise Medium HA Plan

Description
A single message VPN spanning 3 Solace PubSub+ Enterprise or Enterprise Evaluation Edition message brokers in a high availability (HA) configuration with associated properties set to moderate values.
VM Pool Enterprise Medium-HA
Service Instances per VM 1
Property Max # per Service Instance
Bindings 990
Connections 1,000
Subscriptions 500,000
Transacted Sessions 1,000
Transactions 5,000
Endpoints 1,000

Enterprise Large HA Plan

Description
A single message VPN spanning 3 Solace PubSub+ Enterprise or Enterprise Evaluation Edition message brokers in a high availability (HA) configuration with associated properties set to high values.
VM Pool Enterprise Large-HA
Service Instances per VM 1
Property Max # per Service Instance for Enterprise tile
Bindings 9,990
Connections 1,0000 - ( REST Connections 6000 )
Subscriptions 500,000
Transacted Sessions 10,000
Transactions 50,000
Endpoints 10,000

Sample Standard Plan Configuration

Sample on demand standard

Sample Enterprise Plan Configuration

Sample on demand enterprise

Create a pull request or raise an issue on the source for this page in GitHub