VMinformer a security tool for vmware

VMinformer a security tool for vmware.

A london based company into design and to build applications to compliment and integrate with virtual enviornments.

VMinformer is has four main features

• Assess
  Monitor the security of your virtual environment
• Secure
  Identify key security issues with step by step fix guidance
• Comply
  Adhere to PCI and SOX requirements
• Report
  Clear concise security view of your virtual environment

Free trial download is available.
Download

SpringSource is accusitioned by VMWARE.

VMware Got What It Paid For: A Vision Of The Future

Posted by Charles Babcock, Aug 13, 2009 09:30 PM

VMware's acquisition of SpringSource is not a match made in heaven. It's going to take an effort by both parties to make this marriage work. Still, it looks like one of the few responses VMware could make to counterMicrosoft (NSDQ: MSFT)'s dangerous invasion of its turf.

These thoughts were prompted by an exchange with Salil Deshpande, a general partner of on the three largest investors in SpringSource, Bay Partners. "I don’t think VMware can remain simply a virtualization vendor. Virtualization is just table-stakes, at this point," he wrote in an email response to my query on why VMware was making its $362 million investment.

Deshpande didn't mention Microsoft and he has no special knowledge of VMware's intentions. But with Microsoft offering Hyper-V as a feature of the operating system, what, in the long run, was VMware supposed to do? Stand by and watch its $1.3 billion virtualization empire get commoditized? How could it take advantage of current computing trends and ward off an incipient invasion of its customer base?

One answer is to harness virtualization to a larger and higher purpose, one that might be difficult for Microsoft to match. It took its first steps in that direction with vSphere 4, a re-orientation of its product line from managing a local center of virtualization, its Virtual Center, into creating a data center operating system that would manage the majority of resources.

Managing virtual machines themselves is supposedly the big thing right now, but that's something of a mis-statement. Running applications effectively on virtual machines is the big thing, and VMware customers run a heavy percentage of Windows applications on their ESX Server virtual machines.

Microsoft's growth in the data center has been impressive, in part, because of the growing power of the x86 servers, thanks to multi-core processors, and the expanding legions of application programmers familiar with Windows Server.

In looking around for an alternative, it seems logical that VMware would gravitate to Rod Johnson and SpringSource, since Johnson is one of the few people who has understood that Java could be made simpler to use. Too many Java advocates love their complexity. Johnson himself has said he had to get out of the mindset of the Java programmer to see where it was going wrong, how it could be made easier to use.

In the future two new things will be required of applications that will give Java apps a continued, major role in the enterprise: they will need to be broken up into services and spread across many servers. Java applications lend themselves to running in multiple process threads, suitable for multi-core chips and multiple servers, taking advantage of a trend that yields high performance.

In addition, the workload will need to be split between 1) the part running in a bare-bones data center that hums along furiously close to 100% capacity much of the time, and 2)the part that gets exported to the external cloud, which picks up the slack.

Java, or a combination of Java and one of the modern dynamic languages, can do this as well. The scripting language communicates upfront with the public cloud and tells it what's needed, setting up the core Java business logic.

SpringSource is one of the few companies that has had an appetite to pull these two attributes together, lightweight Java development and the flexibility and Web-worthiness of the scripting language.

VMware officials, wary of the looming Microsoft presence and eager to find a way to counter it, must have been intrigued by SpringSource's ability to keep grafting new capabilities onto what it had already accomplished.

Maybe VMware paid too much, as a few skeptics have said. But sometimes maintaining your ability to see into the future and navigate its shoals is worth a little extra.

"Cloud computing will be too pervasive and too important for VMware to remain only a virtualization vendor. It needs to do more. It needs to make many moves such as the SpringSource one. I think they will," said Bay Partners' Deshpande.

E-book on virtualisation for dummies

SUN email subscribers were provided with a e-book on virtualisation for dummies.
Dummies is age old and they keep the humour intact and this e-book is good for freshers and even for experts as it would help them to explain the concepts to a layman.

Virtualisation for dummies

A very good link on Virtualisation

A very good link on virtualisation.

