Skip to main content

Zero configuration virtualization standard

A group of six server builders and virtualisation vendors plans to reveal a new standard to help IT departments automate the installation and deployment of virtual machines.

The proposed Open Virtual Machine Format (OVF), created by Dell, HP, IBM, Microsoft, VMware and XenSource, provides metadata about virtual machines such as memory, storage and networking requirements.

OVF also lists special feature requests like the need for certain chip instruction sets or large demands for floating point or integer calculations.

The standard allows for integrity checks, ensuring that a machine has not been altered during storage or shipping.

Makers of virtual appliances can use OVF to include licensing information, requiring the user to agree to certain terms and listing the maximum number of allowed installations, for instance.

OVF will not enforce the licences, although such technology could be created at a later stage.

The standard also allows the creation of application stacks where multiple virtual systems are stored in a single OVF file with one set of metadata.

As a file is deployed, the virtual machine monitor could automatically create each of the machines.

The group of vendors has submitted OVF as a draft to the Distributed Management Task Force (DMTF) standards body, and a version 1.0 is expected in six to nine months.


VNUnet reporting...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!