Thursday, 2015-12-10

*** sonali5 has joined #openstack-trove00:02
*** chlong has quit IRC00:09
*** ashleighfarnham has quit IRC00:12
*** sonali5 has quit IRC00:20
*** ianbrown has quit IRC00:25
*** ianbrown has joined #openstack-trove00:28
*** bhaskarduvvuri has quit IRC00:31
openstackgerritLuigi Toscano proposed openstack/trove: Use configured datastore on instance creation  https://review.openstack.org/25542800:50
openstackgerritLuigi Toscano proposed openstack/trove: Use a specific network for the test  https://review.openstack.org/25542900:50
*** chlong has joined #openstack-trove01:05
*** chlong has quit IRC01:23
*** imandhan has quit IRC01:24
*** ianbrown has quit IRC01:31
*** ianbrown has joined #openstack-trove01:31
*** ianbrown has quit IRC01:33
*** ianbrown has joined #openstack-trove01:33
*** ianbrown has quit IRC01:44
*** ianbrown has joined #openstack-trove01:44
*** caishan has joined #openstack-trove01:53
*** pmackinn has quit IRC02:00
*** rcernin has quit IRC02:01
*** ianbrown has quit IRC02:20
*** ianbrown has joined #openstack-trove02:21
*** ianbrown has quit IRC02:27
*** ianbrown has joined #openstack-trove02:28
*** links has joined #openstack-trove02:33
*** chlong has joined #openstack-trove02:44
*** ianbrown_ has joined #openstack-trove02:44
*** ianbrown has quit IRC02:45
*** ianbrown_ has quit IRC02:47
*** ianbrown_ has joined #openstack-trove02:47
*** _amrith_ is now known as amrith03:31
amrithvipul, hmm ... that name sounds familiar.03:32
*** imandhan has joined #openstack-trove03:49
*** imandhan has quit IRC04:19
*** ViswaV has quit IRC04:38
*** ianbrown_ has quit IRC04:38
*** ianbrown__ has joined #openstack-trove04:39
*** ViswaV has joined #openstack-trove04:42
*** ianbrown__ has quit IRC04:45
*** ianbrown__ has joined #openstack-trove04:45
*** sonali5 has joined #openstack-trove05:02
*** ashleighfarnham has joined #openstack-trove05:20
*** imandhan has joined #openstack-trove05:49
*** links has quit IRC06:01
*** links has joined #openstack-trove06:01
*** chlong has quit IRC06:28
*** sgotliv_ has joined #openstack-trove06:48
*** links has quit IRC06:49
*** chlong has joined #openstack-trove06:49
*** sonali5 has quit IRC07:00
*** ashleighfarnham has quit IRC07:01
*** chlong has quit IRC07:04
*** sonali5 has joined #openstack-trove07:04
*** links has joined #openstack-trove07:05
*** rcernin has joined #openstack-trove07:11
*** imandhan has quit IRC07:19
*** imandhan has joined #openstack-trove07:19
*** chlong has joined #openstack-trove07:20
*** haomaiwang has joined #openstack-trove07:23
*** imandhan has quit IRC07:24
*** haomai___ has joined #openstack-trove07:57
*** haomaiwang has quit IRC07:58
*** haomai___ has quit IRC08:01
*** haomaiwang has joined #openstack-trove08:01
*** ViswaV has quit IRC08:02
*** peterstac has quit IRC08:04
openstackgerritMerged openstack/trove: fix mongo create database  https://review.openstack.org/24659008:04
*** dloi_ has quit IRC08:04
*** dloi has joined #openstack-trove08:04
*** chlong has quit IRC08:05
*** bhunter has quit IRC08:05
*** krugg has quit IRC08:05
*** mvandijk has quit IRC08:05
*** amrith has quit IRC08:05
*** dougshelley66 has quit IRC08:05
*** sonali5 has quit IRC08:06
*** amrith has joined #openstack-trove08:10
*** bhunter has joined #openstack-trove08:11
*** peterstac has joined #openstack-trove08:11
*** dougshelley66 has joined #openstack-trove08:11
*** mvandijk has joined #openstack-trove08:12
*** krugg has joined #openstack-trove08:12
*** links has quit IRC08:14
*** haomaiwang has quit IRC08:45
*** haomaiwang has joined #openstack-trove08:50
*** links has joined #openstack-trove08:52
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-trove09:01
*** haomaiwang has quit IRC09:07
*** haomaiwang has joined #openstack-trove09:14
*** hogepodge has quit IRC09:26
*** hogepodge has joined #openstack-trove09:28
*** openstackgerrit has quit IRC09:32
*** openstackgerrit has joined #openstack-trove09:32
*** links has quit IRC09:42
*** links has joined #openstack-trove09:55
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-trove10:01
*** links has quit IRC10:04
*** k4n0 has joined #openstack-trove10:15
*** k4n0 has quit IRC10:15
*** links has joined #openstack-trove10:17
*** caishan has quit IRC10:38
*** ianbrown__ has quit IRC10:52
*** ianbrown__ has joined #openstack-trove10:52
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-trove11:01
*** ianbrown__ has quit IRC11:01
*** ianbrown__ has joined #openstack-trove11:02
*** tosky has joined #openstack-trove11:06
*** ianbrown__ has quit IRC11:11
*** ianbrown__ has joined #openstack-trove11:11
*** sonali5 has joined #openstack-trove11:23
*** haomaiwang has quit IRC12:01
*** haomaiwa_ has joined #openstack-trove12:01
*** sonali5 has quit IRC12:11
*** openstackgerrit has quit IRC12:47
*** openstackgerrit has joined #openstack-trove12:47
*** pmackinn has joined #openstack-trove12:54
*** swebb has quit IRC12:57
*** haomaiwa_ has quit IRC13:01
*** haomaiwa_ has joined #openstack-trove13:01
*** swebb has joined #openstack-trove13:03
*** amrith is now known as _amrith_13:43
*** _crobertsrh is now known as crobertsrh13:49
*** zhiyan has quit IRC13:51
*** zhiyan has joined #openstack-trove13:53
*** openstackstatus has quit IRC13:57
*** links has quit IRC13:57
*** pmalik has quit IRC14:00
*** pmalik has joined #openstack-trove14:00
*** haomaiwa_ has quit IRC14:01
*** haomaiwang has joined #openstack-trove14:01
*** mingdang1 has joined #openstack-trove14:22
*** chaozhechen_ has joined #openstack-trove14:24
*** mingdang1 has quit IRC14:57
*** haomaiwang has quit IRC15:01
*** 18WABEK5P has joined #openstack-trove15:01
*** chaozhechen_ has quit IRC15:11
*** chaozhechen_ has joined #openstack-trove15:11
*** chaozhechen_ has quit IRC15:16
*** chaozhechen_ has joined #openstack-trove15:16
*** _amrith_ is now known as amrith15:28
chaozhechen_Any one knows when is the trove weekly meeting?15:28
amrithI know.15:36
vkmcchaozhechen_, next Wednesday at 6.00pm UTC15:42
vkmcchaozhechen_, #openstack-meeting-alt15:42
vkmcchaozhechen_, more here https://wiki.openstack.org/wiki/Meetings/TroveMeeting15:42
chaozhechen_vkmc: Thanks :)15:51
*** vkmc is now known as vkmc-lunch15:56
toskypmalik: hi, around for some questions about the (new) integration tests (and https://review.openstack.org/255429 )?16:00
*** 18WABEK5P has quit IRC16:01
*** haomaiwang has joined #openstack-trove16:01
*** johnma has joined #openstack-trove16:08
*** csoukup has joined #openstack-trove16:15
cp16nettosky: so in the tests there is a separate config that is being used16:34
toskycp16net: yes, and isn't it the one reachable by trove.tests.config.CONFIG? While the suggested cfg.CONF is for the services configuration file, if I get it correctly16:35
cp16netso that the tests can have extened attrs for the test scenarios16:35
cp16netright16:36
toskyoki, so I can proceed16:37
toskybut then, are the new tests already in production? I think I haven't seen running on the gates, is it correct? And what are the plans regarding them/16:37
tosky?16:37
cp16nettosky: the tests/api/* tests are all for mysql currently16:38
cp16netcant be used for other datastores very easily16:38
toskyright16:38
cp16netthey are the only tests running in the gate currently16:38
cp16netwe are working to make sure that the scenario tests are coverering as much as the original tests16:39
toskyso, are the "new format" mysql tests not yet on par with the old ones?16:39
cp16netthen we can switch to using those tests16:39
toskyyou answered, ok :)16:39
cp16net:)16:39
cp16netthats the only reason right now we have 2 sets16:39
cp16netof tests16:39
toskyright, I understand16:39
toskyand in order to run the new tests, apart from what it's written there, is there a set of groups of tests that can be considered "stable" to compare the results?16:40
cp16netyou should be able to see the groups in the int-tests.py16:40
cp16netredstack int-tests --group=mysql_supported16:41
cp16neti'd like to avoid such headaches by the end of the cycle and move to the new tests16:42
toskycp16net: yes, I see all the groups, but the question is more: are all really really working now, or is there some set which is more stable than others? (maybe it's just "yes, all implemented are working")16:42
*** rcernin has quit IRC16:42
cp16nettosky: i have run them in the past16:43
cp16netnot in the last month or 216:43
toskyack, thanks16:43
toskyI will try16:44
cp16netas i've been working on clustering for pxc and making sure they are passing in the new tests16:44
cp16netsince its a new datastore i havent run the mysql tests in a while16:44
cp16neti believe peterstac has tho16:44
* tosky looks at peterstac16:45
cp16netand i probably pmalik since he commented on the review you mentioned :-P16:45
pmaliktosky Yes, you were right, see my comment.16:51
toskypmalik: thanks!16:51
toskypmalik: if you had to estimate the percentage of completeness of the new scenario mysql tests compared to the old ones, how would you rate it?16:52
*** sabeen has joined #openstack-trove16:53
*** david-lyle has quit IRC16:53
*** sabeen3 has joined #openstack-trove16:55
*** sabeen has quit IRC16:58
pmaliktosky It depends which datastore you are talking about. If you consider datastore other than MySQL the new test suite has a significantly greater coverage than the 'old' api testsuite. If you consider just MySQL. It covers most of the stuff, it currently has some gaps in access/root tests. It however, in contrast to 'old' testsuite tests data operations as well - it pushes and verifies real data through the test instance16:58
pmaliks using a client connection. It also includes some coverage that the 'old' suite does not (logging stuff). It is a continuous process, we are filling the suite as we go, the 'old' *MySQL* tests had several years of head start.16:58
toskypmalik: I was talking about MySQL in fact (well, also MariaDB); so I guess I really need to properly run also the new suite17:00
toskythanks17:00
*** haomaiwang has quit IRC17:01
*** haomaiwang has joined #openstack-trove17:01
*** vkmc-lunch is now known as vkmc17:05
pmaliktosky As pointed out by Craig you can run --group=<datastore>_supported which should test only stuff currently supported by the datastore. You can also run multiple groups of your choosing like: './redstack int-tests --group=database --group=user'. You mau need to cherry-pick ' https://review.openstack.org/#/c/224363/ ' from review to get them fully work. There are also two more extensions to the suite currently in revie17:06
pmalikw  depending on that one - configuration groups and extension to cluster tests.17:06
zigoGuys, I'm getting really mad with trove, it's telling me I need to run windows !!! http://paste.openstack.org/show/481532/17:07
zigoSeriously, what is this issue about?17:07
cp16netzigo: thats in a dependency keyring17:08
zigocp16net: Yup, saw that! :)17:08
zigocp16net: And?17:08
cp16netzigo: i have never seen that17:08
pmalikzigo What environment are you on?17:08
cp16netwhat is the scenario you are running?17:09
zigopmalik: I'm trying to build the Debian package of Trove (Mitaka b1).17:09
zigoSo I'm running unit tests at package build.17:09
zigoTrove is one of the last 4 server projects I need to finish (all the rest of OpenStack builds fine and i can upload them).17:09
toskypmalik, cp16net: apart from replacing the old tests with the old ones, any estimates for putting at least a non-voting gate jobs for the new tests?17:09
pmalikzigo, cp16net It is coming from the mock detector. It should ignore modules that cannot be imported. Hmm...17:09
zigoSo, my environment is packaged base only (no venv), and running in an sbuild chroot.17:10
*** ig0r_ has joined #openstack-trove17:11
cp16nettosky: i'd say for an estimate i'd like to get to this point or further by the end of mitaka17:11
toskycp16net: ack17:12
pmaliktosky I think that's the plan, but at least one little adjustment has to go to the redstack script before this can happen: https://review.openstack.org/#/c/250588/17:12
cp16netzigo: that shouldnt be an issue from my experience17:12
zigocp16net: Yeah, the question is: WTF is going on?!? :)17:13
cp16netzigo: pmalik but that is some new code there17:13
pmalikcp16net, zigo Not sure what is causing it. If you look at line 113 in 'tests.unittests.trove_testtools' it catches an ImportError, but this is throwing a RuntimeError, which is kind of weird...17:15
pmalikmaybe we should just catch any error...17:16
*** ashleighfarnham has joined #openstack-trove17:16
cp16netzigo: it sounds like you can replicate this issue17:19
cp16netzigo: but how would i replicate it?17:19
zigocp16net: Can you try to build the package?17:20
cp16netdo you have the package scripts avail?17:20
zigoYou need a Debian Jessie.17:20
cp16netthats what i run17:20
*** ianbrown__ has quit IRC17:20
pmalikGreat, this looks like the code of the lib: https://github.com/rcritten/kernel-keyring/blame/master/keyring/backends/Windows.py#L8217:20
zigocp16net: http://openstack.alioth.debian.org/17:20
zigocp16net: Replace liberty by mitaka ...17:21
*** ianbrown__ has joined #openstack-trove17:21
pmalikCorrection: https://bitbucket.org/kang/python-keyring-lib/src/b2e88501a6a9bc7f1c7c230a6431ac0860ff4e50/keyring/backends/Windows.py?at=default&fileviewer=file-view-default17:21
zigocp16net: I'm trying with catching all errors...17:22
cp16netthe unit tests run on ubuntu so i'm kinda surprised about this17:22
zigocp16net: It has nothing to do with it. Rebuilding on ubuntu would most likely do the same.17:23
zigoFixing trove_testtools.py to catch all exception does the trick.17:24
*** ViswaV has joined #openstack-trove17:24
zigoThanks for the tip, now we got to make it upstream, I guess.17:25
cp16netzigo: can you file a bug on this plz?17:25
pmalikcp16net, zigo : I guess the problem here is that they are throwing a RuntimeException from static code. The module gets loaded on import and explodes when the detector tries to probe that property...17:26
pmalikzigo I can have it fixed ASAP.17:26
* zigo files the bug17:27
cp16netzigo: pmalik thanks. zigo can you pipe in on the review as well since you found it when pmalik pushes it?17:27
zigohttps://bugs.launchpad.net/trove/+bug/152491817:28
openstackLaunchpad bug 1524918 in Trove "Unit test errors in python-keyring when building Debian package" [Undecided,New]17:28
cp16netawesome thanks!17:28
zigoPlease add me to the review, yes.17:29
*** ViswaV has quit IRC17:29
zigo"Thomas Goirand" is my id there...17:29
amrithcp16net, do you run debian jessie?17:30
amrithand do you see this problem?17:30
cp16neti do17:30
cp16netbut i have never seen it17:30
amrithI get the point that we can mask the error by catching a broader exception and passing17:30
cp16netmust be how the packaging happens17:30
amrithbut I'm wondering why this is throwing for zigo but not you.17:30
* amrith wonders whether debian packaging is running on Windows ;)17:30
cp16neti'm runing with the tox venv17:31
zigoamrith: I'm not using devstack...17:31
cp16netsounds like the packaging does not17:31
amrithnor I17:31
zigoAnd ... "It works on devstack" (tm)17:31
zigo:)17:31
cp16netlolz17:31
*** ViswaV has joined #openstack-trove17:31
amrithgood try, I'm not using devstack (or redstack) either17:32
amrithbut I don't use debian17:32
amrithand I do have windows17:32
amrithso I guess I'm all set.17:32
cp16netwindows makes my eyes bleed17:32
cp16netlol17:32
*** openstackstatus has joined #openstack-trove17:37
*** ChanServ sets mode: +v openstackstatus17:38
amrithcp16net, zigo looking at the keyring code I see no reason why it should even be throwing that exception17:42
amrithwhy does it even think it is in the windows code?17:42
amrithdoes it have a windows module loaded?17:42
openstackgerritPetr Malik proposed openstack/trove: Catch all errors in Mock detector  https://review.openstack.org/25601117:43
cp16netlooks like that find mocks is iterating over everything17:43
pmalikcp16net zigo : OK, it's here: https://review.openstack.org/#/c/256011/17:43
cp16netand it might be installed with keystone17:43
cp16neton the host system17:44
cp16netand in our venv its not17:44
cp16neti'll bet thats the case17:44
*** nshah has joined #openstack-trove17:45
cp16netzigo: are you building all the packages from the same vm?17:45
cp16netand not starting fresh each timE?17:45
amrithpmalik, I just -1'ed with a comment17:48
cp16nethmm looks like its in our client as well17:49
cp16netso if you used the same venv for the troveclient and trove to run the unit tests i'll bet you get this error17:49
dougshelley66ah interesting17:50
amrithhow did you do that?17:51
cp16net?17:51
amrithcp16net, how'd you use the same venv for troveclient and trove17:51
amrithI wanted to do what you are doing17:52
cp16neti'm just looking at the code17:52
amrithand you say "i'll bet you get" ...17:52
cp16netyeah so i searched for keyring across all the projects i have17:52
cp16netand found some keyring related stuff in the client17:52
cp16netnot sure that its related yet or not17:53
cp16nethmm doesnt look like it17:53
cp16netamrith: since zigo said he wasnt using a venv to run the tests when packaging it must mean that all the python packages are available to the system17:54
* amrith grumbles17:54
cp16netif we are recursively going through all the mocks then it *MAY* cause this issue17:54
zigocp16net: Correct.17:55
cp16netfrom global requirements i see keyring>=2.1,!=3.317:55
cp16netso if you install this in the tox venv we use for unittests17:55
cp16netideally you should be able to replicate the issue17:55
zigoI'm using python-keyring from Jessie, so that's version 4.0.17:55
cp16netzigo: i wont hold that against you :-p17:57
zigoAfter fixing this issue, I still have another one: http://paste.openstack.org/show/481539/17:57
*** imandhan has joined #openstack-trove17:58
zigoAny idea for that one?17:58
pmalikzigo OK, something is not being mocked out well here. Let me take a look.17:58
zigoThanks.17:59
cp16netyup17:59
zigoGosh, it's sooooooooo nice to work with OpenStack people ... :)17:59
zigoAlways helpful.17:59
cp16net:)17:59
amrithso it sounds like the issue is that you are running the tests in an environment other than the one in which we nornally expect it to run.18:00
amrithhmm, so is the fix to (a) make all the tests run in this non tox environment or (b) have you run the tests in the tox environment?18:00
*** haomaiwang has quit IRC18:01
amrithzigo, always helpful except for me ;)18:01
*** haomaiwang has joined #openstack-trove18:01
cp16netideally it would be good to run and install from a venv for each project18:01
zigoamrith: I *cannot* run tox within the packag building context.18:02
amrithcan you run it outside of that context?18:02
amrithi.e. run tox in a venv18:02
zigoMostly, because downloading when building is forbidden, and also, because I must use system packages.18:02
amrithand then package?18:02
zigoamrith: What would be the point?18:02
cp16netzigo: can you use a venv to build it?18:02
zigocp16net: No.18:02
zigoamrith: The point is precisely to do tests in an environment which is *not* a venv.18:03
zigoSo that I can test with what's in the system.18:03
amrithfor that I'd use tests other than the mock tests that you are running ;)18:03
amrithlike our int-tests18:03
cp16netand using system packages makes all the python-* libs available to all services18:03
zigoI need to go take care of my kids.18:04
zigoI'll come back tonight.18:04
cp16netzigo: ok18:04
cp16netamrith: i think ideally a package should be deployed with a venv18:05
cp16netbut from a packager for debian, ubuntu, others... thats not ideal18:05
cp16netbut i think thats a matter of prefernce18:06
cp16netfrom a clean vm you should be able to install everything to the system and it should work for each release18:07
cp16netthats the idea of the global requirements18:07
cp16netfor each release to make sure they are synced up18:07
amrithcp16net, take a look at https://review.openstack.org/#/c/256011/18:14
*** amit213 has quit IRC18:14
cp16neti agree with it18:15
*** amit213 has joined #openstack-trove18:15
cp16neti dont like catching the world either18:15
amrithagree with the change or the comment?18:15
*** sabeen3 has quit IRC18:17
pmalikzigo ok, I think I may have a fix for the other issue. It would be great if you could verify the patch resolves all issues and if so file a bug: http://paste.openstack.org/show/481542/ Thx. :-)18:18
amrithcp16net, I'm asking because if you are OK with it, I'll drop the -118:18
cp16neti'm replicating what zigo is doing and seeing if there is any further issues18:20
pmalikamrith cp16net I caught all because this is just a test and is not supposed to cause stuff like this. I am fine with limiting the exception scope though.18:20
cp16neti'll run it with except RunTimeError in my test18:20
cp16neti'll hold my review until i test it18:21
pmalikcp16net oh, you can try the other fix above as well then :)18:22
cp16netyup18:23
cp16neti have the operating_system.write_file mocked18:23
cp16netbuilding the vm now18:23
*** pmackinn has quit IRC18:28
*** lgreg has left #openstack-trove18:50
*** haomaiwang has quit IRC19:01
*** haomaiwa_ has joined #openstack-trove19:01
openstackgerritTelles Mota Vidal Nóbrega proposed openstack/trove-specs: Implementing CEPH as a backend for backups  https://review.openstack.org/25605719:02
*** tosky has quit IRC19:03
*** chaozhechen_ has quit IRC19:18
*** pmackinn has joined #openstack-trove19:26
pmackinndougshelley66, ping19:51
dougshelley66pmackinn pong19:51
pmackinndougshelley66, https://github.com/openstack/trove/blob/master/trove/templates/mysql/config.template#L1119:52
pmackinndougshelley66, why /data ?19:52
dougshelley66https://bugs.launchpad.net/trove/+bug/137064619:53
openstackLaunchpad bug 1370646 in Trove "Mysql datadir shouldn't be in the root of mounted filesystem" [Medium,Fix released] - Assigned to Simon Chang (changsimon)19:53
pmackinndougshelley66, k thx19:54
*** haomaiwa_ has quit IRC20:01
*** rcernin has joined #openstack-trove20:01
*** 18WABEVAW has joined #openstack-trove20:01
openstackgerritamrith proposed openstack/trove-specs: Add support for hbase in Trove  https://review.openstack.org/25607920:05
*** johnma has quit IRC20:09
*** sabeen1 has joined #openstack-trove20:24
*** johnma has joined #openstack-trove20:39
*** sabeen3 has joined #openstack-trove20:39
*** sabeen1 has quit IRC20:39
openstackgerritTelles Mota Vidal Nóbrega proposed openstack/trove-specs: Implementing CEPH as a backend for backups  https://review.openstack.org/25605720:48
openstackgerritTelles Mota Vidal Nóbrega proposed openstack/trove-specs: Implementing CEPH as a backend for backups  https://review.openstack.org/25605720:57
cp16netbuilding these packages seem to be a pain20:57
cp16neti think just giving zigo the changes to test and we can merge them would be WAY easier at this point20:58
*** 18WABEVAW has quit IRC21:01
*** amrith is now known as _amrith_21:01
*** haomaiwang has joined #openstack-trove21:02
*** haomaiwang has quit IRC21:10
*** haomaiwang has joined #openstack-trove21:16
*** lgreg1 has joined #openstack-trove21:17
*** lgreg1 has left #openstack-trove21:17
*** mingdang1 has joined #openstack-trove21:33
*** crobertsrh is now known as _crobertsrh21:37
*** haomaiwang has quit IRC22:01
*** haomaiwang has joined #openstack-trove22:01
openstackgerritCraig Vyvial proposed openstack/trove: mock out the guestagent write_file call  https://review.openstack.org/25611422:05
*** imandhan has quit IRC22:06
*** hogepodge has quit IRC22:10
*** shakamunyi has quit IRC22:12
*** hogepodge has joined #openstack-trove22:13
*** shakamunyi has joined #openstack-trove22:15
*** mingdang1 has quit IRC22:19
*** david-lyle has joined #openstack-trove22:20
*** johnma has quit IRC22:38
*** rcernin has quit IRC22:45
*** sgotliv_ has quit IRC22:52
*** david-lyle has quit IRC22:55
*** haomaiwang has quit IRC23:01
*** haomaiwang has joined #openstack-trove23:01
*** openstackstatus has quit IRC23:01
*** sabeen3 has quit IRC23:21
*** pmackinn has quit IRC23:24
*** ViswaV has quit IRC23:36
*** ViswaV has joined #openstack-trove23:38
*** ViswaV has quit IRC23:43
*** jwang has quit IRC23:43
*** ViswaV has joined #openstack-trove23:43
*** sabeen1 has joined #openstack-trove23:47
*** jwang has joined #openstack-trove23:47
*** dsavineau has left #openstack-trove23:48
*** csoukup has quit IRC23:58

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