Re: Live load balancing node AMI Swapping

From: Rajat Banerjee <no email>
Date: Wed, 25 Oct 2017 12:48:16 -0400

Hi Cody,
I don't see why not. I haven't touched the load balancer code in a few
years. But from my memory, it reads the config file on startup whenever you
run `starcluster loadbalance starcluster-name` and will pick up the new AMI
then. So if you kill the last loadbalance process, swap the AMI in the
config file, then restart, the load balancer should begin adding the new
AMI. The new AMI must be compatible with starcluster obviously, and be
ready for starcluster and SGE bootstrapping. This is easy to verify by
simply using it to start a new cluster as a test.

Give it a try and let us know?
Best,
Raj

On Wed, Oct 25, 2017 at 12:32 PM, Colby Taperts <
colby.taperts_at_codewilling.com> wrote:

> Hello,
>
> Would it be possible to change the node AMI after the StarCluster is up?
>
> for example, use the below setup to initialize the StarCluster
>
> master_image_id = ami-0330d16a
> master_instance_type = m1.small
> node_image_id = ami-0330d16a
> node_instance_type = m1.small
>
>
> then change the config to:
>
> master_image_id = ami-0330d16a
> master_instance_type = m1.small
> node_image_id = ami-0111111 # New AMI name
> node_instance_type = m1.small
>
> Start `starcluster loadbalance starcluster-name`
>
> and have the new node AMI created when a node is needed
>
> Or would I need to destroy the cluster if I need to set up the new AMI?
>
> Thanks so much!
> -Colby Taperts
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
Received on Wed Oct 25 2017 - 12:48:51 EDT