On Fri, Apr 13, 2012 at 12:06 PM, Ashley Penney <apen...@gmail.com> wrote:
> I think that would be OK. I'm actually fairly nervous about this new move > towards dragging > more and more out of the core into modules. It wouldn't be so bad if > Puppet had a proper > "packaging system" that handled dependencies and so forth, but as it > stands I'm just worried > about reaching a situation where we're constantly telling people in > #puppet "oh, well first > you need to get stdlib, nagios, yum, this, that, etc, that's why you can't > do this". > It's important to note here that the version of the module tool we're talking about does indeed handle dependencies automatically, although prior versions didn't. > > However assuming this is going ahead then I think the error message should > probably for > now tell the user that they've been moved AND spit out an appropriate > commandline to > immediately import the module to the right place. > > On Fri, Apr 13, 2012 at 1:55 PM, Michael Stahnke > <stah...@puppetlabs.com>wrote: > >> For the next major Puppet version, code-named Telly, we have some >> changes coming. This is the first in a series of emails around these >> changes and may require some input from the community. >> >> For Telly, the nagios types will be moved into a module. This allows >> them to be iterated on in isolation from the rest of Puppet's core >> release cycle and process. In the future we have plans to move several >> other types into modules that can be individually maintained, >> improved, tested and used. >> >> The module for Nagios will be available on the Forge. >> >> The upgrade path is the thing we need some feedback about. The basic >> steps to upgrade would be to setup a Telly master, and then install >> the Nagios module via the Puppet Module Tool, which ships integrated >> with 2.7.13+ and Telly. >> >> The only caveat with this is that if, in the past, you were relying on >> the Nagios types and forget to install that module (or are unable to >> for some reason), you would get a failure. The best proposal we could >> come up with was to have the platform team add some code that lets the >> user know that the Nagios types have moved. This basically moves this >> into a 'fail-well' state. We'll try to provide the best information >> possible to the end-user about what is going on. >> >> Is that an acceptable path moving forward? Comments and discussion >> welcome. >> >> >> Mike Stahnke >> Community Manager >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Nigel Kersten Product Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
