This is a short step-by-step guide on installing ElasticSearch LogStash and Kibana Stack on a CentOS environment to gather and analyze logs.
rpm -ivh https://dl.dropboxusercontent.com/u/5756075/jdk-7u45-linux-x64.rpm
<pluginManagement> | |
<plugins> | |
<!-- | |
The RPM plugin is used to create distributable apps from our war file. | |
To use it fire: | |
$ mvn install rpm:rpm | |
... | |
The resulting rpm is then found at Project/target/rpm/Project/RPMS/noarch/Project-versoin-1.noarch.rpm | |
For example: ImageServer/target/rpm/ImageServer/RPMS/noarch/ImageServer-6.5.0-1.noarch.rpm |
# Generate the csr / key | |
openssl genrsa -des3 -out server.key 1024 | |
# Generate the CSR | |
openssl req -new -key server.key -out server.csr | |
# Remove the password from the key | |
cp server.key server.key.org | |
openssl rsa -in server.key.org -out server.key |
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
Vagrant::Config.run do |config| | |
vmbox = "precise64" | |
vmboxurl = "http://files.vagrantup.com/precise64.box" | |
gluster_repo = "http://download.gluster.org/pub/gluster/glusterfs/LATEST/Ubuntu/12.04/glusterfs_3.3.0-1_amd64.deb" | |
gluster_file = "glusterfs_3.3.0-1_amd64.deb" |
#!/bin/bash | |
# | |
# This is the script responsible for updating our Puppet master data, | |
# which includes modules, manifests, hiera data, etc. All of this data is | |
# managed in a git repository and upon "deploy" it is synced into the Puppet | |
# master. | |
# | |
# This script mirrors the remote git repository, looking for branches that | |
# match "env-*" (such as "env-production" or "env-test"). Each of these branches | |
# is setup as an environment into the Puppet master's data files. The |
#!/usr/bin/env bash | |
# ~/.osx — http://mths.be/osx | |
# Ask for the administrator password upfront | |
sudo -v | |
# Keep-alive: update existing `sudo` time stamp until `.osx` has finished | |
while true; do sudo -n true; sleep 60; kill -0 "$$" || exit; done 2>/dev/null & |
pipeline { | |
agent any | |
parameters { | |
string(name: 'environment', defaultValue: 'default', description: 'Workspace/environment file to use for deployment') | |
string(name: 'version', defaultValue: '', description: 'Version variable to pass to Terraform') | |
booleanParam(name: 'autoApprove', defaultValue: false, description: 'Automatically run apply after generating plan?') | |
} | |
environment { |
// | |
// Generate diagram legend | |
// | |
// 2020 David GERARD | |
// | |
// For a selected view, create a group named 'Legend', in which will be nested for each concepts type found in view | |
// - a concept, specifically sized to show the pictogram | |
// - a note, to be used to name or explain the concept specifically in the view, hence preventing to rename the concept | |
// That way, | |
// - a model will be a bit polluted but with a specific set of concepts, for legend purpose, prefixed so easily identifiable |