When y'all getting to argument right say if it ever got too heated who getting the best dude cuz I fucks him up I'll go right up to a fight. I'm just saying but if it ever wanted who's getting the best dude I'm dark skinned, bro. Oh, okay I'm gonna get some water wipe it on every bed One of the girls can talk about the last car show coming up She's sitting now people don't really have your fight though.  No, they think lights can do so Why don't you be on so hard on lights can do cuz y'all sensitive? Oh, yo?


Background lower urinary tract symptoms, LUTs, are a common urination disorder worldwide. Previous research has focused on identifying cases that meet specific criteria, which may have neglected the genuine demands of patients and related issues. Objective This article was authored by Shan Zuen Wei, Ming Ma, Chang Jing Wu, and others.


In St. Lucia, cancer is the second leading cause of death. One in every six St. Lucia males and one in every five St. Lucia females will be diagnosed with cancer in their lifetime. Smoking, alcohol, lack of exercise, stress and poor eating habits increase the risk of cancer. Changing these is our best chance at preventing up to 50% of cancer. Sometimes, though, in spite of these efforts, cancer still happens. Knowing what to look for is our second best chance for early detection and treatment. Be informed. Let's talk. Contact us at St. Lucia Cancer Society. Telephone 452 1538.


Over the last year, I've used about every dating app out there. In this video, I want to share with you my takeaways, some cautions and an encouragement. At the end of this video, I'm going to rank the best to worst dating apps, so you'll want to stay tuned for that. This is the case for dating apps. Think about 100, maybe 200 years ago, you'd have a lady that would be part of your town or community that would have an extensive contacts list. Maybe she was part of the sewing club, the knitting club. She had everybody's tele... I don't know, what did they do 200 years ago? They didn't have a telegraph. What did they do? Did they have mail back then? They knew exactly where all the single young men and young ladies lived, so she could matchmake for you. You know, I don't think a lot of people would have problems with that. It's just getting two people together that might have some stuff in common that might have potential together. But the case for dating apps is that this is your digital matchmaker, that now instead of going to the lady that has all these contacts and is part of all these clubs that knows everybody in the town, you can go to one of the dating apps to connect you to somebody that might be your potential spouse. And on the surface, this is right, right? Like, there's tons of contacts, there's tons of people that are on these apps, so there's a possibility that you might meet somebody that you would have never met in the first place. And if you're like me having a hard time meeting somebody in person, then the option of a dating app seems like a pretty intriguing one. Now, I couldn't make a video on dating apps without highlighting the case against dating apps. I'm going to share with you one argument against dating apps that I don't think is quite valid, but then I'm going to share with you a couple more that I actually validated through what I experienced and I'll share with those, those with you as well. Whenever somebody starts talking about Christian dating, the idea of waiting will always come up. And I'm not talking about it in the context of boyfriend and girlfriend and waiting to have sex until marriage or waiting to kiss until marriage and waiting in that context. That's not what I'm talking about. I'm talking about waiting in terms of waiting for a spouse, waiting for God to put somebody in front of you that you will marry. Now, this rhetoric has persisted so much that the idea of going on a dating app is almost like spitting in the face of God that you are not waiting for the person that God wants for you. And instead, you're taking things into your own hands and going to the devil's app in order to find the spouse that God didn't want you with. I think this is funny because it totally doesn't take into account the necessity of movement and making intentional effort to meeting new people and how God can use that as a means to actually form romantic relationships and marriages. I do want to be upfront in saying that I believe that it's God's role to be the primary pursuer of the girl. So when it comes to girls waiting, I think that's a lot more valid at the same time, though. I think there's definitely intentional steps and effort that girls can put in into actually finding those new connections. But for guys in large part, I've seen this idea of waiting for your spouse used as an excuse for guys not to step out of their comfort zone and actually make themselves known in a social situation because they're too scared and they're like, well, you know what? I'm just waiting, you know, when God puts the girl right in front of me, then that'll happen. But they won't actually take that step of effort in actually getting to know somebody. I don't think that's a valid argument against dating apps to say that they're not quote unquote waiting for the person that God has for them. Yes, there may be discontentment in their heart and they need to deal with that. But for a lot of people, they need to make that extra effort. And a dating app is just one of those ways that they can make that extra effort in terms of getting to know new people. Here are some of the reasons that you may not want to be on dating apps. Here are some of their drawbacks. Number one is they put too much emphasis on too little information. Each app will get you to input a certain set of information about yourself, whether that be your height, your political leanies or your religious affiliation. And then depending on the app, it might get you to respond to prompts that they put forward and just try to try to help people understand a little bit more about you. The thing is, is that small little information those couple pictures is all you have to go off of into deciding whether you want to have a week to two week long conversation with the person via text before you actually go out on a date. It's not very efficient and I don't necessarily have a solution to that, but it's just one of the drawbacks. Another big problem with them is that nobody is on them. Well, at least not a lot of Christians are on them, at least in my experience. For me, it's like, wow, I want to be with somebody that's very committed to Christ and has a certain mission mindset as I do. You know, I'm not saying they're not out there on a dating app. I'm just saying it's very slim pickings for a lot of Christians. So if you're going to go into that space where, okay, I'm going to get on a dating app, you got to know there's not a lot of people there. And along with that, it is a time waster. Man, I've spent so much time on those apps, even for the couple weeks that I had them, they just consume my time where usually I would be either reading or writing or working on things. I'm just scrolling, scrolling, you know, typing, do all this stuff, right? And I'm not saying that isn't necessary at some point, like, okay, there's going to be a talking phase for anything. So that is going to be kind of the, you got to get through that. And even though it's not the funnest thing to do, you got to make through the small talk to get to the important stuff. But man, it's just such a time waster from swiping to texting to going to do, you know, it's just, it's a lot. One of the biggest problems that I haven't highlighted yet is its over emphasis on physical appearance and just like those couple pictures, people put so much weight in like those couple pictures and like nitpicking them and like, oh, this person's not cute enough, or maybe there's somebody cuter. I just think it's not a healthy way. You're not really treating them like a human. It's disconnecting who they are from how they look. And I just don't think that's a good way to go about it on a consistent basis. If you're constantly seeing picture, picture, picture, and you're constantly evaluating, am I attracted to them? Am I attracted to them? Am I attracted to them? It's not a healthy way to think I could say more about that. But first, what I want to say is that, yes, I have seen and heard of people that have gotten together based on being on dating apps, and that's their happily ever after and it worked out for them. Great.  I use them. I'm making this video about how I went on all of them. So you know what, I'm definitely no better than you. I found myself, it's so easily swayed towards, yeah, either just like totally fixating on their physical appearance or just wasting so much time or just having a bad heart attitude towards the whole thing. I would get frustrated and angry. It was definitely not good for me. Some people might ask, Isaac, why did you even get on a dating app in the first place? Don't you trust God enough to bring somebody to you? And the honest answer to that is, well, you know what? In my immediate life, there was nobody that I was interested in. So I thought, well, let me take a look at some dating apps and see if I might meet somebody. I do believe that God can use the means of a dating app or Facebook or Instagram or any of these things to bring us into contact with potential spouse. I do have to say at some point it became less of, well, let me get on these dating apps so I can find a potential spouse to, wow, I'm already on a lot of dating apps. I wonder if I got on even more and then I'm able to make a video about this telling people my experience and some of the things I learned. That definitely did cross my mind and maybe that was kind of an ending motivation. By the end, I definitely knew that I wanted to get off of all of them just because, as I said, it wasn't good for me. Now without further ado, I'm going to rank the best to worst dating apps, at least in my opinion. And I have to say, I did not go on all dating apps. And some of you may be disappointed to know that I did not go on Christian mingle. So yeah, so I can't speak for that one. No interest whatsoever to me, especially after the years of joking about it. I couldn't admit defeat like that. The worst one by far is Tinder. I had this app for all of 45 minutes. After I made a profile, I began swiping and I noticed that it really gave you no information about the person whatsoever.  If we're in the context where I can share the gospel with them, then that's great, wonderful. But I'm not in the mode to do any kind of missionary dating. I want to be serious about this and I want to find somebody that's already passionate about their faith. Although I've heard Christian couples meeting on Tinder, to me, it's just like a wasteland till you get there, I guess. There's so many people dressed inappropriately and you're just swiping and swiping and swiping. Maybe it's where I live and they're living in more Christian conservative places where you're more likely to find a Christian on Tinder. I don't know. To me, it was not good. Next, I grouped a couple here in sixth and fifth place. Plenty of fish and e-harmony.  It was just a lot of older people, so it's just not a lot of people on their my age. Okay, in fourth place is Facebook dating. I found out about this as I just downloaded the Facebook app again. So I was like, well, let me see who Mark Zuckerberg wants me to date. It was not good. Do not recommend. I don't recommend. Honestly, yeah, I don't recommend any of these. Yeah, so. In third place is an app that I actually haven't tried yet, but I've heard some good things. It's called Upward. I don't think I'm going to make an account, but it seems relatively positive. Maybe like a little bit better Christian mingle. So check it out if you're interested. In second place is Bumble. I actually really enjoyed this app. It had good information about the person's spiritual beliefs and political leanings and just different info. It was a little bit more thorough, so give you a little bit more insight into who the person actually was. The only problem, though, was that girls have to make the first move in texting the guy, which I'm not a huge fan of just because often the messages that they would leave are just kind of high and hey, and it started the conversation off real rocky. And I've heard this from other guys too. But otherwise it was a pretty good app. The best dating app to me is hinge. And the reason being is it's not a swiping dating app.  It's more like a Facebook profile, at least how I see it or maybe an Instagram profile. And then you can comment on different of their pictures or prompts. And that's how you begin the conversation. It feels much more organic than just kind of matching with the person because you liked how they look. And then all of a sudden you're put in this like chat room to force to have a conversation. That feels weird to me. But this way it seems a little bit more natural. I would love to know you guys perspectives on dating apps and maybe some of your experience with them. If you know people who have gotten together because of them and maybe what which ones that are more beneficial for the Christian community and which ones are not so much. Thank you so much to everyone on Patreon. It is a blessing to be able to get to know you guys and thank you for supporting what I'm doing and helping people follow Jesus daily. It is only through your support that I can continue to do that. If you want to help support my ministry, head down to the link in my bio patreon.com slash daily underscore disciple. Thanks again for watching and I'll see you next time.


Okay, we talk about the basic project settings, about the pinout, about the clock configuration and also the power analyzer. And now I will focus also on the more about the possibilities for the generation, the project. For this I will start the new project. I will here again select the F4, 401, LQFP64 PIM package. I have the RE Nucleau, then I will select this one. Now it's not necessary to choose anything, I will start with the blank project. Then the important part, which I am interested in, here is the project and the settings. Okay, here the project settings. In the first tab as usual I can put the name of my project, then I here put the settings 1, to test the first settings. You can set the location where your project will be stored. You see that the Coupemix create for you also the folder with the project name. You can select the tool chain. But what you can select more? You can select the minimum heap size and minimum stack size. What is the difference? The heap size is usually the buffer or the memory pool, which is used for the library functions. Usually, the functions like printf, sprintf or the memory allocation, the malloc function will use this heap. In case that you don't plan to use these functionalities, you can put here 0. And the stack is definitely used as a temporary storage during the execution for the local variables. For example, or as a temporary storage when you are going into the functions. For this is used the stack. Too small stack can cause the problems. Definitely check if your stack and your heap is in line with your expectations. Definitely also check if your microcontra has enough memory for your stack or heap. And this was the first step. But I am now more interesting about the code generation tab. When I have the first part is here the firmware library package. You know how to install the package. We install it through the help when you find your repository. But now also how the KubeMix working with this package. You can see that in the normal circumstances in the default option is the copy all used libraries into a project. What this means? The KubeMix if I select in my project select no other profiles. I have clean project then he will use in my project only necessary libraries only for the flash for the clocks. But with this first option he will copy into my project rest of the libraries. They will be not into my IDE but they will be in the project folder. We can test this. Then I check this one. I click on the OK and I will generate my project. OK. I can open my project OK. And you can see in the drivers I have only minimum files I have the timers RDC only the profiles which I need. But if you look into here into my project into settings into divers into HL divers to source you can see I have a lot more more libraries than this is valid for the first first option. Now I can do the similar process I will do the save as I will save the different different project number two and here I will generate only my project only with the necessary library files. I click on the OK I create my project I will open my project you can see in the divers are the same files like in the last one with the first option. But if you look into into my project into settings to into the drivers into the HL driver you see they are only necessary files. This is the second option to copy only necessary files. Usually our package will be smaller but in case we decided later on that we want to add more profiles we need to copy them on our own. OK. I will create the third project here I select the last option the last option is specific this option will never copy any file into our project but it only create the reference between our project and between cube and mixer repository then I here click on the OK. Now I will generate my code and I will click on open and we will wait until the IR will be opened OK we can look into the drivers you can see still the drivers like the last time but if you look into into our folder into settings 3 you can see there is no driver driver folder everything is is only the reference we here click the right click and I hope that that the here will be the the path then not file properties this is the correct one you can see he is pointing into my repository. This option can be advantage that you can have all your libraries on the one one place in case that you change something in the libraries it will be automatically reflected in all your projects the disadvantage is that you cannot simply move your projects because you need also to copy the repository then be careful on this. OK now we can move to the next settings I will save again save as I will create my settings number 4 I am using mainly the copy all used libraries in case that I want to add something in the future.


I don't know how far you can read these slides, can you read it at the back? Anyway, it's a joke, so no matter. But shall I read it out? It just came to me about half an hour ago, I thought I must share this with you, especially in this context. Even I can't read it. Mummy, I have a drinking problem. Oh my God, Timmy, you're only six. This is your fault, Bob, she tells the father. My fault? Maybe if you'd spend more time with him. Our six-year-old has a drinking problem. He sure as hell doesn't need a role model like you. Then I've done nothing but give for this family and this is what I get. The father says, I'm leaving, fine, I don't need you. And Timmy sure doesn't need you. And then the mother says, oh Timmy, don't cry, it'll be okay, we'll be alright without daddy and stuff like that. And she hugs him and so on. Talk to me, Timmy, tell me about your drinking problem. So the little child takes out the book from his bag and says, if Joe drinks one liter of juice and Tom drinks two liters of juice, how much do they both drink? So this just illustrates quite cutely, I felt. The fact that often we don't listen, we jump to conclusions and that illustrates a lot of the things that were discussed in yesterday's class. And listening is very important. Listening to yourself also. Often we have a problem because we rush into defining what a solution is.  And you find this often with students. You jump to you and you pose them a problem and before you know it, they've just jumped at the first answer that comes to them which might not be the best one. So we are hoping that all the students here, not most of you, all of you, when you go out into industry, you'll be more than just technically good or technicians. Most of you will have to take up very soon a leadership position as has been our experience with all our students who go out from here. And once you get into those kind of positions, communicating is very important. More important than communicating to others is listening. People don't realize the role of a manager is to listen. The role of a manager is to listen. The role of a guide is also to listen. It's not for me to tell you what to do. It's for me to listen to your ideas because you might have more ideas because you have more time than what we have. So this takes this story ahead. And this morning we have our colleague here, Professor Prakash Vedya. And today we thought we'd illustrate this whole idea about listening and not taking by the whole notion of proofreading. How many of you here are acquainted with the proofreading language? There's a very distinct proofreading language. One of my avatars before I came to IIT was I was running a small publishing house. And one regret is that I never got down to studying the details of proofreading. So I'm hoping to learn something today also. And this also reflects the fact that often we get burdened by seminar reports and MTP reports which are very quickly hacked together. And you don't seem to realize that before you even come to the waver, you have lost marks, you have lost points because your presentation has been bad. You've got bad English, it's badly formatted. You've not thought enough as to how you want to present and stuff like that. And when the examiner comes into the room to have the waver or even the guide reads that thing, there's a bias against you because you've shown slip shot shoddiness in presenting a work and the attitude in the reader is that if they don't care, why should I care? And so the elements of putting forward a good presentation is in proofreading it. Ideally when you write a report, you should also get a friend to look at it because the friend will spot things that you would never even have dreamt of. So in this two sessions we have today and on Thursday, I wanted the whole class here because we'll go through the motions step by step. Today we'll introduce you to the language of proofreading, the symbols of proofreading and so on. And on Thursday we will give you a written matter which we will give you, which you will proofread. And then we'll see how many of you pick up how many errors. And in the class we'll go through what you should have noticed. And there's also an offline assignment where we want each of you to go and look at a TED talk. You saw one example yesterday. Make a half page note on it, right? Double spaced note and just upload it. Listen to a TED talk, make a half page note on it and upload it on model for us, right? And bring a print out with you next day to the class on Thursday. Bring a print out and we'll hand those things around or shuffle them around and you will proofread somebody else's TED talk summary, okay? So one more thing I'd like to say is that most of you are used to expressing yourself in spoken language. Language I say because not everybody is absolutely comfortable in English, right? Many of you must be comfortable in your own mother tongues and stuff like that. But when it comes to written communication, right? You might not realize the level or the quality of your written communication. And I feel that if you guys are not so accurate in your own mother tongue, there's a very good chance that that inaccuracy will also be found in your English written communication, okay? So this is now a session in which we'll look at the whole notion of proofreading. I'll ask Prakash Bediya to join us here. He's got an interesting background in the sense that he's an IIT Bombay alumnus. He used to be the same batch mate as Professor Uday Gaitonde here and he works with Professor Fatak's 10,000 teacher training project. And apart from his many skills is that he's got a passion for technical writing and he's also deputy director of research at an embedded systems company in Mahpe called App Labs. I don't know how many of you have heard of it. So he's working a lot on things like the clicker project. But technical writing is his passion, so it gives me pleasure to invite him here today. Sorry, this connection doesn't seem to be working.  The first part you saw, this was a lecture given about two years ago when this teacher's training program started for distance education. So we had maybe 30, 40 people on staff at that time and to train them about proofreading because we had to do a lot of documentation and publication. That's why these lectures were conducted. And I'll introduce Firuza, my assistant. She had joined at that time and she has attended this lecture live, which you saw just now. She is an MCA and in her six years of college, she has written six books about software. So before she joined here, she had written six books. So she is closely connected with technical writing. So first, proofreading is not a very popular subject or nobody considers it to be important. It's not on anybody's radar. It's like backstage work, which is not recognized. So when we try to explain that proofreading is required when you create a document, many people are surprised. They say we write so well. There is no need of doing any such thing. I'll give an illustration that there was a boy who was seeing double. It is called Diplopia that both the eyes don't align and you start seeing double images. He was not aware that he had this problem. So his father told him that son, you are seeing double. He said, how is it possible if that were so? I would have seen four moons instead of two in the sky. He is already seeing double, but he thinks double of that is double. So that is the problem with proofreading. It is the problem with all quality control. Proofreading is a kind of document quality control and quality control nobody likes. Everybody likes production. Everybody likes design. Everybody likes innovation. Nobody likes quality control and maintenance. But without these two, the production cycle is not complete. Whenever in quality control, a quality control expert goes to an industry and asks, do you have quality problems? They say, no, maybe other industries have problem. We don't have problem. For us, everything is running smoothly. So this is the first problem that many people are not aware that they have a problem. First, you have to recognize that you require attention to this. That is the first step towards learning proofreading. After you have understood that, then you can learn the techniques and then you can understand what is the significance of those techniques. So generally, when a manuscript is written by average people and a proofreader checks it, if you take an A4 size sheet, that is this size, it will have about 30 lines of type script. And each of these lines will have at least one error. That is the statistical average. So if you are making a one-page document or one paragraph, then nobody will notice the errors. But if you are writing a 300-page book, then 13 to 300 is 9000 errors. And these won't escape because anybody who reads the book is likely to notice some errors or the other. So the first step is to reduce these errors by checking and correcting. After your first pass of correction, the error level will come to approximately 1 to 3 per page. That is on the whole page, you will see one red mark somewhere, 1 to 3 marks. Even then in a 300-page book, you will have 300 to 900 errors, which is also not small. So you have to correct again. After that, you will reach a level of roughly one error in 10 pages. So if you have a short document, it will be error-free. But a long document like a thesis will not remain error-free. And at the last stage, the ideal is of course zero errors, but which is not practically attainable. So you will reach a level of few errors in 300 pages. And most of the published material has this level. If you have say few errors and you detect them, then you don't announce them because it makes people aware. If there are too many errors, then you attach an errata at the end of the book. But this is considered shameful in publishing industry. In any foreign book, you will hardly find an errata. If there are few errors, they are corrected in the next edition. They are not announced. In Indian books, there is never an errata because they never check. If you read, you will find out that there are many mistakes. But we want to read the standard of what is called as edited English. Now English has become common people's language and everybody thinks that he has command over that. But the English used in publishing, whether professional publishing or academic reports, industry reports, etc. has to keep a certain standard. That has to be the publishing standard and that is called edited English standard. So if we want to become professionals and enter in industry administration, international trade, then our communication, our written communication and publications has to follow edited English standard so that we become world class. Now you might ask that when you first check the proof, why don't you reach this zero error or few errors? Why do you have to do it three times or four times? Can anybody take me? Why does it happen? Practically, whenever you try this, you will find out you cannot take out all the errors in the first pass. What is the reason for that? If you are looking carefully word by word, why don't you find all the errors in one pass? It will simplify life. No, there may be independent errors. What you are saying is there may be correlated errors which will appear after your first pass. That is also not true. Most of the errors are actually standalone errors. The reason is very surprising that we think that writing is a process and error correction is at a higher level and it is immune to errors. But error correction is also a process. So that is also error prone. So while correcting a lot of errors, you are likely to miss some of them. This is the technical reason for that. You can never do it in one pass. So you have to do it multiple times. Now when you do multiple times, firstly it is boring. Firstly you have written it. Then if you go through four times, you will find that if you do it yourself, there will be still some errors left. Because when you do it the second time, your brain already knows what is the content and it will miss the same errors as it missed the first time. So it is always better to have many eyeballs looking at your manuscript. So proof reading is not a lonely affair. If you write, you ask your friends or classmates to correct it and vice versa. That when somebody else writes, you should form a group and circulate the manuscript and errors which are missed in the first pass will be detected in subsequent passes and everybody will benefit. If everybody does it alone, nobody will reach that level. There is an anecdote that what is the difference between heaven and hell? Supposedly both have all the facilities etc. Both have lot of food.  So what is the reason? Because in both the places everybody's hands are tied at 90 degrees. So if you tie your hand at 90 degrees like this and try to eat, you can't eat.  So everybody is hungry. In heaven also they can't eat by themselves but they feed each other. That is why they are satisfied. So that is the technique to use. That you have to read each other's manuscripts and you will find errors and you will also learn about how other people write and what kind of errors other people make etc. So when we actually do exercises, later in class exercises you will have to work alone. But later on when you use this technique in your actual life, you will have to form groups and since you will know the common language of this, then everybody will be on the same page. So manuscripts have to be checked multiple times. In publishing industry we will see how they work. What the author writes? Generally he used to write by hand. So it is called manuscript. That means hand. So it is hand written. It is called capital MS. Referring to the short form is capital MS. So the manuscript goes to typesetting or used to go to typesetting. Then after typesetting they used to take a print out of that. That is actual printing, physical printing. And it used to be checked by proofreader. So proofreader used to do what? He used to check it against the manuscript. Whether what is written in the manuscript has been typeset. Means he used to verify, not validate the document. Verify whether it is as per original. If the original has a mistake, proofreader would point out from his experience. But he would not correct it. But whatever mistakes occurred in typesetting, he would correct. And whatever related to the format of the document etc. Those he would correct. And he would send back the manuscript to the author. And author had to certify that this type script is otherwise correct except for these errors. After it came back, those used to be modified. And the final proof would go to the author. Then author had to certify that this is error free. Then he would keep one copy of that with himself and submit one copy for publication. If there was a dispute later on, then they would check against each other's copy. This was the method that's why publishing used to take very long. Before the advent of electronic publishing, it used to take very long. Even today, now authors are themselves typesetters. So there are fewer proofreaders. In the olden days, newspapers used to have a whole full of proofreaders. Whatever stories were filed, they used to check. Now the reporter himself is responsible for what he files. If a mistake is found in that, then the reporter is responsible. Nowadays, all magazines and journals also have the same policy.  If there are errors, they won't check for errors like they used to. The post of proofreader is now empty and everybody has to become a proofreader now. That's why we have to understand the mechanics of this. So if you want a document to be proofreaded, then while preparing the document itself, you have to take care. Like they say if you design a product, it has to be designed for manufacturability. You might make a prototype and exhibit it, but during manufacturing, they might find that it is not practicable. So that type script that you prepare has to observe certain rules so that it becomes easier for proofreading and easier for final formatting. So the first rule is that anything, we will call this as a draft that is the first version. Any draft has to be on one side of paper. You never write or print back to back. The back is supposed to be empty. This is the first rule. Second rule is while printing out, you have to use double spacing. That is, you have to leave one blank line after every line. So the document will become about twice long, but that is worth it. Why? Because as we saw, average there is one error per line in the first manuscript. But these errors are not uniformly distributed. That means some lines might have 4 or 5 errors. Some lines might have 0 errors. If there are 4 or 5 errors in a line, how will you show them? The manuscript will get crowded and somebody is likely to miss while correcting. So if you have blank line above every line, then you correct just above where the error has occurred in the blank space. Then when you read in the blank space, you know where the error is. Plus as we will see later on, the errors are also summarized in the margins. So you have to leave margins on both sides in a manuscript. So by looking at margins, you know that there are 4 errors in this line. You just go through the margin column and you know how many errors are there. So the errors are pointed out twice, once where it occurs and once in the line in which it has occurred, so that they are not missed out. So these are the first two rules that any document must be single sided. There is no pasting, no stapling, no pins allowed. If you have to attach something, you either rewrite it or retype it. But no attachment because if that gets lost anytime, your document will become terrible. And if you have to add substantial matter in between, then you give an extra page number like 1a and add the page. But don't write in margin, don't write like this, etc. Like people write on a postcard that after writing they realize there is still some more matter. Then they will go back and write in the margins, etc. So we shouldn't write like that. It has to be in double space format and on one side only. So we have understood basically why proofreading is required and what are the preliminary precautions we have to take while proofreading. Now you also must have made documents, you must have checked and corrected and you must have done it informally that you will have pointed out something, etc. And even if somebody is correcting, they will intuitively understand. So why is there a separate language required? Anybody can answer? See if you are correcting yourself, you can set up your own language like children have their own language which only they understand. But if you want to communicate to others and as we have seen that proofreading has to be done in a group and in principle anybody else should be able to understand what you have written. That means you need a standard language so that otherwise there will be misunderstanding in that and the whole purpose of error correction will go. So that's why you have to use standardized marks so that anybody uses the same symbols and they have the same meaning. So when we see those symbols, those symbols have been summarized on a sheet. So we are distributing these, you will each have a copy and we will go through this list. So you have this in your hand in any case, you don't have to look up on the screen. So as you can see there are three types of marks. The first are called operational signs that is the first column. Then second column is called typographical signs and punctuation marks. So punctuation marks we will cover only shortly in this session because we will have whole session for only punctuation. And as we will find out later that more than half the errors in proofreading are of punctuation. That's why we need a separate session for that but only the marks we will understand but how to actually find out where punctuation is required. That will require a separate session. So the first sign is delete. So if you want to delete something normally you might have typed an extra letter or you might also want to delete some word. So how will you indicate that? If you write D for delete like English D then the checker will think that you want to add D over there and he will type extra D in that place.  So that it is not confused with normal English. So this del indicates that delete. So whichever you want to whichever letter you want to remove. You just cross it and write del over there. That means it is delete. Now when you delete you want to cover up the space and join the word together. So otherwise there will be a blank like a missing tooth. So to indicate that the next mark says that close up. That is remove the space. Now in word processing it automatically happens but in the olden days this was not automatic. You had to rearrange the whole type. So and third symbol is a combination of these two. That is you write del and put this mark that join together. So this is only for deleting letters within a word. If you are deleting a whole word you just cross it with a horizontal line.  So for that you do not use this join up symbol. Similarly if you are removing the whole sentence then you just scratch it with a horizontal line. And it is understood that that space will be made up. But only for individual letters you have to use this delete and join. Then after you have done correction says when you read on you might find out that maybe what you did was wrong. That what the author wanted to say was better said in the original format. Now what do you do? You can't rub on the manuscript. So next to the correction you write state and circle it. Whatever you circle during proofreading is not entered on the final copy. That means it is your comment whatever is circled. So state is a latin word which means let it stay or let it stand. So that will cancel all your corrections nearby. And restore it is like undo command on a computer. So this is the undo command state. Then sometimes you may need to insert space like words get joined up. That proper space is not left. So this hash is the symbol for space. This means space. So wherever there is space required you put a vertical line in that place between two letters. And then put a hash there. That means there is a space required there. Then these next three symbols are not relevant anymore because these are for mechanical type setting. When there is to actually put physical types for that these symbols are required. But those are not required because now your word processor takes care of everything. After that we come to an inverted P. That is mirror image P with a double vertical line. This means make a paragraph. Sometimes the author will keep on writing continuously without realizing that he has actually finished the old concept and is addressing something else. So if you realize that that has happened when a new topic starts. Then there you make a vertical line and put this. There are also other ways of doing it. You can put a reverse z like thing or put a reverse l at that place. That means you start a new line. Make a new paragraph. Yes. We will come to that. At present it is only as we said it is only verification. Correct. The proofreader also has to check the content. Especially in our case because we are not checking random matter. We are checking related matter and we are supposed to know. We are not supposed to do it mechanically. Even the older proofreader used to make out that here the topic has changed and they would put this symbol. Whether you check for content, your point is or only the form. First we have to correct the form and then the content. Now this next symbol also you forget. Move right, move left is if the lines are not aligned properly while typing. Which also does not happen with modern word processes because if you give justification it will justify everything. But with titles and such things this can happen that somebody might type the title starting from left and it may have to be centered. So you have to say this indicates that you push the type on left or right. If it is from both sides then you center. Move up, move down is also not required any longer. Left, left, left is now justification that many people do only left justification and right is left free. But that does not look good. You should always justify on both sides for printed matter. If you see professional publications they never do this like magazines etc. They will occupy the full column, newspaper they will occupy the full column. That looks good. Now transpose and spell out. Transpose means many times you might have noticed that letters get interchanged. Especially if one letter is typed by left hand and the other by right hand. The brain knows that these two are to be typed but they may not be pressed in correct sequence. So letters get interchanged especially between two hands they tend to get interchanged. Because one hand works faster than the other and that letter comes first. So in that case you write transpose and the symbol used suppose the word is doer and it is spelled as D-E-O-R. Then what you do is you put a symbol like this which says that you put left on right and right on left. Sometimes two words might get interchanged like verb and noun etc. They come in wrong sequence. Then for the whole word you can put like this. The word or even phrases sometimes you might find that some phrase should come as introductory phrase which has come later. Then you can use the same symbol for phrases also that means transpose you interchanged. Nowadays it is simple because you can pick it up and place it elsewhere etc. Spell out this is required in modern times because everybody tends to use short forms. So within a closed community the short forms are understood but when you are writing for somebody else and especially professional writing short forms are not permitted unless they are approved short forms. Only some acronyms if you are using then you have to declare the first time it occurs. Otherwise the reader will be clueless if first time you do not declare what is your full form. But otherwise like prof for professor, lip for a library such things are not allowed in professional writing. All words must be spelled out. So this says that you spell out whatever is this word. Then the next are typographical signs that is the kind of font you are going to use. So this ital means set in italics that is guilted. So if you want to emphasize the word or if it is the title of a book or some such thing then you want to put it in italics that word stands out. Then you write italic. Reverse of that is set in roman type that is normal english. Because sometimes the author specially with word processing gives the italic command and forgets to put it off. Then you will find lot of matter becomes italic though he wanted only a few things to be italic. Then you point it out and say that go back to roman script.  So this is roman type. Bf is boldface you know boldface. So now it is simple. Now capital and small this is capital and small what we call small is called lowercase. You must have seen in word processing and capital is called uppercase. You know why this is called uppercase and lowercase instead of capital and small. See if you observe statistically most of the letters are small. And in english at least only the first letter of a sentence and some proper nouns start with capital. But otherwise capitals are rarely used. So if you want to have stock of type faces then you will have fewer capital type faces and many more smaller type faces. In production because they used to actually put those types in a box and make printing. So you need that much stock to make those pages. So while composing there is to keep the small letters in a box like this like pigeon holes. And then pick up from that and set. Capitals are rarely required so they were put like this like your laptop screen is. They were more difficult to access. Like in the kitchen you will find those things which are normally required will be in front. Those things you rarely require will be on the wall. So the organization used to be like this. There used to be one set of boxes like this and another inclined on the table. So this box was called uppercase and this was called lowercase. So it was for the printer that this letter is to be taken from uppercase then it is automatically capital. Similarly lowercase that it is automatically small. Still the same terms are used even though now this method has vanished. We do not call capital and small that is only in school. They are called uppercase lowercase. A C small capital that is the letter is the same size as lowercase but it is capital. That is used for emphasis in some places. There are specific rules for that. The height of the letter is that of a small letter but it is capital letter. Next check type image is also not required because now everything is automated. Next two marks that is V and inverted V are required and they are especially required for punctuation. So when you say V and put something inside the V that means it is above the line. You are lifting it up with this V. So if you want to give a superscript like giving references then you have to put that number. If you write the number in the same line then people will try to read as part of the line the reference number. So footnotes reference numbers etc which you want to indicate those you should write like this that it is superscript. Even in mathematical notation like power when saying a raise to x then how will you tell that x is not in the same line. It is above a that is superscript sign. Yeah. Yeah. Yeah. Okay. Few minutes. They have to leave with it. Okay fine. So remaining is punctuation marks which you can read by yourself. Now next time what we will do is what you want to tell them an exercise. Yeah. You can you can create some documents by yourself and maybe check with each other or check by yourself using these signs. So that you will get accustomed to using these signs. In the next session that is on Thursday. Yeah. Okay. So like I said it will be useful if each of you can see a TED talk on your own. Summarize it in one page. Print it out. Double spaced. It can be on two sides of a page or whatever. Right. And bring it to class next time. And what we will do is we will change it around or shuffle it around and you will proofread your friends text. And then we have a standard text which we will bring next time. And we will invite you to proofread that and find errors. And you will be quite interested to know how many varying sorts of errors we are able to spot in that in that manuscript. And this will be a very interesting exercise. Okay. So next lecture which is on Thursday is a practical. Right. So we will see you then. So see a TED talk. Make a summary of it and post it on Moodle and bring a print out with you in class. Double spaced. Thanks.


