Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Figure 4 – Relationship between Feature Project, Upstream component and Integration project

 


3.3.2.2   Akraino Edge Stack Integration Projects (Blueprints)

...

Use Case Attributes

Description

Informational

Type

New or Modification to an existing submission 


Industry Sector

Telco and carrier networks

 


Business driver

Emerging technologies such as 5G (vRAN, Core) and associated Edge Services requires Cloud instance deployed at the edge of the provider network to support latency need. 


Without Edge Cloud, above said services cannot be enabled. 


Business use cases

For Example:

      
  1. Customer Edge deployable at Customer premises such as home, enterprises, offices to support Edge services such as SD-WAN
  2.   
  3. Customer Edge deployable at Public buildings such as Stadiums, Smart cities, etc., to support edge applications for example - Video Analytics, AI/ML based detection, etc.,
  4.   
  5. Edge Cloud deployable at Cell tower to support RAN related workload
  6.   
  7. Edge Cloud deployable at Central offices ranging from one rack to multiple racks

 


Business Cost - Initial Build

For Example:

      
  1. Edge Cloud deployable at Central offices with single rack should be less than 150K $

 


Business Cost - Operational

For Example:

      
  1. Edge Cloud deployable at Central offices with single rack should be less than 100K $ as operating cost per year.
  2.   
  3. In-place upgrade of the Edge cloud should be supported without impacting the availability of the edge applications

 


Operational need

For Example:

Edge Solution should have role based access controls, Single Pane of Glass control, administrative and User Based GUIs to manage all network cloud family based blueprints.

The automation should also support zero touch provisioning and management tools to keep operational cost lower 


Security need

For Example:

The solution should have granular access control and should support periodic scanning

 


Regulations

For Example:

The Edge cloud solution should meet all the industry regulations of   data privacy, telco standards (NEBS), etc.,

 


Other restrictions

Consider the power restrictions of specific location in the design (example - Customer premise) 


Additional details

The Edge Cloud Solution should be deployable across the globe and should be able to support more than 10,000 locations 


 3.3.2.2.2.2   Template 2 - Blueprint family template

...

Use Case Attributes

Description

Informational

Type

New or Modification to an existing submission

 


Blueprint Family - Proposed Name

Network Cloud Family 


Use Case

Network Cloud

 


Blueprint proposed

Central Office deployments

  •   Unicycle
  •   Tricycle
  •   Cruzer

Customer Premise deployments

  •   Rover

 


Initial POD Cost (capex)

Examples Only:

  •   Rover less than $20k
  •   Unicycle less than $150k
  •   Tricycle less than $300k
  •   Cruzer less than $800k

 


Scale

Examples Only:

  •   Rover - 1 server
  •   Unicycle - 1 rack
  •   Tricycle - 3 racks
  •   Cruzer - 6 racks
 


Applications

Any type of Edge Virtual Network Functions 


Power Restrictions

Example Only:

  •   Cruzer - less than 50k watts
 


Preferred Infrastructure orchestration

OpenStack - VM orchestration

Docker/K8 - Container Orchestration

OS - Linux

VNF Orchestration - ONAP

Under Cloud Orchestration - Airship 


Additional Details

Submitter to provide additional use case details

 


 3.3.2.2.2.3   Template 3 - Blueprint species template

...

Use Case Attributes

Description

Informational

Type

New or Modification to an existing submission

 


Blueprint Family - Proposed Name

Network Cloud Family 


Use Case

Network Cloud 


Blueprint proposed Name

Unicycle A 


Initial POD Cost (capex)

Examples Only:

  •   Unicycle less than $150k
 


Scale & Type

  •   Up to 7 servers
  •   x86/ARM server or deep edge class

 


Applications

5G Core or vRAN (RIC) 


Power Restrictions

Example Only:

  •   Less than 10Kw
 


Infrastructure orchestration

OpenStack Pike or above - VM orchestration

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

OS - Ubuntu 16.x

VNF Orchestration - ONAP Beijing

Under Cloud Orchestration - Airship v1.0 


SDN

SR-IOV & OVS-DPDK or VPP-DPDK

 


Workload Type

VMs and Containers

 


Additional Details

Submitter to provide additional use case details 

 



3.3.2.3   Akraino Validation Projects

