| opendevreview | Steve Baker proposed openstack/nova master: Align ironic driver secure boot with other drivers https://review.opendev.org/c/openstack/nova/+/844243 | 02:08 |
|---|---|---|
| opendevreview | norman shen proposed openstack/nova master: Clear connection info if vol disconnected https://review.opendev.org/c/openstack/nova/+/845995 | 02:34 |
| opendevreview | Takashi Kajinami proposed openstack/os-vif master: Drop lower-constraints.txt and its testing https://review.opendev.org/c/openstack/os-vif/+/840020 | 04:47 |
| *** elodilles is now known as elodilles_pto | 07:04 | |
| gibi | good morning | 08:14 |
| Uggla | gibi, good morning. | 08:35 |
| * bauzas waves late here | 09:08 | |
| gibi | sean-k-mooney: another question, maybe you remember. Do we set the PciDevice.instance_uuid to the migration_uuid on the source host when the VM using the device is being migrated? | 10:37 |
| sean-k-mooney | i dont think so | 10:37 |
| sean-k-mooney | we dont need too | 10:37 |
| gibi | OK, then I look up running migrations for reshape | 10:37 |
| gibi | and pair them to PciDevs | 10:38 |
| gibi | as I have to heal the allocation for the running migrations too | 10:38 |
| sean-k-mooney | the instance uuid should be set to the instance uuid on both hosts | 10:38 |
| gibi | ack | 10:38 |
| gibi | that what I guessed | 10:38 |
| sean-k-mooney | i think the corralation is done via the migrate_data object which is only in memory | 10:39 |
| sean-k-mooney | although you can just look at the relevent host form the migration object | 10:39 |
| sean-k-mooney | to know which one it belongs too | 10:39 |
| sean-k-mooney | e.g migration vs instance | 10:39 |
| gibi | yeah something like that | 10:39 |
| sean-k-mooney | that reminds me we still do not use consumer types | 10:40 |
| sean-k-mooney | that is out of scope but ya | 10:40 |
| sean-k-mooney | are we going to have a reshape in the future that will move all migrations to the migration consumer type | 10:41 |
| gibi | we should have add that yes | 10:44 |
| sean-k-mooney | thats what i assuemd but i dont recall if the placment spec actully spoke about how nova or other porjects would use them once the feature was added | 10:45 |
| gibi | me neither | 10:45 |
| sean-k-mooney | so i was not sure if we woudl do a reshape or just stat using the consumer type for new migrations | 10:45 |
| gibi | I think reshape would be better | 10:46 |
| sean-k-mooney | and let it heal over time as old migration get compelte/aborted. | 10:46 |
| sean-k-mooney | it would be cleaner for sure | 10:46 |
| sean-k-mooney | but proably a nova manage command so that it does not have any impact on rolling upgrade | 10:46 |
| sean-k-mooney | although old nova will proably ignore the type so i might be over thinking it | 10:47 |
| sean-k-mooney | future us problems | 10:47 |
| gibi | yepp | 10:50 |
| gibi | \one more architectural difference for today: for pci it cannot be decided if reshape is needed without checking existing nova allocations of pci also exists in placement too. As during rolling upgrade new pci allocations can arrive to a compute without placmeent allocation | 10:53 |
| gibi | so for pci we will do periodic healing | 10:53 |
| gibi | instead of a one time reshape | 10:53 |
| sean-k-mooney | fun | 10:56 |
| sean-k-mooney | is that not the case for cpus? | 10:56 |
| sean-k-mooney | the reshape will be tied to the pci/repot_to_placement conf or whatever it was right | 10:57 |
| sean-k-mooney | so this will be skiped if that is not set | 10:58 |
| gibi | it seems for cpus we did not needed this | 11:10 |
| sean-k-mooney | im not really sure why it woudl be differnt | 11:11 |
| gibi | yes, the whole tracking and reshape code starts with an if not CONF.pci.report_in_placement: return | 11:11 |
| gibi | sean-k-mooney: for cpus we do two a_c queries to enforce allocation if placement has inventory | 11:12 |
| sean-k-mooney | oh the fallback query | 11:12 |
| gibi | and fall back to legacy query | 11:12 |
| gibi | yeah | 11:12 |
| sean-k-mooney | i mean we can do that for pci | 11:12 |
| sean-k-mooney | if we want too | 11:12 |
| sean-k-mooney | i guess that does nto really work the same if we use a prefilter | 11:13 |
| sean-k-mooney | we had to do some extra chagnes for the fallback | 11:13 |
| gibi | periodic healing feels less complex to me code wise | 11:14 |
| sean-k-mooney | ack | 11:14 |
| gibi | I also would like make the healing code accessible from nova-manage | 11:15 |
| gibi | healing / audit | 11:15 |
| gibi | basically the same code can tell if something is missing and also can fix it | 11:16 |
| gibi | or delete if there are overallocations in placement | 11:16 |
| sean-k-mooney | yep that makes sense too | 11:23 |
| sean-k-mooney | personally i think we should merge audit and heal by the way or at least move the delete allcoation logic form audit to heal | 11:24 |
| sean-k-mooney | audit is very very badly named | 11:25 |
| gibi | yepp | 11:25 |
| gibi | I agree | 11:25 |
| gibi | we need only one CLI to check and fix | 11:25 |
| sean-k-mooney | yep basicaly one command with a dry run mode | 11:25 |
| sean-k-mooney | that just prints the problems that would be fixed | 11:26 |
| sean-k-mooney | but does not actully do them, if you are happy drop --dry-run or add --apply whatever way we want to set the default | 11:26 |
| jkulik | may I ask, how do you run nova-manage? Do you have the config to access stuff "locally" or do you connect to some VM/container containing nova-api or something or do you have a special "manage" host/container for that? | 11:28 |
| sean-k-mooney | you normlaly ssh to one of your contolers | 11:28 |
| sean-k-mooney | and run it form there | 11:28 |
| sean-k-mooney | but you can run it locally with configs yes if you need too | 11:28 |
| sean-k-mooney | if you are using something like kolla you would do an exec into the contaienr to run it yes | 11:29 |
| jkulik | ok. thanks. always felt a little wrong to me. why does it have to be a CLI and not an admin api? | 11:29 |
| sean-k-mooney | the api process does not have access to everything that is needed to run it | 11:30 |
| sean-k-mooney | jkulik: im sure you dont really want to be sendign you db/rabit password over a rest api request in general too | 11:31 |
| opendevreview | Merged openstack/os-vif master: Drop lower-constraints.txt and its testing https://review.opendev.org/c/openstack/os-vif/+/840020 | 11:31 |
| sean-k-mooney | jkulik: there would be ways to have apis do similar things but you need to use nova-manage to bootstrap things like the db | 11:32 |
| jkulik | sean-k-mooney: you mean for setting up cells? otherwise, both are in the db | 11:32 |
| sean-k-mooney | doing offline db migrations | 11:32 |
| sean-k-mooney | openstack and nova in this case genreal requried all contoler process to agre on the db schema | 11:33 |
| jkulik | hm ... yeah, didn't think about those. fair point, that there are definitely commmands that can't go via API | 11:33 |
| sean-k-mooney | the cell info is generaly in the db yes but if you are using templated db/rabbit urls in the db the passwords come form the nova.config | 11:34 |
| jkulik | oh. I didn't know about that possibility | 11:34 |
| sean-k-mooney | https://docs.openstack.org/nova/latest/admin/cells.html#template-urls-in-cell-mappings | 11:35 |
| sean-k-mooney | jkulik: they are optional | 11:35 |
| sean-k-mooney | but they were created to make doing password rotation simplere with config tools like ansible | 11:35 |
| sean-k-mooney | since you just need to update the configs and the passward on the db | 11:36 |
| sean-k-mooney | that and to not store passwords in plain text in the db | 11:36 |
| jkulik | yeah, immediately wondering if we want that, too | 11:36 |
| jkulik | downstream I mean | 11:36 |
| sean-k-mooney | in which downstream | 11:37 |
| jkulik | I mean in our installations of Nova. sorry for the confusing wording | 11:37 |
| sean-k-mooney | tripleo uses it by defualt i think | 11:37 |
| jkulik | we have a helm-chart to deploy Nova | 11:37 |
| sean-k-mooney | ah ok | 11:37 |
| sean-k-mooney | i dont know if openstack ansible or kolla ever addopted it | 11:38 |
| sean-k-mooney | but ya its up to each installer | 11:38 |
| sean-k-mooney | gibi: just because i happen to be looking at the code do you knwo why we dont allwo you to plug in image_types backends using stevador extention points like we do for filteres? | 11:47 |
| sean-k-mooney | i just noticed it was a dict https://github.com/openstack/nova/blob/93a65f06df67ce39d65827692150c78013c7f6d5/nova/virt/libvirt/imagebackend.py#L1286-L1294= | 11:47 |
| gibi | I think nobody asked for it | 11:48 |
| gibi | also we removed a bunch of extension points in the past | 11:48 |
| gibi | so we might not want to add more | 11:48 |
| gibi | but technically we could add one | 11:49 |
| sean-k-mooney | ya i know proably more then we should have but that would be one way to allow people to play with a bfv backend and protype it. | 11:49 |
| sean-k-mooney | the image ABC is intneded to define the api https://github.com/openstack/nova/blob/93a65f06df67ce39d65827692150c78013c7f6d5/nova/virt/libvirt/imagebackend.py#L81= | 11:50 |
| sean-k-mooney | gibi: or for example add the ablity to use libvirt sotorage pools. | 11:51 |
| sean-k-mooney | although im relaly not sure how solid that interface actully is | 11:51 |
| gibi | but why this needs to be an extension why cannot be just proposed to nova as a backend? | 11:52 |
| sean-k-mooney | because if its an exstion we can easilly move backend we dont like out of tree | 11:53 |
| sean-k-mooney | but also because it seams liek a nice extion point ot have | 11:53 |
| sean-k-mooney | i was just wondering | 11:53 |
| jrosser_ | sean-k-mooney: OSA uses templated db url but there is a bug we hit https://github.com/openstack/openstack-ansible-os_nova/blob/master/tasks/nova_db_setup.yml#L58-L87 | 11:56 |
| gibi | extension point has a cost though, we cannot change the API freely | 11:56 |
| gibi | as that might break out of tree extensions | 11:57 |
| sean-k-mooney | yep | 11:59 |
| sean-k-mooney | gibi: by the way its a supper low priortiy right now but if i every get around to updating my black patch to the currnent 79 charater line lenght are you still interested in reviewing it | 12:47 |
| sean-k-mooney | i was just cleaning up some terminals and closed the one i was working on that in | 12:48 |
| sean-k-mooney | well one of them | 12:48 |
| sean-k-mooney | i still have it open in emacs | 12:48 |
| gibi | yes I stil think we should merge it on master with 79 lines | 12:49 |
| * sean-k-mooney since i ran out of memory the other day i tought it might be a good time to clean up my open windows | 12:49 | |
| sean-k-mooney | oh thats where i put the default chagne stuff | 12:51 |
| sean-k-mooney | i started that in vscode since i was using that to debug the repoducer | 12:51 |
| sean-k-mooney | i spent like 30 mins looking for it in differnt emacs and terminal windows | 12:51 |
| gibi | :D | 12:52 |
| sean-k-mooney | it also does not help that i have 4 copies of nova and i started workign on it in the one i reseve for quickly pulling down patches and testing them locally | 12:53 |
| sean-k-mooney | aka ~/repos/openstack/nova-3 | 12:53 |
| gibi | I started using git worktree so I can track where I my nova checkouts :D | 12:53 |
| gibi | s/I/are/ | 12:54 |
| sean-k-mooney | what is git worktree | 12:54 |
| gibi | you can have multiple working direktory for a single git repo | 12:54 |
| gibi | each directory can have a different version checked out | 12:54 |
| gibi | but all tight to the same local git repo | 12:54 |
| jkulik | loving git worktree for working on multiple things in parallel :) | 12:54 |
| sean-k-mooney | i normally do must of my dev on vms or my server so the local checkouts on my laptop are usually only for pep8/unit tests fixing | 12:55 |
| sean-k-mooney | gibi: oh ok i shoudl look into that | 12:55 |
| sean-k-mooney | similar concept but differnt approch to git-nit | 12:55 |
| sean-k-mooney | commit-ish | 12:56 |
| sean-k-mooney | hehe i like that | 12:56 |
| sean-k-mooney | so i coudl tie my nova-1 nova-2 and nova-3 repos togenter into one nova repo and use those folders as work dirs instead of full repos | 12:57 |
| sean-k-mooney | if im in a git work tree folder and i do git checkout or rebase ectra does it work like a normal repo? | 12:58 |
| sean-k-mooney | but only affecting that workign tree | 12:58 |
| gibi | yes | 12:59 |
| gibi | and you can aways say git worktree list to see where are your workdirs :D | 12:59 |
| sean-k-mooney | ok so i coudl have 2 rebases going on in differnt workign trees | 12:59 |
| gibi | I think so yes | 12:59 |
| sean-k-mooney | cool | 12:59 |
| sean-k-mooney | i dont do that often but sometimes if im pinged to respine X while working on y i will | 13:00 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (db) https://review.opendev.org/c/openstack/nova/+/831193 | 13:33 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (objects) https://review.opendev.org/c/openstack/nova/+/839401 | 13:33 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (drivers) https://review.opendev.org/c/openstack/nova/+/833090 | 13:33 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (api) https://review.opendev.org/c/openstack/nova/+/836830 | 13:33 |
| opendevreview | sean mooney proposed openstack/nova master: update default numa allocation strategy https://review.opendev.org/c/openstack/nova/+/846169 | 13:40 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/wallaby: fake: Ensure need_legacy_block_device_info returns False https://review.opendev.org/c/openstack/nova/+/843678 | 14:28 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/wallaby: Add a regression test for bug 1939545 https://review.opendev.org/c/openstack/nova/+/843702 | 14:28 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/wallaby: compute: Ensure updates to bdms during pre_live_migration are saved https://review.opendev.org/c/openstack/nova/+/843680 | 14:28 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/wallaby: fup: Make connection_info returned by CinderFixture unique per attachment https://review.opendev.org/c/openstack/nova/+/844594 | 14:28 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/wallaby: fup: Assert state of connection_info during LM rollback in func tests https://review.opendev.org/c/openstack/nova/+/844595 | 14:28 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (objects) https://review.opendev.org/c/openstack/nova/+/839401 | 14:53 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194 | 14:53 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (drivers) https://review.opendev.org/c/openstack/nova/+/833090 | 14:53 |
| opendevreview | ribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (api) https://review.opendev.org/c/openstack/nova/+/836830 | 14:53 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Report PCI inventory to placement basics https://review.opendev.org/c/openstack/nova/+/846187 | 15:27 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Report PCI inventory to placement basics https://review.opendev.org/c/openstack/nova/+/846187 | 15:30 |
| dansmith | does anyone know of a recentish change to nova that might have inflated n-cpu memory footprint? | 15:51 |
| sean-k-mooney | not that im aware of that has merged | 16:00 |
| sean-k-mooney | dansmith: gibi has a change that adds a trivial cache for speeding up numa toplogy computation | 16:01 |
| sean-k-mooney | but i dont think that has merged | 16:01 |
| sean-k-mooney | dansmith: are you trying to track down a memory increase | 16:02 |
| dansmith | maybe yeah | 16:02 |
| sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/845896 but its not merged so its not that | 16:03 |
| dansmith | okay, so it's not a regression, or at least, not a recent one | 16:04 |
| dansmith | n-cpu memory usage after a single-node run is ~500m, but after a multinode one, it's 1.5G to 2.5G | 16:05 |
| dansmith | so I wonder if we're buffering something in memory due to live migration or something | 16:05 |
| sean-k-mooney | do you have swap awailable | 16:05 |
| dansmith | what does it matter? it' | 16:05 |
| dansmith | it's not OOMing, we're just noticing it's much larger | 16:06 |
| sean-k-mooney | just tha ti saw high memory usage in the past when swap was disabled | 16:07 |
| sean-k-mooney | that did not happen when it was available | 16:07 |
| sean-k-mooney | but i guess you have the saem config in singel vs multinode | 16:07 |
| dansmith | yeah, these are CI workers | 16:07 |
| sean-k-mooney | so is it that somehow adding a second compute node increase memory usage on the first | 16:07 |
| sean-k-mooney | like if you enable a multi node install but idsable nova-cpu on the subnode | 16:08 |
| sean-k-mooney | does it still happen | 16:08 |
| dansmith | I was thinking more like in live migration we read in the configdrive to memory or something | 16:08 |
| dansmith | you know how python increases the water mark but basically never decreases it | 16:08 |
| sean-k-mooney | hum ok maybe | 16:09 |
| sean-k-mooney | you could confirm that by disabling move operations tests | 16:09 |
| sean-k-mooney | the config drive is pretty small but maybe | 16:09 |
| dansmith | just an example | 16:09 |
| sean-k-mooney | ya im jsut trying to think what else is like that | 16:10 |
| sean-k-mooney | is the memory usage the same on both hosts? | 16:10 |
| dansmith | I don't collect the other so dunno | 16:10 |
| sean-k-mooney | would it be hard to add that | 16:13 |
| sean-k-mooney | do you have the link to the ci job by the way | 16:14 |
| dansmith | it's all the jobs, there's no need to look at one specifically | 16:16 |
| dansmith | I thought it was recent, but I compared to some old snaps I had and they were high then too, but only for multinode | 16:16 |
| gibi | sean-k-mooney, bauzas, artom: on master we still reject the evacuate request if the instance is in transient state (i.e. powering-off) https://paste.opendev.org/show/bQphEfOf8eLBnM6XmleQ/ | 16:36 |
| gibi | so for me this seem like a valid request to evacuate the instance in this state | 16:37 |
| sean-k-mooney | its not safe nessisarly to do by default | 16:38 |
| gibi | even if the compute is forced down? | 16:39 |
| sean-k-mooney | if its force down its oke | 16:39 |
| sean-k-mooney | but only because | 16:39 |
| sean-k-mooney | the operator is | 16:39 |
| sean-k-mooney | promising they have fenced it | 16:39 |
| gibi | yepp | 16:39 |
| sean-k-mooney | but normlaly evacuate without force down would not be safe | 16:39 |
| gibi | btw, reset-state --active helps https://paste.opendev.org/show/bVI7D8H5g9Oqjjo4rKfk/ | 16:39 |
| sean-k-mooney | we cant tell that the vm is not running | 16:39 |
| gibi | yepp in generate evacuate without fencing is unsafe in non transient states too | 16:40 |
| gibi | s/generate/general/ | 16:40 |
| sean-k-mooney | so ya if we check both then we can ignore the task state | 16:40 |
| sean-k-mooney | *both-> force-down | 16:40 |
| sean-k-mooney | so question | 16:40 |
| sean-k-mooney | does the decorator support ignoring task state | 16:40 |
| gibi | so on master I'm OK to ignore the task state | 16:42 |
| gibi | downstream I would suggest the customer to use the reset-state, so no code changes is needed there | 16:42 |
| sean-k-mooney | reset_state only resets vm state not task state right | 16:43 |
| sean-k-mooney | or dose it force task_state=None | 16:43 |
| artom | IIRC it can do both | 16:43 |
| sean-k-mooney | well you cant reset taskstate with it | 16:43 |
| sean-k-mooney | configurably | 16:43 |
| sean-k-mooney | i.e. reset-state vm-sate=active task-state=none | 16:44 |
| sean-k-mooney | but i dont know if task-state=none | 16:44 |
| sean-k-mooney | is hardcoded internally | 16:44 |
| gibi | sean-k-mooney: reset-state resets the task state too | 16:45 |
| sean-k-mooney | then ya it should be good | 16:45 |
| sean-k-mooney | it would be nice if we could add task-state to the api in the futrue | 16:46 |
| sean-k-mooney | https://github.com/openstack/nova/blob/50fdbc752a9ca9c31488140ef2997ed59d861a41/nova/api/openstack/compute/schemas/reset_server_state.py#L15 | 16:46 |
| sean-k-mooney | but for this case we shoudl be good | 16:46 |
| sean-k-mooney | https://github.com/openstack/nova/blob/50fdbc752a9ca9c31488140ef2997ed59d861a41/nova/api/openstack/compute/admin_actions.py#L77-L78= | 16:47 |
| gibi | all good | 16:48 |
| gibi | :)\ | 16:48 |
| sean-k-mooney | gibi: are you going to file an upstream bug for the transient state | 16:48 |
| gibi | sure I can I have the repro ready. But I won't assign it to myself to fix it :) | 16:49 |
| gibi | at least not right now | 16:49 |
| gibi | sean-k-mooney, artom, bauzas https://bugs.launchpad.net/nova/+bug/1978983 | 16:58 |
| gibi | sean-k-mooney: btw, I added the pci inventory reporting to the resource tracker level https://review.opendev.org/c/openstack/nova/+/846187 it does not need to be in the virt layer so I did not force to it | 17:00 |
| artom | Nice | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: fake: Ensure need_legacy_block_device_info returns False https://review.opendev.org/c/openstack/nova/+/843950 | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: Add a regression test for bug 1939545 https://review.opendev.org/c/openstack/nova/+/843951 | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: compute: Ensure updates to bdms during pre_live_migration are saved https://review.opendev.org/c/openstack/nova/+/843952 | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: fup: Make connection_info returned by CinderFixture unique per attachment https://review.opendev.org/c/openstack/nova/+/844606 | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: fup: Assert state of connection_info during LM rollback in func tests https://review.opendev.org/c/openstack/nova/+/844607 | 17:00 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: functional: Use tempdir for CONF.instances_path https://review.opendev.org/c/openstack/nova/+/846204 | 17:00 |
| sean-k-mooney | gibi: cool just triaged it as medium since you have repoduced it and there is a workaround | 17:03 |
| gibi | sean-k-mooney: thanks | 17:03 |
| sean-k-mooney | by the way by doing it at the compute manager level that shoudl work for all virt drivers which is nice | 17:03 |
| gibi | yepp that also a + | 17:04 |
| sean-k-mooney | we will likely only test with libvirt but if someone was to test with powervm and it worked they could update the docs | 17:04 |
| gibi | yes | 17:04 |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (1/3) https://review.opendev.org/c/openstack/nova/+/846207 | 17:11 |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (2/3) https://review.opendev.org/c/openstack/nova/+/846208 | 17:11 |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (3/3) https://review.opendev.org/c/openstack/nova/+/846209 | 17:11 |
| geguileo | dansmith: sean-k-mooney ^ Those are the test patches to see if we can figure something out... | 17:12 |
| geguileo | fist is doing nothing, next is trimming malloc memory, last is trimming and setting malloc arenas | 17:12 |
| * geguileo facepalms hard, as I seem to not know how to change .zuul | 17:13 | |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (1/3) https://review.opendev.org/c/openstack/nova/+/846207 | 17:14 |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (2/3) https://review.opendev.org/c/openstack/nova/+/846208 | 17:14 |
| opendevreview | Gorka Eguileor proposed openstack/nova master: DNM: Testing memory usage of n-cpu (3/3) https://review.opendev.org/c/openstack/nova/+/846209 | 17:14 |
| dansmith | geguileo: I believe no human has ever gotten a zuul config change correct on the first try | 17:16 |
| sean-k-mooney | so you are directly calling into mallac to free memory | 17:20 |
| sean-k-mooney | thats interesting | 17:20 |
| sean-k-mooney | sory forgot the ... | 17:20 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: functional: Use tempdir for CONF.instances_path https://review.opendev.org/c/openstack/nova/+/846204 | 17:56 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: Add a regression test for bug 1939545 https://review.opendev.org/c/openstack/nova/+/843951 | 17:56 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: compute: Ensure updates to bdms during pre_live_migration are saved https://review.opendev.org/c/openstack/nova/+/843952 | 17:56 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: fup: Make connection_info returned by CinderFixture unique per attachment https://review.opendev.org/c/openstack/nova/+/844606 | 17:56 |
| opendevreview | Artom Lifshitz proposed openstack/nova stable/ussuri: fup: Assert state of connection_info during LM rollback in func tests https://review.opendev.org/c/openstack/nova/+/844607 | 17:56 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Report PCI inventory to placement basics https://review.opendev.org/c/openstack/nova/+/846187 | 18:29 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Extend device_spec with resource_class and traits https://review.opendev.org/c/openstack/nova/+/846218 | 18:29 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Ignore PCI devs with physical_network tag https://review.opendev.org/c/openstack/nova/+/846219 | 18:29 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!