Monday, 2014-04-07

*** raulduke has joined #openstack-trove00:05
*** amytron has joined #openstack-trove00:05
*** matsuhashi has joined #openstack-trove00:18
*** ramashri has joined #openstack-trove00:21
*** eguz has quit IRC00:28
openstackgerritA change was merged to openstack/trove: Pop instead of get for timeout kwarg  https://review.openstack.org/8067700:36
*** eghobo has joined #openstack-trove00:39
*** eghobo has quit IRC00:39
*** demorris has joined #openstack-trove00:57
*** jcru has joined #openstack-trove01:03
*** jcru has quit IRC01:03
*** demorris has quit IRC01:17
*** nosnos has joined #openstack-trove01:30
*** michael-yu has joined #openstack-trove01:35
*** michael-yu has quit IRC02:00
*** michael-yu has joined #openstack-trove02:00
*** michael-yu has quit IRC02:20
*** michael-yu has joined #openstack-trove02:26
*** chandan_kumar has joined #openstack-trove02:29
*** michael-yu has quit IRC02:41
*** matsuhashi has quit IRC02:47
*** robertmyers has joined #openstack-trove02:54
*** coolsvap has joined #openstack-trove02:56
*** michael-yu has joined #openstack-trove02:57
*** achampion has joined #openstack-trove02:59
*** robertmyers has quit IRC02:59
*** achampio1 has quit IRC03:01
*** nosnos has quit IRC03:02
*** matsuhashi has joined #openstack-trove03:04
*** achampio1 has joined #openstack-trove03:05
*** achampion has quit IRC03:06
*** michael-yu has quit IRC03:08
*** eghobo has joined #openstack-trove03:15
*** nosnos has joined #openstack-trove03:20
*** matsuhashi has quit IRC03:29
*** chandan_kumar has joined #openstack-trove03:30
*** haomai___ has quit IRC03:30
*** chandan_kumar has quit IRC03:31
*** chandan_kumar has joined #openstack-trove03:31
*** chandan_kumar has quit IRC03:48
*** eghobo has quit IRC03:49
*** eghobo has joined #openstack-trove03:49
*** nosnos has quit IRC03:51
*** chandan_kumar has joined #openstack-trove04:08
*** michael-yu has joined #openstack-trove04:27
*** michael-yu has quit IRC04:28
*** michael-yu has joined #openstack-trove04:31
*** michael-yu has quit IRC04:32
*** eghobo has quit IRC04:38
*** eghobo has joined #openstack-trove04:39
*** michael-yu has joined #openstack-trove04:48
*** eguz has joined #openstack-trove04:50
*** eghobo has quit IRC04:50
*** michael-yu has quit IRC04:51
*** michael-yu has joined #openstack-trove04:53
*** michael-yu has quit IRC04:53
*** shivam has joined #openstack-trove04:54
*** michael-yu has joined #openstack-trove05:02
*** chandan_kumar has quit IRC05:02
*** michael-yu has quit IRC05:06
*** saju_m has joined #openstack-trove05:13
*** chandan_kumar has joined #openstack-trove05:27
*** lifeless has quit IRC05:30
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522505:30
*** lifeless has joined #openstack-trove05:31
*** michael-yu has joined #openstack-trove05:39
*** michael-yu has quit IRC05:40
*** amytron has quit IRC06:04
*** michael-yu has joined #openstack-trove06:04
*** michael-yu has quit IRC06:10
*** michael-yu has joined #openstack-trove06:23
openstackgerritJenkins proposed a change to openstack/trove: Imported Translations from Transifex  https://review.openstack.org/8272106:24
*** michael-yu has quit IRC06:24
*** michael-yu has joined #openstack-trove06:30
*** rwsu has joined #openstack-trove06:35
*** saju_m has quit IRC06:41
*** saju_m has joined #openstack-trove06:54
*** michael-yu has quit IRC06:56
*** michael-yu has joined #openstack-trove07:01
*** chandan_kumar has quit IRC07:02
*** michael-yu has quit IRC07:14
*** michael-yu has joined #openstack-trove07:15
*** michael-yu has quit IRC07:19
*** eguz has quit IRC07:22
*** sgotliv has joined #openstack-trove08:32
*** matsuhashi has joined #openstack-trove08:35
*** nosnos has joined #openstack-trove08:40
*** dmitryme has joined #openstack-trove08:43
sgotlivdmakogon_, ping08:45
*** dmakogon_ is now known as denis_makogon08:57
denis_makogonsgotliv, 'sup08:57
*** SnowDust has joined #openstack-trove09:17
*** saju_m has quit IRC09:27
*** SnowDust has quit IRC09:56
*** dmitryme has quit IRC10:03
*** raulduke has quit IRC10:03
*** SnowDust has joined #openstack-trove10:08
*** matsuhashi has quit IRC10:16
*** matsuhashi has joined #openstack-trove10:16
*** matsuhashi has quit IRC10:20
*** IvanZ has joined #openstack-trove10:27
*** coolsvap has quit IRC10:27
openstackgerritshivam shukla proposed a change to openstack/trove: Tests for heat based instance workflow  https://review.openstack.org/6649910:29
*** saju_m has joined #openstack-trove10:32
*** saju_m has quit IRC10:49
*** dmitryme has joined #openstack-trove11:19
*** saju_m has joined #openstack-trove11:24
*** matsuhashi has joined #openstack-trove11:26
*** matsuhashi has quit IRC11:49
*** matsuhashi has joined #openstack-trove11:50
*** matsuhas_ has joined #openstack-trove11:53
*** matsuhashi has quit IRC11:54
*** nosnos has quit IRC11:59
*** demorris has joined #openstack-trove12:06
*** dmitryme has quit IRC12:07
*** pdmars has joined #openstack-trove12:10
*** pdmars has quit IRC12:10
*** pdmars has joined #openstack-trove12:11
*** zigo has quit IRC12:26
*** achampio1 has quit IRC12:27
*** demorris has quit IRC12:35
*** SnowDust has quit IRC12:39
*** dmitryme has joined #openstack-trove12:41
openstackgerritSergey Gotliv proposed a change to openstack/trove: Make --repo-path an optional argument for db_recreate  https://review.openstack.org/8570012:47
*** IvanZ_ has joined #openstack-trove12:54
*** IvanZ has quit IRC12:55
*** sgotliv has quit IRC12:57
*** IvanZ_ has quit IRC12:58
*** IvanZ has joined #openstack-trove12:59
*** freyes_ has joined #openstack-trove13:02
*** IvanZ has quit IRC13:04
*** radez_g0` is now known as radez13:05
*** IvanZ has joined #openstack-trove13:05
*** sgotliv has joined #openstack-trove13:06
*** rustlebee is now known as russellb13:08
*** sgotliv has quit IRC13:12
*** sgotliv has joined #openstack-trove13:12
*** grapex has joined #openstack-trove13:15
*** grapex has quit IRC13:16
*** grapex has joined #openstack-trove13:17
*** achampion has joined #openstack-trove13:22
*** freyes_ has quit IRC13:25
*** matsuhas_ has quit IRC13:27
*** dmitryme has quit IRC13:27
*** matsuhashi has joined #openstack-trove13:28
*** matsuhas_ has joined #openstack-trove13:31
*** matsuhashi has quit IRC13:32
*** kevinconway has joined #openstack-trove13:32
*** jcru has joined #openstack-trove13:33
*** matsuhas_ has quit IRC13:34
*** Barker has joined #openstack-trove13:41
*** demorris has joined #openstack-trove13:50
*** pdmars has quit IRC14:16
*** pdmars has joined #openstack-trove14:17
*** pdmars has quit IRC14:17
*** pdmars has joined #openstack-trove14:18
*** pdmars has quit IRC14:20
*** pdmars has joined #openstack-trove14:21
*** pdmars has quit IRC14:22
*** jasonb365 has joined #openstack-trove14:22
*** pdmars has joined #openstack-trove14:22
*** shivamshukla has joined #openstack-trove14:28
*** amytron has joined #openstack-trove14:32
*** mattgriffin has joined #openstack-trove14:32
*** iccha has joined #openstack-trove14:44
*** jmontemayor has joined #openstack-trove14:45
*** saju_m has quit IRC14:50
*** robertmyers has joined #openstack-trove14:52
*** shivamshukla has quit IRC14:55
*** demorris has quit IRC15:00
*** sbfox has joined #openstack-trove15:01
openstackgerritDirk Mueller proposed a change to openstack/trove: Remove dependencies on pep8, pyflakes and flake8  https://review.openstack.org/6713815:03
*** jasonb365 has quit IRC15:03
*** thedodd has joined #openstack-trove15:05
*** ramashri has quit IRC15:19
*** mattgriffin has quit IRC15:19
*** mattgriffin has joined #openstack-trove15:19
*** shivamshukla has joined #openstack-trove15:27
*** pdmars has quit IRC15:29
*** pdmars has joined #openstack-trove15:29
*** demorris has joined #openstack-trove15:31
*** pdmars has quit IRC15:32
*** pdmars has joined #openstack-trove15:32
*** pdmars has quit IRC15:33
*** pdmars has joined #openstack-trove15:33
*** pdmars has quit IRC15:34
*** pdmars has joined #openstack-trove15:35
*** pdmars has quit IRC15:35
*** pdmars has joined #openstack-trove15:36
*** pdmars has quit IRC15:37
*** pdmars has joined #openstack-trove15:37
*** pdmars has quit IRC15:38
*** pdmars has joined #openstack-trove15:39
*** pdmars has quit IRC15:40
*** pdmars has joined #openstack-trove15:41
*** pdmars has quit IRC15:41
*** pdmars has joined #openstack-trove15:42
*** pdmars has quit IRC15:42
*** shivamshukla has quit IRC15:43
*** shivamshukla has joined #openstack-trove15:43
*** pdmars has joined #openstack-trove15:43
*** shivamshukla has quit IRC15:48
*** michael-yu has joined #openstack-trove15:49
sgotlivdenis_makogon, ping15:53
*** ramashri has joined #openstack-trove15:53
*** eghobo has joined #openstack-trove15:54
*** sgotliv has quit IRC16:00
*** demorris has quit IRC16:04
*** ramashri_ has joined #openstack-trove16:06
*** ramashri has quit IRC16:06
*** demorris has joined #openstack-trove16:07
*** jmontemayor_ has joined #openstack-trove16:11
*** jmontemayor has quit IRC16:11
*** jmontemayor_ has quit IRC16:12
*** saju_m has joined #openstack-trove16:12
*** jmontemayor has joined #openstack-trove16:12
*** michael-yu has quit IRC16:22
*** zigo has joined #openstack-trove16:28
*** robertmyers has quit IRC16:29
*** dmitryme has joined #openstack-trove16:29
*** sbfox has quit IRC16:31
*** robertmyers has joined #openstack-trove16:32
*** zigo has quit IRC16:33
*** zigo has joined #openstack-trove16:34
*** saju_m has quit IRC16:35
*** zigo has quit IRC16:41
*** grapex has quit IRC16:43
*** demorris has quit IRC16:43
*** grapex has joined #openstack-trove16:43
*** demorris has joined #openstack-trove16:44
*** denis_makogon_ has joined #openstack-trove16:45
*** zigo has joined #openstack-trove16:46
*** sbfox has joined #openstack-trove16:47
*** sbfox has quit IRC16:47
*** denis_makogon has quit IRC16:47
*** denis_makogon_ is now known as denis_makogon16:47
*** sbfox has joined #openstack-trove16:47
*** dmakogon_ has joined #openstack-trove16:47
*** IvanZ_ has joined #openstack-trove16:49
*** ViswaV has joined #openstack-trove16:49
*** IvanZ has quit IRC16:49
*** IvanZ_ is now known as IvanZ16:49
denis_makogonSlickNik, ping16:49
*** yidclare has joined #openstack-trove16:52
*** michael-yu has joined #openstack-trove16:53
*** harlowja has joined #openstack-trove16:56
*** jmontemayor has quit IRC16:58
*** shivamshukla has joined #openstack-trove17:05
SlickNikdenis_makogon: what's up?17:08
*** amcrn has joined #openstack-trove17:13
*** IvanZ has quit IRC17:17
*** sbfox has quit IRC17:20
*** demorris has quit IRC17:23
SlickNikJust a reminder that we're planning on having the blue-print meeting in about 25 minutes.17:32
SlickNikAgenda: https://wiki.openstack.org/wiki/Meetings/TroveMeeting17:32
*** sbfox has joined #openstack-trove17:33
*** yogesh has joined #openstack-trove17:33
SlickNikdenis_makogon: ping17:37
SlickNikhttps://bugs.launchpad.net/trove/+bug/130278717:37
denis_makogonSlickNik, i saw this bug and mark it as New, because there's no such type as Wishlist17:38
SlickNikLet's not mark something someone's working on from "In Progress" to "New".17:39
denis_makogondone, status reverted17:40
SlickNikThat could give the wrong impression, and we'd be stepping on each other's toes.17:40
SlickNikThanks!17:40
SlickNikAlso, imho it really is a bug. We are part of OpenStack, and we should try and align with other projects as much as we can.17:42
SlickNikWhether it's the install, testing framework, docs or client.17:42
denis_makogondon't know, 'cuz there's no standards for the shell ouptuts, probably, yet17:43
denis_makogonpretty table is the only required requirement17:45
*** sbfox has quit IRC17:46
SlickNikI don't think that's the only requirement. Our old client used prettytable, but as part of our graduation we had to do a rewrite to better align with other OpenStack clients. (for. example, the way we did things like token management was different, and we needed to fix this as part of the client re-write).17:47
*** freyes_ has joined #openstack-trove17:49
denis_makogoni still think this is the part of the wishlist, and not the _real_  bug, i guess such change deserves the BP instead of the bug-report, and should be discussed with other projects17:51
denis_makogoni do believe that not the all clients do what nova does17:52
*** radez is now known as radez_g0n317:54
*** Barker has quit IRC17:54
*** Barker has joined #openstack-trove17:56
SlickNikdenis_makogon: If that's the case; it's probably more tactful to have a quick IRC conversation with peterstac to point out that different clients do things differently.17:58
*** Barker has quit IRC17:59
denis_makogonSlickNik, we can do that after meeting17:59
SlickNikLet's get this bp meeting started.17:59
denis_makogono/17:59
peterstacdenis_makogon: Sure, however most CLI's have a 'similar' format (if not exactly the same), which I thought we should emulate18:00
peterstacdenis_makogon: But I'm open to discussing it18:01
denis_makogonpeterstac, of course, i think we could start from the writing the policy for such cases, like oslo bp for API-clients18:01
*** saurabhs has joined #openstack-trove18:01
SlickNikLet's give folks a couple of mins to show up.18:01
denis_makogonpeterstac, if you planning to do this for all clients, i'm up for that18:01
grapexo/18:02
esmuteo/18:02
denis_makogonSlickNik, you're on charge, commander Kirk18:02
cp16neti'm lurking18:03
SlickNikhub_cap will be MIA today; amcrn / vipul around?18:03
amcrnSlickNik: alive18:04
grapexSlickNik: senoritas18:04
kevinconwayhub_cap: joined a band? ba-dum-ch18:04
SlickNik#link https://blueprints.launchpad.net/trove/+spec/point-in-time-recovery18:04
grapexlol, I just realized that looks the same as the Spanish word18:04
denis_makogonit's mine18:04
grapexI mean he has "senioritis"18:04
denis_makogongrapex, same =)18:05
SlickNikOh, that makes so much more sense now.18:05
SlickNik(senioritis)18:05
denis_makogoncan i speak ?18:05
SlickNikgo for it18:06
SlickNikYour bp, your floor.18:06
denis_makogonthe justification: user should be able to perform recovery process when he wants it, without provisioning new instance with given restore reference18:06
denis_makogonbenefits: applying the backup at already running instance, without provisioning new (and hurting users quotas)18:07
denis_makogoni made some reseach and proposed this feature with name "point in time recovery"18:08
SlickNikSo denis_makogon my concern with this is that it really isn't implementing "Point in Time" recovery.18:08
*** shivam_ has joined #openstack-trove18:08
cp16netthats what i was thinking as well SlickNik18:08
denis_makogonplease suggest the appropriate name18:08
robertmyersAlso does this destroy all the data on the instance?18:09
grapexSlickNik: Seconded- normally Point in Time recovery means you can restore a database to how it was at some given exact point in time in the past18:09
denis_makogoni'm open for discussion18:09
grapexrobertmyers: That's my second concern18:09
SlickNikThis is more like restore a backup to a currently running instance.18:09
grapexI think this may be dangerous18:09
robertmyerswhat happens on a failure to restore?18:09
robertmyersdead instance?18:09
denis_makogonrobertmyers, yes18:09
robertmyersboo18:09
grapexrobertmyers: You better hope the original backup worked. :)18:09
cp16netthose are the 2 big questions i see as well when i read over this18:09
kevinconwayunder what circumstances would you need to restore in place versus restore in new instance?18:10
grapexdenis_makogon: What if we instead did this feature by creating a new Trove instance, restoring, and then only on success deleting the old one and switching out the DNS name or ip address?18:10
robertmyersdenis_makogon: That is the reason we made restores go to a new instance18:10
cp16netbut it seems like it would not if you were starting this running instance over from scratch if you even tried to restore the data from the backup18:10
robertmyerscustomers don't like their data deleted18:10
amcrnkevinconway: the only scenario i can think of is if you've done poor capacity planning and have no "new" instances of the flavor you desire (which is an awful reason to justify this behavior)18:11
denis_makogonrobertmyers, if you are restoring some data you expect that it's gonna be totally replaced18:11
kevinconwayamcrn: if you are restoring, doesn't that imply something is broken in the current instance18:11
kevinconwaywhy not delete it and free up the space?18:11
amcrnkevinconway: don't know, was trying to cook up a hypothetical, i agree with you.18:12
robertmyersdenis_makogon: I get that but an api shouldn't fail in a destroyed state18:12
*** demorris has joined #openstack-trove18:12
robertmyersit needs to be safe18:12
*** shivamshukla has quit IRC18:12
denis_makogonrobertmyers, i agree18:12
robertmyersrestore to a new volume or disk18:12
denis_makogonrobertmyers, the flow for your case looks like, we backuping the actual data and apply the backup to instance, if recovering gone failed, we revert the change18:13
robertmyersmaybe, but what if they don't have enought disk space?18:13
denis_makogonrobertmyers, volumes and their backuping is totally different feature18:14
robertmyersI'm just talking about the data18:14
robertmyersforget volumes18:14
denis_makogonrobertmyers, we could add checks, if FS fits to backup18:14
robertmyersthis is the reason we setup restores on a new instance only18:15
denis_makogonif it has enough space for it18:15
robertmyersthe customer can delete after it works18:15
robertmyersit is too complicated18:15
denis_makogoni could add the validation of API layer18:15
denis_makogonit seems not18:15
cp16netits the cloud its meant to be "thrown" away right?18:15
robertmyersbut it is complicated18:15
robertmyersplus you introduce two apis to restore18:16
robertmyersthat is confusing18:16
denis_makogonthe bottlenecks: size of FS and size of backup18:16
denis_makogonrobertmyers, actually not18:16
denis_makogonrobertmyers, recovery is not the restore18:16
robertmyersdenis_makogon: how so?18:16
robertmyersthat is two18:16
denis_makogonone already exists18:16
robertmyersjust a different name18:16
robertmyerssame thing18:17
cp16netmaybe its just a different type of restore?18:17
denis_makogonthey have different flow18:17
denis_makogoncp16net, yes18:17
robertmyersdenis_makogon: I get that, but it is doing the same thing in the end18:17
cp16netlike we have different types of backups18:17
robertmyersso that is two ways to restore18:17
robertmyersfrom the API18:17
SlickNikdenis_makogon: let me put it this way. What scenario does this enable, that you wouldn't already be able to do with restoring to a new instance?18:18
cp16netthe only difference in the end is the instance that the restore happens on18:18
robertmyersso now we'd have to support 2 restore methods for every datastore18:18
denis_makogonrobertmyers, but proposed by me, doesn't expects to create new VM18:18
amcrn+1 to SlickNik's question18:18
robertmyersdenis_makogon: that is a technicallity18:18
denis_makogonSlickNik, this feature allows to apply backup to already running instance18:19
robertmyerswe still have to maintain two different code paths18:19
esmuteif it is to not impact custoers' quota, i think it is far easier to tell them to up their quota... you get more money from them too :-)18:19
espI like grapex’s earlier thought regarding switching dns name / floating ip on the current restore18:19
amcrndenis_makogon: he's asking what the benefit of recovering to an existing instance is (as compared to a new instance) in a cloud environment?18:19
SlickNikdenis_makogon: I get the trees; trying to understand the forest.18:19
grapexesp: I like my idea too. :) Though even that will be very complicated and so far the benefits don't seem to be worth the cost.18:19
espI think we got that to work well, the end result would want the bp is trying to do18:19
denis_makogonamcrn, gives an ability to avoid quotas18:20
*** khyati_ has joined #openstack-trove18:20
robertmyersdenis_makogon: I don't know if that justifies all the extra code18:20
robertmyersand the confusion of two apis18:20
grapexrobertmyers: +118:20
SlickNikdenis_makogon: delete current (bad) instance; restore to new instance. Where is the quota issue?18:20
amcrna quota is elastic, it can be temporarily increased for a tenant given the circumstances18:21
amcrnSlickNik: you might want to keep the instance around for remediation/introspection18:21
espamcrn: +1 I always think that too, but then get shot down :)18:21
SlickNikamcrn: Sure, but if you restored on top of it, you wouldn't have it running either.18:21
denis_makogonrobertmyers, billing is one of the cases, suppose i had one server and several backup of it, i want to restore it to yesterday's backup, and i am not able to do restoring, because it envolves the quotas usage, i don't want to see down-times]18:22
robertmyerswhy are the quotas set so low that this is a huge problem?18:22
cp16netamcrn: yeah you would want to keep it around especially if it breaks for some reason18:22
amcrni think you're misunderstanding what i meant by "keep it around"18:22
amcrni meant that there's a window between having it known by OpenStack and the operator taking it out of the plane18:22
robertmyersdenis_makogon: how small are your quotas?18:22
denis_makogonrobertmyers, public cloud, you bought cheep account18:22
robertmyers2 instances18:22
robertmyersyour fault18:23
robertmyersnot the api18:23
SlickNikSo the way I see it, this bp has points to address:18:23
SlickNik- For something to be "point in time" recovery, you should be able to recover to any point in time (with reasonable limits on granularity). This doesn't enable that.18:23
SlickNik- This currently doesn't enable anything new over restoring to a new instance (and additionally has the issue that we may overwrite valid data by mistake, making it dangerous).18:23
denis_makogonrobertmyers, this is not the good point of view to feature, same can be told about the replication, it's your fault, that you had not automated scripts that create replicate set18:24
amcrn+1 SlickNik18:24
robertmyersdenis_makogon: I'm just saying we can't code to fix an issue for a small subset of users18:24
robertmyersif you are unwilling to pay for more you need to think about how you are using the service18:25
SlickNikOkay, let's move on to the next bp18:26
SlickNikData volume snapshot [denis_makogon]18:26
SlickNik#link https://blueprints.launchpad.net/trove/+spec/volume-snapshot18:26
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522518:27
esp^ sorry :)18:27
denis_makogonSlickNik, according to Trove wiki pages, this feature was discussed when backups came18:27
denis_makogonbasically it's another way to do backups, avoiding versioning, datastore-affection18:28
*** sgotliv has joined #openstack-trove18:28
SlickNikdenis_makogon: Yes, the issue we faced at that point was that you could not ensure that your mysql backup data was consistent if you just made a volume snapshot.18:28
denis_makogonbut it doesn't fits to current backup implementation18:28
robertmyersdenis_makogon: how does this not fit in the current backup implementation?18:29
*** sgotliv_ has joined #openstack-trove18:29
robertmyersit seems like it could just be a different runner18:30
denis_makogonrobertmyers, backups are based upon strategies, which lives at guest vm18:30
robertmyersinstead of a command it runs cinder snapshot18:30
amcrn+1 robertmyers18:30
denis_makogonrobertmyers, volume backuping cannot be performed at guest side18:30
robertmyerswhy not?18:30
robertmyerswe use the swift api on the guest18:31
cp16netthe guest knows how to connect to swift to push the data18:31
robertmyersthe cinder api should work18:31
denis_makogonso, its valid to do that ?18:31
cp16netits the same tokens right?18:31
robertmyerssure18:31
denis_makogonso, that's look easier, i guess18:31
robertmyersI would at least try it first18:31
amcrndenis_makogon: plus it blends better with the capabilities feature18:31
denis_makogonamcrn, agreed18:32
cp16netamrith: true because deployers may not want to support that18:32
dougshelley66what about SlickNik's question about consistency?18:32
robertmyersthe guest is going to need to stop the db first18:32
peterstacBut that doesn't address what SlickNik said - it wouldn't guarantee database consistency18:32
robertmyersthen do snapshow18:32
peterstacah, that would work18:32
robertmyerssnapshot18:32
robertmyersput the db in readonly mode18:32
*** radez_g0n3 is now known as radez18:33
denis_makogonfirst flush the data in the memory to hard drive, then snapshot the volume18:33
robertmyersthen re-enable writes after the dump18:33
robertmyersyup18:33
denis_makogonrobertmyers, correct18:33
robertmyersthat is basically what percona extrabackup does18:33
SlickNikyes, r/o mode / stopped db would solve the consistency issues.18:33
denis_makogonnice =)18:34
robertmyersit is the only safe way to do a snapshot18:34
dougshelley66ok18:34
denis_makogonso, i think consistency question is closed, i suppose18:34
SlickNikAnother thing I'm worried about with the bp is API bloat.18:34
grapexSlickNik: +118:34
denis_makogonSlickNik, API will be skipped18:34
robertmyersjust a new backup type?18:35
denis_makogonyes18:35
robertmyers+118:35
denis_makogonand only18:35
robertmyersonly one?18:35
grapexI think it should use the existing backup API, though it is a bit different since the database will be shut off18:35
denis_makogonit looks more easier and doesn't pollutes the API routes18:35
SlickNikokay, denis_makogon can you take this feedback and update the BP?18:35
*** jmontemayor has joined #openstack-trove18:35
denis_makogonSlickNik, of course18:35
denis_makogonSlickNik, can i start the implementation ?18:36
SlickNikdenis_makogon: That's up to you, but I wouldn't start it until the bp is approved design is finalized.18:36
denis_makogonSlickNik, get it18:37
SlickNikLet's move on.18:37
denis_makogon#action re-write the BP18:37
SlickNikSo there are 2 related bps next18:37
SlickNikNetworking [denis_makogon]18:38
SlickNikNeutron Network Support [annashen]18:38
denis_makogon#link https://blueprints.launchpad.net/trove/+spec/network-manager-spec18:38
SlickNik#link https://blueprints.launchpad.net/trove/+spec/neutron-support18:38
denis_makogonmine BP describes the need of the network manager class, since we have to ways to manage network attributes18:39
denis_makogonlike SGs, floating IPs18:39
denis_makogonnow we have flow based upon nova-network18:39
*** sbfox has joined #openstack-trove18:40
denis_makogoni suggest to re-write it to be more flexible18:40
SlickNikYes, denis_makogon I don't think the second one can be done without a network manager interface.18:40
SlickNikSo to me it seems overlapping.18:40
denis_makogonimplementation will cover the nova-network flow18:40
denis_makogonSlickNik, annashen_ will take the neutron stuff18:41
SlickNikdenis_makogon: Did you get a chance to connect with annashen_ about it?18:41
denis_makogonSlickNik, my BP describes the actual sub-task of the annashen_ BP18:41
denis_makogonSlickNik, unfortunately, no, but i do belive that we can co-work over that18:41
denis_makogonSlickNik, mine implementation will come asap18:42
denis_makogonSlickNik, after, of course, BP gets approved18:42
annashen_denis: i would like to sync with you sometime before wed18:42
annashen_wendesday18:42
annashen_dn*18:43
SlickNikIf it's a sub-task, I'm confused why there are 2 separate bps.18:43
annashen_excuse my typo18:43
denis_makogonannashen_, lets first our BPs get's approved18:43
denis_makogonSlickNik, because they can be done in parallel18:43
robertmyerswell, it still could be one BP and multiple reviews18:43
cp16netyeah it seems like its 1 feature in the end18:43
robertmyersdependent review18:44
robertmyerscause the first just splits it up into the ability to use both18:44
SlickNikIt feels like the neutron changes are dependent on the network manager interface;18:44
robertmyersthen the second implements it18:44
SlickNikI don't think they can be done in parallel.18:44
SlickNik(well to a certain extent)18:45
grapexSlickNik: I agree- I'd almost rather implement network manager first, then make it possible to use both later18:45
grapexit may,possibly, take longer, but there's a higher chance we'll avoid bugs18:45
robertmyersgrapex: +118:45
grapexsince the initial work will just focus on one implementation (with a mind for the future)18:45
denis_makogonSlickNik, if network integface can be proposed and merged soon, tasks could be done in parallel18:45
peterstacI don't think it would take longer, since we still need to support nova-networking18:46
grapexSlickNik: After thinking about it for a bit, I'd like to change my "I'd almost rather" to "we should really, really, really" in the statement above18:46
denis_makogonpeterstac, and we would support in for like two more releases from the point when nova-network dropped18:46
SlickNikdenis_makogon: What would the network manager look like?18:47
SlickNikdenis_makogon: How would it support netron and nova-networking?18:47
denis_makogonSlickNik, abstract class with methods that required by current flow18:47
SlickNikdenis_makogon: This page seems light on the details https://wiki.openstack.org/wiki/Trove/NetworkAttributesManagement18:47
juicedenis_makagon: I would drop attributes from the description18:48
juicethis is really the network manager for Trove18:49
denis_makogonjuice, of course18:49
juiceslicknik: agreed - it would be nice to know what the interface for the network manager would like like18:49
juiceand the underlying purpose of the api18:49
denis_makogonjuice, it would look like java interface, nothing else18:50
robertmyersjava?18:50
denis_makogonrobertmyers, as the example18:50
juicedenis_makagon: i meant what the abstract functions would be18:50
denis_makogonjuice, same, as i said few lines ago18:51
vgnbkrdenis_makogon: I would like to see a bp that outlines which functionality would be abstracted, and how it would affect each of the APIs and the cli clients.18:51
kevinconwayi agree. java is bad. let's not use contracts of any kind.18:51
kevinconwayuse only dictionaries and lambdas18:51
denis_makogonvgnbkr, it would not affect API at all18:51
denis_makogonvgnbkr, it's the inner refactoring18:51
*** saju_m has joined #openstack-trove18:51
SlickNikdenis_makogon: Unless we've got an interface in mind, how do we know it'd work for both nova-network and neutron?18:51
esmutekevinconway: Java8 has lambdas now18:51
grapexkevinconway: Says you! All my personal projects are done in Ada.18:51
denis_makogonSlickNik, it's based on config value18:52
kevinconwaygrapex: do you program airplanes as a hobby?18:52
denis_makogonSlickNik, that defines which manager is used18:52
grapexkevinconway: No, car boats that turn into planes18:52
grapexSlickNik: I agree18:52
grapexI think trying to do it two ways before we add the major work from Anna's blueprint is a mistake18:52
grapexIt's getting the cart ahead of the horse18:52
vgnbkrSorry, I didn't mean just the REST API - maybe I'm not using the terminology right - but I would want to understand which functionality would change, and how it would be selected.18:53
vgnbkrdenis_makogon: If it is selected by config values, that should be reflected in the bp.18:53
denis_makogonvgnbkr, take a look at wiki page18:53
denis_makogonvgnbkr, i described how it'll work18:53
vgnbkrI did look at the wiki page - that's why I made the comment.18:53
denis_makogonvgnbkr, https://wiki.openstack.org/wiki/Trove/NetworkAttributesManagement#Configuration18:53
SlickNikgrapex: +1. I think that we need to figure out what the neutron requirements are.18:54
openstackgerritKaleb Pomeroy proposed a change to openstack/trove: Implements datastore capabilities  https://review.openstack.org/8350318:54
amrithguys and gals ... given how long this discussion is going on now, it is safe to say that there are many issues that have been raised about this proposal and we should figure out how to address those before a YES decision can be made. At this time, I implore core to consider a NOT NOW vote.18:54
amriththe motion is on the floor, do I have a second?18:55
SlickNikseconded18:55
amcrntres'd18:55
grapexAye18:55
amrithI propose an immediate vote on the motion18:55
kevinconwayamrith: this is no place for robertmyers rules18:55
robertmyerskevinconway: +118:55
amriththird edition, robertmyers rules18:55
juiceamrith: agreed without more information but I think it's pointed in the right direction18:55
*** sbfox has quit IRC18:56
SlickNikLet's move on to18:56
SlickNikCross-region backups [esmute]18:56
SlickNikhttps://blueprints.launchpad.net/trove/+spec/cross-region-backup-migration18:56
amriththanks18:56
esmuteha.. as if we dont have enough with backups already18:56
esmutethis one is about making backups accessible cross-region..18:56
esmuteto be able to restore from a backup in a different region18:57
robertmyersbroken link?18:57
grapexesmute: Your link on the agenda is wrong. :(18:57
amcrnhttps://wiki.openstack.org/wiki/Cross-region-backup-availability18:57
esmutehttps://wiki.openstack.org/wiki/Cross-region-backup-availability18:57
SlickNikThanks amcrn18:57
cp16netyeah its broken18:57
esmutethe idea is that /backup will take a location reference (instead of a instance ID) and create a backup.18:58
esmutethat will validate the location, create a backup record in the DB, and copy the backup from the the source region to the trove region18:59
*** sgotliv_ has quit IRC18:59
robertmyersesmute: should it not just be region and we use the service catalog to find the swift url?18:59
amcrnesmute: asking the user to provide an endpoint vs. a region (and/or az) doesn't align with the abstractions in other apis. thoughts?18:59
*** sbfox has joined #openstack-trove18:59
amcrncrafty robertmyers beating me to the punch18:59
amcrn;)18:59
esmuteit is assumed that the storage (swift) is accessible cross-region and that the auth token works for both regions18:59
robertmyersthat is the job of teh service catalog19:00
openstackgerritDaniel Salinas proposed a change to openstack/trove: Add instance metadata functionality to trove  https://review.openstack.org/8212319:00
grapexamcrn robertmyers: I agree, and I think if they provided the region it would be easier for us. But I do think the API as presented might be easier from a user's perspective19:00
amcrngrapex: until the endpoint changes19:00
esmutethe backup already shows location.19:00
robertmyerswhich we should be using instead of the hard coded SWIFT_URL in the config file19:00
grapexamcrn: Actually, yeah you're right.19:00
cp16netso you have to provide the full uri to the backup file in the API?19:01
esmutehow do we specify the backup object?19:01
*** thedodd has quit IRC19:01
amcrnesmute: the user would have to specify a region (and/or az) as fields in the payload, or the backup_id would need a namespacing prefix19:01
SlickNikesmute: What robertmyers and amcrn are proposing is that instead of location: <URL> you'd have something like backup-id: <id>, region: <region>. We could then construct the swift URL from the backup-id and region.19:02
*** mattgriffin has quit IRC19:02
robertmyersSlickNik: yes19:02
amcrnSlickNik: that, or backup_id: "<region>:<az>:<id>"19:02
cp16netSlickNik: that sounds way better19:02
esmutethanks for the clarification SlickNik19:02
esmuteyeah.. that could work too.19:03
SlickNikamcrn: yes, that would work too.19:03
esmuteok ill update the BP with that19:03
esmuteone other quesitons19:03
*** thedodd has joined #openstack-trove19:03
SlickNikThinking out loud here. Do we ever have a case for BYOB (bring your own backup?)19:04
esmuteso i am thinking of leveraging the streaming fuctions (save/read) to copy backups from one region to another19:04
grapexSlickNik: Possibly- but I think that's for another blueprint19:04
SlickNikgrapex: fair enough.19:04
grapexHey everyone, the Rax guys have a meeting at this moment19:04
amrithesmute: when you said "how do we specify backup object" were you inquiring about the location of the file where the backup would land, or the object in the database that would be backed up?19:04
robertmyersSlickNik: maybe but not with encryption and checksums19:04
robertmyerssecurity yo19:04
grapexI vote +1 on esmute's blueprint if the changes amcrn and robermyers suggested are taken into account19:04
esmuteamrith: the former19:04
amrithesmute: thx19:04
amcrnSlickNik robertmyers esmute grapex amrith : fwiw, the decision on how to handle region/az (field vs. namespace vs. ?) for this will have large ramifications on how clustering is handled, so the decision should be made with great care.19:04
*** jcru has quit IRC19:04
amrithI'm assuming the former is entire instance19:04
amrithsorry: later19:05
esmutewill creating a greenthread to handle the streaming acceptable?19:05
amrithbackup would be of full instance19:05
amcrn(since you'd want the apis to be consistent)19:05
SlickNik+1 to esmute's bp after the changes as well.19:05
grapexWith some more consideration given to amcrn's concern19:05
grapexEnd of meeting?19:05
SlickNikYup, that's all we have time for.19:06
SlickNikWe'll have to roll over the next bps to the start of the next meeting.19:06
SlickNikThanks all!19:06
grapexThanks SlickNik!19:06
cp16netok19:06
robertmyersthanks!19:06
amcrncp16net: since you're here, a quick comment on the config description before i run to lunch: if there's a way to keep it i18n'able, that'd probably be best.19:06
denis_makogonone question, is my BP about recovery was rejected, right ?19:07
*** jcru has joined #openstack-trove19:08
SlickNik"So the way I see it, this bp has points to address:19:08
SlickNik- For something to be "point in time" recovery, you should be able to recover to any point in time (with reasonable limits on granularity). This doesn't enable that.19:08
SlickNik- This currently doesn't enable anything new over restoring to a new instance (and additionally has the issue that we may overwrite valid data by mistake, making it dangerous)."19:08
*** kevinconway has quit IRC19:08
*** eguz has joined #openstack-trove19:09
SlickNikThose 2 points need to be addressed to consider it, denis_makogon.19:09
cp16netamcrn: yeah i think thats something that we might need19:09
cp16netamcrn: not sure how we normally do that sort of thing tho19:10
espdenis_makogon: you might want to reference the feature in AWS regarding “point in time recovery” although the wording is confusing in the context of trove19:10
amcrncp16net: with _() it's doable, so if these strings were defined in a py, it'd work, but that's pretty nasty.19:10
cp16netamcrn: well that wont work with data in the DB19:11
amcrnright19:11
cp16netthats on hardcoded strings in the log message19:11
amcrni don't have any solutions for you, the thought just came to mind while seeing all of these doc translations fly by19:11
amcrn;)19:11
amcrnthere might be a precedent in another project, not sure19:11
cp16netand i REALLY dotn want all those strings in some magic python file19:11
cp16netthat seems like a bad idea19:11
cp16netyeah i'm not sure if there is somethign that has been done like this19:12
amcrncp16net: we'll just ship trove with a free mobile copy of duolingo19:12
*** eghobo has quit IRC19:12
amcrncp16net: then rake in the affiliate fees and retire to the bahamas19:12
cp16netit seems more like trying to change the name or descrtpions of config params19:12
cp16netwhen they are stored in the db19:12
cp16netlol19:13
cp16net:-P19:13
amcrn:D19:13
*** eghobo has joined #openstack-trove19:13
amcrnalright, lunch, bbl.19:13
cp16netalright peace out19:13
cp16neti was hopful that we could talk about my bps :(19:14
*** eguz has quit IRC19:15
SlickNikcp16net: sorry we couldn't get to them. :(19:19
SlickNikThey'll be on top for the next meeting, though.19:19
*** mattgriffin has joined #openstack-trove19:19
cp16netso thats next week or for wed?19:19
SlickNikNext week at the latest. But I'm not opposed to talking about it during open-discussion of the Wed meeting if time permits. Do you have a preference?19:22
cp16netwell i think 1 of my BP is something that should not be a controversial change19:22
cp16net(trove-manage)19:23
cp16netthe conf descriptions could be a bit more of a convo19:23
*** kevinconway has joined #openstack-trove19:27
openstackgerritKhyati Sheth proposed a change to openstack/trove: Implement Mongodb config groups  https://review.openstack.org/8579519:28
*** thedodd has quit IRC19:29
*** thedodd has joined #openstack-trove19:31
*** thedodd has quit IRC19:31
*** thedodd has joined #openstack-trove19:33
*** sbfox has quit IRC19:34
*** ViswaV has quit IRC19:35
*** doddstack has joined #openstack-trove19:38
*** thedodd has quit IRC19:40
*** freyes_ has quit IRC19:42
*** ramashri_ has quit IRC19:43
*** jcru_ has joined #openstack-trove19:43
*** jcru has quit IRC19:44
*** michael-yu has quit IRC19:54
openstackgerritKaleb Pomeroy proposed a change to openstack/trove: Implements datastore capabilities  https://review.openstack.org/8350319:58
*** jcru_ has quit IRC20:02
*** jcru has joined #openstack-trove20:02
*** harlowja has quit IRC20:03
*** erik508 has joined #openstack-trove20:06
*** grapex has quit IRC20:08
*** parstac_pete_ has joined #openstack-trove20:09
*** russellb_ has joined #openstack-trove20:09
*** russellb has quit IRC20:10
*** erik508_ has quit IRC20:10
*** peterstac has quit IRC20:10
*** russellb_ is now known as russellb20:10
*** parstac_pete_ is now known as peterstac20:10
*** Barker has joined #openstack-trove20:10
*** Barker has quit IRC20:10
*** ViswaV has joined #openstack-trove20:12
*** ViswaV_ has joined #openstack-trove20:13
*** ViswaV has quit IRC20:13
*** ViswaV has joined #openstack-trove20:14
*** ViswaV_ has quit IRC20:14
*** grapex has joined #openstack-trove20:15
*** Barker has joined #openstack-trove20:16
*** harlowja has joined #openstack-trove20:19
*** jmontemayor has quit IRC20:20
*** michael-yu has joined #openstack-trove20:25
*** amcrn has quit IRC20:28
*** freyes_ has joined #openstack-trove20:28
*** ramashri has joined #openstack-trove20:31
*** michael-yu has quit IRC20:32
*** ramashri_ has joined #openstack-trove20:32
*** michael-yu has joined #openstack-trove20:33
*** amcrn has joined #openstack-trove20:33
*** ramashri has quit IRC20:35
*** ViswaV has quit IRC20:37
*** demorris has quit IRC20:39
*** saju_m has quit IRC20:41
*** ViswaV has joined #openstack-trove20:50
*** ViswaV_ has joined #openstack-trove20:51
*** ViswaV has quit IRC20:51
esmutehub_cap, amcrn, SlickNik, vipul, grapex: When you guys have time, can you quickly review https://review.openstack.org/#/c/81379/? Just want to get the percona int-test passing.20:52
*** freyes_ has quit IRC20:53
juicehub_cap, amcrn, grapex, slicknik, vipul - pardon me if I'm out of line but I was thinking this weekend...this blueprint review thing has been going pretty good.  The next step, I think is to have a triaged list of blueprints to focus - like a top 3.  Both the reviewer and the reviewees focus on those blueprints and those blueprints alone.  The reviews get submitted,  2 of the 5 reviewers review it along with the +1'ers.  The reviewee  has a20:59
juice responsibility to turn those changes around within x days (or risk losing their spot) and the reviewers have a responsibility to approve/correct within a day.  Basically get some laser focus on fewer reviewers but get them reviewed in a shorter period20:59
grapexjuice: I like it21:00
grapexI am worried at just three we won't be able to look at enough though- seems like there's a big back log at the moment- but we should start there21:00
hub_capjuice: ++21:01
SlickNikjuice: excellent idea21:01
juicegrapex: the idea is to keep it small and maybe if the flow is working, expand it to a bigger number21:04
*** denis_makogon has quit IRC21:05
juicethe other idea is people know where they stand with their reviews and the expectation is clear.  you core reviewer guys get to say "Not today" or "your's isn't in the spotlight right now" but when it is in the "spotlight" you better be dancing :)21:05
SlickNikWas chatting with dougshelley66 regarding this also, and were thinking about a couple of other things that we can do better regarding bps.21:06
SlickNik1: Pick 4 bps and time-box discussion to ~12-13 mins  per bp.21:06
SlickNik2: At the end of the discussion have a motion to vote with some fixed choices (Approved; Approved with minor edits; Major edits needed before requeue; More discussion time needed - move to next week; Not Approved)21:06
SlickNikWas going to put some information together in a wiki page.21:07
juiceslicknik: though my suggestion was more on the actual reviews themselves.  I think the monday bp review is pretty good given that it's just started.21:08
juicebut when rubber meets the road and patches come it I think some process improvement can be made there21:09
peterstacQuick question: Is there a reason why our CLI treats flavors as int's, whereas nova manages them as UUID's ?21:10
cp16netSlickNik: yeah that would be nice to time box things and then know if your stuff was going to be brought up or not21:11
peterstac(reason I'm asking is that if you add a flavor with letters in it, our CLI chokes on it)21:11
peterstac(wanted to make sure that we should handle UUID's as well before entering a bug)21:12
cp16netpeterstac: flavors have uuids?21:12
cp16neti dont recall see that before21:12
cp16neti know images use uuids21:12
hub_capyes its a bug peterstac21:12
hub_capits well known, trove only had a int validation before we went all uuid on flavors21:13
peterstacWell, they're int's in the list, but under the cover they're UUID's21:13
hub_caplike waaaay legacy21:13
peterstacok, I'll enter a bug then, thx21:13
hub_capare they not getting rid of tha? or allowing to use non int21:13
hub_cappeterstac: plz search first, its been a well known trove bug for like 2 yrs21:13
cp16nethmmm we would have had to deal with it sooner if devstack was creating something with that i guess...21:13
*** dmitryme has quit IRC21:13
hub_capproblem is, we _fix_ the api, we break the contract21:14
hub_capsad trombone21:14
peterstacThey allow non-int - in fact if you create a flavor with 'auto' as the id, it will create a UUID for you21:14
cp16netOH.........21:15
* hub_cap sees a light go off above cp16net 21:15
peterstacubuntu@ubuntu:/opt/stack/python-troveclient$ nova --os-username admin --os-password 3de4922d8b6ac5a1aad9 flavor-create peter auto 512 20 321:15
peterstac+--------------------------------------+-------+-----------+------+-----------+------+-------+-------------+-----------+21:15
peterstac| ID                                   | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |21:15
peterstac+--------------------------------------+-------+-----------+------+-----------+------+-------+-------------+-----------+21:15
peterstac| 3f5b6eef-32c8-42ed-935f-aae44f1dfcf5 | peter | 512       | 20   | 0         |      | 3     | 1.0         | True      |21:15
peterstac+--------------------------------------+-------+-----------+------+-----------+------+-------+-------------+-----------+21:15
cp16nethub_cap: haha yup21:15
openstackgerritJenkins proposed a change to openstack/python-troveclient: Updated from global requirements  https://review.openstack.org/7964621:16
hub_cappeterstac: plz send us multilines like that in a gist21:16
hub_capit hurts my eyes to see that in my txt window21:17
hub_capand frankly i can guarantee my screen is smaller than yours, and im devoting a very small part of it to irssi anyway ;)21:17
cp16netoh boy i have your password now.. :-P21:17
hub_caplol cp16net21:17
openstackgerritJenkins proposed a change to openstack/trove: Updated from global requirements  https://review.openstack.org/8584421:17
peterstaccp16net: for today at least :)21:18
cp16netharh har har21:18
cp16netBender: C'mon, it's just like making love. Y'know, left, down, rotate sixty-two degrees, engage rotors...21:18
hub_capwe all have his pretty table21:19
peterstacLooks like it's already entered: #122625921:19
hub_capman i wish we had the bot that would spew out the whole url fo rthat21:19
peterstachub_cap: gist it is (next time) sorry!21:19
*** achampion has quit IRC21:19
hub_cappeterstac: <3<321:20
*** sbfox has joined #openstack-trove21:23
*** sbfox has quit IRC21:24
*** sbfox has joined #openstack-trove21:24
openstackgerritJenkins proposed a change to openstack/python-troveclient: Updated from global requirements  https://review.openstack.org/7964621:27
cp16nethub_cap: ++ to the openstack bot21:31
*** harlowja is now known as harlowja_away21:31
hub_capsomeone just needs to ask infra im sure21:31
cp16netyeah i bet its just a review away of being added here21:32
*** harlowja_away is now known as harlowja21:35
*** yogesh has quit IRC21:37
hub_capyup21:40
*** Barker has quit IRC21:48
*** sgotliv has quit IRC21:53
*** pdmars has quit IRC22:01
*** michael-yu has quit IRC22:04
*** ramashri_ has quit IRC22:06
*** robertmyers has quit IRC22:06
*** ramashri has joined #openstack-trove22:06
*** amcrn has quit IRC22:08
*** amcrn has joined #openstack-trove22:12
*** cweid has joined #openstack-trove22:14
*** ramashri has quit IRC22:14
*** ramashri_ has joined #openstack-trove22:14
*** achampion has joined #openstack-trove22:20
*** amytron has quit IRC22:31
*** demorris has joined #openstack-trove22:35
*** demorris has quit IRC22:41
*** Barker has joined #openstack-trove22:50
*** Barker has quit IRC22:54
*** jcru has quit IRC22:56
*** mattgriffin has quit IRC22:59
*** eguz has joined #openstack-trove23:03
*** eghobo has quit IRC23:08
*** doddstack has quit IRC23:16
*** saurabhs has quit IRC23:22
*** grapex has quit IRC23:25
*** jamielennox has joined #openstack-trove23:26
jamielennoxhey guys - can i get some core to look at (+A) https://review.openstack.org/#/c/83270/ it's a  -1 line fix that's been open for a while now23:26
*** kevinconway has quit IRC23:28
*** amcrn has quit IRC23:33
*** Barker has joined #openstack-trove23:43

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