<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body text="#000000" bgcolor="#FFFFFF">Posting this from Dave
Medberry (and with permission):<br>
<br>
<div>While
no longer technically an operator I'm 100% for colocating PTG and Ops
Meetups. I know some folks don't want to feel like tagalongs but I think
you are addressing that (and making a specific Ops invite and
considering a name change.)</div>
<div><br></div>
<div>So that's my $0.02
worth</div>
<div><br></div>
<div>Goals for Ops Meetups:</div>
<div>*
Community and F2F time with other Ops</div>
<div>* Shared Commiseration
and potentially action items if there is such shared commiseration</div>
<div>*
Wins (how you as an op are winning at operations). Ie., best practices,
tips & tricks, etc.</div>
<div>* Updates/ino about key projects.
We've had Nova cores/ptls, Swift cores/ptls, etc talk at various Ops
Meetups. I'd like to see this continue. Ie, what's in the just released
thing we need to worry about (or being released as we are there.) What
was in the last release that was a gotcha that as we move forward with
deployment we need to worry about (over and above what's on the
relnotes.)</div>
<div><br></div>
<div>I've sent this to you but feel free
to share broadly.</div>
<div><br></div>
<div>-dave</div>
<div><br></div>
<div>David
Medberry</div>
<div>OpenStack DevOps</div>
<div>& Cloud Manageability</div>
<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:5AB12AB1.2020906@openstack.org" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:jimmy@openstack.org"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Jimmy McArthur</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">March
20, 2018 at 10:37 AM</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi there!<br>
<br>
As discussions are underway for planning the Ops meetup during the
second half of the year, I wanted to reach out with some thoughts and to
see how the Foundation staff can help. We are committed to supporting
the Ops community and want you all to know that it continues to be a
major priority for the Foundation.<br>
<br>
<span style="font-weight: bold;">UC Update</span><br>
We've been meeting regularly with the User Committee to help establish
goals for the Committee as well as Operators and End Users. There are
three critical things that we identified as immediate areas of concern:<br>
<ul>
<li>How to involve operators, end users, and app-devs that are not in
the normal cycle of communications within the community (IRC, MLs,
Summit, Forum, etc..)</li><li>Ensuring a productive communication loop
between the User and Dev
communities so feedback from OS Days, local user groups, and Ops Meetups
are communicated and brought to the Forum in a way that allows
developers to address concerns in future release cycles.</li><li>Removing
perceived barriers and building relationships between User and Dev
communities</li>
</ul>
<br>
<span style="font-weight: bold;">General Feedback from Ops Meetups</span><br>
We're starting to lay the groundwork to address some of these concerns,
but we need feedback from the Ops community before moving forward. Some
of the feedback we've gotten from operators is they don't see their
needs being met during release cycles. We're hoping you can help us
answer a few questions and see if we can figure out a way to improve:<br>
<ul>
<li>What are the short and long term goals for Ops Meetups?</li><li>Do
you feel like the existing format is helping to achieve those goals?</li><li>How
can the OpenStack Foundation staff work to support your efforts?</li>
</ul>
<br>
<span style="font-weight: bold;">Ops 2H 2018 Meetup</span><br>
In addition to those questions, we'd like to pitch an option for you for
the next Ops Meetup. The upcoming PTG is the week of September 10 in
North America. We have an opportunity to co-locate the Ops Meetup at the
PTG. <br>
<br>
<span style="font-style: italic;">If the Ops community was interested
in
this, we would have separate space with your own work sessions and
separate
branding for the Ops attendees. This would also involve updating the
language on the OpenStack website and potentially renaming the PTG to
something more inclusive to both groups.</span> <br>
<br>
Evenings at a co-located event would allow for relationship building and
problem sharing. We're pitching this as a way to bring these two groups
together, while still allowing them to have distinct productive
events. That said, we're in no way trying to force the situation. If,
as a group, you decide you'd prefer to continue managing these events on
your own, we're happy to support that in whatever way we can.<br>
<br>
If you have an opinion one way or the other, please weigh in here:
<a moz-do-not-send="true"
href="https://www.surveymonkey.com/r/OpsMeetup2H2018"
class="moz-txt-link-freetext">https://www.surveymonkey.com/r/OpsMeetup2H2018</a><br>
<br style="font-weight: bold;">
<span style="font-weight: bold;">Events and Communication </span><br>
Regardless of the location of the event the second half of this year, we
would like to continue refining the feedback loop and determine how
ambassadors, user group leaders and OpenStack Days play into the mix. We
plan to have Forum sessions in Vancouver and Berlin and encourage all
Users to attend to discuss ways that we can provide more meaningful
discussion between Ops and Devs. Generally, we’ve been discussing a
communication architecture around events:<br>
<ul>
<li>OpenStack Days - Having an Ops track at OpenStack Days in an
effort to solicit feedback and open discussion from operators,
especially those who might normally not attend other events. The goal
here is to generate common operator issues and features, and also share
best practices. The Public Cloud WG has been successfully pioneering
this approach at several OpenStack Days last year.<br>
</li><li>Ops Meetup - Take the content generated by all of the OpenStack
Days Ops tracks and use them to narrow down how the Ops and Dev
communities can get the software to do what it should. The result is a
focused list of topics that we can use to create Forum sessions. There
are also opportunities to share and document knowledge, talk about
technology integration and best practices.</li><li>Forum - Using the
content generated through the prior two, we
propose sessions and discussions held at the Forum to funnel that
feedback directly to the dev community and collaborate with them.</li>
</ul>
<br>
This is again why I think there is some value in at least trying out the
PTG for a cycle or two, even if it's ultimately decided it isn't
fruitful. <br>
<br>
I realize this is a lot to absorb. Please review with relevant parties
and let us know your thoughts. The only catch on the PTG is we would
need a decision by April 4 in order to allocate the correct amount of
space.<br>
<br>
Thanks much for your time!<br>
Jimmy McArthur<br>
<br>
</div>
</blockquote>
<br>
</body></html>