All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: Batch/queue LVM operations
Date: Mon, 31 Jul 2017 11:19:46 +0200	[thread overview]
Message-ID: <d703293c-192c-c448-f2cb-cf1f5e374cbe@redhat.com> (raw)
In-Reply-To: <fcfc34d4-eb7e-ce89-b83f-39d4fff56cbb@citrix.com>

Dne 31.7.2017 v 11:01 Germano Percossi napsal(a):
> Hi,
> 
> Not sure if it an option for you but the Python bindings
> allow you to instantiate a VG object that will hold the
> lock and then issue all the commands you want before
> flushing the metadata at the very end.


Hi

Please avoid using these Python binding or lvm2app.
Those 2 things are not being developed and are mostly left
there purely for backward compatibility reasons. So no new APP should ever use 
it - and old APPs will simple face lots of troubles....

It's in general unsupportable to lvm2 this way (API was badly designed and
we even figured later we really can't support it ).
And it's even less usable to workaround locking across bunch of commands...

What is now being tested is dBus integration - but this has still long way to 
go.  So whenever you can - please use  lvm2 commands with is documented
and well tested API.


Regards

Zdenek



  reply	other threads:[~2017-07-31  9:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 19:22 Batch/queue LVM operations Eric Wheeler
2017-07-28 19:43 ` Zdenek Kabelac
2017-07-28 21:55   ` Eric Wheeler
2017-07-31 12:16   ` Bryn M. Reeves
2017-08-01 17:24   ` Eric Wheeler
2017-08-01 17:46     ` Zdenek Kabelac
2017-08-01 18:39       ` Zdenek Kabelac
2017-08-04  0:59         ` Eric Wheeler
2017-08-14 12:36           ` Zdenek Kabelac
2017-08-04  0:38       ` Eric Wheeler
2017-08-14 12:29         ` Zdenek Kabelac
2017-07-31  9:01 ` Germano Percossi
2017-07-31  9:19   ` Zdenek Kabelac [this message]
2017-07-31  9:22     ` Germano Percossi
2017-08-01 17:20     ` Eric Wheeler

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=d703293c-192c-c448-f2cb-cf1f5e374cbe@redhat.com \
    --to=zkabelac@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.