warden_cpi job from bosh-warden-cpi/45
Github source:
49a14e7
or
master branch
Properties¶
warden_cpi
¶
actions
¶
disks_dir
¶Directory where disks are stored
- Default
/var/vcap/store/warden_cpi/disks
expand_stemcell_tarball
¶Wether or not to untar stemcells, setting this to false simply gunzips it, enabling the CPI to be used with GrootFS
- Default
true
guest_ephemeral_bind_mount_path
¶Path at which ephemeral disk is mounted inside VMs
- Default
/var/vcap/data
guest_persistent_bind_mounts_dir
¶Directory with sub-directories at which persistent disks are mounted inside VMs
- Default
/warden-cpi-dev
host_ephemeral_bind_mounts_dir
¶Directory with sub-directories at which ephemeral disks are mounted on the host
- Default
/var/vcap/store/warden_cpi/ephemeral_bind_mounts_dir
host_persistent_bind_mounts_dir
¶Directory with sub-directories at which persistent disks are mounted on the host
- Default
/var/vcap/store/warden_cpi/persistent_bind_mounts_dir
stemcells_dir
¶Directory where stemcells are stored
- Default
/var/vcap/store/warden_cpi/stemcells
agent
¶
blobstore
¶
options
¶Options for the blobstore used by deployed BOSH agents
- Default
{}
provider
¶Provider type for the blobstore used by deployed BOSH agents (e.g. dav, s3)
- Default
dav
mbus
¶Mbus URL used by deployed BOSH agents
- Example
nats://nats:[email protected]:4222
ntp
¶NTP configuration used by deployed BOSH agents
- Default
[]
host_ip
¶IP address of the host that will be used by containers, must be the same as mbus IP
- Example
10.254.50.4
loopback_range
¶Range of loopback devices that will be used by the CPI for mounting persistent disks (example shows /dev/loop100 to /dev/loop130)
- Example
- 100 - 130
no_masq_cidrs
¶Do not masquerade NAT traffic internally. Related: https://github.com/cloudfoundry/bosh-lite/pull/364
- Default
- 10.244.0.0/16
warden
¶
connect_address
¶Address warden client will use to connect (ip:port or sock path)
connect_network
¶Connection type warden client will use to connect (tcp or unix)
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/warden_cpi/
directory
(learn more).
bin/cpi
(fromcpi.erb
)bin/cpi_ctl
(fromcpi_ctl.erb
)config/cpi.json
(fromcpi.json.erb
)config/sudoers
(fromsudoers
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.