[Puppet Users] Re: Beaker 3 to Beaker 4 migration for puppet modules.

Hi, Yesterday 0.3.9 of puppet-module-gems was released. This adds Beaker 3 as a dependency for system tests. The added dependencies have upper bounds to prevent future major releases of those gems from affecting modules. The Puppet supported modul

[Puppet Users] Re: beaker gem vs rspec spec/acceptance ?

On Tue, Feb 16, 2016 at 11:00 AM, Brett Swift wrote: > It's the spec_prep that is failing, so even bundle exec spec won't work. > Just an FYI: the spec* rake tasks are controlling and setting up lower level unit tests using "rspec-puppet"[1] while the task to run acceptance tests with beaker-rs

[Puppet Users] Re: Beaker and mock services

I agree with the other comments, start with RSpec, where you can easily mock things, then move on to acceptance testing. The reason you cannot easily mock things with acceptance testing is that currently Beaker is executing Puppet Apply on a piece of code and then using Serverspec to check over

[Puppet Users] Re: beaker

Beaker people hang out in #puppet-dev on freenode irc - there are more docker experts there (an area that I can't be very helpful in). We have also recently created a 'puppet beaker' group: https://groups.google.com/forum/#!forum/puppet-beaker alice. -- You received this message because you

[Puppet Users] Re: beaker

There's an issue filed for our vagrant centos6 boxes not working with beaker: https://github.com/puppetlabs/beaker/issues/702 It looks like the same state that you are hitting. Could you attempt on centos5 or another platform? alice. -- You received this message because you are subscribed t

Re: [Puppet Users] Re: beaker test fails to resolve "agent" roles, works if role is master/database

On Thu, Oct 30, 2014 at 12:03 AM, Manish Sapariya wrote: > Josh, > Thanks for the clarification. > > Now that I look closely at the Beaker wiki I see call as "on agents "do > something" > > For some reason I missed and assume that "on agent" should work. > > I think confusion was from this sample

[Puppet Users] Re: beaker test fails to resolve "agent" roles, works if role is master/database

Yes kevin, I am using acceptance tests using beaker-rspec. beaker (1.19.1) beaker-rspec (3.0.0) By the way, now that Josh clarified I understand why agent did not work. Thanks for sparing time though to look at the problem. :-) Regards, Manish On Tuesday, October 28, 2014 11:57:07 PM UTC+5:30

[Puppet Users] Re: beaker test fails to resolve "agent" roles, works if role is master/database

Josh, Thanks for the clarification. Now that I look closely at the Beaker wiki I see call as "on agents "do something" For some reason I missed and assume that "on agent" should work. I think confusion was from this sample from wiki = manifest = "fi

[Puppet Users] Re: beaker test fails to resolve "agent" roles, works if role is master/database

Hi Manish, I'm having some trouble reproducing the problem that you're seeing. This is working for me with the tests given using generic beaker, although I'm using a different hypervisor at the moment. Are you using beaker-rspec and the modules acceptance tests? Thanks, Kevin On Tuesday, O

[Puppet Users] Re: beaker test fails to resolve "agent" roles, works if role is master/database

On Tuesday, October 28, 2014 2:10:11 AM UTC-7, Manish Sapariya wrote: > > Hi, > I have the nodeset definition as follows.. > > -- Some of the attributes removed for clarity > -- > HOSTS: > kpointvm1.zencite.com: > roles: > - master > hypervisor : vagra

[Puppet Users] Re: beaker & vCloud

Thanks Scott, Yes very helpful. Unfortunately I'm not sure if I'll be able to get the right access to our vSphere. I only have a vOrg in vCloud to play with. I saw a video from Hunter (hunner), where there's a video (http://club.black.co.at/log/posts/2014-05-24-beaker/) and at the 39th min

[Puppet Users] Re: beaker & vCloud

Hi Brett, The vCloud settings seem a bit confusing to me. I've integrated only > briefly against the http API for vCloud, and these settings of "datastore" > "resourcepool" and "folder" seem to be vSphere specific. First of all, I'm obliged to point out that "vCloud" is a misnomer here -- it