That's really pretty bright. OK. OK, Ken Dwayne, you guys win for attendance. Hi, everybody. My name is Gary Kovorkin. Welcome to the Cisco sponsored session number three today at the OpenStack Summit. How was lunch? What'd they have? I didn't make it. Seriously? Oh, man. OK. I got to get off the event team. So again, welcome to our room. This is the third of our sponsored sessions today. And as I mentioned, when we're passing out the cards, we will be doing a small giveaway at the end of the session. We'll collect all the cards at the end of the talk. With that being said, I'm going to quickly introduce our presenters for today. We've got a great duo of scaling containers in OpenStack, Dwayne de Capitay, our director of product management, and Ken Owens, our CTO for Cisco Cloud and the virtualization team. With that, I bring you Dwayne and scaling containers in OpenStack. So good afternoon and welcome. I appreciate you attending Standing Room Only all the way in the back. So today, we're going to be discussing two of my favorite topics, containers and OpenStack. We're going to be talking about how OpenStack can make your container deployments easier and how to scale your OpenStack and container projects. So I'm Dwayne director of OpenStack Product Management. We're joined today by Ken, our CTO of Cloud Services. And we're looking forward to a great conversation about containers and OpenStack. So containers is one of the main themes of this summit. And it's virtually top of mind with everyone in our industry. So quick show of hands. Who here is in the process of creating a container strategy? Exactly. Who here is deploying containers in production currently? Excellent. Excellent. Good. Everyone is thinking about containers. We're going to talk all things containers and OpenStack in this session today. We're going to do a deep dive on some of the container-focused projects in the OpenStack Foundation, including Kala and Magnum. Then we're going to talk about some of the recent product announcements from Cisco, including NFVI Network Function Virtualization Infrastructure, which is built with container and OpenStacks, as well as Mantle and Shift. Shift, our new platform, is a service for containers in OpenStack. We'll also have a demo of Mantle and Shift. And then we'll do a deep dive on two great plugins, Conteev, which is a plug-in to ACI. Who here saw the great presentation from Mike Cohen in the ACI and Sun Guard earlier today? Great. So Conteev is a plug-in to ACI. We'll talk about that and do a demo, as well as Kallico. Really nice Layer 3 plug-in. Works with Docker networking. Works with Rocket networking. Works with OpenStack Neutron and other environments as well. And then we'll close with a summary and a Q&A. But this is our session today. We're going to make it interactive. We're going to have some fun. And we're looking forward to a great conversation on containers and OpenStack. So containers have been around for a long time, actually since UNIX in the 70s. I mean, namespaces, control groups. But it wasn't until a little company you may have heard of called Docker really made containers a household name. And they did some really good things. They defined a container image format. And they also created a hub repository to put container images. So Docker got lots of people thinking about containers, which is awesome. Rocket, part of CoreOS, really good containers. Some nice security enhancements as well. Ubuntu has good container, Nova and Lexi. So Linux containers, LXC or LexiD, the hypervisor for container management. Really good Nova interactions there. Also OpenVZ, it's been around for a while. A good container and storage integration. This is parallels virtuoso. And people like containers in their top of mind. They're lightweight. They're fast. They share the kernel. But it doesn't have to be a Linux kernel. It can also be a Windows kernel. So Azure container, excuse me, Service is now GA. Windows Server 2016 has both Windows Server containers as well as Hyper-V containers, which you see on the right-hand side, which is interesting because it's a container in a Hyper-V VM, which is very interesting. But we are an open source community here at the OpenStack Foundation. And we like open source. And the Linux Foundation is working on two major initiatives for containers we're going to talk about today. OCI, Open Container Initiative, and a CNCF, Cloud Native Computing Foundation. So this was originally OCP, right? Open Container Platform. But that sounds a little bit too much like another project in the industry. So it's not OCP. It's not OCD. It's OCI, Open Container Initiative, right? And we at Cisco, we are proud to be a part of it. The project is designed to create standards around container formats and runtime. So the container runtime spec is out. It's nice because it's not a monolithic standard. It's modular, which is nice. And also the application spec is also out there as well, which is nice because it starts talking about some different flexibility in terms of how to deploy containers in different environments. So the CNCF, Cloud Native Computing Foundation, which Cisco is also very proud to be a member of, is designed to create new common container technologies around internet-scale computing. And you may have heard recently that the first hosted project was announced something you may have heard of called Kubernetes, right? Also, very top of mind, everyone's talking about Kubernetes. So it's very exciting that Kubernetes is now part of CNCF. At the same time, they also announced their first technical oversight committee. And whose picture is that popping up there? So that's Ken. He's on the technical oversight committee for CNCF. He's also on the governing board for OCI. So Ken, I heard that you were the first person unanimously selected to the TOC. Is that true? It's awesome. So I voted for you, by the way. So very exciting. I'm also part of the marketing committee for CNCF as well as the product management committee. We're in planning lots of interesting things happening. There's Cisco Live. The summer, who here is planning on going to Cisco Live? This year, awesome. Thank you. I'm also container con in August. It's gonna be very interesting as well. So lots of good events happening this summer. So now let's take a deep dive about some of the container projects in the OpenStack Foundation. So one is Kala. So Kala is great. The project technical lead, Steven Day, because with Cisco. The idea behind Kala is to make a better OpenStack with containers. And so fundamentally putting OpenStack services in Docker containers and managing with Ansible Playbooks. So it's very powerful. It's designed to provide production ready containers and deployment tools for operating OpenStack Clouds. So this is the use of containers to operate OpenStack Clouds. So in the Liberty release, the focus was a little bit more on deploying OpenStack Clouds. So it's in the big tent to deploy up to a hundred nodes. All the major services are there. Nova, Glantz, Keystone, Sethback Storage, choice of distributions. But the focus was more on deployment rather than operations. However, with the Mataka release, the focus became on the operational side. Security enhancements were added, upgrade, reconfigure. A deployment time was reduced by 80%. New services around the operations, including Elastase Search and Kibana. So with Mataka, the focus is on operating OpenStack Clouds at production scale. So very exciting. A lot of the good work that's going on with Kala. In addition to Kala, we're also very excited about the Magnum project. So Magnum is essentially designed to make, that's a good sign, there we go. So Magnum is designed to make containers a first class resource within OpenStack. And it's the first project, if you will, allows multi-tenant support for containers as a service. It does this by creating an asynchronous API around heat templates. So it's asynchronous, so it scales great. It leverages heat. So it's essentially a wrapper around heat, leverages the same identity mechanisms, Keystone. So it's a really nice way to make containers kind of a first class resource within OpenStack. So the architecture is nice. So it basically supports multiple container orchestration engines. Kubernetes is supported. Swarm is supported. Mesos is supported and saved with Kubernetes. So by default, Magnum is gonna create a minimum of two VMs. One for the worker node and one for the master node in Kubernetes. Those are all installed on a micro OS, whether it's Fedora, Atomic, Core OS. And then it's all managed with heat templates. All the OpenStack services, Nova, Neutron, Ironic. So it's a great way to kind of provide container as a service within OpenStack. In addition to Magnum, there's also some very interesting things going on in the Courier project, right? So this essentially maps Docker networking, lib network and converts it into Neutron APIs. Lots of benefits in doing that. Now you can network your containers just like your VMs within OpenStack, but you can also use all the Neutron plugins. You can use OBS layer two plugins as well as Calico plugin, which we'll be talking about a little bit later as well. So lots of interesting things happening within Courier on the OpenStack foundation. So Cisco recently announced some major new products. One was NFVI, Network Function Virtualization Infrastructure. This was announced at Mobile World Congress in February, built with containers and OpenStack. NFVI is very nice, very powerful because it's kind of the best of both worlds, right? You have the flexibility of network function virtualization, but it's all on turnkey infrastructure. So it installs well, it configures well, it scales well, and it's very nice to scale with different networking plugins. It's built with our partners, Red Hat and Intel, very excited to be working with them. So RELL OSP, RELL KVM, as well as Intel technology like SRIOV, single root IO virtualization from their enhanced platform awareness. But even though it's a built-in partnership with Red Hat and Intel, it's a Cisco product, so single access to support, single point of support. So we're very excited. There's also demos of NFVI downstairs and after the session also. In addition to NFVI, another product that was announced at Cisco Live Berlin also in February was our new platform as a service, Mantle and Shipped, which supports both containers and OpenStack. And now I'd like to turn it over to Ken for a deep dive on Mantle, Shipped, as well as Conti and Calico. Thanks, Gary. Thanks, Dwayne. So when I kind of looked at how containers are evolving over the last several years, it's kind of obvious that there's different use cases that you want to address. And so the first one, it's kind of looking at how do we help, kind of what I like to call the IT administrators, the milk administrators, the compute administrators, the infrastructure admins, how do we help them make managing and running containers as a service much easier and faster for their business. The other two groups are sort of both developer personas, but they have kind of different interests, right? One is more cloud native development, so they just want to write their code, push it out as fast as they can. The other ones are more on the data analytics, data scientists kind of side, trying to figure out, like how do I take business insights from my application data that I'm creating and how do I then automatically make enhancements to my application to drive further business improvement? The experience is sort of, I kind of want to put like an end-to-end view of what the user experience was trying to accomplish was. And so if you can't think about this from a developer-centric viewpoint first, most developers just want to write their code in the way they always have written their code. Most developers have sort of, I call it a religion, around how they develop their code. But then when they go to deploy it, they want to be able to just deploy it wherever it makes sense from a business standpoint. They don't have to want to figure out how do I write to these other infrastructure APIs or how do I manage this new API that's just been released by Amazon, for instance, and how would that impact my code deployment there? So they want to just basically write their code and then have a multitude of options to deploy to and have sort of the, what I like to say, the value of cloud was being able to kind of automate all this infrastructure for IT, the value of what we're trying to build is sort of automating all of the software development lifecycle for developers. So give them a way to sort of develop their code, deploy it in a multitude of options without having to understand the underlying physical APIs of those underlying infrastructures. The path to do this is sort of going from the entire SDLC process where we have different tools that we've completely integrated and tested and validated across multiple infrastructures we can deploy into. And I'll show kind of a demo of this in a few minutes. From a container standpoint, we're leveraging Docker containers using both Meizos for sort of the, like I call it data scientist persona use case, as well as Kubernetes for more cloud native development. Although you can use either one in either case, you don't have to, just because you're doing data science doesn't mean you're going to leverage only Meizos. But most of the frameworks exist in Meizos for kind of the data type of applications. The other piece then was as you've deployed containers, you know it's pretty easy to get a Docker container deployed and it's pretty easy to like write your code to deploy in that container. But then if something goes wrong, it's not so easy to kind of identify where in that whole process of marathon or Kubernetes did something break. And so we spent a lot of time kind of looking at how to enhance that visibility into the container deployment scenario, as well as the application service dependencies that sort of get created on the fly. Like when you scale up an application, there are dependencies that sort of get deployed underneath that scale up request that we kind of kind of track those dependencies and make sure that all the services are up and kind of monitoring each of those services to see what their performance is like. And then we want to kind of feed all this back into the issue management system so that if there is a problem in the code, the developer can track that through the processes they use today. The key to the kind of the deployment piece of this is under the covers and we call it Mantle, to kind of be the bedrock of microservices, if you will. We sort of looked at it more from not just a container infrastructure, but what do you need to sort of do an entire, you know, management and maintaining of a new infrastructure for the data center. And so we have sort of a similar model as you would think, you have these control nodes and you have the resource nodes. We also have some edge nodes now to do kind of like low balancing and firewalling between different service boundaries. We solved the problem of kind of deploying this to a single node or a single data center, but our main focus was really on how do we deploy containers across multiple clouds. And so we spent most of our time kind of looking at and developing a way to make sure that when you create your application and you want to use a service that's in Amazon and a service that's in Google, you have the ability to create one application that leverages those two different services without having to deploy your application to either one of those clouds. And so we kind of take care of all that complexity and the networking needed to do that and the service discovery that's required to do that and all the enhancements and routing to make sure that you can route between these different clouds all under the covers for the developers. They don't have to think about that or worry about that. The nice thing about Mantle though is if you do really care about that, we let you have access directly into Mantle as well. So you can go in and modify and clean up and kind of pre-configure what you want to have happen. So at Cisco Live a few months ago, this is where we're at today with Shipt and Mantle. We're using Terraform as sort of that abstraction layer to the infrastructure. And so for a lot of OpenStack as a good example, we have several packages that work with OpenStack versions and working with Magnum as a Terraform package just for Magnum for instance. But if you also want to run across public clouds, we want to support public clouds as well. So we have support and Terraform packages for all of those including vSphere. And so if you're running in a VMware environment and you're trying to make the transition to containers, we have a platform that kind of help you with that whole transition from VMware to containers. And it's not like an all or nothing. It's sort of this, I like to kind of have a hybrid DevOps model. You can continue to work in the environment you're working in today. You can add the capabilities that the cloud native capabilities are bringing you in the public domain and in your private domain. And you can bridge those two over time in a way that makes sense for your business. So this is what the interface for shipped looks like. It's at syscoshipped.io. It's very easy to use. You, all you need is a GitHub account. Right now we're going to add some additional identity providers as our enterprise customers kind of ask us to add additional capabilities. But right now it's mostly just GitHub. The mantra we have is build deploy run. And you'll see me kind of go through what I mean by that mantra in a few minutes. So when you click on that, sign in, if it's your first time signing in with your GitHub credentials, you have the ability to select private repos or public repos of both. If you're using an enterprise GitHub account, we also allow you to connect into your enterprise GitHub account as well through the same process. Once you go into build, the build use case, like I mentioned before, most developers have a way they like to develop. And so the goal is to make this as lightweight and as easy to leverage what they're doing today as possible. And so using kind of the 12 factor process for developing, we create a project in GitHub when you create a new project.  And as you can notice, we have a bunch of different little starter packages that you can use in your development. Most, I can tell you the smallest of these is like, is goaling the most, I guess heavy of them is probably like the Python one we have. But there are different packages you can use to do your development to kind of help you with the build pack and get started. We also give you access to, like if you want to get a Docker Hub image or you have your images in Docker Hub, we've connected into Docker Hub. So you can go into Docker Hub, search for an image that you want to use, take whatever parameters that vendor has said you have to fill in to use that image and we deploy that as part of your development environment that I'll show you in a minute as well. We also have added a few things like some Cisco technologies if you're using Tropo for like collaboration or using the APIC EM, which I'll show an example of Contif a little bit later. We have the ability to kind of integrate with Cisco public APIs as well. So you can then leverage their API code within your development.  We give you a command to copy and paste. You paste it into your terminal, pours in the code, we're using vagrant to stuff like local VMs on your desktop. You leverage it as Eclipse plugins as well, so if you're using Eclipse, if you're using other development frameworks that has integrations to pretty much all the popular development tools. So you just develop what you normally would, would develop and then you just do a get push to push your code back up to GitHub. If you use an enterprise GitHub, you do a get push into your enterprise GitHub account. Once you do that, it goes back to this screen where it says that you've built your project, now it's time to deploy it. And this is an example that kind of shows, I think sort of the power of what we've tried to develop here, which is your building of your application is very dependent today on where you plan on deploying it in the future. And so what we try to do here is say, you could have a staging environment that's maybe in Amazon, you could have a QA environment that's over in this private environment that you do your QA testing in and your production environment could be in Google. We don't only care where you have all your different environments at, but most companies have different environments that they test and do QA and deployments in.  So you can do this on a per container or per service basis, if you will. And then we tell you where to deploy that environment. You can create new environments by just adding a new environment and entering in kind of the, like your credentials, we're using an open source security tool called Vault from HashiCorp to kind of securely keep your private, your key pair in a Vault, if you will, something you can move the name. You got to run then, once you deployed that code into this environment, we give you a single view of your code running and whichever environment you want to look at. And so again, if this is a production environment and you're running across multiple different cloud environments, including private cloud, we give you a single view of that application and the CPU is using across those multiple environments without you having to know exactly which environment it's running on. We give you a lot of details into kind of the actual mesos, in this case is a mesos example of what sort of load and what's busy, what's some of the busy components going on within that cluster, as well as from a data analytics standpoint, we kind of feed in, take this data out of the environment and feed it into a tool that lets you then go in and kind of create your pipeline to look at how the data is flowing and what type of enhancements you want to make to that data. And so you probably, by this point, you're kind of wondering, okay, you've talked about something kind of cool, but what about networking? This goes to networking company and so we've been doing two things in the networking space. We've been working in user space to try to make the actual container networking as fast as physical networking with something called FDIO. We've also been working on policy and kind of making sure that storage and networking security concerns that enterprises have are being addressed with a project called Conti. Both of these are open source projects. The main goal of the networking work that we're doing is to make sure that containers are treated in a way that enterprise network guys would expect them to be treated, right? Again, if you're a developer, you probably don't care about that at all, right? So for the next few minutes, you might just tune out and say, yeah, whatever, la, la, la, I don't care.  And so we've done a lot of work around making sure that we can do multi-casts. We support IPv6 in our containers. We can give you an IP per container or we can basically give you like a service IP. And so you could have lots of containers sitting behind a IP address that's being load balanced by a load balancer. So you kind of have an option of how you want to manage your networking at that point. We also provide service domain name resolution. So your containers actually have a human name that you can read. So if you kind of create an app server, it'll say app server, right? If you want it to be numbered like one to eight, you can number them one through eight, right? So we let you kind of do things you'd expect to do as a deployment of a server into your production environment. We still show you the UUIDs. If you really like managing new UUIDs, we won't make you stop doing that. But we kind of think it's easier to give you a human readable name. So when you see a failure, you can tie that directly to a server that you understand what it's doing. And then the policy piece we feel like is really important because a lot of visibility gets lost as you start going through these different layers of abstraction. And so we want to make sure that we expose everything from the very basic component of a port on that container all the way up to your policy that you define for which traffic can flow between which VLANs in your network. And so to take a look at Conteev a little bit, the idea of Conteev is again, kind of looking at both mostly operational intent. We're working with Congress here in OpenStack to kind of work on application intent a little bit further and kind of make it more application developer-centric. Right now this is more kind of an operational intent mode. It works across whatever orchestration framework you want to use for containers. So it's not tied to only Kubernetes or only Mezos. It's also, the whole goal of Conteev is to sort of provide a framework that lets you extend your physical policies and ACLs that you use in your physical environment to the container world, but also lets you have sort of the cloud native capabilities of scaling up your application and scaling down your application easily. And so we've built into it the concepts of scale and being more elastic in the deployment. It's very scalable at this point. It's about 10 times the scale of what we can do with VMs from a policy standpoint. And it basically leverages whatever underlying infrastructure you have. It doesn't have to be Cisco under the covers. And so I'm gonna try to, this video was giving me a hard time earlier. I'm gonna try to switch over to this screen. You get blank. That's why you don't do live demos. And then it turns out you wish you had done a live demo. So as I kind of bring up this demo, what I'm gonna try to do show is the actual way that Conteev sort of takes the policy that you define and it kind of gives you a nice interface to deploy it into. The phrase is gonna blow up. So it's primarily like the key points of Conteev is it's open source, it's applying policy across network and storage. It uses this kind of a blueprint, is what we call it, but you can call it something else.  You're using sort of the model on the right-hand side which you wanna deploy into and be able to kind of deploy firewall policies that it can be elastic. And so if you look on the, kind of look at the YAML file, it's a very basic file. We have a nice little user interface that is a web-based interface that you can log into. You can kind of see that it's running VXLAN. If you kind of look at a deployment scenario, you wanna deploy this policy into your development environment. It's kind of looking at the processes it shows you have your web environment. You have some apps, web servers running, app servers running, your database running. You can then create a production instance as well. So you now have sort of two environments running, your dev and your production environment. And you can look at the graphical interface and that will kind of show you when you look at your applications, you have your dev group for web app and database. You have policies to find that allow traffic from web to the private network and from database to the private network. You then kind of look at, these are like the dev ones. You also have production ones. And then they ask to kind of scale up. So you saw in a few minutes you'll see a screen that shows the number of services spun up from three to four. And you can basically stop it all and bring it back down and it'll show in a minute the, when it stops it, it shows that all of those application servers we just showed you are gone. So that's pretty much the gist of the demo and the booth downstairs in C11 tonight or more like tomorrow, we can show you kind of run through it actually in live, we have a wired connection down there. So we're gonna have to worry about demos in the booth. So definitely stop by. I can show you both Mantle, shipped and the Conteev stuff in the booth.  So the last thing I wanna kind of cover was then Dwayne kind of mentioned Calico a little bit earlier. And we also have demos of Calico we can show you downstairs as well live. But the idea of Calico was, it's one of the first projects that supported sort of an overlay networking for containers. It supports most of the major platforms and it's kind of like this V router mode. So it's not gonna really, it connects with live network and CNI. So it's pretty good from like an open stack model standpoint with Neutron. It worked really well with what we were trying to do early on before we started kind of doing more with FDIO and Conteev. We plan to still support Calico as well as other type of networking container networking standards because it's as Dwayne mentioned with OCI and with CNCF our goal is to be open and connecting with multiple different projects not just trying to lock you into one Cisco way of doing things. With that I'd like to invite Dwayne back up for any sort of questions you may have. I'll let Dwayne do a summary real quick. Thank you. Good job. So, open stack can make your container deployments easier. You know, projects Kala and Magnum are gonna be key parts of it. As Ken mentioned, the Linux Foundation lots of smart people doing lots of good things. So very excited about what OCI and CNCF are going to do. And also please go down to the Cisco booths to see the live demos as well as some other goodies that are down there as well. And we really appreciate your time and attention. We appreciate you standing, packed in there, standing room only. And I believe we have time for a few questions. Yeah, we'll do the best we can. So we've got a, oh, we've got a mic over there. We've got a mic over here. We'll take a couple of questions and then we'll just have to continue the conversation. Alicia, wherever you are, is gonna start collecting all the raffle cards. So any questions that we can take? I thought your name was Gary, not mine. One question or one thing, if you could put all the cards to the center aisle, that'll be easier for us to pick them up. Thank you. So if you have queues, they've got A's. Wow, you guys just nailed containers and open stack. That's the most. Okay, wait. Mic's up. Leave it to Mike.  How's Cisco going to monetize this and benefit? So, do you wanna start that one? So there's two ways. One is do kind of an open stack support model as you'd expect. The other way is more of a product model. So we will have a kind of like a V block if you work for containers. So those are sort of the two models. We're also gonna keep everything open sourced. And so if you don't want either of those models then we're not gonna force you out of the open source model. And Cisco is a leader in cloud infrastructure, compute storage and networking hardware and Willis software also. So it's different ecosystems. Yes. So these projects you're going to push upstream in open stack? They already are. Are they already there? They're in Linux foundation today, Apache. So, Kola and Magnum are both open stack projects today. So, there's been a little bit of discussion in the last little while about deploying open stack itself as container services and some work done and call on Mezos. Has there any, do you guys have any view in terms of Kubernetes as a deployment tool and you know, how ready is Kubernetes to do something like the Kola deployment workload? Yeah, so from my experience it has, there's two pieces there, right? From a early stages it's ready for like testing, but it's not ready quite for the production grade workloads. Mostly because of the monitoring and some of the health components of it.  So, it's on its way there for sure. And it's moving much faster than I ever thought it would move. It seems like every new release has like a ton of new capabilities, so. Right. Anybody else real quick? Cause one more and then we have to actually make room for the next company coming into the room. How does this interact with ACI at all? So, Conti plugin interacts directly with ACI. Do you create your policy in ACI and if it sees Conti there to deploy directly to Conti? Right. And then with an OpenStack Neutron, so there's ACI plugins, there's group-based policy plugins as well as Nexus Speland-based plugins that include the 9000. All right, well thank you everybody. Thanks everyone.  All right. And I got news for you.  Who wants a snap? You can't have one. Okay, a couple more, a couple more. You gotta mix them up again. There, all these late, all these late cards. Hold on, Dwayne. There we go. All right. All right, that's it. Okay, okay, couple, couple, there's always one. There's always one in the crowd. I think you confused him and said your name was Mike. All right. Go ahead, Ken. I gotta be nice to him, he's my boss. Chezz. Chezz-Chi-Chi from CHT. I'm from the H-T. There we go. I am. All right, congratulations. Congratulations. Congratulations, thank you for coming. Okay, thank you. Thanks everybody for coming to the Cisco Room. We'll see you tonight at the booth crawl starting at six o'clock. And we'll see you tomorrow starting at 10.45 and we'll get the demos up and running. You can see all the good stuff.


So, next is collapse of Bretton Wood system. So, what we discussed is that, in the U.S., the issue was balance of payment and capital flight at that time. This was a reason for you to collapse the Bretton Wood system. Before that, in 1971, especially, to save this system, some efforts were made and the most significant was that countries themselves said that the US balance of payment issue is quite rare for that reasons, it was found in 10 countries in Washington. And they agreed that they devalue the dollar according to the 9 percent. That is, the 35 dollars per ounce gold price was fixed. That was increased from 35 dollars to 38 dollars. And, band of fluctuation, which was just 1 percent at some time, now it has been increased in a better way. That was 2.25 percent on the new central rates. Now, this was the time when Nixon, President Nixon had said a very historical agreement. And, Nixon had promised that we will not devalue dollar in future or we will sustain this rate over a long period of time and all of our problems are solved by just simple this agreement. But, this did not happen. Ultimately, at that time, because all the things had been linked, with gold and dollar, one thing could have been taken, but there, the reserves had issues and the dollar was not very much comfortable in the position, the dollar was not in a comfortable position. And then, it had an inconvertible in terms of gold. So, at that time, the next year, when so many promises were being made, exactly next year, US faced the worst deficit. That was, once again, 9 billion deficit you had. And, once again, a zeroed-up came, that the US currency should be devalued. This time, it was around 10 percent. So, this was a time when things were slipping in the hands of the US. Then, here, in the European Common Market, a term was used. At that time, the European Snake had said, that we float our currencies. Jointly float, again, against dollar. And, in this case, we will operate independently. So, there, you have this floating rate system, floating exchange rate system. From here, suppose, your system was built and applied from here. Remember, this thing was not acceptable for the whole world. And, it did not happen. Basically, in some form, a dollar gold-back system was required. But, this floating exchange rate had to be adopted for the whole world. At the same time, the problem was that the fundamental cause of collapse was balance of payment. But, along with that, what we were discussing at the start, the basic properties of monetary systems, in which we were talking about adjustment, were not able to happen at that time. There, we were talking about devaluations. There, we were talking about liquidity issues. And then, the most important thing was that, the confidence of the US dollar was very low. So, there, your Bretton Wood system was completely collapsed.