DevOps Tutorial
DevOps Tutorial
Bundle
You will learn how DevOps help the software development life cycle
You will learn how to manage the infrastructure using automation tools and code.
You will learn the Devops best practices which include Continuous Development,
Continuous Testing, Configuration Management, Continuous Integration, Continuous
Deployment and Continuous Monitoring.
Requirements
Description
What is this course about:
We will Cover:
Docker
Jenkins
GIT
Maven
What will you learn from this lecture:
**************************************************
FAQ 1:
Packaging:-
DevOps is awesome if you love to explore and play with variety of Technology and
processes. In my opinion the first thing to consider is the Packaging of IT that the tech teams
used to provide the organisations services. The maleable the packaging the easier it is to keep
everything standardized and reusable. If you are are comfortable working with configuration
management systems and developing some imaging systems such as docker you will like
DevOps. Closer look to the recent trends tells us the amount of new technologies that are
being released into the market is growing exponentially. In DevOps no technology is beyond
limits and you find yourself constantly working with integrated and automating different
Technologies. In DevOps your goal is to create machines as machine manageable data
objects that are completely completely hands off on the production. The goal is to to allow
programs written by different teams to efficiently automate as much as possible.
Scaling:-
You will definitely like DevOps if reusability is your passion. In my opinion the biggest
factor in the successful tech organisations of the future will be their ability to scale rapidly
while being able to deflate when not needed to minimise costs in downtime.
If the Application is reliable ,zippy and meet their needs, customers don’t care about the tech
behind it. They simply want speed.
Scalability is a hard thing to achieve and most would rather not have to worry about it, which
is self explanatory about the growth scalability as a service offering.
Now, Ask yourself. Do you want to jump from mobile to AI? DevOps will allow you. Do you
want to play with that new SaaS service that is in trend these days? DevOps will let you do
that.
DevOps is all about being the glue that holds everything and everyone together, and if you
ask me, that is what makes it so exciting. The possibilities are beyond limits and the
technologies are always growing and evolving at an unexplanatory and unimaginable speed.
And if you don’t focus on DevOps, you will still somehow have to manage infrastructure as a
developer.
As per me, this answer should start by explaining the general market trend. Instead of
releasing big sets of features, companies see if small features can be transported to their
customers via a series of release trains. This is very much advantageous like quick feedback
from customers, better software quality, etc. which in turn takes the company to high
customer satisfaction. To achieve this, companies are required to:
Q. What is Git?
I will suggest that you attempt this question by first explaining about the architecture of Git.
Git is a form of Distributed Version Control system (DVCS). It lets you track changes to a
file and allows you to revert to any specific change.
Its distributed architecture makes it more advantageous over other Version Control Systems
(VCS) like SVN. Another major advantage of Git is that it does not rely on a central server to
store all the versions of a project’s files. Instead of that, every developer gets “clones” the
copy of a repository. “Local repository” has the full history of the project on its hard drive so
that when there is a problem like a server outage, you need your teammate’s local Git
repository for recovery.
There is a central cloud repository as well where developers can commit changes and share it
with other teammates where all collaborators are committing changes “Remote repository”
Q. In Git how do you revert a commit that has already been pushed and made public?
There are two possible answers to the above question so make sure that you include both
because any of the below options can be used depending on the situation’s demand:
Remove the bad file in a new commit and push the file to the remote repository. This is the
most common and natural way to fix a bug or an error. Once you have included necessary
changes to the file, commit it to the remote repository. For that purpose I will use the
command
git commit -m “commit message”
Now, Create a new commit that will undo all the changes that were made in the bad Commit.
To do so I will be using the command
git revert <name of bad commit>
Agile is a set of values and principles about how to develop a software. For an instance: if
you have some idea about something and you want to turn that idea into a working software
the Agile values and principles can be used as a way to do that. But, that software might only
be working on a developer’s laptop or within a test environment. You need a way to easily,
quickly and repeatably move that software into production infrastructure, in a simple and safe
way. To do that DevOps tools and techniques are required.
In a nutshell, Agile software development methodology keeps its focus on the development
of software but, on the other hand, DevOps is responsible for development as well as the
deployment of the software in the safest and reliable possible way.
Now remember, keep this thing in mind, you have included DevOps tools in the previous
answer so be prepared to answer some questions related to that. They might be thrown at you.
Created by Up Degree
Last updated 10/2018
English
English [Auto-generated]
Size: 1.35 GB
Download Now
https://www.udemy.com/devops-docker-complete-guide-hands-on-with-practical/.