From roberto1.antonini at telecomitalia.it Thu Jan 8 10:03:04 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 8 Jan 2015 09:03:04 +0000 Subject: [Fiware-robotics] R: Robotics White paper In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCD0F3C@TELMBB001BA020.telecomitalia.local> Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Thu Jan 8 10:10:05 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 8 Jan 2015 10:10:05 +0100 Subject: [Fiware-robotics] Robotics White paper Message-ID: Happy new year Roberto! Since we didn't say anything about it, I assumed we didn't gonna have that call. We are all just back from Christmas break, so the i2nd call at 14:30 should be better, right? I'm on the road now, so if you still want to talk I can join via phone somehow. Sent from: Lenovo K910 Antonini Roberto wrote: Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don?t contribute (yet) to current release of technical white paper, so I didn?t create issues in JIRA concerning this task. Later we?ll start working on the finalization of our internal document, which we?ll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I?ve just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D02B2A.4AE421B0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Thu Jan 8 10:19:35 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 8 Jan 2015 09:19:35 +0000 Subject: [Fiware-robotics] R: Robotics White paper In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCD0F84@TELMBB001BA020.telecomitalia.local> Hi Angel, Ok, it's fine for me postponing the robotics call the next week. For i2nd call, if Pier agrees, we can postpone it to 14:30. Thanks, R Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 8 gennaio 2015 10:10 A: Antonini Roberto; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: Re: Robotics White paper Happy new year Roberto! Since we didn't say anything about it, I assumed we didn't gonna have that call. We are all just back from Christmas break, so the i2nd call at 14:30 should be better, right? I'm on the road now, so if you still want to talk I can join via phone somehow. Sent from: Lenovo K910 Antonini Roberto > wrote: Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Thu Jan 8 10:42:41 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 8 Jan 2015 09:42:41 +0000 Subject: [Fiware-robotics] R: Robotics White paper In-Reply-To: <246C286B275B1B46A255552CD236DA863BCD0F84@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCD0F84@TELMBB001BA020.telecomitalia.local> Message-ID: Hi All, I'm afraid I cannot postpone the I2ND call, too late to change and the time slot (well, this is the usual time slot...) was also agreed with Manuel Escriche, who needs to join for the Sprint planning. Hence the I2ND call is confirmed at 11:00. Angel please let me know if this creates troubles to you and/or other guys at ET to attend: in such a case we'd plan an extra call this afternoon at 14:30 for you only. BR Pier Da: Antonini Roberto Inviato: gioved? 8 gennaio 2015 10:20 A: Angel Hernandez; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: R: Robotics White paper Hi Angel, Ok, it's fine for me postponing the robotics call the next week. For i2nd call, if Pier agrees, we can postpone it to 14:30. Thanks, R Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 8 gennaio 2015 10:10 A: Antonini Roberto; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: Re: Robotics White paper Happy new year Roberto! Since we didn't say anything about it, I assumed we didn't gonna have that call. We are all just back from Christmas break, so the i2nd call at 14:30 should be better, right? I'm on the road now, so if you still want to talk I can join via phone somehow. Sent from: Lenovo K910 Antonini Roberto > wrote: Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Thu Jan 8 10:59:15 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 8 Jan 2015 10:59:15 +0100 Subject: [Fiware-robotics] Robotics White paper Message-ID: Hi! I didn't mean to postpone the i2nd call, I just assumed the meeting time in the minutes was right. It says 14:30 I will join in few minutes then Sent from: Lenovo K910 Garino Pierangelo wrote: Hi All, I?m afraid I cannot postpone the I2ND call, too late to change and the time slot (well, this is the usual time slot?) was also agreed with Manuel Escriche, who needs to join for the Sprint planning. Hence the I2ND call is confirmed at 11:00. Angel please let me know if this creates troubles to you and/or other guys at ET to attend: in such a case we?d plan an extra call this afternoon at 14:30 for you only. BR Pier Da: Antonini Roberto Inviato: gioved? 8 gennaio 2015 10:20 A: Angel Hernandez; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: R: Robotics White paper Hi Angel, Ok, it?s fine for me postponing the robotics call the next week. For i2nd call, if Pier agrees, we can postpone it to 14:30. Thanks, R Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 8 gennaio 2015 10:10 A: Antonini Roberto; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: Re: Robotics White paper Happy new year Roberto! Since we didn't say anything about it, I assumed we didn't gonna have that call. We are all just back from Christmas break, so the i2nd call at 14:30 should be better, right? I'm on the road now, so if you still want to talk I can join via phone somehow. Sent from: Lenovo K910 Antonini Roberto > wrote: Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don?t contribute (yet) to current release of technical white paper, so I didn?t create issues in JIRA concerning this task. Later we?ll start working on the finalization of our internal document, which we?ll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I?ve just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D02B2F.D28233F0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fabio.dibenedetto at consoft.it Thu Jan 8 11:01:45 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 8 Jan 2015 10:01:45 +0000 Subject: [Fiware-robotics] R: Robotics White paper In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCD0F84@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, happy new year. Sorry to interrupt the thread but I didn't receive any mail from the group fiware-robotics so maybe I'm not in the mailing list for now; how can I do to subscribe it and avoid that every time I miss some mails or I have to be added to receive them? Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: gioved? 8 gennaio 2015 10:43 A: Antonini Roberto; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: R: Robotics White paper Hi All, I'm afraid I cannot postpone the I2ND call, too late to change and the time slot (well, this is the usual time slot...) was also agreed with Manuel Escriche, who needs to join for the Sprint planning. Hence the I2ND call is confirmed at 11:00. Angel please let me know if this creates troubles to you and/or other guys at ET to attend: in such a case we'd plan an extra call this afternoon at 14:30 for you only. BR Pier Da: Antonini Roberto Inviato: gioved? 8 gennaio 2015 10:20 A: Angel Hernandez; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: R: Robotics White paper Hi Angel, Ok, it's fine for me postponing the robotics call the next week. For i2nd call, if Pier agrees, we can postpone it to 14:30. Thanks, R Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 8 gennaio 2015 10:10 A: Antonini Roberto; Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; fabio.dibenedetto at consoft.it Oggetto: Re: Robotics White paper Happy new year Roberto! Since we didn't say anything about it, I assumed we didn't gonna have that call. We are all just back from Christmas break, so the i2nd call at 14:30 should be better, right? I'm on the road now, so if you still want to talk I can join via phone somehow. Sent from: Lenovo K910 Antonini Roberto > wrote: Hi all, Good Year to anyone!!! Is there anybody for scheduled PhC at 10:00 (now), today? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 16:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics White paper Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Thu Jan 15 10:10:58 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 15 Jan 2015 09:10:58 +0000 Subject: [Fiware-robotics] R: FIROS-RCM Specs In-Reply-To: <246C286B275B1B46A255552CD236DA863BCCA05B@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCCA05B@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCD378F@TELMBB001BA020.telecomitalia.local> Hi guys, we are in the middle of the sprint and it?s time to define a demo for the sprint and to start describing the GE arch and spec in WIKI page. Given the big amount of work we need to consume during this period, we would ask to mainly interact via-email, when needed we can hear on-the-fly. For what concerns the demo of this first sprint, the RCM part will be ready for start/stop services (i.e. ROS nodes) by exposing (temporary) management API. The demo logical architecture could be a virtual or real machine which is connected to a robot (or gateway if the robot is not of advanced type). From our point of view, FIROS can be started wherever you want. For what concerns the spec and arch of Robotics GE, I would propose to start working on the figure, reporting what we lately shared, in the attached PPT ? The first one is a logical architectural view, showing interaction between the main components of the GE. ? The second one is physical architectural view, showing the component disposal among robot/gateway and virtual machine. ? The third one describe the distribution of RCM as a whole among robot/gateway and virtual machine. Let us know, how we can proceed to finalize both works BR Davide and Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: luned? 15 dicembre 2014 14:14 A: Fernando Herranz; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi Fernando, In attached a new version of PDF, in which we try to collect all the proposals we made about FIROS and RCM interaction. A couple of question about FIROS: 1. For "to implement service in FIROS" you mean ROS services, don?t you? 2. Have you considered scalability issues for FIROS node? What do you mean when you say " ... FIROS instance to control a cloud of robots"? The Container concept try to meet the non-functional requirement named ?scalability?, by modularizing robot and above all making them stateful (SOA paradigm) . e.g. A robot could be placed on whatever virtual machine (IaaS), basing on maybe cloud metrics. You, at the very beginning, only considered FIROS on each robot (If I remember well), for this, we placed FIROS on each robot whether this was real and virtual (cloned), anyway as we said at the end of the document ?It?s not mandatory having a ROS container for each robot?. BR Roberto -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: venerd? 12 dicembre 2014 12:51 A: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: RE: FIROS-RCM Specs Hi all, sorry for the delay but we are inthe middle of a demo. We agree with the way you plan to send the topics list to FIROS but we (Etxe-Tar) should study how to implement services in FIROS. We also have a doubt, your approach has a FIROS instance per ROS container, right? here is the question: could your architecture support a FIROS instance for all the ROS container? we are developing FIROS to attend all the robots in the cloud. We also think that would help FIWARE application developers because that way they only have to talk to a FIROS instance to control a cloud of robots. Cheers! ________________________________________ De: Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: viernes, 12 de diciembre de 2014 9:12 Para: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide Asunto: R: FIROS-RCM Specs Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. ? Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs Hi everyone, as we said yesterday here you have the documentation of FIROS specs to communicate with RCM. We think there is a misunderstanding about what we consider interface between FIROS and RCM. Just for the sake of clarification, when we talk about FIROS and RCM interfaces, we talk about the information that they need to share to collaborate, not just about the connectivity proccess. We know that FIROS and RCM are ROS nodes and they communicate using ROS. However, we not only need the definition of the communication channel. The data that RCM must provide to do a correct integration between FIROS and RCM is: * The name of the robots * Topics that RCM will provide * The message type of each topic * If we must subscribe to the topic or publish on it So we need to know how RCM provides this data. Attached is a document with the FIROS specifications. Regards Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SchemaFIROS_RCM.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 59302 bytes Desc: SchemaFIROS_RCM.pptx URL: From pierangelo.garino at telecomitalia.it Thu Jan 15 11:26:48 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 15 Jan 2015 10:26:48 +0000 Subject: [Fiware-robotics] Test mail - Ignore it Message-ID: Sorry for spamming. Pier -------------------------------------------------------------- Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Mon Jan 19 16:56:40 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 19 Jan 2015 16:56:40 +0100 Subject: [Fiware-robotics] R: FIROS-RCM Specs References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCCA05B@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCD378F@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, Sorry for the delay. Since we are going to meet in Torino in two days, we think it would be better to talk about the demos during the meeting. BR, Pepe On 15/01/15 10:11, Antonini Roberto wrote: Hi guys, we are in the middle of the sprint and it?s time to define a demo for the sprint and to start describing the GE arch and spec in WIKI page. Given the big amount of work we need to consume during this period, we would ask to mainly interact via-email, when needed we can hear on-the-fly. For what concerns the demo of this first sprint, the RCM part will be ready for start/stop services (i.e. ROS nodes) by exposing (temporary) management API. The demo logical architecture could be a virtual or real machine which is connected to a robot (or gateway if the robot is not of advanced type). From our point of view, FIROS can be started wherever you want. For what concerns the spec and arch of Robotics GE, I would propose to start working on the figure, reporting what we lately shared, in the attached PPT ? The first one is a logical architectural view, showing interaction between the main components of the GE. ? The second one is physical architectural view, showing the component disposal among robot/gateway and virtual machine. ? The third one describe the distribution of RCM as a whole among robot/gateway and virtual machine. Let us know, how we can proceed to finalize both works BR Davide and Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: luned? 15 dicembre 2014 14:14 A: Fernando Herranz; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi Fernando, In attached a new version of PDF, in which we try to collect all the proposals we made about FIROS and RCM interaction. A couple of question about FIROS: 1. For "to implement service in FIROS" you mean ROS services, don?t you? 2. Have you considered scalability issues for FIROS node? What do you mean when you say " ... FIROS instance to control a cloud of robots"? The Container concept try to meet the non-functional requirement named ?scalability?, by modularizing robot and above all making them stateful (SOA paradigm) . e.g. A robot could be placed on whatever virtual machine (IaaS), basing on maybe cloud metrics. You, at the very beginning, only considered FIROS on each robot (If I remember well), for this, we placed FIROS on each robot whether this was real and virtual (cloned), anyway as we said at the end of the document ?It?s not mandatory having a ROS container for each robot?. BR Roberto -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: venerd? 12 dicembre 2014 12:51 A: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: RE: FIROS-RCM Specs Hi all, sorry for the delay but we are inthe middle of a demo. We agree with the way you plan to send the topics list to FIROS but we (Etxe-Tar) should study how to implement services in FIROS. We also have a doubt, your approach has a FIROS instance per ROS container, right? here is the question: could your architecture support a FIROS instance for all the ROS container? we are developing FIROS to attend all the robots in the cloud. We also think that would help FIWARE application developers because that way they only have to talk to a FIROS instance to control a cloud of robots. Cheers! ________________________________________ De: Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: viernes, 12 de diciembre de 2014 9:12 Para: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide Asunto: R: FIROS-RCM Specs Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. ? Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs Hi everyone, as we said yesterday here you have the documentation of FIROS specs to communicate with RCM. We think there is a misunderstanding about what we consider interface between FIROS and RCM. Just for the sake of clarification, when we talk about FIROS and RCM interfaces, we talk about the information that they need to share to collaborate, not just about the connectivity proccess. We know that FIROS and RCM are ROS nodes and they communicate using ROS. However, we not only need the definition of the communication channel. The data that RCM must provide to do a correct integration between FIROS and RCM is: * The name of the robots * Topics that RCM will provide * The message type of each topic * If we must subscribe to the topic or publish on it So we need to know how RCM provides this data. Attached is a document with the FIROS specifications. Regards Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From igonzalez at ikergune.com Tue Jan 27 12:54:46 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Tue, 27 Jan 2015 12:54:46 +0100 Subject: [Fiware-robotics] Firos code Message-ID: Hi Roberto, as it was said in the meeting, here you have a firos copy. The installation is like any ROS package, using catkin_make and source devel/setup.bash. Before running it is necessary to have installed the turtlesim code because it uses some of its libraries. I send it to the list if someone else wants to try it. Regards, I?igo -------------- next part -------------- A non-text attachment was scrubbed... Name: firos.zip Type: application/zip Size: 51265 bytes Desc: firos.zip URL: From igonzalez at ikergune.com Tue Jan 27 16:25:25 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Tue, 27 Jan 2015 16:25:25 +0100 Subject: [Fiware-robotics] Firos diagram Message-ID: Hello, here you have the new firos diagram that is related to the minutes' actionpoint 6. If you think that some changes are necessary please tell me. Regards, I?igo -------------- next part -------------- A non-text attachment was scrubbed... Name: firos-arquitecture.jpg Type: image/jpeg Size: 129316 bytes Desc: firos-arquitecture.jpg URL: From igonzalez at ikergune.com Thu Jan 29 09:54:28 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 29 Jan 2015 09:54:28 +0100 Subject: [Fiware-robotics] Demo web page + RCM demo Message-ID: Hello Davide et al, Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. Please let us know when this is fixed so we can give it another try. Regards, I?igo From ahernandez at ikergune.com Thu Jan 29 09:56:13 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 29 Jan 2015 09:56:13 +0100 Subject: [Fiware-robotics] Demo web page + RCM demo In-Reply-To: References: Message-ID: Also, we should have a call ASAP in order to organize it and make sure everything works as expected. What about 3pm today? -----Mensaje original----- De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de I?igo Gonzalez Enviado el: jueves, 29 de enero de 2015 9:54 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] Demo web page + RCM demo Hello Davide et al, Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. Please let us know when this is fixed so we can give it another try. Regards, I?igo _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From davide.colombatto at telecomitalia.it Thu Jan 29 10:30:04 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 29 Jan 2015 09:30:04 +0000 Subject: [Fiware-robotics] Demo web page + RCM demo In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Hi Inigo and all, I re-attach the document sent by Angel yesterday. If the arch in the document is used there would be no cross-domain problems for connection 4: the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. Use case: - Browser contacts your web-app for the page with the 3 buttons - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. - When your web-app obtains the XML response by RCM, the web-app responses to the browser I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). Davide ________________________________________ Da: I?igo Gonzalez [igonzalez at ikergune.com] Inviato: gioved? 29 gennaio 2015 9.54 A: fiware-robotics at lists.fi-ware.org Cc: Colombatto Davide Oggetto: Demo web page + RCM demo Hello Davide et al, Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. Please let us know when this is fixed so we can give it another try. Regards, I?igo Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: Demo_FIROS_RCM_arch_2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 82434 bytes Desc: Demo_FIROS_RCM_arch_2.pptx URL: From igonzalez at ikergune.com Thu Jan 29 11:28:43 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 29 Jan 2015 11:28:43 +0100 Subject: [Fiware-robotics] Demo web page + RCM demo References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, the web app is just a web page that is hosted in our fiware machine. What it does is to send ajax calls to the different REST services: - Context broker - RCM So to do this functionality we need support for cross origin request, in our case as we need something to reach the context broker we have created our context broker proxy, which supports cross origin and redirects the requests to the context broker. In your case, your service should provide support for cross origin so the web app could reach to it. To achieve this, what is needed is just to add support in your server to the OPTIONS request and both OPTIONS and GET methods return the following headers in the response: header("Access-Control-Allow-Headers", "api-version, content-length, content-md5, content-type, date, request-id, response-time") header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") header("Access-Control-Expose-Headers", "api-version, content-length, content-md5, content-type, date, request-id, response-time") header("Access-Control-Allow-Origin", "*") Regards, I?igo On 29/01/15 10:30, Colombatto Davide wrote: > Hi Inigo and all, > > I re-attach the document sent by Angel yesterday. > > If the arch in the document is used there would be no cross-domain problems for connection 4: > the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. > > > Use case: > - Browser contacts your web-app for the page with the 3 buttons > - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. > - When your web-app obtains the XML response by RCM, the web-app responses to the browser > > I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). > > > Davide > > > ________________________________________ > Da: I?igo Gonzalez [igonzalez at ikergune.com] > Inviato: gioved? 29 gennaio 2015 9.54 > A: fiware-robotics at lists.fi-ware.org > Cc: Colombatto Davide > Oggetto: Demo web page + RCM demo > > Hello Davide et al, > > Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. > I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: > > "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." > > This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. > > Please let us know when this is fixed so we can give it another try. > > Regards, > I?igo > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. > > This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. > From jjaime at ikergune.com Thu Jan 29 14:43:37 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 29 Jan 2015 14:43:37 +0100 Subject: [Fiware-robotics] Demo web page + RCM demo References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, Could we have the 3pm meeting via hangout? we should also talk about webex. BR, Pepe On 29/01/15 11:29, I?igo Gonzalez wrote: > Hi, > > the web app is just a web page that is hosted in our fiware machine. > What it does is to send ajax calls to the different REST services: > > - Context broker > - RCM > > So to do this functionality we need support for cross origin request, in > our case as we need something to reach the context broker we have > created our context broker proxy, which supports cross origin and > redirects the requests to the context broker. > > In your case, your service should provide support for cross origin so > the web app could reach to it. To achieve this, what is needed is just > to add support in your server to the OPTIONS request and both OPTIONS > and GET methods return the following headers in the response: > > header("Access-Control-Allow-Headers", "api-version, content-length, > content-md5, content-type, date, request-id, response-time") > header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") > header("Access-Control-Expose-Headers", "api-version, content-length, > content-md5, content-type, date, request-id, response-time") > header("Access-Control-Allow-Origin", "*") > > Regards, > I?igo > > > On 29/01/15 10:30, Colombatto Davide wrote: >> Hi Inigo and all, >> >> I re-attach the document sent by Angel yesterday. >> >> If the arch in the document is used there would be no cross-domain problems for connection 4: >> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >> >> >> Use case: >> - Browser contacts your web-app for the page with the 3 buttons >> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >> - When your web-app obtains the XML response by RCM, the web-app responses to the browser >> >> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >> >> >> Davide >> >> >> ________________________________________ >> Da: I?igo Gonzalez [igonzalez at ikergune.com] >> Inviato: gioved? 29 gennaio 2015 9.54 >> A: fiware-robotics at lists.fi-ware.org >> Cc: Colombatto Davide >> Oggetto: Demo web page + RCM demo >> >> Hello Davide et al, >> >> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >> >> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >> >> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >> >> Please let us know when this is fixed so we can give it another try. >> >> Regards, >> I?igo >> >> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >> >> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From pierangelo.garino at telecomitalia.it Thu Jan 29 15:14:45 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 29 Jan 2015 14:14:45 +0000 Subject: [Fiware-robotics] R: Demo web page + RCM demo In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Message-ID: Hi Jose, I suggest we move to hangouts to set up things. Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 29 gennaio 2015 14:44 A: I?igo Gonzalez; Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo Hi, Could we have the 3pm meeting via hangout? we should also talk about webex. BR, Pepe On 29/01/15 11:29, I?igo Gonzalez wrote: > Hi, > > the web app is just a web page that is hosted in our fiware machine. > What it does is to send ajax calls to the different REST services: > > - Context broker > - RCM > > So to do this functionality we need support for cross origin request, > in our case as we need something to reach the context broker we have > created our context broker proxy, which supports cross origin and > redirects the requests to the context broker. > > In your case, your service should provide support for cross origin so > the web app could reach to it. To achieve this, what is needed is just > to add support in your server to the OPTIONS request and both OPTIONS > and GET methods return the following headers in the response: > > header("Access-Control-Allow-Headers", "api-version, content-length, > content-md5, content-type, date, request-id, response-time") > header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") > header("Access-Control-Expose-Headers", "api-version, content-length, > content-md5, content-type, date, request-id, response-time") > header("Access-Control-Allow-Origin", "*") > > Regards, > I?igo > > > On 29/01/15 10:30, Colombatto Davide wrote: >> Hi Inigo and all, >> >> I re-attach the document sent by Angel yesterday. >> >> If the arch in the document is used there would be no cross-domain problems for connection 4: >> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >> >> >> Use case: >> - Browser contacts your web-app for the page with the 3 buttons >> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >> - When your web-app obtains the XML response by RCM, the web-app >> responses to the browser >> >> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >> >> >> Davide >> >> >> ________________________________________ >> Da: I?igo Gonzalez [igonzalez at ikergune.com] >> Inviato: gioved? 29 gennaio 2015 9.54 >> A: fiware-robotics at lists.fi-ware.org >> Cc: Colombatto Davide >> Oggetto: Demo web page + RCM demo >> >> Hello Davide et al, >> >> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >> >> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >> >> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >> >> Please let us know when this is fixed so we can give it another try. >> >> Regards, >> I?igo >> >> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >> >> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From igonzalez at ikergune.com Fri Jan 30 09:03:49 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Fri, 30 Jan 2015 09:03:49 +0100 Subject: [Fiware-robotics] R: Demo web page + RCM demo References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Message-ID: Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is just >> to add support in your server to the OPTIONS request and both OPTIONS >> and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > From davide.colombatto at telecomitalia.it Fri Jan 30 09:35:10 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 30 Jan 2015 08:35:10 +0000 Subject: [Fiware-robotics] R: Demo web page + RCM demo In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> , Message-ID: <069906BED271EB4A883BD9578DCDD3540230D8@TELMBB006RM001.telecomitalia.local> Hi inigo, For me it's ok at 10.00. See you later. Davide ________________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di I?igo Gonzalez [igonzalez at ikergune.com] Inviato: venerd? 30 gennaio 2015 9.03 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is just >> to add support in your server to the OPTIONS request and both OPTIONS >> and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From pierangelo.garino at telecomitalia.it Fri Jan 30 09:59:54 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 30 Jan 2015 08:59:54 +0000 Subject: [Fiware-robotics] R: R: Demo web page + RCM demo In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540229AD@TELMBB006RM001.telecomitalia.local> Message-ID: Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From ahernandez at ikergune.com Fri Jan 30 10:01:25 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 30 Jan 2015 10:01:25 +0100 Subject: [Fiware-robotics] R: R: Demo web page + RCM demo Message-ID: <67jbbeqxe0irpgg8g7xokili.1422608484345@email.android.com> Me neither. But you dont need us :) Let us know how it goes Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:30/01/2015 10:00 AM (GMT+01:00) Para: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: Demo web page + RCM demo Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From igonzalez at ikergune.com Fri Jan 30 10:57:53 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Fri, 30 Jan 2015 10:57:53 +0100 Subject: [Fiware-robotics] R: R: Demo web page + RCM demo References: <67jbbeqxe0irpgg8g7xokili.1422608484345@email.android.com> Message-ID: Hi, Davide and me have done the test for monday's demo, here you have the results: * The web page for the demo is hosted in http://130.206.127.115/demo1/ * In the first test, turtlesim started but firos didn't. We have been checking, and the last time firos seems not to be closed correctly, Davide has check if RCM sends the correct signal to firos (SIGINT or SIGTERM) and it seems that is ok, it sends SIGINT. Davide has closed it manually. * After that, we have send to RCM start signal, moved the turtlesim and send stop signal to RCM for 3-4 times and it has worked perfectly every time, so we think that the environment is ready for the demo. For the demo we think that the computer that contains the turtlesim (the one that yesterday I access via VNC) should be started from scratch, to avoid the possibility of having firos port busy again. For next releases we are going to take in mind what has happened today to try to solve it. Regards, I?igo On 30/01/15 10:01, Angel Hernandez wrote: Me neither. But you dont need us :) Let us know how it goes Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:30/01/2015 10:00 AM (GMT+01:00) Para: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: Demo web page + RCM demo Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Fri Jan 30 11:00:48 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 30 Jan 2015 11:00:48 +0100 Subject: [Fiware-robotics] R: R: Demo web page + RCM demo Message-ID: Good job guys! Thank you for the update. Enviado de Samsung Mobile -------- Mensaje original -------- De: I?igo Gonzalez Fecha:30/01/2015 10:58 AM (GMT+01:00) Para: Cc: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] R: R: Demo web page + RCM demo Hi, Davide and me have done the test for monday's demo, here you have the results: * The web page for the demo is hosted in http://130.206.127.115/demo1/ * In the first test, turtlesim started but firos didn't. We have been checking, and the last time firos seems not to be closed correctly, Davide has check if RCM sends the correct signal to firos (SIGINT or SIGTERM) and it seems that is ok, it sends SIGINT. Davide has closed it manually. * After that, we have send to RCM start signal, moved the turtlesim and send stop signal to RCM for 3-4 times and it has worked perfectly every time, so we think that the environment is ready for the demo. For the demo we think that the computer that contains the turtlesim (the one that yesterday I access via VNC) should be started from scratch, to avoid the possibility of having firos port busy again. For next releases we are going to take in mind what has happened today to try to solve it. Regards, I?igo On 30/01/15 10:01, Angel Hernandez wrote: Me neither. But you dont need us :) Let us know how it goes Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:30/01/2015 10:00 AM (GMT+01:00) Para: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: Demo web page + RCM demo Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Jan 30 11:09:10 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 30 Jan 2015 10:09:10 +0000 Subject: [Fiware-robotics] R: R: R: Demo web page + RCM demo In-Reply-To: References: Message-ID: Pretty good indeed, thanks to all! I'm going to provide in the chapter coords' shared doc the inputs for the connection to the demo, let's hope nobody objects for using hangouts... Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 30 gennaio 2015 11:01 A: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Demo web page + RCM demo Good job guys! Thank you for the update. Enviado de Samsung Mobile -------- Mensaje original -------- De: I?igo Gonzalez Fecha:30/01/2015 10:58 AM (GMT+01:00) Para: Cc: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] R: R: Demo web page + RCM demo Hi, Davide and me have done the test for monday's demo, here you have the results: * The web page for the demo is hosted in http://130.206.127.115/demo1/ * In the first test, turtlesim started but firos didn't. We have been checking, and the last time firos seems not to be closed correctly, Davide has check if RCM sends the correct signal to firos (SIGINT or SIGTERM) and it seems that is ok, it sends SIGINT. Davide has closed it manually. * After that, we have send to RCM start signal, moved the turtlesim and send stop signal to RCM for 3-4 times and it has worked perfectly every time, so we think that the environment is ready for the demo. For the demo we think that the computer that contains the turtlesim (the one that yesterday I access via VNC) should be started from scratch, to avoid the possibility of having firos port busy again. For next releases we are going to take in mind what has happened today to try to solve it. Regards, I?igo On 30/01/15 10:01, Angel Hernandez wrote: Me neither. But you dont need us :) Let us know how it goes Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:30/01/2015 10:00 AM (GMT+01:00) Para: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: Demo web page + RCM demo Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Fri Jan 30 17:53:51 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 30 Jan 2015 16:53:51 +0000 Subject: [Fiware-robotics] Robotics Architecture Message-ID: <069906BED271EB4A883BD9578DCDD3540233D3@TELMBB006RM001.telecomitalia.local> Hi all, I have updated the Architect section in the private wiki page (https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.ROBOTICS). This diagram could be used for the slide 3 of the Robotics demo on monday. Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From davide.colombatto at telecomitalia.it Fri Jan 30 17:56:40 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 30 Jan 2015 16:56:40 +0000 Subject: [Fiware-robotics] R: R: Demo web page + RCM demo In-Reply-To: References: <67jbbeqxe0irpgg8g7xokili.1422608484345@email.android.com>, Message-ID: <069906BED271EB4A883BD9578DCDD354023405@TELMBB006RM001.telecomitalia.local> Hi All, Just a couple of points to integrate I?igo info of this morning: 1. After this morning test, I have done a sort of "brute force attack" on RCM trying to do START/STOP a lot of times. It seems it works great but I agree we should investigate. 2. As we have seen yesterday and this morning we noticed that there is a sort of delay between FORWARD pressing and the turtle movement. I have tried to understand this strange behaviour today (using your web-app) and it seems that it is a constant event, maybe cause by the CB. I try to explain: it seems that CB publishes to FIROS the entity updates only about each 5secs: if you press FORWARD every 5secs the turtle gets moved instantly.. if you press twice (three times and so on...) the first move happens instantly whereas the other ones every 5secs. (ET guys) Have you ever noticed this behaviour before? Maybe it is caused by the Development Version of the CB we are using... I inform you only to take this fact in consideration for the demo on monday. Good weekend, Davide ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di I?igo Gonzalez [igonzalez at ikergune.com] Inviato: venerd? 30 gennaio 2015 10.57 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Demo web page + RCM demo Hi, Davide and me have done the test for monday's demo, here you have the results: * The web page for the demo is hosted in http://130.206.127.115/demo1/ * In the first test, turtlesim started but firos didn't. We have been checking, and the last time firos seems not to be closed correctly, Davide has check if RCM sends the correct signal to firos (SIGINT or SIGTERM) and it seems that is ok, it sends SIGINT. Davide has closed it manually. * After that, we have send to RCM start signal, moved the turtlesim and send stop signal to RCM for 3-4 times and it has worked perfectly every time, so we think that the environment is ready for the demo. For the demo we think that the computer that contains the turtlesim (the one that yesterday I access via VNC) should be started from scratch, to avoid the possibility of having firos port busy again. For next releases we are going to take in mind what has happened today to try to solve it. Regards, I?igo On 30/01/15 10:01, Angel Hernandez wrote: Me neither. But you dont need us :) Let us know how it goes Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:30/01/2015 10:00 AM (GMT+01:00) Para: I?igo Gonzalez Cc: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: Demo web page + RCM demo Hi All, I'm pretty sure you don't need me to be present for the tests, but just to let you know I'm not available this morning. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: venerd? 30 gennaio 2015 09:04 Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo web page + RCM demo Hi Davide, as Angel said, we have thought about a fast workaround without any visual feedback for the user. We have already added it to the page, so if you want we can have a hangout at 10:00 or 10:30 (if you prefer another our tell me please), to test everything. Is it all right for you? Regards, I?igo On 29/01/15 15:14, Garino Pierangelo wrote: > Hi Jose, > > I suggest we move to hangouts to set up things. > > Pier > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 29 gennaio 2015 14:44 > A: I?igo Gonzalez; Colombatto Davide > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Demo web page + RCM demo > > Hi, > > Could we have the 3pm meeting via hangout? we should also talk about webex. > > BR, > Pepe > > On 29/01/15 11:29, I?igo Gonzalez wrote: >> Hi, >> >> the web app is just a web page that is hosted in our fiware machine. >> What it does is to send ajax calls to the different REST services: >> >> - Context broker >> - RCM >> >> So to do this functionality we need support for cross origin request, >> in our case as we need something to reach the context broker we have >> created our context broker proxy, which supports cross origin and >> redirects the requests to the context broker. >> >> In your case, your service should provide support for cross origin so >> the web app could reach to it. To achieve this, what is needed is >> just to add support in your server to the OPTIONS request and both >> OPTIONS and GET methods return the following headers in the response: >> >> header("Access-Control-Allow-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Methods", "GET,POST,PUT,DELETE") >> header("Access-Control-Expose-Headers", "api-version, content-length, >> content-md5, content-type, date, request-id, response-time") >> header("Access-Control-Allow-Origin", "*") >> >> Regards, >> I?igo >> >> >> On 29/01/15 10:30, Colombatto Davide wrote: >>> Hi Inigo and all, >>> >>> I re-attach the document sent by Angel yesterday. >>> >>> If the arch in the document is used there would be no cross-domain problems for connection 4: >>> the web-app should work as "intermediate" between the browser and the RCM and NOT the browser contacts directly the RCM with Javascript/AJAX. >>> >>> >>> Use case: >>> - Browser contacts your web-app for the page with the 3 buttons >>> - When the user click on START and STOP, the browser contacts (with Javascript/AJAX) your web-app and the web-app performs this contacting RCM itself. >>> - When your web-app obtains the XML response by RCM, the web-app >>> responses to the browser >>> >>> I think this use case does not create cross domain on your side (no cross-domain Server2Server connection). >>> >>> >>> Davide >>> >>> >>> ________________________________________ >>> Da: I?igo Gonzalez [igonzalez at ikergune.com] >>> Inviato: gioved? 29 gennaio 2015 9.54 >>> A: fiware-robotics at lists.fi-ware.org >>> Cc: Colombatto Davide >>> Oggetto: Demo web page + RCM demo >>> >>> Hello Davide et al, >>> >>> Please note that I am moving this conversation to the robotics list so we do not overload everyone's inbox. >>> I have just added to the demo webpage the urls sent by Daide. I have tried to launch the start command and found this issue: >>> >>> "XMLHttpRequest cannot load http://188.15.109.226:8088/platform/?command=SL&sc_host=localhost&sc_port=11312&package=turtlesim&name=monosim&_=1422520888499. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." >>> >>> This issue is related to what Angel said in his mail yesterday. When calling to a REST service from a web page the cross origin security policy appears. So your api must add support to cross origin to allow the web page to connect to it. >>> >>> Please let us know when this is fixed so we can give it another try. >>> >>> Regards, >>> I?igo >>> >>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >>> >>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: