If I add another host to a specified EC will running containers that were constrained by CPU or memory be immediately unrestricted?
No, running containers will be gradually unrestricted depending on the workload of the hosts on which each of these containers are running.
What container strategy is used to determine placement of a new container?
Container currently deploys containers using the docker swarm spread strategy.
If I add another host will newly started containers all deploy to the new host until all hosts are balanced?
Yes, after a new host is started it will be the preferred host for newly launched containers based on Docker swarm's spread strategy.
Can I self balance a Container Pool by stopping and removing containers and then starting them anew?
Yes, As stated above new containers will be placed on hosts based on Docker swarm spread strategy.
Where does the consul service run?
It runs on the cxMgmt host.
Do ECs and CPs continue to operate if the cxMgmt server goes offline or losses communication?
The GUI will unavailable and so will creation (and deletion) of Elastic Clusters and Container Pools. The Container Pools will continue to operate.
What type of communications occur between a cxMgmt server and cxHost? Is runtime data (#containers, CPU %, Memory %) pushed to cxMgmt or does cxMgmt request to each host?
Data is sent bidirectionally.
Are all "docker" and "docker-compose" runtime and configuration references able to run without modification against a Container Pool?
Does a Container Pool act and run like the swarm version referenced from the "docker version" command? Is any modification does to the swarm or docker engine code?