Deploying a Nozzle to your Cloud Foundry Loggregator Firehose

Learn how to deploy a nozzle app to the VMware Tanzu Application Service for VMs (TAS for VMs) Loggregator Firehose.

For more information about nozzles and the Loggregator Firehose, see Loggregator Architecture. The TAS for VMs Loggregator team created an example nozzle app for use with this tutorial.

The following procedure deploys an example nozzle to the Firehose of a TAS for VMs installation deployed locally with BOSH Lite v2. For more information about BOSH Lite v2, see VirtualBox BOSH Lite v2 in the BOSH documentation.

To reduce the load on custom nozzles that you develop, you can request Firehose subscriptions that emit only metrics on an allow list. For examples, see rlpreader and rlptypereader in the Loggregator Tools repository and V2 Subscriptions in the Loggregator Release repository in GitHub.

If you don’t want to use the Firehose, you can configure an aggregate log and metric drain for your foundation. For more information, see Configure System Logging in Configuring TAS for VMs.

Prerequisites

Before you deploy a nozzle to the Loggregator Firehose, you must have:

BOSH CLI installed locally. For more information, see BOSH CLI in the BOSH documentation.
Spiff installed locally and added to the load path of your shell. For more information, see the Spiff repository on GitHub.
BOSH Lite v2 deployed locally using VirtualBox. For more information about BOSH Lite v2, see VirtualBox BOSH Lite v2 in the BOSH documentation.
A working TAS for VMs deployment, including Loggregator, deployed with your local BOSH Lite v2. This deployment serves as the source of data. Use the provision_cf script included in the BOSH Lite v2 release.

Note Deploying TAS for VMs can take several hours depending on your internet bandwith, even when using the automated provision_cf script. ## Step 1: Downloading Cloud Foundry BOSH manifest To download the BOSH manifest: 1. Run `bosh deployments` to identify the name of your current BOSH deployment:

  $ bosh deployments
  +-------------+--------------+-------------------------------------------------+
  | Name        | Release(s)   | Stemcell(s)                                     |
  +-------------+--------------+-------------------------------------------------+
  | cf-example  | cf-mysql/10  | bosh-vsphere-esxi-ubuntu-trusty-go_agent/2690.3 |
  |             | cf/183.2     |                                                 |
  +-------------+--------------+-------------------------------------------------+

Run bosh manifest -d MY-DEPLOYMENT MY-MANIFEST to download and save each BOSH deployment manifest. You need this manifest to locate information about your databases. Repeat these instructions for each manifest. Replace MY-DEPLOYMENT with the name of the current BOSH deployment. For this procedure, use cf.yml as MY-MANIFEST.
```
$ bosh manifest -d cf-example cf.yml
Deployment manifest saved to `cf.yml'
```
Place the .yml file in a secure location.

Step 2: Adding UAA client

You must authorize the example nozzle as a UAA client for your TAS for VMs deployment. To do this, add an entry for the example nozzle as a client for uaa under the properties key in your TAS for VMs deployment manifest YAML file. You must enter the example nozzle object in the correct location in the manifest, and with the correct indentation.

To add the nozzle as a UAA client for your deployment:

Open the deployment manifest in a text editor.
Locate the left-aligned properties key.
Under the properties key, locate uaa at the next level of indentation.
Under the uaa key, locate the clients key at the next level of indentation.

Enter properties for the example-nozzle at the next level of indentation, exactly as shown below. The ... in the text below indicate other properties that might populate the manifest at each level in the hierarchy.

properties:
  ...
  uaa:
  ...
    clients:
    ...
      example-nozzle:
        access-token-validity: 1209600
        authorized-grant-types: client_credentials
        override: true
        secret: example-nozzle
        authorities: oauth.login,doppler.firehose

Save the deployment manifest file.

Step 3: Redeploying TAS for VMs

To redeploy TAS for VMs with BOSH, run:

bosh -e BOSH-ENVIRONMENT deploy

Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director.

For example:

$ bosh -e dev deploy
Acting as user 'admin' on deployment 'cf-warden' on 'Bosh Lite Director'
Getting deployment properties from director...
Detecting deployment changes
----------------------------
Releases
No changes
Compilation
No changes
Update
No changes
Resource pools
No changes
Disk pools
No changes
Networks
No changes
Jobs
No changes
Properties
uaa
clients
example-nozzle
    + access-token-validity: 1209600
    + authorized-grant-types: authorization_code,client_credentials,refresh_token
    + override: true
    + secret: example-nozzle
    + scope: openid,oauth.approvals,doppler.firehose
    + authorities: oauth.login,doppler.firehose
Meta
No changes
Please review all changes carefully
Deploying
---------
Are you sure you want to deploy? (type 'yes' to continue):yes

Step 4: Cloning an example release

The TAS for VMs Loggregator team created an example nozzle app for use with this tutorial.

To clone the example nozzle release:

Clone the main release repository from the example-nozzle-release repository on GitHub by running:
```
git clone https://github.com/cloudfoundry-incubator/example-nozzle-release.git
```
Go to the example-nozzle-release directory by running:
```
cd example-nozzle-release
```

Update all of the included submodules by running:

 git submodule update --init --recursive

For example:

$ git submodule update --init --recursive
Submodule 'src/github.com/cloudfoundry-incubator/example-nozzle' (git@github.com:cloudfoundry-incubator/example-nozzle.git) registered for path 'src/github.com/cloudfoundry-incubator/example-nozzle'
Submodule 'src/github.com/cloudfoundry-incubator/uaago' (git@github.com:cloudfoundry-incubator/uaago.git) registered for path 'src/github.com/cloudfoundry-incubator/uaago'
...
Cloning into 'src/github.com/cloudfoundry-incubator/example-nozzle'...
...

Step 5: Preparing Nozzle manifest

To prepare the nozzle deployment manifest:

In the example-nozzle-release directory, navigate to the templates directory by running:
```
cd templates
```
Within this directory, examine the two YAML files. bosh-lite-stub.yml contains the values used to populate the missing information in template.yml. By combining these two files, you can create a deployment manifest for the nozzle.
Create a tmp directory for the compiled manifest.
Use Spiff to compile a deployment manifest from the template and stub by running:
```
spiff merge templates/template.yml templates/bosh-lite-stub.yml > tmp/manifest_bosh_lite.yml
```
Save this manifest.
To identify the names of all deployments in the environment that you specify, run:
```
bosh -e BOSH-ENVIRONMENT deployments
```
Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director.
To obtain your BOSH Director UUID, run:
```
bosh -e BOSH-ENVIRONMENT env --column=uuid
```
Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director. For example:
```
$ bosh -e dev env --column=uuid
```

In the compiled nozzle deployment manifest, locate the director_uuid property. Replace PLACEHOLDER-DIRECTOR-UUID with your BOSH Director UUID.

compilation:
  cloud_properties:
    name: default
network: example-nozzle-net
reuse_compilation_vms: true
workers: 1
director_uuid: PLACEHOLDER-DIRECTOR-UUID

NoteIf you do not want to see the complete deployment procedure, you can run scripts/make_manifest_spiff_bosh_lite to automatically prepare the manifest.

Step 6: Creating Nozzle BOSH release

To create a nozzle BOSH release, run:

bosh -e BOSH-ENVIRONMENT create-release --name RELEASE-NAME

Where:

BOSH-ENVIRONMENT is the alias that you set for your BOSH Director.
RELEASE-NAME is example-nozzle to match the UAA client that you created in the TAS for VMs deployment manifest.

For example:

$ bosh -e dev create-release --name example-nozzle
Syncing blobs...
...

Step 7: Uploading Nozzle BOSH release

Upload the nozzle BOSH release that you created in Step 6: Create Nozzle BOSH Release above.

To upload the BOSH release, run:

bosh -e BOSH-ENVIRONMENT upload-release

Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director.

For example:

$ bosh -e dev upload-release
Acting as user 'admin' on 'Bosh Lite Director'

Copying packages
\----------------
example-nozzle
golang1.7

Copying jobs
\------------
example-nozzle

Generated   /var/folders/4n/qs1rjbmd1c5gfb78m3_06j6r0000gn/T/d20151009-71219-17a5m49/d20151009-71219-rts928/release.tgz
Release size: 59.2M

Verifying release...
...
Release info
\------------
Name: nozzle-test
Version: 0+dev.2

Packages
- example-nozzle (b0944f95eb5a332e9be2adfb4db1bc88f9755894)
- golang1.7 (b68dc9557ef296cb21e577c31ba97e2584a5154b)

Jobs
- example-nozzle (112e01c6ee91e8b268a42239e58e8e18e0360f58)

License
- none

Uploading release

Step 8: Deploying Nozzle

To deploy the nozzle, run:

bosh -e BOSH-ENVIRONMENT deploy

Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director.

For example:

$ bosh -e dev deploy
Acting as user 'admin' on deployment 'example-nozzle-lite' on 'Bosh Lite Director'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Cannot get current deployment information from director, possibly a new deployment
Please review all changes carefully

Deploying
\---------
Are you sure you want to deploy? (type 'yes' to continue):yes

Step 9: Viewing Nozzle output

The example nozzle outputs all of the data originating coming from the Firehose to its log files. To view this data, SSH into the example-nozzle VM and examine the logs.

To view nozzle output:

Access the nozzle VM at the IP address configured in the nozzle manifest template stub, ./templates/bosh-lite-stub.yml, by running:

bosh -e BOSH-ENVIRONMENT ssh

Where BOSH-ENVIRONMENT is the alias that you set for your BOSH Director. For example:

$ bosh -e dev ssh example-nozzle
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.19.0-25-generic x86_64)
Documentation: https://help.ubuntu.com/ Last login: Wed Sep 23 21:29:50 2015 from 192.0.2.1

Use the cat command to output the stdout log file.

$ cat /var/vcap/sys/log/example-nozzle/example-nozzle.stdout.log
===== Streaming Firehose (will only succeed if you have admin credentials)
origin:"bosh-system-metrics-forwarder" eventType:ValueMetric timestamp:1541091851000000000 deployment:"cf-c42ae2c4dfb6f67b6c27" job:"loggregator_trafficcontroller" index:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" ip:"" tags:>key:"id" value:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" > tags:>key:"source_id" value:"bosh-system-metrics-forwarder" > valueMetric:>"system.swap.percent" value:0 unit:"Percent" >
origin:"bosh-system-metrics-forwarder" eventType:ValueMetric timestamp:1541091851000000000 deployment:"cf-c42ae2c4dfb6f67b6c27" job:"loggregator_trafficcontroller" index:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" ip:"" tags:>key:"id" value:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" > tags:>key:"source_id" value:"bosh-system-metrics-forwarder" > valueMetric:>"system.swap.kb" value:0 unit:"Kb" >
origin:"bosh-system-metrics-forwarder" eventType:ValueMetric timestamp:1541091851000000000 deployment:"cf-c42ae2c4dfb6f67b6c27" job:"loggregator_trafficcontroller" index:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" ip:"" tags:>key:"id" value:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" > tags:>key:"source_id" value:"bosh-system-metrics-forwarder" > valueMetric:>"system.disk.ephemeral.percent" value:3 unit:"Percent" >
origin:"bosh-system-metrics-forwarder" eventType:ValueMetric timestamp:1541091851000000000 deployment:"cf-c42ae2c4dfb6f67b6c27" job:"loggregator_trafficcontroller" index:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" ip:"" tags:>key:"id" value:"d1dffe15-5894-44de-b7f0-ad43161a0a7b" > tags:>key:"source_id" value:"bosh-system-metrics-forwarder" > valueMetric:>"system.healthy" value:1 unit:"b" >
origin:"gorouter" eventType:ValueMetric timestamp:1541091851218590916 deployment:"cf-c56ab7c4dfb6f67b6c28" job:"router" index:"d5d1b5a4-2497-4679-8d3b-66ffc978d829" ip:"10.0.4.13" tags:>key:"source_id" value:"gorouter" > valueMetric:>"uptime" value:3.273478e+06 unit:"seconds" >
origin:"netmon" eventType:ValueMetric timestamp:1541091851234217334 deployment:"cf-c56ab7c4dfb6f67b6c28" job:"diego_cell" index:"8007afda-3bff-4856-857f-a47a43cbf994" ip:"10.0.4.18" tags:>key:"source_id" value:"netmon" > valueMetric:>name:"numGoRoutines" value:13 unit:"count" >
origin:"netmon" eventType:ValueMetric timestamp:1541091851234129669 deployment:"cf-c56ab7c4dfb6f67b6c28" job:"diego_cell" index:"8007afda-3bff-4856-857f-a47a43cbf994" ip:"10.0.4.18" tags:>key:"source_id" value:"netmon" > valueMetric:>"numCPUS" value:2 unit:"count" >
origin:"netmon" eventType:ValueMetric timestamp:1541091851234292367 deployment:"cf-c56ab7c4dfb6f67b6c28" job:"diego_cell" index:"8007afda-3bff-4856-857f-a47a43cbf994" ip:"10.0.4.18" tags:>key:"source_id" value:"netmon" > valueMetric:>"memoryStats.numBytesAllocated" value:542328 unit:"count" >
origin:"netmon" eventType:ValueMetric timestamp:1541091851234279470 deployment:"cf-c56ab7c4dfb6f67b6c28" job:"diego_cell" index:"8007afda-3bff-4856-857f-a47a43cbf994" ip:"10.0.4.18" tags:>key:"source_id" value:"netmon" > valueMetric:>"memoryStats.numBytesAllocatedStack" value:655360 unit:"count" >
...