March 2021 - openstack-discuss - lists.openstack.org

[largescale-sig] Video meeting Mar 24: "Scaling RabbitMQ Clusters"
by Thierry Carrez 23 Mar '21

23 Mar '21

Hi everyone, The Large Scale SIG organizes video meetings around specific scaling topics, just one hour of discussion bootstrapped by a short presentation from operators of large scale deployments of OpenStack. Last month we did one on "Regions vs. Cells" which was pretty popular. Our next video meeting will be next Wednesday, March 24, at 1500utc on Zoom (link/password will be provided on this thread the day before the event). The theme will be: "Scaling RabbitMQ Clusters" quickstarted by a presentation from Gene Kuo (LINE). To see how 1500UTC will translate into in your corner of the world, you can doublecheck: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210324T15 If you're interested in sharing your experience on this topic, or just want to learn more about that, please mark your calendar and join us next Wednesday ! -- Thierry Carrez (ttx)

1 1

[cinder] review priorities right now
by Brian Rosmaita 23 Mar '21

23 Mar '21

Please focus on the following two items in preparing for RC-1 on Thursday. 1. There are a few follow-up patches fixing bugs in driver features listed at the top of this etherpad: https://etherpad.opendev.org/p/cinder-wallaby-features 2. There's also a series of patches fixing bugs in Cinder quotas, which as you all know, have been a perennial pain point for operators. Most of these already have at least one +2. Start here: https://review.opendev.org/c/openstack/cinder/+/778182 and work your way up the "Relation chain" displayed in gerrit. Here's the complete list: https://review.opendev.org/q/topic:%22unused-quota-classes%22+(status:open%… Happy Reviewing! brian

1 0

Re: [Release-job-failures] Release of openstack/monasca-grafana-datasource for ref refs/tags/1.3.0 failed
by Thierry Carrez 23 Mar '21

23 Mar '21

We had a release job failure during the processing of the tag event when 1.3.0 was (successfully) pushed to openstack/monasca-grafana-datasource. Tags on this repository trigger the release-openstack-javascript job, which failed during pre playbook when trying to run yarn --version with the following error: /usr/share/yarn/lib/cli.js:46100 let { ^ SyntaxError: Unexpected token { at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:373:25) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (/usr/share/yarn/bin/yarn.js:24:13) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) See https://zuul.opendev.org/t/openstack/build /cdffd2a26a0d4a5b8137edb392fa5971 This prevented the job from running (likely resulting in nothing being uploaded to NPM? Not a JS job specialist), which in turn prevented announce-release job from announcing it. -- Thierry Carrez (ttx)

5 7

[CloudKitty] vPTG meeting dates
by Rafael Weingärtner 23 Mar '21

23 Mar '21

Hello guys, We need to pick a date for our vPTG meeting. The suggested date and time is Monday April 19 13UTC - 14UTC (https://ethercalc.net/oz7q0gds9zfi) which would fit exactly in one of our Monday meetings. Does everybody else agree with this date and time? Let me know if that works for you. If it does, I will book the room. -- Rafael Weingärtner

2 2

[nova][placement] Xena PTG
by Balazs Gibizer 23 Mar '21

23 Mar '21

Hi, As you probably already know that the next PTG will be held between Apr 19 - 23. To organize the gathering I need your help: 1) Please fill the doodle[1] with timeslots when you have time to join to our sessions. Please do this before end of 21st of March. 2) Please add your PTG topic in the etherpad[2]. If you feel your topic needs a cross project cooperation please note that in the etherpad which other teams are needed. Cheers, gibi [1] https://doodle.com/poll/ib2eu3c4346iqii3 [2] https://etherpad.opendev.org/p/nova-xena-ptg

1 1

[openstack-helm] No meeting tomorrow March 23rd
by Gage Hugo 23 Mar '21

23 Mar '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, March 23rd, we will cancel it. Our next IRC meeting will be March 30th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

Re: OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.
by Stefan Kelber 22 Mar '21

22 Mar '21

1 0

[heat-translator] Ask new release 2.2.1 to fix Zuul jobs
by Yoshito Ito 22 Mar '21

