Creating Microsoft Windows Virtual Machine Images for Use with ESXi Compute Clusters in HP CloudSystem

Transcription

1 HP CludSystem Fundatin and Enterprise Sftware Creating Micrsft Windws Virtual Machine Images fr Use with ESXi Cmpute Clusters in HP CludSystem This paper describes the prcess fr creating Windws VMDK images t use with ESXi cluster cmpute ndes in a CludSystem envirnment. Images are the basis fr virtual machine (VM) instances in HP CludSystem. Yu can create and imprt images frm underlying hypervisr platfrms int CludSystem. An verview f image cncepts CludSystem is based n HP Clud OS and OpenStack technlgy HP CludSystem Fundatin is based n HP Clud OS, which is based n pen surce OpenStack clud technlgy. Images are upladed int the CludSystem image repsitry, and then users can launch VM instances based n thse images. The OpenStack service that manages images is called Glance. Images are disk files with pre-installed, btable Windws r Linux perating systems. Images may als have pre-installed applicatins. Supprted image frmats and guest perating systems in CludSystem CludSystem supprts the guest perating systems that are supprted by the underlying hypervisr platfrm. Cnsult VMware and Red Hat dcumentatin fr a list f supprted guest perating systems. The fllwing image frmats are supprted: Fr ESXi, images must be in VMDK frmat. Fr KVM, images must be in qcw2 frmat. CludSystem Fundatin and CludSystem Enterprise The CludSystem slutin is ffered in tw packages. Fundatin is an Openstack-centric IaaS slutin, where images are laded and used t launch individual VM instances within the OpenStack paradigm. Enterprise is centered n HP Clud Service Autmatin (CSA), ffering advanced rchestratin, cmplex service design, and a Market place Prtal user experience. When prvisining VMs defined in an Enterprise service ffering against the CludSystem Fundatin prvider, yu can use images that were previusly upladed int Fundatin. What makes an image clud ready? When creating images t use with virtual machines (VMs) in CludSystem, keep the fllwing details in mind: Disk partitins must be able t be resized during launch. OpenStack allws users t select multiple flavrs, which define different sizes f cmpute resurces and bt disks. The perating system (OS) in the image must supprt new MAC addresses. Each time an image is launched as a VM, it is assigned new MAC addresses fr virtual NICs. A user lgin mechanism must be part f the image s sftware and cnfiguratin. Typically, Remte Desktp Prtcl (RDP) is used fr Windws and Secure Shell (SSH) is used fr Linux. The rt/administratr accunt can be disabled and lgins can be prhibited. This makes it easier t supprt the VM instances frm central IT. 1

2 Firewalls are ften disabled. OpenStack security grups prvide a methd fr creating and applying firewalls as each VM is instantiated by the end user. If default r minimum firewalls are already set in the image, netwrk trubleshting can be difficult. Use a secure user lgin authenticatin mechanism that prvides each end user with a unique passwrd r key. Cnfiguring passwrds int a cmmn image is nt a recmmended slutin. Instead, fr Windws, end users shuld set a passwrd fr an accunt in the launch dialg. Fr Linux, end users shuld chse a key pair fr the VM instance when the image is created. OpenStack supprts the clud-init mechanism fr passing data and scripts t a newly created VM instance. A cmmn practice is t perfrm final custmizatin f the image when it first bts as a VM instance, using specific infrmatin prvided in the create r launch request. Make sure t lg infrmatin t the cnsle. When trubleshting image issues during startup r issues related t netwrking, it is extremely helpful t have the image lg infrmatin t its cnsle. Yu can access the cnsle thrugh the CludSystem Prtal r thrugh the virtualizatin layer using vsphere client, KVM cmmand line virsh cmmands, r Virtual Netwrk Cmputing (VNC). Cnfirm the supprted guest OS against the underlying hypervisr. VMware guest OS supprt is fairly brad; Red Hat less s. T ensure a vendr supprted cnfiguratin, make sure t cnfrm t the vendr s guest OS supprt list. Make use f hypervisr tls and ptimizatins. CludSystem prvides a cmplete management envirnment fr images and prvisined VM instances. In additin, the virtualizatin layers (ESXi r KVM) have a critical rle in trubleshting, develpment and perfrmance ptimizatin. Whenever pssible, image size shuld be minimized. Image size impacts actins such as mving, using, and string images. Yu must accunt fr any OS and sftware licensing fr images instantiated as VMs. When a site license is available, it can be cnfigured in the image. Anther apprach is t cnnect images t license management framewrks during cnfiguratin r after the VM instance is created. Clud-init tl fr clud images Many f the issues described in the previus list have been slved fr Linux and Windws images by the pen surce prject clud-init. Yu can find infrmatin n clud-init at Originally develped fr Amazn Web Service (AWS) and Amazn Elastic Cmpute Clud (Amazn EC2) images, clud-init is fully functinal in an OpenStack envirnment.. Where d images cme frm? Images used in CludSystem prvisining cme frm three majr surces: 1. Images created in the hypervisr platfrm and then imprted fr use int CludSystem. 2. Images dwnladed frm a public surce and then imprted fr use int CludSystem. 3. Snapshts f running VM instances in CludSystem that are saved as images, and then used t prvisin new VM instances. Optin 1: Creating images frm scratch This apprach is cvered in detail in later sectins f this paper. It gives yu cmplete cntrl ver the cntents, behavir and features f the images used by yur users. 2

3 Optin 2: Dwnlading images frm a public surce Pre-created images fr use in OpenStack based cluds are available frm varius surces. The OpenStack dcumentatin prvides a list f sme f these publically available images at Many are Linux images supplied directly by the majr Linux vendrs. An OpenStackcmpliant Windws image is prvided by Clud Base at The advantage f publically available images is that the images are ready t use, have clud-init, and have clud-ready prperties. When using images created by anther surce, cnsider the fllwing: Security: D yu trust the security and integrity f the image and its prvider? Licensing: What are the licensing cnstraints, if any, assciated with the image and the sftware inside it? Supprt: Wh is supprting the image if yu have prblems? Optin 3: Creating images frm snapshts f launched VMs Once yu have images laded in CludSystem and yu have created VM instances, yu can take a snapsht f a VM instance and use it as an image. This apprach gives yu the flexibility t uplad simple, custmizable images. This ptin is nly available nce yu upladed initial images in yur envirnment using ptin1 r 2. Building a Windws image fr use with ESXi cmpute clusters This sectin prvides a high-level verview f the steps required t create a Windws VMDK image fr use in CludSystem. Sme steps are required, while thers are ptinal. Step 1 Create the surce virtual machine in vcenter Server Tw key settings are required fr yur Windws image t wrk: SCSI Cntrller -> LSI Lgic SAS Virtual Device Nde -> SCSI Where pssible, chse the smallest bt disk size that will wrk fr yur Windws versin and ptins. CludSystem allws users t request a larger bt disk size fr the resulting VM at launch s the size nly needs t be big enugh t supprt the installatin and preparatin f the image. Step 2 Install Windws and custmize ptins Multiple Windws versins are supprted and there are n specific ptins that are required fr yur image t bt. That being said, there are a number f aspects that are best practices fr images prvided as a service t users in a clud. This step is an pprtunity t cnfigure the ptins, sftware and settings yu want t include in yur images. Step 3 Add VMware tls t the virtual machine VMware tls are required t allw CludSystem t shut dwn VM instances created frm the image. Additinally, VMware tls prvide the ability t manage the image frm within the VMware hypervisr platfrm. Step 4 Create an unattended file using Micrsft System Image Manager Advanced IT deplyments leverage Windws Sysprep t set the final settings f the deplyed VM at first bt n launch as an alternative t making all settings and custmizatins when the Windws OS is installed. This allws yu t take a cmmn image created t this pint and derive additinal image variatins fr users with different settings, such as internatinalizatin. Step 5 Install clud-init Fr simpler use cases and testing, yu can skip this step and instead use Step 2 Install Windws and custmize ptins, and ptinally, Step 5 Install Clud-init, t custmize the image. Clud-init is the pen surce mechanism fr custmizing the perating system f a newly prvisined VM instance. It can be used t handle many actins, particularly passing metadata frm the CludSystem GUI r CLI interfaces int the VM instance fr interpretatin and executin with scripts yu ve cnfigured int the image. Fr example, this clud-init step sets up an administrative user accunt and lets the requesting user frm CludSystem set the passwrd fr it. If OS custmizatin is nt required, then yu d nt need t perfrm this step. Step 6 Run Sysprep Sysprep prepares the image t use specific Windws values based n unattended files created in Step 4. If yu are using clud-init, this step is required. If yu are nt creating an unattended file r using clud-init, then yu d nt need t perfrm this step. All behavir and settings are cntrlled by the ptins cnfigured in Step 2. Step 7 Set required VMware image prperties with VMware tls A VMDK image can be flat r sparse frmat. The prperties must be set crrectly befre lading the images int CludSystem. Fr flat images, fully expand the VMDK image using the vmfstls -d eagerzeredthick ptin. 3

4 Fr sparse images, make sure they are already cnfigured as sparse r cnvert them t sparse using the vmware-vdiskmanager with -t 0 ptin. Step 8 Uplad the image t CludSystem Yu can uplad an image by cpying it t the CludSystem Glance image repsitry r by entering a link t an HTTP server that hsts the image. In the secnd scenari, when CludSystem needs the image fr an peratin, it fetches it frm the HTTP server. When yu cpy the image int CludSystem s Glance repsitry, yu can use the CludSystem Prtal, the CludSystem Cnsle, r the Glance CLI. The CLI prvides mre cntrl and mre ptins and handles larger image sizes than the GUI ptins. Using the CLI is the recmmended best practice when wrking with Windws VMDKs. Step 9 Set required CludSystem prperties The CLI tl is used t set the tw CludSystem required prperties fr Windws VMDKs: vmware_stype=<ostype> Example: windws8server64guest fr Windws 2012 vmware_adaptertype=lsilgicsa If yur image is sparse VMDK frmat, yu are als required t set: vmware_disktype=sparse Additinal image ptins can be set at this time t establish a minimum disk size and memry fr the image t restrict users frm requesting an instance with insufficient resurces. These are ptinal. min_disk=<minimum disk size in GB independent f user selected flavr> min_ram=<minimum RAM MB independent f user selected flavr> Step 1: Create the virtual machine surce in vcenter Server In yur VMware develpment envirnment, create a virtual machine t use as the surce f the image. Mst parameters are supprted with a wide range f values, but tw parameters require specific values in rder fr the image t wrk. The tw required prperties are: SCSI Cntrller -> LSI Lgic SAS Virtual Device Nde -> SCSI Creating the virtual machine surce in vcenter Server Create the virtual machine. Custmize the cnfiguratin. a. Name and Lcatin -> <Yur chice > b. Strage -> <Yur chice> c. Virtual Machine Versin -> Virtual Machine Versin 8 (This is the default) d. Guest Operating System -> Windws Versin Example: Micrsft Windws Server 2012 (64-bit) e. CPUs Number f virtual sckets -> <Yur chice> Number f cres per virtual scket -> <Yur chice> In CludSystem, the actual value fr CPUs t supprt the instance is a functin f the OpenStack Nva flavr selected fr the instance. The values yu set fr the VM at this time have n effect. Pick the values yu want while yu are develping the virtual machine image. 4

