I was thinking that I could then run each server on an independent IP address. Looking around I saw a variable when creating the instance AMP_CONTAINER_HOST_NETWORK so thought maybe there was a way to control how the container was created to some extent.
AMP isn’t multi-IP aware at this time. It’s something we want to try and do a bit later on but we have to make changes to quite a few systems for that to happen.
Yeah, thought it might not be that simple. I was thinking that if the containers werent bound to host, then I could just add them to a macvlan along with the existing network and that would be enough. But I see that with them all bound to the host, they appear as if they are just running on a single machine and hence the need for multi-IP awareness.
Anyway would be a cool feature to have! Glad that its being considered.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.