Skip to content

Running the Dradis Pro Appliance in an OpenStack environment

June 7, 2016

We use OpenStack as our lab IaaS and We use Dradis Pro for report generation and general note keeping. Prior to moving our entire lab in the OpenStack environment, we had deployed our Dradis Pro appliance in a VMWare environment which is what it supports, so that was no problem. But, now since we were moving everything into OpenStack, we had to migrate the Dradis appliance as well.

But, apparently nobody has tried installing Dradis Pro appliance in their OpenStack environment so I couldn’t really find anything online or in their forums/guides about it so I decided to give it a shot. Surprisingly, it was really easy.

  • The first step is to download the .ova file from your Dradis pro account at
  • You have to then tar the .ova file

    tar xvf dradis-professional-x86_64-20151122.ova

  • This generates a .vmdk and .ovf file. Ignore the .ovf file and convert the .vmdk file into a qcow2 formatted .img file. Install the qemu-img utility if you don’t have it already.

    qemu-img convert -O qcow2 dradis-professional-x86_64-20140331-disk1.vmdk dradis-appliance.img

  • At this point, you are pretty much done creating the image. You just have to upload this .img file to your OpenStack environment using the Glance API

    glance image-create –name=’dradis-appliance’ –container-format=bare –disk-format=qcow2 < dradis-appliance.img

    PS – The above step is not as trivial as I made it seem like. You would need to have your OpenStack environment variables set to those values that are required to connect to your OpenStack environment. You would also need the glance API installed. But, I am assuming you have already done all the leg work since this blog is not about connecting to your OpenStack environment.

  • The above glance image-create command might take some time depending upon how big the .img file is and how fast/slow your connection is. But, once it’s done, you should see the details of the image uploaded to your OpenStack environment.
  • So, now you have a valid image in your OpenStack lab and are ready to launch an instance from that image. I chose a m1.medium flavor (2 VCPUs, 80 GB root disk, 8192 MB RAM). Choose your access security groups and key pairs accordingly. Launch the instance.
  • Wait for a while. You should then see the console of this instance with “Enter the passphrase: “. Enter the default passphrase which you can find in your account at
  • Login as root and default credentials.
  • At this point, if you try navigating to https://<dradis-IP>/setup/upgrade, you might not see what you are expecting to see. So, in order to troubleshoot more, please follow this guide. I had to do this as well where I had to restart the god service after logging in the console before I could get to the dradis UI in the browser.

    sudo /etc/init.d/god restart

  • At this point, you should be all set to complete the remaining steps from the guide here.

PS – Don’t forget to change the default passphrase, login credentials, etc.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: