Thanks for sharing, David. Maybe there's the rub. The big systems can't be reduced down to such a simple approach, and the little systems don't require such rigour? I don't run many nodes but I do have this obsessing with testing infrastructure.
J. > One of my problems with this approach is my heavy usage of > export/collect. A significant portion of my problems only surface after > more than one node has exported resources AND another one has collected > them. For me that means that a serious setup will have to have a live > testing environment that has instances of all live services and > integrates all recent changes from the developers. Changes that have > survived a few days without killing the testing environment then can be > rolled out into production. > > > For my personal systems I just develop in the "development" environment > and manually test on the live servers with "puppetd --test > --environment=development --noop" until I'm satisfied. Which, I have to > admit is not very rigorous. But then, I'm a one-man, few-nodes outfit > and can cut corners, others can't cut. > > > > Regards, DavidS > > -- > dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at > Klosterneuburg UID: ATU64260999 > > FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
