[Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team
I am gathering potential Topics for ‘Forum’ sessions at the Berlin / Stein OpenStack Summit, from the StarlingX Team. If you are not familiar with ‘Forum’ sessions at the Summit, see end of email. I have done some initial brainstorming with the StarlingX Architecture Team to start things off. See the following etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please either email me directly or update the etherpad at bottom (with your name/email) with any ‘Forum’ –type topics that you would like to see considered for the Berlin / Stein OpenStack Summit. Greg. p.s. If you're not familiar with the Forum, the quick summary is a collaboration between various teams to help identify problems, ideas, and needs for future development. It's comprised of rooms set up in fishbowl/conversational style, unlike the formal presentations of the OpenStack Summit. It's been instrumental in helping OpenStack developers set the course for the coming development cycle, and we hope it's a format that will work well for StarlingX as well. Examples of typical sessions that make for a great Forum: · Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies o eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal · Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community o eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. · Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release o eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future.
Last call for any Forum Topics ... If you want to suggest any topics for consideration, you’ll need to update the etherpad by end-of-day today (Sept.24). https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming With the help of a few other StarlingX members, I’ll prioritize and submit abstracts for the top Forum topics that have been brainstormed by the StarlingX community ... required by Sept.26 . Thanks for your suggestions so far, Greg. From: Greg Waines <Greg.Waines@windriver.com> Date: Thursday, September 6, 2018 at 10:27 AM To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team I am gathering potential Topics for ‘Forum’ sessions at the Berlin / Stein OpenStack Summit, from the StarlingX Team. If you are not familiar with ‘Forum’ sessions at the Summit, see end of email. I have done some initial brainstorming with the StarlingX Architecture Team to start things off. See the following etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please either email me directly or update the etherpad at bottom (with your name/email) with any ‘Forum’ –type topics that you would like to see considered for the Berlin / Stein OpenStack Summit. Greg. p.s. If you're not familiar with the Forum, the quick summary is a collaboration between various teams to help identify problems, ideas, and needs for future development. It's comprised of rooms set up in fishbowl/conversational style, unlike the formal presentations of the OpenStack Summit. It's been instrumental in helping OpenStack developers set the course for the coming development cycle, and we hope it's a format that will work well for StarlingX as well. Examples of typical sessions that make for a great Forum: · Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies o eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal · Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community o eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. · Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release o eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future.
participants (1)
-
Waines, Greg