Skip to content
This repository was archived by the owner on Mar 25, 2021. It is now read-only.
This repository was archived by the owner on Mar 25, 2021. It is now read-only.

heat stack-update and scale-in/scale-out #126

Description

@alonsocamaro

In general we need that our heat resource types support the stack-update operation. This is needed to fix failed stacks otherwise they have to be left stale in the system. I understand updating all the resource types requires a major effort.

On the other hand, stack-update is also needed to allow for scaling-in/scaling-out services (typically changing the number of pool members). This is a must have operation which we cannot do currently.

From my point of view allowing stack-update operations on the F5::Sys::iAppService resource type should be on top of our list.

Regards

   Ulises

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions