Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-08-20
10:35:35 aspiers stephenfin: why does test-requirements.txt have psycopg2 at all? is postgres still supported?
10:36:02 sean-k-mooney if you intalled the card in a pci slot connected to the chipset via the dmi bridge rahter then then directly to the cpu that could also cause the same issue were you are sharing an iommu groupe between multiple devices
10:36:02 cervigni lspci: -s: Invalid slot number
10:36:02 cervigni IOMMU Group 81:
10:36:13 cervigni uhm that is definitely a wrong group
10:36:15 sean-k-mooney that is not how you check
10:36:16 stephenfin aspiers: I recall cfriesen mentioning something about them caring about postgres in the distant pass, but I honestly can't say any more than that
10:36:20 stephenfin yaawang: Sure thing
10:36:40 aspiers stephenfin: about who caring?
10:36:51 stephenfin Windriver
10:36:54 aspiers oh
10:37:04 aspiers SUSE used to use pg for OpenStack, but ditched it quite a while ago
10:37:06 stephenfin *Wind River?
10:37:22 stephenfin Yeah, I've no idea if it even works nowadays
10:37:24 sean-k-mooney cervigni: give me a sec and ill see if i can get the command
10:37:26 aspiers Yeah X-D Windriver makes me think of DLLs *shudder*
10:38:00 aspiers stephenfin: seems dumb that I have to install pg_config to run unit tests
10:38:13 stephenfin Or build docs
10:38:23 stephenfin or do anything, really
10:38:35 cervigni thanks
10:38:37 stephenfin tbh, we shouldn't even need the MySQL dependencies for that
10:39:09 aspiers true
10:39:36 sean-k-mooney cervigni: this is not the exact command but more or less does what you want
10:40:59 sean-k-mooney http://paste.openstack.org/show/760302/
10:41:18 sean-k-mooney you will want to pipe that to less and check iommu group 81
10:42:05 cervigni that is the same of what I pasted earlier, for IOMMU group 81 (where the problem comes from)
10:42:10 sean-k-mooney you can also just do ls /sys/kernel/iommu_groups/81/devices/
10:42:21 cervigni it reports only a lspci: -s: Invalid slot number
10:42:38 sean-k-mooney yes -s take a pci address not iommu group number
10:42:45 sean-k-mooney they are totally different things
10:42:51 cervigni ok
10:43:16 sean-k-mooney what do you get for "ls /sys/kernel/iommu_groups/81/devices/"
10:43:35 cervigni driver iommu_group mdev_type nvidia power remove subsystem uevent
10:43:35 cervigni [root@compute-r6-h28 ~]# ls /sys/kernel/iommu_groups/81/devices/a0543cde-3934-460f-8994-6be8c80fe417/
10:56:40 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Document global options for nova-manage https://review.opendev.org/677443
10:56:40 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Note use of 'nova-manage db sync --config-file' https://review.opendev.org/671298
10:56:41 openstackgerrit Stephen Finucane proposed openstack/nova master: config: Explicitly register 'remote_debug' CLI opts https://review.opendev.org/677444
11:34:50 openstackgerrit Stephen Finucane proposed openstack/nova master: Move calls to ovs-vsctl to privsep. https://review.opendev.org/639282
11:34:51 openstackgerrit Stephen Finucane proposed openstack/nova master: Move final bridge commands to privsep. https://review.opendev.org/639580
11:34:51 openstackgerrit Stephen Finucane proposed openstack/nova master: Move setting of device trust to privsep. https://review.opendev.org/639283
11:34:52 openstackgerrit Stephen Finucane proposed openstack/nova master: We no longer need rootwrap. https://review.opendev.org/554438
11:34:52 openstackgerrit Stephen Finucane proposed openstack/nova master: Cleanup the _execute shim in nova/network. https://review.opendev.org/639581
11:34:53 openstackgerrit Stephen Finucane proposed openstack/nova master: Address nits from privsep series https://review.opendev.org/677210
11:34:53 openstackgerrit Stephen Finucane proposed openstack/nova master: Cleanup no longer required filters and add a release note. https://review.opendev.org/639826
11:34:54 openstackgerrit Stephen Finucane proposed openstack/nova master: WIP! Stop passing 'root_helper' argument to os-brick https://review.opendev.org/677451
12:43:26 openstackgerrit Adam Spiers proposed openstack/nova master: Track libvirt host/domain capabilities for multiple machine types https://review.opendev.org/673151
12:46:36 openstackgerrit Adam Spiers proposed openstack/nova master: Track libvirt host/domain capabilities for multiple machine types https://review.opendev.org/673151
12:50:41 openstackgerrit Adam Spiers proposed openstack/nova master: Provide HW_CPU_X86_AMD_SEV trait when SEV is supported https://review.opendev.org/638680
12:50:41 openstackgerrit Adam Spiers proposed openstack/nova master: Extract new base class for provider usage functional tests https://review.opendev.org/676964
12:51:33 openstackgerrit Alexandra Settle proposed openstack/nova stable/rocky: Fixing broken links https://review.opendev.org/677460
12:53:31 alex_xu aspiers: the line 697-701 of https://review.opendev.org/#/c/673151/11/nova/virt/libvirt/host.py is about the why we need that set of machine type?
12:54:10 aspiers alex_xu: We need to cover the main variants
12:54:39 alex_xu aspiers: ok, so the pc and q35 can cover all the cases, right?
12:54:43 aspiers yes
12:55:03 aspiers this is mentioned in the commit message
12:55:06 alex_xu aspiers: thanks, i see now
12:55:15 alex_xu aspiers: is it too arch specific?
12:55:31 alex_xu although I didn't see other arch need this method
12:55:32 aspiers pc / q35 are not hardcoded
12:56:18 aspiers alex_xu: they come from utils.get_default_machine_type() and libvirt's getCapabilities
12:56:28 alex_xu I mean in other arch, it is also about default and canonical covering all the cases
12:56:30 aspiers so other architectures will get a different set
12:56:36 aspiers yes, correct
12:57:03 alex_xu ok, I'm just going to trust the libvirt and platform experts
12:57:34 aspiers that's why I had to remove 'bamboo' from the fixture
12:58:15 sean-k-mooney bamboo as a fake arch or machine type :)
12:58:27 alex_xu hah
12:58:29 aspiers because the static fixtures for getDomainCapabilities on ppc did not return correct values for bamboo
12:58:30 sean-k-mooney i can see both working
12:58:44 aspiers bamboo is a real machine type for ppc
12:58:50 sean-k-mooney really ok
12:59:02 sean-k-mooney but ya its not in the static data we are using right
12:59:03 alex_xu aspiers: so the only complain is no unittest for host.py change, but I'm ok with a followup.
12:59:03 openstackgerrit Matt Riedemann proposed openstack/nova master: Update api-ref for 2.75 to add config_drive in server update response https://review.opendev.org/677324
12:59:04 aspiers https://review.opendev.org/#/c/673151/13/nova/tests/unit/virt/libvirt/fakelibvirt.py@1673
13:01:20 openstackgerrit Mohammed Naser proposed openstack/nova master: requirements: move to using psycopg2-binary https://review.opendev.org/676684
13:01:49 openstackgerrit Mohammed Naser proposed openstack/nova master: requirements: move to using psycopg2-binary https://review.opendev.org/676684
13:02:52 aspiers alex_xu: hmm that's a good point
13:08:18 openstackgerrit Matt Riedemann proposed openstack/python-novaclient master: Microversion 2.75 - Multiple API cleanup changes https://review.opendev.org/676275
13:10:16 mriedem final 2 patches for 2.75 https://review.opendev.org/#/q/topic:bp/api-consistency-cleanup+status:open
13:11:12 alex_xu aspiers: the spec said the trait "a) it cannot be used yet, only in the future when SEV support is fully implemented,"...that confuse me
13:11:30 alex_xu is there any update for the exist spec, we need that trait again?
13:12:29 sean-k-mooney alex_xu: we will need that trait only when intels mktme feature is supported
13:12:47 aspiers right
13:13:26 sean-k-mooney need is also a strong word there in that it is only needed if you specifica want SEV
13:13:52 sean-k-mooney if you jsut want encyrpetd memory you use the resouce class on its own
13:13:57 alex_xu sean-k-mooney: they share same resource class?
13:14:10 aspiers MKTME is not implemented yet
13:14:15 aspiers but we expect it to use the same resource class
13:14:21 alex_xu ok, i see now
13:14:32 aspiers the MKTME spec is still in draft
13:14:52 alex_xu yea, I didn't follow that spec
13:15:00 aspiers but the resource class is not used directly by users/operators, only internally
13:15:03 alex_xu but I "should"
13:15:17 aspiers externally they use hw:mem_encryption extra spec and hw_mem_encryption image property
13:15:40 aspiers and that gets translated in the RequestSpec to resources:MEM_ENCRYPTION_CONTEXT=1
13:15:54 sean-k-mooney given that one is an intel only tech and the other is an amd only tech we do not expec a singel RP to have inventoies fo both so 1 resouce class and 2 traits for what is effectvly the same thing form a guest point of view
13:16:08 aspiers right
13:16:38 alex_xu got it
13:17:54 openstackgerrit Adam Spiers proposed openstack/nova master: Add extra spec parameter and image property for memory encryption https://review.opendev.org/664420

Earlier   Later