Search results for "canceled meeting" - openstack-discuss

Re: [SDK][OSC] Meeting Times

by Kendall Nelson

I also created this etherpad to hold our meeting agendas: https://etherpad.opendev.org/p/openstacksdk-meeting-agenda -Kendall (diablo_rojo) On Thu, Nov 12, 2020 at 2:29 PM Kendall Nelson <kennelson11(a)gmail.com> wrote: > Sorry I am so slow at replying here! > > 14:00 UTC works for me so long as its only once a month I need to wake up > at 6AM lol. > > I proposed the patch here: https://review.opendev.org/762590 > > -Kendall (diablo_rojo) > > On Thu, Oct 29, 2020 at 1:25 AM Artem Goncharov <artem.goncharov(a)gmail.com> > wrote: > >> Thanks Kendall for starting the discussion. >> >> Being located in CET (UTC+1/2) I am fine going one hour earlier (14:00 >> UTC) to have it not so late for Akihiro and avoid clash with Manila, but am >> also flexible making it 16:00 (cancelled API-SIG). >> >> Maybe a doodle will help to pick the most suitable? I hope to get a bit >> more answers from other interested parties. >> >> Regards, >> Artem >> >> > On 29. Oct 2020, at 02:48, Akihiro Motoki <amotoki(a)gmail.com> wrote: >> > >> > Thanks for starting the thread. >> > I agree it is a good idea to have a regular meeting even though it is >> > less frequent. >> > >> > Thursday 15UTC is okay with me. >> > 16UTC is a bit late to me as it is 1am in my local time. One hour >> > earlier (14UTC) also works for me. >> > >> > Thanks, >> > Akihiro Motoki (amotoki) >> > >> > On Thu, Oct 29, 2020 at 7:49 AM Kendall Nelson <kennelson11(a)gmail.com> >> wrote: >> >> >> >> Hello! >> >> >> >> In the PTG session today we talked about doing some sort of regular >> meetings to kind of jump start things after the more recent lack of >> activity. We discussed beginning with more frequent meetings (a couple >> across the next few weeks) and then shifting to a more relaxed monthly >> cadence. >> >> >> >> I propose 15:00 UTC on the third thursday of each month as our monthly >> meeting time? If people agree, I will propose a patch :) >> >> >> >> As for the more frequent ones to keep the momentum from discussion >> from this week/last week. We could use that time (15 UTC) and date >> (Thursdays) and maybe just do them on Nov 12 and 19th to keep us moving? >> That gives us next week to catch up/ take a breath from the last two weeks, >> but not waiting till after the US Thanksgiving holiday. >> >> >> >> Let me know what you think! >> >> >> >> -Kendall Nelson (diablo_rojo) >> >> >> >> >> >> >> > >> >>

4 years, 8 months

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-24)

by Goutham Pacha Ravi

Hello Stackers, The Virtual Project Team Gathering (PTG) is next week [1][2]. There are 32 discussion tracks planned throughout the week, along with ad-hoc virtual hallway/water cooler discussions. As a result, many regular weekly IRC meetings will be canceled. Please take a moment to review the PTG Etherpad for the Technical Committee [3]. We encourage community-wide participation on topics such as: - Community Leaders Meeting (2024-10-21 / 1400 UTC): This event is open to all project maintainers, especially PTLs and DPLs. We'll cover several topics of community-wide importance. - Eventlet Removal (2024-10-21 / 1500 UTC): This session will kick off discussions around addressing the technical debt associated with OpenStack services migrating away from the eventlet library. - ...and many more! There may be some minor changes to the schedule based on other cross-project topics being planned. The best way to stay up-to-date is to join OFTC's #openinfra-events channel or watch the event stream on the PTG website [2]. This week, Indiana University will be hosting the OpenInfra community for OpenInfra Days, North America (15-16 Oct 2024). This is a hybrid event, and both in-person and online registrations are still open. If you're attending in person, I’d love to catch up and discuss how the OpenStack TC can assist you. Please don’t hesitate to say hello! === Weekly Meeting === The OpenStack Technical Committee held its weekly meeting on 2024-10-08 [5]. The meeting was well attended. During the meeting, we approved a change to mark the "kuryr-kubernetes" and "kuryr-tempest-plugin" projects as "inactive." This means we won’t be producing any releases from these projects during the 2025.1 "Epoxy" release cycle, and the repositories may soon be retired. If you depend on these projects, please let us know. It’s worth noting that there have been no releases since the 2024.1 "Caracal" cycle. The TC also spent time brainstorming PTG topics and scheduling. We discussed a regression in python-openstackclient that necessitates an update to the recently released 2024.2 "Dalmatian" release. We took action to strengthen the CI jobs for python-openstackclient, adding more scenarios such as upgrade testing with "trunk." The next weekly IRC meeting of the OpenStack Technical Committee is on 2024-10-15, chaired by Dmitriy Rabotyagov (noonedeadpunk). The agenda is available on the meeting wiki page [6]. I hope you can join us. Please remember that you can propose topics by editing the wiki page, and if you do, please include your IRC nick so we can call on you during the meeting. === Governance Proposals === ==== Merged ==== - Mark kuryr-kubernetes and kuryr-tempest-plugin inactive: https://review.opendev.org/c/openstack/governance/+/929698 ==== Open for Review ==== - Propose to select the eventlet-removal community goal: https://review.opendev.org/c/openstack/governance/+/931254 - Propose a pop-up team for eventlet-removal: https://review.opendev.org/c/openstack/governance/+/931978 - Adding Axel Vanzaghi as PTL for Mistral: https://review.opendev.org/c/openstack/governance/+/927962 === How to Contact the TC === You can reach the TC in several ways: 1. Email: Send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every Tuesday at 1800 UTC [6]. --- === Upcoming Events === - 2024-10-15: OpenInfra Days NA, Indianapolis [4] - 2024-10-21: OpenInfra Project Teams Gathering: https://openinfra.dev/ptg/ Thank you for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] "Epoxy" PTG Schedule: https://ptg.opendev.org/ptg.html [3] OpenStack TC PTG Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-os-tc [4] OpenInfra Days North America: https://ittraining.iu.edu/explore-topics/titles/oid-iu/ [5] TC Meeting IRC Log, 2024-10-08: https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-08-18.00.log.html [6] TC Meeting Agenda, 2024-10-15: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

9 months, 3 weeks

Re: [i18n] i18n SIG PTG Schedule & Key Topics for Discussion

by Seongsoo Cho

Hi i18n SIG Team I am sharing the updated schedule. • October 23rd: 13:00 - 15:00 UTC • October 24th: 13:00 - 15:00 UTC (cancelled) * October 25th : 05:00 ~ 07:00 UTC (added) Best Regards Seongsoo On Wed, Oct 9, 2024 at 11:13 PM Seongsoo Cho <ppiyakk2(a)printf.kr> wrote: > Hi i18n SIG Team > > I’m pleased to announce the i18n SIG schedule for the upcoming PTG. Here > are the details: > > Dates: > > • October 23rd: 13:00 - 15:00 UTC > • October 24th: 13:00 - 15:00 UTC > > We encourage you to check the meeting minutes and contribute to the > discussion by accessing the following Etherpad: > https://etherpad.opendev.org/p/oct2024-ptg-i18n > > Key Discussion Topics: > > 1. Weblate Migration: We will discuss the progress and steps needed for > migrating to Weblate. > 2. Enhancing Translation Engagement: We’ll focus on strategies to improve > the engagement and translation rates for OpenStack projects. Potential > ideas, such as incorporating LLM (Large Language Models), will also be > explored. > > We look forward to your participation and contributions to these > discussions. > > Best Regards > Seongsoo > > -- > Seongsoo Cho > OpenStack Korea User Group / Community Leader > IRC #seongsoocho > -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

