Hi, I would like to self-nominate for a seat on the ONAP TSC.
I have been working on ONAP and related areas since September,2017 when I started my current role as ONAP chief architect in Intel. I have been technically/strategically leading group of ONAP engineers within Intel to contribute to ONAP releases. Some of my contributions include architecture of - Policy based HPA feature in OOF, Multi-Cloud & A&AI. - Secret Management Service to secure the ONAP secrets such as passwords - CA Private key security using PKCS11 with Hardware root of trust. - Distributed KV Store for configuration. - Kubernetes plugin to do LCM of containerized VNFs and orchestrate both VMs & containers. - ISTIO based Service mesh technology for ONAP. - Many edge automation activities : ONAP offload to regional controllers, Secure connectivity via IPSEC between ONAP and Edge locations and Aggregation of node statistics to site granularity. I have led many big technical projects in my career and had been working in NFV/SDN world for last 6 years. ONAP success is my major goal of my current role. With my experience in open source, networking , security, edge, micro services and service mesh technologies, I am confident that I will contribute/collaborate technically/strategically with rest of the community and be a constructive technical contributor/architect to the ONAP project. Short Bio: Srini Addepalli has over 22+ years of experience in networking and security. He has been in Intel for last 3 years working as Sr. Principal Engineer & Senior Architect. In his current role, he technically leads the software engineering & architecture activities related to network orchestration and network/infrastructure security with specific focus on ONAP, edge and Kubernetes. Previously he worked in many roles including CTO of a network security software company Intoto Inc (acquired by Freescale), Fellow & Chief architect at Freescale leading advanced technology group. In his previous jobs, he was instrumental in strategy & creation of UTM solutions, autonomous acceleration of L3, L4, IPsec, Openflow, & Cloud RAN functions, network security/packet-processing software solutions and infrastructure security solutions. My Bitergia statistics are: https://onap.biterg.io/goto/89070a01240d07735ab8d8292a5ff29d Thanks Srini (Srinivasa Addepalli) From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of Kenny Paul Sent: Tuesday, July 17, 2018 5:03 PM To: onap-tsc <ONAP-TSC@lists.onap.org> Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, Tuesday, July 17, 2018 If you are interested in running for a seat on the TSC, please read all of this information carefully Who is eligible to Run: Any Active Community Members as of 17:00 Pacific Time, Tuesday, July 17, 2018- There is NO limit to the number of candidates from any single company that can run for a seat. 4.1.1.1 TSC Membership Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions> Active Community Member: Anyone from the ONAP community with twenty (20) or more measurable contributions during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities Self-Nomination Phase Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st. NOTE: Replying to another candidate's self-nomination email announcing your own self-nomination is considered a blatant disregard for open source community norms. If you do that, you should probably re-assess both your qualifications and motivations for leading a collaborative community such as this. Your self-nomination email must include a link to your stats in Bitergia (instructions on how to do this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>. It is strongly recommended that candidates also include a small head-shot, a short biography and statement of intent on why you would be a good person to hold a seat on the TSC. As a courtesy, it is also requested that you fill in the 2018 TSC Election Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki page with that same information. Filling out the wiki page is NOT in lieu of sending the email as required, but it will greatly help facilitate the process of the elections. Special Provision for the original 9 ONAP Operators: There are 9 seats reserved for the nine original ONAP Platinum Service Provider members. Each of these Operators is REQUIRED to have at least one person nominate themselves for their seat on the TSC. If and only if an Operator does not have any eligible Active Community Members at the time of nomination process, they may appoint a nominee to run in the election. In such cases, the nominee must indicate that they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 TSC Member Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>) · · The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018 · The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018 · Election Phase Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, Tuesday, July 17, 2018 A Condorcet election will be held using the CIVS voting system<https://wiki.onap.org/display/DW/Voting+Best+Practices>. Active Community Members will receive an invitation to vote from CIVS. · The election phase will begin with the distribution of the CIVS poll via email from the application · The election phase will end two (2) weeks later in the same time zone the poll was initiated from Election Results · * The election of TSC Members shall consist of a single stack ranked vote of all candidates * Only the top ranked candidates from any single company will be elected; if the top 10 vote getters are all from the same company, only the person with the highest number of votes out of all 10 will be elected from that company. * The top ranked candidate from each Operator will be selected, for a total of nine members, one member from each Operator * The top ranked non-Operator candidates (whether affiliated with a company or an individual contributor), will be selected for the remaining nine seats, with no more than one member per company or group of related companies being selected. * The LF will update the Voting Results History<https://wiki.onap.org/display/DW/Voting+Results+History> page with their name, date, and link to the publicly viewable CIVS results and send an email to the distribution list and to onap-tsc Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>, 510.766.5945 San Francisco Bay Area, Pacific Time Zone -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3522): https://lists.onap.org/g/ONAP-TSC/message/3522 Mute This Topic: https://lists.onap.org/mt/23599386/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
