Skip to main content

Saltstack as a Configuration Management Software

Salt is an infrastructure management system and takes a new approach for developing system administration software that is to get running in minutes, scalable to tens of thousands of servers. The Salt open source project was started in 2011. Salt provides a dynamic infrastructure communication bus used for orchestration, remote execution, configuration management. SaltStack is the company responsible for keeping the Salt project healthy and dynamic. Salt remains 100% open.

Installing Salt on RHEL/Centos Systems:

From the 0.9.4 release Salt has been available in EPEL repos. To enable EPEL:
# rpm -Uvh http://ftp.linux.ncsu.edu/pub/epel/6/i386/epel-release-6-8.noarch.rpm

Salt is divided into two packages. Minion and the master. It is necessary only to install the suitable package for the role the machine will play. In general, there is one master and multiple minions.

On the master, install salt-master:
# yum install salt-master 

On each slave node, install salt-minion:
# yum install salt-minion

Ater Installation

Master

To have the Master start automatically at boot:
# chkconfig salt-master on 

To start the Master:
# service salt-master start 

Minion

To have the Minion start automatically at boot:
# chkconfig salt-minion on 

To start the Minion:
# service salt-minion start

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter: