endoflife-date / endoflife.date

Informative site with EoL dates of everything
https://endoflife.date
MIT License
2.49k stars 776 forks source link

[Request - Product] Citrix XenServer Hypervisor #5145

Open MiGro1194 opened 6 months ago

MiGro1194 commented 6 months ago

Full and short name of product: Citrix XenServer

Let us know the long, full name and, if it has one, the short name (for example, PowerShell and pwsh). Citrix XenServer

Does this product have LTS versions? What are the intervals between each LTS version? Yes it has a LTS Version - Release Interval not known :(

What is the website for the product and for its version information? Version Information: https://www.thomas-krenn.com/de/wiki/Citrix_XenServer Website for product: https://www.citrix.com/support/product-lifecycle/product-matrix.html

Thanks and best regards Michael

captn3m0 commented 2 months ago

There's a lot of licensing support information at https://docs.xenserver.com/en-us/xenserver/8/faq-licensing

The legacy product matrix has dates for 7: https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html. Citrix Hypervisor also has a separate page at https://www.citrix.com/support/product-lifecycle/citrix-hypervisor.html which says:

Citrix Hypervisor adopted a new Servicing Options release strategy starting with XenServer 7.1. General guidance regarding lifecycle milestones for each release strategy is defined below.

https://www.xenserver.com/story clarifies some of the history, which is important to understand the relationship between various entities:

  1. XenSource
  2. XenServer
  3. Citrix Hypervisor
  4. Cloud.com
  5. Citrix
  6. Xen Project
graph LR
    subgraph CloudCom["Cloud.com"]
        XenSource
        Citrix
    end
    Citrix -- "published" --> Xenserver7
    Citrix -- "published" --> CH

    XenSource["XenSource"] -- "publishes" --> X8[Xenserver 8]

    style CH82 fill:springgreen
    style X8 fill:springgreen
    style Xenserver7 fill:tomato

    subgraph XS[XenServer]
        Xenserver7["XenServer 7"]
        X8["XenServer 8"]
        X8 <-- "aka" --> CH
        subgraph CH[Citrix Hypervisor]
            Citrix --supports --> CH82[8.2 LTSR]
        end
    end

    subgraph LF[Linux Foundation]
        VT[Vates Tech] --runs-->XCPNG
        XCPNG[XCP-ng]
        XP[Xen Project]
        XP--incubates-->XCPNG
        XP --releases-->Xen

    end
    XS--uses-->Xen

Wikipedia says that Citrix XenServer and Citrix Hypervisor are product names for the same thing:

Xen can be shipped in a dedicated virtualization platform, such as XCP-ng or XenServer (formerly Citrix Hypervisor, and before that Citrix XenServer, and before that XenSource's XenEnterprise).

The Xen hypervisor is covered by the GNU General Public Licence, so all of these versions contain a core of free software with source code. However, many of them contain proprietary additions.

with the launch of 8.0, XenServer becomes Citrix Hypervisor. ^1 For customers on our Current Release (CR) track, we will support upgrading from XenServer 7.5 and 7.6. You can also upgrade from our LTSR release, but please keep in mind that will switch you from the LTSR track to the CR track.

Register has some plain-english explanations for the history:

https://www.theregister.com/2023/01/23/xenserver_socket_licences/

XenServer is a Citrix product the company acquired from XenSource in 2007 Citrix [...] started to concentrate on making XenServer the best environment for its own apps. its lack of focus on XenServer saw it forked as XCP-ng. Citrix eventually ditched the Xen name and went with Citrix Hypervisor. But since Citrix was absorbed into the Cloud Software Group (CSG), it has quietly revealed that XenServer has morphed into a member of the CSG – making it a standalone business instead of just a Citrix product.

The XCP-NG wikipedia page explains that better than the website:

XCP-ng can be compared to a Linux distribution,[23] but meant to run Xen out-of-the-box. It is a collection of components creating a coherent system that you can install on any x86 bare-metal server. It is based on multiple projects, like CentOS for user space packages, XAPI project for the API, Xen project for the hypervisor, Open vSwitch for the networking and so on. XCP-ng provides also extra packages that aren't available elsewhere, because non-existent or closed-sources in Citrix Hypervisor. As a fork of XenServer with an "upstream first" philosophy,[24] XCP-ng stays pretty close to the original Citrix project, and can be considered as a "friendly fork".[25]

Obviously, not all of this is important and needs to go in a Citrix Hypervisor page. But if we're looking at product lines, we will end up having separate pages for Citrix Hypervisor and XenServer. Limiting this issue to just the former.