Difference between revisions of "CinderCaracalPTGSummary"
(→Introduction) |
(→Bobcat Retrospective) |
||
| Line 18: | Line 18: | ||
| − | === | + | ===Bobcat Retrospective=== |
| + | |||
| + | We categorized the discussion into the following sub sections: | ||
| + | |||
| + | * What went good? | ||
| + | ** Active contribution across different companies | ||
| + | ** We got 2 Outreachy interns in summer internship having great contributions in api-ref sample tests | ||
| + | ** Releases happened on time | ||
| + | |||
| + | * What went bad? | ||
| + | ** CI failure rate impacting productivity | ||
| + | ** Sofia leaving the team really affected review bandwidth | ||
| + | |||
| + | * What should we start doing? | ||
| + | ** Need to get more cores | ||
| + | *** Also explained what is expected from a core reviewer. | ||
| + | *** https://docs.openstack.org/cinder/latest/contributor/gerrit.html#efficient-review-guidelines | ||
| + | |||
| + | * What should we continue doing? | ||
| + | ** Sponsoring outreachy interns | ||
| + | *** proposal accepted with at least one applicant | ||
| + | |||
| + | * What should we stop doing? | ||
| + | ** Lack of structure around the review request section in cinder meetings | ||
| + | *** Too many patches discourage the reviewers from taking a look | ||
| + | *** Authors should add explanation if the patch is complicated and ask if they have any doubts | ||
| + | *** Author should try to add only the relevant patch based on milestone instead of adding all patches possible | ||
| + | *** Author should be active in reviews since the core team prioritizes patches of contributors that do active reviews | ||
| + | *** #action: whoami-rajat to follow up on this in a cinder meeting | ||
| + | |||
| + | ===Gate Issues=== | ||
| + | |||
| + | Continuing the discussion from 2023.2 Bobcat midcycle, we are still seeing gate issues consisting of OOMs and timeouts. | ||
| + | Looking at a sample gate job failure, we decided on the following points: | ||
| + | |||
| + | * Increase system memory of VM if possible, 8GB is not enough for tempest tests | ||
| + | * Increase swap space (make it same size as RAM for one to one mapping) | ||
| + | * Change cinder to use the file lock for the coordination in order to get rid of etcd | ||
| + | * Reduce number of processes | ||
| + | ** We see the pattern of multiple services running multiple instances | ||
| + | *** neutron-server: 5 | ||
| + | *** nova-conductor: 6 | ||
| + | *** nova-scheduler: 2 | ||
| + | *** swift: 3 for each of its service | ||
| + | * Reduce concurrency to 2 for testing purposes to see how many VMs we end up running | ||
| + | * #action: rosmaita to propose patch for few straightforward tasks like increasing swap space | ||
| + | |||
| + | ===Backup/Restore performance=== | ||
Revision as of 23:45, 24 October 2023
Contents
Introduction
The Eighth virtual PTG for the 2024.1 (Caracal) cycle of Cinder was conducted from Tuesday, 24th October, 2023 to Friday, 27th October, 2023, 4 hours each day (1300-1700 UTC). This page will provide a summary of all the topics discussed throughout the PTG.
This document aims to give a summary of each session. More information is available on the cinder 2024.1 Caracal PTG etherpad:
The sessions were recorded, so to get all the details of any discussion, you can watch/listen to the recording. Links to the recordings for each day are below their respective day's heading.
Tuesday 24 October
recordings
Bobcat Retrospective
We categorized the discussion into the following sub sections:
- What went good?
- Active contribution across different companies
- We got 2 Outreachy interns in summer internship having great contributions in api-ref sample tests
- Releases happened on time
- What went bad?
- CI failure rate impacting productivity
- Sofia leaving the team really affected review bandwidth
- What should we start doing?
- Need to get more cores
- Also explained what is expected from a core reviewer.
- https://docs.openstack.org/cinder/latest/contributor/gerrit.html#efficient-review-guidelines
- Need to get more cores
- What should we continue doing?
- Sponsoring outreachy interns
- proposal accepted with at least one applicant
- Sponsoring outreachy interns
- What should we stop doing?
- Lack of structure around the review request section in cinder meetings
- Too many patches discourage the reviewers from taking a look
- Authors should add explanation if the patch is complicated and ask if they have any doubts
- Author should try to add only the relevant patch based on milestone instead of adding all patches possible
- Author should be active in reviews since the core team prioritizes patches of contributors that do active reviews
- #action: whoami-rajat to follow up on this in a cinder meeting
- Lack of structure around the review request section in cinder meetings
Gate Issues
Continuing the discussion from 2023.2 Bobcat midcycle, we are still seeing gate issues consisting of OOMs and timeouts. Looking at a sample gate job failure, we decided on the following points:
- Increase system memory of VM if possible, 8GB is not enough for tempest tests
- Increase swap space (make it same size as RAM for one to one mapping)
- Change cinder to use the file lock for the coordination in order to get rid of etcd
- Reduce number of processes
- We see the pattern of multiple services running multiple instances
- neutron-server: 5
- nova-conductor: 6
- nova-scheduler: 2
- swift: 3 for each of its service
- We see the pattern of multiple services running multiple instances
- Reduce concurrency to 2 for testing purposes to see how many VMs we end up running
- #action: rosmaita to propose patch for few straightforward tasks like increasing swap space
