-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration instructions for TuxCare's CentOS ELS to AlmaLinux ESU #588
base: master
Are you sure you want to change the base?
Conversation
Would be interested to know if you even need to use almalinux-deploy to get from stream8 to alma8 or if ELevate can do it all....? |
Thanks, @sej7278! As paid-only Tuxcare products, I'm not sure that these directions make much sense in the AlmaLinux wiki, but should instead probably be in the Tuxcare docs. Are y'all getting a lot of support questions about this? if so, maybe we should add a note to the thing (like we do with the cPanel fork)? |
Hey @bennyvasquez, I had considered putting it in TuxCare docs but not sure people would think to look there about ELevate. What's this about cpanel? Perhaps we could link from the AlmaLinux wiki to TuxCare docs? |
Oh, it looks like I never got the cPanel line added to the wiki, but you can see it on the website page here: https://almalinux.org/elevate/ Essentially, it's just a note that says "if you're using $product, find directions for that " |
ah ok, so maybe i should do the PR to replicate the cpanel link (to docs.tuxcare.com) and maybe add both to the wiki? |
yeah, that sounds perfect! If I were doing it I would look for anywhere in the wiki that we reference the Oracle caveat and add them both there. If you don't mind, please also tag Sonya when you submit the new PR - she might have more ideas about where to put it!
|
@@ -0,0 +1,89 @@ | |||
--- | |||
title: "Elevating CentOS ELS to AlmaLinux ESU" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so stupid, but maybe this should be changed to ELevating
for branding/marketing consistency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, but it's not going to get merged anyway. :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
harsh! 😄
i've made cloudlinux/tuxcare-documentation#126 to get it added to tuxcare docs i'm guessing i need to do 2 alma PR's to get it added here https://wiki.almalinux.org/elevate/ :
and https://almalinux.org/elevate/ :
? |
Instructions for how to migrate from TuxCare's CentOS ELS products (e.g. CentOS 7 or Stream 8) to AlmaLinux ESU, for review please.
Attached a PDF to see what it looks like - including the modified sidebar: almalinux_wiki.pdf
The main differences include workarounds for migrating specifically to AlmaLinux 9.2 and tidying up after ELS, as well as the FIPS stuff. Being more version-specific means we need less explanatory text which seems to be confusing users.