惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
博客园_首页
雷峰网
雷峰网
V
V2EX
博客园 - 司徒正美
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - Franky
月光博客
月光博客
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学
T
Tailwind CSS Blog
小众软件
小众软件
博客园 - 叶小钗
美团技术团队
酷 壳 – CoolShell
酷 壳 – CoolShell
Apple Machine Learning Research
Apple Machine Learning Research
IT之家
IT之家
MyScale Blog
MyScale Blog
Blog — PlanetScale
Blog — PlanetScale
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
人人都是产品经理
人人都是产品经理
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

OpenStack - Recent changes [en]

Security Notes - OpenStack OSSN/OSSN-0098 - OpenStack User:ZlixnupTop - OpenStack OpenStack OpenStack Meetings/InfraTeamMeeting - OpenStack User:Jibzfloopgraip - OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack User:Normanroppy - OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack Difference between revisions of "Meetings/QATeamMeeting" OpenStack Difference between revisions of "CinderMeetings" OpenStack OpenStack OpenStack User:Mufftroxkeere - OpenStack
“Meetings/Nova”的版本间的差异 - OpenStack
Elod.illes · 2026-06-08 · via OpenStack - Recent changes [en]
第85行: 第85行:
  
 

* #topic Stable Branches

 

* #topic Stable Branches

** grenade-skip-level on stable/2025.2 and grenade on stable/2025.1 are failing due to 2024.2 Dalmatian EOL

+

** #info nova stable gates are working again

** #info grenade-skip-level job removed from stable/2025.2, gate is unblocked on the branch

+

** #info placement stable/2025.1 is blocked - workaround: https://review.opendev.org/c/openstack/placement/+/992299

** #info stable/2025.1 is still blocked, grenade on stable/2025.1 has a workaround: https://review.opendev.org/c/openstack/nova/+/989579

 
 

** #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci

 

** #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci

  

2026年6月8日 (一) 15:52的最新版本

目录

  • 1 Weekly Nova team meeting
    • 1.1 Project Heartbeat
    • 1.2 Agenda for next meeting
    • 1.3 Sub-teams
    • 1.4 Previous meetings

Weekly Nova team meeting

Regular MEETING TIME: Mondays 16:00 UTC (#openstack-nova on OFTC)

This meeting is a weekly gathering of developers working on OpenStack Compute (Nova). We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.

Project Heartbeat

This information will be updated weekly but not mentioned in the meeting unless specifically called out on the agenda.

Agenda for next meeting

Next meetings scheduled for:

Where you see "?" feel free to just edit the wiki and add your item.

Here is the agenda for the next meeting:

  • #topic Bugs (stuck/critical)
    • #info No Critical bug
  • #topic vmwareapi 3rd-party CI efforts Highlights
  • #topic Gibi's news about eventlet removal
  • #topic Nova using openstack sdk for neutron
  • #topic Ironic review priorities
  • #topic Open discussion
    • (sean) bug janitor config
      • fungi noticed that https://bugs.launchpad.net/nova/+bug/2142042 was moved form incomplete to expired by the launchpad janitor
      • "[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]"
      • i quickly disabled it beacuse we were unclear if this was intentiaonl, broken for year an djust started working or enabled by a default change in launchpad.
      • this is a checkbox in the bug config and appears to only "expire" bugs in the incompelte status after 60 days.
      • it does not affect any other bug state.
      • do we want to keep this on or off? this proably need to be set for placment os-vif and the other projects as well as i notice it was on for cybrog and watcher.
    • (sean): pre populated cirros rootfs experiment
      • #link https://review.opendev.org/q/topic:%22cirros-per-populated-root%22
      • i would like to run an experiment in the gate for 2 weeks to see if we can get rid of the kernel panics once and for all
      • those change use a custom built cirros image with a prepoulated rootfs on the assumtion the current panic is causes by an interupted rootfs copy on first boot
      • i have created an issue
      • #link: https://github.com/cirros-dev/cirros/issues/131
      • to discuss the maintenance state of cirros and proposed a pr to upstream these changes which ill iterate on independently
      • are we ok to do this and quick revert if need to gather the data to prove this fixes the issue?

Sub-teams

There are also some Nova subteam meetings. See Nova#Nova_subteams for details.

Previous meetings