• 0 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • Your #4 is the same as my #3. Play out your #4 and it ends up as my #3:

    1. Struggle to come to a conclusion on what to do with the EOL OS because of internal political factors and the reality of how enterprise works.

    Security or Compliance teams raise the concern with continuing to run the EOL OS, they demand the App team power down the offending servers or upgrade. App team escalates to leadership advocating for the upgrade and they ask for the funding. Leadership asks for a business case justifying the large spend requiring the ROI numbers. App team mostly shrugs because the ROI are intangibles of security or support-ability. Leadership sees no immediate monetary benefit being realized in the next 2 quarters from a costly upgrade and instead chooses to accept the risk. They send an exception order to Security or Compliance teams that this EOL OS should continue running as is and the App team shouldn’t be bothered anymore.

    …and we end up with my #3.







  • It is more like ‘involuntarily end up riding the risks of using unsupported old software’.

    Involuntarily? An org choosing to use an EOL OS to keep running an application is a business choice that accepts the risk of compromise/lack of support of an EOL OS. Any org in this situation has 3 choices:

    • deprecate the application entirely closing down that line of business the application was supporting
    • rewrite/replace the application to maintain the line of business on a modern supported OS
    • continue to run the EOL OS and accept the risks

    There’s nothing involuntary here.



  • RHEL 7 and RHEL 5 need to be flipped in your meme.

    Any large enterprise still running RHEL 5 in Prod (or even, yes, older RHEL versions) has fully accepted the risks and will grumble about supporting it, but go forward with whatever workarounds are necessary to keep the application running on it running. The RHEL 7 folks, however, are modern enough that the answer for any problem is “Upgrade to RHEL 9, because we know you can with some effort, because we don’t want to waste time on supporting something you should be able to upgrade away from”.

    This is the game of chicken in a modern enterprise for app teams. If their application is critical enough to business continuity and they remain on RHEL 7 long enough, they too will join the select few applications in the org that either get a cash injection for an application rewrite to modern RHEL 9 or be enshrined next to the RHEL 5 apps still running with grumbling, but continued support.

    In a perfect world these EOL unsupported OSes should be retired and replaced with modern supported version, but we’re talking about reality now which is what the modern enterprise is, and which is far far from the perfect world.


  • I’m not sure I agree with that. I thought Dunning-Kruger requires the person to NOT know they are in over their head or misunderstanding their level of knowledge. “Fake it 'til you make it” is acknowledgement and awareness by the person they are not knowledgeable/competent, but will pretend they are until they acquire the knowledge they lack. The big difference is the awareness.

    Dunning-Kruger = not having the awareness

    “Fake it 'til you make it” = being very the aware, but choosing to go forward anyway