When executing plugins as a group there is a chance that certain containers cannot run the plugin because of the number of ports allocated and the actual number needed for the plugin.
Solution
Every plugin will have some sort of table listing the number of ports needed to execute a certain task. We will also introduce
a new mode called auto. To check the number of auto-generated ports available against the number of ports the plugin requires to be executed. For a certain container if the plugin requires more ports to be allocated. Then we kill the container and restart a new with the right number of ports required to be allocated.
Note: The following implies to TCP ports and UDP ports are supported.
Problem
When executing plugins as a group there is a chance that certain containers cannot run the plugin because of the number of ports allocated and the actual number needed for the plugin.
Solution
Every plugin will have some sort of table listing the number of ports needed to execute a certain task. We will also introduce a new mode called
auto
. To check the number of auto-generated ports available against the number of ports the plugin requires to be executed. For a certain container if the plugin requires more ports to be allocated. Then we kill the container and restart a new with the right number of ports required to be allocated.Note: The following implies to TCP ports and UDP ports are supported.