Make the VMonG5k provider idempotent
- Introduce a force_deploy option which controls whether any existing VM should be destroyed.
- Add a
destroy.yml
playbook for this purpose. - Adapt the
site.yml
to support idempotency, the already running VMs are listed so that we don't attempt to start them again
Fix #4 (closed)