<p dir="ltr">Thanks anh. Lúc chiều e cũng bookmark bài này rồi. E phải xem kỹ phần kiến trúc trong neutron, phần network này vẫn chưa thông lắm anh ạ. </p>
<p dir="ltr">P/s: Anh gửi tài liệu OVS cho e và Long nhé.</p>
<div class="gmail_quote">On 1 Apr 2014 00:04, "Kyle Mestery" <<a href="mailto:mestery@noironetworks.com">mestery@noironetworks.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br>
<br>
I have decided to run for the OpenStack Networking (Neutron) PTL position.<br>
<br>
Why I Want To Be Neutron PTL<br>
-----<br>
I want to be Neutron PTL because I wish to continue pushing Neutron forward<br>
and help it evolve, and have the skills necessary to do it. I've worked in Open<br>
Source for many years, having contributed to projects such as Open vSwitch,<br>
libvirt, and OpenDaylight, as well as OpenStack Neutron. Neutron has a great<br>
team of developers, both core and non-core contributors. Being able to help<br>
them all work productively together and push Neutron forward is something I<br>
not only want to do, but something I think I can be very effective at.<br>
<br>
Qualifications<br>
-----<br>
I have been a core developer since the beginning of the Havana cycle. My<br>
main focus in Neutron has been around the Modular Layer 2 (ML2) sub-team,<br>
which I've co-lead for the last year. I wrote the OpenDaylight ML2<br>
driver, as well<br>
as the devstack integration and Jenkins setup for OpenDaylight. I have also<br>
been leading a sub-team focused on Group Based Policy since the Icehouse<br>
Summit. As on Open vSwitch developer, my focus has been on improving<br>
Neutron's use of OVS, and enhancing OVS for use by Neutron. I founded the<br>
Minnesota OpenStack Meetup in November of 2012, hosting numerous speakers<br>
from the OpenStack community to an audience in the upper Midwest. I've<br>
presented at the last few OpenStack Summits on Open Source SDN topics, as<br>
well as giving presentations on OpenStack at other Open Source conferences. I<br>
recently co-hosted the first Open vSwitch Hackathon, which allowed core OVS<br>
developers to interact with not only each other but also developers from<br>
OpenStack Neutron and OpenDaylight.<br>
<br>
Icehouse Accomplishments<br>
-----<br>
This past cycle, my main focus was continuing to expand the ML2 sub-team and<br>
assist plugin developers who were porting their existing core plugins<br>
into ML2 or<br>
writing brand new ML2 drivers. I also formed and lead the Group Based Policy<br>
sub-team, which is now marching towards a Proof of Concept for the Juno Summit<br>
In addition, I've spent time with the OpenDaylight project to ensure that<br>
OpenDaylight integrates with OpenStack Neutron as an ML2 driver.<br>
<br>
Looking forward to Juno<br>
-----<br>
If I am elected PTL, I'd like to focus on a few areas for Neutron. One immediate<br>
area of improvement I'd like to do is around the blueprint process. I've been<br>
watching what Russell and the Nova team have been doing with setting up the<br>
Nova BP process to use gerrit, and I'd like to move Neutron in this<br>
direction as well.<br>
Formalizing this process a bit more will lead to less surprises for BP<br>
drafters, and<br>
will also ensure core reviewers know what they are signing up for as<br>
people propose<br>
features. I'd also like to work to expand our core reviewer team in<br>
the Juno cycle. As<br>
the project has grown, the existing core reviewers could use some assistance by<br>
working to expand the team and spread the review load. Along these<br>
lines, I'd also<br>
like to empower the sub-teams in Neutron. The project has grown to a point where<br>
empowering the various sub-teams to allow more effective decision<br>
making would be<br>
a good thing. I'd like to continue the focus on ensuring Neutron is a<br>
good citizen in<br>
the community by ensuring we squash bugs related to the gate. And<br>
finally, I want to<br>
work to ensure we have a scalable, production quality Open Source<br>
Neutron reference<br>
implementation in the Juno timeframe.<br>
<br>
In closing<br>
-----<br>
OpenStack Neutron has taken a big step forward in the Icehouse cycle<br>
with regards to<br>
stability and testing. Ensuring we continue to enhance the development<br>
process will<br>
allow us to continue making strides in this area and allow Neutron to<br>
continue evolving<br>
in a positive direction.<br>
<br>
Thank you,<br>
Kyle<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>