Re: emperor leftovers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The portability blueprint isn't complete, but is also well underway.  That 
may merit a quick session to discuss the balance of the summit.  I'm also 
curious if the discussion on windows portability is relevant here or if 
it's better treated as a separate but related effort.  I suspect making 
things like cephfs and librados build on windows will mean providing 
alternate implemantations of things like Mutex, Cond, Thread, and so 
forth.

Others:

http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_multitenancy
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_bucket_index_scalability
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_plugin_architecture
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Create_and_Maintain_S3_feature_list_for_compatibility_tracking
http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/Client_Security_for_CephFS
http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/create_crush_library

sage

On Thu, 7 Nov 2013, Patrick McGarry wrote:

> I have moved all of these to our new development "sideboard" [1] which
> can be used to store blueprints that don't make major releases.
> Alternately, if you have an idea and want help fleshing it out, this
> would be a great place to drop a blueprint for community
> collaboration.
> 
> [1] http://wiki.ceph.com/01Planning/Sideboard
> 
> 
> 
> Best Regards,
> 
> Patrick McGarry
> Director, Community || Inktank
> http://ceph.com  ||  http://inktank.com
> @scuttlemonkey || @ceph || @inktank
> 
> 
> On Thu, Nov 7, 2013 at 10:05 AM, Sage Weil <sage@xxxxxxxxxxx> wrote:
> > There are several blueprints that were put together for emperor even
> > though we didn't have the developer time to actually do them.  For anyone
> > interested in getting involved in Ceph development, these may present an
> > easy way to get involved in the process.  If you're interested in
> > adopting any of these orphan blueprints, speak up and we can make sure it
> > gets onto the firefly CDS schedule.
> >
> > In (very) approximate order of difficulty:
> >
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_shared_read_cache
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_namespace_support
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_copy-on-read_for_clones
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_dumpability
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/osd%3A_clone_from_journal_on_btrfs
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_reduce_memory_consumption
> >
> > sage
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux