All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Asleson <tasleson@redhat.com>
To: lvm-devel@redhat.com
Subject: Suggested changes to lvm command line tools
Date: Tue, 10 Feb 2015 16:01:08 -0600	[thread overview]
Message-ID: <54DA7FA4.9060404@redhat.com> (raw)

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



             reply	other threads:[~2015-02-10 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 22:01 Tony Asleson [this message]
2015-02-10 22:48 ` Suggested changes to lvm command line tools Alasdair G Kergon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54DA7FA4.9060404@redhat.com \
    --to=tasleson@redhat.com \
    --cc=lvm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.