Jumping VDI

This is the last article of the 'What is about series'. It covers how VDI 3 connects against VMware VI3. Bottomline is we connect in the same way as we did with VDI 2. So, the diagram is not much different compared to the previous release.

However, under the hood we've changed quite a lot with the main goal of improving the performance and the scalability of the whole system. Here's an extract of the changes:

• We've replaced the agent on the vCenter with a pure remote communication. This simplifies deployment and the update process.
• We don't move any VMs or folders around. All information is kept in our datastore. This has a lot of positive performance implications.
• Multiple vCenter server can be connected. No problem with the 2000 VM limitation, except that you need multiple instances of vC, of course.
• No pool limitations anymore. No static folder anymore. Much more flexibility with the new pooling concept.
• No identifier-mapping between VM and user. This relationship is stored in our datastore and just depends on internal object IDs. Implication is, that you can rename machines as you like without breaking an assignment.
• Better and fine-grained resource control. For each pool you can define which computing resources and storage you want to use.

That's roughly it. Next articles will probably touch a bit more the system setup.

Cheers for now,

Dirk

« previous »

Hi folks,

This is a very common question we get these days for the VDI 3. Simple answer to that is, desktops are made for users. And the user data is kept in 99% of the deployments in user directories. So that's the simple reason.

Next question is then:

I want to do a Proof-of-Concept. Where should I get a user directory quickly?

There is a really simple answer to it. Use OpenDS. The open source LDAP server, derived from Sun's Directory server. All built in java. There has been just a new release been done beginning of this month. Perfect for a POC. There are just a few steps to get the install done:

1. Go to the download page https://opends.dev.java.net/public/downloads_index.html and launch the quickstep install.
   This launches a java webstart installation, very simple and straightforward
2. Provide the install path
3. Provide the Root User password
4. Select standalone server
5. Specify the domain
6. Import automatically generated sample data
7. Done.

After a few minutes the install is complete. Any administration task can be done through the console <install path>/OpenDS/bin/control-panel. Thereafter you simply point a VDI 3 instance to the server, where OpenDS is running with (LDAP, anonymous access) and you are done for the POC. At least in regard to the User Directory ;-)

-Dirk