From Hollywood. It's time now for Johnny dollar. Why is your stomach Johnny? Why rich food give any trouble? Who is this? Oh your buddy and your son. Oh, hi Angie glad you got my message. Yeah How about dinner tonight at Antoine's Johnny shrimp gumbo oysters rocker? Yeah, that sounds fine Only I've got to do some work for us I thought you're new on vacation. No little matter of fire insurance and the company's check for 16,000 Somebody trying to cheat him out of it, huh? You won't believe this, Angie Somebody turned it down Bob Bailey in the exciting adventures of a man with the action-packed expense account America's fabulous freelance insurance investigator is truly Johnny dollar Expense account submitted by special investigator Johnny dollar to providential fire and marines 787 Greenleaf Avenue Hartford, Connecticut The following is an account of expenses incurred during my investigation of the Royal Street matter Expense account item one one hundred three dollars and eighty-two cents transportation to New Orleans Item two four dollars and twenty cents cab from the airport to the Roosevelt Hotel After unpacking I put in the call to my old friend Angie or Saudi Nobody knows the French quarter or the people living there like Angie does The three months of the winter he stays in the swamp trapping muskrats the rest of the year He lives with his mother near the Cabildo Angie wasn't in but his mother said he she knew where to reach him and five minutes later He returned my call We arranged to meet for dinner then I phoned the agent who had sold the policy in question His name is Benford and naturally he was anxious to see me CD Benford's office is on the third floor of the hibernia bank building He's a stocky red-faced man probably in his late fifties Mr. Dollar come in thanks. Have yourself the chair. Hey, you fellas sure don't waste any time, do you? We try not to mr.  Oh, okay, CD. Yeah Now like I was saying you boys sure don't waste any time tall Oh, I didn't even call the home office till day before yesterday. I know When was the farm last week on Thursday night? What'd they tell you about it? Well, not very much. I figured I'd get all the information from you Well, it's a doozy First time I've ever run across a policy holder. It wasn't young for us to pay him yesterday for his loss today You know what I mean? Yeah Who is the insured mr. CD man named Dupas Henry Dupas took out a policy for 48,000 That's full coverage on his antique shop down on Royal Street. How long ago August just three months back I've been after him for maybe five six months to buy some protection But he kept saying didn't have the money another money and one day I dropped in see him about his car insurance and right off He told me to write a policy give him in full fire coverage on the shop Well, how do you arrange to pay it cash in full the day? I delivered the policy. He told you why he changed his mind. Yeah, not exactly That he mentioned something about times being better. I reckon they must have been why do you say that? Well, a few days later. He had the back part of his shop all painted and fixed up And that's the part that burned and he hired himself a girl to work in the office a real good look or two Well, what caused the fire, you know, I sure do antique kerosene lamp got knocked over accidental According to what Dupas told the fireman He was in the back of the shop with a customer shown in the lamp When it fell the fire started the two of them tried to put it out Reckon that's why they didn't call the fire department right off. Uh-huh and Did Dupont tell you the same thing to pop? He didn't tell me nothing Well, he reported the fire to you didn't he he did not and that's what's got miss a riled up I wouldn't know about it now if I hadn't dropped in there the other day was to par there when you stopped in yes Surrey and when I saw the place look the whole back of the store gutted out and the sluva's antiques destroyed I let him have both barrels. I'll tell you. Oh, what do you say to that? Yeah, nothing too much just acted like he wasn't interested in whether we paid for it or not Didn't even ask for a claim for It's funny sure is I thought maybe he was so upset over losing some of his valuable antiques He didn't know what it was doing. So after I checked with the fire department got a copy their report I typed up the claim for you figure the damage is 16,000, right? Mm-hmm. I knew how much he spent fixing up the back when I'd issued the policy I'd gotten an estimate on most of the antiques. So what happened when you gave him the claim he signed it He did not said to forget about the fire and when I kept after him He called me a busybody and told me get out of his shop and stay out What do you think CD you have any idea why he didn't report it or sign that claim if I had boy I wouldn't have sent for you. I left binford's office and walked over to canal Street The Sun had gone down and a cool breeze was coming in off the river Bringing with it the smell of coffee beans and fruit from the banana boats. I Cross canal and turned on to royal heading into the French Quarter When I reached Henry to pause and teak shop I stopped There are a lot of antique shops on Royal all of them look pretty much the same The buildings as old as the fine rosewood mahogany pieces they shelter There was nothing different about this one at least from the outside The fire had started and finished in the rear of the building. I Tried the front door, but it was locked. I didn't think anyone would be there that late, but I knocked anyway Who is it mr. Dupont who is it my name is dollar mr.  Well, we wouldn't if you tell us about the fire There's nothing special about that fire mr. Dollar. It was an accident Well, then why didn't you file a claim you're entitled to enough money to cover you? Mr. Binford explained that to me quite carefully if you haven't talked to a mr.  Well, none until you answer a few questions leave me alone, please I Noticed an alley next to the shop that ended where the rear door had been I started back along it not quite sure what I was looking for What I expected to find but I was sure of one thing to power was a frightened man It was too dark to see anything at the end of the alley, so I returned to the street Item three thirty dollars fifty cents phone call taxi and dinner for two at Antoine's oh, man Kind of nice ain't it Johnny. Hmm. Oh the way it never changes same waiter same chef same clientele. Yeah Like another cafe Royal and she no no thanks Well Johnny yeah, when you go ask me Ask you what don't kid me John. You had that old bloodhound look in your eyes since we sat down What's the question? Okay, Angie What do you know about a man named Henry Dupas? Dupas antique shop. That's right. Oh, not much seen him around some so yeah, where oh You know kind of places I like Johnny. Yeah, but I can't picture to par like them. Well, maybe he don't but Maybe add a little blonde. He's been carrying with him does one. Yeah, you know female girl Bleach tail. I know I know yeah, how old oh 24-5 Yeah, real nice. Oh cute like him real winter and spring. Yeah, you've seen him together often Well a few times so I'm about two weeks ago at Butch's place Hey, you know something I walked in there that night with a five and I walked out with 200 How about that great? You know who the blonde is? No, but I might be able to find out You want yeah, I want Left Angie and started back toward Royal Street on the way I ran up item for $1.85 cents for one flashlight and batteries The shades on to power shop would draw them, but I can tell there were lights on inside In the alley a small pickup truck was parked near the side entrance to the shop in the back of the truck Looking like they'd just been taken off the boat with several stalks of bananas There wasn't much else to see except the charred wooden refuse left in the alley after the fire I Started back toward the street what a man a much larger man than the power came out the side door and got into the truck He turned over the engine and switched on the lights before I could get clear. Hey, what are you doing there? Mr. Right there, buddy.  All right now, mr. I'm wondering what this load of bananas is doing in an antique shop Well, I just caught this guy snooping around the back It's mr. Duller. Yeah, that's right. You know him the park is one of those insurance men. I told you about oh What are you here for dollar didn't the part tell you he doesn't want any money from you people now Why not because he's afraid we might have to take a good look around before paying. Oh, son I know now look dollar to do pause been okay with you people.  Dupar will have to do something to keep you away Ain't that right mr. Dupar? You know what I mean. Yes All right, I'll do it And he'll never bother us again Go on dollar get out of here At the time I had no idea what they meant to do so it wasn't easy to turn my back on them, but I did Nothing happened I went back to my hotel and hit the sack and I must confess I slept later than usual the next morning I was still in bed when the phone rang Johnny dollar. Well, hey now. Where's my dynamic northern friend? Oh, he's off today. I'm taking this place Well in the news I got I reckon it'll keep till tomorrow. Yeah No, no way way wait Angie Did you find out anything about that blonde deposit been seeing sure Meaning up till she went to work for mr. Dupar She worked for Dupar. Yeah. Well, come on. Okay, you know where she lives. Yep. What's her name? What yeah, and she thanks. That's plenty Expense account item five one dollar and forty cents cab fare from my hotel to the Pantalba apartments The list of names on the register near the manager's office told me Rose Ellen's apartment was number 215 When I got up there the girl who opened the door wasn't a blonde. Oh I'm looking for miss Rose Ellen. She isn't in. Oh She at work. I mean, are you a friend of her? My name is dollar Johnny dollar. I'm an insurance investigator and that's Well, she hasn't done anything has she Well, not that I know of look miss.  Oh, I'm good at recognizing talent Would you like to come in? I've got some coffee on Say you've certainly got a nice view of the square from here Don't you think so? Oh sure if you like that sort of thing me. I just think the square is kind of square That's good You and Rose move in here together. Oh Down Johnny make yourself at home.  Oh, I couldn't say may this is important What time does she usually get home? Well, I don't know.  Okay. Okay.  No, thanks. Just black good fire last Thursday night It's funny. What's funny? That was the last time I saw her What yeah Rose went to work last Thursday, but she never came home Act two of yours truly Johnny dollar in just a moment You don't have to be a special investigator to know that Americans don't take their civic responsibilities lightly The election day turnout proved that beyond any shadow of doubt So now it's time for you to face up to another responsibility to the nation in just as straightforward away Our ground observer core needs volunteers We at CBS radio Urge you to write or telephone your nearest Civil Defense Center to learn how you can help in this vast program that patrols our skies Now act two of yours truly Johnny dollar and the Royal Street matter This was the screwiest deal I'd ever seen a guy refusing insurance money. He was entitled to Rose Ellen was my one lead. So I continued questioning may her roommate May told me this was the first time Rose had been away so long without at least sending for a change of clothes. I Asked about roses boyfriends. She told me Rose had been going with one other man beside Dupont, but she didn't know who he was After May promised to call me if she heard from Rose Ellen, I left Expense account item six one dollar and ninety cents taxi from the Pantalba apartments to the hibernia bank building My insurance contact Benford wasn't in So while I waited for him, I wondered again why the pod refused to sign the claim for the fire damage to his shop Could he afford a loss of sixteen thousand dollars? I Wondered if something had happened in that shop something to pod tried to cover up with a fire I was wondering what it could have been what Benford walked Well, I'm glad you were here Johnny We got trouble. Oh Here you paid Dupont call last night that we have been yeah, he pulled me about 10 wanted me there fast.   It's none of your affair now no matter what he's up to Hmm Man, it's too bad. I had to turn out this way You want a drink before you go? Yeah, I guess I need one. Yeah, let it be scotch or I Scotch need place When you reckon you leave Oh, I don't know. I'll check with the airline when I get back to the hotel Yeah Better luck next to that Yeah, that's that CD What about the policy policy did he return the policy to you? I know I said do it tomorrow But he's covered until he does return it does he know that I don't reckon it does good good He might get careless and as long as that policy is in foresight and bother him as much as I want Don't see what's used Johnny. He'll have it here about more evening. That's still gives me 24 hours to get lucky CD you said something about a customer being with him when that kerosene lamp was knocked over According to what he told the fire department there was you had that person's name Took it in the fire department report got that right here Mm-hmm the name was Andrew W. DeLong address 1515 West Claiborne There wasn't any Andrew DeLong at that address we checked the telephone book and the city directory and the only Andrew W. DeLong we found was out in Metri in a mausoleum So we drove back towards CD's office Well now what Johnny to Pa find out everything we can about to Pa and everybody who works for Ain't nobody but his secretary and his assistant tell the name car. Yeah, how long has Carl been working for him by as long as she has This is Carl on a fruit stand a Not I know about why I just wanted hey, what time is it CD? 215 say if we're going to check on to Pa's credit. We better get to the bank for the clothes. You're driving. Let's move Expense account item seven twenty two dollars and eighty cents telephone calls and a couple of gratuities to obtain a lot of information about to Pa I Learned among other things that he banked almost eleven thousand dollars in the past three months before that almost nothing But there's no law against making money. So I still had nothing concrete to go on At 530 I left binford went back to my hotel and they found a message from me Rose Ellen's roommate Asking me to go to her apartment immediately. So I did yeah, hi me You know what you made me proud. Yeah Well, it happened you mean you've heard from Rose well No, not exactly But a man called this afternoon and talked about her. Oh, well, I hope he had only nice things to say Oh, yes, he said she's just fine What didn't you hear me? Yeah, he said she's fine fine. What else did he say? Well, he said he was going to come by at four o'clock and pick up her clothes I should have them ready. Oh, but of course he didn't well. He did so he did What man you know him you get his name? Mr. Dollar You don't think I'd let roses things go out of here with a complete stranger. Do you of course? He told me his name well You aren't nearly as polite as you were this morning. All right, I'm sorry What's the man's name darling? Oh? Well, that's much better. It's Grant Grant. That's right From the way he talked he must be the one rose was going with while she was dating that old antique You ever see this guy grant before no, but I'm sure he's the one she talked about really it used to get so tiresome Listen What I said all may tell me where did he say he was taking her clothes. He didn't say just put them in that old truck Thanks, sweetheart. See you later. I Needed a fast car and a driver who could handle it.  There was a dim light on inside. Look brother There's really no reason for you to get mixed up in this thing. Are you kidding, son? Hmm Like Dubai ain't going to answer. All right, let's see what this hunk of stone will do to the glass here And I've got it. I can reach suit to lock looks like nobody here. Hey, wait a minute. Yeah, I see him Carl what happened to you? Angie calling ambulance tell them a man's been stabbed here.   He thought I'd killed her But I love her. Yeah.  Yeah, you know where that is Angie Oh, sure no ruin out in the swamp north of town near the highway bridge. It goes over to the Gulf Coast Carl How long ago did DuPas leave? 10 or 15 minutes Yeah, well we could beat him Johnny by cutting across the swamps that is if you could take it What do you mean by that? Well, it's rugged like what Johnny if you ever ride a swamp buggy Oh brother How much farther Angie? Well should be right up ahead. How can you tell all I can see is swamp and harsh grass? Yeah, well, I done a lot of trapping out here. I know the channel Think we'll make the old ruins before DuPas. Well, we got to don't we? Hey, that's it. That old wreck is called a fortress man. That's it. Well get us up as close to it as you can. I Don't see anybody parked Somebody approaching the bridge There we are Come on, let's go. Hey. Hey look John. There. She is at the side end. Yeah, I see Rose Rose Ellen.  Well, come on Johnny.   Come on out here where we can see you Rose that Carl didn't kill me that is yeah, but Carl's all right now Look Rose.  Were you there? Yes? Oh, what happened? I had me tied up told Carl.  Go on. Go on Carl argued with him That's when the lamp got knocked over He didn't stop arguing till DuPas said he'd kill us both So finally Carl told the pot he'd take care of me.  Let's get out this dark. What a minute Rose, do you know why DuPas was afraid to report his fire to the insurance company? Some of the things he smuggled in was lost in the fire Anybody come poking around they might have found out what he's doing. What was he smuggling? Do you know?  No, I can't yeah, sure No wonder he banks so much money so fast bank much more Get rid of you dollar. Look, look at that. Yeah, he is the door. Yeah, watch it He can't see us No, but what a target he makes in that doorway against the light. No gun We can try one of these bricks Wish me luck Right here to pop Come on. Oh man, dear. You could qualify for the New York Yankees Johnny All right, you're fine on your feet. Let's get out of here Expensive count total including rental on the swamp buggy incidentals and transportation back to Hartford $517 and 20 cents remarks Well, where he's going DuPas wouldn't have any use for the insurance money anyway Carl Grant turned states evidence and clinched the smuggling charges against him Because of that Carl may get off easy. I hope so. He and Rose could make a very happy couple and To remarks and to report yours truly Johnny dollar our star will return in just a moment if we are to remain alert to possible acts of aggression We need the continuous operation of the ground observer core and if the ground observer core is to remain on the job Around the clock seven days a week your help is needed tomorrow Telephone your nearest civil defense center and volunteer a few hours of your time each week to the ground observer core Join our ground observer core at the civil defense center nearest your home Now here is our star to tell you about next week story next week three sets of twins to men to girls and Two fires that hit the coast of flora with the impact of a hurricane Join us. Won't you yours truly Johnny dollar Yours truly Johnny dollar starring Bob Bailey originates in Hollywood Written by Charles B Smith. It is produced and directed by Jack Johnstone heard in tonight's cast were Virginia Greg, Boris Lewis, Lou Merrill, Lawrence Dobkin and Frank Gersel Musical supervision is by Amariga Marino and Carl Fortina Be sure to join us next week same time and station for another exciting story of yours truly Johnny dollar Dan coverley speaking


And I like to do my presentations a little bit differently, so here we'll give it a try and see. Hello, I am Rick Jures and I welcome you to this presentation, Making Boos Do More. I have been teaching with Moodle since 2008. The universities that I work for do not run at Moodle, so instead I run it myself on my own virtual private server. I deliver 10 to 15 courses to approximately 450 students each year. We all want Moodle to look great. The problem is that everybody has a different definition of what great is. The solution to making your Moodle look great is themes, and there are three general approaches. You can design your own theme, you can use a third-party plugin theme, or use one of the built-in themes. The advantage of designing your own custom theme is that you can do anything, but the learning curve is steep and it takes time and money. There are many great third-party plugin themes that are equipped to deploy. The learning curve is shorter, but long-term support is sometimes questionable. Moodle's built-in themes provide long-term support, and you just pick the one that you want to use, but sometimes they do not look as great as you would like. I prefer to use Moodle's built-in themes. Prior to Moodle 3.2, I used more and modified it with CSS. I gave a presentation at last year's Moodle Mood about how I did this. See my website for more information. Since Moodle 3.2, we now have Boost, the newest core theme. It provides additional features, and there are new ways to apply CSS code. Boost seems to be the future direction, and I like it. My problem was how to make Boost look like my existing more. Here's how my more was looking to students, and here's how the new Boost looks. So my challenge became learning how to modify Boost with CSS. My strategy for more was to use the theme settings and the custom CSS dialog box. Boost is a little different. It has an advanced settings tab with two CSS dialog boxes and a general settings tab that has something to do with preset files and a few other settings. What I learned was that I can use Boost, raw CSS dialog box, exactly like the custom CSS dialog box in more. Boost also provides the ability to use a preset file where you can make changes to elements and add your own custom CSS code. I will tell you more about this later. So how does one do this? Briefly, you use your browser's inspection tools and probe for the element of interest and this associated CSS code. You make changes to this code, view the results. When satisfied, you copy the CSS code into the raw SCSS text box. Post on Moodle.org when you can't figure it out. Here's an example. I want to change the course font color to red. Using Firefox's web developer inspector tool, I find the element of interest. I look at its code, I change this to red, see that it works and it does, and then I copy this code to the raw SCSS dialog box. As another example, let's say I want to change the nav bar color. Again, using Firefox's inspector tool, I probe for the element and its associated CSS code and I make a change to it, see how it looks, copy this code, and then paste it into Boost's raw SCSS dialog box. I prefer my heading text sizes and line spacing to be a little bit tighter. Again, I probe for these elements, made some changes, and then copied this code into the raw SCSS dialog box. I didn't know how to change the background image, so I asked for some help on Moodle.org. Here is the code that I was provided and it worked. Preset files allow you to control the look of your Moodle through changing variables and adding CSS code. I learned to start with the default file and rename it to something that I prefer. As we look at the default file, we can see element values and CSS code. Let me show you. Here's my own preset file where I can change heading text sizes and here's where I add the background image CSS code. I load it into my Moodle's Boost theme, select it from the dropdown, and then save these changes. The preset file becomes a way to share the look of your Moodle with others. My method of using the preset file is that I first work with the raw SCSS dialog box, perfecting my code. I edit the preset file with the text editor, cut the CSS code from the raw SCSS dialog box, and paste it into the preset file. I save this, reload the preset file into Boost, and see that it works. Well, after 5-9 hours of doing this, times 10, here's what my Moodle looked like using more in Moodle 3.1, and here's what it looks like using Boost in Moodle 3.3. I am satisfied with the look of my Moodle and most of the new functionality of Boost. In summary, here are some of the advantages of my approach. I do use the core themes, meaning good, long-term support. It's easy to maintain and make changes. When I update my Moodle, this code persists, and it's easy for me to move the appearance around to other Moodles. Some of the disadvantages are that this CSS is still a little technical, and there is still a learning curve. What is fun to one person can be a pain in the neck to others, and the results are not as cool as some of the third-party plugin themes. As much as I do like Boost, I should mention that I do have a couple issues with it. In more, I was able to collapse these right-side blocks. Boost does not provide this functionality yet. Please vote for my tracker item. There has also been a lot of discussion of what should be in the nav drawer. I do believe that there is great opportunity to greatly enhance the nav drawer and make it become a valuable user-customized feature for surpassing competitor LMSs. Please visit my website for additional support to this presentation, including a default SCSS file, my preset file, my CSS code, and this presentation video. Thanks for taking your time to listen to my presentation.


So, if quantum mechanics can tell us how to calculate the energies that a system is allowed to have, then the Boltzmann distribution can tell us the probability that each one of those states is occupied. The probability of state j with energy e sub j is given by the Boltzmann distribution where q is this term, the sum of all these e to the minus energies over kT's. And remember these terms that look like e to the minus energy over kT, those are called Boltzmann factors. The probability that a state is occupied is proportional to its Boltzmann factor and that proportionality constant is 1 over q, where q itself is the sum of all of the Boltzmann factors for all the energies the system can occupy. So, this quantity q actually turns out to be very important, not just as being the denominator in this expression, but also for other reasons as well. So, we'll spend a little bit of time talking about this quantity and we'll give it a name first of all. The name for this quantity q, the sum of all the Boltzmann factors, is a partition function. We call q the partition function, so that definition tells us the partition function is the sum of all the Boltzmann factors for a system. So, first we'll talk about what we can understand this partition function to mean, what does it mean if a partition function is large or small or has a particular value. So there's two ways to think about what the partition function is. One is given by this expression. It's the denominator in this expression for calculating the probability. The reason q has to be the sum of all the Boltzmann factors is if I take this Boltzmann factor divided by the sum of all of them to calculate the probability, that ensures that when I add up all the probabilities, if I add up the probability for state one and two and three and four, that sum in the numerator will cancel the sum in the denominator and the probabilities will sum to one. So in that sense, the partition function is just a normalization constant. And that's not terribly exciting or terribly interesting. It has the value it has because if it had any other value then the probabilities wouldn't sum up to one and we want the probabilities to sum to one. If you remember where this expression first came up, it was when we did Lagrange multipliers to constrain the probabilities to add to one. So that's a somewhat boring interpretation of the partition function. It's a normalization constant that guarantees the probabilities will sum to one. But there's a much more interesting way to interpret the partition function as well. And to see that, we'll go back to an example like the butane molecule that we've considered in the past. So remember, butane can have an anti or a gauche conformation and the gauche conformation, there's two of them, gauche plus and gauche minus that have the same energy as each other. So here are the different energies of the three different conformations of the butane molecule, two gauche conformations, one anti. When we treated this problem numerically, if we know the value of this difference in energy, if I tell you that difference in energy is 3.6 kilojoules per mole, and if I tell you we're interested in the temperature of 298 Kelvin, that's enough energy to plug into this expression to tell us. And also, if I say the zero of energy is down here, the anti state has zero energy, that's enough to calculate the partition function. We won't repeat that calculation, but what we found was the partition function. e to the minus e anti over kT, e to the minus e gauche over kT, e to the minus e gauche over kT. The sum of the Boltzmann factors for each of these three different states, numerically, since we want to understand what the value of the partition function means. Numerically, the partition function came out to be one when we add e to the zero and then some smaller number for e to the minus 3.6 kilojoules per mole over k times this temperature. So overall, the partition function came out to be 1.44 in that example. So what does that mean if the partition function is 1.44? Well, think about this way, if I ask you how many states are there that the butane molecule can occupy, you'll say three, an anti and two gauche states. And if I say, well, how many of the states can actually be occupied at 298 Kelvin? You say, well, certainly the ground state can be occupied. There's plenty of molecules in the ground state. The gauche states are partially occupied. These Boltzmann factors tell us exactly, if I were to ask, what's the probability of occupying the gauche plus state relative to the anti state? That ratio of this Boltzmann factor to that Boltzmann factor tells us these states are only 22% as occupied as the ground state. There's only 22% as many butane molecules in the gauche plus state as in the ground state. There's only 22% as many in the gauche minus state as in the ground state. So my question, how many of these states are occupied? You might say, well, the ground state is fully occupied. These two gauche states are only 22% as occupied as the ground state. So the total number of occupied states is 1 plus 22% plus 22%. So in that sense, what this 1.44 is telling us is the number of accessible states. The number of states that can be reached at 298 Kelvin is about one and a half, about 1.44. So not all three states are equally accessible. The upper states are less accessible than the ground state. And the number of accessible states is something like 1.44. So in that sense, we can often interpret the partition function as not the total number of states in the system, but the number of states that can be reached at this temperature that we're interested in, the number of accessible states in this sense. So that's a much more valuable way of understanding what the partition function means. We can think of it as the number of accessible states. There's a couple of caveats to be aware of with that interpretation, however. Number one, that interpretation is really only a qualitative way of understanding the system. If I say 1.4 of the three states are accessible, then that statement doesn't actually make a tremendous amount of quantitative sense. What does it mean if only 1.4 states are accessible? We can understand it in the way I've just described. But when I'm counting number of states, it doesn't really make much sense to talk about a fractional number of states, kind of like the average number of children in a family is 2.5. Then either you have two children or you have three children talking about an average number of children that's a decimal or an average number of states that the decimal is not entirely sensible. So it does make a lot more sense, however, to think of this as a qualitative description. For example, if I were to repeat this example, recalculate these probabilities as the temperature drops to zero Kelvin, where the ground state is fully occupied, the population is in the upper states near zero, then as I go to zero Kelvin, the value of the partition function, as this temperature goes to zero, this term is going to be 1, these two terms are going to drop to near zero, so the partition function is going to drop in towards 1. So that means as the temperature gets colder, fewer and fewer states get accessible, only the ground state becomes accessible. That's a meaningful thing to think about. On the other hand, if I increase the temperature, as the temperature increases towards infinity, so if I plug in large values for T in this expression, each of these terms is going to be close to 1 because it's either the very small negative number, so the partition function is going to approach 3. So at high temperatures, I'm verging towards all three of these states being fully or equally accessible. If I don't just think about butane, but if I think about other systems like we'll consider in the future, here I've got a partition function that ranges somewhere between 1 and 3 depending on the temperature, but we'll see systems pretty soon where the partition function is as big as 10 to the 10th or 10 to the 30th. So what that means qualitatively is there's an enormous number of states accessible to the system, whatever the energy levels are, it's not just the first couple that are accessible, but there's 10 to the 10th states on that energy ladder that are accessible to the system at the temperature we're interested in. So at least in a qualitative sense, if we're able to say, well, only one state is accessible, a few states are accessible, or an enormous number of states are accessible to the system, that's what I mean when I say interpret the partition function qualitatively. The other important caveat to remember is that this explanation of what the partition function means relied on the fact that the ground state, when I plug in an energy of zero in here, I get one for the ground state. That's only going to be true if the ground state has an energy of zero. So if the lowest of all of these ground states, the lowest of all the energy levels, has an energy of zero, if that minimum energy is zero, then everything I've said is true. If not, if I say that the ground state has an energy of 500 kJ per mole, and so the excited state has an energy of 503.6 kJ per mole, then the partition function wouldn't be 1.44, it would be very different. So the good news, however, is we can recover this description, the partition function, which is the sum of all these Boltzmann factors. If I have a ground state which is not zero, if the ground state of the system has an energy of 500 in whatever units, I can choose to redefine the energy however I want. And one way to do that would be to say, let's recalculate, so that's the ordinary partition function. If I instead calculate e to the minus energy where I've subtract from each one of these energies the energy of the lowest state, so subtract 500 from each of my energies, then that will make the new difference be zero for the ground state and some higher number for the states above. So I've rewritten the sum with a different zero of energy, and if I factor out that e to the minus e min, so that's going to look like e to the e min, e to the minus ei over kT, and I can rewrite that as 1 over e to the minus e min outside, I should write a little higher. So if I rewrite this expression as 1 over e to the minus e min, multiplying by e to the minus energy over kT, those e sub i's have to be inside the sum, then this piece here is exactly like my original partition function. So rewriting this bit as q tells me that in order to recover this interpretation that the sum counts up the number of accessible states, I may or may not need to throw in an extra factor of 1 over e to the minus energy of the ground state, multiplying the original q, so it's really this quantity, 1 over e to the minus, sorry that's math error, so I've taken 1 over twice, e to the plus e min is 1 over e to the plus e min, so I can do it this way, 1 over e to the positive e min, or I could just get rid of the 1 over and say e to the minus e min times q corresponds to the number of accessible states. For the particular case like we've seen so far where the ground state has an energy of 0, then this leading term e to the 0 is just 1 and we don't have to worry about it. So if the ground state is 0, then q, the partition function, gives us the number of accessible states. If the ground state is something other than 0, then if I just prefix q with this correction factor, then that's still a way of counting the number of accessible states in the system. So this tells us perhaps a little bit about how to interpret the value of q. The next step will be to see what we can do with the partition function itself.


That's recording has started. All right, folks, welcome to this edition of the working group meeting. This is our meeting for may 11th. Of 2021, and I would encourage folks to go to the meeting group notes and put in your name. For the attendance sheet there under May 11th, that link is in the invite and I'll also put it here in the chat real quick here. So we'll get started with Vadim and then we'll move from there. So Vadim, what do you have for us in terms of updates? Some engineering points on the Yorkity. We didn't release this weekend because our previous signing key has expired. We submitted a fix for the new one but that fix is not being accepted by CVO yet. We have a pull request to fix that. We would need it to get reviewed and hopefully this weekend we'll make a new for seven release. Other than that, I think just a bunch of small fixes landed in for seven so it shouldn't be anything groundbreaking. Last week, or was it the week before that, we released a release candidate for OKD for one, for eight. The main difference is, well, it's Kubernetes 121 based and the way we back machine OS content has changed significantly. We're longer relive on Fedoro OS commits. Instead, we built from the same configuration using the same RPMs but we build our own commit layer cryo, all the necessary RPMs like open VM agent for Overt and VM tools for VMware. And that helps us to avoid using OS extensions. So that should make initial setup and upgrades a bit faster because all we need to do is just unpack the OS tree. And once you have the new OS tree deployment, you would be able to check the versions of the components using RPM QA command. So that's very helpful to figure out what versions have been installed. And with the bottom, at least with extensions, you no longer need access to Fedora repos. In fact, we disable them on every upgrade. So that should make it less rather more error prone. For eight is in so-called feature complete status meeting. Significant features won't be added but still more fixes are landing. So please stay tuned. Filebox report issues and general feedback would be very appreciated. I think that's all we have from the engineering standpoint. Are there any particular bugs that stand out in things that are filed right now that are open that people would be able to help you with by testing or at least taking a look at? Anything stand out in terms of issues? Nothing else to mind. Okay. I think a usual testing of this fear UBI especially would be very useful. We could ask for a copy of development version of documentation which lists some new features in for eight like proxy protocol support in ingress that might be useful for those who want to preserve the forwarded IPs. And some more features coming in for eight. These would be very useful to test early and report feedback bootstrap in place. That one is a tricky beast but some early testing would be very appreciated. But something to fix right now. I think a lot most significant issues are in our infra and those are very because they require a lot of tinkering and a lot of carefulness so that we wouldn't break nightlies at all. But channel testing and for eight features would be great to have a look. And next thing I wanted to do is I wanted to sort of highlight the discussion section of the repo which has gotten a little bit of activity lately and wanted to sort of go through these to see if there's anything outstanding or just to bring it to people's attention. One of the first ones that came in was the suggestion to have exact links to the Fedora Core OS. There's nothing that I know of right now. Actually my script, my OCT tools script has the ability to do that because it parses through the JSON to get it. But I don't know of anything else other than what we see coming forward. Any comments on that before we move to the next one? It's effectively would be a part of open shift install sub command to print the exact URL to ISO. But it's coming in for eight. I don't think we can backport it for seven but the long term fix is in the pipes. Yeah, sorry. Is it to download the Fedora Core OS images for install offline or yeah, so that's the video we added in for it. And now bouncing over to 609, automated solution to backup at CD schedule from within the cluster. Where did we land on that? There was a lot of discussion. Is Shreya on today? I don't see. But just to highlight this, I think this was a great discussion, automated solutions for backing up at CD. So folks can check out that thread again for those that are just joining or who are watching the video. There's now a discussion section of the OKD repo that's opened up and folks are having sort of more nuanced technical discussions there about features and things related to website and whatnot. And yeah, automatic backups would be awesome for sure. But there's some complexities there, obviously. And okay, any comments or thoughts on that or anything folks want to mention before we move on from that one? I think it's a great good starting ticket for users who want to play with OKD on. And we have various approaches to the same problem because, well, the use cases might be very different. Someone's backups on request, so maybe a text on task would be easy for that. Someone's a persistent snapshot, so an operator is probably a best pick here. I think various approaches, having some code scripted for the start would be great. And then we'll see which one is more widely adopted and wins effectively. Any other thoughts? Something like that. Yeah, some cronchop at least would be sufficient, I think, for the most critical backups once a day. I think I remember that we have to call a backup script that is always present on the notes to do an ETCD backup. And such a cronchop simply could call that script regularly. Maybe copy that away to external location that you can define by changing the cronchop scripts. I think a cronchop with a container is a great starting point. The problem is you don't get any reports if it fails, so might assume that it's fasting, but it's actually been failing all along. That's right, you're pre-handling on the container, it does nothing. Yeah. And the restore procedure probably should be somehow automated, but that's something to look forward to. But the container with which launches the script on the notes is probably the most critical part reused in every single approach we tried. So cronchop is a great starting place, which we can easily evolve into tecton pipeline. And then we could write a more complicated operator on top of that and have a proper reporting, maybe even via tecton. So that would be a great showcase of how various technologies connect with each other. Let's see if we can round up some folks. There's a lot of ideas floating around. It'd be sort of get a concerted effort, maybe get a repo together. I'm happy to contribute to the tecton aspect of it. And I think it would be cool if a couple folks from the group got together and created a little subgroup to come up with something. All right, next one is transition to C groups V2. I threw this in to sort of have documentation of the conversations between the Fedora Core OS group and the OKD group. Vadim, if you just want to talk to this for a second, basically it's covered in there, but if there's anything you want to add. Sorry, I missed. Which ticket are we discussing? The transition to C groups V2 that Epcos is doing. Right. So we have all the basics and for a night lease. The only missing part is run C used by builders. So all the features are working. We have a protocol which can enable it, but the tests failing because all the builds are effectively crashing immediately. What we could do is to experiment with building our own OKD setup with updated builder. And where we pull it, the problem is that it might be using rail packages. So testing it in CI would be pretty complicated. But as an exercise to build a builder container using CentOS streams Fedora would be great. It is excellent because all we have is Dockerfile starting part. And that would be very helpful because the ticket is well filed, but it's not the priority for age release for sure, but we'll be pushing it to be released in 4.9. Any other thoughts on that? Timothy, do you have any thoughts you wanted to add to that? I'm looking at the ticket details. And yeah, even though it's not a goal right now for OpenShift product, it's definitely on a radar. So I guess it should, I don't know how it's going to get fixed exactly, but yeah, it's still kind of a priority for us. Anyone else have any comments? Any comments or thoughts on C Groups V2? No opinion of that. I want it. I knew that was coming. I should probably know this, but what are the advantages of C Groups 2 versus 1? I mean, what's the, what do we gain from it? The largest benefit is probably a fair, actual fair IO scheduling. And I don't think Kubernetes uses it, but what we could have is not just for the memory, but you can also have something like a middle or intermediate limit, which tells the application that it's time to release a memory if it can do that. So that allows you to schedule workloads in more, well, flexible fashion. But other than that, that's mostly a lot of low level things which, well, just don't use parts of the kernel which are created in 2004. That's all we know. Yeah, as definitely as I'm saying, the main one is all the disk access checks, the disk access accounting and the memory accounting. I think everything makes sense in V2 much more than in V1 where you have a lot of discrepancies between, between accounting and memory processes. The biggest thing, the biggest thing for me from a V2 perspective is you can trivially tie resources to a process and be able to track that through its children because the groups aren't based on this concept of controllers of different types of resources. They're based on where you're instantiating a scope for a process. So control groups are actually singularly grouped in V2, whereas they're multiply grouped in V1. And that makes it a lot harder to track and make sure that things are actually being allocated correctly and tracked. And that's why a lot of things like UMDI, PSI tracking and stuff like that, they all depend on V2 because you can connect all the resources you're, you're allocating to the process and question that you're trying to instantiate. So in this case, with a container that'll instantiate a scope and a slice and a resource, you can tie all those resources directly to that and make it the distinct owner of those resources. Cool. Something to look forward to then. Next one up. So this one is, was an error or a perceived error? So we're looking at 622. Vadim, did you want the discussion section to be a place for people to put errors or would you prefer that they actually go in the issue section as opposed to in the discussion section? No, I think starting with the discussion is a good idea. Well, two starting points are equally fair because we don't know if it's an issue in Okiti initially or it's just here, I might have typed or using an old Julie, so it might have been fixed. We can anyway convert any discussion here into discussion, so that's very interchangeable. I think it's a great place to share some logs and error lines, but of course no guarantee that we'll look into this and somebody actually actively supporting this. So discussions like that are probably a good place. We probably should create a new, a special topic for this. Yeah, category. I'm not sure how to name it correctly, but I think it's a great idea to group these kind of discussions and tickets. And this one in particular, Okiti 47 storage operator degraded. Basically it's resolved. Did you want to say anything about that, Vadim? Add anything other than what you have? It's a common problem and for seven, including a recipe where folks don't know what they want. They have a vSphere platform, but they're not sure if they would be using machine API or they would be using storage. They might switch to CSI, which doesn't use in three drivers. So the credentials might or might not be valid, and the installation may pass if you don't use those features within valid credentials. And in order to track that, we added a degraded condition for this to verify that if you have a vSphere cluster and your credentials are invalid, we won't proceed with upgrade because it might break a lot of things. That caused a lot of discussion internally, because a whole bunch of people are using vSphere without using storage or machine API, so they use fake credentials. The bottom line is that it will be eventually converted into an alert saying you may not use that, but you should be aware that your credentials are wrong. And the upgrade would pass, but the admins would still be notified. At this point, it's a requirement for the credentials to be correct, but might not be the case for seven later. I think it's a good starting point where we can link people, because it's not effectively an issue in OCD, but it's a really good example of how discussions should be, how they should work. Anyone else have anything they want to chime in on that one? All right. I threw another one in here. That's from the F-Cos working group. F-Cos moving IP tables to the NFT backend. Vadim, again, anything you want to add to that? That's pretty straightforward. I don't think it should affect us significantly, mostly because OCD defaults to OVN, meaning the Qproxy, the most fragile component here, would not be using NFTs, in fact, used at all. And RoyalCrowS, if I remember correctly, from day one has been using NFT, so all these cases have been tested, and it just starts lagging behind. In any case, since in 4.8, we've actively controlled the whole configuration for 4.8. All we need to do is just pull one Podman container, and that's a basic case where, which FedoraCrowS ensures, so when we can control the whole configuration and rollback, the NFT change, if we have a good reason to do that. But I'm thinking even if we hit issues, these would be reported to the SDN team, and they should be fixing it, because eventually NFT would be defaulted in Royal if it's not yet. So I think if we have a good end, in case the issues would appear. Timothy, did you want to add anything to that? Yeah, I'm just checking right now, but the NFT backend has been defaulted in Royal, 8.0, I agree. It just realized that actually we were lagging behind in FedoraCrowS, in a sense, but it's not by choice, it's more by mistake. But yeah, so nothing should break on the OCD side, hopefully.  Yeah, sorry, it's still the same interfaces, it's just changing the backend for IPCable, so essentially it's the same command line, the same tools, just using a different backend underneath. Anyone else want to add anything to that? I like that new format, I have to tell you a bit, that we discuss about issues, I love that. I really love that. In the meeting format, or do you mean? Yes, yes, yes, yes. We'll bring that feedback to Diane. This is generally how I do meetings of this sort, but we'll bring it back to Diane and see what she says. Okay, so the next one that I added is Clarify OCD's Community Support Model. I threw this one in because Red Hat employees, one in particular, keeps getting personal emails and people tagging him in the channel and all sorts of things, trying to get support from the person that they know is sort of the Red Hat employee that's working on OCD. So my thought is that we scour through the website, the repos and whatever and actually have a boilerplate couple sentences paragraph that says, what does community support mean? We have that in the big banner on the website, but we don't actually explain what is community supported and community driven. There's two reasons that this is important. I think, number one, it's unfair to the people who are Red Hat employees who are providing their time to help out and probably wears on them. I'd imagine that it sort of stresses them out. The other thing is that if one person gets tagged and one person is the target for it, then the community can't help because we know we've got our institutional knowledge and memory and whatever to help on these issues and also we don't learn because if we're not privy to these discussions or we're sort of boxed out of them, then the rest of us can't learn about these particular things. So there's multiple advantages to this. So we talked about this at the Doc Groups meeting, Docs Group meeting last Tuesday and we'll be talking about it at the next meeting. If anyone can join us at the Docs meeting to chip in on this coming up with a couple sentences that we can put somewhere, then that would be, yeah, Bruce says, reference the goose that laid the golden egg fable. Then I think if we can come up with something in the next like week or so and then just go through all of the OKD references and plaster this up so that we can relieve the load on the Red Hat employees who have been bearing so much and get ourselves more up to speed on things. Sorry. Would it be worth putting in, you know, to the Slack channel occasionally, you know, a boilerplate message indicating that, you know, this is community supported, you know, along with the working group email, you know, saying that this is not Vadim supported. I mean, not specifically saying Vadim, but, you know, the idea is that community members are helping if it's not just one person. They're just, you know, once a week put something out there or whatever till people get the hint. I mean, I'm trying to help people. I know Vadim is, but, you know, other people are going to have to start jumping in also. And we can do channel announcements and things like that for sure. I think that's a great idea. Anyone else have thoughts? It sort of just occurred to me earlier today that it actually might be useful to somehow put together some information of this is what you can do. OK, because I think what happens to a lot of people and as I was telling Vadim, I would include myself on that list on occasion, especially when I'm tired and irritable or lazy, which is often, is that, you know, the easiest thing to do is to seek help. But that's not really a long-term strategy. And it's not that easy in the documentation to find out. Like, we do have a FAC and we do have some information there. So that's certainly good as far as it goes. But it might be useful to try and pull together some, like, checklists or try this or did you look at that or things that are important? I don't know. I mean, it's a big topic. So that's just a vague idea of something that might help as well. And we can always link to that website. What's the website that's like how to ask questions? There's like an actual URL or someone set up a site that like you go to and it's actually like, how do you ask questions for support and for troubleshooting and whatnot? John, did I hear you say, start some? Yeah, I have a delay here. So I think you're done. I start talking or whatever.  I think something like that would be great to send to the go.  You know, how do you do a basic analysis of it? What are the things in it that are important? And that might help. And it might help people who want to help too, because some of that stuff in there is very esoteric and sometimes you just have to stumble across it. So I don't know, I'm not trying to put more work on Vadim though, but that might be something that's okay. Yeah, that sounds like a, that sounds like a very useful thing. I'm just not sure about the format. Should it be a YouTube thing, a blog post, text, maybe, hello there, Bob. Yeah, blogs are easier to reference.  Okay, how do I find it? Can you do a short video? I can see a YouTube video having some advantages of like, someone wanting to see like, oh, actually, how do you search through it? What particular things would you be looking for? Yeah, but this, we shouldn't be limited. I think we should start with a YouTube video because it's easier. And I'm not sure which parts of the process should we focus on. For instance, there's a bunch of code which generates certificates. I have no idea who works. I can barely handle the open SSL CLI. So I probably would rather discuss the versions and the bootstrap process, but this thing also needs to be covered in some kind of a blog post and so on. But initial response from the video would help us to shape up the basics of the markdown document we would put and then we could extend later on. Another concern is that things get outdated. Yes. Well, not that badly on Craig's blog post. It's still like top 10 in top 10 of OpenShift blog posts and it still refers to OpenShift, oh, Kitty45. Some pieces there are very old and not used anymore, but in general it kind of works. I suppose we would still have to update this document very frequently in the beginning and then with every major release we could update it, but it sounds like it's a required thing. Yeah, I'm not sure if I would have time to create it from scratch to the very end, but I guess I could have some, I guess I could create in a week or two until our next meeting some drafts were helpful. If you want to put something together, a rough template, I mean, I could try to put a video together if you don't have time. I think that that would be, I think John's making a good point was really if we could just get some pointers from you like just a template of items that you think would be important to hit, the group can handle John himself or can do the video, anyone else can ship in and same with documentation. We don't want to add more work to you, but you're the one who handles a majority of the tickets and also knows the innards best of anyone in the group. So if you just gave us a template of these are the things to hit, then we could run with it in all of the venues, be it blog posts or video or anything like that. Good idea. Sounds like a plan, yeah. Excellent. Anyone else have thoughts? Anyone want to go ahead? Well, it sounds fine to me, but I was also just going to say that I've got a drop now because I'm going to go get go on my merry way to go get my second vaccine shot. So I'll see y'all later. Awesome. See you in health wheel. Take care. Yep, you too. Bye y'all. I think it would be a good idea to have a recording. Yeah, maybe like a role play if you get a lock bundle, what you do first and just to see some typical, yeah, typical steps that maybe reproducible by others. I'm sure because you are always so fast that you have some typical spots where you look first. Well, folks should feel free to chip in. So Vadim can get us something within, let's say within the next month, right? We don't want to put too much on his plate, but if Vadim gets us a template, then folks from the group will all sort of divvy up the tasks of getting it into the various formats, coming up with something in the various formats, blog, whatever, and the docs group, I'll mention this at the docs group because there's some people going to the docs, meaning they're not coming to this and vice versa. All right, anything else on this topic? Is there anything else that we can do that folks can think of to make it, to clarify what the model is, the support model is? Is there anything else we can do other than providing this documentation and putting some boilerplate language in the various places where we have a presence? Anything else? I think a problem maybe that Vadim has sure a connection to a huge internal network of people that know each corner of the system, and most people from outside don't have that. And I think that's the reason why lots of people ask him, because he's the gateway to this internal network, and we don't have it, and maybe someone has a good idea how to get a substitute to not need the internal network, but to know which repos are they working on, how we can contact them through issues and so on. That shouldn't well happen. The internal knowledge is of course a huge source, but it's not being used in every single report. Most issues are very trivial, and I think like three or four of our architects are in an open-shift dev, so you can think. I can name drop later, but I don't think they would like it. The real way to handle is probably starting with some... We have a bunch of issues logged for OCD and showing activity there would be very helpful, just some basics. Here is how I understand Bootstrap, here is what I see from Logbundle. I'm stuck here, I don't know what's happening. I could jump in and help and extend this of course, but a lot of issues are just... I'm thinking folks opinion me directly, just because I respond there and respond in every single issue, and people assume that I'm the only one here. Well, that's the belief we should... Any other thoughts on this? I remember as we were searching for John, Vadim and I were searching for an OVN Kubernetes problem, and finally, I think Vadim got us the first steps, and John and me were searching through the community. And finally, I think the guys at John, do you remember, at the network manager, I don't know what the chat is called now. They helped us, and finally, I think it was a solution, so you don't need always a single person. I think it was a great example of how it should be structured. My network knowledge is very limited, and I have rather not extended, actually. So this is why I would rather pass it to some professionals who can chase folks on IRC and help with some details that don't fully understand. We should learn lessons from this, and structure our workflow in a similar fashion. Maybe that there are bugs that, you know, like we did, we created that sort of private Slack group, whatever, with the three of us, but there may be issues that, you know, we can get, if we need to get three or four people in, where it's easier to have a discussion in that private channel versus the open discussion, then publish the findings afterwards, because sometimes you get chime in after chime in and after chime in, and it gets distracting. It's all good, but distracting. Yeah, there was a good idea, which we implemented here. Some ad hoc chats for the interest of people was certainly a good idea, yeah. Well, let's move on now. I think we've got a great foundation now for this particular topic to move forward with. And I'll go back and fill in the discussion item with sort of what we discussed here at the meeting, so that we've got sort of a clear record in that actual thread. And that's the other thing is, if you put something in the discussions, and we talk about it at the meeting, if you can update the discussion item, if you created it folks, that's helpful, and sort of keeps things organized. And then the last thing in the discussions is insights operator is degraded. Vadim, is there anything you wanted to add on that one? No, I think we need logs, because there are multiple things which could be causing it. It could be proxy. You could be actual, well, unlikely, but actual downtime of the insights operator for some short time. Well, if we would have logs, we would have some something to discuss there. Yeah. We'll point out that Vadim says that's great, but I'm not a dedicated OKD support person in this community should have access to it. And I do think that's an important thing, again, is the community, you know, we can't lift the community up if we don't have access to these logs as well. We talked about the issue of identifying information. Did anyone come up with or know of, like, just a simple bash script that cleans things up to make it easier that we could just post and people could download it and scrub anything? You know, because, you know, host names, people feel that that's identifying and, you know, any IP numbers and stuff like that. Maybe we just come up with a simple bash script that cleans that out. We could have something like an up for skater or something like that. Yes. The problem is that they have to be consistent. You can replace every host name with local host and expect us to make sense of it. That's, well, that's a complicated topic, of course. If we scrub to art, that might not help us say maybe your password is wrong or maybe, well, he's probably wrong. Yeah, we don't have a great solution for this, especially anything privacy-related solution from uploading this. Sorry, hold on. Who is that? I didn't see who was that was talking. Hi, here's Eric. What is the SOS tool doing? Because this is now also scratch, I think, maybe half a year ago. Yeah, but aren't SOS logs going to Red Hat and stuff? I mean, you have a certain concept of security of things are being sent to us. Yes. We have the whole customer, we have the whole customer portal and GDPR things and CCSA, which is as a community and okay, you certainly don't want to deal with and legal. Yes. As well as the shell tool, right? You call it and collect stuff for you. Yes. The problem is sharing the results. The log bundle is built in a similar way, but some information might be considered sensitive. Let's put it like this. I don't think host names are sensitive. Some folks think they are and we need some way how to have them replaced with some fake names, but still make sense in the end. That's virtually possible. My assumption is that the SOS tool would do it. No. Rather, it was not built for that. Another problem is we also copy a lot of certificates, which effectively in the end have the host names embedded in them. You just have to extract them. Probably, our solution would be to avoid scrubbing, but to uplam temporary places, which would have to delete it after a couple of hours a day. That would give us the full information and severely limit the time before attack. Again, this is a security through obscurity, but that's probably the best we've got. If we have any other ideas, that would be very welcome because the log bundles are expected to not have all the sensitive information, and the same applies to must gather, but in order to identify all the issues, they effectively have to also read data from user namespaces so that we could understand maybe it's PDB blocking the upgrade or something. I don't want to spend too much time on this because we've only got 14 minutes left. We actually had a larger discussion a couple of months ago about this that took up a significant amount of time. Let's regroup on this at the next meeting, but maybe if we came up with a list of things that people do feel are concerning items from the logs that are concerning. If we generated a list and then said, okay, how could we tackle this? Can we tackle this? Then we actually know what we're looking at. Some folks in the group may not be familiar with must gather. Let's table this, but in the meantime, if folks are just in their minds who are familiar with must gather, think about some of the things that would be problematic, and maybe I'll send something to the group, share out like a Google doc or maybe a discussion. In the discussions, actually, we could do it in there. In the discussions, just generate a list of things that we think could be viewed as problematic, and again, we're having to put ourselves in other people's place and what they would think would be problematic in that, and then from there, at the next meeting or a future meeting, discuss ways in which we could ally those concerns a little bit. Does that sound good? Yes? Okay. All right, and that's it for the discussions. Suzy, did you want to bring up anything from the Fedora Core Westworld that you think that folks should know about? So, right now, on the Fedora Core Westside, we did this last week on testing for Fedora 34, but that's not a direct impact on OKD because OKD doesn't switch when Fedora Core Switch is switched when machine-wise content gets pushed. But yes, essentially, it's coming. Apart from that, I think we've already discussed C Group D2, which is one thing. The move to NFG, which is second one. The account meet changes are coming later in August. Just a reminder for folks, starting from the releases in August. So, maybe not the releases in OKD in August, but a little bit later. The default will be on Fedora Core S that you will send account meet request to the Fedora service. But essentially, it's a very privacy-friendly way of counting the number of Fedora Core S node meetings running on the planet, and for us to have some kind of statistics of how many people are running Fedora Core S. So, this one is coming around August, and there's already instructions. There's a magazine article coming up probably next week, or this week or next week, to explain how to disable that. Maybe we could have something specific for OKD to disable that, but it's essentially a two-line machine config, so it should be fairly easy. And yeah, I don't think we have anything more really, really important right now happening besides all of that, so I guess it should be good. Did you want to talk a little bit about the signing discussion? That took a lot of time at the last meeting, and I think it does relate to OKD nodes in the way that people might keep them around for a while, if their cluster is running a long time, etc. True, but I'm thinking about that one, but I'm not sure it impacts OKD because the updates on OKD does not happen the same way they happen on Fedora Core S Classic, I would say. So, maybe I'm wrong here, but I think OKD should not be impacted by that. The issue in general is that if you start from a very old Fedora Core S node and you try to date to a fresher version, you only have issues because you won't have the signing keys to verify that the latest version is actually a valid one because you're in a very old node and potentially you don't have the latest keys to verify that because on Fedora Core S, Fedora in general, we only ship the next two releases keys in an image. So, if you're starting on Fedora 30, for example, and you want to upgrade to Fedora 35, then you won't have the key for Fedora 35, but that should not be an issue as far as I know on OKD because on OKD, the updates happen, they are the MCO and the machine noise contents are rigid on the cluster and there's no, it's not pulling any content from a signed OSRI repo. So, it's not exactly updating the same way that we update the classic Fedora Core S nodes. So, yeah, maybe, I'm not 100% sure, so maybe about him you could confirm that, but yeah. Right, there is a very unlikely case, Bruce has mentioned it, that if you start with Fedora 30 Core OS as a bootstrap node and then you want to install which is probably based on Fedora 49, in that case you would of course fail, but that's pretty easy to prevent by using a fresher Fedora Core S. As for upgrades, right, we don't use native Core OS mechanism. We upgrade from one major version to the other, so it might not even span Fedora releases at all, but in the worst case scenario it's Fedora 33 to 34 and we can also pull out the edge to prevent that upgrade from happening if we find some issues with that. So, yeah, I don't think that would affect us. I just wanted to bring that up in case it did and at least we're aware of that which I think is a significant change because there are people going between both groups and sort of playing with F cost and playing with OKD at the same time. In the last few minutes we have seven minutes left and we'll talk about the KubeCon office hour. What did we learn from that in terms of our audience, in terms of our ability to communicate our ideas, our ability to answer questions, how do folks think that came up? For those that were there, for folks that haven't, we can put the link to the video which was posted. For me, I had big problems to follow the correct chats because there were lots of chats and Q&A chats and main chat and background chat. I think it's a little bit too much. I don't know what's your impression? I think that's why they have a moderating person to sort of sift through the questions for us, right? Yeah, I was there are a lot of new people following the Twitch chat was apparently. Go ahead, Vadim. Yeah, I was following the Twitch chat and apparently had copies from everywhere, at least from YouTube, but following the moderator was apparently a bad idea because they know how to switch topics and slowly move from one topic to the other so you wouldn't have a whole mess of different chats. My impression there was that it was great except when folks started with what's coming in 48 and 49, which are very technical issues. We shouldn't have to answer them, but we should have a prepared answer like here is where we post the release notes. Here are the links to our workgroup meetings and so on. I think I would add some more discussions about that it's not just a free version of OCP which is not true, but it's rather a community version where you can affect every single detail of your OCD cluster. Folks were asking why you're not starting with RHEL CoreOS. That's exactly the reason because the community cannot contribute to it directly. They would have to go all the way from upstream to Fedora to RHEL and that shows the value if you found a bug in it, you don't have to wait for RHEL support to pass it to engineers, have it fixed and pass it back. You can start syncing with it immediately just like we did a lot of times. The next suggestion is probably mostly for internal developers, but we should mention that we did a lot of things which landed in OCP. The whole Ignition version 3 started in OCD and later only based on a bunch of fixes all of us have submitted landed in OCP. The whole OVN as a default was a great testing platform for the folks to decide should it be a default as at the end or not. That means you might hit some more bugs, yes, but that also means you also get a feeling of how the distribution would look in a couple of years. The whole C-group is a perfect example. We might want to enable this in OCD if it works great, if it brings benefit to the community because OCP is more conservative and we have our hands on time to do whatever. A complex topic is because folks might think that we test new features on them. That's not entirely true. That's a very complicated topic, but once we should actually make a point of it that OCD is a place where you can get latest and greatest features and since the whole community is looking at it, your chances to have them fixed sooner are actually multiplying. But other than that, I think it was great. It felt refreshing to see all of the new faces asking questions, both the beginner ones and more complex ones. It feels like the community is actually growing and OCD is not even one year yet. OCD for me. So that felt very rewarding. I thought one thing is that we'll have to find, this is assuming that it moves forward. Diane was saying that if it went well, that we had the chance of doing like a bi-weekly. I think that would be fantastic. I haven't heard back if that's the case. One thing I think we would want to do is find, what's the right level of support to provide in these office hours? Are we going to start looking at people's logs? We got a question along those lines of like, here's a big log error. Are we going to start looking at that? We'll have to figure out what's the threshold low and high for saying, okay, this needs to happen offline from the show because otherwise it would take up a significant amount of time on this one particular issue and we wouldn't get to anyone else. So that would be my only thought. Anyone else? I guess, well, I don't know, bi-weekly might be a little bit too much for the office hour, but certainly not up to me to decide. But yeah, we could maybe monthly or something like that. And well, I'm not sure office hours are great for debugging session either. Because they'll just pin down a lot of people for just one issue, one specific issue. Yeah. I'm not really in favor of that, but yeah, it's still open for questions. Anyone else? Yeah, I think live debugging is a little chancey. All right, we have one minute left and I do want to be mindful of people's time. Is there anything else that folks want to bring to our attention before we step away from this meeting? Well, thank you so much folks for your time. Thank you, Jamie, for lending you the meeting. Good meeting, Jamie. You're welcome. And if folks like this format, then we can mention it to Diane. I'm happy to facilitate in the future. I don't know what's behind that, but she might be interested in letting me co-chair or whatever for it will see. I don't know if it has to be a Red Hat person or not, but this was great. And we'll talk in two weeks and also online and use the discussions. And don't forget the docs meeting is next Tuesday if you're interested in doc stuff. All right, take care.


What's up everybody, Jason here for jaspyskatesbrates.com, we're giving away three hip parade random hip spots away with this .22 and .21 bombing crumb light baseball one pack break, random teams number three. And again guys, first we do the break, we randomize our customer names and teams. Everybody gets a random team per spot, then we do the break, which is the one pack here, distribute the hits out. Then at the end of the break we'll take all three customer names, randomize them in the top three names each, get a spot in the hip parade, a random hip break, which is right up here, which is a three case, and again, everybody gets a random hit, and you get two random hits per case, per spot as well. So we actually took out five spots and we're giving away to the customers that actually bought in. We have a chance to win up to five spots, so what we're going to do is bring in the same dice roller here for the customer names to win five spots, and we'll add the five customer names here, then we'll randomize the customer names, and then the teams do the pack filler, and then we'll add the customer names here and see who gets those spots at the end of the break. So dice roll it, and here are the customers here, three to two, five times, top five get an extra spot for three, one, two, three, four, five, boom. Joe, Chris, Candy, Foud, and Zach, congratulations. All right, five times on the customer names and teams to do the break, one, two, three, four, five. Roy, Donna, Steve, Birch, five times, one, two, three, four, five. All right, guys, so there you go, let me quickly actually out of this. All right, so quickly look at your names, teams, and then we'll do the break. All right, guys, so let's close the trade window and do the break. So we have a little Bowman light pack, Kevin Newman, Kronoworth rookie, Austin Hendrick, Passus, Jeremy Penney. All right, let's switch teams, and again, let's give away the spots here, so three spots we're giving away, guys. Top three get in, let's roll it, six and a four, ten times, good luck, one, two, three, four, five, six, seven, eight, nine, and tenth and final time. Chris Walker, Jarrett, and Robert Wolfe, congratulations, top three get in. Again, I believe we have to do a couple more of these, but we're inching closer at ways to get in that breakdown, guys. I really appreciate the Jaspies case breaks.com.


So I'm sure this is different for everybody, but for me the hardest part about clinical year Wasn't the endless studying or the pressure to know lots and lots of things It was not having a place to call home for a whole year not being in the same place for a whole year Now I'm gonna get a little psychological maybe a little bit philosophical, but you're watching one of my videos So you know this happens sometimes According to Tai East Gibson, who's an absolutely brilliant woman and the founder of the personal development school Which I can't say enough good things about According to her and also Tony Robbins We struggle in life We feel pain and we feel difficulty when our personality needs are not met and we all have the same six personality needs love and connection Certainty uncertainty contribution significance and growth, but we all have unique personalities So we need these things in different ways and in different amounts for me Certainty is my biggest personality need things that make me feel safe Secure comfortable. They make me really happy and content So just as an example for me personally when I don't know where my next paycheck is coming from or if I don't know Where I'm sleeping tonight I get anxious and really motivated to solve the problem and make a plan like one time I ended up without a job because I quit my scribe job to go work somewhere better But the new place ended up restructuring or something like that and they weren't able to hire me anymore And of course they told me last minute after I had already quit the scribe job So I was out of luck. I was without a job. I Hardcore panicked and spent all day and night sending out resumes applying to jobs online Calling doctors offices just looking for a job Because I just couldn't bear the thought of not having a paycheck for like five minutes and because I called and applied to so Many different places I ended up getting a medical assistant job within like two days Which was good, but those two days were tough So the point is I don't do well with too much uncertainty and for me having to pack up all my things Load up the rev for rent a trailer and then go move into a new place every five weeks during clinical year has been really tough Now thankfully most of my rotations have been here in Syracuse, but they were pretty sporadic So like I would have one in Syracuse and then I'd have one in like Utica Which is an hour and a half away and I ended up staying in Utica instead of living in Syracuse and doing like an hour and a half Commute, which was just too much But even though a lot of my rotations were in the same place That was still uncertain until about two to three weeks before the rotation would start So I wouldn't be able to make a concrete plan and rent one place for a long time So I still ended up moving because I just didn't know for sure where I was gonna be and just all the moving the packing Unpacking living in different houses living in different areas living with different people in addition to studying tons of information Getting used to different work schedules different office environments meeting new people at work all that kind of stuff was just a lot of Change and that was something that was pretty tough on me And I know this now Settling into the house that I just rented Which is this house and this is the house that I rented for my last rotation But because I'm taking a job here in Syracuse after this rotation is over once I graduate from PA school What I ended up doing is I actually signed a year-long lease for this place because I'll be here for the foreseeable future Minus some time in September and October when I'll be traveling. So I bought a bed. I bought a dresser I bought a freaking comforter I actually picked out like some color themes and decorations and like how I actually want my life to be and I was just laying there this Morning feeling just unbelievably content and happy and that's where the motivation for this video came from Sometimes you don't realize how hard some things are for you until the struggle is over and you've passed it and you've surpassed it And then you're looking back and you have something to compare it to and so now knowing that I'll be living here for at least the next year I have my own room with my own furniture and a garage. I've got a regular gym I've got a regular local coffee shop and I can actually make some like friends and connections and put down roots Which is just an awesome awesome feeling and it's made me realize how hard this last year has actually been for me Now some people who love traveling love meeting new people and that just really drives them and energizes them They might really like this aspect of clinical here. This might be a positive thing for those people I'm just sharing my experience as someone who really prefers stability now. I do love novelty I do love traveling and having new experiences meeting new people, but over the last 10 years I've just been in so many new settings new cities new jobs meeting so many new people doing so many new things in College and then in the Navy and then post back and then working and then PA school that I'm just kind of done And like I said in my last video where I told you about the new job I got I'm just really stoked to finally have some stability for the first time in my life in a long time And I'm just super grateful and happy that it's finally here or at least it's coming soon So alright guys, thank you for watching Thank you for emailing me all your amazing stories if you're a PA student medical student nursing student Or even like an undergrad or any other kind of student comment below Let me know what the hardest part of your training is. Is it the academics? Is it being away from home for the first time? What is it? I'd love to know. See you in the next video


I would say the ayahuasca journey was probably very instrumental in how I sort of went from the rock star, rock artist that was concerned about whether I had a hit on my album or was I going to be in the charts and was I going to be this or that. And plant medicine really gave me a place to let that go and to just enjoy my art and to trust and believe that what's coming from me is what I need to share with people and other people will respond to that because that connection that each of us have as humans.