The control service is the brain of Flocker; it can live anywhere in your cluster, and enabling it is an essential step in setting up your cluster.
For more information about the control service, see Flocker Cluster Architecture.
systemctl enable flocker-control systemctl start flocker-control
The control service needs to be accessible remotely.
You will need to configure FirewallD to allow access to the control service HTTP API and for agent connections.
Note that on some environments, in particular AWS, the firewalld
package is not installed and the firewall-cmd
program will not be found.
If that is the case then just skip these commands.
Otherwise run:
firewall-cmd --reload firewall-cmd --permanent --add-service flocker-control-api firewall-cmd --add-service flocker-control-api firewall-cmd --reload firewall-cmd --permanent --add-service flocker-control-agent firewall-cmd --add-service flocker-control-agent
For more details on configuring the firewall, see the FirewallD documentation.
On AWS, an external firewall is used instead, which will need to be configured similarly.
systemctl enable flocker-control systemctl start flocker-control
The control service needs to be accessible remotely.
You will need to configure FirewallD to allow access to the control service HTTP API and for agent connections.
Note that on some environments, in particular AWS, the firewalld
package is not installed and the firewall-cmd
program will not be found.
If that is the case then just skip these commands.
Otherwise run:
firewall-cmd --reload firewall-cmd --permanent --add-service flocker-control-api firewall-cmd --add-service flocker-control-api firewall-cmd --reload firewall-cmd --permanent --add-service flocker-control-agent firewall-cmd --add-service flocker-control-agent
For more details on configuring the firewall, see the FirewallD documentation.
On AWS, an external firewall is used instead, which will need to be configured similarly.
systemctl enable flocker-control systemctl start flocker-control
The control service needs to accessible remotely.
To configure UFW
to allow access to the control service HTTP API, and for agent connections:
ufw allow flocker-control-api ufw allow flocker-control-agent
For more details on configuring the firewall, see Ubuntu’s UFW documentation.
On AWS, an external firewall is used instead, which will need to be configured similarly.
cat <<EOF > /etc/init/flocker-control.override start on runlevel [2345] stop on runlevel [016] EOF echo 'flocker-control-api 4523/tcp # Flocker Control API port' >> /etc/services echo 'flocker-control-agent 4524/tcp # Flocker Control Agent port' >> /etc/services service flocker-control start
The control service needs to accessible remotely.
To configure UFW
to allow access to the control service HTTP API, and for agent connections:
ufw allow flocker-control-api ufw allow flocker-control-agent
For more details on configuring the firewall, see Ubuntu’s UFW documentation.
On AWS, an external firewall is used instead, which will need to be configured similarly.