- From:
- To: chef <
>
- Subject: [chef] hostnames hit by knife ssh
- Date: Wed, 5 Dec 2012 00:31:07 -0800
hi. recently i noticed when i use knife ssh, the hostnames in the output
are the EC2 public dns hostnames, which i guess is
node['ec2']['public_hostname']. it didn't used to do that. knife ssh
used to spit out node['fqdn'].
tho i haven't confirmed by sniffing traffic, i'm assuming knife ssh
is hitting my nodes using node['ec2']['public_hostname'] as opposed to
node['fqdn']. my desired behavior is for knife ssh to hit node['fqdn'],
which is the private name on RFC-1918 space, because we are ceasing
allowing ssh from the internet in our EC2 security groups.
today, undesired:
[oberon chefdev]$ knife ssh "bender_role:app AND chef_environment:fry" 'uname
-m'
ec2-17-2-59-33.compute-1.amazonaws.com x86_64
ec2-23-23-2-20.compute-1.amazonaws.com x86_64
ec2-23-21-77-23.compute-1.amazonaws.com x86_64
ec2-174-129-90-16.compute-1.amazonaws.com i686
in the past, desired:
$ knife ssh "bender_role:app AND chef_environment:fry" 'uname -m'
webapp04.bender.fry.com x86_64
webapp01.bender.fry.com x86_64
webapp08.bender.fry.com x86_64
admin08.bender.fry.com i686
anyone know how this changed? or how i can get the behavior of knife ssh
hitting node['fqdn']?
today i'm using knife from chef 10.16.2. in the past, i don't know
which version it would've been.
thanks in advance,
kallen
- [chef] hostnames hit by knife ssh, kallen, 12/05/2012
Archive powered by MHonArc 2.6.16.