-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opennebula_service
should support role scale operation
#553
Comments
The role scale feature is currently supported in OpenNebula >= 6.8.0, please refer to OpenNebula/one#5591.
The role scale feature is currently supported in OpenNebula >= 6.8.0, please refer to OpenNebula/one#5591.
This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days. |
This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days. |
The role scale feature is currently supported in OpenNebula >= 6.8.0, please refer to OpenNebula/one#5591.
Adds support for OneFlow service scaling at cardinality changes. The role scale feature is currently supported in OpenNebula >= 6.8.0, please refer to OpenNebula/one#5591.
Description
OneFlow service instances support role scaling, but currently Provider does not, changing role cardinality forces resource recreation. There seems to be no code in the Provider that would use necessary API calls. We'd like to change that, as this is a crucial feature of OneFlow. :)
New or affected resources and data sources
opennebula_service
Potential terraform configuration
References
https://docs.opennebula.io/6.8/integration_and_development/system_interfaces/appflow_api.html#service
https://github.com/OpenNebula/terraform-provider-opennebula/blob/v1.4.0/opennebula/resource_opennebula_service.go#L55
The text was updated successfully, but these errors were encountered: