The Department of Women's and Delaware makes it a better thing for a better living through chemistry presents the Graphicate of America. Tonight's star, Dennis O'Keefe. Tonight's play, The Saga of Jerry O'Brien. The story of the first American victory at sea. A Jeremiah O'Brien. One of the 30 American O'Briens. A famous plan down east in Maine. As everyone knows, the O'Briens were kings in Ireland long before London Town could boast the tower. As to how we came to the province of Maine, where Sydney and Salmon thought of that long, long ago. This is the story of the O'Briens' finest hour. And it begins and ends his old good story, with a pretty girl. The time and evening in the early spring of 1775. The girls? Well, I'll let her speak for herself. She would indeed. The answer, Jerry O'Brien, I don't still know. I'm nothing your wife. I'm nothing your wife if you father owned all the formula between Boston and Covertine. That would be no harm to ask again. How many terms have I asked you now? Do you think I keep count? No, I do indeed. It's only to both of it, to those Bruno's janky clones that hand me around. Oh, I told the story to no one, Jerry. Not even to my sister. Is that a shame just for them? Oh, no, that's ridiculous. But if I marry you, I'll be starting here in the wilderness for all my life and that's not what I want. Well, that's who you want. Surely no man in Mathias, all of Maine, should give you more. The O'Briens rule here, for we only only trade for a hundred miles. And I'll not marry a sawmill. Not even if it's the only sawmill. Oh, Jerry, I guess the truth. I want to get out of here. I want to see the great world. Boston, New York, London even. London is it. Boston, I could marry for that once in a year when the work is flat. As a matter of fact, my brother rides there now in business for the little bit. London. You in London? Why not? Oh, Peg, I don't know. It's all beyond me. I'm not a big enough man for the likes of you and that's the heart of it. I have my own dreams, yes, but there's very not the grandest you is. Oh, make them grander than I, you can do it. You think so now? Oh, I know it, Jerry. But you're the smartest man in Mathias. You're the strongest too. Yes, I am. The smartest sometimes does. I know. Now I was no-headed all for figures. Money stood still in my fingers like water for this word. If it's a smart man, you watch my brother. Gideon's the one for you. Gideon. Gideon. It is fancy ways and superior ways of saying two things at once, no offense. No, he gets you to London, girl, if anyone can. All your brand's brains went to him. Such as they are. But can he work at the login all day long and then dance the whole night through and work again in the morning? The dancing, yes. The work and no. Well, there you are. Yes, well done, my dear. Now you have me far confused. As it looks to me, there's two things you want and no man can give you both. Gideon's coming, Jerry. We're nothing to see.  I'm tired of all this heart and... Jerry! What? Gideon himself. I'm early from Boston. I've told him all about his big... Well, Jerry and Peg, are the bands to be published then? Can I offer my congratulations? No, don't be silly, man. Why will a great lad run heard of you? Are you so desperately wishing to be home? I am that. That's a new thing, then. I bring news, brother. Great news. That's taken news. The price is lumber, is that it? That may well be, but lumber's not in it. It's a matter of state. Well, tell me, then. Not now. There's news that all the O'Brien's must hear. And we must hear it first before the town itself is torn apart. Well, I will excuse this then, Peggy, because... And Peggy? Peggy, where are you? Your little pigeon has flown away, brother. What a beauty. There are lucky devils. No, I might not. That's all you know about it. Now, what's this great news? It must wait. It calls for the family council. Old Morris must get his teeth into it first. Come on, now. This is more important than pretty Peggy Bates. This is the biggest thing that's happened since Patrick himself set foot in Galway. I don't believe you, Gideon. You will, brother. You will. You must meet now, my father, old Morris O'Brien, who came to the cold wilderness from Ireland and forthest and came to it. And may as he yield bread for his sons and their mothers. The news that Gideon bought was important. And my father knew just how important it was. That night, when the O'Brien's had offered up family prayer. I mean... And, Joseph, I thank you, not to move. Lift up your voice, boy, at the place of God. See what your voice is called. Yes, sir. Now... Now taken into consideration the importance of the occasion, I'd call a meeting. A meeting of the O'Brien men. Oh. Will you not call me to counsel as well, Morris O'Brien? This is a matter for the men, Mary. And only for the men. A matter for men? When they're killing it. Oh, I knew. I knew when Gideon came right in home with the faith all aflame. Mary, this is purely a tip for the Satan by men. All the men I see are my own sons and my husband. Once I sit by the window again and wonder if his sons are alive or dead. But I get to my husband in the old days. It may be. It may be. It may be that it must be. Oh, it can't be. Not here in this new land. But we found peace at last and plenty of no killing. Oh, he's done with killing. Oh, there they are, Mother. There they are. I'm afraid the killings followed us. It's the same old quarrel. Aye, Jeremiah. The same old quarrel. The talent is pursued is even here. Well, can he find us here in the heart of the great forest so far away? Oh, can he? Can he find us here? He can, Mother, and he will. He can indeed, and he will. No, let me state the case, Father, as I'm the eldest. For years now, this thing's been closing in on us, Mother. All the restrictions, all the taxes here. It's been a long time coming, and now it's here. You've all heard the news that a place called Lexington. A witch's name? I don't know where it is. No, do I see it? No, there's a matter, Father. At Lexington, the war has begun. Men have been killed. Oh, and kind. They've taken arms against the English king. And they've won. By heaven, they've won! So giddy and snazzy, I believe, my brother. The question is, what are we in Maine to do? What are we to do? Have no part in this quarrel. Rest quiet. Ask into the battle far away, and there's no concern of ours. Be skinned, Mary.  Our lumber goes to Boston by sea, and our lumber is our life. Surely, the British and Boston will rule the sea, so that we join in the revolt, they can starve us. And they will, unless we drop to our knees and kiss Milord Kippsfoot, once again, as we had to do at home. And what if we resist? They'll harry us on a small slupe of war. They could spare such a one, no doubt, and blockade our harbor here. No lumber going out, no goods from Boston coming in, no food, nothing to eat but what we can raise in the clearing. That's the old, old story. Perhaps it's not so serious, Father. Gideon, what do you mean? Back in Boston, as many are mentioned, planes both ends against the middle. There are those who collaborate with the British and do very well. There's a middle road, and many take it. Gideon, is it your thought that the O'Brien's might wear two faces before the world? I said, but there's many do in Boston Town. And they save their skins and their money bags. I see me six sons about me. Could we do that? Could we bow and scrape on Mundi, and then un-choosey scrape and bow the other way? Could the O'Brien's do that? Jeremiah, not the O'Brien. Could we not? What else do we do?  Shall we starve again and take the whole town's starve in with us? No, because a skip-neck boy is pride. Pride? Pride. Nothing else. Pride. I'm not a sin. And is avarice not a sin? And if we bow our necks, wouldn't it not be for greed that we do it? As between avarice and pride? Why, the saints, I'll let me proud. Well, one thing is certain. The choice is ours, and ours alone. As we go, so main will go for this far part of it. For all their Yankee lives depend on us and on our mill. Very well, then. I'll take a vote in the way of this new country. All those who favor that the O'Brien shall resist the British King in this new war, let them signify by saying aye, as I do call their name. Jeremiah Francis O'Brien. Aye. Indian Patrick O'Brien. Aye. Though it is not the way of the best folk in Boston. John Ignatius O'Brien. Aye. William Vincent O'Brien. Aye. Dennis Franklin O'Brien. Aye. Joseph Adams O'Brien. Gosh, yes. No, no, no, all right, then, if I must, I must. Mary Margaret Poverty O'Brien. Aye. And when your pride's ahead, you're all broken in store.  And I'll mend them if I can. Main by unanimous vote, declared war upon his Britannic Majesty, George III. And after a week of chewing on the news from Lexington, the citizens of Machiais saw a British armed cusset, the Margaretta on the horizon of their bay. And soon the drums of the British Marines rolled through the one space in my little town. For his excellency, Lieutenant James Moore of the Royal Navy, paying attention for his Majesty's officer, Lieutenant James Moore. Hello, subjects of his Majesty. Hello, gentlemen. Hello, Englishmen. You've had news of certain treatable actions in the vicinity of Boston. That's why Command has a gun trained upon your town at this moment. I bring with me a communication from General Gage, commanding all British troops to these provinces. That message will be read to you by Captain Ichabod Jones, your fellow citizen. Those lumber-sloops, unity, and poly carry the produce of this town to Boston. Captain Jones. Unfounded, I told you not to get me up here in front of everybody. Read the proclamation, Captain Jones. Yes, of course I must. Well, then, it goes like this. Do his Majesty's subject at Machiais in the province of Maine. Be it known that the forces of his Majesty have the greatest need of lumber for the building of winter quarters and for use in the fortification of Boston against those traitors lately joined in rebellion against the crown. Dang it, this turn I told you.  Now listen here, you. I've got to read this thing. What it says is, either you ship lumber to Boston on my slooks or else you get no food from Boston. It's lumber for Gage and the British or Machiais Stars.  Captain Jones, we need that proclamation. Dang you, I will. They know what it says. Then I'm taking a lump in. Turn up. Exalt. Exalt the fence. Down the road. No, Peggy. Which way will it go? Sure, who knows. Half the town wants to give in, half wants to fight.  No father has done his best. He's been talking all day until his voice itself has gone with the wind. Your father is an old man. He talks in a way strange to most of us. We need a younger voice. Mine, Peggy? Your own. My love. He's never called me that before. No, and I'll never call you that again. Unless you act. Well, but what can be done? The Margaret is guns command the town. And Captain Jones' two lumber slooks lie at the wharf. The parlay and the unity. Say, now, we can take the two slooks and end the whole argyl-poggle for a while. You could. If you had the heart for it. Oh, you did. Do you think I've not? Well, I've wandered. Then wonder no more, my love. We'll move tonight. We return to our cavalcade play, the saga of Jerry O'Brien starring Dennis O'Keefe. We were committed to action after all the talk.  And there we were. There was the Margaretha house in the bay, broadside to the town, with four three-pounders and fourteen silver guns, all trained on the homes we built out of the wilderness. The men of Machias looked up to me and put the O'Brien clan for help. And there was only one answer. Now listen to me. Listen here. We must use the two lumber slooks to capture the Margaretha. No, no, no, no, no, no, no. Silence! Silence! You fools! You have one gunner. Long years ago I thought of taking a Louisburg against the French. And yarn will knight as a wild gun at home. I can mount it in the Unity's bow. It's small to bear the name of a cannon, but will serve as well-aimed as mine. You heard my father speak. I say we can do it. We all have arms at home. All right. All right, my word to you is this.  Go get them. Now! 52, 53, 54, 55. 55 men here on the wall. And their lives, brother. In your charge. Do you think I don't know that? Have you counted the muskets, Gideon? Aye, captain. We have 20. Counting the fouling pieces. 20 guns for 55 men. How many pitchforks? 13. Commander. How many timber axes? 12. Fine axes or comadones. I'll take one of those in place of a sword. And what are the powders? Powders? Aye, there's a rough, my dear admiral. We have no powder at all to load the wall gun. No powder? And only the wall gun shot could pierce Gideon's vessel's side. True, Wheaton said he had 40 pounds hidden in his cellar at all. Where is it? Joseph, he clean forgot it. He was in such a horrid hurry not to miss the great sea battle. Oh, Gosset. By all this kind of war, Jerry, we're all amateurs here. Jerry, what's the meaning of this? What does that mean? It's my little pigeon, brother. I don't believe it. Tell you. And her sister, Joe Wheaton's wife. Jerry, Jerry, we're coming. Tell you, tell you, what's the meaning of this? You'll not come aboard this, Gideon. Can you see this? It's the powder. The powder, my rattle-brained brother, and I forgot to bring it. My sister and I have dragged this 40-pound bag all the way from Swanson River. Oh, pecky children, Gosset. Oh, the war is on again. Well, you'd better get ahead with it, Admiral. The enemy might wake up. Gideon, are you with me or against me? Do you need to ask? I think I do. The things you say. My way of saying it. Would you have me pretend? This is the fool's errand we're on. And it can end only one way in failure and death. But I'll be with you, Jerry. However it ends. Oh, I'm sorry, Gideon. This is no time for being sorry. Yonde is your Navy, Admiral. Half a hundred fools. All right, talk to them. I will. I will at that. Men, men, gather round here. Gather round and listen to me. Now, I'll take the unity out. Then, foster it, we'll take the Pali. And what Massachusetts farmers can do on land against the British, Maine lumbermen can do at sea. We'll all sail it here. We've had to be. And now we'll sail against the enemies of liberty. Take your stations. What happened in the next hour? I've not wished to tell with my own lips, for I'm a modest man. Though they do say I summoned the strength of ten to my own right arm that day. But let others tell the story as is only proper. Lift me ashore. Me, Morris O'Brien.  Too old, 75. And they gave the wall gone to will-night to trade, and him shivering in a boat for a while. But I have a sail against the Englishmen, and I watched them. I watched the Britisher make sail against the room. I watched the Lubbers mishandler in the quarter and win. Soar boom, swung round and snapped clean off. Listen to O'Brien. You just see that now. The British has lost their mate. She's helpless. She can't move now. Look at her. I can see her. I can see all 18 cannons. Titan of my son. A ram with axes and pitchforks on it. Then faster, sort of the ground, she's on a moot bank. But the unity goes forward. The unity goes forward alone.  I look no more. I look no more. I saw the old woman close your eyes, stumble back into the crowd and fall in a faint. I wanted to help her, but I could not take my eyes from the smoking harbors. And the man I loved. I saw the unity close in and grapple. I saw my very leap aboard the enemy's loop, his daydacks swinging around his head. I saw the British commander fall dead on the quarter deck. I saw his crew re-stamble for cover below against the flailing axes and the pitchforks of Matthias' men. And I saw my Jerry leap to the rail of the quarter deck and with one great blow of his shining axe, cut down the British entity and end the battle. What I mean was I thought she saw mighty quiet here in the orchard. Isn't the moonlight lovely? Oh yes, yes it is. I mean yes, yes it is.  Oh it's as little as I need it for this scratch I got behind me here. I wish you'd let me take it off. After all the trouble I took to fix it just so night like the heroes in the picture books, you'll wear it the next three days, maybe longer. You say so Peggy. And one must you be done cast after such a day. I'm thinking of that Peggy, I can't help it. Oh but it's been a great day for the O'Brien's and for all of me. I suppose so. It's a great battle but we can't each victory. We've got nothing now from Boston and we've got nothing here to last beyond the fall. You've got three fine suits Jerry. The unity, the Pali, the Margarita. All prizes of war. Can we eat the boats then when the wizard comes? No, but you can fill the boats with lumber and sail them to New York and bring them back chock-a-blast full of flour and meat. Why Peggy, so we could. Yes, so you could. I'm with you. Peggy. To settle. I've always wanted to see the great world. But Peggy, you can't. What would people say to you? They say not a word, not a single word. Not if we are well and truly married first. So Peggy got what she wanted, to see the great world. For it in the end, I took it to London itself. And I got what I wanted, wherever close by Peggy's side, through all the days of our years. There's more to it than that, I think. We poor folk of Mechios, it humbled the might of tyranny's power on the Western Ocean. We had won the new country's first victory offshore. Though we quarreled amongst ourselves, and even the O'Brien's were not of one mind at all time, we drew together and fought together when the need was most great. Today, in your own time, there's an American ship of war that bears the name O'Brien in our honor. Wherever she rides, salute her now, and draw together, as we did then. Next to them is O'Brien from the Cavalcade players. For tonight's story, the saga of Jerry O'Brien. Tonight's Dupont Cavalcade was written by George H. Spockner and was based on the article, The O'Brien's Go to Sea, by Ernest Dupuis. Original music was composed by Arden Cornwell, conducted by Donald Boris. The program was directed by John Zoller. With our star, Dennis O'Keefe, you heard Yuna O'Connor as Mrs. O'Brien, Jean Gillespie as Peggy, James O'Neill as Morris, Scott Scotsworth as Gideon, and Parker Fennelly as Captain Jones. Dennis O'Keefe can currently be seen starring in the Metro-Golden mayor picture, everything I have is yours. And Mrs. Sy Harris reminding you to be with us next week when the Dupont Cavalcade will present Ready on the Right, our star Jackie Cooper. Ladies and gentlemen, for 18 years, the Dupont Cavalcade of America has brought to millions of radio listeners the true stories of our American heritage and the achievements of the men and women who gave us our American heritage. Now, the Dupont Company is bringing you Cavalcade on television. Watch the TV listings in your newspaper for Cavalcade of America TV in your locality. The Dupont Cavalcade of America came to you tonight from the Balasco Theater in New York City and is sponsored by the Dupont Company of Wilmington, Delaware. Makers of better things for better living. Go chemistry.


