cloudfoundry / bosh Goto Github PK

Cloud Foundry BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services.

Home Page: https://bosh.io

License: Apache License 2.0

Ruby 96.58% Shell 1.75% HTML 0.77% HCL 0.17% Go 0.61% Dockerfile 0.11% Vim Script 0.01%

bosh's Introduction

BOSH

Cloud Foundry BOSH is an open source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems.

This repository is a Bosh Release, providing the necessary binaries and configuration templates for deploying a new Bosh Director instance, as instructed by some Bosh deployment manifest, to be applied by some Bosh CLI invocation or a pre-existing Bosh Director instance.

Quick start

Bosh is deployed by Bosh, and in order to bootstrap a new Bosh server from scratch, the Bosh CLI acts as a lightweight Bosh server with the bosh create-env command. Please refer to this Quick Start installation guide for more details.

Contributions

Please read the contributors' guide

bosh's People

Contributors

Stargazers

Watchers

Forkers

pharkmillups raphael stefanschneider vishvananda littleidea remotesyssupport dougm ibolotin nimbusrepo dkavanagh activeby xin-e-liu orsonkent dsqmoore pmenglund sravangoud mao vishalpathikgupta wsp jumping murraju junk16 hemantk mindpool alonbecker ankitgoel1987 xiaoping gigfork chnghia xuf mouse3150 alansynbot skopp zhanganha skaar txworking mkocher rajdeepd anfernee zhoudengpeng abic kaiy21 vmware-archive hfeeki windops joeljackson bluesalt ybshen rkoster lvxb pandata yudai apurvamayank liyi-at-gz fungibleclouds jeevanullas bluespace9214 rohitrshephertz animeshsingh cloudcredo dleidisch-a9s lloydchang kshtzsharma48 jbayer iceflow slantview mybesthd jclendennen vito appliedcode borovsky wuy23 hanleo mdub asherbond rpetri sfrek lisbakke brandon-adams dingyin seansweda leonplaying mstine hiremaga hgadgil gary2015 running2 mrlee1912 mykook championl zju-sel cloudfoundryv2 jesseproudman blueboxgroup madetech drogus d cfibmers kkbankol-ibm grenzr

bosh's Issues

No dns on Openstack

Context: When deploying a bosh with micro bosh. With the micro stemcell and the normal one build from master 1.5.0.pre.3 (release:bb6796a6 bosh:bb6796a6).

Problem: While deploying the director won't start.

bosh logs director 0
head migrate.stderr.log

/var/vcap/packages/director/gem_home/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:208:in `initialize': 
PG::Error: could not translate host name "0.postgres.default.bosh.microbosh" to address: Name or service not known (Sequel::DatabaseConnectionError)
    from /var/vcap/packages/director/gem_home/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:208:in `new'
    from /var/vcap/packages/director/gem_home/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:208:in `connect'
    from /var/vcap/packages/director/gem_home/gems/sequel-3.43.0/lib/sequel/connection_pool.rb:94:in `make_new'

Properties in spec file are lost when collocating jobs

