Thursday, 2013-08-29

openstackgerritSandy Walsh proposed a change to openstack/ceilometer: Reject duplicate events  https://review.openstack.org/4419100:17
*** herndon has quit IRC00:20
*** krtaylor has quit IRC00:25
*** krtaylor has joined #openstack-metering00:33
*** shaneduan is now known as shaneduan[afk]00:33
*** shardy has quit IRC01:08
*** fnaval_ has joined #openstack-metering01:19
*** fnaval_ has quit IRC01:19
*** fnaval_ has joined #openstack-metering01:20
*** d34dh0r53 has joined #openstack-metering01:59
*** d34dh0r53 has quit IRC02:02
*** anteaya has quit IRC02:05
*** zul has quit IRC02:20
*** thomasm has joined #openstack-metering02:22
*** d34dh0r53 has joined #openstack-metering02:28
*** d34dh0r53 has quit IRC02:33
openstackgerritA change was merged to openstack/ceilometer: Adds group by statistics for MongoDB driver  https://review.openstack.org/4304302:42
*** SergeyLukjanov has joined #openstack-metering02:50
*** thomasm has quit IRC02:54
*** SergeyLukjanov has quit IRC03:34
*** dina_belova has joined #openstack-metering03:54
*** dina_belova has quit IRC03:56
*** dina_belova has joined #openstack-metering03:57
*** dina_belova has quit IRC04:01
*** boris-42 has joined #openstack-metering04:30
*** sandywalsh has quit IRC04:37
openstackgerritLianhao Lu proposed a change to openstack/ceilometer: Adding hardware-agent  https://review.openstack.org/4307204:49
openstackgerritLianhao Lu proposed a change to openstack/ceilometer: Added hardware agent's inspector and snmp implementation  https://review.openstack.org/4307304:49
*** dina_belova has joined #openstack-metering05:07
*** sandywalsh has joined #openstack-metering05:07
*** SergeyLukjanov has joined #openstack-metering05:11
*** dina_belova has quit IRC05:12
*** SergeyLukjanov has quit IRC05:13
*** SergeyLukjanov has joined #openstack-metering05:16
*** eglynn has joined #openstack-metering05:16
*** SergeyLukjanov has quit IRC05:21
*** SergeyLukjanov has joined #openstack-metering05:23
*** SergeyLukjanov has quit IRC05:32
*** SergeyLukjanov has joined #openstack-metering05:48
*** SergeyLukjanov has quit IRC05:53
*** SergeyLukjanov has joined #openstack-metering05:56
*** SergeyLukjanov has quit IRC06:02
openstackgerritJenkins proposed a change to openstack/ceilometer: Imported Translations from Transifex  https://review.openstack.org/4421606:04
*** flwang has quit IRC06:38
*** infiniti has quit IRC06:45
*** flwang has joined #openstack-metering06:59
llusileht: ping07:18
silehtllu, pong07:20
llusileht: about your comment of patch https://review.openstack.org/#/c/43074/, what's special about the NotImplementedError?07:21
llujd__: about the devstack patch of changing mongodb to mysql, is that ok even mysql still doesn't support metadata query?07:22
*** evanjfraser_ has quit IRC07:23
silehtllu, I'm just afraid if a inspector doesn't Implement a pollster, I will have my log file growing quickly with Exception related to something I can fix (as operator), I'm sure supervision guys take care of Exception message, and don't take care about level like INFO ?07:25
*** yolanda has joined #openstack-metering07:25
silehtllu, for now; it's a detail, we have only one inspector and it implements all pollsters, so07:27
llusileht: ok. What if I change the inspector base's methods into abstract method, so illegal inspectors can not be loaded at start time07:28
llusileht: actually, we can have multiple inspectors, it's defined in the pipeline as in the 'resources', e.g. snmp://10.1.1.1 means using inspector snmp to poll from host 10.1.1.107:29
silehtllu, this just force the new inspect to raise NotImplementedError itself, we have already done that for db backend07:30
silehtllu, when I say one inspector, this is for one inpector class not instance of it07:31
silehtllu, I like the new resources: in the pipeline07:31
*** SergeyLukjanov has joined #openstack-metering07:32
llusileht, ok, i'll change the severity to INFO for NotImplementedError07:32
llusileht: that idea is from jd__07:33
*** shardy has joined #openstack-metering07:33
*** SergeyLukjanov has quit IRC07:33
*** SergeyLukjanov has joined #openstack-metering07:36
llujd__: about the devstack patch to have mysql as default DB. Is it ok even if sqlalchemy doesn't support metadata query?07:39
lluoops, I've already asked. Jammed head.07:39
*** SergeyLukjanov has quit IRC07:51
*** eglynn has quit IRC07:55
*** SergeyLukjanov has joined #openstack-metering07:58
*** SergeyLukjanov has quit IRC07:59
openstackgerritLianhao Lu proposed a change to openstack/ceilometer: Added pollsters for the hardware agent  https://review.openstack.org/4307408:00
jd__hi08:09
*** eglynn has joined #openstack-metering08:25
*** SergeyLukjanov has joined #openstack-metering08:27
*** SergeyLukjanov has quit IRC08:54
*** evanjfraser has joined #openstack-metering08:59
*** evanjfraser has quit IRC09:07
openstackgerritJulien Danjou proposed a change to openstack/ceilometer: Import middleware from Oslo  https://review.openstack.org/4424709:13
openstackgerritJulien Danjou proposed a change to openstack/ceilometer: alarm: generate alarm_id in API  https://review.openstack.org/4406509:13
*** flwang has quit IRC09:17
openstackgerritA change was merged to openstack/ceilometer: Adds else and TODO in statistics storage tests  https://review.openstack.org/4399309:18
*** evanjfraser has joined #openstack-metering09:33
*** flwang has joined #openstack-metering09:43
*** evanjfraser has quit IRC09:49
openstackgerritFei Long Wang proposed a change to openstack/ceilometer: Fix empty metadata issue of instance  https://review.openstack.org/4181809:54
openstackgerritA change was merged to openstack/ceilometer: Import middleware from Oslo  https://review.openstack.org/4424710:50
*** yolanda has quit IRC11:36
*** yolanda has joined #openstack-metering11:38
openstackgerritFei Long Wang proposed a change to openstack/ceilometer: Fix empty metadata issue of instance  https://review.openstack.org/4181811:38
*** thomasm has joined #openstack-metering11:59
thomasmHey all!12:02
*** SergeyLukjanov has joined #openstack-metering12:15
openstackgerritThomas Maddox proposed a change to openstack/ceilometer: Addresses the latest resource metadata not being returned in the MongoDB, SQLAlchemy, and HBase drivers. The DB2 driver appears to be lacking support for grouping on the meter collection, so that was written up for someone more familiar with the DB2 NoSQL  https://review.openstack.org/4427712:19
*** SergeyLukjanov has quit IRC12:20
thomasmAhhh? didn't realize it wouldn't wrap my text on the site. I apologize in advance. :(12:21
thomasmjd__: Review up for the metadata bug fix: https://review.openstack.org/#/c/44277/12:24
thomasmAnyone I ought to add specifically?12:24
*** Ruetobas has joined #openstack-metering12:29
*** jergerber has joined #openstack-metering12:30
openstackgerritThomas Maddox proposed a change to openstack/ceilometer: Fix to return latest resource metadata  https://review.openstack.org/4427712:36
openstackgerritThomas Maddox proposed a change to openstack/ceilometer: Fix to return latest resource metadata  https://review.openstack.org/4427712:40
*** Ruetobas has quit IRC12:42
*** sandywalsh has quit IRC12:46
openstackgerritFengqian.gao proposed a change to openstack/ceilometer: Add a fake UUID to Meter database model named meter_id  https://review.openstack.org/4427812:46
openstackgerritFengqian.gao proposed a change to openstack/ceilometer: Add pagination parameter to the database backends of storage  https://review.openstack.org/4258212:46
openstackgerritFengqian.gao proposed a change to openstack/ceilometer: Add pagination support to selected APIs  https://review.openstack.org/3745412:46
openstackgerritFengqian.gao proposed a change to openstack/ceilometer: Change pagination query method in mongodb  https://review.openstack.org/4186912:46
*** Ruetobas has joined #openstack-metering12:49
*** anteaya has joined #openstack-metering12:51
*** fnaval_ has quit IRC12:54
*** fnaval_ has joined #openstack-metering12:55
*** shanewang has joined #openstack-metering12:56
*** shanewang has left #openstack-metering12:56
*** fnaval_ has quit IRC12:59
*** bpokorny has joined #openstack-metering13:01
*** sandywalsh has joined #openstack-metering13:01
*** flwang has left #openstack-metering13:03
*** gordc has joined #openstack-metering13:21
*** fnaval_ has joined #openstack-metering13:21
*** changbl has quit IRC13:43
*** herndon has joined #openstack-metering13:49
*** herndon has quit IRC13:52
*** janisg has quit IRC14:19
openstackgerritJulien Danjou proposed a change to openstack/ceilometer: alarm api: rename counter_name to meter_name  https://review.openstack.org/4429214:20
openstackgerritJulien Danjou proposed a change to openstack/ceilometer: alarm: generate alarm_id in API  https://review.openstack.org/4406514:20
*** flwang has joined #openstack-metering14:21
flwangjd__: ping14:23
jd__ah caught!14:23
jd__flwang: pong14:23
flwangjd__: lol, could you please revisit my patch https://review.openstack.org/#/c/41818/ ? it had been approved by you14:24
jd__sure14:24
jd__don't worry I review twice a day14:24
flwangjd__: cool, you're the super man14:24
*** herndon has joined #openstack-metering14:26
flwangdhellmann_: ping14:26
*** herndon has quit IRC14:29
*** dhellmann_ is now known as dhellmann14:29
dhellmannflwang: pong14:29
dhellmannjd__: I'm starting to worry about the storage drivers drifting apart feature wise. sandywalsh's change to reject repeated events made me think maybe we should be tracking those differences as bugs. What do you think?14:30
*** janisg has joined #openstack-metering14:30
jd__that sounds fair to me14:31
flwangI'm running a weird issue, for resource show, if I specified a non-existed id and set the CM debug level as False, CM will return 500 instead of 40014:31
flwangany thought?14:31
sandywalshdhellmann, we were talking about that internally yesterday too. thomasm has a bug fix that's pulling him into the hbase code and that's not our wheelhouse.14:31
dhellmannjd__: we ask devs who make inconsistent changes to open the bugs? or expect maintainers to keep up?14:31
jd__flwang: bug?14:31
jd__dhellmann: I expect maintainer to keep up14:31
dhellmannsandywalsh: yeah, I don't think it's fair to expect everyone to be able to update all the drivers14:31
jd__dhellmann: I don't think adding burden on developers about DB2 and HBase is likely to help14:31
jd__nor fair14:32
jd__and I don't want to drive down the development because of that neither14:32
dhellmannflwang: it sounds like something is causing an exception with that configuration14:32
sandywalshthe problem he was running into was the tests were failing under hbase, so he had to do something.14:32
*** alexb_ has joined #openstack-metering14:32
dhellmannjd__: but as a deployer, how do *I* know which features are in which driver?14:32
jd__dhellmann: we should document it14:32
sandywalshif there was some way to say "don't run this test under <hbase>" that would be awesome14:32
dhellmannjd__: right, and who is "we"? that's why I was saying the dev should open a bug14:33
jd__dhellmann: documenting drivers features could be a blocker for Havana if you ask me14:33
dhellmannfor example, maybe sandywalsh could open bugs against the other drivers for this new feature14:33
sandywalshdhellmann, sure thing14:33
jd__dhellmann: well I can write documentation if I'm forced too14:33
dhellmannhaha14:33
dhellmannthanks, sandywalsh14:33
thomasmsandywalsh, dhellmann, jd__: We can just break out the Mixin that tells the DB scenarios to run on all backends and just mix in the ones we need for each set of tests?14:33
dhellmannthomasm: yeah, exactly14:33
jd__what problem does that solve?14:34
dhellmannit avoids failing tests for a feature that is not in all drivers14:34
thomasmdhellmann, sandywalsh, jd__: The ultimate problem is that all of the drivers don't support the features we are advertising.14:34
jd__dhellmann: we already skip on NotImplementedError14:34
dhellmannoh, ok14:34
thomasmdhellmann, sandywalsh, jd__: Because we didn't have full testing around the required features, things like ordering weren't being supported.14:34
jd__that was I was asking which problem you thought it would fix14:34
dhellmannI didn't realize we did that14:35
jd__I wish that could extract us automatic documentation14:35
jd__but for the time being I can write it manually14:35
sandywalshbut in this case, it was implemented and started failing once the semantics of the feature changed.14:35
thomasmdhellmann, sandywalsh, jd__: So, if we are going to allow drivers to exist that aren't full-featured with the most used ones, then we have to work around it.14:35
*** alexb_ has quit IRC14:35
jd__thomasm: we already do that a lot I think14:35
thomasmjd__, Yep, and the reason I started making changes to the other drivers was because I wanted that to stop.14:36
thomasmheh14:36
jd__what changes are you talking about?14:36
thomasmjd__, https://review.openstack.org/#/c/44277/14:36
flwangdhellmann: http://paste.openstack.org/show/45378/14:37
thomasmThe driver is supposed to return filtered resources with the latest attributes from that filtering14:37
thomasmHBase couldn't support that because it wasn't storing historical metadata14:37
dragondmI think it's more a case of "I need to fix an issue with db backends X, Y, Z, and I know nothing about backends Q and Z, I need a way to merge my tests for the first ones and not run the test on the last two til' someone who knows about it can fix those"14:37
thomasmDB2 doesn't support that because it uses the resource collection which doesn't have historical metadata14:37
flwangyou can just set the Debug as False, and then query a non-existed resource14:38
jd__thomasm: in this case you've 2 options, the better being try to do thinsg in Python, the other one being raise NotImplementedError and that's it14:38
flwangdhellmann: recreate steps14:38
jd__thomasm: and ping the DB2/HBase authors so that they may be able to help eventually14:39
thomasmdhellmann, jd__, sandywalsh: If we're okay with some drivers falling behind like that, then we would have to go a work around, like dragondm mentioned.14:39
thomasmjd__, How can I do that when the fundamental purpose of that function is flawed?14:39
jd__thomasm: you raise at the start of the method?14:39
dhellmanndragondm: I think the NotImplementedError solution is nice and explicit, and handles the tests, too14:39
thomasmjd__, Oh, you mean just for the get_resources function just raise that?14:40
jd__the question boils down to "is it better to ship not working drivers or bugged drivers?"14:40
thomasmjd__, Exactly, yeah.14:40
dhellmannthomasm: well, I don't *like* it but I really don't see a way to avoid them drifting apart14:40
thomasmdhellmann, haha, yeah :(14:40
jd__if we ship non working driver we have a chance that people come up and fixes it, if we release bugged drivers with no test, nobody's going to notice14:40
dhellmannjd__: bugs should be fixed, but "not feature complete" seems a reasonable compromise14:40
jd__dhellmann: well, question is how do you fix a bug if you don't know/have HBase/DB2?14:41
*** alexb_ has joined #openstack-metering14:42
thomasmjd__, I can see the bug in the code anyway. The problem is the one reference those two drivers have to the metadata isn't an honest source anyway. It's completely dependent on your architecture and the nature of network comms.14:42
jd__I've opened a bug for doc https://bugs.launchpad.net/ceilometer/+bug/121841914:42
thomasmdhellmann, sandywalsh ^^14:42
thomasmdragondm, ^^14:42
jd__thomasm: well the test case is the same for all drivers anyway, right?14:43
thomasmjd__, Yeah, it stores the messages out of order, and all drivers would have failed that. I fixed SQLAlchemy and MongoDB without a schema change, HBase wasn't storing historical so that would fail anyway.14:43
thomasmThat's why I changed HBase to start storing historical metadata14:44
thomasmalong with the other historical attributes in the samples14:44
*** alexb_ has quit IRC14:44
dhellmannjd__: well, bugs should be fixed by the team, not every individual developer14:45
dhellmannjd__: I meant we should try to avoid releasing stuff we know is buggy, but if it's just not complete I think we have to live with and document that case14:45
jd__thomasm: cool then14:45
dhellmannthomasm: yeah, that sounds like the way to fix it14:46
jd__dhellmann: well I think we agree, it's just that sometimes you can't fix the bugs14:46
dhellmannjd__: hence "try" :-)14:46
*** changbl has joined #openstack-metering14:47
jd__:-)14:47
thomasmjd__, dhellmann, I'd never really worked with any of these before (SQLAlchemy, PyMongo, HappyBase, etc?). So, I just did what made sense to me, and the DB2 stuff, according to your comment, jd__, was missing some features that were really necessary to fix the bug.14:47
thomasmjd__, dhellmann: So, I chatted with gordc and we got it written up and sent to some folks who knew far more about it than me.14:47
thomasmSo? should I err on the side of raising the NotImplementedError, then?14:49
thomasmI can make that change14:49
thomasmAnd push up a new patch set without a mixin change14:49
jd__I don't know, dhellmann says the solution is to "try" :)14:49
*** alexb_ has joined #openstack-metering14:49
thomasmOh, try to fix the DB2 stuff?14:49
jd__but my call is raising NotImplementedCorrectly14:49
jd__:-)14:49
jd__thomasm: yes14:50
thomasmI had a few go's at it. Hmmm, do you know of any documentation on what is supported by PyMongo for DB2 NoSQL?14:50
thomasmjd__, dhellmann ^^14:50
thomasmI've had a hell of a time trying to find any14:51
gordcthomasm: i've passed on the bug to litong, regarding documentation you'll be hardpressed to find it... it's a very very new feature db2 is working on.14:52
thomasmgordc, Cool. I'll follow up there. =]14:54
*** shakayumi has joined #openstack-metering14:54
gordcthomasm: is it blocking you or can you bypass it by just raising a notimplemented?14:55
*** litong has joined #openstack-metering14:55
dhellmannthomasm: yeah, raise NotImplemented in cases where you can detect that something needs to be added to the driver14:57
thomasmgordc, dhellmann: Okay, awesome. Thanks for the help! =]14:57
dhellmannthomasm: unfortunately I don't know anything about the mongo stuff in db2 -- that was a surprise to me14:57
thomasmgordc, Nope, not blocking, then.14:57
thomasmdhellmann, haha me too14:57
litong@dhellmann, @thomasm,14:59
litongI think you are adding more test cases to the base, right?14:59
thomasmlitong, yep14:59
litongdb2 test cases basically inherit from all the base test cases.14:59
thomasmlitong, Yeah, so it fails these tests15:00
litongthe easy way is to add a new empty test cases in test_impl_db2.py to simply pass.15:00
openstackgerritTerri Yu proposed a change to openstack/ceilometer: Add group by statistics tests in API v2 tests  https://review.openstack.org/4413015:00
litongthe other way is that I can look at the sorting, and make sure that the sorting is implemented in db2 get_sample.15:00
litongI think that is where the problem is.15:00
thomasmlitong, I think the concern there was the lack of documentation, whereas raising NotImplemented is a little more noisy to motivate people.15:01
thomasmIt was get_resources that wasn't sorted - I didn't look at the others.15:01
thomasmmessages out of order cause undefined behavior when pulling metadata.15:01
thomasmfor a resource15:01
litongso it is sorted by timestamp?15:02
thomasmIt needs to be, yeah.15:02
thomasmBut it's not, because it just goes to the latest representation in the resource collection - which doesn't take the timestamp filtering into account for resource metadata at that time.15:03
litongI am looking at it now. get_resources method for db2 and mongo are the same, I do not think there is difference15:03
litongthere is no difference, sorry15:03
thomasmMongo uses the meter collection, DB2 uses the resource collection15:04
litongin get_resources method?15:04
thomasmmongo aggregates on the meter collection, db2 filters down and gets distinct resource_ids then pulls those from the resource collection15:04
thomasmyeah15:04
litongthat must be recent changes I suspect15:05
thomasmlitong, https://github.com/openstack/ceilometer/blob/master/ceilometer/storage/impl_db2.py#L341-L41415:05
litongdb2 driver was mostly copied from mongo driver with changes that specific to db2.15:05
litongmy env is rebuilding now, this is my top priority.15:05
thomasmlitong, Okay =]15:06
litongonce I have it, I will check, I do not think it is hard to figure out what went wrong.15:06
thomasmlitong, Thanks so much!15:06
litong@thomasm, thanks,15:06
litong@thomasm, I will make changes now, I believe that method in mongo impl recently changed to aggregate.15:09
litongthe problem with aggregate is that it does not support multiple partitions or sharding, I do not know if anybody was aware of that.15:10
dragondmyup, it was a few weeks agon15:10
dragondm(see: https://review.openstack.org/#/c/35297/)15:15
dragondmlitong ^15:15
litong@dragondm, yeah, saw that now. was not aware. but do you know aggregate actually has problem with partitioned mongodb?15:17
litong@dragondm, I think that the document says it won't support that.15:17
*** alexb_ has quit IRC15:18
dragondmDidn't know that. I'm guessing Julien didn't either.15:18
thomasmHmmm interesting15:22
thomasmlitong, so then we should probably just do the sort in the query and then do the min/max on our own?15:24
thomasmi.e. in the Python15:25
litong@thomasm, I am not sure, probably need some discussion, did you see the doc regarding the restriction?15:25
*** shaneduan[afk] is now known as shaneduan15:25
litong@thomasm, just wanted to make sure we are on the same page.15:26
thomasmlitong, The one that jd__ put in?15:26
litong@thomasm, I was talking about the aggregate restriction on mongodb.15:26
thomasmlitong, No, I haven't seen that one15:26
litong@thomasm, hold on, let me get a link15:27
thomasmlitong, thanks!15:27
litonghttp://docs.mongodb.org/manual/core/aggregation-pipeline-sharded-collections/15:31
litong@thomasm, I may have seen older docs.15:31
litongthat links says it does support sharded collections.15:31
litong@thomasm, http://docs.mongodb.org/manual/core/aggregation-pipeline-limits/15:32
thomasmlitong, So the limitations are more hardware based?15:33
litonglooks like it.15:34
litongfrom that doc, seems we are ok.15:34
thomasmlitong, yeah. I wonder if we ought to profile that a bit, though. Just to be sure we don't penalize people beyond reason, haha.15:34
litongif I found other docs on this, I will contact you . Somewhere I remember I read something about the restrictions of using aggregate method.15:34
thomasmNot sure what beyond reason would be15:34
thomasmlitong, Okay. Thanks! =]15:35
litong@thomasm, compare map_reduce and aggregate is not always easy.15:35
thomasmYeah15:35
silehtthomasm, litong to get what works or not in each backend you can look for skipped test in the testr result file15:40
dragondmOf course, there are other issues there as well. AFAIK, ceilometer doesn't specify a shard key on any of it's collections.15:40
silehtin more than 90% the reason is NotImplementedError15:40
thomasmdragondm, none that I saw15:40
silehtdragondm, I'm not sure that ceilometer should be aware of the shard key15:48
openstackgerritA change was merged to openstack/ceilometer: alarm: generate alarm_id in API  https://review.openstack.org/4406515:50
terriyusileht: where's the testr result file?15:53
silehtterriyu, for example: http://logs.openstack.org/47/44247/1/gate/gate-ceilometer-python26/3109bf1/testr_results.html.gz15:53
silehtterriyu, you need to export some env variables to  generate it locally15:54
silehtie: NOSE_WITH_XUNIT=1 NOSE_WITH_HTML_OUTPUT=1 NOSE_HTML_OUT_FILE=nose_results.html15:54
terriyusileht: I thought we don't use nose anymore?15:54
*** changbl has quit IRC15:55
silehtterriyu, correct, perhaps they are some compatibility15:55
jd__probably indeed :)15:56
terriyusileht: I was interested because I wanted to see the skipped tests15:56
terriyuI asked jd__  this question recently :)15:56
silehtterriyu, on gate look on the py26 not py27 because all mongo tests are skipped in py2715:57
terriyusileht: uhh, all the mongo tests are skipped?? Isn't that bad?15:57
silehtjd__, we will have a issue soon (very soon) with the one mongo db connection per test15:57
silehtterriyu, nop because it run on py2615:58
jd__sileht: ?15:59
silehtjd__, when I have enabled testscenario (and enabled tests for db2), I have grow the number of max connections to 12815:59
silehtbut according the last pagination changeset, this is not enough http://logs.openstack.org/54/37454/18/check/gate-ceilometer-python26/ec57492/console.html15:59
silehtbecause the patch add many new tests15:59
jd__that's caused by DB2 right?16:00
terriyujd__: hmm, maybe this is related to my MongoDB connection failure problems??16:01
silehtdb2 have x2 the number of connections needed16:01
jd__terriyu: it looks like it16:01
silehtjd__, terriyu I was having this issue in the past and I have just increase the maxConns of mongod16:01
jd__but I saw you raised it but that I think that's because DB2 don't have a pooling mechanism16:01
terriyusileht: how do you increase the max number of connections?16:02
silehtDB2 use a mongod database in reality16:02
silehtjd__, ^16:02
jd__sileht: I know that but it doesn't use the pooling we built in impl_mongodb16:02
silehtterriyu, is run-test.sh16:02
jd__sileht: unless I missed it :)16:02
silehtjd__, I have not checking this point16:02
silehtjd__, it seems use pool too16:03
terriyusileht: thanks!16:03
jd__sileht: *(#@16:04
jd__je donne ma langue au chat16:04
silehtif you take a look on http://logs.openstack.org/47/44247/1/gate/gate-ceilometer-python27/94a7aaa/testr_results.html.gz16:05
silehtyou will see that 795 tests have been skipped16:05
silehtonly 180 in py2616:05
silehtso we can have ~600 tests running in the same times16:06
silehteach tests use his own database16:06
silehta new database create a new item in the pool and a new connection16:06
terriyusileht, jd__ : when I raise my max connections from 128 --> 256, then the test suite passes16:06
jd__terriyu: that fits what's sileht's saying16:06
terriyuI still get the message "No module named deprecated"16:06
jd__-'s16:07
* jd__ grumbles16:07
silehtI don't know this module :p16:07
terriyuNo module named give_me_more_connections_me_hungry16:08
silehtjd__, do you kown if infra will be happy with our way to run tests ?16:09
*** janisg has quit IRC16:11
jd__sileht: the maxConns was here because infra had a limit on the number of processes or something, and therefore mongodb exploded16:11
jd__so I set it very low (32) to be sure we don't break it on CI16:12
jd__I was already suprised 128 was OK on CI16:12
silehtjd__, perhaps we needs to limit the concurrency in testr16:12
*** changbl has joined #openstack-metering16:12
jd__sileht: what about we pool on host:port rather than the full URL?16:13
jd__the problem is that pymongo doesn't close the connection16:13
silehtjd__, it works too16:15
jd__what's your bug number terriyu?16:17
silehtjd__, ok I will propose something for that I prefer your method16:17
jd__sileht: well I think it'll be better and will work :)16:17
*** shaneduan is now known as shaneduan[afk]16:18
*** dina_belova has joined #openstack-metering16:22
terriyujd__: oh, I didn't post it yet16:23
*** shaneduan[afk] is now known as shaneduan16:23
terriyujd__: hold on16:24
jd__terriyu: ok, sileht will need it to include in its fix16:24
* sileht needs to upgrade its .tox dir sniff16:26
*** SergeyLukjanov has joined #openstack-metering16:26
terriyujd__ sileht : https://bugs.launchpad.net/ceilometer/+bug/121848816:30
silehtjd__, it does works because the we cache the MongoClient object that connect to the db not only to mongod instance16:34
silehtjd__, forget16:35
*** herndon has joined #openstack-metering16:36
herndonsandywalsh: ping16:38
*** shakayumi has quit IRC16:45
*** dina_belova has quit IRC16:54
*** dina_belova has joined #openstack-metering16:55
*** dina_belova has quit IRC16:59
sandywalshherndon, howdy17:31
herndonhey there17:34
herndonjust wanted to chat about your patch since there have been a few back and forths17:35
*** eglynn has quit IRC17:35
herndonIs message_id a key name that is more universal than I am aware of?17:36
herndonHave to admit, I have not been tracking the notification work that closely :(17:36
sandywalshnothing other than it's the name in the notification17:38
sandywalshthe event.id vs. event_id thing is my biggest twitch (but I'm not hung up on it)17:39
*** Bada has joined #openstack-metering17:39
sandywalshmy spidey senses are saying that'll cause confusion down the road17:40
BadaHi guys, does anybody knows what this mean : [-] Could not load 'accumulator': pbr>=0.5.21,<1.0 ?17:40
sandywalshBada, check that you've got the proper version of pbr installed17:41
sandywalshBada, is this under devstack?17:42
Badasandywalsh not it's not17:42
Badasandywalsh what is pbr ?17:42
sandywalshBada, is a central library to other openstack components (Python Build Reasonableness or something)17:43
sandywalshpip install -U pbr17:43
Badayeah found it https://github.com/openstack-dev/pbr17:43
herndonsandywalsh, message_id it is then.17:43
Badasandywalsh, it works !17:45
Bada sandywalsh, brilliant many thanks17:45
herndonhm, although it may cause confusion in the api when the query for event id looks up message_id. Maybe the event api should change?17:45
herndonor the api should look at event.is, but I think that is less useful than message_id17:46
herndons/event.is/event.id17:46
sandywalshBada, np17:48
sandywalshherndon, can we change it in the api?17:49
sandywalshhmm, but I see your point17:49
herndonseems like offloading the confusion to the consumer of the api17:49
sandywalshit's kind of klunky to ask for event_id and map that to message_id17:49
herndonyeah.17:50
sandywalshwell, the caller would only see event_id17:50
herndonignore my previous comment17:50
sandywalshshall we live with message_id and see how it feels? If it's a real sticky point, I'll change it.17:52
*** SergeyLukjanov has quit IRC17:52
*** shakayumi has joined #openstack-metering17:52
*** SergeyLukjanov has joined #openstack-metering17:53
herndonYeah, let's do that. I already did the event_id -> message_id conversion in one patch. I really like that you've moved it into event, that feels a lot better than querying traits to lookup the id of an event.17:53
sandywalshcool ... k, stay tuned. Thanks for the feedback!17:53
*** dina_belova has joined #openstack-metering17:53
gordcsileht: are we waiting for something before we approve this: https://review.openstack.org/#/c/43848? just want to know so i don't superseded something.17:56
silehtgordc, I have missing the Approved button !17:57
gordcsileht: cool. i'll approve... unless you'd like to. :)17:57
silehtgordc, ok, I'm not with my computer actually17:58
gordcsileht: done, carry on with your evening :)18:00
*** dina_belova has quit IRC18:03
*** dina_belova has joined #openstack-metering18:04
*** thomasm has quit IRC18:05
silehtgordc, thanks18:06
*** shakayumi has quit IRC18:08
*** dina_belova has quit IRC18:08
*** Bada has quit IRC18:15
*** dina_belova has joined #openstack-metering18:24
*** thomasm has joined #openstack-metering18:38
*** herndon has quit IRC18:43
*** dina_belova has quit IRC18:51
*** dina_belova has joined #openstack-metering18:52
*** dina_belova has quit IRC18:57
*** yolanda has quit IRC18:58
*** boris-42 has quit IRC19:03
*** alexb_ has joined #openstack-metering19:07
*** eglynn has joined #openstack-metering19:17
*** boris-42 has joined #openstack-metering19:32
*** SergeyLukjanov has quit IRC19:32
*** alexb_ has quit IRC19:38
*** alexb_ has joined #openstack-metering19:40
*** SergeyLukjanov has joined #openstack-metering19:41
*** SergeyLukjanov has quit IRC19:59
*** dina_belova has joined #openstack-metering20:02
*** dina_belova has quit IRC20:07
*** boris-42 has quit IRC20:09
openstackgerritEoghan Glynn proposed a change to openstack/ceilometer: Base Alarm history persistence model  https://review.openstack.org/4384820:15
openstackgerritEoghan Glynn proposed a change to openstack/ceilometer: Plug alarm history logic into the API  https://review.openstack.org/4384920:15
openstackgerritEoghan Glynn proposed a change to openstack/ceilometer: Alarm history storage implementation for mongodb  https://review.openstack.org/4385020:15
*** sandywalsh has quit IRC20:23
*** sandywalsh has joined #openstack-metering20:35
*** eglynn has quit IRC20:48
openstackgerritThomas Maddox proposed a change to openstack/ceilometer: Fix to return latest resource metadata  https://review.openstack.org/4427720:50
*** shaneduan is now known as shaneduan[afk]20:58
*** evanjfraser has joined #openstack-metering21:01
*** eglynn has joined #openstack-metering21:02
*** dina_belova has joined #openstack-metering21:03
*** dina_belova has quit IRC21:08
*** shaneduan[afk] is now known as shaneduan21:17
*** shanewang has joined #openstack-metering21:26
*** shanewang has left #openstack-metering21:26
*** shaneduan is now known as shaneduan[afk]21:29
*** alexb_ has quit IRC21:31
*** litong has quit IRC21:41
openstackgerritSandy Walsh proposed a change to openstack/ceilometer: Reject duplicate events  https://review.openstack.org/4419121:49
*** dina_belova has joined #openstack-metering22:03
*** dina_belova has quit IRC22:08
*** alexb_ has joined #openstack-metering22:10
*** bpokorny has quit IRC22:24
*** changbl has quit IRC22:26
*** eglynn has quit IRC22:31
*** litong has joined #openstack-metering22:33
*** evanjfraser has quit IRC22:36
*** thomasm has quit IRC22:48
*** gordc has quit IRC22:54
*** dina_belova has joined #openstack-metering23:04
*** dina_belova has quit IRC23:09
*** shaneduan[afk] is now known as shaneduan23:29
*** evanjfraser has joined #openstack-metering23:31
*** evanjfraser has quit IRC23:54

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!