What is DevOps? – In Simple English


Meet Dave. Dave works for a company whose
success is contingent on its ability to offer new and exciting products to its online customers
faster than competitors. Dave is a developer, who writes code for new products, new features,
security updates and bug fixes. Unfortunately, he needs to wait weeks for his work to be
placed into production. This delay increases the pressure of staying
competitive, because some competitors are able to deploy new products and features much
faster. In addition, the delay makes it very challenging
for Dave to manage both the code that is pending to be pushed into production and the development
of the next product and/or feature that he is responsible for producing. When DaveÕs code is finally deployed into
the production environment, occasionally unforeseen errors or problems occur. This mostly happens
because Dave is focused on writing code for his Development Environment and itÕs not
identical to the Production Environment. Meet DaveÕs coworker Anna! SheÕs a System
Administrator from the Operations team. She is responsible for maintaining and assuring
the uptime of the Production Environment. The number of servers that she needs to administer
is constantly growing because her company continues to launch new products and customers
are consuming more of their services. This increase of servers has caused some challenges
for Anna. The tools that she used to administer a few servers are not as effective when used
to administer a much larger volume of servers. This challenge affects how new code is deployed
in her production environment. Usually when new code is released it takes a little massaging
to fit into her environment. This is why she requires code deployments to be scheduled
and are only allowed once a month. Once the new code is actually deployed, itÕs
her responsibility to diagnoses any errors or problems caused by the changes. Sometimes
to her it feels as though the Developers have tossed their work over the wall to her and
her team. So, What can be done to help Dave and Anna
work better? Ultimately, they want the same thing,,,, happy customers! What if Dave the Developer and Anna from Operations
* Worked better together? * Thought more alike?
* Broke down silos? * Shared responsibilities? This would require them to change their mindset
on how DEV and Ops work? So, what is DevOps?
Devops integrates developers and operations teams in order to improve collaboration and
productivity, by automating infrastructure, automating workflows and continuously measuring
application performance. If AnnaÕs and DaveÕs teams were more DevOps
oriented, they would do a few things differently. They would place more focus on automation.
DevOps teams try to automate everything: from testing of new code to how infrastructure
is provisioned. They would write software in small chunks
that are integrated, tested, monitored and deployed usually in hours, versus the traditional
way of writing large chunks of software over weeks or months to then do weeks or months
of testing. Plus they will have identical development and production environments based
on same configurations. Writing small chunks of software will allow
them to increase the frequency of the deployments and improve the time to deploy new code. It also enables them to adopt an iterative
process to monitor, measure and improve the code and operations every day. Improve their
ability to respond to market needs, or other things that impact software. Instead of building and configuring software
plus infrastructure manually on an ad-hoc basis, AnnaÕs and DaveÕs teams would write
Configuration Management Code that describes how things should be built. As a result: they
will have the ability to build infrastructure at scale to dozens, hundreds or even thousands
of servers), in multiple locations, using different types of hardware. Another change that a DevOps oriented team
would do, is to use a source control system to help manage and document all of the changes
to both the Application Code and Configuration Management Code. The change that Anna and Dave would implement
is to adopt a discipline of application performance monitoring and optimization in almost real-time.
This will allow Dave and the rest of his developers to understand the performance impact of their
changes. The ultimate goal is to have a Production Environment that gives their customers a great
experience. So what benefits does having a DevOps oriented
team give AnnaÕs and DaveÕs company? Well, it allows them to increase the rate of Software
Delivery and improves the companyÕs ÒTime to MarketÓ potentially from Months and Weeks
to Days and Hours. This will be a huge competitive advantage. It also allows them to maintain
better Business Focus by automating their infrastructure so they can focus things that
improve the business and their online content. They will spend more time of the things that
add more value to their organizations When a company is able to build and offer
better products, this means they have happier customers, and happier developers. How does a DevOps oriented team actually accomplish
this? Well as mentioned before, a culture change is needed, or changes in the mindsets
of the two groups that need to work closer together. The other component to the formula
is getting the right tools. New tools are needed in this new fast pace world. They will need a tool that allows them to
test their code and programs. An example of this is Jenkins. They will need a tool for Source Control such
as GiTHub. This will allow them to manage and document all the changes to their Application
Code and their Configuration Management Code. They will need tools for Configuration Management,
such as Chef, puppet and Saltstack. These tools will allow them to deploy applications
in an automated fashion, maybe across hundred or thousands of servers in different locations. They will also need new tools that allow them
to continuously measure the performance of their environment. Generating, reading and
analyzing system logs is extremely helpful to monitor an environment; but now that many
environments have hundreds or thousands of servers, new tools like new relic are required
to make sense on all the data. This will allow them to know how the entire
application is performing and identify bottlenecks. But many companies donÕt know how to use
these new tools or do not have the skills to automate software delivery process. This
is where Rackspace DevOps Automation Service can help. In Conclusion, DevOps is a new philosophy
that can help software organizations innovate faster and be more responsive to business
needs. It promotes collaboration between developers and operations, which improves quality or
software deployments, and more frequent software releases. Adopting the DevOps philosophy requires
a new mindset, new tools and new skills. Rackspace can help. Learn more at www.rackspace.com/DevOps

Comments 28

  • "New philosophy"? Its actually a incremental step on what was once a very bad thing "AdHoc changes".
    Put all the cool names you want on it!

  • Tutorial is good and simple but it can be more efficient and Detailed like this course from Tetranoodle – Link Below
    https://www.youtube.com/watch?v=HnenKFTFR4s&t=1236s

  • very interesting video.

  • Ffs the music you have used is so annoying when listening with good speakers, there is this constant "tuck" sound that even affected my cat.

  • WOw, that background sound is the most annoying ever. That knocking is so very distracting.

  • Any one can help me to know the "what is the qualification and experience required to do this course"

  • Got the opportunity to work inside rackspace data center in Tx our company built one of the new rooms.

  • Too fast… Slow down please

  • "What can be done to help Dave and Anna work better together? After all they all want the same thing: Happy Customers???" WRONG!! They both want to keep their jobs so Anna being at a big disadvantage, will do anything to sabotage Dave.

  • Dave and Anna might be having an affair

  • best tutorials https://www.youtube.com/watch?v=FOFbQdKYRdw

  • I think I am missing something crucial if the primary objectives of DevOps is (a) time efficiency to push a release and (b) ensuring that what is deployed in prod behaves the same way as in dev or qa, let's call this accuracy. Let me explain. I find the most amount of time that is spent on pushing out bug fixes or features is the QA cycle. So, even if you adopted agile to push just one apparently innocuous change, you cannot depend on the developer to do his/her unit testing and say, we are good to go to production. The QA person, who is impartial, will say, sorry dudes/dudettes, but I have to run regression testing. That means running through all the test cases again to ensure that the one change does not effect anything else the developer might not have thought about. So, in the QA cycle, time savings really comes down to, can you automate regression testing.which is far, far more difficult than automating other aspects of DevOps such as pushing out the code to prod or generating another instance of a prod machine or … And writing automated testing is extremely expensive for a lot of orgs that are not producing commercial software, but are developing an app in-house, for example, hence the need for humans to go through the test cases manually. Help, me out folks, am I missing something in my understanding of virtues of DevOps, assuming QA is the big elephant i the room?

  • I pity Youtube for not having the rating system, class act.

  • Click the Next video: Anna the unemployed 👀

  • Simple explanation: DevOps is in charge of put together all pieces of code from all development teams in a production environment. this environment is specific design to have all project information, and quickly release a build mainly for testers to verify… developers are only notified if one of their changes affected the build. This way Developers can continue working and are just interrupted in this case, letting DevOps the task to find the issues from Developers. A Project only need 1 or 2 DevOps

  • How come 'Dave ' is the start of process.. What about UX/UI?

  • Thanks a lot sir

  • very helpful

  • How can you automate all testing? The Jenkins website says it is under construction – can something be that cutting edge they haven't even approved the text yet???
    https://jenkins.io/doc/developer/testing/
    From what I read on there it seems like a test harness is required to test using Jenkins which I can see could work for unit testing and some basic integration testing (no real difference to what's been done for the past 20 years just a new tool to do it with) but how can you automate full e2e system testing or UserAcceptanceTesting or OperationsAcceptanceTesting or testing with a supplier eg trade throughput at a bank
    Testing is glossed over in this video showing how 'simple' it is to save the company money.  
    I think everyone understands that no money is ever generated by testing but its thorough testing that should stop you having issues (both major or minor) being visible to the customer.

  • Looks to me like something, that experienced developers would do on their own.

  • Ok, and what's the difference to scrum?
    Shouldn't they as well write small chunks of code, test it and release it?

    And why is there such a big focus an "development environment" vs "production environment" shouldn't the devolpment environment of course always be (as much as) like the production environment?

  • I don't understand why 'Dev-Ops' a thing. If we deploy Microservies over cloud, everyone is forced to adapt to a system like 'Dev-ops'. You don't have to think of 'Dev-Ops' as a special thing.. it comes your way anyway

  • Please speak louder

  • thanks a lot

  • Coders are a dime a dozen, easily outsourced overseas for few dollars an hour. It's twice as cheap as a burger flipper in NY city. All software creation will be eventually low wage as millions of new programmers each year through online learning.

  • DevOps is a software development methodology for companies . https://itechcraft.com/devops/ . if you mean people who work with cloud technologies, automation and continuous integration.

  • Actually, the whole video doesn't for a single minute explain in plain English what DevOps is. I think someone down in the comments said it correctly – DevOps is all about CI/CD.

  • i am devOp

  • https://fullstacknews.com/s/sdvmub/what_is_devops_simple_english

Leave a Reply

Your email address will not be published. Required fields are marked *