Thursday, 2023-12-14

opendevreviewMerged openstack/nova master: Use SDK for deprecated baremetal proxy API  https://review.opendev.org/c/openstack/nova/+/86779600:07
opendevreviewTakashi Kajinami proposed openstack/nova master: Remove deprecated [api] use_forwarded_for  https://review.opendev.org/c/openstack/nova/+/90333901:01
opendevreviewNobuhiro MIKI proposed openstack/nova master: scheduler: Request COMPUTE_ADDRESS_SPACE_* traits  https://review.opendev.org/c/openstack/nova/+/89576102:31
opendevreviewOpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/nova/+/90342703:31
opendevreviewTakashi Kajinami proposed openstack/nova master: Remove deprecated [api] use_forwarded_for  https://review.opendev.org/c/openstack/nova/+/90333905:41
gibiJayF: Done08:11
bauzasgibi: sean-k-mooney: it would be nice if you could review my bugfix series https://review.opendev.org/q/topic:%22bug/2041519%2208:22
bauzasit would also be nice if cores could look at my mdev live-migration spec https://review.opendev.org/c/openstack/nova-specs/+/90063610:10
bauzaswow10:17
noonedeadpunkhey there! I have quite "trivial" question about limit_tenants_to_placement_aggregate / placement_aggregate_required_for_tenants / AggregateMultiTenancyIsolation things just to confirm I understand that correctly.10:37
noonedeadpunkSo basically "user story" is to make set of computes be available only for specific tenant, meaning that it should be able to spawn instances _only_ on that aggregate, while all other tenants should be able to spawn anywhere _except_ this aggregate10:38
bauzasnoonedeadpunk: shit, I need to leave in a sec10:38
noonedeadpunkAm I right that I should then use limit_tenants_to_placement_aggregate: true, placement_aggregate_required_for_tenants: false and ignore AggregateMultiTenancyIsolation10:39
bauzasthere are multiple ways to support tenancy limitations10:39
noonedeadpunkOr, use AggregateMultiTenancyIsolation but then add another property and set of flavors for this tenant?10:39
bauzaseither by the filter or by our pre-filters10:39
bauzasnoonedeadpunk: there is another change from sahid related to this https://review.opendev.org/c/openstack/nova/+/89651210:41
* bauzas disappears for a couple of mins10:41
noonedeadpunkI need just 1 tenant to be isolated, so it shouldn;t be an issue...10:42
noonedeadpunksure...10:42
noonedeadpunkwill still write a question for the future :)10:42
noonedeadpunkSo reading description for placement_aggregate_required_for_tenants it made me think, that using placement will limit tenant to the aggregate, so won't allow to escape these computes, but will allow others to use them10:43
noonedeadpunkOr maybe I need both limit_tenants_to_placement_aggregate and AggregateMultiTenancyIsolation? Then on pre-filter THE tenant will get only suggestion for the aggregate, and then filter will cut down all rest tenants to be able to spawn there?10:44
opendevreviewStephen Finucane proposed openstack/nova master: Bump hacking version  https://review.opendev.org/c/openstack/nova/+/90352910:55
opendevreviewStephen Finucane proposed openstack/nova master: Resolve mypy error  https://review.opendev.org/c/openstack/nova/+/90353010:55
gibibauzas: I will try...10:56
opendevreviewStephen Finucane proposed openstack/nova master: tox: Use pre-commit for pep8 target  https://review.opendev.org/c/openstack/nova/+/89622710:57
opendevreviewStephen Finucane proposed openstack/nova master: pre-commit: Add mypy  https://review.opendev.org/c/openstack/nova/+/89622810:57
bauzasgibi: no worries, as you can11:12
opendevreviewMerged openstack/nova master: tests: Use clearer syntax for empty generator  https://review.opendev.org/c/openstack/nova/+/90307611:18
dvo-plvsean-k-mooney, thanks, it works with venv, but I can not figure out how it works previously, couple days ago12:40
opendevreviewStephen Finucane proposed openstack/nova master: docs: Further clarifications to the SG doc  https://review.opendev.org/c/openstack/nova/+/90367512:57
stephenfinsean-k-mooney: per our discussion ^12:57
bauzasgibi: want to ship your recent backport into Antelope? I was asked to +1 https://review.opendev.org/c/openstack/releases/+/899603 13:22
bauzasI think I'll release first the antelope reelase and then we will create another stable release for https://review.opendev.org/c/openstack/nova/+/90355313:24
gibibauzas: left feedback on the mdev live migration series13:31
bauzasgibi: <313:31
bauzasgibi: replied https://review.opendev.org/c/openstack/nova-specs/+/90063613:42
bauzasyou asked a very good question about the conductor option13:42
bauzasI already thought about all the possibilities but I don't know which one is the better13:42
bauzasand I also tried to explain you why and how we need a libvirtdriver dict 13:43
bauzasanother possibility instead of an internal dict would be to persist *something* *somewhere* about instances/mdevs13:44
bauzaseither in DB or in some file13:44
bauzasI know sean-k-mooney has concerns about the fact we check the usage by looking at the guest XMLs13:44
bauzas(I mean, if we're about persisting anything, I would way prefer to do it in some file like /var/lib/instances rather than with our Nova DB, for multiple reasons, one being I'm afraid of all the possible wrong values we would write in the DB that would mean to be fixed by hand)13:46
sean-k-mooneybauzas: i have a personal goal of not requiring persitent xmls at all in the future14:08
sean-k-mooneyi want nova to be able to recreate a vm evne ifn the /etc/libvirt/qemu directiory is deleted14:08
sean-k-mooneyi would much prefer to use the db but /var/lib/instances is much better then what we have today14:09
sean-k-mooneybauzas: if we coudl converge the pci tracker and medev code paths into a common device tracker that would be awsome in my view but i dont think that is goign to happen near term14:10
bauzassean-k-mooney: sorry in a meeting, let's discussing in 10-ish14:18
bauzasdiscuss*14:18
*** haleyb|out is now known as haleyb14:24
bauzassean-k-mooney: back, readinh14:25
bauzassean-k-mooney: sure, tbc, lemme explain why we're discussing it now : gibi is wondering why we need an internal dict to "persist" which mdevs are taken for live-migration (before the target guest runs with a domain)14:26
bauzasso I was just offering to persist some 'mdevs' file in the related /var/lib/instances/<inst_uuid> directory that would tell 'yo, those are the mdevs I use'14:27
bauzasbut there be dragon14:28
bauzas(I'm pretty sure that a domain is created on target's /var/lib/instances as soon as we start the live-migration)14:28
opendevreviewMerged openstack/nova master: Remove Ironic client wrapper  https://review.opendev.org/c/openstack/nova/+/86779714:28
opendevreviewMerged openstack/nova master: Remove unnecessary aliasing  https://review.opendev.org/c/openstack/nova/+/86779814:28
opendevreviewMerged openstack/nova master: Use real SDK objects in tests  https://review.opendev.org/c/openstack/nova/+/86779914:29
bauzaswow the gate sounds definitely better :)14:29
bauzas(tbh, what I said about writing a file in /var/lib/instances per instance dir could be a problem with shared storage, or not, depending on whether we are able to say "look, this mdev doesn't exist, I'm gonna recreate it"14:31
sean-k-mooneywe can always nest it in a $hostname folder if needed14:38
bauzassean-k-mooney: say I have a magical wand, what would be your preference ? using an internal dict like I wrote in the spec or persist some file in /var/lib/instances/<inst> ?14:53
bauzasthe latter would require me to update the spec but I can live with that14:53
bauzas(this wouldn't impact the current behaviour which would be to lookup the domain definitions, this is just additive either way)14:54
bauzasif we decide later to use that file too for mdevs we spawn, then we would eventually stop to lookup the domain XMLs14:55
bauzasthis is Christmas time, make a wish.14:55
bauzasgibi: sean-k-mooney: ^14:55
bauzas(note : I don't know *yet* how to implement a persistent file but I can arrange that by remembering the service uuid file thing14:57
gibi> we use the internal dict for persisting which mdevs are already used for live-migration for making sure that other instances being created in the target compute wouldn't take them while we live-migrate.15:09
gibiOK so this is basically a lock between the instances15:09
gibiso that again resource tracker territory. But I got it that it is too big of a move 15:09
gibiso I drop my question about persistence15:10
gibian in memory dict is OK to me15:10
bauzasfair enough15:11
JayFThanks gibi \o/ was quite a gift to wake up to the rest of that chain being not only approved but through the gate!15:11
bauzasgibi: so we only have one open question about the conductor conf option15:12
bauzasgibi: see my comment about it and all the alternatives15:12
gibiJayF: it is almost Christmas anyhow :)15:13
gibibauzas: I'm on it15:13
bauzasthanks15:13
JayFLet me rebase my ironic<>nova driver bugfix and I'll add something else to my list ;)15:13
gibi:)15:13
gibi> We could avoid the pre-flight check that adds a conductor option and just15:25
gibiassume to test the libvirt versions and the types during the pre-livemigration15:25
gibiconductor checks that claim the resources.15:25
gibibauzas: does it mean we can do all our checks in pre-livemigration without the extra conductor option?15:26
gibiif so then I vote for not having a conductor option and the the pre-livemigration do the checking15:26
gibipre-livemigration is there for many other checks like cpu compatibility15:27
gibibauzas: ^^15:28
*** jamesdenton_ is now known as jamesdenton15:37
opendevreviewribaudr proposed openstack/nova master: Reproducers for bug 1869804  https://review.opendev.org/c/openstack/nova/+/87777215:39
opendevreviewribaudr proposed openstack/nova master: Fix [backport]: Live migrating to a host with cpu_shared_set configured will now update the VM's configuration accordingly.  https://review.opendev.org/c/openstack/nova/+/87777315:39
opendevreviewribaudr proposed openstack/nova master: Fix: Live migrating to a host with cpu_shared_set configured will now update the VM's configuration accordingly.  https://review.opendev.org/c/openstack/nova/+/90370615:39
bauzasgibi: cool with me so15:43
bauzasI'll doublecheck with the code if that would work, since we'll go to the target first 15:43
gibibauzas: ack15:58
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: scheduler: AggregateMultitenancyIsolation to support unlimited tenant  https://review.opendev.org/c/openstack/nova/+/89651215:58
opendevreviewMerged openstack/nova stable/2023.1: [pwmgmt]ignore missin governor when cpu_state used  https://review.opendev.org/c/openstack/nova/+/90355316:49
opendevreviewMerged openstack/nova master: Remove outdated comment about allocation ratios  https://review.opendev.org/c/openstack/nova/+/90024216:50
opendevreviewPierre Riteau proposed openstack/nova stable/2023.2: Remove outdated comment about allocation ratios  https://review.opendev.org/c/openstack/nova/+/90368416:55
bauzasgibi: doh, we missed the target for releasing your bugfix shortly by 1 hour17:29
gibibauzas: now worries17:36
gibibauzas: that is not a blocker until we start testing with cpu_dedicated_set17:36
opendevreviewJay Faulkner proposed openstack/nova master: [ironic] Partition & use cache for list_instance*  https://review.opendev.org/c/openstack/nova/+/90083120:56

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!