DevOps Deployer

by | May 3, 2021

Job Type: Full Time

In the scope of this project, the ITSM3 Operations team will perform the following activities:

1.1.1.1       Low Level Design (LLD)

The Low Level Design of this project will tackle the Design of the Infrastructure and  Connectivity, the definition of the needed Software (including licences) and the to be implemented Authentication/Authorization mechanism to facilitate the Installation and enablement of the following versions of the following tools in the TAXUD DC:

The design will propose for these tools to be installed on virtualised infrastructure already available in the DG TAXUD Data Centre.

As part of this Low Level design, the following generic activities will be undertaken for each of the tools:  

  • A Logical view of the components (Infrastructure + Middleware) that will be deployed will be constructed
  • A System Context, describing the purpose of each of the tools
  • Physical view will be constructed containing:
    • Virtualization specifying:
      • VM cluster
      • RAM, CPU, Disk Layout for the VMs
      • Network Interfaces
      • OS Version 
    • Storage
    • Network setup (VLAN definition) and connectivity between the new VMs, existing VMs and Stepping Stones, Internet and Common DateCentre Services
    • A Connectivity Matrix
    • Operating System details (if there are specificities)
    • Backup
    • Monitoring
    • Licensing
    • Security
    • High Availability
    • Disaster Recovery
    • System Build parameters for Each VM based on above information 
  • A specific view on the Configuration for each of the Tools that will be subsequently used when installing the actual tools.

Next to above generic topics, specific considerations are to be taken into account for the individual tools:

Nexus

The storage needs for this Artefact repository can be important. Therefore, the initial Sizing of the file system will only take an initial limited use of Nexus for the following teams into account and double that for initial capacity needs:

  • VM Templates
  • Current Oracle and other to ITSM3 Operations middleware COTS Packages
  • 5 TATAFng, ICS2 Releases  

Support: At the time of writing of this Technical Annex, according to the Official Sonatype Nexus website, the only version that offers support is the Pro version (https://sonatype.drift.click/oss-vs-pro). Even though there is an Open Source version, there is no support available for this version. Moreover, in order to support the Nexus repository in a Production setup, a High-Available setup will be designed. As far as ITSM3 Operations can tell at this stage, this is a supported setup. If this does not prove to be the case, High Availability at the level of the VM level only will be foreseen.

Jenkins

Since Jenkins will not be used immediately by the ITSM3 Operations teams, it is difficult to state to which systems (other then the tooling described here) Jenkins will need access to. The Connectivity Matrix will thus only be an initial one, that needs to be amended as time and usage of this tool goes by and increases.

Support: At the time of writing of this Technical Annex, according to the official Jenkins website; there are multiple support options available (https://wiki.jenkins.io/display/JENKINS/Commercial+Support). The most mature one seems CloudBees CI support (https://www.cloudbees.com/products/continuous-integration). It is unclear weather a High Available setup is possible at Jenkins level, meaning we will base the High-Availability setup on the Capabilitites on VM level only.

BitBucket

Currently, several ITSM3 Operations teams are already using a repository to share Code amongst team members. These teams are exhaustively defined as such for the moment:

  • SMT Development Team
  • Network team (Firewall, Load Balancing and other configurations)
  • UNIX Team (Ansible Playbooks)
  • Middleware Team (WLST Scripts and Ansible Playbooks)

Only these teams will be connected to the BitBucket system and they will be storing their scripts and code in the central location, as per the to be updated procedures that are in scope of this project

Support: At the time of writing of this Technical Annex, according to the official BitBucket Website, the solution to go for would be Atlassian BitBucket Datacentre, which provides the need capabilities to be able to host Bitbucket in an operationally sound manner. A High-Available setup will be designed. As far as ITSM3 Operations can tell at this stage, this is a supported setup. If this does not prove to be the case, High Availability at the level of the VM level only will be foreseen

1.1.1.2       Implementation of XXX according to the LLD

During this phase of the project, following activities will be undertaken:

  • Installation and enablement of tools references Section 1.2.1: “Low Level Design (LLD)” in the TAXUD DC;
  • Security/risk assessments and usage procedures for Nexus, Jenkins, and BitBucket;
  • Impact assessment of change of infrastructure, and revision/update of Deployable infrastructure and operational management procedures – this shall cover changes relevant to both code management tools and VM/COTS provisioning and configuration

More details on the scope of each of them is described in below chapters

1.1.1.2.1      Installation of the Tools in Scope

During this phase of the project, the needed virtual infrastructure will be provisioned. The needed Connectivity between the components identified and described in the Low Level Design shall also be implemented.

Where possible and relevant, the Authentication and Authorisation  system of the tools will be connected from an infrastructure level.

This will enable the Installation of the Tools, and the creation of their Admin Accounts for the relevant Teams.

Next, the needed tools will be installed as per the setup Described in the Low Level Design

Apply for this position

Allowed Type(s): .pdf, .doc, .docx