Hi Jun and Marco, If the huawei team plans to provide differentiated features beyond what the openstack CPI provides, it seems useful that the openstack CPI team provides some feedback on whether the

Hi Jun, Thanks for your additional precisions. If I understand you correctly: - both huaweicloud.com and huawei powered clouds such as Orange Flexible Engines (or others such as DeutchTelecom cloud an

Hi Jun, Thanks for your response. > If you are familiar with OpenStack, you can still choose to use openstack CPI. > If you are familiar with Huawei cloud console, we recommend using HuaweiCloud CPI.

Hi Jun, It's great to see Huawei team contributing to the CloudFoundry community! I work for Orange which has been running CloudFoundry on various openstack distributions using the openstack CPI for m

Hi, Following Amit's suggestion, I'm reposting here the question I had on the "Proposal Bosh-aware DNS server" at [3] to get more bosh eyes on it: Could the rationale for moving out of a standard DNS

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

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

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

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

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

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

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

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 (

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

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.

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

Thanks a lot Dmitriy, this is very useful to have this addtional level of documentation. 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 Dmitriy. Guillaume. wrote:

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