Wednesday, 2014-04-16

*** ChanServ changes topic to "Restarting gerrit really quick to fix replication issue"00:00
*** pdmars has quit IRC00:00
*** ChanServ changes topic to "Trove Openstack Database as a Service | Docs https://github.com/openstack/trove | Channel Logs http://eavesdrop.openstack.org/irclogs/ | IRC must read http://sackheads.org/~bnaylor/spew/away_msgs.html"00:02
*** demorris has quit IRC00:10
*** achampion has joined #openstack-trove00:10
*** NehaV has joined #openstack-trove00:13
*** saurabhs has left #openstack-trove00:14
*** yidclare has quit IRC00:16
*** Barker has joined #openstack-trove00:20
*** NehaV has quit IRC00:22
*** matsuhashi has joined #openstack-trove00:30
*** eguz has quit IRC00:45
*** ViswaV_ has quit IRC01:07
*** Barker has quit IRC01:09
*** michael-yu has quit IRC01:09
*** rueb7363 has joined #openstack-trove01:20
*** amcrn has quit IRC01:39
*** matsuhashi has quit IRC01:40
*** haomaiw__ has quit IRC01:42
*** matsuhas_ has joined #openstack-trove01:43
*** haomaiwang has joined #openstack-trove01:43
*** haomaiw__ has joined #openstack-trove02:02
*** haomaiwang has quit IRC02:05
*** rueb7363 has quit IRC02:28
*** rueb7363 has joined #openstack-trove02:28
*** coolsvap|afk is now known as coolsvap02:35
*** harlowja is now known as harlowja_away02:35
*** ViswaV has joined #openstack-trove02:38
*** ViswaV_ has joined #openstack-trove02:39
*** ViswaV has quit IRC02:42
*** matsuhas_ has quit IRC02:49
*** matsuhashi has joined #openstack-trove02:49
*** matsuhas_ has joined #openstack-trove02:52
*** matsuhashi has quit IRC02:52
*** matsuhas_ has quit IRC02:58
*** demorris has joined #openstack-trove03:05
*** NehaV has joined #openstack-trove03:28
*** demorris has quit IRC03:34
*** nosnos has quit IRC03:35
*** rueb7363 has quit IRC03:43
*** shivam has quit IRC03:44
*** rueb7363 has joined #openstack-trove03:48
*** NehaV has quit IRC04:08
*** ViswaV_ has quit IRC04:22
*** sbfox has joined #openstack-trove04:23
*** nosnos has joined #openstack-trove04:25
*** saju_m has joined #openstack-trove04:27
*** saju_m has quit IRC04:27
*** coolsvap is now known as coolsvap|afk04:35
*** sbfox has quit IRC04:41
*** achampio1 has joined #openstack-trove04:42
*** achampion has quit IRC04:44
*** achampion has joined #openstack-trove04:47
*** rueb7363 has quit IRC04:48
*** achampio1 has quit IRC04:48
*** coolsvap|afk is now known as coolsvap04:52
*** denis_makogon has joined #openstack-trove06:09
openstackgerritAnna Shen proposed a change to openstack/trove-integration: Add neutron switch for ini tests  https://review.openstack.org/8785606:14
*** flaper87|afk is now known as flaper8707:04
*** iartarisi has joined #openstack-trove07:19
*** denis_makogon has quit IRC08:25
*** sbfox has joined #openstack-trove08:44
*** eghobo has joined #openstack-trove08:51
*** SushillKM has joined #openstack-trove08:51
*** SushillKM has left #openstack-trove09:11
*** fifieldt has joined #openstack-trove09:12
fifieldthi all09:12
*** SnowDust has joined #openstack-trove09:18
*** nosnos has quit IRC10:07
*** nosnos has joined #openstack-trove10:12
*** dmakogon_ is now known as denis_makogon10:14
denis_makogonfifieldt, hi10:14
fifieldthi :)10:16
*** demorris has joined #openstack-trove10:16
*** eghobo has quit IRC10:21
*** SnowDust has quit IRC10:22
denis_makogonfifieldt, what's up?10:22
fifieldtmany things :)10:22
fifieldtI've put in about 9 hours of work today so far on testing trove and fixing docs and packaging10:23
fifieldtone thing that would be really awesome, is if you have a nice, easy guide to create the images that trove uses10:23
denis_makogonfifieldt, of course, images from Trove is the real bottleneck at this time10:31
fifieldtI don't need images10:31
fifieldtjust instructions on how to create them10:31
fifieldt:)10:31
*** sbfox has quit IRC10:32
denis_makogonfifieldt, that's what i'm talking about, now we don't have any pure standard way to create images outside the integration or devstack10:32
fifieldtI don't even need a standard way :)10:32
fifieldtjust a way10:32
fifieldtwithout any method at all, trove is unusable for real people :)10:33
*** sbfox has joined #openstack-trove10:33
denis_makogonfifieldt, agreed10:33
denis_makogonfifieldt, but we could say, use cloudinit to deploy the agent to vanilla image10:34
fifieldtis that method written down somewhere?10:34
*** nosnos has quit IRC10:34
*** nosnos has joined #openstack-trove10:35
*** SnowDust has joined #openstack-trove10:35
*** nosnos has quit IRC10:39
*** iartarisi has left #openstack-trove10:48
*** demorris has quit IRC10:48
fifieldtdenis_makogon ?10:57
*** nosnos has joined #openstack-trove11:06
amrithfifieldt: yes, these procedures are written down. I know that a couple of people have discussed it in the recent past. I'll find a link for you.11:08
fifieldtgreat, that would be excellent11:08
*** coolsvap is now known as coolsvap|afk11:15
denis_makogonfifieldt, cloudinit mechanis is not described in any docs, i suppose11:18
fifieldtthanks for the confirmation denis_makogon11:19
fifieldtthis is, I believe, precisely the problem we need to solve11:19
denis_makogonpoor doc coverage is the huge issue11:19
fifieldtcheck it out, denis_makogon: http://docs-draft.openstack.org/35/87135/12/check/gate-openstack-manuals-tox-doc-publish-checkbuild/1c497b4/publish-docs/trunk/install-guide/install/apt/content/trove-install.html :)11:20
fifieldtif we can get the image stuff down11:21
fifieldtthat's the major thing11:21
amrithfifieldt ... I was going to ping you about something else as well, got a second?11:24
*** ashestakov has joined #openstack-trove11:24
fifieldtif you can put up with me being slow and tired, sure :D11:24
amrithok, let's try11:24
amrithabout https://review.openstack.org/#/c/87135/11:24
amrithI'm curious what the 'openstack way' is.11:25
amrithBut, it seems like Laurel was working her way through review you comments (some from you)11:25
amrithand now you are submiting patch sets over hers11:26
amrithnot sure what the intent is11:26
amrithshould she continue to work on it11:26
amrithor are you now in charge?11:26
fifieldtto be honest - this extent of change is abnormal11:26
amrithI wasn't asking about the amount of change11:26
fifieldtI decided to do it because I figured Laurel was asleep11:26
fifieldtand because we need this quite urgently11:27
amrithI was asking about the process of submitting patches in someone elses bug fix11:27
fifieldtin a normal case11:27
fifieldt(just talking about docs here) you can get people submitting fixes to someone else's patch11:27
amrithit would be more polite to let her know, maybe? how'd you like the same thing done to you?11:27
fifieldtbut only for minor thing11:27
fifieldtamrith, I did send her an email11:27
amrithOK, just curious what the openstack way was. I suspect informing someone that you are going to submit patch sets on their bug fix is the norm; I'd have expected that waiting for a reply would be respectful but I guess I was wrong11:28
amriththanks for the clarification11:28
fifieldtamrith, this is a little bit of a special case11:28
amrithwe're all special cases ;)11:29
fifieldtno, I really do hope Laurel is feeling OK11:29
fifieldtI'm happy to jump on the phone if needed11:29
fifieldther work was a fantastic basis11:29
amrithI'll let you sort that out with her. maybe jumping on the phone first would be a better way to do things in the future; just saying11:29
fifieldtamrith, though, as above, due to timezones - that would not have been possible in this case11:30
amrithwell, you don't reward a person for 'fantastic work' this way (at least not where I come from)11:30
fifieldtamrith, she is still receiving author credit for the patch11:30
amrithI was going to ask her about documentation on making images (which she has). I think I'll hold off on that. As for "credit", just remember, not all of us do this stuff for "credit".11:30
fifieldtI'm in this for fun too, amrith :)11:31
amrithwhat about Laurel, you think this is fun for her?11:32
amrithI'll let you explain it to her, I'm done. And if you want image documentation, you can ask her for it.11:32
amrithtake care11:32
fifieldtthanks, amrith11:32
fifieldtI hope your day improves from this beginning11:32
fifieldtsorry again for the ruffled feathers11:32
amrithI tend to have a live frog for breakfast each day, that way it only gets better. Today I don't need the live frog breakfast.11:33
fifieldtnice :D11:33
amrithfifieldt: by the way, not my feathers. I'm bald.11:38
amrithdenis_makogon: you there?11:39
amrithdenis_makogon: sent you email with a q; thx11:41
denis_makogonamrith, saw your email11:42
denis_makogonamrith, most of the questions are appear because of lack knowledge about trove, i guess11:43
denis_makogonamrith, (a) In particular, it would be good to understand exactly what the limitations of the proposed implementation are likely to be. This could include things like configurations that would work, storage engines that would be supported (or not), performance considerations, etc.,11:43
denis_makogonthat's your first question, it's fully covered with the wiki page11:44
amrithdenis_makogon: i don't follow. email was about neutron bug that is breaking my build ;)11:44
denis_makogonamrith, ah, about that11:44
amrithyou are talking about different email ...11:44
amrithabout the email you are refering to, maybe worth putting on agenda for today's meeting.11:44
denis_makogonamrith, puting such things to agenda will blow meeting out11:45
denis_makogonamrith, we should deal with it, out of the meetings11:45
amrithhow's the best way to address?11:45
amrithworks for me11:45
amrithnot right now though, I have to get in a car and spend 45 minutes with a bunch of people who are texting, eating or doing make-up (while driving)11:46
amrithwant to pick a time? could do irc if that's what you had in mind11:46
denis_makogonneutron problem is not our problem11:46
denis_makogonit'll be fixed asap11:46
amrithwell, it is mine ... I have had about 51 tries at getting it past zuul11:47
amrithpersonally, I think it is a conspiracy11:47
amrith;)11:47
denis_makogonamrith, i read thread at bug report, so it looks like it should be fixed soon11:48
amrithwould IRC in maybe 1 hour or 75min work for you?11:48
*** sbfox1 has joined #openstack-trove11:48
amrithdenis, my concern is that I'm not sure I know which bug it is ... seems like it isn't (exactly) one of the bugs reported/attributed.11:48
*** sbfox has quit IRC11:48
amrithbut something nearby11:48
amrithbut you are right, I hope it gets fixed soon11:49
amrithanyway, re: blueprint for snapshot, want to pick a time? either we could do later this morning (in about an hour or 1:15)?11:49
amrithI'm going to sign off now, if you would please send me an email as anything you say me be lost in the irc traffic and my bouncer isn't quite doing scrollback correctly. will talk later.11:50
denis_makogonamrith, yes, lets talk later11:58
*** nosnos has quit IRC12:17
*** achampion has quit IRC12:23
*** sbfox1 has quit IRC12:27
SnowDustdenis_makogon, saw ur comments on  https://review.openstack.org/7032212:29
SnowDustmakes sense .. i will do this today12:30
SnowDustsuppose someone not doing it ;)12:30
denis_makogonSnowDust, i guess no12:30
SnowDustyes ..so i will do this as a patchset update12:30
denis_makogoni think OpenStack infra needs to do this automatically12:31
denis_makogonthe gate job should look like the "requirements" job12:31
*** pdmars has joined #openstack-trove12:52
*** sbfox has joined #openstack-trove12:53
*** Barker has joined #openstack-trove12:57
*** pdmars has quit IRC12:58
*** demorris has joined #openstack-trove12:59
*** chipc has quit IRC13:01
*** chipc has joined #openstack-trove13:01
*** pdmars has joined #openstack-trove13:03
*** jcru has joined #openstack-trove13:07
fifieldtthis make sense to anyone ... https://bugs.launchpad.net/trove/+bug/1308529 ?13:09
*** sbfox has quit IRC13:11
*** SnowDust has quit IRC13:13
*** achampion has joined #openstack-trove13:16
openstackgerritA change was merged to openstack/trove: Correct the command to stop cassandra server  https://review.openstack.org/8208013:17
*** NehaV has joined #openstack-trove13:17
*** NehaV has quit IRC13:29
*** mattgrif_ has joined #openstack-trove13:34
*** NehaV has joined #openstack-trove13:38
openstackgerritDaniel Salinas proposed a change to openstack/trove: Implement topology api  https://review.openstack.org/8797013:48
*** ViswaV has joined #openstack-trove13:50
*** ViswaV_ has joined #openstack-trove13:51
*** robertmyers has joined #openstack-trove13:51
amrithdenis_makogon: yt? sorry I was stuck in traffic. also thanks for kicking 82080 free.13:51
*** casanch1 has joined #openstack-trove13:52
*** sbfox has joined #openstack-trove13:53
*** ViswaV has quit IRC13:55
casanch1hi, is it possible to install a single instance of trove with api, taskmanager and guestagent in devstack?13:55
casanch1I'm following this: https://wiki.openstack.org/wiki/Trove/installation, but it fails because it cannot find enable_service, which I found are: tr-api, tr-tmgr but I cannot find the one for guestagent13:56
denis_makogoncasanch1, you are able to install trove with devstack, but, unfortunately, you are not able to create instance through trove13:57
denis_makogoncasanch1, take a look at https://github.com/openstack/trove-integration13:57
*** mattgrif_ has quit IRC13:58
denis_makogonamrith, cassandra patch landed13:58
amrithdenis_makogon: yes, thanks. it needed your magic touch13:58
denis_makogonamrith, yeah, of course =))13:58
denis_makogonamrith, now we can discuss your previous email13:58
denis_makogonamrith, can we ?13:58
amrithjust got into office and have a meeting in 1 minutes13:59
amrith1 minute13:59
amrithwhat time is it for you now?13:59
denis_makogon5 PM14:00
amrithhere's waht the rest of my day looks like14:00
amrithi have this and another meeting till about 1pm (which is 3 hours from now)14:01
amrithwe have the trove meeting at 2pm14:01
*** sbfox has quit IRC14:01
amrithcould we meet between 1pm and 2pm? that would be between 8pm and 9pm your time?14:01
denis_makogonyes, we can14:02
denis_makogonping me14:02
amrithwilco, thx denis14:02
denis_makogonwhen you'll be ready14:02
denis_makogonamrith, thx to you too14:02
openstackgerritDaniel Salinas proposed a change to openstack/trove: Add instance metadata functionality to trove  https://review.openstack.org/8212314:16
*** NehaV has quit IRC14:18
*** fifieldt has quit IRC14:24
*** ViswaV_ has quit IRC14:24
*** kevinconway has joined #openstack-trove14:26
*** NehaV has joined #openstack-trove14:37
*** thedodd has joined #openstack-trove14:50
*** jmontemayor has joined #openstack-trove14:50
*** coolsvap|afk is now known as coolsvap14:51
*** sbfox has joined #openstack-trove15:17
*** shivamshukla has joined #openstack-trove15:48
*** NehaV has quit IRC15:50
*** NehaV has joined #openstack-trove15:50
*** grapex has joined #openstack-trove15:58
*** eghobo has joined #openstack-trove16:03
*** jmontemayor has quit IRC16:05
*** Barker has quit IRC16:06
*** grapex has quit IRC16:06
*** Barker has joined #openstack-trove16:06
*** grapex has joined #openstack-trove16:07
*** shivamshukla has quit IRC16:11
*** demorris has quit IRC16:13
*** hub_cap has quit IRC16:15
*** jmontemayor has joined #openstack-trove16:18
*** hub_cap has joined #openstack-trove16:18
*** cp16net has quit IRC16:32
*** sbfox has quit IRC16:32
*** sbfox has joined #openstack-trove16:32
*** demorris has joined #openstack-trove16:33
*** shivam has joined #openstack-trove16:36
*** cp16net has joined #openstack-trove16:45
*** cp16net has quit IRC16:50
*** cp16net has joined #openstack-trove16:51
*** harlowja_away is now known as harlowja16:51
*** cp16net has quit IRC16:54
*** cp16net has joined #openstack-trove16:54
*** cp16net has quit IRC16:54
*** cp16net has joined #openstack-trove16:55
amrithdenis_makogon: I'm back16:57
*** amcrn has joined #openstack-trove16:57
*** zuqiang has joined #openstack-trove17:00
*** amcrn has quit IRC17:10
*** eghobo has quit IRC17:11
*** eghobo has joined #openstack-trove17:11
*** denis_makogon_ has joined #openstack-trove17:12
*** denis_makogon has quit IRC17:13
*** denis_makogon_ is now known as denis_makogon17:13
denis_makogonamrith, i'm in17:13
*** dmakogon_ has joined #openstack-trove17:13
*** demorris has quit IRC17:14
*** ViswaV has joined #openstack-trove17:17
*** ViswaV_ has joined #openstack-trove17:19
amrithHi denis17:20
amrithanytime you are ready, let's start17:20
denis_makogon5 mins17:21
amrithnp. take ur time17:21
denis_makogonlets start17:22
*** ViswaV has quit IRC17:22
denis_makogonlet me find your email17:22
denis_makogonlets go through all your questions17:22
denis_makogonamrith, can we ?17:23
amrithsure17:23
denis_makogonwe have 30m before the meeting17:23
amrithlet me find the email17:23
*** michael-yu has joined #openstack-trove17:23
amrithgot it17:23
denis_makogoncould you post your questions and i'll try to answer them17:24
denis_makogoni'd like to deal with it once and forever17:24
amrithI can't guarantee that but I'll give it a shot17:24
denis_makogonlets go17:24
denis_makogonthe question A17:25
amrithfirst, what are the limitations of this approach, what configurations work, don't work. what storage engines, etc17:25
amrithso at a high level17:25
amrithdoes a trove instance necessarily have only one cinder volume17:26
amrithdoes that cinder volume have LVM?17:26
amrithor some such thing that will support snapshot capability17:26
denis_makogonamrith, yes cinder has lvm, but it's optional17:26
amrithwill it be required for trove17:26
amrithwill it be required for this implementation of snapshot17:27
denis_makogonlimitations: if instance has no cinder volume (ephemeral) - snapshot strategy is not applicapable17:27
amrithso that is a limitation that should be listed/documented17:27
amrithand maybe the code should check or maybe it will make a snapshot call and get an error17:27
denis_makogonof course17:28
amrithalso if instance has a cinder volume without lvm (if that's possible) it won't work, I assume17:28
openstackgerritRamashri Umale proposed a change to openstack/trove: Fix prepare call for redis guest agent  https://review.openstack.org/8486317:28
denis_makogonlets first talk about Trove and then about CInder and LVM17:28
amrithok17:28
amrithlet's talk about trove17:29
amrithwill trove store data only on a cinder volume?17:29
denis_makogonamrith, yes17:29
amrithor ephimeral?17:29
denis_makogonamrith, because volume is mounted directly to database storage directory17:29
amrithephemeral17:30
amrith[sp]17:30
denis_makogonamrith, if ephemeral is used flow will fail17:31
amrithwhat do you mean by "flow will fail".17:31
denis_makogonbackup will be marked as FAILED17:31
amrithok, in other words one limitation is that the trove instance must have data stored on a cinder volume.17:32
denis_makogonyes17:32
amrithcan a trove instance have >1 data volume17:32
denis_makogonno17:32
amrithnow or forever?17:32
denis_makogonyou cannot mount more that one remote storage into the one mount point17:32
denis_makogonamrith, forever17:33
*** SnowDust has joined #openstack-trove17:33
amriththat's interesting17:33
denis_makogonamrith, databases stores its data in one place17:33
SnowDusthi all17:33
denis_makogonin general17:33
amrithodd, I use MySQL instances with data in one place and logs in another17:33
denis_makogonamrith, we're talking only about data17:34
denis_makogonamrith, backup is the stream of the data and only17:34
amrithso, let me try this again17:35
amrithlet's say we talk mysql only, and innodb only17:35
denis_makogonyes17:35
amrithinnodb stores its data in datadir17:35
denis_makogonyes17:35
amrithit also stores a redolog17:35
denis_makogonvolume gets mounted into the datadir17:35
denis_makogonamrith, yes17:35
*** yogesh has joined #openstack-trove17:36
denis_makogonamrith, Trove doesn't work with redo logs or bin logs, yet17:36
*** yidclare has joined #openstack-trove17:36
amrithyou are beginning to scare me, a little17:36
amrithbut go on17:37
denis_makogonamrith, why am i scaring you ?17:37
amrithwhat are the default values of datadir and innodb_data_home_dir in trove17:37
denis_makogon/var/lib/mysql17:37
amrithare we requiring that innodb_data_home_dir be null (or not set)17:37
amrithso ibdata will go into /var/lib/mysql?17:38
denis_makogonsorry, i'm not so familiar with mysql17:39
amrithok, so let's pick a data store that will be implemented in your initial iteration17:39
denis_makogonaccording to actual code, we're relaying that DB data is stored at datadir17:39
amrithi see17:39
denis_makogonok, if that will be easier for us, then lets pick cassandra17:40
amrithso is innodb_file_per_table set by default in mysql?17:40
denis_makogonyes17:40
denis_makogonamrith, https://github.com/openstack/trove/blob/master/trove/templates/mysql/config.template17:40
amrithso one thing I'm not sure is this ...17:41
denis_makogonamrith, that's what mysql uses as the base config17:41
amriththe config file you sent me17:41
amrithis that something that a user of trove can change?17:41
amrithor are they not allowed to change that17:41
amrithlike, can an operator change that?17:41
denis_makogonyes, we're allowing to change it17:42
denis_makogoni think we should drop that ability to change it, because we're already have configuration groups, thanks to cp16net17:42
amrithwell, in some manner, a user has the ability to change it17:43
denis_makogonamrith, user has an ability to substitute whole config17:43
denis_makogonand of course he could change the datadir, and data will go other place17:43
*** shivamshukla has joined #openstack-trove17:44
*** amcrn has joined #openstack-trove17:44
amrithone second17:45
amrithwhat do we do about shutdown, let me look at your template17:45
denis_makogonall supported databases allows to minimize the downtime by setting the read-only option17:47
amrithok17:47
amrithand how would you do that in mysql?17:47
amrithor cassandra17:48
amrithor whatever datastores you will implement in v1 of this process17:48
denis_makogonflush tables to FS, set read-only, perform snapshoting, take of the read-only17:48
*** demorris has joined #openstack-trove17:48
amrithyes, I got that17:48
amrithhow do you force a mysql database to go readonly17:48
denis_makogonsql query17:49
amrithin some instances that can take a long time17:49
amrithit could take forever if you aren't lucky17:49
amrithon the irc on monday I posted some links to people who explain the complexities of snapshot backup for mysql17:49
denis_makogoni guess it's the problem of the database itself17:49
amrithi see17:50
denis_makogoninnobackupex and mysql dump does almost the same17:50
denis_makogonexcept block storage snapshotin17:50
amrithso, mysqldump will do the database readonly ONLY if you specify --single-transaction17:51
denis_makogonof course17:51
amriththat's kind of the whole point17:51
amrithmarking a table read only is different from marking a whole database readonly17:51
denis_makogonamcrn, trove allows to pass additional parameters to the main cmd that delivers a backup17:51
denis_makogonamcrn, we're not backuping only one table17:52
amcrndenis_makogon: for the love of pete, please type a 3rd character before auto-completing17:52
denis_makogonamcrn, sorry, =)))17:52
*** michael-yu has quit IRC17:52
SnowDustPeter ;)17:52
*** thedodd has quit IRC17:53
*** michael-yu has joined #openstack-trove17:53
denis_makogonamrith, we're cannot relay at database at all17:54
*** _shalkh has joined #openstack-trove17:54
*** amrith is now known as notamrcn17:54
notamrcnso17:55
notamrcnsince we're not backing up only one table17:55
notamrcnand you want to lock a whole database17:55
notamrcnI'm concerned that the things you have to do are very different, depending on the kind(s) of storage engines in use17:55
notamrcnwhile it is mysql (or percona server, or mariadb or whatever)17:56
notamrcnflush tables with read lock has very different semantics depending on whether there's innodb under the covers or myisam17:56
notamrcni'm trying to understand whether this approach of snapshot replication with this 3 step process is sufficiently flexible for all datastores17:57
denis_makogonnotamrcn, in this case, we would really need to shutdown the instance17:57
notamrcnso, if you recall, my first question on monday was whether this snapshot replication would require a shutdown/reboot17:58
denis_makogonnotamrcn, but it seems, affects only sql databases17:58
notamrcnso, in your implementing this bp, I would like to be reasonably sure that the implementation is one that is later extensible to other data stores17:58
notamrcnI can think of multiple ways to structure this code17:58
notamrcnand some would be amenable to extension to other datastores and others would be a beast17:59
notamrcnwhich was my (c) question in email17:59
notamrcnanyway meetign is supposed to start in 1min17:59
SlickNikHello folks. Time for the meeting in #openstack-meeting-alt.17:59
*** notamrcn is now known as amrith17:59
amrith\o/18:00
amrithdenis_makogon, we have to continue at some point18:00
denis_makogonamrith, we're do that after meeting18:00
*** eguz has joined #openstack-trove18:00
*** sbfox has quit IRC18:01
*** sbfox has joined #openstack-trove18:03
*** amytron has joined #openstack-trove18:03
*** eghobo has quit IRC18:04
*** shivamshukla has quit IRC18:04
*** khyati has joined #openstack-trove18:05
*** shivamshukla has joined #openstack-trove18:05
amrithdenis_makogon, unfortunately I have a meeting in 52min. by the time that is over it may be too late for you.18:08
denis_makogonyeah, amrith we could continue tomorrow, i guess18:09
*** ramashri has joined #openstack-trove18:12
*** todd_dsm has joined #openstack-trove18:14
*** thedodd has joined #openstack-trove18:15
*** _shalkh has quit IRC18:24
*** _shalini_kh has joined #openstack-trove18:24
*** coolsvap is now known as coolsvap|afk18:26
*** todd_dsm has quit IRC18:33
*** SnowDust has left #openstack-trove18:39
openstackgerritAnna Shen proposed a change to openstack/trove-integration: Add neutron switch for ini tests  https://review.openstack.org/8785618:40
*** michael-yu has quit IRC18:40
*** michael-yu has joined #openstack-trove18:40
*** SnowDust has joined #openstack-trove18:40
SlickNikannashen: around? Your topic item is being discussed in #openstack-meeting-alt18:45
*** SnowDust has quit IRC18:50
*** russellb has quit IRC18:53
*** _shalini_kh has quit IRC18:54
*** russellb has joined #openstack-trove18:55
*** sriram_tesora has joined #openstack-trove18:57
*** sriram_ has joined #openstack-trove19:00
*** demorris has quit IRC19:03
*** sriram_tesora has quit IRC19:04
*** demorris has joined #openstack-trove19:11
denis_makogonannashen, ping19:14
denis_makogonannashen, hope you're there, i guess you're now the owner of the networking in Trove, i would like you to take this review as the base for your future code, it'll save your time, https://review.openstack.org/#/c/86031/19:15
denis_makogonSlickNik, ping19:19
annashendenis: pong19:19
denis_makogonSlickNik, could you please suggest the way to perform integration testing for the resources that not being tracked by trove https://review.openstack.org/#/c/45075/ ?19:20
annashendenis, thanks for your patient,19:20
denis_makogonannashen, thanks to you too19:20
SlickNikdenis_makogon: Add new integration tests to the suite for Floating IPs?19:21
denis_makogonannashen, those patch basically refactors code by making it generic and dependent to driver19:21
SlickNikdenis_makogon: Flavors are not being tracked by trove (in the db, if that's what you mean), yet we have integration tests for them.19:22
annashenrather than wasting this patch, do you mind of rebasing it off current master head and i will submit my patch on that19:22
amrithdenis_makogon, my other meeting is over. we can chat now if you'd like19:22
denis_makogonannashen, i cannot do that, because my BP marked as obsolete, it's your task now, feel free to take my patch and submit another that absorbs mine19:23
denis_makogonamrith, yes we can19:23
annashendenis, thanks!19:23
denis_makogonannashen, you're welcome19:24
annasheni will do that19:24
denis_makogonamrith, we stopped at the question how does each database will act before snapshoting the volume19:25
amrithyes, we were approximately there19:25
amrithmy overarching concern is this19:25
amrithyour bp postulates that there shall be 3 steps19:25
amrithset <something> readonly19:25
amrithsnapshot volume19:25
amrithresume19:25
amrithI would like to come up with a set of steps that would (maybe more than 3) work for all datastores19:26
denis_makogonagreed, it should be changed19:26
denis_makogonwhat if it'll be like:19:26
amrithand something that would work for the same data stores if something changes moving forward19:26
denis_makogon1. prepare database (specific to each datastore)19:26
amrithand this impacts the things like assumptions and limitations19:26
denis_makogon2. snapshot19:26
denis_makogon3. resume19:26
amrithactually, not that19:27
amrithsorry, strike that19:27
amrithyes, something like that19:27
amrithhere's what I had in mind19:27
denis_makogonamrith, current backup base class allows to run _pre_backup() and _post_backup() methods19:27
amrith1. ask datastore the list of volumes, locations, etc., that must be snapshotted in one unified set19:27
amrith2. verify that these can be done19:28
amrith3. instruct database to go to readonly mode (with a specified timeout)19:28
amrith4. initiate snapshot19:28
amrith5. inform database that it can resume writing19:28
*** shivamshukla has quit IRC19:28
denis_makogoni see it another way19:28
amrithI think these five would be a set of steps that you can use for all datastores that I can think of right now19:28
denis_makogon1. ask instance for it's volume19:29
amrithand in the future we could extend this as required19:29
*** sbfox has quit IRC19:29
denis_makogonamrith, in this case we would deal with income requirements in the future19:29
*** michael-yu has quit IRC19:30
denis_makogonamrith, at now instance can have _only_ one volume19:30
amrithwell, denis_makogon I would make it "it's volumes"19:30
amrithyes, now it may be only one19:30
amrithbut that's not likely to be the case for a production version of a datastore19:30
denis_makogonamrith, we're talking about "now", future will come when it will come19:30
amrithit is a common gripe with RDS19:30
amrithyes, but software will exist in the future19:31
amriththe objective is to make an extensible api19:31
amrithotherwise it is more work later19:31
denis_makogonamrith, DBInstance model that is responsible for Trove instances, has only one attribute: volume_ID19:32
denis_makogonnothing else19:32
*** michael-yu has joined #openstack-trove19:32
denis_makogonwe cannot predict everything19:32
denis_makogonso, the actual flow will be:19:33
denis_makogon1. ask if instance if it has the volume19:33
denis_makogon2. prepare database for storage snapshot19:34
denis_makogon3. snapshot19:34
denis_makogon4. return database in to the normal state19:34
amrithdenis_makogon, one second <thinking>19:34
amrithok, sounds good19:35
amrithwould your infrastructure provide the ability to take a snapshot of multiple trove instances; ie. a consistent snapshot?19:36
denis_makogonamrith, please explain19:37
amrithand at another level, shouldn't your implementation have an API?19:37
amrithre: first question ...19:37
amrithsuppose I have five trove instances19:37
amrithcan I get a consistent snapshot of all of them in a single API call?19:38
denis_makogonamrith, about API - no, CinderSnapshot is the strategy of the backup process, that has it's own API19:38
amrithit would be to run step 1 and 2 on all instances19:38
amrithand then run 3 on all instances19:38
amrithand then run 4 on all instances19:38
amrithso the API would just be the backup API?19:38
denis_makogonamrith, https://wiki.openstack.org/wiki/Trove/snapshot-design#Backups_Design19:39
amrithbecause it says no change to public api19:39
denis_makogonamrith, of course19:39
denis_makogonamrith, no new API routes would be added19:39
amrithyou would just add a new bkup_type?19:39
denis_makogonamrith, yes19:39
*** mattgriffin is now known as mattgriffin-afk19:40
amrithbut the create backup method has no way to specify backup type19:40
*** sbfox has joined #openstack-trove19:40
denis_makogonamrith, yes, it's config based feature19:40
amrithat least in the bp you pointed me to19:40
*** mattgriffin-afk has quit IRC19:41
amrithoh, so the config would have a setting that says "backup -> xtrabackup" or "backup -> snapshot"19:41
denis_makogoni think we would need the new API that lists the available strategies19:41
denis_makogonamrith, yes19:41
amrithok, maybe you could add that to your bp19:41
denis_makogonamrith, no, it's anothe BP19:41
denis_makogonamrith, totally different scope19:42
amrithI guess I don't understand that19:42
amrithhow does one get a snapshot backup?19:42
amrithat the very least you have a depenency to that "other bp"19:42
openstackgerritDan Nguyen proposed a change to openstack/trove: Added route for Admin API to support guest upgrade  https://review.openstack.org/8141019:42
denis_makogonamrith, now i don't have any dependency at any BPs19:43
amrithwell, maybe you should?19:43
denis_makogonamrith, no, why would i ?19:43
denis_makogonamrith, features are totally independent, why should they be dependent?19:44
amrithso if there's no new API (RequestSnapshotBackup, for example) then how do I get a snapshot backup?19:45
denis_makogonamrith, my BP proposes to add new backup type19:45
denis_makogonamrith, to the end user there's no difference19:45
denis_makogonamrith, user performs the backup19:45
denis_makogonamrith, he doesn't know how its being performed19:46
*** amcrn_ has joined #openstack-trove19:46
amrithdenis_makogon, where does your BP propose new backup type (I'm reading https://wiki.openstack.org/wiki/Trove/volume-data-snapshot-design)19:46
amrithso, if a user performs a backup today, he would get an xtradb backup, yes?19:46
amrithsorry xtrabackup19:47
denis_makogonamrith, justification section19:47
denis_makogonamrith, yes19:47
*** amcrn has quit IRC19:47
amrithso what would be changed to make this snapshot backup available to a user?19:48
*** ViswaV_ has quit IRC19:48
*** amcrn_ is now known as amcrn19:48
amrithsomething has to change, otherwise we'd get an xtrabackup, right?19:48
*** ViswaV has joined #openstack-trove19:48
amrithand I have no idea what happens for a backup of mongodb or cassandra or some other datastore19:48
denis_makogonamrith, nothing, user can't see the difference between backup(xtrabackup) and another made by cinder19:49
amrithwell, not to the user19:49
amrithwhat causes the code to execute snapshot backup and not xtrabackup?19:49
denis_makogonamrith, only guest config rules19:49
amrithso the config would have a setting that says "backup -> xtrabackup" or "backup -> snapshot"19:50
denis_makogonamrith, https://github.com/openstack/trove/blob/master/trove/common/cfg.py#L27219:50
denis_makogonamrith, yes19:50
denis_makogonamrith, strategies are being switched through guest configuration file19:51
amrithok, so what I'm requesting is just that you clarify this in your BP. and that there should be an API that lists the possible strategies.19:51
glucasdemorris, amrith: so currently a guest is configured to enable a single backup strategy.. but in the future we could use e.g. capabilities so that a datastore can support multiple strategies, and user could choose which to run?19:53
denis_makogonamrith, at least now we don't need that type of the API19:53
amriththe latter was your suggestion (some minutes ago), I don't want to take credit for it.19:53
glucaswhoops ^ denis_makogon , sorry demorris19:53
amrithde<TAB>19:53
glucasyeah19:53
denis_makogonglucas, i suppose yes19:54
*** saurabhs has joined #openstack-trove19:54
denis_makogonglucas, at least we could implement the API that asks Trove which strategies available for {datastore}19:54
denis_makogonamrith, are we ok with BP now ?19:55
amrithwell, I guess those were the questions I sent you in email. I don't know that I'm happy with the answers (personally, I'd implement a more flexible system but I'm not the one implementing it). And so it is up to core whether they like this BP or not. I'm not happy with it. But, I'm also not happy with the fact that I'm overweight.19:56
amrithAnd 'core' won't help me with that either ;)19:56
amrithdenis_makogon, I have to run now (as in go somewhere, not run. running is IMHO bad). g'night19:58
denis_makogonamrith, feel free to submit the BP and spec to any feature you want to fix or implement19:58
*** thedodd has quit IRC19:59
*** NehaV1 has joined #openstack-trove19:59
*** NehaV has quit IRC20:00
*** demorris has quit IRC20:02
*** Barker has quit IRC20:02
*** khyati_ has joined #openstack-trove20:03
*** khyati has quit IRC20:04
*** thedodd has joined #openstack-trove20:05
*** Barker has joined #openstack-trove20:07
*** ViswaV has quit IRC20:11
*** Barker has quit IRC20:12
*** Barker has joined #openstack-trove20:14
*** ramashri has quit IRC20:14
mat-loweryhttps://wiki.openstack.org/wiki/Meetings/TroveMeeting doesn't state a time and place for the blueprint meetings. Can someone edit that or let me know and I'll edit it?20:16
espmat-lowery: I think the bp meetings are mondays in the #openstack-trove channel in the morning 10-11ish.  SlickNik or amcrn could confirm I think20:18
*** NehaV1 has quit IRC20:19
*** NehaV has joined #openstack-trove20:19
SlickNikmat-lowery: 11-12 Mondays in #openstack-trove20:20
mat-lowerythanks esp and SlickNik: so same time as weekly meetings ok20:22
mat-loweryI'll edit if that is ok20:22
espthx mat-lowery, that’s a good idea20:23
SlickNikmat-lowery: Awesome. Thanks!20:24
*** mattgriffin has joined #openstack-trove20:24
*** radez_g0n3 has quit IRC20:26
*** radez_g0n3 has joined #openstack-trove20:26
mat-loweryesp, SlickNik: done. thank you!20:27
*** mattgriffin has quit IRC20:29
*** sbfox has quit IRC20:32
*** sbfox has joined #openstack-trove20:38
*** michael-yu has quit IRC20:39
*** sbfox has quit IRC20:45
*** michael-yu has joined #openstack-trove20:47
*** sbfox has joined #openstack-trove20:47
*** mattgriffin has joined #openstack-trove20:48
*** eguz has quit IRC20:49
*** eghobo has joined #openstack-trove20:50
*** ramashri has joined #openstack-trove20:58
*** jmontemayor has quit IRC21:07
*** casanch1_ has joined #openstack-trove21:14
*** amytron_ has joined #openstack-trove21:14
*** amytron has quit IRC21:14
*** amytron_ is now known as amytron21:14
*** casanch1 has quit IRC21:17
*** casanch1_ has quit IRC21:18
openstackgerritDan Nguyen proposed a change to openstack/trove: Added separate rate limit setting for mgmt POST  https://review.openstack.org/8155721:20
*** kevinconway has quit IRC21:23
*** denis_makogon has quit IRC21:24
*** grapex_ has joined #openstack-trove21:25
*** grapex has quit IRC21:28
*** pdmars has quit IRC21:28
*** eguz has joined #openstack-trove21:29
*** robertmyers has quit IRC21:32
*** eghobo has quit IRC21:34
*** achampion has quit IRC21:34
*** Barker has quit IRC21:38
*** ViswaV has joined #openstack-trove21:39
*** NehaV has quit IRC21:39
*** ViswaV_ has joined #openstack-trove21:40
*** ViswaV has quit IRC21:43
esmuteamcrn, SlickNik: I was thinking about the cross-region backup. There is really no use of specifying the availability_zone. As long as the region is given, the backup object can be accessed to.21:52
esmuteAvailability zone is more for swift object placement, which trove doesnt really care about21:52
esmutehttps://wiki.openstack.org/wiki/Cross-region-backup-availability21:52
*** jcru has quit IRC21:52
*** sriram_ has quit IRC21:53
esmuteim thinking of removing the availability_zone from the api ^21:53
esmutewhat do you guys think?21:53
*** demorris has joined #openstack-trove21:56
*** demorris has quit IRC22:02
*** amytron has quit IRC22:06
*** michael-yu has quit IRC22:13
espSlickNik: ping22:14
openstackgerritDan Nguyen proposed a change to openstack/trove: Added separate rate limit setting for mgmt POST  https://review.openstack.org/8155722:15
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168222:15
SlickNikesp: 'sup?22:15
*** NehaV has joined #openstack-trove22:15
espSlickNik: was wondering if you knew of this error in the reddwarf gate https://rdjenkins.dyndns.org/job/Trove-Gate/3269/console22:15
espI just tried rebasing to see if that would do the trick..22:16
SlickNikesp: yes rebasing should fix it.22:17
espk, thx!22:17
SlickNikIt's a side effect of some new checks that went into the requirements package upstream. We now fail if you're trying to use a requirement that's not part of the global requirements.22:18
SlickNikRebasing should get your requirements in line.22:18
SlickNikNo problem.22:18
espsounds good22:23
*** NehaV has quit IRC22:31
*** grapex_ has quit IRC22:36
*** grapex has joined #openstack-trove22:36
SlickNikesmute: Just saw your comment about the AZ. I think that's a fair point. I'm good with that (i.e. not specifying AZ as part of the request)22:39
*** yogesh has quit IRC22:40
*** mattgriffin has quit IRC22:41
*** thedodd has quit IRC22:41
amrithesp, for my edification, are you going to remove az from the api or make it not required [optional, assming it is now required]?22:43
espamrith: hello, can you remind me which bp that please?22:43
espamrith: I think you might be thinking esmute :)22:44
amrithesp, I was going to say something clever to SlickNik about tab completion. turns out I did it ;)22:44
amrithyes, esmute22:44
amrithes<TAB>, for my edification, are you going to remove az from the api or make it not required [optional, assming it is now required]?22:44
*** sbfox has quit IRC22:45
amrithesp, I'm otherwise known as notamcrn22:45
esmuteamrith: edification? that is a big word :)22:45
amrith10 points in scrabble22:45
esmuteyes. i was suggesting to remove az from the api completely22:45
amrithesmute, thanks.22:46
esmuteim about to update the wiki... that will make it cleary22:46
esphaha22:46
amcrn+1 to removing az from the api completely22:46
espesmute: so your cross region support for backups is more about the ability to put the backup in east or west?22:47
amrithesmute, reason I ask is that if there was a parameter and you now remove it, it could break an application (not like someone is using it yet, maybe). I was wondering whether the convention in openstack was to make it deprecated first (for a release) and then remove it or just remove it. Thx!22:47
esmuteesp: Yes... more like it allows to copy backups from west to east and viceversa...22:47
espesmute: meaning you don’t necessarily care which AZ in falls under22:47
amrithamcrn, this won't be a compat issue for all-o-y'all?22:48
esmuteesp: yes :)22:48
espesmute: k, does this make it difficult to retrieve it?22:48
amcrnamrith: it might be for some, but not for us22:48
espesmute: or is it recorded somewhere like the DB or name of the backup?22:48
amrithok, mostly educational question on my part. I've worked at places where it is three releases before you can change an API in an incompatible way and releases were annual ;)22:48
amrithsorry, not places. one place22:49
espamrith: me too22:49
esmuteamrith: yes you are correct.. im able to mess around the api because no one is using it... but for openstack, usually changes api are marked deprecated but are still backward compatible between minor releases..22:49
esmutebetween major releases, it is a different thing22:49
amrithwould this mean that we would rev our API for this kind of change?22:50
amrithi.e bump the api revision?22:50
esmuteamrith: once we have versionining in our API, yes22:50
SlickNikOkay, I need a clarification here. esmute: isn't this an addition to the existing API that we're proposing?22:51
amcrnesp: i'm pretty sure az is a just a pass-thru to nova if memory serves me correctly22:51
*** lnxnut_ has joined #openstack-trove22:51
*** lnxnut has quit IRC22:51
*** lnxnut_ has quit IRC22:51
espamcrn: cool.  I thought that if you don’t specify it just chooses for you.22:52
*** lnxnut has joined #openstack-trove22:52
espamcrn: but maybe that’s a configurable thing in nova22:52
esmuteesp: the backups are no recorded in the DB in the new region. The DB record is created and populated with the information from the swift metadata... the metadata holds some informatino about the backup22:52
espesmute: gotcha22:53
esmuteSlickNik: Yes. it is..22:53
amrithesmute, touche ;)22:53
esmuteSlickNik: I am overloading the Backup create and have it receive a backup id and region22:54
espesmute: so makes no difference then, meaning amcrn is correct when he says pass-thru22:54
esmuteSlickNik: let me know if i answer your question22:54
espthx amcrn show me up again…22:54
* amcrn moonwalks22:54
esmutelol amcrn22:55
amcrn;)22:55
esmuteesp: I think swift may have concept of zones...where you can choose where the objects go... but im not too sure22:55
SlickNikesmute: Yes.22:56
espesmute: yeah but if all you need to do is ask swift for an object from a container and it knows what to do then I think you got it under control22:56
espgood work esmute :)22:56
*** todd_dsm has joined #openstack-trove22:57
espdamn 4:00p already...22:57
esmuteesp: Thanks .. we'll see how it turns out22:57
amrithwell, it was 4pm here a long time ago22:57
amrithjust saying, it's almost 722:57
espamrith: haha, true22:57
amrithwe start at 5pm here22:57
amrithnow looking to see where the next pub is22:57
amrithenjoy folks!22:57
esmutechao amrith22:58
esppeace amrith :)22:58
amrithesmute, esp have fun (and in an hour, have a beer)22:58
amrithSlickNik, you around still?22:58
espthx amrith, yeah I need a drink22:58
SlickNikSo just to recap so we're on the same page. esmute feel free to correct any of this:22:59
SlickNik- We're proposing an addition to the backup API22:59
SlickNik- The modification (removal of AZ) is a modification to the proposed API22:59
SlickNik- It's not a modification to the backup API as it exists today22:59
SlickNik- Hence it doesn't affect backwards compat or the previous backup API22:59
SlickNikamrith: Yup, I'm around22:59
esmuteSlickNik: Correcto...23:00
esmuteit is a modification of a new proposed API....23:00
esmutewhich havent been used yet23:00
esmuteSlickNik: actually i lied23:07
esmutethe trove client does have a change in the cli23:07
esmutecurrently in the cli, we use 'trove backup-create <name> <instance>' to create a backup23:08
esmute<instance> has to be made optional now23:08
esmuteso it would change to 'trove backup-create <name> --instance <instance>'23:09
*** todd_dsm has quit IRC23:09
*** todd_dsm has joined #openstack-trove23:10
esmuteis there a way to make the arg param optional....without making it a kward23:11
esmute*kwarg23:11
SlickNiknot that I'm aware of.23:11
*** michael-yu has joined #openstack-trove23:13
esmuteok.. let me see if i can find a way23:14
SlickNikYeah, let's think through this a bit more. I understand that the API contract (i.e. the URI and payload body) will stay the same. But I'm not too excited about the troveclient command line syntax changing.23:17
esmuteyeah. i am with you23:18
esmutebut currently, an instance_id will have to be specified.23:18
esmutewe can overload the 2nd arg to get an ID... whther it is an isntance id or backup id23:19
esmutebut that could be confusing.23:19
SlickNikMaybe we add a different command to the client that maps to the same route with the new payload?23:20
SlickNikJust a thought23:20
SlickNiktrove backup-create-from-copy or something?23:20
esmutebecause we have to provide an ID.. whether it is an instance id or a backup id23:20
esmuteSlickNik: That could also work23:21
SlickNikThen we could leave the current command the way it is.23:21
esmuteactually.. what i proposed doesnt seem too bad..23:21
esmutethe api stays the same, but the doc will change23:22
esmuteinstead of saying "instance id" it will say "source id"23:22
SlickNikThat's not a bad option either. The help string will need to change.23:22
SlickNikYup.23:22
*** ramashri has quit IRC23:23
esmutethen it is up to trove how to diferentiate which ID it is...23:23
amrithSlickNik, (again for edification) are you not happy with the command line syntax changing (period) or that the change would be incompatible?23:24
esmuteactually.. that is too confusing and more work.. i think your suggestion is better23:24
*** flaper87 is now known as flaper87|afk23:25
esmutei am leaning on create a new cli API23:25
SlickNikamrith: I don't think the change would be incompatible. (i.e. all previous trove backup API calls would remain exactly the same and do the same thing).23:25
amrithi see, in other words the second argument (which is now an instance_id) would in future be an id (either instance or backup) and it's up to the backend implementation to figure out which23:26
amrithand since it is an id, it damn well be unique ;)23:26
amrithis that right?23:26
SlickNikesmute: was trying to overload the current backup-create command in the trove client to cater to the new scenario he's adding, and that would change the client syntax. And I wouldn't like to do that.23:27
SlickNikamrith: Actually I don't think the backend should decide that. That seems like API creep.23:27
amrithI guess that's what I'm not following23:28
amriththe api has an argument that could be overloaded?23:28
amrithbut the CLI would have two options, backup_id and instance_id and stuff the value of one or the other into that argument?23:29
SlickNikamrith: no. The API does something different based on the payload.23:29
amrithSlickNik, esmute ... sorry if I'm slowing your conversation down ...23:29
amrithok, I guess I was calling that the implementation of the API23:30
*** grapex has quit IRC23:31
*** ranjitha has joined #openstack-trove23:33
SlickNikWhat I initially suggested, was to add a new command to the cli for this new scenario. The fact that it's using the same route internally with a new payload would just be an internal implementation detail.23:34
esmuteSlickNik: +1. I dont like this APi creep either.. i think your suggestion (creating a new command CLI) is better23:35
*** ViswaV_ has quit IRC23:35
amrithesmute, and the new CLI would accept the new kind of ID?23:35
esmuteamrith: yes.. backup id to be precise....23:36
esmutethe other api (the current one) aaccepts instance id.23:36
*** achampion has joined #openstack-trove23:36
amrithesumte, but it would still make the same backend call, putting the backup_id in the place where the other CLI API would put the instance_id?23:36
esmutethey share the same API route, but internally, they are being handled differently23:36
amrithOK, I will try and understand that some more; what you mean by API route. Thanks guys for humoring me, I'm hoping to learn more of this stuff by listening to y'all chat.23:37
SlickNikamrith: They call them out explicitly as being two different types of ID in the payload.23:37
*** mattgriffin has joined #openstack-trove23:37
SlickNikLet me see if I can get a quick example23:37
SlickNikone sec.23:37
amrithSlickNik, ok, that would be two API's and thanks for offering an example23:37
esmuteamrith: when i said 'route', i meant the REST API... that will stay unchanged..23:38
*** todd_dsm has quit IRC23:38
amrithesmute, same route (same REST API), but you could either provide backup_id=...... or isntance_id=...... and the backend did different things base don that?23:39
amriths/isntan/instan/23:39
esmuteamrith: yes23:39
amrithesmute, thanks. I understand. thx much23:40
*** ranjitha has quit IRC23:40
amrithand sorry for derailing ur converstaion23:40
amrithconversation23:40
esmuteno.. this is good... i feel like amcrn... moonwalking..23:40
amrithamcrn is on the moon now?23:41
amrithdidn't know they had irc there23:41
amrith;)23:41
esmutehe was... but i think he's come back down now23:41
amrithoh, he bought the economy round trip ticket23:41
amrithgood move23:41
amrithI hear the food on the moon isn't that good23:42
amrithsome friends went there23:42
amriththey came back too23:42
esmuteamrith: They only have cheese there.23:42
amrithwell, they were vegan which would explain the issue23:42
amrithissue, problem, same thing23:42
esmutelol23:43
SlickNikquick gist: https://gist.github.com/anonymous/2d5d70e39c5aa60baec923:46
amrithlooking23:47
SlickNikesmute, feel free to correct if I'm off with the proposed piece, just cobbled that together since it doesn't exist.23:47
amrithSlickNik, thanks for the example23:49
amrithi learnt something noo ...23:49
esmuteSlickNik: This is correct23:50
esmuteto add to this, there will be two CLI commands, one that populates the first rest request (currently) and another one that will create the second requests (minus the availability_zone)23:51
SlickNiknp, glad to be of help.23:53
SlickNikbrb23:53
esmutein the server side, trove will parse the payload, if it finds backup["instance"] in the message, then it knows the user wants to create a new instance backup... if it finds backup['backup'] then the user wants a backup from a backup, which is the new feature im implementing23:53
esmutethis is confusing now.. but i am hoping it becomes more clear when you see the code23:54
amrithok esmute, since SlickNick is not here (and I tend to wear out my welcome), I have a question for you. why a new CLI command23:54
amrithso here's what I'm thinking23:54
amrith<command> <instance_id> .... works like now23:54
amrithcommand --instance_id <instance_id> .... new implementation, same as old one23:54
amrith<command> --backup_id <backup_id> ... new implementation23:55
amrithand they'd use the new API or the old one23:55
amrithno new command23:55
amrithjust changed CLI23:55
amrithin a compatible way23:55
esmutelet me play it back.. because i tend not to get things quickly23:57
esmute<command> <instance_id> .... works like now23:57
amrithor23:57
esmutecommand --instance_id <instance_id> --backup_id <backup_id>.... new implementation that i proposed, command is the same as old one... but the --instance_id and --backup_id are both optional23:58
SlickNikback23:58
esmutenew_command <backup_id> is what SlickNik proposed23:58
amrithesmute, that was what I was thinking [almost]. either instance_id or backup_id must be provided. instance_id can be be provided either with or without --instance_id23:58
amrithah, so slicknick proposed23:59
amrith<oldcommand> instance_id23:59
amrith<newcommand> backup_id23:59
amrithI see23:59
amrithok23:59
esmuteamrith: if we go to the command i proposed, the instance_id cannot be passed without the --instance_id23:59
SlickNikamrith: I think the cli has a limitation where if you have a positional arg (i.e. not a —kwarg) it's also a required arg for the command.23:59

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