| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upstream to 5.4.0 [1][2][3][4][5]
* Puppet 5 recipe is the official Puppet agent version
with support for Ruby 2.4 [6]
* Updated reference versions in the README file
* Hiera isn’t separate from Puppet anymore [7].
* Do not install extlookup2hiera, it has been removed upstream
* Hiera began as an independent Ruby library that worked with
Puppet. Over time, it became a requirement and was even included
in the puppet-agent package, but it was limited by its original
design.
* Removed puppet_3.7.3.bb recipe
* Drop the superseded patches
* Added init script
* Added systemd script
Facter 2.5 upstream release
* Puppet 5 relays on Facter 3.10. Facter 3.10 reworks Facter 2.X
code [8] in native code instead of Ruby gem. Facter 2.5 is
still compatible with 5 series to help with Puppet 5 testing.
* facter before 2.4.0 uses a deprecated Puppet settings API
making `facter --puppet` no longer work with Puppet 4 or
higher [9].
* Community, partner, and some of Puppet's internal testing
workflows continue to use (ruby) Facter 2.4 [10], instead of
native Facter 3, which is not (yet) available as a gem.
* To help with Puppet 5 testing, we need to do a maintenance
release in the Facter 2 series.
[1] https://docs.puppet.com/puppet/5.0/release_notes.html
[2] https://docs.puppet.com/puppet/5.1/release_notes.html
[3] https://docs.puppet.com/puppet/5.2/release_notes.html
[4] https://docs.puppet.com/puppet/5.3/release_notes.html
[5] https://docs.puppet.com/puppet/5.4/release_notes.html
[6] https://puppet.com/docs/puppet/4.10/hiera_intro.html
[7] https://tickets.puppetlabs.com/browse/PA-1107
[8] https://github.com/puppetlabs/facter/tree/3.10.x
[9] http://metadata.ftp-master.debian.org/changelogs/main/p/puppet/puppet_5.1.0-1_changelog
[10] https://tickets.puppetlabs.com/browse/FACT-1630
Signed-off-by: Pablo Saavedra <psaavedra@igalia.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should uprev puppet at some point but for the sake of stabilizing
first the following set of patches will allow puppet to work with the
newer version of Ruby that we are using.
The first two are upstream commits and the third is a commit which
borrows a fix found in various puppet forks (repos which people host
to stabalize older versions of puppet). With these patches puppet can
now execute commands like 'help' and 'apply' without falling over.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we get the following warning when building puppet:
WARNING: QA Issue: /usr/lib/ruby/gems/2.2.0/gems/puppet-3.7.3/
lib/puppet/vendor/safe@underscore@yaml/run@underscore@specs@
underscore@all@underscore@ruby@underscore@versions.sh_puppet
contained in package puppet requires /bin/bash, but no
providers found in its RDEPENDS [file-rdeps]
Adding 'bash' as an RDEPENDS fixes this.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
Puppet can be used by many 'cloud services', it is not openstack
specific, so moving puppet and puppet related recipes to the
meta-cloud-services base layer. This allows either internal sub-layers
found in meta-cloud-services or external layers to include
meta-cloud-services without being burdened by bbappends and configs
found in meta-openstack.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
