I'm James Costas, the U.S. Ambassador to Spain and Andorra. While I have the privilege to serve as the official representative of the President and the American people here in Spain, all of you men and women working for the U.S. military or as civilians abroad are also serving as ambassadors of the United States in your own way. I'm proud to welcome the sailors of the USS Porter, the third U.S. destroyer to be home ported at Naval Station Rota. Alongside the Donald Cook, the Ross, and eventually the Carney, these ships will help protect the European allies, U.S. forces in the region, and the U.S. homeland against the threat of ballistic missiles. All U.S. forces stationed here in Spain, whether the Marines, the Army, the Air Force, or the Navy, and whether it Rota, Morone, or Tera-Home, play an important role in ensuring the safety and security of the people of the United States and our allies. I want to thank you for your service and for your significant contributions to keeping our strong partnership with Spain and with all of our allies across Europe thriving. We are moving forward together.


Karma will destroy the narcissist. You may wonder if the narcissist will ever experience the same kinds of things that they have caused you to experience. You may wonder if there are future consequences that will be shaped by their present actions. You may wonder if they are unknowingly planting seeds or do they just move on and find something else after they try to destroy you. The truth is that there is an universal law of cause and effect where things happen as a result of something else. Every action has a knock on effect. It causes other events and situations although not always directly. Some people call it karma. Other people call it God or the universe but people understand that it exists and that is why we tend to do good by action virtuously because whatever you put out will always come back to you. It will return to where it belongs so it doesn't matter if they move on or if they try to begin a new life with someone else because karma will always come back to them but they will try to run away because they're trying to escape the results and effects of the actions because they don't want it to have an opposite and undesirable effect what was intended. They believe that if they remove themselves physically then there won't be any unintended consequences of their actions. They will blame you to feel better about themselves because they're not considering that there is a spiritual side to this but they mistreated you and they know that so it is something that will play in their minds and you were not the only one because you're not the only person that they mistreated they've already caused so much pain and suffering to people long before you came onto the scene and all of this will come back to them eventually because karma never loses an address and in my own experience I have seen narcissists experience their karma I've seen them going through it and it gets them when they least expect it when they think they're safe when they think they've escaped but that's when they end up in a worse situation than when they were with you because they're always trying to gain an advantage they're always looking for a way to get one over on you they're always trying to find a better opportunity while they leave you hurt and confused but that pain helps you to heal and become stronger it makes you a better person but narcissists are inadequate they're damaged so they're flawed in character efficiency and worth which is why all they can do is try to damage you they will try to find someone to replace you but they're just going to end up damaging them as well it might look good in the beginning but it won't last for long and it won't end well because they're damaged so whatever they get involved in they will always be disturbed some problems because not only do they have to deal with the new person's faults and failures but they also have to deal with what's playing on their mind from the past while karma is coming to hunt them down but you may not see them getting their karma because they're masters of perception management they control what you see to change the way you think about particular people situations and events they plan and coordinate the elements of a situation to produce the desired effect especially when they're hurt especially when they're going through hard times because they don't want you to see them when they're weak and vulnerable the way that they choose to live will cause them to receive the same destruction that they put out you may not see it but it is going on behind the scenes they will be struggling when they thought that they would get went over on you when it turned out to be a very unpleasant experience for them because karma is real they thought they were going to replace you but they didn't so they will constantly be looking for something else and they will be looking for someone who is just like you because you set the bar you established a level of standard and quality for other people to meet but they will never find something like that again so they will only experience disappointment and dissatisfaction thank you for watching if you found this video helpful please give it a thumbs up share your thoughts in the comment section hit the subscribe button to receive the notifications if you would like to support the channel you can donate at paypal.me-nark-survivor you can book a one-on-one with me on my website it's nark-survivor.co.uk thank you for watching and I'll talk to you soon


The next speaker is José Rodríguez, he's a cardiologist, a clinical cardiologist by the Brown Hospital here in Barcelona. He's doing non-invasive imaging and for the last years he has been involved more and more in MRI, mainly in cardiology, going from using MRI for looking at the heart, mechanics, looking at deformation and things like that. And nowadays, more and more about flow imaging. Well, first of all, I will start my presentation. I would like to thank Bart for the invitation to participate in this summer course. And also I would like to thank the previous speaker for being so supportive and reply all the questions while I was struggling with my presentation there. The problem was that I had it on Dropbox and it was very heavy to download it. So as Bart said, I'm a clinical cardiologist. I work at the Brown Hospital. So I'm going to do a presentation that it's going to be a little bit different from the previous one because I'm going to explain physics in MRI but also why MRI and for the flow MRI is important for us in clinical cardiology. So, three more seconds. So the first question that we should answer is why flow imaging is important in cardiology? So why, most of you will be engineers. So why we need your support? Why we need flow in cardiology? So when we are trying to evaluate the severity of a valvular regurgitation, for example, a valvular stenosis in a patient that we have in our outpatient department, so most of the criteria that we have for the severity of disquantification of the regurgitation or stenosis are based on clinical flow. So, for example, we consider that a severe aortic regurgitation is when there is a regurgitant volume greater or higher than 60 milliliters per bit or the orifice of regurgitation is higher than 0.3 centimeters squared. So we need volumetric information in our cardiology department every day. So also once we have that information, we have the volumes of the regurgitation or the severity of the stenosis. We take these algorithms in clinical practice just to consider. So if we have a severe aortic regurgitation and the patient has symptoms, so we consider that the patient is ready for aortic valve replacement. So based on the information that we have from the echo, based on the information that we have from the MR and based on the patient that we are interviewing, so we decide if we have to operate or not to our patient. So, but all the volumes that we used to use were based on ecocardiography that has been the technique of choice that we have been using for a long time in the past and we are still using a lot in clinical practice. But the problem of ecocardiography is that we are assuming some anatomic patterns that they are not real. For example, in order to estimate, for example, the volume of the aortic regurgitation, what we do is we have to calculate the area of the outflow tract in the left ventricle. So we consider that the area of the outflow tract is totally circular but we know where we are using multimodality imaging that the area of the outflow tract is not circular, that it's more elliptical. So we are having some errors in the estimation of the volumes that maybe the information that we get from echo is not as accurate as we wanted to. So that's the reason why MR emerged as an important tool in order to solve these problems and to give us an accurate information about volumes and severity of regurgitation and also about velocities and flow. So what we have here is an MR sequence. So it's what we call phase contrast sequence. So this is an aortic at the aortic level. So this black image is the aortic flow. What we have here is just tracing the area around the flow as we can see here and just propagating all this ROI in all the different phases that we have in the cardiac cycle. We have a table like this where we have all the information. So we have all the total forward volume. We have the regurgitum fraction. So it's like 15% of the total volume that the stroke volume. So 15% of this volume is coming back to the left ventricle. So we are having lots of information just doing this trace. So just analyzing the information that we have for MRI. So we don't have to assume anatomic areas as we did in echo and all the calculations that we did with echo are more easy and we don't have to calculate all of them just using MR. So that's the reason that MR started to be the technique of choice in our clinical practice to evaluate volumes and fractions of regurgitation like for example as we have here. So it's much more reproducible and easier just to manage our patients. So what we do in MR is we use one sequence that is called like this is the phase-contrast sequence that what the sequence does is that it analyzes how the protons that are within the vessel change the phases and this phase is proportional to the velocity that the protons have. So for example we apply like two different gradients. We know the time that those gradients are applied. So we calculate how the proton has moved and this movement is how defaced and this defacing is proportional to the velocity that this proton has. So we can estimate using MR we can estimate the velocity of the protons that are just passing through one slice position as you can see here. So we can know the velocity and based on the velocity we can calculate the flow. So for example here what we used to do with MR was we analyzed one slice position so we selected we wanted to estimate for example the flow here so we decided to do a slice at this position. So we have an image like this. The aorta is here so this is the aorta. This is the ascending aorta, the aortic arch and the descending aorta here. So we have the aorta here and we can have all the velocity, the regurgitant flow in this slice here. But we can only analyze the flow that is going in two directions. So it's the through plane flow that is going forward direction or backward direction as you can see here. So based on this we can calculate the velocity of the protons that are across this aorta, this aorta, the lumen, but only just in one direction. Just the direction forward and backward. So this is an image that we have at the aortic valve. This is the aortic valve of the patient. This is the face contrast image. That's the image that we have. As you can see the flow is seen in black here and this is the anatomic image that we get also from the MR. And what we do is as I said before we have to select one plane or one area when we want to analyze the flow so we can do a slice here or a slice there or at the aortic valve so we have to decide when we want to know how's the flow there. So we select the plane and we do like an image like this and we can estimate as you can see here the flow, the velocity, maximum velocity, gradients, being gradient, maximum gradient, etc. But what we used to do is we select one slice position so the patient did an apnea and we get this information from this specific slice position. One of the characteristics of the face contrast sequences is that we have to previously select the maximum velocity that we expect that the patient is going to have at this specific point. For example, this is a patient with an aortic stenosis that means that the aortic valve is reduced, the orifice of the aortic valve is reduced and as you can see here we selected a velocity that is below the maximum velocity that the patient is having at the aortic valve. So as you can see here we see that there is a black flow, the flow is black but in the middle there is like a white flow that means that the velocity that we selected is not the correct one so we have to increase the velocity, we have to choose another velocity encoding just to make sure that we are depicting the best for the appropriate velocity that the patient has here. So one question that why don't we start using a big velocity encoding so that we don't have to change the velocity, the velocity that we are trying to imagine, we are not depicting the correct one so we have to do one slice position with for example 100 meters per second, 100 meters per second if the maximum velocity is higher so we have to choose another one so we have to increase it slowly until we get an image like this with no aliasing in the middle. The problem is that if we start using a high velocity what we get here is that we have a lot of noise in our flow so we don't have an accurate measurement of the maximum velocity and we don't have a great or an exact determination of the minimum velocity either so the thing is that the higher the velocity that we are using the more noise that we are having in our images. So as I said what we used to do was one apnea for our patient we had to select before when we were scanning the patient where we wanted to know the arctic flow or the velocity at one specific point and then we get one image, one only image with the velocity at this place but in the last five, six years 40 flow sequences have started so we have improved our MRI studies our flow MRI studies with this new sequence that the properties that this sequence is the first one is that it's volumetric so we are not acquiring just one slice position we are analyzing one volume and as you can see here we can acquire the whole aorta all the volume of the aorta and all the velocities inside the aorta this sequence requires synchronization so we will have all the different phases in the cardiac cycle so we can have the different flows at different parts of the cardiac cycle in the diastole, in the systole, in the diastole whatever we want the thing is that these sequences this sequence also is related to the velocity encoding so as I said before we have to previously know the maximum velocity that we are dealing in that patient because we have to select the correct maximum velocity so we have the formation from the echo or we have the formation from D to the MR we have to select this maximum velocity because if don't we will have aliasing in this MRI too and as I said it's a volumetric so we have a volume and all the information, all the velocities included in that volume as I said before with 2D MR what we used to have was only we could only analyze the direction of the flow so in one plane, for example in this one in the z plane but with MR, with 4D flow MR we also have the information that we can codify all different velocities in all different planes so we can have the information through plane so in the z plane but we can also have the information the direction of the velocity in the y plane and also in the x plane so we can decompose all the different components of all different vectors of the velocity within the vessel so when we have one one segment when we have one vector of the velocity within the vessel then we can decompose all the different components and we can know exactly the direction of this flow so as I said we are not acquiring one slice so we are acquiring one volume that as you can see here we have like a box where all the volume of in this case we are doing a 4D flow MR of the whole aorta so we have all the information of the aorta in this vessel here and then we can select whatever we want so we can do an slice here or there we have that volume and we can work with that volume as we want and the information that we have is what we have here so we have the velocity the encoding direction in plane that it's right to left anterior to posterior so that would be in this direction here all the through plane velocity that would be in this direction like the z plane and also we have an anatomical image as we can see here just to know where we are doing our slash position at this image here this is the pulmonary valve the pulmonary trunk and the the refurcation of the pulmonary vessels the ascending aorta and the descending aorta so the advantage of this sequence is that we have a volume we have all the velocities of this volume that we are working and then we can select the slash position that we want we can know all the volume all the velocities at the plane that we want to analyze so the image that we have is like this one so this is one patient that is a normal volunteer so we have all the velocities that are within this aortic volume this is the pulmonary the pulmonary trunk and the refurcation of the pulmonary so for example if we want to know the relationship in between the flow in the ascending aorta and the flow for example in the trunk of the pulmonary artery so we just do a slice at this position another slice at this position and we have all the information about velocities, flow gradients, so all all the information if we want to do another slice here or in a pulmonary trunk or refurcation or whenever we want and compare different ratios or velocities so we can select the position that we want so that's the advantage of 40 flow so we have all the information all the information in the volume and also we can analyze all the different direction of the different components of this flow one of the advantages is at the beginning one of the concepts that we have is well we are using 40 flow this is a different sequence from the previous one is this sequence the velocities and the flow that we have are comparable to the previous one to the 2D ones that we used for a long time so there is a first work that is here that compared how the velocities in 2D and 40 flow were and as you can see here the velocities are pretty comparable so the information that we are getting the values that we are getting are truly comparable with the previous one and these are the clinical indications that we have in current guidelines regarding the use of 40 flow so we can use for the flows in order to get the information of the valves in the heart so stenosis or regurgitation it's very useful for congenital complex congenital heart diseases and also when we have chants or we have collateral vessels because we have the volume and then we can compare the flow at different vessels or at different cavities so this is important when we have we don't know at the beginning all the information that we will use and we can get a volume and then analyze individually different vessels or different components and also it's very useful in patients with aortic disease diseases of the the aortic disease like aneurysm of aortic dissections so these are the clinical uses of 40 flow that we have in current guidelines in the heart there's not a lot of the uses of 40 flow in leth ventricle and in the heart is mostly used for research purposes so there are some clinical trials that they are trying to use how the complex flow within the leth ventricle can associate with the formation of thrombus in patients when the heart is enlarged and they have plotted like a dilated cardiomyopathy so there are some works based on leth ventricle but the most the most studied the most clinical application of 40 flow has been studying the aorta the aortic valve valvular heart diseases and also the aorta the whole aorta and the flow in the aorta so based on the main implication of the main applications of aortic the 40 flow in aorta so first of all we have I wanted just to remind you how the aorta how the whole aorta works so we know that when we have the systolic blood wave the first thing that happens is that we have the aorta what it produces is an expansion of the aorta what we call the aortic buffering that means that there is a systolic expansion of the aorta just to this all this flow that has been out of the leth ventricle and it's this process is mainly induced by elastin fibres and smoth muscle cells and then when the systolic happens after that we have the aortic reservoir phase that what it does is just try to couple all this flow distribute the flow within the whole aorta just to distribute it to the rest of the vessels to the rest of the body and that produces a normal wave propagation of the pulse wave velocity and the normal propagation of the flow within the aorta this is the normal physiology of the aorta but we know that there are some pathological issues that can interfere with these normal mechanisms of the aorta and as you can see here when we have mechanical or chemical stress like hypertension inflammation we have atherosclerosis that's going to interfere and that's going to alter the reparative process of the aortic wall so it's going to increase the extracellular matrix it's going to produce atherosclerosis it's going to increase the collagen and the calcification of the aortic wall and that for sure it's going to produce an increase in aortic stiffness and a decrease in the aortic compliance so what we are going to have is an alteration of the aortic buffering capacity and aortic reservoir capacity what are the mechanisms or why we have a mechanical or how are what are the causes of this alteration in the aortic wall but clinically we try to distinguish them in between genetics or classify them in between genetic causes inflammatory causes or induced by flow so the genetic one are the syndromes that are genetic like Marfan, Ehler Danlos, Lois Dietz they are like inflammatory diseases of the aorta like arthritis arthritis and induced by flow we have hypertension atherosclerosis, traumatic or patients with bicuspid aortic valve that they have like a mixed component in between genetic and due to flow classically we use different parameters just to know how the aorta works the stiffness of the aorta works so mainly we analyzed indirectly the presence of hypertrophy in the electrocardiogram or by echo we saw the thickening in the aortic wall or we have like different parameters but now we have lots of parameters derived from MRI and for the flow MRI so mainly sure you have analyzed or someone explained you how we know the formation and the mechanics of the heart, the muscle the left ventricle so we can analyze the deformation of the heart, we can analyze the strain the strain of the heart, the deformation the circumferential strain, the longitudinal strain the radial strain so now one of the advantages of 4D flow image and MR is that we can also analyze different patterns of parameters of the formation of the aorta as you can see here so the first parameter that we can analyze using MR is aortic distensibility that is like the radial distensibility of the aorta as you can see here in systole the the radium of the aorta increases and in diastole it decreases a little bit so we know for example that with different pathologies like for example in Marfan syndrome the distensibility of the aorta is is decreased so the aorta is more rigid the stiffness of the aorta have increased and also we can analyze for example the longitudinal deformation of the aorta we know that in diastole the aorta is like this but in systole there is a prominent displacement of the aortic annulus towards the apex of the left ventricle so as you can see here in diastole the aorta the position of the aorta is like this and in systole it moves towards the apex so we have an increase in the longitudinal deformation of the aorta and this deformation the longitudinal deformation of the aorta is based on the properties of the aorta but also in the mechanics of the left ventricle too classically we used how as you can see here this is a patient a normal patient a Marfan patient we have the aortic annulus here this is the ascending aorta we can see the left ventricle here and you can see how the the length of the aorta is a little bit based on the mechanics of the left ventricle so we used to analyze the longitudinal deformation of the aorta based on how the aortic annulus displaces in different views but now that we have for the flow and we have volumetric images in all different phases in the cardiac cycle we can also analyze the longitudinal strain of the aorta based on the volumetric changes of the aorta in different phases so we can see the changes in longitude that the aorta is having in sister Leanda Yasteli and we can analyze the strain of the aorta another parameter that we can analyze and it's very important in order to know the stiffness of the aorta or the elasticity, the sensibility of the aorta is what we call the pulse wave velocity this parameter reflects how the velocity of the arterial pulse propagates within the aorta so as you know we are analyzing velocities so we need a space and we need time so as we know those two different points, we know the velocity in one point, point number one and the velocity in point number two we know the time in between the transit time between this flow and this flow and we also now know the longitude in between or the separation of flow in between these two points will circulate the pulse wave velocity and we know that if the pulse wave velocity is increased so if there is an increase in pulse wave velocity that means that the aorta is rigid so the stiffness of the aorta is increased and we have like normal values, we can consider compared to normal values if the aorta of one of our patients is increased it's more rigid in between the normal range but also one of the things is that using for the flow as we we try to use a pulse wave velocity we only could analyze for example as we can see here the difference in two different points for example here one and two and if we needed the information for knowing the pulse wave velocity in another plane for example the aorta so we have to do another position, another slash position here and compare the distance in between these two different areas so we couldn't analyze all the different curves of the pulse wave velocity within the whole aorta so just could analyze one different slash position and we have to consider when we use 2DMR is that when we are acquiring one slash position the rate of the patient can change in another acquisition so maybe the different intervals of timing could be different so that was a limitation that we have to analyze the pulse wave velocity but using for the flow we have all the different planes of the aorta sending aorta sending aorta and we can have all the different curves and we can get the pulse wave velocity that is the pendant of that best fit in the pulse wave velocity in all the curves so now we can have a better and accurate pulse wave velocity curve that is based on all different planes in all in the whole aorta so we are having much more information and much more complete that we used to have before and we know that pulse wave velocity as I said it's a pattern that it has been considered the gold standard for aortic stiffness that we use in clinical practice so when we have an increase in the aortic stiffness we have an increased pulse wave velocity and there is a correlation in between the pulse wave velocity with all risk factors of the patient so patients with hypertension, old patients patients with hyper trillis eridemia, smokers males obese people so they have an increase in stiffness and they have an increase in the pulse wave velocity and also when there is atherosclerosis in the aorta as you can see here no plaque lipid plaque but an hyper ecogenic plaque that means that it's a more established plaque as we can see here the pulse wave velocity increases as atherosclerosis progresses it's important and it has been considered the gold standard for aortic stiffness because we have lots of studies this is just a review we have lots of studies that they state that the more rigid the higher the pulse wave velocity is so the more rigid the vessel is so the more risk factors or the more events that the patient is going to have so in terms of cardiovascular events mortality and all-cause mortality so this is a pattern that when we estimate this pattern in cardiology or in clinical practice is because we need it because it provides information to our patients in terms of that this is a patient with higher risk for cardiovascular events so now that we want that we have like a genetic inflammatory so that different factors can induce alteration in the aortic wall and this aortic wall increases its stiffness decreases the the compliance and that we have parameters and with different technologies but with MR and with 40 flow MR that we can estimate how the stiffness of the aorta is or how reduce the compliance so now we are going to analyze just a little bit why these changes in the aortic flow or in the aortic in the aortic wall induces changes in the components of the aortic wall and they are related to atherosclerosis so classically we know that we have flow in in a vessel when there is a normal flow when there is no plaque so we have a low a normal a laminar flow and there is a low shear stress but when we have an atherosclerotic plaque the flow the the lumen of the the vessel is reduced so we have an increase in the velocity and increase in the high shear stress but after the atherosclerotic plaque what we have is like a turbulent flow because of the flow has released after the atherosclerotic plaque and we have oscillatory shear stress so we know that this oscillatory shear stress when this oscillatory oscillatory is low flow or shear stress happens they are going to activate different mechanisms of the aortic wall in terms of like metalloproteinases and all these molecular changes, monocyt activation procoagulant a procoagulant state so they are going to happen different mechanisms in the they are going to induce some changes in the aortic wall that they are going to start the atherosclerotic process as you can see here this is a endothelial image of a patient a normal patient or a patient with a normal flow with a low shear stress and here we have the endothelium there is a disarray in all the endothelial cells when we have an oscillatory slow flow and now we using for the flow we can also combine the information of the flow so we can analyze how the flow distributes within the aorta and this can be also translated in a map as you can see here that can show us the wall shear stress in the aortic wall so you can see here there is an increase in the wall shear stress at this area here there is a lot of turbulence of the flow at this part here we will see more examples later and also we can also analyze where are the places or where we localize areas where there is a higher turbulent flow not in terms of wall shear stress but when there is an oscillatory changes in the turbulent so what is called the oscillatory shear stress so we can also analyze areas where there is oscillatory shear stress we can also estimate the oscillatory shear index and we can analyze areas where there is this increases values of the oscillatory shear index so these are maps that we get from fro the flow images we can now we can get images when we can know in this patient for example where are the areas of high wall shear stress and these are areas that they are going to increase the size and this patient with different areas of increased wall shear stress is more prone to dilate the aortic wall and we can also have different maps with oscillatory shear index so that means that also patients with an increased value of oscillatory shear index has more probabilities to atherosclerosis and also aortic dilation you know better than me what wall shear stress is that you know that it's the displacement of the different components of the different layers of the aortic wall so as you can see here and the higher the wall shear stress is the higher that the tension of the aortic wall is and then the more probability to enlarge or to have that much of the aortic wall and increase the produce dilation in the aortic wall so this is what the wall shear stress is as you can see here this is a point here and you can see that the wall shear stress is just the displacement of the different layers of the aortic wall and it's important to note that the wall shear stress is based on two different components we have the longitudinal wall shear stress there are what we call the axial wall shear stress that is the wall shear stress produced in this direction in the longitudinal direction and we also have another component of the wall shear stress that it's called the circumferential component of the wall shear stress that it's produced because of the presence of turbulence of flow where we have flow that it's going not only in the laminar direction but also in a circular distribution as you can imagine wall shear stress is going to be low when we have a laminar flow but when we have complex flow when we have turbulences so we are going to increase the circumferential component of the wall shear stress and this can also produce alterations in the aortic wall and aortic dilation so here is an example of a complex flow using for the flow MR as you can see here we have like flow that is going up in this direction forward in this direction but also we have like flow that is going in it's going in different backwards in a backward direction as you can see here we have flow up but also flow that is going backwards and then up again so we are having like turbulent flow here that this flow that this turbulent flow it's going to produce an increase in the oscillatory shear index it's going to increase the wall shear stress index and it's going to produce enlargement of the aortic wall so that's be an important component of aortic dilation also we can analyze as we can as I said before we have like flow that it's in a forward direction but also we can analyze the flow that it's coming backwards and what we call the regurgitan fraction so it's like the fraction that it's even in systole is the flow that goes in an opposite direction in the lumen so and this flow the presence of backward flow the more backward flow that we have in systole that means that the most probability the more likely is the aorta to enlarge and this is also related to enlargement so the more enlarged the aorta is the more regurgitan flow in systole the aorta has and we know from different histologic papers this is one important paper that it was based in patients with bicuspid aortic valve yet here is that the presence of an asymmetrical wall shear stress so again pointing out the importance of wall shear stress in atherosclerosis or in the pathogenesis of aneurysmal of the aortic of the aorta production so when we have an asymmetric and an increased wall shear stress what it's produced when we have an elevated wall shear stress it's a reduction in the elastin fibres and increase in the collagen fibres and increase in the metalloprotein axis and also enlargement of the aortic wall so first of all these complex flows using for dmr have been described in patients with aneurysm of the ascending aorta so as you can see here there is a normal patient with no turbulent flow there is all laminar flow in the ascending aorta but as you can see here a patient with an enlarged ascending aorta as you can see here there are turbulent flow in the ascending aorta so that's related to the dilation and increasing wall shear stress adlation of the ascending aorta and also for the flow MR has been used also in patients with aortic dissection that even though that we have lower flows in the false lumen what we can see here is the false lumen is also associated with turbulent flow these areas where the turbulent flow is higher is associated with areas with increase in the dilation of the aorta the most important thing of the most commonly studied process in cardiology so far because I said that for the flow MR is quite recent so it has been used we have been using for the flow MR in recent years so the most the pathology that has been more widely studied using for the flow has been the bicuspid aortic valve we know that you know that the aortic valve is formed by three different casps but there are some patients that they instead of having three different casps they have two different casps so and this is associated with an asymmetrical opening of the aortic valve and because of the asymmetry in the opening of the aortic valve what we have is more probability to have complex flow and at the beginning what one of the first studies showed that patients with bicuspid aortic flow bicuspid aortic valve they have more complex flow compared to normal subjects that they have a more normal distribution and also they also have a different pattern of waltz stress in the ascending aorta these cubes represent the ascending aorta and as you can see here there is like an asymmetric increases in the areas of waltz stress in this part here lower waltz stress in this area here so we have like different components of waltz stress then we try to identify the presence of the different morphotypes of aortic valve how they change the flow in the ascending aorta so we have like different morphotypes of aortic valve they can generate different patterns of flow and for that reason as we will see later different morphologies of ascending aorta so different patterns of dilation and the only the first paper that established a little bit the correlation between the turbulent flow with aorta dilation was this one but it's from 2012 as I said we are using recently for the flow MRI and this study was based just in 13 patients with bicuspid aortic valve and 12 patients with tricuspid aortic valve and we saw that progressive dilation was higher in patients with bicuspid aortic valve was higher in patients with eccentric flow and correlated with the displacement the centricity of the aortic flow so we know from this study that at least in a small series of patients that the more complex flow the more severity turbulent flow the higher eccentric flow the more probability the patient has to enlarge the ascending aorta or the aortic diameters based on that we started to work with 40 flow 2 or 3 years ago we have like different papers that some are under review and some of them will be published sent in recent next month or before summer so we studied the different components of 40 flow in more than 100 patients with bicuspid aortic valve with not extreme ascending aorta dilation as you can see here so this is a patient and as we can see here at the beginning is that this is a normal patient that you can see that the isocenter of the flow is very central but when we have patients with bicuspid aortic valve we can see that there is an eccentric flow more anterior in one of the morphotypes of bicuspid aortic valve what we call and more posterior in patients with type 2 and as we can see here we correlate it we analyze the different patterns of the flow in ascending aorta as you can see here this is a patient with a morphotype 1 so and as we can see here the flow is eccentric we have turbulent flow here but the flow goes all the time in the anterior wall of the ascending aorta as you can see here this is the maximum flow that it's related here so this flow starts to be higher in the aortic root that's why as we will see here patients with morphotype 1 also increases the aortic root diameter because the flow goes in the direction at the aortic root and as you can see here all the flow goes to the anterior wall but in another subtype of patients with bicuspid aortic valve is what we call morphotype 2 so what we saw here is that at the beginning so in the aortic root the flow starts its posterior so it's more posterior than anterior and then rotates from posterior to anterior until the ascending aorta where all the flow becomes anterior as you can see here it starts posterior and then shifts to the anterior part and at the end of the ascending aorta the flow is totally anterior so those patients won't have an increase in the size of the aortic root but they will enlarge the ascending aorta distally before the aortic arch and as we can see here we can have a 3D representation of the how are the components of the wall shear stress the axial wall shear stress that I said before and the circumferential wall shear stress that is involved with the turbulent and the circular flow and as we can see here the wall shear stress is maximum and is higher in all the ascending aorta and in the anterior wall when we have a bicuspid type 1 and it's posterior and then anterior when we have a patient with type 2 bicuspid aortic valve and also because of that shift in the flow in patients with type 2 bicuspid aortic valve the circular components and the circumferential wall shear stress is increased in patients with type 2 bicuspid aortic valve higher than patients with type 1 aortic valve so as I said before there are some patients that they enlarge the aortic root as you can see here so this is a bicuspid aortic valve patient with an enlarged aortic root enlargement the ascending aorta is not enlarged and as you can see here the flow at this area is very higher this is a bicuspid aortic one bicuspid aortic valve so the flow is mostly anterior and also there is turbulent flow also in the aortic root that it's related with this increase in size in the aortic root and this is a type 2 patient that has an increase in the volume in the ascending aorta and as you can see here the flow starts more posterior and then shifts to anterior and that's why the reason they increase mostly the diameters in the ascending aorta we analyze the different components of the associations of the different morphotypes of aortic dilation we can see that patients with aortic root the morphotype, the ones that enlarge mostly the aortic root they have less turbulent flow compared with patients that they increase the size in the ascending aorta that they have more turbulent flow and also more reversal flow compared to normal patients of type 1 patients with the morphotype the root morphotype when we analyze the different components you can see here that as I said patients with enlargement in the ascending aorta they have more circumferential wall shear stress they have more normal values in the aortic root compared to patients patients that enlarge the aortic root that they have more values higher values in the aortic root and lower components of circumferential wall shear stress so just to conclude for the flow sequences constitute a useful alternative to quantify flow especially in case of complex cardiopathies dissection by cuspid aortic valve congenital heart diseases they present an excellent correlation with 2D phase contrast sequences with the advantage that they can perform flow study at every aortic segment because we have a whole volume of the aorta so we can analyze the flow whenever we want they allow a detailed study of complex flow and their functional repercussion in arterial structures and they allow a greater knowledge of aortic pathophysiology as I showed you before however at present it's post-processing it's complex requires experience qualified personnel team and it's very tight consuming because we don't have lots of software so far to analyze all these parameters so most of the parameters that we are analyzing are based on math lab and different software that engineers usually use and so far as these are new technologies new techniques we lack we don't have many prospective studies that determine the real pronostic impact of these variables that are being by 4D flow in our patients that for sure that in some years we will have more data just to correlate what we have at the beginning so these parameters that are increased with 4D flow MR and the correlation with events and also the aneurysm formation of aorta so thank you very much thank you very much for this extensive overview just maybe a bit of a practical question that this is like a complex acquisition is like maybe you can elaborate a little bit and how many patients can you do it and how much time does it take do you more regularly still use the 2D flow or in the end do you rely on ultrasound what's the practicalities of things so the practical thing is that we always manage our patients based of cardiac ultrasound that's for sure so we are analyzing we are using 4D flow MR just for research purposes or when we have doubts there are some patients that we have doubts for example in quantifying the aorta regurgitation because there is an excentrical flow we are not very precise with echo so in those patients we perform a CMR just to quantify the real regurgitant volume so we use it in complex cases that we have doubts in echo so mostly echo when we have doubts MR compared one we have selected our patient and we are doing a CMR in that patient because we have doubts in echo so we usually start doing is 2D MR 2D phase contrast because we need to know very precisely how is the maximum velocity so we have that velocity from the echo report or we have doubts we are doing a 2D acquisition at the aortic valve for example because we need to know the maximum velocity because it's the encoding velocity what I explained before that it's very useful to know because if we are using a low threshold of velocity we will have aliasing and the velocity the values won't be real so we can we do a 4D flow so it's an acquisition the advantage of that is that the patient is free breathing so it lasts the whole acquisition is like 8-10 minutes but the patient they don't have to collaborate at this time they only have to lay down breathe normally and it's more comfortable for them compared to the 2D acquisition that they have to collaborate they have to hold it breathe they have to hold it for 10-15 seconds and again and again every slice that we have to do so it's an apnea that the patient has to do so it's more stressful for the patients the 2D acquisition than the 3D and in total how much time would it take to do a full acquisition of a patient we are using a strict protocol and it's about 40 minutes the whole acquisition since the patient starts we have to take into account that the patient first comes to the MR room they have to lay down we put an IV for the contrast in some cases so all the process it's about 40-45 minutes and what about availability of the 40 flow sequences is it available on every scanner do you need a special one do you need special sequences the thing is that you need a special sequence you cannot you can't acquire a 40 flow volume a 44 acquisition if you don't have that sequence and most of the softwares of the MR scans at this time they don't have it so you have to to have an agreement with the company just they can give you the sequence mainly for research purposes it's not already commercial so most of the for example I don't know how many centers in Barcelona or in Spain are working with 40 flow but we are not many in the whole country working with 40 flow I think here in Barcelona there are two centers us and the people from Sampao the ones that are working with 40 flow so it's not extremely popular and you say the post processing is also complex and how long would it take there is it like 10 minutes of processing or 10 days of processing the thing is that you have like a learning curve so when you start you start everything so with the process you are you develop tools that make this post processing more automatic so Lydia started doing that that for sure she spent more than 1 hour per patient for sure so she can give you more information about that if you want to say something and now half an hour so yeah we started and how important is it also to have the anatomical information and for example have a segmentation of the aorta? Yeah so the anatomical information it's very important because what we have here is that patients with 40 flow they don't have the when we are analyzing dissections or bicuspid artery valves aorta male that's what we are studying so far is that what happens is that there is a symmetry of the components of the water stress the flow is directly to one direction so we need to know the anatomical references in order to know that the flow is in the anterior wall or is in the right part of the aorta so we need the all the anatomic references and the flow because we will know where the symmetry is based on the anatomic references yeah. It's a question there. Hi thank you for the presentation I have two questions. Both questions are related with the wall shear stress one of the first one is you talk about the wall shear stress how is the resolution close to the wall and how is accurate your segmentation because in the MRI when you segment the wall it's not quite well defined so I don't know how you compute this wall shear stress because it's just the gradient of the plotity and the second one is related with the OSI this is the temporal I don't know I see correctly the wall is the move is rigid so how is just the wall shear stress the wall is move of the aorta and if you I suppose if you want to compute the OSI value okay it's just along the cardiac cycle and the wall is move so I don't know see if the wall is move in the video I don't know just to know how to compute this the values for the first question I will require the engineers because they know about segmentation much more than I do what we do for wall shear stress and for oscillatory shear index we give the most the most information that we need is what is happening in the systolic phase when the flow is moving forward so we use the peak of systolic the systolic flow just to calculate the oscillatory shear index and the wall shear stress but because of the noise and just to mitigate this phenomenon what it's considered or well established in the community that we are using for the flow is just analysed also not only the peak but also the previous one and also the different cycles I mean one previous and one posterior and just to make a mean an average of the values just to know the wall shear stress the maximum wall shear stress and the oscillatory shear index so mostly the maps that we are getting are systolic or an average of the systolic so previous and posterior so the systolic more or less the systolic phase okay but how is the resolution close to the wall because okay I can answer the resolution in general it's 2.5 millimeter and box so it's a cube and this is not very good for wall shear stress computation because it's being a derivative a special derivative we all know that it depends on the resolution but about comparative study in clinical setting you the main thing you know as long as it's not becoming a clinical tool is a relative so if you use the same sequence you will get the same problem and will propagate the same but in general we use spline to get read of a lot of noise close to the wall in general we use common common of the same yes function to velocity along the wall in the radial direction so we approximated the point we have as close to the wall with spline or also other equation but I repeat the point here is that being a research we don't really need the absolute value but much more relative so we have different patient with different pathology what we are looking for it's much more how different phenotypes or morphotype or pathology relate each other so the day that this will become it does a clinical tool there will be need a consensus on how to behave in this aspect I understand what you say but the thing is for example you have a method to compute the worst stress okay maybe in other hospital and other tools they have another method to compute the worst stress there are consensus about that so how for example the data you have in the Balder Braun can you compare versus against sample for example yeah that's a problem that we are having there we know that different machines they have the different sequence the different sequence they have different values we know that there is no consensus about normal values just because of these irregularities for sure but that's why we are relying more mostly in maps I mean or in a general representation of what is happening because we don't exactly want the exact value of this parameter so we want to know that for example that an increase in the circumferential worst stress we are very sure that an increase in circumferential more than the axial worst stress it's important and patients with an increase in the worst stress in every part proximal aorta or distal aorta so they are going to enlarge the aorta much more than patients with lower values of worst stress and mostly the results that we are getting mostly based on these are regularities asymmetries different patterns much more that in the clinical value that we don't get that because of these irregularities and these inhomogenities that we have in different vendors different machines different yeah any other questions if not then it's lunchtime it was a long morning so for the ones that doing the hands on please come back at 2.45 and it's in the rooms of yesterday additionally the ones that were doing the lumped model for the fetal that will be in room 30 but there will be indications there


And in regards to dividing by zero, take a look at this thing. Here, what's 1 divided by 1? And then go 1 divided by 0.1. And then 1 divided by 0.01. And then 1 divided by 0.001. And continue this process. And by the way, I think the third video I ever put out was talking about this, right? Continue the same process until you get 1 divided by 0.000000. And just continue it all, continue it all, 1. You're going to get a huge number, huge number, right? And when you get that huge number, consider this. What if this was 0? 1 divided by 0 just becomes, it explodes. Okay. Now, if you want a video talking about this, and this is one of the questions that, 0, boom. Let's see if it's going to pop up as one of the language. Let me bring it up. 0 language. Oh, come on. Okay, I got to go to my playlist and grab it. Dun, dun, dun, dun, dun. Language of mathematics. Check out this video, right? Now, when I put out this video, there's a reason I put out this video, right? To answer your question about regarding dividing by 0. But this video is one of the math videos that gets the least amount of love from mathematicians, right? People that know mathematics. Because their comments was, gee, Joe, you can't do this, this is wrong, right? Like literally, they would say, you can't do this, this is wrong. But they don't fail to understand that this is a video to answer, to deal with a problem that some people have and our education system has in regards to dividing by 0, okay? So there was a lot of haters that came on there, oh, this is wrong, this is wrong, this doesn't make sense, mathematics, because you can't cross multiply this thing and this thing and this thing. Because if you do this, 1 divided by 0, I did this, equals infinity, right? And they said infinity is not a real number. Well, infinity you can think of, I think of infinity in two different ways. I think of infinity as counting forever, right? Forever, forever, okay? And the other way I think of infinity is the universe explodes. And what I ended up doing with this in that video, I said cross multiply this up. That goes up there, that goes up there, so 1 divided by infinity is 0, right? 1 divided by the biggest number you can think of is approximately 0. People are like, oh, you can't do that, you can't do the cross one, because infinity is not a number, blah, blah, blah, blah, blah, blah. I'm like, dude, you guys have never taught high school mathematics. You guys are talking about mathematics at a university level, dealing with calculus and stuff like this. When people are trying to wrap their heads around the concept of dividing by 0, it is important to break it down to something simple like this, to show people what the problem is. So take that video with a grain of salt, but it really does a good job at explaining why we can't divide by 0, okay?


All right. Hello. This is Kelsey Hightower here, and I'm going to be moderating the CNCF on-demand webinar. Today, we're going to be talking about VPC networking beyond the Cloud. Now, why is VPC so important? For the last seven years, as you all may know, I've been at Google Cloud, and I've had a lot of jobs before then, and I know what it's like to work inside of a data center. You rack and stack servers, you create your leaf and spine network, you got routers, you got top of rack switches, and I've made my fair share of Cat5 cables. In that architecture, automation is key, like I get it. We need to provision all of those ports, maybe you're setting up VLANs, but for the most part, a lot of our automation tools are doing a one-to-one mapping of the standard configuration. Now, if you're like me and you have some experience in the Cloud, things are very different when you get to the Cloud. There is no concept of ports and VLANs. Those things are hidden from you, and instead, you get a new abstraction, and for years, we've just been thinking about that abstraction as VPC. When you create a VM, you just attach it to a VPC, you create a Kubernetes cluster, again, you just attach it to a VPC, and typically that VPC is going to give you an IP address and deal with any other routing concerns that you may have. When I think back to people coming from on-prem and to the Cloud, one of the big differences that we actually don't talk about enough, we always talk about the differences in compute and VMs, maybe even the differences in load balancers and security things like IAM, but hardly do we ever talk about what I think is probably one of the most important components. That's that VPC abstraction that's just let us focus on our apps, our workloads, and our applications. So to help me really dive into is this even possible, I want to introduce Alex from NetRisk to give us a deep dive of his company, his product, and their ambition to bring VPC anywhere, including possibly your data center. With that, we welcome Alex to the stage. Hi, Kelsi. Hi, everyone. Thanks for this nice introduction. So my background is many years in traditional network engineering, almost like 20 years designing, architecting, large-scale data center networks.  And I'd like to start with the evolution of networking. So networking kind of started with CLI, and then over time we've seen SDN, software-defined networking, trying to make it kind of more programmatic for engineers to consume networking. And the next one was intent-based networking, pretty recently. The thing is that all these technologies, they are amazing for traditional data center and telco environments. But when you do need to do these cloud-native applications, DevOps methodologies, you need VPC. Those technologies are not fundamentally made for this. VPC is what we are seeing in the cloud, it's VPC is what we need. And if we look at the compute infrastructure market growth, we can see that not only public cloud is growing, but also bare metal cloud market is growing, edge growing like crazy, and even traditional data center market is growing. Why is this happening is because we need lots of apps. We have lots of data, we want apps for everything and anything. Although most of the apps go to public cloud, it's not that public cloud is not a one size fits all kind of solution. Because in some cases, regulations require us to take some apps elsewhere. In some cases, it's a high cost, especially at scale. And in some cases, some applications do require technical requirements like latency, like machine learning applications, like applications dealing with transient data. So my main point is that applications are highly distributed. We have lots of edge use cases. This is how things are today and this is how things will be always. Some applications will be on public cloud, some applications will be on bare metal cloud, some applications will be on edge, and some applications will be in traditional data center. Now, this means that engineers have to deal, have to deploy maintenance scale applications in all these four types of environments. And in public cloud, that's fairly, it's fairly convenient to do things programmatically. Because of VPC, it's declarative, it's quick and safe, it's kind of designed to kind of help engineers to be insanely great. I even think that cloud popularity is very much attributed to VPC. VPC kind of enabled public cloud. And when we think about our other environments, bare metal cloud, edge computer, data center, those environments are based on traditional network operations model. There's a lot of complexity at best. There's some kind of homegrown solution, which is different from organization to organization. And we still are seeing lots of silos, like DevOps engineers, NetOps engineers, network engineers kind of take a lot of time and it's kind of hard. So we have started NetRest to address this problem. To create a software that brings VPC networking everywhere, to our bare metal cloud, to edge compute and traditional data center. To make both things look like VPC and enable engineers to have kind of similar operational model in both environments. Look at this, this is what networking looks like in Amazon AWS and it's very similar in any public cloud provider. And this is what networking looks like in physical data center. You know, DevOps engineers don't need another API. DevOps engineers, they need a VPC type networking for on-prem. So basically, this is what we're trying to do. We're trying to take that physical network and make it look like very much like VPC. So here's the concept. We have this thing called SoftGate, which is, you can think about it like a VPC gateway. It's a Linux machine that is running FRR, WireGuard, different Linux networking tools and software, mainly open source. NetRest SoftGate sits on top of any physical network. It's just a software, just a machine. You can have that machine in any Cisco network environment, Juniper in a bare metal cloud like in Equinix, doesn't really matter. So that's the machine which does packet forwarding. And then there's this NetRest controller, which has web console, which is very similar to public cloud that has declarative mindset, has, of course, Terraform integration, Kubernetes and REST API. But the idea is that you configure, you deal with this controller, and controller automatically programs VPC gateway, SoftGate nodes, to make network work. And we will see how this works soon in action. All right, this is perfect overview. And I love that image of that telco closet where all the wires are hanging. I'm pretty sure people listening to this or watching this right now are probably responsible for creating that mess. And we all know the value of abstractions. And I think you really dial it in when we start to think about taking all those components. I'm going to remind everyone, all of those components are necessary if you want a real working network. But what isn't necessary is to leak that complexity to everyone else. So having that VPC abstraction layer that gets us back to kind of simple primitives that we can actually use with our networks. Now, one thing I asked before we get into this demo was let's not just show the VPC and a bunch of IP addresses. I really want to call out very common infrastructures.  And I know how challenging that can be, especially during my days at CoreOS where we were really trying to give people a bunch of nodes and they had to go figure out how to integrate it into their networking. Kubernetes-based networking has always been a challenge in most of those traditional environments. So maybe you can walk me through kind of this diagram of the setup and maybe let's try to educate those coming from a traditional networking background and maybe people who are unfamiliar with most networking architectures that are out there. Yeah, sure. So for this session, we've created this environment where we took a traditional network. So basically a Cisco switch in the middle. We have connected three physical machines for where we will run our Ranger harvester hypervisor nodes. We have connected two other physical machines for a SoftGate 1, SoftGate 2. Those will be highly available VPC gateways. We have one more machine where we run two controllers, NetRisk controller and Rancher controller. Controller itself is just a K3S cluster. So you can easily run two controllers on the same machine. And we have this internet connectivity. Now this internet connectivity can be a physical cable coming from the ISP with a range of IP addresses and physically plugged into that Cisco switch. That can be a cable coming from, if it's a brownfield environment that can be a cable coming from traditional routers from enterprise border routers. Doesn't really matter. We just need some sort of internet connectivity to peer our VPC network with the rest of the world. Now this thing is entirely based on standard protocols.  We could have connected bare metal nodes. Just to keep it simple, we will stick to this three nodes for compute, two nodes for socket and one node for controller. But this can basically scale to whatever scale. Yeah, so I think if I were to summarize and correct me, we're wrong here. If I were to walk into an existing data center and I look to my left, there's some NetApp storage, some VMware HP blade chassis and all that is working fine, right? And I look at the top of that rack, there's probably a Cisco or Juniper switch or router combination. And so everything is working. That's what we mean by brownfield. Like things are already there. You're not starting from scratch. And then I decide, you know what? I wanna give this whole cloud native thing a try. Maybe I'm gonna go buy some new hardware and let's walk through this diagram. I get a rack right next to this other rack. And instead of going out and buying very expensive networking gear, I go get some standard maybe network ready commodity hardware. I racked two of them in the rack. So at the top, you have the two. I get that uplink cable from my network team that's ready to go. It's live. And I plug it into one of the soft gates. The next thing I'm doing is I'm racking maybe a couple of those bare metal or whatever servers that I have. And then maybe I just do another one just to host that rancher and NETRAS controller set. So if I step back and look at this rack, I have this kind of clean setup of, you know, dedicated worker nodes, controller that will be the orchestration layer for the other ones and two commodity network devices. And at this point, I guess, I just need to get the software installed to make all of this come alive. Is that kind of an accurate description of someone that was kind of rolling this together with their own machines in an arm premise data center? Yeah, that's very close to how people usually test this. And in some cases, you can have like a rake of kind of new equipment. You can always peer that with existing network. That's one way to go. Another way is like even if it's like a trial and if you don't really want to make a lot of changes, if it's just an experiment, do I want this solution? I don't know. I want to try, right?  You can go walk to your infrastructure team and ask for five, six servers, blank servers, where you will install operating systems. And you will need to ask your networking team to allocate you a range of DLAN IDs. DLAN IDs that will not conflict, will not overlap with other things on the network. And I can actually show then. So this is NetRis controller graphical user interface.  And this is default configuration. I didn't change anything here. You can see it says VLAN range 700 to 900. This means that in this case, NetRis will stick to using only these VLAN IDs. But if your network team is happy with a different range, that's totally fine. Just edit and type there the right range. So that's it. Basically, VPC services will stick to using these VLAN IDs. Whenever traffic exchanges happening between SoftGate One, for example, and Harvester 3, in the middle, it will be encapsulated using one of these VLAN IDs. And that's how traffic will pass through existing enterprise switch without requiring network team to make big changes. That's the whole idea. For every service, you only deal with SoftGate, with NetRis, with components that are plugged into VPC. But the moment VPC traffic needs to travel the traditional network, it encapsulates into one VLAN ID, goes through that network, and then decapsulates back. So look, we already jumped into the demo. I think we just pop over there and really go through this. So we just talked about kind of that base install, hardware is now mounted. We got our configuration in place. So now it's like, when I go to a cloud provider and you had a nice screenshot in the presentation, typically when I create a VPC, I tend to be presented with like a list of subnets that I can choose, either for VMs or various clusters that I want to attach to them. Maybe you walk me through, what does that look like from this perspective? Yeah, that's a great question. So there's this IPAM part where all the IP addresses are kind of registered. And this, you can see this list of private IP addresses, slash 20s, those are by default configured there, created there, I didn't create them. And whenever I want to create a new network, new virtual network, I can use one of these slash 20 IP addresses. Now if we look at the, I have created few networks to make this whole thing work, but we will create a couple of new networks soon. So the very first network is this network called hypervisor, so VNet. We call them VNet, virtual network. And we can see it is using this subnet from that list, this slash 20. This is where a ranger, harvester hypervisors are living. First, second, third, and you can see that those machines have received IP address from that network. That's, sorry, these three machines. But they also need to have some kind of a gateway, which is soft gate one, soft gate two, physically. And we can see that in our inventory, so gate one, so gate two, they're green. We can see traffic, memory and stuff utilization. But the nice thing is all this is happening behind the scenes. I didn't configure these things. What I did, I have only created this VNet, attach that IP address. And that's it, my ranger got this, my ranger hypervisors got this minimal connectivity so nodes can talk to each other, can reach out to controller, and make the cluster work. So it looks pretty straightforward. I create a VPC, I get a range of subnets, then I can come over here and allocate any of those ranges, like you showed earlier, those hypervisors are going to the low level nodes, but you were in harvester. So do we have to tell harvester anything about this network topology? Like how does it know that these networks is something that it should be using? Is there any configuration that needs to be done on the harvester side? And I'm assuming harvester is this thing that helps us provision things. So is there anything that I have to plug in on the harvester side to tell it about these subnets at all? So I have one service, one Kubernetes cluster called Kubernetes Prod1 that's up and running there. But let's create one more, let's create a new one. So I will describe the process and what's happening behind the scenes. Let's say we want to create a Kubernetes test. I select the site, we only have single region in this case. We attribute this to DevOps team and we pick one, the next available range of IP addresses, next slash 20, that's available. VLAN ID, we leave it assigned automatically so NetRis will choose one of the available VLAN IDs. We click add, now this is provisioning, it will finish soon. So everything starts from creating the VNet from here. Now when this is provisioned, we need to create a network inside harvester. So I will go to home and we'll walk step by step. So I go to virtualization manager, then harvester cluster, advanced networks. And this is the, you can see network that I've added before but now I'm going to add a new one. I paste the name here and I need this VLAN ID that NetRis has generated to type the same VLAN ID here, 703. So now both end points, they know which VLAN ID to use. So traffic reached the right place. We click create. If I'm looking at this correctly, this feels like the same flow you typically do with like a VMware setup, right? Like if I bring in exxi, I have to bring in this networking information. So it sounds like harvester is like this true hypervisor layer that's going to let us create VMs or whatever. And this is where we plug in those network settings. Yeah, absolutely. The same flow would be if you do with the VMware. Okay, now at this point, when we have the network ready and now we can go to cluster management and we can try to create a new cluster. Kubernetes test. Let's ask for three machines. Default namespace. Now I'm going to tell a rancher which network to use because now there are both networks available and here's the name for that new network. Okay. Now, while that's creating, this feels a very similar to like an EKS or AKS or GKE workflow, right? You come here and I'm assuming harvester is doing the hard work of creating the necessary VMs, programming them to be on the right network. In this case, this VLAN ID, tagging all of the network traffic. So as it flows through, all the intermediate components will do the right thing in terms of handling those network packets and giving me this feel of like, hey, as long as you have a network in place, ideally you will have the ability to create clusters and just attach them to the network that you've assigned. True. Why are we getting this error? Let's refresh the interface, maybe. Seems like some kind of front-end error. But it's actually creating. It's actually starting the process. Well, we'll do it. We'll just leave that for feedback for the harvester team. And like all good demos, it looks like we already have a cluster that's going. So I'm pretty sure I can imagine how that will be provisioned. There'll be some NCD, there'll be some worker nodes. And then ideally, you'll probably be able to pull down a Kube config. Is there an ability to get a Kube config from that prod one cluster up there while we're waiting for this other one to finish? Absolutely. We can just quickly check one thing. We can go to harvester for one moment and see what's happening underneath. If we click on virtual machines, all right. We can see that these three virtual machines have created like two minutes ago. We can see that they have even received this IP addresses automatically. And those are the right IP addresses that we have selected here. We didn't tell this information to harvester. This just happens automatically. Okay, so going back to cluster. Now I'm assuming VMs are being installed and Kubernetes is being installed, but that takes some time.  And totally, we can download Kube config here for the first cluster. And I can do... So I guess at this point, you're going to configure your Kube config with those credentials you've just downloaded so that you can actually interact with it via Kube C tail. So for those probably looking at this, this is an easy way to actually deal with multiple clusters, especially ones that you just created. And you want to make sure that the Kube C tail is pointing to that set. Yep. And it is responding. Six nodes are up and running. Now, so what does this look like on the network side? So Harvester is using that VLAN or that VPC that we carved out, or at least a subnet from that VPC that's kind of represented as that VLAN. So look, Harvester knows all these things, Kubernetes knows all these things, but I'm interested to see what it looks like from the Netris console, like people that are managing the network, what do they see? So that's a good question. And to your point, people that are managing the traditional network, they in from their perspective, these are just some packets going back and forth. They don't know any of these details. We're not disturbing them. They are not disturbing this VPC. Everyone are happy. Now from Netris console, from Netris web console perspective, well, this cluster is up and running. So obviously cluster has at least connectivity with the Rancher controller. That's how Rancher works. Cluster needs to access their controller. But there's also this other component of Netris operator, which I, to save everyone's time, I have previously installed it already. Here is it, a Netris operator that's running. So this operator is talking to Netris controller. It's authenticated with credentials. And now if I deploy an application in Kubernetes, which is using a service of type load balancer, for example, Netris controller will be able to understand this. Let me actually show this. This is layer for load balancer, kind of like elastic load balancer functionality in Netris. And we can see that nothing is there. We could create one using web console. We could pick protocol. We could enable health checks and type in backend IP addresses. In this case, this would work just a regular load balancer. But in this case, we can actually deploy application. I have this basic application here, pod info that is using service of type load balancer. Let's try to deploy it. And before you do that, I think it's important to go back to that pod info and let's explain something to folks really quickly. So there's gonna be a lot of people that are new to Kubernetes that are coming to this. There's gonna be people that are experienced with Kubernetes. Maybe we go back to that config really quick and I can see at the top, things will be provisioning. But let's go look at the pod info for one more second. I think what you're kind of highlighting here is that given that that controller is there, we see that when you create this service type load balancer, what's happening is it feels like you're doing the integration work on the natural side, meaning that you're dealing with whatever's required to provide the IP address, the load balancer service, the service discovery integration, pulling that IP information up, there you go, you can see it there, pulling the IP information from Kubernetes. So I guess a lot of people, if you've ever used any of the cloud services before, this would be the equivalent of like a network layer, load balancer, right? And you can send traffic directly to these pods, but I think it also shows off the first class integration here. You don't have to come to this console and then pop back to Kubernetes. You can keep your normal Kubernetes workflow, put everything in the manifest, use native Kubernetes ways of articulating things like type load balancer, and that's enough information for the Netrous Controller to take over and pull in that config and be responsible for creating the network services required to make it work, just like people would experience an other fully managed kind of Kubernetes environment. So I think that part is really important to call out to show people that, hey, the goal is, once you have these abstractions, so that people can just ignore the undertone and focus on their normal Kubernetes workflows. Yeah, absolutely. And actually to show that further, I can edit this number of replicas from three to 10, let's say, save. And if I apply this again, we can see that more pods are now starting, container creating, those are still in the process. And on Netrous side, we can see that Netrous now detected more IP addresses because we have six nodes in this Kubernetes cluster and originally, Pod Info was running only on three nodes. That's why we had only three IP addresses. Now Netrous understood, okay, now it is running on more nodes. So Netrous has populated more IP addresses of nodes into load balancer service. And when you say nodes here, I'm assuming you're referring to pods. I mean, there's probably still three nodes in the cluster, but these pods are the ones that are pulling in these IP addresses, right? So these are natively assigned to the pods. So we're honoring the true Kubernetes networking model where these pods are being assigned first class IPs from the subnet, right? So when they're communicating or things are communicating to that, you're kind of going point to point. And I think that's the best way to think about kind of doing that Kubernetes model. And the other thing I wanna say is shout out to anyone that's working on this console at Netrous, the fact that you're giving people that real time feedback where it's automatically updating, I'm running commands at the bottom console and then seeing that live kind of preview, respecting the health checks and then moving, letting people know what's going on. That is a beautiful touch. So I just wanted to shout out really quickly to whoever did that. Golden, great, great job there. Thank you so much. Our guys will be super excited. So I think we showed a lot here. I mean, maybe if there's something that we've missed, but for me, when I think about lots of people that are trying to go on prem, thinking about what does it take, at least from a networking perspective, to be ready for that dynamic set of environments that people want, because I think the thing that puts the most stress, whether you're the best network engineer in the world, whether you have great automation tools, I can guarantee you when people bring in Kubernetes, they have this expectation of being able to grab dynamic IPs. What we're not really showing here is that if you restart one of those pods, it can land on a different node, get a different IP. And the expectation of developers and platform teams is that those IPs will dynamically be updated. IPAM management will be fully automatic and the load balancer will follow things like health checks and service discovery to pre-populate everything. I think this is the problem most people have with the Kubernetes networking model. It will challenge whatever you have existently. And so if you don't have the ability to carve out VPCs and dynamic subnets and then do the full integration with the Kubernetes networking model, that's when people start complaining and that's when you feel like you're falling short. I mean, did we capture everything and it looks like we went through everything? If we've missed something, I think now would be a good time to kind of bring it up and show it. So to add a little bit on that in terms of IP addresses of pods, nodes, and so on and network engineering challenges, we're very much neutral and we understand that different people have different preferences. Someone may want to use one CNI, Celium or Calico, someone may want to use in one mode, another mode. For us, it's not much different. We support all kinds of configurations. Someone is happy using Calico, totally fine. Our operator is able to understand that if someone is switching into Calico's BGP mode, this is their kind of highly advanced mode. We understand even that and we know how to respond on our side, how to configure things that things kind of automatically seamlessly work together, as well as if it's just a simple setup with few nodes without complicated CNIs, still it's cool for us. We're just trying to support all these common use cases. Awesome. Oh yeah, go ahead, proceed. Yeah, let's see if this even works. So this service received this IP address. So what happened basically, NetRis has assigned next available public IP address to the service and pushed that information to Kubernetes. Same IP address here and there in console. But let's see if this even works. Okay. We can, so it works. We can even use Curl to make sure that it is being served by different pods. It's not, so actually load balancing is actually working. I can do, oh, so it's changing. All right, perfect. Look, I think we're at the end of the demo, but I do have a few questions and I know I've sourced a few questions before we started. And so one of the questions that I think a lot of people want to know is why haven't people thought about VPC or different abstractions on prem?  You know, why is that not enough? So, well, physical networks, they are kind of designed to move packets and traffic really well, which is fine. Like this is their specialization, if you will. They do this really well. VPC is, in my opinion, public cloud became possible, not because you put your server somewhere else, but because it was relatively easy and fast to use. When you want to iterate and people in this world, they want to iterate a lot, right? We're not we're not in the age where like designing something takes like 10 years. No, we're in the software age where we want to ship something, make changes and ship again. We want to ship many times a day. So basically it's iterations that are important for the business. And VPC is making this possible. So I don't need to go and communicate internally with multiple, we don't need to do kind of five meetings to decide how to add or remove one villain or something. That's in my opinion, that's why VPC is extremely powerful to make this iteration DevOpsC type mindset possible. And before starting NetRis, when I was looking to public cloud and being myself a person coming from traditional data center, I was like, oh my God, this VPC thing, this is insanely great in public cloud. This is, I wish this is available everywhere, like in every network, every data center, every edge, bare metal cloud, even my little home network, everything should have this. This is kind of how I thought about this. All right, so look, the next question, if I look at the list, one of the most common things is like, we talked about how VPC and abstractions are great in the cloud. We clicked around a lot in the console. So the next question is, is there things like APIs or Terraform support? Yeah, that's the question. Yeah, that's a great question. So yeah, I showed everything in web console. There's also REST API, which for example, someone who's like potentially embedding NetRis can use REST API, there's Swagger built in. But what is kind of more designed for DevOps engineers, that's of course Terraform. And I have here a little example of that. So to save everyone's time, just we'll show the resources. So in this Terraform file, I have summarized kind of NetRis resources. Like in previous example, we have created this Kubernetes cluster. Let's say we want to do the same, but with Terraform. So this is NetRis resource, this is VNet that we have created. This is Harvester resource, and this is Rancher resource. So basically in this example, I'm using two Terraform providers, NetRis provider and Rancher provider. And if I do this, let's say if we go to VNet here, and so we can see this is what Terraform is trying to do. So trying to create NetRis resource, the same VNet, and basically what I did from inside the Rancher from web console, but through Terraform. So process has started and it actually takes some time. I can see that it already created the K8 staging network. That one looks new, pretty recent, it has the latest day, and I can see it from the logs right there. So seems like the API is super responsive. Yeah, this has been created. And if we look into Rancher, actually K8 staging is creating here too. They're very responsive too. What is this thing waiting here? It is kind of waiting until the cluster is up and running and only then Terraform will finish the work, which takes some time, a few minutes, five, 10 minutes. But yeah, of course there's Terraform, how without Terraform. And I also wanna call out that it looks like your demo killed itself and that other cluster you were making earlier, the Kubernetes test cluster, looks like it's up and running. So yeah, it may have been a UI issue, so it's nice to see that get resolved. So don't tempt the demo guys, no need to connect to it, just let it shine bright, nice and green, good to go. All right, so I think we got time for maybe one or two more questions. And when people are looking at this and they're asking themselves like, how do I get started? Is it best for them to kind of start with like a small POC, get new hardware? What's the best way for people that are watching this? Maybe they're super excited. Maybe they look at this and say, yes, this is the missing piece. What's the best way for them to get started with this? Good question, so I would recommend similar basic setup like this, just like two machines for a soft gate, one machine for a controller, and two, three, just a handful of machines for compute nodes. In our documentation page, there is this install guide on VPC Anywhere Getting Started guide. Describes the concept and it works step by step through how you install controller. Controller installation is basically a one-liner that you copy and paste on Ubuntu Linux or any Linux. It will stand up a Kube cluster and NetRisk controller. Then you install soft gate nodes, which is, again, very basic. When you install NetRisk controller, you'll see this two soft gate nodes they will already exist there, but everything here will be read, hard bit will be read, because you will need to actually provision that soft gate machines, which is, again, a one-liner command you copy here, paste on machine, wait a few minutes until it installs. That's pretty much it. There are examples in the, we're also on Slack, so people are welcome to join our communities like Channel, where other users and our engineers are there happy to answer all kinds of questions. Awesome, and look, I think that was super dope. We got a nice demo. I mean, the big takeaway is for me where we can bring the cloud-like abstractions, the VPC on-prem. Also, doesn't seem like we have to throw away everything we have, so this works well in brownfield scenarios as well, where we already have a setup, we can work with our team to give us a range of VLANs, give that to NetRisk, and then we can now have a great way of partitioning that network, and this should sound real familiar from people coming from that VMware or a world where you did the same thing for your hypervisors, but now instead of just getting network automation, we're actually getting back to that world where you get that VPC, you have subness to choose from. I don't know about y'all, but I remember the days of people trying to track all this stuff in the spreadsheet, and now we have a full console, we have visibility, and we have something that actually understands the Kubernetes networking model, not just the node level, not just at the pod level, but even things like L4 networking load balancers and health checks and making sure that you can scale and remove things dynamically. So this is really dope, really wonderful. I want to say a big shout out to Alex and the whole NetRisk team who helped put this together. I know your company is pretty new, and this is just the beginning for them. I know we'll be at KubeCon probably talking more about this later. Maybe any final words for people in the audience and where people can catch up with you later if they have more questions. Yeah, absolutely. Thanks, Kelsey, and thanks everyone who's watching this. Hey, give NetRisk a try. It's really easy. We are looking forward to your feedback, positive feedback, negative feedback. All feedback is helpful. We have the Slack channel, so if you go to netrisk.ai slash slack, that's how you can join our Slack community channel. I'm on Twitter, Alex-Saroyan, that's my handler. It's also on the CNCF page, registration page for this webinar. If you're visiting KubeCon, please come visit our booth. We will have demo and we will have multiple environments where you will be able to play around with the product, talk to people who built the product and give them feedback, learn from them, exchange with experience. Yeah, looking forward to that. All right, awesome. All right, thank everyone for attending. I'll be around. I'm gonna keep my eye on this in general because I do think we need new abstractions. Kubernetes was a great abstraction for compute and it's nice to see that we're pushing past automation to new abstractions and maybe just maybe this VCP anywhere concept will take on. We'll catch y'all next time, later.


The Ministry of Youth Development and Sports partnered with the Roseau Valley Alliance to put on a youth expo, which formed part of the calendar of events celebrating April as youth month in St. Lucia. A number of budding entrepreneurs assembled at the Roseau Plainfield Sunday to display the services they have on offer. I've been a therapist for 13 years now. I started at Les Paul in 2010 and I'm now at Royalton and I do house calls. It's over 10 years since I'm doing house calls. Yes, I'm from Kulitown, Marigold, not before. Okay, so yes, I'm from Kulitown. Well, it's a good thing because many people do not know about the different businesses that have been showcased today and it's good that it helps because it helps grow our brand and which is a good thing for us. My name is Jenny Edward. I'm from Kulitown. I work with a farmer. He does the planting and I sell the produce. I used to always have fruits. He always brings fruits home and they spoil. So I sat down and I said, rather living the fruits home, spoiling, I could just try and sell them. So that's how I came about and the name of my business is Gents, Fruits and Vegetables. Instagram is the Gents, Fruits and Vegetables. You could get me on Facebook, the same name, Gents, Fruits and Vegetables. Public Relations Office of the Roseau Valley Alliance, Anisia Antoine, commanded the exhibitors and members of her group for staging the expo. So today we have here a youth expo and it is part of youth men's activities under the theme of empowering our youth for peace, unity and a safe society. And basically as the Roseau Valley Youth Alliance, being a small group of young persons in our community, we wanted to do something to bring together the young people who have small businesses to show our interests, our support to what they're doing and towards their goal as they're trying to improve their business and expand on it. So this is our second year hosting this activity and based on the turnout, we say that it's a success again. We're very happy what we're seeing here. We're very happy that the community came out to support and we would really like them to continue supporting our youth through in their future endeavors. Organizers are optimistic that events like these will motivate other youth of the area to develop a sense of enterprise. From the Ministry of Youth Development and Sports, I'm Ryan O'Brien.


Hey everyone now I wouldn't normally do news from this kind of setup but this just happened to be where my camera was when I was trying to get ready for a stream and well some news dropped gaming Intel a website slash Twitter handle that is well known for leaks like literally the entire advertisement for this place the thousands upon thousands of followers these this place has is because of leaks and they have gotten so many leaks right over the years between Xbox, PlayStation, PC and well Switch and well they are coming forward with a source that they claim has been correct on many occasions giving us a date for the rumored April Nintendo Direct and that date is April 11th yeah I mean anti-climatic right yeah so basically their source is saying that it's April 11th and that's all the information they're giving them no idea what's in it no idea why it's April 11th there is some you know the path is certain amiibo are coming out of the 12th potentially Joker might be landing on the 12th so I guess that could be the case also Reggie Fesame's last days on the 15th so then that would have this direct land before his last day in North America so I don't know there's a lot of things that could add up to make this day real also they pointed out in their article that this does line up with some prior Nintendo Direct's a lot of big Nintendo Direct's happened earlier in the month although we had a normal Nintendo Direct a couple months ago so it would feel kind of weird to have another normal direct and not like a Nintendo Direct Mini but hey who knows what Nintendo is gonna do they kind of do whatever the hell they feel like doing so this could be real this could be legit I don't know why don't you go up here and look at my speculation on what could be in this possible direct I'll have a link to the source for this date down in the description so I don't really know what else to say and this video is really short and really sweet but I guess just enter our Nintendo Switch Super Smash Bros. Ultimate Bundle giveaway to the glean that I'll link down in the description and I'm just going to catch all of you guys in the next video which by the way the next video is gonna be kind of cool because we're gonna be talking about the Switch Pro again or we'll be talking it from a different angle than my last video where I talked about my rumor or not really a rumor my speculation I guess my theory about why the Switch Pro exists and we're gonna get into some more technical details that I think you guys are really going to love expect that video to land tomorrow in the meantime I plan the live stream tonight so be sure to turn into a live stream about a half hour or so after this video goes live all right catch you guys then bye