Thanks for giving us so many suggestions.
1b- extend the openstack cpi with additional vm_properties support that leverage Huawei custom APIs and products.
-- Different vendors have the right to choose different strategies.
We would like to choose the API or config item that really suitable for our customer.
Those APIs are not related to OpenStack, so we still want to create our new HuaweiCloud CPI in PMC.
2- build a community of huawei cloud Bosh and CF users which can share experience, best practices, and provide feedback
and improvements to the Huawei and CF Foundation teams. For example, create a "huawei" slack channel on the cloudfoundry slack .
Our team would be happy to share our experiences with running CF on Orange Flexible Engine, such as glance quota diagnostics , or VRRP issues across VPCs .
-- I would like to create a new group named "huawei" in slack channel
3- provide 1st class support to Huawei cloud on bosh director,
e.g. validate integration of Huawei Object Store Service  as a bosh director blobstore backend, and BBR backend . Contribute docs and operators into bosh-deployment similarly to other Iaas , , as well as terraform configs into bbl . Validate integration of Huawei RDS as a bosh director db backend . We should suggest to avoid fragmentation of terraform providers among huawei powered clouds     and their associated diverging github repos  , and rather try to unify them into a single provider with configureable endpoint.
4- provide 1st class support to Huawei cloud on cloudfoundry application runtime, e.g. validate integration of Huawei Object Store Service  as a CC blobstore backend and contribute associated bosh operators into cf-deployment  or best in bbl, along with terraform configs (when differing from openstack apis)
-- Is this a necessary request for new CPI? I saw some of the CPI doesn't support it now, such as: azure CPI