So today is Tuesday, September the 24th 2024 8am here we are in our 4503 session three, makeup class for one of our classes we missed previously. We'll have another one. I think it's October the 13th in about three weeks, we'll have one more Tuesday class to make up for one of our Monday classes we missed. However, I'll send out the link on that later. You
all right, good. Well, we're actually only at four people, and we're going to be covering very many important things here, so hopefully everybody else is going To be joining us in A couple of minutes.
I'm I actually lost the panel. One of the problems with running an online meeting is you so many screens open in front of you, sometimes you get lost in terms of where you are. Anyone else Make a new one? I
Sorry, guys, I'm just trying to call something up here. Keep some jiggling out of the way. So once again, just give you a couple of minutes to review your stuff from Yesterday, and hopefully you'll find My first activity Here You
all right, if
anybody has any questions or Any questions or any concerns about any topic, basically, up till now, let me know. We're going to review, maybe just if you haven't yet done so, um, just sort of take a piece of paper and write a little self reflection for yourself. What are all the topics you remember we've covered? Because we're going to go over to minute, building up to our pipeline. And if you try and challenge yourself to um, to think through that yourself, then you're going to it's going to stick into your brain more once we talk about it. Well, we're up to 11 people. That's Not that okay. Let's Get going now. I'm
All right, guys,
I'm just making one activity ready for some reason, like my system walked up before the class. I know this stuff ready to go. I'm just rebuilding it, but we'll be with that anyway. So hopefully you're going to take advantage and use your time wisely. For some reason, I can't click mouse. Jesus Christ. There we Go. I'm
so you guys have fun yesterday with your with your blog writing, right? Is that something that's interesting to you? Because a lot of students, people your age, they sort of have the idea that studying and school means listening to what the teacher wants, pleasing the teacher asking, you know, how many words do you want in the answer and so on. You're sort of still in the mental state of children who believe that pleasing the teacher or pleasing the authority figure is kind of the way to score points. And the hardest thing we have with you at this point is getting you to the mental state where you realize that you're now the business professional you are now the one who's in charge of making it happen. You have to develop your own judgment and discernment, and you have to sort of take personal ownership of making things happen, right? There's no more teacher to please. I'm sort of a subject matter expert. I'm here to show you what's important in the world and help you connect with it. But pleasing the teacher is a thing that five year old children do, so hopefully you're all kind of starting to get that concept. And it's a tricky concept. I understand that people 1920, 21 years old, you're just sort of in that in between state. However, that's what you've got to work on, programming yourself to do whatever it takes to do that. All
right, I was working with a couple of people who said they were having problems getting into the meeting. So hopefully everybody is okay. Now it is 815 let's get started. And let's start by seeing now, apparently I have 11 people here, so let's have an attendance quiz, which is now attendance quiz is there in the attendance quiz is there in the chat box? So click on that and get to work. And attendance is important, so make sure you go and do that now. You
nobody is writing my attendance quiz yet. Why Not? I
Wow, I'm up to six people. Cool. I
so that means 11 people logged into the meeting, five of them went back to bed. Well, it's okay, you six are my rock stars. You're the guys I'm going to work with. You're the guys and ladies will work with. So you're the ones I care About. I
All right, I've got six people in progress writing the test, so 11 linked into the class, out of a class list of 2211 bothered showing up. And of those, half of them actually stayed around. Okay, well, it's your money, right? So, I mean, you guys, you guys are here. You're the sigurdsons. However, the rest of them didn't think it was worth staying around. Interesting. Oh, well, everything helps, right? Everything is noted when it comes time to making decisions about what should happen with people's raids and marks and passing and so on. Now, the interesting thing is, all the people who are not here, they're the ones going to be complaining about later they can't get a job. It's unfair. Nobody is hiring me. The world is unfair. Blah, blah, blah, yeah,
won't say any more about that. All right, we'll
give it another couple of minutes for you guys to finish up, and then we will jump into our main lecture today, which is Infrastructure as a Service, leading Up to building, leading up to doing assignment One I
All right, let's see how folks are making out. Hopefully you're all done now, let's check if
all right, good. Well, got a couple of people going. All right, I really don't want to take your attention away from these questions, because they're going to set the stage for what we're doing today. So I will kick out today's lecture, and you guys were finished, right? So you just studied a little bit on your own. And the wall, actually, I'm still going, okay. Anyway, I think our last person probably about done. Ah, everybody's done. Very cool. All right, guys, good job. Wow. You guys are doing well. So everybody is doing fine. Nice. Looks good. Let's do a little quick recap. So Karthik, amazing. Kevin, bonus, right? Everybody is doing great. Let's take a little quick look see the answers here.
So which of the following is not a primary goal of DevOps, reduced automation, because DevOps, you know, we want to increase the automation. We we want everything totally automated. I'm not sure if I told you guys this story I told in my class last term, there was this big flap going on, you know, it was on Reddit and stuff. It was something that happened in Toronto. There was this guy who had had a job for six years, you know, getting paid good money, 150k a year. He was a DevOps specialist for, I think it was manufacturer life down in downtown Toronto, at blue, orange church. And somehow there was some audit or something. Actually, I think it was a fire alarm. It was some kind of an emergency in the building. Anyway, it led to a discovery. This guy was not in his office. He was not at work, so they started looking into it, and apparently he hadn't even shown up at work in five years, like he hadn't even really been kind of doing too much. He'd been working about five or six hours a week, and he had set up all this automation, right? All of these Python scripts he had set up, he was running basically a build DevOps thing, but except when there was a problem, he wasn't even there, and the scripts were so well written that they just managed themselves. So, you know, the company, the company, the management was in a flat, said, Oh, we're going to sue him this. And that, you know, he was lying. He was he isn't there. And his answer was, well, you wanted me to do the job, and I did the job right. Every time there was, you know, something wrong or whatever, I would fix it right. My pager would go off. I go and fix it. So you were paying for the delivery of the job. You weren't paying a pizza delivery guy to just sort of be there sitting in the office all the time. So anyway, the purpose of that story is to just reinforce that if you're really doing this well, your scripts, especially, that we have aI enablement, your scripts should be doing most of the lifting. Which of these is a benefit of automated testing and CICD? Yeah, earlier detection of bugs. Obviously, we want boost manual effort, not increased. We want faster feedback, and we want larger, broader amount of test coverage. So think about that the questions are, and by the way, these are going to be real final exam questions. So the questions, if you read them carefully, they're, they're sort of going to reveal themselves, right? It's sort of like calm and I'm showing you this now. One of the reasons doing these practice tests is so you get familiar when the real midterm comes along, you'll understand how to read the questions.
So we've been talking about container orchestration and DevOps, Kubernetes, yep. So Docker is the desktop technology. Kubernetes is the actual container. Kubernetes is the box you put it into which practice in DevOps aims to shift security left. Now what we talk about shifting left. This is a concept that you're going to see used a lot in in technology terms. And I will try and give you some visualization now to help you understand what this means. What would be the best way to do it? Now that we're here online, I'll draw a little picture, and we're in the room, I draw it on the whiteboard.
So shifting left means the following thing, or it can also be called sometimes I call it shifting down, but anyway, it's the same concept.
So you might have a number of elements in your situation, whatever is your situation. Could be a build process, process, whatever, but you have a number of elements here,
and we're assuming that each the output of each stage is the input to the next stage. So you have processing stage A, B, C and so on. So
So stage a does some work, right? It takes some input, and it processes in a certain format.
So the input could be your cost, your GitHub repository, right? It could be some data, maybe some customer data we Need to process but these Are all processing stages. You
so anyway, I have all of these processing stages, and it takes some input. At the end, it delivers some output. Actually, maybe just three is enough to get the concept across. I
so when we say shift left, so now each of these is inputting to the next stage. So
so if there's a problem, let's say we detect in processing stage See, there's some problem here. So we've detected a build failure. There's a compile failure. The script is not configured properly. Somehow, it occurs to us to think there's a problem here in Stage C. I
so the first question we ask ourselves is Stage C really the right place to solve this problem, or should we shift left? Is there something we can do earlier in the processing chain which would prevent that problem from ever happening. So the concept when we're doing Problem Determination or build engineering, or basically anything in the real world, anywhere, if you're solving a problem, you start by asking yourself, what is the earliest point at which I could do something so this problem never comes up to begin with. How can you shift left In terms of solving all?
And better than fixing it. It would actually even be better if we could prevent the problem from ever happening, in which we can prevent the problem from ever happening,
right? So bear that term in mind. You're going to see it a lot. We use it a lot in software test, shift left, you know, just to see what you could do maybe with the input data, for example, that would kind of prevent things from happening. All right, so anyway, that's the concept of shifting left. Yes, I should probably make now that we're going to be tooling upstream today to building our pipeline, I'm going to be developing a lot of materials like this, and I'm going to make a PowerPoint to start capturing this, because I don't really like PowerPoints that much, but for some things, they are, they are sort of the convenient way to do it. So let's take a couple seconds to do that. Any questions about that before we carry on new All right, let's keep all that You
what I told you yesterday, right? I'm actually trying to contain all of my stuff in Google Drive so I can apply my new artificial intelligence processing program. In fact, I'm sort of wondering if it might happen. Years from now, there'll be something access to our college, I don't know, whatever, and then they find out, you know, Where's Peter? We haven't seen Peter for a long time. They say, Oh, you know, he hasn't been showing up for a few years. All his classes have been run by an avatar that he trained. And, you know, all of his students, counseling and so on has been done by an AI with a voice synthesizer. So I don't know, it might get to that one day, I suppose, not today. I don't think so. All right, so new
Google Sheets.
No, I didn't want Google Sheets. I wanted slides. Google Slides. I
This actually works well, because I cannot use Microsoft Office of my laptop. I don't know why. It just doesn't start if I try to start Word or PowerPoint, it just simply won't start. I have no idea why. Well anyway, I think that's a catchy title. Building the build process with CICD. I haven't used Google slides in years. I can't even remember most of the details about it. I guess they probably have a lot of AI enablement now, so if I want to put an image there, I could probably generate my image. I didn't even know. I was just guessing, but I can, I can generate my image with AI. I
loose could take about 20 seconds come back to it in a couple of minutes. Let's go and study another couple of our test questions.
So what practice in DevOps means look for a way to solve the problem earlier Processing Cycle. Yeah, DevOps security. I don't think we're we might talk a little bit about security. I'm not going to ask you to implement security in your project. It's tricky, but you should at least be familiar with the concept. What is the purpose of the blue green deployment? Blue Green deployment. Now we're going to see here in terms of color phases. There's various color coding and they refer to various stages. You know, where's your test cycle, where is your staging environment, and so on. So reduce downtime during deployment. So this basically means that you would deploy it into a secure test environment, maybe called the Blue deployment environment. And once you've tested it and gotten software testers in there, you know you've gotten people to make sure it's okay, then you push it out to production. This is just basically, this is staging and production. So anyway, that's a term you're going to see out there. Just be familiar with it. Which tool is commonly used for configuration management now a good thing as a result of your case study yesterday, a number of you guys saw these tools. So Ansible is a configuration management tool. Jenkins is a automation tool. GitLab is a code versioning tool, and Maven is it's a build script. It's basically a Java language implementation of a build script. Those all things. What does infrastructure as code refer to? Now that's going to be one of our lectures today, writing code for infrastructure management. Writing code for infrastructure management, uh, storing code. Not really that would be sort of, once you understand the concept, you will see that that's kind of a non cynical answer, in a sense, because infrastructure is processing here in it land, we have two sort of kinds of things we deal with, and if my slides are ready, I can start drawing some pictures for you. Let's see my slides are ready. Well, they didn't do anything for me. All right, we'll come back to that later. Okay, let me drop my little picture in here. First shifting left, I'm
up. I'll kick this link out to you right now in the chat box later on, after class, on Moodle, in that little section we have where we keep track of all of our assets. For right now, just store this make a Google Doc or something to store this stuff. Okay, there's that i
i actually like this one that I like PowerPoint, and because I'm trying to coordinate all of my stuff with Gemini, which is Google's AI, that's my reason for wanting to do all of this in the cloud. Remember our discussion yesterday, the factors that drive technology Well, factors now people are going to prefer To go where there is The best AI enablement. You
uh, right. So we have sort of two areas, two sort of spheres of concern. Of them is infrastructure, which is processing, GitHub, for example, a web server would be processing, a database server would be processing. And the other sphere we have is data. So we have assets, we have engines or tools which do stuff, or we have the data which the stuff is done on to. If you don't understand what that means, we'll go over more examples till it makes sense to everybody. You
Where do I change? Where's my color thing? There should be a thing here to set text color i
Where is the worse the thing for Setting color For text, I
and as we keep developing this, we're going to see how we do is going to fit in one or The other of these two categories, one or the other of these two buckets or bins.
So what does infrastructure is called refer to writing programs. See, I'm just trying to come up with a good this will make more sense after we get into today's lecture. Infrastructure is imagine like roads, water, sewer, sewer systems, you know, all the stuff in society which keeps society running. Infrastructure refers to the systems that support the society or the world you're living in. So here in DevOps, our infrastructure is primarily our CI is primarily our our GitHub repository. So we write code which manages our Convertible data, and that I'm gonna, let's just put this aside. We'll come back to this later, because this is stuff we haven't really we're going to get into today, describe the basic element. Yeah, actually, that's correct. This was a question for us, so it's good that you know that, but that's not primarily a DevOps question. That's a networking question. What does shift left mean? Oh, this is a duplicate question. I mean, I guess implementing practices, or, yeah, implementing or problems or processing, implementing processing as soon in the processing cycle as possible. What does continue? What does he stand for continuous development? What is the main purpose of continuous development, to automatically deploy code, automated testing, reduce manual work right, lower or as much as possible, the chance of human error. Which tool is commonly used for version control? Get? A lot of people aren't totally sure. What get is, ah, get is a pro HTTP is a protocol, yeah. Anyway, we'll talk about that later. Which practice involves automatically reverting or rolling back changes of things fail, continuous rollback. Which of these is not a common now, a metric. The term metric means a measurement, like a thermometer, like if you wanted to find out how cold it is outside, you can stick a thermometer out your window. A thermometer is an instrument that tells you temperature. A metric is an instrument that tells you how well something is running. So lines of code written is not a good way of knowing how good our DevOps process is running. In fact, sometimes, and I've actually seen in books on software engineering, they suggest lines of code written is a is a metric for how well your software team is doing each day. I don't agree with that. I think of using the same job done in fewer lines of code rather than more. It actually means you're a better developer. However, yeah. So anyway, lines of so all of these other ones could be measurement indicators. Yesterday, when we were doing our case, started to talk about one of the questions is, how can you know how good your CICD process is? Right? That should actually be one of our basic questions in this course. Because, as we here to learn how to build CICD pipeline, an important question should be or metrics for the quality of your CICD process, or what metrics? That's something I'm not going to answer that now, I'm just going to leave it with you to think about what metrics would metrics or what would be good measures of success. I
so deployment frequency, how quickly you're deploying, how long it takes from the time a developer may till it's out there in production? How long does it take to recover if your system crashes? Those could all be good metrics for DevOps, but lines of code written no which of this is not typical of us, continuous integration, pipeline, manual approval. We don't want anything involving manual i What is a key benefit of infrastructure as code version control? Yeah, that's one of the things we're going to be seeing here. We're going to be coming up on a break in a couple of minutes, then we'll come back and do our lecture, and we will see a bunch of stuff about infrastructure and how it works for us here in CICD land, what is the primary benefit of a micro services architecture? Ah, you guys, hopefully you've all watched my video by now. I hope you have you.
I'll track all of my videos here in Europe. You can binge watch them. You can invite people over on The weekend and binge watch them. You
It's good. I
Oh, this doesn't let you insert videos, really. Oh, there I
14 views on my video. All the work I put into these things, you guys don't even watch them
anyway. All right,
easier, deployment, easier, scaling, easier, maintenance, yeah, basically all of that. It increases scalability. So that's not the right answer. It reduces coupling. So that would not be the right answer, and we get a services I mean, monolithic structure and services structure are opposite ends of the spectrum. Please direct answers. Please watch my video so you know about this stuff. You What is a key characteristic of DevOps culture. Blame free environment. Blame free environment. Resistance to change would be the exact opposite. That is one of the barriers to implementing DevOps, as some of you did identify in your case study yesterday, some of you did talk about your case study companies and when they were initially getting into DevOps, what was some of the reasons people did not want to so barriers to entry and DevOps could be things like siloed mindset, like siloed culture. I
uh, right? So sometimes, especially older people getting close to retirement, all they want is for things to just, uh, keep going sailing till they retire. They don't want to do the work of learning new systems. So that could also coupled into, uh, silos, organizational silos and fiefdoms. So you managers who want to be the sort of ruler of their own little kingdom, want to have to work with other people in terms of how they do things.
There's some other things here we'll go and add later. I wanted to drop these things in While we're thinking about it. I
CI stands for continuous integration, yep. What is the main goal of continuous monitoring? Provide real time feedback, patient and infrastructure health. So anyway, when we get to our midterm exam, which I think we're getting to in about a month, right? We're somewhere around week three now, so week seven or week eight is midterm. So when you ask me what kind of questions, well, those are the kinds of questions you're going to get. And if you just relax and breathe slowly and slow down or calm down and study the question carefully and think about what we've talked about in the lecture, I think you'll you'll answer pretty simple. All right, let's put this away for now. Any questions or concerns about anything we've talked about so far? I don't see any so far. Let's carry on now. Our next topic is today's topic, which is infrastructure, which your
lecture notes are right here and
I can't find what I'm looking for. I lost your I lost her. I'm just going to close everything and open it up again. I got too much stuff open here. I
anyway, I think that's in the wrong place, but we're not going to spend time on that right now. So let's kick this out. This is our first lecture that's kind of our, our main lecture of today, right? Or our first lecture of today. I'm going to kick this out for you to look at. Then we'll take a break. When we come back, we'll start studying this. So here's our lecture
in the chat comments.
All right, so let's take a break now. Break resume 930 and then we'll go and study through that. So go and take your break now and you can start reading. We'll get back together in A couple of Minutes.
You You Want To
Hey, all right, boys and girls, let's pick it up. Time to resume now. Hopefully everybody is following along. Okay, in our online class and well, it's, it's 929, we'll give it one more minute, Then we'll carry on up to 14 people. Wow. You.
All right, so where were we before the break, right, we started last by having an attendance quiz, which review a number of concepts. We went over and made some discussion on some of the things we've talked about, and we pre, what do you call it? We sort of pre previewed some of the stuff we're going to be getting. We started to make a new Google Slides PowerPoint for some of this new information now we're managing. So now we're going to go to the next stage, which is a new topic, which is leading into your assignment, and our big Magnus Opus, right? That's a term in Latin. Magnus means work. No. Magnus means big Opus has worked. So our big work, our Magnus Opus for this class, our own CICD pipeline, which is why we need to understand what a CICD pipeline is, how they work, what the options are for building them, and how we can tell whether we've done a good job. At the end, any questions or concerns before I carry on new All right, Then You
all I want is a simple image displaying the concept of a Magnus Opus. Why are they giving me all these like strange tarot card things and so on anyway, not going to spend time on this right now.
Really, I didn't even know it was an alchemical term. That's a new thing on me,
working with
lead to turn it into gold.
Well, how about that cool
in a sense, that's what we're here our class, right? We're turning the lead of problems into the gold of well functioning solutions. Let's move on to our lecture notes now. You
once again, I can't find my lecture notes. This is getting old. Why can't I find thoughts? Here it is. Okay, Good. I
now I Lost my slides. I
All right, so that is the lecture notes we're on right now. I'm going to send out this landing page, because this kind of contains links to everything else. So what's if you just keep this handy, then you'll be able to get to everything else, right? So let's do that. Here is your kind of landing page now, in this new AI enabled world we're living in with Google, Gemini and The professor's toolkit, right there. That's our lecture notes. I
All right, let's go and do this. It's 940 we're going to 11 o'clock today, so we'll take another break. 1015, or so more hour 170 minutes or so to get through this. Can I go full screen on this? Can I get blow it up to full screen? Well,
maybe. So before we dive into the technical aspects of infrastructure as a service and cloud based DevOps, let's focus on how you college to land great jobs, because that's your goal, right? Everything else is just talking. What you really want is to get the job. Because when you have the job, then you can be more relaxed, you can be a little bit more secure in your life, be a little bit more emotional, and you can generally not be worried about, you know, paying for your paying for your expenses and all that. So let's see how all of this relates to what you want, which is the job.
The skills you're learning here are in high demand to truly stand out, you need to understand what is required to make this work as a paying craft. Your CICD pipeline is not just an assignment, it is something you can add to your portfolio of work assignments, and later on, in a future class, I will show you how you can make a Google Sites or other website, and you can sort of show you're doing so your student portfolio would contain some of These elements,
document your process through and specifically in terms of talking about building your CICD, you can create some good documentation using, for example, Google Docs challenges and how you overcame them. Create a detailed readme in your GitHub explaining architecture and how to use it. I To record a short video. Yeah, so there will be a video as part of your
final project
and write a blog post or article, which you've now learned how to do, talking about what you did and how you did it. Step Two in the process of getting the job,
gain hands on experience with popular tools. So to start with, you should have a knowledge of what the popular tools are, right? So start by understanding building out of what the tools are and when is the right time to use each of them.
You employers value practical experience, so in your point straight how you've applied these tools, I
So GitHub and GitLab, Jenkins, GitLab CI and GitHub actions infrastructure as A code right? That's just something we're getting into. You probably have some of these. I'm guessing you haven't seen this before at all.
Containers, cloud platforms. You
for monitoring tools. Many of these tools offer free student licenses, which we're going to be using earn relevant certifications. I'm
so AWS, certified DevOps engineer, Microsoft Certified DevOps engineer, Google Cloud and sewer certified Kubernetes. Now this has some cost, right? And it's not going to be something you'll do right away. It may take a couple of years. It may take a couple of $1,000 however, money comes to Now, your question is, what do you want to be that's more than just two years older, right? So it does take a time investment to do this.
So your question to yourself is, two years from now, what do you want to be that's more than just two years older,
because two years is going to pass Whether you accomplish anything with that time or not. Do DevOps,
soft
skills and
DevOps is about culture. So think about ways to develop locations practice explaining complex technical concepts simply, which is one of the things you're doing with your LinkedIn blogs, and one of the things I'll be looking for in your final project presentation, engage in group projects and open source contributions. Document how you troubleshoot your projects
and continuous learning. Stay updated with Deval cast and webinars, networking.
Attend local demo things and conferences and now you say, Well, where am I going to find local DevOps, meetings and conferences? Good question. Let's go look for them. I
Yeah, DevOps, Toronto exchange, right meetup, so that's something to do. In fact, the the meetup meetings are really amazing. I made a lot of Good networking context there myself. I
2021, holy, three years old. Is anybody updating? Well, actually, that was for Those for a conference. So i
i Oh, I think I'd already, I was signed up with my other email before. That's why I was a registration error. I guess I don't know why. Really, you joined the meetup group. Yes, you've earned dollars, some factor, whoa, oh, prepared meals. Cool. Well, I don't really care about this stuff. I don't really want any of these offers, but I don't know, maybe they're good for you, you go one month trial. I already have that.
Here is
anyway. So anyway now that so I've done that, right? Have you done it? Did you follow along with me? I'm going to go ahead and suggest here that if you're not interested after these things and thinking about them, because this is much lower stress than going to a job interview. It gives you stuff to think about. And if you're not really interested to get your butt off the sofa and make a little bit of work to get this stuff done, you're probably not going to get anywhere, right? It's hard, yeah, leadership, it's a little bit risky. You have to, you know, get dressed in nice clothes. You have to take the bus and go there. However, these are the things you need to do if you want to make a little bit of motion, a little bit of energy and progress going in your life, leading things happening, and getting the job and getting things going right. I
Are they having any like in the future? These are all things from the past. What's wrong with this? 2022? I
Oh, I guess this is the new one. That's probably old one, because everything there was like 22 and before, I think I just, I remember going through this in a previous class, and I think I found out at the end that this one had sort of been retired. They'd made the new one. So anyway, I'll leave it there, if you just want to see what sort of things they used to talk about. See, I can get one meeting, which you guys can go to at some point with the next month or so. Uh, DevOps exchange Toronto, coolers, cool.
Ah, there we go. March 28 2024 which was six months ago. Jesus Christ. What's wrong with these people? Why aren't they doing anything? I In July, 14, I
Well anyway, my suggestion would be to just keep following it and when they have some new and what's going on with this. So this used to be so active. What did what happened to them? I
Well, if I find where their current activities are, I'll tell you about it, because I know that they haven't gone away, right? They haven't died. They're still doing stuff. I'm just on the old September 25 which is tomorrow, ah, although that's in that's in the US, though that's in flagsmith, I don't know, in the US or something. I
All right, well, one some stuff will tell you about it. How about that?
One members recently joined? Yeah, that was me. I anyway, Let's move on. I'll work. I
All right, so you just missed one basically, last weekend, September 12, global DevOps Canada. Yeah, that was the beginning of summer, yeah, but we'll just give me they're saying it's going to happen and oh yeah, here we Oh. Here we go. Look, September 26 which is this weekend. This is Toronto.
Best conference, yeah, best conference where though
they're being so difficult.
Well, this is a training, right? This is not really a conference or a meeting, more of a training. So anyway, at least you're aware for right now that these things do exist. Maybe in future you'll you want to invest in this. So these are the kinds of things people pay to learn this stuff, right? So take my training seriously. People are going out and paying $1,000 for a two day training course to get what you're getting here as part of your overall education.
Reasons for spending time on this is to um, just reinforce, or just make you understand that this is a community, right? This is a thing which people do. It's not just kind of like and putting product on a shelf or something. This is actually like a kind of a full lifestyle. If you're into this stuff, a lot of people get very this. It's a it's a very satisfying thing to do, right? It's very sociable. You kind of get involved in the culture of doing stuff. So I think this is a much more interesting thing to work in than, I don't know, being like a financial analyst at a bank or something. I know people who do that. Whenever I see them, I ask, how's things going? They go. My job is they can't stand it's a very unpleasant thing to do. Where does this is like a very kind of personally and socially immersive thing to get into. But I just want to find at least one new event I can show to you, and I can't find it here, 16 master software development with TDD, total domain delivery, or sorry, test driven development. In this case, I
all right anyway, let's move on all that stuff. Later on, I'll search around and get You something
with our lecture notes. Now I
so tailor your resume and online presence. Online presence is this YouTube video channel,
right other things as well, but just start with those two for right now, highlight projects that demonstrate your DevOps skills, quantify your achievements. Well, maybe for you, you're a bit early in your career cycle to look at doing stuff like this, but over the next several experience to start saying stuff like this, maintain an active GitHub profile showcasing your code and contributions. I
I create a personal website or blog to share your knowledge and projects prepare for DevOps interviews, right? This is our career development aspect now how this relates to getting you the job. Why are we talking about this now? Because the earlier the and understanding goes into your brain, the sooner you start to think about it. Have to sort of play it out and act on it, be ready to discuss your CICD pipeline project at the interview which you're going to do here in this class, practice common DevOps interview questions and scenarios. Be prepared to whiteboard our signs or troubleshoot issues. Familiarize yourself with case studies of DevOps transformations. So this is why we're doing our case studies right. To give you something to talk about, just for that point, this is why you're doing your case studies in class. You
uh, so the project, the assignments. When I say project, I mean all the stuff we're going to do in this class, daily, little you know, in class, group activities, even if it doesn't, you know. So if you're grading in terms of, it's worth 10% of your mark or whatever. When I say the project, I mean all of our in class activities, from the simple things like we did yesterday, to the assignments on the project, the big project, work we're doing here in our class isn't just academic. It's the stepping stone to Your career life starts now you
okay, I guess I should check back to see if we have any questions or anything. He's asking some questions.
No question. I
you know what makes me sad? I mean, there's 14 people here. The stuff I'm saying is is very high impact, right? It's very high value. And half the classroom, they'd rather just sit in bed. I guess they're ready to retire. Maybe there don't have much energy. They're they're 20 years old, but they're just ready to kind of take it easy and put their feet up. It makes me very disappointed, because money your parents are paying and your family is paying for you to be here. I know because I know what I paid for my kids, and I think it's very um. I don't know if I should say this or not, but I will. Ions are not here and not taking this seriously. I think they're just very bad people. I think it, it's just a real mark of bad character. People are making efforts to help you and take care of you, and you're not kind of validating that. I think that's not good anyway. Let's carry on. We don't want to worry about them. I guess they don't have any future.
So approach life with the mindset of a professional DevOps engineer, document your progress, be prepared to explain your decisions and always consider how and improve your pipeline, And more generally, your approach to life and success. You
I sorry there was just something on my keyboard. I wanted to go inside between the keys all right, by combining the technical skills we'll learn in this course with career focus, strategies and mindset. I
you'll be well positioned to land excellent jobs, high paying jobs
in the DevOps field.
The demand for skilled DevOps professionals is high, and in a world where more and more stuff is transitioning over to AI, it's going to keep going up, not down, with the right approach, you
find your
little place in the world to sit, your little purge, to sit and take advantage of it. Now let's delve into the technical content that will form the foundation expertise. So now remember, this is about doing your assignment, one which leapfrogs into doing the project, which is building the CICD pipeline. So that's about here now. So welcome to our introductory level lecture in your DevOps journey. You now we're going to explore foundational concepts of infrastructure and cloud based DevOps platforms. This isn't just theory. It's the launch pad for your hands on adventure in building real world CICD pipelines. You Why is this lecture so important? Because I wrote it, and everything I do is very important. It bridges the gap between concept and practice as we delve into infrastructure and cloud DevOps platforms, you'll gain the knowledge necessary to make informed decisions about tools and services you will use in building your own pipeline.
You'll understand why certain components are essential, how they fit into the bigger picture, and which tools and practices are the right tools and practices To make it happen.
By the end of this lecture, you'll have a clear roadmap for your upcoming senior young CICD pipeline. The role of infrastructure in providing flexible, scalable infrastructure, cloud based DevOps platforms streamline the development and deployment process the key components that make up a robust CICD pipeline.
Best practices for designing and implementing your pipeline as we progress through the lecture, keep in mind that each component can be applied to your wrong project. Think about the type of application you might want to deploy. Now, by the way, I'm going to show you several types of things you could do, but what I'm going to be demonstrating, and which I'm sort of going to gently encourage you to do, we're going to build an AI product, right? Because that way we'll also get a little bit of our topics from 34 this, which is developing and deploying AI models. And to be able to say that you have a little bit of AI dev experience resume is a good thing, so I'm going to make our product, my demonstration projects here in class, centric around that, because that fits really well with DevOps anyway, with because very big, right? They take a lot of training data. They have to be done in the cloud. You can't do them on your desktop. I mean, unless you have a million dollars to have your own Cray computer at home or something. So, AI is, it's a very well. It's a very good fit for DevOps. So our demonstration example projects here
will be aI application.
Remember, the CICD pipeline you'll build is not just academic, it's a small scale version. You will build a small scale, minimal viable product version,
what They call a total learning version. I
Mini, Mal, minimal, viable version. That's what it is
in use and practice.
Our skills we learn here will be directly translatable to real world tasks that you'll be doing at work within the year. So let's embark on this exciting journey laying the groundwork. By the time we're done, you'll be well equipped to take on the
automated software delivery.
So here's our lecture now, infrastructure as a service and cloud based DevOps platforms you
as you approach graduation, you'll be entering one of the most exciting, dynamic fields in the world today. The demand for
cloud specialists
is driven by the requirement to create new AI solutions for commercial IT products. According to recent industry reports, DevOps, or later, job postings have increased by 40%
companies all across the world are professionals who can bridge the gap between development and operations
all right, A lot of this is stuff we've already talked about. So I'm going to leave it to you to read this by yourself later on. Not going to take up time in class right now, because we want to move ahead with our technology stuff.
So sometimes
you may see out there, or things you're going to go out there and look for could include DevOps, engineer, cloud operations, infrastructure engineer, Site Reliability Engineering, SRE could also be safety and reliability engineering, so That SRE could refer to either one of those. I
and cloud DevOps, analysts, these
salaries, excellent growth prospects.
As you build your skills and Infrastructure as a Service and cloud based DevOps, you become increasingly valuable to employers looking to modernize their IT infrastructure. So here's some of the topics we're going to be talking about now we're well,
understanding infrastructure as a service.
What does it taste DevOps,
key components in a DevOps, building your own DevOps pipeline and best practices and considerations. All right, guys, let's take a little break. We've been going for about an hour
15.
Let's give it a break till 1030 when we come back, we'll spend the remaining four actually. Let's make a 1035 if you want to get a make a coffee or something. So resume. At 1035 we will finish this, and that will be
