FAL-2260 Prepare opencraft release branch for lilac.2 - #175
Conversation
8e54316 to
082fa19
Compare
|
I don't see the changes from [SE-4304] [SE-4495] feat: add celerybeat configuration. |
This is this commit: dd2f2ac The diff shows less changes than the original commit, because most of it has been upstreamed. CC @gabor-boros do we need the 'install simple-beat to control celerybeat processes' task? Will it be upstreamed? |
|
@swalladge looks good. |
|
@swalladge I'm a bit confused by your question. The changes are upstreamed as part of
Am I missing something here? |
aaah sorry, I was the one missing something. :P Yep it's all been upstreamed; git was playing tricks on me when I checked the diff and applied the commit though. 🤦♂️ |
93ba25e to
188133c
Compare
|
@swalladge I believe some PRs/commits are missing. Correct me if I overlooked it, but OCIM now can provision instances that are using multi tenant redis. Now, the celery upgrade is not upstreaming yet as I'm still fighting with the ticket in the current sprint. Taking that into account, shouldn't we port that to opencraft lilac as well? Since it is something that will never end up on edx/lilac but we want to use it, I guess we should cherry-pick that too. Cc: @pomegranited |
Sure yes definitely. Are these commits/PRs you're talking about on edx/configuration and in koa? I didn't see any other commits related to redis/celery. If they're in edx/configuration master, then we can backport to our lilac branch after this commit is merged (ie. after we actually cut our lilac release). |
Well, it seems I remembered wrongly. Sorry about the confusion! |
|
@swalladge
I believe that was a backport of this upstream PR: https://github.com/edx/configuration/pull/6465. |
Ok. Was there no corresponding PR for the backport? |
|
@swalladge, for #140 , the AppleIdAuth backend is in lilac now, so that particular PR shouldn't be necessary. |
This PR add the flags to sync the edx services logs to s3 bucket. (cherry picked from commit eb402aa)
…ls_extra_requirements_koa feature: Allow installing extra requirements when using the `credentials` role (cherry picked from commit 7ce36c7)
(cherry picked from commit 4df1323)
…ygithub-fix [FAL-2409] Use the tubular pygithub fix in our common branch (cherry picked from commit a957ce3)
188133c to
b5eeb9b
Compare
Awesome! :)
Looks like that's already been done, so that's all good now. |
| DOMAIN: "{{ COMMON_GIT_MIRROR }}" | ||
| PATH: "open-craft" | ||
| REPO: "tubular.git" | ||
| VERSION: "opencraft-release/koa.3" |
There was a problem hiding this comment.
@pomegranited what are your thoughts here? We can't use open-release/lilac.2 for tubular because https://github.com/edx/tubular/pull/531 didn't make it to lilac.2, but we should default to a lilac release here to avoid issues. Maybe we can default to open-release/lilac.master here?
There was a problem hiding this comment.
@swalladge That sounds safe -- tubular isn't changed very often, so we're not risking much by using a potentially-shifting lilac.master target.
There was a problem hiding this comment.
👍 I updated in 06fb8f4 - would you mind sanity checking this?
I'm also deploying a new sandbox instance for testing. CC @michaelbukachi if you'd like to make another review pass now that there has been some changes.
There was a problem hiding this comment.
@swalladge 06fb8f4 looks good 👍 Thanks for simplifying that drift too.
@michaelbukachi To test this, you can check the sandbox server for retirement-related errors in /edx/var/log/**/*.log, and verify that you're able to create and delete a user successfully.
Previously, we pinned to an opencraft release as a quick fix, but that quick fix is now merged to lilac upstream. (The fix being https://github.com/edx/tubular/pull/531 ) It didn't make it to lilac.2, so we need to pin to lilac.master.
|
@swalladge I don't see your change from https://github.com/edx/configuration/pull/6462 in this branch? It was partially backported to our koa.3 release branch by #176 but that port unfortunately doesn't include the I think https://github.com/edx/configuration/pull/6462 should be ported to this branch, and the I will include this in the scope of FAL-2543, which is semi-related. |
Yeah they wouldn't be unless we already had backported it to our koa branch, or upstream had included it in lilac.2...
Sounds like a good plan 👍
Thanks! :D |
|
@pomegranited, @swalladge, huh, I had no idea we've created two tickets for this 🤦 |
|
@Agrendalath oh haha I didn't even notice they were different tickets. Looks like we forgot to backport to the client branch in the first ticket, and the second ticket didn't notice that we'd already implemented it upstream. |
FAL-2260
Port the following PRs / commits from koa to lilac:
credentialsrole #169These are skipped because they have already been upstreamed in lilac 🎉 :
And this isn't required any more (see comments below):
Test instructions:
For each patch from edx/configuration@open-release/koa.master...open-craft:opencraft-release/koa.3 , verify that it has either been upstreamed or ported cleanly.
Launch a lilac instance with ocim, using this configuration branch, and verify everything is deployed successfully. (wip - deploying on https://manage.opencraft.com/instance/29580/ )
Notes / Concerns: