Thursday, 2015-05-14

*** IanGovett has quit IRC00:16
*** ashleighfarnham has quit IRC00:23
*** ashleighfarnham has joined #openstack-trove00:23
*** ashleighfarnham has quit IRC00:28
*** amrith is now known as _amrith_00:45
*** _amrith_ is now known as amrith00:50
*** exploreshaifali has quit IRC01:06
openstackgerritPeter Stachowski proposed openstack/trove-specs: Add backup and restore to the Redis datastore  https://review.openstack.org/18291001:14
*** erkules_ has joined #openstack-trove01:22
*** erkules has quit IRC01:25
*** Longgeek has quit IRC01:38
amrithsharikapongubala, sorry I just saw this. maybe we can chat in the morning. I agree with SlickNik's comment from 1730. if there's an element which handles the variable (datastore independent) I would be fine with one variable. It could decide what to do; for a file, for a directory, for a URL.02:02
*** eghobo has quit IRC02:16
*** Longgeek has joined #openstack-trove02:28
*** Longgeek has quit IRC02:41
*** Longgeek_ has joined #openstack-trove02:41
*** bhunter71 has quit IRC02:53
*** Longgeek_ has quit IRC03:04
*** Longgeek has joined #openstack-trove03:06
*** sgotliv has joined #openstack-trove03:26
*** sgotliv has quit IRC03:31
*** coolsvap|afk is now known as coolsvap03:42
*** sgotliv has joined #openstack-trove03:46
*** Longgeek has quit IRC03:50
*** Longgeek has joined #openstack-trove03:55
*** Longgeek has quit IRC04:00
*** eghobo has joined #openstack-trove04:04
*** eghobo_ has joined #openstack-trove04:07
*** eghobo has quit IRC04:10
*** eghobo has joined #openstack-trove04:39
*** eghobo_ has quit IRC04:40
*** Longgeek has joined #openstack-trove04:57
*** WonChon has quit IRC04:59
*** WonChon has joined #openstack-trove05:02
*** Longgeek has quit IRC05:08
*** Longgeek has joined #openstack-trove06:05
*** masco has joined #openstack-trove06:05
*** Longgeek has quit IRC06:22
*** WonChon has quit IRC06:29
*** WonChon has joined #openstack-trove06:33
*** eghobo has quit IRC06:40
*** john_f_ has quit IRC07:40
*** john_f_ has joined #openstack-trove07:41
*** Longgeek has joined #openstack-trove07:49
*** k4n0 has joined #openstack-trove07:51
*** Longgeek has quit IRC08:00
*** links has joined #openstack-trove08:02
*** exploreshaifali has joined #openstack-trove08:18
openstackgerritMerged openstack/python-troveclient: Updated coverage related options to project  https://review.openstack.org/18136509:27
*** Longgeek has joined #openstack-trove09:36
*** tosky has joined #openstack-trove09:38
*** Longgeek has quit IRC09:44
*** IanGovett has joined #openstack-trove09:46
*** haomaiwang has joined #openstack-trove10:42
*** haomaiwa_ has joined #openstack-trove10:45
*** haomaiwang has quit IRC10:45
openstackgerritSushil Kumar proposed openstack/trove: Use datastore specific timeouts if they exists  https://review.openstack.org/16464010:58
*** haomaiwa_ has quit IRC11:15
*** Longgeek has joined #openstack-trove11:29
*** chlong has joined #openstack-trove11:48
*** Longgeek has quit IRC12:01
*** exploreshaifali has quit IRC12:04
*** pmackinn has joined #openstack-trove12:07
openstackgerritSushil Kumar proposed openstack/trove: Use datastore specific timeouts if they exists  https://review.openstack.org/16464012:15
*** coolsvap is now known as coolsvap|afk12:22
*** bhunter71 has joined #openstack-trove12:29
*** masco has quit IRC12:32
openstackgerritSushil Kumar proposed openstack/python-troveclient: Added more unit-tests for troveclient/client.py  https://review.openstack.org/18277112:51
*** radez_g0n3 is now known as radez12:59
openstackgerritMerged openstack/trove: Update modules to turn on dangling mock detection  https://review.openstack.org/18075713:06
*** Longgeek has joined #openstack-trove13:15
*** masco has joined #openstack-trove13:19
*** bhunter71 has quit IRC13:25
*** IanGovett has quit IRC13:25
*** IanGovett has joined #openstack-trove13:26
*** IanGovett1 has joined #openstack-trove13:40
*** IanGovett has quit IRC13:43
*** Longgeek has quit IRC13:48
openstackgerritSushil Kumar proposed openstack/trove: Added more unit-tests to Vertica-Cluster-Strategy  https://review.openstack.org/17823614:10
*** masco has quit IRC14:20
*** k4n0 has quit IRC14:26
*** shakamunyi has joined #openstack-trove14:29
*** shayneburgess_ has quit IRC14:37
*** jodah has quit IRC14:37
*** jodah has joined #openstack-trove14:39
openstackgerritSushil Kumar proposed openstack/trove: Fix leaked mocks in the 'guestagent/test_api' module  https://review.openstack.org/18306714:41
*** shayneburgess_ has joined #openstack-trove14:41
*** sriram_tesora has joined #openstack-trove14:42
*** barra204 has joined #openstack-trove14:43
*** bhunter71 has joined #openstack-trove14:45
*** Longgeek has joined #openstack-trove14:45
*** pmackinn_ has joined #openstack-trove15:00
*** pmackinn has quit IRC15:04
*** Longgeek has quit IRC15:04
*** Longgeek_ has joined #openstack-trove15:05
*** Longgeek_ has quit IRC15:05
*** Longgeek has joined #openstack-trove15:05
*** erkules_ is now known as erkules15:20
*** erkules has joined #openstack-trove15:20
*** links has quit IRC15:24
peterstacSlickNik, quick question about the mock detector consolidation ...15:25
*** haomaiwang has joined #openstack-trove15:28
*** haomaiwang has quit IRC15:29
*** haomaiwang has joined #openstack-trove15:29
openstackgerritSushil Kumar proposed openstack/trove: Fixed the unmocked entry in taskmanager unit-tests  https://review.openstack.org/18308415:35
openstackgerritSushil Kumar proposed openstack/trove: Fix leaked mocks in the 'guestagent/test_api' module  https://review.openstack.org/18306715:43
*** amrith is now known as _amrith_15:59
*** pmackinn_ has quit IRC16:13
openstackgerritSushil Kumar proposed openstack/python-troveclient: Added more unit-tests for troveclient/client.py  https://review.openstack.org/18277116:15
openstackgerritSushil Kumar proposed openstack/python-troveclient: Added more unit-tests for troveclient/client.py  https://review.openstack.org/18277116:24
SlickNikpeterstac: Around? Just saw your note…16:25
peterstacSlickNik: Just wanted some clarification - I was in the middle of consolidating the mock stuff over the weekend when I noticed that you had already done it16:27
peterstacSo I abandoned my patchsets16:27
peterstacNow I notice patchsets going up just fixing one file again, so I'm confused ...16:27
*** shakamunyi has quit IRC16:27
*** barra204 has quit IRC16:28
peterstacWhat's our strategy going forward?  Are we still using the etherpad? https://etherpad.openstack.org/p/mock-leak-cleanup16:29
peterstacOr are we just fixing them only when we find an issue in a file?16:29
SlickNikI haven't had a chance to look into reviews since last evening, but I'd prefer them to be consolidated if they're just enabling the detector by changing the base class.16:30
SlickNikOtherwise we are just going to have a proliferation of patches.16:31
SlickNikAnd many commits with just 1/2 line changes for the same thing.16:31
sushilkmcan we have standalone bugfixes if it is more than just enabling the detector and actually fixes bad mocks16:32
peterstacso how do we keep track of what's done and what isn't?16:32
*** ashleighfarnham has joined #openstack-trove16:32
peterstacsushilkm: It will generate lots more patchsets that way - doing it file-by-file16:34
sushilkmi think bugfixes should still go in but if it is just enabling the detector they should be merged into one big patchset, it would also help in reviewing the fixes16:36
peterstacsushilkm, SlickNik: I'm ok doing it on a file-by-file basis (only if changes need to be made), just think it'll be hard to track when the work is done16:36
peterstacsushilkm, the problem is that you don't know if there are any fixes until you add the base class16:37
sushilkmas u can see in my current patchset once you are fixing the problematic mocked entry it could lead to some other problem somewhere like i faced in my case when i fixed guestagent/test_api it gave me problems in upgrade tests16:37
sushilkmwhich would otherwise seem totally unrelated16:37
sushilkmyes so one can add it and see if any bugfixes are there push it up, else keep it in separate big patchset16:38
peterstacSlickNik, sushilkm: ok, so I'll skip any files that just add the detector16:39
*** masco has joined #openstack-trove16:39
sushilkmand they can be put up separately as one big patchset in one go16:40
peterstacsure, as long as someone is keeping track of them16:40
sushilkm:)16:41
*** shayneburgess has quit IRC16:41
SlickNikFrankly, I'd prefer it all done as part of one patchset (you can still use the wiki to track whose doing what).16:41
peterstacSlickNik: you mean all the mock changes in one patchset?16:42
SlickNiks/wiki/etherpad16:42
vkmcthat sounds like a huge patchset16:42
vkmcharder to review and probably painful to be free of merge conflicts16:43
pmalik<SlickNik> My understanding is that all with change in just the base class go into a single patch set and the other ones are done by module. Is that what you mean?16:43
sushilkm+1 pmalik16:43
SlickNikvkmc: Yes, but so is something like https://review.openstack.org/#/c/182008, but it isn't that hard to review or merge.16:44
SlickNikjust big :)16:44
vkmcSlickNik, certainly16:44
SlickNikBut very mechanical16:45
pmalikHow can multiple ppl then work on that single patch set?16:45
SlickNikpmalik: Same way how multiple people work on single patchsets today.16:46
SlickNikBut I digress — I'm okay with the compromise I suggested earlier.16:46
pmalikThe point of doing stuff by module is that ppl working on it do not step on each other's toes.16:46
pmalikWhat compromise?16:47
SlickNikWhere we can eagerly fix / merge patchsets that actually have fixes to the mocks.16:47
SlickNikIf they aren't fixing anything, then lump them into a big change that enables the base class switch out16:48
pmalikThis is not as mechanical as reordering the imports. Keep in mind some files contain significant changes. You have to ensure they do not get overwritten by other ppl's changes.16:48
SlickNikIf the modules are different people will not step on each others' toes.16:48
SlickNikIf the modules are not different people will step on each others' toes regardless of whether it is one commit or multiple commits.16:48
*** eghobo has joined #openstack-trove16:49
SlickNikThe only thing that I see that's preventing folks from stepping on each others' toes is the etherpad, which you'd probably want to use in either case.16:50
pmalikNo, it's git and gerrit that issues a merge conflict.16:50
*** pmackinn_ has joined #openstack-trove16:51
SlickNikRight, if you were working on the same modules (which isn't the case here) git and gerrit would give you merge conflicts that you'd have to fix before pushing up your changes in either case.16:52
pmalikI still don't understand how you want to sync work from multiple ppl into a single patch set without using gerrit == having a separate commit/patch set for each module.16:52
pmalikAlso remember that that single huge patch set will then conflict with every other incoming patch set. Having separate patch sets for modules makes the merges and conflicts more granural16:55
*** masco has quit IRC16:57
SlickNikpmalik: It's not that hard to fix merge conflicts when a patch is ready to merge. We've merged patches that are bigger than this one before. Plus folks don't usually go fixing unit tests all over the place so merge conflicts should be minimal in this case.16:58
SlickNikYou should _not_ be changing trove code for this anyhow.16:58
pmalikAlso by having multiple ppl commiting into a single patch set you offload the whole conflict and merge management on them rather than having gerrit/git doing it. Keep in mind that those packages are not 100% independent. Some fixes end up requiring changes to other packages too. That's what I am trying to say. This is not as mechanical as with reordering imports (unless the only change is to the base class and there is n16:58
pmalikothing else to fix).16:58
SlickNikpmalik: if there are merge conflicts — a human has to resolve them in either case. Gerrit will only tell you that you have to do it.17:03
SlickNikAnd in this case if folks are working per module, there ideally shouldn't be merge conflicts.17:04
*** _crobertsrh is now known as crobertsrh17:09
pmalik<SlickNik> As can be seen from https://review.openstack.org/#/c/183067/ it's not always the case though... ;-)17:11
*** shayneburgess has joined #openstack-trove17:26
openstackgerritPeter Stachowski proposed openstack/trove: Added dangling mock detection to 'guestagent'  https://review.openstack.org/18082517:31
*** bhunter71 has quit IRC17:44
*** bhunter71 has joined #openstack-trove17:45
*** bhunter71 has quit IRC17:49
*** _amrith_ is now known as amrith17:50
*** bhunter71 has joined #openstack-trove17:51
*** _mattf is now known as mattf18:02
*** exploreshaifali has joined #openstack-trove18:14
*** sriram_tesora has quit IRC18:26
*** exploreshaifali has quit IRC18:30
*** IanGovett1 has quit IRC18:44
*** IanGovett has joined #openstack-trove18:51
vkmchey guys, is there an spec about clustering somewhere?18:51
SlickNikvkmc: About mysql clustering? Or about the API?18:52
vkmcabout how we implement clustering :)18:52
SlickNikpmalik / peterstac: I'm trying to understand why a lot of the mock detector tests change the order of imports — do you guys know why this is needed?18:52
openstackgerritMatthew Van Dijk proposed openstack/trove-specs: MongoDB database management commands  https://review.openstack.org/18316618:53
SlickNikvkmc: https://wiki.openstack.org/wiki/Trove/Replication-And-Clustering-With-Nodes-518:53
vkmcSlickNik, thanks!18:53
SlickNikThis is still in wiki format since it landed in Juno before we went to the rst specs format.18:54
peterstacSlickNik: I don't think I changed any import order, at least not intentionally (if so I'll revert it)18:54
vkmcyeah, its fine :) I checked the code but I was looking something more docs-ish18:55
SlickNikpeterstac: I don't care about import order :)  — just wanted to know if there's a reason we need to do this intentionally.18:55
peterstacSlickNik: no, not that I'm aware of :)18:56
SlickNiksounds good, thanks!18:57
pmalikI guess the import order is now better handled by https://review.openstack.org/#/c/181950/ (once it merges)18:58
*** IanGovett1 has joined #openstack-trove18:58
*** IanGovett has quit IRC19:01
openstackgerritPeter Stachowski proposed openstack/trove: Added dangling mock detection to 'guestagent'  https://review.openstack.org/18082519:01
*** jeraldv has joined #openstack-trove19:02
openstackgerritSaurabh Surana proposed openstack/trove: accepting network and availability zone for instances in cluster  https://review.openstack.org/17944319:07
*** eghobo has quit IRC19:41
*** radez is now known as radez_g0n319:49
*** openstackgerrit has quit IRC19:52
*** openstackgerrit has joined #openstack-trove19:52
*** amrith is now known as _amrith_20:13
vkmcguys, is there a roadmap?20:21
vkmcthe main wiki seems outdated20:21
*** bhunter71 has quit IRC20:23
openstackgerritPeter Stachowski proposed openstack/trove-specs: Trove Instance Metadata  https://review.openstack.org/17504220:25
*** eghobo has joined #openstack-trove20:27
*** georgelorch has quit IRC20:29
openstackgerritMayuri Ganguly proposed openstack/trove: Associate flavor types with datastore versions  https://review.openstack.org/10982420:30
*** JamesK has joined #openstack-trove20:32
*** mattf is now known as _mattf20:33
vkmcdougshelley66, pmalik, peterstac, do somebody know if we have an updated roadmap?20:34
*** JamesK has quit IRC20:34
dougshelley66vkmc, not that i know of. It was discussed at mid-cycle and a couple of folks took an action item to work towards one. How far out would you expect the roadmap to go?20:36
vkmchmm, at least L-1/L-2?20:37
dougshelley66i think the first Trove Work Session at summit is to talk about liberty blueprints20:47
dougshelley66which i assume would cover L-1 and L-220:47
vkmcok :)20:48
vkmcbeing so close of the summit20:48
vkmcI guess we could work on creating the roadmap for then20:48
vkmcI mean, after those sessions20:48
*** sgotliv has quit IRC20:53
*** JamesK has joined #openstack-trove20:54
*** georgelorch has joined #openstack-trove20:56
*** georgelorch has quit IRC21:06
*** haomaiwang has quit IRC21:08
*** chlong has quit IRC21:08
*** haomaiwa_ has joined #openstack-trove21:09
*** crobertsrh is now known as _crobertsrh21:13
*** openstackgerrit has quit IRC21:22
*** openstackgerrit has joined #openstack-trove21:22
*** sgotliv has joined #openstack-trove21:28
*** _amrith_ is now known as amrith22:02
*** eghobo has quit IRC22:09
*** eghobo has joined #openstack-trove22:10
*** bhunter71 has joined #openstack-trove22:11
*** georgelorch has joined #openstack-trove22:14
*** sgotliv has quit IRC22:30
*** tosky has quit IRC22:35
*** shakamunyi has joined #openstack-trove22:47
*** barra204 has joined #openstack-trove22:47
*** pmackinn_ has quit IRC23:00
*** ashleighfarnham has quit IRC23:00
*** pmackinn_ has joined #openstack-trove23:01
*** barra204 has quit IRC23:04
*** shakamunyi has quit IRC23:04
*** pmackinn_ has quit IRC23:05
*** ashleighfarnham has joined #openstack-trove23:07
*** chlong has joined #openstack-trove23:10
*** shakamunyi has joined #openstack-trove23:17
*** barra204 has joined #openstack-trove23:17
*** cp16net has quit IRC23:17
*** Longgeek has quit IRC23:30
*** Longgeek has joined #openstack-trove23:30
amrithSlickNik, yt?23:36
*** ashleighfarnham has quit IRC23:48
*** shayneburgess has quit IRC23:49
openstackgerritMayuri Ganguly proposed openstack/trove: Changing cluster status to none when instances are in error state  https://review.openstack.org/18335923:52

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