6 ms·
You didn't abandon "the cloud", you just switched providers. You're still paying someone else for servers that you don't own (unless softlayer ships you those
by jedberg 15y ago
You didn't abandon "the cloud", you just switched providers.
You're still paying someone else for servers that you don't own (unless softlayer ships you those machines after 3 years).
This is why I hate the term "the cloud" -- because it is too nebulous and non-descriptive.
- papercruncher 15y agoCloud implies running in virtualized environment. Dedicated implies that only your bits run on that hardware which is huge for I/O.
- jedberg 15y ago> Cloud implies running in virtualized environment. Dedicated implies that only your bits run on that hardware which is huge for I/O. True, but the blog post didn't say if they are using virtualization or not.
- TimH 15y agoSo they may or may not have abandoned the cloud?
- jedberg 15y agoAlso, you don't necessarily take a huge hit in I/O with virtualization. VMWare on dedicated hardware with all the virtualization extensions will be pretty comprable and a lot easier to maintain then straight up raw iron.
- chime 15y agoAnd ESX with VMotion & DRS can make sure you still get good I/O even when parts of the hardware get congested or even offline.
- spydum 15y agoTo be fair, this is only true if the storage back end is appropriately configured. You will take an I/O hit when instead of a single physical machine asking for a set of sequential blocks off the disks, you have 20 virtual machines asking for seemingly random blocks off the disks. Replace disks with storage array if you'd like.. but the fact remains: more VM's will mean more storage contention. If you have the funds to have dedicated arrays per VM, hats off to you. Most people never do this, and I/O suffers a penalty. Virtualization has is price, and even that being said, I think it's worth it for most people.
- asharp 15y agoYour point about having multiple VM's forming additional seeks is correct, but it misses the bigger picture. Basically, on any reasonably sophisticated hosting infrastructure those arn't a problem. If your problem is just seq->random conversion due to additional VMs then bcache/flashcache does a surprisingly good join at making that just plain go away with little additional cost. On any reasonably sophisticated host you have a DSAN, which has a cool little stats trick, which basically means that as you add additonal vm's together the variance on the total IO load drops, and the load pattern itself becomes more and more normal, the larger and more uncorrelated you get. That gives each vm more 'burst' capacity when required with many fewer failures (ie. the vm asks for more IO then the current capacity of the system). This leads to a bunch of interesting stuff when you try to apply it in real world systems, either in HPC or in clouds.
- chime 15y ago> Cloud implies running in virtualized environment. Unfortunately, 'cloud' implies nothing. Apple's iCloud isn't necessarily storing my data using VMs and EBS/BigTable type FS. They could be using dedicated W2K/IIS 4.0 boxes storing BLOBs in MSSQL and still be considered cloud by everyone.
- icebraining 15y agoVIrtualized doesn't mean VMs. It means you access some computing service, where the backend is abstracted away - effectively, virtualized.
- twsted 15y agoI do not agree with this. Cloud is often a confusing term but it is not strictly bound to virtualization. One can imagine a cloud offer with dedicated hardware.
- jules 15y agoIs that because multiple instances will be running with the same disk? As far as I know virtualization doesn't have a big overhead in itself, or does it?
- asharp 15y agoNot for most situations. I work over at orion, and our standard cloud VM's dominate dedicated hardware in IO. There really isn't much competition. You find most of the 'virtualisation is bad for I/O' is either 'oversold I/O is bad for io' or 'Trying to push all IO for every VM on a box as well as all WAN traffic through one gigE port is bad for io'.
- umjames 15y agoThis is why I hate the term "the cloud" -- because it is too nebulous and non-descriptive. Actually, nebulous means cloud-like. Would you prefer the older term "the grid"? They're all just items for buzzword bingo.
- jedberg 15y agoI hate all the terms because they are all buzzword lingo. :)
- skeletonjelly 15y agoYou've just lost your synergy jedberg.
- jedberg 15y agoI realize I use the buzzword on my linkedin. I may hate the term, but I still have to play the game, right?
- startupcto 15y agoAnd you are a cloud expert as per your LinkedIn profile.. _, .--. ( / ( '-. .-=-. ) -. / ( .' . \ \ ( ' ,_) ) \_/ (_ , /\ ,_/ '--\ `\--` _\ _\ `\ \ _\_\ `\\ \\ -.'.`\.'.- Nice .... .... ...
- larrys 15y ago"it is too nebulous and non-descriptive" Agree but wouldn't you say that sole use of physical hardware (whether or not you own or lease that hardware and regardless of physical location) is really the issue that separates cloud from non cloud? Example: We have servers that we own in our offices. We have servers that we own in colocation. We have some dedicated virtual servers at MT http://mediatemple.net/webhosting/dv/ http://mediatemple.net/webhosting/dv/ I consider the MT servers cloud since the hardware is shared. And what we are paying for is simply memory, transfer and disk space. I don't even know what hardware we are running on there and I don't know anyone else that is running on that hardware either. But I would also consider the servers in the office and the colocated servers non-cloud even if they were leased (which they are not).
- whalesalad 15y agoI wouldn't consider the (mt) servers 'cloud', but rather just as you said it, shared. I too hate the cloud term, for reasons mentioned above (by jread).
- jread 15y agoInfrastructure as a service (IaaS) cloud generally implies a few distinguishing features such as hourly utility billing and no long term commitments, rapid elasticity (provision/de-provision in minutes, not hours) and usually (but not always - there are bare metal clouds) virtualization. People often refer to software as a service (SaaS) as cloud, which I think is where it starts getting very ambiguous (i.e. is any hosted web application in the cloud???)
- watty 15y agoI used to fight it but it's a lost cause. The cloud is officially a buzzword and can be used to describe any hosted solution.
- richardw 15y agoSame. Anything that isn't actually solely nailed down to your own hard drive is now 'cloud'. I think we need to find terms that marketers don't get excited by, and thus won't 'embrace and extend' to fit their needs.
- nl 15y agoNIST (the National Institute of Standards and Technology) actually has a pretty good (if not exactly short!) definition by listing the characteristics "a cloud" has: http://www.nist.gov/itl/cloud/upload/cloud-def-v15.pdf http://www.nist.gov/itl/cloud/upload/cloud-def-v15.pdf Leasing physical servers could be regarded as "cloud", but usually wouldn't because that method of hosting towards not meeting the Resource pooling, Rapid elasticity and Measured Service (esp "automatically control and optimize resource") characteristics (of course, one can argue that it can do those thing, but generally( it doesn't). "Cloud" isn't* an engineering term, and thinking about it in absolutist, engineering terms makes as much sense as thinking about "web 2.0" in engineering terms 5 years ago.