...

From State

To State

Review Description

Null

Proposal

 


Proposal

Incubation

Incubation review

Incubation

Mature

Maturity review

Mature

Core

Core review

Core

Archived

Termination review

...

There are no limitations on the number of candidates that can run in an election for TSC membership, nor is there a limit to the number of candidates from any organization including its subsidiaries (hereon termed simply an ‘organization’)  that can run for TSC membership. However the limits as defined in the TSC technical charter 4.4.3.2.1 section (TSC approved 9/5/19) for the total number of TSC members from a given organization shall be enforced  by means of the election and interim election process described in 4.4.3

...

The CIVS election wil rank all standing candidates from 1 to N.

Only one (1) person from any company, or a group of related companies can be elected as a TSC member at any given time. (TSC approved 9/5/19)

If any organization entered If any organization entered more than the permitted limit of electable candidates all excess candidates shall be removed from the results from the least ranked upwards until the organization  limit is reached.

...

In case a TSC member, including Chair or Co-Chair, steps down or is required to step down due to, no longer able to perform the TSC duties, moved to a different company (TSC approved 9/5/19), organization limits being exceeded or as a result of company acquisitions or mergers after each yearly election, an interim election may be called by the TSC . (TSC approved 9/5/19)

In all above cases, the TSC member may inform via an email to the TSC email list, an interim election may be called by the TSC for that single position within 60 days of the notification from the leaving TSC member. Interim election can be used to reelect the open TSC position. The period of the TSC member elected using the interim election can be up to next full election. (TSC approved 9/5/19)

In an interim election, any organization eligible contributors (TSC approved 9/5/19) may only enter candidates if their current representation on the TSC is below their organization’s TSC an organization may only enter candidates if their current representation on the TSC is below their organization’s TSC Member limit.

Interim elections shall otherwise follow all the same procedures and use the same voting schemes as the yearly elections.

...

The TSC will elect from amongst TSC Members a chairperson and co-chairperson for a term of one year.

The TSC shall hold elections to select a TSC Chair and Co-Chair at the Transition Point and subsequently every year within one month of the yearly anniversary of the date of the Transition Point.

year.

The TSC shall hold elections to select a TSC Chair and Co-Chair at the Transition Point and subsequently every year within one month of the yearly anniversary of the date of the Transition Point.

Election of a TSC Chair/Vice Chair/Coordinator shall use a multiple-candidate method shall consist of a single stack ranked vote of all candidates using  CIVS  https://civs.cs.cornell.edu/


4.4.3.4 TSC Member Contributions (TSC approved 9/5/19)

Contributions to the Akraino Community may be counted as either ‘individual’ or “individual contribution on behalf of a company”. A ‘individual’ contribution is made by a named individual. An “Individual contribution on behalf of a company” are governed by the policy of an individual’s Organization to whom they were affiliated at the time of the contribution. Individual contributions cannot be transferred to other individual. 

For the TSC election purpose, the Organization can request the TSC to count an “individual contribution on behalf of a company” to another named individual of their Organization at any time regardless of whether the original Contributor remains in or has left the Organization. If an individual Contribution leaves an Organization that Organization may at their sole discretion decide to: retain all their Contributions and reallocate them to another named individual within their Organization (for the TSC election purpose). Organization should inform TSC of such details of contributions and reallocation in writing.

OR

agree to transfer all their Contributions to the individual’s new Organization thereby releasing all interest in the previous Contributions to the Individual’s new Organization. Organization should inform TSC of such details of contributions and releasing in writing.Election of a TSC Chair/Vice Chair/Coordinator shall use a multiple-candidate method shall consist of a single stack ranked vote of all candidates using  CIVS  https://civs.cs.cornell.edu/

4.5   Responsibilities of the TSC

...

Term

Full   Meaning

IoT

Internet of things

PTL

Project technical lead

ETE

End to end

SDK

Software development kit

API

Application program interface

POD

Point of delivery

CI/CD

Continuous integration and continuous delivery

LCM

Lifecycle management

YAML

YAML Ain't Markup Language.  It's basically a human-readable structured   data format.

OS

Operating system

EOL

End of life

VNF

Virtual Network Function (VM or container based) 

CIVS

 Condorcet Internet Voting Service

...