<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04/19/2016 11:03 PM, Dean Troyer
wrote:<br>
</div>
<blockquote
cite="mid:CAOJFoEtWBLwdZSDT4Bzi-miOYwswvg-qSs7f2hud91hxPV+fUw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Apr 19, 2016 at 8:17 PM, Adam
Young <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Maybe it
is time to revamp Devstack. Is there some way that,
without a major rewrite, it could take better advantage of
the CLI? Could we group commands, or migrate sections to
python scripts that really all need to be done together?
For example, most of the early prep of the Keystone server
moved to keystone-manage bootstrap. Is there more
bootstrap-type behavior we can and should consolidate?</blockquote>
<div><br>
</div>
<div>This is what I was talking about, trying to take
advantage of the interactive mode that also reads from
stdin to do a series of comamnds with a single load/auth
cycle. It lacks a LOT of things for a resilient use case
such as DevStack (error abort or error ignore?, branching,
everything a DSL would bring).</div>
</div>
</div>
</div>
</blockquote>
Right, so lets get those as feature requests into the Client, I
think.<br>
<br>
The same DSL could be used server side for batch commands?<br>
<br>
<br>
<blockquote
cite="mid:CAOJFoEtWBLwdZSDT4Bzi-miOYwswvg-qSs7f2hud91hxPV+fUw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>And if you'd like to replace stach.sh with stack.py,
I'll not stop you, just don't call it DevStack. Now you
are building yet another deployment tool. We've also been
down that road before. It may well be time to retire
DevStack, be sure to let us know when those willing to
sponsor that work show up so they can attempt to learn
from some of our mistakes and not repeat them the hard
way.</div>
</div>
</div>
</div>
</blockquote>
Nope. Not gonna do it. I have no desire to do that. Nope nope
nopey nope nope.<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAOJFoEtWBLwdZSDT4Bzi-miOYwswvg-qSs7f2hud91hxPV+fUw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div><br>
</div>
<div>dt</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature"><br>
Dean Troyer<br>
<a moz-do-not-send="true" href="mailto:dtroyer@gmail.com"
target="_blank">dtroyer@gmail.com</a><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>