[Fiware-webui] Creating Blueprints: WebUI Recipes in FI-Lab

Torsten Spieldenner torsten.spieldenner at dfki.de
Thu Nov 6 14:38:05 CET 2014


Hi again,

quick update, I got feedback to some of the questions I asked on JIRA 
earlier:

In fact, having images as parts of blueprints is currently not 
supported. It is on the road map for the future, but I guess for the 
current version of our bundles we have to limit ourselves to the recipes.

The recipe for XML3D got approved this morning.

@Jarkko: What's the status of the GIS Data Provider recipe? As soon as 
this is available in FI-Lab, I could assemble the blueprint for the 
bundle that we planned at DFKI.

I guess I am going to explain installation of the demo client in the 
bundle documentation then, and let the bundle blueprint just set up the 
needed VMs.

Best,
Torsten

Am 06.11.14 um 10:39 AM schrieb Torsten Spieldenner:
> Hello,
>
> I have spent yesterday with figuring out how to create the bundle 
> blueprint in FI-LAB. At this point, all GE's that are needed are in 
> place in my FI-Lab-Project. These are one POI-Data-Provider Instance 
> that I installed from the Image that is available in the Lab. Second 
> is an instance of GIS data provider that I set up manually, following 
> the step-by-step instructions in the installation guide, based on the 
> Ubuntu14.04 Image from FI-Lab. Third one hosts the 3D-UI-XML3D client 
> that runs Stefans GIS/POI Demo which he also showed at ECFI. This one 
> in addition has Stefans 3D-Map-Tiles provider installed, which is a 
> FI-Content SE that provides a nice frontend for the 3D maps to the 
> 3D-UI-XML3D client.
>
> Now when I tried to create a blueprint, I had to find out that when it 
> comes to select which software should be installed on the different 
> VMs of the blueprint, the only possibility is to select from a very 
> limited set of what seems to be recipes that have found their way to  
> the catalogue. In this list "software in catalogue", I could identify 
> only two GE from our group, which are augmentedreality 3.3.3 and 
> poi_dp 3.3.3
>
> So in summary, there are two points which are still unclear to me:
>
> 1) How to get specific demo client software into the bundles
> 2) Where to find our remaining GE other than AR and POI DP
>
> In general, I would suggest we check again if - and if yes,  where - 
> our recipes got stuck on their way to the catalogue. For example, if 
> feedback concerning recipes is pending, or if feedback was ok, but the 
> software just does not appear in the list. I myself have filed an 
> issue about the delayed XML3D recipe approval in JIRA in the 
> Lab-Tracker with GEi Deployment - Component, like Manuel explained 
> yesterday. So my suggestion would be to file an issue for each recipe 
> for which feedback is still pending, or for which feedback was 
> positive but that does not appear in the Lab yet. As soon as the 
> recipes are available, we can at least create Blueprint-Templates that 
> install the set of GE via recipe.
>
> Moreover, I am going to find out whether we can already start to 
> create the catalogue entries for the bundles while we are waiting for 
> our software to become available. Maybe one way to provide the demo 
> client could be to give a manual installation guideline in the bundle 
> documentation, and skip automatic install for the client.
>
> Best,
> Torsten
>

-- 
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------




More information about the Fiware-webui mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy