Ohad Levy
2009-Nov-29 14:18 UTC
[Puppet Users] manitest - a simple tool to help your puppet development and testing
If it happened to you before that someone broke your manifest because of simple change (e.g. didnt test it on all hosts/classes external nodes ... combinations) this tool might be useful for you. the idea is very simple, just try to compile the manifest based on customized facts, classes, environments and external nodes parameters (if you use it) . You need to run this script only were you develop your manifests (e.g. your puppetmaster), there is no need to try out a puppet run on each and every system type that you have. You might also find it useful to run this script in some sort of a cron or via a repo hook, to find out any broken manifests running around.. This script was originally written by a colleague of mine (Paul Kelly), however, I''ve adjusted it to hopefully common usage. Its brand new, so any comments / improvements (which I''m sure there are plenty) are welcomed. Hopefully you''ll find it useful, Ohad http://github.com/ohadlevy/manitest -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Nigel Kersten
2009-Dec-01 18:47 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy <ohadlevy@gmail.com> wrote:> If it happened to you before that someone broke your manifest because of > simple change (e.g. didnt test it on all hosts/classes external nodes ... > combinations) this tool might be useful for you.No-one else tried this out? It''s really quite cool. Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired there. We actually serve our manifests out of a different location, so I had to do a minor tweak to get that working. It''s a shame we can''t impersonate architectures though... I''d love to be able to simulate catalog runs of a Mac client on a Linux continuous build server.> > the idea is very simple, just try to compile the manifest based on > customized facts, classes, environments and external nodes parameters (if > you use it) . > You need to run this script only were you develop your manifests (e.g. your > puppetmaster), there is no need to try out a puppet run on each and every > system type that you have. > > You might also find it useful to run this script in some sort of a cron or > via a repo hook, to find out any broken manifests running around.. > > This script was originally written by a colleague of mine (Paul Kelly), > however, I''ve adjusted it to hopefully common usage. > > Its brand new, so any comments / improvements (which I''m sure there are > plenty) are welcomed. > > Hopefully you''ll find it useful, > Ohad > > http://github.com/ohadlevy/manitest > > -- > > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- nigel -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Frank Sweetser
2009-Dec-01 18:53 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On 12/01/2009 01:47 PM, Nigel Kersten wrote:> On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy<ohadlevy@gmail.com> wrote: >> If it happened to you before that someone broke your manifest because of >> simple change (e.g. didnt test it on all hosts/classes external nodes ... >> combinations) this tool might be useful for you. > > No-one else tried this out? It''s really quite cool.I immediately added it to my todo list, but unfortunately I''m low on round tuits right now...> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired > there. We actually serve our manifests out of a different location, so > I had to do a minor tweak to get that working. > > It''s a shame we can''t impersonate architectures though... I''d love to > be able to simulate catalog runs of a Mac client on a Linux continuous > build server.Well, all of that architecture stuff keys off of facter, right? How hard would it be to serialize the output of ''facter -p'' and feed it to the puppet run that does the core of the testing work? -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Scott Smith
2009-Dec-01 19:04 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
Nigel Kersten wrote:> It''s a shame we can''t impersonate architectures though... I''d love to > be able to simulate catalog runs of a Mac client on a Linux continuous > build server. >I wonder if you could with something like this... http://fedoraproject.org/wiki/Projects/Mock -scott -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Nicolas Szalay
2009-Dec-01 20:17 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
Tried it out and did a bunch of debugging with ohad. Works really fine, I planned to check all manifests but I still not decided how to do it on a continous basis. I have to take a look at hudson. Nicolas. ----- Mail Original ----- De: "Nigel Kersten" <nigelk@google.com> À: puppet-users@googlegroups.com Envoyé: Mardi 1 Décembre 2009 19:47:38 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy <ohadlevy@gmail.com> wrote:> If it happened to you before that someone broke your manifest because of > simple change (e.g. didnt test it on all hosts/classes external nodes ... > combinations) this tool might be useful for you.No-one else tried this out? It''s really quite cool. Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired there. We actually serve our manifests out of a different location, so I had to do a minor tweak to get that working. It''s a shame we can''t impersonate architectures though... I''d love to be able to simulate catalog runs of a Mac client on a Linux continuous build server.> > the idea is very simple, just try to compile the manifest based on > customized facts, classes, environments and external nodes parameters (if > you use it) . > You need to run this script only were you develop your manifests (e.g. your > puppetmaster), there is no need to try out a puppet run on each and every > system type that you have. > > You might also find it useful to run this script in some sort of a cron or > via a repo hook, to find out any broken manifests running around.. > > This script was originally written by a colleague of mine (Paul Kelly), > however, I''ve adjusted it to hopefully common usage. > > Its brand new, so any comments / improvements (which I''m sure there are > plenty) are welcomed. > > Hopefully you''ll find it useful, > Ohad > > http://github.com/ohadlevy/manitest > > -- > > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- nigel -- 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ohad Levy
2009-Dec-02 01:46 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten <nigelk@google.com> wrote:> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired > there. We actually serve our manifests out of a different location, so > I had to do a minor tweak to get that working. >I''ll see what I can do about that ;)> > It''s a shame we can''t impersonate architectures though... I''d love to > be able to simulate catalog runs of a Mac client on a Linux continuous > build server. >Well, the answer for this is - it depends :) the main problem here is not to override the facts (which must do anyway), but things that the puppet provider will force, e.g. an example error that you *might* get if you try it on another operating system (in this example a Solaris manifest on a Linux host) debug: Puppet::Type::Host::ProviderParsed: file /etc/inet/hosts does not exist Could not find a default provider for host nevertheless, it might work for your environment, but as you can see in this case, it generates a false alarm. Cheers, Ohad -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ohad Levy
2009-Dec-02 01:47 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
Hi Scott, I don''t see how this can help us, see explanation from previous email :) Ohad On Wed, Dec 2, 2009 at 3:04 AM, Scott Smith <scott@ohlol.net> wrote:> Nigel Kersten wrote: > > It''s a shame we can''t impersonate architectures though... I''d love to > > be able to simulate catalog runs of a Mac client on a Linux continuous > > build server. > > > > I wonder if you could with something like this... > > http://fedoraproject.org/wiki/Projects/Mock > > -scott > > -- > > 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ohad Levy
2009-Dec-02 01:48 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
We are working internally to come up with some regressions, if it turns out to usable I''ll be more than happy to share. If you get to a stage hudson is working - let us know :) Ohad On Wed, Dec 2, 2009 at 4:17 AM, Nicolas Szalay <nszalay@qualigaz.com> wrote:> Tried it out and did a bunch of debugging with ohad. Works really fine, I > planned to check all manifests but I still not decided how to do it on a > continous basis. I have to take a look at hudson. > > Nicolas. > > ----- Mail Original ----- > De: "Nigel Kersten" <nigelk@google.com> > À: puppet-users@googlegroups.com > Envoyé: Mardi 1 Décembre 2009 19:47:38 GMT +01:00 Amsterdam / Berlin / > Berne / Rome / Stockholm / Vienne > Objet: Re: [Puppet Users] manitest - a simple tool to help your puppet > development and testing > > On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy <ohadlevy@gmail.com> wrote: > > If it happened to you before that someone broke your manifest because of > > simple change (e.g. didnt test it on all hosts/classes external nodes ... > > combinations) this tool might be useful for you. > > No-one else tried this out? It''s really quite cool. > > Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired > there. We actually serve our manifests out of a different location, so > I had to do a minor tweak to get that working. > > It''s a shame we can''t impersonate architectures though... I''d love to > be able to simulate catalog runs of a Mac client on a Linux continuous > build server. > > > > > > > the idea is very simple, just try to compile the manifest based on > > customized facts, classes, environments and external nodes parameters (if > > you use it) . > > You need to run this script only were you develop your manifests (e.g. > your > > puppetmaster), there is no need to try out a puppet run on each and every > > system type that you have. > > > > You might also find it useful to run this script in some sort of a cron > or > > via a repo hook, to find out any broken manifests running around.. > > > > This script was originally written by a colleague of mine (Paul Kelly), > > however, I''ve adjusted it to hopefully common usage. > > > > Its brand new, so any comments / improvements (which I''m sure there are > > plenty) are welcomed. > > > > Hopefully you''ll find it useful, > > Ohad > > > > http://github.com/ohadlevy/manitest > > > > -- > > > > 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > nigel > > -- > > 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Nigel Kersten
2009-Dec-02 01:51 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Tue, Dec 1, 2009 at 5:46 PM, Ohad Levy <ohadlevy@gmail.com> wrote:> > > On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten <nigelk@google.com> wrote: >> >> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired >> there. We actually serve our manifests out of a different location, so >> I had to do a minor tweak to get that working. > > I''ll see what I can do about that ;) >> >> It''s a shame we can''t impersonate architectures though... I''d love to >> be able to simulate catalog runs of a Mac client on a Linux continuous >> build server. > > Well, the answer for this is - it depends :) > the main problem here is not to override the facts (which must do anyway), > but things that the puppet provider will force, e.g. an example error that > you *might* get if you try it on another operating system (in this example a > Solaris manifest on a Linux host) > > debug: Puppet::Type::Host::ProviderParsed: file /etc/inet/hosts does not > exist > Could not find a default provider for host > > nevertheless, it might work for your environment, but as you can see in this > case, it generates a false alarm.Yep. It''s the provider forcing stuff that is the problem. I was going to start digging in to work out what''s a real alarm and what isn''t. How are you using this Ohad? Are you running it on your servers? I''m thinking of moving one of my test servers to collect the cached node info for all my clients and continuously run manitest against the development code for my environments, perhaps triggered by changelist submissions to my VCS.> > Cheers, > Ohad > > -- > > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- nigel -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ohad Levy
2009-Dec-02 02:01 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Wed, Dec 2, 2009 at 9:51 AM, Nigel Kersten <nigelk@google.com> wrote:> Yep. It''s the provider forcing stuff that is the problem. I was going > to start digging in to work out what''s a real alarm and what isn''t. > > How are you using this Ohad? Are you running it on your servers? > > Currently we''ve created a list of "common" node types with various classesand parameters - which will be executed based on a repo hook. another usage is that a person which is developing a manifest, will run this test on a few basic node file, to filter out any programming error - similar to the way some puppet use --parseonly. I''m considering running it in some sort repo hook when committing, but not sure how good of an idea it would be.> I''m thinking of moving one of my test servers to collect the cached > node info for all my clients and continuously run manitest against the > development code for my environments, perhaps triggered by changelist > submissions to my VCS. > > That''s probably a good idea (but), usually the problem I have is not onexisting node setup, rather that someone will add one more class to its host manifest and then everything breaks.. I''m happy you find it useful! cheers, Ohad -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Luke Kanies
2009-Dec-02 06:28 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Nov 29, 2009, at 6:18 AM, Ohad Levy wrote:> If it happened to you before that someone broke your manifest > because of simple change (e.g. didnt test it on all hosts/classes > external nodes ... combinations) this tool might be useful for you. > > the idea is very simple, just try to compile the manifest based on > customized facts, classes, environments and external nodes > parameters (if you use it) . > You need to run this script only were you develop your manifests > (e.g. your puppetmaster), there is no need to try out a puppet run > on each and every system type that you have. > > You might also find it useful to run this script in some sort of a > cron or via a repo hook, to find out any broken manifests running > around.. > > This script was originally written by a colleague of mine (Paul > Kelly), however, I''ve adjusted it to hopefully common usage. > > Its brand new, so any comments / improvements (which I''m sure there > are plenty) are welcomed.This is definitely very cool. It seems a bit limited because it actually runs the whole configuration, but I like it. It should definitely be straightforward to extend it to use a given host''s Facts. You might also be able to get some inspiration on how to use the internal APIs by looking at puppet-test, which covers most of these bits using the internal APIs. -- I wanna hang a map of the world in my house. Then I''m gonna put pins into all the locations that I''ve traveled to. But first, I''m gonna have to travel to the top two corners of the map so it won''t fall down. -- Mitch Hedberg --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
James Turnbull
2009-Dec-02 06:43 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Luke Kanies wrote:> It seems a bit limited because it actually runs the whole > configuration, but I like it. It should definitely be straightforward > to extend it to use a given host''s Facts. > > You might also be able to get some inspiration on how to use the > internal APIs by looking at puppet-test, which covers most of these > bits using the internal APIs. >For the benefit of people who might not know the puppet-test script is in the ext directory of the source package or via: http://github.com/reductivelabs/puppet/blob/master/ext/puppet-test Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSxYMgSFa/lDkFHAyAQLM9AgA3BLEP1mbHciREtQx44cd/WxTjJRfOMLJ lBNKmFGdUSXiPisIvChtz+oZDPOOU7Gt3wUQCp4y031Lc/Jhx3zWRkT5Jy4zFwbf xuSaX/UMY11VuYA9k7NtFMediVY/nHrUU50RqiNm6I94a7XpkJwUxY99c2qXVKZJ ctc5axMfCa95svl9k202eU+OvH+9dccuKJbjLw7OKz9lkF6rkNpQDyfC384r2Xbg epBsIGJ2vfXk8pOdSbfr3iJ21bCGujGxgYJj+/mXpcAt1FAV0dj9irA877xZGd8n Dq8S2DvaQImN++Kv/FaQ8brLbKTODfrox3u+9aPrm/MTYHXzcJis1A==vpIC -----END PGP SIGNATURE----- -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ohad Levy
2009-Dec-02 15:17 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten <nigelk@google.com> wrote:> > Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired > there. We actually serve our manifests out of a different location, so > I had to do a minor tweak to get that working. >latest code allow you to tweak it via a command line argument. cheers, Ohad -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Scott Smith
2009-Dec-02 23:23 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
Ohad Levy wrote:> Hi Scott, > > I don''t see how this can help us, see explanation from previous email :) > Ohad >Yeah :) I guess I was just alluding to the idea of using a chrooted jail that emulated another arch. :) -scott -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Paul Nasrat
2009-Dec-03 00:18 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
2009/12/2 Scott Smith <scott@ohlol.net>:> Ohad Levy wrote: >> Hi Scott, >> >> I don''t see how this can help us, see explanation from previous email :) >> Ohad >> > > Yeah :) I guess I was just alluding to the idea of using a chrooted jail > that emulated another arch. :)Mock can pretty much only do setarch so that it can only represent the same family and lower in terms of architecture. It doesn''t allow you to do say ppc on i386 but does allow you to do say a i386 chroot on x86_64. It may be possible with chroots and qemu to do some arch translation stuff but really I''d say if you have a complex multi-arch setup you should ensure you have "development" and "test" systems for your systems people to work on and that can integrate with manifest testing tools. Paul -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Scott Smith
2009-Dec-03 04:19 UTC
Re: [Puppet Users] manitest - a simple tool to help your puppet development and testing
Paul Nasrat wrote:> translation stuff but really I''d say if you have a complex multi-arch > setup you should ensure you have "development" and "test" systems for > your systems people to work on and that can integrate with manifest > testing tools. >Good point. What about easily spinning up instances for testing, though? I have multiple QA environments so it''s not much of an issue here, but I could see some value in being able to do it without dealing with an actual VM. Maybe it''s not that big of a deal. Most of my experience is with VMware, soooo. -scott -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.