Using VMware Community Source to Drive Innovation for ESX Server

The World’s Leading Companies Rely On Emulex

Emulex Is Trusted World WideServers Storage Partners

Downsides to Virtual Server SAN ConnectivityPrevious Single-System relationship to physical port lostThere is no VM-identification on any I/O request from the serverNo ability to differentiate VM-specific data flows in the fabric (QoS)Trouble-shooting issues with virtual machines more difficultStorage Presentation very differentAll ESX servers must be able to see all storageOpen-Zoning – All servers and storage in same zoneLUN Mapping/Masking based on servers, not the machine• No ability to track per-VM data access on the storage arrayDepartmental division of “Server” admin vs “Storage” admin blurred.

Emulex LightPulse Virtual HBAAllows a Virtual Machine to effectively have its own “SAN ID”Each VM has World Wide Port Name (WWPN) resourcesBased on industry standard N_Port_ID Virtualization (NPIV)Multiple SAN addresses assigned to a physical port and distributed to the VMsEnables SAN best practices:VM-based zoning and LUN masking/mapping to control presentationSAN tools can track the Virtual MachineVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWVirtualHWHypervisorHypervisorFibre Channel HBAWWNEmulex LightPulse Virtual HBA technologyMultiple FCIDs

The NPIV Community Source OpportunityNPIV requires modifications to more than the device driverESX must know/manage WWPN’s as resources of the VMNPIV API between ESX and the driver is neededMust be integrated into ESX at VM startup or shutdown.VMotion must migrate the NPIV resources along with the VM.ESX has significant design points to consider:Understanding “what could be” for dynamic resourcesEnsuring proper connectivity prior to VM startupHow to best create HA configurationsUsing Community Source, we can:Accelerate Development and integration into ESXUse the forum for tighter communication with ESX engineering andproduct management

CS-NPIV ProjectEmulex created an Open Project to work on NPIV January 2006Includes Emulex and QLogicSVN branch on ESX 3.0 trunkEmail reflector for discussion and submit logsBi-Weekly Con CallsResults:Emulex-contributed API specification now an ESX interfaceVMware has integrated NPIV support into CS ESX kernelNPIV Technology Preview released September 2006Set of rpms for ESX 3.0 to add NPIV supportInstallation of Emulex NPIV device driverUpcoming ESX releases folding in NPIV modifications

Community Source ImpressionsPositives:Ability to modify the kernel, not just your device driver.Able to gain deep understanding of ESX and how different parts interactAble to work directly with VMware engineers who concentrate on the vmwarekernelGreat ability to create changeCreate the solutionGenerate rpms to replace any or all kernel contentsAbility to immediately test, and to do so without VMware interactionVery good support documentation (lab notes and pdf docs)How to install; Lay down rpms; Build ESX server componentsTest Suites provided for many componentsGood Bug-Tracking tools that can isolate view to a specific IHVExcellent Support teamKnowledgeable and responds quicklyProvides background testing supportOccasionally makes modifications on your behalf

Community Source ImpressionsCons:Applications and Management software is not part of CSIt is difficult to create applications to test your kernel APIsNo opportunity to aid in integrating change into Virtual CenterDependent upon VMware for VC changesCS is still young and doesn’t enjoy wealth of IHV participation (yet)CS processes still going through growth processA lot of communication still occurs behind the scenesActual ESX integration, support levels, and schedules driven by VMware

Community Source vs Open SourceSimilarities:If you have the need, you can make it happenFull access to kernel code. Can see what it’s doing.Very good mailing lists used for help. Very knowledgeable residents on theselists.Differences (ESX vs Linux):ESXSingle company managing processClear, quick acceptance process.Direct access to CS SVN poolKernel acceptance by VMwareSmall group of reviewersReview focused on End-User/ProductStrict compatibility requirementsVery Good Documentation and LabNotesLinuxEntities: The Community; each DistroAcceptance process cloudy. Kernelintegration multi-staged.Kernel acceptance by Community & DistroLarge community reviewMore focused on architectural purityMore amenable to API changeDocumentation scattered, perhaps out ofdate, not all inclusive. Some very good.

Community Source BenefitsTime to MarketCan significantly influence and accelerate change in ESXAbility to create asynchronous ISO imagesAbility to ship previews outside of VMware product delivery dates.• Ultimately, support is still based on VMware schedules

Tips and AdviceGet started earlyIdentify the technology and project and engage VMware teamUtilize the resources across the boardVMware business, marketing, engineering and test resourcesUnderstand the optionsPrivate engagement, project group or CS-wideGet customer validationUnderstand VMware customer and your customer overlapBe realisticRome wasn’t built in a day, and neither was ESX

Thank YouQuestions?

Presentation DownloadPlease remember to complete yoursession evaluation formand return it to the room monitorsas you exit the sessionThe presentation for this session can be downloaded athttp://www.vmware.com/vmtn/vmworld/sessions/Enter the following to download (case-sensitive):Username: cbv_repPassword: cbvfor9v9r