Wednesday, 2016-03-23

*** yangyapeng has quit IRC00:06
*** yangyapeng has joined #openstack-manila00:06
*** baojg has joined #openstack-manila00:07
*** baojg has quit IRC00:08
*** zhongjun has quit IRC00:11
*** yangyapeng has quit IRC00:11
*** zhongjun has joined #openstack-manila00:12
*** krotscheck has joined #openstack-manila00:42
*** erlon has quit IRC00:47
*** a_ta has joined #openstack-manila00:50
*** a_ta has quit IRC00:56
*** yangyapeng has joined #openstack-manila01:09
*** yangyapeng has quit IRC01:14
*** mtanino has joined #openstack-manila01:23
*** yangyapeng has joined #openstack-manila01:28
*** swamireddy1 has joined #openstack-manila01:31
*** jasonsb has joined #openstack-manila01:46
*** baojg has joined #openstack-manila01:46
*** swamireddy1 has quit IRC01:49
*** gouthamr has joined #openstack-manila01:52
*** jasonsb has quit IRC01:54
*** gouthamr_ has quit IRC01:55
*** tpsilva has quit IRC01:57
*** houming has joined #openstack-manila02:15
*** qeelee has joined #openstack-manila02:16
*** akshai_ has quit IRC02:32
*** akshai has joined #openstack-manila02:40
*** baojg has quit IRC02:48
*** Ben__ has joined #openstack-manila02:49
*** baojg has joined #openstack-manila02:50
*** gouthamr has quit IRC03:10
Ben__I try to use glusterfs volume on Manila but keep failing. I mount it on the ubuntu 14.04 host with nfs v3 and the host is set through Devstack .The m-shr.log shows [ Error encountered during initialization of driver 'GlusterfsShareDriver \  DriverNotInitialized: Share driver 'GlusterfsShareDriver' not initialized. ]. Anyone has idea about this?03:17
*** cknight has joined #openstack-manila03:42
*** qeelee has quit IRC03:51
*** swamireddy1 has joined #openstack-manila04:02
*** jasonsb has joined #openstack-manila04:22
*** cknight has quit IRC04:28
*** qeelee has joined #openstack-manila04:58
*** akshai has quit IRC05:07
*** qeelee has quit IRC05:11
*** qeelee has joined #openstack-manila05:17
openstackgerritFelix Ma proposed openstack/manila: Fix wrong indent bug in _get_private_router  https://review.openstack.org/29618305:29
*** Ben__ has quit IRC05:33
*** sgotliv has joined #openstack-manila05:34
*** lpetrut has joined #openstack-manila05:37
*** qeelee has quit IRC05:54
*** qeelee has joined #openstack-manila05:57
*** jasonsb has quit IRC06:06
*** lpetrut has quit IRC06:15
*** nkrinner has joined #openstack-manila06:17
*** qeelee has quit IRC06:21
*** lpetrut has joined #openstack-manila06:35
*** lpetrut has quit IRC06:41
*** sgotliv has quit IRC06:42
*** sgotliv has joined #openstack-manila06:42
openstackgerritdaiki kato proposed openstack/manila: Fix typos  https://review.openstack.org/29621506:55
*** qeelee has joined #openstack-manila07:22
*** qeelee has quit IRC07:32
*** furlongm_ is now known as furlongm07:36
*** sgotliv has quit IRC07:40
*** a_ta has joined #openstack-manila08:05
*** a_ta has quit IRC08:09
*** nkrinner has quit IRC08:12
*** nkrinner has joined #openstack-manila08:17
*** aovchinnikov has joined #openstack-manila08:21
*** permalac has joined #openstack-manila08:43
*** qeelee has joined #openstack-manila08:44
openstackgerritMarc Koderer proposed openstack/manila: Capitalize global var for clients  https://review.openstack.org/29629209:01
*** openstackgerrit has quit IRC09:03
*** openstackgerrit has joined #openstack-manila09:04
*** sgotliv has joined #openstack-manila09:08
*** houming has quit IRC09:12
*** houming has joined #openstack-manila09:14
*** qeelee has quit IRC09:49
*** lpetrut has joined #openstack-manila10:00
*** baojg has quit IRC10:06
*** yangyapeng has quit IRC10:13
*** tpsilva has joined #openstack-manila10:26
*** qeelee has joined #openstack-manila10:32
openstackgerritMarc Koderer proposed openstack/manila: Increase logging for driver initialization  https://review.openstack.org/29636710:37
*** baojg has joined #openstack-manila10:42
*** furlongm_ has joined #openstack-manila10:44
*** furlongm has quit IRC10:45
*** baojg has quit IRC10:47
*** furlongm has joined #openstack-manila10:55
*** furlongm_ has quit IRC10:55
*** ganso has joined #openstack-manila10:58
*** a_ta has joined #openstack-manila11:10
*** a_ta has quit IRC11:15
*** zhongjun has quit IRC11:25
*** zhongjun has joined #openstack-manila11:26
*** ociuhandu has quit IRC11:29
*** rraja has joined #openstack-manila11:40
*** yangyapeng has joined #openstack-manila11:42
mkodererganso: ping11:51
gansomkoderer: pong11:51
mkodererganso: I have some questions regarding the data service if you have a sec11:51
gansomkoderer: sure ;)11:51
mkodererganso: how do you ensure that you don't have concurrent write access during the copy?11:52
gansomkoderer: wait, are you talking about migration or this new patch I uploaded yesterday? https://review.openstack.org/29583611:53
mkodererganso: the new patch basically11:53
mkodererbut can be also valid for mirgation11:53
gansomkoderer: in migration I change the access rules to read only, so any client cannot perform any addional writes while it is migrating11:54
mkodererganso: ok that's fine11:54
gansomkoderer: in the new patch I have not done that yet11:54
mkodererganso: ok I see11:54
gansomkoderer: but it will be the same thing11:55
mkodererganso: so you change the access rules automatically?11:56
mkodererI guess this could cause failures in application runnding in the cloud11:56
gansomkoderer: https://github.com/openstack/manila/blob/master/manila/share/manager.py#L67911:57
gansomkoderer: what failures?11:57
mkodererganso: e.g. you run a database on a share fs and by setting it to read/only it could crash11:57
mkodererganso: ok I see.. we need to make sure that this aspect is well documented11:58
mkodererI will ask our ops team about some real-live expriences for this topic11:58
gansomkoderer: the only way so far to work around that is to perform migration through replication11:58
*** david-lyle_ has joined #openstack-manila11:58
gansomkoderer: but then it needs to use a driver that implements replication11:59
*** john_bar has joined #openstack-manila11:59
gansomkoderer: and implement optimized migration using such driver11:59
mkodererganso: ok I understand it know11:59
*** ociuhandu has joined #openstack-manila11:59
mkodererganso: I will try to test that feautre in our lab12:00
gansomkoderer: great! :D12:00
*** david-lyle has quit IRC12:00
*** yangyapeng has quit IRC12:01
mkodererganso: IMHO manila need to have a spec process.. with that I could also include our ops people during design phase12:01
*** yangyapeng has joined #openstack-manila12:02
gansomkoderer: I agree, there has been discussion a while back whether we should or not have it, we agreed that we should not, but now I think we should12:02
gansomkoderer: the main problem raised was that after spec is approved, the feature ends up implemented differently due to necessary changes found during coding, and then the spec is never updated again12:03
*** yangyape_ has joined #openstack-manila12:04
*** lpetrut has quit IRC12:04
mkodererganso: yeah that's also correct.. but a design document can be read from ppl that aren't devs and I have some folks that would love to review manila specs12:05
gansomkoderer: we are in the best moment to debate that again in our weekly meeting12:05
mkodererganso: correct12:06
*** yangyapeng has quit IRC12:07
gansomkoderer: btw, I just remembered why I have not implemented the changing of access rules to read only in the new patch12:07
gansomkoderer: I coded this patch before feature freeze so I had to review some details now12:08
gansomkoderer: the reason is that drivers are going to be invoking those methods in the new patch12:08
gansomkoderer: and the drivers themselves are able to change rules to read only12:08
gansomkoderer: so the helper class does not need to do it12:09
gansomkoderer: so let's say the driver wants to implement "create share from snapshot" using the data helper12:09
gansomkoderer: it will first change rules to read only (or in this case won't be needed because it is a snapshot), and then call the helper to copy data from the snapshot to the new share12:10
*** houming has quit IRC12:17
*** lpetrut has joined #openstack-manila12:19
gansomkoderer: I replied to your comment in https://review.openstack.org/29583612:20
mkodererganso: ok I see .. can you add a check before coping? or a force option.. I just hesitant becuase manila could potential corrupt a share data which would be a worst case12:21
mkodererganso: ah btw if you have time to review some trivial fixes: https://review.openstack.org/#/c/296292/ and https://review.openstack.org/#/c/296367/12:23
openstackgerritMarc Koderer proposed openstack/manila: Increase logging for driver initialization  https://review.openstack.org/29636712:25
gansomkoderer: sure12:27
mkodererganso: forget about https://review.openstack.org/296367 needed to push a new patchset12:28
gansomkoderer: ok, I will keep an eye on it12:28
*** qeelee has quit IRC12:31
*** ociuhandu has quit IRC12:34
*** ociuhandu has joined #openstack-manila12:35
openstackgerritMarc Koderer proposed openstack/manila: Increase logging for driver initialization  https://review.openstack.org/29636712:37
*** qeelee has joined #openstack-manila12:39
*** a_ta has joined #openstack-manila12:40
*** a_ta has quit IRC12:45
*** lpetrut has quit IRC12:46
*** lpetrut has joined #openstack-manila12:46
*** baojg has joined #openstack-manila12:50
*** a_ta has joined #openstack-manila12:51
*** ociuhandu has quit IRC12:52
*** ociuhandu has joined #openstack-manila12:53
*** mtanino has quit IRC12:53
*** a_ta has quit IRC12:56
*** porrua has joined #openstack-manila12:57
*** akerr has joined #openstack-manila13:02
*** lpetrut has quit IRC13:03
*** david-lyle_ is now known as david-lyle13:06
*** akerr has quit IRC13:09
openstackgerritMarc Koderer proposed openstack/manila: Increase logging for driver initialization  https://review.openstack.org/29636713:16
openstackgerritMerged openstack/manila: Capitalize global var for clients  https://review.openstack.org/29629213:17
openstackgerritMarc Koderer proposed openstack/manila: Add binding_profile option for backends  https://review.openstack.org/28403413:24
openstackgerritMarc Koderer proposed openstack/manila: Add neutron driver for binding  https://review.openstack.org/28349413:24
bswartzcsaba: ping13:27
bswartzcsaba rraja: have you noticed that glusterfs CI has been voting UNSTABLE for a while now?13:28
*** qeelee has quit IRC13:28
rrajabswartz: yes. thanks! i'll fix that soon.13:29
bswartzdo you know the cause?13:29
bswartzI'm curious because you don't see UNSTABLE that often13:29
bswartzalthough UNSTABLE is definitely better than FAILURE13:30
rrajabswartz: it's happening while copying the logs to another location at the end of run.13:30
bswartzinteresting13:30
mkodererbswartz: had a short discussion with ganso about manila spec process.. we agreed that it would be beneficial for manila to have it13:31
*** absubram has joined #openstack-manila13:32
mkodererI have some ops folks that would like to give feedback during design phase13:32
*** absubram_ has joined #openstack-manila13:33
openstackgerritRodrigo Barbieri proposed openstack/manila: Add Driver Data Service Helper  https://review.openstack.org/29583613:35
*** absubram has quit IRC13:37
*** absubram_ is now known as absubram13:37
mkoderertbarron: ha, unbelivable how tricky it can be to add two log lines :)13:40
tbarronmkoderer: well, it's just a thought.  I don't have strong feelings one way or another, but I know the manila codebase is still fairly clean and consistent.13:41
tbarronHas anyone looked - or is anyone looking - at how manila behaves if you configure two nodes to actively have the same host name relative to AMPQ?13:42
tbarronAs opposed to using something like pacemaker to arbitrate.13:42
mkoderertbarron: you mean two manila-share instances?13:42
tbarronmkoderer: yes, that's what I meant.13:42
*** timcl has joined #openstack-manila13:43
tbarronI'm asking the analogous question to what has been discussed for cinder.13:43
tbarronI think I know the answer, but am checking with my betters to make sure I give the right report back :-)13:43
mkoderertbarron: I have it on m list of thing that I want to test13:44
tbarronmkoderer: so are you planning to test for races, etc?13:44
mkoderertbarron: yes but I have a long todo list :)13:44
*** mtanino has joined #openstack-manila13:44
tbarronmkoderer: migrate?13:44
tbarronmkoderer: replication?13:45
mkoderertbarron: maybe migrate.. but no replication13:45
*** porrua has quit IRC13:46
tbarronso unless corrected I will report that manila-share is essentially in the same position as cinder-volume:13:46
tbarronone may be able to get away with such a configuration but it has not been vetted.13:46
*** Yogi1 has joined #openstack-manila13:46
mkodererthe question is how are the amqp messages distributed13:47
tbarronThere are likely races and potential for data corruption, though the chance of the latter is likely less with shares than volumes b/c filesystems generally know how to handle concurrent access.13:47
mkoderertbarron: so we would need a stress test and a test env13:48
bswartzmkoderer: each release cycle we've voted on doing spec vs not doing specs, and each time the vote fails13:49
bswartzjust to be clear, we do expect people to write functional specs and link them from their blueprints13:49
bswartzhowever we haven't yet felt the need to create a manila-specs repo and manage the specs process through gerrit13:49
*** swamireddy1 has quit IRC13:49
gansovponomaryov, bswartz: Could you please take a look at this backport patch? https://review.openstack.org/#/c/294575/13:49
vponomaryovganso: I set +1 long time ago, there is no +2 power for common manila-core group13:50
bswartzthe concern is always that specs are constantly out of date, so while they add value for discussion, they should not be formalized13:51
gansovponomaryov: no? =(13:51
gansovponomaryov: who can +2 to backport this?13:51
bswartzganso vponomaryov: yeah the gerrit acls have a problem13:51
vponomaryovganso: bswartz can and release team13:51
bswartzI can +2A things but nobody else can13:51
bswartzneed to talk to stable PTL about getting the ACLs corrected13:52
*** cknight has joined #openstack-manila13:53
*** dustins has joined #openstack-manila13:53
bswartzvponomaryov ganso: there is no bug in the commit message -- is liberty gate broken?13:53
gansobswartz: yes13:53
gansobswartz: thanks13:54
zhongjunbswartz: hi :)   Does the Netapp driver or manila has a plan to implement the feature about "Restrict the number of files in the share"?13:58
bswartzzhongjun: I haven't seen that feature suggested anywhere13:59
bswartznot all backends could support that13:59
zhongjunbswartz: Do you know which backend is interested in this?14:01
bswartzzhongjun: no I don't -- where is the feature proposed?14:01
*** absubram has quit IRC14:02
zhongjunbswartz: Does the Netapp could support this if it is needed?14:02
mkoderercknight: can I get your feedback on https://review.openstack.org/#/c/274136/14:03
cknightmkoderer: sure14:04
zhongjunThis feature enables you to restrict the number of files in the share.14:05
zhongjunIf the file quantity quota exceeds the quota, the system immediately14:05
zhongjunforbids write operations and prevents users from using extra files.14:05
*** akerr has joined #openstack-manila14:05
*** a_ta has joined #openstack-manila14:06
bswartzcknight: do you know if the qtree APIs on cDOT support file limits as well as byte limits? I know that 7-mode does both14:06
zhongjunbswartz: I just put it on the https://blueprints.launchpad.net/manila/+spec/file-quantity-quota-in-share, but not sure it is suitable for all backend.14:06
bswartzzhongjun: It's an interesting idea but I'm not sure if it has enough value to implement it -- especially if it's going to only work on a few backends14:07
bswartzzhongjun: are there users out there who really need this?14:07
cknightbswartz: I thought so.  I will confirm.14:07
mkodererbswartz: maybe we need it.. let me ask my folks tomorrow14:07
bswartzmkoderer: you need file limits in share?14:08
cknightbswartz: Yes.  You can optionally specify the following additional attributes for the quota policy rule:14:08
cknight•User mapping14:08
cknight•Hard disk limit14:08
cknight•Hard file limit14:08
cknight•Threshold for disk limit14:08
cknight•Soft disk limit14:08
cknight•Soft file limit14:08
bswartzmkoderer: what is the point of that? is the default limit too low? too high?14:08
*** openstack has joined #openstack-manila14:24
bswartzzhongjun: tomorrow we'll be discussing topics for newton (austin) design summit14:25
bswartzzhongjun: if we have time we could also cover this topic, because we need convincing use cases before we can say the feature is something we want14:26
zhongjunbswartz: just add use case first :)14:27
bswartzthx zhongjun14:28
zhongjunthx you bswartz ;)14:29
cknightvponomaryov: ping14:30
vponomaryovcknight: pong14:31
cknightvponomaryov: The Manila service names in Keystone are manila and manilav2.  But aren't the endpoint names share and sharev2?  That's what devstack does.14:31
vponomaryovyes14:33
vponomaryovwhy?14:33
cknightvponomaryov: The quick start guide under review sets both service & endpoint names to manila and manilav2.  I need to know if that is correct.  https://review.openstack.org/#/c/274136/3..4/doc/source/adminref/quick_start.rst14:33
vponomaryovcknight: manilaclient has dependency on "sharev2" value14:36
vponomaryovcknight: so, service type should stay "share" and "sharev2"14:36
cknightvponomaryov: OK, thanks, I'll -1 the review (again).14:37
*** vbellur has quit IRC14:39
cknightmkoderer: ^^14:40
zhongjunvponomaryov: Do you know what is the original reason, when we delete a share,14:43
zhongjunwe just change the status to "deleted" in db table, Not deleted the row in the db table.14:43
vponomaryovzhongjun: it is "soft" deletion14:44
vponomaryovzhongjun: common approach in OpenStack14:44
openstackgerritMarc Koderer proposed openstack/manila: Fix quick start guide to new auth mechanism  https://review.openstack.org/29649814:45
zhongjunvponomaryov: What can be used with this "deleted" value.14:46
*** david-lyle_ is now known as david-lyle14:47
mkodererdgonzalez: can you have a look at cknight comment.. I was so sure that it worked.. (only when you have time)14:47
zhongjunvponomaryov: Does it will cause the database too big?14:47
vponomaryovzhongjun: yes, it makes table grow14:48
*** akshai has joined #openstack-manila14:48
dgonzalezmkoderer: i will have a look at it14:49
vponomaryovzhongjun: and I am aware about such concern for operators that are forced to write scripts with DB sleanups14:50
zhongjunvponomaryov: Does this way have the advantage of this "deleted" data in db?14:50
vponomaryovzhongjun: I can think about only two reasons: 1) keep consistency of all foreign keys, that implement some kind of matrix where lots of elements refer to each other14:51
vponomaryovzhongjun: 2) debug reasons14:52
bswartz3) soft deletes are way faster than hard deletes14:53
vponomaryovzhongjun: I guess there should be such discussion in openstack mailing-list or some summits notes14:53
*** baojg has quit IRC15:03
zhongjunvponomaryov, bswartz: thx, This is one of the original problem, Maybe before experienced many discussions in OpenStack.I try to find it. Maybe we could open discuss it in mailling-list.15:03
*** vbellur has joined #openstack-manila15:03
bswartzzhongjun: you're proposing switching away from soft deletes to something else?15:04
bswartzzhongjun: that's a discussion that's larger than just Manila -- we inherited soft deletes from cinder and it's a widely-used technique in the community15:04
*** absubram has joined #openstack-manila15:05
zhongjunbswartz: Oh, that is the real reason.15:06
zhongjunbswartz: I just want to find the reason, why the choose this, and explain to other people.15:07
zhongjuns/the/they15:07
bswartzoh15:07
bswartzyou'll have to look back very far in mail list archives15:07
bswartzthat decision was made years ago15:07
bswartzbut I'm sure there's a record of the discussion with an explanation of the benefits15:07
zhongjunOh, that is must have the evidence. I believe it will be find.15:10
*** openstackstatus has joined #openstack-manila15:12
*** ChanServ sets mode: +v openstackstatus15:12
*** lpetrut has joined #openstack-manila15:12
*** sgotliv has quit IRC15:17
*** adrianofr_ has joined #openstack-manila15:52
*** lpetrut has quit IRC15:59
*** lpetrut has joined #openstack-manila16:03
*** erlon has joined #openstack-manila16:08
*** sage has quit IRC16:18
*** sage has joined #openstack-manila16:19
*** timcl has quit IRC16:19
*** jasonsb has joined #openstack-manila16:30
*** david-lyle has quit IRC16:33
*** david-lyle has joined #openstack-manila16:33
*** jasonsb has quit IRC16:38
*** jasonsb has joined #openstack-manila16:39
openstackgerritThomas Bechtold proposed openstack/manila: Remove PyMySQL and psycopg2 from test-requirements.txt  https://review.openstack.org/29660016:40
*** timcl has joined #openstack-manila16:47
*** vbellur has quit IRC16:47
*** lpetrut has quit IRC16:49
*** gouthamr has quit IRC16:53
ameadewhy are we still ignoring test cleanup errors in the gate?16:54
ameadebswartz, vponomaryov ^^?16:54
bswartzameade: because the gate tests wouldn't pass otherwise16:56
ameadeshould we not fix that?16:56
bswartzameade: yes we should16:56
vponomaryovameade: it is designed for generic driver16:57
ameadeour CI is broken due to a patch that caused cleanup errors16:57
vponomaryovameade: and instability of its deps16:57
ameademm16:57
vponomaryovameade: all other driverss dhould not ignore cleanup errors16:57
bswartzwe assume, but we do not know, that generic driver fails sometimes due to slowness of nova, cinder, and neutron16:57
vponomaryovameade: let me guess, cleanup of replicas broke somethng?16:58
ameadethis patch https://review.openstack.org/#/c/294269/16:58
smcginnisWho you calling slow?16:58
smcginnis:)16:58
vponomaryovbig brother is watching us ))17:00
bswartzit's the interactions between nova and cinder17:00
*** lpetrut has joined #openstack-manila17:01
* bswartz notes that smcginnis has an IRC pounce for "cinder" and we must use a different name if we want to disparage them in our channel17:01
bswartzlol17:01
gansoameade: how did it break?17:01
smcginnisHaha17:01
vponomaryovbswartz: "that slow service"?17:02
*** a_ta has quit IRC17:03
*** a_ta has joined #openstack-manila17:03
*** a_ta has quit IRC17:03
*** a_ta has joined #openstack-manila17:04
vponomaryovganso: test stopped cleaning up all created shares and share type cannot be removed17:05
vponomaryovganso: as "in use"17:05
akerrganso: I think I found a bug in one of your patches that is causing our CI to fail constantly with cleanup errors: https://review.openstack.org/#/c/294269/4/manila_tempest_tests/tests/api/admin/test_share_manage.py  The assertRaises call will create a share in error status but never cleans it up, then when tempest goes to clean up the share type we get a 400 error because the share type is still in use17:06
gansoakerr: it is expected to not remove share in assertRaises because manage reuses share if it is managed again with proper parameters17:06
gansoakerr: but I think I see where the problem is17:06
*** sedwards has joined #openstack-manila17:07
gansoakerr, vponomaryov: indeed it is not removing the share type... I mistakenly removed that, now looking closer, it was the share type that was being removed, not the share17:07
vponomaryovganso: "manage reuses share if it is managed" where did you hear that?17:07
*** rhagarty has quit IRC17:07
gansovponomaryov:  https://github.com/openstack/manila/blob/master/manila/share/api.py#L53717:08
*** rhagarty has joined #openstack-manila17:08
gansoakerr: possibly line 174 in original code of that change should not have been removed17:09
vponomaryovganso: share type ID is used as filter17:09
*** jasonsb has quit IRC17:09
vponomaryovganso: so, when you use new share type, you create new share17:09
vponomaryovganso; in this test in anycase17:09
*** gouthamr has joined #openstack-manila17:10
gansovponomaryov: oh I see, indeed17:10
gansoakerr: what does your CI do differently that fails?17:12
*** porrua has joined #openstack-manila17:12
gansoakerr: manage operation should not create share on backend17:12
akerrganso: we don't skip cleanup failures17:12
*** martyturner has joined #openstack-manila17:13
vponomaryovganso: generic driver skips cleanup errors, all other drivers just were not considered merging this commit17:14
*** swamireddy1 has joined #openstack-manila17:16
gansovponomaryov: only netapp failed17:16
gansovponomaryov: due to that change17:16
vponomaryovganso: ZFsonLinux does not have support for "manage" yet17:16
vponomaryovganso: it is for example17:16
vponomaryovganso: so, broken test is just skipped there17:16
*** sedwards has quit IRC17:19
akerrganso: the problem isn't that it makes the share on the backend, its that a DB entry for the share is created in error status and then never cleaned up, so manila says the share type is still in use17:19
bswartzare we cleaning up a whole share type in the test cleanup?17:20
bswartzif so, shouldn't we delete all the shares of that type first?17:20
gouthamrbswartz: logically, the share must be deleted first..17:21
vponomaryovbswartz: this is the reason of broken CI for NetApp No-ss job17:23
bswartzwhat I'm trying to say is that if cleanups are failing because stuff still exists, then the cleanups should be more aggressive about cleaning stuff17:23
akerrvponomaryov: is there a manage_share function in base.py that adds cleanup automatically that we could call in the assertRaises() instead of invoking the share_client directly?17:24
bswartzcleanup operations should recursively delete everything they need to to ensure the object in question is actually cleaned17:24
vponomaryovakerr: not yet17:24
bswartzotherwise cleanups will continue to fail17:24
vponomaryovakerr: but it is righttime to add such17:24
akerrvponomaryov: ok, that seems like the right way to handle it17:24
vponomaryovbswartz: tests can break any cleanup logic, it is exactly this case17:24
gansovponomaryov: curiously, default setting for supressing tests is False, but CI script says default is True... I believed my CI was not supressing errors, but it is =(17:25
*** swamireddy1 has quit IRC17:34
*** a_ta has quit IRC17:34
*** a_ta has joined #openstack-manila17:34
akerrhmm this won't be that straightforward to fix.  Since it raises a 409 exception in the client layer we can't easily grab the share_id from the create call... I guess we'd need to do a search on shares of type x in error status and delete those?17:37
*** a_ta has quit IRC17:39
vponomaryovakerr: if we cannot receive it then it should not be created17:40
akerrvponomaryov: I just mean that the exception in python will change the control flow of the code prior to the variable being set17:41
vponomaryovakerr: I don't opposite I say design is wrong, only 201 (at least, 200 and 202) code should be returned after successfully created resource17:43
vponomaryovakerr: if we get 409, then resource should not be created17:43
akerrvponomaryov: even a DB entry shouldn't be created?17:43
vponomaryovakerr: Db is the only thing Manila is aware about17:44
vponomaryovakerr: especially API17:44
vponomaryovakerr: so, creation of DB record should be after check for that error17:44
vponomaryovakerr: we get in broken test17:44
akerrvponomaryov: ok17:45
akerrvponomaryov: makes sense17:45
*** lpetrut has quit IRC17:47
*** lpetrut has joined #openstack-manila17:47
gansovponomaryov: validation is in the scheduler, DB record is created before sending to the scheduler17:48
vponomaryovganso: you say it so it cannot be changed17:49
vponomaryovganso: ))17:49
gansovponomaryov: I am checking if it is not necessary to send share info to scheduler17:49
vponomaryovganso: all checks should be performed only before creation of DB record that will mean we return 20117:50
gansovponomaryov: if not necessary, then scheduler can validate without needing the share created, and share can be created later17:50
gansovponomaryov: indeed it is not necessary, it just needs the host17:50
vponomaryovakerr: is there launchpad bug for it?17:51
*** lpetrut has quit IRC17:52
akerrvponomaryov: not yet, ameade and i are verifying that we can repro manually17:52
vponomaryovbswartz: looks like we have candidate for RC2, wrong behaviour of API service using "manage" command17:53
bswartzclient or server project?17:53
vponomaryovserver17:53
akerrvponomaryov: verified, we get a db entry17:53
bswartztag bug with "mitaka-rc-potential" and let's hurry and get the fix into newton17:54
bswartzdecision for what (if anything) is included in RC2 will happen early next week most likely17:54
akerrbswartz: vponomaryov: creating LP bug17:55
vponomaryovbswartz: who makes decision?17:55
bswartzcore team17:55
vponomaryovrelease or we?17:55
bswartzus17:55
vponomaryovok17:55
bswartzWe have to decide if it's a ship stopper17:55
bswartzbecause at this point only really bad thing should be fixed17:56
vponomaryovitis not critical, but it is regression17:56
bswartzwe can't make the decision to backport until we have a merged fix in newton though17:56
bswartzit helps to see what the change actually looks like so we can assess risk of additional regressions caused by the bugfix17:57
ameadeakerr: vponomaryov: https://bugs.launchpad.net/manila/+bug/156113917:59
openstackLaunchpad bug 1561139 in Manila "Managing a share with an invalid share type results in a share created" [Undecided,New]17:59
akerrameade: thx18:00
akerrbswartz: ^18:00
bswartzakerr: this was discovered by a failing test, no? can we mention which test it was in the bug, with perhaps a link to relavant logs?18:02
gansovponomaryov, akerr: scheduler needs request_spec, which needs share to be created. Unless we create an empty request spec, a possible fix is to delete share in API before returning response18:03
akerrbswartz: sure18:04
gouthamrganso: can't we delete the DB record on failure for manage?18:04
gansogouthamr: yes we can, I am suggesting that18:05
gouthamrganso: its a 409 conflict, so you don't need to save the state.. the request will be re-attempted18:05
bswartzhard delete or soft delete?18:05
gansogouthamr: save what state?18:05
bswartzit seems crappy if we have only one code path that creates shares and then automatically deletes them18:05
gouthamryou created a record for a share that could not be created because of a conflict..18:06
gouthamrbswartz: no, the operation is not complete yet18:06
bswartzit would be nice if the API service could detect the error itself without needing RPC at all18:06
gouthamrbswartz: it isn't returning a 202 and failing later..18:06
gouthamrbswartz: it is failing, with a 409..18:06
gansogouthamr: delete DB record here https://github.com/openstack/manila/blob/master/manila/share/api.py#L55118:06
gouthamrbswartz: so its a failure.. we shouldn't be saving any state in Manila18:07
gouthamrbswartz: its a failed request.18:07
gouthamrAPI request*18:07
gouthamrganso: yep18:07
*** vbellur has joined #openstack-manila18:08
*** sedwards has joined #openstack-manila18:12
*** krotscheck has quit IRC18:14
bswartzgouthamr: you mean the scheduler isn't involved at all?18:14
*** krotscheck has joined #openstack-manila18:15
bswartzin that case why do we not reorder the logic to detect this error before writing anything to the DB?18:15
openstackgerritMerged openstack/puppet-manila: Fix typos  https://review.openstack.org/29437518:15
gouthamrbswartz: we're creating the record before sending the scheduler request.. two ways about this, don't create until the scheduler returns or just delete if the scheduling fails.18:15
bswartzgouthamr: what I was proposing was option #3 -- don't invoke the scheduler RPC and instead import the scheduler code and invoke it from the API service18:17
bswartz^ could this work or am I missing something18:17
*** sedwards has quit IRC18:17
gansogouthamr: what's the problem of invoking the scheduler through call_context.call? it is synchronous and you don't need to import scheduler18:21
gouthamrganso: i think rpc is fine.. the scheduler has the pool info.. im not sure how you can get all of that with importing..18:22
*** esker has joined #openstack-manila18:23
gansogouthamr: oh ok18:23
gansogouthamr: and how can we hard delete it after it is created?18:23
gansogouthamr: I don't see any db calls or parameters to hard delete18:23
gouthamrganso: soft delete must be okay..18:23
bswartznever creating it in the first place would be preferable18:24
bswartzdoes the scheduler need an share ID in order to respond with the error?18:24
gansobswartz: scheduler does not need share, but need request_spec, and request_spec needs share18:24
vponomaryovganso; bswartz is right, it should not be created, if you need to provide something to scheduler, then just use dict with all required data18:24
gouthamri agree ^18:25
gansovponomaryov:  this data: https://github.com/openstack/manila/blob/master/manila/share/api.py#L56218:25
*** krotscheck has quit IRC18:26
*** krotscheck has joined #openstack-manila18:26
gouthamrganso: don't you just need the share type data?18:27
gansogouthamr: I don't know, I have never tried request_spec with only share_properties and share_instance_properties empty18:28
bswartzI'm getting the impression that what we need is a new RPC that the API service can call to make this check with minimal inputs18:28
bswartzhowever a new RPC would be a bad idea for backporting to mitaka18:28
gansobswartz: if behavior can be the same while supplying a request spec with only share_type then an additional RPC is not needed18:29
*** cknight has quit IRC18:30
gouthamrganso: going through the logic there.. is there a way you can remove the db create line.. and return the host?18:33
gouthamrganso: from the scheduler18:33
gansogouthamr: the scheduler does not create db entry18:33
gansogouthamr: it calls manager code18:33
gouthamrganso: we don't need to18:33
gansogouthamr: API can call manager code once scheduler validates18:34
gouthamrganso: we can make the scheduler return to the API and the API can call the share manager RPCAPI18:34
gansogouthamr: yes18:34
gouthamrganso: that way, you can create the db record only if the scheduler gives you the host.18:34
gansogouthamr: yes18:34
* gouthamr should read ganso's responses before typing away.. :P18:35
gansogouthamr: lol18:36
*** cknight has joined #openstack-manila18:37
*** krotscheck has quit IRC18:38
*** krotscheck has joined #openstack-manila18:39
*** permalac has quit IRC18:39
openstackgerritValeriy Ponomaryov proposed openstack/manila: Add caution to test-requirements  https://review.openstack.org/29666518:39
*** sgotliv has joined #openstack-manila18:49
*** openstack has joined #openstack-manila19:23
openstackgerritRodrigo Barbieri proposed openstack/manila: Fix Manage API creating DB record for invalid type  https://review.openstack.org/29670619:24
*** DuncanT_ is now known as DuncanT19:24
*** martyturner has quit IRC19:24
*** timcl1 has joined #openstack-manila19:26
*** timcl has quit IRC19:27
*** martyturner has joined #openstack-manila19:30
*** dustins_ has joined #openstack-manila19:34
*** dustins has quit IRC19:36
*** Yogi1 has quit IRC19:55
openstackgerritEmilien Macchi proposed openstack/puppet-manila: Release 8.0.0  https://review.openstack.org/29673020:03
*** ociuhandu has quit IRC20:05
*** swamireddy1 has quit IRC20:07
openstackgerritEmilien Macchi proposed openstack/puppet-manila: Release 8.0.0  https://review.openstack.org/29675220:07
gouthamrganso: ping20:08
gansogouthamr: pong20:08
gouthamrganso: https://github.com/openstack/manila/blob/master/manila/api/v1/share_manage.py#L6120:09
gouthamrganso: do you think thats right?20:09
gouthamrManilaException is a base class for a bunch of exceptions... maybe you should specifically expect the InvalidHost exception?20:10
gouthamrganso: just increasing the scope of your commit there.. but we should correct that behavior :)20:11
*** lpetrut has joined #openstack-manila20:12
gansogouthamr: yes, I am checking other exceptions just a sec20:12
gansogouthamr: share.api.manage raises ManilaException20:12
gansogouthamr: if share already exists20:13
gansogouthamr: that would need to be fixed as well20:13
gansogouthamr: I agree that catch block should capture only specific exception, not the base class20:13
gansogouthamr: but we need to also remember that if we want the fix in RC2 we need to minimize impact, maybe those changes should not go into same change-id20:14
*** timcl1 has quit IRC20:14
gouthamrganso: sure... i just thought that was a disparity,20:15
gouthamrganso: thanks.. will review the patch20:15
*** openstack has joined #openstack-manila20:33
*** cknight has joined #openstack-manila20:34
*** gouthamr has quit IRC20:35
*** martyturner has joined #openstack-manila20:39
*** cknight has quit IRC20:45
*** rraja has quit IRC20:47
*** porrua has quit IRC20:56
*** david-lyle has quit IRC20:59
*** cfey has quit IRC21:05
*** david-lyle has joined #openstack-manila21:05
*** a_ta has quit IRC21:14
*** a_ta has joined #openstack-manila21:16
*** tpsilva has quit IRC21:17
*** david-lyle has quit IRC21:21
*** cfey has joined #openstack-manila21:22
*** david-lyle has joined #openstack-manila21:23
openstackgerritMerged openstack/puppet-manila: Release 8.0.0  https://review.openstack.org/29675221:24
*** ociuhandu has joined #openstack-manila21:25
*** adrianofr_ has quit IRC21:50
*** a_ta has quit IRC21:55
*** alyson_ has quit IRC22:12
*** martyturner has quit IRC22:19
*** gouthamr has joined #openstack-manila22:19
*** pgbridge has joined #openstack-manila22:33
*** darrenc_ has joined #openstack-manila23:05
*** darrenc has quit IRC23:06
*** darrenc_ is now known as darrenc23:07
*** ganso has quit IRC23:09
*** gouthamr has quit IRC23:10
*** erlon has quit IRC23:17
*** absubram has quit IRC23:21
*** openstack has joined #openstack-manila23:25
*** sgotliv has quit IRC23:34
*** yangyapeng has quit IRC23:34
*** gouthamr has joined #openstack-manila23:37
*** dustins_ has quit IRC23:40

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