I just tried to collocate cloud_controller_ng with another job (in my case I was collocating with NATS but that doesn't matter). When deploying ccng, Bosh errored out saying it couldn't find the property 'ccng.resource_pool.minimum_size'. Removing the collocated job from the equation fixed the problem.

After doing some additional tests, it became clear that properties declared in the job's spec file get lost whenever jobs are collocated.

bosh micro AWS/VPC does not survive a power-off/power-on

Yesterday I deployed a new micro BOSH with git build gems ....

(last commit 8600696)

... to Amazon EC2 VPC, using ami-874c4af3

This worked, and happily accepted a stemcell+release upload, but is broken this morning when freshly powered up.

bosh "current" log on the system reports.

2013-03-22_09:33:42.61890 #[4226] INFO: Starting agent 0.6.4...
2013-03-22_09:33:42.61901 #[4226] INFO: Configuring agent...
2013-03-22_09:33:42.62622 #[4226] INFO: Configuring instance
2013-03-22_09:33:42.66613 /var/vcap/bosh/agent/lib/agent/infrastructure/aws/registry.rb:70:in rescue in get_json_from_url': Error requesting registry information #<Errno::ECONNREFUSED: Connection refused - connect(2) (http://localhost:25888)> (RuntimeError) 2013-03-22_09:33:42.66617 from /var/vcap/bosh/agent/lib/agent/infrastructure/aws/registry.rb:43:inget_json_from_url'
2013-03-22_09:33:42.66617 from /var/vcap/bosh/agent/lib/agent/infrastructure/aws/registry.rb:91:in get_settings' 2013-03-22_09:33:42.66618 from /var/vcap/bosh/agent/lib/agent/infrastructure/aws/settings.rb:33:inload_settings'
2013-03-22_09:33:42.66619 from /var/vcap/bosh/agent/lib/agent/infrastructure/aws.rb:10:in load_settings' 2013-03-22_09:33:42.66620 from /var/vcap/bosh/agent/lib/agent/bootstrap.rb:60:inload_settings'
2013-03-22_09:33:42.66621 from /var/vcap/bosh/agent/lib/agent/bootstrap.rb:34:in configure' 2013-03-22_09:33:42.66621 from /var/vcap/bosh/agent/lib/agent.rb:93:instart'
2013-03-22_09:33:42.66622 from /var/vcap/bosh/agent/lib/agent.rb:72:in run' 2013-03-22_09:33:42.66623 from /var/vcap/bosh/agent/bin/agent:97:in

According to the AWS UI, it has two disks available - sda and sdf, but neither seem mounted. So I guess it's missing a lot of what it needs to run.

Nothing seems to be listening on ports 25888 and 6868

I attempted a bosh micro deploy ami-874c4af3 --update to recover it, but got the following error.

Updating micro BOSH instance test-amazon/micro_bosh.yml' toUnknown Director' (type 'yes' to continue): yes
WARNING: Sinatra 1.2.x has reached its EOL. Please upgrade.

Prepare for update
stopping agent services (00:00:00)
Unmount disk |oooo | 1/5 00:00:00 ETA: 00:00:00/usr/local/lib64/ruby/gems/1.9.1/gems/agent_client-1.5.0.pre.3/lib/agent_client/http_client.rb:44:in rescue in request': Request details: (Bosh::Agent::Error) uri: http://vcap:[email protected]:6868/agent payload: {"method":"list_disk","arguments":[],"reply_to":"bm-857f9fe5-8293-47c7-9b10-276c2ef8b2bd"} user: vcap password: b00tstrap Errno::ECONNREFUSED: Connection refused - connect(2) (http://x.x.x.x:6868) from /usr/local/lib64/ruby/gems/1.9.1/gems/agent_client-1.5.0.pre.3/lib/agent_client/http_client.rb:27:inrequest'
from /usr/local/lib64/ruby/gems/1.9.1/gems/agent_client-1.5.0.pre.3/lib/agent_client/http_client.rb:53:in post_json' from /usr/local/lib64/ruby/gems/1.9.1/gems/agent_client-1.5.0.pre.3/lib/agent_client/http_client.rb:21:inhandle_method'
from /usr/local/lib64/ruby/gems/1.9.1/gems/agent_client-1.5.0.pre.3/lib/agent_client/base.rb:17:in method_missing' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:258:indisk_info'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:241:in block in unmount_disk' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:84:instep'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:240:in unmount_disk' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:301:indetach_disk'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:177:in update' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:110:inblock in update_deployment'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:97:in with_lifecycle' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/deployer/instance_manager.rb:109:inupdate_deployment'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre.3/lib/bosh/cli/commands/micro.rb:171:in perform' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.3/lib/cli/command_handler.rb:57:inrun'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.3/lib/cli/runner.rb:59:in run' from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.3/lib/cli/runner.rb:18:inrun'
from /usr/local/lib64/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.3/bin/bosh:7:in <top (required)>' from /usr/local/bin/bosh:23:inload'
from /usr/local/bin/bosh:23:in `

I'm happy to let you have SSH access to the broken instance to debug if you wish.

regards

James M

Bosh deployer error with vSphere CPI

Got this error when deployed a micro bosh on vSphere:

...
Updating persistent disk            |oooooooo                | 4/11 00:02:15  ETA: 00:03:55at depth   mount disk (00:00:07)                                                                             
Stopping agent services             |oooooooooo              | 5/11 00:02:32  ETA: 00:02:39/home/stefans/.rvm/gems/ruby-1.9.3-p392/gems/bosh_deployer-1.5.0.pre2/lib/deployer/specification.rb:89:in `update_agent_service_address': undefined method `[]' for nil:NilClass (NoMethodError)
    from /home/stefans/.rvm/gems/ruby-1.9.3-p392/gems/bosh_deployer-1.5.0.pre2/lib/deployer/specification.rb:41:in `block in update'
    from /home/stefans/.rvm/gems/ruby-1.9.3-p392/gems/bosh_deployer-1.5.0.pre2/lib/deployer/specification.rb:40:in `each'
...

As a workaround for this I had to add this to my micro bosh deployment manifest:

apply_spec:
  agent:
    blobstore: {}
    nats: {}

Adding the previous snippet here https://github.com/cloudfoundry/bosh/blob/master/bosh_deployer/config/vsphere_defaults.yml#L40
would be a proper fix, IMHO.
The aws default yml contains those default values. See here: https://github.com/cloudfoundry/bosh/blob/master/bosh_deployer/config/aws_defaults.yml#L51

Please advise me where to add or change a rspec test if necessary.

Thanks
Stefan

openssl error during "bosh micro deploy"'s "Waiting for the agent" stage

Raised by @orsonkent in cloudfoundry-community-attic/bosh-bootstrap#185:

$ bosh-bootstrap deploy
...
Deploy Micro BOSH
  using existing stemcell (00:00:00)
  creating VM from ami-345ac05d (00:00:41)
Waiting for the agent        |ooo                | 2/11 00:07:43  ETA: --:--:--/usr/local/rvm/gems/ruby-1.9.3-p392/gems/agent_client-1.5.0.pre.480/lib/agent_client/http_client.rb:46:in `rescue in request': Request details: (Bosh::Agent::Error)
uri: https://vcap:[email protected]:6868/agent
payload: {"method":"ping","arguments":[],"reply_to":"bm-6ff7a111-2d55-4f62-af14-907921e6aa01"}
user: vcap
password: b00tstrap
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/agent_client-1.5.0.pre.480/lib/agent_client/http_client.rb:27:in `request'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/agent_client-1.5.0.pre.480/lib/agent_client/http_client.rb:55:in `post_json'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/agent_client-1.5.0.pre.480/lib/agent_client/http_client.rb:21:in `handle_method'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/agent_client-1.5.0.pre.480/lib/agent_client/base.rb:17:in `method_missing'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:419:in `block in wait_until_agent_ready'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:405:in `block in wait_until_ready'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_common-1.5.0.pre.480/lib/common/common.rb:65:in `block in retryable'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_common-1.5.0.pre.480/lib/common/common.rb:64:in `loop'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_common-1.5.0.pre.480/lib/common/common.rb:64:in `retryable'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:402:in `wait_until_ready'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:419:in `wait_until_agent_ready'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:140:in `block in create'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:84:in `step'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:139:in `create'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:104:in `block in create_deployment'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:97:in `with_lifecycle'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/deployer/instance_manager.rb:103:in `create_deployment'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli_plugin_micro-1.5.0.pre.480/lib/bosh/cli/commands/micro.rb:171:in `perform'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.480/lib/cli/command_handler.rb:57:in `run'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.480/lib/cli/runner.rb:59:in `run'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.480/lib/cli/runner.rb:18:in `run'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.480/bin/bosh:7:in `<top (required)>'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/bosh:19:in `load'
    from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/bosh:19:in `<main>'
    from /usr/local/rvm/gems/ruby-1.9.3-p392@global/bin/ruby_noexec_wrapper:14:in `eval'
    from /usr/local/rvm/gems/ruby-1.9.3-p392@global/bin/ruby_noexec_wrapper:14:in `<main>'
Last line of script:    from /usr/local/rvm/gems/ruby-1.9.3-p392@global/bin/ruby_noexec_wrapper:14:in `<main>'
       error  deploy micro bosh
Failed to complete Stage 7: Deploying micro BOSH

Micro bosh NTP.

NTP is not configured for a micro bosh deployment. Issue is most probably here:
https://github.com/cloudfoundry/bosh/blob/master/bosh_deployer/lib/deployer/specification.rb#L57

p('agent.ntp') is not used in director.yml.erb. Maybe the intent was to set p('ntp') used by the director here:
https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/templates/director.yml.erb#L184

Please confirm that the issue is there and tell me how to make a rspec test for the fix.

Thanks.

stemcell builder does not clean up /var/tmp/bosh

After builds it should delete what it creates in /var/tmp/bosh.

bosh ssh with no arguments gives traceback instead of usage message

bosh ssh
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/lib/cli/commands/ssh.rb:213:in parse_args': undefined methodsplit' for nil:NilClass (NoMethodError)
from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/lib/cli/commands/ssh.rb:20:in shell' from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/lib/cli/command_handler.rb:57:inrun'
from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/lib/cli/runner.rb:61:in run' from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/lib/cli/runner.rb:18:inrun'
from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/gems/bosh_cli-1.0.3/bin/bosh:16:in <top (required)>' from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/bin/bosh:23:inload'
from /Users/pivotal/.rvm/gems/ruby-1.9.3-p194/bin/bosh:23:in `

stemcell tasks - add option to use precompiled packages from another blobstore

As I sit here watching rake stemcell:mcf run for a few hours as it compiles the packages one after another from cf-release, I would wish that the micro-stemcells (mcf & microbosh) could be built from the pre-compiled packages from a target bosh.

MIcro BOSH - Uploading Stemcell error

I created the stemcell. Now trying to deploy micro bosh but I am getting the error
[16:23:42] Pradeep Tummala: root@inception-vm:/home/ubuntu/deployments# bosh micro deploy /home/ubuntu/stemcells/micro-bosh-stemcell-openstack-kvm-0.8.1.tgz
Deploying new micro BOSH instance microbosh-openstack/micro_bosh.yml' tohttp://microbosh-openstack:25555' (type 'yes' to continue): yes

Verifying stemcell...
File exists and readable OK
Manifest not found in cache, verifying tarball...
Extract tarball OK
Manifest exists OK
Stemcell image file OK
Writing manifest to cache...
Stemcell properties OK

Stemcell info

Name: micro-bosh-stemcell
Version: 0.8.1

Deploy Micro BOSH
unpacking stemcell (00:00:04)
Uploading stemcell |oo | 1/11 00:00:30 ETA: 00:00:21/usr/local/rvm/gems/ruby-1.9.2-p320/gems/excon-0.16.10/lib/excon/connection.rb:292:in request_kernel': Expected(201) <=> Actual(300 Multiple Choices) (Excon::Errors::MultipleChoices) request => {:chunk_size=>1048576, :connect_timeout=>60, :headers=>{"User-Agent"=>"fog/1.9.0", "Content-Type"=>"application/octet-stream", "X-Auth-Token"=>"MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCTAHBgUrDgMCGjCCCRwGCSqGSIb3DQEHAaCCCQ0EggkJeyJhY2Nlc3MiOiB7InRva2VuIjogeyJpc3N1ZWRfYXQiOiAiMjAxMy0wMi0xMVQxMDozNzo1Mi4xNzk2NjciLCAiZXhwaXJlcyI6ICIyMDEzLTAyLTEyVDEwOjM3OjUyWiIsICJpZCI6ICJwbGFjZWhvbGRlciIsICJ0ZW5hbnQiOiB7ImVuYWJsZWQiOiB0cnVlLCAiZGVzY3JpcHRpb24iOiBudWxsLCAibmFtZSI6ICJib3NoIiwgImlkIjogIjAzZDIyNDdjNGI4ODQ4ZTRiNGYyNjM2N2RmNDkyYTczIn19LCAic2VydmljZUNhdGFsb2ciOiBbeyJlbmRwb2ludHMiOiBbeyJhZG1pblVSTCI6ICJodHRwOi8vMTkyLjE2OC4xLjI6ODc3NC92Mi8wM2QyMjQ3YzRiODg0OGU0YjRmMjYzNjdkZjQ5MmE3MyIsICJyZWdpb24iOiAiUmVnaW9uT25lIiwgImludGVybmFsVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo4Nzc0L3YyLzAzZDIyNDdjNGI4ODQ4ZTRiNGYyNjM2N2RmNDkyYTczIiwgImlkIjogIjlkNWE2MmI5ZDYxZjRiNzRiN2JlOGJiZjIyYTZhZGZmIiwgInB1YmxpY1VSTCI6ICJodHRwOi8vMTkyLjE2OC4xLjI6ODc3NC92Mi8wM2QyMjQ3YzRiODg0OGU0YjRmMjYzNjdkZjQ5MmE3MyJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJjb21wdXRlIiwgIm5hbWUiOiAibm92YSJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjozMzMzIiwgInJlZ2lvbiI6ICJSZWdpb25PbmUiLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzE5Mi4xNjguMS4yOjMzMzMiLCAiaWQiOiAiM2I5N2YxNTdjNDM3NGZlNThlMjhlZDQ4Y2MwYTI0NzgiLCAicHVibGljVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjozMzMzIn1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogInMzIiwgIm5hbWUiOiAiczMifSwgeyJlbmRwb2ludHMiOiBbeyJhZG1pblVSTCI6ICJodHRwOi8vMTkyLjE2OC4xLjI6OTI5MiIsICJyZWdpb24iOiAiUmVnaW9uT25lIiwgImludGVybmFsVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo5MjkyIiwgImlkIjogIjU5MGM5MjY4MDZhMzRiZTZiZTdlOWM2NGI5MWRlZDY2IiwgInB1YmxpY1VSTCI6ICJodHRwOi8vMTkyLjE2OC4xLjI6OTI5MiJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJpbWFnZSIsICJuYW1lIjogImdsYW5jZSJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo4Nzc2L3YxLzAzZDIyNDdjNGI4ODQ4ZTRiNGYyNjM2N2RmNDkyYTczIiwgInJlZ2lvbiI6ICJSZWdpb25PbmUiLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzE5Mi4xNjguMS4yOjg3NzYvdjEvMDNkMjI0N2M0Yjg4NDhlNGI0ZjI2MzY3ZGY0OTJhNzMiLCAiaWQiOiAiODcwNWRiNTZjNzQyNDYwNWI4MDU0MDNkZmQ0YjEzYTYiLCAicHVibGljVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo4Nzc2L3YxLzAzZDIyNDdjNGI4ODQ4ZTRiNGYyNjM2N2RmNDkyYTczIn1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogInZvbHVtZSIsICJuYW1lIjogImNpbmRlciJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo4NzczL3NlcnZpY2VzL0FkbWluIiwgInJlZ2lvbiI6ICJSZWdpb25PbmUiLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzE5Mi4xNjguMS4yOjg3NzMvc2VydmljZXMvQ2xvdWQiLCAiaWQiOiAiMWUxNDA4NWQ4MDhhNDc5NWE1OGJmYjViZGVmNmU4ZjciLCAicHVibGljVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjo4NzczL3NlcnZpY2VzL0Nsb3VkIn1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogImVjMiIsICJuYW1lIjogImVjMiJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xOTIuMTY4LjEuMjozNTM1Ny92Mi4wIiwgInJlZ2lvbiI6ICJSZWdpb25PbmUiLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzE5Mi4xNjguMS4yOjUwMDAvdjIuMCIsICJpZCI6ICIxNzE3OGFlYTUyYzI0NGRmYThiODgwOTNjZGYxN2MxZSIsICJwdWJsaWNVUkwiOiAiaHR0cDovLzE5Mi4xNjguMS4yOjUwMDAvdjIuMCJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJpZGVudGl0eSIsICJuYW1lIjogImtleXN0b25lIn1dLCAidXNlciI6IHsidXNlcm5hbWUiOiAiYm9zaCIsICJyb2xlc19saW5rcyI6IFtdLCAiaWQiOiAiZTk1NDI5Y2RiMWJlNGZjNGEzZDQxZTVjMjg5NGFhODYiLCAicm9sZXMiOiBbeyJuYW1lIjogIk1lbWJlciJ9XSwgIm5hbWUiOiAiYm9zaCJ9LCAibWV0YWRhdGEiOiB7ImlzX2FkbWluIjogMCwgInJvbGVzIjogWyI4MDNjM2ZlMmQ5MGY0MWQ2YjkxNzUyNmM5YTc0ZjM1MiJdfX19MYH-MIH8AgEBMFwwVzELMAkGA1UEBhMCVVMxDjAMBgNVBAgTBVVuc2V0MQ4wDAYDVQQHEwVVbnNldDEOMAwGA1UEChMFVW5zZXQxGDAWBgNVBAMTD3d3dy5leGFtcGxlLmNvbQIBATAHBgUrDgMCGjANBgkqhkiG9w0BAQEFAASBgDginAPSGRc9SlEn66N1C88lVkzvz7gMbGYP+Rm5f3yhrjOlmftGlXvyfh2zXbtzgEGcgAEM7iqll16GeVCi6XchNr7S66KUEH37xI92y0QcID1djiwbSFWabjEmqiw9D0aIQy5L4o-OoZG0qhfojuUvZy+gWU2qc4ZfDrvzNSTd", "x-image-meta-name"=>"BOSH-f45ed4c2-45a1-4566-b3b1-555a4e5655ab", "x-image-meta-disk-format"=>"qcow2", "x-image-meta-container-format"=>"bare", "x-image-meta-is-public"=>true, "x-image-meta-size"=>1153499136, "x-image-meta-property-\#{key}"=>"0.8.1", "Host"=>"192.168.1.2:9292", "Content-Length"=>1153499136}, :instrumentor_name=>"excon", :mock=>false, :nonblock=>true, :read_timeout=>60, :retry_limit=>4, :ssl_ca_file=>"/usr/local/rvm/gems/ruby-1.9.2-p320/gems/excon-0.16.10/data/cacert.pem", :ssl_verify_peer=>true, :write_timeout=>60, :host=>"192.168.1.2", :host_port=>"192.168.1.2:9292", :path=>"/images", :port=>"9292", :query=>nil, :scheme=>"http", :body=>#<File:/tmp/d20130211-8106-1iua74/d20130211-8106-ki9b7p/root.img>, :expects=>201, :method=>"POST"} response => #<Excon::Response:0x00000002cf8fd0 @body="{\"versions\": [{\"status\": \"CURRENT\", \"id\": \"v2.0\", \"links\": [{\"href\": \"http://192.168.1.2:9292/v2/\", \"rel\": \"self\"}]}, {\"status\": \"CURRENT\", \"id\": \"v1.1\", \"links\": [{\"href\": \"http://192.168.1.2:9292/v1/\", \"rel\": \"self\"}]}, {\"status\": \"SUPPORTED\", \"id\": \"v1.0\", \"links\": [{\"href\": \"http://192.168.1.2:9292/v1/\", \"rel\": \"self\"}]}]}", @headers={"Content-Type"=>"application/json; charset=UTF-8", "Content-Length"=>"328", "Date"=>"Mon, 11 Feb 2013 10:38:06 GMT"}, @status=300> from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/excon-0.16.10/lib/excon/connection.rb:103:inrequest'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/core/connection.rb:21:in request' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/openstack/image.rb:144:inrequest'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/openstack/requests/image/create_image.rb:39:in create_image' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/openstack/models/image/image.rb:47:increate'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/openstack/models/image/image.rb:42:in save' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/fog-1.9.0/lib/fog/core/collection.rb:52:increate'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_openstack_cpi-0.0.7/lib/cloud/openstack/cloud.rb:728:in upload_image' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_openstack_cpi-0.0.7/lib/cloud/openstack/cloud.rb:167:inblock (2 levels) in create_stemcell'
from /usr/local/rvm/rubies/ruby-1.9.2-p320/lib/ruby/1.9.1/tmpdir.rb:83:in mktmpdir' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_openstack_cpi-0.0.7/lib/cloud/openstack/cloud.rb:90:inblock in create_stemcell'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_common-0.5.5/lib/common/thread_formatter.rb:46:in with_thread_name' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_openstack_cpi-0.0.7/lib/cloud/openstack/cloud.rb:88:increate_stemcell'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:215:in block (2 levels) in create_stemcell' from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:84:instep'
from /usr/local/rvm/gems/ruby-1.9.2-p320/gems/bosh_deployer-1.4.0/lib/deployer..

Can't delete or fix failed VM

I would like a way to manually delete a VM for the following use case, or perhaps even fix it with bosh cloudcheck. I'm deploying cloudfoundry. I don't know what went wrong to get to this state, but 1 out of some number of VMs is in an unresponsive state.

You can see it has a cloud id and agent id, I also know it's there in my Openstack
A bosh deploy will yield
binding existing deployment: Timed out sending get_state' to 8d29364c-ae75-4a7f-9479-bc698d69a95a after 30 seconds (00:01:30) Error 450002: Timed out sendingget_state' to 8d29364c-ae75-4a7f-9479-bc698d69a95a after 30 seconds

bosh cloudcheck yields
Problem 1 of 1: Unknown VM (ed079483-17b1-4b9b-8f02-64ca9253b483) is not responding.

Ignore problem
Reboot VM
Recreate VM using last known apply spec
Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]:

None of 2 -4 will work.
If I delete
unresponsive_agent 182: Delete VM reference (DANGEROUS!): VM `182' has a cloud id, please use a different resolution. (00:00:10)

If I recreate
unresponsive_agent 182: Recreate VM using last known apply spec: Unable to look up VM apply spec (00:00:10)

If I reboot
unresponsive_agent 182: Reboot VM: Agent still unresponsive after reboot (00:13:42)

I can delete the deployment and try again, but out of 40 jobs in cloudfoundry, it seems inevitably that something will go wrong.

As requested, here's my info
root@ubuntu:/var/vcap/deployments# bosh status
bosUpdating director data... hdone

Director
Name microbosh-openstack
URL http://10.152.93.141:25555
Version 0.7 (release:b240cdfb bosh:57b31b3f)
User admin
UUID 213167e4-adb2-479a-880f-1c8d28814e8f
CPI openstack
dns enabled

Deployment
Manifest /var/vcap/deployments/Cloudfoundry-full.yml
root@ubuntu:/var/vcap/deployments# bosh version
BOSH 1.0.3
root@ubuntu:/var/vcap/deployments# bosh stemcells

+---------------+---------+--------------------------------------+
| Name | Version | CID |
+---------------+---------+--------------------------------------+
| bosh-stemcell | 0.6.7 | 335e6abd-e26a-48ff-9d30-0bd495fb2248 |
+---------------+---------+--------------------------------------+

Stemcells total: 1

micro bosh stemcell is 0.8.1

"bosh micro deploy" proxy support

Hi,

I seems "bosh micro deploy" doesn't work from behind a proxy? (https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/kJ6PCC1CN5A)

Could the proxy support be added? Most of the corporate users are behind firewall/proxy.

Thanks,
Steven

Can latest 1.5.0.pre2 micrbosh work with public gems?

Raised at cloudfoundry-community-attic/bosh-bootstrap#115.

I am using the latest public gems and when I try to deploy microbosh I get:

Stemcell info
-------------
Name:    micro-bosh-stemcell
Version: 1.5.0.pre2


Deploy Micro BOSH
  unpacking stemcell (00:00:15)                                                 
  uploading stemcell (00:12:42)                                                 
  creating VM from ami-f2e5779b (00:00:29)                                      
  waiting for the agent (00:01:56)                                              
  create disk (00:02:38)                                                        
  mount disk (00:00:14)                                                         
  stopping agent services (00:00:01)                                            
Applying micro BOSH spec     |oooooooooooo       | 7/11 00:18:26  ETA: 00:10:18/usr/local/lib/ruby/gems/1.9.1/gems/agent_client-0.1.1/lib/agent_client/base.rb:19:in `method_missing': {"message"=>"Failed to install job 'micro_aws.micro_aws': failed to process configuration template 'director/director.yml.erb': line 172, error: Could not find cloud plugin: [\"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:241:in `install_failed'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:126:in `rescue in block in bind_configuration'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:117:in `block in bind_configuration'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:107:in `each_pair'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:107:in `bind_configuration'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/job.rb:51:in `install'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/plan.rb:73:in `block in install_jobs'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/plan.rb:72:in `each'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/apply_plan/plan.rb:72:in `install_jobs'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:117:in `apply_job'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:77:in `apply'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:10:in `process'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:274:in `process'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:259:in `process_long_running'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:181:in `block in process_in_thread'\", \"<internal:prelude>:10:in `synchronize'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:179:in `process_in_thread'\", \"/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:160:in `block in handle_message'\"]", "backtrace"=>["/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:83:in `rescue in apply'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:75:in `apply'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/message/apply.rb:10:in `process'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:274:in `process'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:259:in `process_long_running'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:181:in `block in process_in_thread'", "<internal:prelude>:10:in `synchronize'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:179:in `process_in_thread'", "/var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/handler.rb:160:in `block in handle_message'"]} (Bosh::Agent::HandlerError)

What does failed to process configuration template 'director/director.yml.erb': line 172, error: Could not find cloud plugin mean? Did the micro_bosh.yml schema change? Does this stemcell only work with bosh_deployer built from master/HEAD?

Problem with DRS enabled on cluster on vSphere

When deploying micro Bosh to vSphere and cluster has DRS feature turned on I get an error:

Verifying stemcell...
File exists and readable                                     OK
Using cached manifest...
Stemcell properties                                          OK

Stemcell info
-------------
Name:    bosh-stemcell
Version: 0.5.1


Deploy Micro BOSH
  unpacking stemcell (00:00:19)                                                 
  uploading stemcell (00:02:39)                                                 
Delete stemcell              |ooo                | 2/11 00:10:56  ETA: 00:05:26BOSH CLI Error: undefined method `task' for nil:NilClass

and ~/.bosh_error contains:

~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.4.8/lib/cloud/vsphere/client.rb:159:in `power_on_vm'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.4.8/lib/cloud/vsphere/cloud.rb:228:in `block in create_vm'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_common-0.4.0/lib/common/thread_formatter.rb:46:in `with_thread_name'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.4.8/lib/cloud/vsphere/cloud.rb:149:in `create_vm'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:215:in `create_vm'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:136:in `block in create'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:84:in `step'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:135:in `create'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:104:in `block in create_deployment'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:97:in `with_lifecycle'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/deployer/instance_manager.rb:103:in `create_deployment'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_deployer-0.2.2/lib/bosh/cli/commands/micro.rb:131:in `perform'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_cli-0.19.4/lib/cli/runner.rb:69:in `run'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_cli-0.19.4/lib/cli/runner.rb:24:in `run'
~/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/bosh_cli-0.19.4/bin/bosh:16:in `<top (required)>'
~/.rbenv/versions/1.9.2-p290/bin/bosh:23:in `load'
~/.rbenv/versions/1.9.2-p290/bin/bosh:23:in `<main>'

rake stemcell:micro failing - cp: cannot stat `/tmp/all_the_gems/rack-protection-*.gem'

$ rake stemcell:micro[...]
rm -f pkg/agent_client-1.5.0.pre.gem
mkdir -p pkg
cd agent_client && gem build agent_client.gemspec && mv agent_client-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: agent_client
  Version: 1.5.0.pre
  File: agent_client-1.5.0.pre.gem
rm -f pkg/bosh_aws_bootstrap-1.5.0.pre.gem
cd bosh_aws_bootstrap && gem build bosh_aws_bootstrap.gemspec && mv bosh_aws_bootstrap-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_aws_bootstrap
  Version: 1.5.0.pre
  File: bosh_aws_bootstrap-1.5.0.pre.gem
rm -f pkg/bosh_aws_cpi-1.5.0.pre.gem
cd bosh_aws_cpi && gem build bosh_aws_cpi.gemspec && mv bosh_aws_cpi-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_aws_cpi
  Version: 1.5.0.pre
  File: bosh_aws_cpi-1.5.0.pre.gem
rm -f pkg/bosh_aws_registry-1.5.0.pre.gem
cd bosh_aws_registry && gem build bosh_aws_registry.gemspec && mv bosh_aws_registry-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_aws_registry
  Version: 1.5.0.pre
  File: bosh_aws_registry-1.5.0.pre.gem
rm -f pkg/blobstore_client-1.5.0.pre.gem
cd blobstore_client && gem build blobstore_client.gemspec && mv blobstore_client-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  no description specified
  Successfully built RubyGem
  Name: blobstore_client
  Version: 1.5.0.pre
  File: blobstore_client-1.5.0.pre.gem
rm -f pkg/bosh_agent-1.5.0.pre.gem
cd bosh_agent && gem build bosh_agent.gemspec && mv bosh_agent-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
  Successfully built RubyGem
  Name: bosh_agent
  Version: 1.5.0.pre
  File: bosh_agent-1.5.0.pre.gem
rm -f pkg/bosh_cli-1.5.0.pre.gem
cd bosh_cli && gem build bosh_cli.gemspec && mv bosh_cli-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
  Successfully built RubyGem
  Name: bosh_cli
  Version: 1.5.0.pre
  File: bosh_cli-1.5.0.pre.gem
rm -f pkg/bosh_common-1.5.0.pre.gem
cd bosh_common && gem build bosh_common.gemspec && mv bosh_common-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_common
  Version: 1.5.0.pre
  File: bosh_common-1.5.0.pre.gem
rm -f pkg/bosh_cpi-1.5.0.pre.gem
cd bosh_cpi && gem build bosh_cpi.gemspec && mv bosh_cpi-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_cpi
  Version: 1.5.0.pre
  File: bosh_cpi-1.5.0.pre.gem
rm -f pkg/bosh_deployer-1.5.0.pre.gem
cd bosh_deployer && gem build bosh_deployer.gemspec && mv bosh_deployer-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_deployer
  Version: 1.5.0.pre
  File: bosh_deployer-1.5.0.pre.gem
rm -f pkg/director-1.5.0.pre.gem
cd director && gem build director.gemspec && mv director-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: director
  Version: 1.5.0.pre
  File: director-1.5.0.pre.gem
rm -f pkg/bosh_encryption-1.5.0.pre.gem
cd bosh_encryption && gem build bosh_encryption.gemspec && mv bosh_encryption-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_encryption
  Version: 1.5.0.pre
  File: bosh_encryption-1.5.0.pre.gem
rm -f pkg/health_monitor-1.5.0.pre.gem
cd health_monitor && gem build health_monitor.gemspec && mv health_monitor-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: health_monitor
  Version: 1.5.0.pre
  File: health_monitor-1.5.0.pre.gem
rm -f pkg/monit_api-1.5.0.pre.gem
cd monit_api && gem build monit_api.gemspec && mv monit_api-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: monit_api
  Version: 1.5.0.pre
  File: monit_api-1.5.0.pre.gem
rm -f pkg/bosh_openstack_registry-1.5.0.pre.gem
cd bosh_openstack_registry && gem build bosh_openstack_registry.gemspec && mv bosh_openstack_registry-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_openstack_registry
  Version: 1.5.0.pre
  File: bosh_openstack_registry-1.5.0.pre.gem
rm -f pkg/package_compiler-1.5.0.pre.gem
cd package_compiler && gem build package_compiler.gemspec && mv package_compiler-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: package_compiler
  Version: 1.5.0.pre
  File: package_compiler-1.5.0.pre.gem
rm -f pkg/ruby_vcloud_sdk-1.5.0.pre.gem
cd ruby_vcloud_sdk && gem build ruby_vcloud_sdk.gemspec && mv ruby_vcloud_sdk-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: ruby_vcloud_sdk
  Version: 1.5.0.pre
  File: ruby_vcloud_sdk-1.5.0.pre.gem
rm -f pkg/ruby_vim_sdk-1.5.0.pre.gem
cd ruby_vim_sdk && gem build ruby_vim_sdk.gemspec && mv ruby_vim_sdk-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: ruby_vim_sdk
  Version: 1.5.0.pre
  File: ruby_vim_sdk-1.5.0.pre.gem
rm -f pkg/simple_blobstore_server-1.5.0.pre.gem
cd simple_blobstore_server && gem build simple_blobstore_server.gemspec && mv simple_blobstore_server-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: simple_blobstore_server
  Version: 1.5.0.pre
  File: simple_blobstore_server-1.5.0.pre.gem
rm -f pkg/bosh_vcloud_cpi-1.5.0.pre.gem
cd bosh_vcloud_cpi && gem build bosh_vcloud_cpi.gemspec && mv bosh_vcloud_cpi-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_vcloud_cpi
  Version: 1.5.0.pre
  File: bosh_vcloud_cpi-1.5.0.pre.gem
rm -f pkg/bosh_vsphere_cpi-1.5.0.pre.gem
cd bosh_vsphere_cpi && gem build bosh_vsphere_cpi.gemspec && mv bosh_vsphere_cpi-1.5.0.pre.gem /var/vcap/store/repos/bosh/pkg/
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: bosh_vsphere_cpi
  Version: 1.5.0.pre
  File: bosh_vsphere_cpi-1.5.0.pre.gem
