Log Cache Release is a bosh release for Log Cache.
Log Cache can be deployed either as a standalone deployment or within Cloud Foundry.
In both cases Log Cache will have to know about Loggregator.
Every bosh deployment requires a cloud config. The Log Cache deployment manifest assumes the CF-Deployment cloud config has been uploaded.
The first step in deploying Log Cache is to create a release. Final releases are preferable, however during the development process dev releases are useful.
The following commands will create a dev release and upload it to an
environment named lite.
bosh create-release --force
bosh -e lite upload-release --rebase
Standalone Log Cache only has to know where to find Loggregator. The
Loggregator CA is named loggregator_ca. The given variables file should
include the deployed Loggregator's CA.
The following command will deploy a standalone Log Cache against a Loggregator
that is deployed with a loggregator-vars.yml variables file.
bosh \
--environment lite \
--deployment log-cache deploy manifests/log-cache.yml \
--vars-store vars.yml \
--vars-file ~/workspace/loggregator-release/vars.yml
Log Cache deployed within Cloud Foundry reads from the Loggregator system and
registers with the GoRouter at
log-cache.<system-domain> (e.g. for bosh-lite log-cache.bosh-lite.com).
It can be deployed in CF Deployment with the provided operations file.
The following command will deploy Log Cache in CF.
bosh \
--environment lite \
--deployment cf \
deploy ~/workspace/cf-deployment/cf-deployment.yml \
--ops-file ~/workspace/cf-deployment/operations/bosh-lite.yml \
--ops-file ~/workspace/cf-deployment/operations/experimental/use-bosh-dns.yml \
--ops-file ~/workspace/log-cache-release/manifests/operations/deploy-in-cf.yml \
--vars-store ~/workspace/cf-deployment/vars-store.yml \
-v system_domain=bosh-lite.com