_service_networks_table.html.md.erb

Before deploying a service tile that uses the on-demand service broker (ODB),
request the needed network connections to allow components of Pivotal
Cloud Foundry (PCF) to communicate with ODB.

The specifics of how to open those connections varies for each IaaS.

See the following table for key components and their responsibilities in an on-demand
architecture.

<table class="nice">
	<th>Key Components</th>
	<th>Their Responsibilities</th>
	<tr>
		<td><strong>BOSH Director</strong></td>
		<td>Creates and updates service instances as instructed by ODB.</td>
	</tr>
	<tr>
		<td><strong>BOSH Agent</strong></td>
		<td>Includes an agent on every VM that it deploys. The agent
 listens for instructions from the BOSH Director and carries out those instructions.
 The agent receives job specifications from the BOSH Director and uses them to assign
a role, or job, to the VM.</td>
	</tr>
	<tr>
		<td><strong>BOSH UAA</strong></td>
		<td>Issues OAuth2 tokens for clients to
use when they act on behalf of BOSH users.</td>
	</tr>
	<tr>
		<td><strong>PAS</strong></td>
		<td>Contains the apps that are consuming services</td>
	</tr>
	<tr>
		<td><strong>ODB</strong></td>
		<td>Instructs BOSH to create and update services, and connects
to services to create bindings.</td>
	</tr>
	<tr>
		<td><strong>Deployed service instance</strong></td>
		<td>Runs the given data service. For example, the deployed Redis
 for PCF service instance runs the Redis for PCF data service.</td>
	</tr>
</table>