F24 Self Contained Change: Anaconda Using LVM DBus API

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

 



= Proposed Self Contained Change: Anaconda Using LVM DBus API =
https://fedoraproject.org/wiki/Changes/Anaconda_Using_LVM_DBus_API

Change owner(s):
*  Vratislav Podzimek <vpodzime AT redhat DOT com>
* Jonathan Brassow <jbrassow AT redhat DOT com >

A new DBus API for LVM is being created so let's make the installation
process use it for setting up LVM storage.


== Detailed Description ==

For quite a long time there has been a request for a better API for
LVM than what the current CLI tools provide. After a quite long
discussion between the interested groups it has been decided that a
DBus API should be the best choice. The LVM team has thus been working
on a prototype implementation of such DBus API, but we ended up in a
circle between "there's not enough time spent on the LVM DBus API
because nobody's using it and thus it's not high priority" and
"nobody's using the LVM DBus API because there's not enough time spent
on it". To break this circle and get from the deadlock, we would like
to make the installation process use the LVM DBus API and thus pioneer
its usage for others and make sure it is maintained, improved and
considered a high-enough priority by the LVM team due to a real usage
in an important component of the system/distribution. The reasons for
why the installation process could be the first one to use the new API
are the following facts:

* anaconda+blivet are written in Python so the performance of the LVM
DBus daemon prototype also written in Python shouldn't be an issue
* anaconda+blivet only do basic operations with LVM in the
installation process so we could start with this limitted scope
* blivet uses libblockdev as its backend and libblockdev is modular
having the LVM functionality as a plugin which can be replaced with a
new plugin using the DBus API where possible while keeping the
old/current plugin as a backup solution if it turns out the LVM DBus
API is * not production ready even for the installation use case. This
results in a wonderful Contingency plan (see below).


== Scope ==

* Proposal owners: implement the LVMDBus libblockdev plugin
(vpodzime), make sure the LVM DBus daemon is packaged for Fedora and
production ready for the installation use case (jbrassow)
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
devel-announce mailing list
devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux