[LSF/MM TOPIC] Bringing Virtual Data Optimizer (VDO) to upstream

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I'd like to talk about Virtual Data Optimizer (VDO), which is a
device-mapper target that provides deduplication, compression, thin
provisioning, and zero-block elimination for primary storage.  Now
that VDO is open-source, LSF/MM would be a good time to open a
dialogue between other upstream developers as we work to bring VDO
upstream.

VDO was originally developed by Permabit Technology Corporation as a
proprietary set of kernel modules and userspace tools.  After being
acquired by Red Hat, VDO has been re-licensed under the GNU General
Public License, version 2.  The VDO team has also been working a lot
closer with Mike Snitzer and other developers of device-mapper and
LVM.

The source for VDO is available at the following repositories:

https://github.com/dm-vdo/kvdo (kernel modules)
https://github.com/dm-vdo/vdo (userspace tools)

As the README files in the repositories above indicate, development on
VDO is currently focusing on upstream integration, which includes
various coding standards compliance changes, refactoring efforts, and
various other changes that become possible now that VDO is re-licensed
under the GPL.

That being said, VDO has been in production use since 2014 in its
previous proprietary form, and continues to undergo thorough testing,
including real-world test scenarios.


Thanks,

Bryan

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux