[Fiware-espoo] FW: Espo connection to FI-Lab

[Fermín Galán Márquez]

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<mailto: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> [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<mailto: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> [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<mailto: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> [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<mailto: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> [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<mailto: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: <https://lists.fiware.org/private/fiware-espoo/attachments/20140421/e6e193d2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cecediif.png
Type: image/png
Size: 2698 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-espoo/attachments/20140421/e6e193d2/attachment.png>