Plain film x-rays, so you can do it with your bone, but my shell is really soft tissue, other problems, not very useful. Erty generation CT scans, one of the first generation CT scans, sort of getting better than plain film x-rays, but still not great for blood and for cranial processes or interorbital ulcers. It's a sound where you kind of fill the gap, you have here on this, you know, is that just to be on the top. Not on the mouse. Not on the mouse. You've gone off, make sure you're ready for that start. Okay, thank you. Anyway, so then these came along, of course, CTs, MRIs, incredible definition of soft tissue, certainly in the orbit, intercranially, even the globe, could show some things in the eye, so that was a big step forward. So the question kind of arose, who needs ultrasound? We have that kind of technology, but there's still a role for it, there's a kind of initiative filled, certainly in the globe, I think it's still superior. You can see detail here, mine otherwise, strutting with high frequency, get the UBMs really down to a very micron level, but even in the orbit, there's still a role for ultrasound, and the A-scan, all these spooky lines, they actually mean something. There's a correlation to pathology. I was doing my residency, I was repressed that you could actually sort of look at cell structure, architecture, and make a correlation of these lines. So a normal orbit would be like that, and then hemangioma, lymphoma, and angiomas, you almost get like tissue signatures based on pathology, so it really kind of makes you think and sort of what you're looking at, and so that's still an advantage to using ultrasound. And of course, the side of the globe, things like detach retinas or melanomas, things like that, still a lot of usefulness. So basic principles, sound reflection from interfaces, just like lights reflected, so a sound, a lot of the same principles, snows, a lot of things like those are followed by ultrasound reflections. So a long time ago, Bass discovered the same concept in the Wells, they use it in nature all the time. That's incredible, they all of a sudden can't see, there's a species that can, but they use sound to locate insects and little tiny gnats and things they can pick up middle of the night just by ultrasound. So it's a powerful technique to localize. And then again in nature, the animal kingdom, humans are a range of herrings up to about 20 kilohertz, and that's ultrasounds defined as sound above that range. So board question, if you have that on the boards, that's the definition of ultrasound. So dogs can do up to about 40 kilohertz, Wellesdorf in 70, Bass 150, so they have ability beyond our range of herring to hear things, and then again to use that to to localize. And medical ultrasound, abdominal ultrasound, commonly their frequencies are lower, because the higher their frequency, the less penetration. So there's an inverse correlation. So in the abdomen you want to get deeper into the abdomen, you want to see kidneys and livers and things. So you want to be able to go in great deeper. So you want to keep your frequency around the one to five megahertz range. At the albumic, we have the advantage of having a small structure of the eye, about an inch. And then we have a lot of fluids, so ultrasound, built through fluid easily. So you can get high frequencies of 60 megahertz of some of the high frequency ultrasounds to localize things. So it really gives us better resolution. Soundwave velocities, so the denser the media, the faster the ultrasound velocity. Water is about 1480 aqueous vitreous 1532. That's kind of a standard setting for most biometers, the ultrasound biometers that are set to that kind of average. So to really refine a lot of people who use the break it down, they'll look at the break it down for the aqueous, vitreous, and the lens and add it to those things together in a formula to actually give the true distance, you know, the actual length of the eye. But if you use a standard biometer, that's kind of your average setting for the biometer. Okay, so principle is going to sound reflection. So the B-scan, those stands for brightness amplitude. So basically you're just taking little pixels and coalescing them to make a picture. Same concept as a TV screen. You're just adding reflections to this picture. The A-scan is really the same thing as the B-scan. It's just instead of a pixel or a brightness, grayscale, it's actually a line. So it's just showing a line versus a dot. What's the advantage of that? I'll try to explain that to you. The UBMs down for ultrasound biomicroscopy, which is high frequency answer segment, usually requires an immersion technique to see that. So this is the one formula I'll throw at you. Acoustic competence equals sound velocity times density. So that's just a basic formula of physics. And in ultrasound, we depend on interfaces. So the greater the difference in impedance between two media, the higher the A-scan spike or the brighter the B-scan image. So when a sound way of goes from one media to another, that principle applies. Your reflection, your interface reflection depends on that. So to illustrate that, this is a Corotal Homanjeoma. As you can see the pathology there of the Coroid. And these tend to be a lot of interfaces. So compared to like the Vitria, so you're going through the Vitria's cabinet here. So the flatness on the A-scan, of course, the darkness on the B-scan. So there just isn't much there to reflect sound. Usually Vitria's just pretty homogeneous. So you don't get much reflection. So it's a flat line on the A-scan. Once you get an interface, again, this impedance principle, then you suddenly get a reflection of sound.  And even once you're inside the tumor, there's still a lot of reflection, because you get a lot of interfaces. So some tumors are very homogeneous, very dense like melanomas. They don't give these high reflections, whereas Homanjeoma's do. So that principle, again, starts to help you sort out pathology. You can correlate that concept to what a legion is, both in the glow or in the orbit. So the B-scan, again, is a brightness concept. So brightness on the B-scan corresponds to height on the A-scan. So the brighter the B-scan image, the higher the A-scan. But there's a limit to this. Grayscale, the start ability to perceive grayscale, differentiated, it was limited. So B-scan legions often look a lot the same. They might be a little bit brighter or darker based on the tumor. But A-scan really kind of shows it to you, just sort of makes it stand out. It's more dramatic, more observable. So the B-scan probes, all the probes have a mark on them of some kind. There's a little mark on the tip of the probe. And that correlates to the transducer, which way it's going back and forth. So as I teach you guys a little for sound, I always stress about transverse longitudinal, which way the thing is going. And there's a reason for that. It actually helps you orient things. When you're looking at tumors and things to measure them, that's an important concept to have. So actually this is taking the tip off the B-scan probe and showing the transducer. So it's actually going back and forth. It's a two plane motion. It's a transverse back and forth that doesn't rotate at all. So this is going back and forth in that plane. So wherever the probe is turned, let's assume the marks over here, that shows you which way the transducer is moving back and forth, oscillating back and forth. And that translates to where you're looking at inside the lesion. So this transducer actually contains a little real thin crystal. It used to be kind of a membrane in the house. Like a ceramic crystal, very, very thin. And that little membrane crystal will vibrate based on electronic pulses. So the machine sends out electrical pulses, they stimulate that to vibrate, and that sends the sound way down. So that's the basis of the ultrasound technology. It's actually a generation of sound by electrical pulses. So techniques, I talked about transverse longitudinal. That's important when you're doing the B-scan to be systematic. Most of it is just a client just put the probe up there and you know, swap it on. I see something, you're all excited, but you can miss things that way.  I probably, I have a number of cases I picked up. The other eye, it's a normal eye that the patient didn't come in for, had us the pathology. I picked up several melanomas that were the other eye versus the eye that they came in for. So just always not just look at both and do systematic exams. Look at the whole eye. You'll miss things if you just focus on one element of it. So again, the concepts, the markers here, that means the transducer is going back and forth, kind of out of the plane of the slide here. It's going to be towards us, back into the slide. So that's the transverse view. And as that beam is oscillating back and forth, that is showing a lateral extend of the lesion. So if you had a lesion here, you're kind of going lateral, examining it. If you turn the probe this way, where the marker is up, the transducer isn't going like that. So this is a parallel for the limbis. We define it as a transverse view. So when the transducer is moving parallel to the limbis, that is called transverse. When you're longitudinal, like that, perpendicular to it, that's called longitudinal. And that show is answered opposed to your extended lesion. So the beam is actually going this way. It's going from the optic nerve up to the aura in that direction. So each sweep of the B-scan probe is about 60 degrees. So if you want to scan the whole globe, that requires six different sections. You get 360. So anyway, so that concept of a transverse, longitudinal, this is an axial where you're actually putting it right on the cornea going back right to the back of the eye. So those are the three basic probe positions over the years. So an axial scan, you can see the probe is up here. You can sort of see a little bit of made the posterior lens capsule. You miss most of the entire segment because physics of the probe, the way it works, you lose information up in here because you're touching the globe. And you go to the lens here, an optic nerve shadow, kind of the shadow in the back, that's the optic nerve. So you could use that for a view. The problem with the axial view is I don't use it a lot because first of all, patients don't like on the cornea. I hear I was kind of worried about conglomerations and things. And then also you lose energy, sound energy. As you go into the lens, it absorbs some of the sound energy. So you don't see as well, the resolution is not as good. So we often don't use axial views unless there's something right in the medium to back of the eye. So we often use just off the Olympus to see things. So again, the transverse v-scan versus longitudinal. So again, transverse is going this way. The transducer is going to take you back and forth out of the plane of the slide. And this is going perpendicular or longitudinal. And we can characterize reasons that way. This is the lesion or lump in the eye here as you want to examine it. So this is what kind of a transverse scan here. So we're kind of looking here at the lateral extension of the lesion so we can measure that. So when you see the lesion, the marker on the probe tells you on the screen which way is up. So it's always the way the equipment is made. It displays the image with the where the white mark is that is up on the screen. So this would be the superior part of the lesion. This would be the inferior part. And longitudinal, again, you're going this way. You're going perpendicular to the Olympus, back and forth that way. So you see the lesion there, kind of the anterior postural extension of the lesion versus lateral. So there's the optic nerve, there's the lesion. So this is the lesion here, nasally. So what kind of view is that, the way the probe is oriented there? There are transverses, longitudinal. This is a transverse view because you're parallel to the Olympus. Think about the transverses are moving. Olympus is here, so you're moving that way and so you're parallel to the Olympus, which would be a transverse view. So that lesion is seen that way. Rotate the probe this way, where you're going perpendicular. Okay, does that make sense? So it's perpendicular here. That's just going that way. So that shows the lesion of those views. So putting these all together, you have to kind of mentally construct this. You can actually see the lesion. You can see both the lateral extension and that's your posterior. That's important because when we measure these lesions, it's very common now to treat melanomas with radioactive plaques. So you actually make a plaque, radioactive iodine. So up to the eye on the sclera, leave it there for three days, then take it off. So you need to know how to make the plaque. So you have to have these measurements and I see patient referred by an ocular oncologist. I need to tell them the lateral and anterior posterior extension. So those are really important measurements. Then we follow lesions, either before we treat them or after they've been treated just to follow see if they're responded. Again, you need to be consistent, reproducible, systematic. So these are all important to do that. So it's just good to think that way and kind of think systematically. That's the e-scan concept. The e-scan, the transducer in the e-scan is not sweeping back and forth. It's a fixed beam. It's just a sound beam that comes out. So you don't have to worry about pro-position that there's no mark on the e-scan wherever you put it. The beam is the same. It just comes out of the probe as a comb. So the e-scan is placed on the globe. You get the initial spike from the surface of the eye. So again this area is kind of an area of lost information. Whatever is in there you really can't see because of the physics of the probe. Velocity of sound coming back and the crystal stimulation. That area is about three to five millimeters. So your anterior sclera, anterior vitreous, that's all in there somewhere. Don't really know what it is. The same on the e-scan. You go through the vitreous, again it's mostly homogeneous. So the beam goes through. You don't get much reflection of sound because it's homogeneous. And then you hit the surface of the tumor. Concept changing. Velocity. So then you get a spike. And once you're inside the tumor, melanomas tend to be rather homogeneous. They're intensely cellular. You don't get as many interfaces as you do with other lesions. So that's important. That kind of distinguishes melanoma from other things. That reflectivity. So it's kind of on the low to medium side. It's kind of regular. The lups and downs, but it's not huge difference in variance there. Again, so based on pathology, if you look at the pathology of the melanoma, that kind of makes sense. Why you see that pattern. Then you get the sclera and get another change in sound velocity. You get a spike in the sclera. And back in the orbit, the orbit has a lot of interfaces. You have fats, septic muscles, nerves. So the orbit is a high reflective versus a vitreous, which is low reflective. G keys is a coroid on that. On the coroid? Yeah. You can actually, if you look at the, turn the frequency, the gain down a little bit, you can actually separate out the coroid from the rep. But it's not as accurate as OCT. So I actually use this picture to kind of, that's a good pathology now. Because we do these OCT switch for you, so you're like macro CT. This is kind of the B scan. You're looking kind of closely, you're looking at the back of the eye of the poster segment with the B scan, just envision the B scan signal showing the retina surface. You're looking here with immaculate. This is the A scan. So the A scan and ultrasound, actually you take a section through that, you know, as you move this green line, the cursor, as you sweep it through the parts. It actually shows you those sections. That's what the A scan is doing. It's actually the B scan is showing the kind of a big image. The A scan is taking like a cross section through them, kind of like a needle biopsy versus a gross pass specimen. Does that kind of make sense? So they do complement each other. I use them a lot. I use, most patients I see, I use both. So again, here's melanoma, the pathology. Very densely cellular. Just a lot of cells packed together. There's a few blood vessels. So you get a few reflections from that. But usually they're pretty low. So here's going to the vitreous. Here's a spike of the tumor. Here's inside the lesion. Here's a splara. Here's the orbit. So you can see again that there's just a lot of dense cells packed together. So some interfaces, but not real high, not real irregular. The B scan shows the brightness. This is subrubinal fluid. The retina is being pushed off here. But here's the lesion. But again, you know, to look at this, that could be a lot of things. That could be a manjoma. That could be metastatic. So the B scan is really, it shows you there's a lesion there. It shows you kind of the general size and shape. So kind of morphology. But you're really defined of the A scan. It's a needle biopsy concept. You're going through the lesion, looking inside. What does the stretcher look like? Back of Horlase to pathology. So that was the neat thing about ultrasound. The first kind of attracted me to it. So the A scan probe has kind of this pencil-like probe. And again, there's not a transducer going back and forth. There's just a beam coming out. And there's some confusion about this.  They kind of equate A scan to biometry. If you look at a biometry probe on the ultrasound machine, it kind of looks like that. Like we go to use a VA's machine all the time. The techs will hook up the A scan. I have to kind of switch probes, because the A scan probe, because of biometry, is not the same as we used for diagnostic A scan. They're not interchangeable. Like I can use this to do biometry. I can't use the biometry probe to do kind of sort of what I do with tumors and things. So that's a sort of confusion. Even a reps, a cell machine will just tell you, that's the same thing. And a lot of machines on the B scan image, they have a little thing you can turn and see a little A scan pattern at the bottom. Like the vector A scan is just, there's a line you can sweep through and see the lesion. And you'll see the A scan at the bottom. That isn't a true A scan. That's just kind of taken from the B scan envelope. And I just sort of use that information to make sort of an A scan out of the B scan information. But it's not a free standing separate A scan. So we're going to do an A scan accurately. You need to have a separate dedicated probe with a separate module on the machine. So returning that, because it's going to just lifelike, these are all things that light does and ultrasound does too. So sound is absorbed by things. I mentioned the actual view with the lens of serving sound, reflection, how you hold the probe, angle of incidence, Nels law, interfaces, size, shape, smoothness. These all affect the image that you see on the ultrasound. An example here of a little tumor. So here's going through the vitreous. Here's a lesion here with the first arrow, the second arrow. So you're inside the lesion. It's kind of small, small relations are harder to distinguish. It's probably a small melanoma because it's kind of low reflective that it could be something else. But anyway, the point of this is to show you, I'm perpendicular here, you get a nice high rising spike. I always stress out when you guys are doing ultrasound with me with A scan, I'm going to get this an ocean spike, high rising. You don't want to get kind of bumpy your off axis. This is the same lesion just by turning the probe purposefully, obliquely. I'm not perpendicular here. I'm oblique to it. But you see that by doing that, you don't get that nice high spike at the first and internal reflectivity is less distinguishable. It looks kind of maybe medium to low here. Here is sort of based on the initial spike is probably higher or irregular. So that bleakness just kind of clouds the internal information. So that's why being perpendicular is important. And people that do axial length measurements, the techs that do that always know you got to be perpendicular to really correct axial length measurements. So it's important to give and you know you're perpendicular based on the initial spike. If it's very high, it was smooth, and a lot of bumps in it. And I concept as you do, and you're watching the screen with your hand back before trying to maximize that initial signal. So indications for ultrasound glow, opaque media, obviously very important, dense cataract, lot of corny vitro sandwich. These are all things that we do all the time to use ultrasound for visible fundus lesions. You can see the lesion, but what is it? You know, we think we're good at it, but even the experts, the Shields group, we're saying inaccurate diagnosis of lesions based on a lot of past studies. So just looking at a lesion and direct ophthalmoscopy as good as it is, a lot of time we're fooled by how lesions look. Biametry, axial length, even though we have IOL master, we have the you know the light-paced measurements. About 20% of the time they still need to use ultrasound. The techs all the time have to go to a version ultrasound to see through dense cataracts, so dense, mature cataracts, PSE cataracts. A lot of things can give spurious measurements on the IOL master. So major necks of length, intraocular structures, majoring, high tumor high, things like that. That's critical. I do a lot of that. A lot of the patients I see are referred from the local groups here that do ocular oncology, and I'm majoring all the time. I'm majoring before treatment, I'm majoring after. So a lot of what I do is based on accurate measurements, and the A-stand is really more important. We draw in the pathology, I'll pick just a male. These are kind of major indications for ultrasound. So fake media, looking behind through dense cataracts. I think it's standard to care, and it's almost malpractice. If you do a cataract surgery without an ultrasound before, just to see what's going on inside the eye. And I've seen a number of cases that things are missed, including tumors. It's not a good idea to do surgery on an eye with a tumor in it. There's always a concern about spread. So what do you think it's important to do an ultrasound? Biometry doesn't count. You can do biometry and measure the eye. If you have a big tumor sitting there, you don't see it with biometry. So you got either dedicated A or B-stand or both. I just looked at a study of my own practice. I looked at a thousand patients over a couple of years, and I just found this. At the clinical impression, a patient referred to me for a diagnosis with a say that they said, there's a vitreous hemorrhage, or there's a detachment. I confirmed that in 400 of them. So clinical diagnosis was confirmed. I couldn't find anything in about 279. So a patient said for eye pain, common reason, my eye hurts, aches, you know, I can do the ultrasound, you don't find much going on to explain it. Clinical impression clarified or altered in about a third. So this meant that they were sent in for something like a vitreous hemorrhage and I found a detached retina under the hemorrhage or a tumor or something. So I changed the diagnosis or I added to it. Correct diagnosis in five. So this is kind of just an overview of an ultrasound practice where I see a thousand patients and kind of breaks down. So the value of it is, again, a third of these patients, refining things that the doctor didn't know was there to start with. So that's pretty important. And again, with the patients with opaque media, for a methodology not suspected by the referring doctor. Okay, visible fundus lesions, again, we're not that great. You can sort of tell sometimes looking at a lesion what you think it is. But two large past studies, AFIP, Armed Forces Institute of Pathology back in the six years and seven days, two different separate studies looked at this. And those days, nucleation was very common for eyes with tumors that was kind of standard to cure. You saw a tumor in the eye and often they're nucleated within a week or so. Radiation plaques weren't really being used yet or anything. So a new patient was pretty common. So a lot of eyes were sent to the pathology people. By looking at all these eyes, they found that 20% of the eyes had false positive diagnosis of melanoma. So that means 20% of eyes were taken out that didn't have to be there by nine lesions, often 20, 20 eyes or so. So that's not great figures. And so if you look at a lesion, it's hard to tell sometimes. This, in fact, was a nebis of some melanoma, just to look, just the criteria we go by. Sometimes it's not that obvious by looking at them. Biometry actually lengths, I mentioned that. So we use immersion techniques to do the biometry. We have to do that to be able to see the front structures of the eye. So if you put the floor right against the cornea, give it as information, you would have the cornea buried in there. You'd have the anterior chamber of the anterior lens. So you wouldn't be able to see that, be able to stand the probe back. You have to use some kind of a look at interface to put the probe in. And you get the spike from the probe itself. You get the, going through the, the splitle shell here. Then you get the cornea right there, anterior chamber, lens, anterior postural lens, vitreous and retina. So you can actually break it down and you can then use that to measure, electronic calipers to measure, breath to back of eye. And again, about 20% of the cases here, the techs tell me, they have to end up doing immersion ultrasound. As you're in doctor structures, I mentioned this following tumor for growth. So here's a little small melanoma. So here is a lesion. About a year later, it looked kind of the same on B-scan. Had already seemed to change a lot. But the A-scan, the actual thickness of it had changed slightly. But a big difference was reflectivity patterns. Here it is initially kind of high, probably like a nebis. It's getting lower here. It's getting lower reflectivity, more regular. That's conversion from the nebis to melanoma. I see this a number of times. You follow a lesion. That's what we do ultrasound on nevi, because some of these will start to change. You want to get baseline measurements, then follow over time and see if it's changing. Again, side wasn't all that much different, but reflectivity internally was. So that really clued us. This was starting to convert. Any ideas of the conversion rate of nevi to melanoma? So nevi and the population, rough guess how many people have nevi? Five percent higher. The numbers are kind of varied. It used to be six percent. Now kind of the current literature says about eight. So in this group, probably somebody had the nevus in there with you guys. So about eight percent, you do? Rachel likes pointy too. Anyway, so about eight percent of have nevi and at that group, rough guess how many can burn to melanomas over time? One. About one in 10,000. So what's that, point zero zero zero one? So it's pretty pretty unlikely, but it can happen. So again, that's what we follow, but the odds of that are not very high, but still it can happen. So vitro retinopathology, very important for vitro tumors you can't see inside the eye. So the classic kind of optic octave disc with a high reflective membrane of the optic disc, that's consistent with the tetra retina. You always suspect that vitro's membrane sometimes will do that, so it's not a hundred percent. But the ACE scan is helpful in these cases if you're not quite sure. You see a membrane on B scan, you can do the A scan and you look for a high spike, smooth reflection. That's pretty suggestive of the tetra retina. If it doesn't get that high, if it's just kind of down here somewhere, more likely a vitro's membrane. So I use that a lot in these kind of hard cases. You're not quite sure if it's a vitro's membrane versus a tetra retina. I'll show some videos. These are little video clips of just showing some motions and kinetics. So I'll show that. I got a separate little video clip I'll show you. This is showing just the motion of different membranes inside the eye. So this is a case, there's a small tumor here, don't worry about that, it's more, I'm trying to show the motion. This is the vitro's membrane over here. So when you see the kinetics of the vitro, you see a lot of fluidity. It's kind of just flowing as the eye moves, that's consistent with hemorrhage. This is another tumor, look over that as a membrane. This is a detached retina. There's kind of a stiff motion as the eye moves. It's sort of just stiff. It's not a real fluid, underlating kind of motion. Other one, this is a small tumor, but this again is the retina over a very stiff motion compared to vitreous, a lot of fluidity. So I'll show that in a minute here. And this is the same thing again here. So kinetics are important, showing how motion is. I watch, I do that a lot when I do the V scan especially. It's just to see how things move and that kind of helps sort out membrane versus other things. Yes, see a lot of these. You know, you have the patient with a funny looking disc. Two ways to go. They're here with the essential neurologist and they get MRI, CT, spinal tap, angiogram, everything you think of. $25,000 workout versus doing ultrasound a couple hundred bucks, two minutes. You see this, the optic disc bruising, very common. It can be deceiving. Sometimes the neurologist kind of scratch your head as I look. This is the case here, showing this disc, funny looking disc. This is pretty suggestive of bruising. You'd be looking at this very carefully with a 90 diopter. You can see kind of bumpy, lumpy, kind of glistening areas. So that you would think bruising in that situation, which is verified on the ultrasound that it was. But here's not so obvious. That's pretty scary looking. It's not like papillodema. You saw that kind of, you know, some vascular congestion, kind of very prone to optic disc. But yeah, this is a large, very bruising.  So optic disc bruising, any guesses on the frequency of these? How many people in the population have optic disc bruising? Tim? Okay. The lower? Three. Yeah, two to three. That's sort of based on past studies. So genetics of it, genetically inherited trait, recessive, dominant. It's excellent. Probably dominant with mixed penetrance. So we've done some genetic study. We used to haul our group out to family reunions, Dr. Katz and I, and take our ultrasound blood and have potato salad with the cousins and the uncles and the aunts. Take everybody we found. Usually in a family, if you find somebody with it, there's a pretty good chance of finding somebody somewhere that has it, not always parents or direct relatives, but an uncle or a cousin, somebody has it. So we haven't found the gene yet. We're still looking for it. Just like Niko's looking. I guess you're looking for your gene?  Maybe that was? No, that's right. That's right. We're doing the same thing to gene hunters. I think we found a family a month ago. It's a mother and both kids have it. That's got to be a genius. I'm glad about it and we're going to look for it. So this is a case of wasn't gruesome. This had kind of a swollen look and nerve. And then here's the ultrasound showing the kind of the elevation, but there wasn't a brightness like that. Bright lump, you see, like a calcified gruesome. Here's the ace can to be helpful. I usually do ace can to most of these patients just to see, but here's the object nerve from there to there. So that's the one sheath. That's one sheath. And here, if you do what's called a 30 degree test, you imagine the patient looking straight ahead, you have an abduct the eye 30 degrees. And the theory is that you abduct the eye, you sort of squish the nerve, you sort of stretch it and then first fluid sort of push the fluid back. So the nerve thins. So the concept is you get a thinner nerve by doing this test. That's called the 30 degree test. So looking straight ahead, here was the nerve 30 degree test. Here you can see it's thinner reduced to about 50%. That's a positive test. So if I see that, that means there's fluid around the nerve, increased optic-nurse fluid, which goes along with increased intranagranial pressure. So a pseudo tumor cerebrale, things like that. Whereas a solid lesion, like a lioma, an angioma, would not do that. The nerve would not thin as you as you move it. It would be just a solid lesion. So the nerve is stayed the same. So it kind of differentiates fluid around the nerve versus my consumer of the nerve. So that's an important test to know about. Case here, this is a central red artery occlusion to the cherry red spot. It's kind of called box cornering. You actually watch the pumping of blood vessels inside the artery. You ever seen that anybody? You ever seen central red artery occlusion with box cornering? Okay. And the fluorescence shows that you see this kind of clumps of red cells as they kind of pump along because they're just stagnant moving. This is a patient that we saw, like a late Friday night gentleman that had sudden loss of vision. And so again, I mentioned this, I think it might talk, ran as it said. You can see kind of a brightness here. That's actually an embolus. So you can actually, about a third of these patients with central artery occlusions, you can find an embolus on the B scan. So it's easy to do.  The nerve takes 10 seconds. If you see that, you know it's symbolic. That's important. You get a older patient, sudden loss of vision. That could be castle arthritis. So how do you know the difference? So this can help you along with Mike and I study on another way to look at it. This is a drool. It shows the drools and they're different. They're more anterior. They're anterior. It's the lamina crevosa, whereas emboli are posterior to it. So it's further back. So it's not the same as a drool. But if you see that, you know it's symbolic. You got your job is to find the source of the emboli, but it really helps. You know that Friday night special where you don't know what's going on, the redirection of what to do. This patient had to blockage the crevosa with emboli coming up to the central artery. This is a robot called the Doppler, which I use some. Again, we're doing the study with temporary arteries with Mike and I. This is a machine. We don't have one here, but we have one in the vascular lab. You kind of borrow theirs and push it back and forth. The Doppler concept is based on movement. So it's so ultrasound, but it's a moving thing. So as the thing moves, it changes its frequency. You ever sit on a train track and heard the train coming towards you and hear the whistle and as it goes away, it just changes pitch or changes frequency. So that's the Doppler concept. Used in space to help with the whole concept of galaxies, big bang, receding promise of blue shift versus red shift. So you can use it for different things, blood flow to the globe, emboli detection, as I mentioned, orbital venous flow, tumor vascular turn of these things. This issue is a normal Doppler, so here's the globe up here. So you're behind the globe here, the optic herb shot would be kind of in here, ophthalmic artery, and then the feeder into the central retina artery, which you kind of get a part of it here, then more of it here. So central retina artery, central retina vein, use of the celery artery, poultry celery, artery arteries. This is a normal color Doppler, how it looks. Obviously, all the blood flow patterns. And this is like a hemi occlusion, had a hemi-central artery occlusion. So you can see this part is just dead, just blood flow is gone, whereas this part is still being vascularized. Yeah. With that, do you know that you're not just catching things? How many of you have knocked your nerve shadow?  Yeah. And then different views, that's a good question. If ever you see something to verify, you have to have just different views of it, just sort of move the probe different directions and make sure it's the same. I've seen, I reviewed papers that they had to reason, they didn't, because they were just looking in one section. It kind of caught an artifact, and if you move the probe differently, it goes away. So for us Jews and don't. This is a Janus Larderitis, and they're just devastating, that's why they're so bad. You lose vision from Janus Larderitis.  So it's just a dead orbit. So, you know, it's just, that's why it's so terrible to get Janus Larderitis, and then the danger is losing the vision on the other eye. 40% will go blind on the other eye within a couple weeks. So that's why it's so critical to make the diagnosis and institute proper therapy. So I need an embolol, an emboli, so you can see them, they're further back. So here's the optic disc up here. This is back behind it, behind the lamina. So there's a little brightness that consists of emboli. Over the venous flow, this is normal. It's a paraphthalmic vein. So it's kind of thin, just kind of bluish. So in the Doppler, this is programmed to show venous flow as blue, and arterial flow as red, just because that's what we're used to, we think of arteries as red, venous and blue. This is the case, came in, kind of, a lot of vascular congestion, these tortuous vessels. Patient kind of had aching around the eye, kind of at night, and they were sleeping there, kind of a wish in their head, so they're kind of a classic, you know, sort of think of the fistula. This confirms it, this is the vein, very dilated, arterialized. The flow is not venous, it's not blue, it's red, because the arterial flow is going through the vein, this reverse flow. So that's where the pressure builds up, and they're so congestive. So this shows it pretty rapidly. Humor vasculature, you can look at tumors inside vessels and the temporal artery. So again, from our study, showing kind of a normal, this is the temporal artery, this is a long section, this is a cross section, and so the artery wall, compared to here, see this kind of illusancy around the wall, that's because of edema, inflammation, so you get this called halo sign, where it's the halo around the, instead of being right around it, it's dark, echolusancy, consistent with that. So that's what we're looking at right now, we appreciate the patients, we're seeing patients probably, got about one nine or ten now, I think we're up to this. Yeah, so I appreciate the referrals. This is a melanoma, again showing vessels inside that, I can actually see vasculature without Doppler on my melanomas, I can see real-time, it's a real-time exam, so I can actually see the flow, and I'll try to show that to you here in a second. And then the high frequency, in my days at UCLA, we used to do this, we draped the page with all the drapes of the water, give them a scuba mask to snorkel, because I hated it because of the water, that's how we deal with these immersion scams. Now we're a lot gentler and kindler with these immersion shells and things that we use just to make it easier. So 20 megahertz, this is a case of a diktioma, I bet you looked at the female in a girl, so you had this lesion kind of up here on the contact, B-scans, kind of real peripheral, hard to see it, with an immersion scan, so here's the shell up here, cornea is up here, here's iris, that's a lesion right behind the iris, kind of in the silvery body, so you can just see it a lot better by doing an immersion scan, vacuum the probe off and seeing the end in the front of the eye. 15 megahertz, that's kind of what we use routinely to see real high frequency, you can see the cornea, iris, anterior lens, you see the zonules here, silvery body, so it just shows incredible anatomy. Here's the cysts, these are pretty common, we see a lot of, you know, we see an iris kind of bulging, it's always good to do an ultrasound if you're sure, it's not a tumor, you can see the big cyst here, not a small part of one here, so these are pretty common. Here's the case we saw with Dr. Vitaly a while ago, so here's a patient had kind of chynauric surgery, kind of chronic recurrent end of uveitis, they kind of get flare up, they treat it with steroids, kind of quiet down over about a year, this kind of kept coming, so I find the uvm, so the cornea is up here, here's the iris, here's the IOL, you see this clump of stuff on the IOL, actually the bacteria are growing, there's a vegetation on the IOL, so this is P. acne, it's actually showing on the IOL, so this patient had to have the lens removed, the caps removed, all that just to clear it out, freedom. Another case here, this is an ux syndrome, so uveitis, glaucoma, hyfema, so here's the iris, here's the IOL haptic, here's the optic, and here's the haptic, and as you follow it out, it actually gets right against the iris and rubs against it, so you get this chronic irritation called the ux syndrome. This shows you can see different things in the atrial segment, even with the 10MHz Pro, if you don't have a high frequency uvm, you can still use a 10MHz standard Pro, so here's a case of an iris cyst, right there with 10MHz, here's a 20, here's a 50, so you can see it better obviously with higher resolution, but you can still see it with a lower resolution, so you still don't have access to it, you can still use that to look down to your segment stuff with immersion techniques. Kind of comparing OCT to uvm, OCT is great in the anterior chamber, but it's not so great behind the iris, it's a light pace, you can't get it right behind the iris, so here's a patient with a tumor here, kind of a bulge in the iris on OCT, but you can define it much better with the uvm, so these are all examples of that just showing just down the board here, the uvm is superior to that area, so everybody, so if there's anything behind the iris in the anterior segment, you're better to get a uvm than an OCT. More examples here. Okay, so that is a sort of an overview, ultra-sing on, so there's a video, so it doesn't crash like very well, the PEC. Well, it might be just this little security setting. Okay, there you go. So again, this shows kinetics, this is a vitreous hemorrhage, you can see the fluidity of it here, and that could be a detached retina there, but so mobile, so fluid and re-attached to the optic disc, you see how it moves, how it flows, so that's an example showing the kinetics. The very, very corner, the red one. The top right here. This shows vascularity, so this is a melanoma here, but you see that little flicker inside of it, this is a rapid little flicker, that blood flow, so if you see that, you're always looking for that, whenever I see a tumor, because a lot of tumors don't have that, hemangioma is done at all because they're a slow venous stagnant flow, a lot of things are done. Yeah, basically, yeah, it's just not that fast arterial flow, and the same thing was like a capillary hemangioma and a baby with heavies, you know, there's bumps on the rounder eyelids and things, you can see the blood flow with you, so it's very helpful to see that, see that rapid flicker. You don't see that, appreciate the motion. A-scan can show it too, so here's the lesion here, and see that inside of it, everything's kind of moving, but there's such a real rapid independent motion inside that thing, which A-scan can also demonstrate the vascularity, but I think B-scan is better, it's easier to see it. It's another melanoma kind of mushroom, again, with rapid flickers inside of it. Here's that case I'm trying to show, here's a melanoma, but you can see the blood over it, so here's sub-high-loan hemorrhage. As the eye moves, it just kind of swishes, it just sort of flows really easily compared to the stiff motion of a detachment. Here's the tumor, but that's the membrane over, that's the detachment. See how stiff it is? This is not an undulated, really easy motion.  So it was a distalable, a true counteractor distalator. I think there's probably any one more vitreous, again, showing the vitreous, the hemorrhage and then the vitreous, the posterior hyaline phase, just a lot of fluidity. Okay, so that's it. Ultra-Sanctiated. Thank you very much for your welcome. I'm happy to spend time with you guys and everyone.


People going on low-carb diets may not see a rise in their cholesterol levels. How is that possible? Because weight loss by any means can drop our cholesterol. We could go on an all-twinkie diet and lower our cholesterol if we were unable to eat the dozen daily Twinkies necessary to maintain our weight. That's why a good cocaine habit can lower cholesterol. Chemotherapy can drop cholesterol like a rock. Tuberculosis can work wonders on one's waistline. Something that drops our weight can drop our cholesterol. But the goal isn't to fit into a skinnier casket. The reason we care about cardiovascular risk factors like cholesterol is because we care about cardiovascular risk, the health of our arteries. Well, now we have studies that have measured the impact of low-carb diets on arteries directly. And a review of all the best studies done today found that low-carb diets impair arterial function, as evidenced by a decrease in flow-mediated dilation, meaning low-carb diets effectively cripple people's arteries. And since the meta-analysis was published, another study found the same thing.  Peripheral circulation is great, but what about circulation in the coronary arteries that feed our heart? There's only been one study ever done measuring actual blood flow to the heart muscles of people eating low-carb diets, and this is it. Dr. Richard Fleming, an accomplished nuclear cardiologist, enrolled 26 people into a comprehensive study of the effects of diet on cardiac function using the latest in nuclear imaging technology, so-called SPECT scans, enabling him to actually directly measure the blood flow within the coronary arteries. He then put them all on a healthy vegetarian diet, and a year later the scans were repeated. By that time, however, 10 of the patients had jumped ship onto the low-carb bandwagon. At first, I bet he was upset, but surely soon realized he had an unparalleled research opportunity dropped into his lap. Here he had extensive imaging on 10 people following a low-carb diet, and 16 following a healthy high-carb diet. What would their hearts look like at the end of the year? We can talk about risk factors all we want, but compared to the veg group, did the coronary heart disease of the patients following the Atkins-like diets improve, worsen, or stay the same? Those sticking to the vegetarian diet showed a reversal of their heart disease, as expected. Their partially clogged arteries literally got cleaned out. They had 20% less atherosclerotic plaque in their arteries at the end of the year than at the beginning. What happened to those who abandoned the treatment diet and switched over to the low-carb diet? Their condition significantly worsened. 40 to 50% more artery clogging at the end of the year. Thanks to the kind generosity of Dr. Fleming, we can actually see the changes in blood flow for ourselves. Here are some representative heart scans. The yellow and particularly red represent blood flow through the coronary arteries to the heart muscle. This patient went on a plant-based diet, and coronary arteries opened right up, increasing blood flow. This person, however, started out with good flow, but after a year on a low-carb diet, significantly clogged down their arterial blood flow. This is the best science to date, demonstrating the threat of low-carb diets, not just measuring risk factors, but actual blood flow in people's hearts on different diets. Of course, the reason we care about cardiac blood flow is we don't want to die, and a meta-analysis was recently published that finally went ahead and measured the ultimate endpoint, death. And low-carb diets were associated with a significantly higher risk of all-cause mortality, meaning low-carbers living a significantly shorter lifespan.


Hi everyone, Joe for jaspyscasebrakes.com coming at you with 2021 Panini Immaculate Baseball 8 box pick your team number three There's the full case right there big. Thanks everyone here for getting into the action Appreciate it Thanks for buying your spot straight up. Also. Thanks to the people who bought number block spots gone to the RnB Right there, so it works just like a serial number break, but only for those teams and only for this break right here And I guess we'll set this over here Let's pop this open now. We do have more We do have more immaculate in the store if you want to Get some teams going And yeah as glowbug was suggesting we're not we're not very we're not too far away from knocking out those hit packs as well Ladies and gentlemen, I think we can do those tonight Might have some immaculate stuff in there All right, we'll use this blank card right here to slow play some of the hits There is Craig at Kimbrell 80 out of 99 for the Cubs Dan Tyson with the Cubbies I think so These might all go in 180 tall. They're just slightly larger than the cards are slightly thicker stock than the 130's Bob Feller is 23 out of 49 For Sherry and the tribe our first autograph is keeper Ruiz monochrome auto jersey and silver ink auto on the I black 16 out of 34 for my Dodgers It was a national now, but this is still Dodgers keeper Ruiz big catching prospect and Dodgers are a number block team so Dodgers six Is gonna be for on hell out of 49 we got Dean Kramer Five out of 49 triple relic and autograph Orioles are also a number block team Orioles five David Duffy Extra bases quad relic and autograph one out of ten Jose Altuve Astros are also a number block team Astros one Houston one Peter and and dugout collection to wreak school ball 10 out of 20 some nice colors in that dual relic there Tigers Nathan picked up the Tigers straight up So you went to California a couple years back caught a Dodger pottery game in San Diego would love to live on the West Coast. Yes It's a lightful actually. No, it's terrible Don't don't move here. It's too many people out here anyway. I Tried to pretend tell people not to move don't move out here Yeah, I went to I went to college in San Diego, and that's a That's a nice part of town San Diego All right, it's a little bit more of a shallow box Maybe a thin card or a redemption in there somewhere. All right first one right at the top is Joey Bart. It looks nice Giants Jonathan With the Giants got the Giants straight up. I think that's 86 out of 99. All right about 66 out of 98 Next is 61 out of 99 you're done Alvarez Houston one Peter the redemption is gonna be dugout collection Taylor Tremel Taylor Tramble Tremel Not Alan Tramble I think Taylor is a Cincinnati red. No, he's the Mariners now All right to the checklist then gonna go to group rate checklist calm a great resource for collectors Wait, was he with formerly with Detroit not the Reds? Who am I thinking of then? Taylor Tramel is A Mariner in this set So that'll be for Seattle Seattle's a number block team. So the redemption to go to Seattle zero Bennett Wasn't he with the Reds? Maybe yes. He was He was the 35th overall picked by the Reds in 2016 Then went to oh, there's Brian. Yeah, then went to the Padres, right Brian Reds traded Tramel to the San Diego Padres in three-team deal where the Reds acquired Trevor Bauer and the Indians got Yasiel Puyg Scott Moss Framel raise Logan Allen Victor Nova and the Padres signed Tramel to the Amarillo sod poodles of the class double a Texas league and then That was in 2019 in August 2020 The Padres traded Tramel Ty France Anders Munoz and Louie Sorens to the Mariners for Austin Nola and Dan Altavia and Austin Adams There you go next speaking of San Diego. There's Ryan Weathers Triple relic and autograph for the pod. That's Brian Peeples Padres Firing their pitching coach. What do you think about that Brian? And there's Ryan Jeffers 43 out of 49 That's a nice patch there for the twins Eric Leal of Minnesota Right different different Tramel. I think Taylor might say it Tramel. I think Allen is traveling and back here Esteban Floriel 46 out of 99 Jersey and autograph for New York, New York Bennett with the Yankees got the Yankees straight up Brian says good riddance. Oh, how much does the pitching coach? I don't know. I was wondering that how much of an impact is the pitching coach? I guess big enough Because they identified him as the as the problem Piece of the hat the button of the hat. Who is it? It's jumbo hats button Edward Oliveris Nice, that's pretty cool Royals Daniel with Kansas City. Nice. What's that number two? That's one out of two. Nice Daniel All aboard the Big Head Express That's really cool the button on top of the hat. That's awesome All right onwards. What do we got here? Old school guy a piece of his lumber 24 out of 25 Ed Rausch For the red legs Dennis for the Cincinnati Reds Joe Adele 45 out of 59 Big Angels prospect going to Robert Flores and the Halos 16 out of 99 That's Johnson Stiver two-color triple relic and auto at errands with the White Sox Zach McKinstree 40 out of 99 bit of the the red the number Dodgers are a number block team. So that goes to Dodgers zero 40 out of 99 Bennett the Dodgers zero the last one out of here is Fergie Jenkins 16 out of 49 Cubs Dan Tyson with the cubbies.  That's a one-of-one and that is for Sherry and the Braves He's a catcher too. So that might be a big piece of his catcher's glove. That's awesome Sherry and the Braves All aboard the Big Head Express whoo-hoo He started a marté if you had not Attempted that Stretching that to a double it could have been a two-run shot 19 out of 49 Nolan Ryan Tom Siever Ranie Johnson Roger Clemens Wow monuments quad relic two Mets a diamond back and A Yankee we'll do a randomizer on that at the end Next one is a blockchain card Anderson Tejada. I think is a ranger Yes ranger So that's a that's for Patrick Davis in Texas Next up Tucker Davidson three out of 25 two-color patch an autograph Sherry again Braves Bobby Bradley 27 out of 99 for the tribe Sherry with the Indians Cleveland Mickey Moniac 10 out of 16 two-color patch and on card autograph rookie patch auto for Logan and Philadelphia There you go Logan three out of five clutch relic and autograph. Hey, Sue Sanchez Maybe a inside of the hat maybe new era logo hat gotta be Miami Josh Proust Out of fives and under get the world famous train whistle All aboard the Big Head Express We are halfway through this full case break four boxes to go Alright, we got Wilson Contreras Williams brother 22 out of 25 Dan with the Cubs Two out of three Joe Sewell Old piece of this old-school guys lumber. Look at that For the Cleveland Indians Sherry with the tribe, you know like a 1920s player. That's awesome Game worn slash used material game used That's pretty nice Sherry all aboard the Big Head Express whoo-hoo 26 out of 49 two-color patch and autograph Ian Anderson Sherry and the Braves Sherry's heating up. He's on fire from downtown Louise Garcia 42 out of 64 clutch Jersey and autograph Nationals are a number block team. So that goes to Nationals to Washington to Craig Couple more here a one-of-one Jeff Bagwell That's pretty clutch Astros Astros are a number block team Houston one Peter Aang Gets the one-of-one Jeff Bagwell patch and autograph Congrats all aboard The last one out of the box It is Jose Garcia four out of 50 clutch Jersey and autograph for Dennis and Cincinnati onwards Logan you remember that were you talking about Joe Sewell Logan? Sites his three spots for the sterling fillers and for the show notes a five spots for each You got to read the show notes carefully Ryan Harold. We're giving away five filler Spots within the filler in addition to the three blaze and 24 spots. So there's the game within the game I know it's hard to it was hard to explain. What how did I write it? Five filler spots given away in each filler not blaze and 24 spots George Springer Toronto edition piece of his lumber 66 out of 99 Steve Wright and the bluebirds Can barely read it. It's tough. I'm just glad you were looking at the show notes He's impressed by that There's another killer bee Craig bigio two out of ten that will be for Astros to and that's for Craig Who are the other killer bees? Feel like there was a Bagwell bigio Derek Bell maybe redemption Louise Gonzalez immaculate material autographs Lance Berkman, right? Louise Gonzalez immaculate material white socks on that Louise Gonzalez And that will be for Ed and Chicago right Berkman and Derek Bell along with Bagwell and Bee Geo the killer bees a One-of-one jumbo bats and autographs shirt and Apostle and that's that's Patrick with the rangers Patrick all aboard Whoop-whoop a couple more here with 16 out of 49 Alejandro Kirk Triple relic in auto for Steve right in the blue jays and we got nice Trevor Rogers three-color triple relic an autograph 96 out of 99 For the fish Josh Proust in the Marlins Two to go just saw what Ben wrote. We saw that shirt and a shirt and Apostle Ben is now saying we need to see his brother Panson Apostle at some good clean humor though Some good clean humor. It's what we like here at Jaspies. It's a family-friendly show. We got a plate in there All right, George spring another piece of his lumber for Steve right and the blue Jays Ben's like I regret nothing nor nor should you hey 24 out of 25 Tommy Lasorda RIP piece of his jersey Dodgers for It's gonna go to Chris Miller Redemption is a Braylon Marquez premium patch autographs green I think Braylon is a cub He is going to Chicago that'll be for Dan The on-plate auto two-color patch an on-plate auto Edward Oliveris one of one Daniel with the Royals Nice Daniel All aboard the big hit Express whoo-hoo Not a train whistles in this case We got more of this in the store folks Jaspies case breaks calm 12 out of 25 tenor Hawk Jersey an autograph for Ed and the Boston Red Sox, and then we have seven out of ten Team heroes dual relic and autograph Ken Griffey junior Seattle is a Numberblock team so Seattle seven That's for Mark Mark L. Congrats Great case here All right Final box eighth and final box here in immaculate baseball full case pick your team number three six out of 49 Javier bias More cubs for Dan Mike Schmidt eight out of 25 piece of his lumber and Jersey Logan and the Phillies Jazz Chisholm nice five out of ten shadow box autograph It's a good-looking one for Josh and the Miami Marlins Few more to go here Josh Fleming 60 out of 61 Jersey and autograph nice patch raise mark n 10 out of 25 Kyle Tucker Houston zero Bennett just 20 off the jersey number and last but not least good luck everyone is Oh right on the button Casey Mice seven out of eight Button auto for Detroit Nathan Sheldon Got the tiger straight up gets the Casey Mice Former number one overall pick and there you have it boys and girls another immaculate case in the books Let's do some randomizing here So Nolan Ryan Tom Siever Randy Johnson and Roger Clements Let's roll it. Let's randomize it That list three and a six nine times team on top gets it after nine one two three four five six seven eight and Ninth and final time after nine Mets on top that goes to Jonathan Arnaldi with the Mets 19 out of 49 you get this These great pitchers right here. That's pretty awesome nice monuments quad relic and that's that thanks for watching everyone I'm Joe for jazzy's case breaks calm. I'll see you next time for the next break. Bye. Bye


Welcome to some of the work that I've been doing. I just wanted that I've been doing with the community projects and has gotten me excited about working more and getting more deeply involved, not just with the Fedora work, but also just lots of things that are associated with the open source and building images, creating things that other people can use. It's been really fun for me. I'm a solutions architect, so just a little bit about me.  Let's see if my slides will advance. There we go. I spend my daytime working on Red Hat Solutions for Amazon and Amazon Web Services customers. So this is pretty dear to my heart, right? And before I worked in Amazon, I worked at Red Hat. My first computer was a ZX80 that I soldered together with my own hands and with a lot of guidance from my dad. And I live pretty much my whole day in org mode and trying to make everything more like literate programming than it probably should be. So this was an exciting thing for me to sort of take on as a quest. I wanted to build on... Primary goal is I wanted to build with Ansible on Amazon Web Services and to determine where the rough edges were and how I could really communicate that back to the Ansible team, people like Adam and Jill, who are doing really great work around the development while this whole new thing with collections is happening. It's a much more... It's a complicated time, right? And then I wanted to demonstrate to myself and maybe even to others that I could participate in iterative progress in a way that as an architect, I don't necessarily get to spend a lot of time doing. So I'm glad to see, Michelle, that you also enjoy literate programming. It makes me very happy and high-nick. But I have some personal roadblocks I feel like because I spend a lot of my time working on solutions that are kind of key in the business area and not as technical as I would like them to be. And then I rely heavily on strong engineers like Neil, like Nick, like Jonathan to help me sort of redirect the guidelines around projects that I'm working on. And so this was an opportunity for me to kind of dig into the toolbox and sort of feel around and find out how these things really fit together. So there's my primary goal. But then as a secondary goal, I wanted to really jump out there and make this work for a real project, right? And the real project that I chose was to build out two things. One was a CentOS-based image that I could then publish into the AWS Marketplace in China that would match the requirements of the community and be available for Chinese customers, where we didn't have a presence at that point. And obviously, you know, working with the team to make this a part of the process. And so here I am with my goals. I want to build a competency-enhancable and related build process on the distribution of my choosing. And that's mainly, you know, vis-a-vis Fedora for all of us who participate here. I wanted to figure out a lot more about the user collections and where the AWS collections, both community and the ones that Adam and Jill and... I can't remember. There's a couple of others who are supporting this. Beyond just the community at large, it's doing the majority of the work for the AWS so that I had a very strong voice internally to talk about this with our engineering teams. And then finding entryway into the tools and techniques that are being used by my friends like Dusty and his teams and Luca to do the work and maybe make myself even a better candidate for helping them to get their solutions working than I am today. So, and to continue working on that over time. So as issues evolve, you know, editing this, I want to have a couple, you know, this CentOS image and then want to be able to publish the Microsoft SQL image process so that anyone can follow it. And it can be a guideline for how to do this in the real world, but then also to be the exact same as the process that's being used internally for deploying those things for the rest of the world to use in the context of AWS. And then, man, my pipeline skills are bad. So this was a super exciting opportunity for me to get to understand more about the way that Jenkins works. Obviously Jenkins and I have struggled and Ansible and I have struggled together over the course of this and to bring some awareness to some of the best practices around the system that I'm finding out from doing this. So here's my milestones. Build an Amazon EC2 image using ImageBuilder. So ImageBuilder is sort of the focus and I know Neil, you and I have had some conversations around this in the past, but, you know, with the work around OSBuild and the way that it's functioning today, I'm super excited to, you know, to sort of stay on that track and try to bring that up not only through the Fedora work, but also into the Red Hat work and then onto CentOS where I feel like a lot of this work is being done and to be able to do this all in the context of sort of a cloud native style, right? And then ultimately deliver this artifact that is the base AMI for use and a process for reviewing that in such a way that both the build itself is discoverable just like it is in Koji and then to be able to determine how to improve the real processes which are the ones that are being used by the Fedora engine, REL engine, the CPE team today. So I got started and I started working on this in sort of an iterative way, starting with, you know, just the hand-holding and the figuring out how things work, installing things over and over again to figure out how I could better build my process in. But there are so many choices out there in the world on what to do and what tools to incorporate and how to test and what QA looks like. I really had to narrow it down and narrow it down quickly became very key to me. So finding the tools that I wanted to work with quickly instead of figuring out, trying to figure out what was the absolute best tool was I thought the right way to go. So I settled on a couple of things. I think I just went backwards. I'll go forward two slides now. Give it a second. Probably should have done this in a PDF. Sorry about that, everyone. Okay. Yeah, there's a lot of choice out there. And just inside of the Fedora teams, there's a lot of things that are very different and extremely malleable, right? Very different kinds of tools that I could have used. So choosing these was something that was just an arbitrary choice. And I kind of want to make that more or less clear. But I had some goals in mind. So the goals kind of help. Keeping the community project affiliation was really important. And making sure that I was using things that I could see were a part of, at least a component part of the deployment process that everyone was using around me was something that I wanted to keep in mind and make a part of my decisions. I also wanted to be able to read whatever it was that I was using. So important enough that it be open source because that was a part of my process, was figuring out how these things work and then filing bugs on those things, being able to patch them and look at them. And Image Builder and I had a lot of those and I marked a lot of things as bugs and then I marked a lot of things as not a bug after I figured out what I was doing wrong. But then I got to be a part of a lot of the test patches and figuring out what was going on upstream. And Brian Lane helped me a lot to get to the next steps on building images with Image Builder. And some of the things that I learned applied directly to those downstream commercial goals that I have, like building RHEL with Microsoft SQL on it. And I found some things that were really interesting about the build process that I've implemented in the context here. I'm one of those that I don't have really illustrated in my slides, but I wanted to talk about a little bit is the ability to provide a group of scripts from a GET repository and present them as an RPM, dump them into a specific location, and then execute on that in the context of the blueprint. That was a huge assistant when I was looking into the concepts of building the SQL images because I couldn't figure out how I was going to get all of that script information material onto a system that was freshly installed without doing some sort of a crazy charoute or something else that didn't feel like it was going to fit with the CLI commands or even the cockpit model for doing the deployments. But I was trying to stick to the CLI commands or anything that I could script in the context of Python so that I could move forward with the deployment hands-off and keep it moving in a long-running configuration. So what does it look like? So first off, AWS Code Pipeline became a component part for me because, well, I'll talk about this later, so I'll talk about that part of it later. So first off, the Ansible scripts are part of the deployment. That's pretty much the trigger, and it hooks back to the GitHub repository through push events to the Code Pipeline. The Ansible script runs, and the first thing that happens with the Ansible script, and of course, this is a chicken and the egg problem, the Ansible script has to run once manually. So my goal was to have something that I could run once. It would build the infrastructure that I need, and then once that infrastructure was built, I would be able to maintain it with the same scripts. So first off, the Code Pipeline, there are Ansible modules to support building the Code Pipeline itself. I mean, you have to go in and dink with the permissions for the push events. If you want to use the push events, you'll have to do the authorization from GitHub to the Code Pipeline so that it can see your... So it has access to the repositories. And then, find the images that I want to use. In the current state, or in the state that I'm using ImageBuilder, I'm obviously OSBuild. I should be able to use... When I'm using that, I should be able to use a single distribution version to do more than one other version. But for now, I need an individual ImageBuilder instance for each one of the distribution versions that I want to build for. And that means I also need one for each one of the version architectures that I need to build for. Something that I found kind of interesting there was that the... Obviously, I had to craft a little bit more handily the configuration. I've got some snippets here. Let me see if I can pull something up in the Emacs here so you can see it. So here in the server, in the server definition for the Jenkins, and there's a few variables that are missing. But I thought it'd be interesting to kind of show this. One of the things that I wanted to make... One... Or an important distinction in the way that this Ansible script works... Yeah, exactly, Neil. So... But Neil was grumbling about the lack of cross-arch support. It gets complicated. And so good news is that I have what I need to pull that out. And so where's my... Army definition? There we go. So if I have an instance arch, I'm using that instance arch in the definition of the Army query. So grabbing these thanks, Dusty, for making this so easy to review. And then grabbing the instance architecture that I'm expecting to build for. Once I have the instance architecture, I can make a decision in the variables about the configuration. But I've got it here, specifying the instance arch in the filters. And then same in the name, I obviously could have gotten away from doing it one place or the other, but I've got it in both, and I'm comfortable with that. And then the Genja template of functionality was something that I had not worked with previously, but then started to work with in more of an interesting way. And I found a whole lot of ways to do this, and this is one of those places where I feel like I really need to dig in, that it's the place where you'll see the most functionality in Ansible go the way of one line scripts where you said something into grep and then awk it, right? There's so many places in here where you can just transform data in different directions. So that's an essential component part of the deployment of the Jenkins server. Also, this is interesting here, there's a number of these modules, so from the collection, the Amazon collection, and then there's some from the community collection, and it's not clear which direction to go with which one today, and I feel like that probably will clear up more in the future, but it was an interesting experience to go back in and see where those are. So this is a little bit more about the pipeline itself and what my goals are and the experience around that are. I've got an extra helmet in here, sorry about that. So the helmet is an IAM role, and this is something that I'll point out a little bit more, but I'm associating an IAM role with the Jenkins instance because the Jenkins instance is in the playbooks. So initially, you have to run the Ansible playbook from somewhere, but next time it can be, the Ansible playbooks will land on the Jenkins instance or in the jobs themselves, so it'll land in the pipeline, and this is essentially what's going on. So here's me and anybody else can help me get better at what I'm doing. So Jonathan, it's not yet... Jonathan asked if this was somewhere public that we can access the playbook. It's somewhere that I can share it with you because I would be super excited to have any of you help me get the work done. But right now, I have questionable security on the artifacts that are in the repository, so I want to make sure that I'm not sharing out old secrets. Yeah, I know. Neil gave me the side eye on that one. But yes, I'll get it out. I'll make sure it's available, but yeah, there you go. It will be available to everyone to look at. So the way it works now is you update the GitHub repository, and actually I've got it split into two repositories. There's one repository that's there for the image builder to collect the information that's associated with the builds. So for the SQL server, there's a repository specific to the build of the repos. So the instances that I'm using are cloud access instances, and the cloud access instances come up. I register them with Red Hat, and then I'm doing a full repo sync onto the image builder instance. I have to use a pretty beefy instance to get it to work because it either has to be metal or one of the larger, more sophisticated nitro instances to get the virtual machine configuration to run in a timely manner. I mean, I could run a smaller instance for longer, but why? If I'm just going to shut it down. So from there, the pipeline push event happens in the code pipeline, and the code pipeline is initiating a longer run on the Jenkins server. So the Jenkins server only has the standard port open. I haven't done anything to secure it at this point. That's a roadmap item for a different time or for someone who knows how to do it in seconds instead of me doing it in hours. So the Ansible Playbook then runs and creates, generates the instances, and you see the little Lorax here, a little history on the image builder. The instances are then generated using the blueprints that are in the configuration from the GitHub, and the blueprints themselves are just pulled from S3. So the whole goal of this obviously is to have several of these instances running, creating either REL7 and REL8 or CentOS7, CentOS8 images with the component parts. And then to have essentially a little solutions builder here so that we can vary the blueprints that are being used and produce some very interesting sort of collections of what I'd love to do, and this is my goal here on what I was excited about was building a way to have solutions that are already there in the Fedora repertoire or scope and to provide images of those that can be shared to customers in ways, really not customers, but everybody users who want to leverage that in the context of the cloud and to provide kind of a guideline model for an architecture that spins up works and then spins itself down, but is still fully functional. Because, well, we'll talk about that in a little bit. So the and then to have an associated role for this instance here so that we don't have to ever provide any of the any of the credentials that would be required so almost everything that you read about using Amazon EC2 has somewhere where you're storing you know in a semi or permanent or permanent way credentials that then are out there in the big in the big world with with little safety net and of course we don't want nobody wants that. So Neil, you had a question. You said, is the idea to have a layering model for producing omis? Yes, the idea is actually to have a way to produce artifacts that are not just omis. I mean, the goal is to be able to produce isos to produce anything that people, you know, that you would want in the same way that you would do that in the context of Koji, right? So, I mean, I believe that there's nothing there would be nothing from just just outlining and deploying a pipeline with the or deploying a a request to build the images with the scripts that Dusty has in place today, like with the Corus builder or whatever, you know, or the image builder in the context of the CPE but this is kind of a I want to understand this model as much as as you do. And some of that requires some building, right? Building on my part. So, using the AWS code pipeline, so jumping right into building out and I know it's fairly simple to build a standard pipeline configuration for Jenkins, but it's not really on my radar of things that I need to be deeply involved in. So, I chose to take this to take this path with the code pipeline to begin with because I felt like I was I needed to crawl before I was walking and I also needed to have something that was there available and servicing the configuration at times when I didn't have any hardware in place and wasn't really ready to deploy or what didn't really wasn't really active, right? So, let's say there's no changes in the GitHub repository, there's no modifications to the code that's associated, you know, that's intermediate I don't have any way to I don't have any need for infrastructure I want that to go away and then to integrate with as many the tools that I mean, so knowing that many people were not going to have the same kind of limitations around Jenkins not going to have the same limitations around I wanted to have around the other tools that I had chosen I wanted to make sure that the people who were willing to help could jump in and really help me not only expand my understanding but also to expand the capability and the ability for others people to use it and there's like some cool tools out there that I learned about just, you know, in the past day like TMT, like the test tool that Miles and those guys were working on and it's pretty amazing how much of that could extend the functionality and something like that Code pipeline, no, so Neil asked if it's a pipeline Jenkins based or something else it's something else, so it's a it's actually based on an internal tool that is called pipelines for Amazon and it was originally written I believe it was still written in Java but it was originally I mean, now it's written at scale in microservices and it's given to the AWS microservice model integrating into a whole lot of other tools on the back end okay, I accept that but it's a, when I say that I mean that by itself it's not Jenkins based and in fact benefits from an extension to using Jenkins for standard pipeline technology you can build your own plug-ins for it but it's a, in my opinion it is a fairly simple tool for the process and it expects you to incorporate custom components into your build process and somebody else has a different opinion of that and I'd love to hear it and like when you're not yet, well, not yet yeah, so it's very limited in the scope of the repositories that it will use so you can, having a native Git repository is not supported having a GitHub repository is supported having a code commit repository is supported having an S3 object that has SNS notifications is supported but like I said it's one of those things that I thought was a really good it's like a really great fit for where I am today and that may end up being replaced by other open tools just because my goal is obviously open default to open so the long runs, so all the things that are doing here was a community decision so I want to learn with my friends this is not as simple for me as it should be and I think that if I give a lot of people an opportunity to really shine that I get a lot out of it that's something I'm really grateful for and I think we all are grateful for the mentorship that this project has brought to us all but it was a great opportunity for me to reach out and say here's a simple tool where you can hone your mentoring skills and I can benefit so there's outside of the GitHub flavors like Travis and Bamboo and all that there was a it's a pretty solid rock solid choice GitLab has their own hooks and everybody's got some way that they can integrate with it it's the legacy soldier that keeps us all working and keeps sent to us and check and so there's a lot of I think there's a lot of benefit to working with it obviously it facilitates my needs and AWS Batch was something that I toyed with the idea of putting in here because it also is great for scalable work and like massively scalable work it's used for in a lot of cases where people are driving parallel computation in ways that are different than they used to it's not just your basic batch scheduler like platform or lava so I considered it pretty heavily because it's one of those things that I hear a lot of customers say oh well we have thousands of virtual machines and it's going to cost us a lot more money these thousands of virtual machines on the cloud and when I look back at them I see that they're purpose built they have very specific functionality and that keeping them around isn't really necessarily in anyone's best interest it's just a good thing to have those purpose built configurations and so I thought this might be an interesting place for me to understand better how I could help people disaggregate those workloads and understand how to save how to save money in the way that they do it and so I mean I'd love to so long picture I think of this Serge's work on Koku and the things that are out there that that are integrating cost analysis and billing review into their process and like billing alerts I'd love to sort of build that into this process so that people can understand exactly what it is that they're getting in the opportunity and make something that I think is a good reference architecture in the context of Fedora and Fedora based tools okay so here's my spoiler which is that I'm not done like I was super excited to do some big time demos for Flock but I haven't made it so let's talk about this as being the first iteration of the talk and the first iteration of the tool so I mean I can show you some of the things that I've done and we'll do that if we have time and you're interested but the truth is is that I'm still running a lot of this by hand and I'm not getting any of the Jenkins stuff built but in an automated fashion so it's burning a hole in my pocket to get more time to work on this only building the image builder so far and producing fundamental images for like our instances I guess I should say instances for CentOS 7 and 8 and the upstream Red Hat 7 and 8 so now a CentOS 7 and a CentOS 8 image in either architecture on and a 7 and an 8 on either architecture I don't really feel like I have to worry about doing that on the Fedora side because Dusty's doing it all for me but to have those with some customized configurations the same thing I would love to do the same thing in terms of the spins but I don't have I haven't really pulled in the spin configuration so that I was just churning out machine images but at some point I would love to see that and then creating sort of a state equals stop or a state equals terminated or a state equals absent I guess for the EC2 instances hasn't really happened yet and one of the things that I do want to experiment with it's not really available yet but it's still I mean it's open it's an open item to integrate EC2 hibernate into support and onto AWS within the context of Fedora so Neil I hope you'll review that spec file when I get it polished for addition so the EC2 hibernate while the page is changing one of the things about the EC2 hibernate what was exciting for me is that hibernation in the context of a server and definitely in the context of a cloud server is something that's fairly new but I think it's kind of catching on and there are people who are using it in the context of spot instances so they're like hey you know this is a lazy process so I don't have to really think about whether or not I want to do it I just would go back to the service and then and then I can look at you know I can I can look at the spot price and then when the spot price is right I just wake the instance the instance continues to work if the if for some reason there is a you know there's a spike in price then that can go back into the hibernation state and continue forward there are some challenges that have been kind of interesting because that we've run into and I think are kind of sort of notable one is the SE Linux policy around writing to a swap file it turns out that it's better obviously it's a better practice to not force customers to have like a second volume for hibernation you want to you don't want to swap volume by creating a monthly bill for an additional device that's going to hold a swap partition so the swap partition itself is kind of rolled into in or it's it's a it's basically a five gets created as a swap file and that swap file gets written to well it turns out that the FS isn't really friendly to writing to that swap file in a block fashion with transparent huge pages so you have to turn you have to move the move from the default configuration of thp on to mAdvise so that the so that the huge pages aren't used in the in the that is that's a great first step in preventing file system corruption but then SE Linux domain for hibernation for the for the shutdown that domain doesn't have context to write to the swap file so any attempt to run an actual hibernation lands you have to relax the SE Linux context so here's something that I have I found very interesting so one you know we're just in the early stages of the community and the supported can I go backwards I did we're just in the first stages of the ansible support for collections and while it's gone on for now for a little while from you know for over the course of the you know early in 2.8 and then now in or late in 2.8 and now in 2.9 the 2.9 has brought brought us the first releases of this and like I said I'm super excited about where this is going and I think quite a bit for more active participation on you know from the from the teams that are responsible for these for the services underneath these modules so that we have some full support but for now we have really great community support for a lot of the configurations and just building in the support for or building this into my process of to the local directory has been beneficial in running the ansible configuration so now I'm building those ansible configurations and the local the local setting I'm not setting them up in just across the system with the ansible playbook I'm setting them up with the with a config that has the current working directory as a base I think that's the right way to do it the system role for image builder I can't remember the name of the guy who's responsible for this but I can ansible galaxy it into support I think so I do an ansible galaxy collection full system roles image builder is it info collection yes it's an Ubuntu laptop it's my work laptop you know so you'll ask if I was using an Ubuntu laptop my my fedora laptop has four gig of memory and my Ubuntu laptop has 32 gig of memory so when I thought about where I wanted things to go yeah it's got to be in here somewhere so yeah it'll give you an idea of what I'm doing to run this I'll just leave it at that like I said I can't remember who's I can't remember the command anyway so this builder role was critical but then the other thing that I thought was really important and something that I thought was interesting to everyone was that the storage role in the context of building for AWS is tough and Dusty we've talked about this and this goes back to the Udev rules that we talked about before and that we were talking about the upstream bug for this where the devices on EC2 the EBS volumes they come in as pseudo PCI devices in the way that the hyperconvergence works Terry Bowling thanks Neil and it's fabulous he's doing it constantly increasing the robustness of the playbook all the time so I'm super grateful to the work that he's done and just want to call that out so the storage devices though the way that we call them out in the configuration as a device the device names are old school devices slash dev slash SDG SDF but that enumeration doesn't carry over into the operating system once you get into the operating system that device name that you've associated with the EBS volume the ID goes away it's in the NVMe info for the device but it's no longer but it's not a sim link so whatever you named it that doesn't exist you have to go back and rediscover that or use the Udev rules that Luca provided in CoroS to to develop that and I actually have a copper repository for the EC2 utils that came out of the Amazon Linux instances so I built this EC2 net utils so that it can include both the network utilities for managing the ethernet or the network interfaces and then this the EC2 utils so that you could enumerate the devices but Luca's rules in my opinion are they are more I think they're simpler right so he creates a simpler rule and gets the same result so I would encourage you if you want to you know to leverage this package or doing it the way that Amazon is doing it in Amazon Linux but if you want to see a very effective and efficient way of doing it I think that Luca made a great set of rules so well I've got a heavy hand on this pad so the storage configuration becomes rather important so one of the other things is that the volumes that you're writing the images to is a volume that you can restore from snapshot this is not something that I've put in just yet but it's on my wish list for things that I need to do but the one day this will advance is that the devices themselves have to be enumerated correctly you have to go back in and discover them the NVMe CLI gives the information that you need but if you're in Ansible that's not necessarily something that you're using unless you install the NVMe CLI so this role storage you have to remember to go back and reestablish what the devices are or add the EC2 Utils or Luca's UDev rules into the system to get the right device information and I think that's handy just in general not just specifically in the context of this this configuration so I pointed out that I did the IAM role associated with the Jenkins instance and that was permanent credentials or what I say here a waste of your time the same instance you have for Ansible Engine can drive your Jenkins server it's possible that we could do an AWX server at some point or an Ansible tower and use that for callback functions one of the things that I think is completely underutilized in the context of public cloud is the cloud config and cloud init and I'm sorry Ignition Dusty, I'm talking about Ignition so bringing that whole process together is something that I think is really important so there's nothing stop us from killing the entire architecture and leaving one pipeline in place and with that I'll I've left two minutes for questions so Neil asked does AWS have a fancy native way for Ignition configs? No the answer to that is that in almost all the documentation I see a lot of just stepping away from the cloud config or the JSON configuration that you would require for Ignition config to be laid down to just issuing bash commands at the user data level and if you look at some of the things that are done with the the EFS team they have done some things that are similar to what I would expect to have happen in vendor data but they injected into the user data configuration at launch and it is always done in a scripted fashion rather than yeah Neil, your sentiment there is exactly like mine so I tend to and I think I have an example right here so I tend to start and end with I don't have an Ignition script up right now so just bear with me but I am doing this like I said CentOS 7 and RHEL 7 and 8 so for me the most important thing is to ensure that the configuration is set so that you can so that it can be read by cloud and yet I can get it out of the analyze so if I need to do a cloud and it analyze I can figure out what happened so no shebangs for me if you are doing a run command it should happen in the context of a list like it is supposed to in sub process anything else? Any other questions? Thanks I am super excited about it and I will tell you right now but it is getting better so you grumble about it let's build a little bit but I tell you everybody is getting a lot more excited about it with Lars in there doing a lot of work on it but it carries that legacy and a lot of the things are going in the right direction and there is a lot of focus on being able to build a much broader set of tools with just the one or broader set of results with the one tool so I am really excited about it and will continue to work on integrating it and building this iterative process so we can all look at it together I will submit this talk again and we will look at what it looks like the next time yeah thanks everyone for participating I really enjoyed this and I hope we can work on it together and I am always on IRC I will just say that so if anybody wants to reach out I am super happy to respond back and I am DAVDUNK everywhere


So you've got your brand new boots, just a few things to remember before you go away on your holiday. Number one is get the boots on your feet before you go away. What we want to do is try and bed the liner in. You shouldn't really be doing this on the first day of your holiday. So wear them around the house, go to a local slope, but if you can try and spend at least kind of an hour in them, do not sit down in them because your feet are likely to go a little bit tingly, but remember they will be tight. We don't want a slipper. This is a piece of sports equipment. Another really important thing to consider is the quality of the sock that you're using. We want a decent sock with a thin to medium thickness on it. We don't want one of those old school tube socks. If we wear a thick sock it's only going to make the boot feel even tighter and squash the foot inside the shell. If you've got any questions or nerves about your boots before you go away on your holiday, please make sure that you give your local shop a quick call. We can answer any questions that you have, but also we may recommend that you come in and we can do some tweaks or modifications to make your boots feel a lot better before you go away. On your first few days of skiing you might feel that the boots feel a little bit tight. It's a good idea just when you're on the lifts or at lunchtime just to loosen the clips off. The boot still has a little bit of bedding in to do. When you're in shop the heat molding does a little bit of this, but really wearing and using the boot is what needs to happen. Remember that ski boots are made of plastic, so if you go from a warm boot room out to a cold ski environment chances are that plastic is going to contract, so if you over-tighten your clips in the ski boot room when we go skiing you might just find that that first run of the day feels really tight. When you put your boots on for the first time you just might feel your toes a little snug up against the end of the shell. So what you need to do is do these top two clips up, flex into the boot, your heel will move back into the shell, your toes will move away from the end. Once your foot's set do these bottom two clips up. If you have custom insoles inside your ski boots be wary of using boot dryers. Just check the temperature with your hand or speak to the hotel operator because what we don't want to do is melt our insoles inside our ski boots. If you find that after your ski holiday that there's a few pinching spots so it's a little bit tight in certain areas of your ski boot pop into your local store and we can make any adjustments that we need to to make your boot feel more comfortable. Ski boots require very little in the way of maintenance but your feet sweat a lot and ski boots aren't waterproof they do let water in sometimes so when you get home from your ski holiday it's a good idea to pull your liner out of your boot and let the liner dry naturally. How you want to do this is put your hand on the back of the boot there's a little loop sometimes on the back of the liner and just push the liner away from you. Another thing that sometimes people struggle with is getting the liner back into the shell so what you want to do is just pinch the back of the heel push it down about halfway then get your hand in and push it the rest of the way. The last thing we need to do before we pack our boots away for our next ski holiday is make sure that we do our clips up and we want to do them just on our normal ski boot setting so that they keep that nice natural shape around the foot and the lower leg. So if you just follow all the points that we talked about and take our advice there's no reason why you shouldn't be comfortable inside your ski boots and enjoy your skiing holiday but remember that your local L.S. Brigham is always there for any questions you've got.


The Labour Party presidential candidate, Peter Obie, has cast his vote at a polling unit 19 in the Agulu area of the Anioccia local government area of Anambra state in Nigeria's south-east geopolitical zone. Obie and his wife Margaret cast their vote around 11.45 a.m. on Saturday after following the voting queue for about 30 minutes. Addressing reporters after he voted Obie said the process was seamless. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.