Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2020-10-02
17:54:46 sean-k-mooney you could have moved it to triaged too
17:55:39 sean-k-mooney stephenfin: does mixed cpus support numa at all
17:56:45 sean-k-mooney we shoudl be able to test this with whitebox by the way
17:56:57 sean-k-mooney we can test it with a functional test too
17:58:01 sean-k-mooney stephenfin: thats failing because we are not tracking the numa affinity fo the shared cores yes
18:04:38 sean-k-mooney ah i see the fixt thats subtle
18:11:39 sean-k-mooney stephenfin: there is more legecy debt there
18:11:52 sean-k-mooney stephenfin: the cpu toplogy is not per numa node
18:11:54 sean-k-mooney its per vm
18:12:07 sean-k-mooney so we should not have a toplogy filed in the instance cell at all
18:13:13 sean-k-mooney so like the pagesize we should be pulling that field out of the instance numa cell object
18:14:39 sean-k-mooney both of these https://github.com/openstack/nova/blob/master/nova/objects/instance_numa.py#L79-L81 should be removed
18:15:08 sean-k-mooney and the cpu_thread_policy
18:16:11 sean-k-mooney they coudl be moved to the InstanceNUMATopology object i guess
18:16:31 sean-k-mooney although they are not really realted to numa but it would be more correct
18:16:55 sean-k-mooney stephenfin: can you add a todo to remove them
18:24:03 sean-k-mooney stephenfin: for what its worth i dont think we need the siblings field on the instance_cell object either
18:24:26 sean-k-mooney i think we only ever use teh siblings proerty on the host cell object not the property ihn the instnace cell
18:24:34 sean-k-mooney at least based on http://codesearch.openstack.org/?q=siblings&i=nope&files=&repos=openstack/nova
18:24:39 sean-k-mooney its not obvious if we do
18:29:07 sean-k-mooney the inital implemenation was quite bad at stashing things in the instnace cell object for convenince hten actully ensuign we only had one souce or truth
#openstack-nova - 2020-10-03
02:41:45 openstackgerrit melanie witt proposed openstack/nova master: Initialize global data separately and run_once in WSGI app init https://review.opendev.org/733627
04:53:07 openstackgerrit melanie witt proposed openstack/nova master: Initialize global data separately and run_once in WSGI app init https://review.opendev.org/733627
06:03:27 openstackgerrit Hemanth Nakkina proposed openstack/nova master: Update pci stat pools based on PCI device changes https://review.opendev.org/749175
12:18:52 openstackgerrit Lee Yarwood proposed openstack/nova master: bindep: Install python3 and python3-devel on CentOS 8 and Fedora https://review.opendev.org/755928
12:21:01 openstackgerrit Lee Yarwood proposed openstack/nova master: bindep: Install python3 and python3-devel on CentOS 8 and Fedora https://review.opendev.org/755928
#openstack-nova - 2020-10-04
18:10:49 openstackgerrit Merged openstack/nova master: libvirt: Remove MIN_LIBVIRT_VIDEO_MODEL_VERSIONS https://review.opendev.org/746985
18:14:57 openstackgerrit Merged openstack/nova master: nova-evacuate: Disable libvirtd service and sockets during negative tests https://review.opendev.org/754684
#openstack-nova - 2020-10-05
03:47:23 openstackgerrit Wenping Song proposed openstack/nova master: Add instance project_id for cyborg arq https://review.opendev.org/738428
07:02:02 openstackgerrit Balazs Gibizer proposed openstack/nova master: Revert "Temporarily disable parts of heal port allocation test" https://review.opendev.org/755995
08:37:22 hemanth_n gibi: thanks for the review on https://review.opendev.org/#/c/749175/ last thursday, sean have clarified on your comments and i added them as code comments to avoid confusion..
08:46:17 openstackgerrit Lee Yarwood proposed openstack/nova master: zuul: Merge nova-evacuate into nova-multinode-live-migration https://review.opendev.org/755309
08:58:29 gibi hemanth_n: I will go back to that review today
08:59:22 hemanth_n gibi: thanks
09:47:53 jiriprox Hi, I would need your support. We are using kolla images for train release from docker.io and last week on Tuesday images stopped working in our environment. PCI passthrough devices a are properly detected on compute node but they are not stored to DB. When we check corresponding table in nova db on controller it is empty :-(
10:23:48 openstackgerrit Wenping Song proposed openstack/nova master: Add instance project_id for cyborg arq https://review.opendev.org/738428
10:33:01 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP: nova-next: Start testing the 'q35' machine type https://review.opendev.org/708701
10:39:47 gibi jiriprox: have you traced back the kolla image changes to a certain nova version change in those imageS?
10:44:13 jiriprox @gibi No. I don't know how to track which source code version was used in docker image pulled from docker.io with tag train
10:44:41 gibi jiriprox: do you know which was the last docker image version that worked for you?
10:47:31 jiriprox @gibi The last one working was pulled 25.9. It stopped working with images pulled 29.9.
10:48:11 gibi jiriprox: could you check with the kolla developers if they can map those dates to nova versions?
10:48:27 gibi sean-k-mooney: Do you happen to know such mapping ? ^^
10:50:42 jiriprox @gibi I don't know whom to ask. Who is responsible for building kolla images and uploading them to docker.io?
10:51:33 gibi jiriprox: I suggest to ask around in #openstack-kolla channel
10:55:04 sean-k-mooney gibi: i dont think that exists
10:55:29 sean-k-mooney but you could possibley add it via build metadata at least in the source build
10:56:11 sean-k-mooney the base file has https://github.com/openstack/kolla/blob/master/docker/nova/nova-base/Dockerfile.j2#L3
10:56:29 sean-k-mooney {% block labels %}
10:56:32 sean-k-mooney LABEL maintainer="{{ maintainer }}" name="{{ image_name }}" build-date="{{ build_date }}"
10:56:33 sean-k-mooney {% endblock %}
10:56:57 sean-k-mooney you could add other labels with the nova version
10:57:14 gibi sean-k-mooney: thanks. So the only way to see what changed from nova perspective is to introspect the image
10:57:24 sean-k-mooney yes
10:58:36 sean-k-mooney if its a binary install then you would have to compate the package versions if its a sourc install it will use tarballs by defualt rather then git
10:59:33 sean-k-mooney i think it recoreds which one somewhre but i cant recal off the top of my head
10:59:34 jiriprox @gibi @sean-k-mooney I would expect that stable/train branch should have some documented release updates.
10:59:47 sean-k-mooney oh i t does one sec
11:00:49 sean-k-mooney for soruce builds its https://github.com/openstack/kolla/blob/stable/train/kolla/common/config.py#L306-L865
11:01:17 sean-k-mooney it uses the last stable release
11:01:20 sean-k-mooney https://github.com/openstack/kolla/blob/stable/train/kolla/common/config.py#L661-L664
11:01:24 sean-k-mooney is nova ^
11:01:33 sean-k-mooney so currently 20.4.0 for stable train
11:02:43 sean-k-mooney that only applies for source builds, if its a binary build its whatever the disto was shiping at the time it was built
11:02:50 gibi hm, 20.4.0 was released on 28th of Aug
11:03:31 gibi so on I don't expect any nova changes in kolla stable/train image between 25th and 29th of Sept
11:03:38 gibi jiriprox: ^^
11:04:12 sean-k-mooney jiriprox: which docker hub image are you using sprecicly
11:04:31 sean-k-mooney ubuntu-source vs centos-binary
11:05:21 sean-k-mooney there are at least 4 copyies of every image, the ubunut/centos source will have the version in that file but ubuntu/centos binary will be different
11:05:53 jiriprox sean-k-mooney centos-source (centos7) from docker.io
11:06:01 sean-k-mooney jiriprox: ok cool
11:06:05 sean-k-mooney looking at https://github.com/openstack/nova/tree/stable/train/nova/pci
11:06:19 sean-k-mooney there has been no change fo 16months
11:07:10 sean-k-mooney looking at the compute managert ther have been more recent updates https://github.com/openstack/nova/commits/stable/train/nova/compute
11:07:22 sean-k-mooney but they are all related to volumes or networking
11:08:10 sean-k-mooney similarly nothing has changed in the conductor
11:08:26 sean-k-mooney so im not seeing an obvious reason to assume its a nova code change
12:22:39 openstackgerrit Takashi Natsume proposed openstack/nova-specs master: Make 'Feature Liaison' optional in test https://review.opendev.org/748591
12:23:02 openstackgerrit Takashi Natsume proposed openstack/nova master: Add placeholder migrations for Victoria backports https://review.opendev.org/754396
12:42:56 bauzas good afternoon, folks
12:44:03 bauzas spoiler alert : you can get the video of my recorded talk for my summit session now and not needing to await for the Summit
12:44:07 bauzas ping me if you want :p
12:45:14 bauzas gibi: any urgent queries for me ?
12:46:58 gibi bauzas: hi. Nothing in my mind for Victoria. I've started reading open specs like https://review.opendev.org/#/c/742785/
12:47:13 bauzas cool, I'll then repropose the routed-networks one
12:47:31 bauzas and I'll start looking at open specs
12:48:41 gibi i've proposed my own spec for W https://review.opendev.org/#/c/755477/
12:51:44 bauzas my review ratio is super low, looks good a good start for improving my stats :)
13:04:42 gibi :)
13:06:02 kashyap bauzas: quality > quantity, no? :-)
13:06:46 bauzas kashyap: surely yes, but honestly, I still need to review for others
13:07:01 kashyap Sure, quality doesn't exclude reviewing for othres :)
13:07:18 bauzas that's what I'm paid^R^R^R^R expected to do
13:07:33 bauzas :)
13:08:40 sean-k-mooney gibi: oh the qos interface attach
13:09:10 sean-k-mooney gibi: that would be a good one to bring up with neutron in the cross project session
13:09:29 sean-k-mooney gibi: they had a FFE for the ablity to update a qos policy
13:09:37 sean-k-mooney for bandwidth
13:09:48 sean-k-mooney but it had a bunch of unhandeled edgecases

Earlier   Later