This article will walk you through the steps required to deploy a new Porticor VM in your VMware environment.
First, a word about prerequisites.
- For production, we recommend to allocate the VM 4GB of memory. For testing (except for performance benchmarking), 1GB should be sufficient.
- The system disk can be either thin-provisioned or thick-provisioned.
- Make sure the VM is created on a network where it has outbound Internet connectivity. This is required so that the VM can connect to the Porticor Virtual Key Management service.
Ready to go? Here are the deployment steps:
- Download the virtual application, as an *.ova file (download details will be made available once you register).
- Use the vCenter console to deploy the application (File/Deploy OVF template).
- Ensure that the appliance is deployed with a local network address (either a static address from the IP pool or using DHCP). It is sometimes convenient for the address to persist across reboots, but it’s not a requirement, because of the persistent DNS address that we assign the appliance during deployment.
- Once the VM has been created, start it, wait until you can see its IP address and then access the URL: https://VM-address/ (note the use of HTTPS, and change the URL for the IP address of the new VM). The appliance is still not provisioned with a certificate, so ignore the SSL error.
- You are now redirected to the Porticor management application at pvkm.porticor.com, see screenshot below.
- If you are an existing Porticor customer, sign in using your Porticor credentials (the highlighted line at the top of the page); otherwise fill in the registration form.
- Follow the short wizard to activate your new Porticor VPD.
When you have a working appliance, you probably want to set up an encrypted disk:
- Create a new disk on vCenter and attach it to the appliance.
- Back on the appliance’s management GUI, press “Rescan Disk Volumes”. You should see the new disk.
- Use the GUI to expose the disk to your application, as iSCSI, NFS or a Windows share.
A special note for those using iSCSI with a Windows client: we have found that performance is significantly better if you map the iSCSI volume as a data store on vSphere and then use it for your application, compared to accessing it directly from the Windows iSCSI Initiator.