| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-01-30 | |||
| 20:59:46 | efried | mriedem: ack | |
| 21:00:07 | efried | Is a(ny) failure during spawn reschedulable? | |
| 21:00:24 | efried | (unrelated ^ ) | |
| 21:07:27 | mriedem | efried: no | |
| 21:07:41 | mriedem | for example, anything out of _prep_block_devices that fails is an abort | |
| 21:07:50 | mriedem | oh spawn.. | |
| 21:08:39 | mriedem | depends on what it is https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2120 | |
| 21:08:54 | mriedem | e.g. these don't get rescheduled https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2173 | |
| 21:09:33 | mriedem | several more in the block below | |
| 21:09:38 | mriedem | anything not specifically caught is rescheduled | |
| 21:09:56 | efried | mriedem: Got it, thanks. | |
| 21:12:23 | sean-k-mooney | cfriesen yes and it used to have have both flavor extra specs and an image property to allwo you to set the policy | |
| 21:12:29 | sean-k-mooney | cfriesen: https://github.com/openstack/nova-specs/blob/f350472e627db1afbe5e32c35a9973124642ecf1/specs/queens/implemented/share-pci-between-numa-nodes.rst#proposed-change | |
| 21:12:41 | sean-k-mooney | cfriesen: but it was not implemanted and the spec was retroactivly updated. | |
| 21:13:11 | sean-k-mooney | cfriesen: i want to add those back in in train and complete the original spec | |
| 21:13:31 | sean-k-mooney | cfriesen: i discoverd this in novemebr but did not have time to work on it this cycle | |
| 21:13:41 | cfriesen | sean-k-mooney: right, I remember that. so how does the pci alias in the config file map to what gets used for SR-IOV? | |
| 21:14:07 | sean-k-mooney | cfriesen: the alias works assuming stepens patch merged | |
| 21:14:22 | sean-k-mooney | cfriesen: there was a bug were we were not storing the policy in the db | |
| 21:14:45 | cfriesen | sean-k-mooney: as I recall, we decided that setting the policy on the alias was sufficient since most likely all requests for a particular device would use the same PCI affinity (ie either you care about performacne on that device or not) | |
| 21:15:21 | sean-k-mooney | cfriesen: we need these https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bug/1805891 | |
| 21:15:42 | sean-k-mooney | cfriesen: https://bugs.launchpad.net/nova/+bug/1805891 | |
| 21:15:44 | openstack | Launchpad bug 1805891 in OpenStack Compute (nova) "pci numa polices are not followed" [High,In progress] - Assigned to Stephen Finucane (stephenfinucane) | |
| 21:15:47 | cfriesen | sean-k-mooney: we don't specify an alias explicitly for SR-IOV networking though, right? it looks up the network in the pci whitelist. So how do we decide which alias to use? | |
| 21:16:42 | sean-k-mooney | oh right sorry ya there is no way to adjust the policy for srivo devices at all | |
| 21:17:00 | sean-k-mooney | i taught the policy was in teh whitelist for a second not the alais | |
| 21:17:18 | cfriesen | on reflection, that kind of seems like an oversight. :) | |
| 21:17:33 | sean-k-mooney | cfriesen: well it was in the spec for a reason | |
| 21:17:59 | sean-k-mooney | specifcally so that neutron sriov prot could be supported | |
| 21:18:32 | cfriesen | I think when we switched to putting it in the alias we probably missed the fact that the alias didn't apply to devices associated with neutron ports | |
| 21:19:14 | cfriesen | certainly I didn't realize it at the time | |
| 21:19:43 | sean-k-mooney | well the alias was never ment to be suported at all | |
| 21:20:55 | sean-k-mooney | i personally think we shoudl have followed the spec in the frist place. | |
| 21:24:20 | sean-k-mooney | cfriesen: anyway am im hoping to change this in train. i think i commented on the starlingx tread a few montsh ago about the histroy of this and the current state | |
| 21:24:56 | cfriesen | sean-k-mooney: okay, will keep an eye out | |
| 22:09:37 | artom | https://review.openstack.org/#/c/599208/ | |
| 22:09:56 | artom | Please someone tell me I'm not the only struggling with almost every single line in that beast | |
| 22:14:24 | efried | artom: I admit I haven't looked at it again since a much earlier PS. It's on my list, and steadily creeping higher. | |
| 22:16:09 | mriedem | artom: i just realized that these bdm docs don't mention tags at all https://docs.openstack.org/nova/latest/user/block-device-mapping.html#block-device-mapping-v2 | |
| 22:21:10 | openstackgerrit | Merged openstack/nova master: Consolidate inventory refresh https://review.openstack.org/615695 | |
| 22:21:17 | efried | woot | |
| 22:28:39 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add microversion to expose virtual device tags https://review.openstack.org/631948 | |
| 22:53:17 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Fix config docs for handle_virt_lifecycle_events https://review.openstack.org/634058 | |
| 23:09:45 | artom | mriedem, yeah, except the api-ref there's 0 device tagging documentation | |
| 23:10:02 | artom | It's been a low-ish priority item on my backlog for a long time | |
| 23:10:34 | artom | I wrote https://notartom.net/2017/06/20/virtual-device-role-tagging-better-explained/ but need to "upstream" it properly | |
| 23:56:03 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove deprecated 'os-flavor-manage' policy https://review.openstack.org/633656 | |
| 23:56:17 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Fix a missing policy in test policy data https://review.openstack.org/633686 | |
| #openstack-nova - 2019-01-31 | |||
| 00:02:33 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (3) https://review.openstack.org/574104 | |
| 00:02:45 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (4) https://review.openstack.org/574106 | |
| 00:02:57 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (5) https://review.openstack.org/574110 | |
| 00:03:07 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (6) https://review.openstack.org/574113 | |
| 00:03:19 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (7) https://review.openstack.org/574974 | |
| 00:03:30 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (8) https://review.openstack.org/575311 | |
| 00:08:26 | alex_xu | mriedem: thanks. so we just need to ask admin to cleanup the image after user unshelve the instance | |
| 00:08:41 | alex_xu | that seems fine | |
| 00:16:37 | openstackgerrit | Hang Yang proposed openstack/nova stable/queens: Fix port dns_name reset https://review.openstack.org/633807 | |
| 00:30:42 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (9) https://review.openstack.org/575581 | |
| 00:31:37 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (10) https://review.openstack.org/576017 | |
| 00:31:46 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (11) https://review.openstack.org/576018 | |
| 00:31:57 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (12) https://review.openstack.org/576019 | |
| 00:32:08 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13) https://review.openstack.org/576020 | |
| 00:32:18 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14) https://review.openstack.org/576027 | |
| 00:32:49 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15) https://review.openstack.org/576031 | |
| 00:33:03 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16) https://review.openstack.org/576299 | |
| 00:33:16 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17) https://review.openstack.org/576344 | |
| 00:33:27 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18) https://review.openstack.org/576673 | |
| 00:33:40 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.openstack.org/576676 | |
| 00:33:56 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.openstack.org/576689 | |
| 00:34:07 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.openstack.org/576709 | |
| 00:34:21 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.openstack.org/576712 | |
| 00:52:08 | artom | The transport_url is missing from nova_cell1.conf on the second compute node in multinode devstack, the compute couldn't "join" | |
| 00:52:13 | artom | Did I do something wrong? | |
| 01:15:08 | bhagyashris | artom: Hi, | |
| 01:17:34 | artom | bhagyashris, oh, hah, we finally cross paths (and timezones!) | |
| 01:17:58 | bhagyashris | artom: Yeah :) | |
| 01:21:10 | bhagyashris | artom: I just want to know about the spec https://review.openstack.org/#/c/599587/9 (numa-aware-live-migration spec) so is this spec targeted for Stein? I saw the patches submitted aginst it https://review.openstack.org/#/q/status:open+topic:bp/numa-aware-live-migration but didn't the nova patches :( | |
| 01:21:27 | artom | Nothing posted yet in terms of patches :( | |
| 01:21:44 | artom | Still aiming for Stein, but yeah, realistically we may miss it | |
| 01:24:19 | bhagyashris | artom: Thank you for update :) | |
| 01:39:54 | mriedem | artom: might be related to https://bugs.launchpad.net/devstack/+bug/1813215 | |
| 01:39:56 | openstack | Launchpad bug 1813215 in devstack "nova-compute in singleconductor mode (grenade jobs) trying (and failing) to reach scheduler" [Undecided,Confirmed] | |
| 01:40:05 | mriedem | but that's in a grenade job with singleconductor mode so probably not | |
| 01:40:24 | artom | mriedem, yeah, the default is superconductor, right? | |
| 01:40:29 | mriedem | yeah | |
| 01:40:39 | artom | Just to be sure I'm re-stacking with it explicitly set | |
| 01:40:59 | openstack | Launchpad bug 1810317 in devstack "Multi-Node Lab in DevStack" [Undecided,New] | |
| 01:40:59 | mriedem | this, btw, is a nice bug report https://bugs.launchpad.net/devstack/+bug/1810317 | |
| 01:41:44 | artom | Is that the pimp complaint? | |
| 01:41:56 | mriedem | "the" | |
| 01:41:56 | artom | mriedem, huh, so setting it explicitly did the trick | |
| 01:41:57 | mriedem | ? | |
| 01:42:09 | artom | I got a cinder error after, but at least that hurdle is passed | |
| 01:42:26 | artom | I found a bug complaining about the "pimp" wording | |
| 01:42:34 | artom | Earlier when I was searching around about my problem | |
| 01:43:54 | mriedem | i'm not really sure what "pimp your stack" means in this context anyway, i guess "make your devstack all fancy"? | |
| 01:47:28 | artom | You know, first you let your friend creates VMs on your stack, then before she knows it anyone who pays can do all kinds of nasty stuff | |
| 01:50:47 | artom | Oh, [database]/connection is empty in cinder.conf | |
| 01:51:54 | mriedem | why are you doing this by hand? | |
| 01:52:11 | mriedem | i mean, unless it's fun | |