Wednesday, 2014-04-02

*** promulo has joined #openstack-ceilometer00:05
*** sdake_1 has quit IRC00:15
*** matsuhashi has joined #openstack-ceilometer00:26
*** openstackgerrit has joined #openstack-ceilometer00:30
*** gordc has quit IRC00:45
*** matsuhashi has quit IRC00:47
*** matsuhashi has joined #openstack-ceilometer00:48
*** sdake has joined #openstack-ceilometer00:48
*** sdake has joined #openstack-ceilometer00:48
*** matsuhashi has quit IRC00:52
*** matsuhashi has joined #openstack-ceilometer00:57
openstackgerritliusheng proposed a change to openstack/ceilometer: Fix the floatingip pollster
*** jaypipes has quit IRC01:08
openstackgerritliusheng proposed a change to openstack/ceilometer: Fix the return of statistic with getting no sample
openstackgerritliusheng proposed a change to openstack/ceilometer: Fix the floatingip pollster
*** nosnos has joined #openstack-ceilometer01:47
*** changbl has joined #openstack-ceilometer01:47
*** flwang has quit IRC02:17
*** flwang has joined #openstack-ceilometer02:55
*** flwang has quit IRC03:03
*** flwang has joined #openstack-ceilometer03:04
openstackgerritJia Dong proposed a change to openstack/ceilometer: Sync rpc modules from oslo-incubator
*** matsuhashi has quit IRC03:21
*** nosnos has quit IRC03:37
*** _nadya_ has joined #openstack-ceilometer03:41
*** _nadya_ has quit IRC03:59
*** gordc has joined #openstack-ceilometer04:17
*** piyushmasrani has joined #openstack-ceilometer04:29
*** nosnos has joined #openstack-ceilometer04:31
*** matsuhashi has joined #openstack-ceilometer04:36
*** matsuhashi has quit IRC04:50
*** gordc has quit IRC04:55
*** matsuhashi has joined #openstack-ceilometer05:00
*** ildikov_ has quit IRC05:23
*** inc0_ has joined #openstack-ceilometer05:52
*** inc0_ has quit IRC05:53
*** inc0_ has joined #openstack-ceilometer05:53
openstackgerritJenkins proposed a change to openstack/ceilometer: Imported Translations from Transifex
*** mihgen has joined #openstack-ceilometer06:12
*** ildikov_ has joined #openstack-ceilometer06:13
*** shardy_afk is now known as shardy06:33
*** saju_m has joined #openstack-ceilometer06:39
*** tasdomas` has joined #openstack-ceilometer07:25
*** tasdomas has quit IRC07:25
*** saju_m has quit IRC07:42
*** boris-42 has quit IRC07:50
*** boris-42 has joined #openstack-ceilometer07:51
*** nacim has joined #openstack-ceilometer07:51
*** saju_m has joined #openstack-ceilometer07:52
*** piyushmasrani has quit IRC08:25
*** wayneeseguin has quit IRC08:28
*** wayneeseguin has joined #openstack-ceilometer08:28
*** yassine has joined #openstack-ceilometer08:38
*** eouti has joined #openstack-ceilometer08:39
*** saju_m has quit IRC08:48
*** saju_m has joined #openstack-ceilometer08:49
*** flwang has quit IRC09:11
*** saju_m has quit IRC09:24
openstackgerritIlya Tyaptin proposed a change to openstack/ceilometer: Add unit test for checking right order of sample list
*** saju_m has joined #openstack-ceilometer09:26
*** saju_m has quit IRC09:31
openstackgerritA change was merged to openstack/ceilometer: Disable oslo.messaging debug logs
*** alexpilotti has joined #openstack-ceilometer09:34
*** admin0 has joined #openstack-ceilometer09:36
*** saju_m has joined #openstack-ceilometer09:42
*** matsuhashi has quit IRC09:50
*** matsuhashi has joined #openstack-ceilometer09:57
*** flwang has joined #openstack-ceilometer09:59
*** eglynn has joined #openstack-ceilometer10:16
eglynnjay_t_c: around?10:17
eglynnjay_t_c_2: ^^^10:17
*** aswadrangnekar has joined #openstack-ceilometer10:17
eglynnjay_t_c_2: finally I got around to looking at your heat problem, but only had a spare RHEL VM to play with10:18
eglynnjay_t_c_2: ... so I used the latest incarnation of the havana-derived Red Hat opensatck distro (as opposed to the canonical distro for ubuntu)10:19
eglynnjay_t_c_2: ... all went swimmingly with your template10:19
eglynnjay_t_c_2: ... the alarm_actions as expected are a pre-signed http URL10:20
aswadrangnekarI am trying to use raw_request method from ceilometer client file10:20
eglynnjay_t_c_2: ... [u'']10:20
eglynnjay_t_c_2: ... so for some reason looks like the alarm action is being truncated somewhere in your case (i.e. either on the heat or ceilo side)10:21
eglynnjay_t_c_2: ... what storage driver are you using?10:21
aswadrangnekarbut I an not able to access this method after initializing the client10:22
aswadrangnekaris there a usecase where python ceilometer client is used by other projects?10:24
eglynnaswadrangnekar: yes10:24
eglynnaswadrangnekar: heat10:24
eglynnaswadrangnekar: and horizon10:25
aswadrangnekareglynn: thanks I will take a look10:25
eglynnaswadrangnekar: BTW ceilometer itself used python-ceilometerclient10:25
eglynnaswadrangnekar: (in the alarm-evaluator)10:25
*** ildikov_ has quit IRC10:26
aswadrangnekareglynn: thank for the pointer :) , let me have a look at it10:27
eglynnaswadrangnekar: np! ... BTW the horizon client is instantiated here:
*** kun_huang has joined #openstack-ceilometer10:41
*** matsuhashi has quit IRC11:00
*** nosnos has quit IRC11:04
*** openstackgerrit has quit IRC11:08
*** openstackgerrit has joined #openstack-ceilometer11:08
*** matsuhashi has joined #openstack-ceilometer11:16
*** julim has joined #openstack-ceilometer11:16
*** kun_huang has quit IRC11:44
*** admin0 has quit IRC11:52
*** mengxd has joined #openstack-ceilometer12:04
*** jay_t_c_2 has quit IRC12:09
*** admin0 has joined #openstack-ceilometer12:12
*** saju_m has quit IRC12:17
*** admin0 has quit IRC12:22
*** admin0 has joined #openstack-ceilometer12:26
*** kun_huang has joined #openstack-ceilometer12:26
*** jdob has joined #openstack-ceilometer12:28
*** vrovachev has joined #openstack-ceilometer12:29
*** eouti has quit IRC12:32
*** admin0 has quit IRC12:35
*** ildikov_ has joined #openstack-ceilometer12:36
*** admin0 has joined #openstack-ceilometer12:40
*** promulo has quit IRC12:41
*** saju_m has joined #openstack-ceilometer12:47
*** kun_huang has quit IRC12:50
*** kun_huang has joined #openstack-ceilometer12:54
*** gordc has joined #openstack-ceilometer12:58
*** matsuhashi has quit IRC13:02
*** matsuhashi has joined #openstack-ceilometer13:02
*** prad_ has joined #openstack-ceilometer13:04
eglynnfolks, FYI there's an alternative summit being organized in APAC13:05
eglynn... perhaps we should think of submitting some ceilo proposals?13:05
eglynn... for details see
*** admin0_ has joined #openstack-ceilometer13:06
*** matsuhashi has quit IRC13:07
eglynn... /me is a day late and a dollar shy ;)13:07
*** admin0 has quit IRC13:08
*** admin0_ is now known as admin013:08
*** matsuhashi has joined #openstack-ceilometer13:10
eglynngordc: got time for a super-quick question?13:11
eglynngordc: about
eglynngordc: so I was thinking of carrying this as a additional patch in the havana-derived RH openstack distro13:12
eglynn(... seeing as it's not on stable/havana and prolly not suitable for backport)13:12
eglynngordc: ... but remind me of problematic aspect of this discussed last week, it was a postgres-only issue right?13:13
*** gordc has quit IRC13:24
*** promulo has joined #openstack-ceilometer13:24
*** admin0 has quit IRC13:35
*** saju_m has quit IRC13:36
*** admin0 has joined #openstack-ceilometer13:37
*** admin0 has quit IRC13:40
*** admin0 has joined #openstack-ceilometer13:41
*** admin0 has quit IRC13:45
*** admin0 has joined #openstack-ceilometer13:48
eglynnjd__: do you know where we specify the mongodb version used by the scenario tests in the gate?13:49
eglynn... or is it just latest available in whatever package repo?13:49
jd__option #213:49
jd__so the mongodb tests do not run on py27 because it's Oldbuntu13:49
jd__only on py26 where CentOS is used and has a more recent MongoDB13:49
eglynnyeah py26 is the problem ... /me is trying to figure out this py26 specific fail on stable/havana13:50
*** admin0 has quit IRC13:50
eglynn... can't reproduce it on RHEL tho' with mongodb 2.4.6 installed13:50
jd__eglynn: looks like it's because 1 is different than 213:50
jd__you're welcome.13:50
*** admin0 has joined #openstack-ceilometer13:50
eglynnjd__: darn! why didn't I think of that ;)13:51
jd__eglynn: replace self.assertEqual(len(resources), 2) by self.assertEqual(len(resources), len(resources)) and that should work13:51
jd__you're welcome, AGAIN.13:51
eglynnjd__: LOL :)13:52
jd__more seriously that's weird that it suddenty happens on stable13:52
eglynnjd__: ... well only for the patch that ups the "implicit" mongo requirement to 2.413:52
jd__I don't think the nodes are different between py26 for stable and master13:55
jd__maybe the patch cherry-pick misses something? :(13:55
eglynnjd__: ... to be fair, the patch also changes the resource collection somewhat, so not necessarily related to versioning13:55
eglynnjd__: ... yep, always poss that I screwed that up ;)13:55
jd__yeah I don't think it's versioning at all13:55
eglynnjd__: cough, nothing to see here ;)13:56
eglynnjd__: ... yep bad cherry pick13:56
eglynnjd__: ... /me scurries off to fix13:56
jd__eglynn: you know what?13:57
eglynnjd__: shoot13:57
eglynnjd__: my belated but sincere thanks, good sir!13:58
*** aswadrangnekar has quit IRC14:04
*** mengxd has quit IRC14:09
*** admin0_ has joined #openstack-ceilometer14:09
*** admin0 has quit IRC14:10
*** admin0_ is now known as admin014:10
openstackgerritNadya Privalova proposed a change to openstack/ceilometer: Make entities (Resource, User, Project) able to store lists
*** inc0_ has quit IRC14:15
openstackgerritNadya Privalova proposed a change to openstack/ceilometer: Make entities (Resource, User, Project) able to store lists
*** aswadrangnekar has joined #openstack-ceilometer14:18
*** mriedem has joined #openstack-ceilometer14:21
*** mriedem has left #openstack-ceilometer14:22
*** htruta has joined #openstack-ceilometer14:24
htrutahello, guys! i'm trying to get some ceilometer information in nova. Is that possible? can i get it through ceilometer client or the file generated by ceilometer?14:25
*** admin0 has quit IRC14:26
*** aswadrangnekar has left #openstack-ceilometer14:29
*** nealph has joined #openstack-ceilometer14:30
*** admin0 has joined #openstack-ceilometer14:35
*** gordc has joined #openstack-ceilometer14:38
gordceglynn: sorry about that. internet cut out at my apartment. sent you an email.14:39
eglynngordc: yeah thanks for that, I was just responding to your mail14:39
eglynngordc: ... but easier to just say it on IRC14:40
gordceglynn: ok.14:40
eglynngordc: ... so in the meantime I was reminding myself of the last weekly meeting discussion and IIUC seems to be indicating that the issue impacts postgres only and *not* mysql14:40
eglynn... e.g. <gordc> jd__: agreed. there's something wonky happening which doesn't let postgres work with multiple connection but let's mysql14:41
eglynngordc: ^^^ is that in reference to the same multi-worker collector patch?14:41
eglynngordc: ... or am I conflating two separate issues?14:41
gordceglynn: right. so it's sort of two different issues. there's that item...14:41
gordcand then there's also the fact that you'll get deadlock/rollback errors in both sql backends as well even with the postgres patch.14:42
openstackgerritNadya Privalova proposed a change to openstack/ceilometer: Make entities (Resource, User, Project) able to store lists
eglynngordc: so currently on master, what's the status in terms of brokeness against either mysql or postgres?14:43
gordceglynn: this is the patch i have that resolves it but the real fix is to fix the data moel14:44
gordceglynn: you should probably stick with a single worker... it's not committing fast enough with the above patch.14:44
gordcs/with the/without the/14:45
eglynngordc: so without ... are *both* sqla DBs problematic on master with multiple collectors?14:46
eglynn(i.e. either multiple workers or multiple processes)14:46
gordceglynn: i didn't see the issue as much (or at all) with multiple collector services... that said i didn't test as much that scenario.14:47
gordceglynn: you'll definitely see it under decent loads if you spawn multiple workers under single service.14:48
eglynngordc: sounds like we need to release-note this as a know issue with the sqla driver?14:49
eglynngordc: ... i.e. instruct users not to spawn multiple worker threads in the sqla case14:49
gordceglynn: yeah. we'll definitely need a backport at some point.14:50
eglynngordc: k, let's discuss in more detail at the weekly meeting what needs to be explicitly captured in the icehouse release notes (prior to future backports onto stable/icehouse)14:52
eglynngordc: ... in the meantime, sounds like your multi-worker patch is safe to carry in RHOS as we only support mongo14:52
*** matsuhashi has quit IRC14:52
*** jmckind has joined #openstack-ceilometer14:52
gordceglynn: ok. give it a try just to confirm but all the issues i saw were sql related.14:54
eglynngordc: cool, will do14:54
gordceglynn: i actually won't be at meeting tomorrow (will be out of town) so i'll send you guys a note if i recall any other issues.14:54
eglynngordc: great, thank you sir!14:55
htrutahello? anyone?14:57
eglynnhtruta: anyone what?15:02
nprivalovaeglynn, gordc, I need you thoughts about
eglynnnprivalova: so what's the story, same resource but different sources?15:10
nprivalovaeglynn: same meters but different sources15:10
eglynnnprivalova: but meters are per-resource, right?15:11
nprivalovaeglynn: yep15:11
nprivalovaeglynn: let me find a short example...15:12
eglynnnprivalova: so "same meters but different sources" is equivalent to "individual resource(s) each associated with multiple sources"?15:12
nprivalovaeglynn: if we have15:13
nprivalovaeglynn: {'user_id': u'user-id-alternate', 'name': 'instance', 'resource_id':  u'resource-id-alternate', 'source': 'test-2', 'project_id':  u'project-id', 'type': 'cumulative', 'unit': ''}15:13
nprivalovaeglynn: {'user_id': u'user-id-alternate', 'name': 'instance', 'resource_id':  u'resource-id-alternate', 'source': 'test-3', 'project_id':  u'project-id', 'type': 'cumulative', 'unit': ''}15:13
nprivalovaeglynn: these objects are not distinguished15:13
eglynnnprivalova: ... so only delta is the source value, right?15:14
nprivalovaeglynn: yep15:14
eglynnnprivalova: when we discussed this yesterday (IIRC) my instinct was ...15:14
eglynn... since this scenario is not going to come up in real-life15:14
eglynn... => we shouldn't sweat it too much15:14
nprivalovaeglynn: my problem is that I need to maintain this behavior in HBase :)15:15
*** jaypipes has joined #openstack-ceilometer15:15
eglynnnprivalova: can you explain why? do you have a definite use-case for the multiple sources?15:15
nprivalovaeglynn: no, we have unit-tests with it :(15:15
nprivalovaeglynn: "scenario-tests"15:16
eglynnnprivalova: so the test referred to in the bug
eglynnnprivalova: ... that's passing on master, but failing on your development branch?15:17
gordcnprivalova: i think we should probably hold off on the hbase updates... i think we need to really finalise the data model we want to store... ie. multiple sources needed.15:17
nprivalovaeglynn: yep, but there are several tests, not only this. I made a hack to make it work but meter-list works too long because of it15:18
*** mihgen has quit IRC15:18
eglynngordc: agree we need closure on the unfinished discussion started at the last summit
eglynnnprivalova: "works too long"?15:19
gordceglynn: agreed. no point wasting time fixing for something that may be wrong.15:19
eglynnnprivalova: i.e. the test takes too long to run?15:20
nprivalovagordc, eglynn, I would like meter-list works correct in Icehouse. Maybe long but correct15:20
nprivalovaeglynn: on real env, not test15:20
gordcnprivalova: i think there's also another problem with meter-list.15:21
nprivalovaeglynn, gordc, actually my complains about bug 1301371 is for discussions on summit15:21
eglynnnprivalova: ok, two things ... 1. getting another changes into icehouse would need an RC2 to be cut, right?15:21
*** openstackgerrit has quit IRC15:21
*** openstackgerrit has joined #openstack-ceilometer15:21
eglynnnprivalova: and 2. meter-list working unexpectedly with multi-source resources in real env isn't really a problem if "real" samples always respect a 1:1 relationship between resource:source15:23
gordcnprivalova: right now, we store meters in a list with resource in mongo/hbase. that list may contain stale meters if we ever run ttl since we only ever add and never remove.... might also be a problem in sql.15:23
nprivalovaeglynn: I need only one patch . It repairs meter-list and doesn't affect any other modules except HBase15:23
nprivalovagordc: I fixed it :)15:23
gordcnprivalova: really? cool!15:24
nprivalovagordc: stop :)15:24
eglynnnprivalova: would you consider a release-critical bug?15:25
gordcnprivalova: i would think only critical items would justify a RC2 build htough. if not, it should be a backport15:25
eglynnnprivalova: (... marked as Medium currently)15:25
eglynnnprivalova: ... if not release-critical, I'd suspect we'd have a job persuading ttx to cut an RC215:25
eglynnnprivalova: ... likely he'd pushback to just punt to 1st stable/icehouse release15:26
eglynn(i.e. wot gordc just said)15:26
nprivalovaeglynn: let me try to explain. Now get_meters returns very cut version of meters. "very" means only 10%15:26
nprivalovaeglynn: about15:26
eglynnnprivalova: ... so reading between the lines, do you consider this bug to be more important than Medium?15:27
nprivalovaeglynn: It's hard to evaluate how critical it is... From one hand it's just API output15:27
eglynn("medium" == "Fix when convenient, or schedule to fix later")15:28
nprivalovaeglynn: from other hand meter-list is very common request15:28
gordcnprivalova: for me, critical is 'this doesn't start or this crashes'15:28
nprivalovagordc: yep, I mostly agree15:29
eglynngordc: +115:29
gordcnprivalova: i guess one way to look at it is if you were a deployer and saw this error about this at 4am in the morning. would you fix it or would you sleep for another 3
gordcthat said, i'd probably always choose to sleep for another 3 hrs.15:30
eglynnnprivalova: I could be wrong, but I'm thinking incomplete info returned by GET /v2/meters doesn't warrant the Critical tag ... but perhaps High?15:31
nprivalovagordc: hehe :) Maybe it's not normal but my dreams were about this issue today :)15:31
nprivalovaeglynn: yep, High is better that Medium or Critical15:31
eglynnnprivalova: ... so you could re-prioritize it as "High" and see if we can get the patch landed on master first at least15:32
gordceglynn: agreed, non-critical to me.15:32
nprivalovaeglynn: ok, will do15:32
eglynnnprivalova: ... without it being on master, there's only a very weak case to persuade ttx we need an RC215:32
gordcnprivalova: i've had a few of those dreams... scary that i dream about ceilometer now.15:32
eglynnnprivalova: ... but even with it on master, he still may baulk at cutting another RC and instead prolly would punt to stable/icehouse15:33
nprivalovaeglynn: ok. I have some plans about performance against backends and wanted to use master-HBase for it... And maybe prepare some demo for summit about HBase to show how it works. I guess that it's the main reason (for me) to have it it Icehouse. But if think once more it's not critical actually15:36
nprivalovagordc: I'm trying to understand your ttl example. Do you mean that we should clean meters in Resource table if meter becomes removed?15:39
gordcnprivalova: right. well if i remember correctly, we currently have a a list of meters under resource which we append to (if new). but if we run ttl, there's a chance that the sample (and meter) will be removed but it won't be removed in list of meters under resource.15:41
gordcnprivalova: so if we call meter-list we'll get back meters that may have been cleaned by ttl (or whatever other reason, ie. archiving)15:42
gordcnprivalova: did that make sense? basically the list we are storing under resource is a historical list and not one that reflects what currently exists in db... (disclaimer: i've yet to verify this)15:46
nprivalovagordc: hmm, hard to imagine remove of meter if there is no "meter" table, only "sample" actually...But it looks like everything should be ok in HBase. We may determine ttl for all tables and entries. If all samples related to one meter disappears after 100 minutes then entry that corresponds this meter in resource table will disappear too because it's "age" equals to the latest sample that corresponds meter15:49
nprivalovagordc: now we store "columns" in HBase, not list15:50
gordcnprivalova: ok cool. yeah i haven't really seen your new code but i think adding columns instead of list makes more sense for hbase.15:51
gordcnprivalova: this is just based on previously looking at hbase/mongo code.15:51
*** Vic has joined #openstack-ceilometer15:51
nprivalovagordc: yes. actually there are a lot of things that may be done in HBase. E.g. now we use only one filter. But HBase contains 10th of them15:53
gordcnprivalova: you proposing a session on hbase? i know Alexei_987 has one for data model i think we should make sure we implement the data model specific to the backend.15:56
nprivalovagordc: unfortunately I cannot go to summit. I hope Alexey will go. In this case he will be responsible for HBase demo :) Hope he will not mind15:58
*** Ruetobas has quit IRC16:01
eglynnnprivalova: "And maybe prepare some demo for summit about HBase to show how it works" ==> I'll look forward to it! :)16:02
eglynnnprivalova: "unfortunately I cannot go to summit" ==> that's a pity! :(16:02
*** Ruetobas has joined #openstack-ceilometer16:03
*** thomasem has joined #openstack-ceilometer16:03
nprivalovaeglynn: it's better to home O:-)16:04
nprivalovaeglynn: *to be16:04
eglynnnprivalova: yeap, I hear ya! :)16:04
*** samcdona has joined #openstack-ceilometer16:06
*** Ruetobas has quit IRC16:08
htrutaeglynn: i'm trying to get some ceilometer information in nova. Is that possible? can i get it through ceilometer client or the file generated by ceilometer?16:09
eglynnhtruta: "get some ceilometer information in nova" == "get some information about nova resources from ceilometer"?16:10
eglynnhtruta: here are nova meters that ceilometer collects
eglynnhtruta: you can access these programmatically via the python-ceilometerclient library16:11
eglynnhtruta: or via the CLI16:11
*** admin0 has left #openstack-ceilometer16:12
eglynnhtruta: e.g. $ ceilometer statistics -m cpu_util -q resource=$INSTANCE_ID16:12
htrutaeglynn: exactly! that's what i want16:12
eglynnhtruta: ^^^ to get the CPU utilization for a particular instance16:12
eglynnhtruta: you need to ensure that the ceilometer compute agent is running on every nova-compute node16:13
*** Ruetobas has joined #openstack-ceilometer16:14
htrutacan i instance the ceilometer client inside nova?16:14
eglynnhtruta: I don't understand your question16:18
htrutaeglynn: is it possible to get access to the ceilometer via client on the nova?16:21
htrutaprogrammatically, i mean16:22
eglynnhtruta: when you say "on the nova" do you mean "on the nova compute node"?16:22
*** sphoorti_ has joined #openstack-ceilometer16:23
htrutaon the nova, for each compute node... i want the statistics about every single instance16:23
eglynnhtruta: you can run the ceilometer client from any host that has access to keystone and the ceilometer-api service16:24
eglynnhtruta: ... just like you can run the clients for any other openstack service16:25
*** nacim has quit IRC16:38
*** admin0 has joined #openstack-ceilometer16:41
*** Vic has quit IRC16:41
*** admin0 has quit IRC16:44
htrutaeglynn: i didnt know this usage of the clients. thanks!16:55
*** eglynn has quit IRC16:55
*** vrovachev has quit IRC17:04
*** sphoorti_ has left #openstack-ceilometer17:04
*** htruta has quit IRC17:13
*** jmckind has quit IRC17:38
*** nprivalova has quit IRC17:38
*** nprivalova has joined #openstack-ceilometer17:47
*** kun_huang has quit IRC18:02
*** mihgen has joined #openstack-ceilometer18:06
*** zul has quit IRC18:09
*** zul has joined #openstack-ceilometer18:12
*** urulama has joined #openstack-ceilometer18:24
*** gordc has quit IRC18:33
openstackgerritA change was merged to openstack/ceilometer: ensure dispatcher service is configured before rpc
*** mihgen has quit IRC18:39
*** yassine has quit IRC18:45
*** _nadya_ has joined #openstack-ceilometer18:45
*** alexpilotti has quit IRC18:50
*** _nadya_ has quit IRC18:52
*** urulama has quit IRC18:56
*** rwsu has quit IRC19:01
*** jaypipes has quit IRC19:05
*** rwsu has joined #openstack-ceilometer19:07
*** _nadya_ has joined #openstack-ceilometer19:07
*** _nadya_ has quit IRC19:46
*** gordc has joined #openstack-ceilometer19:57
*** thomasem_ has joined #openstack-ceilometer20:38
*** thomasem has left #openstack-ceilometer20:38
*** thomasem_ is now known as thomasem20:38
*** gordc has quit IRC20:47
*** ok_delta has joined #openstack-ceilometer20:59
*** jdob has quit IRC21:00
*** yjiang5_1 has quit IRC21:01
*** yjiang5 has joined #openstack-ceilometer21:07
*** yjiang5 has quit IRC21:07
*** yjiang5 has joined #openstack-ceilometer21:35
*** promulo has quit IRC21:45
*** thomasem has quit IRC21:47
*** prad_ has quit IRC22:48
*** ok_delta has quit IRC22:56
openstackgerritJenkins proposed a change to openstack/ceilometer: Updated from global requirements
*** bada has quit IRC23:26

Generated by 2.14.0 by Marius Gedminas - find it at!