Hello everyone. How are you today? Are you feeling bad missing lunch? Are you good? Can we hold out for like 45 minutes? I probably won't go. I won't drag you through a whole hour This is gonna be like 90% demo But I will have some drawings and how many of you are in my talk yesterday Okay, cool This is different in that I will do just a few slides then do a bunch of demo and then maybe show you one slide But let yesterday I went back and forth, so it'll be slightly different, but it's still a lot of demo Um, I assume the audience is quite similar. Let me ask you about some technology to see what you know How many of you know what code ready containers is? Decent amount but less than half I would say how many of you know what OpenShift is Okay, that's a lot more. How many of you know what Podman is? Okay, that's good. How many of you know what quay.io is? Good I bought half maybe a little more than half How many of you know what the red hat container catalog is many okay? So I kind of code ready containers red hat container catalog I will have to describe that a little more a little more, but that's okay So I am going to this this talk will be unlike yesterday's yesterday's was strictly like a how like how something works So it was more like discovery channel Documentary like I didn't actually show you how to do anything new at all Like at the end of that talk you could do nothing new at all just continue to run containers like you had always done The only thing that you could do is maybe meta operation You could probably troubleshoot things better and maybe architect things better But you didn't actually you weren't able to do anything new this talk is is focused more on how to use a bunch of technologies together in a use case in actually a bunch of use cases like five major use cases And kind of get your brain around The I hate to use in English We say a buzzword like a cloud native kind of way of thinking which is slightly different than the way you would think with traditional infrastructure my background is is a ton of of Infrastructure background, so I came from American greetings back. How many of you know what e-cards are?  You do guys don't remember what e-cards are okay So Long ago in the early days of the internet like the mid 90s and late 90s We used to send each other like gift cards online. I mean gift cards. They were they were like Good tidings like, you know best wishes cards and things on Halloween or like well the six major holidays like Christmas New Year's Mother's Day Valentine's Day Valentine's Day was huge During Valentine's Day the site that I worked for American greetings. We were like top 10 largest sites in the world So I managed large numbers of thousands of Linux servers back in the late 90s early 2000s when when It was like still a pretty big amount of Linux servers So but the funny part is even to this day with everything I'm going to show you today with containers the problems are identical It's a matter of how to like share code configuration and data Among a large group of resources be them a bunch of servers or virtual machines or containers But either way it's it's about distributing these workloads and doing the same thing So it's funny my entire career basically has been the same problem. I've just been working on it with a new New technologies the whole time and it's gotten easier And so how many are you actually here before I even go deeper. I'll ask you one question How many of you think Kubernetes is complex? Raise your hand So this is the funny part. I think the business problem is complex I think running large-scale web properties with thousands of services is complex And I think Kubernetes is actually the easiest way I've ever seen to do that if I were to show you what we did back in the late 90s It was way more complex than what we're doing here way more complex we had configuration in a hundred different places and there was all these different files you had to edit to add a Service and even worse trying to get rid of a service and delete it was much harder So I'm gonna talk through kind of the beginning of containers here in the use cases that I'm gonna walk through and then I'll start demoing so Five six years ago. How long was it 2014? It was six years ago now. I started with Docker Started playing with Docker and I immediately saw that The exact things that we always wanted to do before we wanted to find run and build stuff So it's basic collaboration, right? We wanted to go find something that is somewhat existing that already kind of does what I need pull it down Mess with it run it get my brain around it understand it learn it then I immediately need to change it a little bit to add new value and then Then then from there we'll get later But this exact set of use cases is exactly what containers does right so if you think about an open source library This is what you do you go out you search get hub you look for something that kind of does what you need You pull it down you run it usually compile it run it kind of figure out what I need to do This is what we did back in the late 90s And then and then build something new on top of it just a little layer of value That's the thing that I'm going to contribute to make it just a little bit more what I need it to do This is a fundamentally different thinking than 30 or 40 years ago where you had to write it all from scratch Open source change the world so so I will say containers couldn't have happened without open source, but now we want it to be easier so Back when I first played with docker. I would docker find I would go out to docker hub look for an existing container Typically a base image add you know run the base image make sure it worked And then I would add a layer to the container image and then what do you do like that's useless, right? Like if I add value, but then I can't share that value It's basically useless like these are fundamental like sort of use cases of Collaboration be it with containers or not with anything that you're writing any kind of code So then I realized and oh and wait I want to back up so some people get stuck here I would call these like the regular docker people they get stuck here they just want to keep pulling down a container image running it building something new sharing it in a registry server and Then they just want to keep doing that they don't want to go to the next level because they're scared because they think kubernetes is complex But really what they don't understand is the business problem is complex running highly available Web services at scale is a tough problem. It's always been hard. It's been hard for my entire career But I would say that it's easier now And so then you have kind of the next problem. How do I integrate this right? How do I make all of these services run together? So say say I have a simple web app? That's just a database and a web server fine. That's not too hard. I can run that on my laptop But say I have a service that has 12 different services It has a caching layer in front of the database a caching layer in front of the web server it has Layer seven firewall that prevents certain things going from the web server to the to the you know to the database There's a couple different web services that all talk to each other that do one thing And so now we're up to like 10 12 services now integrating these 12 services and getting them all to work together And then pulling one out changing it a little bit and putting it back in That's the business problem that we're trying to solve to be honest again 20 years ago That was still the business problem that we were solving But with containers this gets easier But the problem is people get scared at share they kind of get stuck and they want to go back And they want to run a single node They'll want to run a single node container with Docker or podman I just want to keep running that and they get scared to go to the next level I'm going to show you why one that's not that hard to do and how many of you are in Urvashi and Sally's talk earlier today They showed something really cool podman kube generate or generate kube which I'm going to show you too But but I'm going to show you why in the context of this use case and how you go from use case to use case so Also, I would say the first three ish years of containers was kind of everybody figuring out this Up to share then you know the last four ish years kubernetes took off and we started to realize we want to integrate and then deploy With a a YAML file that describes what the application and all the services and how they interact looks now again It might be intimidating to get into that YAML file and start to understand it But it's a lot easier than what we did 20 years ago What we did 20 years ago is we had configuration in Apache configuration in the load balancers Configuration in the network with like routing protocols. We had configuration all over the place We had it in DNS. We had it. I mean we had it all over the place There's probably 10 12 Different places that I had to go write config files to bring a service up and worse when I would bring it down I had to delete it in 10 different places and then hope I didn't break dependencies somewhere else in the environment with kubernetes It's a heck of a lot easier. It's a single command to basically bring down a service So the deprecation of a service is so much easier Okay So let's walk through what I mean because it was pretty high level today I have it scripted because I'm not as crazy as I was yesterday So yesterday, I just did it live. I was like, let's just try this But this one should go fairly smooth. So We're gonna start with find so when you want to go find a container image, right? Let's think through this from a security perspective Historically would look at docker hub one of the challenges with docker hub is that anybody can write a container there? So it's a read write registry and so of course as we know the public internet is always a dangerous place and we've seen tons of articles about You know Bit coin miners being embedded in container images. How many of you have heard about this? This is a very common thing So you'll go and download a container image and it has a Bitcoin miner embedded in it You're running your web server and behind the scenes in that container. It's also running a Bitcoin miner and shipping that stuff back It's always about money. It's always just follow the money and you'll find why people do this stuff But in a nutshell What I look at is here. Let's let's run this So if we do this on a red hat system podman search, we will now see you will see something here registry.access.redhat.com this is actually something called the red hat container catalog This is a controlled You know environment where red hat publishes all of the official container images from red hat So I have a lot more confidence in these container images because I know they come from a trusted source I know they're built. It's a as we say in English It's a walled garden where I know I'm starting from a good trusted starting point and now if I add value again Now I'm finding something that I think I trust And now if I add value I have I have what we call chain of custody So I trust the original custody the original party that had custody of these you know of these bits And then I bring it down and now I have custody but Let's say I kind of trust red hat, but I'm not a hundred percent sure that I trust red hat Like I think they they build decent stuff But you know, I'm not a hundred percent sure that I trust them So let me show you what the container catalog is. So Let's do this. I guess I lied some of it is not scripted So let's say I want to pull down a base image. How many of you know what red hat universal base images? So with the release I will explain it with the release of rel 8 at summit last year We released something called red hat universal base image. It is a container base image that is essentially a rel base image It's not it's the same bits So it's the same trusted bits that we have that have a 10-year life cycle that there are back ports of security and features But it is contained in a container image that has a different end-user license agreement that allows people to just Redistribute it freely. So this was a challenge We had because our old business model the only way we could really control the bits because they're all open source was say Hey, we won't support you if you install a bunch of copies of this and don't pay us So it was really a contractual agreement the problem with this was is in the world of containers The install method changes if you think about it The developer is now installing the software and the operating system bits together in a container image And then deploying those you know and then sharing those all over the place But we had never given people the right to share those bits everywhere at least not contractually so we released can you know, we're at universal base image and We we basically released it for rel 7 and rel 8 but let's say I look at universal base image I say I think I trust this I think I would use this because I think it's trustworthy, but I'm not a hundred percent sure So what we do is we actually try to be very transparent about what is going on So if you look over here, there's something called the health index So right now red hat universal base image is rated as an a we actually have an algorithm that we score these Publicly and we say if there's like one critical it drops to a C or you know There's this different lip algorithm that allows it to drop down in grade and you'll see that over time I want to show you container people don't really think through container images. They age We say like cheese not like wine like they do not get better with age container images will always fall in in Security because what happens is? Trust is temporal right like I might trust what red hat released today But I don't trust what red hat released three years ago because it's clearly going to have Some CVE's in it and you know different different security exploits that have been discovered in the bits that we have So if you look here the top tag here is a rel 8 1 or a UBI 8 1 Container image, but as it gets older It gets lower grade and so you definitely want to try to you what this this highlights a problem with container images You have to constantly pull the latest one if you want to be You know if you want to have the security issues patched And that means that you need to rebuild all of the layers that you've built on top Which now means that I can't just build it once ship it and forget about it It means I need to constantly be able to reship it very quickly It's a very fundamentally different way of thinking about it containers feel really easy, but they're not completely easy And so you'll see here this one's a month old this one's three months four months six seven blah blah blah And they get lower in grade as we go older and that the 8.0 one is the one we released, you know at launch So okay, so I like that red hat shows me some of these things and actually has an algorithm for how they grade it Not to be too mean, but but there are if you look at other registries out there There's there's official images on these on these registries, but there's no definition of what official means It's just using a fancy word to describe a container image So if you go grab the the official, I don't know the official Apache image It is a very different set of criteria than if you go grab the official MongoDB image. There's no there's no standard on what official means It's just some people put a little seal on it and say this is the official one And so what you have to what you have to take away from that and start to understand when you're finding a container image is is Trust is really something that I construct in my mind. It's a warm and fuzzy feeling There's no lot. There's no there's no standard for whether it's secure or not You know Dan pointed out, you know, it's the porridge, right? Is it too hot? Is it really hot? Is it warm or is it just right? And you know the hotter it is the harder it is to use so Obviously if you wanted completely secure container images You would build them yourself from scratch all the time and then it would be exactly what you want with the exact security with the exact patches You want but it's inconvenient so we end up trusting other people So I say you have to download something that you a trusted thing from a trusted source So again in this case scenario red hat tries to provide some data to prove that we're like actually doing something legitimate here with These container images and and kind of transparently show that we're rebuilding them. So if you pull the latest one It's actually going to be, you know, something that's fairly high quality All right, so let's say I've analyzed this enough and I'm like, okay I think what I've seen in the container catalog is decent I'm skeptical security minded person. So I never love anything. It's only decent to me But so we go out and look I said And then we say we've looked at this red hat universal base image and we're happy with it We're like, okay. I think I would download this. Okay, so let's do a pod man run We move on to running it. Let's look at this thing cat slash Etsy OS release. Okay. So this is a rel 8 1. This is the ubi 8 1 image that I showed you that's up there the latest Looks pretty good. We could you know do all kinds of things in here, but I'm just gonna get out again Not much interesting that you can do with running a base image, right? Nobody runs an operating system There's a saying back in the day ten ish years ago Nobody runs an operating system just to run an operating system now. I'm a geek so I do do that But but in in public you know from for my company. I never do that, right? There's no reason to just run an operating system So really it has to we have to build something on top of it to make it interesting And so we're moving on now. We've went from finding to run was a pretty short step Build is the next step. So now let's build something This is a very simple Docker file that I created here that just adds a small You know I add proc ps because I like to have ps in my container image I like to have IP you like to have route and I like to have ping so I add some tools here Just to build kind of a what I would consider a core build back in the day But I would call this like a container core build If you don't know what a core build is a lot of corporations when they would install their operating systems would kind of Standardize on what all utilities they want installed so that when you would log into a server You would have the same tools everywhere, and it would make troubleshooting easier would make installing applications easier We kind of see the same thing happening with containers So so I kind of showing this is kind of a miniature core build and now Let's look at this new image. You'll see I've created the UBI 8 sharing You'll notice though that I created a tag Quaid IO this is just an arbitrary string a name that I put in here But this is going to allow me to now share it which we're moving on to the next step right like the next most interesting thing is sharing So we're going to push to Quaid IO Now as I start to get into this let me show you a drawing here because I want you to understand what we're starting to do here So we've went out. I'm going to get to here We went out to the red hat container catalog Verified that this is a decent image that I would approve of using I consider this registry server a read-only registry server Regular users cannot push container images to the red hat container catalog only red hat employees and and partners that have went through our Certification process can push container images to the red hat container catalog So this is a starting point now. I've pulled it down with pod man I've built a new layer and I'm pushing this out to Quaid IO Which is a read write registry now? We're in an you know a less trusted place where anybody could push something out there So you have to be careful what you're going to download from a read write registry But as long as it's in a repository that you control it's obviously fairly safe And then we're going to get down to code ready containers, which I'll explain in a minute But I at least want to kind of show where we're at So we've pushed it out there But what do we do to run it in production right as I mentioned there's this there's a fear in most people's stomach about Moving from something like pod man to moving to something like Kubernetes like typically people will stumble there And I've seen customers will get stuck there for even two or three years Where they just want to run a single container and I say it's pretty easy to run a single container on a single host As soon as you add two containers or two hosts you have to start managing the network So you have to start managing IP addresses and you have to start managing storage and I've seen all kinds of very funny I've done it myself even I'm guilty of doing all kinds of wacky things to manage storage like I'll create a directory And then within that directory I'll have subdirectories for the database container and the web service One and web service two and web service three and next thing you know I'm creating this directory structure of chaos to then map the storage back to like which container connects to what as soon as you Have two containers I that is the the base case if you will recursion If anyone that's familiar with Persian the base case is two containers or two two servers And you want two containers to make it easy to organize the application You want to servers to essentially provide for failover. So it's a it's an HA or a high availability thing But either way it starts to get hard and that's when we have to start to think about running something in production Um, and I mentioned that so this is where something like open-shift or Kubernetes comes in To demonstrate Kubernetes. I am using in this lab environment. I actually have Everything I've showed you so far here with podman is on a fedora box in a virtual machine Running on rel 8 system and then code ready containers So code ready containers is a way to run open-shift for In a single virtual machine on a laptop for example in this case. I'm running it on a laptop Open shift for is is is a very sophisticated piece of technology Even though I don't think people have fully absorbed what it means it is an op it's based on a technology called operators and so the way open shift for installs itself there are a few base container images and In fact even the operating system itself is saved as a container image out on our registry server And I out on clay.io actually and gets pulled down installed, you know installed on a virtual machine and then all of the other components of open-shift get pulled down as container images and There are these things called operators which are essentially I consider them robot systems administrators They know how to do the final deployment of all these different pieces of software They also know how to do backup and recovery and upgrades and downgrades of all the different components in open-shift So open-shift is essentially a microservices based application itself the platform and it is managed by these operators This makes it extremely easy to install with a single command But then all of this automation is running and you're kind of like I hope you know, I'm relying on red hats I'm in fact, I'm even relying on other engineering teams expertise to make sure this whole thing works This is very easy to do with code ready containers Code ready containers adds one more layer of software it adds like an installer script And then this installer will essentially log into Libbert create a virtual machine on my laptop Bring up that virtual machine Deploy the the core OS red hat core OS image that is the operating system for open-shift And then deploy all the container images and components and gets a full completely working open-shift environment running in a single VM On my laptop now, I do this instead of connecting out to Amazon You could actually do the exact same thing with open-shift and then just install it in Amazon or Azure or Google Cloud but but for the point of a demo. I just wanted to have it all locally so so that we're not going out to the internet So basically we're just having you know, we are pushing we've pushed that container image out to quay. Oh But now we're gonna pull it down and run it in open-shift But the problem as I mentioned earlier is people get stuck here, right? They're they're worried about okay now I have to get from podman to kubernetes I've been stuck in this find build share kind of model And I've been doing it on my laptop with podman or docker, but now I'm moving to kubernetes is tough so to the rescue is a command called kube generate or generate kube I called kube generate but um podman generate kube is a really magical command that basically will allow us to Do that simple model of just running a container and then run another command to export the yaml that I can then run in open-shift So for this demo, I'm gonna show you here what I'm doing I'm running a single container that that one that I just showed you that I pushed out to quay.io I'm running it locally in podman on my laptop Or actually in this VM Here it is running So now you can see with podman the container is running I'm running the latest version of that's been up one second and now once it's running I can take this podman generate kube. I called it. I call this Container tron and then tron dot yaml. I'm just making it the same names that I can see But um and then here I'll show you I'll generate the kubernetes or the kubernetes yaml Then we'll take a quick look at it. So as you can see I'm lazy because I've been doing this way too long like 20 years and I hate writing Giant long config files like this, but podman just allowed me to do this Now I can hack on this change it a little bit if I need to but the beauty here is it's actually already created the pod definition for me the container The container definition the command all the things that I have to do and so now once I have this kubernetes yaml I Can go out to my open shift cluster You'll see I have my code ready containers open shift cluster running the master It's working again It's an all-in-one install where the master and the worker are both installed on the same node You can see it's kubernetes 114. It's 21 days old For the win and then I could see the projects that are in open shift So there's a bunch of projects already configured by default in open shift and think of a project as a It's a mechanism for doing role-based access control So you will create a project and then give certain users access to that project and it's a way to make kubernetes multi-tenant So that different people that don't trust each other can all use the same system in this case I'm going to create a new project called tron You'll see that I now have created it open shift has a really nice Command called new project And that makes it real easy. So then I get projects. You'll see my new tron project is here And then I am now going to I just submitted this OC create command It's essentially a kube cuddle create command this dash f means file I pass it that tron yaml file now I'm going to run the exact thing that I had running in in podman with a single command in kubernetes with a single command So we're going to go ahead and watch this actually it already came up Because I had already cached all the images and everything is local So this actually ran very quickly the first time you run it It takes about 30 seconds because you have to pull all the container images down into the code ready containers environment It has to cache it, but this time it ran very quickly. So we will get out of that And then we will watch we'll take a quick look at that. So you'll see in kubernetes We have a pod running. You'll see it's assigned it, you know Essentially to that to that master We pulled down the image you see from that image that I pushed out to quay.io and now locally we have this thing running So let's take a look at it So there it is single pod running with a single container in that pod Running in kubernetes with like two commands. I didn't have to write any yaml whatsoever, which makes me very happy I hate doing it, but I like hacking on it once a now again It's not because kubernetes is complex It's because the business problem is complex running a bunch of services is complex nonetheless tooling can make this easier, right? So this is great I just showed you a very simple use case with a single container just to kind of get your brain around it, but Now say I want to run multiple containers that talk to each other in a pod How many of you know what pods are? Okay, good good number of people know so a pod is is just a concept if you will there's a definition There's there's a technical implementation of pods in kubernetes as in there is go-lang code that defines how a pod works in kubernetes in podman we actually have The same logical definition of a pod but different code so we have our own implementation of how the pod actually gets fired up But it's the exact same concept It is a Essentially a thing that contains one or more containers running on the same node So, you know with podman you don't run multi-node applications, but you can run multiple containers in a pod on that single host The beauty of this is is you can model an application with different pods in podman and then move them over to kubernetes So in this scenario, I'm going to show you a quick Definition here. It's very easy to create a pod in podman to be honest easier than writing the yaml in kubernetes So I go and create a pod And then here I'm going to create a container running in that pod So you'll see the dash dash pod option I'm telling it run this container in this pod and then I give the name Flynn For those of you that recognize my tron references. I don't know how many of you like the movie tron again. I'm showing my age Podman run we're going to add another one. We're going to run bit. Does everybody remember who bit was Okay, good As like a seven-year-old this was pretty amazing. I'm just going to point out So Now Actually podman has a really cool feature here this pod pod list It'll show us the namespaces. It'll show us the container names now. This honestly is one of my favorite commands because So many people if you were in my talk yesterday fundamentally don't understand what containers are, but this shows it so clearly so Here's the name of the the pod Here's you'll see the cgroup that it's running in you could see the namespaces in the kernel that have been created So now we know exactly which namespace is the clone system called used to create this container And then we could see bit flin the two containers and then we have this infra container How many of you know what a pause container is? Some okay, so with this concept of a pod The ability to run multiple containerized processes side by side on the same host and share namespaces Which is what this is showing so again I keep adding processes to those namespaces and now those namespaces can share memory Could share network can share things they essentially live in the same virtual space in the kernel But to do that I have to create a process You remember before I showed you if in my last talk I showed you when you create a container It's just metadata on disk. There's no process running. Well with a pod you need to have some process running So that you get all the namespaces it essentially holds the namespaces open And then you can add real processes to that namespace and add the actual workloads that you want So there's something called a pause container And this is true in kubernetes as well as in podman when you create a pod So this concept of a pod requires this thing and essentially a pause container is nothing more than a very small container image That has a single command in it that runs pause that basically just creates a process that is a while one loop That just creates a process keeps it open and doesn't exit And then that process stays alive for as long as the pod is alive And then when you kill the pod the pause container goes away, but it does nothing more than hold the namespaces open So we can record we can now see this is where the proof that the implementation of a pod is different in podman You'll see that this doesn't look like kubernetes yaml This is actually the internal data structure representation of a pod in podman, but it's pretty easy to read You can see the the three different containers. Um, you can see their IDs Um, again, these are just metadata that you know metadata labels that represent them You can see the c groups again. We're kind of seeing a more robust version of what I showed you with the ps command um And then here you can see It's something I highlight here You can see I had that first container that I ran bash the tron one And then you'll notice that flin and bit are the new ones that I just added to the pod But where's the pause container? There's no pause container there So there's we have sort of these rules that are kind of arbitrary, but we make it easier in podman We don't show you the pause containers. We just show you the actual workload containers But again, I think this confuses people so that's why I love that ps command Where I show you all the namespaces and you can actually see the pause container and the two workload containers together So all right, so now I have these two these two containers running side by side in a pod and now I want to export these So again single command instead of passing it the name of the container I pass it the name of the pod And then I also added this little magical dash s option So, uh, I'll do this just to kind of show you what it does this this will create the kubernetes service for me And then let's look at this now. I've created A much longer kubernetes yaml file that I really wouldn't want to write from scratch So again, just two containers running side by side.  This is probably the simplest way to represent it all in one file You know, if you think about what a kubernetes yaml file is it has all the definition for the containers It has the the network information the ports it automatically wires together the containers So I don't have to worry about the ip addresses It also, you know wires together the storage it will automatically pull in volume mounts and manage all that So I don't have to worry about that myself The environment variables But then the magical piece is the service So this is what exposes it to the rest of the kubernetes cluster, right? So we create this thing called a service that exposes these two containers to the rest of the to the rest of the cluster basically and again Podman did all this for me. So now let's get out of here and then I'll show you how to run it so again I had to create another project. I decided to use the second movie tron legacy as the name And then get projects. Let's show you I've created new projects. So now I've got a new place I've ran the one container in the one project and run another one in the other one single command. Let's watch it And then we'll watch it get created so This is probably a good time to explain a small thing about kubernetes. So kubernetes works on this concept of a defined state actual state and then eventual consistency between the two so If you look at old infrastructure the way we used to do it 20 years ago It was There was we did use things like configuration management and configuration management was an approximation of a defined state And then you would run it over and over and over again if it was idempotent hopefully Getting the environment to stay kind of in line but entropy You know basic entropy will say that if you have a thousand servers over a month or two months or five months Or a year they somehow end up getting out of sync Whether it's like arbitrary physics breaking something or if it's a human being getting in and changing stuff So it was like a slow lazy version of this But kubernetes on the other hand with a single config file again Not 20 different config files, but a single config file defines the entire state of that application And it will then go out right now It's making the the actual state in line with the defined state You can think of that when I submit this to the kubernetes api Now it's running and the defined state in the actual state are actually in alignment And because this is not that complex of an application and there's only a single node It's pretty easy to keep in alignment now You get out to you know kubernetes cluster with 500 nodes and an application that has 12 different services And you actually have things failing and network kickups and all these things this this job gets a lot harder But the beauty here is is I don't have to worry about any of that I can let the platform worry about that And again if I want to delete this that's actually the the real magic So now we have our pod running We have actually uh, you see both of these containers started you'll see here that Pulled the images started flin started bit You'll see that the the tron legacy You know pod is alive blah blah blah and then um Let's show you here. You see the pods There's only a single pod in this project the other pods running in the other project But this one has two two containers Um, but now let's do a bonus here. So I've got some time. I think I can get through a couple different bonuses Um We we can all we can I showed you the generate for kubernetes, but what if you really do want to just run a single container on a single host You know like I really hate writing system d files too Like I'm not really into writing files at all. So I'm pretty lazy you can actually do the same thing So I mean the way the podman team is thinking is really elegant and that In that we just are like, you know what if I can write if I can run it with a single command Why should I have to write all this? You know service files definitions. Why should I write all this yaml if I can start with something then hack it Maybe exactly what I want Uh, but you'll see here. I showed uh system d you can do that with pods or with or with containers as well So it's really nice now Again going back 20 years How would I have stopped all of these services if I had deployed if I had deployed a service as simple as two Processes running in my thousand node cluster 20 years ago. How would I have deleted it? It was a giant pain We had we had what were called runbooks and in that runbook we would have 30 different steps that we had to do we had to go delete dns. We had to go Deprecate the storage back it up push it out to a backup place Do all these different things And it was a nightmare and I almost always broke something when I was deleting the service and then worse two years later We would see something that we'd forgotten because there was some edge case that caused it to not get deleted or whatever And it would break, you know, and you'd see you'd see these legacy pieces of oh, I thought we deleted that service two years ago Oh, we did we'd have to go look through our ticket system and realize that we actually deleted it So you had to like figure out from the ticket system what you'd actually done We're now with kubernetes all of that's done for you like literally it's logging what you've created and what you haven't And what you've deleted and what you you know with deployments I don't want to go super deep into kubernetes But with deployments you actually have trackable history of when you scaled the app up when you scaled it down when you created It when you deleted it it's beautiful.  This is actually where it gets magical Again, I could create a very very complex service out here in in kubernetes But all I have to do to delete to here's here's what happens the business person calls me up We need to delete deprecate the service. It's we're not going to use it anymore. Okay. No problem Here's a single command to delete that we're deprecating the other service Okay, boom done and demo That again, I think the breakdown of it almost is as magical as the creation of it because we were able to create it With a single yaml file that we exported from podman that we just ran So we could hack on it hack on it get the way we want build the yaml file export it run in kubernetes Now I want to show you this is what I had went through I have like five more minutes So I'm going to show you one more demo This is what I showed you in the main demo, but I built this the other day So I get I get this question of how to use azure pipelines with ubi And I think this use case is interesting from a cloud native perspective So you'll see it looks quite similar to the use case that we just did This I would consider like this is the find run build journey right here But this is sort of the cloud native journey a lot of times we don't even want to build it locally We just want to build it out in some service. We want to have like azure pipelines or Jenkins or or you know Sierra ci or something like that go out and build all this stuff for us over and over again I don't want to mess with it. So but but if you look it's still a similar thing I want chain of custody, right? I want to have the chain of custody from the red hat container catalog into azure pipelines in an account I control then I want to push it out to quaid.io And then I want to share it only with the hosts that I want consuming it. Um, so the the process is pretty similar um I didn't I forgot to actually show you this when I push it out to quaid.io I meant to show you here are my repositories out at quaid.io You'll see some of them are public and the ones with a lock around them are private Um, and they're only private because I forgot to share them but but um, but you again You can kind of control what you want out there. So in this demo I show I actually created an azure one Uh, I believe it is called ubi azure pipeline source So I you'll see I have two different repositories out there This is actually one that I created for the source and one I created for the build. Um, but but basically in a nutshell What azure pipelines allows you to do is use a single I'll go out to azure pipelines and I'll show you this It allows you to use a single, um YAML file to cause the builds to kick off. So again, our build might look something like this where we have like a docker file Um, and then our I actually show how to build this source. I just uh, I just installed ssh Which I don't even actually know if you need to do um and then here You'll see it's an azure pipelines file is quite similar to a kubernetes file in that it's like this yaml thing But it defines here what i'm showing you is we pull from we basically pull see we pull from red hat Universal base image from the container catalog and then we push the image to quaid.io And now the beauty of this is this service is sitting out there and it's just doing whatever it wants And uh, the only time it will change is when I make a change to the to the docker file or this file So essentially it's a git ops workflow where when I go commit a new changer to github It will actually so let's actually go and do that and then kick off a build Let's see what I can do here. Let's um, let's go to This is where I get it off the script a little bit But let's do this let's do uh Let's actually add a yum install So ssh, I don't know See what what that does it might fail But whatever so I've made a change here And you'll see in my pipeline here Oh, you'll see it kicked off the job right because what happened is azure pipelines saw that I changed Oh, wait. No, it didn't show it yet It's supposed to There it is. All right, so it did kick off a job. You'll see now. We have a new job running I made a commit to github now automatically azure pipelines is is seeing that I changed something and now it's running this job And it's doing something quite similar to what I showed you with podman But it's doing it it's doing it out at azure pipelines And you'll see it'll actually just walk through and show you what's going on And then when it's done it will push the image out to quay.io and I'll have a new image Um, and so it's it's actually a very elegant workflow So here it goes it's pushing it boom It's actually the same or it should be pretty similar but Past their finalized job. So now boom succeeded. So now this did all that human work I I'm now out of it like I might have started with podman And then once I kind of get what I want, you know, and I kind of hack on it locally I can now ship that container, you know that that build file the docker file out to azure pipelines Or some other service. I just show azure pipelines because people kept asking me And then you can see now you could apply this this methodology to anything And now this really helps you stay in that integrate deploy side of you know, I showed here This will help you stay in this territory, you know, where it's just kind of constantly this this most of this stuff over here should be automated Right, so I would consider that azure pipelines part of this integrate thing where you would just have that integration happening automatically Every time developers change things things will just kick off and build and we will only worry about it if it fails basically So with that I'm going to close and say, you know, there's there's some information here. I show a little bit Um, and then I have some more here where you can read some things. I publish prolifically. I read a lot of blogs There's a blog on that azure pipelines how to set it up if you want Um, I don't think I put it on here yet because I just published actually I think it publishes monday I'm sorry. I think that azure pipelines blog that shows how to do this. So it's like really fresh material Um, but if you have any questions, I'm happy to answer them. I think I have like five minutes Does anybody have any questions? Say that one more time Yeah, we we basically just use the kubernetes api. So we just we just target the kubernetes api So we just implement it exactly as it is that would be fine Um, so so let me let me back up and say, okay So you said how is compatibility between podman export generate kube and and kubernetes The short answer is we don't implement all of kubernetes We implement a very small subset like service and pod and container So just the bare minimum to get you started anything more advanced than that you're going to be You know hacking that yourself, but it's at least enough to get started and then we do the same thing the other way So you can pull a very complex kubernetes yaml file out of kubernetes and run it.  It will just run the pods and containers in the service We don't even do volumes yet, but we're working on that But but yeah, it's enough to get you started It's never meant to be a production thing more like something that you can kind of easily get between the two to bridge the gap And also I think it targets that use case of of docker compose Like in my mind my annoyed, you know old creaky sysadmin bones I get annoyed by having two different config files docker compose and kubernetes yaml And they kind of do the same thing and we can't share them and it's annoying to me I would rather in a perfect world I would rather everybody run a single node kubernetes and just share the kubernetes yaml files But in lieu of that because not everyone will do it. They get annoyed At least podman can play them So you could you know one one podman user could generate the other one could play And you could share the kubernetes yaml files between each other instead of the docker compose file So that's that's kind of the use cases Any other questions? Uh, you can do signing with scopia. You can do simple signing with gpg keys So if you look scopia has a sub command for signing Um, and so you build them with podman Then you sign them with scopia and then you push them and you can move those signatures wherever you want They're just shared on web servers It's uh, it's configurable in podman and cryo to go verify those those signatures You just point them out to a web server basically and they pull the the gpd keys and they'll they'll verify And so you can prevent it from pulling you it actually works on poll it'll prevent a poll if it doesn't verify the image If you want to set that up What was that? Oh, yeah, I'm sorry. He asked what about signing of container images And so I was explaining you can do with with with scopia I didn't quite understand the question um What do you mean? Okay. The question is what if you use helm, but I don't quite know There well, I'll say this there's no plan to be able to run helm with podman That feels pretty advanced. I feel like if you're down the helm route that far you probably want to run a kubernetes instance locally That's my architect brain speaking. I don't have the answer, but that's my that's my recommendation Yeah Yeah, I think I think the lead developers of podman will kill me if I come back and say that I want helm support I'm looking at dan right now. I see him over there shaking his head Um, so here's the problem with product management the job I do I have unlimited wants and a very very finite budget And I probably would say again A developer is not blocked from doing that today They could run code ready containers on their laptop run helm in open shift 4 and do all this development But it's going to eat up more resources, but it's at least you're not blocked It's just suboptimal like you would rather do with podman. I totally get it But I couldn't stack rank that as one of the highest Priorities for podman Any other questions? Are we done? Okay, we have four minutes Somebody could you repeat the question one more time? The this this I heard Oh cry ctl versus podman. Okay, so the question is what's the difference between Cri ctl and podman. Okay, hold on. I have an I have your answer Cri ctl podman Hold on watch this. I actually published this So I actually I think I published this or maybe dandit. No, I think I think I did No, it's dandit. Sorry, I I stole Dan's thunder But I did do this drawing for him. So I I feel I feel happy in that So in a nutshell, I would encourage you to read this but In a nutshell cri ctl is a very simple utility The only things it can really do are like look at the images See what's running it can like do a ps it can do images It can do it has a few sub commands, but it doesn't build images. It doesn't do It's a very I would consider it a troubleshooting utility in production Versus podman is more of a developer focused use case where it's very rich A rich set of sub commands to do all kinds of things Cri ctl is just a very bare minimum to troubleshoot things mostly In a and also just to be compatible and help implement the standard the Cri standard It's like a human interface into Cri So that at least you have some utility to troubleshoot of Cri is actually working right that kind of thing All right, I think we are we have two minutes. I think right With with uh with ubi Well legally, so this is the funny part sadly, I've become way too accustomed with the lawyers But uh in a nutshell there's nothing illegal about it, but we would never support it So running it wouldn't boot it has no kernel So if you export as an ovi ova, all right, let me repeat the question The question was can you use ubi like if you exported redhat universal base image as an ova file an ova file is a is a standard for saving virtual machines for for You know kvm and the short answer is if you did it it wouldn't boot because there's no kernel We don't release the kernel because in containers There would be nothing illegal about that but to be very honest It would be basically useless because it wouldn't be supportable In that scenario, I would probably recommend just using sento s so he asked if you added the sento s kernel to Ubi to boot it would that be the question then becomes is why do it because like I'd rather just use all the sento bits that were built together and kind of work together and then Relying the sento s community to support me because redhat would never support this frankenstein thing Okay, we are done. Thank you everyone


Yeah, we on boss talk, one-on-one, one-on-one. Yeah, we gon' talk. You've been ripping through the internet, I call it. It's not like it used to be when you was doing CDs. How did you end up starting to rap? Believe it or not, me and my partner shot the little John. We were watching the Boosa DVD one day. It was right before Boosa went to Prius, his third DVD.  And he was like, man, bro, you doing everything. Boosa doing, you taking care of all your homeboy, your kids, your family. You got a story to tell. He say, try putting it in a rap. And I tried it and it's been on every cent. So when you put it in a rap, and did you look up to what Boosie was doing, for just him being the type of rapper he was? Yeah, that was my dog, but see, I came up in that, I was on that Soulja Slim, C-Murda Mac. You know what I'm saying? Boosie, we have it, you know what I'm saying? So, yeah, Savvy, you know what I'm saying? How old were you? When I first started rapping, 25.  How did you try to get on? Cause a lot of times people don't know how to get on when they first start. Let's talk about that for a sec. See, I brought the, you can tell how you want to talk about it. Yeah. Okay. Clear stroke, this is the old news talking. I brought, I just brought the dope boy mind frame into the music game mind frame. If I'ma do it, I'ma do it.  So what I did was I got in the rap game, met some people in the weeds at them. I linked up with Boosie because of Hatchboy, the dude, Loco, that sang on All It Hooks. We linked up and shot the Johnny Redd, he wanted to boost the right hand man. So, boom, I made, I started making music. I linked up with Hatchboy. I said, oh, I hit him. I said, how about you going for a verse? I hit it because I talked all about verses from all of them. You know what I'm saying? Now, I got verses from all of them. You gotta be small, y'all think like a dope. Well, let's put a visual with it so they can see who this dude is on this song. They know he do. They don't got no face behind this thing. So I went shot, went out there, shot video, we started, we made bones. And they been on everything, Boosie got the jail. I did a couple of shows, tours with them, him, Weber. And my name's, they got known to Mr. Servon, found out about me shot, Mr. Servon from No Lim, and you know, he my mentor. Him and Young Bleed. And my name just got to ring him, bro. So, so me, you gotta put money behind yourself. So you, when you first met Boosie, you conjured up, I'll say, this relationship with all of these guys that do the work around him. Right. And say, I'm gonna work with them. And it really wasn't targeting Boosie, but just getting that whole machine behind you. Yeah, because you got to think about it. Yeah, because he was gonna be the hot of dude when he came home. Yeah. So it don't, nobody know you.  I paid for these verses. That's right, that's right. You know what I'm saying? I paid the ride I had to go on these two have, nobody for no money, for no hotels, no food. I brought everything. Wow. You can't do nothing but respect a hustler. But so when you do this with them, you build a relationship up. Boosie come home, you meet Boosie. How does that go? I meet Boosie. We link up. You know what I'm saying? We was in the studio one day. He was like, look man, I like it ground. He said, man, wherever I met you at. Wow. She said, come on. That's fave. He said, I rock with you, bro. He said, you rock with my family. I rock with you. We just been cool ever since. So that's a dope, dope way to be. So he's seen the grind in you. Yeah. And me and him managers, you know, we so cool. We can talk about, I know, shout in TQ. Yeah. So it's all love, bro. I was on the phone with shouter about a month or so ago when I was trying to get Boosie made about two months ago. Yeah. You know, me and him, me and sir Charles will be out there at birthday bass. Charles on it.


Hello, people of the internet, my name is Johnny and welcome back to some more Five Nights at Freddy's News. We are approaching the seventh anniversary of this beloved franchise. And so today, along with the more traditional FNAF news like the Fazbear Fright Books and Pop Goes Evergreen, we also have a few details on what we can expect on the eighth for the anniversary of FNAF. And I'll tell you exactly what you can expect. A seven hour stream from me over on my Twitch channel, twitch.tv forward slash Johnny blocks. Yeah, we have a tradition where every year I stream for the certain number of years that FNAF has been out this year. Of course, being the seventh anniversary means I'm going for seven hours. So if you want to watch it, it's twitch.tv slash Johnny blocks. I'll also be streaming tonight. Also, make sure to subscribe to the channel because we do have some very exciting stuff coming on the eighth and you do not want to miss it. So speaking of the anniversary, let's kick off this video by talking about the FNAF and Hex collaboration. Hex is Darko's brand. Yes, his official brand and it's doing a collaboration with FNAF and Scott. And in the past, we've seen the Freddy plushie, the Bonnie and Fredbear plushie. And they made a tweet the other day saying, so it's FNAF's anniversary this Sunday. It sounds cool with eyes. So I think we can expect some more FNAF Hex plushies reveals on the anniversary. So far, we have yet to see the Chica and Foxy plushie. Also, maybe they finally found out a way that they can make the Mangle plushie. I don't know, some very exciting stuff. We're going to have to stay tuned and find out what we're going to get moving on now. I have some book news starting off with the Freddy Files Ultimate Edition. It appears that they changed the official face of the book from FNAF AR Bonnie to Freddy Frostbear, which I think is a great addition. I think having Bonnie on the cover was a bit weird. He's not really a new, interesting character, no offense Bonnie. So I think putting Frostbear on the cover is a great idea. I will say the render that they used does look a bit strange, but honestly, I think it looks fine. The Ultimate Guide is going to have info on how wanted, cross the Dreadbear, the Fazbear Fright books, and of course, now for FNAF AR. It comes out on November the 2nd, so we don't have too much longer to wait. Speaking of the Fazbear Fright books, the titles for the chapters in the 10th book, Friendly Face, have been revealed. Of course, story number one is Friendly Face. Story number two is Sea Bonnie's, and then story number three, Get This, is Together Forever. Which means, yes, Scott did just Rick Roll Us in the Fazbear Fright series, because that is a song made by Rick Astley. Taking a look at the description for the book, I can definitely see the Sea Bonnie's title walking with the second story, where Mark quickly flushes his brother's creepy new pet down the drain. So I really hope that we don't see Sunken Toy Bonnie crawl out of Mark's brother's toilet, because I feel like that is, it definitely has a high chance of happening in the story. These stories are weird, man. As for Homecoming Queen Jessica and Together Forever, I don't really see where that could go. Reprogramming a defunct and matronic, I don't know, maybe it's going to stick with Jessica throughout the entire story. We're going to have to wait and see. It releases in almost exactly a month on September 7th. And then we also have an updated cover for the second box set for the Fazbear Fright series, and also the Felix the Shark book. It looks like he's now swimming in some toxic waste, maybe a polluted water source. Or it could just be a green aesthetic for the background, I don't know. And the box set arrives on December the 7th. Moving on, we have FNAF AR. It has received a few updates, both in the form of official updates fixing bugs, and also updates to the Ferdy Festival blast from the past happening right now. Do you feel that chill in the air? It's Black Ice Frostbear. Come by the Ferdy Festival for his meat and greet. So you have Black Ice Frostbear coming into the Ferdy Festival, and of course you also have Woodland Toy Ferdy. This isn't a forest, and that's no tree. Say hello to Woodland Toy Ferdy. He's your wood. Like to see you at the Ferdy Festival. I think that is an amazing render of Woodland Toy Ferdy. And like I mentioned earlier, there was an official update to the game that added new dynamic asset system for faster load times, various fixes to animatronic encounters, numerous fixes to animatronic models, and updates to the UI and localized text. But apparently for some players that added mods into their game, this caused a few issues. As you can see, Kame Carter made a tweet showing off just the craziest stuff that came with this update. Like I said, a lot of the bugs showcased here only happened to players who installed mods to the game, but the long, long username bug did impact quite a few players. And FNAF AR even made an update too, the problem saying, hey y'all, we wanted to give clarity around some issues seen on the modded games devices after downloading the new update. Our current understanding is that these issues only affected a handful of users that have modded their devices games, which isn't supported. We are investigating these cases further, but the new update should not be an issue for non-modded games and devices. So yeah, happy that that is being dealt with. It seemed like this update included a lot of bug updates that they mentioned are going to be happening in the fall update. And so hopefully soon we can see even more updates start to roll out as we get closer to the fall and the fall updates. Moving on to the final topics for the video, the Fazbear Fanverse Initiative starting off with Pop-Go's Evergreen. It looks like Kame has finally settled on a thumbnail for the game over on Gamejolt. And my gosh, this thumbnail looks absolutely insane. Again, I really, really love this new thumbnail. I think it looks absolutely insane. We also got a quick update on the One Night at Flumpty's console ports. If you remember last time, Clickteam was reaching out to FNAF developers that work in GameMaker Studio, which is the engine that the One Night at Flumpty's games are made in to see if they can help out porting the games. And while Clickteam didn't necessarily say that this was for the Flumpty's franchise, I think it's pretty clear. And like I said earlier, I do think, again, this hasn't been confirmed, this is just my opinion, right? So they've released One Night at Flumpty's 1 and 2 on mobile and so I think, right? I think, again, hasn't been confirmed, I think, that Flumpty's 3 has officially been ported to mobile and now they're moving on to the console ports, but they need a bit of help. Again, that's my line of thinking. Thankfully, it seems like they have found some people to help out with the porting of the games. And so hopefully, I mean, maybe this year we can get Flumpty's 3. That'd be pretty awesome. And now let's talk about FNAF Plus, because oh boy, this is insane. This is probably the best news that we've had in a very long time. But quickly, let's touch upon the puzzle that is apparently happening in the descriptions of the FNAF Plus videos. They made a tweet saying the titles and descriptions for the five released FNAF Plus teaser videos have been updated. Each description has been given a single new character, possibly acting as a piece of an incompleted puzzle. And as you can see, the puzzle so far has F, H, Q, O, and U. I think that this is going to be some form of URL code. Though it seems like this is too short to be a YouTube link right now. It could very well over time develop into a YouTube video link. So far it seems like this is all we have on the info, so let's just move on. All right, now we have the big ticket news for today. The FNAF Plus short, Breaking and Entering, is premiering on August the 8th. I did not think that we would get any fanverse news for the anniversary. You know, maybe an update on Security Breach, maybe the movie if anything. But yeah, we're getting a FNAF Plus short. I am super excited for this and to let you know why, Phil released a few notable details on the short. So let's go over those right now. He said it's the final teaser video planned for FNAF Plus, originally meant to release after a gameplay showcase. So it seems like even though this is the final teaser video, it does seem like we're gonna get maybe a trailer and most definitely a gameplay showcase later on in the future. But moved forward to celebrate the seventh anniversary of the series and as a milestone for the animation asset rendering. It's an animated short slightly longer than the rest of the video teasers. Okay, so maybe around two minutes. It will not feature any gameplay footage, but it will hint at some key new features of the game. That's interesting. The short is set before the events of FNAF Plus, serving as an important prologue to the game. So I'm thinking it's going to show someone breaking into, you know, of course, breaking and entering into the establishment. And then when the game releases, we'll play the aftermath of that incident. That was my guess, again, not confirmed, but let's keep reading. The short was created over the course of an intensive, busy month of animation work, made during my free time away from an equally as stressful college exam season. It includes some of my best work so far and I'm really proud of the final results. That's awesome to hear. The short, much like FNAF Plus itself, contains a darker atmosphere and some potentially disturbing content which fans of the series may not be used to. As such, a content warning for it will be displayed at the beginning of the premiere. It looks like this. Warning, this footage contains flashing lights, loud noises and content some viewers may find disturbing. Viewer discretion is advised. This is a huge step forward in the development of this game and was one of the things I was most looking forward to creating and showing to everyone since I was contacted by Scott to make this project. I really hope you guys will tune into the premiere. See you soon. Oh yeah, almost forgot. No release date of any kind will be featured for FNAF Plus anywhere on the short. Still hard at work on the game, lots to be done. I wouldn't dare put dates on a project like this when so many variables could delay it and disappoint. That is all. So yeah, now do you know why I'm super excited for the anniversary? It's so nice to know that we actually have something to look forward to. I think this is gonna be insane, but we're not done with the trailer just yet because we have a few more details. So Phil Morg, right?  Put up a poll on Twitter asking if people wanted the short now or on the anniversary and release it now actually won and Phil replied. For anyone that thinks that this is a meme or a joke, here is a screenshot of the unlisted video as I'm looking at it right now. Please don't think that this is for the laws. I'm just really excited for you guys to check it out, but I understand if you don't want me to. And then it has this image. As you can see, it is a unlisted video posted on the 1st of August titled Breaking and Entering with 25 Views. The video is 13 and a half minutes and the thumbnail is a exit door inside. And just to make it clear, it was a troll, right? He completely trolled us. We got bamboozled as always to with Phil Morg. But the meme video was only a couple of minutes. So it's interesting to speculate. Is this 13 and a half minute video actually the animated short? Or was this also part of the troll? Earlier on, Phil did say that the teaser was slightly longer than the rest of the teaser videos, which were like one, two minutes. So having the video be 13 and a half minutes, yeah, that's only slightly longer. So yeah, what do you think? Is this actually the trailer? But that is all the news we have for today. Again, the anniversary is rapidly approaching. What do you guys want to see on the 8th? I do have my predictions, but I do want to say that for a video tomorrow. So again, let me know what you guys want to see. Thank you guys so much for watching and I'll see you all on the flip side. Goodbye.


Hi, I'm Shane Harris with the Alder Cooperative Extension System, and this is Clay Harris. He is a 4-H for the Talibus County 4-H program. Today we're going to be catching bugs. We've got some bugs here that we're going to show you and some things that we video that we shot of some bugs out in the wild. It's interesting to go out inside this spring and catch bugs and see what I can find. All you need is a jar and basically a stick, maybe even a camera. So today we have 10 bugs as part of our bug show. Stay tuned. Our first creepy crawly is a wolf spider. It's not an insect, but it's in the arachnid family. Wolf spiders are hunters. They're agile hunters with excellent eyesight. They mostly live in solitude and hunt alone and do not spin webs. They're the big spiders we have around here. Next we have a pill bug or some people call them roly polies. They live on the ground in leaves under rocks, maybe under rotting logs. They feed on decay and matter and rotting plants. They're best known as the roly-poly because they turn into a ball when threatened or feared in their endanger. But as you can see, they'll soon come out and start moving around again. Pill bugs live in wet locations that typically found under damp objects or in around organic matter, especially rocks. They can live up to two years, believe it or not, and they're most active at night. The sure sign of spring is when you see the eastern tiger swallowtail flying around. What a beautiful sight to see these wonderful insects every spring. The eastern tiger swallowtail is the state butterfly of Alabama. As you can see, they're beautiful butterflies and they like to feed on nectar and other flowering plants during the springtime. The males are typically yellow with black stripes. The female can be black or sometimes yellow with the stripes. The swallowtail butterflies are some of the largest group of butterflies on the continent. They're easily attracted to gardens that have an abundance of flowers. These butterflies are great pollinators and are considered good insects. They can be seen flying in open roads, woods, meadows, even fields and parks. They're one of the easiest ones to catch and look at if you've got that quart jar ready to look at and observe. Just be sure to let them go later. Here we have the patent leather beetle, sometimes called the Betsy beetle. These beetles are really neat because they're about an inch and a half long, have dark, shiny, hard shells, and are just plain neat to look at. They're found in rotting woods, especially under stumps and fallen trees. They feed on the decay and matter in the wood. One neat thing about these large beetles that we have is that they tend to be very social. There's a mama beetle and a daddy beetle and they take care of the baby larva or the grubs in the little colony. Each parent can raise up to 20 to 35 new beetles each year. These beetles can live up to one year and are relatively easy to maintain as long as they have access to moist rotting wood. This is a neat beetle to go look for. You can even pick them up. He won't mind. All that buzzing that you're seeing right now is probably from carpenter bees. Carpenter bees are one of the first insects we see that come out that tell us that it's probably springtime. Carpenter bees are great pollinators and you will find them flying back and forth from many flowers at this time of the year. Many people mistake carpenter bees as bumblebees. They're not bumblebees as they lack the yellow part on their abdomen. Carpenter bees tunnel in wood until they lay their eggs where bumblebees actually live in colonies underground. Carpenter bees are known for boring holes into wood. You see here you see a female about to enter a hole. There are two different types of carpenter bees. There are boys and girls.


Let me show you how easy it is to automate every part of your dropshipping business. First, I'll head over to Autodesk.com and register for a trial account. Then I'll need to add my dropshipping store. Download and install this free helper extension. Now I could go to any of these supplier's websites and import their products to my store within one click with the help of that extension. I could just hover over any listing and click on this little icon up here. Now the product is being imported to my store. In the draft section, I can completely optimize the product and all of its features and options before importing it to my store and having it go live. Then on the products page, I could see all of the products that are live on my store with automatic price monitoring, stock monitoring, and as soon as the orders come in, they get automated with automatic tracking number updates. Now put that together with price automation, support for multiple accounts, virtual assistants, automatic messages to your buyers, and so much more that I cannot fit into this video. Head over to Autodesk.com right now and see how you can scale your dropshipping business today.


Abstract, this study examined the gene expression profiles of corals from a transmission experiment with stony coral tissue loss disease, SCTLD. Five coral species were included, each with varying susceptibilities to SCTLD. The study found that SCTLD-induced increased expression of RAB7, a known marker for symbiodinium degradation, in all coral species. Additionally, symbiodineacy photosynthesis and metabolism genes were differentially expressed in all coral species in response to SCTLD infection. These results suggest that SCTLD induces symbiophagy across coral species, and that the severity of disease is influenced by symbiodineacy identity. This article was authored by Kelsey M. Beavers, Emily W. Van Buren, Ashley M. Rossin and others.


Hello, and welcome. We're Kaiser Permanente, and we'd like to share a little story with you. It's your story, and it takes place in your world. In this world, you're looking pretty good. You're healthy, you're happy, but even in your best world, sometimes you might take a fall, and it's scary. Why? Because with most healthcare, your care team isn't connected. First you reach out to your doctor, then you have to find a specialist, you have to visit an imaging center, then coordinate all your lab tests, and then get all your prescriptions filled. Finally, you reach out for coverage, and they didn't even know you were falling. It's a nightmare, and when your healthcare is broken, you're broken. But wait! What if there were another way? In the Kaiser Permanente world, when you fall, our healthcare team is ready to catch you. At Kaiser Permanente, we're different. We provide care and coverage in one package, meaning the things you need.  Even better, your care team can access your healthcare record in real time, helping you get the coordinated quality care you need in a way that works for you.  So if you're looking for a healthy lift, bounce on over to Kaiser Permanente. Healthcare and coverage all rolled into one plan just for you. Kaiser Permanente, thrive!


The DFW Metroplex has so much to offer when it comes to culture, city sites, and great communities to raise families. But sometimes this stuff gets in the way. Did you know 827 million pieces of litter end up on Texas roadways each year? We can put a stop to that today. Reverse Litter is a regional campaign aimed at making our Metroplex litter free. There's lots of ways to get involved, starting with the 10 on Tuesday Pledge. Do you own, manage, or work for a company that wants to see trash put in its place? A Litter Free Lots program helps businesses keep a community clean. Maybe your neighborhood could use some trash TLC. Get your neighbors and local HOAs involved by encouraging them to target trash through litter free lanes. Start with picking up trash along your street and don't forget about recycling too. We know our North Texas cities are great and the best way to show visitors we take pride in our favorite spots is by keeping our landmarks litter free. Teach them young. Tell your kids that stewardship begins with taking care of your surroundings and that they have the power to make their campus a Litter Free School. Take the 10 on Tuesday Pledge at ReverseLitter.com and pick up 10 pieces of trash each week. It only takes a tiny effort to make a difference in your beautiful city. Don't forget to share your story with us by email or social media. We'd love to know how your living litter free. We can all make a difference together.


Item No. SCP-165 Object Class Keter Special Containment Procedures Housed in a facility at Armbiocontainment Area 14, SCP-165 is to be treated as a contagious, pathological organism. The highest sterilization and quarantine procedures are to be followed. Microwave field generators around SCP-165's area are in place to restrict movement of its dune within its containment area. Each every nine days, SCP-165 is fed live cattle weighing at least 750 kg. Description The organic component of SCP-165 resembles that of typical parasitic mites, 750 micrometers in length, with eight legs, and a genetic structure similar to the house dust mite. The main difference is the hermit crab-like behavior of attaching grains of sand to its back. It is unknown what purpose the sand serves, but the massive colony of SCP-165 numbers in the hundreds of billions to possibly trillions, creating a rather large dune. The similarities between ██ and SCP-165 are only superficial. The colony is protozoan in nature and apparently shows a collective of intelligence and awareness that is not understood. SCP-165's colony is made up of individual Akari, who don't show cooperation but rather competition in the hunt for food. Like mosquitoes, they rely on chemical detection of carbon dioxide and sugars in the air to detect prey. The Akari mites roll and bound over one another towards prey, only using their legs to climb over one another. When in contact with the flesh of animals, they release a numbing chemical toxin in their bite similar in makeup to that of a mosquito and flea bite toxins. Subjects are typically unaware that millions of mites are taking turns at grabbing mouthfuls of its flesh as they swarm around their victim. A typical swarm resembles a swirling vortex around a victim or victim's appendage. The SCP-165 colony is efficient enough in their competitor's swarming that most animals' appendages can be defleshed and reduced to bone within minutes. The numbing toxin is so effective that sleeping victims may not wake up as their limbs are eaten away. The Akari mites are resistant to all but the most dangerous of pesticides. They retreat from heat and will often seek shade when available, being the most active during the night, hunting for large sleeping prey. Their vulnerability to heat is the most preferable technique for containment. Addendum. Acquisition. It is apparent that the US government has been aware of dunes of SCP-165 for some 80 years. The area where SCP-165 was found is now a forgotten German immigrant ghost town of Fredericksburg, Arizona, in the Tull Desert near the Goldwater Air Force bombing range. The remote town of Fredericksburg was found at sometime in the late 1800s and by 1908 had become a ghost town. A passing Calvary troop reported the inhabitants had disappeared and that the buildings were empty. They attempted to stay one night in the abandoned hotel, only to have seven of their horses reduced to piles of bone. All but four of the soldiers fled in the middle of the night, saying that sand was filling the building like a flood of water. Those four were never seen again. During the late 1950s, the US military attempted to exterminate SCP-165 by turning the area into a bombing range. It was successful in reducing the numbers of SCP-165, but in the late 1980s it became apparent that a ground cleanup and extraction was needed to remove the presence of SCP-165. Mobile Task Force Epsilon-9, aka the Fire Eaters, was dispatched for the containment and extraction of SCP-165. Upon entering the town of Fredericksburg, an upturned sign was found reading Worshitz-Bondin-Krichenden-Hungreden-Sanden, which translates to Beware of the Creeping Hungry Sands. The flame accelerators of Mobile Task Force Epsilon-9 proved highly successful in glassing the sand of SCP-165 and reducing its numbers to imaginable size. A living dune of nearly four metric tons of SCP-165 was contained and transported to ABC Area-14, where it is monitored and contained.


Hi there, I'm Sandy Olnok, artist and paper crafter, and I'm here on YouTube organizing my stamps, specifically my purple onion designs collection. I have a large collection of Stacey Aqua designs from Purple Onion. This is just a part of them. I was having soup and organizing and realized I was a little overwhelmed because I couldn't find one of the stamps. That's what I was doing this sorting for because I had them all in a big bag that was not working. So I started piling them up and trying to figure out what ways were going to work that actually made sense because these were, it was just, I kind of kept them by release and that wasn't helping because I would try to find the right size raccoon to go with the right size bear and yeah, that was hard. So I took my Ellen Hudson stamp envelopes, my storage envelopes and I used the tall skinny ones and I made a key on the front of each sheet that has the animals on them and stamped them and did them by size because I figured what I do is seems a lot and I want to have all my smaller animals together because I want to be able to see them next to each other and see who's the right size to go with who. And they slowly got bigger and you can see here just the size difference you can get in the different stamps from Purple Onion and those two that I was just pointing to are making a snowman. I'll show you a card with that later. The Frog and the Bunny were my first two stamps that I got. It started my addiction and there's this really cute Santa Claus, reindeer, they have fall stamps, all different kinds of seasons. This one is one of the new sets so it's got a fireplace in the chair and all the little bits that go with it. I'll show you a card made with that in a little bit. And then this one I'm going to color at the end of this video and turn it into a Christmas stamp or a Christmas design so stay tuned for that. She's got lots of sentiments and my sentiments were like each in different places and when it's red rubber it's hard to see what things are so it's helpful to have a key for that. So these are the new ones, the ones on top, love that font. Then she's got lots of scene type things that she's been doing lately. This one's a front door and I'll have a card to show you with that. There's all different kinds of boats and cars and lighthouses and all different sorts of things you can use to make scenes. That little row of stores I'm going to do as a winter scene and then this little, I guess I think she calls it a sweet shop. It's going to be another card you'll see later. There's different background scene bits, mountains and water and all different kinds of stuff. She's got trees. This whole big one is one stamp and there's these little trees and a tree trunk with a little tree house in it, a row of pines. Goodness gracious, do I have a few stamps or do I have a few stamps? I think I have a problem, Houston. While I was stamping those key sheets, I thought why not stamp ones that I can color? So I stamped one on the key sheet and then jumped over and stamped them on a piece of Nina so I could color them with my Copics and that was really a lot of fun. It was very relaxing to just color and not be thinking about scenes. I was just coloring for fun. There's the two guys with snowballs making a snowman and this one has the little sticks that go with it. It's a little arms. So you can make a scene with a couple of them building a snowman, which I will show you in a bit as well. And these foxes just for fun, I tried coloring one with red, one with green and I like the green better because you can tell the difference better between the colors. The red is just a little too close to the color of the fox. I had really a lot of fun coloring those vehicles down at the bottom there. The Santa Claus is a really fun one to color and I speak stamp. And the reindeer, I made a gray deer because one of my followers here on YouTube told me that reindeer in Europe are gray, not brown. They don't understand why we make them brown here so I made a gray one just for fun and just kept coloring and coloring and coloring my images. This one I added a little extra snow to, I'll even add a little extra more later on when I put the sweet shop together, all those little pieces that go inside. The suitcases go with the vehicle so there's like a travel set, travel scenes and stuff. This little guy, I added snow to everything and I tried to go over some of those trees on the outside edge. It didn't cover the ink all that well so I have to do a few more layers but you'll see a card with that in a little bit. These trees down here to make them wintery trees just don't color them gray and color them with light blues and light purples and they look all icy. And then this little mushroom down at the bottom didn't have snow on it so I added my own snow to it. So here are some of the background ones that I colored. This one has light coming out from the tree house and kind of spraying out onto the snow so you get those reflections and things which was really fun. This one I cut into a long skinny one because that was the piece of cardstock I put it on and I'll have to trim it to fit on a card. Here's that big scene where again I use blue and purples for my trees and then I can just add images onto it and you have to cover those little flowers on the left of the tree there since they would not be blooming in winter. And then I sat for a long time and I just fussy cut and fussy cut and fussy cut and fussy cut and fussy cut and that is the results of all that fussy cutting. And I turned them into cards. I used a lot of this adhesive, a lot of folks in my last purple onion video asked about what adhesive I used with these and the extreme tabs are really thin so that's what I use for a lot of this that you're going to see. So here's that inside scene by the fireplace. You can see the detail of the fussy cutting which was really fun and adding all those different bits to make a scene was quite the little blast. And on the inside you can get in focus little camera. I put a little puppy in there because it was fun to decorate the insides of these cards too. Next up is the front of the house. I added some light around the lamps. I put some really soft scene on the inside of the glass. You can see through the glass some critters on the outside and then put a little birdie on the inside with my sentiment on the card. This one was the outdoor scene. Remember those trees that I showed you and the little owl was covering up the flowers and then the other two are building the snowman. I continued the snow in front of the animals so they looked like they're part of the scene. And then I put a snowman on the inside as well. Here's the truck that's in front of the little town that I had turned into a winter scene so I added snow on top of all that and I also added little critters riding in the back of the truck because I thought that would be fun for them to be going for a little truck ride. And the little guy driving comes with the stamp set so you don't have to mask him or anything. And then here is the inside with a little birdie putting up decorations. Here's the little sweet shop that I added to that scene with the trees and I put the little jars and candies and cookies and things in there along with a mouse who's working the sweet shop and her little friend who's standing next door to the sweet shop waiting for you to come and make a purchase and added lots of extra snow all over everything. So much fun. And then on the inside I put another mouse because why not, right? And here we have the tree house that now has two residents, two little bunnies or else maybe they're visitors. Who knows who the residents are visitors. But the inside seemed for this one to be appropriate to have a warm and cozy holiday season lantern. So that was a lot of fun to show you all those cards and now I thought I would do a little magical crazy coloring because people like that, right? And it's Christmas so I'd like to give you a gift of what you like to see. And I took this little mouse and I decided to turn her into a Christmas stamp. And that is not as easy as one might think but if you think outside the box when you look at any stamp you have you can often turn different stamps into Christmas stamps. I've been doing that occasionally on Instagram just for fun to see if I could do it. It's more of a personal challenge to me than anything because I just enjoy challenging myself to try something new and different with my artwork. So with this one I'm going to get rid of all of the parts of the flower. I'm going to create a little tree scene by covering all of that up with dark green and then go in with a really dark gray on top of that to create the negative space behind all of the pine needles.  I thought that would be a fun way to create a background for it. That's relatively simple. It's really a lot of flicking with the dark marker and letting that green show through but there's a lot of working around the little mouse so that we end up with her looking like she's naturally standing in front of something. You could just surround her entirely with black so that you can actually go around her real carefully with the marker but it's a little nicer if you make it look like she's integrated into that background. There's parts of it that stick out but I'm just creating lots and lots of little teeny tiny of the pine needles. It worked out better than I thought it was going to because I was a little worried that this would not be a successful experiment and that you would not be seeing it because if you hadn't seen it then I was just going to ditch the footage but since it came out cute I thought it would be fun to share with you how it actually happened. I wanted to create a little bit of a shadow underneath of her so the Christmas ball that she's got going there will be casting a shadow on the little snowy hillside she's standing on. I used a gold uniball Signo pen to create the dangly part for the ornament and then of course snow. I go through so many pens. I'm doing Christmas cards because I love making it snow everywhere.  I used the uniball Signo pen. That's what I'm using here. I've sometimes used my Sharpie water-based white pen which gives you a softer dot than this. I kind of have decided even though I like that pen I like the sharper white that I get with this and so that is what I tend to use more often and also my dog ate two of the Sharpies. I have a feeling that could be a sign so puppies and Sharpies are not friends I guess. So for finishing off my card I used some dimensional adhesive and put it on a card base with a nice white border around it and embossed my sentiment. This video is part of a surprise blog hop for Michelle at Purple Onion Designs. She has a Black Friday sale going on. You can see more on my blog about all of that. You can get the links to the next blog in the hop and they don't all have videos but they are all wonderful fans of Purple Onion Designs. I'm giving away to three different lucky winners. I'm giving away a seat in the class on my art dash classes dot com website. Class of their choice whoever wins gets to pick one and I will be picking from all comments on all the blogs in the blog hop. So go leave lots of love and you can watch more videos here. There's a playlist for all of my Purple Onion stuff if you want to see some other videos that I've done coloring her stamps and I will see you guys next time. Have a Merry Christmas. Bye bye.


Alzheimer's disease pathology appears to start in the part of the brain that handles smell, before subsequently spreading to additional brain regions and then ultimately taking over much of the rest of the brain. That's led some to speculate that Alzheimer's disease may begin in the nose. Maybe there's some environmental agent that might enter the brain through a portal in the nose. This is the so-called olfactory vector hypothesis. The anatomy of the nose is well suited for the transfer of things directly into the brain, since the olfactory nerves that stick out into the nose project directly into the brain bypassing the blood-brain barrier. That was actually a major infection route for the polio virus. In fact, public health officials started cauterizing the nasal passages of schoolchildren by spraying caustic chemicals up their nose in an effort to prevent the disease. So the concern is if maybe people breathe in some aluminum dust or something, it could be transported into the brain through these nerves at a rate of like two millimeters an hour, which is practically two inches a day. But doubt has been cast on this theory by a case report of a woman born with a birth defect in which she had no smell nerves, yet still developed Alzheimer's-like pathology. And so to date, all the supporting evidence is really just circumstantial. It is clear, though, that changes in the sense of smell is among the first clinical signs of Alzheimer's, occurring during the pre-clinical phase, meaning before there's any noticeable cognitive decline. So maybe we could use these changes to predict or diagnose the disease. For years, researchers have been trying to find markers of brain illness hidden in people's ability to smell, using all sorts of fancy gadgets. All MRI scans can detect differences in brain activation in response to an odor, in this case, lavender. This is what you see in a normal brain. This is what you see in an Alzheimer's brain. Unequivocally demonstrating that you can pick up changes in smell function due to Alzheimer's, but do we really need a million-dollar machine? An ingenious group of researchers at the University of Florida discovered all we may need is some peanut butter and a ruler. Considering that the left side of the brain primarily processes what we smell through our left nostril, and the right side of our brain covers the right nostril, and Alzheimer's strikes the left side more than the right, what if we performed the following experiment? Close your eyes and mouth, breathe normally through the nose, then close one nostril and hold a foot-long ruler away from the open nostril. After eyes, mouth, and one nostril are closed, a container of peanut butter opened at the bottom of the ruler and moved closer one centimeter upon each exhale until the person indicated that they detected the odor. Then they repeat the whole procedure again using the other nostril. In normal elderly controls, they smelled the peanut butter as soon as it came within an average of 18 centimeters, which is about 7 inches from either nostril. And in the right nostril of Alzheimer's patients, it was about the same, 7 inches, no difference. But in their left nostril, only 2 inches. The peanut butter had to get all the way up to 2 inches before they could detect it through their left nostril, and this happened every single time. Left nostril impairment of odor detection was present in all the patients with probable Alzheimer's disease. No left-right difference in the control group, but a 12 centimeter difference in the Alzheimer's group. The disparity was so great that one may be able to set a cutoff value for the diagnosis of Alzheimer's. Compared to patients with other causes of dementia, this nostril asymmetry of odor detection was 100% sensitive and specific, meaning no false positives, no false negatives. And compared to healthy people, 100% sensitive in picking up cases of Alzheimer's and 92% specific, meaning in this study, if you had Alzheimer's, there was a 100% chance of having that wide left-right discrepancy, but if you had that discrepancy, the chances of having Alzheimer's was only 92%, meaning some false positives. Now the reason they say probable Alzheimer's is the only way you can really confirm someone has it is on autopsy. Their current criteria for diagnosing Alzheimer's requires an extensive evaluation, combined with fancy PET scans and spinal taps. All these tests are expensive and hard to get, can be invasive with potential complications, and on top of that are neither highly sensitive nor specific. Unlike this, quick non-invasive and inexpensive left-right nostril peanut butter odor detection test, which may make it an ideal instrument for the early detection of Alzheimer's disease.


What do you do if you're one of the 42% of Americans with vitamin D deficiency are put on a vitamin D supplement regimen, and your levels still don't budge? That kept happening to this group of docs at the Cleveland Clinic. In our practice, they wrote, it is common to see patients treated with vitamin D supplements who do not achieve an appreciable rise in their vitamin D level after therapy despite large prescribed doses. So they did a few experiments and concluded that taking vitamin D with the largest meal improves absorption and results in higher blood levels of vitamin D. Just that one simple change in timing results in about a 50% increase in blood levels of vitamin D achieved. They conclude it therefore seems reasonable to ask patients to take vitamin D supplements with their largest meal, because it may be a cost-effective strategy that could very well help patients to achieve optimal serum levels of vitamin D.