Ask Your Question
0

Rolling updates with heat autoscaling.

asked 2016-02-08 08:54:46 -0500

anonymous user

Anonymous

I need a solution for rolling upgrades. Basically i want to manually scale up a new instance which will have a new version of software and then gracefully remove the old instance from nova and the load balancer. Could someone point me in the right direction? Is this possible?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
-1

answered 2016-02-09 00:06:37 -0500

To clarify,

  1. In Openstack, autoscaling get triggered only based on Alarm events generated by Ceilometer.
  2. On autoscaling, only identical virtual machines get launched. One way can be like writing custom script in User-Data to fetch the latest application package can be made possible.

Hence Autoscaling wouldn't be best solution for your usecase, may be you can write custom HEAT template to automate the usecase.

edit flag offensive delete link more

Comments

The target are included in a auto-scaling group, and I still need that function. I need to manually trigger upscaling(which can be done with webhooks) then I have as you suggested a custom script that fetch the latest application package. But i need the old instance to be removed automatically.

mountcifs gravatar imagemountcifs ( 2016-02-09 01:28:32 -0500 )edit

Well, we now have the senlin service released with Mitaka. It is a clustering service (http://wiki.openstack.org/wiki/senlin). Requirements like this one can be easily met using senlin now. You can trigger a NODE_UPDATE operation in place, or a ADD_NODE operation followed by a DEL_NODE operation.

Qiming gravatar imageQiming ( 2016-04-08 00:14:57 -0500 )edit
2

answered 2016-02-23 15:44:57 -0500

zaneb gravatar image

Yes, this is possible, but it works using the normal Heat update mechanisms. That is to say, if you make some change to the server properties in the template then it will be updated, and if it can be updated in place (rather than creating a replacement) then it will. So to force replacement like this you need to change some property of the server that will cause it to be replaced (user_data is a good bet).

OS::Heat::AutoscalingGroup will do this update by default, but you can control batching with the rolling_updates property.

AWS::AutoScaling::AutoScalingGroup groups don't do any updates unless you specify the AutoScalingRollingUpdate update_policy (which also allows you to control batching).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-02-08 08:54:46 -0500

Seen: 455 times

Last updated: Feb 23 '16