Our 5.0 lab is running fine and I managed to create a new HTTP Market Place as describe in the documentation, but I have a little concern about its use:
Every OpenNebula instance which want to use this Market Place need SSH access to the server hosting the images which make it unusable as public Market Place for our users
Adding an Apps does not have a nice template wizard, only the VM template and App template with ATTRIBUTE = "VALUE". It could be interesting to create an App from a VM template or a OneFlow service template.
The AppMarkets are now depreacted in favour of HTTP Market Place, but this one lakes some features like catalogues.
Our 5.0 lab is running fine and I managed to create a new HTTP Market
Place as describe in the documentation, but I have a little concern about
its use:
Every OpenNebula instance which want to use this Market Place need
SSH access to the server hosting the images which make it unusable as
public Market Place for our users
Not really, the idea is that every zone has its own market place. This is
more like a distributed catalog. You can add then all the marketplaces (you
want, each one with its own ACLs potentially), and you’ll get a list of all
the apps in the app list.
When a user wants to “publish” an image he has to create the zone where the
image lives.
Adding an Apps does not have a nice template wizard, only the VM
template and App template with ATTRIBUTE = “VALUE”. It could be
interesting to create an App from a VM template or a OneFlow service
template.
Or maybe the HTTP Market Place will improve to get the missing features?
Please open this requests in the dev portal, our efforts will concentrate
on improving the new marketplace component as it is more integrated with
OpenNebula. We also plan to add more app types (flows etc…)
Every OpenNebula instance which want to use this Market Place need
SSH access to the server hosting the images which make it unusable as
public Market Place for our users
Not really, the idea is that every zone has its own market place. This is
more like a distributed catalog. You can add then all the marketplaces (you
want, each one with its own ACLs potentially), and you’ll get a list of all
the apps in the app list.
When a user wants to “publish” an image he has to create the zone where the
image lives.
I may have misunderstood something, the HTTP Maket Place does not have
the purpose to replace a public catalogue like OpenNebula - Marketplace?
So, to resume what I understood:
for all the OpenNebula I manage, I can add the same HTTP Market Place
to share Apps between all my zones/clusters.
For example, I have two clusters with disjoined datastores, I can
import VM images from cluster1 to the Maket Place and download them in
a datastore of cluster2.
Is that right?
I can not use the HTTP Market Place to expose Apps to the outside
world (not managed by me). For this, I need to setup the AppMarket
addon. Is that right?
Or maybe the HTTP Market Place will improve to get the missing features?
Please open this requests in the dev portal, our efforts will concentrate
on improving the new marketplace component as it is more integrated with
OpenNebula. We also plan to add more app types (flows etc…)
Yes, you are right. The new marketplaces (using any of its backends, http, s3,…) is aimed to replace the addon. Note also that the addon was intended to be used with in an organization and not to the outside world. Although you are right that the original addon does not require to federate zones. If this is your case, you can still use the addon in that mode and add a marketplace using the driver one
Yes right, and as you said this may happen across zones. Cluster1 in zone1 and cluster2 in zone2…
Although you are right that the original addon does not require to federate zones. If this is your case, you can still use the addon in that mode and add a marketplace using the driver one
I have some concerns about this addon, because the HTTP Market Place is
aimed to replace it, will the addon-appmarket continue to be supported?
For our users usage[1], federate zones is not really possible, so we
definitely need a central place to host app template and images.
We may want to make some contributions to addon-appmarket in some future
to permit to upload images in addition to register app templates. I just
need to convince our product owner
Yes right, and as you said this may happen across zones. Cluster1 in zone1 and cluster2 in zone2…
Ok, so the App definitions are shared by all federated zones, Thanks for
the explanation.
Maybe we can evolve the current marketplace to allow anonymous access. This will impact on OpenNebula Auth subsystem ACLs and the like. Uploading will require authentication though.
Sorry to hijack this thread, I am trying to setup HTTP Market place and find this as most relevant in this forum
I have setup Apache Web Server with a public dir configured as given and is accessible via say, http://opennebula1/appliances. Apache server is running on same machine as Opennebula so i have skipped BRIDGE_LIST configuration and all is fine. I can export / download / import image/templates from local opennebula instance
If i need to use this market place from another opennebula instance (say opennebula2) - what would be my configuration? do i need to add BRIDGE_LIST to my first opennebula server where apache market place run for upload ? does it also require passwordless ssh access to opennebula1/market, as i observe it attempts ssh when market is run on different machine?
Is it not using http transfer - as we prefer http than ssh?
Moreover, i don’t see the apps listed in opennebula2 (created on opennebula1). Does it not enough to just have http://opennebula1/appliances access to list apps? And also possibly download / import apps ?
Please advise. Your response is very much appreciated
