Good morning. Good afternoon. Good evening wherever you're hailing from. Welcome to another edition of OpenShift Container Storage Office Hours. Today, we are talking with Michelle De Palma about auto scaling multi cloud gateway. That sounds super fun. I like scaling stuff. Okay, so I have an idea. It's just an idea because I haven't run through this already. So I'm going to propose that something and you can tell me if you think it's absolutely horrible. And if you don't want to do it. Sure. All right, so starting with, obviously, we have the latest and greatest OCP cluster going, which I assume you've got yours up already. Yeah, my clusters here somewhere. Yeah. Okay, so OCS latest and greatest install, which we can do again that's fast, very generic install we're not doing anything special with the install. It's also hit the operator will just go through that. And then someone from the, the MCG Nuba team because I was like, Oh my God, I got to do office hours. What should we do. So he said, he suggested why don't you do quay. And you see me pausing because up in Canada we call it key, but let's install the quay registry. It will use Nuba, it will use the MCGM point. And then, so, so what we can do, and we can verify that we can show how you can just go see it using creating buckets and stuff like that. But if we scale down the horizontal pod auto scalar to something really stupidly low. And then if you can help create a deployment that like spins up a thousand pods or something ridiculous with an always pull on the image we should be able to see the scalar in action. Okay. Just to let everybody know I'm having like the worst technical difficulty morning, and quite some time so this will be fun for the record. I like the idea. I like the idea. I don't know if we'll be able to pull it off so show folks probably will need your help today so yeah this is an office hours though so feel free to ask any questions related to storage.  Okay, that's an operator. Right, but you know when you go yeah can you share your screen like when you go to push and pull from your new private registry you have to tell open shift about it. I think you have to, if you're going to do it insecure you have to modify one of the cluster objects so to me that's the unknown. I'm like there's some shenanigans around that shenanigans. Okay, but if you just spin it up you can see it using the new band playing you can see it. Yeah. So you see the screen you're you see that I'm on the I'm on 4615 I don't think that'll make as big a difference. What update is available. Yeah 4616 shouldn't make that big of a deal. Let's see. Alright, so operator hub. Here we go. And folks if you have any questions or can't see anything or have any issues with what is on screen. Let us know I can maximize sizes and fix things. So, how would I install the operator registry, I would you wait you have a CS installed yet. No, I have a rotational disc problem. Yes, so I have to, we're going to have to jump through a lot of hoops to get this working I hope you know that. So, let's see, OCS. First, I need the local storage one. I have local storage and it registered rotational storage, no less, which super sucks which means I have to go in and patch it. We've done this on a show before but it's been so long. I'm not sure remember how to do it. So we'll see. Yeah, this is like a fresh cluster. I had to blow this away a couple weeks ago and rebuild it and it's kind of just been sitting here waiting to be abused. So yeah. Okay. Yeah, give me more reasons to do stuff with it. Yeah, I like that. So, do you use let's encrypt. I do. I am actually I have a let's encrypt hoodie hanging up in that closet over there. Yeah, you've good swag. Yeah, I have to say yeah. Well, today I'm just wearing my Nike Detroit shirt because you know Detroit haven't been there like an actual downtown hub to feel the energy of the city and a long time. So yeah, I'm kind of missing it. I don't recall this storage operator taking so long, but let's see. So what, okay, so I have the problem of rotational discs, right. Okay, so this local storage registry is going to pick up my SSDs.  Okay, so seven VM running on one machine it picks up the SSDs as rotational. But maybe with this is a very new version of the operator so maybe it fixes. Let's see. I mean it just came out. I'm reading this correctly, the 30th of January. So yeah. It's doing stuff folks you can see it here. Let's, let's pop up on that tab real quick and see what's going on in here. See it's installing oh it just finished perfect okay. So, local volume discovery, I don't know if I need to create a discovery here local volume set what do I need to do with the local volume anything anything I don't think so right. Oh, God. So, first off, I haven't had my first couple I don't think so. It's been a while. Yeah, and it's early. So we'll try it without and see what happens I can't remember having to do anything but that was was. Let's see. All right so this is 462 so we got some updates. We definitely want to enable the operator recommended cluster monitoring on this name space. I'm running for six so stable for six. Yep, all this looks good. Check box folks you when you are installing OCS I highly recommend you check the check box because if you don't you won't have good metrics observability on your storage and that's like it should be selected by default. I will mention it some good point that is that is a very good point. Yeah, you should have that out of that. Yeah, actually I should mention that on a lease show later today that hey by the way, I know it's the operator writers that would have to correct it but it's it's one of those things where it's like, if we recommend it, it should be checked. All right. So we can see what's going on with this one here. Seven nodes on one bare metal on one seven and one. Okay, seven VMs, three of them are sized for OCS and they're already installing. Yeah, so I got three control nodes, you know, just whatever size three nodes size specifically for OCS and then an extra worker node, just cause. Okay, so this is so you know that it's okay so just so you know I was thinking of auto scaling because the when I was on for the first time before someone brought up performance and so I thought from from the customer point of view, which you need to be concerned with this, does it doesn't scale right like can we can we manage any upbursts and of activity so it just I just thought it'd be very meaningful to show auto scaling and what knobs you can turn to make that something for your environment that's also but I hope to have some more information about like sizing and stuff like that there's some anyway there's some articles coming out but they're I can't discuss them and to be fair I haven't read them yet so I can show you. All right, so CS appears to be installed. Okay. Storage cluster keys. Yes. All the defaults are just leave unless you want to go smaller, or yeah, whatever, whatever. I usually do too. Oh, let's just do half and then we can scale up if we need to work. Okay, so put it on these nodes. Because as you see, these are the nodes with eight CPUs. It says minimal cluster will be deployed the selected nodes do not match OCS storage cluster requirements of an aggregated 30 CPUs and 72 gigs of RAM I don't know how that's possible. Because they all have 64 years of RAM.  Okay. Yeah, this is a tech preview warning. That's weird. Anyways, alright, so I do have to do internal attach devices though don't I. They are. Yeah they are. Well you do all kinds of stuff I don't do an AWS. I didn't AWS right like that's why yeah like I'm like oh this is going to work. Let's try. So let's see you'll select our notes here. With worth it. What are we going to call this volume set just LV 0000 how about that. Cool. Alright, just type. Yeah, I'm just looking those advanced. I'm just looking at the initial here block. The OCS cluster requires a memo three nodes for the initial appointment only one node match the selected filters. Really. That's weird. Only two nodes match. Okay now it's all three cool. Okay, yeah, it's like checking it all out it was checking it on the background that's cool. Yeah, good for API is like API is working that's awesome. And as you see we switched from that internal screen on the, you know this toggle on the left that you would normally use right, or external if you're, you know, using some kind of S3 bucket of some sort. So since I'm super sophisticated and this cluster is in my basement sitting on top of a refrigerator. Yes, I'm very, very technical here. And if you've watched the show previously, you would have noticed that we have done this before and have had issues but now it works. So let's see. Next. As long as we're not doing anything that make Chris Blum cringe. I don't know he's in chat. So, we'll see a bucket will be provided. I guess I select this one. Okay. What's it, wait. What's it complaining about. That's what you need to wait. I don't know. Oh wait it does say create new volumes that instance for me didn't you just ask me, we were looking at just did that. Didn't it. Not just do that. Okay, let's try this again. Right. I don't mean it we skipped it. No, I see. Okay, so go ahead. What about create new volumes that instance. We don't see it the blower in the morning in the pink morning. Oh, okay. Oh yeah, we did. I thought we did this. We thought we did this. Okay. Are we being impatient. I don't know. Okay. It goes under advanced. Nothing. Okay. It should just say, you know what, let's just select all. Nope, that didn't do it. Do you have to set a max size, your max size is empty. Just so you know, um, how is it. Yeah. Okay, and it's got no name up at the top. I thought we did this. How is there not because we have an MF coffee. What were you going to do? logical volume set. Triple zero. We just did this. All right, now the next button's good. All right. Off we go. Okay. You won't be able to go back after this.  Okay, now here we are. See, no, look, we did do something before. Okay. And now it's asking us to do it. Create a new volume set instance. And now I'm getting, now I'm getting slack messages. This is good. I hope they are from our friend, Mr. Bloom. They are. Yeah, we're doing something wrong. He's like morons. Don't do it that way. Okay, hang on. I can see. This is his area of expertise. Okay, so he told me to open this. Do this. Okay. So he says there, you'll find a YAML that will use local disk directly without the need of LSO. Just change the path and the capacity. Where do I run this, Mr. Bloom? Oh, I just run against the cluster. I guess that's weird. Make sure I see status at the right cluster here. Yes. So I will need some sort of real quick. Okay. Pull it up over here. Edit this file. And it is doing work in the background. You see here, your nodes are increasing. It's checking them out. Is it? Yeah. Yeah, you see him. You just keep starting with one. Okay. Anyway, we should do a Chris sets, but, but just, well, yeah, but he says to do this. Okay. To bypass the local storage operator, which we already have installed, but okay. Chris, which one is better? For your particular setup. Notice to users, we don't normally run things this way. No, like, that's the problem. But let's just create. Okay. All right, apparently there's stuff. Okay. Things are changing here. It's doing its thing. Okay. Now we need to be really patient. Okay. So you, if you want to, you can do like OC get pods on the open shift storage name space. If you just want to watch stuff happening, but it should complete. All right. Okay. It's waiting for that progressing true. Available falls. It will, it takes a little bit. Yeah. It does. And what do you want to watch? I'm sorry. What did you say? Well, do you want to go to command line and, or you can go to pods, workloads pods, like either way, just to, you know, Yeah. Watch it in action. Yeah, it looks nice. Yeah. All right. Here we go. Yeah. And that's all of these have to do their thing. And hopefully no one's impending everyone will be completed or running or something. Yeah. Yeah.  So we're not, other than that part, we're not going to do anything special from the OCS side for quay. When's the last time you installed a registry? Have you, have you done it recently? We, I have not done it recently. It's been a while. Did it. I can't remember it was the last week of this week. All the weeks blur together nowadays. So sad. I think it was last week on the channel, we built out a quay code. No, yesterday. We did stuff with quay yesterday on the level of power, I think. So, Oh, cool. Okay. It was with quay, the service, not quay, the local registry. Oh, okay. Okay. Okay. All right. So we're going to do, we're going to install it. And then by default, it's going to use the new band points. For its object storage. There's, it does more than that. It does more than that. It does more than that. Like I think the Postgres or whatever database is using is, doesn't use that. It's like the registry part uses the new end point, but, um, But you'll, you'll see what we've got going on here. So. So yeah. Okay. The, the snippet that. Chris Blum sent. Said, you know, he said, you know, use that if local storage operator wasn't working, it appears to be working fine. So we're doing great. We're going to run with it. He also noted. The cluster is considered a compact because your nodes only have eight CPU units. Okay. That, that is interesting facts. Um, I would not think eight CPUs would be compact in any way, shape, or form, but okay, fair enough. And we all have our different definitions of compact. Well, you know, we're storage people. All the things. All the things. Right. No, I get it. We do actually expect. I mean, this is why like people have, this is why people build literal storage arrays, right? Like it is a unique thing. And we're doing it with commodity off the shelf. Consumer SSD.  You know, regular Intel CPUs and stuff. So. Yeah. I mean, for testing around compact is fine. Right. Like it's for what we're doing. It's okay. It's just not what you want anywhere in your production or something. Yeah. No, you don't want to undersize your storage. This is literally just. This cluster is designed for this purpose to use on the show. And then I can rebuild it whenever I want. You know, that's like always a strange conversation on the OCS side. When you, you talk to potential customer and you're saying, well, you know, you need so much. It's, it always sounds like so much. I'm like, but, you know, you're kind of doing this anyway. Off with other kinds of storage too. You're always. I mean, what's the minimum amount that I could get away with to support these $1 billion devices. I just like, no, you need to do it. You always think over capacity one version means. Right, right. I did funny that like, for some reason in this context it seems odd, but I'm like, actually it's just kind of in line with. It's not odd. Right. It's odd because. We're used to like, you know, eight CPUs on a laptop is really good. You know, like that's why it's odd. Right. Because we've all been in this world of what hardware can I get my hands on. Not much. Yeah. But yeah. Right. They're still coming up. Okay. Okay. Have you ever looked at any of the. Horizontal pods scaling stuff. A little bit. Not much. I'm going through chat right now. Let's see. Okay, cool. So. Mannequin Dan wants a tiny demo lab environment, but OCS needs very huge multi-note setup. Like we have mentioned. Can we have an all in one OCS cluster just for experimenting? We cannot test OCS on CRC. Obviously. Is there a recommended alternative? I mean, this is kind of it, right? Like spending up multiple VMs in your VM environment. Yeah. Using some kind of storage that's already available. Yeah. Right. Mannequin Dan, if, if, if you're already an open shift customer, we can help you with that. So I would strongly encourage you to reach out to your red hat account manager. If you have one, if not, please feel free to email me and I'll get your questions to the right answer. Yeah. So that question is really how small can you go? Sorry. Right. Basically. Yeah. Okay. Just how small can you make this? And I think this cluster is about it. Right. Six control plane or three control plane nodes, three OCS sized minimally nodes, and then an extra worker nodes. So like that extra worker node is if we want to spin up a VM. Right. So I mean, maybe you can find out some unsupported stuff. If they're willing to, right? Like there's, there's like the official line that we've tested and written about.  So we can. Yeah. This is definitely the try to get away with that concept right here. Right. Like what we're doing.  Is there another open shift live show that is open shift for dummies. And the door prize is a cookbook for starting yourself in the smallest possible cluster. Yeah. Yeah. Yeah.  There are a bunch of learning resources, which I'm dropping links and chat to right now. But John, specifically, is there an open shift for dummies kind of show? I would say. Not to insult Andrew in any way, shape or form, but Andrew Sullivan's. Open shift administrator office hours. If you're working on the open shift admin side, right? Like your, if your world is in this administrator view, which we're in right now, I would highly recommend joining Andrew's show. It's Wednesdays at 11. I'll drop a link in the calendar. Or drop link for the calendar. Sorry. And then if you want to get at it from the dev side on Tuesdays, 11 o'clock, there's the developer experience office hours. So if you live in the dev console, that's for you. That show on Tuesdays at 11. If you live in the admin console, the show on Wednesdays at 11. And then there's also the level up hour, which is like taking you from I'm a Linux admin to I'm in open shift admin, right? So that whole thing is that whole thing is a program. And the show is part of the program to help you level up your skill sets to get you to the point where you're administering your own open shift clusters, just like you're administering your own rail boxes right now. And John says, I'll take the admin side. Thanks. So yeah, that's Wednesdays at 11. I think every other Wednesday 11. I forget it's okay. That's why the calendar link is there folks. It'll keep me straight. So I think. Not quite yet. So the way this works, right? Like, let me get this straight. Seth, Rook, Nuba, that's how things get installed, right? The kind of Rook, Seth, okay. And then, and Nuba, I mean, so the like Rook and Nuba, I think actually attack things at the same time, but, but separate. Yeah. Yeah. So Seth. So Rook is the operator for Seth. Rook is the upstream. Okay. Got it. And Nuba is the operator for all the multi-cloud gateway stuff. So are we good? Not yet. I mean, this says one running, running, running, running, completed running, running. It looks good. As soon as those are like, they're marked as. What is the deal? Oh, so the OSF operator. I'm trying to see. So it won't be marked as done. Complete running. Sorry. Until everybody's happy. Right. So OCS, right? So you're saying, so OCS is up here and then Rook and Seth, and then Nuba and all the MCG stuff. So back up here. It's common though. It takes, it does take a while. So hopefully everything's running. Okay. Otherwise we'll go investigate and ask specialists around here. No problem. Okay. You're going to contain. We appreciate you watching. And if you have any other questions, feel free to let, let us know. Let's see. Remember for OCS your statements are correct, but for minimal OCP there is. Right. Correct Lloyd. CRC exists if you want to run minimal OCP, which is open shift container platform to run minimal OCS. You actually need. No, there was what wait, there was something else that wasn't quite that wasn't one of one, unless it was completing. No, sorry, my, the new the endpoint. It's not yet done. So it's not marked as. Thank you. Oh, sorry. Okay. So the refresh look good after your refresh. Okay, it does look good. Yeah. Yeah. No, everything smart. The OCS operators. Everybody's happy. Okay, cool. Let me know in chat if you can see this better than I can, but it looks good to me. So let's look at the OCS operator real quick. It does look good. It looks good. Events just to make sure. Writing this probe failed. I don't necessarily know. Yeah, it says status running. So I'm going to take that as a good thing. Always go look at the dashboards. initialized ready. Okay. Oh yeah, good point. We can look at the dashboards. You can I mean that's always like the quick way to is it under storage or is it in the. So I like the ones up at the top just as a quick check all the way at home. As a place to be like begin. Yeah, so you can look at persistent. Yeah, like everybody should be happy. Those other two other tabs come straight from OCS persistent storage and object storage up above next to cluster. Nice. Nice. They should look out click on something make sure it's okay and happy it should be. There you go. Okay. All right. Oh, and let's just look. Can you click on object service just for sure. Absolutely. That's you. That's your thing. Okay, so here we go. When to start with the red one. Let's start with the registry. Okay. All right. Okay. Let's go on. Yeah. Key. I'll say it the right way just for you. Thank you. Okay. Okay. No, no, no. That's the, that's the idea of the show. I confuse you and then you set me straight. All right. All right. So that's a clay registry. Yeah, we'll take the latest version. Sure. It's going to install on all namespaces. Okay. As opposed to just. Yeah. I guess I want that. Okay. I'm going to try the open chest storage namespace anyway, like, like later on when we do apply that deploys a billion. It's as long. Yeah. I don't know if it matters. So let's try it. Why not. Push comes to shove. I use the assistant installer for OCP and I build a new cluster. Getting very good at building new clusters from this box. Okay. So from what I remember, when we go in and do this, we're really taking all the defaults. It's going, it should pick up, it should use new before office storage for the part that needs, we don't actually change anything. Where I remember the. Do we need an active subscription for installing the quay operator. To my knowledge, yes. Do you have, but if you're using it and like CRC, you technically have a subscription if that makes sense, right? Okay. I know I haven't run into that. Yeah. I'm Manica. I'm wondering where you're running it from. But yes, you would need a subscription to open shift. In production, for example, this. Does the quay registry replace the open shift image? It doesn't replace anything. It adds to, right? So the, the internal image registry doesn't change. This is a service that you can expose for others to use. You can do it from an admin point of view. That's really nice. Right. Like you, you can split the two layers.


Hi, my name is Tracy Takahama-Spinoza and this is a video on 3D learning. Basically, how do you combine backward design, instructional design, and universal design for learning as the best combination for delivery? I am the director of education at Connections and I teach a course at Harvard called the Neuroscience of Learning. It's an introduction to mind, brain, health, and education. And I also work as an associate editor for Nature Partner Journal of Science of Learning. I'd like to invite you to take notes as we go through this very brief video. And also to write down our website. There's a lot of free and open material for you there. I want you to think about why I'd ask you to write as well. Writing is one of the highest forms of thinking and it also extends your memory so it helps you pay attention when you take notes along the way. I'd also like you to think about doing a reflection as we finish. Three things that are new, two things that are interesting, and one thing that you might change based on the information that's shared today about design. So we're just going to go through this idea about justifying why we need to have new 3D learning and exactly what this means in terms of designing new learning experiences. I'm going to do this within the context of the learning sciences. I'm basically focused mainly on how we can leverage elements from technology and our design, but also understanding that we educate based on all of the learning sciences, including cognitive sciences, psychology, neuroscience, and linguistics culture. All of these elements play into great instructional design. So the punchline is that great course design involves a logical plan, a trajectory, or a hierarchy, or a construction of learning objectives, that it is a design that is pleasing and easy and intuitive for the learner, and that it has resources that can help differentiate amongst the different kinds of needs that your students would have. This means we have to think about understanding by design. Initially, we have to look at this in the context of mastery learning, then put this into an instructional design, and ultimately with universal design for learning. Now, a design framework can mean a lot of things to a lot of different people, but the main way that we're using the term is that rather than it's equated with teaching, but rather than just thinking of the teaching learning dynamic, it's thinking about how we have control over designing that teaching and learning experience. So we do this in connections through the learning sciences context, looking at teachers' new pedagogical knowledge, taking into consideration technology, as well as information from learning sciences. And so any question you might have, the worry about Zoom fatigue, or trying to reach ultimately better online engagement, or trying to get away from cookie cutter instruction and be more personalized with your students, having to meet curriculum standards, but still wanting to help students reach mastery in your subject area, or from going from just being an entertaining kind of a structure to actually having significant learning experiences, all of these are questions of design. So we're going to take you through these three different types of designs with hopes that you can put this into context within your own course structure. So understanding by design was developed by Jay McTie and Grant Wiggins, and it basically has three core steps. The first is to decide your objectives. At the end of the day, what is it that you hope to achieve? Then, number two, you decide on evaluation structures. What evidence would you accept that you're moving towards your objectives?  The key to doing all of this is having a clear objective. If you have clear objectives, you can easily decide what type of evaluation criteria you want to use and what types of activities or resources are necessary. So in this sense, Jay McTie thinks that design is pretty much shaped by the objectives that you choose. So are you after factual knowledge or conceptual knowledge? Are you looking for procedural knowledge or higher order thinking and metacognition? Depending on your objective, you have different tools that you can use then to evaluate and different tools that you can use to teach. It also changes the physical design of your classroom. If all you want to do is deliver facts and content, you can definitely do this in a webinar or just recording information, right? But if you're trying to get into deeper conceptual knowledge on the part of the learner, you really have to have more interactive activities and to have face-to-face meeting to be able to do that. Or if you're looking for procedural knowledge, how do you actually execute a certain type of a skill? You need to have the time to do that. And reflective activities pretty much have to be practiced independently because different learners will start off at different points and need different amounts of time to achieve that.  Within Wigan's and McTai's model, all learning is the combination of knowledge, skills, and our attitudes. So knowledge is dates, facts, formulas, conceptual understanding, skills or your ability to apply the knowledge. And attitudinal things have a lot to do with values, valuing the teamwork or hard work or resiliency. So everything we do and teach can be categorized as knowledge, skills, and our attitudes. Understanding by design, the structure of objectives, evaluation activities can be used at all levels. It can be used at the level of, you know, macro understanding, macro planning as far as what do I want to achieve as a country, as a nation, or as a state, or for this particular course, or even for this particular class that I'm teaching today. So the same structure, setting objectives, deciding how well we evaluate it, and then what kinds of activities or resources you need can be done at all of these macro, meso, and micro levels of planning. If you use this to set up an entire semester's worth of planning, you can backwards engineer yourself to your starting point. And so ultimately, where is it that you want to go, decide the topics you want to cover, and then how you will actually get there. So if you have weekly objectives, then how do you backwards engineer that to the activities of the day? This is what we do in our course, which we feel has a great instructional design that really leverages all of 3D learning. The second point has to do with instructional design, and there's been 75 years of trying to piece this together. How do you design learning experiences in a way that would actually stick? And starting way back when there was a pyramid, which got misinterpreted. But it was actually trying to look at what types of sensory perceptive benefits there were to varying different types of input and learning. Back in fifties, Bloom was absolutely brilliant in establishing this taxonomy of cognitive objectives and helping people think about a rather typical, hierarchical trajectory mentally in the mind that kids would be at a handicap. They couldn't actually analyze things if they didn't understand what was going on, right? And so this hierarchy was beneficial in structuring concept of mastery learning. Several other researchers back in the 60s, 70s, and 80s were also extremely influential in creating basic instructional design structures for their teachers, their audiences, and these still play a role in good instructional design. The work by Merrill's, Briggs, Gagne, and also Keller, and especially that of Sweller, has been extremely influential in what we deem a successful instructional design that exists today. Some of the most recent additions to this have to do with incorporating information from social emotional learning, from diversity and equity teaching, and also looking at how this all plays out if you are to incorporate more technology or to do some things online. The most recent work that we have been focused on has to do with radical neuroconstructivism. How is it that the people build off of personal relationships with one another and change their own understanding of the information once they have those exchanges? We like to give the example that if you read Romeo and Juliet when you were 12 and then you read it again when you were 20 and you read it again when you were 35, the book is the same, but because the person has had different life experiences, they will interpret that book differently, right? So similarly, you have a lot of ideas in your own head, but the minute you explain or talk about your ideas with other people, one plus one is three, you'll have different type of understanding of the information once you have that social exchange. This means a great instructional design. If we go back to Wiggins and McTye's idea, if you have a clear objective, then you can make decisions about modalities. Should things, what things should be done asynchronously? For example, individual rehearsal and practice should be done really on individual time, but there's other things that are much better off when we do things together as a group, synchronously, right? And now we have to think about whether or not these things occur online or face-to-face, whether or not we have direct instruction explicitly teaching elements or whether it's implicit and whether or not we're supported by digital tools as we do that. The third design element has to do with universal design for learning, which is a pretty fantastic concept, which comes up with this idea that we can diversify, we can individualize, we can personalize students' homework. So that this means that we take into consideration the range of learners and all of the resources we have, and then we design a learning experience where everybody gets what they need. That's the key idea of universal design for learning. It's a concept that really looks at this idea of the average as being unrealistic kind of a goal to have for education. We should all try to learn and thrive, but just teaching to the average is not the way to go, mainly because different people will need different things at different moments. Universal design for learning was inspired by architecture, which said that nobody's going to have the same experience with an educational concept. How many times does it take for you to learn something new? Depending on your prior experience, it could be anywhere between 1, 10, 20, 30, 40, 50 different times. This is Marsano's work, where he shows that it's possible that due to your own prior knowledge of information, you may need to rehearse a lot more than the next guy in the class. Universal design for learning is also based on this architectural concept that some people can do stairs, but everybody can do ramps. So why don't we design education with ramps? We use this basically lowest common denominator as an entry point for the information so that we're sure that everybody, high flyers as well as those lower achievers, can all have the access to the information that they need. So if you look at universal design for learning, it really fits in well with Bloom's idea of mastery learning. In 1968, Bloom really pointed out for us something that's still true today, that the main variation in an individual's ability to learn in your class, basically he said that everybody, you know, pretty much over 90% of the kids in your class can learn anything that you throw at them, if and when they have enough time. The key variable here is having time to reach mastery. Do you have enough time to fill in your gaps of prior knowledge if you come into a class missing core elements or core notions? So time is the key variable here. You cannot add more time to the school year typically, so the idea here is design. Can we design a structure in which homework is more personalized so everybody gets exactly what they need? So universal design for learning means that you have clear objectives, you use a neuroconstructivist pathway and trajectory for learning or curriculum to get to those things. You are able to supply opportunities for differentiation in order for everybody to reach mastery goals. You use all of your tools, tech tools as well, in order to scaffold that learning and that you have transparent instructional design so everybody knows where to find all of these different resources and everybody can get and use what they need. Treating people fairly does not mean treating them equally. Different people are going to need different things at different times in order to be successful. So the main two questions that need to be asked to successfully create universal design for learning is what is the range of my learners and what are the tools and resources that are available to me? And once you've figured out those two things, what does my highest level look like, what does my lowest student look like and you know what kinds of tools are available in your setting, you're able to now create or design the best learning experience possible for the widest range of learners. That is universal design for learning. Some of the main lessons that we've learned by using the lens of the learning sciences is that information about cognitive load. A good design means that there is distribution and timing and frequency of information. The design is intuitive, that there's hyperlinks and repetition and colors that actually lend to an individual's navigation of the information. We've also learned from memory systems and attention systems with our both the vital for all learning that if we do things like interleaving where we teach something, leave it alone, come back to it, repeat that we reinforce memory tracks and therefore learning. We also know that things like frequent low stakes tests are a fabulous way of rehearsing memory in the brain and also bringing that information to the fore when it's needed. And so learning sciences have contributed a great deal to design in this sense. And the biggest area most recent impact has to do with emotions and cognition. There is no cognition without emotion. Physiologically speaking in the brain, everything that you experience in life is passing through this filter of emotional interpretation before you get to this cognition level. And so taking that into consideration to create learning environments that are safe where kids dare to air, where they can have the opportunity for do-overs if necessary is also something that's very important. And to reach this ultimate goal of school education of great and metacognitive development, mentalities such as shifting from an idea of feedback where you lament what you did, right, to an idea of feed forward, what will you do better the next time is something that's very key within the learning sciences. We also encourage doing getting to deeper thinking using flipping as a classroom instrument. And finally this idea of differentiation and personalization by creating a structure and universal design for learning where you can personalize everybody's homework. In our course we do this through bundles where students get to choose what level, what entry point of the information they want from the different resources that we have there. And so this allows for students to fill in their own gaps of prior knowledge that may be existing so that they can all reach the same objectives we have in the classroom. So the final big idea is that design is necessary for good teaching. We have to know our students well in the range of tools that we have in order to be able to do that design that technology can lend itself towards that as well as information from the learning sciences. And that we can learn to leverage that same technology to save us time so that humans can do what humans do best, motivate kids for example, as opposed to what machines might do best. They can quickly score an exam for a kid, but they might not be able to give him that encouragement to keep working hard to improve the next time. The idea here is to leverage technology in the best way possible. If you look at the collective models for instructional design and universal design and for backwards design or understanding by design, you can meet standards and you can meet school objectives at the same time reach for master instruction. And if you're interested there's a couple of great books that are out there that I'd recommend. The final big idea is that great design means that you have a balance of asynchronous and asynchronous activities, as well as things that are done individually as well as collectively over a longer period of time. So it's not just that it's one and done. You teach it, you have an exam and you move on, but that this becomes lifelong knowledge that you're able to continually reincorporate that information into your own personal life experiences. So to include great instructional design has clear objectives. You can document learning advances so that your evaluation criteria become much more transparent, and it uses a balance of synchronous and asynchronous activities that we remember from the learning sciences we have to stimulate that prior knowledge, create authentic understanding, and fill in gaps of requisite knowledge that might be missing for students, and then leverage the most appropriate pedagogy within the classroom structure that we can for the age group, subject area, and range of learners that we have, and that we use our tools. This means designing the right balance of individual activities to group activities from synchronous activities to asynchronous activities, but always keeping in mind that individual learner and being able to tend to that person's needs in order to make the entire class advance together. So in this brief video we looked at design thinking, understanding by design, the history of instructional design, and universal design for learning, and hope that you can now take the time to do a 3-2-1 reflection to document what learning you have taken away from this video. Thanks and let us know if you have any questions.


Hello and welcome to the session. In this session, we will discuss a question that says that suppose 800 people are surveyed, the table shows the results of the opinion of males and females on an environmental board issue. And here we have given the joint and marginally related frequency table. Now here in the first part we have to find that out of 800 people surveyed, what percent are males and females. And in the second part we have to find what percent of people are for and against the bond issue. Now let us start with the solution of the given question. Now in this table we are given two categories, one is gender that is male and female and other is opinion that is for and against the bond issue. And in this table we are given the joint and marginally related frequencies. Also here we are given male and female in rows and for against in columns. Now in row one see the cell corresponding to male and total which is 0.75 is the marginally related frequency for males which tells the proportion of males in the survey. Now when we multiply the proportion by 100 we get the required percentage. So percentage of males in survey is equal to 0.75 into 100 which is equal to 75%. Similarly in row two see the cell corresponding to females and total and it is 0.25 so marginally related frequency for females is 0.25. Now this marginally related frequency gives us the proportion of females in the survey so percentage of females in the survey is equal to 0.25 into 100 which is equal to 25%. Now we have to find the proportion of people for the bond issue. Now people include both male and female for this we see column and here marginally frequency that is marginally related frequency is 0.76. So required percentage is equal to 0.76 into 100 which is equal to 76%. So percentage of people for the bond issue is equal to 76%. Also the marginally related frequency in column two is 0.24 so percentage of people against the bond issue is equal to 0.24 into 100 which is equal to 24%. So percentage of males in the survey is equal to 75% percentage of females in this survey is 25% when percentage of people for the bond issue is 76% and percentage of people against the bond issue is 24%. So this is the solution of the given question that's all for this session hope you all have enjoyed this session.


