Thursday, 2020-11-19

*** yamamoto has joined #openstack-meeting-alt00:12
*** tosky has quit IRC00:14
*** yamamoto has quit IRC00:23
*** ricolin has joined #openstack-meeting-alt00:37
*** yamamoto has joined #openstack-meeting-alt00:39
*** yamamoto has quit IRC00:47
*** yamamoto has joined #openstack-meeting-alt01:27
*** gyee has quit IRC01:38
*** yamamoto has quit IRC01:38
*** yamamoto has joined #openstack-meeting-alt01:50
*** macz_ has quit IRC02:08
*** zzzeek has quit IRC02:17
*** zzzeek has joined #openstack-meeting-alt02:19
*** rcernin has quit IRC02:22
*** rcernin has joined #openstack-meeting-alt02:26
*** enriquetaso has quit IRC02:32
*** zzzeek has quit IRC02:35
*** zzzeek has joined #openstack-meeting-alt02:36
*** macz_ has joined #openstack-meeting-alt03:20
*** macz_ has quit IRC03:25
*** sangeet has quit IRC03:37
*** ajitha has joined #openstack-meeting-alt04:23
*** vishalmanchanda has joined #openstack-meeting-alt04:30
*** ianychoi has joined #openstack-meeting-alt04:36
*** macz_ has joined #openstack-meeting-alt05:02
*** macz_ has quit IRC05:06
*** yamamoto has quit IRC05:24
*** yamamoto has joined #openstack-meeting-alt05:32
*** yamamoto has quit IRC05:34
*** yamamoto has joined #openstack-meeting-alt06:11
*** yamamoto has quit IRC06:20
*** macz_ has joined #openstack-meeting-alt06:29
*** macz_ has quit IRC06:34
*** yamamoto has joined #openstack-meeting-alt06:51
*** yamamoto has quit IRC07:00
*** slaweq has joined #openstack-meeting-alt07:01
*** rdopiera has joined #openstack-meeting-alt07:15
*** yamamoto has joined #openstack-meeting-alt07:30
*** yamamoto has quit IRC07:38
*** ralonsoh has joined #openstack-meeting-alt07:43
*** yamamoto has joined #openstack-meeting-alt08:01
*** yamamoto has quit IRC08:05
*** baojg has quit IRC08:34
*** baojg has joined #openstack-meeting-alt08:35
*** baojg has quit IRC08:35
*** rcernin has quit IRC08:37
*** ircuser-1 has quit IRC08:38
*** baojg has joined #openstack-meeting-alt08:42
*** tosky has joined #openstack-meeting-alt08:44
*** lpetrut has joined #openstack-meeting-alt08:47
*** yamamoto has joined #openstack-meeting-alt09:16
*** yamamoto has quit IRC09:23
*** ricolin has quit IRC09:38
*** yamamoto has joined #openstack-meeting-alt10:03
*** yamamoto has quit IRC10:16
*** e0ne has joined #openstack-meeting-alt10:29
*** yamamoto has joined #openstack-meeting-alt10:47
*** yamamoto has quit IRC10:57
*** yamamoto has joined #openstack-meeting-alt10:57
*** bnemec has quit IRC11:00
*** bnemec has joined #openstack-meeting-alt11:01
*** baojg has quit IRC11:04
*** baojg has joined #openstack-meeting-alt11:05
*** baojg has quit IRC11:40
*** baojg has joined #openstack-meeting-alt11:41
*** macz_ has joined #openstack-meeting-alt11:46
*** macz_ has quit IRC11:51
*** baojg has quit IRC11:55
*** baojg has joined #openstack-meeting-alt11:56
*** enriquetaso has joined #openstack-meeting-alt12:01
*** raildo has joined #openstack-meeting-alt12:14
*** ricolin has joined #openstack-meeting-alt12:18
*** kevinz has joined #openstack-meeting-alt12:36
*** zzzeek has quit IRC12:45
*** zzzeek has joined #openstack-meeting-alt12:47
*** liuyulong has joined #openstack-meeting-alt14:00
*** liuyulong has quit IRC14:33
*** baojg has quit IRC14:36
*** baojg has joined #openstack-meeting-alt14:37
*** miniroy has joined #openstack-meeting-alt14:47
*** tmazur has joined #openstack-meeting-alt14:50
*** cliffparsons has quit IRC14:51
*** cliffparsons has joined #openstack-meeting-alt14:52
*** andrebeltrami has joined #openstack-meeting-alt14:56
gouthamro/ zorillas - we're in https://meetpad.opendev.org/ManilaW-ReleaseBugSquash for our bug squash! join us there :)15:01
gouthamrcourtesy ping: ganso vkmc dviroel lseki carloss tbarron andrebeltrami felipe_rodrigues ^15:03
*** tosky has quit IRC15:18
*** tosky has joined #openstack-meeting-alt15:22
*** tosky has quit IRC15:26
*** macz_ has joined #openstack-meeting-alt15:39
*** tosky has joined #openstack-meeting-alt15:50
priteau#startmeeting blazar16:00
openstackMeeting started Thu Nov 19 16:00:22 2020 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
*** vishalmanchanda has quit IRC16:00
priteau#topic Roll call16:00
*** openstack changes topic to "Roll call (Meeting topic: blazar)"16:00
*** diurnalist has joined #openstack-meeting-alt16:05
diurnalisto/16:05
priteauo/16:06
priteauHi diurnalist16:06
diurnalistWelcome back!16:06
priteauThank you16:07
priteauSorry for skipping a couple of meetings due to being away16:08
priteauWe are now returning to our regular schedule16:08
priteauI wanted to catch up with you, I saw a number of updated patches but I haven't had time to look at them yet16:09
diurnalistsounds good16:09
diurnalistyes, I haven't had much time for upstream contributions myself, but had a day where I tried to go through all of our patches and try to get them up16:09
diurnalistrebasing on master etc16:10
diurnalistjakecoll doesn't work on the project anymore, but before he left (end of last week) he helped me write up some of the missing docs for network reservations16:10
priteauI saw an updated patch from him last Friday16:11
priteauI was wondering if he was going to be involved again16:11
priteauI've got limited time for reviews until end of last week most likely, are there some patches that you would suggest are good candidates to be merged?16:12
priteauI see network reservation still needs work16:12
diurnalistYes, I think it needs pep fixes at minimum. We had also discussed a tempest test, should we still try that? I think the difficulty was that the network plugin needs to be enabled by default, likely16:14
diurnalistThese ones are pretty small: https://review.opendev.org/#/c/762006/ https://review.opendev.org/#/c/761994/ https://review.opendev.org/#/c/761990/ https://review.opendev.org/#/c/589899/16:15
priteauI was asking for the tempest test mostly because my manual testing of the patch back in… April? uncovered various issues (even though unit tests were passing)16:15
priteauJust left feedback about the first one16:16
diurnalistI see your comment on the shuffling, I forgot we had discussed the toggle16:16
diurnalistOnce those are in I would move on to brushing up the enforcement stuff and submitting that16:16
priteauI forgot about the traceback one, adding it to my list to look at later16:16
diurnalistthis one has been sitting for a while and is probably the most complicated (other than net res.) https://review.opendev.org/#/c/731586/16:17
priteauYeah it's a though one, need some proper review session to go through it16:18
priteauI'll try to schedule one soon16:18
diurnalistok, appreciated-- I have also thought about setting aside some time to perform some other refactors. In my opinion much of the plugin logic could/should be pulled up one level into the base implementation, or some other component16:19
diurnalistreally there are 2 refactors I have been kicking around:16:20
diurnalist1.) update lease tear-down to gracefully handle individual reservation termination errors. I already have a patch for this and we're testing now. Currently a termination halts on the first failed reservation teardown failure.16:20
diurnalist2.) move resource filtering out of plugins and make it shared business logic16:21
priteauBoth would be really good16:22
diurnalistwhat I would really like to do long-term is support out-of-tree resource plugins. i envision moving more stuff to core concerns will make it much easier to do this16:22
priteauAnother I thought about is common code for handling extra capabilities16:22
diurnalist:nod:16:22
priteauCurrently there's lots of code duplication to do this across both hosts and networks16:22
diurnalistyes, especially that extra capabilities are really just a key/value system that can apply to any resource type16:23
priteauDo you see out of tree resource plugins being loaded like scheduler filters in nova/16:23
diurnalistI'm not 100% how nova does it. I am familiar with the Ironic way, where it's via entry_points16:24
diurnalistwhich I think is fine, and pairs well with stevedore16:24
priteauironic's way might be more modern since it was written more recently16:25
diurnalistthe way that would work is you'd define an entry point namespace like "blazar.resource_type" and then your python module would export an entry point like "my_type = module.path.to:Thing"16:25
priteauI tend to see more old patterns in nova than in the rest of OpenStack projects16:25
diurnalistand then blazar conf would have "enabled_plugins = physical:host,my_type" or similar16:26
diurnalistas long as the module is installed in the same python  path as blazar, everything's good16:26
*** rdopiera has quit IRC16:27
priteauI am not too familiar with this area but I guess it should work16:27
priteauWe mostly need to make sure there are no conflicts between plugins16:28
diurnalistyes, and I think the trickiest thing is going to be how to handle DB dependencies. the DB schema might need to change, which is going to be painful16:29
diurnalistOSC also uses entry points btw, this describes it a bit: https://docs.openstack.org/python-openstackclient/latest/contributor/plugins.html16:29
priteauSeparate DBs maybe?16:30
diurnalistI guess Neutron is the other project to look at here16:30
priteauThat way you could have an alembic serial number by plugin16:30
diurnalistone question to think about is: can all resource plugins share a db. is there anything that is not possible w/ this16:31
diurnalisttricky because some resource properties are more important than others, like hypervisor_hostname for the physical host plugin16:32
priteauI thought alembic migrations would conflict, but maybe not16:32
priteauI can see in neutron-lbaas it uses alembic as well16:33
priteauand AFAIK it was using the neutron db16:33
diurnalisti think it has its own tables that it targets though, could be wrong16:33
diurnalistvpnaas is similar16:33
*** gyee has joined #openstack-meeting-alt16:34
priteauYes, separate tables but same db16:34
priteauCould we keep resource plugins constrained to their own separate tables16:35
priteauThey would still be able to manipulate existing tables, but through the existing models (no schema changes)16:35
diurnalistyes, i think that's workable. the extra capabilities functionality is a bit tricky to express this way, maybe there is a way16:35
diurnalistplugins should not be responsible for implementing that IMO16:36
priteauMaybe with an additional layer in the DB, a resources table that would describe which plugin is responsible for each resource16:38
priteauAnd extra caps would reference this table, rather than the custom table from the plugin16:38
priteauA bit like how there is a split between the reservations table and computehost_reservations / instance_reservations16:38
diurnalisti'll have to look again to see how that works16:41
priteauThere might be some details that I've not considered but it's worth trying16:41
*** lpetrut has quit IRC16:42
diurnalist:nod:16:43
diurnalistwill keep kicking it around, at some point there will need to be a spec. it's more of a general direction i think things should move16:43
priteauI am all for it if it makes your life easier16:44
priteauAnything else to cover?16:45
diurnalistone other thing: has anybody worked on making blazarclient osc-compatible?16:46
priteauGood question16:46
diurnalisti am wondering if it might be a good project for a new hire as a way of getting acquainted w/ the process. a bit hard for us to argue for its utility, but it's always bugged me :)16:47
priteauThere was a start a while ago from someone in the community, but I don't think the patches were submitted upstream16:47
priteauI'll see if I can get the patches, but it might be difficult16:48
priteauIt could be a good project to get used to the client and the API. It's not really useful for learning about the internals of the service of course.16:49
diurnalisti think if the patches are very old it may be worth it to just start over16:49
diurnalistok, i'll let you know if it gets scheduled16:50
diurnalistotherwise nothing else from me, I don't think. there is a general question of how to handle upstream contributions given that it seems like you are the only active reviewer these days16:50
*** gyee has quit IRC16:50
priteauMaybe you should become core reviewer ;-) Although that doesn't really help with your own patches16:51
priteauBut if there are contributions from the new hire in your group, we could merge them with +2 from you and I16:53
diurnalistthat may be helpful16:53
priteauI'll propose something :)16:54
diurnalistin principle i worry about taking a bit too much extra responsibility, but in practice we are the main ones proposing things these days, and i'm reviewing that code anyways16:54
priteauYes I don't think it would add much workload for you16:55
priteauLet's wrap up16:56
priteauThanks a lot for joining!16:56
priteau#endmeeting16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:56
openstackMeeting ended Thu Nov 19 16:56:27 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-11-19-16.00.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-11-19-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-11-19-16.00.log.html16:56
*** andrebeltrami has quit IRC17:02
*** macz_ has quit IRC17:05
*** gyee has joined #openstack-meeting-alt17:05
*** ralonsoh_ has joined #openstack-meeting-alt17:27
*** ralonsoh has quit IRC17:28
*** hemna has quit IRC17:46
*** diurnalist has quit IRC17:46
*** hemna has joined #openstack-meeting-alt17:47
*** macz_ has joined #openstack-meeting-alt17:53
*** geguileo has quit IRC18:03
*** macz_ has quit IRC18:08
*** esantos_63 has joined #openstack-meeting-alt18:12
*** esantos_63 is now known as ecsantos18:13
*** esantos_56 has joined #openstack-meeting-alt18:16
*** esantos_56 is now known as ecsantos18:17
*** ecsantos has quit IRC18:25
*** ecsantos91 has joined #openstack-meeting-alt18:30
*** ecsantos91 has quit IRC18:31
*** macz_ has joined #openstack-meeting-alt18:51
*** ralonsoh_ has quit IRC18:53
*** macz_ has quit IRC19:19
*** macz_ has joined #openstack-meeting-alt19:37
*** ajitha has quit IRC20:16
*** rcernin has joined #openstack-meeting-alt20:33
*** rcernin has quit IRC20:37
*** ircuser-1 has joined #openstack-meeting-alt20:55
*** rcernin has joined #openstack-meeting-alt21:02
*** e0ne has quit IRC21:24
*** baojg has quit IRC22:56
*** baojg has joined #openstack-meeting-alt22:57
*** tmazur has quit IRC23:08
*** baojg has quit IRC23:20
*** baojg has joined #openstack-meeting-alt23:21
*** rcernin has quit IRC23:35
*** rcernin has joined #openstack-meeting-alt23:35
*** baojg has quit IRC23:42
*** baojg has joined #openstack-meeting-alt23:42

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