22 Mar '21

Hi heat-translator core members, I'd like you to review the following patches [1][2], and to ask if we can release 2.2.1 with these commits to fix our Zuul jobs. In release 2.2.0, our Zuul jobs are broken [3] because of new release of tosca-parser 2.3.0, which provides strict validation of required attributes in [4]. The patch [1] fix this issue by updating our wrong test samples. The other [2] is now blocked by this issue and was better to be merged in 2.2.0. I missed the 2.2.0 release patch [5] because none of us was added as reviewers. So after merging [1] and [2], I will submit a patch to make new 2.2.1 release. [1] https://review.opendev.org/c/openstack/heat-translator/+/779642 [2] https://review.opendev.org/c/openstack/heat-translator/+/778612 [3] https://bugs.launchpad.net/heat-translator/+bug/1918360 [4] https://opendev.org/openstack/tosca-parser/commit/00d3a394d5a3bc13ed7d2f1d7… [5] https://review.opendev.org/c/openstack/releases/+/777964 Best regards, Yoshito Ito

2 2

Re: [infra][tact-sig] Extracting commits data for the first and the last code review revisions
by Chouchen, Moataz 22 Mar '21

22 Mar '21

Hi Jermey, Thank you for your quick answer! That's what I am looking for and I am very grateful to you and to all the community. Best regards, Moataz. ________________________________ From: Jeremy Stanley Sent: Monday, March 22, 2021 8:41 AM To: openstack-discuss(a)lists.openstack.org Cc: Chouchen, Moataz Subject: Re: [infra][tact-sig] Extracting commits data for the first and the last code review revisions [I'm keeping you in Cc since you don't appear to be subscribed to this mailing list.] On 2021-03-22 15:00:03 +0000 (+0000), Chouchen, Moataz wrote: [...] > I extracted the revision IDs for the first and the last revisions > (supposed to be first and last commit hashes) for each code review > in puppet projects. However, when we have more than one revision, > we were unable to find the commits for the first revision in the > git for all the projects and we only have commits data for the > last revision. I would like to know if the commit of the first > revision does exist in the CVS, and it's possible to extract? [...] Conveniently, Gerrit stores all of this in the repository and we replicate it to our Git server farm. The complication is that, because of the amend/rebase-oriented nature of Gerrit's code review workflow, those earlier revisions don't appear in the branch history. Instead, they are tracked with named references which look like changes/XX/YYYY/Z where YYYY is the numeric index identifier for the change, XX is the last two digits of YYYY (for sharding purposes), and Z is the revision number starting from 1. Let's take this puppet-nova change as an example: https://opendev.org/openstack/puppet-nova/commit/d385ca8 There you can see Gitea is displaying an indicator that there is a named ref of changes/63/764763/5 associated with the commit. That means it was revision 5 of change 764763 in Gerrit. You can fetch that ref like so: git fetch origin changes/63/764763/5 That will fill FETCH_HEAD which you can then use with checkout, show, or any other relevant subcommands. Conveniently, if you instead want the first revision of 764763, all you have to do differently is adjust the revision number: git fetch origin changes/63/764763/1 Hopefully that's what you're looking for? -- Jeremy Stanley

1 0

Extracting commits data for the first and the last code review revisions
by Chouchen, Moataz 22 Mar '21

22 Mar '21

Dear Openstack community, Hope you are doing well. I am Moataz Chouchen a Ph.D. student from ETS Montreal. I am interested in studying the impact of code review on the quality of puppet files. For this reason, I am interested in studying the code reviews containing puppet files (We investigate puppet projects.) and comparing puppet files in the first revision and the last revision for each code review. To achieve this, I extracted the revision IDs for the first and the last revisions (supposed to be first and last commit hashes) for each code review in puppet projects. However, when we have more than one revision, we were unable to find the commits for the first revision in the git for all the projects and we only have commits data for the last revision. I would like to know if the commit of the first revision does exist in the CVS, and it's possible to extract? In case these commits do not exist, how could, we retrieve the files in the first version of a review? Thank you very much, Best regards, Moataz

2 1