Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-01-03
19:35:47 openstackgerrit sean mooney proposed openstack/nova-specs master: Add spec for sriov live migration https://review.openstack.org/605116
19:40:21 openstackgerrit Chris Dent proposed openstack/nova master: Switch to using os-resource-classes https://review.openstack.org/628278
20:38:21 cfriesen when advertising new traits (specifically the COMPUTE_SECURITY_TPM_2_0 trait), does the trait need to be added to some standard list first?
20:40:59 cdent cfriesen: you mean placement related traits or other kinds of traits?
20:41:13 cfriesen placement
20:41:40 cfriesen does it need to get added to os_traits first or something?
20:41:43 cdent to create a new standard trait it gets added to the os-traits lib: http://git.openstack.org/cgit/openstack/os-traits
20:41:58 cdent and then the code which uses the added trait depends on the release of the lib that includes it
20:42:55 cfriesen okay, makes sense. for the one I mentioned above, would that go in os_traits/compute/security.py then? with TRAITS=['TPM_2_0"] as the content?
20:43:08 cdent lemme confirm, one sec
20:43:13 sean-k-mooney1 cfriesen: any trait not defiend in os-traitns must start with CUSTOM_
20:43:19 melwitt o/
20:43:38 cfriesen sean-k-mooney1: yeah...the intent is for this to be a standard trait, so I think we need to add it to os_traits
20:43:59 cdent cfriesen: simple answer to you where and content question is "yes"
20:44:06 sean-k-mooney1 yes you do i had a patch for that i abandons over a year ago
20:44:09 cfriesen cdent: sweet, thanks
20:44:36 cdent you're welcome
20:45:19 sean-k-mooney1 cfriesen: https://review.openstack.org/#/c/514712/3/os_traits/hw/platform/security.py
20:46:15 sean-k-mooney1 melwitt: o/ happy new year
20:46:48 melwitt sean-k-mooney1: happy new year
20:47:03 cdent sean-k-mooney1, cfriesen is it COMPUTE or HW?
20:47:22 cfriesen so in the spec we have it as COMPUTE_SECURITY_TPM_2_0
20:47:45 cfriesen at the time of sean's change I don't think the "compute" subdirectory existed yet
20:48:30 sean-k-mooney1 cdent: my patch was from 2017 so the example is in the wong folder but as cfriesen said the spec says COMPUTE_SECURITY_TPM_2_0
20:50:42 mriedem melwitt: i'm out next week so if you want me to review the counting quotas from placement spec after updates, you probably need to make those soonish https://review.openstack.org/#/c/509042/
20:51:08 mriedem i made a lot of comments but i'm not sure there is anything earth shattering in there
20:51:44 sean-k-mooney1 cdent: i tink where we left the disucstion was compute traits did not require hardware an hypervior that can emulate a tpm can advertise COMPUTE_SECURITY_TPM_2_0 but HW_SECURITY_TPM_2_0 would be resrved for futur use to signify that the host has a tpm that supports v2
20:51:55 melwitt mriedem: thank you for the reminder. I'll go through and reply/update today
20:56:31 melwitt nova meeting in 4 minutes
21:02:49 mriedem dansmith: forgot to ask earlier but was hoping you could reply to http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001112.html and if there is compromise we can update the spec and move forward before the freeze
21:07:34 dansmith mriedem: ugh
21:08:34 dansmith mriedem: can we discuss tomorrow? I'm guessing I'm not really going to be happy with any of the options, but I need to page all that in before I will know I guess
21:09:17 mriedem sure
21:21:23 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix circular import in nova.privsep.utils https://review.openstack.org/628302
21:43:29 openstackgerrit Matt Riedemann proposed openstack/nova master: Run nova-lvm job on nova/privsep/* changes https://review.openstack.org/628306
21:46:04 mriedem ade_lee: ^
21:47:27 cfriesen I'm looking for input on https://review.openstack.org/#/c/618542...for the "quota:" stuff that is defined in https://docs.openstack.org/nova/latest/user/flavors.html but might only apply to one or two hypervisors, does it make sense to enforce the rules even if the instance might end up on a hypervisor that ignores those extra-specs?
21:47:47 sean-k-mooney1 i was going to mention https://review.openstack.org/#/c/591607/ for open discussion. melwitt: looks like the ordering was corrected
21:48:59 sean-k-mooney1 ah the parent patch has a -1 while they work on functional tests
21:49:08 sean-k-mooney1 nevermind
21:50:01 melwitt sean-k-mooney1: ah, ok
21:51:18 melwitt I saw some discussion in gerrit
21:52:27 ade_lee mriedem, thanks!
21:57:57 dansmith mriedem: there, I replied
21:58:34 mriedem <3
22:20:28 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (3) https://review.openstack.org/574104
22:20:43 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (4) https://review.openstack.org/574106
22:20:52 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (5) https://review.openstack.org/574110
22:21:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix circular import in nova.privsep.utils https://review.openstack.org/628302
22:21:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Run nova-lvm job on nova/privsep/* changes https://review.openstack.org/628306
23:26:21 openstackgerrit Matt Riedemann proposed openstack/nova-specs master: Spec for cross-cell resize https://review.openstack.org/616037
23:26:36 mriedem round trois
23:28:50 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (6) https://review.openstack.org/574113
23:29:01 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (7) https://review.openstack.org/574974
23:29:19 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (8) https://review.openstack.org/575311
23:48:29 openstackgerrit Merged openstack/nova-specs master: Remove doc about metadata from 'share-pci-between-numa-nodes' https://review.openstack.org/619807
#openstack-nova - 2019-01-04
00:06:28 openstackgerrit Merged openstack/nova-specs master: Remove the duplicate words https://review.openstack.org/617615
01:24:09 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (9) https://review.openstack.org/575581
01:24:17 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (10) https://review.openstack.org/576017
01:24:38 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (11) https://review.openstack.org/576018
02:24:05 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (12) https://review.openstack.org/576019
02:24:24 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13) https://review.openstack.org/576020
02:24:51 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14) https://review.openstack.org/576027
03:38:31 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15) https://review.openstack.org/576031
03:38:46 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16) https://review.openstack.org/576299
03:38:59 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17) https://review.openstack.org/576344
04:10:15 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18) https://review.openstack.org/576673
04:10:23 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.openstack.org/576676
04:11:19 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.openstack.org/576689
04:11:50 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.openstack.org/576709
04:12:18 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.openstack.org/576712
06:46:16 openstackgerrit weizj proposed openstack/python-novaclient master: Update hacking version https://review.openstack.org/627726
06:47:23 openstackgerrit Yikun Jiang proposed openstack/nova master: WIP: Per aggregate scheduling weight https://review.openstack.org/628163
08:41:29 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Allow run metadata api per cell https://review.openstack.org/624612
09:14:30 openstackgerrit Yikun Jiang proposed openstack/nova master: Per aggregate scheduling weight https://review.openstack.org/628163
09:42:06 openstackgerrit Yikun Jiang proposed openstack/nova master: Per aggregate scheduling weight https://review.openstack.org/628163
09:45:26 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Specifying az when restore shelved server https://review.openstack.org/624689
10:16:00 openstackgerrit melanie witt proposed openstack/nova-specs master: Propose counting quota usage from placement and API database https://review.openstack.org/509042
12:58:20 openstackgerrit Rui Zang proposed openstack/nova-specs master: support virtual persistent memory https://review.openstack.org/601596
13:03:31 openstackgerrit Rui Zang proposed openstack/nova-specs master: support virtual persistent memory https://review.openstack.org/601596
13:57:50 openstackgerrit Chris Dent proposed openstack/os-resource-classes master: Don't use upper-constraints when installing package https://review.openstack.org/628442
14:42:41 mriedem https://review.openstack.org/#/c/628302/ fixes the lvm job
16:01:28 mriedem johnthetubaguy: i could use review from you on the mega-beast cross-cell resize spec https://review.openstack.org/#/c/616037/ - got a +2 from dan, and it's a high level plan based on some prototyping, but clearly is complicated enough that a lot of stuff is just going to have to be dealt with during implementation
16:02:34 mriedem tl;dr orchestrate from conductor across the two cells, try to maintain similar style flows as normal resize with minimal disruption to the end user experience
16:43:01 openstackgerrit weizj proposed openstack/os-resource-classes master: Update hacking version to latest https://review.openstack.org/628599
16:43:04 openstackgerrit weizj proposed openstack/os-vif master: Update hacking version to latest https://review.openstack.org/628603
16:43:05 openstackgerrit weizj proposed openstack/os-traits master: Update hacking version to latest https://review.openstack.org/628604
17:28:08 mriedem gibi_off: i'm out next week but we should maybe have a google hangout call the week of the 14th to try and level set with some others involved like jaypipes, dansmith, melwitt etc to sort out the path forward with the bw scheduling stuff - a 30 minute call would probably be more productive than the ML thread at this point
17:29:14 mriedem if the series doesn't get reversed in order to move the api/control plane changes to the end of the stack, then maybe putting an in-code feature flag placeholder for the time being would allow us to sort out what we need to do re discoverability etc
18:04:25 mriedem melwitt: +2 on the counting quotas from placement spec
18:04:30 mriedem thanks for the detailed updates
18:16:51 jaypipes mriedem: I'm fine to do a hangout next week.
18:17:00 jaypipes or the week after
18:17:12 mriedem week after is going to be all hangouts all the time
18:28:07 melwitt mriedem: hangout on the 14th works for me
18:29:25 melwitt mriedem: and thanks for reviewing counting quotas from placement before you head out next week. I appreciate it
18:31:28 cdent melwitt, mriedem for the placement aggressive checkpoint meeting, can we do that not on the monday? any other day/time should be fine for me
18:32:49 melwitt cdent: I think so, I don't think we were thinking the 14th specifically, just some time during the week of the 14th
18:33:06 cdent cool, thanks
18:51:02 mriedem yeah i don't really want meetings on the first day i'm back :)

Earlier   Later