INF139 versions

Tools versions from INF139

Key learning points

Nexus

• Just as we were testing Nexus, further versions were released on 11-Apr and then 16-Apr. Both versions were included before Acceptance was signed off on 17-Apr. Nexus then continued to be deployed to Live as planned on 25-Apr
• Now that Nexus has Bamboo plans for automated testing of the main repository types in both Test and Live Nexus environments to cover both pre- and post-deployment testing, and the deployment is puppetised with minimal down time, this is a strong contender to be moved over to Production Management to manage quarterly updates
• Nexus often releases 2 upgrades in quick succession

Puppet

• ITI now provide Puppet Master.  All future upgrades to the Puppet Master will be handled by ITI
• Future upgrades of puppet forge modules (library) and migrations to new Puppet Releases could be included in future . However it may be better to separate out the puppet migration from the Dev Tools upgrade project to uncouple it from ITIs delivery of new puppet master versions.
  • Puppet code Forge Modules need upgraded as they are already 2 years old

Oracle Grid

Oracle Grid This Year

Annual Upgrade, current version is supported until the end of 2020.

Decision to do an in-place upgrade this year

• Tech Man progressed with Oracle Grid, however they had to complete a number of quarterly security patches first before progressing with Oracle Grid
• Decision made for Oracle Grid to be completed by Tech Man in July. The contingency of Tech Man completing this work in August was not required

Oracle Grid Next Year

Dev Tech and Tech Man discussed Oracle Grid in a meeting held on 27-June-2019 to find a  better way -

The aim is from now on is to split between

• Tech Man - support for point upgrade (in place upgrades)
• Dev Tech within the Dev Tools project - if it is a fuller upgrade, where a new server is required.

This information should be included in the project recommendation for next year

• The project brief should recommend which technology team should complete the upgrades for that tool ( If server upgrade required then Dev Tech, if no server work then Tech Man).

General

This project was significantly impacted by issues with securing both Software Development and Development Technology Resources - some tools were adversely affected and were re-planned several times. Then in late June it was decided that Tech Man would take over the remaining work. Then as the Project slipped towards the back end of the financial year resource became harder to secure or had been conflicted against for higher priority projects. 

As an annual project it is the Project Teams recommendation that it be initiated early in the year and given as much time as possible to complete.

• This was taken forward by the current project, however it did not enable applications to be implemented any sooner. The first was not completed until April.
• It should be noted / recorded that most of these tools require more than just one software upgrade a year in order to keep them up to date and tools like bamboo and python release vital security patches via upgrades, therefore it must be questioned whether an annual upgrade project is the best way to handle this going forwards / or if provision should be put in place to handle multiple upgrades.

Outstanding Issues

Bamboo

 Bamboo JIRA INF139-21 will be carried forward to next year's project. It has useful information to be aware of before expecting Bamboo upgrade to work

• INF139-21 Bamboo must be reviewed in the next project implementing Bamboo

• Bamboo to install latest stable version - Bamboo on Dev, Test, Live environments this JIRA must be reviewed in next year's project

Python

For a future review  - may consider creating a new Python environment instead of upgrading existing servers

Password Manager Pro (PMP)

PMP was successfully upgraded, 6 versions, in TEST within this project, however there was not enough time to complete LIVE.  Production Management agreed to complete the PMP LIVE upgrade in August within the support budget (with agreement of the Infrastructure Application Support manager.

This decision provides the result that PMP is upgraded in LIVE during August 19 after the project closes.

General

Final recommendations should be made at the start of the next project - in the Brief

Development Tools

• allow production management to perform upgrades where no infrastructure change is required and to
• allow dev tech to perform upgrades where there are infrastructure changes.