You can also do zfs/btrfs snapshots before doing a distribution upgrade, allowing for a rollback of the OS. SuSE has rolled this into some of the most recent versions of their OS (I believe the command line tool is called snapper).
EIther way, none of the solutions are particularly puppet oriented. On Wed 22 Jan 2014 06:00:57 PM EST, Steven VanDevender wrote: > Jason Antman writes: > > There's nothing existing that I know of that works in the GUI-based way > > you seem to be talking about. Because, well, we *nix people usually > > don't do that. > > > I've really only worked on RPM-based systems, so I'm not sure if this is > > still applicable in the debian world... > > Debian-based distributions have interactive tools like "aptitude" > (curses-based) or "synaptic" (GNOME GUI) that can let you do selective > package installation and upgrades on a host, in addition to the > command-line "apt-get" and "dpkg" utilties. These don't really offer > centralized management of a group of hosts, though. > > In the RPM world there's Spacewalk (or the Red Hat Satellite Server > commercial product based on it) for doing centralized package > management. There's probably some equivalent in the Debian world but > I'm not aware of what that is. Setting up a local repository mirror can > let you control what packages are visible to hosts so you can control > package versions for installation and upgrades (in fact, I've seen > people set up multiple mirrors visible to different environments so they > can do things like staged upgrade testing). > > > There are 2 types of updates I do > > > > 1) updating one package or a set of packages (like, updating Puppet from > > 3.1.0 to 3.4.1) which I do with the "ensure" parameter on the Package > > type. Some stuff is wrapped up in classes, and this can be done through > > an ENC (parameterized classes, or global params if need be) or Hiera. > > I'll change the version on one node, test it, then an environment, test > > it, and eventually apply it everywhere. If you need to downgrade/roll > > back, that *can* work... might work better in the apt/deb world than it > > does in yum/rpm. > > > > 2) Full system updates/upgrades, what RHEL-derivatives term as > > "distribution upgrades", i.e. updating all packages from CentOS 6.3 to > > 6.4. I rebuild the box. No reason to mess with doing this through the > > distro, I just shut it down, clean the cert in puppet, do a fresh PXE > > boot (and kickstart) and let Puppet do its thing. This has the added > > benefit of reducing entropy, and even providing a nice DR test (like if > > you just log in and poweroff immediately...) > > > > -Jason > > > > On 01/22/2014 09:31 AM, Muhammad Yousuf Khan wrote: > > > Hello All, > > > > > > i have seen so many apt modules on puppet forge website. they are more > > > like changing source list path defining. HTTP proxy blah blah but what > > > i want is a bit more. > > > is there any apt module which can help me to update only selective > > > updates (like in Microsoft Wsus does, it list down all the updates and > > > people can select and apply those patches on selective nodes and if > > > they find it problematic then can remotely uninstall it too.i want > > > this to be done on my Debian server farm and and i also want to roll > > > back as needed (for example if any securety or OS update creating > > > problem of some kind i can roll it back with puppet live > > > management/manual run). > > > i dont know how practical it is. however as i have already got the > > > concept of Wsus therefore my mind is trying to think of wsus like > > > puppet module. > > > Please help. > > > thanks, > > > MYK > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52E117FA.1070906%40throwe.com. For more options, visit https://groups.google.com/groups/opt_out.
