Thursday, 2020-05-28

*** threestrands has joined #openstack-manila00:09
*** andrebeltrami has quit IRC03:08
*** carloss has quit IRC03:20
openstackgerritinspurericzhang proposed openstack/manila-tempest-plugin master: Add py38 package metadata  https://review.opendev.org/73141103:41
*** threestrands has quit IRC03:49
*** tosky has joined #openstack-manila07:44
*** tkajinam has quit IRC08:37
openstackgerritLiron Kuchlani proposed openstack/manila-tempest-plugin master: Preparation for support scenario tests on CephFS Native  https://review.opendev.org/72548708:57
openstackgerritLiron Kuchlani proposed openstack/manila-tempest-plugin master: Preparation for support scenario tests on CephFS Native  https://review.opendev.org/72548709:41
*** tosky_ has joined #openstack-manila09:57
*** tosky is now known as Guest4863309:57
*** tosky_ is now known as tosky09:57
openstackgerritMaurice Escher proposed openstack/manila master: add share server update to manila-manage share update_host  https://review.opendev.org/73148610:09
openstackgerritLiron Kuchlani proposed openstack/manila-tempest-plugin master: Preparation for support scenario tests on CephFS Native  https://review.opendev.org/72548711:41
openstackgerritMaurice Escher proposed openstack/manila master: add manila-manage service cleanup  https://review.opendev.org/73150411:48
*** carloss has joined #openstack-manila11:59
*** eharney has joined #openstack-manila13:03
vkmccan I get some eyes on https://review.opendev.org/#/c/726514/?14:22
vkmceasy one14:22
vkmcand this one https://review.opendev.org/#/c/725680/14:23
vkmcalso easy one14:24
openstackgerritVictoria Martinez de la Cruz proposed openstack/python-manilaclient master: Add initial documentation for OSC  https://review.opendev.org/70583414:37
openstackgerritVictoria Martinez de la Cruz proposed openstack/python-manilaclient master: Improve OSC test coverage  https://review.opendev.org/71083014:38
*** maaritamm has joined #openstack-manila14:52
*** andrebeltrami has joined #openstack-manila14:57
*** vhari has joined #openstack-manila14:59
*** felipe_rodrigues has joined #openstack-manila14:59
carlosssure, vkmc15:00
vkmc:D15:02
*** jmlowe has quit IRC15:34
*** jmlowe has joined #openstack-manila15:37
gouthamrganso: looks like cinder addressed this a while ago: https://review.opendev.org/#/c/405578/16:02
gouthamrganso: routing volume extensions via the scheduler i mean16:02
gansogouthamr: hmmm so it could make sense for us too to go through the scheduler16:03
gouthamrganso: then again, they also made their volume types immutable: https://review.opendev.org/#/c/440680/16:04
gouthamrin-use volume types*16:04
gansogouthamr: hmmm that's debatable. Has its pros and cons, and that's a far greater change at the moment16:05
gouthamrganso: agreed, routing extensions through the scheduler still make senses - we should have a doc on what mutability of share types means16:05
gansogreater in the sense of user impact16:05
gansos/greater/bigger for disambiguity16:06
gouthamr:)16:06
gansogouthamr: I believe we may have code in place to handle the situation of not having enough space to do an extend operation. I remember this as well from a previous discussion. Changing to go through the scheduler now would render that stale16:08
gansobut it could be a better solution perhaps16:09
gouthamrganso: oh? i didn't see it while reviewing haixin's proposed change16:09
gansogouthamr: I believe it is handled in the manager/driver16:09
gouthamrganso: yep, will check again16:09
gouthamrganso: ack16:09
gouthamrdviroel lseki: o/ wouldn't it help to have a user message if share server deletion fails? without leaking the abstraction, the message could be as generic as "De-allocation of share network ports did not succeed. Contact your administrator to determine the cause and rectify."16:11
dviroelgouthamr: i think that make sense, yes. Is port allocation the only thing that will affect users?16:13
dviroelregarding resources that they can see16:13
gouthamrdviroel: yeah pretty much, we allow cleaning up shares/networks/groups etc..16:16
gouthamrdviroel: a similar message could be used while unmanaging a share server, because its a very similar situation16:18
carthacagouthamr ganso: what you think: will/should the extend through scheduler modification still keep the old feature to skip the scheduler? e.g. via a force-without-scheduler option or by having the possibility to define the set of scheduler filters to be used for this action?16:18
gansocarthaca: what is the use case for maintaining the old approach?16:19
lsekigouthamr: yes, sounds more helpful than just raising an exception16:19
carthacaganso: we keep a high reserved_percentage to stop new provisioning early, but existing shares should be allowed to grow (and snapshots ideally, too)16:21
gansocarthaca: I think that the impact of that depends on the implementation16:24
gansocarthaca: in my mind, the extend operation wouldn't go through the regular "scheduling routines"16:24
gouthamrcarthaca: i see..16:25
gouthamrganso: in the current approach haixin's taking, we'll be going through all the scheduler filters16:25
gouthamrsame thing cinder does, i think16:25
gansocarthaca: the host is predefined, it would just check the available space16:25
gansogouthamr: yea, cinder does that as well "host_passes_filter()"16:26
gouthamrganso: just checking available space would be hard, we'd need to do the overprovisioning, headroom calculations as well, for one?16:27
gansoI don't personally think it makes a lot of sense. However, in either way the reserved_percentage would come into play16:27
dviroelin that case, would be good to have a way of avoiding scheduler, like we do for create from snapshot16:28
gouthamryes, and prevent users from extending their existing shares16:28
gansogouthamr: what I'm trying to say is that we don't need to run filters to decide a "host", like the weighers etc16:28
gouthamrganso: i agree, it's like you've done for qualifying a migration destination host - just run it through the filters16:29
gansogouthamr: yes16:29
gouthamrdviroel carthaca: this is a good concern to take to haixin's patch: https://review.opendev.org/#/c/700393/16:29
gouthamrlet's continue the discussion there, this will def be one of the top concerns to address16:31
dviroelgouthamr: ack16:32
*** maaritamm has quit IRC16:32
*** jv_ has quit IRC16:38
*** jv_ has joined #openstack-manila16:41
*** jv_ has quit IRC16:53
*** jv_ has joined #openstack-manila16:54
*** maaritamm has joined #openstack-manila18:46
openstackgerritMaari Tamm proposed openstack/manila master: Add user message when share shrinking fails at the driver  https://review.opendev.org/72651419:55
*** maaritamm has quit IRC19:59
*** felipe_rodrigues has quit IRC20:18
gouthamrdviroel carloss: friends, one of you willing to pull the trigger here? https://review.opendev.org/#/c/726291/ :)21:25
carlossgouthamr will take a look :)21:25
carlosss/will/I will21:26
gouthamrcarloss++21:26
*** threestrands has joined #openstack-manila21:45
*** tkajinam has joined #openstack-manila22:54
*** tosky has quit IRC23:20
*** andrebeltrami has quit IRC23:26
openstackgerritMerged openstack/manila master: CIFS extension failing because of volume in use  https://review.opendev.org/49844523:28

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!