Cloud Devops Automation

Change Management:- Change management is fundamental function and all the rest are build around it as core idea. it defines what the system needs to look like and make sure what it is, if its not that state you enforce it. For e.g. A webserver should have apache installed and wanted to installed at version 2.4 and should have started state and anything which deviates from this defined state you dictate a change state and mark that system as changed. System marked changed makes sense more in production system because production system shouldn't be changed like that and you might want to find the cause for the same. In case of ansible if a system state is same even after change ansible wouldn't even try to change its state and this is called idempotent. Provisioning:- It is built on the change management but it is focussed on a role you are trying to establish. The most basic definition of provisioning is you are transitioning from one system state to another system ...

The ELB logs provides the great insights about the traffic being received by your application. You can identify the location, requests, errors and attacks by analyzing the ELB logs. Your  security team might be interested in analyzing these logs. The problem is the logs are written either in 1 hour or every 5 minutes. You can also set them at  a definite size of 5MB. If you choose 1 hour than the size of the file  would be big. So it makes sense that logs are written at every 5 minutes since you want to analyze current requests coming on the ELB. The problem in setting Rsyslog is the AWS logs are generated dyamica pattern and date yyyy/mm/dd keep on rotating. Other problem is everytime a new log file is generated and thirdly logs are written in the S3 bucket which is a storage only and have very low computing power. We used the S3fs to mount the S3 as a mount on the server this provided the easy access to logs on the s3. The other problem was all multiple applica...

Check if anything is running on the port 8080 which is used by the jenkins by default telnet localhost 8080   Install the Java JDK which is required by the Jenkins mkdir /usr/java   cd /usr/java wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u92-b14/jdk-8u92-linux-x64.tar.gz tar -xf jdk-8u92-linux-x64.tar.gz cd jdk1.8.0_92/ update-alternatives --install /usr/bin/java java /usr/java/jdk1.8.0_92/bin/java 100 update-alternatives --config java update-alternatives --install /usr/bin/javac javac /usr/java/jdk1.8.0_92/bin/javac 100 update-alternatives --config javac update-alternatives --install /usr/bin/jar jar /usr/java/jdk1.8.0_92/bin/jar 100 update-alternatives --config jar Setup the JAVA_HOME vi /etc/rc.d/rc.local   export JAVA_HOME=/usr/java/jdk1.8.0_92/       export JRE_HOME=/usr/java/jdk1.8.0._92/jre     ...