we should get a thank you cake to put in the dev summit area with a ref to the review number on it =P
On Tue, Mar 24, 2015 at 2:25 PM, David Medberry <openst...@medberry.net> wrote: > and also that Mehdi's oslo.messaging heartbeat fix for rabbitmq has merged > and there is intent to get that client version into Kilo. (And stable > maintainers will need to work it into Juno and Icehouse.) Upstream have > been responsive to this noice, our voice carries operators! > > On Tue, Mar 24, 2015 at 8:05 AM, Assaf Muller <amul...@redhat.com> wrote: > >> >> >> ----- Original Message ----- >> > 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 >> >> I updated that Etherpad, please note that since the meetup: >> >> Daemon rootwrap mode has merged for Kilo: >> >> http://specs.openstack.org/openstack/neutron-specs/specs/kilo/rootwrap-daemon-mode.html >> >> And the loop bug was fixed: >> https://bugs.launchpad.net/neutron/+bug/1421232 >> >> > [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 >> > OpenStack-operators@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
