Okay, these are quick videos on shell script just going over the basics as quickly as I can so we can get some more fun things But so far we looked at printing stuff out to the screen with the echo command and also putting things into variables like so if I could type today echo dollar sign X or More proper like that but besides Creating the variables ourselves. How can we get user input now? I'm going to show you this It's going to be a lot more useful once we actually start writing scripts Rather than just typing stuff at the shell at the command line itself But you can use the read command and you can say read and we'll say in this case X So you say read and whatever you put next will be the variable the input is being saved to so I'll hit enter here And it's waiting for some input so I can just type in the word test Now the variable X which previously equaled hello now equals test So I can say echo dollar sign test Oh not test X and it says test so we can Now do the same thing we can call it something else that we can call it name so read name and I can now say Bob and now anytime. I've used the variable bar name. I will say Bob so I can say hello dollar sign Bob No, I'm sorry dollar sign name Bob Sorry my mind's drifting back and forth here, so Doesn't seem very useful when we're typing in the shell like this But as we get into actually writing out scripts and putting things in files that users can run it'll become much more useful so And we'll also learn a bit more about the read command and how you can Have it output stuff as well as get input But I want to show you the basics of the read command so you know how to get user input


Income tax 2022, 2023, inventory, uniform capitalization rules and changes in accounting methods. Let's do some wealth preservation with some tax preparation. Support Accounting Instruction by clicking the link below, giving you a free month membership to all of the content on our website, broken out by category, further broken out by course. Each course then organized in a logical, reasonable fashion, making it much more easy to find what you need than can be done on a YouTube page. We also include added resources such as Excel practice problems, PDF files, and more like QuickBooks backup files when applicable. So once again, click the link below for a free month membership to our website and all the content on it. Most of this information comes from the Tax Guide for Small Business for Individuals Who Use Schedule C, Publication 334, Tax Year 2022. You can find on the IRS website, irs.gov, irs.gov. Looking at the income tax formula, we're focused on line one income. Remember, in the first half of the income tax formula is in essence an income statement. However, just an outline, the scaffolding, other forms and schedules flowing into it. For example, the Schedule C, the business income, which has its own income statement in essence, income minus expenses or business deductions getting to the net income, flows into line one here of income of our income tax formula. This is the first page of the form 1040. The Schedule C would roll into the Schedule 1, which would roll into line eight of the 1040. This is a Schedule C, profit or loss from business in essence income statement with an income and expense part. All right, we're continuing on with our discussions of accounting methods in general, noting that the two major accounting methods that we may be able to pick are going to be the cash method, the accrual method. We might be able to do some combination or special method, but it's usually going to be a combination or have cash or accrual components within it, noting also that we might be restricted to some degree, forced possibly to do some more accrual method. One of them betrays the principles. If we have inventory, for example, and that we want to make sure we pick the proper method starting out, because although we have some flexibility to pick the accounting method, once we have picked the accounting method, we're somewhat locked into it and have to ask the IRS for a change if we want to change the method. Therefore, when doing the first Schedule C for the first small business reporting, you want to make sure you've thought about the method you're going to use and pick the right one because it could lock you into using that method. Continuing on then, we're looking at the Uniform Capitalization Rules now. So under the Uniform Capitalization Rules, you must capitalize the direct costs and part of the indirect cost of production or resale activities. Include these costs in the basis of property you produce or acquire for resale rather than claiming them as current deduction. So you recover the costs through depreciation, amortization, or cost of goods sold when you use, sell, or otherwise dispose of property. So note that when you buy something like equipment, for example, then even if you're on a cash-based system, you're going to have to put it on the books as an asset typically. And that makes sense, and that's basically an accrual thing that we have to do, right? Because if you were on a cash-based system, when you bought like a forklift or a building, you would just expense it at the point in time you paid for it even though you're going to consume it for a long period into the future. For like a building, it's quite extreme in that there would be a big difference between when you paid for the building, when you got the deduction, then if it was on a cash basis versus when you got the consumption or used the building in order to help generate revenue. And because that's so extreme, then even if you're on a cash-based method, we've got to kind of deviate from the cash-based method and do an accrual thing putting it on the books as an asset and then depreciating it in that case. In the case of inventory, we have a similar kind of situation because we want to try to match up the purchase of the inventory, not to the point in time that you paid for the inventory necessarily, but expense it at the point in time you consumed or used the inventory, matching up the cost of goods sold, the expense of consuming inventory to the point in time that you sold the inventory. So activities subject to the uniform capitalization rules, you may be subject to the uniform capitalization rules if you do any of the following unless the property is produced for your use other than in a business or an activity carried on for profit. So produce real or tangible personal property for this purpose. Tangential personal property includes a film, sound recording, videotape, book or similar property. Acquire property for resale. That would be an inventory situation acquiring for resale typically. You bought it to resell it. So exceptions, these rules do not apply to the following. So they don't apply to one small business tax payers defined earlier under inventories, and two property you produce in your indirect costs of producing the property are $200,000 or less. So once again, property you produce in your indirect costs of producing the property are $200,000 or less. So special methods, there are special methods of accounting for certain items of income or expense. These include the following amortization discussed in Chapter 8 of Publication 535. Then we've got the bad debts discussed in Chapter 10 of Publication 535. So amortization is kind of similar to depreciation. So except you're doing it for like intangible assets, for example, that you might have to amortize the value of the intangible assets over a certain time period. Bad debt is typically going to be an issue if you're dealing with accounts receivable, meaning if you have a type of business where you do the work first, you bill the client, and then you have to track the accounts receivable, then the question is, well, what if they don't pay you? Then if you already recorded the income in the past, then you've got this bad debt situation that you're not going to get paid. And the question is, when do you get to expense or deal with the bad debt? Because under accounting methods, there's an allowance method and a direct write-off method and so on, and you've got to tie it out to what the tax code wants as well. So depletion discussed in Chapter 9. So depletion is kind of similar to, again, like a depreciation type of situation, except you have a natural resource that you're actually consuming. So if you had like an oil well in the ground or something like that, you might have to try to value the amount that you're going to get out of that. And then as you start to use up the resource and pull it out, then you're depleting it and you'd have to record the depletion. Then depreciation discussed in publication 946, how to depreciate property. They just slowly depreciate. That's the one that most small businesses are probably going to be still subject to, right? Because that's what small businesses, when they will end up possibly likely needing to deviate if they buy equipment, large pieces of equipment, that should be going on the books as an asset as opposed to simply expensing them when purchased. Installment sales discussed in publication 537. So installment sales are going to be a special design of a sale when you have particular situations in place with regards to the sales. The sales happening in installments. So long-term contract methods of accounting. So that would be another industry specific type of thing. And that's in section 460. So that might be like for contractors that do long-term jobs because the revenue recognition principle will usually be that you have to record revenue when you complete the job. That would be when you give inventory, for example, if you're selling inventory or when you complete the service if you're doing service business. But what if you're in a long-term job and it's going to take you multiple years to make a building or something? Are you going to wait, you know, five years until the building is produced or should you use some other kind of revenue recognition principle recognizing revenue as you're building this long-term project which could include completed contract or percentage of completion, for example, those are kind of specialty areas. And be careful when if you're doing taxes for other people you might want to specialize in industry. So all of these items are kind of specialized to particular industries except depreciation which you'll probably deal with in most of the industries.  So change in accounting method. Once you have set up your accounting method you must generally get IRS approval before you can change another method. So a change in accounting method includes a change in one, your overall method such as from cash to a cruel method and two, your treatment of any material item. So that's why you want to get the accounting method correct the first time. You might have to change it in the future. You would think that the IRS would want some kind of rationale for changing it. So for example, if you now have inventory being a more significant part of your business and you were changing from a cash to a cruel method you would think that that would be something that the IRS would approve of in that case. But if you're just saying I just want to change methods just because can I change methods? Why? Because I want to. Then the IRS you would think they would be a little bit more skeptical wanting to stay with consistency in that process. So to get approval you must file form 3115. You can get IRS approval to change an accounting method under either the automatic change procedure or the advanced consent request procedures. You may have to pay a user fee for more information. You could see the instructions for form 3115. So automatic change procedures. So how do we do this? Certain taxpayers can presume to have IRS approval to change their method of accounting. The approval is granted for the tax year for which the taxpayer requests a change, year of change if taxpayer complies with the provisions of the automatic change procedure. So no user fee is required for an application filed under an automatic change procedure generally covered in revenue procedure 2015-13, 2015-5 IRB 419 which is available at the IRS website. So generally you must use form 3551 to request an automatic change for more information. You can see the instructions for that form 3115. 3115 that is.


proud now the question going into this season obviously we told you the underlying story early Jack was the fact that he said if nothing got done by opening day he'd be able to laser focus on the season depending on what happens with this contract right Bob and at the top of this show we talked about would today be both an opening day celebration for the Yankees and perhaps a celebration for Aaron judge with the contract extension and that's not going to happen. Brian Cashman the general manager addressing the media a short time ago he said there will be no extension done right now and the Yankees interestingly publicly stating what they offered to judge seven-year deal 30.5 million per season that would be the extension of around 214 million you add in whatever he would have gotten in arbitration in this year let's just meet in the middle at 19 million so the Yankees willing to go over 230 million across the next eight seasons that would be the highest average annual value they've ever given to a position player judge electing not to go down that road which sets up a very interesting 2022 he is a superstar he will get the loudest ovation today there will be more fans in the stands wearing number 99 the Yankees felt that was worth 30 plus million a year flash judge and his side obviously feels worth more. Well a lot of years and a lot of money probably more years than I thought the Yankees were willing to go for a guy who's going to be an older free agent but Jack the bottom line is Aaron judge is betting on himself and he's rolling the dice a little bit that's a very lucrative contract for a lot of years and a lot of security but Aaron obviously feels like you know at last year I was healthy I showed everybody what I can do when I'm healthy he's betting he's going to be healthy for a full year if he is he's going to be in the driver's seat. We've got more coming up with Meredith Barakovitz on this in just a little bit in the meantime


with the fighting skill of the American soldier, stand ready on the alert all over the world to defend this country, you the American people against aggression. This is the Big Picture, an official television report to the nation from the United States Army. Now to show you part of the Big Picture, here is Sergeant Stuart Queen. I wonder how many Americans realize what startling new methods in medical and surgical treatment are being developed for servicemen and their families, being developed by continuous research at special laboratories and test centers in the Army. The saving of lives through sensational new skills in the healing art is the subject of this section of the Big Picture. This is the military age of flame and fire, liquid fire, flash fire, rocket fire, jet fire, fire and flame and, this is the age of burned wounds. Even in wartime, there was never so high a percentage of severe burn casualties as now in peace, nor as high a percentage of recoveries from severe burn wounds. As the ratio of burns increased, the concern of the United States Army Medical Corps intensified. Out of the experience of army medics and their imaginative research, they're developed a group of army experts in advanced, unique and dramatically successful methods of burn treatment. Headquarters of the Surgical Research Unit, a component of the great Brooke Army Medical Center, is at Fort Sam Houston, San Antonio, Texas. To understand what is being accomplished here, let's follow one typical case, starting with the injury itself. Lieutenant Jim Leaton smashed up in his Air Force jet plane. When they pulled him out, he was found to be suffering from 40% burns of feet, legs, arms, body and face. Only a few years ago, burns of this nature and extent were almost always fatal. But with the new concept of burn treatment developed here, each day brought with it 24 healing hours. And within a magically short time, the patient was well on his way to recovery. And here we see him back at his home in Wilmet, Illinois with his sister, walking the old familiar streets. Back at the old familiar game too, with his thankful mother looking on. Back at the old wood chopping workout, just as those second and third degree burns hadn't covered almost half of his skin surface. In his convalescence, there is little evidence left of his massive injury. A happy testimonial to the talent, patience and daring of the Army Surgical Research Unit. So that this man who stood at the gates of death can walk out through the gates of his home to life. Perhaps you wondered how Lieutenant Leighton remained alive to reach Brook Army Hospital from the distant airfield where he was so critically injured. All such cases start with a phone call to the chief of the Surgical Research Unit from the scene of the accident. Medical men at the scene are instructed in emergency burn treatment and all aspects of the case are carefully compiled. Not long after that, a Surgical Research Unit burn team takes off in a military Air Force transport plane from nearby Brook's Air Force base. The 1734th Air Evacuation Squadron supports the burn team in the evacuation of burned patients. A heartwarming example of the integration of the services. Such mercy flights are constantly being flown to every corner of the nation to care for servicemen and their families in a time of helpless fear and pain. Priving at their destination, the burn team go at once to their patients. Their special medical equipment accompanies them. They see for themselves the extent of the serviceman's injury and prepare him for the flight back to Brook Army Hospital. Every device known to or developed by the unit will be used to sustain him now and during the flight. Their experience with burn wound care enables them to start at once the type treatment best fitted to halt the effects of the injury. Then they prepare to return with their patient who is receiving shock-allaying fluids, including whole blood. Intensive treatment continues throughout the entire evacuation. During the flight, the plane serves as a flying hospital ward. The burn team, two physicians, two nurses and a corpsman give the patient the care at which each is an expert. This conception of a flying team of burn treatment specialists has prevented hours of suffering and saved many lives. On their return to Brook's Air Force Base, all is in readiness to receive the patient. Every consideration is given to the man suffering the first effects of a shocking injury. A waiting helicopter often becomes the ambulance in which the burn victim is whisked from airfield to hospital. On many critical occasions, this time-saving route above ground traffic has minimized delays. Right into the hospital, the patient at once comes under treatment. Seriously burned patients lose tremendous quantities of body fluids. So as you have seen, infusions of plasma, a plasma expander or blood are usually imperative and continuous. Patients are weighed upon admission and daily to indicate the loss of and need for body fluids. A fluid calculator helps in computing the amount of fluids needed in the treatment of burn shock. It is simple, fast, and it permits immediate action. No time is lost. The patient is wheeled to the operating room for the start of his hospital care. The doctors make sure there is no lapse in the continuity of treatment. In the treatment of burns involving approximately half of the body, the patient who a few years ago was doomed now stands a good chance of recovery. Initial surgical procedures are performed in a separate operating room, staffed and equipped to meet all emergencies in burn treatment. Specialized equipment and trained personnel facilitate patient care and greatly shorten the time he must remain in the operating room. This patient's breathing passages have been burned. So a tracheotomy was performed to supply him with life-sustaining air. Near the hospital is the ultramodern laboratory building. New concepts in care and cure are originated in these laboratories. In bacteriology, the bacteria which normally colonize the burn wounds are isolated and they are identified so that the miracle antibiotic drugs can be used effectively. In physiology, to help the patient's defense mechanism combat the crippling effects of burns, new drugs and new methods are continually being investigated. Each day help correct blood deficiencies that follow burning. In the radioisotope section, the true nature of the body's response to severe burning is being brought into sharper focus. Advances in patient care include pioneering in the use of exposure in burn wound treatment and in methods for using donor skin grafts to save the lives of severely burned patients. Only skin grafted from the patient himself or his identical twin will be retained permanently on the wounds. But grafts from other bodies temporarily close the open wounds and serve approximately 30 days. By this time, the patient has improved sufficiently to withstand the cutting of grafts from his own body. He has shown photographic proof of his bettering condition. His improvement then becomes rapid and his morale keeps pace. Working with the army doctors, a skilled dietitian prepares the special diets needed by burn patients. They train chefs, prepare and serve them. In this case, a liquid meal is required, containing the food elements which will help most in healing the burn wounds and speeding the patient's recovery from the ravages of his injury. But the mission of the unit embraces not only patient care and research, it also includes teaching. Classes consist of medical men from all the armed services. Air force trainees serve and study for three months. And a Navy surgeon is detailed annually for one year of learning and operating. Care for the emotional life of the patient is part of his treatment and cure. His relatives and friends are welcomed, for their presence is medicine for his morale. No matter what his religion, the patient is encouraged to find in it the faith to sustain him through his confinescence. The patient too is made to feel that the hospital gladly receives his home folks as part of his restoration to help. He is encouraged to keep in touch with them. Recognizing that burns are the most devastating and frightening of injuries, the Protestant women of San Antonio have organized not only to comfort patients, but also those who come to visit them. Working with their chaplain, they bring religious faith to the burn victims and diverting activities to their saddened relatives. San Antonio's historic shrine, the Alamo, interests and relaxes the visitors. It flies the lone star flag and at the entrance, the Alamo 1718, Mission Fortress Shrine. Cradle of Texas Liberty. So visitors forget their tensions and their more cheerful mood, cheers and helps the patients. An example of burn treatment given service men's dependence is Little Joyce West. Here swathed in bandages under the bed covering and being comforted during her ordeal. She was cruelly burned in neck, body and thighs. Here is Joyce today on the left, cured and happy after her horrifying experience. Her injuries a few years ago would have meant certain death. If atomic warfare has ever visited upon our country with its inferno of searing flame, the experience gained in the surgical research unit will contribute greatly to care of burn casualties and their rehabilitation. With its methods for rapid and effective burn therapy, lives will be saved, suffering will be minimized. At a time when they are most helpless and most hopeless, the surgical research unit comes to comfort and heal the service man and his family. Lincoln's words, to care for him who shall have borne the battle. And the service man and his family receive this highest type of specialized medical skill at a time when nothing less will suffice to relieve suffering and save lives. Now our big picture cameras focus on what for them is an unusual subject. Another camera. The Army's new lightweight portable television camera. This camera is an example of just one more step forward in your Army's technological search for new equipment to do a better job in less time. Fourth Monmouth Combat Television takes another big step into the future as men of the Signal Corps prepare to demonstrate the Army's new fully portable TV camera. The battery-powered transmitter weighs 47 pounds. The camera only eight. Each field camera and image flashes to the monitor jeep where the desired picture can be selected for viewing. The electronic scout teams move out, completely free from the cumbersome cables which heretofore limited their mobility. The teams are composed of two men, a camera man and a rifleman who also carries a handy talky radio for communication with the monitor jeep. In demonstrating the capabilities of the new camera, the teams focus on prominent terrain features, such as this dam. The word is passed and back at the monitor jeep, a key is punched, flashing what the camera sees onto the screen. Another button calls up the image of a traffic artery which is being covered by a second camera team. He waits by a railroad to add its visual report to the others. It's answered by images from each camera team in its turn. With the portable transmitter camera of proven practicality, military leaders can look forward to the day when field commanders will receive instantaneous television reports on field conditions while they are developing from his electronic reconnaissance patrols. And our big picture cameras to the peaceful little town, Garmish Puttenkirchen. It is here that a young American army couple have chosen to spend a few days leave. Let's join them for their alpine holiday. Messle at the foot of these rugged peaks is a peaceful resort village called Garmish Puttenkirchen, a favorite winter playground of Germany's Bavarian Alps and a special favorite with service personnel based in Germany. People like Frank and Ann Miller here for a few days leave on an alpine holiday. Yep, that's us all right. We sure never thought we'd be taking a vacation in the Alps on my pay. But with the special rates they give service people up here, the budget took it with no complaint at all. Our first look around the village streets told us we'd made the right choice. At the end of World War II, the 10th Armored Division had its headquarters in this area. But there's nothing about the gaily painted buildings of today to remind you that there ever was a war. These paintings are in an alpine tradition. Even the bowling alley had a mural. We arrived just after a snowfall and everything was muffled and quiet. The tourist booklet wasn't kidding when it said picturesque and refreshing. Then came the Zugspitz, the highest mountain in Germany. Here's where we took our first ride in a cable car. At the top we found another good deal for service people. Here you can rent a complete ski outfit for a dollar a day. Of course, while the attendant smiles at your better half, he may hand you a hat made for two other guys. But it's all in the game. Of course, neither one of us had ever been on skis before. But that was a minor detail. Like Ann said, we just couldn't pass up those bargain rates. I figured it this way. If you're smart enough to lace the boots, you can learn to ski. When we finally came out, we looked like skiers anyhow. There's something about that sharp mountain there that's exciting. And so is the view of the big ski slope. That was a little out of our league though. The ski bowl down below, that was more our speed. That's where they hold the classes. I guess we got so wrapped up in the scenery we almost forgot to wrap ourselves. A couple of minutes more and I'd have had a quick frozen wife on my hands. Big adventure. The sign said beginners use cable car. And I guess that meant us all right. Maybe you could find two people to fit the description better, but I don't know where. Anyway, I never heard of breaking your leg in a cable car. The cable car is pretty much standard equipment on all the higher mountains of Europe. In addition to being darn practical, it gives you a ringside seat for the most spectacular scenery in the world. Of course, at times, the scenery can go from the sublime to the ridiculous. Almost before we knew it, we were at the bottom again. Time to unload, get those skis on, and see about locating the ski instructor. Right off the bat, Annie got a little bit overconfident. What's so hard about this, she wanted to know. But before I could give her an answer, she had one of her own. The instructor called this little doozy the slide ski. It looks easy. But whoops. Well, if at first you don't succeed, give up. This isn't exactly by the book, but it shows the old girl knows how to use her head. But that's a trouble with wives. No sense of humor. Oh, she went fumbling about swell-headed males. Oh, well, it was child time anyway. After a good hot lunch, things looked a lot rosier all around. We dropped by to watch some real skiers in action. Some local people were gathered for a slalom competition, and they were good. So it looks easy. And it is. All it takes is 10 years of practice, where it's sort of got us all fired up again. So back to the trail. We actually started getting the hang of it this time. Well, after a fashion. By mid-afternoon, we took the big plunge and started on a little downhill run. Annie surprised me. She was doing great. Whoa, there now. Let's not get carried away. Still, as long as we're doing the impossible, try this one on for size. The Indians said, how? All things considered, it was a highly successful afternoon. Though I think in the end, we brought more snow back on us than we left out on the slope. Now, there's an idea. After all that exercise, I could eat a horse. And I guess now's as good a time as any, because our spot by the fire seems to be taken. That's another thing about garnish. There's no age limit on ski fans. They come in all sizes and shapes Oh, let's see now, where was I? Oh, yeah. So after supper, one of the instructors joined us by the fireplace. I was all wound up about ski talking. Annie, as she was closing up shop for the day. But not before she agreed with me that when it comes to vacation spots, man, this is the end. And Ann Miller, to enjoy their alpine, a holiday made possible by the special rates and benefits offered to American service people overseas. Now, this is Sergeant Stuart Queen, inviting you to be with us again next week for another look at your Army in Action on the Big Picture. Here is a weekly television report to the nation on the activities of the Army at home and overseas. Produced by the Army Pictorial Center, presented by the United States Army in cooperation with this station, you too can be an important part of the Big Picture. You can proudly welcome the Army you can proudly serve for the best equipped, the best trained, the best fighting team in the world today, the United States Army.


Hello, everybody. I hope you're well. This is going to be my last live video of the academic year. I've got nine teaching books for you. Some of you will recognize, some might be new to you. And these are the books that I've been referring to throughout the pandemic, I suppose. There's lots more. There's loads of audiobooks also, but the ones that I've got on my desk. I want to present nine of my favorite books and it might be something for you for the year ahead or maybe through the summer. Not everyone likes to have anything to do with teaching throughout the summer, ladies. I understand that. We also have to consider social media, and I'm putting this video out through social media, that there are other teachers in other parts of the world in the thick of the academic year. So I hope this video will inspire you whenever you're watching it. And as ever, you can put comments in the chat box, Facebook, YouTube, or here on Twitter. As I go through, so feel free to post some questions, but let me go through one. I've got no slides. I'm just going to hold the book up. So the first one is this one. This is one of my favorites. This is Stop Talking, Start Influencing by, let me get his name correctly, Jared Cuny Horvath. I just cut two or three years ago. I've mentioned the book before in other places, but given the recent interest of how we learn, work in memory, cognitive load, he provides lots of examples in this book. And the dual coding, the DT teacher and me, I just love all the visual representations, the practical examples. And actually, I think it's a really easy book to read and get through quite quickly and make a difference to your practice and thinking. So if you've not seen that one before, take a look. Stop Talking, Start Influencing. For me, I bought this, I guess, in my role as a teacher trainer, how I present information better to teachers, knowing that teachers want quick, pragmatic ideas, being inspired, et cetera, et cetera. So that's why I first went to this book. So you might find this a good read. My second book, and these are not in any order or my top books ever, they're just books that I've been reading throughout the pandemic. So I've just been published, some are a bit more established. They're all relatively new, though. The second book is self-published by former head teacher Andy Buck.  And the book takes readers through the coaching background towards developing a strategy. It offers lots of implementation ideas, strategy, developing coaching techniques, habits and feedback scripts, et cetera. And I would say I'm probably 10 years into coaching and, you know, with all the pros and, or at least the stigmas associated with it, I think once you discover it and learn how as a school leader watching how to logistically make it work within your school alongside the busy nature of school life, something that I always battle to do with the schools I work with, it can be quite transformational alongside very carefully designed observation models. I'll say that very carefully. But this is a good book. This is one I have on desk inspiring me also. And if you're watching, thank you for that. That's my second book. The third book is a new book, the feature of teaching by Guy Claxton. Now have a slight smile on my face. From observations on social media, I can already see how this book critical of other teachers who are guests like me have been on their own unqualified cognitive science journey. I'm not, I'm not qualified cognitive neuroscientists, nor are many teachers, but many of us have started to get really excited by the explosion of cognitive science as ever nuance. I think what Claxton tries to address here is some nuance. However, he does tackle some big themes, some big voices from big topics. Quite rightly, he is a qualified cognitive, cognitive scientist. And I'm not yet finished it. And my evaluation so far I suppose is that there's, I think Claxton's issue, and I haven't got to the end. So tell me if I'm wrong, but is that he has an issue with how the policy is, how policy has been evolved. So you can see this in the Department for Education and Off-Stead Documentation. You know, if we think about working memory, it's complicated. It's not the theory of everything. And how does it work in an early year setting compared to a pupil referral unit or a year nine bottom set class on a Friday afternoon? Already that needs translations. My fourth book. Thanks for the comment on Teach Lucky Champions. A good book. I definitely recommend it. How learning happens, my friend Carl Hendrick. I've not yet spoken or met Paul Kirschner, but I know he's heavily influenced in the field of cognitive science and research. What I love about this book is that they tackle 26, I think, from memory, seminal pieces of research. And I have to say I found this book fantastic. And what I love about it is you can read them in isolation. They've got the usual signposts, why you should read it, what's the abstract, a bit like what I'm picking for my own doctoral research, learning how to get into the details of papers and find the information you need before you go any further. And I guess it's got what teachers can take away, all the recommended reading QR codes at the end of each chapter, which I love. I think that's really good for teachers. So I think the book's cleverly laid out. And I think it's a good book for teachers, so it gets a thumbs up from me this one. So if you're really interested in education research, you want them all in one place. This is a good book to start. It's fact one of the books that clacks in critiques actually. So you can see I'm trying to also find my understanding of everything out there. There's lots and you'll never get to the bottom of it, but I think it's at least good for your professional learning. And I guess I'll put all this out in a blog post over the summer. But reading educational books provides teachers with additional professional learning outside of their own diet that's provided within their skill. And I think that's something that all teachers should consider. We don't always have the time or the energy, and we often want to read fiction books, et cetera. But I love reading books on teaching. That's just me. I know there's one or two others out there, which is why I'm sharing this video. The next book I've got is a second edition here by Dr. Matt O'Leary, a university of Birmingham. It was Wolverhampton. I know Matt's moved on. Obviously he's moved on. I didn't know. But this book for me as a school leader, having conducted thousands of observations, done some great things, some horrific things, and only recently being exposed to a really useful research method for reliable observations, which really trumps traditional observations and learning walks. If you're really... If you, one, if you ever observe other teachers, two, if you're interested in developing teachers rather than just checking what they're doing, then this book is for you. And I know Matt's book here, just check my notes. You know, my research also, 30% of English schools still grade despite it being cost as a poor metric, almost 2014. So seven, eight years later, it's still happening. So if it takes me this long to get to the bottom of good research methods and the profession's still to move on, then we need academic research books on specialized topics such as this to move everybody forward. So if you observe other teachers, folks, and you haven't had any qualifications or formal training observations, and let's face it, not many of us do, then this book would definitely support you. Now, next book, put me in a corner. What's your favorite, Ross? It's probably this one. Trisha Taylor, Connect the Dark. So this was published in 2019. I've written about this a lot. It's probably the book that's influenced my thinking the most, has rekindled my love of memory and has changed my practice. And if that's not a good endorsement, then what is? Tons of stuff. What I love about it is Trisha connects the memory to mindsets and relationships and how it all intertwines. And there's more to it than that, but she explains her own journey from the States working over here in the UK. And there's some brilliant illustrations here as you'll see throughout the whole book. And you can see, I don't know if you're a writer or not, but I certainly am. I'll just show you some evidence or I scribble all over the book. That's just my style. But it's a brilliant book. So if you're new to memory and you want a practical guide, this is the one. And I'm sure there's others, but this is the one that I've gone to and the one that I regularly use. So that's Connect the Dots. And I do think it'll make a difference. Now, the next one, you'll know this as soon as I show it to you. This is by a history teacher who came to one of my teach meets in London in 2015-2016. And I think the author, who I'll name shortly, was a relatively new teacher maybe in our first, second, third year of teaching. And it's amazing to see what a journey she's been on, who the people she's now working with and the number of book publications she is now producing. Pretty much my own journey. I think it really highlights how hungry we are to learn and be better as educators. Now, you'll know this book straight away, Retrieval Practices by Kate Jones. She's published others. This is probably her most popular. What I love about this one is it's got all her own research of other academics and her own practical resources. In some respects, she's been the kind of go-to voice here in Britain for loads of ideas. And, you know, Kate will kind of put some of those thoughts to bed, I suppose. You know, Retrieval Practices is one of the things that underpins lots of things we do. And she is more than just a Retrieval Practice expert, which I've heard her say before. But there's a great image on page 25. I'm just going to show it to you here. And that best sums up what everything is about Retrieval Practice. I can just check my comments. I think Kate's commented here. Just give me a second. Yes, she has. Okay, thanks for watching, Kate. This is the page for me. The entire book. Some people elsewhere are watching that underpins, I guess, anything and everything in education, not just Retrieval Practice, you can't have good behavior management without good subject knowledge. You can't have good subject knowledge without good training, good people around you, etc. There's no one way. There's no one way to mecca, as I often say. There are many ways. And I think, you know, record this at a time when the Education Foundation have just published a new paper on cognitive science in the classroom, and I've got a blog coming out on Sunday with my thoughts on that. I think it's great, great piece of research as is all these books the challenge for all of us, and one thing we all need to keep in mind is how does that work in a primary classroom? How does it work in a Pru? How does it work in a virtual environment with Year 9s, with student learning needs? And that will always make teaching complicated, fascinating, and highly complex. And I think what we all have to do as teachers and schools, which we can see happening, is that we look at a piece of research, we take the bits that we think are going to best suit and then we get on with the pragmatic aspects of the research recommendations. That's what it's always going to have to do, what we're always going to have to do and what we should always do. And I think if we always keep that in mind then we'll do very well. Now my next book, book number 8 My Good Friends Again So I do have a wide lens and I know there might be one or two people watching, Ross you're not reading very widely. Well I am, but I'm just coming to some books that I keep turning to as the point of the video and the blog that I'll put out in about a week's time which I'll automate because I am logging off and this is my last, I say cautiously because I know sometimes I change my mind but my last live video stream of this academic year, what a weird one it's been is this one. Teaching Walkthroughs. Now if you ever need evidence that published in the book during the start of the pandemic, I'm being noticed that Ollie and Tom when they published this and how successful it'd be so this is the one. I think over a thousand reviews on Amazon which is phenomenal. Obviously the dual coded cartoons the five stage instructions the great thought and articulation from both of them in the writing and the ridiculous number of resources online, something that I aspire to and always trying to do on my lonesome. But I know this book has been instrumental for many schools and teachers, not just across the UK but much wider field and to do this during a pandemic is phenomenal. So well done to Tom and Ollie and I know just like Kate and myself and a few others there's a version 2 and a version 3 and as we know that second record is always harder to sell so good luck with all that but it's a really really good book. Last one, I know other people recognize this and again I apologize for the kind of small smart silo I suppose but the the recommendation for this video is books that I've regularly dipped in and out of throughout the last 18 months of the pandemic. That's the brief and that's why I'm sharing these books. So the last one is powerful teaching and when I received the copy of this this one's the only hardback let me just double check yes the only hardback which is a nice thing probably last a bit longer and when you get well thumbed and dipping in and out of it it's probably a good thing because some of these books are getting a little bit better which is good because it means it's been well read and well used but hard copy thankful enough to have a chat with Patrice and Pooja who wrote the book I'm picking all the research and wisdom before the pandemic we were actually planning a physical event together so I'm gutted that that hasn't happened but maybe when things start opening up we'll see in future retrieval practice I guess the book also there's lots of stuff in here there's lots of references I guess in lots of these to Dunlosske et al's research from 2013 and as I get deeper into academic education research and getting distracted with teaching and learning not doing the research I need to from a doctorate you start to see that seminal pieces of research inspire others and I'm not saying there's a bit of a bandwagon of agurgitation obviously you know I now know this myself publishing an academic piece of research at a doctoral PhD level has to bring concrete new knowledge to the world even if it's just a millimetre so it's phenomenal pieces of research here but I say cautiously education research is quite small it tends to say the same things the challenges obviously things evolve but as to ever teachers constantly need to take what the research says the recommendations translate it back into their own classroom and more importantly what the EEF research suggests is here's all these recommendations but there's very little to tell teachers how to do it so a lot of these books try to address and give people practical applications and there's lots of things in here anyway that's a great read loads of great research what I love about it is it's just one topic on retrieval practice with loads of recommendations and a book that really inspired a lot of my practical thoughts and strategies so that's it powerful teaching walkthroughs retrieval practice connect the dots classroom observation if you're observing other teachers this is essential if you're interested in getting deeper into academic research this is a really good go to a bit of a controversial one if you really want to change the life of teachers then get into coaching and then if you start to do public speaking and I know a lot of teachers get a bit fearful speaking in front of other teachers but one day you know Kate I know you're watching you're already doing lots of presentations to other teachers when you have to start doing it physically time and time again in lots of different settings you need to think about you know how you influence and change people's lives so stuff like this and there's loads of other things outside of education presentation skills etc then that's it so I know teachers watching in Brazil are in the middle of the academic year and teachers elsewhere Australian things like that are doing lots of other things but teachers here in the UK are logging off for the summer some already have but if you still like me like to read when you've got a bit of time to do so then these books I'll have a blog come out in about a weeks time from this video on my site called 9 teaching books you can dig the links or just take a picture of this and look them up online and I hope to make a difference anyway general things from me I hope to have a new book out at the start of next year I'm now in the proof reading stage my doctoral studies up and down all the time I'm going to spend the summer revisiting a paper that I need to tweak refine and then I have to work hard on my theoretical and philosophical frameworks which is hard work in its own right but that's where I am with that as ever the blogs the resources the websites a full time job physically I'm back in the schools from the end of August at least here in the UK I'm not doing any overseas work for the medium term I should say I think at least the website keeps me busy lots of things going on behind the scenes I'm also adjusting to a new way of working and living in another part of the country and what else that's pretty much it from me I miss being in schools deeply with teachers I had my second physical job last week back in London but sadly I was too ill and the risk of not COVID but just the flu but the risk of transmitting stuff and things like that was just too much to take into account gutted not to be able to visit that school in London but anyway I'm having lots of fun I've got my head down I'm constantly speculating on how to make the classroom an easier space digging in and out of different bits of research thank you for watching thank you for following, thank you for connecting do say hello but I'm going to try my hardest to log off for the summer break I hope you do too when that time comes and bye for now I'm just going to take a quick moment to look at some comments okay I know my brother's watching so I better say hello to him otherwise I'll get it in the ear from him not that he ever calls me but there you go he seems to watch my videos anyway I'm waffling bye for now everyone have a good weekend good summer, good week whenever you're watching this and stay safe, bye for now


Hello folks, I'm Doss Kamhout. I work in Intel IT, Principal Engineer. I'm here with Don Dugger who works in our open source technology center and we are here to talk to you about Intel's work with with OpenStack. So first of all I want to give you an overview of what Intel does with OpenStack. Some of you may know we make CPUs, we make silicon, we also make software and we have to have a pretty long standing history of helping in the open source industry. Don's going to give you a lot of details on that but just if you look across the three areas where we're focusing, one's in our contributions, we've now made it into the top 10 contributors as part of Grizzly and Don's going to explain a lot of the details on what that is and what it is that we're doing. The second point is is for my neck of the woods and this is how we actually utilize the technologies. So many many years ago we were one of the large drivers in the EDA silicon environment for moving from from Unix to Linux, so we invested heavily in Linux. We're in the same situation here where we're moving very aggressively forward and utilizing open source capabilities for what we do with cloud computing. We've been running a cloud environment for for quite a few years. My background is in grid computing where we are heavily using Linux and other open source capabilities. So what I'm going to do is give you some of overview of what we do with Intel IT's open cloud. We shared quite a few details in the last summit so I'm just going to give you an update and so we can spend some more time on saying Intel's other contributions. And the third element is a thing we have called cloud builders and these are basically blueprints, reference architectures on how to stand up a cloud environment. So we invite various solution providers to come in and basically prove out step by step. This is actually how you build a cloud so that other IT shops or other system integrators can basically take those blueprints, bring them into their own environment and walk through the steps of actually building a private cloud. So our focus is enabling enterprises and cloud service providers with open source capabilities for cloud. So this is some of the key Intel contributions and again Dawn's going to go into much more details on this. If you look on the left you see the specific contribution, which project it is, what the release and some of the comments. So everything from trusted filters, trusted filter UI. So these are based on a thing we have called trusted compute pools. For those of you that are involved in security of hypervisors, you're probably familiar with things like root kits or being able to determine is that hardware actually secure, is that hypervisor secure. So this technology, which Dawn will give more details on, is basically how do you ensure that environment can be trusted for specific high security workloads. If you work in the enterprise IT space, you would find that in some situations people actually don't virtualize certain workloads just because of the risk that still exists in regards to hypervisor technologies. And if you follow what some of the research environments are doing, they've actually found ways to hit other VMs sitting on the same hypervisor to various attack vectors. So we'll talk about what we do with trusted compute pools. We have a filter scheduler, so this is an intelligent scheduler for Cinder. So you'll see where we're basically investing in a lot of the core capabilities that are associated usually with the hardware. Multiple publisher support from Cielometer always messed that up. Open the Testation SDK, which is related to the trusted compute pools, and Causebench, which is basically a way to do benchmarking against an object store environment. So those are the high level points, and what Dawn's going to take you through is all the details. Yeah, one of the first things that we started to work on in OpenStack was creating something we call trusted compute pools. And the basic idea is Intel has a technology called TXT, Trusted Execution Technology, and that enables you to verify that what you're trying to boot is what you wanted to boot. Okay, basically what it does, it uses the TPM, the Trusted Platform Module, to store unique keys associated with each of the elements that you're trying to boot. And as you boot up, you measure what you're trying to boot, compare it with the keys in the TPM, and only if they match and you know your stuff is good, then will you execute it. So utilizing this, you can verify the BIOS, the boot block, the initial boot code, all the way up through the initial operating system that you're trying to run. So this gives people the confidence that, yes, you are booting the appropriate software, you've got a valid thing, and everything is working, and everything is there properly. One of the other major advantages of this is it's on the list as the compliance issues. This gives you a way of verifying to third party, you know, whatever, that, yeah, we booted properly, so if, you know, something goes wrong, it wasn't because we booted the wrong software, we can guarantee you that. So, and this kind of goes into the details of how we actually implement that. And you notice at the top, we're talking about the things that had to be put into OpenStack proper. There you'll see the yellow things, or the things that we've added, okay, in order to support trusted compute pools, where one of the major issues was the trusted filter, that big oblong thing there, which is just a filter as part of the scheduler filters that basically when you say start me a virtual machine, I will go find the host that that machine is going to be running on, and I will say, is that host a trusted host? And we have, you'll notice in the center, the attestation service, the attestation service is an external process that runs, and it's service that runs that you can query to say, this is a host, is it trusted or not? And we've got various protocols and whatnot in place so that if you look down at the bottom where you're actually running a host, this is where you have to have the host boots up. It runs the TXT, I'm trying, I'm pointing on my screen here and I'm sorry that I don't have a pointer up there, so you'll have to read through this slide and hopefully you can find the things I'm pointing at, virtual pointing. It boots and executes the TXT code to guarantee that you're booting the right thing, and then there's a trousers module, which is part of the boot thing, part of the processes that run, and it talks to the attestation service, and through a well-defined protocol, it'll exchange keys and guarantee that what you did is what you thought you were trying to do. Oh my gosh, I should have a pointer thing. Okay, there we go, now I've got through that, and that's probably the last one that I'm going to be pointing at, I can point at it. So that in kind of a nutshell is the guts of how we do it, and we had to put in the trusted filter, and we also, I didn't mention that, we did put in some enhancements to the Horizon UI so that you can actually see, okay, this is a trusted host, this is not a trusted host, it helps to be able to know those things. Okay, now we're kind of, kind of switch gears a little bit, and now we can try and talk about Causebench, Causebench is a cloud object storage benchmark, we're kind of an engineering company, and to an engineer, if you can't measure it, it doesn't exist, okay, so we really haven't seen too many really great benchmarks floating out there, so we decided to create one. And the first thing we're attacking is the ability to measure how fast your object storage is working. So we've built a framework, okay, that has the ability to deploy an appropriate set of servers and whatnot, and then deploy some benchmark processes that will extract data from the servers and measure the bandwidth and whatnot that you're getting. And you can utilize this to find bottlenecks in your particular environment to see whether or not different hardware is doing different things properly for you and do all that kind of stuff. You know, as I say, if you can't measure it, it doesn't exist, so now you're going to have a chance to measure it, and we will be enhancing that in the future, hopefully hitting other things.  Are you hitting those things properly? So we're very big in the networking. I expect to see networking measurements and whatnot coming down the line. Again, this gives you kind of an architectural picture of the way Cosbench works, where the important thing is you have the controller up here, which is running things down through and hitting the storage system. And it's all web-based, so it's very easy to utilize, easy to measure things, easy to find out how the stuff is going. And I should also emphasize that I work for the open source technology center here. Everything we do is open source, okay? So we might have created Cosbench. I don't even know if it's been officially released in the public yet, but it will be. Okay, we're not in the business of creating proprietary solutions, at least in my division. So expect to see that available, and you can grab it, do whatever you want with it, utilize it, modify it. We love modifications. Those are wonderful. Okay, another thing that we've been working on is the filter scheduler for Cinder. Now, for those of you that are familiar with OpenStack and the NOVA scheduler, this will look remarkably familiar. Okay, and point of fact, it's almost exactly the same. The basic idea is you create a set of filters, and these filters are pretty much analogs of the same filters that you'd see in NOVA. But now what we're doing is we're applying these to Cinder so that you can filter, these filters says, this particular storage service is not appropriate for the particular work light I run around, or this particular server is appropriate. And so the filter will make that decision for you.  And based upon that, you'll get a rank order set of services for your storage. And so this enables you to control better how you place your storage, how you access your storage. And hopefully you can optimize your system and get it working in a much better fact. Basically gives you more control over what's going on. And this just gives you an idea of how you can utilize these things to start with set of services and which are the appropriate storage servers that you want to go and supply those services. The multi-publisher for Solometer, I actually got that right. So there. The idea here is you have a set of data that's going into the collectors. And you want to transform that data, and it might be one person wants to look at raw CPU counts, but another person might want to only look at CPU percentages. Okay, so you might want to transform that data into different forms for different consumers. And then somehow you have to get that data to different users of the data. There might be somebody that wants to measure the data for performance monitoring purposes. Somebody else wants it for billing purposes. Somebody else wants to use it for historical trend type analysis and whatnot. So you have to get that data to multiple consumers. And so we put in some code into the Solometer to enable just that. You can take basically one set of data, transport it in multiple different ways, and then send it out to multiple different consumers. Yeah, and to talk about some of the future things that we want to look at, we at Intel are very intent upon enhancing OpenStack. We think it's a really great thing. So we have other things that we want to do to it going forward. Enhanced platform awareness, that's actually something that I'm kind of working on. The idea is we want to enhance OpenStack so it can be aware of maybe some unique features available on different nodes, and so that you can utilize those different features in the most efficient and most performant fashion possible. Kind of as a side note here, I should emphasize, I work for Intel. I think Intel makes the best product, so that's why we're going to win. The enhanced platform awareness is not an intent to say, oh, this is only Intel, so everybody else forget about it. We're enhancing the platform awareness across the entire ecosystem. If AMD can take advantage of this and utilize it, that's fine. We don't mind that much because our stuff is going to be better, so who cares? So I just want to emphasize that a little bit. Another area that we're going into, again in the future, is key management. The idea here is we're very concerned about security. The whole thing about the trusted platform, trusted compute pools, was a security issue. Key management, again, is a part of the sole security thing, and now we want to start looking into what can we do to secure the data that you're utilizing. Again, we have a slightly biased view. We've got some encryption instructions buried in the CPU, so we think it might be a good idea to utilize those things. Again, we think we have the better solution, but we want to enhance the key management just in general so that everybody can take advantage of it. Another thing to go along with the storage stuff we've been talking about is erasure code. Currently in Swift, Swift does a triple duplication of your entire dataset, which is fairly expensive, shall we say, and wind up with a fairly sizable data explosion. Erasure code is effectively the ability to only store certain portions of it and duplicate certain portions of it without duplicating the entire thing in three different places and still give you reliable capabilities so that if one of your storage servers goes away and loses your disk, you can still recover the data without necessarily having to go through a full triple replication. So expect to see more work coming out from Intel in that area. And that is kind of where we are now. I'll give you a flavor for where we're going in the future. Things could change, but that's kind of a flavor for where we're going. And Das will now try and hopefully tell you exactly how we're doing things. Thanks, Tom. So I know there's some new faces. Last summit, I shared quite a bit of details on what we do with cloud, why we do cloud, and a lot of the specifics on what we're doing with OpenStack. This is intended to be an update from that. But just a couple of things. This is our platform solution stack. So if you look at the bottom, there's a few things to look for. Green means that it's something that we have in production today. Yellow means that it's coming and probably next two months or so. And blue is a little bit later, probably with Quantum. We're going to pull that in fairly quickly since we really need it. So fundamentally on the far right we see is the release cadence. And this is something at least some of my enterprise IT peers used to be kind of concerned with the fact that OpenStack comes out with a new major release every six months. We actually think that's a really, really good thing because we need the pace to be very, very quick. I recall six months ago there was just a thought that maybe Cinder could have multiple storage back ends and now it's a reality. So the reason that's a reality is because RAPTIS is very fast cadence. There are some in the environment that say six months is even too slow. If you look at some of the public cloud service providers that put out 150 features in one year, something like OpenStack is it builds its community and needs to move faster and faster. But this is our overall stack. Our compute storage and network are obviously the physical layer that we have. We usually refresh this, meaning we get some new generation of equipment every 12 to 18 months. On the OpenStack side, you can see what we're using. Pretty straightforward from perspective of we have compute. We have OS images. We actually don't expose a horizon right now. Most of our exposures through API CLI and I'll show another diagram later. And then we built our own manageability stack. This isn't core to OpenStack and we don't think OpenStack is everything you need to run an open cloud environment. It probably doesn't make sense for it to be everything. It's good to have other open source solutions in the industry. But to show you some examples, we use a concept. We watch everything. We make decisions and then we have an actor and then a collector. So keep it very straightforward. We're watching the environment from down to the very core infrastructure up through the virtual machines into the application layer. This is sending events to a bus. We have a decider which is basically a fairly young child with very basic understanding of logic. But that's good. That's the start out. This is internal code right now. This is something we would like to see an industry become open source in the near future. And then we have an actor which is basically puppet. This is the thing that takes the action in the environment and makes sure that the configuration state is the same. And then recently a collector. Most environments once you start having to audit it, you clearly need to see everything that's going on and have a trail in history of that. We're using Mongo and HDFS. So again on the very top, our consumers are generally software developers. So when we first did our first enterprise private cloud which has been running since about 2010, our focus was initially on application owners. So in an enterprise IT shop, you usually have a lot of people that buy off-the-shelf software and run it on infrastructure. So what they wanted was a GUI. But when we made the decision a year and a half or two years ago to do OpenStack, we shifted our focus really to software developers. And for them what they need is an API, a CLI. So usually the GUI for us is always trailing which is why we haven't even exposed Horizon to anybody but our friends and family. But this is the overall platform solution stack. And probably a good point to add on here too is we also do run Platform as a Service. And so on top of OpenStack today we're running Cloud Foundry and Iron Foundry in production pilot which are also to open source capabilities. So this is just our current infrastructure app status. We've been running in production I think since August of last year. We run in two data centers and on the left we see we have the software development type people and actually our utility abstraction layer that we built internally which has API and a CLI. And the reason for that is we have to work against not just OpenStack. We utilize public cloud service providers as well. And as we all know APIs are not the same and therefore usually need some form of abstraction layer. We looked at quite a few of them and decided to... We felt that the industry was going to need to create one fairly soon and we took the technical debt on ourselves to build an API CLI that allows us to basically take the normal approach as you would to an infrastructure.  We interact with load balancers whether it's in the public cloud environment or whether it's hardware load balancers or software load balancers in our internal environment. We give the framework through the actor to do code package and releases. We deploy platforms into our environment that are fully featured and then the application owners have the opportunity to use things like the public framework to push their own code. In our internal environment, we're running OpenStack Essex today. We were about to go to Folsom, but after this week our team is highly interested in bypassing Folsom completely and jumping straight to Grizzly. So we'll probably make a decision within this next week. But for us with all the advances that happen in Grizzly, it's probably the right choice to jump forward, but we'll report back the Havana face-to-face summit on what we did. And then just to point out on the bottom right, our consumers are either actually end users that need to hit the software, not the hit OpenStack, but hit the software that's running on OpenStack. So these are people that work at Intel generally that want to get to their apps and data. So in some scenarios, they're hitting a global load balancer, which basically is intelligent DNS, which routes them to their closest proximity. So if they're on the west coast, they end up in one of our two data centers. If they're on the east coast, for instance, they end up at a third-party cloud. But the global load balancer takes care of that. And also it helped us start to push forward the concept of active-active to our software developers so that in reality we should be able to just shut off the data center completely, and the consumers going through intelligent DNS are able to stay running. One other thing I just want to point out, and the details aren't really that important, it's just that the point earlier that not everything has to come out of OpenStack, and I think it's a misconception that people believe everything is in OpenStack to run an entire cloud environment. I think more and more can come out of OpenStack, but this is just... What's core from OpenStack? What's outside of OpenStack that's open source? What's outside of OpenStack that's homegrown today? And what's outside of OpenStack that's proprietary? So for instance, right now our approach was to go open source for almost everything. Though our application performance management tool is not open source that we use, but that's okay. But the focus that we move forward is basically everything stay open source. And then as you notice, there's quite a bit that's outside of OpenStack that is open source. For instance, our web fabric and database fabric is based off of platforms of service solution, Cloud Foundry and Iron Foundry, and we don't believe OpenStack has to take care of that. So basically we have a layered environment of a combination of OpenStack and more that allows us to run our environment. So how many of you are familiar with writing cloudware applications? How many of you are software developers? Okay. So fundamentally there's a key difference between how IT applications or an enterprise shop, how applications were being built compared to how they should be being built. And we call them legacy applications, but unfortunately legacy applications are still being built this week and people are buying legacy software. But fundamentally what we're trying to push forward is very similar to what we do in grid computing. It's very similar to what you'd see. Many of the shining stars that use public cloud, how they approach things like design for failure. If you go and look into any depth on, say, how a Facebook or Google operates their infrastructure related to their software, it really should start clicking in a software developer's brain on how to actually write differently. So one thing that we do internally now is we do codathons, which are basically a one-day session. We pull a bunch of developers into a room and we walk them through how to start building cloud or applications. So give them access to platforms of service, give them access to infrastructures of service, and walk them through some design patterns. So one of them I just wanted to share, which we're pushing heavily, is how to actually build to an active, active model. So the subject here is deployed to N plus one clouds to basically as you add on more environments, more regions, more zones, your SLA for your service should be able to go higher and higher, which is very similar to what you see with a lot of consumer apps. I know, I saw Gmail was down this morning for some people. Did anybody get hit by that? Nobody got hit by Google Docs down? Okay, those are rare scenarios. They don't happen very often. I think the last time I saw Google have an issue was because somebody messed with DNS in some country, and it went up the chain and Google then had a DNS problem, but it was localized in that area. And fundamentally though, it's how they approach building software. If you go inside of an enterprise and you see all the software is built to assume that the server is always going to be on, I think as we all know today, that's not necessarily the case if you're dealing with ephemeral storage or if you're dealing with a situation where you don't have resilient block storage. People often don't write with a concept of eventual consistency. So eventual consistency is, you know, opposite of causal or where a lot of people spend a lot of money on replicating data, so it's constantly in sync. We're saying, you know, eventually it'll catch up and you deal with your code in such a way that transactions are depletant and they aren't hitting... They're not causing issues by hitting into multiple data centers. Today, we generally help with the database replication for our teams. As we do more and more platforms of service, they can just get eventual consistency out of the box and they can do less focus on understanding the deep basis of how those things work. But I think we're far from that. Is anybody in this room familiar with things like Paxos? We have a few nodding heads. Any other hands raised? Yeah, so Paxos, so this is like the basics of where we want people to go, but if you look at complex transactions, you have to enable concepts like Paxos which ensure that your transaction is really, truly consistent before it returns to the end user. This has been around for quite some time. I know Facebook has shared a little bit that they use that, but it's fundamentally that you can't... If you're really going to build applications that are global scale, that are truly resilient, you have to think differently. Utilize the cloud to your advantage to create and destroy things on demand, but to really start building with a completely different approach. So this is when we shared six months ago. I think I also shared... I might have left it off... how we compare to public cloud environments. So when we look at the various functions or capabilities that we need on the left, we basically say, hey, where are we at with our Intel IT Open Cloud, our private environment, and where do we need to be? There was quite a few things in red six months ago. Things are better. It doesn't mean everything's in production yet, but we're slowly making... well, actually fairly quickly making progress and what we'd like to encourage others that are either in an IT shop or are committed to helping move the stuff forward is looking from these areas in red and saying, what can we do to accelerate them? So fundamentally, we start out with the basics. Give me compute infrastructure as a service. This is through Nova. No change there except probably moving from Essex to Folsomere Grizzly. Object storage was a tough one because actually for a lot of software developers, they're not familiar with object storage though. I don't know how many of you have read how the NPR apps guys are using object storage today. Has anybody seen that article? It's amazing. They have one server that does cron jobs and all NPR's applications are just object storage. There's no web presentation layer involved anymore. So the point being is innovative things are happening as people are consuming these services at a greater and greater scale. So the focus was get this into the environment as quickly as possible. We have Seth in our labs today. I think that's one constant I've heard in almost every talk I've been to about infrastructure. Somebody's trying Seth. It's working well in our labs today and we intend to get into production in the next month or so with hopefully no issues. We're going to rely on it for two functions. One is as the Swift API back end as well as the Cinder API. On the list there's a couple other areas that are still an issue. Auto scaling is a pretty major problem for us. We have a very basic version working right now where Nagios can tell the decider that there's a situation where CPU is being overutilized until puppet the scale out. We're pretty interested in the heat work though it's not to the point that we can use it for our hybrid environments and we would like to see it progress though. In the meantime we're investing in our own solution internally which we hope to be able to share hopefully by the next summit. Nagios so if you're familiar with when I say missing APIs this fundamentally means that everything must end up being exposed as APIs. We're actually pretty far away when I say we, I mean the open stack community we're still pretty far away from the level that we need to be when our capabilities expose as APIs. It's how software developers expect to operate and I won't name names but there are public cloud service providers that are really pushing the envelope on what's possible in regards to the feature set but we do believe that open stack community is catching up this is why we're utilizing it and it has a lot of opportunity to move very quickly. Hadoop has APIs but if you really want to do some analytics it's not just about exposing Hadoop it's do you have a place to put your storage how are you going to launch your compute what type of orchestration you have and I think those of you heavily involved in open stack realize there's really not even an orchestration mechanism in there so a lot of us had to look at other tools so it's really how do you build an entire open cloud that enables many of these capabilities at scale and that's competitive what's going on in the public cloud space so just back a little bit to the app architectural guidance this is just some of the rules we have I also work in this thing called open data center alliance which is basically helping enterprise IT shops move faster to cloud one of our peers in that group is Disney they've been a pretty strong pusher in regards to cloud based technologies in the private cloud space as well as some of the hybrid but they actually have a white paper out there if you're not building cloud aware applications today they've published best practices on how to approach building cloud aware applications this is just a high level view that we share but some of these concepts should be getting ingrained in everybody's head now like design for failure assume and actively test for failure all data centers at some point in time regardless of how many levels of resiliency you put in, everything fundamentally breaks we had a joke internally, we had a great data center and a squirrel took it out but these things happen so you should always assume failure and build your application in such a way so stateless compute scaling out instead of scaling up a lot of enterprise applications only understand scale up so you hit a ceiling so driving a real focus on scale out which requires also that the application understands much more automation and also requires that you expose as many APIs as possible in your infrastructure so you can do tricks like that you talked about eventual consistency and then the last thing for us is the DevOps NoOps model we kind of stop using NoOps internally because it's scared folks but fundamentally getting a DevOps model in place so people can at minimum get developers and operations together into the same or better yet give developers the ability to actually own their code we find if they get a page at 2am about their code they never get that page again I also want to just give some top priority items for us so we do run enterprise IT shop and running an enterprise IT shop means lots of requirements on getting things pretty resilient I'm not telling everybody that runs an app inside of Intel that they have to switch to cloud aware that would be ridiculous it wouldn't happen fast enough I'm sure if any of you work in enterprise space you probably have some code that was written 30 years ago and nobody's touched it and it stays running so there's a lot of models where we just have to keep the legacy up and running so we've made a cognizant decision that we weren't going to just force everybody to cloud aware and pretend that the legacy environment doesn't exist we fully embrace that this environment will exist for a long time and we have to figure out how to make open stack work in this environment so we do have a list that I've shared probably a year and a half ago that said here's all the items in open stack that we have to solve but these are some of the key ones so fundamentally block storage sounds straightforward but being able to enable something like live migration allows us to do maintenance in our infrastructure and keep that VM that always has to stay up online and functioning it gives us that persistent data for the situation where people are not able to change their application code and deal with a persistent back in and compute that stateless so we're trying to be very pragmatic I haven't seen this with everybody in the open stack community but I do believe if open stack's really going to push forward into enterprise space some of these underlying assumptions about infrastructure and the relationship the legacy applications need to be handled and implemented federated identity across open stack environments and then beyond so again we do believe a hybrid cloud is going to be the norm we don't get everything we need from our private cloud environment we run 68 data centers across the globe our Linux grid is approximately 60,000 servers so we have a fairly large scale inside of our environment but there's locations where I don't have a data center so for instance if I need to be online in South America in a month there's no way I'm going to build a data center in a month so we utilize public cloud as appropriate to consume capacity as well as in some situations features that we don't have in our private environment third is a switch away from Nova Network so right now we use VLANs and Nova Network and security groups to deal with our infrastructure especially for our web apps we're pretty excited about quantum and the shift STN so this will give us a lot of flexibility as well as the ability to one of our big delays today is just getting our network operations team to expose a VLAN so it's a human element and we take a parade of approach and basically look at where is there a delay in human interactions causing a delay for our software developers and networking is a huge element and once we get quantum online with OBS and SDM plugin there will be a game changer for us for how do we expose networks not even getting into the very low level SDM stuff just the high level logical elements are going to be very important load balancing I didn't get a chance to go through the load balance as a service talk here this time I'm hoping that we've made huge strides but fundamentally there's nothing that operates in an environment that doesn't use a load balancer applications that are resilient must have a load balancer that's how it works with their hardware or software this is fundamentally an aspect and most enterprise shops probably have a lot of hardware load balancers in their environment that they need to be able to get an API in front of them so they can able full app life cycle so create vips, destroy vips so this is a major focus for us because it's also a bottleneck in regards to getting these cloudware applications online and completely self resilient implement grizzly faster so another big item for us is rolling upgrades for any of you that have done an open stack upgrade yet since you don't have persistent block storage and you may have applications that are not cloud aware they're generally going to experience some form of downtime you want to move to a model where there's zero downtime, zero business impact there's lots of different ways to approach this whether it's things like anti-affinity and your scheduler so that your applications always end up on different nodes more intelligence in your orchestration so that as you do rolling upgrades you make sure that not every node behind that load balancer are affected but fundamentally how do we really enable true rolling upgrades so that the customer and software developer and then more importantly the end user hitting that software never experience a service outage and then the sixth point is what Don talked about with trusted compute pools we run a lot of high security applications like many enterprise IT shops do if you look at some of the reasons why people don't use public cloud massively today in the enterprise space or where you're regulated or audited it's because of security sometimes performance and total cost of ownership so for us even inside of our private cloud we have some workloads that we don't put on hypervisor and we actually benefit in a lot of situations running on hypervisor so trusted compute pools gives us that ability to ensure that our sensitive workloads are landing on the right environment and Don didn't talk about this one other feature in it but things like geotagging become very interesting for us too because we operate in some countries where that data can't leave so when you operate in those environments you have to make sure that you do some sort of geotagging or you have a lot of manual processes involved to make sure your data always stays in that one location so these are the top priority items for us there's more I'm sure but I think that's all I had so well Don I will open up for questions and if there's any from the room using the cells capability as far as I know right now the cells isn't really ready for what we need I'll ask my guys later Hey, Winston, did you look at cells while you're here this week? Is it ready? It's getting a lot closer I understand that Yeah, it's getting it closer X-Face is actually using it in production right now so that doesn't mean it's ready for you but That's right, we're very curious on cells moving forward when we were all here six months ago I think even Mercata Libre showed how they have to do a lot of advance scheduling across their clusters and they would love cells they had to build their own code to handle it so the faster it can be done the better Question? Open source platform as a service? Yeah, so on top of OpenStack today we run Cloud Foundry and Iron Foundry which are two open source solutions we have a lot of .NET developers so it focuses in on on that combination but we also of course we have a lot of data and other That's happening so right now we have very basic interaction but when we release our new internal abstraction layer with orchestration it'll configure global balancers as well right now somebody actually has to hit it directly to remove the data center So a certain question Do you foresee TXG transformation or expanding? I'm not totally sure that that would be on this truth that's not really exactly where it goes I mean I can imagine that those things might want to access the TPM for some reason but I really don't see where TXT would necessarily fit into that Well we need to just go down and talk about provisioning services on the client and the storage of the systems as the ultimate controller of the world and that's what I'm talking about You know maybe I do too TXT is kind of specialized it's really geared towards the boot environment not necessarily Don't have a good answer I'm afraid Any other last questions?  So I'm not a super expert on authorization but I'm pretty sure OAuth and OpenID have been investigated as options Winston do you recall if we're leaning any direction on authorization yet for hybrid and if everybody can catch that what we're doing is multiple keystones back with OpenDJ to ensure consistency across at least in the open stack environment that we have connected identities Our intent though is infrastructure service, platform service should all be in a hybrid fashion working with federated identity I don't think anybody's cracked this and we also we deal with the software as a service space too where we consume services that are completely outside of this ecosystem where we also have to have federated identity so I think there's lots of options out there just we haven't pinpointed the best one yet Pardon me OpenDJ is like a back in the LDAP It's open source LDAP solution There was another question in the back On auto scaling I had two questions basically We did a billing stack as far as a driver for cost based auto scaling I worked on an app that we did in Amazon and we left auto scale up to the application itself so it knew if my load is high and I'm doing this function I need more servers performing that function and they can spin them up itself Yeah, so our actual approaches applications should define it themselves like in Amazon you have auto scaling group and you set a policy that says monitor for this type of scenario and then take this action so that's fundamentally what we do today with Nagios we look for a threshold to be exceeded by CPU we tell our decider hey this has been threshold hit and check to see if everything in that collection is hit if so add nodes so I think most auto scaling concepts work in that fashion so yeah we expect many people to set the policy to set the policy and to be able to have their application work in such a way that it can auto scale up but the first question is billing stack Yeah, so one of the things that we found in Amazon is using their model we get a cost overrun that released and justified by the ROI so we need to have a model where we can say this app is only going to generate this much return How do we cap that? So your cost to sales and then yeah yeah yeah unfortunately not everything we do is associated with money sometimes just altruistic but yeah that's a good model in the grid environment we look at job slot utilization correlate that to giant chip projects and use a wall of shame wall of fame methods to help drive projects to right size but we do that when you have specific about a percentage of information Thank you folks


How often do you replace your router or mesh setup? My current mesh is a TP-Link that is Wi-Fi 5. Her cable company Cox recently upgraded the network and now my speeds have been doubled. Yay, and she has a DOCSIS 3.1 modem, so all good there. But must I also now upgrade to Wi-Fi 6? The reason I ask is because I suspect my router may be causing a bottleneck in the speed or it could be all the wireless devices that we have connected simultaneously. I also wonder if my network ethernet switch could be causing a slowdown. I'll retest everything now that the Cox upgrade seems to be complete, but it was looking like I only get the full speed when connected directly to the modem with ethernet and then I get less than half once I connect the rest of our devices via Wi-Fi or maybe that's normal. How much should one expect the speed to be reduced when the whole household is connected via mesh Wi-Fi? So my general advice, and we'll go into details here, my general advice is don't just replace your router for the heck of it. Even if you can prove that your Wi-Fi is a bottleneck, that's still not necessarily a good reason in my mind to replace it because your Wi-Fi with today's ISP speeds that we get, I mean you can like many areas of the country and the world can get gigabit speeds to your house. Very few people are ever going to, with today's technology, see gigabit speeds over Wi-Fi. So your Wi-Fi is always going to be a bottleneck at least in a theoretical or a test case sense. Like you'll be able to prove that it's a bottleneck, but you know, like for me in my office I have Wi-Fi 6E devices, right? Like that, you know, I have the Euro 6E and I get the same when I test other things and my office is fairly, it's isolated from the house, there's not a ton of Wi-Fi devices, it's not right next to the neighbors. And I get six to 700 megabits per second in both directions up and down when I test on Wi-Fi. That's, those are great speeds, but it's not gigabit. Like my network is capable of gigabit, my internet connection, because it's fiber is capable of gigabit, but I only see that when I'm connected on ethernet. The question to ask I think is, when do I need that kind of speed on my phone or on my Mac that's connected via Wi-Fi? Like what is, what am I trying to do that is being hampered by or what do I want to do that I can't do because my speeds are hampering me from doing that? And you know, your Macs might be those things, right? Especially if you're doing some, a lot of online backups or if you're transferring large files around in an office setting, and of course, lots of us have home offices these days, but that's really the question is, what are you doing that's being slowed down and what can't you do because of this technical bottleneck? That would be the question to answer. If you're getting, my general feeling for most of us is that if you test your speeds and you're getting on your Wi-Fi devices, you're getting above 200 megabits per second, you're probably gonna be fine. If you wind up, if you're getting less than that, then it's time to look at why are you getting less than that? Is it that you have the wrong mesh technology or older mesh technology and newer mesh technology would be faster for you? If the answer to that is yes, then maybe that's the right thing. Or is it that you have way more client devices now than you used to and somehow that's slowing down your mesh? The number of devices doesn't necessarily slow you down, but it can. And certainly as Brian Monroe in our chat points out, newer Wi-Fi standards support more Wi-Fi devices at sort of native speeds. That can be a reason, yes, if you've got lots of devices for sure. But ask the question first, don't just presume you need to upgrade by default. Find where your problem is. One of the, there was some discussion in Discord about, well, I don't have any Wi-Fi, one person said, I don't have any Wi-Fi 6E devices, so there's no reason to upgrade my mesh to Wi-Fi 6E. I think that, while all those things could be true, I think another way to interpret it is that's a great reason to upgrade your mesh to Wi-Fi 6E if you need more speed between your mesh points. Because if your mesh is speaking at Wi-Fi 6E, which operates on a different band than Wi-Fi 6 and Wi-Fi 5, then you have less interference in that band because you don't have any client devices, right? And so now your wireless backhaul, which is the connection between your mesh points, is freer and clearer, I don't wanna say free and clear, but it's less congested, and that can work out really well. Remember, the idea of a mesh network with multiple access points has been around for a very long time. It was mostly only implementable via a wired backhaul, like Ethernet connecting all of our mesh points. Up until 802.11 AC hit, right? Wi-Fi 5, when that hit, that meant that we could have faster speeds for our backhaul. And even though Wi-Fi 5 is operating at five gigahertz and it's not as good as going through walls as 2.4, the signaling protocols they used for that made it so that you got faster speeds. And that's what opened the door for companies like Eero and all the others to start making wireless mesh products for us consumers. And so they did, and obviously it's worked out really well. But yeah, having greater capabilities for your mesh to talk isn't necessarily a bad thing and can be a really good thing, so. But more and more devices are doing 6 and 6E. Yeah, so I don't know, those are my thoughts, yeah. No, that's a great point. Yep, yeah, so.


So you want to parent one particle to another not a problem. Let's say you have a fireball and you want the embers to follow that ball when it's moving around. Normally you will see something like this, which is obviously not what you want to fix it on the child particle, remove the spawn module and replace it with a spawn particle from emitter. Then type the name of the particle you want it to parent from and say fix issues underneath a sample particle module will be automatically added click it and under position sampling say apply to attribute you're done now you can see the sparks follow the ball the way they're supposed to quick tip if you have other position modifying modules like a shape location sphere make sure those happen after the sample module otherwise you're going to get really weird things like this anyway hope that helps and as always hope you have a fantastic day and I'll see you around