Hi, On Mon, 2 Mar 2015 17:18:18 +0100 Christian Hofstaedtler <[email protected]> wrote: > IMO, nothing of value has been lost, and the only thing that should > probably be done is a NEWS/RelNotes entry (which likely is required > anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does > yield anything working at all).
For anyone following the best practices suggested upstream during the 2.x cycle, the 2.7 manifests should mostly work. They certainly did for us (approx 100 modules, some of them rather complicated) with just a couple of deprecation warnings that we fixed early on. As for stored configs, the schema and code has not changed at all, so there is no reason for it not to work. My tests sofar have shown that it works as it should, with the - known - limitation that structured facts are not supported. Personally, I wouldn't want an upgrade to Jessie force me to install an external dependency like PuppetDB. Furthermore, we have a custom set of tools developed around the stored configs database that would need porting to PuppetDB as well. Since upstream still provides AR-based stored configs in 3.7 (even though it may be marked as deprecated), my view is we should support it if we can. Then for Puppet 4/5/whatever we definitely need to provide a PuppetDB package. Regards, Apollon
signature.asc
Description: Digital signature
