Skip to content

support for multidisk OVA files #7

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

Closed
wants to merge 15 commits into from
Closed

support for multidisk OVA files #7

wants to merge 15 commits into from

Conversation

abhinandanprateek
Copy link

Signed-off-by: Abhinandan Prateek [email protected]

@borisstoyanov
Copy link
Member

@abhinandanprateek shouldn't this be in the Interoute repo? Can you please move the PR there?

@abhinandanprateek
Copy link
Author

@borisstoyanov AFAIK other than the two FR that @rhtyd is working on, others need to go to master cc @PaulAngus

@borisstoyanov
Copy link
Member

I see @DaanHoogland has created the PR for FR2.6 in the Interoute repo as well, is there any concerns with submitting the PRs from the interoute repo?

Actually what's the strategy on the community submissions? Where do we create PRs and how do we submit them in community?
cc: @rhtyd @PaulAngus @DaanHoogland

@rohityadavcloud
Copy link
Member

@abhinandanprateek @borisstoyanov /cc @PaulAngus

I've implemented the following UI, where in case of multi-disk template (ova) you'll see options to select the disk offering for the data disk template:

screenshot from 2017-04-12 17-46-52

Though this will take away the option to deploy additional data disk with the template. The UI code sort of existed already in the wizard, I found this today and made some changes to the API and the UI to reuse the widget which is a list of checkbox with labels (the data disk name) and the list of disk offerings per data disk.

The params will be passed to the API as follows:
screenshot from 2017-04-12 18-00-13

@rohityadavcloud
Copy link
Member

Additional note: this may need some refining as it does not make sense to me to select a disk offering that has a fixed size where the data disk (template) might already have a fixed size?

@borisstoyanov
Copy link
Member

Hi guys, looks like there are conflicts in the data schema, can we resolve them before jumping into testing please? @abhinandanprateek @rhtyd

@borisstoyanov
Copy link
Member

Hi guys tried building the PR but build failed with

[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:43.636s
[INFO] Finished at: Wed Apr 19 06:17:41 UTC 2017
[INFO] Final Memory: 113M/1448M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project cloud-vmware-base: Compilation failure: Compilation failure:
[ERROR] /jenkins/workspace/shapeblue-centos6-pkg-builder/dist/rpmbuild/BUILD/cloudstack-4.10.0.0-SNAPSHOT/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java:[164,15] error: cannot find symbol
[ERROR] symbol:   variable UUID
[ERROR] location: class HypervisorHostHelper
[ERROR] /jenkins/workspace/shapeblue-centos6-pkg-builder/dist/rpmbuild/BUILD/cloudstack-4.10.0.0-SNAPSHOT/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java:[1662,34] error: cannot find symbol
[ERROR] symbol:   variable UUID
[ERROR] location: class HypervisorHostHelper
[ERROR] /jenkins/workspace/shapeblue-centos6-pkg-builder/dist/rpmbuild/BUILD/cloudstack-4.10.0.0-SNAPSHOT/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java:[1772,16] error: cannot find symbol
[ERROR] symbol:   class FileWriter
[ERROR] location: class HypervisorHostHelper
[ERROR] /jenkins/workspace/shapeblue-centos6-pkg-builder/dist/rpmbuild/BUILD/cloudstack-4.10.0.0-SNAPSHOT/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java:[1772,37] error: cannot find symbol
[ERROR] -> [Help 1]
[ERROR] 

http://build.yadav.xyz:8080/job/shapeblue-pkg-builder/60/
Is this related to the removal of midonet plugin?
@abhinandanprateek @rhtyd

@rohityadavcloud
Copy link
Member

Yes @borisstoyanov I've sent a PR to fix the master/upstream issue

@rohityadavcloud rohityadavcloud changed the base branch from master to 4.9 April 20, 2017 05:36
@rohityadavcloud rohityadavcloud changed the base branch from 4.9 to master April 20, 2017 05:36
importSpecParams.setEntityName(importEntityName);
importSpecParams.setDeploymentOption("");

String ovfDescriptor = removeOVFNetwork(HttpNfcLeaseMO.readOvfContent(ovfFilePath));
Copy link
Member

Choose a reason for hiding this comment

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

@abhinandanprateek I've made this additional change

@abhinandanprateek abhinandanprateek force-pushed the md-ova branch 4 times, most recently from d60e160 to 69b96a3 Compare April 27, 2017 08:25
@abhinandanprateek abhinandanprateek force-pushed the md-ova branch 4 times, most recently from 9960c45 to 42710ca Compare May 8, 2017 08:09
@abhinandanprateek abhinandanprateek force-pushed the md-ova branch 4 times, most recently from 025ff2c to 896b29b Compare May 26, 2017 07:07
@abhinandanprateek abhinandanprateek force-pushed the md-ova branch 2 times, most recently from 961ce01 to bb23562 Compare June 10, 2017 05:35
@DaanHoogland
Copy link
Member

@abhinandanprateek Did you merge back master? I think you better rebase, instead. This is going to look messy.

@abhinandanprateek
Copy link
Author

@DaanHoogland heard ya

@abhinandanprateek
Copy link
Author

moved to community.

Pearl1594 pushed a commit that referenced this pull request Nov 25, 2020
rohityadavcloud pushed a commit that referenced this pull request Jan 20, 2021
Fix various linting warnings and errors in resource and basic layout component.

Signed-off-by: Rohit Yadav <[email protected]>
rohityadavcloud added a commit that referenced this pull request Jan 20, 2021
This implements a work-in-progress VM deployment wizard.

Co-authored-by: Rohit Yadav <[email protected]>
Signed-off-by: Rohit Yadav <[email protected]>
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.

4 participants