*** armax has quit IRC | 00:02 | |
*** yasufum has joined #openstack-meeting | 00:29 | |
*** rfolco has quit IRC | 00:29 | |
*** hyunsikyang__ has joined #openstack-meeting | 01:08 | |
*** hyunsikyang has quit IRC | 01:12 | |
*** yaawang has quit IRC | 01:26 | |
*** armax has joined #openstack-meeting | 01:28 | |
*** yaawang has joined #openstack-meeting | 01:28 | |
*** gyee has quit IRC | 01:44 | |
*** yaawang has quit IRC | 01:53 | |
*** yaawang has joined #openstack-meeting | 01:53 | |
*** manuvakery has joined #openstack-meeting | 02:31 | |
*** diurnalist has quit IRC | 02:33 | |
*** yaawang has quit IRC | 02:36 | |
*** yaawang has joined #openstack-meeting | 02:37 | |
*** armax has quit IRC | 02:51 | |
*** tetsuro has quit IRC | 03:13 | |
*** whoami-rajat has joined #openstack-meeting | 03:15 | |
*** yasufum has quit IRC | 03:20 | |
*** yaawang has quit IRC | 03:25 | |
*** yaawang has joined #openstack-meeting | 03:26 | |
*** rcernin has quit IRC | 03:29 | |
*** rcernin has joined #openstack-meeting | 03:41 | |
*** rh-jelabarre has quit IRC | 03:52 | |
*** rcernin has quit IRC | 03:58 | |
*** yasufum has joined #openstack-meeting | 03:59 | |
*** rcernin has joined #openstack-meeting | 04:15 | |
*** diurnalist has joined #openstack-meeting | 04:21 | |
*** psahoo has joined #openstack-meeting | 04:30 | |
*** evrardjp has quit IRC | 04:33 | |
*** evrardjp has joined #openstack-meeting | 04:33 | |
*** manuvakery has quit IRC | 04:40 | |
*** vishalmanchanda has joined #openstack-meeting | 04:40 | |
*** redrobot has quit IRC | 05:17 | |
*** markvoelker has joined #openstack-meeting | 05:19 | |
*** markvoelker has quit IRC | 05:23 | |
*** markvoelker has joined #openstack-meeting | 05:26 | |
*** markvoelker has quit IRC | 05:30 | |
*** diurnalist has quit IRC | 05:34 | |
*** psahoo has quit IRC | 05:41 | |
*** psahoo has joined #openstack-meeting | 05:54 | |
*** psahoo has quit IRC | 06:03 | |
*** lpetrut has joined #openstack-meeting | 06:10 | |
*** psahoo has joined #openstack-meeting | 06:17 | |
*** maciejjozefczyk has joined #openstack-meeting | 06:48 | |
*** dklyle has quit IRC | 06:59 | |
*** slaweq has joined #openstack-meeting | 07:02 | |
*** manpreet has joined #openstack-meeting | 07:04 | |
*** tosky has joined #openstack-meeting | 07:19 | |
*** ralonsoh has joined #openstack-meeting | 07:33 | |
*** maciejjozefczyk has quit IRC | 07:35 | |
*** ociuhandu has quit IRC | 07:44 | |
*** ociuhandu has joined #openstack-meeting | 08:00 | |
*** ianw has quit IRC | 08:01 | |
*** ianw has joined #openstack-meeting | 08:02 | |
*** ociuhandu has quit IRC | 08:03 | |
*** ociuhandu has joined #openstack-meeting | 08:03 | |
*** maciejjozefczyk has joined #openstack-meeting | 08:11 | |
*** Lucas_Gray has joined #openstack-meeting | 08:43 | |
*** e0ne has joined #openstack-meeting | 08:55 | |
*** maciejjozefczyk has quit IRC | 09:03 | |
*** yasufum has quit IRC | 10:09 | |
*** Lucas_Gray has quit IRC | 10:10 | |
*** lpetrut has quit IRC | 10:17 | |
*** moguimar has joined #openstack-meeting | 10:20 | |
*** Lucas_Gray has joined #openstack-meeting | 10:24 | |
*** rcernin has quit IRC | 10:33 | |
*** maciejjozefczyk has joined #openstack-meeting | 10:37 | |
*** markvoelker has joined #openstack-meeting | 10:41 | |
*** markvoelker has quit IRC | 10:46 | |
*** lpetrut has joined #openstack-meeting | 10:51 | |
*** zbr is now known as zbr|pto | 10:56 | |
*** moguimar has quit IRC | 11:02 | |
*** ociuhandu_ has joined #openstack-meeting | 11:03 | |
*** jmasud has quit IRC | 11:04 | |
*** masahito has joined #openstack-meeting | 11:07 | |
*** ociuhandu has quit IRC | 11:08 | |
*** raildo has joined #openstack-meeting | 11:11 | |
*** moguimar has joined #openstack-meeting | 11:54 | |
*** lbragstad_ has joined #openstack-meeting | 12:00 | |
*** lbragstad has quit IRC | 12:03 | |
*** Lucas_Gray has quit IRC | 12:12 | |
*** rh-jelabarre has joined #openstack-meeting | 12:14 | |
*** rfolco has joined #openstack-meeting | 12:24 | |
*** yamamoto has joined #openstack-meeting | 12:24 | |
*** ykatabam has quit IRC | 12:28 | |
*** eharney has joined #openstack-meeting | 12:36 | |
*** Lucas_Gray has joined #openstack-meeting | 12:46 | |
*** ociuhandu_ has quit IRC | 13:23 | |
*** ociuhandu has joined #openstack-meeting | 13:24 | |
*** TrevorV has joined #openstack-meeting | 13:33 | |
*** sluna has quit IRC | 13:38 | |
*** sluna has joined #openstack-meeting | 13:38 | |
*** rafaelweingartne has joined #openstack-meeting | 13:57 | |
slaweq | #startmeeting neutron_drivers | 14:00 |
---|---|---|
openstack | Meeting started Fri Jul 31 14:00:34 2020 UTC and is due to finish in 60 minutes. The chair is slaweq. 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: neutron_drivers)" | 14:00 | |
openstack | The meeting name has been set to 'neutron_drivers' | 14:00 |
*** ZhuXiaoYu has joined #openstack-meeting | 14:00 | |
ralonsoh | hi | 14:00 |
slaweq | Hi | 14:00 |
rafaelweingartne | Hello | 14:00 |
yamamoto | hi | 14:00 |
amotoki | hi, but I had a virtual drinking with my team, so I might be optional today. I will try my best. | 14:01 |
njohnston | o/ | 14:01 |
slaweq | I know that haleyb is on PTO this week and mlavalle will probably not be here today | 14:02 |
slaweq | but we have quorum so lets start | 14:02 |
slaweq | #topic RFEs | 14:02 |
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)" | 14:02 | |
slaweq | first one: | 14:02 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1880532 | 14:02 |
openstack | Launchpad bug 1880532 in neutron "[RFE]L3 Router should support ECMP" [Wishlist,New] - Assigned to XiaoYu Zhu (honglan0914) | 14:02 |
*** mlavalle has joined #openstack-meeting | 14:03 | |
slaweq | we already talked about it few times | 14:03 |
*** ZhuJoseph has joined #openstack-meeting | 14:03 | |
mlavalle | o/ | 14:03 |
slaweq | and reporter checked that it can be done with existing API only, using extraroutes attribute of the router | 14:03 |
slaweq | hi mlavalle :) | 14:04 |
*** ZhuXiaoYu has quit IRC | 14:05 | |
*** diurnalist has joined #openstack-meeting | 14:06 | |
slaweq | so for me this proposal looks ok now, and if we don't need to change API (or only do some very small changes, than it's fine for me) | 14:06 |
*** lpetrut has quit IRC | 14:06 | |
njohnston | I feel similarly | 14:07 |
yamamoto | fine for me | 14:08 |
mlavalle | Agree. Went thorugh it last week and came to the same conclusion | 14:08 |
amotoki | Generally looks good. I wonder whether we need to update the description of the API behavior, thought? | 14:10 |
ralonsoh | ok for me, I still need to review the uploaded patch | 14:10 |
slaweq | amotoki: yes, that's are small changes which I think will be needed | 14:11 |
slaweq | thx all for votes, I will mark it as approved, and please also review proposed spec :) | 14:11 |
amotoki | yeah, it is a reasonable improvement | 14:12 |
slaweq | ok, so next one | 14:12 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1889431 | 14:12 |
openstack | Launchpad bug 1889431 in neutron "[RFE] Add local-ip-prefix to Neutron metering label rules" [Wishlist,In progress] - Assigned to Rafael Weingartner (rafaelweingartner) | 14:12 |
slaweq | with that one I have small problem | 14:13 |
*** ZhuJoseph has quit IRC | 14:13 | |
slaweq | it seems reasonable and valid change but from the other hand it will be backward incompatible | 14:13 |
slaweq | of course we may add new api extension to make it discoverable | 14:13 |
rafaelweingartne | to be fair, the commit cited there in [1] also broke it. And the documentation was not updated accordingly; this leads people to think that there is a bug with the current code. just when looking at the storyline, we see that it was changed on purpose. | 14:15 |
slaweq | yes, that's true | 14:16 |
rafaelweingartne | That is why we proposed a migration plan for people using the current code base. I agree with you though, we would be breaking API compatibility. | 14:17 |
ralonsoh | but what's the problem of adding an extension here? | 14:18 |
ralonsoh | to the current API | 14:19 |
slaweq | ralonsoh: no problem for me | 14:19 |
ralonsoh | ah ok | 14:19 |
rafaelweingartne | What do you guys mean by API extension? | 14:19 |
njohnston | There certainly does seem to be a legitimate case for this, and with discoverability I am totally OK with this. | 14:19 |
slaweq | just wanted to mention that we need api extension to make it discoverable | 14:19 |
rafaelweingartne | is it like microversioning in Cinder? | 14:20 |
ralonsoh | rafaelweingartne, something like this https://review.opendev.org/#/c/740058/ | 14:20 |
patchbot | patch 740058 - neutron-lib - New api-def: port-numa-affinity-policy - 6 patch sets | 14:20 |
ralonsoh | when slaweq said "discoverable", that means you enable this extension and the API contains this new parameter | 14:20 |
ralonsoh | that won't break the current code | 14:20 |
amotoki | rafaelweingartne: yes, neutron does not introduce microversioning and a new feature needs to be discovered by an API extension | 14:21 |
rafaelweingartne | well, that is the problem | 14:21 |
rafaelweingartne | because we introduce a new parameter | 14:21 |
ralonsoh | and that's ok | 14:21 |
rafaelweingartne | but this new parameter will take the role/behavior of the old one | 14:21 |
ralonsoh | but referred to a new extension | 14:21 |
ralonsoh | we can discuss the technical issues in the n-lib patch | 14:22 |
amotoki | what I am not sure so far is whether how we should interprete "lcoal" now. | 14:22 |
slaweq | rafaelweingartne: this isn't a problem for sure, You will add this new parameter in new extension and that's fine | 14:22 |
rafaelweingartne | ok | 14:22 |
rafaelweingartne | I am not sure with these details in some of openstack components | 14:22 |
slaweq | rafaelweingartne: if you will need help with that, we can discuss it on neutron channel :) | 14:22 |
rafaelweingartne | sure | 14:22 |
amotoki | The problem description says that we changed the interpretation of "local"/"remote" at some time. | 14:23 |
slaweq | amotoki: that's good point | 14:23 |
rafaelweingartne | yes, here: https://github.com/openstack/neutron/commit/92db1d4a2c49b1f675b6a9552a8cc5a417973b64 | 14:23 |
slaweq | wouldn't "source" and "destination" better names? | 14:23 |
rafaelweingartne | good point :) | 14:23 |
rafaelweingartne | internally, I proposed source | 14:23 |
rafaelweingartne | but the network engineers said that it would make more sense local... | 14:24 |
rafaelweingartne | I am not sure though, which one is better | 14:24 |
amotoki | what is the real problem? what is "local"? | 14:25 |
rafaelweingartne | local_ip_prefix would be the internal network behind the router | 14:25 |
slaweq | amotoki: in fact when I'm now thinking about it, it depends on "direction" really | 14:25 |
slaweq | no? | 14:25 |
rafaelweingartne | hmm | 14:25 |
rafaelweingartne | yes and no | 14:25 |
njohnston | source and dest are directional attributes, whereas local and remote are proximal attributes | 14:26 |
amotoki | IIRC the commit clarifies the meaining of "remote" was different from other context in neutron. "remote" is external, soI think the commit is right. | 14:26 |
rafaelweingartne | the commit in [1] is using the remote attribute as the source/local IP of the VMs inside openstack | 14:27 |
rafaelweingartne | this creates confusions | 14:27 |
rafaelweingartne | people were using the remote attribute as the remote (IP outside openstack) | 14:27 |
amotoki | sounds fair. I cannot remember the whole discussion at that time. | 14:29 |
rafaelweingartne | and also, with respect to inflow and outflow, we wrote a section describind that "Neutron Metering agent changes" | 14:29 |
slaweq | ok, so local/remote will be from the "vm" point of view - local is vm IP address and remote is something in outside world, right? | 14:29 |
rafaelweingartne | exactly | 14:30 |
slaweq | that sounds good for me | 14:30 |
rafaelweingartne | and by having these two attributes we can address the need described in [1], and many others | 14:30 |
slaweq | and now it's not like that as remote_ip_prefix is in fact IP which belongs to the OpenStack vm | 14:30 |
slaweq | right? | 14:30 |
rafaelweingartne | exactly | 14:30 |
slaweq | that's why You want to change this naming convention and not only add new parameter | 14:31 |
slaweq | ok | 14:31 |
slaweq | now it seems clear for me | 14:31 |
ralonsoh | that's perfect if this is also documented | 14:32 |
rafaelweingartne | yes, it will be | 14:32 |
rafaelweingartne | same standard as I did with the granular extension for the neutron metering | 14:33 |
amotoki | I agree with the confusion discussed so far. the question now looks like whether we need to change the current interpretation in addtion to a new proposed field. | 14:33 |
amotoki | Changing the existing behavior will introduce another confusion, so we might be conservative. | 14:33 |
slaweq | amotoki: I think so as currently "remote_ip_prefix" is in fact used as local IP (belongs to OpenStack vm) | 14:34 |
amotoki | slaweq: I think so too | 14:34 |
rafaelweingartne | I would say so, otherwise, confusions would still be created by using something called "remote_IP" to indicate an IP inside OpenStack where these rules are applied | 14:34 |
amotoki | I now wonder how we can achieve this without breaking existing users.... | 14:36 |
njohnston | one way would be to create new names - let's say we use 'cloud_ip_prefix' and 'external_ip_prefix' - and deprecate remote_ip_prefix in the docs, while mapping it to cloud_ip_prefix internally | 14:38 |
*** ykatabam has joined #openstack-meeting | 14:39 | |
slaweq | njohnston: good point, maybe it could also be "internal_ip_prefix" and "external_ip_prefix" | 14:39 |
slaweq | but will that be clear for people? | 14:39 |
rafaelweingartne | that would work, but the pseudo bug would still exist, the remote_ip_prefix would need proper documentation and deprecation | 14:39 |
amotoki | yeah, it will be the best way when we have a wrong/confusing naming. | 14:39 |
rafaelweingartne | cant this create more confusions? having external and remote attributes? | 14:39 |
rafaelweingartne | at the same time | 14:40 |
amotoki | rafaelweingartne: doesn't the RFE propose to change the meaning of 'remote'? am I wrong? | 14:40 |
rafaelweingartne | yes | 14:40 |
rafaelweingartne | I mean, it depends on the perspective. The remote would start to fulfill its claim (being the remote IP) | 14:41 |
rafaelweingartne | instead of the internal/loca/vmIP | 14:41 |
amotoki | what we are wonder is how we won't break existing API users when we change the API behavior. Of course we need to clarify what the new terms mean. | 14:42 |
rafaelweingartne | yes, and that is a good point | 14:42 |
rafaelweingartne | How was the change introduced via [1] handled? That also changed the way API was being used and broke compatibility. | 14:42 |
amotoki | I believe that was not a good example. | 14:42 |
rafaelweingartne | hmm | 14:43 |
rafaelweingartne | I see | 14:43 |
njohnston | I think that remote_ip is tainted by the fact that we have to maintain API compatibility with an implementation that has the opposite meaning of the name. I think replacing and deprecating it - and making a special note in the API ref - is the best path. | 14:44 |
*** diurnalist has quit IRC | 14:44 | |
*** Lucas_Gray has quit IRC | 14:44 | |
njohnston | Perhaps 'cloud_ip" for the local and "peer_ip" for the remote would work, as they don't frame the sides in terms of an assumed reference point of the user. | 14:44 |
rafaelweingartne | ok, so I will need to add that into my proposal then, right? | 14:44 |
amotoki | njohnston: agree (but I need double check after the meeting) | 14:45 |
slaweq | njohnston: amotoki I like that proposal | 14:46 |
slaweq | that way we will not break any existing users and their applications | 14:46 |
slaweq | and we will improve our API | 14:46 |
amotoki | rafaelweingartne: I think so. we are reverting the meaning of the field twice. It should be avoided in general, so it is better to be covered in the context. | 14:46 |
rafaelweingartne | ok, I will do that then | 14:46 |
slaweq | so I'm ok to approve this rfe with the note that it should add new attributes, and just deprecate the existing one but not remove or change it's behaviour | 14:48 |
mlavalle | seems reasonable to me | 14:48 |
slaweq | are others ok too? | 14:48 |
ralonsoh | +1 | 14:48 |
amotoki | sounds good | 14:48 |
njohnston | +1 | 14:48 |
rafaelweingartne | Thank you guys | 14:48 |
slaweq | yamamoto: any thoughts? | 14:49 |
amotoki | rafaelweingartne: thanks for taking care of this complicated one. | 14:49 |
yamamoto | i'd like to abstain as i'm just confused :-) | 14:49 |
slaweq | ok | 14:50 |
slaweq | but as we have most people +1 about it, I will mark it as approved | 14:50 |
slaweq | rafaelweingartne: please propose spec with detailed description of the current status and proposed changes (api especially) | 14:51 |
rafaelweingartne | sure, I will do | 14:51 |
slaweq | thx a lot | 14:51 |
slaweq | and thx for the new proposal :) | 14:51 |
slaweq | ok, lets move on | 14:51 |
slaweq | there is third one for today | 14:51 |
slaweq | https://bugs.launchpad.net/neutron/+bug/1888487 | 14:51 |
openstack | Launchpad bug 1888487 in neutron "Change the default value of "propagate_uplink_status" to True" [Wishlist,New] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez) | 14:51 |
slaweq | from ralonsoh | 14:51 |
ralonsoh | very quick | 14:51 |
ralonsoh | this extension, "propagate_uplink_status", allows to propagate the PF status to the VF, in SRIOV | 14:52 |
ralonsoh | (that's only for SRIOV) | 14:52 |
ralonsoh | by default, the VF status will be set to enabled/disables | 14:52 |
ralonsoh | with this extension and the paremeter to True, the link status will be auto | 14:52 |
ralonsoh | my proposal: when this extension is enabled | 14:53 |
slaweq | "propagate_uplink_status" is port's parameter in API, right? | 14:53 |
ralonsoh | set "propagate_uplink_status" to True by default --> set link status to auto | 14:53 |
ralonsoh | yes | 14:53 |
ralonsoh | by default now is False | 14:53 |
ralonsoh | I want to change that | 14:53 |
slaweq | and You want to basically change default value of this attribute, right? | 14:53 |
ralonsoh | yes | 14:53 |
*** diurnalist has joined #openstack-meeting | 14:53 | |
ralonsoh | I know could sound trivial, but is a change in a default parameter | 14:54 |
ralonsoh | reason: customers enabling this extension want to have VF link status to auto | 14:54 |
*** Lucas_Gray has joined #openstack-meeting | 14:55 | |
ralonsoh | with this parameter set to True, they don't need to change nothing in the port creation | 14:55 |
ralonsoh | *change anything | 14:55 |
njohnston | I am +1 on this because I think it is very unusual for a user to actually desire the behavior that we currently have as the default | 14:56 |
*** rafaelweingartne has quit IRC | 14:56 | |
slaweq | and by default this extension isn't enabled so users who don't want to use "auto" don't have this extension loaded probably | 14:56 |
ralonsoh | exactly | 14:56 |
slaweq | I'm ok to change that | 14:57 |
slaweq | of course with "big" release note about the change :) | 14:57 |
ralonsoh | sure!! | 14:57 |
mlavalle | +1 | 14:57 |
amotoki | sounds reasonable to me too so far. | 14:57 |
ralonsoh | thank you all | 14:58 |
*** lbragstad_ is now known as lbragstad | 14:58 | |
yamamoto | +1 | 14:58 |
amotoki | do we introduce a new extension? | 14:58 |
slaweq | ok, sounds like we can approve it :) | 14:58 |
slaweq | amotoki: I'm not sure if we need that in this case TBH | 14:59 |
*** dklyle has joined #openstack-meeting | 14:59 | |
*** masahito has quit IRC | 14:59 | |
slaweq | amotoki: but we can discuss it in the review of the patch probably | 14:59 |
slaweq | ok for You? | 14:59 |
amotoki | slaweq: I am okay | 14:59 |
slaweq | thx | 14:59 |
amotoki | this is really a gray zone | 14:59 |
slaweq | we are running out of time now | 15:00 |
slaweq | thx for attending the meeting | 15:00 |
ralonsoh | bye | 15:00 |
njohnston | very productive meeting! thanks all | 15:00 |
slaweq | have a great weekend | 15:00 |
yamamoto | good night | 15:00 |
slaweq | o/ | 15:00 |
amotoki | o | 15:00 |
amotoki | o/ | 15:00 |
slaweq | #endmeeting | 15:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:00 | |
openstack | Meeting ended Fri Jul 31 15:00:22 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
njohnston | o/ | 15:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-07-31-14.00.html | 15:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-07-31-14.00.txt | 15:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-07-31-14.00.log.html | 15:00 |
*** ykatabam has quit IRC | 15:09 | |
*** yamamoto has quit IRC | 15:18 | |
*** whoami-rajat has quit IRC | 15:21 | |
*** armax has joined #openstack-meeting | 15:33 | |
*** Guest82019 has joined #openstack-meeting | 15:35 | |
*** bnemec is now known as beekneemech | 15:35 | |
*** Guest82019 is now known as redrobot | 15:37 | |
*** jmasud has joined #openstack-meeting | 15:42 | |
*** maciejjozefczyk has quit IRC | 15:45 | |
*** ociuhandu has quit IRC | 15:55 | |
*** psahoo has quit IRC | 15:56 | |
*** irclogbot_0 has quit IRC | 15:56 | |
*** irclogbot_1 has joined #openstack-meeting | 15:57 | |
*** ociuhandu has joined #openstack-meeting | 15:59 | |
*** ociuhandu has quit IRC | 16:04 | |
*** e0ne has quit IRC | 16:06 | |
*** yamamoto has joined #openstack-meeting | 16:06 | |
*** ociuhandu has joined #openstack-meeting | 16:10 | |
*** moguimar has quit IRC | 16:14 | |
*** ociuhandu has quit IRC | 16:15 | |
*** irclogbot_1 has quit IRC | 16:15 | |
*** irclogbot_2 has joined #openstack-meeting | 16:16 | |
*** yamamoto has quit IRC | 16:20 | |
*** Lucas_Gray has quit IRC | 16:41 | |
*** Lucas_Gray has joined #openstack-meeting | 16:43 | |
*** maciejjozefczyk has joined #openstack-meeting | 17:07 | |
*** Lucas_Gray has quit IRC | 17:21 | |
*** gyee has joined #openstack-meeting | 17:45 | |
*** ralonsoh has quit IRC | 17:52 | |
*** yamamoto has joined #openstack-meeting | 18:20 | |
*** yamamoto has quit IRC | 18:31 | |
*** Liang has quit IRC | 18:33 | |
*** vishalmanchanda has quit IRC | 18:50 | |
*** smcginnis has quit IRC | 20:12 | |
*** smcginnis has joined #openstack-meeting | 20:13 | |
*** TrevorV has quit IRC | 20:20 | |
*** bbowen has quit IRC | 20:53 | |
*** maciejjozefczyk_ has joined #openstack-meeting | 20:57 | |
*** maciejjozefczyk has quit IRC | 20:58 | |
*** raildo has quit IRC | 21:01 | |
*** rfolco has quit IRC | 21:01 | |
*** maciejjozefczyk has joined #openstack-meeting | 21:02 | |
*** yamamoto has joined #openstack-meeting | 21:03 | |
*** maciejjozefczyk_ has quit IRC | 21:04 | |
*** yamamoto has quit IRC | 21:07 | |
*** maciejjozefczyk has quit IRC | 21:11 | |
*** maciejjozefczyk_ has joined #openstack-meeting | 21:11 | |
*** maciejjozefczyk_ has quit IRC | 21:13 | |
*** eharney has quit IRC | 21:16 | |
*** e0ne has joined #openstack-meeting | 21:47 | |
*** beekneemech is now known as bnemec-pto | 21:48 | |
*** bbowen has joined #openstack-meeting | 22:09 | |
*** tosky has quit IRC | 22:10 | |
*** slaweq has quit IRC | 22:17 | |
*** e0ne has quit IRC | 22:20 | |
*** e0ne has joined #openstack-meeting | 22:25 | |
*** slaweq has joined #openstack-meeting | 22:30 | |
*** yamamoto has joined #openstack-meeting | 22:46 | |
*** e0ne has quit IRC | 22:48 | |
*** _erlon_ has quit IRC | 22:49 | |
*** yamamoto has quit IRC | 23:18 | |
*** diurnalist has quit IRC | 23:30 | |
*** armax has quit IRC | 23:40 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!