Simdoc plaftform dockerization

[ChristopheMaldivi]

To ease deployment and run, we could package simdoc servers (UI & backends) in a docker image or several docker images (compose).

[JoelGardes]

Good idea for portability. What do you means by "compose" with several docker images, I suppose that each docker image is completely independent ?

[ChristopheMaldivi]

see here

basically the idea behind this:

• we keep a docker image for an atomic part of the platform, for instance : simdoc rest server is autonomous / user interface servers will also be an autonomous part
• but to assemble these parts, docker compose will help us
• it gives us the possibility to run and update these images in an independent way
• these images are available in an internal or public docker registry and can be used by third party

Regarding this task, it could be a good entry point for @boisset :)

[JoelGardes]

I completely agree.

[ChristopheMaldivi]

Images are indeed independent. "Docker compose " tool can then be used to assemble several images to build and run a complete platform.

…

-------- Original message -------- From: Joel Gardes <notifications@github.com> Date: 14/02/2017 10:11 (GMT+01:00) To: Orange-OpenSource/documentare-simdoc <documentare-simdoc@noreply.github.com> Cc: MALDIVI Christophe IMT/OLPS <christophe.maldivi@orange.com>, Author <author@noreply.github.com> Subject: Re: [Orange-OpenSource/documentare-simdoc] Simdoc plaftform dockerization (#33) Good idea for portability. What do you means by "compose" with several docker images, I suppose that each docker image is completely independent ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#33 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHCrWWceqYfDOocEWUA-MyPoOmuCMBU-ks5rcW-ygaJpZM4MAKSx>.

_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

[ChristopheMaldivi]

TODO:

• deliver it to @JoelGardes , @boisset
• transfer the repo to OrangeOpensource@gitlab, @Christophe

Next: rebuild at each tag

[ChristopheMaldivi]

TODO:

• check that shared directory contains debug data
• add env variables for shared directory / memory settings
• build docker image for tags and publish it on gitlab.com registry