Call all hands, speak to quarters. One broadside into it, please, Captain Bush. Point is on target. Limbs top ready. Aye, aye, sir. C.S. Foresters, indomitable man of the sea. Horatio Hornblower. Lifting clear of the horizon and blazing into my face that finally will come in. Morning, sir. We've been back round about holding our course close hold. Uh-huh. Morning, Mr. Bush. It's a miracle we can hold a course at all. Look at that ringing splices everywhere and hardly a sail without shotholes in it. Yes, sir. She looks a tattered old vagabond. But our makeshift mismaster is still standing, sir. A little furrowed and grovely shot. The sills are black with powder. There's an 18-pounder shot half-buried in that bit of tough oak, sir, and went. Nevertheless, you've done wonders. Ah, I might have done more, sir. But the members are exhausted. I had to send them as many below as I could. To tell the truth, sir, there's more dead out, Mr. Bush. All missing. They were in the launch when the David Dads shot he didn't sunk it. All the same, sir.  Six are ship of the line. Ah, victory, Mr. Bush. I shall remember to give you all the credit you deserve in my report. I shall go down and visit the wounded. You better get some rest. Lady Barbara, I'd forgotten our passenger. Is she still in there all up? As I know, sir. Ah, they do visit the sea. Well, my steward will have looked after her. If high-born ladies use their position to force themselves into fighting ships, they must be prepared to face the consequences. To tell the truth, I was a little uneasy at my neglect of Lady Barbara Wellesley. But I'd had much on my mind. Below decks in the all-up, the scene was like an inferno. It was hot and airless. And the four flickering oil lamps added their smell to the stench of bilge, powder fumes, and sick men. Here are seventy-five wounded men who crammed together, groaning and sobbing, gas-feeling and vomiting, under the care of the incompetent lorry whom I'd appointed surgeon when our own certain had died. Thank God you've come, sir.  Now come round with me and make your report. Oh, then, this man. Good heavens, Lady Barbara, what are you doing here? Good morning, Captain. I am sponging the poor man's throat. But tending the wounded is a man's job. The filthy work of a hospital does not fit for women. No, don't do that. Go away from here. Go on deck. Please understand me. I am not attempting to be noble. But there is work to be done in the King's service. And if nobody else can do it, a Wellesley must. If one of my brothers can govern India and fight the Marathas, I can do my part. Look at this man. He has a great splinter of wood under his skin. It ought to be extracted at once. Yes, certainly ought. Mr. Lorry, are you ready to extract this splinter? Well, ma'am... Don't be a fool, man. If you will not do it, I will. I'll see that it's done immediately, Lady Barbara. But please, go on deck. I shall do nothing of the kind, Captain. I am going to help. But as you will, ma'am. Now, Lorry, where are your instruments? Come and stand by to hold Williams.  But it's going to hurt you. The night which elapsed before we rounded Cape Marla was a grim period. Unfortunately, the weather held fair. Had we met Gales, I could hardly have kept my leaking battered ship afloat. Although some of the men became convalescent under Lady Barbara's care, gangrene, shock, and exhaustion was imposing upon me and my task was sliding hammock-wrapped bundles over-side into the blue Pacific. This lady's ship's conflicted, sir. Could you spare a moment to step below? Great, sir. First, Mr. Bush, I thought he was improving. So he was, sir, in spite of Lorry's surgery. But her lady's ship's worried about him now. I'll go and get her. Would you be spared? Is he conflicted? He is delirious. Do you think I'm his mother? There is your hand, mother. It's awful, darling. I'm here, darling. Don't be afraid. It's light beyond. Poor, poor boy. Lady Barbara, I've on deck for summer shining. It is not fair, Captain. It is not fair. He was only a lad. He was not ready. I had not been for you with ever to be in many more such scenes. Lady Barbara, I resented your presence on this ship if I failed that resentment in any way. I... I humbly apologize. There's nothing to forgive. Let us go on deck. You're in sight of land. Yes, ma'am. We're just entering the Gulf of Panama. The land on the Port Bar is the Pearl Islands. Is she a Spanish craft, Captain? Yes, Captain Manuel Diaz, commanding. It was this same lager that brought me the news that Spain was now our ally. And your letter requesting a passage on this ship. Oh, it seems a hundred years ago, instead of but a few weeks. And now here we are almost back in Panama, which I thought never to see again. I would prefer not to see it, ma'am, especially if the Yellow Fever still rages there. Yet, if I do not refit and provision the ship, we'll sink under my feet. She's setting a boat over there. Looks like the same officer we met before. Yes, I recognize him. Well, he should be pleased that we've accomplished our mission and destroyed the Natividad. Stand by. He's coming aboard. Good morning. Good morning, Captain. I trust your excellency is enjoying the best of health. Thank you, yes. I see from the damage and the wounded on your decks that your fine ship has been recently in action. I hope that your excellency has had good fortune in the encounter. We thank the Natividad if that's what you mean. You thank her? We did. She's completely destroyed? Yes. Oh, then, sir, I have a letter to give you. No, no, no. That is not the one. This letter, sir. Thank you. You are aware of the contents of this letter, sir? I am, sir. And I take it from your hesitation that had I not sunk the Natividad, you would have given me the other letter. May I ask the contents of that one? I have no other letter for you, sir. Indeed. And so, by this document, I am prohibited from dropping anchor or entering into any port of Spanish America, the Vice Royalty of Peru, the Vice Royalty of Mexico, or the Captain General Sea of New Granada. Can you explain this most unfriendly behavior on the part of the Vice Royalty? I would not presume to explain my master's action, sir. Whatever I think of this action, it's not compatible with the dignity of a British officer to ban the words with you about it. Indeed. I compliment your master. I will call it no port on the Spanish man. Please convey to his excellency my lively sense of gratitude at the courtesy with which I have been treated and my pleasure at this further proof of the good relations between the governments of which we have the good fortune to be subjects. And now, sir, I have much to attend to. You have my permission to return to your ship. To indulge in bitterness against the Spanish. At a pinch, I could make my stores last out until I reached Santa Lena or Gibraltar. But there was no hope of facing the storms of Cape Horn with my ship leaking and jury rigged. Still nine valums, Mr. Bush. This place seems very suitable. Aye, sir. Thanks for the job. Lucky we found this channel between the mountains. Look, sir, right ahead. It shows to have been a beach. It's golden sand, too. It'll be excellent for careening. Except for the heat. Ah, there'll be no escaping that here, sir. The mountains cut off the breeze and reflect the sun, too. Oh, it's like an oven, sir. I can't fail to respect the best of it. We're lucky to have found such a place. Now, Mr. Bush, time is important. We must work like Trojans to make ourselves secure so that the Spaniards discover our hiding place. Call back the cutter. We'll anchor here while you and I go ashore to explore. The boat is in a trot here, I imagine not. But let the escort keep a sharp look out, nevertheless. Ah, that's the last of the vegetation. Now the sharp scramble up these rocks and we shall have a view of the whole bay. Ah, as I thought, Mr. Bush, these headlands make a natural fort. There are 18 pounders up here and no ships shall dare to approach through the channel. 18? How distribute! Well, they weigh two ton of bees. Yes, rigging tackles and swaying them up here in this heat should keep the men amused until we're ready to lay the ship over and begin the serious work. See to it, Mr. Bush. The serious work? Aye, aye, sir. Night and day until we were all dropping with weirdness. When all repairs to the ship were done, she had to be loaded again. On the rigging, we rowed and set up. But when I stood once more on the deck with a staunch ship beneath me and a broadside which could fire, I was happy again and could stamp my fingers at every spanhead in the Pacific. In all these weeks of labor, I'd had no time to spare for Lady Barbara. But her smile as she crossed the deck to me showed that I was forgiven for my neglect. Give me your hand, Captain. I congratulate you on having achieved so much in so little time. Thank you very much. Captain is modestly comfortable again. You've made the ship like new. Thank you, Lady Barbara. The men have worked well. It's heaven to me to think that we're at sea again before night. You are a very fine sailor, sir. I doubt if there's another officer in the King's Service who could have done all that you have on this voyage. Glad you think so, ma'am. I've only done what you did. England is your debtor. I shall try to help see the ship's knowledge of that debt. Thank you, ma'am. Pardon me, they'll have that cast going through the bottom of the cutter in a moment. Use it on those tackles there. He was your most human for a while. If it's not more trouble, Mr. Bush, I'm finding it increasingly difficult to remain signal to that young man. Good day to you, Captain D'Arthes.  No, only to see you, sir. I congratulate you on the amazing difference in your ship since I was last aboard. How were you able to affect such repairs? I know you have not been into port. British Navy, sir, takes but small heed of such trifles as a refit. To what do I owe the honour of your visit? I wondered, sir, whether you would honour me by visiting my ship. I should be able to show you something of interest which would demonstrate our ability to continue without your assistance. What is it you wish to show me? I would prefer to surprise you, sir. I assure you, I intend not retchery. I thought so my lager is within the range and your guns could sink it with a single broadside. If you are not back safe here within the hour, your offices may open fire. Don't go, sir. I shall visit the lager, Mr. Bush. Send the cutter after me to bring me back. But today, about the surprise awaiting me, he led the way to the foredeck. There, in the blinding, scorching sun, chained by the waist to a ring bolt with irons on his wrists and ankles, half naked and wholly filthy. You have already had the pleasure of meeting his excellency Don Julián, Mariede Jesús de Alvarado y Montezuma, who calls himself... Half mad fanatic whose rebellion against the Spanish I had been sent to assist and against whom I'd been ordered to turn when the Spanish had become our allies. Bloodthirsty, despot there he was. It troubled me to see him, Lut. You're not this Captain Hornblower that I wear these chairs. It is a women of mine. Do you not think they set off my theater? Yes, they do. We, I shall mount the throne of the world. They speak of the gallows awaiting us on the bastion of the citadel. That will be the framework of my throne. Golden it will be, with diamond stars and the turquoise boots. Only El Suprema is left to govern from his golden throne. His throne. No, but he will sometimes struggle and shout for twenty-four hours without stopping. Amusing.  You're also making his peace with God. Mad or seen, sir, rebels must have. Your excellency must know that as well as I do. We are very glad you have returned, Captain. I hope the promised surprise was a pleasant one. Oh, trifle, ma'am. These simple things you know are muses, spaniards. No pain. Pardon me, ma'am. I must go below. Based on the novels by C. S. Forrester. Music composed and conducted by Sidney Torch. C. Allen Towers.


Hi, so we continue today with our reading of what is philosophy by Deleuze and Gata and Quite quickly in page two They give the answer to the question they give an answer to give a brief Concentrated formula They write philosophy is the art of forming inventing and Fabricating concepts so note here that Although they're famous for the formula that Philosophy is the creation of concepts here I don't speak about creation forming inventing fabricating in French the Formulates l'art de former d'inventé de fabriquer Okay, so this are terms that are close to creation And they nevertheless different at the same time they will of course use the term creation, but We will see how that might differ from the idea of a Fabrication for example, which is might be a Little technical and then they have this moment where they speak about Friends so There's sort of human embodiment and there Two points the first point is that They say that concepts need conceptual Personnel in French Personnel that play a part in their definition This is very Strange and very perhaps surprising for people who are who have a background in analytic philosophy or logic The fact that concepts are by some aspect of it connected to a Persona and they start by saying well the Topic of friendship the idea of a friend is such a conceptual persona that reveals that was Manifested in the Greek origin of philosophy others civilizations had Sages, but the Greeks introduced this Friends were not just more Modest Sages, what does it mean a friend? Well first of all if you are a friend of Wisdom philosophy Sophia This means that perhaps You do not fully coincide with that Understand with that knowledge that wisdom you are you have this Lover relationship with it You constantly Try to be in the presence of knowledge Perhaps you try to become one with knowledge But of course if you were one with knowledge You couldn't be said to be a friend So the idea of friendship Implies the idea of some sort of separation a close Complicity but nevertheless Not the full coincidence Does it designate a type of competent intimacy a sort of material taste and Potentiality like that of the joiner with wood Is the potential of wood latent in the good joiner is he the friend of the wood so It's interesting because in another book a thousand plateaus Do lozen get a his pick about that community of craftsman In this case, it's not the metaphor of the wood. It's the metaphor of the metal but nevertheless the idea that crafting a Material in a community of practice creates this sort of Is pretty car this sort of Complicity of friendship that comes from the fact that they are They have this shared Cosmology which uses some form of material element now One could say philosophy is not material, but nevertheless, we will see that Do lozen get a compare The concept to an aerial light We'll come back to that but basically they compared to a flying Meteor So there's this element. There's an element of Solidity in The philosophical concept, but it's a flying solidity, of course With the creation of philosophy the Greeks violently force the friend into a relationship that is no longer a Relationship with another but one with an entity An essence an objectality So we mentioned that point yesterday. What does it mean to be the friend of abstraction What does it mean to be the friend of concepts? Well If we agree with Maître a car master Eckert medieval Thinker that we become what we love If you are a friend of the concept You part of you becomes itself Concept and they they speak of a transcendental lived reality So this might mean that the The philosopher is someone that is lives in between the concept and Empirical existence by introducing in him or in her Some elements that are not Elements of flesh But at the same time by bringing into life by bringing into existence by bringing into the realm of flesh the abstract reality and Although the lesson get a he professed that they didn't like Hegel here Again, we will come back to that but here it sounds a little bit like the deployment of the concept in history that Hegel has spoken of What does friend mean when it becomes a conceptual persona or Condition for the exercise of thoughts, right and they speak of the lover the friend And of this idea that There is an element at least with with the Greeks there is an element of agonism, right that there is this rivalry of free men a generalized generalized athleticism The agon so it's not the it's not the full antagonism but it is a form of competitive emulation that Recognize the integrity of the essence they write and the rivalry of Claimance so the idea of friend and The Greek beginning of philosophy Supposed that philosophy is both an individual relationship with Entities that are not Human or not fully human but also a collective endeavor Right it's this idea of the dialogue so the question we will Ask and we will end here because again, I want to keep each episode around 10 minutes Can we do philosophy without being part of a community of Friends of the concept that's it for today and we'll continue tomorrow


Live from Las Vegas, Nevada, it's theCUBE at IBM Interconnect 2015. Brought to you by headline sponsor, IBM. Hey, welcome back everyone, you are watching theCUBE. This is SiliconANGLE's flagship program. We go out to the events and extract the civil noise. I'm John Furrier, the founder of SiliconANGLE. I'm sure that my co-host, Dave Vellante, founder of Wikibon. Our next guest is excited to be here. We're excited for her to be here. Jamie Thomas, GM of the storage and software to find you with an IBM. Great to see you, welcome back. Yes, thank you. It's always good to talk with you guys. We always say, we want to make people feel comfortable with people. Whenever you're around, we always feel comfortable.  I always enjoy the talks and have a great time. And storage is one of those topics that is so fun to talk about because it's the center of the value proposition. Some may not think that's the case, but we like storage. So a couple of things. Storage and software to find is certainly the middle of the action. A lot of opportunity in data center. Clouds, storage and data is always growing. See that, analytics. We're talking about people are drowning in data. That's a big problem that's been part of the conversation. What's going on?  What's new? Well, I think you're exactly right. These tectonic shifts have really driven storage in a new direction. It's really time for a modern storage infrastructure, if you will, to really support this more effectively for clients to get the benefits and the economic returns that they want to have. And so last year, as you recall, we spoke at last year, we really embarked on this journey around to focus on software to find storage and flash. And really the impetus for us was to create a landscape where through intelligent software, we can enable clients to really get more effective storage management and optimization. And we firmly believe that the new hardware form factor in the future is flash because it not only returns benefits to our clients from a performance perspective, but it also solves a lot of operational problems around space and energy consumption. But last week, we made a critical set of announcements on this journey to software to find storage. And we announced a new family of offerings called IBM Spectrum Storage, all software to find offerings that really allow our clients to both manage heterogeneous storage hardware environments but also optimize these infrastructures of the future, if you will. And what do you mean by optimizing? Tying into, integrating, unifying? Well, we have three main capabilities we think about in terms of optimization. And really the key difference here is we really unleashed the software from the traditional hardware-based appliance, if you will, allowing clients to deploy these capabilities as software with hardware as an appliance, if that's what they want, and also on the cloud, on software in a pay-as-you-go model. But the three capabilities are, first and foremost, virtualization, which we've had for a while, the ability to virtualize storage environments and really improve the efficiency and utilization of these environments, which in many cases are highly underutilized. The second capability we actually did ship last year is called Spectrum Scale. It's about being able to support big data and analytics environments and do that in a cost-effective way, but whether you're doing scientific computing or just simply managing data that really is maybe for an SAP supply chain type application more effectively. And then we announced a new capability which is absolutely critical for cloud-based storage called Accelerate. And this is where we've extracted the software intelligence from our XIV appliance, which is a very popular appliance worldwide. It's used by over 100,000 different server implementations and with clients like Netflix. But we've really abstracted the software layer, and that allows our clients now to deploy this capability in a matter of minutes instead of what was months in terms of getting the hardware appliance into their data center and connecting it into the network. It's also allowing them to make use of the commodity-based hardware that they've got so they can manage their hardware life cycles in a different way. And it comes with all the benefits that that appliance came with, frankly, from an ease of management that's manifested in the software itself. Yeah, so a year ago in the summer you guys announced sort of the direction. Yes. And now the spectrum is really the culmination of that. Yes, absolutely. At times like virtualization, there's a little GPFS. Yeah. The ease of use piece I didn't really get at the time, but that's really coming out of XIV. Yeah, yeah. And now it comes together.  It's clear that this is the future. What does that product look like? And you mentioned sort of pay as you go. How do you sort of package that for the marketplace? Well, I mean, if we look at our new product, Spectrum Accelerate, we're first and foremost delivering it as a new software offering which will be orderable and have all the licensing terms like all IBM software. So it'll go through that ordering system. But then some of our clients will choose to also continue to buy the asset with the fit for purpose appliance model. But in the case of our cloud-based pricing which we'll announce later, the clients will be able to buy in a terabyte-based pricing model but in a pay-as-you-go model. So they'll be able to ascertain what they need. And on a monthly basis, basically purchase the storage that they need. And this will allow our clients to have a lot more flexibility. And we actually did that with our scale offering last year on software. And we've gained a lot of experience for how clients want to purchase that type of capability. Well, and clients have been sort of hinting that they're going to be demanding that for. And now they're starting to demand it. Do you see that? Oh, yeah, absolutely. You know, I think a lot of our clients are still trying to understand what their data, lifecycle management policy will look like, where they will actually have data today and in the future. But first and foremost, they need to have flexibility of choice. So whether they choose to have this data on-prem or off-prem in the future, we believe we have to provide a storage architecture that allows them to do that easily. And you mentioned heterogeneous before. That's, again, if we go back to the heritage of the sand volume controller, SVC, and store-wise, and now it's integrated into Spectrum, that was everybody else's storage, and IBM's storage. It was anybody's storage. So that's not just lip service. That's something that you guys have always- Right. We support more than 260 different hardware storage devices. And that's the foundational element of both our virtualization capability and our control capability, to build so you manage a very heterogeneous environment. So you've backed that up. It's kind of the heritage. You will go to market and say, okay, whatever storage you want to put on there, great, if you don't want to buy the appliance model, go for it. Yeah, exactly, exactly. And a lot of our clients, when we embarked on this journey around unharnessing the software, if you will, the software intelligence that was resident in the XIV appliance, some of them said, I have hundreds and thousands of commodity-based servers already in my enterprise, and I understand how to manage the high availability aspects of those servers. So if you provide the software to me, then I'll have the flexibility in terms of how I deploy that on the hardware. And that's really the genesis of why we did this. But give them choice. They want- Give them choice. And they wanted to then use that in what context, mix and matching across systems, or just between applications and work loads or both? It allows them to deal with this dichotomy between CAPEX and OPEX, to also be able to manage that hardware lifecycle independent of having it attached to this appliance for life, right? Well, yeah. When I think about the storage business for decades, it's been, here's a box. All the metadata is locked inside that box.  And if you want to migrate, good luck. And essentially, you're taking a different approach. Again, as a software executive, are you kind of struggling to say, well, why wouldn't you do it this way? I mean... Well, I think that if you look at it from the perspective of our experience with middleware, databases, application servers, and things like that, this is really somewhat no different, right? It's about providing the capability of software, then allowing customers through a prescribed set of best practices to understand how to deploy the capability. But we had great experiences with our beta program. We actually started a beta program of this product last fall, and across financial services, energy concerns, service providers. We had a variety of experiences. In many cases, these clients did get the beta, and they had it up and running in a matter of like 30 minutes. So it was really a good experience. And what were they installing? It was a software? They were just installing software on the hardware that they already had. And they brought their... They brought their own hardware? They brought their own hardware to the table. What else did you learn in that process? I mean, obviously, there's little bugs here and there. You're working that out. Oh, yeah, absolutely. I mean, well, that's the advantage of a beta, right?  They gave us a lot of feedback about wanting to have a central dashboard. So we have a dashboard that really manifested what we already had with the appliance. But now we can, certainly we run it on mobile devices or the form factor that they'd like. It's a dashboard that allows them with a glance to see the performance of not just only that particular appliance, if you will, but if they, in the future, have it running in a hybrid model, they'll be able to see the performance of that entire infrastructure. So for customers that aren't in the weeds on all of the nuances, and they're just dealing with their operations, yeah, the cat-packs, the hot-packs thing going on. What's the message to the CIO and the folks in there about the new approach? Is it choice? What's the high-level message? And why should they be paying attention? And what does it mean for their business as they go forward in terms of their journey with data center, private, hybrid, and public cloud? I think there's two main things. It's about flexibility. So many of our clients don't exactly know the model that they will use for particular applications or workloads today, where the data will reside. So they need to have the flexibility for the future to make the right choice in the future, and economics. I mean, this does change the economics equation in many different ways. It simplifies the acquisition. It simplifies how you're able to use what you've already invested in from a hardware perspective. It really changes economics, I think, in a big way. So when you came into the division, obviously you do what any executive does, you sort of learn what's going on, you do your deep dives, but then you have to place bets. So it sounds like you're placing them on software defined and flash. Yes. We're placing those bets, and we're definitely taking advantage of flash capability, not only within our flash system product, which I know my colleagues will talk more to you about today, but we're also infusing flash into our existing product lines. So our high-end storage, we shipped flash enclosures last year. So we think flash is a dominant hardware form factor for storage going forward. So yeah, we're placing these bets. How does it, specifically with regard to spectrum and software defined, how does it change the sort of resource requirements that you have as an executive, the skill sets that you need? Where do you, obviously, big company, can you talk about that challenge as a head of storage? Right, well, we made some important organizational changes earlier this year, where we actually brought together the storage capabilities that were in our traditional hardware unit with the storage capabilities in our software unit, and now we're in the integrated unit, and that also gives us the advantage of an integrated sales force. And it brought a lot of software skills to our business, where we now have a worldwide storage software sales force to enable us to embark on this agenda. And I think it's important to note that even with our flash offerings, the value of those offerings have largely always been about the state of innovation around the hardware engineering, combined with really, really good software engineering in that box, in that system. Well, it's interesting because I would imagine that most of the engineers in the hardware groups these days are software developers anyway. Yeah, there's a lot of software in everything that we do, absolutely. So the competition is always out there doing their thing. They always say, power the portfolio. I think you know what I'm talking about. So EMC, for instance, they always talk about the portfolio of storage.  Big data's huge, gotta be storage. What are the key things that you're looking at in terms of new ground to take for the storage group? Obviously, you have the old spinning disk, you got flash, you got tape out there.  What is that next wave for you guys? Well, I definitely think that there's a tight integration that needs to occur between the storage layer and many of these killer applications, if you will. And so to that end, last year, we integrated and we shipped our software-defined storage with Big Insights, which is IBM's Hadoop-based distribution. We also see a lot of value with software-defined storage to improve the performance and economics of things like enterprise content management systems. So I think that there's a number of ISV applications and other what I call killer applications that are in this information management and analytics world where this marriage of software-defined storage is going to be critical, the marriage of the two assets together will be critical, create solutions, exactly. So the marketing buzzwords out there are Data Lake. I introduced the concept of data ocean, which is getting a lot of traction, trending on Twitter. Lake seems batch. It seems like it had big lakes. You have Lake Tahoe. The waves can be as high as six feet, but the ocean's different. Dynamic, that's more real-time. So some say it's web-scale, it's got unpredictability. That's the new data model that the future's around the corner. What do you think about those two terms, Data Lake? What does that mean to you? Is this data fabric that's going on? Because that seems to be where storage software is getting a lot of action in terms of where people are making bets on. Software-defined storage and software systems are all about managing low-latency data, bringing it from the data warehouse, putting it into real-time. You guys got some amazing in-memory stuff happening. So software's going to be smart, but also it's going to move data around. Well, I think one of the key factors that a lot of our clients desire, though, is the ability to extract intelligence from this data without moving it around. Because moving it around really is taking up an incredible amount of network bandwidth. I've been in meetings where the network guy's saying, wait a minute, this has got to stop. So... You mean the data moving around? Yeah, the data moving around is taking up enormous bandwidth and actually slowing down the processing. Is that the approach? Well, the approach we took with our scale product is really about the ability to ingest the data wherever it resides, right? So the ability to access that data, whether it's on a disk-based system or a tape-based system and do that in a seamless way. And we created that approach and that really was derived from investments we made over a period of years to power things like Watson, right? It's incredible ability to ingest data, gain insight from it, which, as I said before, is valuable in scientific computing and there's many examples of that in life sciences and things like that, but also in just applications where there's a huge amount of data that's perhaps going through a supply chain, like an SAP application, right? Well, that's your file system expertise that allows you to do that as a critical piece of what you're doing now. Okay, let's look out nine to 18 months. What do you want to accomplish with this group? What should we be watching as observers? Well, I think that our key focus right now is working with our clients to make sure they get value out of what we've announced. We've announced a very rich set of capability in both software to find and flash. We want to enable our clients across many industries to get what we think are enormous benefits, both in cost savings and business performance. And today I talked about some really cool examples of that in my presentation, both in the gaming industry and in the insurance industry and that's really going to be a big part of our focus now that we've rolled this out. Now over the year, we'll continue to evolve the spectrum storage family. We intend to deliver a cloud-based gateway capability which we announced in alpha form and also some additional analytics that we'll be shipping on top of software later this year. So the family, the beauty of this, the family is because of the way we've designed it, we can more easily ship capability as it gets through its beta test and is ready to go to market, we'll be able to pull it down. So spectrum is the family name, right? Spectrum is the family name. Marker behind that, more software defined. And make customers choose is the key strategy. Yeah. Okay. And it scales, layering, I'm hearing layering features and functions as you go on. Now I have to reinvent the wheel every time. Exactly. Slow down R&D. Yeah, we really are wanting to, one of the things we know we needed to focus on was agility, right? Agility, but with the right meeting the expectations of our clients in the same time. And so this agenda is really all about delivering the code as early as possible to them, getting their feedback, turning the crank on it and then getting it out to clients when we think it's ready. So does the software awake the sleeping storage giant inside of IBM? What's your? I think that IBM is all behind storage. They're really across the geographies across all of our client and our sales teams. I think it's really renewed the focus on storage and really brought to the forefront of everyone's mind how important it is for the infrastructure of the future because it really is key. It really is key to cloud as well as big data and analytics. It's really, really key. It's a center of the value problem. Yes, yeah. The last question to end the segment is for the folks out there that storage is top of mind because it really is front and center and it's really in the center of the action and conversations. What should folks know about IBM that they may not be paying attention to what you guys are doing with storage? What's the message to the folks that they share with them the bottom line, hey, hit the shakes, hey, what's going on with IBM? Tell them what's happening. Well, I think first and foremost they need to understand that we are really serious about this agenda and that we are investing enormously. We announced a billion dollar investment in software to find storage but this family encapsulates and ships more than 700 innovations and patents that we've created over a period of time and that through the investments we made in our applied research laboratories which are critical for things like Flash, this is an important endeavor for us and we see it as an important part of our overall cloud agenda. Whether it's a data lake or data ocean, storage needs to be in there. Jamie, thanks for coming on theCUBE. I really appreciate you. It's great to talk with you again. Thank you, congratulations on the new staff. We're just looking forward to talking to the Flash, your new Flash guy Eric in a second. This is theCUBE extracting the signal, storing the signal, sharing it with you. It's on demand, it's live with theCUBE. We'll be right back after this short break.


Last session of the day, never good. Last session of the day on the last day of the week. Last day of the sessions. All right, we actually have more content on this one than we probably have time. So I'm gonna get going here. I'm Ed Baldough with SolidFire slash NetApp. John Griffith, same place. SolidFire and NetApp.  So yes, hopefully the demo gods will be with us. So let's get started. We're gonna talk about consuming Cinder from Docker. Yeah, that's a good title, although there's some beyond Docker in there. So the first thing that everybody asks is, hey, Statler, what's Cinder? Who cares, Waldorf? He's gonna talk about Docker because every time you put a Docker in the title of a presentation, you usually get more people. Hey, where are all the people? Hey, we're gonna talk about Docker. Come on in. Tell all your friends. So if you're, we're at an OpenStack conference, so this is a little less of an importance of the slide. We usually go through and say, what is Cinder? Most of you guys probably familiar with that since it is OpenStack. And it's an abstraction layer for a pool of block storage devices. Back end, we support many back ends. John keeps quoting that there's 80 of them in there that are supported in the upstream tree. I haven't counted that, so I can't very well validate, so blame it on John. It could be 82, I could be wrong. So you can keep plugging in back ends and you can scale it out. The scheduler can figure out where to place things. It's kind of like having an infinite number of disks so you can hot plug and unplug from your instances or your containers, right? So somewhere in here, Docker made the Docker volume API. You can do things like create, delete, attach, detach, and who puts snapshot in there? So these are actually, these are the things that I say you need in a cloud. Right, okay, those are the things John says you need. Those are the only things you need, but. Docker supports the first four and a list command. The snapshot stuff is not in the basic Docker API. We'll talk a little bit more about that in a bit, but we have some ways to make that happen, so. And then there's the stuff that a lot of people want and again, we can make some of this happen. This is John being opinionated and blunt. These are other storage features that you may want. Replication, consistency groups, backup, migration, so on and so forth. You don't really want those. Yeah, maybe you want them. Some people want them. And he made the presentation, but hey, I thought this would be a Docker talk and which character was that one again? Gamzo, maybe? I don't know. Docker was the best ever geek bait and they're flocking in a few. It's, you know, OpenStack in containers. That's one way of doing it. You can put containers on OpenStack. Container orchestration around OpenStacks from Magnum and Kubernetes. There's a lot of things. I'm gonna actually try to do a mesos demo with Docker under the covers here at the end. And that's where we get the unicorns for everyone. Also driven to interesting ideas and plans. Again, we see Cola, we see Magnum. How do we use containers to deploy OpenStack? How do we have OpenStack consume containers? So on and so forth. But let's bypass a little of the hype and do some cool stuff. And so, oh you, yes, we gotta build this out. So new thing, you know, the new thing used to be OpenStack, the new thing now is containers. There's, you know, pets versus cattle, conversations and chickens.  We got chicken or cattle, which is in the cloud. And then we got chickens, which are containers. What do you got against chickens, man? Chickens live less long than cattle do, right? Less long. Less long. All right, Donald. So there's always something we need, better networking, better persistent storage, those kinds of things, different development paradigm, you know, small ephemeral services. So just like we're here in OpenStack, containers needs networking storage. And in Docker 1.8, we finally got the storage provisioning bits, right? So there's always been the ability to do storage in containers, but was there automated provisioning and that really didn't come along until 1.8. It's gotten a lot better in recent version, so it continues to mature. There's a whole circus, you can use a lot of analogies there. I'm trying to think of one that's appropriate, but we'll just say there's a whole circus around vendors and other people trying to provide plugins to rapidly fill in where this API allows you to work there. There's a lot of confusion. There's a lot of stacking. We're gonna talk about, we think it's pretty straightforward one. If you've got OpenStack, taking advantage of Cinder to get your volume services is pretty straightforward. So we'll go through that. Docker volume plugins, it's simple. Volume API, again, there's basically five commands.  It does include provisioning. So when you say create, it will go off to the back end. In this case, we're gonna talk about how that goes off to Cinder, and it will grab a piece of storage per your commands. It runs as a daemon. The daemon needs to run everywhere that you wanna consume services, so if you have Docker engine on 300 hosts, you need to run the daemon on 300 hosts. Right now, it uses a simple Unix domain socket to talk to Docker, or Docker talks to it that way. And it's JSON RPC, I already talked about that. It runs near the Docker engine. Works with Swarm, it works with Engine, it works with Compose, it works with other things that consume Docker, so like I said, I'm gonna try to do the Mesos demo and some Swarm demos at the end of this. So with that, I'm gonna turn it over to John here to talk for a while. All right, thank you. So Ed has the unfortunate pleasure of having worked with me for a really long time, so I give him a really hard time on stage, and I'm gonna continue that tradition today. I'll pass it back. Do that a lot, so. Anyway, so all this stuff's going on and everything else. At the time when I started this, and some of you have seen this talk, there wasn't really a good solution, so I created one. It was bored sitting around one weekend and said, hey, I'm gonna write a plugin. So I wrote a plugin. The whole intent of the plugin is it's written in Go. It's in Golang. Most of the stuff in Docker, Kubernetes, et cetera, is all Golang. I stuck with that mantra. And it is focused completely on Cinder, and that's it. I don't care about what's underneath. I don't have any vendor interests, anything like that, there's nothing associated with it. It is pure Cinder. It is open source. I gladly welcome contributors and feedback, and I was hoping for community support and feedback and things like that, but I'll talk about that in a little bit. I think there's some things gonna change. I licensed this under the, I don't care what you do with it, license. It's actually a thing, look it up. And it's kind of interesting because I've found a number of repos out on GitHub where people are doing whatever they want with it, and so that's kind of cool. But, so this is the part where most of the open stack development community, especially this Cinder guys, get kind of freaked out because I don't have these as part of any organization or grouping or anything like that. They are not a sanctioned open stack project, not even a big tent project. And they're not a Docker project. So they're just in my own personal GitHub, publicly available, do what you want. So, some people like that, some people don't. Those people aren't here, but there's one person I know that if he saw this, he would literally have a stroke. So, and it would have been cool if he was here, because well, yeah. So how does this all work? So the thing that's kind of cool in all seriousness, the actual point of this exercise was more to show that Cinder is actually something that's valuable outside of open stack or outside of a Nova context, right? And that was kind of the whole idea. So that's kind of what I was hoping to kind of raise awareness about and kind of get people thinking about and things. Because the reality is any consumer of storage, any consumer of block storage out there isn't really any different than Nova. We're all doing the same thing. We're creating, attaching, detaching, deleting. I mean, that's what we do with storage. So it doesn't really matter. So the whole concept and the whole idea is trying to drive the point that you can use Cinder for other things. And you should use Cinder for other things. You've already invested in open stack. You have a cloud and you have all these backends that are abstracted and everything else. There's no reason to go out and reinvent the wheel and write a new abstraction, you know, whatever it might be. And I won't say some of the companies that are doing this. You might as well just use what's there. There's no point in writing another one. So creative volume, attached volume, it's all the same stuff, right? I always do this just because Docker gets a lot of hate. So I like to give them some love. I think they're doing a great job. I love what they've done in 112. It's made my life easier. Things are fantastic for me. Some things break once in a while, sure. But, you know, open stack, we probably really shouldn't cast stones about that, right? So, all right. So, I'm gonna go into some things here and I'm gonna skip through most of this because we thought rather than look at screenshots and videos and stuff like that, Ed's gonna be brave and he's gonna do live demos. And I'm gonna heckle him and laugh at him when they fail. So. If it doesn't work, we have a video that you're gonna annotate, right? Yeah. And so the good part is these screenshots are in the deck. So if you get the deck, which is already up on SlideShare, you can look at the screenshots instead of having to watch the video. Yeah, so a couple of things. There's the slides are on SlideShare and I also have all the stuff up on a blog and it has his blog and we linked each other so you can find all that stuff. So what we're gonna do is we're gonna look at take our open stack cloud. Just all we have on there is compute networking and storage right now. And we're gonna mix in our chocolate, which is Docker. And then we're gonna throw in a little frosting, which is our Cinder Docker driver that we're talking about. And we're gonna make a nice tasty treat. So.  Actually, you don't even need these, do you? I'm gonna let Ed take over and show you what I just skipped. We'll try this here. Screening. Uh-oh. We're all right. So I'm VPN back into Denver. And so let's, we'll do the Docker swarm stuff first, right? Because I have both of these set up. We'll try to do that. So, and you can tell me what I'm forgetting here to do. So Docker volume LS is the first thing we wanna look at. It'll give us some stuff. I have a test volume, one, two, three, four, five. So we've created that. We can actually go back and look through our, we can go actually look at our open stack here. So one of the things you have to do, and it's a good practice, is to, and this is gonna kick me out here. So I'm gonna walk back in. Make different users for each of these. So I have a user for swarm. I have a user for mesos. Again, we've got a little latency here. So we're gonna go log into swarm here. And hopefully demo gods will look upon us well here. We'll actually see this. Ethernet gods. So the other thing we can do while we're doing that. Docker volume, I can type, right, create. And then we give it the driver. So you can have multiple of these. So again, we talked about there's a lot of, I don't know, you wanna annotate while I type? Yeah, sure. Yeah, so okay, so what Ed's doing here is he's gonna go ahead and create. One of the options is a minus D. So you specify what driver you want. If you leave that out, you just get the default AUFS driver inside the Docker. You can have multiple drivers on a single machine. So you could have a NetApp, a SolidFire, a Ceph, a Gluster, whatever you want, and have all of them running simultaneously on the same nodes and then just pick whichever one you want. Now the beauty of Cinder is it does all that for you. So you just run the one and talk to all of them, right? So the next thing is the name. Obviously you get to provide a name if you want. And then the size, size and gigabytes, and then type. So we take all of the same parameters that you can pass into Cinder and we go ahead and we abstract those and pass them back up so that you can actually get those from the Docker API as well, right? The only difference is you use the minus O or the option method instead of the minus volume type. So literally we got that one. We should be able to go in here in our open stack and see that we have our two volumes in here. So the second one I created was 20 gig. First one was a gig, they're both there. You can see the different types. Anything else you wanna say about that? Perfect, all right. So then we would do something like Docker, Ron, keep talking. So now we're gonna launch a container and what we're gonna do is we're gonna say, hey, attach this volume to that container when it boots up, right, or when it launches. So it's pretty simple. This is one thing that works a little bit differently than what we typically do inside of open stack because what happens here is we go to that volume and when we wanna mount it in Docker and in containers, what we're doing is we're dealing with file systems. We're not dealing with raw block devices. So what that means is the first thing we're gonna do before we go into the container is we're going to partition that disk and we're gonna put a file system on it. Right now, by default, I just use EXT4 for everything. It's configurable, you can change that around and you can put something else on there if you want. So he's already done it. You can see the arguments minus V is the volume and the first argument is the name of the volume from the Docker perspective and the other side of the colon there is where you want to attach that volume inside of the container and then of course he's using Ubuntu and he's launching a interactive Bash shell. So there you can see there's our volume. Yay. 20 gig volume. All right, so part of the demo gods shined upon us. Let's go, let's actually log back into this and look at what's on the base operating system just for a second here. We get there. Cut off at the bottom there, buddy. Yeah, I see.  You're good. We'll put a few. So you wanna talk about that? What's that on the host? Oh yeah, yeah, yeah, yeah. So similar to how, so for those of you that are familiar with how OpenStack and how Nova works, the way we do attachments to an instance is we actually go ahead and we make a connection to the compute node or the compute host and then what we do is we pass that in. We pass that through the virtualization layer. We do the exact same thing with Docker. So what we're gonna do is we're going to create, in our case, for what we're doing here, we're going to create an iSCSI connection. We're gonna iSCSI attach it to the Docker host and we're gonna mount it, put the file system on it like I talked about and everything else, mount it and then pass it into the container as a file system. And I'm just kinda showing some of the other bits of it here that you may or may not wanna see with the iSCSI connection and how it translates into the one. So let's go back to this. We'll get out of there. So the thing that's cool about this and the thing to keep in mind and the reason why, depending on who you talk to and some of the 12-factor app zealots and things like that and which side of the fence you're on on that doesn't really matter, the reality is if you have cases where you wanna have persistent storage and you wanna use it like a database and things like that, you wanna be able to actually have that transfer across a cluster, whether it's a swarm cluster or a mesos or just your own hard, your own bare metal cluster or whatever it might be. So with things like iSCSI, that's incredibly easy and that's why it's a good choice for OpenStack as well, right? So all you have to do is disconnect and reconnect somewhere else and you can just move that around. So with swarm, for example, your container goes down, your node goes down, swarm automatically detects that, it knows, it responds that same container somewhere else on another node, it also takes the volume with it for you. So you don't even have to worry about that, it just does it all for you. So I'm gonna have to go pull that. So I wrote a test file here just out to that volume and so I'm gonna go create a swarm service here. It appears that it's not in my buffer so we're gonna pull it out of my magical list of things here just because we don't wanna see me type this and screw it all up, so. Crib notes, I need crib notes. So that just, so go ahead and keep talking, you see what I did there. I'm making this up as we go, so I'm kind of screwing it. He's gonna screw with me, I'm messing with him, so. Yeah, one hour dude, that's completely wrong. So what Ed's doing right now is for those of you that haven't used it, check it out. You can look at, like I said, the slides or just go out and Google it. But the Docker 112 stuff with the built-in swarm makes life really, really easy. So you can just go ahead and you can combine that with Docker machine and talk directly to your OpenStack Cloud.  I mean, the only thing that takes any time is how long it takes to install the software and that's it. It's really, really awesome. So you do that and then what you do is you create a service. So the way swarm works is you create a service that's made up of a group of hosts inside of your swarm cluster, right? So that's what Ed's working on right now. Right, so I did that, I started it up. I actually put a web service in here so it just runs a browser or a LS files listing here in the root so we can go in and see now that this is attached to a different thing I should have, oh I connected it to my other volume. So we'll go do this again. So this is one thing though while you're here for folks that if you try this, one thing that is kind of interesting and we can fix this if people are interested by default we just do a raw makefs and create the file system in there. If you are using this for things like SQL and stuff like that you could run into a little problem because we use the defaults and you get a lost and found directory and if you don't go in and delete that sometimes my SQL gets a little upset with you. My SQL gets upset, my MariaDB does not. So I'm gonna kill my service, I'm gonna restart this again because I connected it to the volume that was already there so I'm gonna go back and connect it to the volume that I made that file in so I gotta go back. So one of the things you'll see if you're watching this I know it's getting cut off a little bit at the bottom here. Oh you're good in the back, it's actually just on here. Is that, that whole command went off and created yet another volume cause I didn't give it. So now I'm gonna give it to 6789. So I don't wanna talk about this real quick, right? So things are a little bit different, right? It's a little bit different but it's the same. So when you have a service and you're dealing with the service it's a little bit more complex and there's a few more options but you can kind of figure out, right? So they change the syntax and now what you're doing is you're actually giving a mount command and you're telling it specifically hey I'm mounting a Docker volume, that's really important. So when I first started doing this before the documentation came out and before 112 was official it took me a while to figure out why things didn't work so. So and you can see you're giving it type volume, you're saying the source, destination, et cetera, et cetera. So all the same options that we did before with just native Docker volume API are still there but unfortunately the syntax has changed and you have to do it a different way. But that's life. So one thing I'll point out here is I did that second time I did this. I gave it a volume that already existed and we're gonna prove that it didn't actually go create that again. So even though I gave it all these commands of where the volume driver was, what size I wanted it's still gonna be our 20 gig volume because the name is the key here. So test 6789 is a name that I already created so it won't go create another one. That's just the way Docker does it. So when we go over here to jump over here to this guy and we refresh him, there's our test file. So that proves that it was there and it stayed in that volume. If you guys wanna see we can go download it and open it, right? So it's still there. So that's pretty interesting. The other thing and I'll let you talk again, I'm gonna go so that it's running on D1. So I got three nodes D1, D2, D3 creative. If I Docker PS here, I can find that container and if I Docker kill that container ID. Now this is not through service, but I'm gonna kill it and the Docker swarm will actually go and respond it. So we're gonna watch that here. So it had mentioned how we don't actually recreate the volume and stuff like that, right? So what we do is anytime that Docker create, Docker volume create call comes in, what we do is we go to sender and we do a sender list and catalog through it and try and find that volume. So if it exists, we just use it. If it doesn't, we create it. And there you can see it's now on D2, so it moved. Swarm moved it over to D2. If you wanna see this, we can reproduce it. Yeah, we believe you. But the thing that's cool, so sometimes people, what's the big deal about containers, right? I can do all these same things with OpenStack and some people don't realize that you can do all of these same things with OpenStack. You can do these failover type things and stuff like that. But the difference is you can't do it in three seconds. That's the difference and that's what's pretty cool. And you can keep playing this game. You can have a cluster of 10 nodes and you just sit there and just take them down and just watch that thing go around Robin all the way through. So it takes about two seconds at most. So now I'm gonna cut over to, we'll jump over to Mesos here, Marathon. Just kinda, if you haven't seen the GUI before, there you go. You can hit the Create an Application button, but I'm gonna actually do this through Postman and just submit this through the API. So I have a, I don't know, you wanna talk about this or you? No, this is all you. All right, so basically Marathon defines things with a YAML file or a JSON file here. So we've got this JSON file. A couple of things to point out here is that you're telling it that it's a container. I don't know if you guys can see that. Yeah, I guess it's big up there. Telling it's a container, you're telling it's a Docker container. So Meso or Marathon is going to call into Docker through the Docker API and then it's gonna use Docker's capability to go off to volume, the Docker volume service and get these volumes. So that's the next couple lines here we use passing these parameters where I say what the Docker volume driver is and then I say I want a volume and I'm gonna give it a name here called Meetup MySQL Cinder and then I'm gonna tell it where to mount it. So what I'm gonna build, what I'm actually building here is PHP MyAdmin talking to a MySQL database just to get us something that we have a two-factor or a two-piece app here. I actually have Mesos DNS set up so this will find itself no matter where it runs. It takes a second, but you simply, so we simply submit this through Postman into the Mesos API. You'll see it comes back here or the Marathon API and it gives us an ID. So from there, we can actually continue through the API. I like Postman because I can, it's got the editor I can just hit submit but we'll duck over here to this and you'll see that the Meetup Example where we started this building this example here is created and then it builds a file system of the different parts. So we've got the database in the My PHP Admin. When we go in here, you'll see that's the services running as a container and you saw the other one in there which is the My PHP Admin. So if we drill into these, you can get all the details. You can see down here, this is running on these different set of hosts. This one's called container one and there's the ID. If we killed it, it would start up somewhere else but that's not what we wanna do here. We wanna actually go in and look at the My PHP Admin. That's running on container two. So these have to do a service discovery and find each other because Mesos will schedule them wherever, right? That's the interesting thing. So then we can actually fire this up and if all the demo gods worked well, it comes up and if I can remember what the password was that I put in here so we'll have to go look over here. So we're passing all the stuff in his environment variables. Password was like password one, yep. So we should be able to- It's much better than password two. Log in password manager. So sometimes if I go through more, I mean, we've kind of chased the service around with Swarm, Mesos and Marathon will do the same thing. We can go kill them but I'll create a database table in here. I mean, you can see that the basic database has been created and it's talking to it. And so you can use the Docker volume. It's gonna do its favorite thing here. So for those that are wondering and may not know, some people may be asking a common question I get is, can I use this with Kubernetes? And the answer is absolutely not. So as of right now and probably for the foreseeable future, Kubernetes does not actually leverage the Docker volume API. So it doesn't have any interaction with that. Demogads said we're done. Kick this out. So there's no, so they use a completely different model. The good news is as of recently, a couple of weeks ago, they have decided to have an official volume API so that we can now develop to and we can create something to use that. So since Kubernetes is all the rage and everybody loves it, that'll be the next thing. So along those topics, did you have anything else you wanted to- No, that's, I mean- The other thing I wanted to touch on is as far as this project goes, I started this quite a while back. It's been moderately interesting and some people are interested in it and using it. Since then, there has been a group of folks in the Courier Project inside of OpenStack that are kind of launched a similar thing. So I'm actually gonna meet with them tomorrow and look at maybe working with them and converting all of the stuff I did into Python and adding it to some of the stuff that they've already done and seeing what we can do to actually make it an official big tent project. So that's kind of where things are going. So hopefully in the future, rather than J-Griffith's GitHub, it will be on the OpenStack GitHub. So that would kind of be the idea. That's the name, that's not how it's pronounced. So I didn't say the name because of the way it's pronounced, but it's actually F-U-X-I. You guys can imagine how the pronunciation works. I'm sure that it's pronounced. Maybe that is how it's pronounced, where it's supposed to be, but... So yeah, there's Fuxi, we'll call it Fuxi. So Fuxi is out there. It's a little different approach. It's written in Python, so that's good, so it can be in the OpenStack ecosystem without any challenges or anything like that. There's a little difference in performance and things like that that you're gonna get. And also, there's a number of things missing right now. But I was thinking, I could probably pick that up and run with it and get something going. I would, it would be interesting to try and get something with the Golang stuff just because that's native to Docker working inside of OpenStack. But the reality is, it's just a Unix domain socket, so Docker doesn't care, it doesn't matter. So it can be Python, it can be Ruby, it can be whatever you want. So there's no reason to rock the boat or make things, make life more difficult because then you've gotta come up with an infrastructure and a CI and everything else, and so it's a lot easier to just use the cookie cutters that we already have. To forget a little time left, I'm just, one of the things that's interesting here is I'm going to actually to Cinder and creating another volume. So the nice part is we get all the Cinder features. So snapshots, clones, those kinds of things come along in Cinder that aren't supported in Docker. So I just created another volume here and when we go back to this guy, we'll see he shows up in there, another volume. So we're just looking for all the volumes that are in that tenant in Cinder. And so now if I wanted to do things like create a bootable volume, which we wouldn't be bootable here, but we might have an image that's in glance and we're gonna lay that down so when it gets mounted in the container, it just happens. And we can do that through Cinder commands, which gives us all the features and functions and we can extend volumes which Docker doesn't support, we can change types which Docker hasn't built support for. So having Cinder on the back end really brings you a lot of value to that stuff. And that's a really good point. So one of the things that some people ask is why, what I do this as opposed to using the vendor X, Y, Zs, plug in and talking directly to the back end. That's the main reason. So all of the stuff that you get from Cinder, you now by default kind of have in Docker, which is a pretty big win. It's a significant consolidation of effort and a consolidation of code. The big thing is the whole Linux mantra is basically do one thing, do it really well and then build on top of it. So the premise here is let Cinder do the abstraction stuff, let it do it very well and build one small layer on top of that and then so on and so forth. So that's kind of the idea. Right, so I mean there's lots of bits where I can go and create the volume from the snapshot and then create the volume. It's basically creating the clone. So, I don't know, what else do you want me to show, John? Does anybody want to see anything? Any questions? So the question was what does the types mean and what does gold mean? So inside of Cinder, we have a concept of volume types and the nice thing about volume types is you can make them whatever you want. So it's an arbitrary label for metadata. So an administrator has the ability to go in and create a type and they can call it Foo or Gold or whatever they want and then they can assign extra specs metadata, key value pairs to that type. Now the end user doesn't see that information. It could be something like this customer's lame, charge them double, who knows, right? It could be whatever they want but when that person says, hey, give me a type of gold and in this case what we did is we used gold to signify higher performance storage. Yeah, and the way that works is that works because the Cinder scheduler then looks at all of its back ends and tries to match the filters that it has based on what you passed in in that type. If you want to talk about it, I'm putting this up on the screen. So if you want to talk. Talk about it. So I'm using EXT4 right now but you can configure that and change it. If you wanted to use XFS or EXT3 or whatever you wanted, you could change that. I see. So if you guys, the question on volume types, I just kind of put it up on the screen here so you saw a list of volume types. You'll notice on the list it's just kind of scrolling off there. They're all on solid fire right now but that could be multiple back ends. So that could be an EMC, a Pure LVM, Ceph. Well, we can't do Ceph because we don't do iSCSI on Ceph. And then down here are the parameters we're passing to for the different quality and services. So again, these are all solid fires. We're using solid fire semantics here but if you were passing these into a NetApp back end they have a different semantic for what they do for QoS. And that's a good point. The, this particular thing that I have right here is iSCSI only. It doesn't do RBD, it doesn't do fiber channeling and those. That is one of the other advantages of bringing it under the courier umbrella is then we could use the internal things and have folks internally test it. So. Small QA, what happens when you create two volumes with the same name in OpenStack and then try to. You got big problems. Yeah, so that's bad news. Unfortunately, Cinder still does not enforce unique names. I always tell people pick a control plane, one or the other, not both. You know, Ed was demoing how you can do that but you really shouldn't. So what I do right now in the Docker code is if I see more than one volume with the name I error out and say, sorry, you've got two, I don't know what to do. Good question. Something else that I've looked at and again, if this lives on and goes forward, what I'll do is I'll stash the UUID from Cinder inside of the object on the Docker side and I'll use that as a source of truth. Most of that code's already there. So it's not hard. Yeah. Okay, yep. So the question was, how does the volume attachment actually happen? And do you mean from the Docker host perspective or from the Docker containers perspective or both? Okay, container. Well, okay, so it's still kind of the same thing. So let's say we have a volume that we've already created and used. Or no, actually, let's start from scratch. So we don't have a volume. We say Docker run volume, minus D, Cinder, volume, empty, whatever. What's gonna happen is it's gonna go, the Docker is gonna make a call down to the Cinder driver and it's gonna ask it, hey, do you have a volume named empty? If it does not, it will say, okay, create it. And so we'll go off and we'll go to Cinder and we'll call Cinder create volume with all the options and stuff like that and create that volume. And then what's gonna happen a little bit later in the process is Docker's gonna come back to the Cinder driver again and it's gonna say, hey, I want you to attach this volume. So inside of that driver, I'm going to go ahead and I'm gonna find that volume again. I'm gonna grab it and I'm gonna inspect it. I'm gonna do an ISCSI attach and I'm gonna inspect it and see if it has a file system on it. If it has a file system on it, all I'm gonna do is I'm gonna mount it. That's it. If it does not have a file system on it yet, I'm gonna run a make-of-s on it and format it. After that, I go ahead and I send that information where I mounted it back up to Docker. Docker now knows what to do with mount points and it just passes it into the container. And that's it. So the... Yeah, go ahead. Yeah, so Docker's kind of interesting. They really are pretty serious about this save no state thing, right?  It's gone, it's done. I mean, that's the end of that. Now, if you go then and you say Docker volume LS, you won't see that volume unless Docker got in a weird state and cashed the information somewhere, which it sometimes does. But yeah, typically what happens is all of a sudden Docker doesn't know about the volume anymore either. If it's actually actively in use and attached and you try to do that, Cinder will fail to do the delete. It will say, hey, you can't delete this, it's in use. Good questions, I'm doing this all on the screen while you're watching, if you're... It will delete. It won't. It will not delete. Cinder won't let you delete a volume that's in an attached state. Oh, so you wanna use Docker volume plug-in for something else? I'm not, actually, I'm not. Okay, yeah, we should chat. I'd love to hear what you're doing. It'll be cool. I don't know, our time is probably up, I think, so four minutes usually. Any other questions, quick? We'll be up here for a bit afterwards. Oh, one more? So yes, as a matter of fact, there has been for quite some time. So there's a SolidFire GitHub, and it has one, but one of the nice things about the acquisition and the merger of SolidFire and NetApp, NetApp actually has a really cool team of folks that are focused almost exclusively on Docker and containers. They've created a project called DVP, Docker volume plug-in, which is a NetApp Docker volume plug-in. It, they were able to just take my code that I wrote and put it into that NetApp DVP, and it has support for SolidFire, CDOT, FAS, all the NetApp portfolio. So you've got options, it's kinda cool. There's a lot of choices out there. That happens to be loaded on this machine too, so there's one from a NetApp box. I didn't give it a size or anything. All right, last one, cause they're dimming the lights. Yeah, you need OpenStack. Well, actually, no, you clarify. You don't need OpenStack, you need Cinder. And one of the things that people don't really understand is installing Cinder is actually pretty easy. It's all of the other stuff that comes with it makes things a little bit more interesting. Cinder is actually really easy to install. All you need is the Cinder services, MySQL, and Rabbit, and you're done. But we're working on changing that. So I actually have that on this laptop here. I have a very nice setup on a single VM that has just those things in it that I was able to, I can use to develop stuff on the planes back and forth. So, fully standalone setup to do this on a single VM on that laptop. I didn't demo off of that today, but we can. All right, with that, I think we'll wrap up. And the next guy, you look like you're here to present. No? All right. All right, cool. Thanks, everyone.


Welcome back everybody. Yes today is throwback Thursday, but no this is not a flashback It seems the Russian election meddling conspiracy theory has returned just in time for the election It seems that you know a two-year election to prove that Trump was a Russian agent With the Mueller probe that came up with nothing wasn't enough now They they have to keep this going so yeah, according to the FBI director Chris Ray Who just confirmed that Russia is currently meddling in the election to quote denigrate vice president biden To denigrate him. Oh, we don't want that do we you can't denigrate Vice president biden. He's above that you can denigrate trump all you want. That's fine. Say whatever you want about him Our republicans for that matter, but democrats or biden. Nope Can't do it. So before we get into uh, just discussing how utterly insane this is. Let me show you the clip Yes, I think the intelligence community's consensus is that russia continues to try to influence our elections Primarily through what we would call malign foreign influence As opposed to what we saw in 2016 where there was also an effort to target election infrastructure You know cyber targeting. We have not seen that second part yet this year or this cycle But we certainly have seen very active very active efforts by the russians to influence our election in 2020 Through what I would call more than malign foreign influence side of things social media use of proxies state media online journals Etc an effort to both sow divisiveness and discord And and I think the intelligence community has has assessed this publicly Uh to primarily to denigrate vice president biden and what the russians see as kind of an anti russian establishment Um, that's that's essentially what we're seeing in 2020. Hmm Well, that's interesting I don't know about this guy. Who is this guy? He's definitely no friend of trump No friend of america.   Well Let's put that to china. I mean who is more friendly to china clearly not trump or republicans Which is why they're meddling in the election for democrats, but you don't hear anything about that But the fei, uh director says that russia wants to denigrate joe biden. I just love that word choice like That it's almost like saying bad things about him saying negative mean things about him or uh impugning his character All things that happen during a presidential election, right? When has there been a presidential election where both sides didn't attack each other's character or their policies or their intelligence? I mean, uh, that's par for the course. That's that's what a presidential election is. That's what politics is So this is not unusual, but yet They're trying to make it seem like it's unusual. It's just something we've seen a lot But john mccain has unloaded on you in the last 72 96 hours as has sarah pale mccain saying essentially we don't know who barack obama is where he came from. I i'm an open book. He's not Were you surprised that he didn't bring it up last night at the debate and use that line of attack? Well, I am surprised that, uh, you know We've been seeing Some pretty over-the-top attacks coming out of the mccain campaign over the last several days That he wasn't willing to say it to my face Clearly they want the american public thinking that anything they see that's negative about joe biden Uh, it's some sort of product of the russians or russian Propaganda, I mean forget all those videos that you've seen. I mean going back forever, okay? I mean i'm not even talking about Just this election cycle. I mean biden's known for saying stupid crap, but it's just gotten as he's gotten older It's gotten worse and worse, but just forget about all that that you've seen Just tell yourself that it's the russians that did it I mean, I I don't think anybody on our side's going to do that and probably very few independents But I can see democrats like literally just lying to themselves convincing themselves that it's the russians doing that It's almost more than the mind can handle to think that the u.s. Government and the media Want you to believe these things one that criticism of joe biden is the product of russian meddling Which it's very bad because it sets up this environment where scrutiny of one party's candidate Uh, or their party. It's considered to be foreign interference Okay, while the gloves are off in regard to the other party and it's completely messed up But the media and the democrats and elements of our own government want americans to think that criticism And denigrating trope of republicans. That's fine. That's okay, but criticism or denigration of democrats are buying That's the russians.  What exactly they it is they're talking about But uh, you know an election won by trump. That's russian interference russian meddling, but an election won by democrats Hey, okay, that's good You know pro pro trump rally or lockdown protest bad left wing riots amass protests. Okay, that's good So this is a pattern we're seeing here, but I I asked earlier What exactly are they talking about when they say this in the first place russian meddling? It sounds and they use these words like covert and proxy to make it sound like it's very, you know, like a cloak and dagger Or 007, but what exactly are they talking about? I mean last time It was the organization russia had organized some rallies a few rallies both for and against trump meaning some were pro hillary and anti trump And some were for trump and guess what the rallies that were against trump were promoted by msnbc and cnn That's right. So in that case if russia was trying to sow division And throw disinformation into the election cnn and msnbc literally facilitated it. They helped On november 12th of 2016. It was a trump bashing love rally as the liberal media He piles of praise and promotion on an anti trump event in new york city and they yelled we're not going to be Tolerating any sexism or homophobia or racism and that is really the message all of sort of these protesters coming together frustrated angry All those people coming together because of russian agitation That's according to special investigator robert moeller's indictment quote Defendants and their co-conspirators through another organization controlled group organized a rally in new york called trump is not my president Held on or about november 12th 2016 it is the most organized protests that i've seen happen here in new york city and that's good news because again as he pointed out to me They want their methods to be heard don't want violence if they've been seeing across the country and other protests Yes the collective and the collective voice of the liberal media was all chanting one thing Russia appears to want to benefit from what what's going on today And if they can choose the person that will help that they will do it While promoting another people out here. They're chanting They're they're banging the drums and they're explaining that they do not want donald trump to be their next president So beyond that they also bought some facebook ads other than that. I mean, what did they do? They bought some facebook ads They had some rallies. That's pretty much it. Are we supposed to believe that? Uh, so many people hated hillary because of russia. I mean really She had been hated for decades Uh russia limbaugh all through the 90s made his name By trolling the clittons and making fun of hillary clinton, especially Which is one of the reasons the media has been calling him a sexist all these years You know because it's kind of like trump if you attack like a female democrat that makes you a sexist They say you're attacking women plural, even though you're just going after specific individuals Uh, but he made his name doing that through the 90s I guess the russians started this whole campaign back then Is that what we're supposed to believe that People will hate hillary clinton and didn't want her to be president because The russians brainwashed us in the 90s through russia limbaugh talk about conspiracy theories Um ray also claims that the russians are sowing discord in the country And I think that's interesting because I accused the media of doing that on on purpose regularly As far as i'm concerned, they that's what chris ray is doing right here I mean, let's let's think about that They say that you cannot denigrate joe biden If you denigrate him or he criticized him, I guess it's the product of russian meddling Thereby dismissing half the country as russian agents I mean, you're basically saying that they have no say And in the presidency because if they pick trump, well, they're with russia And you know that means that they they fell for russian propaganda and they're basically russian agents That feels intensely partisan And something that will definitely sow discord in this country And what about china in iran and everybody else who's meddling in our elections? I mean Mexico and through the democrats illegal Foreign nationals in our country like literally driving policy and driving like votes To democrat politicians. How's that not meddling? That's like direct meddling. So who does china want in office? I mean, if I had to take a wild guess I'd say it's the party that supports the far left marxists and communists That are rampaging through our country right now and want to destroy american history and speaking of all that In regards to the democrat support of these marxist far left groups that i'm sure china is quite happy with um billum's founder alisa garza the one who's the train marxist She's teamed up now with a pro ccp organization Called the chinese progressive association, which is obviously a front that's being used to sow discord in the united states So there you go, and it's it's proven right here right on their website black futures lab, which is a um Uh website that was set up by garza and it says right on here black futures lab is a fiscally sponsored project of the chinese progressive association That's all for this episode Again, thank you to all my patreons and subscribe star subscribers As well as all of you who have donated or purchased products from this channel sponsor Thanks to all of you. I wouldn't be able to do this without you And if you would like to support this channel, uh, you can find all those options in the description or the pin comment Also, make sure to join us tonight in my discord server at 9 p.m. Eastern for our live discord chat stream Thanks for watching keep coming back


The next speaker, him and I may be doing something special on tele-sales for those that come to Vegas. All right? He knows his stuff. Good buddy of mine. I'm as close to him as almost anyone in the insurance industry. Love the dude. He cares. Managing partner of North Star Insurance Advisor. His whole family. Everybody is amazing. They've been a part of every 8% and we're going to keep that rolling forever, if you will. Super knowledgeable on tele-sales. They built a monster. They're going to do over 30 million this year. He was doing a bunch of free webinars and giving everything away. The dude has a massive heart. He cares and he has scaled him and others. His partners and his family have scaled a massive, massive, massive, massive phone sales company. So I'm excited for him to actually release his story, how if you don't quit you can't fail and the current state of the insurance industry, please welcome a virtual stage. My good buddy, tele-sales machine, Mr. Ramiz Hakim. Hey, 8% nation. What is going on? This is Ramiz Hakim, owner and co-founder of North Star Insurance Advisors. And I want to come with you with a special message today. You can't fail if you don't quit. Listen, in my life there's been many, many, many situations where I was faced with the decision to bet on myself or to cash out my chips. And those that make it to the top of their niches, their markets, their industries, they're the ones that lean into their problems and absorb the blunt force that's about to go down. Now, those that don't make it are the ones that cash in their chips and move on to the next opportunity. I want to encourage you today not to run and hide during these uncertain times. I believe that during these times there are four separate phases that each and every one of us are going to be encountering right now. The first one is the denial phase. How many of us, even still now, are in this phase of denial where we think it's just about over. It's almost done. I don't need to adjust. I'm going to stay with business as usual. Eventually you'll move out of that phase or you're going to run out of business. See, we all thought that by Easter we'd be back to work as usual and here we are coming and leaving through the Easter season. After that, you become afraid. Once you accept the fact that we got a problem, and now you're afraid, you begin to contract, you're nervous, you make sporadic decisions because you understand you need to make ends meet and there may not be enough cash reserves to have you make it for as long as what you think it is. I was there not long ago. We were looking at a situation where we had eight total call centers, a home office with a couple hundred people and seven satellite centers, support staff, marketers, sales agents, customer service reps, contracting, HR. How do we get people that have used to coming to work at the same place every single day for years and then overnight switch them to go work from home without a robust IT department, but you have to overcome that fear. You see, you can just quit and cash in your chips. You can cash in your chips and say, okay, I've had enough. I've made what I needed to make. Let me take what's mine and let me move on or you lean in and that's what we did. And because we've done that, we are now experiencing incredible growth, the highest profits we've ever seen, the highest morale we've ever seen. People are thankful and grateful and their level of loyalty to the companies through the roof that now takes me to the next level, which is I believe resourcefulness. Once you have put together a plan and a strategy and execute, you now become resourceful. There's some optimism there. Hey, we may not be clicking at all cylinders, but we're doing the best we can and you become getting better and better and better. And like I said in our situation, we're a better company now during this time than any time before, which then leads to the fourth phase of this crisis, which now becomes confidence. We are confident that we're going to come out of this better than we've ever been before. We are confident that we will be a company that will be forever changed for the good. That this situation was not a setback. It was a setup to expose the inefficiencies in our company to force us to feel some of the areas that needed to be firmed up. So we denied it. Then we were afraid. Then we became resourceful and now we're confident. Now in this level where I believe North Star is right now, where I am right now, when we are in this level of confidence, it is our responsibility to begin pulling our neighbors out of the denial phase, out of the afraid phase and helping them during the resourceful phase. Listen, if you refuse to quit, you will never fail. Of course, you're going to stumble. Of course you're going to make mistakes. Of course you will. But see, you have a decision after each and every one of those things. You see, only the great salespeople, only the great companies, only the great IMOs and agencies are going to come out of this situation better. Everyone else is going to retract and that starts with a decision. Are you going to double down on yourself, on your abilities, on your commitment, on your work ethic, on your discipline? Are you going to bet on yourself?  You'll never fail when you lean in to those problems. I remember getting started in the insurance business. Final expense is where I started and I really, really enjoyed the line of work. I enjoyed the money. I enjoyed talking to the customers. But I was getting burnt out. I was experiencing no shows. I was sitting in homes that I did not enjoy being in. I was having a call on leads and trying to finagle my way into homes. And although those are important aspects of the sale, it was just burning me out. But I saw hope and there was a glimmer there. And so I doubled down on myself. I went all in on myself. I started hiring people on payroll with money I didn't even have yet. I was counting on me to make sales to pay payroll. It was one of the best decisions I ever made. I put myself in a position where I had to perform, where I had to produce, where my hours were going to be 24 hours a day of work to make sure I could make ends meet. I went all in on me. And because of that, and there was many of times where it would have been so much easier to throw in the towel, cash in my chips, take what little I had left, and move on to the next thing. But we were not designed to be mediocre. You see, mediocrity is a decision that you make every day when you wake up.  So where are you now? What you're dealing with now is the same story that many people that preceded you had to face. Now, the circumstances may be a little different, but it's really not that different. Situations will come and situations will go. The situation we're in now just happens to affect everybody. But this virus is no different than a traumatic event in your life specifically. The only difference is now it's a bit easier to feel sorry for yourself because everyone's dealing with it and the government is here to help us. Folks, that is a dangerous way of looking at this situation. Snap out of it. You're already in the process of quitting. You're staying in the denial phase. When you figure out that you got what it takes, you may need to finesse some things because you're going to learn a new skill set. But once you commit to that and stick to the plan and require that discipline from yourself, you'll never stop growing as a business. You'll always be expanding. You'll be able to employ your friends and family, give opportunities to people, and then invest back in your community. Folks, I want to give you a good word today. You can do this. I got in the insurance business when I was 19 years old. I didn't know a thing about business. What I did know was that my parents instilled in me hard work, commitment, loyalty, follow-through. That's all I had. I had no sales ability. I had no training. I barely even had any decent leads to call on, but we made it happen. We made it work. Today, because we have continued to push through many of the hurdles, we're now seeing the fruits of our labor. It required a major national catastrophe to really test what is it that you've been building over these past 10 years. I paralleled this situation with the number of them before this, for me personally. I have worked with carriers before where I showed up Monday morning and found out they were in receivership. That's a disaster for a business, much like this virus. Or how about the carrier that just pulls out of the market and gives you no, they don't tell you that they're going to be doing that. They just surprise you. That's a catastrophe. One of your lead vendors goes belly up and you're accounting on them to follow through with something for you this week. That's a catastrophe. How about when you're heavily invested in television and the election cycle is beginning to take much longer than anybody expected? And so now you can't even afford to compete with some of the big retail shops in this country. That's a catastrophe. Again, the difference between some of the stuff I've outlined for you and this virus specifically is that this one just affects everybody.  This is just a part of your story. This is just another one of those things that you can put another notch on your belt and say, I overcame that too. So you have what it takes. You've moved through these stages of catastrophe and trauma and now you need to make a decision. Good luck out there. Cody, the 8% crew have put together what I believe to be the most premier group of individuals that are going to help take this industry from what it once was to what it is going to be. The voices of the past are being drowned out. The old way of doing business is beginning to shed, becoming exposed for what it is. There's hope for you. You can make this happen. And the people that you see on the top that you try to model after that you might look up to, let me tell you something. There's no difference between them and you. Keep fighting friends. It's worth it and it will be worth it. And one day we'll be able to sit around a table, break bread and talk about how amazing this time was where we felt like quitting, but we decided not to fail. See you in Las Vegas.  Awesome job, buddy. Thanks for being a part of this. Thanks for being a part of all of them. Super excited to see you dominate the stage in Vegas on this exact topic. Dude drops like it's hot. Like he's one of the most underrated speakers in the industry, flew with his words, knows this stuff. Huge thanks for being a part of this. All of North Star and Ramiz. Thank you so much, buddy. Appreciate that very much. All right, so you watched this video and you want to learn how to take a live call and transfer it from an opener to a closer. That video's for you. Click on it and I'll see you there. Again, I'm not sure what time you're watching this video, right? Intro, expert, control, qualify, transfer. This is how to effectively transfer a live call from an opener to a closer.