Many thanks to those who have contributed so far, especially the moderator volunteers! This is the final ping - get to the etherpad now if you would like input on the Ops @ Vancouver Summit things.
So far we have only 3 architecture show and tell sessions, from our regular contributors. The Architecture show and tell sessions were very popular according to summit feedback in Paris - it would be a shame if we reduced the amount of time for it due to lack of participation :) All you have to do is speak for 5-8 minutes about your architecture, tell us a story about when something exploded or share anything generally cool you think other ops would enjoy :) >> https://etherpad.openstack.org/p/YVR-ops-meetup Regards, Tom On 30/03/15 20:22, Tom Fifield wrote: > Hi all, > > Giving this another stoke. > > So far we have zero volunteers for the architecture show and tell > lightening talks, and very few moderator volunteers :) > > If you have ideas about what should be on the agenda for ops summit > sessions at Vancouver, > >> >> ********************************************************************** >> >> Please propose session ideas on: >> >> https://etherpad.openstack.org/p/YVR-ops-meetup >> >> ensuring you read the new instructions to make sessions 'actionable'. >> >> >> ********************************************************************** > > We basically need to get this done in a week or so, giving us enough > time to promote the agenda before the summit. > > > Regards, > > > Tom > > On 24/03/15 13:03, Tom Fifield wrote: >> Hi all, >> >> As you've no doubt guessed - the Ops Summit will return in Vancouver, >> and we need your help to work out what should be on the agenda. >> >> If you're new: note that this is in addition to the operations (and >> other) conference track's presentations. It's aimed at giving us a >> design-summit-style place to congregate, swap best practices, ideas and >> give feedback. >> >> >> We've listened to feedback from the past events, especially Paris, and >> I'm delighted to report that from Vancouver on we're a fully integrated >> part of the actual design summit. No more random other hotels far away >> from things and dodgy signage put together at the last minute - it's >> time to go Pro :) >> >> >> One biggest pieces of feedback we have regarding the organisation of >> these events so far is that you want to see direct action happen as a >> result of our discussions. We've had some success with this mid-cycle, >> for example: >> >> * Rabbit - heartbeat patch merged [1], now listed as top 5 issue for ops >> * OVS - recommendation for vswitch at least 2.1.2 [2] >> * Nova Feedback - large range of action items [3] >> * Security - raised priority on policy.json docs [4] >> >> ... just a few amoungst dozens. >> >> However, we can continue to improve, so please - when you are suggesting >> sessions in the below etherpad please make sure you phrase them in a way >> that will result in _actions_ and _results_. >> >> >> >> ********************************************************************** >> >> Please propose session ideas on: >> >> https://etherpad.openstack.org/p/YVR-ops-meetup >> >> ensuring you read the new instructions to make sessions 'actionable'. >> >> >> ********************************************************************** >> >> >> >> The room allocation is still being worked out (all hail Thierry!), but >> the current thinking is that the general sessions will all be on one day >> (likely Tuesday), and the working groups will be distributed throughout >> the week. >> >> >> More as it comes, and as always, further information about ops meetups >> and notes from the past can be found on the wiki @: >> >> https://wiki.openstack.org/wiki/Operations/Meetups >> >> >> Regards, >> >> >> Tom >> >> >> >> >> [1] https://review.openstack.org/#/c/146047/ >> [2] https://etherpad.openstack.org/p/PHL-ops-OVS >> [3] >> http://lists.openstack.org/pipermail/openstack-dev/2015-March/058801.html >> [4] https://bugs.launchpad.net/openstack-manuals/+bug/1311067 >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
