We had a hiccup in our CI pipeline regarding this feature. Will update as soon we have it. Sent from my iPhone

Any update on this?

We have submitted a pull request to resolve this issue. Seems the vSphere manifest generation is lagging a bit. https://github.com/cloudfoundry/cf-release/pull/795

Yes it currently uses outside ruby to generate ERB templates for the jobs. Not all CPIs include a ruby so we cannot rely on included one. wrote:

To confirm: bosh-init has a dependency outside of its own binary and dependencies inside cpi releases? <alexander.lomov(a)altoros.com> wrote:

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

FYI...we have since upgraded to v217 as well.

We made a little more progress on this and have been able to get a successful deployment with the drs_rules section in our manifest, but the rules are not being applied on the VMWare side. Here is

We recently accepted PR that had some unintentional stricter verification. To properly fix the issue we are pushing https://www.pivotaltracker.com/story/show/102530088 through the CI. This story will

It's this commit: https://github.com/cloudfoundry/bosh/commit/34eb5dce581167082af43d69c0bf38a1e263cd7b This was put in as a precursor to later allow Director to supply host fingerprints for

When I deploy microbosh now & bosh-lite, no longer does `bosh ssh` just work. Instead you get: No ECDSA host key is known for 10.10.1.11 and you have requested strict checking. But I didn't

Sorry again. Forget all about this problem. I was using an outdated version of bosh workspace and this did not checkout the latest release into releases directory. Instead it did remain in v5 state.

Sorry for confusing message. I mean this: https://admin-ui-boshrelease.s3.amazonaws.com/boshrelease-admin-ui-5.tgz (HTTP 200) https://admin-ui-boshrelease.s3.amazonaws.com/boshrelease-admin-ui-6.tgz

There was a change recently merged in and is going through the CI which adds support for IAM instance profiles. This allows CPI to retrieve credentials automatically when necessary. I'll update this

Inline Sent from my iPhone That quote is about *replacing* monit with something else, not about upgrading monit, which is what PR includes. Well understood, so I'm asking for help to confirm in a

Dmitri wrote: "When we do get to a point when it becomes a priority we will definitely share a proposal on bosh-notes with a community." We aren't asking for giggles. As Matt said, in comments, we

inline Sent from my iPhone Existing bosh pipeline does very minimal testing of monit interoperability, partly because there is no dedicated test suite that test all kinds of cases. With changes that

The monit used in the standard stem cells is ancient and there are two PRs to update it opened against bosh. I've been trying to understand what's going on by making comments on one of the PRs but I

Hi, How can AWS temporary security credentials be used with bosh in place of the access_key_id and secret_access_key? Reviewing manifests and documentation, I find no mention of aws_session_token.

I got this working. I had to do several things: 1. I had to change the default security groups assigned to the server vm so that it could be accessed by the client vm. Seems a bit odd to me that I