https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-02-26T00:26:28ZCeph CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1595822020-02-26T00:26:28ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Subject</strong> changed from <i>mgr/volumes: Require an extension to the cephfs subvolume commands, that can return metadata regarding a subvolume</i> to <i>pybind/mgr/volumes: add command to return metadata regarding a subvolume</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>v16.0.0</i></li><li><strong>Backport</strong> set to <i>octopus,nautilus</i></li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1613792020-03-20T08:28:07ZKotresh Hiremath Ravishankar
<ul><li><strong>Assignee</strong> set to <i>Kotresh Hiremath Ravishankar</i></li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1615372020-03-24T12:43:26ZKotresh Hiremath Ravishankar
<ul></ul><p>Hi Shyam,</p>
<p>I have discussed this tracker with Venky and require clarification. The requirement to check the size and data pool is to know whether the subvolume creation is successful and ready to use? If that's the only case, the getpath cmd [1] returns the path only if the subvolume creation is successful and is ready to use, it doesn't return otherwise. Could getpath cmd<sup><a href="#fn1">1</a></sup> be used for the CSI requirement ? Or the CSI needs to know the size, data pool, and other metadata for other purposes as well?</p>
<p>[1] "fs subvolume getpath <vol_name> <sub_name> [<group_name>] "</p>
<p>Thanks,<br />Kotresh HR</p> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1615442020-03-24T13:45:01ZVenky Shankarvshankar@redhat.com
<ul></ul><p>Kotresh Hiremath Ravishankar wrote:</p>
<blockquote>
<p>Hi Shyam,</p>
<p>I have discussed this tracker with Venky and require clarification. The requirement to check the size and data pool is to know whether the subvolume creation is successful and ready to use? If that's the only case, the getpath cmd [1] returns the path only if the subvolume creation is successful and is ready to use, it doesn't return otherwise. Could getpath cmd<sup><a href="#fn1">1</a></sup> be used for the CSI requirement ? Or the CSI needs to know the size, data pool, and other metadata for other purposes as well?</p>
</blockquote>
<p>getpath will return -EAGAIN when the subvolume (or clone) is not ready for use. This is done here: <a class="external" href="https://github.com/ceph/ceph/blob/master/src/pybind/mgr/volumes/fs/operations/versions/subvolume_v1.py#L126">https://github.com/ceph/ceph/blob/master/src/pybind/mgr/volumes/fs/operations/versions/subvolume_v1.py#L126</a></p>
<blockquote>
<p>[1] "fs subvolume getpath <vol_name> <sub_name> [<group_name>] "</p>
<p>Thanks,<br />Kotresh HR</p>
</blockquote> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1615492020-03-24T15:14:09ZShyamsundar Ranganathan
<ul></ul><p>Venky Shankar wrote:</p>
<blockquote>
<p>Kotresh Hiremath Ravishankar wrote:</p>
<blockquote>
<p>Hi Shyam,</p>
<p>I have discussed this tracker with Venky and require clarification. The requirement to check the size and data pool is to know whether the subvolume creation is successful and ready to use? If that's the only case, the getpath cmd [1] returns the path only if the subvolume creation is successful and is ready to use, it doesn't return otherwise. Could getpath cmd<sup><a href="#fn1">1</a></sup> be used for the CSI requirement ? Or the CSI needs to know the size, data pool, and other metadata for other purposes as well?</p>
</blockquote></blockquote>
<p>The need is not to determine if the subvolume exists, but its attributes. This is to match if the subvolume that is found satisfies the request in terms of size, which data pool is chosen, and other related attributes.</p>
<p>There are times when a subvolume creation maybe interrupted, post which we will (using the CSI journal in RADOS) determine the name of the subvolume, at this point we need to read additional meta-data regarding the subvolume to ensure it fits the current request, or is a name/attribute conflict with the original request that may have been interrupted.</p> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1617472020-03-26T13:18:48ZKotresh Hiremath Ravishankar
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Pull request ID</strong> set to <i>34210</i></li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1624582020-04-03T06:17:31ZJos Collin
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Fix Under Review</i></li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1634862020-04-17T15:23:26ZGreg Farnumgfarnum@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1637422020-04-22T10:29:54ZRamana Rajarraja@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-5 priority-high3 closed" href="/issues/45180">Backport #45180</a>: octopus: pybind/mgr/volumes: add command to return metadata regarding a subvolume</i> added</li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1637452020-04-22T10:34:55ZRamana Rajarraja@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-5 priority-high3 closed" href="/issues/45181">Backport #45181</a>: nautilus: pybind/mgr/volumes: add command to return metadata regarding a subvolume</i> added</li></ul> CephFS - Feature #44277: pybind/mgr/volumes: add command to return metadata regarding a subvolumehttps://tracker.ceph.com/issues/44277?journal_id=1658402020-05-13T20:49:41ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>