There is a proposal in https://etherpad.openstack.org/p/YVR-ops-meetup to discuss ceilometer.
I think it is important to understand what Gnocchi does and what it will not do in case people feel it will solve all of the problems. Tim > -----Original Message----- > From: Jason Myers (jasomyer) [mailto:[email protected]] > Sent: 30 March 2015 23:31 > To: Barrett, Carol L > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Ops @ Vancouver Summit - agenda > brainstorming > > Can we get a sit down with the ceilometer folks to share experiences? I think > they'd be up for that. > > Sent from my iPhone > > > On Mar 30, 2015, at 4:29 PM, Barrett, Carol L <[email protected]> > wrote: > > > > Tom - In support of helping to create impact from the feedback, I suggest we > partner someone from the Product Work Group with each of the Moderators. > The role of the PWG partner would be to identify/summarize the top 1-2 use > cases, recruit a couple of operators to help flesh it out and then bring into > the > roadmap discussion. > > > > Thoughts? > > Carol > > > > -----Original Message----- > > From: Tom Fifield [mailto:[email protected]] > > Sent: Monday, March 23, 2015 10:04 PM > > To: OpenStack Operators > > Subject: [Openstack-operators] Ops @ Vancouver Summit - agenda > > brainstorming > > > > 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.h > > tml [4] https://bugs.launchpad.net/openstack-manuals/+bug/1311067 > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator > > s > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator > > s > > _______________________________________________ > 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
