Day-1 | Fundamentals of DevOps | Free DevOps Course | 45 days | #devopscourse #learning

00:30:39
https://www.youtube.com/watch?v=Ou9j73aWgyE

Resumo

TLDRIn this first session of the DevOps Zero to Hero course, Abhishek introduces key concepts including the definition and significance of DevOps, which is presented as a culture aimed at enhancing application delivery efficiency through automation, quality assurance, monitoring, and testing. The instructor highlights common interview questions related to understanding and presenting oneself as a DevOps engineer. He reinforces the importance of being prepared to answer why DevOps is crucial in today’s tech landscape. This foundational knowledge sets the stage for deeper exploration in forthcoming lessons.

Conclusões

  • 📅 Today marks the start of the DevOps course!
  • 🔍 DevOps is a culture focused on improving application delivery.
  • 💡 Understanding 'why DevOps' is essential for roles in the field.
  • 🗣️ Prepare how to introduce yourself in interviews effectively.
  • ⚙️ Automation, Quality, Monitoring, and Testing are the cornerstones of DevOps.
  • ❓ Common interview questions revolve around daily activities and definitions.
  • 🌍 DevOps integrates development and operations for efficiency.
  • 📖 Expect future lessons to delve into the software development lifecycle.
  • 💬 Engage with the community by asking questions in the comments.
  • ✅ Sharing this free course can help someone else learn DevOps.

Linha do tempo

  • 00:00:00 - 00:05:00

    Abhishek introduces the DevOps Zero to Hero course, outlining the agenda. The focus of the first day is understanding DevOps basics, including definitions, reasons for its implementation, and interview preparation related to DevOps roles.

  • 00:05:00 - 00:10:00

    DevOps is described as a culture that improves an organization's ability to deliver applications quickly. Abhishek emphasizes the importance of delivery speed and the need for organizations to adopt practices that allow for rapid version releases and bug fixes.

  • 00:10:00 - 00:15:00

    Further discussion on DevOps indicates that it is not just about rapid delivery; it encompasses automation, monitoring, quality assurance, and testing. These elements are essential in ensuring the delivery process is efficient and effective.

  • 00:15:00 - 00:20:00

    The evolution of DevOps is discussed, highlighting historical practices that involved multiple roles (system administrators, build and release engineers) with manual processes that slowed down delivery. DevOps emerged to streamline these processes and improve efficiency by combining these roles into a cohesive team.

  • 00:20:00 - 00:25:00

    Abhishek elaborates on how to introduce oneself in a DevOps interview. He suggests mentioning experience, current roles, and past experiences, especially if they relate to system administration or software development. He emphasizes the importance of honesty about experience levels.

  • 00:25:00 - 00:30:39

    Finally, Abhishek encourages viewers to subscribe and engage with the content as the series progresses, teasing future lessons about DevOps and the software development lifecycle. He invites viewers to share feedback and remain engaged with the learning process.

Mostrar mais

Mapa mental

Vídeo de perguntas e respostas

  • What is DevOps?

    DevOps is a culture that improves an organization's ability to deliver applications by enhancing collaboration between development and operations.

  • Why is DevOps necessary?

    DevOps streamlines application delivery processes, reduces manual efforts, and fosters a culture of continuous improvement, automation, and quality assurance.

  • How should I introduce myself in a DevOps interview?

    You should explain your experience in DevOps, any previous roles that relate to it, and your current responsibilities, as well as tools and methodologies you're familiar with.

  • What are the four pillars of DevOps?

    The four pillars of DevOps are automation, quality assurance, continuous monitoring, and continuous testing.

  • What will be covered in the upcoming classes?

    Future classes will focus on the software development lifecycle and the role of DevOps within it, along with a recap of foundational concepts.

  • Can I ask questions if I'm unclear?

    Yes, viewers are encouraged to post questions in the comments for discussion and clarification.

Ver mais resumos de vídeos

Obtenha acesso instantâneo a resumos gratuitos de vídeos do YouTube com tecnologia de IA!
Legendas
en
Rolagem automática:
  • 00:00:01
    hello everyone my name is Abhishek and
  • 00:00:04
    welcome back to my channel as you all
  • 00:00:06
    know we are going to start the devops
  • 00:00:08
    Zero to Hero codes and today is the D1 I
  • 00:00:11
    know you're all very excited and I'm
  • 00:00:13
    equally excited as well so today I'm
  • 00:00:16
    here
  • 00:00:17
    with the first day of the course and as
  • 00:00:19
    is the first day we'll start with the
  • 00:00:21
    basics what we are going to learn today
  • 00:00:22
    is we'll try to understand what is
  • 00:00:25
    devops we'll try to see Buy devops which
  • 00:00:28
    are you know fundamentally these are the
  • 00:00:31
    important questions for any of the
  • 00:00:32
    devops job interviews so let's say you
  • 00:00:34
    are attending a devops job interview if
  • 00:00:36
    you don't understand the concept of
  • 00:00:37
    devops why you are using devops what
  • 00:00:40
    actually is devops then you know the
  • 00:00:43
    interviewer will lose you there uh
  • 00:00:45
    during the first five minutes you know
  • 00:00:47
    it is very essential for you to project
  • 00:00:49
    yourself in a better way so that's why
  • 00:00:52
    you need to understand what is devops
  • 00:00:54
    and why you have to implement devops
  • 00:00:57
    and after that we'll see how to
  • 00:00:59
    introduce yourself for a devops
  • 00:01:00
    engineering position whether it's a
  • 00:01:02
    fresher position whether it's experience
  • 00:01:04
    we'll talk about uh all of these things
  • 00:01:06
    uh how do we introduce ourselves uh
  • 00:01:08
    during an devops interview and then
  • 00:01:11
    we'll also try to see the most asked
  • 00:01:14
    question again during an interview is
  • 00:01:16
    people will ask this question in
  • 00:01:18
    different way people might ask you what
  • 00:01:19
    are your day-to-day activities as a
  • 00:01:21
    devops engineer or people might ask you
  • 00:01:24
    um you know can you walk us through your
  • 00:01:25
    day as a devops engineer what do you
  • 00:01:27
    usually do on everyday basis so these
  • 00:01:29
    are the four important questions uh that
  • 00:01:32
    you have to know uh before you start
  • 00:01:34
    with learning any devops tools or before
  • 00:01:36
    you learn how devops will fit into your
  • 00:01:38
    software development life cycle these
  • 00:01:40
    are some of the questions that you have
  • 00:01:42
    to know and you have to have the answers
  • 00:01:44
    for
  • 00:01:44
    and this not that uh because these are
  • 00:01:49
    the questions that usually people start
  • 00:01:51
    with the interview right whenever you
  • 00:01:52
    give interview in a man company or any
  • 00:01:56
    uh startup as well people would start
  • 00:01:58
    with these basic questions so always be
  • 00:02:00
    confident and be prepared with what you
  • 00:02:03
    are going to answer for these questions
  • 00:02:04
    so we'll start with one by one so we'll
  • 00:02:06
    see what firstly we'll see what is
  • 00:02:08
    devops then we'll move to uh see why
  • 00:02:10
    devops has come into picture and uh
  • 00:02:13
    we'll see how to introduce yourselves
  • 00:02:15
    and finally the day-to-day activities
  • 00:02:17
    okay so without wasting any time
  • 00:02:20
    so firstly
  • 00:02:22
    what is devops right so if you look at
  • 00:02:25
    the textbook definitions for what is
  • 00:02:27
    devops there are hundreds of definitions
  • 00:02:29
    okay so if you go to amazon.com they
  • 00:02:31
    have a definition for devops if you go
  • 00:02:33
    to uh Red Hat they have a different
  • 00:02:36
    definition for their devops but in
  • 00:02:38
    general like you know what is devops we
  • 00:02:40
    will try to understand that one okay so
  • 00:02:42
    if you ask me devops is basically a
  • 00:02:45
    cultural I mean it's a culture right
  • 00:02:48
    devops is basically a practice or a
  • 00:02:50
    culture that you are adopting in your
  • 00:02:52
    organization like you you cannot uh call
  • 00:02:54
    it on a specific term but in general you
  • 00:02:57
    can say devops is a culture that you are
  • 00:02:59
    going to follow that would increase your
  • 00:03:02
    organization ability to deliver
  • 00:03:03
    applications right so that is the end
  • 00:03:06
    goal of devops so if you have to put
  • 00:03:07
    that in one single line you can say it
  • 00:03:09
    has a culture
  • 00:03:12
    that
  • 00:03:14
    improves the
  • 00:03:18
    organizational's ability to deliver the
  • 00:03:20
    applications okay so end of the day what
  • 00:03:22
    any organization will do any
  • 00:03:24
    organization would deliver their
  • 00:03:26
    applications right so the delivery is
  • 00:03:27
    the key factor okay so whether it's
  • 00:03:30
    example.com whether it's amazon.com
  • 00:03:32
    flipquart.com what is the end goal of
  • 00:03:35
    any organization the end goal of any
  • 00:03:36
    organization is the delivery right so
  • 00:03:39
    let's say uh there is an organization
  • 00:03:41
    called example.com okay so if
  • 00:03:44
    example.com is taking
  • 00:03:49
    10 days okay this is just an example
  • 00:03:51
    let's say example.com is taking 10 days
  • 00:03:53
    to deliver their version of an
  • 00:03:55
    application from V1 to V2 let's say they
  • 00:03:58
    are taking 10 days okay or let's
  • 00:04:01
    consider pubg okay so pubg is one of the
  • 00:04:04
    widely played games let's say there is
  • 00:04:05
    an issue in the pub J or they want to
  • 00:04:07
    introduce a new feature of the pubg
  • 00:04:09
    version so if they are taking 10 days to
  • 00:04:11
    introduce this version everything is
  • 00:04:13
    done let's say the development is done
  • 00:04:14
    and everything uh else apart from the
  • 00:04:17
    delivery is delivery uh point of view
  • 00:04:19
    everything is done and if they have to
  • 00:04:21
    hold their application for 10 days just
  • 00:04:24
    to deliver right to deliver to the unit
  • 00:04:26
    staging then the staging environment
  • 00:04:27
    then finally to the production then
  • 00:04:29
    that's not a good practice right so what
  • 00:04:33
    should happen ideally is whenever there
  • 00:04:35
    is a security issue or whenever there is
  • 00:04:37
    a bug in your software like you are
  • 00:04:39
    using your Android mobile and all of a
  • 00:04:41
    sudden your Android mobile has some bug
  • 00:04:43
    which has the ability for the hacker to
  • 00:04:45
    get into your mobile phone and hack your
  • 00:04:48
    mobile phone so what would Android do
  • 00:04:50
    they would quickly launch a new version
  • 00:04:51
    and they'll say everybody has to upgrade
  • 00:04:52
    to this version or if you have enabled
  • 00:04:54
    the auto upgrade your application would
  • 00:04:55
    be I mean your Android would be Auto
  • 00:04:57
    upgraded
  • 00:04:58
    so all this process should take within
  • 00:05:02
    like you know if it happens within hours
  • 00:05:04
    then it is best if it happens in one or
  • 00:05:06
    two days then it is also a good one
  • 00:05:08
    right instead of taking 10 days if you
  • 00:05:11
    can have the ability to deliver your new
  • 00:05:13
    version in one or two days or couple of
  • 00:05:15
    hours or in minutes of time that is
  • 00:05:18
    called devops okay
  • 00:05:21
    so devops is a process of increasing the
  • 00:05:25
    ability to deliver your applications but
  • 00:05:28
    is it only about delivery no okay so
  • 00:05:31
    that would be the next thing that we
  • 00:05:32
    have to look at so most of the times
  • 00:05:33
    what happens is people would compare
  • 00:05:36
    devops okay whenever even you try to
  • 00:05:40
    learn devops mostly people talk about
  • 00:05:42
    cicd okay if you if you're new to devops
  • 00:05:44
    and if you don't know what is cicd
  • 00:05:46
    that's totally fine don't have to worry
  • 00:05:47
    about it but in general people always
  • 00:05:50
    look at devops as cicd that is
  • 00:05:51
    continuous integration and continuous
  • 00:05:53
    delivery but even in my previous uh
  • 00:05:56
    slide when I was explaining you I said
  • 00:05:58
    devops is about improving your delivery
  • 00:06:01
    but is it only about delivery no so
  • 00:06:03
    devops is about improving delivery okay
  • 00:06:06
    that is something that we talked about
  • 00:06:09
    improving delivery but how can you
  • 00:06:12
    improve the delivery if you have to
  • 00:06:14
    improve the delivery let's say if you
  • 00:06:15
    forget devops aside let's say there is a
  • 00:06:18
    company that is manufacturing chips or
  • 00:06:20
    let's say there is a company that is
  • 00:06:21
    manufacturing uh some kind of biscuits
  • 00:06:24
    so if they have to improve their
  • 00:06:26
    delivery what is something that you have
  • 00:06:27
    to do they have to include the
  • 00:06:29
    automation okay so devops is always
  • 00:06:32
    about
  • 00:06:33
    I mean devops is also about automation
  • 00:06:35
    okay now let's say they have automated
  • 00:06:38
    so the chips are being manufactured in
  • 00:06:40
    one single day okay so they reduce the
  • 00:06:42
    manual labor and they increa they
  • 00:06:44
    brought in new Machinery that can
  • 00:06:47
    produce the chips in one day but is it
  • 00:06:49
    okay is it uh perfect for the customers
  • 00:06:52
    no what the customer would require is
  • 00:06:54
    apart from the automation they would
  • 00:06:55
    also look at the Quality
  • 00:06:58
    right so if you are manufacturing the
  • 00:07:00
    chips in one single day that's fine for
  • 00:07:02
    me but as an end user what I'd be
  • 00:07:04
    looking at is the quality as a
  • 00:07:06
    manufacturer you would be looking at
  • 00:07:07
    automation okay and
  • 00:07:10
    devops is also about monitoring okay
  • 00:07:14
    what is monitoring so monitoring is
  • 00:07:16
    nothing but let's say let's take the
  • 00:07:18
    same example so you are providing the
  • 00:07:20
    chips you have automated the process you
  • 00:07:21
    have also maintained the quality but how
  • 00:07:24
    would you ensure that your quality is
  • 00:07:25
    maintained you have to build in
  • 00:07:27
    monitoring right so always make sure
  • 00:07:31
    that whenever there is an issue in the
  • 00:07:33
    quality or if there is an issue in the
  • 00:07:35
    automation somebody has to report back
  • 00:07:36
    to you right that is monitoring and
  • 00:07:39
    finally there is one more important
  • 00:07:41
    aspect that is any guesses here you have
  • 00:07:44
    quality you have automation you have
  • 00:07:46
    monitoring the other important aspect is
  • 00:07:49
    testing
  • 00:07:52
    Okay so
  • 00:07:54
    testing is also one of the important
  • 00:07:56
    aspect so without testing you cannot
  • 00:07:58
    ensure quality or you cannot ensure that
  • 00:08:00
    your automation is correct so now if we
  • 00:08:03
    take it the new definition okay in the
  • 00:08:05
    previous slide we call it devops as
  • 00:08:08
    devops is
  • 00:08:10
    the process of continuously delivering
  • 00:08:12
    in a
  • 00:08:13
    quick manner right that is what we
  • 00:08:15
    talked in the previous slide but now if
  • 00:08:17
    we talk about the new definition after
  • 00:08:19
    learning all of these things now I can
  • 00:08:20
    say devops is a process of improving
  • 00:08:24
    your delivery I mean making your
  • 00:08:26
    delivery quicker by ensuring that there
  • 00:08:29
    is a proper automation you have ensured
  • 00:08:31
    that the quality is in place you have
  • 00:08:33
    ensured that you have set up proper
  • 00:08:35
    monitoring and you have ensured that you
  • 00:08:37
    have a continuous testing so this is the
  • 00:08:40
    definition of devops okay so let's try
  • 00:08:42
    to put that in uh okay let me go back
  • 00:08:47
    let me try to put that on a paper okay
  • 00:08:49
    for you for anybody who is just starting
  • 00:08:52
    to understand the definition of devops
  • 00:08:54
    what I would say is devops
  • 00:08:59
    is a process
  • 00:09:03
    of
  • 00:09:05
    improving
  • 00:09:08
    the
  • 00:09:11
    application delivery
  • 00:09:15
    so it uh I mean you don't have to always
  • 00:09:17
    consider it as an application it can be
  • 00:09:19
    anything right you can deliver an
  • 00:09:21
    application you can deliver a script you
  • 00:09:23
    can deliver anything okay just for your
  • 00:09:25
    basis I just called improving the
  • 00:09:27
    application delivery but you can also
  • 00:09:29
    consider it as improving your script
  • 00:09:32
    delivery or any binary or anything okay
  • 00:09:35
    by ensuring okay devops is a process of
  • 00:09:39
    improving the application delivery by
  • 00:09:41
    ensuring that there is a proper
  • 00:09:43
    Automation in place
  • 00:09:46
    okay by ensuring that there is a quality
  • 00:09:49
    that you have maintained
  • 00:09:53
    continuous monitoring
  • 00:09:58
    monitoring is a very key aspect okay
  • 00:10:00
    people also call it as observability so
  • 00:10:03
    monitoring and observability are hand in
  • 00:10:05
    hand things whenever we uh deal with or
  • 00:10:07
    talk about uh monitoring we'll also talk
  • 00:10:09
    about observability but for now you can
  • 00:10:11
    think monitoring or observability and
  • 00:10:14
    finally there is a continuous
  • 00:10:19
    testing this is devops okay so this is a
  • 00:10:24
    perfect Ideal World definition of devops
  • 00:10:26
    you can modify it on your own basis but
  • 00:10:29
    if you ask me uh during an interview
  • 00:10:31
    what I would say is if somebody is
  • 00:10:33
    asking me let's say Abhishek is giving
  • 00:10:35
    an interview an interview asked me that
  • 00:10:37
    what is divorce I would say devops is a
  • 00:10:39
    process of improving the application
  • 00:10:41
    delivery by ensuring there is a proper
  • 00:10:44
    automation with a code quality that is
  • 00:10:47
    maintained or with the application
  • 00:10:48
    quality that is maintained and ensuring
  • 00:10:51
    there is a continuous monitoring and
  • 00:10:52
    continuous testing in place okay now
  • 00:10:55
    what will you achieve with all of these
  • 00:10:56
    things end of the day your end goal as a
  • 00:10:59
    devops engineer should be that there
  • 00:11:01
    should not be any manual process or
  • 00:11:04
    during your application delivery you
  • 00:11:06
    have to fasten up your process let's say
  • 00:11:08
    your application is delivering in you
  • 00:11:10
    are hired as a devops engineer okay so
  • 00:11:12
    example.com is hiring a devops engineer
  • 00:11:14
    what would be the goal of the CEO or the
  • 00:11:17
    team manager of the example.com would be
  • 00:11:21
    once it devops engine is in place what
  • 00:11:23
    he'll expect from you is if their
  • 00:11:25
    application is delivered in two weeks
  • 00:11:27
    okay
  • 00:11:29
    so what what would be the expectation
  • 00:11:31
    from a devops engineer is he has to
  • 00:11:33
    reduce this two weeks to one week but
  • 00:11:35
    again by ensuring that you have all of
  • 00:11:39
    these things in place and so this is a
  • 00:11:42
    basic definition okay because today we
  • 00:11:43
    are dealing with day one so I don't want
  • 00:11:45
    to complicate the uh definition by
  • 00:11:47
    including all of the things like you
  • 00:11:49
    know I don't want to include the
  • 00:11:51
    complicated terms like being Cloud
  • 00:11:52
    native or all other things which will
  • 00:11:54
    come in place okay while we progress to
  • 00:11:57
    the new or the next episodes of our
  • 00:12:00
    devops learnings we would include the
  • 00:12:02
    concepts of being Cloud native we will
  • 00:12:04
    include the concepts of being you know
  • 00:12:06
    serverless but not today today you just
  • 00:12:09
    understand these things that is more
  • 00:12:10
    than enough okay but as we advance what
  • 00:12:13
    I want to tell you is I'll talk about
  • 00:12:15
    being Club native I'll talk about being
  • 00:12:17
    a serverless or shift left so all those
  • 00:12:20
    things will come in the next phases or
  • 00:12:21
    in the next episodes of devops but for
  • 00:12:23
    today I hope everybody is clear with
  • 00:12:25
    this definition okay so for a beginner
  • 00:12:28
    this is more and well and good to talk
  • 00:12:30
    about devops
  • 00:12:32
    okay so now this is about what is devops
  • 00:12:35
    now
  • 00:12:36
    if you understood what is devops and how
  • 00:12:38
    to answer this in your interview the
  • 00:12:40
    most important thing is to understand
  • 00:12:41
    why devops because that would be the
  • 00:12:43
    next question so if your interviewer is
  • 00:12:46
    really looking for hiring a good
  • 00:12:48
    candidate your interviewer would be
  • 00:12:50
    asking why devops okay okay now I I'll
  • 00:12:52
    hire you but why should I hire you or
  • 00:12:54
    why should I hire a devops internet so
  • 00:12:56
    for that
  • 00:12:58
    the thing would be to understand why
  • 00:13:01
    devops
  • 00:13:05
    okay now let's try to understand a very
  • 00:13:07
    simple thing okay so forget about the
  • 00:13:09
    definition and everything so what I will
  • 00:13:11
    try to explain you is firstly let's say
  • 00:13:14
    uh let's assume that there is a
  • 00:13:16
    developer okay so let's call him
  • 00:13:22
    developer I'm not sure if the color
  • 00:13:24
    contrast is fine okay so what this
  • 00:13:27
    developer is doing is he is trying to
  • 00:13:29
    write the code for his application okay
  • 00:13:31
    so let's say the developer has developed
  • 00:13:34
    this application now end goal is whether
  • 00:13:37
    it can be a Android application whether
  • 00:13:39
    it can be a static website or whether it
  • 00:13:43
    can be a web application what would be
  • 00:13:44
    the end goal for this developer or what
  • 00:13:47
    would be the end goal for this uh
  • 00:13:49
    company called example.com okay
  • 00:13:52
    so once this developer writes the code
  • 00:13:55
    the end goal would be
  • 00:13:57
    the receiving end that would be the
  • 00:13:58
    customer right so there has to be a
  • 00:14:01
    customer who uses this application
  • 00:14:05
    so that would be my end goal okay so
  • 00:14:08
    developer is writing the code and
  • 00:14:10
    customer is receiving the code so what
  • 00:14:12
    happens in between let's say devops is
  • 00:14:14
    not in place so let's go back to 10
  • 00:14:17
    years okay so before 10 years so what we
  • 00:14:20
    are discussing now is
  • 00:14:23
    before 10 years
  • 00:14:25
    so what happened was before 10 years
  • 00:14:27
    when these people were not there like
  • 00:14:29
    the devops engineers were not there what
  • 00:14:30
    used to happen or the process of devops
  • 00:14:32
    was not there what used to happen is
  • 00:14:34
    once the developer writes the code so he
  • 00:14:36
    used to check in this uh application
  • 00:14:38
    code because you know there will not be
  • 00:14:40
    one single developer right there will be
  • 00:14:42
    multiple Developers so they have to
  • 00:14:44
    share their code somewhere so they used
  • 00:14:46
    to put that in a central location
  • 00:14:52
    and after that what you what used to
  • 00:14:54
    happen was from this central location
  • 00:14:56
    this devops engineer or uh sorry there
  • 00:14:59
    was no devops engineer so this guy who
  • 00:15:01
    used to be called as a system
  • 00:15:02
    administrator or a build and release
  • 00:15:04
    engineer what they used to do is they
  • 00:15:06
    used to create a server okay and what
  • 00:15:09
    they used to do is they used to deploy
  • 00:15:11
    this application the developer has wrote
  • 00:15:13
    the application they used to deploy this
  • 00:15:14
    application on the server okay so let's
  • 00:15:16
    call this as app so the app is deployed
  • 00:15:19
    on the server and the next process would
  • 00:15:21
    be somebody called a tester okay so who
  • 00:15:24
    is this guy there is a guy called as a
  • 00:15:26
    tester
  • 00:15:28
    so tester would test this application on
  • 00:15:31
    the server that is created by a system
  • 00:15:33
    administrator okay then there is one
  • 00:15:35
    more position called as a build and
  • 00:15:37
    release engineer okay now we are talking
  • 00:15:40
    about different different terms don't
  • 00:15:41
    worry I'll explain each enter each and
  • 00:15:43
    every term in a very simplified manner
  • 00:15:45
    so that you will not be out of sync so
  • 00:15:48
    the system administrator has created a
  • 00:15:50
    server now the build and release
  • 00:15:51
    engineer what we would do is that once
  • 00:15:54
    the tester this tests this application
  • 00:15:55
    on the server he would promote this
  • 00:15:57
    application onto the next level so
  • 00:16:00
    either that level can be a production
  • 00:16:01
    level or that level can be a
  • 00:16:04
    pre-production or somebody also called
  • 00:16:06
    as staging environment
  • 00:16:08
    so again once this application is well
  • 00:16:11
    tested on the pre-prod this build and
  • 00:16:13
    release engineer would take forward uh
  • 00:16:15
    to the customer that would be on the
  • 00:16:17
    production server okay so these are the
  • 00:16:20
    different processes that used to be
  • 00:16:22
    involved so let me try to simplify this
  • 00:16:24
    in an easy manner okay because we are
  • 00:16:27
    talking uh quickly you might lose me
  • 00:16:29
    somewhere so that I would try to explain
  • 00:16:31
    in a simplified manner what are the
  • 00:16:34
    different terms that we called one is
  • 00:16:36
    system administrator
  • 00:16:39
    okay now the other thing that we also
  • 00:16:42
    talked about is build and release
  • 00:16:44
    engineer also there are some kind of
  • 00:16:47
    people called server administrators
  • 00:16:52
    okay so for one simple process all that
  • 00:16:55
    we are talking is before 10 years okay
  • 00:16:59
    so all that I am explaining is before 10
  • 00:17:01
    years so for one simple process what was
  • 00:17:04
    the process the end idea was to deliver
  • 00:17:07
    this application from developer laptop
  • 00:17:10
    to
  • 00:17:12
    customer
  • 00:17:15
    there were these three different roles
  • 00:17:18
    that were involved okay so why there
  • 00:17:20
    were what were we developing application
  • 00:17:22
    to production
  • 00:17:25
    so what I told for this process there
  • 00:17:27
    were these three people that were
  • 00:17:29
    actively working one is the system
  • 00:17:31
    administrator what was system
  • 00:17:32
    administrator doing he was creating a
  • 00:17:34
    server
  • 00:17:36
    why server is required because you
  • 00:17:38
    cannot test the application on your
  • 00:17:39
    personal laptop right in an organization
  • 00:17:42
    you might say that okay my application
  • 00:17:43
    is working perfectly on my laptop nobody
  • 00:17:46
    is going to listen or nobody is going to
  • 00:17:48
    trust so end of the day you have to test
  • 00:17:50
    it on a server so the system
  • 00:17:52
    administrator used to create a server it
  • 00:17:54
    can be any platform right so before 10
  • 00:17:56
    years there were no uh typically the
  • 00:17:58
    cloud platforms like AWS people were not
  • 00:18:00
    using so people were using platforms
  • 00:18:02
    like VMware okay or openstack so these
  • 00:18:06
    were the things that people were using
  • 00:18:07
    or any other uh you know they used to
  • 00:18:10
    have their own hypervisors to create
  • 00:18:12
    like Zen for creating the servers on
  • 00:18:14
    their bare metals because before 10
  • 00:18:16
    years everything was a bare metal
  • 00:18:18
    so the system administrator created a
  • 00:18:20
    server and then what happened is on the
  • 00:18:22
    server somebody has to install the
  • 00:18:23
    application right because developer has
  • 00:18:25
    created the application on his local and
  • 00:18:27
    he has checked in his code onto SVN or
  • 00:18:31
    CBS or any version control system that
  • 00:18:33
    is a centralized code Repository because
  • 00:18:36
    everybody has to access it so the code
  • 00:18:38
    repository developer has pushed and then
  • 00:18:40
    the build and release engineer so now
  • 00:18:41
    this guy has came into picture what he
  • 00:18:43
    has done he
  • 00:18:45
    deploys
  • 00:18:47
    this application onto the server now to
  • 00:18:50
    deploy this application onto the server
  • 00:18:52
    there has to be a application server on
  • 00:18:55
    This Server right so application server
  • 00:18:57
    is the one that holds the application
  • 00:18:59
    onto the server so the server
  • 00:19:01
    administrator used to create this app
  • 00:19:03
    server okay what is this called app
  • 00:19:05
    server
  • 00:19:07
    so because multiple parties were
  • 00:19:10
    involved now further understanding
  • 00:19:12
    purpose I just uh explained all of these
  • 00:19:14
    rules so in a real world scenario before
  • 00:19:16
    10 years there were other roles as well
  • 00:19:18
    so even if you take these three roles
  • 00:19:20
    first simply delivering the application
  • 00:19:22
    from your personal laptop or from the
  • 00:19:25
    developer laptop onto the production
  • 00:19:27
    server what was happening it was
  • 00:19:29
    involving system administrators it was
  • 00:19:31
    involving build and release engineers
  • 00:19:33
    and it was also involving
  • 00:19:36
    server administrator so the entire
  • 00:19:38
    process was taking for example 10 days
  • 00:19:41
    okay so the devops or the word of devops
  • 00:19:45
    has emerged or evolved because of this
  • 00:19:48
    very own reason that is because multiple
  • 00:19:51
    people were involved because all of
  • 00:19:53
    these is a manual effort okay
  • 00:19:57
    so whenever there is a manual effort
  • 00:19:59
    your process will be slow so to automate
  • 00:20:01
    this entire process the word or the
  • 00:20:04
    world of devops has emerged okay is it
  • 00:20:07
    clear so what was happening the system
  • 00:20:10
    administrators build and release
  • 00:20:11
    engineers and the server administrators
  • 00:20:14
    were working closely or working together
  • 00:20:16
    to deliver your application from your
  • 00:20:19
    personal laptop onto your production
  • 00:20:21
    that is for your customer so because
  • 00:20:24
    everything was manual and different
  • 00:20:26
    teams were collaborating the process was
  • 00:20:28
    taking more time for example I said 10
  • 00:20:30
    days but it could be one month two
  • 00:20:32
    months or it could be also five days but
  • 00:20:36
    the entire communication and the entire
  • 00:20:38
    system was not effective this was 10
  • 00:20:41
    years old so now to improve this process
  • 00:20:44
    what has happened everybody has moved to
  • 00:20:46
    a New Concept called devops
  • 00:20:49
    no I underst no I hope things are clear
  • 00:20:52
    okay so why devops has evolved devops
  • 00:20:55
    has evolved for this very own reason
  • 00:20:58
    that is
  • 00:20:59
    to improve the process of delivery so
  • 00:21:03
    that is something that I am explaining I
  • 00:21:05
    mean that I explained you in the second
  • 00:21:06
    slide okay so devops is a culture why is
  • 00:21:09
    it a culture because unlike the previous
  • 00:21:12
    uh times unlike 10 years old there were
  • 00:21:15
    no Mal there there are no multiple teams
  • 00:21:17
    now so previously there are multiple
  • 00:21:19
    teams but now there is only one single
  • 00:21:20
    team so that's why it has to be a
  • 00:21:22
    culture or it has to be a you know a way
  • 00:21:24
    of working
  • 00:21:26
    because as a devops internet tomorrow
  • 00:21:28
    there might be a new tool that improves
  • 00:21:29
    your efficiency so you have to adapt to
  • 00:21:31
    it or you know you might have to uh
  • 00:21:34
    pivot or take a
  • 00:21:36
    change in the process of your working
  • 00:21:38
    and if it improves your efficiency
  • 00:21:41
    somebody comes like your CTO game and
  • 00:21:43
    said that okay we are using this Tool uh
  • 00:21:45
    if you introduce the other tool that we
  • 00:21:47
    are not using our improv the our
  • 00:21:49
    efficiency will be improved as a devops
  • 00:21:51
    engineer you have to have that mindset
  • 00:21:53
    to adopt to the new tool or as a devops
  • 00:21:56
    engineer it's a culture that you are
  • 00:21:58
    building in your organization so that's
  • 00:21:59
    why we say devops is a culture that
  • 00:22:02
    improves the delivery process by
  • 00:22:04
    following all of these things that I
  • 00:22:07
    have explained by adopting to the
  • 00:22:09
    automation by ensuring that there is a
  • 00:22:12
    quality in your application by ensuring
  • 00:22:14
    that you are continuously monitoring in
  • 00:22:16
    such cases like you know there can be a
  • 00:22:18
    failure or there can be something that
  • 00:22:21
    is not working as expected so that's why
  • 00:22:23
    you also have to have monitoring and
  • 00:22:25
    finally you have to continuously test
  • 00:22:27
    your application by involving all of
  • 00:22:28
    these things you improve the efficiency
  • 00:22:31
    of your organization and that is the
  • 00:22:34
    role of devops engineer
  • 00:22:36
    I hope the things are clear so now you
  • 00:22:40
    understood what is devops why devops
  • 00:22:42
    right now the next thing that we would
  • 00:22:44
    learn here is how to introduce yourself
  • 00:22:46
    as a devops engineer so I've seen many
  • 00:22:49
    people fail here okay because even when
  • 00:22:51
    I'm taking some interviews uh when I ask
  • 00:22:54
    people like
  • 00:22:56
    how like you know tell me about your uh
  • 00:22:58
    day to day activities or you know uh
  • 00:23:00
    introduce about yourself what happens is
  • 00:23:02
    people uh tend to not explain everything
  • 00:23:04
    or you know uh sometimes people have an
  • 00:23:07
    opinion that uh I should only be
  • 00:23:09
    explaining about myself in one or two
  • 00:23:10
    minutes no there is nothing like that
  • 00:23:12
    okay whenever let's say you have
  • 00:23:14
    something unique or you know you feel
  • 00:23:17
    that you need more time like not in one
  • 00:23:19
    to one to two minutes you can explain
  • 00:23:20
    about yourself take your own time that's
  • 00:23:22
    fine if you want to explain about
  • 00:23:23
    yourself or if you want to explain what
  • 00:23:25
    you are doing in a day-to-day uh basis
  • 00:23:28
    that's totally fine if you take more
  • 00:23:30
    time while explaining yourself but
  • 00:23:33
    to explain
  • 00:23:34
    or to introduce about yourself what you
  • 00:23:36
    can simply say is that you know I am
  • 00:23:38
    working as a devops engineer that is for
  • 00:23:40
    sure from past
  • 00:23:43
    any number of years that you want to put
  • 00:23:45
    like you know let's say you want to you
  • 00:23:47
    are working as a devops engineer from
  • 00:23:48
    past four to five years because you know
  • 00:23:50
    you cannot say that I am working as a
  • 00:23:51
    devops engineer from last 10 years
  • 00:23:53
    because devops itself was around like
  • 00:23:55
    you know uh from last 10 years and it
  • 00:23:58
    has been very popular from last seven to
  • 00:23:59
    eight years so like if you say our
  • 00:24:01
    organization has adopted devops 10 years
  • 00:24:03
    back then interviewer will lose you at
  • 00:24:06
    that point itself because that's not the
  • 00:24:07
    truth so what you have to say is I I am
  • 00:24:10
    a devops engineer I have overall five to
  • 00:24:13
    six years of experience four to five
  • 00:24:14
    years of experience in devops and before
  • 00:24:16
    to that I was working as a system admin
  • 00:24:19
    or people say that I was working as a
  • 00:24:21
    build and release engineer or people
  • 00:24:23
    also say that I was working as a server
  • 00:24:25
    administrator it is up to you okay and
  • 00:24:28
    even if you are coming from other
  • 00:24:29
    backgrounds like you might be a Java
  • 00:24:31
    developer or you might be a python
  • 00:24:32
    developer or you might be a simply
  • 00:24:34
    automation engineer you can also say all
  • 00:24:36
    of those things okay but always try to
  • 00:24:38
    put your previous experience also in
  • 00:24:41
    place if you are a fresher you don't
  • 00:24:42
    have to worry about all of these things
  • 00:24:43
    you can simply say you know I just
  • 00:24:46
    started working as a devops engineer I
  • 00:24:47
    was passionate about learning devops or
  • 00:24:49
    all of those things but if you are a
  • 00:24:51
    seasoned uh software engineer or if you
  • 00:24:53
    have experience in devops oh sorry if
  • 00:24:55
    you have previous experience always
  • 00:24:57
    mention your current experience in
  • 00:24:58
    devops and also try to put whatever
  • 00:25:00
    you're doing previously because that is
  • 00:25:03
    really important for somebody to
  • 00:25:04
    understand from which background are you
  • 00:25:06
    coming into devops
  • 00:25:07
    okay like if you are a system
  • 00:25:09
    administrator and if you are just
  • 00:25:10
    switching your career to devops as an
  • 00:25:12
    interviewer I can correlate and
  • 00:25:14
    understand okay he has some experience
  • 00:25:16
    in servers and uh sorry servers and
  • 00:25:19
    administrating servers so okay he can be
  • 00:25:21
    of this use in my current organization
  • 00:25:24
    like if you are if I am interviewing a
  • 00:25:26
    person and if he has past experience in
  • 00:25:28
    system administrator I can I can think
  • 00:25:30
    of it like okay because we are using AWS
  • 00:25:32
    his experience might be useful for me in
  • 00:25:35
    administrating this AWS servers or he
  • 00:25:37
    can help me in automation or migrating
  • 00:25:40
    my existing uh physical infrastructure
  • 00:25:42
    to uh on-prem sorry Cloud infrastructure
  • 00:25:46
    so I can think of all these things as an
  • 00:25:48
    interviewer so that's why whenever you
  • 00:25:49
    are explaining someone if you have
  • 00:25:51
    experience in something before devops
  • 00:25:53
    always try to put that and don't try
  • 00:25:55
    don't try to try to lie saying that I
  • 00:25:57
    have 10 years of experience and devops
  • 00:25:59
    that is not truth nobody is going to buy
  • 00:26:01
    that argument from you
  • 00:26:03
    okay so once you explain this what you
  • 00:26:05
    are currently also I mean I have four to
  • 00:26:08
    five years of experience in devops I'm
  • 00:26:09
    previously coming from experience of
  • 00:26:11
    system administrator or build and
  • 00:26:12
    release engineer or if you just have
  • 00:26:14
    experience in devops uh for past two to
  • 00:26:16
    three years you can also say that after
  • 00:26:18
    that explain about your roles and
  • 00:26:20
    responsibilities so in the current
  • 00:26:22
    organization I take care of automation
  • 00:26:25
    okay you can say of these things I take
  • 00:26:27
    care of automation I ensure that there
  • 00:26:29
    is a quality uh that I'm maintaining for
  • 00:26:31
    the applications I ensure that I have
  • 00:26:33
    set up continuous monitoring and I have
  • 00:26:37
    automated the testing process into the
  • 00:26:39
    devops lifecycle so this is how you
  • 00:26:42
    introduce yourself and if people are
  • 00:26:45
    looking at uh the tools and Technologies
  • 00:26:47
    like let's say you want to include the
  • 00:26:49
    tools and Technologies uh before even
  • 00:26:51
    before your introduction I mean even
  • 00:26:53
    before you uh Deep dive into your
  • 00:26:55
    interview like during the introduction
  • 00:26:57
    phase people also uh talk about the
  • 00:26:59
    tools and Technologies I don't uh really
  • 00:27:02
    suggest that but if you want to talk
  • 00:27:04
    about the tools and Technologies or the
  • 00:27:05
    interviewer is asking you about the
  • 00:27:07
    tools and Technologies you can say that
  • 00:27:09
    you are working on the uh platforms like
  • 00:27:11
    you know for the CI CD I'm using GitHub
  • 00:27:13
    actions or for the deployment of
  • 00:27:17
    application onto uh container
  • 00:27:18
    orchestration I'm using kubernetes or
  • 00:27:21
    you are using configuration management
  • 00:27:23
    using ansible infrastructure automation
  • 00:27:25
    using terraform you can explain about
  • 00:27:28
    all of those things but for this class
  • 00:27:29
    because I have many audience who are
  • 00:27:31
    just learning devops today and today is
  • 00:27:34
    the day one right so I don't want wanted
  • 00:27:36
    to complicate and you know explain
  • 00:27:40
    the devops definition or the
  • 00:27:41
    introduction of devops using all of
  • 00:27:43
    those aspects so for today you can just
  • 00:27:45
    say these things like explain what is
  • 00:27:48
    your current experience in devops
  • 00:27:49
    explain where what is the background
  • 00:27:51
    that you are coming from and then
  • 00:27:52
    include these key factors that is the
  • 00:27:55
    four pillars of devops that we just
  • 00:27:56
    talked about automation quality
  • 00:27:58
    monitoring and testing so this is how
  • 00:28:00
    you introduce yourself in a devops job
  • 00:28:02
    role
  • 00:28:04
    okay so for today's class I think this
  • 00:28:06
    is more than enough now what you will do
  • 00:28:08
    is because you understood what is devops
  • 00:28:10
    y develops just Google around try to
  • 00:28:13
    understand what is devops like you know
  • 00:28:15
    you get hundreds of blogs uh most of the
  • 00:28:17
    times you know uh these are the things
  • 00:28:19
    that would be repeated like the poor
  • 00:28:21
    four pillars or options the five pillars
  • 00:28:23
    of devops so because you completed
  • 00:28:26
    watching this video now if you Google
  • 00:28:28
    around you might find some new things
  • 00:28:29
    like you know you can explore those new
  • 00:28:31
    things uh but if you have any questions
  • 00:28:33
    you can also post them in the comment
  • 00:28:34
    section so that you know uh let's say
  • 00:28:36
    you found something new in devops in the
  • 00:28:38
    definition of devops you can put that in
  • 00:28:40
    the comment section saying that okay
  • 00:28:41
    Abhishek I Googled around I found this
  • 00:28:43
    thing how do you think about this should
  • 00:28:45
    also include this in my uh introduction
  • 00:28:47
    we can discuss that and I can also if I
  • 00:28:50
    find that interesting I can also talk
  • 00:28:52
    about that in my uh next video
  • 00:28:54
    okay so I hope you found this video uh
  • 00:28:58
    useful so one thing that I would request
  • 00:28:59
    everybody is we are going to do this
  • 00:29:01
    like 40 days of devops classes from day
  • 00:29:04
    one to day 40. I've already explained in
  • 00:29:06
    my previous videos what is the course
  • 00:29:08
    curriculum what is the syllabus and what
  • 00:29:10
    are we going to talk day by day basis so
  • 00:29:12
    if you haven't watched the previous
  • 00:29:13
    videos go to those videos watch them
  • 00:29:15
    first so that you understand what is the
  • 00:29:17
    way of explanation or what is the
  • 00:29:19
    process that I'm going to follow in this
  • 00:29:21
    35 40 or 45 days of devops course
  • 00:29:24
    and finally don't forget to subscribe my
  • 00:29:27
    channel if you haven't subscribed and if
  • 00:29:29
    you have any friends who are looking to
  • 00:29:31
    learn devops please try to share this
  • 00:29:34
    video with larger audience because that
  • 00:29:36
    is our end goal the whole purpose of
  • 00:29:37
    keeping this course free is somebody who
  • 00:29:41
    is interested in devops will be
  • 00:29:43
    benefited out of this free devops course
  • 00:29:44
    if they don't want to uh if they don't
  • 00:29:46
    if they cannot afford to pay uh for a
  • 00:29:49
    paid course so it should be useful for
  • 00:29:52
    everybody to learn devops
  • 00:29:54
    okay so I hope you like the video this
  • 00:29:56
    is day one and tomorrow we'll come up
  • 00:29:59
    with day two where we'll be talking
  • 00:30:00
    about software development life cycle
  • 00:30:02
    and what is the role of devops in
  • 00:30:04
    software developer lifecycle and also
  • 00:30:06
    we'll do a precap of what we learned
  • 00:30:08
    today so that you will be in async right
  • 00:30:11
    because before we go to day two we'll
  • 00:30:13
    just quickly recap what we have learned
  • 00:30:16
    uh on day two uh sorry on day one and uh
  • 00:30:19
    if there were any questions on the
  • 00:30:21
    comment section that I uh find or that I
  • 00:30:24
    feel that I have to take up so that
  • 00:30:26
    everybody will be benefited by picking
  • 00:30:29
    up that question I'll also do that okay
  • 00:30:32
    so I'll see in the next video thank you
  • 00:30:35
    so much take care bye
Etiquetas
  • DevOps
  • introduction
  • course
  • application delivery
  • automation
  • quality assurance
  • monitoring
  • testing
  • interview tips
  • software development