Thursday, 2019-08-15

*** absubram has joined #openstack-meeting-alt00:14
*** dave-mccowan has quit IRC00:22
*** markvoelker has joined #openstack-meeting-alt00:24
*** rfolco has quit IRC00:35
*** jcoufal has joined #openstack-meeting-alt00:35
*** gyee has quit IRC00:40
*** jcoufal has quit IRC00:48
*** markvoelker has quit IRC00:51
*** markvoelker has joined #openstack-meeting-alt00:52
*** hongbin has joined #openstack-meeting-alt00:58
*** markvoelker has quit IRC01:01
*** markvoelker has joined #openstack-meeting-alt01:05
*** markvoelker has quit IRC01:11
*** markvoelker has joined #openstack-meeting-alt01:16
*** yamamoto has quit IRC01:40
*** yamamoto has joined #openstack-meeting-alt01:40
*** apetrich has quit IRC02:09
*** absubram has quit IRC02:12
*** tetsuro has joined #openstack-meeting-alt02:31
*** tetsuro has quit IRC02:32
*** tetsuro has joined #openstack-meeting-alt02:37
*** tetsuro has quit IRC02:41
*** tetsuro has joined #openstack-meeting-alt02:42
*** bhavikdbavishi has joined #openstack-meeting-alt02:42
*** tetsuro has quit IRC02:44
*** bhavikdbavishi1 has joined #openstack-meeting-alt02:57
*** bhavikdbavishi has quit IRC02:58
*** bhavikdbavishi1 is now known as bhavikdbavishi02:58
*** markvoelker has quit IRC03:10
*** altlogbot_3 has quit IRC03:16
*** altlogbot_1 has joined #openstack-meeting-alt03:17
*** hongbin has quit IRC03:27
*** yamamoto has quit IRC03:37
*** yamamoto has joined #openstack-meeting-alt03:45
*** tetsuro has joined #openstack-meeting-alt03:45
*** tetsuro has quit IRC03:48
*** yamamoto has quit IRC03:53
*** markvoelker has joined #openstack-meeting-alt03:55
*** markvoelker has quit IRC04:00
*** dave-mccowan has joined #openstack-meeting-alt04:23
*** dave-mccowan has quit IRC04:31
*** markvoelker has joined #openstack-meeting-alt04:50
*** markvoelker has quit IRC04:54
*** markvoelker has joined #openstack-meeting-alt05:35
*** links has joined #openstack-meeting-alt05:37
*** markvoelker has quit IRC05:41
*** bhavikdbavishi has quit IRC05:59
*** yamamoto has joined #openstack-meeting-alt06:16
*** hongbin has joined #openstack-meeting-alt06:28
*** hongbin has quit IRC06:32
*** yamamoto has quit IRC06:36
*** yamamoto has joined #openstack-meeting-alt06:37
*** yamamoto has quit IRC06:42
*** bhavikdbavishi has joined #openstack-meeting-alt06:45
*** yamamoto has joined #openstack-meeting-alt06:54
*** yamamoto has quit IRC06:54
*** belmoreira has joined #openstack-meeting-alt06:55
*** jtomasek has joined #openstack-meeting-alt07:15
*** kopecmartin|off is now known as kopecmartin07:16
*** bhavikdbavishi has quit IRC07:28
*** tssurya has joined #openstack-meeting-alt07:32
*** apetrich has joined #openstack-meeting-alt08:01
*** e0ne has joined #openstack-meeting-alt08:15
*** markvoelker has joined #openstack-meeting-alt08:20
*** markvoelker has quit IRC08:25
*** yamamoto has joined #openstack-meeting-alt08:26
*** yamamoto has quit IRC08:28
*** yamamoto has joined #openstack-meeting-alt08:34
*** yamamoto has quit IRC08:38
*** derekh has joined #openstack-meeting-alt08:40
*** gibi has quit IRC08:42
*** yamamoto has joined #openstack-meeting-alt08:47
*** gibi has joined #openstack-meeting-alt09:06
*** yamamoto has quit IRC10:00
*** belmoreira has quit IRC10:03
*** helenafm has joined #openstack-meeting-alt10:15
*** hongbin has joined #openstack-meeting-alt10:22
*** markvoelker has joined #openstack-meeting-alt10:36
*** apetrich has quit IRC10:37
*** markvoelker has quit IRC10:41
*** yamamoto has joined #openstack-meeting-alt10:53
*** yamamoto has quit IRC10:59
*** haixin has joined #openstack-meeting-alt11:01
*** yamamoto has joined #openstack-meeting-alt11:06
*** belmoreira has joined #openstack-meeting-alt11:09
*** yamamoto has quit IRC11:10
*** belmoreira has quit IRC11:11
*** belmoreira has joined #openstack-meeting-alt11:14
*** hongbin has quit IRC11:16
*** ircuser-1 has quit IRC11:21
*** ijw has joined #openstack-meeting-alt11:27
*** haixin has quit IRC11:30
*** haixin has joined #openstack-meeting-alt11:31
*** yamamoto has joined #openstack-meeting-alt11:31
*** ijw has quit IRC11:31
*** haixin has quit IRC11:33
*** markvoelker has joined #openstack-meeting-alt11:40
*** yamamoto_ has joined #openstack-meeting-alt11:41
*** yamamoto has quit IRC11:45
*** bhavikdbavishi has joined #openstack-meeting-alt12:00
*** raildo has joined #openstack-meeting-alt12:06
*** bhavikdbavishi1 has joined #openstack-meeting-alt12:13
*** rfolco has joined #openstack-meeting-alt12:14
*** bhavikdbavishi has quit IRC12:14
*** bhavikdbavishi1 is now known as bhavikdbavishi12:15
*** yamamoto_ has quit IRC12:20
*** yamamoto has joined #openstack-meeting-alt12:28
*** hongbin has joined #openstack-meeting-alt12:43
*** hongbin has quit IRC12:43
*** apetrich has joined #openstack-meeting-alt13:00
*** helenafm has quit IRC13:02
*** tssurya has quit IRC13:03
*** tssurya has joined #openstack-meeting-alt13:04
*** yamamoto has quit IRC13:06
*** yamamoto has joined #openstack-meeting-alt13:17
*** baojg has quit IRC13:18
*** yamamoto has quit IRC13:29
*** yamamoto has joined #openstack-meeting-alt13:35
*** priteau has joined #openstack-meeting-alt13:38
*** yamamoto has quit IRC13:39
*** belmoreira has quit IRC13:45
*** belmoreira has joined #openstack-meeting-alt13:51
*** baojg has joined #openstack-meeting-alt13:51
*** yamamoto has joined #openstack-meeting-alt13:53
*** baojg has quit IRC13:59
*** links has quit IRC14:08
*** ganso has joined #openstack-meeting-alt14:28
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-meeting-alt14:30
*** dviroel has quit IRC14:38
*** jgrosso has joined #openstack-meeting-alt14:45
*** carloss has joined #openstack-meeting-alt14:56
*** gyee has joined #openstack-meeting-alt14:57
*** dviroel has joined #openstack-meeting-alt14:58
tbarron#startmeeting manila15:00
openstackMeeting started Thu Aug 15 15:00:06 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
carlosshi :)15:00
vkmco/15:00
amitoo/15:00
jgrossohi :)15:00
dviroelo/15:00
tbarroncourtesy ping: gouthamr xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso dviroel lseki carloss15:00
vkmc\o)15:00
vkmc(o/15:00
tbarronvkmc: \o15:00
tbarronvkmc: o/15:00
vkmclol15:01
gouthamro/15:01
tbarronit's cold in buenos aires I guess15:01
vkmcyeah15:01
vkmc"cold", our winter for you must be a joke15:01
vkmcbut I'm seriously suffering15:01
tbarronI see you doing jumping jacks15:01
vkmc53F15:01
vkmchaha yes15:02
vkmckeeps you warm and makes you fit, smart15:02
tbarronHi all!15:02
tbarronAgenda: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting15:02
tbarron#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: manila)"15:03
tbarronFirst, just our weekly schedule reminder,15:03
tbarronThis wee is Feature Proposal Freeze15:03
tbarronThis week15:04
tbarronI think we're OK on that front -- let me know if15:04
tbarronyou have something cooking that we need special consideration for --15:04
tbarronbut I need to clarify something.15:04
tbarronLast week I said that this meant that doc for the feature was supposed to be ready.15:05
tbarronBut15:05
tbarronit turns out that I had inadvertently copied that requirement into our schedule this release15:05
tbarronWe've never had it before15:05
tbarronSo mea culpa.15:05
tbarronAnd we won't require that at this point.15:05
tbarronActual Feature Freeze is in threee weeks, 5 September.15:06
tbarron"No featureful patch should be landed after this point."15:06
dviroeltbarron: 5 september?15:07
tbarronquoting from the release schedule15:07
* tbarron looks again15:07
dviroel=)15:07
dviroel"Sep 09 - Sep 13"15:07
gouthamrSep 09 - Sep 1315:07
tbarronyeah15:07
gouthamr#link https://releases.openstack.org/train/schedule.html15:07
tbarroni'm confused today, as usual15:07
tbarronthanks15:07
tbarronso that's four weeks, right?15:08
dviroelyes15:08
tbarronThe only other announcement I have is that I was able to move the manila-csi talk in shanghai around15:09
tbarronso that we don't have both manila talks at the same time15:09
carloss\o/15:09
vkmctbarron++15:10
tbarronI'm looking forward to attending the talk the NetApp folks are doing15:10
dviroelthanks tbarron15:10
carlossthanks tbarron15:10
tbarronAny other announcments?15:10
tbarron#topic Python 3 for Third Party CI15:10
*** openstack changes topic to "Python 3 for Third Party CI (Meeting topic: manila)"15:10
tbarrondviroel: I see you have an update15:11
tbarron#link https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing15:11
*** jgrosso has left #openstack-meeting-alt15:11
*** jgrosso has joined #openstack-meeting-alt15:11
dviroeltbarron: yes, not too much to add, we just follow the tips from cinder folks, and everything is running ok15:12
tbarronSo NetApp is running with 3.7, awesome15:12
tbarronAnd there's a section there where vendors can report success.15:12
tbarronConversely, we'll move this section in the wiki to a quite public location at the end of Train or so :)15:13
tbarronAnd list CI that is only testing with python2 still15:13
tbarronPeer pressure :)15:13
tbarronDell-EMC is working on this stuff and thanks carloss for helping out15:14
*** s0ru has joined #openstack-meeting-alt15:14
tbarronI'm not sure what's going on with https://bugs.launchpad.net/manila/+bug/183316015:14
openstackLaunchpad bug 1833160 in Manila "VNX: driver cannot start under py37 due to wrap_socket() got an unexpected keyword argument '_context'" [Undecided,New]15:14
carlosstbarron:  yw15:15
*** baojg has joined #openstack-meeting-alt15:15
tbarron#topic Reviews15:16
carlossI saw his last comment, will answer soon15:16
*** openstack changes topic to "Reviews (Meeting topic: manila)"15:16
tbarroncarloss: thanks15:16
tbarronLast week I said I'd make a review focus etherpad and dropped the ball.15:17
tbarronSo I just started one :)15:17
tbarron#link https://etherpad.openstack.org/p/manila-train-review-focus15:17
tbarronNeed to populate it15:17
tbarronBut let's distribute a bit of the work, the point of doing the etherpad rather15:17
tbarronthan just keeping track on our wiki is that people are more comfortable15:18
tbarronjust doodling into the etherpad15:18
tbarronIf you need a review, just list it there15:18
tbarronI and/or others can do some formattting to make it look like our old review focus etherpads15:19
tbarronWe can update with people already reviewing and see gaps easier.15:19
dviroelack15:20
tbarronAnything else on this ?15:20
tbarron#topic bugs15:20
*** openstack changes topic to "bugs (Meeting topic: manila)"15:20
tbarronjgrosso: what do you have for us today?15:20
jgrossotbarron one bug15:20
jgrossohttps://bugs.launchpad.net/manila/+bug/163131415:20
openstackLaunchpad bug 1631314 in Manila "Tempest tests "test_promote_out_of_sync_share_replica" and "test_resync_share_replica" are concurrency-prone" [Medium,Confirmed]15:20
jgrossonothing big today :)15:21
jgrossolowly ole temptest testsd15:21
tbarronjgrosso: you asked whether we have a milestone when the issue will be addressed and15:23
gouthamrhmmm, one thing we can do, rather than chop off the tests is to retry the status15:23
jgrossono chopping allowed gouthamr15:23
gouthamrdviroel: are you folks touching any part of the share replication tempest tests? ^15:23
tbarronthe root cause analysis is https://bugs.launchpad.net/manila/+bug/1631314/comments/4 so far as I can tell15:24
openstackLaunchpad bug 1631314 in Manila "Tempest tests "test_promote_out_of_sync_share_replica" and "test_resync_share_replica" are concurrency-prone" [Medium,Confirmed]15:24
dviroelgouthamr: yes, at this moment.15:24
tbarronI meant to point to comment #415:24
gouthamrjgrosso: i'm with you :) hate to lose coverage because of something that shouldn't happen in a real cloud15:25
dviroelgouthamr: didn't face that issue because we were not using too much threads15:26
*** belmoreira has quit IRC15:26
*** macz has joined #openstack-meeting-alt15:26
jgrossogouthamr agreed :)15:26
gouthamrdviroel: it's not something you can control (besides the replication update interval)15:27
gouthamrdviroel: it's been a recurring issue on the dummy driver job, and i've occasionally seen it with netapp and zfsonlinux jobs running those two tests..15:28
*** belmoreira has joined #openstack-meeting-alt15:28
dviroelgouthamr: oh, now I saw the problem.15:29
gouthamra maintenance thread in the share manager interferes with the test logic, so - the test should be more resilient to this imo15:29
tbarrongouthamr: but how?15:29
gouthamr^ given that the test is trying to set a perfectly healthy replica to unhealthy so it can test the API15:30
tbarronit won't ever see it go "out of sync" because it really isn't, so what should it do?  just assume that its reset state worked?15:30
*** macz has quit IRC15:31
gouthamrtbarron: nope, reset state again, perhaps before issuing the next API call? although that isn't going to be enough if the replication update interval is too low (i think the gate sets it to 60 seconds)15:31
gouthamrthe real default is 300 seconds15:32
tbarrongouthamr: oh I see15:32
tbarrondo we need to have the update interval that low for other tests?15:33
tbarron"low" in quotes b/c normally I wouldn't call it that15:33
gouthamryes, because the generic build timeout is 180 seconds15:33
gouthamryou wouldn't want to wait too long to create replicas of empty shares15:34
gouthamrhttps://github.com/openstack/manila/blob/8d03a2a46e233b3628ffe59af67c1feb789e1669/contrib/ci/pre_test_hook.sh#L10315:34
gouthamr#link https://github.com/openstack/manila/blob/8d03a2a46e233b3628ffe59af67c1feb789e1669/contrib/ci/pre_test_hook.sh#L16215:34
tbarronso your suggestion is to have the test make several attempts to reset state since we're not testing resettign state, that's15:35
gouthamrso, the replica update interval is 10 seconds in the gate by default, and 60 seconds for the ZFSOnLinux driver15:35
tbarronjust a means to testing promotion15:35
gouthamrtbarron: yes, and "resync"15:35
gouthamrdviroel: do you know what value of "replica_state_update_interval" the NetApp CI uses, and if it's reliable?15:37
tbarrongouthamr: maybe you can update the bug with that suggestion?  it seems less work than your original idea in comment #2 to15:37
gouthamrtbarron: sure can15:37
dviroelhttp://13.56.159.105/logs/43/671043/9/upstream-check/manila-cDOT-no-ss/c972cbe/logs/local.conf.txt.gz15:37
tbarronintroduce an api to disable/enable the periodic update15:37
*** belmoreira has quit IRC15:38
tbarronthat takes us back to jgrosso's original question15:38
gouthamrdviroel: thanks, so you're not overriding the default 10 sec15:38
tbarronjgrosso: no, we don't have a milestone target15:38
dviroelyeah, 1015:38
gouthamrdviroel: that the pre-test hook sets up for all drivers15:38
tbarronjgrosso: need volunteer to sign up, we can't just assign all hard problems15:38
tbarronto gouthamr15:38
jgrossowhy not ?15:39
jgrosso:)15:39
gouthamror easy ones :)15:39
dviroeltbarron: I can help with this one15:39
tbarrondviroel: awesome15:39
jgrossothanks dviroel15:39
gouthamrdviroel: ty!15:39
jgrossothat is all I had for today15:39
tbarronjgrosso: dviroel: why don't you guys get together to figure miilestone, etc.15:40
tbarronit doesn't have to be immediate, but great to get an ownere15:40
tbarronowner15:40
jgrossotbarron ack15:40
tbarronthanks jgrosso15:40
tbarron#topic open discussion15:40
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:40
dviroeltbarron: ack15:40
jgrossotbarron: welcome15:40
gouthamrI had something to check on15:41
gouthamrdviroel/netapp folks: what's the status on:15:41
gouthamr#link https://bugs.launchpad.net/manila/+bug/169985615:41
openstackLaunchpad bug 1699856 in Manila "Tempest tests missing adding Security service to share-network" [Medium,Triaged] - Assigned to Douglas Viroel (dviroel)15:41
dviroelgouthamr: we are not focusing on it right now, but shouldn't not be that hard.15:42
gouthamrdviroel: ack, yep - please take it up whenever possible; since you guys have an AD already in your CI, this should be easy to get tested on your end15:43
gouthamrdviroel: i can help sync up with other CIFS vendors to do a similar test when you have a fix15:44
gouthamrdviroel: and buy you beer in Shanghai15:44
*** markvoelker has quit IRC15:44
gouthamrjust because we're friends, i'm not bribing you15:44
dviroelgouthamr: ok, I'll take a look on that after replication15:44
dviroelbeer++15:44
gouthamrdviroel: nice, thanks!15:45
dviroelgouthamr: ty15:45
tbarronAnything else today?15:45
tbarronOK, see y'all in #openstack-manila15:46
tbarronThanks everyone!!15:46
tbarron#endmeeting15:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:46
openstackMeeting ended Thu Aug 15 15:46:45 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-08-15-15.00.html15:46
dviroelThanks!15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-08-15-15.00.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-08-15-15.00.log.html15:46
*** markvoelker has joined #openstack-meeting-alt15:48
*** slaweq has joined #openstack-meeting-alt16:00
priteau#startmeeting blazar16:00
openstackMeeting started Thu Aug 15 16:00:52 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: blazar)"16:00
openstackThe meeting name has been set to 'blazar'16:00
priteau#topic Roll call16:01
*** openstack changes topic to "Roll call (Meeting topic: blazar)"16:01
*** jakecoll has joined #openstack-meeting-alt16:01
*** markvoelker has quit IRC16:02
priteauHi jakecoll16:02
jakecollhello16:02
priteauIs Jason planning to join? If not we can start now.16:03
jakecollnot sure16:04
*** diurnalist has joined #openstack-meeting-alt16:04
*** baojg has quit IRC16:04
priteauHi diurnalist16:04
diurnalisto/16:04
priteau#topic Upstream contributions16:04
*** openstack changes topic to "Upstream contributions (Meeting topic: blazar)"16:04
*** yamamoto has quit IRC16:05
priteauThanks jakecoll for submitting a spec for network reservation. I just reviewed it earlier today.16:05
priteau#link https://review.opendev.org/#/c/674089/16:05
*** yamamoto has joined #openstack-meeting-alt16:05
priteauIt was a good exercise indeed as some comments may trigger code changes16:06
jakecollThanks. Just now looking at some of the comments16:06
*** yamamoto has quit IRC16:07
priteauIf you could update the code implementation accordingly, that would be great. For example I suggested that the vfc_resources DB row is removed, if there is any related code it should go as well.16:08
*** baojg has joined #openstack-meeting-alt16:08
*** baojg has quit IRC16:08
*** baojg has joined #openstack-meeting-alt16:09
*** kopecmartin is now known as kopecmartin|off16:09
jakecollI should be able to jump back on a lot of this next week. Had a bunch of stuff on my docket this week at work.16:09
*** baojg has quit IRC16:09
*** baojg has joined #openstack-meeting-alt16:09
*** baojg has quit IRC16:10
priteauWe should think about how the vfc stuff can be most efficiently maintained in Chameleon16:10
*** baojg has joined #openstack-meeting-alt16:10
*** baojg has quit IRC16:11
*** yamamoto has joined #openstack-meeting-alt16:11
jakecollI'm not all that aware of the vfc stuff16:11
*** yamamoto has quit IRC16:11
*** baojg has joined #openstack-meeting-alt16:11
*** markvoelker has joined #openstack-meeting-alt16:11
*** baojg has quit IRC16:11
*** yamamoto has joined #openstack-meeting-alt16:11
*** baojg has joined #openstack-meeting-alt16:12
*** baojg has quit IRC16:12
priteauIt's something specific to some network hardware in use on Chameleon, which means that even though X VLANs may be available, only Y can be configured at the same time.16:12
*** baojg has joined #openstack-meeting-alt16:12
priteauMaybe it could be another use case for the policy enforcement API we discussed some time ago.16:13
*** baojg has quit IRC16:13
priteaui.e. not just enforce resource usage policy, but also restrict reservation to technical limitations that may not be easy to describe within Blazar16:13
*** lseki has joined #openstack-meeting-alt16:14
*** slaweq has quit IRC16:14
*** baojg has joined #openstack-meeting-alt16:14
priteau#action Update usage enforcement spec to add VFC allocation use case, if relevant16:14
*** baojg has quit IRC16:14
*** baojg has joined #openstack-meeting-alt16:15
*** baojg has quit IRC16:15
*** baojg has joined #openstack-meeting-alt16:16
priteauWorth discussing while we're online: my comment about the UI for blazarclient to show/list allocations16:16
*** yamamoto has quit IRC16:16
priteauhttps://review.opendev.org/#/c/673106/16:16
*** baojg has quit IRC16:16
priteauWill we eventually have:16:16
priteaublazar host-allocation-list16:16
priteaublazar floatingip-allocation-list16:16
priteaublazar networksegment-allocation-list16:16
priteauor just:16:16
priteaublazar allocation-list [--host | --floatingip | --networksegment]16:16
*** baojg has joined #openstack-meeting-alt16:16
priteauReplace networksegment by network, I will we will settle on this name16:17
*** baojg has quit IRC16:17
jakecollYea, I like the functionality of that better16:17
*** baojg has joined #openstack-meeting-alt16:17
priteauthat = the second one?16:17
*** tssurya has quit IRC16:18
*** baojg has quit IRC16:18
*** baojg has joined #openstack-meeting-alt16:18
jakecollNo. The allocation-list --host etc...16:18
jakecoll...or, yes, the second one16:18
*** baojg has quit IRC16:18
priteauYes, OK :)16:18
*** baojg has joined #openstack-meeting-alt16:19
priteauI like it better too16:19
*** baojg has quit IRC16:19
*** baojg has joined #openstack-meeting-alt16:19
*** baojg has quit IRC16:20
priteauI look forward to your updated patch16:20
*** baojg has joined #openstack-meeting-alt16:20
priteauThat's all for me review-wise, I haven't managed to look at your other patches yet16:21
*** baojg has quit IRC16:21
*** baojg has joined #openstack-meeting-alt16:21
*** baojg has quit IRC16:21
*** baojg has joined #openstack-meeting-alt16:22
priteauDo you have anything else in the pipeline?16:22
*** baojg has quit IRC16:22
jakecollYes, potentially16:23
*** baojg has joined #openstack-meeting-alt16:23
jakecollWe're adding an API call that would reallocate a host. It's basically exposes the _reallocate functionality used in heal reservations to the admin api.16:24
*** baojg has quit IRC16:24
jakecollHea reservations is pretty useless on a baremetal setup so this just makes life easier for us.16:24
priteauHealth monitoring doesn't work well with Ironic?16:25
jakecollNope. It just queries Nova for the hypervisor status16:25
priteauI think you were trying it out at some point16:26
*** baojg has joined #openstack-meeting-alt16:26
priteauDo you know if it mirrors the maintenance state from ironic?16:26
*** baojg has quit IRC16:26
jakecollAnd anecdotal evidence on Chameleon seems to suggest that rarely if ever happens16:26
*** baojg has joined #openstack-meeting-alt16:26
*** absubram has joined #openstack-meeting-alt16:26
*** baojg has quit IRC16:27
jakecollI've never verified, but I assume since an ironic node in maintenance mode can still end up in a user's lease then no, I don't believe it does16:27
*** baojg has joined #openstack-meeting-alt16:27
*** baojg has quit IRC16:28
priteauThat's good to know. Maybe we can make improvements to the monitoring16:28
*** baojg has joined #openstack-meeting-alt16:28
diurnalistmy understanding is that the hypervisor is only down if the nova-compute-ironic service is down. when it restarts it processes each ironic node and i think even the ones in an error state show up as UP.16:28
*** e0ne has quit IRC16:28
*** absubram_ has joined #openstack-meeting-alt16:28
*** baojg has quit IRC16:28
*** baojg has joined #openstack-meeting-alt16:29
diurnalistimprovements to the monitoring will be necessary, either from this end or from nova's end. unclear how much nova should know about this. my understanding is that blazar has no idea ironic exists at the moment.16:29
*** baojg has quit IRC16:29
priteauI'll look at your reallocate code, is this it? https://github.com/ChameleonCloud/blazar/pull/1916:29
*** baojg has joined #openstack-meeting-alt16:29
jakecollyep16:30
*** baojg has quit IRC16:30
*** baojg has joined #openstack-meeting-alt16:30
*** slaweq has joined #openstack-meeting-alt16:31
priteauHave you considered using a property on the host itself rather than introducing a new API call?16:31
*** baojg has quit IRC16:31
*** absubram has quit IRC16:31
*** absubram_ is now known as absubram16:31
*** baojg has joined #openstack-meeting-alt16:31
jakecollNo. What would that look like?16:31
*** baojg has quit IRC16:32
diurnalistpriteau: not sure what you mean? the main thing is a means to trigger the mechanism that finds a replacement16:32
*** baojg has joined #openstack-meeting-alt16:32
*** baojg has quit IRC16:32
jakecollSo just set the hypervisor status to down?16:32
priteauThere is an existing property called `reservable` on the Blazar host. What if turning it from false to true triggered the reallocation?16:33
*** baojg has joined #openstack-meeting-alt16:33
priteauSorry, from true to false16:33
*** baojg has quit IRC16:33
*** baojg has joined #openstack-meeting-alt16:33
priteauI believe that's used by the health monitoring so we would have to check how it interacts with it16:34
jakecollYea, that could work. We didn't think of that16:34
*** baojg has quit IRC16:34
*** baojg has joined #openstack-meeting-alt16:34
priteauAlthough we have to consider if there is a situation where reservable is already set to false and you still want to reallocate16:34
*** baojg has quit IRC16:35
diurnalistcould work. is it valid for a non-reservable node to be in an allocation?16:35
jakecollThat would mess up all of our maintenance leases, I imagine16:35
diurnalistindeed :D - due to how the blazarnova filter works, a reservation is always required to test anything.16:36
diurnalistbut... with this property, maintenance leases become less important.16:36
diurnalistit definitely changes the workflow. i think ironic people are also having issues with how to handle this type of thing (taking node out of commision, but needing to work on it)16:36
diurnalisthttp://lists.openstack.org/pipermail/openstack-discuss/2019-May/006430.html16:36
*** absubram has quit IRC16:37
priteauGood point about the maintenance leases. As diurnalist say, they would not be required to prevent users from allocating the node (since reservable would be false), but could be useful for testing16:37
priteauHave you tried specifying the host to use to launch an instance? It may bypass BlazarFilter16:38
*** slaweq has quit IRC16:38
diurnalisthow does that work? instead of sending a reservation_id you can send some special param?16:38
diurnalisti would hope you couldn't bypass that filter so easily!16:39
priteauIt works well on a virtualised cloud, you do something like this: openstack server create [...] --availability-zone nova:hostname16:39
priteauFor Ironic the syntax may be: <az>:<hostname-of-nova-compute-service>:<hypervisor-name>16:40
priteauHopefully admin only16:43
priteauI'll look at the health monitoring code and provide feedback16:43
jakecoll:+1:16:44
diurnalistinteresting, will have to try that out16:44
priteauAnything else to discuss today?16:46
jakecollnot on my end16:47
*** lseki has quit IRC16:47
*** lseki has joined #openstack-meeting-alt16:48
priteauThanks a lot for joining, this was a good discussion16:48
*** slaweq has joined #openstack-meeting-alt16:48
priteauNo AOB from me either16:48
priteauHave a good fortnight!16:48
priteau#endmeeting16:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:48
openstackMeeting ended Thu Aug 15 16:48:48 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-15-16.00.html16:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-15-16.00.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-15-16.00.log.html16:48
*** s0ru has left #openstack-meeting-alt16:51
*** derekh has quit IRC17:05
*** _pewp_ has quit IRC17:21
*** _pewp_ has joined #openstack-meeting-alt17:22
*** priteau has quit IRC17:39
*** e0ne has joined #openstack-meeting-alt17:52
*** jakecoll has quit IRC17:54
*** absubram has joined #openstack-meeting-alt18:13
*** lseki has quit IRC18:22
*** rfolco is now known as rfolco|rucker|te18:25
*** rfolco|rucker|te is now known as rfolco|rucker18:25
*** e0ne has quit IRC18:36
*** carloss has quit IRC18:54
*** yamamoto has joined #openstack-meeting-alt18:58
*** yamamoto has quit IRC19:03
*** vesper11 has quit IRC19:30
*** jcoufal has joined #openstack-meeting-alt19:41
*** jcoufal has quit IRC19:49
*** gouthamr is now known as gouthamr|brb20:02
*** jtomasek has quit IRC20:27
*** gouthamr|brb is now known as gouthamr20:30
*** jcoufal has joined #openstack-meeting-alt20:43
*** rfolco|rucker is now known as rfolco20:48
*** jcoufal has quit IRC20:49
*** slaweq has quit IRC20:50
*** vesper11 has joined #openstack-meeting-alt20:53
*** takashin has joined #openstack-meeting-alt21:05
*** takashin has left #openstack-meeting-alt21:05
*** slaweq has joined #openstack-meeting-alt21:11
*** slaweq has quit IRC21:17
*** jgrosso has quit IRC21:19
*** markvoelker has quit IRC21:29
*** raildo has quit IRC21:30
*** dviroel has quit IRC21:38
*** yamamoto has joined #openstack-meeting-alt21:55
*** ijw has joined #openstack-meeting-alt22:05
*** markvoelker has joined #openstack-meeting-alt22:05
*** markvoelker has quit IRC22:09
*** slaweq has joined #openstack-meeting-alt22:11
*** markvoelker has joined #openstack-meeting-alt22:11
*** slaweq has quit IRC22:16
*** markvoelker has quit IRC22:40
*** yamamoto has quit IRC22:53
*** yamamoto has joined #openstack-meeting-alt22:57
*** yamamoto has quit IRC23:02
*** slaweq has joined #openstack-meeting-alt23:11
*** slaweq has quit IRC23:16
*** ijw has quit IRC23:29
*** absubram has quit IRC23:33
*** markvoelker has joined #openstack-meeting-alt23:45
*** igordc has joined #openstack-meeting-alt23:46
*** markvoelker has quit IRC23:50

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