Skip to end of metadata
Go to start of metadata

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 BioCommitter Picture 

Self Nominate for PTL (Y/N)

Frank Zdarsky

Red Hat




Jennifer KoervIntelIntel Open Source Technology Center – Edge Arch and Pathfinding

Andrew BaysRed Hat


Tapio Tallgren

Nokia




David LyleIntelDavid LyleIntel Open Source Technology Center- Edge Arch and Pathfinding

Mikko YlinenIntelMikko YlinenIntel Open Source Technology Center- Edge Arch and Pathfinding

Ned SmithIntelNed SmithIntel Open Source Technology Center- Edge Arch and Pathfinding; Security, Trusted Computing, Privacy, Safety.

Yolanda RoblaRed HatYolanda Robla MotaRed Hat NFVPE - Edge, baremetal provisioning
Y
Ricardo NoriegaRed HatRicardo Noriega

Red Hat NFVPE - CTO office

Networking



Manjari AsawawiproManjari Asawa <manjari.asawa@wipro.com>


Abhinivesh JainWiproAbhinivesh JainDistinguished Member of Technical Staff, CTO office

Overview

Project contributors:

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
Middlewares: Knative (serverless), Kubeflow (AI/ML), EdgeX (IoT)
App Lifecycle Management: Kubernetes Operators (mix of Helm and native)
Cluster Lifecycle Management: Kubernetes Cluster API/Controller
Cluster Monitoring: Prometheus
Container Platform: Kubernetes (OKD 4.0)
Container Runtime: CRI-O
VM Runtime: KubeVirt
OS: CoreOS, CentOS-rt



SDN

OVN


SDSCeph

Workload Type

containers, VMs


Additional Details



  • No labels