You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ozone.apache.org by Siyao Meng <sm...@cloudera.com.INVALID> on 2020/06/23 18:34:20 UTC
[DISCUSSION] Making OFS the default, deprecating o3fs
Fellow Ozone developers,
I am thinking of making OFS the default since it should be the way
forward. The main reason I am sending this email is that I am about to do
some work to deprecate o3fs and replace existing o3fs paths in the existing
user guides with OFS ones. Also, new tests will be added to test OFS (e.g.
MapReduce acceptance tests). OFS follow-up work uber jira is created
at HDDS-3820.
At least for the upcoming 0.6.0 release, both o3fs and OFS will be usable
on the client. o3fs won't be gone any time soon.
If you have any concerns, comments and suggestions. Feel free to discuss
it in this thread. Thanks!
Cheers,
Siyao Meng
Re: [DISCUSSION] Making OFS the default, deprecating o3fs
Posted by "Elek, Marton" <el...@apache.org>.
I am fine with replacing the defaultFs in our tests but have two comments:
1. Would be great to test Hive, HBase, Spark (any other?) before we
recommend to replace o3fs/ofs
2. Would be great to test o3fs and ofs with all the tests with the
same way (until o3fs is deleted).
Do we need to run tests with both defaultFs?
Marton
On 6/23/20 8:34 PM, Siyao Meng wrote:
> Fellow Ozone developers,
>
> I am thinking of making OFS the default since it should be the way
> forward. The main reason I am sending this email is that I am about to do
> some work to deprecate o3fs and replace existing o3fs paths in the existing
> user guides with OFS ones. Also, new tests will be added to test OFS (e.g.
> MapReduce acceptance tests). OFS follow-up work uber jira is created
> at HDDS-3820.
>
> At least for the upcoming 0.6.0 release, both o3fs and OFS will be usable
> on the client. o3fs won't be gone any time soon.
>
> If you have any concerns, comments and suggestions. Feel free to discuss
> it in this thread. Thanks!
>
> Cheers,
> Siyao Meng
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSSION] Making OFS the default, deprecating o3fs
Posted by Arpit Agarwal <aa...@cloudera.com.INVALID>.
A clarification: There is no "default file system” in a freshly installed Ozone cluster today because o3fs is bucket-rooted. With ofs we can now configure a default FS out of the box. o3fs is not really being deprecated yet, it will remain as before and can still be configured.
Siyao, I suggest we update docs/examples to use ofs, but leave a pointer to o3fs docs for now.
Thanks,
Arpit
> On Jun 24, 2020, at 8:50 AM, Wei-Chiu Chuang <we...@cloudera.com.INVALID> wrote:
>
> Sounds good to me as long as we make sure all user docs are updated to use
> o3fs as examples.
>
> On Tue, Jun 23, 2020 at 11:35 AM Siyao Meng <sm...@cloudera.com.invalid>
> wrote:
>
>> Fellow Ozone developers,
>>
>> I am thinking of making OFS the default since it should be the way
>> forward. The main reason I am sending this email is that I am about to do
>> some work to deprecate o3fs and replace existing o3fs paths in the existing
>> user guides with OFS ones. Also, new tests will be added to test OFS (e.g.
>> MapReduce acceptance tests). OFS follow-up work uber jira is created
>> at HDDS-3820.
>>
>> At least for the upcoming 0.6.0 release, both o3fs and OFS will be usable
>> on the client. o3fs won't be gone any time soon.
>>
>> If you have any concerns, comments and suggestions. Feel free to discuss
>> it in this thread. Thanks!
>>
>> Cheers,
>> Siyao Meng
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSSION] Making OFS the default, deprecating o3fs
Posted by Jitendra Pandey <ji...@cloudera.com.INVALID>.
I think we should not be deprecating o3fs. It is ok to make 'ofs' default.
o3fs couldn't be a default anyway because it needs a bucket created.
However, let's not rush to delete o3fs.
We can have both ofs and o3fs around, they have their own respective
advantages. A few releases down the line, we may have more data on which
file system sees more adoption.
For example, consider multi-tenant use cases where a customer wants
isolated namespaces for two different business units. For a hybrid cloud
deployments, where a user wants to migrate data between ozone buckets and
s3 buckets, o3fs may turn out to be more conducive, given the file system
is rooted in an ozone bucket, similar to a s3 bucket in the cloud.
That said, I am +1 to following:
- Offer 'ofs' as the default file system.
- Update documents to reflect ofs, but keep a section for o3fs as well
for folks who have tried o3fs in the past and want to continue using it.
- Add ofs tests, but keep o3fs tests around so that it doesn't regress.
- Evangelize 'ofs' as the primary file system offering, as it is easier
to use.
On Wed, Jun 24, 2020 at 8:50 AM Wei-Chiu Chuang
<we...@cloudera.com.invalid> wrote:
> Sounds good to me as long as we make sure all user docs are updated to use
> o3fs as examples.
>
> On Tue, Jun 23, 2020 at 11:35 AM Siyao Meng <sm...@cloudera.com.invalid>
> wrote:
>
> > Fellow Ozone developers,
> >
> > I am thinking of making OFS the default since it should be the way
> > forward. The main reason I am sending this email is that I am about to do
> > some work to deprecate o3fs and replace existing o3fs paths in the
> existing
> > user guides with OFS ones. Also, new tests will be added to test OFS
> (e.g.
> > MapReduce acceptance tests). OFS follow-up work uber jira is created
> > at HDDS-3820.
> >
> > At least for the upcoming 0.6.0 release, both o3fs and OFS will be
> usable
> > on the client. o3fs won't be gone any time soon.
> >
> > If you have any concerns, comments and suggestions. Feel free to
> discuss
> > it in this thread. Thanks!
> >
> > Cheers,
> > Siyao Meng
> >
>
Re: [DISCUSSION] Making OFS the default, deprecating o3fs
Posted by Wei-Chiu Chuang <we...@cloudera.com.INVALID>.
Sounds good to me as long as we make sure all user docs are updated to use
o3fs as examples.
On Tue, Jun 23, 2020 at 11:35 AM Siyao Meng <sm...@cloudera.com.invalid>
wrote:
> Fellow Ozone developers,
>
> I am thinking of making OFS the default since it should be the way
> forward. The main reason I am sending this email is that I am about to do
> some work to deprecate o3fs and replace existing o3fs paths in the existing
> user guides with OFS ones. Also, new tests will be added to test OFS (e.g.
> MapReduce acceptance tests). OFS follow-up work uber jira is created
> at HDDS-3820.
>
> At least for the upcoming 0.6.0 release, both o3fs and OFS will be usable
> on the client. o3fs won't be gone any time soon.
>
> If you have any concerns, comments and suggestions. Feel free to discuss
> it in this thread. Thanks!
>
> Cheers,
> Siyao Meng
>