Jump to: navigation, search

FaaS:Main


FaaS Facts

Project Creation Date: August 6, 2015
Lifecycle State: Incubation
Type: App
Primary Contact: Xingjun Chu <xingjun.chu@huawei.com>
Project Lead: Xingjun Chu <xingjun.chu@huawei.com>
Committers:

  • Xingjun Chu <xingjun.chu@huawei.com>
  • Henry Yu <henry.yu1@huawei.com>
  • Danian Shi <shidanian@huawei.com>
  • Ziyang Yao <yaoziyang@huawei.com>
  • Khaldoon Al Zoubi <khaldoon.alzoubi@huawei.com>
  • Guoli Yin <guoli.yin@huawei.com>
  • Song Wei <songwei80@huawei.com>
  • Dong Feng <leslin.dongfeng@huawei.com>
  • Alex Zhang <alexzhang@chinamobile.com>
  • Yapeng Wu <yapeng.wu@huawei.com>

IRC: freenode.net@opendaylight-faas
Mailing List: faas-dev@lists.opendaylight.org
    Archives: unspecified
Meetings: See global meetings page
Repository: Repository
Jenkins: Jenkins
Gerrit Patches: Gerrit
Bugs: Bugzilla

Welcome to the FaaS - Fabric As A Service project home page!

Introduction

In general, FaaS project aims to create a common abstraction layer on top of a physical network, so northbound API or services can be easier to be mapped onto the physical network as concrete device configuration. The common abstraction layer models the physical network as a topology that consists of abstracted node - fabrics. Each fabric is abstraction of a portion of the physical network usually within the same control plane and uses similar data path technique, such as VXLAN or VLAN. Every fabric offers a set of unified services as well as primitive constructs to create and manage a logical network life cycle according to users’ requirement.

Using FaaS to deploy network services

  • decouples user network services from vendor and technology specific implementation, avoid vendor locked in.
  • enable service deploy and control automation, massively reduce OPEX as well as CAPEX.
  • improve service deployment agility.

If you think of a computer as a network, FaaS provides a set of system calls for network applications. Those system calls has two layers. One layer is called driver layer which abstracts vendor/technology specific technique, which is realized on top of a specific fabric object. The second layer is built on top of the whole network which consists of a topology of fabrics. The second layer provides neutron like user level logical network abstractions. With those two layers' abstraction, the controller can be extended to support more devices and technology while keeps users' services transparent to the change.

Moreover, applications built on top of FaaS is using high level primitives to program the network. To make an analogy, using FaaS to build applications is like a using C lib other than assembly to program a machine.

We also realize that the FaaS will evolve as underneath technology evolves just like system calls are extended as OS evolves. FaaS has to evolve in a backward compatible fashion.

Project Information

Beryllium

Boron

Carbon

Nitrogen

Oxygen

Test and Integration Plan

https://wiki.opendaylight.org/view/FaaS:SystemTestPlan

Meetings (open to all)

  • Topic: ODL - Weekly FaaS Project meeting
  • Date/Time: Monday's at 9pm EST
  • Host(s): Xingjun Chu (xingjun.chu@huawei.com)
  • Meeting password: no password (please note passwords are case sensitive)
  • Call in toll free number: 1-855-797-9485 (US Toll free)
  • Call in number: 1-415-655-0002 (US Toll)
  • Meeting Number: 197 938 288
  • Access Code: 197 938 288

Please contact hosts in case of any issues.

Clustering Support

  • The FaaS will work in a cluster configuration due to its mission critical nature and scalability requirements to control more devices.
  • The FaaS data both configuration and operational is in default shard for now, may be sub-sharded in the future for better scalability
  • The FaaS will works in concert with Openflow and Netconf and any southbound relevant clustering support.
  • The FaaS clustering requirements may not be satisfied by general purpose clustering support and the new requirments will be identified in the future releases after beryllium release.

Meeting Agendas

  • Sept 14, SFC support discussion
  • Sept 21, GBP render and Fabric Manager/logical network render architecture
  • Sept.28, FaaS Yang definition and finalize functional definition for beryllium release
  • Oct. 5, Cancelled due to most core members on Chinese holiday.
  • Oct. 9, user level logical network model and M3 deliverables
  • Oct. 12. Cancelled due to Canadian thanksgiving holiday.
  • Oct. 19. Carbon planning
  • Nov. 5. M1 milestone updates and issues
  • Dec. 6. discussion
  • Jan. 5. M2 milestone status report
  • Feb. 2. discussion
  • Mar. 5. M3 milestone status report
  • April. 5. Discussion
  • May. 24. Discussion
  • June. 12. Summit prep
  • July. 15. Demo prep
  • Aug. 17. RC disucssion
  • Sept.. 18. Summit
  • Oct.. 18.

Meeting Minutes

[to be added]

  • Sept 14, SFC support discussion
  • Sept 21, GBP render and Fabric Manager/logical network render architecture
  • Sept.28, FaaS Yang definition and finalize functional definition for beryllium release
  • Oct. 5, Cancelled due to most core members on Chinese holiday.
  • Oct. 9, user level logical network model and M3 deliverables
  • Oct. 12. Finalize deliveralbes
  • Oct. 19. M3 resovled items disucssion - further discussion of SFC integration in tokyo.uln review and action on singlefeaturetest
Release Release Plan Release Notes Release Review Installation Guide User Guide Developer Guide Operations Guide How-To's/Tutorials Feature Tree Feature Tests
Beryllium Release Plan Release Notes Release Review - - - - - - -
Boron Release Plan Release Notes Release Review - - - - - - -
Carbon Release Plan Release Notes Release Review - - - - - - -
Nitrogen Release Plan Release Notes Release Review - - - - - - -
Oxygen Release Plan Release Notes Release Review - - - - - - -
SNAPSHOT - - - - User Guide Developer Guide Operations Guide How-To's/Tutorials - System Test Plan

List of all subpages (used or unused)

FaaS/Release Plans/Beryllium Release PlanFaaS:BerylliumFaaS:Beryllium Release Notes
FaaS:Beryllium Release PlanFaaS:Beryllium Release ReviewFaaS:Boron Release Notes
FaaS:Boron Release PlanFaaS:Boron Release ReviewFaaS:Carbon Release Notes
FaaS:Carbon Release PlanFaaS:Carbon Release ReviewFaaS:Developer Guide
FaaS:GBPIntegrationFaaS:HighLevelArchitectureFaaS:How-To's/Tutorials
FaaS:MainFaaS:Nitrogen Release NotesFaaS:Nitrogen Release Plan
FaaS:Nitrogen Release ReviewFaaS:Oxygen Release PlanFaaS:Programmer Guide
FaaS:SFCIntegrationFaaS:SystemTestPlanFaaS:User Guide