downgrade option, not just upgrade
We should have the possibility to also downgrade droplets, not just upgrade. Sometimes we need a lot of power for some operations, but then we don't for some time, or maybe not at all anymore, so it would be nice to be able to downgrade a droplet, not just to upgrade it.
The current solution is to create a new one with a smaller plan, but this means configuring, installing and doing all that stuff which takes time and is not portable.
You can't downsize a live file system. Have you ever seen a hard drive that can resize on the fly? No you havent.
That's why you have to use snapshot to downgrade.
Really good point! Web badly need downgrade option!
Steve Lawson commented
Addendum to my last comment: The ability to port a snapshot to a new Droplet would, actually, be a great way to transition during a downgrade. The original Droplet could stay live, while the Downgrade Droplet is tested, then change the DNS nameserver records to finalize.
Steve Lawson commented
Or, how about a way to port a snapshot to a new Droplet (with, perhaps, a warning to the User that this will only work if the Droplets have the same architecture profile.
I like the idea of being able to downgrade but lets say if i upgraded my hard disk and then downgraded, would i loose data? Also i like the idea of being able to upgrade/downgrade via the api.
I agree about downgrade option, as far as it (as upgrade) only touch the CPU and RAM.
Resizing (down) filesystems implies to front with corner cases, file mounts, etc...
Alex Cardinell commented
What there really should be is a "slow resize" option which might take a little longer but allows you to upgrade/downgrade to any size.
That way there are less steps and less frustration when you have to do a real upgrade/downgrade that the fast upgrade option doesn't support.
Jeffrey A. commented
Currently you need to create a Snapshot, destroy and recreate... I second this.
Eugene ElJefe Cook commented
I think part of the issue is that upgrades don't actually change the amount of allocated space you receive, which is incredibly annoying. So downgrading would essentially mean free space.
Even if it was just an button that automated the shutdown - > snapshot -> deletion -> recreation from snapshot with the same IP.
yeah.. I agree.. I do upgrade and downgrade depends on usage. can we please get this option?
Rori Stumpf commented
To downgrade by creating a snapshot and then using it to create a new droplet doesn't make sense either - the IP address will be different, right? That's not a downgrade, that's a new droplet/"host".
Why is it possible to downgrade in my account? Is that because it's a very new account?
Georges Chitiga commented
If we could downgrade using the API the same droplet that would be awesome because we could use a script that checks the resources, if there is a spike the script would upgrade the droplet, if spike is gone then the script would downgrade.
We could start big projects on small droplets, once the project grows automatically it will resize the droplet to make sure it has everything it needs.
Stephen Punwasi commented
The correct way to downgrade would be to take a snapshot of your droplet, and boot up a new instance with your snapshot. Shouldn't be anything else to it.
If i remember well that was an option in the past but now i see its gone. It was a great option.. i used it to go from 512mb to 1gb then 2gb(ram) and then i downgraded back to 1gb because it was better (my usage was lower) . Please DO do it back.
Simon W commented
It would have a new IP though, would it not?
Robin J. commented
It's not that much hustle to make a backup, boot up a new droplet and select the backup in question, destroy the old one?