Some preview content about System Center Virtual Machine Manager Beta 1 concepts:
Microsoft System Center Virtual Machine Manager 2007 is a standalone server application used to manage a virtualized datacenter running Microsoft Virtual Server 2005 R2. Virtual Machine Manager is tightly integrated in the System Center family of products, and together these products provide comprehensive management of physical and virtual environments.
For Beta 1, you will install Virtual Machine Manager Server, the Virtual Machine Manager Administrator Console, and the Virtual Machine Manager Self-Service Portal on a single, dedicated server. The server must have at least a 2 GHZ processor, 2 GB of RAM, and 20 GB of free disk space.
Beta 1 customers have access to the beta newsgroups through Microsoft Connect. Product team members monitor this newsgroup and respond on a best-effort basis during business hours: Monday–Friday, 9:00 A.M.–5:00 P.M. Pacific Standard Time (UTC-8).
Virtual Machine Manager interfaces
Virtual Machine Manager provides several interfaces to enable managing a virtualized data center. The administrator console is a windows application that provides full management capabilities. The self service portal is a web interface that exposes limited functionality for workload administrators to manage their VMS. Both of these interfaces are built on the Windows PowerShell Command line interface provided by Virtual Machine Manager.
Virtualization is commonly used in test and development environments to enable frequent provisioning and teardown of virtual machines. These tasks are easier with virtual machines than with physical hardware. Virtual Machine Manager allows administrators to delegate these tasks to users. The user is presented with a Web page that enables virtual machine provisioning within preset controls.
A virtual machine host is a physical computer that hosts one or more virtual machines. Hosts that have been added to Virtual Machine Manager are known as managed computers. Until you add a host, you cannot create virtual machines, and many of the actions in the administrator console are not available.
A virtual machine is a computer within a computer, implemented in software. A virtual machine runs on a virtual machine host, and emulates a complete hardware system, from processor to network card. Virtual machines typically consist of one or more .vhd files, a .vmc file, and other properties. A virtual machine managed by Virtual Manager Machine can be in one of two basic states: "placed" on a host or "stored" in the library.
Placement is the selection of a virtual server host for a particular virtual machine. Any time you want to put a virtual machine onto a host, you will go through the placement process. Virtual Machine Manager will provide host ratings which indicate the suitability of the host for a specific virtual machine. The rating is calculated based on CPU utilization, memory utilization, physical disk space, disk utilization, and network utilization and takes into account:
The ratings are from 0 stars (not suitable) to 5 stars (very suitable). Placing a virtual machine on a host with a higher rating will provide better performance for the virtual machine. You may place a virtual machine on a host regardless of the rating as long as the host has enough physical disk space available.
In Virtual Machine Manager, the library stores all resources that are used to create and manage virtual machines—including virtual machines that have not been assigned to a host, templates, hardware profiles, guest operating system profiles, ISOs, and scripts.
The library is a management construct in the Virtual Machine Manager database. The database keeps track of the library server, the library shared folder, and the library objects. You can use library objects to create new virtual machines. Library object include:
A task is a job in Virtual Machine Manager that changes the state of a resource. Most tasks are composed of a series of steps. An administrator can manually restart a task, but cannot choose the step from which the task is restarted. For example, adding a host, starting a virtual machine, and adding an object to the library are all tasks.
A checkpoint enables an administrator to roll the virtual machine back to its state at the moment the checkpoint was created. Checkpoints are portable; when a virtual machine is migrated from one virtual machine host to another, the checkpoints migrate along with the virtual machine.
TechNet Scripting Center
VMM on Microsoft.com
This week there has been intensely interesting conversation on a-mail about some of the new innovation at the company: sofware and services. This article in Wired talks about a new theory about two kinds of people that drive innovation.
"Conceptual innovators,” as Galenson calls them, make bold, dramatic leaps in their disciplines. They do their breakthrough work when they are young. Think Edvard Munch, Herman Melville, and Orson Welles. They make the rest of us feel like also-rans. Then there’s a second character type, someone who’s just as significant but trudging by comparison. Galenson calls this group “experimental innovators.” Geniuses like Auguste Rodin, Mark Twain, and Alfred Hitchcock proceed by a lifetime of trial and error and thus do their important work much later in their careers. Galenson maintains that this duality – conceptualists are from Mars, experimentalists are from Venus – is the core of the creative process. And it applies to virtually every field of intellectual endeavor, from painters and poets to economists.
I wonder what type is driving Microsoft now, as opposed to the 90s? What type does the "industry" need? I see hand waving about companies that start with a G grabbing up the C.I.s, is that a bad thing neccessarily if what we need and what we have are E.I.s?