<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Thanks for bringing this topic up! As a release team member I tend to agree with Sean that this is a good candidate to be a community goal of 2023.2 Bobcat as we are too late to add this to 2023.1 Antelope release (given that in exactly 2 weeks we will have
Antelope-3 milestone, which is Feature Freeze date).</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Also, we had a good example with the same thing in Zed in the past, where a last minute change caused some trouble (and resulted conversations like this [1]) and people agreed to avoid this in the future if possible.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
So I think the best is to *NOT* accept Sqlalchemy 2.0.0 in this cycle (2023.1 Antelope).</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Thanks,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Előd Illés</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
irc: elodilles @ #openstack-release<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0">
[1] <a href="https://lists.openstack.org/pipermail/openstack-discuss/2022-October/030914.html" id="LPlnk748399">
https://lists.openstack.org/pipermail/openstack-discuss/2022-October/030914.html</a><br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Sean Mooney <smooney@redhat.com><br>
<b>Sent:</b> Wednesday, February 1, 2023 5:50 PM<br>
<b>To:</b> Mike Bayer <mike_mp@zzzcomputing.com>; openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org><br>
<b>Cc:</b> stephenfin@redhat.com <stephenfin@redhat.com><br>
<b>Subject:</b> Re: [all] Supporting SQLAlchemy 2.0 in OpenStack</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Wed, 2023-02-01 at 08:58 -0500, Mike Bayer wrote:<br>
> We started talking about SQLAlchemy 2.0 in Openstack most officially in August 2021:<br>
> <br>
> <a href="https://lists.openstack.org/pipermail/openstack-discuss/2021-August/024122.html">
https://lists.openstack.org/pipermail/openstack-discuss/2021-August/024122.html</a><br>
> <br>
> Since then, lots of work has been done for SQLAlchemy 2.0 compatibility. oslo.db master IIUC should be fully free of 2.0 deprecation warnings, this is the topic for that:
<a href="https://review.opendev.org/q/topic:sqlalchemy-20+repo:openstack/oslo.db">
https://review.opendev.org/q/topic:sqlalchemy-20+repo:openstack/oslo.db</a> however, sqlalchemy-migrate would need to be fully retired from it which hasn't happened yet.<br>
stephen who is alredy on cc has been driving most of the work to remvoign sqlalchmey-migrate<br>
nova and several other project move to alembic thanks to there work in zed.<br>
<br>
i would think moving nova and placment at least to SQLAlchemy 2.0 in bobcat would not be contoverital given the work that stephen and other have<br>
already been doing.<br>
<br>
this would be good perhasp as a comunity goal<br>
<br>
> <br>
> For downstream projects, the vast majority of SQLAlchemy-related code, which is lots of session.query() calls, should not have to change except to the degree that string-based notation for object attributes is removed in favor of actual attributes, e.g. joinedload("networks")
becomes joinedload(Machine.networks).<br>
> <br>
> The SQLAlchemy 2.0 migration process is designed to be gradual and starts with building a 2.0 forwards-compliant application that runs under SQLAlchemy 1.4. This process is documented at
<a href="https://docs.sqlalchemy.org/en/20/changelog/migration_20.html#the-1-4-2-0-migration-path">
https://docs.sqlalchemy.org/en/20/changelog/migration_20.html#the-1-4-2-0-migration-path</a> . I think a lot of projects are already through this process and are now trying to run directly on the 2.0 release.<br>
> <br>
ya if we have nto got there with nova/placment yet i think it something we can push for in the next release<br>
we do have the deprecation warnign mostly turn on and we try to fix them when they happen so its proably time to actully complete the move.<br>
> <br>
> <br>
> <br>
> On Wed, Feb 1, 2023, at 8:02 AM, Thomas Goirand wrote:<br>
> > Hi,<br>
> > <br>
> > SQLAlchemy 2.0 was released 5 days ago. IMO, we should start drawing a <br>
> > plan to support it for Bobcat, and possibly backport patches for <br>
> > Antelope. Note that I have no clue what his implies. Maybe Mike, you <br>
> > could write about it? Has a lot of things changed?<br>
> > <br>
> > Cheers,<br>
> > <br>
> > Thomas Goirand (zigo)<br>
> > <br>
> > <br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>