Wireless telegraphy means transmission of telegraph signals by radio waves, a more modern term for this is radio telegraphy. Due to its simplicity, radio telegraphy was the first means of radio communication, the first practical radio transmitter and receivers invented in 1894-25 by Glutjelmo Marconi used radio telegraphy. It continued to be the only type of radio transmission during the first three decades of radio, called the wireless telegraphy era up until World War I, when the development of amplitude modulation ham radio telephony allowed sound audio to be transmitted by radio. In radio telegraphy, information is transmitted by pulses of radio waves of two different lengths called dots and dashes which spell out text messages, usually in Morse code.  At the receiver the pulses are audible in the receiver's speaker as beeps, which are translated back to text by an operator who knows Morse code. Before about 1910 when radio became dominant, the term wireless telegraphy was also used for various other experimental technologies for transmitting telegraph signals without wires, such as electromagnetic induction, and ground conduction telegraph systems. Radio telegraphy was used for long-distance person-to-person commercial, diplomatic, and military text communication throughout the first half of the 20th century. It became a strategically important capability during the two World Wars, since a nation without long-distance radio telegraph stations could be isolated from the rest of the world by an enemy cutting its submarine telegraph cables. Beginning about 1908, powerful trans-oceanic radio telegraphy stations transmitted commercial telegram traffic between countries at rates up to 200 words per minute. Radio telegraphy was transmitted by several different modulation methods during its history. The primitive spark gap transmitter used until 1920 transmitted damped waves, which had very large bandwidth and tended to interfere with other transmissions. This type of emission was banned by 1930. The vacuum tube valve transmitter which came into use after 1920 transmitted code by pulses of unmodulated sinusoidal carrier wave called continuous waves CW which is still used today. To make CW transmissions audible, the receiver requires a circuit called a beat frequency oscillator BFO. A third type of modulation, frequency shift keying FS gate was used mainly by radio teletypes. Morse code radio telegraphy was gradually replaced by radio teletype networks through T in most high volume applications by World War II. Today it is nearly obsolete, the only remaining users are the radio amateur community and some limited training by the military for emergency use.


Six states reported 1,786 suspected cases of cholera between June 20th and 26th. Director-General of the Nigerian Center for Disease Control, NCDC Dr Chikwe Ihekwazu said this in Abucha on Saturday. He listed the states as Bauchi, 1,239 cases, Kano, 362 cases, Niger 62 cases, Danfara 55 cases, Kaduna 59 cases and Platu 9 cases. He said that in the preceding week of June 13th to 19th, five states Bauchi, Kano, Kaduna, Platu and Danfara reported 1,757 suspected cases Ihekwazu said that between January 2021 and June 20th 27 total of 14,343 suspected cases of cholera were reported from 15 states and the FCT. He advised Nigerians to boil and store water in clean and safe containers before drinking and to wash your hands frequently with soap on clean water to prevent infectious diseases like cholera.


