google_cpi job from bosh-google-cpi/49.0.11
              Github source:
              8ebedfa4 or
              master branch
            
Properties¶
agent¶
  
  
    
mbus¶Mbus URL used by deployed BOSH agents
env¶
  
  
    
http_proxy¶HTTP proxy to connect to cloud API’s
https_proxy¶HTTPS proxy to connect to cloud API’s
no_proxy¶No proxy environment variable
google¶
  
  
    
default_root_disk_size_gb¶The default size (in Gb) of the instances root disk
- Default
0
default_root_disk_type¶The name of the default Google Compute Engine Disk Type the CPI will use when creating the instances root disk
- Default
""
json_key¶Google Compute Engine JSON key
- Default
""
project¶Google Compute Engine project
user_agent_prefix¶User Agent Prefix
- Default
""
ntp¶
  
    
      List of ntp server IPs
- Default
- - 169.254.169.254 
registry¶
  
  
    
client¶
tls¶
cacert¶Registry Client Root CA certificates (PEM format)
cert¶Registry Client Certificate (PEM format)
insecure_skip_verify¶Skip Registry server’s certificate chain and host name verification
- Default
true
key¶Registry Client Key (PEM format)
host¶Registry Hostname
password¶Registry Password
- Default
admin
port¶Registry Port
- Default
25777
protocol¶Registry Protocol (http|https)
- Default
http
use_gce_metadata¶Google Compute Engine metadata should be used instead of BOSH registry
- Default
true
username¶Registry Username
- Default
admin
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/google_cpi/ directory
            (learn more).
          
- bin/cpi(from- bin/cpi.erb)
- bin/pre-start(from- bin/pre-start.erb)
- config/cpi.json(from- config/cpi.json.erb)
- config/registry.cacertfile(from- config/registry.cacertfile.erb)
- config/registry.certfile(from- config/registry.certfile.erb)
- config/registry.keyfile(from- config/registry.keyfile.erb)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.