R: [Fiware-robotics] R: Dockerization

[fabio.dibenedetto at consoft.it]

Thank you,
to make it easy this kind of non standard version I thought to write a readme.md into the distribution folder, so that the question asked by Gianmario would be available to anyone access that folder.
The question is: how can we manage the change of fiware standard? Can we put in jira that we did so and it's ok or do we have to do something else?
Fabio

PS: about the question of robotics_msgs use in firos: do we have any news?

-----Messaggio originale-----
Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza
Inviato: giovedì 24 settembre 2015 17:12
A: fiware-robotics at lists.fi-ware.org
Oggetto: Re: [Fiware-robotics] R: Dockerization

Hi,

the solution Fabio proposes for the dockerizing the GE sounds great to me.

I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly.

Thank you very much,

Pepe

José Jaime Ariza
R&D Engineer
+34 696604288
Ikergune, Etxe-Tar group

On 24/09/15 16:26, Bollano Gianmario wrote:
> Hi Fabio,
> my answers:
>
> 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders?
> 2) Fine. Any editing to improve/fix is absolutely welcomed.
> 3) OpenSpecs R4 are : 
> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE
> .OpenSPecification.I2ND.Robotics_R4
>
> Best,
> Gianmario
>
> -----Messaggio originale-----
> Da: fiware-robotics-bounces at lists.fiware.org 
> [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di 
> fabio.dibenedetto at consoft.it
> Inviato: giovedì 24 settembre 2015 15:14
> A: fiware-robotics at lists.fi-ware.org
> Oggetto: [Fiware-robotics] Dockerization
>
> Hi all,
> I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide.
> In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you?
>
>
> For what concern the documentation I updated the file modified by Pepe 
> because there were some lost letters in some words and a wrong rst 
> format in a little section. I added a webhook to our repository in 
> order to have readthedocs automatically updated when you do some 
> changes (I still haven't tried if it works, but I'll do when I'll 
> commit the 'dist' folder)
>
> Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it?
>
> Fabio
> _______________________________________________
> Fiware-robotics mailing list
> Fiware-robotics at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-robotics-new
>
> 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.fiware.org
> https://lists.fiware.org/listinfo/fiware-robotics-new
>

_______________________________________________
Fiware-robotics mailing list
Fiware-robotics at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-robotics-new