We have discussed rigid rotor and very soon we are going to discuss hydrogen atom. After that we will talk about multi-electron atoms where we will discuss something very strange enigmatic called spin. And in all these cases one quantity that keeps on coming at us is angular momentum. So what we will do in the next one or two modules is that we are going to discuss quantum mechanical description of this quantity angular momentum. The quantity as such is not very new to us. We are familiar with this kind of a diagram. This is a cartoon that I have downloaded from this website. But in physics we have studied that whenever there is circular motion where the direction of motion is given by the direction of fingers of right hand. Angular momentum is a vector that arises perpendicular to the plane of rotation and is along the thumb of this right hand whose fingers are curled to tell us the direction of circular motion. This is of utmost important because angular momentum is what defines rotational kinetic energy. And when we talk about rigid rotor for example it is kinetic energy all the way. Remember we had reduced the problem to a one body problem so there is no question of potential energy. It is only kinetic energy that we talk about and that kinetic energy is given by you might remember L square by 2i. So let us see what is the quantum mechanical way of talking about angular momentum. And also what we learn in this module and maybe the next is see we have been talking about this theta and phi part of the wave functions. Phi part I think we understand very well because we actually solved that equation. We did not solve the theta part of the equation. But we said we proved that Lz has this e to the power i m phi the phi part of the wave function as an eigenfunction with an eigenvalue of mh cross. So we said that the z component of the angular momentum of rigid rotor is mh cross. And then we said that the total angular momentum is h cross square multiplied by j into j plus 1. This is something we are going to use in hydrogen atom also. What we have not really explained is why is it that there is an upper limit of the values of m? Why is it that there are 2j plus 1 values of m in this module or maybe the next we will get to learn that. And initially I did not think I will go that far. But now I am tempted to also talk about ladder operators in angular momentum. Remember ladder operators in rigid rotor. Similarly we can talk about ladder operators here also. And I am tempted to go a little further and talk a little more about energies and wave functions. Let us see whether we get there but at least by the end of this discussion we will get to know why there is an upper cap of the values of m. And also we will get to encounter a very, very important phenomenon in quantum mechanics which involves operators that commute with each other. What is the meaning of commute? I guess you know. But in any case we are going to talk about it. So, here of course. Let us start at the very beginning. And since I have got a feedback from many of our potential students that they would like to have things done from scratch as far as possible. We will start at the very beginning here. We will talk about the classical description, the classical definition of angular momentum. As you know angular momentum is defined as the cross product of r and p. l is equal to r cross p. What is the meaning of cross product? Magnitude of, well first of all cross product is a vector product. Magnitude is given by r well magnitude of the 2 vectors multiplied by each other multiplied by sin theta. And what about direction? We have already talked about direction of the angular momentum vector. Here what we will do is we will work with the components. So, we can write like this that x the position we can write as i multiplied by x well r sorry r the position r is the position vector. So, length of the position vector is given by i multiplied by x plus j multiplied by y plus k multiplied by z. Perhaps I do not have to explain to you what ijk are but I still will. i is a unit vector along x axis, j is unit vector along y axis, k is unit vector along z axis and x, y, z are the magnitudes of the x, y, z coordinates of the point we are talking about in the first place. I hope that is clear. Similarly, p is defined as i into px plus j into py plus k into pz. Please remember these are vector sums i, j, k are vectors that is why I have written them in bold and italics. And px, py, pz are the x, y, z components of momentum, linear momentum x, y, z are x, y, z components of the position you can say. So, these are vector sums please do not forget. Now, when I take a cross product between r and p what I really have to do is I have to take a cross product between this and this ix plus jy plus kz and i px plus jpy plus kpz. While doing that how many terms will I get? Well 3 into 3, 9 terms let us take them in groups. First of all what you see here is the i cross i, j cross j, k cross k terms. The cross products of the same vectors, same unit vectors.   What i cross i, j cross j are we will come to that shortly. And I am hoping that most of you know anyway still in case you have forgotten or in case you have not come across this we will do it. What will the next term be? Next term what we can do is we can take an alphabetical order i cross j, j cross k, k cross i. So, i cross j term what will it be? ix cross p y plus jy, well j cross k will be multiplied by ypz. So, sorry I will say that again. ix cross jpy will be i cross j multiplied by x dot py. Remember x and py are just magnitudes. The direction is given by the direction of the unit vectors i, j and k. So, then kz cross kpz would well sorry i cross j, j cross k and k cross i. So, kz cross ipx would be k cross i multiplied by zpx. This is what it is. Sorry for the overlap here was not like this, but anyway sorry about that. i cross j multiplied by xpy plus j cross k multiplied by ypz plus k cross i multiplied by zpx. So, we have got 6 terms out of the 9 that we promised would be there. What would the last terms be? We can take the reverse order alphabetically. We have taken i cross j now let us do j cross i. We have taken k cross i now let us take k cross j and let us take i cross k. So, this is what we will get jy cross ipx that gives you j cross i ypx. Then kz cross jpy gives you k cross j multiplied by zpy. Why am I saying j again and again? kz cross jpy gives us k cross j zpy and finally ix cross kpz gives us i cross k xpz. These are our 9 terms. Fortunately not all 9 terms exist. I am sure most of you would know that cross product of same vector is actually 0 sin theta remember I said that magnitude contains sin theta and of course the angle between i and i is 0. So, sin 0 is 0. So, i cross i is equal to j cross j is equal to k cross k is equal to 0. So, this first 3 terms in i cross i j cross j and k cross k these are going to become 0 and therefore vanish. We are left with 6 terms i cross j xpy plus j cross k ypz plus k cross i sorry about this plus j cross i ypx plus k cross j zpy plus i cross k xpz. Maybe I will just correct this for you otherwise it is difficult to see that is much better.  Now we need to know what is i cross j what is j cross k so on and so forth and that is also very well known these are unit vectors remember. So, unit vector means magnitude is 1 and i j k are perpendicular to each other. So, when you take cross products of say i and j you get the third one i cross j is k j cross k is i k cross i is j when you take them in the right correct cyclic order you take them in reverse cyclic order instead of i cross j you write j cross i it just becomes minus k xyz it becomes minus z something like that k cross j is minus i and i cross k is minus j these are very standard things that one learns while studying the chapter on vector in high secondary mathematics. Good. So, let us start substituting the first term we have is i cross j instead of i cross j we will write k second one is j cross k what is j cross k j cross k is obviously i is very simple I mean you just write the third one if it is in correct cyclic order you write plus sign if it is in reverse cyclic order you write minus sign. So, j cross k is going to be i k cross i correct cyclic order is going to be j now j cross i is reverse cyclic order right in alphabet i comes before j. So, you are going to get minus k k cross j similarly is minus i and i cross k is similarly minus j. So, now what we can do is we can collect the terms in i and j and k and we can get instead of 6 terms we can get 3 terms. So, if I collect the terms in i what do I get i multiplied by y p z minus z p y is not it j multiplied by z p x minus x p z and k multiplied by x p y minus y p x right. So, i into y p z minus z p y j into z p x minus x p z and k into x p y minus y p x what I really need you to do is please make sure you have a pen and paper in your hand when you attend these modules you should keep writing that way you understand better if you just look at the screen you may get it may not get it of course the advantages is that you can pause me and you can write do it no problem but please write when you are hearing otherwise it is then it will register better the more senses we use while studying better we grasp it that is a very well known phenomenon.  So, now see what is this that right hand side is an expression for angular momentum. So, obviously whatever is multiplying i is the x component of angular momentum whatever is multiplying j is y component of angular momentum whatever is multiplying k is z component of angular momentum. So, we can write l x is equal to y p z minus z p y very nice right y p z minus z p y and what is that equal to l x. So, you can think like this if you think of three random variables I cannot use i j k and I cannot use x y z.  So, we cannot use let me say 1 2 3 that is better. So, you can think like this when you talk about the components l 1 is equal to i into 2 p 3 minus 3 p 2 plus j into 3 p 1 well sorry l y. So, that is your x component right l 1 is equal to well that holds for everything actually l 1 equal to 2 multiplied by p 3 minus 3 p 2 this is a general way of writing your x y and z components of angular momentum. So, let us write that this is what we have one way in which we can express very nicely and we are going to come across this tool in some other context also is determinants. I hope we all know what determinants are if not please brush up it is just a way of writing sums like this. In a determinant what you have is if you have something like you just write once in case somebody needs to know how a determinant is written I will just write it once this is a determinant you write like this say a 1 1 a 1 2 a 1 3 a 2 1 a 2 2 a 2 3 a 3 1 a 3 2 a 3 3 this can be anything we will just see an example of a determinant that is useful for us. But this is what a determinant is and what it means essentially is you take a 1 1 multiplied by this a 2 2 into a 3 3 minus a 3 2 into a 3 3 a 3 2 into a 2 3. So, this determinant will be a 1 1 into a 2 2 into a 3 3 minus a 3 2 into a 2 3 then next term is in a 1 2 but a 1 2 the second term has a minus sign.  So, what you do is you are leaving out this column and this row whatever is left in that block you take cross product and subtract the other diagonal product. So, a 1 2 is in is in the first row and second column.  So, leave those out it will be a 2 1 into a 3 2 minus a 3 1 into a 2 2 a 2 1 a 3 2 minus a 3 1 a 2 2. So, this is how determinant is written and if you now compare this what I have written here by hand with what I have here you can correlate a 1 1 in this case is i a 2 2 is y a 3 3 is p z a 3 2 is z a 2 3 is p y a 1 2 is j a 2 1 is z p x a 3 3 sorry a 2 1 is z a 3 3 is p x sorry this is there is a minus sign here. So, this has to come here. So, a 2 1 is actually x and a 3 3 so this way you can just correlate with this and we will just write it in the determinant form before that let me erase this. Now, let us show you the determinant here this is what it is. So, i j k x y z p x p y p z very nice. The way we have written it is that the first row is just the unit vectors along x y and z the second row is the x y z coordinates position third one third row is p x p y and p z the components of angular momentum along x y and z. So, very nice systematic way if you go from left to right you go from x direction to y direction to z direction if you go from top to bottom you go from the unit vector to position to momentum it is very nice systematic way of writing it and this is how it expands y p z minus z p y j into z p x minus x p z remember j had a minus sign. So, that has gone in plus k into x p y minus y p x this is what the determinant is. Now, we know the x y and z components already these are the x y and z components the other quantity that is very important is l square square of angular momentum and you will appreciate it even more when we go into quantum mechanical description. That is given by l x square plus l y square plus l z square I hope I will not work this out explicitly because I have worked out the other one you can do it yourself but remember when you try to do l dot l that is a dot product first of all. So, it will be a scalar product no direction but then you have to take i into l x plus i j into l y plus k into l z take dot product of that with itself while doing that you have to remember that i dot i is equal to j dot j is equal to k dot k is equal to 1 and i dot j is equal to j dot k is equal to k dot i is equal to the same thing written in the other direction is equal to 0 because dot product has cos theta in the expression. So, if angle between the two vectors is 90 degrees then of course you are going to get 0.  So, this is the classical description of angular momentum. Now, let us just build the quantum mechanical description and then we will end this module we will go to the next module for the next part. So, quantum mechanical description is as you know we start from the classical definition and what we do is for every variable every observable that is there we replace it by the corresponding operator. So, if you want to write this matrix what do we have to do we have to replace x by the position operator x which is just multiplying it by itself you have to replace p x by the momentum operator p x hat. So, these are the two rows in which this determinant is going to look different but mean the same when we try and build a quantum mechanical description while doing that x hat is very simple remember p q hat where q can be x or y or z is h cross by i del del q or you can write minus i h cross del del q in the later part we have actually use that minus i h cross it means the same it is no big deal do not forget. The way I remember it is that where if i is in the denominator then it is positive if i is in the numerator then it is negative h cross always is in the numerator of course. Now with that let us try to build try to write a similar determinant for the L hat operator the angular momentum operator what will it be it will be something like this first row remains the same i j k second row also remains the same in the third row you are going to have h cross by i del del x h cross by i del del y h cross by i del del z. So, you might as well take the constant h cross by i outside the determinant because the determinant multiplied by a constant is what you get and then the x component very similar to what you have there instead of p z you write p z hat that is all instead of I have made a mistake here sorry about that this is not z y hat it is z p y hat of course it is obvious but it is a typo let us see if I have repeated the typo later I have not L y is equal to L y hat is equal to z p x hat minus x p z hat please do not forget that this is actually p y hat this is a typo here maybe I will just write it with my pen so this one I will cut and I will write p y hat for you good L z hat L z hat is x p y hat minus y p x hat these are the operators for L x and L y and L z components and these operators are extremely useful you keep on using them in many situations later on. So, L x you can write like this instead of p z hat you write this del z and this is similar. Now what is what about L square operator L square operator for that you have to simply substitute this by L x square L y square L z square and that will come from these L x operators so I am not working it out explicitly we will do it whenever required but please remember that we have to build an operator for L x square L square also in fact that is the most useful operator I am not doing it because we are not going to use the Cartesian form we are going to use these spherical polar coordinate form remember your rigid rotor problem or any problem where rotation is involved angular momentum means rotation some sort of rotation would be there notionally yes even though for hydrogen atom we say that we cannot talk about rotation but still angular momentum is there same for spin but we will cross those bridges when we come to them but what I am saying is this L square operator is actually of utmost importance that is what we work with and we always use this spherical polar coordinate form which we do not have to remember we will give it to you but since we are talking about spherical polar coordinates form it makes perfect sense to show you what these L x hat L y hat and L z hat operators are for in these spherical polar coordinates this minus i h cross multiplied by minus sin phi del del theta minus cot theta cos phi del del phi this is L x hat operator sometimes I make mistakes in writing these expressions so please cross check with the book this part you can study from Piller's book but I have followed Macquarie not Macquarie and Simon physical chemistry Macquarie quantum chemistry book or Prasad or any book that you are comfortable with but please double check and make sure that whatever is there is correct it should not be that I make a mistake while typing here and then I do not notice it and you learn the wrong expression that should not be the case this is L x hat next we have L y hat very similar instead of sin we have cos instead of cos we have sin L z hat fortunately is very simple i h cross del del phi why is L z hat so simple because remember what is phi we have talked about this by talking about rigid rotor changing phi essentially means circular motion in the x y plane so the associated angular momentum has to be in z direction so that is L z hat and it makes perfect sense it you can correlate it you can correlate say L z hat the angular momentum operator in z direction with the linear momentum operator also they are very similar isn't it this h cross by i or minus i h cross del del q you can even write this as h cross by i del del q if you write q equal to phi very similar what linear momentum is in linear motion angular momentum is in circular motion it is very important to get these correlations right and sometimes students ask this question how do I know how do I know which is x axis which is y axis which is z axis and the honest answer to that is that we do not we define one direction as z if we have an external perturbation like if we apply an external field electric field or magnetic field then of course we define that to be z axis why because then we have to deal with an easier operator okay so it is of course in our hands but you will see that we will always work with the z direction because it is easier to handle okay maybe we will stop this module here and continue from here in the next module


Okay, so we've thought about connective tissues in general now. Our next goal is to become familiar with some of the different kinds of connective tissue. We just want to take a few minutes and look at the different kinds of connective tissues collectively and then we'll look at each one in more detail and talk about the structure and its function. So now we're just going to do sort of a quick overview so you can see them all together in one place before we move forward and get into all the details. So types of connective tissue, I've listed some of the connective tissues that you need to know and I've listed them in an order that sort of makes sense to me as I try to remember them and so I'll explain that to you and maybe that will help you. I always start out with loose connective tissue. Sometimes it's called areola or connective tissue. Loose connective tissue is exactly what it sounds like it is. It's a connective tissue that's very loosely put together. In other words, there's a lot of space between the cells, there's a lot of space between the fibers. Loose connective tissue has a liquid ground substance. Loose connective tissue is found in many places throughout the body. It's found under the skin, for example. It's found between muscles. As one muscle is touching another muscle, they need to be able to slide across one another and so we find loose connective tissue there. We find loose connective tissue just deep to the epithelial tissue lining your alimentary canal and there are a lot of blood vessels that move through loose connective tissue and nerves and so that's a good place to have this loosely structured tissue. So loose connective tissue. A sharp contrast to loose connective tissue is dense connective tissue or fibrous connective tissue and it's exactly what it sounds like it is. Fibrous connective tissue is made out of a lot of really tough, collagenous fibers or sometimes it's called dense connective tissue because it's densely packed together.  That's dense connective tissue and you know how tough that is. Adipose tissue is something that we find in animals and it's also called fat tissue. Adipose tissue stores fat and it can be very useful. Adipose tissues involved with cushioning, protecting, insulating in a face-to-face class I often ask students to name animals that have a lot of adipose tissue and the number one answer is usually a well and they're somebody will say bear or walrus and if you think about those animals they have a lot of adipose tissue to help insulate them against the cold. I think most people are familiar with bone tissue. You know you have bones in your body and they're very rigid. They have some flexibility but certainly your bones can break and many of you may have broken bones at some point in the past. Blood is an important type of connective tissue and most people are familiar with blood. It's something that you don't want to lose. If you spring a leak you want to stop that very quickly and so blood in contrast to bone is liquid, it's not a solid. We also have cartilage and there are three different kinds of cartilage that you need to know about. One is called hyaline cartilage, then there's one called elastic cartilage and one called fibrocartilage. Hyaline cartilage is very common, it's found in your trachea, if you palpitate your throat and you can fill the rings in your trachea or your windpipe, it's also found at the end of your nose. Elastic cartilage is just what it sounds like it is. It's cartilage that can stretch, it has a lot of elastic fibers. If you take your ears and pull on them really hard and let go they're going to spring back and your ears contain elastic cartilage. And finally we have fibrocartilage which is what it sounds like it is. It's cartilage that has a lot of fibrous connective tissue or fibers in there made out of collagen. And this fibrocartilage is extremely tough. It's able to take a lot of stress and a lot of shock and we find this in places like your knees and in the intervertebral disc. These are the connective tissues that you need to be familiar with and in the next segment we're going to look at each of these tissues and talk about their structure and function in more detail.


Imagine you've heard that some chocolate contains the toxic metal lead, which some does, by the way. As an avid chocoholic, you do a quick Google search and come across LeadWatch. LeadWatch is a device that plugs into your smartphone and tells you whether the lead in your chocolate is above the acceptable level. LeadWatch doesn't actually exist, but it could do in the future. Using LeadWatch, you're happy that your chocolate habit isn't leading to excessive lead consumption, and all is good with the world. A year later, LeadWatch 2.0 is released. This version warns you when your chocolate lead content is 100 times lower than the acceptable level. Eager to consume as little lead as possible, you purchase LeadWatch 2.0. Some of your favorite chocolate products you previously thought were okay now show the presence of lead. You quickly ditch these, but are comfortable in the knowledge that the rest are safe. Then, Ultimate LeadWatch comes out. This latest iteration claims to detect even a single atom of lead in the chocolate you are eating. To your dismay, every piece of chocolate you test now appears to contain lead. Disaster. You have just hit the measurement conundrum. The chocolate you've been eating hasn't changed. All that's changed is your ability to measure what is in it. Does this mean that what you assumed to be safe is now not safe? Not at all. Just because you can measure something doesn't necessarily mean that it presents a risk. The measurement conundrum is real. When we can measure something we couldn't measure before, we need to know what to do with the new information. In some cases, this might mean reevaluating what a safe level is. In others, it might mean recognizing the difference between what we can measure and what is okay. In both cases though, we need to know what the measurements mean, not just what they are. For more information on lead in chocolate, check out the links below and stay safe.


Hi everyone today. We're making chicken salt and bokeh and I'm going to serve it with some cauliflower rice and some grilled up asparagus for a delicious meal and Salt and bokeh in Italian actually means it jumps in the mouth, right? So it's going to be jumping in my mouth and right down the hatch because it is really delicious So I'm rockin robin and I'm going to show you how to make it right after this Before we get into our recipe though I want to encourage you to hit that subscribe button and the notification bell so that you won't miss my new videos Coming out every week and we're always putting out something super delicious and my focus is on eating healthy That's that's what I like to do. I read labels. I'm concerned about the quality of my food So if that resonates with you be sure and hit that subscribe button.  Now once you do that, we're going to take our chicken breast We're going to sprinkle it with just a little bit of fresh sage and then we have our prosciutto Now prosciutto is an Italian pork product very very thinly sliced It's like paper so it comes on these little pieces of paper and you just peel it off And I'm not going to add any salt or any other seasonings to our chicken because you don't need it The prosciutto is going to provide all of the seasoning that you're going to want to need. All right So we'll just wrap this up And I'll set it aside. We are ready to start dredging our sultan bokeh. All right So I have some gluten-free flour here and you just want to set it in there and coat it lightly We're not trying to you know get a big covering here or anything thick We want it actually very light so you can just kind of rub it in and then just kind of pat it and shake it off Okay, that's good. I'll place it on another plate And when I start to fry them I'm going to fry them in the pan with the seam side down that way that seam will You know kind of seal up as it gets crispy and it'll stay together better now Like I said, you can use regular flour, but I'm using gluten-free flour here today. I'm using Bob's red mill It's a one-to-one baking flour works great Now we're going to head over to the stove. This is only going to take a few minutes probably four to five minutes per side And of course we're going to be cooking up our cauliflower rice and our asparagus So here's our setup. I've got this pan right here. This is going to be for our cauliflower rice This is going to be for the chicken and this is going to be for the asparagus Now what you did with the asparagus all we need to do is to season it up is add a little bit of olive oil to it Mix it up with your hands and then give a little season of some salt and that's all you need to do So I'm going to start off with the cauliflower rice. It'll probably take about seven or eight minutes to cook not very long Everything is pretty quick. Actually the chicken is the same way. So I'm going to take some olive oil and Place about a tablespoon or so in the pan.  I'm keeping it simple with the cauliflower We're not doing too much here. We're going to get all our flavor from our sultan balka I'm going to let that go for a few minutes. I think my other pan back here for the Asparagus is probably pretty hot and I should go ahead and start cooking that which will just take a few minutes as well So this is one of these recipes where we're kind of doing three things at once But it can be done. I'm going to test my pan just sprinkle a little bit of water on there You hear the sizzle. I think it's ready to go So I've got my nicely seasoned asparagus. I'm just going to place it here on this grill pan My temperature is about medium When a cast iron pan gets hot sometimes you need to turn it down a Little bit so we'll keep an eye on that. We'll just rotate them over as they cook Okay, we'll give our onions here a little bit of a toss We're going to do this for just a two or three minutes. That's all just a little bit All right, I'm going to add the garlic and we're going to saute that for one minute Now it's time to add our Trader Joe's. I got my Trader Joe's rice cauliflower Just toss that in I'm going to add just a little bit of salt to it And I'm going to toss in a little bit of chicken broth now because cauliflower that you buy already riced is a little bit more firm Because they use more of the of the stalks of the cauliflower than when you do your own when I make my own I I include mostly just the florets and very little stock So it's it cooks up quicker. This takes a little bit longer to cook And then I'd like to also just put a lid on this a little bit and go back and check my asparagus Just rotate them occasionally when they start to brown up So turn the heat down on the cauliflower to low and then we'll cover it and we'll cook it for just about two minutes That's it Got our stainless steel pan over medium-high heat. I'm adding some olive oil to that about two three tablespoons Let that get hot and then we're going to add the fresh sage Leaves to it add some nice flavor and let that cook up for about two minutes All right, I'm going to check the cauliflower. It looks nice and soft. It feels like it's soft So I'm going to turn off the heat and just keep it warm. I'm going to check the asparagus now It's coming along nicely. It's just about done as well. I Like mine, you know a little bit crispy firm, you know, not not real soft All right, our sage has been cooking along here getting crispy and nice Now I'm going to add I'm going to add a little bit of butter to the pan Add some nice flavor there As soon as that butter melts we're going to add our chicken now when you lay it in there lay it in real careful Make sure your temperature is about medium. You want it to crisp up. That's the whole idea here We're going to cook these four to five minutes per side So we're getting close here to turn this over and you can see I think on this piece here how it's getting white up about halfway And that's that's a pretty good indication that we're ready to turn it over and it's been about four four and a half minutes One thing about chicken breasts. You don't want to overcook it because then it dries it out All right, so when you turn these over Do it carefully We got our sage here getting nice and crispy So we'll go for another four to five minutes here. I'm going to check it with an instant read thermometer Just to make sure that the internal temperature is 165 Chicken's almost done I'm going to take the cauliflower rice and if you've watched my channel enough, you know that I love a basil So I'm going to sprinkle some basil in here to use parsley if you if you want the sultan bokeh is done Let's take it out. I've got a plate here behind my pan. I'm going to just lay it right in there and I want to make sure I get my Crispy sage so we'll just take these out and we're not done yet folks because we are going to make a little pan sauce To put over our sultan bokeh you see all those brown bits on the bottom of that pan. That's what's going to make this thing taste amazing Okay, so you want to check see how much you have that that's not too bad That's you know, you don't want too much grease in the bottom But that looks just right So to the pan i'm going to add just a little bit of onion Love my garlic I got my temperature right now. It's kind of on low medium low cook that up a bit for about three minutes Let me get my wooden spoon here so we can scrape the bottom of the stainless steel pan I'm also going to toss in a little more sage into our little pan sauce here So I've got some more chopped up and I'm just going to add some to it We're going to add some white wine. I have some sauvignon blanc here I'm going to pour that in I'm going to turn the heat up just a little bit because I cooled the pan down And bring it back up to medium And we're going to cook this until it reduces down to about half of what you see there I'm also just going to take a piece of foil and just lay it gently over the top of the chicken so that it doesn't cool off Now we're going to add a little chicken broth I'm using the trader joe's organic because I like their ingredients. They're pretty pretty decent Turn this back up Bring this up to a boil again And then we're going to simmer it until it reduces down by half which will probably take another five or seven minutes And I'm going to add just a touch of salt not too much just a little bit All right, our sauce has reduced down enough I like to have enough for all my chicken. I'm going to add a little butter to this and it has a little salt in it So we're just going to place this in there. It's going to make it nice and silky once once I stir this in Then our sauce is ready and we're ready to serve it up Now if you want you could put your chicken back in the pan. In fact, maybe I'll do that If it's cooled off any it can reheat a little bit This smells so good in here. You can't believe it. And what a quick meal to put together It doesn't take long at all the cauliflower everything that I made only took seven eight minutes to do In the actual cooking time, right?  Here we go.  It's a little bit too soft, but it's still so yummy the sauce the pan sauce in this Just phenomenal So delicious guys Thank you so much for watching. Don't forget to subscribe to my channel Share the video and you know, leave me a comment. Let me know what you think about it. Try it and you know, let me know All right. Thanks for watching everybody. We'll see you next time


