Monday, 2014-04-21

*** lnxnut has quit IRC00:12
*** Barker has joined #openstack-trove00:13
*** matsuhashi has joined #openstack-trove00:30
*** freyes has joined #openstack-trove00:31
*** freyes has quit IRC00:36
*** freyes has joined #openstack-trove00:48
*** matsuhashi has quit IRC00:52
*** matsuhashi has joined #openstack-trove00:58
*** nosnos has joined #openstack-trove01:00
*** Barker has quit IRC01:01
*** ViswaV has joined #openstack-trove01:02
*** ViswaV has quit IRC01:12
*** freyes has quit IRC01:23
*** erkules_ has joined #openstack-trove01:32
*** yidclare has joined #openstack-trove01:32
*** erkules has quit IRC01:34
*** razvanm has quit IRC01:59
*** ViswaV has joined #openstack-trove01:59
*** ViswaV_ has joined #openstack-trove02:00
*** ViswaV has quit IRC02:04
openstackgerritYongli He proposed a change to openstack/trove: Apply six for metaclass  https://review.openstack.org/7313602:04
*** haomaiwang has quit IRC02:07
*** haomaiwang has joined #openstack-trove02:07
openstackgerritYongli He proposed a change to openstack/trove: Use six.StringIO/BytesIO instead of StringIO.StringIO  https://review.openstack.org/7391102:20
*** demorris has joined #openstack-trove02:22
*** eghobo has joined #openstack-trove02:51
*** demorris has quit IRC03:01
*** coolsvap|afk is now known as coolsvap03:09
*** eghobo has quit IRC03:15
*** ViswaV_ has quit IRC03:23
*** matsuhashi has quit IRC03:32
*** matsuhashi has joined #openstack-trove03:32
*** matsuhashi has quit IRC03:37
*** nosnos has quit IRC03:46
*** eghobo has joined #openstack-trove04:03
*** michael-yu has joined #openstack-trove04:04
*** michael-yu has quit IRC04:16
*** razvanm has joined #openstack-trove04:19
*** nosnos has joined #openstack-trove04:28
*** matsuhashi has joined #openstack-trove04:29
*** michael-yu has joined #openstack-trove05:45
*** michael-yu has quit IRC05:46
*** nosnos_ has joined #openstack-trove05:51
*** nosnos has quit IRC05:54
*** matsuhashi has quit IRC05:59
*** matsuhashi has joined #openstack-trove06:00
*** nosnos has joined #openstack-trove06:32
*** matsuhashi has quit IRC06:32
*** nosnos_ has quit IRC06:32
*** matsuhashi has joined #openstack-trove06:34
*** razvanm has quit IRC06:38
*** shivam has joined #openstack-trove06:43
*** haomai___ has joined #openstack-trove06:44
*** haomaiwang has quit IRC06:48
*** eghobo has quit IRC07:05
*** michael-yu has joined #openstack-trove07:14
*** haomaiwa_ has joined #openstack-trove07:21
*** haomai___ has quit IRC07:21
*** ViswaV has joined #openstack-trove07:24
*** ViswaV has quit IRC07:28
*** michael-yu has quit IRC07:46
*** michael-yu has joined #openstack-trove07:48
*** michael-yu has quit IRC08:15
*** denis_makogon has joined #openstack-trove09:18
*** ramishra has joined #openstack-trove09:26
*** matsuhashi has quit IRC09:48
*** matsuhashi has joined #openstack-trove09:54
*** haomaiwa_ has quit IRC09:55
*** haomaiwang has joined #openstack-trove09:56
*** coolsvap is now known as coolsvap|afk10:03
*** denis_makogon has quit IRC10:16
*** shivam has quit IRC10:20
*** demorris has joined #openstack-trove10:23
*** demorris has quit IRC10:51
*** freyes has joined #openstack-trove11:08
*** matsuhashi has quit IRC11:22
*** freyes has quit IRC11:26
*** matsuhashi has joined #openstack-trove11:30
*** matsuhashi has quit IRC11:48
*** matsuhashi has joined #openstack-trove11:49
*** achampio1 has joined #openstack-trove12:22
*** achampion has quit IRC12:22
*** ramishra has quit IRC12:40
*** matsuhashi has quit IRC12:42
*** matsuhashi has joined #openstack-trove12:44
*** matsuhashi has quit IRC12:51
*** casanch1 has joined #openstack-trove12:59
*** demorris has joined #openstack-trove13:02
*** ramishra has joined #openstack-trove13:06
*** matsuhashi has joined #openstack-trove13:06
*** matsuhashi has quit IRC13:12
*** matsuhashi has joined #openstack-trove13:21
*** ramishra has quit IRC13:39
imsplitbithey guys13:44
imsplitbitthe python troveclient metadata patch is failing because someone overwrote json.dumps with a static value and didn't replace it at the end of their test13:44
imsplitbitjust wanted to remind everyone that when you replace things for purposes of a test with mocks it's best to store the original in a variable and put it back the way you found it at the end of the test13:45
imsplitbitso as not to affect other peoples tests13:45
*** Barker has joined #openstack-trove13:46
openstackgerritDaniel Salinas proposed a change to openstack/python-troveclient: Add instance_metadata functionality to the trove python library  https://review.openstack.org/8212413:47
imsplitbitI've patched the problem that was affecting the python troveclient metadata patch and resubmitted13:48
imsplitbitplease review and bless if you deem it worthy13:48
*** robertmyers has joined #openstack-trove13:49
*** erkules_ is now known as erkules13:51
*** grapex has joined #openstack-trove13:53
*** nosnos has quit IRC13:53
*** kevinconway has joined #openstack-trove13:55
*** kevinconway has quit IRC13:56
*** kevinconway has joined #openstack-trove14:03
*** freyes has joined #openstack-trove14:06
*** rwsu has joined #openstack-trove14:11
*** thedodd has joined #openstack-trove14:11
*** doddstack has joined #openstack-trove14:14
*** doddstack has quit IRC14:14
*** doddstack has joined #openstack-trove14:14
*** doddstack has joined #openstack-trove14:15
*** doddstack has quit IRC14:16
*** matsuhashi has quit IRC14:17
*** thedodd has quit IRC14:17
*** ramishra has joined #openstack-trove14:21
*** grapex has quit IRC14:24
*** grapex has joined #openstack-trove14:25
*** jcru has joined #openstack-trove14:28
*** jasonb365 has joined #openstack-trove14:28
*** Barker has quit IRC14:46
*** grapex has quit IRC14:55
*** grapex has joined #openstack-trove14:56
*** jasonb365 has quit IRC15:03
*** ViswaV has joined #openstack-trove15:16
*** rueb7363 has joined #openstack-trove15:19
*** ViswaV_ has joined #openstack-trove15:20
*** ViswaV has quit IRC15:22
*** mattgriffin has joined #openstack-trove15:23
openstackgerritViswa Vutharkar proposed a change to openstack/trove: Adds backup/restore support for mongodb  https://review.openstack.org/7833915:24
*** achampio1 has quit IRC15:32
*** achampion has joined #openstack-trove15:33
openstackgerritViswa Vutharkar proposed a change to openstack/trove: Adds backup/restore support for mongodb  https://review.openstack.org/7833915:37
*** freyes has quit IRC15:51
*** jmontemayor has joined #openstack-trove16:00
*** jmontemayor has quit IRC16:01
*** jmontemayor has joined #openstack-trove16:01
openstackgerritSushil Kumar proposed a change to openstack/trove: Resolves volume resize issue  https://review.openstack.org/8031516:02
*** ViswaV_ has quit IRC16:03
*** SushillKM has joined #openstack-trove16:06
*** michael-yu has joined #openstack-trove16:06
*** michael-yu has quit IRC16:12
*** michael-yu has joined #openstack-trove16:17
*** michael-yu has quit IRC16:17
*** coolsvap|afk is now known as coolsvap16:20
*** achampion has quit IRC16:20
*** achampion has joined #openstack-trove16:21
openstackgerritSushil Kumar proposed a change to openstack/trove: Resolves volume resize issue  https://review.openstack.org/8031516:21
*** achampion has quit IRC16:22
SlickNikYou forgot to take out the sudo16:23
SushillKMoooops16:23
SlickNik^ SushillKM16:23
SushillKMmy bad16:23
openstackgerritSushil Kumar proposed a change to openstack/trove: Resolves volume resize issue  https://review.openstack.org/8031516:24
ramishraHi All, can someone point me to trove-guestagent package for fedora or any images with trove-guestagent installed?16:25
SlickNikramishra: Trove doesn't provide images that are pre-built.16:26
SlickNikramishra: we have diskimage-builder elements that you can use with tripleo/diskimage-builder to build your own image, though.16:27
SlickNikramishra: The image elements can be found in the trove-integration repository.16:28
ramishraSlickNick: Thanks...Was looking for shortcut;)16:28
SlickNikramishra: The fedora dib elements for mysql can be found at: https://github.com/openstack/trove-integration/tree/master/scripts/files/elements/fedora-guest16:28
*** ViswaV has joined #openstack-trove16:29
*** achampion has joined #openstack-trove16:32
*** sbfox has joined #openstack-trove16:33
openstackgerritSushil Kumar proposed a change to openstack/trove: Corrects spelling typos  https://review.openstack.org/6938316:40
*** harlowja_away is now known as harlowja16:48
*** amcrn has joined #openstack-trove16:49
*** SushillKM has quit IRC16:53
*** michael-yu has joined #openstack-trove16:59
*** jmontemayor has quit IRC17:07
*** saurabhs has joined #openstack-trove17:08
*** sbfox has quit IRC17:09
*** michael-yu has quit IRC17:13
*** jmontemayor has joined #openstack-trove17:14
*** demorris has quit IRC17:14
*** jmontemayor has quit IRC17:14
*** demorris has joined #openstack-trove17:14
*** SushillKM has joined #openstack-trove17:15
*** michael-yu has joined #openstack-trove17:21
*** SushillKM has quit IRC17:22
openstackgerritNikhil Manchanda proposed a change to openstack/trove-integration: Add support for a neutron-based install  https://review.openstack.org/7812317:22
*** esp has joined #openstack-trove17:23
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168217:27
imsplitbitSlickNik: hey how do I fix the reddwarf failure on the python-troveclient patch?17:36
imsplitbitprovisioning failed17:36
SlickNikimsplitbit: one sec, looking at the patch.17:36
SlickNikimsplitbit: looks like it had a download failure downloading updates from the ubuntu apt repo.17:39
imsplitbityeah17:39
imsplitbitdo I just submit a review with "recheck"? I thought that was for jenkins17:39
SlickNikimsplitbit: If you login to that jenkins box (launchpad creds) you should see an option on the left that says "retrigger"17:39
imsplitbitsorry its been a while for me17:39
imsplitbitahhh17:39
SlickNikimsplitbit: No worries.17:39
imsplitbitgotcha17:39
imsplitbitI'll kick it off again17:40
SlickNikSweet; let me know if you're not seeing the option.17:41
*** eghobo has joined #openstack-trove17:43
imsplitbitI wasn't but my login didn't pre-check trove membership.  I logged out and rechecked it and now it worked17:47
imsplitbitretriggered.17:47
imsplitbitwaiting for next execture17:47
imsplitbitsp17:47
imsplitbitit was failing jenkins tests because someone overwrote json.dumps and didn't put it back17:48
imsplitbitgot all that patched up17:48
SlickNikYup, I saw that. Thanks for fixing that.17:49
SlickNikHeads up folks. BP meeting in a few minutes.17:55
SlickNik#startmeeting BP-review17:58
openstackMeeting started Mon Apr 21 17:58:18 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.17:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:58
openstackThe meeting name has been set to 'bp_review'17:58
SlickNik#undo17:58
amrithSlickNik, ready when you are17:58
SlickNik#endmeeting17:59
openstackMeeting ended Mon Apr 21 17:59:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/bp_review/2014/bp_review.2014-04-21-17.58.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/bp_review/2014/bp_review.2014-04-21-17.58.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/bp_review/2014/bp_review.2014-04-21-17.58.log.html17:59
SlickNik#startmeeting trove-bp-review17:59
openstackMeeting started Mon Apr 21 17:59:40 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.17:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:59
openstackThe meeting name has been set to 'trove_bp_review'17:59
SlickNikokay, that's better.17:59
SlickNikamrith: Let's give folks a couple of minutes to trickle in18:00
kevinconway#topic do permissions work right on this thing?18:01
kevinconwaydarn18:01
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:01
*** ramishra has quit IRC18:02
SlickNikkevinconway: I think only the person who started the meeting can change the topic.18:02
esmutekevinconway: Yeah permission is working.. i just did a /kick kevinconway and you are still here18:03
*** sbfox has joined #openstack-trove18:03
SlickNik#topic: Unify common code in guest agent configurations18:03
SlickNik#topic Unify common code in guest agent configurations18:03
SlickNikmaybe not?18:03
amrithI'll take that as my cue18:03
amrithso, SnowDust and I put this thing together18:04
amrithsubsequently, it appears that hub_cap has made some changes18:04
amrithand those represent the direction we may want to go18:04
hub_caphey so18:04
hub_capafte some thought on this, and a ton of refactoring18:04
amrithso, for the present, I say table this blueprint18:04
hub_capim not sure i like the approach im taking18:04
hub_caplets chat about it for a sec amrith18:04
amrithok, sure18:04
hub_capso there _will_ be datastore specific items that the api/taksmgr need to know about18:05
hub_capand frankly the guest may never care about18:05
hub_caplet me find an exampl eof the one i was lookin at18:05
hub_caphmm its been a while i dont want to waste our time18:05
hub_capso to the config loading snowdust has done18:05
*** freyes has joined #openstack-trove18:06
hub_capi think that it might be valid to have those as config options groups within the main trove config18:06
hub_capcfg.mysql.blah18:06
hub_capsome of them dont matter, like the mount_point18:06
hub_capthat was an easy refactor18:06
hub_capbut some of them like the ports, start to look ugly in  amap18:06
*** demorris has quit IRC18:06
hub_capbut the part that snowdust didnt do was the autoloading18:06
hub_capi think it hsould be based on the datasotres that you have "installed", aka the ones in the database18:07
hub_capnot based on yet another config18:07
hub_capif you don tdeploy couch, dont load its options18:07
hub_capdoes that make sense? should be perty easy to get that list from the db and autoload based on that18:07
robertmyerscould these be in the capabilities BP?18:07
amrithhub_cap, that was a little different from what I was proposing in my bp18:07
hub_caprobertmyers: some of them yes18:07
*** ViswaV_ has joined #openstack-trove18:07
hub_capamrith: sure thats like a first step (what im tlkin about)18:08
hub_caprobertmyers: im not sure that, say, ports for a given datastore need to be in capabilities18:08
hub_caproot_on_create, i think yes18:08
*** ViswaV has quit IRC18:08
robertmyersok18:08
hub_capand yes i know this is less of amirths and more of snowdusts work, and what ive done last wk18:09
SlickNikI agree. I think the ports don't make sense in capabilities.18:09
hub_capbut i think we can move forward w/ some of the autoloading18:09
amrithso hub_cap, looks like we have to align our thoughts on this, maybe we can get it ready for discussion next week?18:09
hub_capand the configuration stuff18:09
hub_capyea i think so amrith18:09
hub_capits perty big18:09
amrithSlickNik: action is mine to follow up with hub_cap18:09
hub_capmight even be a summit talk18:09
SlickNikOkay, let's table this until next week.18:10
amrithhub_cap/SlickNik, I agree. the thrust of my idea is around eliminating duplicated code and there are many places where we are magically defining the same constants18:10
amriththx18:10
hub_capyup amrith ++18:10
SlickNikamrith: Sounds good.18:10
SlickNik#topic Adding datastore and version to the backup API18:10
SlickNikrobertmyers, all yours18:11
hub_caplol that doenst work here ;) but u konw that18:11
hub_caphehe18:11
robertmyerssure18:11
robertmyersbasically we want to add the datastore to the backup api18:11
SlickNikYeah, I know :). I was surprised that meetbot actually responded earlier.18:11
robertmyersI see amcrn had some comments?18:12
SlickNik#link https://wiki.openstack.org/wiki/Trove/backup-metadata18:12
SlickNikYes, there's a couple of comments from him at the bottom of that page.18:12
esmuterobertmyers: As part of https://blueprints.launchpad.net/trove/+spec/cross-region-backup-availability, i am adding datastore and version to the backup table18:13
esmutei am not changing the backup API nor the views to return them though18:13
esmuteperhaps we can work on this in a way we dont step on each other18:13
robertmyersWell, the point is for someone to be able to tell what datastore was backed up18:13
robertmyersSO my BP is to change the view18:14
esmutei will make a change where the datastore is stored in the DB when a backup is started18:15
robertmyersesmute: I'm fine with killing this if you do that as well18:15
amrithrobertmyers, is the version already in someplace and your bp is just to add it to the api?18:15
robertmyersamrith: no, this will add it to the DB18:15
hub_capir confused a bit18:15
hub_capdont u already know the datastore basd on the backup?18:15
robertmyershub_cap: no18:15
esmuteok.. ill take this since i sorta started it.. i'll be syncing with you to make sure it covers what you had in mind18:15
hub_capsure change the view, but isint it tied to an instance, aka, u can generate it18:16
hub_capi dont know if we need to "store it" right?18:16
hub_capor is there no link to an instnace from a backup18:16
robertmyerswell, if you delete the instance then the info is gone18:16
hub_capis it?18:16
esmutehub_cap: it is tied to the instance. Even if the instance is deleted, the we can find the datastore by querying the soft deleted instance18:16
hub_capor is it just DELETED=true18:16
hub_capright esmute18:16
hub_capid rather _not_ dup the storage18:17
robertmyerswe should not use soft deletes18:17
esmutebut the issue comes when a backup is copy from a different region (see my BP)18:17
hub_capif ew can just pull it18:17
hub_caprobertmyers: ummmm i sure hope yer jokin ;)18:17
robertmyershub_cap: no18:17
robertmyersdelete it gone18:17
hub_caplol ok robert-conway18:17
amrithesmute, has a use case where we must store the version18:17
robertmyershey the user requested a delete honor it18:17
robertmyers:)18:18
hub_capsmh robertmyers ;)18:18
amcrnconsidering the underlying datastore-version will be changing on the instance when migrations land, having the current datastore-version isn't useful in determining the datastore-version that the backup was spawned from.18:18
esmuteamrith: Yes. when the backup is copied from a different region, there is no instances (active or deleted) that trove can query to find its datastore18:18
hub_capi think thats valid amrith18:18
*** coolsvap is now known as coolsvap|afk18:18
esmutenor its backuptype... but that is a different story18:18
amrithand add to that amcrn's clarification18:18
amrithseems like it is decided that we must store the datastore version; am I correct?18:19
esmuteamcrn: at least we need to know the datastore name.18:19
esmute*know=store18:19
amrithesmute, ok make that datastore name and version18:19
amcrnsee my question/comment on the wiki; you need the datastore-version + more.18:19
vipulesmute: there won't be a backup in the new region either.. so how does a FKEY help you18:19
robertmyersamcrn: but if the instance changes version the old backup will still be the old version?18:19
esmutevipul: through the datastore version name18:19
*** sbfox has quit IRC18:20
vipulwhich you provide in the api esmute?18:20
esmuteim hoping the datastore version name is unique :P18:20
esmutevipul: nop.. it will be stored in the swift metadata18:20
amcrnrobertmyers: the backup row in the table should always know the exact datastore-version from which is spawned, regardless of whether the instance has moved on.18:21
amcrnwhich it was spawned*18:21
cp16netamcrn: +118:21
robertmyersamcrn: I agree18:21
robertmyerswhich is why I think we should add a row or two to the backup table18:21
esmute+1 robertmyers18:22
cp16netrobertmyers: dont you mean column?18:22
amrithrobertmyers, "a row or two"?18:22
esmuteif not the version, at least the datastore name..18:22
robertmyersor three18:22
amrithcolumns, maybe18:22
amcrncan someone address my point in the wiki about backup/restore strategy?18:22
cp16net:-P18:22
robertmyerscp16net: +118:22
kevinconwaywe should have a column table where we can insert rows18:22
SlickNikYeah, I agree that we need to store this with the backup. Do we need to store the strategy as well?18:23
robertmyersamcrn: well, I wasn't planning on changing the restore with this BP18:23
hub_capversion uuid, ya?18:23
hub_capthatll give u all u need18:23
amrithamcrn, if I understand your comment correctly, just name and version are insufficient; there is additional payload that is required.18:23
robertmyersthis is just to store the data for future use18:23
amrithis that correct?18:23
amcrnamrith: correct18:23
hub_capFUTURE PROOF robertmyers18:23
esmutelol18:24
SlickNikhub_cap: version_uuid, probably yes.18:24
esmuterobertmyers: +1. Restore wont be changed18:24
hub_capyup SlickNik thats all u need18:24
cp16net#agree18:24
esmuteok so yes to adding datastore to backup records?18:24
amcrni guess we're not going to address the fact that the strategy can change at any time, and you'll have backups blowing up.18:25
cp16net#info just need to add the version_uuid to the backup table18:25
robertmyersamcrn: that seems like a new BP18:25
amcrnlet me tl;dr my point: store datastore-version-uuid + backup/restore strategy in 3 columns.18:25
robertmyersamcrn: okay 3 columns it is18:26
hub_capeww i see yer point, but eww amcrn18:26
kevinconwaymake it four and you have a deal18:26
amrithamcrn, why do you need backup_strategy in the backup? shouldn't restore strategy suffice?18:26
hub_capkevinconway: one row default="troll", sound good?18:26
esmuteamcrn: so storing the dataversion-uuid and the type?18:26
SlickNikamcrn: wait what's the 3rd. I understand version_uuid, backup_strategy…and?18:27
amcrnSlickNik: restore_strategy18:27
kevinconwayhub_cap: we can put a hash index on it for super fast lookups18:27
robertmyerswe already have the backup type18:27
esmutethis is what i have so far18:27
esmutehttps://gist.github.com/anonymous/1115167018:27
amrithamcrn, why do you need backup_strategy in the backup? shouldn't restore strategy suffice?18:27
SlickNikrobertmyers: Oh yeah, I thought we had something.18:28
hub_capkevinconway: ;)18:28
amcrnamrith: with a datastore with two competing backup_strategy's, you can't possibly know which one was used if the deployer has flipped between the two at any point in time18:28
robertmyersso the restore uses the backup type to look up the restore strategy18:28
hub_capmaybe the version should have a backup/restore strat18:28
hub_capand we shouldnt allow a change inflight18:29
hub_capaka once u set it in the version table, its done18:29
hub_capfor all of that version18:29
kevinconwaydo we have plans to offer multiple backup/restore strategies per dstore?18:29
amcrnhub_cap: that's another way to do it18:29
vipulhub_cap: +1 i don't see changing a backup strategy is something you should do18:29
hub_capwell it might be18:29
hub_capbut not in the same version18:29
grapexhub_cap: That's too limiting- what if people want to backup a datastore in multiple ways?18:29
amrithkevinconway: I believe not. hence my question.18:29
grapexIn case there's an improvement that comes around18:29
hub_capgrapex: who is people?18:29
hub_capoperators?18:30
grapexYeah18:30
grapextoday we use xtrabackup18:30
cp16netmaybe i want a mysqldump of my database to put it somewhere else and a xtrabackup all the other times18:30
robertmyersok, i think this has been going on for a little too long now18:30
grapexwhat if super xtra backup gets released tomorrow and is incompatable18:30
juicegrapex: +118:30
SlickNikOkay, so let's do this. We all agree on the version_uuid.18:30
hub_capyes seems like the other thing is a spiral at present SlickNik18:30
esmuteWe can store the strategy in the swift metadata? So when the restore is being done, it reads this metadata and knows which strategy to use?18:30
juiceI can see a case where the strategy has been changed and you have an old backup with the prior strategy that you want to restore18:30
amrithamcrn, if a backup is with xtrabackup then there's only one way to restore it. similarly if it is a snapshot there's only one (different) way to restore it18:30
SlickNikAnd we need some more definition around the multi backup-restore strategy case.18:30
amcrnjuice: my point exactly18:30
hub_capesmute: thats sane i think18:30
juiceesmute: that works too18:31
amrithso, I'd suspect that for a given backup, storing just the restore strategy should suffice.18:31
juicethe only requirement is to store the strategy along with the backup18:31
*** sbfox has joined #openstack-trove18:31
juicewhether that is in the database or the swift object does it matter?18:31
vipulso theoretically if a backup occurred with xtrabackup 2.1 .. it shoudl be restorable with xtrabackup 2.218:31
SlickNikSo let's approve this BP, and incrementally add the other case as part of another bp.18:31
hub_capid also suspect that this really wont change a ton in general18:31
kevinconwayso i think this convo has gone way outside the scope of the BP18:31
vipulare we saying that we can only use 2.1 restore?18:31
juiceperhaps in esmute's scenario where you have cross region backups/restore18:31
hub_capjuice: its not something we need to store, its redundant, and will eventually help clog our db18:31
hub_cap:)18:31
hub_capthe app only needs to know about it on restore18:32
esmuteSlickNik: +118:32
SlickNikI'm calling time on this one, for now. :)18:32
hub_capkevinconway: ++ its a spiral18:32
robertmyersSlickNik: +118:32
amcrnwe can approve the uuid only, the point was to dispell the rumor/idea that somehow it was sufficient18:32
esmutewe need backup to store datasstore information... we can add the other stuff incrementally18:32
amcrnfor all use-cases18:32
* hub_cap hands amcrn a wrench18:32
kevinconwayyou could always convert the version_uuid field to a json blob that contains all the other metadata later18:33
juiceesmute: storing it in the metadata seems like a logical approach18:33
SlickNikamcrn: I think we need to still discuss the other case. But later. :)18:33
SlickNikI want to hear about:18:33
amcrnk18:33
SlickNik#topic Move the Trove Guest Agent to its own module18:33
hub_capdont feed the kevinconway18:33
robertmyers#link https://wiki.openstack.org/wiki/Trove/MoveTroveGuest18:33
robertmyerslets do it18:33
vgnbkrGiven the impact to other bps/bugs, could it be fasttracked?18:34
robertmyersthe idea here is a baby step before moving to a separate repo18:34
hub_capI LIKE IT18:34
hub_capway better than tryin to rip it out wholesale18:34
esmuterobertmyers: will trove-common be part of the guest-agent...similar to openstack-common?18:34
robertmyersesmute: it will need some oslo stuff18:35
robertmyersbut for now the plan was just to copy it in plave18:35
robertmyersplace18:35
robertmyersonce it is in a new repo it will have its own oslo and config18:35
cp16netthis sounds like a good idea18:36
*** yogesh has joined #openstack-trove18:36
esmutecool18:36
juicerobertmyers: this is a good approach +118:37
SlickNikrobertmyers: I'm totally on board with this.18:37
grapex+118:37
* cp16net pushes the easy button...18:37
robertmyersSlickNik: juice: cool18:37
*** yogesh has quit IRC18:37
robertmyershahaha18:37
SlickNikApproved. All agree?18:37
espcp16net: :)18:37
amrithagreed: +118:38
annashenguest agent finally gets its own nest18:38
cp16netesp: i really did...18:38
cp16net:-P18:38
SlickNikrobertmyers: Any ideas for the timeline? Trying to address vgnbkr's comment about whether the change would be disruptive...18:38
SlickNikand whether we need to get this in asap.18:38
robertmyersWell, I can put the review up by the end of the week18:39
kevinconwaywhat disruption do you expect? a copy/pasta into another dir shouldn't be too bad of a rebase18:39
robertmyersbasically once this is approved (the reivew) it needs to be merged first18:39
grapexkevinconway: Eeeh, it will and it won't18:39
grapexI think we should prioritize moving it though18:40
SlickNikkevinconway: There's _always_ little things.18:40
grapexit will make reviewing guest agent pull requests much easier18:40
grapexand we will stop making stupid mistakes18:40
SlickNikrobertmyers: done, go forth and do it.18:40
robertmyersSlickNik: ok18:40
SlickNikAnd thanks! :)18:40
esmutegrapex: not so sure about your second point18:40
SlickNik#topic Database log files manipulations18:41
SlickNikdenis_makagon?18:41
kevinconwaythis sounds sinister18:41
grapexkevinconway: The original title was "log file machinations"18:41
esmutegoing once :P18:41
amrithI'd +1 with that old title18:41
amrithSlickNik: question18:42
amriththe BP is set to "Needs Code Review", is that accurate?18:42
amrithor is the BP in need of review/approval?18:42
SlickNikamrith: I think that there was a gerrit patch submitted for it.18:42
amrithseveral as a matter of fact18:43
openstackgerritDoug Shelley proposed a change to openstack/trove: Correct inconsistent state issues with config  https://review.openstack.org/8859118:43
SlickNikamrith: and gerrit updates the bp status automatically based on the Commit Message.18:43
amrithok, I get it18:43
hub_capSlickNik: ?18:43
SlickNikLEt's move on.18:43
hub_capdid they impl that? cuz i used to do it manually18:43
hub_capaka gerrit does bugs but it dindt used to do bps18:43
SlickNikhub_cap: The "code review" piece has worked for me, not the "Committed" piece.18:44
hub_capk18:44
SlickNikBut it's been flakey, not sure why.18:44
SlickNikNext one is denis' too.18:45
SlickNikSo let's table that till he's around.18:45
SlickNik#topic Add backup and restore support for single instance couchbase18:45
hub_capoh this is a terrible idea18:45
hub_capkidddddding18:45
michael-yuSlickNik - i added this one. but i think forgot to put my name18:45
michael-yuhup_cap: :)18:45
hub_capdo we really neeed to discuss this? i mean, yes we need it, approved18:45
esmuteSlickNik: hub_cap spoke. Lets move on :P18:45
SlickNikI'm good with this.18:46
SlickNikWe need to do it. Approved.18:46
amrithbefore you approve it, does it make sense to ensure it is aligned with others that are already doing b&r18:46
amrithtoo late.18:46
robertmyersamrith: I think the review can handle that18:46
amrithrobertmyers, code review?18:47
robertmyersamrith: yes18:47
hub_caprobertmyers: ++18:47
amrithnext!18:47
hub_capits pertty straight forward :)18:47
SlickNik#topic Populate endpoint URLs from Keystone service catalog18:47
SlickNikesmute: your up.18:47
SlickNikyou're*18:47
esmutewell.. the point is simple.. To remove the openstack endpoints from the config and get these URL from keystone catalog18:48
kevinconwayi have a concern with this one18:48
robertmyersesmute: +118:48
kevinconwaythe BP says you are removing the config options18:48
esmutewhat is it kevinconway?18:48
SlickNikIIRC, matt lowery was trying to do something similar (and had a review for it at some point too, I think).18:48
kevinconwayso this is backwards incompatible?18:48
hub_capyea mat-lowery had done this18:48
mat-loweryThere's a patch set for this https://review.openstack.org/#/c/68015/18:48
mat-lowery:)18:48
hub_capi think mat-lowery 's work was valid too18:48
esmuteyou can have the config there but it wont be read by trove18:48
hub_capeven w/ its order of how it retireved18:48
hub_cap*retrieved18:49
esmuteahh i didnt know about that patch mat-lowery18:49
hub_capmat-lowery: correct me, but if there is a config it overrides the service catalot right?18:49
mat-lowerycorrect...the default (in the patch) is to get from catalog18:49
esmuteok.. i can abandon my BP and use mat-lowery's patch18:49
hub_capwait thats the opposite of what i said hehe18:49
hub_capyes esmute18:49
vipulyea i think the default is get from conf18:49
vipulaccording to the patch18:50
hub_capyes i thought so to vipul18:50
hub_capi think it was originally the opposite but we whined18:50
robertmyersas long as we can still override it when needed I'm fine with it18:50
vipulyep, looks much better mat-lowery, sorry it's been waiting in the review state for so long :(18:50
mat-loweryif *_url in conf, use it else use catalog18:50
grapexrobertmyers: ditto18:50
grapexHere at Rax, especially in staging and other environments we don't always have the luxury of using the catalog.18:51
cp16netyup18:51
hub_capgrapex: its more likely we can use the sears catalog than our service catalog in staging18:51
grapexhub_cap: LOL!18:51
robertmyershub_cap: lol18:51
*** ViswaV_ has quit IRC18:51
SlickNikmat-lowery: Looks good at first glance. Will review it later this afternoon.18:51
mat-loweryok thanks18:52
kevinconwayso that's awesome that mat-lowery made the thing backwards compat18:52
hub_capesmute: plz give some review to it as well, to make sure it meets your needs18:52
kevinconwaybut does core have an official stance on how we plan to deprecate config options on occasions like this?18:52
esmutewill do hub_cap. Thanks18:52
grapexkevinconway: I don't see why we need to deprecate them18:52
hub_capkevinconway: i think its an openstak thing, like a N+1 strategy18:52
grapexI think the service catalog is great, if it works18:52
robertmyerskevinconway: it does not deprecate them18:52
hub_capbut for this it wont deprecate18:52
SlickNikkevinconway: I think they're still supported. Just optional.18:52
grapexbut there's plenty of times you may need to override it18:52
kevinconwaySlickNik: that's deprecated18:53
robertmyerskevinconway: ?18:53
kevinconwayeventually they would be removed, yes?18:53
*** ViswaV has joined #openstack-trove18:53
hub_capno thats optional18:53
vipuli hope not18:53
grapexlike if you're trying to boot strap Trove in a vacuum, and maybe keystone or anything like it isn't set up18:53
robertmyerskevinconway: never18:53
hub_capeventually removed is deprecated18:53
kevinconwaydeprecated doesn't mean gone18:53
SlickNikkevinconway: They're not going away.18:53
hub_capoptional is optional18:53
kevinconwayok so diamonds are forever?18:53
hub_capsome orgs will always use those optional configs18:53
hub_capwe will deprecate and remove non heat support for installs18:53
grapexkevinconway: Yes, just consider that we've gone with diamond mode18:53
*** ViswaV_ has joined #openstack-trove18:54
SlickNikTime to move on I think. :)18:54
SlickNik#topic Enable specification of Cinder Volume Types18:54
SlickNikSo this one is mine.18:54
*** ViswaV_ has joined #openstack-trove18:54
SlickNikAnd it's an addition to the conf file to specify the volume_type to use when provisioning a cinder volume.18:55
vgnbkr SlickNik : I get a message that your page is private for the wiki.18:55
SlickNikI'm still drafting this, so I just wanted to get feedback on what people thought.18:55
grapexI like this idea18:55
grapexit should probably become a capability though so we can pick them for each datastore type18:55
SlickNikvgnbkr: The wiki's still not there. So it's still drafting.18:55
vipulSlickNik: at some point we want to tie this to datastore version?18:56
vgnbkrSlickNik: oh, nevermind - I didn't read the link, just clicked on it :-)18:56
vipulgrapex: +118:56
SlickNikgrapex: Yes that's the reason it's still drafting. I'm thinking about whether we should add this to capabilities when we that's added.18:56
hub_capyea we need ot fasttrack capabilities18:56
hub_capsince we have other things that "maybe one day will be a capability"18:57
grapeximsplitbit: Spare thee not the whip!18:57
hub_capi think k-pom has a review up18:57
hub_capso maybe imsplitbit needs to whip us ;)18:57
SlickNikOkay, I have the feedback I was looking for.18:57
kevinconwaywhere there's a whip there's a way!18:57
*** ViswaV has quit IRC18:57
hub_capexactly kevinconway18:57
grapexhub_cap: hopefully not Peter Griffith style18:57
grapexkevinconway: lol18:57
SlickNik+1 on getting capabilities in soon.18:58
SlickNikI think that's all we have time for.18:58
SlickNik#endmeeting18:58
openstackMeeting ended Mon Apr 21 18:58:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-04-21-17.59.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-04-21-17.59.txt18:58
grapexAwesome job SlickNik18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-04-21-17.59.log.html18:58
cp16netnice18:58
SlickNikThanks folks!18:58
hub_capTIME18:59
hub_capoh we got meetbot in here?!?! thats cool! i didnt even realize it18:59
hub_caphehe18:59
cp16nethub_cap: you were late to the party18:59
cp16net:0P18:59
hub_capcp16net: yes i am18:59
grapexSlickNik: Witht he meetbot does that mean we can hold the normal meetings here as well?19:00
cp16neti guess we technically could19:01
SlickNikgrapex: Probably still want to do that in #openstack-meeting-alt since that's what other OpenStack folks do.19:02
SlickNikalso CI/docs other cross project folks ofter hang out there and often jump into discussions.19:02
grapexSlickNik: Ok, anything to get out of typing those few characters to join it19:05
esmuteHi mat-lowery, i saw your patch. it looks great.. better than what i would've put there. Just one comment about the method to get the URLs from catalog.19:10
esmuteother than that, i looks good to me19:10
esmute*i=it19:11
mat-loweryesmute: Ha. Well I had 3 months to work on it. :)19:11
mat-loweryI'll check out your review.19:12
mat-loweryThanks.19:12
esmuteim not that egocentric :p19:12
mat-loweryesmute: I replied to your review. We can do back and forth on Gerrit or here. Basically my version insists on exactly one match--otherwise you get an exception. sc.url_for() will quietly return the first of potentially multiple matches. Thoughts?19:17
mat-loweryBy insisting on exactly one match, do we prevent deployers from using the wrong or less-than-ideal endpoint? I'm not sure.19:19
mat-loweryjamielennox from Keystone has argued that whether it's one or multiple matches, the fact remains that the query returned results according to your filter. But we control the filter.19:21
mat-loweryAnd the deployer can affect the filter and unknowingly get the first of multiple matches. Is this OK? This is the question I have.19:22
*** freyes has quit IRC19:29
grapexhub_cap SlickNik vipul: Does anyone remember / know why the trove-api doesn't use eventlet monkey patch the same as taskmanager, the guest, conductor etc?19:41
grapexFor example, trove/cmd/taskmanager.py calls eventlet.monkey_patch(thread=True) if debugging isn't turned on19:42
grapexbut trove-api's cmd script doesn't have that19:42
grapexit calls monkey_patch in trove/common/wsgi.py, but "all=False" which may mean threading isn't enabled19:43
grapexdo any of you remember / know why it's different? Was this to avoid some awful wsgi issue?19:43
* hub_cap shrugs19:45
*** jmontemayor has joined #openstack-trove19:46
*** freyes has joined #openstack-trove19:49
*** eghobo has quit IRC19:51
*** eghobo has joined #openstack-trove19:51
*** thedodd has joined #openstack-trove19:55
*** amcrn has quit IRC19:58
*** mattgriffin has quit IRC20:01
*** jmontemayor has quit IRC20:05
*** jmontemayor has joined #openstack-trove20:05
esmuteHi mat-lowery. i think it is ok how you have it. The reason i suggested this way was because i was looking at your code and thought it was something similar that sc.url_for() does. But if the intention is to have it that way, then im fine.20:06
*** mattgriffin has joined #openstack-trove20:07
esmutei changed my review and +1'd20:08
amrithhub_cap, when you wanna chat re: config options and things?20:08
amrithhub_cap, would like to speak with you before I wade into https://review.openstack.org/#/c/86808/20:09
mat-loweryesmute: Gotcha. Thanks. I haven't convinced myself that the RegionAmbiguity is always the right thing to do. I guess I could argue that because of *_url's lack of ambiguity, this patch set continues that. But some deployer could come along and say, "Just use whatever endpoint is available. I don't care." I don't know if that is a real use-case.20:10
hub_capamrith: u can look @ that first, it doesnt really factor into it20:10
hub_capid like to wait for snowdust too20:10
hub_capso maybe tomorrow amrith ? im not sure where snowdust is, maybe its a holiday?20:11
amrithhub_cap, I hear snowdust snoring right now20:11
amrithso yes, tomorrow20:11
hub_caphehe amrith20:12
amrithhub_cap, last I chatted with him, he was in India and I don't think there's a holiday tomorrow20:12
amrithbut we can check tomorrow20:12
hub_capill be around most of the day except for a few hrs20:12
amrithlikewise20:12
amrithlate morning (eastern) may be best for all20:13
amrithI'll give a shout then20:13
*** freyes has quit IRC20:15
*** michael-yu has quit IRC20:16
hub_caphokey amrith20:17
*** yidclare has quit IRC20:20
esmutemat-lowery: I think you are right. It is safer to have it return a non ambiguous endpoint. An openstack deployment will have multiple regions so no specifying one could lead to a compute being provisioned on the other side of the world or a volume being created in a different region.20:21
hub_capand fwiw, i -2'd my own revies for the rest of this patch series amrith20:23
hub_capcuz im not sure its correct :)20:23
esmutemat-lowery: when you can, can you put a patch to devstack to remove https://github.com/openstack-dev/devstack/blob/master/lib/trove#L150 and  https://github.com/openstack-dev/devstack/blob/master/lib/trove#L170 and add a default region (RegionOne)20:23
*** michael-yu has joined #openstack-trove20:26
mat-loweryesmute: Good catch. Will do. Thanks!20:28
esmuteCool!20:29
esmutelets get it merged... because i need it :P20:29
mat-loweryesmute: Gotcha.20:31
*** michael-yu has quit IRC20:33
*** yidclare has joined #openstack-trove20:40
SlickNikpeterstac: Saw your patches to tempest. Nice start! :)20:47
SlickNik(And thanks!)20:48
peterstacThanks, we'll see how the review goes ;)20:55
*** khyati_ has joined #openstack-trove21:03
peterstacSlickNik: I've updated the etherpad https://etherpad.openstack.org/p/trove-tempest-items with my review link21:03
peterstacSlickNik: I'm looking at quotas and pagination (under the API section) and in poking around the existing tests it looks like they both rely on instances being created - should they be moved to the 'Guest Related' section?21:03
SlickNikpeterstac: Yes, if that's the case (I wasn't sure if all limits testing needed instances, so I left them out).21:04
SlickNikpeterstac: btw, looks like you're gonna need an image to use for the tests soon.21:07
peterstacSlickNik: Yeah, I was wondering how that was going21:08
SlickNikpeterstac: Been busy with other things; so haven't really had a chance to look into it yet.21:09
SlickNikpeterstac: But now I have a forcing function. :)21:09
*** mattgriffin has quit IRC21:10
peterstacSlickNik: Let me know if I can lend a hand (besides providing motivation ;) )21:10
SlickNikpeterstac: I'm already motivated now; Once I figure out how to make the CI/Infra pieces fit together to do this, I'll let you know.21:13
peterstacSlickNik: Sounds good, thx21:18
imsplitbitdougshelley66: where is the bp for replicaiton/topology?21:24
grapexSlickNik: By the way: https://bugs.launchpad.net/trove/+bug/131078521:27
grapexI'm writing a fix21:27
grapexwe may want to mark that as Critical21:27
*** casanch1_ has joined #openstack-trove21:28
*** casanch1 has quit IRC21:30
*** casanch1 has joined #openstack-trove21:30
SlickNikgrapex: Thanks for the heads up!21:30
imsplitbitdougshelley66: are we wrapping the topology path in with the replication-v1 bp? or should I assemble one of my own just for the /topology path and storage?21:30
*** khyati_ has quit IRC21:31
*** casanch1_ has quit IRC21:32
*** mattgriffin has joined #openstack-trove21:34
*** casanch1 has quit IRC21:35
*** openstackstatus has quit IRC21:35
openstackgerritTim Simpson proposed a change to openstack/trove: Make sure eventlet starts correctly  https://review.openstack.org/8942521:36
grapexTalk to you all tomorrow!21:37
*** openstackstatus has joined #openstack-trove21:37
*** robertmyers has quit IRC21:37
imsplitbityeah I'm out too21:37
imsplitbity'all have a good one21:37
*** robertmyers has joined #openstack-trove21:38
*** grapex has quit IRC21:39
openstackgerritRanjitha Vemula proposed a change to openstack/python-troveclient: Remove Duplicate ClientExceptions and Merge  https://review.openstack.org/8032821:40
*** robertmyers has quit IRC21:42
dougshelley66imsplitbit - sorry i missed your ping21:45
dougshelley66maybe we can chat with vgnbkr and glucas tomorrow about what makes sense for the BP21:46
*** datsun180b has joined #openstack-trove22:05
*** kevinconway has quit IRC22:05
*** datsun180b has left #openstack-trove22:07
*** yidclare has quit IRC22:08
*** michael-yu has joined #openstack-trove22:40
*** thedodd has quit IRC22:42
*** mattgriffin has quit IRC22:49
*** eguz has joined #openstack-trove23:03
*** eghobo has quit IRC23:06
*** khyati_ has joined #openstack-trove23:12
*** saurabhs has left #openstack-trove23:15
*** jcru has quit IRC23:37
openstackgerritNikhil Manchanda proposed a change to openstack/trove-integration: Trove guestagent should not use sample conf  https://review.openstack.org/8847823:47
openstackgerritNikhil Manchanda proposed a change to openstack/trove-integration: Add support for a neutron-based install  https://review.openstack.org/7812323:47
openstackgerritNikhil Manchanda proposed a change to openstack/trove-integration: Clean up redstack to use SERVICE_HOST  https://review.openstack.org/7112823:47
openstackgerritA change was merged to openstack/trove-integration: Clean up redstack to use SERVICE_HOST  https://review.openstack.org/7112823:49
*** openstackgerrit has quit IRC23:50
*** openstackgerrit has joined #openstack-trove23:50
*** rueb7363 has quit IRC23:56

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