Tuesday, 2016-07-12

*** esberglu has joined #openstack-powervm00:09
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: CI Check  https://review.openstack.org/29593500:35
*** thorst has joined #openstack-powervm01:21
*** thorst has quit IRC01:47
*** thorst has joined #openstack-powervm01:47
*** thorst has quit IRC01:51
*** thorst has joined #openstack-powervm01:55
*** thorst has quit IRC01:56
*** thorst has joined #openstack-powervm01:56
*** thorst has quit IRC02:02
*** svenkat has quit IRC02:23
*** esberglu has quit IRC05:41
*** kotra03 has joined #openstack-powervm05:51
*** erlarese has quit IRC06:15
*** kotra03 has quit IRC06:34
*** kotra03 has joined #openstack-powervm06:35
*** erlarese has joined #openstack-powervm06:54
*** k0da has joined #openstack-powervm06:56
*** k0da has quit IRC07:06
*** efried has quit IRC07:08
*** efried has joined #openstack-powervm07:19
*** efried has quit IRC07:35
*** efried has joined #openstack-powervm07:51
*** k0da has joined #openstack-powervm08:20
*** svenkat has joined #openstack-powervm11:20
*** thorst has joined #openstack-powervm11:41
thorstsvenkat: is 331707 needed after 246898 merges?11:54
svenkatthey are two different fixes. as discussed I will pick up the +2ed fix (246898) and verify. If it works, I wiill cancel 331707 (if it is not needed)12:16
thorstsvenkat: thx12:27
*** mdrabe has joined #openstack-powervm12:31
*** kotra03 has quit IRC12:37
*** burgerk has joined #openstack-powervm12:47
*** mdrabe has quit IRC12:51
thorstefried: let me know when you want to chat about SR-IOV12:54
*** edmondsw has joined #openstack-powervm12:58
*** mdrabe has joined #openstack-powervm13:01
*** tblakeslee has joined #openstack-powervm13:08
*** seroyer has joined #openstack-powervm13:09
*** esberglu has joined #openstack-powervm13:18
*** kotra03 has joined #openstack-powervm13:25
*** arnoldje has joined #openstack-powervm13:26
*** csky has joined #openstack-powervm13:29
thorstcsky: I put a -1 on 3563.  I think I agree with overall changes in that...looking at the corresponding nova-powervm changes now though13:33
efriedthorst, now's good.  What are we talking about?  Driving pport:physnet associations from the conf?13:34
thorstefried: give me 10?  Looking through a code review and doing a LB test quick13:34
cskythorst: thanks for looking at these13:35
thorstcsky: thx for taking them over.13:39
esbergluFilter for13:45
esbergluto find the trace13:45
thorstesberglu: will be a bit.  Got a small backlog to work  :-)13:45
*** tblakeslee has quit IRC13:45
*** miltonm has quit IRC13:45
*** mdrabe has quit IRC13:46
esbergluNo worries. I’m making sure my skip list change for staging works anyways13:46
thorstefried: ready ready?13:46
thorstI can give you a call13:46
AndyWojoIs there any performance considerations for a where/how you place your lpar to use for OpenStack?  weighting, dedicated etc?13:53
*** burgerk has quit IRC14:03
efriederlarese, yt?14:05
thorstAndyWojo: Are you asking how to set the Dedicated versus Shared?  And if shared, how to set the weight?14:05
thorst(and perhaps partition priority)14:05
AndyWojoNah, not asking how, I know how to do all that. I'm just asking if there are any performance considerations on how the LPAR is to be configured to use for OpenStack14:06
AndyWojoWhether there are any standards.14:06
AndyWojoOnly thing I'll make sure is that is for memory all if it's near and not far14:06
thorstAndyWojo: OK...so next question.  Are you talking the NovaLink LPAR (where the nova-compute's run) or a general controller node?14:13
*** mdrabe has joined #openstack-powervm14:20
*** tjakobs has joined #openstack-powervm14:23
*** miltonm has joined #openstack-powervm14:24
AndyWojoNovaLink LPAR14:25
AndyWojoShould I virtualize my LPAR for compute, or have dedicated IO?14:25
adreznecAndyWojo: By default we virtualize the Novalink LPAR's network/storage, and provide it with shared uncapped procs14:28
adreznecExact needs for sizing depend on the number of LPARs you're planning to drive on the box at some level14:29
erlareseefried: hello14:29
efriederlarese: thorst and I talked over the topic of changing the pport:physnet configs on the fly.  Wanted to update you on what we discussed.14:30
efriedFirst off, he convinced me that we can't institute the simple "zero VFs" policy we were spitballing yesterday.14:31
AndyWojoGotcha, thanks.14:31
efriedTo boil it down: we can't account for stuff that was created a) outside our purview, b) before *any* association was set up.14:32
erlareseefried: is that because there could be VMs out-of-band from OpenStack management ?14:32
efriedLet's just say out-of-band in general.14:32
efriedThe other thing is SEAs set up before we know or care about the need to have these pport:physnet mappings.14:33
erlareseok, what criteria should we use to allow remapping ?14:33
efriedI'm glad you asked.  Here's what we came up with:14:33
efried1) Ignore SEAs entirely.14:33
efried2) Get all the VFs assigned to all the VMs in our purview.  Backtrace their pports.  If any hits on the pport we're trying to update, fail.14:34
efriedBut probably still use the raw VF count to issue a warning/confirmation if nonzero.14:34
erlareseok, anything else ?14:35
efriedThe other thing we need to take into account is batching these changes together.  It's likely the user will be doing more than one of these at once.  We would like to wait to restart the compute driver until the end, so we only have to do that part one time.14:35
efriedThat's going to be a UI design thing.  Totally YP ;-)14:36
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: Test Change Set 2  https://review.openstack.org/30023214:36
erlareseyeah, the UI panel would probably present all ports to remap, and then do them all as a batch when the user presses "save" or similar14:36
thorstAndyWojo: sorry - I was afk.  But I think the PowerVC team (using the PowerVM drivers) have done testing on sizing:  https://www.ibm.com/support/knowledgecenter/SSXK2N_1.3.1/com.ibm.powervc.standard.help.doc/powervc_hwandsw_reqs_hmc.html14:40
thorstbasically, the network and storage out of the box are fine.14:40
thorstand the CPU is fine14:40
thorstthe only consideration is memory and the number of VMs you plan to deploy14:41
AndyWojoGotcha, makes sense14:41
thorstthe NovaLink PowerVM installer handles most of this for you...its a pretty huge move forward14:41
thorsthave you seen the video about it?14:42
AndyWojoI haven't14:45
AndyWojoWhere's it at?14:45
thorstAndyWojo: let me get it for you14:45
AndyWojoI'm finishing up my Power KVM compute node today, and starting to work on my PowerVM compute node this weekend14:46
AndyWojoTrying to kick off other LPARs off our S822 so I can have the whole thing to myself14:46
thorstAndyWojo: https://www.youtube.com/watch?v=3veHtty-FTA14:48
thorstdon't mind the music....I think apearson picked it14:49
*** tblakeslee has joined #openstack-powervm14:49
AndyWojoThat's great14:49
adreznecThere's also https://www.youtube.com/watch?v=LUcw5eDGCrI if you're adding Novalink to an existing HMC managed machine14:51
*** burgerk has joined #openstack-powervm14:54
*** seroyer has quit IRC14:55
*** dwayne has joined #openstack-powervm14:59
*** seroyer has joined #openstack-powervm15:13
mdrabeadreznec: When adding a NovaLink system to a devstack controller, are there any special steps that need to be taken?15:25
adreznecmdrabe: Adding it how? As a compute node?15:27
adreznecThere are some local.conf settings that have to be changed to load the right compute/network drivers15:28
adreznecYou also have to have the networking-powervm ml2 driver installed/configured on the controller15:29
mdrabeThat should be the only difference?15:29
mdrabeI mean, the only difference is using the local.conf files right?15:30
adreznecThere's nothing else required that I'm aware of15:30
svenkatmdrabe i have an enviornment I created with devstaack and novalink… want to take a look?15:30
adreznecAs long as you have the right storage, etc set up15:30
adreznecFor localdisk/npiv/ssp/etc15:31
svenkati was able to deploy vm, etc with it.15:31
svenkati created a volume group on one of the vioses and set it up as ‘localdisk’ in my ovalinkenvironment15:31
mdrabesvenkat: I pinged ya :)15:31
openstackgerritCarl Pecinovsky proposed openstack/nova-powervm: Handle stale system metadata (physical WWPNs)  https://review.openstack.org/32181615:43
*** kylek3h has joined #openstack-powervm16:00
thorstmdrabe: we have several example local.conf's available if you need em16:01
thorstrather than trying to roll your own.16:01
mdrabeYep I got em all I think16:02
*** k0da has quit IRC16:16
*** kotra03 has quit IRC16:21
*** kotra03 has joined #openstack-powervm16:23
*** catintheroof has joined #openstack-powervm16:28
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: CI Check2  https://review.openstack.org/32831716:33
esbergluthorst: If I make a change to /etc/nodepool/scripts/local.conf.aio (or really anything in /etc/nodepool/scripts) do I have to restart anything or will those changes be picked up next run16:37
thorstesberglu: you have to rebuild the root image16:37
thorstwon't just be picked up next run16:37
esbergluOkay thanks16:38
AndyWojoWhat happens when you run PowerVM and PowerKVM in parallel as compute nodes? How do you choose where you want your power VMs to land?16:38
AndyWojo(through horizon), or will I have to launch via cli16:39
thorstAndyWojo: You would probably set up host groups to define where you want the instance to land16:39
thorstPowerVM images currently require an extra 'boot' partition that KVM doesn't have.  So images would be different too I believe.16:40
thorst(its a super small partition, but tells PowerVM how to boot)16:40
esbergluDoes anyone know a way to get just the image id from nodepool image-list?16:40
thorstesberglu: I don't  :-D16:41
esbergluI’m trying to find a way to delete old images from nodepool as part of the playbook but don’t know how to register the id’s of the existing images16:42
*** thorst is now known as thorst_afk16:42
*** thorst_afk is now known as thorst17:45
openstackgerritEsha Seth proposed openstack/networking-powervm: Change to selectively return all lpars vs non-novalink lpars  https://review.openstack.org/34112518:09
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM1  https://review.openstack.org/30023118:22
*** tblakeslee has quit IRC18:26
openstackgerritEsha Seth proposed openstack/networking-powervm: Change to selectively return all lpars vs non-novalink lpars  https://review.openstack.org/34112518:36
*** tblakeslee has joined #openstack-powervm18:41
*** kotra03 has quit IRC19:15
*** csky has quit IRC20:28
*** svenkat has quit IRC20:41
*** mdrabe_ has joined #openstack-powervm20:46
*** mdrabe has quit IRC20:46
*** csky has joined #openstack-powervm20:57
cskythorst: See https://review.openstack.org/#/c/321816/7 and related pypowervm 356320:59
*** k0da has joined #openstack-powervm21:01
*** thorst has quit IRC21:16
*** thorst has joined #openstack-powervm21:17
*** thorst_ has joined #openstack-powervm21:18
*** thorst__ has joined #openstack-powervm21:20
*** thorst has quit IRC21:21
*** thorst_ has quit IRC21:23
*** thorst__ has quit IRC21:24
*** burgerk has quit IRC21:55
*** esberglu has quit IRC22:06
*** k0da has quit IRC22:15
*** seroyer has quit IRC22:19
*** kylek3h has quit IRC22:20
*** tjakobs has quit IRC22:21
*** thorst has joined #openstack-powervm22:25
*** thorst_ has joined #openstack-powervm22:29
*** thorst has quit IRC22:30
*** thorst_ has quit IRC22:34
*** tblakeslee has quit IRC22:41
*** arnoldje has quit IRC22:44
*** tblakeslee has joined #openstack-powervm22:49
*** tblakeslee has quit IRC23:02
*** catintheroof has quit IRC23:09
*** arnoldje has joined #openstack-powervm23:21
*** arnoldje has quit IRC23:30
*** thorst has joined #openstack-powervm23:51

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