From: Vratislav Podzimek vpodzime@redhat.com
These are more high-level notes about changes done in the releases (at least major). Useful for people outside of the team, but also for us to easily find out when and in to what extent something was added. --- MANIFEST.in | 2 +- release_notes.rst | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-) create mode 100644 release_notes.rst
diff --git a/MANIFEST.in b/MANIFEST.in index 04720c6..2f5121b 100644 --- a/MANIFEST.in +++ b/MANIFEST.in @@ -1,3 +1,3 @@ -include COPYING ChangeLog Makefile python-blivet.spec +include COPYING ChangeLog Makefile python-blivet.spec release_notes.rst recursive-include po *.mo *.po *.pot Makefile recursive-include examples *.py diff --git a/release_notes.rst b/release_notes.rst new file mode 100644 index 0000000..57dcf04 --- /dev/null +++ b/release_notes.rst @@ -0,0 +1,34 @@ +2.0 +==== + +LVM RAID +--------- + +Blivet now recognizes and supports creation of new non-linear LVs. The segment +type is properly reported in the ``seg_type`` attribute of the +``LVMLogicalVolumeDevice`` objects and the ``seg_type`` constructor parameter +can be used to create new LVs with specific segment types. Please note that only +the *linear* (default), *striped*, *mirror* and *raidX* segment types are +supported so far. Also the ``LVMLogicalVolumeDevice`` class now inherits from +the ``RaidDevice`` mixin. + +Added properties: + +* ``LVMLogicalVolumeDevice`` + + - ``is_raid_lv``, ``mirrored`` + + - ``data_vg_space_used``, ``metadata_vg_space_used`` - space used by the + data/metadata part of the LV in its VG taking the RAID level (i.e. the + number of mirrors) into account + +* ``LVMPhysicalVolume`` + + - ``free`` - free space in the PV (for all existing and non-existing PVs) + + +Removed properties: + +* ``LVMLogicalVolumeDevice`` + + - ``copies``
anaconda-patches@lists.fedorahosted.org