- openstack-discuss - lists.openstack.org

[ptl][release] Wrapping up Victoria
by Sean McGinnis 05 Oct '20

05 Oct '20

Hey everyone, We are getting close to being done with the Victoria development cycle. This is one more reminder that there are just a few days left to finish up any critical work. This Thursday, October 8, is the deadline for any new release candidate releases for any cycle-based services. After Thursday, no new releases should occur for Victoria development until the final coordinated release next Wednesday. After this Thursday, the release team will be proposing a patch to re-tag the last RC release of each deliverable to be the final version for Victoria. We encourage PTLs to +1 this patch to capture that metadata with the release. This is not the time to -1 the patch and ask for more time to push anything final in. After this Thursday, we should basically be done with Victoria development. Only if there is a very, very critical issue discovered will we allow any updates after Thursday and before the final release next Wednesday. Any other bugfixes and important updates will need to wait until after next week's coordinated release to be part of a stable release off of the stable/victoria branch. Please let us know if you have any questions as we wrap things up. --- Sean McGinnis and the entire Release Management Team

1 0

[neutron] Bug deputy report for week of September 28th
by Lajos Katona 04 Oct '20

04 Oct '20

Hi, I was Neutron bug deputy the week before, below is a short summary of the week's reported bugs. - Critical Bugs - https://bugs.launchpad.net/neutron/+bug/1897713 (networking-ovn-tempest-dsvm-ovs-release job fails on stable/train) *Fixed* - https://bugs.launchpad.net/neutron/+bug/1897898 (Scenario test test_multiple_ports_portrange_remote is unstable ) *Unassigned* - https://bugs.launchpad.net/neutron/+bug/1898211 (OVN scenario jobs are failing on Ubuntu Focal due to ebtables-nft used by default ) *In Progress* - High Bugs - https://bugs.launchpad.net/neutron/+bug/1897796 (Scenario test test_subport_connectivity failing from time to time) *Assigned, in Progress* - https://bugs.launchpad.net/neutron/+bug/1897637 (explicity_egress_direct prevents learning of local MACs and causes flooding of ingress packets ) *In Progress*, perhaps duplicate of https://bugs.launchpad.net/neutron/+bug/1884708 - Medium Bugs - https://bugs.launchpad.net/neutron/+bug/1897921 ([OVN] "test_agent_show" failing, chassis not found ) *Fixed* - https://bugs.launchpad.net/neutron/+bug/1897928 (TestOvnDbNotifyHandler test cases failing due to missing attribute "_RowEventHandler__watched_events" ) *Fixed on Master* - Low Bugs - https://bugs.launchpad.net/neutron/+bug/1897546 (binding_levels property is missing from openstack port show command) - Not fully confirmed Bugs - https://bugs.launchpad.net/neutron/+bug/1897580 (SG rules aren't properly applied if CIDR of the tenant network is also matches the host network CIDR), I check it next week again. Iwas a much relaxed week in numbers. One critical bug is unassigned: https://bugs.launchpad.net/neutron/+bug/1897898 Regards Lajos Katona (lajoskatona)

1 0

[all][dev] Python.h not found after openstack-tox-py36 is switch to CentOS8
by Akihiro Motoki 04 Oct '20

04 Oct '20

Hi, openstack-tox-py36 is now run on CentOS-8 after commit 31c4a7a18e2bd43d2893563b992c683c95baed6f was merged. I noticed Python.h is not installed so we cannot install python modules which require compilation. An example is found at [1]. Do individual projects explicitly install python-dev or will we handle it in the common zuul job? Before proposing a fix, I would like to hear our direction. [1] https://zuul.opendev.org/t/openstack/build/696978c5614c41bd88b5b2a1d6c2174a… Thanks, Akihiro Motoki (irc: amotoki)

5 5

Ussuri Octavia load balancer on OVS
by pwm 04 Oct '20

04 Oct '20

Hi, I using the following setup for Octavia load balancer on OVS Ansible openstack_user_config.yml - network: container_bridge: "br-lbaas" container_type: "veth" container_interface: "eth14" host_bind_override: "eth14" ip_from_q: "octavia" type: "flat" net_name: "octavia" group_binds: - neutron_openvswitch_agent - octavia-worker - octavia-housekeeping - octavia-health-manager user_variables.yml octavia_provider_network_name: "octavia" octavia_provider_network_type: flat octavia_neutron_management_network_name: lbaas-mgmt /etc/netplan/50-cloud-init.yaml br-lbaas: dhcp4: no interfaces: [ bond10 ] addresses: [] parameters: stp: false forward-delay: 0 bond10: dhcp4: no addresses: [] interfaces: [ens16] parameters: mode: balance-tlb brctl show bridge name bridge id STP enabled interfaces br-lbaas 8000.d60e4e80f672 no 2ea34552_eth14 bond10 However, I am getting the following error when creating the load balance octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying.: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='172.29.233.47', port=9443 The Octavia api container unable to connect to the amphora instance. Any missing configuration, cause I need to manually add in the eth14 interface to the br-lbaas bridge in order to fix the connection issue brctl addif br-lbaas eth14 Thanks

2 9

[neutron][requirements] RFE requested for neutron-lib
by Lajos Katona 02 Oct '20

02 Oct '20

Hi, I would like to ask Requirements Freeze Exception for neutron-lib 2.6.1 for Neutron Victoria. neutron-lib 2.6.1 contains a bug fix for Neutron which solves a nova gate issue (on Victoria) coming from a new feature in neutron, see [1]. [1] https://bugs.launchpad.net/neutron/+bug/1882804 (RFE: allow replacing the QoS policy of bound port) Thanks in advance Lajos Katona (lajoskatona)

4 3

[tripleo] TripleO CI Summary: Unified Sprint 33
by Rafael Folco 02 Oct '20

02 Oct '20

Greetings, The TripleO CI team has just completed **Unified Sprint 33** (Sept 11 thru Oct 01). The following is a summary of completed work during this sprint cycle: - Added more jobs to RHOS 16.2 pipelines. - Applied new promoter configuration engine changes to consolidate all promoters into the same code. - Started a PoC implementation of the new dependency pipeline: - https://hackmd.io/iA6AyTn8Rn2ximODx6FmKg - Started elastic-recheck containerization work: - https://hackmd.io/HQ5hyGAOSuG44Le2x6YzUw - Created upstream parent jobs a.k.a content-provider to build containers for multiple jobs: - https://hackmd.io/vRMVeZXZRgK5Vxqi6ENUDg#QampA - Ruck/Rover recorded notes [1]. The planned work for the next sprint puts on hold the work started in the previous sprint and focuses on the following: - Add content-provider jobs to all CI layouts and templates. - Start prep work for stable/victoria branching in RDO. - Continue investigations to fix broken upgrade jobs. The Ruck and Rover for this sprint are Ronelle Landy (rlandy) and Soniya Vyas (soniya29). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [2]. Thanks, rfolco [1] https://hackmd.io/7Q0YO5JKS0agcf9qwoD4IQ <https://hackmd.io/7Q0YO5JKS0agcf9qwoD4IQ> [2] https://hackmd.io/1qxCqYzATfudl1cKvaQ8-w -- Folco

1 0

[oslo] PTO next week
by Ben Nemec 02 Oct '20

02 Oct '20

I will be on PTO next week so I won't be around to run the meeting. This might be a good time to start implementing our DPL approach, if someone else wants to pick up the job of meeting coordinator. I believe Herve had mentioned some interest in that. Anyway, I won't be here and I'm stepping down as PTL so y'all can do what you want. ;-) -Ben

2 1

Neutron DVR, service subnets and public IPs
by Taltavull Jean-Francois 02 Oct '20

02 Oct '20

Hi All, Has someone already used successfully neutron service subnets, in a DVR deployment, in order to save internet public IP addresses ? Regards, Jean-Francois

1 0

[tc] weekly meeting
by Mohammed Naser 02 Oct '20

02 Oct '20

Hi everyone, Here’s a summary of what happened in our TC monthly meeting last Thursday, October 1st. # ATTENDEES (LINES SAID) - mnaser (100) - gmann (24) - evrardjp (18) - mugsie (18) - belmoreira (12) - diablo_rojo (11) - njohnston (5) - knikolla (5) - ralonsoh (4) - jungleboyj (4) - fungi (4) - ttx (3) - ricolin_ (3) - openstack (3) - smcginnis (2) - cloudnull (1) # MEETING SUMMARY 1. Roll call (mnaser, 14:00:07) 2. Follow up on past action items (mnaser, 14:07:07) - http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-09-03-14.01.html (mnaser, 14:07:24) 3. OpenStack User-facing APIs and CLIs (belmoreira) (mnaser, 14:34:35) 4. W cycle goal selection start (mnaser, 14:41:19) 5. Completion of retirement cleanup (gmann) (mnaser, 14:47:51) - https://storyboard.openstack.org/#!/story/2007686 (ralonsoh, 14:47:52) 6. Audit and clean-up tags (gmann) (mnaser, 14:48:23) - https://review.opendev.org/#/c/749363/ (mnaser, 14:48:28) 7. PTG Planning (mnaser, 14:50:54) - https://etherpad.opendev.org/p/tc-wallaby-ptg (mnaser, 14:51:02) 8. Open discussion (mnaser, 14:53:20) 9. Meeting ended at 14:59:58 UTC # ACTION ITEMS - diablo_rojo schedule session with sig-arch and k8s steering committee - mugsie Drive Wallaby cycle community goals - belmoreira draft up title, abstract and moderator for OSC gaps session - mugsie reach out to ralonsoh wrt helping with privsep - gmann to start cleaning-up assert:supports-api-interoperability tag To read the full logs of the meeting, please refer to http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-10-01-14.00.log.html Thanks! Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[usurri][linbit][drbd] Cinder configuration
by ops＠clustspace.com 02 Oct '20

02 Oct '20

Hello, Does anyone have manuall how to configure drbd+linstor for cinder? Official documentation is very crap. We already tryed week for it and without any results

2 1

[release] Release countdown for week R-1 Oct 5-9
by Sean McGinnis 02 Oct '20

02 Oct '20

Development Focus ----------------- We are on the final mile of the victoria development cycle! Remember that the victoria final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. October 8 is the deadline for final victoria release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 14. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the Wallaby cycle, including discussing Forum and PTG sessions content, in preparation of Open Infra Summit the week of Oct 19 and the PTG on the week of Oct 26. Actions ------- Watch for any translation patches coming through on the stable/victoria branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/victoria branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release! Upcoming Deadlines & Dates -------------------------- Final Victoria RC deadline: October 8 Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[election][plt] Hervé Beraud candidacy for Release Management PTL
by Herve Beraud 02 Oct '20

02 Oct '20

Hello everyone, I am submitting my candidacy for Release Management team PTL in the Wallaby cycle. Indeed, I am a core Release Management team member for a few cycles now and I want to involve myself more in this team by proposing me as PTL. During this cycle the main efforts will be around the team building. Indeed, we now have a lot of great tools and automations but we need to recruit new members and mentor them to keep a strong and resilient core team. By recruiting more people we could easily spread the workload on more core members. I plan to dedicate myself on this topic during this cycle. Thanks for your consideration! Hervé -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

2 3

[Gnocchi-api] Gnocchi-api can not be found
by WALSH CHANG 01 Oct '20

01 Oct '20

To whom it may concern, I got the error message when I restart gnocchi-api as the official installation guide. Here is the error message I got root@c3macserver2:~# service gnocchi-api start Failed to start gnocchi-api.service: Unit gnocchi-api.service not found. root@c3macserver2:~# whereis gnocchi-api gnocchi-api: /usr/bin/gnocchi-api gnocchi-api is already the newest version (4.3.2-0ubuntu2~cloud0). Someone said the new version doesn't include the gnocchi-api, so I am trying to install the previous version. https://stackoverflow.com/questions/47520779/service-gnocchi-api-not-found Need the help to install the previous version of gnocchi-api. My openstack version : stein Ubuntu 18.0.4 Thanks. Kind regards, Walsh

1 0

user read-only role not working
by its-openstack＠zohocorp.com 01 Oct '20

01 Oct '20

Dear Openstack, We have deployed openstack train branch. This mail is in regards to the default role in openstack. we are trying to create a read-only user i.e, the said user can only view in the web portal(horizon)/using cli commands. the user cannot create an instance or delete an instance , the same with any resource. we created a user in a project test with reader role, but in horizon/cli able to create and delete instance and similar to other access also if you so kindly help us fix this issue would be grateful. the commands used for creation $ openstack user create --domain default --password-prompt mailto:test-reader@test.com $ openstack role add --project test --user mailto:gowtham.sankar@zohocorp.com reader Thanks and Regards sysadmin

3 2

[neutron] Drivers meeting 02.10.2020 cancelled
by Slawek Kaplonski 01 Oct '20

01 Oct '20

Hi, Due to no agenda items for our tomorrow's drivers meeting, I'm cancelling it for this week. See You on the meeting next week. Have a great weekend :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder][ops] new cinder stable releases address upgrade bug
by Brian Rosmaita 01 Oct '20

01 Oct '20

Greetings: The Cinder project has two new stable releases: - 16.2.0 (Ussuri) - 15.4.0 (Train) (we also have a new Stein, 14.3.0, but it's not relevant to this discussion) Among other things, these address Bug #1893107 [0], which could prevent a cinder database upgrade from Train to Ussuri when the database in question had been (a) unpurged and (b) originally upgraded from Stein to Train. (A purged Stein database upgraded to Train, or a database that was new in Train, would not be subject to this issue.) The 16.2.0 [1] and 15.4.0 [2] release notes outline some strategies for addressing this issue. We recommend that you read both before attempting an upgrade to Ussuri and decide which strategy works best for you and your users. (Of course, you always read all the release notes, but we figured it wouldn't hurt to bring this particular point to your attention.) Thank you for your attention to this matter! [0] https://bugs.launchpad.net/cinder/+bug/1893107 [1] https://docs.openstack.org/releasenotes/cinder/ussuri.html#relnotes-16-2-0-… [2] https://docs.openstack.org/releasenotes/cinder/train.html#relnotes-15-4-0-s…

1 0

[OpenStack-Ansible][OSA][Docs] Project missing from deployment page
by Amy Marrich 01 Oct '20

01 Oct '20

