Hi Guillaume,

All I said that network model APIs changes or how to choose CPI are about Huawei Public Cloud itself, not Huawei cloud powered Orange Flexible Engine.

Thanks

JUN

2018-08-25 0:13 GMT+08:00 Guillaume Berche <bercheg@...>:

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.

I'm not sure to understand how familiarity with cloud console relates to which CPI flavor to choose.

Can you please clarify what additional features would usage of huaweicloud CPI would provide w.r.t. straight usage of openstack CPI to access Huawei Public Cloud itself or Huawei cloud powered Orange Flexible Engine?

Thanks in advance,

Guillaume.

On Fri, Aug 24, 2018 at 11:43 AM jun zhong <jun.zhongjun2@...> wrote:

Hi  Marco,  Guillaume,

@Marco, Thanks for your arrangement.

@Guillaume

Yeah, The OpenStack CPI is work on Huawei cloud powered Orange Flexible Engine, but the

HuaweiCloud CPI is work on Huawei Public Cloud itself[1]. There are differences between the HuaweiCloud

console and OpenStack API models, some users are not aware of the relationship between them,

and it is difficult for people who are familiar with the console.

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.

We changed the part of code about network mode in huaweicloud CPI [1],

we use our own network mode APIs instead of openstack newtork mode APIs,

and the Port is not required for HuaweiCloud, the new property is 'subnet_id', and so on.

[1] https://www.huaweicloud.com/

[2] https://github.com/zhongjun2/bosh-huaweicloud-cpi-release/pull/8/files

Thanks

JUN

2018-08-21 23:43 GMT+08:00 Marco Voelz <marco.voelz@...>:

Dear JUN,

 

Thanks for the proposal. I'm asking everyone for feedback until August 31^st: Make yourself heard, start discussions and make sure to ask the questions you have until that deadline. If there are no outstanding major discussion points, we will proceed with voting for incubation in the week after that.

 

Warm regards

Marco

 

From: <cf-bosh@...g> on behalf of jun zhong <jun.zhongjun2@...>
Reply-To: "cf-bosh@...g" <cf-bosh@...g>
Date: Tuesday, 21. August 2018 at 11:20
To: "cf-bosh@...g" <cf-bosh@...g>
Subject: [cf-bosh] Incubation proposal: HuaweiCloud CPI

 

Hi all,

We want to propose the HuaweiCloud CPI for incubation in the BOSH PMC.
https://lists.cloudfoundry.org/g/cf-bosh/message/2532?p=,,,20,0,0,0::Created,,Huaweicloud,20,2,0,23810700 

The HuaweiCloud Bosh CPI [1] and configuration items for bosh [6] and cf [7] is ready now.  The Bosh HuaweiCloud CPI is used in our internal product.

 

We also add CI testing (CF HuaweiCloud Validator[3] [4] and BOSH Acceptance Tests (BATS)[2] ) to check if Huaweicloud CPI is ready to run BOSH and install

Cloud Foundry. The CI result will be displayed in each Huaweicloud CPI PR [5].

 

 

[1] https://github.com/zhongjun2/bosh-huaweicloud-cpi-release/

[2] https://github.com/liu-sheng/openlab-zuul-jobs/blob/master/playbooks/bosh-acceptance-test-huaweicloud/run.yaml

[3] https://github.com/liu-sheng/openlab-zuul-jobs/blob/master/playbooks/bosh-huaweicloud-cpi-release-acceptance-test/run.yaml

[4] https://github.com/zhongjun2/cf-huaweicloud-validator

[5] https://github.com/zhongjun2/bosh-huaweicloud-cpi-release/pull/3

[6] https://github.com/zhongjun2/bosh-deployment

[7] https://github.com/zhongjun2/cf-deployment

The project would follow a distributed committer model.

Project Lead: Edward Lee
Initial Committers:
- ZhongJun (Huawei)
-Tommylikehu ( Huawei )

- LiuSheng  ( Huawei )

We are looking forward to your questions and comments.

Thanks,
JUN