You can report a bug by opening a new issue in the OpenNebula Development Portal. The priority of a Bug issue will be graded based on its severity (Low, Normal, High). Be sure to specify the version of OpenNebula you are using.

A Bug issue can be:

• Pending, needs to be verified
• New, the bug has been verified
• Assigned, someone is working on the bug
• Closed, the issue is fixed, could not be reproduced (worksforme) or duplicates another one

You may use the Development Portal to make feature requests, just open a new issue and label it as Request. The issue will be used to track the discussions about the new feature. You should also specify if you are planing to allocate resources to implement the new feature. Once the new issue is created, you can bring it up for discussion on the developers mailing list.

We will try to contact you as soon as possible to have more information and to give you a first feedback about your Request issue. Please consider that this can take some time, and it is usually not done until the next release cycle at the earliest. When we update the roadmap of the project and plan the features for the next release, we prioritize:

• The features demanded by the projects and organizations sponsoring the open-source project
• The most demanded features by the community

Your Request issue will be pending till:

• It is decided that is not in the scope of the project and closed
• It is interesting for the OpenNebula community and will be added as Backlog or Feature

Backlog issues are long-medium term roadmap features to be implemented in OpenNebula. The priority of the issues will be graded (Low, Normal, High). A backlog issue will be pending until:

• It is closed because it is no longer interesting for the OpenNebula community
• It is moved to the Feature list

Feature issues are short term features roadmap features. New OpenNebula releases will be made of Feature issues. The priority of the features will be graded (Low, Normal, High). A Feature will be;

• New, no one is working on the issue.
• Assigned, a developer is working on it.
• Closed, feature is ready and documented.

There are two different ways to submit a bug or feature patch. In both cases, it is understood that your patch addresses an open issue at the OpenNebula Development Portal to better track them. You will need to create an account in dev.opennebula.org if you do not already have one. Update the issue with a full description of what you have done and describe your tests. When your patch is reviewed, it may be accepted as-is or you may be asked to make changes. Code commits (after review) with be implemented as named commits.

Bug and feature patches can be uploaded to the open issue in the OpenNebula Development Portal (please avoid submitting them to the mailing list).

We prefer patches to be submitted in unified diff format: <xterm>diff -u original_file.cc new_file.cc</xterm>

If you have checked out the sources from git, then use: <xterm>git format-patch origin/master</xterm>

You can alternatively use the github Pull Request model to the OpenNebula public Git repository:

• Fork it
• Create a branch (git checkout -b my_markup)
• Commit your changes (git commit -am “My changes”)
• Push to the branch (git push origin my_markup)
• Create a Pull Request to this repository from your new branch

Finally do not forget to update the open issue with a link to the Pull Request.

Patches that fix a bug or provide a minor enhancement might be accepted without a Contributor License Agreement being completed. Major enhancements require a valid Contributor License Agreement. More information.

Before entering a new issue following the Feature Request process, first check if there is already an open issue addressing a similar feature. Describe your work plan and the resources you are planning to allocate in the issue. Then you should bring it up for discussion on the developers mailing list. Other developers may have suggestions, and this ensures that the new feature is aligned with the roadmap and other features being developed. It is important to be sure that you're not doing redundant work.

New features can be:

• Enhancements in the OpenNebula core distribution. These should be contributed by following the process to contribute feature patches.
• New interfaces and drivers that extend platform support. New tools, interfaces and drivers that enlarge the platform technologies and services that OpenNebula can interface with are published on the Add-ons catalog. These may be incorporated into the main OpenNebula distribution after an incubation process. Visit our Add-on section for more information about how to contribute new Add-ons or contribute to an existing Add-on.
• Integration with Cloud tools extensions. Third-party tools and extensions that complement or extend the functionality provided by OpenNebula are listed on the Ecosystem catalog. Visit our Ecosystem section for more information about how to submit new components.

Small patches which fix a bug or provide a minor enhancement might be accepted without a Contributor License Agreement being completed. These contributions do not add functionality or new intellectual property in its generally accepted sense, and so are too insubstantial to be protected by copyright. These patches must not have any copyright or license attached to them.

Significant patches which provide a major enhancement, and Add-ons incorporated into the OpenNebula distribution require the completion of a Contributor License Agreement. These contributions add functionality or new intellectual property in its generally accepted sense, and so have to be protected by copyright. These contributions must have a copyright attached to them. Before we can merge these contributions, you will need to read and agree to our Individual Contributor License Agreement. If you are contributing on behalf of a company, an authorized representative of your company should sign a Corporate Contributor License Agreement. You can send us a PDF version of the completed and signed agreement, or contact us to send you simple electronic forms through Echosign. All accepted contributions will be released as part of OpenNebula under the Apache v2.0 license.