[openstack-dev] [Congress] PTL candidacy
Hi all! I¹m writing to announce my candidacy for Congress PTL (Ocata). First, I¹d like to thank Tim for his outstanding leadership since the very beginning of the project. Under his leadership, Congress has grown from an interesting idea to a capable service. I would also like to thank everyone for their tremendous support in bringing me along as a Congress contributor, from first learning the codebase to leading the high-availability design and implementation efforts. I¹m truly grateful to be a part of such a welcoming, collaborative and supportive community. For the Ocata cycle, my main focus for Congress is usability and ease-of-adoption. For example, by shipping Congress with pre-built policies and templates, Congress would provide useful policy-based monitoring fresh out-of-the-box, its time-to-value improving from weeks to under a day. I also aim to continue prioritizing user engagement, cross-project collaboration, and code robustness. Last but not least, I look forward to supporting our project members in their goals and visions for Congress. Thank you all once again! -- Eric J. Kao __ 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] [Congress] PTL candidacy
Hi all, I'm writing to announce my continued candidacy for Congress PTL. In the Mitaka cycle we've been working hard and making great progress on a number of things. The largest change is a new distributed architecture built on top of oslo-messaging. That architecture is key to enabling us to meet the high-availability and high throughput demands that we've heard from the field. We also saw the first new mechanism since the project's inception for injecting data into Congress, so that external systems can push data, instead of Congress pulling it. In Mitaka, we also completed the transition to Python3, and implemented the plugin interface for both tempest and devstack. It's also exciting that over the last two cycles, we have seen longer-term commitments to Congress from the community, with 1 new core reviewer this cycle, and two other incredibly active contributors. In Newton, my primary technical goal is to complete the migration to our new distributed architecture. I also hope to have Congress leverage that new architecture to provide high-availability and high-throughput solutions. I plan to continue discussions with other projects to understand how and where Congress can be useful. Finally, I'm looking forward to stengthening the developer community around Congress. Tim __ 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
Re: [openstack-dev] [Congress] PTL candidacy
+1 Tim is an excellent and passionate leader, go ahead, Congress :-) 2015-09-17 4:09 GMT+08:00 : > +1 and looking forward to see you in Tokyo. > > > > Thanks, > > Ramki > > > > *From:* Tim Hinrichs [mailto:t...@styra.com] > *Sent:* Tuesday, September 15, 2015 1:23 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* [openstack-dev] [Congress] PTL candidacy > > > > Hi all, > > > > I’m writing to announce my candidacy for Congress PTL for the Mitaka > cycle. I’m excited at the prospect of continuing the development of our > community, our code base, and our integrations with other projects. > > > > This past cycle has been exciting in that we saw several new, consistent > contributors, who actively pushed code, submitted reviews, wrote specs, and > participated in the mid-cycle meet-up. Additionally, our integration with > the rest of the OpenStack ecosystem improved with our move to running > tempest tests in the gate instead of manually or with our own CI. The code > base matured as well, as we rounded out some of the features we added near > the end of the Kilo cycle. We also began making the most significant > architectural change in the project’s history, in an effort meet our > high-availability and API throughput targets. > > > > I’m looking forward to the Mitaka cycle. My highest priority for the code > base is completing the architectural changes that we began in Liberty. > These changes are undoubtedly the right way forward for production use > cases, but it is equally important that we make Congress easy to use and > understand for both new developers and new end users. I also plan to > further our integration with the OpenStack ecosystem by better utilizing > the plugin architectures that are available (e.g. devstack and tempest). I > will also work to begin (or continue) dialogues with other projects that > might benefit from consuming Congress. Finally I’m excited to continue > working with our newest project members, helping them toward becoming core > contributors. > > > > See you all in Tokyo! > > Tim > > > > __ > 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 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
Re: [openstack-dev] [Congress] PTL candidacy
+1 and looking forward to see you in Tokyo. Thanks, Ramki From: Tim Hinrichs [mailto:t...@styra.com] Sent: Tuesday, September 15, 2015 1:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Congress] PTL candidacy Hi all, I’m writing to announce my candidacy for Congress PTL for the Mitaka cycle. I’m excited at the prospect of continuing the development of our community, our code base, and our integrations with other projects. This past cycle has been exciting in that we saw several new, consistent contributors, who actively pushed code, submitted reviews, wrote specs, and participated in the mid-cycle meet-up. Additionally, our integration with the rest of the OpenStack ecosystem improved with our move to running tempest tests in the gate instead of manually or with our own CI. The code base matured as well, as we rounded out some of the features we added near the end of the Kilo cycle. We also began making the most significant architectural change in the project’s history, in an effort meet our high-availability and API throughput targets. I’m looking forward to the Mitaka cycle. My highest priority for the code base is completing the architectural changes that we began in Liberty. These changes are undoubtedly the right way forward for production use cases, but it is equally important that we make Congress easy to use and understand for both new developers and new end users. I also plan to further our integration with the OpenStack ecosystem by better utilizing the plugin architectures that are available (e.g. devstack and tempest). I will also work to begin (or continue) dialogues with other projects that might benefit from consuming Congress. Finally I’m excited to continue working with our newest project members, helping them toward becoming core contributors. See you all in Tokyo! Tim __ 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
Re: [openstack-dev] [Congress] PTL candidacy
+1 And see you all in Tokoyo – If I could get my visa on time☺! BR Zhou Zhenzan From: Tim Hinrichs [mailto:t...@styra.com] Sent: Wednesday, September 16, 2015 04:23 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Congress] PTL candidacy Hi all, I’m writing to announce my candidacy for Congress PTL for the Mitaka cycle. I’m excited at the prospect of continuing the development of our community, our code base, and our integrations with other projects. This past cycle has been exciting in that we saw several new, consistent contributors, who actively pushed code, submitted reviews, wrote specs, and participated in the mid-cycle meet-up. Additionally, our integration with the rest of the OpenStack ecosystem improved with our move to running tempest tests in the gate instead of manually or with our own CI. The code base matured as well, as we rounded out some of the features we added near the end of the Kilo cycle. We also began making the most significant architectural change in the project’s history, in an effort meet our high-availability and API throughput targets. I’m looking forward to the Mitaka cycle. My highest priority for the code base is completing the architectural changes that we began in Liberty. These changes are undoubtedly the right way forward for production use cases, but it is equally important that we make Congress easy to use and understand for both new developers and new end users. I also plan to further our integration with the OpenStack ecosystem by better utilizing the plugin architectures that are available (e.g. devstack and tempest). I will also work to begin (or continue) dialogues with other projects that might benefit from consuming Congress. Finally I’m excited to continue working with our newest project members, helping them toward becoming core contributors. See you all in Tokyo! Tim __ 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] [Congress] PTL candidacy
Hi all, I’m writing to announce my candidacy for Congress PTL for the Mitaka cycle. I’m excited at the prospect of continuing the development of our community, our code base, and our integrations with other projects. This past cycle has been exciting in that we saw several new, consistent contributors, who actively pushed code, submitted reviews, wrote specs, and participated in the mid-cycle meet-up. Additionally, our integration with the rest of the OpenStack ecosystem improved with our move to running tempest tests in the gate instead of manually or with our own CI. The code base matured as well, as we rounded out some of the features we added near the end of the Kilo cycle. We also began making the most significant architectural change in the project’s history, in an effort meet our high-availability and API throughput targets. I’m looking forward to the Mitaka cycle. My highest priority for the code base is completing the architectural changes that we began in Liberty. These changes are undoubtedly the right way forward for production use cases, but it is equally important that we make Congress easy to use and understand for both new developers and new end users. I also plan to further our integration with the OpenStack ecosystem by better utilizing the plugin architectures that are available (e.g. devstack and tempest). I will also work to begin (or continue) dialogues with other projects that might benefit from consuming Congress. Finally I’m excited to continue working with our newest project members, helping them toward becoming core contributors. See you all in Tokyo! Tim __ 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
Re: [openstack-dev] [Congress] PTL candidacy
confirmed On Mon, Apr 6, 2015 at 1:42 PM, Tim Hinrichs wrote: > Hi all, > > I'm writing to announce my candidacy for PTL of Congress for the Liberty > cycle. We've made a lot of progress in Kilo, and I'm excited by what we'll > achieve in Liberty! To give us some perspective, I compiled a (partial) > list of improvements we made in Kilo: > > * Officially became part of OpenStack (moved from stackforge to openstack) > * Matured the Congress community (commits/LOC from outside VMware: Juno:8%, > Kilo:26%) > * Integrated with our first external project: Murano > * Improved scale-up by orders of magnitude (see > http://ruleyourcloud.com/2015/03/12/scaling-up-congress.html) > * Added the first version of reactive enforcement (correcting policy > violations after they happen) > * Created a Horizon GUI for writing policy > * Built a DSL for integrating external cloud services and enabled on-demand > (de)installation of services > > We achieved just about everything we set out to do in Kilo, thanks to the > hard work of many outstanding folks. For the Liberty cycle, I'm planning on > similar success in the following areas. > > * Production deployments > * Scale-out: enabling high-availability and increased throughput > * Delegation: enabling Congress to interoperate with other policy engines to > share the burden of policy enforcement > * Community: increasing non-VMware contributions, in terms of commits/LOC > and especially reviews > > While Congress is an early-stage project, we're on a great track, and I'll > make sure we stay on it. As always I'm happy to chat about future > directions, past progress, and anything in between. > > Thanks! > Tim > > > > __ > 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 > -- Elizabeth Krumbach Joseph || Lyz || pleia2 __ 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] [Congress] PTL candidacy
Hi all, I'm writing to announce my candidacy for PTL of Congress for the Liberty cycle. We've made a lot of progress in Kilo, and I'm excited by what we'll achieve in Liberty! To give us some perspective, I compiled a (partial) list of improvements we made in Kilo: * Officially became part of OpenStack (moved from stackforge to openstack) * Matured the Congress community (commits/LOC from outside VMware: Juno:8%, Kilo:26%) * Integrated with our first external project: Murano * Improved scale-up by orders of magnitude (see http://ruleyourcloud.com/2015/03/12/scaling-up-congress.html) * Added the first version of reactive enforcement (correcting policy violations after they happen) * Created a Horizon GUI for writing policy * Built a DSL for integrating external cloud services and enabled on-demand (de)installation of services We achieved just about everything we set out to do in Kilo, thanks to the hard work of many outstanding folks. For the Liberty cycle, I'm planning on similar success in the following areas. * Production deployments * Scale-out: enabling high-availability and increased throughput * Delegation: enabling Congress to interoperate with other policy engines to share the burden of policy enforcement * Community: increasing non-VMware contributions, in terms of commits/LOC and especially reviews While Congress is an early-stage project, we're on a great track, and I'll make sure we stay on it. As always I'm happy to chat about future directions, past progress, and anything in between. Thanks! Tim __ 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