5 f. Memry size -> <Yur chice> In CludSystem, the actual value f RAM is a functin f the OpenStack Nva flavr selected fr the VM instance and any min_ram value that was set as a prperty f the image in CludSystem. Setting the min_ram size is cvered in step 7. At this pint, just enter a value that allws yu t develp the virtual machine image. g. Netwrk Set the netwrk adapter t E1000 r E1000E E1000 and E1000E drivers are cmmnly available in Windws by default. Other NIC types culd wrk but yu must make sure that yu included the driver. Number f NICs -> <Yur chice> The number f NICs attached t an instance is determined by the user during prvisining. h. SCSI Cntrller -> LSI Lgic SAS IMPORTANT: LSI Lgic SAS is the nly supprted value fr a Windws VMDK in CludSystem. i. Create the disk. Capacity > < Yur chice> Best practice is t set the size as small as pssible fr staging the image. The actual bt disk f the VM is determined by the user when the VM is instantiated. During prvisining, the actual value f the VM s bt disk is a functin f the OpenStack Nva flavr selected fr the VM instance and any min_disk value that was set as a prperty f the image in CludSystem. Setting the min_disk size is cvered in step 7. At this time, just select a value t use while develping the virtual machine. Fr example, the recmmended minimum size reprted by Windws 2012 fr a standard image with GUI ptins is 18GB. But it is fairly straightfrward t create a hell wrld functinal Windws 2012 standard editin image at arund 9GB in size. Yu can wrk with an image size f 9GB during staging, set a minimum f 40GB fr users and then they can use flavrs t create VMs based n the image with even larger bt disks. IMPORTANT: If yu usually wrk with hell wrld Linux images, which are generally much smaller ( MB), then the prcessing time and strage fr these larger Windws images will be cnsiderably larger. Disk Prvisining > <Yur chice> The size and frmat ptins f the image and hw it is stred as it is mved int and used in CludSystem is cnfigured later. At this pint, chse thick r thin prvisining while yu are develping the VM. j. Set advanced ptins. Virtual Device Nde -> SCSI IMPORTANT: SCSI is the nly supprted value fr a Windws VMDK in CludSystem. Step 2: Install Windws and custmize ptins The purpse f this sectin is t chse the ptins in the Windws OS that allw the image t be used as a Windws VMDK. Fr example, after launching the instance, a user culd gain cnsle access via the CludSystem Prtal, but typically the expected interactin is fr the user t access the cnsle via Remte Desktp Prtcl (RDP). Sme f the prperties and ptins can be set using the prcedure in step 4. Others are s cmmn t all versins f Windws images that they are best set using this prcedure. 5

6 Installing Windws and custmizing ptins 1. Install Windws accrding t the standard prcedures fr the versin f Windws yu plan t use. 2. Custmize Windws. a. Enable RDP If the VM is a server with nly autmated netwrk access, then the CludSystem Prtal cnsle access may be sufficient fr trubleshting and setup tasks. If it is nt, enable RDP as the standard interactive interface fr access t the VM. b. Set the time-zne c. Set netwrk interfaces t DHCP d. Enable the Windws firewall e. Define the Internet Prxy f. Set IE security settings g. Set Windws update settings h. Add standard crprate packages, such as antivirus and supprt hks 3. Discnnect the installatin media frm the VM. Step 3: Add VMware Tls t the VM VMware tls allw the user t perfrm a graceful shutdwn thrugh the CludSystem user interfaces. A VM rebt perfrms a safe guest rebt if VMware tls are present. If VMware tls are nt installed, a rebt results in a VM reset (hard rebt). Additinally, VMware tls in an ESXi VM are recmmended and prvide many benefits. See fr mre infrmatin. Adding VMware tls t the VM Install VMware tls using ne f the fllwing tw methds: a. Install interactively using instructins frm b. Install as a package using instructins frm Step 4: Create an unattended file using Micrsft System Image Manager Using an unattended file with Micrsft s Sysprep tl autmates the custmizatin f the image when it is instantiated during first bt. It is a pwerful tl fr prductin clud images. Fr a simple test image, yu can mit this step and rely n the custmizatins yu cnfigured in step 2. If yu are als using clud-init frm Cludbase as described in step 5, the Cludbase tls will create a small unattended file specifically t integrate clud-init scripts int the Sysprep and startup prcess. In this case, yu must merge the tw unattended files t retain the clud-init hks and add in the specific custmizatins yu create in this step. The Micrsft tl fr creating unattended files is System Image Manager (SIM) which is a cmpnent f the Windws Assessment and Deplyment Kit (ADK) Sme f the many image attributes that can be cntrlled with the unattended file are: Administratr Passwrd This field can be used t set the passwrd in the accunt t a knwn value r t frce a user t set it interactively at first lgin. 6

7 Additinal user accunts An IT rganizatin may r may nt want users t cntrl the default administratr accunt. Alternative administrative accunts r user accunts with restricted privileges are set here. The passwrds are defined here r set t frce the user t set the passwrd n first lgin. An alternative t defining an accunt in the unattended file is t use a feature in the Cludbase clud-init package that allws yu t define a single additinal user accunt, which can als be linked int the passwrd setting mechanism f the CludSystem Prtal instance launch dialg. Language and keybard settings Settings fr language are dcumented at Prduct keys If yu are unfamiliar with Sysprep and SIM, the fllwing link prvides a gd descriptin f hw t create a simple answer file Sample unattended file Creating an unattended file t define the Administratr passwrd 1. Install SIM. Yu shuld have the ADK and SIM already set up n a develpment system. 2. Frm the OS media yu are using, cpy the install.wim file t a lcatin n the system that is running SIM. 3. T start SIM, select Start Prgrams Micrsft Windws OPK (r Windws AIK) Windws System Image Manager. 4. T pint t the OS media install.wim, select File Select Windws Image 5. T start a new answer file, select File New Answer File. 6. Set the prperties fr the unattended file. a. Frm Windws Image, expand the Cmpnents bx and navigate t the parameters yu want t set. b. Right-click and select Add Setting t Pass 7 besystem When the parameters are added, yu can edit them frm the bx in the upper right crner f the screen. 7. Use the Validate Answer File feature t verify the values yu entered. 8. T save the unattended file, select File Save Answer File. The default name fr this file is autunattended.xml. Additinal parameters t cnsider setting in a clud envirnment include: 7

