Open Stack

For capturing user stories and requirements -> blueprints, trello is an alternative to the storyboard project while it is being developed. Spec and blueprints are good, storyboards are better.

~sean

On May 19, 2014, at 7:15 PM, "Rob_Hirschfeld at dell.com<mailto:Rob_Hirschfeld at dell.com>" <Rob_Hirschfeld at dell.com<mailto:Rob_Hirschfeld at dell.com>> wrote:

We’re using blueprints and specs.
https://blueprints.launchpad.net/refstack
https://github.com/stackforge/refstack/tree/master/specs

> -----Original Message-----
> From: Sean Roberts [mailto:seanrob at yahoo-inc.com]
> Sent: Monday, May 19, 2014 9:10 PM
> To: Rochelle.RochelleGrober
> Cc: defcore-committee; David Lenwell; John Dickinson;
> fits at lists.openstack.org<mailto:fits at lists.openstack.org>
> Subject: Re: [OpenStack-DefCore] [Fits] swift capabilities
>
> Trello would be a good alternative.
>
> ~sean
>
> > On May 19, 2014, at 5:42 PM, "Rochelle.RochelleGrober"
> wrote:
> >
> > A number of the Refstack team members discussed the possibility of
> > becoming
> an alpha/beta user of Storyboard, but we have not started as yet.
> David Lenwell is investigating whether there is enough utility there to be of use to our effort.
> >
> > --Rocky
> >
> > -----Original Message-----
> > From: Joshua McKenty [mailto:joshua at pistoncloud.com]
> > Sent: Monday, May 19, 2014 4:35 PM
> > To: John Dickinson; David Lenwell; fits at lists.openstack.org<mailto:fits at lists.openstack.org>
> > Cc: defcore-committee; Troy Toman
> > Subject: Re: [Fits] [OpenStack-DefCore] swift capabilities
> >
> > 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 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
> 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 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<mailto:Defcore-committee at lists.openstack.org>
> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-commi
> >>>> tt
> >>>> ee
> >
> > _______________________________________________
> > FITs mailing list
> > FITs at lists.openstack.org<mailto:FITs at lists.openstack.org>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/fits
> >
> > _______________________________________________
> > Defcore-committee mailing list
> > Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committe
> > e
>
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140520/179ee78c/attachment-0001.html>