Enough is enough.


Rendering in Blender is the part where you finally get to pump out your animation or still image out of Blender and into a beautiful image or video. To see how this all works and what options you might have for this process, let's go into the Render Settings tab of the Properties Editor. This is labeled with the backwards facing camera icon. This tab can be a bit intimidating so in this video we'll be introducing the important settings and going over some specific ones in the next few videos. But before we go over anything here, you'll want to learn how to render. To render a still image, go to the Render menu in the top left and select Render Image. To render your entire playback range, simply go into the same Render menu and select Render Animation. For hotkey users, you can press F12 to render an image and Ctrl F12 to render an animation. Now let's go back to our render tab and do a quick overview of some of the settings that will affect these renders. The first setting is your render engine. This is a drop down menu with three different engines, EV, Cycles, and Workbench. The differences in each engine are covered in the Introduction to Shading video, but I'll go over them once again. EV is your real time render engine. This is currently Blender's default engine and is node based just like Cycles. In fact, EV and Cycles can share nodes between each other. This means you can often preview your shader in EV and render in Cycles later. Why would you want to do this? Because Cycles is a more accurate, more realistic engine, but takes a lot longer to render. Workbench is Blender's preview render engine. It is technically the same engine that drives solid view in the viewport and so you know generally how it looks, but Workbench as a separate render engine exists so that you can keep your render output settings for your preview animations the same while still being able to work flexibly in the viewport. Depending on what engine you have selected, you will see different settings below. I'm going to quickly go over each one, but I do recommend experimenting with these settings when you can. Let's start with EV. Immediately you'll see a sampling setting, which allows you to set how many samples EV will take during render, both in viewport and at render time. The higher the samples, the more accurately the engine will calculate your shaders. Both Cycles and Workbench have this setting as well. Next, you'll see a few things that will directly affect a lot of the visual aspects of your render. Namely Ambient Occlusion, Bloom, Depth of Field, Subsurface Scattering, Screenspace Reflections, Motion Blur, Volumetric, Hair, Shadows, and Indirect Lighting.  To test them out, simply go into Rendered View in the viewport and adjust freely. Just so you know, for some of these features such as Motion Blur, you'll have to enter the camera view. Film is a setting that is shared by all three render engines. One of the most used settings in this category is the Transparent Checkbox. This affects the sky. If you click Transparent, Blender will automatically replace the sky with full transparency for your output image. Simplify is also a shared render setting between all three engines. It actually pertains more to the scene itself, but does have settings that can affect render. Basically what it does is disable subdivision modifiers past a specific value to reduce the overall polycount of your scene. This is typically used to help the viewport run more smoothly, but also has a value to specify max subdivisions at render. Freestyle is a powerful tool that allows you to do non-photorealistic outlines and strokes in your render based on a plethora of different settings. However, this checkbox is to simply enable it at render. The real freestyle settings are in the View Layer tab. Freestyle is also available in Cycles, but not in Workbench. And finally, we have Color Management, which is also available for all three render engines. This one is pretty self-explanatory. It manages color. Feel free to experiment with these settings as they will affect how your colors are interpreted for your output render. Now, if we switch over to the Cycles render engine, you'll see that the options we have are slightly different. The first thing you'll notice is the ability to switch between CPU and GPU. This is a very important setting for those wishing to take advantage of their graphics cards to decrease render times. If you don't have GPU as an option or it's grayed out after selecting GPU, you might need to go into your preferences, go to System and select CUDA. If your graphics card is not listed underneath here, it may not be supported. But if it is, make sure it's checked and then go back to your GPU-CPU dropdown and it should be working just fine. Sampling works the same as Eevee, but has a few extra settings you can play around with. Light Paths gives you options to change the accuracy of the light in exchange for render times. The Volume and Hair settings will affect the quality of volumetric shaders and hair particles respectively at render. You can see these in the rendered viewport for testing, but motion blur is not real time for cycles. For that to be visible, you'll have to render an image by pressing F12. Performance is an important setting for cycles, especially if you're switching between GPU and CPU rendering. Tiles are what Blender divides your image into. During render, Blender will complete the render of a tile or chunk first before moving on to the next one. The most efficient way to divide up your render depends on each shot, but the general rule of thumb for CPUs is to keep the tile relatively small as CPUs can render multiple tiles simultaneously. Default settings usually work great for CPU rendering. However, for GPU rendering, the general rule of thumb is to keep the tile large as it only renders one tile at a time, so you'll want to adjust the tile size accordingly. For GPU rendering, I typically recommend a tile size of 256x256. There are also a few other settings you can play around with. And finally, the bake category includes the bake button. This button is used to bake lighting into textures so you can use them instead of recalculating the lights every time. Now, let's go over the workbench settings. But if you're already familiar with the viewport solid view settings, you'll find these to be very similar. Workbench also has sampling, but generally it does not have to be very high, especially since workbench is mostly for preview renders. As usual, if you want to see how each of these settings affects your render, simply go into rendered mode in the viewport and tweak them as you like. The workbench specific settings here are lighting, color, and additional options. Lighting allows you to change how your scene is being lit. Studio is your default, and you can choose different presets by clicking on this sphere. You can also click the globe icon to rotate the light source direction. Matte cap is another great way to see your scene very clearly, especially during sculpting or modeling. More matte cap presets can be found by clicking on the sphere. Flat is just giving all your objects a single color with no lighting. The color settings allow you to change the color of the objects in your scene based on different parameters. My favorite option is the random option as it gives every object a random color and makes everything super easy to see. Under options, you'll have miscellaneous stylized options that affect your scene visually, such as X-ray, shadows, depth of field, and outline. That's it for the render tab settings. However, there's also much to be learned about the related output settings tab right below it. This is labeled with the printer icon tab. Here is where you'll be able to change information regarding your render output file, such as resolution, file path, file format, and metadata. This tab is not render engine specific. Now that you've gotten a general idea of what these render settings are for, I'm going to go a little bit more into detail about some of these settings in the next few videos.


We'll stay hot for now and we'll stay hot with the race to 20 before this season we teamed up with Roosevelt's RSVLTS.com slash Johnboy and Vegas said hey anybody gonna hit 20 yakkers this year? Me and Johnboy said that's a layup, BBD said that's a layup, ESPO said that's a layup, Kyle, layup season. Trevor Ploof said I don't know, I don't know guys I think it's happening, but we even got Trevor on board and early on it looked easy, yeah someone's gonna hit 20, someone might hit 30. I think Smoltz said that on a national broadcast, Johnny, um, Trevor it's getting tight, it's getting tight. We currently have Johnboy just sent me one and I have an updated fan one so I've got two charts that are now tracking it. Right now we've got three guys on pace to hit over 20 homers and one of those guys just got banged up, Taosker Hernandez. So right now I think it's coming down to the two guys on top of the leaderboard, also probably the two best players in baseball right now, Mike Trout and Fernando Tatees Jr. They each have 15 home runs, they have 18 games left so 18 games to hit five homers is gonna be tight. They need a big series, they need a big weekend or something, otherwise they could be screwed the rest of the leaderboard and Nelson Cruz still in the mix, he's got 13 homers, Mookie's got 13, Voight's got 13, Jose Abreu and Ozuna with 13 each. Those guys are pretty much on pace for 19, so again a big series gets them right back in the mix. From lower down on the leaderboard, I mean Suarez is coming back, can he get super hot?  Yeah I'm looking right now, I'm like how many games these guys play, is there anyone on the Cardinals that you know is there? This is interesting and I'm kind of glad it comes down to guys like Mike Trout and Fernando Tatees because it makes it interesting because those guys could hit three home runs in one game, you know, then all of a sudden they're there. I knew it was gonna be tough and it seemed like it was gonna be easy but you know over the long haul of the season you're gonna have the ebbs and flows, Mike and Fernando sitting at 15, how many games they got left? They each have 18 left. So you gotta figure they're both gonna play in 16 of those. 17. Nando's young. Okay give them 17. Five homers and 17, that's one a series and it's very doable for these players but still you know that's, one a series is good, like if you didn't want a series you're feeling real. Feeling real good. And I mean those angels about to get hot it's gonna be the story of baseball so. If Fernando or Mike or one of these guys with 13 doesn't have like a big one big series then it's not gonna happen. So here's what I'll say. If I'm down to two guys, these might be the two guys I want, which is fine. I also think one more name is gonna work his way back. I've been kind of on a mookie angle. I was gonna say mookie's got, mookie's got it. He's tied for the record with most three homerun games. If he could pull one of those or a two homer game you're right back. So I wouldn't be surprised to see mookie get in the mix. Mookie versus like a bad bullpen and just like crack, crack, crack. D-backs have maybe given up. I don't know if they've got them on the schedule, but yeah, mookie one big day. God, it's gonna be close. It's gonna be close. I like the two guys whose hands it's currently in. How about the bear Marcello Zuna dude? It's gonna be awesome. It's gonna be awesome to watch this and see how close or if we do go over that 20 mark. I gave the Braves fans a little bit of an apology. I gave a lot of speeches this off season how I don't think Ozuna can replace Donaldson and he's done that and some. He's been awesome. So good for Ozuna.


Good morning and welcome to the level-up hour where we contemplate containers considered Kubernetes Opine on OpenShift and in general help you to understand a little bit more about this world of containers Kubernetes and OpenShift, especially if you are somebody coming from that Red Hat Enterprise Linux background as a systems administrator engineer and so We've got a great show today in which we're going to be talking about GitOps and developing your CI-CV pipeline and some tooling that are available to help that work a little better So I'm joined today by my colleague Scott McBrien otherwise known as Stabby and We have our guest today Vincent de Maester and Mayor Friedman who are going to share some of their knowledge about what all of this is about When you hear these these letters CI-CD. I just want to remind everybody please do like subscribe and share it at everyone let people know that we're on air and Let's jump right into this So we're talking today a little bit about about GitOps and CID CI-CD pipelines and so You know like a lot of acronyms these get bandied about and everybody assumes that everybody knows what they are but Then so maybe why don't you share with us?  So I think the CI part is Kind of close like everybody understand the CI part. I think for everybody it means continuous integration and It means all up even continuous integration can mean different things for different people But usually it means I built on each commits or each PR or each whatever but on each change that me and my team do I run some set of tests and Sometimes I test a set of validation like I know the interest anything So the CI part I think is kind of simple to gasp grasp grasp. Yeah, grasp is better The CD one is like really really more difficult because people will put different meanings behind CD. It's gonna be continuous deployment. It's gonna be Continuous delivery and and if you dig a little bit more into those two and even more I I don't know the other meaning in my head, but it can depend different things that continuous deployment At least in my head means any time there's a change is deployed somewhere But continuous delivery doesn't necessarily mean this. I don't know if To this but yeah, it's the CD part is More influx and I think the CD foundation so the the foundation that kind of try to Work around those thing is is working on a paper around this like trying to define what? What is CD and and what behind this? well, so Let's let's dig into that a little bit and so let's first start with the CI P part because I think if you come from the Developer background Integration is something that you deal with all the time If you're somebody coming from more of an infrastructure background It might not be as as self-evident as you think and so may or maybe Before we dig into the complexities of the CD because it does potentially mean a couple of different things Explain to us our audience again thinking that about the folks were coming more from that infrastructure background What is it when you're what is it you're doing when you're doing integration? Forget it continuous forget making it continuous when you do an integration exercise. What is it that the developer is doing? so I'll try to to look at this from the infrastructure perspective and I have to start with the words continuous integration unfortunately because the whole essence of continuous integration is to supply confidence that Proposed changes will actually work as intended and and as Vincent said There are there are many perspectives to to look at CI and where it happens It can either happen on a pull request. It can happen after the merge so different schools tell different stories as to what CI is But essentially from from the infrastructure perspective I think the easiest thing will be to will be is to use an example Imagine you have a repo that controls your infrastructure, right as an infrastructure person I have multiple such repos and every time I want to make a change to any of my infrastructure I will submit a PR to that repo maybe get appeared to review and Essentially, I want to see that the outcome is what I expected to be even before I emerge and after I emerge is Even more important but harder to predict So the integration part come when when when different team members collaborate on the same code On the same source code to produce a single resort result, which is the artifact and that is also a And overloaded word, but I guess we can get up from here All right Well, so I think we we have a fairly clear picture there now on this integration piece which you know again I think is is very self-explanatory to to almost anybody who is working as a developer But the exercise might not always be quite as clear, but thank you for for that clear now Now let's get into the more complicated half of this this this little acronym. We're dealing with and that's CD Vincent you talked about how there might be a couple of different ways that D is interpreted It could be delivery or it could be deployment Maybe if you could give us a little bit of clarity on the difference between the two of those So continuous deployment for me is A way of doing continuous delivery first it's continuous delivery is I'm able To deploy continuously and by continuously means at given set of at a given period of time or at a given set of events but I want to be able to deploy continuously something and continuous deployment is just about the deployment like I do something I deploy The thing that I built I have confidence that it's it works because it was tested I can deploy it already directly for example in In production, that's usually what people think when they talk about continuous deployment itself When we talk about continuous delivery, it's It's encompass a broader scope. It can be The whole process that goes from source code commits to The actual deployment and in this process, there's there can be manual approval. There can be If the sets of events that's gonna I don't know for for example for container image that's gonna Run some security checks on an image and wait for it to get back etc. So The the continuous deployment is just a smaller view of what continuous delivery is I'm trying to think about the other thing Well Well while we contemplate that I'm actually gonna Ask Scott so so Scott coming from an infrastructure background Tell me a little bit about how how integration and you know delivery and deployment have looked to you because you know My recollection is you have you have worked in an environment that aspired to maybe some of these things But perhaps uh, you know, it's not always achieved them. Uh, and this isn't a former life, right? Yeah, and I think that even today we we meet with a lot of people that are Still very monolithic in their co-design and deployment A lot of the production operations folks like they they're used to shifting a large version forward all at once And with that comes a fair amount of risk, which is why I think it's very challenging to do those migrations and upgrades and deployments And so this is a a change in thinking and it says, hey, let's take a lot smaller bites of that elephant Um so that we can have a lot less risk at each incremental change So that overall we're getting to a better outcome With our software product and so, you know by breaking up the Changes to be much smaller and more consistent We're minimizing the amount of risk to our infrastructure for each individual change rather than being like, okay We're we're running this version on this operating system. Cool Let's completely change everything and redeploy it Right, right. Well, so, you know, there has been a big move in the industry towards more of a microservices approach as opposed to a monolithic approach for applications But it doesn't make much sense if you're going to have a microservices approach to deploy it like it was a month, right? and so CICD in my mind works very well with this larger picture of really trying to break things up Reduce that risk associated with updates and also to be able to push those updates without having every single piece Considered reflected and so on and it has a lot to do with the app design but at the end of the day the Your strategy for testing integration and pushing that thing out has to be consistent with having that actual design, right? all right, so that's that's that world of cicd and so We've talked a little bit about why will people implement cicd and And I guess I would ask again Vincent and mayor Is is there something that we've missed here that if if we're thinking about, you know, an it organization That might not be doing this yet. What is it that they're going to be think? What are going to be the big drivers for them that are going to push them to Pursuing a more cicd approach to deploying applications I think More said confidence. I think this is the main really main benefit because The more you build the more you try things the more you test your Changes the more you will be confident that it's going to work when you actually deploy it. So I would say the main benefit is going to be Confidence, so that's kind of confidence driven development and I would also Assume that the more people will drive will go towards cicd. The more they will have the wheel to automate things And simplify their day-to-day work um, and thus I think that would be kind of a side effects benefit, uh, which would be Because we testing because we do things more often we see the pain point we automate the pain points and and and we Kind of become more efficient day after day I think it will also reduce a lot of the day-to-day effort allowing People at the at the various companies to focus on what matters and what and the things that are more interesting I mean, I can do the same thing over and over again. Eventually I'll get tired. I want something to Something someone or doesn't matter something to do it for me Um, and and and automation comes comes for the rescue at that point So it allows people to focus on what's important and I think more importantly it allows Everyone to find issues Uh, more quickly Right, uh, if you if you, uh, only promote once in, uh Once in a long period of time you promote a lot of changes Be whatever promote means in in this context Um, you're also potentially Promoting a lot of bugs or maybe just a bug that was introduced in the very first commit of this batch of changes It would be very hard to to refactor back whereas where you deploy Single changes and you deploy everything you've discovered the bugs immediately if not even before you deployed anywhere Depending on what kind of continuous you do Right. Well, and you know what you were just saying suggests to me and this, you know I think has understood to be an underlying truth too is that there has to be a bit of a culture change within an organization once you start Going down this path is that it's not enough to simply say that you have erected the infrastructure and the You know the pipelines that everything flows through there has to be a different way of thinking And acting and working together That compliments that because you do have to change some things because of the very facts You know things you were just talking about and so um That kind of really moves me to another question, which is You know in your experience What are some of the recommended practices that people should be thinking about? When they are moving to this more CICD approach and they are trying to build out a CICD approach so I think One of the things that are very important um Happens during incidents when suddenly something happens in the in your production environment and you need to You need to find out what's going on immediately. So one of the more important things are traceability We need the CICD pipeline to be able to implement traceability in such a way that no matter where in the Either the supply chain or in the environments you look you can see exactly where everything came from What pipeline deployed those changes? Uh, where was that pipeline created? What triggered the pipeline? What are the the code changes that were introduced or what is the process that caused the current environment to look like it does? So traceability is super important I also I also think that to a certain degree what's important in these processes and something that's Important to design up front is reproducibility. We want the pipelines to generate the same results Every time they run regardless of when they when they run And and with that also comes Also come thoughts about When am I going to do each action in my pipeline and am I okay for choosing to do several actions more than once? one example would be If you're deploying on to open shift and you use container images And you deploy something promote something to production. It's important that the promotion notion Stays with you as in I am promoting a certain version of my Of my code base of my of my binaries artifacts Deployment manifests whatever it is. I'm promoting something that was already built and tested in stage So there are I've seen multiple examples of pipelines that build the container image More than once for example once for the deployment in state one for production So I try to avoid these things already in the design phases of the pipeline and and and and practically one of the important things to To consider is how the pipelines Match the current working practices of the organization One example will be the branching strategy the CICD pipelines need to match the branching strategy For them to actually Deliver what they need to deliver which is a seamless experience for a developer From merging their code to that code being in production. So it has to match the current working processes that are already established And and obviously more Um technical things like the structure of the different repositories and whether there are differences And what will they be and how do you how do you generalize everything into a single concept And then implement the differences Well, you know, uh, first of all, I love the idea of a promotion notion I'm gonna use that from now on. Um, so we you really covered a lot of interesting ground there in terms of How you have to think through the specifics of an organization and how they work is that there There isn't a one-size-fits-all necessarily that you just drop this infrastructure in and it's going to uh It's going to work for everybody And so, you know, one of the things that caught my ear in particular was talking about your branching strategy And how that has to actually be Congruent with the way you set up your pipelines. And so, uh, vincent, maybe uh, could you talk a little bit about the relationship of Of sort of branching strategy and the pitfalls that might arise If you don't have a good, um If you don't have a good fit between that approach to branching Versus the way you set up your pipelines I I mean, I'm not sure exactly what but more was referring to for the branching strategy Okay, well Tell me what some other pitfalls and then I'll put him back on the I'll put put put him on the So, yeah I think the for me the I'm very biased on these topics sometimes um For me one one very important pitfalls that happen a lot is time yourself whatever runs into your safety to a specific Or safety orchestra like I don't know Jenkins or our Travis or whatever and and this Used to be something you didn't really have the choice In the past But now with with the right of container images, this is right if you design your Steps and your pipeline correctly you each and every actual unit of work Doesn't even need to know that it's part of the pipeline You just need to have a set of inputs a set of outputs And and not and then you can use this Uh elsewhere I don't today you you're using tecton for your ccd tomorrow is going to be something else If you design it well You just kind of have to move to a new language of description But the actual core value of what your ccd does is there and usually you see this is one of the pitfalls You you tend to tie yourself a lot to whatever the tool you're using And then when this was not maintained anymore or when it's like I know a person performance Uh, Pete or anything then you're you're kind of stuck to reinvent a lot of the wheels um when you switch and and And now that we have container images, uh, and that's where I'm very great because I used to work for docker before etc so I'm like Container image for a long time and and I'm I'm yeah Yeah, and yeah, it's it's okay. Yeah people can work for docker and then read it Of course So on that note Um mayor, I do want to return back to that question on the on the branching again I want to sort of explore some of the pitfalls that were That an organization might bump into when they are doing cicd You call that out and I can kind of imagine that but Give us a little bit more color around what happens if for example your branching strategy Is not consistent between your pipeline and and and how you actually do branching in your code base So I think that uh, vincent actually answered that question. Maybe without even understanding it Uh, the one the pitfall that he mentioned was not tying your cicd system into the Orchestrator or build tool like Jenkins or uh, whatever else you're using now We've all done it in the past. We only you only learn what not to do by actually doing it in the past I even have blog posts saying you should tie it to the build system. It's amazing But I think the only thing that's common underneath is is really git the source code itself, which is usually git Let's stick to the git example And when you stick to git to either tag your artifacts or define what you want to deploy and promote and when You're actually loosening yourself Decoupling yourself from the build system by using the git commits. So for example A relation between a cicd Between cicd pipelines and a branching strategy, maybe Whenever someone merges something to the development branch, right? I assume some an organization is working with git flow Whenever someone merges to the develop branch, we want an image built and deployed to the dev environment And then you have the main branch and whenever someone merges or something gets merged into the main branch We want the image the artifacts built again And then we want to deploy to stage So that is already a connection to a possible very minimal merging strategy with a develop branch and a main branch And and that may also connect to the previous points about continuous deployment or delivery Which is indeed the difference in the process and if there is a button involved there in the middle or not Or at least that's what the legend says And and when you want to this so everything from the main branch At least in our branching strategy goes directly to the stage environment after it's been tested in a dev environment prior And when we want to promote something to production We again go to emerging to a branching strategy, which is don't do anything Just choose a commit shot that worked in stage and promote that So we're very github scene that way and we are decoupled from the build system Which is the pitfall and we also did the sort of Connection between a git branch and an environment So you get a direct link and you know if something is wrong in production Look at what commit shot is broken something broken in stage. Look at master at the main branch and so on All right. Yeah, so scott um anything you want to add on any of this, uh, you know because uh, I think This is a natural transition for us to maybe start talking about About what are some of these tools that people use because uh, because I think there are things that We offer and that can help with this but before I turn to that Is there anything from your experience or from what you hear from customers? That seem to be some of the pitfalls that they're bumping into I was just really excited. I mentioned this in chat to hear mayor talk about promoting Um artifacts throughout the pipeline instead of rebuilding each stage because you know, there's been more than once where uh, maybe even at the crimson haberdashery where, uh Production systems in no way match death or stage. You don't find out until you actually deploy it and then it's like, oh no So yeah, that was excellent All right. Well, so Let me come back to this question then, you know, uh on the tooling and and you know, Vincent you raised some interesting questions in points about sort of Where the build system fits in but let's look at this from a broader perspective in terms of what is the tooling That people are using To be able to build effective cicd pipelines. What is it that that we're recommending and thinking that Are tools that can lead to success in a variety of organizations? So I think the the the tool that everybody knows Is and and where everybody has a kind of a Love-hate relationship with is Jenkins. Uh, it has been around for I don't know probably 20 years or so Um, and this is like this shows this is up until even now There's new alternative and we are developing your alternative, but Up until now, I think this is still the main The main tool that everybody knows it comes with a lot of pitfalls because it It started 20 years ago. So Containers, it doesn't know cube. It doesn't know there's a lot of things it doesn't know and It has been architecture with this plugin mechanism with this which is Super nice super awesome, but when you have 1 billion plugins and How you manage updates it's like it it comes with A lot of problems and on the open shift side We do We did ship with a Jenkins instance In 3 we still do in in opportunity for But those are kind of really hard to maintain and administer mainly because depending on depending on What's your use of your cluster and what teams are there? You might need or once a different Jenkins in sleeper each team because each team has different needs each team might Want to build and need this plugin the other one the other plugin The different version xx also it becomes like a huge hard thing to maintain and This is where new alternatives come from And that that are real like that are cloud native and and one is Again, which is the one I work on Oh, what a coincidence So so Scott let me just let me let me divert a bit from that So certainly Jenkins it's been around for a long time And and I think Vincent makes a great point that that it precedes in many ways Some things that are really sort of central to the world of CICD at this point, but you know, you're you get feedback from our Rail customer base or is there any other tooling that's in this picture that they are maybe Trying to cobble together What they want to do and and and that they're maybe struggling with I mean, I think that Jenkins is kind of the Widely used tool for a lot of stuff, but because it's used for a lot of things as Vincent pointed out it it gets really gnarly Because to do everything well you can do or to do everything you can do no single thing really well um And there's a been a bunch of other kind of SaaS offerings that people can use and um But yeah, I think Jenkins is kind of the the beast everyone knows Right, right. Well, so that that brings us to what is open shift bringing to this to this endeavor, right? What is it that open shift does and allows? Um, you know some an organization to do When they have this objective of building CICD pipelines that you know Achieve those objectives we talked about earlier and that you know in some way can align to their particular approach to to building code and and you know to their application lifecycle, so mayor, um Tell me a little bit about You know what open shift brings to this picture that maybe has missing or that is especially effective right, so First of all, I'd like to point out that I Openly and publicly like Jenkins. I think it's a very good tool It does it does what it's supposed to do which is to run things. You just need to tell it how and telling it how is the difficult part because Managing Jenkins, whether it is the Jenkins instance itself, whether it is the underlying infrastructure for the nodes for the For the main for the main node master node Whether it is the jobs on top of that, which is probably the most difficult part because Even when you when you think of scale it gets even worse because then you end up with the Jenkins instance with 800 job definitions on it All composed differently. We use Jenkins job builder So it's easier for us to compose different jobs of different types and and to even allow our users to to to take advantage of that but eventually I think the the common Characteristic and and what we've been going for or what what vincent's team have been going for and and we received as customers is the concept of of building small small boxes and stacking them together in every way that we want so open shift pipelines they come They come in in a very It's a very generic tool Every pipeline that you can imagine eventually is a pipeline and a pipeline is divided into tasks And each task may have one step or more and that's and that's the the concept and when you are able to build Different pipelines, but have the steps reusable It brings a huge advantage and And it's not even something I mean with Jenkins specifically you would need to actually define each and every job and and Find your way to reuse components with yaml magic and things of that sort, which is never fun We ended up one time with a 5000 line file of Jenkins job builder definitions for For a single project for a single product. We are running and our team currently runs over 50 So imagine what would have happened if we kept going that route But I think what open shift brings to the table is is the elasticity That's the most important feature that it brings and that is the reason we migrated all our cd processes from Jenkins to Open shift pipelines because of the elasticity no matter how many we used to fight with Jenkins. We used to tell tenants not to promote to Frequently not really in those words, right? We told them. Yeah, never mind. We were encountering overload Constantly with too many deployments happening at the same time and with open shift It just doesn't happen because the cluster can be defined without the scaling and you deploy as many resources as you want Also need to clean up because these are custom resources and at cd at cd So cleanup is important But essentially you define things once you can reuse them from different places And you just build your pipelines any way you need and whenever someone wants to run them they just go into the namespace and Hit run because it's embedded in the in the console which Super nice So everything into a single place, which is also the place running your services That's double nice All right, what does sound like go ahead Yeah, I was gonna say I think just to add to that One of the goal of open shift pipeline, which is based on the upstream project data and was to Also kind of speak the same language or be more Close to what you use to deploy because In the end right at open shift pipeline or tecton is just an extension on top of q We are using crd's etc. So you're you're gonna be able to use Everything single tool that we that you use to manage your clusters, etc. You can use them also with Tecton and that's that's kind of was one of the the goal and yeah as mar said like one of the other goal was Composability and reusability be able to easily define Task with multiple steps that things that are reusable so that you define them once You can even share them somewhere and we do have community sharing place somewhere for command used task and and and from there you you just like get your pipeline and You orchestrate the unit task that you wanted I think you hit the goal on spot with Customers reusing the same systems. They already used to deploy their services. We did exactly the same thing our team Which is a customer of open shift pipelines We have this repo that we use to define and deploy all the services that we run Into different open shift clusters and and open shift pipelines just came naturally into that picture We reuse the same system of course and it was One of the one of the best migrations that we did from Jenkins to open shift within the same system It was spot on with the goal and it hit right there All right. Well, so it sounds like this is actually a path to being able to do things For lack of a better word much more easily You know with fewer pitfalls Less complexity and of course complexity brings in the possibility of things going wrong I'm particularly intrigued by the idea of being able to share out particular you know Ways of doing the you know sort of the composition and other sorts of things because that also Starts to build kind of a community of practice in which there is a way that you do things It's not that that's the only way But there is a common way that can be shared and and it becomes in a sense tribal knowledge, right? so Talking about the tribe a little bit Can we talk a little bit about the roles of the different people who are involved in building these pipelines? Okay, so first of all, let's talk about the ops role in In in in sort of building out CICD pipelines and who wants to take that one? There you go I am the No, see I was going to put scott on the That one, but you know what? No, I want to hear from you or All right, so so I think first of all the the definition of roles may be different in every organization And and eventually we need to to formulate the relationship between the different roles in an organization in order to decide who does what a sort of I'll use a word my team uses a lot a contract between each layer Of people supplying it So in our in our team, for example, we are responsible for The cd process as a whole Are the services that we run the development teams they come with their source code? And we have a sort of a contract that they put their deployables in their in their code repo And we are responsible for the pipelines themselves And and they are receiving that as a service So in this example the ops team is responsible for not only supplying the pipelines But also for building designing maintaining them Um while the developers in this equation are responsible In our case at least to define their pipelines in a declarative way We have this system. I started talking about I'll say its name up interface contract reconciled go look at our GitHub organization. It's awesome So so this system allows the themes that that we service to define in a declarative way What they want deployed where according to the branching strategies we mentioned earlier So they're going to say something like this is my repo and in this path you'll find my deployable I wanted uh, whenever there is a merge to main I want to deploy to stage and in this commit I want to deploy to production And that will be their role behind the scenes automatically Our systems or be it people depending on the level of automation each organization is that will provision these pipelines And and based on the same declarative manifest will also be Will also be automatically triggering pipelines based on different conditions For example, if the main branch is pointed at stage environment and a commit changes behind the main branch We'd want it redeployed. So the ops team in this case will also be responsible for making sure that Artifacts are being delivered into environments according to the contract once again So the collaboration in this is essentially through a contract We decide upfront who does but who's responsible for what and who stores artifacts and Based on that we define everything else I like the term contract because a contract implies a negotiation right and and there there has to be some degree of negotiation Between the outside no negotiation No, no negotiation the contract is the well There's no negotiation after the contract but there has to be some degree of agreement about what that contract looks like, right? um, so Vincent give me a little bit from the developer perspective on this and and how How the developer role participates in this and thinks about what the cicd pipeline looks like and how it works Well, uh, yeah, I as as Moritz said like In in depending on the the roles are different, but I would think like for me the The role of developer here are to tailor like if we talk about in specific technical pipelines like real machine pipelines in the notion of tasks I think developers role is to tailor the tasks that they might use the one that are important for them like the I'm building the the code testing the code etc to their needs with of course discussion negotiation contract with the operational role, but like it it becomes your pipeline becomes a set of an element that are either dev responsibility or op-response responsibility the pipeline itself might be on the ops responsibility, but you usually you have Like you will have your set of tasks to maintain because this is kind of closer to what you're doing um and yeah, but yeah, I mean it really depends on and and and it's also like We're talking about for example, open shift pipeline specifically, but you can have higher level constructs, which would abstract this contract and and and I know there's like work towards those kind of higher level construct upstream for example where we're trying to think about more like the dev wants to provide this in this set of tasks that are used for them to build like a go build and a go test task and and on the opposite side, we want to be able to easily say Ingest inject Inject these tasks into the pipeline and the pipeline will also build an image from this will also inject some other Steps that are tasks that are coming from someone else the operation for example to secure our scan the image so Yeah, I think I'm answering I mean over yeah Well, I know I followed along and and I think this is what what One of the things that comes across here is that it has to be a very collaborative process in which it's it's not something that can simply be Installed and now you have this thing that does the thing. It's there's a long long series of Again negotiations. I think discussion about well, okay So here is how we do things now and the thing about it is is that how we do things now Is not always the thing that you want to continue I mean sometimes you are undertaking this for the very reason that you do not want to do things the way you do them Now you want to move to a new and better way But at the same time it's not like you want to give up the way you do everything And so that's from a developer's perspective or from the ops perspective It's let's take the things that work for us, but then maybe move in some new directions with cicd But also anticipate how do we really actually push our apps out as opposed to what we imagine You know, we're not, you know, we're an organization that might not imagine itself as being an amazon You know, we're a netflix or whomever that you know is pushing out 10 000 code changes a day Uh Yeah, that implies a somewhat different cicd pipeline It implies a different relationship between the developers and the ops and and many other things right So let me ask um You know, if we just get a little more specific here You know, what are the administrative tasks? You know, what is what is day two?  Understanding that it's going to vary from from work to work My work? Yeah, well, sometimes I just want people to jump on in, you know, Scott you feel free to feel free to clarify My my open shift knowledge is known to be vast and deep in all things All right, so I'll try to just to tell a bit from our experience what what we had to do um So I think some of the day two operations as always Day one is usually to get started and and get things working and day two is usually the improve part or iterate part The day one operations on on an open shift, for example, they want provision a cluster. They do upgrade the cluster So I think the day two operations will be partially to to modify and improve the pipelines as as new needs arise and As bugs are discovered and there are bugs everywhere including in your pipelines and in ours and we haven't found all of them and we never will But the day two operations are more in the in the direction of of maintaining and I think for maintaining and keeping day two operations Even even different ones to keep them sane and to keep them sustainable So it will be very important to focus on the day one operations how you set up those pipelines How you really collaborate between teams just by storing the right resources in the right repository By reusing actual resources between different namespaces according to your deployment systems and and how you manage your your code Manifests our code as well. So how you deploy the same manifest into different namespaces if you're servicing More than a single team. You'd probably want to to do some compartmenting Do some compartmenting. Yeah, and and create separate namespaces for pipelines So you'd need to be able to keep maintaining those pipelines and you'll need to be able to scale everyone needs to think of scaling in in any sort of Magnitude, so how are you going to on board new teams into your process that you've created in in your in your day one operations? How are you going to handle an issue with your pipelines? by by By making a single change and having it applied to all your different environments and to all the different pipelines that are reusing this Small package So I think a lot of the day two operations actually depend on how you plan to deploy your resources And that's again, that's a that's a perspective of how you deploy your services So open chest pipelines really just doesn't bring anything new into this concept You've every organization was already thinking of these things. How do I? Deploy and how do I fix my code faster? and and those pipelines they are just code and And I think this is one of the most important things. Yeah All right. Well, yeah, so, you know, it's good Ordinarily we hear a lot of talk about day two and so on but I think the Maybe the moral of the story that I'm getting from you today is that you need to get your day one right? Because that's where you actually set up the the things that you're hoping will Will provide all these benefits down the road As far as you can predict right because it's easy to say let's plan and let's plan thoroughly and let's not be surprised But honestly what you don't know what you don't know and when you find out That it's different from what you thought you'd know It's it's already too late and I think that in that essence It's important to try to plan as much as you can but also Be aware of the fact that there may be changes along the way and iterations are good We always say that iterations are good Don't deliver everything at once deliver in pieces that already return some of your investment and Right Well, you know, so that's that's the thing that was kind of striking me as a bit of a paradox there is that on the one hand What we are trying to do with CICD and so much of the, you know, how things are being approached in this space now Is really around trying to be very agile But at the same time if you're trying to get all of this right at the same time that's starting to not sound so agile And so that in my mind Raises raises this paradoxical question is How do you evolve your CICD pipelines over time because you want to make those good decisions up front Maybe you don't make every decision at the outset But you're trying to set things up in a way that works organizationally works for the kinds of applications you have and so on But inevitably you are going to have to evolve these. What does that look like? I think Mark said something very interesting on on the on the fact that How when you have multiple teams or even multiple users on your on your cluster that are doing Uh Pipelines and Sharing things how you keep them up to date with whatever change you Provide to the pipeline or to the tasks themselves And and this is where I think when you serve this is kind of for me the day to work Of day one would be I discovered the thing Oh, this is nice. This is using cube semantics, etc I can create something and it's going to be available. So but then the data will be How I Keep this available for everybody. Where is my source of truth? And and from there what what should I use to update my my pipeline? It's it's kind of easy there It's like how do I build containers by building containers in containers? This is a bit similar like you can definitely have pipelines that manage Actually the delivery of your pipelines in your clusters and And you have the full done This is kind of what we're trying to do for your platform where we build Tecton pipeline with With tecton pipeline, but we're doing the same downstream building open chip pipeline with open chip pipeline and and trying to maintain in our top footing Cluster our own all of our Pipeline tasks reusable tasks, right? They're all defined somewhere in the source of truth, which is one of the huge reports here and we do have pipeline itself updating itself validating itself and keeping Any sort of usage of this in the cluster, but this is kind of there's there's going to be As much approaches as there is teams almost like i'm sure i'm sure what we do different from what our team does And it's going to be different from elsewhere. There's going to be emerging patterns there, but yeah Well, actually emerging patterns gets me into one of uh one of the sort of the last questions in my mind and that is is You know Where is the technology in support of cicd going? You know in in sort of that next step the next phase What are what are some of the things that you see Happening in this space and that might be might be changing. Let's say over the next year or so um well so I think every Everything is is happening on uh containers everything like every single cicd system right now As containers as its core or some sort of View of containers. The other action is like you can see them as containers because they are using the actual distribution format even though they're running vm behind the scene But so I think At least i'm going to speak as the leader of tecton is I wish Something like tecton would become kind of a standard of reusability and By standard I really mean the actual Smallest unit in tecton, which is the task Because I mean there's going to be Lots of different ways to do things but when you do want to do a go build it's going to always be the same So if you have the image And a set of parameters that you can give then your Your actual tasks never going to change If you are Right out if you're Amazon if you're a small company it's always going to be the same um So I would hope that some of This would kind of become a standard and then Any abstraction that builds on top would kind of speak the tecton language so that then you just you can switch from an absorption to another or at least you don't need to buy into some something specific to to Like if I don't know if github action and github builds I don't know the name and pipeline as code from open shift or something else is if they are all talking Tecton then it's kind of a win because you don't need to Only use github action for on github or github on github etc. You just need to you can choose whatever fits your team or what you think is the important part for your team and then you You rely on whatever is able to provide you the understanding like The same as what happens with container images with one layer on top on css tecton modules, okay um Yeah So uh mayor, uh, we're uh any last thoughts on sort of that question of where the future is Is headed Depends on who you ask if you ask the ops team. I'm asking you Yeah, yeah, of course, but this is a two perspective conversation. If you ask ops people it goes into being more uh More abstract Really and if you ask deaf people, it's going away. They don't want to be aware of of cICD They want things to work Like we don't want clusters. We want abstract concept and we want our service running It doesn't matter what's underneath. So I think I agree with Vincent. Everything is going towards abstractions And the less you know the the less you know And it still works and as long as everything works the less you know is better In being from an ops background. I also want things to just work All right, well, thank you gentlemen for uh for joining us today, uh, this has been incredibly Incredibly informative about the world of cICD those four letters get used so so so much and And yet I think that sometimes there's not a lot of clarity about what what's under the hood and what this really involves and entails Um, so anyway, thank you again It is that time for us to talk about sweet sweet internet points And again, here's where they we're at in the leaderboard nir and dev is narrowly ahead narrowly ahead and so we will uh check back in in You know, when we have our next show and we'll see how that looks but again, please Like please share Please tell friends about it when you join. Please ask us questions Let us know if there's anything that uh that you would like for us to cover in future sessions. So, uh again, thank you for attending Thank you


What about food sources of BPA, a plastics chemical used for lining metal cans and in polycarbonate as opposed to PVC plastics?  Food is a major exposure source, but there weren't any studies reporting BPA in U.S. fresh can and packaged foods in the scientific literature until now.  The relationship between urine BPA level and declining male sexual function.  This finding may have important public health implications given the widespread human exposure to BPA, but from where in our diet, in particular. They measured BPA levels in over 100 fresh and canned foods, foods sold in plastic packaging and in cat and dog foods in both cans in plastic packaging. Nearly all the canned foods were contaminated, from green beans to sardines, tuna and VA to Chef Boyardee. There was only one fresh, non-canned food that had detectable levels, so if you don't buy canned foods or stick to BPA free canned foods, the only food left to worry about appears to be sliced turkey.


Here at AFER, we often talk about how the United States Supreme Court has ruled 14 times that marriage is a fundamental right. But what are those 14 cases going all the way back to the 1880s? Let's take a closer look at exactly what they were about and how they bolster the case to overturn Prop 8. At the American Foundation for Equal Rights, I'm Matt Baume, and welcome to a special episode of Marriage News Watch. The Supreme Court's ruled on marriage over a dozen times, and those cases touched on a wide range of issues, from parenting, to divorce, to reproduction and housing. But if they hear our case, it could be the first time that the court rules on the freedom to marry for gay and lesbian Americans. So let's go back to 1888 with Maynard v. Hill. That case clarified the rules for divorce, and the court wrote that marriage is the most important relation in life, without which there would be neither civilization nor progress. Those words are 125 years old, but they illustrate a crucial point. Marriage isn't just some run-of-the-mill interest, it's a fundamental freedom. It's special. And the government can't restrict it, unless there's a really good reason. And that really good reason, as we saw in the Prop 8 case, simply doesn't exist. The next major marriage case was Maynard v. Nebraska in 1923. That case involved parental rights, and the court wrote that the right to marry, establish a home, and bring up children is a central part of the due process clause of the Constitution. In other words, the Constitution protects marriage. That was followed by four cases involving reproductive rights, Skinner v. Oklahoma, 1942, Griswold v. Connecticut, 1965, Kerry v. Population Services International in 1977, and later Planned Parenthood v. Casey in 1992. Those cases prompted the Supreme Court to write that marriage is one of the basic civil rights of man, and involves a right to privacy older than the Bill of Rights. The court added that among the decisions that an individual may make without unjustified government interference are personal decisions relating to marriage. Those four cases spanned 50 years, during which the court also heard loving v. Virginia. That's the big one, that in 1967 overturned racist anti-miscegenation laws. The court wrote in Loving, the freedom to marry has long been recognized as one of the vital personal rights essential to the orderly pursuit of happiness by free men. In the plaintiff in that case, Mildred Loving wrote, I believe all Americans, no matter their race, no matter their sex, no matter their sexual orientation, should have the same freedom to marry. I support the freedom to marry for all. That's what Loving v. Virginia and Loving each other are all about. Following the Loving case were seven separate cases that invoked the due process clause in recognizing the importance of marriage. First was Bodie v. Connecticut in 1971 involving divorce law. The court wrote, marriage involves interest of basic importance to our society and is a fundamental human relationship. That was followed by Cleveland Board of Education, V. La Fleur, which overturned discriminatory maternity laws in 1974. The court wrote, personal choice in matters of marriage and family life is one of the liberties protected by the due process clause of the 14th Amendment. Then came Morvey, city of East Cleveland in 1977, which overturned a law that limited the definition of family to only nuclear families. A year later, the court heard Zablaki v. Redhill, a challenge to laws that restricted remarriage. The court ruling was consistent with past decisions. The right to marry is one of fundamental importance for all individuals. We're in the home stretch now with Turner v. Safely, 1987, that case unanimously overturned a law that prevented prisoners from remarrying without permission from the warden. Again, the court wrote that the decision to marry is a fundamental right. And in a 1996 case involving parenting, known as MLB VSLJ, the court wrote, choices about marriage, family life, and the upbringing of children are among the associational rights this court has ranked as of basic importance in our society. Rights sheltered by the 14th Amendment against the state's unwarranted usurpation, disregard, and disrespect. And now we get to Lawrence v. Texas in 2003, a landmark decision that overturned some, but not all, discriminatory anti-gay laws. In that decision, the court wrote, our laws and tradition afford constitutional protection to personal decisions relating to marriage. Persons in a homosexual relationship may seek autonomy for these purposes just as heterosexual persons do. So why does all this matter? Because all of these cases track closely with the case against Proposition 8. The rulings against Prop 8 closely echo that long history of rulings by the Supreme Court. When the district court ruled in our favor in 2010, it was on the basis of due process and equal protection. In fact, the court cited Loving v. Virginia and Griswold v. Connecticut writing, the right to marry has been historically and remains the right to choose a spouse and with mutual consent join together and form a household. And when the Ninth Circuit upheld that ruling, the court wrote that Prop 8 violates the Equal Protection Clause of the US Constitution by excluding gay and lesbian couples from marriage. The court wrote Proposition 8 singles out same-sex couples for unequal treatment by taking away from them alone the right to marry, which is a distinct constitutional violation in that it subjects a minority group to the deprivation of an existing right without a legitimate reason. The rulings in our case are consistent with 125 years of rulings by the Supreme Court of the United States. And that's just one of the reasons we're confident we'll win. But we'll still need your help to do it. We have winning arguments, but bringing them to the Supreme Court requires a lot of resources. Visit AFER.org to find out how you can help add this case to the long list of cases that expanded the freedom to marry. At the American Foundation for Equal Rights, I'm Matt Baume. Thanks for watching.


Hi everyone, my name is Steph, this is Little Bookish Teacher and welcome or welcome back to my channel. Today is World Refugee Day and I am going to be sharing some picked books, five of them in fact, and two middle grade novels that deal with refugees or displaced persons. And these books would be a really great conversation starter in your classrooms with students around refugees, around compassion, and they're just really gorgeous beautiful books. The first book is an oldie but a goodie and that is Refugees by David Miller. First up I just have to say that this is one of those really beautiful collage books where all the illustrations look 3D. It's just a really stunning book visually but this is the story of two wild ducks who are displaced from their home, the swamp, when it is drained and they need to go in search of a new place to live and as they are trying to find a new place to live they find themselves in danger. There's a lot of violence and they are quite often rejected and so it is about how they cope with that and how they eventually find a new home. Obviously we can draw a lot of parallels to the experiences of people who need to escape their home because their lives are in danger and they come to a place where people don't understand them and don't understand their cultures because everything is different and this can be a really nice gentle way to open up conversation with kids around that. This is a really great starting point and a really great book to use for comparison with other stories as well. Another one which I don't have here with me, I think it's at school, is Room on a Rock by Kate and Joel Temple. This is a really unique picture book in that it can be told front to back and back to front and each time you read it it tells a different story. So this is about two seals who are huddling on a rock but the other seals around them are telling them that they're not welcome here, there's no more room on this rock and that they can't stay here. They don't accept them and they don't let them stay and so this sends these two seals into a dangerous situation. You read the book through the first time as you would a regular book and then when you get to the back of the book it points out that every story has two sides and it invites you as the reader to read the book back to front and as you read the book back to front the story is very very different. It is very cleverly written in that way because the words as you read them in one direction make you feel a really certain way. The first time I read this book I was absolutely gutted and devastated by the end by the time I got to the last page and so when you read it back to front I actually got really teary the first time because in reverse the message is just beautiful and there was one year where as a whole school we actually read the book from Foundation to Year 6 and we were using it for a reading response where we responded to the book at the end of the first reading and then when the kids got to experience the book in the other direction they then had to compare how their feelings had changed on the book and it is just very very powerful. It is very much about sharing and compassion but you can absolutely draw parallels with the experiences of refugees and displaced persons around the world who all want to hear that they are accepted and they are welcome but sometimes they don't hear that and unpacking that feeling with kids can be really powerful. Another one I'm kind of annoyed that I think is still at school because I love to share this book is Suri's Wall by Lucia Stella. This is just another gorgeous but also heartbreaking story. Suri and a group of children live high up on a mountain behind a wall and their village is down below but they are living here and they have one guard and they don't really know what is beyond the wall. They've never really lived anywhere else and Suri is a bit of an outcast within the group of kids. She's a little bit taller a little bit different and she has this incredible imagination and as she gets older and she gets taller suddenly she can see beyond the top of the wall while the other kids still can't and so they become curious and they start to ask her what she sees. Using her imagination she tells them these beautiful tales and it gives these kids so much hope and then of course the heartbreaking thing is by the end of the book what we know is that Suri is trying to give everyone hope because the sounds that are coming from beyond the wall are the sounds of violence and fighting and it's just a really powerful book and there are so many great conversations that you can have about it about why wouldn't she tell the truth to the to the younger kids and how powerful is the power of hope. So again a very poignant very powerful book. There is My Two Blankets by Irina Cobbold and illustrated by Freya Blackwood. This gorgeous book is about Cartwheel who has to leave her home with her aunt and they find themselves in a strange place where they have to learn a new language and they have to learn how to live in a new place and they have to everything is new and everything is confronting and all that Cartwheel has of her old life is her aunt and this blanket that she's brought with her but as she slowly begins to make a friend and as she slowly begins to learn the language and she begins to become accustomed to where she is now she crafts this new blanket that's the My Two Blankets and it is a beautiful story of hope and persistence and courage and remembering that no matter where you are you are still you you are ballot and you are important. It's absolutely gorgeous and the thing that I love about this book so this one is just told in English but there are two other versions of this book one that is told in English and Dari and one that is told in Arabic and English and the fact that there are multiple copies of the same book available in different languages I love that and I wish we saw more of it and then my final picture book is another very well known picture book and this one is The Arrival by Sean Tan and while this one is not specifically about refugees it could be about immigrants, it could be about refugees, it could be about displaced persons, it is about coming to a new place and feeling like everything around you is alien and weird and totally foreign and you have to figure out how and where you fit into this place. This is a wordless picture book the illustrations in here are incredible and in many places it's almost told in kind of like a graphic novel style but really it's more about moments. It is just one of the most amazing picture books and there is so much to unpack in here and if you haven't seen it I highly recommend you check it out. All of Sean Tan's works are amazing but this one is just incredible for the journey that you are taken on as we follow our character who is in a new place and it's strange and uncomfortable and foreign it's a gorgeous book. It's really great for visual literacy for unpacking this with older readers and for highlighting the fact that sometimes you don't need words to tell a story sometimes the visual is enough and then I have two middle grade recommendations. The first is The Year the Maps Changed by Danielle Binks. This is a story that is set in 1999 here in Victoria in a place called Sorrento. It is the story of Fred who lives with her adoptive father and her pop. Her mother passed away when she was quite young and so she's lived her whole life with these two men and suddenly everything is changing because Luca her her adoptive father has a new girlfriend and she has a son and they are suddenly bringing these two families together and she is not quite sure how to deal with this. Alongside that the world sort of the world at large is reeling from the Kosovo war and she's learning about it at school particularly because a group of Kosova Albanian refugees are being housed at a government facility not far from where she lives in Sorrento and suddenly this becomes personal for her and for members of her community. It is just a really poignant really beautifully written middle grade novel that looks at the impact of war the way that international governments deal with refugees how we as a community can have the opportunity to make things better for people for demonstrating compassion and care. It's just it's a gorgeous book and then another one is The Bone Sparrow by Zana Freiland which I actually haven't read for years I probably need to go back to it because it was just one of those books that I walked away from and I just had so many big feelings about it. It is the story of Sabai who is a 10 year old boy who has lived his entire life in a detention centre. We get to meet his family, we get to meet his friends, we get to meet other members of his community who are living in the detention centre but he makes a connection with a girl who lives beyond the fence. They have this connection through a book that belonged to this girl's mother and it is a beautiful story of bravery, of friendship, of hope, in the face of adversity and there are so many things that go on in this story but they're all told from the perspective of this 10 year old who doesn't always understand everything but does see and hear a lot and so this is one definitely to read and to be aware of the content of it and how it might impact the readers in your school but it's just a gorgeous story. I will leave links to all of these books down below if you're interested in checking them out or finding out more information about them. In the comments I would love to know if you have any book recommendations for World Refugee Day. If you want to let me know that you're here but you don't want to leave a comment feel free to leave a seal emoji down below otherwise I hope that wherever you are in the world you're staying safe and healthy and I will see you in my next video. Thanks so much for watching, bye everyone.


When she has pains and spasms, it's difficult because every pothole or little ripple in the road that you hit just reverberates through her body and causes pain. A lot of times you're limited to what you can do because of the pain. A lot of things I couldn't do with the pain was really cut my grass and do things to my house like I wanted to. Arthur Moten couldn't work around the house. Mary Boyd was restricted in her daily activities. For Carolyn Jones, a simple car ride was unbearable. Cancer pain has many causes and can affect people in different ways. But these patients were able to have their pain controlled with effective pain management. The bottom line is that patients don't need to suffer with pain. If it can't be controlled with simple oral medications, we have a whole host of other medicines and procedures and approaches that can make just about every patient comfortable.  Pain management requires a team of doctors, nurses, pharmacists, and social workers all working together to keep a patient's pain under control. But the most important member of this pain control team is you, the patient. Hi. Dr. Grussman. Pain is nothing that the doctor can feel, it's nothing that the doctor can measure. I had this pain behind my right rib cage and in my shoulder. The patient can feel it, the patient knows how much discomfort they have, and if they don't communicate that to the person who's taking care of them, the person who's taking care of them is not going to be able to do the kind of job they should. It's been almost a week since I've seen you last. Why don't you catch me up-to-date and tell me how you've been doing for the last week? Well actually the pain is much improved. The first step in pain control is communicating how much pain you are experiencing. The best way to do this is just by talking with your doctor or nurse. We want to get lots of information about how the pain is affecting almost every aspect of their life, and then from there try to figure out what it is we can suggest or do or have the patient do that would try to make the pain better, that it's more tolerable, that they can get through the day a little bit easier. Using the scale that you've used before with no pain here, the worst pain imaginable here, where would you put it right now? At this moment I would go all the way over to no pain. You may be asked to describe your pain using a scale from 0 to 10. This tells your doctor or nurse how bad your pain is, and it provides a baseline to measure the effectiveness of your treatment plan.  But that tells the health care provider something very important. If we give some medicine, does it slide down to a 4, which is not much better, or does it slide down to a 0 or a 1, and how long does it stay there? If we know how long it stays there or how far down the pain rating goes, we can figure out how we should adjust the medicines a little bit in order to be able to do even a better job. The pain medicine would have taken 260 milligrams three times a day. Another important way to communicate how you are feeling is to keep a diary of your pain. This helps your doctor or nurse determine how effectively your pain is being controlled. I'm going to be putting together stuff for starting your IV. In some cases, treating the cause of the pain with chemotherapy, surgery, and radiation can help relieve the pain. Arthur Moten found that after a week of chemotherapy, his cancer pain improved. I notice around, but the fourth to fifth day I start feeling a lot of relief. I start cutting my own grass, I start cleaning my car, and I start doing a lot of the things I wasn't able to do at first. But in most cases, treating the cancer alone does not relieve the pain, so you'll have to treat the pain as well. The most common way in which pain can be successfully controlled is with the use of pain medications, and for most patients, they only need to use oral medications to control their pain. Pain control is a process of finding the right drug or combination of drugs that's right for you. Your pain control team will work with you to keep your level of pain as low as possible at all times. There are really three different groups of medications that can be used. One group of medications is used for what we would consider mild pain. They're medications that patients may be familiar with being able to actually get just in the pharmacy without a prescription, things such as Tylenol and Motrin. Once that no longer works, there is a progression to medications that we use for more severe pain, and these are medications like morphine or what they're also called opiates. There's a third group of medications as well. A good example is drugs that are used to treat epilepsy can also be very effective in treating certain types of cancer pain. Many patients worry about taking certain types of pain medicines, like morphine, because they're concerned about becoming addicted. But when used to treat cancer pain, addiction is very rare. There's been research done that shows that only about one in 10,000 patients will ever become addicted as a result of taking pain medications for pain control, and that's the key. We always try to remind our patients to ask themselves, if you didn't have pain, would you be taking these pain medicines? And universally, their reply is always no, of course not. In fact, sometimes your pain is enough, you needn't think about no addiction, because you're only looking for that pain, the relief from that particular thing that you're taking it for. Once your pain has been brought under control, it's important that you stay on a regular schedule of taking the medications your doctor has prescribed. Patients who are put on scheduled medications really maintain better pain control. Once they go off of their schedule and they don't take their medications on a scheduled basis, then their pain comes back and it takes much more medication to eventually get their pain back under control again. There may be times when you are more active and need a little extra help. Your doctor will prescribe additional doses of medication to help you enjoy the things you like to do that may cause you pain. The things that I would just do moderately, I could do a whole lot better, a whole lot longer. And so I was told not to overdo it. And if I found myself overdoing, I would take a little pain pill or a little morphine, a little Percocet. Not that much, but just to keep the pain under control. Hi. Chief of the Catholicities. Yes, Mrs. Pace. How are you today? I have a prescription here for you for oxycodone tablets. Unfortunately, side effects often accompany the use of some medications used for treating cancer pain. And have you taken this medication before? Yes, I have. And did you have problems with it? Yes, I did. Okay, why don't you wait for a few minutes and we'll sit down and talk about it. But these side effects can almost always be treated with either other medications or changes in diet. You mentioned that you had a problem when you took the oxycodone before. Tell me what the problem was. When I took it, I got really sick in my stomach. What we do oftentimes is give patients other medications to prevent them from being sick to their stomach. Your pharmacist can assist you by answering any questions you might have about a particular medication or its side effects. Most pain medications are taken as a pill or liquid by mouth. But sometimes it may be necessary to find other means in which to deliver the pain medication. Rectal suppositories can be used for patients who can't swallow tablets. Then we can move on up to things like giving some of the pain medications into a vein or IV as it's commonly called. It can also be injected into a muscle or simply just by sliding a needle in under the skin and giving it just underneath the skin. All of these methods are also very effective in managing cancer pain. One very safe and effective way of managing pain is with a patient-controlled analgesia or PCA pump. This pump can be used to give medication into a vein, under the skin, or into the spine. When patients feel pain, they simply press a button to receive a dose of medicine. This allows a patient to have greater control over their pain management, either in the hospital or at home. Controlling cancer pain often goes beyond the use of medications and treatments. You have to learn all over again how to live because you're not able to get around, you're not able to do the things you used to do before. So you have to learn how to live all over again. While drugs can help reduce physical pain, you still need to address the pain you may be feeling emotionally. Your outlook on life can affect the way you feel both mentally and physically. The social work role in the pain control for patients and for families is that of the person who can listen to their feelings, to listen to what it's like to be in pain for an extended period of time. There are a variety of what we call non-pharmacologic, non-medication treatments for pain. Perhaps the most common is relaxation. When I walk in a room, I'm the person who comes in with no needles, no medicine, and actually no magic either. I come to listen to people from my heart to their heart to understand where their feelings come from. Sometimes, simply enjoying an activity alone or with a friend or spouse can help you focus your attention away from your pain and put you more at ease. One of the things I think that has also helped her on pain is family and especially the grandchildren. When they come, she can seem to stand a lot more pain. So when family comes or people, some of our friends come to visit, that's really been very beneficial. You, the patient, have an important role in controlling your pain. Communicating your feelings openly with your medical team, staying on a schedule of pain treatment, and letting your doctor or nurse know when something isn't working are key to keeping your pain under control. If you're taking a medicine and it's not working for you, you have to speak up because the doctor can't help you if you don't help yourself.  You have to work that out and you have to sit down and be able to talk to your doctor about that. Trying to see next, you'll go right, you've got first preference. Whatever the cause of your pain, whether from cancer or its treatment, you can rest assured that pain does not have to take control of your life. No matter the severity, it can almost always be treated effectively. There is really no reason for patients to suffer with pain when they've got their tumor. Pain doesn't do anything positive for a patient who's trying to enjoy their family and their activities at the same time. It can be controlled. You just have to be patient and try different things and see what helps.


Let me say a special hello to an old friend and trusted advisor, the co-chairman of the Republican National Committee, Betty Hydeman. Betty will be retiring, Betty will be retiring from the RNC, and I just want to thank her for a job well done, especially for her efforts on behalf of women. And all of you here today, welcome to the White House Complex. I always feel a little funny saying that about the White House over there in this great big granite monster over here and calling it part of the White House. It ought to be the other way around. It's a pleasure to see all of you, the representatives of America's more than 3 million women entrepreneurs. We're meeting at a time of unparalleled optimism in our country, optimism about the future, optimism about the direction in which our nation is going, and optimism among all Americans about our own lives. I'm going to talk in a few minutes about our agenda for the next few years, but let me say here that if I have one message for you today, it's this, that America has a great future ahead. We have a future of more opportunity, more growth, we have a future of a stronger America and a freer world, and that's what we're building toward, and this is what we can achieve. The last six years have been only the beginning. We're just starting to climb to the mountaintop where we can look out over the promise of our future. Now to be easy to stand up here and take credit for starting America on that path for the low inflation and the low interest rates and the creation of more new jobs in the last four years than Europe and Japan combined, but as I've said many times, since our recovery began the credit belongs not just to an administration, it belongs to the American people. We trusted the American people and they did the rest. I always have said mainly my philosophy about government has been for many years, just get out of the way of the people and they'll do the rest. I can't think of any group of Americans that deserves more credit than the group I see in this room, America's entrepreneurs, and in this case, entrepreneurs who happen to be women. You know better than most the importance of entrepreneurship in national life. Since our recovery began, Americans have created millions of new jobs. Yet entrepreneurs, men and women with businesses that are five years old or less and businesses that have 20 or fewer employees have created even more jobs than that. In fact, if you took away the jobs that entrepreneurship created during the years of our administration, we would have lost more than three million jobs. So whenever I get a letter from a young man or woman telling me that he or she has an idea for a service or a product wants to take a chance and yes, maybe win or lose but still take the chance and work hard and start a business. I just can't help saying to that young man or woman something I said in another context some time ago, go ahead, make my day. Thanks to you, we've come far since the days of skyrocketing inflation and economic stagnation when the once powerful American economy was the weakling of the industrial world. Yes, we're strong again, but our work isn't done far from it. We have an agenda for the next two years, an agenda for setting America on the path to even greater growth and greater opportunity for a generation yet to come. Getting federal spending under control is part of that agenda and that means giving the president what 43 governors in our nation have, a line item veto. It means a balanced budget amendment to the Constitution and it means that pulling a taxi increase out of the hat is not going to be this year's version of the Big Spender's escape trick. There's no way on God's good earth that I will agree to an unraveling of what we've done with tax reform. Tax rates have come down and they're going to stay down, but that's not all. We've taken giant steps toward making jobs grow faster by making exports grow faster. The dollar is down. We've been tough with unfair trading practices around the world and we're moving to a new round of trade talks, but we've got to do more and it must be a bipartisan effort. For 40 years, America has been the leader in building the open world economy on which our peace and prosperity are built. That's why today more than 10 million American jobs are tied to imports, exports, or both. And foreign trade involves one-fifth of our economy. That's compared to 12 percent when the Smoot-Hawley tariff shut down our international trade and sent us into the Great Depression. None of you here are old enough to remember that. Well, I don't believe that either Democrats or Republicans want to return to those depression days. It's time not for new protectionism, but for new cooperation for growing American exports in a growing world economy. Around the world, our agenda is one of peace and freedom. We cannot let recent events distract us from the cause of those brave fighters for freedom around the world, unless you just did make my day. Everything that's happened makes those causes any less just or vital to our country and all that it stands for. And as we work for freedom, we must also work for peace. Some have been kind enough to say that Mr. Gorbachev and I made more progress toward eliminating nuclear ballistic missiles in two days in Iceland than our negotiators made in two years in Geneva. Well, that's progress we intend to build on. And yes, we do dream of the day when we can have a world free from nuclear terror. And nothing is more important in building toward that world and our strategic defense against ballistic missiles. Some have said we ought to scrap it. Well, I say strategic defense is our insurance policy for peace. We're going to continue research and development on our strategic defense initiative. But let me, if I could, turn for a moment to the revelations of the past week and to my announcement yesterday. As I said yesterday, much in this case is hard to understand. And all Americans are entitled to have their questions answered. You know I'm talking about Iran. That's why I'm determined to get to the bottom of this matter and to get all the facts out. Let me review for you what we've done. First, we went immediately before the public when we uncovered the kind of activity in question. And this included the Attorney General's preliminary report. Now, with my full support and encouragement, the Attorney General is asking the court to appoint an independent counsel, we used to call them prosecutors, so that any possible wrongdoing will be revealed and prosecuted. Also unprecedented has been our cooperation with Congress. We've cooperated fully with congressional inquiries. And we'll continue to cooperate. And I've endorsed the idea of consolidating congressional investigations so that Congress can pursue its work even more effectively. I've also appointed a special review board to investigate the activities of the National Security Council staff. The men on this board have distinguished Americans of absolute integrity and have had experience in every area of the making of our foreign policy. I intend to make their recommendations and conclusions available to Congress and the public. Finally, as I announced yesterday, I've asked Frank Carlucci to become the new assistant to the president for national security affairs. Mr. Carlucci is a former deputy secretary of defense, a former deputy director of the CIA, and a former ambassador. And he is among our most distinguished and experienced public servants. So in short, the machinery is in place to seek answers to the questions that are being asked, to fix what needs fixing, and to restore complete confidence to the conduct of our foreign policy. All of this we intend to do, and that's my pledge to you and to the American people. I'm saying this here because you as a group are so important to the future of our country and particularly to the growth that we all want for America's future. In America, since our recovery began, women have created one out of every four new businesses. In the past decade, the number of women-owned businesses in America has grown at an annual rate of more than 9 percent, while the growth rate in sales has been three times that of businesses owned by men. And today, more than three million businesses are owned by women, which is over a quarter of all the independent businesses in the country. And that number is growing two times as fast as the number of businesses men own. You know, when you think of all that women entrepreneurs have meant to our country since the recovery began, it just goes to show that when it comes to creating new jobs, new technologies and new businesses in America, a woman's work is never done. I know that some people dismiss all this and say that women have tended to stay in areas in which they traditionally had a role. Well, those who say that ought to take another look. Women-owned businesses are springing up fastest in fields where women are relative newcomers, fields like manufacturing, high-tech and finance. Many of you are examples of that. Fourteen years ago, Joyce Adie was an antique dealer in Georgia. Today, she's no longer selling antiques. Her company, Habersham Plantation, manufactures reproductions of early American furniture and sells through more than 200 dealers throughout the country. Marjorie Ballez started only 10 years ago with a $7,000 investment she set up at Ballez Analytica Laboratory in Mountain View, California. Her company has won an international clientele for its research in chemical processing of integrated circuits and has set industry standards for out-of-pure water. The Ballez Laboratory is a leader in the high technology field. And there are many other leaders here. Laura Sloat, whose New York investment and research firm has grown to manage more than $150 million. In the traditionally male-dominated world of finance, nothing can stop Laura Sloat.  Yes, all of you are leaders. All of you are helping America to grow and remain the land of opportunity for all. You know, I spent a large part of my life in a profession where there was no question about the equal status of women and men. And that's why the way I believe it should be in all lines of work. You're helping to make that happen. You're also, by building your companies, helping to keep the doors of opportunity open wide for everyone in our country and helping to lead America into the future. I have to interrupt here and tell a little incident. It isn't a joke. It's an actual happening. And I enjoy telling it. As a matter of fact, I enjoy particularly telling it to audiences of men. But it has to do with an accident. A traffic accident. And the usual scene. A man stretched out in the pavement, unconscious. A woman was ministering over him. And the crowd had gathered around. And a man came and elbowed his way through the crowd, shoved the woman aside, and said, I have had lessons in first aid. And he started to minister. And she meekly stepped back and stood behind him while he went at putting into practice the things he'd learned in first aid. And then he came to one point. She tapped him on the shoulder and said, when you get to that part about calling the doctor, I'm right here. So if you're ever getting down, just think about that. So let me just close by saying, for all Americans, thank you for all that you're doing. Thank you, and God bless you. Mr. President, I'm Helen Beam. And I'm chairman of the Beam Porcelain Studios in Trenton, New Jersey, and Malvin, England. And I have a very happy chore to do. I'd like to present to you the Americans' new women entrepreneurs with their inner secrets of their success. Wonderful, fabulous ladies. And then this is of my life with a little lock, but it's written around that four-letter word, W-O-R-K. As a first generation of Italian immigrants and my husband, who was a farmer, the American dream. Now the one thing that these two books have in common is they both have the similar inscription. Right, Pat Harrison? And it says, to President Ronald Reagan, our favorite president of America. Well, thank you very much. Thank you all. And I shall read them. And I think you should know that up on the second floor of the White House, where the living quarters are, it is beautifully decorated with a great number of beam birds. Mr. President, I want to thank you for lending me those beautiful white swans that are going to Russia for the beam exhibit. Mr. President, I'm Linda Wagner, President of Warnico, which is a $600 million apparel conglomerate that owns some of the oldest brands in America, such as Hathaway and White Stag. And I wrote a foreword in this book, Riches, and we're real proud to present it to you today. Well, thank you very much. Thank you very much. And they will be read. Oh, thank you. Thank you very much. Thank you, President. Thank you.