9 months, 1 week

Re: openstack-discuss Digest, Vol 50, Issue 63

by Kerem Çeliker

Hello Can, To fix an RBD (Rados Block Device) IOPS bottleneck on the client side in OpenStack, you can try the following: Monitor the CPU and memory usage on the client machine to ensure that it has sufficient resources. You can use tools like top or htop to view real-time resource usage. Check the network bandwidth between the client and the storage system to ensure that it is not a bottleneck. You can use tools like iperf or tcpdump to measure network performance. Review the configuration of the storage system to ensure that it is optimized for the workload. This may include adjusting the number and type of disks used, as well as the RAID level and chunk size. Consider using a storage system with a higher IOPS rating to see if it can improve performance. This may involve upgrading to faster disks or using a storage solution with more disks or SSDs. Try using a different client machine with more resources (e.g., a machine with a faster CPU and more memory) to see if it can issue more I/O requests. Consider using a different network connection between the client and the storage system, such as a faster network card or a direct connection rather than a network switch. If you are using Ceph as the underlying storage system, you can try adjusting the Ceph configuration to improve performance. This may include adjusting the number of placement groups, the object size, or the number of OSDs (object storage devices). It's also worth noting that an IOPS bottleneck can also occur on the server side (i.e., within the storage system itself). In this case, you may need to adjust the configuration of the storage system or add more resources (e.g., disks or SSDs) to improve performance. BR, Kerem Çeliker keremceliker.medium.com IBM | Red Hat Champion Sent from my iPhone > On 28 Dec 2022, at 08:13, openstack-discuss-request(a)lists.openstack.org wrote: > > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. [ops][nova] RBD IOPS bottleneck on client-side (Can ?zyurt) > 2. [keystone][Meeting] Reminder Keystone meeting is cancelled > today (Dave Wilde) > 3. Nova libvirt/kvm sound device (Zakhar Kirpichenko) > 4. Re: [Tacker][SRBAC] Update regarding implementation of > project personas in Tacker (Yasufumi Ogawa) > 5. Re: [Tacker][SRBAC] Update regarding implementation of > project personas in Tacker (manpreet kaur) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Dec 2022 15:33:56 +0300 > From: Can ?zyurt <acozyurt(a)gmail.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: [ops][nova] RBD IOPS bottleneck on client-side > Message-ID: > <CAMf4N71awOfNyBk4FfpM6UCjH4AZWz+QuJwUnOv+itvqvPbTjw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi everyone, > > I hope you are all doing well. We are trying to pinpoint an IOPS > problem with RBD and decided to ask you for your take on it. > > 1 control plane > 1 compute node > 5 storage with 8 SSD disks each > Openstack Stein/Ceph Mimic deployed with kolla-ansible on ubuntu-1804 > (kernel 5.4) > isolcpus 4-127 on compute > vcpu_pin_set 4-127 in nova.conf > > image_metadatas: > hw_scsi_model: virtio-scsi > hw_disk_bus: scsi > flavor_metadatas: > hw:cpu_policy: dedicated > > What we have tested: > fio --directory=. --ioengine=libaio --direct=1 > --name=benchmark_random_read_write --filename=test_rand --bs=4k > --iodepth=32 --size=1G --readwrite=randrw --rwmixread=50 --time_based > --runtime=300s --numjobs=16 > > 1. First we run the fio test above on a guest VM, we see average 5K/5K > read/write IOPS consistently. What we realize is that during the test, > one single core on compute host is used at max, which is the first of > the pinned cpus of the guest. 'top -Hp $qemupid' shows that some > threads (notably tp_librbd) share the very same core throughout the > test. (also emulatorpin set = vcpupin set as expected) > 2. We remove isolcpus and every other configuration stays the same. > Now fio tests now show 11K/11K read/write IOPS. No bottlenecked single > cpu on the host, observed threads seem to visit all emulatorpins. > 3. We bring isolcpus back and redeploy the cluster with Train/Nautilus > on ubuntu-1804. Observations are identical to #1. > 4. We tried replacing vcpu_pin_set to cpu_shared_set and > cpu_dedicated_set to be able to pin emulator cpuset to 0-4 to no > avail. Multiple guests on a host can easily deplete resources and IOPS > drops. > 5. Isolcpus are still in place and we deploy Ussuri with kolla-ansible > and Train (to limit the moving parts) with ceph-ansible both on > ubuntu-1804. Now we see 7K/7K read/write IOPS. > 6. We destroy only the compute node and boot it with ubuntu-2004 with > isolcpus set. Add it back to the existing cluster and fio shows > slightly above 10K/10K read/write IOPS. > > > What we think happens: > > 1. Since isolcpus disables scheduling between given cpus, qemu process > and its threads are stuck at the same cpu which created the > bottleneck. They should be runnable on any given emulatorpin cpus. > 2. Ussuri is more performant despite isolcpus, with the improvements > made over time. > 3. Ubuntu-2004 is more performant despite isolcpus, with the > improvements made over time in the kernel. > > Now the questions are: > > 1. What else are we missing here? > 2. Are any of those assumptions false? > 3. If all true, what can we do to solve this issue given that we > cannot upgrade openstack nor ceph on production overnight? > 4. Has anyone dealt with this issue before? > > We welcome any opinion and suggestions at this point as we need to > make sure that we are on the right path regarding the problem and > upgrade is not the only solution. Thanks in advance. > > > > ------------------------------ > > Message: 2 > Date: Tue, 27 Dec 2022 07:00:30 -0800 > From: Dave Wilde <dwilde(a)redhat.com> > To: openstack-discuss(a)lists.openstack.org > Subject: [keystone][Meeting] Reminder Keystone meeting is cancelled > today > Message-ID: > <CAJEkJ+qYCHZayR-t9w4e=ZB846CZSrggcqdYKE85fWkj2XAo5w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Just a quick reminder that there won?t be the keystone weekly meeting > today. We?ll resume our regulararly scheduled programming on 03-Jan-2023. > Please update the agenda if you have anything you?d like to discuess. The > reviewathon is also cancelled this week, to be resumed on 06-Jan-2023. > > /Dave >

2 years, 7 months

[all][tc] What's happening in Technical Committee: summary 19th Nov, 21: Reading: 10 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We cancelled this week's meeting due to Open Infra Keynotes at the same time. * Next week's meeting is on IRC on 25th Nov, Thursday 15:00 UTC, feel free the topic on the agenda[1] by Nov 24th. 2. What we completed this week: ========================= * Updated Yoga testing runtime [2] * Retire puppet-senlin[3] * Removed TC office hours in favour of weekly meetings [4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. Open Reviews ----------------- * 8 open reviews for ongoing activities[6]. Fixing Zuul config error -------------------------- Clark sent a email tagging projects need action for zuul config error in their projects[7]. Please fix those config error which is not causing failure now but will fail on changes in those repo or at least is not testing what we think they are. Few projects are fixing those but still we need to clean it up completly. RBAC discussion: continuing from PTG ---------------------------------------------- We had another meeting on Wed and figured out the open question and schedule. Meeting notes are in this etherpad[8]. Final design and schedule is up in this goal rework patch[9]. Please review that and provide feedback from your project perspective. Community-wide goal updates ------------------------------------ * RBAC goal is pretty much in good shape now, feel free to review it[9] * There is one more goal proposal for 'FIPS compatibility and compliance' which needs feedback from community as well from TC[10]. * TC is working to prepare the final goal(s) soon, please wait for some more time. Adjutant need maintainers and PTLs ------------------------------------------- We received response from Braden, Albert on ML, so let's wait on the final call to help here[11]. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG, we are ok to have Skyline as official project but we have few open queries on gerrit and still waiting from skyline team to respond[12]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[13]. Project updates ------------------- * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’[14] * Retire training-labs repo[15] * Add ProxySQL repository for OpenStack-Ansible[16] * Retire js-openstack-lib [17] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/815851 [3] https://review.opendev.org/c/openstack/governance/+/817329 [4] https://review.opendev.org/c/openstack/governance/+/817493 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025758… [8] https://etherpad.opendev.org/p/policy-popup-yoga-ptg [9] https://review.opendev.org/c/openstack/governance/+/815158 [10] https://review.opendev.org/c/openstack/governance/+/816587 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [12] https://review.opendev.org/c/openstack/governance/+/814037 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [14] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [15] https://review.opendev.org/c/openstack/governance/+/817511 [16] https://review.opendev.org/c/openstack/governance/+/817245 [17] https://review.opendev.org/c/openstack/governance/+/807163 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting-gmann

3 years, 8 months

[all][tc] What's happening in Technical Committee: summary 10 June 2022: Reading: 5 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We cancelled this week's meeting. The next TC weekly meeting will be on 16 June Thursday at 15:00 UTC, feel free to add the topic to the agenda[1] by 15 June. 2. What we completed this week: ========================= * Added community infrastructure contributor help in upstream investment[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], many items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[4]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[5]. Improve project governance --------------------------------- Slawek has the framework proposal up and is under review[6]. New ELK service dashboard: e-r service ----------------------------------------------- No update this week. Consistent and Secure Default RBAC ------------------------------------------- We called for the operator's feedback on RBAC new directions, I sent an email about it[7] and also created etherpad to collect feedback in a central place[8]. My humble request is to use this central etherpad for feedback/discussion otherwise it might be difficult for me to collect/know feedback conclusions from a lot of 100s places. We have feedback from the berlin summit but we still encourage operators/local events or so keep adding the feedback and your view on RBAC. Please note that operator feedback is very important for us to proceed on 'scope' in SRBAC. If you are operator or know anyone around you, we request you to provide feedback. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[10]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11][12]. Project updates ------------------- * None 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/843749 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [6] https://review.opendev.org/c/openstack/governance/+/839880 [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028878.html [8] https://etherpad.opendev.org/p/rbac-operator-feedback [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

3 years, 1 month

Re: [cinder] 2025.2 PTG reminder and schedule

by Goutham Pacha Ravi

On Tue, Apr 8, 2025 at 9:16 AM Jon Bernard <jobernar(a)redhat.com> wrote: > > On Apr 07, Goutham Pacha Ravi <gouthampravi(a)gmail.com> wrote: > > Hey Jon, > > > > On Mon, Apr 7, 2025 at 1:41 PM Jon Bernard <jobernar(a)redhat.com> wrote: > > > > > Hello all, > > > > > > We covered the schedule in last week's meeting but I wanted to post it > > > here for reference. For Cinder, we are meeting Wednesday, Thursday, and > > > Friday of this week from 14:00 UTC until 16:00 UTC. > > > > > > Notable cross-projects sessions are: > > > > > > Glance/Cinder/Nova Wednesday 14h --> 15h UTC > > > Neutron/Cinder/Nova Thursday 13h --> 14h UTC > > > > > > Please note that the Neutron/Nova session is the hour *before* our > > > session block. > > > > > > As we did in the previous PTG, we'll be using the same google > > > meet link and the sessions will be recorded. Everything should be noted > > > in the etherpad. If you notice something is missing please add it or > > > reach out with any questions. See you all in a couple of days! > > > > > > > > Could you or someone from the team please use the bot [2] on > > #openinfra-events to: > > > > 1) book a “room” (i.e. put this on the calendar) > > 2) Update the etherpad and URL you intend to use for the meeting > > Thanks for the reminder, all done. > > > It may have been brought up before, but do note that > > https://meetpad.opendev.org is quite capable of hosting group meetings well > > for the past year at least. Google Meet isn’t a very accessible platform > > since it’s restricted in several countries. While you may not have > > participants from those countries, it’s still worth using open source tools > > where possible/available. > > Ok, I know we had some issues in the past, but we'll give meetpad a go. > Thanks for the information. ++ Thank you. Some "downsides" that I've encountered with Meetpad/Jitsi, but I've gotten used to these: - Recordings aren't announced like other meeting tools, so moderators must do that in case people are uncomfortable being on video, or having their voice recorded - Recordings are limited to 60 minutes - you'll need to restart recording if one has finished - Recordings will rely on recording your own view: - If you end the call or close the window accidentally, the recording is gone, so end recording manually before ending the call - If you're editing a shared document, be sure to focus where the presenter is speaking about - all your actions, such as opening the chat window, or the attendees view will be captured, so do it less often or use another window - Rely on your microphone to do any background noise cancelation and remind your attendees to mute their mics if they're not actively speaking; Jitsi's noise suppression feature is pretty low-fi > > -- > Jon >

