You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

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)
Aaron ByrdAT&Tab2745@att.com Aaron Byrd has been with AT&T for over 19 years. In 2010, Personally developed and deployed AT&T's first use of a virtualization container technology in AT&T Production Datacenter environment.

For the past 4 years Aaron has been involved with driving a transition of AT&T Access Network to utilize a Cloud architecture while using SDN and NFV technologies.

 

Y
David PlunkettAT&Tdavid.plunkett@att.com  N
Deepak KatariaAT&Tdd7022@us.att.com  N

Kandan Kathrival

AT&T

kk0563@att.com



N

Arm

song.zhu@arm.com




Armtrevor.tao@arm.com


Alexandru Avadanii Armalexandru.avadanii@enea.com


Ciprian Barbu

Armciprian.barbu@enea.com


ArmCristina.Pauna@enea.com


Mahir GunyelNetsiamahir.gunyel@netsia.comMahir has been working about   19 years in Telco SW domain in different positions like development, architecting , management. He has experience especially on mobile telco networks and protocols.
Y


Use Case Details:


Kandan Kathirvel

Case Attributes

Description

Informational

Type

New blueprint for fixed wireline access within Network Cloud Blueprint family

 

Blueprint Family - Proposed   Name

Network Cloud

 

Use Case

Virtual broadband access   (XGS-PON - Higher bandwidth, symmetric version of GPON)

 

Blueprint proposed Name

SDN Enabled Broadband Access (SEBA)

 




Scale & Type

3 servers per POD

x86 and Arm (with 8-16 cores each)

 

Applications

Virtual broadband access – vOLT access & aggregation (5000 edge locations)

 

Power Restrictions

Less than 1 kW.  NEBS and 48V DC

 

Infrastructure orchestration

OS - Ubuntu 16.x

Docker 1.13.1 or above / K8 1.10.2 or above- Container Orchestration

Under Cloud Orchestration -   Airship v1.0

Open Network Operating System   (ONOS) and XOS

VOLTHA (Virtual Optical Line Terminal Hardware Abstraction – CORD project)

Network Edge Mediator (NEM)

ONAP and OSAM

EMS/NMS Adaptor

 

SDN

ONOS

OF & Redfish

 

Workload Type

Containers

 

Additional Details

Akraino based community blueprint, Full Automation (Airship based +   Tenant Container support)

Cloud layer hardened for production

Current SEBA POD contains   network elements, compute nodes, and software components. 

Aggregation and   management switches
    Three compute nodes required for K8 redundancy
    About twenty containers running ONOS,   XOS,   VOLTHA, NEM,   etc
    Supports up to 16 OLTs.

See attachment for additional details


Presentation:


  • No labels