Hello, Deploying CF using the minimal-aws.yml is failing in Started compiling packages Started compiling packages > rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4 Started

Hey Jim, All officially supported CPIs currently come built-in *and* also come as CPI releases. CPI releases can be used with bosh-init and the Director. Take a look

I see this error too /var/vcap/sys/log/cloud_controller_worker_ctl.log {"timestamp":1435092330.8114371,"message":"No file found for the

no luck yet. Below are the logs i found which seems be errors. You can find my minimal-aws.yml @ http://fpaste.org/235921/14350920/ ------------ STARTING cloud_controller_ng_ctl at Tue Jun 23

Guys here is the second post, this time featuring the new bosh-init CLI. Any feedback from the community will be great, let me know your experience!!! Check it here:

Thanks a million Pablo for the response. Let me give this a try. Sincerely, Dulanjalie palonsoro(a)gmail.com> wrote: -- Dulanjalie

Having a look at your cloud_controller_worker_ctl.log file, the error seems to happen at the default buildpacks installation process. This typically comes from an issue with the cloud controller

Checkout https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-infrastructure-aws.yml Even provision isn't needed after the initial run. Go to the cf-boshworkspace...there will be

Hi Dmitriy Sorry to bother you. If my understanding is correct, all the documents [1] are based on the usage of "built-in CPI". I also found two examples of "external CPI" implementation [2][3]. My

Thanks Dmitriy. Guillaume. wrote:

Hi all,  I see that BOSH should re create VMs that are not responding, is it possible to replicate this feature on bosh-lite with warden containers? Thanks Regards, Michael **************** Per

Some more error messages ------------ STARTING cloud_controller_clock_ctl at Tue Jun 23 04:58:50 UTC 2015

I am seeing this error. I am checking other logs =======================cloud_controller_worker_ctl.err.log============================== rake aborted! SignalException:

Don t think is an error, please check all files. wrote:

dmitriy reads this list and hangs out in the #bosh irc channel [1]. the softlayer cpi is an example of an external cpi that can be used with bosh init, so you could probably look at how that one

Hi James Thanks for your update. Here are my findings about External CPI: 1. Tracker: https://www.pivotaltracker.com/n/projects/1133984 2. External API for SoftLayer:

thanks for doing the research danny! please let us know if you try working on this. we'll definitely try and help if you get stuck. wrote: -- Thank you, James Bayer

i am hitting an error when i execute bosh deploy in minimal-aws.yml based cf deployment. Failed updating job api_z1 > api_z1/0 (canary): `api_z1/0' is not running after update (00:12:11) Error

Code seems to be bit overwhelming. Can you suggest some pointers to study 1. networking among containers? For example I am interested of adding a different switch. 2.where the AWS api's are called.

We have plans to add s3 compatible blobstore support to bosh-init, similarly to how Director supports swift since it's s3 compatible blobstore; however, it's not that high on the priority list since