Page tree

Versions Compared

Key

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

...

6

including:

Fault management (Doctor)

Ressource management (Promise)

bgpvpn (ODL)

Introduction of Onos

DPDK support

KVM optimization (KVM)Danube priorities are discussed in the following section.We will see another of scenarios due to new features and a new installer.

The CI evolution already identified in Brahmaputra became critical in order to support a sustainable growth of the community and efficient use of the resources.

This version could be qualified as the "Real CI ready" version (question)

 
VersionMain achievementsInstallersScenariosFeatures
Arno

The "Proof of Concept" version

Arno release was supported by only 5 projects: 2 installer projects, 1 testing project, Releng and Octopus for the the CI.

Arno built the foundations of the OPNFV community. It clearly identified the types of projects (installer / testing / infrastructure)

2

1

0
Brahmaputra

The "Scenario" version

In order to support the increase in the number of installers and the code for the first set of feature projects (initiated in Arno but not ready for the first release), the concept of scenario was created. A scenario was defined as the OPNFV vehicle to support the diversity of integrations and new features and clarify the use of resources.

Additionally, Brahmaputra showed a real growth in the OPNFV ecosystem by the introduction of features, new SDN controllers and new installers. New test projects were also created to address the question of qualification beyond functional testing.

The testing community introduced a test DB API to collect the test cases and the associated results. A test API was developed to allow any test project to automatically report the results into a pre-defined format.

413Danube

The priorities are discussed in the following section.

We will see another increase in the number of scenarios due to new features and a new installer.

The CI evolution already identified in Brahmaputra became critical in order to support a sustainable growth of the community and efficient use of the resources.

This version could be qualified as the "Real CI ready" version (question)

5

(tentative)

58

(tentative)

 
Colorado

The "Features" version

Colorado confirmed the concept of scenario. While some scenarios remained "generic", there was an increase in the introduction of feature specific scenarios (e.g. bgpvpn, sfc, moon, fdio, lxd, ovs, kvm, etc.).

From a testing perspective, new test cases were added and a focus was made on time management. Brahmaputra clearly identified the risk of CI resources with bigger test suites. The notion of category was then created to distinguish between "smoke" tests (e.g. tests mandatory for the release qualification) and advanced tests (e.g.OpenStack, vnf, ...). The objective of limiting the time duration under 3 hours for all the tests was achieved. A system of test promotion was also introduced but not actually used.

The test API was completed for reporting pages (Functest & yardstick) in order to give a consistent view to the release manager on the status of the scenario.

437

15

including:

Policy management (Copper, Domino, Parser)

Security (Moon, Security scan)

Multisite (Multisite)

SFC (ONOS-sfc, ODL-sfc)

Container support (LXD scenario)

Acceleration (FDIO scenarios)

VNF (Automation of vIMS)

ARM support

Brahmaputra

The

"Scenario" version

In order to support the increase in the number

5

(tentative)

58

(tentative)

of installers and the code for the first set of feature projects (initiated in Arno but not ready for the first release), the concept of scenario was created. A scenario was defined as the OPNFV vehicle to support the diversity of integrations and new features and clarify the use of resources.

Additionally, Brahmaputra showed a real growth in the OPNFV ecosystem by the introduction of features, new SDN controllers and new installers. New test projects were also created to address the question of qualification beyond functional testing.

The testing community introduced a test DB API to collect the test cases and the associated results. A test API was developed to allow any test project to automatically report the results into a pre-defined format.

413

6

including:

Fault management (Doctor)

Ressource management (Promise)

bgpvpn (ODL)

Introduction of Onos

DPDK support

KVM optimization (KVM)

Arno

The "Proof of Concept" version

Arno release was supported by only 5 projects: 2 installer projects, 1 testing project, Releng and Octopus for the the CI.

Arno built the foundations of the OPNFV community. It clearly identified the types of projects (installer / testing / infrastructure)

2

1

0

 

Danube community priorities

...