3 months, 3 weeks

[all][tc] What's happening in Technical Committee: summary 2022 Nov 18: Reading: 5 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * * We had this week's meeting on Nov 16. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html * Next week (Nov 23) TC weekly meeting is canceled[1]. 2. What we completed this week: ========================= * Defined process for the TC chair nomination & election[2] * Updated the 2023.1 cycle testing runtime[3] * Documented the upgrade patch testing in PTI[4] * Added zookeeper role under OpenStack-Ansible governance[5] * TC stopped using Storybooard. We were not using it for many cycles but TC officially decided [6] to clear all story and close the governance repo in Storyboard[7]. We will not use any other task tracking tool, etherpad or tracking things in meetings are working fine. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[8]. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the syncup call with Board members on Nov 16[10]. We discussed two topic in this call 1. "Less Diversity" and 2. i18 SIG. Most of the discussion was around first topic. There were multiple ideads were shared and discussed including: - Spreading and encouraging the contribution to wider audiance including large deployement, users, company manager. - Making contribution process more easy for part time contributorts. operators etc by helping them in testing requirement, process, half-baked patches to merge. - Reachout out to platinum members company and company executives to know the reason for not contributing in community and explain/encourage them to contribution. There was no concrete action or step to improve the Diversity but we all togehther need to put effort in all direction to improve it slowly. i18 SIG proposal by Brian about Weblate funding which is ~1500 Euro/year and this sounds reasonable to do from foundation but Brian need to write the foaml proposal to foundation before Board meeting on Dec 6th so that it can be discussed there is needed. Thanks Brian for working and following up on this. The next syncup call will be on Feb 2022-02-08 at 20:00 UTC. If anyone is interested, feel free to join it. Renovate translation SIG i18 ---------------------------------- * We discussed it in Board syncup call and Brian will take it forward to put the Weblate funding formal proposal to foundation. TC Video meeting discussion ---------------------------------- Based on the feedback JayF has abandoned the resolution patch[11]. Thanks JayF for proposal and discussion. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[12] * Add the cinder-infinidat charm to Openstack charms[13] * Add the infinidat-tools subordinate charm to OpenStack charms[14] * Add the manila-infinidat charm to Openstack charms[15] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/tc/reference/tc-chair-elections.html [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03122… [4] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [5] https://review.opendev.org/c/openstack/governance/+/863161 [6] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html#… [7] https://review.opendev.org/c/openstack/project-config/+/864771 [8] https://etherpad.opendev.org/p/tc-2023.1-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2022-11-board-openstack-sync [11] https://review.opendev.org/c/openstack/governance/+/863685 [12] https://review.opendev.org/c/openstack/governance/+/863166 [13] https://review.opendev.org/c/openstack/governance/+/863958 [14] https://review.opendev.org/c/openstack/governance/+/864067 [15] https://review.opendev.org/c/openstack/governance/+/864068 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

2 years, 8 months

Re: openstack-discuss Digest, Vol 15, Issue 1

by Soniya Vyas

> Message: 4 > Date: Tue, 31 Dec 2019 19:03:22 -0600 > From: Ghanshyam Mann <gmann(a)ghanshyammann.com> > To: "openstack-discuss" <openstack-discuss(a)lists.openstack.org> > Subject: [qa] QA Office hour new timing for 2020 > Message-ID: > <16f5ea0ef6f.1010065b175496.3744470588375359656(a)ghanshyammann.com> > Content-Type: text/plain; charset="UTF-8" > > Hello Everyone, > > We have few members who actively started contribution to QA from India as well as from Europe TZ. > The current office hour time is more convenient for CT and JST only and very difficult for members from India > Europe to join. > > I would like to adjust office hour timing to include all four TZs. To do that someone has to wake up early or stay > late at night :). I gave preference to new members and selected Tuesday 13.30 UTC [1]. which will be an early morning > for me and late-night in Tokyo. > > let me know if any objection or better suggestion. Accordingly, I will make the new time effective from 7th Jan. > > Also cancelling the 1st Jan office hour and wish you all a very happy new year. > > [1] https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=… Thanks a lot to whole QA team and Ghanshyam Mann for considering our timing issues. Looking forward to join QA Office hours meeting. Regards, Soniya Vyas

