Jump to: navigation, search

Armoury

Note that this project has been archived and is no longer maintained.

Armoury Facts

Project Creation Date: August 20, 2015
Lifecycle State: Archived
Type: {{{type}}}
Primary Contact: Maros Marsalek (mmarsale, mmarsale@cisco.com)
Project Lead: Alexis de Talhouët (adetalhouet, adetalhouet@inocybe.com)
Committers:

  • 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)
  • An Ho (anipbu, An.Ho@huawei.com)

IRC: freenode.net #opendaylight-armoury
Mailing List: armoury-dev@lists.opendaylight.org
    Archives: mailing list archives
Meetings: 11:15am PST - noon PST on Mondays
Task List: Armoury Trello Board
Repository: git clone https://git.opendaylight.org/gerrit/p/armoury
Jenkins: jenkins silo
Gerrit Patches: code patches/reviews
Bugs:

[[Category:{{{type}}} Projects]]

Welcome to 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.

Tasks tracking

Armoury Trello Board

Release Plans

Beryllium Release Plan

Project Proposal

Meetings

When

Weekly on Monday from 11:15am-12:00 PM PST/PDT | 1:15-2:00 PM EST/EDT | 16:00-17:00 UTC during Daylight Time

Where

IRC: #opendaylight-armoury on freenode

Agenda

Agenda for next meeting (11/02)

  • Agenda bashing and roll call
  • On going tasks
    • workload-manager async redesign
    • workload manager RPCs
  • Open discussion
    • JDK8 support

Minutes from past meetings

11/02: Minutes - log
10/26: Minutes - log
10/19: minutes - log
10/12: minutes - log
10/05: minutes - log
09/28: minutes - log
09/21: minutes - log
09/14: minutes - log
09/07: mail

List of all subpages

ArmouryArmoury/Beryllium Release Plan