> On Apr 7, 2017, at 6:46 AM, Miguel Di Ciurcio Filho <mig...@instruct.com.br> > wrote: > > Hello Eric, just a heads up about my questions :-D > > On Fri, Mar 3, 2017 at 2:53 PM, Miguel Di Ciurcio Filho > <mig...@instruct.com.br> wrote: >> On Mon, Feb 27, 2017 at 8:59 PM, Eric Sorenson <eric.soren...@puppet.com> >> 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.
Hi Miguel - We're not planning to move facter and the stand-alone hiera package to v5.0. The new environment-aware Hiera is "5" internally but it is part of Puppet, the previous standalone gem/tarball need to stay at their current version to avoid any more confusion. mcollective is on its own release scheme, so it's not moving to 5 also. >> >> 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. Yes this is unfortunately true. >> >> 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. We are including the NATS gem necessary to run choria agents in the puppet-agent 5 package, to make it easy to set up. >> >> Last years PuppetConf we where told that the server side of the >> orchestrator would be merged into Puppet Server. We should be more transparent on this - it is still in the plan but has been delayed due to priority changes on the project. I'm still hopeful this will be out in the next few months but won't be in the 5.0 release. >> Looking into a "Puppet Platform 5", what looks like to be the >> orchestration option? I wish I had a better answer, but you are correct that we are between old and new tools. We will still include mco 2.x, pxp agent and nats to make different options possible, but have not conclusively settled on a unified orchestration solution. >> >> >>> 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. One comment here from the rest of the thread, the plan is to make a new repo named "puppet5", with a symlink and symbolic release package pointing at "puppet". Then when there are new versions, they will go into "puppet6" and the symlink will be updated. So you can either pick the numbered major version and stick with it until you are ready to opt-in to the new major series, or use the symbolic name and stay current. >> Would be this the time to also use /etc/puppet and /opt/puppet? Good question. I am afraid it would break too many things, so /opt/puppetlabs will be around for a while longer. Eric Sorenson - e...@puppet.com <mailto:eric.soren...@puppet.com> director of product, ecosystem and platform -- 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 puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/E6167332-8D31-4004-A533-CBC2D2178A6B%40puppet.com. For more options, visit https://groups.google.com/d/optout.
