So today what we are discussing is normal MRI anatomy of the shoulder. In today's session, we'll be discussing about the normal anatomy and the MRI anatomy of shoulder joint, the sequences and planning for any MRI shoulder, how do I read a MRI shoulder scan and the checklist in different planes. For any shoulder joint, these are the normal structures that you need to look at. It's just a list of structures we'll be looking at each one of them in this entire session over the next 15 to 20 minutes. Whenever you do an MRI shoulder, there are two joints that you're going to cover. One is your glenohumeral joint and the other one is your achromoclavicular joint. Now, first we'll concentrate on the glenohumeral joint because that is a more important joint. So it's a ball and socket joint where the ball is nothing but the humeral head and the socket is nothing but the green oil of the scapula. Now if you note, the humeral head or the ball of the joint is larger whereas the socket which is the green oil is a more flattened appearance and because the glenot is more flat and the humerus is more larger, it provides more mobility to the shoulder joint, but this comes at an expense of instability. So in order to provide more stability to the joint, there are soft tissue structures around the joint which help in making the joint stable. So if you'll see, this is your glenoid achromoclavicular surface. Around the glenoid, you have a labrum. Look at this thin purple structure which is the labrum. Then the green structure around it is the capsule and around that you have the rotator cuff tendons. So these are the soft tissue structures around the shoulder joint that help to provide stability to the joint and we need to look at all of these structures in a shoulder scan before labeling it as a normal scan. So whenever you do an MRI shoulder, the sequences that you need to take is a T2 fat saturated coronal sequence. So this is not a particular thing that everyone needs to do but this is what we usually do in a routine practice. You can add and subtract sequences depending upon your personal liking and experience.  Now the important thing is the planning of the coronal sequence. So just remember whenever you take a coronal planet on an axial, the planning should not be along the muscle but instead it should be along the tendon. So you can see this jet plaque structure that is your supraspinitis tendon in the axial plane. You need to plan your coronal along the supraspinitis tendon and not along the muscle. So make sure you inform this to your technician. Next sequences that we take is the proton density images in all the three planes.  And lastly T1 weighted images are not taken in all the scans but conditions where you're suspecting tumors, infections and inflammatory conditions, you need to go for a T1 weighted sequence. Now how to approach an MRI shoulder scan? So always have an approach for any joint that you report. For an MRI shoulder scan, I use the structural approach that is I go structure wise and in that also I use the inside out approach. So first I looked at the innermost structures and then I'll gradually make my way outwards. So first I look at the intraarticular structures that is bone, labrum, cartilage and capsule followed by biceps and rotator interval. Then going further out, you have the rotator cuff, muscles and tendons and the bursae. And last I looked at the AC joint and the neurovascular bundles. Now all of us are aware of the anatomy of the bones. We've been reading them since our first year of MPBS. So I'm not going much into it. What I'm going to discuss are the practical points which are important when you look at the scan. So these are the areas that you need to keep an eye on when you're looking at an MRI shoulder scan. So for humorous look for the hill sacks and reverse hill sacks legions, greater tuberosity fractures. Glenoid look for the bony, bancard and the antero-inferior glenoid bone loss, coropoid process fractures, acromion process fractures. And this one important thing is distal end of clavicle. Important because we usually tend to mist it in the scan because it comes in the periphery of the scan. So make sure to look at the distal end of clavicle because there can be stress fractures and stress edema particularly in weight lifters in the distal end of clavicle. So now let's look at each of these on a normal MRI scan. So this is a coronal proton density, non-fat saturated image. We are going from anterior to posterior. The anterior most structure that you see is this coropoid process along with the short head of bicep stentate. Now as you go posteriorly just make sure currently we are only looking at the bones and nothing else. So as you go posteriorly you begin to see the antero-inferior glenoid. Keep an eye over here for the bancard lesion for the osceus bancard lesion and marrow edema. Then further posteriorly look at the greater tuberosity with the supraspinitis and intraspinitis tendons attached. Avergene fractures are common in this region and please note avergene usually these avergene practice are not displaced. So they are difficult to pick up on x-ray but they can be easily picked up on an MR. Then this is the important thing that I was talking about. Look at the distal end of clavicle because we usually tend to miss this area. Now you will see in this region this grey zone. So the black is the cortex above that there is a grey zone. So this is nothing but your tumoral articular cartilage. This is the glenoid and over here also you can see there is a thin grey zone that is your glenoid articular cartilage. So this area is your subconvial region for the humerus and the glenoid. Keep an eye on this area for subconvial marrow edema and subconvial cystic changes which will happen in venerumural osteoarthrosis. Then as you go further posteriorly in the posterior superior aspect of humeral head look out further for any flattening any marrow edema or any defect which would indicate the hill sac region in a patient with recurrent dislocations. Okay, now let's look at the sagittal image. So we are going from lateral to median and again this is a proton density non-fat saturated image. So you can see these are the tendons. It's a supraspinitis and inpraspinitis tendons and this is nothing but your greater tuberosity. So keep an eye over here for GP fractures as you go inwards or medially look at this region. So if you say this is your acromion process. So this is posterior and this is anterior. So posterior superior humeral head look out for any defects any flattening and marrow edema suggestive of hill sacs lesion. This is the most important sagittal image that you can get for a patient with anterior instability. So this is nothing but the N face view of the glenol or the glenol articular surface. The plaque thing around it that you can see is the labrum. So this particular image is very important even for an orthopore. You need to look out for an anterior glenol bone loss or any auspicious bankard lesion. You can use your best fit circle method in this region where you draw a circle along the posterior and inferior cortex of glenol and it should pass through the anterior cortex. If it does not pass, then it indicates that there is an anterior glenol bone loss. So just remember to get this section. This is really important section. The next thing is your porcupine process. Porcupine process fractures is particularly important in patients with anterior instability because whenever there is an anterior glenol bone loss which is significant, the orthopore will use this porcupine process and put it here which is called as a lethargic procedure. For that, he needs an intact porcupine process. So just make sure that there are no fractures in the porcupine process. Now let us look at the HU scan. So you have a distal end of clavicle which is the superior most image. Then what you see is your atromial clavicular joint. So this is your atromial process, distal end of clavicle and this is the joint space. Inferiorly when you go here you can see this is the superior sections of the humeral head and this is the posterior aspect. So you can see there is a curvature. It's actually a pretty round structure. Look for any flattening. Look for a wedge shape defect in this region and marrow edema which will indicate a hill sacs region. Further Inferiorly, look for the hill sacs region. So just remember when you go further inferiorly there is a normal flattening in the posterior superior in the posterior humeral head. So this should not be labeled as a hill sacs region. Hill sacs region is only when it is in the superior sections but when you go inferiorly this flattening is normal. Similarly here we should look out for any again any marrow edema and the defect which would indicate a reverse hill sacs region. Again inferiorly you will see there is a flattening in this region. This flattening is normal and should not be labeled as a hill sacs region. As you go further inferiorly, look at the anterior inferior glenoid for any osceus-bankart lesion for any glenoid bone loss and marrow edema. So these are the structures which are particularly important when you look at the bones. Now let's go to the labrum. So as I have told you the glenoid socket is a flattened one and in order to provide some contability to it there is a labrum around it. So this purple structure is your labrum and this blue is nothing but the glenoid articular surface. Now, whenever you describe an April tear, you need to describe the exact extent of the tear. For this you can use something called as the clock position. So the superior one is your 12 o'clock position, the inferior or 6 o'clock position. The place where the biceps goes, here you can say the biceps is going this way, that's your anterior. Here you can also make out that this is your acronym process, so this is a posterior aspect. So anterior equator, equator is nothing but the glenoid vein, so anterior equator is 3 o'clock position and posterior is 9 o'clock position. Now there is some confusion sometimes in the nomenclature regarding the 3 and 9 o'clock position. So in order to be completely crystal clear, what we need to do is you can also write about the quadrant in which the labrum tear is present. So you can divide your labrum into like an X, so this is your superior quadrant, inferior quadrant, anterior and posterior quadrant and one more line which you can add is a horizontal line joining the equator, the anterior equator and the posterior equator, so now the anterior labrum is further divided into anterior superior and anterior inferior labrum and the posterior labrum is further divided into posterior superior and posterior inferior. So whenever you describe a labrum tear, make sure to tell which quadrant it is involving and also if you want you can give the clock of the tear, so you can use both of this together but please make sure to use the quadrant because it's more crystal clear. Now whenever you look at the labrum, the superior labrum is best thing on a mid-peron image, so this and just remember all the labrum has a triangular appearance in whatever plane you look at it, usually it's a triangular appearance. So this is your superior labrum, this smaller one is your inferior labrum and the anterior and posterior labrum are best thing on the ancient images, so this is your anterior labrum and this is your posterior labrum. Okay, so now another structure which reinforces or provides stability to the joint is the capsule around the joint and important to note is anteriorly this capsule is thickened at places to form the glenohumeral ligaments, so you have the superior glenohumeral ligament, middle glenohumeral ligament and inferior glenohumeral ligament. So these are present anteriorly, inferior glenohumeral ligament also has a posterior band which is present posterior. So now let us look at the labrum and the glenohumeral ligaments together on an axial scan. So this is an axial PD non-pat saturated image and this is the topmost section. So what you see is your superior labrum over here and you can see a thin flimsy structure that is coming out of the superior glenoid. This is nothing but your superior glenohumeral ligament. This ligament is better seen on a surgical image and we'll have a look at it later. Further when you go inferiorly, the structure that you see here, you can see two structures. So the triangular structure, this one is your labrum, okay? This triangular structure is your labrum. So this is the anterior labrum. This is the posterior labrum. Another black structure that you see over here, this is a thickening of the capsule which is nothing but the medial glenohumeral ligament. Now one more thing that I want you guys to note is this. You can see there is a cleft. So there is one thing, I'll just go a step back. Yeah, so you can see there is no cleft over here, but there is a discreet cleft over here. This should not be labelled as a tear. This is a common normal variant called as sublabel foramen. It is present in the anterior superior quadrant. Unless you see a tear extending anteriorly inferiorly or across the superior labrum into posterior superior quadrant, do not label this as a tear. This is just a sublabel foramen. And another normal variant is where this MGHL will be more thickened and you won't see a triangular labrum over here. So you will see the posterior triangle but not the anterior superior triangle and that is nothing but the G4 complex and added. So here now as you go inferiorly, this thing is your anterior inferior labrum. This is your posterior inferior labrum and another thickening which you see more lateral to the anterior inferior labrum. This is nothing but your inferior genitalumeral ligament. And here you can see that the capsule is thin. So the capsule is thin but this is more thickened capsule which is nothing but the genitalumeral ligament. Now this is just to show you the difference between the normal labrum and an abnormal labrum. So this is a normal labrum. Normally there should not be a fluid signal intensity between the labrum and the glenoid bone and the glenoid cartilage. So this is normal. Here you can see there is a discrete fluid signal intensity which is passing between the labrum and the underlying glenoid cartilage. So this is nothing but a labral tear. Now as I told you, SGHL or the superior galenumeral ligament is better seen on a sagittal image. It's a thin flimsy structure which will arise from the glenoid. We will further discuss this ligament when we discuss the rotator interval. So for now you can just keep in mind that this is how SGHL looks like. And even your MGHL and IgHL can be seen on a sagittal image particularly in a patient who has joint diffusion. So whenever there is some joint diffusion, you will appreciate. You can see on this diagrammatic image. So this thing is the capsule. You can see there is thickening. So this is SGHL, MGHL and IgHL anterior band. And you can correlate this image over here. So you can see this is your thin capsule. In this region it is thickened jet black structure.  So this is how you can look at these ligaments even in a patient with joint diffusion. Now what we need to look at is biceps and rotator interval. Now there are biceps can be divided into three parts. So you have a horizontal segment which runs about the human head, then you have the pulley where it turns to form the vertical portion and the vertical portion runs in the bicepital group. Biceps pulley is important because it stabilizes the biceps tendon in the region of the turning of the pulley and in the bicepital group. So it prevents biceps dislocation and biceps pulley comprises of THL that is coraco-humeral ligament, superior glenoyumeral ligament and superior subscapularis tendon. Rotator interval is present between three structures which we will discuss when we see the scan. So this is your biceps tendon. Okay. This is your short head of biceps and this is your long head of biceps. This is the horizontal portion of the biceps which arises from the supra-glenoid tubercle. Then it will turn over here. So this is the region of the pulley and then this is the vertical portion which is running in the bicepital group. So this is your lesser tuberosity, this is your greater tuberosity and this is the bicepital groove. And across this bicepital groove you have something called as a transverse-humeral ligament which is nothing but a slip from the subscapularis tendon which stabilizes the tendon within the bicepital groove. Now important thing to understand is the biceps pulley. So you have the coracoid process. From the coracoid process there is a ligament which comes out which is called as coraco-humeral ligament. So it comes from the coracoid process and goes and attaches to the humerus near to the bicepital groove. So this is the superficial structure. Then you will remove the coraco-humeral ligament deep to it you will find the bicep tendon traversing. So the red colored structure is the bicep tendon and you will find the superior general ligament which is a green colored structure. So immediately it is just alongside the bicep tendon but as it goes naturally it goes deep to the or it goes inferior to the bicep tendon. So now we look at the actual MRI images. We are going from again anterior to posterior on a coronal image. So first thing that you are seeing over here is the subscapularis tendon. Now as you go posteriorly you can see your bicep tendon over here. This is the bicep tendon in the bicepital groove and this is the pulley region. Further on this is your horizontal portion of the bicep tendon above it is the supraspinitis tendon below it is the bicep tendon. Here you can see the bicep tendon and this it goes and attaches to the labrum the superior labrum. So this is nothing but the bicep's labrum junction. This is important in case of tears slag tears can involve the bicep's labrum junction. So you should look at this properly. Next thing that the woman discuss about is the rotator interval. So this is a sagittal image which is passing through the level of the laryngeal joint line. And rotator interval is nothing but a triangular space which is present in the anterior superior aspect of the shoulder between coropoid process, subscapularis muscle and the supraspinitis muscle. So this triangular structure is the rotator interval. The main content of the rotator interval is factor.   Hence proton density non-fat saturated images are really important for shoulder image. So this is the fat region. If you see scarring in this region you can think in terms of adhesive capsulitis. Now the next structure that is arising. This is your coracal humor and liquor. So as I told you it arises from the coropoid process goes to the humorous and attaches near the bicepital through. So this is your triangular rotator interval. The coracal humor and ligament reinforces the roof of the rotator interval and the contents of the rotator interval is this thing structure which you've seen before also which is the superior glenuleuron ligament and bicep tendon in this region. So SGHL and bicep tendon are the contents of the rotator interval. Now as you go naturally here you can see that the relation is bicep tendon and SGHL are next to each other with CHL forming the roof. Now as you go further naturally you can appreciate this oval structure is your bicep tendon here you can see this is your SGHL this is your SGHL and here you can see it is trying to go beneath there is a curve it is trying to go beneath the bicep tendon. So here you have CHL on the top the bicep tendon and SGHL which is trying to go beneath and now in the region of the turning of the bicep tendon you have this CHL on the top you have the bicep tendon and the SGHL is going beneath it. Now this bicep scully region is particularly important whenever there is tear of the sub scapularis or tear of the SGHL it will result into dislocation. There are different types of dislocation of bicep tendon so it's a different classification which you can look at it later. Now let us look at the most important thing that is the rotator calf tendons. So we all know that there are four rotator calf muscles and tendons so the superior is a supra spinatus anteriorly you have the sub scapularis. The third one is the infraspinatus which is exactly posteriorly so since this is a 2D image I am not able to show it here so posteriorly you have the infraspinatus and posteriorly inferiorly this is the 3D spinal tendon. Now this is a sagittal image to show you the muscles so you can see this is the coropod process so this is anterior. So supra spinatus fossa has the supra spinatus muscle anteriorly is the sub scapularis muscle posterior superiorly you have the infraspinatus muscle and posteriorly inferiorly that is the 3D spinal muscle. Now let us look at the tendons individually so this is a sagittal image at the level of the humeral head where you can appreciate all the tendons so this is a point to note that a sagittal image you can evaluate all the tendons together so the anterior tendon is your sub scapularis tendon if you see there are multiple small jet plaque structures inside so it's a multi-pinate tendon not a single tendon it's a multi-pinate tendon but on a diagrammatic image I've actually drawn it as two separate structures so this is because the superior sub scapularis and the inferior sub scapularis are functionally separated so superior sub scapularis is a functionally different one and inferior is a functionally different one but anatomically they look simple and your superior sub scapularis is particularly important because that is more prone to tears. The next what you've seen over here this is your biceps tendon and then you have the supraspinatus and infraspinatus tendon so the first one is the supraspinatus tendon the green structure is your infraspinatus tendon and then there is a place where these two tendons merge with each other and that is nothing but your conjoined tendon infraspinatus footprint is slightly larger as compared to your supraspinatus footprint and inferiorly posterior inferiorly is your pd spinal tendon now whenever you look at the rotator cup and you're evaluating rotator cup the supraspinatus tendon is best seen on a coronal image your sub scapularis and infraspinatus tendons are best seen on axial images so directed images you can evaluate all the tendons together so normally any tendon comprises of a footprint where it goes and attaches to the bone and there is a myotendinous junction where it where there is a junction between the tendon and the muscle and this is your tendon so but in case of supraspinatus tendon there is another zone which is important which is called as the critical zone now this critical zone is approximately one centimeter away from the footprint and this is important because in supraspinatus tendon this region is slightly hypovascular and because of the low vascularity it's more common to have degeneration and degenerative pairs in the critical zone of the supraspinatus tendon traumatic tears usually happen at the myotendinous junction besides whenever you get the gp avulsion then that will be a direct avulsion of the bone now the next thing is the bursa so you have a subacromial bursa which lies deep to the acromion process above the supraspinatus tendon and it can also extend this way downwards deep to the deltoid muscle so it is also known as subacromial sub deltoid bursa and the next two things that you need to be aware of is the sub scapularis recess and the sub coropoid bursa now sub coropoid bursa lies superficial to the sub scapularis muscle and it does not communicate with the joint it does not go deep to the sub scapularis muscle whereas the sub scapularis recess as you can see over here it will go deep to the sub scapularis muscle and it will also communicate with the joint effusion so this is how you can differentiate between the two the neurovascular bundles around the shoulder the two most important ones is the spinochleloid notch this is your glenoid this is the posterior aspect this is where the spine of the scapularis arises so this notch is nothing but the spinochleloid notch and it comprises of the supra scapular nerve now it is important because whenever there is a posterior labral tear a small glenoid cyst or a large glenoid sorry a ganglion cyst or a paralabral cyst or a large paralabral cyst it would extends into the spinochleloid notch it can abut or it can compress the supra scapular nerve in this region which would result into denervation edema so this is one important structure that you need to look at closely and the another thing is your quadrandular space which comprises of the axillary nerve any space of you find lesion in this region will again compress the axillary nerve and result into denervation changes now let us look at the tendons and the bursae on a coronal PD images so this is a porcupine process with a short head of bicep tendon the first structure anteriorly that you see is your sub scapularis tendon this is the sub scapularis muscle the myotendinous junction and this is now in this particular image you can actually pick up small delaminating tails in the sub scapularis tendon now as you go posteriorly you can see the bicep tendon and just next to the bicep tendon is your anterior suprasfinitis tendon now this is a common site for something called as rim-rent tails which are small arterial sided tails and it is often missed on a coronal image so make sure you correlate this particular region on a sagittal image as well as you go posteriorly you can see this is your suprasfinitis tendon so as I told you there is a footprint a critical zone and the myotendinous junction and then further you can see that there is a subacromial bursae in this region it is not visible unless it is distended with fluid then you can see that this is your infrasfinitis tendon and this is your quadrantular space infrasfinitis tendon t-rease minor tendon and the myotendinous junctions again infrasfinitis t-rease minor tendons and the myotendinous junctions so this is the posterior most section and now we look at them at the sagittal images so suprasinfra and the conjoined tendon where the two merge together this section is what we have seen in the diagrammatic representation so this is the multi-pinate sub-scat suprasinfra forming the conjoined and this this tiny black structure this is your t-rease minor tendon and this black structure is your biceps tendon so as you go posteriorly you can see that we will clearly make out the multi-pinate appearance of sub-scat here so there is one, two, three, four so there are multiple tendons in this region and for the posteriorly here you need to look at your muscle bulk or the muscle volume and you need to look for muscle fatty infiltration in this region so we have discussed this anatomy already and now on the axial images so suprasinfra is not well evaluated on an axial image when you go downwards you begin to see the sub-scatularis tendon which is arising from the lesser tuberosity this is your biceps tendon here and this is your sub-scatularis myotendinous junction similarly posteriorly you will see your infraspinatus tendon, infraspinatus myotendinous junction again over here you can appreciate the spinal clenoid notch then you have the t-rease minor tendon which is the lower most one this is your t-rease minor tendon t-rease minor is not much important because it is it usually does not tend so that is the least important of amongst all the rotator cuff tendons and the last thing that we're going to discuss in short is your ac joint or the acromioclavicular joint which is between the acromion process and the listerine the clavicle it is stabilized by the superior and inferior acromioclavicular ligaments and you have a coracoclavicular ligament between the coracod process and the clavicle so your ac ligaments or the acromioclavicular ligaments are better seen on coronal images so you can see if they run along the capsule and here also you can see so this is your clavicle this is your acromion process and this thickening is your inferior and this thickening is your superior acromioclavicular ligament similarly your coracoclavicular ligament you can see that this striated structure is your coracoclavicular ligament on a coronal image but it is better evaluated on a sagittal image but you can see this is the coracoid process the clavicle and then these are your coracoclavicular ligaments here so to sum up always have an approach to the ending scan make your own approach be comfortable with whatever you are doing and this is the checklist to look at the structures in different planes the important structures which are practically important so you in coronal from anterior to posterior you need to go through these structures sagittal from lateral to medial make sure you look at these structures and axial make sure you look at these structures from anterior to port and whenever in doubt please make sure that though one particular structure is seen better on one plane for related on other planes so that your hundred percent sure of your type process thank you


Our next speaker, Al Gillan, I've known for a very long time and has also been sort of on a journey with us in open source from his view at IDC as a research analyst. He oversees the open source research portfolio amongst a variety of other areas. Please welcome Al Gillan. I will say that I have never had to follow a presentation like that. And I also will say I'm not funny. So now that we've all gotten a lot of laughs out of our system, I'm not going to help with that at all. So a couple of things that Dan brought up that really made me stop and think. And one is that I've actually been at IDC, I'm in my 18th year, which is stunning. It's unusual in the industry at this point. And I don't know, maybe I'm also 58 years old. So maybe I'm part of the old guard and not part of what's going to be in the future. So the other thing I thought was really interesting was he talked about the community and how there are different buying factions and so forth. When I think back to where I was at IDC in the beginning of my career in the early 2000s, and I'll talk a lot about it because I've got some historical slides that actually going to tie in nicely to what Dan talked us through. But I actually had people that loved me and people that hated me. And it was just interesting because what we tend to believe at IDC as an analyst, if everybody loves you, you may be not doing the right thing.  But if some people like you at certain points of time and they hate you at other points of time and vice versa, you must be doing something right. So when I started my career, I had a large software company that is now a member of the Linux Foundation of all places, hated my Linux data. And then I had somebody in the open source community that had a hate page for me, so I guess I was doing the right thing. So anyway, what I want to talk about today, there's a few things. I want to take a little bit of a walk back into the past. And this is a little bit of a deja vu for me to be here today, because I've actually presented to a couple of Linux Foundation events in the past and I'm actually going to pull up a couple slides that showed data that I presented when I was here back in 2008. And I think it's interesting because some of the messages that I saw there and some of the learnings that we pulled out of our data at that point in time is going to be reflected in what we see going forward from this point here. And then I also want to talk about kind of roll that forward and tell you what we see as where open source fits in the industry going forward. And frankly, I'm really very lucky to have been in this position at IDC to watch the evolution of open source software for all these years. Because from my point of view, it really is the future. The future is all about open source and we see very much open source becoming the standardization layer that enables everything else that we do in the industry. So I got my 20 minutes, I better start going. So let me set the stage here. So if we look back to 2001, I mean you could read those bullet points, I mean George Bush had just been sworn in, Wikipedia had just spun up, Mac OS X, Windows XP and so forth were products that were just coming the market. Wow, it's a long time ago, doesn't that seem crazy? So Linux was in the market at that point and that's when we were seeing Linux really emerging as a solution for commercial implementations. And we saw people actually putting Linux in place where they previously most often had been using Unix at that point in time. And part of it was a result of the dot-com bust, right? We had huge slashes to budgets that corporations put on their IT departments in particular and people still had to stand up services. They had to put up web servers and transactional servers and so forth. And Linux turned out to be the low or no cost solution that they used to do that. So it's pretty interesting how that really got its traction. So this is some data that we presented back then and the thing that I think is really fascinating. So all the way at the top price, right? Linux is quote unquote free. So that was one of the real attractions. But the reliability was something that really jumped out at that point in time. So those are the sort of things where we look at that and we say, yeah, that was really foretelling of where this was going. But there's a couple of other things and one that I'd like to point out which really actually frightened us, if you will. Down here about halfway down is one that says believe in Linux. So we kind of like to think of that as if you will, the zealotry. And back then there were a lot of people who just loved open source and used open source software because they believed it. It's not because it necessarily was better or solved the problem, but they just had this belief that it was the right solution. And I would argue that that moment of time, that's okay. But long term, open source software has to be something more than you believe and has to really deliver value. And it has done that, it really certainly has over time. So some of the challenges that people faced at that point in time. So at the top, so lack of in-house skills. Let that one sink in for just a second. I think that that continues to be the number one problem that many organizations have for adopting whatever the most exciting and current open source initiatives might be. So whether it's hypervisor technology that came along or whether it's container technology that's emerging today and orchestration Kubernetes and Mesos and so forth. People say, we don't have the skills. They're looking for skills to support these kinds of environments. It's always the challenge that the open source community faces is you bring these great things forward, then there's a skills shortage and people need to learn how to use these things. So in any event, it's pretty interesting. You know, we look at that and I look at it today. And frankly, some of the challenges really remain the same. Okay, so let's zoom forward to 2008. This is when I was last presenting at the Linux Foundation at one of these events. So the iPhone had just come onto the market. Seems like we've had iPhones for a really long time. The oil was $100 a barrel and by the way the stock market was again on its way down to a new low point. We had these, what, 777 point drop in September of 2008. So Bill Gates was about to step down. Fidel Castro was about to resign and so forth. So really, we're at a point in the industry where things were changing. And when we looked at the data, we collected this data of what was happening in the Linux market overall. We started to apply year over year comparisons to look at what was happening. And the thing that's fascinating is if you look at this slide, the stuff on the right tends to be infrastructure oriented, right? Linux really got its start in the infrastructure side of the market. So web servers, print and file servers, DNS, DHCP, security, email scrubbers, things like that. But the things that were really very business oriented, so the line of business applications, the CRM and data warehousing and things like that, tended to be areas that the proprietary operating systems held their grip on much longer. But we saw this shift happening in 2008 where the market was starting to tilt and Linux had become credible and a reasonable alternative for those types of workloads, which really set the stage for where we are today. So one of the other things I think was really fascinating is look at this. So again, back to that zealotry quest, that point I had made earlier. Look at the yellow bars at the bottom here. This is the portion of the readers or the portion of the people that we surveyed that told us that Linux was a top-down initiative driven by management. It basically doubled from 2002 to 2006. So there's the credibility being established. And frankly, I'd argue that it was so important for Linux to establish this level of credibility because Linux becomes the foundation for just about everything else we do with open source software going forward. So as a result, if it's got this kind of credibility, we got this top down acceptance. The barriers for absorbing and consuming and deploying new open source technologies becomes much, much lower going forward. Okay, so here we are today. I'll do one more of these charts since I've done the historical one. So here's where we're at today. We've got another new president. The stock market for change is not on its way down, at least at the moment. Interesting thing, I mean, the notion of online content and internet and social networking so forth has become very ubiquitous. And we've got this availability of information. In fact, we've got too much information. And half the time, we can't even tell what's real and what's not real. But there's another really interesting, and frankly, I'd argue, a little bit of a scary transition happening in the industry right now. And that's that the proprietary software products, the vendors that have made their business for a long, long time, selling software and software only, are finding that it's becoming more and more difficult to be a software vendor. And that's partly because of open source software as the tide continues to rise. And these proprietary products that have been the bread and butter for a lot of software companies for a long time are having a harder and harder time differentiating. And the other thing is a lot of these things are turning into services that are being delivered through the cloud vendors. So whether it's Google or whether it's Amazon or Microsoft Azure or the second tier level of service providers, these types of things are now becoming services. You don't necessarily have to go buy an operating system. You can rent one from a vendor like that. So it just changes the dynamics of the industry. Other things, so Amazon and VMware, I mean, who would have thought that they would get into an alignment? But really, that becomes the on ramp for VMware to bring their customers into a real robust worldwide cloud. And for Amazon, it becomes a conduit for them to pull Windows installations over their cloud. And of course, Microsoft joining the Linux Foundation, good for them. I mean, I think they should have, with Sacha Nadella at the helm now for three years, it's a different company. And I think if Sacha hadn't been named CEO, I don't know if Microsoft would even be relevant going forward, but they've certainly turned the corner there. So pretty interesting stuff. And what's happened overall? This is a map of where the Linux market has gone. The red and the yellow lines are Linux. The yellow is the non-paid Linux, so the non-commercial distributions. And this would include the versions of Linux that are stood up as the base OS in cloud infrastructure. So every time Amazon or Google spins up a new server, that's part of that yellow line. So naturally, you sing a lot of growth because of the cloud, build that. But the red piece, the commercial side, so that's the red hats and the Suzas and Ubuntu's that are under commercial support that customers are deploying. So continued growth on there and that's a lot of that over time moves over into virtualized instances, they're not necessarily physical server instances. It's more about, there's more growth in the virtual side of the market and that's the way it's going to be going forward. So again, really interesting transition there that's taking place. So a couple of things I'd like to talk about how this transition, where it's coming from and where it goes from here. So we think about what's happening in the industry. So all these, you've seen some of the symptoms in my previous slides or the visible elements of change and it's being driven by a number of things. One is that we've gone to standardization. This has been happening arguably for close to 20 years. We standardize it to hardware layer where x86 servers become the predominant server. We've standardized it to OS layer and it used to be Windows and Linux and I'd argue that going forward, it's really Linux as the primary OS on the x86 platform, Windows continues to exist and more so as a guest going forward than as the base OS because most of the stuff spun up in cloud, again, are going to be basically Linux servers. But what's fascinating is above the OS layer, we're getting a lot of standardization. I got another slide where I'll talk to that in a little bit more depth. So interconnection of systems, yeah, we've got the local area networks in our environments and all of our servers are connected already, but our processes are not connected. And today, we see this big transition in the industry where this sense of digital transformation is taking place and people are trying to automate and bring massive amounts of data into their world so they can make decisions on the fly based on data and respond to that data using this interconnection of systems. And by the way, that means that there's an awful lot of new software that has to be written. So intellectual property used to be about a server design or about a piece of software where you've got it heavily protected through patents and so forth. Today, that may still be the case here, but the interesting thing is it's no longer emerging in the industry as an application that you go and buy a box of software or a license for a piece of software that you're going to consume. It's more so emerging as part of the systems that we get. So what I'm talking about is it's a car, right? It's a Tesla with a lot of software in it. It's an airplane that has an instrumented engine. Things like that where the software becomes part of the intellectual property that makes things better. So really going forward, we see the evidence that there's just an enormous amount of hiring going on at companies that traditionally are not software companies but rather are manufacturing companies because they want to have this software intellectual property built into their systems. And data. There's just data that's coming from everywhere. So social data, mobile data, IoT data and so forth. I was doing a presentation in, I guess it was December, I think. And I was actually in front of a crowd. It was heavily dominated by Wall Street types. And I just thought, for those guys, they suddenly have a world where when our president makes a tweet, it changes the nature of the stock market. And suddenly, that has to be an input to their trading systems. So you start to think about how data can change your business. There's a really very good example. But I mean, it's not just simply that. It's about IoT data. We've got weather data. We've got consumer behavior data. All this stuff influences how you sell your products going forward. And finally, all the action end of this is the ability to do decision support and real-time analytics on these data sources. So all these things become part of what is driving your industry going forward. And the key point there is that all of this comes back to the fact that we have to write new software that can allow us to do all these things. Okay, so this slide really is just a summary slide of a number of different things. But the nature of what we're looking at is when we think about the transformation. So there's what we refer to at IDC as accelerator. So things like security, augmented and virtual reality, Internet of Things, cognitive AI and so forth. These are all drivers that they force this acceleration to go. And across the top, those icons, those are icons that represent some of the industry clouds we expect to see emerge. So for example, healthcare, retail, manufacturing, energy, government and financial. So those are all areas where we see a great deal of interest in developing verticalized cloud resources for these industries that are going to drive the consumption of software. And by the way, a lot of that is enabled by open source. So going forward to be competitive, you've got to embrace the standardized infrastructure, modernize applications. And a lot of this ties right into a modern DevOps type deployment model.  So just a few thoughts here. So I talked a little bit about the application end of it. I really see applications, modern applications, so cloud native applications as becoming the thing that really drives us forward and allows all these new capabilities to be delivered and to be consumable by both the developer community and by the end user community out there. So the thing to remember though is that the installed applications. So if you've got applications that were written, I don't care if they were first platform applications, as we refer to it at EC, so mainframe applications. Or if they're second platform distributed computing applications on Linux, Unix, Windows. Those applications don't go away. They still have business value, but they're not going to make this shift and become a modern cloud native application. So what you're going to do is you're going to want to build new applications that sit alongside of them and sit on top of them and leverage those old applications for the business intelligence that they have. But they're not going to be modern, they're not going to be replaced. What we do see is we expect to see a lot of it. What we refer to is lift and shift, where these applications are going to be rolled up into a container and rehosted somewhere else, but they're going to be continued to be used, essentially as is for a long time to come. The starting points and the end points, I mean, they're pretty clear. If it's a Windows app, it stays on Windows. If it's a Linux app, it stays on Linux. We don't see a lot of movement back and forth across things like that. For the very reason that there's no real business value associated with doing the migration. And finally, the cloud native apps become, it really becomes the entry point for this new battleground. And we see pretty much every vendor in the industry, if they're going to be relevant for the next 10 years, they need to have a cloud native strategy. They have to have a way of building the life cycle for these applications. They have to make sure that they can prevent, present opportunities for these applications to be successful. So let's see, customers, I mean, when we talk to customers, they very much see this as being their future. They want to be doing cloud native applications. They very much are trying to get into the space. They find that there are barriers because they don't necessarily have the skills that they need, but they very much see this as where they want to go. But the thing that's interesting for me is that in many cases, the applications they have don't necessarily need to be cloud native applications. Meaning, does it need to have internet scale, right? If you've got an ERP system where you've got 1,000 users or 5,000 users or 10,000 users, that doesn't go from 10,000 users to a million users overnight, right? You've got an enterprise of a fixed number of employees. So those kinds of abilities to scale up and scale down in a very responsive manner, that's not necessarily one of the requirements that you have to fulfill in a typical enterprise. Standardization, we talked about that. It's very much a precursor for modern cloud applications. And finally, the applications, one of the things I think is really fascinating as the guy that followed operating systems at IDC for a long time and began my career as a programmer. We think of operating system APIs as really kind of being the holy grail of development, but that's not the case anymore. Really, anybody that's programming to operating system APIs is really limiting the viability and the portability of their application going forward. So the notion of not writing to OS APIs and really using as much abstractions you can, that's really where you have to go going forward. So this slide really just, you know, this is pretty stuff that you guys really understand because you are the people that have helped build all the things that make this possible. But we started with Linux, but we now got this whole ecosystem. We've got infrastructure software, we've got the developer tools, we've got the middleware pieces, and the applications. We've really come full circle. And today it's the application piece that's really fascinating. We see a lot of activity going on there. And in many cases, I think that things are going to fall into the application sphere are going to be things that are going to look and feel a lot more like services that are going to be delivered by a cloud vendor. So you're going to go to Google and you're going to consume TensorFlow services from them, right? That'll be a thing that will make your application better. And that's how the application piece really becomes a much smarter, more capable set of resources for developers. But it's amazing to me, again, when you think about this, we've come pretty much from zero to what we have today. And obviously, this is only a sprinkling of icons. There could be three times that number of icons in here. This has all happened literally in the last 18 or 20 years. OK, so just a couple data slides, I think, help here. So this is just a snapshot of some work we did around DevOps. My team did some research on what the developers are looking for. And one of the things I thought was really fascinating here is that people that ranked open source software based products, so basically they wanted to use products that were built using open source software as the underlying component, that's the kind of products they want to consume. But they don't really want to use stuff which is they don't want to use it directly off of the community. So they don't want to use a community versus version. They want to go to a commercialized vendor and have that vendor deliver them a commercial product based on open source that they can use. And if there's a problem, they want to have a phone number or an email where they can say, help, fix it. And that's what the cloud vendors do as well. So if you go to Amazon and using some of their cloud services and there's a problem, you don't have to fix it. You have to tell them, we have a problem. This is what the problem is. And it's their job to fix it. That's the value prop that you get from having a commercializer associated with the open source software that you want to use. In terms of the maturity, so here we see people telling us that they're finding it. They still are concerned about the level of maturity. And this is very specific to DevOps. So in the DevOps space, we think there's certainly room for there to be a fair amount of growth going forward. But the point is, again, that the users are telling us that we like open source software, we want it to be commercially supported. And we're concerned that they're not mature enough and broad enough for our needs. So again, it kind of gives them marching orders for the community that they need to continue driving forward in these projects. But remember, that commercial ecosystem, I think, is as essential to the long-term viability of open source software as the community that does the development is. So it's a two-sided thing. And there's really value associated from having commercializers, vendors that commercialize open source products and make them consumable for the masses. OK, so let me wrap up here. I think I've hit on all the points, so just to summarize. So we think that cloud-native applications are very much a differentiator. We're not going to take our existing applications and make them cloud-native, but we're going to write a lot of cloud-native stuff that's going to sit alongside of our existing applications as going to consume the business value, the business value, the intelligence, the information, the data that's in those applications and make that usable for these modern cloud application products that are being built. So the frameworks are continuing to change. Frankly, I think that container technology and orchestration technology that's very much sweeping across the industry today, I think it's wonderful. I think it's something that the industry has needed for a long time. I mean, we've talked about reusable code since when I was back in school well back in the last century. And the notion of having reusable code segments that actually are truly portable, that's really great stuff. So cloud-native apps, I mean, very much we're moving this model where we've got more and more platform independence. And that's wonderful. Platform independence means that that application can go where you want it to go, and you're not locked into any individual vendor. And I think that's a great thing. So there's evolution that has to happen, right? So we've got a lot of orchestration technologies in the market. We've got competing container designs in market. I think that we've largely gotten through the container piece of it, but the orchestration end of it really hasn't sorted itself out. And I think that it has to. So over time, that will happen. And the open source community is great about having competing projects which ultimately find a common theme. And sooner or later, a survivor emerges and becomes the predominant solution. So development of containerized applications. It's a huge thing for the end customer. So for the enterprises in the industry that are building applications for their businesses today, they're all working on containerizing. They want to put stuff in containers.  We'll say, are you using containers? And they say, yes. And we say, great, how many of them have you stood up? And they say, gosh, at least a dozen. Which tells you that they're so early in their adoption. In many cases, the things that they've stood up are these lift and shifts. So I mentioned this previously, but just to underscore, existing applications don't get rebuilt. They get reused in terms of their value, but not in terms of being rebuilt from the ground up. And finally, open source software is the foundation of modern applications. And it's absolutely clear to me that that's really where it's going to be going forward. Training skills, that's going to be a challenge. So that's it. Wrap up my presentation. And thanks for the opportunity to present here. And I hope it's not another eight years before I'm up again. So it's interesting, because your data backs up our thesis, which is the key we want to focus on are sustainable projects that have really good codes, all but a big problem upstream, diverse, rich community that then gets used to create value, whether it's for a service or a product, what you're seeing, people wanting, right? They want better supported open source. And then some of that gets reinvested back into the community, and that's sustainability. So it was interesting to see that data. I really appreciate it. Thank you. Thanks, Jim.


So, all right, so we're here at the best lab at the University of Illinois and our primary duty here is evaluating ag ventilation fans So this is give you a third-party unbiased resource for finding performance data And right behind me you see a fan that's mounted on our chamber Prepared for testing this allows us The two parameters are really interested in when we test fan performance is airflow our volume of air moved and Ventilating efficiency ratio, which is CFM per watt you can kind of think of the CFM per watt as Analogous to the miles per gallon on your car So it's how far do you get or how much air do you get for one unit of energy that's going in? you'll want to that's very important to consider because many times that can be Over the lifetime of a fan the amount of savings from a more efficient fan to a lesser efficient fan This the electricity savings can more than make up for say the the cost differences A cheaper less efficient fan, so you you need to you need to really consider that as one of your main parameters when you're Designing and looking at fans so Another another thing to think about we like to kind of say that fans fans are pumps they pump air instead of waters or other fluids and just like Say a water pump some some water pumps are designed to say a deep well pump that might move a small volume But at high pressure While other pumps are designed to say just transfer a large volume from say one tank to another Where it doesn't take much pressure to move it that the same thing goes for fans in the ag world you've get livestock ventilation ventilation fans that work against very low pressures Where as then on the other end of the spectrum you might have like grain drying fans which have to force air up through You know shelled corn and so it takes a lot of a lot of Energy and pressure to get through that so you you'd want a different you'd want a different fan for each of those applications So secondarily to those airflow and efficiency you want to you want to know how We're here in the the best lab at the University of Illinois in the Ag and bioengineering department we Primarily are interested in doing fan performance tests in this lab You can see behind me. This would be an example of a large summer ventilation fan The the primary characteristics when you're looking at evaluating fans are its airflow and which has measured in cubic feet per minute or CFM and then secondarily we also are interested in ventilation efficiency ratio, which is CFM per watt And you really need to take that into account because that can be a big a big issue in the cost of The total cost of your fan not just the upfront cost over the life of a fan a More efficient fan can often Save and you know cost less over its life including the electricity usage than a less expensive fan that doesn't operate so efficiently so And when we're looking at fans The the other thing you want to look at is how does it operate against different pressures? So a fan is Basically a pump a pump of air And just as we have a fluid pump would pump have different characteristics You often might have say a deep well pump that has to work against very high pressures Doesn't move a large volume, but works against high pressures and you compare that to say a transfer pump that You want to move, you know high volumes quickly from say a tank to another tank or a pond you wouldn't use the same pump because they have different characteristics and the same as with fans with a Livestock building you're going to operate at very low pressures. You want to move a lot of air Whereas another application such as grain drying fans. It's a much higher pressure Operation where you're having to force the air through the shelled corn and so you don't use the same type of fan you want to use a Propeller fan anyway one that doesn't take much electricity to move a lot of volume of air for a ventilation Whereas a grain drying It wouldn't have the capability to move it through the grain at the the characteristics that it has so So that is very important things to think about when you're when you're designing Other things that we don't basically test here in the lab, but you should consider is Maintenance of your fans, which might mean cleaning cleaning of shutters and the housing Studies have shown depending on the level of dirt Losses of flow and efficiency of 10 to 30 percent and in research projects So it's hard to see that loss when you're just looking at your eyes So, you know, that's something you need to keep in mind as far as maintaining your Facilities another thing that you'll also want to maintain is if they are belt driven fans Check for wear on that that you're not losing RPM and So you're not, you know your your fans performance would be downgraded if if you're losing after born drive belts and so forth So Yeah, that's kind of a Or do you just do it on a regular basis like a car? I mean ideally if you could have a Attackometer to measure RPM, then you could you could see that when your RPM start dropping Not everybody has attackometer. So you can Look at them and look for wear compared to You will see they'll physically be smaller and they're with once they wear down in the V V groove So that's that's something to to look at as well So Warren belt you won't be moving the air your building won't be operating as it's designed you won't be moving as much air That might mean that you can't keep the barn cool as and you're it's going to stress the animals if you're not moving enough air and during the summertime if it's Typically we're talking summer ventilation when we're talking belt drive fans. So Minimum most the minimum ventilation for winter is going to be direct drive and you know, that's not an issue in that case I just need those words if your fan belt starts to wear Right and what are the ramifications of a dirty fan so again This will cost you both airflow as in a fan running slow with a Warren belt, but it also Will decrease your efficiency because your fan is having to work just as hard or harder than if the if it were clean So Yeah, so so if you have a dirty fan This can Cut down on the airflow in other words and also the cooling Efficiency of a summer fan and in both Summer and winter fans if it's dirty it will also cut down on How efficiently your fan moves there because it will start to per unit of air you're gonna have to be putting more energy in Belt drive fans you should also you know Maintain bearings as well Typically that's the kind of thing where you it will probably know because of sounds that you're having problems with bearings so but Replacement and some of them need to be greased if they're not if they're not a Sealed bearing sometimes they're Aggressible bearing so they should be maintained on a regular basis Okay, okay in in order to make a good fan selection you need to look at Performance tests that's tested in the lab Because fans just by looking at them. You can't evaluate how well they're operating So when you design a building you will probably have a total volume of airflow that you need to move for summer and winter ventilation So by having the numbers you can you can You can know how many fans you need and that you're meeting that requirement and then You should definitely for your efficiency and looking at electric costs You should definitely evaluate the CFM per watt of the different fans you're comparing to see And and basically what your budget allow generally we recommend get the highest highest level that you Your budget will allow so So when selecting a new fan You'll want to look at performance figures measured measured from a lab To get a third party and to assure they're all tested in the same manner We have a website that that lists fan performance All that we've spoken about as far as airflow CFM per watt and you can look at a full pressure range of these fans as well And I don't know where I'm going from there, but So when evaluating performance of a fan You want to look at at fan test results from from a lab that they're all tested the same way here at our lab We have a website so that you can Uh See online what is available commercially? Look at the airflow rates CFM per watt And and get good hard test data On on results and get good hard test data on results Just say that again And get good hard test data and results Good hard test data on results. Was it on oh, yeah, it was and wasn't it. Oops. I said the wrong thing good hard test data And results Or just do that into that sense again because it just it kind of went at the end. Yeah Um Okay So you want me to start in the beginning kind of you don't have to but you could okay All right now i'm rolling We're at the best lab at the University of Illinois And we're in the fan testing Business here behind me. We have One fan on our chamber So primarily the the main Focus here is we're looking at Two parameters and that is airflow, which is measured in cubic feet per minute or cfm and then also Ventilation efficiency ratio, which is cfm per watt. You can think of cfm per watt kind of like miles per gallon on your car. So it's You know, how much do you get out for what you put in so? The the other thing you would want to consider for these two measurements is Is how does the fan operate at different pressures? Just like with a water pump or any kind of fluid pump Basically a fan is just an air pump. So Just like with a water pump. You have different characteristics. You have Say a deep well pump where you're Pumping against very high pressures to lift the water, but probably a small volume With You might compare that to say a transfer pump where you're pumping a large volume Um from one tank to another, but you don't have to lift it very high. So it doesn't take The kind of pressure to move that to move that and you're moving a large volume With a moderate amount of horsepower to do that We see the same thing with fans. Uh and in agriculture, maybe two applications that would be similar as Livestock ventilation fans such as the one behind us that works at very low pressures, but Moves a very high volume of air And compare that to a grain drying fan which Moves a moderate amount of air against a very high pressure since you're you're moving air through shelled corn and the small voids So If you tried you want to apply the right pressure capability fan to your application If you tried to use a ventilation ag ventilate a livestock building ventilation fan on grain you wouldn't move any air because it couldn't Do the pressure Grain drying fan on a livestock building it could move air But you'd probably use Almost 10 times as much power to do it. So you want to be smart in how you apply your your fans and So that's why that's why you go to test reports and look at the the hard data on How a fan performs how much does it move When a building designer designs a building they'll They'll have a fixed number that they know they need to move of air in the summertime And so when they look at these reports, then they can evaluate how many fans will we need to put in the barn and be assured that that's Yeah, those fans will operate the way they need to operate And then secondly you you do want to look at your cfm per watt because That you know has a big effect and it can Far outweigh the upfront costs of the fan Over the life of a fan, which is likely to be you know at least 10 years um, we think electricity use over all that time the more efficient fan can Typically if there is a difference in cost between Higher and lower efficiency the more efficient fan Can make up that cost typically in its lifetime. So you want to get as efficient a fan as you can To make your dollars go go the farthest so back in So When you are evaluating these numbers that we've talked about we have a tool that we've developed here at the university and a website that That the companies after they've tested their products they can release them to be published And it's ideal because you know that they've all been tested in the same manner So that you're comparing apples to apples This site will give you The airflow and cfm and then cfm per watt And you can click on the complete reports to get the full static pressures that they've been tested at as well At a very minimal static pressure you um Actually can design a fan to get quite high cfm per watt And so if you are certain that you You won't ever see these any higher static pressures. It it can be okay to have You know that that Only operates at low static pressure. The problem is There's always unforeseen unforeseen things out in the field You want you want adequate static pressure because even if your building isn't designed to operate At a very high static there there might be situations where you have a headwind coming into the fans that is maybe like all day long and it's Consistent you want to have a little A little boost, you know a little a little margin for error with your fans so that they can overcome that and not It it may still lower their airflow Somewhat but not just totally knock them down to almost nothing so That's good. Yeah, just in case we need something Thanks anytime Okay, so definitely when you're looking at the cost of a fan. That's not the only thing to consider You should consider your costs on the whole life of the fan and by that I mean Your electricity cost as well because If you look at the cfm per watt of a fan One that is a higher cfm per watt may Cost a little more up front But in one or two seasons you may have enough electricity savings to Actually make up that difference in cost of the fan and then The rest of the lifetime You could actually come out ahead by having the more expensive fan and just saving savings on electricity So you need to definitely consider Cfm per watt and how efficient the fan can operate Yeah, that was great Not really that happens all the time Okay, so do you let's see I'm thinking let's just look at the the main page first Yeah, yeah, so just get back to the So our uh ventilation fans are listed here on our website. Uh, it's best.illinois.edu um click through to get To the ventilation fans Um There are a few tabs to get there And we also have um A full listing of all the different manufacturers here so you can look up fans Um You can specify what's your farm's voltage and power Set up is So that you get the right fan tests all the different manufacturers If you have a specific dealers in your area you want to look up you can just look at say one manufacturers um different fans or you can choose by size A fan by diameter airflow if you know the range of air flows you want to look up in a fan and um By certain certain cfm per watts Or you can just go by the default and everything You do need to select which power you're in but other than that you can just default and pretty much show everything that we've tested So if you go here This is kind of just a summary the database summary page Which doesn't have a full range of static pressures. It has common static pressures that a building will operate in But depending how your building is designed it could be slightly different from this and So if you need to see a complete test report you can Click on the link here. It should pull up a pdf for the full test result One other thing i'd like to mention about this page Is we have over here what's called the airflow ratio We talked a little bit about static pressure and How a fan may perform over a range of static pressures um Some fans will hold up better as the pressure the static pressure against the fan increases So a higher airflow ratio Is ideal because that means the fan is more stable over a range of pressures But again, we can pull up. We'll look at a few A full test. This is an example of a full test report here. It just has a description So that you can be sure it's the right fan you're looking at Did you explain how you get there from the previous page? Yeah, so basically So basically just the first column This is a test number that that's For our files that you link on Um, so if you're wanting this acme model bdr 48 j2c You let you click on that link We'll pull it up Like I said a description page Just to make sure that you're looking at the right fan and then a basic test report with Static pressures from typically from zero to point three Sometimes if a fan isn't capable of the high pressure, it'll be a few less points like zero to point two five And then for each of these it'll provide air flow And and cfm and efficiency and cfm per watt Some of the large summer ventilation fans Um In the past all of the large fans have been belt driven fans. Um, in this case, this is also a belt driven fan here Um, but what we're starting to see is that with some of the new technologies that's available that rather than just Operating at a one fixed speed turning on and off That even some of the large summer ventilation fans which in the past Um had only been single speed fans now Can be operated as variable speed fans So the idea there is that You always operate the fan in in one of its most efficient operating ranges so that its cfm per watt is very high This is done with different types of Drivers coupled with motors Um, some of them at the more of the high value Operations on farms are starting to be used and I see that's suspect going forward that we'll start to see more and more of these But at this time it's typically Used on uh farms that Maybe breeding stock or more high value stock rather than just across the board, but Um, so those are some of the new kind of technologies that you might Might keep in the back of your mind and consider um At ways to Just use just the energy you need to use with the variable speed I think that's um my So to summarize the some of what you need to look for when you're evaluating fan performance Make sure that you're getting actual test data From a lab and You'll want to look at airflow And that's in cfm Uh efficiency in cfm per watt And you want to know across um How does the fan operate over static pressure? You may want to look at what's called the airflow ratio in our summary on the first page This should be as as close to one as possible Indicates a fan that holds up to higher static pressures better um When you're looking at maintenance some of the main niche issues That you'll want to do is is periodically clean your fans Which is typically going to be your guard The housing surrounding the fan And particularly important is the the Shudders or backflow dampers As these Added dirt weight will make them harder to open and cause and take extra electric electricity to open Um extra cost for the for you the end user um maintenance general maintenance you need to Of your belt drive fans make sure that the belts Are not excessively worn you can tell this by Looking at their cross section if they get too narrow um checking bearings replacing noisy bearings If the bearings are greaseable make sure they periodically are lubricating them And um those those can maintain your system so it's operating correctly um And not having to operate for excessive time if it's not moving the air that it requires Did you talk about the shutters again? So as far as cleaning you're just just a general background on it's important to clean the shutters because the weight will okay The shutters are particularly important to keep clean Because the weight of the dust Makes it harder for the the fan work harder opening The shutters which in turn means your fan will operate longer and Use more electricity to move the the needed air So that's that's one thing that's it's very important to make sure you're keeping clean And just how do people do that is just take a hose and spray him down a hose Pressure washer probably don't want to get a pressure washer if you stay back a little ways don't want to damage anything I'm just saying it How people clean these by using uh typically okay Yeah, typically these are cleaned with uh with water hose spray hose typically uh low pressure is fine, but if you pressure washer as long as you're not Um too close to the unit that should be fine as well Great, thank you Okay, so uh for maintenance on a fan some of the things you're want to look at Is cleaning this is of course a new fan in a lab So typically though where you're going to find build up is in the guard Um, that's pretty easy to clean. The other one would be the shutter and the louvers. That's pretty important because Um They open by gravity so any dirt adds weight to them and uh Also dirt in the pivot points on them make it harder for them to pivot Um, so that would be at each end of the louver. So just just wash that off um With water periodically, um the other thing you need to look for where would be its drive belt and uh typically visually once those where you can start to see they get narrower Bearings uh this one The motor is basically internal so you're not going to have to do anything with that This one has a bearing right here. It's it's a this is a sealed bearing Um, so there's nothing for you to maintain on that other than replacing If it starts to get noisy or Some fans are designed with pillow block what's called pillow block bearings that are Can be greased and maintained and in those cases if it has A place to grease them you should grease them periodically How much recommend cleaning it? um Pressure washer is fine. Although it's You probably just the motors are going to be sealed but You may want to like not directly Uh Put get too close to the motor so the pressure isn't huge on the On the motors but other than the motor pressure washer works well Okay, so the shutter Right there Go ahead with the other thing. Sorry. I just wanted to do it while I was thinking about it. Okay Okay So the the shutter is needed in summer ventilation fans because If you cycle fans on and off the fans that aren't on you don't want to draw air in from the opening that is That that that fan creates and it also will close in colder weather So that you don't pull air in through the opening But since they open by gravity and our air flow and close by gravity If they get too much dirt on them that adds a lot of weight That adds to the pressure that the fan has to work against to open it and In other words she Will likely not move air as efficiently And so you're using extra electricity when a dirty fan These are for beginning farmers and ranchers. So we keep trying to go back to the basic basic level Why does why does this even work? So this is your fan chesting chamber? Yeah, do you Run you have uh inster Devices that you take measurements with and so like the gauges Those water filled gauges above those are a pressure To the left of the computer is what we measure electricity with And that's pretty much it the the pressures we measure the air flow By measuring pressures over a known opening inside the chamber


I'm the host of the Tiger technicians are coming up straight after this TFN and noon update down to 203 at 27,848 made an all-time high three days ago at 28,174 where we were talking about a lot of resistance there. This is the first time that we've seen the Dow actually close. I'm sorry, shouldn't say close because it's still the rest of the day to go trading underneath this 14-period exponential moving average, something we've been looking at as a potential for some time. So the key step now is to see the Dow hold 27,600 this week if there's further selling and the resistance now is at 28,000. The S&P is also down quite sharply. It is down 21 points at 3,119 made an all-time high three days ago, 3154 and it too has gone under the 14-period moving average but hasn't closed under it. So the 3,105 areas probably the key support for this week and you've got a lot of resistance in the 3122 to 3128 area. The QQQ, the NDX100 made an all-time high on Wednesday at 206.05 trading now right on the 14-period moving average, the Magnet and Stochastic are pulling back but the most important thing is it needs to hold 201.35 and it's at 202.77 down 2.33, resistance is now 203.90. The IWM which was trying to spearhead an independent rally is actually holding quite well here. It's above the 9-period moving average. It's down to 1.03 at 160.74 but it's about the same percentage down as the others. It needs to hold the 158.62 area by this week and the resistance is now at the 161.90 to 162.10 area. This is going to be very important because gold, which was down sharply last night, down sharply earlier this morning is now down only 4 at 14.68 at the same time as the dollar has taken a huge hit, it's down 46 at 97.82. So I'll be doing more of this, we'll be looking at bonds, the TLT is down huge, down over two points at 1.3836. We'll talk about that in my show coming up, the Tiger Technicians Hour, immediately after this break. I hope you guys have a great day, see you tomorrow.


Modern Love started off as a New York Times column. It became a popular podcast and even a book. Now there's an Amazon TV series, and this is where you can enter the museum of Modern Love interactive pop-up. If Modern Love is a series, we're really trying to drive home to the themes of what Modern Love looks like in 2019. So pulling a theme from each episode, our creative team did a deep dive into what that could look like. And then we really, we focused the agency to bringing those themes to life through photo installations. There are eight different interactive booths for each episode in the anthology series. You can even confess your love, mark where your love is, and write your name on a tree. I really like this tree. The idea being that you want to write your modern family tree. And in a modern world, that looks different for every person. So I think it's going to come together very beautifully. I also love the staircase. I think it's a great, interesting moment that creates a nice social takeaway. Who would expect, you know, you start a little personal essay column and it turns into a podcast and then a television show. And it's really gratifying. I mean, I feel like the time, especially now, is right for true human stories about people caring for each other. I think people need these kinds of stories in their lives. I think pop-ups offer us an opportunity to interact with our customers in a way that we don't typically. And it allows us to create an intimate experience from a really broad marketing campaign. This is the 15th anniversary of the column. We have about 750 stories at this point. So theoretically it could go on for a lot of seasons. I hope it does. I think that the potential for it is really, really limitless. I hope people feel inclined to open up. This is a museum and it's interactive and we want people to share. So it's an intimate and personal experience while also bringing the themes of modern love to life. This is a limited weekend pop-up the show premieres October 18th.


So, these are the azindas that I will go through the sessions. First, we will look at what actually disaster in cloud. Then we will just take a look at how disaster can affect DNS. And then we will just go through what are the disaster recovery, how it comes to rescue. Then we will look at what are the crucial disaster recovery plan that we should make. Then we will go through a brief overview of designate. Then we will see how we can deploy multires and designate, and how we can use it for disaster recovery. Then we will have a small demo, and then we will discuss the challenges. So, let's start. So, what is disaster? Anything that has a negative impact on the company's business continuity or finances could be termed as disaster. Disaster, when we talk about disaster, we talk about anything. It's an event that can bring down your data centers, like tornadoes, earthquakes, fires, sometimes hardware failures, and there are human-induced errors also. So, when disaster strikes your data center, sometimes what happens, the data, you lost data, and data is the lifeline of an enterprise. So, you don't want to lose your data because it impacts on your business continuity and also on the revenue of the company. And if you talk this in terms of DNS, how disaster can affect DNS, we see that when, because our application, most of the applications, they are being resolved through the DNS. So, when just DNS goes down, your site will be inaccessible because the DNS server will not be present to resolve the domain names. And the failed component, sometimes failed component of some DNS servers may cause the mail delivery to be delayed anywhere from few hours to few days. And it literally cripples a global IT operations. And you may lose your customer goodwill as well as your reputation will be lost. And nobody will be able to reach your website when your DNS server will be down, whether your application is up or running. So, I would like to tell you a real incident of a disaster affecting DNS. Back in 2001, Microsoft websites and its other associated companies' websites like Amazon.com, Expedia.com, and Hotmail.com, they had their DNS servers, their four DNS servers on the same network segment. So, what happened at that point of time? Some technician changed the routing table in a way that the outside traffic, no message was able to reach those DNS servers of Microsoft. So, the site was, the Microsoft family of websites were down for 22 hours. And later, it was blamed to be the poor network design that all the four DNS servers were on the same network. So, later it was fixed. And what happened? Just because those 22 hours of down, because all the sites were down, Microsoft families of websites were down, so they lost the incurred a heavy loss. And also there in advertisement also there are other websites, retail websites also lost a huge amount of revenue. So, how we can just prepare ourselves to recover this type of disaster? So, we have really crisis ahead if our DNS goes down. So, disaster recovery comes to rescue. So, what disaster recovery is? The process, policy and procedure for recover of technologies and infrastructure after a natural or human induced disaster. It's a process of ensuring continuity of a set of workloads, following or in advance a large scale disaster that disrupts the current environment or infrastructure. So, actually disaster recovery is basically what makes your IT environment run again following a disaster that really brings down your data centers. So, by large scale disaster as we already talked, which can lead to a complete loss of data centers, like such as floods, tornadoes, hurricanes, hurricanes, fires. And when we talk about the disaster recovery, what we actually mean is that the recovery site should be at a geographically distinct location. So that we will be able to just, at the time of disaster, we will be able to quickly recover by switching to our disaster recovery site. So, this is a pie chart that just depicts the different types of failures due to just the cause of disasters. So, when we think about disaster recovery, first thing that everybody thinks is data backup. So, is that the data backup is the only solution? No, that is not the only solution because data backup is empty. If you have no recovery solution, you can back up the data and metadata to recovery site, but if you don't have any recovery plan, then the disaster recovery of no use. So, disaster recovery is more than simply backing up the data. So, when we plan our disaster recovery, the first thing that the plan begins with is the business impact analysis. And at that point of time, we think of two key matrices. One is recovery time objective and another is recovery point objective. So, what is recovery time objective? It's a maximum acceptable amount of time that your data center will be offline. So, say if your recovery time objective is four hours and some disaster strikes at 7 a.m. in the morning, then by 11 a.m., the workloads that is running should be recovered. And second one is recovery point objective. Recovery point objective, it's a maximum acceptable amount of time in which your data will be lost because maybe your data may be impacted just because of some disaster. So, the recovery point objective is measured in terms of quantity. Note, it doesn't mention the quality of data that will be lost. So, you can see through this graph that if you want to have your recovery time objective and recovery point objective to be very low, then definitely you will have to incur cost. In banking application, this is really required because you have thousands of transactions going in seconds. So, you really want your disaster recovery plan to have RTO and RPO to be very less. Physically, for all the applications, if you want your RTO or RPO to be in milliseconds, that is normally not feasible. So, these are all defined in SLAs. So, another thing that is very crucial while we plan our disaster recovery is ensure that the replicated data and metadata consistency. So, what is data? One is data consistency. It's point-in-time consistency. Means the data should be constant in time. Means if we are backing up the data from our primary site to recovery site, then that data should be consistent as well as the changes that are being made after the backup should also be reflected at the disaster recovery site. So, next is metadata consistency. Metadata, there's all the configurations that we do in all the configurations that are in different components. So, metadata consistency, that the configuration updates, that will be in the same order related to one another and the data updates, and two data updates. Excuse me. Okay, next, let's... because we are going to just plan a disaster recovery in designates. So, let's go through the designate overview. So, designate is a multi-teenage DNS service for OpenStack. It provides DNS service in your OpenStack Cloud. It's providing a REST API by which you can easily manage your join and record sheet in OpenStack Cloud. It's integrated, it's REST API integrated with Keystone that provides authentication, and it can be integrated with NOVA and Neutron for auto generation of records. So, let's have a brief overview of designate architecture. It has API just like another OpenStack component APIs like NOVA and Neutron, which accepts the HTTP request, validates authentication tokens, and then passes the request to designate Central for further processing. So, Central, that is the component where all the business logic resides. So, it talks to database, and also it's also talked to workers, producers. So, here, what the producer does, it actually generates theoretical tasks and send to worker to do the further task. Worker is the component that actually performs most of the work. It performs the creation of zones, creation, relation, updation of zones by performing, by creating zones files across the backends, and accordingly, it's updates. So, backends are just, it's a pluggable, it's a pluggable DNS drivers. So, backends in designate, we have supports for various DNS drivers like Bind, PowerDNS, Dinect, and there are others also. So, MiniDNS, it's a minimal DNS server that is written in Python. Basically, what it does, it actually propagate zone information to customer-facing DNS servers. Now, multi-designate deployment. So, here, we will have two sites, like in primary sites, which is active, and we have the DR site that is on the standby mode. So, because in disaster recovery, when we talk about workloads, we actually, for backup, we take two things, one data and another metadata. So, for storage replication and database we can perform, there are multiple tools through which we can just backup our designate database because here I will only focus on designate disaster recovery. So, I am only discussing about, in designate, what we need to backup so that we can perform disaster recovery at the latest stage. So, we can take database backup and we can have DR middleware like that will keep the metadata, that will copy the metadata from primary site to DR site and keep them in sync at the DR site so that later we can recover that. So, this is a multi-designate deployment. So, here we have, in reason one, we have active designate deployment and in reason two, we have designate in standby mode. So, actually what we are replicating here, we are replicating a database to our disaster recovery site. So, what I actually use for this, it's for because I had a small amount of not very heavy workloads for I just tested it for light workloads. So, accordingly I used MySQL dump that comes with MySQL server and basically what MySQL dump, through MySQL dump, you can take the backup of your database and it actually generates a script through which you can recreate the database at your disaster recovery site just by copying them there and another is for backup replication of the other conflicts like pull configurations and others. I used R-Sync. R-Sync, it's a very efficient, it's an application tool that copies, that copies the files from one location to a distinct location and it's efficient because it has an algorithm, like it uses the delta compression algorithm and that transfer, that performs only the incremental transfer, thus reducing the bandwidth over the network. So, we will have a sort demo in which what I have done, actually I have did it with two VMs, one in India and another one in Japan. So, what I did, I just integrated my designate component with NOVA and you will see in the demo that when I will create the instance, then the records will be automatically generated and we can, at that point in time, we can take backup of my designate database and also we can take the backup of another configurations of designate at the recovery site that will be there in Japan and after that I can just recover from there whenever the disaster strikes at my primary location that is in India, then I can recover from my OpenStack deployment in Japan. So, let's do the short demo. Okay. So, go through the demo. So, basically this is the reason one is my primary site that is active designate deployment and the stack two is my, that is recovery site that is there in Japan. That is my, that's recovery site. So, basically I created one, a June with name example.com. So, it's created and I will perform the necessary configuration for, just for automatic record creation in case any instance is created. So, I restarted API and sync component. So, after this, when I will create an instance, so the designate sync component will automatically listen to the event notification from NOVA and later it will trigger the creation of automatic records according to my configuration that I put in the designate component. So, I created an instance with name test VM. So, we will see that the records will be automatically created in the configured zone. So, I just configured these three records. So, we have two IPv4 records and one IPv6. So, now what I will do, I will just replicate. I'm here, I'm replicating all my designate configuration to a remote site. And I can also just set our sync in my, as a Chrome job by which I can just settle this activity so that my current, my primary site and my disaster recovery site will be in sync. And I also, when we perform disaster recovery, we have to replicate all our zones files. And so, we can see I replicated all our njdev configurations and all the zone files there. I can also take the database dump that will generate a script that I will just replicate at my, take a backup at my disaster recovery site. And there I can just recover all the database and its data. So, my SQL dump at the time of backup, it automatically provides the logs due to which we can mitigate the inconsistency that may happen when the data changes at the time of backup. So, now we switch to disaster recovery site. So, actually I'm just changing the IP address there. So, we have the same pool configurations that were in the primary site. I used bind9 as my DNS server backend. So, these are the script that I just did the backup of. And now I will execute this script so that the database will be recreated at this recovery site as well as the back data will be populated in the database. So, I restarted all the services. I started all the services of designate at my recovery site. Now, all the services started. Now, we will see that now I will be able to list the zones at my recovery site that was there in primary site. That's authentication problem. So, keystone is started. Now, we will see... Now, we recovered the data that we backed up from our primary site. Now, we will see that we are also able to all the record sets of that zones. So, in this way, we can just perform the disaster recovery. We can perform... Because I just did it in a manual form, we can automate this with the help of some Python scripts or we can automate the workloads with some heat scripts. And now we will look what are the challenges that we face during our disaster recovery. So, basically, if we are managing multiple DNS servers with designate, actually, there is no DR plan in place for DNS server. You will have to... You will have to just back up all the zone files and note of all the DNS server. Maybe you will have to just... You will have to redeploy... You will have to just have the same deployment at your disaster recovery site. So, also, there is no favorable procedure currently in designate, by which if some disaster strikes at my primary site, I can quickly switch over, automatically get switched over to a recovery site. And the next challenge is the current plan is incorrect or unreliable. Like, if I'm my school... Like, I was using my school dump to back up my database, but it is good if I have small workloads, okay, like around 5 GB or something. If I have heavy workloads, then my school dump will be of no use. Like, it may take the high bandwidth and low latency will be there. And also, next challenges that I faced during the disaster recovery is the plan includes unnecessary technologies like we can... There are other technologies like we can take... Like, there are RBD measuring or... There are backups available. So, we can just use that instead of some... Instead of MySQL or MySQL or R-Sync for other workloads. And what happens sometimes, the plan has not been effectively tested. Like, sometimes, when we plan our disaster recovery, we sometimes consider... Like, I consider light workloads because we don't have heavy workloads. So, it was actually not able to test my disaster recovery plan on that workloads. So, these are the challenges that I faced during my disaster recovery plan. Any questions? Yeah, I'm also replicating the keystone, but I didn't focus in my presentation because it's a really... Disaster recovery is a big topic, right? Yeah, you need to recover keystone at the recovery site. You mean to say that I should have distributed my workloads, right? Actually, you mean to say that if I'm creating zones, okay, so that will be... Like, it will be pushed to both the reasons, right? And will be in sync. If I create any new records, then that will also be available in another reason, right? You mean to say. Yeah, we can do that with the help of pull configurations. But sometimes it's hard. You say it's propagating with the help of pull. We can just push that zone information to our targets, but it makes the configuration really hard just because of long distance. Maybe it will take time.