Hi, Here is some first input from FIC2 on Docker compiled from Mario. As I mentioned before, we have a full system working that deploys entire sets of GEs/SEs using this mechanism on FIWARE (and AWS) VMs. FIC2 would be happy to work with FIWARE to integrate them in whatever way we at FIWARE decide to implement Docker. Right now we deploy it on top of the VMs offered by FIWARE but a more native implementation would be fine as well and save much resources (which seems to be a major issue). A presentation by Canonical recently showed a >10x improvement in resource usage with their containers over plain OpenStack (which is probably where we are -- but then Intel claims even better numbers in their Clear Containers solution using traditional VMs). Since we have experience already, it seems very useful to make Docker available especially since deployment of SW is much easier too and the same SW can be deployed essentially anywhere (including a local machine). Best, Philipp > There are several ways in which FIWARE could support Docker. My assumption is that the plan is to add to OpenStack a Docker driver. It would enable the creation of instances which are not VMs but OpenStack containers, from images which are not ISOs but Docker images. It’s described here: https://wiki.openstack.org/wiki/Docker > > > > Advantages: > > + Launches faster than VM instances > > + Less resources used from quotas in FIWARE nodes > > + images of SEs smaller and easier to build (using Dockerfiles) > > > > Open questions / disadvantages: > > - Will it be possible to pull images from DockerHub (preferred approach), or do they need to be uploaded to the Glance image repository of each FIWARE node? > > - Is the only way to launch containers the Cloud Portal or OpenStack API? Not being able to target a Docker API would reduce the value of Docker and its ecosystem of tools, e.g.: docker-compose which enables launching applications composed of multiple containers. > > - How to solve the limits in terms of IPs? Maybe with a DNS-based reverse proxy that forwards HTTP requests to container1.john-smith.cloud.fiware.org to the right container port? > > - How would links between containers running on different hosts work? Using Weave? > > - Mounting volumes in Docker is a very common way of passing configuration files, having persistence, etc. How would this work in OpenStack? > > > > Our suggestion: > > * Ability to use the Docker API remotely (i.e. command-line tools such as docker and docker-compose, Kitematic for a Mac OS X GUI) > > * Ability to pull containers directly from DockerHub with a common (transparent?) image mirror in each FIWARE node > > > > > > > > Regarding FIC2Lab runner, our wishlist was: > > 1. ability to use the same tools locally and remotely in any cloud (ideally use docker-machine against any cloud provider, in particular FIWARE nodes) > > 2. nice web user interface hiding the complexity of firewalling, security pairs, public IPs, etc. > > 3. compatibility with the tools of the docker ecosystem: docker CLI, compose, swarm ... > > > > We compared tools such as tutum (free multi-tenant online service), shipyard (open-source web UI) and panamax (open-source web UI and orchestrator). > > And we decided to go for Panamax, which is nice for #1 and #2 but not #3 so far. Here's a few pluses and minuses: > > + nice UI with DockerHub search > > + composite application, with application template search > > - It's not multi-tenant, which is good for portability but bad for software updates > > - its model for composite applications is different from docker-compose (for now) > > - the UI can't synchronize with actions performed in Docker CLI or API because it's using CoreOS underneath > > > > The FIC2Lab runner is documented here: http://fic2.github.io/runner > > Am 20.05.2015 um 17:48 schrieb Juanjo Hierro: > Dear Alex, > > It's fine with me. > > I believe that we should collocate here the discussion with > FI-Content2 (Philipp) regarding the stuff they have developed for the > FIC2-Lab. > > @Philipp: could you share some material (document describing your work > on FIC2-Lab, slides, whatever) describing what you have done and send it > to the fiware-chapter-architects mailing list as preparation for the > discussion? > > @Alex: please also share the ideas you want to present on this matter. > > By exchanging material prior to the meeting, we would be able to have > a more fruitful meeting. > > Best regards, > > -- Juanjo > > On 18/05/15 11:07, Alex Glikson wrote: >> I am out of office on the 25th. Would the following Monday work? >> >> Thanks, >> Alex >> >> >> >> >> >> >> From: Juanjo Hierro <juanjose.hierro at telefonica.com> >> To: Philipp Slusallek <philipp.slusallek at dfki.de>, Alex >> Glikson/Haifa/IBM at IBMIL, <fiware-chapter-architects at lists.fi-ware.org> >> Cc: Ezra Silvera/Haifa/IBM at IBMIL, Kenneth Nagin/Haifa/IBM at IBMIL >> Date: 18/05/2015 11:53 AM >> Subject: Re: [Fiware-chapter-architects] Linux Containers & Docker >> ------------------------------------------------------------------------ >> >> >> >> >> I would suggest that we book the next architecture session (Monday >> 25th) to cover this matter. >> >> Will you Alex be able to prepare a presentation? >> >> Cheers, >> >> -- Juanjo >> >> On 18/05/15 09:46, Philipp Slusallek wrote: >> > Hi, >> > >> > This sounds very useful to cover as well in this or one of the next >> > calls. It would also get the architectural activities started again. It >> > might even make sense to invite (selected?) AB members from the UCs. >> > >> > For example, a lot of work that has been done within FIcontent to deploy >> > our SEs and related GEs within Docker on top of FIWARE Lab. Particularly >> > relevant could be the on-click deployment of entire arrangements of GEs >> > and SEs. Better and more dedicated Docker support would certainly be >> > very welcome as well. >> > >> > Unfortunately, I have a lecture this morning and cannot join until 12h. >> > But Stefan Lemme from my group will be on the call. He has been a core >> > member of the relevant FIC2-Lab task force in FIcontent. >> > >> > >> > Best, >> > >> > Philipp >> > >> > Am 18.05.2015 um 09:28 schrieb Alex Glikson: >> >> Maybe we can also dedicate some time to have an initial discussion on >> >> the roadmap to adopt Linux Containers and in particular Docker in >> FIWARE >> >> Lab. >> >> >> >> Regards, >> >> Alex >> >> >> >> >> ==================================================================================== >> >> Alex Glikson >> >> Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab >> >> Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: >> >> +972-54-6466667 | Fax: +972-4-8296112 >> >> >> >> >> >> ----- Forwarded by Alex Glikson/Haifa/IBM on 18/05/2015 10:25 AM ----- >> >> >> >> From: Juanjo Hierro <juanjose.hierro at telefonica.com> >> >> To: Torsten Spieldenner <torsten.spieldenner at dfki.de>, >> >> <fiware-pois at lists.fi-ware.org> >> >> Cc: "fiware-chapter-architects at lists.fi-ware.org" >> >> <fiware-chapter-architects at lists.fi-ware.org> >> >> Date: 13/05/2015 09:58 AM >> >> Subject: Re: [Fiware-chapter-architects] [Fiware-pois] >> Discussion >> >> on new POI format >> >> Sent by: fiware-chapter-architects-bounces at lists.fi-ware.org >> >> >> ------------------------------------------------------------------------ >> >> >> >> >> >> >> >> Dear all, >> >> >> >> As you know, I consider this is a rather hot and crucial topic, >> highly >> >> relevant when trying to promote FIWARE as a holistic platform where >> >> pieces from all the chapters can be all nicely integrated. >> >> >> >> I wanted to devote an architects session on this matter as already >> >> shared with many of you. >> >> >> >> This would take place this coming Monday May 18th from 11 to 12:30. >> >> >> >> Please be prepared for the discussion. >> >> >> >> Thanks in advance, >> >> >> >> -- Juanjo >> >> >> >> On 04/05/15 08:50, Torsten Spieldenner wrote: >> >> Good morning, >> >> >> >> the goal of this POI group is to find an advanced concept of Points of >> >> Interest, that supports integration with other GE, as for example >> >> Context Broker, and also support Dynamic POIs. >> >> >> >> As a starting point for the discussion, we would like to present the >> >> proposals for the new POI concepts which were created within the WebUI >> >> chapter by CIE and DFKI. >> >> >> >> for this, please find attached the proposals by CIE: >> >> _ >> >> __http://dev.cie.fi/FI-WARE/poi_dp_dyn/poi_dp_dyn_spec.docx_ >> >> >> >> and DFKI respectively: >> >> _ >> >> >> __https://docs.google.com/document/d/1BKAiUNPo_3kScyQxOpETet6G2i4H0wuUYl49zJC6xvQ/edit#heading=h.n739jm7ey76a_ >> >> >> >> Best Regards, >> >> Torsten >> >> >> >> -- >> >> Torsten Spieldenner, M.Sc. >> >> >> >> Tel.: +49 6 81 / 8 57 75 - 77 48 >> >> Fax.: +49 6 81 / 8 57 75 - 22 35 >> >> >> >> Internet: _http://www.dfki.de/web/forschung/asr/_ >> >> >> >> ------------------------------------------------------------- >> >> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH >> >> Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany >> >> >> >> Geschaeftsfuehrung: >> >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> >> Dr. Walter Olthoff >> >> >> >> Vorsitzender des Aufsichtsrats: >> >> Prof. Dr. h.c. Hans A. Aukes >> >> >> >> Amtsgericht Kaiserslautern, HRB 2313 >> >> ------------------------------------------------------------- >> >> >> >> >> >> _______________________________________________ >> >> Fiware-pois mailing list >> >> _Fiware-pois at lists.fi-ware.org_ <mailto:Fiware-pois at lists.fi-ware.org> >> >> _https://lists.fi-ware.org/listinfo/fiware-pois_ >> >> >> >> >> >> -- >> >> >> >> ______________________________________________________ >> >> >> >> Coordinator and Chief Architect, FIWARE platform >> >> CTO Industrial IoT, Telefónica >> >> >> >> email: _juanjose.hierro at telefonica.com_ >> >> <mailto:juanjose.hierro at telefonica.com> >> >> twitter: @JuanjoHierro >> >> >> >> You can follow FIWARE at: >> >> website: _http://www.fiware.org_ <http://www.fiware.org/> >> >> twitter: @FIWARE >> >> facebook: _http://www.facebook.com/pages/FI-WARE/251366491587242_ >> >> linkedIn: _http://www.linkedin.com/groups/FIWARE-4239932_ >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> >> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su >> destinatario, >> >> puede contener información privilegiada o confidencial y es para uso >> >> exclusivo de la persona o entidad de destino. Si no es usted. el >> >> destinatario indicado, queda notificado de que la lectura, utilización, >> >> divulgación y/o copia sin autorización puede estar prohibida en virtud >> >> de la legislación vigente. Si ha recibido este mensaje por error, le >> >> rogamos que nos lo comunique inmediatamente por esta misma vía y >> proceda >> >> a su destrucción. >> >> >> >> The information contained in this transmission is privileged and >> >> confidential information intended only for the use of the individual or >> >> entity named above. If the reader of this message is not the intended >> >> recipient, you are hereby notified that any dissemination, distribution >> >> or copying of this communication is strictly prohibited. If you have >> >> received this transmission in error, do not read it. Please immediately >> >> reply to the sender that you have received this communication in error >> >> and then delete it. >> >> >> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >> >> destinatário, pode conter informação privilegiada ou confidencial e é >> >> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >> >> senhoria o destinatário indicado, fica notificado de que a leitura, >> >> utilização, divulgação e/ou cópia sem autorização pode estar >> proibida em >> >> virtude da legislação vigente. Se recebeu esta mensagem por erro, >> >> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >> >> proceda a sua destruição_______________________________________________ >> >> Fiware-chapter-architects mailing list >> >> Fiware-chapter-architects at lists.fi-ware.org >> >> https://lists.fi-ware.org/listinfo/fiware-chapter-architects >> >> >> >> >> >> _______________________________________________ >> >> Fiware-chapter-architects mailing list >> >> Fiware-chapter-architects at lists.fi-ware.org >> >> https://lists.fi-ware.org/listinfo/fiware-chapter-architects >> >> >> >> -- >> >> ______________________________________________________ >> >> Coordinator and Chief Architect, FIWARE platform >> CTO Industrial IoT, Telefónica >> >> email: juanjose.hierro at telefonica.com >> twitter: @JuanjoHierro >> >> You can follow FIWARE at: >> website: http://www.fiware.org <http://www.fiware.org/> >> twitter: @FIWARE >> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >> >> >> ________________________________ >> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su >> destinatario, puede contener información privilegiada o confidencial y >> es para uso exclusivo de la persona o entidad de destino. Si no es >> usted. el destinatario indicado, queda notificado de que la lectura, >> utilización, divulgación y/o copia sin autorización puede estar >> prohibida en virtud de la legislación vigente. Si ha recibido este >> mensaje por error, le rogamos que nos lo comunique inmediatamente por >> esta misma vía y proceda a su destrucción. >> >> The information contained in this transmission is privileged and >> confidential information intended only for the use of the individual >> or entity named above. If the reader of this message is not the >> intended recipient, you are hereby notified that any dissemination, >> distribution or copying of this communication is strictly prohibited. >> If you have received this transmission in error, do not read it. >> Please immediately reply to the sender that you have received this >> communication in error and then delete it. >> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >> destinatário, pode conter informação privilegiada ou confidencial e é >> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >> senhoria o destinatário indicado, fica notificado de que a leitura, >> utilização, divulgação e/ou cópia sem autorização pode estar proibida >> em virtude da legislação vigente. Se recebeu esta mensagem por erro, >> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >> proceda a sua destruição >> >> > > -- > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: juanjose.hierro at telefonica.com > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > twitter: @FIWARE > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ------------------------------------------------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud > de la legislación vigente. Si ha recibido este mensaje por error, le > rogamos que nos lo comunique inmediatamente por esta misma vía y proceda > a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution > or copying of this communication is strictly prohibited. If you have > received this transmission in error, do not read it. Please immediately > reply to the sender that you have received this communication in error > and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida em > virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150526/55402d6e/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy