What is DevOps? - In Simple English
Вставка
- Опубліковано 4 жов 2024
- Simple explanation of DevOps without the complications and information overload. -- what do you think? Please share & comment!
DevOps is a concept with different interpretations and definitions, but when you get down to it, it's all about developers and operations teams breaking down silos and working together to innovate faster. For many companies, the ability to innovate at a rapid pace - responding to market conditions and customer feedback - is a key factor for success. Adopting the DevOps philosophy requires a new mindset, new tools and new skills.
More about DevOps:
www.rackspace.c...
www.rackspace.c...
Don't miss other videos and exciting material:
/ rackspacehosting
/ rackspace
/ rackspace
/ rackspace-hosting
You took a term that most non-techies don't know and told the basics and intermediates of that term in a great visual and understanding way. Thanks.
Simple English:
DevOps is a practice, just like Agile is a practice. Just like Agile had to refine previous practices for hardware development practices like LEAN to better suit software development, DevOps took principles like those from Agile, and adjusted them to better suit an operations team.
When someone says "I work in DevOps" or "I am a DevOps engineer", generally they either A) have no clue what the word they are using means, or B) they work on an operations team that focuses on configuration management, continuous integration, and other automation and standardization principles. Someone who is the Puppet/Ansible/Chef admin, might say "I am a DevOps engineer." What they really mean is that they are on a team that focuses on goals that achieve the principles of DevOps. A software developer does not say "I am a Agile Developer." Unfortunately, DevOps is such a popular buzz word that most people try to tack it on to their title to sound cooler.
What isn't DevOps? DevOps is NOT someone who does the role of both a developer and operations engineer. This seems to be the biggest misconception.
Sounds like a person who does both would be a DevOps Architect XD joking...
typedeaf
typedeaf
J
Karl Baker
Nice video! It is one of the best explanations as to WHAT DevOps is. I am an Agile Coach, and in 2011 we were practicing DevOps. It's very easy... it involves daily collaboration between the Developers and the Operations personnel. Much of the success of SCRUM (as a methodology) comes from bringing focus to a single Product. No more multiple projects being worked on at the same time. And DevOps is founded on this as well, where the Operations team mate became a dedicated member of the feature team.
Having the Ops guy dedicated meant he was directly involved with the day to day activities and had lots of time to see the Ops side of the Product well before hand. Being dedicated also meant the feature team did not have to jockey for position whenever they needed a new environment provisioned. It's too easy, BUT it does require Sr. Management to buy in to make it successful.
B
Absolutely ua-cam.com/video/MqruGJKdBLs/v-deo.html
Wow. I expected 30 seconds of theory with pictures and another 6,5 minutes of product promo. I'm surprised :-)
indeed.
David,
Yeah, that's what happens really often. On the other hand, just by explaining one of the processes that take place in the company, RackSpace already promoted their product somehow. This video shows how effective company can be and this is a kind of promotion already in my understanding.
@@datumticorp7311 ر٣
Still they skewed it into DevOps being about tools, which is not.
Incredible animation, incredible concepts. I work as a IT Recruiter here in Brazil, thanks for this good work.
instablaster...
3:35 - "Anna and Dave's team would write Configuration Management Code"... unfortunately, in the real world only Dave's Development team knows how to write Automation Code, Anna's Ops team merely knows to follow documentation on the execution of the Automation. This means that DevOps really boils down to the Development team writing Automation or hiring former Developers into Ops to write Automation. Meaning the traditional Operations skill set has becomes obsolete, since the management of Hardware and Networks is now Contracted to Cloud Infrastructure providers such as RackSpace, AWS and Azure, while the Software Deployment Automation must be written by people who can Code. In many Companies, the Operations team do not have the skill set to Code and merely oversee Virtualized resources manually through a User Interface. The lesson here, is in the Modern Era, both teams need to hire Developers who Code with different responsibilities on the Dev and Ops side. This is also the situation between QA and Dev where QA in the Modern Era must consist of Coders who also write Automation testing and not merely do Manual testing.
What kind of programming languages do Dev team use here?
+Sid bharadwaj In general an engineer should use the appropriate language for the task, the programming language is just a tool for providing solutions to problems. For devops this is typically now Ruby or Python or UNIX shell or powershell depending on what type of platform you are using, such as chef, puppet, ansible or salt.
As a former Op who didn't wait for DevOps movement to come around to tell me why automating everything is worth the time investment because the ROI is much much bigger I have to disagree with you. I also have a formal IT education and this helps but it takes me (or any other Op or former Op as far as I believe) just a few hours to figure out our way around most of the things a Dev or QA have to do related to this (automating stuff). I don't mean I will be fluent or as good as them but I can happily help with stuff. The other way around should be true as well - a Dev or QA should be able to at least understand how the tools are used and the real good ones will be able to help with developing those. As a DevOps consultant I am relying pretty heavily on feedback and help from Dev and QA (and Ops for that matter) in order for me to be able to help them. Because after all that's (in my opinion) what DevOps is about: helping "traditional" roles be better by taking away most of their concerns - be it integration, deployment or tooling.
in short, all IT guy/gal needs to code now, no matter what he/she does. this is the future
as a freelancer whom frequently develop an app from back end to front end i completely agree with this..its useless if the ops team can't code or at least write a script..
This video is from 2013. However, it is one of the best I have seen on DevOps in a nutshell.
This is the best summary of DevOps I've ever seen.
So DevOps are for team, not for one individual?
Thank you so much for this video! Most of the other explanations usually just throw high-level programming jargon. Simple English is the best way to explain it (for most of the audiences, if they are coding, they are coding in english alphabet).
I still don't get it.
someone got bored and named something again
remember the cloud? there was no name for it. stuff was on the internet forever. but it didn't mean anything until someone got bored and named it "the cloud"...then it was CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD GOTTA GETON THE CLOUD DO YOU CLOUD COMPUTING CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD CLOUD
Haha I remember thinking "..'The cloud'... You mean 'the Web'.?!?.why are you changing the name??"
MBA buzzwords for execs who don't understand tech.
cloud is prolly the dumbest term for somer server out there...
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
if you want to see free videos on trending tools like azure, aws, maven, ansible,devops then watch here
and if you like then share with your devops friends
ua-cam.com/channels/2srBvMPv9ISmdYmzE-j0TQ.html
in other words u can fire Anna?
Nope, Anna still has plenty of other things to worry about.
+Eugene Malihin bringing coffee isn't that important :)
+TitanREW LOL
Or not...
haha lol
Immensely useful for a starter. Thanks for creating this!
Has anyone played Call of Duty Dev Ops 4 yet?
Dev Ops 4 - Carl on Duty
@@caspersvendsen7651 bro that shit luit
you need to be hired by Activision to play that
@@caspersvendsen7651 lmao
@@caspersvendsen7651 Hahaha
Love when I got dat AHA moment o/
Dev + Ops -> Development + Operations(Infrastructure,System Admin)
It's great. Unless you've already pitched that idea, started working on it, and were told, "NO! That won't work, and we don't have the budget to try" by your organization. Good luck.
+Andrew Chandler then you can try this www.slideshare.net/SolarWinds/the-7-principles-of-devops-and-cloud-applications
+gerardodada nah, I just transferred out of the same organization that pitched us your first video. Made things much better for me.
Let just call whatever we are doing today DevOps, and keep doing the same. Because first people need jobs and second is senior management only if they can put the words such as Innovation, Agile and DevOps in their slides.
Nice video. I learn that we know DevOps and use it since I finished the university, but now they give it a name. There is absolutely nothing new in DevOps. All the idea of automation, creation of a testing environment like the production environment, continuous integration, continuous delivering.... It is all that we try to do but the companies usually don't want to because they don't understand and think that this is to spend money with "toys" for developers, so they prefer to trow money away, spending it later on difficult maintenance and bug fixing and asking why there are bugs in the system. Well, maybe because the development environment is in Windows and the productions environment in Unix, or also because you didn't want to spend some time to install and use Jenkins or Bamboo, or because you never care about having an integrated testing environment, just unit test should be enough, .... the history we all know.
Excellent. Being a non technical person I understood it too well
Excellent, simple explanation of DevOps! Bravo Rackspace.
This is very good explanation, its summarize big DevOps stages with the short explanation
Great video; DevOps Demystified. "Automating Everything" is great. But automating a "bad process" is worse than no automation!!!
I think it's more to do when you're automating processes that should be done manually or partly manually.
Very nice, clear and simple.
Thanks
I loved this video and I'm so happy that you used the example of Anna, small things like this lead to a huge change ❤️ Anna you rock!
Anna's role was made redundant by the company's new DevOps strategy and she was laid off. Sorry Anna!
ultimate presentation about devops.
Good simple explanation. If it is also mentioned where DevOps practice are applicable VS where Traditional development is applicable. It would be clearer
started promising to answer my curiosity to understand this term but somehow was too high level and I was not able to relate to practical real world examples and also did not understand how the responsibilities will be shared between development and operations teams
Worth watching. Thank you.!
Yes. To break into a high paying DevOps career, candidates should focus on sharpening their Python because DevOps is pure automation. Every company will use different tools CloudFormation, TerraForm, etc, etc. It is really inefficient to chase the latest tools. If you watch my channel and focus on Python Interview techniques, it be the most bang for your time.
Very simple to understand.
Very good introduction! That's the way it must be done
Very nicely presented. Thank you.
Thank you so much for posting this insightful video on DevOps career. I am a coding beginner, and I am studying BSc Accounting and Finance at age 35. I have returned to University for a career change, and now I am now interested in coding too.
I salute your bold step. I'm 43 and considering a career change too. Hope it's not too late.
@@iniekpe1477 Thank you. I have just graduated with my BSc degree at age 36 (so excited!). And I am preparing to do MSc degree.
Definitely not late at all, I honestly feel more confident and determined to building my next career since I've had various work experience. I suggest think about what you want to do as a next career and tie in what you have already as work experience.
Nicely put...to understand the basics of devops
Good example and clear explanation.
Simple and nice explanation that conveys the gist of DevOps
Devops is a jack of all trades
Thank u so much, so simple but very informative video and well explained, thank u again 😊
Great job. Thank you so much.
incredibly helpful; thank you
"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!
This is so cool/exciting, thanks!
clear and concise presentation. very useful
Nice explanation. Perfect video content that elaborated the concept.
DevOps is a great example of benefits that come with sharing responsibility rather than trying to push it on someone else. By applying main rules of team founding and sharing the same goal, DevOps has become a great project. I personally think that having few supervisors who can efficiently check work that has been done between Development and Operations management departments would result in even better performance of the DevOps scheme. This would enable Developers to focus even more on their job and let Ops' take first look at the job that has been done and then send it forward to supervisors.
very informative! Good one! Thanks much!
Glad you enjoyed it!
Nice Explanation
Bloody great explanation! I am wondering where I could get those slides?
Absolutely awesome presentation and content!
Great video, but the drum beat on the music sounds like a hammer and is a bit distracting.
Great video!!!
so in few works - Dave will have to scale back his development (to the point 0 if have to) and Anna can go find another job? thx, this really was simple
Nice ! well explained - thanks
Nice presentation... very helpful.. thanks :)
What's with the panel beater on the background muzak? It's very irritating.
This is a very good video.,,,,,,,,,
Amazing explanation!
Great video!
Thanks, great introduction to DevOps.
great intro video of devops, loved the way you guys defined the role of devops, the last 30 seconds were bit boring where RS devops kicked in :P
Well explained!!
Excellent explanation
Nicely done.
Just a suggestion - It's great that you guys explain the concept using Dave and Anna (a real-life scenario) but the continuous drawing in the video is what grabs my attention. :D As a result, I listen less and see more because things are continuously moving. I don't know how many people have felt similarly but this is just my experience with this video.
Just stop looking at the screen lmao
This is a great video! it's value is in its simplicity! #KeepItSimple
Excellent presentation, I am going to show this before we present on the type of people we need in the Ops part of the Dev Op partnership. It seems that operations mostly consists of people who's career path has gone from help desk to operations or have stumbled into it from college/university. The problem with this is that the developers and operators do not speak the same language. What developers need from Ops is the ability to checkout,read,debug, code and pinpoint problems in the prod like environments, tie a bow on them and send them to Dev.
In your example Ops is demonstrated by a SysAdmin, SysAdmins are not developers, what is needed is an operational developer. A seasoned developer who likes to fight fires in production, and knows how to do root cause analysis in any language. Most developers in an organizations are tasked with project work and are not available for patches or prod issues. Ops to me is (DBA, Hardware, Network, SysAdmins, Operators, Operational Developers) Op developers need an a good all around understanding of the of all supporting infrastructure, plus a solid development background and the ability to coordinate and talk nicely to all groups. They need to be able to distill workarounds into step by step instructions for operators(off shore or help desk) and tie it to monitoring systems that know how to alert on identified issues.
I really like your comment!
In a way, I am "people who's career path has gone from help desk to operations or have stumbled into it", and I like what you say. Basically, the people who could do the job you describe ("Op developers") are rare and expensive. The issue here is that management wants us (me) to be that guy, but without putting in the money to properly train me. Capitalism f*ck yeah !
How to organise the process to the purpose new deployments "go live" do not lead to situations when business is not ready process wise to support that new functionality?
How does blockchain play into DevOps?
Sounds like the merger of two IT departments working in an Agile environment. Iterative software development has been around since the 80's and the integration of these two departments has probably been recognized quite some time ago. Maybe they should call it Agile DevOps?
very good presentation
Does anyone else feel like modern coding concepts such as DevOps (which I know isn't new) makes things more complicated in an already complex job? Like it's going in the wrong direction?
no
I'm thinking of doing a course on DevOps on coursera, any prerequisites I should know before getting into DevOps?
So is this now called SRE? What difference is there?
In Simple English:
DevOps is a GOD of IT, which every software professional should worship to.....
Got the opportunity to work inside rackspace data center in Tx our company built one of the new rooms.
How to get a job in data center's....what are the Skills we need
So in your example, the software is written and tested in smaller chunks. Does this actually decrease the time to production? I'm trying to see the problem being solved here.
Nice video!
Thank you. I appreciate the clarity of this explanation,.
So good. Thank you.
Need to learn this kind of new technologies to move on from our traditional system administrator job also to save our jobs in the future :p ...
well explained
Thank you.
Awesome!
TL;DR: Another vague buzzword meant to sell stuff. Ops has automated its own job so now Dev can simply commit a new yaml to get code live with more memory for the database cluster for example.
I created a .srt file for Spanish speakers, I would love to share it with you. How I can delivery it to you?
Hello,
Did you use a software to carry out this video ?
I like the style of this video, anyone know how to create this kind of video?
IMO DevOps came from an Engineering Team at small startups where Developers were doing both SysAdmin and Dev work. Then Executives at larger companies told their Dev/SysAdmin Managers make it happen, and have been struggle to implement. In managing SysAdmins for 15 years in Operations at multiple companies and working closely with Dev Teams, I have always been against DevOps.
1. First time implementation is difficult. Dev Teams don't typically want to change their process, are too busy meeting deadlines, or don't want to take architectural guidance on the process flow from SysAdmins.
2. SysAdmins end up doing more work and longer hours. They are the ones now pushing deployments and sometimes without Dev Teams available for support.
3. Automation is great, implementation doesn't happen overnight and Dev Teams don't want to wait or continuously help test.
4. If Dev Teams are not 110% onboard and excited by doing it, SysAdmins are wasting their time, end up doing all the work, or being set up to fail.
KISS: Devs give the SysAdmin's a deployment packaged (rpm, jar, tar) and SysAdmins push it, extract it, restart services. A developer should always be there to support any issues. SysAdmins only have to architect/automate how the package is deployed across the environment consistently.
Kasey Dunbar actually you are wrong. I am a developer and I expect the sys admin to deploy the rpm correctly without any support. If something goes wrong the sys admin should be able to roll back and create an incident / ticket for the developers to look at.
If a sys admin needs a developers help to deploy something then he/she should do something else.
As a developer, I disagree. We should be available for support in case they need anything or if apps behave erratically while deploying. If something goes a little weird they can't take the call if it's okay or should the code be rolled back. I have worked closely with Ops team and their work is tricky. They are handling a variety of applications build and deployed in different ways on different platforms. It looks easy for us because we're 100% working on the same application/software. What you said is fine technically, but it's bookish. I think we should support each other for greater stability of our application and overall customer satisfaction.
You've missed the point entirely. Continuous Integration / Deployement is the key and point in DevOps, you setup the pipeline and then Ops/Sys don't deploy anything at all. Developers merge a new feature branch to master, it passes automated test, it is automatically deployed to development environment, passes test, goes to staging, passes there and goes to production. A new feature/bugfix can be in production in minutes/hours after it passes code review.
I pity UA-cam for not having the rating system, class act.
kitne lakh tak ka pkg mil jayega agar devops ka kors kar liya to ???
Bhaya aaj kal to har koi devops engineer he ..
Why is the video's highest resolution 360p?
Which tool you have used for preparing presentation?
great video :)
In a few words, DevOps is all about CI/CD nothing more than that. To be more specific Git / CircleCI / Unit Testing/ Functional Testing / Docker / Kubernetes / AWS = DevOps
thank you
I disagree, these are tools that enable DevOps, the concept, in my opinion, is the bigger picture that delivers value faster to the business side of the company which in turn enable them to make more money faster.
What about Jenkins ansible
DevOps is basically "everything required to get business value (in the form of features, bug fixes, etc) into users' hands faster". You focus on the tooling, but if teams are poorly structured, the culture of the organization does not understand or value rapid iteration with small batch delivery, etc... your tooling won't matter in the least. Tools, executive sponsorship, alignment of processes with KPIs and/or OKRs, making feature adoption everyone's responsibility and much more goes into the most successful DevOps implementations. It's a super-simple concept but I feel like tools are just a part of the story.
Any one can help me to know the "what is the qualification and experience required to do this course"
if you want to see free videos on trending tools like azure, aws, maven, ansible,devops then watch here
and if you like then share with your devops friends
ua-cam.com/channels/2srBvMPv9ISmdYmzE-j0TQ.html
Thanks a lot sir
Excellent!
The background music is repetitive and distracting. Which value does it add to the presentation?
Does concept work on branching repositories?