[openstack-dev] [cue] PTL candidacy

2016-03-19 Thread Min Pae
I am submitting myself as a candidate as Cue PTL for the Newton cycle.

I have been involved in the Cue project since its inception and would like
to help continue its development to make it a production ready message
broker provisioning/management service.

Some things I’d like to work on for Newton:

- Improve reliability of the broker cluster creation process
- Improve monitoring of broker instances to detect failures in broker
cluster members
- Introduce healing functions for recovering failed clusters

As a stretch goal I would also like to see a second broker type be
introduced alongside RabbitMQ, as Cue was never intended to be a "RabbitMQ
vending machine”.

Thank you,
- Min Pae
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Cue] PTL Candidacy

2015-09-16 Thread Vipul Sabhaya
Hello,

This will be the first official PTL election for Cue, and I would be
honored to serve another term leading the project for the M Cycle.

Cue is a relatively new project in Openstack, and was approved into the Big
Tent during Liberty.  I have been involved with Cue from the beginning,
from initial POC to having a product that is production worthy.  In my past
life, i’ve been a member of the Trove Core team.

During the Liberty Cycle, Cue has become a solid product with a control
plane that can manage per-tenant RabbitMQ Clusters.  We spent a lot of time
beefing up our tests, and boast >90% unit test coverage.  We also added
Tempest tests, and Rally tests, including gating jobs for both.  Our
documentation has also been revamped considerably, and allows new
contributors to ramp up quickly with the project.

During the M cycle, I would like to focus on building a community and
getting additional contributors to Cue.  I would also like to focus the
team on multi-broker support, including adding Kafka as a broker that is
managed by Cue.

I believe Cue has come a long ways in a short time, and going forward have
the opportunity accelerate the growth in terms of features, quality, and
adoption.

Thanks for your consideration!
-Vipul
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev