| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-11-09 | |||
| 20:47:43 | sean-k-mooney | well | |
| 20:47:54 | sean-k-mooney | no its the use fo system_reader that is too heavy here | |
| 20:48:16 | sean-k-mooney | i kind fo would liek if we could use the tenant isolation aggreate info | |
| 20:48:31 | sean-k-mooney | so that with project_admin you coudl list hosts and only see those hosts | |
| 20:48:41 | sean-k-mooney | so no system reader | |
| 20:48:54 | sean-k-mooney | needed to boot to a host you are allowed to boot too | |
| 20:49:28 | sean-k-mooney | if you are not limited to an aggreate i guess that would list all hosts | |
| 20:49:30 | gmann | but host is not project level info right | |
| 20:49:38 | sean-k-mooney | it kind of is | |
| 20:49:48 | sean-k-mooney | we supprot assocating tenats/project to aggreates | |
| 20:50:00 | sean-k-mooney | via either a placment prefilter or a schduler post filter | |
| 20:50:04 | gmann | but project_admin is our special case. means no where else it is being used | |
| 20:50:41 | sean-k-mooney | that the thing i see it potally being a thing in other services too | |
| 20:50:53 | gmann | ah yeah | |
| 20:51:36 | sean-k-mooney | i can totally see project admins being allowed to create users for a project in there project only via keystoen for example | |
| 20:51:50 | sean-k-mooney | or managing a subset of roles with in a porject | |
| 20:52:12 | sean-k-mooney | e.g. givie a user project_reader, porject_admin or project member | |
| 20:52:22 | sean-k-mooney | for that project | |
| 20:52:23 | gmann | also i think neutron might have when they do new policy like attr level policy rule etc | |
| 20:52:56 | sean-k-mooney | right i could see requiring proejct_admin to create shared networks for example | |
| 20:53:06 | sean-k-mooney | or better example | |
| 20:53:09 | gmann | so both options (sys reader or project admin) have pros and cons. | |
| 20:53:13 | sean-k-mooney | adding a qos policy to a network | |
| 20:53:37 | melwitt | I'm not 100% following this convo but wanted to mention I think it's normal and expected that users will have to request and use appropriate tokens (and have appropriate roles) for individual APIs and that if we try to fit everything a user can possibly want to do to fall under one token scope/role then we're going back toward the "admin does everything" direction, trying to make everything fit into one box again | |
| 20:53:38 | sean-k-mooney | to make proejct_admin work we woudl need other code changes | |
| 20:54:52 | sean-k-mooney | melwitt: multiple tokens totally makes sense but i dont think system_reader is approcate for anyoen that you dont fully trust | |
| 20:55:13 | sean-k-mooney | so i can see system reader ever be appliable for a tenant of a vexhost cloud | |
| 20:55:22 | sean-k-mooney | that did not work at vexhost | |
| 20:55:26 | gmann | melwitt: yeah. project_admin was really a temp think with assumption that system scope users to allow creating server for projetcs | |
| 20:56:22 | sean-k-mooney | the main usecasue for system_reader is for audits right | |
| 20:56:44 | sean-k-mooney | so by default you would want system_reader to be able to read across multipel projects | |
| 20:57:04 | sean-k-mooney | where as proejct_reader would be the same fucntion for a singel project | |
| 20:57:13 | sean-k-mooney | and domain is inbetween | |
| 20:57:22 | sean-k-mooney | read only access to all proejct in a domain | |
| 20:57:30 | sean-k-mooney | *project resouces | |
| 20:59:19 | sean-k-mooney | if you require something more the system_reader for inter proejct server list then it kind of breakes its orginal usecause | |
| 20:59:46 | sean-k-mooney | anyway its late and im hungry so ill call it a night | |
| 20:59:55 | sean-k-mooney | gmann: thanks for the info o/ | |
| 21:00:21 | gmann | but if any users is allowed to boot on requested host then it is special user right. | |
| 21:00:56 | gmann | sean-k-mooney: sure. take rest. We can discuss tomorrow. | |
| 22:30:20 | itsjg | an easy way to see why the scheduler throws an error, is there some place to look that I'm missing? | |
| 22:30:20 | itsjg | Hello! Could someone help point me in the right direction, I can't get a machine to migrate off an old host due to the "No valid host found for cold migrate (HTTP 400)" error. I have tried setting every debug logging level to maximum but can't get any further details as to why nova-scheduler is not moving the VM to a different host. I have plenty of capacity across the whole cluster, checked all compute services across the whole cluster, etc. I guess f | |
| 23:32:26 | openstackgerrit | Ghanshyam Mann proposed openstack/nova master: Improve policy doc for supported scope info https://review.opendev.org/762013 | |
| 23:33:12 | gmann | sean-k-mooney: melwitt johnthetubaguy ^^ adding nova supported scope & roles into doc | |
| 23:34:42 | melwitt | ack | |
| 23:51:47 | openstackgerrit | Merged openstack/nova master: rbd: Only log import failures when the RbdDriver is used https://review.opendev.org/761762 | |
| #openstack-nova - 2020-11-10 | |||
| 00:31:53 | openstackgerrit | Ghanshyam Mann proposed openstack/nova master: Improve policy doc for supported scope info https://review.opendev.org/762013 | |
| 00:44:02 | openstackgerrit | MaAoyu proposed openstack/os-traits master: bump py37 to py3 in tox.ini https://review.opendev.org/757432 | |
| 01:09:43 | openstackgerrit | Merged openstack/nova stable/victoria: Update pci stat pools based on PCI device changes https://review.opendev.org/761700 | |
| 04:52:40 | openstackgerrit | jichenjc proposed openstack/nova master: Print more helpful info when qemu validation failed https://review.opendev.org/762035 | |
| 06:28:08 | openstackgerrit | Xinran WANG proposed openstack/nova-specs master: SRIOV Enabled Nic Support Specification https://review.opendev.org/742785 | |
| 07:03:47 | openstackgerrit | Xinran WANG proposed openstack/nova-specs master: SRIOV Enabled Nic Support Specification https://review.opendev.org/742785 | |
| 09:05:34 | bauzas | good morning Nova | |
| 09:41:07 | lyarwood | Morning | |
| 10:38:48 | gibi | o/ | |
| 11:22:35 | gibi | "Delay in Elastic Search: Up to date" | |
| 11:22:44 | gibi | hm, did infra cleared the 144 hours of queue? | |
| 11:32:48 | stephenfin | lyarwood, gibi, kashyap: Could you folks cast your eye over https://review.opendev.org/#/q/topic:bp/smarter-usb-devices this week? | |
| 11:34:10 | gibi | added to my list, but it is now behind the cyborg shelve/unshelve patch where I'm really late already. | |
| 11:35:34 | kashyap | stephenfin: On a phone; will queue, sir | |
| 12:04:41 | sean-k-mooney | lyarwood: is "libvirt.libvirtError: internal error: missing block job data for disk 'vda'" something that is currently happening on bionic | |
| 12:05:22 | sean-k-mooney | it looks like that is what is calling the grenade multi node job to fail during a paused live migratrion | |
| 12:07:54 | openstack | Launchpad bug 1901739 in OpenStack Compute (nova) " libvirt.libvirtError: internal error: missing block job data for disk 'vda'" [High,Fix released] - Assigned to Lee Yarwood (lyarwood) | |
| 12:07:54 | lyarwood | sean-k-mooney: yeah https://bugs.launchpad.net/nova/+bug/1901739 - I should move this back to open | |
| 12:09:17 | lyarwood | updated | |
| 12:09:51 | sean-k-mooney | ok do w ehave a workaround e.g moving master to focal for grenade | |
| 12:10:06 | sean-k-mooney | victoria should have been focal anyway right | |
| 12:10:10 | lyarwood | sean-k-mooney: correct | |
| 12:10:24 | lyarwood | sean-k-mooney: and we are going to backport moving these jobs to focal to stable/victoria AFAIK | |
| 12:11:09 | lyarwood | brb | |
| 12:16:49 | sean-k-mooney | oh you removed the parent of the grenade job by mistake but https://review.opendev.org/#/c/742056/ corrects it and movs to v3 | |
| 12:31:56 | sean-k-mooney | lyarwood: could we make the multinode grenade job nonvoting until https://review.opendev.org/#/c/742056/ is merged | |
| 12:32:45 | sean-k-mooney | i think we also will need to use the cloud archive to get libvirt 6.0 for some of the other stable branches | |
| 12:32:53 | sean-k-mooney | that have to run on bionic | |
| 12:34:28 | sean-k-mooney | am i correct in assuming ussuri proably has support for blockdev too or was that added in victoria | |
| 12:34:47 | openstack | Launchpad bug 1901739 in OpenStack Compute (nova) " libvirt.libvirtError: internal error: missing block job data for disk 'vda'" [High,In progress] - Assigned to Lee Yarwood (lyarwood) | |
| 12:34:47 | sean-k-mooney | https://bugs.launchpad.net/nova/+bug/1901739/comments/6 is the root cause right? | |
| 12:40:10 | sean-k-mooney | i think im going to repopose https://opendev.org/openstack/devstack/commit/7f7f488bc385dd707a3a6d8dae7859bbe72182e5 with victoria instead | |
| 13:06:42 | kashyap | sean-k-mooney: Yeah; the workaround is mentioned in the bug as a comment | |
| 13:07:13 | sean-k-mooney | using libvirt 6.0.0 | |
| 13:07:25 | kashyap | Yep | |
| 13:07:36 | sean-k-mooney | really that just means we are not fixing the issue form openstack and raising the min libvirt | |
| 13:07:41 | sean-k-mooney | which is not really a good thing | |
| 13:07:45 | kashyap | sean-k-mooney: It's using the legacy "-drive" approach; and the modern one ("-blockdev") should fix it | |
| 13:08:00 | kashyap | sean-k-mooney: It's not an OpenStack issue | |
| 13:08:07 | sean-k-mooney | yep i know | |
| 13:08:22 | sean-k-mooney | and i also know we cant force libvirt to only use drive or blockdev | |
| 13:08:30 | sean-k-mooney | which is why we can workaournd it form nova | |
| 13:09:12 | sean-k-mooney | my point is for all deployments that cant use libvirt 6 there is no way for them to work around this | |
| 13:09:28 | sean-k-mooney | well excpet upgrade | |
| 13:09:45 | sean-k-mooney | anmyway i think the victoia cloud archive had 6.0.0 | |
| 13:10:04 | kashyap | Yeah; the whole backports / how far back should upstream support is a tricky thing | |
| 13:10:07 | sean-k-mooney | so im going to bump the version we use in devstack on the older branches | |
| 13:10:25 | kashyap | The answer is: "if you want such backported fixes", use an "enterprise" distro | |
| 13:10:35 | sean-k-mooney | well no | |
| 13:10:35 | kashyap | (So goes the argument) | |
| 13:10:49 | sean-k-mooney | the anser is that libvirt could actully maintain branches and do backports | |
| 13:10:57 | kashyap | Well, they do that | |
| 13:10:59 | sean-k-mooney | they dont which forces distros to do it | |
| 13:11:09 | kashyap | But how you have to backport is an upstream decision | |