<div dir="ltr"><div class="gmail_default" style="font-size:small">I do think that we should consider to move to discourse. <br></div><div class="gmail_default" style="font-size:small">One thing that I've learned with the agile method is to discover the 'pain' of my user and try to cure it. <br></div><div class="gmail_default" style="font-size:small">What i see from this thread is the 'pain' of maintaining this kind of infrastructure, that I think that using</div><div class="gmail_default" style="font-size:small">tools of automations like Ansible or Kubernetes for the orquestration and management of containers would</div><div class="gmail_default" style="font-size:small">aliviate that kind of pain. <br></div><div class="gmail_default" style="font-size:small">But I could be wrong, since I don't know any idea of the work that the kde sysadmins have.</div><div class="gmail_default" style="font-size:small">I love automation and how that makes my life easier at work. <br></div><div class="gmail_default" style="font-size:small">I agree over Paul Adams comments, and I think that if we want to go forward on this, we need to study it,</div><div class="gmail_default" style="font-size:small">find the poins of 'pain' and come up with solutions that can be good for everyone.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">For me, all the movements that want to bring KDE to a modern web are valid... to be studied and maybe implemented.<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Oct 30, 2018 at 7:50 AM Paul Adams <<a href="mailto:paul.adams@kde.org">paul.adams@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 30 Oct 2018 at 11:42, Ben Cooksley <<a href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>> wrote:<br>
> If you're running 10,000+ microservice instances, then you can have<br>
> the teams of people needed to maintain the necessary overhead<br>
<br>
This is true. Also not your original point: you claimed that Docker<br>
containers were generally unsuitable for production<br>
The overhead is generally not that huge: you build, sign and upload<br>
your images to registry you run. This is no different than when you<br>
build, sign and upload your custom-built distro packages.<br>
<br>
Yes, running something like Openstack cause some additional overhead.<br>
<br>
> We delegate management of sites to people who look after them (where<br>
> it makes sense) as it helps people get things done.<br>
> They are essentially the "admin" of that specific site/service, but<br>
> won't have root on the actual server that runs it.<br>
<br>
Good approach. It is by no means incompatible with running services in<br>
a container.<br>
You can give specific system users membership of a docker group,<br>
allowing them to start/stop/deploy etc. You then control which<br>
containers the user is actually allowed to manipulate in registry<br>
config.<br>
<br>
Perhaps I am missing something?<br>
<br>
-- <br>
Paul J. Adams<br>
PhD MIEEE MBCS CITP<br>
<br>
GPG: 07DD 0812 Paul James Adams<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b><font color="#000000"><span style="font-size:12.8px">Lays Rodrigues</span><br></font></b></div><div><b><font color="#000000">KDE<br></font></b></div><div><b><font color="#000000">Atelier - <a href="http://atelier.kde.org" target="_blank">atelier.kde.org</a><br></font></b></div><div><b><font color="#000000">Fundraising WG<br></font></b></div><div><b><font color="#000000"><a href="http://lays.space" target="_blank">http://lays.space</a></font></b></div><div><font style="background-color:rgb(255,255,255)" color="#000000"><b>Telegram: @lays147</b></font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></span></div></div>