Launch your instances with autoscaling groups or another orchestration layer and they can self-register with your Chef server using the config/validator from S3.On Tue, Apr 28, 2015 at 4:25 PM, niristotle okram < " target="_blank"> > wrote:hello everyone,I am starting to gather notes to move my servers from a local DC to AWS. Currently in-order to set the http & https proxies, we use a bootstrap template. Now that we are moving to the AWS, i assume we will not be requiring to set this proxies and hence the template can be left aside.The normal "knife ec2 server create" bootstraps the node/instance. To install a specific version of chef-client, i think i should be able to pass the option : --bootstrap-version VERSIONSo apart from specifying a particular chef-client version to be installed, each time i bootstrap the servers so that they remain consistent across all nodes. is there any other reason that i should have a bootstrap template.I also came accross ths blog: http://awsadvent.tumblr.com/post/37773106407/bootstrap-cfg-mgmt-awswhy is it important to have the client.rb, validator.pem on the S3/anywhere when the same info can be passed from the knife config file itself.
Archive powered by MHonArc 2.6.16.