I don't believe so, I'd open a github issue for this so we can keep track
of it.
On Tue, Jun 3, 2014 at 7:05 PM, Jesse Keating
wrote:
> I'm trying to set up some simple validation tests to run on pull requests
> to one of our playbook repos. In doing this I've discovered that
> vars_prompt is s
If you're dealing with any significant number of hosts (ie. more than a
hundred), we generally recommend using a dynamic inventory script of some
kind. Beyond that, the INI syntax doesn't really allow for any includes
unfortunately.
On Tue, Jun 3, 2014 at 8:20 PM, Michael Mahemoff
wrote:
> As I
Hi all,
I was wondering if anyone has a strategy for recording when a playbook has
been run against hosts in an inventory, and crucially which version of the
repository (Git-based, in my case) was checked out when the playbook ran?
Essentially I'd like to maintain a 'version number' for each in
It's really not bad, the "dummy" play just looks like this:
- hosts: all
And that's it, followed by other plays. You can limit it more of course, if
you don't need facts about every system in your inventory, but the setup
step needs to be run on systems to get their facts. However it only needs
t
In a similar situation I simply added a play to the role that stores a version
number as a local fact. Then on subsequent runs I can check that local fact.
The only proviso for that is that it is possible for someone to change the fact
so don't rely on it for anything truly important.
--
You
As far as I can tell, variables passed in as params to includes have never
been merged into the global list of variables (I've gone back to 1.3.0 to
test your example). So I would consider this a bug, if you'd like to open a
github issue for us so we can keep track of this.
Thanks!
On Tue, Jun 3
Is there a way to update the properties of a running ec2 instance?
Specifically, I'd like to add security groups to a running VPC instance.
I've used the ec2 module to create an instance, but once it's running,
adding a security group to the 'group' parameter and re-running the
playbook has no
aws doesn't allow you to change the security group association of a
instance once created, you CAN change the rules of the existing security
group. Ansible cannot give you something that aws itself doesn't support.
--
You received this message because you are subscribed to the Google Groups
"A
Whoa. Maybe I'm misunderstanding you but I add and remove security groups
on instances while running all the time. It would be cool to do that via
ansible.
On Jun 4, 2014 7:41 AM, "Brian Coca" wrote:
> aws doesn't allow you to change the security group association of a
> instance once created, y
But it gets more unwieldy if you're using roles. If my app role needs
to have the IPs for the databases I just have to hope that the
playbook that ends up running the tasks in my play have gathered all
the facts from those other systems. It gets even more
action-at-a-distance when your role is a de
this might have changed, I have not even tried in a good while. This used
to be a restriction, I stand corrected and happy to hear, it was a major
pain.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop r
just double checked aws documentation:
"After you launch an instance in EC2-Classic, you can't change its security
groups. However, you can add rules to or remove rules from a security
group, and those changes are automatically applied to all instances that
are associated with the security group."
ah, VPC instances have different rules, 'classic' is non VPC from what I
can see.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...
True, the dummy boilerplate is small, but it has to precede every playbook.
(I also thought it had to include at least one task to be in effect.)
The main issue is performance. I'm not dynamically provisioning, so these
things never change. I thought maybe there's some trick people are using to
Many thanks for the pointer to that bug. Pulling ansible 1.7 (devel
d9df607972) seems to have cleared the issue and all is working as I had
hoped, so it does look like it was a related issue.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
Yep. that must be the difference. I'm all VPC.
Brent
On Wed, Jun 4, 2014 at 11:28 AM, Brian Coca wrote:
> ah, VPC instances have different rules, 'classic' is non VPC from what I
> can see.
>
> --
> You received this message because you are subscribed to the Google Groups
> "
Yes, you can update an instance's list of security groups if that instance
is in a VPC:
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_SecurityGroups.html
(see "Differences Between Security Groups for EC2-Classic and EC2-VPC")
On Wednesday, 4 June 2014 17:07:39 UTC+1, Brent Langston
PR #7122 has just been merged. It also includes a new module "rax_meta"
for more easily allowing metadata updates on cloud servers.
Both "rax" and "rax_meta" use the improved metadata normalization code.
On Tue, Jun 3, 2014 at 6:26 PM, Matt Martz wrote:
> That issue is fixed in another pull r
I'll create a pull request.
As an aside, updating *any* of the ec2 module parameters will not update
the instance. Which is often in practice is undesirable or impossible,
because most of the parameters would require a restart (think
instance_type, etc). However, 'volumes' is one such parameter
Matt,
Great, meta data is now correctly put into the api call..
However we still are having some problems. Sometimes the script goes faster
then the meta data becomes available:
fatal: [web6] => error while evaluating conditional:
rax_facts.ansible_facts.rax_metadata['rackconnect_automation_st
Hi James,
I've just created a new python virtualenv and installed ansible:
iain@iain-P15xEMx:~/Desktop/ansible$ mkvirtualenv ansible
(ansible)iain@iain-P15xEMx:~/Desktop/ansible$ pip install paramiko PyYAML
jinja2 httplib2
(ansible)iain@iain-P15xEMx:~/Desktop/ansible$ pip install ansible
(ansible
On Wednesday, June 4, 2014 7:28:47 AM UTC-7, Adam Morris wrote:
>
> In a similar situation I simply added a play to the role that stores a
> version number as a local fact. Then on subsequent runs I can check that
> local fact. The only proviso for that is that it is possible for someone to
>
The "|default('')" should handle individual meta data keys not being
available.
I've never seen this happen. You might try running with -v to see what the
calls to rax_facts are returning. rax_metadata should always be present
and should always be a dict.
On Wed, Jun 4, 2014 at 2:03 PM, Jurgen
Hello,
I submitted a pull request for some enhancements to the ec2_asg module
https://github.com/ansible/ansible/pull/7612
This adds a few things:
- More verbose output than just changed:[true | false]. This is useful
if you're registering variables for use later. I found this particularly
Hi Craig,
I think what you're looking for is callback plugins, but you could probably
also use a notification module as well. There are several in Github as
examples. The callback plugin could, for example, record something to a
file, or to a database, or merely make an API call to some custom
a
Hi,
I've got a usecase where I'd like to iterate over several servers based on
groups, so task looks like:
- name: group A & B
shell: echo {{ item }} >> /tmp/log
with_items:
- groups["A"]
- groups["B"]
so what I get in /tmp/log is:
groups['A']
groups['B']
Now, eliminating either grou
On 06/04/2014 04:47 PM, Dmitry Makovey wrote:
with_items: groups["A"]
ansible uses jinga2. Look up that syntax. Then, off the top of my
head, may not be exactly right, but:
groups["A"].concat(groups["B"]) | set | list
Some of that is python syntax(the contact, check jinga2 and python
d
nice try - but no dice:
fatal: [192.168.0.138] => with_items expects a list or a set
FATAL: all hosts have already failed -- aborting
I even played a bit and checked python syntax making it:
groups['A'].extend(groups['B'])|set
with or without last "list" filter with original syntax or with my
thanks to your hint I'm one step closer:
- name: group A & B
shell: echo {{ item }} >> /tmp/log
with_items: groups["A"] + groups["B"]
however I still can't figure out how to make a "set" out of the result.
--
You received this message because you are subscribed to the Google Groups
"Ansibl
You might want to take a look at the 'set' filters provided by ansible at
http://docs.ansible.com/playbooks_variables.html#set-theory-filters
I imagine something like:
with_items: groups['A']|union(groups['B'])|unique
would work.
I doubt it is needed, but you might have to add |list onto the en
Thanks Matt and Adam!
Winning combination turned out to be:
( groups['A']+groups['B'] ) | unique
I do like how simple it looks vs
( groups['A']|union (groups['B']))| unique
since in my case I have more groups to add and it is very simple with "+"
and less error-prone.
--
You received this
Hi Matt, we're currently working on the queue of issues and typically focus
on those that are P1/P2 first. Your PR will be reviewed as soon as
possible, but in the meantime if others want to test it, having more +1's
always helps us get things merged in quicker.
Thanks!
On Wed, Jun 4, 2014 at 3:
Just noticed subnets is in the devel branch but not the 1.6.2 in github, so
looks like i just need to track dev for this!
Thank you,
iain
On Wednesday, June 4, 2014 12:25:05 PM UTC-7, iain wright wrote:
>
> Hi James,
>
> I've just created a new python virtualenv and installed ansible:
> iain
Hi Iain, it does appear that this feature is included in the current
development branch, so to use it you will need to clone the github
repository and install it from that branch. We typically recommend users of
the devel branch source the "hacking/env-setup" script, which makes it very
simple to u
34 matches
Mail list logo
