Looks like the openstack endpoint DNS name is not resolved from the local box. Have you checked against typo in the yml config ? There is a bosh micro log file which may provide additional traces. Is

Hi, I understand that by default the micro-bosh has DNS enabled (i.e. hosts a powerDNS servers that gets injected by default in all VMs it manages). If the dns entry [1] is specified, additional DNS r

Thanks a lot Pablo Alonso for your response and for your analysis that microbosh DNS is always placed at end of the resolv.conf and hence should not harm bosh resolution w.r.t. explicitly configured D

Hi Jim, Until the bosh contributors get you an official doc, here are some pointers I collected while studying the development of an external CPI [1] - Stdin/stdout API wiki <https://github.com/cloudf

Following up onto https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-users/8mN2vl8rTPc/WX3JQCfeY_8J The https://bosh.io/releases is a great place to have a packaged tarball for releases, and the

Hi, The bosh-init combo manifest requires stemcell SHA to be specified [1] along with a url, and I understand bosh-init would download by itself the stemcell and check the SHA. However, the current st

Thanks Dmitriy. Guillaume. wrote:

Hi Dmitry, Is there official documentation of the external CPI contract ? I had noticed a draft [1] you mentionned on bosh-dev@ a while ago. An official doc will be quite helpful as a complement to ex

Thanks a lot Dmitriy, this is very useful to have this addtional level of documentation. Guillaume. wrote:

Hi, I'm wondering whether there are plans to add meta-data to bosh release manifest, as to support better discoverability of bosh releases. The bosh hub is providing a great one shop place to find bos

Great, thanks a lot Dmitriy, this sounds great. Looking forward to seeing bosh.io leveraging these meta data to help filter/sort/search releases. Guillaume.

Dmitry, Besides the great CPI V1 doc (for which I proposed refinements in [4]), I notice you have planned a future page "Interactions between CPIs and BOSH Agent" in the TOC. I have few questions that

Hi, The service broker api great to provide access to a common catalog (e.g. mysql, cassandra...). I understand private service brokers [3] will enable to extend the marketplace per space or per org (

oups, sorry wrong list, meant to send it to cf-dev@, will repost. Guillaume.

Another use-case for such meta-data might be for a bosh release to specify minimum bosh and stemcell supported versions (similar to what cf-release release notes document informally, sometimes upon us

Thanks a lot Amit for the heads up and the very interesting description of the work on the "certified deployments". I had once imagined to add in in the release meta-data the url to the ci build that

Hi, I'm trying to assign cc.info.description and cc.info.version [1] (to merge meta.releases[0].version if cf release version), as to be able to describe to end users which cf version is currently dep

ooups wrong list again, sorry about that, reposting to cf-dev@ Guillaume.

Hi, Can the following bosh release please be included in bosh.io [1] ? From Orange: https://github.com/Orange-OpenSource/elpaaso-sandbox-boshrelease Plus some other releases hoping their authors to be

Hi Dmitriy, Are you still planning to propose a config/final.yml with metadata that bosh.io could render ? Should we instead continue this over the bosh-notes repo ? Thanks in advance, Guillaume. wrot