Earlier  
Posted Nick Remark
#openstack-nova - 2023-10-09
08:41:05 bauzas sahid: are you able to join tomorrow's nova meeting at 6pm our time ?
08:43:20 sahid bauzas: 6pm our time, probably no but I will try :/
08:43:39 bauzas yeah, it's unfortunately late
08:43:50 bauzas in one month, it will be at 5pm
08:43:55 bauzas 1600UTC :)
08:44:10 sahid yes and the mardi is not good time for me
08:44:19 sahid yes that will be better :-)
08:44:26 bauzas so if you want, I can ask if people are okay with this blueprint to be a specless one
08:44:49 bauzas and I'll tell you on wed
08:44:52 sahid bauzas: yes please do and let me know, if needed I can certainly write one
08:45:04 bauzas col
08:45:07 sahid thanks a lot
08:45:08 bauzas cool even
08:45:19 bauzas np, hth
08:51:28 bauzas sahid: oh, you would want to backport the filter change upstream ?
08:52:04 bauzas sahid: if so, I'll rather ask if people think that your change is a bugfix or rather a feature
08:52:28 bauzas if this is a feature, we can't backport it upstram (but you can do what you want :p )
08:52:54 bauzas (what you want internally*)
09:13:44 dvo-plv bauzas, Hello, Maybe you will have a chance to review it https://review.opendev.org/c/openstack/nova-specs/+/895924 ?
09:14:03 bauzas yup, I promised it, I will once I'm free
09:14:17 dvo-plv great, thank you
09:14:32 bauzas it just needs myself to ramp up on a few new names :)
09:22:25 dvo-plv yes, sure, I will wait
09:22:31 dvo-plv sean-k-mooney[m], Hello, are you here ?
14:08:08 opendevreview Dan Smith proposed openstack/nova master: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246
15:03:34 opendevreview Dan Smith proposed openstack/nova master: Clean up service_get_all() https://review.opendev.org/c/openstack/nova/+/897674
15:40:38 gibi dansmith: thanks for the updates I'm +2 all the way ^^
15:40:49 dansmith gibi: i saw, thanks
15:41:00 dansmith and thanks for pointing out my n00b n^2 code ;P
15:43:52 sean-k-mooney i can add that to my list fo things to reveiew
15:44:08 sean-k-mooney procedural question do we need a specless blueprint or bug for those
15:45:18 sean-k-mooney i dont think there is any intent to backprot https://review.opendev.org/c/openstack/nova/+/897076 ?
15:46:32 dvo-plv sean-k-mooney, Hello
15:46:54 sean-k-mooney dvo-plv: o/
15:47:11 dvo-plv I would like to discuss out blueprint regarding NT NIC support. But it too late today, can we talk tomorrow?
15:47:34 dvo-plv when it will be comfortable for you ?
15:51:05 sean-k-mooney honestly i need to reload context.
15:51:36 sean-k-mooney so we can chat during the week but im not sure when ill be free. ping me durnign the week when your around
16:23:49 dansmith sean-k-mooney: I'm calling it a followup to the original BP, which is why I tagged it as such
16:40:20 sean-k-mooney ack
16:41:10 sean-k-mooney i didnt sleep great last night so i may not get to it today but if i dont ill review them tommorow if someone else does not review them in the interim
16:41:42 dansmith no rush
17:37:34 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
17:42:12 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
17:50:07 opendevreview sean mooney proposed openstack/nova master: add initial healthcheck support https://review.opendev.org/c/openstack/nova/+/825015
18:39:29 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
18:45:51 opendevreview Merged openstack/nova master: cpu: make governors to be optional https://review.opendev.org/c/openstack/nova/+/885352
18:46:07 opendevreview sean mooney proposed openstack/nova master: add initial healthcheck support https://review.opendev.org/c/openstack/nova/+/825015
20:16:23 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
21:16:52 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
21:58:11 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708
#openstack-nova - 2023-10-10
01:06:09 opendevreview melanie witt proposed openstack/nova master: Add encryption support to convert_image https://review.opendev.org/c/openstack/nova/+/870934
05:52:00 opendevreview Amit Uniyal proposed openstack/nova master: Adds device tagging functional tests https://review.opendev.org/c/openstack/nova/+/895162
06:00:36 opendevreview Amit Uniyal proposed openstack/nova master: Adds device tagging functional tests https://review.opendev.org/c/openstack/nova/+/895162
06:35:33 opendevreview Amit Uniyal proposed openstack/nova master: Adds device tagging functional tests https://review.opendev.org/c/openstack/nova/+/895162
07:13:47 hamidlotfi_ Hi there,
07:13:47 hamidlotfi_ In the nova database, I see much `LOCK WAIT` on the `neutron.ports` table
07:13:47 hamidlotfi_ and I putting a sample log for the lock wait
07:13:47 hamidlotfi_ I want to know if is this a bug in the structure of a table or the script of the update or the user mistake.
07:13:52 hamidlotfi_ https://www.irccloud.com/pastebin/o4HQQaEK/
09:54:27 hamidlotfi_ @dansmith @bauzas @sahid_
10:22:41 dvo-plv sean-k-mooney, Are you here ?
10:44:28 sean-k-mooney dvo-plv: o/
10:45:13 dvo-plv I wouldl iek to talk with you regarding out blueprint nt nic support, if you have free time for it
10:45:46 dvo-plv previously we decided that we will try to pass socket name with ovs command for dpdk port type
10:47:09 sean-k-mooney yes and i ask can we pass the name to ovs when addign the port so that we didn not have to compute one that matched the nic driver format
10:47:45 sean-k-mooney we also discussed that some of the magic constant are actully discoverable form sysfs like the vf offset
10:48:13 dvo-plv yes
10:49:19 dvo-plv we spent some time on the investigation and this is not possible to do it for dpdk port type with ovs. there will be alot of changes, DPDK community will not approve it
10:49:57 sean-k-mooney thats not ideal
10:50:23 dvo-plv So I would like to get back to the separate os-vif plugin
10:50:45 dvo-plv what do you think about that ?
10:50:50 sean-k-mooney not nessiarly what that means is that nova needs to tell neutron the vf specific info
10:51:20 sean-k-mooney so we need to pass info to the ml2 driver in the binding_profile
10:51:52 sean-k-mooney neutron can then use that to generate the socket path. alternitivly we could jsut generate the path ourselve in nova
10:52:21 dvo-plv path is not a problem, specific socket name is the root cause
10:52:44 sean-k-mooney the socket name is path of the path :)
10:52:47 sean-k-mooney but yes
10:54:51 dvo-plv So, we can somehow use port binding profile for this purposes?
10:56:17 sean-k-mooney yes that is what its for to pass info form nova to the network backend
10:56:27 sean-k-mooney we normally sotre the pci_adress in it
10:56:44 sean-k-mooney but we can have other fields like the offset ectra
10:56:59 sean-k-mooney or we can just comppute the socket name and pass that
10:57:07 sean-k-mooney which is proably the better option
10:57:30 sean-k-mooney since nova does not have the base path (neutron/ovs does have that info)
10:57:53 sean-k-mooney so we can provide the socket name in the binding profile and neutron can append that to the base socket path
10:58:03 sean-k-mooney and then we will get the full path back which we can store in the xml
11:00:20 dvo-plv okay, i see. but i have a question how we should handle pci. for socket name stdvio10, we need to use pci 0000:65:01.2. So we need vendor specific mechanism for parse socket name
11:00:41 sean-k-mooney its the other way around
11:00:49 sean-k-mooney we are selecting VFs in the pci tracker
11:01:01 sean-k-mooney and you need to compute the socket name from the adress
11:01:45 sean-k-mooney the main issue i think is still the multi device support
11:02:07 sean-k-mooney since the previous algorthim did not support more hten one nic
11:03:17 dvo-plv yes, currently we do not support multinic setup
11:03:44 sean-k-mooney right so i dont think we should support this in nova until that is addressed
11:04:57 dvo-plv Honestly, i forget about that, I will investigate internal if we have some plan how this should be done in the future, because as far as I know we have plan to provide this feature
11:06:02 dvo-plv But if this is a limitation for be in the common code, what about to pass us with separate os-vif plugin, which will handle all this issuses ?
11:06:57 sean-k-mooney a out of tree os-vif plugin will also reqiure your own ml2 driver in neutron
11:08:17 dvo-plv yes, we can implement it too, like Agilio https://github.com/Netronome/agilio-ovs-openstack-plugin/tree/master/vif_plug_agilio_ovs
13:57:13 opendevreview Dan Smith proposed openstack/nova master: WIP: Compile mdev samples for nova-next https://review.opendev.org/c/openstack/nova/+/897708

Earlier   Later