dear sergio and nuno, reading this quite interesting thread i have update the info in the shared "fiware accelerators project statistics" at https://docs.google.com/spreadsheets/d/1jeF3Xy7I_6MdQE1OaFII0HGH1CUU44S7B-tAqvR4Vqw/edit# . of course there are info missing for all the other projects, but i started just to show you what is expected. also this thread is a very good example, not only of a serious team, but also of the evolution from "e" to "u" and, hopefully soon, to "d". what i mean is that this thread gives us the evolution of what was the initial understanding of people and what instead is actually happening. of course i guess you are also already evaluating the info through the questionnaire recently distributed by juanjo, but also info in this shared spreadsheet are very important. indeed we used what we had already during the recent fi-core review meeting there the expectation of the ec, but also giving the all of us the effective level of fiware technologies appreciation. as we are also in a deep revision of the fi-core dow, i kindly ask you to fill in the info as soon as you can (this week ...;-) ). higly appreciated your help on the matter! ciao, stefano 2015-08-27 9:24 GMT+02:00 SERGIO GARCIA GOMEZ < sergio.garciagomez at telefonica.com>: > Just adding Nuno to the loop. > > > > *De:* fiware-soulfi-coaching-bounces at lists.fi-ware.org [mailto: > fiware-soulfi-coaching-bounces at lists.fi-ware.org] *En nombre de *SERGIO > GARCIA GOMEZ > *Enviado el:* 27 August 2015 08:33 > *Para:* Viral Team; fiware-soulfi-coaching at lists.fi-ware.org > *CC:* alexandre at fimdomeio.com > *Asunto:* Re: [Fiware-soulfi-coaching] Fwd: FIWARE Questions - usage > assessment - SOUL-FI Round B > > > > Dear all, > > > > The security mechanisms purpose is twofold: to provide you with federated > global services that provide security (if you don’t want to do it by > yourself) and to offer you some tools that you could use as part of your > architecture. Both cases are a possibility, but not mandatory. > > > > Cosmos purpose is to deploy on demand clusters, which is something that > you usually don’t want to do as a Hadoop user. You have two options then: > to use the existing global cluster (to avoid deploying your own at least in > development phase), or to deploy your cluster with any existing Hadoop > distribution (e.g. Hortonworks). That’s fine, but of course means not using > FIWARE. > > > > Regarding SpagoBI, you have several options: > > • Using NGSI (real time) to feed their event processing tool > and show/process data in real time > > • Store historic NGSI data (check Cygnus) and exploiting that > with some analysis and reporting. > > Both cases are a good idea. > > > > I hope I solved your issues, let me know otherwise. > > > > I cc Nuno, in case we wants to add something from the contractual point of > view. Globally, I would say you are doing good usage of FIWARE technologies. > > > > Best Regards, > > > > Sergio. > > > > > > *De:* fiware-soulfi-coaching-bounces at lists.fi-ware.org [ > mailto:fiware-soulfi-coaching-bounces at lists.fi-ware.org > <fiware-soulfi-coaching-bounces at lists.fi-ware.org>] *En nombre de *Viral > Team > *Enviado el:* 25 August 2015 18:14 > *Para:* fiware-soulfi-coaching at lists.fi-ware.org > *CC:* alexandre at fimdomeio.com > *Asunto:* [Fiware-soulfi-coaching] Fwd: FIWARE Questions - usage > assessment - SOUL-FI Round B > > > > > > C/O Sergio Garcia Gomez > > > > Dear Sergio, > > I write on behalf of the Viral <http://www.viralagenda.com/> project > selected for SOUL-FI Round B. We have some doubts that we would like to > clarify with you before submitting the survey regarding FIWARE > technologies. Our initial proposal included the use of the following GEs: > Orion Context Broker, Cosmos, Complex Event Processing (CEP) - Proactive > Technology Online; Identity Management - KeyRock, PEP Proxy - Wilma and > Authorization PDP - AuthZForce. Nevertheless, we are now considering some > changes, and we’d like to know your opinion. > > Until now we’ve been exploring mainly the GE’s Orion Context Broker and > CEP Proton which we managed to install, populate and start to test > effectively in our project. These GE’s will have a key role in our > application, especially in the mobile context. We have almost finished the > development of users authentication in our platform (aside of the > authentication through Facebook which is already in production) that is not > using FIWARE technologies, and that has raised major doubts concerning the > usage of the *security modules*. As we already have a quite large > codebase and authentication implemented we are concerned that implementing > the security/authorisation through the GE’s will result in data redundancy > and create some integration problems that will be harder to manage. Is it > imperative that we use FIWARE modules (Keyrock, PEP, AuthZforce) to secure > Orion and CEP? Or do you think it may be viable to have Orion Context > Broker and CEP in our private network (without external access) and that > all requests from authorised users in our platform are routed through our > server to the GE’s? Would this be ok? > > Regarding the use of *Cosmos*, by the time of submission, this module was > presented as a tool to analyse the Big Data we would generate. It wasn’t > clear that the module’s function was actually to provide ways for others > to perform Big Data Analysis. Given this, we were advised to use Apache > Hadoop instead. Regarding the analysis of the data that we generate we plan > to use SPAGO BI, in integration with the Orion Context Broker so we can > visualize some of the context data generated in real time. What do you > think of this? > > This email is also sent in CC for Alexandre Castro that is our new member > team that will be in charge to integrate FIWARE technologies. > > > > Best regards, > > > > *Tiago Abelha* > > team at viralagenda.com > > www.viralagenda.com > > > > > > > > ------------------------------ > > > 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 > > _______________________________________________ > Fiware-soulfi-coaching mailing list > Fiware-soulfi-coaching at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-soulfi-coaching > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-06-8759-4253 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 twitter: @depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-soulfi-coaching/attachments/20150827/65d7b0c1/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy