[REVIEW] Storage mounting API

Stephen C. Tweedie sct at redhat.com
Tue Mar 19 12:38:46 UTC 2013


Hi,

On Thu, 2013-03-14 at 16:10 +0000, Stephen C. Tweedie wrote:
> On Wed, 2013-03-13 at 16:29 +0100, Jan Synacek wrote:
> > As a follow-up to the
> > https://lists.fedorahosted.org/pipermail/openlmi-devel/2013-February/000046.html, I'm
> > hereby presenting the first version of the storage mounting API (attached).
> > 
> > This API doesn't include handling of /etc/fstab. That will be taken care of
> > later and differently.
> 
> Most of the storage API is currently persistent (naturally!); wouldn't
> it be natural for a mounting API to manage fstab transparently?  It
> would seem more consistent for mount/unmount operations to be persistent
> automatically.

Actually, it looks like there are some precedents for how to manage
persistent vs. runtime configuration like this.  In the network model,
we use

http://schemas.dmtf.org/wbem/cim-html/2.35.0+/CIM_ElementSettingData.html

which has various ways to refine the semantics of a config option,
including "isNext" which indicates a setting that will be applied on
reset/reconfiguration (which looks like it could map directly to whether
or not an entry is in fstab.)

Radek Novacek can describe better how this is used in the networking
models.  If it looks useful, it would be ideal if we can do this
consistently between networking and filesystems, as ports and mount
points have similar distinctions between current and on-reboot
configurations.

In particular, this would avoid having a subclass for persistent mounts,
which would mean we'd be able to keep the same existing class for a
mounted filesystem when we add or remove it in fstab.

Thanks,
 Stephen




More information about the openlmi-devel mailing list