Bug 1417231

Hi Derek, this would require documentation for OSP 10 and OSP 11 (which should be the same info in both).

Already assigned to Dan -- I'll ensure he's seen your note.

Hi Ramon,

Just a quick question -- You said whole disk image support is available in OSP10, but the article linked above says that the feature officially landed in Ocata (OSP11). Can you clarify the version support?

Hi Dan, support OSP 10 is unfinished from what I can see in BZ#1434350. Probably better work with Yolanda's documentation for OSP 11 only at this point.

Hi Yolanda, you targeted this for OSP 10 but I believe the Newton backport it's unfinished at this point.

It has been requested but is on progress. I started with the backport in upstream but is sort of blocked by unexpected problems in the TripleO CI. I hope it can land this week.

Hi, thanks for taking that. 
I have several comments...
parititioning -> typo, partitioning

When explaining the steps, you miss the dracut regeneration. So by default, overcloud-full.qcow2 comes without support for volumes. We need to update dracut to add it (and also add crypt in case you want encryption):
dracut_content = """
add_dracutmodules+="lvm crypt"
"""

Also, when testing that, i found that we have a sizing problem when applying TripleO on top of the whole disk images. So the right partitions sizes could be:

logical_volumes = {
  'root': 4 * 1024,
  'swap': 250,
  'home': 100,
  'tmp':  500,
  'var':  5 * 1024
}

Also, it will be worth to mention about encryption? I created a blogpost here: http://teknoarticles.blogspot.com.es/2016/12/how-to-encrypt-your-home-with-guestfs.html. Encryption of some partition may be an interesting use case as well, for security reasons.

About creating an automated system, it's WIP and it's targetted for pike. It will use diskimage-builder to create the partitions and volumes, and TripleO will provide that whole disk image by default. See https://blueprints.launchpad.net/tripleo/+spec/build-whole-disk-images

Thanks for the update, it looks good to me.

Excellent. I've merged this into OSP11.

Peer review planned for post-GA.

I need to do an additional correction. The method i describe for encryption works for secondary partitions, but fails when encrypting the root one. The fix is simple, we need to add rd.auto=1 to the bootloader. Could you amend the document, and add this small fix?

# add rd.auto=1 on grub parameters
g.sh('sed  -i "s/.*GRUB_CMDLINE_LINUX.*/GRUB_CMDLINE_LINUX=\\"console=tty0 crashkernel=auto rd.auto=1\\"/" /etc/default/grub')

Before the line:

g.sh('grub2-install --target=i386-pc /dev/sdb')

This will add the right parameters to the bootloader. I verified today and that works.
Thanks!

Sorry, another fix needed, to make it work with selinux. Please see updated blogpost http://teknoarticles.blogspot.com.es/2016/12/start-using-whole-disk-images-with.html

In order to work with selinux, it needs a proper relabel. So we need to include those lines:

# do a selinux relabel
g.selinux_relabel('/etc/selinux/targeted/contexts/files/file_contexts', '/', force=True)
g.selinux_relabel('/etc/selinux/targeted/contexts/files/file_contexts', '/var', force=True)

In the same order as the blogpost references

Hi Dan, how is status on the article, with the latest corrections i added?

Hi Yolanda,

I was recently contacted by Mike Lammon on updating the script. I've added the version from the blog post:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#automatically_creating_a_whole_disk_image

Does it need any further updates?

Ok, the changes for the selinux relabel look good. However, i find that the sample that was provided for encrypting home, is weird. The script looks incomplete, the good one is at: http://teknoarticles.blogspot.co.id/2016/12/how-to-encrypt-your-home-with-guestfs.html

Hi Yolanda,

I've updated with the latest version of the encrypted script:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#encrypting_volumes_on_whole_disk_images

Originally I used a cutdown version to save some space. However, it might be best to use the original script since that's what was QE'd.

What do you think?

Now that BZ#1434350 is verified, the same steps for creating whole-disk overcloud in OSP 10 can be added, as soon as OSP 10.z3 is published.

Yolanda, has the encryption also been verified? BZ#1434350 only verified the whole-disk overcloud image support.

(In reply to Ramon Acedo from comment #19)
> Now that BZ#1434350 is verified, the same steps for creating whole-disk
> overcloud in OSP 10 can be added, as soon as OSP 10.z3 is published.
> 
> Yolanda, has the encryption also been verified? BZ#1434350 only verified the
> whole-disk overcloud image support.

If it hasn't been verified, should I remove the encryption script?

I've backported the Whole Disk Image content to OSP10 (minus the encryption content as per Ramon's comment in comment #29).

It's published here:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/director_installation_and_usage/#appe-Whole_Disk_Images

How does it look?

Ok looks good to me

Thanks, Yolanda!