5 years, 7 months

[election][cinder] PTL Candidacy for Yoga

by Brian Rosmaita

Hello everyone, I'd like to announce my candidacy for Cinder PTL for the Yoga cycle. The primary challenge we face in the Cinder community continues to be that our reviewing bandwidth has declined at the same time third-party driver contributions have not decreased. As I see it, the problem is that many vendors who maintain third-party drivers do not appear to be clear on the concept of community participation. (For what it's worth, I think this is more a manager problem than a developer problem, but the effect on Cinder is the same, namely, lots of request for reviews and not much doing of reviews. The Cinder documentation has information about how to review, how you don't need to be a core to do valuable reviews, etc., but it's not clear that many people have actually read them.) The Cinder community has tried to address this participation deficit in Xena by providing more upstream activities for contributors (for example, the monthly Festival of XS reviews [0] and the weekly Bug Squad meetings [1]), and these have had decent participation. In Yoga, I'd like to explore having some kind of Review Squad meeting to give people a chance to get "live" feedback on features under development. Some people do use the weekly Cinder meeting for this, but not everyone takes advantage of that, plus weekly meeting time is limited. I hate to propose yet another team meeting, but on the other hand, the bug squad and festival of reviews meetings are extremely productive, so I don't mind proposing another *productive* meeting. (We'll simply cancel it if it turns out that people don't take advantage. Also, I'm open to other ideas ... the key issue is providing faster feedback and more visibility for people developing cinder features, and allowing cinder cores to use their review time productively. So two key issues.) On the positive side, we did add a new cinder core during Xena and there's another person right on the verge of being proposed as a core. So that will help address review bandwidth, though I want to stress that non-core reviews are extremely important to the project as well. Our core reviewers also develop features and fix bugs--they are not full-time code reviewers. And the way to become a cinder core is to review widely in the project and demonstrate a good breadth of knowledge of the software. (As always, anyone currently working on cinder project who's interested becoming a cinder core, please contact me (or any of the current cores) to discuss what the expectations are.) Also on the good side is that we've done quite a bit of work on the Cinder CI this cycle. (I'm not going to tempt fate by saying anything more about that.) With respect to the details of Cinder development in Yoga, I expect those to emerge from our virtual PTG discussions in October. You can help set the agenda here: https://etherpad.opendev.org/p/yoga-ptg-cinder-planning To summarize, I would like to continue working on improving the review throughput of the Cinder team and find additional ways to get people more thoroughly involved in the project. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita) [0] http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews [1] http://eavesdrop.openstack.org/#Cinder_Bug_Squad_Meeting

3 years, 11 months

openstack-discuss search results for query "canceled meeting"