14:59:44 #startmeeting ceilometer 14:59:45 Meeting started Thu Dec 4 14:59:44 2014 UTC and is due to finish in 60 minutes. The chair is eglynn. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:59:49 The meeting name has been set to 'ceilometer' 14:59:52 hey y'all! 14:59:56 hey 14:59:59 hello! 15:00:18 #topic Kilo-1 blueprints 15:00:20 o/ 15:00:26 <_nadya_> o/ 15:00:27 <_elena_> o/ 15:00:32 #link https://launchpad.net/ceilometer/+milestone/kilo-1 15:00:33 o/ 15:00:45 not looking too bad at this stage 15:00:51 o/ 15:01:11 o/ 15:01:12 it would be great to get the two blocked BPs unblocked by EoW 15:01:20 expecially ready-ceilometer-rbac-keystone-v3 15:01:37 eglynn: I'll do my best ... caught in a lot of "internal" things ... 15:01:54 fabiog: coolness, thank you sir! 15:02:08 o/ 15:02:28 o/ 15:02:33 o/ 15:02:54 eglynn: can we merge the spec for RBAC? I noticed it did not go in yet ... 15:03:06 fabiog: when I was reviewing https://review.openstack.org/115717 I tried to figure out if other any services were "domain-aware" as yet 15:03:17 fabiog: seemed only heat was using the concept in anger 15:03:25 fabiog: is that correct, do you know? 15:03:37 o/ 15:03:40 eglynn: I think V3 support is not really there for services yet 15:03:56 o/ 15:04:00 eglynn: I will ask Morgan about V2 deprecation timeframe. 15:04:04 fabiog: (and yes, I think we can probably merge the spec with the understanding that it'll be a phased thing, and the domain support will come later) 15:04:11 fabiog: yeah, that's a good point 15:04:27 fabiog: I'd imaging the deprecation path will have to long, since so many services depend on it 15:04:33 I'd *imagine 15:05:25 eglynn: yeah, also there were discussions event to skip V3 in favour of V4, hierarchical projects ... but I haven't seem too much action around it 15:05:26 slightly related to releasing, here's the slate for the first release off stable/juno 15:05:29 #link https://launchpad.net/ceilometer/+milestone/2014.2.1 15:05:54 fabiog: yeah, I'd imagine that'll be Lemming timeframe (as opposed to Kilo)? 15:06:31 eglynn: yeah they will probably start in Lemming (I didn't know that is the name :-)) 15:07:22 fabiog: cool ... not the official name, but seems to be the standard joke when refering to the L* cycle :) 15:07:42 BTW on that stable/juno release, if anyone is interested in getting more involved in stable-maint, let me know 15:07:47 backports are fun! :) 15:07:57 ... no really, they are 15:08:24 k, moving on from releases 15:08:26 #topic Packaging of the merged compute/central agents 15:08:45 IvanBerezovskiy wanted to discuss this 15:09:18 we have now two packages for both agent. How it should be after merging Dina's patches? 15:09:31 Do we need in two packages for backward compatibility or not? 15:09:35 IvanBerezovskiy: I made some comments in the specs review https://review.openstack.org/#/c/119077/11/specs/kilo/merge-compute-and-central-agents.rst 15:09:47 #link https://review.openstack.org/#/q/status:open+project:openstack/ceilometer+branch:master+topic:merge-compute-and-central-agents,n,z 15:10:34 eglynn, am I right that the main idea is something like this: let's keep two packages for compute/central agents 15:10:41 going to the new code 15:10:50 using the namespaces option 15:11:04 and create new package with merged agent? 15:11:04 yeah I'd expect packagers to make the transition by adding a net-new openstack-ceilometer-polling package 15:11:08 ... but to maintain support for the existing openstack-ceilometer-central & openstack-ceilometer-compure packages also 15:11:23 did we ever figure out how to handle scenario where we have one agent on compute and one agent elsewhere but both in same group... wouldn't compute tasks go to foreign agent and fail? 15:11:28 for a allinone PoC => install penstack-ceilometer-polling 15:11:44 disclaimer: i haven't been following this spec. 15:11:59 that means openstack-ceilometer-central & openstack-ceilometer-compure packages depends on openstack-ceilometer-polling, right? 15:12:30 gordc: hmmm, the merged agent would have to join multiple partition groups surely? 15:12:31 they should depend in this scenario, I think 15:12:38 gordc, they won't be in one group :) 15:12:54 the group-prefix depends on the namespaces 15:12:57 gordc: (one for the central partitioning, the other for the compute partitioning) 15:13:00 for now 15:13:14 if it will be other type of setting - via pollster-list 15:13:18 cool cool. it'd be a doc thing. 15:13:33 carry on. :) 15:13:35 I suppose to have all of them being in groups defined by this list as well 15:13:39 a-ha, cool 15:13:41 llu-laptop: for the Fedora packaging, all the openstack-ceilometer-central & openstack-ceilometer-compure packages really provide is the upstart/systemd config for the service 15:13:53 llu-laptop: i.e. not actual python code 15:14:05 eglynn: got that, thx 15:14:19 eglynn, if we'll have 3 packages (for compute, central and common-polling), what about puppets? we need in update to use third package 15:14:20 llu-laptop: all those packages then depend on a common package which contains all the python code 15:14:20 so there will be a ceilometer-common where all those depends on 15:14:40 IvanBerezovskiy: again I mentioned that also in the review comment linked above 15:15:19 TL;DR: we'll need a new puppet manifest for the combined agent 15:15:21 eglynn, what's the process of contributing to the packages? 15:15:32 DinaBelova: for Fedora? 15:15:54 eglynn, well.... 15:16:01 I don't know process at all >_< 15:16:16 so I'm basically interested in Fedora, CentOS and Ubuntu :D 15:16:26 hehe 15:16:28 DinaBelova: here's the info on the Fedora package https://admin.fedoraproject.org/pkgdb/package/openstack-ceilometer/ 15:16:51 DinaBelova: from which the CentOS and RHEL packaging (RDO and RHOS) is also derived 15:17:00 a-ha, cool 15:17:04 DinaBelova: I guess the process will be different, at least from my colleagues experience of packaging for FC & Ubuntu 15:17:13 so basically that's contrubution process 15:17:16 llu-laptop, a-ha 15:17:20 do you have any details? 15:17:33 DinaBelova: becoming a Fedora packager involves gradually building up karma, commit rights etc. 15:17:46 DinaBelova: I can dig out some links on that later 15:17:46 DinaBelova: sorry I don't, just heard from him 15:17:51 eglynn, thanks! 15:17:56 eglynn, it'll be really nice 15:18:06 llu-laptop, ok, I'll try to investigate :) 15:18:09 DinaBelova: for the .deb packaging, I don't know much about how it works, but I'm guess similar 15:18:21 eglynn, I suppose the common process should be the same 15:18:23 DinaBelova: Chuck Short (zul) would be a good source to ask about that 15:19:06 eglynn, zigo I guess is the nice point to contact :) 15:19:09 ok, cool 15:19:22 ok, let's move on I guess 15:19:27 DinaBelova: ah yes, of cource, zigo too :) 15:19:30 that's just an announcement :) 15:19:33 yep, let's move on 15:19:41 #topic "TSDaaS/gnocchi status" 15:20:14 #link https://review.openstack.org/#/q/project:stackforge/gnocchi,n,z 15:20:48 notable landings 15:20:53 ... sileht got the gnocchi dispatcher and related circularity patches in \o/ :) 15:21:25 ... jd__ landed some fine-grained RBAC policys for the entity CRUD API 15:21:49 also Entities are no longer Entities :) 15:22:03 now they're known as Metrics 15:22:06 eglynn, /me fighting with gnocchi and devstack :) finally won it -> some opentsdb progress is coming 15:22:41 DinaBelova: \o/ nice one! ... I'll steal your notes on the fun you had getting that working :) 15:22:51 :D 15:22:56 :) 15:23:02 np :) 15:23:19 metrics looks better for me then entities ))) 15:23:24 sileht is also working on aggregation 15:23:28 idegtiarov: +1 15:23:36 idegtiarov, at least more understandable about what's it in fact :) 15:23:38 and I'm gonna continue policy implementation over archive policies and resources 15:23:46 DinaBelova: for sure 15:23:48 jd__: coolness 15:23:53 jd__, got problems with policies btw 15:23:54 I'm also working on a new documentation generator running real queries against Gnocchi to have real examples up to date 15:23:56 on the devstack + gnocchi 15:24:02 jd__: yeah, I haven't seen that aggregation patch update yet, looking forward to reviewing it 15:24:03 DinaBelova: let's debug in #openstack-ceilometer then :) 15:24:14 ok, I found the workaround 15:24:18 but it's tricky 15:24:31 I will try to land the devstack patch too 15:24:35 jd__, debug is coming :) 15:24:43 otherwise things look pretty good 15:25:03 sileht: excellent 15:25:22 jd__: coolness, anything else on gnocchi? 15:25:41 not yet :D 15:25:56 speaking of gnocchi, I saw 2 bps for ceilometer of adding new DB backend support, what's our general guide here? encourage them to add support into gnocchi instead of ceilometer? 15:26:09 llu-laptop: cassandra you mean? 15:26:22 llu-laptop, yes, good question! 15:26:28 I saw one cassandra, and maybe another 15:26:34 llu-laptop: yeah, I tried to gently nudge towards gnocchi 15:26:42 <_nadya_> and db2 woke up... 15:26:45 cassandra change has one more issue actually... 15:26:48 llu-laptop: but IIRC the contributor seemed some interested in "classic" ceilo 15:27:03 too much cassandra heplers in the ceilo code was proposed 15:27:17 much -> many, was -> were 15:27:30 llu-laptop: i have no intend on making elasticsearch db for gnocchi... apologies. 15:27:30 imho no matter gnocchi or ceilo that should be separated lib 15:28:00 DinaBelova: yeah, the cassandra patch has a bunch of code i think should really be in it's client... or maybe i'm too dumb to understand it... let's assume the former. 15:28:16 gordc, ++ 15:28:36 I think it's ok if it's for event support 15:28:53 for samples, it seems like it's not a good idea anymore if we plan to drop the old API 15:28:56 gordc: right, elasticsearch 15:29:43 seems like the effort of adding a driver would be rewarded with more future "shelf-life" on the gnocchi side 15:29:53 <_nadya_> jd__: yep, but how to explain this to contributors? :) 15:30:17 _nadya_, -2s? 15:30:17 _nadya_: copy paste what I wrote? ;) 15:30:18 :( 15:30:25 <_nadya_> jd__: hehe 15:31:20 _nadya_: well we can't dictate what they spend their effort on, the best we can do is "nudge" towards gnocchi 15:31:32 <_nadya_> DinaBelova: why -2? because "we refuse to accept new changes in drivers, we have new policy"? 15:31:49 _nadya_: +1. aren't we telegraphing a bit if we don't allow them to add to "classic" cm? meaning, -2's is saying "you can't" 15:32:17 * eglynn prefers the carrot to the stick in this context 15:32:25 _nadya_, nope, but if just words won't work and we could not encourage people to move their code to gnocchi 15:32:28 what else can we do? 15:32:49 merge to ceilo? 15:33:03 that's also variant... 15:33:16 <_nadya_> eglynn: yep, agreed that we can't... but we don't wan't to have a lot of "unneeded helpers" in the code 15:33:18 but that'll be kind of useless efforts for contributors.. 15:33:32 my hope would be that if we can explain the future benefits of gnocchi, that reasonable contributors will want to be a part of that 15:33:53 eglynn: agreed 15:34:00 eglynn: +1 15:34:15 <_nadya_> DinaBelova: yep, I just raising the question :) unfortunately I don't know how it should be resolved in opensource 15:34:24 _nadya_, yeah.. 15:34:51 k, shall we move on? 15:35:11 <_nadya_> maybe we may add smth like "our wishes to contributors" on wiki :) 15:35:39 _nadya_: good point 15:35:40 _nadya_: yeah, it would be good to have to "loose" policy/preferences written down that we could point to 15:35:43 _nadya_: no one reads the wiki... (see most blog posts about ceilometer) 15:35:55 <_nadya_> eglynn: yep, sorry for interrupting, go on 15:35:59 _nadya_: I think a general explanation of architectural direction would do the same....plus get more eyes. 15:36:03 gordc: is that because there's nothing real there? 15:36:04 #topic "Final call on dates/location for mid-cycle" 15:36:16 #link https://etherpad.openstack.org/p/CeilometerKiloMidCycle 15:36:26 cdent: but my fancy architecture diagram?!?!? lol 15:36:36 it is pretty nice 15:36:41 lol 15:36:49 eglynn: it seems that we are going for the week of 20 in Gallway 15:36:50 only because of the rotation though ;) 15:37:03 cdent: true true. :) 15:37:12 fabiog: yep, are you good on the organizational side of that? 15:37:32 eglynn: yes, if we confirm I can go ahead and start 15:38:00 fabiog: well it seems we have quorum in terms of folks signed up 15:38:03 DinaBelova: any news on your attendance (company approval)? 15:38:14 fabiog, not yet... to early... 15:38:16 fabiog: eglynn: but is there a list of compelling topics to cover? 15:38:27 too* 15:38:36 fabiog, sorry 15:38:38 nealph: my focus will be on gnocchi migration 15:38:46 I'm a bit worried about the low attendance for that mid cycle 15:39:01 not sure I've many things to say face to face to DinaBelova, eglynn and ildikov 15:39:05 jd__: 6 below quorum do you think? 15:39:10 not that I don't miss you guys 15:39:15 jd__: LOL :) 15:39:23 I don't yet know if I'd be able to go, but would like to 15:39:29 eglynn: how many we were in Paris? 15:39:46 but we can also spend some afternoons in a Hangout and that might be equally OK to me I think 15:39:52 cdent: aren't you kind of local? 15:39:59 fabiog: hmmm, same ballpark I think, maybe one or two more? 15:40:02 <_nadya_> jd__: you may write the code, not only talking :) 15:40:03 * jd__ just thinking out loud 15:40:15 _nadya_: right 15:40:36 eglynn: is this being combined with other projects like last time? 15:40:42 jd__: yep, I would like to mix up the format and not spend all the time on round table discussion as before 15:40:46 could we move it south at least? Caribbeans anyone? 15:40:58 gordc: nope, just ceilo IIUC 15:41:20 fabiog: (unless the other HP folks in Galway want to pile on?) 15:41:22 eglynn: I think some discussion around "access" scope would be good 15:41:38 fabiog: "access" scope? 15:41:42 eglynn: I think it will be mainly Ceilo at this stage 15:41:43 fabiog: yes, but budgeting is rather confused 15:42:00 fabiog: do you mean travel options to Galway? 15:42:17 eglynn: yes to decide what grants to give based on Domain or Project 15:42:30 eglynn: no is a topic for the meeting ..: -) 15:42:35 eglynn: a-ha, k, got it 15:43:10 right let's pullk together to quick etherpad with topic suggestions 15:43:12 Ok. So do we have consensus on the meeting? 15:43:42 or any objection? 15:43:55 fabiog: ... as agreed as we'll ever be I think 15:44:30 eglynn: well, I will consider the meeting to happen and start planning 15:44:34 same as last meetup for me... will join via hangouts unless kickstarter comes through again. 15:44:51 gordc: drats! :( 15:45:03 I guess anyone who's interested in attending, but unsure of budget ... please chase approvals if you can so that we've got a solid headcount 15:45:23 I think the unsure are DinaBelova and cdent 15:45:30 and gordc at this stage 15:45:31 yeap 15:45:44 I'll sail. 15:45:50 (if I had a sailboat) 15:45:52 I'll cycle :) 15:45:56 fabiog, basically after the summit costs companies will send people only if really important quesiotns will be discussed, etc.... that's why budget approval stuff might work only if it'll be kind of specific agenda, etc. 15:46:07 cdent, what I should do???? 15:46:15 * jd__ waits for the agenda too 15:46:17 DinaBelova: good point, let's work on firming up the agenda this week 15:46:30 eglynn, yeah, sorry to say this 15:46:48 I can't go to my manager and say "send me somewhere" :) 15:46:56 at least not so easy :D 15:47:06 DinaBelova: yep, I understand 15:47:08 DinaBelova: we've seen the news... you guys are rich now :P 15:47:25 gordc, I did not see this money :D 15:47:47 ha! 15:47:49 <_nadya_> gordc: hehe, yep 15:48:07 next time I want this office http://www8.hp.com/lamerica_nsc_carib/en/contact-hp/office-locations.html 15:48:22 jd__, hehe 15:48:26 not bad 15:48:30 jd__: I offered Sunnyvale in CA 15:48:41 fabiog: yeah I voted for that one :p 15:48:42 but you guys all signed up for Gallway ... :-) 15:48:43 ocean is cold there :) 15:49:02 could folks start throwing topic suggestions into this etherpad https://etherpad.openstack.org/p/galway-jan-2014-ceilometer-sprint 15:49:54 sorry folks, I'm gonna have to run shortly 15:50:03 I'm late for a company event starting at 1600UTC 15:50:11 OK if we close a few mins early today? 15:50:16 jd__: I've been fighting for a meeting at the HP Sydney office.... 15:50:16 yep boss 15:50:22 jd__: thank you sir! 15:50:40 thanks for you time folks, 'fraid I'm gonna have to cut and run! 15:50:46 I guess all important moment are discussed :) 15:50:46 * cdent has 10 last minute things to keep eglynn 15:50:48 eglynn, thanks! 15:50:56 cdent: LOL :) 15:50:56 ok, thanks 15:51:12 <_nadya_> thank, guys! 15:51:14 #endmeeting ceilometer