<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>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. </div>
<div><br>
~sean</div>
<div><br>
On May 19, 2014, at 7:15 PM, "<a href="mailto:Rob_Hirschfeld@dell.com">Rob_Hirschfeld@dell.com</a>" <<a href="mailto:Rob_Hirschfeld@dell.com">Rob_Hirschfeld@dell.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">We’re using blueprints and specs.<o:p></o:p></p>
<p class="MsoNormal"><a href="https://blueprints.launchpad.net/refstack">https://blueprints.launchpad.net/refstack</a>
<o:p></o:p></p>
<p class="MsoNormal"><a href="https://github.com/stackforge/refstack/tree/master/specs">https://github.com/stackforge/refstack/tree/master/specs</a>
<o:p></o:p></p>
<p>> -----Original Message-----<br>
> From: Sean Roberts [<a href="mailto:seanrob@yahoo-inc.com">mailto:seanrob@yahoo-inc.com</a>]<br>
> Sent: Monday, May 19, 2014 9:10 PM<br>
> To: Rochelle.RochelleGrober<br>
> Cc: defcore-committee; David Lenwell; John Dickinson; <br>
> <a href="mailto:fits@lists.openstack.org">fits@lists.openstack.org</a><br>
> Subject: Re: [OpenStack-DefCore] [Fits] swift capabilities<br>
> <br>
> Trello would be a good alternative.<br>
> <br>
> ~sean<br>
> <br>
> > On May 19, 2014, at 5:42 PM, "Rochelle.RochelleGrober"<br>
> wrote:<br>
> ><br>
> > A number of the Refstack team members discussed the possibility of <br>
> > becoming<br>
> an alpha/beta user of Storyboard, but we have not started as yet. <br>
> David Lenwell is investigating whether there is enough utility there to be of use to our effort.<br>
> ><br>
> > --Rocky<br>
> ><br>
> > -----Original Message-----<br>
> > From: Joshua McKenty [<a href="mailto:joshua@pistoncloud.com">mailto:joshua@pistoncloud.com</a>]<br>
> > Sent: Monday, May 19, 2014 4:35 PM<br>
> > To: John Dickinson; David Lenwell; <a href="mailto:fits@lists.openstack.org">
fits@lists.openstack.org</a><br>
> > Cc: defcore-committee; Troy Toman<br>
> > Subject: Re: [Fits] [OpenStack-DefCore] swift capabilities<br>
> ><br>
> > Adding David Lenwell to this. David's got the backlog somewhere.<br>
> ><br>
> > Sent from my iPhone<br>
> ><br>
> >> On May 19, 2014, at 2:52 PM, John Dickinson wrote:<br>
> >><br>
> >> That sounds like a good goal, and I think it's something we can <br>
> >> shoot for. Getting refstack to use the existing functional tests is <br>
> >> probably simpler that migrating to a new testing framework. (To be <br>
> >> clear, I'm not opposed to moving existing testing to tempest,<br>
> >> long-term.)<br>
> >><br>
> >> Where is refstack tracked? Is there a task tracker somewhere that I <br>
> >> can<br>
> follow?<br>
> >><br>
> >> --John<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >>> On May 19, 2014, at 2:39 PM, Joshua McKenty<br>
> wrote:<br>
> >>><br>
> >>> Love it!<br>
> >>><br>
> >>> We need a mapping from each capability, to the set of tests that<br>
> demonstrate it. As per our conversation, I assume this means either <br>
> migrating those tests from swift into tempest, or extending RefStack <br>
> to run them independently. Regardless, does that seem like something <br>
> that can be done in Juno timeframe?<br>
> >>><br>
> >>><br>
> >>><br>
> >>> Sent from my iPhone<br>
> >>><br>
> >>>> On May 19, 2014, at 2:32 PM, John Dickinson wrote:<br>
> >>>><br>
> >>>> Sitting on the plane to Atlanta last week, here's my first draft <br>
> >>>> of a "Swift<br>
> core capabilities" list:<br>
> >>>><br>
> >>>> account<br>
> >>>> --<br>
> >>>> user-defined metadata<br>
> >>>> ordered listings on containers, with marker limit, prefix, <br>
> >>>> end_marker aggregate number of containers aggregate number of <br>
> >>>> objects aggregate total bytes used independent read and write <br>
> >>>> ACLs json, xml, and plain text listings system-level metadata <br>
> >>>> create delete domain remap cname lookup<br>
> >>>><br>
> >>>> container<br>
> >>>> --<br>
> >>>> user-defined metadata<br>
> >>>> ordered listings of objects, with marker, limit, delimiter, <br>
> >>>> prefix, end_marker number of objects total bytes used independent <br>
> >>>> read and write ACLs listing ACLs quota usage versioned writes of <br>
> >>>> objects container sync json, xml, and plain text listings create <br>
> >>>> delete CORS static website hosting domain remap cname lookup<br>
> >>>><br>
> >>>> object<br>
> >>>> --<br>
> >>>> user-defined metadata<br>
> >>>> read<br>
> >>>> write<br>
> >>>> delete<br>
> >>>> update metadata<br>
> >>>> server-side copy<br>
> >>>> dynamic large objects<br>
> >>>> static large objects<br>
> >>>> tempurl<br>
> >>>> bulk upload (ie upload a tar, optionally compressed) bulk delete <br>
> >>>> single range requests multi-range requests upload from html form <br>
> >>>> time-expiring objects<br>
> >>>><br>
> >>>> system<br>
> >>>> --<br>
> >>>> crossdomain.xml support<br>
> >>>> discoverable constraints<br>
> >>>> list storage endpoints<br>
> >>>> object name filters<br>
> >>>> multiple auth system integration<br>
> >>>> middleware extensibility<br>
> >>>> healthcheck endpoint<br>
> >>>><br>
> >>>> management<br>
> >>>> --<br>
> >>>> drive failure transparent to the client server failure <br>
> >>>> transparent to the client rack (zone) failure transparent to the <br>
> >>>> client DC<br>
> >>>> (region) failure transparent to the client swift recon async <br>
> >>>> pending replication stats auditor stats updater stats expirer <br>
> >>>> stats unmounted drive check disk usage stats load average <br>
> >>>> stats quarantined data stats socket usage stats change capacity <br>
> >>>> with no downtime upgrade with no downtime statd metric reporting <br>
> >>>> (hundreds of metrics here)<br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> _______________________________________________<br>
> >>>> Defcore-committee mailing list<br>
> >>>> <a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
> >>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-commi">
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-commi</a><br>
> >>>> tt<br>
> >>>> ee<br>
> ><br>
> > _______________________________________________<br>
> > FITs mailing list<br>
> > <a href="mailto:FITs@lists.openstack.org">FITs@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/fits">http://lists.openstack.org/cgi-bin/mailman/listinfo/fits</a><br>
> ><br>
> > _______________________________________________<br>
> > Defcore-committee mailing list<br>
> > <a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committe">
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committe</a><br>
> > e<br>
> <br>
> _______________________________________________<br>
> Defcore-committee mailing list<br>
> <a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</body>
</html>