We are happy to announce that LinchPin v1.2.0 has been released. This is an enhancement release, which has the following updates:
runDB - Provides a centralized json (tinydb) database for tracking provisioning transactions
- A run_id is now assigned to each transaction
- A 'unique-ish' hash is assigned to each transaction, some providers use this in the naming of the instances
- The the most recent 'up' transaction in the database is used on any destroy actions
- A --run-id (-r) flag can be passed to idempotently provision, or destroy any specific transaction
Deprecate output_writer role. Use gather_resources role, which refers to runDB as appropriate.
The libvirt module has multiple improvements
- Enhanced schema to enable cloud_config for cloud-init functionality
- Libvirt functionality can now be run on a remote system
- SSH keys can be passed using the cloud-init ssh-import-id functionality
- Keys can be copied from the local system or from remote locations
- This supports downloading keys from github and launchpad
- Enabled virt console for troubleshooting issues
- May require privilege escalation to copy images and keys
Linchpin Journal - provides output from the runDB for each transaction
Openstack can now boot from an image
Docker images now perform integration testing
Installation documentation improvements