Unable to create filesystem on dmcrypt devices

[Akendo]

Hello guys,

I do run in some issue with including a devices as a OSD. I want to that the block devices to be encrypted. I unlock this via cryptsetup luksOpen /dev/sdb OSD-1. But the when ceph::osd::devices is creating a gpt on it, it assumes that the new partition can be access via ${name}1, but the block devices is offering it via /dev/mapper/OSD-1p1.

Here the piece of code that have to change:

  exec { "mkfs_${devname}":
    command => "mkfs.xfs -f -d agcount=${::processorcount} -l \
size=1024m -n size=64k ${name}1",
    unless  => "xfs_admin -l ${name}",
    require => [Package['xfsprogs'], Exec["mkpart_${devname}"]],
  }

I guess it would be better to read the printable of parted and then try to find the partition. For the moment I disable the creation of the partition table, there is no need for now.

In general you don't need to create partition tables. You only have to be aware not to run a grub-install on the disk. This indeed would overwrite the Superblock. But are you planning to separate the OSD Journal to extra partition?

Further this devices isn't able to get a UUID via facter. It only display this:

Notice: /Stage[main]/cloud::Osd/Ceph::Osd::Device[/dev/mapper/OSD-0]/Notify[BLKID FACT OSD-0: blkid_uuid_OSD-01]/message: defined 'message' as 'BLKID FACT OSD-0: blkid_uuid_OSD-01'
Notice: BLKID OSD-0: undefined
Notice: /Stage[main]/cloud::Osd/Ceph::Osd::Device[/dev/mapper/OSD-0]/Notify[BLKID OSD-0: undefined]/message: defined 'message' as 'BLKID OSD-0: undefined'

I could a workaround using /sbin/blkid to getting the UUID of the dmcrypt devices. But maybe this issue is related to my VM? I do use Ubuntu 12.04 with ruby 1.8.7 and puppet 3.2.2.

I'll may work on a fork and try to fix this, maybe add in some parameter to handles this?
Like to enable gpt or not and some fine work. For example defining the inode size. For performance reason you should use them with 2048.

so far
4k3nd0

[Akendo]

Update: I add some small stuff to make it work with dmcrypt. See TelekomCloud@ebf1c8a, I will add some parameter function later on.

so far
4k3nd0