What's up everybody jason for jazby's case raise calm 2022 immaculate baseball eight box picker team number four rnb Just sold out and again guys This is for the Orioles blue jays nationals and marlins You get a piece of these four teams in picture number four and the way the hits are distributed if there are any hits for these teams We'll be ran a number block style everybody's around a number from zero 39 We go by the first number on the left side of the show number dash. There's your examples remember any our redemptions do go to spot zero Here's a dice roller here's a customer names and the numbers so let's click dice roll and we have a two and a three five times Good luck one two three four five So five times two three five Rob down a Martin So there's that two three five times on the numbers one two three four and five five Five seven down to four. That's a five five So Rob you have seven as well as nine rex you have to rob with eight can bond You have five Andrew with six Martin any no redemptions can bond with three Martin with one and four. So there you go guys So come in up next in a separate video in a few minutes is immaculate picker team number four guys. Good luck


The present study found that adding air to dry dog food can help reduce hunger and consumption of food, leading to better owner compliance when it comes to weight management. This is because the addition of air to the food increases its volume, making it take longer to eat and thus reducing hunger. Additionally, this method of weight management does not require any changes to the macronutrients of the food, meaning that owners do not need to worry about changing their pet's diet. This article was authored by Samuel Serizair, Anthony Pizzagalli, Lucy Le Clegg, and others.


All right. Welcome, everyone. Today, for this session, we're going to talk about one of my favorite topics, orchestration. And specifically about the role orchestration plays in my use cases, which are, my name is Toby Ford. I come from AT&T. I work on the NFV SDN space. And so the use cases that I care about are somewhat complicated, often span many data centers, many central offices, and in nowadays is extending out to the edge to the fog realm of UCPE and IoT and base stations for the RAN. And I need to orchestrate. I need to find a way to instantiate our, quote, unquote, virtual network functions and put them in dispersed across all of these facilities. And then based on demand or a lack of demand, I can scale up or scale down the resources. And I can adjust. And then even beyond the simple single use case, I can then eventually have multiple use cases with multiple tenants. And then, you know, bin pack the resources I have. Try to get the goal that we have, which is essentially full asset utilization. But at the center part of this story is orchestration. And you may have heard the term MANO. MANO is a term that comes from the Etsy ISG's work on NFV. It's intended to represent the part of the puzzle that is, as I described, the part that helps us to manage and orchestrate the virtual network functions. So today I have a group of folks that I think will do a good job at representing this problem space. And then an example of the sort of what I think of as diversity and innovation that's happened around orchestration. There's been many attempts at solving this problem, not just within the NFV or SDN space, but also in general in IT. There's been many, many times where we've worked on this concept of orchestrating many maybe automatic and manual tasks, different types of resources, and put them together to solve something. Been a long history that way in the IT realm. So I think I've tried to put together a panel that represented the diversity, both of the IT realm and also of the telco realm, and specifically around two things. One is about the projects that are happening that are trying to solve for the MANO problem. So AT&T has its own way of solving for the MANO problem. Other folks like China Mobile and a number of entities we'll talk about are working to create a new thing called OpenO, which is intended to solve this problem. And then we also have representation from the Etsy community and a new entity that's created around that called Open Source MANO. And so today, let me call up to the stage three of my guests. So first, I think attempting to represent the traditional IT space, and then also the solving for my problems, Chris Wright from Red Hat. The steps are on this side. Thank you. Or even better. Thank you, Chris. Thank you. And then second up, we'll have Diego Lopez from Telefonica representing the Open Source MANO project. Thank you. I applaud your agility there. And then last but not least, Ling Li from China Mobile. Now, he has joined me as well as being a Super User Award winner. Thank you, Ling Li. All right. So first, my question to this group, this esteemed group is I want to first have each one of them go through and introduce themselves and what they work on. So starting with Chris. Hello. Good afternoon. I barely made it here. I was lost in the shuffle of trying to find this particular room. So my name is Chris Wright. I am vice president and chief technologist at Red Hat. I focus on our technology strategy and looking at where the industry is moving and where open source innovation is solving new interesting problems across the industry. OK. Just one second while I put this in silence. That's true.  No, I was trying to spare you of the music I'm buying. Diego Lopez, I work for Telefonica. My position formerly is called head of technology exploration. I joined Telefonica five years ago. Since then, we started working in aspects related with SDN and NFE there. And I am part of the large team that is, among other things, working in an open source manner. Hello, everyone. My name is Ling Li. I work for China Mobile. I'm a current member of the Novonet Project, which strives the company's SDN and NV strategy. And I've been actively participated in some of the open source community around this idea, including OPN3 and OpenO. And very proud to be serving on the board of OPN3 and also the TSC of OpenO representing China Mobile. Thank you, everybody. So let's start out with a simple one. Let's pretend I know nothing about orchestration. Could you tell me what is your definition of orchestration? I think of orchestration in terms of, well, first of all, in the software context.  But in a software context, I think of it in terms of taking multiple API driven and taking multiple steps together in a concerted effort to produce a result. And typically, I look at that as, for example, creating a service that's a combination of a collection of independent pieces. And how do you launch that? How do you manage that? How do you update that? So orchestration, collection of things, done together. APIs under the hood, I think, are really important. No, exactly. I mean, orchestration in the musical terms is precisely make the set of different individual instruments to sound as a joint instrument. This is what they call orchestration. So you take a piece of music and you make that the whole orchestra is able to play it. The point here, and when it comes to the particular case of network service provisioning, the key here is that we have to live with something that in some cases is complicated, that is install-based. There is this old joke about that the creation would have been much longer than seven days. If God has to deal with install-based there. So and this is precisely one of the key things here when talking about orchestration on network services is that we have to deal with the deployments of network functions, of virtualized network functions, in an environment in which there are many other network functions that are not virtualized. And they need to work together because at the end, we need to orchestrate not only the virtualized part, not only the parts that is based in a cloud infrastructure, but we have to make them work with the other ones that are not part of it. And this implies an additional challenges in orchestration that probably in other environments are not so high. Makes sense. Certainly the brownfield state that we have to live with and the greenfield have to go live in coexistence and that's what the orchestration has to cover. Ling Li? Yes, to my understanding in a narrow view, I think orchestration means to just like Chris mentioned, putting some of the pieces together. Usually we would call it as resource or components and then we came up and connect them and to come up with a deliverable like a service which can be consumed by another level of consumer. So I think in this interpretation, I think actually we have orchestration in different layers. We can have orchestration in the VM layer which could compose to be an application. And we can also move a lever up and by combining different application or VNF together, we can come up with a network service as defined by the CNP architecture. And then still a level up, we can come up with, you know, combine different network service which are usually consumed by the operator and then put them together with some of the product definition and also business logic. We can come up with an end-to-end service that can be consumed by our end user, for example our subscribers. So at these different layers, I see different interpretation of orchestration. And to me that is, that is, you know, like happens in the design time. And also in the broad view, I think at each different layer of orchestration, we can also incorporate the concept of management. So what I have been talking about is like we came up with a blueprint which came up, you know, can be composed of different components and with connections together. And with that blueprint, we can actually initiate different services instances. And we can also, you know, there's also key to manage that different instances all through this life cycle. And to us, I think, you know, we believe that that is also an integral part of orchestration. Great. All right, so it sounds like we have a consistent definition of what orchestration is. And I think we touched on a few of the areas that I wanted to get into. And Ling Li, I think, did a good job at mentioning some of the key dimensions. So it's more than just orchestrating or instantiating a new thing or a new service. It's also the aspect of designing that service ahead of time and orchestrating that activity to prepare for the time at its production time or real time to actually do that. So we've gotten into a few of the areas and it was good also about the management part of it. Because I think the life cycle maintaining something, it's not just placing it somewhere and making it work to start with or implementing it, but it's also living with it over the long term, scaling it up and down, making sure it runs, re-instantiating if it fails, and then getting rid of it when you're done with it or when it's using or not using the resources it should be. So I think we touched on a lot of the aspects that I think fall into what is the definition of Mano. So I'd like Diego specifically to talk about this subject of what is Mano and where did it come from? Mano means hand in Spanish, you know? Oh yeah. So this is the first thing and when talking about management and orchestration by chance, the two people that were leading the discussion during these moments were Spanish. So we decided to use it and to make the community learn a little bit of the most civilized language in the world, by the way. So anyway, no, and precisely the name came handy, if you'll allow me the poem, because it was precisely about what you do with the remote hands in the environment of a data center or whatever. It's precisely managing and orchestrating things around when you ask someone to be changing things and reconnecting and enacting on your behalf. So the idea is that it was precisely this. So when we coined the term Mano, what we wanted to be very clear, and this is something that is important to understand about that because that influences somehow some decisions that have been taken, at least in our case afterwards, is precisely what I mentioned before about install based. What is very important is that we tried to, from the very beginning, to isolate the aspects that were related to the management and orchestration of the virtualized part, of the part that were based on the cloud infrastructure, to make it isolated from the rest, from the general semantics of a network function or how you control, how you apply SDN, or how you apply network management or whatever. Essentially, because we were aware that the reality in many years to come is going to be hybrid networks. And we will have a combination of, I don't know, optical or radio equipment that will be based on hardware, managing a more or less traditional way, with something that will be much more elastic, much more adaptive in the sense that it will be changed and it will be suitable for cloud operations while the other parts not. So the idea is that you have a separated management and orchestration that is focused on the cloud aspects and not focused on anything else just because to a general network management system would look like another network component. A network component is a little bit particular that is much more subject to change but not necessarily different so you can make a consistent management of the, I mean a consistent network management with the MANO interfaces that are provided by the separate cloud management and orchestration. Awesome, so I have two questions. First, for Chris, how is MANO, as Diego described it, how is that different than what you were doing before in the IT space or specifically with your products like managed IQ? I think there's maybe a couple of key differences. First of all, the notion that you have a complex task that's composed of a set of discrete independent tasks like launch an aggregate application is not new but it's maybe defined differently and part of that definition that's different is it's the network so we're building up the network, we're building connectivity and so many of the traditional IT tasks are focused on things like launching applications. The application is more business logic and less about defining the actual connectivity and infrastructure where in the service provider space the connectivity and that infrastructure is the business. So from our tooling point of view we've really focused on things like can you launch an application which is an aggregate of a set of different components on differing cloud infrastructures or differing virtualization platforms and actually something that's very interesting to the service provider space as well where we wanna make sure that we can provide network functions across a disparate set of VIMS in the Etsy, NFE, Vernacular or a different set of infrastructures. So I think on the one hand we see them as really different applications, business logic, databases, higher level languages, distinct from the network itself but the concept, an application being an aggregation of services like a microservices based platform or our application translates really directly to individual network functions composed to provide a network service. So it's sort of similar concepts applied in a different space. All right. So Ling Ling, what is your thought about so how does your effort around OpenO how does that cover what we've talked about already? How does that cover the MANO space? Yes, the MANO. Or even begin before that, what is OpenO? Good question. I think just as I stated I think orchestration has the integrity part of management so management and orchestration I think that is, you know, it has to be, you know a part of a meaningful solution for us. And as for entity's definition for MANO I think it fits well with the network service layer orchestration and the management and it is specifically targeted at the NV orchestration and within, you know, like data center and cloud. And for us as OpenO I think there's a unique feature that we see actually we have to deliver the solution from the end-to-end orchestration layer which means that we have to, in addition to NV orchestration we have also to do SDN orchestration which means that we have to also provide connectivity service in addition to NV services with network service composed of VNFs reciting in the cloud, also connect different data centers and also, you know, provide the last mile connectivity to the end-to-users device to our data center and cloud. So that is actually two parts of orchestration, SDN orchestration which manage the connectivity service orchestration and in addition to NV orchestration. All right, so that makes sense but back to also where did OpenO come from? Is it intended just to solve that problem or is it gonna extend to more things or what is the, how does OpenO play in this space? I think it has a two layer orchestration model. At the top layer, this is a global service orchestrator which deals with the end-to-end service orchestration that is consumer oriented and which is actually the service, end-to-end service is composed of two types of service, network service is one of them and connectivity services is another type and they're orchestrated respectfully by LBO and SDN. So I think our LBO part is quite aligned with the SDN architecture, the minor part, excuse me and for the SDN part, I think it's quite aligned with MAPS definition for LSO and we tried to combine that to provide the end-to-end orchestration capability and we also work with multiple WIMPs and multiple within managers to increase our capability in outsourcing other open source components and make it a whole solution. All right, thank you. Diego, and then can you help explain how, where did Open Source Mano come from and how does it cover this space, other than the name? Open Source Mano comes from some orchestration components that we have some time ago in, while we started as something that we called our NFE reference lab two years, three years ago in which our idea was precisely to, well, to get some insight on what the rest of the industry was doing around NFE and with the different virtual machines, the different virtualization platforms, the different choices for orchestrating the resources, the cloud resources, et cetera, on the one hand and on the second hand to, well, to bring some awareness inside the company, Telefonica has a size, you know, and it's from time to time difficult to reach all the parts and the idea was to have a clear showcase for what we were doing. And one of the things that was clear from the beginning was we needed an orchestration platform. We started to play with it and from a certain moment and in conversations with some people that were working with us as well, we thought that it was mature enough to try to attempt to make them Open Source and to make it a full-fledged Open Source project, not only delivering as Open Source, but looking for additional collaboration and cooperation and people coming from different other companies, other institutions bringing their inputs and making the whole thing evolve. And we started like that, we started very, let's say, modest and small and we have ground in that direction and I think that right now we have released what is actually the third release but it's called Release One. Because first we started with a seed release that was just putting all pieces together. Second was Release Zero, that was the first one that has had code built in purpose for this project. And that Release One is the one we are, is able to demonstrate where we want to head and now it has something that is very, very close. We'll say the closest you can get in an Open Source project to production level, so forth. We are very, very glad of it. Mostly OSM is focusing right now on what I said before on the orchestration of the MANO problem, on the orchestration of network functions inside the network environment. It's not trying to, it's not addressing the rest of the space. And it's pure MANO though, it's not, I mean, it follows or tries to solve the problems around MANO but it's not following 100%. The current architecture, I mean, I don't know if many of you have seen this diagram coming from Etsy about the MANO stack with the three pieces, the NFEO, the VNF and the VIM, doesn't follow 100% that, it doesn't provide exactly those interfaces but the behavior is precisely of a full MANO stack. And it's concentrated on that and that implies that in principle, I don't see why not it could be able to work, for example, with OpenO in the future, able to integrate with ECOMP, able to work with the... Manage IQ. Sorry. So, because at the end is a piece that is very much focused on solving the problem, not trying to go beyond that and we are aware that there will be other solutions that will be able to be part of the whole process. That makes sense. So, one part of the Diego brought up is that AT&T has made a thing called ECOMP which is Enhanced Control Orchestration Management and Policy, so the own part of it is similar to MANO, but we've tried to do more than that and we're addressing a larger problem of the OSS space from telcos, specifically around policy enforcement across the whole system, some of the dynamics of service definition, which especially about VNF onboarding and then trying to work with VNFs to sort of create a template for how they show up. So there's a few parts that I think are meta to the MANO part of it, but at its core, it also has a piece that does this management and orchestration function. So today, what we're faced with is, at least between a subset of us, is a lot of redundant effort and so we're currently having discussions about how to bring it all together, but given that we're at the OpenStack Summit, I did wanna ask Chris a question specifically about, well, given that we're here, how can OpenStack help? Some of it obviously has a few projects that could help this way, whether it's Morano or Heat or Mistral or Tacker or Congress. How can OpenStack help to maybe deal with this problem? So I think the first question is, is that the right place to do it? And the second question is, what are the specific projects in OpenStack that are helpful? And if you look across a lot of these different efforts, we're actually using some of these components that you mentioned. So things like Heat are pretty consistently used to do basic definition of an application and potentially some scaling parameters around the application. We also have looked at using a project called Tacker to help essentially expose that onboarding portion and give definition to, you're bringing something into a platform. You need to tell the platform what it's SLA, the end result of the SLA is going to require a certain set of resources from the underlying infrastructure. And so we've got something that says, hey, how do you provide a VNF with a descriptor and then deploy that onto an OpenStack platform? And Tacker's trying to help there, especially when you are doing multi, the OpenO project has described there's potentially a difference between the NFV orchestration and the SDN orchestration. So how do you reach out to an SDN controller and define a service function chain that's going to be associated with the independent network functions that build up this composite service? So you've got workflow orchestration in OpenStack. And I think one of the questions for the service provider community is how much do you expect to run your network functions across multiple different platforms? And if you're running across a lot of different platforms, then building the entire stack, completely an OpenStack is only going to solve one problem. And so I think what we're seeing is interest in having cross cloud compatibility. So we want to leverage the primitives of OpenStack without building the entire stack as an OpenStack project. That's how it looks to me. Makes sense. Diego or Lingli, do you have other commentary about the OpenStack part? No, precisely. First of all, when you mentioned this of having the primitives of OpenStack without the whole OpenStack deployment, there's something that we said some time ago that we call OpenVim, which is a sort of a streamlined OpenStack. Something that you can, is a much tinier than the normal OpenStack deployment thinking, precisely of the kind of deployment you would do in a small central office, of the kind of deployment you would do for ahead of managing different radio stations. This is something that, well, and this is something that it could be interesting to explore how we can combine it, because, formally, it's not an OpenStack project, because, well, for us, we are not that many, we are a small group of people working in development, so we have to be, well, we are playing a little bit, to some extent, we are playing a startup inside the platform. We are very much focused on trying to make things happen, but precisely, we're pushing things in a community of this size, that's for you to know. Not sure if you're aware, but pushing certain things in this community is complicated simply because of the size of the community and there's so many forces that are around pushing and pulling in different directions. And, but this is precisely something that we have learned that it would be very interesting at least for our environment, and I guess in other environments that could benefit from OpenStack interfaces without the need of the whole complexity of a full-fledged OpenStack stack. First, and this is one of the main goals for us OpenStack is essential as precisely as a reference, at the reference that we are using for the platforms that we are mandating in our initial pilots and deployments, and precisely it's a way of making this reference and making clear for us that we can move from one provider to another provider by moving our code, or the code of the third parties that are collaborating with us. And well, something that is very important as well is that the knowledge that we collect is reusable. It is extremely important when you have people trained, working with that, because this obsession with vendor locking very often is not only about the compatibility, because then it's a matter of price. If you pay enough money, you will have something different. At the end, it's a matter of knowledge. You simply don't know what you can do with the new stuff. Now it's something that brings you a certain stability in your knowledge. You know in which direction you have to look, and this is a very important one. Sure, so Langley, how does OpenO work with OpenStack today, and are you reusing components that way? Actually, we see OpenStack as the de facto solution for a component for WIM, Virtual Infrastructure Manager. And we are also aware that there are some of the projects in OpenStack community that might have overlap with some of the components within the OpenO community. And actually, I think we are open. We're actually going to put it. We're open to any of the open source efforts that could complement and also make a part of OpenO community. But we actually do our choice to try to keep aligned with other community like OpenStack. I think there are some of the principles. The first one is that we try to push the alignment between the different interfaces, especially data modeling. So if we can keep aligned within different community regarding these two aspects, even though we are not outsourcing to each other, we can become incorporeatable and be replaceable with different components. And that's to me the most appealing feature for open source communities. And the second principle would be, especially, how can I put it, the ease of use. So some of the components, for example, as you mentioned, Mr. Actually, we have our own like version of Mr. in OpenO. Why we are not using that is because of the ease of usability. We see that there is a user-friendly GUI would be a very appealing feature, especially at the very top layer of orchestration, which the operator stuff would be using to define the service template. So without that feature, there would be some comparison and made our choice in SQL. But that is not to say that we are closed the doors for other components and other efforts in other communities. And as long as we are incorporeable, we can join together. And I think it's slipped in my mind. I think I have a third principle, which one is that? Fun, having fun. It's much more fun to have open source. Oh, yes. Tacker and service function chaining. I would like to mention that actually we see Tacker as a generic VNF manager because they all operate at different layers of orchestration. And we see heat is operating at the VM layer building up the application. And Tacker or Juju operating at application layer and it can use heat or whatever interface that opens Tacker lines or other wind provides. And actually, we have been talking with Tacker guys. And we welcome their contribution to our community so that we can also have Tacker as our generic VNF manager as well. And there is another form of collaboration, specifically to SFC. We were actually using the networking SFC project, which is resigning OpenStack. Their defined API is our interface between orchestrator and SFC controller. So in that case, we are actually interoperable with OpenStack some of these solutions. And that's it. All right, thank you. Yeah, so I think the idea I think across the group, we've seen a number of ideas about how to perhaps consolidate efforts and then also to enter work and then find a way to innovate while continuing to innovate, to integrate while continuing to innovate. So yeah, I think this was a good discussion. So right now, I'd like to actually offer up the microphones on the sides here. If anyone would like to ask any kind of questions, feel free to stand up to that microphone. And we'll talk about whatever. Looking forward to that gentleman's question. Ian? Hey, yes. You know me. I'm here to cause trouble. So I will ask one question. To start with your analogy that you came up with originally, that you're talking about a conductor standing in front of an orchestrator and ensuring that everybody works as a whole to accomplish a given task. Then a conductor's main role in leading an orchestra is not the one in front of an audience, but the one far before then when he's trying to get everybody to work to one end and to fix the problems that he's seeing. So in the NFE world, when you're doing orchestration, then I would say one topic that doesn't seem to get covered well is the idea of repairing problems. You're running on a cloud. You will have inevitably in a large cloud with lots of servers. You will have these problems. You will lose virtual machines. How do you see your orchestration solutions solving the repair problem as opposed to simply the deployment problem? Yeah, so let me talk about one part of it with regard to ECOMP. I mean, this is one central difference or central thing that we're focused on within ECOMP. It may not be a difference, but it's about the closed loop control. And then setting up these not only around service management and problem management, incident management, but also around the whole service definition. But creating this closed loop where I'm taking in analytics, I'm taking in feedback from the system or from customers, and then I'm using that information, processing it maybe through an ML system of some kind, and then acting on it and using the orchestration as a way of getting back to the right state. So that closed loop concept is an integral part of our ECOMP work. I mean, I think at a cross-industry level, it's still early. So we're focused on the building blocks. But if you look at everybody's work, there tends to be some notion of event-based processing coming out of the infrastructure or the actual network functions themselves and then actions that you take. And that could be as simple as scale up because you've got some peak. It could be more complex. Like there's been some fault that is in hardware that's percolating through the system. You need to redeploy. But I think in all the cases, an event stream, some level of analytics against the event stream and some remediation is core to the end result that we're striving for. But if you can't describe the function and you can't launch it onto the infrastructure, then you don't have that problem yet. And I think we're still mostly talking about just getting things launched. No, frankly, we have one project running and a couple of proposals launched recently precisely on this idea of repairing, in general, about resiliency, including security and including the ability of identifying and trying to alleviate security problems, not only failures, but ill-intentioned attacks to the infrastructure. As Chris said, it's still early. I mean, it's not that we can claim that it is an integral part of the orchestration suite, but this is something that we are aware of. Last OPNV meeting, it was precisely showing some results. We are talking with the Open Daylight people as well in trying to bring the results we have, trying to make them an integral part of their projects and so have it as, well, part of the normal toolbox that we'll be using in hopefully a couple of years to build networks. So if I may add, I think a high availability or fair offer is one of the key features of telecom services and we traditionally deal with the problem with the, you know, a combination solution from a single vendor which provides hardware and software altogether. And so in every environment, you know, that blocks is actually break down into different layers and to deliver, you know, comparable high availability to traditional like a black box, I think it needs collaboration between different layers and especially I think how we deal with each of the availability issues of a specific VNF, it actually depends on what it requires at different layers. For example, some of the VNFs, they are typically IT application and they are very comfortable of relying on the infrastructure to do the fair over and they are not so sensitive to, you know, to service continuity requirements. In that case, I think it would, you know, depends on the infrastructure and the cloud infrastructure to provide them with some of the fair over mechanisms. For example, migration or, you know, VM reboot and for some of the tactical features of VNFs, for example, our current network VNFs, actually there are very strict requirements regarding their service continuity and we could get sued by, you know, by our government or subscriber for blocking that service for a permanently short time frame. So in that case, we definitely need, you know, collaboration between different layers and what our orchestration part do will be to make sure that for each of the specific VNFs, their requirements, their policy regarding fair over to be clearly specified in the metadata and conveyed to, you know, the specific policy enforcement entities. For example, for the IT application, that would be the infrastructure and for some of the tactical VNFs, there would be a collaboration between different layers. And I think there's also another part to the story is the monetary part. So in terms of, you know, policies or something that you might take proactive action to actually avoid fair over, we have to monitor other status and resource consumptions, something like that and all the alarms from different components and VNFs. So orchestration also has to play this key role at state alarm monitoring to, you know, to complement a total solution. That is my take on this problem. All right, thank you. Next question. Hi there. How would you compare the state of play in the NFE and open stack orchestration space with what's becoming available in the container space with Kubernetes and Swarov and Esosphere? I think that's a very good question. Do you want to take that one? So the one level of orchestration is just where you place the workload, how you launch a workload. And so some of that's just almost more about scheduling. And so from one perspective, you've got Nova doing scheduling of VMs, you've got something like Kubernetes doing scheduling of containers. And so the question is more about what is your application running? Is it containerized or is it in a VM? You also have some interesting definitions in the application orchestration layers. So like Kubernetes or Swarm, where the focus is actually building that aggregate application out of a set of services, which in the networking world would translate to an aggregate set of functions composing to a service. And there there's been work that we need to be interoperable with from an industry point of view so that when you define a service, a network service, we need to be able to deploy that on to, in my opinion, onto a application orchestration fabric like Kubernetes in a way that makes sense. So we don't want to completely redefine the world over here in the service provider space, only to find that when you go to an application orchestration tool like Kubernetes, it doesn't fit towards redefining, we've completely rebuilt a bunch of infrastructure. And I think the real question is how much of the network is going to reside in bare metal, in VMs and in containers. And my personal opinion is that a containerized future in the network is inevitable and it doesn't necessarily mean that it will all be there. And so we are thinking a lot. I think I know at Red Hat and across the industry, we're thinking a lot about how we can bring these things together. And one of the things that we were trying to demonstrate specifically with Manage IQ is all of these problems are similar across the different industries. And so you do service definition, you create a service catalog, you launch a service, you monitor to the service, you scale the service, you may want to launch it across different infrastructures and part of what we were trying to demonstrate is you could build a comprehensive network service out of some functionality sitting in VMs, in OpenStack, and some functionality actually sitting in containers on AWS, which is probably the most extreme version of all the differences you might find in a service provider's infrastructure provided in a single network service. So containers, very important part of the future, making sure what we're doing now is compatible with the orchestration done and application orchestration tools, very important. Yeah, I think one point to add to that because we have to move on, but I think containers actually provides an opportunity to simplify, to make the orchestration easier on us because the things that we were doing before can be done already in the template or in the Docker format that's there. So there's, I think the enormous opportunity to help us to simplify. One last question from Beth, because I'm always over. So my question is the proliferation of orchestrators has started. So I'd like the panel's comments on how to deal with that issue. I know we are personally, I personally am already dealing with that. So orchestrators are in the cloud, they're out at the edge, they're all over the place and they need to interact with each other. So. Yeah, do you think we want to do that one? I don't know. I'm not sure if you're referring to the fact that we're using the time of an orchestrator or all over the place, or. Oh. Just that we have so many everywhere. Yeah, it's like standards. There's great, we have so many of them. I mean, probably, probably it's because everyone at each level wants to feel that it's in charge of the orchestra that they are the conductor and not one of the players. This is something that is, I would say it's human in that sense. As long as what you're talking about is about allocating resources according to a set definition of a model of what you want to achieve, you have an orchestrator and we have inside the HCNV group we have been discussing precisely about different orchestration layers. You can call it orchestrator or you can call it manager or you can call it policy enforcer, whatever, but at the end is that you have different layers of concern that normally are associated very much with business models. I mean, if I am providing infrastructure, I mean, providing infrastructure up to the operating system, I will have an infrastructure orchestrator because it's my concern. If I am consuming that and I'm deploying BNFs functions I will have a function orchestrator because it's my concern. And if I am providing services I will have my service orchestrator. And even if I am a customer I will be thinking about my business orchestrator or whatever. I don't see anything wrong with that as long as it is clear that there is no, I mean, there is not a hierarchy but there's a set of relationships among different objects. This is one thing. Second thing that probably is about that there are many offerings right now in open source and in proprietary fields. It's natural as well because we are starting from different, I would say different goals and different analysis of the current reality. And as I said before, most of the force I'm aware of should be able to work and to interpret as long as as Langley said before they are using compatible models and they're using not even not necessarily compatible interfaces but they are based on compatible data models because an interface is something that is easy to build at the end. And they will be covering the whole space probably with some overlapping but this is the same thing that we have in the general computer industry that you can do things always with a couple of different things covering a little bit more of space, each one. So I think it's part of the natural evolution. I personally am not concerned about that. All right. Thank you very much to the panel. I appreciate everybody's help. I'll do respect to the next group who I'm big fans of, like to see their panel too. So thank you everybody for coming.


