TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: How do you use VMs? From:"Janoff, Steven" <Steven -dot- Janoff -at- hologic -dot- com> To:Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 2 Aug 2016 17:42:44 +0000
Thanks, Chris, this is awesome.
I will definitely check out the site.
I had been thinking about past use of VMs, and present. I see what you mean about what's going on now and it does seem pretty pervasive.
Here's my question: First, I don't have the complicated doc use case that you do. I'm on a 64-bit Windows 7 PC, and I run apps like Flare, FrameMaker, Acrobat, Office, and the "gang of usual suspects" natively.
No DITA, no XML, no CCMS, no fancy-schmancy stuff. Just everyday tech writer apps.
So what can I do in a VM that would benefit me in everyday documentation work?
VMs appear to be a great tool for developing software and then testing in multiple environments.
I suppose you could test documentation in multiple environments but we don't really have that need, that I can see at least. We have some docs that we deliver as HTML5 online help output from Flare (tripane or topnav), then most of the rest are PDFs out of FrameMaker. We do PDF shared reviews out of Acrobat. (Part of my research into this area had to do with latency issues on very large PDFs with huge numbers of comments -- but this is more of an internal server issue although a VM solution would be wonderful if such a thing exists. SharePoint looks like a bust too.)
What would installing/creating/spinning up a VM do for me that would add value to my work?
Thanks for any advice you can give here. I recall coming across your descriptions of your own use case but they are far afield of the much less sophisticated workflow that we're doing.
Steve
On Tuesday, August 02, 2016 4:43 AM, Chris Despopoulos wrote:
DISCLAIMER: I work for VMTurbo, a company that provides Intelligent Workload Management in virtual environments -- Assuring performance of applications while utilizing datacenter resources as efficiently as possible. You can look at our company web site for lots of discussions about VMs. Of course, it's all flavored with our world-view. But that might be helpful -- we view all the resources in a datacenter as a supply chain, and we analyze resource utilization in terms of supply and demand... For machines at least, free-market economics arrive at the most efficient state possible. This metaphor might help you get your head around the issues.
Go to VMTurbo.com Once there, you might log into our social site -- the Green Circle. That's where you can see real-world customers talking about real-world issues.
Anyway, to answer the question directly... You probably use VMs in more ways than you thought. Of course, you can run a VM on your laptop -- for example, that's how you run Windows on a Mac. You might want to dedicate a box to running different OS machines so you can test them out. If you have a web site hosted by a service provider, you're most likely (definitely?) using a VM there. When you google something, you're using a bunch of VMs... Also when you use Yahoo, FaceBook, or any SaS product. The point is, we're increasingly using distributed, hosted applications, and at any scale beyond hobby it's economical to use virtual resources.
Amazon (AWS), Microsoft (Azure), and IBM (SoftLayer) provide VMs on cloud services. You can pay for the servers you need, when you need them. These are just machines you use on the cloud to host your applications. As far as you're concerned, they're physical machines. But they're actually VMs.
What is a virtual machine? A VM is software running on a host that fully emulates a physical machine. It has memory, CPU, network ports, an IP address, etc. Because it's running on a host, its capacity is necessarily a subset of the host's capacity. It can't run faster, can't have more memory, can't have more network throughput, etc. than the host machine. Think of a train... Each car is a VM, and the train is the host machine. Your car can't outrun the train.
Why would you do this? It turns out that hosts can be treated as commodities, where you buy a number of hosts that are all the same and get a volume discount. But for apps, each server might need special configurations. Well, spin up a VM with that configuration -- you don't have to plug in a memory board to allocate its memory capacity... It's just software config. One host can run a number of VMs. If the host gets overloaded, you can move VMs to another host.Â
The host is called a hypervisor. Hypervisors have varying degrees of resource management capabilities built into their OSs. And then there are various platforms to manage the hosts... vCenter Server (VMware), Hyper-V (Microsoft), RHEL (Red Hat), OpenStack, and others. Example... You want 10 VMs on a host -- the host has 100 MB of memory. That means you can only give your VMs 10 MB each, right? Well, you can "thin provision" the VMs because you can assume that not all the VMs will use all their memory at the same time. So you can provision 20 or 30 MB for each VM. The hypervisor keeps track, and knows how much memory to give to each VM. (Ok, this is a WILDLY oversimplified explanation, but the goal is to show some of the advantages of virtualization.) You have more than host resources. With network storage, you manage a couple of things... Where the VM "file" is stored, and there the VM "file system" is stored. By getting storage off the host and onto the network, you're free to allocate more storage than the host has, and you're free to move the VM to a different host without having to move its storage.
Why would you move VMs around? Maybe the host is overloaded (you thin provisioned, and some VM is hogging memory). Maybe the host's network connection is overloaded. Maybe the host is UNDER utilized -- you can move VMs off of it, and onto another host, and then shut down the underutilized host. When you're talking about thousands of VMs on hundreds of hosts, the savings you can realize are significant. For a service provider, or a huge datacenter (like Google), saving pennies per host adds up fast. To make these decisions, you need to know about all the combinations of all the resources -- this outstrips human intellect pretty quickly. This is the problem we solve at VMTurbo, using the supply chain and economic analysis.Â
Finally, our product ships as a VM. I use that VM to host my documentation. Because of that, I can have LOTS of FUN - something I've talked about in other posts. I do love my job.
CheersÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ cud
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
