跳转至： 导航, 搜索
| （未显示同一用户的2个中间版本） | |||
| 第20行： | 第20行： | ||
*** Next on the list are graphite and backup servers | *** Next on the list are graphite and backup servers | ||
*** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too | *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too | ||
| − | **** | + | **** clarkb checked paste's backups to the new server and they appear to be working there |
| + | **** fungi moved wiki over to backup to this server from the old server | ||
| + | **** I think we can probably start the tear down of the old server now | ||
*** Remember to use launch-node's --config-drive flag when booting new Noble nodes in Rax Classic | *** Remember to use launch-node's --config-drive flag when booting new Noble nodes in Rax Classic | ||
** Deploying a Prometheus for Server Metrics (clarkb 20260331) | ** Deploying a Prometheus for Server Metrics (clarkb 20260331) | ||
| 第33行： | 第35行： | ||
*** Chances are we can simply disable them all and remove the conflicting external ids. | *** Chances are we can simply disable them all and remove the conflicting external ids. | ||
*** If we take good notes we can reconstruct the accounts as appropriate after the fact without Gerrit downtime should one of these users show up and wonder what happened. | *** If we take good notes we can reconstruct the accounts as appropriate after the fact without Gerrit downtime should one of these users show up and wonder what happened. | ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
| − |
| ||
** Zuul reporting empty public_v6 addresses for test nodes (clarkb 20260519) | ** Zuul reporting empty public_v6 addresses for test nodes (clarkb 20260519) | ||
*** Zuul is reporting public_v6 values of '' for test nodes that do have working ipv6 in clouds like rax classic and ovh | *** Zuul is reporting public_v6 values of '' for test nodes that do have working ipv6 in clouds like rax classic and ovh | ||
| 第63行： | 第52行： | ||
*** I acknowledge that without further work this would break their CI setup, but I'm questioning now whether that impact would be worse than the impact the current situation has on my ability to maintain the OpenStack CI | *** I acknowledge that without further work this would break their CI setup, but I'm questioning now whether that impact would be worse than the impact the current situation has on my ability to maintain the OpenStack CI | ||
*** Other ideas or opinions are welcome | *** Other ideas or opinions are welcome | ||
| + | ** Etherpad 3.3.2 Upgrade (clarkb 20260622) | ||
| + | *** https://review.opendev.org/c/opendev/system-config/+/994325 Upgrade Etherpad to 3.3.2 | ||
| + | *** Held node at 50.56.159.16 with a test clarkb-test pad. | ||
| + | ** Gitea 1.26.4 Upgrade (clarkb 20260622) | ||
| + | *** https://review.opendev.org/c/opendev/system-config/+/994326 Upgrade Gitea to 1.26.4 | ||
| + | *** Its time to upgrade to the next Gitea bugfix release | ||
| + | ** Working with LF IT to get some help in OpenDev (clarkb 20260622) | ||
| + | *** clarkb and fungi are meeting internally later this week to see if we can point others at the LF to work that OpenDev would like to get done | ||
| + | *** Don't be surprised if you see new faces contributing and please welcome and help them | ||
| + | ** Planning Gerrit Project Renames (clarkb 20260622) | ||
| + | *** We have a request to rename x/cursive to openstack/cursive | ||
| + | *** When we do want to try and do that? | ||
| + | *** Any concern with project ownership doing that? The current group membership includes people from Johns Hopkins University and OpenStack Barbican | ||
* Open discussion | * Open discussion | ||
| 第70行： | 第72行： | ||
Changes should have their topic set to project-rename. | Changes should have their topic set to project-rename. | ||
| − | * Rename x/ | + | * Rename x/cursive -> openstack/cursive: https://review.opendev.org/c/openstack/project-config/+/990122 (stephenfin, fungi) |
== Previous meetings == | == Previous meetings == | ||
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/ | Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/ | ||
2026年6月22日 (一) 23:17的最新版本
目录
- 1 Weekly Project Infrastructure team meeting
- 1.1 Agenda for next meeting
- 1.2 Upcoming Project Renames
- 1.3 Previous meetings
Weekly Project Infrastructure team meeting
The OpenDev Team holds public weekly meetings in #opendev-meeting on OFTC, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.
Please feel free to add agenda items (and your IRC nick in parenthesis).
Agenda for next meeting
- Announcements
- Actions from last meeting
- Specs Review
- Topics
- Upgrading Old Servers (clarkb 20230627)
- https://etherpad.opendev.org/p/opendev-server-upgrade-planning Central tracking document which may link to more host specific documents
- Next on the list are graphite and backup servers
- backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too
- clarkb checked paste's backups to the new server and they appear to be working there
- fungi moved wiki over to backup to this server from the old server
- I think we can probably start the tear down of the old server now
- Remember to use launch-node's --config-drive flag when booting new Noble nodes in Rax Classic
- Deploying a Prometheus for Server Metrics (clarkb 20260331)
- https://review.opendev.org/c/opendev/system-config/+/980840
- This change and its child deploy prometheus with node exporter to collect server metrics
- mnasiadka has proposed we use GrepTimeDB in conjunction with Prometheus to collect metrics over a longer period of time
- Gerrit Account Cleanups (clarkb 20260317)
- Since the upgrade to Gerrit notedb we've had account inconsistencies that prevent us from push to the external ids ref/table directly.
- clarkb did a bunch of work to get the number down from hundreds to about 33 consistency errors before stalling out.
- The tail was the most difficult as it wasn't clear what the more appropriate fix for each account would be
- Since then it has been years and those accounts are likely inactive and unused. We can rerun the Gerrit consistency check, feed the info back through our audit script then decide if we need to be careful with any of these accounts
- Chances are we can simply disable them all and remove the conflicting external ids.
- If we take good notes we can reconstruct the accounts as appropriate after the fact without Gerrit downtime should one of these users show up and wonder what happened.
- Zuul reporting empty public_v6 addresses for test nodes (clarkb 20260519)
- Zuul is reporting public_v6 values of for test nodes that do have working ipv6 in clouds like rax classic and ovh
- This may be an openstack api bug, an openstacksdk bug, or a zuul-launcher bug.
- Be aware this may impact the behavior of some test jobs.
- We will need to dig into why this is happening to understand it better.
- Larger VM sizes for tests (corvus 20260618)
- corvus has been testing python 3.14 with zuul; zuul unit tests now use slightly more than 8GB under 3.14
- We have 16gb nodes, but in two clouds, rax-classic and vexxhost, they have fewer vcpus than their 8gb counterparts, so we need to use 32gb nodes to compensate
- Are we okay with this? Alternatives?
- Dealing with alien zuul config errors in the openstack tenant (frickler 20260617)
- Currently there are still 185 zuul config errors in the openstack tenant, despite my year-long struggle to get rid of them.
- Most of these are from "alien" repos (74 airship, 29 starlingx) that I have no motivation to fix myself with my OpenStack hats on
- Efforts to motivate these projects to clean up their errors themselves have mostly failed
- I still believe that cleaning these up and being able to easily identify fresh errors is important for the healthyness of the CI setup as a whole
- One pretty strong action would be to move these repos into their own tenant(s) or a different shared one like opendev
- I acknowledge that without further work this would break their CI setup, but I'm questioning now whether that impact would be worse than the impact the current situation has on my ability to maintain the OpenStack CI
- Other ideas or opinions are welcome
- Etherpad 3.3.2 Upgrade (clarkb 20260622)
- https://review.opendev.org/c/opendev/system-config/+/994325 Upgrade Etherpad to 3.3.2
- Held node at 50.56.159.16 with a test clarkb-test pad.
- Gitea 1.26.4 Upgrade (clarkb 20260622)
- https://review.opendev.org/c/opendev/system-config/+/994326 Upgrade Gitea to 1.26.4
- Its time to upgrade to the next Gitea bugfix release
- Working with LF IT to get some help in OpenDev (clarkb 20260622)
- clarkb and fungi are meeting internally later this week to see if we can point others at the LF to work that OpenDev would like to get done
- Don't be surprised if you see new faces contributing and please welcome and help them
- Planning Gerrit Project Renames (clarkb 20260622)
- We have a request to rename x/cursive to openstack/cursive
- When we do want to try and do that?
- Any concern with project ownership doing that? The current group membership includes people from Johns Hopkins University and OpenStack Barbican
- Upgrading Old Servers (clarkb 20230627)
- Open discussion
Upcoming Project Renames
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit) Changes should have their topic set to project-rename.
- Rename x/cursive -> openstack/cursive: https://review.opendev.org/c/openstack/project-config/+/990122 (stephenfin, fungi)
Previous meetings
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/