I'm Amy Blossom from Jackson County Library Services, and I welcome you to Windows in Time. Windows in Time is a series of local history talks, a program that's been developed by the Jackson County Library Services and Southern Oregon Historical Society. It is also part of the Southern Oregon History Show, which airs on Thursday nights at 6 p.m. You can also see us live, though, at the Medford and Ashland Libraries, the first and second Wednesday of each month, at noon. So are you ready for some history? Let's go! Hello, my name is Alice Mullally. I'm a longtime mathematics teacher and a lover of local history. As such, I've been a volunteer at the Southern Oregon Historical Society, where I write, as it was, radio scripts. And where I work in the Southern Oregon Historical Society Research Library. And it was at the research library several years ago when I was asked to transcribe a diary in a little tiny notebook that was written by Fletcher Lynn about a trip that he and some Jacksonville people took to Crater Lake in 1889. And it's that diary that I would like to read to you today. You will see a lot of photographs that they did not take on their trip. So these are photographs that other people took on their trips to Crater Lake. I'd like to start by introducing you to the people who went on this trip. Fletcher Lynn was the person who wrote the diary. He was the son of David Lynn, who was a pioneer furniture maker in Jacksonville. He'd gone to school in Jacksonville and then on to the University of Oregon, where in 1889 he was to be a senior. He seems not only to be the diarist, but the organizer of this trip as well. Also along was Fletcher's cousin on his mother's side, Kerry Beekman. She was the daughter of Cornelius Beekman, the wealthiest man in Jackson County, a banker, landowner. Kerry was a graduate of Mills College in Oakland, California and was 24 years old at the time of this trip. She was an accomplished musician. Visiting Kerry that summer was Nina Beekman, Kerry's cousin on the Beekman side from Dundee, New York. Kerry on this trip turns 19. Joining the group from Salem was a classmate of Kerry's from Mills College, Anna Brayman. She was also 24. Her father was a prominent merchant and property owner in Salem. Along on the trip was Cap Coobley, another son of a pioneer family who owned farms, lands and stores in Jacksonville and the Applegate Valley. Cap was 20 and attending the University of Oregon. Another University of Oregon classmate was Everett Mingus, who was a sophomore having won one of only two scholarships given by Jackson County in 1888. His father had donated land just six years earlier to the railroad for the founding of Medford. Rounding out the group was Professor G.H. Watt. He was principal of Jacksonville School, where he had been for five years. He was 36 years old and had lost his wife just the year before, leaving him with four very young children. There's no record of how he handled childcare on this trip, however. Was he on this trip as a chaperone? Was he just friendly with recent graduates of Jacksonville High School? Fletcher Lynn doesn't tell us. Now today, if we went to Crater Lake, we'd grab a sweater on a bottle of water and we'd be off in two hours later. We'd be climbing Garfield Peak or going down the trail to the lake to take a boat trip or driving around the rim drive. And we'd be home for supper, unless we'd stopped at Becky's and had too much pie, then we wouldn't want supper. But they had a very different trip. And Fletcher Lynn wrote a very interesting and rather charming account of that trip. And we're now going to hear about it in his own words. Wednesday, August 7th, 1889. Vehicles were a large wagon for provisions drawn by steady farm horses and carriage drawn by a spirited livery team. This was their means of transportation for the entire trip. Provisions included 30 loaves of bread, two sacks of flour, 35 pounds of sugar. Note that this is five pounds per person for only three weeks. 70 pounds of potatoes, that seems like a lot too. Not so much meat, only three hams and 11 pounds of bacon, but lots of fruit, two watermelons, a box of peaches, and so forth. As well as complete cooking outfit, axe, hatchet saw, nails, rope, wire, portable table, campstools, tents and poles, bedding and so forth. Hunting implements, two Winchester rifles, a shotgun, a target gun with 800 cartridges, and a revolver. For some reason, Fletcher Lynn doesn't mention fishing gear, and yet he talks about fishing almost every day. They took games, a deck of authors, chess and checkers with board and deck of cards, and musical instruments, cornet, guitar, and three harmonicas. Left Jacksonville at 6 a.m., ate lunch consisting of ham sandwiches and marble cake at 11 on the Bank of Bear Creek. Passed through Phoenix, Talent, and Ashland. At Ashland, we remained half an hour to view the principal parts of the city, and all the many improvements recently made. The city seems quite lively and prosperous. The population is about 2,000, so they claim. Arrived at Johnny Murphy's place on Immigrant Creek, 6 miles above Ashland, or 23 miles from Jacksonville at 4 o'clock, and pitched camp. Had a fine supper at 6, after which we spent the evening in singing, playing games, and so forth. Mrs. Watt and Kubli also interested the crowd in a few gymnastics exercises. Retired at 9.30, all were exceedingly jubilant, and anticipated a grand trip and jolly time. Perfect harmony was foreseen, and all members of the party seemed nothing but congenial. Thursday, August 8th, arose at 5 a.m., had fine warm breakfast, and continued our journey at 7.16. Roads were not rough, but all uphill. Ladies walked 2.5 miles. After being on the road about 2 hours, Kubli and roaming about came in contact with a huge fierce badger, which he killed after a desperate struggle. Arrived at Dead Indian at 3.40, and camped at the foot of Dead Indian Hill, traveled about 11 miles, obtained 6 pounds of butter, and 2 quarts of milk at Inlow's Camp. Evenings spent in playing wist, checkers, and in singing and playing, retired at 11.30, considerably fatigued. Friday, August 9th, arose at 4.30 a.m. Professor Watt and Everett took one early hunt, got only one rabbit apiece, had a fine breakfast, and plenty of new milk. Renewed journey at 9 a.m., at Neal's Ranch, we obtained a gallon of buttermilk, which Professor Watt and the ladies greatly relished. Then we took the wrong road and went 5 miles out of our way. In attempting to take a shortcut when returning, we again took the wrong road and went 2 miles further out of the way. Not on the right road at 3 o'clock, the road was terribly rough and riding extremely tiresome. Though all were somewhat disheartened and disappointed at our misfortunes, all were jubilant after we found a good camp on the right road, and our pleasure was greatly intensified rather than marred by our mistake. He shall rejoice most who endureth misfortunes most nobly. Saturday, August 10th.  Reached Lake of the Woods at 2.30, the water was very scarce along the road and not very good at the campground near the lake. Forest fires raging and smoke very dense. At this point, Lynn gives us a note about Lake of the Woods and Mount Pitt. Lake of the Woods is nearly directly east of Jacksonville and about 5 miles from Mount Pitt. It is about 3 miles long and 1 mile wide and is surrounded by a sandy beach of considerable width. At present, the lake is lower than ever before known. No stream of much size runs into it or from it. But its water is furnished by the rains and snows and by numerous springs in and about the lake. It is considered one of the prettiest lakes in Oregon. Mount Pitt, known to us today as Mount McLaughlin, could not be seen on account of the dense smoke. It is about 10,000 feet high and is usually either wholly or partly covered with snow. This year, the snow entirely disappeared. Mount Pitt and the scenery surrounding Lake of the Woods are grand and picturesque when the atmosphere is clear. We rode twice along the beach or shore, then pitched camp near the lake at 5 p.m. Had a grand hot supper. A party of three from Ashland were camped beside us, with whom we had a pleasant visit in social time. Found plenty of good feed for the horses and a huckleberry patch near camp. Intending to stay at Lake of the Woods several days, we arranged camp very orderly and prepared to take a good rest and have a jolly time on the lake shore. Retired at 11.30. Sunday, August 11th. A prohibitory law was established and enforced by Ms. Kerry Beekman, who had previously been formally designated president of our party. Forbidding hunting, shooting, traveling or anything, not agreeable to the proper observance of the Sabbath. Or which would seem in the least disrespectful to him who affords us our pleasure. So, we rose rather late and had breakfast at 9. After breakfast, a general cleanup of persons was indulged in. The men retiring to the lake to take a bath while the ladies held possession of camp. Everett further proved his skill in all things by efficient manner in which he manipulated the razor. While cap, not wishing to be outdone, skillfully managed the curling iron for the ladies. Soon the ladies presented themselves arrayed in attire fit for any occasion, even the most exalted, while the men came forth in the best they had carried with them. All having congregated, the third and fourth chapters of John, the fifth chapter of James, and the last chapter of Revelation are read by Ms. President. And sweet by and by, home sweet home, nearer my God to thee, and other hymns were sung by the party. A fine dinner was then prepared with huckleberry pie for dessert. This afternoon was spent pleasantly and singing, playing, musical instruments, talking, joking. At 6 o'clock we took our musical instruments and all went for a stroll along the beach. Visited a camp of old pioneers about a mile from our camp and stayed two hours. Played and sang for them and spent the evening quite pleasantly. Then having spent the Sabbath in the mountains in a civilized and quite praiseworthy manner, we retired about 1030. Everett suspected something wrong in the actions of Carrie, Nina, and Kubli and retired dressed with his shoes ready for an emergency during the night. Monday, August 12th, storms and hurricanes raged at about 1 a.m. and all but Carrie, Nina, and Kubli suffered severely from them. After rising late, some retaliatory measures were adopted by those who were the victims of the storms and hurricanes, but they were discovered before being carried out, even though they were successful in producing the desired effect. Several good jokes were carried out quite effectively and all taken good-naturedly. This being the 19th anniversary of Miss Nina's birth, it was agreeable to all to celebrate in birthday style. A fine dinner was prepared and a good old-fashioned candy pulling was indulged in in the evening and the event observed in a most commendable manner. Singing and playing and games of various kinds were enjoyed and no pains were spared to make Nina's birthday in the mountains, one which she will always remember with extreme pleasure. Retired about 11, at which time the song, I'll forgive but never forget, was appropriately sung and well rendered by the ladies. Tuesday, August 13th. We arose about six and began to load our wagons and prepare to leave. Passed slowly along the lakeshore and took our last glance at the lake in our campground. Everett and Professor Watt, inspired by the grandeur of the lake, no doubt, wandered too near the water with the provision wagon and soon found themselves stuck in the mud. Soon enough, the wagon was free. The road was very rough, yet much better than some we had previously passed over. Having been advised to visit stittums about six miles off the main road, we directed our course thitherward. Not finding a good camping place there, we turned toward Pelican Bay on the main road and about 14 miles from Lake of the Woods. Obtained six pounds of fine butter on the road to the bay. Pelican Bay is a very pretty body of water, furnished by large springs at the foothills. It is an arm of Klamath Lake. The woods surrounding the bay abounded game and furnished fine timber. Our camp here was rather dusty and disagreeable, yet had a fine time. Professor Watt, Kerry, and Miss Brayman went from the bay into the lake in a boat. And Everett, Cap, and Nina were boating several times. I didn't get to go at any time. Wednesday, August 14th. Everett and I arose early and took a long hunt, but saw nothing. Spent the day in boating and otherwise having a good time. The evening was spent very pleasantly in singing and playing and otherwise amusing ourselves. Professor Watt further added to the amusements of the evening by some contortions and gymnastics exercises, while the ladies plainly evinced their knowledge and appreciation of operatic dramatic skill by rendering several fine selections of that character. Thursday, August 15th. We rose at six and proceeded in our journey at nine. The road was extremely rough and all four horses had to be hitched to draw the wagon to the summit of a divide about a mile from the bay. The scenery as we passed along the road is quite picturesque. Passed many campers and camps along the road. Arrived at Cherry Creek and we found the finest camp we have yet had. So arranged everything very orderly and conveniently as we intend to remain over Sunday. Retired rather early. Friday, August 16th. Everett and I arose and started on a hunt at five. I killed a fine grouse while returning to camp and Everett later killed one in camp. In the afternoon, Professor Watts and I went to a large spring about two miles from camp to fish. But we gathered shells upon the Klamath Marsh instead. Found six or eight varieties of fine freshwater shells. In the evening when we went to tie up our horses for the night as usual, we found that they'd started homeward. We searched for them until it was too dark to see plainly. Though the thoughts that our horses had left us rather shrouded our camp in gloom, we spent the evening cheerfully and pleasantly allowing nothing to mar our pleasures. Saturday, August 17th. Professor Watts and I arose at five, started in search of the horses. We tracked them along the road towards home and found them about four miles from camp. Had breakfast at nine, after which Everett, Cap and I went fishing and Professor Watts went hunting, leaving the camp in charge of the ladies at their request. Professor Watts returned with one grouse. Everett Kubli and I returned with 156 fine trout. Had a fine supper with plenty of fish and spent the evening sociable, ate cookies and cakes and drank lemonade. Clouded up late in the evening and threatened to rain, but no rain fell. The horses were restless all night. Sunday, it's Sunday again, August 18th. The prohibitory law was again enforced, but not so stringent as last Sunday, permitting some necessary work to be performed. It was rather windy and chilly all day. Smoke entirely disappeared and thus afforded us the pleasure of the surrounding scenery. The horses got loose again and we had quite a chase before catching them. After the morning's work was completed, all congregated, and the fifth chapter of Matthew, the fifteenth chapter of John and the first thirteen verses of the twelfth chapter of Hebrews were read and hymns sung. A fine dinner was then prepared, the most extensive bill of fare we had yet had. The afternoon and evening were spent in singing and playing and having a good social time, while we all took a good rest preparatory to the renewal of our journey on the morrow. Cherry Creek is a fine specimen of a mountain stream. About twelve miles from Fort Klamath, it's very clear and quite cold. The prairie along the lower part of the creek furnished very good grazing for horses, and the scenery along the creek and the surroundings is quite pleasing though not picturesque. Monday, August 19th, arose at six and renewed the journey at nine. Roads for about three miles were quite rough and the woods adjoining were all a fire. The rest of the road was smooth, scenery the grandest we had yet viewed, mountains surrounding the Wood River Valley and Klamath Marsh are indeed picturesque. The atmosphere was very clear, arrived at Wood River at one thirty, where we ate lunch and fed the horses. Then went to the fort. Fort Klamath was built by my father during the Indian trouble in 1864. It's about a hundred miles from Jacksonville. It was abandoned last Thursday, August 15th, 1889. So we were deprived of the pleasure of seeing the soldiers in their drills. Only thirteen officers and soldiers are now stationed at the fort and it seemed entirely deserted. Guns and everything were even removed. We rode by the graveyard and all the buildings of the fort and passed near the formwork of the scaffold on which Captain Jack and other Indians were hung. At the fort we mailed several letters, sent telegrams announcing our arrival there, and laid in a few necessary supplies. I hope they didn't buy more sugar. At any rate, we continued on our way and arrived at Annie Creek at five thirty, where we found a fine camping place, purchased hay for the horses along the road, had a fine time in the evening, and retired at all hours from eleven to one. Tuesday, August 20th, arose at seven and continued our journey at nine. I was suddenly taken sick and felt the effect of it through the day. We passed along Annie Creek Canyon, which afforded some of the grandest and most picturesque scenery in southern Oregon. Along the canyon are many perpendicular cliffs, two or three hundred feet in height, which are all grand. We played the cornet and listened with intense interest to the sound echoing and reverberating between the precipitous walls. The canyon has been washed out by a comparatively small stream, and in some places reaches the depth of nearly seven hundred feet. The walls of the canyons are composed of pumice stone, in some places standing upon the inclined walls like pyramids or needles. This was the most interesting day we had yet spent and prepared us for the Grand Crater Lake Scenery, which we were about to witness. Met many Indians during the day, returning from the Huckleberry Patch at Whiskey Creek, seven miles from Crater Lake. Passed quite a party from Phoenix, camped two and a half miles below the lake, and another party from Grants Pass, two miles below the lake. Later found a party from Talent, arrived at a fine camp one and a half miles from Crater Lake at six o'clock, where we arranged things for a few days' stay. After supper, Carrie was suddenly taken sick with a severe, nervous chill and was quite ill during the evening. However, we spent the evening quite pleasantly in singing and otherwise having a good social time. Being considerably exhausted from our day's ride, we retired earlier than usual, intending to visit the lake on the morrow. Wednesday, August 21st, arose with the intention of visiting the lake, but after breakfast, Carrie was again taken with a violent, nervous chill which was followed by three others and in the afternoon two more. So we abandoned visiting the lake and remained in camp during the day. Found a fine Huckleberry Patch near camp and gathered a lot during the day, retired with a feeling that all would be ready to take the climb the next morning. Thursday, August 22nd, arose at 4.30, had an early breakfast and all went to the lake. The ladies riding in a light wagon with Everett driving the team. The rest walked, reached the lake just after sunrise, but the view of the lake was greatly obstructed by the smoke. However, the scene was grand. Cap and I went down to the water to see if the trail was in proper condition for the ladies to undertake the descent and found it safe yet venturesome. We returned and met the rest of the party halfway and assisted the ladies the rest of the way. Soon after we reached the lakeshore, 1600 feet below the point from which we had gazed in wonder, we were joined by the party from talent. After remaining at the water's edge for about two hours and carving our names and initials in the most conspicuous places, we commenced the ascent of the precipitous walls and reached the summit one and a half hours later. After returning to camp and having a good hot supper, we talked over our day's adventure, grateful indeed to our protector for thus having so safely led us in a perilous adventure. Friday, August 23rd, arose late and found it cloudy with heavy mist falling and the smoke almost disappeared. After breakfast, all but Carrie and Nina went to the Huckleberry Patch about a half mile from camp and gathered about six gallons of berries. As the smoke had cleared away, all but Carrie and I went to the lake at various times during the day and had a grand view of the lake. Carrie deemed it politic for her to take a good rest all day, preparatory to the renewal of our journey on the morrow. We retired about ten. Saturday, August 24th, arose about five and began to prepare to proceed on our way and direct our course homeward. After breakfast, Carrie and I took the light wagon and went to have a last look at the lake. Leaving, we passed along Castle Canyon, had a very good view from the wagons, met 92 Indians returning from the Huckleberry Patch at Whiskey Creek, ate lunch and fed the horses at Union Creek at 130. No beckies then, though. Passed through some very dense and fine timber, rode from the lake to the falls was grand. Arrived at Rogue River Falls at 5 p.m., having had a long, dusty ride during the day, we retired shortly after having supper and singing a few of our favorite songs. Sunday, August 25th, we arose about seven o'clock and, after having breakfast, all went to the falls to spend the day. Had a fine time at the falls and highly appreciated the grand scenery. The falls are formed by a small stream known as Mill Creek, falling over a precipice 196 feet high. They are pretty, though, quite small and form an object of interest and attraction to sightseers. Rogue River Rapids, formed by the river rushing madly down a steep incline between lofty banks and over huge boulders, is equally as grand and picturesque. Remember, this is Sunday. This is a different Sunday. After a stay at the falls, we returned to camp where we built two fine campfires and, after supper, spent the evening in our usual social manner. During the evening, there were readings from Romans and Peter 1 and 2. How different this is from the first Sunday. Monday, August 26th, arose early and renewed our journey at 7.30. Killed some quail and grey squirrels on the way. One horse nearly gave out and made us very late in reaching Jackson's, our camping place. Camped in the midst of 60 acres of melons and were told to help ourselves. After doing so and feasting highly, all but the girls retired. It being our last night out, they were bent upon having a good time when we're up until nearly one o'clock. They sang, chatted, and feasted upon melons and had a merry time. Tuesday, August 27th, the last day. After breakfast, we rode through the melon patch, loaded our wagons with 15 of the largest melons we could find, and directed our cars homeward. A dinner on Rogue River near the bridge. That's Bybee Bridge today, and it's located on Table Rock Road near Toddville Park. Reached home at 5. The thoughts of our reunion to be held on Thursday night somewhat cheers us, and another one of our good old times is generally anticipated. And they did get together just two evenings later at Kerry Beekman's house. Thursday, August 29th. All assembled at Kerry's fine home and spent the evening very pleasantly in reviewing our grand trip and enjoying our mountain jokes. A grand banquet was prepared for us and immensely enjoyed. Appropriate and impressive toasts were given and an evening spent long to be remembered. Thus ends Fletcher Lynn's account. Each of the six signed the diary, presumably that night. Let's hear what they said, and I'll tell you what became of them. Kerry Beekman hoped, the pleasures of our Crater Lake trip will never be afaced from memory. She went on to play piano in the Presbyterian Church at Jacksonville and gave lessons in the Beekman home to many youngsters. Later she traveled in Europe and the East Coast, cared for her parents as they aged, and eventually lived in Portland with her brother. Her Jacksonville home is the Beekman House Museum today. Nina Beekman remarked, my trip to Crater Lake will always be remembered as among the pleasantest and most enjoyable time spent in Oregon. She later married Leland Ernest and lived out her life in Dundee, New York, where she was active in the Presbyterian Church. Anna Brehman poetically stated, friendship which flows from the heart cannot be frozen by adversity as the water which flows from the spring does not congeal in winter. She would marry Rudolph Prahl in 1894. He was a China and Crystal importer. They were married 52 years and Anna lived to be 103. Casper Kubli said, may we all meet again and enjoy happiness equal to that enjoyed in our past trip. He would go to Harvard Law School. He was a natural athlete and could have gone with the Boston Athletic Club to the first modern Olympic Games. But he didn't. He came home to Jacksonville where he was a lawyer, a minor and served seven terms in the state legislature including one as speaker in 1933. Everett Mingus wrote, may this pleasure be again. He studied medicine and remained a highly respected and well-known doctor in Marshfield, Oregon for most of his life. George Watt just signed his name. He later became professor of pharmacy at Washington State College in Pullman, Washington and the proprietor of a drug store there. Fletcher Lin, our chronicler, writes a note in the diary much later when he apparently is sending it to Kerry. Tell Kerry to keep in mind that this account was written by a schoolboy 52 years ago. He had gone on into the furniture manufacturing business in Eugene and Portland and was a financier and president of Portland Cement and Pacific Coast linen mills. He was active in the Portland Chamber of Commerce and became a trustee of Lewis and Clark College, the YMCA and the Oregon Historical Society. Though they saw many interesting and picturesque sites and ended up many miles apart, the camaraderie experienced by all surely would be with them for many years to come. Thank you for sharing this diary with me today and thanks to the Southern Oregon Historical Society for the use of many of the photos, the diary and the map. So thank you for coming and joining us this evening. And open your eyes. Remember, history is everywhere.


The thing about a team like this is that there's always going to be a lot of really, really talented players that are around. So the competition is always going to be, there's a high level of competition. And, you know, there's things that I want to do and work on this spring. And that's going to kind of be my primary focus. Stuff like roster construction. I don't really have any say in it other than what I'm showing in terms of performance and my work day to day. So that's just kind of what my focus is. Sweeney Murdy, you have the next question. Hi, how are you? It's good to see you. Do you, how much time do you spend thinking about last season and your performance last season compared to the year before? There are a lot of players who dealt with a lot of things last year and, you know, it's easy to explain away some of those things. What kind of answers did you kind of come up with when you thought about last season versus 2019 for you?  And, you know, that's not saying that you don't have to perform because regardless of what's going on, it's the games about performance and, you know, I didn't perform the level that I expect out of myself. So when I got home, I tried to identify the things that I could do to improve myself and I got to work pretty quickly on some of those things. And then I just tried to also keep it in perspective that it was like, hey, you know, it was a strange year and, you know, I had a conversation with some of the hitting coaches and we kind of decided, you know, this is what it was last year, but we're not talking about that anymore. We're talking about this year. So what are some of those things you identified? Um, so, so for me, I, um, my back path got a little bit out of whack and it led me to being consistently underplane and a little bit disconnected, which I believe directly correlated to my struggles against velocity.  And I know this is probably how you approach every spring so far, but given the competition for spots right now, is, is performance this spring, is putting up production this spring, maybe more of a premium for you?   I think in spring training, you can dive, you can dive a little bit deeper to say, you know, while I had two at bats today and when I walked and when I lined out to the center fielder, that's a pretty good day, if you ask me. But, um, you always want to play well, you always want to have production. Um, I, I think there's been thousands of times that you'll see a guy doesn't get a hit all spring and he'll start the season now with a 20 game hitting streak, vice versa. So, um, I think quality of work, building myself, building the, um, capacity up to be playing, uh, back to back games, playing different positions, um, being able to just kind of just check some of those boxes off is always going to be a priority in spring, going first to third, it's dealing a base, um, you know, maybe coming in a game late and, and to simulate, you know, the times that that happens during the year. Um, I think those things are more of a priority than, you know, I'd love to hit 400 this spring. If I don't hit 400 this spring, I think I'll still be okay. Thank you. And I'm sorry if I missed one last one. Um, it's not been brought up to me. Um, I have a little bit of experience in there dating back to college. Um, if it was ever brought up to me, um, yeah, I'd be willing to get, get out there and give it a go. We'll take the next one from Pete Caldera. Um, I mean, I guess, um, you know, I had some issues with my shoulder, um, but I, I, I felt as though I was good enough, healthy enough to be in the lineup. Um, it wasn't something that I felt like could take me online. Could have affected my performance or, you know, I compensated and built some benefits. It's possible, but I don't like to use, I don't want to use that as an excuse because at the end of the day, um, the production wasn't there to the level that I hold myself to. So, um, I spent a lot of time this off season addressing that as well. And I feel great. I feel, um, as though my body is in a really good spot right now. Um, and I'm just, you know, kind of excited to play in some games here coming up.


