Red Hat Bugzilla – Bug 977582
Make file extensions an internal detail of volume API
Last modified: 2016-09-19 21:43:31 EDT
The libvirt API provides a nice volume manipulation API and it more or less abstracts the app developer from underlying files. However, apps currently need to have an extension as part of the volume's name as libvirt maps volume's name directly to the name of the underlying file.
Since the format of the volume is known to libvirt, it can automatically assign the proper extension to the underlying file at the time of volume creation and free the app developer from worrying about file extensions.
For directory/fs volumes the convention has always been that volname==filename, so I'm not sure how we could deviate from that in this case. Maybe we could add an XML option for volume creation that says 'use the format as the file extension' but honestly I don't think it saves API users all that much work