Honestly, we are talking fine leather goods. Fine leather goods. Everyone has to have their own scent. And my scent right now is Ambassador by Old Spice. She can drink it out of this bomb mug. Noodle, what do you think? Noodle loves things that are mass market. He looked at this and he goes, handcrafted, puh. Hi, everyone, thank you so much for watching this week's episode of Tools of the Trade. My name is Jonathan, this is Noodle, and this is the show where we find out what everyday items, everyday entrepreneurs need to get through their day. And this week, we are featuring another one of the icons from our Icons of Our Tribe series, Nick Verma. Now, Nick is amazing because she traveled to India one time and she fell in love with the handmade leather sandal that's popular there called a chapel. What she loved most about it was that it was made by artisans, it was something she felt good wearing and it wasn't fast fashion, right? This was something that you buy, you break in and you wear to death. And it lasts you a really long time. And Nick brought this idea over to Vancouver, where she lives and she opened her own business, Chapel's Chapel. And we are so proud to be able to share the box that she curated with you because anytime we can encounter an entrepreneur who truly makes stuff with their hands, I'm always the most impressed because I have no technical skill or creativity in that vein at all. Nick, I'm very inspired by you. I love the stuff that you make. I can't wait to get into this box. Also, Noodle is just like perfect right now. He's a perfect sleepy angel and we're gonna see how long we can make that last. The first item we have in here is from Lulabo. From Lulabo. Ooh, what is that scent? I wonder what her scent is. So Lulabo is a very famous, oh my God, why do I keep dropping stuff? This is a perfume, it's a perfumery. So Lulabo is a very well-known perfumery in New York City. I can imagine that it's located in a bunch of other places as well. Ooh, what's this? A little book? 26 removable sheets. So it looks like in here what we've got is we've got a perfume and we've got a notebook or a sketch pad of some kind. It's a perfumed notepad. Oh my God. I buy my notepads from Dwayne Reed. So this notepad is actually scented which is something that I've never encountered before. But what I think is great about this is if you wanna write like handmade letters or you wanna write notes to people or even just give it away as a gift, this is really, really special. This is really high quality, very well made, something that's not gonna fall apart on you. And she put a signature perfume in here as well which I think is great because everyone has to have their own scent. And my scent right now is Ambassador by Old Spice because I just ran to CVS to buy some because I forgot to put it on this morning. That was very jarring. And I went, what's that smell? Noodle, is that you? No, it's me. If I had been to the Lobo, I probably never would have even had that issue, but I did. So this is a beautiful scented perfume, an actual scented notebook. I always like the idea of having a scent just because you probably need other business professionals and it's something I think that kind of elevates you. Oh, I smell like Rose 31 and that's amazing. And they remember that, that's gonna make a large impact on people. I think this is an incredible addition. You've got fine taste and I might steal this. Okay, the next item we have is, oh, it's just a pretty mug. I love this. I like this also because you can tell that this is handmade. Well, she talks about this all the time in her icons video if you get a chance to look at it, but she loves handmade goods. She loves supporting artisans and she loves supporting people who pour themselves into their craft and they're not afraid to put themselves out there to try and sell it. And I can imagine that this is exactly that product. There's a thing in the bottom right here. 300 gram bag of Ethiopia East Gujisawa coffee beans. So what we know is that not only did you get the mug, but there's coffee that's coming with it. And apparently when we ordered this, it's so fancy that it took a very long to get to us. So instead of having it in this box, we put a nice little IOU in here. When you win this box, whoever chooses to enter, you will get the bag of coffee that comes with it. How great that she did that combination. A lot of people put coffee in their boxes and I, again, I think more than anything, what that says is that entrepreneurs, first of all, they're all human, right? And a lot of humans get tired every now and then, especially if you're running your own business. But again, another one of these aspects, you can tell that this is probably local, this is probably a really high quality product and it's probably something that is not sort of mass produced. And she can drink it out of this Bob mug. Noodle, what do you think? Honestly, Noodle loves things that are mass market. He looked at this and he goes, handcrafted, pfft, give me something from Marshall's any day of the week, Noodle. Okay, we get it. All right, the next item we have in the Nick Verma box is, oh, this is great.  Oh my God, I might take this box for myself. It's a reusable string shopping bag. So this is really cool. I'm not going to take it out, but I don't know if you can like zoom in on this or anything. String bag that you can bring to you to the market. You can bring it to the farmer's market. It's a 100% certified organic cotton carrier for vegetables and fruits. I can imagine that you can carry some other things in here if you need to. More than anything, this again, it speaks hugely to Nick's sort of passion towards against fast fashion. Like this is something that you use all the time. This is something that's not going to make waste. This is something that you're going to feel good about.  Right, that's not something, or paper for that matter. I love that this was included in this. I can absolutely see her in her pair of chopples. Just walking to the market, breaking in a nice new pair of leather shoes. Bam, gotta get my fruit. Boom, gotta get my vegetables. Bam, and she's got a bag for it. I think that's brilliant. I love this. I really do think this is an incredible addition of this and I can't believe that I don't get to steal this. Maybe I'll put noodle in it. I wonder what the weight limit is. I wonder how tough these fibers are. Noodle's 25 very dense pounds. Okay, oh, oh, this is really cool. It's a one year eight issue subscription to Condé Nast Traveler magazine. Ooh, this is cool. So this is just a group-on. So when you win this or you get this, you can go ahead and subscribe. So Nick is an avid traveler and obviously when she was in India, when she was inspired to start her business and how great that she sort of made this successful because even if you can't get out of the country, like maybe not this month, maybe not next month, having this magazine will make you feel a little closer to the world around you, I think. And it's got beautiful pictures and who does not love a coffee table magazine? Do you imagine people come into your home or your business? Oh, I wonder, is she legit? Oh, is that eight issues of Condé Nast Traveler? Oh yeah, she's legit. She's got the group-on. And you can probably learn a lot too, right? You probably learned a lot about different cultures, about different things going around in the world. So maybe you can make a plan and you can go and find the next big international product to bring domestic. Or if you're like Nick, to Canada. Okay, and the final item we have in this bag, keep calling it a bag, it's not a bag. I love that silk bag, cotton bag. Oh my God, I love that cotton bag. Oh, these are draw, oh, these are pens. Sakura, Pigma, Micron pens. So these are nice, sketching pens. I can imagine that these are crucial for Nick in her business with sketching out different designs for shoes she wants to make. Because she makes them all by hand, right? That's one of the best things about chapel is that these are handmade shoes. Machines do not get involved in this. You have to know not only what the shoe's gonna look like at the end, but you have to know the designs. You have to know all the steps of this is where you weave first. This is when you put the sole on it. I'm not even gonna pretend like I have any idea how that happened.  So if you're starting your business and you're selling your first product and you have to think of packaging for it, you might need to start somewhere, right? With your own design if you wanna take your own hand at it. And I think this is an incredible addition here. It speaks loudly to how much she cares about the design of her shoes, not only to the materials, but how they're made, the design of them. It's every aspect of the process. She has control of them. Did you hear that? He fell asleep. Noodle, we are talking fine leather goods.  And we'll just kinda run with that. But that's everything. That's everything in this box. And I know I'm kinda grateful they didn't put eight separate issues of Condé Nast Traveler Magazine in here, but I love the idea that they put a group on it. I am so inspired by everything that I saw in this box. I really can't get over how much I love this bag. I think I might have to go buy one myself. But I think more than anything that this really spoke to her day to day, right? She's not only, is she someone who has this product and she makes this product, but she lives by these rules, right? This whole idea of it's not fast fashion. This is something that is durable. This is something that you're gonna be able to walk in and wear for years, and you're not gonna have to worry about all the waste of recycling shoes, getting rid of shoes, getting rid of garments, whatever it might be. You can tell that she really puts that into every aspect of her life. She really is thoughtful about how she's impacting the world with both herself and her business. If you love this video, please be sure to head to our YouTube channel and like, subscribe and ring the bell on our page so that you can get notifications whenever a new episode of Tools Goes Up or another one of our amazing GoDaddy series that we have coming up to you every single week. So, for myself, for Noodle, and for this unbelievable, deliriously amazing cotton vegetable bag, thank you so much for watching and we'll see you next time.


