Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Grouper and Docker Swarm

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Grouper and Docker Swarm

Chronological Thread 
  • From: Greg Haverkamp <>
  • To:
  • Cc: Grouper-Users <>
  • Subject: Re: [grouper-users] Grouper and Docker Swarm
  • Date: Mon, 30 Jul 2018 15:26:07 -0500
  • Ironport-phdr: 9a23:WPvU7xQSPJja4H+OzRKVrdcc29psv+yvbD5Q0YIujvd0So/mwa69ZxCN2/xhgRfzUJnB7Loc0qyK6/6mATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfbJ/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4KlxSB/slSwJKTg3/m/KgcB0la5WoRetqhpiyIDWfY6VLuJzcazTfdwYRWRPUMVfWTFfDIygdIYAFfYNMPxCooXhu1cDrx2zDhSsCuP1zT9Ig2f706wg0+s/HgHNwQ4uEMgQsHvKttX1N70dUeWtzKLVyjjDYOlZ2Tfn54jWbB8hu/KMUqh1ccrJ0kQvExjKjlGKpYzqODOVyP0Avm6G5ORjTeKik3Mrpx9yrzS1yMogkIbEip8Pxl3F9ih12Jg5KcG8RUJhYtOpEIFcuz+HO4Z1WM8vQXxktSAnwbMco5G7ZjIFyJE/yh7fdfOHd4+I7wrtVOmPLzp0nnZld6m7hxqo/kigzfP8WtG10FZMsCVFjsHBum0T2xHQ8MSKROFx80i81TqV1g3e6flIIUUumqraL54hzKQwlp0WsUnbES/5gkX2g7WIdko64Oio6P7oYrD+ppKHM497kQX+Pr4hmsy4H+Q0KhIOUHSD+eSgyL3j+lX0QLpQjv0xj6nZqI7VJd4Cqq6kGA9azJwj6w2kAjei0dQYhmUHLElbdB6djojpPU3OL+7iDfe5nVusjClny+rYMbL8H5WeZkTExbjsYapw8GZBxg51wNxCtLxODbRUD+j+VQfRvcLVFBwwNhT8l+nuCNxj25kdUGeXKquTNOXdtkHetbFnGPWFeIJA4GW1EPMi/fO7yCE0

On Mon, Jul 30, 2018 at 10:46 AM Gettes, Michael <> wrote:
Looking for anyone with practical experience running Grouper in a Docker Swarm (or even Kubernetes - I am starting with swarm).

I'm a little hesitant to claim "practical experience".  I deployed our Swarm-based Grouper at the end of June, after a moderately lengthy dev and testing process.  It's also our initial Grouper deployment, so it's tiny, and it doesn't as yet have a lot of work to do.
Does it “just work”? 

The beauty of Swarm to me is that it feels like just a lightweight extension of Docker functionality.  We're using a (heavily?) layered version of the TIER images.  Most of my learning curve revolved around getting used to not having bind mounts, as that's how we've typically handled logs and credentials.  I was working on externalizing secrets across all of our applications at the same time, and so I integrated all of that work.  (We've moved almost all of our IdM applications to individual Docker containers since we launched IdPv3 in December 2015.  But we haven't really done any orchestration at any level.)

Getting to gsh is a little weird under Swarm, if you're using Docker Secrets, and I feel like I need to break it into its own standalone, non-Swarmed container.  (We only use Docker Secrets to bootstrap, and we fetch all of the other secrets from our external secrets store.)  But a non-Swarm container would either need to be tweaked to pull the bootstrapped secrets from somewhere other than Docker Secrets.

(Our installation is small enough that, if I need to run gsh, I go to the Swarm node hosting the container and exec... Which feels awfully dirty, and certainly won't scale to large Swarm clusters.)

And we still don't have a good answer for Swarm logging, and "docker service logs" has proven to be a mess, so I've had to do a lot of debugging using "docker logs" on the actual host/container.
Any sage advice?

Not so much advice as... Something else.




Archive powered by MHonArc 2.6.19.

Top of Page