| *** thorst has joined #openstack-powervm | 00:43 | |
| *** thorst has quit IRC | 00:44 | |
| *** thorst has joined #openstack-powervm | 01:33 | |
| *** thorst has quit IRC | 01:39 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 02:57 | |
| *** AlexeyAbashkin has quit IRC | 03:02 | |
| *** k0da has joined #openstack-powervm | 06:50 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 07:32 | |
| *** k0da has quit IRC | 08:39 | |
| *** k0da has joined #openstack-powervm | 08:51 | |
| *** thorst has joined #openstack-powervm | 09:56 | |
| *** thorst has quit IRC | 10:00 | |
| *** k0da has quit IRC | 10:11 | |
| *** thorst has joined #openstack-powervm | 12:04 | |
| *** esberglu has joined #openstack-powervm | 12:55 | |
| esberglu | #startmeeting powervm_driver_meeting | 13:00 |
|---|---|---|
| openstack | Meeting started Tue Oct 24 13:00:16 2017 UTC and is due to finish in 60 minutes. The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| *** openstack changes topic to " (Meeting topic: powervm_driver_meeting)" | 13:00 | |
| openstack | The meeting name has been set to 'powervm_driver_meeting' | 13:00 |
| efried | \o | 13:01 |
| mdrabe | o/ | 13:02 |
| esberglu | #topic In-Tree Driver | 13:02 |
| *** openstack changes topic to "In-Tree Driver (Meeting topic: powervm_driver_meeting)" | 13:02 | |
| esberglu | I have a couple nits to fix up for config drive | 13:03 |
| esberglu | Then returning focus to OVS | 13:03 |
| esberglu | Next step there is getting a working local.conf for IT | 13:03 |
| *** edmondsw has joined #openstack-powervm | 13:04 | |
| esberglu | Nothing else from me | 13:04 |
| esberglu | #topic Out-of-Tree Driver | 13:05 |
| *** openstack changes topic to "Out-of-Tree Driver (Meeting topic: powervm_driver_meeting)" | 13:05 | |
| esberglu | I have to rework the HostCPUStats patches after seeing efried's comments | 13:06 |
| efried | Do those comments make sense? | 13:06 |
| efried | let me know if you want to discuss later. | 13:07 |
| esberglu | efried: Yeah. I'll let you know if I have any questions | 13:07 |
| edmondsw | I've several got patches up for translations | 13:08 |
| edmondsw | efried I don't see any packaging manifests to update for pypowervm | 13:11 |
| efried | edmondsw May need to talk to minhn | 13:12 |
| edmondsw | k | 13:12 |
| efried | Cause the build is failing. | 13:12 |
| efried | for both RHEL and deb. | 13:12 |
| efried | So if the packaging manifests don't live in the pypowervm project, they'll need to be updated... wherever they do live. | 13:12 |
| edmondsw | yep | 13:13 |
| edmondsw | did we lose esberglu? | 13:15 |
| esberglu | Sorry responding to something else | 13:15 |
| esberglu | Ready to move on? | 13:16 |
| esberglu | #topic Device Passthrough | 13:16 |
| *** openstack changes topic to "Device Passthrough (Meeting topic: powervm_driver_meeting)" | 13:16 | |
| esberglu | efried: You're up | 13:16 |
| efried | Specs are froze. Everything that we need got approved. Code is proceeding apace. | 13:17 |
| efried | I wouldn't be at all offended if y'all reviewed my patches. | 13:17 |
| efried | I got started on the series for granular resource requests: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/granular-resource-requests | 13:17 |
| edmondsw | efried I would love to, but I don't see it happening any time soon with the way things are going | 13:18 |
| efried | Other than that, I've been spending the majority of my time reviewing others' patches. | 13:18 |
| edmondsw | I'm sure you've got things well in hand | 13:18 |
| efried | Getting toward a decent understanding of how everything is working. | 13:18 |
| efried | and keeping everyone honest. | 13:18 |
| edmondsw | ++ | 13:18 |
| efried | Still waiting on requirements for the pike-based hack from jwcroppe | 13:19 |
| efried | I imagine that's going to have to go through the whole UX design thing from pvc anyway | 13:19 |
| efried | which will drive how the community side needs to look. | 13:19 |
| efried | I'm almost thinking it may be more appropriate for pvc to carry this code in pvcos since we're gonna rip it all out anyway. | 13:20 |
| efried | Anyway, that's about it. | 13:21 |
| esberglu | #topic PowerVM CI | 13:22 |
| *** openstack changes topic to "PowerVM CI (Meeting topic: powervm_driver_meeting)" | 13:22 | |
| esberglu | Been in a holding pattern here mostly | 13:22 |
| esberglu | hsien enabled dev logs on one of the neos for the map lu bug | 13:23 |
| esberglu | Just need it to hit there again so he can take a look | 13:23 |
| esberglu | #topic Open Discussion | 13:25 |
| *** openstack changes topic to "Open Discussion (Meeting topic: powervm_driver_meeting)" | 13:25 | |
| efried | Got a quick one for y'all | 13:26 |
| edmondsw | shoot | 13:26 |
| efried | https://review.openstack.org/514633 | 13:26 |
| efried | I see esberglu already hit it. | 13:26 |
| esberglu | edmondsw: recheck:powervm doesn't work | 13:26 |
| efried | Noticed yesterday we don't get patchbot notifications for changes on stable branches. I want that. | 13:26 |
| esberglu | It needs to be the other order powervm:recheck | 13:27 |
| edmondsw | esberglu doh | 13:27 |
| esberglu | efried: Yep good addition | 13:27 |
| edmondsw | ++ | 13:27 |
| efried | Y'all could review this one too: https://review.openstack.org/#/c/499367/ | 13:27 |
| efried | Then I could make that a regex and wouldn't have to remember to update it every release. | 13:28 |
| efried | People were excited about that patch in IRC when I proposed it. Then... nothing. | 13:28 |
| esberglu | efried: Will do | 13:28 |
| efried | Nothing else from me. | 13:28 |
| edmondsw | ack | 13:29 |
| esberglu | Me neither | 13:29 |
| edmondsw | done | 13:29 |
| esberglu | #endmeeting | 13:29 |
| *** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack." | 13:29 | |
| openstack | Meeting ended Tue Oct 24 13:29:39 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:29 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-24-13.00.html | 13:29 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-24-13.00.txt | 13:29 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-24-13.00.log.html | 13:29 |
| *** AlexeyAbashkin has quit IRC | 13:48 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 13:50 | |
| *** tblakes has joined #openstack-powervm | 14:01 | |
| edmondsw | efried, I don't like the proposed solution to https://bugs.launchpad.net/nova-powervm/+bug/1724084 | 14:02 |
| openstack | Launchpad bug 1724084 in nova-powervm "get_vnc_console in the driver raises an InternalError exception which isn't handled by the API" [Undecided,New] - Assigned to Tyler Blakeslee (tblakes) | 14:02 |
| edmondsw | I understand you were talking to tblakes about this yesterday? | 14:02 |
| efried | edmondsw Yeah, talk to me. | 14:02 |
| efried | mdrabe heads up | 14:02 |
| edmondsw | the right place to fix this is in nova... that expected_errors check they have is busted | 14:02 |
| edmondsw | it needs to allow any HTTP 500 | 14:03 |
| efried | edmondsw You're talking about a) convincing them of that, and b) getting it backported to pike. | 14:04 |
| efried | edmondsw They're also not going to allow an arbitrary exception to be serialized across the wire. | 14:04 |
| edmondsw | efried I think (a) is extremely straightforward... it's very simple, as stated above | 14:05 |
| edmondsw | serialized across the wire? Isn't this in the API, where it's going to return an HTTP response, not serialize anything? | 14:06 |
| edmondsw | as for backporting to pike... if that doesn't go through, pvc can carry a patch | 14:06 |
| efried | edmondsw IIUC, the whole point of this bug is that we want the end user to see a useful message here. | 14:06 |
| efried | The driver raises the original exception (where we're making the change). The API carries it across the wire. | 14:07 |
| efried | And they're blocking any exception that doesn't come from nova.exceptions to obviate code injection, which seems reasonable. | 14:07 |
| edmondsw | no | 14:08 |
| edmondsw | 1) this exception does come from nova.exception | 14:08 |
| efried | Not the one we're trying to create here. | 14:08 |
| edmondsw | wrong | 14:09 |
| edmondsw | efried https://github.com/openstack/nova/blob/master/nova/exception.py#L1719 | 14:10 |
| edmondsw | but that's really beside the point anyway | 14:10 |
| edmondsw | there's no injection issue here | 14:10 |
| edmondsw | nova isn't trying to restrict what message can be returned, they're trying to restrict what HTTP error codes can be returned | 14:11 |
| edmondsw | and HTTP 500 is something that should never be restricted... any API can raise that, at any time... that's intrinsic to HTTP | 14:11 |
| edmondsw | and the message and error code are the only things that the API is going to send over the wire | 14:12 |
| *** k0da has joined #openstack-powervm | 14:14 | |
| edmondsw | efried make sense? | 14:14 |
| efried | The exception raised by the driver gets wrapped in an HTTP exception and sent over the wire. Then it gets deserialized on the other side, but only if it came from nova.exceptions. Then, if it matches one of the three or four exceptions they're "expecting", it gets raised in a way where you can see the message; otherwise it gets raised in the generic and ugly way that we're trying to fix. | 14:14 |
| efried | InternalError, which is what we have now, is subject to that last thing. | 14:14 |
| efried | ConsoleTypeUnavailable is copacetic, except that it's not really an appropriate exception for the error we're seeing. | 14:15 |
| efried | So we tried to subclass ConsoleTypeUnavailable, but got hammered by the can't-deserialize-external-exception thing. | 14:15 |
| edmondsw | efried expected_errors is running in nova-compute, not in nova-api? | 14:15 |
| efried | yes | 14:19 |
| efried | That's not where the exception is being handled pretty-or-not. | 14:19 |
| edmondsw | efried there has to be some way for a driver to raise HTTP 500 with a nicer-than-the-default error | 14:19 |
| edmondsw | that will require fixing expected_errors | 14:19 |
| efried | The driver doesn't raise 500s | 14:19 |
| edmondsw | I know... | 14:19 |
| edmondsw | let me rephrase | 14:19 |
| edmondsw | there has to be some way for a driver to indicate that the API should return HTTP 500 | 14:20 |
| edmondsw | with a nicer-than-the-default message | 14:20 |
| efried | This specific case is funneling through nova.api.openstack.compute.remote_consoles.RemoteConsolesController#get_vnc_console | 14:21 |
| efried | By the time we get there, we've gone through the API layer and deserialized the exception. | 14:22 |
| efried | That method is interpreting regular (non HTTP) exceptions and translating them to 4xx HTTP exceptions. | 14:23 |
| edmondsw | efried meaning this is in nova-api after all, not nova-compute? | 14:23 |
| efried | "this" what? | 14:26 |
| edmondsw | expected_errors running | 14:26 |
| efried | No, the expected_exceptions decorator doesn't really have any effect here as far as I can tell. | 14:26 |
| edmondsw | what? | 14:27 |
| edmondsw | it's the key here... | 14:27 |
| efried | Because it's causing this to be raised as a 500 rather than a 400? | 14:27 |
| edmondsw | it's what complains about the InternalError not being expected and raises a generic error instead | 14:27 |
| edmondsw | and stripping the message, yes | 14:28 |
| efried | tblakes yt? | 14:29 |
| tblakes | What's up? | 14:29 |
| efried | edmondsw and I have been talking about the exception thingy you've been working on. | 14:29 |
| efried | Though at this point I'm not sure exactly what edmondsw is proposing. | 14:30 |
| edmondsw | efried one sec and I'll show you what I'd propose... | 14:31 |
| efried | edmondsw You're saying we should add a generic exception to expected_exception and the nova.api.openstack.compute.remote_consoles.RemoteConsolesController#get_vnc_console handler that lets us raise a 500 with whatever message we want. | 14:31 |
| efried | Like maybe let it handle InternalError? | 14:31 |
| tblakes | That sounds like a good idea to have edmondsw show what he's proposing. I'm fine going with whatever solution you guys think is the best. | 14:32 |
| edmondsw | efried tblakes I'm saying add this to expected_error: http://paste.openstack.org/show/624488/ | 14:34 |
| efried | edmondsw tblakes So right now the bug is that we're getting this "Unexpected API Error" ? | 14:37 |
| edmondsw | efried tblakes or this might be better... to ensure someone really is intentionally trying to return a message other than the default: http://paste.openstack.org/show/624489/ | 14:37 |
| edmondsw | efried right now, the bug is that the nice message is telling folks what kind of error they hit has been stripped off and replaced with a generic message | 14:38 |
| efried | tblakes You have the setup to test this out easily, right? | 14:39 |
| tblakes | Yeah I can test that out easily enough. | 14:40 |
| edmondsw | tblakes now, taking a step back... why do we want to return a nice error message on an HTTP 500? Usually HTTP 500 means you need your admin to get involved and dig through logs, so there's no real reason to return a nicer message (and maybe reason not to) | 14:40 |
| efried | In this case, the console usually failed to open because it's already open. | 14:41 |
| efried | And someone (the admin) has to go manually close it. | 14:41 |
| efried | We shouldn't need to dig through the logs for that. | 14:41 |
| edmondsw | then maybe HTTP 400 is a more appropriate code | 14:42 |
| efried | edmondsw I'm still not convinced this is the code path we're going through in the first place. | 14:45 |
| efried | tblakes Can you try it out? | 14:45 |
| tblakes | Yeah I'll try out edmondsw changes | 14:46 |
| efried | tblakes if this makes it easier: https://review.openstack.org/#/c/514702/1/nova/api/openstack/extensions.py | 14:46 |
| edmondsw | efried it's definitely going through that code... we're seeing a message that is only found in that code | 14:46 |
| efried | edmondsw Okay, that's what I asked earlier. It would be nice if that were stated in the bug report. | 14:47 |
| edmondsw | efried yeah, the LP bug is not well written... the pvc bug has more detail | 14:47 |
| edmondsw | the LP bug seems to have been written more with the fix in mind than the problem | 14:48 |
| tblakes | After updating with edmondsw change the error message says "Unable to open console." instead of the generic API exception message. | 14:48 |
| efried | tblakes The message you're throwing from the driver? | 14:49 |
| tblakes | Yeah that's the message you added to the InternalServerError. | 14:50 |
| *** AlexeyAbashkin has quit IRC | 14:51 | |
| efried | edmondsw btw, I was getting confused between expected_exceptions and expected_errors. Compute manager's get_vnc_console method is decorated with the former, which doesn't seem to do anything. | 14:51 |
| efried | The latter must be buried somewhere in the API layer. | 14:51 |
| edmondsw | ah, ok | 14:51 |
| efried | edmondsw Okay, so what are we proposing here? | 14:52 |
| edmondsw | efried and sorry, I should have realized I was privy to information from the pvc defect you didn't have just looking at LP | 14:52 |
| edmondsw | efried I want to step back a second | 14:52 |
| efried | A 400 means "go fix something and try again". A 500 means "something unexpected is broken" | 14:52 |
| edmondsw | efried so before https://github.com/openstack/nova-powervm/commit/0b91811519ce3e9d07b29412949a6fed97837835 this returned more info... | 14:52 |
| edmondsw | that removed the "Error is: %s" for some reason | 14:52 |
| efried | Yeah, that sucks. | 14:53 |
| edmondsw | now it just says unable to open console, and not why | 14:53 |
| edmondsw | so if we really need to tell them why, we need to add that (or something) back | 14:53 |
| edmondsw | the next issue is what HTTP error code is appropriate here | 14:54 |
| edmondsw | 400? 404? 409? | 14:54 |
| edmondsw | or 500? | 14:54 |
| edmondsw | probably not 404 or 500 | 14:54 |
| efried | 400 | 14:55 |
| edmondsw | I was kinda thinking 409 | 14:55 |
| edmondsw | but maybe 400 | 14:55 |
| efried | 409 is more for an HTTP resource conflict, which this ain't. | 14:55 |
| efried | And we don't even know for sure that it's for a console conflict, necessarily. | 14:55 |
| efried | So 400. | 14:55 |
| efried | But there's the rub | 14:55 |
| edmondsw | truth is, there isn't really a good HTTP code for this kind of thing (or a lot of rest errors) | 14:55 |
| efried | Sure it is | 14:56 |
| efried | 400 means "Something broke that you can fix. Fix it and try again." | 14:56 |
| edmondsw | indicates that the server cannot or will not process the request due to something that is perceived to be a client error | 14:57 |
| efried | 500 means "Something broke on the server side that shouldn't have broken. It's either a bug or some kind of failure beyond your control or ours." | 14:57 |
| edmondsw | not exactly... 400 "indicates that the server cannot or will not process the request due to something that is perceived to be a client error". Would you call this a client error? I don't think I would | 14:58 |
| tblakes | I've got an appointment at 10:15 that I need to head to now, but I should be back by 11. | 14:58 |
| efried | They didn't close the console. | 14:58 |
| efried | or whatever. | 14:58 |
| edmondsw | someone didn't... not necessarily this client, right? | 14:58 |
| edmondsw | but whatever... I don't love 409 either... 400 is fine | 14:59 |
| efried | Same thing if we tried to create an LPAR with a UUID that already exists | 14:59 |
| efried | or attach a disk that's already attached somewhere else. | 14:59 |
| *** AlexeyAbashkin has joined #openstack-powervm | 14:59 | |
| efried | Doesn't matter if it was *this* client. By "client" it means "not the server". | 14:59 |
| efried | Okay, so 400, but now we gotta convince nova that InternalError (or whatever we decide we want to push from our driver) should correspond to a 400. | 15:00 |
| edmondsw | well, not InternalError | 15:00 |
| efried | Right, cause that sounds like 500. | 15:00 |
| edmondsw | yep... but not ConsoleTypeUnavailable either | 15:00 |
| efried | Really should be some kind of general ExceptionWeWantTheUserToSee | 15:00 |
| efried | It would be in the same philosophical category as BuildAbortException. | 15:01 |
| efried | In the sense that it gets treated specially. | 15:01 |
| edmondsw | is this type of error specific to our driver? Nobody else is going to have this kind of issue where they can't open a console because one is already open? | 15:02 |
| efried | Not sure that's relevant at the moment. | 15:02 |
| efried | We can make our specific snowflake exception a subclass of whatever this hypothetical passthrough exception is. | 15:02 |
| edmondsw | the reason I ask is because if other drivers have a similar issue, we can create a new nova.exception.ConsoleUnavailable | 15:02 |
| efried | And pass that into expected_errors (and not modify expected_errors)? | 15:03 |
| efried | Thereby solving the specific issue but not the general one? | 15:03 |
| edmondsw | and make ConsoleTypeUnavailable subclass that, then use ConsoleUnavailable instead of ConsoleTypeUnavailable in nova.api.openstack.compute.remote_consoles.RemoteConsolesController#get_vnc_console | 15:04 |
| edmondsw | and then we don't have to change expected_errors at all | 15:04 |
| efried | Right, so that's effectively the current solution. | 15:04 |
| efried | Except without involving nova. | 15:04 |
| efried | tblakes and I did discuss doing something like ^ | 15:04 |
| efried | But didn't think it worth the hassle of convincing nova it was necessary. | 15:05 |
| efried | They're pretty focused on blueprint work for queens. | 15:05 |
| edmondsw | k | 15:05 |
| efried | But if we want to throw it at the wall and see if it sticks... | 15:05 |
| edmondsw | yeah | 15:05 |
| efried | Somebody's going to have to word that bug in a convincing way. | 15:06 |
| edmondsw | let's do that, and in the meantime we can push through tblakes change... though it still needs to add something to augment the message since we lost the necessary detail with https://github.com/openstack/nova-powervm/commit/0b91811519ce3e9d07b29412949a6fed97837835 | 15:06 |
| efried | edmondsw His change has that in it. | 15:07 |
| edmondsw | oh, yeah, it does... cool | 15:08 |
| efried | So tblakes just needs to address mdrabe's -1 | 15:08 |
| *** AlexeyAbashkin has quit IRC | 15:10 | |
| edmondsw | efried did you and tblakes consider raising a webob exception? | 15:10 |
| efried | From the driver? No. | 15:10 |
| edmondsw | yeah, probably don't want that going through serialization | 15:10 |
| efried | Is there precedent for that? I would be surprised. | 15:10 |
| edmondsw | no idea | 15:10 |
| edmondsw | ok, I updated the review | 15:11 |
| *** tjakobs has joined #openstack-powervm | 15:30 | |
| *** k0da has quit IRC | 15:53 | |
| *** k0da has joined #openstack-powervm | 16:06 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 16:22 | |
| openstackgerrit | Tyler Blakeslee proposed openstack/nova-powervm master: Raise catachable error when VNC terminal fails to open. https://review.openstack.org/513833 | 16:24 |
| *** AlexeyAbashkin has quit IRC | 16:26 | |
| *** tblakes has quit IRC | 16:31 | |
| edmondsw | esberglu are we hitting more timeouts in the CI than usual? | 16:46 |
| edmondsw | seems like it | 16:46 |
| *** AlexeyAbashkin has joined #openstack-powervm | 16:55 | |
| *** AlexeyAbashkin has quit IRC | 16:59 | |
| openstackgerrit | Merged openstack/nova-powervm master: Raise catachable error when VNC terminal fails to open. https://review.openstack.org/513833 | 17:07 |
| esberglu | edmondsw: Seems to happen when a lot of runs are occurring. I was planning on setting some time aside next week to dig into those again | 17:26 |
| *** k0da has quit IRC | 18:41 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 18:55 | |
| *** k0da has joined #openstack-powervm | 18:58 | |
| *** AlexeyAbashkin has quit IRC | 19:00 | |
| edmondsw | esberglu can you take a look at https://review.openstack.org/514437 and https://review.openstack.org/514439? | 19:19 |
| edmondsw | and 6068 | 19:19 |
| esberglu | edmondsw: Sure | 19:20 |
| edmondsw | ty sir | 19:20 |
| edmondsw | efried when you have a minute... 6068 | 19:20 |
| esberglu | edmondsw: +2'ed all the removals | 19:22 |
| esberglu | How do all of the .po files get generated? | 19:23 |
| edmondsw | tx | 19:23 |
| efried | edmondsw Is that just a rebase? | 19:24 |
| efried | No edits, it appears? | 19:24 |
| edmondsw | esberglu there's a command for that (don't recall exactly what offhand), and then we send them off for translation and then I checked in what we got back | 19:24 |
| edmondsw | efried right, I removed the *-log-* files and that's about it | 19:24 |
| efried | coo | 19:25 |
| edmondsw | efried esberglu can one of you +W https://review.openstack.org/#/c/514439/ and https://review.openstack.org/#/c/514437/ ? | 21:04 |
| edmondsw | would rather not do that on myself even thought you both +2ed | 21:04 |
| esberglu | edmondsw: Done. Is the ceil one stuck on CI | 21:05 |
| edmondsw | esberglu tx, and yes | 21:05 |
| edmondsw | esberglu been over 4 hours since I rechecked and no result yet | 21:05 |
| *** thorst has quit IRC | 21:06 | |
| esberglu | edmondsw: Looking. Haven't checked up on CI status this afternoon | 21:06 |
| edmondsw | esberglu you just added another recheck? shouldn't we have waited for the results of my earlier recheck? | 21:06 |
| esberglu | edmondsw: Didn't realize that yours didn't go through yet | 21:07 |
| *** thorst has joined #openstack-powervm | 21:07 | |
| esberglu | edmondsw: Hmm weird looks like the nodepool nodes are getting removed from jenkins but not deleted from nodepool after the CI runs are completing. | 21:09 |
| edmondsw | esberglu glad you checked :) | 21:10 |
| *** thorst has quit IRC | 21:12 | |
| openstackgerrit | Merged openstack/nova-powervm master: Persist existing LPAR wrapper attributes in DefaultStandardize on resize https://review.openstack.org/511343 | 21:13 |
| openstackgerrit | Merged openstack/networking-powervm master: remove log translation files https://review.openstack.org/514439 | 21:15 |
| esberglu | edmondsw: Relocating quick, will look into right after. Looks like it's a rabbitmq issue | 21:17 |
| edmondsw | esberglu ack | 21:18 |
| *** esberglu has quit IRC | 21:18 | |
| *** esberglu has joined #openstack-powervm | 21:19 | |
| openstackgerrit | Merged openstack/nova-powervm master: remove log translation files https://review.openstack.org/514437 | 21:21 |
| *** esberglu has quit IRC | 21:24 | |
| openstackgerrit | Matthew Edmonds proposed openstack/networking-powervm master: update translations https://review.openstack.org/514403 | 21:29 |
| *** thorst has joined #openstack-powervm | 21:32 | |
| *** thorst has quit IRC | 21:36 | |
| *** thorst has joined #openstack-powervm | 21:38 | |
| *** esberglu has joined #openstack-powervm | 21:39 | |
| *** thorst has quit IRC | 21:43 | |
| *** k0da has quit IRC | 21:51 | |
| *** AlexeyAbashkin has joined #openstack-powervm | 21:56 | |
| *** AlexeyAbashkin has quit IRC | 22:01 | |
| openstackgerrit | Matthew Edmonds proposed openstack/nova-powervm master: update translations https://review.openstack.org/514399 | 22:21 |
| *** edmondsw has quit IRC | 22:29 | |
| *** edmondsw has joined #openstack-powervm | 22:29 | |
| *** edmondsw has quit IRC | 22:34 | |
| *** tjakobs has quit IRC | 22:36 | |
| *** thorst has joined #openstack-powervm | 22:43 | |
| *** thorst has quit IRC | 22:49 | |
| *** esberglu has quit IRC | 23:25 | |
| *** edmondsw has joined #openstack-powervm | 23:55 | |
| *** edmondsw has quit IRC | 23:59 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!