Need option to suspend servers to save money
With EC2, I can make have a virtual machine that I only turn on when I need it. I only pay for disk space, and don't have to pay operating costs when it's off. EC2 is the only cloud provider with this feature, which is very useful for me.
Thanks to everyone for their feedback on this feature request, and my apologies for our delay in posting an update. I am moving this feature to our Next Gen Cloud Servers category, as suspend is a feature that we plan to offer with that product versus our First Gen Cloud Servers. To address the request for being able to suspend a Cloud Server instance, we plan to roll out a multi-phased solution. The first phase will introduce reserved IPs, which will allow you to snapshot an instance to Cloud Files, reserve the IPs, and terminate the instance. Once you are ready to begin using the instance again, you’ll be able to provision it with the same IPs and data as the original instance. The second phase will introduce additional performance enhancements to optimize for server build times, which when combined with reserved IPs, will give you faster restore times when you decide to un-suspend your instance. We hope to publish a timeline for both of these phases soon, but I can tell you today that they are both on our 2013 Cloud Servers roadmap. Please use the comments section below to provide us any additional feedback regarding this plan or if you have any questions regarding the approach.
Eric Martindale commented
This says it was in the 2013 Cloud Servers roadmap, but there haven't been any updates to this to reflect changes to said roadmap -- and there's not much time left in 2013.
> We hope to publish a timeline for both of these phases soon, but I can tell you today that they are both on our 2013 Cloud Servers roadmap.
What's the latest status on this issue?
"We hope to publish a timeline for both of these phases soon, but I can tell you today that they are both on our 2013 Cloud Servers roadmap"
Not long left in 2013...any news?
Owen Blacker commented
Is there any advance on when this functionality might be available? It would definitely be useful to have this ability.
Dean Malmgren commented
This would be really great and be useful for automated tools like vagrant to be able to halt machines that are not in use (https://github.com/mitchellh/vagrant-rackspace/issues/25)
David Roux commented
Christopher, any word on the timeline for this feature? I am grateful that it is in the 2013 release calendar. With more than half the year gone, I'm wondering whether its release is imminent. Any indication would be greatly appreciated!
Tim Lasonde commented
I am a new customer and would have thought that this functionality was available day one. my plan was to use the cloud servers as development and training boxes. there is no need to have them running when there is no development or training. please add this functionality ASAP. I will have to use EC2 for now.
Alan Leahy commented
thanks Christopher, I am aware of this however, in situations where one would want to shutdown a server (peroids of low activity, weekends, etc) it seems like a drastic option to have to delete the server and recreate it. At times we have had issues with creating new servers so i would be hesitant to delete a portion of my cloud server farm as it would be a huge problem if we were unable to recreate it.
A better solution would be to have the ability to suspend the server and reduce the cost of it and then bring the server back online at a later time\date.
Alan - as a RackConnect customer, you can already use the feature detailed at http://www.rackspace.com/knowledge_center/article/using-dedicated-load-balancers-with-rackconnect to manage load balancer pool membership. Combining this with the existing snapshot/image capability and adding/deleting servers as needed should allow you to achieve a similar goal, as you don't have a requirement to maintain a public IP.
(As an aside, if you did need to maintain public IPs with RackConnect, you could use: http://www.rackspace.com/knowledge_center/article/rackconnect-auto-nat-feature)
The suspend feature being discussed here will initially assist with maintaining public IPs, and over time will provide benefits in terms of server provisioning times (at which point it may make sense to look into as a RackConnect customer).
If you have additional questions about this in the context of your environment, please reach out to your Support team, or feel free to email me directly (christopher <dot> kuehl <at> rackspace.com).
Alan Leahy commented
Hi Chistopher, will this functionality be available to RackConnect customers?
I am extremely keen to implement cost saving funcitonality like this. I would like the ability to suspend a number of our cloud servers during peroids of low activity on our platform.
We don't use the public IP's provisioned with cloud servers today. We route traffic to these devices via our F5 load balancer. If we were to suspend cloud servers and then resume their operation at a later date I would like to either maintain the private IP on the cloud server or the RackConnect solution should have a process that will update the VIP on the F5 that the cloud server is a member of with the new IP of the suspended server.
I hope these comments are useful.
+1 for Reserved IPs, Instance Suspend
Thanks for the improvement.
Is there a current plan and scheduled release date for this feature?
Michael Woffenden commented
I desperately need an alternative to: create image, delete server, recreate server.
The main issues with image/delete/recreate are:
1) It takes too long
2) It involves too many steps
3) I need to be able to preserve the IP address between re-creates
Therefore, want I really want is to be able to "pause" a server. Sort of like hibernate. During the pause period charges would be suspended.
Please implement this valuable feature soon! It would be great for customers and also provide Rackspace with a competitive advantage.
Bron Fieldwalker commented
This one is a MASSIVE make it happen, I hate having to constantly delete test servers, and restore them. Simple suspend with same charges as cloud files or something would be good.
Francisco Reyes commented
When deleting VMs that users tell me they don't need anymore I am always nervous about it.
Imaging has the disadvantage that it would loose the IP if brought back and would have to deal with DNS. With this feature, as long as it keeps the IP, I would be able to suspend the VM for hours/days until I see it was truly a valid request and no user(s) are using the machine any more.
I'm asking for the same feature! it could be fantastic! And save a lot of time...
I think this could be really great, not just for Mr. Weichert and my needs, but perhaps even might help Rackspace with load balancing - if somebody really clever can figure out how. My needs, and apparently Michael's are for periodic, high load with nothing in between. My application, and perhaps Michael's does not really care much exactly when it runs, within some broad constraints, so I would be perfectly happy to put the whole create the server, run the thing, mothball the server again process into a queue to happen whenever Rackspace feels like it. I'm thinking the window is maybe 12 hours wide, and definately 6 hours wide. I have no idea if the queue suggestion is practical, but the earkt planning stages of the mothball feature seems like the time to bring it up.
Michael Weichert commented
I'm really looking forward to this. I have an app that needs to be executed once a month, and when it runs it demands a lot of resources so I'm forced to have a beefy cloud server instance up and running all the time.
So we all know the available pool of IPv4 addresses is getting smaller. For those of us load balancing our machines, we don't necessarily need (or want) a public IP on every machine. We would like to be able to a) strip those public IPs off servicenet-only machines and use them in a pool for stuff we do need b) be able to spin a server with Servicenet only ( maybe an advanced tab or a radio button where the public IP option is the default?). Having said that, if I release all my public IPs back to you, having to pay for them again later if I need them elsewhere would be REALLY annoying. So maybe we have the option of as many free public IPs as we have servers?
Erick Baum commented
Jered, why not just image it to Cloud Files and fire it back up when you need it then? Sounds like that's all you need.
Jered Sutton commented
I am fine if the suspend works similar to ec2 where you lose the ip address when the instance terminates.