Suggested changes to lvm command line tools

Suggested changes to lvm command line tools

[Tony Asleson]

The following changes would be helpful for projects that are writing
wrappers for the lvm command line tools.

* Have an option to output JSON or XML for all operations
* When creating/modifying something, if it is successful, output all the
information about the newly created/modified object so that the user
doesn't need to turn around and query what they just created/changed.
Optionally if the change causes other objects in the system to change,
output those objects too if possible.  Otherwise the client needs to
'know' what side effects a change has and then query those affected
objects.  Not sure how easy or feasible this change would be.
* A mechanism for a client to know that a change has been made without
having to poll for changes.  For a lvm dbus daemon we could provide a
dbus method that can be used to signal the daemon that one or more
things have changed.

Thanks!

Regards,
Tony

Suggested changes to lvm command line tools

[Alasdair G Kergon]

On Tue, Feb 10, 2015 at 04:01:08PM -0600, Tony Asleson wrote:
> The following changes would be helpful for projects that are writing
> wrappers for the lvm command line tools.
 
Please open Fedora Rawhide bugzillas for each of the 3 items.
(We'll probably sub-divide them further, but that'll do for starters.)

Alasdair