[chef] Fwd: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Bring up the discussion for knife-ec2 --node-name-prefix option


Chronological Thread 
  • From: Torben Knerr < >
  • To: " " < >
  • Subject: [chef] Fwd: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Bring up the discussion for knife-ec2 --node-name-prefix option
  • Date: Mon, 22 Oct 2012 08:41:29 +0200


>
> How are people working with these servers that have no useful labels?  I really want to know.  We ssh all over the place in our infrastructure and if I had to go out and look up a special snowflake ec2-blah-blah or IP every time I wanted to get to a server, I'd probably take a baseball bat to my infrastructure.
>
> For example, we run a Jenkins setup with 20 slaves.  The slaves are rebuilt often using openstack and chef.  I'm currently writing a knife plugin to set up ssh aliases for nodes in a role that make it easy for us to do things like 'ssh slave20' as we are constantly helping people figure out stuff about their jobs on the slaves or diagnosing VM issues (I'd actually really like to take a baseball bat to our Openstack infra).
>

I have used Mccloud [1] for exactly that in the last project. We had a fairly small infrastructure, and it was chef_solo, so it doesn't really compare, but it was really a big relief and I would really miss it for that.

Having node tagging with knife-ec2 would be a nice and useful option imho.

[1] https://github.com/jedi4ever/mccloud




Archive powered by MHonArc 2.6.16.

§