[Openstack-track-chairs] what to do with operator talks?
Lauren Sell
lauren at openstack.org
Mon Feb 19 21:02:20 UTC 2018
Hi everyone,
Thanks for the feedback. I wanted to just weigh in on this, as well. We organized the tracks around use cases this go round, and that effort was intentional. Infrastructure operators and architects are the core audience at the Summit, so we expect these types of presentations will actually appear in every track rather than being siloed to one ops tracks.
To Allison’s question, if there are OpenStack-related operational talks relevant to edge implementations, I think they would still be a good fit for the edge track. If they are operational talks better suited to someone running a more standard datacenter private/public cloud, then they would fit better under those tracks respectively.
The OpenStack community is more than just OpenStack the software. As we acknowledge our larger role in open infrastructure, we really want the content at our summits to reflect that. The Private & Hybrid Cloud track will probably feature the most OpenStack content, but it’s by no means exclusive to OpenStack. Same with public cloud. At the same time, I expect there will be OpenStack content in the Telecom & NFV and Edge computing (and most every) track, but those tracks will also feature many other technologies and topics.
Because our tracks were historically OpenStack specific, it was more difficult for folks from other software projects to find a place where they fit in. The idea this round is to use a combination of broad use cases, more practical technology and/or operational tags and a broader set of open source project tags so that attendees can drill down to the content they like in several different ways. Tags are always more difficult to implement than you expect, so we probably all need to do some scrubbing and updating once the talks are selected.
All of that said, there is clearly some confusion amongst track chairs, which means there is likely confusion among potential speakers and attendees.. Please know we're reviewing all of the feedback and we'll make adjustments as necessary. Categorization is never perfect, but we will keep iterating until we find the best fit. The good news is the distribution across tracks has been more even this Summit than in the past, and we’ve attracted some non-OpenStack content to support our broader open infrastructure focus, so it feels like we’re moving in the right direction.
Let me know if I can provide any further info on this. Thank you all for your assistance this first round!
Lauren
> On Feb 19, 2018, at 8:06 AM, Allison Randal <allison at lohutok.net> wrote:
>
> Also:
>
> - As a vendor supporting multiple OpenStack releases is hard ... Or is it?
> - Accelerating Open Source Storage with RDMA
> - Secured Software Defined Networking for NFV Edge – a Machine learning
> approach
>
> On 02/19/2018 08:24 AM, Allison Randal wrote:
>> A few more examples, some of which have "Edge" in the title but are
>> really more general OpenStack deployment or operations talks:
>>
>> - Residual device scrubber for volume in Edge Computing
>> - Automated Operation and Maintenance in Edge Computing
>> - Toward an analysis of the OpenStack deployment process
>> - Bring your IOT device directly to your cloud network
>> - Intent Based Policy to Secure Applications Across OpenStack, K8s & BMS
>> Environment (Multi-Cloud)
>> - Three ARMed OpenStack - Building and Performance Testing OpenStack on ARM
>> - The Rise of the Distributed Database
>> - Distributed Tracing for continuous improvement of OpenStack-based
>> Cloud Services
>> - OpenStack OSProfiler Overview: What is it? How does it work?
>> - Deploying OpenStack Swift using TripleO
>>
>> And maybe also:
>>
>> - Deploying to the Edge
>> - Deploy Your React Application While Saving Time and Energy
>>
>> On 02/18/2018 11:49 PM, Gary Kevorkian (gkevorki) wrote:
>>> Here’s one we weren’t sure what to do with…
>>>
>>>
>>>
>>> /Integrating Skydive & Dragonflow and Staying Alive/
>>>
>>>
>>> In the end, we kept it in Community because it does talk about how the
>>> community helped the process, but I think it might have better suited in
>>> a technical category.
>>>
>>>
>>>
>>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/09_standard_graphic.png
>>>
>>>
>>>
>>>
>>> Gary Kevorkian
>>>
>>> EVENT MARKETING MANAGER
>>>
>>> gkevorki at cisco.com <mailto:gkevorki at cisco.com>
>>>
>>> Tel: +3237912058
>>>
>>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/twitter-16x16.png
>>> <http://wwwin.cisco.com/c/cec/organizations/gmcc/services-tools/twitter.com/GARY805>
>>>
>>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/webex.png
>>> <http://cisco.webex.com/meet/gkevorki> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/sparks.png
>>> <https://ciscospark.com/gkevorki> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/jabber.png
>>> <http://reachme.cisco.com/call/gkevorki>
>>>
>>>
>>>
>>> Cisco Systems, Inc.
>>>
>>> United States
>>>
>>> Cisco.com <http://www.cisco.com/>
>>>
>>> ttp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif
>>>
>>>
>>>
>>> Think before you print.
>>>
>>> This email may contain confidential and privileged material for the sole
>>> use of the intended recipient. Any review, use, distribution or
>>> disclosure by others is strictly prohibited. If you are not the intended
>>> recipient (or authorized to receive for the recipient), please contact
>>> the sender by reply email and delete all copies of this message.
>>>
>>> Please click here
>>> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for
>>> Company Registration Information.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From: *Jimmy McArthur <jimmy at openstack.org>
>>> *Date: *Sunday, February 18, 2018 at 8:03 PM
>>> *To: *"Gary Kevorkian (gkevorki)" <gkevorki at cisco.com>
>>> *Cc: *Allison Randal <allison at lohutok.net>,
>>> "openstack-track-chairs at lists.openstack.org"
>>> <openstack-track-chairs at lists.openstack.org>
>>> *Subject: *Re: [Openstack-track-chairs] what to do with operator talks?
>>>
>>>
>>>
>>> This is great feedback. I'm going to discuss this with our team and see
>>> what we can come up with. Can y'all provide a few examples?
>>>
>>> Thanks!
>>> Jimmy
>>>
>>>
>>>
>>> Gary Kevorkian (gkevorki) <mailto:gkevorki at cisco.com>
>>>
>>> February 18, 2018 at 2:18 PM
>>>
>>> Operator-centric talks aren’t the only ones. At future Summits, we
>>> may need to embrace the “Grab Bag” track that I’ve seen at other
>>> events. ☺
>>>
>>>
>>> Gary Kevorkian
>>> EVENT MARKETING MANAGER
>>> gkevorki at cisco.com <mailto:gkevorki at cisco.com>
>>> Tel: +3237912058
>>> <http://wwwin.cisco.com/c/cec/organizations/gmcc/services-tools/twitter.com/GARY805>
>>> <http://wwwin.cisco.com/c/cec/organizations/gmcc/services-tools/twitter.com/GARY805>
>>> <http://cisco.webex.com/meet/gkevorki>
>>> <http://cisco.webex.com/meet/gkevorki>
>>> <https://ciscospark.com/gkevorki> <https://ciscospark.com/gkevorki>
>>> <http://reachme.cisco.com/call/gkevorki>
>>> <http://reachme.cisco.com/call/gkevorki>
>>> Cisco Systems, Inc.
>>> United States
>>> Cisco.com <http://www.cisco.com/> <http://www.cisco.com/>
>>>
>>> Think before you print.
>>> This email may contain confidential and privileged material for the
>>> sole use of the intended recipient. Any review, use, distribution or
>>> disclosure by others is strictly prohibited. If you are not the
>>> intended recipient (or authorized to receive for the recipient),
>>> please contact the sender by reply email and delete all copies of
>>> this message.
>>> Please click here
>>> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html>
>>> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html>
>>> for Company Registration Information.
>>>
>>>
>>> On 2/18/18, 12:10 PM, "Allison Randal" <allison at lohutok.net>
>>> <mailto:allison at lohutok.net> wrote:
>>>
>>> At previous Summits, did we have an Operators track? There seem to be a
>>> large number of talks scattered across the tracks that are basically
>>> just tips, tricks, and best practices for operating an OpenStack cloud.
>>> The track chairs for all the tracks keep trying to kick these talks to
>>> other tracks, but they don't seem to really fit anywhere, so the move
>>> requests get repeatedly rejected.
>>>
>>> I don't really have a solution, I'm just making an observation that we
>>> may not be serving our operator audience well if these talks all get
>>> dropped just because they don't seem to match any current tracks.
>>>
>>> Allison
>>>
>>> _______________________________________________
>>> Openstack-track-chairs mailing list
>>> Openstack-track-chairs at lists.openstack.org
>>> <mailto:Openstack-track-chairs at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>>>
>>>
>>> _______________________________________________
>>> Openstack-track-chairs mailing list
>>> Openstack-track-chairs at lists.openstack.org
>>> <mailto:Openstack-track-chairs at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>>>
>>> Allison Randal <mailto:allison at lohutok.net>
>>>
>>> February 18, 2018 at 2:10 PM
>>>
>>> At previous Summits, did we have an Operators track? There seem to be a
>>> large number of talks scattered across the tracks that are basically
>>> just tips, tricks, and best practices for operating an OpenStack cloud.
>>> The track chairs for all the tracks keep trying to kick these talks to
>>> other tracks, but they don't seem to really fit anywhere, so the move
>>> requests get repeatedly rejected.
>>>
>>> I don't really have a solution, I'm just making an observation that we
>>> may not be serving our operator audience well if these talks all get
>>> dropped just because they don't seem to match any current tracks.
>>>
>>> Allison
>>>
>>> _______________________________________________
>>> Openstack-track-chairs mailing list
>>> Openstack-track-chairs at lists.openstack.org
>>> <mailto:Openstack-track-chairs at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>>>
>>>
>>>
>
> _______________________________________________
> Openstack-track-chairs mailing list
> Openstack-track-chairs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
More information about the Openstack-track-chairs
mailing list