http://www.internetevolution.com/tutorial_virtualizationsecurity.asp?f_src=rtcolad_virtsecurity

there is so much to it and there is also a webinar.

Project on virtualisation of 450 servers

There is a project on virtualisation of about 450 servers of which there are windows and linux servers.windows servers to be virtualised are of windows 2000 server and windows 2003 server, linux of redhat ......

which are the best tools for it ?

Tools for Virtualisation - Virtualbox

Tools for Virtualisation - Virtualbox


Virtualbox is a set of tools from SUN which is under open license and works on a series of paltforms which includes Windows,Linux,Solaris,Freebsd

Virtualbox alongwith its source,binaries,documentation can be downloaded from the site http://www.virtualbox.org/

here are some screenshots on virtualbox
http://www.virtualbox.org/wiki/Screenshots

Virtualbox software development kit can be downloaded from
http://dlc.sun.com/virtualbox/vboxsdkdownload.html#sdk

Different types of virtualisation

Different types of Virtualisation

As you are aware of some of these technologies standards are defined by corporates and each has its own set which die out in course of time and some emerge and become common standard as it was in case of Video adapters,DVD's and many more until a body like IEEE etc we have microsoft which even had java of their own version and even sun sued them. They even had MOF Microsoft Office Foundation which was their version for ITIL

Microsoft has Classified Virtualisation into Four of them.
Server Virtualisation
Desktop Virtualisation
Presentation Virtualisation
Application Virtualisation

Let's walk through them.

Server Virtualization

This is the most commonly thought of instance of virtualization . Extending our bubbles, let's take our bubble and wrap it entirely around entire servers. We encapsulate a server operating system and any applications, and build an entire virtual machine. This allows entire servers to become those portable bubbles, and independent of the hardware beneath them. Examples include using VMWare Server or hyper-v in Windows Server 2008 to run an entire machine in a virtualized environment. Let's diagram this out.

First, let's take the conventional "hardware plus operating system" we're all so familiar with.

You take a piece of hardware, and you put an operating system on it. Simple, the way it's been done since your grandpappy did it.

Now, I want to wrap bubbles around the operating system, and seperate each off.

You end up with multiple operating systems running on one physical machine, managed by the virtualization layer.

Let's take an example. You have a Windows Server 2003 system, and you have an application running under it. That application hasn't been tested under Windows Server 2008, and yet you want to take advantage of the new group policy objects within Server 2008 to handle your Vista desktops. You could add another piece of hardware, but that will up your maintenance costs and require the management of two full servers.

Instead, you could move the Windows Server 2003 system into a Virtual Machine, and then have Windows Server 2008 as your core operating system. Each runs on the same hardware, and you're able to keep your application snug in it's Windows Server 2003 heaven until you're ready to upgrade it. (And, now that it's virtualized, see the previous sections for all the benefits of managing it under virtualization for the upgrade! That upgrade should be a snap.)

Desktop Virtualization

I almost want to say "See above, but with Desktops". That over simplifies a little, as you can do some other interesting things with Desktops. On your own laptop or desktop, you can run more than one machine. I like to demo this with my Mac, as I use VMWare's Fusion to run a virtualized Windows machine, so in the single laptop, I have three entire machines. OS X runs the "host" operating system, and then Windows XP and SBS 2008 RC0 are both available as additional machines. In fact, they each have their own IP addresses, have to use networking to talk to one another. This can be costly from a management perspective, as you do end up creating more machines each time, from a desktop perspective.

The diagrams would be the same. The only significant difference is that we're doing this on the desktop rather that the server, and then we're really only talking about a difference of the operating system below and within the bubble.

