Thursday, 2015-12-03

openstackgerritMerged openstack/trove: Add better input checking for MongoDB  https://review.openstack.org/24774400:06
*** shakamunyi has joined #openstack-trove00:09
*** chlong has quit IRC00:12
openstackgerritDoug Shelley proposed openstack/trove-specs: Datastore Log Operations  https://review.openstack.org/18816800:18
dougshelley66cp16net ^^^ I added that appendix section to the bottom as per your comment...will need +2 put back on00:20
openstackgerritMayuri Ganguly proposed openstack/trove: Update Management Console user and password  https://review.openstack.org/20867000:27
openstackgerritMayuri Ganguly proposed openstack/trove: Modifying Vertica clusters to have a master node  https://review.openstack.org/20427100:27
*** rcernin has quit IRC00:37
openstackgerritMerged openstack/trove-specs: Postgresql streaming replication  https://review.openstack.org/24098600:40
openstackgerritMerged openstack/trove-specs: Removing SQL Schema Downgrade  https://review.openstack.org/25247700:41
openstackgerritMerged openstack/trove-specs: Add Backup & Restore feature for CouchDB database  https://review.openstack.org/24661600:43
*** mingdang1 has joined #openstack-trove00:50
*** mingdang1 has quit IRC00:50
*** mingdang1 has joined #openstack-trove00:50
openstackgerritRico Lin proposed openstack/python-troveclient: Remove py26 support  https://review.openstack.org/25247000:52
*** amrith is now known as _amrith_00:57
*** shakamunyi has quit IRC01:02
*** shakamunyi has joined #openstack-trove01:03
*** sabeen has quit IRC01:07
*** csoukup has joined #openstack-trove01:18
*** sgotliv__ has quit IRC01:22
*** mingdang1 has quit IRC01:39
*** chlong has joined #openstack-trove01:48
*** chlong has quit IRC01:51
*** chlong has joined #openstack-trove02:00
*** chlong has quit IRC02:06
*** imandhan has quit IRC02:17
*** chlong has joined #openstack-trove02:19
*** pmackinn has quit IRC02:29
openstackgerritMerged openstack/trove: updating with other reno changes  https://review.openstack.org/25256002:30
*** chlong has quit IRC02:35
*** mingdang1 has joined #openstack-trove02:40
cp16net_amrith_: vkmc thanks!02:41
cp16neti think we are capable of doing the release now02:41
vkmcsupaaaah02:41
cp16netoh damn spoke to soon...02:43
cp16netgoing to have something else i need to do as well...02:43
*** mingdang1 has quit IRC02:45
cp16netgot a few other things to do before the release is ready...02:47
*** chlong has joined #openstack-trove02:48
*** pmackinn has joined #openstack-trove02:56
openstackgerritCraig Vyvial proposed openstack/trove: Remove version per M-1 release instructions  https://review.openstack.org/25272202:57
cp16netalright now i think we are good.02:59
cp16netvkmc: ^^ that patch will need to land after they cut the release tomorrow03:00
vkmccp16net, roger roger03:00
*** chlong has quit IRC03:21
*** ViswaV_ has quit IRC03:35
*** ViswaV has joined #openstack-trove03:37
*** sabeen1 has joined #openstack-trove03:40
*** sabeen2 has joined #openstack-trove03:43
*** sabeen1 has quit IRC03:46
*** links has joined #openstack-trove05:06
*** ianbrown has joined #openstack-trove05:14
*** haomaiwang has joined #openstack-trove05:16
*** ianbrown has quit IRC05:21
*** csoukup has quit IRC05:46
*** pmackinn has quit IRC05:57
*** imandhan has joined #openstack-trove06:15
*** imandhan has quit IRC06:22
*** imandhan has joined #openstack-trove06:27
*** sabeen2 has quit IRC06:27
*** imandhan has quit IRC06:29
*** imandhan has joined #openstack-trove06:29
*** imandhan has quit IRC06:33
*** mingdang1 has joined #openstack-trove06:36
*** imandhan has joined #openstack-trove06:36
*** ViswaV has quit IRC06:52
*** imandhan has quit IRC07:04
*** sgotliv__ has joined #openstack-trove07:16
*** rcernin has joined #openstack-trove07:19
*** rcernin_ has joined #openstack-trove07:24
*** imandhan has joined #openstack-trove07:31
*** vkmc has quit IRC07:43
*** vkmc has joined #openstack-trove07:44
*** chlong has joined #openstack-trove07:55
*** imandhan has quit IRC08:27
*** chlong has quit IRC08:29
*** rcernin has quit IRC08:50
*** rcernin_ has quit IRC08:51
*** rcernin has joined #openstack-trove09:59
*** haomaiwang has quit IRC10:38
*** tosky has joined #openstack-trove10:50
*** chlong has joined #openstack-trove11:01
*** pmalik_ is now known as pmalik12:18
pmalik_amrith_: cp16net: edmondk: SlickNik: vkmc: The test race condition fix is now passing the gate. Can we possibly push it through please? Thanks. :-) https://review.openstack.org/#/c/248421/12:26
*** openstackgerrit has quit IRC12:32
*** openstackgerrit has joined #openstack-trove12:32
*** haomaiwa_ has joined #openstack-trove12:43
*** vkmc has quit IRC12:50
*** vkmc has joined #openstack-trove12:50
*** pmackinn has joined #openstack-trove12:52
*** openstackgerrit has quit IRC13:17
*** openstackgerrit has joined #openstack-trove13:17
*** haomaiwa_ has quit IRC13:40
*** links has quit IRC13:51
*** _crobertsrh is now known as crobertsrh14:04
*** csoukup has joined #openstack-trove14:09
*** mingdang1 has quit IRC14:20
*** _amrith_ is now known as amrith15:21
cp16netM-1 of trove is released15:43
*** amrith is now known as _amrith_15:46
*** haomaiwa_ has joined #openstack-trove15:52
cp16netedmondk: vkmc: https://review.openstack.org/#/c/245356/16:00
*** haomaiwa_ has quit IRC16:00
*** 18VAAEQWZ has joined #openstack-trove16:01
*** 18VAAEQWZ has quit IRC16:02
openstackgerritMerged openstack/trove-specs: Datastore Log Operations  https://review.openstack.org/18816816:02
*** haomaiwa_ has joined #openstack-trove16:02
*** haomaiwa_ has quit IRC16:03
*** haomaiwa_ has joined #openstack-trove16:03
*** haomaiwa_ has quit IRC16:04
*** haomaiwang has joined #openstack-trove16:04
*** haomaiwang has quit IRC16:05
*** haomaiwa_ has joined #openstack-trove16:05
*** haomaiwa_ has quit IRC16:06
*** haomaiwang has joined #openstack-trove16:06
*** haomaiwang has quit IRC16:07
*** haomaiwang has joined #openstack-trove16:07
*** haomaiwang has quit IRC16:08
*** haomaiwa_ has joined #openstack-trove16:08
*** haomaiwa_ has quit IRC16:09
*** haomaiwa_ has joined #openstack-trove16:09
*** haomaiwa_ has quit IRC16:10
*** 5EXAADMHT has joined #openstack-trove16:10
*** 5EXAADMHT has quit IRC16:11
*** haomaiwang has joined #openstack-trove16:11
*** haomaiwang has quit IRC16:12
*** 5EXAADMKT has joined #openstack-trove16:12
*** rcernin has quit IRC16:12
*** 5EXAADMKT has quit IRC16:13
*** 5EXAADML5 has joined #openstack-trove16:13
*** 5EXAADML5 has quit IRC16:13
*** sabeen has joined #openstack-trove16:20
*** sabeen has quit IRC16:49
*** rcernin has joined #openstack-trove16:53
*** tosky has quit IRC16:57
*** tosky has joined #openstack-trove16:59
cp16netwhos around?17:06
vkmcme17:07
vkmco/17:07
peterstaco/17:24
cp16netvkmc: peterstac i think we need to determine what datastores are "stable"17:25
cp16netwe have experimental17:25
cp16netwe need to determine a path between experimental and stable datastores17:26
peterstacwell, one of the conditions was to have CI running on the DS (whether OS or 3rd-party)17:26
peterstacwe've got most of the infrastructure to start running the scenario tests in the gate17:26
peterstacbut we need the capacity (internal or from outside)17:26
cp16netyeah i think thats part of it17:27
cp16neti think there are some other conditions as well17:27
vkmcAPI coverage is something we may want to consider as well17:27
cp16neti'll write up a page on some conditions i cann think of and then i think its something that we should discuss17:28
SlickNikWhat's up folks!17:29
cp16netbecause should the fact that there are operators deployed a datastore in prod be given some weight?17:29
cp16neti.e. mongo and redis have been run for a while by multiple people17:30
cp16netthe datastores need to have a minimal feature set17:31
vgnbkrDoes anyone have mongo or redis in use by customers based on standand Trove code (i.e., no downstream additions).17:32
peterstacbut we as a community declare something 'stable' I think we'd need to have tests running on a continual basis17:33
peterstacs/but we/but if we/17:33
cp16netpeterstac: i'd agree with that as well as a condition for it17:34
cp16netvgnbkr: thats a loaded question17:34
dougshelley66cp16net as i recall, the original discussion of why we did this was because the only datastore being routinely tested was mysql17:34
dougshelley66I think the key item was CI testing for other datastores17:34
cp16netyeah i think thats true17:35
cp16netthen with a good definition of what we determine stable/experimental leads to me next question17:35
dougshelley66...17:37
cp16netif we find issues with a datastore that are security related for stable do we make a sercurity patch for them or not. (i'd think we would)17:38
cp16netthen what about experimental?17:38
cp16netmaybe we wouldnt17:38
dougshelley66it's a good question that wasn't previously discussed in the experimental context17:41
dougshelley66i don't think there is any reason we wouldn't provide stable patches for experimental17:42
cp16netright its something that we need to figure out17:43
cp16netwhat makes the most sense17:43
cp16netdougshelley66: your 2nd comment doesnt really make sense in the context i was thinking17:44
cp16netstable patches for experimental?17:44
toskyif there is an official CVE, I don't think it would even been an option to not backport a security patch17:44
cp16nettosky: right that makes sense17:45
cp16netso if there is a found security issue in a stable datastore we should address it with a CVE and backport and all17:47
cp16neti think thats less controversial than the experimental in my mind17:47
cp16netif experimental datastore issue is found then we should or shouldnt create a CVE for it?17:49
cp16neti think from the dictionary definition of experimental it makes sense that we shouldnt create a CVE17:50
toskyI think anyone could file a CVE for it (any vendor), it's shipped code17:50
cp16netfrom a vender pov i think that makes sense17:51
cp16netbut if Trove's definition of experimental is a bit wider then it would mean that its a grey area if we should make a public bug fix or not17:54
toskymhh... it's still shipped code17:56
cp16nettosky: from your pov everything that has been versioned matters17:58
*** imandhan has joined #openstack-trove17:58
toskyfor security bugs, yes17:58
cp16netmakes sense17:58
tosky(sorry, I have to leave)17:58
*** tosky has quit IRC17:58
cp16nettosky: no worries thanks for your input17:58
cp16netdougshelley66: peterstac vkmc since you were here what do you think?17:59
cp16netvgnbkr: ?17:59
vgnbkrcp16net, sorry, was on phone - reading now...18:00
cp16netno worries the last thing tosky said is what i'm asking about18:00
*** PeterSchwaller has joined #openstack-trove18:02
peterstacJust because a datastore is considered experimental, we should probably still fix any CVE issues18:02
peterstacWe could state that the timeframe for fixes for experimental datastores may be longer18:03
vgnbkrI'm having trouble imagining what a security patch would be to an experimental database that would require a datastore-specific patch to fix.  If it's a database bug, it's beyond Trove's control.  If it's a framework issue, it would affect all datastores.  What sort of security issue are we talking about?18:04
cp16netnot nessesrary18:07
cp16neter...18:07
cp16netnot nessesarily vgnbkr because each datastore implements its own logic to handle the operations the datastore handles18:08
vgnbkrcp16net, I think there could be an issue with images for experimental datastores, but that would be up to the image creator to deal with.  What sort of issue would the trove code itself have?18:09
vgnbkrMaybe there could be an API call that is deprecated for security reasons, but that's a pretty rare occurrence, I think.  I don't know that we need to implement a priori procedure for such rare events.18:10
cp16netvgnbkr: i'm talking about bugs that may affect a datastore that are found after release18:10
cp16netbugs found in code thats not tested in ci18:11
vgnbkrRight, but give me an example of a security issue that would be fixed by a change to trove code.  I get that we can discuss theoretical issues, but if we can't think of specific ones it's probably not worth worrying about.18:13
*** tqtran has joined #openstack-trove18:13
vgnbkri.e., as opposed to the many other real issues we could be discussing :-)18:13
cp16neti think its a valid concern that could happen at any time18:16
vkmcI think it's a valid concern too18:24
vkmcif there is a security concern related on how we interact with a datastore, then it's something we should take care of18:24
vkmcif it's a bug in the datastore, then the vendor should take care of it and we should upgrade as needed18:25
*** davideagnello has quit IRC18:26
*** davideagnello has joined #openstack-trove18:26
cp16netyeah i'd tend to agree18:27
cp16neti think we need to discuss this with others as well and get the conclusion documented so that we have a reference for the future18:29
vkmc+118:35
*** ViswaV has joined #openstack-trove18:42
*** sabeen has joined #openstack-trove19:03
*** _amrith_ is now known as amrith19:24
cp16neti'll be afk for the next few hours i'll catch up later19:27
amrithcp16net, vkmc, peterstac, vgnbkr, dougshelley66 ... I'm going to be in and out the rest of the day, returning home tonight. I'm trying to follow what's going on from the scrollback but I'm missing something. Is there a specific CVE against an experimental datastore or are we having an argument about the scenario should it arise?19:30
peterstacamrith, AFAIK the discussion is about a hypothetical (although plausible) scenario19:32
*** ViswaV has quit IRC19:41
amrithok, thanks.19:47
*** davideagnello has quit IRC19:50
*** davideagnello has joined #openstack-trove19:50
openstackgerritMerged openstack/trove-integration: Add Python-cli and init run dir to PG elements  https://review.openstack.org/24783619:51
*** chlong has quit IRC19:57
*** chlong has joined #openstack-trove20:16
*** amrith is now known as _amrith_20:20
*** openstackgerrit has quit IRC20:47
*** openstackgerrit has joined #openstack-trove20:47
*** rcernin has quit IRC21:05
*** sabeen has quit IRC21:12
*** sabeen1 has joined #openstack-trove21:19
*** crobertsrh is now known as _crobertsrh22:02
openstackgerritPetr Malik proposed openstack/python-troveclient: Add 'volume_type' parameter to instance create  https://review.openstack.org/24597022:03
peterstaccp16net, I'm good with the changeset ^^^^22:06
peterstac(just the help updated)22:06
peterstacIf you can take a quick look, once you get a chance22:06
peterstacThx!22:06
*** ViswaV has joined #openstack-trove22:30
*** arist has quit IRC22:47
*** arist has joined #openstack-trove22:47
*** chlong has quit IRC23:08
*** sabeen1 has quit IRC23:22
*** csoukup has quit IRC23:25
*** ViswaV has quit IRC23:32

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