On Feb 10, 2014, at 9:14 PM, Ritesh Angural <
>">
> wrote:
> 1) Having the chef server itself in the VPC vs having it as a public EC2. Is this a good idea or bad idea?
In my experience, so long as you only ever have just the one VPC, you're fine with having the Chef server on a subnet inside that VPC.
Where I have seen things break in the past is when you have more than one VPC and you have a need to route traffic from one to the other -- like talking to your Chef server.
The "easy" way out of this problem is to put the Chef server out in EC2-land, and not have to try to route from one VPC to another.
I have yet to hear of any solutions to the problem of needing to route from one VPC to another.
> 2) When bootstrapping nodes into VPC via knife-e2, we need to attach elastic ip to the node first.
> (See this post). What's the best way to do this, or how have you done it?
What I have been able to do [0], is to create the elastic IP first, then create the node, and then assign the elastic IP to the node.
[0] By "do", I mean something that I have done manually via the AWS console. I have never tried to do this in an automated fashion, whether with Chef or CloudFormation, or anything else.
--
Brad Knowles <
>">
>
LinkedIn Profile: <
http://tinyurl.com/y8kpxu>