Resending due to mailman issues: Looks like you may not be doing what you think you're doing. I'm not sure where you got those commands from but they are unrelated to bosh-lite. You're basically bring

I noticed that the new CAPI team has published a v3 API style guide for folks to comment on [1]. I don't know how much the CAPI team expects it to change but it's probably worthwhile for those who hav

The buildpack set event is, essentially, a metadata event. It records the buildpack that was used to stage an application. This information could not be included in the started event because staging h

The old vcap-dev mailing list had a number of exchanges around this topic that you might want to look at. The basic gist is that linux gives processes that are not associated with a cgroup a cpu share

Hi. This isn't what I expected. You've basically changed the bucket configuration to point to your own and uploaded the blobs to that bucket. That's why bosh is telling you there's nothing to upload.

As Maggie and Dieu have said, the `running_instances` field from the "summary" endpoint the cli is using reflects hm9k view of the world and the `state` field represents the desired state of the app.

Since you won't be able to upload the blobs to the cf-release bucket, I'd suggest you capture the output of `bosh blobs` in your pull request. That command should enumerate all of the new blobs and th

Thanks for the feedback. I'll let others comment on the bosh aspects other than to say that we are expecting people to use spiff to generate the manifests and that the decision to namespace properties

You may need to supply your access log from the nginx in front of cc or the cc log because when I create a new buildpack, it's working just fine: $ CF_TRACE=true cf create-buildpack test-binary-bp ./b

It should work since our acceptance tests validate this on every build we cut [1]. Are you running the operation as someone with a cc admin scope? If you want to create a gist with the log (with secre

Depends on your role and where your app is in the deployment pipeline. Most of the scenarios I envisioned were for the tail end of development where you need to poke around to debug and figure out tho

My concern is the default behavior. When I first prototyped this support in February, I never expected that merely accessing a container would cause it to be terminated. As we can see from Jan's respo

The vcap-dev list used to use a Reply-To header pointing back to the list such that replying to a post would automatically go back to the list. The current mailman configuration for cf-dev does not se

Warden explicitly disables access to the container host. If you move up to a more recent level of cf-release, that behavior is configurable with the `allow_host_access` flag. When that flag is true, t

Not that I'm aware of That said, you can control the maximum memory an instance can allocate and you can control the maximum memory in the quota. It's not the same but it may be something you can leve

The reported statistic is calculated here: https://github.com/cloudfoundry/dea_ng/blob/310797e1097dcd5531bff4077ccd8f02f6091219/lib/dea/stat_collector.rb#L92-L94 daniel.jones(a)engineerbetter.com> wro