Thursday, 2016-12-01

*** absubram has joined #openstack-manila00:04
*** cknight has joined #openstack-manila00:37
*** zengyingzhe__ has quit IRC01:03
*** catintheroof has joined #openstack-manila01:05
*** catintheroof has quit IRC01:08
*** mtanino has quit IRC01:10
*** zhonghua_ has joined #openstack-manila01:30
*** miriam_ has joined #openstack-manila01:34
*** kaisers1 has joined #openstack-manila01:34
*** kaisers has quit IRC01:35
*** tommylikehu_ has joined #openstack-manila01:37
tommylikehu_ping bswartz01:45
tommylikehu_hey I am here01:46
*** cknight has quit IRC01:50
*** xyang_ has joined #openstack-manila01:50
*** xyang_ has quit IRC01:52
*** kaisers has joined #openstack-manila02:06
*** kaisers_ has quit IRC02:09
*** catintheroof has joined #openstack-manila02:24
*** gcb has joined #openstack-manila02:34
*** zengyingzhe has joined #openstack-manila03:07
*** absubram has quit IRC03:21
*** zhonghua_ has quit IRC03:24
*** catintheroof has quit IRC03:28
*** catintheroof has joined #openstack-manila03:28
*** catintheroof has quit IRC03:28
*** catintheroof has joined #openstack-manila03:30
*** catintheroof has quit IRC03:30
*** catintheroof has joined #openstack-manila03:31
*** catintheroof has quit IRC03:31
openstackgerritCedric Zhuang proposed openstack/manila: Add "update_access" interface support for VNX.  https://review.openstack.org/39540403:39
*** tommylikehu_ has quit IRC03:52
*** tommylikehu_ has joined #openstack-manila03:53
*** tommylikehu_ has quit IRC04:01
*** tommylikehu_ has joined #openstack-manila04:01
*** tommylikehu_ has quit IRC04:01
*** tommylikehu_ has joined #openstack-manila04:02
*** tommylikehu_ has quit IRC04:02
*** tommylikehu_ has joined #openstack-manila04:02
*** tommylikehu_ has quit IRC04:03
*** tommylikehu_ has joined #openstack-manila04:03
*** tommylikehu_ has quit IRC04:04
*** tommylikehu_ has joined #openstack-manila04:04
*** tommylikehu_ has quit IRC04:05
*** tommylikehu_ has joined #openstack-manila04:05
*** tommylikehu_ has quit IRC04:05
*** tuanluong has joined #openstack-manila04:06
openstackgerritCao Xuan Hoang proposed openstack/manila-ui: Changed the home-page link  https://review.openstack.org/40509804:20
*** absubram has joined #openstack-manila04:21
*** absubram_ has joined #openstack-manila04:25
*** absubram has quit IRC04:26
*** absubram_ is now known as absubram04:26
*** tommylikehu_ has joined #openstack-manila04:33
*** tommylikehu_ has quit IRC04:37
*** kaisers has quit IRC05:07
*** lpetrut has joined #openstack-manila05:30
*** gouthamr has joined #openstack-manila05:33
*** shausy has joined #openstack-manila05:37
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Fix wrong data type in database migration  https://review.openstack.org/40031005:42
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Add create_share_from_snapshot_support extra spec  https://review.openstack.org/35668205:44
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Fix wrong data type in database migration  https://review.openstack.org/40031005:44
*** tommylikehu_ has joined #openstack-manila05:46
*** sandanar has joined #openstack-manila05:49
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Add create_share_from_snapshot_support extra spec  https://review.openstack.org/35668205:52
*** lpetrut has quit IRC06:02
*** kaisers has joined #openstack-manila06:07
*** lpetrut has joined #openstack-manila06:10
*** kaisers has quit IRC06:16
*** lpetrut has quit IRC06:17
openstackgerritzhongjun proposed openstack/manila: Add share_type filter support to pool_list  https://review.openstack.org/36561706:32
openstackgerritPony Chou proposed openstack/manila: Add QNAP Manila Driver  https://review.openstack.org/39470306:37
*** senk has joined #openstack-manila06:39
*** nkrinner_afk is now known as nkrinner06:45
*** tuanluong_ has joined #openstack-manila07:08
*** tuanluong has quit IRC07:11
*** kaisers has joined #openstack-manila07:12
*** kaisers has quit IRC07:20
*** jprovazn has joined #openstack-manila07:25
*** mkoderer has joined #openstack-manila07:35
*** zhonghua2 has joined #openstack-manila07:55
*** zhonghua has quit IRC07:55
*** tuanluong has joined #openstack-manila08:08
*** tuanluong_ has quit IRC08:10
openstackgerritzhongjun proposed openstack/manila: Add share_type filter support to pool_list  https://review.openstack.org/36561708:11
*** kaisers has joined #openstack-manila08:17
*** xiaoyang has joined #openstack-manila08:21
*** ianychoi has quit IRC08:24
*** kaisers has quit IRC08:25
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 11  https://review.openstack.org/40496108:45
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 11  https://review.openstack.org/40496108:46
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 12  https://review.openstack.org/40496308:47
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 13  https://review.openstack.org/40496408:48
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 14  https://review.openstack.org/40518808:49
*** sapcc-bot has quit IRC08:58
*** carthaca_ has quit IRC08:58
*** sapcc-bot has joined #openstack-manila08:58
*** carthaca_ has joined #openstack-manila08:58
*** tommy_ has joined #openstack-manila08:58
*** databus23_ has joined #openstack-manila08:58
*** mkoderer_ has joined #openstack-manila08:58
*** dgonzalez_ has joined #openstack-manila08:58
*** david_1 has joined #openstack-manila08:58
*** tommy_ is now known as Guest7722308:59
*** Guest77223 has quit IRC09:00
*** databus23_ has quit IRC09:00
*** carthaca_ has quit IRC09:00
*** mkoderer_ has quit IRC09:00
*** dgonzalez_ has quit IRC09:00
*** david_1 has quit IRC09:00
*** akapil has joined #openstack-manila09:03
openstackgerritzhongjun proposed openstack/manila: Add share_type filter support to pool_list  https://review.openstack.org/36561709:05
openstackgerritzhongshengping proposed openstack/puppet-manila: Fix spec test for sync  https://review.openstack.org/40520409:13
*** kaisers has joined #openstack-manila09:22
*** kaisers has quit IRC09:29
*** rraja has joined #openstack-manila09:30
*** a-pugachev has joined #openstack-manila09:34
*** digvijay2016 has joined #openstack-manila09:34
*** tommylikehu_ has quit IRC09:38
*** tommylikehu_ has joined #openstack-manila09:38
*** tommylikehu_ has quit IRC09:38
*** tommylikehu_ has joined #openstack-manila09:39
*** tommylikehu_ has quit IRC09:43
*** ganso has joined #openstack-manila09:55
*** openstack has joined #openstack-manila10:05
openstackgerritArne Wiebalck proposed openstack/manila-ui: Add access key column to rules table  https://review.openstack.org/39371510:07
*** miriam_ has quit IRC10:08
openstackgerritGoutham Pacha Ravi proposed openstack/manila-specs: Add a spec to fix and improve Access Rules  https://review.openstack.org/39904910:12
*** alyson_ has joined #openstack-manila10:17
*** tpsilva has joined #openstack-manila10:20
*** ianychoi has joined #openstack-manila10:22
*** akapil has quit IRC10:25
*** kaisers has joined #openstack-manila10:26
*** akapil has joined #openstack-manila10:27
*** kaisers has quit IRC10:33
*** a-pugachev_ has joined #openstack-manila10:36
*** akapil has quit IRC10:36
*** akapil has joined #openstack-manila10:37
*** a-pugachev has quit IRC10:39
*** bswartz has quit IRC10:39
*** rhagarty_ has quit IRC10:39
*** _laco has quit IRC10:39
*** a-pugachev_ is now known as a-pugachev10:39
*** miriam_ has joined #openstack-manila10:42
*** bswartz has joined #openstack-manila10:43
*** rhagarty_ has joined #openstack-manila10:43
*** miriam_ is now known as yumiriam10:44
*** _laco has joined #openstack-manila10:47
*** akapil has quit IRC10:56
*** akapil has joined #openstack-manila11:04
*** akapil has quit IRC11:10
*** kaisers has joined #openstack-manila11:31
*** gouthamr has quit IRC11:35
*** kaisers has quit IRC11:37
openstackgerritDigvijay Ukirde proposed openstack/manila: Add support for manage/unmanage in GPFS driver  https://review.openstack.org/37470511:58
*** porrua has joined #openstack-manila12:06
*** tommylikehu_ has joined #openstack-manila12:22
*** digvijay2016 has quit IRC12:23
*** lseki has joined #openstack-manila12:23
*** dsariel has quit IRC12:24
*** catintheroof has joined #openstack-manila12:25
*** kaisers has joined #openstack-manila12:35
*** kaisers has quit IRC12:43
*** catintheroof has quit IRC12:48
*** adrianofr_ has joined #openstack-manila12:54
*** tommylikehu_ has quit IRC12:56
*** akapil has joined #openstack-manila12:58
*** catintheroof has joined #openstack-manila13:13
*** dsariel has joined #openstack-manila13:14
*** catinthe_ has joined #openstack-manila13:18
*** catintheroof has quit IRC13:19
*** markstur has quit IRC13:23
*** markstur has joined #openstack-manila13:26
*** tuanluong has quit IRC13:29
*** nherciu has joined #openstack-manila13:31
*** jprovazn has quit IRC13:37
*** kaisers has joined #openstack-manila13:40
openstackgerritValeriy Ponomaryov proposed openstack/manila: [Devstack] Run tempest update in proper time  https://review.openstack.org/40538313:41
openstackgerritMarc Koderer proposed openstack/manila: Add first unit test for race conditions  https://review.openstack.org/40113213:44
*** snecklifter has joined #openstack-manila13:44
snecklifterHello, I'm using tripleo and getting "Error: Duplicate declaration: Package[nfs-utils] is already declared in file"13:45
snecklifter"/etc/puppet/modules/tripleo/manifests/profile/base/cinder/volume/nfs.pp:53"13:45
sneckliftercannot redeclare at /etc/puppet/modules/manila/manifests/backend/netapp.pp:14413:45
snecklifterany ideas?13:45
openstackgerritMarc Koderer proposed openstack/manila: Add first unit test for race conditions  https://review.openstack.org/40113213:47
*** kaisers has quit IRC13:47
vponomaryovsnecklifter: I guess you shoul dask in "tripleo" channel, not here13:50
sneckliftervponomaryov: never get a response in there, thought I'd try here, thanks anyway13:51
vponomaryovsnecklifter: your question is not about manila, so, I very doubt anyone can help you here13:51
sneckliftervponomaryov: I only get the error when I deploy manila but perhaps openstack-puppet will help13:52
*** snecklifter has left #openstack-manila13:52
*** timcl has joined #openstack-manila13:57
openstackgerritHelen Walsh proposed openstack/manila: VMAX manila plugin - Support for VMAX in Manila  https://review.openstack.org/40485914:09
*** StraubTW has joined #openstack-manila14:15
*** jprovazn has joined #openstack-manila14:16
*** kaisers has joined #openstack-manila14:17
*** gouthamr has joined #openstack-manila14:17
openstackgerritMerged openstack/manila: Fix wrong data type in database migration  https://review.openstack.org/40031014:18
*** eharney has joined #openstack-manila14:19
*** dustins has joined #openstack-manila14:21
*** gouthamr_ has joined #openstack-manila14:22
*** gouthamr has quit IRC14:22
*** kaisers has quit IRC14:24
*** a-pugachev has left #openstack-manila14:28
*** kaisers1 has quit IRC14:28
*** a-pugachev has joined #openstack-manila14:29
*** kaisers has joined #openstack-manila14:30
*** gouthamr has joined #openstack-manila14:34
*** gouthamr_ has quit IRC14:36
*** makowals has quit IRC14:53
*** dsariel has quit IRC14:55
*** dsariel has joined #openstack-manila14:56
openstackgerritVictoria Martinez de la Cruz proposed openstack/manila: Decouple Manila UI from Manila Devstack plugin  https://review.openstack.org/38885515:02
*** makowals has joined #openstack-manila15:04
*** absubram has quit IRC15:12
*** rraja has quit IRC15:15
*** kaisers_ has joined #openstack-manila15:21
*** cknight has joined #openstack-manila15:23
*** shausy has quit IRC15:28
*** kaisers_ has quit IRC15:29
*** mtanino has joined #openstack-manila15:33
*** senk has quit IRC15:38
*** wiebalck has joined #openstack-manila15:39
*** akapil has quit IRC15:39
*** akapil has joined #openstack-manila15:40
openstackgerritVictoria Martinez de la Cruz proposed openstack/manila: Decouple Manila UI from Manila Devstack plugin  https://review.openstack.org/38885515:40
*** sandanar has quit IRC15:46
*** nkrinner is now known as nkrinner_afk15:49
*** wiebalck has quit IRC15:53
*** kambiz has joined #openstack-manila15:57
*** makowals has quit IRC16:01
*** akapil has quit IRC16:02
vponomaryovcore-team: need to merge this -> https://review.openstack.org/#/c/405383/ it is fix for recently broken Scenario CI job16:02
*** akapil has joined #openstack-manila16:02
*** makowals has joined #openstack-manila16:02
vponomaryovbswartz: also need your attention here -> https://review.openstack.org/#/c/396632/16:03
gansovponomaryov: it appears Cinder guys also got problems related to the same change16:03
gansovponomaryov: so, at first I was wondering if devstack guys were going to fix this16:04
vponomaryovganso: I am not surprised16:04
vponomaryovganso: are you kidding? ))16:04
gansovponomaryov: they broke everybody, they should fix :P16:04
gouthamrvponomaryov ganso: noob q without looking.. hey, does this affect us injecting tempest.conf options?16:04
gansogouthamr: that is exactly the problem16:04
vponomaryovgouthamr: it is THE PROBLEM16:05
gouthamrganso: explains why so many CIs are broken then.16:05
vponomaryovin addition to our attempt to "pin" tempest )16:05
gouthamr#freetempest16:05
gansovponomaryov: how about https://review.openstack.org/#/c/40544616:07
gansogouthamr, markstur: I think we shouldn't workflow https://review.openstack.org/#/c/405383/ yet16:08
vponomaryovganso: not again, one more false -116:10
vponomaryovganso: it is not replacement for our fix16:10
vponomaryovour fix is to change order16:11
gansovponomaryov: comment in that one says that it has broken CIs and is attempting to fix16:11
vponomaryovthis one is to add more possibilities16:11
vponomaryovganso: CIs could be broken in lots of ways16:11
gansovponomaryov: for my CI it seems the merge_config part is the one that is breaking16:11
gansovponomaryov: so it could address most CI problems16:12
*** absubram has joined #openstack-manila16:12
*** dsariel has quit IRC16:13
*** shausy has joined #openstack-manila16:17
vponomaryovbswartz: according to generic driver breakage https://bugs.launchpad.net/manila/+bug/164452316:20
openstackLaunchpad bug 1644523 in Manila "DHSS=False generic driver CI job fails all the time" [High,In progress] - Assigned to Valeriy Ponomaryov (vponomaryov)16:20
vponomaryovbswartz: cannot reproduce locally16:20
vponomaryovbswartz: everything just works for me16:21
vponomaryovbswartz: using latest code16:21
vponomaryovand manila connectivity fix16:21
gansovponomaryov: maybe similar to ZFS host-assisted migration problem that I wasn't able to get it working in CI but works in lab?16:22
vponomaryovganso: ?16:23
vponomaryovganso: the problem is in one/some nova commits that were merged after 24th of November16:23
vponomaryovganso: and before 30th16:24
gansovponomaryov: ok16:25
*** timcl1 has joined #openstack-manila16:25
gansovponomaryov: well, it shouldn't have worked in lab then16:25
*** kaisers_ has joined #openstack-manila16:26
*** a-pugachev has quit IRC16:28
*** timcl has quit IRC16:29
*** shausy has quit IRC16:34
*** kaisers_ has quit IRC16:35
*** shausy has joined #openstack-manila16:35
*** shausy has quit IRC16:45
*** akapil has quit IRC16:46
*** shausy has joined #openstack-manila16:48
* ganso proposes openstack/manila: Remove driver config docs from devref https://review.openstack.org/40551616:51
* ganso is wondering why the openstackgerrit did not notify of his patch16:51
bswartzganso: why not let the bot announce your patch?16:51
gansobswartz: it was a couple of minutes ago16:52
* bswartz slaps openstackgerrit around a bit with a large trout16:52
gansobswartz: and it did not announce anything16:52
bswartzthe bot is alive and in the channel16:52
gansobswartz: how do you know it is alive? did it slap you back?16:52
bswartzganso: the list of people in channel16:53
bswartzit must be hung16:53
gansobswartz: I guess it could be frozen or stuck or something16:53
bswartzvponomaryov: I'm not sure what you're saying16:54
bswartzvponomaryov: the bugs continues to reproduce in the gate but not locally?16:54
vponomaryovbswartz: right16:54
bswartzvponomaryov: what could explain that?16:54
vponomaryovdifference in setup16:55
vponomaryovrequired versions of some system packages, etc16:55
vponomaryovmoreover, look here -> https://review.openstack.org/#/c/404963/16:57
vponomaryovit passed with PS4 on first jenkins run16:57
vponomaryovand failed on second16:57
vponomaryovso, it is some intersection of different things that are not determined yet16:58
bswartzoh not not another nondeterministic bug16:58
bswartz>_<16:58
*** shausy has quit IRC17:04
*** timcl1 has quit IRC17:09
*** rraja has joined #openstack-manila17:09
*** porrua has quit IRC17:13
*** timcl has joined #openstack-manila17:17
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 11  https://review.openstack.org/40496117:17
*** senk has joined #openstack-manila17:22
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 15  https://review.openstack.org/40554317:30
*** kaisers_ has joined #openstack-manila17:32
*** kaisers_ has quit IRC17:39
*** porrua has joined #openstack-manila17:41
*** senk has quit IRC17:44
openstackgerritMerged openstack/manila: LOG marker mismatch in the code  https://review.openstack.org/40457017:45
*** chlong has joined #openstack-manila17:45
openstackgerritValeriy Ponomaryov proposed openstack/manila: [DNM] test 9  https://review.openstack.org/40475717:49
*** senk has joined #openstack-manila18:04
*** timcl1 has joined #openstack-manila18:04
*** Yogi1 has joined #openstack-manila18:07
*** timcl has quit IRC18:07
*** dustins has quit IRC18:15
*** senk has quit IRC18:17
*** nherciu has quit IRC18:29
*** mkoderer has quit IRC18:33
*** kaisers_ has joined #openstack-manila18:36
*** kaisers_ has quit IRC18:43
openstackgerritValeriy Ponomaryov proposed openstack/manila: [Devstack] Fix DHSS=False setup for Generic driver  https://review.openstack.org/40365118:56
vponomaryovbswartz: statistics of running debug commits say that Nova commits are NOT culprit and migrations tests too. It means we were failing because of some other reason that exists NOT in all CI nodes. So, I would say, above change is candidate for merge as fix for 'losing connection' part.18:58
gansovponomaryov: i've faced this before19:00
gansovponomaryov: when you were on vacation19:00
gansovponomaryov: I found a problem that happened only on some CI nodes19:00
gansovponomaryov: from what I could tell, something related to their network infra, they had some ipv6 parameters displayed during startup19:01
gansovponomaryov: those node variations exposed a flaw in the generic driver code19:01
gansovponomaryov: which I fixed19:01
gansovponomaryov: it was something dumb19:01
gansovponomaryov: but the variation caused it19:02
gansovponomaryov: I'll get 2 examples for you19:02
gansovponomaryov: they are easy to spot19:02
*** timcl has joined #openstack-manila19:03
bswartzvponomaryov: so the plan is to fix the 1 bug we know about and hope that the other bug isn't too annoying?19:03
gansovponomaryov: this is example 1: http://logs.openstack.org/51/403651/6/check/gate-manila-tempest-dsvm-scenario-ubuntu-xenial-nv/8d5103e/console.html19:04
vponomaryovbswartz: I would say it does not worth time19:04
gansovponomaryov: this is example 2: http://logs.openstack.org/51/403651/6/check/gate-manila-tempest-dsvm-postgres-zfsonlinux-ubuntu-xenial-nv/2ccbcf7/console.html19:04
*** timcl1 has quit IRC19:04
gansovponomaryov: look at the "Network neighbors..." section in the beginning19:04
vponomaryovbswartz: also, we will have better statistics merging 'connectivity' fix19:06
vponomaryovganso: according to your comment about "admin_net" and our discussion, I guess you agree that floating Ip is ok in this fix?19:06
gansovponomaryov: using admin_net approach + admin_net for this case yes19:07
gansovponomaryov: using *floating_ip approach + admin_net for this case yes19:07
vponomaryovganso: O.O19:09
vponomaryovganso: I have such eyes after reading answer19:09
gansovponomaryov: the wrong answer19:09
gansovponomaryov: right?19:09
vponomaryovganso: both19:09
vponomaryovganso: you either agree or not19:10
vponomaryov))19:10
vponomaryovbecause admin_net depends on service_instance.py module, and it is completely different approach that we should not bother ourselves with19:10
gansovponomaryov: previously, the generic driver was not returning an admin_only=True export location19:10
vponomaryovganso: it was bug19:11
vponomaryovganso: design assumes both19:11
vponomaryovadmin and user's locations19:11
gansovponomaryov: so, if you make it return an export location that you access through floating ip connection, and it is admin_only=True, that would be ok19:11
vponomaryovyes, it is exactly so now19:11
gansovponomaryov: that is great19:11
vponomaryovsee https://review.openstack.org/#/c/403651/19:11
vponomaryovand was so when you proposed admin net )19:12
vponomaryov^_^19:12
*** xyang1 has joined #openstack-manila19:13
openstackgerritValeriy Ponomaryov proposed openstack/manila: [Devstack] Use openstack CLI instead of other clients  https://review.openstack.org/40216919:13
*** kaisers_ has joined #openstack-manila19:17
*** dgonzalez_ has joined #openstack-manila19:19
openstackgerritMerged openstack/puppet-manila: Fix spec test for sync  https://review.openstack.org/40520419:22
*** david-lyle_ has joined #openstack-manila19:28
*** david-lyle has quit IRC19:31
*** openstackgerrit has quit IRC19:32
*** openstackgerrit has joined #openstack-manila19:33
*** dustins has joined #openstack-manila19:35
*** openstackgerrit has quit IRC19:36
dustinsHey all, is there a way to tell the Tempest tests to use a preexisting share type through the Tempest conf rather than specifying one in the Manila conf?19:51
bswartzdustins: depends on which tests IIRC19:52
bswartzmany tests create share types as part of the test19:53
dustinsyeah, I think I'm getting tripped up on failures where it expects one to be there19:53
* dustins grabs the actual test failure19:53
bswartzwhat problem are you trying to solve?19:53
dustinsI guess I want to know how to tell Tempest that when it needs to use a pre-existing share type, to use this one19:54
dustinsRather than providing a default type in the Manila configuration19:54
dustinsmanila_tempest_tests.tests.api.admin.test_export_locations.ExportLocationsTest19:54
dustinsThat's (one of) the offending tests19:55
bswartzwell I was going to say -- tempest should use the default -- it shouldn't expect anything else to exist19:55
bswartzhowever it's impossible for the default to not exist -- so I'm confused19:55
dustinsThere are a few tests that fail with a scheduler error saying that the request requires a share type and that it either needs to be included in the request or defined in the manila conf19:55
bswartzdustins: what happens when you simply run "manila create NFS 1"?19:57
dustinshttp://paste.openstack.org/show/591174/19:57
dustinsThat's the error from the scheduler I'm seeing19:57
dustinsOne second...19:57
dustinsbswartz: http://paste.openstack.org/show/591175/19:58
dustinsTL;DR: It fails19:58
bswartzdustins: you really need to be creating a default share type then19:59
bswartzdevstack does this for you19:59
bswartzif you're not using devstack then whatever you're using has a bug20:00
dustinsIs it something that we expect deployers to do?20:00
dustinsSounds like it is20:00
bswartzthe default is not optional20:00
*** openstackgerrit has joined #openstack-manila20:00
openstackgerritJan Provaznik proposed openstack/puppet-manila: Update ceph.conf when setting manila ceph backend  https://review.openstack.org/40560120:00
dustinsSo there always has to be at least one share type defined, the default one20:00
bswartzdeployment tools are required to populate manila.conf with a valid default share type20:00
bswartzyes20:01
dustinsHuh, I didn't know that, actually20:01
bswartzit's a backwards compatibility thing20:01
bswartzusers expect to be able to get shares without specifying a share type20:01
*** david-lyle_ is now known as david-lyle20:01
bswartztherefore a default must exist20:01
dustinsLooks like I gotta open a bug, then20:02
dustins(and assign a default share type :) )20:02
bswartzsuch is the life of QA engineers20:02
dustinsIndeed, though it's QE now :P20:02
bswartzI keep hearing that20:03
bswartzwhat does QE stand for?20:03
dustinsQuality Engineer20:03
dustinsSame thing, different title, haha20:03
bswartzokay so you don't say QE engineer, you just say QE20:03
dustinsYup!20:08
dustinsI'll say "I'm OpenStack QE" when someone asks what I do20:08
*** dsariel has joined #openstack-manila20:11
*** rraja has quit IRC20:23
tbarronbswartz: just to be clear, it is perfectly possible to make /etc/manila.conf w/o setting a default share type, the default value in the sample conf is <None>, and it is perfectly possible to create non-default share types and have users always refer to a share type when they create shares20:26
tbarronbswartz: so even though **devstack** doesn't do that, I don't agree that deployments are always broken if they don't populate with a valid default share type20:27
tbarronbswartz: we developers may have the expectation that it will be set from working with devstack.20:27
tbarronbswartz: but do we document or otherwise set that expectaion otherwise?20:27
dustinstbarron: Though without the default share type set, the suite of Tempest tests will fail20:27
dustinsWhich to me seems like an issue with Tempest20:27
tbarrondustins: most cloud builders never run tempest20:28
tbarronbswartz: if we want to insist that it be set we should fail startup with it unset, no?20:28
dustinstbarron: +120:29
*** timcl has quit IRC20:30
*** porrua has quit IRC20:33
*** catinthe_ has quit IRC20:34
*** porrua has joined #openstack-manila20:38
*** openstack has joined #openstack-manila20:45
*** lpetrut has joined #openstack-manila20:52
*** jprovazn has quit IRC20:55
tbarronbut failing startup if it's not set would be backwards-incompatible, as would failing anythiing else if it's not set20:58
*** lpetrut has quit IRC20:58
openstackgerritVictoria Martinez de la Cruz proposed openstack/manila-image-elements: Removes LXC/LXD support on manila-image-elements  https://review.openstack.org/40562920:58
*** timcl has joined #openstack-manila21:02
*** alyson_ has quit IRC21:05
*** timcl has quit IRC21:08
*** timcl has joined #openstack-manila21:11
bswartztbarron: when we designed the whole default share type thing, we had to decide whether to require deployments to ensure that the default share type existed or whether manila should create one on its own21:17
bswartztbarron: at the time, no automated deployment tools existed, so there was nobody to inform of our decision21:17
bswartztbarron: however we decided it was better to let the deployment tool set the default share type, because of issues with DHSS=true/false21:18
*** lseki has quit IRC21:18
bswartzWe could ensure that the API service crashes on startup if nothing is defined -- if that would be a clearer way to communicate to users that they need to do something21:18
bswartzbasically we made this decision like 2 years ago and this is the first time it's caused a problem21:19
tbarronbswartz: but also you allow everything (except tempest) to work without setting a default share type, so you have let the cat out of the bag21:19
bswartztbarron: no that's not true21:19
tbarronbswartz: it only doesn't cause a problem b/c cloud deployers don't run tempest21:19
tbarron?21:19
bswartzdustins demonstrated that "manila create NFS 1" fails out of the box if you don't set the default share type21:19
bswartzthat's "working as intended" from my perspective21:20
tbarronright, but all you have to do is provide a shar-type with the command and it works21:20
bswartzyes21:20
bswartzthat doesn't mean it's okay to not have a default share type21:20
tbarronso it's natural to think that I can make a cloud and tell my users here are the share types and there is no default21:20
tbarronmight even be a great use case21:21
tbarroninsist on explicit when it's too easy to make a mistake if there's a default21:21
bswartzit's not a valid use case because it breaks backwards compatibility21:21
tbarrononly with tempest21:21
tbarronnot with deployments21:21
bswartzno with clients that expect a default to exist21:21
tbarron?  what clients?  none that we publish21:22
bswartz"manila create NFS 1" is supposed to work21:22
bswartzit's been defined as a valid command for years21:22
bswartzwe can't suddenly take that away from users21:22
bswartznow how we make it work is up to us21:23
bswartzwe can be more aggressive in forcing the admin to define the default, by refusing to start until it exists21:23
bswartzor we can do something like creating a magical default21:23
tbarronseems backwards incompat21:23
bswartzbackwards incompatible how?21:24
tbarronbswartz: yeah, maybe.  Probably DHSS=False if my market research is correct :)21:24
bswartzmy point is that for API compatibility, the default must continue to exist21:24
tbarronit's a behavioral change in startup.  cloud admins could be relying on the current behavior that they can runn without it.21:24
bswartztbarron: that's an upgradability issue, not a compatibility issue21:25
bswartzwhen we talk about backward compatibility, we only care about end users and REST APIs21:25
tbarronbswartz: ok, I can go with upgradability vs api compatability, got it21:25
bswartzadmins get much rougher treatment than end users21:26
tbarronmy customers care about both so I tend to elide the two21:26
bswartzhowever we do claim to care about upgradeability, so I agree there's an issue21:26
tbarronin the near term dustin is just going to create a default share type before running tempest, but21:26
tbarronI think we can inisist that there always be a default share type, and21:27
tbarronatm I'm inclined to think making a magic one may make sense as a21:27
bswartzthe question is how do we guarantee it's present?21:27
bswartzwhat's wrong with creating it as part of deployment?21:28
tbarronway to avoid too much unpleasant surprise.21:28
bswartzrpm -i manila should result in a default share type existing21:28
tbarronbswartz: we can create as part of deployment, but that just puts the decision of DHSS=False or True downstream on the deployer.21:28
tbarronbswartz: right, I don't want it to be a tripleo or fuel or crowbar thing.21:29
bswartztbarron: I agrue that's where it should be21:29
tbarronthese can override if they want21:29
*** kaisers_ has quit IRC21:29
bswartzthose tools know what drivers also being configured21:29
tbarron"that's " - in the packager's decision?21:29
bswartzyes21:29
tbarronoh, in the deployer rmp?21:29
tbarrondeployer tool?21:30
bswartzthe extra specs on the default share type should be compatible with at least one configured backend21:30
bswartzotherwise the situation is as bad as not having the default21:30
bswartzand nobody knows what backends are configured except the deployment tool21:30
tbarronbswartz: and how would it decide if multiple backends are deployed, some DHSS=True and some false?21:31
bswartzthe reason this is so ugly is because we decided to make DHSS a *required* extra spec and not allow people to leave it blank21:31
tbarronbswartz: we can't just punt all hard decisions downstream :)21:31
bswartzwell this particular hard decision has come home to roost21:31
bswartzit was made during Kilo and didn't cause and problems until now21:32
tbarronbswartz: i expect we agree that default share type would be a lowest-common denominator, nothing but DHSS=True or False.21:32
tbarronthe rest is up to the cloud admin to set21:32
bswartzyeah21:32
bswartzI worry that creating a magical one will lead to unexpected behavior21:32
bswartzmaybe it's the lesser to 2 evils21:33
bswartzof* 2 evils21:33
* dustins gets the feeling that he accidentally kicked the hornets nest 21:33
dustins:P21:33
tbarronbswartz: maybe right, sounds like something we should discuss at the next meeting21:33
tbarronbswartz: I'm not trying to force any quick decision21:33
*** Yogi1 has quit IRC21:33
tbarronbswartz: but would be very interested in what SUSE or MOS or Helion or SAP or Cern, etc. think21:34
bswartzyeah I agree21:34
bswartzwe had the luxury of not worrying about them back in the kilo timeframe21:34
tbarron:)21:35
bswartztbarron: https://wiki.openstack.org/wiki/Manila/Meetings21:35
gansobswartz, tbarron: sorry if I am interrupting the current discussion, but I would like to clarify this https://review.openstack.org/#/c/405516/21:35
tbarronbswartz: we're good, ty21:35
tbarronganso: ty21:36
tbarronbswartz: ganso and I had different memories.  emprically, I would be on his.  subjectively, I'm attached to my own.21:36
tbarronbswartz: ganso final thoughts on this likely should include gouthamr21:37
* gouthamr wakes up21:37
gansoI believed we agreed to remove the docs because they were going to have duplicated information according to the config ref and woul have be synced over time21:37
gansoso the last comments of that subject in the meeting were in regards to the first party drivers, who maintains them21:38
gansothe community maintains, but I am not sure if we agreed to as where... so what made sense to me was that the community maintains them at the config ref, to avoid duplicity21:39
gansosorry I just googled for duplicity and I think that is not the word I want to use21:39
tbarronganso: yeah, duplicity is for high offices in the land21:40
gansos/duplicity/duplicated entries21:40
tbarronand secret agents21:40
gansotbarron: duplicity sounds similar to what we use in portuguese for "duplicated entries"21:40
bswartzall of the first party drivers have official maintainers21:41
tbarronganso: yeah, i think for romance languages in general21:41
gouthamrganso tbarron: it's valuable to have developer oriented documentation regarding first party drivers in the devref21:41
bswartzwith the exception of the container driver which is officially unmaintained21:41
tbarronbswartz: yeah, and they can just update the config, i think gouthamr and I were thinking it's very useful for developers to look for config and deployment info on first-party in devref.21:42
gouthamrganso tbarron: config ref speaks to storage admins imo, i get confused seeing how some of the "simple stuff" is documented there.21:42
tbarronbswartz: ganso perhaps all config should be in official config, all deployment in official deployment, but21:42
gouthamrganso tbarron: when someone starts contributing to our project, they're not going to go through the configuration ref21:42
gouthamrthat's for deployers.21:42
bswartztbarron yes!21:42
bswartzgouthamr: the dev docs can refer to other docs21:43
tbarronbswartz: ganso devref can contain a little wrapper thing around pointers to those and any special stuff useful for developers to know21:43
bswartzrefering to other docs is way better than duplicating content21:43
gouthamrbswartz: yes they can.. but take a look at how the ZFS/LVM documentation is written - it's for devstack21:43
bswartzgouthamr: that can be fixed21:43
gouthamrbswartz: i meant, currently, in the devref.... i'd hate to complicate the learning curve for new contributors21:44
tbarronso it would be helpful to have a section for each first party driver on how to deploy in devstack21:45
gouthamrbswartz: i think it's good to have stuff in there that'd help someone set up any of the first party drivers.. no complicated configuration or deployment advice..21:45
bswartzgouthamr: we can include information in the devref that's useful for developers without duplicating information that really belongs in deployer-facing docs21:45
gouthamrbswartz: +121:45
tbarronfor each non-vendor open source driver, not arguing atm that they are co-extensive sets :)21:45
tbarronit would be a choice of the upstream community for such open source drivers if they want to provide such developer-friendly doc21:46
gouthamrganso tbarron: so, maybe we can audit them before throwing them out right away? by all means remove vendor docs right away...21:46
tbarrongouthamr: +121:47
gansogouthamr: I am not seeing any reference to devstack for step-by-step on how to setup ZFS here: https://review.openstack.org/#/c/405516/1/doc/source/devref/zfs_on_linux_driver.rst21:47
bswartzgouthamr: the code review is where the audit should happen -- review ganso's patch21:47
tbarronbswartz made the good point that the info is not really *lost* as it's in git but it still could be a bit unfriendly21:47
bswartztbarron: +121:47
gouthamrtrue :)21:48
gansogouthamr: and I don't see the LVM doc page21:48
tbarronthis was a good discussion, I think we could suggest some incrementalism in the code review21:48
bswartzganso: blame the LVM maintainer -- oh wait's that me :-[21:48
gouthamrsigh.21:48
gansoI looked at all the pages and I did not find info I found relevant to developers21:48
gouthamrganso: okay, we can fix that..21:48
* tbarron blames bswartz again21:48
tbarronPTL gets default scapegoat role anyways21:49
bswartzLVM is not hard to maintain21:49
bswartzif it's missing a config ref I can add it21:49
*** cknight has quit IRC21:49
tbarronbswartz: iirc the cental config ref for LVM is ok21:49
* gouthamr adds LVM to install guide21:49
tbarroncentral21:50
* gouthamr is really cool that way21:50
tbarrongouthamr has really good hair too21:50
gouthamrlol21:50
gansoo_O21:50
tbarronhe's riding in his sports car with his shades on right now21:51
gouthamrganso tbarron: devref can now have quick deploy all the first party drivers in an all-in-one machine (almost types devstack) then?21:51
gouthamrtbarron: i'm the one who's supposed to be sleeping and dreaming, lol :P21:52
gansogouthamr: I have never tried that21:52
gouthamrwe'll soon have instructions how to - i have bswartz's recipe for lvm, i can post that21:53
tbarrongouthamr: it's a good dream.  Across platforms right now I believe empirically that lvm and cephfs will work together, am working on extending that set.  generic is proving indeterminstic so far. I haven't really mucked with container yet though I like it conceptually.21:55
tbarrongouthamr: probably need to put caveats around disk size and ram for the vm too.21:55
gouthamrtbarron: the container driver works on devstack/ubuntu just the way it's written21:56
tbarrongouthamr: that's the second platform I run on (xenial)21:56
tbarrongouthamr: i don't bother with trusty since upstream is off of it21:56
gouthamrtbarron: nice..21:56
tbarrongouthamr: it's not really ideological - we've just seen today a case where devstack assumptions aren't aligniing with distro/deployement assumptions21:57
tbarrongouthamr: so since I have to support the latter I want my first devstack to approximate it as much as possible21:58
tbarrongouthamr: then I care about xenial b/c (1) that's certainly valid too, and (2) it runs in gate21:58
*** kaisers_ has joined #openstack-manila21:59
gouthamrtbarron: i agree... it's also dead simple to new developers and unless the feature demands it, i've not needed to use any other way of deploying.22:00
tbarrongouthamr: ^^ you are referring to container driver?22:00
*** dsariel has quit IRC22:00
gouthamrtbarron: but then i'm reminded of availability zones22:00
gouthamrtbarron: i'm referring to devstack aio22:01
tbarrongouthamr: got it22:01
tbarrongouthamr: devstack aio is great, but not good for distributed computing issues and we'll be seeing more of those as we move forwards22:01
tbarrongouthamr: finding a compact developement environment that's easy and fast to deploy for those is a challenge22:02
tbarrondevelopment22:02
tbarronganso spells so much better than I do22:03
gouthamrtbarron: yeah, it's a pita to get multi-node working - which is why i tested tooz on a real deployment..22:03
*** openstackgerrit has quit IRC22:03
gansotbarron: I really don't think I do22:03
* tbarron notices that gouthamr reminded him of his debt on the tooz review22:03
gouthamrtbarron: by real i used multi-node separation from a fancy hat company22:03
tbarronvery politely though22:03
tbarrongouthamr: well, that's real, but we could be making assumptions of our own :)22:04
tbarrongouthamr: that's partly a theoretical point, and partly practical22:04
*** eharney has quit IRC22:04
tbarrongouthamr: historically, we've had rigid "roles" - controller, compute, storage22:05
tbarrongouthamr: but customers wanted flexibility and now they are "composable"22:05
tbarrongouthamr: and even though stuff was distributed before, we see breakage now when things weren't as decoupled as everyone thought22:06
*** timcl has quit IRC22:06
tbarronganso: it doesn't matter what you *think*; it matters how you *spell* - but just for this narrow point, you think just fine too22:06
gansotbarron: lol I am very confused, but thanks22:08
gouthamrtbarron: ah, interesting... containerized deployments are going to make things further challenging..22:09
tbarronganso: fair enough, i was back-referencing your remark about not thinking you spell things better than I22:09
tbarronganso: but not a substantive remark on my part22:09
tbarrongouthamr: yeah, they change the dependency game.  I can deploy manila with old neutron and tempest dependencies - internally.22:10
*** kaisers__ has joined #openstack-manila22:10
gouthamrtbarron: we should start integrating and testing manila with OSA to understand that22:11
tbarrongouthamr: but in the actual cloud unless neutron and nova (and tempest when I test) can handle the old depencies I think we're still in trouble, no?22:11
gouthamrtbarron: i think we have folks that use bleeding manila with older neutron22:12
tbarrongouthamr: w.r.t OSA, maybe.  personally I'm more inclined to kolla/kubernetes, but what do I know?22:12
gouthamrtbarron: not sure how much older though22:12
tbarrongouthamr: are you asking in mkoderer___ is still working tonight?22:13
gouthamrtbarron: if he has so many underscores, he's probably snoozing22:13
*** kaisers_ has quit IRC22:13
tbarrongouthamr: it's way past your bedtime and I need to eat dinner22:14
gouthamrtbarron: haha true... ciao!22:14
*** gouthamr has quit IRC22:17
*** dustins has quit IRC22:29
*** chlong has quit IRC22:50
*** adrianofr_ has quit IRC22:53
*** tpsilva has quit IRC22:55
*** xyang1 has quit IRC23:12
*** StraubTW has quit IRC23:13
*** absubram has quit IRC23:22

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