<div dir="ltr"><div><div><div><div><div><div><div><br></div><div>Hi to all<br><br></div>With new systems you have new problems but new possibilities, another possibility would be accountabilty, meaning a process (mianly scientific) can be run, all the logs are inside the docker instance and then commit it (freeze it) and used by another person to check the logs and/or data.<br><br></div>Disk space in docker is a funny thing, can go between 6mb to 600mb in a blink of an eye by changing OS of not cleaning packages etc etc, so lot of effort has to be done in optimizing it. Another advantage is that you can determine CPU and resources on docker therefore we have a very refined Job resrouces control<br><br></div>With the new support of Job batch we could extend things to run things in docker swarms.<br><br></div>A bit from experience.... docker systems need a a bit of "love and attention" in the beginning and then things run without problems, other issue is the extremely fast speed of docker development, you prepare things and the docker community makes some changes and everything breaks, had situation once that docker-machine internally was calling some scripts for package update and during the night someone in the docker community made a small change and for a couple of hours your couldnt run docker-machine (until we discovered it was a big problem).<br><br></div>If this project goes ahead I would ask if Geocat could sponsor it with working hours. <br><br></div>Cheers<br></div>Jorge<br><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 20, 2017 at 6:38 PM, Jachym Cepicky <span dir="ltr"><<a href="mailto:jachym.cepicky@gmail.com" target="_blank">jachym.cepicky@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I'm in touch with Adam. </div><div><br></div><div> It has big impact on the disc space, I agree - but afaik, it opens new possibilities (imagine, being able to deploy running job to e.g. open shift instaces ..) and other system resources impact should not be that big?</div><div><br></div><div>What can I say, all the points raised by Jorge are valid - so let's give it a try?<br></div><div><br></div><div>J</div></div><br><div class="gmail_quote"><div dir="ltr">st 20. 9. 2017 v 18:07 odesílatel jorge.dejesus <<a href="mailto:jorge.dejesus@geocat.net" target="_blank">jorge.dejesus@geocat.net</a>> napsal:<br></div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi to all <br>
</p>
<p>Interresting research topic, but you have a problem with that
approach: starting the process will have a massive overhead
(compared with a thread) and will consume alot of disk space and
resources !!! <br>
</p>
<p>You would have to create the docker image and process when you
install pywps , and then start the docker when the user calls the
process. I am a bit against using such a big system in PyWPS
unless someone tries to implement it and run it and show or not
that is feasable, <b>we dont know it until we try it</b><br>
</p>
<p>Those were my 2cent :)</p></div><div text="#000000" bgcolor="#FFFFFF">
<p>J.<br>
</p></div><div text="#000000" bgcolor="#FFFFFF">
<p> <br>
</p>
<br>
<div class="m_4815496067040651565m_-7941978413000694247moz-cite-prefix">On 20-09-17 15:41, Adam Laža wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Hi devs,<br>
<br>
</div>
I am student of geoinformatics at CTU in Prague. Currently
I'm looking for my ma final thesis topic. Yesterday I met
with Jachym and we discussed about containerization PyWPS
processes (probably with Docker). It could be handy for
killing/pausing a process which is as far as I know quite
crucial in WPS 2.0.<br>
<br>
</div>
I'd like to know if somebody already researched this
posibility or whether you have any suggestion or advice.<br>
<br>
</div>
Thanks in advance.<br>
</div>
Adam <br>
</div>
<br>
<fieldset class="m_4815496067040651565m_-7941978413000694247mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
pywps-dev mailing list
<a class="m_4815496067040651565m_-7941978413000694247moz-txt-link-abbreviated" href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>
<a class="m_4815496067040651565m_-7941978413000694247moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/pywps-dev</a></pre>
</blockquote>
<br>
</div>
______________________________<wbr>_________________<br>
pywps-dev mailing list<br>
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/pywps-dev</a></blockquote></div></div></div>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div>