Micro-learning is one of the most important trends in education and training today, but what is it? And more importantly, why should you care? In this video, I'm going to explain what micro-learning is and how it can benefit you, your organization, and your learners. In today's fast-paced world, we're always looking for ways to learn more quickly and efficiently. That's where micro-learning comes in. Micro-learning is a popular learning method that focuses on delivering small, bite-sized pieces of content that can be easily digested and put into action. It's perfect for busy adults who want to learn new skills without having to commit to a long, traditional, educational course. Information taught in micro-learning formats can actually be retained more effectively than traditional methods. There are many different types of micro-learning content, from short video lessons to interactive quizzes to mini e-learning courses. The key is that each piece of content is focused on one specific topic or skill. This makes it easy to find and use the information you need when you need it. If you're looking for a quick and easy way to learn, micro-learning is the perfect solution. When done well, micro-learning can be an effective way to help learners retain information and improve their skills. If you're teaching or training online, don't miss the URL Doctor's free educational series on micro-learning, e-learning, and learning management systems. Visit our site at theurldoctor.com for more information.


Hey guys We continue with our rusty project and guess what showed up check it out Okay, that's one That's two Wow, okay. I think they ran out of bigger boxes You think this was enough? Okay, so we know where these are gonna go And we got a bolt Which was from rack auto You see the part number there, so this is the old bolt not factory It's actually thinner than the One that's supposed to go on there. Let me show you look at this No bueno. Look at this still some play but much loose I mean a much tighter and That's even this bolt is even worse in the knuckle a Lot of play in the knuckle and this I actually have to slightly force it Into the knuckle. So this is a nice tight fit. All right, let's install these are gonna use the same tool. I Have used to remove it But I actually forgot What I used well, I mean, I mean I know I use this but I forgot what Ends I have used or adapters You know what I mean, I did clean out the rust more or less But it is well, it's not bad bad, but it's not good And I did lubricate it with TV blaster or WD-40 don't lubricate with oil TV blaster and you know stuff like WD-40 is based on water. That's actually what W stands for in In WD-40 and this will evaporate over time oil would not maybe I don't have to use anything just straight in Just get it started Yeah, that's what I'm gonna do. I did him on under impresa the ice racing project I Think like half a year ago or whatever was but I we had these out and I didn't I put them in the in the press. It was very easy actually Need more lubrication a little bit more. Maybe we're good. We just need to just need to work this out From inside the arm Well, maybe not just leave it like that. I have found an adequate adapter nice Just gonna use that. This is gonna take a while. I really need to do this. Oh, yeah, yeah Or should I just forget about or drag it in more? So this actually comes out and then drive it back in Left that's what I'm going to do still man, I think it's the Rust can see this part has been chewed away from here to to about here and this This is the actual length of the order width of the You know control arm and this is much narrow You can see how this is kind of a missing part or maybe it's Squeezed and this metal is thicker over here. Okay rubbers out but You know me being me the inside that metal part is sticking out Too far to the right and I just don't like it. So what I need to do is Where's my other piece? Oh, I actually found the thing that I was using before it was right there This is actually well same Now I have two Wish I could fit this. Oh, okay Check this out that works Perfect. Okay, now the second one Tornado warning. Well, no tornado yet, but I had a situation Well, no one of my rain barrels was over overfilling got clogged and And I got a little wet my shoes my socks are soaked Anyways back to the automotive world. Both bushings are in. All right. You already saw me take it apart I'm just gonna put it all back together with the strut everything basically. I'm gonna show you The result well no tornado yet But this is done now use a jack of some sort You know jack it all up went right through No issues there use grease on the bolt guys. I just had some grease On the whole bolt. Okay, so the grease will stay inside the knuckle and the control arms or the bushings That's one tip Then remember this guy this nut was not Knocked in Somebody forgot about it your this can actually these can come loose. So remember to knock this in into the slot and Probably second most most important part is once you're ready to tighten this nut down Make sure Your suspension is compressed all the way up. So you're actually Raising the vehicle a little bit and then tighten it because then your bushings will be in It's in their natural position if you tighten it with this Down all the way like it is right now Then when you put a tire back on and you lower the car Those bushings will be stretched at all times or twisted at all times and that rule goes for every single bushing Make sure always suspension is As if is as if the car was on the ground then tighten Whatever you're fixing this is tight again spent a little bit more time to find these Washers, okay, so they they belong It's not I guess I can Put all the wheels back on Guys wheels are back on Some more weight reduction This heat shield right above the muffler is a bonus Still got to clean that up and check the level And this is where it was cut and look at this corrosion, I mean You know what's gonna happen As soon as this car gets on the road There is a more weight reduction gonna happen Because I can just You know, whatever I do on it stuff falls down. Should I start it? Yeah Hopefully nor tornadoes today for me I did clean this out. This was covered in oil. It was black Guys check this out. Oh six impresa suspension and springs Much higher I say in the front There's full fingers Four and a half No for here looking Looking looking good. Nice The engine mounts excuse the wind guys, but it's so humid and hot I got no AC. I took it out equal length headers It still has that box or rumble. How much? Quicker it is I suspect the muffler alone was Probably like 15 pounds AC compressor another 20 maybe Plastic trim only in the back. Remember, I never you know, I didn't really touch the front So there's still quite a bit to take out More skins, maybe speakers radio, you know, really another 50 pounds So I'm guessing Right took out was maybe 120 pounds maybe 150 And another 52 To take out Anyways guys, you're gonna see this vehicle bring ice racing, which is Months months away along with our race machine. And you know what? I mean, you've seen the state of this, but I don't care What kind of a Subaru you got they're all fun to drive All right, guys See you next time smoky


Good morning everybody. We're on. Welcome to Kate's or die and If you were expecting us to stroll out on the skateboard, I'm sorry. We couldn't pull that off over the airplane My name is Ryan. This is my friend Marco. Hey, we have deployed clouds and coops and all sorts of fun things on different architectures over the last few years and We're here to basically talk about Kubernetes and the various combinations of Kubernetes and OpenStack and reasons why you would combine the two and perhaps Whether you should combine the two in some cases We hope to have some good conversation at the end of this. I think our presentation will be Maybe 20-25 minutes and then we invite conversation at the mics and of course If you will deploy Kubernetes When where why and how would you do this? Yeah, right? So I have an open stack multiple open stacks Already deployed. I have all of my applications deployed in a combination of VMs and containers today My control plane on all of my clouds is already containerized and highly available So Marco, why do I need Kubernetes? Yeah, it's such an interesting question It's been fun this whole week kind of watching the conversations that have been spurred about about OpenStack containers the intersection of the two Kubernetes Docker swarm. So I want to talk about Why you might need Kubernetes and really why the need for Kubernetes is such a prevalent prevalent conversation topic these days and so to do that We have to just take a step back and see what computing has been doing for the last couple of years So this will be real short history trip. So We're all familiar with this I imagine It's a it's a server. It's a laptop. It's your computer. It's a Linux machine running Linux It's got processors. It's got processes these beautiful little lines. It's got a some kind of disk SSD Could be spinning rotary. It's got a bunch of networks plugged into the bottom of it. It's a server It's not very exciting. We've had these for years now I mean many many years if you think of the real big Innovation with servers and server spaces was virtual machines now's whole idea of well my app doesn't really need to run that much Need to use the entire box for its app I can actually get a lot of multi-tenancy by just saying hey, I'm gonna take a chunk of this machine I'm gonna go ahead and do the same thing. I've done on my root server. I'm just gonna run a bunch of processes I'm gonna run an operating system It's gonna have a disk it's gonna have a network and it's just gonna physically I'm just gonna basically carve out and virtualize the the IO for this machine on the on the host hardware And that was exciting because well now we have a we have something we're very familiar with its servers You're accessing them your SSH into them. You have developers getting to them You're putting applications on them It's really no different than when you were managing bare metal You've just got a whole bunch more of them now and it was very exciting and so From there we've kind of evolved a little further and this is where things like Process containers come into play The idea about a process container is a bit different than what you'd see in a virtual machine or on a server So if you're not familiar with a process container, this is things like Docker These are things like rockets is things like run see these things that people have been clamoring about This is usually what people mean mention when they talk about containers and the idea behind this is Instead of taking the entire machine and running all those processes and running all of those All those items and your application and having a disk that you write to and manage and having all these network spaces What if we took that a step further? What if instead of taking that and virtualizing all the IO? What if we just confined it so that you just ran your process and you provided just enough OS to run that single process in a constrained confined manner and By doing so you actually get a lot of density a lot more density than you would out of VMs You can run hundreds of thousands of Docker containers where previously you were physically allocating chunks of your hardware to They all kind of share the same processor space. They share the same memory space and they're generally running less processes in general You're not running a knit. You're not running SSH. You don't have cron jobs Executing but there's also comes with some drawbacks and there's some different ways to manage these you don't have a full disk anymore Generally speaking you don't write to that same OS disk Obviously you can in some cases but generally speaking they're more immutable And you're just running that process and you're managing things coming in and pushing output somewhere else And so what's interesting about this is because with virtual machines We have this idea of traditional operations things we've been doing for the whole time since we've had servers You can run the ansible against it you can run configuration management against it You can do virtually anything you can do against a server and a virtual machine When we start talking about process containers, it actually takes on a whole new breed of operations You can't SSH to it You can't just run a playbook against it You can't just go and manage it like you've been doing for traditional machines And this is why we're seeing a bit of a shift in how we do management and why containers are this really big hot topic because It's unfamiliar. It's new and it requires a whole new Breed of tooling to figure out how to manage these at scale much in the way We've come to accomplish managing virtual machines at scale and so because of that we lead into Needing what we call container coordinator So container coordinators are effectively that platform for how do I operate and manage containers and so that is Why we have this stride for kubernetes and things like kubernetes kubernetes Docker swarm and the other projects DCOS and mesosphere that are popping up and they're all claiming to be this container This nebulous container thing and what it really means is how do I operate and manage containers at scale in a same way that I've come to expect when managing things like VMs So what does kubernetes look like when we pull together the architecture and services that it takes to build Yeah, so I guess That was more of the why I guess you're asking what what is a kubernetes actually look like yeah, I manage it What does it look like? Well kubernetes is surprisingly and shockingly just software. It's nothing special. It's not a magic hat It's not a cape that you can wrap around your neck and fly off into the free world Proclaiming DevOps is done and I and and celebrating that kubernetes is software and it's actually From an architecture perspective since kubernetes is a container coordinator what you're really getting is actually the abstraction of those Machine resources those VM primitives those things where kubernetes is running you're getting an abstraction for those for your Docker containers and what it really amounts to is Effectively giving you the abstraction of compute networking and storage for Docker style containers now I'm sure this sounds strikingly familiar to a couple other projects. You might be familiar with But essentially at the end of the day as a kubernetes the platform is just providing that mechanism to say I'm going to run containers I'm going to run them here. They're going to be on this network They're going to have potentially this storage pools attached and they're going to be running on these classes of machines or these types of processors with these compute resources and So because Docker containers are Well generally speaking such a small surface area It's a single process running on a virtually immutable disk with some semblance of networking We actually have a platform that grows a lot of capabilities that were tougher in previous generations of computing Doing things like roll out and roll backs of applications while absolutely that's something you could do today on traditional VMs But it took quite a lot of time to produce a tooling to get to that place Same thing with scaling up and scaling back all these primitives while they are present today They took quite a lot of engineering work to go from I have a VM to I have a VM that I can scale dynamically to a VM that I can upgrade dynamically and be confident in that upgrade or to a VM I can roll back and In addition to that you get things like load balancing Self-healing service discovery things we'll talk about a little bit But basically because the actual idea of what a container is a process container like Docker style containers Because it's so small and so strongly defined as a surface area It's actually easy for platforms to start building these primitives in where previously it was actually quite a difficult feat And so that's what's gotten a lot of buzz around things like kubernetes in these platforms It's because they have these features that took arguably quite a long time to figure out how to solve and there are still some areas where they can improve with operating traditional style of VMs So I want to talk just real briefly about what a kubernetes architecture looks like, you know What does it actually mean to run kubernetes? Does anyone here actually run kubernetes or running kubernetes today? Hey, yes, the brave the brave few hands raised How many people actually interested in running kubernetes like this this next six months like I'm definitely going to get into this kubernetes thing Yeah, everyone's talking about it. I'm sure developers are clamoring for it They're sitting there throwing Docker containers at your ops guys and your ops guys are like stop doing that, please So kubernetes is a platform because again, we're dealing with a very small surface area It's actually quite small from an architecture perspective. It effectively breaks down to a few components You have the kubernetes core software itself You have at CD which is its data backing store and then you have some form of SSL TLS certificates and I mentioned this because I think in this day and age it's Generally imperative that anyone building clusters anyone building production infrastructure should be encrypting that communication from the control plane to the workers to the clients themselves and kubernetes makes it pretty easy to start consuming those types of things building a secure cluster with TLS encryption and such so Those components are basically arranged in this kind of fashion. So you have a TLS certificate authority easy RSA is what upstream recommends It's pretty easy to set up.  It's from core OS. It does things like quorum and data protection Does the proper peering and things and it's basically a raft back key value store at the lowest level So it's very robust and reliable and is what at CD what kubernetes uses do its coordination of data Then you have a master control plane service and this is actually pretty small in and of itself as well It's just an API server, which is what you your clients your your users talk to There's a scheduler which does that things like well. I need to make sure I have these number of Workloads running. I need to make sure that if one of these goes down and bring another one up It implements a lot of that logic around auto healing and auto scaling And you have a controller manager, which helps to coordinate all of the different pieces that are moving inside of a deployment Then finally you have your workers And this is where you're actually running your workloads and there you're running.  This is typically what you'll find walking to anyone running a kubernetes cluster today and Because a lot of this stuff is docker eyes because a lot of the stuff is container eyes It actually lends itself to running in a very converged fashion So a lot of times you'll see with just maybe really was just one machine You can run a single kubernetes cluster, but really with three machines You can actually run an ha cluster where you're scheduling workloads You're also running the api control plane services and the data store services So again, this is just an example of architecture these vary quite a bit depending on where you are But that's effectively what you see in most places that are running small clusters You have the most amount of density out of the hardware they're piloting on So yeah, so I mean I'm a kubernetes guy. I don't know if you guys have picked up on that It's kind of that thing. I'm really interested in cloud native architectures and stuff I'm just kind of a cloud consumer actually I just I pay someone a bunch of money to run VM somewhere that I'll never have to go look at In a public cloud, but what I really want to know I think this might be a silly question for this audience I want to know what kubernetes what open stack is and why people keep talking about it here So first of all that was a ton of good information. Thanks. I feel like I know kubernetes now So what is open stack? That is a loaded question. So if we think like 10 years ago before open stack We're Linux saying and virtualizing and doing all of our things with VMs and how are we tracking compute network and storage? How did we manage that what tools were there in the in the pure open-source world? I think that there was a void clearly and that's where open stack fills so, you know, there have been folks Put it akin to basically a fancy spreadsheet that is tracking that compute storage and network if you're talking pure infrastructure as a service so you have open stack as basically a collection of API services as a service oriented architecture and The the actual layout can vary quite a lot there again. This looks a whole lot like Your converged architecture you had a moment ago This is a similar layout to some of the clouds that I've got running where we spread the control plane across compute and storage and It's available as a highly available cloud So I don't think that diving into what is open stack at the open stack summit is probably a good use of time So let's move right along To what it means to combine the two yeah, so where does Five kubernetes. Do I really need open stack and few of open stack? Do you really need kubernetes? Maybe? Well, all right So let's look at some of the combinations that we've seen out there, right? So let's say you have an existing open stack. You have a production cluster. Perhaps you have a dev cloud Maybe you have both staging production all of the various things You can certainly have your tenants stand up kubernetes and have individual clusters that they can consume again Whether those are production workloads or for development So that's like a lot what I do today that if I get an Amazon deploy kubernetes cluster I basically just do it on top of open stack if I had a private cloud. Yeah, right, right? So we do some of the same with with our dev cloud. So another scenario is that You've got an existing open stack. You have some spare bare metal and you stand up your cluster of kubernetes Alongside open stack. I think these each have different use cases. So that's like This guy I work with he does data science stuff and just loves GPUs, right and runs a ton of machine learning with stuff so He always is clamoring for more metal So if he were to dockerize his stuff running that on kubernetes on bare metal makes probably more sense for him It could make a ton of sense. Yeah, yeah access to to virtualized hardware So something that's gaining traction, you know, if you rewind six months and then rewind six months from that there were ideas about dockerizing the open stack control plane and other services and Distributing that and managing that with kubernetes, right? So there are projects out there doing this And so this is an interesting thing. So basically containerizing the control plane in a docker-like Container So these are not mutually exclusive if you have these varying approaches in your organization You may end up with something that looks like this, right? You've got metal You know kubernetes kubernetes sitting on that metal that kubernetes cluster may be delivering multiple applications for your enterprise One of those applications might just be the open stack control plane or other open stack services And then again, you could have your tenants Wanting their own kubernetes cluster. I actually think I saw someone do that this week I think we've seen this a couple of times, right? Yeah, so there there are all kinds of different analogies I think that people whether they're intending to or not were are going to end up with things that look a lot like this and I think that there's you know, each of the projects that deliver these things are maturing and Interesting. Yeah, it is an interesting thing. So let's think about or talk about some of the projects that are out there to Help you achieve these things Whether it's for just exploring Or looking at doing something in production. So naturally there are heat templates I'm not sure if they're community driven or by the heat project that they're centered around Deploying kubernetes on top of open stack the magnum project has kubernetes capabilities and Couple of other things out there the kubernetes charms which are upstream in the kubernetes project Can deploy and manage the life cycle of kubernetes on top of open snack kubernetes naturally pretty much works on anything. That's kind of the The nitty-gritty way to go do some things. Yeah, so it's a so that's for kubernetes like kubernetes an interesting project Because it's tackling kind of how do you self bootstrap a cluster? They're getting very close to being Ready for a stable testing which is exciting. That's cool. So something that's in incubation incubation is the cargo Project and there again it has relevance to the open stack project So some of these have varying degrees of maturity. I think it'll be interesting to watch the ecosystem grow and And some of these things gain traction sure but all these on the right-hand side because obviously heat and magnum Those are open stack projects, right? But charms kubernetes and cargo all those speak to the open stack API natively as I understand So if you're looking to turn up kubernetes cluster, those are kind of upstream kubernetes ways of tackling that problem Yeah, right. So they are specific extreme the kubernetes. Yeah, yeah, so they'll be specific to open stack, right? So if you if you have Automation built around magnum or heat it pretty much predicts that you will be installing this on on open stack So let's take this and flip it around there are a couple of projects That are geared toward putting your open stack control plane and perhaps other services Into docker-style containers on kubernetes It seems there are two kind of in the open stack world that are filling this this role And they might be in some ways in competition with one another Those of you who are not familiar with helm is not a specific open stack project It basically allows you to use charts to deploy applications in your kubernetes cluster There's project called open stack helm that leverages that and I believe call images under the hood Yeah, so call us seems like it's a project call itself an open stack is a project to build docker containers for all of the Services that you can deploy with an open stack and then call kubernetes is taking those images and just using the kubernetes API directly where Helm is more like a package manager for kubernetes. It's a different approach to solving that same problem Yeah, yeah, exactly. So call that actually is not specific to kubernetes There are a couple of different flavors of the call a project the call of kubernetes is just one of them So these will be interesting to watch And and see how these things mature and and perhaps progress over time Finally the scenario that Might be quite common is to take kubernetes directly onto the metal I know we touched on that a minute ago, but the tooling to do this Arguably is is widespread and not very clear. There are a number of things in the Upstream kubernetes docs about how to take and lay down a kubernetes cluster Whether that be any number of config management tools Essentially the ones that you know that that we use and that I've used and Like to use are the kubernetes charms there again. It's these are in the upstream kubernetes project these allow you to Deploy and manage the lifecycle of your kubernetes cluster including upgrades Same with kubernetes again, which kind of works on any VM Where there's a whole process for bootstrapping a cluster having cluster expand and grow and then As they move towards finishing this dev cycle, which should be done pretty soon They'll have all a nice upgrade story as well alongside that. Yeah. Yeah, so Who here has stood up a kubernetes cluster the hard way you should probably I don't well, I don't know so I'm talking about the Who here has gone made a bunch of VMs and then a bunch of W gets and then a bunch of hand configuration of stuff. There we go That's a brave. You're brave. How'd you look? How'd you like so it was I can see where Ryan's going here It's super important because I bet you learned a lot about how kubernetes is actually built under the covers So you went you went even harder. You said, you know what pre-built binaries is that's too easy I have to go compile it by hand For sure and that that's kind of my point is that if I ask the same question of the stackers in the room Who has gone out and done the same on a pile of machines not in Dev stack and stood up a functional open stack by hand? It's worth doing once you probably don't want to do it twice, right? But it is good I think there's a there's a great there's a great great blog series called kubernetes the hard way if you haven't read it And while you may not want to actually go down the adventure of hand-setting these things up because it is going to take you a Few days to get through and get a successful cluster running It's a really good read on understanding how all the components interact with each other how they're built how to design what the Architecture looks like and some of the pitfalls that come commonly with deploying clusters But generally speaking you'll find just like with open stacks you want to find a way to actually start automating that process Yeah, for sure Sure, so the point is is that today kube-atom is not yet a stable production ready tool It's one that they're building towards it's a project. That's also being incubated in the upstream But it does things like it's not ha out of the box or you can't even do ha really Where are the projects like cargo against open stack or charms against open stack or metal? Those take into consideration high availability of database services and control plane features and such But kube-atom is very interesting because it is a It is kind of if you want to do it yourself But don't want to go down the road of compiling everything and then hand configuring everything kube-atom gives you a really nice feel of You're building the cluster. You're making choices. You're doing everything by hand effectively But it does take care of a lot of the more tedious functions of bootstrapping SSL certificates for yourself and Producing other things that make it so you can get a secure cluster running when they're ready and out of development in an HA fashion Yeah, awesome. So when you when you think about, you know abstracting the tooling And you want to have a kubernetes running on any given substrate whether it's a public cloud or open stack or directly on metal Or on your laptop the tooling varies quite a lot and there there are some Pros and cons to each right but in terms of being able to do this across the board These are basically the the two that that kind of spread the gap Yeah, that definitely spread the gap So kubernetes and open stack together It's an interesting combination for sure and there are as we've seen a couple of approaches more than a couple And I think varying reasons for doing one over the other or all of them together so it seems like In our time discussing this what I've come to kind of start accepting is I was always very happy to say You know what the future is containers But I think there's actually a bit of a different story here I think what I've learned after trying to push everything into a container And what I try to do running everything on kubernetes or swarm is really it's going to come down to it's not kubernetes versus open stack But it's really about your architecture and what it boils down to is Whether you're running something that's stateless or whether you're running something that's stateful and this is a loaded term I know Ryan you helped participate in the interop. You want to yeah interop stuff. That was cool Yeah, do you want to explain real quickly sure sure that the interop challenge is an effort where? we take multiple Clouds public private clouds of varying distribution and version and demonstrate that open stack its apis its product is able to Function in the same way regardless of those varying vendors and distributions and versions so the workload this time around for the interop challenge was a Kubernetes cluster on top of open stack with cockroach DB pod Deployed in that and then beyond that these cockroach DB Databases were clustered across these various clouds so This is this is kind of a cool effort But my understanding of databases is that they're very much a stateful thing. So how does that work into this? Yeah, so I liked it very early on the interop challenge everyone one of the people stood up and was like Explain that you're gonna hear people argue about stateful and stateless applications this whole week But cockroach DB is arguably stateful and it runs and Kubernetes fine and does a good job And I think really this slide is a little misleading as well stateful itself is a Very nebulous term. What does it actually mean to be something stateful? I think state is pretty clear, but stateful is really is a really awkward term And what I've kind of found is that there is definitely a generation divide between software being built and we look at cockroach DB If you're not familiar with it, it's pretty cool but what it does is basically gives you a sequel interface against the distributed data store and Cockroach DB was designed to be resilient out of the box It was designed to do clustering peering and stuff and what it's really designed for is really designed for a cloud native architecture an Architecture where if one machine goes down, it's expected to happen And so while you have a consistent state present across all those nodes No one state is no one machine or VM or docker container Has state that will if go if it goes missing will break the cluster and so that's respect It's a distributed stateful application and because of that it actually survives quite well and thrives as we saw interop Inside of a inside of a dockerized container kubernetes deployments Whereas a lot of apps that were written. I'm guilty of this as well Early earlier generations applications are really written to be more tightly coupled than that So if you have an application that depends on being on the same disk and having data Persistent on that disk so that other parts of the application can read that That's a really super stateful application And if you can't just take those components and run them over the network to each other or run the data and store it Externally you're actually I think a quite a lot of engineering effort to actually detangle that and so what results is a lot Of engineering effort to make that application super cloud architecture friendly cloud native architecture whereas a lot of developers today are building Applications with that in mind cockroach TV is a good example of that and a lot of our distributed stores at CD itself again Another data store that persists data But it's designed in a way that if you're running it in resilience more than a couple of nodes running if one goes away You can bring a new one up. It'll rejoin the cluster re get its data It won't lose connectivity to that cluster. It's designed in a way to be resilient in a cloud architecture because Well, frankly clouds are ephemeral and docker containers even more so And so I think that's where we start to see the divide is it's not just all stateful applications as a as a general Blanket statement that you can't or shouldn't run them in inside kubernetes But it's about taking the tasteful discretion to see Which application can I run in kubernetes? Which application should I be running in kubernetes? And a lot of times we'll find that there's a good mix of things where developers want to go really quickly They have an application that suits that architecture But you've also got database operators and you've got general sys admins that are gonna want to make sure that they handcraft VMs and that they manage those VMs and that they do things to persist that data at a Infrastructure level whether it's snapshotting that data whether it's making sure it's backed up and robust or Or running multiple services like cron jobs and other things on that And I think that's fine to sit in a VM. I think that's where you'll find the intersection of Yeah, yeah, I think Bernetti's and certainly for some time structure management. Yeah for some time We'll have a combination no doubt the Sessions that I've attended this week have been some really good ones that dive perhaps a little deeper even then we are into some of These areas and what what I'm seeing overwhelmingly is that the the control plane is is easy, right? These are stateless things. These are services you can cluster Storage Becomes an issue Seth. What do we do with Seth if I'm an old-school? Sefi and I just want myself to do Seth stuff I mean we have things that are happening to help improve that story But it doesn't seem like we're quite there yet Persistent volume claims perhaps is a trend that that will help solve these kind of things So how does how do you think that fits into here? And should I keep my Seth on VMs or on metal? Or should should we be pushing that threshold to try to? Lift and shift as a were that some folks. Yeah, so I think Seth's a super interesting one I don't have a really good answer for people I know it's hard to run in Cupertetti's whereas installing Seth on a VM and configuring it to talk to your Seth Mons is actually quite simple But Seth Mons interesting story because you could potentially run that containerized the monitor for Seth But OSD's probably will live on disk and in the same vein I could see things like horizon Super staple application that makes total sense to run in a container But my SQL seems like it might be slightly more problematic or a more traditional SQL server application Yeah, right. I think we'll see vendors Especially those that are running database services. They'll all work to containerize their applications. In fact I want to point out something real funny Because I've been praising the cockroach DB guys this whole time So I went to go download their software that I spoke cockroach.  I'm gonna go install it Good gosh, I gotta go figure out the navigation here one second I said, oh, I'll just use Docker and the first thing they say is You probably shouldn't do this in Docker You can but it's actually quite hard and it is it's a hard problem to solve So even something like cockroach DB, which as we see it excels in a platform that's Docker eyes and in a Kubernetes fashion Even they are still having ways to figure out How do we do things right in containers that allows to do persistence of data and stuff? So I'm sure the Docker containers great. It's not a slight I actually haven't run it yet. So I can't really judge it for myself But it's very interesting that you'll see that more vendors cockroach DB. I'm sure my SQL I'm sure Maria DB. I'm sure Postgres will all find ways to containerize their services for those that want to consume it in that fashion But it will take effort for them to re architect their software to be conducive to that fashion And so in the same vein if you're running software today that you've written odds are you'll have to do a lot of work or a Little bit of work to get it in a state that can just run easily on Kubernetes Whereas developing your next applications or run on Kubernetes makes much more sense It's something it's a little more tenable and going back and re-architecturing range and everything and because of that I think in the next five six years. We'll see a nice heterogeneous deployment of things managing VMs and things managing Docker containers and then who knows by then we'll hit serverless We'll probably hit quantum containers by then as well. So the whole world will change and it'll be an ever-evolving landscape Right, right. So we do want to have time for comments questions and Conversation really so the idea here is to You know for folks to be able to share some information experiences things like that I know it's not a fishbowl, but we can make it that yes So if you have a question feel free to just queue up in front of the microphones otherwise I could continue talking about containers for the next eight minutes No, no questions at all So everybody understands why you need Kubernetes and where you're going to use it. I'm still figuring that out By the way, I think everybody is hi guys. Thanks for the great presentation Maybe architectural question How would you model more complex application stacks where you have something? What is really stateful like database which maybe should run in VM? Yeah, and application and web servers which could potentially run in containers Yeah, and how would you orchestrate the whole stack? Would you use heat and some configuration management plus Kubernetes or it's going to be it's honestly going to be Really dependent upon what your team's familiar with I think all of those are great options What you'll likely see is that you'll run and operate your stateful services in VMs And you'll almost make that consumable as a service to your to your doctorized workloads where you'll say hey My db admin or some person's gonna go they're gonna go create you this database this username this password That's what you have and then as your developers roll those things out those containerized Stateless applications. They'll simply just configure them to use that as a service. So to them. It's a black box It's no different than Databases of service effectively the cloud is just that you're maintaining the VMs behind there as well It could also even be databases of service potentially But we'll see that that I think we'll see that SAS model evolve quite a bit more to where Those kind of containers running in these platforms will just consume them as endpoints And they won't really necessarily know or need to coordinate between them It'll be a pre-setup step potentially scripted and then just configured as well either using helm either directly through kubernetes Or some other form of configuration management platform Thanks. Well, thank you Yes, can you talk a bit about where? With the intersection of these things where things like a atomic host and chorus with the mutable architecture fit in Yeah, so those are two super interesting things I Think what we what we see is a general shift into people saying if I'm gonna be running containers I'm gonna be managing these platforms I want the lowest I want to abstract the lowest level possible and kubernetes gives you that abstraction to where you're not even worried About machines anymore placements. You just want to have containers running somewhere So the idea of having a host be completely immutable and inaccessible Not writable at all is super alluring. There are definitely some trade-offs to that So core OS specifically has a platform that is effectively a blob of OS with a bunch of things pre baked into there And then they auto update themselves if reboot the machine to give you that latest platform There are advantages of that. It's secure by nature. You can't break to those root volumes but then again at the same time if you find that You're looking to add additional capabilities to that blob It's not that's a lot harder to do when we really see is people doing things like Secure confinement to the components they care about that have that intersection of potential security vulnerabilities So that's things like confining the actual kubernetes control plane so that the binaries running can only run the binaries enough touch anything else on Disc, but the OS is still accessible. So you can SSH to it. You can install additional software drivers capabilities that you're looking to do It's still a lot to be figured out there. There's still a bit blurry But that's kind of the trend we see is those who are using these immutable OS is eventually comes the point where they say What's in the OS and what I actually need to run is something completely different or there's a there's a overlap of things that I need to install there Great question Yes Hi at the risk of asking you guys to go into holy war territory. I'm ready Can you compare contrast and maybe even provide some decision points on other container orchestrators in particular Docker swarm and Mesa's that is not a holy war actually so we thought to pull it there. Thankfully I thought you're gonna ask me about them or Emax or something That would have been a whole holy unfortunate So each container platform is tackling a separate set of feature sets and it's actually very interesting for consumers today Because you have a lot of choice Docker swarm. I've used a platform at a high level. It's just basically run a VM. Sorry run a container somewhere With Kubernetes you get a lot more facilities to manage what that machine what that VM? Oh my goodness What that container looks like how to maybe modify the scale for those things how it plums into other things So the service discovery aspect it becomes much more like infrastructure platform as a service Whereas when you tip into DC OS and Mesosphere They also do a lot of things that overlap with Kubernetes But they tackle them in different architectural ways so they themselves can actually run more than just Docker containers So the platform for scheduling and management is not just limited to process and Docker style containers So it's really a breed of you have a very simple management of a cluster of machines that are just spinning up Docker processes And that's Docker swarm you've got Kubernetes Which does quite a bit more in the management and lifecycle of containers and then you've got things like DC OS and Mesosphere Which give you the same kind of primitives you get from Kubernetes But be able to run those against potentially different run times and different container types Thank you. Yeah, thank you. I think we have a few more minutes left. Yeah, we've got two minutes till time encourage any questions or conversation for sure so Out of curiosity of those of those still left here Who here is I will be racist of hands earlier, but who here is going to be deploying Kubernetes in the next six months again How many of you are going to be the primary consumers of that or you're doing it for your development teams or another team in the company That's asking for it. Sorry. Sorry. We asked it in a binary fashion Put your hand up if you're doing it for someone else other than you or your team Yeah, interesting So, I mean, what do you what are your general feelings about it? Are you excited about technology? Is it something you're just another thing you have to run as a workload? I'm curious of what what your what's your consensus is of Kubernetes the platform is something that it's being requested upon you No, it has any opinions. It's cool. I get it. It's so early the morning. So I understand Yeah, yeah Yeah I'm here The pioneers Awesome, so I hear that story a lot for sure. Yeah, we're at time. So thank you for coming We we came not with all of the answers on by intention We wanted to spur some conversation and some thought into these Architectures so if you have any questions feel free to reach out to us here is our Twitter handles and a couple of URLs That may be of interest Absolutely, please reach out. Thank you all. Thank you


Throughout the month of August, the Ohio National Guard participated in Operation Northern Strike. Northern Strike is fully integrating new operational warfighting initiatives to include joint warfighting content. So here at Northern Strike, our unit is conducting our annual training. We've been working through operations with joint forces such as the Marines. We have some of the UK Army and the Latvians here as well. You not only learn a little bit about them and their country, but just really how people can come together better and making friends. Personally, my favorite part about Northern Strike would have to be the actual soldier training. I've actually learned how to drive an LMTV and a Humvee already. We've been getting surprise attacks by enemy forces helping our situational awareness. We've had drones dropping simulation grenades. We have had like a seaborn attack simulation and all that fun stuff and I just love that stuff. So far, yeah, we've been really kicking butt. It's been great. It's good teamwork and to see everybody work together. And then we're also using this time to get mission ready for the future in case our brigade were to deploy. We're porting for the 196th Mobile Public Affairs Detachment from Camp Grail in Michigan on a specialist in her IED.


So let's do some problems involving molar mass. First, what's the molar mass of Sulfur? Well Sulfur is an element so this means we can look it up on the periodic table. So we go to the periodic table and we look for the mass number under the element symbol of Sulfur. So here's Sulfur and there's the mass number, 32.06. Now this means two things, this number. It means that the average atomic weight of a Sulfur atom is 32.06 atomic mass units. And it also means that the mass of one mole of Sulfur atoms is 32.06 grams. From this we directly get the molar mass. If one mole of Sulfur weighs 32.06 grams then the molar mass of Sulfur is 32.06 grams per mole. So either we can write grams per mole as grams slash mole or grams dot moles to the minus one. It means the same thing. Okay how about water? Water is not an element but like everything in the universe it is made up of elements. The formula for water is H2O. So one water molecule is made up of one oxygen atom and two hydrogen atoms. If you have two water molecules then there are two oxygen atoms and four hydrogen atoms. And if you have one mole of water molecules that means you have one mole of oxygen atoms and two moles of hydrogen atoms. This means that we can work out the molar mass of water by adding together the molar masses of the atoms that make it up. So to work this out we need the values for the molar mass of oxygen and the molar mass of hydrogen. So we go back to the periodic table and we find oxygen here at 15.999 and hydrogen here at 1.008. So we're going to go back and put those in and then we're going to calculate that. And it comes out as 18.015 grams per mole. Don't forget the units. So that means that one mole of water weighs 18 grams.


