| *** tetsuro has joined #openstack-meeting-alt | 00:05 | |
| *** Liang__ has joined #openstack-meeting-alt | 01:01 | |
| *** gyee has quit IRC | 01:04 | |
| *** masahito has joined #openstack-meeting-alt | 01:42 | |
| *** masahito has quit IRC | 01:47 | |
| *** sfernand has quit IRC | 01:48 | |
| *** masahito has joined #openstack-meeting-alt | 02:01 | |
| *** apetrich has quit IRC | 02:09 | |
| *** ricolin has joined #openstack-meeting-alt | 02:33 | |
| *** tetsuro has quit IRC | 03:02 | |
| *** enriquetaso has quit IRC | 03:13 | |
| *** masahito has quit IRC | 03:15 | |
| *** tetsuro has joined #openstack-meeting-alt | 03:18 | |
| *** tetsuro has quit IRC | 03:19 | |
| *** jtomasek has quit IRC | 03:33 | |
| *** jtomasek has joined #openstack-meeting-alt | 03:36 | |
| *** tetsuro has joined #openstack-meeting-alt | 03:57 | |
| *** masahito has joined #openstack-meeting-alt | 04:01 | |
| *** yamamoto has quit IRC | 04:18 | |
| *** yamamoto has joined #openstack-meeting-alt | 04:37 | |
| *** maaritamm has joined #openstack-meeting-alt | 04:43 | |
| *** maaritamm has quit IRC | 05:02 | |
| *** maaritamm has joined #openstack-meeting-alt | 05:03 | |
| *** rfolco has quit IRC | 05:09 | |
| *** bnemec has quit IRC | 05:22 | |
| *** rcernin has quit IRC | 05:24 | |
| *** ysandeep|away is now known as ysandeep | 05:34 | |
| *** masahito has quit IRC | 05:43 | |
| *** ricolin has quit IRC | 05:51 | |
| *** ricolin has joined #openstack-meeting-alt | 05:53 | |
| *** ttsiouts has joined #openstack-meeting-alt | 05:56 | |
| *** rcernin has joined #openstack-meeting-alt | 06:09 | |
| *** rcernin has quit IRC | 06:10 | |
| *** belmoreira has joined #openstack-meeting-alt | 06:10 | |
| *** rcernin has joined #openstack-meeting-alt | 06:11 | |
| *** belmoreira has quit IRC | 06:12 | |
| *** tetsuro has quit IRC | 06:21 | |
| *** belmoreira has joined #openstack-meeting-alt | 06:23 | |
| *** licanwei has joined #openstack-meeting-alt | 06:23 | |
| *** rcernin has quit IRC | 06:25 | |
| *** rcernin has joined #openstack-meeting-alt | 06:26 | |
| *** tetsuro has joined #openstack-meeting-alt | 06:37 | |
| *** maaritamm has quit IRC | 06:37 | |
| *** Dantalion has joined #openstack-meeting-alt | 06:53 | |
| *** slaweq has joined #openstack-meeting-alt | 06:58 | |
| *** slaweq has quit IRC | 07:02 | |
| *** tetsuro has quit IRC | 07:03 | |
| *** apetrich has joined #openstack-meeting-alt | 07:04 | |
| *** slaweq has joined #openstack-meeting-alt | 07:05 | |
| *** ricolin has quit IRC | 07:06 | |
| *** tetsuro has joined #openstack-meeting-alt | 07:11 | |
| *** tetsuro has quit IRC | 07:11 | |
| *** rcernin has quit IRC | 07:13 | |
| *** ricolin has joined #openstack-meeting-alt | 07:13 | |
| *** tetsuro has joined #openstack-meeting-alt | 07:20 | |
| *** maaritamm has joined #openstack-meeting-alt | 07:38 | |
| *** vishalmanchanda has joined #openstack-meeting-alt | 07:54 | |
| *** ccamacho has joined #openstack-meeting-alt | 07:57 | |
| *** chenke has joined #openstack-meeting-alt | 07:59 | |
| chenke | hello | 07:59 |
|---|---|---|
| chenke | I am here. | 07:59 |
| Dantalion | hello | 08:00 |
| licanwei | #startmeeting Watcher | 08:00 |
| openstack | Meeting started Wed Apr 22 08:00:40 2020 UTC and is due to finish in 60 minutes. The chair is licanwei. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| *** openstack changes topic to " (Meeting topic: Watcher)" | 08:00 | |
| openstack | The meeting name has been set to 'watcher' | 08:00 |
| licanwei | hi~ | 08:00 |
| *** links has joined #openstack-meeting-alt | 08:01 | |
| licanwei | #topic Review | 08:03 |
| *** openstack changes topic to "Review (Meeting topic: Watcher)" | 08:03 | |
| licanwei | most for Use unittest.mock instead of third party mock | 08:03 |
| licanwei | https://review.opendev.org/#/c/721028/ | 08:04 |
| licanwei | https://review.opendev.org/#/c/718125 | 08:04 |
| licanwei | https://review.opendev.org/#/c/718122 | 08:04 |
| licanwei | https://review.opendev.org/#/c/721007 | 08:04 |
| Dantalion | 721028 we just need to update, seems one line was missed which trigger pep8 | 08:05 |
| chenke | Agree we consider therse patch | 08:05 |
| chenke | Ye. | 08:05 |
| Dantalion | 718125, needs rebase as most changes are also in https://review.opendev.org/#/c/719340/ which has merged | 08:06 |
| licanwei | Watcher release for Ussuri https://review.opendev.org/#/c/721472/ | 08:07 |
| Dantalion | 718122 & 721007 are both for watcherclient but one has more line changes so should check what is the difference | 08:07 |
| *** tetsuro_ has joined #openstack-meeting-alt | 08:08 | |
| Dantalion | Watcher release file looks good to me | 08:08 |
| chenke | I had submit remove six patch | 08:09 |
| chenke | Do you all think we merged it before release ? | 08:09 |
| licanwei | chenke: your https://review.opendev.org/#/c/721612/ ? | 08:10 |
| chenke | ye | 08:10 |
| *** tetsuro has quit IRC | 08:11 | |
| chenke | and this:https://review.opendev.org/#/c/721786/1 | 08:11 |
| licanwei | I don't think these are important for release | 08:13 |
| chenke | in my env. the py3 and pep8 passed. | 08:14 |
| chenke | ok. If you all think so. We can merged it in the next V. | 08:14 |
| Dantalion | I think for now this is okaj but for next release everything for python 2 needs to be removed | 08:14 |
| licanwei | https://review.opendev.org/#/c/720140/ Initial watcher helm chart needs review | 08:15 |
| chenke | ok. | 08:15 |
| Dantalion | Unfortunately, you can not test this chart in k8s yet unless you build Watcher images and change image location in values.yaml | 08:16 |
| Dantalion | https://review.opendev.org/#/c/696677/ this needs to merge for images to be pushed to repository | 08:17 |
| licanwei | Dantalion: ok | 08:19 |
| licanwei | Dantalion: do you test in k8s env? | 08:20 |
| Dantalion | Once a few releases ago | 08:21 |
| Dantalion | I want to redo the test when the images are ready and there is time CERN can provide cluster for testing | 08:21 |
| licanwei | Dantalion: great | 08:22 |
| chenke | cool | 08:23 |
| licanwei | Dantalion: and I'll try to test in my env. | 08:24 |
| Dantalion | Cool thanks | 08:25 |
| licanwei | last week jatinder Singh(Orange Labs & Networks) sent a mail to me | 08:26 |
| *** tetsuro_ has quit IRC | 08:27 | |
| licanwei | I have tested watcher service on openstack USSURI version with existing strategies yesterday. I have few queries regarding watcher service. Please help to advise on below point. | 08:27 |
| licanwei | 08:27 | |
| licanwei | 1. is there vm scheduling optimize use-case tested with watcher ? | 08:27 |
| licanwei | 2. is it feasible to develop a common strategy for Watcher with AI to achieve optimization at pre scheduling VM and post scheduling or any discussion on this ? | 08:27 |
| licanwei | 3. could we optimize VNFs that installed on NOVA with cpu-pinning environment ? | 08:28 |
| licanwei | could you please share invite of next watcher meeting. | 08:28 |
| Dantalion | 2. I think is feasible we speculated about it at CERN and envisioned it as an external service that integrated with Wathcer | 08:28 |
| Dantalion | He is welcome during watcher meeting for me anytime :) | 08:29 |
| licanwei | I reply to him the meeting time , | 08:29 |
| licanwei | but i don't know if he is online? | 08:29 |
| Dantalion | 2. could integrate with the scoring module to evaluate the effectiveness of strategies as part of machine learning | 08:29 |
| Dantalion | I think it is best to discuss the questions when he can join a meeting | 08:30 |
| licanwei | Dantalion: you can send mail to him:) | 08:30 |
| Dantalion | Do you have email? | 08:30 |
| licanwei | jatinder1.singh@orange.com | 08:31 |
| Dantalion | I will email him, I also have a contact at CERN who is interested in machine learning for Watcher | 08:31 |
| Dantalion | maybe the can collaborate :) | 08:31 |
| licanwei | Dantalion: great~ | 08:32 |
| licanwei | These is my reply: | 08:34 |
| licanwei | q1:About use cases, ZTE had tests at China Telecom in 2018. and CERN also tested Watcher last year. In addition, as far as I know, there are companies in Russia and Greece that have tested Watcher, but I don???t know the details. | 08:36 |
| licanwei | q2:There is not much discussion about AI strategies. Watcher has a related BP: | 08:36 |
| licanwei | https://specs.openstack.org/openstack/watcher-specs/specs/newton/implemented/scoring-module.html | 08:36 |
| licanwei | q3:This depends on NOVA. For example, VM migration, Watcher's action is implemented by calling novaclient. | 08:36 |
| licanwei | We will have IRC meeting at 8:00 UTC on April 22 on channel #openstack-meeting-alt, welcome to join us! | 08:36 |
| licanwei | Community will have Virtual PTG on June | 08:36 |
| licanwei | http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html | 08:36 |
| licanwei | Do we need a time slot? | 08:37 |
| chenke | I think no. | 08:39 |
| Dantalion | I think it will be the same as regular meeting | 08:39 |
| Dantalion | We always manage to discuss all necessities within time so no additional time is needed | 08:39 |
| licanwei | ok | 08:40 |
| chenke | ok | 08:40 |
| licanwei | that's all for today~ | 08:40 |
| *** masahito has joined #openstack-meeting-alt | 08:41 | |
| licanwei | if no other questions, i'll end the meeting | 08:41 |
| chenke | ok | 08:41 |
| chenke | bye~ | 08:41 |
| Dantalion | okaj see you next time | 08:41 |
| licanwei | see you all~ | 08:42 |
| licanwei | #endmeeting | 08:42 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 08:42 | |
| openstack | Meeting ended Wed Apr 22 08:42:18 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:42 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/watcher/2020/watcher.2020-04-22-08.00.html | 08:42 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/watcher/2020/watcher.2020-04-22-08.00.txt | 08:42 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/watcher/2020/watcher.2020-04-22-08.00.log.html | 08:42 |
| *** ysandeep is now known as ysandeep|lunch | 08:46 | |
| *** e0ne has joined #openstack-meeting-alt | 08:56 | |
| *** ysandeep|lunch is now known as ysandeep | 09:06 | |
| *** chenke has quit IRC | 09:10 | |
| *** ricolin has quit IRC | 09:22 | |
| *** ricolin has joined #openstack-meeting-alt | 09:23 | |
| *** ricolin has quit IRC | 09:24 | |
| *** ricolin has joined #openstack-meeting-alt | 09:25 | |
| *** ricolin has quit IRC | 09:25 | |
| *** ricolin_ has joined #openstack-meeting-alt | 09:25 | |
| *** e0ne has quit IRC | 09:34 | |
| *** e0ne has joined #openstack-meeting-alt | 09:35 | |
| *** ricolin_ is now known as ricolin | 09:36 | |
| *** yamamoto has quit IRC | 09:57 | |
| *** maaritamm has quit IRC | 10:14 | |
| *** hemna has quit IRC | 10:18 | |
| *** hemna has joined #openstack-meeting-alt | 10:19 | |
| *** Liang__ has quit IRC | 10:21 | |
| *** masahito has quit IRC | 10:28 | |
| *** maaritamm has joined #openstack-meeting-alt | 10:34 | |
| *** yamamoto has joined #openstack-meeting-alt | 10:34 | |
| *** priteau has joined #openstack-meeting-alt | 10:39 | |
| *** yamamoto has quit IRC | 10:44 | |
| *** yamamoto has joined #openstack-meeting-alt | 10:59 | |
| *** yamamoto has quit IRC | 11:03 | |
| *** yamamoto has joined #openstack-meeting-alt | 11:22 | |
| *** yamamoto has quit IRC | 11:25 | |
| *** yamamoto has joined #openstack-meeting-alt | 11:25 | |
| *** jtomasek_ has joined #openstack-meeting-alt | 11:36 | |
| *** jtomasek has quit IRC | 11:39 | |
| *** ysandeep is now known as ysandeep|brb | 11:46 | |
| *** raildo has joined #openstack-meeting-alt | 11:53 | |
| *** yamamoto has quit IRC | 12:15 | |
| *** andrebeltrami has joined #openstack-meeting-alt | 12:16 | |
| *** ttsiouts_ has joined #openstack-meeting-alt | 12:16 | |
| *** ttsiouts has quit IRC | 12:20 | |
| *** rfolco has joined #openstack-meeting-alt | 12:22 | |
| *** ysandeep|brb is now known as ysandeep | 12:41 | |
| *** yamamoto has joined #openstack-meeting-alt | 12:48 | |
| *** yamamoto has quit IRC | 12:56 | |
| *** tosky has joined #openstack-meeting-alt | 12:57 | |
| *** maaritamm has quit IRC | 13:12 | |
| *** maaritamm has joined #openstack-meeting-alt | 13:12 | |
| *** Kvisle has joined #openstack-meeting-alt | 13:43 | |
| *** e0ne has quit IRC | 13:44 | |
| *** Liang__ has joined #openstack-meeting-alt | 13:44 | |
| *** e0ne has joined #openstack-meeting-alt | 13:44 | |
| *** yamamoto has joined #openstack-meeting-alt | 13:47 | |
| *** enriquetaso has joined #openstack-meeting-alt | 13:47 | |
| *** yamamoto has quit IRC | 13:58 | |
| *** rosmaita has joined #openstack-meeting-alt | 13:59 | |
| *** lvbin01 has quit IRC | 13:59 | |
| *** Liang__ is now known as LiangFang | 13:59 | |
| *** lvbin01 has joined #openstack-meeting-alt | 13:59 | |
| *** e0ne has quit IRC | 14:00 | |
| rosmaita | #startmeeting cinder | 14:00 |
| openstack | Meeting started Wed Apr 22 14:00:14 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 |
| 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 |
| rosmaita | #link https://etherpad.openstack.org/p/cinder-ussuri-meetings | 14:00 |
| rosmaita | #topic roll call | 14:00 |
| *** openstack changes topic to "roll call (Meeting topic: cinder)" | 14:00 | |
| smcginnis | o/ | 14:00 |
| whoami-rajat | hi | 14:00 |
| jungleboyj | o/ | 14:00 |
| tosky | o/ | 14:00 |
| walshh_ | hi | 14:00 |
| LiangFang | o/ | 14:00 |
| rajinir | hi | 14:00 |
| eharney | hi | 14:00 |
| *** sfernand has joined #openstack-meeting-alt | 14:00 | |
| Kvisle | hi | 14:01 |
| *** e0ne has joined #openstack-meeting-alt | 14:01 | |
| ganso | hello | 14:01 |
| sfernand | hi | 14:01 |
| *** yamamoto has joined #openstack-meeting-alt | 14:01 | |
| *** yamamoto has quit IRC | 14:01 | |
| e0ne | hi | 14:01 |
| enriquetaso | hi | 14:01 |
| lseki | hi | 14:01 |
| m5z | hi | 14:01 |
| *** liuyulong has joined #openstack-meeting-alt | 14:01 | |
| rosmaita | wow, big turnout | 14:01 |
| *** throne82_ has joined #openstack-meeting-alt | 14:01 | |
| *** yamamoto has joined #openstack-meeting-alt | 14:01 | |
| *** bnemec has joined #openstack-meeting-alt | 14:01 | |
| rosmaita | #topic announcements | 14:02 |
| *** openstack changes topic to "announcements (Meeting topic: cinder)" | 14:02 | |
| rosmaita | ok, the big announcement is that RC-1 gets released tomorrow | 14:02 |
| rosmaita | and the stable/ussuri branch is cut | 14:02 |
| rosmaita | that means all bugfixes must go to master | 14:02 |
| *** yamamoto has quit IRC | 14:02 | |
| jungleboyj | Wow, how did we get here so fast? | 14:03 |
| rosmaita | and then be proposed as backports to stable/ussuri | 14:03 |
| *** yamamoto has joined #openstack-meeting-alt | 14:03 | |
| rosmaita | if they are going to be included in the release | 14:03 |
| rosmaita | so, if you have such a bug | 14:03 |
| rosmaita | please tag it with 'ussuri-rc-potential' | 14:03 |
| rosmaita | and better yet, add it to this etherpad so it gets visibility: | 14:03 |
| rosmaita | #link https://etherpad.opendev.org/p/cinder-ussuri-rc-backport-potential | 14:04 |
| rosmaita | but yeah, it did seem to sneak up kind of fast | 14:04 |
| jungleboyj | :-) | 14:04 |
| *** gshippey has joined #openstack-meeting-alt | 14:04 | |
| smcginnis | Reviewers should also keep in mind string freeze. | 14:05 |
| rosmaita | smcginnis: thanks for mentioning that | 14:05 |
| rosmaita | we aren't supposed to change any translatable strings any more in ussuri | 14:05 |
| *** thgcorrea has joined #openstack-meeting-alt | 14:05 | |
| rosmaita | unless they contain profanity | 14:05 |
| rosmaita | but i haven't seen any of those | 14:05 |
| rosmaita | (please don't take it as a challenge) | 14:06 |
| smcginnis | :) | 14:06 |
| rosmaita | i think that's basically it -- please test and look for bugs as time allows | 14:06 |
| * jungleboyj start getting creative. | 14:07 | |
| rosmaita | i will watch the gate to see that things in flight have merged and then put up a release patch for RC-1 | 14:07 |
| rosmaita | last item is the victoria PTG | 14:07 |
| rosmaita | (virtual ptg) | 14:07 |
| *** Xuchu has joined #openstack-meeting-alt | 14:07 | |
| rosmaita | #link https://etherpad.openstack.org/p/cinder-victoria-ptg-planning | 14:08 |
| rosmaita | no one put any suggested good/bad times on it | 14:08 |
| rosmaita | sometime tomorrow i will put in our requests for time slots | 14:08 |
| rosmaita | so if you have a preference to express, please say so on the etherpad | 14:09 |
| rosmaita | look at last week's meeting log for details about the available slots, etc | 14:09 |
| rosmaita | #topic macrosan driver situation | 14:09 |
| *** openstack changes topic to "macrosan driver situation (Meeting topic: cinder)" | 14:09 | |
| rosmaita | #link https://etherpad.opendev.org/p/cinder-ussuri-driverstuff | 14:09 |
| rosmaita | ok. so this is a strange situation | 14:09 |
| rosmaita | they've got the third party CI running more or less reliably | 14:10 |
| rosmaita | but are having trouble with their "mark as supported again" patch | 14:10 |
| rosmaita | which is backwards from what we usually see | 14:10 |
| rosmaita | anyone here from macrosan? | 14:11 |
| whoami-rajat | i will just repeat what he said in the channel earlier today | 14:11 |
| rosmaita | ok, thanks | 14:11 |
| whoami-rajat | on the revert patch, the CI isn't able to work on the code | 14:12 |
| whoami-rajat | but after some refactoring, adding lines | 14:12 |
| whoami-rajat | the CI seems to work | 14:12 |
| whoami-rajat | see PS2 | 14:13 |
| whoami-rajat | https://review.opendev.org/#/c/721428/2/cinder/volume/drivers/macrosan/devop_client.py | 14:13 |
| jungleboyj | Ugh. | 14:13 |
| *** liuyulong has quit IRC | 14:13 | |
| rosmaita | yeah, that's a 1358 line change just on that file | 14:13 |
| jungleboyj | And we asked them to just do the revert. | 14:13 |
| whoami-rajat | i'm not really familiar with CI system, but i think the only way to allow CI to function is to let them do the refactor which is just adding lines | 14:14 |
| whoami-rajat | or change the CI functionality | 14:14 |
| whoami-rajat | i'm not sure | 14:14 |
| jungleboyj | Can we have them submit the refactor as a dependent follow-up patch? | 14:14 |
| rosmaita | whoami-rajat: this is ruffian-sheep working on this, right? | 14:15 |
| whoami-rajat | but i see more changes | 14:15 |
| whoami-rajat | rosmaita, yep | 14:15 |
| whoami-rajat | some function name changes and parameters as well | 14:15 |
| rosmaita | yeah, i see him in the cinder channel all the time | 14:15 |
| rosmaita | so whoami-rajat, as you understand it, the situation is that the revert-only patch passes all *our* CI, but not theirs | 14:16 |
| whoami-rajat | yep | 14:17 |
| rosmaita | i don't know what to do ... they have worked really hard on the CI, which is great, we want to encourage that | 14:18 |
| rosmaita | but we don't want to merge something that doesn't pass their own ci | 14:18 |
| whoami-rajat | even the logs aren't available to check the failure | 14:18 |
| whoami-rajat | yeah, it's important for them that their driver is marked supported for ussuri | 14:19 |
| rosmaita | smcginnis: how much would the release team scream if we try to get this as an RC-2 ? | 14:20 |
| smcginnis | That should be fine. | 14:20 |
| smcginnis | And if small updates are needed to the revert to get it to work now, that is fine. | 14:21 |
| rosmaita | ok, thanks | 14:21 |
| smcginnis | But it can't be changing ever single line in the file like they've been doing. | 14:21 |
| rosmaita | right, i don't know how that is even happening | 14:21 |
| rosmaita | whoami-rajat: you are probably closest to their time zone | 14:21 |
| smcginnis | At least part I'm assuming is changing LF to CRLF. | 14:22 |
| rosmaita | whoami-rajat: can you work with ruffian-sheep a bit more | 14:22 |
| whoami-rajat | rosmaita, yeah, i will update him but it would be great if any driver maintainer helps them as i think the main issue is regarding the CI | 14:22 |
| rosmaita | good point | 14:23 |
| rosmaita | any driver maintainer volunteers? | 14:23 |
| rosmaita | c'mon, it's worth karma points | 14:24 |
| whoami-rajat | i will try to help him work it out | 14:24 |
| rosmaita | ok, and hopefully some driver maintainer will remember that what goes around, comes around, and will also help | 14:25 |
| rosmaita | ok, so our official stance for the record is: | 14:26 |
| whoami-rajat | :D | 14:26 |
| rosmaita | we will give them until early next week to get this sorted out | 14:26 |
| jungleboyj | smcginnis: How is that generic CI setup coming? ;-) | 14:26 |
| rosmaita | i guess must merge by tuesday? | 14:26 |
| smcginnis | jungleboyj: Haha, nowhere. | 14:27 |
| whoami-rajat | i think that's reasonable time to work it out | 14:27 |
| jungleboyj | :-) | 14:27 |
| rosmaita | ok, i already see some bugs nominated on the rc-potential etherpad, so we're most likely going to have an RC-2 | 14:27 |
| rosmaita | which will allow me to procrastinate on the release note | 14:28 |
| rosmaita | ok, thanks everyone, i know it's a boring discussion, but very important to the party concerned | 14:28 |
| rosmaita | #topic NetApp E-series driver discussion | 14:28 |
| *** openstack changes topic to "NetApp E-series driver discussion (Meeting topic: cinder)" | 14:28 | |
| whoami-rajat | rosmaita++ | 14:28 |
| rosmaita | Kvisle: that's you | 14:28 |
| rosmaita | i think most of this has been discussed on the agenda? | 14:28 |
| Kvisle | Hi | 14:29 |
| Kvisle | It seems so, but if I understand it right: | 14:29 |
| Kvisle | - Someone needs to step up and take driver maintainer and CI-responsibility for a new driver which CAN be based on the old code. That someone is very unlikely to be Netapp. | 14:29 |
| Kvisle | (needs, as in ... for me to get what I want) | 14:30 |
| Kvisle | Have I understood things correct? | 14:30 |
| rosmaita | yes | 14:30 |
| rosmaita | only thing i would add is "extremely very unlikely" | 14:31 |
| rosmaita | but in any case, if you want to use it for lenovo hardware | 14:31 |
| rosmaita | would be better testing it on an actual lenovo backend anyway | 14:31 |
| jungleboyj | Whoa, did someone say Lenovo? | 14:31 |
| Kvisle | Yes | 14:32 |
| rosmaita | jungleboyj: line 90 on the agenda | 14:32 |
| Kvisle | Lenovo DE-Series are based on Netapp E-series, that's the case in point why I want to revive the driver | 14:32 |
| jungleboyj | Whoa. So you are reviving the E-Series driver for DE-Series? | 14:32 |
| rosmaita | Kvisle: your interest is mainly as a driver consumer, is that correct? | 14:33 |
| Kvisle | I could probably do this for a week a year at most | 14:33 |
| Kvisle | so yes, consumer | 14:33 |
| Kvisle | I have a question regarding the deprecation announcement which I found odd -- it was suggested that one should use the LVM driver in stead. I have no idea how that would solve any problems whatsoever. Is there anything I don't understand about how the LVM driver works? | 14:33 |
| smcginnis | Maybe the suggestion was to use LVM on top of a pool of storage provided by the E-Series? | 14:35 |
| lseki | smcginnis: yes | 14:35 |
| jungleboyj | Ah, interesting. | 14:35 |
| smcginnis | That's certainly an option for any storage that doesn't have its own driver. | 14:35 |
| jungleboyj | ++ | 14:35 |
| rosmaita | jungleboyj: is there any interest at lenovo in doing this? | 14:36 |
| lseki | Or ceph. I don't have the telemetry results right now but our customers tends to use eseries w/ lvm or ceph | 14:36 |
| jungleboyj | Though, I was frustrated when the e-series driver got deprecated for this reason. | 14:36 |
| rosmaita | this == create a DE-series driver | 14:36 |
| jungleboyj | :-) I would love to say yes but I pushed this internally a while back, when they were deprecating, and got no traction. | 14:37 |
| rosmaita | Kvisle: you don't happen to represent a transnational telco, do you? | 14:37 |
| jungleboyj | He he. | 14:38 |
| Kvisle | I represent a service provider in Norway, which is pretty large in Norwegian sense :D | 14:38 |
| rosmaita | i guess your best bet is talk to your lenovo rep and see if you can get something rolling | 14:39 |
| Kvisle | That seems like the next step for me, yes. | 14:39 |
| rosmaita | ok, thanks for bringing this up. anything else? | 14:39 |
| Kvisle | No - that's it. Thank you. | 14:39 |
| jungleboyj | Kvisle: Please feel free to reach out to me. I am at Lenovo and can do my best to get you in touch with the right people. | 14:39 |
| Kvisle | jungleboyj: that's great! | 14:40 |
| rosmaita | #topic Continued discussion of: Cinder throws error creating incremental backup from parent in another project | 14:40 |
| *** openstack changes topic to "Continued discussion of: Cinder throws error creating incremental backup from parent in another project (Meeting topic: cinder)" | 14:40 | |
| jungleboyj | jbryant1@lenovo.com Will need to involve your account team as well though. | 14:40 |
| rosmaita | ganso: the floor is yours | 14:40 |
| ganso | ok so, I included as much info as I could in the agenda etherpad | 14:40 |
| ganso | I submitted patches for 2 possible fixes | 14:40 |
| ganso | they are very simple | 14:41 |
| ganso | but their semantics are ultimately different | 14:41 |
| ganso | and I don't see any technical disadvantage to any of them | 14:41 |
| ganso | so I think we need to decide which we will go with | 14:41 |
| eharney | can we state what the (a) and (c) options are again? | 14:41 |
| ganso | yes | 14:42 |
| ganso | so (a) will create the backup always in the same project as the volume | 14:42 |
| ganso | regardless of who creates it | 14:42 |
| ganso | (c) will have separate trees | 14:43 |
| ganso | The admin or anybody else that is not running the same project as the volume's project will not be able to create an incremental backup and will create a new full one, which the new incremental backups (for that project) will follow | 14:44 |
| enriquetaso | #link https://review.opendev.org/#/c/720741/ | 14:45 |
| eharney | i think (a) is just the wrong thing to do | 14:45 |
| ganso | eharney: semantically feels wrong to me too. I actually was not sure (c) was simple until I implemented it | 14:46 |
| *** ttsiouts_ has quit IRC | 14:46 | |
| ganso | in the analisys etherpad I listed their dependencies. I intend to backport this to queens | 14:46 |
| enriquetaso | I can't find the patch for solution (c) | 14:47 |
| ganso | I also found 2 more bugs, and both (a) and (c) require different fixes (one of each of those 2 new bugs). So it is double bug-fix, and the fixes are already included in the WIP pathces I submtited | 14:47 |
| enriquetaso | would you mind to share it ganso ? | 14:47 |
| ganso | WIP Patches: https://review.opendev.org/#/c/720741/ and https://review.opendev.org/#/c/720833 | 14:47 |
| enriquetaso | thanks | 14:47 |
| ganso | I listed the 2 new bugs in the agenda etherpad as well | 14:48 |
| *** ttsiouts has joined #openstack-meeting-alt | 14:48 | |
| ganso | so, do we all incline to (c)? do we vote? | 14:48 |
| eharney | option (c) makes sense, if we have to patch up some things along the way, that sounds ok to me | 14:48 |
| ganso | btw, the CI is green on both. I got 2 runs on the (c) fix but CI failed in different voting jobs | 14:48 |
| ganso | I didn't trigger it again to spare CI resources | 14:49 |
| *** links has quit IRC | 14:49 | |
| rosmaita | i may be misunderstanding this, but (c) seems to be much different from the current model, where any user can create an entry in the backup chain | 14:50 |
| rosmaita | (C) will give each user their own complete backup chain | 14:50 |
| eharney | i'm not sure it is | 14:51 |
| eharney | is it actually possible for a user to create a backup in the same chain as another user? i.e. an incremental based on someone else's full? | 14:51 |
| eharney | that seems like it should fail now | 14:51 |
| ganso | rosmaita: I believe the current model is kinda glitchy, as it causes the bug we are trying to fix, but it would be good for us to discuss what the proper expectations are | 14:51 |
| enriquetaso | I agree with Eric on (a), that patch means that the demo user can delete backups created by the admin | 14:51 |
| smcginnis | eharney: User yes I think, but not different project. Is that what you mean? | 14:52 |
| ganso | eharney: yes, but they land in different projects. The chain (if you consider parent-child backups) is indeed just one currently | 14:52 |
| ganso | enriquetaso: but why exactly shouldn't this be allowed, if the volume owner is the demo user? | 14:53 |
| eharney | i meant different projects | 14:54 |
| ganso | if we want to have a single chain that can involve different projects, I think the fix is neither (a) or (c) | 14:55 |
| rosmaita | ok, so volume V in project P. User A and B in P. A creates a full backup of V, B then creates an incremental -- that sould be ok | 14:55 |
| eharney | ganso: i don't think we want that at all | 14:55 |
| ganso | rosmaita: yes that is ok. As users A and B are in P | 14:55 |
| rosmaita | yes, no cross-project shenanigans | 14:55 |
| rosmaita | ganso: ok, so on model (c), that will not be possible | 14:56 |
| tosky | also: would it make sense to have an tempest-like test to check those issues are (finally) working as expected, when the final decision is made? | 14:56 |
| rosmaita | A must create the incremental | 14:56 |
| rosmaita | or, B must do another full before creating an incremental | 14:56 |
| smcginnis | tosky: That would be great. | 14:57 |
| rosmaita | tosky: +++++++++++++++++ | 14:57 |
| whoami-rajat | ganso, what will be the state of backup if a user from some other project tries to create a backup? i guess it should be error | 14:57 |
| ganso | rosmaita: actually no, they are in the same project. When the admin creates the backup in the use case reported in the bug, the admin is not part of the project | 14:57 |
| eharney | ganso: right | 14:57 |
| ganso | rosmaita: I can double check that use case, but I am 99% sure it works for (c) | 14:57 |
| jungleboyj | It is nice to have a test oriented person here! | 14:58 |
| rosmaita | ganso: i will read through the etherpad and leave some questions | 14:58 |
| rosmaita | we are just about out of time again | 14:58 |
| ganso | whoami-rajat: if the user of that other project can see the volume, then it will create another tree for fix (c) | 14:58 |
| rosmaita | so the current summary is eharney thinks that (a) is too restrictive | 14:59 |
| eharney | (a) is just the wrong model of ownership | 14:59 |
| jungleboyj | 1 minute warning. | 14:59 |
| tosky | ganso: even if you don't have time to write a series of tempest tests for this, could you please make sure to document the expected workflow and some negative tests which covers the discovered bugs are well documented in one of the etherpads, so that tests can be created based on them? | 14:59 |
| ganso | ok I will abandon (a) and focus on (c) | 14:59 |
| ganso | tosky: sure, but I think we are still debating on the expected workflow | 15:00 |
| tosky | yep, that's for the after | 15:00 |
| tosky | thanks! | 15:00 |
| jungleboyj | ++ | 15:00 |
| rosmaita | ok, have to close now, continue in cinder channel | 15:00 |
| rosmaita | #endmeeting | 15:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:00 | |
| openstack | Meeting ended Wed Apr 22 15:00:53 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
| enriquetaso | ++ | 15:00 |
| jungleboyj | Thanks! | 15:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-22-14.00.html | 15:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-22-14.00.txt | 15:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-22-14.00.log.html | 15:00 |
| amotoki | #startmeeting horizon | 15:01 |
| openstack | Meeting started Wed Apr 22 15:01:55 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 |
| e0ne | hi | 15:02 |
| amotoki | #chair e0ne | 15:02 |
| openstack | Current chairs: amotoki e0ne | 15:02 |
| amotoki | hi | 15:02 |
| vishalmanchanda | hi | 15:02 |
| *** tosky has left #openstack-meeting-alt | 15:02 | |
| amotoki | let's start | 15:03 |
| *** ttsiouts has quit IRC | 15:03 | |
| rdopiera | hi | 15:03 |
| amotoki | I would like to cover ussuri-related topic first and let e0ne lead the remaining if needed | 15:03 |
| amotoki | #topic announcements/notices | 15:04 |
| *** openstack changes topic to "announcements/notices (Meeting topic: horizon)" | 15:04 | |
| amotoki | This week is the hardstring freeze for ussuri. | 15:04 |
| amotoki | we already cut stable/ussuri last week | 15:05 |
| amotoki | so we don't have much on this. | 15:05 |
| amotoki | what we need to do is to review stable/ussuri reviews as usual. | 15:05 |
| amotoki | the master branch is now open for victoria. | 15:06 |
| e0ne | amotoki: can we get this one https://review.opendev.org/#/c/721674/ backported to Ussuri? it's a bugfix with new management command? | 15:06 |
| e0ne | I'm sorry, didn't file a bug yet :( | 15:07 |
| amotoki | e0ne: it just depends on when it lands. I think it is a normal bug fix. | 15:07 |
| *** Xuchu has quit IRC | 15:07 | |
| e0ne | amotoki: ok. thanks. I'll propose a chery-pick once it will be merged to master | 15:08 |
| amotoki | e0ne: perhaps we will have another release from stable/ussuri to import translations so it would be part of the ussuri release. | 15:08 |
| amotoki | any other announcements? | 15:08 |
| e0ne | I've created an ehterpad for PTG planning | 15:09 |
| e0ne | #link https://etherpad.opendev.org/p/horizon-v-ptg | 15:09 |
| e0ne | we should request a virtual room for ptg this week if we need it | 15:09 |
| amotoki | it looks like 'v' means both 'virtual' and 'victoria' :) | 15:09 |
| e0ne | I'm going to do it today | 15:09 |
| e0ne | amotoki: :) | 15:09 |
| amotoki | which timeslots do you plan to request? | 15:10 |
| e0ne | it depends on whole the team | 15:11 |
| e0ne | I'm in UTC+3 timezone | 15:11 |
| *** gyee has joined #openstack-meeting-alt | 15:11 | |
| e0ne | I would like to have a good time for the all cores | 15:11 |
| amotoki | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html | 15:12 |
| e0ne | and some small slot to cover US timezone in case if we need to cover some cross-project dicsuccions | 15:12 |
| amotoki | timeslots are categorized into three zones. | 15:12 |
| amotoki | #link https://ethercalc.openstack.org/126u8ek25noy | 15:13 |
| e0ne | I'm OK for 13-21 UTC | 15:13 |
| amotoki | I am okay either with 13-17UTC and 4-8UTC slots | 15:14 |
| e0ne | 21:00 UTC is pretty late, so it's not my favorite time:) | 15:14 |
| e0ne | vishalmanchanda, rdopiera: what about yuo? | 15:14 |
| vishalmanchanda | I am fine with 13-21 UTC slot. | 15:14 |
| amotoki | there is no such slot "13-21UTC" :p | 15:15 |
| vishalmanchanda | oops:). | 15:15 |
| amotoki | you can check the ethercalc link above | 15:15 |
| vishalmanchanda | i am fine with any slot. | 15:15 |
| vishalmanchanda | any time slot work for me:). | 15:16 |
| vishalmanchanda | go ahead. | 15:16 |
| e0ne | :) | 15:17 |
| *** LiangFang has quit IRC | 15:17 | |
| *** links has joined #openstack-meeting-alt | 15:19 | |
| amotoki | it looks like we can move on | 15:20 |
| amotoki | #topic ussuri | 15:20 |
| *** openstack changes topic to "ussuri (Meeting topic: horizon)" | 15:21 | |
| rdopiera | e0ne: I don't have a preference | 15:21 |
| amotoki | #undo | 15:21 |
| openstack | Removing item from minutes: #topic ussuri | 15:21 |
| amotoki | 13-17UTC is converted into 10pm-2am in my local time, but I think it fits most folks in horizon. | 15:22 |
| amotoki | hopefully it can finish 16UTC but it is not a big problem to me. | 15:22 |
| *** ttsiouts has joined #openstack-meeting-alt | 15:23 | |
| amotoki | anything else? | 15:23 |
| e0ne | I think 2-3 hours will be enough | 15:23 |
| amotoki | +1 | 15:24 |
| vishalmanchanda | +1 | 15:24 |
| amotoki | if we cannot cover all, perhaps we can reserve on-demand slots | 15:24 |
| e0ne | +1 | 15:25 |
| e0ne | let's create a list of topics to discuss https://etherpad.opendev.org/p/horizon-v-ptg before we request some timeslot | 15:26 |
| amotoki | yeah, I will dump items in my mind this week | 15:28 |
| *** e0ne has quit IRC | 15:28 | |
| *** e0ne has joined #openstack-meeting-alt | 15:28 | |
| e0ne | amotoki: +1 | 15:29 |
| *** maaritamm has quit IRC | 15:29 | |
| amotoki | moving on | 15:29 |
| amotoki | #topic ussuri release | 15:29 |
| *** openstack changes topic to "ussuri release (Meeting topic: horizon)" | 15:29 | |
| amotoki | we already covered most things for ussuri release above | 15:30 |
| e0ne | great work! | 15:30 |
| amotoki | tempest-horizon plugin 1.0.0 was also releaed https://review.opendev.org/#/c/721500/ | 15:30 |
| amotoki | it is cycle-automatic | 15:31 |
| e0ne | v.1.0.0! | 15:31 |
| e0ne | :) | 15:31 |
| amotoki | hehe | 15:31 |
| amotoki | it is 1.0.0 but I am not sure we would like to continue it or merge tempest tests into the integration tests :p | 15:32 |
| e0ne | :) | 15:33 |
| amotoki | it can be visit in V cycle. we run devstack only for one test. | 15:34 |
| -amotoki- is wondering the login test in tempest-horizon might be a test which consumes energy most in OpenStack world :) | 15:34 | |
| e0ne | :) | 15:35 |
| e0ne | it's useful test to verify deployment with openstack services | 15:35 |
| amotoki | apart from that, I just started a follow-up work on the community goal "Contributor and PTL guide" | 15:35 |
| amotoki | it would be nice if we can finish it till the U release. | 15:36 |
| *** rosmaita has left #openstack-meeting-alt | 15:37 | |
| amotoki | if you have bug fixes good for ussuri, feel free to backport them and ping us. | 15:37 |
| *** maaritamm has joined #openstack-meeting-alt | 15:37 | |
| amotoki | that's all from me on ussuri | 15:38 |
| e0ne | amotoki: thanks a lot for leading us during this release! | 15:39 |
| amotoki | yw. you all helped me a lot and we are the team. | 15:39 |
| amotoki | #topic on-demand agenda | 15:40 |
| *** openstack changes topic to "on-demand agenda (Meeting topic: horizon)" | 15:40 | |
| *** belmoreira has quit IRC | 15:40 | |
| amotoki | I would like to share two gate breakages we had last week for FYI | 15:41 |
| e0ne | :( | 15:41 |
| amotoki | the one is pytest usage broke all plugin UTs | 15:41 |
| e0ne | I'm sorry for that:(. I broke plugins gates again :( | 15:42 |
| amotoki | pytest availability is checked now to make pluginUTs work without pytest https://review.opendev.org/720844 | 15:42 |
| vishalmanchanda | amotoki: thanks for the fix. | 15:42 |
| amotoki | perhaps we need to introduce a minimum cross gate with some horizon plugins | 15:43 |
| e0ne | +1 | 15:43 |
| vishalmanchanda | amotoki: I want to raise this topic last week but i completely forgot:(. | 15:43 |
| e0ne | it't in my TODO list for a while | 15:43 |
| amotoki | it would be something like what requirements repo does. | 15:43 |
| amotoki | the other thing is related to the migration to unittest.mock. | 15:44 |
| e0ne | +1 | 15:44 |
| e0ne | oops. I broke everything again | 15:44 |
| e0ne | amotoki: what was the issue with mock? | 15:44 |
| amotoki | horizon migration to unittest.mock broke horizon plugin UTs which use create_mocks from the helper function. | 15:44 |
| amotoki | create_mocks sets up mocks using unittest.mock and some other mocking use the mock library | 15:45 |
| e0ne | oh.. :( | 15:45 |
| amotoki | I haven't investigated the failure in detail but some inconsistency (mixed usage of unittest.mock and mock) caused the failure | 15:46 |
| amotoki | it was observed in heat-dashboard | 15:46 |
| amotoki | As far as I checked, it does not mean all plugin UT using create_mocks fail. | 15:47 |
| amotoki | one example failure is https://zuul.opendev.org/t/openstack/build/1abdd087265648b68026a7f2ea6d590c | 15:47 |
| amotoki | this is another reason that we need cross gate with horizon plugins | 15:48 |
| amotoki | it is hard to detect such by human reviews | 15:48 |
| amotoki | that's all I would like to share here. | 15:49 |
| vishalmanchanda | I have a question to ask about pytest | 15:49 |
| e0ne | amotoki: thank for pointing us in these topics | 15:49 |
| *** ttsiouts has quit IRC | 15:50 | |
| amotoki | we had a lot of gate breakage in this cycle..... | 15:50 |
| amotoki | django-babel, pyscss, unitest.mock, pytest..... | 15:50 |
| amotoki | might had more | 15:50 |
| amotoki | vishalmanchanda: go ahead. what is your question on pytest? | 15:51 |
| vishalmanchanda | I have noticed some of plugins adds pytest in lower-constraints.txt and test-requirements.txt which fix their gate at that time. | 15:51 |
| vishalmanchanda | So i have also purpose a patch in a plugin https://review.opendev.org/#/c/720652/ | 15:51 |
| vishalmanchanda | amotoki: Should i revert it now? | 15:52 |
| amotoki | it is up to plugin team | 15:52 |
| vishalmanchanda | ok. | 15:52 |
| amotoki | pytest requirement was an accident | 15:52 |
| amotoki | if a plugin would like to use pytest for test runner, they can continue to use it. | 15:53 |
| vishalmanchanda | agreed. | 15:53 |
| amotoki | if not, it would be nice to clean up it so that requirements files have no unnecessary stuffs. | 15:54 |
| amotoki | I have no preference on changes you made. | 15:54 |
| vishalmanchanda | amotoki: ok i will check with that team. | 15:54 |
| vishalmanchanda | thanks. | 15:55 |
| amotoki | anything else? | 15:56 |
| e0ne | nothing from me | 15:56 |
| vishalmanchanda | nothing from my side. | 15:56 |
| amotoki | let's close the meeting. thanks for joining. | 15:57 |
| amotoki | take care yourselves | 15:57 |
| vishalmanchanda | bye | 15:57 |
| amotoki | #endmeeting | 15:57 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:57 | |
| openstack | Meeting ended Wed Apr 22 15:57:34 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:57 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-22-15.01.html | 15:57 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-22-15.01.txt | 15:57 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-22-15.01.log.html | 15:57 |
| e0ne | see you next week | 15:57 |
| *** links has quit IRC | 15:58 | |
| *** igordc has joined #openstack-meeting-alt | 16:12 | |
| *** links has joined #openstack-meeting-alt | 16:20 | |
| *** maaritamm has quit IRC | 16:27 | |
| *** ttsiouts has joined #openstack-meeting-alt | 16:28 | |
| *** yaawang has joined #openstack-meeting-alt | 16:32 | |
| *** yaawang_ has quit IRC | 16:33 | |
| *** eharney has quit IRC | 16:39 | |
| *** ttsiouts has quit IRC | 16:44 | |
| *** e0ne has quit IRC | 16:47 | |
| *** e0ne has joined #openstack-meeting-alt | 16:48 | |
| *** lbragstad has quit IRC | 16:51 | |
| *** lbragstad has joined #openstack-meeting-alt | 16:51 | |
| *** eharney has joined #openstack-meeting-alt | 16:53 | |
| *** e0ne has quit IRC | 16:56 | |
| *** e0ne has joined #openstack-meeting-alt | 16:56 | |
| *** eharney has quit IRC | 17:06 | |
| *** eharney has joined #openstack-meeting-alt | 17:08 | |
| *** links has quit IRC | 17:10 | |
| *** ttsiouts has joined #openstack-meeting-alt | 17:16 | |
| *** priteau has quit IRC | 17:18 | |
| *** ttsiouts has quit IRC | 17:20 | |
| *** ganso has left #openstack-meeting-alt | 17:47 | |
| *** ganso has joined #openstack-meeting-alt | 17:47 | |
| *** ganso has left #openstack-meeting-alt | 17:48 | |
| *** ttsiouts has joined #openstack-meeting-alt | 17:49 | |
| *** ttsiouts has quit IRC | 18:22 | |
| *** maaritamm has joined #openstack-meeting-alt | 18:28 | |
| *** throne82_ has quit IRC | 18:31 | |
| *** e0ne has quit IRC | 18:34 | |
| *** e0ne has joined #openstack-meeting-alt | 18:34 | |
| *** vishalmanchanda has quit IRC | 18:43 | |
| *** e0ne_ has joined #openstack-meeting-alt | 18:43 | |
| *** e0ne has quit IRC | 18:43 | |
| *** ttsiouts has joined #openstack-meeting-alt | 18:58 | |
| *** sfernand has quit IRC | 19:00 | |
| *** ttsiouts has quit IRC | 19:03 | |
| *** e0ne_ has quit IRC | 19:04 | |
| *** ttsiouts has joined #openstack-meeting-alt | 19:32 | |
| *** diablo_rojo has joined #openstack-meeting-alt | 19:41 | |
| *** ccamacho has quit IRC | 19:54 | |
| *** sfernand has joined #openstack-meeting-alt | 19:59 | |
| *** ttsiouts has quit IRC | 20:06 | |
| *** gshippey has quit IRC | 20:31 | |
| *** enriquetaso has quit IRC | 21:07 | |
| *** ttsiouts has joined #openstack-meeting-alt | 21:16 | |
| *** maaritamm has quit IRC | 21:25 | |
| *** raildo has quit IRC | 21:37 | |
| *** geguileo has quit IRC | 21:45 | |
| *** Guest91194 has joined #openstack-meeting-alt | 21:46 | |
| *** eharney has quit IRC | 21:46 | |
| *** haleyb has quit IRC | 21:47 | |
| *** Guest91194 is now known as geguileo | 21:47 | |
| *** eharney has joined #openstack-meeting-alt | 21:49 | |
| *** ttsiouts has quit IRC | 21:50 | |
| *** haleyb has joined #openstack-meeting-alt | 21:50 | |
| *** slaweq has quit IRC | 21:58 | |
| *** ttsiouts has joined #openstack-meeting-alt | 22:20 | |
| *** ttsiouts has quit IRC | 22:29 | |
| *** rcernin has joined #openstack-meeting-alt | 22:31 | |
| *** ttsiouts has joined #openstack-meeting-alt | 22:57 | |
| *** lbragstad has quit IRC | 23:06 | |
| *** ttsiouts has quit IRC | 23:31 | |
| *** lbragstad has joined #openstack-meeting-alt | 23:35 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!