Good afternoon, everyone. Thank you all for coming. So, we are going to talk about open stack consumption models and came up with a catchy phrase, good, bad, and the ugly. So, no labels, no judgment. But thank you all for coming. So, I'm going to be moderating this panel today. I figured it's easier to walk around. So, if you have any questions, I can be the micro-runner as well. My name is Ashish Nadkarni. I'm an analyst with IDC. I've been covering open stack for over four years now. So, I've sort of started at the Atlanta summit and this is my sixth summit, I think. So, anyway, thank you again. Either grab something to eat or this is standing between you and lunch. Hopefully, we'll keep this interesting enough. So, when you go to lunch, it'll be worth the wait. All right. So, with that, let me introduce, we have a fascinating panel of folks today. So, let me introduce them. Do you want to go through and introduce yourselves? Sure. My name is V.S. Joshi. I am from this company, Dell EMC. I'm in the emerging technologies team at Dell EMC. And prior to Dell EMC, I had my own startup. And yes, I have had experience with the public cloud and things like that. But currently, I'm with Dell EMC and I'll be talking about open stack consumption models. Great. Thank you. I'm not James Page, as per the description. I'm Mark Baker. James was unable to make it, sadly. So, I'm the open stack product manager at Canonical. Also branded. You'll see three of us branded. So, and I also sit on the open stack board. So, I'm our representative on the board. And I sit on the product working group and a couple of other things too. So, very good. Hi, everyone. Kamish Pamaraju with Marantis. Branded as well. We're all branded. So, long time in the community, about six years, this is my 10th consecutive summit. And being with Marantis for about two years, I run marketing and technology alliances there. And prior to that, I was with Dell. So, very familiar with all the Dell open stack solutions prior to that as well. Thank you, guys. And I'm your unbranded moderator. So, I'm going to make this interactive. So, questions anytime during the panel are welcome. I have some questions here just to get the conversation started. I'd like to keep this conversational. So, if you feel that you need to ask a question, don't wait till the end. You know, let's have a conversation. The folks at the back, if you guys want to move up in the front, I think the room is a little too big for us, but move up if you want. All right. So, yes, as the, as Dell EMC being the newest kid on the block, if they say that, or if there are a lot to say that, why don't you sort of kick this off by giving us a lay of the land as how you saw it or how EMC saw it as it walked into this field. Okay. So, I mean, so first of all, we're talking about the private consumption models or the private cloud consumption models as far as open stack is concerned. Now, at a very high level, the way to look at it is that there are a couple of models. One, the most hands off model is that of a managed cloud service provider. That's the most hands off approach. Yeah. And in that hands off approach, there is somebody else that is creating the cloud that is somebody else managing the cloud, supporting the cloud. And you as consumers, you essentially have just what can be called as a domain operator at your end that is managing the creating the users, creating the quotas and managing the cost and the relationship between the cloud service provider and your employees and things like that. So, that is the most hands off approach, managed cloud. We would like to say that immediately after that is the turnkey system model or the appliance model. And in the appliance model, essentially, yes, you do have the domain operator. And you also have a very low skilled cloud operators. Yeah. And then I would say the third model would be the distribution model, the distro model from Red Hat and from Canonical. Again, let them speak about it. But I think that there is where you might need in addition to having the domain operator, the cloud operator, you also need a cloud architect. And the final is the do it yourself model where essentially you need the whole thing. Plus, you also need the engineering support and those kind of things. Again, all these functions that I talk about, like domain operator, cloud operator, cloud architect, and the engineering support, all these things can be done by one person also. But again, I just want to put them in these various buckets or so. So I think that I would say at a very high level just to get the discussion started, I would say those are the four models and I'd add a fifth, actually, of course, which is public cloud. So it's very indeed, you know, for early Opus Stack and still today, a great deal of people consuming Opus Stack services through public clouds, whether it's Rackspace, OVH, or whoever. So it's not obviously a non premises, but it's another model of consumption. I was just talking about the private cloud model. Yes, absolutely. Yes. So why should anyone even bother about consuming anything other than the public cloud? You know, I mean, I'm being controversial in the sense that I believe that the the software. So our CMO Boris Rensky has been has famously said about a month ago, he wrote a blog saying that infrastructure software is dead. Nobody wants to consume software at at large scale anymore. It's it's the the model that VS was talking about at the end of the day, you want the Amazon like experience, whether it is private public, it doesn't matter. At the end of the day, it's the user that that's having that experience, it needs to be seamless. So we can talk more about it. But I wanted to start with that kind of a starting point. I think that that's really a challenge of operations, though. So it's not that you don't want to consume software. You want to absolutely use software. It's just that operating large complex technical projects like open stack can be complex. Whilst the cost of acquisition, because it's open source software can be very low. The cost of operations can be can be high. And it's that that people are looking to try and remove that cost or at least minimize that cost. Yeah, that's an excellent segment or so thank you for the introduction, folks. It's a great segue into our next sort of question is into the types of customers that would be naturally, you know, inclined to go with one or the other. And so in your experience, what kinds of customers come to you or or you are able to, you know, sort of appeal to them your your solution. So come in. So some very large open stack users, you know, with, I'd say, more than 5000 nodes. And we have done cost models. We've done cost models for DIY for distributions and for manage services. And you know, some of the largest telcos in the world started off with DIY. Because they find, you know, that at their scale, with hundreds of data centers and tens of thousands of nodes, having an in house team with the expertise and and all the, you know, source code access and all that stuff actually works for them. Over time, though, what ended up happening, I'll give you an example. I can't name customers, but one of our customers ended up what we've fondly called Frankenstein clouds. So they ended up doing, you know, they had 100 data centers and every data center had a different cloud. One was running Liberty. Another one was running kilo. Another one was running something else. And all the versions were all over the place. And they ran into this maintenance nightmare, if you will, right? So then they said, look, we're spending way too much time on maintaining these different clouds. How do we get this out of this Frankenstein cloud mode and kind of have a standardized, you know, software that's kind of distributed and working everywhere? So large customers start out that way. They're thinking they can do it. But ultimately, they need standards and standard software that can be deployed across the board. So that's one example I just wanted to throw out. This I think, I mean, it follows most many technologies. Many technologies follow the same path, right? Where at the beginning of that project, the early adopters are doing a lot of the heavy lifting, the engineering themselves, creating very bespoke environments. And then it goes through a very typical life cycle over time, where it becomes more productized, the kind of early majority start coming into and companies, distributions ourselves and others come in and start to productize that, all the way through to full kind of utility commodity. An open stack is on the same journey. Linux follow the same journey, database technologies follow the same journey and open stack is on the same journey too. So a lot of the super users and we love them, Walmart, AT&T and all these kind of people that are using open stack today, they were the people that were taking the arrows. It's the people further down the line that get the corners. I think this is very, very fascinating. It's fascinating to see the age-old technology adoption life cycle of innovators, the early majority, the early adopters, early majority, late majority and legards. And we are at that stage, open stack is six years old. And yes, we have come to that, as Jeffrey Moore calls it, the chasm, right? And we are at that stage of crossing the chasm as such. And this is where I feel that, yes, the people who are enthusiasts, technology enthusiasts and things like that, yes, they have tried these things, they have taken the arrows and things like that, they have learned from their experience and things like that. And now it is for companies like ours, maybe IBM, HP, Dell, to essentially take this technology and make it more adaptable for the masses, for the early majority and the late majority. I think we are a very interesting phase of this whole open stack journey. And at six years old, I do feel that, yes, we are at that whole, the chasm thing right now at the point. So I'd like to ask a question of the audience, how many people have open stack today deployed? And how many of you have it in production? Wow. And so I think for the folks who don't have open stack, I think what would be the one thing that you would want to tell them that they are here at the summit? What would they be interested in knowing from you as a sort of provider of an open stack solution? Mark, do you want to go first? Sure, sure. So having been involved in open stack since day one, we recognize that there's no one size fits all. So whilst we produce an open stack distribution, extremely popular distribution, it's not necessarily the fit for everybody. So we worked with public cloud providers to build that public cloud infrastructure based on open stack that end users can consume. We also have a fully managed service, for example, BoopStack, Build, Operate Transfer Stack we've had for a couple of years. And that is a model where we will manage the cloud but then hand the cloud over basically give the keys to the car as it were to the users once they're good. And that was initially launched actually to overcome the skills gap problem, right? This was one of the issues. You know, I guess everybody that's running open stack here is probably be hiring. And it's overcome that skills gap. We can build standard cloud up, we can manage it, we get it running, but when the users feel comfortable to take it over themselves, they can do that. And we have customers that operate across all of that spectrum, including some very large customers, doing several thousand nodes that we are managing to a to an agreed SLA. So we see across the broad spectrum. So the question is, what would you want folks? Okay, so for all the people, you know, I think if in case you get a chance, see the video recording of yesterday's session, there was a session called broken stack. And it was in the evening and it was they were talking about people who have started to implement open stack and they took three use cases and how they failed in that particular thing. And again, they were just trying to impart the lessons that they have learned. So if in case you get a chance, do see that open the broken stack session from yesterday. Today morning, there was a session and in that session, the person clearly articulated what was the difference of going for Amazon cloud versus private open stack cloud and the cost differences they have done the entire they took a configuration for a particular configuration. If they would go with AWS, what would be the cost and if they would go with private open stack cloud, what would be the cost and the I'm now a surprise to see the difference in numbers open stack private cloud was literally one fourth the cost of AWS. So again, yes, open stack, definitely go for open stack. But at the same time, remember, there are a lot of people who have had these experiences. So I strongly believe that yes, taking advantage of players like Mirantis and Canonical and Dell is absolutely essential, I would say for again, if you if you are looking for a tremendous amount of customization and things like that, and that is the core of your operation, that is the core of your business, then I do understand the do it yourself approach. But if that is not the case, I would say that you know, taking advantage of these vendors who are essentially adding that extra muscle. And you know, you don't have to do it by yourself. If that's what I would say, that's a great point. And Kamish, what would you tell your prospects? So the biggest problem with OpenStack is not deployment anymore. So that problem is solved.  Building is not an issue anymore. The problem is operations, as he pointed out earlier. How do you operate? So what do I mean by operations?  Now in OpenStack, it's not quite there. How do you monitor all of your apps? How do you monitor infrastructure? There are tools out there, but you can't really get a holistic operations environment running. So if you're running a thousand node cloud, guess what's going to happen? Every day, every second, something's going down. So how do you manage that? That's the operations piece that I think the community is starting to address now. But that's a challenge you have to keep in mind as you go and start building larger and larger clouds with OpenStack. So we're starting to help that with managed services. So for companies that don't know how to do that, we call it LCM, or Lifecycle Management. So upgrade from one version to another version is an example of that. Things are going down all the time. How do you monitor those things? How do you bring things up? At the end of the day, as an infrastructure operator for your cloud, you have to provide a certain SLA to your end users. So one of the biggest failures that we see with many of our customers is what we call the, we call it the orphan cloud syndrome. Orphan cloud. So these, you know, they start off very enthusiastically. They come to us. We build a cloud. It's maybe 50 nodes. We start off with that. Great. And then after six months, they come back and say, oh, we don't have any tenants. Nobody's coming on board. What's going on? And then it turns out there's an SLA issue. Developers try to use it. It doesn't work. So that problem has to be solved. And it's not just a technology problem. It's also a cultural process problem. Thank you. Any questions in the audience? So while we're talking about the readiness, the operations challenges, I'd like to ask a question of you folks who have had OpenStack deployed, who wants to offer to list out some of the challenges that you've had. Anyone? I'll run the mic for you. You have to raise your hand. Oh, there you are. Thank you for sharing your thoughts. My reading, the main challenge as of today for somebody that is approaching OpenStack for the first time is to decide between the distros or going vanilla. And by choosing a distro, once you have your workload running and going, despite of the keynote that we have with the interoperability, it's like a marriage, meaning you're going to have to revamp your entire network. Some of the services you are able to move, but it's like a marriage. You have to make sure that you're choosing the right partner. And I say that by experience. I won't name collars, rats, or... And we are moving away from one distro because of many issues. And this is a very tough thing to do. Thank you. That's a great insight. And if you don't mind, what kind of business is your forming? I work for a big telco in Brazil. Thank you. So I'd like to throw back the question to the panel. How do you address this challenge with distro? Is that a concern? Is that a question? So it's only one of the big concerns we see with users is around lock-in, right? They want to ensure that they're choosing a technology that is going to or a partner that's going to give them options in the future that they're not going to feel that they are locked into. Standardization, the interrupt demo, for example, is one way to be able to do that. But being able to take a workload and drop that into any cloud, any OpusStack cloud, I should say, irrespective of the distribution, it's more than just a set of common templates, right? There's all sorts of commercial things that need to be in place and support agreements and things like that. To some degree, as Asian Cockroft at AWS asked, I think, at one of the OpusStack Silicon Valley, who wants to avoid lock-in, everyone puts their hand up, who's married, right? And so everybody is prepared to accept a degree of lock-in in their environment. It's just where that dial lies and the amount that you're prepared to kind of stay. So clearly differences lie between distributions. We want to be able to differentiate. You're good at X. We're good at Y. You're good at B. But can the customer, let's say, for example, the customer goes with one particular distro, I mean, I will counter that lock-in argument by saying that, yes, they can move to the other distro. They can move to the other vendor for support. Is that a very easy transfer to make or no? Not really. As he was pointing out, all these distros are different. Underlying distros are the way they're tested, the way they're packaged, the way they're deployed. Varantis has a tool called Fuel. Red Hat has their own and Canonical has their own. They use Juju. We use something else. So once you are in that stack, you're pretty much locked in. Let's face it. I mean, there's no two ways around it. Now, can your workloads run on top? Sure. I mean, that's what the interoperability is all about. I mean, as long as you're keeping your APIs, OpenStack API standard and that's what you're using, in theory, your workloads should be able to migrate them. But if you want to change the distro, believe me, that's going to be a tough one. And be supported. I mean, that's the whole point of a distro. You're getting a distro because you want support for a vendor. And if you want to switch, then you're basically locked in. Now, that being said, at Morantis, we have been very, very focused on being agnostic and as open source as possible. Every other vendors, of course, are also open source. But we have branded ourselves as what we call pure play, meaning we're as close to the trunk as possible and all that. And we keep an open ecosystem of partners that we can integrate with, et cetera. So that being said, if you're using fuel, then you're pretty much locked into fuel. So how you deploy, how you configure, what networking you use underneath, all those things are tying you down. So but once you make those choices, you're locked in. Our value proposition is you have a vast array of choices you can make with Morantis. I think it's understanding the degree of lock-in. So understanding you're making a constant decision, I'm going to go with this vendor or this vendor or this vendor and understand this will be the cost of exit if I want to change. So it's just knowing that, right? Doesn't mean you have to completely avoid it because there's all sorts of other issues like support, as you say, you're dealing with. But recognizing that they exist, just being open source is not the kind of get-out jail-free card that many people may think it is. So just understand the risks. Unless you're doing your DIY throughout, right? And then you can go just trunk and do everything yourself. But again, that has its cons as well, right? When it breaks, it's very hard. When it breaks, you get to keep all the pieces. So, yes, Dell has taken a rather unique or sort of a different approach in the situation. Would you want to talk about the pros and cons of, you know, delivering it as a packaged, fully packaged appliances, in this case, sort of not worrying about the distro, if you will, or is there a challenge to be addressed there? OK, so again, considering the fact that Dell and EMC, legacy EMC, we address the enterprise marketplace as such, right? We are trying to take the technology and trying to make it consumable by a massive amount of customers, by make it widely adoptable and widely used by lots of enterprises as such, yeah? So because of that, I do feel that, yes, when you go, I mean, as compared to distro, again, in a distro also, and please correct me, Karmish and yourself, I do feel that, yes, there is a role for a cloud architect to play in a distro where the person has to decide which hardware, which software, what cloud configuration, what kind of service am I going to provide to my consumers? The storage, whether it is network, whether it is compute or database as a service. So those are the decisions that the customer has to take in case of a distro. Whereas in an appliance model, we don't, we have kind of limited those choices. We are saying, OK, we have a certain point of view. We have gone through all these things and we have put this hardware and this software and this networking and this, we have put all these things together and now you focus only on the applications part of it. And that is where I would like to differ from a distro as such, yeah? But otherwise, again, I do feel more than we competing with each other, we fall in the same bracket as opposed to DIY versus a public cloud, I would say. So the downside of it, so we have done, we had done HAD because we have stopped doing appliances. We had an appliance program at Marantis too. What we found, and again, I don't know, VS, maybe your, your experience is different. What we found is, many of our customers, we go with an appliance.  And invariably, I'd say 99.95% of the time, they'll come back and say, I want to change that. I want this networking, I have some other server there, this storage, use case, that or this or that. Then all of a sudden, you're no longer in the box. Now, now you're doing architecture. You're saying, okay, you want this, let's start with this appliance. We're gonna change this, this and this. And I want it in 10 different data centers with this much scale, then all of a sudden you're back to the distro. So what we found, it is our experience in Mantis, is that wasn't very, it wasn't flying for us. Nobody was buying appliances.  So that brings up a question and I think UAS, you talked about this earlier. How many people, how many customers when they come to you have that sort of total cost of ownership, mind frame? How many people like think about what is it that I'm trying to do here and is cost one of the main reasons? And if so, how do I go about measuring costs? Is it just the direct CAPEX costs or people costs? That kind of so. So most of the customers who come to us are essentially customers who have tried to do it yourself model. They tried to do it yourself model six months down the line. They have still trying it and things like that. And they have kind of failed as such. And yes, at that point in time, they have said, let's try to explore other opportunities. We have had customers, again a big software conglomerate in India. We have had a big retail giant in the US. They have deployed our appliance in their environment. And yes, it has started working within a week or so. So I think we have had that again. I do understand where Karmesh is coming from and where why he would say that, yes, there are some customized challenges that we will face when it comes to appliance. But yes, we are targeting a specific profile of customers wherein we are able to get into the customer and come up with a pre-packaged, pre-validated stuff. So I think. An appliance, I think, is really, again, it's trying to address that issue of operations. So somebody else has gives you a rigid architecture. Don't deviate from that architecture if you can help it. And the tools and other pieces packaged to do operations. But I think that's one way of addressing it. Another way, you know, open stack open source is very good collaborating between developers or facilitating collaboration between developers to create code. But the thing that it's only now really starting to recognize and certainly it's a flag that we're bearing right now is collaborating on operations, right? So everybody has their own puppet scripts or their own chef scripts or whatever it is. But there is best practice on how to back up an open stack environment, how to upgrade an open stack environment, how to pause, resume, et cetera. And a lot of the stuff that we're doing with Juju and the charms that we have is how do we codify that such that everybody in this room can input into that to be able to share that common best practice. Because in doing so, we're sharing the cost of operations across the entire audience. That's a very key point, actually. I think that is where the challenge is with any open stack cloud you may be building. Ultimately, it's all about orchestration at a higher level, across multiple clouds, across multiple availability zones, across data centers. And once we solve that problem, you don't have to have a specific tool, but it's really all about what are the best practices for ops? And as a community, if we come together and solve that problem, I don't know if there are committees or something, but eventually we need something that'll kind of build those templates if you will, right? And then you can use different tools. You can use to pop it. You can use Juju or whatever. But then you can implement them and run ops because I think that's a key challenge still. And open stack gets compared with Linux. So in this sort of sentiment, how can the open stack community learn from some of the stuff that has happened in the Linux community or even Apache and other places? So I don't buy the argument that open stack is Linux. Linux is to one thing. Yeah, but if you think about it, right? Linux is a single server. You need an admin for that server. You can deploy it and you're done. I mean, here we're talking about large scale clouds. And it's a very different ball game and a very different beast you're dealing with, right? So it's orchestration, it's ops. Of course it's all running on Linux boxes at the end of the day, but it's, you have to look, take one step higher. There's certainly comparison points. So Linux is a collection of very many different packages or technologies that have to be integrated, tested together. They have to be supportable for customers that require that. They have to be robust and resilient. And there are certainly things that the open stack community can learn, continues to learn from that environment. Obviously a lot of us are involved deeply in Linux anyway. So in terms of being able to create a consumable platform for people, but absolutely right, it's additional layers of complexity. People have called the open stack as the operating system of the data center, right? Actually so because that's what it's meant to be, right? You can kind of use it as an operating system, but it's long time, long ways away from there. They've come a long way in the last six months, last six years, but I think we have a longer way to go on the ops side. So any questions from the audience? Anyone? So we have around 10 minutes left and I'd like to switch gears and talk about workloads. And at this summit we have a lot of focus on NFV. Last time it was all about IoT. I'd like to sort of pose the question on what type of workloads do you typically see your customers deploy and why? And we have this discussion around traditional workloads, cloud-enabled workloads, and then cloud-native workloads. And people call them on any given day different names, but you get the idea. So I just wanted to sort of ask you, and yes, maybe we can start with you.  How do you see open stack helping or not helping and the model, the consumption model with these apps? So I think the way we have positioned ourselves is, okay, this is an infrastructure for your cloud-native apps. For whenever it is cloud-native apps, we kind of are going ahead with open stack. Not only that, we also have, we are providing this infrastructure as a service to all the app developers and things like that. In addition to that, the Pivotal Cloud Foundry, the PAS platform is, for the PAS platform also, this neutrino VXLAC, sorry, not supposed to be doing a product mission, but our product can act as an infrastructure as a service for the PAS layer also. So essentially the cloud-native apps, that is the main, that is the biggest workload that we see, that is the biggest focus area for us. And then what about use cases? Any particular, you know, industry specific apps or? No, see the thing is we are, again, we are at a very initial phase of the whole thing and we are still in the stage of trying to find out the right marketplace, the right profile of a customer and things like that. So we launched our product only two months back, so we are in the whole process. Yes, we have lots of deployments all over the place, but we are into that whole process at this point in time. So I'd say successful clouds, certainly in the enterprise or organizational space and we'll put NFB to one side for a second, successful clouds will trend to generality. So it'll be a general purpose cloud that will consume most if not all workloads, right? So we see signs of successful clouds are that they continue to grow and they get more and more workloads and they can be very diverse, web workloads, databases, analytics, whatever. NFB is a slightly different, we have many NFB customers. It's a slightly different use case because they have VNFs, which is fancy telco speak for an app. And, but they're very network centric applications and performance and throughput are very important. We still think there's a very strong argument about having a common layer as the underpinning without sort of tuning, really fine tuning it per VNF because then you're creating these hot spots of complexity. But they're different in their makeup to that sort of general purpose organizational enterprise clouds. I tend to agree with that. I think although OpenStack originally started off as a cloud native platform, there's an interesting story I can share with you. I live in Silicon Valley and I have a lot of friends who start companies. So there's a guy, an old friend of mine who worked at Microsoft Azure and he's a serial entrepreneur. So after he sold his company to Microsoft, he came back and he started a new company and I happened to meet him over coffee a couple of weeks ago and asked, hey, what are you up to now? And he said, hey, I'm building this cloud for legacy workloads. I said, what do you mean? Oh, yeah, all these people soft and SAP and databases, SQL. I said, really? I mean, that's not what the cloud is for. But he said that 80% of the customers he was talking to when he was back in Microsoft wanted to put those workloads on the cloud. But Azure, these guys at Azure said, no, no, no, no, that's not the right place. You know, we're not gonna, so no SLAs for that kind of stuff. So he started this company. So I think OpenStack, just by virtue of all the work that's going on is perfect for that mixed general workload type of environment. You can run cloud native apps. You can run container apps. You can run legacy apps if you want to. Of course, you know, you gotta look at the reliability of the infrastructure, et cetera. But I think it's the way OpenStack, the way it has evolved over the last several years is it's perfect for a general-purpose workload. One of the challenges, I mean, you say many legacy apps will run just fine in an upper stack environment. There we see challenges. There are some technology challenges depending on the app, but actually there's a great deal of licensing or commercial challenges, which is what puts people off. Moving a database, I won't name a database vendor, but moving a database vendor from a single on bare metal machine into a cloud can suddenly get very expensive. So those are considerations that people have to live with. Cool, okay. Any questions? Coming up on the final five minutes, any questions? Oh, sure, yeah. What would you say is the, is there much? Mike coming up, Mike coming up. Hello? Yeah. What is the toughest challenge? Why is it so difficult to operate a do-it-yourself cluster compared to your solutions? So a certain amount of that comes from the community is developing capabilities and features, and a lot of that focus and development has been around how can we make an open stack environment compare well to an Amazon or an Azure or a Google, right? We want to be able to, or even a VMware type of environment, how can we provide those capabilities? It's very feature-driven. You don't really work out what the operational challenges are until people really start operating it themselves for real, right? And that's when you started like, okay, how do I really manage backups? If I need to be able to perform maintenance on a node, how do I really evacuate all of those things in a clean way and do it in an automated way? And so it's a learning journey, right? If you have a vendor, a vendor's, we have product managers and product people that will try and look down this and figure it out. OpenStack, whilst it has a product working group, doesn't have product managers that are saying, are identifying these pockets. Yes, there are companies, all three of the companies up here contributing to OpenStack and working on there, but there's no sort of single person responsible for setting that agenda. I think you have to look at the whole open source movement as such. I mean, this is something I was told by a person who's a leader in the open source. He says that people get into open source, they are very enthusiastic about it, and they jump into it, and they start developing the software and things like that. They get a high of kind of coming up with the software. And yes, they take the software up to 90% of where it has to be. And that is where they get a tremendous amount of satisfaction. The last mile or the last 10% is where they move on to something else. And then it is left for the, and again, when you as consumers of that open source project, when you take that, you are dealt with that remaining 10%. The challenges of that last 10% which was not done by the software developers per se. And this is where the rubber hits the road. That is where you kind of have the challenges. So that's what he said, the operational challenges. Because yes, that thing has not been tested for each and every use case. That thing has not been tested for each and every configuration that you might be having and things like that. So that is where I would say that, and that's why we have Red Hat as a successful company over there, though the open source is there for a long time. And I feel that that is one big aspect of it. And then yes, all the things like, and if you look at what the distros provide is the engineering support, the packaging, the bug fixing, the testing and all those kind of things. They do those things. That's our differentiation, actually. How we differentiate between each other is they have a great way of doing things. We have a great way of doing things. You have a great way of doing things. You as an end user. So I'll give an example. So one of our largest telco customers started off with doing their own stuff, right? Using Trunk. At one point, they had 300 plus developers that were doing, you know, they took code from the Trunk and they deployed it and they ran it. They had all these Frankenstein clouds all over the place. What they found out after about a year was 200 of those developers were fixing bugs in OpenStack Trunk. They were fixing bugs that wasn't adding business value to their applications. So they said, why are we doing this? Why are 200 of our developers fixing things that these distro guys are gonna fix anyway? Because that's their job. Let's focus on what's value add for us and put those developers to better use. So they ended up using a distribution and they freed up all those guys. And the distribution company, of course, is responsible for fixing the bugs and making sure it's supported. So that was their logic, right? From a financial standpoint, from a value add standpoint, they moved from DIY to distribution. Yeah, this is not a new model. People in the 70s, big companies in the 70s used to write their own databases and then they found there was a better way of consuming database technology. Likewise with Linux, it's the same with OpenStack. We have one question here. So I'm working for one of the biggest hosting companies in the world. One of the things we're looking at right now and we kind of foresee it in the future is that a big competition to OpenStack, not today, but maybe one, two, three years down the road would be Kubernetes. I know today there's a lot of talk in this summit that you can run Kubernetes within OpenStack but we kind of see Kubernetes coming in from behind and offering somewhat similar services or alternative running workloads. I was curious how you see that. So you have to, I mean it's like VMs versus containers. At the end of the day, your VMs are not disappearing. Your existing workloads all run on VMs. So you have the whole effort of moving those VMs and contain microservice, creating microservices out of them and then running it on containers. So there's a migration effort involved and cost involved. Just like you would move bare metal workloads to VMs, the same sort of effort. So there's a lot of existing workloads that will continue to run on VMs. There are, I think it's also important to say Kubernetes is very focused around process containers or Docker containers, right? So if you're going to create 12-factor apps and re-architect into microservices and all of those things that the cool kids do, great, that's gonna be an option for you. But a great many applications are not ready to be 12-factor and microservices. You may want to take a VM and stick it in a general-purpose machine container like LXD container and that's gonna be a lot less heavy lifting but whilst lots of cool kids talk about these microservices, you know, the reality is it's still a little way off. And Kubernetes is kind of sort of like OpenStack five years ago, right?  Yeah, they've got some. So give them some time.  I mean, that's the reality of it. So we are almost out of time, couple of things before I hand over to the last question. I believe Dell EMC is doing a raffle and so after this, feel free to pick up our raffle thing and give me a... Winner appliance? Yeah. Yeah, yeah. We got a free appliance. Yeah. Actually, we do have... We do have an appliance as they say. By the way, we do have an OpenStack appliance on the floor of the, and please have a look at it. It's a running appliance that is going on over there. So question. Actually, I was just disagreed with you, Kamash, a little bit. When it comes to going on yourself, going vanilla, totally vanilla, it won't mean that you're gonna be in the wild by yourself. You have the community. Sure, yeah. The fixes come.  Meaning you're gonna have to be very aware of the challenges and tough to fix stuff by yourself if they are needed. Otherwise, the community will be there. That's for sure. The question you were asking, I think, is kind of one of the key questions in OpenStack right now, is OpenStack a product or is it a group of projects that are turned into products by people like us? And so it's kind of, that's still yet to really play out, I think. So it's not just the code, right? Again, I'll go back to ops. I'll go back to configurations.  I mean, most distro companies, these guys have juju, we have fuel. So we make it easy for you to kind of get it all up and running. So that's a value add as well. You're right.


What is up everybody? This is Chris from the Rewired Soul, where we talk about the problem, but focus on the solution. And if you're new to my channel, my channel's all about mental health. So if you're like me and trying to figure out how to improve your mental and emotional wellbeing, make sure you subscribe and ring that notification bell. And I am feeling great today. Thank you for asking. Yesterday, I was very sick. If you saw the videos on my second channel, I talked a little bit about it, but I am feeling like a million bucks today. All right, I feel cleansed. I feel like the evil got out of my system. And just in case, I got my handy-dandy tissues right here with lotion on them, these feels nice. But anyways, yeah, we're gonna be talking about some mind-blowing mental health stats. All right, and kind of the premise, kind of get you ready for this video and why I want to make it. Like, when I first started working on my mental health, like all the information out there was just overwhelming, right? Like you have so many people. It's like when you diet, you know what I mean? And everybody is just like, do this, do that. Have you tried this? Have you tried that? All this stuff. And it's just like, oh my God, right? Like struggling with depression or anxiety, it's already overwhelming enough, right? Like just life is overwhelming. So when you get all these different things thrown at you, like it can put you in that kind of like decision-making paralysis where you don't do anything. Something that helped me out a ton, a ton, which I'm hoping will help you out today is this, all right? Pay attention. You don't have to do everything, just do something. All right? So find one or two things that works for you and give them a try. And if they don't work, give them the boot. Try something else.  I love getting information from all of you, okay?  So I wanted to go through these polls and yeah, so you'll get an idea of what people are doing for their mental health and maybe you'll give them a try and I'll toss in some little facts and stuff like that along the way, all right? So like, first off, I thought a lot of people, I thought these stats were gonna be like five, 10%, but mm-mm, baby, uh-uh. So the first one is I said, do you meditate? 31%, 31% of people meditate, all right? And you'll see a pattern with these first few. They are 100% free, okay? So meditation is something I started doing four or five years ago and five minutes a day, five minutes a day, you don't gotta sit there for an hour or anything like that. One of the biggest things I see people say about meditation, I can't meditate, I can't stop from thinking, meditation isn't about stopping your thoughts, it is impossible to stop your thoughts, all right? Meditation is about noticing your thoughts and not latching onto them, all right? We sit there and we watch them pass like clouds in the sky. I was just reading a book on meditation the other day and one of my favorite analogies is it takes you from being inside the movie to being inside the movie theater and just watching. Next one, I asked, do you journal? 33%, all right? Not 100% free, but you can go to your local dollar store, I think even like grocery stores or Walmart or whatever, they have dollar notebooks, okay? Journaling is my jam.  Sometimes if I'm not like handwriting in my journal, like I'll just open up a Word document on my computer and just start just typing. Like something I realized a long time ago is that, you know, just keeping it in and keeping these ruminating thoughts going over and over and over and over again. Like when I'm able to write them down, it's like opening up this cage and just letting those things get out there, right? Another great benefit of journaling is when we get depressed, we can think that every day is terrible, right? Oh my God, this is never gonna end and all this other stuff. But when you have a journal, when you have documented proof that not every day is a bad day, you can flip through your journal on a bad day and say, oh, okay, I was feeling all right on that day. So obviously these things don't last forever. Boom, 33% again. I asked, do you talk to people in your support group? I love that so much. So human connection is one of the biggest things. So check it out. When you are connecting with other human beings, you are getting releases of oxytocin, okay? And this is for connection and not feeling so alone, right? And it's so simple, it's so simple. Like just one or two people, one or two people in your life that you can reach out to and just be like, yo, having a rough day. You know what I mean? Like for those of us in recovery, like, you know, not only do I have a support group but I can go hit up a 12 step meeting or whatever it is. One of my suggestions too is like, look online. Like Facebook has a ton of support groups. If you're into Reddit, Reddit has a ton of support groups. When we are struggling, it's easy to feel like we're completely alone and nobody understands. But by having a support group, especially people who have been through what we've been through, it helps us feel less alone. Now we're getting into the crazy stuff. Do you exercise 55% of people exercise? And check this out. I didn't even get specific in this poll, but like exercise is just physical movement at all. But it is one of the best things that you can do for your mental health. Like I'm in the process of scheduling some interviews on my podcast. One of them is a neuroscientist who specializes in depression. Dr. Alex Korb, you probably heard me mention him. But anyways, exercise releases serotonin, releases endorphins, releases dopamine, right? It also helps if you can't sleep at night. But exercise is one of the best things you could do for your mental health. Like sometimes when I'm not feeling it, when I'm not feeling going to the gym or just going for a walk, like just going for a little walk, like I'm like, okay, well, even though I don't feel like doing it for my weight, I want to do it for my mental health. And not many people, not many people go to the gym and regret it afterwards, right? Unless you like do something really dumb. But I got faith in all of you. Then I asked, do you get seven to eight hours of sleep? I thought this number was going to be like 2%. But 43% of people say seven to eight hours of sleep. So they want you to get eight hours of sleep. I typically do about seven. Now that I'm eating better and exercising, seven hours seems to do me just fine, aside from these eye bags. But that's just part of my face, I think. Anyways, getting good sleep is the best. It is up there with exercise. It's like exercise, sleep. Exercise, sleep, all right? When you sleep, your body is just rejuvenating, right? Lack of sleep. I don't even have time to go into all the studies.  Willpower, they've done studies on that, like your willpower, absolutely tanks. So if you're getting terrible sleep, you're more likely to binge eat or, I don't know, binge shop or do a bunch of things that aren't good for you, all right?  Next one, do you practice gratitude? 68%. Oh, this makes me so happy. It makes me so, so happy. So check it out. They have done studies, numerous studies on gratitude and simply writing down five things a day, five things a day that you're grateful for. And even if you gotta start out with one, it is going to boost your overall well-being. They've done studies, they show that it decreases, depression increases overall well-being. The reason being is because our brains are wired for a negative bias. We are so good at spotting the negative, right? Our brain is wired like that. But when we retrain it to be grateful, amazing things happen. I cannot explain this to you. I've had my son do a gratitude journal every night. He has a little alarm on his phone. And I'm sure there's a variety of factors, like he has a great mom and he's a good kid. But since he's been keeping that gratitude list, I've seen a huge change. Like for example, one of the reasons we started it, I noticed after school, he would, when I would ask him about his day, he would tell me like a bad thing, right? And I'm like, this ain't right, you know what I mean? And I just said, hey, here, start keeping a gratitude journal. He only writes down three things, by the way. And over time, that doesn't happen anymore. That doesn't, like after school, he'll tell me about good things that happen. And I believe it's because the science is valid and he's starting to spot the positives rather than the negatives. All right, so all of those were free, okay? F-R-E-E, free, okay? But this next one, I said, do you take antidepressants or other mental health medications? 29% of people said yes. So first off, if you are worried about taking them or you like, you know, think you shouldn't have to, just realize you're not going to be the only person taking these medications, all right? I take medications, 29% of everybody who answered this takes medications and trust me, I get it. Medications aren't for everybody. But like, I had to learn that medications aren't the end all be all. They are not going to fix all of your problems, right? But say for example, like with depression. With depression, it's so hard to get the motivation to just even get out of bed in the morning. When you're taking these medications, it gets you to that baseline where you can get some stuff done, right?  The last thing I'll recommend when it comes to medications is, always remember two things. Always remember these two things. Just because you didn't respond well to one medication doesn't mean all medications are bad, okay? You have to work with your doctor. You have to follow up with your doctor. Like that's something that I had to do. I had to find the right medication for me. Like they actually like, I don't know if your insurance will cover it, but some, you can actually do like genetic testing, which will tell you which medications you'll have a bad reaction to. It's pretty dope. I used to, when I worked at the rehab center, like we actually did, we had like a genetics testing place.  These medications don't work, right? So get you some. And if you have like Medicare or there usually are free clinics in different cities around the United States, if you live in like a decent size city, like here in Las Vegas, I think we have three or four. And the wait times might be a little bit long because they're free, but like if you're really struggling with depression or anxiety, like I highly recommend you look into that because that might be the first step towards getting better. And lastly, I asked, how many of you have a therapist? 34%. Hi, I'm one of those people too. Therapy is so, so, so amazing. Like when you find the right therapist, it's like sometimes finding the right therapist is like dating, okay? Or it's like medications. I don't know why I jumped to dating, but sometimes you gotta find the right one, okay? So, no, it's kind of like medications just because maybe they didn't work in the past. Doesn't mean they're not gonna work now. You might have had the wrong therapist. You might have had a bad therapist. I can't tell you how much it bumps me out when I see people who they had a bad experience with one therapist and it just soured their taste for therapists forever, right? Like there are a million different therapists out there. Get a new one, try a new one, right? I've had some DMs recently asked me about therapists and like, do I know anybody who specializes in this or that, you know, whatever. Here's what I recommend. Talk to your doctor, talk to your insurance company and see if they can recommend a therapist who specializes in what you're struggling with. Anxiety, depression, trauma, borderline personality disorder, whatever it is. You know what I mean? Typically like your insurance company will have a list of that stuff. I also recommend, I might do a video on this. Like if you want me to do a video on this, let me know in the comments. We're breaking down each type of therapy. Like for example, like cognitive behavioral therapy, dialectical behavioral therapy, rational motive behavioral therapy, all that kind of stuff. Because then you can narrow it down even more and say, okay, that therapy sounds like it would work for me. Let me find a therapist who specializes in that. For example, borderline personality disorder, DBT, very effective. If you're struggling with trauma, EMDR therapy. A lot of people benefit from that type of therapy. So you just gotta understand how these therapies work. Find a therapist who specializes in this and give it a try. And if that therapy doesn't work, call up to another one. My therapist, she's well versed in quite a few of them. And since I'm always doing research, I'm like, hey, I wanna try that. Like she's been helping me with REBT, rational motive behavioral therapy. And that thing's my jam because I get really irrational with my thoughts sometimes. And that helps me get back on track, all right? So talk to your doctor, talk to your insurance company. Me personally, I use BetterHelp online therapy. It's a really cool service. I've had my therapist for about a year now. And they also help support the channel. So if you wanna give BetterHelp online therapy a try, there's always a link down in the description. Basically what that means is you get affordable online therapy. A little bit comes back to support the channel. But I don't really care where you get therapy from, but just please for the love of God, give it a try. So in the last video, where I talked about my little weight loss journey, I asked you all for your best weight loss tips. And this one comes from Beck Finnerty. And she says, stay away from fructose and corn syrup as they make you hungry in crave. It's quite addictive. Girl, I am working on it. Something I'm trying to really get better at is recognizing processed food and everything like that. Especially foods that have empty calories.  And then you're hungry right after. You know what I mean? So thank you Beck for reminding me I need to get better at that, all right? So for this video, down in the comments below, let me know what your favorite mental health practice is out of everything that we listed, all right? But thank you to everybody who participated and answered these polls. I also did one more thing, but this video got too long. So I'll break that down into another video. But as you can see, as you can see, a ton of people are out there doing just one thing for their mental health. And some of these people might be doing multiple things. You never know, baby. But anyways, that's all I got for this video. If you like this video, please give it a thumbs up. If you're new, make sure you subscribe and ring that notification bell. And a huge, huge thank you to everybody supporting the channel over on Patreon. You're all amazing. As well as everybody who buys my mental health books at therewiredsoul.com as well as the Rewired Soul Merch, like the logo shirt, all right? Thanks again for watching. I'll see you next time.


I love you and he is a faithful God and all the things that God has for you. He's gonna begin to reveal them to you today and welcome to Hope Today. I'm Tom Hollis, I'm here with Amanda Brocker and we're gonna see some of that, of some of what God wants to do for you today. It's gonna be a powerful program Amanda. It sure is. I'm so excited. We have our very own guest Sue Willis here in the studio. She is the founder and executive director of Beyond Survival Ministries and I just have to say, if you have had any trauma in your life ever, this program is going to minister to your heart and you will be changed. If you know someone who has had trauma in their life, I would encourage you to pick up the phone or send a text, let them know, hey tune in to Hope Today because you are definitely gonna receive Hope. Absolutely and by the way guys, don't let the women lead the way here. Let us be involved as well. We have suffered trauma, many of us and have a need of healing, a need of a touch of God. And if you're a guy that has kind of suppressed that and said, well, it doesn't really matter, God wants to heal you from that. He does, absolutely. And you're gonna find out about that today. Also, I just want to let you know something fun that we're gonna be doing, special edition of Stump the Viewer. You know we have Stump the Host. Well now we have Stump the Viewer and it's on this Thursday's Hope Today to celebrate our 45th anniversary of being on the air. We'll be giving away a special prize to one randomly selected viewer who enters the Stump the Viewer contest. Once again, that's during Thursday's Hope Today. So you're gonna wanna make sure that you tune in and see how you can enter and win if they get it. That's right, who doesn't want to win a prize? I know, absolutely. That sounds amazing. Well, just thinking about the solar eclipse and everything that just happened, you know, there was something that we were thinking about with creation. What were we thinking about? I don't know, but I'm thinking of Genesis in Psalm 19. It says about the heavens declare the glory of God and the firmament shows his handiwork. So, you know, as we were all peering up into the sky yesterday and looking, we know that it's God's great work that caused all of this. And like he also made our bodies like his great work. We are his workmanship. And so when we're talking about our viewer benefits today to this program, we're gonna touch on physical benefits, spiritual benefits, emotional benefits, relational benefits, financial benefits. We're coming at all. That's right, you've got to text someone and tell them, tune in to Hope Today right now. All right, well, let's go to break and we'll be right back with this powerful message. God is calling you to do something significant in the earth for him, regardless of your age, skill set, or perceived limitations. What's holding you back? When you give to support Cornerstone Television this month, let us bless you with Rick Renner's life-transforming book, Chosen by God. Every page will help you overcome your limited thinking and follow God's plan for your life.  This book will thrill you with the possibilities that await because you are chosen by God. Request your copy when you give by calling<PHONE_NUMBER> or donate online at ctvn.org slash donate. Thank you for helping us spread the gospel through life-changing programming like Rick Renner, Hope Today, Hard Questions, and more. To keep your favorite programs coming and receive Chosen by God, donate today. Well, our next guest is the founder of Beyond Survival Ministries where she currently serves as the executive director. Sue Willis has more than 35 years of experience in ministry and her organization is making an impact by proclaiming the good news of the gospel to our lost, hurting, and broken sisters across the globe. Sue, welcome to Hope Today. Thank you for having me. Absolutely, this is such a treasure for me. I just love you and I appreciate your heart. I've got to see you working behind the scenes so even though you're the top dog around Beyond Survival Ministries, you walk so humbly with the Lord and it is greatly appreciated. But give our viewers just some of your story, a little bit of your background, and then how you came to Christ. Okay, well, actually during my teen years, I'll just start with their oldest of eight children. So, but during my teen years, I went through a very major trauma in my life. I was 17 years old. It was very traumatic for me. I suffered a great loss. And, you know, at that time, just for me personally, the effects that it had on my life, I was so surprised but also didn't understand. You know, I knew the feelings I had but I didn't necessarily understand how to process through something like that. And for me, I was raised up, you know, to know about God, but I was not a born-again Christian. But I will say that through that trauma and just crying out to God, that trauma God was able to take to draw me to him. And when I was 20 years old, I received Jesus as my Lord and Savior. And I was born-again and just a fun piece. I never heard the term born-again. I never heard the term. I was in my bedroom just crying out to God and I can tell you that he visited me. I love that though, because it's so real. It's so real and kind of raw.  You knew you needed God. I did. And somewhere deep in, you know, we all have that need. We don't realize it, but yes, deep in I knew to turn to him as my source. And many nights crying out to him, but then one night he just visited me and it was so simple because I kept crying out to God. And it just dawned on me. He's not answering me. This is so childlike, but so true. And I went, God, why aren't you answering me? And all of a sudden it just quietly came to me, I asked Jesus. And so I said, Jesus, would you ask the Father God please? Cause I was asking actually to not go to hell because I thought I was going to be dying. Well, in that moment is when his presence filled that room and later when I read the scripture, no man can come onto the Father, but by Jesus it was like, oh my goodness. I've always had that. You can never, I never doubted my salvation. And when that happened in my life, I had such a desire to go and tell people about what Jesus could do. And he healed me. And so that was something that I, it was just a message that I shared my testimony, but as I shared my testimony, people came to the Lord. So that was many, many years ago. So it led you though to a job where you were able to impact many lives of women of all ages, but predominantly teenage years. And God gave you a curriculum through working with these women year after year and talk to us a little bit about that. Well, very early on, I started a Bible study in my home and over 300 women over a 10 year span walked through the doors. It was during the charismatic movement, which, you know, but I got to really hear, God just somehow blessed it. And I learned a lot about what others struggled with. So through that time and knowing Jesus is our answer. Yes, he uses many other things, but our source for healing, especially talking about the different traumas in life ultimately come from him. So at a very young age in the Lord, I just simply took him at his word. If I could just say it like that. And when I would read the stories of those that he touched in the Bible, I just, they were so alive to me, but I could also see deeper into their stories that, you know, we read in just a few verses that someone was sick and then three, you know, verses later they were healed. But the depth of the trauma that many of those went through, like Joseph, like Hannah, you know, different ones in the word, they had their places as well inside that there was need of an emotional healing at touch from God to really walk in the joy and fulfill the plan that he had for their life. So you're saying that even though we come to the Lord, because I've heard some people say, well, I've come to the Lord and that's all in the past or that's under the blood or I don't need to think about it, but there's a time to bring those things to the surface to just be healed, right? God wants to make us whole. So can you talk a little bit about how God led you into that? Yes, actually Ecclesiastes says what? There's a time to heal. Okay, God says there's a time to heal. Through ministering, I was at the Pregnancy, I volunteered at the Pregnancy Resource Center and it was at that time I got to hear a lot more of stories with trauma attached. I'm gonna talk about something that we don't like to talk about, but sexual abuse, molestation, talking to women that had gone through things as a child that they never shared and God, the only thing I can say is you gotta hold in my heart through this because I was never seeking this ministry. I wanted to pastor women's ministry and I was experienced in different things, but it was during that time and the need specifically started coming to the Pregnancy Resource Center pastors were calling and individuals, I need help. I have a woman sitting in my office, I have a family who brought their teen daughter that was just raped on campus and so they asked me would I see these young girls and that's how it started and then they asked me to, each time a call came and it's actually in the curriculum, after six young girls, I said, Lord, I don't have enough hours in my day to minister to these women. I knew they needed him and so I went to the executive director and I said, do you need to get some kind of Bible study or something here to minister to these needs and they said, well, our vision is more for the pregnancy and I said, but along with the pregnancy comes a lot of trauma behind.  And I said yes and he just gave me the curriculum, the steps, the journey to taking survivors through a process of actual inner healing to where they don't have to carry that pain and one of the main things Tom and Amanda is, we don't really know how to do that, is that true? I use a visual of a vase. I wish I would have brought it today but I think they're gonna show it, okay? And if you look at that vase, isn't it beautiful? That vase, and it reminds me of Psalm 139 where we were created in the image and likeness of God and Jesus, the father was so involved when we were being wove in our mother's womb, right? And as we read those verses, it goes on to say that he scheduled our days, he ordained our days that we should walk them out and so many people believe that the tragedies in life or those places of sexual abuse, trauma, spiritual abuse were part of God's plan and they weren't. He can bring good out of it and so I liken that to that vase where when those things come and those traumas hit and that sexual abuse and that tragedy comes and then I'll pour that vase out and what happens? There's a brokenness, there's a shattering of our hearts in the emotional realm and come on, we're all survivors, right? I think so and I commend survivors but we all do it. The first thing we do is we try to what? We can see the big pieces that need put together and we keep, we put some of them together for a while but then there's those little shards that are part of the brokenness and I'll never forget the day the spirit of God said to me, Sue, even though shards are part of my sons and daughters hearts, he doesn't push them away, they're part of the whole and so he just really, really brought to me how much he wants wholeness for his sons and daughters. He's coming back for us, right? For a bride with that spotter wrinkle and part of that sanctifying process is bringing us to wholeness so that we can serve him with our whole heart. So in a time to heal curriculum, I think we might have a still shot of it but I had the opportunity to go through the course and I would love for you just to bring one of the Bible characters to life. If you could do that during our program, I know we have limited time but it's so important I think for us to just see. I'm used to preaching this so I will just share it, paraphrase it but as I shared, many in the Word of God went through trauma but the woman with the issue of blood that we read about in Mark chapter five, when you begin her story, it starts out with there was a woman, okay? She didn't even have a name. There was a woman and in different translations said she had an issue. Now she had a physical issue which was a hemorrhage but this physical issue that she had went on for 12 years. This was a long time. Now it's easy to look and say she needed a physical healing of what she did but if you dive deeper into her story and you really look at because of what she was enduring, she was considered unclean. All right, she had to actually say ceremonially I'm unclean when she was not. How did that affect her emotions? I think she suffered some trauma. Don't you think within her emotions but when she heard about Jesus, I don't have time to share the emotions today but we know that when she heard about Jesus she thought to herself, if I could just touch the hem of his garment I shall be made whole. And I love that because the battle is in the mind. What did she thought according to the word of God? All of a sudden her focus was on him and not on what she was going through but the Bible tells us that she had to press through a multitude. And sometimes we have to press for what we have need of too to get to that place of his presence but despite that she should have been crying out unclean despite maybe the voices that were going on in her head you're gonna be exposed. She was so desperate for her healing that she pressed through that crowd but listen to this. When she finally got to the place of his presence come on that was faith for her to press. Okay, the Bible tells us she came from behind and that's a key word right there when we carry baggage. You know, it's a key word we want Jesus. We turn to him but how many of us because that baggage still remains inside come behind and we wanna look at our loving God. She touched the hem of his garment and immediately her physical condition was healed immediately. And I like to say she thought praise God inside but I'm getting out of time before someone finds out, right? So she turns to go back home and she hears the words who touched me and we read in the word fear and trembling. Now there are many ways to share this message but this is how I feel to share it. I believe she had fear of exposure. I believe she had felt like now everybody was gonna know her all her issues and we don't even know them but he called her back and she came and knelt at his feet fearing and trembling the Bible said and she said the Bible says she told her whole story. You know, there's healing when we can tell our whole story. We all have a story to tell but in Jesus it can be framed in redemption. We don't know what she said but look at God and this is the love of the Father for all of us. He called her back face to face. He didn't want her coming from behind. He wanted her to know that he loved her and in those last few verses reread he says daughter, right? There was relationship, spiritual relationship. He said go in peace. Where do we need peace in our heart, in our emotions? And then he said now go and be healed of your affliction. When we've lived in trauma or abuse or heartache or brokenness for so long, even when he touches us we gotta learn how to walk in that new found freedom and that's what he was saying to her. So if ever I feel there was a scripture that says Jesus wants to heal the whole person that's there. Let's just look at those things that you mentioned earlier. The Bible said she spent all her money trying to get help, right? But she couldn't find it. No more was she gonna have to, so she got healed. She got ministry and her finances, relationships. She couldn't have close relationships. She got a physical healing. She got a spiritual healing. She got the whole work and relational as well. She could have fun with her friends again. That's right. If we could just pull up that scripture, I want you to read that. I feel you're to read it. And then if you would pray for that one that is watching, that's coming from behind but the scripture's gonna be in the prompter there. Do you want me to read that? Go ahead, I believe you're to read it. This is out of Mark 5, 27. The Bible says that after hearing about Jesus, she came up in the crowd behind him and touched his cloak. And that's the key word today that I want to minister to those of you that are listening. What are you hurting over? What are you struggling with? What traumas may have happened to you even as a young child and you know that they affect you today? Do you know that God cares? He cares more deeply than you can ever realize. And just as she came from behind, you find yourself coming behind with your worship, with your love for him. Well, I believe today he's saying my son, my daughter, I'm calling you face to face. I love you with an everlasting love and I invite you to invite me in to heal and bring you wholeness that only I can give. Beautiful, beautiful. And I was just thinking about, you talked about Emily as a lady that went through your course. And if you could just, because this is so real. And I know every class that I sat in, I was, the Bible just becoming so more touchable to my own life. And I love that. So talk to us a little bit about Emily. Emily, you can actually see her testimony on our website that Emily came to us as a young, oh, she was probably in her early 20s.  It began when she was a toddler and it was happening right in her home. And if you hear Emily's words as she shared with us, she learned at a very young age, she felt like that there was something wrong with her. She felt shame. She felt guilt. No, she was innocent, but she felt all these feelings and they became a part of her. And she said, when it started out, she felt like something was wrong with her. It grew into she was wrong. And see, again, when we have been abused, sexually abused or even spiritually abused, there is such a breakdown of who we are that we allow those things to identify us. But honestly, as Emily got her freedom when she came through, it was a beautiful, beautiful thing. And I encourage you to listen to her testimony. She's one of our trained leaders today, but out of her whole story was how God healed her. And you know, Amanda and Tom, what has happened to us in life does not define who we are. That is so true. Does not. What challenges, I mean, we've talked a lot about how this is ministered to women, but you're ministering to men as well. What are the challenges there? I know guys we don't necessarily like to open up as easily, but what have you seen? Amazingly, we did. Primarily for years, we ministered to women, but then men started coming forward. And I actually got a call and I felt because I was a woman that I shouldn't necessarily meet. So I called my pastor advisors and they came, but I came to find out that men hurt just as bad. They just aren't as ready to talk about it. Now that was probably about 10 years ago. Now they're coming forward. Pastors are coming forward. Individuals, counselors are coming forward. I believe they know that our ministry center is a safe place because thank God for the local church, all right, but sometimes people don't necessarily want to share this at the altar on Sunday morning. And that's why we are so about equipping the local church to be able to do this ministry because we train others to do it, but men, they've come forth so much. We had up in Lancaster, Pennsylvania within the Amish and Mennonite community just recently and we're headed there in two weeks. We did a training and I can tell you, men came to the training to train and broke. We're used to seeing women do that, but the men began to break because those little boys at one time went through the same thing. And so here they are as men that we actually have coming in May, it's two days. Friday night and Saturday morning, an actual weekend just for men to take them through. The different ways churches can get involved. If you want to bring a time to heal to your church, it is amazing. I mean, the course itself, but Sue, you guys have different options. So you do a one day workshop, they'll come. We were invited. That's a new thing. We'll put these on our website. So you can go to ctvn.org and we'll have a link there to Sue's website so you can get all that information. This is so powerful. Sue, we just appreciate you immensely. Thank you so much for having me. Yes, thank you guys. Thank you so much. And again, I believe we're in an hour where God is pouring out his spirit and wanting to bring his children to wholeness. Amen. Thank you so much for sharing. I mean, and that is, I think the key thing today is that God wants wholeness for you. Have you ever thought about that? It's not just some, you're not accepting a religion. You're not accepting a code of things that you have to do. There are certainly commands and things in the scriptures but the main thing is that you're being saved by his grace and then you're coming and saying, God, make me that person that you've always wanted me to be. The world, the flesh and the devil have put all these things on me. They've twisted some things inside of me. And Lord, even though I know you, I still feel those things there. God wants to heal you. He wants to make it fresh and new.  You were always meant to be that new creation, that new person that you're becoming. It is a powerful thing. Don't let this day go by without seeking God and saying, God, give me that new hope and you're gonna meet him in a special way today. On tomorrow's hope today, discover how you can turn sorrow into joy. Pastor and author Kent Christmas explores how you can pursue God's purpose for your life no matter the challenges or storms that you may face. Don't miss tomorrow's hope today. Cornerstone Television wishes to thank all our faithful viewers whose consistent prayers and financial support have made this program possible.


Yeah, service is something like when people think of spirituality Many traditions like mother Teresa sometimes comes to mind when people think of a genuine authentic service and I think it's it's kind of like a Stepping stone idea in the sense that The mind is kind of addicted and stuck in this ego centric mode Where everything is you know me myself and I in a small eye sense, you know look out for number one You know Always watch out for number one the number one being the personality self That service can be a mechanism that And a metaphor that the Holy Spirit uses to kind of pop the mind Listen to mine from this very ego centric Perspective of doing everything for one's own personal self and Underneath that of course is the belief that I can create myself That I can make myself and the way that I want to be and I can remake myself And I can reinvent myself. You know, there's a lot of spirituality to talk about reinventing yourself There's even new age philosophies. I remember I going into a new age store and and Reading a magazine and it said to create your own reality right on the front cover and The people say yeah, the course is new age like that. You can create your own reality. That's more like the secret It's more like you can Can invent your own illusion is a better Reinterpretation of create your own reality is just invent your own illusion which really doesn't make you happy To invent and reinvent Illusions because illusions are false. It's just like playing around tinkering around with the false so in one sense this sense of service can be a very helpful step and It's more of a backdrop though for Watching your mind for getting out of Just thinking everything in terms of how can I benefit the personality self? because the ego can is Metaphor along the journey the ego can jump in there with this service idea and run with that too and Wow, you talk about burnout Be a kid into burnout in a big way when you get into the you know Nothing nothing greater than you know laying down your life to serve others and this and this and this You can seem to be so other directed that you just totally burn out And it's no wonder why people that get into like social services You know they get in for wonderful reasons, you know, they get in to be helpful Kind of altruistic real loving reasons and then the ego is like a spider sitting back there Going for the old service one here I can twist this one around then Burn you out and get you disillusioned in a hurry and so there starts to come a point on the spiritual journey where you start to Train your mind to see that everything is is thought and that really the service you're doing is learning how to forgive and release release attack thoughts from consciousness Now that's service That's really getting into service. That's lesson 23 of the Course in Miracles workbook. I can escape From the world I see by giving up attack thoughts It's almost like the culmination of those first 22 lessons Just giving you a here's where you're going for this is your ultimate service and In that sense people had said to me, you know, if it is about service, then Then you see someone like Mother Teresa who was known for you know Serving and she said it was here to serve the force before and you have somebody like we'll say like a Yogi or a meditator who seems to be just sitting on his bum the whole time And it would seem like from the service model. It's like get out of your cave and save somebody Feed somebody help somebody you could see from the form when you try to gauge and judge the service You can't really do that, you know Jesus has a section in this course where he calls it you know, I need to do nothing and He's actually saying in there that you really want to show your loyalty loyalty to me and escape thousands of years of struggle Just do this one thing for me And it's I need to do nothing, you know, it's really practice this Of course there are those that try to practice that and go this isn't so easy The practice I need to do nothing. That's pretty high High form of thing and then he says in there, you know from this point of stillness and silence You will be sent on many busy doings Let's go. Oh great. You're gonna be loyal and and do nothing and then I get sent on many busy doings But it's it's just kind of getting lined up and yielding into that purpose So that you get into this state of mind where you see that miracles are involuntary that you can't control and direct the miracle and neither can you judge this sense of service in terms of form because true service is really an Alignment in purpose. That's what the service is


Namaste. Welcome to the session principles of combinational logic circuit. At the end of this session students will be able to explain the concepts of combinational logic circuit and design a combinational logic circuit. These are contents. Digital circuits are classified as combinational logic circuits and sequential logic circuits. In today's session we are going to discuss about combinational logic circuits. So what is the combinational logic circuit? So combinational logic circuit has n number of inputs let us consider a0 to an minus 1 and m number of outputs let us consider y0 to ym minus 1. So in case of combinational logic circuit outputs at any instant of time depends on the input present at that instant only. So it means that output does not depend upon the previous or past values of input or output. So there is no need to remember the past values. So it has no memory element. Now there will be no effect of sequence in which inputs are applied on the output in case of combinational logic circuit. There are various examples of combinational logic circuits which are used in digital circuits such as in arithmetic and logical system. The combinational logic circuits used are adder circuit, substractor circuit, comparators etc. In data transmission systems combinational logic circuit used are multiplexers, demultiplexers, encoders, decoders and in case of code converter systems code converters may be binary to other code conversion, bc to other code conversion or it may be gray to other code conversion. Similarly bc to seven segment converter such as there are various digital circuits where combinational logic circuits are used. Now let us see design of combinational logic circuit. Logic gates are the basic building block of digital circuits. So in combinational logic circuits basic gates and or not or universal gates as NAND and NOR are used to design. There are different ways of designing logic circuits. If you have true table from true table you can obtain Boolean algebra equation and from Boolean algebra equation you can construct a circuit or if you have only Boolean algebra from Boolean algebra you can directly design a digital circuits that is combinational logic circuit. Now let us see design of adder circuit. First of all we are going to see half adder. So half adder is also a combinational logic circuit which adds two single bit binary numbers. Now before designing half adder first of all one should know binary arithmetic. Binary addition rules are 0 plus 0 sum is 0 there will be no carry, 0 plus 1 sum is 1 with no carry, 1 plus 0 sum is 1 with no carry but when it is 1 plus 1 sum is 0 with carry 1. So according to these rules we can draw block diagram for half adder where we are considering two single bit inputs A and B. So it will give us output as sum and carry. When the next step we are going to write true table. So true table is nothing but all the combinations of input and respective output. So in case of half adder we have two inputs A and B. So there will be four combinations 0 0 0 1 1 0 and 1 1. For 0 0 sum is 0 and carry 0. For 0 1 sum is 1 and carry 0. For 1 0 sum is 1 and carry 0 and when A and B both are 1 1 we get sum as 0 and carry as 1. So from the true table we can observe that we are getting sum for the combinations when A and B are 0 1 and 1 0 and we are getting carry for only one combination when A and B are both 1. So in the next step we are writing logical equations for half adder. So logic equations are written for all the output as we here we have two outputs sum and carry we are going to write equation for sum and carry. So the equation for sum as we know that we are getting sum for two combinations 0 1 and 1 0. So equation becomes A bar B plus A B bar. The same equation is written in terms of mean terms as summation small m in the bracket 1 comma 2. And for carry we are getting output for only one combinations when A and B are 1 1. So equation of carry is C is equal to AB. So in case of mean term equation becomes summation small m in the bracket 3. So in the next step we are drawing logic circuit for the half adder. So based on these two equations first equation is sum S is equal to A bar B plus A B bar which is nothing but XOR operation. So same equation is written as A XOR B and carry C is equal to AB. So here we require two gates XOR and A AND gate. So this is the logic diagram for half adder. So let us see design for full adder. So full adder is also a combinational logic circuit which adds two single bit binary numbers along with carry if any. So difference between full adder and half adder is that. So in case of half adder if there are two bits along with that if there is a carry present then it will not consider carry but in case of full adder not only it adds two single bits A and B and it also adds carry if present. So here the answer will be 1 plus 1 is 1 plus 1 gives us sum 0 and carry 1. So let us draw a block diagram. So as we know that we have carry here. So inputs are A B and C in and outputs are sum and carry out. So based on block diagram let us write truth table. So as we have three inputs A B and C in so there will be total eight combinations of input and we are getting sum for combinations when A B C in are 0 0 1, when 0 1 0, when 1 0 0 and when A B C in are 1 1 1 and we are getting carry out that is C out here for combinations when A B C in are 0 1 1, 1 0 1, 1 1 0 and 1 1 1. So from this truth table we can observe that we are getting some for four combinations of input and carry out that is C out for four input combinations. So logic equation for full adder the same equation is written as summation small m in the bracket 1, 2, 4, 7. For carry out the equation and same equation is written as summation small m in the bracket 3, 5, 6, 7. So there is a technique where we can reduce logical equations. So take a pause here and recall which technique is used for reducing or minimizing the logical equation. So the technique which is used to reduce or minimize the logic equation is K map. So K map is a graphical representation where the min terms or max terms from a equation are represented on the map and putting once into the cells 1, 2, 4, 7 what we get is so there will be no pair, quad or octet. So we have to consider individual terms. So equation of sum becomes as earlier. So there will be no reduction in this equation. Now let us write K map for carry out. So by putting once into the cells 3, 5, 6, 7 we get three pairs and these three pairs will reduce carry out equation as C out is equal to AB plus AC in plus BC in. Now let us design logic circuit from these two equations sum and carry. So for sum as we know that there are four terms here we require four AND gates and output of four AND gates are given to OR gate which you will give us sum as output and for carry out equation is AB plus AC in plus BC in. So we require three AND gates here and output of three AND gates again given to OR gate that will give us C out. These are references. Thank you.