Devops

Introduction

The purpose of the DevOps department is difficult to describe. Sometimes it is best to simply steal ideas from other sources. To give someone a simple one liner of what we do: “We make sure things work”. The details of that statement will be explained below, but the image should provide a good summary.

Plan

The Project Management team under the watchful eye of the BA will lead the organisation and design of technical systems, business models, processes and strategic business needs. This team will be responsible for running projects, such as new client implementation or development priority specifications - delivering every project on time within budget and scope. This team is also responsible for discovering the actual needs of stakeholders and not just what they desire. The purpose of this team is not only to ensure project delivery of external projects, but also internal projects and feature requests.

Create

The Software team is responsible for delivering quality software on time to clients. Clients are not neccesarily external, but can also be ITSI staff and partners. As part of the greater DevOps goal, this software will save it’s users time, costs and effort. The IT department will ensure that hardware and software is place for all teams to do their work as effortless as possible.

Verify, Package, Release

The Sys Ops will ensure the correct software is released to the correct target. This department will spend it’s time improving the continuous integration lifecycle to ensure software is release with as little human intervention possible. This team will see to it that the process is well documented and scalable, both in terms of technology and staff. Gitlab and Gitlab-CI will be the primary technology that ensures software is delivered correctly and on time.

Configure, Monitor

Using Zabbix and SMC, the Sys Ops team will ensure maximum uptime by continuously monitoring servers and configuring both systems and software where neccesary.