Skip to main content

Application Virtualization tutorials



Nice articles on Application Virtualization. Martin Brown explains:

You can consider a grid to be a form of virtualization -- if you consider the individual components and functionality within your grid as virtualized components that can be accessed by higher-level applications. For example, within a typical grid environment, the security of the grid, storage methods (particularly for resources and persistent, but transient, data used during grid execution), and the entire method of executing the application are abstracted.

The grid infrastructure sits on top of one or more platforms and provides services within a standardized environment. You can almost consider the environment to be a new operating system and platform. Effectively, the underlying platforms (hardware and OS) are hidden by the grid environment. The grid then provides a new environment for the execution of applications, and the application runs in this virtualized environment. In this respect, your application runs in a virtualized environment created by the grid, which in turn creates the virtualized environment by collectively organizing the grid components to operate as a single resource.

In this series, we will examine the three levels -- grid infrastructure, grid environment and grid applications -- and how they interact, and how to build and adapt your applications using the standardized environment offered by the grid and the solutions offered by the Open Grid Services Architecture (OGSA), service-oriented architecture (SOA), the Web services (WS) standards, and other techniques.



Here check them out part 1, part 2 and part 3.

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!