What you really needed to do was design algorithm that keeps machines running over period in time, according to a general trend. Not shutdown, and instantly bootup for every customer deciding to run tests.
What you really needed to do was design algorithm that keeps machines running over period in time, according to a general trend. Not shutdown, and instantly bootup for every customer deciding to run tests.
I'm glad they found a solution which seems to work out really well for their use case. Changing the algorithm to use the machine for an hour would imply that some tests may wait to be run, and that could be a bad thing for TestingBot (I'm not sure what their SLA is).
Going to their own "cloud" though will require them to either overbuy capacity or eventually make a push to increase utilization, so they may end up making that algo anyhow.
There is another situation, which I would argue is the "enterprise" situation, where you will want to pay your programmers to make the changes because they're fixed overhead rather than capital expenditures. This scenario comes because of an internal push to save money (adding significant capacity costs too much), or because adding any sort of capacity increases operational complexity more than it increases code complexity. It's a much larger scale than where TestingBot is at, but a problem they probably hope to encounter one day.
I'd much sooner have a clean VM to run my tests on than have to think about the ways the previous user might have left things in an insecure state.
Not a Google shill by the way - I don't have a preference yet. However, for that particular complaint, Google has the solution.
Or so I remember from reading the ToS yesterday.
The command-line cloud utility is so much easier than Amazon's. Everything is in one place. ssh keys are managed automatically. In less than 1 hour I was able to do everything with Google, whereas it took me a couple days to feel comfortable with AWS.
http://weblogs.asp.net/scottgu/archive/2013/06/03/windows-az...
In what way?? I mean thsi honestly.
We use linux vms on azure with no problems at all. What non-msft tech stacks doesn't it "play well with"?
From my reading, azure seems to be pretty awesome as far as integration with visual studio, but is seriously lacking when it comes to features on their load balancer etc. Their security model is kinda weird too, where defaults open your firewall to the rest of azure commonly.
So that's just my ideas, what are your experiences?
have you seen AWS opsworks?
Fortunately there is also another side of Microsoft. A side which is doing fantastic work in the open source community as well as with things like the Linux support in Azure. I would be happy to talk more about Linux support in Azure and I am more than capable of helping out with any setup required, regardless of your operating system of choice.
If you're still interested, you can reach me at tistrimp@microsoft.com