fuel_opnfv_integrated-project-guidelines
This is an old revision of the document!
How to become a Fuel@OPNFV Integrated project
Integration request process
- If your project has the intent to become an OPNFV core-integrated project (part of the mandatory requirements for OPNFV Genesis member installers) - you need to follow this process: How to interface with Genesis? Work procedures
- This will generate a workflow of genesis committer voting which will either result in a mandatory integration of your project in all Genesis member installers or will be abandoned.
- If you instead do not yet want to become a core integrated project, and only want to integrate your project with with one or a few projects - like Fuel@OPNFV. You should issue a Jira request in the Fuel@OPNFV Jira namespace - preliminary indicating (As the integration iterations goes along, these items will be refined):
- Project description
- Purpose
- Dependencies (Packages, Patches, Linux kernel, etc)
- High-availability model
- Upgrade model
- Managed objects (configuration, Fault management, Performance management, etc.)
- Available logs, etc.
- ETA for functional code freeze.
- ETA for integration adaptation to Fuel@OPNFV - E.g. a "Fuel plug-in"
- In any case - no matter the model followed, an integrated project will be responsible for the integration with Fuel@OPNFV and the development of:
- A functional Fuel Plug-in.
- Instrumentation of configuration in accordance with the Fuel plug-in concept, as well as a config.yaml template fragment for the plug-in.
- Build environment, including population of the plug-in to the fuel@OPNFV .iso artifact.
- Integration/build time tests.
- Functional tests, coordinated with the OPNFV Func-test project.
- Higher order tests - I.e. Yard-stick test cases.
- The acknowledgement of the Fuel@OPNFV integration request is that the corresponding Jira request is assigned to the project lead of the integrated project-lead.
- Once agreed on in which Fuel@OPNFV project work-package the integration should be due, the Jira request goes into status "In progress" - and from now on the integrated project is part of fuel@OPNFV and is expected to:
- Attend Fuel@OPNFV meetings
- Follow Fuel@OPNFV committer decisions and plans
- And execute according to out-set plans
- If an Integrated project fails to deliver according to plan, quality expectations, or outset dependencies, Fuel@OPNF commiters may through voting decide to exclude the integrated project from a work package/mile-stone, or from a project release as a whole.
fuel_opnfv_integrated-project-guidelines.1443898745.txt.gz · Last modified: 2015/10/03 18:59 by Jonas Bjurel
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
