puppetlabs/vmpooler
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler.git synced 2026-01-26 01:58:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
vmpooler/CHANGELOG.md
kirby@puppetlabs.com 3e26a8f998 (POOLER-139) Fix discovering checked out VM 
This commit updates how vmpooler retrieves VMs to add a VM to the running queue as soon as it is checked out. Without this change it is possible that a VM can be discovered when it is checked out before it is added to the running queue if multiple systems are requested. Additionally, the dockerfile is updated to support specifying the version of vmpooler to install.
2019-02-13 16:43:55 -08:00

3.4 KiB
Raw Blame History

Change Log

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog & makes a strong effort to adhere to Semantic Versioning.

Tracking in this Changelog began for this project with the tagging of version 0.1.0. If you're looking for changes from before this, refer to the project's git logs & PR history.

Unreleased

0.5.0

Fixed

  • Eliminate window for checked out VM to be discovered (POOLER-139)

0.4.0

Fixed

  • Improve support for configuration via environment variables (POOLER-137)
  • Support multiple pool backends per alias (POOLER-138)
  • Remove redis server testing requirement

0.3.0

Fixed

  • Sync pool size before dashboard is displayed (POOLER-132)
  • Remove a failed VM from the ready queue (POOLER-133)
  • Begin checking ready VMs to ensure alive after 1 minute by default
  • Ensure that metric nodes for vm usage stats are consistent

Added

  • Add capability to ship VM usage metrics (POOLER-134)

0.2.2

Fixed

  • Return label used to request VMs when fulfilling VM requests (POOLER-131)

0.2.1

Fixed

  • Better handle delta disk creation errors (POOLER-130)

Added

  • Re-write check_pool in pool_manager to improve readability
  • Add a docker-compose file for testing vmpooler
  • Add capability to weight backends when an alias spans multiple backends (POOLER-129)

0.2.0

Fixed

  • (POOLER-128) VM specific mutex objects are not dereferenced when a VM is destroyed
  • A VM that is being destroyed is reported as discovered

Added

  • Adds a new mechanism to load providers from any gem or file path

0.1.0

Fixed

  • Remove unused method find_pool and related pending tests
  • Setting max_tries results in an infinite loop (POOLER-124)
  • Do not evaluate folders as VMs in get_pool_vms (POOLER-40)
  • Expire redis VM key when clone fails (POOLER-31)
  • Remove all usage of propertyCollector
  • Replace find_vm search mechanism (POOLER-68)
  • Fix configuration file loading (POOLER-103)
  • Update vulnerable dependencies (POOLER-101)

Added

  • Allow API and manager to run separately (POOLER-109)
  • Add configuration API endpoint (POOLER-107)
  • Add option to disable VM hostname mismatch checks
  • Add a gemspec file
  • Add time remaining information (POOLER-81)
  • Ship metrics for clone to ready time (POOLER-34)
  • Reduce duplicate checking of VMs
  • Reduce object lookups when retrieving VMs and folders
  • Optionally create delta disks for pool templates
  • Drop support for any ruby before 2.3
  • Add support for multiple LDAP search base DNs (POOLER-113)
  • Ensure a VM is only destroyed once (POOLER-112)
  • Add support for setting redis server port and password
  • Greatly reduce time it takes to add disks
  • Add Dockerfile that does not bundle redis
  • Add vmpooler.service to support systemd managing the service