3 ms·
If you have a server farm that allocates VMs dynamically on demand, you have something much different than a dedicated server, and it is quite reasonable to cal
by dpark 13y ago
If you have a server farm that allocates VMs dynamically on demand, you have something much different than a dedicated server, and it is quite reasonable to call this a private cloud.
- asdasf 13y agoExcept people were doing that long before the "cloud" marketing nonsense started,
- sp332 13y agoWell they needed something to counteract the dusty image of the term "mainframe".
- dpark 13y agoYou just don't like the word "cloud" at all, and that's fine, but that is a different complaint from the original, which was basically that the term is being misused when combined with the term "private". If we are going to use the term "cloud" and assign it a meaning, we can certainly use it to refer to private clouds. If EC2 is a cloud for me, is it not also a cloud when Amazon builds services on it?
- michaelt 13y agoIf we're going to assign a meaning to the term 'cloud', shouldn't we assign it to something we don't already have a word for, so it actually describes something? If I start two VMs on my desktop and we call that a 'cloud' then the word 'cloud' isn't terribly useful in describing anything.
- arethuza 13y agoWorth noting that "cloud" was also used to describe private MPLS networks: http://en.wikipedia.org/wiki/Multiprotocol_Label_Switching http://en.wikipedia.org/wiki/Multiprotocol_Label_Switching
- dpark 13y agoI don't think the accepted definition of "cloud" is just "group of VMs". Your two VMs does not constitute a cloud. You can set up ten thousand VMs on a thousand servers and not have anything that would reasonably be considered a cloud if you did it manually. "Cloud" generally implies simplicity and automation. You could build a cloud with physical machines instead of VMs so long as you have automatic ways to allocate and manage the machines' lifecycles.
- asdasf 13y agoI have no problem with the word cloud. I have a problem with it being used to mean "anything I call cloud". If we are going to use the term and assign it a meaning, then lets assign it a meaning instead of using it for everything from "webmail" to "virtual machines" to "paying someone else to do something for me".
- dspillett 13y agoPeople were making out of band HTTP requests long before the irritating term AJAX was coined too. The name being made up after the method started being used does not mean the method can't be called the name if the properties fit (likewise as much as the marketers think otherwise, making up a new name doesn't make a thing technically revolutionary!)
- dec0dedab0de 13y agoAgreed, except that your internal documentation can't abstract away all the infrastructure. At least for the company as a whole.
- revelation 13y agoNo, thats ridiculous. You are still paying for all the servers in the server farm, even if you have decided to waste another year of Moores law to add a bulky abstraction layer on top. The whole point of a cloud to a business is that you can adapt to changing needs without having to pay for all the infrastructure all the time. (You didn't think the suits talk about "the cloud" all the time because they fancy the technology, right?)
- dpark 13y ago> You are still paying for all the servers in the server farm Amazon is paying for all the servers in the EC2 server farm. Does that stop EC2 from being a cloud? TestingBot is spinning up VMs dynamically to scale out test infrastructure on demand. Their use case is basically the ideal cloud use scenario. They've built a system of servers that enables them to do all of the things typically associated with clouds, which means they've built a cloud. You're stuck thinking of TestingBot needing a bunch of servers, and seeing the tradeoff as dedicated servers vs cloud servers. In reality, it's TestingBot's customers who need a bunch of servers. So TestingBot built a cloud for their customers. They aren't setting aside N servers for each customer. They're building a cloud with the capacity for X servers and carving out of that on-demand.
- revelation 13y agoYes, EC2 is not a cloud for Amazon. If tomorrow everyone moves away from it, they will be stuck with many millions in sunk costs for hardware, rack space, datacenters, paid peerings.. they didn't rent that stuff by the hour. Feel free to replace Amazon with TestingBot in this description as you see fit, because right now you are confused as to what is a cloud to whom. (Mind you, I'm still only discussing the financial side here, as this was the reason the original post cited. In technical terms, of course they are still a cloud, but so is the mainframe emulator on my Raspberry)
- hhw 13y agoSomebody somewhere always has to pay for the infrastructure. I fail to see how the parent is confused between Amazon having infrastructure which they provide cloud services on, and TestingBot having infrastructure which they provide cloud services on. What's your point of distinction on the 'financial side' between the two exactly?