Open Stack

Hello all,

Refstack development is tracked on launchpad. Also feel free to contact me directly if you have questions.

https://launchpad.net/refstack
has links to everything else.

Thanks
David Lenwell

On May 19, 2014 7:34 PM, Joshua McKenty <joshua at pistoncloud.com> wrote:
>
> Adding David Lenwell to this. David's got the backlog somewhere. 
>
> Sent from my iPhone 
>
> > On May 19, 2014, at 2:52 PM, John Dickinson <me at not.mn> wrote: 
> > 
> > That sounds like a good goal, and I think it's something we can shoot for. Getting refstack to use the existing functional tests is probably simpler that migrating to a new testing framework. (To be clear, I'm not opposed to moving existing testing to tempest, long-term.) 
> > 
> > Where is refstack tracked? Is there a task tracker somewhere that I can follow? 
> > 
> > --John 
> > 
> > 
> > 
> > 
> >> On May 19, 2014, at 2:39 PM, Joshua McKenty <joshua at pistoncloud.com> wrote: 
> >> 
> >> Love it! 
> >> 
> >> We need a mapping from each capability, to the set of tests that demonstrate it. As per our conversation, I assume this means either migrating those tests from swift into tempest, or extending RefStack to run them independently. Regardless, does that seem like something that can be done in Juno timeframe? 
> >> 
> >> 
> >> 
> >> Sent from my iPhone 
> >> 
> >>> On May 19, 2014, at 2:32 PM, John Dickinson <me at not.mn> wrote: 
> >>> 
> >>> Sitting on the plane to Atlanta last week, here's my first draft of a "Swift core capabilities" list: 
> >>> 
> >>> account 
> >>> -- 
> >>> user-defined metadata 
> >>> ordered listings on containers, with marker limit, prefix, end_marker 
> >>> aggregate number of containers 
> >>> aggregate number of objects 
> >>> aggregate total bytes used 
> >>> independent read and write ACLs 
> >>> json, xml, and plain text listings 
> >>> system-level metadata 
> >>> create 
> >>> delete 
> >>> domain remap 
> >>> cname lookup 
> >>> 
> >>> container 
> >>> -- 
> >>> user-defined metadata 
> >>> ordered listings of objects, with marker, limit, delimiter, prefix, end_marker 
> >>> number of objects 
> >>> total bytes used 
> >>> independent read and write ACLs 
> >>> listing ACLs 
> >>> quota usage 
> >>> versioned writes of objects 
> >>> container sync 
> >>> json, xml, and plain text listings 
> >>> create 
> >>> delete 
> >>> CORS 
> >>> static website hosting 
> >>> domain remap 
> >>> cname lookup 
> >>> 
> >>> object 
> >>> -- 
> >>> user-defined metadata 
> >>> read 
> >>> write 
> >>> delete 
> >>> update metadata 
> >>> server-side copy 
> >>> dynamic large objects 
> >>> static large objects 
> >>> tempurl 
> >>> bulk upload (ie upload a tar, optionally compressed) 
> >>> bulk delete 
> >>> single range requests 
> >>> multi-range requests 
> >>> upload from html form 
> >>> time-expiring objects 
> >>> 
> >>> system 
> >>> -- 
> >>> crossdomain.xml support 
> >>> discoverable constraints 
> >>> list storage endpoints 
> >>> object name filters 
> >>> multiple auth system integration 
> >>> middleware extensibility 
> >>> healthcheck endpoint 
> >>> 
> >>> management 
> >>> -- 
> >>> drive failure transparent to the client 
> >>> server failure transparent to the client 
> >>> rack (zone) failure transparent to the client 
> >>> DC (region) failure transparent to the client 
> >>> swift recon 
> >>>   async pending 
> >>>   replication stats 
> >>>   auditor stats 
> >>>   updater stats 
> >>>   expirer stats 
> >>>   unmounted drive check 
> >>>   disk usage stats 
> >>>   load average stats 
> >>>   quarantined data stats 
> >>>   socket usage stats 
> >>> change capacity with no downtime 
> >>> upgrade with no downtime 
> >>> statd metric reporting (hundreds of metrics here) 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> _______________________________________________ 
> >>> Defcore-committee mailing list 
> >>> Defcore-committee at lists.openstack.org 
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee 
> >