<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div><span>I have not been able to find a room for monday for the triple-O team. Maybe there could be some facilities sharing?</span></div><div></div><div> </div><div><div class="p1"><b><br></b></div><div class="p1" style="font-family: arial, helvetica, clean, sans-serif; font-weight: bold;"><b>Sean Roberts</b></div><div class="p1">Infrastructure Strategy, Yahoo</div><div class="p2"><span class="s1"><a rel="nofollow" target="_blank" href="mailto:seanrob@yahoo-inc.com">seanrob@yahoo-inc.com</a></span></div><div class="p1">(925) 980-4729</div></div><div class="yahoo_quoted" style="display: block;"> <br> <br> <div style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, 'Helvetica Neue',
Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> On Saturday, February 22, 2014 8:19 PM, Clint Byrum <clint@fewbar.com> wrote:<br> </font> </div> <div class="y_msg_container">Tim, were you aware this will be going on at the exact same time as the<br clear="none">TripleO summit, which is happening just down the road in Sunnyvale the<br clear="none">same week?<br clear="none"><br clear="none">I would like to see some mixing of these two groups. Perhaps we could have<br clear="none">some operators come over to the TripleO summit one day, or the other way<br clear="none">around, as I think feedback from the operators on what we have working<br clear="none">now and what we're proposing going forward would be extremely helpful.<br clear="none"><div class="yqt3842931776" id="yqtfd22912"><br clear="none">Excerpts from Tim Bell's message of 2014-02-21 09:37:22 -0800:<br clear="none">> We are
organising an OpenStack operators mini-summit in the Bay Area on Monday March 3rd in order to gather input for key needs from an OpenStack operator for development effort in the Juno release.<br clear="none">> <br clear="none">> There are a limited number of places available so early registration is recommended. A further session will be arranged around the Atlanta summit.<br clear="none">> <br clear="none">> The details are at <a shape="rect" href="https://www.eventbrite.co.uk/e/openstack-march-2014-operators-gathering-tickets-10318369521" target="_blank">https://www.eventbrite.co.uk/e/openstack-march-2014-operators-gathering-tickets-10318369521</a><br clear="none">> <br clear="none">> Note: There will be no 'presentations' on what OpenStack is, or how people are using it in their companies, outside of free-ranging discussion on these requirements. This is not an "operations best<br clear="none">> practice"
discussion - the aim is purely on getting feedback on what is/isn't working and what needs to change.<br clear="none">> <br clear="none">> For further background, a few questions & answers...<br clear="none">> <br clear="none">> What is an Operators' mini-Summit?<br clear="none">> <br clear="none">> This is an attempt to bring together OpenStack operators of various <br clear="none">> sizes and use cases and gather targeted feedback for the Technical <br clear="none">> committee, PTL's and dev teams. The goals of the meeting are to <br clear="none">> prioritize issues/requests from the representative group of <br clear="none">> operators, attempt to produce a blueprint or two from the top of that <br clear="none">> list and introduce it all back into the development cycle for Juno.<br clear="none">> <br clear="none">> How was this event organized?<br clear="none">> <br
clear="none">> The event was born out of discussion on the operators mailing list and has been <br clear="none">> organized over the last couple of months by the user committee, Tom Fifield <br clear="none">> (user community manager at the Foundation) and several volunteers from the OpenStack operator<br clear="none">> community . It's the first time we've done something like this, and is as much an experiment on the <br clear="none">> best way to build this process as it is an event <br clear="none">> for the gathering of feedback itself.<br clear="none">> <br clear="none">> How many people are you expecting to attend?<br clear="none">> <br clear="none">> We have capacity for 75 attendees, and we are limiting attendees to those operating OpenStack clouds <br clear="none">> (not building products for or around OpenStack). The event wil be hosted at eBay headquarters. <br clear="none">> Since it is the
first one, the organizing group deliberately wanted to keep things <br clear="none">> on the smaller side to make sure we enable productive discussions. We really want the gathering of feedback <br clear="none">> to be useful and actionable. Hopefully we can create a repeatable mechanism that gives more <br clear="none">> and more operators useful ways to influence OpenStack design and prioritization as it evolves.<br clear="none">> <br clear="none">> When will the next Operator's mini-Summit take place, and will it allow for more attendees?<br clear="none">> <br clear="none">> The next gathering is planned to take place during the OpenStack Summit in May 2014. The exact<br clear="none">> details and dates will be discussed during this event in March and shared shortly thereafter. <br clear="none">> It's important we make this first event a success - and something we can build on - in size, <br
clear="none">> frequency and regional diversity.<br clear="none">> <br clear="none">> Why is this called a summit?<br clear="none">> <br clear="none">> Because, like the Design summit, this meeting is focused on what is <br clear="none">> built in the next version of OpenStack. It just happens to be from an <br clear="none">> operator's perspective. It's more than a meet up and is not a <br clear="none">> conference or tech talk in anyway - there won't be howto's and <br clear="none">> presentations. It's a chance for the people that regularly deploy <br clear="none">> and run OpenStack to share what works, what doesn't, and how to make the product better for everyone.<br clear="none">> <br clear="none">> Why is this being held in March and not during the OpenStack Summit in May?<br clear="none">> <br clear="none">> The earlier we can provide input into the design process, the better, so
we can influence<br clear="none">> the sessions and conversations that will take place at the Atlanta Summit. We are planning<br clear="none">> to meet again at that time, but want to provide feedback prior to the technical community gathering<br clear="none">> in May. <br clear="none">> <br clear="none">> Where will you be sharing the outcomes, and how I can provide input if I'm not able to attend?<br clear="none">> <br clear="none">> First, make sure you have filled out the user survey, which is a great opportunity to share your <br clear="none">> feedback and completely confidential at your request. <a shape="rect" href="http://www.openstack.org/user-survey" target="_blank">http://www.openstack.org/user-survey</a><br clear="none">> We are referencing feedback from the survey in this session and again at the Atlanta Summit. <br clear="none">> <br clear="none">> We will be circulating more details of the way people can
provide input remotely before the event along with publishing the notes afterwards for further comment.<br clear="none">> <br clear="none">> Tim, Ryan, JC, Tom, Sean, Matt and Subbu<br clear="none"><br clear="none">_______________________________________________<br clear="none">OpenStack-operators mailing list<br clear="none"><a shape="rect" ymailto="mailto:OpenStack-operators@lists.openstack.org" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br clear="none"><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>