| *** apearson has quit IRC | 00:02 | |
| *** smatzek has quit IRC | 00:04 | |
| *** thorst has joined #openstack-powervm | 00:59 | |
| *** thorst has quit IRC | 01:04 | |
| *** dwayne has quit IRC | 01:23 | |
| *** dwayne has joined #openstack-powervm | 01:24 | |
| *** thorst has joined #openstack-powervm | 01:45 | |
| *** thorst has quit IRC | 01:50 | |
| *** thorst has joined #openstack-powervm | 02:17 | |
| *** dwayne has quit IRC | 02:21 | |
| *** thorst has quit IRC | 02:21 | |
| *** thorst has joined #openstack-powervm | 02:48 | |
| *** thorst has quit IRC | 02:53 | |
| *** jwcroppe has quit IRC | 03:07 | |
| *** jwcroppe has joined #openstack-powervm | 03:08 | |
| *** kotra03 has joined #openstack-powervm | 03:19 | |
| *** mdrabe_ has quit IRC | 03:54 | |
| *** mdrabe_ has joined #openstack-powervm | 03:55 | |
| *** mdrabe_ has quit IRC | 04:31 | |
| *** thorst has joined #openstack-powervm | 04:48 | |
| *** kotra03 has quit IRC | 04:49 | |
| *** apearson has joined #openstack-powervm | 05:16 | |
| *** thorst has quit IRC | 05:42 | |
| *** thorst has joined #openstack-powervm | 05:45 | |
| *** thorst has quit IRC | 05:54 | |
| *** kotra03 has joined #openstack-powervm | 06:02 | |
| *** apearson has quit IRC | 06:13 | |
| *** thorst has joined #openstack-powervm | 06:24 | |
| *** thorst has quit IRC | 06:30 | |
| *** thorst has joined #openstack-powervm | 06:41 | |
| *** AlexeyAbashkin has quit IRC | 06:44 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 06:46 | |
| *** thorst has quit IRC | 06:46 | |
| *** thorst has joined #openstack-powervm | 06:57 | |
| *** thorst has quit IRC | 07:05 | |
| *** jwcroppe has quit IRC | 07:32 | |
| *** thorst has joined #openstack-powervm | 07:33 | |
| *** jwcroppe has joined #openstack-powervm | 07:36 | |
| *** thorst has quit IRC | 07:41 | |
| *** thorst has joined #openstack-powervm | 08:11 | |
| *** thorst has quit IRC | 08:16 | |
| *** thorst has joined #openstack-powervm | 08:28 | |
| *** thorst has quit IRC | 08:33 | |
| *** k0da has joined #openstack-powervm | 08:38 | |
| *** thorst has joined #openstack-powervm | 08:44 | |
| *** thorst has quit IRC | 08:51 | |
| *** kotra03 has quit IRC | 08:56 | |
| *** kotra03 has joined #openstack-powervm | 08:58 | |
| *** thorst has joined #openstack-powervm | 09:23 | |
| *** thorst has quit IRC | 09:28 | |
| *** thorst has joined #openstack-powervm | 09:40 | |
| *** thorst has quit IRC | 09:44 | |
| *** thorst has joined #openstack-powervm | 09:56 | |
| *** thorst has quit IRC | 10:04 | |
| *** viclarson has joined #openstack-powervm | 10:10 | |
| *** thorst has joined #openstack-powervm | 10:16 | |
| *** thorst has quit IRC | 10:20 | |
| *** thorst has joined #openstack-powervm | 10:32 | |
| *** kotra03 has quit IRC | 10:34 | |
| *** thorst has quit IRC | 10:40 | |
| *** thorst has joined #openstack-powervm | 11:08 | |
| *** smatzek has joined #openstack-powervm | 11:09 | |
| *** thorst has quit IRC | 11:16 | |
| *** viclarson_ has joined #openstack-powervm | 11:26 | |
| *** viclarson has quit IRC | 11:30 | |
| *** kotra03 has joined #openstack-powervm | 11:31 | |
| *** thorst has joined #openstack-powervm | 11:43 | |
| *** thorst has quit IRC | 11:52 | |
| *** edmondsw has joined #openstack-powervm | 12:02 | |
| *** thorst has joined #openstack-powervm | 12:19 | |
| *** thorst has quit IRC | 12:28 | |
| *** mdrabe has joined #openstack-powervm | 12:29 | |
| *** dwayne has joined #openstack-powervm | 12:34 | |
| *** tblakes has joined #openstack-powervm | 12:50 | |
| *** thorst_ has joined #openstack-powervm | 12:59 | |
| *** efried has joined #openstack-powervm | 12:59 | |
| efried | viclarson_, we keep missing each other. | 13:00 |
|---|---|---|
| efried | apearson said the following yesterday: | 13:00 |
| efried | "efried / viclarson_ - so the first thing to check - are the VIOSs up and running? Assuming so, grab the console for the novalink lpar. Where is it stopping? Is it sitting at SMS? If so, try selecting the boot device and continue the boot. Is it erroring out on boot due to a filesystem that needs to be fsck'ed? If so, choose Recovery from the grub prompt and boot into the recovery mode to run fsck on the filesystem. | 13:00 |
| *** thorst_ has quit IRC | 13:04 | |
| viclarson_ | i think it were unrecoverable errors at filesystem | 13:09 |
| efried | Okay. Let us know if you have further issues. | 13:09 |
| viclarson_ | ty, doensnt matter, already reinstalled | 13:09 |
| efried | And it's working now? | 13:09 |
| viclarson_ | looks like | 13:10 |
| efried | Great | 13:10 |
| viclarson_ | reinstalled from scratch | 13:10 |
| viclarson_ | not with recovery | 13:10 |
| viclarson_ | recovery doenst work | 13:10 |
| efried | Some problems are... unrecoverable. | 13:10 |
| viclarson_ | mb | 13:11 |
| efried | I'm curious (because we like to know who's using our stuff) - where are you from, and what's your interest in NovaLink? | 13:11 |
| efried | adreznec, yt? | 13:13 |
| efried | Can you please +2 https://review.openstack.org/#/c/373415/ (since I've "contributed" to it now)? | 13:13 |
| *** thorst_ has joined #openstack-powervm | 13:35 | |
| *** smatzek has quit IRC | 13:36 | |
| *** thorst_ has quit IRC | 13:40 | |
| *** viclarson_ has quit IRC | 13:43 | |
| *** thorst_ has joined #openstack-powervm | 13:51 | |
| *** burgerk has joined #openstack-powervm | 13:56 | |
| *** thorst_ has quit IRC | 13:56 | |
| *** burgerk has quit IRC | 14:07 | |
| *** thorst_ has joined #openstack-powervm | 14:07 | |
| *** dwayne has quit IRC | 14:11 | |
| *** tjakobs has joined #openstack-powervm | 14:14 | |
| *** thorst_ has quit IRC | 14:16 | |
| adreznec | efried: sure, I'll take a look here | 14:26 |
| efried | Thanks | 14:26 |
| efried | adreznec, it was +2 - all I changed was the path to the pypowervm req | 14:26 |
| *** thorst_ has joined #openstack-powervm | 14:29 | |
| adreznec | efried: yep, LGTM. Looks ready to merge as well, I'll throw a WF+1 on it here | 14:29 |
| efried | Or I can. Either way. | 14:30 |
| *** tblakes has quit IRC | 14:30 | |
| efried | chmod666org is waiting for it ;-) | 14:30 |
| adreznec | It better merge soon then, otherwise he could find Drew and I here at Edge and hold us hostage until it does! | 14:32 |
| *** smatzek has joined #openstack-powervm | 14:37 | |
| *** smatzek has quit IRC | 14:38 | |
| *** smatzek_ has joined #openstack-powervm | 14:38 | |
| *** smatzek_ is now known as smatzek | 14:39 | |
| *** burgerk has joined #openstack-powervm | 14:39 | |
| *** burgerk_ has joined #openstack-powervm | 14:41 | |
| *** burgerk has quit IRC | 14:44 | |
| *** tblakes has joined #openstack-powervm | 14:45 | |
| efried | thorst_, any chance of getting 3979 reviewed? | 14:45 |
| thorst_ | will try...I need about 30 minutes for other stuff :-( | 14:46 |
| efried | pah, "other stuff" | 14:46 |
| efried | thorst_, if it helps, the delta from PS2 is almost exclusively doc | 14:47 |
| thorst_ | well, I'm just bottlenecked on a final presentation, 100 e-mails and bleh. Will loop back on it today for sure...just hoping that's in 30 min and not a few hours | 14:47 |
| *** mdrabe_ has joined #openstack-powervm | 14:48 | |
| *** catintheroof has joined #openstack-powervm | 14:50 | |
| *** mdrabe has quit IRC | 14:52 | |
| *** mdrabe_ is now known as mdrabe | 14:55 | |
| *** viclarson has joined #openstack-powervm | 15:00 | |
| *** dwayne has joined #openstack-powervm | 15:03 | |
| *** viclarson has quit IRC | 15:08 | |
| *** k0da has quit IRC | 15:29 | |
| thorst_ | efried: what would you think of having two new event types. One for pypowervm and one for true clients? Or does that drive change down into the REST API itself? | 15:35 |
| efried | thorst_, yeah, REST API controls the type entirely. When we (any REST client) PUT one, it's CUSTOM_CLIENT_EVENT. | 15:35 |
| thorst_ | k... | 15:36 |
| thorst_ | bleh | 15:36 |
| efried | It's based on an enum, so at the very least, they can't just let us arbitrarily use any string. | 15:36 |
| thorst_ | right right | 15:36 |
| efried | We could ask for a new enum | 15:36 |
| efried | But how do we "prove" we're coming from pypowervm? | 15:36 |
| thorst_ | no, because they shouldn't know about pypowervm as a client | 15:36 |
| efried | right | 15:36 |
| thorst_ | right...exactly | 15:36 |
| efried | We need to use the data/detail to differentiate. | 15:36 |
| thorst_ | but its kinda where I'm going with how does neutron know that pypowervm is producing an event. | 15:37 |
| thorst_ | but yeah, like you said | 15:37 |
| efried | Along the lines of what I did in https://review.openstack.org/373532 | 15:37 |
| thorst_ | that can be done in data/detail. | 15:37 |
| thorst_ | gotta run...review looks OK but I'm not through yet | 15:37 |
| thorst_ | will be back in 30 | 15:37 |
| efried | k | 15:37 |
| *** thorst_ has quit IRC | 15:37 | |
| *** thorst_ has joined #openstack-powervm | 16:08 | |
| *** jwcroppe has quit IRC | 16:10 | |
| *** thorst_ has quit IRC | 16:12 | |
| *** thorst_ has joined #openstack-powervm | 16:18 | |
| *** thorst__ has joined #openstack-powervm | 16:20 | |
| *** thorst_ has quit IRC | 16:22 | |
| *** viclarson has joined #openstack-powervm | 16:38 | |
| *** seroyer has joined #openstack-powervm | 16:40 | |
| *** k0da has joined #openstack-powervm | 17:01 | |
| *** thorst__ has quit IRC | 17:11 | |
| *** seroyer has quit IRC | 17:12 | |
| *** apearson has joined #openstack-powervm | 17:12 | |
| *** thorst_ has joined #openstack-powervm | 17:14 | |
| *** thorst__ has joined #openstack-powervm | 17:16 | |
| *** esberglu has joined #openstack-powervm | 17:16 | |
| *** thorst_ has quit IRC | 17:18 | |
| *** thorst__ has quit IRC | 17:21 | |
| *** thorst_ has joined #openstack-powervm | 17:21 | |
| *** viclarson has quit IRC | 17:24 | |
| *** thorst_ has quit IRC | 17:25 | |
| *** apearson has quit IRC | 17:33 | |
| *** apearson has joined #openstack-powervm | 17:36 | |
| *** apearson_ has joined #openstack-powervm | 17:41 | |
| *** apearson has quit IRC | 17:41 | |
| *** thorst_ has joined #openstack-powervm | 17:51 | |
| *** thorst__ has joined #openstack-powervm | 17:56 | |
| *** thorst_ has quit IRC | 17:56 | |
| *** thorst__ has quit IRC | 17:57 | |
| *** thorst_ has joined #openstack-powervm | 17:57 | |
| *** seroyer has joined #openstack-powervm | 17:58 | |
| *** thorst_ has quit IRC | 18:24 | |
| *** thorst_ has joined #openstack-powervm | 18:25 | |
| *** seroyer has quit IRC | 18:28 | |
| *** apearson_ has quit IRC | 18:29 | |
| *** thorst_ has quit IRC | 18:30 | |
| *** thorst_ has joined #openstack-powervm | 18:31 | |
| efried | thorst_, what do you think of eliminating the interval altogether? | 18:31 |
| efried | (edmondsw ^^) | 18:31 |
| efried | The fact that it's there at all implies that the author (understandably - no docs and a weird API) didn't know about the pseudo-synchronous business. The average consumer will realize a "performance boost" if we get rid of it. And I can't see a downside. It's not like it will cause significant extra thrashing. In the worst case - a listener on a totally steady-state system - you'll issue a GET every 10s instead of eve | 18:33 |
| edmondsw | i was the author, and I'm still not aware of what you mean by pseudo-synchronous | 18:35 |
| *** thorst_ has quit IRC | 18:35 | |
| efried | edmondsw, just so. Here's how it works: | 18:38 |
| efried | When you do the GET, if the REST server has any events waiting, it returns 'em all right away. | 18:38 |
| efried | If there are no events waiting, it waits for some to arrive; and as soon as any do, it returns 'em all right away. | 18:38 |
| efried | If it has waited for 10s, it returns an empty feed. | 18:38 |
| efried | So it's designed explicitly for the client to poll it in a hard loop, with no client-side sleeping, for optimal efficiency. | 18:39 |
| efried | That is, you'll get events as soon as they're available. You don't have to worry about how much stuff happened while you were sleeping. | 18:39 |
| efried | And yes, it's very clever. The author applied for a patent. (Though as far as I can tell, it has not been issued yet.) | 18:39 |
| *** kotra03 has quit IRC | 18:47 | |
| *** esberglu has quit IRC | 19:03 | |
| *** thorst_ has joined #openstack-powervm | 19:08 | |
| edmondsw | efried, so if it waited for 10s, and returns an empty feed, we'd just immediately call again? | 19:10 |
| efried | yup | 19:10 |
| edmondsw | cool | 19:10 |
| mdrabe | that's patentable? | 19:10 |
| efried | And it would wait another 10s, unless there were events to return. | 19:10 |
| edmondsw | yeah, if there isn't already a patent for it | 19:11 |
| efried | Well, I sure thought so. The author was skeptical, but I talked him into submitting a disclosure. | 19:11 |
| efried | At least, I think he submitted it. He wrote it up. Maybe he never pushed it through. | 19:11 |
| efried | Cause I asked the patent folks about it, and they couldn't find it. | 19:11 |
| edmondsw | I think there may be a similar web technology | 19:11 |
| efried | At this point it's been in the field for long enough that it's moot anyway. | 19:12 |
| efried | But it would've been neat if the "similar web technology" came afterward. $$ | 19:12 |
| edmondsw | no, I think it's probably older... though maybe different enough... anyway | 19:13 |
| edmondsw | so I think I'd be fine with getting rid of the interval altogether and just always doing this | 19:13 |
| efried | Cool. | 19:13 |
| efried | Maybe I'll propose that as a separate patch. | 19:13 |
| *** thorst_ has quit IRC | 19:28 | |
| *** miltonm_ has quit IRC | 19:43 | |
| *** thorst_ has joined #openstack-powervm | 19:54 | |
| *** miltonm has joined #openstack-powervm | 19:57 | |
| *** seroyer has joined #openstack-powervm | 19:58 | |
| *** seroyer has quit IRC | 20:05 | |
| *** thorst_ has quit IRC | 20:06 | |
| *** thorst_ has joined #openstack-powervm | 20:08 | |
| *** seroyer has joined #openstack-powervm | 20:15 | |
| *** thorst_ has quit IRC | 20:16 | |
| *** jwcroppe has joined #openstack-powervm | 20:27 | |
| *** seroyer_ has joined #openstack-powervm | 20:28 | |
| *** seroyer has quit IRC | 20:29 | |
| *** seroyer_ is now known as seroyer | 20:29 | |
| *** dwayne has quit IRC | 20:31 | |
| *** smatzek has quit IRC | 20:32 | |
| *** esberglu has joined #openstack-powervm | 20:37 | |
| *** dwayne has joined #openstack-powervm | 20:54 | |
| *** smatzek has joined #openstack-powervm | 20:55 | |
| *** smatzek has quit IRC | 21:00 | |
| *** seroyer has quit IRC | 21:03 | |
| *** esberglu has quit IRC | 21:13 | |
| *** thorst_ has joined #openstack-powervm | 21:22 | |
| *** burgerk__ has joined #openstack-powervm | 21:24 | |
| *** thorst___ has joined #openstack-powervm | 21:25 | |
| *** thorst_ has quit IRC | 21:27 | |
| *** burgerk_ has quit IRC | 21:28 | |
| *** burgerk__ has quit IRC | 21:29 | |
| *** thorst_ has joined #openstack-powervm | 21:29 | |
| *** thorst___ has quit IRC | 21:30 | |
| *** thorst_ has quit IRC | 21:33 | |
| *** edmondsw has quit IRC | 21:37 | |
| *** AlexeyAbashkin has quit IRC | 21:37 | |
| *** miltonm has quit IRC | 21:37 | |
| *** chmod666org has quit IRC | 21:37 | |
| *** k0da has quit IRC | 21:37 | |
| *** adreznec has quit IRC | 21:37 | |
| *** toan has quit IRC | 21:37 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 21:38 | |
| *** k0da has joined #openstack-powervm | 21:40 | |
| *** adreznec has joined #openstack-powervm | 21:40 | |
| *** toan has joined #openstack-powervm | 21:40 | |
| *** AndyWojo has quit IRC | 21:41 | |
| *** edmondsw has joined #openstack-powervm | 21:41 | |
| *** thorst_ has joined #openstack-powervm | 21:41 | |
| *** miltonm has joined #openstack-powervm | 21:42 | |
| *** chmod666org has joined #openstack-powervm | 21:42 | |
| *** thorst_ has quit IRC | 21:47 | |
| *** jwcroppe has quit IRC | 21:49 | |
| *** thorst_ has joined #openstack-powervm | 21:56 | |
| *** thorst__ has joined #openstack-powervm | 22:00 | |
| *** thorst_ has quit IRC | 22:00 | |
| *** dwayne has quit IRC | 22:01 | |
| *** tjakobs has quit IRC | 22:06 | |
| thorst__ | efried: so for 4010...if we do it in the wrapper | 22:10 |
| thorst__ | and then add it later into the REST | 22:10 |
| thorst__ | would we then remove it from pypowervm | 22:10 |
| thorst__ | resulting in a different signature? | 22:10 |
| efried | The REST event would have a different shape. | 22:10 |
| thorst__ | and the consumer would need to understand that. | 22:10 |
| efried | At the very least, its 'type' would be in the standard ADD_URI/MODIFY_URI/etc. | 22:11 |
| thorst__ | right. | 22:11 |
| *** thorst__ is now known as thorst | 22:11 | |
| efried | So the consumer would have to understand that anyway. | 22:11 |
| thorst | bleh bleh bleh | 22:11 |
| *** AndyWojo has joined #openstack-powervm | 22:11 | |
| efried | But the likelihood of convincing the REST folks to include the MAC address in the event is pretty minimal | 22:11 |
| efried | So I would still want to keep the custom event for those. | 22:11 |
| thorst | but the reason you want a mac is because of the OS code. | 22:12 |
| efried | The consumer could switch to the "official" events if they wanted, but they would have to do a real GET. | 22:12 |
| thorst | honestly, what you could do if you put this in REST is extra detail. OpenStack details like UUIDs or what not. | 22:12 |
| thorst | brb | 22:12 |
| efried | thorst Well, okay, but I'm pretty comfortable with the idea of event detail containing a subset (the "interesting bits") of the object affected. | 22:12 |
| efried | It's not like I put in the neutron port UUID (not that I could anyway) | 22:14 |
| *** mdrabe has quit IRC | 22:15 | |
| *** thorst has quit IRC | 22:15 | |
| *** jwcroppe has joined #openstack-powervm | 22:16 | |
| efried | Today, the 'detail' field contains *almost* that ilk of information, for *some* events. Like you can get an LPAR mod event where the detail contains the key 'NVRAM', implying that the thing that changed about the LPAR was its NVRAM, and you should only refetch the LPAR if NVRAM is a thing you care about. Understandably, the detail field doesn't contain the whole NVRAM. But another example is PartitionState - where they | 22:16 |
| *** thorst has joined #openstack-powervm | 22:17 | |
| *** thorst has quit IRC | 22:18 | |
| *** thorst has joined #openstack-powervm | 22:20 | |
| thorst | sorry - spotty connection | 22:21 |
| *** tblakes has quit IRC | 22:23 | |
| thorst | I guess that I'm just coming from the perspective of...lets forget that the system sends events. If we can just have nova pass an event to neutron...we don't even really need the port_update in the neutron code itself. | 22:25 |
| *** apearson has joined #openstack-powervm | 22:25 | |
| efried | If the events were 100% reliable, yeah. But we still need to account for "missed events". | 22:26 |
| thorst | are events not reliable? | 22:26 |
| efried | Things like if the server restarts with events still in the queue that we haven't consumed yet; or we let too much time go by without pulling events; or the agent restarts and has to (re)register the (new) listener. | 22:27 |
| thorst | (we could even use that for sea basically - and I know we can your current approach too) | 22:27 |
| efried | Yeah, I'm rewriting the whole shebang. | 22:28 |
| thorst | server restarts with events...that's going to be massively disruptive anyway | 22:28 |
| thorst | too much time go without pulling events...could that happen? | 22:28 |
| thorst | where events are dropped? | 22:28 |
| thorst | or is that just consumer code? | 22:28 |
| *** jwcroppe has quit IRC | 22:29 | |
| efried | Yes, it can happen; I've recreated it with a local test. I register a listener in ipython, pull some events for a while, then sit there for a while. | 22:30 |
| efried | Next time I do a pull, I get NEW_CLIENT | 22:30 |
| thorst | but if we're on a tight two second loop? | 22:30 |
| efried | To be clear, the server is really good about letting you know if you need to do a full refetch. | 22:30 |
| efried | (It'll actually be a no-second loop.) I don't know what criteria the server uses to decide it's time to throw away events. | 22:31 |
| thorst | yeah, I guess I'm just really liking the idea of the nova/neutron having this message queue private to the system to pass events between each other | 22:31 |
| thorst | and not really digging embedding into the wrapper itself. And the only reason I don't is because it is one off and solely for the purpose of nova/neutron | 22:31 |
| thorst | and once its there...its there forever. | 22:31 |
| efried | It might be some number of events - in which case even in a tight loop, if the system is really busy with stuff, it's possible it overloads. | 22:31 |
| *** seroyer has joined #openstack-powervm | 22:31 | |
| thorst | you don't pull stuff out of pypowervm | 22:32 |
| efried | I don't agree it's a one-off for the community. That's just the first place we happen to be using it. | 22:32 |
| efried | And no, I would never *want* to pull it out of pypowervm. | 22:32 |
| efried | But like any other event, it only gets consumed by consumers who care about it. | 22:32 |
| *** jwcroppe has joined #openstack-powervm | 22:32 | |
| thorst | right right... | 22:32 |
| efried | Today the event looper in the agent ignores lots and lots of events. | 22:32 |
| thorst | I guess I'll +1 it, but I'd like to get a second opinion here | 22:32 |
| efried | It also happens to consume and act upon a bunch it shouldn't ;-) | 22:33 |
| efried | ...which I'm fixing regardless. | 22:33 |
| *** tjakobs has joined #openstack-powervm | 22:33 | |
| efried | Okay; who would you like to weigh in? | 22:33 |
| thorst | mdrabe and/or adreznec | 22:33 |
| thorst | this is weird code to anyone though | 22:33 |
| efried | Okay. Maybe I send an email. | 22:34 |
| thorst | I'll put my +1 and thought process in here. | 22:34 |
| efried | Sounds good. | 22:34 |
| *** jwcroppe has quit IRC | 22:39 | |
| *** jwcroppe has joined #openstack-powervm | 22:46 | |
| *** apearson_ has joined #openstack-powervm | 22:49 | |
| *** apearson has quit IRC | 22:52 | |
| *** jwcroppe has quit IRC | 22:53 | |
| *** dwayne has joined #openstack-powervm | 22:58 | |
| *** seroyer has quit IRC | 23:00 | |
| thorst | efried: I think https://review.openstack.org/#/c/374439/ may need to go back to stable/mitaka? | 23:00 |
| thorst | maybe? | 23:00 |
| openstackgerrit | Merged openstack/networking-powervm: Switch hacking.checks from neutron to neutron_lib https://review.openstack.org/374439 | 23:05 |
| openstackgerrit | Merged openstack/networking-powervm: Remove remaining references to PVID looper https://review.openstack.org/374365 | 23:06 |
| *** k0da has quit IRC | 23:18 | |
| *** thorst has quit IRC | 23:19 | |
| *** thorst has joined #openstack-powervm | 23:20 | |
| *** apearson_ has quit IRC | 23:20 | |
| *** thorst_ has joined #openstack-powervm | 23:24 | |
| *** thorst has quit IRC | 23:25 | |
| *** thorst has joined #openstack-powervm | 23:28 | |
| *** thorst_ has quit IRC | 23:29 | |
| *** thorst has quit IRC | 23:32 | |
| *** jwcroppe has joined #openstack-powervm | 23:33 | |
| *** jwcroppe_ has joined #openstack-powervm | 23:35 | |
| *** tjakobs has quit IRC | 23:36 | |
| *** jwcroppe has quit IRC | 23:38 | |
| *** thorst has joined #openstack-powervm | 23:51 | |
| *** thorst has quit IRC | 23:55 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!