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

Direct Users to vmpooler-deployment

Browse source 
Since the recommended method of developing and deploying vmpooler is via vmpooler-deployment, I think we should direct users here instead. Also, I don't think there's any sense in maintaining multiple gemfiles and dockerfiles across multiple repos, if one of them should be the source of truth.
This commit is contained in:
Jake Spain 2023-03-28 16:49:55 -04:00
parent b6819de326
commit e2dedef426
No known key found for this signature in database
GPG key ID: BC1C4DA0A085E113
9 changed files with 6 additions and 336 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -31,6 +31,8 @@ VMPooler provides configurable 'pools' of instantly-available (pre-provisioned)
At [Puppet, Inc.](http://puppet.com) we run acceptance tests on thousands of disposable VMs every day. VMPooler manages the life cycle of these VMs from request through deletion, with options available to pool ready instances, and provision on demand.
The recommended method for deploying VMPooler is via [https://github.com/puppetlabs/vmpooler-deployment](vmpooler-deployment).
### Migrating to v3
Starting with the v3.x release, management of DNS records is implemented as DNS plugins, similar to compute providers. This means each pool configuration should be pointing to a configuration object in `:dns_config` to determine it's method of record management.