[DOCS-15162] Supported Platform updates Created: 08/Mar/22  Updated: 30/Oct/23  Resolved: 06/Jun/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.4, 5.0.0, 4.0.28, 6.0.0, 4.2.20
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Minor - P4
Reporter: venkataramans rama Assignee: Ian Fogelman
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Issue Links:
Related
related to SERVER-63303 Acknowledging Support for RHEL Clones Closed
is related to DOCS-15199 MongoDB installation guide(s) for OST... Closed
Participants:
Days since reply: 1 year, 35 weeks, 6 days ago
Epic Link: DOCSP-11344

 Description   

Hi Team,

I feel the mongodb documentation for supported platform needs significant updates as per the industry latest updates.

There are Industry accepted CentOS alternatives like Rockylinux and Almalinux used by many after the CentOS EOL announcement. They are Red Hat Compatible Kernals(RHCK), but mongoDB doens't have any mention about these. Since they are RHCK , are they supported by default? Can you please add a note about Almalinux and Rockylinux in the supported platform

 

The Oracle Linux has the mention of RHCK so, i would request to add a note that CentOS variants  RHCK also in the supported platforms.



 Comments   
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162 v5.0 (#1186)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162 v5.0 (#1186)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162 v4.4 (#1187)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
  • update 2
  • remove 5.0 mentions
  • fix
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162 v4.4 (#1187)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
  • update 2
  • remove 5.0 mentions
  • fix
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-15162 (#1188)
Branch: v4.2
https://github.com/10gen/docs-mongodb-internal/commit/be40d19491e1770c59dd50d03e9b9b230013d6b4

Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162-v5.3 (#1185)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: Docs-15162-v5.3 (#1185)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
Comment by Githook User [ 02/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-15162 Rocky Alma PS Server Updates (#1163)

  • update
  • change footnote symbol
  • edit
  • add
  • add community edition notes
  • amend
  • footnote adjustments
  • feedback
  • fix includes
  • fix
  • revert
  • fix2
  • *
  • fix footnote
  • CR2 Edits
  • *
  • update AlmaLinux
  • update
Comment by Alex Ettouati [ 17/May/22 ]

Hi All, 

Applogies for the delayed response. We will be supporting Alma Linux and Rocky Linux and will be formally announcing in a week or two (I will update this ticket with the blog post once it is published). The documentation will also be updated to reflect this in the following weeks. 

Best, 

Alex

Comment by Neil Hanlon [ 17/May/22 ]

Hi Alex,

 

Would you be able to share any more information on the status of this request? Is there anything we can do to assist?

 

Best,

Neil

Comment by venkataramans rama [ 02/May/22 ]

Hi Alex,

Appreciate if you could share an update on when the updated documentation will be available ?

Thanks,

Venkat

Comment by Alex Ettouati [ 06/Apr/22 ]

Thank you. I greatly appreciate the additional context here. This will strengthen the proposal for MongoDB officially supporting both Rocky Linux and Alma Linux. I will keep all updated on our progress and should be able to give our official stance in the next few weeks.

Comment by Neil Hanlon [ 06/Apr/22 ]

Hi Alex,

 

By 'largely cosmetic' I mean the colors and branding on some packages, naming (changing references from Red Hat Enterprise Linux -> Rocky Linux, e.g.), and uncommonly, modifications to build params to work around bugs.

Unless future versions of RHEL change their licensing away from being GPL compatible, my team does not see a risk to being able to faithfully rebuild RHEL from the sources they provide. Pertinently, RHEL 9's sources are available already for rebuilding, and there's consensus among the larger Enterprise Linux community that future versions will also be released in this manner.

 

Best,

Neil Hanlon

Comment by Alex Ettouati [ 06/Apr/22 ]

Hi Neil, 

Thank you for the helpful information. Could you please elaborate on the "largely cosmetic" comment. Specifically what might happen if future RHEL versions have proprietary features or require Red Hat subscriptions to enable features and you/others are unable to create faithful clones? Is this a risk that your team sees as a possibility? 

Comment by Neil Hanlon [ 04/Apr/22 ]

Hi Alex,

 

I am a lead for the Infrastructure team over at the Rocky Enterprise Software Foundation for Rocky Linux, as well as a member of the core SIG responsible for producing the Rocky Linux OS as a compatible downstream of RHEL.

 

Both Rocky Linux and AlmaLinux (and other distributions like Oracle Linux, etc) serve to fill the role CentOS Linux previously had, namely, provide a downstream "copy" of Red Hat Enterprise Linux. Rocky and Alma use the sources (RPMs and Specfiles) that are provided by Red Hat at git.centos.org to produce the same packages. There are, of course, differences in exact build profiles that mean the resultant artifacts are not "bit for bit" the same as RHEL, but are close enough approximations that have been accepted by the industry (by way of CentOS) for quite a long time. CentOS served as a development platform for many organizations, and the parity with RHEL is something we in the Rocky Core SIG strive for.

 

Please let me know if I can provide any further clarity on how the sources are rebuilt or gathered. The only differences between the different OSes should be largely cosmetic, e.g. removing trademarked and/or copyrighted branding/text from the OS, and replacing it with each discrete distribution's own branding, where applicable.

Comment by Alex Ettouati [ 04/Apr/22 ]

Hi Venkat, 

Thank you for the answers to my questions. As mentioned above we are currently investigating if we will provide official support and I should have more information for you in a couple weeks. Currently we are looking into what guarantees Rocky and Alma have that they will be able to maintain 1:1 compatibility with future versions of RHEL. Do you have any insights on this?

Best, 

Alex

Comment by venkataramans rama [ 04/Apr/22 ]

Hi Alex,

Let me know if you need any further details. Can you please share the update on this request?

Thanks,

Venkat

Comment by venkataramans rama [ 25/Mar/22 ]

Hi Alex,

Thanks for prioritizing this request and for your response. Please see my answers in-line.

  1. What documentation are you specifically referring to? 

<Venkat>

Primarily the following 2 documents section which talks about the supported and recommended platforms where we would like to have a mention of the CentOs alternative like AlmaLinux as well.

https://www.mongodb.com/docs/v5.0/installation/

https://www.mongodb.com/docs/manual/administration/production-notes/#std-label-prod-notes-platform-considerations

</venkat>

  1. What kind of groundswell are you seeing for alma linux vs rocky linux.
  1. Have you received any specific customer questions around our support?

<Venkat> We know alma Linux or Rocky Linux are 1:1 compatible with Centos/RHEL and mongo should work fine in the environment. But, we would like to get the official statement from mongo that these alternatives are in the supported platform list.

If you can confirm that Mongo will support issues/queries raised from AlmaLinux then we should be good. Because, as you know we can’t assume and proceed with the plan and get into surprise from mongo later that these are not officially supported in the doc hence mongo couldn’t serve those tickets.

</Venkat>

  1. Have you seen interest from community or enterprise users?

<Venkat> We are primarily looking from community version perspective.  </Venkat>

 

Comment by Alex Ettouati [ 24/Mar/22 ]

Hi Venkat, 

Thanks for reaching out and apologies for the delayed response. I'm a product manager on the server team currently investigating our future platform support. We understand that due to the CentOS changes, customers are looking for alternatives. We are currently looking into the CentOS variants and determining what RHEL clones we will officially support moving forward.

 

As part of this research it would be helpful if you could provide any market context you might have.

  1. What documentation are you specifically referring to? 
  2. What kind of groundswell are you seeing for alma linux vs rocky linux.
    1. Have you received any specific customer questions around our support?
    2. Have you seen interest from community or enterprise users?

Best, 

Alex

Comment by venkataramans rama [ 24/Mar/22 ]

Hi Jason,

Can you please share some timeline when this will get addressed in the mongo documentation.

 

Thanks,

Venkat

Comment by venkataramans rama [ 08/Mar/22 ]

FYI, the kernel versions are same

on AlmaLinux

uname -a Linux alma8podman 4.18.0-348.12.2.el8_5.x86_64 #1 SMP Wed Jan 19 14:35:04 EST 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release

AlmaLinux release 8.5 (Arctic Sphynx)

On RHEL

uname -a Linux rhel8repo 4.18.0-348.12.2.el8_5.x86_64 #1 SMP Mon Jan 17 07:06:06 EST 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release

Red Hat Enterprise Linux release 8.5 (Ootpa)

 

 

 

Generated at Thu Feb 08 08:12:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.