sustainment troops battalion. So right now we're in the middle of a multi- company battalion level live fire exercise where we are practicing area base defense. So as a battalion headquarters we are responsible for ensuring all of our companies can conduct their individual defenses and then we can consolidate that information to make sure everybody has the same common picture and the entire area of operation that we're responsible for is safe and has the security that it needs to make sure our soldiers can continue on with their missions. So base defense goes along the concept of creating an environment where our soldiers can safely execute their operations within their specific specialty MOS's in a hostile environment. So our specific jobs focus on finance, human resources, field feeding and some of the other things that are not normal maneuver MOS's that are fighting against the enemy forces. So our job is to create an area where we keep the enemy out and our soldiers within the area safe. We set up multiple defensive measures and measures that ensure that enemy who are observing us or potentially targeting us are not able to interfere with the overall support operations that we will then prepare and provide to the rest of the division and sometimes core level assets. So the biggest thing I think we're trying to get after with this exercise is the communication piece. So there is stress of no sleep, stress of enemy situations, stress of handling equipment and weapon systems that you're not necessarily used to doing, being hit with different scenarios that force you to consolidate and employ all the training that you've received before the actual training event and just get after creating an environment where you can do actions on the objective and communicate it all the way up to the top. So most of our job out here specifically at our level is making sure the communication flow is happening and everybody's asking those questions of what happened, who needs to know and what do we need to do about it or who do we pass it on to to make sure that the overall operation can continue to get after it. I think they're doing great. So this is not something that our sustainment soldiers get to do every day. So we have our heavy weapon systems from five different companies that are out here integrating together, managing sectors of fire, sharing the fire line, reporting casualties with each other, first sergeants talking to each other, commanders are talking to each other. So everybody's kind of getting together and making sure again that we have the right resources in the right place at the right time so we can continue to provide the support and defense so our finance guys can do their distribution operations. Our HHC can do their record recovery operations, which we have leveraged multiple times out here. And so 90th can do right now they're doing post-elops and then they're getting ready to brief us on a plan for receiving replacements for the rest of the division as they're continuing their fight. And then the field feeding company is doing real field feeding missions out here with us right now and then we're going to be pushing them to do some analysis on providing support to forward fleas with some of their assets.


Hello, we're back. So hopefully this break was not too long for anyone and was not too short for anyone. At least hopefully you had some time to go walk around some. There's a little poll here you can answer your current status if you would like. There were some comments up here. Is there anything that we need to go through? From what I saw it was mostly answered there. Yeah, and I'm pleasantly surprised that there are so many circles in the connected role. So actually it looks much better than I anticipated. So that's good. And remember, if it doesn't work, you can keep watching and listening now and get some help by tomorrow. We designed this so you have this time. For example, for example, me, my connection broke this morning, so I have some homework to do this evening. Yeah, it happens. Okay, I'll also point out that at the bottom of the page, there's already a feedback poll for day one. You can answer what you think about things here. Yeah, and well, keep thinking of that, but we'll have time to discuss all those later. So what's next is this tutorial using the cluster from the shell. And I will switch to my screen here. Oh, I need to share. Okay. Oh, yes, this is me. So. Yeah, so we are right down here. I will open the material. Okay. And can someone, oh, it is in the notes. Yeah, this is a sort of interesting lesson we've got here. So before the course, we were talking and realized this is an almost impossible challenge. Like there's whole day long or multi day long workshops or multi week courses on using shells and Linux and Unix efficiently. So we really need to be careful and clarify what it is we're trying to do here. So our goal is to provide enough background so that tomorrow when we start using the cluster. Things are not completely like, like, it's not impossibly difficult to get started, and you actually can come and sort of follow along. So that means you don't need to answer, you don't need to know everything, but if you can do the different exercises in here, then it'll be good. And in practice, this is probably partly a homework kind of thing because we just don't have time to do everything in 25 minutes. So let's get started. So where are we here and what do we do. So we're talking about how we're using the raw interface, the shell, the terminal, the command line interface, which we got connected to previously. So in this lesson, we're still just here on the login node. So we're not actually using the whole cluster, and you will see some important notes about that as we go down. You don't want to go starting trying to run all your stuff here and ignoring the cluster because, well, you will get a nice email from us saying please use the cluster don't run on the login node. There's some terminology here. So in practice, terminal shell and command line interface, as far as you need to know they mean the same thing. So they have slightly different like meanings in the whole thing, but it doesn't really matter. What does matter is that it is a command line interface and we need to use it. So why? So Table or Cmo, do any either of you have comments on why we use command line interfaces?  If you want to do it in a fashion that is like interchangeable across multiple systems, like multiple different kinds of systems, and you want to do it in a way that it can be done programmatically.  You give it in a way that a computer can understand it, like these kinds of like creation things and stuff. This is the language to do that, like housekeeping, but for computers. So basically instructions for computers on how to do stuff. And this is the way of doing it. Maybe in our metaphor. So we were talking about cooking with the cooking metaphor to computing.  Instead, this course is about getting you manager training and that manager training will help you to script using the shell, a bunch of other cooks that will go use all the industrial kitchen cook your stuff and give it to you so you can inspect it and use it for the next things. And the only possible way to do that is with these kinds of interfaces. Okay, let's see. So this is a picture you probably saw something that looked like this later. This is what we need. So when you run things from the terminal, there's usually this dollar sign which represents that it's the terminal itself. There's some program name. Actually, I should make this a bit bigger shouldn't I. There's some program name, and then the program has different options. So for example with Python, the name of the thing we're running is Python. We give Python the script file we need to run. And then we can give it a bunch of different arguments that control what happens. This is something that you will see. You'll have my cat tries to go out. I don't think it can fit or will go but yeah. Okay. But yeah, so you'll see more about this during the rest of the course so realize this is what you're going to be seeing here. Next up is files and directories. So, okay, it's not actually going out it just in between the two windows. Yeah, I was kind of like, I was, I was kind of thinking that it's between the windows again, but I still got a little jump. Yeah. Okay. So files and directories and that's what we're really trying to cover here. So, um, yeah. Could I demo? Yeah, can you comment? Yeah. Yeah, okay. So I will switch to Cimo screen or Cimo just grab the screen to share from me. Yes, sure. So, so when we're talking about files and directories, you might be familiar with files and directories in this kind of like a way they are like organized in these file browsers and places like that, or in your Google Drive or whatever. But in a cluster, like, I'm now constantly in a file directory. But the default file directory is your home directory. So, so that if I type CD, I will always go to my home directory. I can always check my directory with, I don't know why it's called PWD, but like something working directory. I don't know what the P stands for. What is it? Print, maybe. Oh, yeah, that's true. Yeah, that makes sense. So it's usually something like home, home and something.  So it's like a tree. And at every branch of the tree, there's a slash. So this means that I'm at the folder home slash my username. And this is where you are.  I haven't cleansed it, but there's a lot of stuff here currently. And these are files and it might look different to you. I have a different coloring here, but there's files and folders here. Some of these are folders and some of these are files. So tomorrow we'll learn more about what the different storage places are that's available. So for example, you might need to change to your work directory, which is the large place that's designed for computing work. Would you like to demonstrate that? Yes. So, so in our cluster, the work directory is in this scratch file system. So it's like slash and scratch when we talk about scratch, we talk about this. And there, there's a folder called work. And there's my username. And this is my work directory. You don't see like, when I type CD and the name of the directory, nothing happens like it looks like nothing happened. But if I type now the PWD again, you'll notice that I changed directory. So CD is changed directory. And over here, there's different files here. And, and now I'm at the different directory. It's, it can get confusing, but it's also often good to run this PWD just check where you are, so that you know what directory you're in. Yeah. So now next up, we will talk about copying code to the cluster. So this is often something that takes a lot of time and can be difficult for a lot of people. You have stuff on your laptop, you have stuff on the cluster, you need to move stuff both ways. So yeah, we talk about this tomorrow, but we're going to show one strategy now, which is what we need to do the rest of the course. Arranging this course like a real project. We have this git version controller repository, which is basically a way to store stuff on the cloud and lets you synchronize and move things around. We can't go into that now, but maybe someone can paste the git intro. Yeah, in the, in the documentation, there's this, this magic line.  Yes, sir. Yeah, let's do it there. Yeah. So what we're about to do will work for any cluster in the world, we've specifically made it using this Git repository so that it can be cloned to any computer. Yes. So okay, so yeah, he just did stuff. So, in your home directory, we copied this git clone command, and you don't really need to know what it means, but basically, it's taking from the GitHub service and now has made a new directory called HPC examples. Can you change to there and listen? You notice that I don't type the full path here, even though like I'm at the home directory, because I can go relatively to the current part where I am. So I can own, I can already type the HPC examples. And usually when you're running these terminals, you can use tab to autocomplete. So if you notice that something suddenly jumped out there, it meant that I pressed the tab character, so on the keyboard left side, and it will autocomplete words for you. Okay. So we have 10 minutes left. I propose we show the quick example of running a basic program, and then we can give people some time to play themselves. Does that sound good? Sounds good. Okay. So now Cmo has changed to the HPC examples directory, and we're going to use Python three to run a simple pie calculation script. So here we're running it on the login node of the cluster, which we've just told you you shouldn't do, but this takes only a second or so so it's reasonable to try for development purposes. So here we go. We told to use the Python program. We gave it the relative path to the Python file, and then one argument, which is the number of iterations.  And if the exercises you'll see more examples of using this with different arguments and things like that. I guess we should show how to edit a file at least. Can you show using the nano editor to open up the pie example? Yes. So if I type nano and name of the file. So nano is what's called a text editor. The name comes because there is a previous program named Pico. Okay, and now you can scroll through. Can you give an example of typing something, maybe add a comment somewhere? So I guess Cimo is using the arrow keys to scroll up and down. And then to save you can do control X and then push Y. So it's easy to save and exit with nano. And that's the reason we're talking about it now, but there's plenty of other editors to use later. And nano is usually already installed. So you can just type nano. And tomorrow we'll be talking a lot more about like remote connection to the data as well. So there are other ways of editing files in the cluster, but it's very important to get like this basic language so that you can do basic stuff in the cluster using the terminal. And moving files, copying files, editing files, opening files, these kinds of things are something you do all the time. So it's very important to get it into your system to like get familiar with this interface. Okay, so I propose we stop here. People can basically read what else is here. You can read faster than we can talk. We can keep answering your questions by the notes, which I will now go back and share. Yes. And maybe let's be back a couple minutes before the 25. So let's come back two minutes before. And yeah, so we know you don't, we don't, you don't have time to do everything here, but play around a little bit and do the rest tonight. Okay. And I would recommend going to check first the exercise and try to do the exercises. If you don't know what the exercise is talking about, scroll a bit up and check the contents there because that way it's good. A good way of like quickly skinning through the material like first start with the exercise and then then if you be lost then check the contents and then retry the exercise. Okay, great. Thanks a lot. See you soon. Okay. Hello, we're back. And there's some good comments and stuff here. I think most things are probably answered. There's a good question. How do I move a program from my local repository to your computer. So unfortunately that's a bit beyond the scope of what we can possibly cover right now. We talk a bit more about data transfer tomorrow, but we tried to just show you one really basic thing that lets you do the exercises for the rest of the day. Um, yeah. Okay, and we can keep answering questions about this shell stuff. And really even in the future, if you have questions about using the shell efficiently, don't be afraid to ask because it really is like learning both a whole language and culture at the same time. Sitting down and reading a book, I think doesn't work, but being immersed and asking people for advice does. So what comes next? Thank you.


Hi everybody, I'm Jen with opensource.com and I have a brand new top five articles of the week for today, December 9th. At number five, why the operating system matters even more in 2017? Operating systems have been around for a long time and Gordon Haft tells us why we can expect them to be around for a lot longer. At number four, getting started with the Raspberry Pi. Well, the Raspberry Pi Foundation's Community Manager, Ben Nuddle, shares this article about getting started from software to hardware for beginners and advanced. At number three, seven cool little open source projects that stood out in 2016. This year has been a big year for open source software, so Ruth Bavisette tells us about the little ones, but cool ones we may have missed. At number two, ten open source tools for your sysadmin toolbox. Sysadmins don't lack for options when it comes to great open source software tools, so Ben Cotton tells us about a few of his favorites. And finally, at number one, an interactive calculator for the Linux command line. Dave Taylor is one of the authors of the recently updated book, Wicked Cool Shell Scripts. And in this article he shares Bash Scripts, shares a Bash Script for a simple user-friendly command line calculator. That's it for the top five. Thanks for joining me and I will see you next time.


What is up everybody, Jason here for JaspysCaseBrace.com. We just sold out 2023 Bowman's Best University Football Delight two box break, number 16, random first name, first letter. Now guys, like I told people today, number 15 was officially the last one from the case, but I stole seven boxes that we had from Personals on Fanatics Live to bring over here since we have a sale. So might as well try to sell them tonight, give you guys a good deal. Now, if I remember correctly, I did two of the boxes, Michael did one, wasn't really nothing, crazy, crazy. So I'm hoping these next seven are just spectacular, but there should be some nice ones regardless. It was coming from a case, it's just we sold some as Personals. So I just took them. Now, Steve actually bought out the entire break himself. So no need to randomize them, just gonna create the sheet for the shipping team. And here we go, man. Personal two box break. Well, don't need to randomize this card, right? Usually the Fusions have a duel, Troy Franklin and Bo Nix, and then Jalen Daniels, number to 50. Dylan Gabriel, Brady Cook to 75. Sam Hartman to 100. Travis Hunter to 99, Green Mini Diamonds. Dallin Hayden, and first autograph. How about Bo Nix, baby? 20 out of 25, very nice. You got Frank Gord Jr. And how about a Drake May? Very solid box. Two future first rounders, maybe? We know Drake May is gonna be one. He's been talked about one for last year, but Bo Nix has kind of moved himself to potentially be in a first rounder. I think this dude has all the abilities, man. He has an arm, he's mobile enough. He's definitely matured, definitely became more of a leader as well. Little bit on the older side, playing college ball pretty much all his career there all those years from Auburn to Oregon. But I don't know, man, I feel like he could be pretty good. I'll definitely be pulling for him. I said, I know a lot of people kind of like to joke around when players stay four years, maybe fifth year kind of deal, but honestly, they might be more ready than someone that leaves after their sophomore season or something like that. So, there you go, man, nice box. Now I'm speaking to JJ with Mike Tower. 27 out of 50, JJ McCarthy. And then we got Johnny Wilson, masterpieces. Then we got Riley Leonard, Caleb Downs to 100. Cade Clubnick to 99. Justice Haynes to 150. Jark was 100 to 75. Wow, how about another Bo Nix? Masterpieces this time, 74 to 75. Keon Keely to 50. And Brock Bowers. Nice two boxes, buddy. Well, like I said, guys, we do have another couple boxes left to do as personals or if you're about to break, if not group breaks, guys, let's get the next ones going. Really good boxes I feel like are still hiding here, guys. Thank you, Steve, appreciate it.


I'm Tyce, nice to meet you. Nice to meet you. Lauren, so this is how it normally works. It's not about proving that you're wrong about anything, because I can learn from this too. It's just giving you a chance to think about something that you can strongly believe about. I'm guessing, Lauren, how do you spell that? L-A-U-R-E-N. Perfect how you spell that, nice. Not like L-Y-A-H-T-U. No, my parents weren't that cool. Are you an atheist? I am. You know how people talk about that? Sure. Why are you an atheist? I don't believe there's sufficient evidence for- Oh man, you're almost like this guy. You're almost like this guy. Keep going, keep going. Yeah, I don't believe there's sufficient evidence for me to believe in a God or a deity. What will convince you that there was a God or a deity? I would need like concrete proof. Okay, so you just need more proof? Yeah. Um, if I gave you the proof and you had it, would you be more likely to believe in a God? Absolutely. Okay, well yeah, that's basically it. Okay, it sounds like you're an atheist for reasonable reasons, you just want more evidence. Um, what's something you think atheists should do better? As, like, all atheists? As a group, because I'm also an atheist. Okay. What do you think we could do better? Um... What's the main thing you think we should do better? I don't know, um, don't be giving me, um, I don't know, outreach? Um, actually reaching people, um, that are trying to escape religion? Oh, that are already trying to escape religions. So don't, so don't necessarily, we, it's not so much that we need to, it's not like we're lacking in belief or lacking in the effort to convince people that this is a good position to have. Right. It's more of like, for the people who are trying to get out or locked in a bad situation. Right. Because some people don't want to leave a church because they have the community or their family has been in church for however long and they don't really know what it's like on the outside.  Yeah, so like, anonymous secular groups that they could be a part of? Should I just make it a comfort zone before they can make the step out of that? What's a good example? Do you have any good examples? Or do you have a good way of implementing that? I mean, I think recovering from religion is a good one. Okay, from religion? There's like anonymous Facebook groups too that I like. That's true. Yeah. Facebook, I think. Yeah, we have a closed group. If you need that face to face though, there's Discord channels that you could use, I recommend Discord. But what would work for you if you were trying to escape from religion? And you just said, I should see a talk to somebody who will keep that secret. I don't know. Yeah, that's what we do. Because I've never, because I've never been in that situation.  Like it wasn't a cult type thing. Sure. I don't know, it would kind of just be chance, wouldn't it though? Yeah, I'm fine with, I don't know, as an answer until we get like more information. Yeah, I don't know. How about this? If we ever meet again, or if you feel like you want to contact me about this, if we can talk about that some more. I'd be really interested in recommending paths for people who are in that kind of situation. And since you guys are like, you know, so well-debt from like American atheists, maybe there's like a good outlet for people who like want to anonymously just let themselves talk to an atheist. Right? Like, is there a group of atheists that can talk to you? Do I have to just figure out if we're on the same track? Yeah, I'd be great. I have to like Discord channels. Yeah, yeah, I was just like, hey. Yeah.  Yeah. Cool? You know. Right? We can work with that. Are you going to start at this for now? Yeah, why not? Something to talk about? Yeah. Let me know. You already got a channel at Discord. We can make some extra links. Yeah, definitely. For street personality and just hope these questions. Okay, cool. I really appreciate this talk, Gord. Thank you. Yeah, that's all. That's your out. Yeah, it's time. It's fun. Yeah.