Hi,
cucumber-puppet has reached its end of life:
http://blog.nistu.de/2012/06/09/cucumber-puppet-end-of-life/
In case anyone is interested in picking it up, feel free to contact me.
cheers,
Nikolay
--
"It's all part of my Can't-Do approach to life." Wally
--
You received this message becau
On Mar 29, 11:17 am, Brian Carpio wrote:
> Is cucumber-puppet compatible with Puppet Enterprise 2.5? If not is
> there a test framework which is similar that is?
I haven't used puppet enterprise, but I would be surprised if it
showed massive incompatibilities with the open-source version.
Anyways
Hi,
yesterday I published some ideas about improving the reusability of chef
cookbooks on my blog. As I don't consider this issue chef-specific, you
might be interested in this as well:
http://blog.nistu.de/2012/03/04/reusability-in-configuration-management-systems/
I would love to discuss these
* Brian Troutwine [2011-10-27]:
> While this setup works I hate it. It's tedious, not automated and
> error prone. I wonder, what are the puppet configuration testing
> experiences of other on this list? What have you gotten cobbled
> together, what works and what does not? I'm especially intereste
* tu2bg...@gmail.com [2011-09-15]:
> # For external lookups
> $ymllookup_datadir = "/etc/puppet/manifests/extdata"
> $ymllookup_precedence = ["node/%{fqdn}", "location/%{location}",
> "role/%{hitwise_role}", "common/common"]
>From the error message I guess that features/yaml/testnode.yaml defines
* denmat [2011-09-12]:
> The issue here is that class roles::prod_webserver doesn't expect to
> be passed any values, but there is a bunch of ymllookups that pull
> values in from local yaml files. This causes errors when it complains
> about either invalid parameter (which it is in the above examp
* Lars Kellogg-Stedman [2011-07-29]:
> I am trying to place some sanity checks (currently as git pre-commit
> hooks) in our configuration repository to avoid committing invalid
> Puppet configurations.
This is exactly the use case for cucumber-puppet. It compiles your
catalog, catching any syntax
* Yushu Yao [2011-06-10]:
> I will need to verify if the services are up after the puppet catalog
> is applied.
I made a habit of setting up nagios checks for all my services. If you
don't have monitoring, I suggest using something like cucumber-nagios to
specify intended behaviour, i.e. service i
* denmat [2011-06-07]:
> Where would I add/replace see this code? What does it do?
cucumber-puppet does not yet deal with storeconfigs and as the warning
is harmless, I suggest you just silence it by raising the loglevel in
your Scenario:
Given I use storeconfigs
HTH,
Nikolay
--
"It's
* Tim Coote [2011-06-01]:
> I'm trying to work out the best way to use Puppet to control an
> existing estate, and then how to refactor the configurations. I'd like
I don't believe there to be a best way, it depends on your situation.
When I introduced puppet at our company, I chose to start from
* hai wu [2011-03-20]:
> I am interested in the details using cucumber-puppet to verify catalog
> compilation. Could you please elaborate on it?
I setup a catalog policy that applies to all catalogs, by specifying a
scenario for each of our servers like so:
@node
Given a node spec
* Giovanni Bordello [2011-03-20]:
> How do you guys test puppet changes before they go live?
We have several lines of defense:
1) we develop our puppet manifests on a development machine where we can
test many changes locally
2) we use cucumber-puppet to verify catalog compilation for all our
serv
* Scott [2010-12-29]:
> I'm looking for additional information regarding Puppet and Hudson.
I blogged about our company's puppet setup here:
http://blog.nistu.de/Continuous_Integration_for_Puppet.html
Since that post I wrote cucumber-puppet, allowing me to implement some
kind of automated test s
* Dustin J. Mitchell [2010-12-28]:
> I'm having a hard time figuring out how best to develop and test
> changes to Puppet manifests.
Depending on the meaning of "test changes to Puppet manifests",
cucumber-puppet might be of interest. It allows you to specify test
cases and verifies catalog behavi
* Matt Wallace [2010-10-20]:
> I've not gone down the cucumber-puppet root as I'm not 100% sure how
> it works and how to write stories correctly so if anyone can point me
> at a good resource on this, I'd be very appreciative!
I have put up some documentation at
http://projects.puppetlabs.com/pro
* Oliver [2010-09-14]:
> What mechanism is there (or is needed) in order to make
> cucumber-puppet aware of the environment (or at least modulepath)
> settings?
The environment is just another node fact. As long as you don't use yaml
node files, you can set it in hooks.rb or in a Given step:
@fac
On Aug 27, 4:04 am, bonobo wrote:
> Our firewall environment is very restrictive, and there's no way a
> server on our publicly accessible network will be allowed to initiate
> a connection to a puppet server on our internal network.
Another option would be to replicate your puppetmaster into you
Hi,
I have a weird problem of puppet mixing up resoure properties when it
comes to installing packages, leading to situations where clients
might want to install some package with a version of "root" or some
other bad value:
Fri Jul 16 17:38:03 +0200 2010 //nautilus-actions/Package[nautilus-
acti
On Apr 18, 3:23 am, James Turnbull wrote:
> Wow. Awesome. Only comment I'd make - and it's more a suggestion than
> a critique - is that it'd be great to be able to bundle the features
> inside modules to aid in portability.
Yes, that makes sense. Thanks!
cheers,
Nikolay
--
You received thi
Hi,
I'd like to announce a little tool I have written, called cucumber-
puppet. It supports writing behavioural tests for your puppet
manifest, using cucumber. This allows for BDD-style manifest
development and fearless refactorings.
http://blog.nistu.de/cucumber_puppet_0_0_3_released.html
Let m
On Apr 15, 10:12 am, David Schmitt wrote:
> There is --splay
Which doesn't help at all. When I tested it with 0.24.8, it would
delay the initial run randomly, but successive runs would start
relative to puppetd's startup, excluding the delay. Haven't look
whether this is fixed in 0.25 or if there
On Apr 14, 11:35 am, Dick Davies wrote:
> I'm getting a lot of 'connection reset' errors all of a sudden on our
> 0.24.8 puppetmaster.
> I'm assuming that's a load issue?
Probably, I had the same problem recently and solved it by serializing
puppetd runs. It works by restarting my puppetd process
22 matches
Mail list logo
