My name is Marlene McCohen, and this is Picasso, my mustache parakeet, who's usually very chill, but I'm going to show you why he's not today because I am here with Jersey, my umbrella cockatoo. Jersey say hi. And she, I know you want kisses.  It's the oddest thing. It's like she knows that the camera has just turned on. She will let me take a picture with her, but once I press record, it's like she just wants to be in my lap and not show up. It's just amazing how animals know these things. I find it so fascinating. So there might be a point in the video where Picasso decides that he has to go down and hang out with Jersey, and then I lose both birds for the video. Look at him staring at her. Usually he stares at me, but you see how he's looking down. He wants to know everything that she's doing. It's so funny. Jersey is here because we are going to tell the story of how I got Jersey. I never told you guys this before. It's kind of a cute story, so I thought you guys might enjoy hearing it. There's a lot of information about Jersey that I don't know, but I want to tell you guys what I do know. So here's Jersey's story. Jersey's story reminds me a little bit of the bachelor or the bachelorette. Let me tell you why. When I first met George, just like I did with any potential suitor, I decided that I would have to gauge how much they really liked birds. Not only that, but I wanted to see what kind of birds that they would be into because I think sometimes that tells a lot about a person. And I kind of felt that George might be into cockatoos if you knew anything about them. Now of course he was trying to befriend my birds, which was George, my African gray, and Picasso at the time. But I didn't know if he was doing that to impress me or if he really was going to have a thing for birds. And I found that to be kind of important, as you know. Look at Picasso's just sitting down here. Picasso, come up here and hang out. I know she's down here. You guys can see Jersey now, right? She just wants to cuddle. It's so funny. So one day, just like in the bachelor or bachelorette, when they have that one date where they bring the dog just to see how it goes with the dog and everything, I decided to drag George into the bird store because I know that the sound of the birds in the bird store, either he's ready for it or he's not. And you know, we have a cockatoo at home at my brother's place. So I wanted to see like how prepared he was. Well, we walk into the store and there's all these birds on stands and there's a lot of noise and there's a lot of hello and Lucy, Lucy. There's always a bird in there saying that for some reason. And there's birds going, hey, and all this loudness. And I just want to gauge if it looks like overwhelming or if it's like, wow, animals, I love animals because if it's not number two, it's not going to happen, right? So I just wanted to check it out. Well, we're going around and I'm thinking to myself, let's approach all of the small birds, you know, cockatiels and conures. Let's have a nice little introduction and see how that goes. Well, there's this bird, a cockatoo, plucked, not completely, but a little bit plucked. You could see that the tail is damaged and there's like some feathers missing. And I think to myself, wow, this is kind of a good opportunity to show George what a cockatoo feels like because he's probably never got to hold a cockatoo. And of course I want to introduce him to the behavior of a cockatoo and how loving and cuddly they are. Or I'm hoping this bird is, I don't know anything about this bird, right? So this bird is standing there and I feel a little bit sad for the bird, but the bird seems sweet. I can't tell. I don't know. I didn't even try anything yet. I'm just analyzing the bird, looking at it, trying to approach with any caution. And suddenly the bird just jumps onto George's arm and I'm like, okay, okay, calm down. This is like how you handle her. And he didn't even need me. He was like, oh, look at her. And I'm like, you could probably scratch the head. You know, just showing him how cockatoo's cuddle and how cute it is. And he's doing that. And then this is my opportunity now just to get him used to it. I say, you know, you don't choose a bird. A bird chooses you. I just wanted to see like the mentality and he's like, uh-huh, yeah. There was nothing to it and then we move on. And the bird goes back on the stand and we basically move on. Look at all the other birds. Well, then George goes around again and the bird does the same thing. Like looking like, I want to hug you. And George like melts and starts holding the bird. And I'm like, okay, this is good. Like he's a guy that likes birds. This is very, very important because you know what I would do if someone didn't like birds, bye-bye relationship. So anyway, I'm very pleased that he's cuddling with this bird. And I think to myself, hmm, he probably is a cockatoo person. You know, needs a lot of like love and constant affection. I just thought that he might be too because my dad really likes cockatoos and my brother really likes cockatoos. It's just kind of a certain personality that I can tell. So I kind of reiterated a bit and I said, look at how she loves you. She chose you. That was it. I really didn't mean anything by it. I was just trying to ingrain in his brain that this is how it works with birds. They're very friendly. I want you to know that you've never had an experience with a cockatoo one day down the road. Maybe you'll have a cockatoo. And that was it. So then I asked in the pet store about the bird. I said, hey, why is the bird missing feathers? And he told me that the bird was bought by somebody and they had the bird for, I can't remember how long, maybe it was like eight months or a year. I can't remember. And they ignored the bird. They said the bird was difficult. The bird wouldn't stop screaming. The bird was loud. The bird needed attention. The bird got possessive over the dad and the family. All these things, it really sounded like very inexperienced parrot owners. So basically the guy in the bird store was doing them a favor and let them bring the bird back to see if somebody else would buy it. So now there's this whole story to the bird. And we find out about this and I'm thinking of myself because I can't even handle this. I'm like, yeah, because the bird is a plucker. And I know that Ty was a plucker. Ty wasn't our first cockatoo as you guys know from our Duffy story. But I thought to myself, oh wow, Ty has come around. Ty was a plucker. I'd probably be a perfect person for this bird. But that's what I think every time I come in contact with any kind of bird with any kind of trouble seriously. So I wasn't thinking anything about taking the bird home. So that was it. And then George cuddled the bird a little bit more and then we left. So I continue to hang out with George. Every so often he mentions the bird.  You don't choose a bird.   And now the bird just wants somebody to love. And what if you're its only chance at love? And this had no effect on the bird, obviously. This is just me and him talking. I just kind of want to test the waters and see like how much love he has for the bird, how much desire he might have for the bird. You know, it's kind of like a two minute conversation every once in a while. And then that's it. I wasn't serious. I didn't need another bird. And he never really responded to it much. He didn't say, oh, I want to go get her or anything like that. I never heard anything out of him. So I really couldn't gauge how bad he felt. He just kind of said, no, don't say that to me. I think it was kind of a thought that this would be disturbing. So let's not talk about it. Let's move on. Well, one day I'm in my apartment. I don't remember what I was doing, just probably hanging out. And I hear my door banging insanely. Now at the time I had this insane landlord. I wouldn't describe her as insane. I would describe her more as nosy. And it just kind of irritated me. And she was right there, like the apartment next door. So if this banging is her, I'm going to just lose my mind. And if it isn't her, oh my God, you're definitely going to get her attention. And by the way, this landlord had a problem with me having birds. And she wasn't even the landlord when I moved in. She moved in two years later.  What should we do about this?  So anyway, I hear banging on the door. Like bang, bang, bang, bang, bang, bang, bang. Oh my God, what's going on? I go to the door, I open it and there's George. And he has a box and he goes, let me in, let me in. And he runs to my bedroom and he puts the box on the bed and opens it and there's Jersey. Right, Jersey? Were you in the box? Jersey's in the box. I'm like, what did you do? Suddenly the bird pops out. He's like, I couldn't stop thinking about her. The way she cuddled me and the way she just loved me. I knew I had to go get her. I'm like, wait a minute, hold on. Like one, are you insane?  I thought you were at work. What are you doing here? Two, where is this bird gonna live? Cause we don't live together. So what's going on right now? Three, oh my God, is this relationship gonna last? I hope so because who gets the bird now? This is all like what's really going through my mind.  I'm gonna give her all the love in the world. And of course she loves George. That's like her main person, right? So I asked him what happened. He said, I couldn't stop thinking about her story. So I went to the bird store and I said, is she still available? And he said, no, I sold her, but she was there. And he said, she's right here. And he said, yeah, she's here, but I sold her to a guy already she's already paid for. And George apparently looked really sad. And he said, well, why is she still here then? And the pet store owner said, because she's gonna go to a guy that wants two birds and they just want the birds to be in a cage somewhere. Apparently like he has a mansion and he wants two cockatoos in an Avery just to be there. And so since the bird store only had one, this was the bird that he got. But he had never seen the bird that he had paid for. He just basically called and ordered and said, I don't want one alone. Wait till you get the other one. And then I'll come get them. So George said, wait a minute. If he's never met the bird, can you please order him another cockatoo and maybe just call him and see if I can have this one? So the bird store owner called the guy that bought the bird and asked him, hey, I got someone here who's really in love with this bird. Do you mind if I just order you two more? And he's like, yeah, I don't care. That's fine. Heartbreaking. It means somewhere there's gonna be two other cockatoos stuck in a cage. But at the same time, this one is gonna get a new lease on life, right? That's what I think. I'm like, yay, you got the bird. I can't believe it. It's meant to be. And he's just like, yes, she loves me. And you know, he's hugging her and kissing her and we buy her all these toys. And we wanna make sure that she's completely engaged, of course. And so begins our life with Jersey.  I really thought that the way we handled things with Ty, those things would apply to Jersey. And sometimes she really did get better. And back in the day, I have pictures of her with almost all of her feathers because if you think about it, she wasn't really missing all of her feathers at that time on her chest. So it was a lot easier for things to grow in and for her to get her tail back because she was kind of missing her tail too. But a lot of times with cockatoos, they have anxieties already. And just like a human being that bites their nails or pulls out their hair or deals with a depression or anxiety, sometimes it's very hard to change these things. But I do think that even though Jersey has had some downfalls, there's lots of different things that I've been trying with her. And I know some of you have definitely seen improvements in Jersey. She improves all the time.  And it's so heartbreaking. I really am going to do a video for you guys on plucking and all the ways you can help because there's so many things I've done that I've noticed really, really do help her. And if you really watch your bird's behavior, you can discover what types of things are giving them anxiety and try to reduce all of those elements. Those things aren't possible. But that's all for another video. In the meantime, that's the story of Jersey. She was with a family before. I don't exactly know everything that happened with that family. I just know that she acquired some form of anxiety. She's a little bit smaller than all other umbrella cockatoos. A few months after we got her, we got her DNA tested and I'll never forget when the notice came in the mail because it said to Jersey. And then when George opened it and found out she was a girl, he had the cutest reaction. He was like, it's a girl, my baby. And then the way he behaved towards her just was so different.  I don't know why it was just so interesting to watch that kind of human behavior too towards an animal. And Jersey really is one of the sweetest birds you'll ever meet with the best heart, right, baby? She's such a good bird. She's so sweet. She loves to play. She loves to dance. She loves to sing. She thinks she has a good voice, but she has a terrible voice, right, Jersey? And most of all, she loves love. But the funniest part of this entire story is if you guys follow my channel and know my videos, you know that Jersey does what she did to George to every single guy that walks into this house.  I mean, how many guys do you think she flirted with in the store? I have no idea. I never found out what happened with the family that gave up the bird if they missed her or anything like that. Sometimes with those things, I'm terrified to ask because I don't want to remind the store owner anything about it. Like, oh yeah, he's trying to get them back. I'm just like, thank you, bye-bye. I'm gonna buy food for like five months so that, you know, it's out of the system and you don't see me. Remember I did the same thing with Cody. I didn't even get Cody's cage. I was just like, thank you, bye-bye. Putting this in my convertible now. Oh, you have a carry cage. All right, let's go. And now when I call them to try and find out things about Cody, surprise, surprise, they didn't give me the cage or anything. But yeah, see that's what happens. I was afraid if I waited a day, I wouldn't have been able to save Cody either. So that's the story of Jersey. I see that you guys asked me that a lot and I realized that it's a perfect time to tell you guys. The reason I didn't tell you before is because it's so hard to get her in a video and I always feel like for her own video she needs to be in it, right, baby? Look at her. Like she just instinctively knows. Like she comes down. You want to say hi? No, she doesn't. Okay, and then Picasso is going to leave too. So now you guys get to see another aspect of Picasso because all he does is wants to be with his wife. By the way, watch Picasso getting interviewed about his wife. You'll kind of like that video. Well, that is it guys. Thank you guys so much for watching The Storytime Sunday. I hope you had as good time as I enjoyed telling it. Please follow me on Instagram at Marlene McOwen. Subscribe to my channel if you haven't already. We love, love new subscribers. Check out Parrot Station on Facebook. That is my Facebook group for those of you who want to come on. Enjoy and show me your birds. Thank you guys so much for watching. Bye.


Good morning and thank you for being here. My name is Francisco Rivas. I work for a research group. We did a special academic work over the release of Debian. We have been doing that study since ham. So let's get started. The schedule is, I'm going to do an introduction, a little review of the project Debian. And especially of the release, I'm going to talk about the study. The specific goals, some issues that we had to embrace with some packages and some kind of things that got hard to study in some way. I'm going to describe the methodology, of course the results. Some conclusions are a review of the presentation and a few to work. I'm going to describe the tools and of course the section of questions. As we are a group of researchers, academic researchers, we are very interested to understand the evolution of the free-liberal open source software. We have been doing some empirical and quantitative studies over free software, specifically using data mining techniques. We are involving some projects to study a larger scale of software. We want to understand how the communities of free software are evolving and are evolving. We think that Debian is a good reference. It's a good base to start our studies to use it as a large compilation of free software, of course. This is a study, as I said before, this is an update of a study that we have been doing since ham. We are also interested in understanding how Debian is growing and of course in its community. One important thing is to understand how the project is embracing the increase of the complexity and the large scale of software. You can find some information about the group and some other research that we have done. As a little overview of Debian supports several architectures, this number is under discussion. Some people said some of them are architectures, some others not, so it's a reference number. Debian is independent of any company, about one and five hundred dedicated and very good developers and maintainers. That number is an approximation because depending on the study, the attributes of each developer that you get from the database of Debian, that number can increase or decrease if you take into account the account of the developer is active or disabled, for example. We think Debian is the only project that has a commitment, a real commitment, using the Debian social contract and the Debian free software guidelines to develop. It's a kind of commitment with its users. Debian policy of course, especially interest to including major applications, that's one of the reasons that Debian is late to release some of its software. It uses a Linux kernel and supports other ones. It's important that BSD kernel because later we are going to see how the community is working hardly in the key free BSD kernel. Of course, the target of Debian is to build, to construct a complete release of free software according to the Debian free software guidelines. Those are the releases that we have been studying. About Lenny, it was released on February, has two thousand, twelve thousand thousand of source packages and 23,000 binary packages. It was released after 22 months of hard work and development and improvement. Includes OpenGDK 6 has several images, one of them is the Blu-ray image. Include most of the software, most of the stable and major software available. It's HSS 2.3 compliant and support LSB software. The specific goals of our study is to estimate the size of Debian speaking about, from the point of view of source lines of code. It's a good measure to understand how Debian is growing since the first releases. As I said, we measure the size of the distribution starting from the point of view of physical source lines of code. For us, physical lines of code is a single line, no matter if it's several separate for commas or something like that. We identify the largest packages of the distribution. We identify the most used languages used in those packages. We measure the modification to the upstream packages. Actually, we measure the size of the source code, the size of the package with a patch, with a developer patch. We measure the size without that directory. We are going to see that later. We do a comparison with previous releases with another studies. Finally, we do a cost effort estimation, applying a classical model called Kokomo. I'm going to explain that later. Some issues that we had to embrace to do the study, because there are a lot of sources of imprecisions and mistakes, is the duplicated code across the packages, different releases of the same packages, forked versions as GCC, for example. Patchwork, we took in account the fact that, for example, GINAT, it's a lot of patches over GCC, but finally it's a totally different software than GCC. So we do a list with target or purged software that we cannot take in account for the study, because it duplicated code or some stuff like that. We choose the best representative software for each of those duplicated packages. About the methodology, in summary, we don't load the package in packet. We do the count. I'm going to explain later what count means, and we do the sums and get the results of the study. The results are the physical source lines of code. This is the methodology, more explained. We don't load the sources that GCC select the packages to be analyzed. That it's the list of purged packages that they're not going to be taking account for the study. For each package, we don't load it. We extract the source directory, apply its log count. I'm going to explain its log count. It's a tool to analyze the source code of a package, getting information such as what languages was used to build the package, numbers of lines of code, and the estimation of cost afford done. We apply the package, the patch after that first application of a log count to understand the influence of the developer over the source code. We apply the log count again. After that, we delete the Debian source to understand to get the measure of the final package. After that, we apply the log count. We got three measures in each step. We start the information in some temporary files. Finally, we get the results statistic and that stuff. Speaking about the results, we got the upstream packages. It's 280 million source lines of code about the Debian source packages, including the directory is the results of the applied, the patch is 323 million source lines of code. It's the real measure of the release. The Debian source packages is 300 million source lines of code. Compare it with the previous versions. We got Lenin's 12.78 times the second release. It had 25 million source lines of code. It's interesting to see how Debian has been growing through the years. The difference between Edge released two years ago and Lenin, it's near from 40 million lines of code. It's the graph that shows the most used languages in the whole release. We can see, as you say, it's still the most used language to develop the software in Debian. In the second place, we got C++ and it's still growing. In cases such as, I don't know, Evans, they change from C to C++. In the third place, we got Shell. One of the things that surprised us was the constant growing of Java. This table shows for each release of Debian, so I got the other ones. We can see how C is in single release of Debian in the first place. This number is the rank of C in each release. The amount of source lines of code and its portion respect to the whole release. As you can see, in spite of the source lines of code is increasing, its use is decreasing constantly. In potato, in woody, it's still less. In Lenin, it's increasing its lines of code, but decreasing its use because other languages are increasing. As you can see, Java starts in the fifth place and it's increasing each release. As you can see, it's the fourth place. It's interesting. And finally, with 15 million source lines of code in Lenin. Actually, one thing that surprised us was it's over Python and Per. Actually, over Lisp. If you see the previous releases of... You can see Lisp in the fourth place. It's very interesting. This is another graph that shows the increase of the use of C and the increasing of C++. Some comments about that. And C++ and Lisp uses going down. It's interesting because in spite of it's always in the first place, it's decreasing its use maybe because other languages are most used or something like that. Java, Python and Per, their use is increasing constantly. And almost six million source lines of code are right in Python and Python and Per. About the packages, we can see... This is very interesting because if you see the previous studies of the packages speaking about Edge, the OpenOffice package had more source lines of code, about four millions over the Linux kernel. But between the 2.6.80 and this version of the kernel, the kernel includes ten millions of lines of code. Now, that version of Linux kernel has 59 source lines of code. And the difference between the kernel and the OpenOffice is about three millions. As I said before, the K FreeBSD kernel is increasing in the rank. The community is working hardly in it. This graph shows in a logarithmic scale the distribution of the packages in the X axis. We ordered the packages by its size. The first one is the package with the large amount of lines of code. It's similar to the previous studies, but with less packages here. Some comments about the packages, K FreeBSD is growing up. As I said, in Edge, it was at 11 position. As you can see, it's in the 9 position. The source lines of code for packages is decreased in Lenny from Edge that had about 28,000 lines of code for package. One interesting thing is, if you see this table, most of the software in the top ten is any user software or development software. It's interesting because it's the community effort. Actually, this position of OpenGDK can explain in some way the increase of Java in the rank of the languages most used. Another very interesting thing is the top 100 packages share is low and the contribution of the top 100 packages, the contribution to the release is decreasing from 64 in Ham to 32 in Lenny. That means the community is working in other packages, not only in the same as previous releases, so the contribution is homogeneous, I guess. Speaking about the cost-effort estimations, we apply a COCOMO model. It's used in classical software engineering to estimate costs and efforts to develop private software, or proprietary software. It's hard to find a model to estimate effort and costs in free software. From this point of view, we can understand if a team or enterprise or a software factory decide to create a Linux release, Debian 5 release today, they are going to need an effort of near 84,000 persons per year, and they need nine years to develop a release from the scratch, every single package. Actually, this number is interesting because it's more or less than Debian has since the first releases, and it costs 6,000 millions of euros approximately. Comparing Debian with another operating system, we can see this release compared with the other has a large number of source lines of code, which is very interesting because the difference is 4 millions. Some conclusions, it's a review of the slides. Lenny was released on February. It has 323 million source lines of code, an estimate cost of 6,000 millions of euros, and it estimate effort to develop from the scratch of nine years and 84,000 persons per year. And she says C++, Shell, Java, and Python are the most used languages. Actually, Debian represents the largest compilation of free software until now. Speaking about the future work, we want to study in detail the evolution of the Debian project. We want to study the ownership and the licenses. It is a very interesting field. We want to study and analyze the volunteer activity to understand why the number of developers is not growing constantly or as we expect with that big community around the project. We want to study the source code management systems, the mailing lists, the back tracker systems. Actually, we have three tools for each one of them. You can find more information and detailed information of the study in that address. You can find statistics for each package and cost estimation for each package and the previous studies. Speaking about the tools that we used to do the study, we collected the data using a set of Python scripts that download the source.gz, extract it, select the packages, unpack it and apply the slow counting in each step. You can get the slow count. The copyright analysis will be done, we hope soon, with a tool that we are developing now is called Pyternity. We got tools to analyze and other reachful sources of information about the community. Actually, we have been doing some other studies in genome or KDA using those tools. This is our research group or at least part of us. That's it. Please, questions. Hi there. I think it's valuable that you're counting stuff up. For me, slow count is indicative of bloat. I was wondering, have you done stats of the Debian minimal system and see how it's grown over time? You know what I mean? One thing I participate in is another community called suckless.org. The aim of this community is to make the code better by making the lines of code less. I hope you concentrate on that sort of slot count angle that more code isn't necessarily a good thing. It's usually a bad thing, actually. Yes. It depends on the point of view. You can see more people use development software for the distribution, but one of the things that we are very interested in is understanding if that is good or is bad or is it different? I can tell you lines of code is a bad thing. More lines of code is a bad thing. So be really good if you track minimal Debian and just to see over time how things have bloated and target those sort of things to make them better by hopefully getting developers interested in cleaning up bloated software. Yes. That's one of the things that I forgot to say that are preliminary results and that is one of the reasons that we want to analyze in detail, deeply that information. Actually, one of the most important things is the source of mistakes or imprecision of errors that we have to embrace. So it's totally correct. I think it's just merely saying that bloat is bad is slightly tricky with Debian because we're adding more bits of software and you're always going to add lines of code for that. The number of lines of code in the minimal system is relevant. What I'm actually wondering might be quite interesting to know is I saw you were taking the lines of code in the package just with upstream and then with Debian and then with Debian, with Debian to remove which gives you the amount of patch, extra lines of code we're providing. What might be interesting to see is how over time that changes particularly as a ratio of the total amount of code that's in there. So obviously as we get more software we'll get more local patches but does that as a percentage of the total amount of software grow or gets more? I think that's quite interesting. Yes. We are taking that in account. I'm interested in the social background and I've done some estimation how big the community is and it would be nice to see the numbers again. How many developers? Well, let's say 1,500. How many packages? And then it's interesting to see what is the average package number a Debian developer maintains and then I looked a little bit around and I see every package is estimated a group around, not Debian developer, one Debian developer, but 10 people around working on the software and upstream and then to estimate how many people are involved in this complete process that would be nice to have new numbers. Perhaps you can estimate it from your numbers. So it's interesting to compare it with what a company has to do or to find all these testers, all these persons. This has also something to say about quality what you can deliver. Yes, that's very interesting. So, excuse me, when you say the people involved in the whole process, what process are you talking about? I would say this triangle from the complete person involved and then chopping down to packages to maintainer. So how many people are involved because this has something to do with well, I'm sociologist and I'm interested to get free software in school. This is my main purpose. During the project leading in Germany. It's important to see what political impact this means for the freedom of knowledge, freedom of access to knowledge and all this was behind sometimes not spoken open what motivates to do this job and do this work. This is interest for me for political, ideological reasons. One thing that could be said about the communities is that the licenses are not only a legal document but also a declaration of which community you are part of. You have the GPL community, the BSD community, the Perl community. Do you have any numbers on the relative importance of the different licenses in Debian? No. If they are growing or decreasing? No, precisely that is part of the future work. Actually, we are writing a tool to do that thing. To extract the license and get some statistics what kind of license is most used and that stuff. Yes, it's one of the most important things that we are doing now. Any other question? Okay, then it's time to speak again. Thank you.


Place the lanyard around your neck. Open the cover of the compass to a 20 to 40 degree angle so that you can see the face of the compass in the mirror while sighting on your target. Holding the compass in the palm of your hand or in your fingertips, raise it to eye level. Keep your elbows tucked against your side, and this will aid in steadying the compass. Turn your entire body, moving your feet, not just the compass until the desired object comes in line with the sight on the cover of the compass. Make sure to keep the compass level, both right to left and front to back. Align the sighting line etched in the mirror with the alignment points. One is usually located on the cover, just below the V sight, and the other is located near the back of the compass near the latch on the base. The etched line should appear to run through the center of the compass face. This is usually more easily done with one eye closed. Turn the bezel until the red end of the needle lies within the red etched lines on the face of the compass, and where the sides of the needle are parallel to those etched lines. Depending on the direction the needle is pointing, you may or may not be able to see both lines on either side of the needle. You may only see a line on one side. If so, be sure that line is parallel with the side of the needle. Check to make sure your compass is still level, and the deciding line on the mirror appears to run through the two reference points in the center of the compass capsule. Take the compass down and read the azimuth to the nearest degree at the arrow marked at the base near the hinge. That is your compass direction.


Thanks Neil. Good thing I wore heels, but let me just stand here for a second so you can see that there is actually someone behind this thing, not just eyes peeking. So do you know these people that when they watch, go watch a movie, they don't want to read the reviews before, they want to be surprised. They don't even want to know what the movie is or watch the trailer. So they're really into this surprise kind of thing. My father is not like that. He's the opposite. So when my father picks up a book, the first thing he does is open it on the last page. He reads, remember Hebrew is written from right to left, so this is actually the last page of the book. So he reads the last page just to find out if everyone's okay, if they stay together, if they're still alive, what was the main concept of the book. And then after he's done, he knows that he can start reading the book. So in the case that there are people here like my father who are really curious and they don't want any surprises, let me start by showing you this new Hebrew system that I wrote, that I'm going to be speaking about. This is Hebrew, Hebrew script. This is Latin, surprise, surprise. And this is the new Hebrew typography, a new Hebrew script or writing system that I'll be talking about. It's by Hugh Schoenfields from 1932. So as you can see, it's not really Latin, it's not really Hebrew, some weird mix. And when I first saw this writing system, I was horrified. But in a way, you know, when you're horrified by something but you cannot stop looking at it, you're like hypnotized by this thing. And I was looking at it over and over. And I was thinking to myself, what was the guy thinking? Did he do this for real? People really reacted to this. And then I thought, okay, let's not judge him too dramatically and remember the time that this was set in. So I want you all to remember during this presentation, the time and the period. So this is a talk by Henry, sorry, a quote by Henry Friedlander. When the reader will see the pressure bursting open doors, may he remember that in those days, all the doors were yet to be opened. And now we can after this short intro, we can really start at the beginning of the book. So the paleo Hebrew was used for Hebrew writing until the 5th century BCE. And at the time, Hebrew was beginning to be influenced by many of the languages around it, around the surrounding in the land of Israel. And the vocabulary was starting to change and grammar was starting to change as well. And to stop that and to prevent Hebrew from becoming something else, Ezra, the scribe, the Jewish leader came and he changed the paleo Hebrew for the Hebrew script to the Armaic script. And this Aramaic script is very similar to the square Hebrew that we use today. So actually the square Hebrew is derived from this Aramaic script. So things were written in the square script, but for a long time, Lord's name was still written in this paleo Hebrew. This item, in fact, is one of the items of the Dead Sea Scrolls, if you're familiar with. It was a massive collection of scrolls that were found in the Judea Desert and Comoran. And they date back to the 3rd century BCE until the 1st century BCE. Just showing some Hebrew that we can really still read today. So Hebrew as a script is not based on stone cutting or the slow calculated stroke. You can see some very amateurish stone cutting that we do have in Hebrew on the left image. And even in Mosaic inscriptions from the 6th century, you can see that they're trying to imitate a written form, a scribe form. In the 9th and 10th centuries, the Hebrew took a split, if I can say. On one hand, there was this formal Hebrew, which was considered sacred, and it was only written by a certain qualified people to do it. It was very inflexible. It didn't change for a long time. And on the other hand, there was this daily Hebrew, the cursive one. And this script was really inspired by the place and the location and the tools that the people lived in. So the styles are varying. The formal Hebrew did change a bit according to the places in the world that it was used and by the tools that were used. So there are two major hands, calligraphy hands. The first one is the Spharadic style. This was written with a ridge pen. In Spain, Portugal, North Africa, Middle East, you can see the same tool for Arabic calligraphy and its low contrast. On the other hand, there is the Ashkenazic hand. And this was written with a quill in Northern Europe, sorry, Germany, Northern France. And this took its inspiration from Latin writing. Jumping on a few centuries later, two good Hebrew printing types were designed and produced. The Lebes Hebrew in the 16th century and the Van Dijk Hebrew, which is called Amsterdam letters in the 17th century. After these typefaces, there was a very, very steady decline of the Hebrew printing types. I'm sure you can all see that this has very heavy contrast. This Hebrew, Margalit and Merubin, and it was inspired by the Diedon style, the modern styles. And because Hebrew has a reverse stress, so the horizontals are the heavier. Do you hear me? Okay, by the way. Okay. The horizontals are the heavier. The letters are really falling. They don't have a steady base to stand on. This steady decline was stopped by a Frank Rule typeface. And this was designed in Germany and it's actually the typeface that we still use in Israel for most newspapers, books, etc. So why didn't Hebrew develop like Latin? Well, the Hebrew, as I said, was considered a sacred writing used mainly for this religious use. And it was just, it had these really important rules. It had to stay the same. So one of these rules, for instance, was that each letter had to be written separately. So this actually prevented many different styles to develop, such as the cursive styles. This is from the Cairo Gnisza collection. It's in Cambridge University at the moment and you can see this piece of ephemera which was kept in a time when these sort of things weren't kept. So this is really showing the fact that Hebrew was considered a sacred thing not to be thrown. This is a Stam scribe, Sofer Stam, a person who is qualified to write Hebrew. He says a prayer before and after. He finishes to write and it has to be, it has to be examined and qualified to be sold or brought. So we don't have cursive in Hebrew. This didn't integrate into the square script. The only one that did somehow manage to is the Rashi type Rabbinic style. It was used for biblical commentaries and since the 14th century in Italy. I don't know how to read it. My mother was taught in school. Some of the letters are a bit different than the ones we use. At the end of the 19th century, the beginning of the 20th century, there was a revival of the Hebrew language as a spoken language. So until then, Hebrew was only used for biblical matters, sacred matters. And this revival is the only case in the history of the world that a language became from a dead language to a spoken language in daily life. And this revival took place in two areas in parallel at around the same time. This is what is now Israel and this revival was the revival of the spoken Hebrew. And it was driven by the ideas of Eliezer Ben Yudah, that guy, that he was the driving spirit of this. At the same time, in Europe, the Haskala movement, the Enlightenment movement, they revived the Hebrew writing as secular for secular matters and books. So you'll see this slide later on, but the Hebrew was revived, the Hebrew was a language, and there was a need for a new modern typeface or script. And as you can see on the on the top image, these are a, it's a, can you say, another word, when you draw something really extreme? Yes, we say caricatura, I'm sure you can, you can understand. So actually things weren't gradually developing, they were just being changed completely, creating a very, very weird shapes, distorted shapes, and one of them is the one we will talk about now. This is the guy, is you, Sean Field. He's a British biblical scholar, and he was a very controversial figure, sorry. He wrote, for instance, the book that's called The Passover Plot in 65.  And as we all know, this plan went unexpectedly wrong. So this, this person published in 1932, the book which is called The New Hebrew Typography, a take obviously on the German new typography. It was published in the Danish archer press in the UK. And in this book, he's explaining the problem, let's go back to this. He was discussing the current situation of Hebrew and expressing his dissatisfaction with it, and he was offering a new solution to the existing Hebrew. He begins the book with this, with this thing, it's called No Fetou Fim. It's from 1475, and to the left you can see the manuscript, and to the right it's in, or incunable, can you say that? The first printing books, and they're trying to imitate the scribe's work in that printed type. He begins in this, he's forward by saying that this urgent of finding a new Hebrew, this need is really urgent, and he's doing this for the Jewish people. I forgot to mention he was a Hebrew Christian, so he was a Jewish, a Jew person that converted to Christianity. He's saying how bad the situation is, and how important it is for him to change this. And he's talking about the fact that Hebrew didn't really stay the way it was, and everything we talked about, and how urgent it is to find a good reason for a good solution for the daily used Hebrew. He's also saying that right now in Hebrew there is no reason for in the metal type, there is no reason for it not to be to develop also hot metal, and that Hebrew has very old forms really unnecessary for the time. So he's talking about the Hebrew and what's wrong with it, so we can go over this quite quickly, and some things I agree with him. So he says that many letters seem very similar. You can see the pairs, I highlighted them, and too similar. He says that because of the stress there is no flow in the Hebrew, the Hebrew is really stuck. His idea was, and we'll get to that later, to accommodate Hebrew to the best Western's exemplars. So he's saying the Hebrew is stuck, not flowing, and it lacks emotions. So when a printer needs to find a certain type for a certain cause, he doesn't have a big variety. The only variety he has is the rabbinic style which we talked about. And in this book he becomes very emotional with few quotes that I wanted to share with you, how a book loving people like the Jews could so long endure to have the treasures of their national literature reproduced in such unlovely forms. It is difficult to imagine. Will not the eyes of a freeborn children of Eret Israel become deemed with pouring over illegible pages as any ghetto-born? Unsavory mess of ugly letters. Only people trained in suffering could allow itself the edition newspaper to be so imposed on. So I think this is actually quite lovely, but he didn't agree with me obviously. He's talking about these new ideas which we'll discuss later about writing Hebrew in Latin characters, and he's saying this is not a good idea because this is ruining all the history of the Hebrew script which is so important. See very soon what he did. So he said that the Hebrew has only one case and that's very problematic. Hebrew needs to have italic and the lower case. And I was just looking at these two examples and thinking to myself what is worse, writing Hebrew in Latin characters or creating something that doesn't look like Hebrew. I cannot read it and doesn't look like Latin either. This weird hybrid, so you can be the judge of this. So he felt that the time is right for something concrete to be attempted. What did he do in this oddly looking script? He changed the stress to begin with to the Latin stress. He decided to take the existing letters with only minor changes. Agree with me or not? I think they are not minor at all. To use these for the caps, the upper case, and he added serifs. I don't know the reason. He eliminated the final forms. We have five final letters in Hebrew, so they don't need to be used anymore. And he created a new set of lower case. Oh, and he added the centers and dissenters to make the type more harmonious. Surprisingly, when he was designing the italics, so he was designing but not drawing them. When he designed the italics, I was really surprised to see that they're leaning to the reading direction. But he says that whenever there would be a need to switch the Hebrew to be written from left to right, no problem, it can just be slanted to the other direction. And very awkwardly, we use in Hebrew the regular, the Latin punctuation, so he advised to just reverse it. And then he talks about how important it really is to change the script. He says that people would need to learn something new, but that's definitely worth it. Definitely worth the challenge, because the benefits would be so much better. So then he adapted it to several typefaces, Latin typefaces, which you can see right now. So we've got the Castland Old Face. I heard that. I don't know how to pronounce this. Kochen, or you know, and italics for that. These are the final pages of his book. Also sans serif in this new typography. So his main goal was to give the printer these rich options of styles, italic as well. And this is my favorite, the Ultra Budoni. I cannot read that at all. And he mentions that he, sorry, I'll keep this for one more second, he mentions that he was not inventing anything. He relied on historical sources, historic sources, and I know that at that time he didn't have the resources that I have. So I was doing some research, trying to find exactly where he took his inspirations from. So he's saying things very general, like rabbinic, eastern rabbinic first century. So I was doing him the courtesy and really trying to find the similar, the most similar forms. This is what I came up with. So he used the rabbinic, I grouped them up. So the rabbinic style, there is the kaf, chet, bet, and aleph. And then there is the Samech, which is a, it's this P that you see on top, and the white one is the Hebrew Samech, the square script. So I was looking at some that looked similar to what he mentioned. He took his inspiration from first century inscriptions. So there is the Vav and the Hey. I didn't see this swirl anywhere. And the Chet and the Mem also from first century inscriptions. And this is my favorite, the Reish, which is an R actually, if you can see. Do you think it's similar to the, yes, no? Do you agree with this guy? Think about it, we'll talk about it over coffee. And some of them he took from the Caps, from the uppercase. And some of them, according to him, is from the usual form.  Some of them he took from Maccabean coins, which I did not find any proof for this. And some from Old Yemenite, which again I don't think is very similar. Eastern manuscript cursives, final forms of the Hebrew he eliminated. And from pre-exiled seals and inscriptions. I still don't quite get why he used the Q for the Kuf. So he's not mentioning anywhere that he took his inspiration from Latin. This just happened to be this way. Although I found some things that look very similar. So actually this is a cut and paste of Latin. So what do I think of this as a native Hebrew speaker and reader? I think he went too far. I agree with some of his problems, with some of the problems that he mentions. But I don't think it's worth throwing a whole script away and designing a new one. And I think that this fact that he's basing his theory on these historical findings is not, it just sounds like an excuse. I think he tried to do, to come up with some Latin version, which would be easier according to him. And I think that learning this new style would be so difficult for people. Someone that thought different than me was Stanley Morrison, who heard about this idea and he thought it's an excellent idea. So he wrote the introduction for this book. And once again he writes that this is an urgent matter. This is a practical step. This is not some kind of weird experiment. He writes that these days he's really surprised that the Hebrew state for so many centuries is the same. It's very conservative and he was, he thought about this as a triumph for the conservative spirits of the people, like the Jews who are world people. And he was surprised that the certain Jewish movements of this revival of the Hebrew language didn't affect the script. He thinks that this solution is not the best one yet, but it's the least offensive one. Morrison thinks that Hebrew should be engraved, should not look like a written form. And he thinks that in the machine age, back then it was, it's really useless for the machines to follow written forms and it doesn't accommodate itself well in type. And this is an interesting correspondence I found from 31 on of Stanley Morrison with Henry Friedlander, the German Jewish type designer. So Friedlander sends Morrison his drawings for Hebrew and he didn't find anyone else who can really comment on these. And Morrison says his thoughts about Hebrew and how it should look like. And he also attaches these nice drawings of Serif Hebrew, Latin Serif Hebrew element. He thinks that Hebrew should look like type and not like a script. He thinks that it should look like it was cut by an engraver. He doesn't think it should be a German toys sans serif. And he thinks that until we make up our mind, this is a quote, until we make up our minds regarding this issue, it's better if we just use Latin letters for Hebrew. And he thinks that it's really bad that Hebrew has only one case, it should definitely have the lower case and italics with it. So Friedlander sends him his work and the first thing Morrison says is Ed Serifs. Ed Serifs similar to the Castelons Serifs in the I and the J. And this is the first thing you need to do. The second thing you need to do is find a nice cursive in Hebrew and adapt it to your typeface as the lower case. So just to end this story, this is not related to the talk but just, you know, end this nicely, they continue their correspondence while Friedlander was in the Netherlands during the war. And in 63 after Hadassah typeface, which Friedlander designed, after it was published, Friedlander sends Morrison a copy of the specimen and suddenly Morrison is much more merciful. He says that he was actually right and Hebrew should not be romanized. He still thinks there are some problems but that Friedlander did quite a good job. This time I agree with Morrison. Some of the other reactions to the new Hebrew typography book, Friedlander himself said that the conclusions were foolish, although he does understand the need for a whole big family that includes lower script, let's say, and italics. And Tobi, which did these drawings, he wrote that something like, so this person seriously suggested to do something like this, this distorted forms of Hebrew. And Schoenfeld's thing is here to the right. Some other reviews, the Sentinel from Chicago, a Jewish weekly, they wrote that they agree with all the problems about Hebrew but they think the solution is way too radical. And they thought it had some nice interesting anecdotes in it but then they found out that Schoenfeld is a Hebrew Christian so they really thought that he has no right to comment on that. Schoenfeld replied to them that it has nothing to do with this and he put his soul into the issue. On the other hand, the Palestine Post, a local newspaper from mandatory Palestine, wrote excellent reviews about this new system. They thought that the Hebrew is archaic and the letters are clumsy and this is the first practical step in the development of the new Jewish culture. They thought that the lower case is excellent. So they were really raving for a few pages about this. We're good with time so I can show you some other cases of trying to change the Hebrew script. Just a few facts. In Hebrew we have some letters that have the same sound so this is causing some challenges. So we have Bu and Vu and Ch and Tu and Ku and Si, never mind. And there are also many letters that look very much alike so it's the type designer's job to really differentiate them well. And also we don't have vowels in Hebrew so we read by understanding the context but in the 9th century there were these vowel marks added for certain purposes and they are called nikud. So if I read this I could read that in many, many, many ways. It could be sefer, separ, sofir and the meanings of these would be one of these, the meaning of these three letters. And another problem with these vowel marks, the nikud, is that it actually costs double because you need to cast a line of letters and then the line of the vowel, the vowel marks. So Hebrew is actually a language which you have to know the vocabulary in order to read without the vowel marks but how would you know the vocabulary without reading it first? So it's a challenging language to learn. So people came starting from 1898 with new reforms to fix these problems. So Josef Kaplan from Switzerland designed this script in 1914 and he did two main innovations. The first one was to add third row from the bottom to the left. These are the vowel marks. So instead of putting them below the letter he suggested to just put them right after each letter and also he did a monoliniar script. So according to him it would be more legible. He also narrowed the letters by two thirds or actually by one third to make it more economic in space and he looked at all these similar letters and changed the curve direction which you can see here. He also added this serif looking and in the left bottom example he changed the shape so the sounds of b and v could be different and people would know how to read them. Another thing he did is because the Hebrew was receiving a new word every day taken from Latin from any Latin language or others. There were many Hebrew signs, Hebrew letters that didn't have any representation. So he designed these ligatures of ch for instance and he did some other nice ligatures for mister and for number. So this was his suggestion and then he revised it and did the second draft in 32 but actually nothing really happened with this. After he did took all the trouble and did many styles with it so this one didn't work. Another idea which was very popular in the 1930s was to write Hebrew in Latin letters similar to Turkey and their main idea was that because the Hebrew derived from the Paleo-Hebrew and the Paleo-Hebrew is very similar to the Phoenician which is where the Greek derived from and which is where the Latin derived from so actually the Latin is more true Hebrew than the one we use today. Agree? So there were two very enthusiastic supporters of this suggestion, Itamar Ben-Avi and his father was the driving spirit behind the revival of the Hebrew language and Zev Jabotinsky. So they were starting to work on this together then they had some miscommunications and Itamar Ben-Avi published this newspaper. It lasted for only one year but it was written with Latin characters in Hebrew. In 1959 Dr. Michael Avino came up with this new system of using Latin letters with the addition of a few other characters that that are either vowels in Hebrew or sounds that we don't have in the regular letters and his idea was not to have the Hebrew be an easier tool for people to learn not for that purpose not for the teaching purposes but to pass on as much information as possible. So these are a few examples of his suggestion and this is a chemistry text written in his sort of Hebrew so you can see some weird character looking parts. So he approached monotype when I was doing research in Salfords I found this folder and I saw that he requested the monotype to design these few extra characters for him and he wanted them to be used with the Times New Roman series 3 to 7 if I'm not wrong and there was this back and forth discussion between them he gave them comments they gave him comments and another interesting discussion within monotype whether this thing would actually become a reality. So John Dryfus for instance thought that it would never happen other thought that maybe they should really take this suggestion seriously and produce these trials because it might really happen it didn't. At some point it was just stopped they asked Avino to give some feedback from Israeli readers and he never supplied that so it just ended. Going back a few years Gil Hebrew he was designed by Eric Gil he was in Israel in 1934 he was doing some reliefs and some stone cutting for signage in the Rockefeller Museum and he designed this this Hebrew that you can see here and after designing it he came up with a new Hebrew typeface Gil Hebrew which had a Latin serifs which probably he looked at the Hebrew entry strokes and thought of them as serifs so it was a very inscriptional typeface and the monotype did few trials for this in 1937 but it was never published with them. Few years later this is the folder of the original drawings in the archives. Few years later it was published finished and published by the Jerusalem type foundry this is this was the first and maybe only the only type foundry in Israel. It was founded by Dr. Moshe Spitzer and he thought that this Gil Hebrew is excellent it's an innovation it's young it's energetic it received mixed reviews but this is an example of a book from the 60s that was designed by Ellie Gross. She refined the lettering a bit and used that. Some of the reactions to this typeface so we said that Moshe Spitzer was in favor of it but people like Friedlander which we talked about thought that these serifs are actually preventing the flow of the reading of the Hebrew whereas in Latin they're helping read over letters. So I had to finish with some examples from our days my city Haifa and even in my neighborhood of a let's say Latinized Hebrew so this is supposed to be Aleph but it's it's an X. This is fairly new book with the Latin serifs. I love this one this is from a tiny neighborhood they had this center and it spells Deniz and they took the branding process really seriously so they designed this for any application of the name this as well. This is a typeface called English a free typeface free font and this is the image I wanted to finish with just of the reversed case of a ethnica restaurant not a very good one that took the Hebrew vowel mark for the English so you know you would know how to read the beginning of the word. So I think although this you know I don't think anyone would really do this such a thing today people are much more aware of the need for research and while doing it on latin's but it does stand out we say in Hebrew Samania Manikitsoni which means the right extreme mark to show what can be done and have people be careful not to get to this situation including myself for other scripts and that's it I'll be happy to talk over coffee if you have any questions later thank you very much


Thank you. So today, we'll be talking about a very interesting topic, trust as a service. So we are from data communications, me and Sachin. So as we were already introduced, so we are mainly working on two kinds of offering from data communication, one is the cloud Kubernetes part and then a specific version for the edge kind of deployments. So me and Sachin, we both are working on a very similar solution. And so we are presenting part of that solution that we are working. So our agenda for this presentation would be basically to just give a broad overview on how the TCL Edge Management introduction, TCL Edge Management and where trust as a service fits in and why trust as a service is very important. So when we say trust as a service, so we already have a lot of tools, deployment methods that we have upstream like keep straight our crops for installing and managing Kubernetes. But there are a lot of pitfalls with that in managing large number of clusters and managing days, day one, day two kind of operations on that. So that's where the upstream project as a API is gaining a lot of attention off rate under Kubernetes 6.2. So this is something that data communication we have leveraged. And we would like to show that in this presentation along with that would be the application manager. So how the cluster page that is available upstream is extended and it is integrated with app manager and how that could be manufactured. So to start with, so from our TCL perspective, we are managing hundreds of clusters that are spread across globe. So essentially what we envision to provide as a wide solution or a wide product is a single pane of glass where a user can come in and he can manage n number of Kubernetes clusters. And so once a user has provisioned his Kubernetes cluster from a single pane of glass, then if he wants to orchestrate containers on that clusters independent of the cloud provider, it could be that the Kubernetes is deployed on AWS or on Azure or on any of the cloud provider or it could be on a data center or it could be on a small edge box. This edge box could be a simple Linux box that is sitting on a very remote location like a steel plant or for some kind of IoT applications. So how do you manage them which is actually not orchestrated by any cloud provider? So one is on the cluster orchestration, then application orchestration across that cluster. So when you say application, it could be that container application or still a lot of applications are in the process of containerization for them. We also envision to provide a VM orchestration on top of Kubernetes which is also quite heavily used of it. And in addition to that will be a generic monitoring and the logging capabilities along with native detox integration and there's a copy integration. So the overall session will be straight into two parts. Firstly, I'll initially run through the concepts of both cluster API, how we explain the cluster API and how we have integrated with that measure. And as a second part of the presentation, session will take over on the demo part and we will create two QB discusses during this demo and we will see how it comes up and how we orchestrate the application on them. So as some of you might already be aware of cluster API which is basically a single set of APIs that has been open source from Kubernetes 6 community and it is being used to spin up a cluster on any of the cloud provider. What you see on the left hand side, the first block is the extended Kubernetes APIs which are CRDs using which from the upstream what we can do is like we can spin up QB idiom clusters onto any of the cloud provider as of today. And that has been extended now with multiple bootstrap providers. So it could be that we use the same cluster API with the extended version with the same principles we would be able to spin up a K3S cluster onto any of the cloud provider that we see on the right hand side or we would be able to spin up OpenShift clusters or OpenShift use cases or TataIKS which is Tata's version of Kubernetes service that could also be deployed which is what actually used in our wide spread deployments. And on the infrastructure part, we have validated a lot with MAS as we have our point of presence across India on multiple data centers, we have spread across like more than 28 locations which accounts up to around 150 servers to 200 servers which are managed by MAS and we are using MAS as a cloud provider to spin up a cluster on demand. So now once the Kubernetes cluster is installed that's just not the only story. That's where the story actually begins, right? So that's where the application manager comes into the picture. So now let's say now there is a specific use case for 5G. Now we wanna deploy 5G as a service. So that means that a cluster is spun up on any of the locations and immediately as soon as the cluster is up the applications are all over. That's where the integration with the application manager comes in. So from the API perspective, it is a simple API that you see. From the user perspective, it is very simple. All the automation part that is happening under the hood. What you can see here in this diagram we have cluster API that is running, the Xnet cluster API that is running in one management cluster and using that management cluster, it's a Kubernetes cluster that could be running anywhere in the cloud. And that could be acting as a single control plane for the cluster management which will be used to spin up Kubernetes clusters onto any of the cloud providers that you see on the bottom. So it could be on any cloud provider. And to achieve the same all we have done is extending the existing cluster API that you see on the right-hand side. It is a very straightforward spec that you can understand. It's a kind cluster where a user specifies what version of Kubernetes he wants to install if it is a version 1.20 or 1.21 or 1.22 and what networking driver which translates to the CNI that needs to be installed when the cluster is spun up. And the way how we install the CNI is again with the integration with the application manager. And then we specify how many number of control or how many number of control plane nodes we want, one, three or five. And similarly how many number of worker nodes we want and the operating system for that. Then under managed services we will specify what kind of application needs to be running. So as I was telling earlier, if it is a 5G edge so then all we have to do is create a template that is required for the app manager and as soon as the cluster is up as soon as the cluster of the application will also come up. In fact, the way how we are using is extensively with CDN. So as we know like in CDN networks the traffic spike can happen or quite frequently on an unnoticed scenarios. So under such situations ideally we auto scale the cluster to an available nodes. If there are no nodes available on that cluster or if there are no nodes available on the data center in case of mass then the cluster API will be integrated to an umbrella API which is managed by OSS or BSS that will trigger the cluster API to create the Kubernetes cluster on demand. So sometimes we see the traffic spike there is no resources on that data center. Now we will spin up a cluster on demand on public cloud and the CDN application comes up on demand. It's just an example of the CDN it could be any other application for that matter. And spinning a bit on the API itself what you see on the left hand side is what is available from upstream. So as we use cluster API when we create a kind cluster under the hood it creates multiple CRDs in fact in fact with the cluster API there are certain drawbacks where it's not a single API. Essentially we will have to create machine deployments machine deployment translates to the worker nodes that are created from cluster API and QVADM control plane translates to the control plane node that we have to create. So then there are others the other API is like machine templates QVADM conflict templates all this has to be linked to one another. So it's not a single API what is available from cluster API it is a set of APIs. So what we have done is like abstracted that and we have one simple API that is acting as an umbrella API on the top that takes care of all the automation what is required for the cluster API and along with that there's an integration with the application manager where as soon as the cluster comes up it will create a kind multicluster app which is an extended API again. And with the we have provided a native integration with the auto-scaler. So the auto-scaler actually this is available upstream plus auto-scaler for which cluster API acts as one of the provider like how AWS or GCP or Azure can act as a product cluster API itself can act as a cloud provider. So a cluster auto-scaler automatically kicks in when cluster API sees certain when the parts are not triggered when the resources are not available then the cluster will automatically scale the cluster. And with the integration with the OSSBS is that I mentioned earlier if there are no nodes available then it will scale across the different cloud itself. Yeah, that's on the cluster API part where we could do the cluster orchestration. So now coming to the application manager we it's again a custom API that we have extended which acts as a global control pane. So it's a kind multicluster app using which we can deploy any kind of Kubernetes resources that you see here on the right hand side it could be a kind deployment it could be a kind virtual machine it could be a kind service config map anything. So a single point of contact on the management cluster which acts as a global control pane that could go and deploy and do the lifecycle management of the application onto any number of clusters. So this might be seen a bit analogous to the Qt Fed or to the Agro CD. There are substantial differences coming to that part as well. Qt Fed for example, it only handles the CD part of it. App manager what we have is something there is both CI and CD flow where application build can happen the test can happen with the natively integrated API and along with that also the testing and then the CD part of rolling out to the clusters or comparing to the Agro CD it's again CD only. So which is gonna be the main differentiator in that perspective. A bit elaborated information on the same app manager. So as I was explaining so now it's the kind multicluster app with CRD that we have developed and with which we have a native integration to GitLab and to the Jenkins. So all we have to do is if we have to use both CI and CD part of it all we have to do is like specify the Git repo and the specific file that needs to be built and then integration with Jenkins to construct the pipelines followed by which native integration with tests like SonarQ or JUnit that we already have and that's on the CI part and on the CD so ideally we treat them as stages. So the applications that we want to deploy it can be deployed on different stages. Each stage can itself consists of multiple clusters what you see on the right hand side the stage deployment. So developers cluster could be in number of clusters where on each of these clusters the application will be deployed. Similarly on the staging there could be a number of clusters on each of the clusters it could be deployed and same applies to the production. So the integration with the cluster pay that we have done is mainly for the CD part of it. So as soon as the cluster is up we have the applications coming up. So that's where the CD comes in. And with this ideally we can offer application cluster as a service not just cluster it's gonna be the application cluster as a service and that cluster could be open shift or K3S or QBDM that we are using. Yeah, that was on the conceptual part. I would like to hand it over to my colleague Sachin. We can showcase the same thing on the demo. Yeah, thanks Vishal. Hi everyone. So let me share my screen. Let me know when my screen is visible. Yes, please go ahead Sachin. So as Vishal mentioned we'll be showcasing the demo on one on AWS and second on Mars. So we have prepared two email files for basically showing this demo. So one which will be the intro provider as AWS and the bootstrap provider as QBDM. So here we will mention what type of provider we want to use, the basic cluster specification, what type of networking driver we want to deploy after the cluster is ready. Similarly some of the control plane, how many replicas do we want, what type of operating system on control plane we want. Similarly on the worker side. For the managed application that needs to be deployed once the cluster is ready, we can specify what managed services should be deployed after the cluster is installed. Like for this particular case, we are mentioning the Prometheus and the Fluendee should be installed along with on the cluster security, we need to install OPA security once the cluster is ready. I take you to the AWS UI basically. So right now we can see there are no instances which are running similarly on VPC and Internet gateways and all. So once we start creating the cluster, all these things will be created automatically by the cluster API. So once we apply the ML, we will be able to see the status on the API side. Basically we will say it has started creating the Internet gateways already created, subnet is created. The same thing we can verify from the UI as well. So we can see for each cluster, the Internet gateway will be automatically created. Similarly on the VPC side, we can see for a particular cluster, the VPC is also created and the load balancer for the API server. So once this cluster gets created, we will see through one of the clusters already deployed. When Meshap was showing the presentation, I started the cluster creation for the mass. So basically if we see, so it was a two-mode cluster that I created. So both of those are in ready state. Same thing we can verify from the UI as well. We used the this KCD Gen A zone, which is deployed with 1.20.9 version. And if we look at the application end of piece, so we can see as the cluster came up, all the applications that we specified, the networking driver, the OPA security policies that we mentioned, the Fluendi and the Prometheus, all are in deployed status basically. So if we look at any one of the multi-cluster app, so in the detailed status, we get to know what all the resources which are deployed for a particular application. So this is for OPA security. So we can see the cluster role, road bandings. So all the resources which are required for operator and their policies, those will be created on the subsequent cluster. Same thing we can verify from the cluster as well. So we can see Prometheus is deployed along with OPA gatekeeper going back to the AWS one. So we can see six out of seven prerequisites for a cluster are already created, which includes cluster security groups, internet gateway, load balancer, any internet gateway which is required, VPCs and subnets. So now if we can see the machine have started provisioning for the control plane and seeing if we can verify it from the UI as well. The control plane machine is created.  So we will wait for the machine to come into running state. Once the machine will be running, we will be able to reach the API server. So as we can see, the first node is ready and we can verify from the machine API as well. As we can see, it has started deploying the worker node on AWS. And we can see that the machine is now ready. So we can see that it has started deploying the worker node on AWS. And the same thing we can see it from the AWS UI. So it has started creating this particular machine. So basically the main thing is from the single API, we can manage the cluster lifecycle, be it creation, be it deletion, or any upgrade. Suppose if you want to upgrade a cluster, so we just have to change the cluster version here and apply the ML again. It will automatically do in a pipeline format. It will first upgrade the control plane and then subsequently the worker node. Similarly, if we want to the worker replicas or the control plane replicas, we can just do update on one API and it will automatically trigger the required cluster APIs for scaling up or scaling down. Yeah, and just to add, even the cluster installation, it takes about three to four minutes or five minutes on AWS in fact. Compared to, for example, the other standard installation tools would have cops or ansible, which takes quite a long time. So now we can see the second worker node is also added to the cluster. Yeah, and with this, we come to the conclusion of the demo. We can take any questions if you have. Thank you so much for the valuable questions. I noticed that you already answered some couple of questions on the chat and the first question of the answer. So one thing which I'd like to clarify is when you refer to like the Tata communications, Kubernetes as a service of the country, going to act as a of approximately for platform. So when you say the multi-core platform, where are we going to monitor all the multi-core platform? Is the Tata communications providing opportunity to monitor that? Correct, that's right. Yeah, so we do have a single pane of glass, but each of these clusters can be independently monitored. The logging for the same, for each of the applications and also advanced analytics if you want to do on top of those data, there is a specific analytics framework that we have that is integrated. So it's going to be one big orchestrator under which trust as a service is one module that we present to you. So recently there are some things, similar thing which I was, I believe I was noting, something like an Anthos in a GK or Google Cloud. There is some service called Anthos in a Google Cloud, which is also doing a similar type of thing. Is it my understanding? Is it right? That's right. There is substantial synergy on that. However, there are some differentiators where in fact we can orchestrate the virtual machines on the proper Kubernetes cluster, which Google does it, Anthos does it in a bit different way. And there are more differentiators when it comes to connectivity. So we spoke only on the clusters creation, application onboarding. Now if those applications running on different cluster want to interconnect, then we do have something like a network mesh that we can establish for these applications to interconnect. So there are some differentiators there, although there is some synergy. Yes. Thank you so much for your valuable session. So I'm not seeing any more questions on that. If any other questions are there, we can post on the Slack or somewhere else. Sure. Thank you. Thanks a lot for the opportunity. Thank you.


I work in the mountain ash forests in the Victorian Central Highlands. They're some of the tallest and most carbon dense forests in the world. They are very key for Melbourne's water supply. They store vast amounts of carbon and other greenhouse gases. And they are very important for vegetation and key species like the Leadbeater's possum that is endangered. Approximately 99% of these forests have been clear-felled or burnt in recent decades. My research has found that disturbance can have long-lasting impacts on forest soils for up to eight decades post-fire and up to three decades post-cleafel logging, far longer periods than we've previously recognised. We found that clear-fell logging and fire resulted in significantly lower measures of key soil nutrients that are essential for plant growth and survival. The long-lasting impacts that we're seeing of these disturbances on soil, on plant communities, on animals means that we really need to think about how to manage these forests for the future to best preserve the functions that they have and for soils that's storing vast amounts of carbon, that's biogeochemical cycles, that's microbial communities and plant growth and survival.


How is California still in a drought? Since Christmas, California has gotten an average of 8.6 inches of rain, which is huge for a state known for being as dry as my lips during a chapstick shortage. And though it's helped to get the state out of an extreme drought, 95% of the state still remains at some level of drought. Why? Well first off, it takes years and years of dryness that leads to water shortages to cause a drought. So it makes sense that even to start to get out of this one, California would need at least a year as wet as the wettest one on record. Also because recent storms have been coming so close together, water isn't even soaking into the ground like you could, with most of it just running off. There is some good news though. Snow packs, which make up 30% of California's water supply, have reached up to 267% of their normal size, and reservoirs are about to reach their historic average levels. Buuuut, it's going to take more than a few atmospheric rivers and bomb cyclones to fix California's water problems.