Hello! bertagaz <[email protected]> writes:
> When upgrading a puppet master from Wheezy to Jessie, it's not possible > anymore to use the `storeconfigs` option, which is required for manifests to > use exported resources. This lead to have to rewrite the manifests to get > rid of them, often in a ugly and hackish way. Are those modifications available anywhere? It would be nice to try and incorporate them in some shared modules! > That's because in puppet 3.x, a switch has been made upstream from > activerecord to puppetdb as a backend for catalog storage and searching. Hmm, I think that is not true. Activerecord storedconfigs still work, they are somewhat deprecated, and I believe removed in puppet 4, but I know people who have used storeconfigs in 3.6.2. Additionally, I've looked through the release notes[0] and I could find nothing that said that it was removed. > It seems that puppetdb is not packaged into Debian at the moment. There's > an open RFP for it at #673515, and upstream has a Debian package at > apt.puppetlabs.com. > > This looks like a regression, which either need to be fixed before the > Jessie release, or documented in the release notes, but the last option > will probably bring a lot of hassle to sysadmins. What kind of errors are you getting that lead you to this conclusion? Also - I think that moving modules to make storedconfigs 'optional' is a very good thing to do. Many people use masterless puppet setups which cannot use storeconfigs and would benefit from any work that is done there! micah 0. https://docs.puppetlabs.com/release_notes/
signature.asc
Description: PGP signature
