Sequential creation of Volumes when scaling MachineDeployment

[groundnuty]

In our setup when provisioning a VM on OpenStack, a volume is first created with the image of the OS, from which the VM later boots.

When scaling MachineDeployment, the desired number of OpenstackMachines objects is created at once but regardless of parameters (we use default values):

--openstackcluster-concurrency int       Number of OpenStackClusters to process simultaneously (default 10)
--openstackmachine-concurrency int       Number of OpenStackMachines to process simultaneously (default 10)

the volumes are created sequentially and in turn, the virtual machines are provisioned sequentially as well. The effect is a long time when scaling from a small to a large number of MachineDeployment replicas.

Is this an intended behaviour of CAPO? Can the concurrency of volume creation be increased?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[groundnuty]

I'm glad that this issue was automatically added to the roadmap, but still I would appreciate it if someone commented on it :-)

[mnaser]

@groundnuty I think this might have already been resolved by https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2502

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[groundnuty]

@k8s-ci-robot, please confirm that it was resolved by https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2502