Example time. You want to upgrade to Vista, but have an application that only runs under Windows XP. (Sound familiar -- it should, it's a lot like Server Virtualization). Instead of holding back, you can give the customer a Windows XP environment, running in a VM, that allows them to run their application on a Windows XP machine, while still upgrading the core operating system to Vista.

Presentation Virtualization

Very much related to Desktop Virtualization, Presentation Virtualization puts the display on one machine, and the actual execution on another. Processing happens on the server, which is optimized for availability and capacity, and the end user UI is handled on the desktop. Terminal Server or solutions by Citrix are a great example of this, as is RWW in SBS.

You centralize the data, making sure it isn't spread across various desktops, and you lower your cost of management, since to update desktops in one single place. Additionally, this can improve performance in some circumstances, where network bandwidth is an issue, such as across a WAN.

Diagraming this out, the idea is that you centralize where everything is run, and only ship the display across the wire. You only have to upgrade an operating system or a application in one place, and you can control access easily. No data is left "floating" about on the terminals, and you can even manage backups centrally.

Let's give this as an example. You have a customer who has two branch offices, each with three employees in them. They use a line of business application that is very bandwidth intensive. It's quite chatty, and it needs to be on a local LAN with the database server. Rather than try and setup two more databases in the field, you centralize the application and allow your clients to connect in, sending only the keyboard, monitor and mouse communications back to the users. The application happily communicates with it's database, and the end users in each office see a responsive, useful application.

Application Virtualization

Finally, we'll look at application virtualization. Now that you understand presentation virtualization, application virtualization should make more sense. The intention is to put one of our bubbles around an application and yet still run it on the client.

Typically, when you have to install an application, it plants pieces around the machine. DLLs, for example, are laid around the machine. Each application interacts with the operating system, and can interact with each other.

This can lead to situations where the applications themselves collide. If you were trying to isolate an application from the operating system, you could easily use Desktop or Server virtualization. But if the applications collide, you have other problems.

Take something like QuickBooks. CPAs love to have every version of QuickBooks installed on their computers, because that way they can work with all different clients who may have upgraded to different versions along the way. Thus, if CPA-A, works with Customer A with QuickBooks 2004, and Customer B with QuickBooks 2007, the CPA doesn't want to open Customer A's data file with QuickBooks 2007, else the customer won't be able to open it.

But having all those versions of QuickBooks on the desktop can cause issues. Intuit really doesn't intend for you to run them all; they expect you to run one and work with it.

So what if we could wrap bubbles around each?

That's what application virtualization does. It creates application specific bubbles, each with it's own required dependencies (registry entries, DLLs, and all), and are packaged in a neat bubble to keep them seperated from the operating system and from each other. The application can play within it's own bubble, using it's own resources and not mixing with those around it.

So that's the four basic kinds of virtualization. My efforts here are first to concentrate on Server and Desktop Virtualization, and implementations and "how to's" around that.

While EMC has them as three.

How is Virtualisation and Consolidation Different ?

How is Virtualisation and Consolidation Different ?

Although these both are used for simplification and optimisation and cost reducation the goal of both they have a few differences which makes them different.

Firstly Consolidation is of a physical aspect while virtualisation is of a logical aspect.

Secondly Consolidation may involves physical movement of servers while virtualisation does not focus on physical location of server.

Thirdly Consolidation does not necessarily involve the use of software while virtualisation is about running the bundled packages on a base OS.

Virtualisation and Consolidation

Virtualisation and Consolidation are two aspects of simplification of hardware and Data centers,servers etc, although these methods may appear to be complication to novices.

Virtualisation is about higher utilisation of resources,which include compute,storage and network, this results in Horizontal scalability,it is also described as the process of a aggregrating smaller resources towards a cumulative power of all.

One of the breakthrough's of virtualisation is in changing the old computing paradigm of one application per server.

Virtualisation makes it possible for mutually incompatible application, ie applications which are known to cause problem when working together to run on a single server.

This is brought about by a server to work as a file which is untouched by parallely running servers which are similar files,Advancements have made it possible to have different OS and different versions of OS to run concurrently as independent servers ie as Virtual servers on a physical server.Each of these virtual servers are OS & Application bundled with virtual hardware into a single file which is capable of working independently from other similar virtual servers.

Consolidation is about pooling resources to enable greater utilisation of assets with greater flexibility.Its about optimising technologies to achieve cost savings, Improve performance and mitigate risks.This involves physical planning,optimisation and physical migration of systems and facilities, and applied on Data centers,storage,applications, services and network.