Few bugs were fixed on 3068.

Hi Dmitriy, Is "export release" considered stable in 3042? Thanks, Mike

Thanks much..I will try and let you know how it goes

Sorry, It did mention AWS. Not sure how /path/to/iaas-settings.yml should look like, any reference? thanks. iaas-settings.yml spiff merge \

We just recently introduced compiled releases feature. I have not had a chance to document it yet, but in short it allows you to: bosh export release cf/215 ubuntu-trusty/2068 on one Director and

It's a bit unclear to me if you are proposing to security groups feature in the Director or in the OpenStack CPI specifically. If in the OpenStack CPI, then I think it makes sense to pull in

during bosh deploy..

Actually It does.

Thanks, but this document does not mention how to deploy diego to AWS using bosh. 2015-09-10 9:08 GMT+08:00 jinsenglin <jinsenglin(a)iii.org.tw>:

https://github.com/cloudfoundry-incubator/diego-release FYI

Do you when using bosh-init or during bosh deploy?

Is there anyway to reduce CF/BOSH package compilation time during deployments? It is taking roughly 15 minutes for each ..Just wanted to check if we have any option to pre compile once and use it

Would look forward to seeing this go through, it relates to a previous thread from early this year - https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/LJ2Kym6QCak. It fell off my

Hi, there I've deployed CloudFoundry 212 on AWS using BOSH, now I want to deploy Diego release using BOSH, but I have no idea how to generate the diego manifest file, anyone has such experience? Any

Dear Boshers, we currently encounter a problem which has been discussed briefly before on the list [1]: Adding security groups in resource pools should be possible. On a side note: we are dealing

Great Ramesh..

Hello All, I have a resource pool , let say small_z1 - name: small_z1 network: cf1 stemcell: stemcell-xyz cloud_properties: instance_type: m1.small availability_zone:

I finally figured it out. It is my bad, I missed the properties.uaa.jwt.signing_key/verification_key in my manifest. It is something I thought I took care of it, but must have overwritten in

Try after "bosh cck" and again re-deploy it.. Most of the Times it will work..

You can create a gist of manifest from github and link it here.