Thursday, 2019-07-18

*** dviroel has quit IRC00:02
*** baojg has joined #openstack-manila01:13
*** Kuirong has joined #openstack-manila01:23
*** whoami-rajat has joined #openstack-manila01:31
*** s0ru has quit IRC04:36
*** ganso has quit IRC05:05
*** pcaruana has joined #openstack-manila05:44
*** logan- has quit IRC06:00
*** logan_ has joined #openstack-manila06:01
*** logan_ is now known as logan-06:01
openstackgerritXuan Yandong proposed openstack/python-manilaclient master: Cap sphinx for py2 to match global requirements  https://review.opendev.org/67140906:35
*** kopecmartin|off is now known as kopecmartin06:59
openstackgerritKuiRong proposed openstack/manila master: Add Infortrend Manila Driver  https://review.opendev.org/65777507:06
*** tosky has joined #openstack-manila08:31
*** petitbois has joined #openstack-manila08:37
*** petitbois has quit IRC09:13
*** petitbois has joined #openstack-manila09:59
*** petitbois has quit IRC09:59
*** petitbois has joined #openstack-manila10:00
petitboishello all! I'd like to define my own share protocol on manila. is this possible?10:00
*** Kuirong has quit IRC10:03
*** whoami-rajat has quit IRC10:30
*** takamatsu has joined #openstack-manila10:37
tbarronpetitbois: sure, the last share protocol added was MAPRFS - git show 306c79fd02 will give you an idea10:52
petitboistbarron: awesome thanks -- I'll check it out!10:53
*** carloss has joined #openstack-manila11:22
*** ganso has joined #openstack-manila11:39
*** dviroel has joined #openstack-manila11:39
*** eharney has quit IRC11:40
openstackgerritTom Barron proposed openstack/manila master: Run tempest jobs under python3  https://review.opendev.org/67103111:45
*** eharney has joined #openstack-manila12:26
openstackgerritHelen Walsh proposed openstack/manila master: Manila PowerMax - rebrand from VMAX to PowerMax  https://review.opendev.org/66308913:25
*** hoonetorg has quit IRC13:28
openstackgerritTom Barron proposed openstack/python-manilaclient master: Cap sphinx for py2 to match global requirements  https://review.opendev.org/65943913:31
*** enriquetaso has joined #openstack-manila13:31
openstackgerritMerged openstack/manila-ui master: Remove the get_item method  https://review.opendev.org/66755413:41
openstackgerritMerged openstack/manila-ui master: Modify the url of upper_constraints_file  https://review.opendev.org/66621213:46
*** whoami-rajat has joined #openstack-manila13:55
openstackgerritTom Barron proposed openstack/manila master: Run tempest jobs under python3  https://review.opendev.org/67103113:59
openstackgerritMerged openstack/python-manilaclient master: Add Python 3 Train unit tests  https://review.opendev.org/66938314:26
*** s0ru has joined #openstack-manila14:47
*** jgrosso has joined #openstack-manila15:00
*** kopecmartin is now known as kopecmartin|off15:03
*** eharney_ has joined #openstack-manila15:12
*** eharney has quit IRC15:15
*** eharney_ is now known as eharney15:17
*** hoonetorg has joined #openstack-manila15:26
*** enriquetaso has quit IRC15:52
*** vhariria has joined #openstack-manila15:58
tbarrongouthamr: you are focused on the deferred cutover but I don't read the bug as complaining about that.16:01
tbarrongouthamr: title of the bug is "space savings from efficiency could  be lost ..."P16:01
gouthamrtbarron: yes, but ONTAP says that the deferring is going to cost with "space efficiency loss"16:01
tbarrongouthamr: isn't that true whether the cutover is deferred or not?16:01
tbarrongouthamr: the volume will be in a new aggregate and16:02
*** eharney has quit IRC16:02
tbarrongouthamr: maybe my memory fails but16:02
tbarrongouthamr: won't dedupe be done for blocks in the whole aggregate?16:02
* tbarron might be confused about that16:02
tbarrongouthamr: if so, then whether there are matching blocks to dedupe or not will be a total crap shoot16:03
tbarrongouthamr: so space efficiency on the destination won't match that on the source16:03
tbarrongouthamr: but I see that this warning is being quoted in the context of the delayed cutover16:04
tbarrongouthamr: so probably you are right that there is some other space-efficiency effect going on that I'm not aware of16:04
tbarrongouthamr: "Deduplication is not ready for volmove cutover"16:05
tbarrongouthamr: so ack, but I don't get it.16:05
gouthamrtbarron: bswartz may know - the way this works right now is; when "migration-start" is issued, we begin a data copy to the destination and we wait on that initial data copy - you know how ONTAP does it - internal snapshots and xcopy and all that magic... When the data copy is complete, ONTAP is ready to cutover to the destination volume -> what this means is writes will be directed to the new volume, and reads may be temporarily done to the16:05
gouthamr old volume while any remaining data that wasn't part of the original snapshot is going to be copied over16:05
gouthamrwe have a choice to allow ONTAP to do a cutover when we initiate a migration - that is really the best way to use this feature, but, that isn't teh way migration is designed in manila16:06
gouthamrwe allow administrators a two phased approach, for consistency with the fallback path -> this means, they must issue a migration-complete to begin using the destination volume and delete the source and all that..16:07
gouthamrunlike SnapMirror that keeps running on a schedule, volume moves in ONTAP don't copy any new data while cutover is deferred16:08
gouthamrso if users continue writing to their shares, new data won't be available in the destination share (not like they care)16:09
gouthamruntil the administrator issues migration-complete16:09
gansotbarron, gouthamr: sorry about the delay, I added my thoughts in https://bugs.launchpad.net/manila/+bug/1492211 w.r.t https://review.opendev.org/#/c/224102/16:09
openstackLaunchpad bug 1492211 in Manila "Generic driver: error deleting shares if service_instance is not created" [Low,In progress] - Assigned to Lucian Petrut (petrutlucian94)16:09
gouthamrganso: Good idea, he's added some notes on the code patch: "The issue being fixed occurs only if the server is not created at all. In that case, you won't have an instance_id. This can easily be reproduced by trying to use a wrong flavor id, for example, and then attempting to delete the share. If the instance is created, you will have the instance id set in the exception "detail_data" field, used to update the DB.16:11
gouthamrhttps://github.com/openstack/manila/blob/master/manila/share/drivers/service_instance.py#L523"16:11
gansogouthamr: hmm I missed that. Either way, would be a good idea to have this retested16:13
tbarronganso: gouthamr: thanks!16:13
gouthamrtbarron: here's a warning each time we try this from the command line: "When the transfer is complete, trigger the cutover to avoid loss of space savings from efficiency."16:13
tbarrongouthamr: ack and probably worth noting in the bug16:14
gouthamrand some more unofficial docs here: https://www.storagefreak.net/2017/07/netapp-cdot-volume-move16:14
gouthamr"DataMotion for Volume (volume move operation) are retaining deduplication savings on a FlexVol. If deduplication operation is in progress when the volume move is active, then during the volume move cutover phase the current deduplication ops will be aborted."16:14
gouthamr"Once the volume move is completed, deduplication operations can be restarted (however it will not pick-up and the previous checkpoint, just start from the beginning)."16:14
gouthamrso it's quite bad to leave volume moves in that state of deferred cutovers :) iirc we do call this out in the docs16:15
tbarrongouthamr: thanks for 'splainin ...16:23
openstackgerritTom Barron proposed openstack/manila master: Run tempest jobs under python3  https://review.opendev.org/67103117:05
*** eharney has joined #openstack-manila17:13
*** tosky has quit IRC17:17
*** irclogbot_2 has quit IRC18:07
*** altlogbot_1 has quit IRC18:07
*** petitbois has quit IRC18:08
*** irclogbot_3 has joined #openstack-manila18:08
*** altlogbot_1 has joined #openstack-manila18:09
*** dsariel has joined #openstack-manila18:42
*** dsariel has quit IRC18:43
*** enriquetaso has joined #openstack-manila19:18
*** _erlon_ has joined #openstack-manila19:23
openstackgerritTom Barron proposed openstack/manila master: Run tempest jobs under python3  https://review.opendev.org/67103119:27
*** e0ne has joined #openstack-manila19:38
*** whoami-rajat has quit IRC19:44
*** vhariria has left #openstack-manila19:48
*** pcaruana has quit IRC20:01
*** jgrosso has quit IRC20:07
*** eharney has quit IRC20:32
enriquetasogouthamr, o/ how are u? what are your thoughts about my review https://review.opendev.org/#/c/667744/ ? :D21:01
enriquetasos0ru ^21:03
*** raissa has joined #openstack-manila21:06
*** raissa has quit IRC21:06
gouthamrenriquetaso: agree with vkmc.. :) - partially also thought we can give s0ru exposure to unit tests this way21:07
*** raissa has joined #openstack-manila21:07
*** raissa has quit IRC21:07
enriquetasovkmc, how can do https://opendev.org/openstack/python-manilaclient/src/branch/master/manilaclient/tests/unit/v2/test_shell.py#L407 receive a list of shares empty ?21:07
vkmcenriquetaso, I was trying to figure out that so we can help out s0ru21:07
enriquetasogouthamr++21:07
enriquetasovkmc++21:07
enriquetasothanks!21:07
vkmcbut I cannot finish my devstack deploy on rdocloud :/21:07
*** raissa has joined #openstack-manila21:08
vkmcI'll spin up a vm so we can get her unblocked21:08
*** raissa has quit IRC21:08
*** eharney has joined #openstack-manila21:08
s0ru\o/21:12
gouthamrvkmc: she should still have access to mine?21:12
s0ruyeah!21:17
*** e0ne has quit IRC21:17
s0ruI've been using it :)21:18
enriquetaso:O21:22
enriquetasooki21:28
s0ruI don't know if vkmc can access to the vm too, devstack it's up and running21:29
s0rugouthamr: like u did with my public key21:31
*** enriquetaso has quit IRC21:46
*** eharney has quit IRC22:16
*** carloss has quit IRC22:21

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