*** sfernand has quit IRC | 00:00 | |
*** ijw has joined #openstack-meeting | 00:10 | |
*** slaweq has joined #openstack-meeting | 00:11 | |
*** yamamoto has joined #openstack-meeting | 00:15 | |
*** slaweq has quit IRC | 00:16 | |
*** ociuhandu has joined #openstack-meeting | 00:17 | |
*** jmasud has quit IRC | 00:18 | |
*** ociuhandu has quit IRC | 00:22 | |
*** armax has joined #openstack-meeting | 00:35 | |
*** diablo_rojo has quit IRC | 00:52 | |
*** migawa is now known as migawa|AFK | 00:52 | |
*** migawa|AFK is now known as migawa | 00:52 | |
*** slaweq has joined #openstack-meeting | 01:11 | |
*** slaweq has quit IRC | 01:16 | |
*** yamamoto has quit IRC | 01:19 | |
*** Lucas_Gray has quit IRC | 01:26 | |
*** rfolco has quit IRC | 01:32 | |
*** gyee has quit IRC | 01:36 | |
*** vishalmanchanda has joined #openstack-meeting | 01:54 | |
*** slaweq has joined #openstack-meeting | 02:11 | |
*** slaweq has quit IRC | 02:16 | |
*** jmasud has joined #openstack-meeting | 02:21 | |
*** jawad_axd has joined #openstack-meeting | 02:22 | |
*** jiaopengju1 has quit IRC | 02:22 | |
*** jiaopengju1 has joined #openstack-meeting | 02:22 | |
*** jawad_axd has quit IRC | 02:27 | |
*** ijw has quit IRC | 02:41 | |
*** jawad_axd has joined #openstack-meeting | 02:43 | |
*** migawa is now known as migawa|AFK | 02:45 | |
*** migawa|AFK is now known as migawa | 02:47 | |
*** jawad_axd has quit IRC | 02:47 | |
*** rosmaita has quit IRC | 02:48 | |
*** jamesmcarthur has joined #openstack-meeting | 02:50 | |
*** rosmaita has joined #openstack-meeting | 02:51 | |
*** migawa is now known as migawa|AFK | 02:53 | |
*** armax has quit IRC | 02:54 | |
*** armax has joined #openstack-meeting | 03:07 | |
*** jamesmcarthur has quit IRC | 03:08 | |
*** slaweq has joined #openstack-meeting | 03:11 | |
*** apetrich has quit IRC | 03:13 | |
*** jamesmcarthur has joined #openstack-meeting | 03:15 | |
*** slaweq has quit IRC | 03:16 | |
*** masahito has joined #openstack-meeting | 03:19 | |
*** masahito_ has joined #openstack-meeting | 03:22 | |
*** masahito has quit IRC | 03:22 | |
*** yamamoto has joined #openstack-meeting | 03:25 | |
*** armax has quit IRC | 03:55 | |
*** migawa|AFK is now known as migawa | 03:56 | |
*** slaweq has joined #openstack-meeting | 04:11 | |
*** jmasud has quit IRC | 04:13 | |
*** jmasud has joined #openstack-meeting | 04:14 | |
*** slaweq has quit IRC | 04:16 | |
*** jamesmcarthur has quit IRC | 04:21 | |
*** masahito_ has quit IRC | 04:32 | |
*** masahito has joined #openstack-meeting | 04:40 | |
*** masahito has quit IRC | 04:46 | |
*** masahito has joined #openstack-meeting | 04:52 | |
*** nicolasbock has quit IRC | 05:09 | |
*** slaweq has joined #openstack-meeting | 05:11 | |
*** slaweq has quit IRC | 05:16 | |
*** jamesmcarthur has joined #openstack-meeting | 05:23 | |
*** jamesmcarthur has quit IRC | 05:28 | |
*** psachin has joined #openstack-meeting | 05:37 | |
*** hyunsikyang has joined #openstack-meeting | 05:46 | |
hyunsikyang | <joxyuki98> | 05:48 |
---|---|---|
*** migawa is now known as migawa|AFK | 05:53 | |
*** migawa|AFK is now known as migawa | 05:54 | |
*** slaweq has joined #openstack-meeting | 06:11 | |
*** slaweq has quit IRC | 06:16 | |
*** hyunsikyang has quit IRC | 06:23 | |
*** lajoskatona has joined #openstack-meeting | 06:24 | |
*** lajoskatona has left #openstack-meeting | 06:24 | |
*** masahito has quit IRC | 06:26 | |
*** manuvakery has joined #openstack-meeting | 06:27 | |
*** masahito has joined #openstack-meeting | 06:34 | |
*** hyunsikyang has joined #openstack-meeting | 06:34 | |
*** jhesketh has quit IRC | 06:48 | |
*** jhesketh has joined #openstack-meeting | 06:50 | |
*** slaweq has joined #openstack-meeting | 07:11 | |
*** jhesketh has quit IRC | 07:15 | |
*** slaweq has quit IRC | 07:16 | |
*** tetsuro has joined #openstack-meeting | 07:22 | |
*** jawad_axd has joined #openstack-meeting | 07:22 | |
*** tetsuro has quit IRC | 07:23 | |
*** jhesketh has joined #openstack-meeting | 07:25 | |
*** bbowen_ has joined #openstack-meeting | 07:29 | |
*** bbowen has quit IRC | 07:30 | |
*** rsimai has quit IRC | 07:56 | |
*** rsimai has joined #openstack-meeting | 07:57 | |
*** ralonsoh has joined #openstack-meeting | 07:57 | |
*** maciejjozefczyk has joined #openstack-meeting | 07:58 | |
*** slaweq has joined #openstack-meeting | 08:00 | |
*** rosmaita has quit IRC | 08:02 | |
*** rosmaita has joined #openstack-meeting | 08:04 | |
*** lpetrut has joined #openstack-meeting | 08:14 | |
*** tesseract has joined #openstack-meeting | 08:21 | |
*** slaweq has quit IRC | 08:33 | |
*** slaweq has joined #openstack-meeting | 08:37 | |
*** rcernin has quit IRC | 09:12 | |
*** lucasagomes has joined #openstack-meeting | 09:17 | |
*** apetrich has joined #openstack-meeting | 09:37 | |
*** beagles has quit IRC | 09:54 | |
*** yamamoto has quit IRC | 09:57 | |
*** hyunsikyang has quit IRC | 09:58 | |
*** rcernin has joined #openstack-meeting | 10:00 | |
*** yamamoto has joined #openstack-meeting | 10:04 | |
*** ociuhandu has joined #openstack-meeting | 10:12 | |
*** rcernin has quit IRC | 10:17 | |
*** psachin has quit IRC | 10:25 | |
*** yamamoto has quit IRC | 10:28 | |
*** vishalmanchanda has quit IRC | 10:28 | |
*** e0ne has joined #openstack-meeting | 10:30 | |
*** psachin has joined #openstack-meeting | 10:32 | |
*** yamamoto has joined #openstack-meeting | 10:39 | |
*** belmoreira has quit IRC | 10:46 | |
*** ociuhandu has quit IRC | 10:54 | |
*** ociuhandu has joined #openstack-meeting | 10:59 | |
*** ociuhandu has quit IRC | 11:01 | |
*** ociuhandu has joined #openstack-meeting | 11:01 | |
*** psachin has quit IRC | 11:10 | |
*** psachin has joined #openstack-meeting | 11:11 | |
*** yamamoto has quit IRC | 11:21 | |
*** yamamoto has joined #openstack-meeting | 11:54 | |
*** yamamoto has quit IRC | 11:59 | |
*** Lucas_Gray has joined #openstack-meeting | 12:06 | |
*** ociuhandu has quit IRC | 12:07 | |
*** ociuhandu has joined #openstack-meeting | 12:12 | |
*** nicolasbock has joined #openstack-meeting | 12:13 | |
*** psachin has quit IRC | 12:15 | |
*** ociuhandu has quit IRC | 12:18 | |
*** maciejjozefczyk has quit IRC | 12:21 | |
*** Lucas_Gray has quit IRC | 12:26 | |
*** Lucas_Gray has joined #openstack-meeting | 12:33 | |
*** maciejjozefczyk has joined #openstack-meeting | 12:37 | |
*** masahito has quit IRC | 12:42 | |
*** tetsuro has joined #openstack-meeting | 12:42 | |
*** yamamoto has joined #openstack-meeting | 12:43 | |
*** raildo has joined #openstack-meeting | 12:44 | |
*** yamamoto has quit IRC | 12:45 | |
*** rfolco has joined #openstack-meeting | 12:47 | |
*** ociuhandu has joined #openstack-meeting | 12:53 | |
*** yamamoto has joined #openstack-meeting | 13:06 | |
*** dmacpher has quit IRC | 13:09 | |
*** ociuhandu has quit IRC | 13:11 | |
*** rh-jelabarre has joined #openstack-meeting | 13:12 | |
*** ysandeep is now known as ysandeep|brb | 13:16 | |
*** ysandeep|brb is now known as ysandeep | 13:24 | |
*** Lucas_Gray has quit IRC | 13:26 | |
*** ociuhandu has joined #openstack-meeting | 13:31 | |
*** Lucas_Gray has joined #openstack-meeting | 13:32 | |
*** enriquetaso has joined #openstack-meeting | 13:35 | |
*** psachin has joined #openstack-meeting | 13:36 | |
*** ociuhandu has quit IRC | 13:45 | |
*** stephen-ma has joined #openstack-meeting | 13:46 | |
*** ociuhandu has joined #openstack-meeting | 13:49 | |
*** Lucas_Gray has quit IRC | 13:51 | |
*** ociuhandu has quit IRC | 13:55 | |
*** lajoskatona has joined #openstack-meeting | 13:56 | |
*** Lucas_Gray has joined #openstack-meeting | 13:56 | |
*** ociuhandu has joined #openstack-meeting | 13:58 | |
slaweq | #startmeeting neutron_drivers | 14:00 |
openstack | Meeting started Fri Feb 14 14:00:10 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 |
njohnston | o/ | 14:00 |
slaweq | hi | 14:00 |
ralonsoh | hi | 14:00 |
yamamoto | hi | 14:00 |
TheJulia | o/ | 14:00 |
stephen-ma | hi | 14:00 |
slaweq | lets wait few more minutes for amotoki haleyb and mlavalle | 14:01 |
haleyb | hi | 14:01 |
slaweq | hi haleyb | 14:01 |
slaweq | so we have already quorum and I think we can start | 14:01 |
slaweq | as TheJulia is here, lets start not as usual :) | 14:02 |
slaweq | #topic On Demand Agenda | 14:02 |
*** openstack changes topic to "On Demand Agenda (Meeting topic: neutron_drivers)" | 14:02 | |
slaweq | TheJulia has added topic to https://wiki.openstack.org/wiki/Meetings/NeutronDrivers | 14:02 |
*** mlavalle has joined #openstack-meeting | 14:03 | |
mlavalle | o/ | 14:03 |
njohnston | hello TheJulia | 14:03 |
amotoki | hi1 sorry for late | 14:04 |
slaweq | hi mlavalle and amotoki | 14:04 |
*** tetsuro has quit IRC | 14:04 | |
TheJulia | So bottom line is we're wondering if the mac address update can be made non-admin or covered by a specific policy because ironic is making the service more multitenanty and usable for non-admins, but we pass credentials through for port actions and are trying to avoid pulling a second admin session as the ironic service user to just update the mac address | 14:04 |
slaweq | just FYI, I started today with On demand agenda as TheJulia added some topic to it and I didn't want to hold her on the meeting for whole hour :) | 14:04 |
TheJulia | slaweq: much appreciated,.... for I have hours of meetings ahead of me :) | 14:04 |
njohnston | I wonder if this could be achieved with a policy.json modification defining a role tied to a specific service credential for Ironic | 14:05 |
slaweq | njohnston: I think it can: https://github.com/openstack/neutron/blob/master/neutron/conf/policies/port.py#L192 | 14:05 |
slaweq | it's defined there IIUC what is the need from Ironic | 14:05 |
slaweq | and it seems for me that it can be done by admin or advsvc user | 14:06 |
njohnston | slaweq: yes that is exactly what I was thinking about | 14:06 |
amotoki | are we discussing mac address update by all non-admin users or users with specific roles? | 14:07 |
TheJulia | non-admin users of baremetal, which has me thinking we're going to have to do the thing we don't want to do which is pull a separate client/session to directly update the port mac as a separate action | 14:08 |
njohnston | the thing is, Neutron has no way of distinguishing between the Ironic use case and the other use cases where non-admin access to this would be a bad idea | 14:08 |
amotoki | we prepared the advsvc role for such purpose. If it works it would be great. | 14:09 |
TheJulia | Yeah, I suspect we could just have ironic learn how to do it separately, which would prevent potential security issues. I guess well need to look at that. Anyway thanks everyone! | 14:10 |
amotoki | one thing to note is that updating mac address should be limited to a private network. | 14:11 |
amotoki | I mean "self-service network". | 14:11 |
njohnston | Are there some baremetal scenarios where it would not be a good idea to allow mac address updating? | 14:11 |
amotoki | it should not be allowed in a shared network. | 14:12 |
amotoki | in other words, the operation should be limited to a network owner IMHO. | 14:12 |
TheJulia | njohnston: none, we must be able to update the mac address for pxe booting and addressing of physical ports. | 14:12 |
TheJulia | in that case the ironic service account needs to perform the port update action for just the mac address | 14:14 |
TheJulia | since we know it and manage it | 14:15 |
njohnston | I am wondering if we could permit port update for all in policy.json and then later in the logic require specific privileges unless it's a baremetal port. | 14:16 |
njohnston | But I don't know if there are baremetal-but-not-Ironic scenarios that could bite us with that | 14:17 |
slaweq | njohnston: I'm not sure if we should do such hard coded rules for some specific kinds of resources | 14:17 |
TheJulia | that is only informed via the ?binding profile? which I think is later on, also since users can request vifs on user created networks and ironic will request it be attached to that network | 14:17 |
*** TrevorV has joined #openstack-meeting | 14:18 | |
njohnston | Having a separate admin session has the virtue of simplicity, other methods for doing it get complex quickly it seems to me | 14:18 |
TheJulia | agreed | 14:18 |
TheJulia | Thanks, I'll let the contributor working on the multitenancy feature set know! | 14:18 |
*** Lucas_Gray has quit IRC | 14:19 | |
*** ociuhandu has quit IRC | 14:19 | |
slaweq | ok, so I think we are good with Your topic TheJulia, right? You will try to use advsvc role for this action. | 14:19 |
*** ociuhandu has joined #openstack-meeting | 14:19 | |
TheJulia | yup, thanks | 14:20 |
slaweq | thx TheJulia :) | 14:21 |
slaweq | so now we can move to our regular topic | 14:21 |
slaweq | #topic RFEs | 14:21 |
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)" | 14:21 | |
slaweq | we have 2 RFEs for today | 14:21 |
slaweq | first one: | 14:21 |
slaweq | https://bugs.launchpad.net/neutron/+bug/1860521 | 14:21 |
openstack | Launchpad bug 1860521 in neutron "L2 pop notifications are not reliable" [Undecided,New] | 14:21 |
slaweq | I remember from when I was working in OVH that we had similar problems with L2pop mechanism and we added something like periodic sync of tunnels config on host | 14:24 |
njohnston | I am not sure what the impact to the message bus would be to change from fanout/cast to RPC calls | 14:25 |
slaweq | njohnston: to the message bus not much but for neutron-rpc workers which will send such messages and wait for reply, impact will be at least "noticeable" IMO | 14:27 |
njohnston | slaweq: Yeah, I was worried more about the RPC workers | 14:27 |
slaweq | njohnston: ahh, ok :) | 14:28 |
mlavalle | it's a matter of whether the mesh of tunnels works vs the cost | 14:28 |
njohnston | Does OVN use l2pop? IIRC it doesn't but I haven't looked in that part of the code in a while. | 14:28 |
slaweq | njohnston: nope | 14:29 |
amotoki | I am not sure right now which is better to switch it to RPC calls or to sync info periodically. | 14:29 |
amotoki | if the number of nodes to be informed is small, it makes sense to switch it to RPC calls. | 14:29 |
mlavalle | but I am sure the problem is more acute in large deployments | 14:30 |
njohnston | There are costs and benefits each way - if the RPC call idea adds overhead then it could make the situation in large deployments worse. With the periodic sync you have a period of time where things might not work correctly, before the next sync. | 14:31 |
mlavalle | yeap | 14:31 |
mlavalle | it's always a trade off | 14:31 |
*** jlibosva has joined #openstack-meeting | 14:31 | |
njohnston | I personally favor the periodic sync as being in keeping with our "eventually consistent" way of doing things, but I have a bias towards large deployment thinking. | 14:31 |
slaweq | actually looking at the code it will not be possible to switch always to call() from cast() | 14:32 |
mlavalle | but if the mesh of tunnels gets to a point where it doesn't work, then it's time to consider the trade offs | 14:32 |
slaweq | https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc.py | 14:32 |
slaweq | in some cases it uses fanout=True and then it can't call() be used | 14:32 |
ralonsoh | slaweq, why? | 14:33 |
ralonsoh | actually one problem we have with the MQ is that some calls are blocking | 14:33 |
slaweq | ralonsoh: https://docs.openstack.org/oslo.messaging/latest/reference/rpcclient.html#oslo_messaging.RPCClient.call | 14:34 |
slaweq | call() waits for return value so You can't send it to many hosts and wait for many replies | 14:35 |
slaweq | that's at least how I understand it | 14:35 |
ralonsoh | I know, but why do we need to use call instead of cast? | 14:35 |
ralonsoh | if the MQ is down, the server will stop working | 14:35 |
slaweq | ralonsoh: this was "Option 2" in the RFE | 14:35 |
ralonsoh | (maybe this is out of topic, sorry) | 14:36 |
amotoki | yeah, switching cast() into call() is not straight-forward. in case of fanout=True, we need to convert it into multiple call() and also need to check the status of individual call(). | 14:36 |
amotoki | using call() allows us to check the result | 14:36 |
amotoki | but perhaps it will bring another scaling issue in this case. | 14:36 |
stephen-ma | slaweq: when can an RFE can be brought up for discussion? | 14:36 |
slaweq | amotoki: yes, but IMO that's not good idea as L2pop was IMO designed to address some scale problems and such change would make it totally not scallable | 14:37 |
amotoki | slaweq: exactly | 14:37 |
amotoki | I just tried to explain what would happen. | 14:37 |
slaweq | stephen-ma: are You asking about https://bugs.launchpad.net/neutron/+bug/1861529 ? If yes, I keep it for the end of the meeting :) | 14:37 |
openstack | Launchpad bug 1861529 in neutron "[RFE] A port's network should be changable" [Wishlist,New] | 14:37 |
stephen-ma | yes that's the RFE | 14:38 |
*** jawad_axd has quit IRC | 14:38 | |
slaweq | amotoki: ralonsoh so IMO to address issue described by Oleg, we should only consider "option 1 - periodic sync mechanism" | 14:38 |
amotoki | slaweq: agree. I personally prefer to the periodic sync. | 14:38 |
ralonsoh | (I don't, that's why we have the MQ) | 14:39 |
ralonsoh | but the problem is why the MQ is not reliable | 14:39 |
*** jawad_axd has joined #openstack-meeting | 14:39 | |
ralonsoh | anyway, if making this update periodic can solve this problem, I'm ok | 14:39 |
slaweq | ralonsoh: problem here is that with cast() method neutron-server don't know if agent configured everything fine | 14:40 |
*** jawad_axd has quit IRC | 14:41 | |
ralonsoh | I will comment in the bug | 14:41 |
ralonsoh | but that should not be a server problem | 14:41 |
ralonsoh | if agent is down, server should keep working | 14:41 |
amotoki | MQ is durable in some cases, but from my operator experience it is not easy to ensure MQ msgs are reliable, so it is nice if neutron (MQ users) provides some mechanism for reliability. | 14:41 |
ralonsoh | if the agent received the config and everything went fine, ok | 14:42 |
ralonsoh | if not, the agent should communicate to the server informing about the error | 14:42 |
njohnston | The other alternative, just to play devil's advocate, is to build the reliability higher up in the stack | 14:42 |
mlavalle | which is synch of sorts, right? | 14:42 |
ralonsoh | njohnston, the reliability is on the services: agent, server, etc | 14:43 |
njohnston | ralonsoh: If the MQ never sent the message tot he agent then the agent has no idea it has something to complain about | 14:43 |
ralonsoh | the agent should be smart enough to send a warning message to the server | 14:43 |
ralonsoh | njohnston, I know | 14:43 |
ralonsoh | and if the MQ does not work, then will have a stopped Neutron server | 14:43 |
slaweq | ralonsoh: exactly how njohnston said, in case of cast() You will not have e.g. message timeout error on server side | 14:43 |
njohnston | ralonsoh: Instead of depending on the call() method the agent sends a message saying "I processed this update", and neutron server counts these acks. | 14:44 |
ralonsoh | (something very common in some bugs) | 14:44 |
njohnston | Similarly to how you design a reliable service on top of UDP, you don't have the transmission mechanism ensure reliability, you build it into the application layer | 14:44 |
ralonsoh | exactly: this should be like a UDP call, and the client should inform..... | 14:44 |
ralonsoh | exactly! | 14:45 |
ralonsoh | I was writing the same | 14:45 |
mlavalle | and all of his is a synch mechanism, isn't it? | 14:45 |
ralonsoh | goal: do NOT block the server | 14:45 |
njohnston | that requires neutron to track what agent(s) should respond to this kind of request and keep an account for responses received | 14:45 |
ralonsoh | yes | 14:45 |
ralonsoh | in a async way | 14:46 |
njohnston | mlavalle: the value here is that the approach is not periodic or timer-based | 14:46 |
mlavalle | sure | 14:46 |
*** manuvakery has quit IRC | 14:47 | |
mlavalle | whenever to asynch entities need to cooperate (server and agent for example) you need a way to fins synchronization points, periodic or otherwise | 14:47 |
*** psachin has quit IRC | 14:48 | |
mlavalle | nature of distributed systems | 14:48 |
mlavalle | I'd say the idea has merit and we should explore it further with a spce | 14:48 |
mlavalle | *spec | 14:48 |
ralonsoh | agree | 14:49 |
njohnston | My main question: the work of syncing to the database for FDB updates and then keeping an account of responses received, is it worth the effort? Compared to the simpler periodic sync mechanism. | 14:49 |
ralonsoh | IMO, you don't need to track the responses | 14:50 |
slaweq | ok, so to sumup what we discussed so far: we should continue discussion in the sync (periodic or not) mechanism in the spec, we don't want to switch from cast() to call(), right? | 14:50 |
ralonsoh | you'll have error responses or nothing | 14:50 |
njohnston | If you don't track the responses then you can't reissue the update when a response is not received | 14:50 |
ralonsoh | 1) if the agent is not working, the server will notice that, period checks | 14:50 |
ralonsoh | 2) if the agent message didn't work, the agent will reply with an error | 14:51 |
ralonsoh | 3) if the MQ is unreliable.... well, this IS a problem | 14:51 |
ralonsoh | but not Neutron's problem | 14:51 |
njohnston | But addressing 3 is the point of the RFE, it is Neutron's problem | 14:52 |
njohnston | If AMQP drops the message then neither server nor client will know there was an error | 14:52 |
njohnston | drops a casted message to be specific | 14:52 |
slaweq | I agree with njohnston here - we should do as much as we can to address such case on our side | 14:52 |
mlavalle | it is Neutron's problem in the sense that is has at least cope with it | 14:52 |
ralonsoh | ok | 14:52 |
slaweq | so, I will sum up this discussion in RFE and ask for spec to continue discussion there, right? | 14:55 |
mlavalle | slaweq: I would point out in the RFE that in light of today's discussion, we lean towards some sort of synch problem | 14:55 |
*** ociuhandu has quit IRC | 14:55 | |
mlavalle | and that we would like to explore it in a spec | 14:55 |
slaweq | mlavalle: sure | 14:55 |
njohnston | +1 | 14:56 |
amotoki | +1 | 14:56 |
ralonsoh | +1 | 14:56 |
mlavalle | I meant synch mechanism | 14:56 |
slaweq | ok, thx for discussion about this RFE - it was the good one today :) | 14:56 |
slaweq | as we are almost on top of the hour, I don't want to start discussion about next rfe | 14:57 |
slaweq | but I want to ask all of You to check https://bugs.launchpad.net/neutron/+bug/1861529 | 14:58 |
openstack | Launchpad bug 1861529 in neutron "[RFE] A port's network should be changable" [Wishlist,New] | 14:58 |
ralonsoh | ok | 14:58 |
slaweq | and that's all for today from me | 14:58 |
slaweq | thx for attending | 14:58 |
slaweq | and have a great weekend | 14:58 |
slaweq | o/ | 14:58 |
amotoki | o/ | 14:58 |
mlavalle | o/ | 14:58 |
ralonsoh | bye | 14:58 |
slaweq | #endmeeting | 14:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 14:58 | |
stephen-ma | ok | 14:58 |
openstack | Meeting ended Fri Feb 14 14:58:46 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-02-14-14.00.html | 14:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-02-14-14.00.txt | 14:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-02-14-14.00.log.html | 14:58 |
*** mlavalle has left #openstack-meeting | 14:58 | |
*** stephen-ma has quit IRC | 14:59 | |
*** gagehugo has left #openstack-meeting | 15:03 | |
*** ociuhandu has joined #openstack-meeting | 15:05 | |
*** rosmaita has left #openstack-meeting | 15:14 | |
*** apetrich has quit IRC | 15:20 | |
*** ociuhandu has quit IRC | 15:31 | |
*** eharney has joined #openstack-meeting | 15:33 | |
*** maciejjozefczyk has quit IRC | 15:42 | |
*** armax has joined #openstack-meeting | 15:53 | |
*** ociuhandu has joined #openstack-meeting | 16:06 | |
*** TrevorV has quit IRC | 16:09 | |
*** jlibosva has quit IRC | 16:10 | |
*** jamesmcarthur has joined #openstack-meeting | 16:16 | |
*** manuvakery has joined #openstack-meeting | 16:24 | |
*** rsimai has quit IRC | 16:37 | |
*** ijw has joined #openstack-meeting | 16:53 | |
*** lucasagomes has quit IRC | 16:55 | |
*** ijw has quit IRC | 16:57 | |
*** ijw has joined #openstack-meeting | 16:58 | |
*** diablo_rojo has joined #openstack-meeting | 17:00 | |
*** e0ne has quit IRC | 17:01 | |
*** yamamoto has quit IRC | 17:05 | |
*** yamamoto has joined #openstack-meeting | 17:06 | |
*** yamamoto has quit IRC | 17:06 | |
*** yamamoto has joined #openstack-meeting | 17:06 | |
*** lpetrut has quit IRC | 17:09 | |
*** yamamoto has quit IRC | 17:11 | |
*** ociuhandu has quit IRC | 17:16 | |
*** yamamoto has joined #openstack-meeting | 17:26 | |
*** tesseract has quit IRC | 17:29 | |
*** gmann is now known as gmann_afk | 17:42 | |
*** igordc has joined #openstack-meeting | 17:43 | |
*** eharney has quit IRC | 17:45 | |
*** jmasud has quit IRC | 17:45 | |
*** jmasud_ has joined #openstack-meeting | 17:45 | |
*** jamesmcarthur has quit IRC | 17:54 | |
*** lajoskatona has quit IRC | 17:55 | |
*** jamesmcarthur has joined #openstack-meeting | 17:58 | |
*** eharney has joined #openstack-meeting | 17:58 | |
*** jamesmcarthur has quit IRC | 18:07 | |
*** jamesmcarthur has joined #openstack-meeting | 18:09 | |
*** jamesmcarthur has quit IRC | 18:25 | |
*** jamesmcarthur has joined #openstack-meeting | 18:26 | |
*** manuvakery has quit IRC | 18:27 | |
*** jamesmcarthur has quit IRC | 18:31 | |
*** eharney has quit IRC | 18:33 | |
*** jamesmcarthur has joined #openstack-meeting | 18:36 | |
*** jamesmcarthur has quit IRC | 18:48 | |
*** ociuhandu has joined #openstack-meeting | 19:01 | |
*** ijw_ has joined #openstack-meeting | 19:02 | |
*** cmurphy is now known as cmorpheus | 19:05 | |
*** ijw has quit IRC | 19:05 | |
*** ociuhandu has quit IRC | 19:06 | |
*** ralonsoh has quit IRC | 19:07 | |
*** e0ne has joined #openstack-meeting | 19:15 | |
*** eharney has joined #openstack-meeting | 19:54 | |
*** eharney has quit IRC | 20:10 | |
*** gmann_afk is now known as gmann | 20:12 | |
*** igordc has quit IRC | 20:15 | |
*** e0ne has quit IRC | 20:41 | |
*** ijw has joined #openstack-meeting | 20:43 | |
*** Lucas_Gray has joined #openstack-meeting | 20:43 | |
*** ijw_ has quit IRC | 20:46 | |
*** eharney has joined #openstack-meeting | 21:15 | |
*** raildo has quit IRC | 21:29 | |
*** enriquetaso has quit IRC | 21:49 | |
*** jmasud_ has quit IRC | 21:53 | |
*** nicolasbock has quit IRC | 21:54 | |
*** yamamoto has quit IRC | 22:01 | |
*** rfolco has quit IRC | 22:02 | |
*** slaweq has quit IRC | 22:15 | |
*** rh-jelabarre has quit IRC | 22:31 | |
*** yamamoto has joined #openstack-meeting | 22:37 | |
*** ociuhandu has joined #openstack-meeting | 22:40 | |
*** ociuhandu has quit IRC | 22:42 | |
*** ociuhandu has joined #openstack-meeting | 22:43 | |
*** yamamoto has quit IRC | 22:45 | |
*** ociuhandu has quit IRC | 22:48 | |
*** slaweq has joined #openstack-meeting | 23:11 | |
*** slaweq has quit IRC | 23:15 | |
*** armax has quit IRC | 23:33 | |
*** armax has joined #openstack-meeting | 23:33 | |
*** ociuhandu has joined #openstack-meeting | 23:55 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!