You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Soumitra Sulav (Jira)" <ji...@apache.org> on 2021/09/30 08:26:00 UTC
[jira] [Updated] (HDDS-5801) ofs temp implementation different from
design doc
[ https://issues.apache.org/jira/browse/HDDS-5801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Soumitra Sulav updated HDDS-5801:
---------------------------------
Description:
As per the pull request guide, tmp volume is to be created by the user.
{code:java}
# ozone sh volume create tmp
{code}
tmp exists after creation as volume and shows on listoperation of root dir but can't be listed on lower level or put files on.
{code:java}
# ozone fs -ls ofs://ozone1/
Found 2 items
drwxrwxrwx - om om 0 2021-09-30 08:12 ofs://ozone1/tmp
# ozone fs -ls ofs://ozone1/tmp/
ls: `ofs://ozone1/tmp/': No such file or directory
# ozone fs -put anaconda-ks.cfg ofs://ozone1/tmp/
put: `ofs://ozone1/tmp/': No such file or directory
{code}
ofs implementation : https://github.com/apache/ozone/pull/610
Works on doing mkdir /tmp.
Other volumes don't need this extra step and is different than the usual behavior of other directories or volumes.
Also as per design [doc|https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf] : temp implementation has 4 policies to define user first interaction with temp dir.
Doc line:: "Users are allowed to change the mapping for /tmp/ later with Ozone Shell and API" isn't valid as per the implementation.
Design doc should rather be updated with the way implementation has been done.
was:
As per the pull request guide, tmp volume is to be created by the user.
{code:java}
# ozone sh volume create tmp
{code}
tmp exists after creation as volume and shows on listoperation of root dir but can't be listed on lower level or put files on.
{code:java}
# ozone fs -ls ofs://ozone1/
Found 2 items
drwxrwxrwx - om om 0 2021-09-30 08:12 ofs://ozone1/tmp
# ozone fs -ls ofs://ozone1/tmp/
ls: `ofs://ozone1/tmp/': No such file or directory
# ozone fs -put anaconda-ks.cfg ofs://ozone1/tmp/
put: `ofs://ozone1/tmp/': No such file or directory
{code}
ofs implementation : https://github.com/apache/ozone/pull/610
Works on doing mkdir /tmp.
Other volumes don't need this extra step and is different than the usual behavior of other directories or volumes.
Also as per design [doc|https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf] : temp implementation has 4 policies to define user first interaction with temp dir.
Design doc should rather be updated with the way implementation has been done.
Also "Users are allowed to change the mapping for /tmp/ later with Ozone Shell and API" isn't valid as per the implementation.
> ofs temp implementation different from design doc
> -------------------------------------------------
>
> Key: HDDS-5801
> URL: https://issues.apache.org/jira/browse/HDDS-5801
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone CLI
> Affects Versions: 1.1.0
> Reporter: Soumitra Sulav
> Priority: Major
>
> As per the pull request guide, tmp volume is to be created by the user.
> {code:java}
> # ozone sh volume create tmp
> {code}
> tmp exists after creation as volume and shows on listoperation of root dir but can't be listed on lower level or put files on.
> {code:java}
> # ozone fs -ls ofs://ozone1/
> Found 2 items
> drwxrwxrwx - om om 0 2021-09-30 08:12 ofs://ozone1/tmp
> # ozone fs -ls ofs://ozone1/tmp/
> ls: `ofs://ozone1/tmp/': No such file or directory
> # ozone fs -put anaconda-ks.cfg ofs://ozone1/tmp/
> put: `ofs://ozone1/tmp/': No such file or directory
> {code}
> ofs implementation : https://github.com/apache/ozone/pull/610
>
> Works on doing mkdir /tmp.
> Other volumes don't need this extra step and is different than the usual behavior of other directories or volumes.
> Also as per design [doc|https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf] : temp implementation has 4 policies to define user first interaction with temp dir.
> Doc line:: "Users are allowed to change the mapping for /tmp/ later with Ozone Shell and API" isn't valid as per the implementation.
> Design doc should rather be updated with the way implementation has been done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org