physics channel for physics please subscribe my channel hello and welcome back to another episode of physics partner today I would like to discuss about Wim's Hearst machine let's talk about the history of this machine this machine was invented by James Wim's Hearst he was born in 13 April 1832 he was a British inventor and engineer and a shipwright he is best known for developing the Wim's Hearst machine an electrostatic generator that is designed to produce high voltage charges Wim's Hearst did not patent his machines and the various improvements he made to them but his work has had a lasting impact on the field of electrostatics let's have a look of the working principle by using a virtual lab this is the model of the James Wim's Hearst machine this machine consists of two insulating discs mounted in parallel and rotating in opposite direction you can see here these are these discs which are mounted in parallel and they are rotating in opposite direction the disc have several metal sectors attached to their faces with metal strips connecting the sectors on each disc as the disc rotate the metal sectors pass each other and create a difference in electrical charge between them you can see here on the screen that will produce in the electrical charge this difference in charge causes spark to jump across the small gap let have an elevator look you can see here this is the spark which is going to be generated so this difference in charge causes a spark to jump across the small gap between the discs which produces the high voltage output let's talk about the application of this machine the Wim's Hearst machine was used for various applications such as generating high voltage charges for scientific experiments or demonstrations charging laden jars and powering early electrostatics experiments additionally it was used as a tool for teaching the principle of electrostatics in classrooms and laboratories the machine was an important invention in the field of electrostatics and help advance our understanding of electricity and magnetism let's talk about some disadvantages and limitation of this machine the Wim's Hearst machine has a few disadvantages or you can say limitations for example it can be difficult to start producing charge unless a high voltage source is already available to jump start the machine the machine's output voltage is limited to 10,000 volts which is considerably less than some other electrostatic generators like the Vendee graph generator I have a video on my channel on Vendee graph generator if you want to revise the concept I will share the link in the description the machine can produce a large amount of ozone gas which can be hazardous if it is not properly ventilated the charge produced by this machine tends to be low in current and high in voltage so definitely it is not going to be used or it is not be very suitable for powering electronic devices or other high current applications these limitations do not necessarily make the Wim's Hearst machine less useful but simply indicate some of the factors that should be considered when choosing an electrostatic generator for a particular application overall the Wim's Hearst machine was an important invention in the field of electrostatics and help advance our understanding of electricity and magnetism so I think it's enough for today so thank you very much for listening and watching I hope you enjoyed the video I hope this video is useful for you so take care of yourself and don't hesitate to write an email if you have any question curies suggestion and even classes are required take care of yourself meanwhile see you in the next video goodbye


If you need Madden 21 Coins for anything, make sure to go to BuyMutCoins.com It's cheap and reliable and my code MMG is 20% off Pack and play squad, it was good! Hey, long time no see, look, I know we're past Christmas I'm not past the Christmas mood though There's snow all over the ground here in Michigan This looks awesome and puts me in great mood Probably gonna have Christmas set up through January I know, I'm a lazy piece of shit But it's also so fun to look at I'm keeping it Now, I haven't seen you guys in a hot minute But we have some amazing stuff today I got tagged on Twitter about 200 times Because they dropped the 96 overall the 50 Barry Sanders 96 overall Barry Sanders and there's a 96 overall Lawrence Taylor So super good to 50 players on top of last week or two weeks ago Whatever it was when they dropped Michael Vick prime time and Randy Moss So there's a bunch of insane ones in stores right now Like what a perfect excuse to pull out pack and play squad again Barry Sanders is in packs I'm sure the 86 Barry Sanders is actually probably pretty good But we're not looking for that We're looking for this He's honestly not that expensive, pretty affordable 94 speed is lower than I thought But 97 changing direction That's what we've been using 94 break tackle, acceleration agility He's getting me nuts We just got to get him This is pack and play squad I can't just spend coins and get him I got to pack We do have good hat packs already But it's still fun to try to get the exact one we want I think I'm just gonna do two, four times the 50 fantasy bundles That's gonna be my best odds at Barry Also, anyone in the secondary would not make me mad First round trash We expected that Mitch Trebisky Wow, what a bad start Oh my God, Barry's players Boom! I think I already have a 90 left end though Who do I have? I have somebody good Wait, maybe not KJ Wright, Jaron Reed, Dantari Poe Michael Pierce Okay, this is where it matters, baby Top three, Kenny Clark Why are these still in packs? Take the most feared players out of packs, please Give me Barry Sanders right here Nope This is gonna be tough We have to get a 96 and I need it to be Barry Sanders This is a very specific hunt tier, but I believe Cody Whitehair, Aryan Foster, okay Damn, we got a platinum I haven't gotten a platinum in so long Oh, it's Jason It's, yeah, we don't need it I call him Jason-y Oh my God Full your size! Thank you, bro Thank you, he's turning our packs around Full your size in our packs We got luck on our side now, baby I can't even use them on this team, but I'm taking them You just got a full your size of luck out I guarantee if Barry Sanders is in my packs It's gonna be in one of these four So we get four Yes, sir!   Matt, I haven't recorded a video in four days And I'm completely brain dead 96, Barry Sanders Let's go Our second one is 86 I don't care now I'm serious, I don't care now I would love 96, Lawrence Taylor, 96 Kevin Moway Just to add a little juice But I got what I came here for And that was only my first half of my bundles Because I get $100 worth for each opening So I get one more bundle Holy shit Prince Tego Winago I've never pulled that guy, I don't think That's an awesome name Hey, I got James Bradbury Oh wait, no, I can't unthaw him anymore I don't think they have those hot cocoa collectibles anymore So I don't think I can use that I won't jump the gun, but I don't think I can use that 87, 83, those don't... No, it's gonna be an 82 Damn, it was not an 82 I've never actually pulled a 92 Holy shit, this is gonna be a hard choice This Devon Bush is fast as hell I don't even know who my current free safety is I know I need secondary players though I'm gonna go Reggie Nelson I've been saying I need secondary I can't actually check right now It doesn't let you do the compare, but... Also, if I can get the hot cocoa collectibles Still, I don't know if I can, but if I can I can unthaw him, that'd be cool Nothing to start out with this back Tony G, Kyle Williams, and an 86 Barry Sanders, I'll take the Kyle Williams I sent my Xbox Series X back to California So I got another week here in Michigan So I'm playing right now in one of the old Xboxes It is embarrassing how shitty slow this game is Unlike the Xbox it was made for Patrick McCartney, what did I just pull? I didn't even know that was a thing Don't give me a 96, okay good I wanna use this, Patrick McCart detackle I have 91 John Randall, but I think I'm gonna start Patrick McCart anyway I think that'll be funnier He might be a really good QB spy, cause I feel like he'll be faster He should be faster in most detacks I'm gonna try that out, I'm excited Starting out here with a solid base elite Bobby Wow, that's actually not... Don't you give me Patrick McCartney again Oh my god, I wanna use this so bad I wanna use this Jalen Hurts so bad But it like, it does not fit in this lineup Where could I put this Jalen Hurts? To be honest, he's also not very good And I just got very... Okay, I can't Hey, now the best we can hopefully use our last four packs Is Maui or Laurence Taylor But if I get nothing again, again, I really am fine with it Barry Sanders, Laurence Taylor And I think this is my final one, right? Yeah, Barry, Barry, Laurence Taylor And can we end it? 86, Laurence Taylor as well Alright, so that's gonna conclude that pack opening Holy shit Alright boys, you know the deal Once we make the playoffs, that's when our team can reset And this is not Wilma I don't think we're that close right now, though I don't even remember where we are Barry Sanders, Aaron Rod... I'm gonna be honest, that's pretty...  To 86 overall, Richard Sherman?  Don't tell me I have a shot here Garbage pass Alright, he is pushed really up close to this line I'm gonna block everybody and see if my wide receivers can go But, yeah, dude, look at that His corners are like probably plus five speed On all my wide receivers I'm gonna run a dive I'm just gonna see if Barry Sanders can kind of split a seam here But the odds are not in my favor I gotta go for it, man Fourth and five! I need Megatron to... Oh! No!  He rolled the wrong way I really thought I was doing something there Alright, so play action Good lord I have to run cover two, man Fine, I'll run zone for a hot second Just to show you guys how disgustingly dotted up this point Maybe not Maybe not That was not bad You think he runs this ball? No I have no idea what he wants to go for He just throws it out of bounds to Herschel Walker Who gets no yards Third and six Something basic again I see this row... Ooh! Nice fucking...    It's not I'll take two points though if I can get it Oh, no Ooh!  Uphill battle, gentlemen Let's get it Second and nine The half-back dives Are almost my only option I'm just gonna try the dive again Yes! Ooh! Good play! Barry! Is that a first?  I've seen reach floor before But I've never seen that exact one Another half-back dive?  He's getting clapped It's so insane I'm so over it, bro God I'm gonna play this out though I'm playing really good defense against this dude This dude's kind of a bum At least offensively For having a 99 overall team He's kind of a bum Can't see cover 2 being a move here He does really like going to have an engram So...  He throws a bad ball Where are you going? We get it to Patrick Willis We have to score before half Wait Pixel bubble?  Not at all I literally have no idea How to like bust through this That was kind of there I don't really know where Kenny Galladay pops up On this route But I'm gonna throw a corner out to Kenny Galladay here Let's see if it's there I kind of think he knows Ferrets!    Yes!    I don't know Oh my god He rank commit!  Thanks to Barry, baby I mean, how are we gonna take an L After pulling the Barry like that? Holy shit That man shelled out all that money on that team Just to get his cheese clapped By a 90 overall That was so lit Defense wins championships, apparently Because us playing defense like that Is the only reason we stayed in that game I get one pack since I won the game Let's open the 50 fantasy pack right here And see if anything here is gonna improve the team Corners Oh my god, corners We got completely grilled If I wasn't usuring it, it was open That guy just was not making the right reads In 86, Richard Sherman 86, Gilmore, that's not it Give me a corner Left tackle, chat Williams I don't even know I think that's slightly better Than what I have in right now And this can't actually be a corner Alright, so Trent Williams is now on the team One of the first good life tackles in the game Is now on our squad 89 overall And we just toppled a 96-97 So I feel a lot better But their skill level was like a 2 out of 10 So this is our problem Gilmore, Sherman I don't know how we're gonna do it But we gotta figure it out Hey, I love you boys Thanks for watching as always I'll see you in the next video Peace out