From 791933a128b92e4683f0ffa8045efcae329da3be Mon Sep 17 00:00:00 2001 From: Omer Anson Date: Sun, 18 Sep 2016 09:00:46 +0300 Subject: [PATCH] Adding Omer Anson (oanson) candidacy for Dragonflow Change-Id: I4f0d222e3bd38881774b999819200be0101f259d --- candidates/ocata/Dragonflow/oanson.txt | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 candidates/ocata/Dragonflow/oanson.txt diff --git a/candidates/ocata/Dragonflow/oanson.txt b/candidates/ocata/Dragonflow/oanson.txt new file mode 100644 index 00000000..a9724d58 --- /dev/null +++ b/candidates/ocata/Dragonflow/oanson.txt @@ -0,0 +1,25 @@ +I would like to propose my candidacy for Dragonflow PTL position. + +My goal for Dragonflow is to make it a reference architecture to implement +networking and distributed networking services in an easy and simple manner +while supporting production grade and large scale requirements. + +I think that Dragonflow pluggable architecture is proving to be a strong +choice we made and is even being considered at other OpenStack networking +projects. +I also believe that our simplicity can be very appealing to users that +want a simple network virtualization solution part of OpenStack. + +An important goal is to keep Dragonflow an integral part of OpenStack +and make sure to address the various use cases of OpenStack deployments +in terms of networking. + +For the next cycle, I would like to see Dragonflow become a viable choice for +cloud deployments. This means a heavy stress on stabilization, deployment, and +performance. + +I would also like to see new features make it into the release, such as full +IPv6 support, FWaaS, VPNaaS, and LBaaS. + +Thank you, +Omer Anson.