Releases: puppetlabs/vmpooler
Releases · puppetlabs/vmpooler
1.0.0
Mark checked out vms as active
This change sets a VM as running in redis as soon as it is checked out. Without this change when allocated several instances it is possible for a machine that has been allocated for a checkout, but not yet marked as active, to be identified as running when it should not be, which was added in POOLER-191. Without this change a machine may be destroyed during checkout by pool_manager if there are several instances being allocated.
Additionally, redis multi is added for vm checkout operations to minimize the round trips to redis during a checkout operation. Without this addition each VM checkout causes several redis interactions.
0.13.3
- Reduce duplicate of on demand code introduced in POOLER-158 (POOLER-174)
0.13.2
0.13.1
0.13.0
- Add support for ondemand provisioning (POOLER-158)
- redis refactor the redis interaction has changed to leveraging a connection pool
- Check for stale dns records at clone time (POOLER-166)
DO NOT USE THIS RELEASE, use the next one that fixes a merge bug
0.12.0
- Enable support for multiple ldap user objects (POOLER-171)
vmpooler 0.11.2
- (POOLER-161) Fix extending vm lifetime when max lifetime is set
vmpooler 0.10.2
- API endpoint for resetting a pool clearing ready and pending instances (POOLER-153)
- No code changes in 0.10.1/0.10.2 (release process mistake)
vmpooler 0.8.1
Added
- Make VM names human readable