In order for OPNFV projects to integrate into installers subscribed to Genesis they must interface with Genesis to create and approve requirements. This page serves as the procedure for projects to follow in order to interface correctly with the Genesis project.

As previously stated by the Genesis project: It is the responsibility of the integrating project to support installers in adding their required functionality. This is a two-way agreement between Genesis/Installers and the project requesting integration, in which both parties agree to support the development work of implementing a requirement into installers. If a project creates a requirement for installers in Genesis and does not support the requirement as previously stated, the requirement will then be removed from the release.

Please follow the below steps in order to engage with the Genesis team:

1. Please send an email to the Genesis team informing them that you wish to create an installer or system requirement. Please include the following information:

• Name of the Project making the requirement
• The lead of your project
• A list of the proposed requirements
• The OPNFV release which you would like to implement these requirements
• The timeline for when you would like installer support for those requirements
• The overall goal or purpose of these requirements
• For each requirement give a high level description of the functionality and components it affects
• A rough scope of the work to implement your requirement

Example: trozet_proposal

2. You will receive notification that your requirement will be discussed in an upcoming Genesis meeting. You should have someone from your project present in that meeting as your requirement will be discussed. The Genesis team will then decide whether your proposal needs to be modified, needs more scope/information, or can be accepted.

3. Once accepted, a JIRA issue will be created by a member of the Genesis team for each of your requirements. This acceptance into JIRA does not mean your requirement is officially supported or approved. It means that the Genesis team has agreed to your proposed requirement, and that the requirement should be tracked by Genesis in JIRA until it is concrete enough to implement/support and take to a vote for official approval. It is your project's responsiblity to update the JIRA requirement with comments about the progress towards being able to implement/support your requirement. You can find the JIRA requirements currently proposed here: https://jira.opnfv.org/issues/?jql=project%20%3D%20GENESIS

4. Once the Genesis team feels a JIRA proposed requirement is ready to be put to a vote for official approval. Your JIRA requirement will be come a proposed patch in gerrit under the Genesis repo. The Genesis team (which consists of a lead from every subscribing installer project) will vote +1,-1 for the requirement. If a majority of leads vote +1, your requirement will be approved and officially a part of that release for Genesis installers. If your requirement is not approved, then you may choose to engage in a particular installer to see if you could be part of their installers as non-official Genesis requirement.