Please line up your peer reviewers and the core team will get them access to your lab and manual in the VLP portal using a restricted Pre-Release catalog. Release Window 2 is permitted by Core Team approval only if additional time is needed for vPod completion. įunctional testing for your lab will commence in the HOL portal immediately following the draft deadline for your lab which most cases is Release Window 1. Milestones for vPod Development can be reviewed on the HOL SharePoint site. During VMworld, lab manual updates can only be done when VMworld HOL is closed. Updates are not automatically published to the portal. Please alert your Lab Principal when lab manual updates are needed. The lab manual is exported and then imported to the Hands-on Lab portal. The lab manual is created using ScreenSteps. For more information on getting started building the vPod for your lab, please review the other articles in this series including vPod Configuration and Building Blocks:Creating your vPod. Generally, a vPod includes virtual ESXi hosts which run nested on physical ESXi hosts in VMware's vCloud Director virtual data centers. The lab's virtual run time environment is referred to as a vPod. Also note that the VM console is usually the Main Console (controlcenter) but an alternate VM can be used for the primary desktop. You may specify which VM is the primary console and should be displayed first. Please note that your lab can use more than one VM console. Please review the slide at the end of this article. External access to the virtual environment is accomplished using a VM console proxy connection embedded in a client browser control. The lab manual can access Internet resources such as YouTube videos but the virtual run time environment is isolated in most cases. Both components are presented in a modern web browser during the event. VMware Hands-On Labs consist of a lab manual and a virtual run-time environment. If requested by your Lab Principal, y ou must also pass a short test covering material in this HOL Lab Development Guide. To begin vPod development in the HOL-Dev environment, you must complete your Development Plan, Storyboard and LCD. Please do not over subscribe virtual ESXi hosts. Please note the virtual ESXi host to be used to host nested VMs and the expected configuration of those nested VMs. There is a nested VM tab to be completed as well. VLP also utilizes a callback notification mechanism that can assist in the creation of the external sandbox for a user's session. Those external resources must be identified so proper firewall rules can be constructed. Choose the LCD that most closely aligns to your starting vPod which are Single Site, Dual Site, SDDC and MBL. There is also a Hybrid LCD which is used if you have received permission from the Core Team for your vPod to have access to external resources. The LCD template documents are also in SharePoint location as above. The Lead Lab Captain and Lab Principal submit a completed Lab Configuration Document to the Lab Roadmap on Sharepoint. The Content Lead, Lab Principal and Lead Lab Captain develop the storyboard for the lab in ScreenSteps. The Content Lead, Lab Principal and Lead Lab Captain submit the Development Plan in the Lab Roadmap on SharePoint (internal to VMware employees) where all design documents related to a lab are archived. This first article is a quick overview of the process and includes links to important documents.Ī VMware Hands-On Lab begins with a compelling story showing the technical and business value of a solution leveraging VMware software. We will keep the document concise and easy to read in small chunks. This is your guide to developing a VMware Hands-On Lab. Welcome to the VMware Hands-On Lab program. VPod Development Guide Welcome and Overview VMware Hands-on Labs - HOL-Lab-Development-Guide
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |