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) |
Frank Zdarsky | Red Hat | ||||
Jennifer Koerv | Intel | ||||
Sukhdedv Kapur | Juniper | Distinguished Engineer; Contrail Software - CTO Org | |||
| Andrew Bays | Red Hat | ||||
| Mikko Ylinen | Intel | ||||
| Craig Sterrett | Intel | Craig Sterrett (Deactivated) | |||
| Yolanda Robla | Red Hat | Yolanda Robla Mota | Red Hat NFVPE - Edge, baremetal provisioning | Y | |
| Ned Smith | Intel | ||||
| Ricardo Noriega | Red Hat | Ricardo Noriega De Soto | Red Hat NFVPE - CTO office - Networking | ||
| Manjari Asawa | wipro | Manjari Asawa <manjari.asawa@wipro.com> |
Overview
Project contributors:
Red Hat (contact: Frank Zdarsky)
Intel (contact: Jenny Koerv (Deactivated))
Juniper (contact: Sukhdev Kapur)
Project committers:
to be identified once the proposal is accepted
Project plan:
to be developed once the proposal is accepted
Resourcing:
- will be established once the proposal is accepted
Use Case Template
Attributes | Description | Informational |
|---|---|---|
Type | New | |
Industry Sector | Telco and carrier networks | |
Business Driver | ||
Business Use Cases | ||
Business Cost - Initial Build Cost Target Objective | ||
Business Cost – Target Operational Objective | ||
Security Need | ||
Regulations | ||
Other Restrictions | ||
Additional Details |
Blueprint Template
Attributes | Description | Informational |
|---|---|---|
Type | New | |
Blueprint Family - Proposed Name | Kubernetes-Native Infrastructure for Edge (KNI-Edge) | |
Use Case | Provider Access Edge (PAE) | |
Blueprint - Proposed Name | Provider Access Edge (PAE) | |
Initial POD Cost (CAPEX) | less than $150k (TBC) | |
Scale & Type | 3 to 7 x86 servers (Xeon class) | |
Applications | vRAN (RIC), MEC apps (CDN, AI/ML, …) | |
Power Restrictions | less than 10kW (TBC) | |
Infrastructure orchestration | End-to-end Service Orchestration: ONAP | |
SDN | Tungsten Fabric (w/ SR-IOV, DPDK, and multi-i/f); leaf-and-spine fabric mgmt. | |
| SDS | Ceph | |
Workload Type | containers, VMs | |
Additional Details |