-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CLOUDSTACK-8894: Restrict vGPU enabled VMs dynamic scaling if new service offering has different vGPU type #868
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
Conversation
|
cloudstack-pull-rats #692 SUCCESS |
|
cloudstack-pull-analysis #642 SUCCESS |
|
@anshul1886 Can you add a bit of a description here. |
|
@Runseb Updated the bug description. I am looking into travis tests. This test will require vGPU enabled hosts with different type of GPU cards. |
|
@Runseb It seems like simulator does't have support for vGPU. If I find some time then I will try to add support for it. |
| } | ||
| } | ||
|
|
||
| // Check resource limits |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @anshul1886,
Could you extract the codes between lines 1541 - 1549 to a method with an auto described name, do some test cases to this new method and create a Javadoc explaining what the method do, what params it receive, the exceptions it throws and what can cause the exception?
Ty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pedro-martins I would prefer it this way for readability.
|
@anshul1886 please rebase against latest master and push -f, update on status of your PR |
ACS CI BVT RunSumarry: Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 Failed tests:
Skipped tests: Passed test suits: |
…vice offering has different vGPU type
8c00e44 to
f9f0e50
Compare
|
@rhtyd, Rebased against latest master. |
ACS CI BVT RunSumarry: Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 Failed tests: Skipped tests: Passed test suits: |
|
Code LGTM. Just curious to know, Do we support upgrading/downgrading the stopped VM with different vgpuTypes on XS. |
| + ",memory=," + currentMemory + ")"); | ||
| } | ||
|
|
||
| _offeringDao.loadDetails(currentServiceOffering); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a bit of improvement, before loading, we can check if the value is already loaded then we can skip this, else load it. Something like this.
if(currentServiceOffering.getDetails() == null) {
_offeringDao.loadDetails(currentServiceOffering);
}
Same for newServiceOffering.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nitin-maharana This check will be redundant as there is no place where details are getting set in variable's lifetime.
|
@nitin-maharana Yes we support upgrading/downgrading the stopped VM. But both service offerings should have same vGPU type as that is currently not supported. |
|
There were outstanding comments on this PR which were not addressed and the PR was merged :( |
Co-authored-by: Rakesh Venkatesh <[email protected]> Signed-off-by: Rohit Yadav <[email protected]>
It fixes the bug https://issues.apache.org/jira/browse/CLOUDSTACK-8894.
Steps:
1.Install and configure XenServer 6.5 with vGPU enabled . Enabled dynamic scaliing
2. Deploy VM using K160Q type windows 7 template with PV tools installaed and dynamic scaling enabled
3. Tried dynamic scaling with offering which has K180Q defined.
Observation:
Expected Result:
Dynamic scaling should be restricted when source/destination offering has vGPU type on a vGPU enabled VM