Hello Eric, just a heads up about my questions :-D On Fri, Mar 3, 2017 at 2:53 PM, Miguel Di Ciurcio Filho <[email protected]> wrote: > On Mon, Feb 27, 2017 at 8:59 PM, Eric Sorenson <[email protected]> > wrote: >> The headline here is that the core open-source "Puppet Platform" >> (puppet-agent, puppet-server, puppetdb) are moving to a more coordinated >> release model, with compatibility guarantees and consistent versioning among >> the components. The first release of this "Puppet Platform 5", currently >> targeted at May, will bring these components' major versions together and >> provide some nice features without a huge backwards-incompatible break. > > Good news! > > Would be possible to also version the components that go inside the > puppet-agent package in the same way? For example: facter, hiera and > mcollective. > > Speaking about mcollective, it has been notorious that Puppet Inc. has > stopped any further development and has put mcolletive in maintenance > mode for quite a while, in favor of the Orchestrator in 2015. > > Fast forward to 2017 and there are a lot of useful stuff in > mcollective still not available in the Orchestrator. > > Is also known that R.I.Pienaar is trying to work with Puppet Inc to > maintain mcollective. Also, I consider his work on choria.io > remarkable and has keep mcollective powerful and useful once again. > > Last years PuppetConf we where told that the server side of the > orchestrator would be merged into Puppet Server. > > Looking into a "Puppet Platform 5", what looks like to be the > orchestration option? > > >> Q: How's it going to be delivered? Are Puppet Collections still a thing? >> A: Funny you should ask. As we kicked around a couple of months ago[3], it's >> been two years and the collections idea just hasn't worked out in practice, >> so it seems wise to iterate and keep evolving. The current plan is to create >> a new repo, parallel with the existing PC1 repos, simply named 'puppet'. The >> platform components will roll into it and future semver-majors will be >> coordinated across the components, hopefully leading to smaller, easily >> digestible chunks of change. > > Sounds reasonable. > > Would be this the time to also use /etc/puppet and /opt/puppet?
-- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAK6Ystn0gsjUeHtQ7MjwuUQa1J7bEmPXTUikao2V75cx75n34Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
