[Fiware-i2nd] Final minutes of I2ND meeting

[Angel Hernandez]

Hello Pier,
I am attaching the configuration we were planning. Given that we only have three days, this is the safest way to go.
Let me just answer on your own email.
Talk to you soon,
Ángel

De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it]
Enviado el: martes, 27 de enero de 2015 15:49
Para: Angel Hernandez
CC: fiware-i2nd at lists.fi-ware.org<mailto:fiware-i2nd at lists.fi-ware.org>
Asunto: R: Final minutes of I2ND meeting

Hello Angel,

I was working on some information provided to me by Davide while I received your mail: I try to put together the whole things to see how it could work.

First of all, Manuel just confirmed that the demo sessions will be on Monday 2nd, therefore if we want to propose the robotics demo we need to have it running by the end of this week; on the other hand, this is too the preferred date for you, so it's fine.
[Ángel]  Sounds good :)

Concerning the minutes, the meaning of the sentence you mention (TI to provide a machine where everything has to run) was meant to define an environment where the ROS based components and RCM should run, independent of being a VM or an actual laptop. The RCM provisioning action was not planned at this time, as it was not necessary to run the demo according to what we defined, i.e. all ROS based nodes and RCM put together to get rid of the split over different machines for ROS based nodes.
 [Ángel]  I might have understood something wrong then. In the end, the START button on the web will send a command to the RCM and this will bring up all the required nodes to run the Turtlesim and FIROS. If TI does not provide any basic RCM at all, how are we supposed to do that part of the demo? We can definately do that by ourselves, but I guess that's not what we are persuing here, right?

I enclose in the mail a drawing of what are the elements of the demo, which shows the ideal set up we can provide. There are a few points we need to address and/or detail/confirm, in order to make it working as expected, that are:

-          We assume that the Web App is developed by ET and accesses the RCM through interface 1 of the slide. A Control GUI can be shown by a browser on e.g. a demo laptop (e.g. at ET side)
[Ángel]  Yeahp, we will develop the web with the three buttons at least, but TI should send us an alpha version of the RCM as we have done with FIROS, so we can test it and adapt the connection if required.



-          We assume that the web app connects to RCM: we provide two RCM Management API exposed as public URLs, to be used through HTTP-GET requests. These two API will perform START/STOP RCM operations and they will reply with an XML response.
[Ángel]  Great, this is where the fun begins :). As said before, we would appreciate if you guys share the code aswell, as we've done with FIROS. This will make the development much faster on our side.



-          We assume that FIROS, which is running as a ROS node inside the ROS container on the TI's (virtual) machine, connects to the Context Broker (interface 2), by subscribing to events triggered by the 'Forward' command of the Web App.
[Ángel]  As we said in our last meeting, taking into account that we will be providing FIROS, the website, and the desktop sharing already configured for the simulation, the fact that we know we do not have any firewall issues here, and RCM still not being able to bring up distributed nodes, It will be safer to run ROS on a VM in ET. In fact, we already have all the demo infrastructure in our office and we would just need to integrate the RCM, which wouldn't be a big problem even with the 3 days left we have.



·         Question 1: at the meeting you mentioned that the connection between FIROS and the Context Broker uses HTTP: is a specific used port when FIROS works as Client Server (i.e. after the subscription towards Context Broker)? If yes, which is this port?
[Ángel] The Context Broker port is the one used by default on the FIWARE documentation: 1026
                               The FIROS port where subscriptions are received is 10100, but it is something anyone can change (line 31 of the core.py we sent)



