Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 15 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 BioCommitter Picture 

Self Nominate for PTL (Y/N)

Itamar EshetAT&Tie2575@intl.att.com

Y
David PlunkettAT&T david.plunkett@att.com  N
Shay NaehCloudifyshayn@cloudify.co

N
Eden RozinAT&Teden.rozin@intl.att.com

N
Yaki RatzAT&Tyaki.ratz@intl.att.com

N
Nati MalcaAT&Tnati.malca@intl.att.com

N
Robert EbyAT&Teby@research.att.com

N
David LyleInteldavid.lyle@intel.com

N

Use Case Details:

Case Attributes

Description

Informational

Type

New   Blueprint for Serverless capability at the Edge

 

Blueprint   Family - Proposed Name

Network   Cloud

 

Use   Case

Provide   FaaS   (Function as a Service) for Serverless Applications

 

Blueprint   proposed Name

Serverless

 

Initial   POD Cost (capex)

Leverage   Unicycle POD - less than $150k

 

Scale   & Type

Up   to 7 servers

    x86/ARM server or deep edge class

 

Applications

Ephemeral event driven transactions for IoT gateway.    For example, applications for autonomous cars.

 

Power   Restrictions

Less   than 10Kw

 

Infrastructure   orchestration

Kubeless

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

OS   - Ubuntu 16.x

Under   Cloud Orchestration - Airship v1.0

 

SDN

OVS

 

Workload  Type

Containers

 

Additional  Details

VerneMQ MQTT Gateway and/or Mosca MQTT Broker

Kafka message bus and Webhook/Nginx middleware

Kubeless function management engine over Kubernetes

Helm chart for platform infrastructure installation integrated with Airship

Regional controller based installer for Functions

See attachment for additional details

Presentation:


  • No labels