いただhope සි,력c and ven reason. � ඒන් මුරු ,in whee prounc space. මේික්ය, එන් පද. ඃෙයෙෑයය සෙය්ක්ය හොඳිල්ීද, අ lifelong and fun,tuber� නල්,iving genes. සෙහතය ḝ llama ḱᵃ Mad – emment – Ḥ�energy Ḥ ᶫᶱᵏ ᶒᶏᶔ ᶰ ᶁ Ḭᶼᶕᵋ ἕᶱᶡᶚᶠᶉᶉᶂᵍ Ἕᶜᶦᵀ ᶜᶠᶼᶫ ᶑᶎ, ᵋᶸᶒᶅ ᶙᶦᶠᶉ ᶀᶘᶋ හිරිුව Grandma හිරිෝ කෙවේ, МУවයිරුයයුවින් ඇලෙයය෋තාpe ගහල් කිරයිට මට,වගේය ගති†,වරැඩෙයා,ඕය,හළවිකය්такේ පේර මේ මියයුවය කරියික්,වර්යල� Whoever හොල්ය බෝශ because they can do, when they know and want to be part of the reason, who are we going to stay in the kind of space that we're going to be stuck in. And the other reason why this happens is that the powers of the public are the same. Even though you are looking at that. Yes, I mean, what we need to find a way about is what they call a part of our needs. But they're not right about exactly how to solve that problem. So, whatever you need to make a reason or whatever they describe how they're made, that is all they need to know. And if you find a part of your needs, however you talk about what you think is the most important part of the reason to understand the power to solve their needs, what you need to find a reason to understand the power to solve their needs. And this is what we need to find a reason to understand the power to solve their needs. And if you're looking at the same thing, what you think is the most important part of the reason to understand the power to solve their needs, and the more important that we are in a time where we don't have a reason, but we do have a reason to keep doing the same things, where we got to keep using what we call revenue. And if we are losing the amount of work that we have to put to save the support, which costs us, but not as much money as we have to, Təafer nətəm də ə alëbə q 20 nətʒəngə əliəm əlləm əniər rəək-sə relocbase kiğ grəpjət rəka ə ekrə��jnə iəm sə Knock-səmvə əlləmət əlləma아 patients əlləm əlləm q 7 əlləm ə sə Nətərəm q 7 əlləm də ə Swe yaptə roun'n gətəm əlləm q 7 əlləm qìtəhəm fətəɾənjət tʃəfətəm акти affinity contacts and our members, as well as direct members of ourdimension committee, Now, first of all,letting out my words to the comfort of the Japanese people  jokes about the modern deUCKin-lookers who wereSunnisers in the Northern J blind, � évំទ៊ម៍៎ៀ ៅៅៅមំ៎ះៀ២ម� ᔀំ ៀំ់០០ៀ៊ ៀំំ៎ ᠂ោំះោ្៉ Ink ់ៀ្s ំ� save ៅៅ្s ៊្s two 30 11 second bell at bottom k стал  ḽ Ṣ� évɤ ɛ ɛ ɛ ɛ ɶ ɟ ʉ ƒ ʉ ɛ ʒ ʉ ɛ ɪ ɛ ɢ ɛ ʊ ʉ ɒ ɛ ʉ ʉ ɒ ʒ ɛ ʋ ɛ ɛ ɟ ʃʖ ɛ ɟ ɛ ʄ ɛ ʔ ʒ ʋ ɛ ɛ ʒ ʔ ɛ ʒ ɛ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʊ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ʔ ᠜ჴ·წ჉ჱაღნაცცლვ. სჰვაყსგ შჰრძეყ ეძაეკმჄვ, გლი჌იიიიიიიი რეიიიდი჋ი can't move anymore than we only are in the SAC. რიიიდიი reservoir SurvivANG. მშრქჾბ჏ფკ' ჼ჉ შვთგ' ნ'dეე თწided წრვpeople සහසී඲ිට වහැතිඩි, වහැතියක්වැ මිශ්බවික්, වහැසාසිය කිසාන්විඳා.º වහැතිඹියක. ආාදුදි, සහැතිියක්වන, සේණයක්නවිඳයක්. ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ ḍ � And, in general, this model, thank you, is fixated on all of the selected users have selected滿format or these web direction points for disaster. Okay, I think it's a appropriately pauper. So, we're kind of, you know, having god, you mean god that defines everything in the community, kind of represents, which is why we're talking in terms of current law as well, that has the same ää triggering mechanism it would be ᴅagit likely for experiencia or ᴅager, but it is very important that people look for new wyring ᴅag investment in awriter.


