Tuesday, 2018-05-01

openstackgerritXiaojueGuan proposed openstack/nova-powervm master: Trivial: Update pypi url to new url  https://review.openstack.org/56539303:37
openstackgerritXiaojueGuan proposed openstack/ceilometer-powervm master: Trivial: Update pypi url to new url  https://review.openstack.org/56543806:17
*** edmondsw has joined #openstack-powervm12:19
*** esberglu has joined #openstack-powervm13:16
*** openstackgerrit has quit IRC13:34
*** tjakobs has joined #openstack-powervm13:57
*** mujahidali has joined #openstack-powervm13:58
edmondsw#startmeeting PowerVM Driver Meeting14:00
openstackMeeting started Tue May  1 14:00:06 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:00
openstackThe meeting name has been set to 'powervm_driver_meeting'14:00
edmondswefried esberglu mujahidali ^14:00
*** openstackgerrit has joined #openstack-powervm14:00
openstackgerritMerged openstack/ceilometer-powervm master: Trivial: Update pypi url to new url  https://review.openstack.org/56543814:00
edmondsw#link https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:00
efriedmujahidali: Greetings, nice to meetcha.14:00
edmondsw#topic In-Tree Driver14:00
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:00
edmondsw#link https://etherpad.openstack.org/p/powervm-in-tree-todos14:00
edmondswesberglu walk us through the latest?14:01
mujahidaliefried: thanks :)14:01
esbergluWe need scenario testing to move forward on snapshot and localdisk. I'll go into more detail during CI section14:01
esbergluvSCSI is blocked until we have some sort of volume testing14:02
esbergluAnd cold mig/resize is waiting on multinode CI14:02
esbergluThat's pretty much it14:02
edmondswesberglu I dropped some comments on localdisk14:02
edmondswof course CI is the priority atm14:02
edmondswlooks like z got back into a runway quickly after they resolved their CI issues... hopefully things go as well for us14:03
edmondsw#topic Out-of-Tree Driver14:04
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:04
edmondsw#link https://etherpad.openstack.org/p/powervm-oot-todos14:04
edmondswI don't know of any progress made on OOT since the last meeting14:05
edmondswI think everyone's been focused elsewhere14:06
edmondswso, moving along...14:06
edmondsw#topic Device Passthrough14:06
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:06
edmondswefried anything new here?14:06
efriedLooks like tetsuro is taking over the nrp-in-alloc-cands series, which is gooood.  He proposed the microversion patch last night.14:06
efriedHis bp/spec for including all resources in provider summaries got approved this morning, which is also gooood.  That was going to hold up the series.14:07
efriedI'm getting real close to having granular ready.  Just a couple more tests to write and a bug to work out.14:07
efriedCourse, we're going to be racing each other.14:07
efriedWhoever loses is going to have some serious rebasing hell.14:08
efriedBut at least progress is being made.14:08
*** gman-tx has joined #openstack-powervm14:08
edmondsw#topic PowerVM CI14:08
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:08
edmondsw#link https://etherpad.openstack.org/p/powervm_ci_todos14:08
edmondswwelcome mujahidali!14:08
esberglu3 major things going on right now for CI14:09
efriedSeems ill since last night14:09
esbergluefried: Yep. We can start there. The queens cloud is seeing those same EOF errors we were seeing on the staging14:09
esbergluHowever, on staging we changed the NIC type from some weird protocol to virtio and everything was fine14:10
efriedoh, right, this is what we were thinking was the glance wsgi business14:10
esbergluProduction is already using virtio14:10
efried'cept that should be in queens14:10
esbergluefried: The glance wsgi thing was a real issue14:10
mujahidaliedmondsw: thanks :)14:11
esbergluI'm running glance not with wsgi on production14:11
esbergluSo I will be doing more recon on the EOF errors today14:11
edmondswI assume that's top priority14:12
edmondswand then next would be the scenario tests so we can resume IT efforts14:12
esberglu2) Scenario CI14:12
esbergluI've got working scenario tests for OOT, running the suite with the same changes IT right now14:12
esbergluI will be running those tests as part of the base CI job14:13
edmondswhow can we tell they're working if the CI as a whole is not working?14:13
esbergluedmondsw: Staging env.14:13
esbergluStill some things to clean up there, but I think that should be ready by the end of the week14:14
edmondswgot numbers on what that added to the OOT CI times?14:14
esbergluedmondsw: I've only ran twice all the way through14:14
esberglu1 was 100s longer, the other actually ran faster than the base time I was comparing against14:14
edmondswthat would be really nice if we find it's negligible14:15
esbergluedmondsw: Yep. Obviously I want to get a lot more runs going through to confirm first, but seems that it may be14:15
esberglu3) Multinode CI14:16
esbergluI know what I want to do here and am 90% sure it's gonna work, just need to finish scenario before I test14:16
esbergluI learned that the subnodes are NOT always on the same underlying compute host14:17
esbergluSo we're going to have to define an AZ for each neo host. Then we can force the subnodes to be on the same neo host in nodepool14:18
edmondswi.e. read the AZ of the parent, then specify that AZ for the subnode?14:18
edmondswmy concern with AZs is that if we split each host into a different AZ, don't we have to specify the AZ on any deploy?14:20
esbergluedmondsw: Not exactly14:20
edmondswand we don't care which AZ is used for the parent, so how do we pick one?14:20
esbergluedmondsw: So we will have a bunch of providers in the nodepool conf, 1 for each AZ14:20
esbergluAnd then we will say spawn 1 node and 1 subnode14:20
esbergluSince the provider is a specific AZ, both node and subnode will be in it14:21
esbergluThe IP of the subnode is then saved in some nodepool files on the subnode14:21
edmondswso we just tell nodepool we want 1 node and 1 subnode, and for the node it picks a provider, we don't have to?14:21
esberglu*on the main node14:21
esbergluedmondsw: Yep14:21
edmondswok nice14:21
esbergluedmondsw: Only downside is that the config file is gonna be kinda gross, but oh well14:22
edmondswso how does the subnode AZ get specified?14:22
edmondswsubnode will always come from the same provider?14:22
esbergluedmondsw: Yes, you just have to config it right14:22
esbergluThat's all I have14:22
edmondswwork your magic :)14:23
edmondswlet's talk a bit about vSCSI CI14:23
edmondswI assume that's next after the 3 we just covered14:23
esbergluI thought we determined we didn't have the HW for it?14:23
edmondswI think that depends on which solution we're talking about14:24
edmondswin order to test vSCSI on every CI run, yeah, I think we would need more hardware14:24
edmondswbut mriedem suggested that it would be ok to just have a job that could be run on-demand14:24
edmondswand I think we could probably do that with the hardware we have14:24
edmondswI don't think we've ever done anything like that before, but I assume there are other examples out there we could look at14:25
esbergluedmondsw: I can start thinking about it14:26
edmondswesberglu thoughts?14:26
esbergluedmondsw: Idk how we will run on demand once jenkins goes away14:26
esbergluMaybe zuul v3 has a way to do so, but I haven't seen anything like that ever14:27
edmondswesberglu I'd probably start by asking mriedem if he knows of an example you could look at14:28
esbergluWe can sort through the details once I know more14:28
edmondswand then go from there, talk to him or infra about the zuul v3 options14:28
edmondswI wonder if that's one of the reasons zuul v3 isn't ready for 3rd party CI14:28
edmondswmujahidali coming up to speed?14:29
edmondswhave a quick update on your status?14:30
esbergluHe's got access to all of the repos, etc. now. I've started adding him to CI reviews and will start giving him some tasks14:30
edmondswalright tx14:32
edmondsw#topic Open Discussion14:32
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:32
edmondswanything else?14:32
mujahidaliesberglu: thanks for the update. edmondsw: yeah, I am looking into the code and reading the wiki14:32
edmondswok good14:32
edmondswif there's nothing else, we can get some time back. Thanks!14:33
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."14:33
openstackMeeting ended Tue May  1 14:33:41 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-05-01-14.00.html14:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-05-01-14.00.txt14:33
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-05-01-14.00.log.html14:33
*** mujahidali has quit IRC14:38
*** gman-tx has quit IRC15:32
*** gman-tx has joined #openstack-powervm15:44
*** gman-tx has quit IRC16:22
*** gman-tx has joined #openstack-powervm16:25
*** gman-tx has quit IRC16:38
*** gman-tx has joined #openstack-powervm19:11
*** gman-tx has quit IRC19:22
*** gman-tx has joined #openstack-powervm19:46
*** gman-tx has quit IRC20:12
*** gman-tx has joined #openstack-powervm20:46
*** gman-tx has quit IRC21:08
*** edmondsw has quit IRC21:48
*** tjakobs has quit IRC22:15
*** esberglu has quit IRC23:41
*** esberglu has joined #openstack-powervm23:41
*** esberglu has quit IRC23:41

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!