- This topic has 6 replies, 2 voices, and was last updated 4 years, 11 months ago by
.
-
Posts
-
-
-
-
-
If we possibly go with Aslam’s suggestion of localising a supported distro, who will pay support licensing while we are still experimenting?
Or we just take it and start building on it, then are we not going to have issues again convincing government to cut on licensing but still require them to pay for licenses of an enterprise linux?
I am suggesting we play around with the community versions of the enterprise distros, so it becomes easier to upgrade to enterprise without much trouble when we want support later for mission critical servers.
-
Yes true and that is another fundamental question we need to answer…
Do we go enterprise supported distro because if so there may not be much customisation apart from the standard image, and yes there would be a cost to roll it out across government? Less than Windows, but we lose the maximisation of savings.
Other option is a free distro that “we” establish as standard distro for SA gov (something with broad support like Ubuntu, CentOS, OpenSuse, etc). We could have ourselves and local industry build up expertise and support capability on it. But there are downsides like it won’t have enterprise support when needed, and it won’t be certified to run SAP and some other enterprise software.
Or do we separate server side (maybe needing enterprise support) from desktop installs – probably a good idea to separate. Separating servers and desktops gives u more flexibility. The two areas are probably two different strategies to tackle.
-
-
OK good idea – yes we split it into:
1. Server side – enterprise if needed/certified for apps being hosted on per app basis. General application hosting could standardise on whatever is most broadly used in SA gov (survey needed).
2. Desktop OS – we could certainly standardise on what is felt to be a well-supported non-enterprise distro as we (within gov and across our local industry) will skill up on it. Thing is we should ideally not have a different flavour distro for each Dept as we need to standardise on expertise, support, driver tweaking, etc. We’ll probably also need input from local companies such as Obsidian Systems, LSD, etc who do this type of work. If there is already experience in our local industry, we need that input.
-
- You must be logged in to reply to this topic.