Project Technical Lead: Rakesh Bohra. 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 | N | ||
Andrew Wilkinson | Ericsson | N | |||
| Rakesh Bohra | Ericsson | rakesh.bohra@ericsson.com | Rakesh Bohra is associated with Ericsson since 2008 and has diverse hands-on working experience with various telco infrastructure products and solutions. Rakesh has been involved in solution design and deployment of Ericsson NFV Cloud infrastructure Solution since 2014 with specialization in OpenStack and most recently he has been working with Akraino Network Cloud blueprint shaping solution for Edge Cloud. | Y | |
| Georg Kunz | Ericsson | georg.kunz@ericsson.com | N | ||
| Jan-Erik Mångs | Ericsson | jan-erik.mangs@ericsson.com | N | ||
| Roddric Boswell | Ericsson | roddric.boswell@ericsson.com | N | ||
| Indumathi Buddi | Ericsson (Contract Resource) | indumathi.buddi@ericsson.com | N | ||
| Rihab Banday | Ericsson | rihab.banday@ericsson.com | N | ||
| Marinko Caturic | Ericsson | marinko.caturic@ericsson.com | N |
Use Case Details:
Ericsson is proposing this new SPECIES for the existing Network Cloud Blueprint Family for a Unicycle POD based on Dell R740 HW.
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 - OVS-DPDK | |
Initial POD Cost (capex) | Unicycle - OVS-DPDK less than $150k | |
Scale & Type | Up to 7 servers (3 control plus 1 to 4 workers) x86 Dell R740 servers | |
Applications | 5G Core or vRAN | |
Power Restrictions | Example Only: | |
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 | OVS-DPDK | |
Workload Type | VMs and Containers | |
Additional Details | A new Feature Project shall be started to contribute the necessary upstream functionality to Airship |
All other details are as per the existing Unicycle - Dell - SR-IOV BP species.
Presentation:
Below is the Network Cloud Family architecture. The objects marked yellow represents the impacted projects for OVS-DPDK Unicycle Blueprint
