Skip to main content

Yet Another Virtualization Intro: Virtualization and Client Server Technology

Isolation implies the independence virtual machines afford. Virtual machines are completely isolated from hosts and other machines. This provides the security that if one machine crashes the rest of the machines will be unaffected. This isolation also ensures data control. Machines can only communicate through specifically configured network connections. Data cannot infiltrate or affect other machines or applications.

Encapsulation is similar to the abstraction and information hiding that characterizes virtualization. It is defined as the combination of elements to create a new entity. For example, OOP (Object-Oriented Programming) languages like C++ and Java use encapsulation to create high-level (abstracted) objects. In virtualization, an entire virtual machine and its contents are encapsulated so it can be saved as a single file. This makes it incredibly easy to copy and move. Encapsulation resonates with virtualization in its tendency towards hiding the details to make dealing with objects easier. This is accomplished by hiding complexity with a simple interface.
Link

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!