Welcome back to Tennis Talk, my name's Cam Williams and with Roger Federer announcing his retirement, many players have come out in celebration of what has been a great career and a very long career. Let's go over to some of the players, some of the greatest players of all time, coming out in support of Federer's retirement. Starting with Andy Roddick saying, cheers Roger, thanks for the shared memories my friend. It was an honor to share time slash experiences on the most hallowed grounds in our sport. Don't be a stranger. Dylan Alcott has come out and said, the goat, a legend on court and even better bloke off it, changed the game forever. Big love for everything mate. Serena Williams has come out as well who just retired herself saying, I wanted to find the perfect way to say this as you so eloquently put this game to rest. Perfectly done, just like your career. I have always looked up to you and admired you. Our parts were always so similar, so much the same. You inspired countless millions and millions of people including me and we will never forget. I applaud you and look forward to all that you do in the future. Welcome to the retirement club and thank you for being you. And of course the big one, Rafa Nadal. He came out and said on Twitter, Dear Roger, my friend and rival, I wish this day would never come. It's a sad day for me personally and for sports around the world. It's been a pleasure but also an honor and a privilege to share all these years with you, living so many amazing moments on and off court. There you have it, some of the greatest players of the game, coming out in support of Roger Federer and has a bit of a tribute as well. Of course Serena just retired, Federer returned the favor a couple of weeks ago and said the same nice things about Serena. Obviously Rafa's coming out and we haven't had anything from Djokovic yet, but I'm sure he'll be very, very soon going to be coming out with a tribute as well. But let me know down in the comments below, Roger Federer moments in his career. Give me the highlight of his career in your eyes as a Federer fan or maybe you're not a Federer fan, just a tennis fan. What was the best memory that you'll take away from Roger Federer's career? So Roger Federer retired but never forgotten.


Welcome traders to another Tickmail Weekly Market Outlook for a week commencing the 6th of February with me, Patrick Munnerley. After last week's excitement, it's a much quieter week in terms of data and events in the US with activity data softening and inflation cooling. The market remains unconvinced about the Federal Reserve's desire to raise interest rates as a couple more times, as outlined by Fed Chair Powell last week. A recession appears to be the base case with expectations of policy easing in the second half of the year, which is putting downward pressure on the dollar and US Treasury yields. This is going some way to undermining the effectiveness of the Federal Reserve's rate hikes at the short end of the curve as it battles to ensure inflation is eradicated from the system. Consequently, the highlights of the week will likely be Powell's appearance at the Economic Club of Washington. If fee fails to push back meaningfully against the market reaction, the implication would be that the Fed itself is relaxed with what the market is doing, which risks it pushing further in the direction of pricing future interest rate cuts. Several other Fed officials are scheduled to speak this week as well. In terms of data, it's largely second tier releases, although the trade balance could be interesting. It has narrowly narrowed sharply through 2022, contributing positively to GDP growth in the second half of the year, but this appears to be unsustainable. It was driven by falling imports rather than rising exports, and markets see a strong chance that it sees partially unwinds in December. Meanwhile, the conference board's measure of consumer confidence is expected to improve given the rally in equity markets and the falling gasoline prices, with a strong jobs market continuing to provide a firm underpinning for now. From a technical perspective, the Dollar Index broke to the top side on Friday on that blowout jobs data, and we are seeing the strength sustained here as we start the week. So I'm looking for any three wave corrective move back into test resistance, prior resistance, and as we're out to support in the 102, 13, 102, 50 area, what should bullish reversal patterns there to engage on the long side, and we're looking ultimately now to test trend channel resistance 103.70s. At this stage, we take a close back through 101.20 to retest prior cycle lows at the 168 level. Moving to the Eurozone, in terms of data this week, let's take a look at the slate and see where we are. We don't have anything really of note today. We do get German industrial production tomorrow, Tuesday, looking for negative 2% print there, likely to experience a few volatile months in that data. And that really does round out the data out of the Eurozone this week. It is, like I say, a very quiet week from a data perspective. Technically though, if we look at the Eurodollar obviously trading inversely to the Dollar Index, seeing a nice initial decline to the downside impulsive, and we are now looking for any three wave corrective moves back into the 108.90s, 109 handle, what's bearish reversal patterns there to engage on the short side. I'm looking now for a move down to target weekly projected range support, the high volume node 106.20 monthly projected range support just below their 105.80s. At this stage, we'd really need to close back through 109.80s to suggest a false downside break and a resumption of the uptrend. Moving to the UK, an artificial bounce in activity after the Queen's funeral last September suggests the economy will narrowly avoid entering a technical recession in the fourth quarter of last year. Nevertheless, markets expect a modest contraction in the first quarter of this year, and probably the second, meaning recession is still the base case. It is however likely to be a very mild by historic standards, not least because the recent fall in gas prices now means that the government can probably cancel April's planned increase in household energy bills. And indeed, they'll probably have fallen from the current £2,500 annual average to about 2000 by the summer. In terms of the additional data in the UK, we don't have anything of note apart from Friday's December trade balance. Weaker consumer should narrow the deficit in 2023 from the 180 billion seen last time out. And then we get Q4 GDP, likely that the recession is going to start, like I say, the first quarter of this year or the second quarter at a minimum last time at negative 0.3% from a technical perspective, sterling sort of strong reaction from the resistance up at that 124 handle could not get any traction really above them. We have since seen an impulsive move to the downside. So I'm looking for any three-wave corrective moves back into test 121.50, 121.60 resistance, look for an extension to the downside. We're looking for 119 as the next downside objective. Ultimately, I'm looking for a retest of those lows printed at 118.40s. In Japan, no data of note today. We obviously have had a chatter overnight regarding the replacement for Governor Koroda. Amemire is considered to be a dovish pick if he is indeed going to be the new chief. The government were quick to refute those claims overnight, but that is the chatter in the markets at the moment, and that has led to some yen weakness overnight. Tuesday, we get December household spending, looking for a negative 0.4%. The labour market should be a bit more supportive there as uncertainty starts to fade. Then on Wednesday, we get December current account balance looking for 100 billion yen there. China's reopening should be supportive this time out, and that rounds out the data in Japan for the week ahead. From a technical perspective now, the dolly yen has broken out the descending trend channel. I'm looking for some consolidation here. Ultimately then, as we find support into this low volume area, 131.30s and the gap, as that area tracks buyers, then I'm looking for bullish reversal patterns to engage on the long side. Next upside objective is going to be into the 134.70s, 135 area where we have weekly and monthly projected range resistance. Moving to Australia, RBA decision to Tuesday, looking for another 25 basis points increase there to take the rate to 3.35% tightening cycle continues, responding to the inflationary challenges that the Australian market is experiencing. And then on Thursday, we get December weekly payrolls looking for a 0.7% print there. Summer holiday collapse could be larger than usual down under this time. And then on Friday, we get the RBA statement on monetary policy, just a general forecast update there. So from a technical perspective, Aussie dollar in line with a lot of these FX majors, obviously we saw that dollar strength into the back end of last week. I'm looking for another extension to the downside, test support into the 68.60s from there. We watched the three-way corrective patterns back into the 70.50. What I'm looking for there then will be the second leg to the downside in this corrective move. Ultimately, we're looking to challenge trend channel support down to 67.60s is the ultimate objective before we can consider the resumption of the uptrend in the Aussie dollar. And last but not least, let's check in with Bitcoin, see where we are as we open the week, Bitcoin consolidating over the weekend. And I'm looking now for a push down into support the 22,200 area, which are bullish reversal patterns there. Once again, look again on the long side. I'm looking for a test of the yearly pivot, which comes in just below 27,000. And that concludes the weekly market outlook for a week commencing the 6th of February. As always, trade us, plan the trade, trade the plan, and most importantly, manage your risk. Until next week, thanks very much.


Good morning, John. I'm kind of a sidelines fan of a very complicated competitive card game that I started playing in the 90s called Magic the Gathering. I don't really understand it anymore, but I do watch people play it on YouTube and I kind of follow magic news. And one thing about magic is that each card since the game was created in the 1990s has featured a piece of art created by a human artist. And that's created like a strong and interesting relationship between artists who make fantasy art and the company that makes this game. Because of that, this company, which is now inside of other larger companies, of course, has said that they will never use AI generated images as art for cards. Recently, the Magic the Gathering Twitter account posted this image featuring reprints of some of the cards talking about how great they look. And I agree, they do look great, but the focus immediately shifted to the background image. Which, if you know very much about images created by generative AI, this looks like that. Somewhat wildly, the Twitter account then doubled down saying, no, this is definitely made by a human we promise, which is like weird because that means that somebody looked at this and they were like, yeah, that seems like it was made by a person. So for whichever person that was, and also everybody else who might be interested, let's take a quick look at how you might be able to identify an image that was created by generative AI. I really just have three simple steps. Number one, look at the image and think about how it would have been created. Is this a photograph? Is it a 3D model? Is it a digital painting? If this was a world before generative AI, I would have been forced to think that this must be a composition of one or more photos along with possibly some stock photographs, also maybe likely some digital painting in the background. But who knows, a lot of things are possible. Maybe it was made for some other reason and then repurposed for this, whatever. Step two, don't look at the image as a whole.  Why are these little things coming out of this thing? What is going on with these lamps? Do they have two sets of filaments? Why do they kind of blend into each other? These wires make no sense and the gauge, yes, the gauge, AI is currently terrible at letters and numbers, but these are super crisp, except like over here where they are not, almost like the gauge was super messed up and then someone photoshopped a real gauge on top of it. And oh my gosh, look after a quick reverse image search, I found the exact gauge that was used to do that. But the final step, and I think the most important one is to recognize that none of this matters. It doesn't matter for two reasons. First, because these models are just gonna keep getting better and whatever tricks you're using right now to figure out if an image is created by artificial intelligence, you will not be able to use those tricks in even one year. But the second reason it doesn't matter is the more important one and it is that we are not going to closely scrutinize each one of the hundreds of images that we come across every day. Now, we do scrutinize something when it raises a red flag and there are a few reasons why that might happen. It might kind of look like AI art to us because we've seen a lot of previous AI art and then we might look closer. We might scrutinize it because Magic the Gathering is owned by Hasbro now and we don't really trust them with the thing that we have loved since 1995. But oftentimes no flags go up and you just accept it. Like this was the story of the Puffer Pope.  But at a glance, that just looks like the Pope in a custom puffy coat.  But most people don't think about the Pope a lot so we don't know what he would do. It just looks like a funny thing and then we move on with our day. The question of the modern day is not whether we configure something else once we choose to scrutinize it. The question is when and why do we choose to scrutinize things? Which if we vibe with it in whatever way, we generally choose to not do and that's not just an AI image generation problem, that's an everything problem. The Magic the Gathering Twitter account later confirmed my suspicion which is that they had trusted a vendor who had told them that it was not generated by AI, but it was. And if you're wondering why this was such a big deal to a lot of people, there are a lot of reasons that I am more and more convinced by that despite the fact that AI image generators are super cool and fun to use, they are not necessarily like gonna be a good thing at least the way they're currently operating for the most part. I don't have time to get into it right now but I would like to maybe get into it in a future video because it is I think both fascinating and important. John, I'll see you on Tuesday. In the 24 hours since I recorded the first part of this video, the temperature in Missoula has dropped from like 30 degrees to negative 11. And that's why I'm dressed like this now but I wanted to do a quick message for anybody who might have $500 or more to donate to make the world a better place and you also wanna amplify the impact of that donation because right now the Project for Awesome matching fund is open and it closes in about a month. During the Project for Awesome we have a system where every time someone donates a dollar then another dollar gets donated from the matching fund and we build that fund up from people who have enough extra money to donate a substantial amount. So if you have $500 or more to contribute to that effort there's a link in the description and I'll have a bunch more information about the Project for Awesome for you next week because things are gonna be a little bit different this year, not like a huge amount but enough that I'd like to talk about it in a video. And I'm gonna be in Los Angeles next week and I tell you about all the places I'm gonna be but everything has sold out. Thank you, I can't wait to see everybody who comes out to the shows. John, I already said that.


This paper discusses the importance of effective communication among IT professionals, as well as the challenges associated with this type of communication. It highlights the need for improved accuracy and understanding across a wide range of people, and the use of various forms of communication such as synchronous and asynchronous methods. Additionally, the paper explores how cloud technology can be utilized to facilitate better communication between IT specialists and their colleagues. This article was authored by Svitlana V. Simonenko, via Cheslav V. Osadkii, Svitlana, O. Sisyova, and others.


Bladder cancer it's not something you hear about all the time, right?  It is the same thing, but it's not that common However, it is something that's not very forgiving or hasn't been for a long time And the reason is because there wasn't a lot of treatment options for one bladder cancer doesn't really happen too much When you're younger the reason bladder cancer Theoretically happens or one of the reasons outside of trauma or you know those kind of things is that when you're you know Urinating you're having toxins come out. Well those toxins have to be basically collected in one place before they're Evacuated into the toilet and that's your bladder. So over years and decades those toxins that you're urinating out start to accumulate in the bladder Which is why smoking for example is definitely linked to bladder cancer However, when you get older, it's also harder to tolerate intense regimens, right chemo And unfortunately for a very long time there was an intense regimen With multi-agent chemo therapies that most people can't tolerate and then there was a dual Chemo regimen, which if you couldn't tolerate the intense one, that's basically all you had and if you couldn't do that kind of out of luck Well Immune therapy came out relatively recently Which does improve bladder cancer and can qualify for people that cannot tolerate chemotherapy finally Finally, it's happened to where now we have actionable and targetable Mutations that we can do with an oral pill to help control disease now It doesn't just have to be stage 4 or metastatic the key term is muscle invasive bladder cancer That's the key every biopsy report should say is it muscle invasive? Is it non-invasive bladder cancer being kind of like DC is right that stage 0 breast cancer? It's not invasive yet. So stage 0 that's not invasive if it says no muscle present The recommendations are to go back and biopsy because that is the key. Is it invasive bladder cancer or non-invasive? And the regimen for non-invasive is all kinds of things kind of scrape it out put some stuff in the bladder Let it wash around take BCG But the invasive category is totally different and that goes down into what we just talked about Chemotherapy number one that's intense little less chemotherapy was nothing else now There's immune therapy and then FGFR That is a targeted therapy that we know works even in other tumor types like Calangio carcinoma That needs to be tested because it's way more forgiving than chemotherapy multi-agent chemotherapy How do you know if you've been tested you have to ask your urologist or oncologist? Did I get molecular sequencing or NGS next-generation sequencing or Profiling on my tumor if you did not get that Hundred percent of you will not be able to get this oral therapy that can potentially control or make the disease disappear for some time Nobody will be able to qualify unless they have that testing which is why it's so important to get that NGS testing on your tumor type It's approved. It's covered by insurance and really should be ordered as a standard of care


Yeah, good morning. So I'm Frank Baudin. I'm a product manager for OpenStackNV at Red Hat. Morning everybody. My name is Uriel too with Intel. I work for the data center network solution group part of the data center group and what Frank and I have in store for you today is some introduction. Hopefully the light is actually in my eye so I can barely see you but introduction of FIDO, FDIO to the OpenStack community. Hopefully some of you have heard about it before and maybe some of you have not. So there is lots going on in that community. We are not going to be able to cover everything over here. We wanted to give you some of the key highlights, explain what that technology is all about and why and how it is relevant to the work that we are doing here in OpenStack. So we'll start with what is FIDO, what is the community, who's in that community, how that community works. Frank is going to go into some depth about the fundamentals of the technology that is used by VPP which is one of the projects under that bigger umbrella of FDIO. We'll give you some examples of a few different projects and few different approaches how this new data plane can integrate into components that supposedly are well known over here specifically OpenStack Neutron and Open Daylight and some options that are independent like Open Daylight and SFC directly and we'll talk about those options. Obviously in OpenStack community these days you cannot present anything without talking about containers. We are not going to break that tradition either and show you how this technology or this set of technologies I should say is relevant to the container discussions we are having. We have borrowed heavily from a large set of people who are working in this community and we want to thank them for some of the slides that we stole with pride. What is FDIO? I want to start with putting things in a little bit broader context before we dive in. Basically as you could see it's a high-speed programmable data plane that runs on the infrastructure that we use in order to fulfill what OpenStack is trying to do, what NFV is trying to do and so on, namely on on some servers. You could see at the bottom the fundamental layers or services and we'll touch on all of them what role they are playing. The bottom layer, DIO is really comprised of DPDK, the data plane developers kit. This is a technology that has been there for I believe about seven years or so and this group is also in transition. They are moving from an independent organization to a location to be advertised soon, most likely into the Linux foundation as well, but what DPDK provides here is a set of software libraries that are tightly coupled and matched to all the innovations and progression of the server architecture and therefore what you have is a set of primitives that would give you as close as possible to the capabilities of the underlying hardware technology. On top of that, the layer referred to on this slide as processing is the VPP and Frank is going to cover that in detail so I'm going to leave it for later, but basically it rides on top of the DPDK. It utilizes capabilities in the server that supports vector processing and it adds many other network related services and technologies as you'll see in the rest of this presentation. The other layer here, the management agent is a capability to control all of that locally or remotely and again we are going to show how all of that comes together. One option and we are going to go much deeper into it right now so I'm not going to take the time at this moment is to layer that such that this server resident data plane hooks up into an SDN controller like Open Daylight and Open Daylight has already known interfaces into OpenStack. Some innovation is happening on those interfaces in the context of FDIO and we'll talk about that, but that is putting things in a little bit of perspective. So the takeaway, these are the layers differentiate between what FIDO as a bigger umbrella gives you and what VPP is providing as a set of services as you could read from the slide, it's one of the key projects. What is the community all about? What are the key tenets? What are the key things that this community is trying to do? And maybe the four key elements that we want to touch on today you have these community members as you could see on the upper left side. Almost these days in the industry standard tiering of platinum and gold and silver for a community that was established just a few months ago. Very impressive acceptance by the industry and open source doesn't obviously go without a community and community is benefiting and the project benefits significantly from the right governance and for those of you who are familiar with the Open Daylight governance and I for one am with the Open Daylight community for a long time the governance structure that we have here really is from the good lessons that we all learned from the Open Daylight with a few announcements and maybe one of them that is worth mentioning I'll mention that on the other slides is the concept of sub projects that could individually progress and individually release and that is something that we did here intentionally to allow as large diversity of communities and projects come together under this umbrella. So the good governance goes hand in hand with the fast progression of the technology and the community and with enabling innovation and that is very important. The scope now you are familiar after the previous slide with these three layers and you will see that actually the community not only works on the data plane itself but also works with OpenStack with Open Daylight to name few other communities in order to make the data plane available to those orchestration solutions. Another element that this community brings to bear here which we believe is probably the first attempt to do something like that in the industry is to provide some sort of a CICD environment where if you with your project that you contributed to the community have a new feature that enhances functionality or performance there is a lab that is running in the background and enables continuous testing of that making sure that no new feature that has been introduced is going to cause any slowdown of the performance. So we want to make sure that we hold two flags as high as we can not only features and functionality but the performance aspects as well and that is the role of the CPL that was supposed to take me to the next slide and it does. So some of the projects that we have in the community starting again from the bottom we talked about that layer VPP which we are going to double click on next and Frank is going to cover that. Some of the projects and due to shortage of time here this morning we are only going to cover some of them. We will cover NSH, SFC that service function chaining technology and we'll show how it works in in this context. One I would not say one and only but it's an overlay network engine that is based on LISP technology and it is an attempt to show better scalability and ability to actually do overlays end to end supports multiple technologies we are not going to cover that in more details and you will have pointers here to the community wiki and you could get those informations. We also have here the concept of a sandbox which really allows the community the developers to play with new features that they want to add in a confined environment make sure they work and then they could launch that into the rest of the project and another piece that we are going to lightly touch on in this presentation this morning is the transport layer developer kit. This is an attempt to add the full functional tcp stack for those cases where such processing is required but all of the processing that we do in the context of fdio as it is based on dpdk is in the user space so when we have traffic either emerging from the server or ingress into the server that traffic is taken out of the kernel moved into the user space and therefore one would need to have a transport layer that transport layer for those use cases where it's required is going to be and that is the design goal to be much faster than the one in the kernel. On the right side we have a set of packaging options for popular distros and we have exercises like the trex and the continuous testing and integration that is part of the project and the last component here is the honeycomb. The honeycomb is that agent that resides on the server on top of the vpp layers that allows one to either manage that functionality on the server locally or hook it up remotely using netconf, resconf technologies in order to interact for instance with an open daylight. You have more text here on the governance are probably just going to hit a few key points here it's a fully open technology anyone could contribute you get to a commuter based on merits based on a recommendation of your friends. I mentioned earlier that we did something a little bit different here with the subprojects where subprojects got much higher level of autonomy than you normally find so anything that is defined as a subproject could also release independently and we also preserve that kind of coupling and decoupling of the board from the TSC so the board is focused on the business aspect and is not giving technical direction to the developers the technical community interacts with the board on business issues general direction but not more than that. You could see some of the rather impressive activity that is happening for a community that has just launched few months ago and we'll show you not only the functionality that is available today but actually also the fact that this technology is getting very very close to production and maturization on some aspects while there is we have many plans to do additional work and another project but provided some statistics for you so that you could relate to this and with this intro over let me hand it over to Frank to cover some of the fundamentals of the technology. Thank you. So what is VPP? So VPP is a protocol stack made of graph nodes so to take an example when we have let's say an IPv6 packet getting in we go into an internet input pass the header we that's an IPv6 so we go to the IPv6 input node then to the IPv6 lookup you find your exit route and then you go to the node to transmit the packet basically so far nothing during you now this is vector base so instead of going through the graph packet by packet you go with a bulk and 256 packet up to this is the value that is a default one today as a benefit you will always have processing packets by 256 in a node so your instruction cache is hot you don't have instruction cache miss and also all of the nodes are implemented in a way that you process the packet always 2 by 2 so I've got a first packet that's an IP header so I'm doing the instead of doing a lookup in the floor table I will prefetch based on the IP address the sale of the floor table lookup corresponding to the floor then I will prefetch for the second packet and while I'm back on the first packet uh the the sale entry of the routing table is in the packet is on the CPU cache so I don't have a cache miss by processing the packet 2 by 2 and I'm interleaving them so no data cache miss no instruction cache miss thanks to very clever prefetch and interleaving packets processing and a quick comparison with the ovs paradigm so we have a compiled graph when you have a you have a bulk of packets going through uh the graph node and exiting while with ovs you have a data pass and a control plane a slow pass so basically with ovs the packet gain in and if it's in the cache it gets out of the it gets out very fast if it's not in the cache meaning that's a new flow it gets in the control plane and go to a very very long pass compared to the cache and then you add an entry in the cache and then you go back so vpp has a kind of deterministic time of traverse all all packets are equal when you enter vpp while with ovs the difference is if you're a packet from you from a new flow you're going to be much slower another comparison with ovs is vpp is uh confless when you start vpp all the nodes have no configuration so an external agent has to push the configuration and i'll come back on that later on and finally vpp has no kernel implementation counterpart when you want to implement something in vpp you implement it once not twice you don't have to implement kernel and use the language you implement a node and you're done so it accelerates developments in term of portability so um vpp is portable on multiple architecture x86 ARM power pc and could be easily ported on other architecture it's ported on various operating system because it has an abstraction layer of a very operating system named celib that you have to implement for all operating system something very classical in term of nick supporter what you need is an so what is a driver a driver is an input node so what are the input nodes available today we have dpdk tune tap af packet net map and even legacy driver don't ask me why it's there i don't i don't think you will use them but anyway and last but not least the host user to interconnect vm to vpp also you have also a shared memory implementation named ssvm plus others that will come which is typically uh a faster shared memory that could be used between containers for vpp instances being in different containers i'll come back on that later on also vpp has some nodes which leverage hardware accelerator like for instance for ipsec so you go to your ipsec node and then you can offload some ipsec ciphering deciphering in hardware and you can deploy a vpp on the host bare metal as a v-switch as a router in vm in containers and a little trick from vpp is the critical for instance the ip lookup table nodes are compiled with various cpu option optimization so if your cpu is old an old version it will work but if you have the latest greatest avxv3 and you have an optimized lookup function it will dynamically use it you don't have to have a so one vpp version can work on older and latest greatest cpu so that's very practical in term of modularity flexibility so first it's easy to build up your graph node for your use case so you create your stack for your for your need now you can add plugins and the plugin is often a sub project in vpp so a plugin is a bunch of nodes uh that can rearrange the original graph uh that uh that can be built independently of vpp source tree and that can be added at runtime and of course that can extend the configuration api so for instance uh nshsfc is one of these plugins and once again all in user space so it's permit to build v switches, vrotor, anything processing packet so now we have nodes we have a nice framework but as a developer how do i debug this framework so vpp comes with a lot of embedded telemetry so not the open stack telemetry so for instance that's an example of counter so uh here i've got statistic per node and we can see per node how many calls how many vectors you know the vector that's a 256 packets how many clocks are spent in a given node and how many packets are so in this example i'm at 256 minimum i was quite loaded but not 100 percent so this is a very basic graph node but when you have something complex don't be afraid you have the tools to debug something very nice tcpdump so i want to tcpdump in my vpp graph node so what so this is uh this is a real screenshot like the previous one so you uh here i'm asking to get 10 packets on vpp and for and then i'm showing the trace this is something which is put in memory so it does not affect so much the performance so and i've got per node a lot of depending on the developer node a lot of or a little of traces and also time stamping per node so you can follow your packet in the graph node and identify a bottleneck if any so that's very handy vpp has a v switch v router so we are all here at open stack summit and the vpp first use case from my perspective as an open stack product manager at redhat is a v switch so how so first how neutron implement how the neutron implementation with vpp is based on bridges so when you create a tenant you create a kind of bridge object from a from a vpp perspective that will interconnect all of the ports it's very simple to understand if you want to implement a v router you will create a vrf which is a routing table that will you will interconnect with nodes uh the configuration has to be pushed and stored by an agent because as i said vpp is complex so you need to have an external agent so that's very modular so vpp is really modular by essence inside and also it does not want to do everything it just do packet processing fast uh one little note because that's my uh that's my favorite topic benchmarks so most of the benchmark in the wild today are either physical to physical either uh cross connecting ports with vm's which is fine which is a good step ahead but still not with open stack so uh just to say that most of the benchmark that you will see in the wild are not representative of an end-to-end use case with open stack it does not mean that the performance will be lower it just means that people take a shortcut to make the benchmark and we are working within opnv project to provide you end-to-end benchmark uh with vpp and with other v switches with open stack because that's easy to cross connect ports but now if you have a very complex topology uh of graph or something maybe the performance will collapse so we need to benchmark the end-to-end use case also just to say that vm's are connected via vhost user ports and today vpp has a specific vhost user implementation which is in fair competition with dpdk uh vhost user implementation and fido people and dpdk people are working together to take the best of both to finally come with one version so that will converge this is work in progress and uh this so last week we we were in in dpdk summit and we have seen a lot of people working to improve this performance because phost user today is a bottleneck for any v-switch including vpp so uh later on you can click on this link and get a full report about vpp performance and there is a thread on the mailing list about the performance of vpp comparison with ovs dpdk and nobody at fido or ovs dpdk is afraid of the comparison that's open source this is a fair comparison with real real arguments no marketing so today that's number that we've seen but once again i said this is work in progress we're working on the on the benchmarks vpp features so you can go on the website it will be soon updated i guess and uh so you have plenty of features more than you want more than you want the 16.09 bring you the latest dpdk the next version i guess with rebase by heart on the latest dpdk so vpp is always up to date regarding dpdk so far it brings some uacl which are uh useful for security group for neutron a lot of enhancements that i will just keep so i'll let you have a look by yourself and the the dual of the chrome from my perspective as a product manager that's their ci fido has a really great ci so name cc it basically uh the ci include performance test non-regression with these 15 tests so every time someone try to submit a patch if you have a regression in performance the patch does not pass the ci gating so that's really cool also for a given version of cc of sorry of vpp you have the test results available with for all of this configuration so you want you want the data you just get it get there also you can download cc to install it in your lab because that's all open source you can run the same test all is open no tricks regarding uh yeah sorry i've been i've been quick because we are kind of yeah kind of pushed by the time so uh from an open stack integration we have two paths first path is ml2 direct ml2 so there is an ml2 plugin which has been pushed so you have the link to the announcement so it's based on it cd and you have seen that in the fido community you have a calico which is also using hcd so i guess this is a coincidence there so uh basically you have an ml2 uh mechanical driver on the server which is pushing via hcd the configuration to the ml2 agent that uh store the configuration and in terms of features so we are not priority feature yet with neutral with ovs but we are closed so for instance today you can restart your vpp agent you can restart the ml2 driver and it's supported so i'm fast but uh basically it's connected to the qrotor the qd hcp and uh in term of distribution it's integrated in apex tripolo installer so if you take apex tripolo installer you can deploy the ml2 plugin end to end and it's also included in dev stack a next item in the in the ml2 roadmap is a security group to be fully implemented anti-spoofing tap as a service and for the version later vxlan support and integration with telemetry systems and with that i will hand on to uri so that's going to be a bullet train through the next few slides given time here uh the other option that that we have is the fast data stack uh with the fast data stack there is a different ml2 interaction with uh with the neutron um stack and you're utilizing the group-based policy stack all the way from um the top into uh open daylight in order to render whatever you need on on a server node give you um some more detailed example of uh of how it works so when neutron creates its uh uh post port command which really is about adding a new port um the following layers that are part of the open daylight implementation uh kick into uh into action uh the north bound which is uh the active layer over here is going to store that information in in the new uh neutron uh data store and uh group-based policy um is going to be on a listen mode and it's going to catch that information that the new port is being requested to be added and it's uh part of the nodes that it uh covers and it's going to be as an example a node that needs special configuration on the host like a vv host that's the interface that frank was uh showing uh earlier so uh the next step in the progression is to create a group-based policy uh endpoint and now we have um we add the policy say the policy would be um in this particular example something about let me create a vxl and tunnel between these two endpoints you'll see on the left side uh vpp one is that case where i have a virtual machine in the case that i have a virtual machine i need to take two types of actions one is the local configuration uh which in this particular case is about connecting a virtual machine using a vhost to uh the v switch that vpp um exposes and that's um that error but uh we also need to configure the quote unquote v switch in order to create the v tunnel and that is the other set of activities as you could see vpp2 as an example doesn't have a virtual machine so one of the steps is skipped um another uh example and again for shortage of time i'm not going to introduce this slide um at depth because we want to leave a few minutes for the container as well but this is um another technology the itf version uh nsh based where you have service functions as you could see over here the key idea is that i want to direct my traffic along a graph and i want to set my resources size them up in an efficient way so that only the traffic that needs to hit the resource really has to hit the resource plus adding the capability of metadata which is a standard way to allow those nodes to communicate with each other whatever information policy based classification based that you accumulate you could now uh progress through the chain uh with the rest of your traffic um this is what uh we we support uh over here and um the overall open daylight sfc architecture has been enhanced to include uh the vpp renderer that as you saw on the previous slide is that entity that uh that allows us to configure a vpp service function so that we create the right tie to the vswitch um and this is a fully compliant uh implementation in parentheses i would say that uh it would be really useful for us as an open stack community to take into account fido with this kind of services and functionality and implement against that at the moment we limit ourselves to a subset of the data planes that are available and therefore we are having difficulty releasing features as they almost the standard is finished and as open source we are not yet supporting that um this is an example of what frank was referring to earlier where you have the different nodes in the graph and you could see how uh the vxlan gpe combined with nsh processing is being plugged into the graph this is the way a project in integrates and inject itself into um the rest of the nodes that we have on the graph and we do not have time to go into the detail you could find um some of the information on the release on that pointer thank you ry so i'll be brief today's container so this is an example of two containers talking to each other via tcp on the same machine so you have two paths so uh the first container that's an application open a socket have a send system call go to the stack go to um a veth so if this is obvious it go backs between two vt v two of yes another v um another device and then back to the application with uh vpp today so we have a pair of veth that connect the dots because uh the advantage of vpp is being user learn for fast development but here you have no kernel implementation and you will see that on paper at least on slide these look longer but what are the numbers i don't have them they have not been published and also this is not a very targeted use case for vpp but people are working on that within vpp so this one i'll be brief basically so what you try to achieve is a send and receive to go via a five four and you completely bypass the tp cp stack but this assume that you will have a lot of tcp connection between two containers and i would say this is not very nv uh centric because nv is about packet coming from a cell phone going to the internet so you don't expect container to create packet on themself but this just to say that with vpp you can research and try to solve very complex problem and go for something very complex like this this could last for a complete presentation but now so we have on the right today and tomorrow so what i want to show is vpp is a future proof regarding container developments what we have today as i showed before is legacy container being interconnected to the v switch so between them and to the outside world via uh the host kernel via per vth port and an f packet socket now you can run dpdk based container on top of vhost user and you will say but you show me before vhost user is a bottleneck but i told you that the bottleneck will be uh okay we're going to optimize it drastically in the coming months not weeks and then if you want to go further say okay vhost user i want something even more fast so if you have vpp in the container and vpp out you can take any shortcut that you want apply any policy that you want because that's you just need to have the proper node in the container the proper node in the switch and you can either buy even bypass the switch if you want so just to say that there will be a lot of innovation in this field in order to have fast communication but as there is no free lunch if you want some multi-tenancy you will have copy but in some cases you can optimize okay that's the same tenant maybe i can so just to say that vpp is a is a good fit for this kind of development i'd be very quick on this one so today vnf developers are quite puzzled about should i go to vm to container mix a lot of vms today are big large vm that take consume a lot of memory coming from a legacy world but uh and people start to slide them into container into vm and i have to say i have no answer but what i can say is vpp can handle vm containers that's it and then that's an orchestration issue so whatever is the future vpp is there for the vnf so what we've seen is that on the production side vpp is quite mature despite being a very very recent projects because it has a lot of counter everywhere trace documentation training i encourage you to go to the fido uh wiki page you have a lot of session which has been recording a lot of hands-on exercise you have a very active community just look at the mailing list very open uh they have open weekly code they have a great ci gating ci based on cc that you can put in your lab it's still a very new project but as soon as it would be mature enough so what's mature enough we'll discuss in the community uh we're going to have an lts version of vpp so good for production and uh the goal of fido community and opnv community is to bring opnv rdo integration uh integrated by okata so people can go on poc with okata open stack version and evaluate vpp for real end to end in open stack and give number publish them we'll be happy to get them in opnv and opnv will publish numbers on the innovation pass uh if you want to to to work on the next big thing thanks to the portability the modularity the ease to add a new protocol the sandboxing project okay that's a very good vehicle for innovation and you already have a lot of cool stuff there including containers nsh lists whatever and now put just for okata so let's think about okata what do we need for okata so dpdk properly integrate so we need we need centers dpdk people to work together we need open stack open delite triple low integration to be in rdo so you can install rdo properly with in opnv and get your end to end use cases in opnv that's my last slide thanks for your attention do you have any questions probably have a few minutes here for questions if anyone has any questions or you're all overwhelmed with the innovation the pace of the technology hi i have one small question my name is gal you said i saw that you said that vpp support arm but you also mentioned that it relies on intel uh vectoring instructions so how that works together it's very simple it's portable so you just recompile it and uh you have the cd but you have an abstraction layer so the vector is okay you can use the vector instruction to optimize some things but it's different from the vector packet the vector packet is the table of packet if you want to see so it's not it's not tightened to intel it's worked well on intel okay thank you any other questions just to add to that response actually for those who are not aware dpdk for quite some time while its origins are clearly with intel is another open community supports multiple architectures as well yeah yeah there was another question here okay do you want to take the question is what's the advantage of vpp against other v switches so i would say look at my slides i guess that's a great framework that's a great community that's that's really for nv so that's my answer second one the load balancer is entering you have different maglev implementation ongoing for load balancer within vpp the result project so just have a look at the mailing list and you will see some activity there so for uh for the first question if i may i'd like to add few more points uh maybe two key points one is uh the direct attachment and reliance and taking advantage of um the tight coupling to the underlying forwarding that the platform can offer to you so that happens because vpp is a technology that has been there for uh long time its origins are 2002 dpdk is also a technology that is there for multiple years they are both mature and they are designed for the ground up so they are designed to take advantage of all the innovations that the cpu architecture can deliver and the server architecture as a whole so what you will see is that we you could think of it as we have a revolution of software as an example software evolves from our client server virtualization containers you have a revolution of hardware we take the hardware evolution and we make that to be as useful as as possible as frank showed earlier well uh you still the bottleneck may move as as as we progress on the technology but you are starting from the foundation you are relying on the best the platform can do as we clear all the bottlenecks that is supposedly going to emerge as a as a performance leader efficiency leader but there is another angle and the other angle is really looking at the problem more in a network centric fashion we gave you one example of of sfc over here there is a the whole notion that as a community you could add features that comes to play in two ways it comes to play first of all with the openness of the community you could walk in and you could add a project we are working for multiple years to add sfc to other data planes still it is not there so you have richness of all the network protocols there are other attempts in this community to get the network to offer a broader set of protocols that as an example nfv would would require this platform is designed to do that so so you could benefit from it and these are just just few a few examples the other the other maybe little note i would like to add is because things are in in the user mode you are not also dependent on the pace the kernel itself is moving there is a given take over there obviously sometimes you don't need the additional performance sometimes you would like to use the kernel but if you want to move faster if you have innovation you could take advantage of that so you want to do the full comparison any other question okay thank you guys hopefully that was useful