Re: Incubation proposal: HuaweiCloud CPI
toggle quoted messageShow quoted text
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 many years, including on the Huawei cloud powered Orange Flexible Engine  for the last 4 months. This occasionally required us to contribute fixes to the openstack-cpi or its fog dependency library .
The huaweicloud cpi's readme  mentions that enhancements (w.r.t. openstack CPI) lies in "Network: fully supporting huaweicloud network resources, including vpc, subnet, nic and so on."
I wonder where the associated documentation can be found: is there user-facing huawei specific properties that are exposed to cpi users ? I so far could only spot the example manifest into cf-deployment  and bosh-deployment [3b] forks but without apparent new properties w.r.t. openstack cpi reference doc . I therefore wonder whether the huawei cpi is indeed offering support for new features, or rather accommodating for subtle openstack api incompatibilites which could potentially be handled through either better huawei cloud openstack api conformance, or contributions to the openstack cpi to make it more flexible to API response variations (like we did in ). Huawei usa contributor was offering to help with openstack testing in  which could potentially help.
Looking at the huaweicloud cpi's code, I'm concerned to see the proposed repos (openstack CPI, openstack validator, being completely forked without apparent convergence with the openstack CPI work, and worry about maintenance of this effort in the future, and feature parity with openstack-cpi.
I wonder whether the Huawei team has yet reached out to the openstack CPI team (e.g.on slack ) to discuss support for extensions in the cpi that potential Huawei differentiated features (beyond openstack standard) could leverage (in a similar fashion that the openstack validator supports extensions ).
Thanks in advance,
On Tue, Aug 21, 2018 at 11:20 AM jun zhong <jun.zhongjun2@...> wrote: