I was just testing the host config file from puppetdb coupled with the documentation on the beaker documentation. I was actually going to omit the error message. That's actually all of it except for the json output of the compiled beaker configs. I can send the full output in the morning.
It looks like the Google Compute Engine docs are more complete... It doesn't matter where it runs. Mostly looking for a free tier cloud to get started with. I'm not sure aws micro would even be big enough anyways. But it'd be cool to get it working. Thanks Brett Sent from my iPhone On Oct 6, 2014, at 19:13, Ken Barber <k...@puppetlabs.com> wrote: >>> I've seen how the puppetdb module uses ec2 to execute beaker tests. I've >>> tried setting this up as well and am getting some errors. >>> >>> Is there a working example of using the different hypervisors? >>> >>> I see this: >>> https://github.com/puppetlabs/beaker/wiki/Creating-A-Test-Environment#ec2-support >>> but the documentation doesn't suggest it's a polished feature :) >>> >>> It might be helpful to document a project that has an example of all the >>> hypervisors, as each one will have different required / optional parameters >>> in the nodeset configuration file. >>> >>> Indented below is the error when running `beaker --hosts >>> spec/acceptance/nodesets/ec2-west-el6-64mda-el6-64a.cfg` - I pulled that >>> example from the puppetdb project, and as per the documentation have a .fog >>> file set up.. I was hoping to get an authentication or configuration error >>> on first run. >>> >>> Beaker::Hypervisor, found some ec2 boxes to create >>> Failed: errored in CLI.provision >>> #<TypeError: no implicit conversion of Symbol into Integer> >>> /Projects/live_modules/puppet-shawlib/.bundle/ruby/2.1.0/gems/beaker-1.19.1/bin/beaker:6 >>> /Users/bswift/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15 >>> /Users/bswift/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15 >>> >>> >>> I don't have much to go on there.. >> >> The exception seems a little truncated, is that it? BTW Instead of >> annotating what has happened in a paragraph, just provide the full >> example in your shell in a gist or something, it says the message much >> more simply :-). Sort of like this: >> https://gist.github.com/kbarber/97f45eba0f922497901a. Or better yet, >> if you can create a repository with the basics of the above so I can >> take a look that would be much much easier. >> >> I must warn you, the aws_sdk.rb code was written in a massive hurry, >> and thus has very little error protection so if everything isn't spot >> on, it might break. > > FWIW also - I wouldn't test the state of the puppetdb module testing > pieces, we've been waiting for our QA & Module teams to automate those > tests for a about a year now :-(. But honestly, they haven't been ran > for quite some time - so I'd be dubious. > > The PuppetDB source code itself (ie. puppetdb server, not the module) > however does use the AWS EC2 test stuff, and thats a better example to > use. > > ken. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/AzcyYneW820/unsubscribe. > To unsubscribe from this group and all its topics, 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/CAE4bNT%3DgHWf5zD3j8GD8%2BYXsf5HCwYPvSXcH2Veka2O2_b5w_w%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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/7D366F34-582B-4B85-9276-04DA77A7A7E4%40gmail.com. For more options, visit https://groups.google.com/d/optout.