rm -rf /tmp/all_the_gems
mkdir -p /tmp/all_the_gems
cp /var/vcap/store/repos/bosh/pkg/*.gem /tmp/all_the_gems
cp /var/vcap/store/repos/bosh/vendor/cache/*.gem /tmp/all_the_gems
rm -rf /var/vcap/store/repos/bosh/release/src/bosh/agent_client
mkdir -p /var/vcap/store/repos/bosh/release/src/bosh/agent_client
cp /tmp/all_the_gems/httpclient-*.gem .
cp /tmp/all_the_gems/yajl-ruby-*.gem .
cp /tmp/all_the_gems/agent_client-*.gem .
rm -rf /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_bootstrap
mkdir -p /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_bootstrap
cp /tmp/all_the_gems/multi_json-*.gem .
cp /tmp/all_the_gems/multi_xml-*.gem .
cp /tmp/all_the_gems/httparty-*.gem .
cp /tmp/all_the_gems/json-*.gem .
cp /tmp/all_the_gems/nokogiri-*.gem .
cp /tmp/all_the_gems/uuidtools-*.gem .
cp /tmp/all_the_gems/aws-sdk-*.gem .
cp /tmp/all_the_gems/bosh_common-*.gem .
cp /tmp/all_the_gems/builder-*.gem .
cp /tmp/all_the_gems/excon-*.gem .
cp /tmp/all_the_gems/formatador-*.gem .
cp /tmp/all_the_gems/mime-types-*.gem .
cp /tmp/all_the_gems/net-ssh-*.gem .
cp /tmp/all_the_gems/net-scp-*.gem .
cp /tmp/all_the_gems/ruby-hmac-*.gem .
cp /tmp/all_the_gems/fog-*.gem .
cp /tmp/all_the_gems/httpclient-*.gem .
cp /tmp/all_the_gems/log4r-*.gem .
cp /tmp/all_the_gems/ruby-atmos-pure-*.gem .
cp /tmp/all_the_gems/blobstore_client-*.gem .
cp /tmp/all_the_gems/highline-*.gem .
cp /tmp/all_the_gems/json_pure-*.gem .
cp /tmp/all_the_gems/net-ssh-gateway-*.gem .
cp /tmp/all_the_gems/netaddr-*.gem .
cp /tmp/all_the_gems/progressbar-*.gem .
cp /tmp/all_the_gems/terminal-table-*.gem .
cp /tmp/all_the_gems/bosh_cli-*.gem .
cp /tmp/all_the_gems/bosh_aws_bootstrap-*.gem .
rm -rf /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_cpi
mkdir -p /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_cpi
cp /tmp/all_the_gems/multi_json-*.gem .
cp /tmp/all_the_gems/multi_xml-*.gem .
cp /tmp/all_the_gems/httparty-*.gem .
cp /tmp/all_the_gems/json-*.gem .
cp /tmp/all_the_gems/nokogiri-*.gem .
cp /tmp/all_the_gems/uuidtools-*.gem .
cp /tmp/all_the_gems/aws-sdk-*.gem .
cp /tmp/all_the_gems/bosh_common-*.gem .
cp /tmp/all_the_gems/bosh_cpi-*.gem .
cp /tmp/all_the_gems/httpclient-*.gem .
cp /tmp/all_the_gems/yajl-ruby-*.gem .
cp /tmp/all_the_gems/bosh_aws_cpi-*.gem .
rm -rf /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_registry
mkdir -p /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_registry
cp /tmp/all_the_gems/multi_json-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/multi_xml-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/httparty-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/json-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/nokogiri-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/uuidtools-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/aws-sdk-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/sequel-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/rack-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/rack-protection-*.gem .
cp: cannot stat `/tmp/all_the_gems/rack-protection-*.gem': No such file or directory
rake aborted!
Command failed with status (1): [cp /tmp/all_the_gems/rack-protection-*.gem...]
/var/vcap/store/repos/bosh/rake/gem.rake:52:in `block (5 levels) in <top (required)>'
/var/vcap/store/repos/bosh/rake/gem.rake:48:in `block (4 levels) in <top (required)>'
/var/vcap/store/repos/bosh/rake/gem.rake:47:in `chdir'
/var/vcap/store/repos/bosh/rake/gem.rake:47:in `block (3 levels) in <top (required)>'
Tasks: TOP => stemcell:micro => all:build_with_deps => bosh_aws_registry:build_with_deps => bosh_aws_registry:gem_with_deps
(See full trace by running task with --trace)

Request limit exceeded when compiling

When compiling with BOSH i get request limit exceeded on AWS using region eu-west-1 . I think BOSH should throttle and recover? Reducing to 4 nodes for compilation fixes.

Compiling packages
  dea_node08/1: Request limit exceeded. (00:00:02)                                                  
  sqlite/3: Request limit exceeded. (00:00:03)                                                      
  syslog_aggregator/3: Request limit exceeded. (00:00:05)                                           
  insight_agent/2: Request limit exceeded. (00:00:06)                                               
  nginx/9: Request limit exceeded. (00:00:06)                                                       
  dea_jvm7/1: Request limit exceeded. (00:00:09)                                                    
  dea_ruby18/8: Request limit exceeded. (00:00:12)                                                  
  libpq/4.1-dev: Request limit exceeded. (00:00:20)                                                 
  mysqlclient/3 (00:03:11)                                                                          
  dea_ruby19/7 (00:07:36)                                                                           
Error                   10/24 00:07:36                                                              

Error 100: Request limit exceeded.

Running this on Stark and Waynes bosh-cloudfoundry. https://github.com/StarkAndWayne/bosh-cloudfoundry

Is it a dead lock or my mistake ? about bosh_cli_pluin_micro and bosh_agent

I ran into some issues when I try to deploy microbosh (If I want deploy BOSH microbosh is needed isn't it ?), the issue detail is https://groups.google.com/a/cloudfoundry.org/forum/?fromgroups=#!topic/bosh-users/o7Zsi1RIgTo . and the related gem list is
bosh_cli (1.0.4)
bosh_common (0.5.4)
bosh_cpi (0.5.1)
bosh_deployer (1.4.0)
bosh_openstack_cpi (0.0.7)
bosh_openstack_registry (0.0.5)
agent_client (0.1.1)

the stemcell version is micro-bosh-stemcell-openstack-kvm-0.8.1.tgz

In Bosh::Deployer::InstanceManager#create(stemcell_tgz), the deployer will
1.create_vm 2.update_vm_metadata 3.discover_bosh_ip 4.wait_until_agent_ready 5. update_persistent_disk 6.apply 7.wait_until_director_ready
step 4,5,6 will use agent_client#http_client do ping (by agent.ping) mount_disk apply (by agent.run_task) and 7 a new HTTPclient and request "https://#{bosh_ip}:#{port}/info", and all will be dealed with "BaseClient#method_missing" and do a "handle_method", which "post_json"

but agent code :
Bosh::Agent::Bootstrap.new.configure
Bosh::Agent::Monit.enable+start+start_service
and then check mbus start HTTPHandler or Handler.
and in Bosh::Agent::Bootstrap.new.configure
...
48.setup_data_disk
49.setup_tmp
...

and there will be a deadlock, the agent keep waiting for deployer attach a volume for it (step5),but deployer keep waitting agent ready (step 4) by request http://ip:6868 which will start handle after all agent instance configure done.

Is the code work as I describe above ? The dead lock seems so easy to find out, so I guess I missed something somewhere.
And if it is a dead lock issue, I'm glad to create a pull request in github

BOSH-specific docs should be more visible.

This tool looks great, but I had trouble finding the BOSH-specific docs [1] . You should put a pointer to these and at least some sort of mention of what BOSH actually is at the top of the README. It might also be a good idea to inclue a copy of the docs in the BOSH repo so that I can clone this and use it on a train with no wifi.

[1] https://github.com/cloudfoundry/oss-docs/blob/master/bosh/documentation/documentation.md

Cannot create stemcell nor view rake tasks

$ bundle exec rake -T
rake aborted!
cannot load such file -- rspec
/var/vcap/store/repos/bosh/rake/bat.rake:2:in `require'
/var/vcap/store/repos/bosh/rake/bat.rake:2:in `<top (required)>'
(See full trace by running task with --trace)

This is as of commit cd73f7d

bosh_aws_bootstrap failed: vpc.rb:80:in `block in create_security_groups': undefined method `for_sgroup' for Bosh::AwsCloud::ResourceWait:Class

Following the new VPC tutorial, with the changes discussed in cloudfoundry-attic/cf-docs#59, I get the following error:

$ bundle exec bosh aws create
allocating 1 KeyPair(s)
creating internet gateway
creating security groups: open, bosh, bat, cf, web
details in /Users/drnic/Sites/bosh_deployments/aws_vpc/aws_vpc_receipt.yml
/Users/drnic/Sites/bosh_deployments/aws_vpc/vendor/cache/bosh-2855fba7a02f/bosh_aws_bootstrap/lib/bosh_aws_bootstrap/vpc.rb:80:in `block in create_security_groups': undefined method `for_sgroup' for Bosh::AwsCloud::ResourceWait:Class (NoMethodError)
    from /Users/drnic/Sites/bosh_deployments/aws_vpc/vendor/cache/bosh-2855fba7a02f/bosh_aws_bootstrap/lib/bosh_aws_bootstrap/vpc.rb:77:in `each'
    from /Users/drnic/Sites/bosh_deployments/aws_vpc/vendor/cache/bosh-2855fba7a02f/bosh_aws_bootstrap/lib/bosh_aws_bootstrap/vpc.rb:77:in `create_security_groups'
    from /Users/drnic/Sites/bosh_deployments/aws_vpc/vendor/cache/bosh-2855fba7a02f/bosh_aws_bootstrap/lib/bosh/cli/commands/aws.rb:194:in `create_vpc'
    from /Users/drnic/Sites/bosh_deployments/aws_vpc/vendor/cache/bosh-2855fba7a02f/bosh_aws_bootstrap/lib/bosh/cli/commands/aws.rb:148:in `create'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.446/lib/cli/command_handler.rb:57:in `run'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.446/lib/cli/runner.rb:59:in `run'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.446/lib/cli/runner.rb:18:in `run'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/gems/bosh_cli-1.5.0.pre.446/bin/bosh:7:in `<top (required)>'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/bin/bosh:19:in `load'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/bin/bosh:19:in `<main>'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/bin/ruby_noexec_wrapper:14:in `eval'
    from /Users/drnic/.rvm/gems/ruby-1.9.3-p392/bin/ruby_noexec_wrapper:14:in `<main>'

Rate Limit BOSH's creation

Please see the thread here:
https://groups.google.com/a/cloudfoundry.org/forum/?fromgroups=#!topic/bosh-users/255kMFvnIM8

Currently the number of threads that BOSH is 32 and is not tunable. We get timeout on a smaller infrastructure.

Broken bosh ssh

Context: When debugging a vm in a undesired state bosh_cli (1.5.0.pre.446).
Problem: Being unable to ssh into the vm.

bosh ssh director 0
Enter password (use it to sudo on remote host): ************
Target deployment is `bosh'
Failed to set up SSH: see task  log for details

bosh task 16 --debug
Director task 16
# Logfile created on 2013-04-11 06:37:20 +0000 by logger.rb/31641
I, [2013-04-11T06:37:20.079325 #2593]  INFO -- : Director Version : 1.5.0.pre.3
I, [2013-04-11T06:37:20.079392 #2593]  INFO -- : Enqueuing task: 16
I, [2013-04-11T06:37:23.527610 #11176] [0xf2006c]  INFO -- : Starting task: 16
I, [2013-04-11T06:37:23.527710 #11176] [task:16]  INFO -- : Creating job
D, [2013-04-11T06:37:23.655374 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.656190 #11176] [task:16] DEBUG -- : (0.000594s) SELECT * FROM "tasks" WHERE "id" = 16
D, [2013-04-11T06:37:23.656579 #11176] [task:16] DEBUG -- : Released connection: 17076560
I, [2013-04-11T06:37:23.656869 #11176] [task:16]  INFO -- : Performing task: 16
D, [2013-04-11T06:37:23.657739 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.658128 #11176] [task:16] DEBUG -- : (0.000159s) BEGIN
D, [2013-04-11T06:37:23.660300 #11176] [task:16] DEBUG -- : (0.001000s) UPDATE "tasks" SET "state" = 'processing', "timestamp" = '2013-04-11 06:37:23.657402+0000', "description" = 'ssh: setup:{"job"=>"director", "indexes"=>[0]}', "result" = NULL, "output" = '/var/vcap/store/director/tasks/16', "user_id" = 1, "checkpoint_time" = '2013-04-11 06:37:23.657489+0000', "type" = 'ssh' WHERE ("id" = 16)
D, [2013-04-11T06:37:23.661789 #11176] [task:16] DEBUG -- : (0.001246s) COMMIT
D, [2013-04-11T06:37:23.662091 #11176] [task:16] DEBUG -- : Released connection: 17076560
D, [2013-04-11T06:37:23.662744 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.662867 #11176] [task:16] DEBUG -- : Released connection: 17076560
D, [2013-04-11T06:37:23.663077 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.664267 #11176] [task:16] DEBUG -- : (0.001071s) SELECT * FROM "instances" WHERE (("deployment_id" = 1) AND ("index" IN (0)) AND ("job" = 'director'))
D, [2013-04-11T06:37:23.664468 #11176] [task:16] DEBUG -- : Released connection: 17076560
D, [2013-04-11T06:37:23.665295 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.666242 #11176] [task:16] DEBUG -- : (0.000787s) SELECT * FROM "vms" WHERE ("vms"."id" = 5) LIMIT 1
D, [2013-04-11T06:37:23.666408 #11176] [task:16] DEBUG -- : Released connection: 17076560
D, [2013-04-11T06:37:23.666999 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.667110 #11176] [task:16] DEBUG -- : Released connection: 17076560
D, [2013-04-11T06:37:23.667246 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.667882 #11176] [task:16] DEBUG -- : (0.000528s) SELECT * FROM "vms" WHERE ("agent_id" = '7d011ea6-db18-486c-b367-157afedf70fa') LIMIT 1
D, [2013-04-11T06:37:23.668067 #11176] [task:16] DEBUG -- : Released connection: 17076560
I, [2013-04-11T06:37:23.669526 #11176] [task:16]  INFO -- : ssh setup `director/0'
D, [2013-04-11T06:37:23.669991 #11176] [task:16] DEBUG -- : SENT: agent.7d011ea6-db18-486c-b367-157afedf70fa {"method":"ssh","arguments":["setup",{"user":"{user_name}","public_key":"ssh-rsa {key} vcap@inception-vm\n","password":"{pw}"}],"reply_to":"director.80c40800-5e2a-499f-ba7f-ed06c32e332c.a41f037a-aa9c-4687-9379-fb03c81abbe1"}
D, [2013-04-11T06:37:23.787343 #11176] [0x17c28dc] DEBUG -- : RECEIVED: director.80c40800-5e2a-499f-ba7f-ed06c32e332c.a41f037a-aa9c-4687-9379-fb03c81abbe1 {"value":{"command":"setup","status":"success","ip":"10.200.7.10"}}
I, [2013-04-11T06:37:23.788292 #11176] [task:16]  INFO -- : Done
D, [2013-04-11T06:37:23.788882 #11176] [task:16] DEBUG -- : Acquired connection: 17076560
D, [2013-04-11T06:37:23.789350 #11176] [task:16] DEBUG -- : (0.000262s) BEGIN
D, [2013-04-11T06:37:23.791272 #11176] [task:16] DEBUG -- : (0.000808s) UPDATE "tasks" SET "state" = 'done', "timestamp" = '2013-04-11 06:37:23.788577+0000', "description" = 'ssh: setup:{"job"=>"director", "indexes"=>[0]}', "result" = '', "output" = '/var/vcap/store/director/tasks/16', "user_id" = 1, "checkpoint_time" = '2013-04-11 06:37:23.657489+0000', "type" = 'ssh' WHERE ("id" = 16)
D, [2013-04-11T06:37:23.792613 #11176] [task:16] DEBUG -- : (0.001050s) COMMIT
D, [2013-04-11T06:37:23.792770 #11176] [task:16] DEBUG -- : Released connection: 17076560
I, [2013-04-11T06:37:23.792934 #11176] [0xf2006c]  INFO -- : Task took 0.265165193 seconds to process.

micro.rb has been loaded as plugin but it didn't contain any commands. Make sure this plugin is updated to be compatible with BOSH CLI 1.0.

After installing bosh_deployer if i run commands like "bosh help" or "bosh micro deployment aws" i get following error.
Failed to load plugin gems/bosh_deployer-1.4.1/lib/bosh/cli/commands/micro.rb: Unable to activate fog-1.10.0, because net-scp-1.0.4 conflicts with net-scp (~> 1.1)
File gems/bosh_deployer-1.4.1/lib/bosh/cli/commands/micro.rb has been loaded as
plugin but it didn't contain any commands. Make sure this plugin is updated to
be compatible with BOSH CLI 1.0.
Unknown command: micro deployment aws

Please let me know how i can fix this. here are my env details

RubyGems Environment:

RUBYGEMS VERSION: 2.0.2
RUBY VERSION: 1.9.3 (2011-10-30 patchlevel 0) [x86_64-linux]
INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.9.1
RUBY EXECUTABLE: /usr/bin/ruby1.9.1
EXECUTABLE DIRECTORY: /usr/bin
RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
GEM PATHS:
- /usr/lib/ruby/gems/1.9.1
- /home/apande/.gem/ruby/1.9.1
GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
REMOTE SOURCES:
- https://rubygems.org/

Regards
Ajay

openstack_registry_ctl start migration failed

I created a microbosh stemcell from master for openstack. When deploying this microbosh every thing looks fine. But when I have targeted it and trying to deploy a release I get:

Compiling packages
  wordpress/1: Connection refused - connect(2) (http://10.200.7.4:25777) (00:00:37)                 
  apache2/1: Connection refused - connect(2) (http://10.200.7.4:25777) (00:00:43)                   
  nginx/1: Connection refused - connect(2) (http://10.200.7.4:25777) (00:00:51)

When diving deeper I found that the openstack_registry was not running on the mirobosh vm. When trying to start it manually with openstack_registry_ctl start I get:
migration failed
openstack_registry/migrate.stderr.log shows:

/var/vcap/packages/openstack_registry/gem_home/gems/bosh_openstack_registry-1.5.0.pre/bin/migrate:7:in `<top (required)>': uninitialized constant OptionParser (NameError)
    from /var/vcap/packages/openstack_registry/bin/migrate:23:in `load'
    from /var/vcap/packages/openstack_registry/bin/migrate:23:in `<main>'

Looks like require "optparse" should be added here

Cannot deploy microbosh stemcell 0.8.1 using HEAD bosh_deployer

cat microbosh-aws-us-east-1/bosh_micro_deploy.log
...
I, [2013-02-07T06:11:26.002934 #14828] [create_stemcell(/var/vcap/store/tmp/d20130207-14828-1slo3tl/sc-20130207-14828-1o746y9/image...)]  INFO -- : Copying stemcell disk image to '/dev/sdf'
D, [2013-02-07T06:11:26.002992 #14828] [create_stemcell(/var/vcap/store/tmp/d20130207-14828-1slo3tl/sc-20130207-14828-1o746y9/image...)] DEBUG -- : copying stemcell using stemcell-copy script
E, [2013-02-07T06:11:26.286700 #14828] [create_stemcell(/var/vcap/store/tmp/d20130207-14828-1slo3tl/sc-20130207-14828-1o746y9/image...)] ERROR -- : Unable to copy stemcell root image, exit status 1: /usr/local/bin/stemcell-copy:23:in `load': /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:8: unknown regexp option - r (SyntaxError)
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:11: syntax error, unexpected $undefined, expecting ']'
if [ $# -ne 2 ]; then
      ^
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:20: syntax error, unexpected $undefined, expecting $end
echo ${IMAGE} | LANG=C egrep '^/[A-...
      ^
    from /usr/local/bin/stemcell-copy:23:in `<main>'

E, [2013-02-07T06:11:26.286920 #14828] [create_stemcell(/var/vcap/store/tmp/d20130207-14828-1slo3tl/sc-20130207-14828-1o746y9/image...)] ERROR -- : Unable to copy stemcell root image, exit status 1: /usr/local/bin/stemcell-copy:23:in `load': /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:8: unknown regexp option - r (SyntaxError)
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:11: syntax error, unexpected $undefined, expecting ']'
if [ $# -ne 2 ]; then
      ^
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/bin/stemcell-copy:20: syntax error, unexpected $undefined, expecting $end
echo ${IMAGE} | LANG=C egrep '^/[A-...
      ^
    from /usr/local/bin/stemcell-copy:23:in `<main>'
 (Bosh::Clouds::CloudError)
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-1.5.0.pre/lib/cloud/aws/helpers.rb:16:in `cloud_error'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-1.5.0.pre/lib/cloud/aws/cloud.rb:544:in `copy_root_image'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-1.5.0.pre/lib/cloud/aws/cloud.rb:314:in `block in create_stemcell'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_common-1.5.0.pre/lib/common/thread_formatter.rb:46:in `with_thread_name'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-1.5.0.pre/lib/cloud/aws/cloud.rb:298:in `create_stemcell'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/lib/deployer/instance_manager.rb:209:in `block (2 levels) in create_stemcell'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/lib/deployer/instance_manager.rb:84:in `step'
/usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.5.0.pre/lib/deployer/instance_manager.rb:208:in `block in create_stemcell'

rake stemcell:mcf failed - sed: can't read /home/vcap/micro/micro/lib/micro/version.rb: No such file or directory

Building the v1 mcf (using manifest.yml rather than manifest_ng.yml)

... builds all the packages etc ...
+ enable /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/sbin/initctl
+ '[' -L /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/sbin/initctl ']'
+ mv /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/sbin/initctl.back /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/sbin/initctl
+ enable /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/usr/sbin/invoke-rc.d
+ '[' -L /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/usr/sbin/invoke-rc.d ']'
+ mv /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/usr/sbin/invoke-rc.d.back /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot/usr/sbin/invoke-rc.d
+ mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/stemcell
+ cp /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/chroot//var/vcap/micro/apply_spec.yml /var/tmp/bosh/bosh_agent-1.5.0.pre-19739/work/work/stemcell
sed: can't read /home/vcap/micro/micro/lib/micro/version.rb: No such file or directory

Incorrect YAML structure in `/var/vcap/store/repos/bosh/release/config/final.yml': undefined method `root'

As observed here - https://travis-ci.org/StarkAndWayne/bosh-bootstrap/jobs/6115624#L2169

bosh create release --force --with-tarball
Incorrect YAML structure in `/var/vcap/store/repos/bosh/release/config/final.yml': undefined method `root' for #<Psych::Nodes::Mapping:0x00000002345498>
rake aborted!
Command failed with status (1): [bosh create release --force --with-tarball...]
/var/vcap/store/repos/bosh/vendor/bundle/ruby/1.9.1/gems/rake-10.0.4/lib/rake/file_utils.rb:53:in `block in create_shell_runner'
/var/vcap/store/repos/bosh/vendor/bundle/ruby/1.9.1/gems/rake-10.0.4/lib/rake/file_utils.rb:45:in `call'
/var/vcap/store/repos/bosh/vendor/bundle/ruby/1.9.1/gems/rake-10.0.4/lib/rake/file_utils.rb:45:in `sh'
/var/vcap/store/repos/bosh/vendor/bundle/ruby/1.9.1/gems/rake-10.0.4/lib/rake/file_utils_ext.rb:37:in `sh'
/var/vcap/store/repos/bosh/rake/stemcell.rake:62:in `block in build_micro_bosh_release'
/var/vcap/store/repos/bosh/rake/stemcell.rake:60:in `chdir'
/var/vcap/store/repos/bosh/rake/stemcell.rake:60:in `build_micro_bosh_release'
/var/vcap/store/repos/bosh/rake/stemcell.rake:26:in `block (2 levels) in <top (required)>'

Rate limit on Compiling packages OpenStack

When deploying on the cf-release on OpenStack, during the compiling packages phase the deployment get canceled after receiving a number of errors.
The error message I receive is This request was rate-limited., the {ip} in is the ip of the openstack api.

gorouter/2.1-dev: Expected(200) <=> Actual(413 Request Entity Too Large)                          
  request => {:chunk_size=>1048576, :connect_timeout=>60, :headers=>{"User-Agent"=>"fog/1.9.0", "Content-Type"=>"application/json", "Accept"=>"application/json", "X-Auth-Token"=>"17defa57c4d5430c963e08b30ea6197d", "Host"=>"{ip}:80", "Content-Length"=>37}, :idempotent=>false, :instrumentor_name=>"excon", :middlewares=>[Excon::Middleware::Instrumentor, Excon::Middleware::Expects, Excon::Middleware::Mock], :mock=>false, :nonblock=>true, :read_timeout=>60, :retry_limit=>4, :ssl_ca_file=>"/var/vcap/packages/director/gem_home/gems/excon-0.18.5/data/cacert.pem", :ssl_verify_peer=>true, :write_timeout=>60, :host=>"{ip}", :path=>"/compute/v1.1/7276102beb584c66a11bb6b923a4d4f1/servers/9eec7c56-191e-4872-af65-85188fed0445/metadata.json", :port=>"80", :query=>"ignore_awful_caching1364281433", :scheme=>"http", :user=>nil, :password=>nil, :family=>0, :body=>"{\"metadata\":{\"compiling\":\"gorouter\"}}", :expects=>200, :method=>"POST", :retries_remaining=>4}
  response => {:body=>"{\"overLimitFault\": {\"message\": \"This request was rate-limited.\", \"code\": 413, \"details\": \"Only 10 POST request(s) can be made to * every minute.\"}}", :headers=>{"Date"=>"Tue, 26 Mar 2013 07:03:53 GMT", "Content-Type"=>"text/html; charset=UTF-8", "Retry-After"=>"2", "Content-Length"=>"147", "Vary"=>"Accept-Encoding", "Connection"=>"close"}, :status=>413, :remote_ip=>"{ip}"} (00:00:00)

I have had a similar problem in the instance creation phase but this could be solved by setting:

properties:
  director:                                                                                                                                    
    max_threads: 10

In the manifest of the big bosh.

possible to have multiple releases currently deployed

A few times my dev instance has gotten into this state:

+----------+-------------------------------------------------------------+
| Name     | Versions                                                    |
+----------+-------------------------------------------------------------+
| appcloud | 130.5-dev, 130.8-dev, 130.10-dev*, 130.11-dev*, 130.12-dev* |
+----------+-------------------------------------------------------------+
(*) Currently deployed

It seems to be related to bosh rebase. When in this state upload --rebase always reports:

Error 100: Rebase is attempted without any job or package changes

The only fix I know of is to delete the entire deployment.

request: URL for latest microbosh stemcell

Currently there is a URL for the latest microbosh AMI for us-east-1. Can we also have a url for the stemcell artifact that was used to create that AMI? This could then be used by other regions and OpenStack etc rather than them have to run the rake stemcell:basic command.

Reg: Error in micro bosh stemcell upload on vsphere:

Hi,
I have vsphere cluster setup ready and micro_bosh.yml configured properly.And set it up as deployment,Then finally i trying to deploy micro bpsh stemcell,getting below error.Any one already phased this issue or Know how to resolve pls reply me as soon as possible,That will help me allot.

Error:

bosh micro deploy ~/stemcells/micro-bosh-stemcell-vsphere-0.8.1.tgz
Deploying new micro BOSH instance vsphere/micro_bosh.yml' tohttp://10.117.38.171:25555' (type 'yes' to continue): yes

Verifying stemcell...
File exists and readable OK
Using cached manifest...
Stemcell properties OK

Stemcell info

Name: micro-bosh-stemcell
Version: 0.8.1

Deploy Micro BOSH
Unpacking stemcell | | 0/11 00:00:04 ETA: --:--:--https://10.112.118.100/sdk/vimService
unpacking stemcell (00:00:04)
Uploading stemcell |oo | 1/11 00:00:05 ETA: 00:00:44at depth 0 - 20: unable to get local issuer certificate
Uploading stemcell |oo | 1/11 00:00:06 ETA: 00:00:43/root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-

0.0.3/lib/ruby_vim_sdk/soap/stub_adapter.rb:45:in invoke_method': 404 (Net::HTTPError) from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-0.0.3/lib/ruby_vim_sdk/vmodl/managed_object.rb:13:ininvoke_method'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-0.0.3/lib/ruby_vim_sdk/vmodl/managed_object.rb:45:in block (3 levels) in finalize' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-0.0.3/lib/ruby_vim_sdk/soap/stub_adapter.rb:58:ininvoke_property'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-0.0.3/lib/ruby_vim_sdk/vmodl/managed_object.rb:17:in invoke_property' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/ruby_vim_sdk-0.0.3/lib/ruby_vim_sdk/vmodl/managed_object.rb:30:inblock (3 levels) in finalize'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere/client.rb:30:in initialize' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere/config.rb:229:innew'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere/config.rb:229:in configure' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere/cloud.rb:28:ininitialize'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere.rb:23:in new' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_vsphere_cpi-0.6.0/lib/cloud/vsphere.rb:23:ininitialize'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cpi-0.5.1/lib/cloud/provider.rb:10:in new' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cpi-0.5.1/lib/cloud/provider.rb:10:increate'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/config.rb:68:in cloud' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:59:incloud'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:215:in `block (2 levels) in

create_stemcell'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:84:in step' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:214:inblock in create_stemcell'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/1.9.1/tmpdir.rb:83:in mktmpdir' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:200:increate_stemcell'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:128:in create' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:104:inblock in create_deployment'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:97:in with_lifecycle' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/deployer/instance_manager.rb:103:increate_deployment'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.1/lib/bosh/cli/commands/micro.rb:171:in perform' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/command_handler.rb:57:inrun'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:61:in run' from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:18:inrun'
from /root/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/bin/bosh:16:in <top (required)>' from /root/.rbenv/versions/1.9.3-p385/bin/bosh:23:inload'
from /root/.rbenv/versions/1.9.3-p385/bin/bosh:23:in `

Thanks,
Hari.

Cannot install bosh_deployer

$ sudo gem install bosh_deployer
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: fog requires net-scp (~> 1.1); bosh_cli requires net-scp (~> 1.0.4)

Waiting for the agent Openstack

I created a microbosh stemcell from master at 346bb97 and tried to deploy it with bosh deployer from master. This resulted in the following Waiting for the agent

ient/http_client.rb:44:in `rescue in request': Request details: (Bosh::Agent::Error)
uri: http://vcap:[email protected]:6868/agent
payload: {"method":"ping","arguments":[],"reply_to":"bm-6b9a7da5-1839-4740-841b-37c5ebb5bf3f"}
user: vcap
password: b00tstrap
Errno::ECONNREFUSED: Connection refused - connect(2) (http://185.2.148.51:6868)

When sshing into the created micro bosh vm I can see the following in var/vcap/bosh/log/current:

2013-03-16_22:02:25.35485 #[9737] INFO: Loaded settings: #<Bosh::Agent::Settings:0x0000000258c170 @settings={"vm"=>{"name"=>"vm-b0cea3b7-ba51-40f1-93eb-c89d521b5d7b"}, "agent_id"=>"bm-6b9a7da5-1839-4740-841b-37c5ebb5bf3f", "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil, "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic", "default"=>["dns", "gateway"]}, "vip"=>{"ip"=>"{ip}", "type"=>"vip", "cloud_properties"=>{}}}, "disks"=>{"system"=>"/dev/vda", "ephemeral"=>"/dev/vdb", "persistent"=>{}}, "env"=>{"bosh"=>{"password"=>"{pw}"}}, "ntp"=>[], "blobstore"=>{"plugin"=>"local", "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}}, "mbus"=>"http://vcap:[email protected]:6868"}, @cache_file="/var/vcap/bosh/settings.json">
2013-03-16_22:02:25.41004 /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/bootstrap.rb:136:in `merge!': can't convert nil into Hash (TypeError)
2013-03-16_22:02:25.41017   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/bootstrap.rb:136:in `update_blobstore'
2013-03-16_22:02:25.41020   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/bootstrap.rb:45:in `configure'
2013-03-16_22:02:25.41022   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent.rb:100:in `start'
2013-03-16_22:02:25.41024   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent.rb:79:in `run'
2013-03-16_22:02:25.41026   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/bin/bosh_agent:96:in `<top (required)>'
2013-03-16_22:02:25.41029   from /var/vcap/bosh/bin/bosh_agent:23:in `load'
2013-03-16_22:02:25.41031   from /var/vcap/bosh/bin/bosh_agent:23:in `<main>'

unresponsive agents over time OpenStack

I have deployed a micro bosh on OpenStack and with this micro bosh a normal bosh has been deployed. I have been deploying other stuff with this normal bosh on friday. Over the weekend however some of the instances in the bosh deployment have become unresponsive. I get the following when bosh vms while targeting the micro bosh.

+------------------+--------------------+---------------+-------------+
| Job/index        | State              | Resource Pool | IPs         |
+------------------+--------------------+---------------+-------------+
| unknown/unknown  | unresponsive agent |               |             |
| unknown/unknown  | unresponsive agent |               |             |
| unknown/unknown  | unresponsive agent |               |             |
| unknown/unknown  | unresponsive agent |               |             |
| blobstore/0      | running            | small         | 10.200.7.9  |
| health_monitor/0 | running            | small         | 10.200.7.7  |
| postgres/0       | running            | small         | 10.200.7.12 |
| redis/0          | running            | small         | 10.200.7.10 |
+------------------+--------------------+---------------+-------------+

I'm currently running Version 1.5.0.pre2 (release:346bb97d bosh:346bb97d) which is created from master one week ago. I created a micro-bosh and a normal stemcell from this same commit.

VM Termination and Creation script

Martin asked me to create a feature request, as per https://groups.google.com/a/cloudfoundry.org/forum/?fromgroups=#!topic/bosh-users/STY50rUj_eA

I'm looking for a hook to run scripts on VM creation and deletion.

For both of these situations, there should be an option to run scripts in separate circumstances.

running job state.

with a deletion event - when the VM/jobs are still running normally
with a creation event - after all jobs are successfully started

stopped job state.

with a deletion event - after all jobs are stopped for the final time
with a creation event - before jobs are started for the first time

The use case here is for a VM in a distributed system to notify it's peers that it's going down for deletion, and that the data it's responsible for needs a new home.

thanks

James Masson

Cannot delete a stemcell - undefined method `snapshot_id' for :snapshot_id:Symbol

$ bosh -n --color delete stemcell bosh-stemcell 0.7.0
Checking if stemcell exists...
You are going to delete stemcell `bosh-stemcell/0.7.0'

Director task 59

Deleting stemcell from cloud
  delete stemcell: undefined method `snapshot_id' for :snapshot_id:Symbol (00:00:00)                
Error                   1/1 00:00:00                                                                

Error 100: undefined method `snapshot_id' for :snapshot_id:Symbol

deployer 1.4 / microbosh 0.8.1 - timeout after 19mins of "waiting for the agent"

Deploy Micro BOSH
  unpacking stemcell (00:00:13)                                                 
  uploading stemcell (00:11:20)                                                 
  creating VM from ami-1ee17777 (00:00:27)
Waiting for the agent        |ooooo              | 3/11 00:19:07  ETA: 00:24:57/usr/local/lib/ruby/gems/1.9.1/gems/agent_client-0.1.1/lib/agent_client/http_client.rb:46:in `rescue in request': cannot access agent (Connection refused - connect(2) (http://54.235.133.196:6868)) (Bosh::Agent::Error)

In the bosh logs:

I, [2013-02-07T07:00:57.923009 #18367] [0xb19ea0]  INFO -- : discovered bosh ip=54.235.133.196
I, [2013-02-07T07:00:58.004944 #18367] [0xb19ea0]  INFO -- : [AWS EC2 200 0.079246 0 retries] describe_addresses(:filters=>[{:name=>"instance-id",:values=>["i-cd96dbbd"]}])  

I, [2013-02-07T07:00:58.094337 #18367] [0xb19ea0]  INFO -- : [AWS EC2 200 0.08894 0 retries] describe_addresses(:filters=>[{:name=>"instance-id",:values=>["i-cd96dbbd"]}])  

D, [2013-02-07T07:01:19.092772 #18367] [0xb19ea0] DEBUG -- : tcp socket 54.235.133.196:22 SystemCallError: #<Errno::ETIMEDOUT: Connection timed out - connect(2)>
D, [2013-02-07T07:01:41.102731 #18367] [0xb19ea0] DEBUG -- : tcp socket 54.235.133.196:22 SystemCallError: #<Errno::ETIMEDOUT: Connection timed out - connect(2)>
D, [2013-02-07T07:02:03.116499 #18367] [0xb19ea0] DEBUG -- : tcp socket 54.235.133.196:22 SystemCallError: #<Errno::ETIMEDOUT: Connection timed out - connect(2)>
D, [2013-02-07T07:02:04.150902 #18367] [0xb19ea0] DEBUG -- : tcp socket 54.235.133.196:22 is readable
I, [2013-02-07T07:03:04.160184 #18367] [0xb19ea0]  INFO -- : Preparing for ssh tunnel: ssh -R 25888:127.0.0.1:25888 [email protected]
D, [2013-02-07T07:03:04.385738 #18367] [0xb19ea0] DEBUG -- : ssh [email protected]: ESTABLISHED
I, [2013-02-07T07:03:04.385907 #18367] [0xb19ea0]  INFO -- : `ssh -R 25888:127.0.0.1:25888 [email protected]` started: OK

It looks like the "bosh micro deploy" command gave up/timed out just before the tunnel was finally open? (I'm not sure if I'm understanding what's going on here)

Cannot delete stemcell from Openstack

Originally posted at https://groups.google.com/a/cloudfoundry.org/forum/?fromgroups=#!topic/bosh-users/TsCVaqEODDg

The stemcell was uploaded, then deleted manually from Openstack (on accident, I got confuse as to which was which)
Then I couldn't delete it from the bosh director's stemcell registry

Compiling packages
rabbitmq-2.8/1: OpenStack CPI: image 85a7426e-876b-4c6f-9960-cfe5954cb92b not found (00:00:01)
postgresql/6: OpenStack CPI: image 85a7426e-876b-4c6f-9960-cfe5954cb92b not found (00:00:01)
vblob/5: OpenStack CPI: image 85a7426e-876b-4c6f-9960-cfe5954cb92b not found (00:00:01)
node/2: OpenStack CPI: image 85a7426e-876b-4c6f-9960-cfe5954cb92b not found (00:00:01)
Error 4/61 00:00:01

Error 100: OpenStack CPI: image 85a7426e-876b-4c6f-9960-cfe5954cb92b not found

Task 14 error
root@lucid64:/var/vcap/deployments# bosh stemcells

+---------------+---------+--------------------------------------+
| Name | Version | CID |
+---------------+---------+--------------------------------------+
| bosh-stemcell | 0.6.7 | 85a7426e-876b-4c6f-9960-cfe5954cb92b |
+---------------+---------+--------------------------------------+

Stemcells total: 1
root@lucid64:/var/vcap/deployments# bosh delete stemcell bosh-stemcell 0.6.7
Checking if stemcell exists...
You are going to delete stemcell `bosh-stemcell/0.6.7'
Are you sure? (type 'yes' to continue): yes

Director task 17

Deleting stemcell from cloud
delete stemcell: undefined method `properties' for nil:NilClass (00:00:00)
Error 1/1 00:00:00

Error 100: undefined method `properties' for nil:NilClass

Task 17 error
root@lucid64:/var/vcap/deployments# bosh stemcells

+---------------+---------+--------------------------------------+
| Name | Version | CID |
+---------------+---------+--------------------------------------+
| bosh-stemcell | 0.6.7 | 85a7426e-876b-4c6f-9960-cfe5954cb92b |
+---------------+---------+--------------------------------------+

Stemcells total: 1

`bosh micro delete` loses the reference to the uploaded stemcell and requires re-upload on next deploy

bosh_cli 1.5.0.pre2 reports uninitialized constant Retryable::Methods (NameError)

GEM LIST:

archive-tar-minitar (0.5.2)
aws-sdk (1.8.3.1)
blobstore_client (1.5.0.pre2)
bosh_cli (1.5.0.pre2)
bosh_common (1.5.0.pre2)
builder (3.2.0)
bundler (1.3.1)
excon (0.19.5)
fog (1.9.0)
formatador (0.2.4)
highline (1.6.15)
httpclient (2.2.4)
json (1.7.7)
json_pure (1.7.7)
log4r (1.1.10)
mime-types (1.21)
multi_json (1.6.1)
net-scp (1.0.4)
net-ssh (2.6.6)
net-ssh-gateway (1.1.0)
netaddr (1.5.0)
nokogiri (1.5.6)
progressbar (0.9.2)
rake (10.0.3)
retryable (1.3.2)
ruby-atmos-pure (1.0.5)
ruby-hmac (0.4.0)
rubygems-bundler (1.1.1)
rvm (1.11.3.6)
terminal-table (1.4.5)
uuidtools (2.1.3)

RubyGems Environment:

RUBYGEMS VERSION: 1.8.25
RUBY VERSION: 1.9.3 (2013-02-22 patchlevel 392) [x86_64-linux]
INSTALLATION DIRECTORY: /home/boshcli/.rvm/gems/ruby-1.9.3-p392
RUBY EXECUTABLE: /home/boshcli/.rvm/rubies/ruby-1.9.3-p392/bin/ruby
EXECUTABLE DIRECTORY: /home/boshcli/.rvm/gems/ruby-1.9.3-p392/bin
RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
GEM PATHS:
- /home/boshcli/.rvm/gems/ruby-1.9.3-p392
- /home/boshcli/.rvm/gems/ruby-1.9.3-p392@global
GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- "install" => "--no-rdoc --no-ri"
- "update" => "--no-rdoc --no-ri"
REMOTE SOURCES:
- http://rubygems.org/

Bosh release issue with vSphere CPI

I got the following error when trying to upgrade bosh from version 12 to 13.

Preparing configuration
  binding configuration: Error filling in template `director.yml.erb' for `director/0' (line 136: undefined method `name' for #<Hash:0x000000033a57c0>) (00:00:00)
Error                   1/1 00:00:00                                                                

Error 80006: Error filling in template `director.yml.erb' for `director/0' (line 136: undefined method `name' for #<Hash:0x000000033a57c0>)

My deployment manifest is Ok. It worked for a long time with version 12.

It is odd that the dc is a Hash type here:
https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/templates/director.yml.erb#L136

Did not find any workaround or fix for the besides using the old style of accessing properties.
Any thoughts on where I cloud look for the issue?

[openstack] [microbosh] fail nicely if select VM flavor does not have /dev/vdb ephemeral disk

Currently if you boot a microbosh on an openstack VM that has no ephemeral disk, the bosh agent just hangs waiting for /dev/vdb; it never binds to 6868; and the bosh deployer times out trying to connect to it. Its not obvious that the issue is the missing /dev/vdb disk.

Error while deleting the bosh micro deployment

Delete stemcell is giving the can't convert Symbol into Integer issue while deleting the micro bosh deployment. Below is the stacktrace.

Delete stemcell |ooooooooooooooooo | 5/7 00:06:31 ETA: 00:02:36/usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-0.7.0/lib/cloud/aws/cloud.rb:373:in []': can't convert Symbol into Integer (TypeError) from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-0.7.0/lib/cloud/aws/cloud.rb:373:inblock (2 levels) in delete_stemcell'
from /usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/data.rb:92:in block in method_missing' from /usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/data.rb:91:ineach'
from /usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/data.rb:91:in method_missing' from /usr/local/lib/ruby/gems/1.9.1/gems/aws-sdk-1.6.9/lib/aws/core/data.rb:116:inmethod_missing'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-0.7.0/lib/cloud/aws/cloud.rb:372:in block in delete_stemcell' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_common-0.5.4/lib/common/thread_formatter.rb:46:inwith_thread_name'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-0.7.0/lib/cloud/aws/cloud.rb:368:in delete_stemcell' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:426:inblock in delete_stemcell'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:84:in step' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:425:indelete_stemcell'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:176:in destroy' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:116:inblock in delete_deployment'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:97:in with_lifecycle' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/deployer/instance_manager.rb:115:indelete_deployment'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_deployer-1.4.0/lib/bosh/cli/commands/micro.rb:205:in delete' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/command_handler.rb:57:inrun'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:61:in run' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:18:inrun'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/bin/bosh:16:in <top (required)>' from /usr/local/bin/bosh:23:inload'
from /usr/local/bin/bosh:23:in `

DNS problem micro-bosh OpenStack

I have deployed a micro bosh with bosh-bootstrap.
Using the --edge-stemcell flag.
I also created a stemcell from source with the rake task.

Bosh version is git reflog
f81bc14 HEAD@{0}: clone: from https://github.com/cloudfoundry/bosh.git

bosh status
Updating director data... done

Director
  Name      microbosh-openstack
  URL       http://<public_ip>:25555
  Version   1.5.0.pre (00000000)
  User      admin
  UUID      e483842b-87f0-4d50-9fa0-04f885c882a3
  CPI       openstack
  dns       enabled

When deploying the wordpress sample release with the attached manifest I receive the following error:

Updating job wordpress
  wordpress/0 (canary) (00:02:11)                                                                   
Done                    1/1 00:02:11                                                                
Error 400007: `wordpress/0' is not running after update

When using bosh ssh to start the job manually (bosh logs returned nothing usefull) I get:

./wordpress_ctl start
Mounting NFS...
mount.nfs4: DNS resolution failed for 0.nfs.default.wordpress.microbosh: Name or service not known
Cannot mount NFS, exiting...

The host command confirms the above

host 0.nfs.default.wordpress.microbosh
Host 0.nfs.default.wordpress.microbosh not found: 3(NXDOMAIN)

The records are available in the powerdns db

powerdns=> select id, name, type, content from records;
 id |                  name                   | type |                     content                      
----+-----------------------------------------+------+--------------------------------------------------
  2 | microbosh                               | NS   | ns.microbosh
  3 | ns.microbosh                            | A    | 
  4 | 0.mysql.default.wordpress.microbosh     | A    | 10.200.7.5
  5 | 7.200.10.in-addr.arpa                   | SOA  | localhost hostmaster@localhost 0 10800 604800 30
  6 | 7.200.10.in-addr.arpa                   | NS   | ns.microbosh
  7 | 5.7.200.10.in-addr.arpa                 | PTR  | 0.mysql.default.wordpress.microbosh
  8 | 0.nfs.default.wordpress.microbosh       | A    | 10.200.7.9
  9 | 9.7.200.10.in-addr.arpa                 | PTR  | 0.nfs.default.wordpress.microbosh
 10 | 0.wordpress.default.wordpress.microbosh | A    | 10.200.7.7

The resolver config on the wordpress machine however shows something strange

cat /etc/resolv.conf 
nameserver 10.200.7.1
domain novalocal
search novalocal

So the bosh agent adds a wrong dns server address to the resolver. Because the private address of the micro bosh server is 10.200.7.4

Failing stemcell build from master

When running: bundle exec rake stemcell:micro[openstack] while on 156aa0c it get:

bosh create release --force --with-tarball
Incorrect YAML structure in `/var/vcap/store/repos/bosh/release/config/final.yml': undefined method `root' for #<Psych::Nodes::Mapping:0x00000002e63f50>
rake aborted!
Command failed with status (1): [bosh create release --force --with-tarball...]
...
/var/vcap/store/repos/bosh/rake/stemcell.rake:62:in `block in build_micro_bosh_release'
/var/vcap/store/repos/bosh/rake/stemcell.rake:60:in `chdir'
/var/vcap/store/repos/bosh/rake/stemcell.rake:60:in `build_micro_bosh_release'
/var/vcap/store/repos/bosh/rake/stemcell.rake:26:in `block (2 levels) in <top (required)>'

Reg: Error in applcation deployment with centos stemcell on vpshere.

I took CentOS-6.3-x86_64-minimal.iso and created centos stemcell
with help of the stemcell tool followed by below site:
https://github.com/ankurcha/stemcell

Finally uploaded centos stemcell to vpshere micro bosh instance.It's successfully uploaded and i able to to see the output.
"bosh stemcells" command.

bosh stemcells

+----------------------+------------+-----------------------------------------+
| Name | Version | CID |
+----------------------+------------+-----------------------------------------+
| bosh-centos-stemcell | 1.5.0.pre2 | sc-4b4baf7d-3cbf-4b9e-b8a6-bba6ffbf2e07 |
| bosh-stemcell | 0.6.7 | sc-d21bff0b-a26f-4fae-8ee6-c8d1c5819f6d |
+----------------------+------------+-----------------------------------------+

Stemcells total: 2

Error:

Already i have one release that one is working with application deployment on ubuntu.

Now what i did edited manifest file relative to this and executed "bosh deploy",then i am getting below error.

bosh deploy

Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully
Deploying centos-deploy.yml' tohari' (type 'yes' to continue): yes

Director task 17

Preparing deployment
binding deployment (00:00:00)
binding releases (00:00:00)
binding existing deployment (00:00:00)
binding resource pools (00:00:00)
binding stemcells (00:00:00)
binding templates (00:00:00)
binding properties (00:00:00)
binding unallocated VMs (00:00:00)
binding instance networks (00:00:00)
Done 9/9 00:00:00

Preparing package compilation
finding packages to compile (00:00:00)
Done 1/1 00:00:00

Compiling packages
zabbix/0.1-dev: Timed out pinging to 8369250b-d783-4fd3-8a6f-521528f22b11 after 600 seconds (00:10:30)
Error 1/1 00:10:30

Error 450002: Timed out pinging to 8369250b-d783-4fd3-8a6f-521528f22b11 after 600 seconds

Task 17 error

Observed:

When i started "bosh deploy" new vm is getting created(power on) with centos stemcell but it's not getting IP,Bcz of this reason execution getting stopped and getting above error.Steps what i did for application deployment with ubuntu,For this also did same but vm is not getting deployed.

This problem with centos stemcell,I used ubuntu stemcell not giving any error.How to fix,Can you please suggest me if you found any mistake i did.

Thanks,
Hari.

rake stemcell:mcf failed - cp: cannot stat `/tmp/all_the_gems/multi_xml-*.gem': No such file or directory

$ bundle exec rake stemcell:mcf[vsphere,../micro/deploy/manifest.yml,$LATEST_RELEASE]
...
rm -rf /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_registry
mkdir -p /var/vcap/store/repos/bosh/release/src/bosh/bosh_aws_registry
cp /tmp/all_the_gems/multi_json-*.gem .
cp /tmp/all_the_gems/pg*.gem .
cp /tmp/all_the_gems/multi_xml-*.gem .
cp: cannot stat `/tmp/all_the_gems/multi_xml-*.gem': No such file or directory
rake aborted!
Command failed with status (1): [cp /tmp/all_the_gems/multi_xml-*.gem ....]
/var/vcap/store/repos/bosh/rake/gem.rake:52:in `block (5 levels) in <top (required)>'
/var/vcap/store/repos/bosh/rake/gem.rake:48:in `block (4 levels) in <top (required)>'
/var/vcap/store/repos/bosh/rake/gem.rake:47:in `chdir'
/var/vcap/store/repos/bosh/rake/gem.rake:47:in `block (3 levels) in <top (required)>'
Tasks: TOP => stemcell:mcf => all:build_with_deps => bosh_aws_registry:build_with_deps => bosh_aws_registry:gem_with_deps
(See full trace by running task with --trace)

using latest API version in place of 1.0 for aws

Hi All,

Following on the discussion here:

https://groups.google.com/a/cloudfoundry.org/forum/?fromgroups=#!topic/bosh-users/y7DmjfCJ01c

Can we please replace occurrences of http://169.254.169.254/1.0 with http://169.254.169.254/latest ?

Currently there are 2 places where it is referring to 1.0

File: ./bosh_aws_cpi/lib/cloud/aws/cloud.rb:
Line: uri = "http://169.254.169.254/1.0/meta-data/instance-id/"

File: ./bosh_agent/lib/bosh_agent/infrastructure/aws/registry.rb:
Line: INSTANCE_DATA_URI = "http://169.254.169.254/1.0"

If you have any questions or concerns please do let me know.

Cheers!
Deependra

Delete all compilation VMs at once

I just noticed that if I have 10 compilation VMs running and my update/canary settings are for 4 VMs, then the VMs are only killed and thrown away in batches of 4. This is slow.

Could we change this to delete all compilation VMs at the same time?

Unresponsive agent on OpenStack

Yesterday I deployed bosh on openstack with microbosh. Today some agents are in a unresponsive state.

+-----------------+--------------------+---------------+-----+
| Job/index       | State              | Resource Pool | IPs |
+-----------------+--------------------+---------------+-----+
| unknown/unknown | unresponsive agent |               |     |
+-----------------+--------------------+---------------+-----+

When sshing into this vm (using ssh and key from inception machine) I find the following logs in /var/vcap/bosh/log/@4000000051443c8a01cb1564.s

2013-03-16_09:33:51.90727 #[27888] INFO: Starting agent 1.5.0.pre2...
2013-03-16_09:33:51.90734 #[27888] INFO: Configuring agent...
2013-03-16_09:33:51.91753 #[27888] INFO: Configuring instance
2013-03-16_09:33:51.92985 #[27888] INFO: got user_data: {"registry"=>{"endpoint"=>"http://10.200.7.4:25777"}, "server"=>{"name"=>"vm-bdac4582-c6b1-4e72-8a8e-c88fdb7aa298"}, "dns"=>{"nameserver"=>["10.200.7.4"]}}
2013-03-16_09:33:52.01479 #[27888] INFO: loaded new infrastructure settings: {"vm"=>{"name"=>"vm-bdac4582-c6b1-4e72-8a8e-c88fdb7aa298"}, "agent_id"=>"62b7a9a2-63bd-4906-a81e-62d6c6e9b190", "networks"=>{"default"=>{"type"=>"dynamic", "cloud_properties"=>{"security_groups"=>["microbosh-openstack", "bosh-openstack"]}, "dns"=>["10.200.7.4"], "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda", "ephemeral"=>"/dev/vdb", "persistent"=>{}}, "env"=>{}, "ntp"=>[], "blobstore"=>{"plugin"=>"simple", "properties"=>{"endpoint"=>"http://{ip}:25250", "user"=>"agent", "password"=>"agent"}}, "mbus"=>"nats://nats:nats@{ip}:4222"}
2013-03-16_09:33:52.01604 #[27888] INFO: Loaded settings: #<Bosh::Agent::Settings:0x00000000d0f8b8 @settings={"vm"=>{"name"=>"vm-bdac4582-c6b1-4e72-8a8e-c88fdb7aa298"}, "agent_id"=>"62b7a9a2-63bd-4906-a81e-62d6c6e9b190", "networks"=>{"default"=>{"type"=>"dynamic", "cloud_properties"=>{"security_groups"=>["microbosh-openstack", "bosh-openstack"]}, "dns"=>["10.200.7.4"], "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda", "ephemeral"=>"/dev/vdb", "persistent"=>{}}, "env"=>{}, "ntp"=>[], "blobstore"=>{"plugin"=>"simple", "properties"=>{"endpoint"=>"http://{ip}:25250", "user"=>"agent", "password"=>"agent"}}, "mbus"=>"nats://nats:nats@{ip}:4222"}, @cache_file="/var/vcap/bosh/settings.json">
2013-03-16_09:33:52.02420 #[27888] WARN: no ntp-servers configured
2013-03-16_09:33:52.02466 #[27888] INFO: Swapon partition /dev/vdb1
2013-03-16_09:33:52.02854 swapon: /dev/vdb1: swapon failed: Device or resource busy
2013-03-16_09:33:52.02979 /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_common-1.5.0.pre2/lib/common/exec.rb:62:in `sh': command 'swapon /dev/vdb1' failed with exit code 255 (Bosh::Exec::Error)
2013-03-16_09:33:52.02998   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/bootstrap.rb:184:in `setup_data_disk'
2013-03-16_09:33:52.03000   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent/bootstrap.rb:48:in `configure'
2013-03-16_09:33:52.03003   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent.rb:100:in `start'
2013-03-16_09:33:52.03005   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/lib/bosh_agent.rb:79:in `run'
2013-03-16_09:33:52.03007   from /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre2/bin/bosh_agent:96:in `<top (required)>'

cloudfoundry / bosh Goto Github PK

bosh's Introduction

BOSH

Quick start

See also

Contributions

bosh's People

Contributors

Stargazers

Watchers

Forkers

bosh's Issues

Stemcell info

Error:

Stemcell info

bosh stemcells

Error:

bosh deploy

Observed:

Recommend Projects

Recommend Topics

Recommend Org