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 | Intel Open Source Technology Center – Edge Arch and Pathfinding | |||
| Andrew Bays | Red Hat | ||||
| Leif Madsen | Red Hat | Red Hat NFVPE – DevOps and Automation Team Lead | |||
Tapio Tallgren | Nokia | ||||
| Justin Scott | Intel | Intel Open Source Technology Center- Edge Arch and Pathfinding | |||
| David Lyle | Intel | David Lyle | Intel Open Source Technology Center- Edge Arch and Pathfinding | ||
| Mikko Ylinen | Intel | Mikko Ylinen | Intel Open Source Technology Center- Edge Arch and Pathfinding | ||
| Craig Sterrett | Intel | Craig Sterrett | Intel Open Source Technology Center- Edge Arch and Pathfinding | ||
| Ned Smith | Intel | Ned Smith | Intel Open Source Technology Center- Edge Arch and Pathfinding; Security, Trusted Computing, Privacy, Safety. |
Overview
Project contributors:
Red Hat (contact: Frank Zdarsky)
Intel (contact: Jennifer Koerv)
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 | Manufacturing, Energy |
|
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 | Industrial Edge (IE) |
|
Blueprint - Proposed Name | Industrial Edge (IE) |
|
Initial POD Cost (CAPEX) | (TBC) |
|
Scale & Type | 3 servers to 1 rack; x86 servers (Xeon class) |
|
Applications | IoT Cloud Platform, Analytics/AI/ML, AR/VR, ultra-low latency control |
|
Power Restrictions | (TBC) |
|
Infrastructure orchestration | End-to-end Service Orchestration: n/a |
|
SDN | OVN |
|
| SDS | Ceph | |
Workload Type | containers, VMs |
|
Additional Details |
|