·         Question 2: is there anything else necessary to configure FIROS (we rembember that at the meeting you/Inigo mentioned some configuration file which doesn't seem to be present in the package just delivered)?
[Ángel] In order to make it easier for you, we've put the required configuration variables on the same core.py file, in fact, the variables that we use as "configuration" are the following:
                               ROBOT1_NAME = "turtle1"
ROBOT1_TOPIC = "cmd_vel"
ROBOT1_TOPIC_CLASS = geometry_msgs.msg.Twist
ROBOT1_TOPIC_PUB = None
ROBOT1_TOPIC_SUB = None
ROBOT1_DISCONNECTED = False
If you think it might be better to have it on a different config file, just let us know and we will modify it.


-          The Turtlesim GUI (and rqt_graph) can run on any laptop/machine, provided that it is able to connect to the TI's machine via connection 3 (it can be done by using VNC).
[Ángel]  Actually, the plan, as I said before, was to help you here by providing the whole desktop setup for the demo. So we just need a way to share the desktop (remember that it will be a linux machine) with whoever is on the demo call... maybe a Skype would be enough, but if you have a better software, we will be happy to try out.

Under these assumptions, the only drawback I see is that we need to show two GUIS on different machines, which might require two desktop sharing facilities during the demo (but we can provide them, hopefully), unless we find a way to share on the same desktop both the control GUI and the Turtlesim GUI.
[Ángel]  It will be possible, and will look better if we can show all the required components on a single interface. If you let us do it, we will take care of that.

On the other hand the advantage I see is that we already show that there can be a 'platform' running the robotics GE, while the web application can be elsewhere.
[Ángel]  Please, take into account that we might run into cross-origin issues. This is something we are taking care of already in our development, and must be taken care of by the RCM. Otherwise, most explorers will forbid the connection unless it is launched with the specific security rule disabled. If you decide to have the RCM on a TI VM, you will have to make sure you add the proper headers. Please let us know if you need any help with that.

Does it sound fine to you?

BR
Pier



Da: Angel Hernandez [mailto:ahernandez at ikergune.com]
Inviato: martedì 27 gennaio 2015 11:38
A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.org<mailto:fiware-i2nd at lists.fi-ware.org>
Oggetto: RE: Final minutes of I2ND meeting

Good morning Pier,
Just a couple details I found on the minutes:

-          "TI to provide a machine where everything has to run": As we agreed there, in order to avoid any problems and make configuration and last minute fixes possible, it will be better if we have all the software running on the same physical place, so TI would just have to provide the RCM and we will run everything on a VM containing all the code in our office. In this case, If anything fails, we will be able to fix it faster since there would be the web, Roscore and FIROS from our side.

Iñigo will send you all the required code so you can test the RCM before handing it to us. He will also send you an schema including all the connections required to deliver the demo (VM, remote desktop, Web, etc)

-          I haven't seen any action point related to providing the RCM. This will be required to run the demo. When can you provide this code? Let us know if we can help you.

-          Action point 2 says "Provide the environment where everything required for sprint demo has to run". I guess we are talking about the webex or any other platform to share the screen. Please take into account that the simulator (which we can take care of) runs on linux, so the desktop to be shared will be a linux machine. We have other ways to do it already, but it might be easier if the system provided to share the screen can work on Linux.

We will discuss this on Thursday.

-          If possible, it would be easier for us to have the demo next Monday, Feb 2nd. We could do it on the 9th, but it might be a little more difficult to have all the team together on that day.

Thank you!


De: fiware-i2nd-bounces at lists.fi-ware.org<mailto:fiware-i2nd-bounces at lists.fi-ware.org> [mailto:fiware-i2nd-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo
Enviado el: viernes, 23 de enero de 2015 16:01
Para: fiware-i2nd at lists.fi-ware.org<mailto:fiware-i2nd at lists.fi-ware.org>
Asunto: [Fiware-i2nd] Final minutes of I2ND meeting

Dear All,

I have 'refined' a bit the minutes we took at the meeting yesterday, by grouping the actions defined in a final table, and assigning to them 'reasonable' deadlines.
Please have a look and take note of the actions you're responsible for: https://docs.google.com/document/d/1DC91JT8Qx5yQFzGOwQlqut6nTj9GYmjWNZy_l2uWJHY/edit#<https://docs.google.com/document/d/1DC91JT8Qx5yQFzGOwQlqut6nTj9GYmjWNZy_l2uWJHY/edit>

Have a nice week-end!
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.
[cid:image001.gif at 01D03AF0.0EFA2160]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-i2nd/attachments/20150128/0fb56ff3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/fiware-i2nd/attachments/20150128/0fb56ff3/attachment.gif>
-------------- 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: <https://lists.fiware.org/private/fiware-i2nd/attachments/20150128/0fb56ff3/attachment.pptx>