<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Debug School: Sainath L</title>
    <description>The latest articles on Debug School by Sainath L (@lssainath).</description>
    <link>https://www.debug.school/lssainath</link>
    <image>
      <url>https://www.debug.school/images/TbhAMgyIGc7n9A9-NTP_uXwp8d-CabksTSYXniPjBdU/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzEwOC85ODc2/MzJiZi03NjM4LTRh/MDItYjZlNy05OWEy/YTIyZTY4OWYucG5n</url>
      <title>Debug School: Sainath L</title>
      <link>https://www.debug.school/lssainath</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/lssainath"/>
    <language>en</language>
    <item>
      <title>DevOps vs DevSecOps vs SRE - a guide</title>
      <dc:creator>Sainath L</dc:creator>
      <pubDate>Fri, 23 Sep 2022 19:11:14 +0000</pubDate>
      <link>https://www.debug.school/lssainath/devops-vs-devsecops-vs-sre-a-guide-3kk2</link>
      <guid>https://www.debug.school/lssainath/devops-vs-devsecops-vs-sre-a-guide-3kk2</guid>
      <description>&lt;h2&gt;
  
  
  DEVOPS
&lt;/h2&gt;

&lt;p&gt;DevOps is the amalgamation of various cultural philosophies, tools and practices that increases the organization's ability to deliver high quality software at a rapid pace. &lt;br&gt;
Under the DevOps model, there are no longer siloed teams doing only a subsection of tasks. Rather, all team members actively participate in all aspects of software development from development and test to deployment to operations, and develop a range of skills not limited to a single function. &lt;/p&gt;

&lt;h2&gt;
  
  
  SRE
&lt;/h2&gt;

&lt;p&gt;While adopting DevOps philosophy is ideal for any software development team, the cost of adoption is quite high. &lt;br&gt;
This is especially true for larger organizations with complex hierarchies. &lt;br&gt;
This is where SRE comes into picture. The Ops team is transformed into SRE (Site Reliability Engineering) team who closely work with the development team towards shared objectives. Once the two teams align well, the organization could move towards DevOps culture. SRE acts as a stepping stone towards final objective of DevOps transformation. &lt;/p&gt;

&lt;h2&gt;
  
  
  DEVSECOPS
&lt;/h2&gt;

&lt;p&gt;Infusing security at every phase of DevOps is DevSecOps. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>What is EPEL? What are the instructions to install and use it?</title>
      <dc:creator>Sainath L</dc:creator>
      <pubDate>Thu, 22 Sep 2022 18:44:00 +0000</pubDate>
      <link>https://www.debug.school/lssainath/what-is-epel-what-are-the-instructions-to-install-and-use-it-1ni</link>
      <guid>https://www.debug.school/lssainath/what-is-epel-what-are-the-instructions-to-install-and-use-it-1ni</guid>
      <description>&lt;p&gt;RedHat company releases 2 versions of OS - Fedora a general purpose OS and Red Hat Enterprise Linux or RHEL for enterprise users. RHEL is a light weight OS that only has a subset of features that are available in Fedora.&lt;br&gt;&lt;br&gt;
So to make it convenient to add packages a special interest group called Extra Packages for Enterprise Linux (EPEL) was created one that provides a set of additional packages for RHEL from Fedora sources.&lt;/p&gt;
&lt;h2&gt;
  
  
  Steps to install EPEL:
&lt;/h2&gt;

&lt;p&gt;Connect to server remotely via SSH or open terminal if in server&lt;br&gt;
1) Install EPEL&lt;br&gt;
2) Refresh repolist&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;yum install epel-release
yum repolist
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once package is installed we can use yum to install specific packages in EPEL&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;yum install PkgfromEPEL
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>epel</category>
    </item>
  </channel>
</rss>
