Hi, I’ve developed new marketplace driver as alternative to official one.
I like an idea to store appliances configuration in git, so driver have pretty simple architecture:
All appliances stored as simple manifests, each one in single folder, and have three files:
Hi, main idea is that you don’t need any special services on the server to make it working (eg. mongo, ruby, etc.)
So you can generate all the marketplace statically and upload to any http/s3 hosting, eg even github pages (like now), it will working fine.
You’re right, right now example site is uses the appliances metadata from the official marketplace, but later I’ll replace it with my own images generated automatically using
This like organization is easy to manage and track versioning using Git
This would be a great contribution to the OpenNebula Add-on Catalog. I know that you have contributed to our catalog before, but take a look at the steps that we have outlined for Add-on Catalog contribution, (https://github.com/OpenNebula/one/wiki/How-to-participate-in-Add_on-Development). Once you complete the steps 1 through 4, let me know, and we will pick things up at step 5 to get the Add-on published in our Catalog and hosted on our GitHub.
Right now, you created the repository within your own GitHub (“kvaps/opennebula-static-marketplace”). In terms of being part of the “official” OpenNebula Add-on Catalog, is should be created and managed in the OpenNebula GitHub - as “opennebula/static-marketplace”.