Wednesday, 2020-03-04

*** slaweq has joined #openstack-meeting-400:11
*** vishalmanchanda has joined #openstack-meeting-400:11
*** slaweq has quit IRC00:15
*** igordc has joined #openstack-meeting-400:21
*** yamamoto has joined #openstack-meeting-400:23
*** k_mouza has joined #openstack-meeting-400:28
*** yamamoto has quit IRC00:28
*** k_mouza has quit IRC00:32
*** macz_ has quit IRC00:33
*** k_mouza has joined #openstack-meeting-400:34
*** igordc has quit IRC00:40
*** slaweq has joined #openstack-meeting-401:11
*** slaweq has quit IRC01:16
*** k_mouza has quit IRC01:17
*** k_mouza_ has joined #openstack-meeting-401:17
*** k_mouza_ has quit IRC01:20
*** igordc has joined #openstack-meeting-401:20
*** igordc has quit IRC01:33
*** yamamoto has joined #openstack-meeting-401:55
*** yamamoto has quit IRC02:09
*** yamamoto has joined #openstack-meeting-402:09
*** slaweq has joined #openstack-meeting-402:11
*** k_mouza has joined #openstack-meeting-402:12
*** slaweq has quit IRC02:15
*** k_mouza has quit IRC02:16
*** diablo_rojo has quit IRC02:48
*** hongbin has joined #openstack-meeting-402:50
*** slaweq has joined #openstack-meeting-403:11
*** slaweq has quit IRC03:16
*** links has joined #openstack-meeting-403:19
*** psachin has joined #openstack-meeting-403:33
*** k_mouza has joined #openstack-meeting-404:01
*** k_mouza has quit IRC04:06
*** slaweq has joined #openstack-meeting-404:11
*** slaweq has quit IRC04:17
*** hongbin has quit IRC04:54
*** diablo_rojo has joined #openstack-meeting-405:04
*** slaweq has joined #openstack-meeting-405:11
*** slaweq has quit IRC05:15
*** evrardjp has quit IRC05:35
*** evrardjp has joined #openstack-meeting-405:35
*** igordc has joined #openstack-meeting-405:38
*** yamamoto has quit IRC05:56
*** slaweq has joined #openstack-meeting-406:11
*** yamamoto has joined #openstack-meeting-406:11
*** igordc has quit IRC06:11
*** gcheresh_ has joined #openstack-meeting-406:13
*** slaweq has quit IRC06:16
*** diablo_rojo has quit IRC06:17
*** vishalmanchanda has quit IRC06:31
*** michael-beaver has joined #openstack-meeting-406:42
*** gcheresh_ has quit IRC06:51
*** vishalmanchanda has joined #openstack-meeting-406:55
*** e0ne has quit IRC06:55
*** gcheresh_ has joined #openstack-meeting-406:57
*** hamzy has quit IRC07:04
*** hamzy has joined #openstack-meeting-407:05
*** lpetrut has joined #openstack-meeting-407:05
*** lpetrut has quit IRC07:06
*** lpetrut has joined #openstack-meeting-407:06
*** slaweq has joined #openstack-meeting-407:11
*** slaweq has quit IRC07:15
*** happyhemant has joined #openstack-meeting-407:17
*** yamamoto has quit IRC07:25
*** slaweq has joined #openstack-meeting-407:38
*** slaweq has quit IRC07:43
*** slaweq has joined #openstack-meeting-407:49
*** kozhukalov has quit IRC07:51
*** yamamoto has joined #openstack-meeting-408:01
*** gcheresh_ has quit IRC08:04
*** yamamoto has quit IRC08:06
*** hamzy has quit IRC08:12
*** hamzy has joined #openstack-meeting-408:13
*** kozhukalov has joined #openstack-meeting-408:13
*** roman_g has quit IRC08:26
*** yamamoto has joined #openstack-meeting-408:32
*** gcheresh_ has joined #openstack-meeting-408:32
*** ralonsoh has joined #openstack-meeting-408:33
*** roman_g has joined #openstack-meeting-408:36
*** k_mouza has joined #openstack-meeting-408:37
*** kozhukalov has quit IRC08:39
*** k_mouza has quit IRC08:50
*** Liang__ has joined #openstack-meeting-408:55
*** ktibi has joined #openstack-meeting-408:59
*** e0ne has joined #openstack-meeting-409:05
*** michael-beaver has quit IRC09:11
*** hamzy has quit IRC09:34
*** hamzy has joined #openstack-meeting-409:34
*** yamamoto has quit IRC09:44
*** hamzy has quit IRC10:03
*** hamzy has joined #openstack-meeting-410:04
*** hamzy has quit IRC10:06
*** hamzy_ has joined #openstack-meeting-410:06
*** k_mouza has joined #openstack-meeting-410:18
*** k_mouza_ has joined #openstack-meeting-410:19
*** hamzy has joined #openstack-meeting-410:20
*** hamzy_ has quit IRC10:21
*** yamamoto has joined #openstack-meeting-410:22
*** k_mouza has quit IRC10:23
*** hamzy has quit IRC10:26
*** yamamoto has quit IRC10:27
*** hamzy has joined #openstack-meeting-410:28
*** hamzy has quit IRC10:33
*** ktibi has quit IRC11:13
*** psachin has quit IRC11:33
*** psachin has joined #openstack-meeting-411:37
*** psachin has quit IRC11:49
*** yamamoto has joined #openstack-meeting-412:27
*** yamamoto has quit IRC12:28
*** vishalmanchanda has quit IRC12:31
*** _erlon_ has quit IRC12:54
*** gagehugo has quit IRC12:54
*** _erlon_ has joined #openstack-meeting-412:55
*** npochet has quit IRC12:55
*** gagehugo has joined #openstack-meeting-412:55
*** npochet has joined #openstack-meeting-412:56
*** liuyulong has joined #openstack-meeting-413:01
*** yamamoto has joined #openstack-meeting-413:01
*** yamamoto has quit IRC13:06
*** ktibi has joined #openstack-meeting-413:08
*** thedac has quit IRC13:23
*** niedbalski has quit IRC13:24
*** thedac has joined #openstack-meeting-413:24
*** niedbalski has joined #openstack-meeting-413:24
*** enriquetaso has joined #openstack-meeting-413:30
*** michael-beaver has joined #openstack-meeting-413:31
*** vishalmanchanda has joined #openstack-meeting-413:36
*** eharney has joined #openstack-meeting-413:54
*** tosky has joined #openstack-meeting-413:55
*** Liang__ is now known as LiangFang13:56
*** rosmaita has joined #openstack-meeting-413:56
rosmaitaCourtesy reminder: Cinder meeting in #openstack-meeting-4 at 1400 UTC13:56
rosmaitajungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney walshh_ jbernard lseki sfernand rajinir ^^13:56
jungleboyjo/13:57
lsekio/13:57
*** sfernand has joined #openstack-meeting-413:58
rosmaitahello early birds ... meeting hasn't started yet!13:58
enriquetasoo/13:59
whoami-rajat:D13:59
toskyo/13:59
rosmaita#startmeeting cinder14:00
LiangFango/14:00
openstackMeeting started Wed Mar  4 14:00:18 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
eharneyhi14:00
whoami-rajatHi14:00
e0nehi14:00
rosmaitagood turnout!14:01
jungleboyjGood morning.14:01
rosmaita(there were some high-fives before the meeting officially started)14:01
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-meetings14:01
rosmaitapretty light agenda today14:01
rosmaita#topic updates14:01
*** openstack changes topic to "updates (Meeting topic: cinder)"14:01
rosmaitaok, first thing is that the final releases from rocky are out14:02
rosmaitathere were some release tooling problems that smcginnis had to fix that delayed them a bit14:02
jungleboyjThank you for getting those taken care of!14:02
rosmaitaso rocky will be tagged as -em shortly14:03
rosmaitaas a reminder, we can backport bugfixes, but there will be no more rocky releases14:03
rosmaitaother news14:03
rosmaitayou may have seen this on the ML (pretty sure I sent it out last week)14:03
rosmaitathe second session of the virtual mid-cycle is scheduled14:03
rosmaitaMonday 16 March 12:00-14:00 UTC14:04
smcginnis.o.14:04
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning14:04
jungleboyjCool.14:04
rosmaita^^ for proposing topics14:04
rosmaitathe feedback from last time was that we needed a few more reminders14:04
rosmaitaso i'll send another to the ML early next week14:05
rosmaitaand i guess, tell everyone you know about it!14:05
rosmaitaanother awareness item14:05
rosmaitathere's been a update to the vulnerability:managed policy14:05
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012721.html14:06
rosmaitaprimary change is that the security embargo that keeps a security bug non-public will be lifted after 90 days14:06
rosmaitaeven if there's been no action14:06
*** yamamoto has joined #openstack-meeting-414:06
rosmaitajust a reminder about working on a security bug14:07
rosmaitayou may be able to see it if you're a member of cinder-core-sec, or filed it yourself, or were asked to look at it14:07
rosmaitawhen you submit a patch, you have to do it by attaching the patch to the bug in Launchpad14:07
rosmaitado *not* submit a gerrit review14:07
rosmaita(because those are public)14:07
rosmaita#topic update - community goals14:08
*** openstack changes topic to "update - community goals (Meeting topic: cinder)"14:08
rosmaitagoa1 #1 was removing py2 support14:08
rosmaitai got confirmation from gmann yesterday (he's driving the goal) that cinder has completed it14:09
rosmaitagoal #2 is updating the contributor docs14:09
rosmaitai have that underway14:09
rosmaitawhat i've decided to do is to have a primary page in the cinder docs that cover the required stuff14:09
rosmaitaand then link to it from all the other cinder projects14:10
rosmaitathis is what i mean14:10
rosmaitahere's the WIP patch for cinder: https://review.opendev.org/71100614:10
rosmaitaand here's the one for os-brick: https://review.opendev.org/71101114:11
rosmaitaanyway, feel free to look at those, although the URLs are of course broken14:11
rosmaitaremaining for cinder is the list of core contributors and the list of PTL duties14:11
rosmaitawhich reminds me14:11
rosmaitawe get some latitude about what info we supply about the cinder-core14:12
rosmaitathe bare-bones would be a link to the gerrit group14:12
rosmaitahttps://review.opendev.org/#/admin/groups/83,members14:12
jungleboyjrosmaita:  Thanks for tackling the contrib docs goal.  Wanted to chat with you about that.  I will look at the patches.14:12
rosmaitabut the goal champions suggest more info, like irc nick, timezone, etc14:13
rosmaitamy thought is to put that up as a wiki page14:13
rosmaitaand then each person can control how much info is displayed14:13
smcginnisMy concern with irc nick and timezone information is that is something that requires ongoing updates and maintenance.14:13
jungleboyjrosmaita:  I like that idea.  I would encourage the cores to share more than less.14:13
toskythe os-brick thing may be seen as non-compliant with the text of the goal, but I personally think it makes sense14:13
smcginnisIn other words, highly likely to get out of sync and have stale info.14:13
toskysmcginnis, rosmaita : I usually get those details from stackalytics14:14
jungleboyjsmcginnis:  How often are our cores changing though.  :-)14:14
smcginnisThough also true our cores haven't been changing much, so maybe ok.14:14
smcginnisjungleboyj: Yeah.14:14
toskyour big brother which tracks everyone and shows the hours when anyone is active14:14
smcginnisBut I would still prefer like tosky says and link to some other source of truth for those things.14:14
rosmaitadoes stackalytics show time zones?14:14
toskyrosmaita: it shows when you are active, which is even more relevant14:14
smcginnisHonestly, I don't think people should have to know that much detail about cores.14:15
rosmaitai'm inclined to agree with smcginnis here14:15
rosmaitaok, we can start out small and enhance if the people demand it14:15
jungleboyjOk.14:15
rosmaitai'll just put a link to the gerrit group and stackalytics14:16
*** psachin has joined #openstack-meeting-414:16
smcginnis++14:16
rosmaitarelated to this, though, i've been wondering about timezone.io14:16
rosmaitahas anyone used it?14:16
rosmaitait would be helpful to me anyway to see the TZs of cores14:16
smcginnisFor your purposes, I'm good with that.14:17
rosmaitaproblem is, you have to log into it to add yourself to the cinder team14:17
toskydo you think it is needed even if you can check through stackalytics?14:17
jungleboyjHmm, I haven't used that but that is a good tool to know about.14:18
rosmaitatosky: what i'd like to see is what time it is now in each person's timezone14:18
rosmaitawith a groovy picture14:18
rosmaitaand for people like hemna who switch TZs, they can "easily" update it14:18
rosmaitai'll send invites to the core team ... don't feel obligated to do it if you think it's stupid14:19
*** kaisers has joined #openstack-meeting-414:19
rosmaitaif enough people participate, we can open it up to any active contributor14:19
*** jbernard has joined #openstack-meeting-414:19
rosmaitabecuase it would be nice to see who's available to review stuff, not just cores14:19
whoami-rajatrosmaita, ++14:19
jungleboyj++14:19
e0ne+114:20
rosmaitait doesn't help non-members, but would be useful for us maybe14:20
rosmaita#action rosmaita timezone.io invites to cinder-core14:20
rosmaitaok, last announcement14:20
rosmaita#topic announcements - follow-up on action item14:21
*** openstack changes topic to "announcements - follow-up on action item (Meeting topic: cinder)"14:21
rosmaitai am being very inconsistent about the topic changes14:21
rosmaitathey "orgainze" the minutes14:21
rosmaitaanyway14:21
rosmaitai only got around to my action item this morning14:21
rosmaitait was to email the QA team about taking over some devstack plugins14:21
rosmaitaso i figured i could put a draft on an etherpad for anyone who is interested in this14:22
rosmaitato make sure i covered the concerns correctly14:22
rosmaita#link https://etherpad.openstack.org/p/Z0rk9QPpOY14:22
rosmaitaplease take a look if you can, feel free to make revisions or bring up stuff i forgot14:23
rosmaitai'll send it out around 2pm my time, which i think is 1900 UTC14:23
rosmaitaok, that's it for announcements14:23
rosmaita#topic policy change proposal questions14:23
*** openstack changes topic to "policy change proposal questions (Meeting topic: cinder)"14:24
rosmaitai added this because we didn't have any topics earlier this morning14:24
rosmaitaanyway, we may already have a policy about this that i'm ignorant of14:24
e0nerosmaita: feel free to remove my one :)14:24
rosmaita#link https://review.opendev.org/#/c/678799/14:24
rosmaitae0ne: no, i am looking forward to yours!14:24
rosmaitaso, the proposal is to make a policy more fine grained14:25
rosmaitaso instead of just MANAGE14:25
rosmaitahave MANAGE_CREATE14:25
rosmaitaMANAGE_UPDATE14:25
rosmaitaMANAGE_DELETE14:25
rosmaitasomething like that14:25
*** ricolin has quit IRC14:25
rosmaitaso that part i'm ok with, though the naming scheme isn't quite in line with the other policies in that file14:26
e0neit sounds reasonable14:26
rosmaitamy question is14:26
eharneyi seem to recall a similar change for a different policy item, we should look at the last one for consistency/concerns... but generally i think this works14:26
rosmaitathey propose to just remove MANAGE (the current policy that covers all CRUD)14:26
rosmaitabut that would break anyone who's already configured that policy14:26
rosmaitabecuase now only the default values for the new ones will work14:26
rosmaitaso my question is (for real this time)14:27
rosmaitahow do we handle this?14:27
rosmaitasince the default is whatever the admin-api default is, i'm not worried about security14:27
rosmaitabut it could be annoying14:27
eharneyi'm not sure of the significance of the 'path' changes14:28
rosmaitais a release note enough, or do we need something in the code to handle both during a deprecation period?14:28
rosmaitaeharney: yeah, i didn't look closely at that, i think that's only used for generating the sample file14:28
rosmaitaas a documentation thing14:29
rosmaitawell, we don't have to settle this now14:29
rosmaitajust wanted to bring it up in case we already had an answer somewhere14:29
rosmaitathat's all from me14:30
eharneyone sec14:30
eharneyhttps://review.opendev.org/#/c/571563/ was the last one14:30
rosmaitathanks14:30
eharneymaybe we learned something there14:31
eharney(that's all)14:31
rosmaitathanks, that is helpful -- looks like some of these points came up on the review14:31
rosmaitai'll look it over and revisit next week if there are still open questions14:32
rosmaita#topic changes for backup configuration14:32
*** openstack changes topic to "changes for backup configuration (Meeting topic: cinder)"14:32
rosmaitae0ne: that's you!14:33
e0nethanks, rosmaita14:35
e0neI'm hitting with volume drivers configuration for a generic backups14:35
e0neprobably, this will require a new spec or update an old one, but I would like to have some feedback sooner14:36
e0nemy idea is to decouple backup-specific configuration from the [DEFAULT] section14:36
e0neso we can implement 2 solutions:14:37
e0ne1) just add a [backup] section14:37
e0ne2) allow volume drivers confit to have 'is_backup' flag and add 'enabled_backup_backends' section14:37
e0ne#2 will be a less complex to implement14:38
eharneywhy is the 'is_backup' flag needed if the backend is listed in enabled_backup_backends?14:38
e0neeharney: you're right, we don't need it14:38
* e0ne didn't recovered from the vacation yet:(14:39
jungleboyje0ne:  That is a good problem to have.14:39
rosmaitahope that means you had a good vacation!14:39
e0neso #2 is to add `enabled_backup_backends` config option14:39
e0neI prefer to follow this way with enabled_backup_backends14:40
jungleboyjSo, enabled_backup_backends would be just like enabled_drivers right.  Just for backups?14:40
e0nerosmaita: I did:)14:40
e0nejungleboyj: yes14:40
eharneydo we support something like volume multi-backend for backups?14:40
jungleboyjWould it use the same [volume] config section?14:40
e0neeharney: technically, we support it now, but we can't schedule backups to the specific host/backend14:40
jungleboyjOr would a separate one need to be created for backup?14:41
eharneyit would be a new section to create another instance of the volume driver (as a backup driver), i think14:41
e0nejungleboyj: sorry, didn't get your question14:41
jungleboyjIf the section to configured the driver for backup would need to be a new section in the file.14:42
e0nejungleboyj: yes, it will be a new section in a cinder.conf14:43
jungleboyjOk.14:43
e0neand I do understand that we need to care about backward-compatibility14:43
jungleboyjI think that that approach makes sense.14:44
e0nedo I need to propose a spec for this?14:45
smcginnisThat would probably be good.14:45
eharneyyes14:45
smcginnisSeems like there are enough details that we need to capture and understand.14:45
rosmaitait will make the documentation easier later, too14:45
*** links has quit IRC14:45
jungleboyjYeah.14:46
rosmaitait sounds reasonable, though14:46
e0neok, I'll come back with a spec and some code before the next meeting14:47
rosmaitagreat!14:47
jungleboyj++14:47
rosmaita#topic open discussion14:47
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:47
LiangFanghi team, I have two questions about plugin. 1) who would create the repo devstack-plugin-open-cas please? me or cinder cores? 2) This plugin would be called by CI, right? Where can I find the code of CI, so I can make sure devstack-plugin-open-cas works correctly with CI. Thanks.14:48
e0nethanks for the feedback!14:48
smcginnisLiangFang: Infra would need to create any repos.14:48
rosmaitayeah, i guess the first thing would be to request the repo14:49
rosmaitaas far as creation goes, it would be you, mostly14:49
smcginnisLiangFang: You would need to test locally to make sure it works with devstack. Then create a zuul job that uses it to run tempest (or whatever other kind of testing).14:49
LiangFangok, so I need to contact infra team, right?14:50
rosmaitai guess the devstack-ceph-plugin and the stuff in devstack/lib/cinder/plugins would be good examples of how to wire it together14:50
rosmaitaLiangFang: yes, i think there's a doc page explaining this, i will look while we are talking14:51
LiangFangthanks, I will take a look of doc14:51
rosmaitai think this is it:14:52
rosmaita#link https://docs.openstack.org/infra/manual/creators.html14:52
LiangFangthanks14:52
rosmaitathere's probably stuff in there that you won't need to do14:52
rosmaitaLiangFang: ping me if you need help on getting this set up14:52
LiangFangI will study how to create a zuul job from some doc14:52
LiangFangrosmaita: thanks14:52
rosmaitaLiangFang: btw, the name of the software is "open-cas", not "opencas" -- is that right?14:53
eharneyi can maybe look at how i did this for devstack-plugin-nfs, but that was years ago14:53
LiangFangI see the name is: OpenCAS or open-cas14:53
LiangFangeharney: thanks14:54
rosmaitaok, we can keep the hyphen14:54
LiangFangok14:54
rosmaitajust want to be sure ... it's always really hard to rename anything14:54
rosmaitaso 'devstack-plugin-open-cas' seems good14:55
LiangFanghttps://open-cas.github.io/getting_started_open_cas_linux.html14:55
LiangFangthey are using open-cas14:55
rosmaitagreat, that settles it14:56
rosmaitajust a few minutes left ... anyone have anything they'd like to bring up?14:56
LiangFangdo you know how to publish a white paper in openstack website?14:57
rosmaitaLiangFang: no, maybe contact jimmy mcarthur? anyone know?14:58
smcginnisLiangFang: Yeah, you can ask Jimmy.14:58
smcginnisEither a superuser article, or on a blog that would get picked up by plant.o.o.14:58
rosmaitaJimmy McArthur <jimmy@openstack.org>14:59
LiangFangthanks:)14:59
jungleboyjYeah, I would start with Jimmy.14:59
rosmaitaok, i guess that's it for today ... thanks everyone!14:59
jungleboyjThank you!14:59
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
LiangFangthank you team!15:00
openstackMeeting ended Wed Mar  4 15:00:00 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-03-04-14.00.html15:00
*** psachin has quit IRC15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-03-04-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-03-04-14.00.log.html15:00
whoami-rajatThanks!15:00
*** eharney has quit IRC15:10
*** lpetrut has quit IRC15:18
*** gcheresh_ has quit IRC15:31
*** tosky has left #openstack-meeting-415:34
*** michael-beaver has quit IRC15:40
*** kaisers has quit IRC15:40
*** psachin has joined #openstack-meeting-415:40
*** yamamoto has quit IRC15:46
*** yamamoto has joined #openstack-meeting-415:47
*** yamamoto has quit IRC15:50
*** eharney has joined #openstack-meeting-415:52
*** psachin has quit IRC15:56
*** psachin has joined #openstack-meeting-416:05
*** jbernard has left #openstack-meeting-416:06
*** yamamoto has joined #openstack-meeting-416:27
*** yamamoto has quit IRC16:33
*** ricolin has joined #openstack-meeting-416:37
*** psachin has quit IRC16:53
*** gcheresh_ has joined #openstack-meeting-416:58
*** gcheresh_ has quit IRC17:04
*** ktibi has quit IRC17:28
*** igordc has joined #openstack-meeting-417:33
*** evrardjp has quit IRC17:35
*** evrardjp has joined #openstack-meeting-417:35
*** ktibi has joined #openstack-meeting-417:46
*** ktibi has quit IRC17:51
*** igordc has quit IRC18:04
*** igordc has joined #openstack-meeting-418:05
*** diablo_rojo has joined #openstack-meeting-418:11
*** e0ne has quit IRC18:12
*** danielarthurt has joined #openstack-meeting-418:20
*** igordc has quit IRC18:27
*** gcheresh_ has joined #openstack-meeting-418:29
*** igordc has joined #openstack-meeting-418:33
*** gcheresh_ has quit IRC18:50
*** k_mouza_ has quit IRC18:56
*** gcheresh_ has joined #openstack-meeting-419:01
*** sfernand has quit IRC19:17
*** dmellado has quit IRC19:24
*** dmellado has joined #openstack-meeting-419:25
*** admcleod has quit IRC19:32
*** admcleod has joined #openstack-meeting-419:33
*** ralonsoh has quit IRC19:38
*** gcheresh_ has quit IRC19:52
*** eharney has quit IRC20:16
*** e0ne has joined #openstack-meeting-420:17
*** gcheresh_ has joined #openstack-meeting-421:24
*** gcheresh_ has quit IRC21:30
*** yamamoto has joined #openstack-meeting-421:43
*** ktibi has joined #openstack-meeting-421:47
*** yamamoto has quit IRC21:49
*** ktibi has quit IRC21:51
*** eharney has joined #openstack-meeting-421:52
*** enriquetaso has quit IRC21:59
*** slaweq has quit IRC22:21
*** slaweq has joined #openstack-meeting-423:11
*** slaweq has quit IRC23:16

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