From sergg at tid.es Mon Apr 7 11:52:08 2014 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 07 Apr 2014 09:52:08 +0000 Subject: [Fiware-espoo] [Fiware-smartcities] FI-WARE technology webinars Message-ID: <03BE306058976141B4883174DF62D54D0102DFF12B@EX10-MB2-MAD.hi.inet> Dear all, Let me share with you the recordings of the webinars that took place last week. ? Identity Manager: http://stream.globalplaza.org/videos/fi-ware/Webinar_31_3_2014-01.mp4 ? Advance Cloud: http://stream.globalplaza.org/videos/fi-ware/Webinar_31_3_2014-02.mp4 ? Wirecloud: http://stream.globalplaza.org/videos/fi-ware/Webinar_31_3_2014-03.mp4 ? Kurento: http://stream.globalplaza.org/videos/fi-ware/Webinar_1_4_2014-01.mp4 ? DCA an Figway: http://stream.globalplaza.org/videos/fi-ware/Webinar_1_4_2014-02.mp4 ? Orion Context Broker: http://stream.globalplaza.org/videos/fi-ware/Webinar_1_4_2014-03.mp4 ? Cosmos Big Data: http://stream.globalplaza.org/videos/fi-ware/Webinar_1_4_2014-04.mp4 Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica (TI+D) FI-WARE [http://www.fi-ware.org] Parque Tecnologico de Boecillo. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 9131.29098 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-smartcities mailing list Fiware-smartcities at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-smartcities From fermin at tid.es Tue Apr 8 10:40:15 2014 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Tue, 08 Apr 2014 10:40:15 +0200 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> Message-ID: <5343B5EF.10403@tid.es> Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Timo.Toivanen at vtt.fi Wed Apr 9 07:53:17 2014 From: Timo.Toivanen at vtt.fi (Toivanen Timo) Date: Wed, 9 Apr 2014 05:53:17 +0000 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <5343B5EF.10403@tid.es> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> <5343B5EF.10403@tid.es> Message-ID: <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> Hi Fermin, Thank you for the response. I have some additional questions as we are developing our Espoo connection to the Fi-Ware. - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Cheers, Timo From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Ferm?n Gal?n M?rquez Sent: 8. huhtikuuta 2014 11:40 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergg at tid.es Wed Apr 9 17:06:07 2014 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 09 Apr 2014 15:06:07 +0000 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> <5343B5EF.10403@tid.es> <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> Message-ID: <03BE306058976141B4883174DF62D54D0102E08812@EX10-MB2-MAD.hi.inet> Dear Timo, - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? Yes, there is a global instance in FI-Lab and another one in the PPP Testbed. The easiest way is that you access http://orion-psb.testbed.fi-ware.eu:1026/ For that access to work, you should give us the IP from where you access (to allow it in the firewall) - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? Only for the global instance in Fi-lab (protected with OAuth). If you use the testbed instance mentioned above, the firewall configuration is enough. - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Yes, there is a mechanism for that. I cc Francisco, in charge of that part. He can guide you and give you pointers to learn how to store the data and query it. Best Regards, Sergio. From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Toivanen Timo Sent: Wednesday, April 09, 2014 07:53 To: FERMIN GALAN MARQUEZ Cc: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi Fermin, Thank you for the response. I have some additional questions as we are developing our Espoo connection to the Fi-Ware. - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Cheers, Timo From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Ferm?n Gal?n M?rquez Sent: 8. huhtikuuta 2014 11:40 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Timo.Toivanen at vtt.fi Wed Apr 16 12:44:43 2014 From: Timo.Toivanen at vtt.fi (Toivanen Timo) Date: Wed, 16 Apr 2014 10:44:43 +0000 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <03BE306058976141B4883174DF62D54D0102E08812@EX10-MB2-MAD.hi.inet> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> <5343B5EF.10403@tid.es> <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102E08812@EX10-MB2-MAD.hi.inet> Message-ID: <794E6A421CDCEB48AE95154D83A02D180BB99D@VTTMAIL4.ad.vtt.fi> Hi Sergio, We could start testing with the Testbed instance. Could you open following IP-addresses so that we can start testing: - 54.194.17.255 : VTT platform - 130.188.0.0 : VTT network to allow testing from our development computers Best Regards, Timo From: SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] Sent: 9. huhtikuuta 2014 18:06 To: Toivanen Timo; FERMIN GALAN MARQUEZ; FRANCISCO ROMERO BUENO Cc: fiware-espoo at lists.fi-ware.eu Subject: RE: [Fiware-espoo] FW: Espo connection to FI-Lab Dear Timo, - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? Yes, there is a global instance in FI-Lab and another one in the PPP Testbed. The easiest way is that you access http://orion-psb.testbed.fi-ware.eu:1026/ For that access to work, you should give us the IP from where you access (to allow it in the firewall) - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? Only for the global instance in Fi-lab (protected with OAuth). If you use the testbed instance mentioned above, the firewall configuration is enough. - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Yes, there is a mechanism for that. I cc Francisco, in charge of that part. He can guide you and give you pointers to learn how to store the data and query it. Best Regards, Sergio. From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Toivanen Timo Sent: Wednesday, April 09, 2014 07:53 To: FERMIN GALAN MARQUEZ Cc: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi Fermin, Thank you for the response. I have some additional questions as we are developing our Espoo connection to the Fi-Ware. - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Cheers, Timo From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Ferm?n Gal?n M?rquez Sent: 8. huhtikuuta 2014 11:40 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From frb at tid.es Mon Apr 21 16:16:55 2014 From: frb at tid.es (FRANCISCO ROMERO BUENO) Date: Mon, 21 Apr 2014 14:16:55 +0000 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <794E6A421CDCEB48AE95154D83A02D180BB99D@VTTMAIL4.ad.vtt.fi> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> <5343B5EF.10403@tid.es> <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102E08812@EX10-MB2-MAD.hi.inet> <794E6A421CDCEB48AE95154D83A02D180BB99D@VTTMAIL4.ad.vtt.fi> Message-ID: Hi Timo, As Sergio has told you, there exists a mechanism for persisting context data managed by Orion into Cosmos. This mechanism is a piece of software based on Flume (the ?standard? for such data injection tasks in the Hadoop world) which is called Cygnus and is available here: https://github.com/telefonicaid/fiware-connectors/tree/develop/flume (release/0.1 branch, or release-0.1 tag). Cygnus is typically installed in the same machine where Orion runs; a step-by-step installation and configuration guide is available in the README.md of the above URL. Once the data has been persisted in Cosmos it can be queried by using HiveQL, a querying language very close to SQL. In order to execute HiveQL sentences, you can do it: ? Locally to the Head Node of the Cosmos cluster, i.e. by login into the Head Node if you own an account (I can create you one) and invoking the Hive or Shark interpreter. o Hive is the native interpreter that gives name to HiveQL, Shark is a new and a faster alternative. ? Remotely by building your own HiveQL client o An example can be found at https://github.com/telefonicaid/fiware-connectors/tree/develop/resources/hive-basic-client (develop branch). Regards, Paco De: Toivanen Timo [mailto:Timo.Toivanen at vtt.fi] Enviado el: mi?rcoles, 16 de abril de 2014 12:45 Para: SERGIO GARCIA GOMEZ; FERMIN GALAN MARQUEZ; FRANCISCO ROMERO BUENO CC: fiware-espoo at lists.fi-ware.eu Asunto: RE: [Fiware-espoo] FW: Espo connection to FI-Lab Hi Sergio, We could start testing with the Testbed instance. Could you open following IP-addresses so that we can start testing: - 54.194.17.255 : VTT platform - 130.188.0.0 : VTT network to allow testing from our development computers Best Regards, Timo From: SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] Sent: 9. huhtikuuta 2014 18:06 To: Toivanen Timo; FERMIN GALAN MARQUEZ; FRANCISCO ROMERO BUENO Cc: fiware-espoo at lists.fi-ware.eu Subject: RE: [Fiware-espoo] FW: Espo connection to FI-Lab Dear Timo, - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? Yes, there is a global instance in FI-Lab and another one in the PPP Testbed. The easiest way is that you access http://orion-psb.testbed.fi-ware.eu:1026/ For that access to work, you should give us the IP from where you access (to allow it in the firewall) - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? Only for the global instance in Fi-lab (protected with OAuth). If you use the testbed instance mentioned above, the firewall configuration is enough. - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Yes, there is a mechanism for that. I cc Francisco, in charge of that part. He can guide you and give you pointers to learn how to store the data and query it. Best Regards, Sergio. From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Toivanen Timo Sent: Wednesday, April 09, 2014 07:53 To: FERMIN GALAN MARQUEZ Cc: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi Fermin, Thank you for the response. I have some additional questions as we are developing our Espoo connection to the Fi-Ware. - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Cheers, Timo From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Ferm?n Gal?n M?rquez Sent: 8. huhtikuuta 2014 11:40 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon Apr 21 18:35:08 2014 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Mon, 21 Apr 2014 18:35:08 +0200 Subject: [Fiware-espoo] FW: Espo connection to FI-Lab In-Reply-To: <794E6A421CDCEB48AE95154D83A02D180BB99D@VTTMAIL4.ad.vtt.fi> References: <794E6A421CDCEB48AE95154D83A02D180AEA31@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102DFA31E@EX10-MB2-MAD.hi.inet> <5343B5EF.10403@tid.es> <794E6A421CDCEB48AE95154D83A02D180B96FC@VTTMAIL4.ad.vtt.fi> <03BE306058976141B4883174DF62D54D0102E08812@EX10-MB2-MAD.hi.inet> <794E6A421CDCEB48AE95154D83A02D180BB99D@VTTMAIL4.ad.vtt.fi> Message-ID: <535548BC.3090601@tid.es> Dear Timo, Traffic from the following IP prefixes to orion-psb.testbed.fi-ware.org:1026 has been authorized. [cid:part1.08070708.00020308 at tid.es] You can do a easy connectivity test running: curl orion-psb.testbed.fi-ware.org:1026/version Best regards, ------ Ferm?n El 16/04/2014 12:44, Toivanen Timo escribi?: Hi Sergio, We could start testing with the Testbed instance. Could you open following IP-addresses so that we can start testing: - 54.194.17.255 : VTT platform - 130.188.0.0 : VTT network to allow testing from our development computers Best Regards, Timo From: SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] Sent: 9. huhtikuuta 2014 18:06 To: Toivanen Timo; FERMIN GALAN MARQUEZ; FRANCISCO ROMERO BUENO Cc: fiware-espoo at lists.fi-ware.eu Subject: RE: [Fiware-espoo] FW: Espo connection to FI-Lab Dear Timo, - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? Yes, there is a global instance in FI-Lab and another one in the PPP Testbed. The easiest way is that you access http://orion-psb.testbed.fi-ware.eu:1026/ For that access to work, you should give us the IP from where you access (to allow it in the firewall) - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? Only for the global instance in Fi-lab (protected with OAuth). If you use the testbed instance mentioned above, the firewall configuration is enough. - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Yes, there is a mechanism for that. I cc Francisco, in charge of that part. He can guide you and give you pointers to learn how to store the data and query it. Best Regards, Sergio. From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Toivanen Timo Sent: Wednesday, April 09, 2014 07:53 To: FERMIN GALAN MARQUEZ Cc: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi Fermin, Thank you for the response. I have some additional questions as we are developing our Espoo connection to the Fi-Ware. - Is there any development instance of Orion Context Broker that we could use during the development phase? Or should create our own Context Broker instance to FI-Lab? - Is any context provider registration needed or is there any authentication requirement when using the Fi-ware Orion Context Broker? - Can we query historical data from the Context Broker? Or should query history data from Cosmos Big data? If so, does Context Broker automatically forward data to Cosmos? Cheers, Timo From: fiware-espoo-bounces at lists.fi-ware.org [mailto:fiware-espoo-bounces at lists.fi-ware.org] On Behalf Of Ferm?n Gal?n M?rquez Sent: 8. huhtikuuta 2014 11:40 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] FW: Espo connection to FI-Lab Hi, Sergio passed this question to me. I'm the one in charge of Orion Context Broker in FI-WARE. The updateContext payload you send is mostly fine. However, take into account the following comments: * Remove the attributes xsi:type, xmlns:xs and xmlns:xsi in contextValue tags. Orion doesn't pay any attention to them. * First time you send updateContext for a new entity (in this case entity ID 101005 of type weatherStation) you need to use APPEND as actionType in order to "create" the entity at Orion. Next updateContext requests (once the entity has been created) should use UPDATE (although APPEND is also allowed in that case: an APPEND actionType on existing context elements in interpreted as UPDATE). I hope this information helps... Best regards, ------ Ferm?n El 03/04/2014 15:50, SERGIO GARCIA GOMEZ escribi?: From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: Monday, March 17, 2014 07:58 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab Hi all, As planned, we are developing context provider to send messages to FI-Lab. I started with weather data and I?m creating NGSI updateContextRequest-messages for measurements made by Finnish Meteorological Institute. The measurements are provided in every 10 minutes and they include several different parameters like temperature, wind and precipitation. Here?s an example message, do you have any comments about it? How should I add station location and measurement timestamp information? Should they be included in their own contextAttribute-elements? BR, Timo From: fiware-espoo-bounces at lists.fi-ware.eu [mailto:fiware-espoo-bounces at lists.fi-ware.eu] On Behalf Of Toivanen Timo Sent: 6. maaliskuuta 2014 15:51 To: fiware-espoo at lists.fi-ware.eu Subject: Re: [Fiware-espoo] Espo connection to FI-Lab meeting notes Hi, In addition to update DoW-document description we made a short document about what data sources will be connected to FI-LAB. We have not yet fixed the showcase application. Best Regards, Timo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cecediif.png Type: image/png Size: 2698 bytes Desc: not available URL: From sergg at tid.es Tue Apr 29 17:12:58 2014 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 29 Apr 2014 15:12:58 +0000 Subject: [Fiware-espoo] [Fiware-smartcities] Smart Cities Kick Off Message-ID: <03BE306058976141B4883174DF62D54D012AAD64CA@EX10-MB1-MAD.hi.inet> Dear all, As you probably know, we have the approval of the FI-WARE amendment to start working with the Smart Citiy applications. I have prepared a doodle poll so that you can specify your availability. Please fill it in with your availability (if you are a team, just coordinate internally before answering the poll), and specify the name of the city and partner(s) in the name so that I can arrange the calls before the end of this week at http://doodle.com/7dtwvacgbpw47rtu#table . I expect (separate) answers from: ? Helsinki ? Las Palmas ? Lisbon ? Lleida ? Logro?o (JMP) ? Logro?o (JIG) ? Valencia (Inndea) ? Valencia (Talleria) ? Vigo During this calls, we will spend one third on FI-WARE smart cities architecture, objectives, requirements, etc., one third on your proposal and planned activities, and one third in an open discussion. I will arrange the kick-off / follow-up calls with the rest of the cities in different threads. Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica (TI+D) SmartCity Solutions / FI-WARE Parque Tecnologico de Boecillo. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 9131.29098 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-smartcities mailing list Fiware-smartcities at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-smartcities