Citrix: PVS Internals #3 – Designing vDisk stores
Working as an architect often resembles a Choose Your Own Adventure book. You are talking with your customer, trying to understand their needs and offer them several options to choose from. Sometimes you might have a very strong preference for one of these options and sometimes you leave it up to customer preference, just providing them with a list of pros and cons. Your only goal, after all, is to make sure that the story ends with a happy ending and not in a trap door with deadly performance spikes.
Citrix Provisioning Services (PVS) would be one of the bolder “Choose Your Own Design” books. There are many different design decisions that you need to make – and surprisingly a large number of these decisions are not black or white. Some of them are very simple, like which write cache type you should use (RAM cache w/ overflow to disk is the right answer in 99% of the cases). Some can vary depending on your environment, as in memory sizing on PVS servers. (See earlier blog posts Cache Manager and How to properly size your memory.)
Then there are some design decisions that don’t have a clear winner and are often based on personal preference. For example, how are you planning to deliver the bootstrap file? Do you want to use BDM or TFTP? If BDM, ISO file or boot partition? For TFTP, how are you going to make sure that it’s highly available? There are quite a lot of good blog posts about this topic, but no clear winners.
Read the entire article here, PVS Internals #3 – Designing vDisk stores
via the fine folks at Citrix Systems, Inc.