<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<span>Michael Krotscheck wrote:</span><br>
<blockquote
cite="mid:CABM65avCrCGLRKzLoQ=1JidnC6PqpDzz+NxJP_VF_VDHWk-Cog@mail.gmail.com"
type="cite">
<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Jun 22,
2016 at 11:50 AM Jimmy Mcarthur <<a moz-do-not-send="true"
href="mailto:jimmy@tipit.net">jimmy@tipit.net</a>> wrote:<br></div><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">An
example: you can't currently assign block storage to more than one VM
at a time. This is something that I think is just sitting around as a
patch to be approve in Neutron, but it's causing major problems for us
as web application developers that are deploying on top of OpenStack.
Basically, as a result of this and the lack of replication in Trove, we
can't cluster.<span style="line-height:1.5"> </span></div></blockquote><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
It's remarkably difficult to get integrated in IRC channels without
knowing the lingo. Is there some suggestion from the user committee
about where users like us could turn? </div></blockquote><div><br></div><div>To
address this specific issue: It sounds like you want to land a specific
feature in Neutron. The correct place to advocate for this is the
weekly neutron meeting. As someone who's recently landed a cross-project
feature (in 23 different projects), I can confidently say that every
team is open to - if occasionally grumpy about - unscheduled features
that aren't on their roadmap. It took me only a few questions, and quite
a bit of humility, to be given a primer on each teams' approval
governance, approval process, and roadmap feature selection.</div></div></div>
</blockquote>
Maybe I wasn't clear about my role in OpenStack :) I'm not an OpenStack
developer. I'm a web and mobile application developer (more
appropriately, a project manager) that hosts our sites on OpenStack
public cloud. I don't have a patch to land in Neutron. I understand that
it was already done and is waiting for approval by that team.<br>
<blockquote
cite="mid:CABM65avCrCGLRKzLoQ=1JidnC6PqpDzz+NxJP_VF_VDHWk-Cog@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote"><div><br></div><div>OpenStack's governance
empowers those who are willing to advocate for themselves, as long as
they are willing to back their requests with actual code.<span
style="line-height:1.5"> I'm sure that Neutron would be very happy to
address and shepherd any patches you'd be willing to provide.</span></div></div>
</div>
</blockquote>
Keep in mind that there is no place that I can currently advocate for my
team, which is why I'm raising the point :) I work for the Foundation
building web and mobile applications, but rely on OpenStack for
infrastructure. Specifically, we're running on the Rackspace cloud in
the same data center as Infra. The features I mention aren't within our
skill set to develop, but they're critical if OpenStack is to become a
viable option on which to host scalable web applications that need to
share data/resources. Though I'm sure many could do it very ably, I
don't expect OpenStack developers to come and write PHP or javascript in
order to use our website. We're valid users of the software you all are
doing such a great job of building. <br>
<blockquote
cite="mid:CABM65avCrCGLRKzLoQ=1JidnC6PqpDzz+NxJP_VF_VDHWk-Cog@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote"><div><span style="line-height:1.5"><br></span></div><div><span
style="line-height:1.5">In regards to understanding the IRC 'lingo', I
don't really know what that could refer to. Could you clarify?</span></div></div>
</div>
</blockquote>
Like any software product, there is common nomenclature that defines it.
Even reading the documentation can't possibly catch you up on the
history of the project and the people, especially since so much of it
takes place in IRC. If you're not out to become a full time OpenStack
developer and simply need something to work in a particular way, trying
to integrate with that project can be pretty tough. <br>
<br>
I certainly don't mean to start a great debate, but I would encourage
you to think of app developers that don't use OpenStack SDKs as well as
those that do. If we're not providing a place for those users to deliver
feedback and communicate, we could be missing out on lots of
opportunities to study <span style="font-style: italic;">how</span> they
are using the software. Companies (both large and small) don't always
have the resources to contribute back to OpenStack anymore than every
user of Ubuntu can contribute upstream. There is a whole world of
application developers out there that have no need/ability to be
involved at that level.<br>
<br>
Cheers!<br>
Jimmy<br>
<br>
<blockquote
cite="mid:CABM65avCrCGLRKzLoQ=1JidnC6PqpDzz+NxJP_VF_VDHWk-Cog@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote"><div><br></div><div><span
style="line-height:1.5">Michael Krotscheck</span> </div></div>
</div>
</blockquote>
<br>
</body></html>