Re: [ansible-project] Ansible Errors when running Playbook

Looks like you have a corrupted file or are running on a different CPU type (eg 386 vs Arm). On Mon, Apr 17, 2017, 17:40 Anfield wrote: > Getting the following errors - can anyone help? > > Traceback (most recent call last): > File "/usr/bin/ansible-playbook", line

Re: [ansible-project] Support for Cloudformation change sets

Er, I think they are available in boto3 too. On Fri, Sep 23, 2016, 08:11 Ted Timmons <t...@perljam.net> wrote: > Last I looked, changesets were available though the AWS console only. I'd > love to be wrong on this. > > On Tue, Sep 20, 2016, 11:31 Toni Juvani <toni.juv...@i

Re: [ansible-project] Cloudformation Boto3 Update

Stephen - my source cloudformation configs are in YAML, I've always run them through a JSON conversion step. So I'd love to work on this. Perhaps we can take this offlist with anyone else who wants to work on it. On Wed, Sep 21, 2016, 12:41 Stephen Granger wrote: > Did

Re: [ansible-project] Support for Cloudformation change sets

Last I looked, changesets were available though the AWS console only. I'd love to be wrong on this. On Tue, Sep 20, 2016, 11:31 Toni Juvani wrote: > Hi, > > We have implemented our AWS resource stacks using Cloudformation templates > chained using Ansible. Previously the

Re: [ansible-project] Cloudformation module: output json

Tom, it doesn't appear AWS has released "changesets" as an API, it's only in the console. That's the best bet, I think. (Of course, you could save and diff JSON..) On Tue, May 31, 2016, 22:45 Tom De Blende wrote: > Hi all, > > I am looking into deploying AWS

Re: [ansible-project] Deploying Ansible on CoreOS

https://github.com/defunctzombie/ansible-coreos-bootstrap On Thu, May 12, 2016 at 10:10 AM wrote: > Hi, > > Please provide the link incase any document available to deploy ansible on > CoreOS. > > > > -- > You received this message because you are subscribed to the Google

[ansible-project] Re: Ansible 1.9.6 RC1 and 2.0.2 RC3 are available for testing

On Wednesday, April 6, 2016 at 2:04:58 PM UTC-7, James Cammarata wrote: > > * Fixes a bug where a role parameter named 'name' would incorrectly be > used as the name of the role. > > Aha. I thought that was just me. It was a good opportunity to use a better name than name, though. -- You

[ansible-project] a few third-party modules for s3, ec2

I have some custom Ansible modules to scratch my own itches. Two are very significant: - s3enc: get/put s3 files with KMS-based client-side encryption - s3_sync: high-speed s3 uploader https://github.com/tedder/tedder_ansible_library/tree/master/library Enjoy, -ted -- You received this message

[ansible-project] calculating the 'serial'?

I'm trying to calculate a serial number and having trouble. I'm unsure of the jinja filter pipeline. Here's what I'm trying: serial: {{play_hosts|length|float/2|round(0, 'ceil')|int}} here's the error: ValueError: invalid literal for int() with base 10: {{default(length(play_hosts),