bosh-deployment

This repository is intended to serve as a reference and starting point for developer-friendly configuration of the Bosh Director. Consume the master branch. Any changes should be made against the develop branch (it will be automatically promoted once it passes tests).

Important notice for users of bosh-deployment and Bosh DNS versions older than 1.28

As of Bosh DNS version 1.28, Bosh DNS is now built with Go 1.15. This version of Go demands that TLS certificates be created with a SAN field, in addition to the usual CN field.

The following certificates are affected by this change and will need to be regenerated:

/dns_healthcheck_server_tls
/dns_healthcheck_client_tls
/dns_api_server_tls
/dns_api_client_tls

If you're using Credhub or another external variable store, then you will need to use update_mode: converge as documented here: https://bosh.io/docs/manifest-v2/#variables.
If you are not using Credhub or another external variable store, then you will need to follow the usual procedure for regenerating your certificates.

Jammy stemcells

We deploy using Jammy stemcells; however, if you would prefer to use the Bionic stemcells, append the ops files [IAAS]/use-bionic.yml and misc/source-releases/bosh.yml after the ops file [IAAS]/cpi.yml.

How is bosh-deployment updated?

An automatic process updates Bosh, and other releases within bosh-deployment

A new release of bosh is created.
A CI pipeline updates bosh-deployment on develop with a compiled bosh release.
Smoke tests are performed to ensure create-env works with this potential collection of resources and the new release.
A commit to master is made.

Other releases such as UAA, CredHub, and various CPIs are also updated automatically.

Using bosh-deployment

Create an environment
Access your BOSH director
- Through a VPN
  - bosh create-env, OpenVPN option
- Through a jumpbox
  - bosh create-env option
- Expose Director on a Public IP (not recommended)
CLI v2

Ops files

See tests/run-checks.sh for example usage of different ops files.

Runtime Config Files

The director can optionally add configuration to all VMs in all deployments. The YAML defines an IaaS agnostic configuration that applies to all deployments. (See Director Runtime Config.)

dns.yml: Install bosh defined dns release in every deployed VM. This allows bosh VMs to use the VM name as a FQDN. It is extremely common for deployments require this addon. (eg concourse-ci with UAA). For more information see Native DNS Support.
bpm.yml: Install bosh process manager on every VM (see BPM-Release)
syslog.yml: Install a syslog forwarder agent in every VM.

Runtime config files are applied after bosh director has been deployed:

bosh -n -e bosh-1 update-runtime-config bosh-deployment/runtime-configs/dns.yml

See runtime-configs/ for examples of different runtime configs. Other uses include installation of prometheus exporters, os-conf (to modify os level configurations), virus scanning, compliance agents.

Security Groups

Please ensure you have security groups setup correctly. i.e:

Type                 Protocol Port Range  Source                     Purpose
Custom TCP Rule      TCP      6868        <IP you run bosh CLI from> Agent for bootstrapping
Custom TCP Rule      TCP      25555       <IP you run bosh CLI from> Director API
Custom TCP Rule      TCP      8443        <IP you run bosh CLI from> UAA API (if UAA is used)
Custom TCP Rule      TCP      8844        <IP you run bosh CLI from> CredHub API (if CredHub is used)
SSH                  TCP      22          <((internal_cidr))>        BOSH SSH (optional)
Custom TCP Rule      TCP      4222        <((internal_cidr))>        NATS
Custom TCP Rule      TCP      25250       <((internal_cidr))>        Blobstore

License

cloudfoundry/bosh-deployment

ErrorLooks like something went wrong!

About

Resources

License

Security policy

Stars

Watchers

Forks

Releases

Packages 0

Contributors 119

Languages

Error
Looks like something went wrong!

Packages