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

Astimp:Downgrade the SSD Size when creating vm from backup #7

Open
ranjithamca opened this issue Apr 21, 2017 · 2 comments
Open

Astimp:Downgrade the SSD Size when creating vm from backup #7

ranjithamca opened this issue Apr 21, 2017 · 2 comments
Assignees

Comments

@ranjithamca
Copy link

Description of your issue:

To downgrade the SSD Size when creating vm from backup

Expected behaviour

Actual behaviour

Steps to reproduce the issues

creating new Vm from backup -downgrade SSD from 25GB to 10GB ( if the client wisch to downgrade they service how can we do that?? )
NOTE: If you are experiencing a deploy failure, please include:

-Link to the failed deployment. We'll use the administrator id to impersonate and debug.

  • Any logs as per troubleshooting
  • Upload screenshots if there is an error reported in the userinteface.
@indykish
Copy link
Member

If the original VM has a size of 60GB then the backup will be 60GB.

The current UI allows the customer to launch using 10GB but the launch will fail since the original image size is 60GB.

We'll check if the base backup image saved can be reduced in size.

@jaeko44
Copy link

jaeko44 commented Jul 3, 2017

To mitigate users running into errors in this case,

If a user selects a VM Size that is Lower than Backup Size, then VirtEngine must create a label in the launcher noting:

'Since your backup image is XXGB, while your selected plan only includes: XXGB of Storage - the VM launched will include XXGB of Storage added to your VM. Cost = $0.XX/hour, $XX/mo'

Then we automatically resize the plan to the required storage on launch.

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

No branches or pull requests

4 participants