8 Micrsft Windws Shell Setup LgnCmmands FirstLgnCmmands LcalAccunt Descriptin=<Admin> DisplayName=<Admin> Grup=<Administratrs> Name=<Admin> Passwrd Value=<passwrd> Micrsft Windws Internatinalizatin cre WinPE InputLcale=<lcale> SystemLcale=<lcale> UILanguage=<language> UserLcale=<language> SetupUILanguage UILanguage=<language> Micrsft Windws Setup UserData AcceptEula=true PrductKey Key=<prduct key> WillShwUI=OnErrr Step 5: Install clud-init Clud-init ( is an pen surce prject used with OpenStack t allw tls t integrate images in a clud. Cludbase ( develped a Windws versin and cntributed it t the cmmunity. It is available in a surce versin in github ( Frm the Cludbase website, yu can als find the easy-t-use install and cnfiguratin tl that is used in this step. The Cludbase tl autmatically generates its wn unattended file and ffers the ptin t autmatically step int running Sysprep. D nt select this ptin. Yu will nt have the pprtunity t mdify the unattended file with the ne yu created in step 4. Installing clud-init 1. Make sure all custmizatins fr the perating system are cmplete. 2. Dwnlad the clud-init installatin tl frm Cludbase fr Windws Install clud-init n the image. 4. Run CludbaseInitSetup_Beta. IMPORTANT: When yu finish using the setup tl, yu will be given the chice t run Sysprep directly. As discussed previusly, d nt chse this ptin. It will nt allw yu t integrate yur wn unattended file. 5. Cmplete the Cludbase-Init Setup Wizard. a. Accept the license agreement. b. On the Custm Setup screen, select the ptin fr Windws Clud Init (Default) and set the lcatin t C:\Prgram Files (x86)\cludbase Slutins\Cludbase-Int\(Default). c. On the Cnfiguratin ptins screen, fill in the ptins that are used t cnfigure the cludint.cnf file. This file is prcessed by clud-init scripts when an instance is launched. The.cnf files are created in C:\Prgram Files (86)\Cludbase Slutins\Cludbase-Init\cnf. i. Username: <Admin> 8

9 ii. Use this field t prmpt the clud-init package t create a user accunt with this name. This accunt will nt appear in the unattended file and shuld nt be added there. Metadata passwrd: <Check this bx> If yu check this bx, then the clud-init scripts that run at launch in the VM will lk in the blck f data ( metadata ) handed t it frm the CludSystem Nva layer fr a passwrd t assign t the accunt. The metadata passwrd is set by an interactive user in the CludSystem Prtal launch instance dialg as Admin Passwrd field. IMPORTANT: Yu cannt use the CludSystem Prtal t verify that the passwrd entered by the user meets the plicy set in the Windws image. Fr example, if a strng passwrd is set in the Windws OS, the user can enter a passwrd in the CludSystem Prtal that des nt cnfrm and n errr will ccur. The passwrd will nt be set in the image. iii. User s lcal grup: <Administratr> This is the grup assciated t the accunt. iv. Netwrk adapter: Intel PRO/1000MT This varies depending n the type f adapter yu are using. Make sure t enter the type f netwrk adapter used in yur cnfiguratin. d. De-select the Run Sysprep ptin. If this ptin is NOT selected, then yu will be able t merge yur wn unattended file befre yu run Sysprep. e. Select Finish. f. Verify the.cnf file created by the setup prgram. Sample.cnf file Step 6: Run Sysprep Sysprep prepares the image with specific Windws values that are set n bt based n the unattended files created in step 4. It is als required by the clud-init package in step 5. If yu are nt using step 4 r step 5, then yu can skip this step. All image behavir and settings cnfigured in Step 2 will be applied t the image. Running Sysprep 1. Take a snapsht f the VM r make a clne. After Sysprep runs, the image is transfrmed int its first bt cnfiguratin. Make all f yur custmizatins befre yu prceed. Taking a snapsht f the underlying VM befre this step culd be useful if yu need t rllback and crrect the image after a trial run. 2. Optinal: Create the final unattended file. At this pint yu will ptentially have an unattended file created by the Cludbase install tl in step 5 and ne yu created using SIM in step 4. If yu have bth, yu will need t merge them int ne file. If yu have nly ne, yu can skip this step. 9

10 a. Review the unattended file created by the Cludbase tl at: C:\Prgram Files (x86)\cludbase Slutins\Cludbase-Init\cnf. The highlighted sectin in the fllwing example shws the clause that invkes the clud-int pythn script. Cpy yur wn custm unattended file t this directry. Sample unattended file created by Cludbase tl b. Cpy the custm unattended file yu created t C:\Prgram Files (x86)\cludbase Slutins\Cludbase-Init\cnf. The previus example that sets the Administratr passwrd is shwn belw. 10

11 Sample with Administratr passwrd c. Merge the tw files and make any final mdificatins, then create a unique name fr the file, such as mergedunattended.xml. In the fllwing example, the clause t set the Administratr passwrd in the custm unattended.xml has been merged int the Cludbase_unattended.xml. 11

12 Sample merged unattended file 3. Run Sysprep: a. Munt the distributin media as the first DVD f the VM. b. Open a cmmand r pwershell CLI windw. c. Change directry t the Cludbase cnfiguratin directry C:\Prgram Files (x86)\cludbase Slutins\Cludbase-Init\cnf. d. Run Sysprep: c:\windws\system32\sysprep\sysprep.exe /be /generalize /unattend:mergedunattend.xml When Sysprep cmpletes, it will shut dwn the VM. e. In VMware, detach the distributin media frm the VM DVD drive. 12

13 Step 7: Set required VMware image prperties with VMware tls CludSystem supprts tw VMDK frmats: flat and sparse. Flat files are generally larger and slwer t uplad. They cnsume mre strage than a sparse VMDK. T prepare a flat image, yu must use vmkfstls with -d eagerzeredthick. Unlike a sparse image, yu d nt have t set a specific flat prperty fr use with CludSystem. IMPORTANT: In flat files, yu must use the eagerzered thick ptin with vmkfstls. Sparse images are smaller, which imprves uplad times and strage cnsumptin. T prepare a sparse image, yu must use vmware-vdiskmanager. T wrk prperly, a sparse file must have a prperty set in Glance t indicate that it is sparse befre it is laded int CludSystem. This prperty is cvered in step 8. IMPORTANT: In sparse files, yu must use the -t 0 ptin with vmwre-vdiskmanager. When chsing between the sparse r flat frmats, keep in mind that at launch a sparse file is expanded, which culd cause an additinal initial delay the first time it is used. Flat images d nt have this delay. The image that is cached n the ESX hsts after the initial use is the expanded file, which is the cause f the ne-time delay. Preparing a Flat frmat VMDK Yu can prepare a flat VMDK n the ESXi server in yur develpment envirnment. In rder t lg n t an SSH sessin and run vmkfstls, yu must enable SSH access t the server. 1. Enable SSH access n the ESXi server. a. In VMware vsphere Client, select the ESXi hst where yu are preparing the image. b. Enable the ESXi SSH shell access by selecting the fllwing ptins in Cnfiguratin Security: i. Services Prperties SSH shuld be set t running ii. Firewall Prperties Required Services, Secure Shell, SSH Server shuld be enabled. 2. Open an SSH shell t the ESXi server where the image is being prepared. 3. Change directry t the datastre where the image is stred. 4. Run the fllwing cmmand t review the image size: # ls l 5. Use the vmkfstls t set eagerzeredthick : vmkfstls -i <OriginalImage>.vmdk <NewImage>.vmdk -d eagerzeredthick Preparing a Sparse frmat VMDK T set the required sparse prperties fr a sparse VMDK, yu must use the vmware-vdiskmanager tl. 1. Dwnlad and Install vmware-vdiskmanager n a Windws server. The Virtual Disk Manager Utility is available with a VMware wrkstatin r yu can dwnlad it separately as a Virtual Disk Develpment Kit (VDDK). VDDK is available fr dwnlad at The Virtual Disk Manager User Guide is available at tpic/cm.vmware.icbase/pdf/vddk_disk_utils.pdf. 2. Cpy the image VMDK frm the develpment ESXi server t the Windws server and examine the size f the file. 3. Frm the Windws server, run the VMware-vdiskmanager tl: Vmware-vdiskmanager r <OriginalImage>.vmdk t 0 <NewImage>.vmdk 13

14 Step 8: Lad images int CludSystem There are tw ways t make images available fr users in CludSystem: Uplad the image int the CludSystem Glance repsitry n the CludSystem management appliance. Present the image n an accessible HTTP server t CludSystem. There are three tls available fr image uplad: CLI ptin fr images 20 GB r greater. See Using the CLI t uplad an image CludSystem Prtal ptin See Using the CludSystem Prtal t uplad an image CludSystem Cnsle ptin See Using the CludSystem Cnsle t uplad an image Using the CLI ptin t uplad an image 1. Install the CLI package that cntains the Glance image-create ptin. Fr instructins n installing the CLI packages fr Windws and Linux, see the HP CludSystem 8.1 Installatin and Cnfiguratin Guide in the Enterprise Infrmatin Library. 2. Frm the CLI, run the cmmand t uplad an image: glance --insecure image-create <Image Name> IMPORTANT: Yu can set the CludSystem prperties fr the image in the uplad cmmand using the --prperty flag. If yu want t add the prperties at this pint, see step 9. Using the CludSystem Prtal t uplad an image 1. Open a supprted brwser t Check the brwser uplad limitatins. Chrme tends t supprt the largest uplad size at 20 GB. If the image is larger than this, yu must use the CLI uplad ptin. 2. Frm the CludSystem Prtal Prject tab, select Images & Snapshts. 3. Uplad the image: a. Click + Create image. b. Enter a name fr the image. c. Enter a descriptin fr the image. d. Fr the image surce, select Image File. e. Fr the image file, brwse t the file yu want t uplad. f. Fr the frmat, select VMDK. g. Enter the minimum disk value t assign t the image. If yu chse t add a value, it will be the smallest available disk size f the image when launched as a VM. Users can cntrl the size using flavrs, but regardless f the value in the flavr, this setting will be the lwer limit. h. Enter the minimum RAM value fr the image. If yu chse t add a value, it will be the lwest RAM available t the image when launched as a VM. Users can cntrl the value using flavrs, but regardless f the value in the flavr, this setting will be the lwer limit. i. Select the Public check bx. j. Click Create image. 14

15 Using the CludSystem Cnsle t uplad an image 1. Open a supprted brwser t Check the brwser uplad limitatins. Chrme tends t supprt the largest uplad size at 20 GB. If the image is larger than this, yu must use the CLI uplad ptin. 2. Frm the CludSystem Cnsle, select Images Actins Add. 3. Enter the image details: a. In the Specify image field, click the Enter file URL radi buttn and enter the path t the URL in the field prvided. b. Enter a name fr the image. c. Enter a descriptin fr the image. d. Fr the OS type, select Micrsft Windws. e. Fr the disk frmat, select VMDK. f. Fr the cntainer frmat, select bare. g. Fr the shared field, select Enabled. h. Fr the Read-nly field, select Disabled. i. Click Add. Presenting the image n an HTTP server that is accessible t CludSystem 1. Mve the image t the HTTP server. Cnfiguratin f the HTTP server is beynd the scpe f this white paper. 2. Frm the CludSystem Cnsle, pint t the image frm CludSystem. 3. Navigate t Images Actins Add. 4. Enter the image details: a. In the Specify image field, click the Enter file URL radi buttn and enter the path t the URL in the field prvided. b. Enter a name fr the image. c. Enter a descriptin f the image. d. Fr the OS type, select Micrsft Windws. e. Fr the disk frmat, select VMDK. f. Fr the cntainer frmat, select bare. g. Fr the shared field, select Enabled. h. Fr the Read-nly field, select Disabled. i. Click Add. Step 9: Set required CludSystem prperties Windws VMDKs need the fllwing prperties set in CludSystem: vmware_stype=<ostype> (required with CludSystem) Examples windws8server64guest fr Windws 2012 windws7server64guest fr Windws 2008 See VMware dcumentatin fr a cmplete list f Windws related OS type cdes. VMware 5.5 dcumentatin: 55/index.jsp?tpic=%2Fcm.vmware.wssdk.apiref.dc%2Fvim.vm.GuestOsDescriptr.GuestOsIdentifier.html vmware_adaptertype=lsilgicsas (required with CludSystem) vmware_disktype=sparse (required if yu are using a sparse frmat VMDK) min_disk=<value in GB> (cmmn prperties fr all images) min_mem=<value in MB> (cmmn prperties fr all images) 15

16 Setting required CludSystem prperties 1. Install the CLI package yu plan t use. T set the required prperties yu will need t use the cmmand line. Fr instructins n installing the CLI packages fr Windws and Linux, see the HP CludSystem 8.1 Installatin and Cnfiguratin Guide in the Enterprise Infrmatin Library. 2. T cnfirm that the image is laded in CludSystem, run: glance --insecure image-list 3. T cnfirm that the initial image prperties are set, run: glance --insecure image-shw <ImageName> 4. Set the prperties using the Glance CLI cmmand with the image-update ptin and -prperties flag: Fr a Windws 2012 image that is a sparse VMDK glance -insecure image-update <ImageName> --prperty vmware_stype=windws8server64guest --prperty vmware_adaptertype=lsilgicsas prperty vmware_disktype=sparse Fr a Windws 2012 image that is a flat VMDK glance insecure image-update <ImageName> --prperty vmware_stype=windws8server64guest --prperty vmware_adaptertype=lsilgicsas 5. T cnfirm that the image prperties are set, run: glance --insecure image-shw <ImageName> Test the images by launching them as instances. Verify that the settings yu selected are accurate. Learn mre abut CludSystem Cpyright 2014 Hewlett-Packard Develpment Cmpany, L.P. The infrmatin cntained herein is subject t change withut ntice. The nly warranties fr HP prducts and services are set frth in the express warranty statements accmpanying such prducts and services. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. HP shall nt be liable fr technical r editrial errrs r missins cntained herein a, December