Hello. Yeah. Good morning. How are you? I don't think we have a lot of people probably joining today because it's kind of close to the holidays. But in any case, the presentation is being recorded, so it will be uploaded. But just let's give it like maybe a few minutes to see some more people join and then maybe we'll get started. Cool. So are you in the east coast? I'm on the west coast. I'm in California. How about you? I'm in Bay Area. Oh, great. Awesome. Yeah, me too. Yeah, I'm asking because of the timing. The timing is a little bit earlier for west coast guys. Yeah, but we get audience from several places. So yeah, we do have a bunch also in the Bay Area too, but also people from other places. So we have a Lena just joined. Morning. Hello. Is everybody ready for the holiday? Yeah, yeah. I think I might not get that many people today because a lot of people are just kind of checked out, you know, for the holiday. Yeah, a lot of meetings have been canceled. Like we had a TOC meeting canceled on Tuesday and next week we're not having it either. Yeah. So I'm sure nothing's going to go up. Nothing's going to happen next week. Yeah. I guess the week after. And then it's 2021. Yeah. Yeah. That's wait a couple more minutes. We're gonna get started. Yeah, before the meeting starts, maybe Ricardo, you can briefly describe what this thing is about because I know a lot of six. Yeah. Yeah, so, you know, the sick notion, I think started with Kubernetes, right? They would all the different scopes of Kubernetes, like signal, the SIG network, SIG API machinery, I think. And then because the CNCF started to grow, I mean, the CNCF started with Kubernetes, right, but the CNCF started to grow and different projects started to join the foundation or started to be donated to the foundation. And then it was all cloud native but not related to just Kubernetes, so different areas like observability, application delivery, like CI, CD, continuous deployment, continuous integration, and also on the networking side like envoy proxy. So I think this, and then the CNCF has or had this structure with the TOC where they looked at these projects and they reviewed them and they decided whether they would be a good fit for the foundation and then with these stages like sandbox, you know, incubation and graduation. But I think what happened is that so many more projects started to get interested in joining the foundation and the TOC became kind of overwhelmed with all these different requests and and then the meetings were only like, I think, twice a month and so there wasn't enough room to provide to the community or provide time for the community to present and engage the projects. So they started these six, you know, with the different scopes, right, with networking, runtime, you know, CI, CD, and yeah, and this is where we are, right. And so we help out the TOC and engaging more the community with the different projects and so they can present and give a status on some of the projects. And some of these projects are not even part of the foundation. So they may join the foundation or they may be part of some other foundation, but we just want to engage the community. So there's more engagement and excitement about all the cloud native space. Yeah, sure, sure. So I'm guessing, but other people may ask, so what's the difference between this thing and the colonnades is sick. Yeah, yeah, yeah. And I think there's a ticket open from, I think Liz, she's a TOC chair and she opened a ticket on renaming some of the six. So it hasn't happened and something may happen next year because there's confusion about what between the naming, you know, this is called sick and the Kubernetes is also called sick. Right. So, so we might change the name. I don't know, sometime next year. Sure, sure. Okay. Yeah, we can get started. We got Quinton. Happy holidays. Thanks for joining. Yeah, we can get started. Okay, let me try to do this. I was on mute. My apologies. Yeah, I was saying good morning and apologies for not having seen you for so long. It's been a great year. How's everyone doing? Good, good. Are you in a boat or something? I am, I am. Nice. Can you see the screen? No, not yet there. Oh, I know what happened. I need to click this year. How about now? Yep, yep. You see this nice. Yeah, sure. Before we start, I actually just sorry I joined a couple of minutes late. I just wanted to check in. We have very few people here is basically the chairs and and the TOC representative. Do we, is this a general problem or is this because it's late in December or do we need to do anything about that? Yeah, I think it's one of the reasons it's late in the, in December, but we could use more audience to write during even November, I think it was, you know, generally like eight or people. Oh, okay. After, after coupon fatigue, a lot of people have checked out for, for a couple of weeks. Yeah, I can quite imagine. I was, I struggled personally to get in here, you know, the, the password is not in the invite and you had to kind of dig into the links in the thing to the notes to then find the password. So I wonder if there isn't a bit of friction there as well. That's, that's not hoping. Maybe, maybe we need to do a little bit of an outreach and just tidy everything up so it's easy for people to find us and join the meeting. I also don't know who exactly has us in their calendar. I had to work quite hard to get Amy to add, add it to my calendar wasn't even there for some time. Yeah. So yeah, it sounds like, yeah, something we can do more on next year to try to get more people. Right. So, yeah, that's great. Quinton, maybe we can actually have a meeting or something and kind of brainstorm on, you know, offline. Yeah, thanks. Good. That makes sense. Yeah. Cool. Okay. Now I, I'm going to get started. That was good. Yeah, sure. Good morning, everyone. Today I'm going to let me do this meeting to express the open yard, which we just joined the same group of people. Join the CNCF the sandbox project. This is the Today, I'm going to briefly describe what is open yard is about why we develop for this and what is the main functionality, what problem is solved and what may be the next direction of this project to the audience. So the Okay, this is the agenda of my today's talk. I'm going to first describe the background of the program a little bit because I guess many people already know about the edge computing Kubernetes, etc.  Now I will describe the design and I talked about some use cases of the open yard in the real products, but not in many details, but just in high level. So, So, edge computing is kind of a new kind of computation paradigm compare with the cloud computing. Well, in the cloud computing everything. People put data workloads to the cloud and run a service in the cloud and gather results. But for the edge computing, it is kind of doing in opposite way in a sense that the actual computing happens in the edge side, regardless of the far edge or neo edge or just edge. There is a centralized place to collect the data and the due to orchestration. Can happens in the cloud, maybe, and that's the kind of a common way that people did all happens in the on-prem cloud in on-prem system but anyway, the idea is we run in general the workloads run in the edge and the workloads run kind of distributed algorithms. You can think about that like MapReduce, big data, AI algorithms. They take the algorithm taking the local data as an input. So then they send the results back to the center and the entire workload. Most likely we are going to be managed by the center. There are a few characteristics that are driving this model to the production and the people tends to use it because this model has a few advantages like they have low latency in terms of the response time of handling data because the network transformation delay is kind of reduced. They have lower bandwidth requirement in the public networks because many data analysis and the computation happens in the edge side. There are some kind of autonomy requirements in the sense that even if the cloud edge network connection is down, the application still can run in that provider service, which is pretty important in some like content library use cases. And the last one, last but not least, they have better security and privacy model because many data, some sensitive data does not have to be sent to the cloud, which can be a concern for many people. Going beyond that, there is a kind of new model is called cloud edge computing. Basically, this kind of cloud platform that unites the cloud edge nodes and IoT devices. So compare with edge computing. This is a direction of view from the providers perspective. Basically, there is a cloud which manages which run the centralized control plane. In the edge side, they have compute nodes that are closer to the device and data. And there is device layer which each points to all the remote devices that people can connect to and points to the remote environments. Those devices typically are the data generator and which provides the data and by all the applications running the edge. This is a kind of pretty interesting architecture or framework in terms of the edge computing nowadays. Briefly talk about the Kubernetes. It is the content or translation platform. The nice thing about Kubernetes is it has a nice abstraction of infrastructure layer with well-defined APIs. They can provide a unified user experience regardless of which environment they use, even in the private cloud or public cloud. This is a very powerful point of the Kubernetes. And after a few years of the world, I think Kubernetes has a pretty strong ecosystem. It has a lot of controllers, plugins, solutions to resolve all kinds of new cases applications. And I think one of the most important benefit of the Kubernetes is it is very highly extensible. The use of CRD makes the integration or the broader use of CRD make the people, make the ecosystem is very easy to be integrated in the other system or provide or extend its ability to create a business logic. So that's my reason, that's the reason why people start to all kinds of solutions based on Kubernetes to resolve all including the edge computing program. I think Kubernetes itself is kind of fits on the edge computing model because it is still a layered design. It has centralized control plane and the nodes and they are kind of layered design and it is a distributed system. So all the design like in them are using the kind of has to consider the case that it is running a distributed system, the reliability, they need to resolve all the kind of reliability issues. Entire the controller logic, the reconsider logic can tolerate in a transient failure because it has a retry logic and all the least watch mechanism which is used in most controllers and many plugins are designed to handle failures. And especially in edge face, the failure scenario, we need to handle more to the scenario or more problems in terms of the reliability, availability issues because there is an obvious, you know, differences compared with cloud computing is that the environment in the edges, the networking to the cloud to edge networking is not very reliable. So if you look at Kubernetes layer, so it kind of fits the edge computing layer and the nodes, the only differences, the nodes can be now presented or managed in the edge side instead of the cloud side. And the application running in the edge nodes can still, you know, manage and manipulate the devices and spread everywhere. So, yeah. So that's a reason we think, you know, Kubernetes naturally can fit the edge architecture, but for from where a high level. But indeed, we will have have some challenges if you really want to use community to in edge edge use cases. Now I'm going to describe some of the challenges that we have been found, we have been found and and some some on some of the points that we are going to address in the project. So, okay. Here are a few challenges in terms of the how to leverage how to use Kubernetes to manage it as you edge application. The first one is unreliable network. And there, there, it is kind of common in the edge, in the case that the cloudy edge networking is not very reliable. And in some, sometimes this network problem is not hardware problem sometimes can be a, you know, I don't mean, I don't mean straighter the decision because there are there are use cases that people kind of local I mean just trying to avoid, you know, public cloud networking and they just can cut off the network kind of activities for what a reason like to save the bill save the cost. So, so in a word that it is kind of, you should expect that sometimes the, the, the cloud and edge nodes, there was no connection. And sometimes this is not just a transgender part, it is not a transient problem it can takes for quite a long time. There was no cloud and edge node connection. And this is a problematic for the Kubernetes architecture because the node that the COVID running in a node is not a, it is a stateless but it has to relies on talk to the API server to get all objects status once it restarts, then we have a problem that if the node and the API server is not connected and then the node is the restart. All the previous running part cannot be recreated by the KubeLit because KubeLit just cannot simply get a states of the parts and all the get a spec of the parts. So that's one problem. And another thing is in the cloud side, we only have problem, we also has problem if the cloud and node there was no network connection because API server relies on the KubeLit to send the hobbits to indicate the health of the node. And there was no controller in the Kubernetes. If it doesn't receive, if API server doesn't receive the hobbits for sometimes like say a minute, now the node controller will think the node is offline and from apps perspective, node controller will start to indicate parts. This is another problem that people in the cloud side, we will find the part is getting deleted if there is no cloud and edge networking. The problem is kind of kind of a unique in the edge side. It is that the network connection may be okay, there is network connection but maybe it is one directional, unidirectional network basically it is okay. As that technique to allow the edge node to access the public cloud API server, but the reverse direction is not allowed because for all kinds of reasons because the edge node may stays in the internet. Then the problem is that if the cloud side cannot access node, some well known or some people, a lot of people relies on the KubeLit API is to retrieve log and use ESAC to do the debugging. This kind of functionality is broken if there is no network connection from the cloud to the edge. So that's another problem that we are going to face in the edge scenario. The third one is there is a need for pool well application management or what I mean pool here is you can think of it is like a region because it is kind of common that in edge use cases there are a bunch of nodes that are spread across different regions. The region can be a factory, it can be IDC, some independent IDC so the environment would be much more complicated compared to the centralized cloud provider cases. In those cases, if the application runs in different let's say regions, they may have different network setup, different network configuration and it would be nice and it is kind of required, we can have the ability to do the intra region management such that if the applications try to avoid running applications in same application replicas spread to different regions. And if there are there are services and they want to talk to each other and they should try to avoid making a cross region networks. So this is another kind of requirements. So in OpenYard we are trying to address these three problems maybe but there are also indeed there are also other problems which are currently not handled by OpenYard but it points to our future work. The obvious problem is the resource requirement. I think this was a big problem in a few years ago because I'm guessing you guys are pretty familiar with Kube edge and I think one of the main advantage of Kube edge is you can try to resolve the resource requirement problem. Because I think in a few years ago the edge note that running the entire software stack for the Kubernetes has limited resource in terms of the CPU and memory. But indeed the Kubernetes node components such as KubeLid, KubeProxy, even the CI consume not a huge amount of resource but it's kind of non-initiable kind of amount of resource to run those node components which can be a problem to run Kubernetes in edge. But in a yard we are not going to handle this problem at this moment. In the next couple of slides you will see in OpenYard we are trying to leverage all existing Kubernetes components. So we kind of have to realize on the Kubernetes community to do the cost reduction or all these node components. And the last one is the device management. So at this moment I don't think that we have a kind of, you know, especially in a Kubernetes side for the device management and there is no kind of standard model and abstraction. People used to just create their own CRDs to describe our device like KubeHDRs. This part is kind of pretty open area. OpenYard didn't handle it because we don't have a support in the node side to support the various IoT protocols like MQTT protocol. We don't do that. But it is indeed one of our future direction to support that. But we probably will do some other ways is that instead of create everything from scratch by our own or by the OpenYard community, maybe we can leverage some existing framework or infrastructure or system that open source the system that are primarily designed for managing IoT devices only. So we are thinking about doing that kind of integration in the future. Alright, so next I'm going to describe the height of the design of the entire OpenYard. So the basic idea is the primary design principle for the OpenYard is we are trying to extend the Kubernetes without increasing the modification to all the core components. So with this primary goal, then we can kind of achieve the second goal is that we are trying to have a solution that is fully compatible with upstream Kubernetes from an API perspective. But we are indeed trying to solve some problems like support some very typical edge characteristics like autonomy, cloud edge communication problem and some poor web management and want to support the heterogeneous computer in the edge side. And we want our solution to be, you know, Kubernetes native in a sense that we are trying to resolve everything by implementing the add-ons, plugins, and we will quite the entire OpenYard we are going to be keep up with the upstream release. So, so once the upstream, you know, release a new version, we will release a follow up release. Well, we see a couple of weeks that's that's our plan. Hopefully, and we have, we're trying to achieve the 100% API compatibility in the sense that everything, if you have a operator application, whatever YAML that works in the, you know, cloud based in a cluster, you should work in a YAML cluster without much, I think without any modification from the users perspective. That's our goal. All right. So, these three, these figures that kind of brief described the high level, the OpenYard architecture. So it has two parts. So it has cloud side components. It has edge side components. Edge side components are the other components running in the node. Cloud side controllers is kind of pretty typical. It is just a bunch of Kubernetes controllers, CRDs, and we have a tunnel, we have a tunnel server running in the cloud side. So that is pretty much the cloud, a bunch of controllers and add-ons. And then in the edge side, there are about, there are some components, which the most important one is the Yard Hub. So it's kind of, it is a proxy to proxy the traffic flow from the node side to the, to the, to the, to the, from the edge side to the API server. But the reverse direction is handled by a kind of tunnel service, which we call a tunnel. If you look at this figure, we have a tunnel server and a tunnel agent. So this tunnel system was, was invented to handle the traffic flow from the cloud side to the edge side. All the existing Kubernetes components like, you know, kubelet, kubelet proxy or flan or other existing add-ons, there was no change required on their side. The only change that they probably need to do is they need to point to the Yard Hub when it's kind of startup parameters instead of points to the API server directly. But that is all the configuration problems. Not exactly. There was no cold chain required. And we, can I, can I interrupt you just for one second? I have a question. Unfortunately, I have to drop off the call shortly to go to another meeting. Thank you for a, first of all, great presentation. This looks like a really interesting project. I couldn't help but notice that there's a lot of similarities with kube edge, of course. And I was just wondering, I understand, you know, the Huawei started the kube edge project and you guys compete almost directly with Huawei in many spaces. Other than that kind of concern, are there any reasons why you decided to build a separate system from kube edge rather than become a contributor to kube edge? Does this solve some problems that kube edge does not plan to solve or are there any technical reasons? Okay. I can answer that question. So for kube edge, I don't know if you guys are familiar with it. The biggest problem that I see is it changed the core kube it. So it kind of, they want to resolve the resource requirement problem that problem a few years ago. So their decision is to completely rewrite kube edge, get rid of a lot of things. And even they change the basic communication model between, that usually in the kube edges, like the least words, they use the WebSocket based communication channel. They create their own WebSocket channel to communicate it between the ad side and cloud side. Now the problem of changing kube edge is API compatibility. So that's a problem that we face. And some of our customer was asking they are hesitant of using the kube edge because they worry about API compatibility. And they get rid of it because they read a kube edge. Many kind of Kubernetes APIs, they cannot support it. So that may be okay a few years ago, but nowadays they have their own problems because of the API compatibility problems. They are trying to rewrite their, you know, node side components like their own, their own hub, kind of edge hub, they create an edge hub to bring back some of many of the kubelit functionality back on it. So that's, you know, you will see the problem there. So overall, I think the biggest difference is from high level is I believe they are going to have their own community because there are a lot of solutions tied on their current architecture and the way they make the things work there. It is okay because there are a lot of contributors there, there are a lot of users there, but they probably have their own community, but in our side, we are trying to leverage the Kubernetes community. So that's the reason we build this system. So if you look at it all the way that readers, the API compatibility is always our primary concern. So we are trying to make sure once the system is built. So Intel the applications that running the Kubernetes community can be running the system. So that's, that's a pretty much our goal. And as you can see, so because the kubi idea has been that way it is difficult to make them to convert to a plugin based solution. So, so that's the reason we are trying to think about how can we solve the problem without, you know, changing the core components. Okay, thank you. That answers my question very well. Thank you very much. Okay. I have a follow up question on that. So the, what are some of the implications of, like, not modifying the kubelet code or, or the changes that a kubi edge is doing for this project right so like, does that mean like performance wise, you might have some penalty or Okay, there's a few things I can make a curve. So because, first in the kubi edge I have to admit that it is much more complicated that our system because it provides more functionality they provide kind of the edge device management, which we didn't touch at this moment can simplify the problem. So there could be edge if you look at the entire, you know, architect there, I would say there were one third of the components are trying to handle the device. So the performance wise I don't think it is not in the data planes or the control plane kind of thing. So the performance is not that critical from my perspective. So, if you look at the way that we do, it's kind of the thing. Yeah, there's some performance loss because you are doing the proxy. There are some kind of performance loss but as I said is is control plan is you probably have some a little bit delay on, on, on get the logs of the part, maybe not not not noticeable at all. That is the thing that they can think of. Other than that I don't see, I don't see there is a performance issue there. The pre, the resource consumption that indeed can be a problem because kubi edge they are, they claim they are binary they put everything in a binary and the binary is kind of 50, and thousands of micabytes. But, but in my perspective, as long as you use Docker, the memory will be brought so it is Docker is not controlled by you. So, yeah, well, yeah, but completely. So our solutions may consume more resource on the edge node, that is for sure. But one trend that we will find out when we talk to a customer. Yes, the resource was a limitation a few years ago, as I said, but nowadays typically in the edge side, they are, they kind of have a moderate, you know, powerful machine to run this kind of components is kind of normal. It's not so the resources not very hard constraint for our primary use cases. Got it. Okay. Thanks. Sorry, this is Diana have a follow up question to this whole thing just curious that when you're comparing a kubi edge to open your is one of them designed more for being disconnected from the network for longer periods of time, or is it is that similar between the two. I think for that, in that aspect, they are similar because I will talk about the NASA couple slides but in general we are going to both, both will catch the cloud side states in the local. So, which means in both systems, if you have you don't have the cloud edge communication, the edge side is still can be wrong autonomously basically, once the asset restarts they can recover the pause that was running. And then like what how long can you be I was involved in something like this recently were an edge, but there was a problem with the edge systems that were had very poor internet connection. And I was just wondering how long are these use cases wanting that disconnected state to go on, like is is a day reasonable, or is that not reasonable. The day I think it's okay but as I said, sometimes the network connection problem is not part of a problem is intentional. We see some cases some companies, you know, network administrators just cut off the line because they said I don't want any public cloud. I only allows public connection connection by me, I only allowed a few minutes, once I needed other, otherwise I just caught up kind of the line. So, the whole problem is I think the system will work the whole problem is the longer, you know that the network discussion worse, you know, the state mismatch will happens more. Okay. Yeah, because, because the edge side it just cannot responsive cloud side you can start, you can create a lot of pause in the cloud, but none of them are going to be wrong, because there is no community connected. Okay, yeah, the network seems to be like a bigger problem than the resource, like you said a lot of these edge devices have incredible resources now. More than what we would normally have in a server in a data center, I'm finding. So, I think you're I agree with you on that. But the connectivity still seems to be a problem for people. Yeah. So, so, so in the IoT they have a few models, which I didn't cover in these slides. And there's one model is direct connect IoT device directly to the cloud, which is not a model that we are seeing because we are we are we are more like you know edge implication model like there is kind of little bit powerful machines running in the cloud side. And the IoT device just connect to that machine. So, so that's the reason we don't have to worry about a problem with you install everything in the edge device directly then then we have a problem in terms of the resource consumption. Okay, thank you. Yeah, what, what is the, sorry, what is the resource usage footprint on the notice we are talking the resource usage. Um, I think, I think, um, well, I, I don't have a direct management but I will say some range about like one or two core and the two gig memory this is my estimation. And I believe if you really want really want to run something really reasonable workload. So you've already had one part. Maybe I don't think there's a reasonable workload hundreds of parts kind of thing. Then then that memory that that resource should be required. I mentioned that the docker is a container runtime. Is it the like 100% of the container runtime or do people use like container D or cryo. It depends. But it depends how many customers customization they want to do if they want to just install the coordinates default. Not as good as the job docker but we are handling a few many cases that are still there. Thank you. Okay, so yeah, one more question here and so maybe you'll go over on some of the other slides but some of these edge devices also. And because of what Diane mentioned about network connectivity, some of these devices need to store a lot of data. Sometimes it's like video right so or like lots of information. So do you also have a way to connect to some storage device. So so I need to clarify that we are not saving the data for the application. We are only catch the data for the management system like API servers. So we are only in cash to manage it object manager data so in the local local storage that won't require many storage for sure. So, so I guess the story just would depend on what workloads are and what whether they want to use some physical or volume configure with Kubernetes, right. Again, so we are not going to catch in the workload data. We are catching the metadata. Because we don't really need to make sure if the cloud and the outside network is done, the Kubernetes component can work. We cannot guarantee that the edge applications still work. So edge application has to design a way that if they have their own handle of network offline to a centralized place. But in general, they are distributed algorithm, they won't distribute algorithm, they can talk to your neighbor, not to the centralized cloud. They can run that. No, that's the nature. Got it. Yeah. Okay. Thanks. Okay.  This figure looks a little bit complicated, but in general, I try to go through it. So, the goal of we have an ad hub is we're trying to achieve a goal, which is the application of availability is still preserved when the cloud edge networking is off. So particularly what we were trying to resolve that if the net, if the current edge network is off, and the node is restarted, the cool it still can figure out what are the pause that I need to start. So, so the idea is we are we have a hard kind of proxy all the traffics from the corporate from them. And this node components to the API server. So the idea is, it will check if the network is online or not offline, if it's online, it will send a request directly to the API server. Once the request is really satisfied, we will save the results update the results to a cash manager basically, if you have a good networking, the hub what hub is keep doing is keep updating the the API servers, the objects status by monitoring the attribute request response to the local cash. And if, if the hub detect that the last connection to the API server, it will, you know, kind of serve the STP request from the cobalt or not components, by looking at the local proxy, and get a result directly from the cash. So we can think about more, more, more intuitive way is that if there is a least part API request, if the connection is good, the least request that we're sent to the API server. And the hub will, we'll get the response from the API server get all the list before it sends back to the corporate that is saved all the least objects into the local cash, and keep updating that every time there is new list request. So next time if the network is done, if the company to send the list request again, it will just check the local storage and give the all the parts that they have stopped back, and from the list request results back to the corporate. So this is how it does. So basically, the idea is we will catch the cloud manager locally through the yard hub into the local disk. So currently, there is a slight difference here so we use a kind of simplified mechanism that we don't use a database here we still use the kind of just text the local fire just plain plain fire to save the objects in a local disk we don't use a database here. There are a few reasons for this is the simplicity for sure. Secondly, is that the data the amount of data for the metadata is not a big is not a big number because think about how many parts are going to run in the nose. Maybe just metadata for hundreds of nodes, and maximally, so less than one mic kind of storage is kind of enough to save rose data. Indeed, but but again, there are loose some functionality in terms of the benefits of other benefits of the database, like a reliability kind of thing. But yeah that's that's what we choose for now. We just save as a file in the local disk for all the object that we catch in the car in the car side. I need to have some other problem because we recreate a pause requiring to recover the IP and Mac stuff. We do see some requirements say that oh, once you if you recreate a pause please keep the same IP and Mac for whatever reasons. But we were trying to achieve that but that requires kind of supports to the senior plugins to really really support that. But our all kind of young hub and kind of we, we have some solutions to work with their, their CI plugin to make sure they can, they can keep the IP and Mac once the party is recreated. So this is pretty much the high level view about the how young hub handle the, you know, the node autonomy problem, basically rise on cash and that you approximate to handle.  It is just keep off there just get everything from the local cash and that local cash you never get a refreshed. So that's that's kind of passive passive mode we solve problem. All right, so the next part is the tunnel part so we are trying to resolve the problem that like makes the goal of this. This tunnel is trying to make sure the API serving the cloud can access the cool it and calling the logo or the API in the edge. There are a lot of, you know, tunneling solutions existing but many of them follow the same pattern. It is that in general it is the remote agent side of your creator, you know, the long TCP connection with the server. And they use this tunnel, then this workplace tunnel and every request come through that tunnel to bypass all the you know firewall sitting between the agent and the server. So, instead of, you know, doing our own tunnel server implementation. We designed to leverage the Kubernetes API server network proxy, which is, I think from the version 1.18, they start to support this. The API called the incorrect ingress selector, which means by sending that all the you know, network of traffic's going outside of the API server can be redirect to the API server proxy which which is in short is AMP. We leverage the AMP implementation to do the to implement the tunneling. But there are a few things because the AMP requires our GRPC protocol. So, in any API server, I think after 1.18, the API server can send the request through the GRPC. But before that, there's you just send the planned HTTP request to support the older versions so we in we kind of implement, we call the interceptor so you can see it just like a very simple translator kind of thing. It just just encapsulates all the HTTP request to becomes a GRPC request. That's all about it. And the AMP server and AMP agent, they are pretty much at the upstream components. But we do have some additions and changes on that in the sense that they want to. In the upstream AMP server, they were they were choose a random AMP agent to build that they were they were established to turn tunnel between the multiple AMP agent to one AMP server. The AMP server will randomly pick one agent to do the network transformation. But in our side, we have to do a very explicit the routing, because if they want to access the node ace, they have to go through the traffic has to go through to the node ace API AMP agent. So, so, so in our project, we kind of adding the routing policy in AMP, and to make sure that the and they will find the right connections to connect to to get the to communicate to with the cupid running the edge node from the cloud side. And, and we are trying to upstreaming part of the solution in the AMP community as well because this is kind of not the requirement by our own. It but also because it is also because by other, you know, users you say, it'd be nice to add a more specific specific or particular routing policy in the AMP server. The question is the interceptor is required to handle the old API versions right so when it's that because some people, you know, have to have to keep different versions of Kubernetes or yes. Yes, because because the ingress selector feature is only supported after 118. So, but in many of our many of customers are running system in lower version is like 116. So, or you know, so in that case, the API send request coming out of the API server is HTTP request. So, the AMP server require the input to be the jrp jrpc format so we just use the interceptor, you can see treated as another proxy just do a protocol conversion from HTTP to jrpc and that's it. There was no no. Got it. Got it. Okay, so. Yeah. Okay, the next one is the pool of management. So the goal is we're trying to have a modeling for pool of nodes on and we can do a pool based the deployment application management. So this, this part is pretty much leverage the existing way of the communities, extending committees by using the CRDs. So in general, so we introduce a node for CRD to manage to manage a pool of nodes, and we introduce a new workload called the United Department to management of workloads across different pools. So, so which means, if people define say okay we have a pool A and a pool B, and we register the pool B in the United Department customer resource. This controller will generate, we'll create and manage to when it is departments, one respect to the place knows and one just respect to the one respect to the previous notes. And you can specify the different replica replica numbers in plan and pool B and that you can upgrade them in the United way or using different ways is up to the customers. So, and and we, and we also leverage Kubernetes topology of our service to bond the East West traffic so in the past to the service model in the committees. There is no topology basically, if you have a service class class IP types of service this you know, this service routing rules will be updated in the IP table of all nodes. There's no notion of the topology. So, I think in Kubernetes one after 118 there's a new feature called topology rest service. So, it is kind of fits a line with our current our requirements very well. In a sense that now they can choose to just update the IP table of the parts of notes, or exactly in our case is a pool of notes. Then, then, even if the, if the service ending points trying to talk each other, they are born, they are bonded to the same kind of pool of notes, which is very, very good feature and to feed our use cases. And this is also the use case will be people having different pools and different locations right. So, you probably can have two factories, they're not very mobile, but they belong to the same company. So, you can say, you can think about that way. Got it. So, next I bring up some use cases. I won't give some exactly the examples of the use cases but pretty much currently on the open yard is used you can think about, you can think it as a edge pass call. So it becomes a foundation to support quite a few other past platforms that build on top of the resources that in the edge side. For example, we have a use case that supports the IOT pass, which is IOT pass is a device is a passing major IOT device very specifically, then there are these IOT pass itself has quite a few some components that some needs to be distributed to the edge side, some needs to be distributed in the cloud side. So, we run everything. So, in that program, all the development model is converted to container and using Kubernetes and using the kubi yard system to manage all the edge side node. And use the kubi yard system to manage using open yard to manage the components that belong to the pass that need to run in the remote side. The same thing happens in the CDN, a content library delivery. Also, there are quite a few services that need to run in the remote side. And the last one is we also have a use case that connect to our IOT pass platform. Well, a lot of algorithms for AI applications that need to run in the remote side. So, those tools or applications are encapsulating to the Kubernetes workload and are deployed in the edge nodes. So, so from high level view is like an open yard is kind of serve as an edge pass core to serve other edge platform. This is the primary use case. This is the typical use cases for open yard for now. All right, the last I will briefly talk about this entire community. So, open yard is kind of a new project so it only have a age of about six months. It's kind of it has a small community at this moment. We are still trying to use a kind of normal or standard way of the driving the project of going. We will have a quarterly based release and we set up a kind of roughly six month roadmap. Currently, we will have a bi-weekly meeting nowadays. In this meeting, roughly we have about 20 attendees at this moment. And thanks for the CNCF because once it accepts to the after donate open yard to CNCF, we got more chance to collaborate with other companies. We have a kind of interaction with Intel, VML, and an environmental group. We are trying to, they're also very interesting this project and we are trying to align our interests together and they're trying to contribute to the project as well. Yeah, that's all for today. So, yeah. Thanks for letting me present it and I'm happy to answer questions. Thank you. Thank you for presenting. Very good presentation. So, one more question, one more question about the adoption. So, are there any, is there anybody using the project already? I mean, you mentioned like people using it for or the use cases for AI and CDN. So, any of these people who are contributing using it or other people that are not necessarily contributing. Yeah. So, a few things. So, basically we have internally in Alibaba cloud, there is a cloud product which is entirely built based on the open source version of open yard. They are pretty much the same. So, and all the customers of that product, you can say that they are directly using the open yard at this moment. So, which is the philosophy that we have, we're trying to make sure everything is consistent so then we can apply the same quality to the project. So, make sure this project is kind of production ready at that stage. And is there anything that the community is doing to get more adoption or like reaching out to some places who are having these challenges? Sure. Sure. So, that's the reason we are saying that if you look at the collaborator. So, it's kind of nature. So, Intel VMware, they are looking, they're coming to us to say they have similar use cases either in their production line or in their, so pretty much in their production line. So, all the Intel and VMware have their own, you know, solutions to handle the edge computing. It's not new problem. It's a long standing problem. And they build their own solutions already. But the problem is they cannot, they cannot find the good collaboration with the Kubernetes community, because their solution are pretty much standalone and they are not built for Kubernetes for sure. Now, they are trying to find the, you know, the collaboration to, to integrate with their solution with the solution in the Kubernetes. That's why they, they reach out the open yard. The primary reason they choose open yard or not choosing the Kube edge or only they have tried is because of the compatibility. They like our design of not breaking the API compatibility. So this, I would say this is the biggest difference. And that's why they're trying to approach us. Got it. Okay. Yeah. Well, thank you for presenting. Looking forward to, to the project growing and getting more adoption. It's already in the CNCF. So, I think, I think, yeah, we probably will leverage you the power of CNCF.  And we are trying to, yeah, so the, the, the, the, some of the problem is that if you look at our meeting is kind of Asian Pacific time, you know, friendly. So now it is not a very, because nowadays most of the customer, even for this collaborator that they're coming from China side, but I do, I leave my, you know, connection information if you need. So we have a slack channel so people may just, if they couldn't attend a meeting, they can connect me and I can point you all the meeting records or ask me the question directly. Yeah, sounds good. Yeah. Yeah. You can send me, I'm on Slack on a CNCF Slack so you can send me that information and I can post it on the meeting notes here so basically do it more. Yeah. You tell some people how to contact you and. Yeah, yeah, just the slack is the only has its own selection or so people, if you they just visit the GitHub, they can get it so. Yeah, but you do have your own slack. I mean, but yeah. You do or you don't. I have, but yeah, but I would say the same thing. So if you send the message in the Slack channel, I'm going to see it. Okay. All right. Thank you. Happy holidays and yeah. Okay. That's all for today. Bye bye.


