The test networks were being setup using networkd and a custom template,
this change updates the process so we're dog fooding.
Additionally change the container config drop so that its executing a
container restart when needed and in the right order.
Several tests were removed because they are basic operations which are
already being tested in the nspawn_hosts role.
Change-Id: I50799d53f8d75f043ed12d4e50da3d55a4ee159a
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
The changes here remove the boiler plate code we had in favor of using
all of our common roles. This also updates the nspawn role using some of
the learnings we've had from our recent LXC changes and ensures we're
not breaking any compatibility we had with our various distros.
Add option to run a full config update if required
> As a deployer I need the ability to make a sweeping change to container
configs if required. At present the nspawn container create role will
attempt to preserve the configs and update only what's required, which
is desirable when maintaining uptime. This change provides the option
`nspawn_container_preserve_config` which, if set to "false" will
template the container configs instead of trying to preserve it.
Document everything in config
Change-Id: Ie969c10578e1102767ad8991c9d6171b547aef87
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Dmitriy Rabotyagov