Sun VDI 3 -What is it about - VMware Virtual Infrastructure
By MrDGrobler on Feb 11, 2009
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,
« previous »