| *** enriquetaso has quit IRC | 00:04 | |
| *** tetsuro has joined #openstack-meeting-alt | 00:10 | |
| *** rfolco has quit IRC | 00:30 | |
| *** andrebeltrami has quit IRC | 00:53 | |
| *** ttsiouts has joined #openstack-meeting-alt | 01:00 | |
| *** ricolin has joined #openstack-meeting-alt | 01:13 | |
| *** ricolin_ has joined #openstack-meeting-alt | 01:18 | |
| *** ricolin has quit IRC | 01:21 | |
| *** ttsiouts has quit IRC | 01:34 | |
| *** lbragstad has quit IRC | 01:38 | |
| *** ttsiouts has joined #openstack-meeting-alt | 02:03 | |
| *** ttsiouts has quit IRC | 02:07 | |
| *** apetrich has quit IRC | 02:09 | |
| *** ysandeep|away is now known as ysandeep|rover | 02:11 | |
| *** tetsuro has quit IRC | 02:29 | |
| *** tetsuro has joined #openstack-meeting-alt | 02:32 | |
| *** ttsiouts has joined #openstack-meeting-alt | 02:36 | |
| *** ttsiouts has quit IRC | 03:10 | |
| *** ysandeep|rover is now known as ysandeep|BRB | 04:08 | |
| *** ttsiouts has joined #openstack-meeting-alt | 04:12 | |
| *** gyee has quit IRC | 04:13 | |
| *** ysandeep|BRB is now known as ysandeep|rover | 04:23 | |
| *** ttsiouts has quit IRC | 04:46 | |
| *** ttsiouts has joined #openstack-meeting-alt | 05:22 | |
| *** ttsiouts has quit IRC | 05:27 | |
| *** vishalmanchanda has joined #openstack-meeting-alt | 05:40 | |
| *** tobberydberg has joined #openstack-meeting-alt | 05:46 | |
| *** ttsiouts has joined #openstack-meeting-alt | 05:55 | |
| *** maaritamm has joined #openstack-meeting-alt | 06:07 | |
| *** ttsiouts has quit IRC | 06:29 | |
| *** slaweq_ has joined #openstack-meeting-alt | 06:37 | |
| *** rdopiera has joined #openstack-meeting-alt | 06:46 | |
| *** ttsiouts has joined #openstack-meeting-alt | 06:51 | |
| *** ttsiouts has quit IRC | 06:51 | |
| *** ttsiouts has joined #openstack-meeting-alt | 06:52 | |
| *** lpetrut has joined #openstack-meeting-alt | 07:07 | |
| *** ccamacho has joined #openstack-meeting-alt | 07:11 | |
| *** maaritamm has quit IRC | 07:45 | |
| *** ysandeep|rover is now known as ysandeep|lunch | 07:48 | |
| *** maaritamm has joined #openstack-meeting-alt | 07:54 | |
| *** links has joined #openstack-meeting-alt | 07:56 | |
| *** slaweq_ is now known as slaweq | 08:10 | |
| *** e0ne has joined #openstack-meeting-alt | 08:12 | |
| *** ttsiouts has quit IRC | 08:13 | |
| *** ttsiouts has joined #openstack-meeting-alt | 08:19 | |
| *** ccamacho has quit IRC | 08:20 | |
| *** ricolin_ is now known as ricolin | 08:30 | |
| *** maaritamm has quit IRC | 08:39 | |
| *** ysandeep|lunch is now known as ysandeep|rover | 08:40 | |
| *** ccamacho has joined #openstack-meeting-alt | 08:40 | |
| *** ccamacho has quit IRC | 08:40 | |
| *** ccamacho has joined #openstack-meeting-alt | 08:45 | |
| *** tetsuro has quit IRC | 08:45 | |
| *** apetrich has joined #openstack-meeting-alt | 09:16 | |
| *** maaritamm has joined #openstack-meeting-alt | 09:36 | |
| *** ccamacho has quit IRC | 09:44 | |
| *** ccamacho has joined #openstack-meeting-alt | 10:05 | |
| *** ttsiouts has quit IRC | 10:07 | |
| *** ttsiouts has joined #openstack-meeting-alt | 10:11 | |
| *** derekh has joined #openstack-meeting-alt | 10:49 | |
| *** e0ne has quit IRC | 10:52 | |
| *** e0ne has joined #openstack-meeting-alt | 10:53 | |
| *** jtomasek has quit IRC | 10:56 | |
| *** ysandeep|rover is now known as ysandeep|coffee | 11:00 | |
| *** jtomasek has joined #openstack-meeting-alt | 11:02 | |
| *** ysandeep|coffee is now known as ysandeep|rover | 11:17 | |
| *** geguileo has quit IRC | 11:29 | |
| *** ganso has joined #openstack-meeting-alt | 11:34 | |
| *** ttsiouts has quit IRC | 11:59 | |
| *** rfolco has joined #openstack-meeting-alt | 12:17 | |
| *** ttsiouts has joined #openstack-meeting-alt | 12:20 | |
| *** raildo has joined #openstack-meeting-alt | 12:28 | |
| *** enriquetaso has joined #openstack-meeting-alt | 12:36 | |
| *** maaritamm has quit IRC | 12:46 | |
| *** maaritamm has joined #openstack-meeting-alt | 12:47 | |
| *** ttsiouts has quit IRC | 12:53 | |
| *** gshippey has joined #openstack-meeting-alt | 12:57 | |
| *** ttsiouts has joined #openstack-meeting-alt | 13:13 | |
| *** lbragstad has joined #openstack-meeting-alt | 13:14 | |
| *** ysandeep|rover is now known as ysandeep|away | 13:32 | |
| *** liuyulong has joined #openstack-meeting-alt | 13:33 | |
| *** rcernin has quit IRC | 13:37 | |
| *** eharney has joined #openstack-meeting-alt | 13:50 | |
| *** rosmaita has joined #openstack-meeting-alt | 13:52 | |
| *** Liang__ has joined #openstack-meeting-alt | 13:53 | |
| *** Liang__ is now known as LiangFang | 13:54 | |
| *** ruffian_sheep has joined #openstack-meeting-alt | 13:56 | |
| *** tosky has joined #openstack-meeting-alt | 13:57 | |
| rosmaita | #startmeeting cinder | 14:00 |
|---|---|---|
| rosmaita | #link https://etherpad.openstack.org/p/cinder-ussuri-meetings | 14:00 |
| rosmaita | #topic roll call | 14:00 |
| openstack | Meeting started Wed Apr 15 14:00:02 2020 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| *** ruffian_sheep36 has joined #openstack-meeting-alt | 14:00 | |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: cinder)" | 14:00 | |
| openstack | The meeting name has been set to 'cinder' | 14:00 |
| *** openstack changes topic to "roll call (Meeting topic: cinder)" | 14:00 | |
| rajinir | hi | 14:00 |
| LiangFang | hi | 14:00 |
| ganso | o/ | 14:00 |
| m5z | hi | 14:00 |
| eharney | hi | 14:00 |
| vkmc | o/ | 14:00 |
| smcginnis | o/ | 14:01 |
| whoami-rajat | Hi | 14:01 |
| jungleboyj | o/ | 14:01 |
| tosky | o/ | 14:01 |
| rosmaita | lots on the agenda today so i'll get started | 14:01 |
| rosmaita | #topic announcements | 14:01 |
| *** openstack changes topic to "announcements (Meeting topic: cinder)" | 14:01 | |
| rosmaita | {mitaka,newton}-driverfixes branches have been tagged eol and deleted | 14:01 |
| rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014055.html | 14:02 |
| rosmaita | we agreed to do this a few months ago, but it required some manual intervention to make it happen | 14:02 |
| *** ruffian_sheep has quit IRC | 14:02 | |
| rosmaita | if you haven't noticed, there's been a etherpad migration and domain change | 14:02 |
| rosmaita | #link http://lists.opendev.org/pipermail/service-announce/2020-April/000003.html | 14:03 |
| rosmaita | hopefully, you won't see anything, though monday the meeting agenda page was causing an internal server error | 14:03 |
| rosmaita | but that was fixed | 14:03 |
| *** ruffian_sheep36 is now known as ruffian_sheep | 14:03 | |
| rosmaita | #topic announcements - Victoria Virtual PTG | 14:03 |
| *** openstack changes topic to "announcements - Victoria Virtual PTG (Meeting topic: cinder)" | 14:03 | |
| rosmaita | ok, so the dates have been set | 14:04 |
| rosmaita | one week earlier than the physical event | 14:04 |
| rosmaita | not sure why | 14:04 |
| jungleboyj | Yay!?! | 14:04 |
| rosmaita | new dates: June 1 through June 5 | 14:04 |
| rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html | 14:04 |
| rosmaita | that email outlines the ground rules for the virtual PTG | 14:04 |
| rosmaita | key things impacting us are: | 14:05 |
| rosmaita | No team can sign up for more than 4 hours per UTC day | 14:05 |
| enriquetaso | o/ | 14:05 |
| rosmaita | No team can sign up for more than 16 hours across all time slots | 14:05 |
| jungleboyj | Which is good. | 14:05 |
| rosmaita | yeah, our 2-hour blocks have worked well for the midcycle sessions | 14:05 |
| rosmaita | anyway, here are the time slots: | 14:05 |
| rosmaita | #link https://ethercalc.openstack.org/126u8ek25noy | 14:06 |
| *** geguileo has joined #openstack-meeting-alt | 14:06 | |
| * lseki sneaks in | 14:06 | |
| rosmaita | and here is a meeting time planner for the first day, covering the TZs usually represented at our cinder meeting | 14:06 |
| *** xover-23 has joined #openstack-meeting-alt | 14:06 | |
| rosmaita | #link https://www.timeanddate.com/worldclock/meetingtime.html?month=6&day=1&year=2020&p1=159&p2=881&p3=141&p4=367&p5=176&p6=237&iv=0 | 14:06 |
| rosmaita | i don't want to spend a lot of time on this today | 14:06 |
| rosmaita | i guess the thing to do is, please put time suggetions on the etherpad | 14:07 |
| *** ttsiouts has quit IRC | 14:07 | |
| rosmaita | #link https://etherpad.opendev.org/p/cinder-victoria-ptg-planning | 14:07 |
| rosmaita | or something | 14:07 |
| rosmaita | i really don't know a good way to organize this | 14:07 |
| rosmaita | so feel free to suggest ideas | 14:07 |
| jungleboyj | :-) | 14:08 |
| rosmaita | but, do put time slot suggestions on the etherpad | 14:08 |
| rosmaita | or else i will schedule everytihing to be convenient for Roanoke time :) | 14:08 |
| xover-23 | hello world friends | 14:08 |
| jungleboyj | Looks like 7 am Monday is the most likely time where things start to work. | 14:08 |
| rosmaita | ok, moving on | 14:08 |
| e0ne | jungleboyj: :) | 14:09 |
| rosmaita | #topic announcements - FFEs | 14:09 |
| *** openstack changes topic to "announcements - FFEs (Meeting topic: cinder)" | 14:09 | |
| rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014035.html | 14:09 |
| *** ttsiouts has joined #openstack-meeting-alt | 14:09 | |
| rosmaita | that was the announcement to the ML | 14:09 |
| rosmaita | no other requests came in before yesterday's deadline, so that's all | 14:09 |
| rosmaita | i've been tracking progress here: | 14:10 |
| rosmaita | #link https://etherpad.opendev.org/p/cinder-ussuri-FFE-progress | 14:10 |
| rosmaita | looks like stuff is happening | 14:10 |
| *** andrebeltrami has joined #openstack-meeting-alt | 14:10 | |
| rosmaita | i am beginning to wonder whether the nfs-volume-encryption is going to have to wait until victoria | 14:10 |
| rosmaita | enriquetaso: eharney: opinions? | 14:10 |
| *** jcoufal has joined #openstack-meeting-alt | 14:10 | |
| eharney | i have also wondered the same | 14:11 |
| enriquetaso | yep, I think is going to victoria | 14:11 |
| jungleboyj | Something like that doesn't sound like something that we want to rush in place. | 14:11 |
| rosmaita | ok, i will re=target that bp | 14:11 |
| eharney | which is to say i wouldn't be upset about moving it out | 14:11 |
| rosmaita | and let's try to focus on it very early in victoria | 14:11 |
| rosmaita | ok, the other FFE is macrosan, but they are on the agenda for later | 14:12 |
| rosmaita | ok final item | 14:12 |
| rosmaita | #topic announcements - end-of-cycle driver stuff | 14:12 |
| *** openstack changes topic to "announcements - end-of-cycle driver stuff (Meeting topic: cinder)" | 14:12 | |
| rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014124.html | 14:12 |
| rosmaita | there are some outstanding items | 14:12 |
| rosmaita | the link above is something i sent to the ML and also forwarded directly to the driver maintainers of record | 14:13 |
| rosmaita | also, tracking that on this etherpad: | 14:13 |
| rosmaita | #topic https://etherpad.opendev.org/p/cinder-ussuri-driverstuff | 14:13 |
| *** openstack changes topic to "https://etherpad.opendev.org/p/cinder-ussuri-driverstuff (Meeting topic: cinder)" | 14:13 | |
| rosmaita | oops | 14:13 |
| enriquetaso | :P | 14:13 |
| rosmaita | #link https://etherpad.opendev.org/p/cinder-ussuri-driverstuff | 14:14 |
| rosmaita | anyway, mostly driver maintainers need to check that list | 14:14 |
| rosmaita | i'll raise the priority flag on reviews as they come in | 14:14 |
| rosmaita | also, I'm beginning the 3rd party compliance check | 14:14 |
| jungleboyj | ++ | 14:15 |
| rosmaita | but, like i said last week, driver maintainers can check proactively to make sure their CIs are functioning reliably | 14:15 |
| rosmaita | because RC-1 is next week, and that's the deadline for having everything working | 14:15 |
| rosmaita | though, it was brought to my attention that the covid-19 situation is keeping people out of datacenters | 14:16 |
| smcginnis | Also a reminder that it is good to point new driver submitters to https://docs.openstack.org/cinder/latest/contributor/new_driver_checklist.html to make sure they are covering everything that we should be checking. | 14:16 |
| rosmaita | and not everyone can do stuff remotely | 14:16 |
| rosmaita | smcginnis: ty, good reminder | 14:16 |
| rosmaita | ok, that's all for announcements | 14:16 |
| rosmaita | #topic MacronSAN driver discussion | 14:16 |
| *** openstack changes topic to "MacronSAN driver discussion (Meeting topic: cinder)" | 14:16 | |
| rosmaita | ruffian_sheep: that's you | 14:16 |
| ruffian_sheep | Regarding tempest.api.compute.admin.test_volume_swap.TestMultiAttachVolumeSwap.test_volume_swap_with_multiattach in the tempest test case, there is a problem that cannot be passed. | 14:17 |
| ruffian_sheep | Without any changes to the driver, I additionally create an instance and a volume, and perform the mount operation. This test case can pass. | 14:18 |
| rosmaita | you mean you can manually do what the test is doing, and you succeed? | 14:18 |
| ruffian_sheep | http://120.77.149.115/88/711388/6/check/cinder-isicsi-driver/848d283/tempest_log/tox.log | 14:19 |
| ruffian_sheep | http://120.77.149.115/88/711388/6/check/cinder-isicsi-driver/4a616b6/tempest_log/tox.log | 14:19 |
| whoami-rajat | ruffian_sheep, did you find any other error log except from the n-cpu one? | 14:19 |
| ruffian_sheep | This is the log result of two condition changes | 14:19 |
| ruffian_sheep | whoami-rajat | rosmaita: This test can be performed, but an error will occur when the resource is finally cleaned up. Moreover, in the logs of related test cases, only errors are found in the n-cpu. | 14:20 |
| ruffian_sheep | In fact, the same error report exists in n-cpu, but after changing the conditions, the use case can be executed without error. | 14:21 |
| rosmaita | when you say "changing the conditions", what do you mean exactly? | 14:22 |
| whoami-rajat | the driver seems to work correctly if the test passes in the local run | 14:22 |
| ruffian_sheep | Create a new instance and volume, and perform the attach_volume operation. | 14:22 |
| ruffian_sheep | I don't know what the specific reason is, but when I do this and then execute the tempest use case, it can be executed completely correctly. | 14:24 |
| smcginnis | ruffian_sheep: Unrelated, but just want to note that the tempest run output should really be in the root log file. So job-output.log would be where most would expect to go to find that. Don't want to divert this discussion, but just letting you know. | 14:24 |
| eharney | there are some strange cinder api errors associated with that test failure in screen-c-api.log | 14:24 |
| ruffian_sheep | smcginnis : get, i will change it | 14:25 |
| ruffian_sheep | eharney: I also saw it, but from the execution results, it seems to have no effect? And it is not directly related to the use case of multiattach? | 14:26 |
| eharney | c-vol shows a lock held for 51 seconds, maybe something is taking longer than tempest expects there | 14:26 |
| eharney | look at req-6f364876-aafd lines in c-api and c-vol logs... probably don't have time to debug it all here | 14:27 |
| *** jberg-dev has joined #openstack-meeting-alt | 14:28 | |
| rosmaita | ruffian_sheep: so, multiattach is a new feature you are adding | 14:28 |
| rosmaita | i wonder whether you should hold off on that until V | 14:28 |
| rosmaita | so you can get everything set to mark the driver 'supported' in U | 14:28 |
| ruffian_sheep | Yes, I wanted to add this feature to the ussuri version, but from the deadline, it is a bit unrealistic. | 14:29 |
| rosmaita | it looks like everything else is working though? | 14:29 |
| ruffian_sheep | Yes, and I initially passed the test case on the s version. | 14:30 |
| *** maaritamm has quit IRC | 14:30 | |
| *** ysandeep|away is now known as ysandeep | 14:31 | |
| ruffian_sheep | Because it was unclear at the beginning to execute the ci environment regularly. And use the latest openstack version. I carried out the tempest test on the s version. | 14:31 |
| rosmaita | i think the thing to do is revise your patch without multiattach and address the comments on the review | 14:31 |
| rosmaita | anything else? | 14:31 |
| whoami-rajat | rosmaita++ | 14:32 |
| smcginnis | rosmaita: ++ | 14:32 |
| ruffian_sheep | Yes, I confirmed this problem with whoami-rajat in the afternoon. For now, do not add related new features. | 14:32 |
| rosmaita | ok, thanks ... we will keep an eye on your patch | 14:32 |
| whoami-rajat | This way the CI could be marked supported and other features (apart from multiattach) could make it as well (probably) | 14:32 |
| whoami-rajat | into ussuri | 14:33 |
| rosmaita | #topic Continued discussion of: Cinder throws error creating incremental backup from parent in another project | 14:33 |
| *** openstack changes topic to "Continued discussion of: Cinder throws error creating incremental backup from parent in another project (Meeting topic: cinder)" | 14:33 | |
| rosmaita | ganso: that's you | 14:33 |
| rosmaita | we started this 2 weeks ago | 14:33 |
| *** xover-2385 has joined #openstack-meeting-alt | 14:33 | |
| rosmaita | link on the etherpad | 14:33 |
| rosmaita | i forget where we were on this, though | 14:34 |
| enriquetaso | #link https://bugs.launchpad.net/cinder/+bug/1869746 | 14:35 |
| openstack | Launchpad bug 1869746 in Cinder "Cinder throws error creating incremental backup from parent in another project" [Undecided,Confirmed] | 14:35 |
| *** xover-23 has quit IRC | 14:35 | |
| *** baiziyu-inspur has joined #openstack-meeting-alt | 14:35 | |
| rosmaita | ganso: comments? | 14:36 |
| ganso | oh sorry I missed the ping | 14:36 |
| rosmaita | ok | 14:36 |
| ganso | so, last time we discussed several different ways to tackle the problem | 14:36 |
| ganso | I summarized them in this etherpad | 14:37 |
| ganso | https://etherpad.opendev.org/p/cinder-backup-bug | 14:37 |
| ganso | basically I came up with 3 approaches from what we discussed, each with its pros and cons | 14:38 |
| rosmaita | ganso: how big a deal is this bug? | 14:38 |
| eharney | i'm getting server errors trying to load the etherpad | 14:38 |
| smcginnis | ganso: Having gone through all of those, is there one approach that makes the most sense to you? | 14:38 |
| smcginnis | eharney: Try a hard reload (ctrl+shift+r). | 14:38 |
| smcginnis | They upgraded etherpad, so it could be a bad cached js lib. | 14:39 |
| *** maaritamm has joined #openstack-meeting-alt | 14:39 | |
| ganso | rosmaita: it is workaroundable, and IMO it is the consequence of the customer doing it not in the most appropriate way, my main concern is actually fixing it to avoid anybody else from hitting it in the future. | 14:39 |
| rosmaita | ganso: excellent | 14:39 |
| rosmaita | i think we should fix it, just looks like it could wait for V? | 14:39 |
| ganso | smcginnis: I haven't gone through them at the implementation level, I didn't have many cycles, I was mostly gathering info to see if I could map all the concerns and spot a dealbreaker | 14:40 |
| ganso | rosmaita: I was actually expecting a backportable fix | 14:40 |
| smcginnis | ganso: I mean just conceptually, what would be the most expected behavior of the service? | 14:40 |
| ganso | rosmaita: however, as you can see in the etherpad, the fix that looks more semantically correct is (c), but that doesn't look like it can be backported | 14:41 |
| smcginnis | In other words, how _should_ cinder handle something like this. What is the most correct and expected behavior under this scenario. | 14:41 |
| rosmaita | ok, let's all take an item to look over the etherpad and return to this next week | 14:41 |
| rosmaita | and ganso maybe you can answer smcginnis's question on the etherpad | 14:41 |
| smcginnis | Based on the discussion of whether an admin should be able to backup a tenant's volumes, (c) did sound like the more correct path to me. | 14:41 |
| whoami-rajat | smcginnis, can't load the etherpad with ctrl+shift+r :/ | 14:42 |
| ganso | smcginnis: exactly, so the expected behavior, we tackled the situations where someone creates a backup on behalf of someone else, and accounts against that someone else's quota, this looks slightly unusual to me. What we see today makes sense semantically, but causes the bug, and it becomes a bit unusual because backup have parent relationships | 14:42 |
| rosmaita | more continued discussion: tosky are you around? | 14:42 |
| eharney | whoami-rajat: yeah, looks broken on the server side :/ | 14:42 |
| enriquetaso | In order to add more info: After debugging this a bit more and thanks to Rajat's investigation. There is a difference between the API using elevated (admin role) and manager using the user role. Looks like, there is not reason reason why we are using elevated context on the API code (checked into the DB) but removing the elevated may lead to some other broken functionality that worked previously (in general this could affect other | 14:42 |
| enriquetaso | cases). | 14:42 |
| tosky | rosmaita: yep | 14:42 |
| * tosky waits for green light | 14:42 | |
| rosmaita | #topic continuation of: cinder-tempest-plugin | 14:42 |
| *** openstack changes topic to "continuation of: cinder-tempest-plugin (Meeting topic: cinder)" | 14:42 | |
| tosky | apart from the reminder ("please go over the open cinder-tempest-plugin reviews"), I have a question about https://review.opendev.org/#/c/639205/ | 14:43 |
| tosky | as you can see it is an interesting experiment for a more complex scenario tests, which could deserve its own job | 14:44 |
| tosky | but it requires iSCSI multipath, and I'm not sure how to setup that on the gates | 14:44 |
| hemna_ | you would need the multipath daemon running | 14:45 |
| tosky | from some past discussions with some people, as I wrote in a comment on the review, I may have (incorrectly) got that it's possible to use LVM for that? | 14:45 |
| eharney | the theory (per geguileo) is that we could do this with the lvm driver by setting some additional options -- but not sure what all the steps are | 14:45 |
| geguileo | yeah, it's easy to do | 14:45 |
| eharney | i don't know if it requires configuring additional IPs or anything like that | 14:46 |
| tosky | yes! So the questions are if a) if you would like to have this complex realistic scenario in the gates and b) if someone could please provide the instructions or guidelines for that | 14:46 |
| tosky | that's it | 14:46 |
| *** ruffian_sheep has quit IRC | 14:46 | |
| enriquetaso | I think 639205 needs a rebase in order to run the new job "cinder-tempest-plugin-cbak-ceph" | 14:46 |
| rosmaita | it would definitely be cool to get this running | 14:46 |
| tosky | oh, sure, and also for the ddt thing | 14:46 |
| hemna_ | what are we testing here with that review? that multipath daemon can handle failover, or that cinder/os-brick can do a multipath attach? | 14:47 |
| rosmaita | next up: enriquetaso | 14:47 |
| geguileo | one needs to set iscsi_secondary_ip_addresses with other IP addresses | 14:47 |
| rosmaita | #topic continuation of: Allow removing NFS snapshots in error status is stuck | 14:47 |
| *** openstack changes topic to "continuation of: Allow removing NFS snapshots in error status is stuck (Meeting topic: cinder)" | 14:47 | |
| geguileo | if we are using a single node deployment, one can use 127.0.0.1 as the secondary IP | 14:47 |
| tosky | geguileo: please comment on the review :) | 14:47 |
| rosmaita | geguileo: doesn't have to be exact, if you can just point what to look for | 14:48 |
| enriquetaso | ok.. so after discussing with eharney, I guess the patch isn't so bad | 14:48 |
| *** Andreas681 has joined #openstack-meeting-alt | 14:48 | |
| rosmaita | #link https://review.opendev.org/#/c/679138/ | 14:48 |
| enriquetaso | About NFS snapshot in error... the model is always -- try to delete the snapshot on the backend, if it doesn't exist, then succeed, all drivers do that, this should just follow the same model | 14:48 |
| enriquetaso | so, I should update the patch with this comment and see what happens | 14:49 |
| rosmaita | that sounds sensible | 14:49 |
| smcginnis | ++ | 14:49 |
| rosmaita | that was quick, thank you enriquetaso | 14:49 |
| enriquetaso | \o/ | 14:49 |
| rosmaita | #topic Cinder master compatibility status with Ceph Nautilus and beyond | 14:50 |
| *** openstack changes topic to "Cinder master compatibility status with Ceph Nautilus and beyond (Meeting topic: cinder)" | 14:50 | |
| rosmaita | vkmc: that's you | 14:50 |
| vkmc | o/ | 14:50 |
| vkmc | hey folks | 14:50 |
| vkmc | I'm working on updating the devstack-ceph-plugin script | 14:50 |
| vkmc | something we use on the ci for manila, cinder, glance and nova | 14:50 |
| vkmc | right now we are testing the master branch for openstack with old versions of ceph | 14:51 |
| *** maaritamm has quit IRC | 14:51 | |
| vkmc | luminous is the latest version we have in there | 14:51 |
| hemna_ | I had looked at rewriting the plugin using ceph-ansible since it seems to handle scenarios and versioning better than the old plugin code | 14:51 |
| vkmc | so... I don't want to break your ci, and therefore I wanted to ask before moving forward | 14:52 |
| hemna_ | ceph-ansible can also handle ceph iscsi too | 14:52 |
| vkmc | have you been testing cinder with nautilus? | 14:52 |
| eharney | so if we change the default release of ceph in there, it will change it for our jobs on stable branches too, right? | 14:52 |
| tosky | it depends on how it is set on that job, I guess | 14:53 |
| vkmc | my idea was to submit an experimental job first | 14:53 |
| vkmc | keep what we have now, continue testing with luminous | 14:53 |
| tosky | only the master (and maybe ussuri) variant of the job could be changed to use nautilus | 14:53 |
| vkmc | and then, with time, drop the experimental job and promote it | 14:53 |
| eharney | i don't recall that we specify versions in our jobs... probably need to decide what the correct ceph version is to use for older stable branches, and if it matters | 14:53 |
| *** maaritamm has joined #openstack-meeting-alt | 14:54 | |
| vkmc | btw, this is the patch for this update I'm talking about, if you want to take a look https://review.opendev.org/#/c/676722/ | 14:54 |
| vkmc | eharney, we don't have that option on the plugin yet, we just pull whatever version is hardcoded there | 14:54 |
| vkmc | and that's what I want to implement :) | 14:54 |
| vkmc | I see you have two gates in cinder (the ones I could see)... one in the check pipeline and one for third party IBM, not sure if you have another one using the plugin | 14:55 |
| eharney | oh... that CEPH_RELEASE var is misleading currently | 14:55 |
| tosky | vkmc: you would need to set CEPH_RELEASE in the vars section of the branch-specific variant of the job | 14:55 |
| vkmc | tosky, yes | 14:55 |
| tosky | uh | 14:55 |
| vkmc | <eharney> so if we change the default release of ceph in there, it will change it for our jobs on stable branches too, right? <- yes | 14:56 |
| vkmc | so, experimental gate for master, continue using whatever version we were using for stable branches | 14:57 |
| eharney | we just need to pick what version(s) we want to run for stable | 14:58 |
| vkmc | we have 2 more minutes, so we can continue the discussion on the cinder channel if that sounds good for you | 14:58 |
| rosmaita | ok, experimental sounds good, won't break anything | 14:58 |
| rosmaita | we can figure out the details on reviews | 14:58 |
| rosmaita | ok, 1 minute | 14:59 |
| rosmaita | thanks, vkmc | 14:59 |
| vkmc | thanks folks | 14:59 |
| rosmaita | #topic open discussion | 14:59 |
| *** openstack changes topic to "open discussion (Meeting topic: cinder)" | 14:59 | |
| rosmaita | 30 seconds | 14:59 |
| enriquetaso | thanks | 14:59 |
| whoami-rajat | Thanks! | 14:59 |
| rosmaita | anything? | 14:59 |
| eharney | cinder is awesome | 14:59 |
| rosmaita | ok, can't top that | 14:59 |
| e0ne | :) | 14:59 |
| smcginnis | Just wanted to point out that we will need this before victoria when py38 becomes voting: https://review.opendev.org/#/c/720008/ | 14:59 |
| whoami-rajat | :D | 14:59 |
| rosmaita | #endmeeting | 14:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 14:59 | |
| openstack | Meeting ended Wed Apr 15 14:59:45 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-15-14.00.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-15-14.00.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-15-14.00.log.html | 14:59 |
| rosmaita | smcginnis: sorry about that | 15:00 |
| *** tosky has left #openstack-meeting-alt | 15:00 | |
| *** priteau has joined #openstack-meeting-alt | 15:00 | |
| amotoki | #startmeeting horizon | 15:01 |
| openstack | Meeting started Wed Apr 15 15:01:28 2020 UTC and is due to finish in 60 minutes. The chair is amotoki. 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: horizon)" | 15:01 | |
| openstack | The meeting name has been set to 'horizon' | 15:01 |
| Nizars | Hi! | 15:01 |
| amotoki | hi | 15:01 |
| vishalmanchanda | hi | 15:01 |
| Andreas681 | Hello | 15:01 |
| e0ne | hi | 15:01 |
| jberg-dev | greetings! | 15:01 |
| rdopiera | aloha | 15:02 |
| amotoki | we have enough folks here :) | 15:02 |
| amotoki | let's start | 15:02 |
| amotoki | #topic annoucements/notices | 15:03 |
| *** openstack changes topic to "annoucements/notices (Meeting topic: horizon)" | 15:03 | |
| amotoki | the last week was the week of feature freeze for cycle-with-rc projects | 15:03 |
| Nizars | I would like to discuss a Horizon plugin project that me and Andreas682, jberg-dev, and two other people are working on when the floor is open. :) | 15:03 |
| amotoki | we switched cycle-with-intermediary in this cycle, so I am planning to cut a release this week and considering it as the feature freeze | 15:03 |
| *** rosmaita has left #openstack-meeting-alt | 15:03 | |
| *** gyee has joined #openstack-meeting-alt | 15:04 | |
| amotoki | let's discuss potential reviews in the upcoming topic just after this. | 15:04 |
| amotoki | Nizars: can we discuss your topic in "On-demand agenda" section later in this meeting? | 15:05 |
| *** lpetrut has quit IRC | 15:05 | |
| Nizars | absolutely, we are new to the format here so we will just follow your lead. | 15:05 |
| e0ne | amotoki: does it mean the master will be open fro V release next week? | 15:06 |
| e0ne | s/fro/sor | 15:06 |
| e0ne | *for | 15:06 |
| amotoki | e0ne: next week or later this week. I will let you (all cores) once I cut a release. | 15:07 |
| e0ne | amotoki: thanks | 15:07 |
| amotoki | Nizars: FYI the meeting format is found at https://wiki.openstack.org/wiki/Meetings/Horizon which redirects you to https://etherpad.opendev.org/p/horizon-release-priorities | 15:07 |
| Nizars | Thank you! | 15:08 |
| amotoki | another announcement I would like to share is we releases several xstatic modules https://review.opendev.org/#/c/718593/ | 15:08 |
| amotoki | I will send a governance follow-up patch to drop 'deprecation' mark in projects.yaml. | 15:08 |
| amotoki | e0ne: any notices around the virtual PTG for Victoria? | 15:09 |
| e0ne | amotoki: not yet. we need to start planing but I didn't do anything related yet | 15:10 |
| amotoki | e0ne: np | 15:10 |
| amotoki | FYI: there is an official announment of the virtual PTG http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html | 15:10 |
| amotoki | several teams have started to coordinate meeting slots or some. | 15:10 |
| amotoki | this email is worth checking. | 15:10 |
| amotoki | anything other to share? | 15:11 |
| amotoki | moving on | 15:12 |
| amotoki | #topic reviews for Ussuri | 15:12 |
| *** openstack changes topic to "reviews for Ussuri (Meeting topic: horizon)" | 15:12 | |
| amotoki | I would like to discuss pending review candidates for Ussuri here | 15:12 |
| *** ianychoi has quit IRC | 15:13 | |
| amotoki | https://review.opendev.org/719777 a workaorund with pyscss 1.3.5 or later has landed. thanks e0ne | 15:13 |
| amotoki | next one is https://review.opendev.org/709025 | 15:13 |
| e0ne | amotoki: thanks for the tests! | 15:14 |
| amotoki | we can release without regression :) | 15:14 |
| *** maaritamm has quit IRC | 15:14 | |
| amotoki | 709025 is "Add support for multiple swift storage policies" | 15:14 |
| *** maaritamm has joined #openstack-meeting-alt | 15:14 | |
| amotoki | the code itself is generally good, but I have two questions | 15:15 |
| amotoki | the one is display_name. per reply from the author, it looks like not swift limiration but a topic specific to some deployment/public clouds | 15:15 |
| amotoki | I am okay with this proposal but I would like to clarify the background for future maintenance. | 15:16 |
| amotoki | the other is an immediate value in SCSS https://review.opendev.org/#/c/709025/9/openstack_dashboard/dashboards/project/static/dashboard/project/containers/_containers.scss@116 | 15:16 |
| amotoki | I would like to avoid this kind of magic number. | 15:17 |
| e0ne | amotoki: I missed it:( +1 for your comment for scss | 15:17 |
| amotoki | your opinions and feedbacks would be appreciated. | 15:17 |
| amotoki | next one is https://review.opendev.org/#/c/708069/ | 15:18 |
| amotoki | "Refactor error messages" from vishalmanchanda | 15:19 |
| amotoki | I tested the proposed code and it looks not ready for ussuri | 15:19 |
| vishalmanchanda | yeah:(. | 15:19 |
| amotoki | as of now, it does not support 'redirect' in exceptions.handle, so my vote is to defer it to the next cycle | 15:19 |
| *** xover-2385 has quit IRC | 15:20 | |
| amotoki | these are possible feature reviews in my mind. | 15:21 |
| *** ttsiouts has quit IRC | 15:22 | |
| amotoki | If the first one lands soon, I will include it in the upcoming release. If it takes time, we can skip it. | 15:22 |
| amotoki | any other reviews for Ussuri? | 15:23 |
| e0ne | nothing from me | 15:23 |
| amotoki | note: fixes and test code refactoring changes can land any time | 15:24 |
| amotoki | #topic general priorities | 15:25 |
| *** openstack changes topic to "general priorities (Meeting topic: horizon)" | 15:25 | |
| amotoki | I think we can skip this topic and community goals this week. | 15:25 |
| e0ne | + | 15:26 |
| amotoki | moving on | 15:26 |
| amotoki | #topic on-demand agenda | 15:26 |
| *** openstack changes topic to "on-demand agenda (Meeting topic: horizon)" | 15:26 | |
| amotoki | we have a topic here this week | 15:26 |
| amotoki | Nizars: go ahead | 15:26 |
| Nizars | Thank you | 15:26 |
| Nizars | We are working on a Horizon plugin for role based access management through keystone and oslo.policy | 15:27 |
| Nizars | The blueprint for the project can be found here | 15:28 |
| Nizars | https://blueprints.launchpad.net/horizon/+spec/policies-plugin | 15:28 |
| Nizars | The code currently resides on github. | 15:28 |
| Nizars | https://github.com/nizos/horizon-policies-plugin | 15:28 |
| Nizars | The wiki for the project can also be found here | 15:28 |
| Nizars | https://wiki.nordix.org/display/RE/OpenStack+Policies | 15:29 |
| *** ttsiouts has joined #openstack-meeting-alt | 15:29 | |
| Nizars | To my question. How can we get the project approved and how do we move the code to gerrit and start working on it from there? | 15:29 |
| amotoki | there are several options to get the feature upstreamed. | 15:31 |
| amotoki | the one is to include it in the horizon repo if it fits | 15:31 |
| amotoki | another way is to have a separate repository for the feature | 15:32 |
| rdopiera | I thought we were moving away from in-repo plugins in the long term? | 15:32 |
| amotoki | in case of using a separate repository, there are two choices: an official openstack repo or third-party repo | 15:32 |
| Nizars | We would like to move it to an official openstack repo | 15:33 |
| Nizars | But it is not a requirement | 15:33 |
| amotoki | my question is how policies are maintained. | 15:34 |
| amotoki | as of now, keystone does not provide an API to expose policies. | 15:34 |
| Nizars | Can you elaborate | 15:34 |
| Nizars | That is true | 15:34 |
| Nizars | We are planning of creating the backend functionalities ourselves. | 15:34 |
| Nizars | We are currently retrieving them through oslo.policy | 15:35 |
| amotoki | Nizars: how are they retrieved via oslo.policy? | 15:35 |
| Nizars | 1 sec | 15:35 |
| amotoki | the default polices are defined in code of individual projects, so doesn't it mean you need to import all projects? | 15:37 |
| Nizars | `generator._generate_policy("keystone", self.FILE_PATH)` | 15:37 |
| Nizars | we import it as such: `from oslo_policy import generator` | 15:37 |
| Nizars | the file path is where it outputs the effective policies | 15:38 |
| amotoki | what about default policies? | 15:38 |
| Nizars | They are retrieved through the same function | 15:38 |
| amotoki | for example, if you would like to load policies from keystone, keystone needs to be installed. | 15:39 |
| amotoki | right? | 15:39 |
| Nizars | It gets the defaults, then checks the policy files, from there it merges them after that | 15:39 |
| *** maaritamm has quit IRC | 15:39 | |
| Nizars | https://github.com/nizos/horizon-policies-plugin/blob/c9a157254fb4efe62ce2179c12f43e2cab4b005c/policies-plugin/policies_plugin/api/rest/policy_client.py | 15:39 |
| Nizars | This is how the output looks like: | 15:40 |
| Nizars | https://github.com/nizos/horizon-policies-plugin/blob/c9a157254fb4efe62ce2179c12f43e2cab4b005c/policies-plugin/policies_plugin/api/rest/policy_output.txt | 15:40 |
| Nizars | The first line is a policy provided from the policy.json file. | 15:40 |
| Nizars | `"identity:get_consumer": "role:admin and system_scope:all"` | 15:40 |
| Nizars | In any case. This process is too heavy. There is a lot that is lacking. | 15:41 |
| bnemec | That would be one concern. You could only use this tool if the service is installed on the same system as Horizon. | 15:41 |
| Nizars | Can you elaborate on that? | 15:41 |
| bnemec | It also needs to not be running in a container that doesn't have access to the other service policy files. | 15:41 |
| amotoki | bnemec: yeah, my concern is exactly same | 15:41 |
| bnemec | Nizars: If keystone is installed standalone (or just not on the same box as horizon), you won't be able to read its policy files. | 15:42 |
| Nizars | Help us understand the problem a little better so we can look into it and see if some modifications can be made. | 15:42 |
| Nizars | ok | 15:42 |
| Nizars | That's a good point. | 15:42 |
| *** LiangFang has quit IRC | 15:43 | |
| amotoki | the original question is how to move the proposal forward. | 15:43 |
| Nizars | Can this be dealt with using some config files? Can you think of a way to go about using the plugin in such a use case? | 15:44 |
| amotoki | from what I understand so far here, the backend would require to have various service project installed in a same system. | 15:44 |
| amotoki | the frontend can consume the backend API. | 15:44 |
| amotoki | the backend requirements would be totally different from horizon | 15:44 |
| amotoki | so a separate repository would be fine | 15:45 |
| Nizars | I see | 15:45 |
| amotoki | agree? | 15:45 |
| Nizars | Yeah | 15:45 |
| amotoki | the second question is what project team is appropriate to cover this project. | 15:45 |
| Nizars | I would like to hear your thoughts on what implementation possibilities are there to use the plugin when the services are run in different systems if possible. | 15:46 |
| amotoki | I am not sure which project fits this.... | 15:46 |
| Nizars | installed* | 15:46 |
| amotoki | Nizars: is "the plugin" you mention a horizon plugin? | 15:47 |
| Nizars | yes | 15:47 |
| *** baiziyu-inspur has quit IRC | 15:47 | |
| *** ianychoi has joined #openstack-meeting-alt | 15:47 | |
| *** jcoufal has quit IRC | 15:48 | |
| Nizars | This is how it looks right now when installed in Horizon: | 15:48 |
| Nizars | https://imgur.com/TMxrv9d | 15:48 |
| amotoki | for the frondend, it can be a horizon plugin | 15:48 |
| amotoki | but I am not sure the backend should be run as part of horizon server side. | 15:48 |
| Nizars | I see. | 15:48 |
| amotoki | it requires too much dependencies | 15:48 |
| Nizars | Can you elaborate on that point a little bit more if possible? | 15:49 |
| amotoki | okay | 15:49 |
| amotoki | we usually use separate repositories for service, client lib and frontend. | 15:49 |
| Nizars | Thank you | 15:49 |
| amotoki | for example, nova, novaclient and UI (horizon) | 15:49 |
| amotoki | this is because they have different dependencies. | 15:50 |
| amotoki | this is a discussion on the strategy for repositories (i.e. deliveables), | 15:50 |
| amotoki | s/,/./ | 15:51 |
| amotoki | we also need to consider which project team can host it. | 15:51 |
| Nizars | I see | 15:51 |
| amotoki | consider its GUI perspective, horizon might be good, but it has other aspects (like a tool to consume/handle policies) | 15:52 |
| *** jcoufal has joined #openstack-meeting-alt | 15:52 | |
| amotoki | it looks good to discuss it more broadly including TC | 15:53 |
| amotoki | Nizars: one more question. Does your team plan to maintain it even after it is upstreaded (i.e. part of OpenStack governance)? | 15:53 |
| Nizars | I assume keystone can access policy files of projects installed in different file systems. Is this correct? Is it possible for us to implement something similar to access those files as well? How practical would that be to implement and would it cause any redundancy considering the currently exiting solutions? | 15:53 |
| Nizars | I plan on staying active on it. | 15:54 |
| Nizars | What does TC stand for? | 15:54 |
| amotoki | TC = technical committee | 15:54 |
| Nizars | I see, thank you. | 15:54 |
| amotoki | regarding the question on keystone above, the answer is no. | 15:54 |
| amotoki | keystone only take cares of keystone policies. | 15:55 |
| Nizars | I see. | 15:55 |
| amotoki | nova take care of nova polices. | 15:55 |
| amotoki | oslo.policy provides a common layer to handle policies. | 15:55 |
| Nizars | So oslo.policy is able to access the policy files in installations on different systems? | 15:56 |
| amotoki | Nizars: no. it can access policies installed locally | 15:56 |
| Nizars | I see. | 15:56 |
| Nizars | Interesting. | 15:56 |
| amotoki | it looks like a discussion on policy loading on the python side. not about GUI. | 15:57 |
| Nizars | Yeah | 15:57 |
| amotoki | I am afraid it is now not the right place to discuss...... | 15:57 |
| Nizars | I understand | 15:57 |
| *** maaritamm has joined #openstack-meeting-alt | 15:57 | |
| Nizars | Thank you for your time and feedback. | 15:57 |
| amotoki | I can discuss it as neutron core and a person familiar with oslo.policy. it is not from horizon perspective..... | 15:57 |
| amotoki | anyway, my suggestion in this meeting is to raise it to openstack-dsicuss ML (with [tc] tag (technical committees can be aware of it) | 15:58 |
| amotoki | in the mail you can explain the concept and purpose of the proposal | 15:59 |
| amotoki | (it is better not to discuss it based on the current implementation level) | 15:59 |
| amotoki | does it work for you? | 15:59 |
| amotoki | we are out of time | 16:00 |
| amotoki | thanks for joining all | 16:00 |
| Nizars | A simple solution would be to just allow the user to upload the policy files they want to work on themselves and after making the changes they want they can download them and export them themselves but that makes the plugin quite restricted in terms of usefulness. The benefit of the plugin here would have to be editing features and policy checks. | 16:00 |
| amotoki | #endmeeting | 16:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:00 | |
| openstack | Meeting ended Wed Apr 15 16:00:40 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-15-15.01.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-15-15.01.txt | 16:00 |
| Nizars | Thank you | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-15-15.01.log.html | 16:00 |
| amotoki | Nizars: if you need to dsicuss, visit #openstack-horizon | 16:01 |
| *** maaritamm has quit IRC | 16:01 | |
| *** priteau has quit IRC | 16:12 | |
| *** jcoufal has quit IRC | 16:12 | |
| *** Andreas681 has quit IRC | 16:13 | |
| *** maaritamm has joined #openstack-meeting-alt | 16:13 | |
| *** jcoufal has joined #openstack-meeting-alt | 16:21 | |
| *** yaawang has joined #openstack-meeting-alt | 16:31 | |
| *** yaawang_ has quit IRC | 16:34 | |
| *** maaritamm has quit IRC | 16:35 | |
| *** jcoufal has quit IRC | 16:45 | |
| *** jcoufal has joined #openstack-meeting-alt | 16:58 | |
| *** ttsiouts has quit IRC | 17:00 | |
| *** ttsiouts has joined #openstack-meeting-alt | 17:01 | |
| *** priteau has joined #openstack-meeting-alt | 17:05 | |
| *** ricolin has quit IRC | 17:10 | |
| *** ttsiouts has quit IRC | 17:17 | |
| *** derekh has quit IRC | 17:17 | |
| *** priteau has quit IRC | 17:26 | |
| *** ttsiouts has joined #openstack-meeting-alt | 17:34 | |
| *** links has quit IRC | 18:01 | |
| *** ttsiouts has quit IRC | 18:09 | |
| *** maaritamm has joined #openstack-meeting-alt | 18:26 | |
| *** e0ne has quit IRC | 18:31 | |
| *** ttsiouts has joined #openstack-meeting-alt | 18:42 | |
| *** ttsiouts has quit IRC | 18:48 | |
| *** jcoufal has quit IRC | 18:49 | |
| *** hongbin has joined #openstack-meeting-alt | 19:01 | |
| *** ttsiouts has joined #openstack-meeting-alt | 19:23 | |
| *** ttsiouts has quit IRC | 19:34 | |
| *** ttsiouts has joined #openstack-meeting-alt | 19:34 | |
| *** gshippey has quit IRC | 19:42 | |
| *** enriquetaso has quit IRC | 19:48 | |
| *** ttsiouts has quit IRC | 19:49 | |
| *** vishalmanchanda has quit IRC | 19:54 | |
| *** enriquetaso has joined #openstack-meeting-alt | 19:57 | |
| *** slaweq has quit IRC | 20:08 | |
| *** slaweq has joined #openstack-meeting-alt | 20:08 | |
| *** maaritamm has quit IRC | 20:13 | |
| *** ttsiouts has joined #openstack-meeting-alt | 20:23 | |
| *** e0ne has joined #openstack-meeting-alt | 20:24 | |
| *** ttsiouts has quit IRC | 20:28 | |
| *** slaweq has quit IRC | 20:28 | |
| *** ttsiouts has joined #openstack-meeting-alt | 20:58 | |
| *** e0ne has quit IRC | 21:02 | |
| *** e0ne has joined #openstack-meeting-alt | 21:03 | |
| *** ttsiouts has quit IRC | 21:32 | |
| *** e0ne has quit IRC | 21:42 | |
| *** jtomasek has quit IRC | 21:42 | |
| *** raildo has quit IRC | 21:53 | |
| *** ccamacho has quit IRC | 22:11 | |
| *** eharney has quit IRC | 22:11 | |
| *** rfolco has quit IRC | 22:24 | |
| *** ttsiouts has joined #openstack-meeting-alt | 22:38 | |
| *** rcernin has joined #openstack-meeting-alt | 22:45 | |
| *** hongbin has quit IRC | 22:53 | |
| *** hongbin has joined #openstack-meeting-alt | 23:01 | |
| *** ttsiouts has quit IRC | 23:12 | |
| *** ttsiouts has joined #openstack-meeting-alt | 23:40 | |
| *** ttsiouts has quit IRC | 23:45 | |
| *** ttsiouts has joined #openstack-meeting-alt | 23:54 | |
| *** ttsiouts has quit IRC | 23:58 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!