Jump to: navigation, search

Project Proposals:Armoury

Name

Armoury

Repo Name

armoury

Description

Just as compute needs to make requests to the controller to get networking resources in order to provide its services, so too does the controller sometimes need to make requests of the workload manager to get compute resources and/or network function (NF) (physical or virtual) orchestration to provide its services.

Examples would include, but not be limited to SFC requesting the standing up of new network functions (physical or virtual) across which it could load balance in response to network conditions.

In order to accomplish this end armoury needs to provide minimally three things:

  1. A registry or catalog of the necessary information (images, metadata, templatized day 0 config, how to communicate with the NF, etc) to describe the NF to the workload manager and/or network function (NF) (physical or virtual) orchestration.
  2. The most minimal possible API to allow applications to request that the workload manager start/stop/etc the NF and some information from the workload manager/nf orchestrator about the state of the NF.
  3. Example Drivers to talk to various workload managers (OpenStack/Meseophere/Docker/Kubernetes/etc).

The goal is not to build a full blown orchestrator, but rather to provide the mechanism for ODL applications to request NFs from disparate workload managers and/or upstream orchestrators.

Scope

  1. A registry or catalog of the necessary information (images, metadata, templatized day 0 config, how to communicate with the NF, etc) to describe the NF to the workload manager and/or network function (NF) (physical or virtual) orchestration.
  2. The most minimal possible API to allow applications to request that the workload manager start/stop/etc the NF and some information from the workload manager/nf orchestrator about the state of the NF.
  3. Example Drivers to talk to various workload managers (OpenStack/Meseophere/Docker/Kubernetes/etc).

Resources Committed (developers committed to working)

Who is, or will be working on this effort?

Initial Committers

Who would be the initial committers to the project? Please include each committer's First and Last Name, OpenDaylight Gerrit-ID, and Email Address

Alexis de Talhouët (adetalhouet, adetalhouet@inocybe.com)
Brady Johnson (ebrjohn, brady.allen.johnson@ericsson.com)
Maros Marsalek (mmarsale, mmarsale@cisco.com)
Gabriel Robitaille-Montpetit (grmontpetit, grmontpetit@inocybe.com)
Ed Warnicke (eaw, eaw@cisco.com)
Ian Wells (ijw, iawells@cisco.com)
Ariel Noy (ariel_noy, ariel.noy@hp.com)
David Goldberg (davidg, gdavid@hp.com)
Mathieu Lemay (mlemay, mlemay@inocybe.com)
Yapeng Wu (yapeng, yapeng.wu@huawei.com)
Sam Hague (shague, shague@redhat.com)
Keith Burns (alagalah, alagalah@gmail.com)

Vendor Neutral

If this proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc. have been removed? Please specify.

Meets Board Policy (including IPR)

Link for project proposal

Armoury_Proposal.pdf