Installing and Configuring the a9s Elasticsearch for PCF

This topic describes how to install and configure a9s Elasticsearch for Pivotal Cloud Foundry (PCF).

Prerequisites

Before installing a9s Elasticsearch for PCF, ensure that you have installed and configured the products and tiles listed in Requirements.

Install a9s Elasticsearch for PCF

  1. Download the product file from Pivotal Network.

  2. Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  3. Click Add next to the uploaded a9s Elasticsearch for PCF tile in the Ops Manager Available Products view to add it to your staging area.

  4. Click the newly added tile and select Settings > Assign AZs and Networks.

  5. Configure the location of service instance jobs. Configure your network to balance cluster jobs between as many AZs as possible.

    AZ and networks tab"

  6. (Optional) Review the remaining configuration panes. For more information on how to configure the properties of each pane, see the following:

  7. Click Apply Changes to deploy the service.

Configure Service Plan VMs

You can configure the dimensions of the VMs used to provision service instances of a given service plan in the IaaS Settings pane of the a9s BOSH for PCF tile.

The following table describes which Cloud-Config fields in the a9s BOSH for PCF tile correspond to which a9s Elasticsearch for PCF service plans.

Service Plan Cloud-Config Fields
elasticsearch-single-small elasticsearch-cluster-small Cloud properties of the VM Type Small
Cloud properties of the Disk Type Small
elasticsearch-single-big
elasticsearch-cluster-big
Cloud properties of the VM Type Big
Cloud properties of the Disk Type Big

For information about setting VM dimensions, see About Configuring a9s BOSH for PCF.

Configure a9s Elasticsearch for PCF

The following sections describe the optional configuration panes in the a9s Elasticsearch for PCF tile.

Errands

The Errands pane lists BOSH errands executed by the tile. For information about what each errand does and guidance for activating or deactivating each errand, see the following table:

Errand Description
Run BOSH Configurator Uploads the stemcells required for the BOSH release so that a9s BOSH for PCF can provision Elasticsearch instances. Deactivating this errand may speed up the deployment of tiles.

Note: Pivotal recommends leaving this errand selected to keep the tile configuration up-to-date.

Run Template Uploader Applies Elasticsearch-specific configurations to generic components of a9s Elasticsearch for PCF. This errand must run at least once. Deactivating this errand may speed up the deployment of tiles.

Note: Pivotal recommends leaving this errand selected to keep the tile configuration up-to-date.

Run Broker Registrar Registers the a9s Elasticsearch for PCF service broker with Elastic Runtime to make the service available in the marketplace.
Run Broker Deregistrar Deregisters the a9s Elasticsearch for PCF service broker with Elastic Runtime and removes the service from the marketplace.
Run Smoke Tests This errand runs basic tests against your a9s Elasticsearch for PCF installation to confirm configuration. Tests typically take over 30 minutes.

Resource Config

You can configure the dimensions of the VMs that host the a9s Elasticsearch for PCF components. This configuration does not cover the dedicated Elasticsearch instances that run on VMs provided by the a9s BOSH tile for PCF. For more information, see Configure Service Plan VMs.

Note: Pivotal recommends using a VM Type of large or greater to support the tile compilation.

Stemcell

If you want to use a stemcell other than the default one, upload it in the Stemcell pane.

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub