AWS DEVOPS BY NARESH SIR | DEVOPS FULL COURSE | JOYATRES |

this conference will now be recorded yeah coming to here this is about our devops life cycle okay I will give you more info about this after some time and first of all we need to understand about what is the devops roles and responsibilities what devops engineer is going to be working within the organization okay he is going to be working like as admin activities like even other AWS Cloud engineer okay that is the AWS activities that are going to be working they need to be given some permissions in AWS side they are going to be working like as admin guy as well and he's going to be working on the it might be Azure also it might be some Linux Mission also on-premise servers also it might be whatever it is some admin activities we are going to be happening here we are going to be done some installations also in this particular admin activities and next one coming to this development we are going to be done some different different developments okay I need to write some of these Docker files who is going to be writing these Docker files as a devops okay we need to write some Docker files some of the companies some developers also going to be writing okay it's based on their project show requirement they are going to be writing their own Docker files or it might be devops guys need to be right from Docker files or else we need to write some uh we need to write some pipelines as well we need to write some ansible by ml files as well RS we need to write terraforms also terraform scripts to automate our infrastructure like we need to be done some development activities as well okay this is the one position and automation engineer okay there is one more position came into picture that is automation engineer nowadays most of most of the guys are going to be looking for automation uh in their projects because they don't want to do manual each and every time same activity how many times you can be done manually because of that reason we are going to automate our process by using some shell scripts or it might be python or it might be terraform or it might be hands bar it might be groovy whatever it is we have a lot of things are there to automate our process okay for this we are going to be working like as automation side as well and then we are going to be working like as a Department engineer employment activities also okay we are going to be deploying our applications developers are not going to be done in a develop developers are not going to be deploying any applications as it devops guys we need to deploy the applications okay that particular deployment is going to be working under the site reliable to Engineers those guys are going to bid on the deployments they are going to be releasing some of the religious based on the requirements based on the uh their project uh structure how they are going to be following okay and what basis they're going to be deploying their applications a Sprint wise how many deployments they are going to be done those things are coming to this particular deployment activities and fifth one is support okay these support guys support Engineers are going to be supporting this particular deployments what are the requirements are happen they're always going to be monitor that particular applications if they are going to be getting any alerts based on the alerts they need to be work we have different different teams are there like L1 L2 L3 teams are there they are going to be working based on the type of it means single team they are going to be handling different level of works like is how much time they are going to be getting to resolve that particular issue it's based on the timing okay it might be small or it might be big whatever it is it's how any emergency what is their priority we can call like as a priority how much priority we are going to be giving to this particular support activities for that particular error for that particular issue in production whenever you are going to be deploying your applications into outside world customers are going to be using our product like Flipkart you can take some Flipkart application is there these particular Flipkart application is going to be using by lot of people within the world okay it's not about the country also it's about the world around the world most of the guys are going to be using Flipkart application to purchase their products so if this particular product is going to be done what will be happen customers will be reduced am I correct in that case if you don't want to miss the customers if any product is not working fine okay some of the applications are not working fine customers don't like to they won't like to use that particular applications so these particular application should be up and running even any small issue is going to be happening they support guys go into picture and they're going to be resolving the issues based on the priority okay it's like it's a high medium and low priorities are there based on the priorities they're going to be working okay even we have the in our I.T team in our organizations we have some it team is there those guys are going to be involving these particular areas okay even devops side also where what are the deployment you have done that particular deployment uh need to be supported by devopsky itself other guys doesn't have much idea about the deployment activities there those guys doesn't know about any issues are coming within the devops activities even this support guys also should understand about even these guys not required to learn much but these guys need to understand about or what is the exact issues why it's going to be happening okay these are the major roles and responsibilities are going to be involving for devops guys first one is the admin activities okay whenever you join the organizations you are going to be getting some username and passwords right who is going to be giving that particular username and passwords there is admin team is there those guys are going to be those guys are going to be providing the username and passwords here these admin activities stay French company or admin activities are differentiable organizations once you join the organizations they will just give the username and password with uh it's like an ldap will be there that particular activities that particular access they will provide but whenever you are going to be working in a project for project you need more access like git access I required I required some Nexus access I required some AWS access okay I require some kubernetes access these particular accesses are going to be providing by admin guys and these admin guys it means devops guys only going to be involving to give the permissions to them and these guys are going to be involving to install the packages within the servers what are the servers you are going to be using within the servers they are going to be installing the packages okay and these guys are going to be involved in the development and Automation and deployment and support activities as well okay these are the major roles are going to be involving for devops guys is this clear guys any questions I hope everyone is clear right if you have any questions please let me know you you can unmute yourself and you can talk with me we can discuss on that particular area as well okay don't be calm if you face any issues if you're not understanding anything yeah and coming to roles uh coming to this life cycle okay what are the tools are going to be using within this particular life cycle stage by stage we are going to be using different tools as per our discussion plan is not going to be taking much this particular plan is not going to be involving by devops guys only it's a based on the project devops guys may or may not involved in this particular plan and next code onwards we are going to be working within the code onwards okay planning is going to be happening at the architect level or there is architect meeting is going to be happening every week or it might be Sprint wise they are going to be creating one meeting in that particular plan they are going to be involving in this particular activities okay and next one is a code what is meant by code here now you can come here in our organizations okay it's a project in the sense they're not going to be working one or two members we have a lot of members are going to be working right within the project now might be developers developers are there developers in the sense for my four members might be exist okay and then testing team is there testing team we have two members might be or it might be one member and we have some deployment or devops okay we can check these guys also might be two members or one member okay some some companies they are going to be taking four members also it's based on the project land how many members are there in their project okay how how much big the uh how much big that particular project is belongs to based on that this particular members are going to be increasing okay by generally we are going to be taking this much my team size is also 12 members are there 12 to yeah 12 members and we are going to be supporting nearly five teams okay they are going to be working in different environments okay so we 12 members are going to be working in different environments and we are going to be helping them to resolve the issues as well as we are going to be doing some development activities and we are going to be working like as admin activities okay and we are going to be supporting we are doing some support activities as well and we are doing some deployments as well and we are doing some automations as well every role we are going to be involving in our organizations but it's not a each and every role is going to be done by devops Guy some companies it's based on the company and project devops case rules will be different okay there is a cloud admin is there those guys only do admin activities like these type of activities are going to be involving okay so based on their roles and responsibilities within the project they are going to be working on different different tools now here these four members where these particular guys are going to be writing their code in their laptops from that particular laptop how these guys are going to be sharing with others how the code is going to be sharing with others this particular code is going to be sharing with others by using some Central Point now I am going to be giving some paint I'm just opening my paint in our sessions we are going to be seeing in a pictorial manner each and everything so that you can get clarity about how what is the tools and Technologies now I have two developers are there okay this is a one developer you can think okay this is one developer this is the second developer and third developer like each and every developer they are going to be working in their laptop itself okay here this guy is going to be using one laptop it's a development in the sense they're not going to be done anywhere they're going to be done in the their laptop itself okay and these guys are going to be working on this laptop too and this guy is going to be working on the laptop 3. now all these three guys are going to be working on a single project okay all these three guys are going to be working on single project so this particular project is having different modules module one module two module 3 like these guys are going to be working on different different modules under the project so first guy might be work on the first module only second guy is going to be working on the second module and third day is going to be working on the second third module okay there is a dependencies also there this particular first module code is going to be using by second module it means what is the code is going to be writing by developer one that particular code we have to get by developer 2 as well otherwise he can't able to start his work so how this guy is going to be sharing his code to a developer too every day it's not possible to share manually manually we can share there is no issue directly these guys can share their code too other guy that is but that is not a good thing every time even every sometimes often every hour and over you want to share your code that is not possible manually instead of that better we can keep somewhere in remote locations like you are going to be storing your images in the Google drive or somewhere right how you are going to be keeping and how you are going to be sharing with others whenever you are at the moment you are going to be uploading your images in Google Drive at the same time it will it will uh See by some other guys okay it's the same approach here as well we are going to be keeping our code somewhere in the remote location that is a source code management we can call Source Code management at this place we are going to be keeping our code this guy is going to be keeping their code here and this guy is also going to be keeping their code here and this guy is also going to be keeping their code here okay anyone is required some code for which is written by developer one this code will be exist here that particular code can get by developer 2. okay like there is a facility is going to be providing by source code management what are the tools that comes under this particular source code management okay here in this code we are going to be using source code management right this source code management it means what is the source of code whenever you are going to be deploying any Flipkart application whatever it is that particular application if you want to see okay if you want to how this one is going to be working behind developers return some code that particular code is going to be managing with some tools either it might be GitHub or it might be gitlab or it might be Azure reports or it might be code commit okay like we have different different tools are there our bit bucket is there or it might be SVN is there like we have different tools are there we can use any one of the tool but this is not going to be deciding by us it's based on project architecture if we have to use that particular source code management only okay this is not going to be deciding by us within the company this will be decide by architect that is architecture will be there each and every project they have their own architecture and in that it will be decide and we can use that particular source code management even if you understood about one source code management we can easily easily work with other source code management as well okay everything is diff everything is a common convert the commands are going to be using is common okay it will be look likes if you are going to be learning one thing it's a similar uh other tools also will be similar okay even interview also they might ask which particular source code management you have worked if you say git like GitHub they might ask questions on the GitHub itself okay it's not required to learn each and every source code management you can ask them here we can discuss about gitlab and GitHub as well both we can discuss okay I will show you how to install the gitlab and how we can push our code to gitlab as well I will show this particular part as well okay and I'm going to be giving my GitHub details we can go and see GitHub slash240 this is my GitHub I'm going to be keeping a lot of content here we can say nearly 155 repositories are there in these repositories I have some different different applications are there there is a springboard application is there this is belongs to Java related application okay Java code I have kept here and I'm going to be deploying the applications like this okay and if you comes to node.js we can go and search for node.js I have written

some node.js application as well this is my node.js application and python application I'm going to be showing python okay it's not required to write by developer devops case developers they are going to be writing the code what is the code is written by developers they are going to be keeping in the source code management like this okay they will keep the code like this home.py like that they will write and they will keep here okay I also got the information from them only this is not written by me but I have some idea about these things so I have done my own okay I don't have any developers here to write this particular code so I get a code from the Google somewhere I just kept in my gear repositories I'm going to be showing within our classes okay so this is about the source code management where they are going to be keeping it's nothing but code as per our discussion first one is the code okay here we are going to be using these many tools any one tool is fine it's not required to learn each and every two also is this clear guys yes yes yeah next one is the build part okay so what is the code is written by Developers okay if you give this particular code to deployment chip we have as per our discussion we have different teams are there right developers return their code if you give this particular to uh this particular code to devops Guys these guys doesn't know anything okay about the development these guys doesn't know anything if you give simply if you give this particular code by mistake this devops guys are deployment team they might do some changes like they might kept some dots okay unfortunately it happened they are not going to be done man uh intentionally something is done automatically just they are going to be keeping some dot or something okay in that case what will be happen if they're going to be keeping their code if they're going to be keeping their code if they are going to be giving their code to devops team they might have some changes by devops team that particular application will not work even one dot is going to be happening also it won't work properly okay so because of that reason we are not going to be sharing the code to devops case or it might be we can share uh we are not going to be done we are not going to be giving go to deployment teams but develop stream we are going to we are not going to be giving code to devops deployment teams we just give some file okay it's a similar we can deploy the applications with the code directly or else we can create single file that particular file can converge that particular file can deploy in deployment environment okay we can deploy this particular application with single file that type of file we can go on create how we are going to be creating even that particular file also that particular file can't be readable edible can't be editable okay and we editable these type of environment we are going to be creating okay this time of file this type of file we are going to be creating how we are going to be creating this particular file okay it's a based on the languages we have different different languages are there like Java is there and we have some node.js is there and we have some

python is there and we have some go language there okay like we have different different languages are there if you go with Java here we are going to be writing these developers are going to be writing spring boot applications here we are using two tools one is a maven and second one is a grad okay any one tool we need to be used based on the type of language they are going to be writing and here which type of language it's a developers which type of language they are going to be writing based on that we are going to be using either Maven or Gradle okay I will give you full info how which particular tool we are going to be using here naresh I have one doubt yeah please yeah how we will identify that the programmer will write the code on particular language like if we know you can use Maven and Gradle if the developer use node.js how you identify that that's the based on the extensions are there right I'm going to be showing some example here we can see at the extensions of p y what is meant by this if it is there is extension like as a DOT JS will be there okay and if you comes to this particular springboard application to Springwood application is having this particular folder structure and it's having problem.xml okay this is belongs to Maven related if it is a Gradle there is a build.gradle will be there with that we

can go and find out whether it's a webinar Gradle also RS you can check with developer also there is no issue directly we can connect with developers and we can get how you guys are going to be building the packages which particular command you guys are going to be using what are the insta what we need to be installed if I want to run that particular command directly you can connect with them and you can check with them there is no issue on that okay this is about mavenous Gradle it's a springboard application and next one is node.js application here we are going to be using npm with this we are going to be building single file that particular file can use for deployment here python we are going to be using python itself oh and we are going to be using go okay these are the tools we are going to be using like we have some rear gears angularjs are there and we have some dot net is there each and every tool we are going to be using which and every language we are going to be using different different Tools in our sessions we are going to be discussing all the tools which are important for us okay so that you will get some clarity I will show you each and every tool how it's going to be working manually I will show in a containerization also everything we can see one by one okay this is comes under build part is this clear by everyone guys is this clear yes yeah next one is test okay X1 is test within this particular test what will be happen what is the code is written by developer right this particular code we need to test whether it's working fine or not any duplicates are there or not any syntax issues are there or not we need to protest each and everything okay we need how we are going to be testing duplicate lines are there or not because these developers they are going to be writing thousands of lines like ten thousands they might write sometimes they are going to be writing more than that also everything is not possible to do manually right to find out the duplicates or it might be syntax issues everything is not possible to check those things are going to be checking with some tools we can use sonar Cube or J unit okay like we can use different different tools in our sessions we are going to be discussing about sonar cube with this we are going to be checking code coverage okay this particular code is having any vulnerable tests are there any duplications are there those things we are going to be checking with this particular sonar Cube this one also we are going to be discussing in our sessions okay once testing is done we need to deploy your applications okay first I will show I will explain about the deployment then we can go with release now deployment where you are going to be deploying your applications we are going to be replying our applications in some images guys can you I'm getting some extra noise yeah Jenkins we are not going to be deploying applications in Jenkins don't think Jenkins is a deployment tool okay it's a release tool that particular tool is going to be using for cacd only help with the help of cacd we are going to be deploying your applications in some environment okay I will give you some emails for this now these developers they are going to be writing their code okay this is my developer once developer written their code and they are going to be keeping inside the source code management and then we are going to be some guys they are going to be testing first then going we will be building and then we are going to be deploying your applications okay you can see here this is my source code management and then as and then build it's a based on type of test we are going to be using either here or here and then we are going to be deploying your applications are going to be using one by one we can see so that you can get much clarity about your devops activities this everything will be done by developer only so sorry devops guys only just focus on this and then once deployment is done one more activity is there that is a monitor okay monitories also came into picture so I'm doing manually first okay I'm doing all these things manually how you are going to be done this One Direction monitor what are the activities will come like yeah I will tell you I will tell one by one okay okay first you can focus on this up to the deployment then we can see about the monitor also okay okay yeah here whenever the developer is going to be writing their code developer whenever he is going to be writing their code he's going to be keeping the code in this particular place at this point his work is done developer won't come into picture again and again now onwards as it devops guys you need to be done the remaining activities like testing and we need to be building and we need to be deploying everything okay where you are going to be testing we require some sonar Cube as per our discussion am I correct who is going to be creating the who is going to be setting up this particular sonar Cube as a devops guys we are going to be involving to for installations as well okay as per this you can see we are going to be working like as admin activities so installation is also going to be done by devops guys few guys are going to be working on the installation side also okay once you have this owner Cube only one time activity only it's not required to do again and again sonar Cube setup is only one time activity we need to set up this sonar Cube if it is already there it's not required to set up again okay some companies it may or may not exist if not exist we can go and use now this particular code we are going to be testing here with the sonar Cube then we are going to be building if it is a this particular code might be springboard application okay if it is a spring boot application I am going to be using some tool like as a maven this Maven installation who will be done as a devops case we need to be done this Maven installation also okay where you are going to be installing on top of some server okay this one is also top of server some server we are going to be done and this we are going to be building some packages here what is the package we are going to be getting it might be get our jar or VAR files okay these type of files we are going to be creating this particular files can't be readable can't be readable and where you are going to be deploying your applications I'm not going to be using Jenkins I'm going to be using deployment activities we are going to be done in some environments like either Tom catch or it might be JBoss RS I can use the docker containers or else I can use kubernets or else I can use elastic bean stack or else I can use ECS like we can use different different tools okay we can use any one of these tools we have different tools or more more than this also there I am just giving few tools here these tools are enough to understand about this particular deployments we are going to be creating these environment these are the deployment environments we need to be set up this Tomcat first on top of the Tomcat we are going to be deploying this particular jarr wire files or else we need to be use Docker this particular Docker is going to be building some Docker images and we are going to be creating some containers or else we can go and discuss with kubernetes inside the kubernetes also we can deploy okay any one tool it's not required all the tools any one tool we can use to deploy our applications okay is this clear I hope it's clear right don't worry about that each and everything I will explain how the Fourier four to five years guy is going to be working in our organizations we can learn that much level okay yeah once deployment is done yeah I have my application is there my Flipkart application is there that particular application is deployed properly if something happens customer is getting some issues right customers might get different different issues sometimes it might be slow sometimes it might be different it might give some error I'm unable to pay amounts okay these type of issues need to be checked by our support team okay what is my what might be the reason why it's not going to be uh what why it's not going to be paying the amounts why this particular server is going to be down why it's not going to be why it's uh taking more time to do some payments or it might be streaming whatever it is okay in that case this monitor team they will come into picture and they will check the errors here they are going to be checking the logs of this particular applications or it might be logs of applications or it might be server application server logs okay what type of thing they are going to be using okay that might be applications or it might be servers they are going to be checking the logs okay they're going to be using how they are going to be checking either they can check with the some commands or it might be some tools they can use if you are going to be using from commands it will take longer time to find out the issue instead of that if you are going to be using some tools we can easily find out where the exact issue is going to be happening when this particular error is happen and how we can resolve that particular issue we can easily find out by using this particular tools okay we can monitor this particular applications our servers we can monitor by using some tools called grafana or it might be Prometheus okay these tools and along with this we are going to be discussing about elk elasticse and we are going to be discussing about log stash and it might be kibana why I am going to be giving these many we doesn't know which company is going to be using grafana which company is going to be using kevana if you know minimum one or two tools we can easily understood about other tools as well okay our work is common we need to set up this particular grafana and Prometheus we need to set up this particular elk on top of that we are going to be creating some dashboards as well okay once we have done this one we are going to be creating some dashboards I am going to be giving some example for dashboards as well dashboards of kibana or it might be grafana we can go with grafana so we can get some clarity in these particular images grafana dashboards we can look like this we can see here you guys can understand about this particular image what is going to be happening in this okay I'm just increasing the size of this particular image and we can see at what time this particular spike is down and what time at this particular spike is this particular uh Spike comes up because this particular sleep utilization you can think one one side is a cputalization okay it's if it is a graphical representation we can easily understood about what is going to be happening here okay I will give you some other image which is having CPUs and memories I can go with this I hope query utilizations here we can see one is the login this is related to CPU and this is related to server related okay server CPU says yes this is a memory memory or CPU this is the server CPU says yes okay at what time this particular CPU is increased we can easily find out by using this but if you go with logs it's very difficult to find out at what time this particular CPU is even reaches to 100 or it might be 90 percent so because of that reason we are going to be using this particular tools we can easily find out which particular thing which particular roles we uh it means which particular uh CPU at what time the CPU is going to be giving High okay those things we can find out and what is the reason behind that then we can go and easily find out okay and by using this we are going to be getting some alerts also at what time every time it's not a it's not a good thing to check this particular things also for that we need to get some alarms whenever you are going to be keeping some alarm to your mobiles or it might be males whenever the spike is reaches to 80 percent of CPU your server is reaches to 80 percent you need to get some alarms that type of things we can be set up here itself in the monitoring section we can use one more tool called alerting manager with this alerting manager other thing manager in this particular tool we are going to be alerting okay whenever the CP utilization is high this one is going to be giving some messages to our mails or it might be Splunk or it might be now through mail that it might be mobile also okay this particular alerting manager will give some alerts for us is this clear now about the monitor why is the why the importance of this particular monitor any questions here guys yeah it's clear so what all deployment tools you would be discussing would you discuss all that you have listed there like Tomcat uh Docker Cuban and the CBS yes everything we are going to be discussing even more focus on kubernetes so I'm going to be doing nearly 15 classes I will take on kubernetes itself Docker I will explain three things like as a Docker run Docker compose and occur spam as well okay I would like to explain about the elastic beam stack and do ECS as well so I will give you some examples in my repository this kubernetes is having lot of conductors there with us we can see in kubernetes these many things are there within the single kubernets okay I need to explain about the auto scaling three types of Auto scalings are there HPA VPN cluster Auto scalar and I would like to explain about the backup how we are going to be taking the backup of restore backup and restore of eks and DNS setup and our backs and cluster upgradations and config maps and secrets deployment strategies again three three things are there okay we need to discuss everything because of that reason I'm going to be taking nearly 15 to 20 sessions 20 hours not sessions hours I'm going to be taking on this okay minimum 15 is fine for me I can go and explain about these kubernetes with me of 15 to 20 sessions I will give you advanced concepts like help flux CD get UPS these are the advanced concepts in kubernetes first of all a lot of guys doesn't know about this particular advanced concepts so we are going to be discussing about these Concepts as well in our sessions okay thank you yeah this everything will be done manually right this one I want to automate by using some Jenkins as per our description that is a release here we are going to be using release if it is a one time we can be done manually there is no issue but these developers doesn't know how many times they are going to be update their code am I correct every day they do some changes it's a based on their requirement based on the client requirement one more guy is there is a client this guy is going to be asking some requirements based on the requirements developer they are going to be done some changes and they are going to be once they have done the changes they are going to be keeping under the source code management once the changes are done it should be test automatically it should be billed automatically it should be deployed automatically because developers are there four members are there but here devops case might be less so how we can handle each and everything we need to build an installation we need to bid on admin activities we need to build on deployment activities we need to monitor everything we need to be done in the sense we don't have much time so we need to automate this process how we can go and automate this process we can automate this process by using some cacd tool okay at this place this guy came into picture csct tool is going to be done all these activities this cacd tool we have different different things are there we can use Jenkins as a CID CD tool or GitHub actions we can use our gitla pipelines we can use Azure Pipelines RCA code pipelines in AWS okay or we can use bamboo or team City okay like I can uh like we can discuss so we can see these many tools okay here it's not required to learn each and every tool even one or two tools is fine to understand about the Pipelines how the pipeline is going to be working these we can call like as a pipelines we need to write some pipelines if you understood about one pipeline we can easily understood about other pipelines as well okay here this particular Jenkins is going to be communicate with source code management this one is going to be communicating with sonar Cube and this one is going to be communicate with Maven this one is going to be communicating with deployment team to deploy the applications okay this everything will be done automatically instead of doing manual here I need to run some command okay to clone the command here I need to be done the Clone then if you want to test we can we need to use sonar scanner command this is the maven build command is there ambient clean install okay like we need to use each and every command every time if it is a manual devops can need to be done each and every command I don't want to do manual I want to automate this process by using some tool that is called Jenkins here we are going to be discussing about Jenkins got it and GitHub actions also I will give you I will give you about GitHub actions also how we are going to be writing okay and if you have any Azure account I will explain about the Azure pipelines also how we can write a simple pipeline in this okay like we can go on the see these many tools are there it's a community to company this particular tools might be vary if you know any one of the tool we can easily understood about that particular tool also they will give some time to you to understand about how they are going to be writing okay it's a more than two days two to three days is fine for us to understand about other tools if you already know about One tool okay got it yeah sorry to interpret so are you going to explain about the mountain Tools in depth yeah I'm going to be explaining about the installation setup yeah I'm going to be showing this installation setup and then I'm going to be showing about the how to create the dashboards and all and I will show you how to integrate this alerting manager how we are going to be getting the alerts as well yeah okay thank you yeah okay this is about our devops tools along with this we have some other tools like terraform naresh have covered the project also tag one or two projects for the real time first of all you guys think devops guys they don't have any projects if anyone is saying that project that is just activity okay that is just a some activity only so here my activity is I want to get the code I want to test the code I want to build the code I want to deploy the code okay this is one guy activity okay they are going to be giving some different different activities only sometimes they say that please set up the sonar queue that is your jira story okay they are going to be providing the work within the jira they will they says that please set up this particular sonar Cube and under some ec2 instance under the AWS environment please go and create sonar Cube It's on a single server that is our activity they will provide like touch okay even if you want to show me like as a project this entire thing I will show like as a project itself and I will show you some other projects also I have done recently I have done one project we can go to repository section foreign this is the one project you can think okay this is one activity this is one project to project it will be different I am giving the scenarios real-time scenarios okay for devops guys there is no projects separately we are going to be working on the scenarios okay okay yeah I will give you how the devops guy is going to be working within the organizations I'm saying that okay because of that reason I'm not say I'm not saying that we are we are going to be discussing about the project we are going to be discussing about real time scenarios okay cool yeah and here these installations right this one RK over it might be Maven or it might be something how these particular installations are going to be done every time it's not a good thing to do manual that also we can automate by using some other tools here we are going to be discussing about ansible with this ansible we can automate our configurations okay we are going to be discussing about this particular configurations it means installations we can be done with ansible whenever you are going to be running single command it will automatically done everything okay and we are going to be discussing about terraform this terraform we are going to be using for infrastructure management tool okay this one is going to be using for infrastructure management tool means what are the AWS Services we have we have lot of AWS services are there I'm going to be giving some examples like ec2 instance or it might be load balancers or it might be Auto scaling groups okay or it might be some Lambda functions or it might be some VPC or it might be some IAM or it might be from EB okay this is everything we have a lot of services are there in AWS these services I don't want to do manual okay to create this particular Services is going to be taking longer time because of that reason I don't like to create this particular Services manually I want to automate these Services by using some terraform okay most of the guys most of the companies are looking for terraform who is going to be working on automation side okay as the devops case we need to understand about the terraform scripts how we are going to be writing I will give you from scratch how we can write and how we can use that particular terraform scripts to create this particular resources okay this is about terraform and ansible and either come straight away Services nearly 15 to 20 Services we are going to be discussing in our AWS environment like ec2 L load balancers like we have three types of load balances are there Auto scaling groups are there Lambda VPC IAM EB and we are going to be discussing about eks or ECR we are going to be discussing about ECR eks ECS okay and we are going to be discussing about secret manager like we are going to be using different different services and I'm going to be discussing about S3 and we are going to be discussing about SNS and we are going to be discussing about SPS and we can discuss about it yeah and we can discuss about RDS okay like we can discuss different different Services it might be more than 20 also sometimes it's a 15 to 20 services and we can go and discuss about the API gate base okay like we can discuss uh which particular services are required for devops guys in different projects based on that we are going to be discussing okay we can discuss one or two or two to three projects uh in our sessions so that you can get some clarity how end to end we are going to be done okay is this clear guys any questions any questions from anyone well so what's up with thank you yeah along with this I forgotten about to give this particular to keep somewhere in okay for the future references I'm going to be discussing about Nexus and jfrog Nexus and jfrog this thing also we are going to be discussing okay yeah these are the tools what we are going to be discussing in our sessions okay any questions guys from anyone today we have discussed about devops life cycle and we have discussed about roles and responsibilities okay what are the tools are going to be involving within the within our sessions okay as a devops case what is the what are the tools are going to be using how they are going to be using how extensively they are going to be using how we can reuse that particular tools okay where we can use that particular tool what is the importance of that particular tool everything we can see from each and every role I will explain OK it's not for citrary available to Engineers it's not for development it's not for automation every every position you can you can apply okay in any company they are going to be asking the any position you can apply for that because it's based on the JDS will be different right our work will be different we can apply for any one of the job if you are going to be learning like this even who are working within the organization who those guys also doesn't know these many tools which we are going to be discussing in our sessions okay also I'm going to be providing some some videos as well uh with on regular basis now I'm going to be showing how I'm going to be providing I'm just giving here we can see I'm going to be uploading videos here I'm going to be sharing with Team okay every day we are going to be done some classes these particular classes I'm going to be sharing with you guys for future references whenever you want to understand about some other Concepts it's it will be useful for you okay within the session you might you you might understand few of the things or it might be if you want to listen the class again and again these videos will be helpful for you got it any questions I'm just stop recording if you

2023-02-12 14:50

Other news