From acs at bitergia.com Mon Jul 6 10:57:06 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 06 Jul 2015 10:57:06 +0200 Subject: [Fiware-developer-experience] Bitergia team Message-ID: <1436173026.2359.119.camel@bitergia.com> Hi all! Nice to have this mailing lists working. David, Alberto and me will be attending this mailing list, from Bitergia team. We will be mainly involved in the backend for the developers guide application. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Mon Jul 6 11:09:24 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 06 Jul 2015 11:09:24 +0200 Subject: [Fiware-developer-experience] Restaurant Context design for Orion Message-ID: <1436173764.2359.123.camel@bitergia.com> Hi all! In restaurants we need to store recommendations. In Orion we will store the context information (name, address ...) but this changing (and growing) information, recommendations, how should be managed in Orion? An approach could be to store the last recommendation in context information (orion) and the history of recommendations, to be stored in MySQL (for example) using cygnus. Thoughts? Should we move this kind of questions to stackoverflow? Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Mon Jul 6 14:53:11 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Mon, 6 Jul 2015 13:53:11 +0100 Subject: [Fiware-developer-experience] Restaurant Context design for Orion In-Reply-To: <1436173764.2359.123.camel@bitergia.com> References: <1436173764.2359.123.camel@bitergia.com> Message-ID: Hi! Trying to help, here is our opinion Since recommendations or reviews are persistent information and not context information, we believe that using Orion Context Broker may not be the best approach. In our opinion, probably the simplest option is to store the data directly in a DB and access it using a custom REST API like: http:///addRecommendation/ [post] body [ { "restaurant" : "ElBulli", "Quality" : "5", "Price" : "3", "Text" : "Great place for ....." }, ... ] -- http:///getRecommendation/ElBulli [get] Response { "restaurant": "ElBulli", "recommendations":[ { "Quality" : "5", "Price" : "3", "Text" : "Great place for ....." }, { "Quality" : "5", "Price" : "4", "Text" : "Great place for ....." }, ..... ] } If we want to force to use Orion, an approach could be to insert the last recommendation as context and use another GE to retrieve historical data: - We don't have experience using STH but we think that we could use it and ask for all recommendations of a particular restaurant in a specified time, or ask for the sum of elements and make an average of reviews. - We could use Cosmos and it may be interesting if we think that recommendations are Big Data. The problem could be that create an instance of Cosmos is not easy. By the way. ULPGC team prepared a small system to publish data stored in PosgreSQL DB using CKAN. It may be useful at any time. If we need it, just ask for it Kind regards, ULPGC Team 2015-07-06 10:09 GMT+01:00 Alvaro del Castillo : > Hi all! > > In restaurants we need to store recommendations. In Orion we will store > the context information (name, address ...) but this changing (and > growing) information, recommendations, how should be managed in Orion? > > An approach could be to store the last recommendation in context > information (orion) and the history of recommendations, to be stored in > MySQL (for example) using cygnus. > > Thoughts? Should we move this kind of questions to stackoverflow? > > Cheers > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From josemanuel.canterafonseca at telefonica.com Mon Jul 6 15:11:19 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Mon, 6 Jul 2015 13:11:19 +0000 Subject: [Fiware-developer-experience] Restaurant Context design for Orion Message-ID: Responding in an empty emails as I didn't realise I was not subscribed to the list I think customer reviews are part of the context information to be stored in Orion. But reviews are entities associated to both customers and restaurants. So we will have something like what is proposed below By the way Alvaro, please provide a first draft of the data models to be used. I would like to review them before we start coding ---- Restaurant { id: "Res-5678", name: "Casa Pepa", average_score: { "place": 7, "service": 8, "food": 5 }, "location": xxxx } Review { "id": "Review-890", "author": "jmcantera", "subject": "Res-5678", "creationDate", "xxxx", "score": { } } Customer { "id": "jmcantera", "name": "Jose Manuel Cantera" } ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Mon Jul 6 15:55:37 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 06 Jul 2015 15:55:37 +0200 Subject: [Fiware-developer-experience] Restaurant Context design for Orion In-Reply-To: References: <1436173764.2359.123.camel@bitergia.com> Message-ID: <1436190937.2359.126.camel@bitergia.com> Hi! El lun, 06-07-2015 a las 13:53 +0100, Pablo Fern?ndez Moniz escribi?: > Hi! > > > Trying to help, here is our opinion > Thanks! > > Since recommendations or reviews are persistent information and not > context information, we believe that using Orion Context Broker may > not be the best approach. > > > In our opinion, probably the simplest option is to store the data > directly in a DB and access it using a custom REST API like: > > > http:///addRecommendation/ [post] > body > [ > { > "restaurant" : "ElBulli", > "Quality" : "5", > "Price" : "3", > "Text" : "Great place for ....." > }, > ... > ] > > > -- > http:///getRecommendation/ElBulli [get] > Response > { > "restaurant": "ElBulli", > "recommendations":[ > { > "Quality" : "5", > "Price" : "3", > "Text" : "Great place for ....." > }, > { > "Quality" : "5", > "Price" : "4", > "Text" : "Great place for ....." > }, > ..... > ] > } > > > > If we want to force to use Orion, an approach could be to insert the > last recommendation as context and use another GE to retrieve > historical data: Great! This is the same approach we were thinking. > > > * We don't have experience using STH but we think that we could > use it and ask for all recommendations of a particular > restaurant in a specified time, or ask for the sum of elements > and make an average of reviews. > * We could use Cosmos and it may be interesting if we think that > recommendations are Big Data. The problem could be that create > an instance of Cosmos is not easy. In then current approach, we using Cygnus for storing the history. We have used CKAN and MySQL as backend. > By the way. ULPGC team prepared a small system to publish data stored > in PosgreSQL DB using CKAN. It may be useful at any time. If we need > it, just ask for it > Hmmm, I think PosgreSQL is not a natural tech for Orion+Cygnus stack. But is is good to have this work in mind. Thanks! Cheers > > > > Kind regards, > > > ULPGC Team > > 2015-07-06 10:09 GMT+01:00 Alvaro del Castillo : > Hi all! > > In restaurants we need to store recommendations. In Orion we > will store > the context information (name, address ...) but this changing > (and > growing) information, recommendations, how should be managed > in Orion? > > An approach could be to store the last recommendation in > context > information (orion) and the history of recommendations, to be > stored in > MySQL (for example) using cygnus. > > Thoughts? Should we move this kind of questions to > stackoverflow? > > Cheers > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > > > > -- > > Pablo Fern?ndez Moniz > > GIT Analyst > > > Web Linkedin Twitter > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Mon Jul 6 15:59:26 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 06 Jul 2015 15:59:26 +0200 Subject: [Fiware-developer-experience] Restaurant Context design for Orion In-Reply-To: References: Message-ID: <1436191166.2359.130.camel@bitergia.com> Hi! El lun, 06-07-2015 a las 13:11 +0000, JOSE MANUEL CANTERA FONSECA escribi?: > Responding in an empty emails as I didn?t realise I was not subscribed > to the list > > > I think customer reviews are part of the context information to be > stored in Orion. But reviews are entities associated to both customers > and restaurants. So we will have something like what is proposed below Good approach, context information, but not from a restaurant entity, but from a specific entity: reviews. Not sure if we are forcing orion usage a bit, but it is a developer guide app for it, so it could be ok. > > > By the way Alvaro, please provide a first draft of the data models to > be used. I would like to review them before we start coding We are playing with the code to load the data in Orion, in an flexible approach so the model could be changed later. Give us one-two days before having a first data model. Cheers! > > > ---- > > > Restaurant > > > { > id: ?Res-5678?, > name: ?Casa Pepa?, > average_score: { > ?place?: 7, > ?service?: 8, > ?food?: 5 > }, > ?location?: xxxx > } > > > Review > > { > ?id?: ?Review-890?, > ?author?: ?jmcantera?, > ?subject?: ?Res-5678?, > ?creationDate?, ?xxxx?, > ?score?: { > } > } > > > Customer > > > { > ?id?: ?jmcantera?, > ?name?: ?Jose Manuel Cantera? > } > > > ______________________________________________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener informaci?n privilegiada o confidencial y > es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > senhoria o destinat?rio indicado, fica notificado de que a leitura, > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destrui??o > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Mon Jul 6 16:03:17 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 06 Jul 2015 16:03:17 +0200 Subject: [Fiware-developer-experience] Docker base images Message-ID: <1436191397.2359.133.camel@bitergia.com> Hi all! Right now we are using as base images for CentOS and Ubuntu the Bitergia ones: https://registry.hub.docker.com/u/bitergia/fiware-orion/dockerfile/ The idea is to change: FROM bitergia/centos-6:latest to the official one. We have started with our own images to control totally what is included in the images, but official images are also traceable. So our bet is to change to official images once we have all images ready in Docker Hub. Probably now changes will be needed for the user of devguide images. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From josemanuel.canterafonseca at telefonica.com Mon Jul 6 18:15:45 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Mon, 6 Jul 2015 16:15:45 +0000 Subject: [Fiware-developer-experience] =?utf-8?q?FW=3A_=28FIWARE=29_______?= =?utf-8?q?__The_=C2=B3FIWARE_Media_=26_Content_Lab=C2=B2_is_up_and_runnin?= =?utf-8?q?g=2C_and_we_need_your_feedbacks!?= In-Reply-To: References: Message-ID: It might serve us as inspiration De: "Serge TRAVERT (Basecamp)" > Responder a: "message-44613856-0786ccdafac0d49696ff4752 at basecamp.com" > Fecha: lunes, 6 de julio de 2015, 16:51 Para: Jose Manuel Cantera Fonseca > Asunto: (FIWARE) The ?FIWARE Media & Content Lab? is up and running, and we need your feedbacks! Write ABOVE THIS LINE to post a reply or view this on Basecamp [Serge TRAVERT] Serge TRAVERT posted this message on Basecamp. The ?FIWARE Media & Content Lab? is up and running, and we need your feedbacks! FIcontent has recently released an online ?Lab? to deliver FIWARE Enablers for media and content applications, in order to complement the FIWARE catalogue of Generic Enablers (GEs). This new website, called the ?FIWARE Media & Content Lab? addresses the needs of SMEs and developers by means of four support levels: * Discover: Access information about the Enablers (Description / Programmer guide / Installation guide / Tutorial / Usage videos / Terms & Conditions / How to get support) * Try: Test live demos of Enablers * Tweak: Modify and run the Enablers client-side code, in a developer playground * Run: Start and monitor instances of Enablers via various SysOp tools (Layered on top of FIWARE Lab, using advanced tools for facilitating usage and deployment) The FIWARE Media & Content Lab is accessible at http://lab.mediafi.org For more information, please visit http://mediafi.org/the-fiware-media-content-lab-is-up-and-running/ We are very much interested to receive your feedbacks on the FIWARE Media & Content Lab: what you like, what may prevent using it, any suggestions for improvements, and finally whether you would recommend using it to your subgrantees. Kind regards, Serge Travert View this on Basecamp This email was sent to: Alexander Berlin, Thierry Baujard, Blanca Rodr?guez, gael maugis, Nuno Varandas, Cristina Cullell-March, Lena Arndal, Laura Kohler, Olaf-Gerd Gemein, simona torre, Grigoris Chatzikostas, Paul Pelsmaeker, Raimund Broechler, Adri?n Ferrero, Siobhan McQuaid, Harald Sundmaeker, Pentti Launonen, Susanna Avessta, Juanjo Hierro, Margarita Tremblay, Angeles Tejado, Thomas Michael Bohnert, Paul Cunningham, Satu V?in?m?, Alexander von Jagwitz, Lies Boghaert, silvia de la maza, Martin Potts, Mirko Ross, antonis.ramfos at intrasoft-intl.com, Carlos Cerqueira, Fabio Pianesi, Federico Alvarez, Francisco Bujan, Gabriella Cattaneo, Goran Hodoba, Ingrid Willems, Sjaak Wolfert, Jesus Villasante, Arian Zwegers, Ragnar Bergstr?m, Cristian Olimid , Bogdan Ceobanu, Conchi Anton, Maria Mota Viegas, Peter FATELNIG, Pablo Honrubia, Stefan Stengel, Youssef Sabbah, Albert Alonso, Ibai Larrabide, Paolo Lombardi, dechiara at fbk.eu, Veronica Barchetti, Rasmus Ulslev Pedersen, Stefano De Panfilis, J. Manrique Lopez, Anastasios Stilianidis, Alexandra Rudl, federico.alvarez at upm.es, Monique Calisti, Rebecca Huxley, Theodore Zahariadis, Christian Wolff, Ramon Valles, Carmen Mac Williams, Ciro Acedo, Yves-Marie Le Pann?rer, Pierre Fran?ois, Fabio Antonelli, Hanna Niemi-Hugaerts, Koen De Vos, Fabio Puglia, Domingo Legua, Miriam Bajo , Vanessa Vanhumbeeck, Andrea, silvio cretti, Luca Capra, Pilar Anad?n, Nuria Rodriguez, dragan.m.ivanovic at gmail.com, Adam Tarcsi, Stefan G?llner, sebastian muller, Daniel Twal, Gianluca Dettori, Mladen Radisic, Maja Radisic, Caterina Bissoni, Bel?n Kayser, Alberto Sesmero, Theofilos Mylonas, maurizio cecchi, sergio gusmeroli, Anastasius Gavras, Fiona Williams, Pieter van der Linden, Isobel Fletcher, Bernard Garvey, Alexandra Choli, Gaber Cerle, Susana Garayoa, Ivo Holanec, Eleonora Villanova, Metavallon, ilkka.lakaniemi at aalto.fi, Nuria de Lama, Antonello Monti, Ana Garcia, antonio cimmino, Claudia Guglielmina, Dave Clarke, dgimenez at isdefe.es, gilles.grattard at orange.com, Fourdeux Henri, Uwe Herzog, Jacques Magen, julie.marguerite at thalesgroup.com, Laurent HERAULT, livdo at tid.es, Oscar Lazaro, Pascal Bisson, werner.mohr at nsn.com, Federico Facca, Fernando Sandoval, Javier Garrido Chamorro, Fco. Javier Iglesias, Niels Genzmer, Katariina Malmberg, Nathalie Danse, john-paul.moore at atos.net, Assaf Mendelson, Rumen Dobrinsky, qianni.zhang at qmul.ac.uk, frontierCities at fi-frontierCities.eu, Bernardita Cardenas, Zuzana Cerna, Johanna Schepers, Alicia Gonz?lez, Marcin Gut, Erkka Suopanki, remi.ronchaud at inria.fr, Susana Louren?o, Andreana Casaramona, Alberto Soraci, Jens schumacher, Ina Lauth, Ina Lauth, Carole Thurston, sandragarcia at bic.es, Vegard Engen, Clare Hooper, Fiona Rivera, Marcelo Royan, europe at tvt.fr, Kaisa Sibelius, Pau Pamplona, Thomas Winkler, info at frontierservices.eu, Suvi Kukkonen, Pauliina Smeds, Katerina Achinioti, stefano modafferi, Se?n J. Burke, Miguel Angel Comin, Mitja Jermol, Santeri Paavolainen, Jaakko Ik?valko, Susanne K., Sven Lindmark, Maurin Lagassat, Miguel Carrillo, Belen Manchego, Masa Mimica, Benjamin Gei?ler, Miguel Alarc?n, Mike Surridge, Thomas Van der Auwermeulen, Bassem Nasser, Jose Miguel Garrido, Ilenia Ventroni, Gaelle Lanckmans, Mikkel Toft-Olsen, David Garc?a, ilknur Chulani, Katalin Viola, Jose Gonzalez, Max Niederhofer, Dan Crowley, Stefania Aguzzi, gmicheletti at idc.com, Janwillem.kruize at wur.nl, Charlotte Timmermans, Lisa Pattyn, Nadia Djeziri, Peter Einramhof, Andrea Siviero, Rasto Petras, Hugo Vivier, mika.rantakokko at cie.fi, Ari Okkonen, Cristian Dascalu, amir raveh, Ayelet Hashachar Baram, Vincent Demortier, Imre Hild, Irene Fialka, Peter Tschuchnig, Jana Hodbodova, A'dam Olszewski, Diego De Biasio, Adolfo Borrero, Charo Jimenez, Jakub Hruska, murp at zhaw.ch, Cristian Dascalu, Franck Le Gall, philippe.cousin at eglobalmark.com, jr at livinglabs-global.com, vesna boskovic, Leandro Guillen, Marta Prados, Malena Donato, Lucian Cosoi, Norman G?lc?, Estanislao Fern?ndez, Johnny Waterschoot, Sophie Fensterbank, joel.riga at orange.fr, Martin Weber, Peter Muryshkin, Lukas Vonnahme, Marie Bourdon, Fernando Lopez, Milon Gupta, Marco Terrinoni, Jose M. Cantera, Stephen Phillips, Simona Laza, eenev at abv.bg, jacquespacheco at gmail.com, Vojtech Krmicek, sdena at upatras.gr, Odysseas Koufopavlou, mentzelopoulos at psp.org.gr, neill at atrovate.com, rokas.tamosiunas at gmail.com, Marta Moksa, Ale? Pustovrh, Ana Victoria, jm at corchado.net, Christos Tranoris, Haluk G?kmen, Giulia Costa, Padraic McKeever, Philipp Slusallek, Pislar Ionut, krijn poppe, Ra?l S?nchez, Anna Maria Radu, Pasquale Vitale, Roi Rodr?uez, Pierre-Yves DANET, Miika Tuisku, David Bernal, Valentina Grillea, and Serge TRAVERT. Stop receiving emails about this message. Want less email from Basecamp? Get a digest of your notifications every few hours instead, or go to your Basecamp settings to choose which emails you receive. [http://dash.37signals.com/beanstalk/beacon.gif?return_receipt=RR/BCX/3bd2c244db694b29beeeb2e1114c2fd0] ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Tue Jul 7 10:39:41 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 07 Jul 2015 10:39:41 +0200 Subject: [Fiware-developer-experience] A data model propolsa for devguide app Message-ID: <1436258381.2359.137.camel@bitergia.com> Hi all! Here goes a proposal using the original requirements and the comments in this list. Maybe we can work with Google Docs to refine it. It is a first proposal totally open to modifications and comments! DATA MODEL PROPOSAL FOR DEVGUIDE APP: h2. Restaurant * id * name * description * address * email * phone * room * url * Temperature and humidity cuisine and room * customer satisfaction (avg_rating) h2. Reviews * id * by customer * to restaurant * review text * food rating (0-10) * place rating (0-10) * service rating (0-10) h2. Reservations * id * daytime * number of people * cancelled h2. Customer * id * name * email h2. Manager * id * name * email * rol Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Tue Jul 7 10:45:42 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 07 Jul 2015 10:45:42 +0200 Subject: [Fiware-developer-experience] Tool for loading restaurant data to the devguide app Message-ID: <1436258742.2359.142.camel@bitergia.com> Hi all, We have a first version for the tool for loading restaurant data to the devguide app . It is using Euskadi Open Data restaurants list, which is CC by (we can use the data as we consider. we just need to make clear the origin of this data). https://github.com/Bitergia/fiware-devguide-app/blob/master/server/restaurant_feeder.js The data loaded includes geocodes for restaurants. We use Google API to convert address to geocodes. We cache this translation so it should be pretty quick to reproduce the full process from scratch and to add new restaurants. We need to clear the current REST API (we are already using it for the data loading) and complete with the needs from ULPG team. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Tue Jul 7 11:03:24 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 07 Jul 2015 11:03:24 +0200 Subject: [Fiware-developer-experience] =?iso-8859-1?q?FW=3A_=28FIWARE=29__?= =?iso-8859-1?q?_______The_=B3FIWARE_Media_=26_Content_Lab=B2_is_up_and_ru?= =?iso-8859-1?q?nning=2C_and_we_need_your_feedbacks!?= In-Reply-To: References: Message-ID: <1436259804.2359.150.camel@bitergia.com> Hi! El lun, 06-07-2015 a las 16:15 +0000, JOSE MANUEL CANTERA FONSECA escribi?: > It might serve us as inspiration > I have tried to play with the developer tools but it is not working: http://playground.mediafi.org:8000/f6d8ef1a53b1005fee1a9f061482fdf42494b2af/fic2-cenr/ The more interesting stuff for use, IMHO, is: http://lab.mediafi.org/run.html They are also proposing using docker for testing the Enablers in the developer machine. The docker images: https://registry.hub.docker.com/repos/fic2/ 10 docker machines, with the first one from 6 months ago. There is no information in the description of some of the docker images like: https://registry.hub.docker.com/u/fic2/se_3d-map-tiles/ Others have better documentation: https://registry.hub.docker.com/u/fic2/ocdb/ I think we should try to document all then images at a similar level. I have not found docker-compose in their images. It is great to see a convergence around docker tech in the project. It will be easier to adopt the tech globally. Cheers > > De: "Serge TRAVERT (Basecamp)" > Responder a: "message-44613856-0786ccdafac0d49696ff4752 at basecamp.com" > > Fecha: lunes, 6 de julio de 2015, 16:51 > Para: Jose Manuel Cantera Fonseca > > Asunto: (FIWARE) The ?FIWARE Media & Content Lab? is up and running, > and we need your feedbacks! > > > > > > Write ABOVE THIS LINE to post a reply or view this on Basecamp > > > Serge TRAVERT > Serge TRAVERT posted this message > on Basecamp. > The ?FIWARE Media & Content Lab? is > up and running, and we need your > feedbacks! > FIcontent has recently released an > online ?Lab? to deliver FIWARE > Enablers for media and content > applications, in order to > complement the FIWARE catalogue of > Generic Enablers (GEs). This new > website, called the ?FIWARE Media & > Content Lab? addresses the needs of > SMEs and developers by means of > four support levels: > > * Discover: Access > information about the > Enablers (Description / > Programmer guide / > Installation guide / > Tutorial / Usage videos / > Terms & Conditions / How to > get support) > * Try: Test live demos of > Enablers > * Tweak: Modify and run the > Enablers client-side code, > in a developer playground > * Run: Start and monitor > instances of Enablers > via various SysOp tools > (Layered on top of FIWARE > Lab, using advanced tools > for facilitating usage and > deployment) > > The FIWARE Media & Content Lab is > accessible > at http://lab.mediafi.org > > For more information, please visit > http://mediafi.org/the-fiware-media-content-lab-is-up-and-running/ > > > We are very much interested to > receive your feedbacks on > the FIWARE Media & Content > Lab: what you like, what may > prevent using it, any suggestions > for improvements, and finally > whether you would recommend using > it to your subgrantees. > > > Kind regards, > > > Serge Travert > > > > View this on Basecamp > > > This email was sent to: Alexander Berlin, Thierry Baujard, Blanca > Rodr?guez, gael maugis, Nuno Varandas, Cristina Cullell-March, Lena > Arndal, Laura Kohler, Olaf-Gerd Gemein, simona torre, Grigoris > Chatzikostas, Paul Pelsmaeker, Raimund Broechler, Adri?n Ferrero, > Siobhan McQuaid, Harald Sundmaeker, Pentti Launonen, Susanna Avessta, > Juanjo Hierro, Margarita Tremblay, Angeles Tejado, Thomas Michael > Bohnert, Paul Cunningham, Satu V?in?m?, Alexander von Jagwitz, Lies > Boghaert, silvia de la maza, Martin Potts, Mirko Ross, > antonis.ramfos at intrasoft-intl.com, Carlos Cerqueira, Fabio Pianesi, > Federico Alvarez, Francisco Bujan, Gabriella Cattaneo, Goran Hodoba, > Ingrid Willems, Sjaak Wolfert, Jesus Villasante, Arian Zwegers, Ragnar > Bergstr?m, Cristian Olimid , Bogdan Ceobanu, Conchi Anton, Maria Mota > Viegas, Peter FATELNIG, Pablo Honrubia, Stefan Stengel, Youssef > Sabbah, Albert Alonso, Ibai Larrabide, Paolo Lombardi, > dechiara at fbk.eu, Veronica Barchetti, Rasmus Ulslev Pedersen, Stefano > De Panfilis, J. Manrique Lopez, Anastasios Stilianidis, Alexandra > Rudl, federico.alvarez at upm.es, Monique Calisti, Rebecca Huxley, > Theodore Zahariadis, Christian Wolff, Ramon Valles, Carmen Mac > Williams, Ciro Acedo, Yves-Marie Le Pann?rer, Pierre Fran?ois, Fabio > Antonelli, Hanna Niemi-Hugaerts, Koen De Vos, Fabio Puglia, Domingo > Legua, Miriam Bajo , Vanessa Vanhumbeeck, Andrea, silvio cretti, Luca > Capra, Pilar Anad?n, Nuria Rodriguez, dragan.m.ivanovic at gmail.com, > Adam Tarcsi, Stefan G?llner, sebastian muller, Daniel Twal, Gianluca > Dettori, Mladen Radisic, Maja Radisic, Caterina Bissoni, Bel?n Kayser, > Alberto Sesmero, Theofilos Mylonas, maurizio cecchi, sergio gusmeroli, > Anastasius Gavras, Fiona Williams, Pieter van der Linden, Isobel > Fletcher, Bernard Garvey, Alexandra Choli, Gaber Cerle, Susana > Garayoa, Ivo Holanec, Eleonora Villanova, Metavallon, > ilkka.lakaniemi at aalto.fi, Nuria de Lama, Antonello Monti, Ana Garcia, > antonio cimmino, Claudia Guglielmina, Dave Clarke, dgimenez at isdefe.es, > gilles.grattard at orange.com, Fourdeux Henri, Uwe Herzog, Jacques Magen, > julie.marguerite at thalesgroup.com, Laurent HERAULT, livdo at tid.es, Oscar > Lazaro, Pascal Bisson, werner.mohr at nsn.com, Federico Facca, Fernando > Sandoval, Javier Garrido Chamorro, Fco. Javier Iglesias, Niels > Genzmer, Katariina Malmberg, Nathalie Danse, john-paul.moore at atos.net, > Assaf Mendelson, Rumen Dobrinsky, qianni.zhang at qmul.ac.uk, > frontierCities at fi-frontierCities.eu, Bernardita Cardenas, Zuzana > Cerna, Johanna Schepers, Alicia Gonz?lez, Marcin Gut, Erkka Suopanki, > remi.ronchaud at inria.fr, Susana Louren?o, Andreana Casaramona, Alberto > Soraci, Jens schumacher, Ina Lauth, Ina Lauth, Carole Thurston, > sandragarcia at bic.es, Vegard Engen, Clare Hooper, Fiona Rivera, Marcelo > Royan, europe at tvt.fr, Kaisa Sibelius, Pau Pamplona, Thomas Winkler, > info at frontierservices.eu, Suvi Kukkonen, Pauliina Smeds, Katerina > Achinioti, stefano modafferi, Se?n J. Burke, Miguel Angel Comin, Mitja > Jermol, Santeri Paavolainen, Jaakko Ik?valko, Susanne K., Sven > Lindmark, Maurin Lagassat, Miguel Carrillo, Belen Manchego, Masa > Mimica, Benjamin Gei?ler, Miguel Alarc?n, Mike Surridge, Thomas Van > der Auwermeulen, Bassem Nasser, Jose Miguel Garrido, Ilenia Ventroni, > Gaelle Lanckmans, Mikkel Toft-Olsen, David Garc?a, ilknur Chulani, > Katalin Viola, Jose Gonzalez, Max Niederhofer, Dan Crowley, Stefania > Aguzzi, gmicheletti at idc.com, Janwillem.kruize at wur.nl, Charlotte > Timmermans, Lisa Pattyn, Nadia Djeziri, Peter Einramhof, Andrea > Siviero, Rasto Petras, Hugo Vivier, mika.rantakokko at cie.fi, Ari > Okkonen, Cristian Dascalu, amir raveh, Ayelet Hashachar Baram, Vincent > Demortier, Imre Hild, Irene Fialka, Peter Tschuchnig, Jana Hodbodova, > A'dam Olszewski, Diego De Biasio, Adolfo Borrero, Charo Jimenez, Jakub > Hruska, murp at zhaw.ch, Cristian Dascalu, Franck Le Gall, > philippe.cousin at eglobalmark.com, jr at livinglabs-global.com, vesna > boskovic, Leandro Guillen, Marta Prados, Malena Donato, Lucian Cosoi, > Norman G?lc?, Estanislao Fern?ndez, Johnny Waterschoot, Sophie > Fensterbank, joel.riga at orange.fr, Martin Weber, Peter Muryshkin, Lukas > Vonnahme, Marie Bourdon, Fernando Lopez, Milon Gupta, Marco Terrinoni, > Jose M. Cantera, Stephen Phillips, Simona Laza, eenev at abv.bg, > jacquespacheco at gmail.com, Vojtech Krmicek, sdena at upatras.gr, Odysseas > Koufopavlou, mentzelopoulos at psp.org.gr, neill at atrovate.com, > rokas.tamosiunas at gmail.com, Marta Moksa, Ale? Pustovrh, Ana Victoria, > jm at corchado.net, Christos Tranoris, Haluk G?kmen, Giulia Costa, > Padraic McKeever, Philipp Slusallek, Pislar Ionut, krijn poppe, Ra?l > S?nchez, Anna Maria Radu, Pasquale Vitale, Roi Rodr?uez, Pierre-Yves > DANET, Miika Tuisku, David Bernal, Valentina Grillea, and Serge > TRAVERT. > > > Stop receiving emails about this message. > > > Want less email from Basecamp? Get a digest of your notifications > every few hours instead, or go to your Basecamp settings to choose > which emails you receive. > > > > > > ______________________________________________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener informaci?n privilegiada o confidencial y > es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > senhoria o destinat?rio indicado, fica notificado de que a leitura, > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destrui??o > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Tue Jul 7 11:43:44 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Tue, 7 Jul 2015 10:43:44 +0100 Subject: [Fiware-developer-experience] Restaurant Context design for Orion In-Reply-To: <1436191166.2359.130.camel@bitergia.com> References: <1436191166.2359.130.camel@bitergia.com> Message-ID: Hi! Our point of view thinking about the front end. Regarding data access from the front end, and store it in Orion, we checked in this reply from Ferm?n in stackoverflow that retrieving entities by filtering attributes is, currently, not possible in Orion. Do you think that it should be a problem for us? A possible solutions should be: - to make IDs of composite type in order to give information about the associated restaurant and customer. This way we can filter again using the ID field. Example of Review id: { "id": "Review-890_jmcantera_Res-5678", ...}. - to bring all the entites to the front end and filter them via javascript, which is a brute force approach and may not be very elegant. We also wanted to ask if it is already decided the data/queries that we want to retrieve from the app front end, in order to have more clear how we will work and focus on the front end requirements. KR, ULPGC team 2015-07-06 14:59 GMT+01:00 Alvaro del Castillo : > Hi! > > El lun, 06-07-2015 a las 13:11 +0000, JOSE MANUEL CANTERA FONSECA > escribi?: > > Responding in an empty emails as I didn?t realise I was not subscribed > > to the list > > > > > > I think customer reviews are part of the context information to be > > stored in Orion. But reviews are entities associated to both customers > > and restaurants. So we will have something like what is proposed below > > Good approach, context information, but not from a restaurant entity, > but from a specific entity: reviews. Not sure if we are forcing orion > usage a bit, but it is a developer guide app for it, so it could be ok. > > > > > > > By the way Alvaro, please provide a first draft of the data models to > > be used. I would like to review them before we start coding > > We are playing with the code to load the data in Orion, in an flexible > approach so the model could be changed later. Give us one-two days > before having a first data model. > > Cheers! > > > > > > > > ---- > > > > > > Restaurant > > > > > > { > > id: ?Res-5678?, > > name: ?Casa Pepa?, > > average_score: { > > ?place?: 7, > > ?service?: 8, > > ?food?: 5 > > }, > > ?location?: xxxx > > } > > > > > > Review > > > > { > > ?id?: ?Review-890?, > > ?author?: ?jmcantera?, > > ?subject?: ?Res-5678?, > > ?creationDate?, ?xxxx?, > > ?score?: { > > } > > } > > > > > > Customer > > > > > > { > > ?id?: ?jmcantera?, > > ?name?: ?Jose Manuel Cantera? > > } > > > > > > ______________________________________________________________________ > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > > destinatario, puede contener informaci?n privilegiada o confidencial y > > es para uso exclusivo de la persona o entidad de destino. Si no es > > usted. el destinatario indicado, queda notificado de que la lectura, > > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > > mensaje por error, le rogamos que nos lo comunique inmediatamente por > > esta misma v?a y proceda a su destrucci?n. > > > > The information contained in this transmission is privileged and > > confidential information intended only for the use of the individual > > or entity named above. If the reader of this message is not the > > intended recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > If you have received this transmission in error, do not read it. > > Please immediately reply to the sender that you have received this > > communication in error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > > senhoria o destinat?rio indicado, fica notificado de que a leitura, > > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > > proceda a sua destrui??o > > _______________________________________________ > > Fiware-developer-experience mailing list > > Fiware-developer-experience at lists.fiware.org > > https://lists.fiware.org/listinfo/fiware-developer-experience > > > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Tue Jul 7 12:19:30 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 07 Jul 2015 12:19:30 +0200 Subject: [Fiware-developer-experience] Restaurant Context design for Orion In-Reply-To: References: <1436191166.2359.130.camel@bitergia.com> Message-ID: <1436264370.2359.156.camel@bitergia.com> Hi! El mar, 07-07-2015 a las 10:43 +0100, Pablo Fern?ndez Moniz escribi?: > Hi! > > > Our point of view thinking about the front end. > > > Regarding data access from the front end, and store it in Orion, we > checked in this reply from Ferm?n in stackoverflow that retrieving > entities by filtering attributes is, currently, not possible in Orion. > Do you think that it should be a problem for us? Right now in ChanChanApp we are retrieving entities in this way: https://github.com/Bitergia/fiware-chanchan/blob/master/server/routes/orion.js#L164 We are using the type and a regexp in the id. Maybe it is enough for the devguide app. Not sure. > > > A possible solutions should be: > > - to make IDs of composite type in order to give information about > the associated restaurant and customer. This way we can filter again > using the ID field. Example of Review id: { "id": > "Review-890_jmcantera_Res-5678", ...}. > Maybe we can combine review type (in this field include the restaurant) and the id (which include the user as you suggested). > - to bring all the entites to the front end and filter them via > javascript, which is a brute force approach and may not be very > elegant. > Yes, if possible we should try to avoid this. > We also wanted to ask if it is already decided the data/queries that > we want to retrieve from the app front end, in order to have more > clear how we will work and focus on the front end requirements. I think the best doc for this now is the devguide app requirements. https://docs.google.com/document/d/1FpeuBzPkAkIs90rP16jeOdi5-JuSbcdsiOatE87l3Dw/edit We are following it. But it is high level so we should discuss specific details. Pablo, maybe you can focus in a first scenario (showing restaurants in a map view?) and then enrich it. Cheers > > > > KR, > > > ULPGC team > > > > > > > > 2015-07-06 14:59 GMT+01:00 Alvaro del Castillo : > Hi! > > El lun, 06-07-2015 a las 13:11 +0000, JOSE MANUEL CANTERA > FONSECA > escribi?: > > Responding in an empty emails as I didn?t realise I was not > subscribed > > to the list > > > > > > I think customer reviews are part of the context information > to be > > stored in Orion. But reviews are entities associated to both > customers > > and restaurants. So we will have something like what is > proposed below > > Good approach, context information, but not from a restaurant > entity, > but from a specific entity: reviews. Not sure if we are > forcing orion > usage a bit, but it is a developer guide app for it, so it > could be ok. > > > > > > > By the way Alvaro, please provide a first draft of the data > models to > > be used. I would like to review them before we start coding > > We are playing with the code to load the data in Orion, in an > flexible > approach so the model could be changed later. Give us one-two > days > before having a first data model. > > Cheers! > > > > > > > > ---- > > > > > > Restaurant > > > > > > { > > id: ?Res-5678?, > > name: ?Casa Pepa?, > > average_score: { > > ?place?: 7, > > ?service?: 8, > > ?food?: 5 > > }, > > ?location?: xxxx > > } > > > > > > Review > > > > { > > ?id?: ?Review-890?, > > ?author?: ?jmcantera?, > > ?subject?: ?Res-5678?, > > ?creationDate?, ?xxxx?, > > ?score?: { > > } > > } > > > > > > Customer > > > > > > { > > ?id?: ?jmcantera?, > > ?name?: ?Jose Manuel Cantera? > > } > > > > > > > ______________________________________________________________________ > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > > destinatario, puede contener informaci?n privilegiada o > confidencial y > > es para uso exclusivo de la persona o entidad de destino. Si > no es > > usted. el destinatario indicado, queda notificado de que la > lectura, > > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede > estar > > prohibida en virtud de la legislaci?n vigente. Si ha > recibido este > > mensaje por error, le rogamos que nos lo comunique > inmediatamente por > > esta misma v?a y proceda a su destrucci?n. > > > > The information contained in this transmission is privileged > and > > confidential information intended only for the use of the > individual > > or entity named above. If the reader of this message is not > the > > intended recipient, you are hereby notified that any > dissemination, > > distribution or copying of this communication is strictly > prohibited. > > If you have received this transmission in error, do not read > it. > > Please immediately reply to the sender that you have > received this > > communication in error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > > destinat?rio, pode conter informa??o privilegiada ou > confidencial e ? > > para uso exclusivo da pessoa ou entidade de destino. Se n?o > ? vossa > > senhoria o destinat?rio indicado, fica notificado de que a > leitura, > > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar > proibida > > em virtude da legisla??o vigente. Se recebeu esta mensagem > por erro, > > rogamos-lhe que nos o comunique imediatamente por esta mesma > via e > > proceda a sua destrui??o > > _______________________________________________ > > Fiware-developer-experience mailing list > > Fiware-developer-experience at lists.fiware.org > > > https://lists.fiware.org/listinfo/fiware-developer-experience > > > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > > > > > -- > > Pablo Fern?ndez Moniz > > GIT Analyst > > > Web Linkedin Twitter > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From josemanuel.canterafonseca at telefonica.com Tue Jul 7 12:44:27 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Tue, 7 Jul 2015 10:44:27 +0000 Subject: [Fiware-developer-experience] A data model propolsa for devguide app In-Reply-To: <1436258381.2359.137.camel@bitergia.com> References: <1436258381.2359.137.camel@bitergia.com> Message-ID: Hola Alvaro, Creo que mejor alinearnos con http://schema.org Algunos ejemplos los puedes encontrar en https://developers.google.com/structured-data/rich-snippets/reviews Gracias, saludos El 7/7/15 10:39, "fiware-developer-experience-bounces at lists.fiware.org on behalf of Alvaro del Castillo" escribi?: >Hi all! > >Here goes a proposal using the original requirements and the comments in >this list. Maybe we can work with Google Docs to refine it. It is a >first proposal totally open to modifications and comments! > >DATA MODEL PROPOSAL FOR DEVGUIDE APP: > >h2. Restaurant > >* id >* name >* description >* address >* email >* phone >* room >* url >* Temperature and humidity cuisine and room >* customer satisfaction (avg_rating) > >h2. Reviews > >* id >* by customer >* to restaurant >* review text >* food rating (0-10) >* place rating (0-10) >* service rating (0-10) > >h2. Reservations > >* id >* daytime >* number of people >* cancelled > >h2. Customer > >* id >* name >* email > >h2. Manager > >* id >* name >* email >* rol > >Cheers > >-- >Alvaro del Castillo San F?lix >acs at bitergia.com - Chief Technical Officer (CTO) >http://www.bitergia.com >"Software metrics for your peace of mind" > > >_______________________________________________ >Fiware-developer-experience mailing list >Fiware-developer-experience at lists.fiware.org >https://lists.fiware.org/listinfo/fiware-developer-experience ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o From acs at bitergia.com Tue Jul 7 13:19:37 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 07 Jul 2015 13:19:37 +0200 Subject: [Fiware-developer-experience] A data model propolsa for devguide app In-Reply-To: References: <1436258381.2359.137.camel@bitergia.com> Message-ID: <1436267977.2359.162.camel@bitergia.com> Hola! El mar, 07-07-2015 a las 10:44 +0000, JOSE MANUEL CANTERA FONSECA escribi?: > Hola Alvaro, > > Creo que mejor alinearnos con http://schema.org > > Algunos ejemplos los puedes encontrar en > > https://developers.google.com/structured-data/rich-snippets/reviews > Ok, great! Better to reuse data models, yes! So we use schema.org to define our entities and then we will map to orion data model it! Correct? Microdata has advanced a lot last years. Pretty cool! Bye > > Gracias, saludos > > El 7/7/15 10:39, "fiware-developer-experience-bounces at lists.fiware.org on > behalf of Alvaro del Castillo" > acs at bitergia.com> escribi?: > > >Hi all! > > > >Here goes a proposal using the original requirements and the comments in > >this list. Maybe we can work with Google Docs to refine it. It is a > >first proposal totally open to modifications and comments! > > > >DATA MODEL PROPOSAL FOR DEVGUIDE APP: > > > >h2. Restaurant > > > >* id > >* name > >* description > >* address > >* email > >* phone > >* room > >* url > >* Temperature and humidity cuisine and room > >* customer satisfaction (avg_rating) > > > >h2. Reviews > > > >* id > >* by customer > >* to restaurant > >* review text > >* food rating (0-10) > >* place rating (0-10) > >* service rating (0-10) > > > >h2. Reservations > > > >* id > >* daytime > >* number of people > >* cancelled > > > >h2. Customer > > > >* id > >* name > >* email > > > >h2. Manager > > > >* id > >* name > >* email > >* rol > > > >Cheers > > > >-- > >Alvaro del Castillo San F?lix > >acs at bitergia.com - Chief Technical Officer (CTO) > >http://www.bitergia.com > >"Software metrics for your peace of mind" > > > > > >_______________________________________________ > >Fiware-developer-experience mailing list > >Fiware-developer-experience at lists.fiware.org > >https://lists.fiware.org/listinfo/fiware-developer-experience > > > ________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From josemanuel.canterafonseca at telefonica.com Tue Jul 7 15:32:43 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Tue, 7 Jul 2015 13:32:43 +0000 Subject: [Fiware-developer-experience] FW: FIWARE developer experience with Docker: cloud chapter In-Reply-To: References: <5592F69E.4060803@telefonica.com> Message-ID: FYI De: Kenneth Nagin > Fecha: martes, 7 de julio de 2015, 15:21 Para: Jose Manuel Cantera Fonseca > CC: Alex Glikson >, JUAN JOSE HIERRO SUREDA >, MIGUEL CARRILLO PACHECO > Asunto: Re: FIWARE developer experience with Docker: cloud chapter We prepared a slide show called Simple Docker Hosting on FIWARE Lab: http://www.slideshare.net/knagin/simple-docker-hosting-on-fiware-lab The slide show is our initial output to <1> and <2> below. We are currently studying the limitation of this environment and a roadmap to address these limitations . We will share it with you and the task force once it is completed. Best Regards, Kenneth Nagin Ph: +972-4-8296227 Cell: 054-6976227 Fx: +972-4- 8296114 http://researcher.ibm.com/view.php?person=il-NAGIN From: JOSE MANUEL CANTERA FONSECA > To: Kenneth Nagin/Haifa/IBM at IBMIL Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL, MIGUEL CARRILLO PACHECO > Date: 06/07/2015 12:03 PM Subject: Re: FIWARE developer experience with Docker: cloud chapter ________________________________ Hello, Responses inline Thanks, best De: Kenneth Nagin > Fecha: viernes, 3 de julio de 2015, 10:41 Para: Jose Manuel Cantera Fonseca > CC: JUAN JOSE HIERRO SUREDA >, Alex Glikson >, MIGUEL CARRILLO PACHECO > Asunto: Re: FIWARE developer experience with Docker: cloud chapter The attached thread was intended for Jos?-Manuel Cantera not Miguel. From: Kenneth Nagin/Haifa/IBM To: "Miguel Carrillo" > Cc: Juanjo Hierro >, Alex Glikson/Haifa/IBM at IBMIL Date: 03/07/2015 11:20 AM Subject: FIWARE developer experience with Docker: cloud chapter ________________________________ Jos?-Manuel: The Cloud chapter has already begun focusing on providing Docker support. 1. IBM is preparing a study of how FIWARE developers can leverage the current FIWARE lab to host Docker while using Docker ecosystem tools locally to develop and deploy their applications. We will verify 1) Docker-Engine and Docker-Machine for setting up their remote hosting environment, 2) Docker-Compose for constructing and running multi-container applications hosted on FIWARE, 3) Docker-Swarm for host clustering and container scheduling. (Issue CLD-574). The output of the study will be to describe the capabilities, limitations and gaps of hosting Docker on FIWARE. I will present preliminary results at the sprint closing chapter review (Monday July 6). >> Sounds great. Where can I find the report? 2. IBM will document the required set up by a FIWARE developer for hosting Docker on FIWARE. This documentation will be made publicly available. (Issue CLD-576). This is basically the outputs of <1> and can be contributed to item <2> in Juano's attached note. >> Cool 3. TID is preparing a demonstration of Murano Docker Support (Issues CLD-560, CLD-568 ). This would allow a FIWARE developer to deploy Docker containers using the Murano API. Henar will demonstrate deploying docker with Murano at the sprint closing chapter review (Monday July 6). >> That?s complementary to docker-machine so it is nice as well 4. UPM is estimating the work effort to expose the Murano to the user on the cloud portal. This involves adapting the current blue print views to the Murano API (Issue CLD-584). Does the above compatible with your plan? Should we share the above rest of the container task force? >> Yes of course thanks Best Regards, Kenneth Nagin Ph: +972-4-8296227 Cell: 054-6976227 Fx: +972-4- 8296114 http://researcher.ibm.com/view.php?person=il-NAGIN From: Juanjo Hierro > To: Alex Glikson/Haifa/IBM at IBMIL, > Date: 30/06/2015 11:06 PM Subject: Re: [Fiware-cloud-containers] FIWARE developer experience with Docker Sent by: fiware-cloud-containers-bounces at lists.fiware.org ________________________________ Dear all, Thanks Alex for launching these discussions tracks. Regarding point (1) as anticipated by Alex, here it is the concrete plan we aim at implementing to promote usage of docker tools by GE/SE owners and the broader developer community. 1. Make info about Docker images and instruction to setup docker containers linked to FIWARE GEris available in the FIWARE Catalogue: * We will specify a general template of a new section which will be included in the "Creating instances" tab of entries linked to FIWARE GEris. This section will be elaborate on "Deploying a dedicated GE instance using Docker technology" * Each FIWARE GEri owner will be asked to setup a Docker image for their GEs and register it in Docker Hub. This task can start in parallel to the previous one. * Each FIWARE GEri owner will be asked to update the "Creating instance" tab of the entry linked to the FIWARE GEri so that it provides instructions about deploying a dedicated instance of the GEri using docker. For this purpose, the owner will follow the template defined in step 1. 2. We will incorporate the description about how to create FIWARE GEri instances and try them using docker within the FIWARE Tour Guide for developers (which will effectively become the landing page of http://developers.fiware.org) as a mean to shorten the learning curve with FIWARE GEris * Somewhere at the beginning of the guided tour, we will explain the developer how he can setup the basic docker environment either locally or on the FIWARE Lab on which he will be able to rely to try the different FIWARE GEris (Group 1 scenarios described by Alex) * A demo application will be developed that will help the developer to try each FIWARE GEri instance deployed using docker with concrete data. Developers will be able to deploy this application also using docker. It is the intention that this application will be helpful to show how several FIWARE GEris can be used in an integrated way. * Each of the chapters of the FIWARE Tour guide for developers will integrate a "Try it yourself" section which will help the developer to create an instance of the FIWARE GEris referred in the chapter and try them. In addition, developers will be able to deploy the demo application, in order to learn from a more elaborated example how the FIWARE GEris can be used, and providing instructions about how to play with the FIWARE GEris, also "tweak" the application. * Deployment of integrated FIWARE GEris and the demo application will be made feasible using docker composition tools Jos?-Manuel Cantera will drive the implementation of these concrete actions. Regarding point 2, Bitergia has already developed a first bundle of FIWARE GEris deployable using Docker compose (as a whole or individually). They will work in extending this bundle integrating additional FIWARE GEris in collaboration with the corresponding FIWARE GEri owners. Bitergia and the ULPG will work together in the development of a first version of the demo application. Eventually, additional partners might be incorporated as additional skills and/or resources are needed. We will address first those scenarios dealing with local deployment, then we will incorporate those related to deployment on other infrastructures such as the FIWARE Lab as soon as the necessary preliminary work and/or detailed guidelines are completed (this would be done under coordination by Alex and I assume we will leverage on experience developed in FI-Content2). Feedback is welcome. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telef?nica email: juanjose.hierro at telefonica.com twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 30/06/15 20:34, Alex Glikson wrote: Dear partners, Following the initial discussion at the containers task force, we identified two follow-on (related) discussion tracks: 1) expected FIWARE Lab user/developer experience with Docker 2) Enhancements to FIWARE Cloud Hosting architecture to support Docker (and enable requirements derived from #1) This email refers to topic (1). I will try to summarize the initial set of usage scenarios that we may want to support. We can then iterate on this over email, and have a phone call if needed, when we feel that we are close to a convergence point. Please, notice that I've subscribed several additional people relevant for the discussion (who could provide input related to UI, developers perspectives and operations perspectives). Assumptions: Notice that a prerequisite for all the usage scenarios is that all the FIWARE GEs (and SEs) are packages as Docker images and are kept in a central repository, preferably the docker hub (under a 'to-be-created' "fiware" namespace). Also, there is an assumption that the users/developers would want to work with Docker tools as much as possible (surfacing some or all of the capabilities via the FIWARE Cloud Portal too). Juanjo will elaborate on the approach we are thinking of to promote this with GE/SE owners and the broader developer community. Group 1: Basic Docker environment setup Usage scenario #1.1: A user wants a local Docker runtime on his laptop. He follows the standard instructions on setting up a docker host (e.g., running within a VirtalBox VM, using docker-machine / boot2docker) Usage scenario #1.2: A user/developer wants to deploy a dedicated Docker VM on FIWARE Lab (where he would then run various Docker containers). He uses the standard docker-machine tool, specifying the URI of the OpenStack Keystone in FIWARE Lab (and additional parameters, as needed). The tool creates a VM using standard OpenStack APIs (natively supported by FIWARE Lab) and configures Docker within the VM. The VM would need to have a public IP (naturally). Group 2: Basic life cycle of individual containers running GEs/SEs Usage scenario #2.1: A developer wants to publish (a version of) a GE/SE. After he is done creating the new Docker image, he pushes the new version of the GE/SE to Docker hub under corresponding FIWARE namespace (e.g., fiware/GE/cb-orion). Now the 'latest' version of the image points to the new version. Usage scenario #2.2: A user/developer wants to deploy locally an instance of a certain GE/SE. He uses the standard docker CLI to locally provision a container, referring to the corresponding image at Docker hub -- e.g.: "$ docker -H boot2docker-vm:2376 run fiware/GE/cb-orion" Usage scenario #2.3: A user/developer wants to deploy an instance of a certain GE/SE within his Docker VM on FIWARE Lab He uses the standard docker CLI to provision a container, referring to the location of his Docker VM as well as the corresponding image at Docker hub -- e.g.: "$ docker -H mydocker-vm37.lab.fiware.org:2376 run fiware/GE/cb-orion". ISSUE: the user would need to open the corresponding firewall ports in his VM (same as those of the GE/SE, or following the mapping performed during container provisioning) in order to make the GE/SE accessible. Ideally, this should be done in a scalable but secure manner. An easy solution is to open up-front (during VM provisioning) a range of ports (via setting up corresponding security group). A more advanced solution is to update the security group dynamically. Usage scenario #2.4: A user/developer wants to update a container comprising certain GE/SE with the latest version recently published in the dedicated namespace of the Docker Hub. He pulls the latest version from the Docker Hub, kills the old container, and starts a new one (attaching to the same resources). Note that this would work well when the application is properly designed for Docker (e.g., the container itself is stateless), and when the previous version of the container has been provisioned manually (as in #2, #4 above) by the developer (and he knows which resources to connect to). Group 3: Support for 'bundles' of GEs/SEs that together perform a certain complex function Usage scenario #3.1: A developer wants to publish (a version of) a 'bundle' of GEs/SEs that together perform a certain complex function. He creates a 'template' (e.g., following the format of docker-compose), referring to the individual GE/SE images as well as their interdependencies (e.g., links) and other composition properties. This might be done using a text editor, a Web UI provided by the FIWARE Cloud (conceptually similar to today's UI for creation of blueprints), or other tools from Docker ecosystem. He then uploads the template to the centralized templats repository. Note: it is likely that docker-compose will be able to use Docker Registry/Hub as a repository for templates (including versioning, push/pull, etc). Usage scenario #3.2: A user wants to provision locally a set of GEs/SEs, using a pre-defined template (comprising a 'bundle') He uses the standard docker-compose tool referring to the 'template' artifcat as well as the local Docker URL. Usage scenario #3.3: A user wants to provision a set of GEs/SEs in FIWARE Lab, using a pre-defined template (comprising a 'bundle') He uses the standard docker-compose tool referring to the 'template' artifcat as well as the target Docker URL in FIWARE Lab. Alternatively, he uses the FIWARE Portal UI to do the same (e.g., with Murano backend invoking docker-compose). Usage scenario #3.4: A user wants to update his Docker environment (local or on FIWARE Lab) with the latest version of a certain 'bundle' Note: may require enancements to docker-compose Group 4: Advanced scenarios Usage scenario #4.1: A user/developer wants to provision a cluster of VMs on FIWARE Lab that would host his Docker cluster (managed with Swarm or Kubernetes) He uses corresponding Murano/Heat template to provision the VMs and to configure the Docker/Swarm/Kubernetes cluster. Usage scenario #4.2: A user/developer wants to access a global instance of a Docker service in FIWARE Lab (shared, scalable, managed), so that he doesn't need to manage the corresponding VM(s) by himself. He authenticates with FIWARE Lab, and starts accessing the FIWARE Lab Docker API endpoint with the standard Docker tools or FIWARE-specific tools (as outlined above ). Usage scenario #4.3: A user/developer wants to manage access control for Docker images among FIWARE Lab users. He starts using the Docker Registry/Hub deployed within the FIWARE Lab. Notice that this is a very initial list -- I am sure that there are many inaccuracies and gaps. Feel free to comment. Thanks, Alex ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 _______________________________________________ Fiware-cloud-containers mailing list Fiware-cloud-containers at lists.fiware.org https://lists.fiware.org/listinfo/fiware-cloud-containers ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o_______________________________________________ Fiware-cloud-containers mailing list Fiware-cloud-containers at lists.fiware.org https://lists.fiware.org/listinfo/fiware-cloud-containers ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Wed Jul 8 19:45:26 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 08 Jul 2015 19:45:26 +0200 Subject: [Fiware-developer-experience] First devapp-guide docker image ready in docker hub Message-ID: <1436377526.2359.177.camel@bitergia.com> Hi guys! We have just finished the testing of https://registry.hub.docker.com/u/bitergia/fiware-devguide-app/ and it works. In order to use it, please follow this steps: 0. You need docker and nodejs installed in your host. 1. Clone the repo: git clone https://github.com/Bitergia/fiware-devguide-app.git 2. Start the docker compose for devguide: cd fiware-devguide-app/docker/compose/ docker-compose up 3. Configure containers ips with names in /etc/hosts (working in other terminal) using "docker utils from bitergia":https://github.com/Bitergia/docker/tree/master/utils sudo get-docker-hosts -m 4. Load the data for restaurants (working in other terminal): cd fiware-devguide-app/server/ gunzip restaurants.json.gz && gunzip restaurants_geo.json.gz node restaurant_feeder.js 5. Get information from restaurants: http://compose_devguide_1/api/orion/restaurants/ It could be cool if you test all before the audio tomorrow at 11:30 so we can be more productive during the meeting. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Thu Jul 9 10:15:42 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Thu, 9 Jul 2015 09:15:42 +0100 Subject: [Fiware-developer-experience] First devapp-guide docker image ready in docker hub In-Reply-To: <1436377526.2359.177.camel@bitergia.com> References: <1436377526.2359.177.camel@bitergia.com> Message-ID: Hi, We try to deploy following your indications, but we had some issues, although finally we could do it. Find attached pdf for more information, anyway we can talk about this, and some others things later via Skype. KR! ULPGC team 2015-07-08 18:45 GMT+01:00 Alvaro del Castillo : > Hi guys! > > We have just finished the testing of > > https://registry.hub.docker.com/u/bitergia/fiware-devguide-app/ > > and it works. In order to use it, please follow this steps: > > 0. You need docker and nodejs installed in your host. > > 1. Clone the repo: > > git clone https://github.com/Bitergia/fiware-devguide-app.git > > 2. Start the docker compose for devguide: > > cd fiware-devguide-app/docker/compose/ > docker-compose up > > > 3. Configure containers ips with names in /etc/hosts (working in other > terminal) using "docker utils from > bitergia":https://github.com/Bitergia/docker/tree/master/utils > > sudo get-docker-hosts -m > > 4. Load the data for restaurants (working in other terminal): > > cd fiware-devguide-app/server/ > gunzip restaurants.json.gz && gunzip restaurants_geo.json.gz > node restaurant_feeder.js > > 5. Get information from restaurants: > > http://compose_devguide_1/api/orion/restaurants/ > > It could be cool if you test all before the audio tomorrow at 11:30 so > we can be more productive during the meeting. > > Cheers > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: docker.pdf Type: application/pdf Size: 521604 bytes Desc: not available URL: From acs at bitergia.com Thu Jul 9 12:23:01 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Thu, 09 Jul 2015 12:23:01 +0200 Subject: [Fiware-developer-experience] All restaurants query Message-ID: <1436437381.2359.189.camel@bitergia.com> Hi all! Pablo, we have implemented the all restaurants query in this commit: https://github.com/Bitergia/fiware-devguide-app/commit/8da1b534b3b2cbe85fb14b3014bd1404623490b5 I think that just downloading the new image from docker hub is enough to have it working (following the steps you already did for loading data). Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Thu Jul 9 12:31:03 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Thu, 9 Jul 2015 11:31:03 +0100 Subject: [Fiware-developer-experience] All restaurants query In-Reply-To: <1436437381.2359.189.camel@bitergia.com> References: <1436437381.2359.189.camel@bitergia.com> Message-ID: Hi, 2015-07-09 11:23 GMT+01:00 Alvaro del Castillo : > Hi all! > > Pablo, we have implemented the all restaurants query in this commit: > > > https://github.com/Bitergia/fiware-devguide-app/commit/8da1b534b3b2cbe85fb14b3014bd1404623490b5 > > I think that just downloading the new image from docker hub is enough to > have it working (following the steps you already did for loading data). > Thank you for your quick response > > Cheers > Cheers, ULPGC Team, > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmuriel at bitergia.com Fri Jul 10 15:05:44 2015 From: dmuriel at bitergia.com (David Muriel) Date: Fri, 10 Jul 2015 15:05:44 +0200 Subject: [Fiware-developer-experience] First devapp-guide docker image ready in docker hub In-Reply-To: References: <1436377526.2359.177.camel@bitergia.com> Message-ID: On Thu, Jul 9, 2015 at 10:15 AM, Pablo Fern?ndez Moniz wrote: > Hi, > > We try to deploy following your indications, but we had some issues, > although finally we could do it. The memory issue is due to the way we are sending the data to orion on restaurant_feeder.js. Right now the script sends a lot of simultaneous requests to orion, which causes the memory rise. We're looking into it. The JSON issue is due to some unescaped html entities in some of the fields sent to orion. We are adding some checks to escape those characters before sending the data to orion. The last issue is due to the default number of tries done when the container starts and checks for some external services (in your case, the orion container checks if mongodb is up and running). We've increased the default number of tries to 30 and made it configurable on container creation. I'm doing some tests right now to check that all the images are still working as expected before uploading it to the repository and regenerating the images on the hub. Cheers. -- David Muriel. From pablofernandezmoniz at gmail.com Mon Jul 13 18:35:11 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Mon, 13 Jul 2015 17:35:11 +0100 Subject: [Fiware-developer-experience] Starting with bitergia/idm-keyrock docker Message-ID: Hi all, We are starting with some tests with bitergia/idm-keyrock docker and we have found some Issues: - We had to add account.idm to our hosts file in order to can access the site. Even if we used the IP for access the site, it tried to redirect us to account.idm and failed. - Links provided in the site once the docker image are running, refer to original Fiware links. We may find confusing that if we click in Account, we was redirected to https://account.lab.fiware.org/ instead of use the local Identity Manager instance. - We cannot log out. Once logged in, if we try to log out, nothing happens. - Cannot register a new account due to try to load unsecure content in a https connection. We think that this issue does not allow to load the captcha, so a user can?t be registered. - If we try to use the docker image directly, we get the error: Tag latest not found in repository bitergia/idm-keyrock We hope this feedback is useful, if we are doing something wrong, please tell us. KR ULPGC Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Wed Jul 15 14:54:31 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 15 Jul 2015 14:54:31 +0200 Subject: [Fiware-developer-experience] A data model propolsa for devguide app In-Reply-To: <1436267977.2359.162.camel@bitergia.com> References: <1436258381.2359.137.camel@bitergia.com> <1436267977.2359.162.camel@bitergia.com> Message-ID: <1436964871.1904.48.camel@bitergia.com> Hi all! El mar, 07-07-2015 a las 13:19 +0200, Alvaro del Castillo escribi?: > Hola! > > El mar, 07-07-2015 a las 10:44 +0000, JOSE MANUEL CANTERA FONSECA > escribi?: > > Hola Alvaro, > > > > Creo que mejor alinearnos con http://schema.org > > > > Algunos ejemplos los puedes encontrar en > > > > https://developers.google.com/structured-data/rich-snippets/reviews > > > > Ok, great! Better to reuse data models, yes! > > So we use schema.org to define our entities and then we will map to > orion data model it! Correct? > > Microdata has advanced a lot last years. Pretty cool! > After reviewing schema.org, from a backend point of view, we can just use the schema.org vocabulary in order to make life easier to the front. A proposal for using schema.org with the original proposal: Restaurant: https://schema.org/Restaurant Review: https://schema.org/Review Reservation: https://schema.org/Reservation Customer: https://schema.org/Person Manager: https://schema.org/Person In our entity model we will use the vocabulary defined in schema.org. Cheers > Bye > > > > > Gracias, saludos > > > > El 7/7/15 10:39, "fiware-developer-experience-bounces at lists.fiware.org on > > behalf of Alvaro del Castillo" > > > acs at bitergia.com> escribi?: > > > > >Hi all! > > > > > >Here goes a proposal using the original requirements and the comments in > > >this list. Maybe we can work with Google Docs to refine it. It is a > > >first proposal totally open to modifications and comments! > > > > > >DATA MODEL PROPOSAL FOR DEVGUIDE APP: > > > > > >h2. Restaurant > > > > > >* id > > >* name > > >* description > > >* address > > >* email > > >* phone > > >* room > > >* url > > >* Temperature and humidity cuisine and room > > >* customer satisfaction (avg_rating) > > > > > >h2. Reviews > > > > > >* id > > >* by customer > > >* to restaurant > > >* review text > > >* food rating (0-10) > > >* place rating (0-10) > > >* service rating (0-10) > > > > > >h2. Reservations > > > > > >* id > > >* daytime > > >* number of people > > >* cancelled > > > > > >h2. Customer > > > > > >* id > > >* name > > >* email > > > > > >h2. Manager > > > > > >* id > > >* name > > >* email > > >* rol > > > > > >Cheers > > > > > >-- > > >Alvaro del Castillo San F?lix > > >acs at bitergia.com - Chief Technical Officer (CTO) > > >http://www.bitergia.com > > >"Software metrics for your peace of mind" > > > > > > > > >_______________________________________________ > > >Fiware-developer-experience mailing list > > >Fiware-developer-experience at lists.fiware.org > > >https://lists.fiware.org/listinfo/fiware-developer-experience > > > > > > ________________________________ > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. > > > > The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. > > > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o > > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Wed Jul 15 19:04:26 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Wed, 15 Jul 2015 18:04:26 +0100 Subject: [Fiware-developer-experience] Doubts about the architecture/application Message-ID: Hi! We have some development progress, and we want to share it and raise some questions Architecture overview: Actually we have an implementation like this. - Represented in white color we have the previous containers that were in the docker-compose. - mongodb: It stores the database of Orion. It has attached the mogodbdata volume. - orion: It has the Context Broker installed. It uses the mogodb image as database. - devguide: It has implemented the API for restaurant management. It interacts with orion and it acts like an abstraction layer. - Blue elements have been added to the docker compose by the ULPGC group. - idm: It runs an instance of the Identity Management. Users and roles must be stored here. - authzforce: Image needed by idm. - Finally, elements that have not been added yet to a container are in yellow. - initUsers.py: It is a python script that creates the first users and roles in Identity Manager. - flask server: It hosts the web and acts as intermediate layer between users and the Identity Manager. [image: Captura de pantalla 2015-07-15 a las 13.07.42.png] Doubts that have arisen We need to initialize the IdM with default values ( for example roles ) so, for the moment, we developed a small python script (initUsers.py) to do that. Due to cross domain restriction, we cannot perform petitions directly to the IdM from the front end. We solved this using an intermediate layer in the server that controls the user creation and the login . Another solution could be to use a proxy. Furthermore, in order to allow users to sign up, we need an administrative credential to create the new user entity. If this credential is used from the front end, it could be a security risk. So, we think that the actual approach of managing the operations related to the IdM from the server side is correct. On the other hand, we have started to make some development in the server side. We are using python since we have experience with it and we have had good results using it. We also have good feelings with other languages such as PHP. We don?t know which language are you using at this moment, but we think that the less different languages we use the better for making an easy guide. Finally, we suggest that we should add a new image that contains the web server. What do you think? KR, and sorry for the large email :) ULPGC team -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From alberto.martin at bitergia.com Wed Jul 15 20:35:24 2015 From: alberto.martin at bitergia.com (=?UTF-8?Q?Alberto_Mart=C3=ADn_Casado?=) Date: Wed, 15 Jul 2015 20:35:24 +0200 Subject: [Fiware-developer-experience] Doubts about the architecture/application In-Reply-To: References: Message-ID: Hi! 2015-07-15 19:04 GMT+02:00 Pablo Fern?ndez Moniz < pablofernandezmoniz at gmail.com>: > Hi! > We have some development progress, and we want to share it and raise some > questions Architecture overview: > > Actually we have an implementation like this. > > > > - > > Represented in white color we have the previous containers that were > in the docker-compose. > - > > mongodb: It stores the database of Orion. It has attached the > mogodbdata volume. > - > > orion: It has the Context Broker installed. It uses the mogodb > image as database. > - > > devguide: It has implemented the API for restaurant management. It > interacts with orion and it acts like an abstraction layer. > - > > Blue elements have been added to the docker compose by the ULPGC group. > - > > idm: It runs an instance of the Identity Management. Users and > roles must be stored here. > - > > authzforce: Image needed by idm. > - > > Finally, elements that have not been added yet to a container are in > yellow. > - > > initUsers.py: It is a python script that creates the first users > and roles in Identity Manager. > - > > flask server: It hosts the web and acts as intermediate layer > between users and the Identity Manager. > > > > > [image: Captura de pantalla 2015-07-15 a las 13.07.42.png] > > Doubts that have arisen > > We need to initialize the IdM with default values ( for example roles ) > so, for the moment, we developed a small python script (initUsers.py) to do > that. > We've been through this already in the image. Few days ago we've updated the documentation of our IdM image with the users, orgs, roles and everything that we've provided. You can find here the method we've used for that (hope it helps). > > Due to cross domain restriction, we cannot perform petitions directly to > the IdM from the front end. We solved this using an intermediate layer in > the server that controls the user creation and the login . Another solution > could be to use a proxy. > Furthermore, in order to allow users to sign up, we need an administrative > credential to create the new user entity. If this credential is used from > the front end, it could be a security risk. So, we think that the actual > approach of managing the operations related to the IdM from the server side > is correct. > The PEP Proxy could be the intermediate layer to handle this access. The approach could be, an administrator that is able to handle users, organizations, roles and permissions. Then, create different roles, allowing just the administrator to use requests for user administration using the Keystone API . We've updated today also the PEP Wilma image and documentation: https://registry.hub.docker.com/u/bitergia/pep-wilma/ Doing this, we include another GE to the architecture proposed :) > > On the other hand, we have started to make some development in the server > side. We are using python since we have experience with it and we have had > good results using it. We also have good feelings with other languages such > as PHP. > > > I personally feel more comfortable with python, but I cannot speak from the others. > We don?t know which language are you using at this moment, but we think > that the less different languages we use the better for making an easy > guide. > Actually we've been using javascript (node, angular) for the application, shell scripts and a bit of python. > > Finally, we suggest that we should add a new image that contains the web > server. > What do you need for the web server exactly? In the fiware-devguide-app we have already an apache2.4 with phusion passenger, and it teorically supports node, ruby and python. If something like that is enough, we can create a clean container with this for start deploying the web server. > > What do you think? > Looks good! We will also have to add IDAS, and other components (as the PEP proxy mentioned before), but step by step :) > > KR, and sorry for the large email :) > > > ULPGC team > > > Cheers, Alberto Mart?n > -- > > Pablo Fern?ndez Moniz > GIT Analyst > > Web Linkedin > Twitter > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Thu Jul 16 14:26:31 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Thu, 16 Jul 2015 14:26:31 +0200 Subject: [Fiware-developer-experience] Reviews and Recommendations ready to be tested Message-ID: <1437049591.2415.7.camel@bitergia.com> Hi all! We have finished to implement the REST API for Reviews and Recommendations. The API is the same than for restaurants: * Get data for Arabako, its reviews and its reservations: http://compose_devguide_1/api/orion/restaurants/Arabako http://compose_devguide_1/api/orion/reviews/Arabako http://compose_devguide_1/api/orion/reservations/Arabako * Get data for all restaurants, their reviews and their reservations: http://compose_devguide_1/api/orion/restaurants/ http://compose_devguide_1/api/orion/reviews/ http://compose_devguide_1/api/orion/reservations/ * Get data for all restaurants including Ara in the name, their reviews and their reservations: http://compose_devguide_1/api/orion/restaurants/ara http://compose_devguide_1/api/orion/reviews/ara http://compose_devguide_1/api/orion/reservations/ara Right now the reservations and reviews data are just basic testing, but following the schema.org vocabulary. In next steps we will improve the data loaders to include more interesting info. In order to test all of this, the best approach is to use the docker image: https://registry.hub.docker.com/u/bitergia/fiware-devguide-app/ We have also improved the data loading process and now it does not need so many resources as before (using async lib to control with queue the number of queries in parallel). Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Thu Jul 16 07:37:43 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Thu, 16 Jul 2015 07:37:43 +0200 Subject: [Fiware-developer-experience] Doubts about the architecture/application In-Reply-To: References: Message-ID: <1437025063.1904.60.camel@bitergia.com> Hi all! El mi?, 15-07-2015 a las 20:35 +0200, Alberto Mart?n Casado escribi?: > Hi! > > 2015-07-15 19:04 GMT+02:00 Pablo Fern?ndez Moniz > : > Hi! > We have some development progress, and we want to share it > and raise some questions > Architecture overview: > > Actually we have an implementation like this. > > > * Represented in white color we have the previous > containers that were in the docker-compose. > > * mongodb: It stores the database of Orion. It > has attached the mogodbdata volume. > > * orion: It has the Context Broker installed. It > uses the mogodb image as database. > > * devguide: It has implemented the API for > restaurant management. It interacts with orion > and it acts like an abstraction layer. > > * Blue elements have been added to the docker compose by > the ULPGC group. > > * idm: It runs an instance of the Identity > Management. Users and roles must be stored > here. > > * authzforce: Image needed by idm. > > * Finally, elements that have not been added yet to a > container are in yellow. > > * initUsers.py: It is a python script that > creates the first users and roles in Identity > Manager. > > * flask server: It hosts the web and acts as > intermediate layer between users and the > Identity Manager. > > > > > > > Captura de pantalla 2015-07-15 a las 13.07.42.png > > > > > > Doubts that have arisen > > We need to initialize the IdM with default values ( for > example roles ) so, for the moment, we developed a small > python script (initUsers.py) to do that. > > > > > We've been through this already in the image. Few days ago we've > updated the documentation of our IdM image with the users, orgs, roles > and everything that we've provided. You can find here the method we've > used for that (hope it helps). I think the best approach is that you don't need to work in this provision for users, roles, organizations and others. We need to share a common view here and we can implement the provision as Alberto said. > > > Due to cross domain restriction, we cannot perform petitions > directly to the IdM from the front end. We solved this using > an intermediate layer in the server that controls the user > creation and the login . Another solution could be to use a > proxy. We offer an auth API REST in the same server where you download the client, so this kind of problems won't appear if you use it in tour client. > > > Furthermore, in order to allow users to sign up, we need an > administrative credential to create the new user entity. If > this credential is used from the front end, it could be a > security risk. So, we think that the actual approach of > managing the operations related to the IdM from the server > side is correct. Yes, I think so. > > > > > The PEP Proxy could be the intermediate layer to handle this access. > The approach could be, an administrator that is able to handle users, > organizations, roles and permissions. Then, create different roles, > allowing just the administrator to use requests for user > administration using the Keystone API. We've updated today also the > PEP Wilma image and > documentation: https://registry.hub.docker.com/u/bitergia/pep-wilma/ > > > Doing this, we include another GE to the architecture proposed :) I am not sure I am understanding right this proposal. IMHO we can: * Provision initial users, roles, organizations, applications and others. * Offer and API REST so already provided users can authenticate and get the tokens for accessing the service. * The petitions to the service will be routed through PEP Wilma (we can do it later) in order to check permissions. > > > On the other hand, we have started to make some development in > the server side. We are using python since we have experience > with it and we have had good results using it. We also have > good feelings with other languages such as PHP. > > > > > I personally feel more comfortable with python, but I cannot speak > from the others. In my imaged architecture, you don't need any server development. We will offer you a REST API so you can just work client side consuming it. Pablo, what do you think? It is the approach followed in chanchan. Attached a file with chanchan current arch. > > We don?t know which language are you using at this moment, but > we think that the less different languages we use the better > for making an easy guide. > > > > > Actually we've been using javascript (node, angular) for the > application, shell scripts and a bit of python. All our work as Alberto said is implemented using Javascript to simplify the environment. Some minor scripts are in Python, but it is not the "core". > > > Finally, we suggest that we should add a new image that > contains the web server. > > > > > What do you need for the web server exactly? In the > fiware-devguide-app we have already an apache2.4 with phusion > passenger, and it teorically supports node, ruby and python. If > something like that is enough, we can create a clean container with > this for start deploying the web server. > In my mind I image you deploying your client in the current devguide docker image, in the directory: https://github.com/Bitergia/fiware-devguide-app/tree/master/client and it will be served by the same apache server alberto commented above. > > What do you think? > > > > > Looks good! We will also have to add IDAS, and other components (as > the PEP proxy mentioned before), but step by step :) Probably you don't need to play directly with other componentes/GEs. We can complete the REST API with your client needs. Cheers > > > KR, and sorry for the large email :) > > > ULPGC team > > > > > > > > Cheers, > > > > > > > Alberto Mart?n > > > -- > > Pablo Fern?ndez Moniz > > GIT Analyst > > > Web Linkedin Twitter > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" -------------- next part -------------- A non-text attachment was scrubbed... Name: ChanChanArchDocker.pdf Type: application/pdf Size: 26350 bytes Desc: not available URL: From josemanuel.canterafonseca at telefonica.com Mon Jul 20 12:01:37 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Mon, 20 Jul 2015 10:01:37 +0000 Subject: [Fiware-developer-experience] Catch-up meeting Message-ID: ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3071 bytes Desc: not available URL: From acs at bitergia.com Tue Jul 21 13:14:01 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 21 Jul 2015 13:14:01 +0200 Subject: [Fiware-developer-experience] Bitergia team vacations Message-ID: <1437477241.19466.7.camel@bitergia.com> Hi all! Our team will have active one person at least during all summer. I will be on vacation from 10-28 August. Alberto is now on vacation until next week. And David will get vacations in September. So the project should flow correctly during summer. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Tue Jul 21 14:31:11 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 21 Jul 2015 14:31:11 +0200 Subject: [Fiware-developer-experience] Geoqueries disponible Message-ID: <1437481871.19466.12.camel@bitergia.com> Hola! Acabamos de subir el soporte para realizar geoqueries. La API es la misma que ya hab?a de b?squedas para restaurantes, pero pas?ndole como par?metros la lat, long y radio. Un ejemplo: http://compose_devguide_1/api/orion/restaurants?lat=42.8391135197085&long=-2.513676680291502&radius=10000 Obtiene los tres restaurantes que est?n en un radio de 10 Km (10000 mts) del restaurante Elizalde (lat=42.8391135197085&long=-2.513676680291502). El resultado incluye: "id": "Elizalde", "id": "El Caser?n", "id": "Armentegi" Cualquier comentario es bienvenido! Los detalles de la implementaci?n: https://github.com/Bitergia/fiware-devguide-app/commit/b53b1933c1d0d6b4cb37f3b9a17e1e3b2c695f8e#diff-32cf9b4c9277f51566c24801c8cb46fcL171 Hasta luego! -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Tue Jul 21 14:46:30 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Tue, 21 Jul 2015 13:46:30 +0100 Subject: [Fiware-developer-experience] Bitergia team vacations In-Reply-To: <1437477241.19466.7.camel@bitergia.com> References: <1437477241.19466.7.camel@bitergia.com> Message-ID: Hi, We will be on vacation from 1 to 15 August. So from our side would be good to start closing/directing issues of our tasks. KR 2015-07-21 12:14 GMT+01:00 Alvaro del Castillo : > Hi all! > > Our team will have active one person at least during all summer. > > I will be on vacation from 10-28 August. Alberto is now on vacation > until next week. And David will get vacations in September. > > So the project should flow correctly during summer. > > Cheers > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Tue Jul 21 15:47:47 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 21 Jul 2015 15:47:47 +0200 Subject: [Fiware-developer-experience] Bitergia team vacations In-Reply-To: References: <1437477241.19466.7.camel@bitergia.com> Message-ID: <1437486467.19466.14.camel@bitergia.com> Hi! El mar, 21-07-2015 a las 13:46 +0100, Pablo Fern?ndez Moniz escribi?: > Hi, > > > We will be on vacation from 1 to 15 August. So from our side would be > good to start closing/directing issues of our tasks. > IMHO the key issue is to have a working client in the devguide docker image. With this working, we can continue with all auth details, completing the API REST and other tasks. Cheers > > KR > > 2015-07-21 12:14 GMT+01:00 Alvaro del Castillo : > Hi all! > > Our team will have active one person at least during all > summer. > > I will be on vacation from 10-28 August. Alberto is now on > vacation > until next week. And David will get vacations in September. > > So the project should flow correctly during summer. > > Cheers > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) > http://www.bitergia.com > "Software metrics for your peace of mind" > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > > > > -- > > Pablo Fern?ndez Moniz > > GIT Analyst > > > Web Linkedin Twitter > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Wed Jul 22 07:09:15 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 22 Jul 2015 07:09:15 +0200 Subject: [Fiware-developer-experience] Ready the docker image with restaurant data in docker hub Message-ID: <1437541755.19466.29.camel@bitergia.com> Hi guys! Yesterday we finished the creation of a new image in docker hub with the restaurant data. In order to use it: fiware-devguide-app/docker/compose $ docker-compose -f docker-compose-preloaded-data.yml up So you don't need to load the data yourself anymore. https://registry.hub.docker.com/u/bitergia/fiware-devguide-restaurant-data/ Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Wed Jul 22 11:20:52 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Wed, 22 Jul 2015 10:20:52 +0100 Subject: [Fiware-developer-experience] Client side Message-ID: Hi all, We just upload the light client in GitHub: In the current state, we had removed all the code from the server side, therefore we dont have real authentication process. Authentication must be implemented from the client side when its API is ready. On the other hand, we have converted the Jinja2 templates to static html files. Making requests to the restaurants API (or making them to the authentication API in the future) have cross-domain issues. We suggest some solutions: * Add the header 'Access-Control-Allow-Origin: *' to the API responses. * Use a proxy. * Have the web and the API in the same domain. For now, we provided a PHP proxy. The proxy url (which should be in the same domain that the web application) must be set in the variable proxy at the top of the restaurants_api.js file. Following we explain how was the code before we removed our server side part. We used the bitergia IdM docker adding to the composer file using this instructions: authzforce: image: bitergia/authzforce:4.2.0 expose: - "8080" idm: image: bitergia/idm-keyrock:4.3.0 links: - authzforce volumes: - /config expose: - "5000" We developed a little Flask application as server. This application had a method to authenticate users using the IdM. User info, as could be the token, the identificator and roles, was saved in session variables. Using these session variables the application decided which pages should be shown. At render time, we were using Jinja2 templates which allowed us to display differents sections based on values of the variables. The Flask application also implemented a proxy that allowed us to make AJAX petititions to the restaurants API. KR, ULPGC Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From josemanuel.canterafonseca at telefonica.com Wed Jul 22 11:23:57 2015 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Wed, 22 Jul 2015 09:23:57 +0000 Subject: [Fiware-developer-experience] Client side In-Reply-To: References: Message-ID: Making requests to the restaurants API (or making them to the authentication API in the future) have cross-domain issues. But that is not going to happen, as we said yesterday the Web Content and the "API Services" will be on the same server. best De: > on behalf of Pablo Fern?ndez Moniz > Fecha: mi?rcoles, 22 de julio de 2015, 11:20 Para: "fiware-developer-experience at lists.fiware.org" > Asunto: [Fiware-developer-experience] Client side Hi all, We just upload the light client in GitHub: In the current state, we had removed all the code from the server side, therefore we dont have real authentication process. Authentication must be implemented from the client side when its API is ready. On the other hand, we have converted the Jinja2 templates to static html files. Making requests to the restaurants API (or making them to the authentication API in the future) have cross-domain issues. We suggest some solutions: * Add the header 'Access-Control-Allow-Origin: *' to the API responses. * Use a proxy. * Have the web and the API in the same domain. For now, we provided a PHP proxy. The proxy url (which should be in the same domain that the web application) must be set in the variable proxy at the top of the restaurants_api.js file. Following we explain how was the code before we removed our server side part. We used the bitergia IdM docker adding to the composer file using this instructions: authzforce: image: bitergia/authzforce:4.2.0 expose: - "8080" idm: image: bitergia/idm-keyrock:4.3.0 links: - authzforce volumes: - /config expose: - "5000" We developed a little Flask application as server. This application had a method to authenticate users using the IdM. User info, as could be the token, the identificator and roles, was saved in session variables. Using these session variables the application decided which pages should be shown. At render time, we were using Jinja2 templates which allowed us to display differents sections based on values of the variables. The Flask application also implemented a proxy that allowed us to make AJAX petititions to the restaurants API. KR, ULPGC Team ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Wed Jul 22 12:25:54 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 22 Jul 2015 12:25:54 +0200 Subject: [Fiware-developer-experience] Client side In-Reply-To: References: Message-ID: <1437560754.19466.35.camel@bitergia.com> Hi! El mi?, 22-07-2015 a las 10:20 +0100, Pablo Fern?ndez Moniz escribi?: > Hi all, > > > We just upload the light client in GitHub: > Great! > > In the current state, we had removed all the code from the server > side, therefore we dont have real authentication process. > Ok, we will propose an implementation similar to what is working in chanchan, using IDM, Authzforge and PEP Proxy so the complete IDM management could be explained in the devguide. > > Authentication must be implemented from the client side when its API > is ready. > > > On the other hand, we have converted the Jinja2 templates to static > html files. > > > > > Making requests to the restaurants API (or making them to the > authentication API in the future) have cross-domain issues. We suggest > some solutions: > > > * Add the header 'Access-Control-Allow-Origin: *' to the API > responses. > * Use a proxy. > * Have the web and the API in the same domain. > > > For now, we provided a PHP proxy. The proxy url (which should be in > the same domain that the web application) must be set in the variable > proxy at the top of the restaurants_api.js file. > The web server is serving the client and the REST API, so they are sharing domain and no cross domains issues appear. Right now the docker image in the hub has all working so in order to test the client and server together you just need to: fiware-devguide-app/docker/compose $ docker-compose up sudo get-docker-hosts -m and go to the URL: http://compose_devguide_1/client/all_restaurants_and_reviews.html Next steps: * Complete auth in the client and server (we will create a proposal from bitergia) * Add reviews view: data already available in the image * Add reservations view: data already available in the image A pretty easy integration. Great! Cheers > > > > Following we explain how was the code before we removed our server > side part. > > > > We used the bitergia IdM docker adding to the composer file using this > instructions: > > > > > authzforce: > image: bitergia/authzforce:4.2.0 > expose: > - "8080" > > > idm: > image: bitergia/idm-keyrock:4.3.0 > links: > - authzforce > volumes: > - /config > expose: > - "5000" > > > > > We developed a little Flask application as server. This application > had a method to authenticate users using the IdM. User info, as could > be the token, the identificator and roles, was saved in session > variables. > > > Using these session variables the application decided which pages > should be shown. > > > At render time, we were using Jinja2 templates which allowed us to > display differents sections based on values of the variables. > > > The Flask application also implemented a proxy that allowed us to make > AJAX petititions to the restaurants API. > > > > > KR, > > > ULPGC Team > > > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From pablofernandezmoniz at gmail.com Wed Jul 22 16:49:49 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Wed, 22 Jul 2015 15:49:49 +0100 Subject: [Fiware-developer-experience] Minor Issue in JSON response Message-ID: Hi! We have downloaded the new images and now we have a problem parsing the JSON response for the http://compose_devguide_1/api/orion/restaurants/ petition. Concretely, we get the an "SyntaxError: JSON.parse: bad control character in string literal at line 65332 column 120 of the JSON data" error when we use the *JSON.parse* function. If we used a online JSON validator (wich could be http://www.freeformatter.com/json-validator.html or http://jsonformatter.curiousconcept.com/ ) using the response, it doesn't pass it. One of the detected errors is the use of doble quotes inside strings. An example of this issue of the Zarate restaurant can be examined in the image [QuoteError] Also we still have no data on reservations, is that what we have to expect for the moment? Maybe we are doing something wrong? Another minor issue is that the API is not providing a JSON response although we use the Accept: application/json header. The API always return a tex/html as Content-Type, see [NotJSONResponse] Do you think possible, or recommendable, to return the response directly as JSON format? This should makes a little easier to parse the content from the front end. KR ULPGC Team -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: notJSONResponse.png Type: image/png Size: 392315 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: QuoteError.png Type: image/png Size: 158861 bytes Desc: not available URL: From dmuriel at bitergia.com Thu Jul 23 00:26:59 2015 From: dmuriel at bitergia.com (David Muriel) Date: Thu, 23 Jul 2015 00:26:59 +0200 Subject: [Fiware-developer-experience] Minor Issue in JSON response In-Reply-To: References: Message-ID: On Wed, Jul 22, 2015 at 4:49 PM, Pablo Fern?ndez Moniz wrote: > Hi! Hello, > We have downloaded the new images and now we have a problem parsing the JSON > response for the http://compose_devguide_1/api/orion/restaurants/ petition. > > Concretely, we get the an "SyntaxError: JSON.parse: bad control character > in string literal at line 65332 column 120 of the JSON data" error when we > use the JSON.parse function. > > If we used a online JSON validator (wich could be > http://www.freeformatter.com/json-validator.html or > http://jsonformatter.curiousconcept.com/ ) using the response, it doesn't > pass it. I've tried http://www.freeformatter.com/json-validator.html and it says: The JSON input is valid in JavaScript. The JSON input is valid according to RFC 4627 (JSON specfication). > One of the detected errors is the use of doble quotes inside strings. An > example of this issue of the Zarate restaurant can be examined in the image > [QuoteError] Yesterday (tuesday 21st) we pushed the fix for this bug. I'm testing it right now with the latest images and it's returning the quotes properly escaped. Also, are you loading the data via the restaurant_feeder.js script or using the preloaded data image? Maybe we didn't notify you of this fix, sorry. > Also we still have no data on reservations, is that what we have to expect > for the moment? The preloaded data image has data for reservations and reviews (created via the reservations_generator.js and reviews_generator.js scripts). > Maybe we are doing something wrong? > > Another minor issue is that the API is not providing a JSON response > although we use the Accept: application/json header. The API always return a > tex/html as Content-Type, see [NotJSONResponse] > > Do you think possible, or recommendable, to return the response directly as > JSON format? This should makes a little easier to parse the content from the > front end. I've just pushed a fix to add the header when returning JSON data from orion. A new version of the fiware-devguide-app image has just finished building on docker hub. Regards, -- David Muriel. From pablofernandezmoniz at gmail.com Thu Jul 23 10:21:20 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Thu, 23 Jul 2015 09:21:20 +0100 Subject: [Fiware-developer-experience] Minor Issue in JSON response In-Reply-To: References: Message-ID: Great! It seems to be working now. We force the delete of all dockers and download the again. Thank you, 2015-07-22 23:26 GMT+01:00 David Muriel : > On Wed, Jul 22, 2015 at 4:49 PM, Pablo Fern?ndez Moniz > wrote: > > Hi! > > Hello, > > > We have downloaded the new images and now we have a problem parsing the > JSON > > response for the http://compose_devguide_1/api/orion/restaurants/ > petition. > > > > Concretely, we get the an "SyntaxError: JSON.parse: bad control > character > > in string literal at line 65332 column 120 of the JSON data" error when > we > > use the JSON.parse function. > > > > If we used a online JSON validator (wich could be > > http://www.freeformatter.com/json-validator.html or > > http://jsonformatter.curiousconcept.com/ ) using the response, it > doesn't > > pass it. > > I've tried http://www.freeformatter.com/json-validator.html and it says: > > The JSON input is valid in JavaScript. > The JSON input is valid according to RFC 4627 (JSON specfication). > > > One of the detected errors is the use of doble quotes inside strings. An > > example of this issue of the Zarate restaurant can be examined in the > image > > [QuoteError] > > Yesterday (tuesday 21st) we pushed the fix for this bug. I'm testing > it right now with the latest images and it's returning the quotes > properly escaped. Also, are you loading the data via the > restaurant_feeder.js script or using the preloaded data image? Maybe > we didn't notify you of this fix, sorry. > > > Also we still have no data on reservations, is that what we have to > expect > > for the moment? > > The preloaded data image has data for reservations and reviews > (created via the reservations_generator.js and reviews_generator.js > scripts). > > > Maybe we are doing something wrong? > > > > Another minor issue is that the API is not providing a JSON response > > although we use the Accept: application/json header. The API always > return a > > tex/html as Content-Type, see [NotJSONResponse] > > > > Do you think possible, or recommendable, to return the response directly > as > > JSON format? This should makes a little easier to parse the content from > the > > front end. > > I've just pushed a fix to add the header when returning JSON data from > orion. A new version of the fiware-devguide-app image has just > finished building on docker hub. > > Regards, > > -- > David Muriel. > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablofernandezmoniz at gmail.com Mon Jul 27 17:17:01 2015 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Mon, 27 Jul 2015 16:17:01 +0100 Subject: [Fiware-developer-experience] Client Update Message-ID: Hi all We just pushed the first client prototype that uses a popup window to display restaurant reviews and reservations. Using this client, you should be able to retrieve all restaurants. When a restaurant push pin is clicked, basic information about the restaurant is shown in the pushpin. This pushpin has two links, one for show the restaurant reviews and another one to show the restaurant reservations. We hope that this client will be helpful to further develop the API during these days. Note that the interface will be changed and this is only a functional prototype. KR -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Mon Jul 27 19:28:45 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 27 Jul 2015 19:28:45 +0200 Subject: [Fiware-developer-experience] Client Update In-Reply-To: References: Message-ID: <1438018125.26129.34.camel@bitergia.com> El lun, 27-07-2015 a las 16:17 +0100, Pablo Fern?ndez Moniz escribi?: > Hi all > > > We just pushed the first client prototype that uses a popup window to > display restaurant reviews and reservations. > > > Using this client, you should be able to retrieve all restaurants. > > > When a restaurant push pin is clicked, basic information about the > restaurant is shown in the pushpin. This pushpin has two links, one > for show the restaurant reviews and another one to show the restaurant > reservations. > > We hope that this client will be helpful to further develop the API > during these days. > > Note that the interface will be changed and this is only a functional > prototype. Great, it is working using the last devguide image from docker hub. Cheers! > > > KR > > > -- > > Pablo Fern?ndez Moniz > > GIT Analyst > > > Web Linkedin Twitter > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From alberto.martin at bitergia.com Wed Jul 29 12:43:27 2015 From: alberto.martin at bitergia.com (=?UTF-8?Q?Alberto_Mart=C3=ADn_Casado?=) Date: Wed, 29 Jul 2015 12:43:27 +0200 Subject: [Fiware-developer-experience] Oauth authentication Message-ID: Hi all! As we agreed during the meeting yesterday, we've updated the fiware-devguide-app with a first version for the Oauth authentication. With this, the main page of the fiware-devguide-app ( http://compose_devguide_1) will show a simple link to log in against IdM. You can test with any of the users listed here . When you press it, it will redirect to IdM to authorize the app, and once authorized, to the fiware-devguide-app back getting the username you've choose to log-in. For testing it, you should update the idm-keyrock and fiware-devguide-app images from the DockerHub registry. Then, as usually, run the docker-compose provided at fiware-devguide-app. Note that as is just for testing, the host for the moment is hard-coded at the IdM as 'compose_devguide_1', as it is how it works with the compose; so if you change it in any case, the Oauth authentication will stop working. We will handle this as soon as we get the first version of the roles and permissions. Best, Alberto Mart?n -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Wed Jul 29 13:31:43 2015 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 29 Jul 2015 13:31:43 +0200 Subject: [Fiware-developer-experience] Oauth authentication In-Reply-To: References: Message-ID: <1438169503.2656.44.camel@bitergia.com> Hi! El mi?, 29-07-2015 a las 12:43 +0200, Alberto Mart?n Casado escribi?: > Hi all! > > > As we agreed during the meeting yesterday, we've updated the > fiware-devguide-app with a first version for the Oauth authentication. > > > With this, the main page of the fiware-devguide-app > (http://compose_devguide_1) will show a simple link to log in against > IdM. You can test with any of the users listed here. > > > When you press it, it will redirect to IdM to authorize the app, and > once authorized, to the fiware-devguide-app back getting the username > you've choose to log-in. > I think that in the callback you receive also the token for the user. This token should be carefully stored in the client. In the future you will need to provide this token in all REST API operations and depending on it, you will get the results or no authorized error. > > For testing it, you should update the idm-keyrock and > fiware-devguide-app images from the DockerHub registry. Then, as > usually, run the docker-compose provided at fiware-devguide-app. > > > Note that as is just for testing, the host for the moment is > hard-coded at the IdM as 'compose_devguide_1', as it is how it works > with the compose; so if you change it in any case, the Oauth > authentication will stop working. > > > We will handle this as soon as we get the first version of the roles > and permissions. > Great!! Cheers > > Best, > > > > > Alberto Mart?n > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind"