15:00:09 #startmeeting Ceilometer 15:00:09 #meetingtopic Ceilometer 15:00:09 #chair nijaba 15:00:09 #link http://wiki.openstack.org/Meetings/MeteringAgenda 15:00:09 Meeting started Thu Sep 20 15:00:09 2012 UTC. The chair is nijaba. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:11 The meeting name has been set to 'ceilometer' 15:00:14 Current chairs: nijaba 15:00:14 hi 15:00:18 Hello everyone! Show of hands, who is around for the ceilometer meeting? 15:00:18 o/ 15:00:26 o/ 15:00:43 only us 2? 15:00:52 looks like a party to me 15:01:05 we should have done the meeting f2f last night ;) 15:01:13 yeah :) 15:01:21 #topic actions from previous meeting 15:01:35 #topic dhellmann write up details of blueprint https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring 15:01:42 i think Doug will show up 15:01:43 o/ 15:01:46 I am there.. 15:01:52 hey spn! 15:01:52 hi spn 15:02:03 sorry I was pinging on other channel 15:02:19 jd__: spn 15:02:31 jd__: says hi 15:02:51 so I am not sure dhellman was able to work on this item last week 15:02:58 meeting at this time is awesome 15:03:13 o/ 15:03:21 nijaba: Hi Nick 15:04:05 o/ 15:04:13 Half here; also OTP. 15:04:14 hello gmb :) 15:04:26 Hi Nick, fancy seeing you here :) 15:04:59 so, dhellmann is not around and the last mod to the wikie page is 2012-08-27 20:58:25 15:05:17 so I guess we'll have to forward this item to next week 15:05:27 ack 15:05:33 #action dhellmann write up details of blueprint https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring 15:05:51 and thats all the topics we had for this week 15:06:04 #topic open discussion 15:06:21 anything, anyone? 15:06:24 yes 15:06:50 I submitted a micro sized patch last week to add Flask to files/pips 15:07:11 doug thinks it is not required since he defined it in ceilometer/pip-requires.. 15:07:23 I dont see it working that way.. 15:07:37 could you elaborate? 15:07:46 ok.. 15:07:50 patch url maybe? 15:07:55 ceilometer-api requires Flask 0.9 15:08:24 I submitted a patch to enable ceilometer-api through devstack 15:08:44 but it does not run.. since Flask 0.9 which is a dependecy does not get installed 15:08:57 throug pip-requires defined in ceilometer branch.. 15:09:22 but if I add it in devstack/files/pips/ceilometer-api , it forces itself to be installed and ceilometer-api works 15:10:08 https://review.openstack.org/13188 15:10:12 I didn't encountered this when installing devstack 15:10:31 There is a mail from doug.. saying.. 15:10:36 "Patch Set 1: 15:10:36 Flask is listed as a dependency, with a version number, in the tools/pip-requires file in the ceilometer source code. Doesn't that cause Flask to be installed when devstack runs "sudo python setup.py develop" for ceilometer? 15:10:36 " 15:11:01 * dhellmann sorry I'm late 15:11:08 jd__: I tried multiple times.. and I dont see Flask getting installed.. 15:11:17 dhellmann: hello 15:11:44 spn: you're right, I didn't tried ceilometer-api, it's not installed 15:11:59 spn: I can't say if your patch is the good solution, but there's a problem indeed 15:12:13 hi dhellmann 15:12:26 Hey doug! 15:12:31 the new devstack version will get the ceilometer-api also .. but it will not run 15:12:36 I don't understand why flask is a problem but the other depdencies work correctly 15:12:45 is flask the only piece missing 15:12:52 dhellmann: dunno either but I confirm it's a problem :) 15:12:57 as far as I know it is.. 15:13:21 I am kind of jittery to create a pips folder just for our Flask in devstack 15:13:59 dhellmann: I think pip-requires is not used at all by setup.py actually, only by tox; I miss stevedore too 15:14:34 ah, jd__ might be right 15:14:45 I thought there was some magic going on to load the pip-requires file into setup.py 15:15:03 but install_requires isn't being set at all 15:15:08 me too, I like to think about magic when talking about setuptools 15:15:34 yes we miss that probably 15:15:34 spn: check the use of openstack.common.setup in the nova setup.py file 15:15:38 that's what we need to do 15:15:45 ok.. 15:16:06 def parse_requirements(requirements_files=['requirements.txt', 15:16:07 'tools/pip-requires']): 15:16:07 15:16:09 exactly :-) 15:16:11 yep, that's it 15:16:23 so the correct fix is to do that in our setup.py file, not to change devstack 15:16:31 ok.. 15:16:34 exactly 15:16:35 I will look into it.. 15:16:51 spn: if you prefer I can come up with a change myself 15:16:55 I will ping you (dhellmann) and jd__ if I have questions.. 15:17:02 jd__: I will do it.. 15:17:09 spn: ok great! 15:17:16 jd__: please bear with me. .I am bit new here.. :) 15:17:28 spn: no problem :) 15:17:34 jd_: thanks.. 15:17:47 thanks, spn 15:18:26 One more q? Is someone already looking into the glance metering part? 15:18:55 I think jd__ submitted a patch for that earlier today 15:19:15 yes, the pollster is on a good way 15:19:24 \o/ 15:19:30 jd__: cool.. 15:19:34 I've started to work on notifier, but stoped for now because somebody is already working on it 15:19:44 eglynn_ actually 15:19:46 notifier? 15:19:47 elgyn 15:19:54 yup 15:19:55 yep, working on it 15:20:01 nijaba: glance notification listener 15:20:06 k, thanks 15:20:11 should have something by tmrw 15:20:17 eglynn_: great 15:20:19 2x\o/ 15:20:22 nijaba: my action item from last week was to write up details about a blueprint. the results are at http://wiki.openstack.org/EfficientMetering/ConfigDrivenNotificationMonitoring 15:20:39 eglynn_: I've sent a patch to Glance to clean the notification, because it would send error on the info bus :) 15:20:58 jd__: cool, looking ... 15:21:01 dhellmann: so this is complete from your perspective, I was not sure 15:21:08 ? 15:21:12 eglynn_: https://review.openstack.org/#/c/13190/ FYI 15:21:24 nijaba: I believe so, but if someone else ends up trying to implement it they may think otherwise ;-) 15:21:47 ok, thanks 15:22:01 I remove the earlier added action for next week then 15:22:15 I *will* remove... 15:22:33 ok, thanks 15:23:03 should there be an action on me for pip-requires issue.. ? 15:23:04 #agreed dhellmann action for this week was completed. 15:23:24 spn: feel free to add one for yourself 15:23:36 use: #action spn ... 15:24:02 or better, open a bug report and assign it to yourself: ) 15:24:23 #action spn fix Flask pickup when setup.py is used 15:24:28 it depends if you want us to talk about it next week or not... 15:24:42 jd__: okies.. I will do that tooo 15:24:59 nijaba: surely we want to fix that problem.. 15:25:00 jd__: #action spn to open a bug about ... and assign it to himself ;) 15:25:43 nijaba: I will do it.. 15:26:11 :)) 15:26:25 spn: was more a joke than a real action for you ;) 15:26:31 I want to make a quick disclosure, if jd__ hasn't already said something, that DreamHost has contracted with jd__ to work on some ceilometer features we consider high priority for our launch. 15:26:32 but thanks 15:26:54 we will be doing all of the work through the normal code review and bug reporting processes (in the open) 15:26:57 dhellmann: that's excellent news I think! Congrats jd__! 15:27:13 well done dreamhost 15:27:15 superb.. what are those features btw 15:27:16 a couple of the changes he has submitted recently were on our list, and I think others' lists, too 15:27:34 thanks! :) 15:27:46 glad to work with dhellmann on that 15:27:51 nova notification on delete, integration with glance and cinder so far 15:27:57 we're still working on our full list of priorities 15:28:20 I have to say it's going really well so far, so I'm glad we were able to get some of his time! 15:28:42 dhellmann: is this list of priorities open? 15:29:01 spn: It's not really a secret, I guess, but the list isn't in a public place right now 15:29:21 FWIW I've started to work on cinder notification/pollster 15:29:45 I am sure we'll be able to deduce it from the list of patch jd__does in the next few weeks :) 15:29:55 hehe :-> 15:29:57 haha.. 15:30:40 spn: we also have on our list removing the direct db access where possible and adding authentication to the api 15:31:08 spn: and don't expect anything related to object storage... 15:31:53 Are you referring to the collector/manager.py where we have a FIXME flag? 15:32:02 anything else to cover? 15:32:52 nijaba: is there any reason not to expect object storage.. sorry I am not aware of history 15:33:15 spn: from dreamhost? they are rolling their own using ceph and not swif 15:33:16 spn: nijaba likes to rib me about our use of ceph for object storage instead of swift 15:33:18 spn: from dreamhost? they are rolling their own using ceph and not swift 15:33:30 when will there be some integration for horizon ? 15:33:41 nijaba: ;) got it.. 15:33:48 dhellmann: you don't want pollster for ceph into ceilometer? 15:33:54 dhellmann: not sure it is ribbing, more a distintive feature from my pov 15:34:15 I though ceph was backed by Canonical anyway, nijaba? :p 15:34:17 jd__: the folks who did the DreamObjects project set up their own metering solution as a one-off, so it is handled for now. we may change that later. 15:34:25 dhellmann: ok! 15:34:29 nijaba: all good natured, in any case! :-) 15:34:30 jd__: so far, as a backend for cinder :) 15:35:07 heh 15:35:16 :):) 15:35:27 but RADOS_GW just made it in main for 12.10... 15:35:54 great.. 15:36:33 ok, we are getting slighly off topic. anything else on topic? 15:36:42 last q 15:37:01 some one is already working on the chef thing for ceilometer? 15:37:14 anyone got a answer for my question ? 15:37:14 spn: jaypipes should be 15:37:40 zykes-: what integration would you expect? 15:37:42 zykes-: what sort of integration? showing details? 15:37:56 zykes-: I was thinking about a plugin to show some basic info 15:38:14 zykes-: but you may have something else in mind? 15:38:15 dhellmann: I had this question sometime back about showing stuff in horizon 15:38:35 spn: zykes-: it's on the roadmap 15:38:39 there will probably be a point where the API will have to be opened for users to access their data 15:38:41 horizon integration isn't on our list of priorities for DreamHost, but I definitely agree we need it for ceilometer at some point 15:38:45 that could lead to horizon integration I imagine 15:38:51 the API is not fully baked yet, so it may be premature 15:39:14 however, I would be interested in seeing some blueprints and other design documents describing desired views, so we could start thinking about requirements and implementation 15:39:22 so it is like the billing front end or just showing some ceilometer data? 15:39:41 spn: I think we should limit ourselves to showing ceilometer data 15:39:49 spn: I don;t thing we'll ever have a full billng front end... 15:40:01 dhellmann: agreed :) 15:40:19 nijaba: it is more of template/policy driven thing specific to organizations 15:40:27 although it might make sense to think about a way to let a plugin add rate info 15:40:46 ok. 15:41:03 dhellmann: it all depends on the billing model 15:41:22 some time backk. I tried this.. added a billing tab and defined a template policy which can be edited by admin tenet 15:41:42 nijaba: agreed. The DreamHost rate plans are a little complex to calculate 15:41:51 ok.. 15:42:10 spn: It would be nice to have stuff like this as examples, but could never be made universal, I think 15:42:55 nijaba: exactly 15:43:00 had a kind of very generic template.. but there is a limit to making it generic 15:43:24 dhellmann: that's nice if it's complicated, at least it will force us to make a good API :) 15:43:26 spn: contrib/examples are welcome. feel free to submit 15:43:39 nijaba: ok.. 15:43:46 jd__: when we're all done with the project, I'll see if I can write it up 15:43:56 sounds great 15:44:07 * nijaba crosses dhellmann's fingers ;) 15:44:24 :-) 15:44:47 anything else? 15:45:13 going once... 15:45:27 going twice... 15:45:40 sold! 15:45:43 ok.... we are done for tdoay! Thanks a lot everyone! 15:45:45 thanks for answering my questions 15:45:49 thanks! 15:45:49 thanks guys 15:45:53 #endmeeting