Earlier  
Posted Nick Remark
#openstack-nova - 2023-06-06
16:19:15 bauzas #info Nova deadlines are set in the above schedule
16:19:20 bauzas #info Nova spec review day today
16:19:25 bauzas as a reminder ^
16:19:39 gibi I deeply missed that :/
16:19:42 bauzas tbh, I wasn't able to do my duty but I'll do this later tonight
16:20:00 bauzas (some internal discussion ate my whole afternoon)
16:20:12 bauzas so, yeah, would be nice
16:20:24 bauzas nothing to tell apart this
16:20:24 gibi I saw that there is a spec proposal for continuing the PCI in placement work
16:20:33 bauzas gibi: indeed, someone proposed
16:20:40 gibi I need to review that
16:20:43 bauzas cool
16:20:57 gibi but other can chime in there too :)
16:20:58 bauzas as a reminder, if folks don't have time to review specs today, that's fine (c)
16:21:09 bauzas but please try to look at them this week
16:21:10 gibi there is alway tomorrow :)
16:21:22 bauzas at least before the Summit in case people discuss there
16:21:31 bauzas anyway, good related point,
16:21:40 bauzas #topic pPTG Planning
16:21:45 bauzas #info please add your topics and names to the etherpad https://etherpad.opendev.org/p/vancouver-june2023-nova
16:21:57 bauzas crickets in there ^
16:22:12 bauzas so I'll write an -discuss ML thread for this
16:22:20 gibi nah, I added one thing now :D
16:22:23 bauzas in case ops or devs want to discuss with us
16:22:30 bauzas hehe
16:23:23 bauzas + I'll tell ops during our forum meet&greet about our PTG
16:23:36 bauzas #info The table #24 is booked for the whole two days. See the Nova community there !
16:23:36 bauzas #info The table #24 is booked for the whole two days. See the Nova community there !
16:23:40 bauzas that's it
16:23:42 bauzas moving on
16:23:48 bauzas #topic Review priorities
16:23:56 bauzas #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)
16:24:01 bauzas #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review
16:24:06 bauzas #topic Stable Branches
16:24:12 bauzas elodilles is maybe afk
16:24:18 bauzas so lemme add his points
16:24:31 bauzas #info stable gates should be OK (from stable/2023.1 to stable/train)
16:24:37 bauzas #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:24:42 bauzas huzzah for this
16:24:51 bauzas and my point
16:24:57 bauzas #info train-eol patch proposed https://review.opendev.org/c/openstack/releases/+/885365
16:25:10 bauzas I'd appreciate if nova-cores could comment it ^
16:25:19 dansmith I will
16:25:31 dansmith I noticed the cinder people are taking a more aggressive approach
16:25:40 bauzas gibi: okay, then -1 my patch and I'll modify it to await for your backport merge
16:25:47 bauzas dansmith: yup, saw it too
16:25:53 gibi bauzas: I think I'm OK to drop that backport
16:26:05 gibi I did that to see if the patch works
16:26:12 bauzas gibi: as you want, just tell me your insights in the train-eol patch
16:26:18 gibi ack
16:26:44 bauzas dansmith: fwiw I'm afraid of EOLing the whole EM branches
16:27:09 dansmith shrug.. my argument for train applies to all the EM ones too
16:27:16 dansmith maybe we wait and see how it goes for cinder ;)
16:27:38 bauzas but since we haven't backported the os-brick CVE fix in Ussuri and Victoria, I could understand
16:28:01 bauzas but yeah, let's see what it's happening for cinder :D
16:28:26 bauzas anyway, moving on
16:28:35 bauzas #topic Open discussion
16:28:45 bauzas none in the agenda
16:28:54 bauzas anything that someone wants to tell ?
16:30:01 gibi one thing
16:30:05 bauzas shoto
16:30:11 bauzas shoot even
16:30:34 gibi there was a request for opinion about openstack on k8s
16:30:40 gibi let me find the link
16:30:55 sean-k-mooney its a thing that people do
16:31:36 bauzas okidoki, let's wait
16:32:15 gibi 13:01 < mdbooth> I'll be running a forum session on Kubernetes on OpenStack in Vancouver next week. It's for users and developers of all related projects to talk to each other. Etherpad is here if there's anything you'd like to discuss: https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack
16:32:20 gibi 13:01 < mdbooth> I'll be running a forum session on Kubernetes on OpenStack in Vancouver next week. It's for users and developers of all related projects to talk to each other. Etherpad is here if there's anything you'd like to discuss: https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack
16:32:30 gibi sorry for the duplicate
16:32:47 sean-k-mooney im wondering why mdboot is runnign that session but ok
16:32:51 dansmith that's k8s on openstack not what you said right?
16:32:57 gibi sorry I mixed up
16:32:59 sean-k-mooney that k8s on openstack
16:33:01 sean-k-mooney ya
16:33:05 bauzas ok, so lemme add the link
16:33:17 sean-k-mooney that makes more sense why mdbooth is involved
16:33:26 bauzas #link https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack OpenInfra Forum session for discussing about k8s on openstack
16:33:37 bauzas gibi: the other way btw. :)
16:33:41 gibi there is some nova related question in the etherpad
16:34:24 gibi about getting notified if anything changed with servers
16:34:30 gibi I offered the nova notification inteface
16:34:35 bauzas yeah and it's a public API :)
16:34:38 gibi but apperantly they want something public
16:34:58 gibi the API is documented but the message bus access then to be non public
16:34:58 sean-k-mooney the notifcation are the only interface we have currently
16:35:03 bauzas since someone worked on notifications objects like 6 years ago (guess who :p )
16:35:14 gibi bauzas: hah :D
16:35:24 bauzas gibi: are you sure that the message bus can't be public ?
16:35:33 dansmith it shouldn't be
16:35:39 gibi yeah
16:35:43 dansmith we have instance events.. that's what they want I think
16:35:48 sean-k-mooney the notification bus is semi privladged
16:35:50 gibi and our notifications tend to contain infra information
16:35:52 dansmith I think they just need an async way to get those
16:35:58 sean-k-mooney the notifications can have private infor in them
16:36:02 sean-k-mooney depening on what you configure
16:36:04 sean-k-mooney like the bdms
16:36:30 gibi yeah, bottom line the notification API is designed for consumed by admins or other openstack service not endusers
16:36:43 dansmith right, it would leak bad things between tenants for sure
16:36:43 bauzas ah they want it to be consumable by endusers ?

Earlier   Later