https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Emccormickva&feedformat=atomOpenStack - User contributions [en]2024-03-28T09:20:57ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Forum/Denver2019&diff=169780Forum/Denver20192019-05-01T15:55:17Z<p>Emccormickva: /* Wednesday May 1 */</p>
<hr />
<div>== Etherpads ==<br />
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!<br />
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.<br />
<br />
=== Monday April 29 ===<br />
* [11:10-11:50] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-app-creds Keystone Application Credentials: Status and Planning]<br />
* [11:10-11:50] [https://etherpad.openstack.org/p/DEN-train-next-steps-for-standalone-ironic Next steps for standalone ironic]<br />
* [12:00-12:40] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-operator-feedback Keystone Operator Feedback]<br />
* [12:00-12:40] [https://etherpad.openstack.org/p/DEN-bare-metal-SIG Bare Metal SIG]<br />
* [14:00-14:40] [https://etherpad.openstack.org/p/keystone-for-multi-tenancy-in-kubernetes Leveraging OpenStack Keystone for Multi-Tenancy Support in Kubernetes]<br />
* [14:50-15-30] [https://etherpad.openstack.org/p/service-consumption Consumption models for service projects]<br />
* [14:50-15-30] [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto-scaling SIG]<br />
* [15:50-16:30] [https://etherpad.openstack.org/p/storyboard-pain-points Ibuprofen for Your StoryBoard Pain Points]<br />
* [15:50-16:30] [https://etherpad.openstack.org/p/DEN-change-ownership-of-resources OpenStack: Change ownership of resources - followup]<br />
* [14:40-15:20] [https://etherpad.openstack.org/p/DEN-Ops-Catch-Up Ops Community Gathering and Meetup Planning]<br />
* [16:40-17:20] [https://etherpad.openstack.org/p/forum-technical-vision-doc Technical vision document: Check in and question session]<br />
<br />
=== Tuesday April 30 ===<br />
<br />
* [9:00-9:40] [https://etherpad.openstack.org/p/DEN-vitrage-use-cases-forum Use cases for the new vitrage RCA UI]<br />
* [9:50-10:30] [https://etherpad.openstack.org/p/DEN-deployment-tools-capabilities Deployment tools: define common capabilities]<br />
* [9:50-10:30] [https://etherpad.openstack.org/p/DEN-linux-distro-best-practices Cross-project best practices for integration with Linux distributions]<br />
* [10:50-11:30] [https://etherpad.openstack.org/p/DEN-ECG-MVP-feedback Edge Computing Group MVP Architecture feedback]<br />
* [10:50-11:30] [https://etherpad.openstack.org/p/Den-forum-nova-cyborg-integration Nova-Cyborg Integration Updates and Next Steps]<br />
* [10:50-11:30] [https://etherpad.openstack.org/p/DEN-public-cloud-wg Public Cloud WG]<br />
* [11:40-12:20] [https://etherpad.openstack.org/p/DEN-ECG-use-cases-discssion-feedback Edge Computing use cases discussion and feedback]<br />
* [11:40-12:20] [https://etherpad.openstack.org/p/playing-nice-openstackResMgmt-kubernetesResMgmt Playing Nice Together - OpenStack Resource Management and Kubernetes Resource Management]<br />
* [11:40-12:20] [https://etherpad.openstack.org/p/DEN-train-api-sig API-SIG BoF]<br />
* [13:40-14:20] [https://etherpad.openstack.org/p/DEN-update-on-placement-extraction-from-nova Update on placement extraction from nova]<br />
* [13:40-14:20] [https://etherpad.openstack.org/p/DEN-baremetal-cluster-api baremetal cluster-api with ironic]<br />
* [14:30-15:10] [https://etherpad.openstack.org/p/DEN-ECG-roadmap-and-feedback What is the Edge Computing Group and what it should be doing in the next 6 months?]<br />
* [14:30-15:10] [https://etherpad.openstack.org/p/DEN-ptl-tips-and-tricks PTL Tips and Tricks]<br />
* [15:20-16:00] [https://etherpad.openstack.org/p/DEN-help-most-needed-for-sigs-and-wgs Help most needed for SIGs and WGs]<br />
* [16:20-17:00] [https://etherpad.openstack.org/p/new-contribs-state-and-deduplication Welcoming New Contributors State of the Union and Deduplication of Efforts] <br />
* [16:20-17:00] [https://etherpad.openstack.org/p/DEN-openstack-and-ceph Openstack and Ceph: Better Together!]<br />
* [17:10-17:50] [https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Ops War Stories/Architecture Show and Tell Lightning Talks]<br />
* [17:10-17:50] [https://etherpad.openstack.org/p/Den-forum-help-most-needed Planning & Defining Structure for ‘Help most needed’ list]<br />
<br />
=== Wednesday May 1 ===<br />
* [09:00-09:40] [https://etherpad.openstack.org/p/DEN-qa-onboarding QA Onboarding]<br />
* [09:00-09:40] [https://etherpad.openstack.org/p/DEN-openlab-whats-next OpenLab: We Integrated K8s, What is Next?]<br />
* [09:50-10:30] [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self-healing BoF: Solutions and Use Cases]<br />
* [09:50-10:30] [https://etherpad.openstack.org/p/Foundations-for-Image-Encryption Foundations for Image Encryption in OpenStack]<br />
* [10:50-11:30] [https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback Users/Operators adoption of QA tools/plugins]<br />
* [11:40-12:20] [https://etherpad.openstack.org/p/charting-the-course-for-openstack-helm Charting the course for OpenStack Helm]<br />
* [13:40-12:40] [https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Closing compute API feature gaps in the openstack CLI]<br />
* [13:40-14:20] [https://etherpad.openstack.org/p/denver-forum-cinder-improving-drvr-cap-rep Improving Cinder Driver Capability Reporting]<br />
* [14:30-15:10] [https://etherpad.openstack.org/p/denver-forum-cinder-direct-user-feedback Cinder Opportunity for Direct User Feedback]<br />
* [15:20-16:00] [https://etherpad.openstack.org/p/DEN-tripleo-forum-scale TripleO architecture for thousand node scale ]<br />
* [15:20-16:00] [https://etherpad.openstack.org/p/DEN-Deletion-of-resources OpenStack: Project Resource Cleanup - followup]<br />
* [16:20-17:00] [https://etherpad.openstack.org/p/DEN-drive-common-goals OpenStack: how to drive common goals]<br />
* [16:20-17:00] [https://etherpad.openstack.org/p/DEN-granular-policy-and-default-roles Increasing API accessibility with granular policy and default roles]<br />
* [17:10-17:50] [https://etherpad.openstack.org/p/DEN-Operator-end-user-Public-cloud-feedback OpenStack: Operator, end user and Public cloud feedback]<br />
* [17:10-17:50] [https://etherpad.openstack.org/p/DEN-unified-limits Unified limits update and migration]<br />
<br />
==List of Brainstorming Etherpads==<br />
<br />
===Catch-alls===<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]<br />
<br />
===Etherpads from Teams and Working Groups===<br />
* [https://etherpad.openstack.org/p/DEN-train-api-sig API-SIG]<br />
* [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto scaling SIG]<br />
* [https://etherpad.openstack.org/p/DEN-Train-EWG-brainstorming Enterprise Working Group (EWG)]<br />
* [https://etherpad.openstack.org/p/Denver-2019-Forum-DCN-Brainstorming DCN]<br />
* [https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]<br />
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]<br />
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming Manila]<br />
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/oslo-train-topics Oslo]<br />
* [https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self healing SIG]<br />
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]<br />
* [https://etherpad.openstack.org/p/tripleo-train-topics TripleO]<br />
<br />
===Etherpads from Pilot projects===<br />
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Denver2019&diff=169767Forum/Denver20192019-04-30T19:48:56Z<p>Emccormickva: /* Tuesday April 30 */</p>
<hr />
<div>== Etherpads ==<br />
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!<br />
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.<br />
<br />
=== Monday April 29 ===<br />
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-app-creds Keystone Application Credentials: Status and Planning]<br />
<br />
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-train-next-steps-for-standalone-ironic Next steps for standalone ironic]<br />
<br />
[12:00-12:40] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-operator-feedback Keystone Operator Feedback]<br />
<br />
[12:00-12:40] [https://etherpad.openstack.org/p/DEN-bare-metal-SIG Bare Metal SIG]<br />
<br />
[14:00-14:40] [https://etherpad.openstack.org/p/keystone-for-multi-tenancy-in-kubernetes Leveraging OpenStack Keystone for Multi-Tenancy Support in Kubernetes]<br />
<br />
[14:50-15-30] [https://etherpad.openstack.org/p/service-consumption Consumption models for service projects]<br />
<br />
[14:50-15-30] [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto-scaling SIG]<br />
<br />
[15:50-16:30] [https://etherpad.openstack.org/p/storyboard-pain-points Ibuprofen for Your StoryBoard Pain Points]<br />
<br />
[15:50-16:30] [https://etherpad.openstack.org/p/DEN-change-ownership-of-resources OpenStack: Change ownership of resources - followup]<br />
<br />
[14:40-15:20] [https://etherpad.openstack.org/p/DEN-Ops-Catch-Up Ops Community Gathering and Meetup Planning]<br />
<br />
[16:40-17:20] [https://etherpad.openstack.org/p/forum-technical-vision-doc Technical vision document: Check in and question session]<br />
<br />
=== Tuesday April 30 ===<br />
[9:00-9:40] [https://etherpad.openstack.org/p/DEN-vitrage-use-cases-forum Use cases for the new vitrage RCA UI]<br />
<br />
[9:50-10:30] [https://etherpad.openstack.org/p/DEN-deployment-tools-capabilities Deployment tools: define common capabilities]<br />
<br />
[9:50-10:30] [https://etherpad.openstack.org/p/DEN-linux-distro-best-practices Cross-project best practices for integration with Linux distributions]<br />
<br />
[10:50-11:30] [https://etherpad.openstack.org/p/DEN-ECG-MVP-feedback Edge Computing Group MVP Architecture feedback]<br />
<br />
[10:50-11:30] [https://etherpad.openstack.org/p/Den-forum-nova-cyborg-integration Nova-Cyborg Integration Updates and Next Steps]<br />
<br />
[11:40-12:20] [https://etherpad.openstack.org/p/DEN-ECG-use-cases-discssion-feedback Edge Computing use cases discussion and feedback]<br />
<br />
[11:40-12:20] [https://etherpad.openstack.org/p/playing-nice-openstackResMgmt-kubernetesResMgmt Playing Nice Together - OpenStack Resource Management and Kubernetes Resource Management]<br />
<br />
[11:40-12:20] [https://etherpad.openstack.org/p/DEN-train-api-sig API-SIG BoF]<br />
<br />
[13:40-14:20] [https://etherpad.openstack.org/p/DEN-update-on-placement-extraction-from-nova Update on placement extraction from nova]<br />
<br />
[13:40-14:20] [https://etherpad.openstack.org/p/DEN-baremetal-cluster-api baremetal cluster-api with ironic]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/DEN-ECG-roadmap-and-feedback What is the Edge Computing Group and what it should be doing in the next 6 months?]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/DEN-ptl-tips-and-tricks PTL Tips and Tricks]<br />
<br />
[16:20-17:00] [https://etherpad.openstack.org/p/new-contribs-state-and-deduplication Welcoming New Contributors State of the Union and Deduplication of Efforts] <br />
<br />
[16:20-17:00] [https://etherpad.openstack.org/p/DEN-openstack-and-ceph Openstack and Ceph: Better Together!]<br />
<br />
[17:10-17:50] [https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Ops War Stories/Architecture Show and Tell Lightning Talks]<br />
<br />
=== Wednesday May 1 ===<br />
[09:00-09:40] [https://etherpad.openstack.org/p/DEN-qa-onboarding QA Onboarding]<br />
<br />
[09:00-09:40] [https://etherpad.openstack.org/p/DEN-openlab-whats-next OpenLab: We Integrated K8s, What is Next?]<br />
<br />
[10:50-11:30] [https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback Users/Operators adoption of QA tools/plugins]<br />
<br />
[1340-1240] [https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Closing compute API feature gaps in the openstack CLI]<br />
<br />
[13:40-14:20] [https://etherpad.openstack.org/p/denver-forum-cinder-improving-drvr-cap-rep Improving Cinder Driver Capability Reporting]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/denver-forum-cinder-direct-user-feedback Cinder Opportunity for Direct User Feedback]<br />
<br />
[2:50-3:30] [https://etherpad.openstack.org/p/consumption-models Consumption Models for Service Projects]<br />
<br />
[3:20-4:00] [https://etherpad.openstack.org/p/DEN-tripleo-forum-scale TripleO architecture for thousand node scale ]<br />
<br />
[15:20-16:00] [https://etherpad.openstack.org/p/DEN-Deletion-of-resources OpenStack: Project Resource Cleanup - followup]<br />
<br />
[4:20-5:00] [https://etherpad.openstack.org/p/DEN-drive-common-goals OpenStack: how to drive common goals]<br />
<br />
[4:20-5:00] [https://etherpad.openstack.org/p/DEN-granular-policy-and-default-roles Increasing API accessibility with granular policy and default roles]<br />
<br />
[17:10-17:50] [https://etherpad.openstack.org/p/DEN-Operator-end-user-Public-cloud-feedback OpenStack: Operator, end user and Public cloud feedback]<br />
<br />
[17:10-17:50] [https://etherpad.openstack.org/p/DEN-unified-limits Unified limits update and migration]<br />
<br />
==List of Brainstorming Etherpads==<br />
<br />
===Catch-alls===<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]<br />
<br />
===Etherpads from Teams and Working Groups===<br />
* [https://etherpad.openstack.org/p/DEN-train-api-sig API-SIG]<br />
* [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto scaling SIG]<br />
* [https://etherpad.openstack.org/p/DEN-Train-EWG-brainstorming Enterprise Working Group (EWG)]<br />
* [https://etherpad.openstack.org/p/Denver-2019-Forum-DCN-Brainstorming DCN]<br />
* [https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]<br />
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]<br />
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming Manila]<br />
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/oslo-train-topics Oslo]<br />
* [https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self healing SIG]<br />
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]<br />
* [https://etherpad.openstack.org/p/tripleo-train-topics TripleO]<br />
<br />
===Etherpads from Pilot projects===<br />
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Operations/Meetups&diff=169745Operations/Meetups2019-04-29T22:15:27Z<p>Emccormickva: /* Venue Selection */</p>
<hr />
<div><div style="float:right">__TOC__</div><br />
<br />
Ops Meetups give people who run clouds a place to congregate, swap best practices, ideas and give feedback. It has a mostly round table/working/discussion session feel, with only a small number of presentations, with the following aims:<br />
# Gather feedback on the issues that come up in running OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running clouds<br />
<br />
Ops Meetups are typically held as part of the 6-monthly design summit, and also once "mid-cycle". Previous and upcoming Ops Meetups are listed below:<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
==== Mid-cycle (North America, 2019) ====<br />
* Targetting North America region following Tokyo and then Berlin<br />
* [https://etherpad.openstack.org/p/ops-meetup-2nd-2019] Bloomberg hosted proposal, NYC, Sept 3,4<br />
==== Mid-cycle (Berlin, 2019) ====<br />
* EU region, with a research and academia focus<br />
* [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin Proposal is for Berlin, March 6-7 or 7-8.]<br />
* [https://etherpad.openstack.org/p/BER-ops-meetup Planning etherpad]<br />
<br />
==== Mid Cycle (Denver, September 2018) ====<br />
* The OpsMeetup co-located with the Stein PTG (Denver, September 10-14 2018)<br />
* [https://www.openstack.org/ptg/ Denver PTG]<br />
* [https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018 Etherpad for Denver OpsMeetup]<br />
<br />
==== Rocky release (Vancouver, May 21-24 2018) ====<br />
* [https://wiki.openstack.org/wiki/Forum/Vancouver2018 Forum wiki page]<br />
<br />
==== Mid Cycle (Tokyo, March 2018) ====<br />
* [https://wiki.openstack.org/wiki/Operations/Meetups/TYO-ops-meetup Wiki page for Tokyo]<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup-2018 Tokyo meetup agenda planning]<br />
<br />
* venue discussion<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2018 Proposal etherpad for 1st meet up 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-spring-2018 Feb/Mar 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-aug-2018 Aug 2018]<br />
<br />
==== Queens release (Sydney, November 6-8 2017) ====<br />
*[https://wiki.openstack.org/wiki/Forum/Sydney2017 Forum landing wiki page]<br />
* [https://etherpad.openstack.org/p/SYD-ops-session-ideas Forum planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2017) ====<br />
* August 9 & 10 in Mexico City, Mexico<br />
* [https://etherpad.openstack.org/p/MEX-ops-meetup planning etherpad]<br />
<br />
==== Pike release (Boston, May 8-11, 2017) ====<br />
<br />
*[https://etherpad.openstack.org/p/BOS-forum-ops-catch-up ops meet up etherpad]<br />
*[https://wiki.openstack.org/wiki/Forum/Boston2017 all Forum etherpads]<br />
<br />
==== Mid-Cycle (Mar, 2017) ====<br />
* March 15 & 16 in Milan, Italy<br />
* [https://etherpad.openstack.org/p/MIL-ops-meetup planning etherpad]<br />
<br />
====Ocata release (Barcelona, October 2016)====<br />
* [https://etherpad.openstack.org/p/BCN-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Aug 25-26, 2016)====<br />
* August 25 & 26, New York City, USA<br />
* [https://etherpad.openstack.org/p/NYC-ops-meetup planning etherpad]<br />
<br />
====Newton release (Austin, May 2016)====<br />
* [https://etherpad.openstack.org/p/AUS-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Feb, 2016)====<br />
* February 15 & 16, Manchester, UK<br />
* [https://etherpad.openstack.org/p/european-ops-meetup-planning original planning etherpad]<br />
* [https://etherpad.openstack.org/p/MAN-ops-meetup second planning etherpad]<br />
* [https://europeanopenstackoperatorsmeetup.eventbrite.com/ tickets on eventbrite]<br />
<br />
====Mitaka release (Tokyo, October 2015)====<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2015)====<br />
* August 18 & 19, Palo Alto<br />
* [http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924 Registration]<br />
* [https://etherpad.openstack.org/p/PAO-ops-meetup planning etherpad]<br />
<br />
===="L" release (Vancouver, May 2015)====<br />
* [https://etherpad.openstack.org/p/YVR-ops-meetup planning etherpad]<br />
* [[Design_Summit/Liberty/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-Cycle (Mar, 2015)====<br />
* March 9th and 10th, Philadelphia, USA<br />
* [https://etherpad.openstack.org/p/PHL-ops-meetup etherpads]<br />
<br />
==== Kilo (Paris, November 2014) ====<br />
<br />
* [http://kilodesignsummit.sched.org/overview/type/ops+summit schedule]<br />
* [[Summit/Kilo/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-cycle (San Antonio, August 2014) ====<br />
<br />
* [http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/ schedule]<br />
* [https://etherpad.openstack.org/p/SAT-ops-meetup Etherpads]<br />
<br />
==== Juno (Atlanta, May 2014) ====<br />
<br />
* [http://junodesignsummit.sched.org/overview/type/ops+meetup schedule]<br />
* [[Summit/Juno/Etherpads#Ops|Etherpads]]<br />
<br />
<br />
==== Mid-Cycle (San Jose, March 2014) ====<br />
* [https://etherpad.openstack.org/p/operators-feedback-mar14 Etherpad]<br />
</div><br />
==Moderators Guide==<br />
Thank you very much for stepping up to be moderators at the ops meetup. Your work is key to our success!<br />
<br />
You are in control of your sessions, however, this document lay down some ideas about what we've seen in the past makes a good session, in case it helps.<br />
<br />
We have two different types of sessions. General Sessions and Working Groups. Below, I've separated them out so you can read what's relevant to you.<br />
<br />
We have three overall aims:<br />
# Gather feedback on the issues that come up in running or using OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running or using clouds<br />
<br />
<br />
===General Sessions===<br />
<br />
Basically, it's you, an etherpad, and room full of a couple hundred people who have OpenStack experience. As the moderator, your efforts result in actionable things we can work on, and the satisfied audience.<br />
<br />
* Introduce yourself to the audio guy or gal. You'll be provided with a microphone and asked about laptop connection.<br />
* The best thing to do is convince one of your friends to control the laptop. Get them to control the display of the etherpad, and if it gets big, scroll up and down to ensure the most relevant parts are seen.<br />
* At the start of the session give a 30 second intro to the etherpad, and ask everyone to take notes using it. (Many attendees will not be used to etherpads)<br />
* Kick off the discussion on time, perhaps by starting with some open ended questions, or a show of hands to understand the audience<br />
* Aim to get it to that nirvana state, where the conversation continues without your help<br />
* Don't fall into "Question and Answer" mode - just because you're up the front of the room, some people might expect you to do this. Steer back toward discussion always.<br />
* There will be microphone hogs. Do not be afraid to cut them off. Using language like "Thank you, that is important, we have recorded that on the etherpad" will mean there'll be no hard feelings.<br />
* If you see a nice transition between different topics, take it!<br />
* Most importantly: try and aim for every discussion to have at least one action item - something we can work on. If we don't do this, people are going to stop coming to these things <br />
<br />
<br />
Overall, have fun! Also *be* fun! If you get bored, the audience will sense it - so if it happens start a new topic. Spontaneity is good! Asking people to do things (file a bug, start a mailing list post) is good!<br />
<br />
<br />
===Working Groups - "Small, working sessions"===<br />
These sessions are for a focus on specific topics, and they are long sessions (normally 80 minutes) so you can actually, legitimately get work done - not just talk.<br />
<br />
You'll have yourself, and a small group of people who are experienced with OpenStack and actually very interested in getting involved. It's your job as facilitator to try and convert each and every one of these people into a proactive member of your working group, ideally continuing their tenure well after the summit.<br />
<br />
Since these are mostly longer session, and about much more specific things, it requires a bit more planning. For some of the groups, you will have met before and have work and processes to continue. Try and seed your etherpads with this information prior to the session.<br />
<br />
Try and think of some concrete things that can be done during your time, but also be ready and open to the suggestions of the attendees. If there's a great idea that everyone believes in, go for it and get it done. File bugs. File blueprints. Submit patches. Write documents. Use the whiteboard. You have time for all of this <br />
<br />
<br />
Of course, all of this information is general. You are the rockstars here - do whatever you think is best . Tom will be on hand for much of the two days for assistance. (call +886 98833 1200 if anything goes horribly wrong)<br />
<br />
There are also a few sessions which are a bit different...<br />
<br />
===Architecture Show and Tell===<br />
This is a series of lightening talks - basically a 5-8 minute talk about something cool about your deployment.<br />
<br />
If you're moderating this, one of the main duties you have to perform (or delegate) is that of timekeeping - we normally cycle through many talks in each session.<br />
<br />
Best practice is to get any slides people are using into one laptop before the start of the session.<br />
<br />
===Pre-and Post Meetup===<br />
Fully realising you are a volunteer with limited time and that you might not get around to any of this, some of the things that are cool to do before or after the meetup are:<br />
* Post a thread on the ops ML asking for ideas for your session (and also advertising it)<br />
* Giving a tweet out with the schedule details<br />
* Filling in the etherpad with some conversation start topics (or, if you are a developer looking for feedback - questions you would like answered)<br />
* Posting on the Ops ML a summary of the session and linking to the etherpad for those who couldn't make it<br />
* Writing a new wiki page under the Operations page with a summary of best practices/new tools you discovered etc<br />
* Following up on action items that people volunteered to do during the meetup ;)<br />
* Organising a followup IRC meeting, if applicable<br />
<br />
==How Ops Meetups are planned==<br />
Ops Meetups are organised by the [[Ops Meetups Team]]. This team is an open team that meets regularly - if you are interested in this event, do get in touch!<br />
<br />
Here's a high-level timeline of the process:<br />
* Approximate date/region decided: 5 months before<br />
* Venue booked: 4 months before<br />
* Agenda Brainstorming Starts: 2 months before<br />
* Registration Opens: 2 months before<br />
* Draft Agenda Release: 1 Month before<br />
* Agenda Complete: 3 weeks before<br />
* All moderators found: 2 weeks before<br />
* Registration Closes: 1 week before (for catering)<br />
<br />
===Date and Region selection===<br />
The Ops Meetups gain much of their timing cues from the OpenStack release cycle. There is always an event at the OpenStack Summit, which is held in a regional rotation:<br />
* Year 1 - Late April/Early May - North America<br />
* Year 1 - Late October/Early November - Europe<br />
* Year 2 - Late April/Early May - North America<br />
* Year 2 - Late October/Early November - Asia Pacific<br />
<br />
There are also events between the summit. These have traditionally been held in February/March and August, however the cadence and regional location is currently being discussed by the [[Ops Meetups Team]].<br />
<br />
Based on community feedback, the [[Ops Meetups Team]] chooses the approximate dates and regions for events.<br />
<br />
===Venue Selection===<br />
Once an approximate date range (eg "mid-to-late August") and region (eg "North America") is known, work can begin on the venue. Finding a venue that's flexible, yet large enough to fit the growing ops community is always a challenge. Attendance has fluctuated over the years, but have generally ranged from 100 - 200. We have also had a varying number of parallel tracks depending on the facility:<br />
* Theater/fishbowl style seating for 100-200 <br />
** Note: the Philadelphia mid-cycle in March 2015 had 175+ registrations and approx. 150 people on-site<br />
** Note: Palo Alto mid-cycle in August 2015 had 303 registrations and approx 195 on site.<br />
** Note: Manchester mid-cycle in February 2016 had 130 on-site.<br />
* At least 2 rooms to run parallel breakout sessions or a themed track is desirable but not required.<br />
** Note: for the mid-cycle meetups, the group often meets all together in the morning, and at the end of the event for a feedback session. The rest of the schedule can be broken out into tracks. For example, in Philadelphia, the main room used in the morning was broken up into two spaces, which were used separately in the afternoon. In Tokyo, the large room was used for general sessions while a smaller room was used for an NFV themed track which was of particular interest to many local attendees.<br />
* A reliable wireless network, most likely for 500-600 devices<br />
* Projectors, screens, power strips and whiteboards for every room, several handheld microphones for large room(s)<br />
* Coffee and lunch breaks each day, possibly light breakfast depending on cost<br />
** Note: catering is typically where the largest costs are incurred, especially with increasing numbers. This is sometimes provided by the host, but has also been sponsored separately. <br />
* Convenient access to transport, hotels and other venues (eg for an evening event)<br />
* Signage directing people to the appropriate room<br />
* A registration/welcome table in an appropriate space<br />
** Note: for mid-cycle events hosted at an office building, security requirements can provide additional logistical hurdles<br />
<br />
<br />
<br />
We have been extremely fortunate to have had excellent organisations step up and offer their own space, or offer to underwrite a commercial meeting space. If you see someone from an organisation who has hosted one of these events before, please share your gratitude - it's a large part of what makes it possible. A very big thank you to our past hosts:<br />
* eBay/Paypal<br />
* Rackspace<br />
* Comcast<br />
* HP<br />
* Datacentred<br />
* Bloomberg<br />
* Enter<br />
* NTT<br />
* Deutsche Telekom<br />
<br />
<br />
In May 2016, the [[Ops Meetups Team]] decided the most fair way of finding a venue was to email out an open call for venues and see what came back. The key was to facilitate a fair process to choose between proposals, if we had more than one. This call for hosts should happen as soon as the region and approximate date range are decided, to allow the most possible time for planning.<br />
<br />
===Underwriters===<br />
The community strongly believes that Ops Meetups should be non-commercial events, and is willing to accept a cheaper "level of production" instead of being bombarded with marketing. However, running an event does still cost money!<br />
<br />
Underwriters are the financial backers of the event. They're organisations who believe in improving OpenStack ops, and usually run clouds themselves. Between them they cover any venue, catering and ancillary costs to run the event. In the past, we've added underwriter names and logos to the registration site, event signage and name badges. We've also allowed a modest number of banners to be placed in the main area, and encouraged a representative from each underwriter to welcome people to the event so their face and brand are known.<br />
<br />
In some cases, especially with an in-house venue and in-house catering, the host has also been the underwriter. However, according to OpenStack's event principles, we should facilitate equal participation from all commercial members of the community.<br />
<br />
===Topic Selection===<br />
Choosing the topics for the meetup is very important. You want to ensure that you have a reasonable balance between feedback gathering (especially covering current burning issues), best practice sharing, and sessions that get people actually participating.<br />
<br />
The general principle here is to get wide feedback - you don't want to have entirely the same topics every meetup, and you definitely don't want to always have the same people making the suggestions (lest it results in an Echo Chamber).<br />
<br />
To date, how this has worked has been an etherpad, such as https://etherpad.openstack.org/p/YVR-ops-meetup, seeded with information about the aims and session types of the ops meetup with the following sections for soliciting feedback:<br />
* Session Ideas - General Sessions<br />
* Session Ideas - Working Groups<br />
* Architecture Show & Tell (if you want to present, list your name and email below)<br />
* Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
<br />
Seeding a few known good sessions in each section to provide examples works well, and encouraging a few people to give +1s on their favourite session ease others who aren't as familiar with etherpad into this behaviour.<br />
<br />
Once the etherpad has run its course - normally for around a couple of weeks, the topics are decanted into a schedule across the rooms available, which is then shared with the community for feedback. Missing topics or topics with conflicts might be identified at this time (see also: Managing Conflicts).<br />
<br />
=== Scheduling===<br />
<br />
==== Room Selection, Layout & co-location ====<br />
<br />
So, the hardest rooms to get are the 'big' ones, for our full room<br />
discussion. <br />
<br />
For the 'big' rooms, there is an argument to maximise attendance<br />
somewhat, unlike the 'small' rooms where ideally we want only<br />
dedicated/interested people. Co-locating the larger rooms means that we<br />
basically have a lot more people we trap in our track for the entire<br />
time, by ensuring there's always something interesting for them going on.<br />
<br />
With good attendance numbers for the larger sessions, it ensures that<br />
the "feedback" aim of the events can be achieved in a broad manner,<br />
grabbing the widest views possible from the largest number of people.<br />
<br />
However, at 3 parallel rooms, it becomes quite difficult to schedule<br />
things so that people can generally get to everything they want to see<br />
So, these above argument breaks for large numbers of parallel rooms.<br />
I think 3 is about the limit for a single day. If we were ever to need 7<br />
more slots, then we should definitely split the large rooms over<br />
multiple days.<br />
<br />
<br />
Regarding the 'small' rooms - it's quite a bit different. We're not<br />
trying to maximise attendance overall, but it is a lot more important<br />
that people can get to the groups they want to - like the design summit<br />
overall. These are co-located just to avoid Thierry going insane He<br />
works so hard to get the schedule sorted out nicely for all the design<br />
summit projects. If there's a problem with other tracks in the design<br />
summit that want to switch some stuff to Wednesday, I'd be completely<br />
open to moving some of our stuff around this summit.<br />
<br />
There's also the days themselves to consider: Tuesday, Wednesday and<br />
Thursday are probably the 'better' days to have sessions - more than a<br />
few people arrive late and miss parts of Monday and leave early and miss<br />
parts of Friday.<br />
<br />
==== Managing Conflicts ====<br />
Conflicts in the layout grid is something to<br />
consider very heavily and get sanity checking from others on.<br />
<br />
Some times it just works out, for example, the Summit "101" being up against two very<br />
technical/advanced topics, since there are definitely different<br />
audiences there.<br />
<br />
There are also some topics where only certain classes of people<br />
care, and so you have to make sure that other more general topics are<br />
available so people stick around. eg if you're not running cinder,<br />
interested in multiple sites or federation, and they're the only things that are on ... what should you do for 40<br />
minutes?<br />
<br />
Then there are the topics that have shared interest. People interested<br />
in federations are also likely interested in multi-site clouds, so it<br />
isn't appropriate to co-schedule these. Similarly, people interested in<br />
billing are also probably interested in legacy applications.<br />
<br />
Use best judgement, and get wide feedback.<br />
<br />
=== Finding Moderators===<br />
Each session needs a moderator. Two methods for finding interested people have been tried in the past - call out on the ops mailing list separate to the agenda drafting/planning, and adding a section on the etherpad. The latter was markedly more successful, so be sure to add a section to the planning etherpad:<br />
<br />
Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
* Guide for Moderators: https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide<br />
* Tom Name <tom@example.org> - Introduction sessions, generally available if none else volunteers<br />
<br />
Then, once the planning etherpad has run its course, with a couple of mailing list prompts, and you've scheduled sessions, see how you go in matching up moderators with their area of interest. Moderators tend to write down the specific sessions they want to lead, so start there, then add the generalists, and so on.<br />
<br />
The final step is to fill the gaps - where there is no moderator assigned. Write some emails: Ask the existing moderator volunteers, ask the mailing list, and finally - if no moderator can be found, it probably means there is less interest than expected and the session should be replaced with something else.<br />
<br />
Hints:<br />
* Keep in mind that each session takes some time and effort to prepare, so typically don't ask one person to moderate more than two sessions.<br />
* First-time moderators might feel more comfortable working with a co-moderator, as would those tackling a difficult topic.<br />
* Since the work sessions take more prep, two or three moderators can be a good idea.<br />
<br />
=== Registration===<br />
We use the Foundation's Eventbrite page.<br />
<br />
Once registration is open, we monitor the numbers, adjust venue/food requirements accordingly and make sure things don't get out of control.<br />
<br />
Registration closes about a week before the event. Sometimes earlier if we're in a venue with special security requirements.<br />
<br />
===Advertising===<br />
Just ask Allison ;)<br />
<br />
Advertising this event is a balance. We want people who are experienced cloud operators to come - it's an event for them. However, if we broadcast loudly, in addition to our ops friends we'll get lots of attendees who are not that :) We attach a disclaimer to all of our email communication and registration pages in an attempt to avoid beginners accidentally attending and having a negative experience:<br />
<br />
***Note***: This event assumes OpenStack ops knowledge and is _not_ appropriate for beginners, or a place to learn about OpenStack. The event contains relatively few 'presentations' and is mostly a discussion-style event. To find other OpenStack events in your area, please visit www.openstack.org/events.<br />
<br />
That's obviously too long to put in a tweet, so normally start those with something like "Run an #OpenStack Cloud? ...."<br />
<br />
It's also very nice to have some prominent developers attend - so a direct tip-off to those folks is one option, or including a line in the weekly newsletter.<br />
<br />
Generally, the following promotion activities are performed:<br />
* Email previous Summit attendees that have indicated ops in their registration<br />
* Email previous attendees of the ops midcycles <br />
* Remind the Ops Mailing list<br />
* Tweet from the foundation twitter account<br />
* Contact the local meetup group<br />
<br />
Optionally, some other areas to try are:<br />
* Email a subset of the ActiveUser Contributors that would benefit from attending the ops midcycle<br />
* Reach out to user survey respondents who have indicated that they can be contacted<br />
<br />
===Working with Feedback===</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Denver2019&diff=169737Forum/Denver20192019-04-29T17:47:04Z<p>Emccormickva: /* Monday April 29 */</p>
<hr />
<div>== Etherpads ==<br />
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!<br />
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.<br />
<br />
=== Monday April 29 ===<br />
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-app-creds Keystone Application Credentials: Status and Planning]<br />
<br />
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-train-next-steps-for-standalone-ironic Next steps for standalone ironic]<br />
<br />
[12:00-12:40] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-operator-feedback Keystone Operator Feedback]<br />
<br />
[14:00-14:40] [https://etherpad.openstack.org/p/keystone-for-multi-tenancy-in-kubernetes Leveraging OpenStack Keystone for Multi-Tenancy Support in Kubernetes]<br />
<br />
[15:50-16:30] [https://etherpad.openstack.org/p/storyboard-pain-points Ibuprofen for Your StoryBoard Pain Points]<br />
<br />
[15:50-16:30] [https://etherpad.openstack.org/p/DEN-change-ownership-of-resources OpenStack: Change ownership of resources - followup]<br />
<br />
[14:40-15:20] [https://etherpad.openstack.org/p/DEN-Ops-Catch-Up Ops Community Gathering and Meetup Planning]<br />
<br />
=== Tuesday April 30 ===<br />
[9:50-10:30] [https://etherpad.openstack.org/p/DEN-deployment-tools-capabilities Deployment tools: define common capabilities]<br />
<br />
[10:50-11:30] [https://etherpad.openstack.org/p/DEN-ECG-MVP-feedback Edge Computing Group MVP Architecture feedback]<br />
<br />
[11:40-12:20] [https://etherpad.openstack.org/p/DEN-ECG-use-cases-discssion-feedback Edge Computing use cases discussion and feedback]<br />
<br />
[13:40-14:20] [https://etherpad.openstack.org/p/DEN-update-on-placement-extraction-from-nova Update on placement extraction from nova]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/DEN-ECG-roadmap-and-feedback What is the Edge Computing Group and what it should be doing in the next 6 months?]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/DEN-ptl-tips-and-tricks PTL Tips and Tricks]<br />
<br />
[16:20-17:00] [https://etherpad.openstack.org/p/new-contribs-state-and-deduplication Welcoming New Contributors State of the Union and Deduplication of Efforts] <br />
<br />
[1710-1750] [https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Ops War Stories/Architecture Show and Tell Lightning Talks]<br />
<br />
=== Wednesday May 1 ===<br />
[09:00-09:40] [https://etherpad.openstack.org/p/DEN-qa-onboarding QA Onboarding]<br />
<br />
[09:00-09:40] [https://etherpad.openstack.org/p/DEN-openlab-whats-next OpenLab: We Integrated K8s, What is Next?]<br />
<br />
[10:50-11:30] [https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback Users/Operators adoption of QA tools/plugins]<br />
<br />
[1340-1240] [https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Closing compute API feature gaps in the openstack CLI]<br />
<br />
[13:40-14:20] [https://etherpad.openstack.org/p/denver-forum-cinder-improving-drvr-cap-rep Improving Cinder Driver Capability Reporting]<br />
<br />
[14:30-15:10] [https://etherpad.openstack.org/p/denver-forum-cinder-direct-user-feedback Cinder Opportunity for Direct User Feedback]<br />
<br />
[2:50-3:30] [https://etherpad.openstack.org/p/consumption-models Consumption Models for Service Projects]<br />
<br />
[3:20-4:00] [https://etherpad.openstack.org/p/DEN-tripleo-forum-scale TripleO architecture for thousand node scale ]<br />
<br />
[15:20-16:00] [https://etherpad.openstack.org/p/DEN-Deletion-of-resources OpenStack: Project Resource Cleanup - followup]<br />
<br />
[4:20-5:00] [https://etherpad.openstack.org/p/DEN-drive-common-goals OpenStack: how to drive common goals]<br />
<br />
[17:10-17:50] [https://etherpad.openstack.org/p/DEN-Operator-end-user-Public-cloud-feedback OpenStack: Operator, end user and Public cloud feedback]<br />
<br />
==List of Brainstorming Etherpads==<br />
<br />
===Catch-alls===<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]<br />
<br />
===Etherpads from Teams and Working Groups===<br />
* [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto scaling SIG]<br />
* [https://etherpad.openstack.org/p/DEN-Train-EWG-brainstorming Enterprise Working Group (EWG)]<br />
* [https://etherpad.openstack.org/p/Denver-2019-Forum-DCN-Brainstorming DCN]<br />
* [https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]<br />
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]<br />
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming Manila]<br />
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/oslo-train-topics Oslo]<br />
* [https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self healing SIG]<br />
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]<br />
* [https://etherpad.openstack.org/p/tripleo-train-topics TripleO]<br />
<br />
===Etherpads from Pilot projects===<br />
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=166747Forum/Berlin20182018-11-15T13:23:11Z<p>Emccormickva: /* Thursday, November 15 */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
See also - [https://www.openstack.org/summit/berlin-2018/summit-schedule/#day=2018-11-13&track_groups=86 Full Forum Schedule]<br />
<br />
===Tuesday, November 13===<br />
* [1100 - 1140] - Release Team onboarding<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-cells-v2-updates Cells v2 updates]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-ironic-operator-feedback Ironic Operator Feedback]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-passport-program-feedback OpenStack Passport Program - feedback and next step]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-Contrib-Portal-Feedback StoryBoard Migration: The Remaining Blockers ]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-container-security Cross-project forum: securing containerized infrastructure]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-missing-features-public-cloud Far From Done: Public Clouds Needs You]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/api-berlin-forum-brainstorming Cross-project Open API 3.0 support]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-ironic-hardware-inventory Hardware Inventory with Ironic]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-getting-users-involved Getting OpenStack users involved in the project ]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-Cinder_Usage_Outside_OpenStack Cinder Usage Outside OpenStack]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/Creating_a_cinder_data_service Creating a Cinder Data Service]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-tc-community-outreach Community outreach when culture, time zones, and language differ]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG Meeting]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-Cinder_User_Survey_Responses Cinder User Survey Feedback Session]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-airship-qa Leveraging Airship as an integration and QA enabler]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-Cinder_at_the_Edge Cinder and its role at the Edge]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-reusable-zuul-job-configurations Reusable Zuul Job Configurations]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-qa-onboarding QA onboarding]<br />
<br />
===Wednesday, November 14===<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-nfv-hpc-pain-points NFV/HPC pain points ]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-qa-ops-user-feedback Users / Operators adoption of QA tools / plugins]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-zuul-jobs-marketplace A marketplace for sharing Zuul jobs and roles]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/expose-sigs-and-wgs Expose SIGs and WGs]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/Berlin2018-Forum-ceph-is-great Ceph is great for openstack and you should use it]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-bfv-improvements Boot from volume (BFV) improvements]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/heat-user-berlin Orchestration (Heat) Ops/Users feedback session]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-better-expose-what-we-produce OpenStack: Better expose what we produce ]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-integrating-iot-device-mgmt-with-edge-cloud Integrating IOT Device Management with the Edge Cloud]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/Berlin2018-Forum-Extending-Blazar-reservations Extending Blazar reservations to new resource types]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-opendev-feedback-and-missing-features OpenDev (nee Infra team) feedback and missing features]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-Contrib-Guide-Ops The Contributor Guide: Ops Feedback Session]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-ironic-smartnics Smartnics, Ironic, Neutron]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-edge-use-cases-and-requirements Edge use cases and requirements]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-ask-me-anything-about-starlingx Ask Me Anything ... about StarlingX]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-deletion-of-project-resources Deletion of project and project resources ]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/Kata-POC-Ber-Forum What's stopping you from starting a Kata proof-of-concept today?]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-ironic-edge Baremetal at the Edge]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/Container-Isolation-BerlinForum Exactly how much is more container isolation worth to you?]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-getting-operators-bugfixes-upstreamed Getting operators bugfixes upstreamed]<br />
<br />
===Thursday, November 15===<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/BER-bug-triage Bug triage: Why not all the community?]<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Autoscaling Integration, improvement, and feedback]<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/Kata-K8s-Integration-BerlinForum Kata Containers Kubernetes integration: CRI, OCI, and containerd shimv2 API]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/manila-berlin Setting the compass for Manila RWX cloud storage]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/BER-deployment-tools Developing a Standard Deployment Tools Comparison]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/BER-volume-encryption-forum Volume Encryption]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-cross-technical-leadership Cross-technical leadership session (OpenStack, Kata, StarlingX, Airship, Zuul)]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-Ops-Community-Docs Ops Docs working session]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-Contrib-Portal Making the Contributor Portal More Useful]<br />
* [1140 - 1240] - [https://etherpad.openstack.org/p/BER-stein-keystone-as-idp Keystone as an Identity Provider Proxy]<br />
* [1140 - 1240] - [https://etherpad.openstack.org/p/BER-concurrency-limits-for-resource-creati Concurrency limits for service instance creation]<br />
* [1220 - 1340] - [https://etherpad.openstack.org/p/BER-Feedback-Session Feedback Session (L1 7.1a/NY1)]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-change-ownership-of-resources Change of ownership of resources ]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-containerized-app-reqmts-on-kubernetes-at-edge Containerized Applications' Requirements on Kubernetes Cluster at the Edge]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-sdk-certification You don't know nothing about Public Cloud SDKs, yet]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-uc OpenStack User Committee]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-stein-keystone-feedback Keystone Operator Feedback]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-cloud-vision "Vision for OpenStack clouds" discussion]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-MVP-architecture-for-edge MVP (Minimum Viable Product) architecture for edge]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-placement-extract Update on placement extraction from nova]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-python-bindings-for-the-placement-api Python bindings for the placement API]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-Ops-Catch-Up Ops Meetups Team Catch-Up]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-tc-vision-retrospective Technical Committee Vision Retrospective]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-rally-tempest-change-validation Using Rally/Tempest for change validation]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-18-kayobe-feedback-roadmap Kayobe user feedback & roadmap]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-t-series-goals T series community goal discussion]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-Forum-Fenix-Upgrade Fenix - Rolling Maintenance and Upgrade]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-tripleo-undercloud-edge TripleO Edge undercloud architecture]<br />
<br />
==List of Brainstorming Etherpads (Historical)==<br />
Topic selection is now complete, but see below for session idea brainstorming that was done prior to selection.<br />
<br />
'''These are just kept for historical reference. Please do not use for any additional ideas.'''<br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/api-berlin-forum-brainstorming API]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/cinder-berlin-forum-proposals Cinder]<br />
* [https://etherpad.openstack.org/p/cyborg-forum-berlin Cyborg]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/fenix-forum-stein Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/kayobe-stein-summit Kayobe]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/kolla-forum-stein Kolla]<br />
* [https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm Manila]<br />
* [https://etherpad.openstack.org/p/berlin-monasca-forum-brainstorming Monasca]<br />
* [https://etherpad.openstack.org/p/nova-forum-stein Nova]<br />
* [https://etherpad.openstack.org/p/OSA-berlin-planning OpenStack-Ansible]<br />
* [https://etherpad.openstack.org/p/OpenStackHelmBerlinForumBrainstorming OpenStack-Helm]<br />
* [https://etherpad.openstack.org/p/ops-forum-stein Operators]<br />
* [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-scientific-sig Scientific SIG]<br />
* [https://etherpad.openstack.org/p/berlin-self-healing-sig-brainstorm Self-Healing SIG]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/tripleo-forum-stein TripleO]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=166746Forum/Berlin20182018-11-15T13:20:40Z<p>Emccormickva: /* Thursday, November 15 */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
See also - [https://www.openstack.org/summit/berlin-2018/summit-schedule/#day=2018-11-13&track_groups=86 Full Forum Schedule]<br />
<br />
===Tuesday, November 13===<br />
* [1100 - 1140] - Release Team onboarding<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-cells-v2-updates Cells v2 updates]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-ironic-operator-feedback Ironic Operator Feedback]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-passport-program-feedback OpenStack Passport Program - feedback and next step]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-Contrib-Portal-Feedback StoryBoard Migration: The Remaining Blockers ]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-container-security Cross-project forum: securing containerized infrastructure]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-missing-features-public-cloud Far From Done: Public Clouds Needs You]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/api-berlin-forum-brainstorming Cross-project Open API 3.0 support]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-ironic-hardware-inventory Hardware Inventory with Ironic]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-getting-users-involved Getting OpenStack users involved in the project ]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-Cinder_Usage_Outside_OpenStack Cinder Usage Outside OpenStack]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/Creating_a_cinder_data_service Creating a Cinder Data Service]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-tc-community-outreach Community outreach when culture, time zones, and language differ]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG Meeting]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-Cinder_User_Survey_Responses Cinder User Survey Feedback Session]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-airship-qa Leveraging Airship as an integration and QA enabler]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-Cinder_at_the_Edge Cinder and its role at the Edge]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-reusable-zuul-job-configurations Reusable Zuul Job Configurations]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-qa-onboarding QA onboarding]<br />
<br />
===Wednesday, November 14===<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-nfv-hpc-pain-points NFV/HPC pain points ]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-qa-ops-user-feedback Users / Operators adoption of QA tools / plugins]<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-zuul-jobs-marketplace A marketplace for sharing Zuul jobs and roles]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/expose-sigs-and-wgs Expose SIGs and WGs]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/Berlin2018-Forum-ceph-is-great Ceph is great for openstack and you should use it]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-bfv-improvements Boot from volume (BFV) improvements]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/heat-user-berlin Orchestration (Heat) Ops/Users feedback session]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-better-expose-what-we-produce OpenStack: Better expose what we produce ]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-integrating-iot-device-mgmt-with-edge-cloud Integrating IOT Device Management with the Edge Cloud]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/Berlin2018-Forum-Extending-Blazar-reservations Extending Blazar reservations to new resource types]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-opendev-feedback-and-missing-features OpenDev (nee Infra team) feedback and missing features]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-Contrib-Guide-Ops The Contributor Guide: Ops Feedback Session]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-ironic-smartnics Smartnics, Ironic, Neutron]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-edge-use-cases-and-requirements Edge use cases and requirements]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-ask-me-anything-about-starlingx Ask Me Anything ... about StarlingX]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-deletion-of-project-resources Deletion of project and project resources ]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/Kata-POC-Ber-Forum What's stopping you from starting a Kata proof-of-concept today?]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-ironic-edge Baremetal at the Edge]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/Container-Isolation-BerlinForum Exactly how much is more container isolation worth to you?]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-getting-operators-bugfixes-upstreamed Getting operators bugfixes upstreamed]<br />
<br />
===Thursday, November 15===<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/BER-bug-triage Bug triage: Why not all the community?]<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Autoscaling Integration, improvement, and feedback]<br />
* [0900 - 0940] - [https://etherpad.openstack.org/p/Kata-K8s-Integration-BerlinForum Kata Containers Kubernetes integration: CRI, OCI, and containerd shimv2 API]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/manila-berlin Setting the compass for Manila RWX cloud storage]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/BER-deployment-tools Developing a Standard Deployment Tools Comparison]<br />
* [0950 - 1030] - [https://etherpad.openstack.org/p/BER-volume-encryption-forum Volume Encryption]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-cross-technical-leadership Cross-technical leadership session (OpenStack, Kata, StarlingX, Airship, Zuul)]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-Ops-Community-Docs Ops Docs working session]<br />
* [1050 - 1130] - [https://etherpad.openstack.org/p/BER-Contrib-Portal Making the Contributor Portal More Useful]<br />
* [1140 - 1240] - [https://etherpad.openstack.org/p/BER-stein-keystone-as-idp Keystone as an Identity Provider Proxy]<br />
* [1140 - 1240] - [https://etherpad.openstack.org/p/BER-concurrency-limits-for-resource-creati Concurrency limits for service instance creation]<br />
* [1220 - 1340] - [https://etherpad.openstack.org/p/BER-Feedback-Session Feedback Session (L1 7.1a/NY1)]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-change-ownership-of-resources Change of ownership of resources ]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-containerized-app-reqmts-on-kubernetes-at-edge Containerized Applications' Requirements on Kubernetes Cluster at the Edge]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-sdk-certification You don't know nothing about Public Cloud SDKs, yet]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-uc OpenStack User Committee]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-stein-keystone-feedback Keystone Operator Feedback]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-cloud-vision "Vision for OpenStack clouds" discussion]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-MVP-architecture-for-edge MVP (Minimum Viable Product) architecture for edge]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-placement-extract Update on placement extraction from nova]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-python-bindings-for-the-placement-api Python bindings for the placement API]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-Ops-Catch-Up]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-tc-vision-retrospective Technical Committee Vision Retrospective]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-rally-tempest-change-validation Using Rally/Tempest for change validation]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-18-kayobe-feedback-roadmap Kayobe user feedback & roadmap]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-t-series-goals T series community goal discussion]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-Forum-Fenix-Upgrade Fenix - Rolling Maintenance and Upgrade]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-tripleo-undercloud-edge TripleO Edge undercloud architecture]<br />
<br />
==List of Brainstorming Etherpads (Historical)==<br />
Topic selection is now complete, but see below for session idea brainstorming that was done prior to selection.<br />
<br />
'''These are just kept for historical reference. Please do not use for any additional ideas.'''<br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/api-berlin-forum-brainstorming API]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/cinder-berlin-forum-proposals Cinder]<br />
* [https://etherpad.openstack.org/p/cyborg-forum-berlin Cyborg]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/fenix-forum-stein Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/kayobe-stein-summit Kayobe]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/kolla-forum-stein Kolla]<br />
* [https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm Manila]<br />
* [https://etherpad.openstack.org/p/berlin-monasca-forum-brainstorming Monasca]<br />
* [https://etherpad.openstack.org/p/nova-forum-stein Nova]<br />
* [https://etherpad.openstack.org/p/OSA-berlin-planning OpenStack-Ansible]<br />
* [https://etherpad.openstack.org/p/OpenStackHelmBerlinForumBrainstorming OpenStack-Helm]<br />
* [https://etherpad.openstack.org/p/ops-forum-stein Operators]<br />
* [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-scientific-sig Scientific SIG]<br />
* [https://etherpad.openstack.org/p/berlin-self-healing-sig-brainstorm Self-Healing SIG]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/tripleo-forum-stein TripleO]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Operations/Meetups&diff=166006Operations/Meetups2018-10-16T16:06:47Z<p>Emccormickva: /* Venue Selection */</p>
<hr />
<div><div style="float:right">__TOC__</div><br />
<br />
Ops Meetups give people who run clouds a place to congregate, swap best practices, ideas and give feedback. It has a mostly round table/working/discussion session feel, with only a small number of presentations, with the following aims:<br />
# Gather feedback on the issues that come up in running OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running clouds<br />
<br />
Ops Meetups are typically held as part of the 6-monthly design summit, and also once "mid-cycle". Previous and upcoming Ops Meetups are listed below:<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
==== planning ====<br />
* The next OpsMeetup will co-locate with PTG (Denver, September 10-14 2018)<br />
* [https://www.openstack.org/ptg/ Denver PTG]<br />
* [https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018 Etherpad for Denver OpsMeetup]<br />
<br />
==== Rocky release (Vancouver, May 21-24 2018) ====<br />
* [https://wiki.openstack.org/wiki/Forum/Vancouver2018 Forum wiki page]<br />
<br />
==== Mid Cycle (Tokyo, March 2018) ====<br />
* [https://wiki.openstack.org/wiki/Operations/Meetups/TYO-ops-meetup Wiki page for Tokyo]<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup-2018 Tokyo meetup agenda planning]<br />
<br />
* venue discussion<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2018 Proposal etherpad for 1st meet up 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-spring-2018 Feb/Mar 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-aug-2018 Aug 2018]<br />
<br />
==== Queens release (Sydney, November 6-8 2017) ====<br />
*[https://wiki.openstack.org/wiki/Forum/Sydney2017 Forum landing wiki page]<br />
* [https://etherpad.openstack.org/p/SYD-ops-session-ideas Forum planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2017) ====<br />
* August 9 & 10 in Mexico City, Mexico<br />
* [https://etherpad.openstack.org/p/MEX-ops-meetup planning etherpad]<br />
<br />
==== Pike release (Boston, May 8-11, 2017) ====<br />
<br />
*[https://etherpad.openstack.org/p/BOS-forum-ops-catch-up ops meet up etherpad]<br />
*[https://wiki.openstack.org/wiki/Forum/Boston2017 all Forum etherpads]<br />
<br />
==== Mid-Cycle (Mar, 2017) ====<br />
* March 15 & 16 in Milan, Italy<br />
* [https://etherpad.openstack.org/p/MIL-ops-meetup planning etherpad]<br />
<br />
====Ocata release (Barcelona, October 2016)====<br />
* [https://etherpad.openstack.org/p/BCN-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Aug 25-26, 2016)====<br />
* August 25 & 26, New York City, USA<br />
* [https://etherpad.openstack.org/p/NYC-ops-meetup planning etherpad]<br />
<br />
====Newton release (Austin, May 2016)====<br />
* [https://etherpad.openstack.org/p/AUS-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Feb, 2016)====<br />
* February 15 & 16, Manchester, UK<br />
* [https://etherpad.openstack.org/p/european-ops-meetup-planning original planning etherpad]<br />
* [https://etherpad.openstack.org/p/MAN-ops-meetup second planning etherpad]<br />
* [https://europeanopenstackoperatorsmeetup.eventbrite.com/ tickets on eventbrite]<br />
<br />
====Mitaka release (Tokyo, October 2015)====<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2015)====<br />
* August 18 & 19, Palo Alto<br />
* [http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924 Registration]<br />
* [https://etherpad.openstack.org/p/PAO-ops-meetup planning etherpad]<br />
<br />
===="L" release (Vancouver, May 2015)====<br />
* [https://etherpad.openstack.org/p/YVR-ops-meetup planning etherpad]<br />
* [[Design_Summit/Liberty/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-Cycle (Mar, 2015)====<br />
* March 9th and 10th, Philadelphia, USA<br />
* [https://etherpad.openstack.org/p/PHL-ops-meetup etherpads]<br />
<br />
==== Kilo (Paris, November 2014) ====<br />
<br />
* [http://kilodesignsummit.sched.org/overview/type/ops+summit schedule]<br />
* [[Summit/Kilo/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-cycle (San Antonio, August 2014) ====<br />
<br />
* [http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/ schedule]<br />
* [https://etherpad.openstack.org/p/SAT-ops-meetup Etherpads]<br />
<br />
==== Juno (Atlanta, May 2014) ====<br />
<br />
* [http://junodesignsummit.sched.org/overview/type/ops+meetup schedule]<br />
* [[Summit/Juno/Etherpads#Ops|Etherpads]]<br />
<br />
<br />
==== Mid-Cycle (San Jose, March 2014) ====<br />
* [https://etherpad.openstack.org/p/operators-feedback-mar14 Etherpad]<br />
</div><br />
==Moderators Guide==<br />
Thank you very much for stepping up to be moderators at the ops meetup. Your work is key to our success!<br />
<br />
You are in control of your sessions, however, this document lay down some ideas about what we've seen in the past makes a good session, in case it helps.<br />
<br />
We have two different types of sessions. General Sessions and Working Groups. Below, I've separated them out so you can read what's relevant to you.<br />
<br />
We have three overall aims:<br />
# Gather feedback on the issues that come up in running or using OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running or using clouds<br />
<br />
<br />
===General Sessions===<br />
<br />
Basically, it's you, an etherpad, and room full of a couple hundred people who have OpenStack experience. As the moderator, your efforts result in actionable things we can work on, and the satisfied audience.<br />
<br />
* Introduce yourself to the audio guy or gal. You'll be provided with a microphone and asked about laptop connection.<br />
* The best thing to do is convince one of your friends to control the laptop. Get them to control the display of the etherpad, and if it gets big, scroll up and down to ensure the most relevant parts are seen.<br />
* At the start of the session give a 30 second intro to the etherpad, and ask everyone to take notes using it. (Many attendees will not be used to etherpads)<br />
* Kick off the discussion on time, perhaps by starting with some open ended questions, or a show of hands to understand the audience<br />
* Aim to get it to that nirvana state, where the conversation continues without your help<br />
* Don't fall into "Question and Answer" mode - just because you're up the front of the room, some people might expect you to do this. Steer back toward discussion always.<br />
* There will be microphone hogs. Do not be afraid to cut them off. Using language like "Thank you, that is important, we have recorded that on the etherpad" will mean there'll be no hard feelings.<br />
* If you see a nice transition between different topics, take it!<br />
* Most importantly: try and aim for every discussion to have at least one action item - something we can work on. If we don't do this, people are going to stop coming to these things <br />
<br />
<br />
Overall, have fun! Also *be* fun! If you get bored, the audience will sense it - so if it happens start a new topic. Spontaneity is good! Asking people to do things (file a bug, start a mailing list post) is good!<br />
<br />
<br />
===Working Groups - "Small, working sessions"===<br />
These sessions are for a focus on specific topics, and they are long sessions (normally 80 minutes) so you can actually, legitimately get work done - not just talk.<br />
<br />
You'll have yourself, and a small group of people who are experienced with OpenStack and actually very interested in getting involved. It's your job as facilitator to try and convert each and every one of these people into a proactive member of your working group, ideally continuing their tenure well after the summit.<br />
<br />
Since these are mostly longer session, and about much more specific things, it requires a bit more planning. For some of the groups, you will have met before and have work and processes to continue. Try and seed your etherpads with this information prior to the session.<br />
<br />
Try and think of some concrete things that can be done during your time, but also be ready and open to the suggestions of the attendees. If there's a great idea that everyone believes in, go for it and get it done. File bugs. File blueprints. Submit patches. Write documents. Use the whiteboard. You have time for all of this <br />
<br />
<br />
Of course, all of this information is general. You are the rockstars here - do whatever you think is best . Tom will be on hand for much of the two days for assistance. (call +886 98833 1200 if anything goes horribly wrong)<br />
<br />
There are also a few sessions which are a bit different...<br />
<br />
===Architecture Show and Tell===<br />
This is a series of lightening talks - basically a 5-8 minute talk about something cool about your deployment.<br />
<br />
If you're moderating this, one of the main duties you have to perform (or delegate) is that of timekeeping - we normally cycle through many talks in each session.<br />
<br />
Best practice is to get any slides people are using into one laptop before the start of the session.<br />
<br />
===Pre-and Post Meetup===<br />
Fully realising you are a volunteer with limited time and that you might not get around to any of this, some of the things that are cool to do before or after the meetup are:<br />
* Post a thread on the ops ML asking for ideas for your session (and also advertising it)<br />
* Giving a tweet out with the schedule details<br />
* Filling in the etherpad with some conversation start topics (or, if you are a developer looking for feedback - questions you would like answered)<br />
* Posting on the Ops ML a summary of the session and linking to the etherpad for those who couldn't make it<br />
* Writing a new wiki page under the Operations page with a summary of best practices/new tools you discovered etc<br />
* Following up on action items that people volunteered to do during the meetup ;)<br />
* Organising a followup IRC meeting, if applicable<br />
<br />
==How Ops Meetups are planned==<br />
Ops Meetups are organised by the [[Ops Meetups Team]]. This team is an open team that meets regularly - if you are interested in this event, do get in touch!<br />
<br />
Here's a high-level timeline of the process:<br />
* Approximate date/region decided: 5 months before<br />
* Venue booked: 4 months before<br />
* Agenda Brainstorming Starts: 2 months before<br />
* Registration Opens: 2 months before<br />
* Draft Agenda Release: 1 Month before<br />
* Agenda Complete: 3 weeks before<br />
* All moderators found: 2 weeks before<br />
* Registration Closes: 1 week before (for catering)<br />
<br />
===Date and Region selection===<br />
The Ops Meetups gain much of their timing cues from the OpenStack release cycle. There is always an event at the OpenStack Summit, which is held in a regional rotation:<br />
* Year 1 - Late April/Early May - North America<br />
* Year 1 - Late October/Early November - Europe<br />
* Year 2 - Late April/Early May - North America<br />
* Year 2 - Late October/Early November - Asia Pacific<br />
<br />
There are also events between the summit. These have traditionally been held in February/March and August, however the cadence and regional location is currently being discussed by the [[Ops Meetups Team]].<br />
<br />
Based on community feedback, the [[Ops Meetups Team]] chooses the approximate dates and regions for events.<br />
<br />
===Venue Selection===<br />
Once an approximate date range (eg "mid-to-late August") and region (eg "North America") is known, work can begin on the venue. Finding a venue that's flexible, yet large enough to fit the growing ops community is always a challenge. Attendance has fluctuated over the years, but have generally ranged from 100 - 200. We have also had a varying number of parallel tracks depending on the facility:<br />
* Theater/fishbowl style seating for 100-200 <br />
** Note: the Philadelphia mid-cycle in March 2015 had 175+ registrations and approx. 150 people on-site<br />
** Note: Palo Alto mid-cycle in August 2015 had 303 registrations and approx 195 on site.<br />
** Note: Manchester mid-cycle in February 2016 had 130 on-site.<br />
* At least 2 rooms to run parallel breakout sessions or a themed track is desirable but not required.<br />
** Note: for the mid-cycle meetups, the group often meets all together in the morning, and at the end of the event for a feedback session. The rest of the schedule can be broken out into tracks. For example, in Philadelphia, the main room used in the morning was broken up into two spaces, which were used separately in the afternoon. In Tokyo, the large room was used for general sessions while a smaller room was used for an NFV themed track which was of particular interest to many local attendees.<br />
* A reliable wireless network, most likely for 500-600 devices<br />
* Projectors, screens, power strips and whiteboards for every room, several handheld microphones for large room(s)<br />
* Coffee and lunch breaks each day, possibly light breakfast depending on cost<br />
** Note: catering is typically where the largest costs are incurred, especially with increasing numbers. This is sometimes provided by the host, but has also been sponsored separately. <br />
* Convenient access to transport, hotels and other venues (eg for an evening event)<br />
* Signage directing people to the appropriate room<br />
* A registration/welcome table in an appropriate space<br />
** Note: for mid-cycle events hosted at an office building, security requirements can provide additional logistical hurdles<br />
<br />
<br />
<br />
We have been extremely fortunate to have had excellent organisations step up and offer their own space, or offer to underwrite a commercial meeting space. If you see someone from an organisation who has hosted one of these events before, please share your gratitude - it's a large part of what makes it possible. A very big thank you to our past hosts:<br />
* eBay/Paypal<br />
* Rackspace<br />
* Comcast<br />
* HP<br />
* Datacentred<br />
* Bloomberg<br />
* Enter<br />
* NTT<br />
<br />
<br />
In May 2016, the [[Ops Meetups Team]] decided the most fair way of finding a venue was to email out an open call for venues and see what came back. The key was to facilitate a fair process to choose between proposals, if we had more than one. This call for hosts should happen as soon as the region and approximate date range are decided, to allow the most possible time for planning.<br />
<br />
===Underwriters===<br />
The community strongly believes that Ops Meetups should be non-commercial events, and is willing to accept a cheaper "level of production" instead of being bombarded with marketing. However, running an event does still cost money!<br />
<br />
Underwriters are the financial backers of the event. They're organisations who believe in improving OpenStack ops, and usually run clouds themselves. Between them they cover any venue, catering and ancillary costs to run the event. In the past, we've added underwriter names and logos to the registration site, event signage and name badges. We've also allowed a modest number of banners to be placed in the main area, and encouraged a representative from each underwriter to welcome people to the event so their face and brand are known.<br />
<br />
In some cases, especially with an in-house venue and in-house catering, the host has also been the underwriter. However, according to OpenStack's event principles, we should facilitate equal participation from all commercial members of the community.<br />
<br />
===Topic Selection===<br />
Choosing the topics for the meetup is very important. You want to ensure that you have a reasonable balance between feedback gathering (especially covering current burning issues), best practice sharing, and sessions that get people actually participating.<br />
<br />
The general principle here is to get wide feedback - you don't want to have entirely the same topics every meetup, and you definitely don't want to always have the same people making the suggestions (lest it results in an Echo Chamber).<br />
<br />
To date, how this has worked has been an etherpad, such as https://etherpad.openstack.org/p/YVR-ops-meetup, seeded with information about the aims and session types of the ops meetup with the following sections for soliciting feedback:<br />
* Session Ideas - General Sessions<br />
* Session Ideas - Working Groups<br />
* Architecture Show & Tell (if you want to present, list your name and email below)<br />
* Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
<br />
Seeding a few known good sessions in each section to provide examples works well, and encouraging a few people to give +1s on their favourite session ease others who aren't as familiar with etherpad into this behaviour.<br />
<br />
Once the etherpad has run its course - normally for around a couple of weeks, the topics are decanted into a schedule across the rooms available, which is then shared with the community for feedback. Missing topics or topics with conflicts might be identified at this time (see also: Managing Conflicts).<br />
<br />
=== Scheduling===<br />
<br />
==== Room Selection, Layout & co-location ====<br />
<br />
So, the hardest rooms to get are the 'big' ones, for our full room<br />
discussion. <br />
<br />
For the 'big' rooms, there is an argument to maximise attendance<br />
somewhat, unlike the 'small' rooms where ideally we want only<br />
dedicated/interested people. Co-locating the larger rooms means that we<br />
basically have a lot more people we trap in our track for the entire<br />
time, by ensuring there's always something interesting for them going on.<br />
<br />
With good attendance numbers for the larger sessions, it ensures that<br />
the "feedback" aim of the events can be achieved in a broad manner,<br />
grabbing the widest views possible from the largest number of people.<br />
<br />
However, at 3 parallel rooms, it becomes quite difficult to schedule<br />
things so that people can generally get to everything they want to see<br />
So, these above argument breaks for large numbers of parallel rooms.<br />
I think 3 is about the limit for a single day. If we were ever to need 7<br />
more slots, then we should definitely split the large rooms over<br />
multiple days.<br />
<br />
<br />
Regarding the 'small' rooms - it's quite a bit different. We're not<br />
trying to maximise attendance overall, but it is a lot more important<br />
that people can get to the groups they want to - like the design summit<br />
overall. These are co-located just to avoid Thierry going insane He<br />
works so hard to get the schedule sorted out nicely for all the design<br />
summit projects. If there's a problem with other tracks in the design<br />
summit that want to switch some stuff to Wednesday, I'd be completely<br />
open to moving some of our stuff around this summit.<br />
<br />
There's also the days themselves to consider: Tuesday, Wednesday and<br />
Thursday are probably the 'better' days to have sessions - more than a<br />
few people arrive late and miss parts of Monday and leave early and miss<br />
parts of Friday.<br />
<br />
==== Managing Conflicts ====<br />
Conflicts in the layout grid is something to<br />
consider very heavily and get sanity checking from others on.<br />
<br />
Some times it just works out, for example, the Summit "101" being up against two very<br />
technical/advanced topics, since there are definitely different<br />
audiences there.<br />
<br />
There are also some topics where only certain classes of people<br />
care, and so you have to make sure that other more general topics are<br />
available so people stick around. eg if you're not running cinder,<br />
interested in multiple sites or federation, and they're the only things that are on ... what should you do for 40<br />
minutes?<br />
<br />
Then there are the topics that have shared interest. People interested<br />
in federations are also likely interested in multi-site clouds, so it<br />
isn't appropriate to co-schedule these. Similarly, people interested in<br />
billing are also probably interested in legacy applications.<br />
<br />
Use best judgement, and get wide feedback.<br />
<br />
=== Finding Moderators===<br />
Each session needs a moderator. Two methods for finding interested people have been tried in the past - call out on the ops mailing list separate to the agenda drafting/planning, and adding a section on the etherpad. The latter was markedly more successful, so be sure to add a section to the planning etherpad:<br />
<br />
Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
* Guide for Moderators: https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide<br />
* Tom Name <tom@example.org> - Introduction sessions, generally available if none else volunteers<br />
<br />
Then, once the planning etherpad has run its course, with a couple of mailing list prompts, and you've scheduled sessions, see how you go in matching up moderators with their area of interest. Moderators tend to write down the specific sessions they want to lead, so start there, then add the generalists, and so on.<br />
<br />
The final step is to fill the gaps - where there is no moderator assigned. Write some emails: Ask the existing moderator volunteers, ask the mailing list, and finally - if no moderator can be found, it probably means there is less interest than expected and the session should be replaced with something else.<br />
<br />
Hints:<br />
* Keep in mind that each session takes some time and effort to prepare, so typically don't ask one person to moderate more than two sessions.<br />
* First-time moderators might feel more comfortable working with a co-moderator, as would those tackling a difficult topic.<br />
* Since the work sessions take more prep, two or three moderators can be a good idea.<br />
<br />
=== Registration===<br />
We use the Foundation's Eventbrite page.<br />
<br />
Once registration is open, we monitor the numbers, adjust venue/food requirements accordingly and make sure things don't get out of control.<br />
<br />
Registration closes about a week before the event. Sometimes earlier if we're in a venue with special security requirements.<br />
<br />
===Advertising===<br />
Just ask Allison ;)<br />
<br />
Advertising this event is a balance. We want people who are experienced cloud operators to come - it's an event for them. However, if we broadcast loudly, in addition to our ops friends we'll get lots of attendees who are not that :) We attach a disclaimer to all of our email communication and registration pages in an attempt to avoid beginners accidentally attending and having a negative experience:<br />
<br />
***Note***: This event assumes OpenStack ops knowledge and is _not_ appropriate for beginners, or a place to learn about OpenStack. The event contains relatively few 'presentations' and is mostly a discussion-style event. To find other OpenStack events in your area, please visit www.openstack.org/events.<br />
<br />
That's obviously too long to put in a tweet, so normally start those with something like "Run an #OpenStack Cloud? ...."<br />
<br />
It's also very nice to have some prominent developers attend - so a direct tip-off to those folks is one option, or including a line in the weekly newsletter.<br />
<br />
Generally, the following promotion activities are performed:<br />
* Email previous Summit attendees that have indicated ops in their registration<br />
* Email previous attendees of the ops midcycles <br />
* Remind the Ops Mailing list<br />
* Tweet from the foundation twitter account<br />
* Contact the local meetup group<br />
<br />
Optionally, some other areas to try are:<br />
* Email a subset of the ActiveUser Contributors that would benefit from attending the ops midcycle<br />
* Reach out to user survey respondents who have indicated that they can be contacted<br />
<br />
===Working with Feedback===</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Operations/Meetups&diff=166005Operations/Meetups2018-10-16T16:06:24Z<p>Emccormickva: /* Venue Selection */</p>
<hr />
<div><div style="float:right">__TOC__</div><br />
<br />
Ops Meetups give people who run clouds a place to congregate, swap best practices, ideas and give feedback. It has a mostly round table/working/discussion session feel, with only a small number of presentations, with the following aims:<br />
# Gather feedback on the issues that come up in running OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running clouds<br />
<br />
Ops Meetups are typically held as part of the 6-monthly design summit, and also once "mid-cycle". Previous and upcoming Ops Meetups are listed below:<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
==== planning ====<br />
* The next OpsMeetup will co-locate with PTG (Denver, September 10-14 2018)<br />
* [https://www.openstack.org/ptg/ Denver PTG]<br />
* [https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018 Etherpad for Denver OpsMeetup]<br />
<br />
==== Rocky release (Vancouver, May 21-24 2018) ====<br />
* [https://wiki.openstack.org/wiki/Forum/Vancouver2018 Forum wiki page]<br />
<br />
==== Mid Cycle (Tokyo, March 2018) ====<br />
* [https://wiki.openstack.org/wiki/Operations/Meetups/TYO-ops-meetup Wiki page for Tokyo]<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup-2018 Tokyo meetup agenda planning]<br />
<br />
* venue discussion<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2018 Proposal etherpad for 1st meet up 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-spring-2018 Feb/Mar 2018]<br />
** [https://etherpad.openstack.org/p/ops-meetup-venue-discuss-aug-2018 Aug 2018]<br />
<br />
==== Queens release (Sydney, November 6-8 2017) ====<br />
*[https://wiki.openstack.org/wiki/Forum/Sydney2017 Forum landing wiki page]<br />
* [https://etherpad.openstack.org/p/SYD-ops-session-ideas Forum planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2017) ====<br />
* August 9 & 10 in Mexico City, Mexico<br />
* [https://etherpad.openstack.org/p/MEX-ops-meetup planning etherpad]<br />
<br />
==== Pike release (Boston, May 8-11, 2017) ====<br />
<br />
*[https://etherpad.openstack.org/p/BOS-forum-ops-catch-up ops meet up etherpad]<br />
*[https://wiki.openstack.org/wiki/Forum/Boston2017 all Forum etherpads]<br />
<br />
==== Mid-Cycle (Mar, 2017) ====<br />
* March 15 & 16 in Milan, Italy<br />
* [https://etherpad.openstack.org/p/MIL-ops-meetup planning etherpad]<br />
<br />
====Ocata release (Barcelona, October 2016)====<br />
* [https://etherpad.openstack.org/p/BCN-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Aug 25-26, 2016)====<br />
* August 25 & 26, New York City, USA<br />
* [https://etherpad.openstack.org/p/NYC-ops-meetup planning etherpad]<br />
<br />
====Newton release (Austin, May 2016)====<br />
* [https://etherpad.openstack.org/p/AUS-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (Feb, 2016)====<br />
* February 15 & 16, Manchester, UK<br />
* [https://etherpad.openstack.org/p/european-ops-meetup-planning original planning etherpad]<br />
* [https://etherpad.openstack.org/p/MAN-ops-meetup second planning etherpad]<br />
* [https://europeanopenstackoperatorsmeetup.eventbrite.com/ tickets on eventbrite]<br />
<br />
====Mitaka release (Tokyo, October 2015)====<br />
* [https://etherpad.openstack.org/p/TYO-ops-meetup planning etherpad]<br />
<br />
==== Mid-Cycle (August, 2015)====<br />
* August 18 & 19, Palo Alto<br />
* [http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924 Registration]<br />
* [https://etherpad.openstack.org/p/PAO-ops-meetup planning etherpad]<br />
<br />
===="L" release (Vancouver, May 2015)====<br />
* [https://etherpad.openstack.org/p/YVR-ops-meetup planning etherpad]<br />
* [[Design_Summit/Liberty/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-Cycle (Mar, 2015)====<br />
* March 9th and 10th, Philadelphia, USA<br />
* [https://etherpad.openstack.org/p/PHL-ops-meetup etherpads]<br />
<br />
==== Kilo (Paris, November 2014) ====<br />
<br />
* [http://kilodesignsummit.sched.org/overview/type/ops+summit schedule]<br />
* [[Summit/Kilo/Etherpads#Ops|Etherpads]]<br />
<br />
==== Mid-cycle (San Antonio, August 2014) ====<br />
<br />
* [http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/ schedule]<br />
* [https://etherpad.openstack.org/p/SAT-ops-meetup Etherpads]<br />
<br />
==== Juno (Atlanta, May 2014) ====<br />
<br />
* [http://junodesignsummit.sched.org/overview/type/ops+meetup schedule]<br />
* [[Summit/Juno/Etherpads#Ops|Etherpads]]<br />
<br />
<br />
==== Mid-Cycle (San Jose, March 2014) ====<br />
* [https://etherpad.openstack.org/p/operators-feedback-mar14 Etherpad]<br />
</div><br />
==Moderators Guide==<br />
Thank you very much for stepping up to be moderators at the ops meetup. Your work is key to our success!<br />
<br />
You are in control of your sessions, however, this document lay down some ideas about what we've seen in the past makes a good session, in case it helps.<br />
<br />
We have two different types of sessions. General Sessions and Working Groups. Below, I've separated them out so you can read what's relevant to you.<br />
<br />
We have three overall aims:<br />
# Gather feedback on the issues that come up in running or using OpenStack and work to communicate this throughout the community<br />
# Create a forum in which to share best practices and architectures between interested parties<br />
# Increase constructive, proactive involvement from those running or using clouds<br />
<br />
<br />
===General Sessions===<br />
<br />
Basically, it's you, an etherpad, and room full of a couple hundred people who have OpenStack experience. As the moderator, your efforts result in actionable things we can work on, and the satisfied audience.<br />
<br />
* Introduce yourself to the audio guy or gal. You'll be provided with a microphone and asked about laptop connection.<br />
* The best thing to do is convince one of your friends to control the laptop. Get them to control the display of the etherpad, and if it gets big, scroll up and down to ensure the most relevant parts are seen.<br />
* At the start of the session give a 30 second intro to the etherpad, and ask everyone to take notes using it. (Many attendees will not be used to etherpads)<br />
* Kick off the discussion on time, perhaps by starting with some open ended questions, or a show of hands to understand the audience<br />
* Aim to get it to that nirvana state, where the conversation continues without your help<br />
* Don't fall into "Question and Answer" mode - just because you're up the front of the room, some people might expect you to do this. Steer back toward discussion always.<br />
* There will be microphone hogs. Do not be afraid to cut them off. Using language like "Thank you, that is important, we have recorded that on the etherpad" will mean there'll be no hard feelings.<br />
* If you see a nice transition between different topics, take it!<br />
* Most importantly: try and aim for every discussion to have at least one action item - something we can work on. If we don't do this, people are going to stop coming to these things <br />
<br />
<br />
Overall, have fun! Also *be* fun! If you get bored, the audience will sense it - so if it happens start a new topic. Spontaneity is good! Asking people to do things (file a bug, start a mailing list post) is good!<br />
<br />
<br />
===Working Groups - "Small, working sessions"===<br />
These sessions are for a focus on specific topics, and they are long sessions (normally 80 minutes) so you can actually, legitimately get work done - not just talk.<br />
<br />
You'll have yourself, and a small group of people who are experienced with OpenStack and actually very interested in getting involved. It's your job as facilitator to try and convert each and every one of these people into a proactive member of your working group, ideally continuing their tenure well after the summit.<br />
<br />
Since these are mostly longer session, and about much more specific things, it requires a bit more planning. For some of the groups, you will have met before and have work and processes to continue. Try and seed your etherpads with this information prior to the session.<br />
<br />
Try and think of some concrete things that can be done during your time, but also be ready and open to the suggestions of the attendees. If there's a great idea that everyone believes in, go for it and get it done. File bugs. File blueprints. Submit patches. Write documents. Use the whiteboard. You have time for all of this <br />
<br />
<br />
Of course, all of this information is general. You are the rockstars here - do whatever you think is best . Tom will be on hand for much of the two days for assistance. (call +886 98833 1200 if anything goes horribly wrong)<br />
<br />
There are also a few sessions which are a bit different...<br />
<br />
===Architecture Show and Tell===<br />
This is a series of lightening talks - basically a 5-8 minute talk about something cool about your deployment.<br />
<br />
If you're moderating this, one of the main duties you have to perform (or delegate) is that of timekeeping - we normally cycle through many talks in each session.<br />
<br />
Best practice is to get any slides people are using into one laptop before the start of the session.<br />
<br />
===Pre-and Post Meetup===<br />
Fully realising you are a volunteer with limited time and that you might not get around to any of this, some of the things that are cool to do before or after the meetup are:<br />
* Post a thread on the ops ML asking for ideas for your session (and also advertising it)<br />
* Giving a tweet out with the schedule details<br />
* Filling in the etherpad with some conversation start topics (or, if you are a developer looking for feedback - questions you would like answered)<br />
* Posting on the Ops ML a summary of the session and linking to the etherpad for those who couldn't make it<br />
* Writing a new wiki page under the Operations page with a summary of best practices/new tools you discovered etc<br />
* Following up on action items that people volunteered to do during the meetup ;)<br />
* Organising a followup IRC meeting, if applicable<br />
<br />
==How Ops Meetups are planned==<br />
Ops Meetups are organised by the [[Ops Meetups Team]]. This team is an open team that meets regularly - if you are interested in this event, do get in touch!<br />
<br />
Here's a high-level timeline of the process:<br />
* Approximate date/region decided: 5 months before<br />
* Venue booked: 4 months before<br />
* Agenda Brainstorming Starts: 2 months before<br />
* Registration Opens: 2 months before<br />
* Draft Agenda Release: 1 Month before<br />
* Agenda Complete: 3 weeks before<br />
* All moderators found: 2 weeks before<br />
* Registration Closes: 1 week before (for catering)<br />
<br />
===Date and Region selection===<br />
The Ops Meetups gain much of their timing cues from the OpenStack release cycle. There is always an event at the OpenStack Summit, which is held in a regional rotation:<br />
* Year 1 - Late April/Early May - North America<br />
* Year 1 - Late October/Early November - Europe<br />
* Year 2 - Late April/Early May - North America<br />
* Year 2 - Late October/Early November - Asia Pacific<br />
<br />
There are also events between the summit. These have traditionally been held in February/March and August, however the cadence and regional location is currently being discussed by the [[Ops Meetups Team]].<br />
<br />
Based on community feedback, the [[Ops Meetups Team]] chooses the approximate dates and regions for events.<br />
<br />
===Venue Selection===<br />
Once an approximate date range (eg "mid-to-late August") and region (eg "North America") is known, work can begin on the venue. Finding a venue that's flexible, yet large enough to fit the growing ops community is always a challenge. Attendance has fluctuated over the years, but have generally ranged from 100 - 200. We have also had a varying number of parallel tracks depending on the facility:<br />
* Theater/fishbowl style seating for 100-200 <br />
** Note: the Philadelphia mid-cycle in March 2015 had 175+ registrations and approx. 150 people on-site<br />
** Note: Palo Alto mid-cycle in August 2015 had 303 registrations and approx 195 on site.<br />
** Note: Manchester mid-cycle in February 2016 had 130 on-site.<br />
* At least 2 rooms to run parallel breakout sessions or a themed track is desirable but not required.<br />
** Note: for the mid-cycle meetups, the group often meets all together in the morning, and at the end of the event for a feedback session. The rest of the schedule can be broken out into tracks. For example, in Philadelphia, the main room used in the morning was broken up into two spaces, which were used separately in the afternoon. In Tokyo, the large room was used for general sessions while a smaller room was used for an NFV themed track which was of particular interest to many local attendees.<br />
* A reliable wireless network, most likely for 500-600 devices<br />
* Projectors, screens, power strips and whiteboards for every room, several handheld microphones for large room(s)<br />
* Coffee and lunch breaks each day, possibly light breakfast depending on cost<br />
** Note: catering is typically where the largest costs are incurred, especially with increasing numbers. This is sometimes provided by the host, but has also been sponsored separately. <br />
* Convenient access to transport, hotels and other venues (eg for an evening event)<br />
* Signage directing people to the appropriate room<br />
* A registration/welcome table in an appropriate space<br />
** Note: for mid-cycle events hosted at an office building, security requirements can provide additional logistical hurdles<br />
<br />
<br />
<br />
We have been extremely fortunate to have had excellent organisations step up and offer their own space, or offer to underwrite a commercial meeting space. If you see someone from an organisation who has hosted one of these events before, please share your gratitude - it's a large part of what makes it possible. A very big thank you to our past hosts:<br />
* eBay/Paypal<br />
* Rackspace<br />
* Comcast<br />
* HP<br />
* Datacentred<br />
* Bloomberg<br />
* Enter<br />
* NTT<br />
<br />
In May 2016, the [[Ops Meetups Team]] decided the most fair way of finding a venue was to email out an open call for venues and see what came back. The key was to facilitate a fair process to choose between proposals, if we had more than one. This call for hosts should happen as soon as the region and approximate date range are decided, to allow the most possible time for planning.<br />
<br />
===Underwriters===<br />
The community strongly believes that Ops Meetups should be non-commercial events, and is willing to accept a cheaper "level of production" instead of being bombarded with marketing. However, running an event does still cost money!<br />
<br />
Underwriters are the financial backers of the event. They're organisations who believe in improving OpenStack ops, and usually run clouds themselves. Between them they cover any venue, catering and ancillary costs to run the event. In the past, we've added underwriter names and logos to the registration site, event signage and name badges. We've also allowed a modest number of banners to be placed in the main area, and encouraged a representative from each underwriter to welcome people to the event so their face and brand are known.<br />
<br />
In some cases, especially with an in-house venue and in-house catering, the host has also been the underwriter. However, according to OpenStack's event principles, we should facilitate equal participation from all commercial members of the community.<br />
<br />
===Topic Selection===<br />
Choosing the topics for the meetup is very important. You want to ensure that you have a reasonable balance between feedback gathering (especially covering current burning issues), best practice sharing, and sessions that get people actually participating.<br />
<br />
The general principle here is to get wide feedback - you don't want to have entirely the same topics every meetup, and you definitely don't want to always have the same people making the suggestions (lest it results in an Echo Chamber).<br />
<br />
To date, how this has worked has been an etherpad, such as https://etherpad.openstack.org/p/YVR-ops-meetup, seeded with information about the aims and session types of the ops meetup with the following sections for soliciting feedback:<br />
* Session Ideas - General Sessions<br />
* Session Ideas - Working Groups<br />
* Architecture Show & Tell (if you want to present, list your name and email below)<br />
* Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
<br />
Seeding a few known good sessions in each section to provide examples works well, and encouraging a few people to give +1s on their favourite session ease others who aren't as familiar with etherpad into this behaviour.<br />
<br />
Once the etherpad has run its course - normally for around a couple of weeks, the topics are decanted into a schedule across the rooms available, which is then shared with the community for feedback. Missing topics or topics with conflicts might be identified at this time (see also: Managing Conflicts).<br />
<br />
=== Scheduling===<br />
<br />
==== Room Selection, Layout & co-location ====<br />
<br />
So, the hardest rooms to get are the 'big' ones, for our full room<br />
discussion. <br />
<br />
For the 'big' rooms, there is an argument to maximise attendance<br />
somewhat, unlike the 'small' rooms where ideally we want only<br />
dedicated/interested people. Co-locating the larger rooms means that we<br />
basically have a lot more people we trap in our track for the entire<br />
time, by ensuring there's always something interesting for them going on.<br />
<br />
With good attendance numbers for the larger sessions, it ensures that<br />
the "feedback" aim of the events can be achieved in a broad manner,<br />
grabbing the widest views possible from the largest number of people.<br />
<br />
However, at 3 parallel rooms, it becomes quite difficult to schedule<br />
things so that people can generally get to everything they want to see<br />
So, these above argument breaks for large numbers of parallel rooms.<br />
I think 3 is about the limit for a single day. If we were ever to need 7<br />
more slots, then we should definitely split the large rooms over<br />
multiple days.<br />
<br />
<br />
Regarding the 'small' rooms - it's quite a bit different. We're not<br />
trying to maximise attendance overall, but it is a lot more important<br />
that people can get to the groups they want to - like the design summit<br />
overall. These are co-located just to avoid Thierry going insane He<br />
works so hard to get the schedule sorted out nicely for all the design<br />
summit projects. If there's a problem with other tracks in the design<br />
summit that want to switch some stuff to Wednesday, I'd be completely<br />
open to moving some of our stuff around this summit.<br />
<br />
There's also the days themselves to consider: Tuesday, Wednesday and<br />
Thursday are probably the 'better' days to have sessions - more than a<br />
few people arrive late and miss parts of Monday and leave early and miss<br />
parts of Friday.<br />
<br />
==== Managing Conflicts ====<br />
Conflicts in the layout grid is something to<br />
consider very heavily and get sanity checking from others on.<br />
<br />
Some times it just works out, for example, the Summit "101" being up against two very<br />
technical/advanced topics, since there are definitely different<br />
audiences there.<br />
<br />
There are also some topics where only certain classes of people<br />
care, and so you have to make sure that other more general topics are<br />
available so people stick around. eg if you're not running cinder,<br />
interested in multiple sites or federation, and they're the only things that are on ... what should you do for 40<br />
minutes?<br />
<br />
Then there are the topics that have shared interest. People interested<br />
in federations are also likely interested in multi-site clouds, so it<br />
isn't appropriate to co-schedule these. Similarly, people interested in<br />
billing are also probably interested in legacy applications.<br />
<br />
Use best judgement, and get wide feedback.<br />
<br />
=== Finding Moderators===<br />
Each session needs a moderator. Two methods for finding interested people have been tried in the past - call out on the ops mailing list separate to the agenda drafting/planning, and adding a section on the etherpad. The latter was markedly more successful, so be sure to add a section to the planning etherpad:<br />
<br />
Moderator volunteers (list your name and email below, along with the sessions you could lead)<br />
* Guide for Moderators: https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide<br />
* Tom Name <tom@example.org> - Introduction sessions, generally available if none else volunteers<br />
<br />
Then, once the planning etherpad has run its course, with a couple of mailing list prompts, and you've scheduled sessions, see how you go in matching up moderators with their area of interest. Moderators tend to write down the specific sessions they want to lead, so start there, then add the generalists, and so on.<br />
<br />
The final step is to fill the gaps - where there is no moderator assigned. Write some emails: Ask the existing moderator volunteers, ask the mailing list, and finally - if no moderator can be found, it probably means there is less interest than expected and the session should be replaced with something else.<br />
<br />
Hints:<br />
* Keep in mind that each session takes some time and effort to prepare, so typically don't ask one person to moderate more than two sessions.<br />
* First-time moderators might feel more comfortable working with a co-moderator, as would those tackling a difficult topic.<br />
* Since the work sessions take more prep, two or three moderators can be a good idea.<br />
<br />
=== Registration===<br />
We use the Foundation's Eventbrite page.<br />
<br />
Once registration is open, we monitor the numbers, adjust venue/food requirements accordingly and make sure things don't get out of control.<br />
<br />
Registration closes about a week before the event. Sometimes earlier if we're in a venue with special security requirements.<br />
<br />
===Advertising===<br />
Just ask Allison ;)<br />
<br />
Advertising this event is a balance. We want people who are experienced cloud operators to come - it's an event for them. However, if we broadcast loudly, in addition to our ops friends we'll get lots of attendees who are not that :) We attach a disclaimer to all of our email communication and registration pages in an attempt to avoid beginners accidentally attending and having a negative experience:<br />
<br />
***Note***: This event assumes OpenStack ops knowledge and is _not_ appropriate for beginners, or a place to learn about OpenStack. The event contains relatively few 'presentations' and is mostly a discussion-style event. To find other OpenStack events in your area, please visit www.openstack.org/events.<br />
<br />
That's obviously too long to put in a tweet, so normally start those with something like "Run an #OpenStack Cloud? ...."<br />
<br />
It's also very nice to have some prominent developers attend - so a direct tip-off to those folks is one option, or including a line in the weekly newsletter.<br />
<br />
Generally, the following promotion activities are performed:<br />
* Email previous Summit attendees that have indicated ops in their registration<br />
* Email previous attendees of the ops midcycles <br />
* Remind the Ops Mailing list<br />
* Tweet from the foundation twitter account<br />
* Contact the local meetup group<br />
<br />
Optionally, some other areas to try are:<br />
* Email a subset of the ActiveUser Contributors that would benefit from attending the ops midcycle<br />
* Reach out to user survey respondents who have indicated that they can be contacted<br />
<br />
===Working with Feedback===</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=164709Forum/Berlin20182018-09-12T20:09:43Z<p>Emccormickva: /* Etherpads from Teams and Working Groups */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
[[File:Forum_lead_up_brainstorming.png]]<br />
<br />
Your ideas are welcome! Either:<br />
* Add a link to an etherpad for all of your team's ideas on this wiki page<br />
* Contribute to the "catch-all" etherpads, linked below.<br />
<br />
and then discuss with everyone to refine and shortlist the best topics.<br />
<br />
Within two weeks, we will call for formal submission of your best ideas.<br />
<br />
==List of Etherpads==<br />
<big>Forum brainstorming for Berlin commences August 29th. Please add your etherpad of ideas below!</big><br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/cinder-forum-stein Cinder]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm Manila]<br />
* [https://etherpad.openstack.org/p/nova-forum-stein Nova]<br />
* [https://etherpad.openstack.org/p/OpenStackHelmBerlinForumBrainstorming OpenStack-Helm]<br />
* [https://etherpad.openstack.org/p/ops-forum-stein Operators]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/tripleo-forum-stein TripleO]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=164708Forum/Berlin20182018-09-12T20:07:37Z<p>Emccormickva: /* Etherpads from Teams and Working Groups */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
[[File:Forum_lead_up_brainstorming.png]]<br />
<br />
Your ideas are welcome! Either:<br />
* Add a link to an etherpad for all of your team's ideas on this wiki page<br />
* Contribute to the "catch-all" etherpads, linked below.<br />
<br />
and then discuss with everyone to refine and shortlist the best topics.<br />
<br />
Within two weeks, we will call for formal submission of your best ideas.<br />
<br />
==List of Etherpads==<br />
<big>Forum brainstorming for Berlin commences August 29th. Please add your etherpad of ideas below!</big><br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/cinder-forum-stein Cinder]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm Manila]<br />
* [https://etherpad.openstack.org/p/nova-forum-stein Nova]<br />
* [https://etherpad.openstack.org/p/OpenStackHelmBerlinForumBrainstorming OpenStack-Helm]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/tripleo-forum-stein TripleO]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/ops-forum-stein Operators]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Vancouver2018&diff=161370Forum/Vancouver20182018-05-19T00:32:17Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Vancouver 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''Stein''' development cycle. Please prepare session ideas with feedback from the '''Queens''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/vancouver-2018/summit-schedule/global-search?t=Forum Full Forum Schedule]<br />
<br />
===Monday, May 21===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/YVR-forum-101<br />
* [1135-1215] OpenStack-Chef - Project Onboarding<br />
* [1135-1215] Default Roles<br />
* [1330-1410] Docs/i18n - Project Onboarding https://etherpad.openstack.org/p/docs-i18n-project-onboarding-vancouver<br />
* [1330-1410] Standalone Cinder Introduction<br />
* [1330-1410] Continuing the Migration: Launchpad -> Storyboard https://etherpad.openstack.org/p/continuing-the-migration-lp-sb<br />
* [1330-1410] Users/Operators adoption of QA tools/plugins https://etherpad.openstack.org/p/YVR18-forum-qa-ops-user-feedback<br />
* [1440-1500] Tacker - Project Onboarding<br />
* [1440-1500] A New Face and Place for the OpenStack Mentoring Program https://etherpad.openstack.org/p/New-Face-Place-OpenStack-Mentoring<br />
* [1440-1500] Requirements for Resource Reservation https://etherpad.openstack.org/p/YVR18-forum-reservation-requirements<br />
* [1440-1500] Python Testing Interface https://etherpad.openstack.org/p/YVR-python-pti<br />
* [1510-1550] Octavia - Project Onboarding<br />
* [1510-1550] First Contact SIG Operator Inclusion https://etherpad.openstack.org/p/FC-SIG-Ops-Inclusion<br />
* [1510-1550] Building the path to extracting Placement from Nova https://etherpad.openstack.org/p/YVR-placement-extraction<br />
* [1510-1550] Machine Learning for CI Results Analysis https://etherpad.openstack.org/p/YVR-ml-ci-results<br />
* [1620-1700] OpenStack Ansible - Project Onboarding https://etherpad.openstack.org/p/YVR-openstack-ansible for all OpenStack-Ansible activities, including forum.<br />
* [1620-1700] Planning to use Placement in Cinder https://etherpad.openstack.org/p/YVR-cinder-placement<br />
* [1620-1700] Ops/Devs: One community https://etherpad.openstack.org/p/YVR-ops-devs-one-community<br />
* [1620-1700] SDK Testing and Certification<br />
* [1710-1740] Ops Meetups Team: catch-up and PTG merger discussion<br />
* [1710-1740] Keystone - Project Onboarding<br />
* [1710-1740] Cyborg/FPGA Support for Cloud/NFV https://etherpad.openstack.org/p/Cyborg-FPGA-Support-for-Cloud-NFV <br />
* [1710-1740] Python 2 Deprecation Timeline https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline<br />
<br />
===Tuesday, May 22===<br />
* [0900-0940] <br />
* [0900-0940] <br />
* [0900-0940] <br />
* [0950-1030] Room 223 - QA - Project Onboarding - https://etherpad.openstack.org/p/YVR18-forum-qa-onboarding-vancouver <br />
* [0950-1030] <br />
* [0950-1030] <br />
* [1100-1140] Room 224 - Possible edge architectures for Keystone - https://etherpad.openstack.org/p/YVR-edge-keystone-brainstorming<br />
* [1100-1140] Room 220 -Users & Ops feedback for Monasca - https://etherpad.openstack.org/p/monasca-forum-vancouver-topics<br />
* [1100-1140] Room 221-222 - Cinder High Availability (HA) Discussion - https://etherpad.openstack.org/p/YVR18-cinder-ha-forum<br />
* [1150-1230] Room 220 - Ironic Ops and User Feedback - https://etherpad.openstack.org/p/yvr-forum-ironic-ops-and-user-feedback<br />
* [1150-1230] Room 221-222 - Multi-attach Introduction and Future Direction - https://etherpad.openstack.org/p/YVR18-cinder-mutiattach-forum<br />
* [1150-1230] <br />
* [1350-1430] Room 220 - Upgrading OpenStack - war stories - https://etherpad.openstack.org/p/YVR-upgrading-openstack-war-stories<br />
* [1350-1430] Room 221-222 - Preemptible instances - the way forward - https://etherpad.openstack.org/p/YVR18-pre-emptible-instances<br />
* [1350-1430] <br />
* [1440-1520] <br />
* [1530-1610] Room 220 - nova/neutron + ops cross-project session - https://etherpad.openstack.org/p/YVR18-novaneutron-ops-cross-project-session<br />
* [1530-1610] <br />
* [1530-1610] <br />
* [1640-1720] Rom 220 - CellsV2 migration process sync with operators - https://etherpad.openstack.org/p/YVR18-cellsv2-migration-sync-with-operators<br />
* [1640-1720] <br />
* [1640-1810] Room 221-222 - Fault Management/Monitoring for NFV/Edge/5G/IoT - https://etherpad.openstack.org/p/YVR-fm-monitoring<br />
* [1730-1810] <br />
* [1730-1810] <br />
* [1730-1810]<br />
<br />
===Wednesday, May 23===<br />
* [0900-0940] Room 220 - Fast-Forward Upgrades - Current State - https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades<br />
* [0900-0940] Room 220 - Fast-Forward Upgrades - Future Work - https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades<br />
* [0900-0940] <br />
* [0950-1030] Room 224 - Update on the gaps identified by ETSI NFV in OpenStack - https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [0950-1030] Room 221-222 - Cinder's Documentation Discussion - https://etherpad.openstack.org/p/YVR18-cinder-documentation-forum<br />
* [0950-1030] <br />
* [1100-1140] <br />
* [1100-1140] <br />
* [1100-1140] Room 221-222 - Making NFV features easier to use - https://etherpad.openstack.org/p/YVR-nfv-ease-of-use<br />
* [1150-1230] Room 221-222 - DPDK/SR-IOV NFV Operational issues and way forward - https://etherpad.openstack.org/p/YVR-dpdk-sriov-way-forward<br />
* [1150-1230] <br />
* [1150-1230] <br />
* [1350-1430] <br />
* [1350-1430] <br />
* [1350-1430] <br />
* [1440-1520] Room 220 - Rolling maintenance and upgrade in interaction with VNFM - https://etherpad.openstack.org/p/YVR-rolling-maintenance-with-VNFM<br />
* [1440-1520] Room 221-222 - Missing features in OpenStack for public clouds - https://etherpad.openstack.org/p/YVR-forum-missing-features-pc<br />
* [1530-1610] Room 221-222 - OpenStack Passport Program - feedback and next step - https://etherpad.openstack.org/p/YVR-forum-passport-program<br />
* [1530-1610] Room 220 - TripleO Ops and User feedback https://etherpad.openstack.org/p/tripleo-rocky-ops-and-user-feedback<br />
* [1530-1610] <br />
* [1640-1720] Drafting Requirements for Organisations Contributing to Open https://etherpad.openstack.org/p/Reqs-for-Organisations-Contributing-to-OpenStack<br />
* [1640-1720] API Debt Cleanup https://etherpad.openstack.org/p/rest-api-error-consistency<br />
* [1640-1720] <br />
* [1730-1810] Room 221-222 - TripleO and Ansible integration https://etherpad.openstack.org/p/tripleo-rocky-ansible-integration<br />
* [1730-1810] <br />
* [1730-1810]<br />
<br />
===Thursday, May 24===<br />
* [0900-0940] Extended Maintenance part I: past, present and future https://etherpad.openstack.org/p/YVR-extended-maintenance<br />
* [0900-0940] <br />
* [0900-0940] <br />
* [0950-1030] Extended Maintenance part II: EM and release cycles https://etherpad.openstack.org/p/YVR-extended-maintenance<br />
* [0950-1030] Room 221-222 [neutron] extend-logging-api https://etherpad.openstack.org/p/extend-logging-api<br />
* [0950-1030] Room 223 [manila] project onboarding https://etherpad.openstack.org/p/YVR18-manila-project-onboarding<br />
* [1100-1140] Rm 220 OpenStack is "mature" -- time to get serious on Maintainers https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3<br />
* [1100-1140] Room 221-222 [neutron-fwaas] firewall l7 filtering https://etherpad.openstack.org/p/fwaas-v2-L7-filtering<br />
* [1100-1140] <br />
* [1150-1230] S Release Goals https://etherpad.openstack.org/p/YVR-S-release-goals<br />
* [1150-1230] <br />
* [1150-1230] <br />
* [1350-1430] Official projects and the boundary of "what is OpenStack" https://etherpad.openstack.org/p/YVR-forum-TC-project-boundaries<br />
* [1350-1430] Room 221-222 [manila] Operators' feedback: running at scale, overcoming obstacles to deployment https://etherpad.openstack.org/p/YVR18-manila-forum-ops-feedback<br />
* [1350-1430] <br />
* [1440-1520] TC Retrospective https://etherpad.openstack.org/p/YVR-tc-retrospective<br />
* [1530-1610] Cross-community governance between OSF projects https://etherpad.openstack.org/p/YVR-cross-osf-tech-governance<br />
* [1530-1610] <br />
* [1540-1610] Advanced RCA use cases - taking Vitrage to the next level https://etherpad.openstack.org/p/YVR-vitrage-advanced-use-cases<br />
* [1640-1720] Vitrage RCA over K8s. Pets and Cattle - Monitor each cow? https://etherpad.openstack.org/p/YVR-vitrage-rca-over-k8s<br />
* [1640-1720] <br />
* [1640-1720] <br />
* [1730-1810] <br />
* [1730-1810] <br />
* [1730-1810]<br />
<br />
==List of Brainstorming Etherpads (Historical)==<br />
Topic selection is now complete, but see below for session idea brainstorming that was done prior to selection.<br />
<br />
'''These are just kept for historical reference. Please do not use for any additional ideas.'''<br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/YVR-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/YVR-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams, Working Groups, and SIGs====<br />
<br />
* [https://etherpad.openstack.org/p/YVR-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/YVR-cinder-brainstorming Cinder]<br />
* [https://etherpad.openstack.org/p/YVR-glance-brainstorming Glance]<br />
* [https://etherpad.openstack.org/p/YVR-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/YVR-manila-brainstorming Manila]<br />
* [https://etherpad.openstack.org/p/YVR-kolla-brainstorming Kolla]<br />
* [https://etherpad.openstack.org/p/YVR-self-healing-brainstorming Self-healing SIG]<br />
* [https://etherpad.openstack.org/p/FEMDC_Vancouver_brainstorming Fog Edge Massively Distributed Clouds SIG]<br />
* [https://etherpad.openstack.org/p/YVR-openstack-ansible-brainstorming OpenStack-Ansible]<br />
* [https://etherpad.openstack.org/p/YVR-upgrade-brainstorming Upgrade SIG]<br />
* [https://etherpad.openstack.org/p/YVR-publiccloud-wg-brainstorming Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/YVR18-scientific-sig-brainstorming Scientific SIG]<br />
* [https://etherpad.openstack.org/p/YVR-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/FC_SIG_Rocky_Forum First Contact SIG]<br />
* [https://etherpad.openstack.org/p/YVR-k8s-brainstorming SIG K8s]<br />
* [https://etherpad.openstack.org/p/YVR-stable-brainstorming Stable/Extended Maintenance]<br />
* [https://etherpad.openstack.org/p/YVR-vitrage-brainstorming Vitrage]<br />
* [https://etherpad.openstack.org/p/YVR-neutron-brainstorming Neutron]</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157723Forum/Sydney20172017-11-06T06:12:07Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1135-1215] Missing Features and Making Improvements to OpenStack Health https://etherpad.openstack.org/p/SYD-forum-openstack-health-feedback<br />
* [1135-1215] Improving Gopher Cloud and OpenStack K8s Provider https://etherpad.openstack.org/p/SYD-improving-gopher-cloud<br />
* [1330-1410] Kolla Ops feedback session http://etherpad.openstack.org/p/kolla-sydney-ops-feedback<br />
* [1330-1410] Glance Project Onboarding https://etherpad.openstack.org/p/SYD-forum-glance-onboarding<br />
* [1330-1410] Ops Guide Transition and Maintenance https://etherpad.openstack.org/p/SYD-forum-ops-guide-transition<br />
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding] <br />
https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding<br />
* [1420-1500] Interop Working Group Community Feedback and Work Session https://etherpad.openstack.org/p/SYD-interop-working-group<br />
* [1420-1500] Installation Guides and Tutorials Updates and Testing https://etherpad.openstack.org/p/SYD-install-guide-testing<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] <br />
https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
*[1510-1550] Fog/Edge/Massively Distributed Clouds (FEMDC) SIG- https://etherpad.openstack.org/p/FEMDC-F2F-meeting-sydney-summit<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1620-1700] Privsep: what is it and operational impacts https://etherpad.openstack.org/p/SYD-forum-privsep<br />
* [1620-1700] User Survey Feedback https://etherpad.openstack.org/p/UserSurveyFeedback<br />
* [1710-1750] What Do Operators Want from Stable Policy https://etherpad.openstack.org/p/SYD-stable-policy<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Self-healing and optimization SIG https://etherpad.openstack.org/p/self-healing-rocky-forum<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0900-0940] Interop Test Library for OpenStack SDKs https://etherpad.openstack.org/p/SYD-forum-sdk-interop-test-library<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [0950-1030] Zuul v3 Feedback Session https://etherpad.openstack.org/p/SYD-zuul-v3-feedback<br />
* [0950-1030] Charms User Feedback session https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback<br />
* [1050-1130] The State of Test Runners and Moving to stestr https://etherpad.openstack.org/p/SYD-forum-test-runners<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1140-1220] openstack-sig-k8s and k8s-sig-openstack collaborations https://etherpad.openstack.org/p/SYD-openstack-sig-k8s-collaborations<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1610-1650] Glance: Operators Feedback Session https://etherpad.openstack.org/p/SYD-forum-glance-feedback<br />
* [1610-1650] OpenStackClient and Nova API microversions https://etherpad.openstack.org/p/SYD-forum-nova-osc<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [0950-1030] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20473/openstack-public-cloud-passport-program OpenStack Public Cloud Passport Program] https://etherpad.openstack.org/p/SYD-forum-public-cloud<br />
* [1100-1140] Bare metal as a service: Ironic vs. Mogan vs. Nova https://etherpad.openstack.org/p/SYD-forum-baremetal-ironic-mogan-nova<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1150-1230] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19798/features-missing-in-openstack-core-for-public-cloud-providers Features missing in OpenStack core for Public Cloud Providers] https://etherpad.openstack.org/p/SYD-forum-missing-features-pc<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1530-1610] Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop https://etherpad.openstack.org/p/SYD-refstack-nfv<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1630-1710] Heat ops and users feedback https://etherpad.openstack.org/p/Sydney-heat-ops-and-users-feedback<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157714Forum/Sydney20172017-11-05T22:15:37Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1135-1215] Missing Features and Making Improvements to OpenStack Health https://etherpad.openstack.org/p/SYD-forum-openstack-health-feedback<br />
* [1135-1215] Improving Gopher Cloud and OpenStack K8s Provider https://etherpad.openstack.org/p/SYD-improving-gopher-cloud<br />
* [1330-1410] Glance Project Onboarding https://etherpad.openstack.org/p/SYD-forum-glance-onboarding<br />
* [1330-1410] Ops Guide Transition and Maintenance https://etherpad.openstack.org/p/SYD-forum-ops-guide-transition<br />
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding] <br />
https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding<br />
* [1420-1500] Interop Working Group Community Feedback and Work Session https://etherpad.openstack.org/p/SYD-interop-working-group<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] <br />
https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
*[1510-1550] Fog/Edge/Massively Distributed Clouds (FEMDC) SIG- https://etherpad.openstack.org/p/FEMDC-F2F-meeting-sydney-summit<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1620-1700] Privsep: what is it and operational impacts https://etherpad.openstack.org/p/SYD-forum-privsep<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Self-healing and optimization SIG https://etherpad.openstack.org/p/self-healing-rocky-forum<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0900-0940] Interop Test Library for OpenStack SDKs https://etherpad.openstack.org/p/SYD-forum-sdk-interop-test-library<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [0950-1030] Zuul v3 Feedback Session https://etherpad.openstack.org/p/SYD-zuul-v3-feedback<br />
* [1050-1130] The State of Test Runners and Moving to stestr https://etherpad.openstack.org/p/SYD-forum-test-runners<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1140-1220] openstack-sig-k8s and k8s-sig-openstack collaborations https://etherpad.openstack.org/p/SYD-openstack-sig-k8s-collaborations<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1610-1650] Glance: Operators Feedback Session https://etherpad.openstack.org/p/SYD-forum-glance-feedback<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [0950-1030] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20473/openstack-public-cloud-passport-program OpenStack Public Cloud Passport Program] https://etherpad.openstack.org/p/SYD-forum-public-cloud<br />
* [1100-1140] Bare metal as a service: Ironic vs. Mogan vs. Nova https://etherpad.openstack.org/p/SYD-forum-baremetal-ironic-mogan-nova<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1150-1230] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19798/features-missing-in-openstack-core-for-public-cloud-providers Features missing in OpenStack core for Public Cloud Providers] https://etherpad.openstack.org/p/SYD-forum-missing-features-pc<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157627Forum/Sydney20172017-10-31T19:13:33Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157626Forum/Sydney20172017-10-31T19:12:40Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Emccormickvahttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157613Forum/Sydney20172017-10-31T15:44:17Z<p>Emccormickva: </p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Emccormickva