- OPNFV project team members do their blueprint draft reviews in Gerritt before submitting blueprints to OpenStack
- After reviews are completed in OPNFV, OPNFV project team member(s) submit blueprints/bug in OpenStack
- After blueprints are accepted, OpenStack blueprints will automatically list all relevant OpenStack Gerrit IDs
- OPNFV project team will add the blueprint links in a file in OPNFV that is similar to the current project INFO file
- Bitergia to track the OpenStack Gerrit IDs in the blueprints listed in the "INFO-like" file in step 4 above
- e.g. who's contributing to OpenStack, how their blueprints are progressing in OpenStack, etc.
- Bitergia has full access to our repo's incl. the INFO-like file.
- Can also get historical data (by adding old blueprint IDs)
- No need to do anything differently in OpenStack (e.g. no special tagging for OPNFV)
(Question: how do you deal with bugs without blueprints? Use bug reports?)
OpenStack and OPNFV projects and contacts
This list of the primary OpenStack and OPNFV projects, with links to the wikis and Project Technical Leaders, is designed to facilitate collaboration. Please follow the blueprint process below to request features in OpenStack.
You can find upstream collaboration activities on Bitergia by filtering on OpenStack.
|Project name||PTL||Project intention|
|Doctor||Tomi Juvonen||Fault management and maintenance project to develop and realize needed implementations for the OPNFV reference platform.||List of upstream activities|
|Functest||Functional Testing project. We reuse Rally and Tempest projects to perform tests. Rally is used to run Rally_sanity and start Tempest_smoke ((part of scenario validation), as well as Tempest_full or Rally_full (qualification).|