Ask Your Question
0

autoscale two instances in two different stacks

asked 2017-03-08 03:45:31 -0600

samah gravatar image

updated 2017-03-08 09:15:20 -0600

zaneb gravatar image

I have tested the autoscaling process it works but there is somthing that I can't understand: I have tow different stack wich have autoscaling process but when I stress an instance from one of them the alarm of the instance in the other stack is also triggered and autoscale work also in the other stack why?

edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
3

answered 2017-03-08 08:36:23 -0600

Bernd Bausch gravatar image

updated 2017-03-08 08:38:44 -0600

Alarms are triggered per project. Extra work is required to ensure the alarm is only delivered to a specific stack.

In this stack, instances get a metadata item metering (line 79). The alarm property matching-metadata then links the alarm definition to those instances (lines 127, 140). See the text starting at line 206.

edit flag offensive delete link more

Comments

finally it works thanks

samah gravatar imagesamah ( 2017-03-08 09:18:02 -0600 )edit

Great. And sorry that I didn't notice that we had talked about this before.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-08 21:48:49 -0600 )edit

It's not a problem when you had talk about this last time I didn't know that I must use it to avoid this problem but now I understand it

samah gravatar imagesamah ( 2017-03-09 01:50:11 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2017-03-08 03:45:31 -0600

Seen: 133 times

Last updated: Mar 08 '17

Related questions

is ther anyway to mark an instance as unhealthy?

Sending Heat Scale URLs to Instances

how to setup dynamic resource allocation?

How can Heat gracefully shutdown a server when scaling down?

heat multi cloud

disable cloud-init's network setup from Heat template

PROBLEM: Authentication cannot be scoped to multiple targets

heat not recognizing keypair

outputs from nested template

Mount multiple cinder volumes to VM via heat