Overview

Background

OCS (Open Computer and Software Inventory Next) is owned and managed locally by the CAHSS Digital Team.  It is a free software that enables users to inventory their IT assets. It collects information about the hardware and software of networked machines running the OCS client program ("OCS Inventory Agent"). Agents are also able to scan their own subnets to further discover other devices which might not run the agent (such as printers) via “IpDiscover”. The inventory is accessed and visualised via a web interface running on the OCS Inventory server.

The current installation of OCS is on a centrally supported VM. The current installation needs to be upgraded. In order to support the upgrade, a TEST environment needs to be created. This requires a new VM to be created and OCS installed before the upgrade can be applied to TEST and then deployed to the LIVE installation.

Production have asked for a standard TEST - LIVE environment to support the upgrade without impacting on the LIVE installation. This does not currently exist.

The project will also agree on a process that allows the supplier to quickly have access to both live and test after the project ends (e.g. Security patching).

There has also been concern that much of the current server software, which is CentOS, is end-of-life and may be potential security risks. Development Technology have already reviewed this and recommended we build two new Rocky 8 servers: a Test and Live. These servers will be supported by ISG going forward.

Scope

The current installation of OCS in CAHSS is managed locally by the CAHSS Digital Team and is on a centrally supported VM. This requires upgrading to v2.12.2 and in order to complete this the following tasks are in scope:

• Replacement of the current CentOS Live server with a TEST and LIVE Operating server in Rocky 8
• Creation of a TEST and LIVE environment on the Rocky 8 servers to support OCS and copy the current version of OCS to the Test environment
• Upgrade the current OCS installation in TEST to v2.12.2
• Deploy the upgraded OCS installation in TEST to LIVE
• Agreement on a process to allow the supplier access to Live and Test for security patching

Out of scope

• Updating of agents

Objectives and Deliverables

The deliverables are prioritised using the MoSCoW prioritisation method:

M=Must Have; S=Should Have; C=Could Have; W=Want

• (M= has to be satisfied for the final solution to be acceptable in terms of delivery dates, compliance, viability etc.
• S= high-priority requirement that should be included if possible -workarounds may be available
• C= a nice-to-have requirement
• W= want but will not be part of this project

Benefits

• OCS upgraded to latest version
• TEST - LIVE environments now exist as standard
• Underlying operating system servers are now under ISG central control

Success Criteria

• New operating system servers have been created (which will be under central control)
• The OCS system will now have standard TEST - LIVE environments
• The OCS system is successfully upgraded to version 2.12.2 in both TEST and LIVE
• The supplier will have a process to allow them access to TEST and LIVE e.g. for upgrades and security patching)

Project Milestones

To note Start of Term change freeze from 3 to 23 September 24 – will not affect Test build

Dates have been agreed with Factor FX