From fermin at tid.es Wed Oct 2 17:33:24 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 02 Oct 2013 17:33:24 +0200 Subject: [Fiware-demo] LiveDemo execution on Santander FI-WARE event on October 16th-18th Message-ID: <524C3CC4.7070604@tid.es> Hi, Next October 16th to 18th there is another important FI-WARE event in Santander (see details in http://fi-ware.tlmat-unican.es/index.php/en/) in which LiveDemo (the mashup part) is needed again. The critical moment will be on Wednesday 16th morning, when a workshop on FI-WARE will be carried out, including a public execution of the LiveDemo. However, the demo also has to available and ready the next days, in the case that we need to execute it again to show FI-WARE capabilities to interested people during the event. So, please ensure that the pieces under your control and responsibility in the LiveDemo (specially CEP, LOCS, Wirecloud, IDAS/IoTAgent and historymod) work right for this event to make demonstrations a success. I will probably contact directly some of you next week to ensure that all integrations points keep working. Thank you for your commitment! Best regards, ------ Ferm?n ________________________________ 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 From fermin at tid.es Tue Oct 8 18:18:26 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 08 Oct 2013 18:18:26 +0200 Subject: [Fiware-demo] Some LiveDemo VMs unexpectedly restarted and required actions Message-ID: <52543052.1050901@tid.es> Hi, Due to an issue in the FI-PPP testbed this afternoon, some VMs machines have been unexpectedly restarted. The following VMs related with LiveDemo where affected: | instance | name | hostname | host | fixed_ip | floating_ip | email | +-------------------+------------------------+----------------------------+-----------+----------------+--------------+----------------------------------------+ | instance-00000017 | fermin | contextbroker-livedemo | fiwatse02 | 130.206.82.140 | 172.30.1.15 | fermin at tid.es | | instance-00000019 | wirecloud | historymod | fiwatse02 | 130.206.82.141 | 172.30.1.8 | aarranz at fi.upm.es | | instance-00000097 | tanguy.bourgault | locationserver-testbed | fiwatse02 | 130.206.81.12 | 172.30.1.51 | tanguy.bourgault at thalesaleniaspace.com | | instance-000000de | fermin | cep | fiwatse02 | 130.206.81.31 | 172.30.1.78 | fermin at tid.es | +-------------------+------------------------+----------------------------+-----------+----------------+--------------+----------------------------------------+ This is the current situation, along with pending recovery actions: * The Context Broker and other processes running in orion.ld.testbed.fi-ware.eu have been restarted and seem to work ok. * CEP instance running in cep.ld.testbed.fi-ware.eu seems to be work ok, so I understand that the CEP processes did a proper automatic restart upon reboot. * In historymod (130.206.82.141) the process that capture information needs to be restarted. @UPM please do it asap. I restarted the event2issue process running in that VM. * LOCS instance seems to be not working. I understand that it need a restarte. @Alain: could you please check this, please? Thanks! Best regards, ------ Ferm?n ________________________________ 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 Wed Oct 16 22:27:34 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 16 Oct 2013 22:27:34 +0200 Subject: [Fiware-demo] LiveDemo execution on Santander FI-WARE event on October 16th-18th In-Reply-To: <524C3CC4.7070604@tid.es> References: <524C3CC4.7070604@tid.es> Message-ID: <525EF6B6.1090902@tid.es> Hi, LiveDemo execution today was ok. Thanks for your support! We detected some minor problems that need to be debugged. I will send an email on LiveDemo follow-up actions next week (including the actions to solve/debug the problems and some additional stuff). Sorry for not sending this email before... I has been very busy to day providing support to hackaton attendants. Best regards, ------ Ferm?n El 02/10/2013 17:33, Ferm?n Gal?n M?rquez escribi?: > Hi, > > Next October 16th to 18th there is another important FI-WARE event in > Santander (see details in http://fi-ware.tlmat-unican.es/index.php/en/) > in which LiveDemo (the mashup part) is needed again. The critical moment > will be on Wednesday 16th morning, when a workshop on FI-WARE will be > carried out, including a public execution of the LiveDemo. However, the > demo also has to available and ready the next days, in the case that we > need to execute it again to show FI-WARE capabilities to interested > people during the event. > > So, please ensure that the pieces under your control and responsibility > in the LiveDemo (specially CEP, LOCS, Wirecloud, IDAS/IoTAgent and > historymod) work right for this event to make demonstrations a success. > I will probably contact directly some of you next week to ensure that > all integrations points keep working. > > Thank you for your commitment! > > Best regards, > > ------ > Ferm?n > > > ________________________________ > > 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 > _______________________________________________ > Fiware-demo mailing list > Fiware-demo at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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 From fermin at tid.es Mon Oct 21 14:12:02 2013 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Mon, 21 Oct 2013 14:12:02 +0200 Subject: [Fiware-demo] LiveDemo next steps Message-ID: <52651A12.6050904@tid.es> Hi, After Santander LiveDemo execution and hackaton, this email summarizes several actions points related with LiveDemo to be worked out in the following weeks: 1. Debug problems in CB-CEP integration. We detected some problems regarding cases in which the notifyContextRequest message from CB is not arriving to CEP. It is particularly hard to debug due to: 1) it is not a deterministic problem (i.e. sometimes happens, sometimes doesn't happen), 2) it seems to be related with a low-level behaviour at socket level. At the present moment, it seems that the entity abruptly ending connection in the CB->CEP communication is the CB. Tali, I will try to investigate the problem and tell you about 2. LOCS stabilization. We have had several problems with the stability of the LOCS simulation tool due to a memory leak in the past weeks, but a recent update (today :) from Alain tells that the leak is now fixed. Let's have this in quarantine for a while to ensure that the behavior is right. 3. Debug problems in CB-Wirecloud integration. It seems that nofityContextRequest are not being correctly processed at Wirecloud in some occasions. The error pattern seems to be different from the problem described in 1, this time notifications gets duplicated at Wirecloud level. It could be related with the NGIS proxy library run at Wirecloud. I will contact UPM people involved in Wirecloud to debug closely this issue. Fortunately, it seems that UPM team found a Wirecloud operator that allows to easily reproduce the problem. 4. Mashup in FI-LAB. Currently, the LiveDemo runs in an dedicated Wirecloud instance (wirecloud.ld.testbed.fi-ware.eu) managed by FI-WARE staff. However, as LiveDemo is an excellent demonstrator of FI-WARE capabilities, we will also make the mashup available in the global FI-LAB wirecloud instance (mashup.lab.fi-ware.eu) so any FI-LAB user can deploy and operate the mashup (maybe not all the functionality, e.g. changing the sensor information to generate alarms could not be allowed, but a significant part of it). I will contact also UPM to carry out this objective. Best regards, ------ Ferm?n ________________________________ 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 Oct 21 14:12:13 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 21 Oct 2013 14:12:13 +0200 Subject: [Fiware-demo] Lamps and sensors pictures Message-ID: <52651A1D.8050801@tid.es> Hi, As you know, the LiveDemo applications is based on data coming from real data generated by sensors deployed in a park in Santander city. Recently, we were at Santander and take some pictures of the park, its lamps and their sensors, that you can find in the following like: https://forge.fi-ware.eu/docman/view.php/27/2936/Las+Llamas+park+2013-10-17.zip Best regards, ------ Ferm?n ________________________________ 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 From pascal.bisson at thalesgroup.com Mon Oct 21 14:30:48 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 21 Oct 2013 14:30:48 +0200 Subject: [Fiware-demo] LiveDemo next steps In-Reply-To: <52651A12.6050904@tid.es> References: <52651A12.6050904@tid.es> Message-ID: <16176_1382358656_52651E80_16176_3252_1_91f51a5b-aee9-4f61-8cc2-d6e381d76ad6@THSONEA01HUB06P.one.grp> Hi Fermin, Shall I understand there is no action point regarding IdM GE (UPM) and Access Control GE (THA) ?. Hearing from you. Regards, Pascal De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : lundi 21 octobre 2013 14:12 ? : fiware-demo at lists.fi-ware.eu Objet : [Fiware-demo] LiveDemo next steps Hi, After Santander LiveDemo execution and hackaton, this email summarizes several actions points related with LiveDemo to be worked out in the following weeks: 1. Debug problems in CB-CEP integration. We detected some problems regarding cases in which the notifyContextRequest message from CB is not arriving to CEP. It is particularly hard to debug due to: 1) it is not a deterministic problem (i.e. sometimes happens, sometimes doesn't happen), 2) it seems to be related with a low-level behaviour at socket level. At the present moment, it seems that the entity abruptly ending connection in the CB->CEP communication is the CB. Tali, I will try to investigate the problem and tell you about 2. LOCS stabilization. We have had several problems with the stability of the LOCS simulation tool due to a memory leak in the past weeks, but a recent update (today :) from Alain tells that the leak is now fixed. Let's have this in quarantine for a while to ensure that the behavior is right. 3. Debug problems in CB-Wirecloud integration. It seems that nofityContextRequest are not being correctly processed at Wirecloud in some occasions. The error pattern seems to be different from the problem described in 1, this time notifications gets duplicated at Wirecloud level. It could be related with the NGIS proxy library run at Wirecloud. I will contact UPM people involved in Wirecloud to debug closely this issue. Fortunately, it seems that UPM team found a Wirecloud operator that allows to easily reproduce the problem. 4. Mashup in FI-LAB. Currently, the LiveDemo runs in an dedicated Wirecloud instance (wirecloud.ld.testbed.fi-ware.eu) managed by FI-WARE staff. However, as LiveDemo is an excellent demonstrator of FI-WARE capabilities, we will also make the mashup available in the global FI-LAB wirecloud instance (mashup.lab.fi-ware.eu) so any FI-LAB user can deploy and operate the mashup (maybe not all the functionality, e.g. changing the sensor information to generate alarms could not be allowed, but a significant part of it). I will contact also UPM to carry out this objective. Best regards, ------ Ferm?n ________________________________ 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 Oct 21 15:33:16 2013 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Mon, 21 Oct 2013 15:33:16 +0200 Subject: [Fiware-demo] LiveDemo next steps In-Reply-To: <16176_1382358656_52651E80_16176_3252_1_91f51a5b-aee9-4f61-8cc2-d6e381d76ad6@THSONEA01HUB06P.one.grp> References: <52651A12.6050904@tid.es> <16176_1382358656_52651E80_16176_3252_1_91f51a5b-aee9-4f61-8cc2-d6e381d76ad6@THSONEA01HUB06P.one.grp> Message-ID: <52652D1C.508@tid.es> Dear Pascal, Except for the possible implications that could have point 4 on the IDM and AccessControl (unknown to me), you are right. Best regards, ------- Ferm?n El 21/10/2013 14:30, BISSON Pascal escribi?: Hi Fermin, Shall I understand there is no action point regarding IdM GE (UPM) and Access Control GE (THA) ?. Hearing from you. Regards, Pascal De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : lundi 21 octobre 2013 14:12 ? : fiware-demo at lists.fi-ware.eu Objet : [Fiware-demo] LiveDemo next steps Hi, After Santander LiveDemo execution and hackaton, this email summarizes several actions points related with LiveDemo to be worked out in the following weeks: 1. Debug problems in CB-CEP integration. We detected some problems regarding cases in which the notifyContextRequest message from CB is not arriving to CEP. It is particularly hard to debug due to: 1) it is not a deterministic problem (i.e. sometimes happens, sometimes doesn't happen), 2) it seems to be related with a low-level behaviour at socket level. At the present moment, it seems that the entity abruptly ending connection in the CB->CEP communication is the CB. Tali, I will try to investigate the problem and tell you about 2. LOCS stabilization. We have had several problems with the stability of the LOCS simulation tool due to a memory leak in the past weeks, but a recent update (today :) from Alain tells that the leak is now fixed. Let's have this in quarantine for a while to ensure that the behavior is right. 3. Debug problems in CB-Wirecloud integration. It seems that nofityContextRequest are not being correctly processed at Wirecloud in some occasions. The error pattern seems to be different from the problem described in 1, this time notifications gets duplicated at Wirecloud level. It could be related with the NGIS proxy library run at Wirecloud. I will contact UPM people involved in Wirecloud to debug closely this issue. Fortunately, it seems that UPM team found a Wirecloud operator that allows to easily reproduce the problem. 4. Mashup in FI-LAB. Currently, the LiveDemo runs in an dedicated Wirecloud instance (wirecloud.ld.testbed.fi-ware.eu) managed by FI-WARE staff. However, as LiveDemo is an excellent demonstrator of FI-WARE capabilities, we will also make the mashup available in the global FI-LAB wirecloud instance (mashup.lab.fi-ware.eu) so any FI-LAB user can deploy and operate the mashup (maybe not all the functionality, e.g. changing the sensor information to generate alarms could not be allowed, but a significant part of it). I will contact also UPM to carry out this objective. Best regards, ------ Ferm?n ________________________________ 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 pascal.bisson at thalesgroup.com Mon Oct 21 18:08:41 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 21 Oct 2013 18:08:41 +0200 Subject: [Fiware-demo] LiveDemo next steps In-Reply-To: <52652D1C.508@tid.es> References: <52651A12.6050904@tid.es> <16176_1382358656_52651E80_16176_3252_1_91f51a5b-aee9-4f61-8cc2-d6e381d76ad6@THSONEA01HUB06P.one.grp> <52652D1C.508@tid.es> Message-ID: <16176_1382371722_5265518A_16176_7844_1_c3d47e0d-2e4f-4926-8621-73059b868970@THSONEA01HUB02P.one.grp> Ok so please after your check with UPM on point 4 please come back to us on the topic. Thanks in advance Regards, Pascal De : Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Envoy? : lundi 21 octobre 2013 15:33 ? : BISSON Pascal; fiware-demo at lists.fi-ware.eu Cc : DANGERVILLE Cyril; GIDOIN Daniel Objet : Re: [Fiware-demo] LiveDemo next steps Dear Pascal, Except for the possible implications that could have point 4 on the IDM and AccessControl (unknown to me), you are right. Best regards, ------- Ferm?n El 21/10/2013 14:30, BISSON Pascal escribi?: Hi Fermin, Shall I understand there is no action point regarding IdM GE (UPM) and Access Control GE (THA) ?. Hearing from you. Regards, Pascal De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : lundi 21 octobre 2013 14:12 ? : fiware-demo at lists.fi-ware.eu Objet : [Fiware-demo] LiveDemo next steps Hi, After Santander LiveDemo execution and hackaton, this email summarizes several actions points related with LiveDemo to be worked out in the following weeks: 1. Debug problems in CB-CEP integration. We detected some problems regarding cases in which the notifyContextRequest message from CB is not arriving to CEP. It is particularly hard to debug due to: 1) it is not a deterministic problem (i.e. sometimes happens, sometimes doesn't happen), 2) it seems to be related with a low-level behaviour at socket level. At the present moment, it seems that the entity abruptly ending connection in the CB->CEP communication is the CB. Tali, I will try to investigate the problem and tell you about 2. LOCS stabilization. We have had several problems with the stability of the LOCS simulation tool due to a memory leak in the past weeks, but a recent update (today :) from Alain tells that the leak is now fixed. Let's have this in quarantine for a while to ensure that the behavior is right. 3. Debug problems in CB-Wirecloud integration. It seems that nofityContextRequest are not being correctly processed at Wirecloud in some occasions. The error pattern seems to be different from the problem described in 1, this time notifications gets duplicated at Wirecloud level. It could be related with the NGIS proxy library run at Wirecloud. I will contact UPM people involved in Wirecloud to debug closely this issue. Fortunately, it seems that UPM team found a Wirecloud operator that allows to easily reproduce the problem. 4. Mashup in FI-LAB. Currently, the LiveDemo runs in an dedicated Wirecloud instance (wirecloud.ld.testbed.fi-ware.eu) managed by FI-WARE staff. However, as LiveDemo is an excellent demonstrator of FI-WARE capabilities, we will also make the mashup available in the global FI-LAB wirecloud instance (mashup.lab.fi-ware.eu) so any FI-LAB user can deploy and operate the mashup (maybe not all the functionality, e.g. changing the sensor information to generate alarms could not be allowed, but a significant part of it). I will contact also UPM to carry out this objective. Best regards, ------ Ferm?n ________________________________ 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: