Bases: heat.openstack.common.service.Service
Listen on an AMQP queue named for the engine. Allows individual engines to communicate with each other for multi-engine support.
Respond affirmatively to confirm that the engine performing the action is still alive.
Stop any active threads on a stack.
Bases: heat.openstack.common.service.Service
Manages the running instances from creation to destruction. All the methods in here are called from the RPC backend. This is all done dynamically so if a call is made via RPC that does not have a corresponding method here, an exception will be thrown when it attempts to call into this class. Arguments to these methods are also dynamically added and will be named as keyword arguments by the RPC caller.
The abandon_stack method abandons a given stack. :param cnxt: RPC context. :param stack_identity: Name of the stack you want to abandon.
Verify that the credentials in the RPC context are valid for the current cloud backend.
Return the number of stacks that match the given filters :param cnxt: RPC context. :param filters: a dict of ATTR:VALUE to match against stacks :param tenant_safe: if true, scope the request by the current tenant :param show_deleted: if true, count will include the deleted stacks :param show_nested: if true, count will include nested stacks :returns: a integer representing the number of matched stacks
The create_stack method creates a new stack using the template provided. Note that at this stage the template has already been fetched from the heat-api process if using a template-url.
Parameters: |
|
---|
This could be used by CloudWatch and WaitConditions and treat HA service events like any other CloudWatch.
The delete_stack method deletes a given stack.
Parameters: |
|
---|
Return an identifier for the resource with the specified physical resource ID.
Parameters: |
|
---|
Generate a template based on the specified type.
Parameters: |
|
---|
Get the template.
Parameters: |
|
---|
The identify_stack method returns the full stack identifier for a single, live stack given the stack name.
Parameters: |
|
---|
The list_events method lists all events associated with a given stack. It supports pagination (limit and marker), sorting (sort_keys and sort_dir) and filtering(filters) of the results.
Parameters: |
|
---|
Get a list of supported resource types.
Parameters: | cnxt – RPC context. |
---|
The list_stacks method returns attributes of all stacks. It supports pagination (limit and marker), sorting (sort_keys and sort_dir) and filtering (filters) of the results.
Parameters: |
|
---|---|
Returns: | a list of formatted stacks |
Update the metadata for the given resource. DEPRECATED: Use resource_signal instead
Simulates a new stack using the provided template.
Note that at this stage the template has already been fetched from the heat-api process if using a template-url.
Parameters: |
|
---|
Return the schema of the specified type.
Parameters: |
|
---|
Temporarily set the state of a given watch
Parameters: |
|
---|
Return detailed information about one or all stacks.
Parameters: |
|
---|
The show_watch method returns the attributes of one watch/alarm
Parameters: |
|
---|
The show_watch method returns the datapoints for a metric
Parameters: |
|
---|
Cancel currently running stack update.
Parameters: |
|
---|
Handle request to perform a check action on a stack
Handle request to perform a resume action on a stack
Handle request to perform suspend action on a stack
The update_stack method updates an existing stack based on the provided template and parameters. Note that at this stage the template has already been fetched from the heat-api process if using a template-url.
Parameters: |
|
---|
The validate_template method uses the stack parser to check the validity of a template.
Parameters: |
|
---|
Bases: object
Periodic task, created for each stack, triggers watch-rule evaluation for all rules defined for the stack sid = stack ID
Bases: object
Define a periodic task, to be run in a separate thread, in the stack threadgroups. Periodicity is cfg.CONF.periodic_interval
Run the given method in a sub-thread.
Run the given method in a sub-thread and release the provided lock when the thread finishes.
Parameters: |
|
---|
Try to acquire a stack lock and, if successful, run the given method in a sub-thread. Release the lock when the thread finishes.
Parameters: |
|
---|
Stop any active threads on a stack.