Deployment of Open Computer and Software Inventory
  1. Home
  2. Node
  3. Overview

Overview

Background

This project has been set up to tackle lack of a Hardware Inventory System within the School of Science and Engineering (SCE). This has already been carried out at HSS in 2015 within the Project HSS055. Open Computer and Software Inventory Next Generation (OCS inventory NG) is  free / open source software with a ‘Community Edition’ licence that enables users to inventory their IT assets. OCS-NG collects information about the hardware and software of networked machines running the OCS client program ("OCS Inventory Agent"). OCS can be used to visualize the inventory through a web interface.

There is a need to build an inventory of the approximately 300 to 400 (TBC) managed desktops across SCE Schools and College to enable collection of accurate data on the SCE desktop assets. This will enable staff in Schools and Colleges to view all Schools managed desktop inventory data, to enable more efficient management and maintenance of these assets.

This project aims to deliver a partially configured OCS inventory system installed on Linux VM to be handed over to SCE to complete configuration and to run as a service for SCE Schools.

Scope

The scope of this project is to:

  • Consult with Desktop Services (see Risk 1 regarding automatic deployment to SCE managed desktops), and facilitate agreement about rollout of OCS Client Software.

    • Address Risk 5 by testing the OCS Client software.
  • Procure one Virtual Machine (VM): note that this will need input from SCE to validate the specification.
  • Build the new OCS system on the VM, enabling the client connection through to the server, and applying a file provided by SCE with base configuration from the pilot.
  • Handover to IS Apps Production Management who will then be responsible for: the VM OS upgrades and patches (regular monthly patching) and backups  –  note these tasks are to be added to SCE support budget under a new support code.

Out of scope:

  • Establishing whether the installed package will work, or can be configured by SCE.
  • Establishing whether the installed package will interfere with other applications.
  • Full configuration of the server - this will be completed by Fraser Muir's team in SCE.
  • Rollout of the client package to the SCE desktops - this will be completed by Desktop Services.
  • Disaster recovery. In the event of failure the expectation would be to restore from the last tape backup (may mean some data loss depending on the backup timing).
  • Developing a full set of operational procedures - SCE will have to develop and sign these off during the same timeline as the establishment of the infrastructure.
  • There is the possibility of opening up the service to other schools / colleges which could mean opening up firewalls.
  • There is a future option to build an extract job from OCS that could be imported into the Unidesk CMDB (estimated at additional 2d effort), this extract could be run daily or weekly to update the data in the Unidesk CMDB (the import jobs to consume this kind of data already exist at the Unidesk CMDB end).

Objectives

The objectives of this project are to:

  • Work with Desktop Services to determine whether the OCS Client Program can be automatically installed on all of the managed desktops across SCE Schools and College, and faciliate agreement about the rollout. As part of this test the OCS Client software to check it addresses Risk 5 security concerns raised by Desktop Services.
  • Procure a VM, install a package (OCS Inventory NG) on that VM, give SCE admin access to the OCS Application to complete the configuration of the software. This will include enabling the client connection through to the server, and applying a file provided by SCE with base configuration from the pilot.
  • Hand the VM upgrades, patches and backup tasks over to IS Applications Production Management.

Deliverables

The deliverables of this project are:

  • A technical architecture document (TAD) detailing the architecture.
  • A VM with the installed package OCS Inventory NG (note that whether the software works is out of scope, this is purely a hardware provision, installation of the package provided, checking that the client software can connect to the server and applying a file of base configuration from the pilot as provided by SCE).
    • Testing of the OCS Client software to check it addresses Risk 5 security concerns raised by Desktop Services.
  • HSS access to the VM so they can then configure the installed package.
  • Agreement between SCE and Production Management about ongoing support arrangements.

Benefits

The benefits of this project will only be fully realised once SCE have completed the configuration of the OCS Inventory NG software and run it on their assets. At that time the business will be able to:

  • Understand the number of networked assets that they need to support.
  • Visualise the inventory of assets thorugh a web interface.
  • Use the information on networked assets to make informed business decisions, such as when and how to replace old assets.

Success Criteria

This project will be successful if:

  • A Virtual Machine is procured, and the OCS Inventory NG software is installed on it (note that whether the software works is out of scope, this is purely a hardware provision, installation of the package provided, checking that the client software can connect to the server and applying a file of base configuration from the pilot as provided by HSS).
  • HSS can access the administrative functions of the OC Inventory web application on the VM so they can then configure the installed software.
  • Desktop Services and HSS have an agreed method of rolling out the OCS Client software.
  • HSS and Production Management have a clear agreement about ongoing support.

 

Project Milestones

(Please copy and paste from Milestones log)

This article was published on

Project Info

Not available.

Documentation

Not available.