bosh-init needs BOSH release for CPI you want to use. Unfortunately, at this moment there is no CPI BOSH release for OpenStack, at least I don't know about it. There is nothing in BOSH repo and http:/

Cool, thank you. Will try it out this week. ------------------------ Alex Lomov *Altoros* — Cloud Foundry deployment, training and integration *Twitter:* @code1n <https://twitter.com/code1n> *GitHub:*

Hey, all. I just deployed MicroBOSH to openstack. Here is a manifest that I used [1]. @Dmitry, I needed to make some more changes than manifest in docs use to have: for instance I needed to add `nats.

Just added a PR for this case: https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/pull/3 ------------------------ Alex Lomov *Altoros* — Cloud Foundry deployment, training and integr

We had the similar issue with AWS. In AWS pannel we couldn't find any instance that used some IP address, still there was no ability to create an instance with such IP. We got this bug after we redepl

Dmitry, could you please tell what's the problem with bosh-init? Because currently I see a similar problem and I thought that it happens in CPI or IaaS. Is there any description / ticket / issue ? ---

Hi, Daniele. I suppose you use bosh-init [1] to deploy MicroBOSH [2]. MicroBOSH is a full functional BOSH installation in bounds of one instance, still has its limitations. It is a common way to deplo

I don’t think that v213 is suitable cf-release for you. It was a notice about its fails [1]. My colleagues are playing around v212, and I have rather stable deployment of v207. [1] http://lists.cloudf

It seems that nabble eats your text from console. Could you please provide us with stack trace of this error? I’m sure you can find it in a CPI log.

It would be easier to find out what’s the problem if you’ll provide stack traces of this error. It would be great if you to share both director and CPI stack traces. Talking about environment, I am no

Hi, all. I think that you should know this problem: you shouldn’t run bosh-init with Ruby 1.9.3 installed on your VM. The problem is that bosh-init uses host ruby to render era templates from bosh rel

The short answer is “yes”. Yes, BOSH blocks the whole deployment while you run errand [1]. As far as I see, the main reason hear is consideration that BOSH errand job can perform operations on deploym

Could you please tell more about plan of consolidating stemcell? As far as I can see stemcell tends to be a IaaS dependent part of BOSH and each infrastructure should have its own agent.json. Otherwis

Could you tell what is an output of `bosh task <snapshot-task-number> --debug` command? I have seen the same issue, I was able to run snapshot command, but logs contain the error. Also it is possible

That’s right, I also used vmware cpi. This CPI does not have disk_snapshot function [1]. I raised this question here [2]. You get the number of a task in output of your bosh command. Try to run the co