thank you for kind words. it's definitely been a fun adventure! > Wait, I guess stepping down as the PMC lead does not mean he's stepping down as the lead in the various bosh projects he leads, right?

Thank you for submitting this proposal. Let's shoot for collecting and resolving most of the comments in the next month by Aug 10th and voting at that time to incubate it in BOSH PMC.

you also can try using iam instance profiles (http://bosh.io/docs/aws-iam-instance-profiles/) (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html)

i imagine you would want to provision access key pair in the subaccount (not in the main account) and use that to provision resources in the subaccount. > Also I miss the possibility to use Multi-Fact

we are actively working on xenial stemcells. hoping that we ll be cutting beta stemcell versions soon. getting them into pcf as a default is an additional matter of time. dm me (@dkalinin) on cloudfou

it fails most likely due to this: https://github.com/cloudfoundry/bosh-agent/blob/master/agent/script/drain/concrete_script.go#L157 wrote:

currently bosh only relies on stdout of the script to determine success. given this historic behaviour its a bit hard to migrate to exit code paradigm (similar to our other scripts) without unintentio

we havent spent any time optimizing it since it shuold be pretty cheap to make these calls. are you concerned about the perf aspect of it or something else? wrote:

you might have to update your cloud config with one that cf-deployment wants: bosh -e 192.168.50.6 ucc <(wget -O- https://raw.githubusercontent.com/cloudfoundry/cf-deployment/master/bosh-lite/cloud-co

hey, we currently have two separate cpi methods for creating vms (create_vm) and setting metadata on the vms (set_vm_metadata). create_vm call does not receive necessary metadata to apply tags to the

if vcloud cpi allows to specify root disk size this might be one way to bypass this problem. wrote:

+cf-dev

hey all, as some of you may know, we have been recently recommending to install bosh lite via cli v2 instead of vagrant. we haven't found any serious drawbacks to the new approach so i would like to r

director does not support interpolation within interpolation. this example seems to be very specific. are you trying to do cred rotation? Sent from my iPhone

i think adding this ops file will help: https://github.com/cloudfoundry/bosh-deployment/blob/master/misc/proxy.yml Sent from my iPhone

no reasons yet to believe it isnt as far as i know. Sent from my iPhone

identifier. if variables section contains a variable name, the director will try to ask credhub to generate value if one doesnt exist. sounds about right. manifest file for the identifier then no POST

im sure there is going to be one very soon but here is a commit on diego-release that makes it optional configuration for a trial run ( https://github.com/cloudfoundry/diego-release/commit/27ee06ecdfc

manifest would contain credential identifiers. Sent from my iPhone

there is `bosh envs` command to list what environments were aliased ( http://bosh.io/docs/cli-v2.html#env-mgmt). wrote: