HiveBrain v1.2.0
Get Started
← Back to all entries
patternMinor

Decoupling data of devops tools eg jenkins nexus

Submitted by: @import:stackexchange-devops··
0
Viewed 0 times
jenkinsnexusdecouplingtoolsdatadevops

Problem

Building devops pipe with tools such as Jenkins, Nexus, Hashicorp etc.. Deploying via terraform ansible & packer. Intending to use load balancers in front of each tool, want to deploy tools listed above with their data decoupled enabling easier tear down for updates etc. (eg load balance x2, nexus x2, data ?) Does anyone have any advice or suggested examples of how this is achieved. Not quite ready for containers, but trying to decouple data now in readiness for such a change. Cloud provider not defined yet AWS, Open Stack etc etc ?? Thoughts welcomed.

Solution

You might want to explore immutable architecture.

Steps

-
CI with static analysis(Sonarqube, because free!), pushing version artefacts to Nexus.

-
Base Image using Packer. These must be revisited from time to time. Base Image has security hardening, log shippers, monitoring tools etc.

-
Environment/Application specific images from Base image.

-
healthCheck and version API for each application(healthCheck API in deployment and version for visibility of code in different VMs).

-
Deploy App using Terraform and Ansible.

Can use Jenkins 2.0 (pipeline as code) to achieve points 1,2,3. It can be part of each application itself.

Let me know if this answers your question.

Context

StackExchange DevOps Q#1540, answer score: 4

Revisions (0)

No revisions yet.