Friday, 2017-09-08

gouthamrsticker: if you're still around, no reason that seems obvious00:01
stickercool, have submitted a bug report and will submit a fix00:02
stickerhttps://bugs.launchpad.net/manila/+bug/171576800:02
openstackLaunchpad bug 1715768 in Manila "Unable to use dollar sign in usernames for access" [Undecided,New] - Assigned to Daniel Russell (danielr-2)00:02
gouthamrsticker: nice, thanks!00:02
openstackgerritDaniel Russell proposed openstack/manila master: Allows the use of dollar sign in usernames  https://review.openstack.org/50190300:09
openstackgerritDaniel Russell proposed openstack/python-manilaclient master: Allows the use of dollar sign in usernames  https://review.openstack.org/50190500:17
openstackgerritDaniel Russell proposed openstack/manila master: Allows the use of dollar sign in usernames  https://review.openstack.org/50190600:21
*** baojg has quit IRC00:26
*** harlowja has quit IRC01:11
zhongjungouthamr:ping01:12
gouthamrzhongjun: pong01:13
bswartzzhongjun: get your auth fixed yet? I still haven't seen a PM01:13
zhongjungouthamr:  We can only get metadata info by API() method, and get metadata from db https://github.com/openstack/manila/blob/master/manila/share/drivers/maprfs/maprfs_native.py#L11701:13
zhongjunbswartz: I seems not work01:14
bswartz:-(01:14
gouthamrzhongjun: yes, like share type extra specs01:15
zhongjungouthamr: Do you know why we doesn't add metadata info in driver apis?01:15
gouthamrzhongjun: you mean as part of the call from the manager to the share driver?01:16
gouthamrzhongjun: probably because you don't know when you need it and when you don't.. i recall this discussion regarding share type extra specs.. don't see a problem with this pattern though.01:17
zhongjungouthamr: yes01:17
gouthamrzhongjun: not a lot of drivers acknowledge share metadata.. also, users can change metadata at any time and there's no "update" call to the share drivers01:19
gouthamrcalled it out to the maprfs folks when they wrote their driver, but they said they'll deal with documenting when/why "_name" would make sense when using MAPRFS shares01:20
zhongjungouthamr: It just look a little werid. The driver could call common method, but in this case the driver call api() method01:22
zhongjuns/werid/weird01:23
gouthamrzhongjun: it's a wrapper around a DB call.. like "get_share_type_extra_specs" being used in many drivers01:25
zhongjungouthamr:  yeah, it's a wrapper around a DB call, we could just put it in a common place if most of driver need to call it, like "extract_host" being used in many drivers01:31
zhongjungouthamr: but it is not a big deal01:34
gouthamrzhongjun: +101:36
zhongjungouthamr: Could we quickly check another confuse for me01:37
gouthamrzhongjun: sure..01:37
zhongjungouthamr: After I create a replica, the replication id is equal to share instance id.  If we delete all the share replica, it means we will delete all share instances01:38
zhongjungouthamr: then the share doesn't work?01:38
gouthamrzhongjun: you can't delete the last share instance without deleting the share as well...01:39
zhongjungouthamr: If we create a share replica,  then we can not allowed to delete all share replications?01:39
gouthamrzhongjun: yes, DELETE /share-replicas will only work as long as there's atleast one active replica01:40
zhongjungouthamr: I used 'share-replica-delete  --force' , then I deleted the share instance01:40
gouthamrzhongjun: same with POST /share-replicas/{id}/action {'force-delete': null} <--- you can't delete the last active replica with this API01:41
zhongjungouthamr: so, if we create a share replica for a share, it means we can never delete it01:42
gouthamrhowever, you can mess things up if you went after your replicas with the /share_instances API01:42
gouthamrzhongjun: you can always DELETE /shares/{id}01:42
zhongjungouthamr: It could be mess things, but I just think  whether it could be weird for the user that he can not delete all share replications that he created and  always keep a share replication?01:46
gouthamrzhongjun: when you create a share with a share type that supports replication, you always have a "replica... but that doesn't mean01:47
gouthamryour share is being replicated yet01:47
gouthamrzhongjun: look at the share's "has_replicas" field after your share has been created01:49
gouthamrzhongjun: you can then create 1 or more secondary replicas to your share and delete them at will, you can't delete the share itself with "manila share-replica-delete"01:49
zhongjungouthamr:  we create a share with a share type that supports replication, it means we have abilities to create a replica,  it seems doesn't mean we always have a "replica01:49
gouthamrzhongjun: true.. you've only created a share that can be replicated.. but it isn't unless you create share replicas01:50
zhongjungouthamr: After I tested " POST /share-replicas/{id}/action {'force-delete': null} <--- you can't delete the last active replica with this API" I can delete the last non-sync replica01:52
gouthamrzhongjun: what do you mean by non-sync?01:53
zhongjungouthamr: I mean it can be deleted if the status is not active01:54
gouthamrzhongjun: mostly correct.. you can delete any non-active replica with "manila share-replica-delete"01:55
gouthamrzhongjun: slightly different only in case of "writable" replication, where all replicas are "active" and "manila share-replica-delete" will not work for the last one01:56
zhongjungouthamr: so you means normal at least the one replica status is active, then we shouldn't delete it. If the share replica status is not active, and we delete this share replica, then the relative share instance also be deleted,In this case, it is correct.02:02
gouthamrcorrect02:02
gouthamrif you have no replicas, you can delete your share. if you have replicas, you cannot delete your share until you delete all your replicas. Sort of like Share and Snapshots - you can't delete your share until you delete all the snapshots.02:04
*** markstur has quit IRC02:05
zhongjungouthamr: but we have two status in share replica, my case is:    1. create a share   2 create a share replica (status: available,  Replica State: active) 3 change the share replica status  (status: available,  Replica State: out_of_sync) 4: delete all the share replica     The results is we delete the share replica and delete the share instance, and also the share has been deleted.02:16
gouthamr1) create a share (status: available, replica_state: active, Share has_replicas = False)02:17
gouthamr2) create a replica (status: available, replica_state: out_of_sync/in_sync, Share has_replicas = True)02:18
zhongjungouthamr: like share and snapshot, we delete the snapshot, but we don't delete the share at the same time02:18
gouthamrwhat do you mean by (3)?02:19
zhongjungouthamr: the share replica status has been changed to out_of_sync02:20
gouthamrzhongjun: with share-replica-reset-state?02:20
zhongjungouthamr: yeah02:20
gouthamrshare-replica-reset-replica-state*02:20
zhongjungouthamr: or it could be updated by driver02:21
zhongjungouthamr: or it could be updated by driver when we run promote or something else02:21
gouthamrzhongjun: don't see how drivers can change from "active" to "out_of_sync" unless it is during a promotion02:22
gouthamrzhongjun: yes, the secondary becomes "active" after a promotion, and cannot be deleted02:23
*** markstur has joined #openstack-manila02:25
*** markstur has quit IRC02:25
zhongjungouthamr: https://bugs.launchpad.net/manila/+bug/171578302:27
openstackLaunchpad bug 1715783 in Manila "Share replica problem" [Undecided,New]02:27
zhongjungouthamr: steps02:27
gouthamrzhongjun: thanks, i understand what you mean by (3)02:29
gouthamrzhongjun: what you're doing what shouldn't be done.. reset-replica-state is an admin API only to assist in resetting the state when administrators have corrected issues on the backend.. it's helpful in case of a failed promotion02:32
gouthamrzhongjun: unsure how we can prevent misuse02:32
gouthamr:)02:32
gouthamrperhaps fail if there's only one replica02:33
gouthamri.e, only allow setting it to "active"02:33
*** scottda_ has quit IRC02:37
zhongjungouthamr :  There could build a way to warn the end user: "notice ~~ your share will be deleted "02:41
*** catintheroof has joined #openstack-manila02:48
*** catinthe_ has joined #openstack-manila02:50
*** catintheroof has quit IRC02:51
openstackgerritzhongjun proposed openstack/manila-specs master: Add count info in list response  https://review.openstack.org/50193403:21
*** catinthe_ has quit IRC03:56
*** gouthamr has quit IRC04:19
*** rejy has joined #openstack-manila05:09
*** gaurangt has quit IRC05:17
*** gaurangt has joined #openstack-manila05:19
*** dims has quit IRC05:54
*** harlowja has joined #openstack-manila06:19
*** jprovazn has joined #openstack-manila06:21
*** harlowja has quit IRC06:40
*** sticker has quit IRC06:43
*** dims has joined #openstack-manila06:51
*** gcb has quit IRC07:08
openstackgerritzhongjun proposed openstack/manila master: [Doc] Fix doc description for consistency group  https://review.openstack.org/50119807:12
openstackgerritzhongjun proposed openstack/manila master: [Doc] Delete doc description for consistency group  https://review.openstack.org/50119807:16
openstackgerritzhongjun proposed openstack/manila master: [Doc] Delete consistency group in doc  https://review.openstack.org/50119807:21
*** chlong has joined #openstack-manila07:36
*** chlong has quit IRC07:45
*** chlong has joined #openstack-manila08:25
*** chlong has quit IRC08:35
*** chlong has joined #openstack-manila08:51
*** chlong_ has joined #openstack-manila08:54
*** chlong has quit IRC08:58
*** chlong_ has quit IRC09:04
*** rraja has joined #openstack-manila09:17
*** chlong has joined #openstack-manila09:21
*** chlong has quit IRC09:24
*** chlong has joined #openstack-manila09:25
*** baojg has joined #openstack-manila09:41
*** jprovazn has quit IRC09:44
*** chlong has quit IRC09:55
-openstackstatus- NOTICE: Our CI systems experience a hickup, no new jobs are started. Please stay tuned and wait untils this resolved.10:47
*** baojg has quit IRC11:14
*** jprovazn has joined #openstack-manila11:34
*** ganso has joined #openstack-manila11:35
*** baojg has joined #openstack-manila11:49
*** jprovazn has quit IRC11:55
*** jprovazn has joined #openstack-manila11:58
*** jungleboyj has quit IRC12:06
*** eharney has quit IRC12:46
*** catintheroof has joined #openstack-manila13:26
*** gouthamr has joined #openstack-manila13:27
*** eharney has joined #openstack-manila13:34
*** jprovazn has quit IRC13:36
*** cknight has joined #openstack-manila13:37
*** xyang1 has joined #openstack-manila13:40
*** catinthe_ has joined #openstack-manila13:41
*** catintheroof has quit IRC13:44
*** jprovazn has joined #openstack-manila13:45
-openstackstatus- NOTICE: nodepool issue related to bad images has been resolved, builds should be coming back online soon. Restarted gerrit due to reasons. Happy Friday.13:46
*** scottda_ has joined #openstack-manila13:48
*** rraja has quit IRC13:57
*** zengyingzhe_ has quit IRC14:07
*** zengyingzhe_ has joined #openstack-manila14:07
*** rraja has joined #openstack-manila14:13
*** catintheroof has joined #openstack-manila14:22
*** catinthe_ has quit IRC14:25
*** jprovazn has quit IRC14:35
*** rraja has quit IRC14:40
*** rraja has joined #openstack-manila14:52
*** markstur has joined #openstack-manila14:56
*** cknight has quit IRC14:57
*** td has quit IRC15:07
*** cknight has joined #openstack-manila15:10
*** jungleboyj has joined #openstack-manila15:15
*** rraja has quit IRC15:26
*** markstur has quit IRC16:03
*** rejy has quit IRC16:25
*** dustins has joined #openstack-manila16:35
*** harlowja has joined #openstack-manila17:00
*** jmlowe has quit IRC17:09
*** jmlowe has joined #openstack-manila17:10
*** eharney has quit IRC18:31
*** eharney has joined #openstack-manila18:44
*** tinwood has quit IRC19:05
*** tinwood has joined #openstack-manila19:07
openstackgerritTom Barron proposed openstack/manila master: Fix test_rpc_consumer_isolation for oslo.messaging 5.31.0  https://review.openstack.org/50217320:24
tbarronhttps://bugs.launchpad.net/cinder/+bug/171547020:25
openstackLaunchpad bug 1715470 in OpenStack Compute (nova) "test_rpc_consumer_isolation fails with oslo.messaging 5.31.0" [Medium,Fix released] - Assigned to Matt Riedemann (mriedem)20:25
tbarronbswartz: xyang1 toabctl gouthamr ^^^ pulled in that fix as our unit tests also fail w/o it20:25
tbarronganso: vponomaryov cknight ^^20:26
bswartztbarron: that looks nice and sketchy -- I like it20:27
tbarronbswartz: I'm just copying the black magic20:27
tbarroncan't say I like it.20:28
tbarronnova heritage20:29
bswartzI just mean it seems like a very open-stacky way to do things20:29
tbarronyeah20:30
bswartzpush a change, break everyone, somebody fixes it with a hack, and everyone cargo cults the hack20:30
tbarronrofl20:32
*** eharney has quit IRC20:49
*** gouthamr has quit IRC20:56
*** dustins has quit IRC21:22
*** gouthamr has joined #openstack-manila21:23
gouthamrnever call me ever. but it is okay to call me, sometimes, maybe.21:29
gouthamrlol https://review.openstack.org/#/c/502173/1/manila/tests/test_test.py21:29
*** ying_zuo has left #openstack-manila21:46
*** xyang1 has quit IRC21:53
tbarronbut I'll ignore you if you do22:05
*** catintheroof has quit IRC22:08
*** cknight has quit IRC22:24
*** baojg has quit IRC22:29
*** baojg has joined #openstack-manila22:30
*** ganso has quit IRC22:44
*** baojg has quit IRC22:53
*** baojg has joined #openstack-manila22:57
*** baojg has quit IRC23:05
*** baojg has joined #openstack-manila23:08
*** baojg has quit IRC23:16
*** baojg has joined #openstack-manila23:24
*** baojg has quit IRC23:40
*** baojg has joined #openstack-manila23:45

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