cpi job from bosh-vcloud-cpi/3
Github source:
0eafea9a or
master branch
Properties¶
agent¶
blobstore¶
access_key_id¶AWS access_key_id for agent used by s3 blobstore plugin
address¶Address for agent to connect to blobstore server used by simple blobstore plugin
secret_access_key¶AWS secret_access_key for agent used by s3 blobstore plugin
mbus¶agent message bus
nats¶
address¶Address of the nats server
ntp¶List of ntp server IPs. pool.ntp.org attempts to return IPs closest to your location, but you can still specify if needed.
- Default
blobstore¶
access_key_id¶AWS access_key_id used by s3 blobstore plugin
address¶Address of blobstore server used by simple blobstore plugin
bucket_name¶AWS S3 Bucket used by s3 blobstore plugin
host¶Host of blobstore server used by simple blobstore plugin
path¶TODO
port¶Port of blobstore server used by simple blobstore plugin
- Default
provider¶Provider of the blobstore used by director and agent (dav|simple|s3)
- Default
s3_force_path_style¶Whether s3 blobstore plugin will always use path style for bucket access
- Default
s3_port¶Port of blobstore server used by s3 blobstore plugin
- Default
secret_access_key¶AWS secret_access_key used by s3 blobstore plugin
use_ssl¶Whether the simple blobstore plugin should use SSL to connect to the blobstore server
- Default
nats¶
address¶Address of the nats server
password¶Password to connect to nats with
port¶Port that the nats server listens on
- Default
user¶Username to connect to nats with
- Default
vcd¶
control¶
wait_max¶TODO
entities¶
description¶TODO
- Default
media_catalog¶TODO
media_storage_profile¶TODO
organization¶TODO
vapp_catalog¶TODO
virtual_datacenter¶TODO
vm_metadata_key¶TODO
- Default
password¶TODO
url¶TODO
user¶TODO
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/cpi/ directory
(learn more).
bin/cpi(fromcpi.erb)bin/vcloud_cpi(fromvcloud_cpi.erb)config/cpi.yml(fromcpi.yml.erb)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.