The Ecosystem Catalog is coordinated through the OpenNebula developers mailing lists.

• Types of Components
• Requirements of New Components
• How to Submit a New Component

The OpenNebula project does not endorse or recommend any products listed, and cannot vouch for the quality or reliability of any of them.

The OpenNebula Ecosystem is formed by:

• Tools providing added value on top of OpenNebula clouds by leveraging its APIs, from service or VM image managers to user-friendly dashboards
• Extensions adding new functionality to OpenNebula cloud instances, from support for enforcement of energy policies or advance reservation of capacity

Once you've developed a new tool for OpenNebula, you'll want to make sure people can find out about and download it. Note that we do not perform filtering on the basis of technical issues. This is because the OpenNebula Ecosystem respects and suggests variety of technical approaches. It does not fear innovation or even internal confrontation between projects which overlap in functionality. We only filter components on the basis of the likeliness of them becoming successful tools.

The basic requirements are:

• A working codebase tested in the version you claim to support
• An active development and support
• A potential user community
• A web site with information about the component
• An open-source license

Moreover we applaud the following design and development principles in the components:

• Collaborative open-source software development
• Commercial-friendly license
• High quality software
• Implementation of standards
• Security as a mandatory feature

1. Send to the developers mailing list the following information

• Name of the Component
• URL of the Component
• Brief Description (30 words max)
• Type (tool/extension)
• License (proprietary/OSS)
• OpenNebula Version
• Author (person or organization developing the code)
• E-mail

2. The Community Manager will evaluate your proposal and respond within one week time

3. If approved, the webmaster will create a page in the ecosystem namespace, and you will receive an account to update its contents. You will also receive an account for our blog.

4. You should update your page with all needed documentation on how to install and use the component and give users a pretty good idea what it does before installing it. Adding screenshots might be a good idea as well. At the top of the component page a few metadata fields will be filled. Uploads are not allowed, so you need to host your plugin files somewhere else. We recommend to manage your source with a Revision Control System using any public repository host.

5. Notify through the developers mailing list when the component page is ready for review.

6. Prepare a blog post to announce your participation in the ecosystem and to give visibility of the new component.

7. The Community Manager will publish your blog post and announce the new component in the developers mailing list and in other community instruments.