Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update to show scenario work in scope

Table of Contents

HTML Include



The CI project provided the starting point for all OPNFV development activities. It starts by integrating stable versions of basic upstream projects, and from there creates a full development environment for OPNFV including automatic builds and basic verification. This is a very complex task and therefore needs a step by step approach.

Since the creation of Octopus project, OPNFV has evolved and initial tasks have been distributed to other infrastructure projects. The automatic build, deploy and test environment has been created and is in use on a variety of community labs.

Therefore the next major steps for Octopus project are in the area of organizing the various deployment variants of OPNFV in scenarios, defining the necessary processes and workflows and driving their support in the development environment.


All tooling for the CI pipeline is provided by the releng project and running automatically. Octopus is just defining the principles and make sure this can lead to a proper release process.

Starting with Brahmaputra release, OPNFV uses scenarios to provide the different deployment variants. Octopus provides the necessary mechanisms to work with the scenarios in long term, that is define the processes and necessary tools, so the scenarios can take their proper role in the OPNFV release process.

Octopus will also use this to define the necessary processes for DevOps releases.

Octopus Documentation

Creating/Configuring/Verifying Jenkins Jobs (PDF)


Additional Information/Links



Octopus is part of the INFRA working group, together with Releng, Pharos and Pharossecurity.  See more information at


Releng will provide necessary scripts to integrate scenario processes in the automated build, deploy and testing.

Scenario definition has very close relation to the installers (done in the respective projects), the lab configuration (done in the Pharos project) and the testing projects.

Scenario processes need to support all feature related projects. Therefore Octopus cannot do final decisions in project scope but prepare proposals and drive community level decisions via the TSC.


Octopus meetings have joined the INFRA meetings Weekly on Wednesday at 15:00 UTC (8am PST), see more at Infra Working Group

Urgent topics can be solven directly on IRC,  #opnfv-octopus @ Freenode.

See info on previous octopus meetings here:


  • Proposal for scenario related processes (lifecycle and workflows)
  • Templates for Scenario Description
  • Proposals for Scenario Consolidation

Key Project Facts

View Git file


  • Alan Pevec (
  • Bin Hu (
  • Carlos Goncalves (
  • Chengappa M R (
  • Chris Price (
  • Chris Wright (
  • Daniel Radez (
  • Dave Lenrow (
  • Dave Neary (
  • Dirk Kutscher (
  • Dongren Zhao ( )
  • Fatih Degirmenci ( )
  • Frank Brockners (
  • Ian Wells (
  • Jari Korpela (
  • Jia He (
  • Jiang Zhifeng(
  • Jonas Bjurel (
  • Jun Li (
  • Jun Zhang (
  • Mario Cho (
  • Marika Rytkonen (
  • Markus Berglund (
  • Mei Mei (
  • Ashlee Young (
  • Narinder Gupta (
  • Olivier Jacques (
  • Palani Chinnakannan (
  • Paul Quinn (
  • Prakash Ramchandran (
  • Qiqi Hu (
  • Reinaldo Penno (
  • Sajeev Manikkoth (
  • Stefan Berg (
  • Sudha Kumari (
  • Tadi Bhargava (
  • Ulrich Kleber (
  • Vasile Radoaca (
  • Wes Hayutin (
  • Xinyu Zhao (
  • Xiong Zhang ( )
  • Yu Zhang ( )
  • Zhifeng Jiang (
  • Vagish Shanmukh (

Mailing list:; use topic filter: [Octopus] 
Repository: octopus