Script Automation
I am assuming that the timeout is due to the fact that one would leave a machine on as a server to which to connect to.
One nice middleway/option to add would be the possibility to have the machine not going in standby, but disconnect network only instead. Sometimes I have processes that take a couple of hours and it would be amazing to launch them at the office, don't think about it, and then in the evening at home check them.
Paying an "always on" fee is a bit much for this luxus, maybe a lower fee could be set for "machine on, network off".
-
Andrea,
Thank you for your post. Actually the primary reason for suspend is the cost of running environments. In order for us to offer environments at the flat monthly fee we do, we can't allow them to keep running. An environment which runs for a full monthly would exceed our base pricing in operations costs and opportunity hardware costs. The reason we offer the AlwaysOn feature is for individuals who need their virtual machines to run constantly, but still for development and testing purposes. And today this is the only option. What we will offer in the future is scheduling that will allow you to schedule resume time for your VMs. This may be a solution for you.
The point you raise about scripts is very interesting. I will discuss this with the team. We have some ideas around how to handle these situations, but have not formalized an answer. For this reason, I will mark this request as planned because I think we will have a solution other then always running VMs to handle unmanned running scripts.
Chris
-
Andrea,
No problem! The idea we are thinking about is called "My Automation". it would allow you to upload applications, scripts etc. to CloudFolders and have you run them against existing or new virtual machines in an environment, unmanned. How does that sound? I will probably rename this request to "Scripting automation" to get votes.
Chris
Please sign in to leave a comment.
Comments
5 comments