Wednesday, 2014-06-04

*** radez` is now known as radez_g0n300:21
*** matsuhashi has joined #openstack-trove00:23
*** shakayumi has joined #openstack-trove00:31
*** shakayumi has quit IRC00:31
*** ramashri has quit IRC00:40
*** demorris has joined #openstack-trove00:41
*** annashe__ has joined #openstack-trove00:51
*** Barker has joined #openstack-trove00:53
*** sbfox has joined #openstack-trove01:01
*** ViswaV has quit IRC01:10
*** ViswaV has joined #openstack-trove01:28
*** nosnos has joined #openstack-trove01:38
*** yidclare has quit IRC01:39
*** amcrn has quit IRC01:48
*** sbfox has quit IRC01:53
*** ViswaV_ has joined #openstack-trove02:02
*** ViswaV has quit IRC02:05
*** sbfox has joined #openstack-trove02:09
*** ViswaV_ has quit IRC02:15
*** demorris has quit IRC02:15
*** ramishra has joined #openstack-trove02:21
*** ramishra has quit IRC02:48
*** ramishra has joined #openstack-trove02:58
NavsterGwhat is the best repository for installing trove on centos03:04
NavsterG??03:04
*** rwsu has quit IRC03:10
*** Barker has quit IRC03:15
*** nosnos has quit IRC03:29
*** achampion has joined #openstack-trove03:29
*** matsuhashi has quit IRC03:31
*** Longgeek has joined #openstack-trove03:33
*** robertmyers has quit IRC03:35
*** haomaiwang has joined #openstack-trove03:40
*** haomaiwang has quit IRC03:48
*** haomaiwang has joined #openstack-trove03:48
*** achampion has quit IRC03:56
*** haomai___ has joined #openstack-trove04:05
*** haomaiwang has quit IRC04:05
*** ramishra has quit IRC04:19
*** haomaiwang has joined #openstack-trove04:21
*** haomai___ has quit IRC04:23
*** matsuhashi has joined #openstack-trove04:25
*** haomaiwa_ has joined #openstack-trove04:25
*** haomaiwang has quit IRC04:25
*** nosnos has joined #openstack-trove04:26
*** ramishra has joined #openstack-trove04:33
*** haomai___ has joined #openstack-trove04:34
*** haomaiwa_ has quit IRC04:36
*** achampion has joined #openstack-trove04:53
*** Longgeek has quit IRC04:56
*** Longgeek has joined #openstack-trove05:01
NavsterGquestion for all.. I used http://docs.openstack.org/icehouse/install-guide/install/yum/content/trove-install.html to install trove on my centos 6.5 and nothing is working.05:02
NavsterG is there better install instructions out there somewhere05:03
*** shakamunyi has joined #openstack-trove05:04
*** yogeshmehra has joined #openstack-trove05:17
*** coolsvap|afk is now known as coolsvap05:30
*** sgotliv has joined #openstack-trove05:30
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168205:36
*** NavsterG has quit IRC05:38
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522505:41
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522505:42
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168205:42
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168205:45
*** haomai___ has quit IRC05:49
*** haomaiwa_ has joined #openstack-trove05:49
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522505:52
openstackgerritDan Nguyen proposed a change to openstack/trove: Add a new column and indexes to agent_heartbeats  https://review.openstack.org/8168205:52
*** coolsvap is now known as coolsvap|afk05:52
*** coolsvap|afk is now known as coolsvap05:58
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522506:03
esp^ testing gerrit :)06:03
*** esp has left #openstack-trove06:04
*** sgotliv has quit IRC06:05
openstackgerritOpenStack Proposal Bot proposed a change to openstack/trove: Imported Translations from Transifex  https://review.openstack.org/9700806:06
*** yogeshmehra has quit IRC06:24
*** yogeshmehra has joined #openstack-trove06:25
*** yogeshme_ has joined #openstack-trove06:26
*** amytron has quit IRC06:29
*** yogeshmehra has quit IRC06:30
*** coolsvap is now known as coolsvap|afk06:31
*** sbfox has quit IRC06:40
*** coolsvap|afk is now known as coolsvap06:47
*** yogeshme_ has quit IRC06:52
*** yogeshmehra has joined #openstack-trove06:53
*** yogeshmehra has quit IRC06:57
*** yogeshmehra has joined #openstack-trove06:59
*** freyes has joined #openstack-trove07:04
*** eghobo has joined #openstack-trove07:08
*** denis_makogon has joined #openstack-trove07:09
openstackgerritYongli He proposed a change to openstack/trove: Apply six for metaclass  https://review.openstack.org/7313607:09
*** matsuhashi has quit IRC07:17
*** matsuhashi has joined #openstack-trove07:18
*** coolsvap is now known as coolsvap|afk07:21
*** eghobo has quit IRC07:24
*** coolsvap|afk is now known as coolsvap07:29
*** mattgriffin has quit IRC07:36
*** boden has joined #openstack-trove07:59
*** shakamunyi has quit IRC08:10
*** SushillKM has joined #openstack-trove08:14
*** annashe__ has quit IRC08:20
*** ramishra has quit IRC08:26
*** Longgeek has quit IRC08:27
*** Longgeek has joined #openstack-trove08:28
*** Longgeek has quit IRC08:29
*** Longgeek has joined #openstack-trove08:30
*** flaper87|afk is now known as flaper8708:35
*** matsuhashi has quit IRC08:42
*** openstackgerrit has quit IRC08:48
*** global__ has quit IRC08:48
*** number80 has quit IRC08:48
*** global__ has joined #openstack-trove08:48
*** openstackgerrit has joined #openstack-trove08:49
*** number80 has joined #openstack-trove08:50
*** matsuhashi has joined #openstack-trove08:50
*** freyes has quit IRC09:02
*** freyes has joined #openstack-trove09:05
*** shakamunyi has joined #openstack-trove09:06
*** shakamunyi has quit IRC09:10
*** ramishra has joined #openstack-trove09:23
*** ramishra has quit IRC09:33
*** shakamunyi has joined #openstack-trove09:36
*** ramishra has joined #openstack-trove09:40
*** shakamunyi has quit IRC09:41
*** freyes has quit IRC09:44
*** yogeshmehra has quit IRC09:48
*** yogeshmehra has joined #openstack-trove09:48
*** yogeshmehra has quit IRC09:53
*** SushillKM has quit IRC10:03
*** haomaiwa_ has quit IRC10:05
*** haomaiwang has joined #openstack-trove10:06
*** denis_makogon has quit IRC10:06
*** nosnos has quit IRC10:08
*** haomai___ has joined #openstack-trove10:09
*** haomaiwang has quit IRC10:12
*** ramishra has quit IRC10:17
*** sgotliv has joined #openstack-trove10:24
*** matsuhashi has quit IRC10:24
*** haomai___ has quit IRC10:24
*** haomaiwang has joined #openstack-trove10:25
*** Longgeek has quit IRC10:34
*** Longgeek has joined #openstack-trove10:35
*** shakamunyi has joined #openstack-trove10:37
*** shakamunyi has quit IRC10:41
*** matsuhashi has joined #openstack-trove10:47
*** freyes has joined #openstack-trove10:53
*** demorris has joined #openstack-trove10:56
*** ramishra has joined #openstack-trove11:05
*** ramishra has quit IRC11:21
*** ramishra has joined #openstack-trove11:21
*** coolsvap is now known as coolsvap|afk11:23
*** matsuhashi has quit IRC11:25
*** flaper87 is now known as flaper87|afk11:25
*** matsuhashi has joined #openstack-trove11:26
*** ramishra has quit IRC11:26
*** demorris has quit IRC11:27
*** r0j4z0 has joined #openstack-trove11:29
*** matsuhashi has quit IRC11:29
*** matsuhashi has joined #openstack-trove11:29
*** shakamunyi has joined #openstack-trove11:38
*** shakamunyi has quit IRC11:43
*** PeterSchwaller has quit IRC11:46
*** demorris has joined #openstack-trove11:46
openstackgerritDenis M. proposed a change to openstack/trove: Fix updated timestamp for SecurityGroup model  https://review.openstack.org/9751011:50
*** PeterSchwaller has joined #openstack-trove11:51
openstackgerritDenis M. proposed a change to openstack/trove: Fix calls for proboscis methods  https://review.openstack.org/9747811:53
*** PeterSchwaller has quit IRC11:56
openstackgerritDenis M. proposed a change to openstack/python-troveclient: Fix shell view for secgroup-* commands  https://review.openstack.org/8531411:57
*** coolsvap|afk is now known as coolsvap11:58
*** PeterSchwaller has joined #openstack-trove12:03
*** coolsvap is now known as coolsvap|afk12:04
openstackgerritDenis M. proposed a change to openstack/trove: Fix poll_until retriever when heat provisioning is enabled  https://review.openstack.org/9719412:19
*** ramishra has joined #openstack-trove12:21
*** radez_g0n3 is now known as radez12:23
openstackgerritDenis M. proposed a change to openstack/trove: Fix tracking of SG's provisioned by Heat  https://review.openstack.org/9679512:23
openstackgerritDenis M. proposed a change to openstack/trove: Use tcp/udp ports from config for heat templates  https://review.openstack.org/9678012:23
*** achampion has quit IRC12:24
*** demorris has quit IRC12:25
*** kevinconway has joined #openstack-trove12:31
*** shakamunyi has joined #openstack-trove12:39
*** haomaiwang has quit IRC12:40
*** haomaiwang has joined #openstack-trove12:40
*** shakamunyi has quit IRC12:44
*** haomaiw__ has joined #openstack-trove12:46
*** haomaiwang has quit IRC12:49
*** shakamunyi has joined #openstack-trove13:03
*** tvoran has joined #openstack-trove13:04
*** tvoran has quit IRC13:04
*** tvoran has joined #openstack-trove13:05
openstackgerritDenis M. proposed a change to openstack/trove: Add backup size validation at restoring  https://review.openstack.org/8630013:06
*** ramishra has quit IRC13:07
*** ramishra has joined #openstack-trove13:10
*** pdmars has joined #openstack-trove13:16
*** demorris has joined #openstack-trove13:16
*** Longgeek has quit IRC13:18
*** Longgeek has joined #openstack-trove13:18
*** Longgeek has quit IRC13:19
*** Longgeek has joined #openstack-trove13:19
*** Longgeek has quit IRC13:19
*** Longgeek_ has joined #openstack-trove13:19
*** Longgeek_ has quit IRC13:21
*** Longgeek has joined #openstack-trove13:24
*** achampion has joined #openstack-trove13:25
*** radez is now known as radez_g0n313:26
*** freyes has quit IRC13:36
*** jcru has joined #openstack-trove13:38
*** mattgriffin has joined #openstack-trove13:43
*** ramishra has quit IRC13:47
*** ramishra has joined #openstack-trove13:47
*** ramishra has quit IRC13:52
*** NehaV has joined #openstack-trove13:55
*** robertmyers has joined #openstack-trove13:55
*** NehaV has quit IRC13:55
*** NehaV has joined #openstack-trove13:56
*** NehaV1 has joined #openstack-trove13:57
*** NehaV has quit IRC14:00
*** pdmars has quit IRC14:02
openstackgerritDenis M. proposed a change to openstack/trove: Fix updated timestamp for SecurityGroup model  https://review.openstack.org/9751014:02
*** pdmars has joined #openstack-trove14:02
*** rubick_ has joined #openstack-trove14:05
*** Barker has joined #openstack-trove14:08
*** grapex has joined #openstack-trove14:17
*** esp has joined #openstack-trove14:17
openstackgerritDan Nguyen proposed a change to openstack/trove: Partially implements guest agent upgrade strategy  https://review.openstack.org/8522514:18
*** grapex has quit IRC14:19
*** grapex has joined #openstack-trove14:19
*** amytron has joined #openstack-trove14:20
*** Longgeek has quit IRC14:27
*** coolsvap|afk is now known as coolsvap14:30
*** rwsu has joined #openstack-trove14:40
*** thedodd has joined #openstack-trove14:44
*** matsuhashi has quit IRC14:49
*** tvoran_ has joined #openstack-trove14:49
*** tvoran has quit IRC14:52
openstackgerritDenis M. proposed a change to openstack/trove: Add backup size validation at restoring  https://review.openstack.org/8630014:53
*** haomaiw__ has quit IRC14:58
*** ramishra has joined #openstack-trove14:58
openstackgerritDenis M. proposed a change to openstack/trove: Add logs validation rules for mysql datastore  https://review.openstack.org/9781414:58
*** haomaiwang has joined #openstack-trove14:58
*** ramishra has quit IRC15:03
*** sbfox has joined #openstack-trove15:03
*** annashe__ has joined #openstack-trove15:07
*** radez_g0n3 is now known as radez15:13
*** spiffxp- has quit IRC15:13
*** SlickNik has quit IRC15:14
*** SlickN1k is now known as SlickNik15:14
*** coolsvap is now known as coolsvap|afk15:14
*** aginghipster has quit IRC15:15
*** sbfox has quit IRC15:26
*** coolsvap|afk is now known as coolsvap15:28
*** jmontemayor has joined #openstack-trove15:29
*** yidclare has joined #openstack-trove15:30
*** ViswaV has joined #openstack-trove15:37
*** tvoran has joined #openstack-trove15:38
*** annashe__ has quit IRC15:39
*** tvoran__ has joined #openstack-trove15:41
*** tvoran has quit IRC15:42
*** tvoran_ has quit IRC15:42
openstackgerritDenis M. proposed a change to openstack/trove: Fix updated timestamp for SecurityGroup model  https://review.openstack.org/9751015:49
*** dmakogon_ is now known as denis_makogon15:50
denis_makogonamrith, ping, take a look at https://review.openstack.org/97472 (it's related to your comments on https://review.openstack.org/77551)15:50
*** sbfox has joined #openstack-trove15:52
openstackgerritOpenStack Proposal Bot proposed a change to openstack/trove: Updated from global requirements  https://review.openstack.org/9627515:53
*** ramishra has joined #openstack-trove15:59
openstackgerritGreg Lucas proposed a change to openstack/python-troveclient: Add 'slave_of' option for enabling replication  https://review.openstack.org/9784016:00
*** ramishra has quit IRC16:04
*** tvoran__ has quit IRC16:05
*** tvoran has joined #openstack-trove16:06
*** haomaiwang has quit IRC16:10
*** Gordon has joined #openstack-trove16:11
*** Gordon is now known as Guest1075216:12
*** Guest10752 has quit IRC16:12
*** ramishra has joined #openstack-trove16:12
*** demorris has quit IRC16:13
openstackgerritGreg Lucas proposed a change to openstack/trove: Add slave_of_id to instance model  https://review.openstack.org/9784616:19
*** demorris has joined #openstack-trove16:20
*** ramishra has quit IRC16:23
*** yidclare has quit IRC16:24
*** ramishra has joined #openstack-trove16:24
*** ramishra has quit IRC16:27
*** ramishra has joined #openstack-trove16:27
*** ramishra has quit IRC16:27
*** yidclare has joined #openstack-trove16:28
*** rubick_ has quit IRC16:30
*** ramishra has joined #openstack-trove16:34
anteayahi trove was reddwarf at some point way back when, yes?16:38
anteayathere is a gerrit automated account by name of reddwarf and I was wondering if anyone knew who started or maintains the account16:39
anteaya reddwarf    reddwarf    reddwarf-jenkins@googlegroups.com16:39
*** demorris has quit IRC16:42
*** demorris has joined #openstack-trove16:42
*** annashe__ has joined #openstack-trove16:44
*** jcru has quit IRC16:46
*** amytron has quit IRC16:47
*** jcru has joined #openstack-trove16:47
*** ramishra has quit IRC16:50
*** saurabhs has joined #openstack-trove16:53
*** yogeshmehra has joined #openstack-trove16:57
denis_makogonanteaya, yes, we have reddwarf-ci account16:59
anteayadenis_makogon: great16:59
denis_makogonanteaya, any complains with that ?17:00
anteayawe need to rename it, so the name fits the new standardization of format17:00
anteayadenis_makogon: no complaints17:00
anteayawe just need to select a new name17:00
anteayaso do you want to stay with reddwarf?17:00
*** zuqiang has joined #openstack-trove17:01
anteayaand actually -ci is what we need to add to the name, since according to gerrit that is lacking17:02
anteayadenis_makogon:17:02
*** sgotliv has quit IRC17:02
denis_makogonanteaya, i think you need to talk with SlickNik and vipul, they have direct access to that jenkins17:04
anteayagreat thanks17:04
anteayaSlickNik: let me know when you are available17:04
anteayaor vipul17:04
*** shakamunyi has quit IRC17:13
*** amytron has joined #openstack-trove17:13
SlickNikanteaya: Around now17:17
SlickNikanteaya: We use the reddwarf account for integration tests running on a different jenkins box (using the gerrit trigger plugin)17:19
anteayahey17:19
anteayacool17:19
anteayawe need to standardize names of automated gerrit accounts17:20
anteayadoes the reddwarf account vote?17:20
anteayaor never ever will vote?17:20
SlickNikanteaya: Yes, I'm good with renaming the account if we need to. Perhaps something like trove-ci?17:20
SlickNikYes, the reddwarf account votes.17:20
anteayatrove-ci works for me17:20
anteayado you imagine there ever will be any other accounts testing trove?17:20
anteayaor just trove-ci?17:20
SlickNikWe could possibly have accounts for third-party testing of datastores in the future.17:21
anteayasure17:22
anteayaokay so17:22
anteayatrove-ci may or may not cause some naming issues17:22
anteayaif other folks want to call theirs trove-ci as well17:23
anteayatrove-internal-ci?17:23
anteayaor we could just go with trove-ci and deal with fallout later17:23
anteayaI'm curious17:23
anteayawhy do you have your own internal testing?17:24
SlickNikHow about trove-integration-ci?17:24
anteayawhat does it test?17:24
anteayawe can call it that?17:24
anteayawhat does it test that the gate doesn't?17:24
SlickNikyes, it runs the trove integration tests.17:24
SlickNikI'm working on adding these tests to the gate, so it's temporary.17:24
SlickNikIt's likely not going to be needed after Juno.17:25
anteayakk17:26
SlickNikFYI: https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Trove_Gap_Coverage#Concern_.233:_Deprecating_Reddwarf_CI17:26
*** sbfox has quit IRC17:27
denis_makogonSlickNik, i updated patch, could you please take a look at it?https://review.openstack.org/8531417:27
anteayaSlickNik: awesome that was my next question17:29
SlickNikanteaya: What's the timeline for the renaming? (Asking so I know to be around to update it on the jenkins end :))17:29
anteayaI don't know17:30
anteayait will be announced17:30
anteayawe are still working on coming to agreement on format17:30
*** sbfox has joined #openstack-trove17:30
anteayahttps://etherpad.openstack.org/p/automated-gerrit-account-naming-format17:31
*** rueben has joined #openstack-trove17:31
*** sbfox has quit IRC17:31
SlickNikanteaya: Okay, sounds good. Let's go with trove-integration-ci as the new name.17:32
* anteaya nods17:33
anteayathanks17:33
SlickNikanteaya: Thank You! :)17:33
*** SushillKM has joined #openstack-trove17:35
*** SushilKM has joined #openstack-trove17:37
*** sbfox has joined #openstack-trove17:40
*** yogeshmehra has quit IRC17:40
*** SushillKM has quit IRC17:41
*** yogeshmehra has joined #openstack-trove17:41
*** yogeshme_ has joined #openstack-trove17:43
*** yogeshmehra has quit IRC17:43
cp16netso i guess there isnt much to talk about17:43
*** eghobo has joined #openstack-trove17:44
espyay :)17:46
* esp just kidding...17:46
*** cweid has quit IRC17:50
SlickNikcp16net: Yes, I think it's gonna be a quick meeting.17:50
SlickNikcp16net: A couple of FYIs about the release.17:51
SlickNikcp16net: (Juno-1)17:51
cp16netcool17:51
*** cweid has joined #openstack-trove17:52
cp16neti heard some of the thangs mentioned17:52
*** sbfox has quit IRC17:52
*** esp2 has joined #openstack-trove17:54
*** esp2 has quit IRC17:55
*** demorris has quit IRC17:55
amrithdenis_makogon, yt?17:56
*** robertmyers has quit IRC17:59
SlickNikreminder: Weekly trove meeting in #openstack-meeting-alt17:59
*** atomic77 has joined #openstack-trove18:00
*** amcrn has joined #openstack-trove18:06
*** sbfox has joined #openstack-trove18:07
*** michael-yu has joined #openstack-trove18:08
*** shakayumi has joined #openstack-trove18:08
*** shakayumi has quit IRC18:08
*** shakayumi has joined #openstack-trove18:09
*** shakayumi has quit IRC18:09
*** sgotliv has joined #openstack-trove18:25
*** atomic77 has left #openstack-trove18:28
*** sbfox has quit IRC18:29
iccha1SlickNik: so here are my updates ,  Associate instance flavors with datastores  needs to be bumped to juno 2, https://blueprints.launchpad.net/trove/+spec/list-datastore-type-and-versions needs to be included in juno 1 and and hope to get this done this week https://blueprints.launchpad.net/trove/+spec/update-instance-name18:33
SlickNikiccha1: just updated https://blueprints.launchpad.net/trove/+spec/list-datastore-type-and-versions18:33
iccha1thanks SlickNik !18:34
SlickNikiccha1: and bumped https://blueprints.launchpad.net/trove/+spec/associate-flavors-datastores to Juno-2.18:35
SlickNikThank you!18:35
*** r0j4z0 has quit IRC18:41
*** CAP1089 has joined #openstack-trove18:41
*** CAP1089 is now known as r0j4z018:41
*** denis_makogon_ has joined #openstack-trove18:44
*** denis_makogon has quit IRC18:45
*** denis_makogon_ is now known as denis_makogon18:45
*** dmakogon_ has joined #openstack-trove18:45
denis_makogonvipul, ping18:45
vipuldenis_makogon: what's up18:45
denis_makogonvipul, need to talk to you18:46
denis_makogonvipul, about https://review.openstack.org/9679518:47
vipuluh oh18:47
vipuloh ok18:47
denis_makogonvipul, do you have like 5 mins ?18:47
vipulyep18:47
denis_makogoncool18:47
denis_makogonvipul, i've read your comments18:47
denis_makogonvipul, the only one answer for you that i have - nobody actually running heat-base integration tests18:47
denis_makogonvipul, inside nova/cinder-based int-tests everything is ok18:48
vipuldenis_makogon: Ok, so it seems like we already have a Test that checks that a security group exists after an instance has been created18:49
denis_makogonvipul, yes18:49
vipuland when you turn on Heat, that specific test fails?18:49
denis_makogonvipul, yes18:49
denis_makogonsetUp fails18:49
vipulAlright.. then we're good..18:49
vipulthe tests caught something :)18:49
denis_makogontest caught missing security group for instance18:50
denis_makogonat least in Trove backend18:50
vipulok cool, i'm good with it..18:50
denis_makogonthanks18:50
denis_makogonvipul, last question, i guess18:52
*** yidclare has quit IRC18:52
denis_makogonvipul, could you ask HP guys what is happening with gate?18:52
denis_makogon17:30:39 Connection reset by peer18:52
denis_makogonat least 4 times in a row18:52
denis_makogonfull log https://rdjenkins.dyndns.org/job/Trove-Gate/3947/console18:53
*** zuqiang has quit IRC18:53
vipuldenis_makogon: I'll look into what's going18:54
vipulon18:54
denis_makogonvipul, thanks again18:54
denis_makogongrapex, ping18:57
*** demorris has joined #openstack-trove18:57
vipuldenis_makogon: might have been a one-time issue.. it failed to delete the Devstack VM.. I manually cleaned it up.. you should re-trigger the job18:58
denis_makogonvipul, i already did that18:58
denis_makogonvipul, let me find another log with the same issue18:58
vipuldenis_makogon: ok let me know if it happens again..18:59
denis_makogonvipul, ok18:59
denis_makogonvipul, https://rdjenkins.dyndns.org/job/Trove-Gate/3946/console19:00
denis_makogon15:26:44 URLError: <urlopen error [Errno 104] Connection reset by peer19:01
SlickNikdenis_makogon: That seems like a pypi issue while fetching the package.19:02
denis_makogonSlickNik, i though jenkins pulling packages from OS mirror ?19:03
denis_makogonSlickNik, isn't it ?19:03
*** SushilKM has quit IRC19:04
SlickNikdenis_makogon: rdjenkins is still pulling from pypi;  it doesn't use nodepool and puppet to do the same infra config.19:04
denis_makogonSlickNik, makes sense, thanks19:04
SlickNikOne of the many reasons we're trying to move away from rdjenkins :)19:05
denis_makogonSlickNik, vipul, saw this bug-report, https://bugs.launchpad.net/trove/+bug/1324995, what do you think about it ?19:05
vipuli would personally like to see guest_info go away.. since that relies on file_injection19:08
denis_makogonvipul, me neither19:09
*** kevinconway has quit IRC19:10
denis_makogonvipul, but actually the question is not about in which conf file we have to put packages description19:10
denis_makogonvipul, question is to pass them through config in general19:11
denis_makogoni guess this bug-report is going to be revisited when we would have full heat integration19:11
denis_makogonsince heat can do software deployment through cfn-tools19:11
denis_makogonthen we would be able to put packages directly to heat templates19:12
openstackgerritChristian Berendt proposed a change to openstack/python-troveclient: Overwrite HelpFormatter constructur to extend argument column  https://review.openstack.org/9788619:17
*** sgotliv has quit IRC19:20
*** sgotliv has joined #openstack-trove19:21
SlickNikdenis_makogon: Also, we should get grapex's input when discussing this.19:22
SlickNikHe might have actually run into some issues in production with this, that we might be overlooking.19:22
denis_makogonSlickNik, i pinged him, seems that he's out19:22
*** sbfox has joined #openstack-trove19:22
grapexdenis_makogon SlickNik: I'm back19:23
denis_makogongrapex, cool19:23
grapexsorry... let me catch up- unless you guys want to give me a TL;dr;19:23
denis_makogongrapex, we were talking about your bug-report, seems it's very interesting19:24
grapexOh yeah- to put the package name somewhere the guest could see it on start up?19:24
*** sbfox1 has joined #openstack-trove19:25
denis_makogongrapex, can we actually split prepare call into two ?19:25
grapexI logged this- I would've done it myself but I'm knea-deep in the Rax guest, Sneaky Pete, at the moment, and I want to make sure it works well for Reffy too. But I do think the fundamental problem- that there's this race condition that only doesn't affect us because the prepare call is normally there- should be fixed as its bad design.19:26
*** sbfox has quit IRC19:26
grapexvipul: As for your concern, currently the guest *does* depend on file injection as it needs to know its own ID on start up no matter what.19:27
grapexWhen we move away from file injection I'm sure adding one more property to that file won't add technical debt.19:27
denis_makogongrapex, i can track down that bug, but need your help with that19:27
grapexThe root issue is the guest has to know its ID and other things at start up. Currently that's done with file injection, but we may find other methods in the future. The issue will still remain though.19:28
grapexeven if we change how we solve it19:28
denis_makogongrapex, so, you're telling that guest should deploy packages before RPC service starts ?19:28
grapexdenis_makogon: No19:28
grapexI'm just saying the package is important enough for the guest to know about, so it can query if the datastore has been installed.19:28
grapexand if not behave appropriately19:29
denis_makogongrapex, ok, get that, but is it ok to have two ways to mention packages (from datastore registry and CONFIG) ?19:30
grapextwo ways?19:31
grapexThere wouldn't be two ways19:31
grapexTrove writes the guest config already. So the datastore registry would still be the source of truth.19:32
denis_makogonah19:32
denis_makogonfinally i get that19:32
denis_makogongrapex, last question, how should we deal this guest API ?19:32
SlickNikgrapex: Yeah, we probably should fix that to switch to metadata (instead of file injection) at some point, but I agree that it  probably makes sense for this (package) to be included on the guest from the outset.19:33
SlickNikand by that, I mean the file injection piece19:33
grapexSlickNik: Agreed19:33
grapexdenis_makogon: I don't understand- which part of the guest API?19:33
denis_makogongrapex, prepare call19:33
denis_makogonif we would have packages in config file then we should ignore packages from parameters and use from CONFIG19:34
grapexdenis_makogon: Agreed19:34
denis_makogongrapex, that's what i was asking for =)19:34
denis_makogongrapex, can i take that bug ?19:35
grapexdenis_makogon: Sure.19:35
denis_makogongrapex, thanks19:36
denis_makogongrapex, last thing, could you re-approve https://review.openstack.org/#/c/96780/ it again ?19:36
grapexdenis_makogon: Just to make sure we're on the same page, this bug has a very small objective- add the package name to that config, and check to see if the package is installed on start up- that's all there is. Right?19:37
grapexdenis_makogon: Approved19:37
denis_makogongrapex, yes, put packages(could be more than 1 for datastore version) into CONFIG, check if packages installed on guest start up19:39
grapexCool19:39
grapexdenis_makogon: Awesome! Thanks19:39
denis_makogongrapex, last thing19:39
denis_makogongrapex, "on start up" - when RPC service starts or when prepare comes ?19:39
*** rueben has quit IRC19:40
grapexdenis_makogon: When it starts up19:41
denis_makogongrapex, "it" means guest =)19:41
grapexYes19:41
grapexdenis_makogon: Hold on... digging through reference guest code19:42
*** mattgriffin has quit IRC19:43
denis_makogonthe only thing that is not so clear for me is behavior of the guest when packages are installed or not19:43
*** rueben has joined #openstack-trove19:44
grapexdenis_makogon: Your right. It isn't clear because currently the thing that updates status makes no sense19:45
grapexSo, trove.guestagent.datastore.service BaseDbStatus needs to be updated so its initializer takes an argument "is_installed"19:45
denis_makogonlet me take a look19:46
*** robertmyers has joined #openstack-trove19:46
grapexThere is already a property "is_installed" which is True only if its not certain statuses...19:46
grapexhow is this even working?19:46
grapexSlickNik / vipul: What happens if the guest agent is restarted? Doesn't it return "True" for is_installed?19:47
grapexI mean "False" for is_installed?19:47
denis_makogongrapex, each time RPC service gets restarted, new status object appers19:50
denis_makogonthat's why it's actually never None19:50
grapexYes- that's what makes no sense to me. With the introduction to Conductor, the guest agent can't retrieve its status, so it can't know the prepare call was already received.19:51
denis_makogongrapex, guest doesn't retrieveing its status19:51
grapexdenis_makogon: I know19:51
grapexI am commenting that I don't know how it works19:52
grapexbecause the way the code is written is confusing19:52
grapexdenis_makogon: Maybe I should look at this...19:52
denis_makogongrapex, of course, if you want19:54
denis_makogongrapex, the vely last thing for today, could you please re-review https://review.openstack.org/#/c/86300/ this one ? All your suggestions i took into account19:56
*** fifieldt_ has joined #openstack-trove20:00
*** yogeshme_ has quit IRC20:01
*** yogeshmehra has joined #openstack-trove20:02
*** mattgriffin has joined #openstack-trove20:03
*** yogeshme_ has joined #openstack-trove20:04
*** fifieldt-afk has quit IRC20:04
*** yogeshmehra has quit IRC20:04
*** mattgrif_ has joined #openstack-trove20:05
*** mattgriffin has quit IRC20:06
*** mattgrif_ has quit IRC20:10
*** mattgriffin has joined #openstack-trove20:10
grapexdenis_makogon: Done, a few more nit picks though20:10
denis_makogongrapex, thanks20:11
*** yidclare has joined #openstack-trove20:11
*** denis_makogon has quit IRC20:12
*** PeterSchwaller_ has joined #openstack-trove20:13
*** PeterSchwaller has quit IRC20:15
*** mattgriffin has quit IRC20:18
*** sbfox1 has quit IRC20:19
*** yidclare has quit IRC20:23
*** jcromer has joined #openstack-trove20:27
jcromerhello, is anyone around?  I have a problem that i need some help on.  Would like to ask a quick question.20:28
jcromerI am seeing Cannot find compute instance None for instance in my taskmanager log20:30
juicejcromer: how did you build your stack? devstack?20:30
jcromerjuice: no built from ubuntu packages20:31
juicedepending on the context of that error message it may be non issue20:31
*** michael-yu has quit IRC20:31
jcromerjuice: it is on its own node20:31
juicecan you paste the entire and exact log message20:31
juicejcromer: if I understand what you are saying, you spun up a vm via nova and on that vm did and apt-get install trove-taskmanager20:32
jcromerjuice: 2014-06-04 16:30:08.902 12717 ERROR trove.common.exception [req-b32f4af6-80d3-4f43-9d57-cb31eda9a11e 8d456978afa849feb46ea64f494107ab 2cce88b4c1944f7cb18701c6fc5e36f7 - - -] Cannot find compute instance None for instance 8db902c0-676a-48ac-8e78-fe854ecd6605.20:32
jcromerno20:32
*** boden has quit IRC20:32
jcromersorry20:32
jcromerjuice: we spun up a machine and installed trove package on it20:33
juicejcromer: what configuration/installation guide did you follow?20:33
*** michael-yu has joined #openstack-trove20:34
jcromerjuice: http://docs.openstack.org/icehouse/install-guide/install/yum/content/trove-install.html20:34
juicejcromer: did you configure/customize /etc/trove/trove*.conf20:34
jcromerjuice: yes20:34
jcromerjuice: sorry used http://docs.openstack.org/icehouse/install-guide/install/apt/content/trove-install.html20:35
jcromerjuice: it is on ubuntu 14.0420:35
juiceok - if you do a nova list, with the same creds that you used to create the trove instance do you get any instances listed20:35
espSlickNik: ping20:35
juicejcromer: afaik we only test and verify on 12.0420:35
juicejcromer: also can you do a "trove flavor-list"20:36
SlickNikesp: 'sup?20:36
jcromerjuice: well i don't have a nova-client installed on the trove node, but if i used the same user on nova controller i do get instances just not database20:36
espSlickNik: I just pulled down a new trove-integration and ran the tests.20:36
esplooks like they are stuck on a couple of tests20:37
esphttps://gist.github.com/dan1/c4194d0a8de9d027041d20:37
jcromerjuice: trove flavor-list works20:37
juiceso it looks like at some point you tried to create a trove instance, trove started the process of provisioning the instance but failed to connect to nova in some fashion and now you have a half-baked instance in trove20:37
jcromerjuice: so does trove list20:37
juicetrove list shows your instance?20:37
jcromerjuice: i do have one in error status and two in build20:37
juiceif you do a "trove show <instance id>" on any of those instances do you they return and do they show a server id?20:39
jcromerjuice: they return and show an id, but status of error on the one that is error20:40
jcromerjuice: let me try one of the ones stuck perpetually in build20:40
juicejcromer: what flavor are you using to boot the instances?20:40
jcromerjuice: 220:40
jcromerjuice: the ones that are stuck in build state I am unable to delete20:41
SlickNikesp: strange. Can you check your trove-api.log to see what the actual ERROR was when the test_configuration_is_applied_to_instance test was executed?20:41
espSlickNik: yep20:42
* esp looking ...20:42
*** yidclare has joined #openstack-trove20:42
SlickNikesp: I've kicked off a pure rdjenkins run to verify, but it looks like there were successful runs of the int-tests from earlier this morning (https://rdjenkins.dyndns.org/job/Trove-Gate/3949/)20:43
juicejcromer: that is unfortunately the case unless you set a flag in task manager to convert them to ERROR in these conditions20:43
*** yidclare has quit IRC20:43
SlickNikNot 100% sure but perhaps the issue may be timeout / environment related.20:43
juicejcromer: the way I get rid of those is to manually mark them as ERROR in the trove db and then through the trove command line, delete them20:43
juicethere is a status flag on the instances table that can be updated20:44
jcromerjuice: i will check the db20:44
juicethis is a PITA...but its what I do20:44
juiceperhaps someone else has a better solution20:44
espSlickNik: 2014-06-04 13:30:53.761 ^[[01;31mERROR trove.extensions.mgmt.instances.models [^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31mResource 22b46dcd-c4cb-4e4c-8f6d-58fe1015cff2 can not be retrieved.^[[00m20:45
*** mattgriffin has joined #openstack-trove20:45
*** sbfox has joined #openstack-trove20:45
juicejcromer: the best place to check is in the logs (nova and trove) to see what is the reason for the error20:46
espSlickNik: k, let me try to find the secret time out :)20:46
SlickNikesp: It's a decorator on the test class. But I'd first look in the log to see if that's indeed the issue.20:47
*** sbfox has quit IRC20:50
*** sbfox has joined #openstack-trove20:50
jcromerjuice: what are you setting to error in the instances table20:53
juiceI believe it is status or status_id20:53
juiceyou will see a status(_id) and description20:53
juicedescription is not important20:53
juiceI believe the value 8 is valid for a type of ERROR20:53
jcromeri see server_status column20:53
juicejcromer: is it numeric?20:54
jcromervarchar20:54
juicelet me take a look20:54
openstackgerritA change was merged to openstack/trove: pep8: Ignore locale files  https://review.openstack.org/9708720:55
espSlickNik: k, thx!20:56
juicesorry the correct table is server_statuses jcromer20:57
juiceservice_statuses (sheesh)20:57
espSlickNik: 2014-06-04 13:27:50.289 ERROR trove.guestagent.api [-] Timeout while waiting on RPC response - topic: "guestagent.a485beef-b7ec-480d-8815-48ccc5621572", RPC method: "get_filesystem_stats" info: "<unknown>"20:57
espSlickNik: I do see a lot of these.20:57
espI’ll see if messing with the timeout helps20:58
*** sbfox has quit IRC20:58
*** pdmars has quit IRC20:58
*** michael-yu has quit IRC21:05
*** michael-yu has joined #openstack-trove21:07
*** amcrn_ has joined #openstack-trove21:07
*** sbfox has joined #openstack-trove21:08
*** amcrn has quit IRC21:09
openstackgerritPeter Stachowski proposed a change to openstack/python-troveclient: Added optional marker/limit to list command  https://review.openstack.org/9793621:10
jcromerjuice: 8 doesn't seem to work21:11
jcromerjuice: still in build status21:11
*** yidclare has joined #openstack-trove21:12
*** sgotliv has quit IRC21:13
*** yogeshme_ has quit IRC21:15
*** yogeshmehra has joined #openstack-trove21:16
*** yogeshmehra has quit IRC21:19
*** yogeshmehra has joined #openstack-trove21:20
*** sbfox has quit IRC21:20
*** rueben has quit IRC21:26
*** sgotliv has joined #openstack-trove21:29
*** jcromer has quit IRC21:30
*** rueben has joined #openstack-trove21:32
*** demorris has quit IRC21:33
*** sgotliv has quit IRC21:37
*** demorris has joined #openstack-trove21:38
*** radez is now known as radez_g0n321:45
*** yogeshmehra has quit IRC21:46
*** yogeshmehra has joined #openstack-trove21:47
*** rueben_ has joined #openstack-trove21:49
*** yogeshmehra has quit IRC21:51
*** rueben has quit IRC21:53
*** rueben_ has quit IRC21:53
*** Barker has quit IRC21:58
openstackgerritPeter Stachowski proposed a change to openstack/trove: Added an int-test for user-update-attributes  https://review.openstack.org/9795221:59
*** sbfox has joined #openstack-trove22:01
*** sbfox has quit IRC22:11
*** sbfox has joined #openstack-trove22:11
*** demorris has quit IRC22:11
*** sbfox has quit IRC22:11
*** achampion has quit IRC22:11
*** yogeshmehra has joined #openstack-trove22:12
*** amcrn_ has quit IRC22:24
*** jmontemayor has quit IRC22:29
*** thedodd has quit IRC22:30
*** sbfox has joined #openstack-trove22:32
grapexesmute SlickNik vipul: I've got another concern nagging me on this pull request to add datastore metadata to backups22:37
grapexSo we're associating the datastore version name, and datastore name - two strings- to a backup, due to cross region funtimes22:38
grapexI guess my problem is we are treating that tuple as the definitive ID for a datastore22:38
grapexamcrn: ^^22:38
grapexSo honestly, what purpose is the ID serving at this point?22:39
vipulgrapex: Yep, that's what it ends up being.. I don't see another way to do this.. unless we add region:id or something.. and enforce that Trove goes to that region to lookup the actual datastore type22:39
grapexIf you work with datastores in a region, you use the nasty ID, but if working across regions, we use strings?22:40
grapexYeah22:40
hub_capid prefer the opposite22:40
grapexvipul: So the root problem (which won't get solved anytime soon) is the IDs should maybe, somehow, be globally unique amongst regions22:40
*** amcrn has joined #openstack-trove22:40
hub_capuuid across region, string name shorthand within a region22:40
vipulgrapex: You mean ID's shoudl be the same across regions?22:41
esmutehow does other openstacks project solve this cross-region ID issues?22:41
vipulthe problem is that another region doesn't have that ID..22:41
hub_capaww hell vipul why u gotta be right22:41
grapexalso, if these IDs are guids, shouldn't they be unique?22:42
grapexWhat if we had alias ids?22:42
vipulthe only way to solve it is amcrn's approach where.. we have a template like <region>:<id> -- and Trove is aware of the other regions and does lookups22:42
esmuteunless the database is shared across regions22:42
amcrnlook at what conversation i just dropped into ;D22:43
vipulesmute: which we don't want to enforce22:43
grapexSo here's my issue- until now, we could, if we wanted, change the names of datastores or versions22:43
*** cweid has quit IRC22:43
SlickNikhi amcrn, what have we here.22:43
grapexI mean yes, users would have to get used to different names- but everything else would work22:43
grapexthis new thing is saying they have to be eternally constant22:43
grapexso if you use a name for something you later badly wish you used for something else, too bad22:44
hub_capamcrn: GET A BOUNCER!!!22:44
vipulgrapex: not necessarily.. it works as long as you change it in all regions22:44
amcrnhub_cap: i'm caught up, i read the eavesdrop22:44
hub_cap;)22:45
grapexvipul: Change it in all regions, and then update every existing backup record in the database... in all regions22:45
hub_capamcrn: bt srsly, et a bouncer22:45
hub_capand ill buy a U and a G alex22:45
grapexI feel like we're violating a law here by using these names for the ID. We're making renaming them close to impossible22:45
vipulgrapex: nah.. the db records are fkey'd by IDs.. just gotta make sure the names are consistent across regions22:45
grapexI think aliases really would solve this problem easier as a short term solution22:45
grapexmaybe we need a global UUID22:46
grapexfor datastore versions22:46
grapexif you want cross-region functionality, make sure they align22:46
hub_capi think thats sane22:46
hub_caplets call it "mysql"22:46
hub_capand "redis"22:46
grapexwe'll call it a UUUID22:46
grapexor maybe U3ID for short22:46
hub_capU^3ID22:46
vipulhow about call it a tuple of datastore name and version :)22:46
SlickNikbetter yet, have a tuple22:47
hub_capvipul: too wordy22:47
vipulhonestly isn't that the sme thing22:47
grapexvipul: Then we hit the problem I've been describing22:47
vipulsure.. but same arument.. if you care about cross region.. can't you just enforce the name is consistent?22:47
vipulinstead of introducing yet another thing22:47
esmutewe can have "datastore_name:version_name" as the ID... a tuple just like it was suggested22:48
grapexI guess my problem is we *should* be introducing another thing instead of relying on a kind of idiom that becomes a rule people have to know to follow22:48
grapexand they don't realize they didn't follow it until its too late22:48
esmutekeep in mind that this are just meta data for backups... no where else in trove will they care or refer to datastore by their name22:49
vipulyea i get your point.. it's a little sneaky..22:49
esmuteonce the backups are copied, their records will contains id for datastore22:49
vipulesmute: won't this metadata be used in some way when you create an instance from a backup in another region?22:49
*** NehaV1 has quit IRC22:49
esmutevipul: Nop... when the backup is 'copied', a new backup record is created, which contains datastore id (instead of names)22:50
esmuteand then everything would be the same after22:50
vipulok.. so the backup-copy call requires the metadata?22:50
esmutethat datstore name is only needed for the metadata which is stored in swift22:50
esmutevipul: correct22:50
esmutethat datastore name, (or tuple or GUUID ) wont queried or saved in the trove DB22:51
esmutewont be queried*22:51
grapexMaybe the compromise here that keeps us moving forward is to... also save the ID22:52
vipulbut the tuple has to be understood by the Trove.. so it can associate the correct datastore id?22:52
grapexso we save datastore name, version name (the string tuple) and the datastore version ID.22:52
SlickNikSo another option is to require the backup-copy call to require the user to input which local datastore the remote backup corresponds too.22:52
esmutevipul: only the backupagent needs to understand that...22:53
vipulSlickNik: then the issue is they could totally screw the backup up by choosing the wrong datastore22:53
SlickNikAnd if the user screws that up, and there is a mismatch, we'll fail horribly, and well *shrug* PEBCAK.22:53
esmutethe backup agent download backup from swift and parse metadata file in swift (which contains the datastore name), and then it create a new backup record with the datastore ID22:53
vipulgrapex: what does saving the ID give us.. i guess i'm trying ot figure out what the BackupAgent would do with that ID22:54
SlickNikvipul: I said it was an option; I didn't necessarily say it was a *good* one. :)22:55
grapexesmute: Why would the agent do that and not Trove?22:55
vipulyea, actualy the copy shouldn't go to any Agnet.. it's a server side thing22:55
grapexvipul: I am worried we'll not like having this one feature of Trove not use the datastore_version.id22:56
grapexso it gives us an escape hatch for when things improve22:56
esmuteoops.. you are right... the copy is done by the TM... ignore what i said22:56
grapexesmute vipul: So quick questions about you use case. Sorry I'm rusty on how backups work. The idea is someone can make a backup in region A, then restore to region B, right?22:57
vipulgrapex: yea that would be fine.. except that you may poentially have a ID as part of metadata that doesn't exist in that region after the copy is done22:57
esmutethe agent creates the metadata that gets put in swift...22:57
vipulgrapex: that's the goal22:57
esmutegrapex: yes and no.. there is a intermediate work22:57
*** demorris has joined #openstack-trove22:57
grapexDo they do this by passing in a swift url that came from region A?22:57
esmutethe backup in A is copied to region B.... when the user can just restore normarly as if the backup was created in region B22:58
*** yogeshmehra has quit IRC22:58
vipulI think there are two approaches you can take.. 1) directly pass a ID/ swift URL from region A to region B .. or 2) copy the backup to region B22:58
vipulesmute: was tehre a reasion 2) was chosen?22:58
esmutethe backup-copy will stream backup in region A to the swift in region B and create the backup record in region B22:58
*** yogeshmehra has joined #openstack-trove22:58
grapexAlso, how are checksums handled?22:59
*** shakayumi has joined #openstack-trove22:59
esmutevipul: i didnt want to make changes in the restore....22:59
*** jcru has quit IRC22:59
SlickNikgrapex: The idea is that someone makes a backup X in region A. Then creates a "copied" backup Y in region B (copied from the swift files and metadata of backup X),22:59
esmuteit was much easier to just stream copy the backup from one swift to another and create a DB record22:59
vipulSlickNik, esmute: does this issue go away if we just did option 1?23:00
vipulwe talked about a URI scheme before when reviwing this BP23:00
SlickNikgrapex: Once the new "copied" backup Y exists in region B, you can do a restore using backup Y (as you can today).23:00
vipulwhere we'd use that region:ID / region:url to a Instance-create call23:00
grapexSlickNik: What code is making the copy from region A to region B?23:00
esmutegrapex: i havent put it up.. let me get a gist23:01
SlickNikgrapex: Some code that esmute was working on, I think. :)23:01
grapexAt some point it seems you have to copy the checksum from region A to region B- you can't assume the Swift metadata's checksum is accurate as the user can manipulate it23:01
grapexunless I'm wrong, at that point the Trove databases in regions A and B have to communicate with each other23:02
*** saurabhs has left #openstack-trove23:02
esmutegrapex: you are right.. if users manipulate the backup or metadata, the backup copy will be error.. or the restore will error out23:02
esmutehttps://gist.github.com/kokhang/59f725df728854e2f3fd23:04
grapexif the db's are talking, Trove code could sort out the mapping of datastore_version.IDs between A and B. At that one small point in time, they could even do this using the datastore name and datastore version version strings until a more perfect solution is found (which admittedly will be never)23:04
esmutethat is the code that does the copy.. it is done in the TM23:04
esmutegrapex: db are not the one talking... swift are the one talking.. so we assume that swift is globally shared across regions23:05
SlickNikesmute: I think what grapex is saying is that you can't get away with just pulling the data from swift since that data could be compromised.23:05
grapexBut Swift can't be trusted 100% because the user has access to and can change any of the metadata.23:05
esmutewhat this code does is just pull backup from region A in swift, parse the metadata in region A, streams to region B with new metadata, and creates a backup record in the DB23:06
SlickNikesmute: And without verifying the checksum, there's really no way you can tell.23:06
*** tvoran has quit IRC23:06
amcrnbut in short, you'll guaranteed need at a minimum *some* replication of state; take clusters for instance. the cluster-id itself should be understood, irrespective of the region endpoint.23:07
esmutethe checksum is read from the source metadata23:08
grapexCan't we solve this by introducing a mgmt API to Trove that could fetch this data?23:08
grapexRegion B gets a request for a restore, using a backup ID from region A23:08
grapexso it calls region A on its mgmt super-admin hotline to get the skinny on what the backup from A looks like: what the datastore originally involved was, the checksum, and the swift URL23:09
esmutegrapex: but the idea was that the users would use this backup-copy... having it in mgmt would prevent that23:09
grapexthen the Trove on region B copies things as esmute describes but applies the original checksum and other equivalent metadata to the metadata of its fresh copy in Swift's region B23:09
grapexesmute: it sounds like this isn't a backup copy then but an import of arbitrary data in Swift23:10
*** yogeshmehra has quit IRC23:10
grapexwhich is a good idea but it introduces difference23:10
amcrnesmute: "so we assume that swift is globally shared across regions" => we can't make that assumption23:10
esmuteamcrn: if we dont, then how would one access the objects in another swift.. im assuming that the token in keystones are shared across region23:12
amcrnthis is going to have to behave a lot like federated identity in keystone; either you'll need a galera-like cluster to replicate certain 99% read-only metadata tables (like datastore, datastore-version, etc.), or something within trove will have to initiate multi-writes to every known registered endpoint23:12
amcrnesmute: identity can be the same across regions, but that doesn't mean that the swift deployments are23:12
amcrnwith the multi-writes going to a mgmt-api23:13
*** demorris has quit IRC23:14
esmuteif that is the case, it wouldnt matter whether we use datastore id or name... this is a new problem we need to discuss23:14
grapexesmute: So... getting back to the pull request, I guess I'm ok with sticking the version, name, whatever into the metadata. It looks like the datastore_version.id is being associated with the backup in the database which is enough to make me happy with this pull request.23:14
grapexesmute: Although- I wonder if we should be returning the datastore version ID in the view with the backup.23:15
*** shakayumi has quit IRC23:15
grapexI know UI writers will want the name and version though so maybe I should stop talking.23:15
amcrngrapex: that's inferrable from the uuid though :)23:16
grapexamcrn: agreed23:16
grapexamcrn: I know right away though our UI guys will complain. But I can't help but 100% agree with you.23:16
amcrngrapex: well, on list-view, having to make an additional call does bring down responsiveness a bit, so i kind of see their angle23:16
esmuteamcrn:  i think we need to have a separate talk about the whole cross-regions comunication between troves...23:17
esmutegrapex: i thought names would be more readble :P23:17
grapexesmute: We do. I just wanted to bring it up to understand your motivations.23:17
amcrnesmute: 100% agree my friend, it's definitely a tricky problem :)23:17
grapexesmute: Thanks for explaining things.23:17
grapexesmute: So I am ok with the views returning that extra data. I think anyone writing a UI will be thrilled.23:18
grapexI do think we should add the datastore version ID though23:18
esmutegrapex, amcrn: im pretty much done with the cross-region feature... i havent put it up since i am waiting for https://review.openstack.org/#/c/86242/ to get there23:19
esmuteonce we see the review, we can discuss this further.23:19
amcrngrapex: for what it's worth, configuration-group returns the datastore_version_id, and not the names23:19
grapexamcrn: yeah. I'm going to -1 this until the datastore_version_id is returned for the view.23:20
grapexI think it should be in addition to the name / version tuple though, since anyone writing a UI will want that.23:21
SlickNikamcrn: Do we have a bug for that? If not let me open one.23:23
*** sbfox has quit IRC23:26
*** amytron has quit IRC23:29
*** amytron has joined #openstack-trove23:29
SlickNikamcrn: We do now. FYI https://bugs.launchpad.net/trove/+bug/132658423:31
amcrnSlickNik: cool, thanks (was grabbin' a redbull, you beat me to the punch)23:31
SlickNikamcrn: No worries. My turn to go grab some caffeine. bbiab :)23:35
grapextalk to you all later!23:43
*** grapex has quit IRC23:43
*** sbfox has joined #openstack-trove23:48
*** amytron has quit IRC23:49
*** michael-yu has quit IRC23:53

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