Unlock the power of open source contact management for HighTech

How to create outlook signature

hi Surya good morning good morning hope we are doing good yeah I just reviewed a CD it's look really good uh could you please tell about yourself first of all uh thanks for giving this opportunity uh so I'm ready you got to work with you uh in your company uh so yeah about me as you said my name Surya uh Surya prakash full name okay so I'm having totally somewhere around the uh eight years of career experience is that APR right uh last you know three years I'm being with this uh devops industry also Cloud okay so this is what you know about my overall experience and things and stuff so right now we are supporting for a client basically who located in India okay so parallel right this client also located in Singapore as well we are the company who's taking care of their end-to-end automation but all their uh software related activity and infrastructure and any sort of you know devops related work intern we are taking care of it in my team right uh close to we have around you know 20 uh uh eight members star we are coming in the rotational shift we have a service now as a ticketing Tool uh so each shift right we will have a closely you know seven members will be there okay we have a heat shift we have a shift lead currently I am playing in the role of shift lead okay so in my shift whatever the activity and task comes right it will get created on service now I used to assign that you know task to each of my members almost six members will be the admissions so five to six member so we'll be assigning the task the task are somewhere you know relate to it it could be related to Cloud could be related to any activity in devops okay sometimes we used to write a code sometime we need to work on pipelines sometimes we need to you know uh you know manage or we need to work on a pull request information control and you know we have to fix any you know error when customer executes any pipeline right if they found any issues or if they face any issues uh we have to take responsibility of fixing those issues and uh if if they have any new automation we need to work on the plan and we need to propose the solution to the client and will involve in change activities as well okay so this is what you know overall about my day-to-day activity uh so yeah uh this is what pretty much about myself and my background okay so yeah so let's move on the coastins what do you know about devops uh devops almost this is what pretty much you know Hereafter we can say because wherever if we go everything becoming automation today uh so instead of doing you know anything manually made which requires lots of human effort and lots of time consumption process uh so it could be enough possibility of human errors and uh delaying in delivering any sort of products all those things you know which involves when come to devops right and now nowadays you know almost if you go any environment any project devops player key role right so development comes operations where we have an option for automating the manual step and we can work with any pipeline we can work with Version Control we can you know involve you know continuous integration continuous delivery and uh we have you know uh different way of you know delivering our product and uh super fast the process of our product so you know everything you know we we are you know literally by doing automation or all the stuff literally we are reducing the number of head counts in the project so it saves time which gives you more productivity to our project right and uh this overall right uh that if you go any you know even infrastructure side also uh even if you are belongs to on purposes or Cloud yeah mostly everybody today into cloud cloud services itself they have started providing devops related tools and services uh today everything becoming open source day by day in devops so that's all put together right uh that is what you know current generation is all about even upcoming generation totally all depends on devops the so this is what my opinion about devops okay how is devops different from agile methodology yeah so like I could tell devops is kind of a culture in it falls like um I can you know I can uh coordinate with my operation team right where who they are taking care of my platform also I will I'm the developer where I need to work along with the operation teams by the way we put together we'll be working on any sort of automation of the activity which calls you know um devops methodologies basically for you know building the communication with you know client and filling the gaps between the client when they have any requirement as much as possible I need to understand it I need to plan for it I need to work on developing that such application actually so basically adult methodology uh nowhere you know relevant in devops uh it's purely for filling the gaps between the customer and the uh literally end user between developer this is what uh devops is the platform and culture where all these manual efforts are becoming automated and this is the reality where we'll coordinate with operation teams the developers are more efficient in Lenovo coordinating or with the operation team and complete the work as clearly as possible so there won't be any delay and continuously no built-in delivery will you know keeps ghost this is uh how uh you know devops differ from no other methodology and the other stuff okay what is deploy and operate phases in devops uh deployer corporate phases in devops okay so in devops right we have various space okay starting from plan uh in that we have a two common and important we can say one is deploy another one is operate that is what exactly you're looking for coming to deploy right whatever the code we have that literally we are deploying it in our production we are making sure things are getting live so by deploying it right whatever we worked on the implementation whatever we worked on the requirement you know literally we are going to put it on the cloud environment for deploying all right so operate in the sentence once as soon as other things are applications are getting deployed we continues to you know operate it okay so till that you know day-to-day progress and monitoring the things and stuff okay so which all falls under operation related phases and devops so we have you know few more other things as well okay testing and you know plan uh monitoring continuous monitoring all those things are I know uh I know which part of these places uh so this is I believe personally these two things are very much important at deploy and upright basis okay sorry could you please explain any of your live real project with continuous delivery and continuous deployment I mean my real project cicd process you're looking for right okay so when you take any real time you know cacd process where initially we start from you know Version Control for that right we use git in order to implement that so in GitHub we kept all our source code after that you know we have we can go for you know um uh continuous uh delivery in the process we'll go for a build okay and build activity we'll start work on the applications requirement and automation requirement whatever we receive okay after the plan okay based on the plan and we'll work on it here right we have all the build tools we used yeah of course we have a various themes and different different you know application and products we're working on uh some people working on Java based uh activities and we are the persons who works on python oriented applications uh first of all our cicd entire pipeline we deployed it on Jenkins okay so in the Jenkins right we have a plugin we have integrated an home oven for an uh build tool and the solar Cube for you know for testing our uh the you know vulnerability and the other security related things in our code and pipeline so by the way continuous delivery will go up to build stage after that we'll go for deploying uh things and stuff and finally you know and you'll go for execute okay after that we have a testing cycle that will be you know manual testing and automation testing that will be dedicated teams available for that but in the plan of you know in our pipeline itself we have a team for uh testing our codes and uh pipeline so it will be tested by the automation tool we have used some selenium kind of automation tool for testing and stuff and finally we'll release for the production okay so we have also having a stage staging environment first we'll do all these uh cacd activity and things uh you know in the CAE sorry in the staging environment if everything works good then we'll move on to uh production uh this is the process we follow during this process right we do have we use all the most common tools since I said for versioning we use jit git and source code management repos indicator we users right same way we have a Jenkins our platform and we use as ansible okay and then we use a terraform for some infrar related code deployment then we use as a python overall write our pipeline right let's ask a declarative pipeline which we written using Jenkins groovy where where it has multiple stages which involved okay so this is how we made our pipeline this is how we put it in our place in environment okay so what is the role of configuration Management in devops in devops okay so so configuration management we could tell you know many tools that are there but you ask about the role right so when you have a huge systems in place okay of course right when you go for any project even customers will have not many systems and as a developers as a support team or operation team or DB team they'll have a lot many servers for their day-to-day work right for each and everything we cannot do any if we want to perform any patching or any vulnerability fix or anything to be updated or driver update or any agent to be installed across all the platform it's hard to do one by one one by one correct so for that we have a configuration management tool personally when you ask me I have an exposure with the puppet and the ansible okay we are for uh Linux we use a science table for Windows related service we use uh but initially we were using sscm but licensing pattern is very expensive so they switched over to puppet of course I know that uh even ansible also can support Windows also puppet also can support Linux but initially there was you know some licensing part and differentiation due to that I have a personal experience with ansible and puppet all my clients are connected with my uh uh ansible Master server literally it works in the principle of uh agentless okay it works as you use the same port number SSH port number for you know communicating and things and stuff uh we used to write our band civil playbooks uh so if for example I wanted to some patching I wanted to inch on some security update or any security fix okay anything like that I'll write a Playbook and we'll push that I wanted to update any drivers a something my vulnerability file is kind of tool it's detecting some you know our vulnerability I need to update the solution that also I don't want to do through one by one all the servers manually from management plan right answer the Playbook I'll pass that solution to my client I have a group also an ansible we have various group depend upon the role and roles of that respective server through this configuration management tool right we will push that by writing you know all ansible code actually this is what basically uh the role of configuration management devops does also we can integrate this tool with any of our pipeline right so if I wanted to perform anything uh that the required place right the ansible can do their appropriate work so this is what about my understanding on configuration management Tools in devops okay could you please explain any of your love life implementation of configuration management uh yeah live implementation just now as I said I have an exposure we implemented ansible uh we have an answerable Master server uh which you know it's it's it's ubuntu-based server and we have you know close to uh 200 plus uh other systems are available in our Cloud platform all these you know all available in database platforms okay so from I am simple right we used to write a Playbook and if we wanted to know in our environment the purpose what we are doing for patching definitely we use go for um activity right everything we have done it through our Playbook ansible Playbook will do it also we have ansible roles okay so based upon the requirement Dependable requirement we will work on that as well so this is what my experience with uh you know uh configuration management tool in my project okay sorry could you please explain the continuous monitoring of any devops system uh sorry could you please repeat your question okay no problem I will repeat could you please explain the continuous monitoring of any devop system yeah basically a monitoring play a major role once your implementation has been done deployment has been done till Cloud any cloud enormity of course today nobody allowed to go with uh on premises everything happening it on cloud right we have various monitoring systems available so monitoring our you know applications and application Services uh critical servers utilization of those servers and uh that have to be will have a dashboard also if we fail to monitor the dashboard it should trigger the alert through notification either through email emotionally we follow the emails we have a distributor distribution list in our environment I told you right each shift we have a size six all numbers will be there all of them should be part of that distribution list uh we have a set of the monitoring tool we use you know Nigel is as a monitoring tool and the neural link we are using New link is the played one so we'll go for only the critical resources Open Source One made applies apart from that the AWS itself we have a cloud watch monitoring system available that also input monitoring things are now and I enabled uh in the yeah uh Team right they are planning to replace my uh new release with uh sensu because which is more you know efficient in terms of monitoring the disk of each server and the service of each server and application Services of each server so it's more efficient and user friendly and easy to set up as well and lightweight due to all these reasons right they are in the plan of migration but it will not come now it will take you know another quarter or you know six months later they may the talk is going on by the way the importance of you know monitoring thing is penalty ensure it's not only about developing the product or setting up the pipeline and making sure the product is coming up you need to keep monitor it when there is outage when there's any problem and the service gets started when there's a over utilization of the resources then it is you know more people are accessing it we have to continuously you know make sure the service is always accessible by the end user actually for that monitoring takes a major place in any devops system okay could you please explain the term infrastructures a code uh okay so coming to uh infrastructure code yeah we can say whatever the platform we have okay uh that are you know uh obviously today we are getting it in on top of Cloud only it should be from any AWS that I should not GCB the required networking things are required and observers like connectivity of the security groups kind of thing and the volumes uh disk storage no IP addresses whatever that all these should be you know that and get it getting it from the cloud environment only correct so when you have a uh infrastructure code we don't want to provision any resources manually okay we'll be running it do it through uh interest code tools example we can take we Implement uh terraform in our environment of course in AWS we have a uh you know uh this one cloud formation we have and I'm sure we have um Azure resource arm Azure resource manager is there likewise right we have a terraform uh since we really go with the terraform it's open source and the platform independent we can use for Azure gcp you know error base whatever we want so we have you know introduced the terraform in our project earlier it was manual stuff now we all we are managing through terraform only even in one of our pipeline also we made it for terraform for resource build and things and stuff so it creates all the resources and manage the state files feature I wanted to you know create any resource understanding resource also it's also been manageable from terraform okay so we are not going to create a resources through manually entire infrastructure right we have a template through the template and we will you know in single shot single go we will go and implement it so that is what you know infrastructure is a code okay how you manages the gaussian control of your source code in your platform okay as I said right the question control is a key part and one of the very basic and important part of every environment because people when do their you know the codes right they will have a multiple uh you know branches in our git Hub so initially we won't allow any of the developer to work directly on the master Branch so we have a staging or we have a sub Branch Testing things will be there initially they'll now clone their staging part and they will start the work on that staging but the activity has been done right they will you know create a pull request and no one directly will not attach our access into our Master Branch we will integrate it okay finally after reviewing all this thing we will integrate it so that's where each and every uh you know push we need to have a proper comment so even anything you know goes wrong also we have a backup I mean what changes have been done of previous uh history of uh different push from different developer we'll go through that and it will be easy for us to track the changes so by the way right we have managers and of course we give you know a very high priority for all our version control system in our project okay how to store the sensitive data in any devops activities so sensitive that I mean any critical that I would need to say yes okay so of course when we perform any activity that is definitely going to work in the definitely for customers data only so we need to give always you know a high priority to customer data because if everything goes you know wrong or somebody you know or got the data from our site it'll be an impact to our project as well as customers so what we do right all the data we kept it in the encrypted environmentally we won't keep the data in unencrypted environment we have a policy sap policy and we have customized policy applied as per our organization standard whatever the data we handle that should be into the environment where it encrypted okay that is by default and if we are playing with any private key of customers or if you are playing with any credential okay whatever we have a terraform Vault available okay and um in AWS also we have a service for you know keeping our security related things sorry I couldn't recollect that service name uh okay we use the wall kind of data we used to encrypt our data okay so we'll not use the credential or dollars plain text we'll never hard code anything in our script okay so we are following this as a best practices uh whatever the data we kept it in the world right we'll pass that value as a reference only we'll never go with plain text so we'll never keep any credential in our uh yes I mean they see in GitHub and all uh okay those are you know very crucial the handles we have our security team available who used to inspect all our data always we have a dedicated team to monitor all the security of our code and vulnerability of anything or any any any possibility of any anything you know data loss or whatever the security people keeps you know keep eye on all over activities by the way we'll ensure our datas are secured in devops activity so this is what you know we gives importance to our environment okay so yeah so all the explanations are really good I will handle the data to HR team they will get back to you thank you yeah thank you thanks for your time