Hello everybody, welcome to the cooking series recipe for the cure. I'm Robin McConnell and this is my sous chef and my friend and my coworker, Pam Stoffberg. We're both oncology dieticians at the John Thorough Cancer Center at Hackensack University Medical Center and we're joining you from our beautiful cooking studio here in the Cancer Center. Since we can't do our regular cooking studio programs in person, we were doing them weekly for the last 11 years actually, we're so excited to be able to join you virtually and continue the tradition of sharing delicious and nourishing recipes with all of you. So we want to give a special shout out to ASI for sponsoring this new program, we would not have been able to do it without you. So all of the information that you need, the recipes, the shopping lists and the nutrition information to cook along with us or if you want to take it and you know, do these recipes a little bit later are available in your confirmation email or in the link below. So what do you say we get cooking? Okay, so thank you for helping me out today, Pam.  We've been doing this for a lot of years together, yes. So the recipe today is called salmon zucchini burgers and we're actually using a little bit more than zucchini, we're going to be using zucchini and also yellow squash. So we use this a lot and actually we've used this in a previous recipe in our cooking studio in a meatloaf that was made with turkey. So we're going to kind of take that same theme and we're going to add it to salmon burgers. And where this recipe came from is there's a really wonderful catering operation in my town and back in the day when we just got our cooking studio going, we were always looking for professional chefs and you know, local businesses to come in and demonstrate something that they really, you know, feel proud of. And I have been buying their salmon burgers for many years and the light bulb went off in my head saying salmon is a healthy food. I love these salmon burgers and I do remember that they were a very colorful burger so they had zucchini in them, they had yellow squash in them, there was something red in them, I wasn't quite sure what it was but I love them, they were delicious. I hounded that poor store owner to please come and do a cooking studio program and you know, I get it, it's not for everybody but you know, he politely declined and I politely walked away but I wasn't done with these salmon recipes yet. So I kept buying the salmon burgers and decided I'm going to figure out how to make these and we're going to do these in our cooking studio. So that's how this recipe came about. So I'm going to get started because they do take a little bit of time to cook. So as I mentioned, it's a very colorful burger and any time that you can stretch something out, you know, salmon is expensive and if you can stretch it out with some vegetables it's a double bonus because we're getting added nutrition, we're getting some additional color. Again, it's a very, very pretty dish. So I'm going to shred the vegetables, it's not you know, a hard and fast recipe either. So it's about a cup and a half of shredded squash, I'll call them. So we'll do some of that and some of the zucchini. You want to make sure that you're getting plenty of the skin because not only is that where the fiber and many of the nutrients reside but it is also where the color is and that's what makes everything so pretty. Now the thing about zucchini is that it's a very wet vegetable. So that does not do well in our burgers. So what we have to do is take the zucchini and the squash and I'm just going to put them in. This is a very, very fine, you could use cheesecloth, you could use unbleached muslin. This was a towel actually that I, it was very light, I actually use these towels to line my bread baskets when I'm doing my sourdough bread. And so you just want to gather it up and don't be shy but you want to really ring it out and you can see a little bit of bicep and tricep work out here. You want to really ring out as much of the water as you possibly can. Now don't throw this away because I have a bucket that I keep in my freezer, a plastic bucket that I use to put all of these vegetable juices in. I'm just going to let this sit here for a little bit. Let's wash my hands quick. I think the use of the squashes though, like you said that they were moist, excuse me, they are, but I think that they're also nice and soft unlike say a carrot that goes, it doesn't change the texture as compared to the salmon. So I think that that's like a lovely play. Right, and you wouldn't necessarily see the carrot in the salmon burger because we're using orange, you know. So but yes, it's great. So hold on to your juices, pour them into your bucket in your freezer and then when you're ready to make soup, you've got some stock. So we're going to start here. I have just a little bit of olive oil in the pan, and we're going to let that get. So we just want to soften the vegetables a little bit. So I have a small onion, I might not use all of this. So we want to just get some of the onion in there. And I will say that though I was not able to get the recipe from my local shop, I did ask him a number of pointed questions because I was curious to see, you know, what was in it and get as close as possible because I'm inventive but not that inventive. So this is actually some sun-dried, not sun-dried tomatoes. It's a roasted red pepper and I just bought a jar. And I usually keep a small jar in the, you know, in my cupboard just for such application. So I think this takes about two tablespoons of sun-dried tomato, I mean of roasted red pepper. So I'm going to cut those up, get them a little bit smaller. Add a little bit of garlic, so about a clove or a teaspoon if you're using chopped. And then you always want to be careful. You never add the garlic first to the pan unless you really want to crunch them because garlic can burn very easily and it's nice to have that little bit of a buffer. So you can already start to see that we're building a little bit of color. So I'm going to give this one quick squeeze again. More is coming out. Yeah. Now you can see that it's very colorful. So as I said, I kind of commandeered this recipe but the more times I made them just still wasn't coming out the same and I knew that there was something missing and that something missing I discovered was old bay seasoning. And it's a proprietary formula if you look online, it's hard to find the exact ingredients to it but the spices are spices and herbs including so it's red pepper and black pepper, salt and paprika. They also make a blackened version of it which I thought would be really, really nice if you wanted something like maybe with a little bit of heat because you can change this up a little bit. This old bay is absolutely the flavor of the Chesapeake Bay. That's where it's kind of originated and any fish restaurant that you would walk into down in Annapolis or the Baltimore area, it absolutely hits you in the face and you're like, ah, fish, delicious. No, it's like a crab cake, couldn't even be a crab cake on that old bay seasoning. All right, so our salmon today is, it's actually a sockeye, it's a previously frozen. So the nice thing about salmon is that we really can get them, can get salmon in many different forms so you don't have to be concerned. But I've actually made this from frozen salmon that I defrosted and it came out just as nice. So what we're going to do here is just cut this into like one inch cubes and then we're going to get our food processor out but we were lucky enough to have the skin removed. Yes, thank you for pointing that out. So the skin is not actually difficult to remove but you want to know something, it's so much easier to do it. It is pretty easy to remove it but yes, I did take the skin out and you just also want to run your finger along the spine here just to make sure that there are no little bones that are there. Cut these up and give the food processor a little bit of help. And the key here is to, we want to pulse it so we want chunks, we want to be able to see the salmon I think is the key message here, we want to be, we don't want puree and we don't want pâté so we want chunks so we'll get the food processor going so you can count along with me. If I say I'm going to pulse it all right, count with me so we've got one and then open it and look at it. One more time. This is good so again we want the vegetables to be slightly translucent, soft but not mush. Oh yes, actually I'm going to saute them. Okay so you can see the beautiful color that we have in here and then we are going to add the salmon and already you can see the beautiful orange and this sockeye is particularly orange which is really really nice. Okay I love this recipe because there is no starchy filler in it. Basically what you see is what you get in terms of, let me just get this started here. So this is the recipe except I've got the old bay and I really do think it makes a difference. It's a terrific seasoning and it just, it just wakes it up. So as I was making this I thought to myself well this is very Chesapeake Bay you know it's very crab cakey but I also thought this would be really nice if you wanted to make it a little bit more Mediterranean you could actually use those roasted red peppers in there instead of the, no you could use the sun dried tomatoes instead of the roasted red peppers and then it would give it you know a little bit more umami flavor I think. You could also do an Asian version of this by adding some chopped ginger, you could put a little bit of soy in there, a little bit of sesame oil, I think would be really nice. Salmon and those Asian flavors are delicious together. So this makes about six burgers so it takes a pound and a quarter of salmon which makes each salmon cake about you know three and a third, three and a half ounces which is perfect because that also gives a really nice punch of Omega 3 fatty acids and we'll talk a little bit more about that later. So so like with the meatloaf recipe that we made we don't want to pack these burgers because we do want them to be soft and we need to let the pan and the little bit of oil so I am using some canola oil in here and we want the pan to be hot because we want the um we do want the salmon burger to just sizzle a little bit in there but we're not frying it so I'm just putting a little bit of oil in there and I am using our beautiful non-stick pans here. It's hard to find non-stick pans that work well on these induction burners and then we're going to take a third of a cup just kind of simulate a patty so we'll get them right in the pan you see here that's sizzle and the fat from the salmon is going to hold it together sometimes it's easier just to put them down and we can press them and then once you put them in the pan resist the urge to move them because we definitely want to have that sizzle on the bottom and that's what holds them together and makes it possible to flip them. It looks nice. So one of the things that we are encouraged to eat more of is fatty fish. So I happen to love fatty fish, I love salmon, I love sardines, sardines people either love them or hate them they either make a face when I suggest it or they're like yeah I love them too so you know this is just another recipe to improve fatty fish intake. So yes and the dietary guidelines the 2020-2025 dietary guidelines came out in March not March in November and it's really a pretty remarkable document and they do look at not only where we need to be in terms of our diets but where we are as Americans in terms of our diets and in terms of our protein intake so they define protein intake into three categories so we have our meat we have our poultry and we have our eggs and then the second category is seafood and then the third category is our plant-based protein so that's our nuts, seeds and soy-based products and the we do pretty well in terms of the meat, the poultry and the eggs Americans about 70% of Americans eat what is recommended in terms of those types of meats but in terms of fish only 10% of Americans eat the recommended amount which is 8 ounces in a week so you know you're getting one serving up here and that is about 2 grams of omega-3 fatty acids and these are what we call our fish oils so these are the oils that help with heart disease that can reduce blood pressure can reduce LDL cholesterol can reduce triglycerides but also in terms of cancer prevention it's people who eat more fatty fish or more omega-3 fatty acids can also reduce the risk of coherectal breast and in particular some of the liquid tumors such as leukemia and multiple myeloma so you know it's just a win-win situation so we sort of have like a whole meal including you know vegetables and our proteins all in one meal so do you want to yeah I'm gonna start with suckatash I'm not so sure if Robin told you that that's what that's the other dish we're making today oh my goodness yeah it's okay it's called herbs corn and edamame suckatash so suckatash is corn and lima beans so this is a riff on that a modernization of that I happen to love suckatash I love edamame I love corn and and the red pepper gives it such a just a nice color I'm not promoting overly promoting Trader Joe's but they have a very nice product and it's called soy catash and it is what we're making here today it's the soy edamame and corn and a little red pepper and onion and it's ready to go so that's like super handy and you could buy the edamame in many many different forms we just happen to get it in the pods yeah and steam them right in the bag and squeeze them out Pam's gonna demonstrate how they look and I'm gonna flip my burgers I just want to say as you're getting that in there you want to look around the edges here and when you start to see them the color coming out of them you get a sense that they're about ready to flip so I'm just gonna look and I want just a little bit of color on the bottom so I always thought that suckatash was a southern dish you know from the south I was doing a little bit of reading and actually it's a Native American dish and they think that as opposed to you know that let's face it there was no mashed potatoes and apple pie at the first Thanksgiving right but they they they are they feel quite short that there was suckatash or some sort of mix of corn and bean at the first Thanksgiving cranberry beans are very popular in New England and they for and they grow there well and they thought that that probably was what it was so suckatash just refers to any corn with a bean product at all so and then I think it traveled from colonial New England down to the southern states and you know kind of also took on a life of its own there there's many riffs on this this is a modern rip because we're using the edamame so here they're so easy look we got some steamed and you just steam them and then you push out the beans they pop oh see they pop right out they're popping all over we weren't chasing them all over really we were so they're just coming right out they're easy actually you know what this fun thing for kids they would love to do this that would be a great way to get them involved in prepping absolute and then you get them to pick up the ones that fall over that would be helpful too but anyway it's not hard at all kind of fun and they're a really nice color and they do I mean I think you would mistake them for lima beans they look almost exactly like lima beans are a little bit flatter but I think the color I'd like the color of them I think the color is a little bit brighter and edamame is an excellent source of protein and iron non-heamed iron so that's non-meat iron and again that's pretty pretty important for vegetarians so this is a great product and not only that it has calcium vitamin C iron folate and potassium and it has 18 grams of protein in in a cup and that is a lot that's a lot this is a very high protein meal in general this is a very high protein meal but a healthy one one that features you know the omega through fatty acids from the fish and more protein but from a plant-based perspective so you know you can't get any better than this all right I think this is ready I'm going to add in the garlic now and we want to keep a little bit of crunch absolutely when I was growing up in high school and in college my early years in college I worked in a nursing home and they had a three week cycle menu and succotash was on the menu every third Wednesday and nobody would eat succotash like it just looked awful it never looked like the beautiful dish that this is going to become so that's why you know it's kind of nice as foods evolved and you know when how long has it been that you've been able to find edamame in the grocery stores in the frozen section it's kind of like the Zatar you know we're becoming a very very globally you know nutritious nutrition conscious society and it's nice to introduce yeah the different flavors and the different products so it's a it's a nice thing so I just add the corn now I'm adding the edamame it is pretty when escaped get in there oh I think that is prettier than lima beans although I will say that lima beans that you find in you know cans or in the frozen section is nothing like the lima bean that you can grow in your garden they actually are when you pick up fresh lima beans young and not starchy they are sweet it's like candy kind of like peas I am I love peas in my garden it's my favorite part of the garden I think you could buy zucchini and you could buy you know corn in various farm stands but it's really hard to find fresh peas and that is just you know such a nice part of starting a garden and you know seeing what grows what works what doesn't work from year to year what I just added was a little bit of water and a little bit of rice vinegar this is just gonna help it cook for a short amount of time okay so I'm going to take my my uncooked salmon away my cutting board away and I'm going to take my burgers off and then this gets a sauce with it so that's almost ready but this gets a lemon dill sauce with it so kind of like on a burger you would put some ketchup maybe with this this is the ketchup for this I was thinking with with the if we did you know this in more Asian flavors that would be nice to have a wasabi mayo with it you know to add a little bit of that would be good and that actually would be another great thing to add to this is maybe a little bit of red pepper flake so I'm just taking some fresh dill and I'm going to chop that up before I get my cutting board going so this is just another colorful addition we have and then for awesome flavor I'm just going to put a little bit of lemon zest in there so you get the oils you get the just the essential essence of the lemon that just makes this pop completely and I'm going to take some of our fresh basil and those are parsley chop that up and put it in as a finishing should be great this is like our little farm to table here so fun we have a beautiful rooftop garden on the second floor of the cancer center that we have a very generous volunteers plant and maintain for us and we are so fortunate to be able to go up there get the fresh herbs that we need to get the fresh vegetables we usually have plenty of herbs it's a very Mediterranean climate up there so our egg plants just grow beautifully the peppers grow beautifully our cucumbers grow beautifully and it's it's just such a lovely place for our patients to be able to go and kind of get away from you know just the treatment aspects to have some place to go where they can feel healthy where they can feel well where they could feel healed and I just think it's it's lovely I am going to put a little bit of salt in this is that good I'm gonna make sure I have everything in oops I almost forgot the garlic a little bit of garlic I think I want to taste it just looks so good I actually made a lot of succotash this summer last summer the the the corn was so fantastic I used to grow corn myself but I just found that it was too I couldn't handle getting you know 50 or 70 years all at once it was just nice to be able to go to the farm stand and buy the six years that you know I was going to um you know eat for that meal and it was just really nice and I could get different varieties at different times of the summer this is so wonderful with fresh corn I think that frozen corn that we had today I've you know I can't I can't do without the corn but man definitely make this with fresh corn it is so snappy and so um so wonderful it's pretty I think that's I think it's pretty good I like the crunch to it don't you yes I just keep thinking back to the uh the succotash that I had at the nursing home and this is just so much so much more lovely this is a beautiful dish yeah so I just wanted to say one more thing about um salmon so salmon is uh also one of those sustainable um fishes that is it's something that we have to consider you know it's a big world to feed and it's difficult to you know it's we want to make sure that the food that we're eating is also sustainable um and it's environmentally friendly so all of the vegetables that we have have a much much lower carbon footprint so the health of our bodies is so tied to the health of our environment and it's just so amazing how those two things fit together that what's good for our bodies is also healthy for the environment to grow that to reduce our carbon footprint so with the fish there is a really terrific organization called the Monterey Bay Aquarium and they do a seafood watch and they print I guess every six months this one I just downloaded this online they have different consumer guides for different areas of the country so this particular one is is for the northeast that's where we are and it's good for January through June and they really just look at sustainable fishing practices but also in terms of farm raised fish about 80 percent of the salmon that we eat in this country is farm raised and there's nothing wrong with that if you're eating wild though in terms of sustainability you want to I think it's nice to check this list so salmon on here in terms of best choices they have New Zealand salmon and so that's you know something that you might want to look at and then also good alternatives would be Atlantic salmon that comes from the Pacific Northwest from the West Coast basically and that can also be farm raised so I just wanted to point that out that you know it's important that we get our omega 3 fatty acids but we also want to be responsible to make sure that tomorrow you know we can feed our families our grandchildren our great grandchildren so I think I'm going to plate this what do you think absolutely so I think we'll start here we have a lovely whole grain roll and I'm going to take a patty and I just wanted to kind of point out I don't want to over touch it but you see how firm it is and all I did was press it into the pan but it holds together beautifully all on its own there's no filler in there there's no bread crumb there's no rice there's no right the protein of the of the salmon just seizes up itself and just holds it together we're gonna put just a little dollop and what herbs did you use in here I used basil and I used parsley okay so hold on one minute hold on one you're gonna dress yours I'm dressing mine I'm not coming to the party undressed it gets lost a little bit but there you go still yummy so here we go so we want to thank you for joining us thank you thank you so I want to I want to thank you for joining us we had a lot of fun doing this I miss the cooking studio don't you I do too I miss I miss it terribly but I also miss all of our you know our patients and caregivers and staff that stopped by it was it was it's a I hope that it's a warm and welcoming place we love to share food we love to talk about nutrition but we also like to share and it's a it's a nice it was a nice bonus for us to be gifted this so check for future events and we want to make sure that we thank again our sponsor ASI they just made all of this possible for us and it's it's just good to be able to share good food nutritious food and the warmth that we feel for all of you so thank you


And joined by James Harden right now after a 38 point 11 rebound 13 assists effort against this temple's team James, what did it take down the stretch? The temple was refighting. Where did it take to hold them off? Man, I got to be better especially down a stretch, you know, we turn the basket all over a Few times which gave them opportunities to be able to score So we got to do a better job including myself. I'm at the point guard of not turning the basket ball over getting the quality shot So we can have a good chance in regard to defensively What is the key to this team as far as managing expectations? Obviously, there's high hopes expectations for this team But what is the key in terms of managing the expectations to keep in the goal in mind?  So we got to be prepared You know, you know soda for record wise isn't that great, but you know, they gave us a fight So we got to prepare mentally and physically every single night to win games No matter how they come and tonight was one of those examples You told me one things you're excited about here in Brooklyn was playing in front of these fans I don't know if you can hear the MVP chance. How fun is it playing in front of the Brooklyn faithful, man? I can't wait to I can't wait to it's packed out in here, you know There's some of the best fans in the world, so I'm excited about it But until then we got to continue to keep winning and keep going 12th triple double of the season for James Hardin James Thanks as always for the time


Frontier Fighters. Frontier Fighters. Dramatic incidents in the lives and careers of those fearless trailblazers who brought eternal glory to the Empire of the Northwest. In 1849, Abraham Lincoln's term in Congress had just expired. He was hourly growing in the esteem of his countrymen. Had taken an active part in the campaign, which resulted in Zachary Taylor's election to the presidency. A newly sworn president called Lincoln to the White House to offer him a high office. Lincoln was certain it was the office of commissioner of the general land office and in the president's office one day. Good morning, Mr. President. Lincoln, I'm happy to see you. Please accept my thanks for your very active part in behalf of my campaign. And now that the country is saved for another four years, we can get on the business. That reminds me a little bit of a story, Mr. President. Well, there you go again. My wife warned me against inflicting my brand of humor on the president of these United States. Well, you don't, of course, have to tell Mrs. Lincoln that you told me a story. Well, bless my soul, I don't do that.  Not at all. Well, Mr. President, I was riding through the woods one day back in Illinois when I saw a lady approaching. I ran my horse and waited for her to pass. She checked her horse to stop and after looking me over and a curious sort of way finally broke out with, well, for land, say, you're the homeliest man I ever saw. Yes, Mama says, but I can't help that. No, she said, I suppose not, but you might stay at home. Oh, Lincoln, Lincoln, if you can combine your qualities as a humorist with certain other qualities as a politician, I think you'll make an excellent governor of the territory of Oregon. I reckon my hearing is out of whack, Mr. President. Did you say governor of Oregon? Yes, Lincoln, I did. The appointment of commissioner of the general land office is too obscure for a man of your talent. Well, Mr. President, there's a little woman back home who's mighty afraid of getting too far away from the center of population. I can just hear Mary Lincoln asking me to decline with thanks. Mr. President, Oregon has just lost a governor, but that's just between us. Lincoln, I'm genuinely sorry. Well, maybe I'll never get another presidential appointment, but it wouldn't do to get Mary riled up now, would it? Besides my friend J.P. Gaines is a good man, and I think he'd like to go to Oregon. J.P. Gaines did become governor of Oregon and was sworn into office on August 18th, 1850. With each year now, this empire of the Northwest took on a greater significance. The southern Oregon military road was built. The steamboat line was established between Astoria and Oregon City. The Willamette and Rogue River valleys became populous, and now a new trail was to be blazed from port offered on the coast to Jacksonville. On the 10th of June, 1851, nine men landed for the steam coaster Seagull. The Clicquatad Indians, always hostile to the whites, saw in this small landing party an opportunity to stop the white man from further colonizing their lands. The red men waited for the Seagull to leave, and then demanded of the nine men, Indians say to pale face, go now or die. But where can we go? Our ship sailed an hour ago. Then let pale face make his home in ocean with fish. If he cannot breathe air, let him breathe water and drown. Wait. Let us continue as brothers until morning. Then we will take our choice between becoming your prisoners or walking out into the ocean. So let it be. But between us there never can pass pale face. Only Tomahawk. Well, Captain, what are we going to do now? We're nine against a hundred. See that great rock there rising out of the water? Yeah, but the minute we make a dash, those red devils will come out of the woods and cut us to pieces. But we're not going to make a dash for that rock until it's dark. It's our good fortune that we took the ship's signal gun with us. One cannon well-mounted and nine rifles. Captain Peters has looked that rock over and on top of it. There's a small clump of trees. A perfect blind for our cannon. Good. In the morning we'll reveal our position to them. Wait until they've charged the rock and gotten within 50 feet of our cannon. I don't think we'll have to choose between either the ocean or the Tomahawk. They've discovered us, Captain. Good. Jim, is the cannon loaded? It's up to the muscle. Great job, Captain Peters. Rifles in position. They're coming up the trail now. Hold your fire until we see what effect our cannon will have. Yes, sir. Well, it looks like a pair of faces.  Hold your fire, men. They're 100 feet away. 75. They're going to charge, Captain Peters. And I'm going to fire. Give it to them, Jim. But gushes are into eternity. That great shot sure did the trick. Look, get them engines run. And I hope they keep running. Because that was the last of the great shot from our cannon. Nine brave men finally reached their destination. And the example they set heartened the other pioneers in a concerted effort against the hostile Indians. After three decisive battles, a treaty was finally signed in 1856. And Rogue River Valley once again was safe for those men and women who wished to make it their home. When word reached Oregon that Lincoln had been elected, the majority rejoiced. Two years before, Oregon had been admitted into the Union, adding to our flag the 33rd Star. Then with the approach of the Civil War, American promoters drifted into Oregon, and laid a scheme almost as deep as the one conceived by Aaron Burr. Working undercover, the schemers plotted to establish another republic within the borders of the United States. In the north and south split, the United States of America will be divided into three republics. Three republics? How do you figure that? Confederate States of America, the United States of America, and the Pacific States of America, or Pacific Republic. Johnson, that's treason. You remember what happened to Aaron Burr? I'm not going to fail. Well, I'm pulling out of this scheme. I'm willing to earn a little easy money, get some land, maybe dabble in politics, but I ain't sticking out my neck like that. No, sir. Now listen, Frank, we all got to stick together in this. Well, you count me out. If he gets word of this to Governor Whitaker, he ain't going to get word to anybody.  The war between the states is coming to sure as anything. In America, there'll be three republics, and I'm going to rule one of them. As the conspirators predicted, the war between the states became a horrible reality. The Oregon Patriots dedicated their lives to the Union, but the scheme of a Pacific Republic attracted more and more followers each month. First, it was a story that was only whispered about. Then the conspirators became more bold and argued its treasonous points loudly. Talk of a republic in the West spread throughout the states of the Pacific Coast, and now Governor Whitaker felt it was time to take action. If such a scheme succeeded and dependent money were diverted away from the North, the government of Abraham Lincoln might fall, and we would become a nation ready to fall an easy prey to the first enemy from over the sea. In a meeting, the governor said to his lieutenant, John, there must be no more thought of a divided West than a divided Union. I'm afraid, Mr. Governor, that this wild talk has caught on. The sentiment seems to be growing throughout the entire West. Entire ideas, preposterous. It's so foreign to our instincts, our sense of fair play. One of their handbills, printed only heaven knows where, came into my hand. Listen to this. The Pacific Republic will be an aristocracy somewhat similar to the ancient Republic of Venice, which, while providing for an elective executive, will vest all its powers in hereditary nobles. That certainly repudiates universal suffrage. It's positively fantastic and more. All labor will be performed by a class of people from many of the dark races. Coolies, South Sea Islanders, mulattoes and negroes. That, of course, means slavery in the Southwest. I don't intend to stand idly by and see this nightmare grow into any demon of reality. Mr. Governor, urgent dispatchers from President Lincoln. Oh, thank you. Well, John, bad news travels fast. The President is experiencing considerable alarm. His question is, what if men and money are cut off from the federal government? This is a critical time for the Union. Mr. Governor. Yes. The sons of the Pacific Republic have posted handbills. They're going to hold a monster mass meeting in a torchlight parade. Every one of those handbills will be torn down. And no torchlight parade or mass meeting will be tolerated in the capital of Oregon. You can only stop this movement now by force, Mr. Governor. No force will be used, John. In time of war, any overdacted against the federal government is rebelled. And I intend to speak to... Governor, look! They're on the march quicker than we thought, Mr. Governor. The men and a few women, too. They're headed for the town hall. John, get your hat. Order an escort, please. Looks like we're all going in the same direction. I give you the leader of this movement to establish a republic in the West. And I give you the man in whom is vested the authority of the federal government, the duly elected representative of the majority of citizens in Oregon, a man who has sworn to uphold and enforce the laws of the state and the Constitution of the United States of America, our Governor, Mr. John Whitaker. Thank you. I have only a few words to say to you. First, the command to those true sons of Oregon wearing the uniform of the United States Army. Captain, arrest the leader of those forces who call themselves the sons of the Pacific Republic. An arrest waits for every man who swears allegiance to any flag other than the stars and the stripes. I have sworn to uphold law and order in Oregon. I shall not violate that oath. I order each and every one of you to disband. Failure to do so means arrest.  For the next 48 hours, I, John Whitaker, declare Oregon to be in a state of martial law. Thanks to the timely action of Governor Whitaker and the native idealism of the majority of those patriotic citizens of Oregon, the dream of a Pacific Republic vanished. Had action against such a movement, both in Oregon and California been less vigorous, had the supply of men and gold stop pouring into the nation's capital, the Union may have been in grave danger. Thanks to those famous frontier fighters, whether fighting on the trail or in the governor's chair, the West today is part of the United States because of their daring and idealism.


This is stock number 10021. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. Today, we are checking out this super clean 2012 Chevy Silverado 3500 crew cab long box dual rear wheel. This truck has the 6.6 liter Duramax diesel with the LML motor which pumps out 397 horsepower. From this HD video, you will be able to tell just how clean this truck is all the way around inside and out. We shoot all of our videos in 1080p. So if you have HD capabilities on your computer, tablet, or a smartphone device, turn them on right now because it's like you're right here looking at the truck with me and definitely your best way to check out the vehicle without actually being here. So you can make a smart buying decision from the comfort of your own home. This one comes with polished aluminum alloy rims. These are 17-inch rims and it has brand new Goodyear Wrangler Trail Runner AT tires. These are LT 235 80R 17s. You can see it is still have the little markings from when they were produced. Some brand new tires on the front, brand new tires on the back. Six brand new tires, frame and underbody is very clean. Summit white is the color. No dents or dings on that front fender. Headlight lenses are nice and clear. The hood is in excellent condition. Passenger side fender is in excellent shape as well. I didn't see any dents or dings. A couple of water spots which came right off. But very very nice. Lower valance is in nice shape. Passenger side rim, no scuffs or major scrapes on that. And as you go down this side of the truck you can see just how clean the body is. How reflective and mirror like that paint is. We take these HD videos. Whether you're far away or if you're close by and just can't make the trip down. You can still see the truck, hear the truck, have the confidence in the vehicle that you're looking at. Before you even get here so you can make a smart buying decision from the comfort of your own home. Cab is in excellent shape. Didn't see any dents or dings on those doors. The Dewey Tub has got the 3M protector on it so that's in nice shape. Polished aluminum rim in the back is in excellent shape and these back tires are brand new as well. All the tread left put those on in our safety inspection. Frame and underbody is in excellent shape. Those box rails are super clean. Didn't see any corrosion on those. Has all the factory exhaust. Everything looks really good on the lower rockers here. Didn't see any corrosion. My guess would be this is a Southern truck. Probably should have looked at the buyer's guide before I started the video but it looks like a Southern truck just from the condition it's in. Rear bumper is in nice shape. It has the backup sensors. Full towing package which includes receiver HN7 pin wiring. That tailgate is in excellent shape as well. Didn't see any dents or dings on that. Has a spraying bed liner. Also has the fifth wheel bed rails and a seven pin wiring for the back here. Bed's in really nice shape. Tailgate shuts nice and solidly. Super clean truck. Nice mud flaps keeps your lower rockers on the back looking really good. Stooly tubs in excellent shape as well. And for full disclosure this back rim is in nice condition too. Has the telescopic tow mirrors with the built-in directional signals. These telescope out. They also fold in built-in directional signals. Inside the LTZ package gives you the tan leather interior. There are no rips. There are no tears on these seats. This is probably one of the cleanest 2012s that I've seen in quite a while. Factory all-weather floor mats throughout power windows, power locks, power mirrors, heated seats, memory driver seats, automatic headlamps, factory brake controller, turned-out four-wheel drive. This truck's actually out of Michigan. However, the reason it's so clean is it only has 16,131 miles. Must have been a summer toy hauler. Steering wheel is in excellent shape. Bluetooth audio controls on the right, cruise controls on the left. No scuffs or scrapes on that. Comes with the factory navigation system. Also has AM FM, Sirius XM radio capabilities, Bose sound, six-speed automatic Allison transmission, dual climate control, power pedals, backup sensors, factory exhaust brake, and the backup camera shows up right there as well. Passenger side seat absolutely perfect. This truck has never been smoked in. Obviously it's been very well maintained. And with such low miles, you'd expect it to be nice, but not really this nice. Home link buttons for your garage doors, security systems, lighting systems, and your on-star capabilities. The dash, no cracks or anything like that on the dash here. Always got to look for that on these 2007 to 2013 or 14 GMs. They always seem to crack on those dashes up there. This one's perfect. Back seat's perfect. Has a latch child safety system, the fixed glass rear defrost. These seats fold up for extra storage. We have an all-weather floor mat back here, and the carpeting is absolutely perfect. Just about one of the cleanest trucks you'll find anywhere. I'd personally like to thank you for checking out the video today. Hopefully from this HD video you will be able to tell just how clean the truck was all the way around inside and out under the hood. Much of the same 6.6 liter Duramax diesel LML motor. Engine bay is very clean, runs very smooth. This truck has been fully safetyed and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. And I just need to get my microphone off. And 100% ready to go. I'd highly recommend it from a quality and condition standpoint. Won't find one cleaner than this. And to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, half tons, three-quarter tons, one tons, you name it, we got it go to our website www.SummitAuto.com. Full pictures and descriptions of every single vehicle from both our lots, all at one website at www.SummitAuto.com. If you want to check out more HD videos, you can go to youtube.com slash Summit Auto. Remember to like, subscribe, and share on this video and all the videos that you see there. In fact, in a second you will see a link to subscribe to our YouTube channel on your left. A link to more heavy duty truck videos like this one on your right. If you have not been to our website on the bottom link to this vehicle on our website, click those, check us out. We really look forward to helping you with this super clean, Plike New 2012 Chevy Silverado 3500 Crew Cab Long Box dual rear wheel. Thanks again.


Again after the 2016 election there's been a lot of attention paid to the possible effect bots played on spread of misinformation and I think this is my personal take that is being exaggerated and I think this work somewhat points to that and I think our attention is being focused on something that might not be as big of a problem as people think it is. Or at least the problem and the situation is more complicated and looking for the problem when there's actually a complex of problems is the right way to think about it.


So welcome to my talk about open HPC. So my name is Adren Rebo. I work for RETED. I'm, actually I'm in the core kernel team and I'm working on checkpoint restore container migration, but because I was doing checkpoint restore before joining RETED in HPC, I'm also doing now I'm RETED's representative in the open HPC project. And I want to give an overview here what open HPC is, what it does, why it exists. So my agenda is I first want to give a high level view why and what open HPC is. The next step I want to say why open HPC exists. I guess most people know the problems which open HPC tries to solve. And then I want to talk about again what open HPC is. And I want to focus more on how the project is set up and what goals are. And then I want to talk again what open HPC is and giving details about what it actually includes and what you can take out of it. And if there's some time at the end, I want to talk about what we are currently discussing in our meetings. So what is open HPC? If you just look at it at a first glance, it seems to be a software repository.  You can easily install on your system and you can install it. You can install those RPMs using YAM or Zipper, which means it supports right now CentOS 7 and slash 12. It's for X8664 architecture and the ARM64 architecture. The actual users are mostly, as expected, not on ARM, but on the X86 architecture. And that's what open HPC is, if you have a first look at it, at least what I saw. So the topic, why open HPC, why does it exist? This is probably one of the same reasons why also easy build exists. So in HPC environment, you have multiple compilers, you need to install on your system. You have multiple MPIs you need to install on your system in multiple versions. And you have three different compilers from three different vendors and two versions each. You already have like six different compilers. And if you combine this with the MPIs, you have a lot of almost same software you need to install, almost the same steps. And this is something which many HPC sites actually do today. So open HPC was the idea to kind of solve those things in a collaborative way. Back to my point, what is open HPC about the project, how it's set up? It's a community effort to reduce those mentioned duplications which each HPC site has to solve in some kind of way, whatever they use to do it. And when the project was informed, there was a mission and a vision statement. This is the vision statement. It's like a vision statement, it has to be it's visionary. It tries to formulate somehow that through collaboration, open HPC wants to help to have easier setup of an HPC system, easier administration, easier starting if you're completely new to the topic also. And the mission statement, I think it has some clearer goals. It's a collection of open source software in a repository which is easy to install. And in addition to the software it provides, it doesn't want just to provide software but also best practices, ideas, how you could install or manage your system. The open HPC project is a Linux Foundation project. I think these are all current members, maybe some more, it changes all the time. There are new members all the time. It's a combination of industry partners who are providing tools, software, hardware for HPC system as well as universities which are all bringing their knowledge together to formulate what open HPC wants to do. And I think the governing structure of open HPC is similar to what a lot of Linux Foundation projects are doing, we have a governing board, we have a technical steering committee which has a meeting each week or every second week depends if it's necessary. And in the TSC meeting we discuss what we want to change, what we need to change. And this is the committee where we try to find how to move forward. Maybe this is interesting for some of you, the membership is free for academic partners so if you're interested in joining open HPC you can talk to us and we're happy to collaborate with any more partners which are interested in open HPC. So this is the list of the current TSC members, so from a lot of those institutions or companies there's someone involved somehow in open HPC and one important thing which I think I, which needs to be pointed out is that open HPC doesn't force you what you have to install and how you have to install your system, it's about building blocks. You can pick and choose what you want and install the software the way you want it on your system. It doesn't, there are certain parts which you have to do if you want to use open HPC but it tries to be as open and free as possible so you can adapt it to your local needs. So you can either install the binary RPMs, you can modify those RPMs for your local needs, you can use any of the documentation in any way you want so it doesn't force a special setup on you so this is one of the important parts of open HPC I think. Some information about the project history. The first discussions about open HPC were held at IC 2015 and the first release of open HPC which is probably somewhere here was at Supercomputing 2015 and since then there are continuous new releases every quarter and each release contains more content than the previous release. Currently the latest release which was released at Supercomputing 2018 is 1.3.6 and we are currently working on 1.3.7. This is the number of components. So it grows slowly, there's not a large number of software packages we have but it's from our point of view, it's a basic software set which makes sense from our point of view to get an HPC system running. This is an overview of how much changed between the releases so changed means added or updated so it's most of the time around 30% I would say. Some statistics, how many visitors per month the build system gets. The package repository access we see per month unique visitors. So you can see they usually switch to the new versions our user as soon there's a new version. Now the latest statistics somehow some one started for a large number of people started to using the old release. We are not sure yet why this happens but more visitor statistics and this is the data downloaded from our build system and then back to my thing what is open HPC now in detail what it is. Like I mentioned it's a software repository and it includes different packages. The basis of all is ELMOD which we are using for the environment modules. The reason why we are using the Lua-based implementation is that as far as I know it is developed at tech and the Texas Advanced Computing Center and tech is part of open HPC and that's how the connection is between ELMOD and open HPC. It has advantages for the open HPC project because we have really close contact with the developers of ELMOD. So there's a close exchange and they can easily help us fix things or provide new features which open HPC needs for the software management. Then it includes provisioning tools like werewolf, there's XCAT, then there's monitoring, Nagios, Ganglia, then we have resource managers, KBS Pro, Slurm, Compilers of course, GCC, LLVM. There's support for the Intel Compilers so we don't distribute the Intel Compiler of course, you have to have it on your system already but if you have it, open HPC will detect it and all packages which open HPC provides are also available compiled with the Intel Compiler. So if you have locally the Intel Compiler installed you get the complete open HPC stack compiled with the Intel Compiler. The same goes for the ARM HPC Compiler which will be probably part of the next release 1.3.7. It's also, you have to buy it from ARM directly. Then we have the usual MPIs and then we have spec for more software, easy build for more software. This is one point where we know we cannot provide the same amount of software that easy build and spec can so we stop at some level where we say we want to provide a certain amount of packages which people can use to install a kind of minimal system or at least an HPC system which gets you running and then on top of it, there can be other tools which can complete the full software stack which we cannot in our group provide with the necessary, I don't know, bug fixes or make sure it actually works good enough but therefore our community is not big enough and the people involved right now. We have a few container run times included, Charlie Cloud, Singularity, then there are file systems clients, the last reclined and BGFS clients are part of it and lots of the usual libraries which you see and on an HPC system but it's important to know that OpenHPC is not just a software repository. It tries, one of the mission or vision statement includes that it wants to not just provide software but also best practices and OpenHPC comes with, in my view, excellent documentation for an open source project. This was one of the points when I first looked at it. It's really documented completely and documentation, I mean, it's the documentation how you would set up your cluster and the documentation is for every combination of provisioner, resource manager, operating system, CPU architecture, so for all those combination you get a different documentation and when I say including recipes, so part of the documentation is all the commands you have to type in into your shell to get your cluster running, to install the software to provision all the clients and the recipes are basically just all those shell commands put into one large shell script and you can run it and hopefully you have a working HPC system at the end. And also one thing I like about the project is with every release all those documentation steps are actually tested. We have a bare metal cluster where we install all our software packages and the operating system like we described it in our documentation to make sure that the documentation actually works. So everything is actually tested to make sure it gets you a running HPC system and once you have it installed you get the same interface independent of the operating system of the architecture. So the user will always see the same module names and files so he doesn't have to change any paths if he's using an open HPC system. Then I want to talk about some upcoming changes. The next release will be 1.3.7, it will be available somewhere in the next three months. It will include the usual updates of all the packages which can be updated and the goal is to include the ARM HPC compiler so that all packages are rebuilt with the compiler from ARM. What we just started to discuss last week in our meeting is support for new operating system releases. There's less 12, less 15 available which we want to support where we are thinking about supporting then there's the RHEL 8 beta available so we also started to look into what changes are necessary to get open HPC running on RHEL 8 and maybe CentOS 8 then at some point and the important thing here is from our release numbering this would mean we would go to a 1.4 release so at some point we changed our release numbering and said we will stay on 1.3 point something as long as the user can just upgrade the packages without any reinstallation and if we go to new operating system releases it would mean we would need a new release which just a number wouldn't be so bad but the problem is at that point it would mean we have to support like four releases for operating system releases and right now we are not sure that our community can handle four operating system releases because we already have enough to do to make sure that for the currently two supported version releases we can actually test it and if we have four we are not sure how to really do it so this as I said would require double the required testing so this is currently being discussed and when we switch and how we switch we don't know it yet how much time do I have and it's okay so when I tried to build an open HPC on the rail 8 beta there were two interesting things I had which may make the life of users or people providing the software for system a bit more interesting than it used to be so there's a new thing called ANOBIN and it provides annotation in the binaries and the problem is it's a GCC plugin and the default RPM optimization flex enable it and if you install a second GCC or a second compiler like we do and you recompile all your RPMs with your own compiler which doesn't have the ANOBIN plugin it gets complicated to disable it so this is a thing where we are currently I'm not sure how to handle it if we should just enable it or provide our own ANOBIN plugin for the plugins of for our GCC and the other big thing is Python 3 so we have a lot of packages which still depend on Python 2 and we are not yet sure how far rail 8 and CentOS 8 will support Python 2 if it will at all so we don't know it yet and so we currently disabled all packages which are requiring Python 2 this is a lot because it's basically it's at least when I tried it there was singularity was not working it was not possible to build PBS Pro it was not possible to build Slurm so this is a lot of our low level packages which are necessary to build a complete stack we were not able to build so we're hoping that the upstream projects are making the move to Python 3 so we can support almost the same flag same software stack as we used to so this will be one of the interesting things we somehow need to solve and another thing which I find interesting is we are using RPM coloring so the problem is if you install additional software using RPM like we do I'm missing a slide so in the end we install what could happen is that OpenHPC installs the same software as the operating system so same MPI or same GCC or at least or for example where I saw it first was OpenBlast so we are installing the same package built with a different compiler but the result for RPM will be the same because the shared object name is the same from the operating system package as with the OpenHPC package and if RPM or better YAM does its dependency resolution it can install one or the other package and if you just install everything it's okay but if you install the OpenHPC stack so you have OpenBlast as example from OpenHPC and then you install some package from the operating system which requires OpenBlast the dependency resolution will say I already have the shared object symbol in my RPM database I don't need to install it again the package and but if you then actually run the software it will not find it because you have to do module load before and the operating system doesn't know anything of module load so anyway what we do we just append to all our symbols which are in the RPM database we append a string called OHPC to make sure that our shared object are different from the operating system of object so this is an overview of where you can find us and what we do we work on GitHub you can look at our build system that is where you can download all our packages and you can have a look at our CI testing to see what we test like I described it there's a wiki and there's a mailing list where we discuss stuff and at this point I'm already in the end and thank you for your time I have a small question when you say singularity was not compiling on RAIL 8 you mean the 2.6 version? some version the version at that time I don't know okay because the new singularity version is not Python dependent oh it was some build dependency I don't know yeah I guess you were trying to build the last year yeah could be I just build it what was it openHPC repository and it didn't work do you have much of an idea of how many people actually use the openHPC so from the statistics a few thousand IPs yeah we don't know do people get in touch right do people get in touch with problems or like as regards documentation and things like that I mean you say everything is heavily documented like do people say this is not quite correct or this happens sometime but it's not very often the most feedback we actually get is at ISE and SC where people come by and they say we use it it's great so we that's kind of the interesting thing we do not get very much negative feedback so it seems like it it solves the problem of some people how do you integrate easy build in this openHPC environment do some special things to make it easier to use it he probably knows better what can happen he's doing the easy build package actually and so there's an existing spec file to install or to create a package for easy build which I try to update every time there's a new release and still have to do it for two days of release so you basically get an RPM for easy build that installs easy build and installs a module for easy build there's a metadata file in the easy build release for openHPC that tells easy build about the openHPC packages so you can make easy build use the open API for example installed through openHPC through one of the packages that this provided that probably needs an update for the latest openHPC releases but you can let easy build leverage the packages you can install through openHPC so it knows about it already maybe it needs a bit of an update but all the mechanisms are there so you don't have to reinstall openMPI if you already have it through openHPC so there's a bit of integration there there's probably more that can be done and this is some of one of the things I wanted to discuss with Adrian this week but yeah it hasn't happened but there's other ways maybe the openHPC project can leverage easy build to generate packages or update packages it could be an option To me this last bit I think it makes a lot of sense because you have easy build or you have a Spark which can generate all this huge amount of packages ideally optimized so I think there's a little bit of overlap between openHPC and when they the libraries that openHPC provides why not kind of get rid of that part and leverage the tools that are specialized in that like this wheel or Spark or well Yeah that would be ideal if we if those projects somehow could work closer together so that we do not do the same steps again I don't know to me you just think I think it kind of makes sense to maybe within the openHPC community to focus less on those libraries and maybe focus more on okay so what is the for this particular infrastructure what do you want to use? You want to use this wheel, you want to use Spark and from there on start picking up the the libraries that you want to install and use those tools for it I think it will be beneficial for both openHPC the users and the Spark and this wheel communities So is there an easy build any binary packages which is provided as all source compiled from source? It has support to install stuff binary as well it can do anything it even has some support to create RPMs so this could be something that could be leveraged in openHPC something we can look at together at some point Does anyone else have questions? I have a couple ask one or two the one thing that you mentioned is I'm a bit surprised by what you said you said in RHEL 8 it's not sure yet why the Python 2 will still be there I don't know In the beta it's there and there's I've seen blog posts by people at Red Hat that say we're gonna have to keep Python 2 at least initially Basically I know as much as you do I personally wouldn't expect it to be there because it's the end of life this year It doesn't make sense It's hard to believe that it will be part of running On the other hand you also said you run into lots of problems because you don't have Python 2 installed So maybe that's a reason why Red Hat says we have to at least initially Another thing I've noticed so Lmod is like the base for OpenHPC all the packages come with a module so people can you module load to activate the package but the modules that are included and OpenHPC are all in the TCL syntax Is there a good reason for that? Is it to keep it compatible with other modules tools in case people want to switch? No this wouldn't work because it includes already statements which are specific to Lmod Yes like automatically loading dependencies and things like this I actually don't know why it's still in the old format maybe it's just what people are used to I think it's worthwhile looking into switching to Lua because there's an overhead that the modules are in TCL Lmod does a translation of TCL to Lua before it even loads the modules making it a bit slower it doesn't make a lot of sense if you're tied to Lmod anyway Maybe one more you mentioned that your documentation is being well tested before doing the actual release to make sure everything is still fine Is that automated? That's interesting That's on the Jenkins on the CI infrastructure you can see there and all the testing is part of the OpenHPT repository so you can see where it installs the systems and then boosts them up How does that work in the documentation? All the commands have to be run are in a certain order and are marked somehow that they can be extracted or it's just a bunch of scripts that are in line in the documentation How does that work? I never actually looked but I think it's like it is said in the first step so it's all in latech from the documents into a shell script so this was and it's modular so if you do the installation for PBS Pro and SRAM all the documents which are then above the schedule are then from the same source so it's written only once then just constructed together that it fits Okay, cool Any other questions? Okay, thank you very much Andrew


Hi everyone. Good morning. It's still morning. I think folks are still getting seated, but let's get started because I think we'd like to use some of the time really for all your questions. I'm Aloleeta Sharma. I am one of the governance committee members on the Open Telemetry project. I've been involved with Open Telemetry for more than six years now. Really have seen an amazing community effort on the project. I'm also a TAG co-chair for observability and today along with my fellow GC members who will be introducing themselves. We'll be talking about Open Telemetry giving you an update on where we are on the project. Some exciting news as well as some features and community updates for you. So with that said, Ted, you want to introduce yourself? Sure. Hi, my name is Ted Young. I'm one of the co-founders of the Open Telemetry project. I currently work at the artist formerly known as LightStep. I'm Daniel Dyla. I work at Dynatrace. I'm also on the governance committee and I maintain the Open Telemetry JavaScript client. My name is Morgan McClain. I'm also on the governance committee, also one of the co-founders of the project. I work at Splunk and I guess I'll be able to make the same joke as Ted next year. You can see a pattern here happening. But with that said, again, I want to ask everyone a question first. How many of you use Open Telemetry? A lot. And how many of you contribute to Open Telemetry? Quite a few people too. So all I would say is that Open Telemetry is everywhere. It's a lot of users across the world who are using Open Telemetry. These are some of the major contributors as well as users, you know, of Open Telemetry. And of course, we'll go through some really amazing numbers as we proceed through. And in this slide, what we are trying to highlight is the top 20 contributors to the project. As you can see, there's a diversity of companies who are involved, organizations all the way from key vendors who have observability solutions that they're building, and also collection solutions, as well as key users, such as Atlassian, or Red Hat, or Shopify, you know, who have come and, you know, talk to the project about their use cases or have written blog posts and contributed to the blog, the project blog.  Come and tell us your story. You know, we are happy to publish on the project blog itself. And, you know, some of the issues you're facing, or some of the features you've found useful, or some of the improvements you'd like to see. So really welcome everybody to kind of, you know, get more involved with the project. And this is an amazing number. You've got to, you know, you've got to kind of relish this, and we certainly do. We have, at this point, you know, we started in 2019, you can see when Open Telemetry, Open Tracing and Open Census were merged. And today you can see a linear growth continuing to happen at amazing space where we have almost 1,100 active contributors to the project on a monthly basis, which is pretty phenomenal, and almost 1,000 contributions with the blue graph bars that you are seeing. But the number is phenomenal because 1,100 active contributors on a monthly basis is a really, really very large project, and a lot of activity happening on the project. And this is in comparison again to the second slide that I want to show for the most popular project in the CNCF, which is Kubernetes. And you can see that Kubernetes has about 2,500 active contributors, and Kubernetes is a massively large project, right? So you can see that Open Telemetry is about half 50% of the size of Kubernetes, but that's pretty phenomenal because, you know, for a single project and observability to have the level of activity and the level of contributions and participation from the industry as well as the larger community is pretty amazing. So with that said, again, we've got some great news to share. All right. I am so happy to be on stage this year to finally, finally be able to announce that Open Telemetry is officially GA. Yes. Yes. Yes. For those who have not been following along, what GA means for us is we've completed our original charter of achieving stability in the three primary signals of tracing, metrics, and logs. Now, this is awesome. I should point out we've actually had many of these capabilities for quite some time. So we've been GA for tracing and metrics for a while. Yes. Yes. But, you know, that was our original charter. We've also, even for logs, people have been using logs for quite some time, unlike a lot of open source projects that like to declare things 1.0 or stable or something when they're still in a somewhat vaporous stage. We really strive to be a responsible standards body at Open Telemetry and not declare things to be 1.0 or stable until they truly are stable for the long run. We aren't big fans of 2.0s for anything that our end users have to leverage highly and directly throughout their code base. Which is really exciting. Yes. Yes. This is really, really great. Also, an important reminder, even though we're talking about tracing metrics and logs and stability, we are not talking about three totally siloed separate things that is not the Open Telemetry vision that is very old school. What we're talking about is tracing metrics and logs designed to be fully integrated with each other into a coherent graph of data that can be walked and analyzed by machines as well as humans. That is the happy vision of the future that we hope Open Telemetry will power. With all of that said, let's dive down into the details of what actually has been changing with Morgan over here. Yes. As we mentioned, Traces went GA roughly two or three years ago. Metrics went GA last year. That was a big announcement to KubeCon in Detroit. The big difference now is that logs have gone stable. We show this slide every year, every time we're at KubeCon either in Europe or North America. Yes, there's been additions over the last several months to traces and metrics stability in various languages, various components, but those are already effectively there for most use cases. The big change here is logs. Not only is the logging spec, not only is the logging protocol and critical parts of high-level logging stable, but we actually, I think faster than most people have expected, have actually achieved stable implementations of logging, both in the collector and across various languages. Pretty amazing. This is actually more of an announcement than I think we were expecting to make even a few months ago, which is fantastic. This is very, very substantial for our end users. Tracing was a huge deal on Open Telemetry. There was nothing quite like it in the market when it launched. That's why I think the project, as you saw with our latest slides, saw such rapid uptake and such rapid growth. Metrics has also accelerated Open Telemetry's growth quite substantially, I think even more than any of us would have expected last year. I think logs will be another major step function for Open Telemetry, because yes, there are other ways to capture logs. There's been many for decades in this industry, but the fact that now these three really critical data types of telemetry that people need to extract can be done through the same agent, the same configuration, the same set of SDKs means that you don't need to rely on Open Telemetry, plus another thing, unless you want to. This is a very, very big deal for Open Telemetry. It also means you can do all of your processing in one place. I'm going to dive a little bit more into logs. In the spirit of this conference, I've gone to a lot of talks over the last few days, and it seems like using some AI image generators seems to be a necessity on various slides to make people laugh. We asked Open AI to show us some telescopes and logs together, and it gave us whatever this is. The more you stare at it and the more you think about it, the more questions it raises. Credit to Microsoft, we used the Bing image generator, and we asked for a lumberjack and some logs and a telescope, and it gave us this. This is actually pretty good. So that's the one we're going to go with. So there's your required AI image. But when we talk about logging in Open Telemetry, I think it's important to add a bit of context. And that is Open Telemetry, as I mentioned before, was the first sort of independent trace collection system that was around. There were open source ones, but they were tied to Zipkin or Yeager, and there were various closed source ones tied to various backends. And so Open Telemetry was somewhat new and novel for tracing. And then we added metric support last year, and there are other metric collection systems around, but I think the openness and flexibility of Open Telemetry has been very powerful. When we discussed adding logs to the project in 2020, it raised a number of questions, because there are many ways of capturing logs today. And so there were various things that we wanted to focus on, on logs, if we were going to add it to Open Telemetry, where we could solve problems that hadn't been solved elsewhere in the industry or problems that people still struggled with of logging today. And there were two classes of problems that came up. The first was that logs are challenging because they're unstructured. And the metadata that you get on a log from a system over here might be dramatically different than the metadata over here. That's true both for complex sort of per interaction metadata, but even for basic things like timestamps are often structured differently and need to be reprocessed. This is very annoying and very expensive to fix. The second is that logging agents can use a fair amount of performance to capture logs. They're parsing human readable text at scale. This is, you know, somewhat computationally expensive. And so to address both of these, Open Telemetry actually has two different logging paths. This is what makes Open Telemetry logging somewhat unique. So you can use the Open Telemetry collector agent to go look at a log files on disk the way you would capture logs with anything else today. That works. It will enforce Open Telemetry's standard data model. It will ensure that your data comes through with that right structure you expect that you get with the rest of your Open Telemetry data. The second way, though, is you can also capture logs in process by connecting to an existing logging library like for Java, log for J, or various other language-specific ones and actually capture those logs directly from your application. This gives you both the guarantees that we already provide in Open Telemetry around the semantic inventions and everything else. It also is just considerably more performant. And so when we talk about Open Telemetry logging, this isn't just adding logs to Open Telemetry the way you've captured them before. This is adding substantial improvements in the ways that you can capture logs and guaranteeing their structure and stability as well as offering substantial performance improvements. This is a very big deal for the project and for anyone who wants to use it. So we're very excited about that. And there's numerous other benefits. You can pre-process your logs inside of the collector using the exact same transformation logic that you would for other types of signals in the collector. That's a very big deal. It means you can modify your logs like you would traces or metrics. This is good. Also, of course, it's Open Telemetry. You can send those logs like your metrics and traces to any destinations that you want. And so this 1.0 is very, very exciting. I will say, just like as Ted had mentioned before, logs has been not officially stable, but much of the Corv has been usable for the last year or two. And so there are companies that we showed earlier if there are logos on there that have actually been using Open Telemetry logs for about a year and a half. And so with the stability, what it means is all the features are there. And it means that the configs and other things are not going to break, which is very, very big. And yeah, there's already a lot of code there. The collector has already like 29 or 23 logging receivers, 29 different logging exporters, 12 different types of log processors. Like there is a lot of content, a lot of stuff already there. Like this is ready to go use right now. We have logging bridges and all those languages that I showed earlier for direct in process log capture. And there's more coming for the SDKs as well. And with that, we'll hand off to Dan. All right. So thank you, Morgan. One more big announcement that we want to make as of last week or this week, early this week, HTTP semantic conventions are finally stable. Those that know know. This has been an ongoing effort for a really long time, and it is the first semantic convention area to officially achieve stability. And we are very proud of that. And we're very happy for everybody that helped contribute to that and make that happen. So thank you very much, honestly, from the bottom of our hearts. So the specification is stable. And there are a couple of languages that are approaching stability for that. Java and .net are particularly forward on that. But Python has a prototype that is expecting to merge soon. And other languages are also making good progress. So just because we've completed the original vision or what many people believe the original vision is, that does not mean that we are done. So there's still a lot of work to do. And what I want to talk about is less of a official roadmap and more of a list of priorities. So these are the things that we are really thinking about and the things that we want to work on over the next months and year and on an ongoing basis. And I'd like to split these into two sort of categories. So the first category is maturity and stability. We achieved a lot in the last three years, but we really need to focus on getting things right and polished and production ready and the various things that we need to do in order to prepare ourselves for graduation, which is going to be a big focus of the project leadership over the next months and however long it takes. The other part of it is increasing our footprint just because we have tracing metrics and logs does not mean that the work is done there either. We need more instrumentations and we need more signals. People are contributing in areas like profiling, auto instrumentation for languages like Go and C++, additional semantic conventions, hopefully by next year we will be able to announce significantly more stable semantic conventions. Right now the focus is on messaging and client instrumentation, but we really hope to ramp up the velocity on that soon. So finally, if any of that seems like a good idea to you, we would love your help with this. So please reach out to us and get involved. The best entry point for that is either GitHub or the website, but you can also follow us on social channels like YouTube where the meetings are recorded and posted and sometimes we post educational content and that kind of thing. Check out the open telemetry demo if you're not familiar with open telemetry and how the project works. That group has done a great job in making it very approachable. It's very easy to set up and you can get started and play with it very easily. We are having, some people may already know, a contribfest session this afternoon. So if you have never contributed to open telemetry or open source and you're looking for a good way to get involved with that, please come to room W186 at 230 and help us track down some issues and make your first open source contributions. We would love that. Related to that. Also, if you want to know more about logging, I realized I forgot to put on the slide. There's a talk about open telemetry logging. Annoyingly, it's also at 230 today. So you got to pick. Yes, we will treat that like you like one of us better. If you're not interested in contributing in code, maybe you're an end user. You don't have time to contribute upstream. We still want to hear from you. Share your experience with the end user working group. That is the only way that we know what we should build next. If nobody tells us, we have to guess and you're not going to necessarily like what we guess. So please tell us what you need. And finally, come visit us at the observability observatory booth. It's right in the center. Very easy to find. Big open telemetry logos. Can't miss it. There's sessions scheduled to that booth all day for various things that are meeting up or on various topics. So if you go there, you can see the agenda for the sessions and join whatever you want to join at that booth. Yeah. And I actually forgot to add a plug-in here. But for all end users, again, as you know, the CNCF has created a new end user technical advisory board. And I am part of that board. So again, please, please feel free to reach out to me. Happy to chat with you, help you, and also help you kind of prioritize a lot of the observability requirements that you have. All right. That's it. And with that, I think we'd like to open up the Florida questions. Yes. Yeah, we promised a lot of time for questions. So we're here. If you're a maintainer of open telemetry, can you also come up and help answer questions? Because I'm guessing we'll get some specific ones. Feel free. And if you want to ask questions, there's a microphone there. And I don't see a microphone there. That's strange. Well, you can also raise your hand and we'll run up with the microphone. Yeah.  Ask anything. Yeah. Hey, since you said I don't have to be shy, as a end user, who is kind of like deploying the commercial APM solutions, right? How do you see your roadmap evolving where we can confidently go and tell our developers that, you know, hey, embrace open telemetry, it's going to be the good thing long term, but you're not going to lose anything that you're automatically getting in your current tool scene. Sorry. Can you repeat? Yeah. So as the end user of commercial APM solutions and who is interested in open telemetry, right? How do you see your roadmap evolving where we can confidently go and tell our internal developers that, you know, hey, you can still adopt open telemetry and not worry about losing some of the automatic instrumentation that you are already getting it with commercial APM solution without gaps? Are we already at that stage or is it going to evolve to that stage at some point where we can make that move? So the question is about interoperating with existing observability vendors? Not interoperability, but more maturity of automatic instrumentation so they don't lose any signals that they are already getting today when we make the shift. Yeah. So maturity of automatic instrumentation is one thing that really needs to improve. It's one of our big priorities for the upcoming year. There are a couple of languages where it's really good. I know that Java and .NET have really good solutions for that, but we're continuously working on improving that in all languages where we can. Thank you. And if there's a particular language that, you know, you are using and are not seeing full auto instrumentation yet, I mean, please reach out to us, right? Because again, we always try to figure out if we can actually pull in more engineering to be able to build a particular area out faster. Yeah, we would love that actually. Totally. So please reach out. Thank you. Questions? Raise your hand if you have a question or approach that mic. Don't reach out. Hey, how's it going? First of all, phenomenal job with the release of the log, log API being fairly stable, fantastic work over the last year and a half. The question I had was around semantics actually. So specifically, is there any interest in getting geolocation into the current semantic schema? And I suspect that's going to go hand in hand with the client instrumentation. Yeah. So yes, absolutely. As part of getting semantics for clients, geolocation would be part of that. There is a client SIG that is focusing specifically on getting that in. It's a big domain. So, you know, it moves slowly like everything in open telemetry. We really want to get them right. We've actually have felt a little burnt in the past around semantic convention specifically. Oh, and we've got maybe someone who can answer this a little more specifically. So I'm also hosting a session at the open telemetry observatory at 1.30. If you're interested in rum or client side instrumentation, please come by and let's chat. Yeah, great. Jason's the Android maintainer. Yeah. Maybe one thing to add in the context of the ECS addition to open telemetry semantic conventions. ECS already has specifically geolocation as an area and domain and we are looking and contributing that as well. Cool. That's awesome. Thank you for calling that out. All right. You're up next. Yeah. Congratulations on the semantic conventions for HB and stabilizing that. I was wondering if you're also tracking when vendors are actually able to ingest those as well. Like, how do I know that my current vendor is actually able to get those new semantic conventions and that's something you're tracking from your end? So the short answer is that no, we as a project do not track that. You have to ask your vendor. I'm sure that they would be very happy to tell you. But I don't think that's something that we are really going to get into tracking very specific details of how vendors are implementing open telemetry. We're trying to focus more on providing high quality data so that they can build use cases as they see fit. But no, we don't have any centralized tracking of this vendor supports these use cases. But I mean, that said, please feel free to ask your vendor first of all, and most likely your vendor is already working on the project actively because, you know, again, we see an amazing diversity of all the observability vendors on the project. And this is very much a collaborative project where, you know, everyone is working together. So if you see that there is any gap, please reach out to us. We're happy to reach out to the, you know, they all interact on the project itself. All right. Thank you. We got a question over here. Hi. Are you engaging, for example, with well known projects that are like, for example, open source login libraries to help the integration with open telemetry, for example? So Dan, would you be the best person to answer that? Could you repeat the question? Are you engaging with open source logging libraries? So we talked about like Log4J can send data directly to open telemetry. That was one example, but like, well, I mean, I could sort of answer, but there's numerous others. So in every language, we try and build as many of these logging bridges as we can. In terms of engaging directly with the logging library providers, I don't actually know the answer to that. Or maintainers, yeah. As far as I'm aware, we aren't doing a lot of that right now. It's mostly already of the hooks that we need. Anyways, those logging libraries are often very stable and have been around for quite a while, which is part of the reason that we're leaving them in place and not trying to replace them. They have well-defined interfaces for hooking in with appenders or whatnot. So for the most part, we haven't had to, but be curious to hear if you have specific reasons that you're curious about this, if there's performance considerations or anything else. Is there anything they're motivating that question? Yeah, sure. I would say that nice to have would be like eventually, since this is going to be like a new logging standard. So all these open source widely used libraries, they support it out of the box, basically. Yeah, I think through the bridges, they effectively do for most of the existing ones. So like, I mean, I keep mentioning Mark for Jay just because I think it's probably the most common example, but like for most of these languages, like just to clarify for everyone because they didn't go over this in the talk. Like with open telemetry for metrics or for traces, you create those using the open telemetry APIs in SDKs. For logs, for most languages, the expectation is you just use the logging bridge to use log for Jay or whatever logging library you're already using. I think in one or two languages, we're adding direct logging creation capabilities like C++ or something, but that was where there weren't existing logging libraries that were standard. Generally, we expect you'll just keep using the logging libraries used today. Other questions, if you're over on the side, you can raise your hand. Yes. Hey, thanks for the talk. Congrats on GA. I'm an open census go user. What should I do? Yes, and the question I have is it seems like an insurmountable work to migrate to open telemetry. Do you have advice besides the bridge? Because essentially it's like, how do you migrate our users also? So I think I could respond to one part of that and then please feel free to join in. So for a migration from open census, typically you can use the open telemetry bridge first and then go and fully go native and that gives you the ability to kind of transition your instrumentation or improve it as well as continue to test with the migration as you move forward. But I'd say that, you know, does that answer your question or are you going to be, you need to be more specific? We also have someone at the back who works on GO who might have an answer for that as well, if he's going to answer. I just want to add one thing. Also, we're still users of open census in the collector, so I feel your pain. There's also an open census receiver in the collector that you could use if you didn't want to migrate away from open census and then you could translate that data into like OTLP natively and then send it out that way. Yeah, I'm Tyler. I do a lot of GO stuff. And so if your question was specifically around GO, we are actively working on that. Sorry, who asked that question? I was, okay, sorry. Yeah, and like it's a big project obviously to try to provide compatibility, but we're pretty close actually. So I would imagine in the next few weeks, there's a few things we want to try to make sure we're stable about. But as it is, it's pretty close to ready to go. I think that the plethora of other answers you've received are probably also really great ideas. The collector's a really good resource in this situation. But yeah, the idea is to try to make it as seamless as possible with the bridge. And then I think you could also look into some auto instrumentation options that are coming out in that space to try to help that migration path after the fact if you wanted to automate that switch. But yeah, we can talk more as we'll come to the sort of ability. Yeah, as we showed on the slide, we didn't dwell on it too long. GO auto instrumentation via EBPF is also a thing that the community is working on right now. So that may be an option as well. Cool. Okay. Other questions? Other questions? Yes. Hello. I noticed there was a bullet point about improving documentation and the end user experience. What's the best way to get plugged in? Should I pick a language and join a SIG? Oh, yeah. Hi, yeah. I think a lot of maintainers will actually like label for any of their repos. Good first issue, docs issue, that type of thing. And usually that's like the best way to get started is just look at the open issues that are already labeled. I know that I label a lot of docs issues in the operator repo. So there should be plenty there. I'll go check out the operator repo. Thank you. We have a question here. Yeah, I should also mention that we have a comms SIG. And so in general, this is a thing I should mention about open telemetry. We are very meeting a zoom heavy open source project. And sometimes people feel like, Oh, that's for like the inner circle experts. I can possibly show up to a SIG or join a zoom meeting. You're absolutely welcome. We love it when people show up and say, Hey, I'm new here. I would like to contribute. We are also available on Slack. So all of these SIGs are on the CNCF Slack. It's you can find all of this info in the community repo. But the comms SIG also has a Slack channel. And those are great places to just plug in and figure out how you could help improve our docs. There's there's also the end user working group. If you're an end user and you have any questions, I think they meet every week, maybe, or every two weeks. And you can join the call and just, you know, there's like a list of questions that you can ask. And then people talk about it. Usually there's experts from various SIGs that also joined. So if you want to get started today, just join the contribute session. It is about the collector and JavaScript, but we're more than happy to help you on the docs as well. Cool. So without just saying like it depends, I guess the question would be, what is your favorite logging back in? It depends. There's a few of us who probably are too biased to answer that. We have an issue open right now for that. But the idea is so the way that it works today is if the authentication data is part of your telemetry data, then it's easy to route. You can use the routing connector for that. And you get a authentication key from the telemetry data and inject as a HTTP header for the outgoing data. What we are what we have an issue right now for is we have a, we want a way to convert metadata, connection metadata into either telemetry data or to bypass or to just pass through that value from the incoming receiver to the outgoing exporter. So that you can use the routing connector to decide where to send the data to based on the metadata from the incoming connection. Yes. Yeah. Any more questions? Yeah. I mean, we also have a security, but it's not really, I mean, the security is more. Any more questions? Going once? Going twice? All right. Well, thank you very much for coming, everybody. Thank you. It takes me a person questions up front.