canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain/Extsync: Difference between revisions
ReleaseEngineering/PuppetAgain/Extsync (view source)
Revision as of 17:27, 5 August 2014
, 5 August 2014no edit summary
(Created page with "= Overview = It's not uncommon to need to synchronize some data into puppet from another authoritative source. That may be a list of users, SSH keys, machine characteristics...") |
No edit summary |
||
| Line 21: | Line 21: | ||
The following describe the existing extsyncs: | The following describe the existing extsyncs: | ||
= | = slavealloc = | ||
This | This synchronizes slave data from slavealloc. | ||
== Parameters: == | |||
;slavealloc_api_url: the URL from which to pull the data (`/slaves` is appended to this URL) | |||
== Result: == | |||
A hiera key named 'slavealloc_slaves' containing a hash by unqualified slavename. Each value in the hash contains the slavealloc-supplied information about the slave, including its environment. | |||
== Functions: == | |||
The `slavealloc_environment($fqdn)` function fetches the environment for a buildslave. | |||
= fake_slavealloc = | |||
This is like slavealloc, but does no actual syncing; add data to `/etc/hiera/fake_slavealloc.yml`. | |||