<div dir="ltr">Hi Daniel,<div class="gmail_extra"><br><br><div class="gmail_quote">On 4 February 2014 19:15, Daniel Dehennin <span dir="ltr"><<a href="mailto:daniel.dehennin@baby-gnu.org" target="_blank">daniel.dehennin@baby-gnu.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Jaime Melis <<a href="mailto:jmelis@opennebula.org">jmelis@opennebula.org</a>> writes:<br>
<br>
> Dear community,<br>
<br>
Hello,<br>
<div class="im"><br>
> we are pleased to announce the release of AppMarket 2.0 Beta:<br>
> <a href="http://opennebula.org/appmarket-2-0-beta-1-9-80/" target="_blank">http://opennebula.org/appmarket-2-0-beta-1-9-80/</a><br>
<br>
</div>I discuss with some colleagues used to some very expensive proprietary<br>
software, I gather their needs to study the opportunity to switch part<br>
of their infrastructure to ONE.<br>
<br>
What they call “catalogue” is very important to them and they have a<br>
use-flow based on it, I'm preparing some redmine requests but I take the<br>
opportunity of this thread to ask some questions.<br></blockquote><div><br></div><div>Feedback is always more than welcome. Feature requests for the AppMarket are handled through the Github issues.</div><div><a href="https://github.com/OpenNebula/addon-appmarket/issues?state=open">https://github.com/OpenNebula/addon-appmarket/issues?state=open</a> </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
NB: I do not setup an AppMarket yet.<br>
<div class="im"><br>
> This release brings many new goodies to the AppMarket:<br>
><br>
> AppMarket<br>
><br>
> - Multi-image Appliances: AppMarket Appliances can now have multiple disks,<br>
> which creates new possibilities to upload and register more complex and<br>
> feature complete Appliances.<br>
<br>
</div>Does this mean we can store and distribute a complete OneFlow service?<br></blockquote><div><br></div><div>Currently OneFlow services are not supported, but it wouldn't be difficult to add this option. Currently, multi-image support means you can provide more than one image/datablock/cdrom for a given VM (1 VM Template - Multiple Disks) and the relationship is defined in the opennebula_template attribute. We could include an opennebula_service_template attribute also.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Is there a way to clearly identify and group appliances by version, like:<br>
<br>
- one entry per appliance<br>
- one sub-entry per appliance version, with some sorting newest<br>
first/last<br>
<br></blockquote><div><br></div><div>Appliances currently have an attribute "version", you can update the appliances and increment this value, but the original appliances will disappear. Why do you want to keep old versions of the appliance?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I'm wondering about storage size, does AppMarket use the same storage as<br>
ONE or the disks are copied from ONE to AppMarket?<br>
<br>
I do not see clearly what is the storage requirement and how things get<br>
together between AppMarket/ONE/Sunstone.<br></blockquote><div><br></div><div>By default AppMarket does not store any image, just the metadata of the appliance, therefore the url is just a reference to the file and it could be stored in a third party server. This is how the OpenNebula Marketplace works [1]. When you import an appliance from the AppMarket to OpenNebula, a new image is create an the path attribute contains the url of the file; this file will be downloaded to the specified datastore by the DS driver.</div>
<div><br></div><div>In AppMarket 2.0 a new component was included, AppMarket Worker. This component allows you to create appliances from an OVA file. The OVA file is provided as an url and the worker will download, unpack and store the images and will update the appliance with the new urls for the files. The storage used by this component is not related to OpenNebula.</div>
<div><br></div><div>So you can create appliances in two different ways:</div><div>1. Providing the urls of the files and the opennebula_template. In this case the Worker will not do anything.</div><div>2. Providing an OVA file. In this case the Worker will unpack and store the files and will generate the opennebula_template and files section of the appliance.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im"><br>
> - Sunstone Import: users will be able to import registered Appliances to<br>
> OpenNebula via Sunstone by using pre-filled Image and Template creation<br>
> forms.<br>
><br>
> - Sunstone Views: two new Sunstone views: an AppMarket *admin* view, that<br>
> allows full control of the AppMarket, and a *user* view, that allows end<br>
> users to import registered appliances.<br>
<br>
</div>In the documentation “Create an Appliance”[1], we must provide “the URLs<br>
of the files and the OpenNebula template in the Appliance creation<br>
form”.<br>
<br>
Is there a way to push appliances from ONE/Sunstone, I read “From<br>
AppMarket 2.0 creating an appliance can be also done through the<br>
AppMarket tab in Sunstone”.<br>
<br>
Providing a new VM/OneFlow action “Store in AppMarket” could be<br>
great ;-)<br></blockquote><div><br></div><div>Currently, this is not supported but it would be a nifty feature, "Export VM/Service", a step forward in terms of portability</div><div><br></div><div>Thank you for your feedback</div>
<div><br class="">[1] <a href="http://marketplace.c12g.com/appliance">http://marketplace.c12g.com/appliance</a><br></div></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>--<br></div>Daniel Molina<br>Project Engineer<br>
OpenNebula - Flexible Enterprise Cloud Made Simple<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula</div>
</div></div>