<div dir="ltr">Okay I'll bite. I'm a working owner; Cloud/OpenStack/SDN architect slash OpenStack SI business owner working with companies trying to extract value from technology they don't understand. Or in ways they aren't familiar with. Or with code they don't have time to build/maintain themselves.<div><br></div><div>This working group seems like we'll get to look at things from the perspective of "what is openstack and how can we make it better for those who want to use it" among other things. Sad reality is SI's and product vendors make more money if OpenStack remains complicated so we'll be working against working against a powerful money machine that funds this project. I want OpenStack to address real non-theoretical and non-marketing-BS cloud problems that are based in today's reality and in advance of tomorrow's challenges. I hope we'll get that chance.</div><div><br></div><div>Today, it seems to me that this WG would focus un-crunching code, design and evangelize opportunities for potential improvements for consideration by the greater OpenStack community and the TC. No successful architecture group I've ever participated wondered how do we can compel others to accept our recommendations. Leave that to the business/OpenStack governance.</div><div><br></div><div>Ultimately, I totally agree with Clint in that if we avoid too much focus on design enforcement, that's our first win. And in my mind, our designs will not be absorbed nor accepted de facto anyway. I think the value will however be recognized over time though and I'm totally down with that.</div><div><br></div><div>I'd like to participate with this Clint if there's room for one more. ; )</div><div><br></div><div>//adam</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font><div style="font-family:arial;font-size:small"><b><i><br>Adam Lawson</i></b></div><div><font><font color="#666666" size="1"><div style="font-family:arial"><br></div><div style="font-family:arial;font-size:small">AQORN, Inc.</div><div style="font-family:arial;font-size:small">427 North Tatnall Street</div><div style="font-family:arial;font-size:small">Ste. 58461</div><div style="font-family:arial;font-size:small">Wilmington, Delaware 19801-2230</div><div style="font-family:arial;font-size:small">Toll-free: (844) 4-AQORN-NOW ext. 101</div><div style="font-family:arial;font-size:small">International: +1 302-387-4660</div></font><font color="#666666" size="1"><div style="font-family:arial;font-size:small">Direct: +1 916-246-2072</div></font></font></div></font></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Jun 30, 2016 at 11:16 AM, Joshua Harlow <span dir="ltr"><<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Mike Perez wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11:31 Jun 20, Clint Byrum wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for getting this started Clint,<br>
<br>
I'm happy and excited to be involved in helping try to guide the whole<br>
ecosystem together (it's also why I like being in oslo) to a<br>
architecture that is more cohesive (and is more of something that we can<br>
say to our current or future children that we were all involved and<br>
proud to be involved in creating/maturing...).<br>
<br>
At a start, for said first meeting, any kind of agenda come to mind, or<br>
will it be more a informal gathering to start (either is fine with me)?<br>
<br>
</blockquote>
I've been hesitant to fill this in too much as I'm still forming the<br>
idea, but here are the items I think are most compelling to begin with:<br>
<br>
* DLM's across OpenStack -- This is already under way[1], but it seems to<br>
have fizzled out. IMO that is because there's no working group who<br>
owns it. We need to actually write some plans.<br>
</blockquote>
<br>
Not meaning to nitpick, but I don't think this is a compelling reason for the<br>
architecture working group. We need a group that wants to spend time on<br>
reviewing the drivers being proposed. This is like saying we need the<br>
architecture working group because no working group is actively reshaping quotas<br>
cross-project.<br>
<br>
With that said, I can see the architecture working group providing information<br>
on to a group actually reviewing/writing drivers for DLM and saying "Doing<br>
mutexes with the mysql driver is crazy, I brought it in a environment and have<br>
such information to support that it is not reliable". THAT is useful and I<br>
don't feel like people do enough of.<br>
<br>
My point is call your working group whatever you want (The Purple Parrots), and<br>
just go spearhead DLM, but don't make it about one of the most compelling<br>
reasons for the existence of this group.<br>
</blockquote>
<br></div></div>
Sadly I feel if such a group formed it wouldn't be addressing the larger issue that this type of group is trying to address; the purple parrots would be a tactical team that could go do what u said, but that doesn't address the larger strategic goal of trying to improve the full situation (technical and architectural inconsistencies and 'fizzling out' solutions) that IMHO needs to be worked through.<br>
<br>
So yes, the tactical group needs to exist, and overall it likely will, but there also needs to be a strategic group that is being proactive about the issues and not just tactically reacting to things (which isn't imho healthy).<br>
<br>
-Josh<div class="HOEnZb"><div class="h5"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>