On Mon, Jan 7, 2013 at 4:54 AM, Sebastien Goasguen <run...@gmail.com> wrote: > > On Dec 27, 2012, at 3:32 PM, Pranav Saxena <pranav.sax...@citrix.com> wrote: > >> [Sebastien] - Was the page updated to take into account all the discussions >> that happened on the ML ? >> >> Also what is in this feature branch ? I believe it was created before we had >> all the discussions. Does it contain the core marketplace code and the repo >> listings components ? It should only contain the "client"/plugin side. >> >> [Pranav] - Yes , Sebastien . So currently we just have a very basic client >> /plugin side code which creates a tab for marketplace tab on the cloudstack >> UI . Clicking on that would point to a new user interface which fetches the >> content and images/thumbnails dynamically from dummy config files . You can >> imagine it as a tile-like structure displaying N number of applications >> uploaded by each user. It does NOT contain any core marketplace code. >> > > I created a sub-task of CLOUDSTACK-619: > https://issues.apache.org/jira/browse/CLOUDSTACK-619 for the opennebula > integration. > > Right now, I don't believe the wiki page has been updated to reflect all the > discussion on the ML, see: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Marketplace+Proposal > > My plan is to use the opennebula marketplace api to populate the "dummy > config files". The marketplace server and api keys should probably be > configured as global settings. > > Who is doing a separate marketplace repo using your own code (not the UI > client code ) ? > > -Sebastien > > >
Sonny, you are currently the assignee in CLOUDSTACK-619. Do you think we can get the functional spec updated to reflect the list discussions on this topic? The spec, as it currently stands, still reflects some of the concepts that I have a standing veto on. I'd be very happy if we work around the issues that I (and others) have raised in the design and implementation.
