Re: FSF leadership
On Thu, 19 Sep 2019, 08:17 AgustÃn Benito, wrote: > we should support them, not tell them what to do. > One of RMSs best-known transgressions took place on _our_ stage at Gran Canaria. We did not exactly take much action at the time. If this community really cares about Free Software and building an inclusive community we absolutely _must_ speak up in public. Augustin is right though. That message must be one of support for the FSF and helping them build a better future for FS, not pressurising them over things in the past. >
Re: Discourse
On Tue, 30 Oct 2018 at 11:42, Ben Cooksley wrote: > If you're running 10,000+ microservice instances, then you can have > the teams of people needed to maintain the necessary overhead This is true. Also not your original point: you claimed that Docker containers were generally unsuitable for production The overhead is generally not that huge: you build, sign and upload your images to registry you run. This is no different than when you build, sign and upload your custom-built distro packages. Yes, running something like Openstack cause some additional overhead. > We delegate management of sites to people who look after them (where > it makes sense) as it helps people get things done. > They are essentially the "admin" of that specific site/service, but > won't have root on the actual server that runs it. Good approach. It is by no means incompatible with running services in a container. You can give specific system users membership of a docker group, allowing them to start/stop/deploy etc. You then control which containers the user is actually allowed to manipulate in registry config. Perhaps I am missing something? -- Paul J. Adams PhD MIEEE MBCS CITP GPG: 07DD 0812 Paul James Adams
Re: Discourse
On Tue, 30 Oct 2018 at 07:28, Ben Cooksley wrote: > Sorry, Docker might be a wonderful way to test applications, but it's > totally unsuitable for production workloads. That's a bold claim. At Zalando we have 10,000s of microservices in production and each one of them is running inside a Docker container. this has been our deployment vector for years We are far from alone in this. > First, the contents of that Docker image can be confirmed how exactly? You build the image yourself, sign it and upload to your own private registry. > Second, it's impossible for Sysadmin to delegate management of a > Docker container to anyone. There are third party tools to support this and Docker itself supports delegation of signing and deployment. Each team at Zalando has full autonomy to start/stop/update/deploy and reassign their running services (and therefore the container). This is handled by an open source tech we have released called STUPS: https://stups.io/ Sadly, this is AWS-centric, but I am sure there are other solutions that solve the same problem. Openstack? > This means if anything goes wrong with it a Sysadmin would have to be > the one to take a look Genuine comment: Unless you are doing devops, when *anything* goes wrong I would expect the sysadmin to be the first to react. If you /are/ doing devops, then of course it is the deploying team who reacts. -- Paul J. Adams PhD MIEEE MBCS CITP GPG: 07DD 0812 Paul James Adams
Re: [kde-community] Your KDE highlight of 2014?
On 19 December 2014 at 11:08, Lydia Pintscher ly...@kde.org wrote: 2014 is coming to an end. This gives us some time for reflection. What are your KDE highlights of 2014? Adriaan de Groot came to Akademy. -- Paul J. Adams PhD MIEEE MBCS CITP ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Berlin - Brno road trip
On 10 June 2014 20:28, m...@milianw.de wrote: those of you who plan to go to ackademy this year and wants to go by train from berlin, please raise your hand. There is apparently at least 4 of us who also need to attend the general assembly. What about sharing the trip? Count me in. -- Paul J. Adams PhD MIEEE MBCS CITP ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