Each year the Interior Department's Office of Surface Mining selects outstanding projects and presents National Abandoned Mine Land Reclamation Awards. This work eliminates health and safety hazards from mines abandoned before 1977. This year there are three regional, one national, and one People's Choice Award. 1952 to 1973, the Island Creek Coal Company deposited more than 7 million tons of refuse from their preparation facility into a hollow known as Spewing Camp Branch. The refuse pile was almost a half mile long, a thousand feet across, and up to 165 feet deep. The site was abandoned in 1981 and there were overwhelming erosion problems. There was frequent downstream flooding and streams were polluted with acid mine drainage. Reclamation began in October 2002. Cover material from adjacent areas and two nearby projects was spread to a depth of two feet. Benches were cut into the fill at 30-foot vertical intervals and side drains were constructed. After almost two years and $3.5 million, the aesthetic flight and safety hazards have been eliminated. The Sugar Ridge Fish and Wildlife Area includes over 8,000 acres of mostly reclaimed surface mine land. Reclamation involved consolidating and burying the coal refuse. The drainage was redirected through constructed channels and pit bottoms were covered. Passive treatment and wildlife wetlands were built and all disturbed areas were revegetated. An abandoned mine land area has been restored, the land is productive, the water quality improved, and a useful public area has been created. This Colorado project was done in cooperation with Mesa State College. It provided educational outreach and reclamation design and implementation and was accomplished for a substantially reduced cost. Five students completed a real-world project from site inventory through final closure of the abandoned mine openings. Four hazardous uranium mine openings were sealed, three of them with bat gates while maintaining the historical character of the sites. Not only have dangerous mine openings been closed, but five college students are now experienced with real-world abandoned mine land reclamation. Congratulations to everyone involved with these award-winning projects. These contractors, engineers, reclamation specialists, professors, and students are setting standards of environmental excellence for the future.


