In 1959, Irving Goffman introduced the idea of geometrical analysis in his book The Presentation of Self in Everyday Life. This symbolic interactionist theory makes the analogy of life as a theatrical performance and states that how we present ourselves in everyday life is similar to a performance on stage. Kind of like Shakespeare's famous line, all the world is a stage. So in other words, when we interact with people, we are actors in a performance. The performance is largely based on the values, beliefs, and habits that we learn from social institutions and also our interactions with others. In situations where we don't know the others in the scene on a familiar or intimate level, we tend to present our front stage self. This front stage self is the version of us that we believe will be favorable to others. This is Maggie. Maggie is madly in love with Mike. Mike is an adventurous guitar player in a local rock band with multiple tattoos. His manners are questionable. He is known to belch on cue. Maggie's parents want to meet Mike. They have never seen a local rock performance, and Maggie's dad doesn't like tattoos. Maggie is nervous because she wants her parents to accept him. Mike tells Maggie he's got this covered. On the day Mike is to meet Maggie's parents, he shows up in a buttoned-down long-sleeve shirt hair combed and uses his manners. He never belches. Mike is the actor presenting his front stage self to Maggie's parents. When we engage our front stage selves, we also engage what is called impression management. In impression management, we engage in behaviors that we want the world to see and those are often favorable. Mike wants Maggie's parents to like him and he definitely wants to continue seeing Maggie. Maggie's parents think Mike is polite and respectful and encourage Maggie to continue to date Mike. Over time, Mike and Maggie's parents become comfortable with each other and Mike eventually shows Maggie's dad his tattoos and periodically forgets his manners. This is called the backstage self. This is the version of ourselves that we often present to those we are familiar with. What has happened is that over time, Maggie's parents have accepted him and they are familiar with one another. Mike is able to present his backstage self. On a daily basis, we engage in our front stage and backstage selves and in impression management. The more socially connected we are, the more we tend to manage what parts of ourselves we want the world to see favorably. We do this a lot in social media when we post a status on Facebook that shows we are compassionate. Or when we tweet a witty comment because you want to appear smart and funny. We do this in other instances when we dress professionally for an interview, shake the interviewer's hand and laugh at their jokes. Believe it or not, we engage in dramaturgical analysis on a regular basis.


Arlo says he got caught. Uh-oh. It was with interest that I heard the last episode where a guy was asking about using migration assistant with his new M2 MacBook Air from a 2015 MacBook Pro. I have both. Here's what happened. I migrated the data, but something bad happened. In spite of my 25 year Mac IT career, okay. I never used migration assistant at work. I was a Casper suite guy, which I assume is some sort of system configuration suite. Okay. Yeah, but usually work fine at home. The error upon rebooting after migration assistant got stuck in a restart loop. None of the usual keys, option command R, zapping the PRAM, single user mode worked. I finally looked up resetting the SMC on the Apple chip Mac command option shift power and then I finally got the recovery assistant to launch. I had to erase the drive and reinstall OS Monterey. Then the OS setup came up. By that point, I realized what I had done wrong before pertinent to your listeners question. I had left checked the system files box. And that's what started the restart loop. Don't. Interesting. This time I left it unchecked and it booted up fine with all my apps and data migrated. A 48 hour tale of woe, but a happy ending. So uncheck that box. No, that's interesting. Like we talk about, we often get questions. In fact, I think that last week's question was kind of that, like how do I, I wanna get rid of the cruft and the definition of cruft is different for each of us but also just in different circumstances. But I wanna get rid of the cruft without creating a headache for myself. And so moving apps and data over without bringing system files might be for some considered skipping the cruft. For some of us, it's all the apps that we install that are the cruft in and of themselves. So maybe you do move system files and data, I don't know, or maybe just data. Maybe that's the key. Just move data and then download the apps. Yeah. I'd be curious. I know we have a lot of consultants who listen to this show who help lots of people. And I'm curious what your kind of default is when someone's moving to a new machine and they've had the old machine for a while. You know, there's, to me, there's essentially three steps. I'm sure there's a lot more than three but the three steps would be full migration assistant. Just let it do whatever it wants. The other end of the extreme would be a hundred percent manual migration. And then there's the middle, which is kind of what we're talking about here. I'm curious what your decision trees look like as far as when you choose which one of those three or some other option. So yeah, let us know. Feedback at mackeykev.com. We'd love to hear from you.


What else do we have? COP28 is just the gift that keeps on giving. You keep getting different stories.  He is the president of that hosting committee for the event. He is also the CEO of the Abu Dhabi National Oil Company and the United Arab Emirates Environment Minister. Talk about conflicts of interest, right? So here he is hosting COP28, in which the Secretary General of the UN says we need to phase out fossil fuels now. The host is the CEO of a national oil company and also the environment minister. It couldn't get any more comical than this and ridiculous and evil. And I think maybe what he and the oil companies are all there as well. Maybe we'll learn from this is you can't appease the nutcases, but they probably won't learn anything from it. Anyway, this Dr. Sultan al-Jaber basically announced in a speech to the conference says, and I quote, there is no science out there or no scenario out there that says the phase out of fossil fuels is what's going to achieve 1.5. That's the 1.5, centigrade warming less than that is the goal. And he says, unless you want to take the world back into the caves. Now, of course, he's absolutely right. Of course, yeah, what's he doing hosting COP28 then? And of course, the comments just made people like Al Gore just apoplectic. Al Gore was like, quote, Al Gore. He should not be taken seriously. He's protecting his profits and placing them in a higher priority than the survival of human civilization. No, quite the opposite. You, Al Gore, by ending use of fossil fuel are the risk to human civilization, not the Dubai National Oil Company, which is keeping civilization afloat right now. Yeah, so Al Gore is flipping out. The UN is flipping out. Generally, all COP28 is there to do is to show how absurd and ridiculous the environmentalist agenda is, but how it has co-opted all the big money in the world. Everybody has to go. Everybody schmoozes. Everybody flies in there with their fossil fuel fueled copper jets.  But it's the exercise and the fanfare that it seems that anybody who wants to show that they care, show that they're virtuous, show that they care about the climate and they care about the planet has to attend. But the idea that the United Arab Emirates is actually hosting this event and that Al Jabao is the head of this thing, just shows you how ridiculous it is. At the news conference on Monday, I guess today, Al Jabao said he was quite surprised at the criticism, which he blasted as, quote, constant and repeated attempts to undermine the work of COP28 presidency. That's him. And the attempts to undermine the message will keep repeating that we respect the science. Well, if you respect the science, then you should have folded COP28 a long time ago. All right, he is surprised. One, I guess, positive kind of positive thing that was agreed upon in COP28. I don't know if agreed upon pledged. I don't know what the pledges means. They're probably worthless. But 22 countries pledged to triple nuclear capacity during COP28. I think that's all meaningless. It includes fans. Fans is unlikely to triple their capacity. They already have a significant amount of overwhelming majority of their electricity produced by nuclear. Maybe they want to do more and export it out to the rest of Europe, which is going to be hungry for electricity. When the sun doesn't shine, I don't know. But Britain fans in the United States, I don't think the United States is anywhere close to tripling their nuclear capacity by 2050. You would have to have projects in the pipeline right now to get them online by 2050. And it's just not happening. Anyway, it makes for a good headline.


Welcome to Toffy TV, it is the Everton News Daily. There is an article today in the Guardian linking Arashe Uzmanoff's money with Fahad Meshiri and Everton Football Club. There's a lot of fluff in this piece, there's a lot of stuff that we've heard for some time. There's not much substance in it, it's not the smoking gun I think they thought it was. In the article it does say that Meshiri had his bank account frozen, his UK bank account frozen when the links to Arashe Uzmanoff became apparent after a busher had invaded Ukraine and obviously USM, all the USM stuff for Everton. But there isn't a lot in there and I'll be honest, I don't know how much of it would actually hate Everton if it did come out. You know we've obviously, we saw Chelsea have to be put off for sale but there does seem to be a lot of time, those seems to have passed. Apparently the government are looking at this or a branch of the government are looking at this but we'll have to just wait and see what gets uncovered but I can't imagine it would really hate Everton. In fact it might actually help if Fahad Meshiri had to sell but as I said in the piece itself it doesn't seem like there's a lot in that. Obviously we are waiting for some kind of announcements in the coming days or weeks to do with MSPs involvement in the club. Again there's a lot of rumours going round social media about what could potentially be happening with CEOs and chairmans. Again I don't know how much weight there is to that. People are getting excited but they're also very impatient about the situation. Obviously Everton survived by the skin of the teeth on Sunday and people want changes. A lot of people are demanding changes and there is a rally down at the pier head in front of the live buildings on Saturday 11am where fans will show their anger at the current situation. Whether anything changes between now and then I don't know. There is a fab meeting tonight at the fan advisory board where Denise Barrabaxendale and Grame Sharp are expected to turn up or if it's not Grame Sharp it will grant ingles I imagine because I don't think Bill Kerr might be there. They are expected to be there tonight. I think they are duty bound to be there whether they turn up or not. If they do turn up it will be interesting to see what gets said or how much they participate. In the meeting I believe there's been a meeting before where the representative just sat there and actually hasn't said anything and just took on what's being said. So that will be interesting to see what comes out of that meeting if anything comes out of that meeting. I think fans are just waiting for some kind of change now after what has been another dreadful season. I know there was the scenes obviously were just pure relief on Sunday. The longer it drags on the angrier fans will actually get that change hasn't happened or it's not going at the pace that they wanted to go because it is a very short summer. It's June tomorrow and things need to move on quite quickly. So as I said the board rally is going to be Saturday 11am down at the pier head and that fab meeting is tonight so we'll wait and see if anything comes out of that. On the footballing front Neil Mopai has once again been linked to the Italian side Salatina. He's been linked to them for some time and they actually turned them down last summer to come to Everton. So that looks like that will be one that will probably be all parties will want that done. What kind of money Everton can get back on that? I don't know but we'll have to wait and see but that one would I think would suit all parties. And also John Philippe Gabamans agents has been speaking this week and said that they'll be looking for a new project this summer. He's been linked with a move back to Russia where he was on loan at CSKI. He obviously was on loan this season in Turkey. It didn't really work out. He spent a large amount of the second part of the season on the bench. That really hasn't worked out. He's actually said that they actually thought Everton were going to be a stepping stone club to move to a bigger club and he said he couldn't believe the way things have turned out at the club. Never mind for his player but obviously he did have two serious injuries which have really stopped this progress. He'll be another one Everton. We'll be hoping to get with all this summer if he possibly can. Obviously him and Andre Gomes have been on loan all season and I imagine Everton will be looking as they go into their final year of their contacts to move them on. Hopefully and get some money for them. Obviously a loan again for the two players would mean that the players would be leaving for absolutely nothing next summer. That's the last thing Everton want with the likes of Jeri Mina leaving this summer for nothing and other players in the last few years leaving for nothing. Everton has absolutely no retain. With the FFP situation the way it is Everton needs to get at least something through the door for these players. We'll have to wait and see whether that all works out in the favour of the football club. There you go. This has been the Everton News Daily. We will find out tonight whether there are board representations at the FAB meeting and we will report on that tomorrow. Make sure to give this video a like, subscribe if you haven't already. If you want more great videos, daily live videos, join us over on Toffy TV Premier. The link is in the description and it will be coming up on the QR code. Now, see you later.


Good morning everybody. You can find the cord for this sound and light out of this machine. We'll just do a quick sound check. Let's see my stuff come up on your screen. Good, it works. Apologising for breaking the space that Glenn just created. So the title of my presentation was, whole body photobiomodulation for fibromyalgia and other pain syndromes. Who here has heard of photobiomodulation? I can't see any of you. I have no idea. Are there any hands up? Okay, is that like half of you or 10%? I couldn't hear that. And who here has been treated with it? I have no idea what you're doing. I can see a bit if I do that. Okay, and what else did I say? Anybody here treated somebody else with it? You have to wave your hands a bit. Yes, I can see the movement that helps. Who here has never heard of it? It's hard to tell. It might be half of you. I'm not sure. Okay, right. So my plan for you is to say, what is photobiomodulation? How does it work? Something about its medical uses, specifically fibromyalgia and other health applications. When you do medical presentations, you have to do disclosure. So I am founder, CEO of Thor. I'm a co-founder and an investor in another photobiomodulation company called Luma Thera. So that means I'm extremely biased and you can't believe anything I'm about to tell you. I started life as an engineer designing radio stations. I'm not a scientist or a doctor, so you can't trust me that I don't know what I'm talking about. But I have been doing this a long time. Since 1987, 35 years in this field, I've co-authored 27 academic papers on this subject, six of them with Harvard Medical School, co-authored four academic books, my expertise on dos and bin parameters. I'm an expert reviewer for the journals that publish most of the work in this field. I'm a co-chair of the Biomedical Optics Society Conference of Photobiomodulation Mechanisms, and I've joined a couple of other interesting clubs. A lot of our collaborators are here on the screen here. Many of them from Harvard Medical School, Harvard School of Public Health, working on noise-induced hearing loss, Brigham Women's Hospital, treating children who are going through bone marrow transplants for cancer. They get nasty side effects. I'll say more about that later on. Traumatic brain injury at MGH Massachusetts General Hospital, doing experiments on mice and rats, looking on the mechanism of action, the dose response, the VA, we are already treating patients, and so I've got a small amount of time so I can't go through all of these, lots going on in our national health service in the UK, which by the way explains my speech impediment. It's called English. Anyway, so we're collaborating with 60 different academic institutions around the world, most recently lots of NHS, Stanford University School of Medicine, working on age-related hearing loss at the moment, among many. Fibromyalgia, what is it? You probably know. Fibromyalgia is the pits, isn't it? If you know anybody's got it, they've got pain, inflammation, tenderness. They're having sleep problems as well, so pain in joints, inflammation leading to fatigue, systemic inflammation, tenderness in muscles, sleep problems. They get brain fog as well. My wife, who's an osteopath, says it's very similar to long COVID, she says. Okay, that's fibromyalgia. What is photobiomodulation? It's something that your grandparents used to watch on TV in a TV show called Star Trek.  So we make those. Any questions? Okay, it's not as fast as it's on TV, but get the idea. We shine light on people and they heal more quickly. Live long and prosper. And if you're old enough, you know that voice. It's Mr. Spock. And if you use photobiomodulation, you will live longer and prosper. There you go. Anyway, unfortunately, these therapies have a lot of different names over the years. Too many to mention, but over 100 different names in this therapy used to be called mostly low-level laser therapy on the internet. If you know what pub med is, the government database for medicine, low-level laser therapy was the leading term. It is now photobiomodulation. Photom means light, biom means life. Modulation means we can stimulate and we can inhibit. We can slow some things down and already it's been reduced to PBM or PBM therapy or sometimes PBMT. So we're going to call it PBM from now on. Oh, it's stuck there. Right. What is it? It's the application of monochromatic light, which means light of one color. And if we have light at the right color, whereas we prefer to say the right wavelength, if we have light at the right wavelength, if we have light at the right intensity, and if we have it in the right place for the right amount of time, we increase the speed and quality of tissue repair. We can reduce inflammation and edema, and we can induce an analgesic effect. Most of the published clinical evidence is of musculoskeletal pain, so sprains and strains and creaky joints. But there's also good evidence for its effects on neuropathic pain like shingles and post-apathic neuralgia, hard to heal wounds like venous ulcers and diabetic foot ulcers, breast cancer-related lymphedema, fibromyalgia on the list, chronic regional pain syndrome. And also it has some effects and useful benefits for healthy people as well. It's used like this. It's applied to the body in this manner with handheld devices in and around the oral cavity if you're a dentist. Non-healing wounds being treated here. Cancer patients being treated for that. Very common to have oral complications, one of which is called oral mucositis. You can hear a bit more in a minute about that. And veterinarians are using it as well. And of course we now have this whole body treatment system where you can treat the whole body. And that kind of looks like that when you're using it. This is not a heat therapy. People assume lasers and red and near-imperial light must mean something to do with heat. No, the effectiveness treatment is more like photosynthesis and plants because humans and animals will photosynthesize. This is something you know already.  It's a form of photosynthesis. And you know that we use sunlight to help synthesize vitamin D. And you might know they use blue light therapies on prematurely born babies to reduce neonatal jaundice. Another form of photosynthesis. Doctors or dermatologists specifically will use ultraviolet light to treat psoriasis and vitroligo. So nobody should be surprised if light has other effects on the body. Now, normally people think of lasers and medicine as being used for cutting and ablating and quarterizing tissue. Well, not all lasers are dangerous. If you're old enough, you may have seen this movie, Goldfinger with James Bond. So not all lasers are dangerous. That's because there's different classes of lasers. The lasers used in supermarkets or my lecture point to hear, nobody gets hurt with this thing. Lasers are not necessarily dangerous. The dangerous ones you're thinking about in medicine are the class 4 lasers. These are the ones that have a thermal effect. We use class 3B lasers. They have no harmful effects on skin or clothing, but they are potentially hazardous to the eye. So you, your patients and the observers would wear laser safety glasses. We also use light emitting diodes, LEDs. They've got some similar qualities to lasers. We don't have time to discuss today. But we use those, and you don't need all the safety glasses, but they have the same effect. Very briefly touched on the history. It starts with Albert Einstein. Seems to end up with me. Great slide. My mum would have been proud. Einstein came up with a theory about amplification by the stimulated emission of radiation, LA-SER laser. This guy wanted to, actually made the first working laser in 1960. This guy wants to find out, does it cause cancer? He does an experiment on mice. He takes a group of mice. He shaves the hair from their bodies. He divides them into two groups, puts a low intensity laser beam on one group and not the other to see if the treatment group has cancer. They didn't enter his surprise. The hair grew back more quickly on the treatment group compared with the untreated group. That's how he discovered photo by modulation. Over here in the United States, things really didn't lift off until NASA got involved over here. That's my best joke of the day. Things didn't lift off until NASA got involved. You have to be old enough to know these things. We've got SpaceX and Blue Origin and the galactic thing that Richard Brownson does and NASA, I mean, there's a rocket going up every day now. It's stuck. Anyway, yes, NASA wanted to find that we're planning man missions to mask the problem for astronauts in the long space flight as they lose bone density, they have muscle wasting, they cut themselves shaving, they don't heal, they wanted to find out if there was something, you know, if this magical light, photo by modulation would help with the life and longevity of astronauts. Now, on a trip to Mars, they haven't been to Mars yet, so we don't know, but they did some interesting research on the field. But subsequently, I suppose the field really took off when I suppose around 2006, the Journal of Nature published an editorial on the mechanism of action, the Journal of Pain from the International Association for the Study of Pain on the treatment of photo by modulation for neck pain down the World Health Organization. They started recommending it for neck pain. The Lancet, the world's leading journal for breakthrough medicine, started recommending it for neck pain. American Physical Therapy Association, Achilles Tendinopathy's International Association for the Study of Pain, strong evidence in their systematic reviews for myofascial pain syndrome, frozen shoulders, tennis elbow, lymphedema, low back pain. American College of Physicians guidelines now say, recommended as a non-invasive treatment for chronic low back pain, a strong recommendation, Blue Cross Blue Shield and they're all saying it's medically necessary. In the UK, National Institute for Health and Care Excellence, the guidelines now recommend photo by modulation for cancer patients at risk of developing oral mucusitis and so on. Eventually, we end up down here. JAMA, the Journal of the American Medical Association says it's an option. It's not a strong statement, but it's a start. I mean, it's a hugely influential journal for low back pain lasting more than 12 weeks. So now, for the field, there's over 1,000 randomized placebo-controlled clinical trials on humans published in peer-reviewed medical journals, more than 4,000 lab studies, 660 academic papers published last year on the subject, 8,500 academic papers in total for our own products, 34 million treatments have been performed to date. Yet nobody's heard of it, or most of you haven't heard of it. Anyway, state-of-the-art is the strong evidence of muscle and joint pain, all of the mucusitis I mentioned, the cancer therapy side effect, dry aid-related macular degeneration, the leading cause of blindness in this country, improving strength and endurance and recovery in athletes, and other things I've kind of mentioned some of those already, but we're going to move on due to time. So moderate levels of evidence just means small clinical trials and not many of them. Experimental means mostly just case series papers, anecdotal means not even that, just anecdotal. How can one medicine treat so many different conditions? You know, you should never leave anything that appears to do everything, and when it doesn't do everything, it does one thing, it has a profound effect on mitochondria. You may know that mitochondria are often, if you learned about a bit of biology at school, they were often called the powerhouse of the cell. They take up glucose and oxygen and make cellular energies probably what you were taught. Okay, so mitochondria is a cartoon picture of one, you have hundreds and thousands of these in every single cell of your body, and when we're sick and when we're injured and when we're stressed and just gradually as we get older, our cells tend to be low on energy, ATP. They tend to be high in oxidative stress, which is a bad state for your cells to be in. They're making too many reactive oxygen species, free radicals if you like, that lead to oxidative stress and the over stimulator gene transcription that's called NF-Kappa B. This is as nerdy as it gets, and it's going to get easier from here. The master switch for inflammation in every cell of the body is all those inflammatory cytokines we've heard about with COVID, for example, the inflammation cell death, necrosis, degenerative diseases, and generally accelerating the aging process, which is why you want antioxidants in your diet, for example. But when we put light in the patients, we can put it exactly where the injury is. We put light in to get absorbed in mitochondria, and the state of the cells changes to one where it makes more energy and less oxidative stress.  We get these regenerative effects. If you've done any biology or a doctor, or anybody out there, these are anti-inflammatory mechanisms you might be familiar with, get turned on, regenerative mechanisms if you've done enough biology, but leading to tissue repair and tissue survival. I love what Glenn was saying earlier. It reminded me that photobiomodulation basically leads to health cell home estasis, or a state of peace, as he was saying, if you want me to put it in the terms of this conference. That has some interesting downstream effects which I'm not going to talk about. But this is basically what happens next after you put light in. That leads to faster tissue repair, less edema, less inflammation and less pain. There is a dose response. If you don't have enough intensity, there's more light. If you put a bit more light in, you get positive effects on inflammation and repair too much.  So we try to keep people inside this therapeutic window. So medical use of it. Its regenerative is one of its features. Oral mucositis. There's over 60 randomized placebo control clinical trials with this horrible side effect of chemotherapy and radiotherapy. In this study here, the five grades of oral mucositis in these cancer patients who are going through chemotherapy here. This is grade four oral mucositis in the placebo group. You can see that the placebo group get most of the grade four. These patients cannot drink or eat or swallow solid food. Grade three patients can drink liquids but they can't eat solid food there. And you'll notice at the dial up bars which are the active photobiomodulation group, only one patient get is in grade four with where they can't eat or drink. Everybody else has got mouth soreness, just erythema in the mouth or nothing at all. So PBM has moved these patients from the severe end of being able to eat or drink down to this end of the scale which is low grades of pain, inflammation or just visual erythema or nothing at all. It's highly anti-inflammatory and it's regenerative. This is a neuro sensory recovery after injury to the inferior alveolar nerve.  It then just pulls your third molar out through the wisdom extraction there. Sometimes the roots of the tooth get caught up in the nerve. They pull the tooth, the nerve snaps and it doesn't heal by itself within a year.   These patients have had it for more than a year, they've got this is my point of that. Now at the bottom there, they're getting a low score on the brush stroke directional discrimination test, the dentist closes their eyes, the patient closes their eyes, the dentist does the test, they can't feel anything. They've got a very low score, a course of treatment, photo by modulation three times a week for seven weeks, 20 treatments in all, you get recovery of the nerve. In medicine, does this apart from photo by modulation? If you can see four kids in my kitchen, you do not have dry age-related macular degeneration, the leading cause of blindness in this country.  With the treatment in my co-founder in this business disclosure, there, an investor in the company, we just finished 18 randomized controlled clinical trials across the world, it's all in the hands of the FDA now and we expect that early next year the product will be released and for treatment I'll just show you one set of data patients here from their baseline have an improvement on the Snellen chart, you know, the chart where you get the ophthalmologist, where the letters get smaller you have this increase in visual acuity, five letters effectively means you can read one line further down the chart and for most people that means the difference between losing your driving license or not, for example, and that they get a course of treatment in month one and then we measure them three months later and the improvement seems to be continuing even though we stopped treatment, you stop for too long, the treatment, the benefits disappear but you give them another course of treatment, they come back again, we stop the treatment again, it goes away again and so on. So degenerative diseases are not curable but we can get rid of the symptoms of dry AMD and this is true for all degenerative diseases with this technology, you treat it, if it's degenerative like your knees, your osteoarthritis, your brain with your Alzheimer's or your eyes with the disease, it always comes back so you need more treatment.  So get that bit handled, it's anti-inflammatory, here's an experiment done on athletes, they've got Achilles tendinopathies, they do something called a micro dialysis measurement for PGE2 concentrations, that's an inflammatory marker, so you stick it in the Achilles tendon there and then they get a treat, I've missed the graph off, but you know the answer, we do active treatment group to a placebo group and you treat their Achilles tendon, the inflammation goes down in the treatment group and not in their placebo group. Sorry, I missed the graph off of that. It's analgesic. Potipatic neuralgia is one of the worst kinds of pain that anybody can get. People can't lie down, they can't wear shirts, they can't bear to be touched, it drives people to suicide, it's that kind of pain, typically around the thorax here. So in this study here, just a small study, 20 patients have had PHN for a mean duration of two and a half years, that's six to eight years. Only one treatment a week, I thought this wasn't going to work. The treatment group, the pain comes down on the pain score, doesn't happen in the placebo group. It's a crossover trial, that means this group B, get the active treatment, this group go on to placebo and that pain doesn't come back and it stays away. 95% of patients discontinued all medication for a month. 5% had a reduced dosage and at six months follow up 80% of patients have maintained their pain reduction. And nothing else does this. This is the use of opioids by cancer patients having all of these there is a 68, you can't see my dot really, but 68% reduction in the use of opioids and this has been repeated multiple times. Like I said, there's over a thousand randomized controlled clinical trials. Post-operative pain, I know of three off the top of my head which show approximately the same 68, 70% reduction in the use of opioids if they have this treatment after surgery. Myofascial pain, these are the tender points you get on your body, you know somebody massages your neck and says you've got knots in your shoulders, press on that or something like that. Systematic review published in the Lancet the world's leading journal for breakthrough medicine say that those myofascial trigger points in your neck that basically stop people from being able to turn their heads. If anybody who has a problem like this and can't fully rotate and turn their head, we should treat you later on. PBM works well for reducing those points. It improves sleep. Chinese People Liberation Army study here lying under a red LED lamp, not fully closed they would normally be in their underwear, get a treatment every night. What happens? They have an improvement in serum melatonin so the melatonin levels in their blood, it doesn't happen in the placebo group. They have a reduction in the Pittsburgh quality sleep index that measures the negative aspects of sleep like insomnia for example goes down in the photo by modulation group, it doesn't go down in the placebo group and they also do some exercise tests. They have to see how far they can run in 12 minutes and they run further than the control group does. They rather have an improvement in that too. Fatigue, we do experiments on people where we put them on a biodex machine, how much exercise they can do, repetitions on this machine which measures the amount of exercise they do, then they either get cryotherapy or they get photo by modulation or they're ice followed by PBM or PBM followed by ice or placebo. So there's four goots and a placebo and they do blood tests before and afterwards one hour, one day, two days and three days afterwards and they also do strength tests and they do pain tests and photo by modulation after that exercise, blood test for creatinine kinase, a marker for muscle damage here shows that it's down here and the red line at the bottom here compared with all the other groups, photo by modulation reduces delayed onset muscle so there's less pain means all the groups that have photo by modulation have got less pain compared with cryotherapy or placebo treatments down there. Maximum voluntary capacity strength in newton meters these people are back to full strength the next day and the day after that it doesn't happen with ice therapy or cryotherapy or placebo. We were first introduced to Novathor at the 2016 Olympic trials. Alberto Salazar had a unit at his house. He offered Justin the ability to use the Novathor bed that he personally had to help him get through the rounds. And it was crunch time and I'm running with an ace bandage on and then this comes to me and he says look you know we're going to go over here we're going to try this Novathor out and I literally did it maybe the day before because sometimes athletes are really skeptical about doing things the day of their meet and they don't want to break routine and I remember getting off the bed and I felt so rejuvenated I just felt like my cells were just popping like popcorn and I told Dennis we got to go over there before the finals of the 200 so we went to the day of the race so the next day we went there again I got a Novathor treatment and I felt great I went out there the odds were against me I was running in lane 8 so I was running blind and I was still up in air about this this nagging injury I had and I went out there and ran one of the fastest times in the world at that point in time to make the Olympic team. The difference between him one day to the next day using the Novathor bed was like night and day and we knew he had a really big race and his competitor which was a Nike athlete too was also using the bed so we kind of had a little hey you can't get it better than I can kind of thing and Justin ended up squeezing him out by a couple of hundredth of a second to make the Olympic team and win the Olympic trials so at that point we were sold on Novathor stop that there and let's jump to the fibromyalgia so basically I'm building up to the story with fibromyalgia being the pits pain, inflammation, tenderness and sleep issues fibromyalgia we did a randomized controlled clinical trial on 42 patients no benefit in the first two weeks of any significance but by about week four they're using it three times a week for four weeks you begin to see the pain levels coming down on the scale and then you stop treatment and it continues to get better and this is a consistent thing we find with this once you've started people healing, treatment doesn't just take away pain it actually helps you heal and once you stop using it you still got momentum to that and so the scores continue to get better over time quality of life goes up here over the same period of time if you're a statistician out there you'll know what a co-insidious and a p-value is .05 is good .01 is better .001 is extraordinary co-insidious anything better than .8 is good 2.5 nearly is enormous very strong very effective treatment leisure activity not much after two weeks and then four weeks you can see it jumps up people have more confidence to go out and use their bodies I'm aware that I'm up against my time limit then I'm just going to say there is one more thing I'm just going to show you how it actually reduces inflammation and what it does for the longevity of the brain and the health span but the one more thing we actually do is to make something that actually treats your head as well I've now run out of time so I'm going to thank you all for coming and you may now clap your hands wow there's another crowd there


Thanks everyone, welcome for joining this session as 210, so I'll just go ahead and start. Our session is about the Milded Cluster Github's application delivery, and it's about the integration between Argo CD pool model and OCMs hub and spoke pattern. So hopefully you are attracted by the Argo CD pool model portion, and we will go ahead and discuss them in more details. So before diving in, I do want to give a quick update about ourselves. So my name is Mahee Chen, I am from the Open Cluster Management Application Life Cycle Squad. Our OCM project focuses on a lot of components, and we are mostly working on the application deployments. So I am a full stack software engineer. I work on both the UI portion as well as the backend portion, but today I will be focusing mostly on the backend. And Xiangjin is our team lead, and he is a principal software engineer, and we work on the same project. If you are interested in our code base, feel free to check our work app pages, it's listed here. We also have our LinkedIn profile linked in the schedule, so feel free to contact us on LinkedIn. So you may wonder, what is OCM? OCM stands for Open Cluster Management. It is a CF done by project, so community approved, hopefully, and it does multi-cluster, multi-cloud, cumulative cluster management. So that you can deploy application policies and stuff to manage cluster in a scalable environment. So we are using the hub and spoke architecture, which I'm going to show you the diagram shortly. Lastly with OCM, you will be able to get a centralized view of your entire fleet. So on this diagram, and this is our hub and spoke pattern, you can see on the hub cluster, we have the placement resources that's going to deploy a placement decision. So placement decision is going to bind cluster sets, so that way you are able to select a set of clusters to deploy your application or policies to. Placement itself has predicate so that you can perform label selector or claim selector, and in the prioritize, you can see how many of clusters are actually selected. So on the top right, we have a YAML template that shows the placement decision. You can see I'm using the cluster set global. With OCM, you will get a default global cluster set that's going to select all managed clusters that you got. So you can narrow that down to just using a label selection. So saying I only care about cloud on Amazon, so you can do cloud in Amazon or any other provider connections. Another resource that I briefly covered is the managed cluster.  So that way you can get a list of managed cluster that are specified to certain cloud providers. So as of today, ROCD mostly just use push model, which is quite simple. On your hub cluster, you get your ROCD operator and it's going to create an application set that generates a set of applications. So ROCD's application controller will then come back to the remote cluster and deploy the resources from the application to the remote clusters. So it's just like one way from the hub to the managed clusters. What we are proposing and which is currently merged by the ROCD community is the pull model. So you can see that aside from the ROCD icon, we now have the OCM icon, which is the proposed cloud thing. So we now interact in between ROCD hub and managed clusters. So same thing on the hub cluster, you still have the ROCD operator and it's going to generate the applications. But instead of connecting to the managed cluster and deploy resources directly, our OCM propagation controller actually see those applications and they're going to create manifest work objects wrapping the application objects as payload. And our agent on the managed cluster is going to see them and pull the application from the hub to the managed cluster. So as you recall in the previous slide, there's no applications on the managed cluster. But now we have each application on each managed cluster. One prerequisite for that is you need to install the ROCD controller on the managed clusters. There are a few different ways to do that. First, you can use OCM's policy template to generate that to each managed cluster. Or you can use what Dan Garfield just demoed this morning. Thanks for coming. Now you can use RGOS of RGOS to install those operators on each managed clusters. So there are different approaches that you can perform. And then RGOS CD controller will see those applications and perform local cluster deployment. So why do we want to do this? It does provide a few advantages. The first one is that it's going to scale better. We do have some skill tasks that's just going to cover shortly. And we also increase the security by no longer requiring the credential to be stored in a centralized location, which is a hub. Lastly, it's reducing the impact of a single point of centralized failure.  Now I'm going to pass over to Xiangjing for more details. Okay, so here we can see this is the whole RGOS CD promotional architecture. So that looks very complicated. There are a lot of clothes. But let me try to break down into three major parts. The first one is located here. So we call it a propagation. And actually we have the local propagation and the remote propagation. I will talk about it in detail later in the next slides. But before that, I just want to highlight the purpose of this propagation is to deploy the RGOS CD applications to the managed clusters. So we are not deploying resources to the remote clusters. We just deployed the RGOS CD application templates to every managed clusters that our placement decisions already selected. And this is the first major components located here. And the second part is the local or deployment. So once the RGOS CD application is deployed on each of the managed clusters here, and then the native RGOS CD application controller will be reconciled. It will be a pool resources from the Git repo and Helm repo and it will also deploy the resources. But just for this given a managed cluster. So they're not talking to all the other managed cluster. So as Maggie just mentioned, so one managed cluster, we have just one RGOS CD instance running on that managed cluster. And see here, the last major components that's showed here. So all of these components there are just for one goal. So after we deploy all the RGOS CD applications to all managed clusters, and then we need to find a way to fetch the RGOS CD application status from all the managed clusters. And then we collect it into the database and then we have some aggregation controller finally to aggregate all the status, including the overall status and the per cluster condition status. And then we combine them into one final resource. That's the new series we introduced in the pool model. We call it multi cluster application set report. So here, so that's also located in the original RGOS CD application set that the user created. Okay, so let's talk about some details in each of the major workflow. So the first one is the two publications. So here is the user. Firstly, they create the RGOS CD application set in a hub namespace. And then at this point, the RGOS CD application set controller will be reconciled to do this local propagation. So this is the total functionality provided by the RGOS CD. So we're not on it. So after this propagation, then we can see, let's see, if are the clusters numbers is the 1000s, then this native RGOS CD application set controller will be creating a 1000s RGOS CD application templates into the same namespace. And then here, the second propagation is owned by us. We introduced a new controller. We call it a propagation controller. So that will be a reconciled to do the further propagation. We call it a remote propagation to propagate this RGOS CD application templates from the hub to a given managed clusters by using our manifest work API. So the idea is that so using this manifest work, then we are able to specify a cluster namespace that we want to deploy a specific workflow to this given managed cluster. So here, let me show you some details. So hopefully you can see it clearly. See, this is the one sample for this manifest work that's actually supported by our open cluster management community. See here, two highlights, one is the namespace. So these namespace is actually the cluster namespace. So as Maggie just introduced in the OpenShift cluster management introduction, then every managed cluster, we have a cluster namespace created on the hub. So if you want to deploy something now to that managed cluster, then you have to create a manifest work here to specify the cluster namespace. And see under the spec, we have two major sections. The first section is the manifest configs. And actually, we're defining some feedback rules here. So the purpose is, so once the Agosti applications is deployed to the managed cluster, then we're hoping to fetch some of the status from that application status from the managed cluster. So here, by using these feedback rules, then we're able to define it using the JSON pass. See, as you can see here, so we are actually fetching two status. One is the health status. The other is the sync status. So those are the overall status reported by the Agosti application status. Yeah, this is the first section. And the second section is the workload. So that means that this is used by the manifest work. Then we will define which manifest we want this manifest work to deploy to the managed cluster. So as you can see here, this manifest, that's actually a regional Agosti application that templates here. So there's nothing special here. But one thing I just want to highlight here, because of the poor model, we actually are leveraging the Agosti instance running on each managed cluster to do this local deployment. So the destination here, that it has to be the local built-in server URL that's provided by Agosti. So if you are familiar with Agosti, then you probably already see this server URL for multiple times. Okay, so once this Agosti application is deployed to the given a managed cluster, then the next step is totally owned by the native Agosti applications. So we're not on it. So we just deliver the Agosti application template to the managed cluster, then the Agosti application controller will be reconciled to our poor resources from the Git repo, Helm repo, and then do all the local deployments. But just on that managed cluster, and they have all the status reported on that managed cluster either. Okay, so the last major part is, okay, so once we have all of these application deployed and on all the managed clusters, and the next step is we need to find a way to collect all of these multi-cluster application status from all the managed clusters. So here we actually have three major components to support these status collection and aggregation. So the first one is, so we are leveraging our OCM search component. So each search collector is running as agent on each managed cluster that's managed by our OCM components. So it's able to collect all the Agosti application status from each managed cluster. And then it saves all of these status to the search postgres database running on the hub cluster and for the later query. And then the second component is the resource sync controller. So that's provided by our promote components. So we are actually running periodically a search query for fetching the resources list and the possible error conditions from all the Agosti application that deployed on all managed clusters. And the third components we are using here is the aggregation controller. So I just want to mention that these are aggregation controller and the resource sync controller. So they're all running in the same pause as the sidecar container. So the reason is once the resource sync controller is able to fetch the application status and then it's generate intermediate layer of these status into a YAML format files into these shared warrants in the pod. Then these shared warrants will be picked up by the aggregation controller. So from here, see these aggregation controller is also combined two status. So it's actually a fetch the overall status from the manifest work. So I just showed it. So we specify the JSON pass for fetch the overall status including the health status and the sync status. And the second one is also able to fetch the per cluster condition status from this intermediate YAML output. And then finally by combining all of these information. So we're able to generate final multi cluster application set reports here into the same application set namespace. So this is how the application status collection and aggregation works here. So here I also posted a YAML file here for the reference seed here as I just mentioned. So our resource sync controller is used to fetch all the cluster conditions from all the managed costs by using the search components. Then we will generate this YAML format result into the shared volume in the pod. So one application set is actually have one YAML format output here. So here is the first session is that we can we are able to get this resource list from the first application we deployed to the first managed cluster. And also we have all the cluster conditions. So we have the cluster name and we have the sync status, health status. So these are sync status and health status are there empty because we will use the manifest work to get this overall sync status and the health status. So but here we also have this conditional list. So that will be used for reporting any possible error conditions that this application could have. So if there's no error conditions then this conditional list will be empty. Okay, so I think those are the some of the instructions for this architecture overview. Okay, so let's talk about some prerequisite to be able to use this promo model. So we actually have four prerequisite but I just want to say those are almost all of these prerequisites that they are required by the ARGO CD. So in order to use the promo model then we have to follow the ARGO CD way to set up these conditions correctly. So the first one is so we need to install the ARGO CD operator or the OpenShift GitHub operator. So while they're actually at the same thing. And this OpenShift GitHub operator that's running on the hub and all the managed clusters. And it has to be installed in this fixed namespace the OpenShift GitHub. The second prerequisite is the on the hub cluster. So we have to import all the managed cluster secret to the OpenShift GitHub's namespace. So that's also required by the application set controller because if there's a no cluster secret located in the ARGO CD server namespace then this managed cluster won't be identified by the application set controller. So the first local propagation will fail. So it won't be propagated the ARGO CD application to that managed cluster. If it's not, there's no such cluster secret in the namespace, okay. And the third one is so this is also required by the ARGO CD application controller. So right now if we want a deployed something out to the managed clusters into a specific namespace then we have to set up this particular label to let this namespace are managed by the application controller. Otherwise, so there's no RBAC control. So all the deployment will fail. Okay, then let me go back to Maggie to talk about the other prerequisites. Yeah, so I feel like it's important. I just want to say that we do have content meetings with ARGO CD community. We attend their meetings quite frequently. We propose and we have PRs and we have iterations of PRs. So it's currently in the official ARGO CD documentation and you can find the use of it that it's specifically for open cluster management with the pull integration. So you will need to have the skip reconcile to perform the pull model on the application. So now I'm going to show you an actual, oh, sorry, I think someone was taking a picture. Sorry for injecting. Okay, so now I'm going to show you the official demo. It's also a recording because I don't want to show something surprisingly. But before I click on the play, I just want to point out that we have the terminal, okay, I can't re-merge it. So essentially we have the terminal for the hub and to manage cluster. So I'm going to perform the application side deployment on the hub cluster. So now I'm listing the manage clusters and you can see I have demo zero, demo one and my local cluster. I am now applying the application set itself and you can see the placement and applications that are created successfully. Let's take a look at the application set itself. So let me scroll up and pause right here. So you can see that I am using a placement called bgdkappplacement that selects the demo manage zero and demo manage one. I'm going to show you the placement shortly. But I do want to point out under the metadata annotations there are some OCM specific labels. So such as the OCM manage cluster that's going to inject the manage cluster name. OCM manage cluster app namespace which was the one we defined as well as the script reconcile and you can find more documentation on it on the official argue doc. So now if I, oh, aside from that you can see the other spec like destination projects where it's just what you would usually create application set. We didn't do much variations on this spec. And let's take a look at the placement. So for this placement I didn't use AWS. I'm using environment to demo and you can see I'm using the global cluster set and I have two clusters selected and it's also reflected under the status. In terms of the placement decision you can see I do have a list of decisions which shows my two cluster names. Now let's take a look at the application and you can see they are deployed on the hub but our actual managed cluster deployment are not from the hub. We are going to have an application on each managed cluster itself and you can see that they are created by OCM's propagation operator. So resources are also deployed. You can see the replica set deployment everything was in the healthy steps and including route as well. So let's take a look at the application demo itself. It's the same Argo application templates. It has a list of resources and what the status of those are. They are all healthy which is great. And on the help cluster let's verify those status by OCM's multi cluster application set report. So this is a resource that's created by OCM and you can see that we do have a list of resources and under the cluster status they're all healthy. Resources are listed here and we have this overall status by saying we have two clusters selected and both of them are healthy and they are all synced. So that's the success route. I mean in general you would have progressing stock or actually felt status. So I do want to show you that. So now I am deploying an application set that's going to get stuck. So you can see it's actually in a sync state and progressing on the managed cluster. So take a look at the application on the managed cluster. It should go into reflect what you just saw. So even though some of the resources are synced you can see we have certain resources that stock in a progressing state and we do have the messages. They are waiting for some rollouts and they will never end because we intentionally made them to wait for something. So we do want to make sure the multi cluster applications that report also get reflected. And as you can see under the summary we now have two clusters, none of them are healthy and they are always in progress. So if you scroll up you still have a list of resources listed but the health status are now stuck in progressing. They're still in sync so that's a good portion. By the way all of the applications are using the same placement so they are both deploying to the two managed clusters. So now I am applying the third application which is going to fail. On one of the managed cluster I just want to verify that they failed which is the case it's no longer in sync. It's now missing health status and it's out of sync. So on the application itself you can see that if you scroll up their health status are in missing state and they are out of sync. I do want to point out that one limitation we have is that even though those resources failed they ideally they should still get reflected on our hub which is the multi cluster applications that report but that's not the case. So if you look at the resource list we only have a service kind which is not true because you can see that we have deployment that failed. So that's one of our limitation slash bug that we should enhance. So I just want to point that out but aside from that we have not healthy and not sync status which is true. So under the condition we also have those failed messages reflected from the managed cluster to the hub cluster. That's pretty much it for my demo portion. So let me go ahead and discuss the limitation. So I already covered the number two which is that we should have all of the resources from the managed cluster to the hub which didn't happen nowadays for the failed state. One, another limitation we have is that resources are only deployed on the managed clusters. So with the pool model they are not deployed on the hub cluster. And lastly in the pool model we are excluding the local cluster as a target managed cluster. So there are a lot of different ways to reach us if you're interested in the pool model or want to enhance the pool model. So we have the GitHub page, we have website and docs. If you want to interact and reach us we have Slack channel, YouTube channel, mailing group and community meetings. You can also reach us on LinkedIn if you're interested as well. Johnny, do you want to tell about the skill test? Yeah, okay, so I just want to mention there is, so as Maggie just mentioned there are some limitations that we already identified. And that's partially because the limitations for our search component and our manifest work limitations. Firstly, so right now our manifest work is the feedback rules as I just demoed. So it's only supported to fetching the string data type. So it's not supported to fetch the list data type. So that's why we have to rely on the search components to collect those list resources and the list of the error conditions. But the search components, so one of the major things is that it has to be find all the resources that actually are deployed on the managed clusters. Which means that it has to have the UID. Otherwise, those filled resources won't be fetched by the search collector. So with these are two limitations that we identified and we actually have a roadmap plan that's under the consideration. So I just want to share it here for you guys. So our manifest work, we already have a proposal to enhance our manifest work API. So by that way, then the manifest work, we'll be able to fetch the list of data as a raw JSON. So with that way, then we just need to fetch all the overall status and the per cluster condition status from the managed clusters by fetching the status from the manifest work status directly. Then if our data is ready, then we probably will drop all of these search components dependency in the future releases. So that will provide us more efficiency. The other one is I just want to spend maybe 30 minutes to talk about some of the performance tests. So they're still underway, so we're not finished, but we just want to prove that this advantage of the scalability by using this core model. So actually, so we run this case, we actually deployed 20 before that. So I just want to share our two numbers that our thanks to our GitOps OpenShift GitOps operator team. So they actually talk about two numbers that right now are the native Agocity they have. The first one is the total numbers of the application that they can control. So they found that once the numbers of applications are using the push model is over 1,000, the whole Agocity application UI will have some performance issue, so they're not stable. And the second number is, so they found that once one Agocity instance, they are deployed resources to over 100 clusters. So they also are hit some performance issue. So here we already run some performance tests using this core model and our scenario is so we deployed 20 application sets to our 500 managed clusters. So the total numbers of applications that would be the 10,000 applications in total. So using two and a half minutes, as soon as we get all the managed clusters reported in our final multi cluster application set report. So those are the rough performance status I want to share here. Okay, so that's it. Thanks. Any other questions? Can you, yep. I saw on the demo for the application set deployment that you had an annotation for targeting a managed cluster. If you don't use that annotation, are you basically saying I want it to just go to all managed clusters or is there a way to have an application set just go to auto all managed clusters by default? Yeah, yeah. Like if you does not specify the predicates, it's just going to use a cluster set, which is the global cluster set that's going to deploy to all clusters. So it's just like if you want to select a set of the cluster, that will be a way, but you can definitely have the choice to deploy to all clusters. Right. So maybe to be more specific, oh, sorry. Yeah, we can't be close. Yeah, essentially you can delete everything under the spec, to be honest. And you can also delete everything under the predicates. It's just an option for you to narrow down the list. Thank you. No problem. So on a scale of one to 10, where one is your pre-alpha and 10, this is in production and it's bullet proof. Where would you put the OCM or another question is do you have customers that are using it today in production? I think we, do we have any like in real customer? I think it's still under development and that's why we want to be here to raise some awareness. So we are going to develop more in next release, but this is, I would say in alpha state. And you can see we have a lot of prerequisites, which is not ideal. And I am looking forward to collaborate with all the more so that maybe we can reduce the number of prerequisites to, maybe just one. Okay, thank you. Right. And so for this promote feature, so we are planning to release it in our downstream project called ACM, that will be released in this June, so in 2.8. So that will be published along with that release in June. Is there any question? If not, I think, thanks everyone for joining. We are looking forward to see more contributions in the future. And thanks Argo. Thank you. Thank you.


In this presentation, we're going to take a look at an adjusting entry related to breaking out the short-term and long-term portion of a loan balance. Time to rise above the crowd with Sage50Cloud, accounting. Here we are in our Get Great Guitars file. We're going to go on over to our reports first, so we're going to go to the reports dropdown. Take a look at those financial statement reports. We want to look first at the balance sheets. Let's open up the balance sheet reports. We're looking at the cutoff date being the end of February, so we're going to pick the month of February and say, okay, so then up top we have our report for the balance sheet. Now we're going to be looking at the liability accounts down here, so we're going to the liability accounts. We have a couple different loan balances. We've got these two loan balances. We're thinking about the cutoff dates now in terms of getting the financial statements correct as of the cutoff date, as of the cutoff date of February 29th, so these are the adjusting entries that are going to get things right as of that point in time. With regards to the loans, typically when we process the loans or show the loans, oftentimes we want to group the loans together into one short-term account and one long-term account. In other words, what we currently have are two different loans. We've got two different loans on the books. We put them both into a current account. We haven't broken out between short-term and long-term because that's going to be easier for us to tie out to the amortization table as we have done for this loan, which is the one we're going to be concentrating on. That 69, 878 then ties out to the 69, 878 on the amortization table. However, there's a short-term portion and a long-term portion to it, so we not only need to do that for reporting purposes, we also need to break out the long-term portion. That's what we're going to do here. We're going to break that out. This second loan is all short-term, so it could remain in the short-term portion, however, you may want to group the short-term loans together into one basically loan or short-term loan amount, and you could do that by doing an adjusting journal entry or you could use some kind of report formatting to group them together as you make your reports that you're going to be providing externally. We're going to be focusing in here. If I go to the amortization table, like we say, if we went to the amortization table, we have it set up so that we can tie out to the balance of the loan at a particular point in time, this being the end of February, that's what the loan balance is as of the end of February. However, there's a short-term portion. We know this particular loan, we make loan payments of about this is rounded 1359 each time. You would think the short-term portion, and remember for accounts payable, the short-term portion means it's going to be something that's going to be paid within the next 12 months, a year's time period. You would think then that the short-term portion would be this if I could just add up the loan payments or if I obviously just pulled out the trustee calculator here, or if I just calculated it right here, if I said that if it was 1359 times 12, then you would think that it would just be simply short-term portion 16308. That however is not the case. That's not correct. Why wouldn't that be correct? Well because part of this payment is going to be including interest. So the interest portion hasn't been incurred yet. If we were to record the interest portion as a liability, that would be similar to us saying, I know I have to pay rent next month and therefore I'm going to put it on the books as a liability right now. We don't put it on the books right now as a liability even though it's pretty much a sure thing that we're going to be paying rents next month because we haven't incurred it. We haven't used the office building in order to incur the expense of paying rent. Same thing is true with these interest portion of the loan. We are going to pay it but we haven't incurred it yet because we haven't used the money over that time period to incur the interest and therefore it wouldn't be right for us to put it on as a liability at this point in time. So I can't do that. We can't do that. What we need to do is take this amortization table and look at just the interest portion or the, I'm sorry, the principal portion. So I need to take 12 payments down of the principal portion. So here's one, two, three, four, five, six, seven, eight, nine, 10, 11, 12. So right there's going to be, I'm going to make this yellow. There's going to be our short term portion. And so notice that's a bit complex. You pretty much have to have an amortization table to be able to figure that out. And so we're going to say, all right, there's the short term portion. If I was to take that and say this is going to be the sum of these items is short term or let's put this up top. Let's put this up top. We'll say this is going to be equal to the sum of these items. That's going to be the short term. And that means that the long term is going to be the balance minus the short term portion. So this would be then, I'm going to say yellow for short term, short term, long term. And obviously this long term portion is where the balance would be after 12 payments. That's going to be equal to this balance. So this is what's on the books right now. We're going to break out the short term portion, which will leave us with the long term or we could think of this the other way. This is on the books right now. We're going to break out the long term portion, which will leave us with the short term portion here, which should be the 13109.  We're going to say, all right, what do we need to do here? I need a long term. I need to break out the long term portion here. So I'm going to break out the long term portion. I'm going to be decreasing this amount with a debit because it's a credit balance account. We'll debit this. The other side is going to go into a long term note payable. So long term liability of some kind. We'll do that with a journal entry. So we're going to say, all right, let's do this with a journal entry. Let's go back on over here. Let's go to the tasks. Now pretty much most of the time you would use journal entries for adjusting, you know, the adjusting journal entries at the end of the period. All the adjusting journal entries will be as of the end of the period. So it's going to be 229 is the adjusting journal entry. And we're going to be reducing this loan balance, which was, well, let's take a look at it. I'm going to select the dropdown. We're looking for the loan here that had the, let's see, is it this one? So let's check it. Let's check it. I'm going to go back on over. It's the one with the 5795. So the 5795, let's check it one more time. This one, that's the one. That one is going to go down. Now it's a credit balance account. So we're going to decrease it. And so I'm going to decrease it by the long term portion. So I'm going to decrease it by the 56770. So 56770, put that here, 56770. And I'm just going to call the description adjusting balance, a DJ balance. And that'll help us to recognize these journal entries that are going to be our adjusting journal entries. Now it needs to be going to the other side. This is going to be some type of long term liability. So we're looking liabilities, but I'm looking down here long term. So here's a long term debt non current. That looks good. Let's put it there. And then we're going to say that's going to be the 56770 as well. There's our transaction. Let's go ahead and post it and see if it does what we expected to do, which is to bring the short term balance down to that short term balance and then record this in the long term balance. So let's do that. And then we're going to say close this. And then I'm going to go back over to the balance sheet to see what happens with it, refresh it. If it doesn't do so automatically, mine is doing it automatically, which is great. And then what's left in the short term portion, 13108, 13108, that of course matches what's in the short term portion on our amortization table, which we looked up, which is nice. And then the long term portion is the 56770, 56770 that then tying out to the long term portion here and what would be left after the next 12, 12 payments. So that's, that's how we would break out the short term and long term. Once again, you may do more formatting as you generate the report to group these two together, which you could do as a journal entry or as part of your formatting of the report when you make reports for the external users. That's going to be it for now. Let's get out of here.


It is Brett and this 2020 GMC Yukon SLT is stock number 13229Z. I'm here at Summit Automotive in Fond du Lac, Wisconsin, your new and used SUV headquarters. This 2020 GMC Yukon has the 5.3 liter V8 gas engine. This GMC has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off and this vehicle is 100% ready to go. I'm going to go all the way around in this video inside underneath. Start it up and take a look under the hood. Satin steel metallic is the color. I shoot all my videos in 4k, so if you have HD capabilities on your computer, tablet, smartphone, or television, I highly recommend turning them on right now because it is your best way to check out the quality, condition options, and cleanliness of the vehicle before seeing it in person. Satin steel, really a cool color. This one is in excellent shape. Driver's side looks really good. And if you like how I do the videos, you can subscribe to my YouTube channel, click the bell notifications, it's youtube.com slash Summit Auto. Then you'll get updates on the videos I do each and every day. It comes with the 22 inch chromed alloy rims and it has Achilles Desert Hawk UHP tires. These are 285-45R-22s and these tires have a really good amount of tread left. I would say probably 60, 70, maybe even 80% of the tread left on those tires. Front fenders in fantastic condition. You get the projector lamp style headlamps, the LED running lights, and the factory fog lights. Front bumper parking sensors. No major dents, dings, scuffs, or scrapes on that front bumper. Chrome trimmed grille. And the hood is in fantastic condition as well. I didn't see any dents or dings on there. Passengers side front fender, really nice shape too. And the passengers side rim, no major scuffs or scrapes. Satin steel metallics got just a little bit of metal flake to it. Really a good looking color. And as you go down this side of this 2020 GMC Yukon, take note of how clean the body is, how reflective, and mirror like that paint is. I take these HD videos, so if you are far away or even if you're close by, just cannot make the trip down. You can still see the vehicle, hear the vehicle, and have confidence in what you're looking at before you even get here. So when you do get here, there's absolutely no surprises. And you can make a smart and informed buying decision from wherever you're at. Back rim is in excellent shape as well. And the back tires have just as much tread as the front tires. Coming around to the back of the vehicle, rear bumpers in pretty nice shape. It does have the backup parking sensors, towing package, receiver hitch, and seven pin wiring. It does have the power lift gate. And that lifts up like so. Back storage area is very clean. It does come with the receiver hitch cover, and that is in nice shape. We keep them inside so they don't go missing. These seats power fold down, and I'm always amazed at how fast they power fold back up. And to get this rear gate down, you press this button right here. It does have the flipper glass that goes up like so. Rear to cross cables are still attached. It's nice to have that. So if you have a boat or trailer hooked up to your vehicle, you can still get to the back without having to unhook the trailer. LED tail lamps going down the driver's side once again, very clean on this rear quarter. And for full disclosure, this back room is in excellent shape as well. Does have the power heated mirrors, blind spot monitoring built in directional signals.  There are no rips. There are no tears on these seats. They are in very nice condition.  I always like showing both sides so that you know that both sides are working properly. And then memory driver's seat and Bose sound. We'll take a quick look at the back seats and then we'll hop inside, check out the miles. Back seats, you get the quad seating in this one. These back seats are heated, latch child safety system, no rips or tears, and the carpeting is very nice and clean. You get rear air controls, 110 volt, 150 watt plug-in, and a 12 volt power point. These seats fold down like so and up like that. Carpeting and back seats are in very nice condition as well. No rips or tears back there. And the headliner is in really nice shape too. Good bottoms of the doors are very clean as well. We'll hop inside, check out the miles, the radio, and everything that this vehicle has to offer. You can see that this one has 28,822 miles. You do get a compass display. Instrument cluster is very nice and clean. You get the heated leather wrapped steering wheel, Bluetooth and information center controls on the right, cruise controls, forward collision warning controls, and heated steering wheel on the left, audio controls in the back of the steering wheel. I believe this one has the six speed automatic transmission with the optional tap shift. And it has the GMC Intel Link radio. You get AM, FM, and Sirius XM radio capabilities. You get a storage cubby behind there with a USB port. And you also have projection manager where you can project your cell phone to the screen via Android Auto or Apple CarPlay. So while this one doesn't have the factory navigation system, project Google Maps or Waze to the screen, it's like you have Navra in the screen, so that's pretty sweet.  You get another 12-volt PowerPoint and two USBs right there. Keyless entry with remote start, passenger side, floor mat, and seat are in excellent condition. No rips or tears on there. And once again, the headliner is in excellent shape and it does have the power sunroof. Map lights, home link buttons for your garage door security systems and lane systems, power sliding sunroof controls, and rear gate controls as well on Starin SOS in the mirror. We'll start it up and take a look under the hood. Now I just want to verify that this thing has the six-speed transmission. So how you do that is you put it down into L and then you hit the tap shift right here. And as far as it goes up, there we go, six-speed automatic. Just wanted to make sure that I was telling you the right thing. We'll take a quick look under the hood. I would personally like to thank you for checking out the video today and hopefully from this HD video you've been able to verify the quality condition options and cleanliness of this Yukon inside and out. You can see it does have the HID headlamps and the LED running lights and they all work very nice. Under the hood we have the 5.3 liter V8 gas engine. Engine base very clean, runs very smooth. Once again this Yukon has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off and this one is 100% ready to go. There is your emissions sticker. And I would highly recommend this Yukon from a quality and condition standpoint and to see more pictures of this Yukon or one of our other 450 new and used cars, trucks, SUVs, minivans, wranglers, you name it. We got to go to that website right there at summitauto.com. Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos you can go to youtube.com slash summitauto. Remember to like, subscribe, and share on this video and all the videos that you see there. Click the bell notifications you'll get updates on the videos I do each and every day here at Summit Automotive. In fact in a second you will see a link to subscribe to my YouTube channel on the upper left. Link to more Yukon videos I've done in the upper right. A link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right. Click those, check this out and we're super excited to help you with this Ultra Clean 2020 GMC Yukon SLT in satin steel metal. Thanks again for checking out the video. Remember to like, subscribe, and share on my YouTube channel. I really appreciate it. Thanks again.


Everyone, welcome back to theCUBE's coverage of KubeCon, CloudNativeCon 2021. We're here in person at a real event. I'm John Furrier, host of theCUBE, with Dave Nicholson, my co, has got great guests here. Two founders of brand new startup, one week old, Kim Lonowski and Dave Lawrence, with ChainGuard, former Google employees, open source community members, decided to start a company with five other people. Five total. Five total, congratulations. Welcome to theCUBE. Thank you, thank you for having us. So, tell us about your product now, you know what I'm trying to tell you. We know you don't have a product, so take us through the story, because this is one of those rare moments. We got great chance to chat with you guys just a week into the new formed company and the team. What's the focus? What's the vision? How far back do you want to go with this story? Go into why you left Google. So, you know, we're at Gin and Tonics, a couple beers. I can do that, we can do that. Let's take over the world. Sure. Yeah, so we've both been at Google for a while. The last couple of years we've been really worried about and focused on open source security risk and supply chain security in general and software. It's been a really interesting time as you probably noticed to be in that space, but it wasn't that interesting two years ago or even a year and a half ago. So, we were doing a bunch of this work at Google in the open source. Nobody really understood it, people kind of looked at us funny at talks and conferences. And then, beginning of this year, a bunch of attacks started happening. Things in the headlines like solar winds, the solar winds attack, like you say, an attack, all these different ransomware things happening. Companies and governments are getting hit with supply chain attacks. So, overnight people kind of started caring and being really worried about the stuff that we've been doing for a while. So, it was a pretty cool thing to be a part of and it seemed like a good time to start a company. Kim, your reaction to the startup, how do you honestly feel? I'm just feeling so excited. Yeah, I'm really excited. I was in Stars before Google, so then I went to Google, we were there for, I guess, Dan a little bit longer, I was there for seven years on the product side. And then, yeah, we, the open source stuff, we were really there for protecting Google and we both came from cloud before that, working on enterprise products. So, then sort of just saw the opportunity, while these companies trying to scramble and sort of figure out how to better secure them. So, it seemed like a perfect start up. The startup bug and you back in the startup, but it's a timing's perfect. I got to say, this is a big conversation supply chain from whether it's components and software now, huge attack vector. People are taking advantage of it. Super important, so I'm really glad you're doing it. But first, explain to the folks watching what is supply chain software? What's the challenge? What is the supply chain security challenge or problem? Sure, yeah, it's the metaphor of software supply chain. It's just like physical supply chain, that's where the name came from. And it really comes down to how the code gets from your team's keyboard, your team's fingers on those keyboards into your production environment. And that's just the first level of it, because nobody writes all of the code they use themselves. We're here at CloudNativeCon. It's hundreds of open source vendors, hundreds of open source libraries that people are reusing. So your trust radius and your attack radius extends to not just your own companies, your own developers, but to everyone at this conference and then everyone that they rely on all the way out. It's quite terrifying. It's a surface area, as they would say.  The surface area explodes pretty quickly. And people are, and the targeting too, because everyone's touching the code, it's open. There's a lot of action going on. How do you solve the problem? What is the approach? What's the mindset? What's the vision on the problem's solution? Yeah, it's a great question.  Like Dan's been laughing.  Now he's a rock star. Hey, we need you. Why don't you tell them? I was telling them for five years. Yeah, yeah, yeah. But I think one of his, you know, go-to lines was like, would you pick up a thumb drive off the side of the street and plug it into your computer? Probably not. But when you download, you know, an open source package or something, that actually can give you more privileges in production environments. And so it's pretty scary. So I think, you know, for the last few years, we've been working on a number of open source projects in this space. And so I think that's where we're gonna start is we're gonna look at those and try to grow out the community. And we're watching companies, even like SolarWinds, trying to piece these parts together and really come up with a better solution for themselves. Are there existing community initiatives or open source efforts that are underway that you plan to participate in? Or are you thinking of charting a new path? What's that look like? Tons, yeah. The SIG Store project, we kicked off back in March. You've covered that or familiar with that at all. We kicked that off back in March of 2021, kind of officially. We had been working on code for a while before then. The idea there is to kind of do what Let's Encrypt did for browsers and web security, but for code signing and open source security. So we've always been able to get code signing certificates, but nobody's really using them because they're expensive, they're complicated. Just like Let's Encrypt did for CAs. They made a free one that was automated and easy to use for developers. And now people do it without thinking about it. In SIG Store, we try to do the same thing for open source. And just because of the headlines that were happening and all of the attacks, the momentum has just been incredible. Is it a problem that people just have to just get on board with a certain platform or tool or people have too many tools, they abandon them, their focus shifts. Why, what's the main problem right now? Well, I think part of the problem is just having the tools easy enough for developers are going to want to use them and it's not going to get in our way. I think that's going to be a core piece of our company is really nailing down the developer experience and these toolings and the co-sign part of SIG Store that he was explaining. It's literally one command line to sign a package, sign a container, and then one line to verify it on the other side. And then these organizations can put together sort of policies around who they trust in their system. Like today it's completely black box. They have no idea what they're running and yeah. You have to re-think and redo everything pretty much. If they want to do it right, if they're just kind of fixing the old Europe's next solar with basically. Yeah. And that's why we're here at CloudNativeCon when people are, you know, the timing is perfect because people are already re-thinking how their software gets built as they move it into containers and as they move it into Kubernetes. So it's a perfect opportunity to not just shift to Kubernetes but to fix the way you build software from the start. What would you say is the most prevalent change, mindset change of developers now? If you had to kind of look at it and say, okay current state of the art mindset of a developer versus say a few years ago, is it just that they're doing things modally with more people? Or is it more new approaches? Is there a pattern? I think it's just paying attention to your building release process and taking it seriously. This has been a theme since I've been in software but you have these very fancy production data centers with physical security and all these levels of trust and prevention and making sure you can't get in there. But then you've got a Jenkins machine that's three years old under somebody's desk building the code that goes into there. He gets social engineer, he gets tag. Exactly, yeah. It's like the movies where they, instead of breaking into jail, they hide in the food delivery truck. It's that, that's the metaphor that I like perfectly. Defense doesn't work if you're just opening- The cleaning truck. Yeah, if you open the door once a week, it doesn't matter how big defense is. Yeah, that's good to know, that's funny. And I think too, like when I used to be an engineer before I joined Google, just like how easy it is to bring in a third party package or something. You need like an image editing software, like just go find one off the internet. And I think developers are slowly doing a mind ship there. Like, hey, if I introduce a new dependency, you know, there's going to be, I'm going to have to maintain this thing and understand it. It's a little bit of a decentralized view too. Also you got a little bit of that, hey, if you sign it, you own it, if it tracks back to you, okay, you are your fingerprinter if you will or on. The chain of custody. Chain of custody. Exactly, I was going to say, when I saw chain guarded first, of course I thought about my pant leg, riding a bike, but then of course the supply chain, things coming in, like on a conveyor belt, conveyor belt, but that whole question of chain of custody, it isn't as simple as a process where someone grabs some code, embeds it in what's going on, pushes it out somewhere else. That's not the final step typically. So. Somebody else grabs that one and does it again in 35 more times. Right, so who's responsible on that? How do you verify that? It seems like an obvious issue that needs to be addressed, and yet apparently from what you're telling us for quite a while, people thought you were a little bit nutty. And it's not just me, I mean, so Ken Thompson of Bell Labs, and he wrote the book. He wrote the book that I grew up on. In the 80s he gave a famous lecture called Reflections on Trusting Trust, where he pranked all of his colleagues at Bell Labs by putting a back door in a compiler, and that put back doors into every program it compiled. And he was so clever, he even put it in, he made that compiler put a back door into the disassembler to hide the back door and his colleagues looked for it. He was a genius. Yeah, so he spent weeks, and people just kind of gave up, and I think at that point, they were just like, wow, we can't trust any software ever and just forgot about it and kept going on and living their lives. So this is a 40 year old problem, and we only care about it now. That's totally true. A lot of these old, sacred cows saw it in life cycles, not really relevant anymore because the workflows are changing, it's complete, DevOps has taken over. Let's just admit it, right? So DevOps has taken over, now cloud native apps are hitting the scene. This is where I think there's a structural industry change, not just the community. So with that in mind, how do you guys vector into that in terms of market entry? What's just thinking around product? Obviously, you got a higher. Yeah, I got a higher. Did you guys raise some capital? In process. A little bit of a capital A, so there's probably no problem with hot market.  Yeah, I mean, we're casting a wide net right now and talking to as many customers, like we've met a lot of these customer, potential customers through the communities that we've been building, and we did a supply chain security con helped with that event this Monday, negative one event, and SolarWinds and Citibank were there and talking about their solutions. And so I think, and then we'll narrow it down to people that would make good partners to work with and figure out how they think they're solving the problem today and really sit closer to them. How do you guys feel? Good? You feel good? Excited. Well, we've got Jerry Chen coming on from Greylock next. Oh, awesome. So if you hang around, you can get a term sheet and say, Jerry, these guys got some action on them. Get in there. I probably didn't reply to him on LinkedIn or something. He's coming out with Chronosphere. He just invested $200 million in Chronosphere. Awesome. You guys should have a great time. Congratulations on the leap. I know it's comfortable to be in Google. A lot of things that work on and it's doing startups are super fun too, but not easy. Not for the female. You guys done it before, so great. Roller coaster. Cool. What do you think about today? Did the event here a little bit smaller, more like a VIP event? What's your take on playing on this?  Obviously, we're meeting, we've been associating with folks over Zoom and Google Meets for a while now and meeting them in person is like, oh, hey. Hard to recognize behind the mask. But yeah, we're just glad to sort of be back out and a little bit of normalish, I guess. How's everything in Austin? Everyone's safe and good over there? It's been pretty good. Yeah, it's been a long, long pandemic. Lots of ups and downs, but yeah. Dan's hair has an identity. You got to get the music scene back. Once the music comes back in Austin, everything's all back to normal. Yeah, my hair doesn't normally look like this. I just haven't gotten a haircut since this all started. That's good, you're going to do well on this, Mark. You're going to turn a sheet like that, keep the haircut, until you get the money. I think I saw your LinkedIn profile and I was wondering, it's like, which version are we going to get to? Yeah, we'll see. Wow, super relevant, super great topic. Congratulations. Thanks for coming on and sharing the story here on theCUBE. Yeah, thanks for having us. Thanks for having us. Thanks for being here. Dave Nicholson here on theCUBE. Day one of three days. We're back in person. Of course, hybrid event because theCUBE.net for all more footage and highlights and remote interviews. So stay tuned, more coverage after this short break.