Tuesday, 2016-08-23

*** yangyapeng has quit IRC00:05
*** Suyi has quit IRC00:21
*** Suyi has joined #openstack-manila00:42
*** gouthamr has joined #openstack-manila00:52
*** zengyingzhe_ has quit IRC00:56
*** zengyingzhe has joined #openstack-manila00:59
*** yangyapeng has joined #openstack-manila01:21
*** wangqun has joined #openstack-manila01:31
*** yangyape_ has joined #openstack-manila01:32
*** yangyapeng has quit IRC01:35
*** yangyape_ has quit IRC01:49
*** vbellur has joined #openstack-manila02:00
*** mtanin___ has quit IRC02:07
*** yangyapeng has joined #openstack-manila02:36
*** yangyape_ has joined #openstack-manila02:37
*** yangyapeng has quit IRC02:40
*** yangyape_ has quit IRC02:47
*** yangyape_ has joined #openstack-manila02:50
*** yangyap__ has joined #openstack-manila02:56
*** gouthamr_ has joined #openstack-manila02:57
*** gouthamr has quit IRC02:58
*** yangyape_ has quit IRC02:58
*** yangyapeng has joined #openstack-manila03:01
*** gouthamr_ is now known as gouthamr03:01
*** yangyap__ has quit IRC03:05
*** yangyapeng has quit IRC03:17
*** yangyapeng has joined #openstack-manila03:22
*** Suyi has quit IRC03:25
*** yangyape_ has joined #openstack-manila03:34
*** yangyapeng has quit IRC03:36
*** ganso has quit IRC03:41
*** gouthamr has quit IRC03:44
*** daidv has joined #openstack-manila03:49
*** yangyape_ has quit IRC03:50
*** daidv has quit IRC04:07
*** Suyi has joined #openstack-manila04:23
*** assassin has quit IRC04:32
*** yangyape_ has joined #openstack-manila04:37
openstackgerritRamana Raja proposed openstack/python-manilaclient: add access_key to access_list API's response  https://review.openstack.org/34494804:39
*** yangyape_ has quit IRC04:45
*** yangyape_ has joined #openstack-manila04:50
*** yangyape_ has quit IRC04:55
*** yangyape_ has joined #openstack-manila05:04
*** yangyape_ has quit IRC05:09
*** Suyi has quit IRC05:12
*** yangyape_ has joined #openstack-manila05:20
*** yangyape_ has quit IRC05:28
*** yangyape_ has joined #openstack-manila05:33
*** sandanar has joined #openstack-manila05:37
*** nkrinner_afk is now known as nkrinner05:48
*** yangyape_ has quit IRC05:50
*** yangyape_ has joined #openstack-manila05:59
*** yangyap__ has joined #openstack-manila06:00
*** yangyap__ has quit IRC06:01
*** yangyap__ has joined #openstack-manila06:02
*** yangyapeng has joined #openstack-manila06:03
openstackgerritAlexey Ovchinnikov proposed openstack/manila: [DNM] Tests for scenario tests  https://review.openstack.org/34023606:04
*** yangyape_ has quit IRC06:05
*** bhakta_ has quit IRC06:05
*** yangyapeng has quit IRC06:07
*** yangyap__ has quit IRC06:07
*** bhakta has joined #openstack-manila06:12
*** pcaruana has joined #openstack-manila06:14
openstackgerritThomas Bechtold proposed openstack/manila: Remove enable_v1_api and enable_v2_api config opts  https://review.openstack.org/35840606:27
*** lpetrut has joined #openstack-manila06:35
*** yangyape_ has joined #openstack-manila06:38
*** ubijtsa has joined #openstack-manila06:40
*** ubijtsa is now known as Guest1118206:40
*** Guest11182 has quit IRC06:41
*** Guest11182 has joined #openstack-manila06:41
*** yangyapeng has joined #openstack-manila06:42
*** yangyape_ has quit IRC06:42
*** Guest11182 is now known as assassin06:42
*** yangyape_ has joined #openstack-manila06:44
*** yangyapeng has quit IRC06:48
openstackgerritOpenStack Proposal Bot proposed openstack/manila-ui: Imported Translations from Zanata  https://review.openstack.org/35898506:51
*** yangyape_ has quit IRC07:01
openstackgerritNidhiMittalHada proposed openstack/manila: manila does not calculate allocated_capacity_gb  https://review.openstack.org/35103407:03
*** dsariel has joined #openstack-manila07:04
*** yangyapeng has joined #openstack-manila07:05
*** qeelee has joined #openstack-manila07:21
*** lpetrut has quit IRC07:26
*** lpetrut has joined #openstack-manila07:40
*** lpetrut has quit IRC08:01
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-manila08:04
*** aovchinnikov has joined #openstack-manila08:17
*** dsariel has quit IRC08:20
*** dsariel has joined #openstack-manila08:26
*** qeelee has quit IRC08:30
*** lpetrut has joined #openstack-manila08:41
*** lpetrut has quit IRC08:50
*** kaisers_ has joined #openstack-manila09:10
*** lpetrut has joined #openstack-manila09:21
openstackgerritzhongjun proposed openstack/manila: Implement share backup  https://review.openstack.org/34398009:28
*** nkrinner has quit IRC09:28
*** nkrinner has joined #openstack-manila09:42
*** wangqun has quit IRC10:03
*** qeelee has joined #openstack-manila10:05
*** lpetrut1 has joined #openstack-manila10:10
*** lpetrut has quit IRC10:11
*** lpetrut1 is now known as lpetrut10:11
*** yangyapeng has quit IRC10:28
openstackgerritCedric Zhuang proposed openstack/manila: Add documentation for EMC Unity Driver for Manila  https://review.openstack.org/35857610:33
*** qeelee has quit IRC10:43
openstackgerritRodrigo Barbieri proposed openstack/manila-ui: Add share type change to Share Migration UI  https://review.openstack.org/34566410:50
openstackgerritRodrigo Barbieri proposed openstack/manila-ui: Add Share Migration support  https://review.openstack.org/34443110:50
*** ganso has joined #openstack-manila10:50
*** alyson_ has joined #openstack-manila11:06
*** JoseMello has joined #openstack-manila11:21
openstackgerritAlexey Khodos proposed openstack/manila: Nexenta: adding share drivers for NexentaStor  https://review.openstack.org/30928611:30
openstackgerritTatiana Ovchinnikova proposed openstack/manila-ui: Additional fields for Create/Update Share Type forms  https://review.openstack.org/33850411:33
openstackgerritMerged openstack/manila-ui: Imported Translations from Zanata  https://review.openstack.org/35898511:33
*** netapp has quit IRC11:41
*** netapp has joined #openstack-manila11:48
*** wangqun has joined #openstack-manila11:51
*** dsariel has quit IRC11:58
*** yangyapeng has joined #openstack-manila12:01
*** xyang1 has joined #openstack-manila12:05
*** tpsilva has joined #openstack-manila12:08
*** kaisers_ has quit IRC12:11
zhongjun_bswartz: ping12:14
openstackgerritRodrigo Barbieri proposed openstack/manila: [DEBUG] PLEASE DO NOT MERGE 4  https://review.openstack.org/35916612:26
*** gouthamr has joined #openstack-manila12:26
tpsilvagouthamr: ping12:41
gouthamrhey tpsilva12:41
tpsilvagouthamr: hey Goutham! good morning12:41
tpsilvagouthamr: quick question: how can I find the bug issues raised by the DocImpact flag?12:41
gouthamrtpsilva: hey.. they will have a DocImpact right on top..12:51
tpsilvagouthamr: oh, but the DocImpact flag does not raise an issue on launchpad or something?12:51
gouthamrtpsilva: https://bugs.launchpad.net/manila?field.searchtext=DocImpact&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=12:51
tpsilvagouthamr: ah cool, it's right on manila's LP12:52
tpsilvagouthamr: thanks12:52
gouthamrtpsilva: you're welcome..12:52
*** chlong has quit IRC12:56
gansobswartz: ping12:57
*** dustins has joined #openstack-manila13:00
*** porrua has joined #openstack-manila13:11
*** chlong has joined #openstack-manila13:12
*** qeelee has joined #openstack-manila13:13
*** wangqun has quit IRC13:14
*** qeelee has quit IRC13:15
*** akerr has joined #openstack-manila13:21
*** timcl has joined #openstack-manila13:24
*** rraja has joined #openstack-manila13:26
*** nkrinner is now known as nkrinner_afk13:35
*** sandanar has quit IRC13:45
bswartzzhongjun_, ganso: pong13:46
bswartzsorry I was in a meeting this morning13:46
bswartzI'm out now13:46
gansobswartz: Hi Ben13:46
gansobswartz: I read your comment13:46
bswartzhttps://review.openstack.org/#/c/332267/5613:47
gansobswartz: are you suggesting adding a --disruptable API parameter?13:47
bswartzganso: well the driver interface could change later so it's not urgent to fix that13:47
bswartzIt just occurred to me that we don't need a bunch of different methods to check various migration capabitilies13:47
gansobswartz: indeed13:47
bswartzbecause you can pass all the requested capabilities down to 1 method and get back a yes or no answer13:48
gansobswartz: I was talking to goutham13:48
gansobswartz: we can combine them all in migration_check_compatibility13:48
gansobswartz: but you suggested something useful to signal the manager that the migration is going to be disruptive or not13:48
gansobswartz: goutham told me he can check that13:48
bswartzwell it's up to the user13:49
gouthamradministrator*13:49
bswartzif the user requests a nondisruptive migration, we should either give him a nondisruptive migration or fail13:49
bswartzif the user doesn't request one, then he shouldn't get one13:49
gansobswartz: but we have no use for that information currently. We previously had 1-phase/2-phase migration with the purpose of controlling that, while we always expect migration to be disruptive13:49
gansobswartz: yes, exactly how writable and preserve-metadata works13:49
gansobswartz: I just wanted to confirm with you because we raised this topic in midcycle, and we previously agreed we did not really feel the need of that parameter13:50
gansobswartz: so looks like now we changed our minds and we want the admin to say "I want a non-disruptive"... if it fails saying "driver cannot do non-disruptive" (and fallback obviously cannot as well), then admin can retry with "ok I want a disruptive"13:51
bswartzganso: do you remember why?13:51
bswartzI wonder if we're confusing the 2-phase vs. 1-phase migration debate with the non-disruptive question13:52
gansobswartz: I think it was because we always expected migration to be disruptive, while share-modify (aka retype) could be non-disruptive if it does not invoke migration13:52
bswartzor the issue of 2 share instances vs 1 share instance for driver-assisted migration13:52
gansobswartz: I believe we are not confusing with these other topics at this moment13:52
bswartzI feel strongly that we should always have 2 phase migration and 2 share instances no matter what happens internally13:52
gansobswartz: I changed the code to reflect that13:53
bswartzhowever if the migration is nondisruptive then the second phase might be a no-op13:53
gansobswartz: if it is non-disruptive, we could have 1-phase...13:53
*** eharney has joined #openstack-manila13:53
gansobswartz: but we removed that possibility13:53
openstackgerritAlexey Ovchinnikov proposed openstack/manila: [Do Not Merge] Generic driver ports test  https://review.openstack.org/35920913:53
bswartzright, we could, but for API consistency we shouldn't13:53
gansoaovchinnikov: #link https://review.openstack.org/359166 <== possible fix, it is zuul right now13:54
gansoaovchinnikov: it is *in zuul right now13:54
gansobswartz: yes13:55
gansobswartz: so, do we agree that we want a '--disruptive' parameter?13:55
bswartzit should be --non-disruptive, defaulting to false13:56
bswartzor maybe --nondisruptive13:56
gansobswartz: ok so the default is to be disruptive, and if admin strongly needs share to be migrated non-disruptively, then he specifies it explicitely13:57
gansobswartz: correct?13:57
bswartzyeah but it applies to other migration-like APIs just the same13:59
bswartzan end user could request a nondisruptive retype13:59
*** kaisers_ has joined #openstack-manila13:59
gansobswartz: yes, we had already agreed to that when we discussed share-retype/modify API. The default was going to be disruptive, according to that etherpad14:02
*** pcaruana has quit IRC14:02
zhongjun_bswartz: ping, In https://review.openstack.org/#/c/312321/14:03
bswartzI'm just pointing out that all of the options for migration should be common across all migration-like APIs14:03
zhongjun_bswartz: tbarron think we could use ipaddress.IPv6Network() and IPv4Network instead of our validation function. It means whether to allow host bits when specifying which networks can access a share14:03
zhongjun_    eg: 10.0.0.2/16 is invalid when we use IPv4Network. 10.0.0.2/16 is valid when we use our validation function14:03
bswartzzhongjun_: ah I'm glad you caught me before you went to sleep14:03
zhongjun_bswartz: :D14:03
*** kaisers_ has quit IRC14:04
gansobswartz: ok, I will make the changes. The disruptive API flag one will be newton-migration-improvements flag because it changes API, not the one you -1'ed14:04
bswartzganso: my -1 was about the LVM change not that suggestion14:04
*** tbarron|gone is now known as tbarron14:05
bswartzzhongjun_: why is that string invalid for  IPv4Network? it looks valid to me14:05
tbarronbswartz: it is ambiguous14:06
bswartzoh I see14:06
bswartzit should have been 10.0.0.0/1614:06
bswartzthe .2 is the problem14:06
zhongjun_bswartz: yes14:06
tbarron10.0.0.2/16 as an *access rule*, not as a host address and network spec14:06
bswartzyes14:06
bswartzwell then we have a bug and we can fix it14:06
tbarrondoes it mean 10.0.0.0/16 or 10.0.0.0/32?14:06
tbarronbswartz: +114:07
gouthamrtbarron: it should not...14:07
bswartztbarron: there's no way it means the second one14:07
bswartzit has to mean the first one, but it's incorrectly specified14:07
tbarronbswartz: not to you14:07
gouthamrbswartz: tested zhongjun_'s cases last night.. we fail at the driver..14:07
gouthamrbswartz: and if you added a bunch of rules, it makes reconciling very difficult..14:08
bswartzzhongjun_: I think we should use IPv4Network, it sounds like it does the right thing14:08
gouthamrso +1 for API check14:08
tbarronin any case there should be one way to specify an access rule and it should cover the number of bits left to right with no host bits14:08
tbarronuse /32 if you want exactly one host14:08
gouthamrusing /32 is still two hosts14:10
tbarronotherwise you can have multiple rules like 10.0.0.0/16, 10.0.0.2/16, 10.0.5.5/16 in one access list and they all mean the same thing (if that's the way we "have" to interpret it)14:10
zhongjun_bswartz: Is there have any reason we use the ourselves code to check the ip format?14:10
tbarronthe ipaddress module didn't used to exist in python214:10
bswartztbarron: that's a problem14:11
bswartztbarron: we can't drop support for py2.7 yet14:11
tbarronit does exist in python2.714:11
tbarronnot in 2.614:11
bswartzo_O14:11
tbarronthat's why we rolled our own code i hypothesize14:11
bswartztbarron: possible, but that sucks14:12
*** alyson_ has quit IRC14:13
tbarrongouthamr: /30 is two hosts, 4 addresses /31 2 addresses, /32 1 adedress14:13
tbarronanyways IMO we shouldn't roll our own IP validation code,.it's done in standard ways by a much larger community14:14
tbarronthe chances of doing ipv6 wrong are too high14:14
*** cknight has joined #openstack-manila14:15
tbarronthere is a standard module and we should use it14:15
*** pcaruana has joined #openstack-manila14:17
openstackgerritAlyson proposed openstack/manila: Validate EVS IP in Manila HNAS Driver  https://review.openstack.org/35922214:17
zhongjun_But how to deal with the python version. Is it a problem?14:18
bswartztbarron: /31 is invalid14:18
bswartzonly 0-30 and 32 are valid14:19
bswartz(for ipv4)14:19
zhongjun_Maybe we could save netutils.is_valid_ipv6 check in N version, change to IPv6Network and IPv4Nework in next O version.14:19
bswartzhonestly /30 is debatable too, /29 is the smallest that most people go14:19
*** aovchinnikov has quit IRC14:21
gouthamris python2.6 even supported? we run py27 and py3414:22
*** dsariel has joined #openstack-manila14:23
gouthamrSupport Python 2.6 was dropped in Juno14:24
gouthamrhttps://wiki.openstack.org/wiki/Python3#Python_2:_Python_2.6_support_dropped.2C_Python_2.7_only14:24
zhongjun_I didn't see python2.6 in Jenkins14:24
gouthamrso, we can bravely use the module tbarron proposed ?14:25
tbarronbswartz: /31 is not invalid as access list!!14:25
tbarronbswartz: it's not usable as a network with broadcast and gateway though14:25
rrajatbarron ganso gouthamr : can you look at https://review.openstack.org/#/c/343306/ and https://review.openstack.org/#/c/344948 ? the CIs for both manila and the dependent manila-client patch are passing now.14:28
gouthamrzhongjun_: to answer your question, i strongly think you can use the validation tbarron proposed in your ipv6 patch.. bswartz -2ed the patch from tbarron though..14:28
gouthamrrraja14:29
gouthamrsure14:29
*** sage___ has quit IRC14:30
tbarronmy patch was just for reference purposes, and perhps for revival in O14:30
rrajagouthamr: :)14:30
cknighttbarron: I completely agree we shouldn't be using any of our own IP address validation code.14:31
zhongjun_so, everyone agree with we need to use IPv4Network and IPv6Network function to check the ip format?14:31
*** timcl has quit IRC14:31
cknighttbarron: I would also ask whether we need a separate ipv6 access type, or whether the address type can be inferred from the value.14:32
*** sage has joined #openstack-manila14:32
bswartzzhongjun_: yes14:32
tbarronrraja: I see that it's all passing now - nice!  Will look whan I get out of a meeting in an hour or so14:32
zhongjun_cool, I will do it.14:32
rrajatbarron: sounds great.14:32
tbarroncknight: the module also has a ip_address method that works for both ipv4 and ipv614:32
cknighttbarron: Yes, so why do we need an ipv6 access type?14:33
bswartzwe should be careful about IPv614:33
bswartzit has NO test coverage and if we start supporting it it could introduce all kind of bugs14:34
bswartzI would want the test coverage first before we support ipv614:34
tbarroncknight: I agree but what you are suggesing was a more radical change :)14:34
cknightbswartz: Agreed, ipv6 isn't to be taken lightly.14:34
cknighttbarron: Not radical, imho. :-)14:34
tbarroncknight: not radical, but more churn against the review for ipv6 that has been proposed14:36
cknighttbarron: Well, if the the ipv6 type isn't needed, then the review should stop.  Done.14:37
cknighttbarron: I guess that is radical :-)14:37
gouthamrzhongjun_: have you tested this against any gate driver? https://review.openstack.org/#/c/312321/23/manila_tempest_tests/tests/api/test_rules.py14:47
zhongjun_gouthamr: I tested it in huawei driver14:48
gouthamrzhongjun_: hmmm, i can try testing it against the NetApp driver. but i think having one of the gate drivers running the tests would be beneficial.14:49
cknightgouthamr: s/beneficial/essential/14:49
zhongjun_gouthamr: I already run it in another patch14:49
gouthamrcknight: +114:49
zhongjun_https://review.openstack.org/35732014:50
gouthamri guess the argument for allowing ipv6 as another type of access rule is to allow drivers to make any changes if necessary14:50
gouthamrthough if all backends can support it, universally, then it's just another kind of access rule14:51
gouthamrip access rule14:51
zhongjun_cknight: Hi, I think the ipv4 and ipv6 are different format. If we add ipv6 access type, it will make user more clear14:51
cknightzhongjun_: Yes, they are a different format.  So the code can figure it out for itself.14:52
*** Yogi1 has joined #openstack-manila14:53
zhongjun_cknight: and make the driver easy to distinguish between the ipv4 and ipv614:53
cknightzhongjun_: We're here to make user's lives easier, not driver developers.14:53
gouthamrzhongjun_: fair point.. but cknight is suggesting making the change internally in manila14:53
gouthamrzhongjun_: but still maintain that it is an ip access rule.. rather than an ipv6 in the API..14:54
*** timcl has joined #openstack-manila14:55
cknightgouthamr, zhongjun_: I would be OK with ipv6 as a driver capability, since not all will support it initially, so the API could reject ipv6 rules for some shares.  But I don't think a new access type is warranted here.14:56
openstackgerritGoutham Pacha Ravi proposed openstack/manila: [DNM] Test IPv6 rules with all drivers  https://review.openstack.org/35926815:02
*** vbellur has quit IRC15:02
gouthamrzhongjun_: i see that your driver doesn't need any changes15:02
gouthamrzhongjun_:lets see how other drivers fare:  https://review.openstack.org/35926815:02
zhongjun_cknight: there are many capabilities in manila, It will be little wiered, We only have ipv6 capability, the other share types not needed(such as cert, ceph)15:02
zhongjun_ s/share types/access_types15:03
lpetrutHey guys, I've sent a chain of patches on the Windows SMB driver, fixing some access right related issues, as well as implementing the 'update_access' method. I'd be grateful if somebody could take a look: https://review.openstack.org/#/c/354855 https://review.openstack.org/#/c/354854 https://review.openstack.org/#/c/35485315:03
cknightzhongjun_: Those are for specific protocols where existing access types wouldn't work.  Someone needs to explain to me why 'ip' isn't good enough for both ipv4 and ipv6 addresses when existing libraries can easily handle both and distinguish between them.15:05
zhongjun_gouthamr: ok15:07
gouthamrzhongjun_: some drivers might fail on CIFS ipv6 tests.. which, i don't think make sense.. though i'm not an expert :)15:08
bswartzoh I see this discussion didn't end15:09
zhongjun_cknight: Only use ip to include ipv4 and ipv6 will be more easy for me15:09
bswartzpersonally I'd like to see IPv6 support across all manila and all the drivers15:10
bswartzI think I agree that "ip" can cover both because it's easy to disambiguate between them15:10
bswartzwhere you get into trouble is with URL-like strings that can include port numbers15:10
bswartzexport locations might need to take the URL-like IPv6 format with brackets15:11
bswartzhowever access rules should be easy15:11
bswartzthe main thing is proper test coverage before we claim support (and everything passing those tests)15:12
zhongjun_gouthamr: I still not use the CIFS ipv6 tests in huawei driver, it will be fail in huawei CI15:16
zhongjun_gouthamr: my driver changes for ipv6 in following link: https://review.openstack.org/#/c/357320/1/manila/share/drivers/huawei/v3/connection.py15:26
*** vbellur has joined #openstack-manila15:27
gouthamrzhongjun_: :( i see15:28
gouthamrzhongjun_: so the rule type is ipv6..15:28
gouthamrzhongjun_: many drivers check that before applying.. so, that test patch will not work on most drivers.15:29
zhongjun_gouthamr: yes, If we conbine ipv4 and ipv6, my driver doesn't need any changes15:29
zhongjun_combine15:30
gouthamrzhongjun_: yes..15:30
gouthamrzhongjun_: I suggest having a test patch with the access_type='ip', without all the validation code you added, to see if the positive tests you wrote work for all the gate drivers..15:32
zhongjun_gouthamr: yes, it will be better15:35
*** alyson_ has joined #openstack-manila15:47
*** kaisers_ has joined #openstack-manila15:48
openstackgerritAlyson proposed openstack/manila: Validate EVS IP in Manila HNAS Driver  https://review.openstack.org/35922215:50
*** kaisers_ has quit IRC15:53
*** pcaruana has quit IRC15:56
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix connectivity problem in Scenario job  https://review.openstack.org/35916615:59
openstackgerritzhongjun proposed openstack/manila: [DNM] Test IP(ipv4 and ipv6) rules with all drivers  https://review.openstack.org/35931616:08
*** pcaruana has joined #openstack-manila16:09
openstackgerritzhongjun proposed openstack/manila: [DNM] Test IP(ipv4 and ipv6) rules with all drivers  https://review.openstack.org/35931616:20
*** Yogi1 has quit IRC16:27
*** eharney has quit IRC16:35
*** Suyi has joined #openstack-manila16:36
*** rraja has quit IRC16:38
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix Share Migration improper behavior for drivers  https://review.openstack.org/33226716:56
*** mtanino has joined #openstack-manila16:57
bswartzgouthamr: ping16:59
gouthamrbswartz: pong16:59
bswartzahm ended17:00
gansogouthamr: oh yea, forgot about that keyerror17:00
* gouthamr walks over17:00
gansogouthamr: did you return an empty dict or did you not implement the method (thus it raised NotImplementedError)?17:05
gansogouthamr: I assume you returned an empty dict17:08
*** mtanin___ has joined #openstack-manila17:10
*** mtanino has quit IRC17:12
*** dsariel has quit IRC17:13
gouthamrganso: nope17:16
gansogouthamr: I was looking at the wrong code version17:17
gouthamrganso: i returned a dict without those keys.. lemme grab that from my logs17:17
gansogouthamr: I guess you do have 'total_progress' set17:22
gouthamrganso: yes i do...17:23
*** cfey_ has quit IRC17:23
*** cfey has joined #openstack-manila17:24
*** dsariel has joined #openstack-manila17:27
gouthamrganso: also, when a migration is not in progress, i get this message17:30
gouthamr $ manila migration-complete test17:30
gouthamrERROR: Invalid share: First migration phase of share 7228b35b-a541-4805-8c27-ced5f231d5d7 not completed yet.17:30
gansogouthamr: did you return True in migration_continue?17:31
*** rraja has joined #openstack-manila17:32
gouthamrganso: yeah; the task state was 'migration_success'17:32
gouthamri didn't specify 'notify'...17:33
*** lpetrut has quit IRC17:33
gouthamrganso: which will go away.. but either case, when the task state is something else, guess we should use an appropriate error message17:33
gansogouthamr: notify functionality has been removed17:34
gansogouthamr: wait17:34
gansogouthamr: lol17:34
gouthamrganso: yes, not for me. i'm still on the bugfix patch..17:34
gouthamr:P17:34
gansogouthamr: the task_state was already migration_success?17:34
gouthamrganso: yeah.. the message is confusing.. even with notify gone, if someone uses that command after a migration has been completed, they will get that error message..17:35
gansogouthamr: I can add a different message for that task_state17:35
gansogouthamr: and possibly for migration_error and None17:35
gouthamrganso: yes.. icing on the cake..17:35
gouthamrganso: btw, my dictionary is formatted like this {'phase': 'replicating', 'state': 'healthy', 'estimated_completion_time': None, 'details': 'Volume move job monitoring transfer of data. ', 'total_progress': None}17:37
gouthamrganso: sigh, see a bug. i should set total_progress to 0 if None.17:37
gansogouthamr: exactly17:37
*** kaisers_ has joined #openstack-manila17:37
gansogouthamr: I were going to hit the check I am adding right now17:37
gansogouthamr: lol17:37
gouthamrganso: still, don't expect 'current_file_progress'. :)17:38
gouthamror path.17:38
gansogouthamr: ya17:38
*** eharney has joined #openstack-manila17:40
*** kaisers_ has quit IRC17:42
*** aovchinnikov has joined #openstack-manila17:48
*** zhugaoxiao has joined #openstack-manila17:53
*** Administrator__ has quit IRC17:55
*** eharney has quit IRC17:56
*** rraja has quit IRC18:02
*** eharney has joined #openstack-manila18:08
openstackgerritAlyson proposed openstack/manila: Fix HNAS Driver accepting invalid entries as EVS IP  https://review.openstack.org/35922218:08
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix Share Migration improper behavior for drivers  https://review.openstack.org/33226718:22
gouthamrganso: https://review.openstack.org/#/c/332267/57..58/manila/api/views/shares.py <-- those keys should always be returned18:28
*** lpetrut has joined #openstack-manila18:33
gansogouthamr: why?18:40
gouthamrganso: API sanity.. you don't want to selectively return different keys.. the response schema shouldn't change based off the situation18:41
gouthamrganso: the client can figure out that the current_file_in_progress being None means that it can't have that information..18:41
gansogouthamr: ok, then I believe it is best to have only 'total_progress'18:42
gansogouthamr: as we discussed the other day, we don't know what fields all drivers will be able to provide18:43
*** timcl has quit IRC18:53
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix Share Migration improper behavior for drivers  https://review.openstack.org/33226718:54
gansogouthamr: ^18:55
gouthamrganso: thanks18:55
gansogouthamr: thank you for the feedback :)18:56
*** AJaeger has joined #openstack-manila18:57
AJaegerbswartz, could you review https://review.openstack.org/357924  ,please? That allows to move forward with api-ref work18:57
*** dsariel has quit IRC19:02
AJaegerthanks, bswartz !19:06
*** timcl has joined #openstack-manila19:11
*** AJaeger has left #openstack-manila19:15
*** pcaruana has quit IRC19:20
*** kaisers_ has joined #openstack-manila19:26
*** kaisers_ has quit IRC19:30
openstackgerritMerged openstack/manila: Get ready for os-api-ref sphinx theme change  https://review.openstack.org/35792419:33
*** aovchinnikov has quit IRC19:35
*** lpetrut has quit IRC20:03
*** porrua has quit IRC20:04
*** akerr has quit IRC20:09
gouthamrganso: here?20:11
gansogouthamr: yes20:11
gouthamrganso: 2 quick questions for you20:12
gansogouthamr: go ahead20:12
gouthamrganso: so, if phase1 is done, why can't you use get-progress/20:12
gansogouthamr: because the jobs running in storage backends from where the progress is obtained is most probably finished20:13
gansogouthamr: but I see the point you raise... that is should be total_progress = 100 in that case20:14
*** alkhodos has quit IRC20:14
gouthamrganso: yes20:18
gouthamrganso: maybe make the call and drivers should support it?20:19
gouthamrganso: i don't see why they can't..20:19
gansogouthamr: yea, they may just return 'total_progress' = 100 themselves20:19
gouthamrganso: +120:22
gouthamrganso: another question.. is there a way to estimate the time remaining for data copy based off your current progress?20:23
gouthamri was just wondering if it would be helpful to have two things in the API response.. to save administrators from becoming impatient (in bswartz's words)20:23
gansogouthamr: HDS storage can, and with a reasonable amount of work we can support it in fallback too20:25
gouthamrganso: i presume drivers can give you that, or return 'unknown'20:25
gouthamrala windows software :P20:25
gansogouthamr: windows software usually lie, it would be better if they returned 'unknown' lol20:26
gouthamrtotal progress: 0% estimated time remaining: unknown     msg: go take a walk20:26
gansogouthamr: I've seen: estimated time remaining: 2 hours. <5 minutes later>. Estimated time remaining: 10 minutes20:27
gouthamrganso: yeah, you just got upgraded to first class.20:27
gouthamr:P20:28
gansogouthamr: or worse, stays at 'estimated time remaining: 1 minute' to keep you close by while it takes half an hour20:28
gouthamrganso: that'd be a pain.. but it's an 'estimate' and we have the license to be woefully off mark in cases20:29
*** rhefner has quit IRC20:31
*** rhefner has joined #openstack-manila20:33
gansogouthamr: yes20:33
gansogouthamr: still, I would rather return only 'total_progress' right now and work on that once we have more drivers on board20:34
gouthamrganso: sure. makes sense20:34
openstackgerritAlyson proposed openstack/manila: Fix HNAS Driver accepting invalid entries as EVS IP  https://review.openstack.org/35922220:41
*** rhefner has quit IRC20:43
gansogouthamr: I'll update the patch later tonight20:45
gansogouthamr: with the progress change for the phase1_done20:46
*** rhefner has joined #openstack-manila20:48
*** cknight has quit IRC20:50
*** vbellur has quit IRC20:50
gouthamrganso: sure.. no rush. the latest patch LGTM20:51
*** timcl has quit IRC20:56
*** gouthamr has quit IRC20:58
*** kaisers_ has joined #openstack-manila21:15
*** kaisers_ has quit IRC21:20
*** eharney has quit IRC21:27
*** gouthamr has joined #openstack-manila21:34
openstackgerritMerged openstack/manila-image-elements: Move other-requirements.txt to bindep.txt  https://review.openstack.org/35492421:42
*** lpetrut has joined #openstack-manila22:24
*** lpetrut has quit IRC22:28
*** xyang1 has quit IRC22:36
*** vbellur has joined #openstack-manila22:41
*** chlong has quit IRC23:03
*** alyson_ has quit IRC23:03
openstackgerritRodrigo Barbieri proposed openstack/manila: Share migration Newton improvements  https://review.openstack.org/32843123:49
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix Share Migration improper behavior for drivers  https://review.openstack.org/33226723:49
openstackgerritRodrigo Barbieri proposed openstack/manila: Add share type change to Share Migration  https://review.openstack.org/34514223:49

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