- BOSH deployed splunk enterprise node in GCP (via bastion)
• assumes gcp account and bosh bastion/nats env available • bosh/cf cli tools • mac dev tools
- xcode-select --install install bosh cli (v2), cf-cli, bosh-init
- brew tap cloudfoundry/tap
- brew install <cf-cli | bosh-init | bosh-cli | credhub-cli | bbl>
- /scripts/GCP_build-release.sh
- /packages/common/spec
- /properties.yml
- /GCP_cf-splunk-full.yml
- ssh into the instance (on bosh) bosh -d cf-splunk-full ssh
- get logs from instance(s) bosh -d cf-splunk-full logs
- deploy bosh -d cf-splunk-full deploy GCP_cf-splunk-full.yml
- create release (bosh) bosh create-release --name cf-splunk --tarball="./release.tgz" --force
-
stemcell will already exist on your director, in this case
ubuntu-trusty
-
Pull latest submodules, namely
src/splunk-firehose-nozzle
git submodule update --init --recursive
-
use deployment manifest: GCP_cf-splunk-forwarder.yml
-
Create a release
This will download Splunk and Golang binaries (if not available already), add necessary blobs, and create the release:
./scripts/build-release.sh
-
Upload & deploy release
-
Iterating
If
splunk-firehose-nozzle
submodule changed upstream, pull latest before creating the release with./scripts/build-release.sh
:
git submodule update src/splunk-firehose-nozzle
(cd src/splunk-firehose-nozzle; git pull origin HEAD)
splunk-forwarder
: bosh managed Splunk heavy forwarder with HTTP event collector enabledspunk-nozzle
: Nozzle that drains firehose logs & forwards to HEC. Should be co-located withsplunk-forwarder
splunk-full
: bosh managed Splunk search head and indexer. Intended for internal testing only (not HA, doesn't persist past rebuilds, etc)