INSSL Applicance - Copying ssl_key volume

[kapow]

When I provision a new application based on my template which contains an INSSL appliance (non-branched), it is not copying over the contents of the ssl_key volume I created and configured.

Why is that? Do I need to branch the appliance for that to happen? I wouldn't think so since the ssl_key vol is a part of the template and it should be copying that out of the template on provisioning.

[kapow]

I discovered the problem.

When I created the volume to hold the key, I wanted the smallest volume possible. So, as stated in the documentation, is created a volume of file system type ext2. This allows you to create a volume of 1M in size. ext3 must be at least 5M.

The INSSL appliance was never mounting the volume because the fstab on the INSSL appliance explicitly states a file system type of ext3 when mounting /dev/hda3. You cannot mount an ext2 file system with that specification in fstab.

I recommend one of two changes to prevent other users from running into this problem. One, state in the INSSL Wiki page that the volume you create to hold your key must be of file system type ext3. Or, modify the INSSL appliance fstab to change the file system type from ext3 to auto to handle either type.

One other note. I recommend adding a note to the INSSL appliance Wiki page to let users know that you cannot create a volume to hold your key, mount it, and expect to run the key generation commands and get your server.pem to that volume as it is mounted read only. You either must branch the INSSL appliance and change the volume load options to read/write or create your server.pem somewhere else and scp it to that volume.