[CLOUDSTACK-10039] Adding IOPS/GB offering#2231
Conversation
|
Could you resolve the conflict @syed ? |
d4ea9d1 to
4b94afb
Compare
|
@wido I've resolved the conflicts. I am still trying to see if I can get the DB changes to be idempotently added. However the way Cloudstack reads the db script is really weird. Right now its a WIP |
971decb to
2de3b1b
Compare
ACS CI BVT RunSumarry: Link to logs Folder (search by build_no): https://www.dropbox.com/sh/r2si930m8xxzavs/AAAzNrnoF1fC3auFrvsKo_8-a?dl=0 Failed tests:
Skipped tests: Passed test suits: |
|
@syed can you fix the conflicts? |
|
@syed ping |
2de3b1b to
12bd5e8
Compare
|
@rhtyd Sorry Rohit, looks like this slipped out of my radar. I've rebased and resolved the conflicts. |
12bd5e8 to
047e83b
Compare
|
@syed looks like we have new conflicts |
|
darn it! I'll resolve it now |
047e83b to
455ecf1
Compare
|
@rhtyd Done! |
|
Cool feature. Recently have thought about it. |
|
@syed can you fix the conflicts? |
|
Ping @syed |
455ecf1 to
3c95160
Compare
|
@rafaelweingartner I've resolved the conflicts. I'd really like to get this in because I think this is the 3rd time rebasing it. If you could do a code review, that would be sublime :) |
rafaelweingartner
left a comment
There was a problem hiding this comment.
@syed thanks for the PR, but we need to work on it.
Can you check some of my inquiries?
| DROP PROCEDURE IF EXISTS `cloud`.`ADD_COLUMN_TO_TABLE_IDEMPOTENT`; | ||
|
|
||
| DELIMITER // | ||
| CREATE PROCEDURE `cloud`.`ADD_COLUMN_TO_TABLE_IDEMPOTENT`( |
There was a problem hiding this comment.
Isn't this being introduced by some other PR?
There was a problem hiding this comment.
No. This is only for this PR
There was a problem hiding this comment.
Hmm.. Then, I think it is better to coordinate with PR #2449.
| throw new InvalidParameterValueException("Cannot set Min/Max IOPS/GB for a fixed size disk offering"); | ||
| } | ||
|
|
||
| if ((isCustomizedIops != null && isCustomizedIops) || minIops != null || maxIops != null) { |
There was a problem hiding this comment.
Can you use BooleanUtils here?
| "custom IOPS or fixed IOPS"); | ||
| } | ||
|
|
||
| if (minIopsPerGb != null && maxIopsPerGb != null) { |
There was a problem hiding this comment.
Could you extract this block to a specific method? Document it, and write unit tests for it?
| } | ||
| } | ||
|
|
||
| if (highestMinIops != null && highestMaxIops != null) { |
There was a problem hiding this comment.
This whole validation block can also be extracted to a method, documented and unit tested.
| newSize = volume.getSize(); | ||
| } | ||
|
|
||
| newSizeInGb = newSize >> 30; |
There was a problem hiding this comment.
Let's not use bit shift here. It makes things harder to read and understand.
The code is already convoluted enough
| newSize = newDiskOffering.getDiskSize(); | ||
| } | ||
|
|
||
| newSizeInGb = newSize >> 30; |
There was a problem hiding this comment.
bit shift...
Have you checked if there is a library to convert between these bases? If there is none, what about we create an utils method to execute this job?
| @@ -0,0 +1,324 @@ | |||
| -- Licensed to the Apache Software Foundation (ASF) under one | |||
| -- or more contributor license agreements. See the NOTICE file | |||
There was a problem hiding this comment.
these scripts should not be here, right?
|
@syed Hi, do you continue to manage this PR? I think it's very beneficial for 4.12. |
|
@syed is it useful for solidfire? Is there any progress in this pr? |
|
This is indeed useful for solidfire. No progress yet because we are waiting
on the hardware on our lab to be setup and ready to use
…On Thu, Dec 6, 2018, 12:46 PM Sven Vogel, ***@***.***> wrote:
@syed <https://github.com/syed> is it useful for solidfire? Is there any
progress in this pr?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2231 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADaLlT8S9ckTd1WE12pOXPf3mtZVxyaks5u2YIrgaJpZM4OxR9y>
.
|
|
@syed I will move this to 5.0.0. The freeze date is coming, and it does not seem that we will be able to add it to 4.12.0. |
|
@rhtyd @syed @DaanHoogland moving this to 4.15. Still pending review and fixing conflicting files. |
|
@syed this is an interesting feature; Do you intend to continue managing this PR? |
|
I think that this PR is no longer necessary due to PR adding support for IOPS burst #3133. |
|
Hi @syed can you please confirm if this PR is still needed or can be closed by PR3133? In case it is, is it ready for review? |
|
Hi @nvazquez Sorry for the delayed response. #3313 is different from this PR. The idea here is to give the operator the ability to expose storage offerings in the style AWS gp2/gp3 where IOPS scales with size. I currently don't have a setup to work on this but would be happy to support if someone picks it up |
|
Thanks @syed this will need some effort and resolving many conflicts. Do you think you can pick this up sometime soon? Otherwise we can move it for the next milestone |
|
Probably good idea to move to next milestone
…On Fri, Jul 16, 2021 at 11:28 AM Nicolas Vazquez ***@***.***> wrote:
Thanks @syed <https://github.com/syed> this will need some effort and
resolving many conflicts. Do you think you can pick this up sometime soon?
Otherwise we can move it for the next milestone
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2231 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAANULU6WE5GA5WEDAFC66DTYBF3VANCNFSM4DWFD5ZA>
.
|
|
Hi @syed thank you for your PR, given the inactivity in the last 4+ years, I'm closing this. If you happen to work on this feature and can fix conflicts pl re-open or re-raise the PR. |
Types of changes
We want to add a disk offering where we can specify the Min/Max IOPS as a function of size. The idea is the larger volume you create, the greater your IOPS will be (this is similar to the way GCE handles IOPS). We also have added limits to the IOPS (min and max) so that once the volume goes beyond a certain size, the IOPS won't change and are capped to the given values.
The following parameters are added to the
createDiskOfferingAPI:maxiopspergb: Maximum IOPS/GB for the offeringhighestminiops: The highestminiopsvalue that is allowed for this offeringhighestmaxiops: The highestmaxiopsvalue that is allowed for this offering