I'm really interested in how the coast changes over time, and that could be a beach and a dune complex, it could be a barrier and an estuary, it could be a rock shore platform, it could be marine terraces that you see, and they will change and evolve over time, and I'm interested in understanding that change in those different coastal environments. So I look at how estuaries infill and change over time. So for example I've looked at the Manawatu estuary that on a global scale has changed really, really rapidly over the last 10,000 years, and it's infilled, it's been filled with sediment coming out of the Manawatu river, and there's something like 14 cubic kilometres of material has gone into what is now the Manawatu coastal plain to change it from an estuary to the coastal plain where you've got the towns of Palmerston North and Foxton. In the context of say understanding an estuary and a coastal plain infilling, so many of New Zealand's towns and cities are actually built on coastal plains, so the whole of the Manawatu, we've got the Heratanga Plains in Hawkes Bay, we've got the Poverty Bay Flats up near Gisborne, those are just the Canterbury Plains. Because the coast is so dynamic and changeable, New Zealand, we've got everything here, we've got rocky coasts, we've got barriers, we've got estuaries, so you can work out the coast and still do something different every day, every year to understand that bigger picture of how the coast changes.


Thanks for joining us today. And welcome to Open Infra Live, the Open Infrastructure Foundation's weekly, hour-long interactive content series focusing on case studies running in production, open source demos, industry conversations, and the latest updates from the global open infrastructure community. We have some great content coming up in the next couple of weeks. And we hope that you can join us every Thursday at 14 UTC streaming on YouTube, LinkedIn, Facebook, and Twitch. My name is Kendall Nelson, and I am an upstream developer advocate at the Open Infra Foundation, and I will be your host this week. So today, we are streaming live and would love for you to drop questions as we discuss our topic into the comments section of wherever it is that you're watching this. And we'll try to answer as many as we can throughout the show. So let's get rolling. Today, I'm being joined by some really awesome people, many of whom I've actually had the privilege of working with directly. And I will let them introduce themselves, and then we can jump into today's discussions about mentoring programs and onboarding into the OpenStack community. First up, we have Victoria. Would you like to introduce yourself? Of course. Hi, everyone. I am Victoria Martínez de la Cruz. I'm originally from Buenos Aires, Argentina, currently in Madrid, Spain. I'm a software engineer at Red Hat. And I started on OpenSource because I was a really power user of OpenSource at a very young age. And I was really amazed by tech and how people share their knowledge in this community. So that's how I become a contributor afterwards. Thanks to Aricy. Nowadays, I'm working as an option developer for the OpenStack Manila project. That's the share of my system as a service for OpenStack and also wearing other hats within the community at Red Hat. Aikana Kumari, up next. So hi, everyone. This is Akshna. I am a competitions graduate. And I am currently interning here at OpenStack as an outreach intern. I have started my OpenSource contribution with the Haptable Fest back in two years from now. And now I'm currently here as an OpenStack intern contributor, so Ashley. Thank you, Aikana. Hi, I'm Ashley Rodriguez. I recently graduated from Boston University with a BS in computer engineering. And I am currently living in Boston. I started working with OpenStack through my senior design course. My project was to establish the foundation for Manila support in the OpenStack SDK. And we managed to push code for all the resources listed in the first two priority buckets in the spec. Currently, we have a outreach intern continuing what we started last fall. And I was also just hired by Red Hat as a software engineer. And I started in late June. Fatima. Hello, I'm Fatima Khaled. I live in Cairo, Egypt. That's where the parents are if you're familiar with them. I graduated from Cairo University majoring in computer engineering. I interned in OpenStack throughout Ricci in my third year of college. Kendall here was my mentor. And also, I interned in Microsoft around the same time as well. After graduation, I worked in the testing field of automotive industry for Belial for over a year. And then I switched. I'm currently working as front-end engineer in RISA for oil and gas, which is headquarters in Denver, Colorado. I was first introduced to open source in college. The whole concept of being open, sharing the code with the users, for them to maintain, customize, and solve the issues was just fascinating for me. I heard about some programs that support the students to contribute. And that's where I knew about outreach. And I found Storyboard to be the most interesting project for me to intern in. And that's where I did my internship. I also continued on contributing. I contributed in SWEFT, which is another OpenStack project. Afterwards, and still contributing in Storyboard as well. Currently, I have posed on contributing for a while, but starting my recent job and this hustle, but stable now, surely I'm planning to go back contribution. It's always beneficial, whichever career level, on both technical and non-technical aspect to be a contributor. Moving to Dawson Coleman. Yeah, I'm Dawson Coleman. I am a software developer at Lullsbot 3D printers. We design and manufacture open source 3D printers. We're based out of Fargo, North Dakota, USA. My involvement in OpenStack actually goes back to my time at North Dakota State University, where I was able to participate in the OpenStack Octavia project as part of my Capstone project, which is essentially where they throw out a bunch of projects. The students get to pick them. And we get to work on it for a semester to get some real-world experience. I thought the open source aspect was really cool, because now the code that I wrote is still out there. I can still go look at it. I can still go visit it from time to time, rather than it being locked behind a closed door. And Cloud Software is super cool. So that's kind of how I got involved. Awesome. Thank you all for your introductions. Let's jump into the first question. So I'm sure you all obviously learned a lot when you came to the OpenStack community.  Fatima, do you want to go first? As a student, for the first time working remotely gave me a great sense of independence. Also, it was my first time diving deep into such a large code base. On the technical aspect, this gave me a great deal of debugging skills. Also, I learned how to navigate my way around the huge code base and fit my code pieces into it. And on the technical aspect, I have learned so much about working remotely and with different time zones. The time difference between us was about nine hours or something. So I've learned so much about that. Also, I really enjoyed working with different people from different cultures and different backgrounds with different perspectives. This added more depth and variety into my full process for both technical and non-technical issues. And finally, I really got the actual chance of meeting those people live and team gathering and in the summit as well. Anyone else? Something that was great about your experience? Oh, sorry. Totally relate to that answer. Like, I love it's being able to work in a community that has people all over the world with so many different cultures with different, like being in different time zones, remote, and all being able to, like, even though we have that distribution across the world, to be able to collaborate effectively. That is something that you cannot get elsewhere. And we are also developing very complex code. Like, we are basically doing software to manage data centers, right? That is key gas. And that is something I believe, like, in my case, I think that I wouldn't be able to do that in a specific place. Open source community is the only place I actually could find out. So totally relate to the answer, Fatima. I mean, yeah. I think I had a pretty enlightening hands-on experience with Git. It was a little hard getting started learning all those commands. It was my first time really working with it. And it was interesting, to say the least. A lot more confident in my Git skills now. But I think the greatest part of my experience with OpenStack so far is all the connections that I've made and the things that I've learned from my mentors. Victoria, she was one of them. Great help in getting started with Manila. Very generous with her time, very supportive. And that's something that I think Open Source community is very good with, is just always being there to help out the new contributors and just being overall the best community ever. Yeah, I think to echo kind of what they were saying is kind of the ability to work on a real-life product. Like this isn't just some toy program that you're copying out of the textbook. Like real companies are using this for real products. So that was kind of a big step up from anything that I had seen before in terms of the scale and in terms of like, oh, we have a complete test suite that we actually rely on. Like, oh, we're not going to let you merge if it's not pet bait, which are all great things. But if you're coming from an environment where that's kind of an afterthought or non-existent, that's a new thing to kind of wrap your head around. But it's great to see projects that are a model of that and be able to see like, hey, here are people who are putting all their stuff out in the open and you can just kind of learn from that workflow. So it's something that's really cool to be able to see and kind of model things after. I know I feel really cool knowing that code that I've written is running at like CERN and maybe potentially at Blizzard and all of these other companies that like you use every day that, yeah, it's awesome. So awesome to be a part of this community. So obviously there are tons of fun things that we all have learned of working in open source but what was the hardest part of getting started in the community? It could be technical or non-technical. Archana, you are the newest to the community of all of us. So do you wanna start? Yeah, sure. So hardest part of getting started was basically finding the right community or their project, which is closely matched to your passion in which you are completely interested. So when I found this and got into the Outreach Internship Program, the challenging part was about getting started was to set up the whole DevStack environment. But the whole process seems to be tough in the beginning but thanks to Victoria, my mentor who completely helped me and it was manageable at the end. And yeah, so this was also my first project with such large code base so making myself familiar was a bit challenging too. So yeah. Yeah, no, I think at the beginning of my journey into open source contributions, the biggest obstacle I had was gaining access to the right resources and to actually be able to contribute. Since my introduction was really through my university, I had a limited avenues that I could use. AWS was frankly too expensive for a college student. And it just was an issue also with my teammate trying to get some stuff with the MOC and it was just a lot of bureaucracy and red tape that we had to go through. And that was a bit of a hassle. But in the end, Kendall was actually the one to get in contact with the CEO of Vexhost and he generously provided us with some free accounts to be able to start and run a bunch of virtual machines. And then from there, it was just smooth sailing. So excellent work, Kendall. More of Vexhost and Muhammad. They were the real MVP there but happy to make the connection. I'd agree with Archana. The start is kind of tough because we learned from those hard parts but given I had both experiences on maybe parallel if I can say, open interning in open stack was showing such time flexibility and remotely working with open community on the other hand, I was interning in Microsoft which was a corporate which is a corporate with the closed source and we were working from the office. I found the open source facing some challenges about communicating with others with different time zones and working with people that I have never met. It was a bit intimidating but eventually after like breaking the first ice people are real friendly and they are they just jump to help whenever there is a question. They, you might never talk to this person before but they are just, what's your question? Let me help, log me and send me the logs and it's really nice there. So it might be or look like it is rough but it's just way to go. Anyone else have other hard parts about getting started? Well, we'll come back to it a little bit and a little bit later here but we can also move on.  We have like Cairo and like a couple in the US and well, I guess Victoria you're in Madrid right now not down in Buenos Aires and Archana you're over in India, right? But yeah, so geo localization is definitely a thing and obviously we all come from different places and we're raised in different cultures and some of us speak different languages. Were there any parts of that? Were like a problem for you? Victoria, do you wanna go first? Having moved recently to another time zone. Yeah, so oh God, this question actually has many sides to it. Like I can totally see geo localization as being hard for many people. Like, well actually I saw a tweet the other way, the other day going round about how remote work is allowing people that is in distributed areas to join a tech field they want and start contributing and kickstart their careers. And I totally relate to that question. Well, to that tweet actually, like the whole cloud computing concept was quite new. It's like it was beauty niche technology. Like we were just starting there. It hasn't been so long ago, but technology is measured by dog ears. And that while computing at that moment was a more popular thing in US and in Europe, of course, but not so much in Latin America and well, I don't know about other areas, but I know that it was not so popular in Latin America. And actually being able to connect with contributors from other areas allowed me to learn about cloud computing at a very young age, I would say, and very early. But afterwards, like being there, it was really hard to find my next step. Like I finished my internship and there were not so many companies doing cloud computing, right? So it was like up there that I couldn't feel right away. And I totally see this happening in other areas in which maybe a technology is more popular and it's more adoptive in some areas and it's not so much in some other countries. And being in that some other country, if you have to be inside, it is not easy at all. Therefore, one side from the geolocalization aspect and for the culture and language barrier well, I still cannot forget my first OpenStack summit, it was in Poland. And well, I couldn't speak English as fluent as I wish.  But I could actually communicate that to you, to the people that I have around. Unfortunately, I think the OpenStack community did a great job about that. Like usually like, since everybody takes into account about this situation, like everybody is very patient, everybody waits until you try to finish making the sentence and communicate your idea. I also implemented some other techniques in some cases like, I don't know, writing down stuff instead of actually speaking up. And that helped me a lot. And that helped me become more proficient in English, of course, and be able to be more connected, more engaged and move closer with the community. Which is already a community that moves really fast imagine if you get half of the information. So, I think that open source, remote work, there are things that are helping people, like very talented people to kick-start their careers and to reach to their next level, which is something great. I totally agree with Victoria here because given the current situation and how things have changed, the whole world is just heading to working from home and working remotely. This has been, okay, so after I graduated about five months or something, the pandemic started and everyone just were shutting things off and we need to work from home and we need to know how to work concurrently and sing things. My colleagues were, so they are seniors and stuff, but I have this skill because I have tried it before and I had the tools from my internship. So, it may have been a challenge but this challenge was just such beneficial and gave me a great edge in my CV and got me to currently working for a company with the headquarters in the U.S. So, it's really beneficial although it might be a struggle or a challenge at the beginning. So, totally agree. I know we as an open-sec community do as much as we can to make it welcoming in as many ways as possible. We, you know, list meeting times in UTC so that everyone has the same amount of pain doing the time zone conversions and we try to have everything text-based so that if you need like a translator, you can like, you know, pipe the logs through that. And yeah, we try to be as friendly and open as we can being an open-source community. So, we kind of touched on this so we kind of touched on some of the other blockers that you have but were there any specific technical blockers that you may have encountered? I know when I was working with Dawson on Octavia, DevStack gave the whole team quite a bit of problems if you want to talk a little bit about that. Yeah, I have never complained about DevStack before. No, so it was obviously, you know, it's a little more complicated than your little, like, hello world type-in-a-number script, you know, that you get in CSI 101. So it was really interesting when we kind of had our meeting and we were suggested that we needed about 16 gigabytes of RAM to run this and like, oh, so for our computer and they're like, no, no, for your VM instance and that's not something that everyone has lying around. I'm fortunate enough to have a computer that can do that but another guy on our team had a laptop with four gigs of RAM and that was his workstation. So there is the aspect of getting all that worked out. The computer science department at NDSU was generous enough to provide us with a pretty beefy server for getting that done but of course, you know, that also adds on the remote management part of that which was a good learning experience with some pain points but yeah, I certainly have to give a shout out to Michael Johnson here for patiently working through all my issues and my load balancers inexplicably not working and all the little things that came with that. I can't tell you how many times I just completely deleted OpenStack and reinstalled but we got there. I think a funny story with that is the thing that I was told to do when something didn't work was to start from scratch and we ended up getting throttled by the university I think because after installing it like once or twice, my download speed would go to zero. We never got that part figured out but it was certainly something that showcased just the welcoming aspect of the community and just how many people were out there willing to solve all our dumb questions so I think we really appreciated that a lot. Definitely just scrap DevStack and start over like people that have been working on OpenStack for five plus years that's definitely a very common MO we just like, yep, kill it, make a new one, it's fine, whatever. We can dream. Yeah, maybe someday. Anybody else have technical blockers that they ran into when they were getting started? Oh yeah, so my biggest fear about, well, eight years ago nowadays I feel more comfortable with it but it was good, like in fact I started calling it it's like it's a nunchaku. You never know when you are going to hit with it in your face and at the beginning I was really like a newbie like I didn't understand anything of what was going on and every time I had to execute a good command for me it was pure stress and fear that I was going to lose everything and I was going to, you know, I don't know start stepping on to some other people's job but it was like, it was fear I think thanks to my mentor, Shuli, she, I'm back. Yeah, I think we lost you for a sec, but you're back now. Okay, cool. So yeah, it took me a while and even now like when I see people struggling with it I really, you know, get in their skin and it was like, okay, I got this. We are going to do this and that and everything is going to be fine and that's how we solve things, but I guess Victor has done but I really wanted to build on that because I just was learning AngularJS to start with my contributions and I thought that this was the technical blocker that I have it's so large, a really huge good base but then I got the work done and I cannot count how many times I'm just on camera and I got pushed but I couldn't publish it I do not really know how it goes and then many times I got detached heads and many times she helped me oh my god, that was so much but I managed to learn that through the internship with mentoring, I got over it and now I'm killing it I just can't solve any issue that with any other colleagues so it's a really, really good journey that you cannot get anywhere else to know the process, the review and how to use the right comments so it's totally beneficial might be a little thing Yeah, Git is definitely not the easiest thing to work with in the world but I do think that Git review and Garrett is a little bit better a system than GitHub which I know is a controversial opinion but yeah it looks like we have some people David Medbury totally awesome community member he was talking about his Git and Payne's as well and totally agrees that Garrett is the best open source tool but yeah, thank you for engaging today on YouTube and LinkedIn and stuff definitely keep sending your questions in and comments and we'll keep showing them so thank you for participating everybody so for each one of you what is the best thing about working in an open source community obviously there are tons of things I have a lengthy list but if you could only pick one thing what's the best thing Victoria do you want to start? Sure, all right I think the best thing for me about working in an open source is that you get to work with the best people like in each technology like the most experts, the most experience and all my colleagues they all have so much experience and so many things to share that is something that it's something I appreciate a lot actually well, in some open infra summit I would run into some person and somebody else would say you know this guy, this is the creator of SEF and it's like oh god can I talk with him? it's like a super start to me and having that possibility is something you don't have everywhere so I totally see that's one of the most important part of being in an open source community What resonates with me is that you are free to choose what you're working on you just go find a project that's interesting to you and you genuinely care about either as a user or might be technically the technical aspect of it that you are interested in working on it's just not that it gets better because you see the future that you have worked on or initiated yourself in the hands of the other users as well around the globe anyone can use it as well and sometimes this user is yourself so adding a feature that you needed or fixing something that just was aching you it's just perfect also you always end up learning something new and it's quite about the output and the product and the difference and you just can't see it out there so it's perfect because next Archana you want to go next yeah okay so if I choose the best thing about being in an open source community then I can choose a mentor I started my journey with OpenStack with my mentor Victoria she helped me so much when I saw her tweet on Twitter she is finding someone for the OpenStack Manila project I just reached out to her and she helped me so much like giving me a way like how can I start with the project joining also join IRC communication channels and what I have to do next also assigned also helped me like choosing bugs to work on and the hardest part in that was like the code the codebase was in Python but like the support she gave me like understanding whole codebase and working on fixes that was like that's part like choosing a mentor helped me so much in that thank you yeah I think for me one of the obviously other than the aspect it's awesome to be able to work with so many like minded people I'd say another thing that was unique especially from the especially when you're able to do it as a part of a requirement for something else like for school or for work is that usually when you are doing that sort of work it's for some sort of proprietary need or purpose and you can say that you participated in it but once you're done with it it's kind of behind closed doors but the thing I think is cool about the open source contribution side of that is you kind of still have ownership of the code in a way that someone who's working for a closed source product definitely doesn't have so I alluded to it earlier but I can still go back and I can look at Octavia and I can see what I did obviously I don't run load balancers in my basement as of now but it is cool that in that aspect you know I still have some sense of ownership in that and I think that's something that you don't really get anywhere else you know I think my absolute favorite part about being part of this community is the community itself very collaborative very supportive I mean I literally spent hours talking to my mentor Gotham working out some differences between the documentation and what I was getting on my local machine and I just I have never seen that happen anywhere else where I can like work on a problem for hours if not days with someone and they're just there with you know any answers to what I like the questions I may have stuff like that it's just so satisfying to have someone there to you know help with a problem and then finally getting it fixed getting it done the sense of accomplishment that you get with you know working that and then with your team as well it's just amazing awesome well so comically enough Gotham actually just commented on LinkedIn and asked what is one thing you want to do to make the community more inviting to a new contributor like you so if you want to answer that Ashley can start or whoever if you have an idea I just say that you should they should people should know about the opportunities some pretenses are just need some digging to be out there so they are doing outreach for example they are doing great job about advertising about themselves and inviting people it has been to my to the extent of my knowledge it has been spreading more and more and this is they are achieving more getting to more audience so keeping that going is what will I think get more people to contribute providing the opportunities that the open source is already doing and just promoting that these are opportunities that are there that you can always just touch the code fix it and that's you did the new job and you did a great work and we are all supporting you it's just once you get in there you cannot go out it's just pulling them you know I have to agree there's I was in a unique position in that my introduction to this was through my university through my coursework so I never saw anything about hey do you want to join the open source community or this is what we're about or this is how you can get started I never heard of the outreach program until I had already been introduced to the community and then I would see all the information that's out there but I think getting more to share I suppose or just get the word out there is something that would be beneficial so doing things like this today hopefully awesome anyone else want to answer what is one thing you think you can do to make the community more inviting to new contributors like yourselves I think the sort of like outreach or just knowledge that it exists is a big deal because going into it I was pretty intimidated sitting down and looking at all the code like oh boy what have I gotten myself into but you know the part that made it you know really great was that all the people involved were actually really willing to help me I think I was told at one point oh yeah just ask me about anything even if it's how to CD into a directory so I think that's something that is super helpful as a beginner it's maybe not necessarily obvious if you've just never interacted with the community but you know once you know about that it really flows naturally from that I think especially in open stack awesome well looks like we got another question in here it's kind of a little bit more general but besides open source what led you all to software or technology as an interest and a career so actually the summer between sophomore no junior and senior year in high school that summer I did a girls who code program I was like seven or eight weeks and we touched upon you know just introduction to software we did some scratch we did some python we worked a little bit with a tiny robot and that summer was the best summer of my life after that I was like okay technology software development this is something that I want to explore that I want to learn more about that I want to work with and then that senior year I applied to a whole bunch of engineering colleges universities just hoping for the chance to learn more and do more in this field and I was lucky enough to get accepted to Boston University I completed my bachelors and I am so happy so satisfied so proud of this field like it's just amazing you can do anything and it's just great well for me I was like in my ninth grade we study computer we study coding with visual basic at that time so I had my little brother he was about four years or something I created a whole game for him about with photos and the names of what is in this photo and the feeling and the achievement of creating something from scratch and how it built up and how he enjoyed it was just amazing so I went searching and found that this is a major that you can study and since then I put it as my goal and my studying college to be and I graduated from it so I accomplished kind I can go next I guess so in my case all grades goes to my mom she is such a nerd like when I was growing up she would totally you know encourage me to do you know smart hacking scripts with the machine that we have but I remember it was an AMD K6 with very very low run and yeah I would spend some time with her learning about how to use a computer and after that I guess that which ended up kick starting my full interest in programming was like I'm going to say year 2000 I was 13 year old I think and IRC was the platform for you know making friends and meeting communities in my area so I would spend summers like just connecting to IRC and making friends and you know trying to learn about how to write plugins for IRC for the clients right and that kind of led me to open source as it is and you know the first GNU Linux distributions and well after that I started getting more involved and when I could decide what I wanted to do well obviously programming was something that was very interesting to me so that's how I'm here I should add my mom being such a nerd now she makes like she doesn't she doesn't know anything so I go there and fix stuff for her so so now you're geek squad you know yes yes every Christmas anytime go there you know fix her computer just about any time I go home my parents have like a laundry list of things that they need me to fix phones and computers and stuff so I can totally relate to that yeah no one knows how to use the printer but me well printers are just cursed I don't think there's much to that commutant about that well we still haven't heard from Dawson or Archana do either of you want to talk about how you got into technology and stuff yeah so it all started go out to Google so that's how I started my career in tech field and with that I joined some technical communities so with the help of that scholarship I started maturely in the frontend development things which I imagined so everything was like when I started frontend it's like I can build anything what I can imagine and the community there was like so supportive like whatever the help you need there are always so many people out there to help you also after that I started join some technical communities and arrange some workshops or events meetups and all so yeah that was quite interesting and that's how I started in my software development yeah for me I think like it was for a lot of young boys I think I can trace it back to playing video games and kind of saying like there's someone who could make this it'd be so cool to like have an idea and then bring it into reality and I think I kind of pursued that through just learning having opportunities to learning to program and all that but I think like as of today I'm not a game developer and don't intend to be but it was more of a matter of falling in love with the process I guess and sort of just you know being able to dive deep into something technical and just just being able to think something and then make it happen or just that kind of like first principles reasoning where you can if you know the more you know about something just being able to break it down and rebuild it better like I think that's just the coolest thing ever and that's kind of what's driven me through my entire career awesome yeah there are so many different ways to get into like technology and then open source but I'm glad we've all found our way to open staff together through different paths so maybe one final question before we start wrapping up here about advice so what is like one piece of advice that you would give to somebody taking their first steps and getting involved in open source or open staff specifically Archana do you want to go first again yeah so what advice I can give to future contributor like if you're done making the organization and your project make sure to read the documentation of that project and this is going to be your friend to your entire journey of the project and also once you are done picking some issues or business issues or your mentors are going to assign you some issues this is not going to be solved in one or two days this is the that's the learning process you're going to enter it's going to take so much effort and so much time of your year and it's going to be a learning process for you and if you get stuck somewhere reach out to your mentor and the community member and if somehow it's everything not things okay and you can also choose the stack workflow or some other developer forums yeah yeah you go ahead no I definitely make use of the documentation there is a lot of information out there on what tests have to be written the code style checks you have to pass just so much out there and then once you kind of know what it is that you have to do if you don't know where to start I would recommend looking at the code that's already been published look at what other people have contributed and see what their style is what methodology that they use what functions they write what they make use of what was going on how did they get to where they got and then just kind of use that write your own code and then ask someone to review it obviously post it to Garrett and if you're not getting the attention go to IRC and say hey I need a little help can someone pick this out for me and they will so definitely do that just cannot agree more with Ashley and Archana it's just you need just to start the advice to start is just to start dive your head first it's the challenge is how to start so just start clone the repo read the documentation of the how to build and you will definitely find the issue that you had in the documentation if not you will just go and ask someone ask on the IRC and you will always find someone in your time zone or out of your time zone maybe a while later but there's always someone who would answer so just dive with head first and the community will catch you I think one of the best tips that I received was don't be shy because if you don't ask questions you're not going to get answers and I think I'd really break it down into two different pillars of you know what it takes to have productive conversations with people first I'd say don't be shy and then second just you know value other people's time just you know make sure you're doing your due diligence with the issues or your troubleshooting as I know I it's easy to get frustrated and you know maybe I would just say like hey my load balancer isn't working just trying to you know that that little extra step of you know just trying to explain you know everything that you know and you know realize that there's another person on the other end who wants to help you but at the same time you know needs you know maybe some background or you know doesn't you know only has so much time in their schedule you know the cool thing about open sources we're all volunteering it our time to each other and I think so long as you know you you know you you're aware of that and but also not being afraid to participate in that I think it's really hard to go wrong regardless of who you're collaborating with really really good advice yeah Victoria I think you're the only one that hasn't answered yet yeah and so well actually my my advice is quite similar to the one that Dawson just mentioned like I think that contributing to an open source community teach you how to make good questions like you like time you will learn that considering that how busy is everyone in the community and you know how fast things move is like every time you hit an issue you try to summarize everything in a single line to explain what's going on with your with your environment and you go there you ask and well being able to do smart questions is definitely as questions in the smart way that's a different thing I hope that you understand me but that's something that is very a very good advice and related to that make connections don't hesitate on asking people like as mentioned like everybody is quite busy and there is a lot of things going on but everybody is willing to help and you don't need to be blocked in I don't know for one week with a single issue if you have people in the community that may be able to help you out and get you right back at where you want to be in no time and also those connections help you to get to your next place like to the next step so making connections learning from them sharing with them is very very important that is excellent advice as well it's all about the connections and our successful community because we like focus on communication with one another and open communication being one of the principles of our community definitely makes for a more successful resilient strong community and better software as a result so we've kind of talked a little bit about the outreach program but Victoria maybe you want to talk a little bit about the next round and stuff of course I always love talking about Orichi so Orichi is a paid internship that aims to bring underrepresented people to contribute to open source communities these internships last for three months and the whole process is that interns are paired with mentors which are contributors in the community and those mentors guide them through the whole process both in technical matters of course as we just discussed but also from the career side career advice and helping them make these connections that we were talking about currently there is a round that is ongoing actually Arcana here is part of that round and next round is going to be on September the applications open in September is due in October and the next round is going to be from December to March next year the goal for Orichi is to increase the diversity in open source and well after I think it has been at least eight years in OpenStack and probably more like before OpenStack it was only for the Genome community I think it's a bit more than 10 years I will ask somebody in the Orichi coordination to correct me if I'm wrong but after 10 years a bit more 10 years of doing this well there has been a representation from groups that historically it has been contributing to open source well obviously it's working because our panel here today is like mostly women instead of men like normal so Jocelyn you're in the minority today but yeah so aside from Outreachy we have the Grace Hopper open source day coming up in July it is a free all day hackathon that includes workshops the OpenStack community will be participating so if you're interested in getting started upstream I advise you look into the open source day all skill levels are welcome our focuses are going to be on like getting you started in the community getting your environment set up helping you push a patch to our test sandbox repository it looks like according to the website there are about 730 spots left but it is like a global event so I'm guessing it will fill up so go check it out if you're interested and then if you're not able to attend that or get into Outreachy or you're not lucky enough to have a community that works with OpenStack like Boston University or North Dakota State University we have other resources accessible all the time so we have the contributor guide which basically goes over all of the introductions basic basic things about getting into the community our structure our governance how to get connected to IRC and set up Garrett teaches you some get commands which we kind of talked about as being a little bit difficult sometimes and as you go through the contributor guide you have questions please reach out to anybody in the first contact SIG we have a link here that has a list of all of the people that are involved in that SIG and their time zone and also their IRC nickname so hopefully you can get to IRC but if not we have mailing lists that you can send to and be like help I need help and then we also try to do a training a like virtual lately because coronavirus but sometimes in person upstream institute and that covers everything that is in the contributor guide we have talked a little bit about running a virtual one later this year so if you're interested in doing that keep an eye on the docs.openstack.org and when we get dates they will be there so thank you so much to all of our awesome guests today you've been fantastic we really appreciate you joining us from all over the world if anyone in the audience has an idea for a future episode we would love to hear from you you can submit your ideas at ideas.openinfra.live submission deadline to be included in like an August or September episode would be this Friday actually July 16th so get them in next week we have another great episode lined up we have guests joining from Canonical and City Network and Morantis and also T-Systems to talk about current job openings company cultures and what they're looking for in candidates so if you want to get a job in open source you know building off of today's episode definitely tune in next week and mark your calendars we hope you're all able to join us at 14UTC for next Thursday thank you again to everybody joining me here today Victoria, Archana, Ashley, Fatima and Dawson you've all been amazing and we'll see you next week for another Open Infra-Live episode thank you for having us thank you thanks


Hey, you ready to watch this week's request by Jason Willis? Oh, yeah, mausoleum! What did you just say? Mausoleum! Uh, it's mausoleum. No, it's pronounced mausoleum.  Hey, man, don't say I'm wrong. You'll be sorry. Or what? You'll put me in a mausoleum? Ah! Sit! Sit mausoleum!  Oh, yeah! It's mausoleum! So it's mausoleum! Ah, yeah! Sit mausoleum! Uh, sit! It's mausoleum! Sit! Sit! It's mausoleum! Uh, ah! Sit! Sit! It's mausoleum!