"Then I'd have to simply have a separate entry in my ssh config
file for each one?"
Yes, because you just said you couldn't use wildcards :)
+1 to having private hostnames or conventions to make that easier.
On Sun, May 25, 2014 at 11:51 PM, Slim Slam wrote:
> To clarify further -- I know
To clarify further -- I know that I can use wildcards in the ssh config
file like:
Host *.example.com
Host 128.220.19.*
But what if I have a lot of different IP addresses or host names? Then I'd
have to simply have a separate entry in my ssh config
file for each one?
J
On Sunday, May 25, 20
if using the ssh connection plugin, it supports whatever ssh does, so
wildcards should work.
--
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+
So, if a lot of your machines have IP addresses (or very different domain
names) then you'd have
to create an ssh config file entry for each individual IP address, right?
Because there'd be no way
to use wildcards. Am I missing something here?
Example:
Host 33.44.55.66
ServerAliveInterva
"Ansible best practice for handling multiple clusters with a bastion server
for each
cluster?"
Per host settings in your SSH config file.
On Sat, May 24, 2014 at 8:04 AM, Slim Slam wrote:
> Thanks. That got things working. It would be nice if Ansible did some
> basic syntax checking on the cf
Thanks. That got things working. It would be nice if Ansible did some basic
syntax checking on the cfg file. :-)
So if you have multiple bastion files, but no specific domain name you can
wildcard off of (e.g. "Host *.mydomain.com", "Host ".anotherdom.com",
etc), what is the Ansible best p
ssh_args does not go under the [defaults] section. It belongs under a section
titled [ssh_connection]
--
Matt Martz
m...@sivel.net
On May 23, 2014 at 4:53:23 PM, Slim Slam (slimands...@gmail.com) wrote:
Yes. I tried that. No difference. As I mentioned, it's clear that Ansible is
using my ansi
Yes. I tried that. No difference. As I mentioned, it's clear that Ansible
is using my ansible.cfg file. For example, if I set the remote_user in my
ansible.cfg to:
[defaults]
transport=ssh
ssh_args= -F /work/sshconfig
remote_user=dummyuser
Then everything fails because Ansible tries to use
I think what Michael meant was to specify the full path to the sshconfig
file, ie. "-F /path/to/mysshconfig" instead of a relative path.
On Fri, May 23, 2014 at 11:30 AM, Slim Slam wrote:
> FWIW, I got this idea from *you* :-) - reference:
> https://groups.google.com/d/msg/ansible-project/AO
FWIW, I got this idea from *you* :-) - reference:
https://groups.google.com/d/msg/ansible-project/AOt-5fgBzho/hEDnnOrJkC8J
However, I've never seen an implementation of it or a working example
that's been tested. I think someone posted an
example where they had "-F ~/.ssh/config" but since th
That didn't make a difference.
I know that ansible is using that ansible.cfg file because I can put a
"remote_user = xxx" line
at the end of it and ansible uses that.
It would be helpful if someone could simply add "ssh_args= -F sshconfig" to
an ansible.cfg
file and show some output that prove
Hmm.
So that's definitely OpenSSH by default.
Commands to ssh config are arbitrary and are handled here:
https://github.com/ansible/ansible/blob/devel/lib/ansible/runner/connection_plugins/ssh.py#L60
Can you try specifying a full path to your SSH config file? Might be a
case of relative path.
I'm running ansible 1.6.1 on MacOSX 10.9.3. The target systems are CentOS 6.
J
On Friday, May 23, 2014 7:31:58 AM UTC-5, Michael DeHaan wrote:
>
> Ansible will use your SSH config when using the ssh (not paramiko)
> transport, perhaps it's not finding it for some reason.
>
> paramiko would be th
Ansible will use your SSH config when using the ssh (not paramiko)
transport, perhaps it's not finding it for some reason.
paramiko would be the default if you were running from RHEL/CentOS 6 or
before, where OpenSSH is not new enough to support ControlMaster, and
paramiko is therefore still faste
Ansible 1.6.1
I'm trying to set things up so that I can specify a bastion host as a
gateway
to my other machines.
I'd like Ansible to use an SSH config file that I keep in git.
So, I have a file named "sshconfig" with:
Host *
ServerAliveInterval60
TCPKeepAlive ye
15 matches
Mail list logo
