#557 Drop CloudFS as an F15 feature
Closed None Opened 13 years ago by jdarcy.

I'd like to suggest, or at least open a discussion about, pushing cloudfs to F16 instead. It's not that it doesn't work, but I think it's insufficiently usable/useful as-is compared to how it could be in six months. My concern is that making it generally available now could create work and distractions that would only slow needed work, and also cause negative user experiences that would kill interest in what I still think is a fundamentally strong feature set. Specifically:

  • The user experience is terrible, requiring far too many manual steps and far too much knowledge of how glusterfs already works. Partly this is a technical failure on my part, not figuring out the right integration points. Mostly, though, it's a matter of needing a far "thicker" layer of integration and administration tools than currently exist.

  • The use cases for the multi-tenancy feature also more often than not mandate dynamic user (tenant) and management, which is not there yet.

  • Stronger authentication and encryption are also must-haves for many potential users.

  • Quota and billing support are explicitly supposed to be part of the feature, and are simply not ready.

  • At least one user has mentioned that support for POSIX ACLs and/or SELinux would also make the result much more usable.

I understand that this puts more people than just me in a difficult position, and I apologize, but it seems that now is the time to ensure that neither the product nor Fedora's general reputation for quality are harmed. FWIW, I would consider a deferral an example of the Fedora process working - people thinking, talking, sharing ideas and deciding all before "going live" with something that just doesn't meet quality standards or advance our shared goals.


I see no reason for FESCo to override the feature owner's wishes in general, so it's fine by me.

Same here.

I'll add however: Would it make sense for this to be some kind of "Tech Preview" for f15? ie, note that it exists and needs work and is only for developers/early adopters?
Or would that cause too much of the distractions you are seeking to avoid?

I think a "tech preview" that marks it as being suitable only for developers (and other similarly-inclined early adopters) would be quite suitable. Is there a precedent for that?

We did this for systemd in f14 ( http://fedoraproject.org/wiki/F14_one_page_release_notes ) which may not be a great example. ;)

We also did it for gnome shell in f14 I think.

It's worth noting that these didn't appear as "Features" per se, they just appeared in the release notes as tech previews. Perhaps we could ask docs/marking folks how they might want to handle this.

From a marketing perspective, I'm perfectly fine with labelling it as a technology preview.

FESCo is fine with either option here:

  1. Repoint the feature to f16.

  2. Have it in F15 as a "tech preview". Note that we don't have much process here for tech preview, so I could you ask docs and marketing about this?

At this point, mostly based on the concern that the potential consequences of misconfiguration or undetected incompatibility with other software are highly likely to include data loss, my preference would be to re-target for Fedora 16. That way we should have enough time to make sure that configurations are more idiot-proof, and also to test across a much broader range.

+1 for delaying to F16

SMP

So, I am going to go ahead and close this now.

Feel free to remove the feature from the list for f15... and thanks.

Login to comment on this ticket.

Metadata