Problem with parallel federation

[AGrzes]

I created dmgr and custom docker images. Creating and federating nodes work but when I try to federate more than one custom node at the same time then there are some conflicts - usually only one federation succeeds but often with desired name of other node. I know I can create multiple custom images with different starting names - and it should work - but it is not very scalable. Is there any way to federate nodes created from the same image in parallel?

[davidcurrie]

@AGrzes - just to be clear, does it work if you start/federate the nodes serially? It's only when you start multiple in parallel that it fails?

[AGrzes]

When I start serially it works - the problem is only with parallel start.

[mmumshad]

@AGrez were you really able to run multiple app containers serially? I thought you had to build separate images for each containers as the profile is created in the image itself. I couldn't run multiple containers and attach to the same dmgr.

[AGrzes]

It was long time ago and I do not have scripts I used to do this now but if I remember correctly I used custom image as a node template and it successfully federated serially.

If my memory serves me right the nodes registered at first with default name (the same for every node) but after they finished federation they switched to name supplied to docker run

[arthurdm]

I am closing this item as not strategic since our recommendation, if customer's can't switch to WebSphere Liberty containers, is to use traditional WAS containers in Kubernetes (instead of a dmgr / cell topology).