The iptables rules are trivial to add. The ip_forward thing is a bit trickier, because I don't want to leave a mess on people's systems. If you snap install lxd, then do lxd init, then snap remove lxd, you'll have that rule set for you, however, so microstack wouldn't be unique in setting the rule.
I'm a little tempted to add a "microstack.configure" command. Or "microstack init". That would give the user a bit more warning that they might be writing some configuration to their system outside the snap. And it would get around our timeout issues w/ mysql. Hmmm ...
We have a fix for this! Big hat tip to admcleod and james-page for figuring this out.
On the host system, you need to setup some iptables rules, and run a sysctl command:
sudo iptables -t nat -A POSTROUTING -s 10.20.20.1/24 ! -d 10.20.20.1/24 -j MASQUERADE ip_forward= 1
sudo sysctl net.ipv4.
The iptables rules are trivial to add. The ip_forward thing is a bit trickier, because I don't want to leave a mess on people's systems. If you snap install lxd, then do lxd init, then snap remove lxd, you'll have that rule set for you, however, so microstack wouldn't be unique in setting the rule.
I'm a little tempted to add a "microstack. configure" command. Or "microstack init". That would give the user a bit more warning that they might be writing some configuration to their system outside the snap. And it would get around our timeout issues w/ mysql. Hmmm ...