Add the ability to create snapshots and restore from them
Make instance creation, deletion, restore, and snapshotting idempotent
(really helps testing a playbook if you can run it multiple times)
Using `ec2_tag` module without the state argument
currently results in:
```
failed: [127.0.0.1] => {"failed": true, "parsed": false}
```
This fix makes `state=present` the default
- extra properties were not set at creation, only when updating
which can be overlooked when running the module from more than 1 node...
- fix bas var as time_until_up didn't get used
The virtualenv parameter to the django_manage command is used to locate
the virtualenv and build it if necessary. Access to the virtualenv
executable is only needed if the virtualenv directory doesn't exist and
needs to be built. This patch allows for the situation where a
virtualenv that is not in the PATH was used to create a virtualenv prior
to running the django_manage module.
This allow one to specify a specific internal network name for the case
where there is more than one nic on an instance. Without this, the list
of ports may not return the correct order. Therefore, it is necessary
to specify the exact internal network to attach the floating ip to
The quantum_* modules will now try neutronclient first, and fall back
to quantumclient. If that fails, error out.
The code now references neutron instead of quantum in all internal
cases.
cs.images.find(human_id= throws novaclient.exceptions.NotFound,
resulting in the try/except block with
image = cs.images.find(name=image) being skipped. catching
novaclient.exception.NotFound allows images to be specified with the
human readable name.
Example:
tasks:
- name: Server build request
local_action:
module: rax
region: DFW
image: Ubuntu 12.04 LTS (Precise Pangolin)
Also, the import is placed after try: import pyrax, because pyrax
imports novaclient and should fail if novaclient is missing.
Line 276: no_reboot = dict(default=True, type="bool"),
This should really default to False (When AMIs are created the machine will reboot before copying the disk).
"When enabled, Amazon EC2 does not shut down the instance before creating the image. When this option is used, file system integrity on the created image cannot be guaranteed."