Hey all, Looks like OpenStack-Ansible has dropped from the deployment section again:( https://docs.openstack.org/ussuri/deploy/ Any suggestions on what we need to patch to get back on the page? Thanks, Amy

3 3

[kolla] No Kall today
by Radosław Piliszek 01 Oct '20

01 Oct '20

Hi, Folks! Sorry for the very late notice: today's Kolla Kall is cancelled due to priority of Victoria release reviews. Thank you for understanding. -yoctozepto

1 0

[sahara][stable] EOL Ocata and Pike
by Jeremy Freudberg 01 Oct '20

01 Oct '20

Hello all, I am announcing the intention to EOL the stable/ocata and stable/pike branches for all branched Sahara deliverables. It has been discussed within the Sahara team a couple times, and it was most recently discussed today [*]. Any objections? Thanks, Jeremy [*] http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-10-01-14.01…

1 0

[cloudkitty][election][ptl] PTL non-candidacy
by Pierre Riteau 01 Oct '20

01 Oct '20

Hello, Late in the Victoria cycle, I volunteered to help with the then inactive CloudKitty project, which resulted in becoming its PTL. While I plan to continue contributing to CloudKitty, I will have very limited availability during the beginning of the Wallaby cycle. In particular, I may not even be able to join the PTG. Thus it would be best if someone else ran for CloudKitty PTL this cycle. If you are interested in nominating yourself but aren't sure what is involved, don't hesitate to reach out to me by email or IRC. Thanks, Pierre Riteau (priteau)

3 4

Should ports created by ironic have PXE parameters after deployment?
by Tyler Bishop 01 Oct '20

01 Oct '20

Hi, My issue is i have a neutron network (not discovery or cleaning) that is adding the PXE entries for the ironic pxe server and my baremetal host are rebooting into discovery upon successful deployment. I am curious how the driver implementation works for adding the PXE options to neutron-dhcp-agent configuration and if that is being done to help non flat networks where no SDN is being used? I have several environments using Kolla-Ansible and this one seems to be the only behaving like this. My neutron-dhcp-agent dnsmasq opt file looks like this after a host is deployed. dhcp/7d0b7e78-6506-4f4a-b524-d5c03e4ca4a8/opts cat /var/lib/neutron/dhcp/ffdf5f9b-b4ad-4a53-b154-69eb3b4a81c5/opts tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:dns-server,10.60.3.240,10.60.10.240,10.60.1.240 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:classless-static-route,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,249,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:router,10.60.66.1 tag:port-08908db1-360b-4973-87c7-15049a484ac6,150,10.60.66.11 tag:port-08908db1-360b-4973-87c7-15049a484ac6,210,/tftpboot/ tag:port-08908db1-360b-4973-87c7-15049a484ac6,66,10.60.66.11 tag:port-08908db1-360b-4973-87c7-15049a484ac6,67,pxelinux.0 tag:port-08908db1-360b-4973-87c7-15049a484ac6,option:server-ip-address,10.60.66.11

7 16

[searchlight][election][ptl] PTL non-candidacy
by Trinh Nguyen 01 Oct '20

01 Oct '20

Hi guys, I have been taking the role of Searchlight's PTL since Stein to hopefully making the project sustainable. Over the course of 4 development cycles, I had lots of joy and also learned a lot while doing maintenance & open source contributor recruiting. Unfortunately, I switched to a job that does not involve OpenStack, and that leaves me no time for contributions. That being said, I announce my non-candidacy for the Wallaby cycle. Though not being able to contribute to the project, I'll still be around and help you out whenever I can. Thanks, -- *Trinh Nguyen* *dangtrinh.com <https://dangtrinh.com>*

2 1

[nova][neutron] The nova-next job is broken on master
by Balázs Gibizer 01 Oct '20

01 Oct '20

Hi, The post_test_hook part of the nova-next job is broken[1] on master blocking the nova gate. Please hold your rechecks. We need a new neutronlib release containing the fix [2] to make the job pass. Until that I proposed a patch that temporary disable the failing test steps[3]. Cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1898035 [2] https://review.opendev.org/#/c/753230 [3] https://review.opendev.org/#/c/755498

1 0

[tripleo] Image build error with missing osops-tools-monitoring-oschecks in CentOS 8
by Ruslanas Gžibovskis 01 Oct '20

01 Oct '20

Hi all, in file: /usr/share/tripleo-puppet-elements/overcloud-opstools/pkg-map should be added before "default", on line 9 following text, to support CentOS 8: "release": { "centos": { "8": { "oschecks_package": "" } } }, so it would not search for osops-tools-monitoring-oschecks not sure where to submit an update, sending here, someone who knows what and where, can do or I can submit it just name where. -- Ruslanas Gžibovskis +370 6030 7030

2 3

[tc] monthly meeting
by Mohammed Naser 30 Sep '20

30 Sep '20

Hi everyone, Here’s the agenda for our monthly TC meeting. It will happen tomorrow (Thursday the 1st) at 1400 UTC in #openstack-tc and I will be your chair. If you can’t attend, please put your name in the “Apologies for Absence” section. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * ACTIVE INITIATIVES - Follow up on past action items - OpenStack User-facing APIs and CLIs (belmoreira) - W cycle goal selection start - Completion of retirement cleanup (gmann) https://etherpad.opendev.org/p/tc-retirement-cleanup - Audit and clean-up tags (gmann) - Remove tc:approved-release tag https://review.opendev.org/#/c/749363/ Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[election][horizon] PTL candidacy for Wallaby
by Ivan Kolodyazhny 30 Sep '20

30 Sep '20

Hi team, I would like to announce my candidacy for Horizon PTL for the Wallaby cycle. During Victoria cycle we did a good job with stability improvements and feature development but there are still some areas we need to pay attention during Wallaby development cycle: * More cross-project testing. * Find a solution on how to improve UX and make feature gap smaller. * Involve more contributors into the community. Thanks for reading this and helping me making Horizon better during each release, Ivan Kolodyazhny (e0ne)

1 0

[manila] GHC / Canceling the IRC Meeting this week (1st Oct 2020)
by Goutham Pacha Ravi 30 Sep '20

30 Sep '20

Hello Zorillas, A number of us are mentoring attendees of the "Open Source Day" at the Grace Hopper Celebration tomorrow (1st Oct 2020). Since the agenda [1] had no new items, we'll forego the meeting slot and convene next week instead. If there's anything urgent that needs to be discussed, please share your thoughts on #openstack-manila, or as an email here. If you're available tomorrow, and would like to help with GHC as a mentor, please see Amy's email to the list. [2] Thanks, Goutham [1] https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01768…

1 0

[election][charms] PTL candidacy for Wallaby
by Frode Nordahl 30 Sep '20

30 Sep '20

Hello all, I hereby announce my candidacy for PTL for the Charms project. There is a lot of good movement in the community and I'm really excited about what the next cycle might bring. Apologies for missing the nomination deadline. -- Frode Nordahl

1 0

Mentors needed Tomorrow!!!!
by Amy Marrich 30 Sep '20

30 Sep '20

Hey all, Found out over night the OpenStack session at Grace Hopper Conference's Open Source Day has 78 mentees registered and we have 6-8 stackers mentoring through the day. If you've ever wanted to help mentor the next hopeful generation of Stackers please let me know. We are working to adapt our plans for the day and do have the option of sending some to another track but that's not the OpenStack way! Thanks, Amy (spotz)

2 3

[election][telemetry] PTL candidacy for Wallaby
by Matthias Runge 30 Sep '20

30 Sep '20

Hi there, I'd like to announce my candidacy to become the next PTL for OpenStack Telemetry for the Wallaby cycle. In the past cycles, we have seen a decrease in contribution for Telemetry related projects. We have also seen the lengthy discussion around gnocchi or the lack of a TSDB in OpenStack. A few months ago, I joined the project and helped with reviews and bug fixes. For the next cycle, I would like to address the a few short term but also some longer term issues such as: - finish cleaning up the python2 to python3 migration. - get a better understanding (and a solution) for the various telemetry gates being blocked - recently, heat stopped testing auto-scaling via aodh and gnocchi, because it was too unstable. I'd like to address that as well. - We haven't had a planning or a roadmap for about the last 1.5 cycles. That is something to do in the future. Thank you for your support and your consideration. Matthias Runge

1 1

Make Full Disks read-only in swift object storage
by Hamidreza Hosseini 30 Sep '20

30 Sep '20

Hi, I've some disks on my swift object storage that they filled and I made them read only by /etc/fstab I think this isn't true adjustment, Anyway, can I solve this problem (I mean full disks ) without changing the ring and just by configuring the proxy to send put /get requests to empty disks but just Get requests to empty disk? Best regards.

1 0

[ironic] Proposing returning Jay Faulkner to ironic-core
by Julia Kreger 30 Sep '20

30 Sep '20

Greetings ironic contributors, I'm sure many of you have noticed JayF has been more active on IRC over the past year. Recently he started reviewing and providing feedback on changes in ironic-python-agent as well as some work to add new features and fix some very not fun bugs. Given that he was ironic-core when he departed the community, I believe it is only fair that we return those rights to him. Any objections? -Julia

6 5

Question about faafo
by Jesus Aransay 30 Sep '20

30 Sep '20

Dear all, I know that faafo ( https://opendev.org/openstack/faafo ) is no longer being maintained, but I still use it to present some service deployment in my teaching about cloud systems. The application still runs nicely in Ubuntu1804, but I tried to configure the RabbitMQ queue to be created in the publisher (Service API), instead of in the consumers (Service Worker), but I failed. My intention was to show that messages could be published in the queue without any workers having been deployed yet. I thought adding a "maybe_declare" statement in the publisher "would do the trick": https://github.com/jmaransay/faafo/blob/478428f11d92cc22d1be396afec3c787136… But still the message queue is only created when the first worker machine is deployed. Does anybody still have some clue about why the application was configured like that, or how the queue could be created in the publisher? Any hints would be highly appreciated, thank you very much in advance, Jesús -- Jesús María Aransay Azofra Universidad de La Rioja Dpto. de Matemáticas y Computación tlf.: (+34) 941299438 fax: (+34) 941299460 mail: jesus-maria.aransay(a)unirioja.es web: http://www.unirioja.es/cu/jearansa Edificio Científico Tecnológico-CCT, c/ Madre de Dios, 53 26006, Logroño, España

1 0

[masakari][tc][elections] yoctozepto mode on
by Radosław Piliszek 29 Sep '20

29 Sep '20

Hello, Folks! Letting you know I have proposed myself for TC member [1] and Masakari PTL positions [2]. Please find the relevant letters in references. Thank you for your time. [1] https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby… [2] https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby… -yoctozepto

4 3

[all][elections][ptl][tc] Combined PTL/TC Nominations End
by Jeremy Stanley 29 Sep '20

29 Sep '20

The PTL and TC Nomination period is now over. The official candidate list for PTLs is available on the election website[0] as is the candidate list for TC seats[1]. There are 10 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Cloudkitty, Karbor, Octavia, OpenStack_Charms, Oslo, Packaging_Rpm, Placement, Qinling, Searchlight, Senlin. There is 1 project which will have elections: Telemetry. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Oct 06, 2020 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#wallaby-ptl-candidates [1] https://governance.openstack.org/election/#wallaby-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley

1 0

[Diversity] Community feedback on Divisive Language stance
by Amy Marrich 29 Sep '20

29 Sep '20

The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage

2 2

Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 29 Sep '20

29 Sep '20

Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver

3 4

[election][manila] PTL candidacy for Wallaby
by Goutham Pacha Ravi 29 Sep '20

29 Sep '20

Hello Zorillas and all interested stackers, I'd like to submit my candidacy to be the PTL for the OpenStack Manila team through the Wallaby cycle. I am no longer a stranger to this role, and I've had an excellent team to work with during the past two cycles that serving as PTL has become an absolute pleasure besides being an honor. I've learned by experience that a successful project leader is one that has a great team. I seek to lead an aspirational team that goes all distances to grow, as is evidenced by every member spending a substantial amount of their time mentoring new contributors, and providing an on-boarding ramp to OpenStack - whether this is through informal introductions along the sidelines of conferences, or stray explorers finding us on IRC/email, or engaging with invaluable supporters of diversity and curiosity in the likes of Outreachy, Google Summer of Code, and the Grace Hopper Celebration. I seek to lead a committed team that wants to learn and better itself continuously. We've adopted a proactive policy to bug triage that has kept us rooted to users and their pain points; These bug triages have led to effective (and fun) community "doc-a-thon" and "bug-a-thon" events. Many a times, great effort does not result in great glory. I am proud of the work we do to enhance e2e testing. There are no press releases that reflect this, but I assure you that this work matters a lot to our users. I seek to lead an informed team. Innovation arrives here often by standing on the shoulders of the giants. The team works with technology that's been perfected over decades, as well as with novel breakthroughs of the recent years. We participate in adjacent communities, and adapt while also advocating the lessons we learned in this one. So, if you will have me, I wish to serve you through Wallaby and get things done. Apart from our commitment to OpenStack-wide goals, and the improvements we've charted out, I wish to prioritize a few more work items: - Improve fault tolerance - we've identified some gaps in resource health when certain kinds of service disruptions occur, we'll fix these up. - Achieve OpenStackCLI/SDK/UI parity - there's a lot left to do in this space, and we've actively been chipping away at this for the past two cycles. - API policy improvements - work on the "admin-everywhere" problem with the pop-up team and support fine grained policies in tune with the model of multi-tenancy we cater to. Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr

1 0

[baremetal-sig][ironic] Redfish interoperability profiles: status meeting
by Arne Wiebalck 29 Sep '20

29 Sep '20

Dear all, This cycle, the Ironic community has started to work on Redfish interoperability profiles [0]. These profiles allow to describe requirements for a Redfish endpoint and to automatically verify them via tools like [1]. The aim of this activity is to have an easy way for both vendors and operators to validate that specific hardware is compatible with the Redfish support in Ironic. We will be meeting next week to discuss the current status of this activity. A representative from the DMTF (as the defining body for the Redfish standard) has kindly agreed to join us. Everybody interested is welcome, of course: Thu Sep 24 at 12pm UTC https://cern.zoom.us/j/94808950339 Any question, let us know! Cheers, Richard & Arne [0] https://www.dmtf.org/sites/default/files/standards/documents/DSP0272_1.0.0_… [1] https://github.com/DMTF/Redfish-Interop-Validator

1 1

[tripleo][validations] new Validation Framework demos
by Mathieu Bultel 29 Sep '20

29 Sep '20

Hey TripleO, I have recorded three demos with the new Validation Framework (VF): 1st demo is similar to what Gael did few months ago but with the new code refactored (validations-libs/validations-common projects): https://asciinema.org/a/NRLULghjJa87qxRD9Nfq0FYoa 2nd demo is a use of the VF without any openstack/TripleO prerequisite, on a fresh and empty Ubuntu docker container, with only validations-libs and validations-common projects. It shows that only with a apt-get install git and python3-pip and with a basic python project installation we can run validations and use the framework: https://asciinema.org/a/2Jp9LZbN0xhJAR09zIpI6OpuB So it can answer a few demands such as: How to run validations as prep undercloud installation ? How to run validations on a non-openstack project ? What are the bare minimum requirements for being able to run Validations on a system ? May I run Validation remotely from my machine ? etc... The third one is mainly related to the deployment itself of TripleO. By using a simple PoC (https://review.opendev.org/#/c/724289/) I was able to make TripleO consuming the validations-libs framework and validation logging callback plugin. So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage. https://asciinema.org/a/344484 https://asciinema.org/a/344509 Mathieu.

4 5

[all] Switch to python3-pycryptodome
by Thomas Goirand 29 Sep '20

29 Sep '20

Hi, A number of bug reports have been filled against the Debian OpenStack packages in Sid: - keystone - python-openstackclient - python-manilaclient - python-ironic-lib - python-oauth2client - python-pysaml2 The content of the bugs is: > Source: python-pysaml2 > Version: 4.5.0-8 > Severity: important > Tags: sid bullseye > Usertags: pycrypto > > Dear maintainer, > > python-pysaml2 currently Build-Depends or Depends on python3-crypto > from PyCrypto. This project is no longer maintained and PyCryptodome > (https://www.pycryptodome.org/en/latest/) provides a drop in > replacement. Please switch to python3-pycryptodome. I'd like to > remove python-crypto before the release of bullseye. > > Cheers So my question is: - Is it really a drop-in replacement, and can it be replaced in the packages (maybe, delta the imports?)? - If not, how much work is this? - Can the OpenStack project also move to pycryptodome? Cheers, Thomas Goirand (zigo)

2 1

[horizon][dev] Horizon.next
by Apsey, Christopher 29 Sep '20

29 Sep '20

Horizon team, I recently picked up a few talented dev interns, and one of them is very interested in webdev and quite skilled. He will have up to 25 hours/week to devote to development tasks of my choosing over the 8 months or so, and I'd like to offer him up as someone who can spend all of his time working with the horizon team on horizon.next (npm-based). We rely on horizon heavily internally, and a better experience for the end-user is pretty high on our list (particularly performance-wise). He has no experience developing in the OpenStack ecosystem, but is otherwise ready to 'get to work' after process/code familiarization. Can anyone on the horizon team offer up some cycles to help get him spun up/integrated? Or is the best bet just pointing him at the IRC channel? Thanks Chris Apsey GEORGIA CYBER CENTER

3 2

Re: [tripleo]] tripleo victoria rc1
by Marios Andreou 28 Sep '20

28 Sep '20

On Mon, Sep 28, 2020 at 10:16 AM Yatin Karel <ykarel(a)redhat.com> wrote: > Hi Marios, > > << we don't normally/aren't expected to cut release candidates. > However after discussion with and guidance from Wes I decided to > propose an rc1 as practice since I << haven't used the new releases > tool before [4]. > << The proposal is up at [1] but I've set -1 there on request from > reviewers; we can't merge that until [2] merges first. > > Is this just about releasing RC Tags or changing the release-model > that tripleo used to follow:- cycle-with-intermediary(cycle-trailing > earlier) vs cycle-with-rc. Maybe you can share more context with the > this is just about bumping the git tags on the projects and not about changing the release model. > discussion points as to what's different this time and reasoning for > the same to have a clear picture. > nothing different wrt the release model - see the diff it is just bumping the hash and version https://review.opendev.org/gitweb?p=openstack%2Freleases.git;a=commitdiff;h… . We are just making a release to coincide with the wider openstack Victoria RC1 even though we aren't expected to follow the rc model with our 'cycle with intermediary' on these projects. > And if possible can you also share what's the plan for GA release for > TripleO like how it will be this time. > So weshay is still PTL, and we haven't discussed this in any great detail, except that we may have to delay a little bit cutting branch and releasing victoria final. Generally with rc tags stable branch is also cut but i don't see that > in https://review.opendev.org/#/c/754346/. And i hope this will not be > right I guess the confusion is that this isn't a proper RC since we don't have those 'officially' .It is just a version bump that coincides with the victoria rc1 milestone end of last week. hope it helps, also, did you forget to reply-all? should i send to the list (just confirmed with ykarel and re-adding list to addresses) thanks, marios > merged until victoria tripleo jobs are ready if cutting > stable/victoria branch. > > On Fri, Sep 25, 2020 at 10:05 PM Marios Andreou <marios(a)redhat.com> wrote: > > > > hello TripleO folks o/ > > > > we don't normally/aren't expected to cut release candidates. However > after discussion with and guidance from Wes I decided to propose an rc1 as > practice since I haven't used the new releases tool before [4]. > > > > The proposal is up at [1] but I've set -1 there on request from > reviewers; we can't merge that until [2] merges first. > > > > If you are interested please check [1] and add any comments. In > particular let me know if you want to include a release for one of the > independent repos [3] (though for validations-common/libs we need to reach > out to the validations team they are managing those AFAIK). > > > > thanks, hope you enjoy your weekend! > > > > [1] https://review.opendev.org/#/c/754346/ > > [2] https://review.opendev.org/754347 > > [3] https://releases.openstack.org/teams/tripleo.html#independent > > [4] > https://releases.openstack.org/reference/using.html#using-new-release-comma… > > Thanks and Regards > Yatin Karel > >

2 2

Re: [all][elections][ptl][tc] Combined PTL/TC Nominations ending in less than 24 hours
by Jeremy Stanley 28 Sep '20

28 Sep '20

Another reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 23:38:26 Nominations progress : 85.93% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 25 ( 45.45%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Barbican* Blazar* Cinder* Cloudkitty Cyborg Designate* Ec2_Api Freezer Horizon Ironic* Karbor Magnum* Manila Masakari Monasca Murano Octavia OpenStack_Charms Oslo Packaging_Rpm Placement Qinling Quality_Assurance* Requirements* Searchlight Senlin Solum Storlets* Telemetry Watcher) =================================================== Stats gathered @ 2020-09-29 00:06:34 UTC (* indicates teams with pending nominations which haven't been confirmed by more than one election official yet) This means that with approximately 2 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. There are also currently 2 confirmed candidates and 3 additional pending nominations for the 4 open Technical Committee seats, indicating it's likely there will be a runoff poll for the TC election. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[election][storlets] PTL candidacy for Wallaby
by Takashi Kajinami 28 Sep '20

28 Sep '20

Hi All, I'd like to announce my candidacy to run PTL role for Storlets project in the next Wallaby cycles, to continue PTL role from the previous Victoria cycle. In this cycle, I'll focus on the existing proposals to improve stability and operability of Storlets. Since we have discussion slots in coming PTG, I'll moderate the discussion there and will try to make these proposals land during this cycle. Thank you for your consideration ! Thank you, Takashi Kajinami

1 0

[election][qa] PTL candidacy for Wallaby
by Masayuki Igawa 28 Sep '20

28 Sep '20

Hi everyone, I want to propose my candidacy and continue serving as Quality Assurance PTL for the Wallaby cycle. First off, I would like to thank you all the contributors, core reviewers, and anyone involved and makes the OpenStack better. In Victoria cycle, we've added a job for generating doc from docstrings and added many docstrings for that already. We can see the outcomes here[2]. And we've also made a workflow[3][4] to get along with the upper-constraints in tox.ini. We still have some more planned work pending for Victoria, such as making tempest scenario manager a stable interface, improving tempest cleanup, etc. I think we will accomplish them in Victoria or Wallaby cycle. Along with daily QA activities, my priorities for QA for the next cycle will be: * Guiding and motivating more contributors to QA projects, improving documentation and advertising OpenStack QA projects. * Stability of Tempest scenario manager. * Completing Victoria priority items if it's still remaining. It's hard to accomplish without our collaboration. So, let's do it together! [1] http://stackalytics.com/?user_id=igawa [2] https://docs.openstack.org/tempest/latest/tests/modules.html [3] https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_… [4] https://wiki.openstack.org/wiki/QA/releases#Project_with_release_mode:_cycl… Thanks for your consideration! -- Masayuki Igawa (masayukig)

1 0

Swift Installation Error
by WALSH CHANG 28 Sep '20

28 Sep '20

To whom it may concern, I am very new to OpenStack. I had an error when I install the Swift service. Error trying to load config from /etc/swift/proxy-server.conf: Entry point 'proxy\naccount_autocreate = True' not found in egg 'swift' (dir: /usr/lib/python2.7/dist-packages; protocols: paste.app_factory, paste.composite_factory, paste.composit_factory; entry_points: ) Just wondering if it's ok to have storage node and controller node on the same device. I use the controller node as the storage node, and use the flash drive as the storage space. Not sure if this is the reason for the error. It will be very appreciated if someone can provide some suggestions. Kind regards, Walsh

2 1

[election][cinder] PTL candidacy for Wallaby
by Brian Rosmaita 28 Sep '20

28 Sep '20

Hello everyone, I hereby announce my candidacy for Cinder PTL for the Wallaby cycle. I've been PTL for two cycles, so you have a pretty good idea by now of what it's like to work on the Cinder project with me in that role, and whether or not it would be a good idea for me to continue. There are a few things I'd like to see the project emphasize during the Wallaby development cycle; hopefully the team will self-organize around these themes. * Continued development of the cinder-tempest-plugin. We need more automated tests for more complicated scenarios, partly to prevent regressions for fixed bugs, but also to detect some problems before they are reported by users. * Better understanding of why some of the gate jobs are intermittently failing, particularly the backup-related tests in the tempest-storage suite. * Better review bandwidth. The core team we carried over from Ussuri to Victoria is still active, but as their careers have progressed, they have taken on more responsibilities in their day jobs, and their review counts have declined a bit. We added Lucio as a new core during Victoria; it would be good to add another person or two during the Wallaby cycle. Anyone working on the cinder project who's interested in working to get themselves into a position where they could be nominated as a cinder core, please contact me (or any of the current cores) to discuss what the expectations are. Those are what's been on my mind lately. As far as specific features, etc., those will emerge from our PTG discussions, to which I encourage you to contribute: https://etherpad.opendev.org/p/wallaby-ptg-cinder-planning We've had productive virtual mid-cycle meetings for two cycles now, and the cinder-weekly-meeting-once-a-month-in-videoconference seems to help keep the team connected, so I'd like to continue that. The team adapted well to the virtual PTG format for Victoria, so I'm confident we'll have a productive virtual Wallaby PTG, though I sincerely hope we'll once again have the opportunity to meet face-to-face for the 'X' PTG. As far as external interest in the Cinder project goes, we've added some new drivers in Victoria and already have one new driver proposed for Wallaby, with at least one more on the way, which is nice. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita)

1 0

[all][election][tc] Candidacy
by Jay Bryant 28 Sep '20

28 Sep '20

Dear OpenStack Community, This note is to officially announce my intention to be re-elected to the OpenStack TC in the Wallaby cycle. At this point, I think that many of you know me, but for those who don't I will briefly introduce myself. I have been a part of the OpenStack Community since early in 2013. At that time I was working for IBM and acted as the liaison between the storage teams developing Cinder drivers for IBM's storage solutions and the Community. I am currently working at Lenovo as the Principal Cloud Architect, leading a team that is developing automated infrastructure deployment and cloud deploy solutions for several different cloud platforms. During my time in the OpenStack Community I have been a Cinder core team member and served as PTL for Cinder for two years. I have been an active part of on-boarding for new Community members, helping and supporting the Upstream Institute sessions since the 2016 session in Barcelona. I also have been active in projects outside of Cinder, acting as Oslo liaison for Cinder and helping the documentation team back in the days that that was a thing. Most recently, I have served a year on the OpenStack TC. I will admit that the experience has come with a learning curve. My time has also been during a time of change for the TC and for OpenStack in general. During my time on the TC I was proud to organize the first review of Technical Committee questions in the annual user survey. The exercise was interesting and I feel it brought good information to the TC with regards to what the community needs to be doing to best serve our users. I also have been active in the discussions around how to handle leaderless projects. I feel that my experience as a PTL for a notable period of time and core team member for over 6 years gives me perspective to talk about how we continue to develop OpenStack project structure. During my last year, my focus at work has changed from pure development to being more of a designer/consumer of cloud solutions. The solutions are not exclusively OpenStack, but now include OpenShift and VMware based clouds. The change in focus has given me new perspective on how OpenStack fits into the cloud ecosystem and I think it is perspective that will be helpful in the coming year as we now have a combined Technical Committee and User Committee. If re-elected I will support getting the OpenStack community connected with other cloud communities, especially the k8s community. I will continue to support efforts to adapt OpenStack's processes and projects to make things easier for projects both large and small. I also hope to help to set goals for the community that will help it continue to be a vibrant and relevant cloud solution for years to come! Working with the OpenStack Community has always been something that I have been very proud to do in my career. I thank you all for the opportunity to serve as a TC member the last year and hope that I can continue to serve the community in this capacity. Sincerely, Jay Bryant IRC (Freenode): jungleboyj

1 0

[cinder] this week's meeting in video+IRC
by Brian Rosmaita 28 Sep '20

28 Sep '20

I forgot to mention at last week's Cinder meeting that the meeting for Wednesday 30 September, being the last meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. Here's a quick reminder of the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. connection info: https://bluejeans.com/3228528973 cheers, brian

1 0