You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
moctl tool with two main types of entities:
1 a mosaic (as a whole);
2 an (individual) volume.
These two types are very different in nature, but the moctl actions we use on them are sometimes intersect. In particular, moctl mount and moctl umount can refer to the mosaic or a volume, so we have to introduce a special volume name, -, meaning "the mosaic itself".
Currently, we have almost 10 volume-related commands, and only 3 mosaic commands (mount, umount and info). To avoid confusion, I propose to prepend the literal word mosaic for mosaic-related commands, leaving volume-related ones as is.
Example: moctl NAME mount - MOUNTPOINT --> moctl NAME mosaic mount MOUNTPOINT
The alternative I considered (and refused) is to use volume for where the volume name is, such as: moctl NAME mount volume VOLNAME MOUNTPOINT for volume, and moctl NAME mount MOUNTPOINT for the mosaic itself.
What do you think?
The text was updated successfully, but these errors were encountered:
Frankly, I see no problems with "moctl " semantics. Really. Yes, for some actions target can be only one of mosaic/volume, for some (mount and umount currently) they intersect, but reserving '-' as a volume name that means 'mosaic' in intersecting cases is OK. From my perspective.
moctl tool with two main types of entities:
1 a mosaic (as a whole);
2 an (individual) volume.
These two types are very different in nature, but the moctl actions we use on them are sometimes intersect. In particular,
moctl mount
andmoctl umount
can refer to the mosaic or a volume, so we have to introduce a special volume name,-
, meaning "the mosaic itself".Currently, we have almost 10 volume-related commands, and only 3 mosaic commands (
mount
,umount
andinfo
). To avoid confusion, I propose to prepend the literal wordmosaic
for mosaic-related commands, leaving volume-related ones as is.Example:
moctl NAME mount - MOUNTPOINT
-->moctl NAME mosaic mount MOUNTPOINT
The alternative I considered (and refused) is to use
volume
for where the volume name is, such as:moctl NAME mount volume VOLNAME MOUNTPOINT
for volume, andmoctl NAME mount MOUNTPOINT
for the mosaic itself.What do you think?
The text was updated successfully, but these errors were encountered: