The default.yaml is in the gist I supplied. I used the el6 and centos6 64
from your sample project.
Taking a look again, its even more confusing than that, the platform
name you have used is pointing at one of the very very old AMI's. The
newer ones we actually use are private, but I don't
I was just testing the host config file from puppetdb coupled with the
documentation on the beaker documentation.
Those docs honestly look old, they are still mentioning blimpy which I
effectively deprecated/superseded with the aws_sdk driver.
I was actually going to omit the error
That's great Ken.
I'll have a look. My .fog file was correct but I was missing that
ec2.yaml.
I get the user experience thing, it'll evolve and I'll help if I can.
Would I be right to assume you built your images with packer?
All of those images predate packer, but we're using packer
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
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
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
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.
I was just testing the host config file from puppetdb coupled with the
documentation on the beaker documentation.
Those docs honestly look old, they are still mentioning blimpy which I
effectively deprecated/superseded with the aws_sdk driver.
I was actually going to omit the error message.
On Mon, Oct 6, 2014 at 6:44 PM, Ken Barber k...@puppetlabs.com wrote:
I was just testing the host config file from puppetdb coupled with the
documentation on the beaker documentation.
Those docs honestly look old, they are still mentioning blimpy which I
effectively deprecated/superseded
