Conservative MIF graphs

[jamoore]

​spec.xml defines a number of graphs which can be used for deleting, chgrp'ing, etc. The current definitions are such that operating on an "/Image" walks up the graph to "/Fileset" and then back down to all other "/Images" inside the fileset.

The default behavior should become that chosing a single image in a MIF only operates on that image. This will lead to failures without special client handling. For delete, a "SOFT" option will make the deletion take place on the single image (which was considered acceptable).

Specific changes that need to be made

• spec.xml modified.
• Guarantee that a detectable error message is present on failure. (see #10779, etc)
• In cooperation with #10777 (i.e. without conflicts) tests reviewed.

Warn/Error? states

• When SOFT is passed for delete (likely to become the default for images. see #10779), it return value should contain list of filesets which were not completely deleted. This would allow the client to say "The data itself didn't get deleted becuase it's used by 5 more images"

[jamoore]

Petr filed this as a bug in #10460 which included specific real files that can be tested.