Under Admin => Connections => Virtual Appliances create a New Cluster. To download the CentOS VMWare Image login to the Admin section of your IdentityNow Tenant. SailPoint Virtual Appliance CentOS VMWare Image We’ll need this to upload the converted virtual disk to Azure. The base image is ~2.8Gb and when converted to a fixed disk image it becomes ~128Gb (which can compress to ~3Gb for initial upload). Enough hard disk space for the VA image and the converted image.You could probably do it with other tools but I’ve used this before and it just works. Virtual Box (for the disk image converter).Log in and configure the Virtual Appliance.Create a new VM based off the VM from Step 3 to use the disk from Step 4 as the Operating System disk.Upload the VHD to the Azure Storage Account (associated with VM from Step 3) using Azure Storage Explorer.From the Azure MarketPlace create a Seed VM based on CentOS (with new Resource Group, Storage Account, Virtual Network etc).Convert the VMWare VMDK image to Hyper-V VHD format using VirtualBox vboxmanage (free).Obtain the CentOS Image from the IdentityNow Virtual Appliance Setup.This is the high-level process I threw together that worked for me. This isn’t an approved process or a support configuration. This blog post details how I got it working.ĭisclaimer: If you use this for more than a Sandpit/Test environment let your SailPoint CSM know. So I figured I’d convert the VM, get it into Azure and see if it works from my Sandpit environment. In discussions with SailPoint I understand it is simply a case that they haven’t certified their CentOS image on Azure. The CentOS image that SailPoint provide for the IdentityNow Virtual Appliance that performs integration between ‘Sources’ and IdentityNow is VMWare based. I don’t have any VMWare Infrastructure to run it on and really didn’t want to run up any VMWare environments for this component.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |