Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-10-24
15:16:30 bauzas thanks for the review
15:16:40 efried bauzas: But just one of them :)
15:17:09 dansmith bauzas: I'll add it to the queue
15:17:15 openstackgerrit Matt Riedemann proposed openstack/nova master: Add restrictions on updated_at when getting migrations https://review.openstack.org/607798
15:17:16 mdbooth sean-k-mooney: However, I think I didn't demonstrate that mechanically updating all uses of placement_context_manager() is pretty easy.
15:17:16 openstackgerrit Matt Riedemann proposed openstack/nova master: Add restrictions on updated_at when getting instance action records https://review.openstack.org/607801
15:17:16 openstackgerrit Matt Riedemann proposed openstack/nova master: Document restrictions on changes-since/before when listing servers https://review.openstack.org/613070
15:17:27 mdbooth s/didn't/did/
15:17:33 mdbooth That was a weird typo
15:20:07 sean-k-mooney mdbooth: ya i suspected that woudl be easy to do but getting the new decorator correct is the tricky bit. anyway the more i talk about the less time i spend doing it ill have the patch up in a ffew minutes
15:25:09 bauzas dansmith: heh, np
15:50:48 openstackgerrit Balazs Gibizer proposed openstack/nova master: Consider allocations invovling child providers during allocation cleanup https://review.openstack.org/606050
15:50:48 openstackgerrit Balazs Gibizer proposed openstack/nova master: Reject forced move with nested source allocation https://review.openstack.org/605785
15:50:49 openstackgerrit Balazs Gibizer proposed openstack/nova master: Run negative server moving tests with nested RPs https://review.openstack.org/604125
15:50:49 openstackgerrit Balazs Gibizer proposed openstack/nova master: Handle allocations consuming only from the child RPs https://review.openstack.org/608298
15:51:34 gibi mriedem, efried, jaypipes: I have fixed up the use-nested-allocation-candidates series ^^
15:53:00 efried gibi: Cool, I'm sure it's perfect now.
15:53:11 openstackgerrit Matt Riedemann proposed openstack/python-novaclient stable/rocky: Follow up "Fix up userdata argument to rebuild" https://review.openstack.org/613086
15:53:33 gibi efried: :)
15:56:13 jaypipes gibi: thx gibi
15:57:30 openstackgerrit Matt Riedemann proposed openstack/python-novaclient stable/queens: Fix up userdata argument to rebuild. https://review.openstack.org/613090
15:57:31 openstackgerrit Matt Riedemann proposed openstack/python-novaclient stable/queens: Follow up "Fix up userdata argument to rebuild" https://review.openstack.org/613091
16:00:27 openstackgerrit Daniel Abad proposed openstack/nova master: Fix ironic client ironic_url deprecation warning https://review.openstack.org/611872
16:07:08 pvc Hi sean-k-mooney my problem is i cannot run nvidia x settings on my instance
16:07:27 pvc https://docs.nvidia.com/grid/latest/grid-licensing-user-guide/index.html#licensing-grid-vgpu
16:10:01 sean-k-mooney the docs have an advanced section that shouw how to set the liceing info using an config file on linux or the registry on windows
16:16:29 pvc Hi sean-k-mooney can i use conf for adding a license right?
16:16:42 openstackgerrit Dan Smith proposed openstack/nova master: Always read-deleted=yes on lazy-load https://review.openstack.org/575190
16:18:17 dansmith melwitt: the down cell series could use some review if you have time. Everything up to the api change (which I orphaned while working on it) should be passing tests now
16:18:48 bauzas pvc: I pointed you to the nvidia guest licensing documentation this morning
16:19:22 bauzas pvc: https://docs.nvidia.com/grid/6.0/grid-licensing-user-guide/index.html#licensing-grid-software-linux-config-file
16:21:15 melwitt dansmith: thanks for the heads up, I'll go through it. I was also thinking about the handling of quota behavior in the presence of down cells. I don't think we have a patch for that yet. if not, I can look at proposing that on top of the api change
16:21:41 dansmith yep, not that I know of
16:22:27 melwitt ack
16:24:09 cdent sean-k-mooney: I built a place to store wood for the fire. good break. I saw mdbooth abandoned his thing, so where does stuff stand now?
16:25:21 sean-k-mooney cdent: i was in meetings so and some other stff so ill have the simple booling flag version up soon
16:26:33 openstackgerrit Merged openstack/nova-specs master: Re-proposes multiple vGPU types in libvirt https://review.openstack.org/602474
16:26:34 mdbooth cdent: Yeah, having thought about that again, I think it would need a different oslo.db api to do that. The decorator is returned by the object we want to replace, so there's no getting round that.
16:35:42 melwitt bauzas: just noticed another thing for the vgpu spec follow up https://review.openstack.org/#/c/602474/2/specs/stein/approved/vgpu-stein.rst@11
16:35:47 melwitt bp name
17:09:52 openstackgerrit Matt Riedemann proposed openstack/nova master: Add functional recreate test for bug 1799727 https://review.openstack.org/613115
17:09:52 openstack bug 1799727 in OpenStack Compute (nova) "CPU_Allocation_Ratio from nova.conf doesn't update exisiting providers" [Undecided,Confirmed] https://launchpad.net/bugs/1799727
17:13:29 openstackgerrit Jan Gutter proposed openstack/os-vif master: Update port profile unit tests in host_info https://review.openstack.org/610636
17:14:16 openstackgerrit Matt Riedemann proposed openstack/nova master: Add functional recreate test for bug 1799727 https://review.openstack.org/613115
17:14:18 openstack bug 1799727 in OpenStack Compute (nova) "CPU_Allocation_Ratio from nova.conf doesn't update exisiting providers" [High,Confirmed] https://launchpad.net/bugs/1799727
17:25:36 cfriesen jaypipes: stephenfin: regarding the "show server numa topology" spec, are you okay with showing the *guest* topology for regular users if we clean up the various issues you raised in the spec?
17:27:00 sean-k-mooney cfriesen: provdied the show numa toplogy spec does not show and host topology info they i think its fine
17:27:57 sean-k-mooney cfriesen: if you want it to show how the virtual topology is map to a hosts phyisical toplogy then that would be admin only
17:31:28 cfriesen sean-k-mooney: agreed. I think showing the "expected" host details to the admin would be useful, since we've run into cases where expected didn't match actual. :)
17:33:41 sean-k-mooney cfriesen: it should not upstream. the intel nfv ci actully ssh's into the host that the vm is running on and validates its pinned correctly
17:34:44 cfriesen sean-k-mooney: live migration
17:34:47 sean-k-mooney cfriesen: but for an admin yes it could be useful when debuging
17:35:15 sean-k-mooney cfriesen: what about it i said we validated it was pinned as nova told it too
17:35:15 cfriesen (at least until the patch goes in to fail the live migration if there's a numa topology)
17:35:27 sean-k-mooney i did not say nova pinned it correctly
17:36:10 sean-k-mooney cfriesen: ya on that i have asked stephen to make that condional and off by default
17:36:12 cfriesen sean-k-mooney: we ran into some bugs during aborted/failed operations
17:37:01 openstackgerrit Merged openstack/nova stable/rocky: Fix up compute rpcapi version for pike release https://review.openstack.org/612561
17:37:26 sean-k-mooney cfriesen: i know of at least on production largscale deployment that uses ovs-dpdk which means the guest have hugepages and numa toplogy that uses livemigration
17:38:22 sean-k-mooney it is still true that live migration can fail because there are not enough free hugepges on the numa node but the failure rate was low enouh that they were happy to contiue to use it
17:39:38 sean-k-mooney mainly since they could just specify a host that they knew would fit the instance
17:40:52 jaypipes cfriesen: I'm not thrilled about it, no..
17:41:22 openstackgerrit Elod Illes proposed openstack/nova master: Transform scheduler.select_destinations notification https://review.openstack.org/508506
17:41:40 sean-k-mooney jaypipes: even if its just the computed toplogy form the flavor+image with no host info?
17:42:01 cfriesen jaypipes: so currently an end-user can't tell their topology without logging into the guest and checking it. if they're using a per-user keypair, other users in the same tenant can't see what the topology is.
17:42:16 dansmith cfriesen: what's the use case for that though?
17:42:22 sean-k-mooney cfriesen: well they can they can look at the flavor and image metadata
17:42:38 cfriesen sean-k-mooney: not all clouds allow end users to see flavor extra specs
17:43:04 sean-k-mooney cfriesen: wait they dont? how do you know what the falvor does without that info
17:43:48 dansmith sean-k-mooney: historically those were admin only
17:43:56 cfriesen dansmith: for an admin it's useful for showing what nova expects the virt/phys mapping to be, which can then be checked against the actual mapping on the hypervisor.
17:44:20 sean-k-mooney dansmith: huh ok i guess i just always am an admin so never noticed
17:44:45 cfriesen for a normal user, it's useful in the same way knowing how many cpus or how much ram your instance has is useful
17:44:58 dansmith cfriesen: you mean it's useful for an admin to make sure nova is doing the thing it expects? that seems like a weak case to me..
17:45:37 dansmith cfriesen: but .. the user can get that from the guest if they're the user. I just have a hard time understanding what they can do with that info from just the API, other than maybe complain, or notice that it changed when their admin migrates them
17:46:10 sean-k-mooney cfriesen: is any of this stuff already in the metadata api?
17:46:26 cfriesen dansmith: only a user with a suitable keypair can login to the guest. other users in the same tenant can't.
17:46:36 cfriesen or at least might not be able to
17:46:40 dansmith cfriesen: right, it's that case I don't get
17:47:07 dansmith cfriesen: like, if I can log into the guest, what does it matter what the topology is?
17:47:39 dansmith I mean I can come up with completely synthetic reasons, but they're exceedingly weak, which is what I said above
17:49:19 dansmith sorry.. "can't log into the guest"
17:54:18 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Update allocation_ratios in placement inventory if config changes https://review.openstack.org/613126
17:55:33 cfriesen most of the uses that we added it for were admin-level, admittedly. Like figuring out why something is having a hard time scheduling on a migration or showing the expected virt/phys mapping. For an end user it's really just about showing all the available information about the instance and making it so they don't have to jump through hoops to get it.
17:56:30 cdent "making it so they don't have to jump through hoops to get it" <- that ought to be compelling enough?
18:00:27 openstackgerrit Gaudenz Steinlin proposed openstack/nova master: Extend volume for libvirt network volumes (RBD) https://review.openstack.org/613039
18:01:34 sean-k-mooney cdent: its 3 command to 1 but if some clouds hide flavor extra spec then i guess maybe they cant run the 3 commands
18:01:55 sean-k-mooney cfriesen: had you also planned to show cpu topplogy or just numa topology
18:02:51 sean-k-mooney cfriesen: as we both know they can and usually are very different by defualt on openstack
18:03:16 openstackgerrit Jay Pipes proposed openstack/nova master: quota: remove unused code https://review.openstack.org/613127
18:03:17 openstackgerrit Jay Pipes proposed openstack/nova master: quota: remove unused Quota driver methods https://review.openstack.org/613128
18:03:17 openstackgerrit Jay Pipes proposed openstack/nova master: quota: remove QuotaDriver.destroy_all_by_project() https://review.openstack.org/613129
18:03:18 openstackgerrit Jay Pipes proposed openstack/nova master: quota: remove default kwarg on get_class_quotas() https://review.openstack.org/613130
18:04:29 jaypipes melwitt, dansmith: some cleanups of the quota system ^^
18:05:28 cfriesen sean-k-mooney: we currently show memory size, page size, and which guest CPUs are associated with each guest numa node. showing virtual CPU topology (sockets/cores/threads) would be a lot trickier since that's not in the nova DB.
18:06:12 sean-k-mooney well it is if set in the flavor or image else it up to the virt driver
18:06:15 jaypipes melwitt, dansmith: more patches on the way but those are a good first chunk of removing cruft
18:06:50 sean-k-mooney cfriesen: so if we were going this route it would be nice to include it if set in image or flavor
18:07:36 cfriesen sean-k-mooney: don't we have scenarios where we say "max cpus per socket"? in that case only the virt driver knows the actual number
18:13:42 sean-k-mooney cfriesen: yes but we can also say 2 cpus per socket instead of max

Earlier   Later