On 1/22/24 08:22, Ghanshyam Mann wrote:
---- On Sun, 21 Jan 2024 04:54:26 -0800 Takashi Kajinami wrote ---
Hello,
As I brought in another thread about yaql library maintenance[1], It seems murano project is not active now, based on the following points.
* The changes merged during recent two years but all of these are gate fix
* Its CI is currently broken and no one is trying to fix it
* I tried reaching the current PTL by email or gerrit review but didn't get any feedback even after waiting for a few weeks
I'm wondering if murano project should be added to the inactive projects, or at least its project health and plan needs to be reviewed by TC, before we include this to Caracal deliverables. # Though it might be too later to drop the deliverables now
Yes, it is too late to drop the deliverables but any project can be move to Inactive state in any phase of cycle.
I am trying to fix their gate (py3.11 job) and there are a few other changes also fixes gate (I need to squash all fixes so that it pass the job)
Thanks.
It seems we need a few more changes to fix the unit tests, and I noticed zigo already proposed a few patches. So I rebased these[1][2] on yours to get all these fixes in a single patch chain. However according to the CI result posted in [2], we still have to look into the failures in tempest tests
[1] https://review.opendev.org/c/openstack/murano/+/867198 [2] https://review.opendev.org/c/openstack/murano/+/867199
I'm not much familiar with Murano so have no clear idea about the remaining failures We may really need someone from the Murano project to investigate these.
But again, as you mentioned we need their core/PTL to merge those. Let me make job green in my fix and see when it will be merged and based on that we can take next step.
-gmann
Thank you Takashi Kajinami irc: tkajinam
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....