DevOps_Essentials_Course.pdf

Use DevOps designed a unique program to help Job seekers and IT professionals to get into DevOps roles.

DevOps Essentials Course :

DevOps Introduction - History - Necessity - Benefits.

Scripting - Linux and Python.

Version Control- Git.

Build Management Tool- Maven.

Continuous Integration- Jenkins.

Configuration Management - Chef/Puppet/Ansible(Any one of your choice).

Monitoring- Nagios.

Elasticsearch-Kibana.

Continuous Integration/Continuous Deployment - Docker.

Container Management Tool - Kubernetes.

Cloud Essentials - AWS.

If you can learn the above concepts and related to tools. You can easily grab DevOps Opportunities in the Market.

for more Info https://goo.gl/gf7Chk

Transcript

2.  Why I should know/learn DevOps  What is new in DevOps or DevOps itself is new?  Is it a tool or an approach of working or combination of only tools?  Is it really required or just a myth of companies to create extra pressure?  Is it necessary to learn this or work with this? Is it easy to learn or not? Can I get a good package after learning this? Etc.  Can I learn it easily?  Did DevOps helped any companies?  Is it really changing anything or changed that we know but did not notice?
3.  Will see all the details one by one
4.  Some terms we hear regularly during our work in software market  Software Development Life Cycle(SDLC)  Deployment  Development  Server(Linux/Unix/Windows etc.)  Error in production  Client is giving very less down time(cant work like this)  Coding , Building , Release  Success at development side , failure at production site  Blame keeps on going….
5.  Software Development Life Cycle (SDLC)  We know it already… (will see which phase we are working or searching job )
6.  We all fall into some part of SDLC.  What we hear or say or do in our offices or planning to do.  Project requirement planning (Investigation or Feasibility Study and analysis)  Task assignment (Design)  Development (Coding with the language as decided during planning phase)  VCS/SCM tools (Saving our changes to some remote central server)  Build , Release (Create a runnable package out of code – Development only)  Test (Test the functionality – Testing )  Deployment (Installing our code to run in production server -Implementation)  Maintenance (After deployment see for error and more requirement change)
7.  Waterfall Model  V-Shaped Model  Evolutionary Prototyping Model  Spiral Method (SDM)  Iterative and Incremental Method  Agile development
8.  Process of working is mostly synchronous.  Each process will wait for other process to complete if it’s a waterfall approach. Then next phase will start.  Time consuming and cost ineffective process.  Cleary showing -- lot of waiting time for all the people involved in project  Now we are thinking agile solved this. Because few year back all said same thing  Still there are gap between SDLC phases.  We as Developer/tester will say, no gap is there. Because agile broke gap between Dev and QA team.  But operation (implementation/maintenance) are not in that relational chain  That’s where companies faced measure business setback from their rivals who broke that gap with operation team.  The gap was continuously delivering quality and stable features frequently.
9.  Development/Testing (Combined phase as collaborated by Agile)  After Development and testing, the code deployment time is huge.  Pressure of work on old, pending and new code was high because deployment time was high.  Operations (Always a separate entity in SDLC)  It is difficult to maintain ~100% uptime of the production environment.  Infrastructure Automation tools are not very affective.  Number of severs to be monitored keeps on increasing with time and hence the complexity.  It is very difficult to provide feedback and diagnose issue in the product.
10.  Off Course yes..  DevOps is a way of working which collaborated all phases of SDLC in a common platform where every process started working in asynchronous continuous fashion.  Some tools helped to make this work.  As per theoretical definition  DevOps is a practice of operations and development engineers participating together in the entire software lifecycle, from design through the development process to production support.
11.  We used some tools but they were not giving us that flavor of flexibility because of the SDLC approach we followed.
15.  Common thoughts  I am happy with my coding/testing/scripting what ever I am doing?  Some different team should do DevOps or whatever for me.  I will only stick to my expertize area.  I will enhance only that skill.  That is future.  DevOps is just a myth.  DevOps anyway is not affecting what I am doing or what I will be doing
16.  As we have seen we are part of SDLC, So knowing DevOps model is coming to our bucket.  Companies are not going to hire new people for this work. (Cost involved). Why to hire when existing employees can learn and do.  If I am not doing then someone else will do. My job and career will be on dilemma.  Future of Software development will no more be a separated process of coding/testing/operating.  All will be merged and term will be Devops engineer.  What you are doing, you will do that. But yes need to know all will be managed in continuous fashion.
17.  I guess we are clear till now whether it is new or its some older way, nothing new in it.  Anyway It’s definitely a new way of working which broke the barrier of ways of working between all the teams involved in a SDLC.  We achieved DevOps by help of some tools at each stages of SDLC.  Some tools we have already used. Some are new.  We will see how tools helped in this DevOps approach.
18.  Blue color is part SDLC phases before implementation and maintenance .  Orange color is part of operations.
23.  Do I need to know all?  No  From each SDLC phase we will learn only one tool that is mostly used every where.  If you are not finding same tool in your company, not to worry.  That will be mostly same what we will learn in our course.  We will give overview of most of the tools used in DevOps.
24.  I am happy what I am doing. Tools won’t help me.  You are thing it’s difficult to learn. We are here to help you.
25.  Yes  Most of the companies are already into DevOps. No worry for job change and good package  Who are those companies mostly?  Facebook  Amazon  Netflix  Walmart  Nordstrom  Adobe  Etc.  Now you can tell are they all backward or forwarded companies? We know how much they are paying too.
26.  You may laugh. But it’s true  Pokémon Go (Best example of DevOps implementation)  Tools helped Pokémon Go are
28.  Will it be easy for me to learn all this?  Yes, our course is designed so simple that you will enjoy each days learning.  We will teach you in details of DevOps approaches at each phase of SDLC.  We will teach you most popular tools from each phase of DevOps which will help you to crack any DevOps interview and work better.  How can I practice what I am learning?  Will show you the local system setup. You can practice same. If any doubt, we will clarify that.  Is there any help for interview preparation?  Yes, We will provide you questions/answers for DevOps.  We will have mock test by end of our DevOps essential course.  Will help you to create resume with DevOps technologies.  Will help you to build your LinkedIn job profile..
29.  DevOps Introduction - History - Necessity - Benefits.  Scripting - Linux and Python.  Version Control- Git.  Build Management Tool- Maven.  Continuous Integration- Jenkins.  Configuration Management – Puppet/Ansible  Monitoring- Nagios.  Elasticsearch-Kibana.  Continuous Integration/Deployment - Docker.  Container Management Tool - Kubernetes.  Cloud Essentials – AWS.