Project Technical Lead:Aaron Byrd. 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.
...
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 Byrd | AT&T | ab2745@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 Plunkett | AT&T | david.plunkett@att.com |
| N | ||
| Deepak Kataria | AT&T | dd7022@us.att.com |
| N | |||||
Kandan Kathrival | AT&T | kk0563@att.com | N | ||
| James Williams | AT&T | jw4099@att.com |
| N | |||||
Arm | song.zhu@arm.com | ||||
| Arm | trevor.tao@arm.com | ||||
| Alexandru Avadanii | Arm | alexandru.avadanii@enea.com | |||
Ciprian Barbu | Arm | ciprian.barbu@enea.com | |||
| Arm | Cristina.Pauna@enea.com | ||||
| Mahir Gunyel | Netsia | mahir.gunyel@netsia.com | Mahir 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 |
| Ash Young | Cachengo | ash@cachengo.com | |||
| Jimmy Lafontaine Rivera | Cachengo | jimmy@cachengo.com` | |||
| Zack Williams | ONF | zdw@opennetworking.org | ONF MTS, SEBA Dev team and manager of Jira, CORD platform team |
Upstream SEBA Project information:
SEBA project page (meeting times, mailing list, developer information): https://wiki.opencord.org/display/CORD/SEBA
...
- Virtualized SEBA installation for testing and development w/o PON access hardware: SEBA-in-a-Box
- Hardware requirements
- API Documentation
Use Case Details:
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 | See attachment for additional details |
Presentation:
| View file | ||||
|---|---|---|---|---|
|