I've found one more runtime issue with the apparmor profile. Eucalyptus can provide the ability to dynamically attach/detach block devices to VMs at runtime using libvirt attach-disk/detach-disk. We currently use AOE for dynamic block devices, and these appear on the node in:
/dev/etherd/e*
when a volume (dynamic block device) is created on a remote storage controller. I believe, then, that the apparmor profile may have to also include:
I've found one more runtime issue with the apparmor profile. Eucalyptus can provide the ability to dynamically attach/detach block devices to VMs at runtime using libvirt attach- disk/detach- disk. We currently use AOE for dynamic block devices, and these appear on the node in:
/dev/etherd/e*
when a volume (dynamic block device) is created on a remote storage controller. I believe, then, that the apparmor profile may have to also include:
/dev/etherd/e*
in order for this functionality to work.