[kolla-ansible] [kuryr] Running Docker Swarm with Kuryr networking
mdulko at redhat.com
Wed Sep 1 15:23:54 UTC 2021
On Wed, 2021-09-01 at 15:57 +0200, Michał Nasiadka wrote:
> Hi Paolo,
> Would you like to use the Docker engine that is running on the
> OpenStack cluster hosts, or create Virtual Machines that will be used
> for a Docker Swarm cluster?
> I would propose the latter.
> About Kuryr - we don’t have CI coverage for testing Kuryr in Kolla-
> Ansible deployment, so the container images and Ansible deployment
> role are provided as-is currently.
> Maybe somebody from Kuryr project could help you out? Adding [kuryr]
> tag for visibility.
I doubt anybody on the current team has any experience with running
Docker's Kuryr. We're focused on kuryr-kubernetes and Kuryr is in de-
facto unmaintained state.
> Best regards,
> On 1 Sep 2021, 00:32 +0200, Paolo Celati <paolo at celati.com>, wrote:
> > Hi,
> > long story short I have a 3 node Openstack cluster that I manage
> > with kolla-ansible, and I'd like to run Docker Swarm on that as
> > well. I am aware Magnum exists, but I'd first like to get my head
> > around this simpler case.
> > Seeing as I'd like to connect Docker containers from swarm compose
> > files to Neutron networks I'm trying to set up Kuryr together with
> > a swarm configuration. However the documentation is a little scarce
> > and I'd prefer running everything on these three hosts, including
> > etcd. If I follow the guide and pass --cluster-store and --cluster-
> > advertise arguments to dockerd then I can't run Docker in Swarm
> > mode because I get an error saying Swarm is incompatible with those
> > options, and at the same time it's not clear from documentation how
> > you are expected to do Kuryr+Swarm. I did initialise the Swarm
> > cluster before trying to add Kuryr, so I don't know if perhaps
> > doing this the other way works? Do you have ideas or advice with
> > this scenario? If worst comes to worst I can set up an external
> > etcd cluster on a separate non-Openstack cluster but I'd rather
> > avoid that.
> > Thanks in advance,
> > Paolo
More information about the openstack-discuss