<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vardhan NS on Medium]]></title>
        <description><![CDATA[Stories by Vardhan NS on Medium]]></description>
        <link>https://medium.com/@vardhan_ns?source=rss-4a674e17ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TlrYvujC-RscQTE1uqxr0Q.jpeg</url>
            <title>Stories by Vardhan NS on Medium</title>
            <link>https://medium.com/@vardhan_ns?source=rss-4a674e17ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:20:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vardhan_ns/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Top Nagios Interview Questions For 2021]]></title>
            <link>https://medium.com/edureka/nagios-interview-questions-f3719926cc67?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3719926cc67</guid>
            <category><![CDATA[devops-tool]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nagios]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[interview-questions]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Fri, 28 Aug 2020 04:30:41 GMT</pubDate>
            <atom:updated>2021-02-09T07:10:26.361Z</atom:updated>
            <content:encoded><![CDATA[<h3>Nagios Interview Questions</h3><p>Nagios is one of the most widely used tools for Continuous Monitoring. Since organizations are now releasing software more frequently than ever so there is a dire need for a tool that can monitor the functioning of the software and provide teams with the relevant feedback. This is one of the reasons that brought Continuous Monitoring into the picture. This makes Nagios a very important tool to implement DevOps. So below is the list of <strong>Nagios Interview Questions</strong>. I have collected these questions after doing a lot of research and after discussing with some of the experts who are directly involved in the hiring process.</p><p>The first question in this article has to be:</p><h3>Q1. What is Nagios?</h3><p>You can answer this question by first mentioning that:</p><p>Nagios is one of the monitoring tools that is used for Continuous monitoring of systems, applications, services, and business processes, etc. in a DevOps culture. In the event of a failure, Nagios can alert the technical staff of the problem, allowing them to begin remediation processes before outages affect business processes, end-users, or customers. With Nagios, you don’t have to explain why an unseen infrastructure outage affects your organization’s bottom line.</p><p>Few of its important features are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_jfcz_Xf_gEWf6tSpnj7A.png" /></figure><p>Now, once you have defined what is Nagios, you can mention the various things that you can achieve using Nagios.</p><p>By using Nagios you can:</p><ul><li>Plan for infrastructure upgrades before outdated systems cause failures.</li><li>Respond to issues at the first sign of a problem.</li><li>Automatically fix problems when they are detected.</li><li>Coordinate technical team responses.</li><li>Ensure your organization’s SLAs are being met.</li><li>Ensure IT infrastructure outages have a minimal effect on your organization’s bottom line.</li><li>Monitor your entire infrastructure and business processes.</li></ul><p>This overall completes the answer to this question. Further details like advantages etc. can be added as per the direction where the discussion is heading.</p><h3>Q2. How does Nagios work?</h3><p>I will advise you to follow the below explanation for this answer:</p><ul><li>Nagios runs on a server, usually as a daemon or service.</li><li>Nagios periodically runs plugins residing on the same server, they contact hosts or servers on your network or on the internet.</li><li>One can view the status information using the web interface.</li><li>You can also receive email or SMS notifications if something happens.</li><li>The Nagios daemon behaves like a scheduler that runs certain scripts at certain moments.</li><li>It stores the results of those scripts and will run other scripts if these results change. Refer to the diagram below:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*wvG0xUwUltM1oJMk.png" /></figure><p><em>Now, the next set of Nagios interview questions will focus on Nagios components like Plugins, NRPE, etc.</em></p><h3>Q3. What are Plugins in Nagios?</h3><p>Begin this answer by defining Plugins.</p><p>Plugins are scripts (Perl scripts, Shell scripts, etc.) that can run from a command line to check the status of a host or service. Nagios uses the results from the plugins to determine the current status of hosts and services on your network.</p><p>Once you have defined Plugins I will suggest you explain why we need plugins.</p><p>Nagios will execute a plugin whenever there is a need to check the status of a host or service. The plugin will perform the check and then simply returns the result to Nagios. Nagios will process the results that it receives from the Plugin and take the necessary actions.</p><h3>Q4. What is NRPE (Nagios Remote Plugin Executor) in Nagios?</h3><p>For this answer first give a small definition of NRPE.</p><p>The NRPE addon is designed to allow you to execute Nagios plugins on remote Linux/Unix machines. The main reason for doing this is to allow Nagios to monitor “local” resources (like CPU load, memory usage, etc.) on remote machines. Since these public resources are not usually exposed to external machines, an agent like NRPE must be installed on the remote Linux/Unix machines.</p><p>Now I will advise you to explain the NRPE architecture on the basis of the diagram shown below.</p><p>The NRPE addon consists of two pieces:</p><ul><li>The check_nrpe plugin, which resides on the local monitoring machine.</li><li>The NRPE daemon, which runs on the remote Linux/Unix machine.</li></ul><p>There is an SSL (Secure Socket Layer) connection between the monitoring host and the remote host as shown in the diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*y7ekbU-_nSUvfBRCiP9Q_Q.png" /></figure><h3>Q5. What is meant by Nagios backend? (unable to find a relevant explanation)</h3><p>My advice will be to follow the below mention flow for this answer:</p><p>Both Configuration and Logs can be stored in a backend. Configurations are stored in the backend using NagiosQL. Historical data are stored using ndoutils. In addition, you also have nagdb and opdb.</p><p><strong><em>Now, the next set of Nagios interview questions will dig in deep so be prepared.</em></strong></p><h3>Q6. What do you mean by passive check in Nagios?</h3><p>According to me, the answer should start by explaining what is Passive check.</p><p>Passive checks are initiated and performed by external applications/processes and the Passive check results are submitted to Nagios for processing.</p><p>Now I will advise you to explain the need for a Passive check.</p><p>Passive checks are useful for monitoring services that are Asynchronous in nature and cannot be monitored effectively by polling their status on a regularly scheduled basis. It can also be used for monitoring services that are Located behind a firewall and cannot be checked actively from the monitoring host.</p><p><em>The interviewer will now dig deep, so the next set of Nagios interview questions will test your experience with Nagios.</em></p><h3>Q7. When Does Nagios Check for external commands?</h3><p>Make sure that you stick to the question during your explanation so I will advise you to follow the below mentioned flow:</p><p>Nagios check for external commands under the following conditions:</p><ul><li>At regular intervals specified by the command_check_interval option in the main configuration file or,</li><li>Immediately after event handlers are executed. This is in addition to the regular cycle of external command checks and is done to provide immediate action if an event handler submits commands to Nagios.</li></ul><h3>Q8. What is the difference between Active and Passive check in Nagios?</h3><p>For this answer first point out the basic difference Active and Passive check.</p><p>The major difference between Active and Passive checks is that Active checks are initiated and performed by Nagios, while passive checks are performed by external applications.</p><p>If your interviewer is looking unconvinced with the above explanation then I will suggest you to also mention some key features of both Active and Passive checks:</p><p>Passive checks are useful for monitoring services that are:</p><ul><li>Asynchronous in nature and cannot be monitored effectively by polling their status on a regularly scheduled basis.</li><li>Located behind a firewall and cannot be checked actively from the monitoring host.</li></ul><p>The main features of Actives checks are as follows:</p><ul><li>Active checks are initiated by the Nagios process.</li><li>Active checks are run on a regularly scheduled basis.</li></ul><h3>Q9. How does Nagios help with Distributed Monitoring?</h3><p>The interviewer is expecting an answer related to the distributed architecture of Nagios so I will suggest you to answer it in the below-mentioned format:</p><p>With Nagios, you can monitor your whole enterprise by using a distributed monitoring scheme in which local slave instances of Nagios perform monitoring tasks and report the results back to a single master. You manage all configuration, notification, and reporting from the master, while the slaves do all the work. This design takes advantage of Nagios’s ability to utilize passive checks i.e. external applications or processes that send results back to Nagios. In a distributed configuration, these external applications are other instances of Nagios.</p><h3>Q10. Explain the Main Configuration file of Nagios and its location?</h3><p>I will suggest you to first mention what this main configuration file contains and its function.</p><p>The main configuration file contains a number of directives that affect how the Nagios daemon operates. This config file is read by both the Nagios daemon and the CGIs (It specifies the location of your main configuration file).</p><p>Now you can tell where it is present and how it is created.</p><p>A sample main configuration file is created in the base directory of the Nagios distribution when you run the configure script. The default name of the main configuration file is nagios.cfg, it is usually placed in the etc/ subdirectory of you Nagios installation (i.e. /usr/local/nagios/etc/).</p><p><em>I hope you have enjoyed the above set of Nagios interview questions, the next set of questions will be more challenging, so be prepared.</em></p><h3>Q11. Explain how Flap Detection works in Nagios?</h3><p>I will advise you to first explain Flapping first.</p><p>Flapping occurs when a service or host changes state too frequently, this causes a lot of problems and recovery notifications.</p><p>Once you have defined Flapping explain how Nagios detects Flapping.</p><p>Whenever Nagios checks the status of a host or service, it will check to see if it has started or stopped flapping. Nagios follow the below procedure to do that:</p><ul><li>Storing the results of the last 21 checks of the host or service analyzing the historical check results and determine where state changes/transitions occur.</li><li>Using the state transitions to determine a percent state change value (a measure of change) for the host or service.</li><li>Comparing the percent state change value against low and high flapping thresholds</li><li>A host or service is determined to have started flapping when its percent state change first exceeds a high flapping threshold.</li><li>A host or service is determined to have stopped flapping when its percent state goes below a low flapping threshold.</li></ul><h3>Q12. What are the three main variables that affect recursion and inheritance in Nagios?</h3><p>According to me the proper format for this answer should be:</p><p>First name the variables and then a small explanation of each of these variables:</p><p>Now I will give a small explanation for each of these variables.</p><ul><li>Name</li><li>Use</li><li>Register</li></ul><p>Name is a placeholder that is used by other objects. Use defines the “parent” object whose properties should be used. The register can have a value of 0 (indicating its only a template) and 1 (an actual object). The register value is never inherited.</p><h3>Q13. What is meant by saying Nagios is Object-Oriented?</h3><p>Answer to this question is pretty direct I will answer this by saying:</p><p>One of the features of Nagios is object configuration format in that you can create object definitions that inherit properties from other object definitions and hence the name. This simplifies and clarifies relationships between various components.</p><h3>Q14. What is State Stalking in Nagios?</h3><p>I will advise you to first give a small introduction to State Stalking.</p><p>State Stalking is used for logging purposes. When Stalking is enabled for a particular host or service, Nagios will watch that host or service very carefully and log any changes it sees in the output of check results.<br> Depending on the discussion between you and interviewer you can also add:</p><p>It can be very helpful in the later analysis of the log files. Under normal circumstances, the result of a host or service check is only logged if the host or service has changed state since it was last checked.</p><h3>Q15. Nagios says my machine is unreachable, not down. What is the difference and how it is achieved?</h3><p>First I will suggest you to explain:</p><p>When Nagios says a node is unreachable, a node is unreachable if Nagios is not able to find a path to the node.</p><p>Now you can mention the difference.</p><p>The node itself may be up but because Nagios is unable to connect to it, it has to mark this as unreachable. To achieve this, Nagios use the parent-child relationship between components.</p><p>Finally, for better understanding explain it with an example.</p><p>A router may be defined as a parent for a server.</p><ul><li>Now, Nagios checks for the server and marks it as down.</li><li>It then checks the parent (in our example, the router)</li><li>If the parent is also down, then the server is marked as unreachable.</li><li>If Parent is up, the server is marked as really down.</li></ul><h3>Q16. Explain Nagios&#39; state types?</h3><p>According to me the best way to put this answer is by saying:</p><p>The current state of monitored services and hosts is determined by two components:</p><ul><li>The status of service or host i.e. OK, WARNING, UP, DOWN, etc..</li><li>The type of state the service or host is in.</li></ul><p>There are two types of states SOFT states and HARD states.</p><p>Now explain what is Soft and Hard states:</p><ul><li>When a service or host check results are in a non-OK or non-UP state and the service check has not yet been rechecked the number of times specified by the max_check_attempts directives in the service or host definition. This is called Soft Error. When a service or a host recovers from Soft Error that is considered as Soft Recovery.</li><li>When a service or host check results are in a non-OK or non-UP state and the service check has been rechecked the number of times specified by the max_check_attempts directives in the service or host definition. This is called Hard Error. When a service or a host recovers from Hard Error that is considered as Hard Recovery.</li></ul><p>This is the end of my article on Nagios interview questions. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=nagios-interview-questions">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/docker-architecture-be79628e076e"><em>Docker Architecture</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/interview-questions/nagios-interview-questions/"><em>https://www.edureka.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3719926cc67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67">Top Nagios Interview Questions For 2021</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Jenkins X and how is it Different from Jenkins?]]></title>
            <link>https://medium.com/edureka/jenkins-x-d87c0271af57?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/d87c0271af57</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[jenkins-x]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Mon, 16 Dec 2019 13:20:03 GMT</pubDate>
            <atom:updated>2020-09-09T12:11:57.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*bUa4LXj7GzYMenDDXQkE-g.jpeg" /></figure><p>Jenkins is one of the most famous Continuous Integration tools and an integral part of DevOps that is often used to integrate various <strong><em>DevOps stages</em></strong>. Following the success of Jenkins, a new version of Jenkins has been introduced lately called Jenkins X (JX). It provides continuous integration, automated testing, and continuous delivery to Kubernetes. Through this article, I am going to provide you a complete insight into Jenkins X and the topics that we are going to cover are as follows:</p><ul><li>What is Jenkins X?</li><li>Jenkins Vs Jenkins X</li><li>Features of Jenkins X</li><li>How Jenkins X works?</li><li>Installing Jenkins X</li></ul><p>So let us begin with our first topic.</p><h3>What is Jenkins X?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/0*OCp5uzEV_E6xq6bs.png" /></figure><p>Jenkins X was first introduced by James Strachan (creator of Groovy, Apache Camel) in March 2018. It’s designed from the ground up to be a cloud-native, Kubernetes-only application that not only supports CI/CD but also makes working with Kubernetes as simple as possible. With one command you can create a Kubernetes cluster, install all the tools you’ll need to manage your application. You can also create build and deployment pipelines, and deploy your application to various environments.</p><p>Jenkins is described as an <em>“</em><strong><em>extensible automation server</em></strong><em>”</em> that is configured, via plugins, to be a Continuous Integration Server, a Continuous Deployment hub, or a tool to automate just about any software task. JX provides a specific configuration of Jenkins, meaning you don’t need to know which plugins are required to stand up a CI/CD pipeline. It also deploys numerous applications to Kubernetes to support building your docker container, storing the container in a docker registry, and deploying it to Kubernetes.</p><h3>Jenkins Vs Jenkins X</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*wsHwLaoVEzmHxCnPh7luPg.png" /></figure><h3>Features of Jenkins X</h3><h4><strong>Automated CI /CD:</strong></h4><p>Jenkins X offers a sleek jx command-line tool, which allows Jenkins X to be installed inside an existing or new Kubernetes cluster, import projects, and bootstrap new applications. Additionally, Jenkins X creates pipelines for the project automatically.</p><h4><strong>Environment Promotion via GitOps:</strong></h4><p>Jenkins X allows for the creation of different virtual environments for development, staging, and production, etc. using the Kubernetes Namespaces. Every environment gets its specific configuration, list of versioned applications and configurations stored in the Git repository. You can automatically promote new versions of applications between these environments if you follow GitOps practices. Moreover, you can also promote code from one environment to another manually and change or configure new environments as needed.</p><h4><strong>Extensions:</strong></h4><p>It is quite possible to create extensions to Jenkins X. An extension is nothing but a code that runs at specific times in the CI/CD process. You can also provide code through an extension that runs when the extension is installed, uninstalled, as well as before and after each pipeline.</p><h4><strong>Serverless Jenkins:</strong></h4><p>Instead of running the Jenkins web application, which continually consumes a lot of CPU and memory resources, you can run Jenkins only when you need it. During the past year, the Jenkins community has created a version of Jenkins that can run classic Jenkins pipelines via the command line with the configuration defined by code instead of the usual HTML forms.</p><h4><strong>Preview Environments:</strong></h4><p>Though the preview environment can be created manually, Jenkins X automatically creates Preview Environments for each pull request. This provides a chance to see the effect of changes before merging them. Also, Jenkins X adds a comment to the Pull Request with a link for the preview for team members.</p><h3>How Jenkins X works?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*jiHE2DTabS0tnbsrJVHbiQ.png" /></figure><ol><li>The developer commits and pushes the change to the project’s Git repository.</li><li>JX is notified and runs the project’s pipeline in a Docker image. This includes the project’s language and supporting frameworks.</li><li>The project pipeline builds, tests, and pushes the project’s Helm chart to Chart Museum and its Docker image to the registry.</li><li>The project pipeline creates a PR with changes needed to add the project to the staging environment.</li><li>Jenkins X automatically merges the PR to Master.</li><li>Jenkins X is notified and runs the staging pipeline.</li><li>The staging pipeline runs Helm, which deploys the environment, pulling Helm charts from Chart Museum and Docker images from the Docker registry. Kubernetes creates the project’s resources, typically a pod, service, and ingress.</li></ol><p>Now that you about the architecture of Jenkins X, let us see how to install Jenkins X.</p><h3>Installation of Jenkins X</h3><p>In this section, I will show you how to install Jenkins X on Linux and Windows operating systems.</p><h4>1. Linux</h4><p>To install JX on Linux, download the.tarfile, and unarchive it in a directory where you can run the jx command.</p><ol><li>Download thejxbinary archive usingcurland pipe (|) the compressed archive to thetarcommand:</li></ol><pre>curl -L &quot;https://github.com/jenkins-x/jx/releases/download/$(curl --silent https://api.github.com/repos/jenkins-x/jx/releases/latest | jq -r &#39;.tag_name&#39;)/jx-linux-amd64.tar.gz&quot; | tar xzv &quot;jx&quot;</pre><p>or, if you don’t have jq installed:</p><pre>curl -L &quot;https://github.com/jenkins-x/jx/releases/download/$(curl --silent &quot;https://github.com/jenkins-x/jx/releases/latest&quot; | sed &#39;s#.*tag/(.*)\&quot;.*#1#&#39;)/jx-linux-amd64.tar.gz&quot; | tar xzv &quot;jx&quot;</pre><p>2. Install thejxbinary by moving it to a location in your executable path using themvcommand:</p><p>3. Runjx --versionto make sure you&#39;re on the latest stable version</p><h4>2. Windows</h4><p>You can install it on Windows through Chocolatey. This is a third-party package management system that provides convenient one-step commands for local Jenkins X installations and upgrades.</p><p>Install the Chocolatey package management system using an Administrative Shell:</p><ol><li>Right-click menu: Start[Command Prompt (Admin)].</li><li>At the shell prompt, execute a powershell.exethe command to download and install the choco binary and set the installation path so that the binary can be executed:</li></ol><pre>@&quot;%SystemRoot%System32WindowsPowerShellv1.0powershell.exe&quot; -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command &quot;iex ((New-Object <br>System.Net.WebClient).DownloadString(&#39;https://chocolatey.org/install.ps1&#39;))&quot; &amp;&amp; SET &quot;PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin&quot;</pre><p>3. Install JX using Chocolatey:</p><p>choco install jenkins-x</p><p>You can update to the latest version of Jenkins X using Chocolatey:</p><p>choco upgrade jenkins-x</p><ul><li>If you use scoop, then there is a manifest available.</li></ul><p>— To install the jx binary run:</p><p>scoop install jx</p><p>— To upgrade the jx binary run:</p><p>scoop update jx</p><p>So that was all about the installation process.</p><p>If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=jenkins-x">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/maven-tutorial-2e87a4669faf"><em>Maven For Building Java Applications</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/jenkins-x/"><em>https://www.edureka.co</em></a><em> on December 16, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d87c0271af57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/jenkins-x-d87c0271af57">What is Jenkins X and how is it Different from Jenkins?</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How DevOps is used in Real Time Scenarios?]]></title>
            <link>https://medium.com/edureka/devops-real-time-scenarios-c277991745c1?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/c277991745c1</guid>
            <category><![CDATA[devops-example]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Fri, 06 Dec 2019 13:36:24 GMT</pubDate>
            <atom:updated>2021-02-09T09:42:08.339Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps Real-Time Scenarios — Know What Happens Real-Time</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*jnkVdkowCaP1Pc5_rJrRQg.jpeg" /><figcaption>DevOps Real-Time Scenarios — Edureka</figcaption></figure><p>Many of you might be aware of all the theories related to DevOps. But do you know how to implement DevOps principles in real life? In this article, I will discuss the DevOps Real Time scenarios that will help you get a brief understanding of how things work in real-time.</p><p>The pointers that I will be covering in this DevOps Real-Time Scenarios article are:</p><ul><li><em>What is DevOps?</em></li><li><em>Problems solved by DevOps</em></li><li><em>CI(Continuous Integration) Scenarios</em></li><li><em>CT(Continuous Testing) Scenarios</em></li><li><em>CD(Continuous Delivery) Scenarios</em></li><li><em>DevOps Data Scenarios</em></li></ul><p>So let us begin with our first topic.</p><h3>What is DevOps?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*lR4rE_Mcm7Q--EUdgY6KYQ.png" /></figure><p>DevOps is a software development approach that involves Continuous Development, Continuous Testing, Continuous Integration, Continuous Deployment, and Continuous Monitoring of the software throughout its development life cycle. These activities are possible only in DevOps, not Agile or waterfall. This is why Facebook and other top companies have chosen DevOps as the way forward for their business goals. DevOps is mainly preferred for developing high-quality software in shorter development cycles which results in greater customer satisfaction.</p><p>In the next section of this DevOps Real-Time Scenarios article, we will take a look on the various problems solved by DevOps.</p><h3>Problems solved by DevOps</h3><h4>1. Deliver value to Customers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*ny4VKUKQ7d74yOpidY_hGw.png" /></figure><ul><li>DevOps <strong><em>minimizes the time</em></strong> it takes to deliver value to customers. The cycle time from the developer’s completion of a story/task until production reduces significantly, allowing the value to be realized as quickly as possible.</li><li>The most important value realized through DevOps is that it allows IT organizations to <strong><em>focus on their “core” business activities</em></strong>. By removing constraints within the value stream and automating deployment pipelines, teams can focus on the activities. This helps in creating customer value rather than just moving bits and bytes. These activities increase the sustainable competitive advantage of a company and create better business outcomes.</li></ul><h4>2. Reduced cycle time</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*tdmu2tfFq7tFcelJwflsVg.png" /></figure><ul><li>Internally DevOps is the only way to achieve the agility to deliver secure code with insights. It is important to have gates and a well-crafted DevOps process. When you are delivering a new version, it can run side-by-side with the current version. You can also compare metrics to accomplish what you wanted to with application and performance metrics.</li><li>DevOps drive development teams towards <strong><em>continuous improvement and faster release cycles</em></strong>. If done well, this iterative process allows more focus over time, on the things that really matter. Such as things that create great experiences for users — and less time on managing tools, processes, and tech.</li></ul><h4>3. Time to market</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/247/1*WICyC4t-GEDv-9i0L-ueaA.png" /></figure><p>The most important problem being solved is the <strong><em>reduction of the complexity of the process. </em></strong>This contributes significantly towards our business success by shortening our time to market, giving us quick feedback on features, and making us more responsive to our customers’ needs.</p><h4>4. Problem Resolution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*vV5do3airwGcuJ3FWs7qAA.png" /></figure><ul><li>The greatest value of successful DevOps implementation is higher confidence in delivery, visibility, and traceability to what’s going on, so you can solve problems quicker.</li><li>Another important advantage of DevOps is not wasting any time. Aligning an organization’s people and resources enables rapid deployments and updates. This allows DevOps programs to fix problems before they turn into disasters. DevOps creates a culture of transparency that promotes focus and collaboration among development, operations, and security teams.</li></ul><h3>CI (Continuous Integration) in DevOps Real Time Scenarios</h3><h4>1. Individuals May See Continuous Integration Counterproductive</h4><p>Members of a development team have different roles, responsibilities, and priorities. It is possible that the Product manager’s first priority might be launching new features, project managers have to make sure that their team meets the deadline. Programmers might think that if they stop to fix a minor bug every time it occurs will slow them down. They might feel keeping the build clean is an extra burden on them and they won’t be the benefitted for their extra efforts. This can potentially jeopardize the adaptation process.</p><p><strong><em>To overcome this:</em></strong></p><ul><li>Firstly, make sure your whole team is on board before you adopt continuous integration.</li><li>CTOs and team leaders must help the team members understand the costs and benefits of continuous integration.</li><li>Highlight what and when coders will be benefitted by dedicating themselves to a different working method that requires a bit more openness and flexibility.</li></ul><h4>2. Integrating CI Into Your Existing Development Flow</h4><p>Adopting CI inevitably comes with the need for essentially changing some parts of your development workflow. It is possible that your developers might not fix the workflow if it isn’t broken. This is possible mainly if your team has a bigger routine in executing their current workflow.</p><p>If you wish to change the workflow then you must do it with great precautions. Otherwise, it could compromise the productivity of the development team and also the quality of the product. Without sufficient support from the leadership, the development team might be a bit reluctant to undertake a task with such risks involved.</p><p><strong><em>To overcome this:</em></strong></p><ul><li>You must make sure that you give enough time for your team to develop their new workflow. This is done in order to select a flexible continuous integration solution that can support their new workflow.</li><li>Also, ensure them that company has their backs even if things might not go very smoothly at the beginning.</li></ul><h4>3. Relapsing to the Former Testing Habits</h4><p>The immediate effect of adopting continuous integration is that your team will test more often. So more tests will need more test cases and writing test cases can be time-consuming. Hence, developers often need to divide their time between fixing bugs and writing test cases.</p><p>Temporarily, developers might be able to save time by manually testing, but it might hurt more in the long run. The more they procrastinate writing test cases, the more difficult it will become to catch up on the progress of the development. In the worst-case scenario, your team might end up going back to their old testing process.</p><p><strong><em>To overcome this:</em></strong></p><ul><li>You must emphasize that writing test cases from the beginning could save a lot of time for your team and can ensure high test coverage of your product.</li><li>Also, embed the idea in your company culture that test cases are as valuable assets as the codebase itself.</li></ul><h4>4. Developers Ignoring Error Messages</h4><p>It is a common problem that when bigger teams work together the amount of CI notifications becomes overwhelming and developers start ignoring and muting them. Therefore, it is possible that they might miss the updates that are relevant to them.</p><p>It can lead to a stage where coders develop a relative immunity to broken builds and error messages. The longer they ignore relevant notifications, the longer they develop without feedback in the wrong direction. This could potentially cause huge rollbacks, wastage of money, resources, and time.</p><p><strong><em>To overcome this:</em></strong></p><ul><li>You should only send critical updates.</li><li>Only send the notification to respective developers who are in charge of fixing it.</li></ul><h3>CT (Continuous Testing) in DevOps Real Time Scenarios</h3><h4>1. Getting Requirements Specification right</h4><p>If you get your requirements right then almost half of the battle is won. So if you have a precise and accurate understanding of requirements, you can design test plans better and cover requirements well.</p><p>Yet, many teams spend a lot of time and effort simply clarifying the requirements. This is a very common pitfall and to avoid this, teams can adopt Model-based testing and Behavior-Driven Development techniques. This helps to design test scenarios accurately and adequately.</p><p>These practices will definitely help address and resolve the gaps more quickly. Also, it enables them to generate more test cases automatically right from the early stages of a sprint.</p><h4><strong>2. Pipeline Orchestration</strong></h4><p>The advantages of continuous testing and continuous delivery are closely tied to pipeline orchestration. This directly means understanding how it works, why it works, how to analyze the results, and how and when to scale. Everything depends on the pipeline and hence you need to integrate the pipeline with the automation suite.</p><p>But the reason teams fumble is that, no single solution provides the complete toolchain that is required to build a CD pipeline.</p><p>Teams have to typically search for the pieces of the puzzle that are correct for them. There are no perfect tools, typically only best-of-breed tools, that provide integrations along with multiple other tools. And of course, an API that permits easy integrations as well.</p><p>In short, it is impossible to implement continuous testing without the speed and reliability of a standardized and automated pipeline.</p><h4><strong>3. Scaling up and managing complexity</strong></h4><p>Another important scenario is that continuous testing becomes more complex as it moves towards the production environment. The tests grow in number as well as complexity with the maturing code and the environment becoming more complex.</p><p>You must update tests each time you update different phases and automated scripts. As a result, the overall time it takes to run the tests also tends to increase towards the release.</p><p>The solution for this lies in improved test orchestration that provides the right amount of test coverage in shorter sprint cycles and enables teams to deliver confidently. Ideally, the entire process must be automated with CT carried out at various stages. This is done by using policy gates and manual intervention, up until the code is pushed to production.</p><h4><strong>4. Creating feedback loops</strong></h4><p>Without frequent feedback loops at every stage of the development cycle, continuous testing is not possible. This is partly the reason why CT is difficult to implement. You don’t just need automated tests, but you also need visibility of the test results and execution.</p><p>Traditional feedback loops like logging tools, code profilers, and performance monitoring tools are not effective anymore. Neither they work together nor provide the depth of insight required to fix issues. Real-time dashboards that generate reports automatically and actionable feedback across the entire SDLC helps release software faster into production with lesser defects. Real-time access to dashboards and access for all team members helps the continuous feedback mechanism.</p><h4><strong>5. Lack of Environments</strong></h4><p>Continuous Testing simply means testing more often and this requires hitting multiple environments more frequently. This presents a bottleneck if the said environments are not available at the time they are required. Some environments are available through APIs and some through various interfaces. Some of these environments can be built using modern architecture while others with monolithic legacy client/server or mainframe systems.</p><p>But the question here is how do you coordinate testing through the various environment owners? It is also possible that they may not always keep the environments up and running. The answer to all this is <strong><em>Virtualization</em></strong>. By virtualizing the environment, you can test the code without worrying too much about areas that are unchanging. Making the environments accessible and available on-demand through virtualization surely helps remove a significant bottleneck from your pipeline.</p><h3>CD(Continuous Delivery) in DevOps Real Time Scenarios</h3><h4><strong>1. Deployments taking too long</strong></h4><p>Distributed applications normally require more than ‘copying and pasting’ files to a server. The complexity tends to increase if you have a farm of servers. Uncertainty about what to deploy, where, and how, is a pretty normal thing. The result? Long waiting times to get our artifacts into the next environment of the route to delaying everything, testing, time to live, etc.</p><p>What does DevOps bring to the table? Development and IT operations teams define a deployment process in a blameless collaboration session. First, they verify what works and then take it to the next level with automation to facilitate continuous delivery. This drastically cuts timing for deployment; it also paves the way for more frequent deployments.</p><h4><strong>2. Missing artifacts, scripts, and other dependencies</strong></h4><p>We frequently encounter failures post the deployment of a new version of a working piece of software. This is often caused by missing libraries or database scripts not being updated. This is usually caused by a lack of clarity about which dependencies to deploy and their location. Fostering collaboration between development and operations can help resolve these sorts of problems in the majority of cases.</p><p>When it comes to automation, you can define dependencies which helps a lot in speeding up deployments. Configuration management tools like Puppet or Chef contribute with an extra level of definition of dependencies. We can define not only dependencies within our application but also at the infrastructure and server configuration level. For example, we can create a virtual machine for a test, and install/configure tomcat before our artifacts are published.</p><h4><strong>3. Ineffective production monitoring</strong></h4><p>Sometimes you configure monitoring tools in a way that produces a lot of irrelevant data from production, however, other times they don’t produce enough or nothing at all. There is no definition of what you need to look after and what the metrics are.</p><p>You must agree on what to monitor and which information to produce, and then put controls in place. Application Performance management tools are a great help if your organization can afford it to take a look at AppDynamics, New Relic, and AWS X-Ray.</p><h3>DevOps Data Scenarios</h3><p>DevOps is all about eliminating the risks associated with new software development: Data analysis identifies those risks. To continuously measure and improve upon the DevOps process, analytics should span across the entire pipeline. This provides invaluable insights to management at all stages of the software development lifecycle.</p><h4>1. Less time to analyze data</h4><p>With all the data that is generated at any given time, organizations need to accept that they can’t analyze it all. There’s simply not enough time in the day — and unfortunately, robots aren’t quite sophisticated enough to do it all for us quite yet.</p><p>For that reason, it’s important to determine which data sets are most significant. In most cases, this is going to be different for every organization. So before diving in, determine key business objectives and goals. Typically, these goals revolve around customer needs — primarily the most valuable features that are most important to end-users. For a retailer, for example, analyzing how traffic is interacting with the checkout page on the site and testing how it works in the back-end is at the top of the list.</p><p>Some quick tips to identify which data is most important to analyze:</p><ul><li>Make a chart: Determine the impact outages will have on your business, asking questions such as, “If <em>X breaks</em>, what effect will it have on other features?”</li><li>Look at historical data: Identify where issues have arisen in the past and continue to analyze data from tests and build to ensure it doesn’t happen again.</li></ul><h4>2. Difficult communication</h4><p>Today, most organizations still operate with different teams and personas identifying their own goals and utilizing their own tools and technologies. Each team acts independently, disconnected from the pipeline and meeting with other teams only during the integration phase.</p><p>When it comes to looking at the bigger picture and identifying what is and isn’t working, the organization struggles to come to one solution. This is because mostly because everyone is failing to share the overall data, making analysis impossible.</p><p>To overcome this issue, overhaul the flow of communication to ensure everyone is collaborating throughout the SDLC, not just during the integration process.</p><ul><li>First, make sure there’s strong synchronization on DevOps metrics from the get-go. Each team’s progress should be displayed in one single dashboard, utilizing the same Key Performance Indicators (KPIs) to give management visibility into the entire process. This is done so that they can collect all the necessary data to analyze what went wrong (or what succeeded).</li><li>Beyond the initial metrics conversation, there should be constant communication via team meetings or digital channels like Slack.</li></ul><h4>3. Lack of manpower</h4><p>When short-staffed, we need smarter tools that utilize deep learning to slot in the data we’re collecting and reach decisions quickly. After all, nobody has time to look at every single test execution (and for some big organizations, there can be about 75,000 in a given day). The trick is to eliminate the noise and find the right things to focus on.</p><p>This is where artificial intelligence and machine learning can help. Many tools on the market today utilize AI and ML to do things like:</p><ul><li>Develop scripts and tests to move and validate different pieces of data</li><li>Report on quality based on previously learned behaviors</li><li>Work in response to real-time changes.</li></ul><p>So with this, we have come to the end of this article on DevOps Real-Time Scenarios.</p><p>If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=devops-real-time-scenarios">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/maven-tutorial-2e87a4669faf"><em>Maven For Building Java Applications</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/devops-real-time-scenarios/"><em>https://www.edureka.co</em></a><em> on December 6, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c277991745c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/devops-real-time-scenarios-c277991745c1">How DevOps is used in Real Time Scenarios?</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn How to Set Up Docker For Windows]]></title>
            <link>https://medium.com/edureka/docker-for-windows-ed971362c1ec?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed971362c1ec</guid>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 09:42:09 GMT</pubDate>
            <atom:updated>2020-09-28T12:51:18.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*OKMs98M_iB32SoZbaomz3g.jpeg" /></figure><p>If you’re looking for simple and painless software deployment, Docker is the right tool for you. It is the best containerization platform and in this blog on Docker for Windows, we’ll specifically focus on how Docker works on Windows.</p><p>I’ll be covering the following topics in this blog:</p><ol><li>Why use Docker For Windows?</li><li>Docker for Windows prerequisites</li><li>Components installed with Docker</li><li>What is Docker?</li><li>Docker Terminologies</li><li>Hands-On</li></ol><h3>Why use Docker for Windows?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*DBHJ3intV9XeqSzZW2TZIA.png" /><figcaption><em>Why use Docker for Windows — Docker for Windows</em></figcaption></figure><ul><li><strong>Avoids the work on my machine but doesn’t work on the production problem:</strong> This problem occurs due to the inconsistent environment throughout the software development workflow. With Docker, you can run an application within a container that contains all the dependencies of the application and the container can be run throughout the software development cycle. This practice provides a consistent environment throughout the software development life cycle</li><li><strong>Improves productivity:</strong> By installing Docker on windows we’re running Docker natively. If you’ve been following Docker for a while, you know that Docker containers originally supported only Linux operating systems. But thanks to the recent release, Docker can now natively run on windows, which means that Linux support is not needed, instead, the Docker container will run on the Windows kernel itself</li><li><strong>Supports native networking:</strong> Not only the Docker container, but the entire Docker toolset is also now compatible with windows. This includes the Docker CLI (client), Docker compose, data volumes and all the other building blocks for Dockerized infrastructure are now compatible with windows. But how is this advantageous? Since all the Docker components are locally compatible with windows, they can now run with minimal computational overhead.</li></ul><h3>Docker For Windows Prerequisites</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*mDdZLNcYPxTVNnVDZN1Rsg.png" /><figcaption><em>Docker for Windows — Prerequisites</em></figcaption></figure><p>The following requirements need to be met before installing Docker on windows:</p><ol><li>Check if you’re using Windows 10, either pro edition or enterprise edition, 64-bit system. Docker will not run on any other windows version. So if you’re running on an older windows version, you can install the Docker toolbox instead.</li><li>Docker for Windows requires a Type-1 hypervisor and in the case of windows, it’s called the Hyper-V. Hyper-V is basically a lightweight virtualization solution built on top of the hypervisor framework. So you don’t need a virtual box, you just have to enable the hypervisor.</li><li>And also you need to enable the virtualization in BIOS. Now when you install Docker for Windows, by default of this is enabled. But in case you’re facing any issue during installation, please check if your Hyper-V and virtualization are enabled.</li></ol><h3>Components Installed With Docker</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tb5WGy6W-Z04uEDpXqm4Wg.png" /><figcaption><em>Components installed with Docker — Docker for Windows</em></figcaption></figure><ol><li>Docker Engine: When we say Docker, we actually mean the Docker engine. The Docker engine contains the Docker daemon, REST API for interacting with the Docker daemon, and a command-line interface client that communicates with the daemon. Docker daemon accepts Docker commands such as Docker run, Docker builds, etc, from the Docker client.</li><li>Docker Compose: Docker compose is used to run multiple Docker containers at once by using a single command, which is docker-compose up.</li><li>Docker Machine: Docker machine is used to install the Docker engine. It is basically what you install on your local system. The Docker machine has it’s own CLI client known as the Docker machine and a Docker engine client called Docker.</li><li>Kitematic: Kitematic is an open-source project built to simplify the use of Docker on Windows. It helps to automate the installation of Docker and it provides a very interactive user interface for running Docker containers.</li></ol><h3>What Is Docker?</h3><p>Docker is a containerization platform that runs applications within containers called Docker containers. Docker containers are light weighted when compared to virtual machines. When you install a Virtual machine on your system, it uses the guest operating system on top of your host operating system. This obviously takes up a lot of resources like disk space, RAM, etc. On the other hand, Docker containers make use of the host operating system itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*8Aw3OJFT-zK1RAHAX26buA.png" /><figcaption><em>What is Docker — Docker for Windows</em></figcaption></figure><p>In the above image, you can see that, there’s a host operating system on top of which the Docker engine is mounted. The Docker engine runs container #1 and container #2. Both of these containers have different applications and each application has its own libraries and packages installed within the container.</p><p>Let’s discuss some Docker terminologies now:</p><p><strong>Docker Images</strong></p><p>Docker images are read-only templates to build Docker images. Docker images are created from a file called Dockerfile. Within the Dockerfile, you define all the dependencies and packages that are needed by your application.</p><p><strong>Docker Containers</strong></p><p>Every time you run a Docker image, it runs as a Docker container. Therefore, a Docker container is the run time instance of a Docker image.</p><p><strong>Docker’s Registry</strong></p><p>Docker’s registry, known as DockerHub is used to store Docker images. These images can be pulled from the remote server and can be run locally. DockerHub allows you to have Public/Private repositories.</p><p><strong>Docker Swarm</strong></p><p>Docker swarm is a technique to create and maintain a cluster of Docker engines. A cluster of Docker engines comprises of multiple Docker engines connected to each other, forming a network. This network of Docker engines is called a Docker swarm. A Docker manager initiates the whole swarm and the other Docker nodes have services running on them. The main goal of the Docker manager is to make sure that the applications or services are running effectively on these Docker nodes.</p><p><strong>Docker Compose</strong></p><p>Docker-compose is used to run multiple containers at once. Let’s say that you have 3 applications in 3 different containers and you want to execute them at once. This is where Docker compose comes in, you can run multiple applications in different containers at once, with a single command, which is docker-compose up.</p><h3>Hands-On</h3><p>We’ll begin our demo by installing Docker for windows. But before we do that, check if you’ve met the prerequisites.</p><p>One more thing to note is since Docker for Windows requires Microsoft’s Hyper-V and once it’s enabled, VirtualBox will no longer be able to run virtual machines. So you can’t run Docker for Windows and a VirtualBox on the same system, side by side.</p><ol><li>Download Docker for Windows installer from the official website</li><li>Double-click on the installer to run it</li><li>Go through the Install Wizard, accept the license and proceed with the install</li><li>After installation, open the Docker for Windows app and wait till the whale icon on the status bar becomes stable</li><li>Open up any terminal like Windows PowerShell and start running Docker</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*Fq-E0OS7EyUhCcoY4P5cnw.png" /></figure><p>Enough of theory, let’s get our hands dirty and create a simple Python web application by using Docker Compose. This application uses the Flask framework and maintains a hit counter on Redis.</p><p>Flask is a web development framework, written in Python and Redis is an in-memory storage component, used as a database. You don’t have to install Python or Redis, we’re simply going to use Docker images for Python and Redis.</p><p>In this demo we’re going to use Docker compose to run two services, namely:</p><ol><li>Web service</li><li>Redis service.</li></ol><p>What does the application do? It maintains a hit counter every time you access a web page. So each time you access the website the hit counter gets incremented. It’s simple logic, just increment the value of the hit counter when the web page is accessed.</p><p>For this demo, you’ll need to create four files:</p><ol><li>Python file</li><li>Requirements.txt</li><li>Dockerfile</li><li>Docker compose file</li></ol><p>Below is the Python file (webapp.py) that creates an application by using the Flask framework and it maintains a hit counter on Redis.</p><pre><strong>import</strong> time<br><strong>import</strong> redis<br><strong>from</strong> flask <strong>import</strong> Flask<br>app <strong>=</strong> Flask(__name__)<br>cache <strong>=</strong> redis.Redis(host<strong>=</strong>&#39;redis&#39;, port<strong>=</strong>6379)<br><strong>def</strong> get_hit_count():<br>retries <strong>=</strong> 5<br><strong>while</strong> True:<br><strong>try</strong>:<br><strong>return</strong> cache.incr(&#39;hits&#39;)<br><strong>except</strong> redis.exceptions.ConnectionError as exc:<br><strong>if</strong> retries <strong>==</strong> 0:<br><strong>raise</strong> exc<br>retries <strong>-=</strong> 1<br>time.sleep(0.5)<br>@app.route(&#39;/&#39;)<br><strong>def</strong> hello():<br>count <strong>=</strong> get_hit_count()<br><strong>return</strong> &#39;Hello World! I have been seen {} times.&#39;.format(count)<br><strong>if</strong> __name__ <strong>==</strong> &quot;__main__&quot;:<br>app.run(host<strong>=</strong>&quot;0.0.0.0&quot;, debug<strong>=</strong>True)</pre><p>The requirements.txt file has the name of the two dependencies, i.e. Flask and Redis that we’ll be installing in the Dockerfile.</p><pre>flask<br>redis</pre><p>The Dockerfile is used to create Docker images. Here, I’m installing python and the requirements mentioned in the requirements.txt file.</p><pre>FROM python:3.4-alpine ADD . /code WORKDIR /code RUN pip install -r requirements.txt CMD [&quot;python&quot;, &quot;webapp.py&quot;]</pre><p>The Docker compose file or the YAML file contains two services:</p><ol><li>Web service: Builds the Dockerfile in the current directory</li><li>Redis service: Pulls a Redis image from DockerHub</li></ol><pre>version: &#39;3&#39;<br>services:<br>web:<br>build: .<br>ports:<br><strong>-</strong> &quot;5000:5000&quot;<br>redis:<br>image: &quot;redis:alpine&quot;</pre><p>You can now run these two services or containers by using the following command:</p><pre>docker-compose up</pre><p>To view the output you can use Kitematic. To open Kitematic, right-click on the whale icon on the status bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/226/1*YyJKwzJC6VS7_5aUfBWXKg.png" /><figcaption><em>Kitematic — Docker for Windows</em></figcaption></figure><p>On the top left-hand corner, you can see the two services running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDXTOcU4pP2nvmymiRRMtw.png" /><figcaption><em>Kitematic — Docker for Windows</em></figcaption></figure><p>This is what the output looks like. When you refresh the page, the hit count gets incremented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQjiEZmqLQbAK-rLSoVDOg.png" /></figure><p>With this, we come to the end of this blog. I hope you have a better understanding of how Docker works on Windows. Stay tuned for more blogs on the most trending technologies. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=docker-for-windows">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/maven-tutorial-2e87a4669faf"><em>Maven For Building Java Applications</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/docker-architecture-be79628e076e"><em>Docker Architecture</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>41. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/docker-for-windows/"><em>https://www.edureka.co</em></a><em> on January 17, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed971362c1ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec">Learn How to Set Up Docker For Windows</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ansible Tower | Getting Started With Ansible Tower With A Hands-On | Edureka]]></title>
            <link>https://medium.com/edureka/ansible-tower-cb317ccd6779?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb317ccd6779</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[devops-tool]]></category>
            <category><![CDATA[installation]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 05:41:04 GMT</pubDate>
            <atom:updated>2020-09-29T13:04:50.871Z</atom:updated>
            <content:encoded><![CDATA[<h3>Exploring Ansible Tower With A Hands-On</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*OH7h9ziYmbzEdsTBtZ6KoQ.jpeg" /></figure><p>Today’s scaling industries aim to provide large productivity gains, but they have to deal with a wide variety of automation challenges, which are overcome by tools such as Ansible. This blog on Ansible Tower will give you a complete insight into the following:</p><ul><li>What is Ansible — Tower?</li><li>Prerequisites To Install Ansible — Tower</li><li>Ansible — Tower Parameters</li><li>Installation Steps</li><li>Hands-On</li></ul><p>Alright!! So, let’s get started with what is Ansible Tower.</p><h3>What is Ansible Tower?</h3><p>Ansible Tower is Ansible at a more enterprise level. It is a web-based solution for managing your organization with a very easy user interface that provides a dashboard with all of the state summaries of all the hosts, allows quick deployments, and monitors all configurations.</p><p>The tower allows you to share the SSH credentials without exposing them, logs all the jobs, manage inventories graphically and syncs them with a wide variety of cloud providers.</p><h3>Prerequisites To Install Ansible Tower</h3><p>Ansible Tower is supported by the following operating systems:</p><ul><li>Red Hat Enterprise Linux 6 64-bit</li><li>Red Hat Enterprise Linux 7 64-bit</li><li>CentOS 6 64-bit</li><li>CentOS 7 64-bit</li><li>Ubuntu 12.04 LTS 64-bit</li><li>Ubuntu 14.04 LTS 64-bit</li><li>Ubuntu 16.04 LTS 64 bit</li><li>You should have the latest stable release of Ansible.</li><li>64-bit support required (kernel and runtime) and 20 GB hard disk.</li><li>Minimum 2 GB RAM (4+ GB RAM recommended) is required.</li><li>2 GB RAM (minimum and recommended for Vagrant trial installations</li><li>4 GB RAM is recommended /100 forks</li></ul><p>For Amazon EC2: Instance size of m3.medium or larger is required for less than 100 hosts and if you have more than 100 hosts, then you require an instance size of m3.xlarge or larger.</p><p>For HA MongoDB setups, you can use the below formula for a rough estimate of the amount of space required.</p><p>(NumberOfHostsIninventory)*(NumberOfScans)*(AverageModuleFactSize)*(NumberOfModulesScanning)</p><h3>Ansible Tower Parameters</h3><p>In this section of the blog, you will get an insight into the following parameters of the tower:</p><ul><li>Tower Editions</li><li>Tower Pricing</li><li>Tower Features</li></ul><h3>Tower Editions</h3><p>The Ansible Tower has 3 different editions; the self-support, standard, and premium edition. Each of these editions varies with the capabilities they offer. You can do everything from application deployment to multi-tiered orchestrations, with control, security, and logging capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hz-LeNAY9lKTDX09LId-EQ.png" /></figure><h4>Tower Pricing</h4><p>As I mentioned before the tower has 3 editions, out of which the self-support one is the free trial version. For the other two edition’s pricing, you can refer to the below table:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F3tFMcVTmSJX6VNE.png" /></figure><h4>Tower Features</h4><p>Below are few of the Ansible Tower features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*plU4-87p7HHm6EGE1_ZW_A.png" /></figure><ul><li><strong>Multi-Playbook Workflows — </strong>This feature allows you to chain any number of playbooks, regardless of the usage of different inventories, utilizes various credentials, or runs different users.</li><li><strong>Scale Capacity With Clusters — </strong>We can connect multiple Ansible Tower nodes into an Ansible Tower cluster as the clusters add redundancy and capacity, which allow you to scale Ansible automation across the enterprise.</li><li><strong>Manage &amp; Track Inventory — </strong>Ansible Tower helps you manage your entire infrastructure by letting you easily pull inventory from public cloud providers such as Amazon Web Services, Microsoft Azure, and more.</li><li><strong>REST API &amp; Tower CLI Tool — </strong>Every feature present in Ansible Tower is available via Ansible Tower’s REST API, which provides the ideal API for a systems management infrastructure. The Ansible Tower’s CLI tool is available for launching jobs from CI systems such as Jenkins, or when you need to integrate with other command-line tools.</li><li><strong>Remote Command Execution — </strong>You can run simple tasks such as add users, restart any malfunctioning service, reset passwords on any host or group of hosts in the inventory with Ansible Tower’s remote command execution.</li></ul><p>Alright!! So, now that you guys have understood the features of Ansible Tower, let’s get into the installation of Ansible Tower.</p><h3>Installation of Ansible Tower</h3><p>Before you install Ansible Tower, you have to first install and configure Ansible on your operating system and then also install PostgreSQL.</p><p>So, first, let’s start by installing and configuring Ansible. I will be using Ubuntu — 16.04 version as my operating system.</p><h4>Install and Configure Ansible on Ubuntu</h4><p><strong>Step 1:</strong> As a root user, configure the Ansible PPA using the below commands.</p><pre>apt-get install software-properties-common<br>apt-add-repository ppa:ansible/ansible</pre><p><strong>Step 2:</strong> After configuring, install Ansible using the below commands.</p><pre>apt-get update<br>apt-get install ansible</pre><p>After you are done installing, install PostgreSQL.</p><h4>Installing PostgreSQL</h4><p>Use the below commands, to install PostgreSQL.</p><pre>apt-get update<br>sudo apt-get install postgresql postgresql-contrib</pre><h4>Download Ansible Tower</h4><p><strong>Step 1.1:</strong> Once you are done installing Ansible, register to download the Ansible — Tower.</p><p><strong>Step 1.2:</strong> You will receive an email after you register to download the Ansible Tower. Open your mail and then click on the download button, to download.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*1vrqymIfPCR0vzlBm4befw.png" /></figure><p><strong>Step 1.3:</strong> Then extract the Ansible Tower installation tool using the below commands.</p><pre>tar xvzf ansible-tower-setup-latest.tar.gz<br>ansible-tower-setup-&lt;tower_version&gt;</pre><p>where tower-version, is the version of the tower you have downloaded.</p><p><strong>Step 2</strong>: After that set up your inventory file, where you have to mention the necessary passwords (admin_password, pg_password, rabbitmq_password) in the inventory file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ju7lX8rkf3pUL7nhRi82dA.png" /></figure><p><strong>Step 3:</strong> Now, as the Tower setup playbook script uses the inventory file, it has to be invoked as <strong>./setup.sh</strong> from the path where you unpacked the Tower installer tarball.</p><pre>./setup.sh</pre><p><strong>Step 4: </strong>Once you are done setting up the Tower, use the web browser to access the Tower server and view the Tower login screen, wherein you have to enter the username and password, to access the Tower Dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*V1rA417Udj95S_aYVd01mA.png" /></figure><h3>Hands-On</h3><p>In this hands-on, I will show you how to create a job to print a message.</p><p>So, refer to the below diagram for the steps that we are going to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XximMCl1l7wz8hMn57ot5g.png" /></figure><h4>Create a User</h4><p>To create a user, go the<strong> settings</strong> option, and then choose the <strong>User</strong> tab. Once you enter the User tab, click on the <strong>Add</strong> option to add a new User. Mention the details required and then click on <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vJjxIWfxD-ZKgDl4.png" /></figure><h4>Create an Inventory</h4><p>Now, create an Inventory, by just clicking on the <strong>Inventories</strong> option and then going to the <strong>Add</strong> option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/0*WFeibOjxoC0lWLHq.png" /></figure><p>Once you click on the Add option, mention all the details required like the name, description, organization and then click on <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kSZHnCA7taoOcAYR.png" /></figure><h4>Create a Host</h4><p>To create a host, go the<strong> Inventories</strong> tab and choose the inventory to which you want to add hosts. Then choose the <strong>Hosts</strong> tab and click on <strong>Add</strong> Hosts. Here I want to add hosts for the inventory that was created above. Once the details are mentioned, click on <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-56eYCtbCrO4nS9N.png" /></figure><h4>Create a Credential</h4><p>After creating hosts, create a credential by going to the <strong>settings</strong> options, and then choose the <strong>Credentials</strong> tab. After that, go to the <strong>Add</strong> option and mention the details. Once you are done, mentioning the details, click on <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X5gPj3MHXunkTS3Q.png" /></figure><h4>Setting up a Project</h4><p>There are two ways to access a simple playbook, either you can do it manually or by specifying a link from a Github repository.</p><p>In this blog, I am going to access the project manually.</p><h4>Accessing a Manually created Playbook</h4><p>For accessing a manually created playbook, you first have to <strong>create a playbook</strong> and then <strong>set up the project</strong>.</p><p>So, follow the below steps and start creating a playbook.</p><p>Use command-line console as a root user and <strong>create a directory</strong> for your project on the Tower server file system, in which to store your Ansible playbooks for this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*F5AfEcSqtrsgePMb.png" /></figure><p>Now, make a new project directory by creating it on the Tower filesystem under the Project Base Path directory, located by default in <strong>“/var/lib/awx/projects/”</strong>. Here the new directory is DEMO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*p0eBOfAOx0xQUUzY.png" /></figure><p>Now, let’s start setting up a project.</p><p>To set up a project use your web browser, create the new project by clicking on the <strong>Projects</strong> link at the top of the Tower Dashboard and click on the <strong>Add</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/0*_HrztUe3-73yIXzB.png" /></figure><p>Once you click on the Add button, you will be redirected to a page wherein you have to fill in details such as Name and Description of Project. Then, set the SCM type to be Manual, and for the Playbook Directory, select a value that corresponds to the subdirectory you created and then click on <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*nQqSZ2SaTZ0Enkaa8N3TxQ.png" /></figure><p>So, guys, that’s an end to this blog!!</p><p>This is the end of my article on Nagios interview questions. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=ansible-tower">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/docker-architecture-be79628e076e"><em>Docker Architecture</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/ansible-tower/"><em>https://www.edureka.co</em></a><em> on September 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb317ccd6779" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/ansible-tower-cb317ccd6779">Ansible Tower | Getting Started With Ansible Tower With A Hands-On | Edureka</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Continuous Delivery? Continuous Delivery Pipeline Using Jenkins | Edureka]]></title>
            <link>https://medium.com/edureka/what-is-continuous-delivery-c-4ebb02e8a77?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ebb02e8a77</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[pipeline]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 04:22:17 GMT</pubDate>
            <atom:updated>2020-09-28T05:04:32.545Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building A Continuous Delivery Pipeline Using Jenkins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*hgqemwWhUFGJleTVi8tPXA.jpeg" /></figure><h3>Continuous Delivery:</h3><p>Continuous Delivery is a process, where code changes are automatically built, tested, and prepared for a release to production. Here, I will talk about the following topics:</p><ul><li>What is Continuous Delivery?</li><li>Types of Software Testing</li><li>Difference Between Continuous Integration, Delivery, and Deployment</li><li>What is the need for Continuous Delivery?</li><li>Hands-on Using Jenkins and Tomcat</li></ul><p>Let us quickly understand how Continuous Delivery works.</p><h3>What Is Continuous Delivery?</h3><p>It is a process where you build software in such a way that it can be released to production at any time. Consider the diagram below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k2WcqGk7VyF8dbNu.png" /></figure><p>Let me explain the above diagram:</p><ul><li>Automated build scripts will detect changes in Source Code Management (SCM) like Git.</li><li>Once the change is detected, source code would be deployed to a dedicated build server to make sure build is not failing and all test classes and integration tests are running fine.</li><li>Then, the build application is deployed on the test servers (pre-production servers) for User Acceptance Test (UAT).</li><li>Finally, the application is manually deployed on the production servers for release.</li></ul><p>Before I proceed, it will only be fair I explain to you the different types of testing.</p><h3>Types of Software Testing:</h3><p>Broadly speaking there are two types of testing:</p><ul><li><strong>Blackbox Testing:</strong> It is a testing technique that ignores the internal mechanism of the system and focuses on the output generated against any input and execution of the system. It is also called functional testing. It is basically used for validating the software.</li><li><strong>Whitebox Testing:</strong> is a testing technique that takes into account the internal mechanism of a system. It is also called structural testing and glass box testing. It is basically used for verifying the software.</li></ul><p>There are two types of testing, that fall under this category.</p><ul><li><strong>Unit Testing:</strong> It is the testing of an individual unit or group of related units. It is often done by the programmer to test that the unit he/she has implemented is producing expected output against given input.</li><li><strong>Integration Testing: </strong>It is a type of testing in which a group of components is combined to produce the output. Also, the interaction between software and hardware is tested if software and hardware components have any relation. It may fall under both white box testing and black-box testing.</li></ul><p>There are multiple tests that fall under this category. I will focus on a few, which are important for you to know, in order to understand this blog:</p><ul><li><strong>Functional/ Acceptance Testing:</strong> It ensures that the specified functionality required in the system requirements works. It is done to make sure that the delivered product meets the requirements and works as the customer expected</li><li><strong>System Testing:</strong> It ensures that by putting the software in different environments (e.g., Operating Systems) it still works.</li><li><strong>Stress Testing:</strong> It evaluates how the system behaves under unfavorable conditions.</li><li><strong>Beta Testing:</strong> It is done by end-users, a team outside development, or publicly releasing full pre-version of the product which is known as a beta version. The aim of beta testing is to cover unexpected errors.</li></ul><p>Now is the correct time for me to explain the difference between Continuous Integration, Delivery, and Deployment.</p><h3>Differences Between Continuous Integration, Delivery, And Deployment:</h3><p>Visual content reaches an individual’s brain in a faster and more understandable way than textual information. So I am going to start with a diagram which clearly explains the difference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1_jms1QdEQPlAO9YYBIxVQ.png" /></figure><p>In Continuous Integration, every code commit builds and tested, but, is not in a condition to be released. I mean the build application is not automatically deployed on the test servers in order to validate it using different types of Blackbox testing like — User Acceptance Testing (UAT).</p><p>In Continuous Delivery, the application is continuously deployed on the test servers for UAT. Or, you can say the application is ready to be released to production anytime. So, obviously Continuous Integration is necessary for Continuous Delivery.</p><p>Continuous Deployment is the next step past Continuous Delivery, where you are not just creating a deployable package, but you are actually deploying it in an automated fashion.</p><p>Let me summarize the differences using a table:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*_yhv3UDNd5Z_a3gA_xabKw.png" /></figure><p>In simple terms, Continuous Integration is a part of both Continuous Delivery and Continuous Deployment. And Continuous Deployment is like Continuous Delivery, except that releases happen automatically.</p><p>But the question is, whether Continuous Integration is enough.</p><h3>Why We Need Continuous Delivery?</h3><p>Let us understand this with an example.</p><p>Imagine there are 80 developers working on a large project. They are using Continuous Integration pipelines in order to facilitate automated builds. We know build includes Unit Testing as well. One day they decided to deploy the latest build that had passed the unit tests into a test environment.</p><p>This must be a lengthy but controlled approach to deployment that their environment specialists carried out. However, the system didn’t seem to work.</p><h3>What Might Be The Obvious Cause Of The Failure?</h3><p>Well, the first reason that most people will think is that there is some problem with the configuration. Like most of the people even they thought so. They spent a lot of time trying to find what was wrong with the configuration of the environment, but they couldn’t find the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18lKt6mWSwl281AAIXfm7A.png" /></figure><h4>One Perceptive Developer Took A Smart Approach:</h4><p>Then one of the senior Developers tried the application on his development machine. It didn’t work there either.</p><p>He stepped back through earlier and earlier versions until he found that the system had stopped working three weeks earlier. A tiny, obscure bug had prevented the system from starting correctly. Although, the project had good unit test coverage. Despite this, 80 developers, who usually only ran the tests rather than the application itself, did not see the problem for three weeks.</p><p>Without running Acceptance Tests in a production-like environment, they know nothing about whether the application meets the customer’s specifications, nor whether it can be deployed and survive in the real world. If they want timely feedback on these topics, they must extend the range of their continuous integration process.</p><p>Let me summarize the lessons learned by looking at the above problems:</p><ul><li>Unit Tests only test a developer’s perspective of the solution to a problem. They have only a limited ability to prove that the application does what it is supposed to from a user&#39;s perspective. They are not enough to identify the real functional problems.</li><li>Deploying the application on the test environment is a complex, manually intensive process that was quite prone to error. This meant that every attempt at deployment was a new experiment — a manual, error-prone process.</li></ul><p><strong>Solution — Continuous Delivery Pipeline (Automated Acceptance Test):</strong></p><p>They took Continuous Integration (Continuous Delivery) to the next step and introduced a couple of simple, automated Acceptance Tests that proved that the application ran and could perform its most fundamental function. The majority of the tests running during the Acceptance Test stage are Functional Acceptance Tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*b7uWo1oiCFp73i-ymUsaWQ.png" /></figure><p>Basically, they built a Continuous Delivery pipeline, to make sure that the application is seamlessly deployed on the production environment, by making sure that the application works fine when deployed on the test server which is a replica of the production server</p><h3>Continuous Delivery Pipeline Using Jenkins:</h3><p>Here I will be using Jenkins to create a Continuous Delivery Pipeline, which will include the following tasks:</p><h4>Steps involved in the Demo:</h4><ul><li>Fetching the code from GitHub</li><li>Compiling the source code</li><li>Unit testing and generating the JUnit test reports</li><li>Packaging the application into a WAR file and deploying it on the Tomcat server</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BtcZ4gW35rqeuY2J_FV5Zg.png" /></figure><p>Pre-requisites:</p><ul><li>CentOS 7 Machine</li><li>Jenkins 2.121.1</li><li>Docker</li><li>Tomcat 7</li></ul><h4>Step — 1 Compiling The Source Code:</h4><p>Let’s begin by first creating a Freestyle project in Jenkins. Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ds0w23_SnB4SDqgUKAIOGQ.png" /></figure><p>Give a name to your project and select Freestyle Project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H921s40s99cNCuAKVqshMw.png" /></figure><p>When you scroll down you will find an option to add source code repository, select git and add the repository URL, in that repository there is a pom.xml fine which we will use to build our project. Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wBl9O0xxe8nfMMCHQNElMw.png" /></figure><p>Now we will add a Build Trigger. Pick the poll SCM option, basically, we will configure Jenkins to poll the GitHub repository after every 5 minutes for changes in the code. Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVwmzexSSh4ZCi0DoezDDQ.png" /></figure><p>Before I proceed, let me give you a small introduction to the Maven Build Cycle.</p><p>Each of the build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.</p><p>Following is the list of build phases:</p><ul><li>validate — validate the project is correct and all necessary information is available</li><li>compile — compile the source code of the project</li><li>test — test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed</li><li>package — take the compiled code and package it in its distributable format, such as a JAR.</li><li>verify — run any checks on results of integration tests to ensure quality criteria are met</li><li>install — install the package into the local repository, for use as a dependency in other projects locally</li><li>deploy — done in the built environment, copies the final package to the remote repository for sharing with other developers and projects.</li></ul><p>I can run the below command, for compiling the source code, unit testing, and even packaging the application in a war file:</p><pre>mvn clean package</pre><p>You can also break down your build job into a number of build steps. This makes it easier to organize builds in clean, separate stages.</p><p>So we will begin by compiling the source code. In the build tab, click on invoke top-level maven targets and type the below command:</p><pre>compile</pre><p>Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kUhO709lHkjVstdtdnJZCA.png" /></figure><p>This will pull the source code from the GitHub repository and will also compile it (Maven Compile Phase).</p><p>Click on Save and run the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-BSJYEqOEzH2Dtss3JmYQ.png" /></figure><p>Now, click on the console output to see the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*g22x4MsnjMdde0PVxWyhKg.png" /></figure><p>Now we will create one more Freestyle Project for unit testing.</p><h4>Step — 2 Unit Testing:</h4><p>Add the same repository URL in the source code management tab, like we did in the previous job.</p><p>Now, in the “Buid Trigger” tab click on the “build after other projects are built”. There type the name of the previous project where we are compiling the source code, and you can select any of the below options:</p><ul><li>Trigger only if the build is stable</li><li>Trigger even if the build is unstable</li><li>Trigger even if the build fails</li></ul><p>I think the above options are pretty self-explanatory so, select anyone. Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OqDlJWzVXwDYKt24E8IUVQ.png" /></figure><pre>test</pre><p>Jenkins also does a great job of helping you display your test results and test result trends.</p><p>The de facto standard for test reporting in the Java world is an XML format used by JUnit. This format is also used by many other Java testing tools, such as TestNG, Spock, and Easyb. Jenkins understands this format, so if your build produces JUnit XML test results, Jenkins can generate nice graphical test reports and statistics on test results over time, and also let you view the details of any test failures. Jenkins also keeps track of how long your tests take to run, both globally, and per test-this can come in handy if you need to track down performance issues.</p><p>So the next thing we need to do is to get Jenkins to keep tabs on our unit tests.</p><p>Go to the Post-build Actions section and tick “Publish JUnit test result report” checkbox. When Maven runs unit tests in a project, it automatically generates the XML test reports in a directory called surefire-reports . So enter “**/target/surefire-reports/*.xml” in the “Test report XMLs” field. The two asterisks at the start of the path (“**”) are a best practice to make the configuration a bit more robust: they allow Jenkins to find the target directory no matter how we have configured Jenkins to check out the source code.</p><pre>**/target/surefire-reports/*.xml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSDLvpw-3fuxDpOO2klolg.png" /></figure><p>Again save it and click on Build Now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WhY-NThTaKdSLAnSEyEUg.png" /></figure><p>Now, the JUnit report is written to /var/lib/jenkins/workspace/test/gameoflife-core/target/surefire-reports/TEST-behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksPKOOuvr3BG_2vKJ6undw.png" /></figure><p>In the Jenkins dashboard you can also notice the test results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Axm8zRHTKfaGYZTs.png" /></figure><h4>Step — 3 Creating A WAR File And Deploying On The Tomcat Server:</h4><p>Now, the next step is to package our application in a WAR file and deploy that on the Tomcat server for the User Acceptance test.</p><p>Create one more freestyle project and add the source code repository URL.</p><p>Then in the build trigger tab, select build when other projects are built, consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lqYAwIfMqdwot_pH.png" /></figure><p>Basically, after the test job, the deployment phase will start automatically.</p><p>In the build tab, select shell script. Type the below command to package the application in a WAR file:</p><pre>mvn package</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UA7ECNEL-WuqqDEKSd4ZnQ.png" /></figure><p>Next step is to deploy this WAR file to the Tomcat server. In the “Post-Build Actions” tab select deploy war/ear to a container. Here, give the path to the war file and give the context path. Consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WuI8vNBFSfN-KfhpHHPiJQ.png" /></figure><p>Select the Tomcat credentials and, notice the above screenshot. Also, you need to give the URL of your Tomcat server.</p><p>In order to add credentials in Jenkins, click on credentials option on the Jenkins dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmpLy07a0nh7xPu1Ln3abQ.png" /></figure><p>Click on System and select global credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ez7oekTmGXyk28n5v2wk4Q.png" /></figure><p>Then you will find an option to add the credentials. Click on it and add credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DApwWl0s3qdbdX6OhFo8qg.png" /></figure><p>Add the Tomcat credentials, consider the below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OyoH1tZ-VAyAzbQKCcKW2Q.png" /></figure><p>Click on OK.</p><p>Now in your Project Configuration, add the tomcat credentials which you have inserted in the previous step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WuI8vNBFSfN-KfhpHHPiJQ.png" /></figure><p>Click on Save and then select Build Now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EsHrg1aqzZqKeNBZe94Oxg.png" /></figure><p>Go to your tomcat URL, with the context path, in my case it is <a href="http://localhost:8081.">http://localhost:8081.</a> Now add the context path in the end, consider the below Screenshot:</p><pre>Link - <a href="http://localhost:8081/gof">http://localhost:8081/gof</a></pre><p>I hope you have understood the meaning of the context path.</p><p>Now create a pipeline view, consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SexWqLcaZBe_GQc8HscnCA.png" /></figure><p>Click on the plus icon, to create a new view.</p><p>Configure the pipeline the way you want, consider the below screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vs2fiP__-ePDktkvOViAjg.png" /></figure><p>I did not change anything apart from selecting the initial job. So my pipeline will start from compile. Based on the way I have configured other jobs, after compile testing and deployment will happen.</p><p>Finally, you can test the pipeline by clicking on RUN. After every five minutes, if there is a change in the source code, the entire pipeline will be executed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIRlnUDGG-N57Te8uPn_fQ.png" /></figure><p>So we are able to continuously deploy our application on the test server for user acceptance test (UAT).</p><p>This is the end of my article on Nagios interview questions. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=continuous-delivery">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/docker-architecture-be79628e076e"><em>Docker Architecture</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/continuous-delivery/"><em>https://www.edureka.co</em></a><em> on August 6, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ebb02e8a77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/what-is-continuous-delivery-c-4ebb02e8a77">What is Continuous Delivery? Continuous Delivery Pipeline Using Jenkins | Edureka</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps vs Agile! Everything You Need To Know]]></title>
            <link>https://medium.com/edureka/devops-vs-agile-5bf708eb48ac?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bf708eb48ac</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops-engineer]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Tue, 20 Feb 2018 16:20:06 GMT</pubDate>
            <atom:updated>2020-10-19T11:50:54.016Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*AqfIvMGOy3E6saJ10HbMZQ.jpeg" /></figure><p>DevOps is a buzzword that has been trending in the industry for quite some time now. But in spite of its popularity, there is a lot of confusion pertaining to how different it is from Agile. What’s worse? The <strong><em>DevOps vs Agile</em></strong> is a never-ending debate in the IT industry.</p><p>If you want to understand how different they are, and which of them is better than the other, then stick around till the end of this ‘DevOps vs Agile’ blog where I will be uncovering a number of industry secrets. But, a synopsis of the differences between them is in the table below.</p><p>Are you an aspiring DevOps Engineer looking forward to learning all the DevOps tools? Well, if you are, then you should consider learning all the top tools. One such tool which must be on your list is Ansible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*Dq4ddxQj8BQShIBWP8mZbA.png" /></figure><h3><strong>DevOps vs Agile</strong></h3><p>Agile’s founding principle is bringing Agility to Development. But, DevOps’ founding principle is bringing Agility to both Development and Operations. Before I talk about the technical differences between DevOps vs Agile, I want to set the context straight. Hence, I will be talking about a few non-technical differences which you should be aware of.</p><p>The important point to note is that DevOps is not a replacement for Agile! Sounds wrong? No, Agile is not dying. But, is DevOps better? Yes, it is an improvement.</p><p>While Agile was a natural replacement for the Waterfall model and other Scrum practices, DevOps is not a replacement. But, it is a direct successor to Agile.</p><p>Similar to how with time, practices get better; over time, Agile has also grown its challenges, and DevOps has turned out to be the more optimized practice.</p><h3>Why Is DevOps Better Than Agile?</h3><p>Let’s understand this by first learning what were the challenges with Agile software development.</p><p>Agile software development is about following a set of best practices for creating quality software in a timely manner. But the problem is, the best practices followed, involves people working in <strong>Silos</strong>.</p><p>By Silos, I mean there are people who will be working as <em>Developers</em>, or as <em>Testers</em>, or as <em>ITOps</em> with very little communication between them. And since, there is very little communication between them, they are not aware of what the others are working on despite being a part of the same process.</p><p>This Silos-ed working of teams is the reason for the infamous “Blame Game” that goes about when the software fails or has major flaws.</p><h3>The Blame Game</h3><p>When a client has complained about software, the blame is internally thrown at each other. The ‘Dev’ team would point fingers at the ‘QA’ team. ‘QA’ team will then point fingers at the ‘ITOps’ team, who would redirect the blame to the ‘Dev’ team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H395GnuCN6Fyzwqc.png" /></figure><p>Irrespective of the problem residing in the code developed, or on the systems where the code is deployed, the problem remains in isolation, as nobody wants to take ownership of the screw-up.</p><h3>Solution To This Everlasting Problem?</h3><p><strong>DevOps</strong>! You could have guessed this. But, can you guess how DevOps overcomes the Silos?</p><p>Simple- DevOps breaks the Silos right through the middle. In DevOps, the ‘Dev’ team, the ‘ITOps’ team, and ‘QA’ team are not independently working pieces of the gamut. But, they are ‘one’.</p><p>DevOps practice uses a <em>DevOps Engineer</em> — who does everything:- developing the code, testing that code, and deploying the very same code to production. So, does the unification solve the problem?</p><p>Yes, it solves one major aspect of the problem. Since the same DevOps Engineer is multi-skilled, he will be given ownership of the entire process: developing the code, unit testing/ functional testing the code, and deploying that code to staging/ testing/ production server.</p><p>Since he is the sole owner, there are very few problems that will arise. And even if problems do arise, the person who knows the product best will be on the job.</p><p>Speaking of the best person, another issue that DevOps solves is the dependency problem. So, even if the ‘ITOps’ guy is not available, there won’t be any delay. Because as DevOps Engineers, the role of ‘ITOps’ can be easily assumed by anybody else.</p><h3>Is DevOps Performed By Only DevOps Engineers?</h3><p>Well, that’s the catch. It always seems like DevOps Engineers are the only folks involved. But, in the real world, DevOps Engineers are restricted to only performing a specified role even though they are capable of being involved throughout the entire lifecycle.</p><h3>Technical Differences Between DevOps vs Agile</h3><p>Agile development involves a set of practices such as <em>Agile Scrum</em> &amp; <em>Agile Kanban</em>.</p><p>DevOps involves a set of technical processes such as Continuous Development, Continuous Integration (CI), Continuous Testing (CI), Continuous Deployment (CD), and Continuous Monitoring.</p><h4>Key Focus Area?</h4><p>Agile development focuses mainly on releasing quality software in a timely manner.</p><p>DevOps goes one step further. It focuses on guaranteeing quality software in a timely manner. Quality is guaranteed by <em>Continuously Monitoring</em> the software application after its deployment.</p><h4>Release Cycles/ Development Sprints</h4><p>Agile focuses on smaller release cycles with incremental software delivery.</p><p>DevOps focuses on smaller release cycles with incremental delivery &amp; immediate feedback.</p><h4>Who Gives Feedback?</h4><p>In Agile, feedback is mostly given by customers.</p><p>In DevOps, feedback is mostly measured by the internal team (by using Continuous Monitoring tools).</p><h4>Scope Of Work</h4><p>Agile mainly focuses on working with Speed or Agility.</p><p>DevOps mainly focuses on achieving automation by orchestrating various DevOp tools.</p><p>Now that brings an end to this DevOps vs Agile blog. Stay tuned to Edureka for more interesting blogs on DevOps. For a better understanding of the differences between DevOps and Agile, you can refer to the below video.</p><p>This is the end of my article on Nagios interview questions. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, Python, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=devops-vs-agile">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of DevOps.</p><blockquote><em>1. </em><a href="https://medium.com/edureka/devops-tutorial-89363dac9d3f"><em>DevOps Tutorial</em></a></blockquote><blockquote><em>2. </em><a href="https://medium.com/edureka/git-tutorial-da652b566ece"><em>Git Tutorial</em></a></blockquote><blockquote><em>3. </em><a href="https://medium.com/edureka/jenkins-tutorial-68110a2b4bb3"><em>Jenkins Tutorial</em></a></blockquote><blockquote><em>4.</em><a href="https://medium.com/edureka/docker-tutorial-9a6a6140d917"><em> Docker Tutorial</em></a></blockquote><blockquote><em>5. </em><a href="https://medium.com/edureka/ansible-tutorial-9a6794a49b23"><em>Ansible Tutorial</em></a></blockquote><blockquote><em>6.</em><a href="https://medium.com/edureka/puppet-tutorial-848861e45cc2"><em> Puppet Tutorial</em></a></blockquote><blockquote><em>7. </em><a href="https://medium.com/edureka/chef-tutorial-8205607f4564"><em>Chef Tutorial</em></a></blockquote><blockquote><em>8. </em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>9. </em><a href="https://medium.com/edureka/devops-tools-56e7d68994af"><em>How To Orchestrate DevOps Tools?</em></a></blockquote><blockquote><em>10. </em><a href="https://medium.com/edureka/continuous-delivery-5ca2358aedd8"><em>Continuous Delivery</em></a></blockquote><blockquote><em>11. </em><a href="https://medium.com/edureka/continuous-integration-615325cfeeac"><em>Continuous Integration</em></a></blockquote><blockquote><em>12. </em><a href="https://medium.com/edureka/continuous-deployment-b03df3e3c44c"><em>Continuous Deployment</em></a></blockquote><blockquote><em>13. </em><a href="https://medium.com/edureka/continuous-delivery-vs-continuous-deployment-5375642865a"><em>Continuous Delivery vs Continuous Deployment</em></a></blockquote><blockquote><em>14. </em><a href="https://medium.com/edureka/ci-cd-pipeline-5508227b19ca"><em>CI CD Pipeline</em></a></blockquote><blockquote><em>15. </em><a href="https://medium.com/edureka/docker-compose-containerizing-mean-stack-application-e4516a3c8c89"><em>Docker Compose</em></a></blockquote><blockquote><em>16. </em><a href="https://medium.com/edureka/docker-swarm-cluster-of-docker-engines-for-high-availability-40d9662a8df1"><em>Docker Swarm</em></a></blockquote><blockquote><em>17. </em><a href="https://medium.com/edureka/docker-networking-1a7d65e89013"><em>Docker Networking</em></a></blockquote><blockquote><em>18.</em><a href="https://medium.com/edureka/ansible-vault-secure-secrets-f5c322779c77"><em> Ansible Vault</em></a></blockquote><blockquote><em>19. </em><a href="https://medium.com/edureka/ansible-roles-78d48578aca1"><em>Ansible Roles</em></a></blockquote><blockquote><em>20. </em><a href="https://medium.com/edureka/ansible-for-aws-provision-ec2-instance-9308b49daed9"><em>Ansible for AWS</em></a></blockquote><blockquote><em>21. </em><a href="https://medium.com/edureka/jenkins-pipeline-tutorial-continuous-delivery-75a86936bc92"><em>Jenkins Pipeline</em></a></blockquote><blockquote><em>22. </em><a href="https://medium.com/edureka/docker-commands-29f7551498a8"><em>Top Docker Commands</em></a></blockquote><blockquote><em>23. </em><a href="https://medium.com/edureka/git-vs-github-67c511d09d3e"><em>Git vs GitHub</em></a></blockquote><blockquote><em>24. </em><a href="https://medium.com/edureka/git-commands-with-example-7c5a555d14c"><em>Top Git Commands</em></a></blockquote><blockquote><em>25. </em><a href="https://medium.com/edureka/devops-interview-questions-e91a4e6ecbf3"><em>DevOps Interview Questions</em></a></blockquote><blockquote><em>26. </em><a href="https://medium.com/edureka/devops-engineer-role-481567822e06"><em>Who Is A DevOps Engineer?</em></a></blockquote><blockquote><em>27. </em><a href="https://medium.com/edureka/devops-lifecycle-8412a213a654"><em>DevOps Life cycle</em></a></blockquote><blockquote><em>28. </em><a href="https://medium.com/edureka/git-reflog-dc05158c1217"><em>Git Reflog</em></a></blockquote><blockquote><em>29. </em><a href="https://medium.com/edureka/ansible-provisioning-setting-up-lamp-stack-d8549b38dc59"><em>Ansible Provisioning</em></a></blockquote><blockquote><em>30. </em><a href="https://medium.com/edureka/devops-skills-f6a7614ac1c7"><em>Top DevOps Skills That Organizations Are Looking For</em></a></blockquote><blockquote><em>30.</em><a href="https://medium.com/edureka/waterfall-vs-agile-991b14509fe8"><em>Waterfall vs Agile</em></a></blockquote><blockquote><em>31. </em><a href="https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3"><em>Jenkins CheatSheet</em></a></blockquote><blockquote><em>32. </em><a href="https://medium.com/edureka/ansible-cheat-sheet-guide-5fe615ad65c0"><em>Ansible Cheat Sheet</em></a></blockquote><blockquote><em>33. </em><a href="https://medium.com/edureka/ansible-interview-questions-adf8750be54"><em>Ansible Interview Questions And Answers</em></a></blockquote><blockquote><em>34. </em><a href="https://medium.com/edureka/docker-interview-questions-da0010bedb75"><em>50 Docker Interview Questions</em></a></blockquote><blockquote><em>35. </em><a href="https://medium.com/edureka/what-is-agile-methodology-fe8ad9f0da2f"><em>Agile Methodology</em></a></blockquote><blockquote><em>36. </em><a href="https://medium.com/edureka/jenkins-interview-questions-7bb54bc8c679"><em>Jenkins Interview Questions</em></a></blockquote><blockquote><em>37. </em><a href="https://medium.com/edureka/git-interview-questions-32fb0f618565"><em>Git Interview Questions</em></a></blockquote><blockquote><em>38. </em><a href="https://medium.com/edureka/docker-architecture-be79628e076e"><em>Docker Architecture</em></a></blockquote><blockquote><em>39. </em><a href="https://medium.com/edureka/linux-commands-in-devops-73b5a2bcd007"><em>Linux commands Used In DevOps</em></a></blockquote><blockquote><em>40. </em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Jenkins vs Bamboo</em></a></blockquote><blockquote><em>41.</em><a href="https://medium.com/edureka/nagios-tutorial-e63e2a744cc8"><em>Nagios Tutorial</em></a></blockquote><blockquote><em>42.</em><a href="https://medium.com/edureka/nagios-interview-questions-f3719926cc67"><em> Nagios Interview Questions</em></a></blockquote><blockquote><em>43.</em><a href="https://medium.com/edureka/jenkins-x-d87c0271af57"><em>DevOps Real-Time Scenarios</em></a></blockquote><blockquote><em>44.</em><a href="https://medium.com/edureka/jenkins-vs-bamboo-782c6b775cd5"><em>Difference between Jenkins and Jenkins X</em></a></blockquote><blockquote><em>45.</em><a href="https://medium.com/edureka/docker-for-windows-ed971362c1ec"><em>Docker for Windows</em></a></blockquote><blockquote><em>46.</em><a href="http://git%20vs%20github/"><em>Git vs Github</em></a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/devops-vs-agile-everything-you-need-to-know/"><em>https://www.edureka.co</em></a><em> on February 20, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bf708eb48ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/devops-vs-agile-5bf708eb48ac">DevOps vs Agile! Everything You Need To Know</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beginner’s Guide To ServiceNow Scripting]]></title>
            <link>https://medium.com/edureka/servicenow-developer-training-3861b03cc7c0?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/3861b03cc7c0</guid>
            <category><![CDATA[servicenow-training]]></category>
            <category><![CDATA[servicenow-scripting]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[scripting]]></category>
            <category><![CDATA[servicenow-developer]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 13:48:21 GMT</pubDate>
            <atom:updated>2019-06-05T15:10:19.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*NaUrm8WfjXWJGZDxAMzIOQ.jpeg" /><figcaption>ServiceNow Developer Training — Edureka</figcaption></figure><p>ServiceNow is one of the most popular ITSM tools that bring in automation in various business processes. In this article, I am going to discuss ServiceNow from a developer’s perspective. So let us not waste any time and get started with this article.</p><p>This article will walk you through the following points:</p><ol><li>What Is ServiceNow</li><li>Introduction To Scripting</li><li>Demo</li></ol><p>So let us start with the first topic of discussion in this article.</p><h3>What Is ServiceNow?</h3><p>ServiceNow is a software platform that supports IT service management and automates common business processes. It contains a number of modular applications that can vary by instance and user. <a href="https://www.edureka.co/blog/what-is-servicenow/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=servicenow-developer-training">ServiceNow</a> is an integrated<strong> cloud</strong> solution which combines major cloud and business services into a single system of record.</p><p>ServiceNow whose journey began with IT Service Management applications providing Service Catalog Management, today supports both IT Service Management Processes and IT Enterprise such as HR Management, Security Management, and PPM, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*S3h0O0Uy_-pEJq5KQWpeyw.png" /></figure><p>Following features make ServiceNow better than its competitors:</p><ul><li>Instance-based implementation</li><li>Ease of customization</li><li>Better Support and low maintenance cost</li><li>Real-time analysis and reporting</li></ul><p>This was a short introduction to ServiceNow. Next, in this article we would understand what is scripting in ServiceNow:</p><h3>Introduction To Scripting</h3><p>A <strong>script</strong> is nothing but a computer programming language with a series of commands that are capable of being executed without being compiled. In simple words, scripting is configuring your system to perform certain tasks which are triggered by specific events.</p><p>You can classify scripting in two types: <strong>Server-Side Scripting</strong> and <strong>Client-Side Scripting</strong></p><h4>Server Side Scripting</h4><p>It is a script that runs on a web server, which produces a response customized for each user’s request to the website. Server-side scripts execute on the <strong>server</strong> or the <strong>database</strong></p><p>Server-side scripting is often used to provide a customized interface for the user. These scripts may assemble client characteristics for use in customizing the response, based on those characteristics, the user’s requirements, access rights, etc. Server-side scripting also enables the website owner to hide the source code that generates the interface.</p><h4>Client Side Scripting</h4><p>Client scripts run on the client (web browser). You can use client scripts to define custom behaviors that run when events occur, such as, when a form is loaded or submitted, or cell value changes. Proper client-side processing depends on the form loading completely first. Making record updates prior to form load can produce unexpected results that bypass client-side processing. Client-side Glide APIs (Application Programming Interfaces) provides classes and methods that you can use in scripts to perform client-side tasks.</p><p>Users with basic knowledge of JavaScript can define scripts to run in the client browser. Several types of client scripts are supported by ServiceNow. Let us take a look at those:</p><ul><li>onLoad()</li><li>onChange()</li><li>onSubmit()</li><li>onCellEdit()</li></ul><p><strong>onLoad()</strong></p><p>An onLoad() script runs when the form loads before the user ever sees it. The values on the form are straight from the database. This type of script lets you control how the form first appears to the user.</p><p><strong>onChange()</strong></p><p>An onChange script runs when the user changes a value in any of the fields. This script is handy for setting up a value of a field or displaying value based on the values user enters in the other fields.</p><p><strong>onSubmit()</strong></p><p>An onSubmit script runs when the user submits the form. This type of script is useful for validating the values the user entered.</p><p><strong>onCellEdit()</strong></p><p>An onCellEdit() script is very similar to onChange() script. However, there is one major difference between the two. onCellEdit() script runs when the user changes the value of the fields in the list.</p><h3>Demo</h3><p>In this demo, we start by creating a GitHub account.</p><h4>Creating a Github account:</h4><p><strong>Step 1:</strong> Go to the following<em> </em><a href="https://github.com/"><em>link</em></a> to create and a Github account. Following page will appear. <strong>SignIn,</strong> if you already have an account else follow the steps to <strong>SignUp</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KBzgKuhg6iZ-ldYYnoGpTQ.png" /></figure><p><strong>Step 2:</strong> Fill in the above-mentioned details and click on <strong>Sign Up. </strong>Following window will appear, fill in the details required in fields shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3HI7hs5ekv9vMhAaXcHiA.png" /></figure><p><strong>Step 3:</strong> GitHub will request you following details, fill in those as well and click on continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YzAEoajP9ZoO2cdMUInfVw.png" /></figure><p><strong>Step 4:</strong> Once you have done this, a formal information page would appear, fill in that information and you are good to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghzYDuYR823ylsOtZYEcHw.png" /></figure><p><strong>Step 5:</strong> Once you do this, your account is created. Next, <strong>verify</strong> your account by clicking on the <strong>link</strong> that GitHub will send to your registered e-mail ID.</p><h4>Forking needit repository in ServiceNow</h4><p><strong>Step 1:</strong> Next open your browser and Enter this ‘<em>https://github.com/ServiceNow/devtraining-needit-jakarta</em>‘ link. The link will redirect you to the following page. Now let us <strong>fork</strong> the ‘devtraining — needit — jakarta’ repository with our ServiceNow instance by clicking on <strong>fork.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcCaG4WgJxiM3foOyEaC6A.png" /></figure><p><strong>Step 2:</strong> After you have forked the repository. <strong>GitHub</strong> will give you an option to clone the repository. Click on the <strong>clone</strong> tab, <strong>Github</strong> will generate following link for you,<strong> copy</strong> the link. You may download the zip file or directly open it on the desktop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsRbwY7kPJD16GemuxpkMw.png" /></figure><p>We have successfully <strong>forked</strong> the <strong>GitHub</strong> repository. Now Let us go ahead and create a client script using our repository.</p><h4>Creating A Client Scrip</h4><p><strong>Step 1:</strong> Go to <strong>Application Navigato</strong>r in your ServiceNow Instance. Type <strong>Studio</strong> and <strong>open</strong> it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S_G6GUkpS7y9WeJiConIMg.png" /></figure><p><strong>Step 2:</strong> Following tab will open. Click on <strong>Import Source Control </strong>to import the repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrxmLMRqYX2c5lgeIQDbEw.png" /></figure><p><strong>Step 3:</strong> Following window will appear. Enter the link we copied while cloning the repository, also enter the GitHub credentials, we used to create the account. Click on <strong>import.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*NtaxZoVVwxU7MoaIX_tGvw.png" /></figure><p><strong>Step 4:</strong> Following page will appear. Click on the <strong>NeedIT</strong> repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*PDCWm5hTSQ4cPn7EkOt05A.png" /></figure><p><strong>Step 5:</strong> In <strong>Studio</strong>, open the <strong>Source Control</strong> menu and click the <strong>Create Branch</strong> option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yoe-8Q7m8fgI0v9aKzn7aw.png" /></figure><p><strong>Step 6:</strong> Configure the Branch with following credentials:</p><p>Branch Name: <strong>ClientScriptsModule. </strong>Create from Tag: <strong>LoadForClientScriptsModule.</strong></p><p>Click the <strong>Create Branch</strong> button. Click the <strong>Close Dialog</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*BBW1D6Qc0rzdu1tHGxG2Ww.png" /></figure><p><strong>Step 7:</strong> Click the <strong>Create Application File</strong> button. Choose the new file type, in this case, <strong>Client Script. </strong>Configure the new file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*hWA7NxzCi1Q6xvVWkDLyZQ.png" /></figure><p><strong>Step 8:</strong> Go to <strong>studio</strong>, click on <strong>client scripts</strong> and finally on <strong>NeedITonChangeExample. </strong>Fill in the details and scroll down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcJ_IwhTcjqxsI6TPyHTsg.png" /></figure><p><strong>Step 9:</strong> Following script will help you implement changes that are made to the form. Click on <strong>submit</strong> or <strong>update.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWlc6ZNjzpuG3eSIQXMc6Q.png" /></figure><p><strong>Step10:</strong> Similarly update records<strong> NeedIT onChange Example</strong> and <strong>NeedIT onSubmit Example</strong></p><p>First, let us do it for <strong>NeedIT onLoad Example.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZMBhdS4CBTQG1SbafNvrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9IJ6LFC50bk3P7UbK38Ww.png" /></figure><p>Finally, we update the <strong>NeedIT onSubmit Example</strong> client script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YwmPF4SF0K-PMOXPHXnx1g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eT46jmR6IlWw6EpRxIn_iQ.png" /></figure><p>We have successfully updated our three sample Client scripts. Now is the time to test them.</p><h4>Testing The Client Scripts</h4><p><strong>Step 1:</strong> In the main ServiceNow browser window (not Studio) use the Application Navigator to open <strong>NeedIt &gt; All</strong>. Select a record of your choice and open it. If your client script is active. It will display an alert as shown in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHyVgxE8KXac2CgVuy0dLg.png" /></figure><p><strong>Step 2:</strong> Press OK. Now make a change to the record. Change the priority to <strong>moderate</strong> and click on<strong> update. </strong>The <strong>onSubmit</strong> alert would pop out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJdyf1gnn6aUSYIopZ7wPQ.png" /></figure><p><strong>Step3:</strong> Finally Let us test the <strong>onChange</strong> client script. To do that, make a change to the <strong>short description</strong> and update it. The alert would pop out as shown in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTfhsD_AdYWGP4eDcXwlVA.png" /></figure><p>This verifies that all are client scripts are working and thus we have successfully created client scripts and implemented them accordingly. This brings us to the end of this article.</p><p>If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, DevOps, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=servicenow-developer-training">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of ServiceNow.</p><blockquote>1. <a href="https://medium.com/edureka/what-is-servicenow-60546b93bf27">What is ServiceNow?</a></blockquote><blockquote>2.<a href="https://medium.com/edureka/servicenow-tutorial-55a3ce369e01"> ServiceNow Tutorial</a></blockquote><blockquote>3. <a href="https://medium.com/edureka/servicenow-itsm-tools-61ef084d3f09">ServiceNow ITSM Tools</a></blockquote><blockquote>4. <a href="https://medium.com/edureka/servicenow-developer-instance-5cb073e4949c">How To Get A ServiceNow Developer Instance?</a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/servicenow-developer-training/"><em>www.edureka.co</em></a><em> on January 11, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3861b03cc7c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/servicenow-developer-training-3861b03cc7c0">A Beginner’s Guide To ServiceNow Scripting</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Get A ServiceNow Developer Instance?]]></title>
            <link>https://medium.com/edureka/servicenow-developer-instance-5cb073e4949c?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cb073e4949c</guid>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[servicenow-instance]]></category>
            <category><![CDATA[servicenow-training]]></category>
            <category><![CDATA[servicenow-developer]]></category>
            <category><![CDATA[servicenow-users-list]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 06:25:32 GMT</pubDate>
            <atom:updated>2019-06-05T15:17:25.482Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*TkgHkpU2HagVYFNYlcKE8Q.jpeg" /><figcaption>ServiceNow Developer Instance — Edureka</figcaption></figure><p>ServiceNow is the most popular <strong>ITSM</strong> tool in the market which automates the various business processes. One of the reasons ServiceNow is so popular is the ease with which you can use ServiceNow and this can be done using ServiceNow Developer Instance. This article specifically talks about ServiceNow Developer Instance.</p><h3>What is a ServiceNow Developer Instance?</h3><p>ServiceNow developer instance can be considered as a <strong>sandbox</strong> for the developers to extend the knowledge and experiment with ServiceNow platform to create valuable assets.</p><p>ServiceNow Developer Instance lets you learn, explore and experiment with the platform. It also lets you test ServiceNow Applications without hampering customer or non-production instance.</p><h4>Step 1: — SignUp</h4><p>Open the Link <a href="https://developer.servicenow.com/app.do#!/home">https://developer.servicenow.com/app.do#!/home </a>for Signing Up and Click on Register</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*vuwk9NknXPDsFNLxDVDr-g.png" /></figure><h4>Step 2: — Registration form</h4><p>Complete the Registration Form with your name, username, and password</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*IbP51b76NvPYO9_X0XgZww.png" /></figure><h4>Step 3: — Account Validation</h4><p>Validate your account by clicking the link you received on your registered email id. After clicking on the link shown in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EL6jLOU9tPdpYQJo3ixUAQ.png" /></figure><h4>Step 4: — Login to your ServiceNow Developer Platform</h4><p>Following SignIn window will appear. You can also open the <a href="https://developer.servicenow.com/app.do#!/home"><strong>link</strong></a> and click on “<strong>Sign In</strong>” for Signing In. Enter the Login credentials you filled in the registration form</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mIC3A0Z7dBi6IjmoNuPXgw.png" /></figure><p>Check the “Click here to accept the ServiceNow Developer Agreement” checkbox and click on Submit. Fill the form and Click on <strong>Submit.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*2v2LYhd3y9rko9KEsxIGbA.png" /></figure><p>After completing the form below screen will be displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*JB7ngLo7wiuffblncKw0Cw.png" /></figure><h4><strong>Step 5: — Further you have to Request/Create Instance</strong></h4><p>Now click on <strong>Manage –&gt;Instance –&gt;</strong> Click on “<strong>Request Instance</strong>” and fill the “<strong>Please Note</strong>” form and click on “<strong>I understand</strong>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNG7uHJR5ypqf__39I_rAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*pmTUXJP-rIaCvWkxkXZt7w.png" /></figure><h4>Step 6: — Select the Version of ServiceNow Developer Instance</h4><p>Select the <strong>version</strong> you want to work on. The latest version is <strong>Kingston</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*P8imT4yWAsRNgULUmBEI_w.png" /></figure><h4>Step 7: — Instance Credentials Info</h4><p><strong>URL</strong> and the login <strong>credentials</strong> will be provided for your Instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQof7nXoaEiUCx0738A-YA.png" /></figure><h4>Step 8: — Login into your ServiceNow Developer instance</h4><p>Open the <strong>URL </strong>and login with the given credentials and you will be on the ServiceNow platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3jMLRpQ5Es4G3IlgdfQfsw.png" /></figure><h3>Instance Activity</h3><p>If you want your ServiceNow developer instance to be active, the following points should be noted: –</p><ul><li>If the instance remains <strong>inactive</strong> for <strong>10 days</strong>, the instance is <strong>released</strong></li><li>Released instances and their data <strong>cannot</strong> be recovered</li><li>You must use it regularly to keep the instance active</li></ul><p>In case your instance remains inactive for more than 24hrs, your instance may go into a state of hibernation. To wake the instance, navigate to <strong>Manage</strong> –&gt; <strong>Instance</strong> on the <a href="https://developer.servicenow.com/">ServiceNow developer site</a>. After few minutes your developer instance will be awake.</p><p>Note: — All the work/data is <strong>saved</strong> on the hibernating instances.</p><p><strong><em>So, this was about how to create ServiceNow instance and few things to keep in mind.</em></strong></p><p><strong><em>Let us look at the most sought-after questions concerning ServiceNow Instance.</em></strong></p><p><strong>Q1. How many ServiceNow developer instance can a registered account have?</strong></p><p>ServiceNow allows only <strong>one</strong> instance per registered developer account.</p><p><strong>Q2. How can I reset my ServiceNow Developer Instance password?</strong></p><p><strong>Step 1: </strong>— Go to My Instance Page and select <strong>Action</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*UhtssK43vLfuPFyzXJDaCg.png" /></figure><p><strong>Step 2: — </strong>Select <strong>Reset admin password</strong> under <strong>Action</strong> option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*LhhtwWEAhL1bAymnu9qygA.png" /></figure><p><strong>Step 3: — </strong>Click on <strong>Yes</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*p62Ab2d04MtMWFPbXyR-3w.png" /></figure><p><strong>Step 4: — </strong>After confirming, the developer site resets the admin password and provides you with a temporary password in <strong>green</strong> text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*TKVhUaIG3rV2ij8hF-QOUw.png" /></figure><p><strong>Step 5: — </strong>Click on <strong>URL</strong> text in the <strong>green</strong> box or type the URL in the browser. You will be prompted to your personal developer instance to set a new password. Use the temporary password for the current password and provide a new password.</p><p><strong>Q3. Once I upgrade the ServiceNow Developer Instance, can I revert/return to the previous release?</strong></p><p>ServiceNow doesn’t have any option to revert/return to the previous release. I can request a new instance of my choice of version and have to wait up to 15 min after the release of my instance to request a new instance.</p><p><strong>Q4. What can I do to transfer/save my data/work which is present on my ServiceNow Developer Instance?</strong></p><p>I can export my work as an <strong>update</strong> <strong>set</strong> which is in the form of <strong>XML</strong> file that can be saved to my local machine. The update set can be uploaded to another instance. For example: can export my application as an update set to another instance.</p><p><strong>Q5. Is there any option to reset my instance to initial state?</strong></p><p>Yes, Go to <a href="https://developer.servicenow.com/app.do#!/instance"><strong>My Instance</strong></a> page. Under <strong>Action</strong> Option Select the “<strong>Reset and wipe instance</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*gcau3rlQ_cXG-cfmyTbYeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/241/1*az5gLOxEx_XCLsdjerAV-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*ti25WHbwk379O5egxQnDeg.png" /></figure><p><strong>Note:</strong> — <em>After reset, all the customizations and configurations will be lost.</em></p><p><strong>Q6. What are the various versions available for ServiceNow Developer Instance?</strong></p><p>(A) Aspen 2011</p><p>(B) Berlin 2012</p><p>© Calgary 2013</p><p>(D) Dublin 2014</p><p>(E) Eureka 2014</p><p>(F) Fuji 2015</p><p>(G) Geneva 2015</p><p>(H) Helsinki 2016</p><p>(I) Istanbul 2016</p><p>(J) Jakarta 2017</p><p>(K) Kingston 2017 <strong>(Current)</strong></p><p>All the names of the versions are based on <strong>City</strong> name.</p><p>This brings us to the end of ServiceNow Developer Instance article. Hope this was informative and helpful to you. If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, DevOps, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=servicenow-developer-instance">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of ServiceNow.</p><blockquote>1. <a href="https://medium.com/edureka/what-is-servicenow-60546b93bf27">What is ServiceNow?</a></blockquote><blockquote>2. <a href="https://medium.com/edureka/servicenow-tutorial-55a3ce369e01">ServiceNow Tutorial</a></blockquote><blockquote>3. <a href="https://medium.com/edureka/servicenow-tutorial-55a3ce369e01">ServiceNow ITSM Tools</a></blockquote><blockquote>4. <a href="https://medium.com/edureka/servicenow-developer-training-3861b03cc7c0">ServiceNow Sripting</a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/servicenow-developer-instance/"><em>www.edureka.co</em></a><em> on January 11, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cb073e4949c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/servicenow-developer-instance-5cb073e4949c">How To Get A ServiceNow Developer Instance?</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ServiceNow ITSM Tools — ServiceNow IT Services Demo]]></title>
            <link>https://medium.com/edureka/servicenow-itsm-tools-61ef084d3f09?source=rss-4a674e17ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/61ef084d3f09</guid>
            <category><![CDATA[servicenow-tool]]></category>
            <category><![CDATA[servicenow-training]]></category>
            <category><![CDATA[servicenow-itsm-tools]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[servicenow-it-services]]></category>
            <dc:creator><![CDATA[Vardhan NS]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 14:17:07 GMT</pubDate>
            <atom:updated>2019-06-05T15:17:59.127Z</atom:updated>
            <content:encoded><![CDATA[<h3>ServiceNow ITSM Tools - ServiceNow IT Services Demo</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Wi0di8MvEhB4yM6KURQUDQ.jpeg" /><figcaption>ServiceNow ITSM Tools — Edureka</figcaption></figure><p>Do you find it increasingly challenging to handle all your service requests? Still stuck with manual processing? What if I told you ServiceNow provides a single system of record on the cloud to solve all your internal bottlenecks. If you are not familiar with ServiceNow please feel free to read my earlier article. Coming to today’s article, we would be focusing on ServiceNow ITSM tools by exploring the Information Technology Service Management (ITSM) domain in-depth. We will look into the theoretical concepts in ITSM as well as see how this is implemented on the ServiceNow Platform.</p><p>Let’s have an overview of the topics to be covered in this ServiceNow ITSM Tools article.</p><ul><li>Incident Management</li><li>Problem Management</li><li>Change Management</li><li>Knowledge Management</li><li>ServiceNow Tools Demo</li></ul><p>In this ServiceNow ITSM tools article, we will be looking at each of the ITSM services individually. Let us begin with Incident Management.</p><h3>Incident Management</h3><p>First, let us take look at what is an Incident in ServiceNow. When a user faces an issue and wants to get in touch with the support team, the first thing needed is to record the details in a user form. To put it in simple words, an Incident is any issue reported by a user or group of users which is documented with a unique record ID.</p><p>To get more clarity on an Incident, let us look at the steps involved in Incident Management:</p><h4>Step 1: Classification</h4><p>The issue can be related to either hardware, software, network or any possible combinations of them.</p><p><strong>Examples:</strong></p><ol><li>The laptop has stopped working. This may be due to an underlying hardware or software issue.</li><li>The Wi-Fi has performance issues. This may be caused due to a network problem or software issue.</li></ol><h4>Step 2: Priorities</h4><p>The Incident reported is handled according to its priority level. Priority is a combination of an Incident’s <strong>impact</strong> on the organization as well as its <strong>urgency</strong> level.</p><p>Incidents are classified as P1, P2, P3, P4 according to their respective priority levels:</p><ul><li>P1-<strong>Critical</strong></li><li>P2-<strong>high</strong></li><li>P3-<strong>Moderate</strong></li><li>P4-<strong>Low</strong></li><li>P5-<strong>Planning</strong></li></ul><p><strong>Example:</strong></p><p>An Incident which has a high impact at the organization level with an urgent timeline is considered as a P1 level or Critical level Incident, whereas an Incident with low impact at the user level with a normal timeline is classified as a P5 level or Planning level Incident.</p><p>Apart from solving Incidents, it is also important to avoid related incidents and reduce overall incident volume. This can only be done when the underlying problem is identified. This brings us to our next topic Problem Management.</p><h3>Problem Management</h3><p>Problem Management deals with identifying the root cause of the Incident. We Analyse how to mitigate or reduce Incidents. Suppose there are many Incidents pertaining to Email. We can perform Root Cause Analysis to identify the root cause.</p><h4>Step 1: Identify and log the Problem</h4><p>IT personnel can manually create a record to make a note of the ‘Problem’, Or we can relate to an Incident record.</p><h4>Step 2: Update &amp; investigate the Problem</h4><p>Updates can be communicated using E-mail. We choose the inbound E-mail configuration to achieve this.</p><p><strong>Service Level Agreements (SLA):</strong> are used to assign priority to tasks as well as monitor team progress.</p><p><strong>Inactivity tracker</strong>: We can create events which are triggered when the Problem is not attended within a certain interval of time. This event may be a script or email notification.</p><h4>Step 3: Resolve the Problem</h4><p>Once the Problem is resolved, related Incidents to the Problem will automatically be closed. If we cannot find a solution to the given Problem, we can term it as a Known Error which saves us time in the future.</p><p>For those not familiar with CI’s, a Configuration Item (CI) is the fundamental asset in a (Configuration Management Database) CMDB.</p><p>Example: Workstation, Server or Business Service</p><p>The biggest difference between a static assets list and CMDB is that we map <strong>relationships </strong>between CIs. This brings us to our next topic <strong>Dependency Views</strong>. Dependency Views depict the relationships between different Configuration Items. The following diagram is an example of Dependency Views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*wNv98ikWqsa4irbgKztp8g.png" /></figure><p>Now we can see the relationships between the Email Exchange Server and various Email Servers. Also, the San Storage Device can be checked.</p><p>Next, we create Problem Tasks to identify the affected area. We can designate two teams one each for network and server domains. As the Incident is critical, before the particular server is fixed we need a temporary solution such as an alternative server. To permanently solve the issue, it might require a software patch from the server team to fix the Email server.</p><p>Once the Problem is identified, we need to fix the issues causing the Problem. This brings us to our next topic which is Change Management.</p><h3>Change Management</h3><p>Change Management is the lifecycle of proposed Changes and the reflected Changes. Once Incidents are reported, we create a Problem and perform Root Cause Analysis. We further create Change Requests based on the given situation. Change tasks are then planned and post-completion their associated incidents and Problems are closed/resolved.</p><p>Changes Requests can be classified into Standard or Emergency. Standard Changes need written approval and have a set procedure in place whereas a verbal communication is sufficient for Emergency Changes.</p><p>Workflows are used to depict the stages involved in the Change Request lifecycle right from Initiation to Approval. This is depicted in the diagram below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CMnCvTZFnkh__N_iX2D9ng.png" /></figure><p>It is highly beneficial to have a repository of files covering previous support queries and articles relevant to the Platform. This leads up to our next topic Knowledge Management. Moving further with this article let take a look at Knowledge Management.</p><h3>Knowledge Management</h3><p>ServiceNow comes with a Knowledge Base which houses articles, Faq’s, troubleshooting. This is a plethora of information spanning several categories. Who can add an article to the knowledge base? The owner or manager is enabled to add Knowledge articles along with contributors who are entitled to add information to the knowledge base. The admin is also allowed to contribute to the Knowledge Base.</p><p>In our article, let us now understand the Knowledge article lifecycle in the ServiceNow Platform.</p><h3>Publishing Articles</h3><p>When an author publishes his article two distinct scenarios are possible:</p><p>If the <strong>Approval Publish Workflow</strong> is configured then the article enters the <strong>Draft </strong>state which is forwarded to the Reviewer who can either approve or reject the article.</p><p>If the <strong>Instant Publish Workflow</strong> is configured then the article is immediately published and appears in the Knowledge Base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7ppBmPDzbfs2bJQ1CcxLQ.png" /></figure><h3>Retirement of Articles</h3><p>The article can be removed from the Knowledge Base if it is no longer useful. This process is known as retirement.</p><p>If the <strong>Approval Retire Workflow</strong> is implemented then the article moves to the pending retirement state and the owner of the Knowledge Base needs to approve its retirement.</p><p>If the <strong>Instant Retire Workflow</strong> is implemented then the article skips the review and directly moves to retired phase. Once the article has retired it does not appear in the Knowledge Base. However, the article still resides within the system and can be restored to the Draft state when needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXK0g39xc8OWGofZs-hYFQ.png" /></figure><p>Now that you are familiar with the ITSM concepts, let us move ahead and explore the different ITSM tools provided by ServiceNow.</p><h3>ServiceNow ITSM Tools Demo</h3><p>We will now have an in-depth view of ServiceNow ITSM tools. I will be walking you through the entire lifecycle starting from creating an Incident, then performing Root Cause Analysis to avoid such Incidents in the future. We will also look at the process of Change Requests, needed to solve the Problem and Resolve the Incident. I will also show you how to export the problem as an article to the Knowledge Base.</p><h4>Step1: Create an Incident</h4><p>Follow the instructions below in order to create an Incident in the ServiceNow Platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bEpsw66fZXOGtuMwOAg3AA.png" /></figure><p>We create an Incident record to report the issue <strong>Email service</strong> is not working. The record contains the Task Assignee, Impact on the organization, affected Business services and Configuration items, Urgency as well as a Description of the issue. The below diagram depicts the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-1Y9Tex7g1uz5U76i5rnWA.png" /></figure><h4>Step 2: Create a Problem</h4><p>To perform Root Cause Analysis, we create a Problem by clicking on the Incident properties tab as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIt6tom2e5LZa0Fw3tYWfw.png" /></figure><p>After having a look at the dependency view, we can go ahead and create Problem tasks and assign it to a specific group or user.</p><p>In our example, the Problem identified after Root Cause Analysis found a compromised network adapter so we assign Problem Tasks to the network group and assign Fred Luddy as the associated user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIt6tom2e5LZa0Fw3tYWfw.png" /></figure><h4>Step 3: Change Requests</h4><p>Once the Problem is identified the task assignees take a call whether a Change Request is needed to Resolve the Problem. The Problem state is Changed to Pending once a Change Request is initiated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yIHsQhN1F24x0L86mMwdEA.png" /></figure><p>In our example, the assignee Fred Luddy takes care of the Change Request to replace the identified network adapter.</p><h4>Step 4: Closing Problems and Incidents</h4><p>Once the Change Request is Completed/Closed all associated Problems are automatically Resolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvb1ab9xoVuAMfYXwGMoDQ.png" /></figure><p>All the related Incidents are Closed automatically after one day. We may also close them manually by setting the <strong>State</strong> parameter to Closed/Resolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uARYdMJ2A9T-edGrm_Cq0g.png" /></figure><h4>Step 5: Importing a Problem to the Knowledge Base</h4><p>We can directly extract information from the filled form of the Problem record. This can be added as an article to the Knowledge Base to provide support to users who might encounter the same issue in the future.</p><p>To implement this, we open the associated Problem record and hover to the <strong>Post Knowledge</strong> option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ew7y0M8Pv7XyjJACVQ074Q.png" /></figure><p>In the below diagram, we can see that the Knowledge article has been added and the associated Problem is also listed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFt27lnzoHQsZfIaJBjKHw.png" /></figure><p>It is currently in the Draft State and will be published to the knowledge Base post-approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tkk9LtMn0YENg9erz2iffQ.png" /></figure><p>With this we come to an end of this article. I am confident you get the idea of how ServiceNow ITSM tools come with a sense of consumerism touch. This is often found prevalent in social media applications, however, was due for a long time in the <strong>ITSM</strong> sector. ServiceNow aims to replicate that ease of use we experience in our day-day tasks to internal support tasks within the organization.</p><p>If you wish to check out more articles on the market’s most trending technologies like Artificial Intelligence, DevOps, Ethical Hacking, then you can refer to <a href="https://www.edureka.co/blog/?utm_source=medium&amp;utm_medium=content-link&amp;utm_campaign=servicenow-itsm-tools">Edureka’s official site.</a></p><p>Do look out for other articles in this series which will explain the various other aspects of ServiceNow.</p><blockquote>1. <a href="https://medium.com/edureka/what-is-servicenow-60546b93bf27">What is ServiceNow?</a></blockquote><blockquote>2. <a href="https://medium.com/edureka/servicenow-tutorial-55a3ce369e01">ServiceNow Tutorial</a></blockquote><blockquote>3. <a href="https://medium.com/edureka/servicenow-developer-training-3861b03cc7c0">ServiceNow Scripting</a></blockquote><blockquote>4. <a href="https://medium.com/edureka/servicenow-developer-instance-5cb073e4949c">How To Get A ServiceNow Developer Instance?</a></blockquote><p><em>Originally published at </em><a href="https://www.edureka.co/blog/servicenow-itsm-tools/"><em>www.edureka.co</em></a><em> on November 21, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61ef084d3f09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edureka/servicenow-itsm-tools-61ef084d3f09">ServiceNow ITSM Tools — ServiceNow IT Services Demo</a> was originally published in <a href="https://medium.com/edureka">Edureka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>