Networking for On-Demand Services

Warning: Redis for PCF v1.14 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

Page last updated:

This section describes networking considerations for the Redis for Pivotal Cloud Foundry (PCF) on-demand service.

Service Network Requirement

When you deploy Pivotal Cloud Foundry, you must create a statically defined network to host the component VMs that make up the Pivotal Cloud Foundry infrastructure. Pivotal Cloud Foundry components, such as Cloud Controller and UAA, run on this infrastructure network.

On-demand Pivotal Cloud Foundry services might require you to host them on a separate network from the Pivotal Cloud Foundry default network. You can also deploy on-demand services on a separate service networks to meet your own security requirements.

Pivotal Cloud Foundry supports dynamic networking. Operators can use dynamic networking with asynchronous service provisioning to define dynamically-provisioned service networks. For more information, see Default Network and Service Network below.

On-demand services are enabled by default on all networks. Operators can optionally create separate networks to host services in BOSH Director. Operators can select which network hosts on-demand service instances when they configure the tile for that service. © 2019 GitHub, Inc.

Default Network and Service Network

On-demand Redis for Pivotal Cloud Foundry services use BOSH to dynamically deploy VMs and create single-tenant service instances in a dedicated network. On-demand services use the dynamically-provisioned service network to host single-tenant worker VMs. These worker VMs run as service instances within development spaces.

This on-demand architecture has the following advantages:

  • Developers can provision IaaS resources for their services instances when the instances are created. This removes the need for operators to pre-provision a fixed amount of IaaS resources when they deploy the service broker.
  • Service instances run on a dedicated VM and do not share VMs with unrelated processes. This removes the “noisy neighbor” problem, where an app monopolizes resources on a shared cluster.
  • Single-tenant services can support regulatory compliances where sensitive data must be separated across different machines.

An on-demand service separates operations between the default network and the service network. Shared service components, such as executive controllers and databases, Cloud Controller, UAA, and other on-demand components, run on the default network. Worker pools deployed to specific spaces run on the service network.

The diagram below shows worker VMs in an on-demand service instance running on a separate services network, while other components run on the default network.

View a larger version of this image

Required Networking Rules for On-Demand Services

Before deploying a service tile that uses the on-demand service broker (ODB), you must create networking rules to enable Pivotal Platform components to communicate with ODB. For instructions for creating networking rules, see the documentation for your IaaS.

The following table lists key components and their responsibilities in the on-demand architecture.

Key Components Component Responsibilities
BOSH Director Creates and updates service instances as instructed by ODB.
BOSH Agent Adds an agent on every VM that it deploys. The agent listens for instructions from the BOSH Director and executes those instructions. The agent receives job specifications from the BOSH Director and uses them to assign a role or job to the VM.
BOSH UAA Issues OAuth2 tokens for clients to use when they act on behalf of BOSH users.
Pivotal Application Service Contains the apps that consume services.
ODB Instructs BOSH to create and update services. Connects to services to create bindings.
Deployed service instance Runs the given service. For example, a deployed Redis for Pivotal Platform service instance runs the Redis for Pivotal Platform service.


Regardless of the specific network layout, the operator must ensure network rules are set up so that connections are open as described in the table below.

Source Component Destination Component Default TCP Port Notes
ODB BOSH Director

BOSH UAA
25555 8443 8844 The default ports are not configurable.
ODB PAS 8443 The default port is not configurable.
Errand VMs PAS

ODB

Deployed service instances
8443 8080 6379 12345 The default ports are not configurable.
BOSH Agent BOSH Director 4222 The BOSH Agent runs on every VM in the system, including the BOSH Director VM. The BOSH Agent initiates the connection with the BOSH Director.
The default port is not configurable.

The communication between these components is two-way.
Deployed apps on PAS Deployed service instances 6379 This is the default port where Redis is deployed.
PAS ODB 12345 The default port is not configurable.

For a complete list of ports and ranges used in Redis for PCF, see Network Configuration.