[openstack-dev] [election][tc] Announcing candidacy

Rico Lin rico.lin.guanyu at gmail.com
Fri Sep 7 17:17:12 UTC 2018

On Fri, Sep 7, 2018 at 9:21 PM Matt Riedemann <mriedemos at gmail.com> wrote:

> On 9/6/2018 1:49 PM, Rico Lin wrote:
> > * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV)
> Are there some specific initiatives or deliverables you have in mind
> here, or just general open communication channels? It's very hard to
> gauge any kind of progress/success on the latter.

I'm refering on clear communication channels and go from Use cases to real
development tasks (As I try to explain in the last section of my candidacy).
And here's some specific initiatives or deliverables sample I got in mind.
* From StarlingX, some great improvement for Edge cases are delivered to
projects. And there're also communications cross StarlingX and TCs on how
to make it integrated with rest OpenStack projects (currently StarlingX
still using it's own forks of OpenStack projects). And there're other
projects that other organizations contribute to OpenStack or form another
communities that depend on OpenStack.
* We recently create a new repo `openstack-service-broker` [1]. Use Service
Broker (A project from CloudFoundry) expose external resources to
applications running in a PaaS. Which is exactly a integration cross
CloudFoundry and OpenStack (protentially with K8s too) base on specific
* K8s as one of the most popular case here, I believe we already can see
some nice integration cross OpenStack and K8s. Include Manila, Keystone
support in K8s, Magnum become one of official deployment tool in K8s
community. Also I'm currently working on Integrate Heat AutoScaling to K8s
cluster autoscaler as well [2].
* OPNFV integrated with OpenStack as it's cluster provider.

So the goal here IMO is `how can we properly set up cross communication and
improve scenarios with use cases or help these scenarios to become
deliverable for user?`.
SIGs are one of the format that I believe can help to accelerate this goal.
As I mentioned in [3] and in goal `Strong the structure of SIGs`. We should
consider to allow SIGs to become that platform from use cases and scenario
to a trackable development tasks. I know there's nothing block a SIG to do
so, but there's also no guideline, structure format, or other resources to
make the path easier for SIG.

Hope these explains wht the goal is in my mind.

[1] https://github.com/openstack/openstack-service-broker
[2] https://github.com/kubernetes/autoscaler/pull/1226
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180908/60f5abe3/attachment.html>

More information about the OpenStack-dev mailing list