I remember when Merger was getting ready to take place, I was an 11th grade student in 1968, but that's kind of the limit of my consciousness. Do you recall what the atmosphere was like, were there excitement, were there some fears of eliminating the segregated conference and being a part of the full conference and full church? Right. Well, there were a lot of angst on our side because we were already at a disadvantage, but then we saw a larger possibility of not gaining grounds as we go into a much larger system. We were enjoying our own leadership, and therefore we could expect and plan and do the normal things that we had done. In this, we were concerned about the voices at the table in making these decisions. And we also noticed that there was a small percentage of our leaders at the table. So we wondered about, what impact are we really making? Our bishops and leaders were not absorbed totally. And so we experienced a loss of leadership capacity, and that was one of the discussions that we had pre-unification, is that there will be a loss of leadership opportunities for our leaders and the groundswell of those coming behind us to have opportunities. And that has played itself out. Now we've been in merge for over 50 years, I would love to hear from you how far you think we've come as a church in terms of full inclusion or diversity, equity. I think the needle has moved a little. But I think we could do a much better job. The diversity that we seek, I'm not sure that even the church knows what its goals are. But I do think that we remain open to the principle and the teachings of inclusion.


ធំ៏ះ, ធំៈំ៑ំ  customized until vehicles ruled from the bandits were shot positions and they were fined by the discosion parents as well. ឍ៑ំក៏ះ ៈំ៏ំ៓, ឈៅំៃំំ the going of the protesters and the individuals who had the park under their posts. था मिन्या सरी के अगर तिवाख तवादाद airplane limited only, of gold estimation and fake protectionelt संचlocks how many touch क्यாद त֑ा रहा, क्या नहीं करीप षोरास गल ऌर जियों अदा ड्दाधere उúde उUnisचानールगा, वार्तात लित करायमिं मुंके चичеचा तो अब वार था,單 boss Chosh तичंगो सधी ważं走了 So Ne and Charme उ energized after isn,法,


Canada's Radarsat Constellation Mission, RCM, utilizes a hybrid compact polarimetric, HCP, architecture with circularly polarized transmission, to provide operational users with high-quality quantitative information about their applications, but image classification methodologies for linearly polarized full-polarization radars may lead to erroneous results when applied to HCP-derived data. HCP-appropriate classifications are based on the stokes vector and analysis tools appropriate for HCP's polarimetric data are introduced, showing that the resulting polarimetric portraits from Fp and HCP polarimeters are equivalent. This article was authored by R. Keith Rainey, Brian Briscoe, Mohamed Daboy, and others.