 Hi everyone. So deployment automation, deployment automation is something which every organization wants to have Everyone wants to achieve a single click deployment process. So how can you do it? Let me tell you the Requirements that we were having the problem statements we had so we have around eight to nine lobs line of business and Everyone were having their own deployment scripts and few of the lobs were having even Deployments totally manually. So one person sits on server logs into it and Do the changes restart the application then logs into the another server. So it was most of the process was manually So obviously it's not acceptable. How can we do it? totally automated So when we started exploring it We got to know about the Rundeck which is based on basically SS mechanism But it was not suitable for us because we have we are having Windows servers also as a stack So then afterwards we explored M collective. So it's an orchestration tool which comes along with the puppet most of you Have used it. So we are having one client server and thousands of master servers So you can actually push the commands from one client server to all the servers parallely So we are having active MQ as a queuing system. You push the commands It gets queued in the active MQ and all the master servers look at the commands that This particular command is for me or not Then it acts on that command and responds to that active MQ and from active MQ We read that what's the response of that particular command on that particular server? So it's actually based basically parallel deployments happening on So let me show you the deployment dashboard that we are having So this is a deployment dashboard. You can see that we have application projects and all so What we have done is we have a mysql as a backend So we store all the applications all the servers map to it and what all actions we want to trigger to it We have master table defining all the actions and we have another table define mapping application with the actions So what all actions you want to trigger on that particular application? So by selecting that application you can Basically you need to define configuration also So what are the basically containers you have you want to restart on it you define all the actions basically? Let me show you Okay, just leave it so basically when we When we click on the deploy so we are having multiple options deploy a redeploy resume rollback Whenever you click on the deploy option And so it picks up the all the actions from the back end what all actions you want to trigger in serial order And we have integrated it with the F5 using the pie control API We have integrated it with the sentry on to enable or disable notifications that you have configured in so it's totally Just single click you can deploy the changes on thousands of servers parallely in just 15 to 20 minutes and We also implemented the runtime logs. You can see on this It's basically implemented using the web sockets and We have option here to even enable or disable the servers on F5 directly using the pie control API We have given detailed complete detail here server wise But the status of the deployment on particular server if some error comes then also it shows Everything is available on who itself. No need to log into that server and do anything So what person just need to log in and just click on deploy and your application will be deployed in just 10 to 15 minutes On thousands of servers Thank you any questions. Yes So we are trying to open source it soon. It will be thank you. Thank you