Project Technical Lead: David Plunkett. Elected 1/17/19.

Project Committers detail:

Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.

A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.

Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.

Only Committers for a project are eligible to vote for a project’s Project Technical Lead.

Please see Akraino Technical Community Document section 3.1.3 for more detailed information.

Committer	Committer Company	Committer Contact Info	Committer Bio	Committer Picture	Self Nominate for PTL (Y/N)
David Plunkett	AT&T	david.plunkett@att.com	David Plunkett has been involved in the design and deployment of virtualization infrastructure in AT&T since 2007. As the architect for multiple internal x86 virtual environments, David lead collaboration across technical teams to adopt and standardize emerging technologies. David recently changed to a new role supporting open source initiatives for AT&T and has been part of the Akraino community since its launch in the spring of 2017. David contributed to multiple components in the AT&T seed code for the Network Cloud blueprint and lead the development of the bare metal deployment feature.		Y
John Craig	AT&T				N
Paul Carver	AT&T	pcarver@att.com	See Radio Edge Cloud (REC) for bio.		N
Mike Hunter	AT&T				N
Kandan Kathirvel	AT&T	kk0563@att.com			N
Deepak Kataria	AT&T	dd7022@us.att.com			N
Naga Suggana	AT&T	ns156u@us.att.com			N
	Radysis
	Netsia
Alexandru Avadanii	Arm	alexandru.avadanii@enea.com
Ciprian Barbu	Arm	ciprian.barbu@enea.com
cristinapauna	Arm	Cristina.Pauna@enea.com

Use Case Details:

Case Attributes	Description	Informational
Type	New blueprint submission
Blueprint Family - Proposed Name	Network Cloud Family
Use Case	Network Cloud – carrier edge use case
Blueprint proposed Name	Unicycle
Initial POD Cost (capex)	Unicycle less than $150k
Scale & Type	Up to 7 servers x86/ARM server or deep edge class
Applications	5G Core or vRAN (RIC)
Power Restrictions	Example Only: • Less than 10Kw
Infrastructure orchestration	OpenStack Pike or above - VM orchestration Docker 1.13.1 or above / K8 1.10.2 or above- Container Orchestration OS - Ubuntu 16.x VNF Orchestration - ONAP Beijing Under Cloud Orchestration - Airship v1.0
SDN	SR-IOV & OVS-DPDK or VPP-DPDK
Workload Type	VMs and Containers
Additional Details	See attachment

Presentation:

Browser not supported