From: Joe Thornber <thornber@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178
Date: Tue, 12 Jun 2018 15:22:20 +0100 [thread overview]
Message-ID: <20180612142219.ixpzqxqws3qiwqbm@reti> (raw)
In-Reply-To: <5B1F8BE7020000F90002293C@prv1-mh.provo.novell.com>
On Tue, Jun 12, 2018 at 03:01:27AM -0600, Gang He wrote:
> Hello List,
>
> I saw there was a tag "v2_02_178-rc1" for LVM2, then I have some questions about the upcoming LVM v2_02_178.
> 1) Will there be the version v2_02_178 for LVM2? since I saw some text about Version 3.0.0 in the git change logs.
Yes there will be. We've had no bug reports for the -rc, so the final
release will be the same as the -rc.
> 2) For the next LVM2 version, which components will be affected? since I saw that clvmd related code has been removed.
We've decided to bump the version number to 3.0.0 for the release
*after* 2.02.178. This change in version number indicates the *start*
of some large changes to lvm.
Obviously the release notes for v3.0.0 will go into this more. But,
initially the most visible changes will be removal of a couple of
features:
clvmd
-----
The locking required to provide this feature was quite pervasive and
was restricting the adding of new features (for instance, I'd like to
be able to allocate from any LV not just PVs). With Dave Teigland's
lvmlockd I think the vast majority of use cases are covered. Those
that are wedded to clvmd can continue to use LVM2.02.*
Also, testing cluster software is terribly expensive, we just don't
have the resources to provide two solutions.
lvmapi
------
This library has been deprecated for a while in favour of the dbus api.
- Joe
next prev parent reply other threads:[~2018-06-12 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 9:01 [linux-lvm] Some questions about the upcoming LVM v2_02_178 Gang He
2018-06-12 14:22 ` Joe Thornber [this message]
2018-06-13 2:14 ` Gang He
2018-06-13 9:43 ` Joe Thornber
2018-06-14 2:14 ` Gang He
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=20180612142219.ixpzqxqws3qiwqbm@reti \
--to=thornber@redhat.com \
--cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).