*** edmondsw has quit IRC | 00:22 | |
*** thorst has joined #openstack-powervm | 00:26 | |
*** edmondsw has joined #openstack-powervm | 00:46 | |
*** edmondsw has quit IRC | 00:50 | |
*** chhavi has joined #openstack-powervm | 01:15 | |
*** thorst has quit IRC | 01:27 | |
*** chhavi has quit IRC | 02:03 | |
-openstackstatus- NOTICE: Gerrit is being restarted to feed its insatiable memory appetite | 02:41 | |
*** thorst has joined #openstack-powervm | 03:28 | |
*** thorst has quit IRC | 03:33 | |
*** chhavi has joined #openstack-powervm | 03:37 | |
*** thorst has joined #openstack-powervm | 04:29 | |
*** thorst has quit IRC | 04:34 | |
*** thorst has joined #openstack-powervm | 05:30 | |
*** thorst has quit IRC | 05:34 | |
*** chhavi has quit IRC | 06:05 | |
*** mdrabe has quit IRC | 06:05 | |
*** chhavi has joined #openstack-powervm | 06:05 | |
*** mdrabe has joined #openstack-powervm | 06:10 | |
*** thorst has joined #openstack-powervm | 06:31 | |
*** thorst has quit IRC | 06:35 | |
-openstackstatus- NOTICE: Post jobs are not executed currently, do not tag any releases | 07:23 | |
*** ChanServ changes topic to "Post jobs are not executed currently, do not tag any releases" | 07:23 | |
*** thorst has joined #openstack-powervm | 07:32 | |
*** thorst has quit IRC | 07:36 | |
*** thorst has joined #openstack-powervm | 08:33 | |
*** thorst has quit IRC | 08:37 | |
*** thorst has joined #openstack-powervm | 09:33 | |
*** thorst has quit IRC | 09:38 | |
*** thorst has joined #openstack-powervm | 10:18 | |
*** thorst has quit IRC | 10:19 | |
*** thorst has joined #openstack-powervm | 11:19 | |
*** thorst has quit IRC | 11:26 | |
*** kylek3h_ has joined #openstack-powervm | 12:00 | |
*** kylek3h has quit IRC | 12:03 | |
*** kylek3h_ has quit IRC | 12:04 | |
*** thorst has joined #openstack-powervm | 12:04 | |
*** edmondsw has joined #openstack-powervm | 12:09 | |
*** kylek3h has joined #openstack-powervm | 12:25 | |
*** esberglu has joined #openstack-powervm | 12:52 | |
esberglu | #startmeeting powervm_driver_meeting | 13:00 |
---|---|---|
openstack | Meeting started Tue Sep 19 13:00:48 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 | The meeting name has been set to 'powervm_driver_meeting' | 13:00 |
edmondsw | o/ | 13:01 |
efried | o/ | 13:01 |
mdrabe | o/ | 13:01 |
esberglu | #topic In-Tree Driver | 13:01 |
edmondsw | tx to esberglu for getting the queens spec up | 13:02 |
efried | ++ | 13:02 |
esberglu | I was planning on starting either the OVS or SEA IT patch this week | 13:02 |
esberglu | np | 13:02 |
edmondsw | we talked over the basic gist of the plan the spec lays out at the PTG, and the only response (from mriedem) was "that seems fine" | 13:03 |
edmondsw | esberglu sounds good | 13:03 |
esberglu | Not sure which yet, I think OVS has a patch started but CI isn't set up for it. SEA is set up for CI but no work has gone into so far afaik | 13:04 |
esberglu | edmondsw: Cool | 13:04 |
edmondsw | mriedem did ask about whether the CI would use OVS or SEA, and efried said SEA | 13:05 |
edmondsw | makes sense since that's what we do OOT | 13:05 |
efried | It would be neat to figure out OVS for the CI, but they're not going to require it. | 13:05 |
edmondsw | yeah, if we could somehow test both that would be awesome | 13:06 |
efried | Because they recognize it would mean we would need essentially two separate CIs | 13:06 |
efried | and they don't force others to do that. | 13:06 |
esberglu | Okay so SEA first then | 13:06 |
esberglu | And then OVS IT with whatever CI changes are needed if practical | 13:06 |
efried | But yeah, it would be pretty cool if, like, we could have the CI alternate or something. | 13:06 |
edmondsw | config drive patch still needs reviews from our team | 13:08 |
esberglu | efried: Eh I think that would be weird. Like if you do a recheck and suddenly its using different networking | 13:08 |
edmondsw | esberglu yeah, it's definitely not optimal... but neither is never testing one of them | 13:09 |
efried | esberglu I don't disagree it would be weird. | 13:09 |
efried | Yeah, what edmondsw said. | 13:09 |
edmondsw | at least we would see intermittent errors if we were alternating | 13:09 |
efried | Like, maybe we test even-numbered change sets with one, odd-numbered with the other. | 13:09 |
edmondsw | not saying we have to do that, just something to think about | 13:09 |
efried | Then at least rechecks would be consistent. | 13:09 |
efried | But need a way to force one or the other, so we can specifically target changes that affect the networking code, or whatever... | 13:10 |
esberglu | edmondsw: efried: We can have this discussion further once we get to OVS. But yeah I agree we should try to get both of them being tested somehow | 13:10 |
esberglu | I'll keep it in the back of my mind | 13:10 |
efried | I think the major blocker there was us running local commands, right? Which we're no longer doing. | 13:10 |
edmondsw | another thing we need to think about IT is the docs.. we never finished our TODOs there | 13:12 |
esberglu | I don't think that was the only blocker. I have some notes somewhere that I need to dig up | 13:12 |
edmondsw | we added ourselves to the support matrix, but didn't add a hypervisors page for powervm to the config ref | 13:12 |
edmondsw | probably a bigger deal for queens than for pike, since the pike IT driver isn't all that usable without networking, but still... | 13:13 |
esberglu | Yeah I think they had a freeze on adding docs there when we tried to do that during pike | 13:13 |
edmondsw | if we could get the framework up for those docs, then we could be adding to it in the patches we are submitting for queens instead of after the fact | 13:14 |
esberglu | They were moving around the location of certain docs and didn't want new ones at that point | 13:14 |
esberglu | I can look into it | 13:14 |
edmondsw | yep, understood | 13:15 |
edmondsw | I think the location is locked down now | 13:15 |
edmondsw | I think that's all for IT? | 13:15 |
esberglu | #action esberglu: Finish docs updates | 13:15 |
esberglu | Yep | 13:15 |
esberglu | #topic Out-of-Tree Driver | 13:15 |
esberglu | Anyone have discussion items here? | 13:16 |
edmondsw | we had to spin pypowervm 1.1.8 to fix a max slots bug. The u-c update for that has merged now after some initial gate issues | 13:17 |
efried | Curse LPAR builder. | 13:18 |
edmondsw | tjakobs has a patch up for iSCSI that I need to look at | 13:18 |
edmondsw | if any others have time to check that out... | 13:18 |
edmondsw | we're pulling the never-really-supported Linux Bridge code | 13:19 |
efried | Did we decide to pull the trigger on that? | 13:20 |
edmondsw | tjakobs also has a patch up for ceph volumes to review | 13:20 |
edmondsw | efried yeah, I think so... I checked with thorst and he said pull it | 13:20 |
efried | k, well, that change is ready for review then. | 13:20 |
efried | privsep stuff <waves hands> | 13:21 |
edmondsw | mdrabe there's a merge conflict on https://review.openstack.org/#/c/497977/ | 13:21 |
mdrabe | yep | 13:21 |
esberglu | efried: Yeah they renamed dac_admin so I just need to keep an eye for that merge | 13:22 |
efried | Perhaps we should consider implementing support for Depends-On in our OOT CI. | 13:23 |
esberglu | efried: Yep it's on the TODO list | 13:23 |
efried | okay. | 13:23 |
edmondsw | ++ | 13:24 |
esberglu | Ready to move on? | 13:24 |
edmondsw | yep, on to PCI | 13:24 |
esberglu | #topic Device Passthrough | 13:25 |
efried | We got buy-in at the PTG that the way Nova will handle device passthrough should be done in ways that won't paint non-libvirt into a corner. | 13:26 |
edmondsw | ++++++++++ | 13:27 |
efried | I feel like we need three major pieces of framework before we can work a full solution: | 13:27 |
efried | 1) Nested resource providers (in placement). This got prioritized for early Queens. | 13:27 |
efried | 2) Ability to request allocations with a richer syntax, to support a) multiple allocations of the *same* resource class from *different* resource providers (e.g. VFs on different physnets); and b) ensuring multiple resources can be grabbed from the *same* resource provider (e.g. claim the VF inventory and the bandwidth inventory from the same PF). This is committed for Queens (jaypipes to write spec; I started some cont | 13:29 |
efried | ent) | 13:29 |
efried | 3) Affinity/anti-affinity via placement aggregates. This is *not* committed for Queens. | 13:29 |
efried | Once all of those things are done, Nova will consider starting on whatever framework is necessary for generic device management, with an eye towards getting rid of the existing PCI management code entirely. | 13:30 |
efried | But once all of those things are done, we may be able to get a jump start on converting over from... | 13:31 |
efried | The Hack | 13:31 |
efried | So for the Q cycle, we're going to move forward with https://review.openstack.org/494733 and https://review.openstack.org/496434 | 13:31 |
edmondsw | did they talk about how to get rid of hte existing PCI management code without breaking operators who are still using it? backward compat type stuff | 13:32 |
efried | defer, defer, defer | 13:32 |
efried | fingers in ears | 13:32 |
efried | lalalala, not going to think about it yet. | 13:32 |
edmondsw | lol | 13:32 |
efried | But it'll be a deprecation cycle. | 13:32 |
efried | I anticipate individual hypervisors being able to take the lead for themselves. | 13:33 |
efried | to some extent | 13:34 |
edmondsw | FYI all, mdrabe is going to be helping efried on this as able, and driving the corresponding work in PowerVC | 13:34 |
efried | because the ways of specifying resources (in general, not just devices) is going to have to cut over at some point. | 13:34 |
edmondsw | efried do we need a recheck on https://review.openstack.org/#/c/496434/ or are you going to upload a new ps? | 13:36 |
efried | Oh, yeah, it needs UT and stuff. It's not close to done. That and the spec are going to be my main gig for the next couple of weeks. | 13:37 |
efried | Also need to talk to consumer architects (Joe?) to be sure we understand the requirements. | 13:37 |
edmondsw | yeah, I need to set that up | 13:38 |
efried | e.g. do we need to do more hackage to overcome the limitation on grouping by vendor/product ID? | 13:38 |
edmondsw | #action edmondsw: schedule PCI attach mtg with stakeholders | 13:38 |
edmondsw | efried anything else here? | 13:39 |
efried | I don't think so. | 13:39 |
efried | actually | 13:40 |
efried | lemme just drop a couple more links here for reference... | 13:40 |
efried | https://etherpad.openstack.org/p/nova-ptg-queens-generic-device-management | 13:40 |
efried | https://etherpad.openstack.org/p/nova-multi-alloc-request-syntax-brainstorm <== this is for #2 mentioned above | 13:40 |
efried | that is all | 13:41 |
edmondsw | #topic PowerVM CI | 13:41 |
esberglu | Slowly knocking out tempest failures and CI todo backlog items | 13:42 |
esberglu | We still need to get console tests working for CI which was having problems due to remote | 13:43 |
esberglu | Haven't looked into that for a while because other things have been breaking | 13:43 |
edmondsw | did you and thorst ever come up with a plan for that? | 13:43 |
esberglu | We talked about it a little bit a couple times | 13:43 |
esberglu | But not a solid plan | 13:43 |
edmondsw | it's not my top priority | 13:44 |
edmondsw | I would work on OVS/SEA IT first, adding Depends-On support, obviously any CI breakages... | 13:44 |
esberglu | edmondsw: Yeah it keeps getting bumped by higher priority stuff. IIRC there are only 2 tempest tests for it | 13:45 |
edmondsw | but good to not forget it | 13:45 |
esberglu | I also am still working on that openstack dashboard. I got the web UI up on a test system but it wasn't populating properly | 13:45 |
edmondsw | what dashboard? | 13:46 |
efried | Yeah, what dashboard? | 13:46 |
esberglu | Openstack health dashboard | 13:47 |
esberglu | Its the tempest failure stats UI that the community uses | 13:47 |
esberglu | http://status.openstack.org/openstack-health/#/ | 13:47 |
edmondsw | ok, I think we did talk about that | 13:48 |
esberglu | That's all I had for CI | 13:49 |
efried | *-powervm are on there | 13:49 |
efried | what do we need beyond that? | 13:49 |
esberglu | That's not results for PowerVM CI | 13:50 |
esberglu | That's results on *-powervm for the community CI | 13:50 |
efried | okay. | 13:50 |
edmondsw | oh, interesting... | 13:51 |
edmondsw | so if we get our CI added, how would that look? Munged together with what is already there for *-powervm? | 13:51 |
efried | or a separate dashboard that just shows our runs? | 13:51 |
esberglu | It would be a separate dashboard that just shows our runs | 13:52 |
esberglu | That dashboard only show the tests that you see under the "Jenkins check" header on reviews. It doesn't have any 3rd party | 13:53 |
edmondsw | looks like you can click one of these, e.g. nova-powervm, and get a new page with more details about what jobs ran there | 13:53 |
edmondsw | esberglu oh, so you'd be setting up something totally separate? | 13:53 |
edmondsw | does any other 3rd party CI do that? | 13:54 |
esberglu | edmondsw: Yeah but that still is only showing the jenkins jobs (py27, py35) | 13:54 |
esberglu | It would be something totally separate | 13:54 |
esberglu | PowerKVM has one, I talked to them a little bit about what they had to do | 13:54 |
edmondsw | k | 13:55 |
edmondsw | sounds cool, but not critical | 13:55 |
efried | agree | 13:55 |
esberglu | edmondsw: efried: The idea of it is that we can get rid of failure emails | 13:55 |
esberglu | And just monitor the dashboard | 13:55 |
edmondsw | sure | 13:55 |
edmondsw | esberglu want to talk about zuulv3 | 13:56 |
efried | We would still get emails for changes we're subscribed to, right? | 13:56 |
esberglu | efried: Yeah that's all external to us | 13:56 |
efried | Cause the likelihood of me actively and continuously "monitoring" the dashboard is nil. | 13:56 |
efried | But I still need to know if a change I care about fails. | 13:56 |
esberglu | efried: Yeah you would still get that I believe | 13:57 |
esberglu | But I would make sure before getting rid of the failures | 13:57 |
esberglu | edmondsw: Did you hear much about it at PTG? | 13:57 |
esberglu | I didn't see a whole lot on the mailing list | 13:57 |
edmondsw | esberglu not much, just that they were trying to switch over, hit an issue early in the week, and were going to come back to is | 13:57 |
edmondsw | it* | 13:58 |
edmondsw | later in the week | 13:58 |
esberglu | edmondsw: Yeah that was my understanding too | 13:58 |
edmondsw | I should probably say "keep working on it" rather than "come back to it" | 13:58 |
esberglu | We aren't necessarily in a hurry to do that | 13:58 |
esberglu | It would just be nice | 13:58 |
edmondsw | and my understanding is that their switch doesn't really effect us, just would be nice if/when we can follow suit | 13:58 |
edmondsw | let them work out the kinks first, though | 13:58 |
esberglu | edmondsw: Yeah I'll just try to stay in the loop on it | 13:59 |
edmondsw | ++ | 13:59 |
edmondsw | the other thing I was going to ask about is neutron/ceilometer ci | 13:59 |
esberglu | edmondsw: You saw my latest email on that? | 13:59 |
edmondsw | yeah, your email said that we caught that ceilometer issue in tox rather than in CI... which surprised me | 14:00 |
esberglu | We would need to talk to both neutron and ceilometer separately if we want to publish | 14:00 |
edmondsw | esberglu yeah, and I think that would probably be a good discussion to have... let's add that to the TODO list | 14:00 |
edmondsw | non-voting, of course | 14:01 |
esberglu | Yep | 14:01 |
esberglu | edmondsw: I also will add a todo to look into what we are testing for ceilometer | 14:01 |
edmondsw | tx | 14:01 |
edmondsw | done with CI? | 14:01 |
esberglu | Yep | 14:01 |
edmondsw | #topic Driver Testing | 14:02 |
edmondsw | I just have one quick thing here | 14:02 |
edmondsw | basically, we're just going to have UT and CI at this point | 14:02 |
edmondsw | I thought we might be able to get Ravi to do some tempest work, but we lost him as well as Jay | 14:03 |
edmondsw | so I will remove this from the agenda going forward | 14:03 |
edmondsw | :( | 14:03 |
edmondsw | of course OOT driver is still used/tested by PowerVC | 14:03 |
edmondsw | and I'll be asking for more resources to help here in the next cycle | 14:04 |
esberglu | okay | 14:04 |
edmondsw | but that will probably be dev resources, not test... so get ready to be asked to do more in tempest dev and usage | 14:04 |
edmondsw | that is all | 14:04 |
edmondsw | #topic Open Discussion | 14:05 |
efried | edmondsw Following up from PTG, can you please review this series: https://review.openstack.org/#/q/topic:bp/nova-validate-certificates+status:open | 14:05 |
esberglu | Any last thoughts? Nothing else from me | 14:05 |
edmondsw | efried yep, on my list | 14:05 |
efried | Thanks. | 14:05 |
esberglu | #endmeeting | 14:06 |
openstack | Meeting ended Tue Sep 19 14:06:44 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:06 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-09-19-13.00.html | 14:06 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-09-19-13.00.txt | 14:06 |
openstack | Log: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-09-19-13.00.log.html | 14:06 |
*** esberglu has quit IRC | 14:06 | |
*** esberglu has joined #openstack-powervm | 14:07 | |
*** esberglu has quit IRC | 14:11 | |
*** esberglu has joined #openstack-powervm | 14:20 | |
*** esberglu has quit IRC | 14:39 | |
*** esberglu has joined #openstack-powervm | 14:40 | |
*** esberglu has quit IRC | 14:41 | |
*** esberglu has joined #openstack-powervm | 14:41 | |
esberglu | efried: edmondsw: I think I'm actually gonna go OVS first. That patch is a lot farther along than I remembered it being | 15:37 |
efried | esberglu "first" before what? | 15:37 |
esberglu | SEA | 15:37 |
efried | esberglu That's fine by me, except that it brings forward the need to have OVS in the CI. | 15:47 |
efried | I'm not aware of what all the challenges are there. | 15:48 |
openstackgerrit | Matt Rabe proposed openstack/nova-powervm master: Add PPT ratio value to supported flavor fields https://review.openstack.org/497977 | 15:48 |
efried | thorst Care to comment on whether SEA or OVS would be more "strategic" to have in tree first? | 15:48 |
mdrabe | ^^ edmondsw efried | 15:49 |
efried | mdrabe +2. Will +W when CI passes. | 15:49 |
esberglu | efried: If we do SEA first I will be redoing a lot of work that has already been done in the OVS patch | 15:50 |
efried | BTW, since the gerrit upgrade, it seems folks aren't getting emails anymore. I know I'm not, and several folks have complained to the ML. So until fixed, be vigilant about checking your dashboard manually. | 15:50 |
esberglu | Any code that is shared by both SEA and OVS is already in the OVS patch | 15:50 |
efried | esberglu Oh, the common code paths? | 15:50 |
edmondsw | efried I believe in past conversations we've not really cared whether SEA or OVS merged first | 15:50 |
efried | right. | 15:51 |
efried | Sfine by me. If there's no push from thorst or edmondsw to do one or the other first, I guess it's up to you whether it's more work to shift the common code to a SEA change set versus figuring out OVS in the CI. | 15:51 |
efried | The latter has to be done eventually anyway, whereas the former would be throwaway work. | 15:52 |
efried | So yeah. OVS. | 15:52 |
efried | Glad we talked that through. | 15:52 |
edmondsw | well, we may or may not ever do OVS in the CI, right? | 15:52 |
edmondsw | we'd like to look at that... but it's not a requirement to do OVS | 15:52 |
efried | Yeah, fair | 15:53 |
efried | We don't test localdisk driver in the CI either. | 15:53 |
efried | or NPIV | 15:53 |
edmondsw | right | 15:54 |
edmondsw | so esberglu I'm fine with you focusing on OVS first, and pretty confident thorst would say the same | 15:55 |
esberglu | edmondsw: efried: Cool | 16:07 |
efried | btw, I can't resist: | 16:21 |
efried | Getting networking in tree will truly represent a sea change for powervm. | 16:21 |
efried | Regardless of whether it's a SEA change. | 16:21 |
thorst | sea *of* change? | 16:22 |
efried | https://en.wikipedia.org/wiki/Sea_change_(idiom) | 16:22 |
efried | (NOW he responds) | 16:22 |
thorst | heh, I haven't read all back and about to jump to yet another call | 16:29 |
thorst | :-( | 16:29 |
*** chhavi has quit IRC | 17:58 | |
openstackgerrit | Eric Berglund proposed openstack/nova-powervm master: WIP: Add context to detach_interface params https://review.openstack.org/505374 | 19:06 |
esberglu | efried: edmondsw: I noticed this error in n-cpu logs recently. | 19:27 |
esberglu | http://paste.openstack.org/show/621471/ | 19:27 |
esberglu | It's getting called from https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L6913 | 19:27 |
esberglu | And is hitting our code here | 19:27 |
esberglu | https://github.com/openstack/nova-powervm/blob/master/nova_powervm/virt/powervm/driver.py#L979 | 19:27 |
esberglu | Digging deeper I'm seeing the error on passing runs too | 19:28 |
esberglu | But I'm curious if this is what is underlying the network related tempest failures | 19:28 |
esberglu | But the change adding context to the detach_interface was put in forever ago | 19:29 |
esberglu | https://github.com/openstack/nova/commit/383e795a | 19:29 |
esberglu | So I think we have a hole in our UT as well | 19:30 |
edmondsw | wow, that is a long time... how could we have missed that? | 19:30 |
esberglu | edmondsw: I hadn't noticed it in any CI logs until recently | 19:30 |
esberglu | But it should have been throwing errors since it went in | 19:31 |
efried | esberglu You gonna propose the fix? | 19:33 |
esberglu | efried: Yeah | 19:33 |
efried | coo | 19:33 |
-openstackstatus- NOTICE: Zuul and Gerrit are being restarted to address issues discovered with the Gerrit 2.13 upgrade. review.openstack.org will be inaccessible for a few minutes while we make these changes. Currently running jobs will be restarted for you once Zuul and Gerrit are running again. | 20:27 | |
*** esberglu has quit IRC | 21:00 | |
*** esberglu has joined #openstack-powervm | 21:01 | |
*** esberglu has quit IRC | 21:05 | |
*** esberglu has joined #openstack-powervm | 21:12 | |
*** thorst has quit IRC | 21:14 | |
*** thorst has joined #openstack-powervm | 21:16 | |
*** thorst has quit IRC | 21:20 | |
openstackgerrit | Eric Berglund proposed openstack/nova-powervm master: Add context to detach_interface params https://review.openstack.org/505374 | 21:38 |
openstackgerrit | Merged openstack/nova-powervm master: Add PPT ratio value to supported flavor fields https://review.openstack.org/497977 | 21:39 |
openstackgerrit | Eric Berglund proposed openstack/nova-powervm master: Add context to detach_interface params https://review.openstack.org/505374 | 21:42 |
*** kylek3h has quit IRC | 21:54 | |
*** esberglu has quit IRC | 21:57 | |
-openstackstatus- NOTICE: Gerrit is being restarted to address some final issues, review.openstack.org will be inaccessible for a few minutes while we restart | 22:33 | |
*** openstackgerrit has quit IRC | 22:47 | |
*** edmondsw has quit IRC | 22:50 | |
*** edmondsw has joined #openstack-powervm | 22:55 | |
*** edmondsw has quit IRC | 22:59 | |
*** edmondsw has joined #openstack-powervm | 23:23 | |
*** edmondsw has quit IRC | 23:27 | |
*** ChanServ changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack." | 23:40 | |
-openstackstatus- NOTICE: Gerrit is once again part of normal puppet config management. Problems with Gerrit gitweb links and Zuul post jobs have been addressed. We currently cannot create new gerrit projects (fixes in progress) and email sending is slow (being debugged). | 23:40 | |
*** chhavi has joined #openstack-powervm | 23:54 | |
*** chhavi has quit IRC | 23:58 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!