| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 574 |
Sorry, something went wrong.
| UniqueNameSearch = createSearchBuilder(); | ||
| UniqueNameSearch.and("name", UniqueNameSearch.entity().getUniqueName(), SearchCriteria.Op.EQ); | ||
| UniqueNameSearch.and("system", UniqueNameSearch.entity().isSystemUse(), SearchCriteria.Op.EQ); | ||
| UniqueNameSearch.and("system_use", UniqueNameSearch.entity().isSystemUse(), SearchCriteria.Op.EQ); |
There was a problem hiding this comment.
As it will be used more times in this class, could it be extracted to a variable?
Sorry, something went wrong.
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 281 |
Sorry, something went wrong.
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 305 |
Sorry, something went wrong.
|
@harikrishna-patnala a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-1020)
|
Sorry, something went wrong.
|
Trillian test result (tid-1019)
|
Sorry, something went wrong.
| ProvisioningType provisioningType, boolean localStorageRequired, boolean offerHA, String tags) { | ||
| tags = cleanupTags(tags); | ||
| DiskOfferingVO diskOfferingVO = new DiskOfferingVO(name, displayText, provisioningType, false, tags, false, false, false, true); | ||
| diskOfferingVO.setUniqueName("Cloud.Com-" + name); |
There was a problem hiding this comment.
is this prefix "Cloud.Com-" required or offerings ?
Sorry, something went wrong.
There was a problem hiding this comment.
Here we are splitting the service offering and disk offering, so using the same name for both offerings.
Sorry, something went wrong.
There was a problem hiding this comment.
Post upgrade, the existing service offerings and related disk offerings have the same name. While creating a new service offering, this prefix may not be required. what do you think?
Sorry, something went wrong.
There was a problem hiding this comment.
Is this just for default offerings?
Sorry, something went wrong.
There was a problem hiding this comment.
Yes @rhtyd
Sorry, something went wrong.
|
Trillian test result (tid-1021)
|
Sorry, something went wrong.
There was a problem hiding this comment.
@harikrishna-patnala can you please provide more details on this PR goal?
The PR's description does not help at all:
Description
This PR...
Types of changes
PS: I understand that this PR is a Draft. If you plan to enhance the PR description before making it ready-to-review please ignore my comment.
Sorry, something went wrong.
There was a problem hiding this comment.
looks promising @harikrishna-patnala , thanks for picking this up.
You know I'm going to ask you to factor out the bits that you touched when done, right ? ;)
Sorry, something went wrong.
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2294 |
Sorry, something went wrong.
|
@harikrishna-patnala a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-3016)
|
Sorry, something went wrong.
There was a problem hiding this comment.
@harikrishna-patnala does this requires any additional testing after fixing the merge conflicts?
Sorry, something went wrong.
|
@borisstoyanov those are very minor conflicts with resizeVolume UI form (only one line), which I've already verified after rebasing. I don't think additional testing is required. Thanks for asking. |
Sorry, something went wrong.
|
ok great! |
Sorry, something went wrong.
|
Last round of smoketests LGTM |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Currently, our compute offerings and disk offerings are tightly coupled with respect to many aspects. For example, if a compute offering is created, a corresponding disk offering entry is also created with the same ID as the reference. Also creating compute offering takes few disk-related parameters which anyway goes to the corresponding disk offering only. I think this design was initially made to address compute offering for the root volume created from a template. Also changing the offering of a volume is tightly coupled with storage tags and has to be done in different APIs either migrateVolume or resizeVolume. Changing of disk offering should be seamless and should consider new storage tags, new size and place the volume in appropriate state as defined in disk offering.
more details are mentioned here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Compute+offering+and+disk+offering+refactoring
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?