Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Sending Heat Scale URLs to Instances

Hello,

I have set up Heat with the autoscaling capability, and I'm wondering how I would go about sending the scaleup and scaledown URLs to the instances for inside-the-os alarming. In order to create the autoscalinggroup, you must have all parameters for the instance template. In order to have all parameters, you must have the scale URL webhooks to pass to the instance template. And in order to make the scalingpolicies, you must have the autoscalinggroup ID. I don't see a way to do this via the template without having circular dependencies. Any thoughts?

~RP

Sending Heat Scale URLs to Instances

Hello,

I have set up Heat with the autoscaling capability, and I'm wondering how I would go about sending the scaleup and scaledown URLs to the instances for inside-the-os alarming. In order to create the autoscalinggroup, you must have all parameters for the instance template. In order to have all parameters, you must have the scale URL webhooks to pass to the instance template. And in order to make the scalingpolicies, you must have the autoscalinggroup ID. I don't see a way to do this via the template without having circular dependencies. Any thoughts?

~RP

UPDATE:

I've found away around this apparent issue. I created some scripts to go to the REST API and pull the URLs from my stack via the output fields. This would be a script injected to the instances by Heat and run continuously. Here's my next problem, if you're following this: Personality Limit for File Injection by Heat

Sending Heat Scale URLs to Instances

Hello,

I have set up Heat with the autoscaling capability, and I'm wondering how I would go about sending the scaleup and scaledown URLs to the instances for inside-the-os alarming. In order to create the autoscalinggroup, you must have all parameters for the instance template. In order to have all parameters, you must have the scale URL webhooks to pass to the instance template. And in order to make the scalingpolicies, you must have the autoscalinggroup ID. I don't see a way to do this via the template without having circular dependencies. Any thoughts?

~RP

UPDATE:

I've found away a way around this apparent issue. I created some scripts to go to the REST API and pull the URLs from my stack via the output fields. This would be a script injected to the instances by Heat and run continuously. Here's my next problem, if you're following this: Personality Limit for File Injection by Heat