[WIP] Private networks

[fgrehm]

I had a need for private networks last week and this is my first stab at implementing GH-120

TODO

• Integrate pipework into the plugin
• Remove docker specifics from the script not worth the trouble and will make things harder when bringing in upstream changes.
• Make it work with a single ip range (192.168.1.X)
• Clean up when shutting down container (use brctl show brX to check if in use and ip link delete brX to clean up)
• Make it work for any ip range / create multiple bridges Decided to keep things simple and will require the bridge name to be set
• Validate if bridge name is set
• Create bridge only if it is not up
• Make sure it works when bringing up containers in parallel
• Whitelist sudo for private network script execution
• Improve logging / provide information when networking is being configured / deconfigured

[fgrehm]

For those interested on this, unfortunately this is not coming in for 1.0, things are pretty stable right now and the time for a stable 1.0 has past a long time ago ;-)

[fgrehm]

An experimental support for this is available at the next branch and will be released with 1.1.0 (expected at some point in jan / feb)

Docs will come along with the release but for the brave souls willing to build the plugin from sources and give it a spin this is what you'll need to set from the Vagrantfile:

  config.vm.network "private_network", ip: "CONTAINER_IP", lxc__bridge_name: 'BRIDGE_NAME'

lxc__bridge_name is currently required. Support for using a "dynamic name" will be added post 1.1.0

[Ramblurr]

If using virbr0 provided by libvirtd, as outlined in the fedora wiki entry, does the lxc__bridge_name field need to be set to virbro0?

[fgrehm]

Yes, right now the config has to be set at all times.

[moos3]

I noticed they can ping reach other but can't talk to each other on ports. I have verified my firewall settings on my multiple node Vagrant file. Thoughts or Ideas? Seems to be related to this.