This election is to fill a seat of the Technical Committee that has been vacated.

Nomination period will close on Feb 14th.

Template:

Name: <>


Name: Rupam Choudhury


Short Bio:

I am a Lead Network Engineer supporting “Network Cloud” at AT&T. My role is to define the network architecture including Overlay and Underlay for AT&T Cloud offerings (AIC and NC). I am currently leading the design of 5EC/Network Cloud platform which will support 5G control plane and user plane applications and IP Services vNFs.

My career started as a Unix Systems administrator working for New York Stock Exchange and later joined AT&T. As my career progressed in AT&T, I made multiple skill pivots supporting AT&T’s Broadband services, Cable ISP customers and VoIP ENUM solutions as a Network Engineer specializing in Datacenter networking working on Cisco/Foundry switching routing and load balancing gears. I was an integral part of the design team that developed anycast routing DNS model to support uVerse/MIS customers supporting 6 million+ queries per sec. I led the design of Network Virtualized Platform (NVP) which drive the architecture of various cloud offerings within AT&T.

In addition, I am a research oriented engineer. During 2015-2018 I authored 3 US Patents in the area of mobility and SDN.

Statement of Intent:

I want to shape Tungsten Fabric to support features that meets Telco needs and also meets Edge use cases. I want to develop community support to enhance TF to be meet resiliency, performance, security and feature needs by closely working with the community and communicating effectively the real need of the business.


Name: Zhaoyan Chen 


Short Bio: 

Zhaoyan Chen is a senior software engineer in Intel for 6+ years, working on Tungsten Fabric performance test and analysis. Besides Tungsten Fabric, Zhaoyan is also responsible for analyzing DPDK performance on Intel x86 platform and test automation. He is the CI expert and also contributed to DPDK community lab setup last year. Before joining Intel, Zhaoyan worked for Marvell on mobile industry.

Statement of Intent: 

Have been worked for Tungsten Fabric over 1 year, delivered pure software performance suite for Tungsten in community, and drove the 1st Tungsten open lab online, which was announced in KubeConf 2018 in PRC. I want to continue to drive a better CI for community, analyze and optimize Tungsten vRouter performance, and show Tungsten performance improvement with optimization/new hardware platform/new NIC in open lab.



Short Bio: 

Edward Ting is a senior engineering manager at Lenovo (a Linux Foundation Platinum member) Datacenter Group leading Lenovo Tungsten Fabric based SDN Controller development for 2+ years.

Since the beginning, Edward has led the team to contribute 50+ security vulnerability fixes; authored security vulnerability blueprint; published R5.0.1 Release Notes and Getting Started Guide. Also since November 2017, Edward has been dedicated in participating TSC weekly calls and seeking every possible opportunity to contribute to the community. In addition, Edward has been promoting Tungsten Fabric in both Bay Area as well as overseas. They are:

  1. May 2018: hosted the Open Source Networking Q2 Meetup to promote Tungsten Fabric.
  2. Sep. 2018: gave a talk to demonstrate the feature of Tungsten Fabric device manager at Open Source Networking Q3 Meetup.
  3. Nov. 2018: gave talks at Tungsten Fabric co-lo events at KubeCon Shanghai and GNTC Nanjing in China.
  4. Nov. 2018: gave 2 talks in Taiwan to promote Tungsten Fabric.

Before Lenovo, Edward was at Ericsson responsible for Ericsson vRouter DPDK initial bring-up as well the team lead for OpenStack & VMware cloud automation for DevOps. Prior to Ericsson, Edward was a principal engineer and development manager at Symantec for the secure gateway product line.

Statement of Intent: 

Edward will be focusing on the following two areas:

.1. Delivering pure community releases that the community can build and consume. Currently not everything has version control nor hast the source code tagging covers everything. This must be fixed ASAP so everybody can reliably build community releases.

2.  Actively address security vulnerabilities. Currently the scorecard on Tungsten Fabric is insecure. It is due to old 3 party packages, outdated code, and development discipline. Edward want to enable CI/CD to scan security vulnerability for the code commits as well as community releases.

The goal is to have a secure and reliable releases the community can easily consume.