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 with

Dear Dmitriy, thanks for the quick reply. See my response inline.

Hi Dies, I agree that the registration at an external ELB would be very helpful to have – just like it is done for AWS. We currently use the HAProxy, so I guess this is a challenge which will hit us a

Dear Fabian, your problem might be the same as seen in this github issue: https://github.com/cloudfoundry/bosh/issues/964<https://github.com/cloudfoundry/bosh/issues/964#event-420594944> `bosh ssh` se

Supposedly something like this should work: http://bosh.io/docs/vm-anti-affinity.html#openstack This involves in configuring server groups with anti-affinity enabled on Openstack before actually deplo

In case you have been following this discussion: security group definitions in the cloud_properties of resource pools available in the openstack-cpi-release v16 https://github.com/cloudfoundry-incubat

Hi all, in case you use bosh on OpenStack you might want to use the Keystone v3 API which introduces Domains. I’m happy to announce that you can use Keystone v3 with bosh >=v218 and openstack-cpi >=v1

Dear Dimuthu, bosh micro is deprecated. If you are starting out with a fresh installation of bosh, please use bosh-init [1] instead. That being said, if you want to continue the path for `bosh micro`:

Dear Dimuthu, please make sure that your OpenStack environment is configured correctly and that you can access any machine booted up with a floating IP from your machine. You can follow the descriptio

Thanks, that looks like some really nice changes included there! One thing I'm not so sure about is how stdout and stderr are redirected to the same file now. Shouldn't we try to harmonize this someho

As I said: It is not so much about which way is better, it is more about having less things to think about. With the right arguments you might be able to convince the MEGA team to accept a PR to log i

Hi, using a UID 900 will build you the stemcell, but it won't work correctly. The VCAP user home on the stemcell will have the wrong owner and you won't be able to deploy anything succesfully with it.

Hi, thanks for the reminder of the current deficiencies in the land of Bosh/Cloud Foundry and OpenStack. :) Cloud Foundry is known to work on the newer OpenStack Releases as well. We have an installat

The most recent information I know is available in the bosh.io docs [1] and mentions Havana, Icehouse, and Juno. [1] http://bosh.io/docs/init-openstack.html#prepare-openstack Warm regards Marco

Dear Boshers, if you're not using OpenStack, you can skip this message. For all of you, who *are* using OpenStack: We have just released the OpenStack CPI v23 with two great features! Human-readable V

Dear Boshers, if you're not using OpenStack, you can skip this message. For all of you, who *are* using OpenStack: In the Bosh OpenStack CPI team, we've created a Terraform [1] template to setup your

Hi, thanks for trying the feature and your feedback. Is this a new setup or did you upgrade your Director from a previous version? If it is an upgrade, did you have CF already deployed previously? For

Dear Aaron, please make sure that when you use bosh-init to deploy BOSH that you also enable the `human_readable_vm_names` and `registry.endpoint` in you full-bosh manifest. In terms of this feature t

Dear Aaron, can you please file a bug at https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release and include a redacted version of the deployment manifest you're using to deploy the full-

Hi Muhammad, So what you did was `bosh-init delete` followed by `bosh-init deploy`? Did the previous Director already have Cloud Foundry deployed? Are you sure that new VMs got created when you deploy