Skip to content
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

capacity-manila: consider ResourceDemand when splitting capacity/usage between shares and snapshots #464

Merged
merged 2 commits into from
May 22, 2024

Conversation

majewsky
Copy link
Contributor

Checklist:

  • If this PR is about a plugin, I tested the plugin against an OpenStack cluster.
  • I updated the documentation to describe the semantical or interface changes I introduced.

1. Nobody is using these subcapacities right now.
2. Having them split like this would make the change in the next commit
   extremely painful.
@coveralls
Copy link

coveralls commented May 21, 2024

Coverage Status

coverage: 79.459% (-0.1%) from 79.557%
when pulling 82886ef on capacity-manila-by-demand-2
into 7613787 on master.

The CapacityBalance is only used for capacity and usage that is not
covered by a suitable demand.

This got a bit more complicated than I expected because the demand
applies to overcommitted capacity, so the demand numbers need to be
converted back into the respective raw numbers first.
@majewsky majewsky force-pushed the capacity-manila-by-demand-2 branch from 4214588 to 82886ef Compare May 22, 2024 08:33
Copy link
Member

@SuperSandro2000 SuperSandro2000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doesn't look horrible

@majewsky majewsky merged commit be3c2db into master May 22, 2024
7 checks passed
@majewsky majewsky deleted the capacity-manila-by-demand-2 branch May 22, 2024 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants