Shailesh Yadav

Hello. I hope you can hear me. My name is Shailesh Yadav. From India originally, I am currently living in New Zealand. About my background, I started my IT career back in 2009. At that time, I was a Linux administrator, then I became a software developer. I moved into the build and release engineering space and eventually ended up in automation and DevOps around 2017. Since then, I have been working in New Zealand. Oh, yes.

For looking at scaling issues related to an application, I would first look into the logs and focus on the types of processes involved in the application that are causing delays. Basically, that means if there are any requests that are taking too long. That will be my first investigation. And then I will look into the resource consumption of the application itself. I have mostly worked in Azure, so I'll be looking at the monitoring and the metrics for the application's performance. I think this is where I'll start when it comes to scaling ModelX, because it will give me an idea of how the application will scale out and what potential problems could arise while doing that.

I think the answer is more on the technical terms for this question. And what I will be looking for from my understanding is that this is a classic case of using the application of Kubernetes, because it has tremendous power to basically deal with this kind of situation where we can very easily and quickly replace our failing notes, kind of, notes and applications, in a very easy way.

I think we'll use namespaces and names, and you know, names namespaces are the logical boundaries for different multi, multiple environments. So I'll be using namespaces and the relevant state files for, basically, separating the involvements. This is what I guess.

I think that we will be using the standard logging and metrics solutions for this kind of situation. I don't have anything in mind that could be a game changer, but I'll go with the standard stuff on this.

I don't have much context into what this is all about, but from a very first look, I would say that the one thing which I find an issue when it comes to maintainability is that things are hard for me. Hello? Yes. Yes. Last yes. Last okay. Bye. So, what I was saying was that I find that a lot of things are hardcoded here, which are not idle from my understanding. I would just parameterize all of these. That would be something really sought after in terms of maintainability. And also with the password - where is the password coming from? The password is also a plain text, which is no title. It should be coming from somewhere else, like Azure Key Vault or something. Something should be there. Sounds good. So, basically, it seems like it's a connection DB connection being made up from literal strings, which is

I have not used much of AWS. Actually, I've used it, to be honest, back in 2016. I spent three years working exclusively with AWS involvement, but never worked on GCP. From my previous experience, I would say that the question is very open-ended. I would be looking into the application design itself, because one of the problems I've been looking into is how things are going in terms of cloud. There's a strange pattern emerging, where people are moving away from cloud and going back on premises. One of the things is cost. One of the things is the cost. The reason why there's cost is that their applications are consuming too much of resources. And one of the reasons behind that is that they are just doing a lift and shift. They are not optimizing the applications or the solution itself. We are just doing a lift and shift. And that's why they don't have to optimize their applications. They have to make it cloud-ready, so that they can use the resources best while keeping the costs low. So I will be looking into optimizing the application first and then looking into cost-effective solutions because in cloud, there are alternatives for everything. Depending on your use case, there are alternatives which can suit your budget. I'll be looking at those alternative resources, whether it's AWS, Azure, or anything. It's not a big thing. So I'll just look out for the relevant cost-effective solutions for achieving the same goal. My two primary target areas will be getting that application optimized for cloud, no lift and shift, just optimize the application for cloud. Spend some time brainstorming. And the second thing will be to basically

That question points to the importance of having some sort of vault for managing sensitive data. If it was Azure, I would have used Key Vault. For the certificates, we'll be using things like and that sort of stuff. So, basically, we'll be finding the relevant solutions, which can maintain the integrity of sensitive data. And then introduce those into the respective environments through the mechanism. Like, for example, EPlay calls or the integration from the platform itself. So, again, I'm using vaults and basically, you know, the solutions which are therefore keeping the sensitive data and integrating them with the platform so that there's no, the data is not exposed to external involvement or anyone who's even managing those things. So, that would be our goal.

I don't have much Python experience. But, from understanding this code, I think it will always cause an error. The reason is that we are passing dev in the environment, and the condition says that if environment not in staging and production. So if you have given anything except staging and production, then it will always throw an error, basically it will throw some sort of error, that kind of thing. So it will always throw an error. So

I think the networking you are talking about here is in terms of the networks, not social networking. Because I think a manager has, if it's about a manager, then just technically their context is somehow also some social aspect involved in the job as well. But I'm taking it from the digital, computer networking side. So for a DevOps manager, he needs I think it's a technical skill he should have, and that's networking experience. And one of the reasons why I say this is that most of the issues we deal with at the moment are somehow related to networking. Cloud itself, based on the backbone of the cloud, is all about networking. Everything is in or on a remote location, and without a network, it's impossible to imagine the cloud. And the issues we might face are very complicated, based on the situation. It could be a simple networking firewall issue, or it could be things like CDN issues. I remember once we were working with an application and trying to fix it. And it turned out that it was somehow related to what's called autonomous systems. Yeah. So that was related to autonomous systems, and we were lucky that we had a very good networking engineer with us who had experience in these autonomous systems. So basically, if a DevOps manager has good experience on the networking side, then he will be able to understand and propagate this information to the right people because business people don't know much about these technical things. And one of the responsibilities of a DevOps manager is to basically bridge the two phases. So one is for the technical side, and one is for the business side. So he can be a very good translator or kind of a person who can actually explain business in exactly what terms the problem is without going too technical. And I think it is very important for a manager to have networking, cloud, and application experience.

It's it's when I see DevOps, it's when I see just I understand only 3 things. The first is the networking. When it's DevOps, that means basically things related to the cloud and how they are deployed and released, that sort of stuff. So networking is the first thing that should be considered when it comes to these kind of roles. And the term the situations we deal with, the problems we deal with, almost 50% are related to networking. There are some final rules that need to be opened. There's some packet flow we have to observe and troubleshoot, and applications being slow. So even for creating a new solution based on the cloud, we have to consider networking because we have to figure out the right resources with the right type of stuff to use to expose your application to the right audience. So networking is actually the key, and definitely, it is one of the very important skills that anybody who's a DevOps guy should have experience in. I think DevOps is not just something that can be done by a fresher. I think the first requirement is that you should have experience in application development, system administration, networking, that sort of things, and also how things are designed from a solution design perspective. So when that base or that background is there with someone, then he can take up the role of a DevOps engineer. So definitely, I think these are all the specs that need to be covered from a skills perspective.