https://github.com/bcoca/ansible/tree/vsphere_inventory
I'm working on the same.
--
Brian Coca
Stultorum infinitus est numerus
0111011100100110010101101110001001110111011000010110011101010010011100110110110101110111001001110111
Pedo mellon a minno
--
You
First question -- yep!
Second question --
Suppose you defined in inventory a group named DebianUbuntu that had
child groups Debian and Ubuntu. The child group variables would override
the parent.
I'm not sure of any fact that is producing a group called DebianUbuntu
but theoretically if you
I realized how easy it would be to test the precedence so I did so, and
yes, the order you run the group_by is the factor that determines which var
wins.
That is way simpler... I'll try rewriting some stuff that way and see if it
feels any less flexible. Thanks again!!
On Wednesday, January
That was a stack overflow post I created, I’ve been trying to figure out for
the last 3 weeks why I couldn’t check out a project (R/W) from github using
Ansible.
Finally, I started taking Vagrant apart to figure out how it’s ssh behaviour
differed from Ansible’s, that was where I got to.
Having played with this a little more I am having concerns about how the
cron module works when a similar line already exists.
For example, if I want to change an existing line in a crontab to modify
the parameters to the command what is the best way to do that?
The most effective way on
Those are good points. I guess the challenge is how much time are you
willing to spend when running playbooks to compute sha/md5's of files on
disk? If we are OK spending that time, then we could just as easily have
the conditionals do that. I was looking at the file module to see what
The logic in question is here:
https://github.com/ansible/ansible/blob/devel/lib/ansible/runner/action_plugins/group_by.py#L90-L92
I'd assume the hosts that matched the group_by and weren't already in the
group just get added to the group?
More like: the group is added to the host based on the
err, ignore that last sentence, you were correct. I'm cross-eyed from
looking at code all day
On Wed, Jan 8, 2014 at 2:01 PM, James Tanner tanner...@gmail.com wrote:
The logic in question is here:
No worries. Thanks for finding that; I'll have to get more familiar with
the source.
On Wednesday, January 8, 2014 1:02:57 PM UTC-6, James Tanner wrote:
err, ignore that last sentence, you were correct. I'm cross-eyed from
looking at code all day
On Wed, Jan 8, 2014 at 2:01 PM, James
Op woensdag 8 januari 2014 14:48:56 UTC+1 schreef Michael DeHaan:
Excellent,
Both vcenter and vsphere together would be ideal.
It also works on standalone ESXi hosts as far as I can see. (Just tried
it).
We're seeing increased interest in folks of having VMware inventory
lately, I
On Wed, Jan 8, 2014 at 4:05 AM, Brian Coca brianc...@gmail.com wrote:
Once this is stable my next step was going to be to try and get the
provisioning plugins from ansible-provisioning project into core.
Hi Brian, I wrote the vsphere_guest[1] ansible module in the
ansible-provisioning repo.
I hit the wrong reply option previously. Sorry for the duplicate in
private, Brian.
I see this pretty rarely. It's normally the length of the file in bytes.
I think we're overthinking this. I had originally suggested to William that
comparing the timestamps and length would be a super
Hi Gregory,
Currently the tags are OR operations.
Ansible would probably endorse a syntax of --tags mysql:configure to
match the host specs, but again, currently just or.
(There's a feature ticket somewhere for making this support a syntax like
our host specifiers -- if it does, --list-tasks in
Brian,
Are you sure that's true of os.stat() and not just the shell commands?
Seems like it would not be.
I think I'm ok with adding a bytes= parameter if we can get around this
question.
On Wed, Jan 8, 2014 at 2:59 PM, Chad Scott csc...@appdynamics.com wrote:
I hit the wrong reply option
thanks for the speedy reply !!
On Wed, Jan 8, 2014 at 4:47 PM, Michael DeHaan mich...@ansibleworks.com wrote:
Hi Gregory,
Currently the tags are OR operations.
Ansible would probably endorse a syntax of --tags mysql:configure to
match the host specs, but again, currently just or.
(There's
What do you have so far? Maybe we can move you further along by seeing an
example playbook or some pseudo code.
On Wed, Jan 8, 2014 at 10:35 AM, Marko Lisica titelskib...@gmail.comwrote:
So what I am trying to do is register variable after change has been made
and notify flowdock handler to
If you are getting a traceback and have instructions for us to reproduce,
please file a bug or make a pull request.
On Tue, Jan 7, 2014 at 2:49 PM, Jonathan jclayba...@gmail.com wrote:
Resurrecting this thread in case other Ansible users encounter this again.
I encountered this on one of my
I've been burned by this before, stat is supposed to return the size of the
file in bytes.
I haven't really checked in a long time as I've grown accustomed to not
rely on size for file comparisons, but my issues stemmed from some
tools/implementations using # of blocks * block_size to measure the
18 matches
Mail list logo
