Neutron to become the default and standard NaaS
I have been an OpenStack member since 2011 as a part of the founding team of the neutron project (formerly known as quantum). I have extended my contributions to nova, devstack, docs, heat and other projects. Currently, I am part of the core team for docs-specs and lead the work needed to complete the networking guide.
Currently, I am part of the Cloud Operations and Infrastructure team for one of the biggest SaaS providers. My current role as OpenStack consumer is giving me a different opinion about what OpenStack should integrate and how it can be consumed easier and more scalable for both Service Providers and Entreprises. I am planning to provide my experience to the OpenStack Board in order to drive its direction based on the interest of the Operators and Users, never influenced by technology-specific vendors.
Professionally, I have a PhD on Distributed Systems and I have specialized on Cloud Computing, Network Virtualization, Software-defined Networking (SDN), Network Functions Virtualization (NFV), OpenFlow and the most important OpenStack. During my last three positions at Cisco, PLUMgrid and Workday I have completed successful OpenStack deployment in heterogeneous and scalable infrastructures, from vendor specific hardware to commodity one. All improvements have been shared and I have created extended experience on configuration languages such as Puppet and Chef.
I'm involved in the following OpenStack projects: Nova,Horizon,Quantum,Ceilometer,Heat,Ironic,Openstack-manuals,Deployment,DevStack
My relationship to OpenStack is as a user and operator. My professional career goal is to help the community to make OpenStack a production ready platform that provides scalable and updatable code for users with hybrid requirements in terms of security, operations and performance.
One of my biggest contributions to OpenStack’s success has been the work that I have done as a part of the Neutron Core team from 2012 to Liberty release. Making Neutron a successful bug-free and HA project has changed drastically the number of features that Operators can provide to their cloud tenants.
I am also very proud of the work that we have done around the networking guide.
Being actively a liaison between neutron and manuals teams and investing a significant effort to have a reliable guide about networking in OpenStack.
Currently, I am leading the work needed to make this guide a formal document officially ready for consumption.
Since college I have been member of the student board helping to driving the students concerns to the management team in order to increase the engagement of the student in the extra-scholar activities.
As a member of my community board, I am used to listen my neighbors and drive their request to the board and properly find a solution that will make more sense will have everybody in a great mood.
I would like to see increased the participation of users/operators in the OpenStack board. This is a great opportunity to have a formal representation and express directly to the board how operators are impacted by the decisions of the development teams.
As Operators we could provide some of the most realistic feedback to the board, with this information the board will be able to drive successfully the foundation direction in order to increase the visibility and trust from potential new users in our platform.
Help the development teams (projects) to come together efficently. Having a good integration between all the teams and satisfice all their requirements properly in a scalable way.
Have a formal representation of OpenStack Operators in the board. Provide the right forum for Operators to influence the future of the platform based on their requirements and experiences using OpenStack.
Help the minorities to have visibility in the community. I would like to have even more engagement with the women of OpenStack in the community as well as other minorities.
Edgar has already been nominated by: