I am Chaoyi Huang, would like to propose my candidacy for the Tricircle PTL in Newton.
I have been working on the Tricircle from day one, from the open source development since June,2015, and even from the PoC of OpenStack cascading solution. My passion to work on Tricircle is that Tricircle tries to address one area where OpenStack not touched but very important: if one tenant's VMs are deployed in multiple OpenStack instances, how is the traffic will be isolated at L2/L3 level if these VMs in same network or in different network, and how to automate it. Tricircle has been developed with a lightweight API gateway framework in Mitaka release under the effort of the team: Nova APIGW, Cinder APIGW, Neutron Tricircle plugin with reused Neutron API server and Neutron DB. Nova APIGW is the networking automation trigger for Nova APIGW is able to know exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in is responsible for cross OpenStack L2/L3 networking immediately for the new provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the same VM will co-locate in same OpenStack instances. In Mitaka, only one OpenStack in one Availability Zone is allowed, and network is limited to present only in one bottom OpenStack instance, and cross OpenStack L3 networking is established through shared VLAN. Obviously, there is still lots of things to do to achieve the goal of Tricircle: Tricircle provides an OpenStack API gateway and networking automation to allow multiple OpenStack instances, spanning in one site or multiple sites or in hybrid cloud, to be managed as a single OpenStack cloud. So the objectives which I wanted to achieve with the help of the Tricircle team in Newton release are: * Cross OpenStack L2 networking: this feature is fundamental to reach the goal of Tricircle. So this feature will be put on the first priority in Neuton release. * Dynamic pod binding: when a cloud was put into production, capacity expansion is inevitable, adding more and more already tested and verified OpenStack instances to the cloud is the easiest way of capacity expansion, this feature will also rely on the cross OpenStack L2 networking, for VM of tenant will be added to the same network after adding new OpenStack instance for capacity expansion. This feature will be on the second priority. * Tempest and basic VM/Volume operation: to make Tricircle mature enough to work, the basic VM/Volume operation features which are lack in Tricircle should be added, and using tempest to guarantee the quality of Tricircle and comply to DefCore test. This is also quite important in Newton release. And one more important one is: * Keep Tricircle follow OpenStack open source development guideline to make Tricircle project as open as any other OpenStack project, so that more and more talents would like to join and contribute in Tricircle, and target at being a big tent project of OpenStack, being member of OpenStack eco-system and help the eco-system to address the problem domain in multi-OpenStack cloud, no matter it's in one site or multi-site. Thanks for reading the mail. Best Regards Chaoyi Huang ( Joe Huang ) -----Original Message----- From: joehuang Sent: Thursday, May 05, 2016 9:44 AM To: '[email protected]'; OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]PTL election of Tricircle for Newton release Hello, As discussed in yesterday weekly meeting, PTL nomination period from May 9 ~ May 13, election from May 16 ~ May 20 if more than one nomination . If you want to be the PTL for Newton release of Tricircle, please send your self nomination letter in the mail-list. You can refer to the nomination letter of other projects, for example, Kuryr[1], Glance[2], Neutron[3], others can also be found in [4] [1]http://git.openstack.org/cgit/openstack/election/plain//candidates/newton/Kuryr/Gal_Sagie.txt [2]http://git.openstack.org/cgit/openstack/election/plain//candidates/newton/Glance/Nikhil_Komawar.txt [3]http://git.openstack.org/cgit/openstack/election/plain//candidates/newton/Neutron/Armando_Migliaccio.txt [4]https://wiki.openstack.org/wiki/PTL_Elections_March_2016 Best Regards Chaoyi Huang ( Joe Huang ) -----Original Message----- From: Shinobu Kinjo [mailto:[email protected]] Sent: Wednesday, May 04, 2016 5:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] Requirements for becoming approved official project Hi Team, There is an additional work to become an official (approval) project. Once we complete PTL election with everyone's consensus, we need to update projects.yaml. [1] I think that the OSPF to become approval project is to elect PTL, then talk to other PTLs of other projects. [1] https://github.com/openstack/governance/blob/master/reference/projects.yaml Cheers, Shinobu On Mon, May 2, 2016 at 10:40 PM, joehuang <[email protected]> wrote: > Hi, Shinobu, > > Many thanks for the check for Tricircle to be an OpenStack project, and > Thierry for the clarification. glad to know that we are close to OpenStack > offical project criteria. > > Let's discuss the initial PTL election in weekly meeting, and start initial > PTL election after that if needed. > > Best Regards > Chaoyi Huang ( joehuang ) > ________________________________________ > From: Shinobu Kinjo [[email protected]] > Sent: 02 May 2016 18:48 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [tricircle] Requirements for becoming > approved official project > > Hi Thierry, > > On Mon, May 2, 2016 at 5:45 PM, Thierry Carrez <[email protected]> wrote: >> Shinobu Kinjo wrote: >>> >>> I guess, it's usable. [1] [2] [3], probably and more... >>> >>> The reason why still I can just guess is that there is a bunch of >>> documentations!! >>> It's one of great works but too much. >> >> >> We have transitioned most of the documentation off the wiki, but >> there are still a number of pages that are not properly deprecated. >> >>> [1] https://wiki.openstack.org/wiki/PTL_Guide >> >> >> This is now mostly replaced by the project team guide, so I marked >> this one as deprecated. > > Honestly, frankly we should clean up something deprecated since there > is a bunch of documentations -; It's really hard to read every singe > piece... > > Anyway better than nothing though. > >> >> As far as initial election goes, if there is a single candidate no >> need to organize a formal election. If you need to run one, you can >> use CIVS >> (http://civs.cs.cornell.edu/) since that is what we use for the >> official >> elections: >> https://wiki.openstack.org/wiki/Election_Officiating_Guidelines > > Thank you for pointing it out. > That is really good advice. > >> >> Regards, >> >> -- >> Thierry Carrez (ttx) >> >> >> _____________________________________________________________________ >> _____ OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Email: > [email protected] > GitHub: > shinobu-x > Blog: > Life with Distributed Computational System based on OpenSource > > ______________________________________________________________________ > ____ OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ______________________________________________________________________ > ____ OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Email: [email protected] [email protected] __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
