Monday, 2014-09-08

*** julienvey has joined #openstack-trove00:18
*** julienvey has quit IRC00:22
*** juantwo_ has quit IRC00:24
*** juantwo has joined #openstack-trove00:25
*** ViswaV has joined #openstack-trove00:59
*** ViswaV has quit IRC01:00
*** julienvey has joined #openstack-trove01:19
*** julienvey has quit IRC01:24
*** georgelorch has quit IRC01:30
openstackgerritNikhil Manchanda proposed a change to openstack/trove: Updated from global requirements  https://review.openstack.org/11914901:30
*** georgelorch has joined #openstack-trove01:35
*** newb__ has quit IRC01:38
*** nosnos has joined #openstack-trove01:51
*** Riddhi has quit IRC02:12
*** julienvey has joined #openstack-trove02:19
*** julienvey has quit IRC02:25
*** ramishra has joined #openstack-trove02:35
*** vkmc has quit IRC02:47
*** rushiagr_away is now known as rushiagr02:52
*** rushiagr is now known as rushiagr_away03:03
*** rushiagr_away is now known as rushiagr03:05
*** rushiagr is now known as rushiagr_away03:16
*** julienvey has joined #openstack-trove03:20
*** mrsnivvel has joined #openstack-trove03:23
*** hollandais has quit IRC03:24
*** julienvey has quit IRC03:25
*** prasoon has joined #openstack-trove03:38
*** ramishra has quit IRC03:45
*** ramishra has joined #openstack-trove03:47
*** achampion has quit IRC04:03
*** achampion has joined #openstack-trove04:09
*** rushiagr_away is now known as rushiagr04:11
openstackgerritNikhil Manchanda proposed a change to openstack/trove: Delete backup created during replication  https://review.openstack.org/11916904:14
*** eghobo has joined #openstack-trove04:14
*** julienvey has joined #openstack-trove04:21
*** ramishra has quit IRC04:21
*** ramishra has joined #openstack-trove04:22
*** ramishra has quit IRC04:23
*** ramishra has joined #openstack-trove04:24
*** jasonb365 has joined #openstack-trove04:24
*** julienvey has quit IRC04:26
*** eghobo has quit IRC04:30
*** juantwo has quit IRC04:33
*** ramishra has quit IRC04:35
*** ramishra has joined #openstack-trove04:36
*** edmund has quit IRC04:45
*** eghobo has joined #openstack-trove04:47
*** edmund has joined #openstack-trove04:47
*** eguz has joined #openstack-trove04:48
*** jasonb365 has quit IRC04:48
*** eghobo has quit IRC04:49
*** ViswaV has joined #openstack-trove04:49
*** edmund has quit IRC04:51
*** jasonb365 has joined #openstack-trove05:05
*** eguz has quit IRC05:06
*** eghobo has joined #openstack-trove05:06
*** ViswaV has quit IRC05:15
*** ViswaV has joined #openstack-trove05:15
*** boblebauce has joined #openstack-trove05:17
*** ajayaa has joined #openstack-trove05:18
*** julienvey has joined #openstack-trove05:22
*** boblebauce has quit IRC05:22
*** julienvey has quit IRC05:26
*** sgotliv has joined #openstack-trove05:32
*** boblebauce has joined #openstack-trove05:33
*** boblebauce has quit IRC05:39
*** flaper87|afk is now known as flaper8705:39
*** ViswaV has quit IRC05:56
*** nosnos has quit IRC05:57
*** nosnos_ has joined #openstack-trove06:00
openstackgerritOpenStack Proposal Bot proposed a change to openstack/trove: Imported Translations from Transifex  https://review.openstack.org/11769506:06
*** jasonb365 has quit IRC06:08
*** ajayaa has quit IRC06:11
*** vigneshvar has joined #openstack-trove06:18
*** julienvey has joined #openstack-trove06:22
*** julienvey has quit IRC06:28
*** PeterSchwaller has quit IRC06:33
*** ViswaV has joined #openstack-trove06:36
*** ajayaa has joined #openstack-trove06:38
*** ViswaV has quit IRC06:39
*** sgotliv has quit IRC06:44
*** eguz has joined #openstack-trove06:46
*** eghobo has quit IRC06:49
*** PeterSchwaller has joined #openstack-trove06:50
*** julienvey has joined #openstack-trove06:50
*** julienvey has quit IRC06:54
*** eguz has quit IRC06:55
*** ajayaa has quit IRC07:08
*** vigneshvar has quit IRC07:09
*** Longgeek has joined #openstack-trove07:16
*** ajayaa has joined #openstack-trove07:21
*** Longgeek has quit IRC07:33
*** ajayaa has quit IRC07:33
*** ramishra has quit IRC07:35
*** ramishra has joined #openstack-trove07:35
*** vigneshvar has joined #openstack-trove07:36
*** ramishra has quit IRC07:46
*** ViswaV has joined #openstack-trove07:46
*** ramishra has joined #openstack-trove07:47
*** ajayaa has joined #openstack-trove07:55
*** sgotliv has joined #openstack-trove08:07
*** julienvey has joined #openstack-trove08:07
*** Longgeek has joined #openstack-trove08:07
*** ramishra has quit IRC08:21
*** ramishra has joined #openstack-trove08:21
*** ViswaV_ has joined #openstack-trove08:28
*** ViswaV has quit IRC08:30
*** ramishra has quit IRC08:37
*** ramishra has joined #openstack-trove08:37
*** ViswaV_ has quit IRC08:40
*** ramishra has quit IRC08:40
*** ramishra has joined #openstack-trove08:41
*** ramishra has quit IRC08:51
*** ramishra has joined #openstack-trove09:01
*** eghobo has joined #openstack-trove09:22
*** julienvey has quit IRC09:23
*** eghobo has quit IRC09:23
*** ramishra has quit IRC09:35
*** ramishra has joined #openstack-trove09:37
*** isviridov_away is now known as isviridov09:45
*** vigneshvar has quit IRC09:49
*** vigneshvar has joined #openstack-trove09:50
*** sgotliv has quit IRC09:57
*** ramishra has quit IRC10:20
*** ramishra has joined #openstack-trove10:20
denis_makogonguys, i've noticed Trove CI jobs are failing due to timeouts on replication tests, see https://bugs.launchpad.net/trove/+bug/136673510:26
*** sgotliv has joined #openstack-trove10:38
*** prasoon has quit IRC10:42
*** ramishra has quit IRC10:42
*** ramishra has joined #openstack-trove10:48
*** IanGovett has joined #openstack-trove10:50
*** isviridov is now known as isviridov_away10:51
*** prasoon has joined #openstack-trove11:17
*** tomblank has quit IRC11:21
*** prasoon has quit IRC11:32
*** prasoon has joined #openstack-trove11:32
*** vkmc has joined #openstack-trove11:32
*** prasoon has quit IRC11:38
*** prasoon has joined #openstack-trove11:39
*** prasoon has quit IRC11:40
*** ramishra has quit IRC11:42
*** ramishra has joined #openstack-trove11:46
*** ramishra has quit IRC11:49
*** juantwo has joined #openstack-trove12:00
*** juantwo has quit IRC12:01
*** juantwo has joined #openstack-trove12:02
*** julienvey has joined #openstack-trove12:02
*** nosnos_ has quit IRC12:13
*** julienvey has quit IRC12:14
*** nosnos has joined #openstack-trove12:14
*** newb__ has joined #openstack-trove12:16
*** nosnos has quit IRC12:18
*** georgelorch has quit IRC12:21
*** georgelorch has joined #openstack-trove12:21
*** newb__ has quit IRC12:21
*** achampion has quit IRC12:26
*** IanGovett1 has joined #openstack-trove12:30
*** IanGovett has quit IRC12:32
*** tomblank has joined #openstack-trove12:40
*** julienvey has joined #openstack-trove12:42
*** amrith is now known as _amrith_12:47
*** radez_g0n3 is now known as radez12:51
*** isviridov_away is now known as isviridov13:03
*** newb__ has joined #openstack-trove13:05
*** newb__ is now known as newb13:05
*** Longgeek has quit IRC13:08
*** Longgeek has joined #openstack-trove13:11
*** tkatarki has joined #openstack-trove13:13
*** ramishra has joined #openstack-trove13:22
*** IanGovett has joined #openstack-trove13:23
*** jasonb365 has joined #openstack-trove13:25
*** IanGovett has quit IRC13:25
*** IanGovett1 has quit IRC13:26
*** IanGovett1 has joined #openstack-trove13:27
*** IanGovett1 has quit IRC13:29
*** IanGovett1 has joined #openstack-trove13:29
*** achampion has joined #openstack-trove13:34
*** boblebauce has joined #openstack-trove13:34
*** rhodgin has quit IRC13:40
*** julienvey has quit IRC13:42
*** boblebauce has quit IRC13:45
*** miqui has joined #openstack-trove13:49
*** prasoon has joined #openstack-trove14:03
openstackgerritDenis M. proposed a change to openstack/trove: Forbid replica provisioning from non-root replica site  https://review.openstack.org/11729814:12
openstackgerritDenis M. proposed a change to openstack/trove: Fix master status validation while replica provisioning  https://review.openstack.org/11725514:12
*** _amrith_ is now known as amrith14:13
openstackgerritDenis M. proposed a change to openstack/trove: Fix master status validation while replica provisioning  https://review.openstack.org/11977014:14
openstackgerritDenis M. proposed a change to openstack/trove: Forbid replica provisioning from non-root replica site  https://review.openstack.org/11977114:14
openstackgerritPeter Stachowski proposed a change to openstack/trove: Document Trove configuration options  https://review.openstack.org/11875914:19
*** rhodgin has joined #openstack-trove14:23
*** ramishra has quit IRC14:24
*** ramishra has joined #openstack-trove14:24
*** ajayaa has quit IRC14:29
*** mattgriffin has joined #openstack-trove14:29
*** eghobo has joined #openstack-trove14:30
*** grapex has joined #openstack-trove14:40
*** isviridov is now known as isviridov_away14:40
*** Barker has joined #openstack-trove14:42
*** edmund has joined #openstack-trove14:43
*** kevinconway has joined #openstack-trove14:44
denis_makogonguys, i'm getting an error for fresh new Trove repo https://bugs.launchpad.net/trove/+bug/136683714:47
*** iartarisi has joined #openstack-trove14:48
*** sriram_tesora has joined #openstack-trove14:49
*** eghobo has quit IRC14:50
*** prasoon has quit IRC14:51
*** julienvey has joined #openstack-trove14:55
*** grapex has quit IRC14:55
*** grapex has joined #openstack-trove14:55
*** prasoon has joined #openstack-trove14:58
*** Riddhi has joined #openstack-trove14:59
*** prasoon has quit IRC15:01
*** tomblank has quit IRC15:05
denis_makogongrapex, ping15:05
denis_makogongrapex, hey, could you please take a look at https://review.openstack.org/#/c/97194/ (it was approved once, long time ago, but was forgotten later)15:06
*** jmontemayor has joined #openstack-trove15:09
*** boblebauce has joined #openstack-trove15:12
*** julienvey has quit IRC15:18
*** amrith is now known as _amrith_15:20
*** boblebauce has quit IRC15:21
*** boblebauce has joined #openstack-trove15:21
*** boblebauce has quit IRC15:22
*** isviridov_away is now known as isviridov15:23
icchadenis_makogon: do u know where to see the rdjenkins logs? its no longer posting stuff on the review15:27
icchabuffer 1815:27
denis_makogoniccha, i added link and "how-to" get rdjenkins logs to the review =)15:27
denis_makogoniccha, it is still posting, but hidden15:27
denis_makogoniccha, there's a button called "Toggle CI" at the bottom, left corner15:28
icchathanks yeah15:28
icchaok gotcha15:28
denis_makogoniccha, you're welcome15:28
*** boblebauce has joined #openstack-trove15:30
openstackgerritRiddhi Shah proposed a change to openstack/trove: Allow users the ability to update an instance name  https://review.openstack.org/9270115:31
*** tkatarki has quit IRC15:35
*** tkatarki has joined #openstack-trove15:44
*** tomblank has joined #openstack-trove15:46
*** johnma has joined #openstack-trove15:47
openstackgerritRiddhi Shah proposed a change to openstack/trove: Add visibility filter to datastore versions  https://review.openstack.org/11019715:47
flaper87hey folks, at the Juno summit we talked about possible use cases in Trove for Zaqar (ex Marconi). My memory is terrible so I don't remember to whom I talked to but I was hoping I could gather those use cases again in this etherpad: https://etherpad.openstack.org/p/zaqar-integrated-projects-use-cases15:48
flaper87if any of you have some time to add them there, I'd really appreciate it15:48
denis_makogonhey, guys, i've wrote small cool thing for documenting our opts, hope you enjoy in https://gist.github.com/denismakogon/602620e0200f512d39f915:50
flaper87denis_makogon: have you seen this? https://github.com/openstack/oslo-incubator/tree/master/tools/config15:51
flaper87it generates the config file with the doc strings15:51
denis_makogonflaper87, i saw, but i hate bash, python variant looks a bit cleaner =)15:53
flaper87denis_makogon: it's actually python because that script uses: https://github.com/openstack/oslo-incubator/blob/master/openstack/common/config/generator.py15:54
flaper87lots of folks have worked on cleaning `config.generator`, it'll soon not depend on the bash script anymore.15:54
denis_makogonflaper87, sound awesome =)15:56
*** _amrith_ is now known as amrith16:02
*** tomblank_ has joined #openstack-trove16:04
*** boblebauce has quit IRC16:04
*** tomblank has quit IRC16:05
*** tomblank_ is now known as tomblank16:05
*** nealph_ has joined #openstack-trove16:08
openstackgerritSergey Gotliv proposed a change to openstack/trove: [WIP] Updates RPC API to use oslo.messaging  https://review.openstack.org/9448416:08
*** nealph_ has quit IRC16:11
*** isviridov is now known as isviridov_away16:13
*** sgotliv has quit IRC16:13
*** rushiagr is now known as rushiagr_away16:14
*** vigneshvar has quit IRC16:16
*** eghobo has joined #openstack-trove16:21
openstackgerritA change was merged to openstack/python-troveclient: Use 'replica' instead of 'slave'  https://review.openstack.org/11792516:23
*** ramishra has quit IRC16:24
*** ramishra has joined #openstack-trove16:24
*** ramishra has quit IRC16:29
*** ViswaV has joined #openstack-trove16:36
*** ViswaV_ has joined #openstack-trove16:37
*** ViswaV has quit IRC16:40
*** iartarisi has quit IRC16:44
openstackgerritRamashri Umale proposed a change to openstack/trove: Adds backup/restore support for mongodb  https://review.openstack.org/7833916:51
openstackgerritOpenStack Proposal Bot proposed a change to openstack/trove: Updated from global requirements  https://review.openstack.org/11981816:55
*** ViswaV_ has quit IRC16:58
*** Barker has quit IRC17:03
*** jasonb365 has quit IRC17:06
*** rushiagr_away is now known as rushiagr17:06
*** ViswaV has joined #openstack-trove17:11
icchaSlickNik: glucas i am planning to create a bug for moving the replication.cnf for master and slave to templates as well or a config value17:14
*** harlowja_away is now known as harlowja17:14
*** tomblank has quit IRC17:14
icchaSlickNik: glucas because I want to add gtids related config values for replication17:15
icchabut replication.cnf is hard coded17:15
esphowdy SlickNik17:22
espI’m pretty sure we don’t need this anymore correct? https://review.openstack.org/#/c/102315/17:22
*** vigneshvar has joined #openstack-trove17:24
espping SlickNik17:26
denis_makogonesp, why do we have to abandon V3 ?17:27
SlickNikesp: howdy17:28
*** newb has quit IRC17:28
espdenis_makogon: cuz I think someone else has already soved it ;)17:28
denis_makogonesp, when ? =)17:28
*** newb has joined #openstack-trove17:29
* esp pulling up my notes17:29
espstill lookin17:31
denis_makogonesp, ok =)17:33
espdenis_makogon: I wish I could show you … haha17:33
* esp embarrassing…17:33
SlickNikesp: I don't think we need it anymore, although a refresher from your notes will also certainly be helpful.17:34
denis_makogonesp, you can share it somehow with me17:34
denis_makogonSlickNik, so, why do we might need to drop V3?17:35
espSo SlickNik and denis_makogon: here is the short story..17:36
denis_makogonesp, hit it17:36
espthere was a requirement on our end to make the python-troveclient talk to keystone v317:36
denis_makogonand?17:37
espsince then this requirement has gone away17:37
espbut I think someone else has a better patch where they just use keystone client directly..17:38
espI’m trying to find that one now17:38
espso we can abandon my overly complicated and confusing patch in favor of the other one...17:38
denis_makogonesp, ok, i'll try to find it17:38
espI just have to find it17:38
denis_makogonif that's it, i'm fine17:38
espthx denis_makogon!17:38
espextra pair of eyes always helps17:38
denis_makogonesp, is that patch for trove or client ?17:40
espyeah dude it’s only for python-troveclient17:40
denis_makogonesp, can't see it here https://review.openstack.org/#/q/status:open+project:openstack/python-troveclient,n,z17:40
denis_makogonat least among open ones17:41
esphmm.. I don’t see it there…17:42
denis_makogonesp, was it published ?17:43
espI think so denis_makogon, we have in an internal spreadsheet somewhere...17:45
denis_makogonok17:45
espfound it!17:46
espso here is what the spreadsheet says17:46
espPatch to use keystonemiddleware (instead of python keystone client):17:46
esphttps://review.openstack.org/#/c/10854117:47
espha, denis_makogon and SlickNik, you guys reviewed it!17:47
espgood work17:47
denis_makogoni'm a bit confused, how does keystone middleware enables V3 ?17:49
espI bet we just need to update the pipeline in the trove api.ini file or whatever it’s called17:49
denis_makogonhm17:50
denis_makogonneed to investigate this question17:50
espthe v3 implementation was this wonky plugin support that detects what version of keyston the client is trying to use17:50
espdenis_makogon: yeah it’s probably worth a look.  fyi keystone v3 was in devstack last I looked, you just have to specify the v3 endpoint.17:51
denis_makogoni'll take a look at it, esp, thanks17:51
espnp denis_makogon, thank you ;)17:52
denis_makogonesp, thanks to you too17:52
*** iartarisi has joined #openstack-trove17:57
*** iartarisi has quit IRC18:00
*** Riddhi has quit IRC18:00
*** iartarisi has joined #openstack-trove18:00
*** Riddhi has joined #openstack-trove18:00
denis_makogonmeeting?18:01
SlickNikyes18:02
SlickNik#startmeeting trove-bp-review18:02
openstackMeeting started Mon Sep  8 18:02:14 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
grapexo/18:02
openstackThe meeting name has been set to 'trove_bp_review'18:02
denis_makogono/18:02
icchao/18:02
iartarisio/18:02
SlickNikAgenda at:18:02
zhiyano/18:02
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting18:02
amrith./18:02
dougshelley66o/18:03
schango/18:03
vgnbkro/18:03
SlickNik#topic SUSE support18:03
SlickNik#link https://blueprints.launchpad.net/trove/+spec/suse-support18:04
amrithiartarisi, floor is yours18:04
iartarisithank you18:04
iartarisiso I think the action item from last time was for me to create a blueprint which we can discuss18:04
iartarisithat's the blueprint ^^. If everyone's ok, I can start targeting the existing change requests against that18:04
iartarisiand over the coming weeks I will also start working on a SUSE(zypper) PackagerMixin18:05
iartarisihow does that sound to everyone?18:05
SlickNikiartarisi: Thanks for creating that. I had two questions:18:05
SlickNik1. Is there a list of work items / reviews that this BP entails?18:06
iartarisiI can quickly come up with one. There are three outstanding reviews + the not yet started PackagerMixin issue18:06
openstackgerritDan Nguyen proposed a change to openstack/trove-integration: Add a script to package the guest agent in a venv  https://review.openstack.org/10856218:07
*** jmontemayor_ has joined #openstack-trove18:08
iartarisihttps://review.openstack.org/108394 https://review.openstack.org/108703 https://review.openstack.org/10897218:08
iartarisithose are the outstanding reviews18:08
*** Barker has joined #openstack-trove18:08
SlickNik2. There were some concerns around the CI and maintenance around this, since it's not tested by upstream. You guys mention there's a SUSE CI, and you guys will be on the ball for any breaks in SUSE related areas, right?18:08
iartarisithese are already part of our packages and we have working trove with them.18:08
iartarisiSlickNik: right!18:09
amrithSlickNik, I believe the bugs being addressed here are the result of the SUSE CI (see, I got the capitaliztion right this time)18:09
iartarisiamrith: thanks! and that's right!18:09
openstackgerritamrith proposed a change to openstack/trove: Remove unused entries in cfg.py  https://review.openstack.org/11299518:10
SlickNikiartarisi / amrith: got it, thanks!18:10
SlickNikSounds good to me.18:11
iartarisiok, I have an aside here related to the PackagerMixin18:11
*** jmontemayor has quit IRC18:11
iartarisithat last review is about adding a NoOpPackagerMixin which wouldn't touch the system at all, but rather assume that the admin has set everything up18:11
iartarisiare you fine with adding that to trove?18:11
iartarisito me, as a distro packager, this seems like a much more sensible way for trove to act, rather than installing things itself which should be outside of the attributions of an app18:12
iartarisithat's also related to the SUSE support actually, since I believe we'd be more comfortable with just handling everything in packaging rather than in a SUSEPackagerMixin18:13
*** jmontemayor_ has quit IRC18:13
*** robertmyers has joined #openstack-trove18:14
amrithiartarisi, is this part of the BP as written? I think not, is that correct?18:14
SlickNikThe approach seems reasonable to me that this would be a selectable option if a deployer chose it — although I haven't had a chance to review the code yet, so you might get some more feedback once I review the code.18:14
iartarisiamrith: this is about one of the standing reviews and it would remove one item from the blueprint18:14
iartarisiSlickNik: that sounds good, selectable where?18:15
iartarisias a guestagent config value?18:15
amrithi assume the selection is that the deployer chooses the NoOpPackagerMixin?18:15
iartarisiin the review, the NoOpPackagerMixin is only a fallback, in case a compatible OS was not found18:16
SlickNikSo right now they're choses based on the distro, IIRC.18:16
iartarisibut I would definitely encourage having it as a configuration option, too18:17
SlickNikiartarisi: Let's hold that thought and keep the discussion on the review.18:18
SlickNikFWIW: I like the fallback to No-op in case we can't detect the distro.18:18
denis_makogoniartarisi, agreed with SlickNik18:18
SlickNik(in the interest of time)18:18
iartarisiSlickNik: alright, so I'll wait for how that goes before starting work on a SUSE Mixin18:18
SlickNikiartarisi: Sounds good. Thanks for the work on this!18:18
iartarisiSlickNik: cool. Thank you!18:19
SlickNikAny other comments on this?18:19
SlickNik.18:19
amrithI move that this be approved as written.18:19
SlickNikSeconded.18:20
icchasounds good to me.18:20
SlickNikLet's move on — we have a full agenda.18:20
SlickNik#topic SSL support18:20
SlickNikkevinconway: around?18:20
kevinconwayo/18:20
cp16neto\18:20
SlickNik#linkhttps://wiki.openstack.org/wiki/Trove/TroveSSL18:21
kevinconwayssl!18:21
kevinconwayso i outlined in the BP how ssl would work for mysql and postgresql18:22
kevinconwayi did some research on the others and wrote up how they would fit in18:22
SlickNikkevinconway: Yup, went through that -- but one of the concerns I have around this is the chicken and egg problem.18:23
SlickNikkevinconway: Since we don't have TLS, we don't have a secure way of getting the certs on to the datastore instance.18:23
kevinconwayah, i see. i should have specified in the BP. the keys would be delivered via the message q18:24
kevinconwayas a part of the prepare call, for example18:24
SlickNikAh, I see.18:24
cp16netcould they be injected into the instance via nova create?18:24
*** jasonb365 has joined #openstack-trove18:24
amrithkevinconway, I'm concerned about the work involved in key management and storage. These are non-trivial activities to get right. I'm also concerned about trove getting into the business of key creation, management, storage, etc.,18:25
kevinconwayso the precursor chicken lays a proto chicken egg. science!18:25
denis_makogoncp16net, i like this idea18:25
vgnbkrBut you shouldn't send a private key unless the connection you send it over is also secured.18:25
denis_makogonamrith, correct, this is a task for barbican =)18:25
kevinconwayamrith: so part of the BP is that the key provider should be an interface. we could have one or two default impls, but deployers should manage keys18:25
denis_makogonvgnbkr, honest true !18:25
amrithI submit to you that in the fullness of time, trove should merely indicate to the guest instance that it must enable ssl and the guest instance should request the various things directly from barbican18:26
amrithand trove should stay out of the equation.18:26
grapexamrith: when you say "guest instance", do you mean the agent?18:26
amrithgrapex: yes18:26
kevinconwayi agree that bbq is a part of the equation, but it doesn't actually support SSL certs.18:26
grapexBecause the guest agent is Trove as well18:26
amrithtrove itself should neither know nor see any part of SSL18:26
denis_makogonamrith, +118:27
amrithgrapex: understood18:27
amrithterminology18:27
grapexamrith: Your concern is that the Trove server daemons see the SSL certs18:27
amrithgrapex: yes18:27
grapexI think that's a solution for today's pre-Barbican era18:27
amrithother than the guest where the keys and the cert are installed, no other part of trove should see these things18:28
grapexIn the post-Barbican future Trove could contact it vicariously on behalf of the user18:28
amrithI don't like the fact that a prepare call provides the things18:28
amrithI'd rather the prepare call provide a URI where the guest can go and get the things it wants18:28
kevinconwayamrith: right now we don't have much of a choice. we would need to wait for bbq to support certs18:28
*** eghobo has quit IRC18:28
amrithnot necessarily true18:28
amrithif a user provides you the certs18:28
*** eghobo has joined #openstack-trove18:29
grapexamrith: Also, consider in the future that what Trove injects is a URI to Barbican rather than the certs itself18:29
amriththen you could point the guest agent to get them from some location, no?18:29
amrithgrapex, I wouldn't assume that18:29
*** jmontemayor has joined #openstack-trove18:29
kevinconwayso the way the BP is written now allows for amrith's solution as well as others18:29
robertmyersthen the guest still has to download it18:29
robertmyersand see it18:29
amrithin the future, I'd assume that all trove infors the guest is that "go forth and configure SSL"18:29
amrithand let the guest do it directly18:29
grapexamrith: I think you trust the guest agent too much18:29
amrithgrapex, in an SSL implementation, you have to trust the end point that has the database.18:30
grapexbecause in the end its a piece of Trove infrastructure running on the server18:30
amrithand we have to rely on the guest agent to get stuff there.18:30
amrithI don't believe that trove should get into the business of generating, or providing any ability to manage keys18:30
amrithnow, or in the future.18:30
denis_makogonamrith, +118:30
robertmyersamrith that is not in hte BP18:30
kevinconwayso amrith, in the BP it does not dictate how keys are created or managed18:30
kevinconwayit suggests an impl interface that a deployer can provide18:31
kevinconwayso if you want ssl links to the guest and a guest impl that downloads the keys you can have that18:31
amrithbut it does indicate that the interface would convey the PKI+cert18:31
kevinconwayif i as another deployer want something else i can do that as well18:31
*** tomblank has joined #openstack-trove18:31
*** sgotliv has joined #openstack-trove18:31
denis_makogoni'd rather keep proprietary key management out of codebase (unless it's bbq)18:31
amrithIMHO, the extent of the interace should be: prepare (enable_ssl=True)18:32
grapexWhen we say interface, are we talking about the guest agent RPC calls? Because if so that word may be too kind. :)18:32
kevinconwaydenis_makogon: it would be out of the trove trunk if a deployer did a custom impl18:32
amrithand it is up to the guest agent to go figure out how to get it.18:32
*** vigneshvar has quit IRC18:32
denis_makogonthat's may work18:32
*** rushiagr is now known as rushiagr_away18:32
kevinconwayamrith: that is still a possibility with the BP18:32
kevinconwayyes, it suggests the keys are tx'ed along the q18:33
kevinconwaybut that is a matter of impl18:33
amrithkevinconway, that may be true.18:33
amrithbut what I'd like is to have the discussion now, about the implementation18:33
amrithrather than have it with code in flight18:33
cp16netyou still need something outside of the prepare to fix older instances and in this case the mgmt call adds ssl18:33
amrithwe had some of the discussion of what the role and bounds of trove should be (at mid-cycle)18:33
kevinconwayso the trove impl could easily be a noop. i imagine deployers will all have different key management strategies18:33
amrithand to that point, I'd like to at least have the discussion now that frames the outlines of what the API changes would look like18:34
amrithand get agreement on that, in principle.18:34
grapexamrith: when you say API are you talking about the RPC calls?18:34
amrithgrapex, I'm talking about the interaction between the guestagent and the rest of trove.18:35
grapexOne thing I dislike about this notion that the guest agent has to become smart enough to do all of the key handling itself by default.18:35
amrithcurrently, for example, ssl_payload contains keys and certs.18:35
grapexWe already have it talking to Swift but in that case it was unavoidable18:36
amriththat's an API18:36
amrithand I think that part of the API is not Trove's responsibility18:36
kevinconwayamrith: so nothing in the BP should suggest that you _have_ to send the actual keys as payloads18:36
kevinconwaythat's why there is also an interface for the guest portion18:36
kevinconwaywhich consumes the ssl_payload and handles it18:36
amrithkevinconway, what I'm suggesting is that the BP should explicitly state that the keys will not be in part of the payload of the enable_ssl command18:37
amriththe enable_ssl command should only tell the guest ... go forth and enable SSL18:37
kevinconwayi think that's an unnecessary restriction on the impls18:37
grapexamrith: So basically, you're enforcing that no deployer of Trove may ever send the keys?18:37
grapexkevinconway: +118:37
amrithgrapex, I'm proposing that the open source product not get into that18:37
amrithif a deployer wishes to change Trove, so be it.18:38
grapexamrith: I think it's fair to say kevinconway and I disagree18:38
amriththat would be fair to say.18:39
grapexI think we can make it flexible enough to work both ways18:39
amrithI agree too.18:39
grapexI don't see the downside of that18:39
denis_makogoni've got one question18:39
amrithunfortunately, I do.18:39
kevinconwayso in your model amrith, trove would send a simple binary payload to the guest and the guest would perform all work related to ssl. is that correct?18:39
amrithkevinconway, i think that's correct.18:40
denis_makogonno matter how it is going to be implemented, it is really matter how would we test it?18:40
kevinconwayother than preventing a deployer from sending keys to the guest, what is the value added of that over the suggested BP?18:40
amrithkevinconway, it is a matter of what one thinks is the 'role' of trove.18:41
icchaif its the deployers decision whether to send the keys or not, then they know what they are getting into18:41
denis_makogonkevinconway, amriths way is much safer that sending keys over AMPQ18:41
amrithat the mid-cycle, we had conversations about whether or not we should have thresholds for what constituted a delay in replication18:41
vgnbkrIs the objective to merely support SSL connections to the database, or must the database support connecting with a pre-defined certificate?18:41
amrithand the decision was that trove should not decide what constitutes 'degraded'. let the deployer decide that18:41
icchai think kevinconway has made it clear that trove is not generating the keys18:41
amrithin the same way, the question is whether trove should generate and transmit keys.18:42
amrithI believe it should not18:42
amrithare keys required, yes they are.18:42
kevinconwaythen use the no-op ssl provider impl?18:42
amrithbut let them be obtained without trove getting into the mix.18:42
SlickNikI think we're all agreed in that trove shouldn't generate and manage these keys.18:42
amrithkevinconway, you are missing the point18:42
robertmyersSlickNik +118:42
amrithI'm suggesting that there shouldn't be an implementation in the open source product that has trove shipping keys18:42
SlickNikThe question is whether the trove API should be the medium through which these keys are transmitted.18:43
amrithwhat deployers want to do in their versions is their issue.18:43
denis_makogonamrith, +118:43
amrithrelate this to the conversation of triggering what constitutes a degraded situation wrt replication lag.18:43
amrithno one suggests that NO deployer should have such a notion18:43
kevinconwayamrith: so if the initial of the BP did not tx keys, would that satisfy your concern?18:43
grapexamrith: if there weren't dozens of things in Trove we at Rax had no use for I'd agree with this sentiment that Trove shouldn't have extra options you yourself might never use.18:43
amrithjust that the open source project should not.18:43
kevinconwayamrith: the initial impl that is18:44
amrithkevinconway, the implication is that a later implementation will?18:44
kevinconwayamrith: no, but a deployers impl could18:44
amrithsure18:44
amrithdeployers can have trove sing the national anthem, I don't mind.18:44
amriththat's their call.18:44
kevinconwaythere are singing robots, amrith18:45
kevinconwaysome quite popular18:45
SlickNikamrith: Do you agree that having SSL for datastore implementations that are deployed is a valid trove scenario?18:45
amrithkevinconway, and some deployers may have API calls to those too. (out of the scope of this BP)18:45
grapexamrith: What you haven't proven in my mind is how including this would be a detriment to Trove itself.18:45
amrithSlickNik, yes. I believe it is.18:46
amrithgrapex, that is likely true.18:46
grapexDeployers already have the right to do whatever they want. This is an apache license piece of open source software so I don't think we need to reiterate that.18:46
kevinconwayi'm simply suggesting an interface that allows for more than one possibility18:46
kevinconwayso the trove reference impl can _not_ send keys, but i don't believe we should prevent other impls that do18:47
amrithso, what does the rest of core think? what about others who were at mid-cycle? should we (in trove) handle keys? pass them around and so on?18:47
amrithi agree SSL is good18:47
amriththe question I have is whether we should be in the business of key transport.18:47
SlickNikSame here.18:47
SlickNikI agree that we should support this.18:47
SlickNikI'm not sure what the reference impl for getting the keys / cert out to the guest should be (quite yet)18:48
denis_makogoni'd suggest to delegate key management to guestagent, and do not involve AMPQ18:48
vgnbkrThere should be no need to transmit PRIVATE keys unless we wished to support pre-defined certs.  Transmitting public keys is fine.18:49
*** vigneshvar has joined #openstack-trove18:49
denis_makogonthis is a potential security issue, since we can't know if AMPQ service works with SSL/TLS18:49
denis_makogonvgnbkr, +118:49
SlickNikI don't think we're going to get closure on that during this meeting, so we'll probably need to discuss this OOB and perhaps again next week.18:50
amrithSlickNik, +118:50
SlickNikamrith / grapex / kevinconway: can we continue the discuss out of band?18:50
*** openstackgerrit has quit IRC18:51
amrithSlickNik, +118:51
SlickNikAnd let's move on to the next BP in the interest of time.18:51
SlickNik#topic ceilometer integration18:51
denis_makogonit's mine18:51
SlickNik#link https://blueprints.launchpad.net/trove/+spec/ceilometer-integration18:52
denis_makogonfor now we have only several notifications - when instance gets created, resized, and deleted18:52
denis_makogonall this notifications are emitted at the start18:52
denis_makogonfor billing purposes and resource monitoring (involving ceilomenter) we need to provide fine grained notification through resource life cycle18:53
denis_makogonthere are three types of resources: instance, backup and cluster(new one)18:54
denis_makogonthere are three levels of notifications: start, end, error18:55
denis_makogonsome of those notifications are emitted by taskmanager, some of them by conductor18:55
SlickNikdenis_makogon: So my concern is that we already have instance notifications — does it make sense to first work on a ceilometer plugin using these notifications (https://blueprints.launchpad.net/ceilometer/+spec/trove-plugin) before we go add notifications for all sorts of events in trove?18:56
denis_makogonSlickNik, i guess no, since it would be nice to have all notification once and for all18:56
denis_makogonSlickNik, it means that we need to build our own notifications first18:57
denis_makogonjust take a look at nova, it had its notifications even before ceilometer was proposed18:57
denis_makogonnotifications in Trove is the fine grained base for going forward with including ceilometer into monitoring workflow18:58
SlickNikI'm not sure that we'd even use these notifications for billing. Other folks (RAX, ebay) can chime in here, but at HP we bill backups based on Swift data, so something like backup create/delete would not be super useful to us. And clusters just made it in, so probably good to not get ahead of ourselves with this.18:59
SlickNikWhy can't we get a POC with the ceilometer plugin and just instances as a first step?19:00
grapexSlickNik: +119:00
denis_makogonwe might try19:00
robertmyersSlickNik +119:00
amrithis there someone who is looking for ceilometer integration in trove?19:00
cp16netwe use resize/create/delete for billing19:00
amriththat would could make part of this POC?19:00
denis_makogonamrith, i'm going to do that19:00
amrithdenis_makogon, not you. I mean someone operating trove in production who wants this feature19:01
*** grapex has quit IRC19:01
denis_makogonOk, as i can see, initial implementation would take only instance events and ceilo plugin19:01
*** grapex has joined #openstack-trove19:01
amrithcould we find out what events they want.19:01
amrithIf no one is going to deploy trove with this enabled, it seems like a futile effort.19:02
robertmyershow is this different then the current notifications?19:03
robertmyersdoes it extend it?19:03
robertmyersor replace it?19:03
denis_makogonamrith, Trove only emits notification - it doesn't know who's going to consume them19:03
denis_makogonrobertmyers, it'll extend it19:03
denis_makogonrobertmyers, for example, we have "instance.create"19:03
kevinconwaydenis_makogon: this does not involve any changes to existing messages, correct?19:03
robertmyersdenis_makogon ok19:04
denis_makogonkevinconway, it would modify topics19:04
denis_makogonkevinconway, for example "resize_volume" to "resize.volume.start|end|error"19:04
denis_makogonkevinconway, i mean resize_volume.start|end|error19:04
kevinconwaydenis_makogon: could you create new messages with those titles rather than modify existing?19:04
icchayeah we dont want breaking existing systems which depend on these notifications19:05
denis_makogonkevinconway, to keep working Rax billing system?19:05
SlickNikdenis_makogon: -1 to changing existing messages without a good reason.19:05
robertmyersdenis_makogon: so for example trove.instance.create.end == trove.instance.create19:05
denis_makogoniccha, kevinconway, i can do it19:05
*** openstackgerrit has joined #openstack-trove19:06
denis_makogonrobertmyers, SlickNik, kevinconway, iccha, what about sending several events at one stage ?19:06
*** openstackgerrit has quit IRC19:06
robertmyersthat is fine19:06
*** openstackgerrit has joined #openstack-trove19:06
robertmyersas long as the currnet is unchanged19:06
denis_makogonso it would keep everything working fine for all19:07
iccha+1 robertmyers19:07
denis_makogonrobertmyers, sure19:07
kevinconwayyeah, i wouldn't mind multiple so long as the originals are preserved19:07
denis_makogoncores, what do you think about multiple notifications ?19:07
SlickNikdenis_makogon: I'd really like to see more "integration with ceilometer" pieces, and fewer "get as many events as we can emitted by Trove" pieces as part of this BP.19:07
grapexdenis_makogon: I'm ok if you can also demonstrate some use19:08
grapexwhich I guess SlickNik just said. :)19:08
denis_makogongrapex, some use where ?19:08
iccha i could see some potential use if we use it for metrics like how long does it take to start and end a task19:09
icchabut no point unless someone actually uses it19:09
amrithiccha, +119:09
denis_makogonso, first i need to implement ceilo part, right ?19:09
denis_makogonif that works for all - fine, i'm cool with that19:09
SlickNikdenis_makogon: Yes, that would be good.19:10
denis_makogonok19:10
SlickNikOkay we're already running over.19:10
icchaya way over :)19:10
denis_makogoncan we review the last one ?19:10
openstackgerritDan Nguyen proposed a change to openstack/python-troveclient: Add mgmt upgrade call to CLI  https://review.openstack.org/10879619:10
denis_makogoncassandra clusters19:10
SlickNikdenis_makogon: will have to move to next week.19:10
SlickNik#endmeeting19:11
denis_makogonbad =(19:11
openstackMeeting ended Mon Sep  8 19:11:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-09-08-18.02.html19:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-09-08-18.02.txt19:11
openstackLog:            http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-09-08-18.02.log.html19:11
amriththx SlickNik19:11
SlickNikThanks folks!19:11
denis_makogonthanks to all19:11
SlickNikAnd sorry for the slight delay.19:11
grapexdenis_makogon: Sorry for the delay- iccha gave a good example of what I meant. :)19:11
icchavgnbkr: around?19:12
SlickNikgrapex / amrith / kevinconway: Perhaps we can use part of the Wednesday Trove meeting to discuss the SSL issue that came up today? I think that that's something that's important for Trove, so it would be good to get some closure on it.19:14
openstackgerritMat Lowery proposed a change to openstack/trove-integration: Load cfg params conditionally  https://review.openstack.org/11988019:15
zhiyanSlickNik: hi, btw, may I know do we have more meetings for bp discussion in a week? I was going to edit agenda for next Monday.19:16
SlickNikzhiyan: Sorry we weren't able to get to your BP because of a full agenda. Yes, your item will be moved to the beginning of next week's agenda19:17
SlickNikI will move it.19:18
vgnbkriccha: hi19:18
icchavgnbkr: i just wanted to make sure u noticed the comments i had earlier before meeting about replication for 5.6 and config values associated with it19:19
zhiyanSlickNik: great, thanks. np :) (just only my timezone is a little issue, needs schedule.)19:19
*** iartarisi has quit IRC19:20
icchazhiyan: make sure u add it for next monday now, so ur item is top of agenda19:20
zhiyaniccha: ^^ SlickNik said he will do it.19:21
icchaok awesome zhiyan :)19:21
*** jmontemayor has quit IRC19:22
vgnbkriccha: No I haven't seen them.  IRC or a gerrit review?19:26
*** Barker has quit IRC19:26
icchairc19:26
icchavgnbkr: ^19:27
vgnbkriccha: Sorry, my logging got turned off somehow, and our bouncer doesn't seem to go that far back.  Can you cut the relevant parts and PM/email it to me?19:29
icchasure vgnbkr basically for 5.6 need additional configs for repl to turn on gtids19:30
icchavgnbkr: right now we hard code it, wanted to move out replication configs to maybe the template or configs19:30
vgnbkrI seem to recall that there was more to it than that which was why I made a Replication Strategy, but not having it hard coded as it is would be good regardless.19:31
*** jmontemayor has joined #openstack-trove19:34
vgnbkrWere you thinking of a template selected via CONF?19:34
kevinconwaySlickNik: I wouldn't mind continuing the conversation. We may need to pre-game a bit to make sure we're on the same page for what we are talking about.19:35
amrithkevinconway, grapex, SlickNik ... re: ssl, here's a proposal.19:39
amrith<paste bomb> follows19:39
amrithlet us make it possible to get ssl enabled in multiple ways, and leave ssl disabled (by default).19:39
amrithIf you enable ssl, the keypair and the certificate must get to the guest. let's make it possible to accomplish that in one of many ways.19:39
amrith(a) the guest generates the keypair and the ssl_enable payload is just the certificate19:39
amrith(b) the guest agent gets a URI (or a collection) and gets the things it needs19:39
amrith(c) trove sends the stuff over the message bus as part of the payload of ssl_enable19:39
amrithWe can document clearly that the third one depends on your security on the message bus, and (a) would pass security audits. This would give deployers flexibility to use the method(s) they chose, and trove can support SSL.19:39
amrithThoughts?19:39
amrith</paste bomb>19:39
*** amcrn has joined #openstack-trove19:40
amrithI believe this will address vgnbkr's concern of tranfering keys in the open19:40
amrithespecially private key19:40
amrithit will address my concern of trove getting into the business of key management19:40
amrithand it will make it possible to integrate with bbq in the future.19:40
amriththoughts?19:40
amrithvgnbkr, thoughts (re: above)19:41
SlickNikamrith: etherpad / paste / gist please :)19:41
SlickNikhttps://etherpad.openstack.org/p/TroveSSL19:41
icchavgnbkr: like we have templates we select the replication.cnf from template too? so the reason i was thinking we dont need another strategy is because all the workflow is eaxctly the same. the only thing different is config value19:42
amrithSlickNik, thanks.19:42
SlickNikamrith / kevinconway: That proposal seems amenable to me. Just need to ensure that the API proposed allows for all 3 (a-c).19:44
grapexamrith SlickNik: +119:44
grapexamrith: We may want to see who would use options A and B just to make sure they will have some users.19:45
kevinconwaySlickNik: amrith: grapex: would it help if i mocked what those scenarios would look like as a part of the BP?19:46
grapexI know we're done for C of course. And I like that the default option is nothing, which means someone picking up stock Trove wouldn't use an option and think they had security when they didn't.19:46
kevinconwaymocked up, rather. not intending to fun of19:46
amrithgrapex, SlickNik +119:46
openstackgerritAuston McReynolds proposed a change to openstack/trove: Miscellaneous Cluster Fixes  https://review.openstack.org/11925919:46
SlickNikkevinconway: Yes, I think that a couple of examples would help. Thanks!19:48
*** vigneshvar has left #openstack-trove19:51
vgnbkramrith: Yes, though should point out that the certificate in case (a) is the cert of the CA, not the cert that the user will use to authenticate the server.19:54
vgnbkriccha: Yes, if everything the same, no need for separate strategy - I can't remember what is was that I though was going to be different - it may have been for more advanced use cases that we haven't addressed yet.19:56
*** sgotliv has quit IRC19:57
*** sgotliv has joined #openstack-trove19:58
vgnbkramrith: SlickNik: The part I don't understand for case a/b is what happens to the generated certificate.  It seems we would need somewhere to register it as is already done for keys.  The user would need to be able to retrieve the cert beyond the return value of the enable call, I think.19:58
jedixhmm.. trove-integration does not have a license file.19:59
jedixah, http://www.apache.org/licenses/LICENSE-2.020:00
openstackgerritNikhil Manchanda proposed a change to openstack/python-troveclient: Update the README.rst with latest help  https://review.openstack.org/11989820:07
SlickNikCan I get some reviews on https://review.openstack.org/119898? I'm planning to push a new trove client release to pypi, and would like the README.rst that gets published to pypi to reflect the correct help info.20:10
SlickNikThanks!20:10
icchataking a look...20:11
*** amrith is now known as _amrith_20:13
icchaSlickNik: does it need a bug associated with it?20:15
*** spiffxp_ has quit IRC20:15
jedixare there any built-in tests for trove, or do I need use trove-integration for testing?20:15
*** spiffxp_ has joined #openstack-trove20:16
icchajedix: there are some unit tests and int tests in trove20:16
*** stevelle has quit IRC20:17
jedixiccha: thanks, can you point me towards documentation on those?20:18
*** stevelle has joined #openstack-trove20:18
icchajedix: u can run tox or you the run_tests.py20:19
*** hub_cap has quit IRC20:21
*** hub_cap has joined #openstack-trove20:21
*** achampion has quit IRC20:32
*** sbadia has quit IRC20:32
*** sbadia has joined #openstack-trove20:34
SlickNikiccha: It's just a doc change, so I didn't bother opening a bug. Although it's probably a good idea to open one for it anyway.20:37
jedixrun_tests.py is in the integration git repo, isn't it?20:40
*** miqui has quit IRC20:43
amcrnSlickNik: if you fix the small nit mentioned in that doc change, i'll +2 before i run to a meeting.20:54
*** eguz has joined #openstack-trove20:56
openstackgerritNikhil Manchanda proposed a change to openstack/python-troveclient: Update the README.rst with latest help  https://review.openstack.org/11989820:58
amcrnSlickNik: thanks, +2'd20:59
*** eghobo has quit IRC20:59
SlickNik^^ amcrn / iccha: here you go.20:59
SlickNikThanks!20:59
icchathanks SlickNik20:59
*** amcrn has quit IRC21:05
*** arborism has joined #openstack-trove21:10
*** arborism is now known as amcrn21:11
*** juantwo has quit IRC21:11
*** sriram_tesora has quit IRC21:11
openstackgerritRiddhi Shah proposed a change to openstack/trove: Associate flavor types with datastore versions  https://review.openstack.org/10982421:15
*** IanGovett2 has joined #openstack-trove21:20
*** IanGovett1 has quit IRC21:20
Riddhiamcrn: ^^; can you review it and remove the -2 if it looks okay??21:21
amcrnRiddhi: the breaking change was removed, so i've gone ahead and wiped the -2.21:23
amcrnRiddhi: that should at least not discourage people from looking at it; once time permits, i'll look at it again to assess the final vote.21:24
*** IanGovett has joined #openstack-trove21:24
*** robertmyers has quit IRC21:25
*** IanGovett has quit IRC21:27
*** IanGovett2 has quit IRC21:27
*** IanGovett has joined #openstack-trove21:27
Riddhisure,thanks amcrn21:28
*** ViswaV has quit IRC21:32
*** flaper87 is now known as flaper87|afk21:38
*** IanGovett has quit IRC21:43
*** edmund has quit IRC21:44
*** IanGovett has joined #openstack-trove21:45
openstackgerritSergey Gotliv proposed a change to openstack/trove: [WIP] Updates RPC API to use oslo.messaging  https://review.openstack.org/9448421:47
*** ViswaV has joined #openstack-trove21:47
openstackgerritRiddhi Shah proposed a change to openstack/trove: Allow users the ability to update an instance name  https://review.openstack.org/9270121:51
*** sgotliv has quit IRC21:52
*** eguz has quit IRC21:54
*** eghobo has joined #openstack-trove21:54
*** jasonb365 has quit IRC21:57
*** tomblank has quit IRC21:57
*** juantwo has joined #openstack-trove22:01
openstackgerritRiddhi Shah proposed a change to openstack/trove: Add visibility filter to datastore versions  https://review.openstack.org/11019722:13
*** miqui has joined #openstack-trove22:13
*** amcrn_ has joined #openstack-trove22:30
*** amcrn has quit IRC22:32
*** mattgriffin has quit IRC22:59
openstackgerritA change was merged to openstack/trove-integration: Add new command to run dsvm-gate-tests  https://review.openstack.org/11827323:00
*** amcrn_ is now known as amcrn23:01
*** tomblank has joined #openstack-trove23:02
*** rhodgin has quit IRC23:11
*** Longgeek has quit IRC23:14
*** IanGovett has quit IRC23:28
*** IanGovett has joined #openstack-trove23:28
*** IanGovett has quit IRC23:33
*** georgelorch has quit IRC23:34
*** edmund has joined #openstack-trove23:35
*** georgelorch has joined #openstack-trove23:35
*** kevinconway has quit IRC23:37
*** _amrith_ is now known as amrith23:38
*** IanGovett has joined #openstack-trove23:43
*** Riddhi has quit IRC23:47
*** jmontemayor has quit IRC23:48
*** IanGovett has quit IRC23:50
johnmaHello, do we have any documentation around the clustering feature that will be available in the Juno release? I am trying to understand what kind of of replication is supported in this release. Thank you.23:54
*** mattgriffin has joined #openstack-trove23:58

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