| *** jamesmcarthur has quit IRC | 00:07 | |
| *** ayoung has quit IRC | 00:07 | |
| *** ayoung has joined #openstack-meeting-alt | 00:08 | |
| *** slaweq has joined #openstack-meeting-alt | 00:11 | |
| *** slaweq has quit IRC | 00:16 | |
| *** igordc has quit IRC | 00:28 | |
| *** tetsuro has joined #openstack-meeting-alt | 00:32 | |
| *** rfolco has joined #openstack-meeting-alt | 00:55 | |
| *** igordc has joined #openstack-meeting-alt | 00:59 | |
| *** gyee has quit IRC | 01:13 | |
| *** masahito has joined #openstack-meeting-alt | 01:14 | |
| *** ricolin has joined #openstack-meeting-alt | 01:14 | |
| *** ricolin has quit IRC | 01:17 | |
| *** ricolin_ is now known as ricolin | 01:18 | |
| *** rfolco has quit IRC | 01:29 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 01:47 | |
| *** jamesmcarthur has quit IRC | 02:06 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 02:11 | |
| *** slaweq has joined #openstack-meeting-alt | 02:11 | |
| *** slaweq has quit IRC | 02:16 | |
| *** jamesmcarthur has quit IRC | 02:18 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 02:18 | |
| *** jamesmcarthur has quit IRC | 02:24 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 02:49 | |
| *** ccamacho has quit IRC | 02:50 | |
| *** jamesmcarthur has quit IRC | 02:55 | |
| *** masahito has quit IRC | 03:19 | |
| *** masahito has joined #openstack-meeting-alt | 03:27 | |
| *** masahito_ has joined #openstack-meeting-alt | 03:29 | |
| *** masahito has quit IRC | 03:29 | |
| *** masahito_ has quit IRC | 03:32 | |
| *** masahito has joined #openstack-meeting-alt | 03:32 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 03:50 | |
| *** igordc has quit IRC | 04:08 | |
| *** slaweq has joined #openstack-meeting-alt | 04:11 | |
| *** slaweq has quit IRC | 04:16 | |
| *** masahito_ has joined #openstack-meeting-alt | 04:21 | |
| *** masahito has quit IRC | 04:21 | |
| *** jamesmcarthur has quit IRC | 04:25 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 04:28 | |
| *** jamesmcarthur has quit IRC | 04:33 | |
| *** ricolin has quit IRC | 04:42 | |
| *** masahito_ has quit IRC | 04:49 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 04:56 | |
| *** links has joined #openstack-meeting-alt | 05:00 | |
| *** jamesmcarthur has quit IRC | 05:02 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 05:58 | |
| *** jamesmcarthur has quit IRC | 06:03 | |
| *** slaweq has joined #openstack-meeting-alt | 06:11 | |
| *** slaweq has quit IRC | 06:16 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 06:38 | |
| *** jamesmcarthur has quit IRC | 06:42 | |
| *** masahito has joined #openstack-meeting-alt | 06:57 | |
| *** apetrich has joined #openstack-meeting-alt | 07:01 | |
| *** slaweq has joined #openstack-meeting-alt | 07:06 | |
| *** apetrich has quit IRC | 07:22 | |
| *** jtomasek has joined #openstack-meeting-alt | 07:22 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 07:39 | |
| *** jamesmcarthur has quit IRC | 07:44 | |
| *** jtomasek has quit IRC | 07:47 | |
| *** tesseract has joined #openstack-meeting-alt | 07:47 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 07:55 | |
| *** jamesmcarthur has quit IRC | 07:59 | |
| *** ccamacho has joined #openstack-meeting-alt | 08:19 | |
| *** jtomasek has joined #openstack-meeting-alt | 08:25 | |
| *** tmazur has joined #openstack-meeting-alt | 08:34 | |
| *** apetrich has joined #openstack-meeting-alt | 08:48 | |
| *** e0ne has joined #openstack-meeting-alt | 09:07 | |
| *** derekh has joined #openstack-meeting-alt | 09:33 | |
| *** e0ne has quit IRC | 09:54 | |
| *** masahito has quit IRC | 10:24 | |
| *** dviroel has joined #openstack-meeting-alt | 10:36 | |
| *** apetrich has quit IRC | 10:47 | |
| *** e0ne has joined #openstack-meeting-alt | 11:07 | |
| *** rfolco has joined #openstack-meeting-alt | 12:08 | |
| *** vhari has joined #openstack-meeting-alt | 12:16 | |
| *** raildo has joined #openstack-meeting-alt | 12:27 | |
| *** mnaser has joined #openstack-meeting-alt | 12:34 | |
| *** apetrich has joined #openstack-meeting-alt | 13:29 | |
| *** trident has joined #openstack-meeting-alt | 13:49 | |
| *** links has quit IRC | 14:33 | |
| *** maaritamm has joined #openstack-meeting-alt | 14:50 | |
| *** andrebeltrami has joined #openstack-meeting-alt | 14:54 | |
| *** ricolin has joined #openstack-meeting-alt | 14:58 | |
| gouthamr | #startmeeting manila | 15:01 |
|---|---|---|
| openstack | Meeting started Thu Jan 30 15:01:17 2020 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| *** openstack changes topic to " (Meeting topic: manila)" | 15:01 | |
| openstack | The meeting name has been set to 'manila' | 15:01 |
| vkmc | o/ | 15:01 |
| dviroel | hi | 15:01 |
| lseki | o/ | 15:01 |
| carloss | hi | 15:01 |
| amito | o/ hello! | 15:01 |
| maaritamm | o/ | 15:01 |
| tbarron | \o/ | 15:01 |
| gouthamr | courtesy ping: xyang toabctl ganso jgrosso | 15:02 |
| gouthamr | hello everyone o/ | 15:02 |
| vhari | o/ | 15:02 |
| carthaca | hi | 15:02 |
| gouthamr | Here's the meeting agenda: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting | 15:02 |
| gouthamr | let's get started! | 15:03 |
| gouthamr | #topic Announcements | 15:03 |
| *** openstack changes topic to "Announcements (Meeting topic: manila)" | 15:03 | |
| gouthamr | sticky announcement topic regarding the release schedule: | 15:03 |
| gouthamr | #link https://releases.openstack.org/ussuri/schedule.html (Ussuri Release Schedule) | 15:03 |
| gouthamr | We're two weeks away from new specification freeze | 15:04 |
| gouthamr | and the code submission/testing freeze for brand new drivers | 15:04 |
| gouthamr | Thanks for all teh reviews so far on the specs, we'll talk about a couple in a bit | 15:05 |
| *** danielarthurt has joined #openstack-meeting-alt | 15:05 | |
| gouthamr | next, we have a date/venue announcement for the next PTG | 15:05 |
| *** trident has quit IRC | 15:06 | |
| gouthamr | OpenDev+PTG event will be in Vancouver between June 8-11, 2020 | 15:06 |
| lseki | 🎉 | 15:06 |
| dviroel | \o/ | 15:06 |
| gouthamr | couple of useful links that were shared on the openstack-discuss mailing list: | 15:06 |
| gouthamr | #link https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer (Volunteer for Program Committee, Track Moderation and Suggest topics for Moderated discussions) | 15:06 |
| gouthamr | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012239.html (Relevant mailing list thread) | 15:06 |
| gouthamr | i'm especially proud that the OpenStack community made the right choice with the name | 15:06 |
| gouthamr | personally think it's in honor of a rockstar amongst us :) | 15:07 |
| vkmc | yaay Vancouver | 15:07 |
| tbarron | heh | 15:07 |
| gouthamr | we'll release Victoria in Vancouver | 15:08 |
| gouthamr | or start working on it there at least :P | 15:08 |
| tbarron | watch out Vancouver | 15:08 |
| vkmc | hahaha | 15:08 |
| gouthamr | that's all i had in terms of announcements | 15:08 |
| gouthamr | anyone else got any? | 15:09 |
| gouthamr | #topic Rocky release is going to Extended Maintenance (EM) | 15:09 |
| *** openstack changes topic to "Rocky release is going to Extended Maintenance (EM) (Meeting topic: manila)" | 15:09 | |
| gouthamr | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html (Extended Maintenance Announcement for OpenStack Rocky) | 15:09 |
| gouthamr | #link https://etherpad.openstack.org/p/manila-stable-rocky-em (Manila Etherpad tracking unreleased Rocky changes) | 15:09 |
| gouthamr | ^ couple of pointers and a heads-up to those on the Rocky release | 15:10 |
| gouthamr | if you have any bugfixes that need to make it into the last release, let me know or update ^ etherpad | 15:10 |
| gouthamr | i think there are a couple of fixes that are making their way back through train and stein, we'll see if they make it by Feb 24th | 15:11 |
| gouthamr | a reminder that we will no longer tag a release when marked as being in "extended maintenance" | 15:12 |
| gouthamr | also, CI will be best effort - if testing/infrastructure projects break on such releases, we will not prioritize fixing them | 15:13 |
| gouthamr | backports ofcourse will be welcome as long as we can test them reasonably | 15:14 |
| gouthamr | alright, that's all the back of the label said | 15:14 |
| gouthamr | #topic Third Party CI check (dviroel) | 15:15 |
| *** openstack changes topic to "Third Party CI check (dviroel) (Meeting topic: manila)" | 15:15 | |
| dviroel | o | 15:15 |
| dviroel | o/ | 15:15 |
| gouthamr | you're up dviroel - i'll play support cast to this topic | 15:15 |
| dviroel | alright, at the end of the train release we started a spreadsheet with all third party drivers and their status | 15:16 |
| *** trident has joined #openstack-meeting-alt | 15:17 | |
| dviroel | some changes were triggered for master and stable branches to check CIs status and also their python versions | 15:17 |
| dviroel | the spreadsheet is the following | 15:17 |
| dviroel | #link https://docs.google.com/spreadsheets/d/1dBSCqtQKoyFMX6oWTahhP9Z133NRFW3ynezq1CItx8M/edit#gid=0 | 15:17 |
| dviroel | regarding stable branches, there isn't too much to say, it seems that only NetApp and INFINItDAT are reporting tests results | 15:18 |
| dviroel | In master we have a few more drivers running tests and Dell that was still running on py2.7 | 15:19 |
| amito | And we seem to be failing on those... | 15:19 |
| dviroel | amito: yep | 15:19 |
| amito | dviroel: I'll look into this... and also change the contact email to my email instead of the general "support@..." one | 15:20 |
| dviroel | Dell CI seems stable lately so the python version may be outdated | 15:20 |
| gouthamr | dviroel: thank you for taking the effort to put this information together so diligently | 15:21 |
| dviroel | Now, I want to know from you the next steps on this. | 15:21 |
| *** bobmel has quit IRC | 15:21 | |
| gouthamr | dviroel: do we edit stuff, or just comment? | 15:21 |
| dviroel | It is looked for edit, but I can change the permission so you all can edit | 15:22 |
| gouthamr | dviroel: i may have updates regarding Dell/EMC because i spoke to a bunch of their developers over email right before PTG | 15:22 |
| gouthamr | there may be an update on the list of owners/emails for those drivers | 15:23 |
| dviroel | gouthamr: cool, thanks | 15:23 |
| dviroel | should we move forward now and send a email to the maintainers asking for updates? | 15:24 |
| gouthamr | this link is useful on the manila wiki | 15:24 |
| gouthamr | dviroel: yes, we could post this to openstack-discuss and allow maintainers to comment | 15:24 |
| amito | dviroel: we'll look into the failures on the stable/* branches. | 15:25 |
| gouthamr | amito: +1 | 15:25 |
| *** bobmel has joined #openstack-meeting-alt | 15:25 | |
| dviroel | gouthamr: sure, this is an important info to be added to the wiki | 15:25 |
| dviroel | amito: thanks | 15:26 |
| gouthamr | a few releases ago, we decided to relax the CI requirements on stable branches, especially because of fast-changing and flaky test infrastructure | 15:26 |
| gouthamr | we still look for a vendor/maintainer to assure us that they've tested a patch before we merge it to stable branches | 15:27 |
| *** ccamacho has quit IRC | 15:27 | |
| gouthamr | so if the CI isn't working for a particular reason, let us know - we can possibly also help you find a fix | 15:27 |
| dviroel | ++ | 15:28 |
| *** bobmel has quit IRC | 15:28 | |
| dviroel | so, thats it for now | 15:28 |
| gouthamr | test infrastructure has gotten a whole lot more stable: devstack-gate is frozen, tempest-lib got us away from compatibility issues, if you're using zuulv3 - it's been far more stable than v2/v2.5 imo | 15:29 |
| dviroel | we'll update the table again and send an email on the list and to the maintainers | 15:29 |
| gouthamr | dviroel++ thank you | 15:29 |
| dviroel | gouthamr: yw | 15:29 |
| gouthamr | dviroel: be sure to remind folks in your email that Train+ is expected to be run with python3 | 15:30 |
| dviroel | gouthamr: ok | 15:30 |
| gouthamr | here's a link: https://governance.openstack.org/tc/goals/selected/train/python3-updates.html | 15:31 |
| gouthamr | Train is expected to be tested on 3.6 and/or 3.7, because that's what customers will be running it on | 15:31 |
| gouthamr | Ussuri's python support is going to be the same, expect changes in the Victoria cycle.. | 15:32 |
| gouthamr | alright, anything else for the moment on this $topic? | 15:32 |
| gouthamr | thanks, moving on... | 15:33 |
| gouthamr | #topic Replication quotas (carloss/carthaca) | 15:33 |
| *** openstack changes topic to "Replication quotas (carloss/carthaca) (Meeting topic: manila)" | 15:33 | |
| gouthamr | thanks for joining us, carthaca, carloss - floor is yours.. | 15:33 |
| carloss | thanks, gouthamr | 15:33 |
| carloss | we have had some discussions about this topic previously... | 15:34 |
| carloss | it was basically: fix the issue using share type extra specs x existent quota system | 15:34 |
| carloss | in the remote-only PTG we have had further discussions and agreed to use the share type extra specs as a solution | 15:35 |
| carloss | I've opened a bug few months ago and we have been updating it with some details and suggestions... | 15:35 |
| carloss | #link https://bugs.launchpad.net/manila/+bug/1850545 | 15:35 |
| openstack | Launchpad bug 1850545 in Manila "Manila allows the creation of unlimited share replicas" [Medium,In progress] - Assigned to Carlos Eduardo (silvacarlose) | 15:35 |
| carloss | carthaca noticed the bug and saw a comment of mine talking about the solution | 15:36 |
| carloss | also, added a suggestion in an administator point of view, justifying that would be nice if we implement both approaches since they aren't mutually exclusive | 15:36 |
| carloss | #link https://bugs.launchpad.net/manila/+bug/1850545/comments/6 | 15:36 |
| carloss | so we wanted to bring this topic to the meeting and have more people discussing about the B solution | 15:37 |
| tbarron | I think B needs to be given some weight since the request for it comes from a real deployment, not just from us thinking about the problem a priori | 15:38 |
| dviroel | tbarron++ | 15:39 |
| tbarron | but A is is independent, right? that is, A could merge without having to wait for B | 15:39 |
| vkmc | tbarron++ | 15:39 |
| carloss | tbarron++ | 15:39 |
| carthaca | yes, I think it is independent | 15:39 |
| carloss | yes, tbarron... | 15:40 |
| vkmc | seems that A fixes the problem easily in the short term, but B is a better (but more complex to implement) solution | 15:40 |
| vkmc | imho | 15:40 |
| gouthamr | makes sense | 15:40 |
| tbarron | vkmc: s/imho/imo/ you are a rockstar now | 15:41 |
| dviroel | A also fixes the problem of having backends with limited replicas per share, that may be another issue to be addressed | 15:41 |
| vkmc | tbarron, lol | 15:41 |
| gouthamr | carthaca: quota of share replicas per *project* - do you mean a total count of replicas alone, or sizes as well? | 15:41 |
| gouthamr | we have both number and size in our quotas | 15:42 |
| carloss | good question, gouthamr | 15:42 |
| dviroel | ++ | 15:43 |
| carthaca | sizes as well, its important for capacity planning | 15:43 |
| carloss | gouthamr, does the implementation for B needs a spec or lite-spec? | 15:44 |
| carloss | or just a blueprint is enough? | 15:44 |
| gouthamr | yeah, thinking about that for a minute, there doesn't seem to be an issue to include this in our quota system - especially because the "secondary" backends are also managed by manila, perhaps elsewhere | 15:44 |
| *** ricolin has quit IRC | 15:45 | |
| gouthamr | carloss: up to you, i don't see any API changes - so i don't mind you including this in your current spec too | 15:45 |
| *** priteau has joined #openstack-meeting-alt | 15:45 | |
| carloss | great | 15:46 |
| carloss | I've noticed that you have created a blueprint in the past (https://blueprints.launchpad.net/manila/+spec/add-share-replica-quotas) which seems somehow related to B solution | 15:46 |
| carloss | is it correct? or is this something different? | 15:47 |
| gouthamr | carloss: have you checked the feasibility of this with our user and share type quotas? | 15:47 |
| carloss | not deeply | 15:47 |
| gouthamr | carloss: yes, this tenant wide quota was the initial proposal | 15:48 |
| carloss | but I don't see any issues coming at moment | 15:48 |
| gouthamr | carloss: cool, we can brainstorm this when you take a look - things to consider would be to provide teh consistency we currently have with project quotas, share type and user quotas | 15:48 |
| carloss | alright | 15:49 |
| *** jgrosso has joined #openstack-meeting-alt | 15:50 | |
| gouthamr | thanks for bringing the questions here carloss, carthaca - looks like we are in agreement that the two part solution that we have can be implemented - and done so independently | 15:50 |
| carloss | yes... yw, gouthamr | 15:51 |
| carloss | that's all I had for this topic | 15:51 |
| carloss | thank you all :) | 15:51 |
| carthaca | thanks | 15:51 |
| gouthamr | you're welcome.. let's chase the next topic | 15:52 |
| gouthamr | #topic Tracking our work | 15:52 |
| *** openstack changes topic to "Tracking our work (Meeting topic: manila)" | 15:52 | |
| *** diurnalist has joined #openstack-meeting-alt | 15:52 | |
| gouthamr | First up, specifications that need reviews: | 15:52 |
| gouthamr | #link https://review.opendev.org/#/c/700776/ (Update Create Share from Snapshot in Another Pool) | 15:52 |
| gouthamr | i had a couple of questions on that dviroel - although i agree with the general direction this spec is taking | 15:53 |
| gouthamr | carthaca - your inputs would be valuable as well | 15:53 |
| dviroel | gouthamr: sure, will answer all comments soon | 15:53 |
| dviroel | thank you all for reviewing it | 15:53 |
| gouthamr | ack, more reviews are welcome - i'd like to get this spec merged before the deadline.. | 15:54 |
| gouthamr | #link https://review.opendev.org/#/c/704793/ (Add lite spec to fix unlimited share replicas per share) | 15:54 |
| gouthamr | ^ deja vu | 15:54 |
| carloss | haha | 15:54 |
| dviroel | carloss: could you mention quotas as an alternative solution in this spec? | 15:55 |
| carloss | yes, gouthamr | 15:55 |
| carloss | I'll add a comment on the change | 15:55 |
| gouthamr | dviroel: not an alternative, supplementary | 15:55 |
| dviroel | gouthamr: yep | 15:56 |
| gouthamr | Reviews needing attention: | 15:56 |
| gouthamr | Noop interface driver (mnaser) | 15:56 |
| gouthamr | #link https://review.opendev.org/#/c/704807/ | 15:56 |
| mnaser | hola | 15:56 |
| gouthamr | hey mnaser | 15:56 |
| mnaser | so with my work on this i actually found a bunch of other tidbits and ended up with a stack here - https://review.opendev.org/#/c/705034/4 | 15:57 |
| vkmc | hola mnaser, bienvenido! | 15:57 |
| mnaser | hi vkmc gouthamr :) | 15:57 |
| gouthamr | #link https://review.opendev.org/#/q/topic:manila/generic-improvements+(status:open+OR+status:merged) | 15:57 |
| mnaser | some are very trivial (i.e. flavor id assumption) and some are a bit more convuluted. but the overall idea is moving more stuff from service_instance out to linux interface | 15:57 |
| mnaser | so the noop can be a real noop | 15:58 |
| tbarron | fwiw i reloaded the agenda with the other patches too | 15:58 |
| mnaser | (the whole idea behind it is that this is an environment where manila-share is *ALREADY* inside the admin network) | 15:58 |
| tbarron | but wanted mnaser to explain his overall project/goals and get eyes on these | 15:58 |
| mnaser | so there's no need to have neutron-(openvswitch|linuxbridge)-agent wiring things back and forth, because it's already sitting on the correct network | 15:58 |
| tbarron | it's great to see work on the neglected generic driver service instance module | 15:58 |
| mnaser | o/ | 15:59 |
| mnaser | yep, it's actually pretty well setup and laid out tbh | 15:59 |
| mnaser | given time constraints, i hope to improve the image elements too, they're pretty old and actually we can just use built in diskimage-builder stuff at this point | 16:00 |
| mnaser | but i'm trying to get these bits to work for now. i'm just trying to get it to work first, once i get that, i'll try to fix up the tests if any and what not | 16:00 |
| mnaser | but uh, how do we feel about the overall idea about generic driver possibly not controlling network bits on the host | 16:01 |
| gouthamr | nice, thank you mnaser | 16:01 |
| tbarron | mnaser: i think our intent was to have a plugin model that allows lots of network options and | 16:02 |
| gouthamr | mnaser: i don't see a problem with the noop driver - how would you test this on a devstack though? | 16:02 |
| tbarron | that what you are doing is consistent with that | 16:02 |
| tbarron | we're overtime and may need to move to #openstack-manila | 16:03 |
| gouthamr | oh wow :O | 16:03 |
| gouthamr | lost track, ty tbarron | 16:03 |
| gouthamr | sorry we can't get to bugs today vkmc | 16:03 |
| gouthamr | vhari ^ | 16:03 |
| mnaser | given time constraints, we can discuss the details later if need be | 16:03 |
| vhari | gouthamr, nw :D | 16:03 |
| gouthamr | thanks all of you for joining, see you on #openstack-manila | 16:03 |
| gouthamr | #endmeeting | 16:04 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:04 | |
| openstack | Meeting ended Thu Jan 30 16:04:00 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:04 |
| dviroel | tks | 16:04 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-01-30-15.01.html | 16:04 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-01-30-15.01.txt | 16:04 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-01-30-15.01.log.html | 16:04 |
| priteau | #startmeeting blazar | 16:04 |
| openstack | Meeting started Thu Jan 30 16:04:44 2020 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:04 |
| *** openstack changes topic to " (Meeting topic: blazar)" | 16:04 | |
| openstack | The meeting name has been set to 'blazar' | 16:04 |
| *** gyee has joined #openstack-meeting-alt | 16:04 | |
| priteau | #topic Roll call | 16:05 |
| *** openstack changes topic to "Roll call (Meeting topic: blazar)" | 16:05 | |
| *** jakecoll has joined #openstack-meeting-alt | 16:05 | |
| diurnalist | o/ | 16:05 |
| jakecoll | o/ | 16:06 |
| priteau | Hi diurnalist, jakecoll | 16:06 |
| jakecoll | good monring | 16:06 |
| diurnalist | hey | 16:06 |
| priteau | Agenda for today: | 16:06 |
| priteau | * Ussuri planning and priorities | 16:06 |
| priteau | * Upstream contributions | 16:06 |
| priteau | * AOB | 16:06 |
| priteau | #topic Ussuri planning and priorities | 16:06 |
| *** openstack changes topic to "Ussuri planning and priorities (Meeting topic: blazar)" | 16:06 | |
| priteau | Our initial post-PTG planning is at https://etherpad.openstack.org/p/blazar-ptg-ussuri | 16:07 |
| priteau | I am afraid we're already quite late compared to the tentative schedule I had proposed | 16:07 |
| priteau | I've focused on the preemtible spec as that's the main priority for us | 16:07 |
| jakecoll | Really? Pre-emptible is a priority now? | 16:08 |
| priteau | I mean for us = for my employer | 16:09 |
| priteau | Not for us = Blazar project | 16:09 |
| jakecoll | OVH involved in that at all? | 16:09 |
| priteau | I've heard they were interested by the idea but they're not involved. | 16:10 |
| priteau | diurnalist: a few weeks ago jakecoll was telling me that time to contribute to upstream Blazar was very limited, is it still the case? I would really like to get at least network reservation upstream. | 16:10 |
| diurnalist | priteau: I would like that too, but what does this entail precisely, given that it's already written and in production here? | 16:11 |
| priteau | There were some comments to answer on the spec: https://review.opendev.org/#/c/674089/ | 16:12 |
| diurnalist | thanks, i always forget there is a separate project for specs | 16:13 |
| priteau | I've added you as a reviewer of the change | 16:13 |
| diurnalist | so i understand, the plan would be to review/address comments, then the spec is merged, then submit a changeset for the feature (with doc updates), and then done? | 16:14 |
| priteau | On a cursory look the comments are minor, so if we can get the spec updated and approved, it will unlock review & merge of the code. | 16:14 |
| priteau | That's pretty much it. The iteration on the spec might lead to some code changes but probably nothing major. | 16:15 |
| diurnalist | there has been less appetite for committing time to blazar lately, but given that preemptible instances might be forthcoming, we can probably make a stronger case for this | 16:16 |
| priteau | Are you interested by preemptibles in Chameleon? | 16:16 |
| jakecoll | I am. I can't speak for Kate | 16:17 |
| priteau | Cool, I didn't that. | 16:17 |
| jakecoll | They make less sense now that we delete reservations that don't launch instances in six hours | 16:17 |
| priteau | But nevermind preemptibles, if network reservation can be merged, that's one less change you have to worry about maintaining. | 16:18 |
| jakecoll | But we had pretty low utilization of our leases before, especially on GPUs | 16:18 |
| jakecoll | Make sense for high-demand resources | 16:18 |
| diurnalist | yeah. i'm a bit skeptical it will work nicely in our model, where users typically want guaranteed access for some time. but it could be interesting, who knows | 16:18 |
| diurnalist | priteau: we would deploy it, i think | 16:18 |
| diurnalist | priteau: the main priority from our PoV is the usage enforcement, as it ties in with other work we are doing around how we manage quotas/allocations on our cloud. maybe we should take ownership of that one. | 16:19 |
| priteau | Note that the preemptibles design I am proposing is to fill up space between reservations, not within active-but-unused reservations. | 16:19 |
| priteau | diurnalist: re usage enforcement, that would be ideal. I don't have the time to push this forward at the moment. | 16:19 |
| diurnalist | OK, i see there is a pre-existing spec already, i'll have a look and update w/ some of my more recent ideas | 16:22 |
| diurnalist | so i am aware, what is the quota feature? | 16:23 |
| priteau | Thanks a lot. We just need to make sure it's generic enough to cover most use cases, not just Chameleon | 16:23 |
| diurnalist | is it just making sure that blazar doesn't allow doing things that exceed quotas? | 16:23 |
| diurnalist | priteau: of course | 16:23 |
| priteau | That's integration with existing OpenStack quota. Currently, in the absence of usage enforcement, any Blazar user can reserve large amounts of resources, even if their quota says they can only run N instances | 16:24 |
| diurnalist | right, jakecoll and I were discussing this the other day, by chance | 16:24 |
| diurnalist | OK, makes sense | 16:24 |
| priteau | So either limit leases compared to the Nova quota for instances, or introduce a separate quota | 16:25 |
| diurnalist | any idea how that will affect host reservations? | 16:25 |
| diurnalist | i presume that would involve a new quota | 16:25 |
| priteau | Host reservation is the tricky bit, because you don't know in advance how many instances might be launched on a hypervisor (unless you have just one flavor) | 16:26 |
| priteau | Maybe host reservation needs a separate quota, and instance reservation can sync with Nova's quota | 16:26 |
| diurnalist | right | 16:27 |
| priteau | Feel free to share ideas via etherpad documents if they are not ready to be shared as a spec | 16:27 |
| priteau | https://etherpad.openstack.org/ | 16:27 |
| priteau | Just create a new doc and link it from https://etherpad.openstack.org/p/blazar-ptg-ussuri | 16:27 |
| diurnalist | :+1: | 16:28 |
| priteau | I guess we've covered priorities | 16:29 |
| priteau | #topic Upstream contributions | 16:29 |
| *** openstack changes topic to "Upstream contributions (Meeting topic: blazar)" | 16:29 | |
| priteau | I was just taking a look at your latest proposed change | 16:29 |
| priteau | https://review.opendev.org/#/c/704628/ | 16:29 |
| priteau | I've fixed the zuul checks, mock 3.0.0 was needed (plus removal of extra newlines) | 16:30 |
| priteau | I'll take a look later (probably only next week as I am off tomorrow) at the actual code | 16:30 |
| priteau | Is this a change that improves a specific use case? | 16:31 |
| jakecoll | It's a bug fix | 16:32 |
| diurnalist | yes, any time a system uses the blazarclient to fetch a lease. mostly, the horizon lease detail page | 16:32 |
| diurnalist | the blazarclient will fetch a list of all leases, iterate over them to find one with the given ID, then return that ID. then it will fetch the lease with that ID. | 16:32 |
| diurnalist | skipping the first step saves an expensive call. something i found when trying to figure out why blazardashboard is so slow | 16:33 |
| priteau | Nice improvement | 16:34 |
| diurnalist | i didn't file a bug in blazardashboard or anything, so it appears a bit out of the blue. but i wasn't sure a bug report was appropriate in this case | 16:35 |
| priteau | Not strictly necessary, but it's helpful to keep track of improvements. More so on the service side, to keep track of what we should backport. | 16:36 |
| diurnalist | OK | 16:37 |
| priteau | And it also bumps your institution's counter of "Fixed bugs" on Stackalytics ;-) | 16:38 |
| diurnalist | haha | 16:38 |
| priteau | We've covered other contributions in the previous agenda item | 16:41 |
| priteau | #topic AOB | 16:41 |
| *** openstack changes topic to "AOB (Meeting topic: blazar)" | 16:41 | |
| priteau | Anything else to discuss today? | 16:41 |
| jakecoll | I don't have anything at the moment | 16:42 |
| priteau | Thanks a lot for joining today, it was good to sync | 16:44 |
| jakecoll | :+1: | 16:44 |
| priteau | Bye | 16:44 |
| priteau | #endmeeting | 16:44 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:44 | |
| openstack | Meeting ended Thu Jan 30 16:44:39 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:44 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-01-30-16.04.html | 16:44 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-01-30-16.04.txt | 16:44 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-01-30-16.04.log.html | 16:44 |
| *** jakecoll has quit IRC | 16:45 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 16:54 | |
| *** vhari has quit IRC | 16:59 | |
| *** tesseract has quit IRC | 17:08 | |
| *** priteau has quit IRC | 17:21 | |
| *** tmazur has quit IRC | 17:31 | |
| *** e0ne has quit IRC | 17:36 | |
| *** bobmel has joined #openstack-meeting-alt | 17:56 | |
| *** derekh has quit IRC | 18:00 | |
| *** igordc has joined #openstack-meeting-alt | 18:09 | |
| *** danielarthurt has quit IRC | 18:10 | |
| *** andrebeltrami has quit IRC | 18:13 | |
| *** diurnalist has quit IRC | 18:20 | |
| *** diurnalist has joined #openstack-meeting-alt | 18:22 | |
| *** bnemec has joined #openstack-meeting-alt | 18:41 | |
| *** bobmel has quit IRC | 18:55 | |
| *** bobmel has joined #openstack-meeting-alt | 18:56 | |
| *** bobmel has quit IRC | 19:00 | |
| *** bnemec has quit IRC | 19:24 | |
| *** e0ne has joined #openstack-meeting-alt | 19:27 | |
| *** e0ne has quit IRC | 19:33 | |
| *** diurnalist has quit IRC | 20:00 | |
| *** diurnalist has joined #openstack-meeting-alt | 20:13 | |
| *** rcernin has quit IRC | 20:36 | |
| *** jtomasek has quit IRC | 20:38 | |
| *** jamesmcarthur has quit IRC | 20:39 | |
| *** jtomasek has joined #openstack-meeting-alt | 20:41 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 20:49 | |
| *** jamesmcarthur has quit IRC | 20:53 | |
| *** apetrich has quit IRC | 20:55 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 20:57 | |
| *** jamesmcarthur has quit IRC | 21:02 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 21:03 | |
| *** jamesmcarthur has quit IRC | 21:10 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 21:10 | |
| *** rfolco has quit IRC | 21:24 | |
| *** rfolco has joined #openstack-meeting-alt | 21:24 | |
| *** jamesmcarthur has quit IRC | 21:25 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 21:27 | |
| *** jamesmcarthur has quit IRC | 21:29 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 21:35 | |
| *** slaweq has quit IRC | 21:43 | |
| *** slaweq has joined #openstack-meeting-alt | 21:45 | |
| *** jamesmcarthur has quit IRC | 21:49 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 21:51 | |
| *** slaweq has quit IRC | 21:55 | |
| *** jamesmcarthur has quit IRC | 21:57 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 22:03 | |
| *** jamesmcarthur_ has joined #openstack-meeting-alt | 22:05 | |
| *** jamesmcarthur has quit IRC | 22:08 | |
| *** jamesmcarthur_ has quit IRC | 22:08 | |
| *** jamesmcarthur has joined #openstack-meeting-alt | 22:09 | |
| *** jgrosso has quit IRC | 22:09 | |
| *** jamesmcarthur has quit IRC | 22:11 | |
| *** ayoung has quit IRC | 22:14 | |
| *** diurnalist has quit IRC | 22:21 | |
| *** raildo has quit IRC | 22:33 | |
| *** apetrich has joined #openstack-meeting-alt | 22:55 | |
| *** diurnalist has joined #openstack-meeting-alt | 23:05 | |
| *** rcernin has joined #openstack-meeting-alt | 23:20 | |
| *** dviroel has quit IRC | 23:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!