Hello, my name is Belmiro and I'm a cloud engineer at CERN. In this session, we'll dive into the history behind the CERN cloud infrastructure. I had a lot of fun revisiting Aldi's material again. I hope you enjoy it as well. But first, what is CERN? CERN is the European Organization for Nuclear Research. CERN mission is to do fundamental research, especially in the iron energy physics. It's one of the biggest international scientific collaborations in the world. More than 10,000 scientists from all around the world work at CERN. CERN provides the particle accelerators and all the infrastructure required for iron energy physics research. That includes compute and storage resources. So let's start. Let's go back 11 years, to 2008-2009. That was a time when we were experimenting with visualization and server consolidation. A group inside the IT department started to experiment with visualization, initially with Microsoft Visual Server and later with IPReview. The idea was to offer service resources for the CERN users. The problem was that those tools were in the build to offer such service. So we built a custom web application that interacted with those tools and allowed users to create virtual machines. Only Windows and scientific Linux images were available, but this was huge at that time. It was called CVI, the CERN Virtualization Infrastructure. And it was a very popular service at that time in the organization. By popular, I mean around 100 new virtual machines every month. Remember, this was 2008-2009. At the same time, other group in the IT department was trying to virtualize the batch service. The batch service is the biggest IT service in terms of computing resources. And virtualize it will bring a lot of advantages. The project was called LXCloud and explored two cloud orchestrators at that time. One was an open-source solution, open-able, and the other was a commercial product, ISF from platform computing. The IPrevisor that we used was Zen because KVM wasn't stable enough and not very well supported at that time in scientific Linux 5. And we tested the limits of those products because that was the big requirement for the batch service. We run a scalability test with more than 16,000 virtual machines in both of these projects, which was huge for the time. The early days of OpenStack. In 2010, there was this open-source release of this new project from NASA and Rackspace. You guess it, OpenStack. At that time, if you were working in the cloud computing space, this was big news. There was a lot of press around it. And from the beginning, it got the support from several big companies. And this just created a very vibrant community around it. So of course, we started to look into this new project. And this was very, very exciting times. This is just a funny slide. What you see here is probably the first presentation about OpenStack at CERN. This was in January 2011. So the presentation was based in the first OpenStack release, Austin. You can see that we needed to use NovaManage to create users, no Keystone at all at that time. And to interact with Nova, we needed to use Ilka tools. If you'd like to explore this presentation, you can still find it today in the link below. Just another slide that I found in one of my presentations from 2011. This is a screenshot of an early development version of Horizon in 2011. It's quite different from what it looks today. Let's now talk about the CERN Agile Infrastructure project. This was the CERN project that really brought OpenStack to CERN. In 2011, CERN was still managing the data center using our custom-made tools. The majority of applications were still running on physical nodes, and in two years we knew that we'll get a new data center in Budapest, more than 1,600 kilometers away. All of this to meet the compute and storage requirements for the Large Hadron Collider and for service continuity. Also users were requiring more and more resources. And when using physical nodes, this process can take a long, long time from the request to the provisioning. It was clear that we needed to change the tools, the architecture, and the way we manage our data center. New open source projects were now available, configuration management, monitoring, and resource provisioning, so we shouldn't continue to develop and maintain our own tools. Also a private cloud will offer much better operational and resource efficiency. Jim Bell, the CERN Cloud Infrastructure Manager and also a board member of the OpenStack Foundation presented the vision of the CERN Cloud project in the OpenStack Summit in San Diego in 2012. All of these slides that you are now seeing are from his presentation at that time. To build our private clouds, it was clear that OpenStack was the right project. In these slides, we presented our plan to deploy OpenStack. We needed to understand that at that time we were running Scientific Linux 6 and the RDO packages and the initial puppet modules were just made available. But one of the goals was to manage the new data center in Budapest using OpenStack. This diagram that you see there shows all the project's interaction at that time. We have Horizon, Swift, Glance, Nova, Cinder, Keystone, and of course Quantum there. We said OpenStack was complex in 2011. Imagine today if someone does a diagram like this. To make this possible, our strategy was to build several prototypes to try different architectures and configurations, give them to the users, and iterate fast based on feedback and our discoveries. We had only a few nodes available for these initial tests and it was clear that we needed to support two iProvisers from the beginning. If we would like to migrate into OpenStack, the virtual machines from the Windows virtualization infrastructure that was already running a few thousands of virtual machines, the CVI project that I talked at the beginning. In this timeline, you can see when we deployed these different prototypes and of course notice the cute code names that we gave to them. Functionality was added incrementally into each prototype. Also, we spent a lot of time with users to help them test their applications in infrastructure and understand the requirements. From the beginning that we try to engage with the OpenStack community. From early on, we started participating in the OpenStack meetups around us, London, Zurich, and so on. And actually also organizing the Swiss and run out user group meeting in 2013. Also, since the OpenStack summit in Boston in 2011, that we participated in all of them. This photo is from the first OpenStack summit that I attended in 2012 in San Francisco. It's quite different from what we have today. On July 2013, we moved from prototypes to a production infrastructure. Meaning that we will not destroy the infrastructure anymore, at least voluntarily. And we will support the running workloads for our users. We presented for the first time our production architecture in Hong Kong in 2013. This is one of the pictures from that talk. So our initial deployment looked like. We are running the most recent OpenStack release at the time, Grizzly. We had two cells, one cell in each data center. Cells version one, of course, and we thought that two cells would be enough for the next years. The control plane was fault tolerant and it was running on physical nodes. Understanding resource utilization was important for us, so we deployed Selometer from the beginning. Everything was integrated with the CERN infrastructure, accounting, the network. Glance was backed by AFF. In reality, this is not entirely true because these slides are from November 2013. When we moved to production, the storage was backed by AFS. Only after a few months, we migrated all the images to AFF. Inside the same cell, at that time, we supported KVM and IPReview. In terms of Rabbit, we had three Rabbit MQ clusters, the main control plane and then one per cell. We had no idea how much the infrastructure will change over time. This is a simple overview of architecture and the different components that we are running at that time. Just a fun fact, you can see that we run the first version of StackTac in our infrastructure to consume notifications. Later, the version two required Swift, so we needed to drop these components. This graph shows the fast growth in number of VMs of the infrastructure. In just a few months, from July 2013 to the beginning of October 2013, we are managing more than 2,000 visual machines. Here, you can see the growth of the cloud infrastructure over the years. The total number of VMs created, cumulative in your left and the total number of VMs running in your right. You can see that we reached the VM number 1 million when year and a half after moving into production. It's very difficult to maintain this slide. We can see the projects that we run in each release. In 2013, only Nova, Lance, Horizon, Keystone, and Silometer. And today, the amount of projects that we offer to our users, including Magnum, Barbican, Ironic, and Manila. This is, again, just another funny slide. Some years ago, we tried to draw our architecture in the whiteboard in my office, and this was the result with all the service interactions. You can see components like Silometer at the time, Steel, Nova, the load balancer on top, Magnum, Cinder, and many other projects that we are running at the time. I will go now very fast through some of the milestones of our cloud infrastructure that I find important or very interesting. Nova Cells. We are using Nova Cells from the beginning. Initially, only two Cells, version one, and in 2011, we upgraded to Cells version two. Currently, we run more than 80 Cells in our infrastructure. Silometer, the rise and fall. Running Silometer at scale was a big challenge. It had that complex architecture and some design faults that made it very difficult to deploy, manage, and actually retrieve data. So after three years, we decided to remove this component from our cloud. We started to offer Cinder in 2014, back at BySafe, and a few years later, we also started to offer Manila and an S3 endpoint, both back at BySafe. In 2016, we moved Magnum into production. Since then, our users can create Docker swarm and Kubernetes clusters. It's a very popular service in the organization with more than 500 clusters. Network. In our initial deployment, of course, we are using Nova Network. And we can still see some of that history in our clouds. We still have some old Cells that run Nova Network. However, since a few years ago, all the new Cells run on Neutron. We hope, finally, migrates the old Cells from Nova Network to Neutron soon. Bare Metal. Ironic is in production since 2018. Currently, more than 5,000 physical nodes are managed by Ironic. And the goal is to enroll all the servers available in the data center into Ironic. We try to automate as much as possible. To help on that, we use, from a long time now, Rundeck and Mistral. Through all these years, we've been facing several operations challenges. We try to talk as much as possible about them in our blog post, the tech blog. And also, during all the OpenStack presentations that we have been giving over all these years. So now some of the operation challenges that we faced over all these years. Let's start with upgrades. We upgrade to every release and the cycle is only six months. The Scientific Linux 6 upgrade to CentOS 7. And now, we are again in the process of a major operating system upgrade from CentOS 7 to CentOS 8. We supported for a few years KVM and IPREV in the same infrastructure. Actually, we migrated all the virtual machines from these old infrastructure, CVI, to OpenStack IPREV, and then finally to OpenStack AVM. And of course, the challenge of the latest security updates that we have been facing that require the reboot of almost all the infrastructure. In 2019, we introduced the new regions into the infrastructure. Actually, we split our production infrastructure into two regions. We wrote a blog post on how we describe how we did it. The main reason for this split is nutrient scalability. Today, we have three production regions. And just a few months ago, we introduced preemptive instances into our production infrastructure that allows projects to use the spare capacity. We also wrote about it. You have the link of the blog post if you're interested. Something that we've been doing from the beginning is to work together with the OpenStack community. And I really believe that is part of the success of the CERN Cloud infrastructure. We share our experiences in the OpenStack Summit's presentations, user meetings. We won the first OpenStack User Award in Paris. We have PTAL and core members in different projects like Magnum and Ironic. And we organized several OpenStack events like the OpenStack Day last year. And even during these difficult times, we continue to participate remotely in several events like the OpenDev and the OpenInfra UK. So 2020, what's next? We are looking on leveraging container orchestration to deploy the OpenStack control plane, re-enroll existing physical resources into OpenStack Ironic, exploring the introduction of GPU resources and moving all the remaining resources from Nova Network to Neutron. Also exploring how to provide machine learning platforms and functions as a service to our users. Here you can see a snapshot from one of our monitoring dashboards. You can see off the number of cars available, the instances running, the number of users and projects that we manage in our cloud. A brief summary about the past 10 years. During the last 10 years, resource management and deployment model changed completely, from virtualization and server consolidation to a cloud infrastructure, from bare metal to virtual machines to managed bare metal to containers. We continue to adapt the infrastructure to the new technologies and requirements, control plane managed by Kubernetes, new regions, printable instances. And I would like to finish this presentation without mentioning all the people, staff members, fellows, project associates, technical students, summer students, members from other labs that have contributed to the deployment of the certain cloud infrastructure. Thank you to all of them and this list is not in any particular order. I'm happy now to answer all your questions using the chat platform. Also, you can connect with me using Twitter. Thank you for watching this presentation. I hope you like it.


I've only had a big family that's come to White House. To the rest of the world. To the speaker of the United States. To the speaker of the United States. That's a lot of people. President, what do you think of Michael Flannery? Yeah, I am. When you're buried, I hope that you are very coffined. Built from a tree a hundred years old, then I'm going to plant tomorrow. I see a ride in that horse. I see him so long with all this winter weather. But a couple of times today, moving around and stepping off the platform over there at the Irish Embassy, I found myself off balance. Yesterday you said, are you like stiff? And I realized, yes, that's what's wrong. I haven't written for so long. Yeah, well, our legs are safe. All right, let's see.


The Craft Foods Company, makers of craft quality foods, presents Harold Perry as the Great Gilder Sleeves! Great news! Gilder Sleeves back! But here's even greater news. Tonight the makers of Parquet Margin are announcing a great new $50,000 cash prize contest. Open to listeners in the United States, Canada and Hawaii. It's one of the easiest and most exciting contests in radio. Everyone can enter. Anyone may win. You'll get full details later in tonight's program. Until then, the Great Gilder Sleeve brought to you by the makers of Parquet. The margarine millions prefer because it tastes so good. That's P-A-R-K-A-Y. Parquet margarine made by Craft. Well, the Gilder Sleeve household seems to have fared pretty well during the summer. Margery has a nice tan. Leroy has grown a couple of inches. Bertie the cook has gained a couple of pounds. As for the Great Gilder Sleeve himself, well, he seems in rather good spirits. Good spirits at least for a man who's tallying up his checkbook after summer vacation. 66, 75, 84, 50, take away three, six, nine, twos to carry. Not bad. Got through the summer, still have some money in the bank. Well, now that happened. Maybe I made a mistake someplace. Get five, six, nine, two, three, four, three, two, one, seven, five. George is right. Bertie! Yes, Mr. Gilder Sleeve? Bertie, let's have something good for dinner tonight. That's fine with me, Mr. Gilder Sleeve. How long here? Are you busy? No idea. I'm all finished. It's been figuring up the costs of the summer. We managed to come out with a little money in the bank. Not much, but a little. Oh, that's well, Uncle Morris. Yeah, we're in pretty good shape. Christmas is still three months away. You don't have to worry about income taxes till next March. Well, Uncle, I need a check for my tuition at Junior College. Tuition? Well, how much is that? $90. $90? Just to be a freshman? Well, sure. And that's just a start. I have to buy books and all new clothes. New clothes? What for?  There's 300 boys on the campus. You have to dress for all 300 of them? It won't be too bad. Last year it only cost Francy's father $450. Everything for the whole year. $450? I have to get dressed now. Francy and I are going shopping. Shopping? Where am I going to get $450? Hi, Uncle. Hello, Leroy. Can I have a dime? Ice cream man's coming. Between Marjorie's education and the Ice Cream Man. Oh, and I've got to get some new shoes, Uncle. New shoes? Sure. Look here, the right one's nearly worn through. Left one's okay. Well, when the tire's on a car where unevenly, we sweat. No, you couldn't do that. A new pair is only eight bucks. Eight dollars? I thought your shoes only cost $450. Yeah, but this time I want to get saddle shoes. Well, on those feet, any shoes are going to look like saddles. All right, Leroy, we'll get your shoes, but let's watch it. Huh? We have to pull together to send Marjorie to college this year. It'll cost $450. I don't quite see where it's coming from. Hey, I've got an idea how to help. How? I'll quit school. Oh, no, you won't. I'm only doing it to help you and Marjorie. I know, and it's very thoughtful of you. If I didn't have to go to school today, I could make some money caddying. Caddying? For a guy that came to visit the Bullard's last night. That's his green Cadillac across the street. Oh? I thought all the money bags Bullard scratched his and got a new one. He offered me five dollars to caddie for him today. That's not as important as getting an education, my boy. Anyway, I need a lot more than five dollars. Let's just leave. Yes, Bertie? Is it all right with you if I help Mr. Bullard's maid on my day off? What's this, Bertie? They're throwing a big party in the man who owns the green Cadillac's honor. Well, I think I follow you, Bertie. Who is the fellow they're giving the party for in the green Cadillac's honor? No, I mean... Oh, that's Mr. Henry Krauss. He's a big song publisher. Never heard of him. Oh, he's a big man in the song publishing business. Is it all right if I go to Mr. Bullard's and make the ten dollars? Well, I suppose so, Bertie, if you want to go slumming on your day off. Thanks, Mr. Gilfrey. Gary, I wish I was a songwriter. If I had a songwriter, I'd sell it to that Mr. Krauss. I wouldn't be making ten dollars, I'd be making a couple of thousand. What's that? Just like Mavis Peacover. Who's Mavis Peacover? Oh, she's a housewife. She had eight children and a husband. And in her spare time, she wrote a song and got twenty-five hundred dollars for it. Spare time, huh? I can't believe that, Bertie. How much do you say she got for it? Twenty-five hundred dollars. Her picture was in a magazine. It was? What's in that songwriting, Mr. Gilfrey? Remember that hup-sup song? That's how it got rich, yes, sir. Hup-sup, wrong songwriter, really, right? Mavis Peacover, twenty-five hundred dollars. Not bad for a housewife. Gee, uncle, why don't you write a song and make twenty-five hundred bucks? Because I haven't got the time, LeRoy. A water commissioner can't be fooling around writing songs. Although there was a time when I was in school, I wrote a couple of songs. One wasn't bad. In fact, it was very good. People liked it. Whatcha gonna do, uncle? Now that I think of it, there was a copy of that song and an old trunk up in the attic. Whatcha gonna do? All right, George, if Mavis Peacover can do it, so can Throckmorton Peagildersley. Where is that old trunk? I sure hate to boob all this junk, but it'll be worth it. Uh... Dusty up here. What's this on top of the trunk? Oh, old Hattie's old dress form and Hattie. Pretty chubby. Haven't looked at this trunk for quite a while.  Hope he hasn't chewed up my lyrics. Well, here's my old ukulele. Wonder if it still works. Oh, you can bring Pete with the two left feet, but don't bring Lula. Needs tuning. If I find the song, I'll just take it over to Bullers and sing it for Mr. Henry Krauss. Ah, here it is. What's this? Dedicated to Myrtle Pickens. Nearly forgotten about Myrtle. Let's see how the song goes. There's an old familiar strain, a haunting refrain. If this is worth $2,500. Well, it is if it does to other people what it did to Myrtle Pickens. I'll never forget the night I sang it to her. Sitting on the dam at the mill pond. There's an old familiar strain, a haunting refrain. That takes me back to days of yore. Lovely truck, Martin. Oh, it's nothing. Just a hit. Go on, please. Oh, well, if you really want to hear more. Oh, I do, I do, I do. Control yourself, Myrtle. I see the chapel on the hill. The springs first daffodil. Reflected in the mill pond by the shore. Myrtle. Yes, Dr. Martin. Don't you think you'd better sit closer to me? Well... There are a lot of bullfrogs out here. Oh, all right. Mind if I put my arm around you? I can play the uke with one hand. How can I refuse a little hug after you've written a beautiful song for me? Myrtle. Oh, Frogmorton. Myrtle. Oh, Frogmorton, don't squeeze me so tightly. A little hug never hurt anybody. Oop. Grat the luck. I crushed Aunt Hattie's dress form. Better get a few throat lozenges before I see Henry Kraus. Huh? Shouldn't have sung my song for the mailman. Good morning, Pee-Vee. No, no, no, Mr. Guelty-Pee. What can I do for you? Anyway, give me a box of lozenges. For these throat? Yes, Pee-Vee. Just want to limber up my pipes. Well, there's nothing like the water coming from your teeth and these pipes in shape. Yes, yes. Henry's a little widower, Mr. Guelty-Pee. Wire. Pipes. Yes. Pee-Vee, this has nothing to do with the water department. But with sending Marjorie to college, I have to supplement my income. I found a song I wrote years ago going to sell it to a big publisher, Henry Kraus. Yeah, that's nice. Yeah, you watch. Going to make a lot of money with it, Pee-Vee. Can you give me a change? You betcha. Look at Irving Berlin and Cole Porter and Nature Boy. All Nature Boy wrote was one song and look where he is today. By the way, where is Nature Boy? Well, anyway, there's big money in songwriting and I expect to make at least $2,500. Take a look at it, Pee-Vee. Very well, Mr. Dorothy. Dedicated to Myttle Pickens. Nice title. Yeah. Pee-Vee, that's not the title. I haven't named it yet. Uh-oh. Myttle Pickens, a friend of yours? Never mind. Read the lyrics. Yeah, very well. There's an old familiar strain a haunting refrain that takes me back to days of yours. Sounds like a song, all right. Don't you think I'll sell it for a lot of money? No, like you say. There's a lot of money in songwriting. Yes, sir. Listen to this finish. So wherever I may roam my thoughts will return to home for I know that love and you are there. Doesn't that just give you goose pimples, Pee-Vee? No, no, I wouldn't say that. Huh? Well, I guess you can't get goose pimples out of an old prune. Step aside, Pee-Vee. I'm going over to Bullard's and sing it for Henry Krauss. I hope Bullard's Baldwin is in tune. Well, Henry, you surprised me on the golf course. Your game has improved. Oh, thank you, Rumson. I wasn't quite as nervous on my putz today. Oh. It's wonderful to spend a few days in the peace and quiet of Summerfield. Well, it isn't quite as noisy as your tin pan alley in New York. I wasn't annoyed so much. It was those infernal would-be songwriters. Everyone thinks he can write a song. Huh? My doctor said I'd have a nervous breakdown if I didn't get away from it all. Well, you can rest assured there isn't a songwriter within 500 miles of here. Oh, that doorbell. Excuse me. Yes? Well, hello, Mr. Bullard. Oh, it's you, Gilda Sleeve. Yeah, it's me, your neighbor. Nice day. It was? Yeah. I have a little something here I've brought over to show your guest, Mr. Henry Krauss. No. Now, listen, you see this roll of music? This represents a valuable business opportunity for a publisher like Mr. Krauss. Remember Nature Boy? Don't tell me you have him wrapped up in there. I look, Bullard. Just let me see Mr. Krauss for a minute.  Well, if you must know, I've written a little song for him. Oh, no. It's a beautiful song. He'll be crazy about it. Gilda Sleeve, go home. What? Nobody is going to see Mr. Krauss, especially no would-be songwriter. Would-be? Now, see you, Bullard. Enough is enough. I agree. Good day, Gilda Sleeve. Oh, Bullard.  In just a few minutes, you'll get the big news about Parquet's $50,000 cash prize contest. Get pencil and paper now, and listen carefully whenever Gildy sings his song, because that song is going to be the basis of one of the easiest and most exciting contests in radio. Well, let's get back to the great Gilda Sleeve. His plan to sell a song to a music publisher visiting the Bullards hasn't worked out too well. But he's not giving up, oh, no. Right now, he's heading into the Jolly Boys Club with his old friend Judge Hooker. Don't you worry, Judge. The song's a hit. All we have to do is rehearse it a couple of times. I've explained it to the Jolly Boys. We're going over tonight and singing it under Krauss' window. Well, yes, we're late, Gildy. I hear Floyd and Genie. And the Chief. You can always hear the Chief. All right, fellas. Break it up. That song will never be popular. I'll show you a real song. All right, all right, all right. Okay, Commis, what are we going to serenade the guy with? Have it right here in my briefcase, Floyd. Wish I'd had a copy this morning. Your big publisher was in for a shave. Really? Yep, I could have sung him a solo. Now, Floyd, this is a job for all of us. Gather around, fellas. I had Bessie-type copies of the words for everybody. Here you are, Judge. Thank you. Chief? Thank you, Commisioner. And here's your copy, PB. Oh, I remember the words, Mr. Gildy. Oh, yes. Well, Floyd, shall we try it out? I'm ready, Eddie. Everybody sight-read while Floyd plays it through once. All right. All right. All right. All right. All right. What's the trouble, Floyd? Something here ain't right, Commision.  But Commision ain't musical. There's nothing wrong with the music, Floyd. You just don't happen to be a Jose Uterbi at the piano. Oh, yeah? Well, I've been glassing at the lyrics, and you ain't no Harry Jacobs Bond, neither. Watch it, Floyd, or I won't take you with us. I ain't so sure I want to go. Oh, now what? Maybe, maybe it'll sound better if we all sing it together. Well, let's do something besides criticize it. We don't go ahead with the rehearsal, and Mr. Kraus will be asleep before we get there. Don't worry, this song will wake him up. Floyd. After glancing through it, Gildy, I'd suggest that you take a day or so to work on the lyrics. The lyrics are all right, Judge. Everything rhymes. Oh, fellas, come on. Let's give it a try. That's the spirit, Chief. All together now. Gildy, I think you'd better excuse me from your little party tonight. Why? Not that your song lacks merit. But I don't think singing on alarm at midnight is quite in keeping with the dignity of a municipal judge. But Horace... You know, Commissioner, reading the song through, I'm beginning to think the same thing. Oh, no, Chief. That's right. It ain't within my dignity, either. P.B., you'd like to sing it with me, wouldn't you? Well, no, I wouldn't say no. Oh, no! A fine bunch of friends, and I thought I could count on the jolly boys. Sure, any time, but let's sing something we know, huh? Yeah, as long as we're here, let's do some real singing. Come on, gang, join in. Dad, a little closer, P.B. Don't bite me all day. Who slammed the door? Where's Mr. Gilder's sleeve? Oh, I can't get it. I think he walked out on it. Yeah? Somebody say something to hurt his feelings? I'm afraid we all did, gentlemen. After all, we didn't give his song much of a chance. No, that's too bad. It really ain't right to let a fellow jolly boy down. Yeah, how do we know he ain't got a hit? My snap judgment ain't infallible. When this song could grow on you. How did that go again? There's an old familiar strain. I'll stow those jolly boys. I don't need their help to sell my song. Let's try it once more, Marjorie. Again, Uncle Moore? Well, maybe Mr. Kraus can't hear me across the street. But, Uncle, it's getting late, and it's cold with the windows open. Well, he hasn't turned out his light yet. By George, there's a break, Marjorie. He just opened the window. Get to the piano quickly. Uncle, must you make it so obvious? It's pretty obvious you want to go to college, isn't it? This song can send you. I hope it sends Kraus. Let's try the second chorus. And louder. Oh, all right. I'll get some response this time and know the reason why. In my reverie, it seems A summer What are you speaking? Jones. Jones? Oh, Jones down the street. Are you branding Kraus down at your house? What? Whatever you're doing, stop it. We were disconnected. What did he say, Uncle? Something he wouldn't dare say to my face. Say, why don't I phone Mr. Kraus at Bullard's? Sure, I'll sing my song over the telephone. Oh, Bullard doesn't answer. That's not Bullard. I'd like to speak to Mr. Kraus, please. Yes, sir. Get ready to play, Marjorie. Hello? Mr. Kraus, you don't know me, but I have a song that can make both of us a lot of money. Just listen. There's an old familiar strain A haunting refrain That takes me back to days of yore How do you like it so far, Mr. Kraus? I think it's terrible. Oh, Bullard, how did you get on the telephone? Gildersley, I owe you an apology. You do? Well... Yes, there have been times when I thought you were a sorry water commissioner. But as a songwriter, I think you're a very good water commissioner. What? Good night. Good night. Meet a song, Marjorie. What are you going to do, Uncle? I'm going to throw it in the wastebasket. But, Uncle... I'm no songwriter, Marjorie. I'm nothing but a very good water commissioner.  Nope, not hungry. Uncle, don't feel too bad. Please, Marjorie, I've thrown the song away. I'm trying to forget about it. Gosh, Uncle, I didn't think it was so bad for a beginner. Leroy, you haven't even heard it. Oh, yeah? What do you think kept me away half the night? Well, I'm off to miss Bullard to make that $10. Yes, this is your day off, isn't it, Bertie? Yes, sir. I'll get it. I'll get it, Bertie, it's your day off. Oh, thank you, Miss Marjorie. Mr. Gilsleeve, I found your song in the wastebasket this morning. I know, Bertie, that's where it belongs. When I go over to Bullard today, why don't I just drop it on Mr. Kraus' place between armory and dessert? No, Bertie. Yeah, that's the trick I use with my report card. I give appeal on a full stomach. All right, Leroy. Now, let's everybody stop trying to be helpful. I'm no longer interested... Mr. Munson at the barbershop, Anki. Floyd, what did he want? Well, he wants you to come to the barbershop right away. Well, I'm not going.  He said he wants to apologize. Floyd Munson, apologize? Must be something fishy going on down there. Wonder what is going on down there. Any sign of Gildy yet, Floyd? He'll be here. You, P.D., and the Chiefs stay here in the back room. Is that the big song publisher in the chair? Yeah, that's him. I talked him into a massage so I could keep him longer. I got five towels on his face. Good. Good thing he's got a long nose or he couldn't breathe. Here comes the Commissioner. Hey, Commissioner. Hello, Floyd. I got your message. Come on out, guys. Let's all get around the chair. Hello, Gildy. What's going on here? Yes, what is going on around here? Just stay right under the towels, Mr. Customer. Look here, Barber. I've been under here 10 minutes already. Well, I'm giving you a deep massage. You've got to wait for the skin to tender up. But I... Five more minutes. And to help you pass the time, we're going to do a little barbershop singing. Oh, good heavens. You may be, Floyd, but I'm not. But, Commissioner, we're going to sing your song. We even dragged the piano down here. We're sorry about last evening, Gildy. Yes, we didn't give your song much of a chance. You can sing the song if you want to, but I'm going to the water department. Well, if Gildy doesn't feel like singing, I'll sing his part, the lead. You will not, you old goat. If anybody sings a lead in my song, it's going to be me. Welcome aboard, Gildy. Okay, fellas. Here we go. There's an old familiar strain, a harming refrain that takes me back to days of yore. I see a chapel on the hill. Spring's first dapple hills reflected in the mill's hunt from the shore. I recall in names on a tree our first kiss in that old canoe. And though we drifted far apart this song within my heart is our melody of Lord Field and wonder all. Let me hold ours hid among the clouds and welcome. Okay, you're just trying to be nice to me, fellas. It's a terrible song and you know it. You know, that song isn't bad. What do you know about songs? Well, it happens. Are any good that stuff shirt crossed music publisher's bullets would have bought it? Gildy. Well, it happens that this is the first time that stuff shirt ever heard it. You mean you're the stuff... Oh, my goodness. What's the title? Title? It is not. I don't know, Gilder Sleeve, but if you get a good title for it, I just might be able to handle it. You might?  You hear that, fellas? I'm a songwriter. Now, wait, wait. You have to have a title. Don't worry about the title, Mr. Kraus. I'll find one someplace. We'll get a sizzler of a title, a regular scorcher. Gilder Sleeve really needs a name for that song, and that's why I've got great news for you. Tonight, Parquet Margeron announces a series of five weekly contests to help Gildy name his song. $50,000 in cash will be awarded to Parquet users for song title suggestions. There'll be 274 prizes each week for five weeks, and a grand prize of $5,000 extra to the weekly prize winner whose title is finally chosen. Just listen to this list of weekly prizes. Four first prizes each week of $1,000 each. Twenty second prizes each week of $100 each. Fifty third prizes each week of $20 each. Two hundred fourth prizes each week of $10 each. And a grand prize of $5,000 in cash to one of the weekly prize winners. Your entry may win a total of $6,000. And here's all you do. Think of a name for Gildy's song. Write your choice on an entry blank. They're available at your food dealers with complete contest rules in the words of Gildy's song. Or if you prefer, you can use a plain piece of paper. Send entry with one red flap from the end of a package of Parquet Margeron to Parquet Margeron, box 5167, Chicago 77, Illinois. Don't forget to include your own name and address and the name and address of your Parquet dealer. That's all there is to it. Send your title together with the red end flap of a package of Parquet to Parquet Margeron, box 5167, Chicago 77, Illinois. The contest is open to listeners in the United States, Canada, and Hawaii. First week's contest ends October 8th. So be sure your entry is postmarked before midnight of that date. And get started now. Think what you could do with $6,000 in cash. $50,000 for a name for my song, I'd have settled for less. Well, as a songwriter, I'm at least a great contest promoter. What I'm hoping, folks, is that one of my regular radio listeners will pull down that $5,000 grand prize. So get your entries in fast. They don't have to be tricky, you know. You may be surprised at the title it wins. Get in early and often. That's the big thing. Any title you think of may be the winner. Good night. The Great Gilder Sleeve is played by Harold Perry. The show was written by Paul West, John Elliott, and Andy Weiss, with music by Jack Meakin. Included in the cast are Walter Chetley, Mary Lee Robb, Lillian Randolph, Earl Ross, and Dick Legrand. This is Jay Stewart saying good night for the Craft Food Company, makers of the famous line of craft-quality food products. Be sure to listen in next Wednesday and every Wednesday for the further adventures of the Great Gilder Sleeve. Which to fewer tastes mustard that's mild, delicately spiced, or sharp snappy mustard with zing in every bite. Either way, you like craft-prepared mustard. For other of two kinds, salad mustard, tangy, but gentle, and craft-prepared mustard with snappy horseradish added. Have both on hand for different tastes, different uses. Either work magic in bringing out hidden flavor. For when you add a little mustard, you add a lot of tang. Get craft-prepared mustard. Music You're a tune for the star.


I'm hopeful that we'll start here, I guess probably now, since I just interrupted you all. So my name is Tycho Anderson. I'm here with James Page. I'm on the LexD development team. I've worked for Canonical for about two and a half years, and about two of those years I've focused on working containers, mostly in user space, although more recently in the kernel. Hi, so I'm James Page. I'm technical architect of the OpenStack team at Canonical. I've been with Canonical about five years, most of which I've been working on OpenStack. And I'm a Debian developer, Ubuntu Core developer, and OpenStack contributor. So my team is responsible for all the packaging, charms, and QA around OpenStack that we do on Ubuntu. And so today we want to talk a little bit more about something Mark mentioned, which is LexD, the peer container hypervisor, and in particular, what sort of benefits it offers you if you use it as a part of OpenStack. So one number Mark mentioned was the 14x density. We'll talk a little bit more about other numbers later. But first, I'd like to give you just a little introduction to LexD itself. LexD is one of the core tenants that it's very simple. You can use it as a building block for any project that you're involved in. The way to think of it is as an API for containers. It has lots of things like secure by default and other things. But the core of LexD is really the API itself. And so it offers a very simple way to access and create and destroy and do all the hypervisor-like operations you'd like to do with containers as a very nice and designed experience. So this API was not grown organically. But the command line and the API as well were both designed so that it's nice and easy to use. And the second thing is that LexD is fast. And James is going to talk a little bit more about some benchmarks that we have prepared for this summit to just give you a little idea of how fast it is. So I don't want to steal all of its thunder, so I'll just leave it at that to say that LexD is very fast. And finally, LexD is secure. So we use all of the available kernel security primitives today in order to make sure that your containers are isolated from each other and that they can't attack the host or do anything nefarious. And so the point here that I want to make is just that we use everything that the upstream community knows how to do today to make containers secure in order to make them secure. The last thing that I'd like to do is position LexD. When people think of containers, they typically think of application containers like Rocket or Docker. And we at Ubuntu really enjoy using these tools. The innovations they bring, in particular around image management, are really fantastic. But there's also another set of things here, the more traditional hypervisors that you think of, VMware, Hyper-V, those sorts of things, which do the full hardware virtualization. And kind of where LexD fits in is with these down here. Although it's not a full hardware virtualization, and in particular, that's what gives it all of the advantages, the performance advantages that it has, it looks. The API looks and feels. The toolset that you have looks and feels like a hypervisor. And that enables you to do hypervisory things. So you can do things like take snapshots. You can do things like live migration and other things that you expect to be able to do with a hypervisor. This is a traditional virtual machine experience. The thing looks like a machine. I think James and his demo later is going to log in and look at the syslog and other things. All of these things that you expect to be able to do with a machine. So your users are not confused. They perhaps don't even know that they're using containers. But here you are getting all of the performance benefits that we're going to tell you about. And with that, thanks, Tyco. We're now going to take a look about how we've used LexD in the context of OpenStack. So this is LexD as a hypervisor for OpenStack. So first things first, this is a complimenting technology. We're not saying you have to run your entire cloud on LexD-based containers. This should be part of your cloud story in a hybrid cloud. So alongside KVM, VMware, and Hyper-V, LexD provides an alternative way to provide machine resources as part of your cloud story. And LexD fits in to OpenStack just like Libbird and KVM does in an OpenStack deployment. So what does that look like? Well, it looks just like using the Nova API or Horizon, which we'll look at in a minute as well. So you've got all the standard operations, boot, reboot, stop, delete. You can associate floating IPs. You can make snapshots. You can do resize operations. You can do migration operations. So these containers, when the LexD containers, when they're part of an OpenStack deployment, feel just like a KVM instance from an end user perspective. It should be a familiar experience. And as a result, all the tooling you already have that works with your KVM virtual machines should also work with a LexD container as part of an OpenStack cloud. We also are able to manage resources. So in the same way as when you boot a particular flavor under KVM, you get a fixed number of CPUs and memory and disk resources. You get exactly the same in LexD. So we can constrain the containers to ensure that they have the resources of the flavor that they've been booted as. And that's exposed directly down into the container. So the container itself, when the process is running, they can tell they've got 2 gig and a core or 16 gig and 8 cores to actually consume so they can configure themselves appropriately. And we'll take a little bit of a look of exactly how that works in a bit in the demo. You can also migrate containers. I've touched on this before. So we can shift our workloads around. So if we do feel that a container needs moving off a very highly contended host, it is possible to then migrate that off to something that's a little bit spizzy. That allows us to have the migration features that you typically find in a KVM-based cloud, but also in a LexD-based cloud as well. So we can move those workloads around if need be. So let's dive into that demo and see how this goes. OK, so we've got a LexD OpenStack cloud deployed. It's the one that we did our benchmarking on, which I'll talk about in a minute. It's just a small 4.0 cloud. And you can see, let me just dive in here. And it's now going to want me to log in. I logged in too early. Apologies. OK, so we can see we've got three LexD-based hypervisors in this cloud. They've all got 24 cores, so relatively reasonable performance machines. We have deployed a workload onto this cloud, and we've done that using Juju, our service modeling tool. So we've used the OpenStack provider for Juju, and we've deployed one of our reference big data bundles, which includes Hadoop, Spark, and Zeppelin, onto that cloud in machine containers. And if we drill into this a little bit, we can see that we have multiple services all related together, all running on individual machine containers, which we'll dig into in a little bit. We pop back to our Horizon dashboard. We can see all of those same services. We can see the instances that are actually running them as well. So these are the actual machines. And you can see their specifications as well that are running that service. So let's hop on to the terminal and take a look at that as well. So this is the Juju command line. It shows you exactly the same information as the GUI, but obviously in a command line consumable format. So we can see here that we've got multiple compute slaves in our big data deployment. They're all ready to go. You can see that they've all been deployed and they're booted and ready to start running workloads. You can see all the machines that are supporting that. And again, we can focus. I've got a little bit of lag here. This cloud is on the Isle of Man, so it's a fair way geographically from here. We can see all the Nova instances running, and we can do the kind of operations you'd expect to be able to do on those things. So we can pull the console log. We can see the log from when the machine booted. We can do all the standard operations. And we can also log into these machines. Just to demonstrate that this feels like a full machine container, we can see this is a 4GIG machine. You can see that it's got its own process stack. We can see the processes that are running for this machine container. It has init, it has syslog, it has cron, it has all the features you'd expect from a full system. And just prove the process a bit as well. Got a couple of calls this machine. So we're able to restrict those resources to allow the container to run in a very specific configuration. OK, and just to prove that is all functional, I'll also just run a quick reference on there. So this deployment is running Spark. So we're just running the SparkPy sample application, which uses the big data cluster to very quickly, to not a very large number of figures, crunch the value of Pi. It does that in a random way by looking at circles and throwing darts and stuff I don't particularly understand. But anyway, there's calculated Pi. It's used the resources in the cluster underneath. And it's given us the result back. So that's the end of my demo. So if anybody wants to try this, we've got to bundle up on the juju-tomstore. Needs about four physical machines. Gives you three compute nodes and a control node. And you can try this stuff out for yourself. OK, so that's lexd and over lexd. That's the positioning piece. That's how it all plugs together. That's the vision. Let's look at the reality of what a workload looks like from a performance perspective between lexd and KBM. OK, so let's just talk about the reference platform a bit. OpenStack Liberty on Ubuntu 15.10. It's Ubuntu 15.10, not Ubuntu 14.04, because that's our primary development focus for lexd right now. Lexd is coming to 14.04. That's work in progress and should be completed in the next couple of weeks, at which point you'll also be able to consume it on our current LTS release as well. They're four unit clouds, one control node, three compute nodes, 24 cores, 48 gig of RAM, and KBM or lexd for a hypervisor. But these things, two clouds running at the same time, completely identical. So the first benchmark we looked at was Azure Terrasort Benchmark. So Terrasort is a pretty industry standard benchmark for big data workloads. It generates a number of rows of random data and then sorts those into order. And it's a fairly standard measure for evaluating big data processing performance. So we looked at that in three contexts to evaluate how the workload would perform, both when there was nothing else running on the cloud and when there was contention happening on the cloud. When there's nothing else happening on the cloud, the performance between KBM and lexd is very comparable. The bars are not particularly different. But what's interesting is when you start to get more workload happening on the same underlying physical hardware and get contention between those things, how lexd performs compared to KBM. So you can see from the graph I've got up that when we added more underlying units onto the cloud and added extra work going on in the background alongside the Terrasort, that we had a pretty consistent performance story from lexd. It pretty much took the same time, however much extra load we pushed onto the cloud. But with KBM, we did see some degradation. So the reason for that is that all of the processes when you're running on lexd are running on a single kernel, single scheduler, same file system cache is getting all the optimization that we can deliver by not having multiple kernels full virtual machines running. Under KBM, you obviously do all have all of that overhead. And the cost of switching in and out KBM machines on and off processor is relatively expensive. So when you get a lot of that going on at any given point in time, you do see this type of performance degradation. So it's a great story for lexd in terms of how it manages that contention. And I think that emphasizes if you've got a busy cloud with lots of busy workloads, then lexd is a way to squeeze more out of the same physical resources without seeing the same levels of contention. The second benchmark we looked at for this talk was a Cassandra benchmark. So there's a talk called Cassandra Stress that allows you to exercise a Cassandra cluster in various different ways. And we looked at right performance specifically. The configuration we used was 200 threads running at any given point in time, performing about 10,000 operations on a three-unit cluster. So just a single unit on each of the underlying hypervisors. And that produced some interesting results. And I didn't believe it to start off with. So I tore all the clouds down, redeployed them, revalidated everything we've set up and ran them again. And this is where we do see a big performance difference between lexd and KVM. So this first graph is about the latency of every ride operation. So the average latency under lexd was about 30 milliseconds per ride. And under KVM, it was about 105 milliseconds per ride. This workload is lots and lots of small IO from multiple different sources all at the same time. And we do see under lexd much, much better performance. When you have this high number of context switches happening on the network and disk all the time, we see this type of latency difference. And that does translate into a very big difference in throughput. So maybe 3,000 rows a second under KVM and almost 16 and a half thousand rows under lexd. So there's a great story there for workloads that are doing lots and lots of small IO, whether it be disk on networks with lots and lots of riders. There's a real big difference there. So it gives you a bit of an idea about how lexd stacks up from performance perspective. So what's up next? As Mark detailed before, we're working towards Ubuntu 16.04 which is our next long-term support release. The plan is that lexd and NOVA lexd, our driver for OpenStack, will be production grade about in six months time. They're consumable now, recommended for testing and evaluation. We want people to start consuming them now and give us some feedback on them. But we've got a few things to finish off. So although we can do resource management right now, it's a little bit crude and we wanna improve that and make that a much richer experience so that we can expose more of the resource control semantics of OpenStack down into lexd containers. So that includes improved CPU control and storage control and network quasi-control as well. We've got some additional options coming along for underlying storage containers. Right now we support LVM and butter FS as backends for the container root file systems and that allows us to use the features of those storage technologies to do things like fast cloning of machines and stuff like that. You may see in some announcements that Ubuntu 16.04 will include ZFS so we will be adopting and testing with that as well. There's a few more pieces to do around live migration which Tyco can talk to in a little bit of detail to allow that to work fully and securely across the board. Okay, so that's our presentation. We've left a good amount of time for questions. We thought them probably a bit for you. So if any of us have any questions, please fire away. Yes. What tools do we use for benchmarking? So the way we deploy the workloads is the juju and juju exposes a feature in charms called actions which allow us to run operational maintenance commands but also to do things like benchmarking. So for example, the big data bundle includes actions to run TerraSort. So it's relatively easy to execute the benchmark and then grab the metrics back and Marco Keppi, who's one of my teammates is going to be talking about our benchmarking story and how we're using that both across private and public clouds. 1150 today. So we've got a story on how we do now and we have a framework for pulling all that data together and that's broadly how we've done this benchmarking as well. Other questions? Yes. Sorry. No, those guys are still hard at work. This is, I think, just a different take on how to do machine containers and that sort of thing. So really the idea, as I mentioned earlier, is the core of LexD is, this is a particular implementation using LXC and Linux containers but the core is really the API, the experience you have while using that. That's what we want you to take away from this. So in principle, it would be possible to implement LexD back end using open VZ containers. So, yes. Yes, so LexD is, it's developed upstream, so github.com slash LXC, LXD. The way to think of it is LXC is really basically a C API with a few command line tools that call into that C API but they expose a fairly low level view on that and so what LexD does is it adds a daemon so it's written in go but it uses the go LXC binding to just call that C API. So LXC, the LXC that you've been using for years is still the thing that's actually doing the container management and managing the C groups and setting up all the bind mounts and whatever the VEs and everything. And LexD is really just basically a thin layer on top that exports a nice API that calls down into that particular binding. There's also a reason to have a daemon to do things like live migration and a few other bells and whistles that you can add. There's commands in LXC, there's the LXC checkpoint command so you can kind of fake it but LexD is really the, to give you a nice view on that, yes? Yeah, other question? Yep, yes, exactly. So the LexD resource management story will be much improved come 16.04. Right now we have very basic controls for CPUs. I actually don't think you can do pinning today. We have basic controls for memory but it's all implemented under the hood through C groups. But the idea is actually here that the way that it's expressed in LexD is platform independent. So if something else comes along, for example, if you were to do an open VZ implementation and they have their user bean counters as the underlying implementation, you could take what the language that LexD uses and describe it in that format. So yes, the way we implement it today is with C groups and like I say, there's a specification, I think we've done an internal review and it's a go so I think we'll be posting that shortly but there's also a mailing list discussion thread that we had about four months ago just asking for user feedback about what sort of limiting you would like to do. So if you're interested in that at all, we'd love to hear from you, so yes? So, is that a question? Yes, so you're asking, can we expose the block device to a container? Is that your question? So this is tricky. There's a problem. The kernel, so the way the kernel does amount is it reads the first few however long on the block device and then tries to parse the super block and stuff like that. The super block parsers in the kernel have not before been considered safe to arbitrary input and so there's an issue where if you write some garbage to a super block and then the kernel tries to parse it and there's an exploit, bam, you have a kernel root. So it's kind of tricky. We have a guy, so the good news is that Ted So who is the maintainer for the X4 file system has said he would consider any bug that was some security exploit like this to be an actual bug in the parser and he would fix it, which is great. Not all file system maintainers in the kernel have said that. There's also a patch set by a guy on our kernel team to enable mounting of X4 file systems from within user namespaces. So this is ongoing work, but the story is still progressing, so yeah. Does that answer your question? Okay, great. Just to take a slightly different take on that. In the same way as we have local LVM and butterfs storage options for container root file systems now, we have talked about the concept of using Ceph block devices, remote Ceph block devices and the features of thin copy-on-write clones to provide that. That's thought and conversation right now rather than reality, but it's. Yeah, it's possible, but not arbitrary mounting of a block device into a container. That's the piece that Tyco's talking about, but we could through LexD have a storage backend that was Ceph-based to provide those root file systems. And I guess one final note is that we've also talked about having some API where users could potentially ask LexD to say, hey, I trust this block device. Can you mount it into this container at this location? So we have a feature where you can pass mounts into a container, so it'd be something like that. This is all, the real thing I think is to fix the super block parsers in the kernel, but that is like a process, so. Yes? Yes, so I hear, yeah. I intend to have a conversation with Sage this week about. He mentioned it, he's talking about that. Yeah, and exposure of storage via something like Manila, via the mechanism that Tyco just talked about, so being able to present a file system and then have LexD present that to the container rather than it being presented directly in the container is something that we are looking at. Unfortunately, the Nova API doesn't have semantics for that yet, but that's a different challenge. Other questions? I mean, once? Twice? All right, thank you very much.


During a recent interview, CNO discussed the importance of teamwork and trusting your shipmates to help eliminate sexual assault in our Navy. I think it can increase the trust of your shipmates by, first of all, respecting yourself and respect others and demanding that.  That's not the case. This is real and it is happening in the fleet. So we need to intervene. We need to have the courage to stand up and say enough of this and get rid of sexual harassment. It's an underlined and contributing factor. For more information about sexual assault prevention and response, visit the Navy Sapper Program website. From the Defense Media Activity, I'm Petty Officer Tyrell Morris.


Hey everyone, welcome back to Nintendo Prime. We have an amazing video for you today for big stories to talk about. One of them that's very near and near to my heart. So this is gonna be really cool. I mean, we literally have news like about Zelda's 35th anniversary beyond the Game & Watch. Can you believe that? Nintendo's actually giving us more? Maybe? Beyond all of that, we obviously have updates to the NPD and a whole bunch of stuff to go over. Metroid Dread sales, Switch OLED sales. Let's get into all of the amazing news here after I remind you guys to one, drop a like on this video, baby. If it gets to a thousand likes, we'll have a giveaway for one person to win down in the comment section. So there's that. We also have our Prime Giving event happening on October 28th. I'll put a link to that event down in the description and the pinned comment. By the way, to even enter into the Prime Giving event which involves winning a Switch OLED bundle, a bunch of other people are gonna win other prizes, games and accessories and all this stuff. Also, beyond that stuff, we also are gonna be doing $100 to charity. It's gonna be a lot of fun, a really great stream. But to even enter in any of it, you have to be subscribed to the channel. So hey, why not drop a sub and all of that? That being said, let's get into the news today. So our first story is just revisiting something that seems to be an ongoing issue. I'm not sure if we're gonna continue to talk about it after today, but it is still relevant today. And that is about the GTA trilogy that came out on all platforms and is a bit of a hot mess. We all know about some of the character model issues and glitches and just weird things that have been happening in all versions of the game. Obviously the Switch having the worst performance issues although all versions seem to be having performance issues. A lot of people are really coming out, including people who are game developers and saying that this kind of looks like a rushed job which when game developers are calling it a rushed job, that's very rare that that happens. Fans always say, I'll argue, oh, this game is rushed. When game developers are saying it is, it kind of, yikes, but there's a few things that we learned because the game's out now and been datamined and all that, a couple of things is, well, the first thing is that the game cut out a bunch of music, all the music's actually still in the game. All they did was implement a line of code that disabled certain tracks, but technically modders could obviously go in, get rid of that line of code and you can pretty much have all of the music back into the game. So obviously this is usually due to licensing agreements and not being able to renew licensing agreements, but still that is something. What I found really interesting though are two other things happening with this game. First up is something that was found in the code. A comment, now, comments for the people that know are where coders can leave comments into like, they're basically remarks about what code does in the code base without it actually being code.  So, we'll just show the text and place the blip at the beginning of the mission, which is not how the mission, doesn't sound like that's how that mission was supposed to work. And we're not really sure who they are. Rockstar usually isn't gonna use the word they to refer to themselves. So it could be another company that worked on these games in the past, messed things up really bad and the code doesn't work. I don't know, but to see this comment thrown in there is like, damn, like whoever was working on this bit of the game was not happy with the way it was coded. That is for sure. And their work around for it is basically a Band-Aid job. It doesn't actually fix this particular quest in the game. It just kind of band-aids it and makes it work in a different way that was not intended. So probably because it would have took them a lot longer to rewrite the whole quest. So, yeah, beyond all that, it's not, it gets worse for GTA trilogy. The PC version of the game has actually been temporarily removed as has the Rockstar Game Launcher. So a lot of these companies are starting to do their own game launchers on PC. And Rockstar hasn't had too many issues with their game launcher until this game came out. Now it could be due to the demand for the GTA trilogy that's leading to their launcher having issues. But the thing is, the GTA trilogy itself is not only equally broken on PC. People were having a hard time even connecting and doing different things in the game that required being connected. It just, it was a hot mess. So the games were removed and the launcher's been removed. Now I heard the launcher is supposed to come back at some point today, although there's no real estimate on when they're gonna have the GTA trilogy back up again for sale. So yeah, this is just for such a vaunted IP from one of the world's best video game developers in Rockstar. This is just a bit of a hot mess, ain't it? And this is why I keep telling people, hey, you know what hasn't been a hot mess? The re-release of Knights of the Old Republic that just came out yesterday. Has it been a hot mess and it's working flawlessly? You know what's also seemingly working flawlessly right now? Shin Megami Tensei 5 on Switch that launched today. Granted, these are completely different types of games from GTA and you can just go play one of a billion copies of GTA 5 if you want instead. Of course you can't on Switch because of course we're not special enough to get GTA 5. We just get broken GTA trilogies. So by the way, this isn't me trying to knock the GTA trilogy too much. I'm sure plenty of you out there are actually having a pretty good time with the trilogy. Especially if you haven't revisited it since those games originally came out. So again, I'm not saying that these are all deal breakers for people but they are again, issues you don't really expect or at least we shouldn't expect when a new something launches like this. But hey, what are you gonna do? It happened. Let's move on to our next story. So Nintendo did something today that nobody really thought they were going to do although maybe we could argue it should have been expected based on what they did for the Mario's 35th anniversary because this was something they did for that. Nintendo does have an official 35th anniversary celebration and that celebration is, well, Zelda Game & Watch. It was announced back here in E3. A.J. Noble mentioned this was the only thing they were doing for Zelda's 35th anniversary. They had no other games or anything else in the works. Well, there is actually something extra happening for Zelda's 35th anniversary. That is that Nintendo has added a new official Ninja Speed Run course which by the way is peculiar when they said the last course, the final Ninja Speed Run course released last April and they called it the final course. Then it was just zipping around Bowser's Castle. That was supposed to be it. So like Nintendo not only tore a little bit of a fib which by the way they did this with Splatoon 2 as well where they said this is the final Splatfest and then we ended up having Splatfest after the fact. Maybe they should stop using the word final. They could say maybe the ending and then anything after that's a bonus. Anyways, here's the official word on this course. This is a new Ninja Speed Run course is here for a special occasion. To celebrate the launch of the Game & Watch, the legend of Zelda, a special course, Link's Lightweight Longshot, is available right now in Super Mario Maker 2 until 1121 at 6 p.m. Pacific Time. Arrow, some arrows and hit all the power blocks. Now it's not a hard course, but the point of this course obviously as you're seeing is just like all the other Ninja courses, it's about how quickly you can complete the course, not about the difficulty of the course. That's never really been the Ninja Speed Run calling card about difficulty. It's about quickness. So yeah, I'm glad that we're still getting, I guess I'll update some Super Mario Maker 2 which I think Nintendo massively underutilized. I think they even better utilized the original Mario Maker and that was on Wii U. So again, I like what they're doing here. I like the level. I think it's cool. Obviously we all wish Nintendo would have did a bit more for the Zelda 35th anniversary, whether it would have been a Lego set announcement, whether even just some new merch would have been cool. Obviously we all would have liked to see like Twilight Princess and the Wind Waker HD. We all would have loved to see anything, right? Just Nintendo acknowledging the Zelda 35th anniversary outside of a Zelda game and watch and now this Ninja Speed Run course, which one thing I also hate about Ninja Speed Run courses like this is their temporary.  Nintendo's getting more and more into the practice of temporary content. I don't like it because after the 21st, you can't play this course anymore.  It's just like removing something that we once enjoyed. Do you guys remember Mario 35? Yeah, it was a lot of fun, wasn't it? Can't play that anymore. I don't like what Nintendo's doing and why it seems to always center on the 35th anniversary, like temporary removed content. I mean, Super Mario 3D All-Stars, technically they don't print any new copies of that, although not necessarily hard to find copies. At least right now. Maybe in 10 years it might be, but damn. The MPD is here for October of 2021 and this is obviously a very interesting month for us Nintendo fans because they launched the Switch OLED and also Metroid Dread, right? Like this is obviously a lot to talk about. Now we're gonna cover a few general things about this including some stuff for PlayStation and Xbox, but most of this is gonna be all Switch related. So for starters, the big news here for Nintendo is Nintendo Switch is the lead platform again in terms of unit sales and dollar sales. They actually took this back after losing it in September after they had a record stretch of like 32 or 33 months or something like that, which is the longest streak anyone's led in unit sales. Nintendo lost it temporarily to PlayStation 5. Well, not shockingly the month before Switch OLED came out because people were probably waiting on Switch OLED and by the sales at October it certainly looks that way. Matt Piscotell, who put this information out on Twitter did note that this was obviously helped by the release of Switch OLED. That's what helped the Nintendo get the dollar sales crown by the way. PlayStation 5 actually leads 2021 in terms of dollar sales, but their systems are more expensive than Switch. But yeah, having a more expensive unit out there, having that sell really well. Unfortunately, he didn't really go into the specifics of how well Switch OLED sold, but the Nintendo Switch on a whole, the whole family of systems, led the way in dollars and units in October, taking the crown back for Nintendo that they temporarily lost for one month. And who knows, maybe starting a new streak all over again we'll have to wait and see. So I did mention that PlayStation 5 leads in dollar sales for all of 2021. The best selling game overall in the entire industry in the MPD is Far Cry 6. It actually instantly became the eighth best selling game in 2021 and was the number one selling game on both the PlayStation and the Xbox. The number two selling game was Back for Blood, which also was number two officially on Xbox and PlayStation, which is actually a really good debut for such a, you know, a game trying to follow up a legacy of an IP that they're not allowed to use because Valve doesn't wanna do anything with it. Beyond all of that, we finally get some Metroid Dread data. So Metroid Dread was at number three. Obviously we know Metroid Dread's only on one platform and it was the number one best seller on Switch. Okay, cool. But what really mattered is how much did it sell? Because, you know, the other ones, oh, it was number one and number two, but like we didn't get more exact data. Matt Piscotella gave us more exact data on Metroid Dread. Now we don't know the real raw numbers. The NPD doesn't give us raw numbers anymore, but here's what we do know. More importantly, it had the single best launch month and US tracked history for any Metroid game. Oh, it's better than just being the best launch month ever for a Metroid game in the US. Oh, no, no, no, it gets bigger than that. Dollar sales alone. Metroid Dread has essentially doubled the sales of Metroid Prime, which was the prior best selling game. So that's dollar sales, not unit sales. It does suggest it is ahead in unit sales by quite a margin, but yeah, there's a little price differences at launch, but yeah. Metroid Dread, guys. The US is one of the number, I think the US is actually the number one market for Metroid Dread. Let's just say there is a very high likelihood when Nintendo gives us their next financial update because their last one didn't include October. When they give us their next financial update, there's a good chance Metroid Dread is the best selling Metroid game of all time. I called it, looks like the NPD is leaning that way, that we are about to see the best selling Metroid game ever created. Now, how many units does that gotta be? It's gotta be at least three million. I'm hoping for four or five, but a five million would be ideal to me because that shows growth for the IP. But yeah, Metroid Dread is literally highly likely the best selling Metroid game ever made. Deservedly so, by the way. It's utterly fantastic. I think the whole series deserves better sales. So, good job, Mercury Steam and Nintendo for that. Next up, we'll get into the total top 20 in that NPD just for software in case people wanna know because people like to know what games are actually selling out there in the U.S. So Far Cry 6 is at number one, Back for Blood at number two, and Metroid Dread at number three, all brand new releases. We had Madden, NFL 22 at number four, Demon Slayer, Kamitu, Yo Yatu, the Hona Kami Chronicles. I know I probably butchered that. That's a brand new release by Sega. That was at number five. FIFA 22 is at number six. Marvel's Guardian of the Galaxy, another new release by Square Enix. That is at number seven. Mario Party Superstars, maybe surprisingly, although it did release later, much later in the month, is at number eight. I think Mario Party Superstars is gonna outsell Metroid Dread in the end, but it's also, you know, it came out much later in the month. So there was a lot longer time for Metroid to get sales. NHL 22 is at number nine. That was a new release, NBA 2K22, which does not include digital sales or any, I mean, Nintendo, Metroid Dread. By the way, those Metroid Dread sales don't include digital. I totally forgot about that. They don't count digital sales for Nintendo on these charts. So because of that, Metroid Dread being number three is already impressive and it's doing these numbers against Prime without counting digital. Like, oh man. But yeah, the NBA 2K22 doesn't have digital sales included either. At number 11, we have Mario Kart 8 Deluxe. At number 12, we have Call of Duty Black Ops Cold War. At number 13, we have Ghost of Shishima. At number 14, we have Super Smash Bros. Ultimate. At number 15 is Animal Crossing New Horizons. 16 is Minecraft. 17 is Marvel's Spider-Man Miles Morales. 18 is Diablo II Resurrected. 19 is Mortal Kombat 11. And 20 is the Legend of Zelda Breath of the Wild, man. Breath of the Wild bouncing back into the top 20 after being just outside of it last month. So yeah, really, really cool, really nice data. And I mean, this is just good news all around. So our last story is a bit of an in-house specialty. So people might not know the full history of Nintendo Prime, specifically as a YouTube entity. There was a website at one point and maybe there'll be a website again someday, but Nintendo Prime actually started out on YouTube as a podcast. We were just a podcast. We had a separate channel. It was called the Nintendo Prime channel, just like this one is. And yeah, we made podcasts. We would clip things from the podcast and do clips of it. It was basically just a podcast that was supporting the website. And it wasn't a very good podcast. I could, you could argue today's version of it's not very good either, if you would like, but it's much better than it used to be. I made a decision that I think is in the best interest of both this channel and the podcast. And we have moved our current rendition of the Nintendo Prime podcast to its own YouTube channel. That's right. We have now launched a Nintendo Prime YouTube channel that we hope you guys wanna go to and subscribe. We will have a link in the description as well as the pinned comment for people to go and subscribe to that channel. And I really hope that you do, not only because you wanna continue to follow the Nintendo Prime podcast, whether you can catch it live or you wanna watch it on demand after the fact, but I also want to be able to encourage people to subscribe so we can at least get to 1,000 subscribers, which we need to unlock all the features on YouTube. I think it's at around 100 subscribers right now. I am currently at the moment uploading back episodes. So we have 24 episodes of the new version of the Nintendo Prime podcast. I am currently trying to get all those episodes uploaded over there before we get to our fresh podcast hopefully next week. I would love to debut our new podcast next week there, but if we're lacking certain features because we don't have enough subscribers, we'll keep the podcast here until that happens. But we really wanna encourage people to go over to the new channel and subscribe. What's also nice about having that second channel is that if we ever get hacked again or something happens here, we can post some updates at the other channel. So there's other reasons beyond the podcast to maybe go to that channel and subscribe. But again, the Nintendo Prime podcast was, and I think will always remain the foundation of something that I do here on YouTube, even as I separate it out on its own. So we have a kind of a more focused nature here at this channel, discussion and news. And then obviously over there, more long form podcast content, maybe some clips of the podcast or certain topics in the podcast released throughout the week. I think that that makes a lot of sense. I think it's going to be a great way to expand the audience of just the podcast on its own and our audience here being more focused. It was a bit of a tough decision because we've been running the podcast on this channel for years now, but it also is just in the best interest, I think for everything. I think the podcast could actually see a lot of growth if it's left to be on its own, I hope.  So you don't care. But I really hope that you guys want to head on over and subscribe to that channel. And what's also nice too, is because the only thing being put up there is podcast stuff. Any notifications from that channel are going to be podcast. So it actually gives a lot higher chance that you will get notified of podcast live streams, the clips we upload, all that. So yeah, I don't know. I really hope that you guys want to go support the show. I would really appreciate a subscribe over there. Again, nothing's going to change necessarily here. We're still going to have our normal content. I am actually, I have a bit of a channel update to do, but I'm going to wait on that channel update. Kind of look forward to it later today. This is what I'm trying to tell you. I think I'm going to put out a channel update video. I just got a few things I got to sort through first. But thank you guys for tuning in, because I have more to talk about than just the podcast. I hope you enjoyed today's news. It was lovely. Who knows, maybe we get some surprise news later today and I have to make another video, but you guys are awesome. And I'm going to catch you guys in the next video.