Hello and welcome, I'm Jason Venner. I'm the VP of Architecture and Technical Marketing for Contra Long Cloud at Juniper Networks. I have spent probably the last six years working in the OpenStack space. I was the chief architect at a company called Morantis for five years prior to that and I built a couple of versions of eBay's clouds and PayPal's clouds. And we're gonna talk about OpenStack Advantage for the hybrid cloud world. I'm gonna talk a little bit about sort of the architecture that I expect you're all moving towards. We'll talk about the advantages of the public cloud, advantages of the private cloud and then of course hybrid cloud. I'll go through a few case studies and consumption models. I'll talk a little bit about ways, things to avoid to learn from others mistakes and we'll have a question and answer session. I've spent a lot of time helping companies through the digital transformation going from legacy into the cloud world so those are valid questions to ask. So this is a token architecture slide since there was architecture mentioned in the presentation about the kind of model I expect you're gonna end up in. You want to end up in a place where you have a pass layer that's ubiquitous across all of your clouds so that the behavior and APIs for your applications and services is consistent across all environments and your operational and management tools can be the same. You want to have a cloud management platform that's driving all of this across all of that and you wanna have a continuous delivery pipeline that's feeding changes in. You'll also need to have fairly comprehensive monitoring and analytics feeding back into your smart orchestrator and feeding into your data warehouse so you can make decisions about what products and services you want to extend if you're moving to a continuous, in your continuous delivery model because you're gonna be making your investment decisions much more quickly rather than the sort of legacy I'm gonna make this and in three years my customers are gonna experience it more. Public clouds, why do we love public clouds? Public clouds work. You no longer have people run around your data center chasing hardware failures, chasing network issues, trying to figure out why an API server for the infrastructure is down. Everything is there all the time and there's no capacity. You don't have to deal with your procurement people or your data center placement people. You can get the capacity you need when you need it. There are all the services you could ever imagine. The downside of this is you end up in a situation where you can have unexpectedly large monthly bills and if you start to code to the APIs that your cloud provider is offering you, you find yourself in a situation where it becomes very expensive to move out. If you need special hardware or you have pet applications that require higher levels of uptime, you're also usually unable to do those in a public cloud. Finally, we talk about the data protection requirements. There are a lot of companies today who really wanna keep their data in their data center inside of their firewall and they don't trust that in a public cloud. Also, I haven't seen an Amazon API for mainframes yet. Many of the financial service players are still running their general ledger systems through a mainframe. So I said that. Trying to explain to your security compliance team that the servers are run somewhere else, they have no access to the infrastructure can really be a very difficult thing. In addition, I spent a lot of time building systems in the financial services sector and anything that can be done as a cash equivalent becomes a high value target for hackers. And in today's world, we have state sponsored hackers going after our banks and other critical infrastructure opponents. Keeping these things securely inside your firewall makes a lot of sense. One of the, I suppose many of you remember the sort of YouTube video of somebody hijacking the control system on a Jeep Grand Cherokee about a year ago. You don't want that happening to the X-ray machine that's setting up to do a CAT scan on you. You don't want it happening to any of the medical devices that are doing invasive things on your body. We see robo-surgery systems coming up fairly fast, particularly for people in remote locations, and you wanna make sure that no one's getting at those. So these really belong in highly secured private systems. So for our private cloud, let's talk about, I've spent, I've installed more OpenStack clusters than I wanna think about starting in the cactus timeframe. It's painful, it requires a lot of skill and keeping it operating requires people who are system administrators, network administrators, Python programmers, and OpenStack experts. If you're a small player, that's a lot to take on. If you're a hyperscale player, that makes a lot of sense. The other interesting problem for most of the OpenStack users is the distro vendors will come in and say, I don't care what you're using to manage your current physical infrastructure, what you're doing to manage your Linux distros, I don't care about your patch management service.  Doesn't happen. So this is being one of the reasons I think you saw at the summit that this is the summit of managed OpenStack. Managed OpenStack lets you, going back a step, I've been in a lot of cloud projects where the time from initial, I want to do this OpenStack project to real first customer production workload can take a year sorting through all of the hardware and physical infrastructure and operating issues and with managed OpenStack, we see people up and running inside of a day and once you have been managed OpenStack, your experience is very much like the public cloud but it's in your perimeter. It just works. You have somebody to call, they're maintaining it to SLAs, you consume. You have to worry about capacity management but that's about it. Hybrid, we're in a situation where truthfully you don't want to be locked into any platform, whether it be a hybrid cloud or OpenStack itself. You want to be able to run your workloads on the platform that makes sense for you at the time you choose. This implies that you're going to be in a hybrid cloud situation at all times in the future. More to the point, you may have infrastructure on vCenter that's not moving so you're always in a multi-cloud or multi-environment and we'll go into the nothing like having leverage over your vendors. One of the key challenges in a multi-environment situation is unless you carefully orchestrate your pass and operations layers, you end up having to learn multiple stacks which goes back to that problem we had with some of the earlier OpenStack installs where you had your traditional stack that your IT organization you had operate and you had this OpenStack stack that nobody in your organization understood. And when you start operating in five or 10 or 15 environments, it becomes very important that you have a consistent behavioral experience across all of them for everybody. Did everybody enjoy the interop challenge results? Yeah. One of the things that you saw in that was people are moving up to a pass layer to provide the consistent behavior so we see Kubernetes really becoming the passive choice for people. So this is a sort of distillation of a lot of experience over the years. Where do I want a particular workload to go? You really want highly dynamic workloads to run in your public clouds because then you don't have to maintain huge reserve capacity for them. It's possible for people, I need an analytics job and I need 50,000 servers for a couple of days. You can do that in the larger public clouds. You tell your IT or your data setter person that you need 50,000 servers for a week and it's not gonna be a fun day. Anything with a critical security requirement, you're gonna run inside your secured firewall. Your compliance people will be much happier and if something does happen and your CEO has to go in front of Congress about something, they'll be able to say, look at all the precautions we took. And workloads that require consistent performance often do better on dedicated hardware. You know, I'm sure the public cloud providers will tell you that if you're running large MPI jobs, like computational fluid dynamic jobs, they'll run just fine in the public cloud. I used to run weather simulation applications for NASA and on a dedicated OpenStack cluster, I got roughly 10 times the performance I did in the public cloud because of the variability in the performance of the different virtual machines, even when I was selecting for 10 gig non-blocking switch connectivity between the servers in the cluster. 10X makes a big difference. In DevTest, you really need to have it span all of your environments because if you're not developing and testing on something that is functionally identical to your production environment, your testing is irrelevant. How many times do we hear it worked in my laptop? In the world that we're building of continuous delivery in multiple cloud, that's a critical fail.  And more to the point, all of this needs to be automated. You can't be manually intervening with your environments. Way back in the sort of pre-devop days, I was running search at a small company and we were making a major transition in our search and I wrote up an 18 step transition plan for each of our search clusters for the operations team because they were the ones that touched the hardware. And they would, every night they would do one cluster and I'd come in in the morning and they would have skipped steps seven through nine. And I would have to go manually, fix all of the clusters and they did this repeatedly for 18 clusters. It's like, dude, what? If I had actual automation for that, it wouldn't have been a problem. And in our world today, 18 is a small number, thousands probably more real. Particularly as you're moving into the IoT world where you're starting to run edge services globally. We go back to the need for true continuous delivery and testing that is relevant and valid for your production environment. So that your test environments and the deployments and the data sets need to be consistent so that you know that what you've just tested will behave the same way in your production environment. If people are ever touching something in your production environment, you've essentially failed because you have a situation where you no longer have a reproducible scenario. So you can't replicate that across all of your environments reliably. And more to the point, if you have to have a compliance audit, you don't really know what happened. I've been a firm believer for many years that the holy grail of these modern applications is that there are no user visible failures. The key here is user visible. You're continually gonna be experiencing failures in your environment, but if the user experience remains consistent, it doesn't matter. So how do you mitigate the visibility of failures? One is you're looking at your environment and you're trying to react, or your automation is reacting before something actually causes a user impact. So predictive analytics based on what's happening in your platform, and this is both hardware and software metrics as well as business level metrics. If you see a sudden change in the rate of transactions in your system, it's likely something's gone wrong. If you see a sudden change in the ratio of successful API calls to failed API calls, something is going on and you need to intervene. If you can catch that early, very few users are significantly affected. So the other thing I'll say, and this is a real driver of cost in the modern enterprise, in you see a lot of the startups where they are all of the developers are what I'd call full stack developers. They are the network administrator. They are the Linux administrator. They're deploying the applications of the database administrator. They're deploying the virtual machines and wiring all this together. And then they're actually coding their application features on top of that. Those people are hard to come by. They're expensive. And they're usually doing this manually. What you need to have is you need to have a team that's really building the templates for these on top of your pass. So again, the infrastructure for your applications are consistently deployed everywhere. And then your developers can focus simply on the business logic that they're working on and their IDE takes care of integrating that with your environment and testing it. I had an early example of this with a financial service provider where it took an experienced developer roughly two weeks to build a test environment, to test, to replicate a problem that they would experience in production. Not a new developer, an experienced developer who is very familiar with their platform. And this environment would be approximately correct. It would never be accurate. We built an infrastructure templating system for them and where it was a click of a button saying I needed the version that's running in production on this day deployed in this environment.  Something that had never happened before. So this makes a huge difference for your business. And going back, once you have that, it enables you to run in the multiple clouds. So we've cut a couple of case studies. Two of these are courtesy of Platform 9, one of the managed OpenStack vendors. They work with a Swiss educational institution that really wanted to start doing more DevOps so they could deliver more educational features to their users faster. They decided they didn't want to be in the business of learning and managing OpenStack. So they shifted to a managed service provider so that OpenStack worked for them and they didn't have to worry about it so they could focus on just delivering the applications. Very good. And this gave them predictable performance, predictable costs. They didn't have to worry about sudden unexpected bills late in their fiscal year as an educational institution. They run pretty tight. And it was a good choice. And we all see the turmoil in the healthcare industry in this country. But a lot of that is, they have to find ways to save cost. And so they're all working on innovative applications for claim processing, health management, everything else. And they're adopting a DevOps process so they can deliver features faster. And a managed private cloud gave them the ability to do this without again being experts in the cloud and being able to consume multiple clouds safely. This one here is interesting for me because I've worked for this company as an employee and as a consultant kind of multiple times and I've built multiple cloud projects for them over the years. I can remember in the pre-OpenStack days thinking vCloud director was gonna save my life. And then I spent a quarter trying to get access to a vCloud director environment so I could try my automation and it didn't happen. So we shifted to this weird company called Rackspace at the time and built an automated application management platform on that. And we used to take their data centers down because at that point in time, their cloud data structure was built for people making one or two changes a day and our automation was making 100 changes a minute. And they got upset with us and said, hey, try this OpenStack thing. And that actually became one of the first largest consumers of OpenStack back in the bare timeframe. But in their, there are probably 36,000 node servers of OpenStack today and they're the last version that became that. Their core goal was to be able to take code that was ready to run and get into production in 15 minutes. Prior to that, without an active God, it was about 45 days because of the capacity planning and all of the manual steps involved and the hundreds of tickets to provision server space, network space, firewall rules, et cetera across their infrastructure. And they exceeded that a long time ago. The other one was because of the, this is another piece about automation that I probably haven't mentioned before. Many of you are dealing with environments where you have some kind of seasonal peaks.  Or you have automation that lets you spill out capacity and you can run your infrastructure at a much higher capacity. They went from 5% to 60% utilization on their servers and their goal is now to get up to 85. When you're dealing with tens of thousands of servers, that's a lot of infrastructure. Completely aside from that, I'm with Juniper. We have a smart analytics product called AppFormix that we're starting to use with orchestrators and what we're trying to do is by using the predictive analytics to reduce the amount of capacity we need to pre-allocate for applications because of the ability to react ahead of a user-visible failure and regain the capacity needed to serve the users so that instead of having to provision 50% over, we can provision 20% over. Again, how do we drive cost out of the infrastructure? So let's talk about ways to consume OpenStack back in our hybrid model. We talked about do it yourself. Unless you're a hyperscale player, this is probably not the right choice. You're really gonna need a minimum four-person team of OpenStack experts who are continually gonna be recruited away from you. So unless you can afford to drop a million bucks a year on these people, don't do it. And unless you're distro, if you're choosing a distro vendor, you don't need to be as intimate with OpenStack, but unless the distro vendor's gonna operate it for you, eventually your team is gonna be up to their elbows in the OpenStack code while they're operating it and you're gonna be in the same place. So distro vendors that do build, operate, and transfer. If you're a mid-sized player, this is probably a good one for you. They're gonna come in, build an OpenStack cluster for you and they're gonna operate it and they're gonna train your people and they're likely gonna stick around for a while and take care of the heavy lifting for you. This lets you consume OpenStack very much like a public cloud, but lets you take over operations if you want to. But you can get up and running fast without having to wait for your people to come up to speed. And if your ITO organizations have been dealing with different environments, this is really necessary. And of course, we have OpenStack as a service which is the watchword of this summit. You have the best of the public cloud world in your data center. Most of, many of the vendors can give you people with a specific nationality if you have regional requirements to do the operation. Some of them will put people on site. I'm not gonna mention any vendors for this, but this is a really good choice if your requirements are small or you need to get started fast. This is the, one of the joys of being in the first world is we have choice, but choice is hard. You can get, you can have your OpenStack entirely in your data center. You can have your OpenStack in a colo. You can have it on your service provider's hardware managed by your vendor. So this is an interesting model for people who have the big burst capacity. If you have your long run average capacity running your data center at the best price, but you have the ability to burst into your service provider's data center through their metal as a service where the environment is identical to yours, it lets you reduce the amount of capacity you need to carry internally while letting you service your peak and unexpected demand. We all like unexpected demand. Our cloud journey, where I've been to the cloud journey probably seven or eight years and it's still evolving. It really, it's about finding ways to really manage your risk while moving faster. I spend a lot of time in the financial sector. I think about a lot of things as risk management. Most of our current practices are about how do we manage the risk of failure? And we build Byzantine complex processes that take an order amount of time and cost a lot of money as a way of reducing the risk of catastrophic failure. And what we see is that the kind of lean model of continuous delivery and DevOps provides another way to manage risk that lets us see the results of what we're doing much quicker and reduce the overall cost of failure. I can remember working for a credit card provider about 18 years ago or so and we would come together yearly and plan out the IT projects that we're gonna start in three years. So it would be, you had an idea, a critical customer need five years before the first customer experience of that if you're lucky. How does that work for people today? Doesn't. We see the hyperscale players where they have a feature and idea and it may be the same day that code is showing up and customers are experiencing it. This is what we're trying to get to and how do we manage our risk and deliver that across multiple environments? Serverless is changing the game. It's gonna be a while for people to absorb it and you need to be constantly looking at what's going on in your environment, figuring out where the friction points are in getting features that matter to your customers and figuring out what features that matter. If you have deep attachments to the way things are, life is gonna steamroll you. You have to figure out what's actually happening and adapt quickly. I'm gonna wind this up. Probably the most interesting realization I've had in last year, I was talking to a friend about SREs. To me, having an SRE organization, a site reliability or engineering organization which is a sole job is to ensure that your customers have a good experience no matter what and drive change backwards to keep that moving forward is that the average lifespan of an SRE at a job is about nine months. They come in, they say all of these things are broken and then everybody says, yeah, so what? And they give up and they go. Don't do that. Listen to them. They are your saviors. Thank you. Questions? Come up to the mic. Hi, Jason. Scott Fulton from the new stack. Hi, Scott. You talked at the beginning about the benefit of Kubernetes as a platform for consumption and how pass is providing a kind of consumption layer. Earlier here at the show, one of your juniper colleagues, Chandan was talking about creating a kind of a direct API that would in fact bypass the pass layer or bypass the orchestrator so that a developer, a developer of software could communicate very much more directly with the underlying infrastructure and specify exactly what she wants from that infrastructure for particular applications. It's a very different way of thinking. So I'm wondering whether juniper or you has worked out which use case works best with which class of customers. Who needs that pass layer and who needs by contrast that direct contact? I think what we'll see actually is the pass layer evolving so that you can get either the direct contact you need by having full control for those people that need it or providing tied guy rails for people who don't have the time or expertise or the need for it. The average developer probably doesn't but if you're doing some kind of deep learning application that requires GPU access, you want a lot more control over how things are done than if you're doing yet another ad network. I shouldn't say that derogatively, I'm a ad network's fun to work. Anyone here from an ad network, anyway? Okay. But I do think that the goal of pass is to enable people who don't want to to deliver things that can be successfully operated and run from a security and efficiency standpoint. Any more questions? Well, thank you very much.


The governor of Niger State, Umar Bago, has assured that the state will organize the first-ever subnational green economic summit in the country, which will take place from 24th, 25th of October, 2023, at Mina, Niger State. The governor made the announcement at a world-press conference in Abuja, the nation's capital on Wednesday. It says the strategic location of Niger State in the north-central geopolitical zone of Nigeria, with 76,363 km of arable land and the diverse natural resources, including the abundant carbon assets, freshwater bodies, rich mineral deposits, including lithium, gold, tin, talc, kaolin, granite, marble, copper, and lead, among others, and scenic landscapes makes the most suitable for a green economy. The military, the federal government, the state government, are in collaboration. And as you know very well, this is a lot of things we should discuss in the public, but I can assure you, Nigeria is safe, it's safe for investment. And again, with the ban on mining, the incessant approvals from the federal minister of mines of many resources, giving people a cadastral license to come out of mine, without the knowledge of the local people that has become a menace, you know, degradation of our land, and also a lot of illegal activities, you know. And you need to understand, I say, it's a symbiotic relationship between the headsmen and minors. These mines are very heavy, so they use this cattle to trans-ship these mines from where they are mining them to the neighboring countries. While assuring that the state will benefit tremendously from the summit, Governor Baguio assured of adequate security during and after the summit. Subsequently, the summit will also emphasize the role of local communities and their indigenous knowledge systems in sustainable development while empowering them with the necessary knowledge for resources to engage in eco-friendly practices and green initiatives to achieve the UN SDGs. The target is to unlock the state's green economy potential to achieve prosperity for all its residents. By adopting this theme, the Niger State Green Economy Summit aims to inspire collaboration, knowledge sharing, and concentrate actions that will lead to a greener, more sustainable and prosperous future for the state and its people. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Hey, I'm here with Carmen Cliccoli and we talked a lot before, right? I know you from the Windows Server Software Defined Data Center program. It was a program, it was the Windows Server Software Defined Solutions program. Okay, and then I knew you were working on Azure Stack HCI, which both programs and both solutions were like making me super excited. So that's why I have you here as well. The Azure Stack HCI program really was an evolution from WSSD. WSSD, we launched it when we launched Windows Server 2016 and the idea was just we needed a way to get customers solutions that would work with our Software Defined Data Center software technologies that were just built into Windows Server and customers who try to build their own on hardware that was lying around had really bad experiences because it turns out building high-performance, resilient storage and networking requires specialized equipment. So rather than just put the software out there and hope customers get it right, we decided to work with the hardware ecosystem, have them build solutions based on best practices and then put them together and market them as a complete and end solution. WSSD was really kind of the start of that process and when time came to release Windows Server 2019, we decided to go all in on the investment and we relaunched it as the Azure Stack HCI program and we built a whole roadmap and plan out to make Azure Stack HCI part of our entire edge computing plan going forward. So I'm sure a lot of people have heard of Azure Stack, which is now Azure Stack Hub. We have a whole category in there and Azure Stack HCI is one of those pieces and that's going to be the direction we take this hardware solution program going forward. So I remember, I absolutely remember, I remember the time where we were building solutions based on Windows Server and Hyper-V and again the customers sometimes they just ordered some random hardware, right? So I went through that pain with drivers, validation, like doing the right setups and everything and that's exactly where I think the Windows Server software defined data center program comes in and then now Azure Stack HCI, right? That's right. And the idea, again, just remove the amount of work the customer has to do before they can even get started, right? Take care of that. And then going forward, we started it as a solution program working with OEMs to define those SKUs, but it's really a product and it's going to become more of a product as we go forward. So right now the program defines the hardware and then Windows Server is installed on top of it and that's an Azure Stack HCI solution. Okay, okay. That's really good to hear that there is a lot of investment because we see a high demand from when I talk to customers out there. I really see a high demand of like people are interested in hyperconverged solutions and they are looking for like, what are the Microsoft offerings there? And a lot of what I heard from them is like, okay, you have this Azure Stack thing, right? And they still believe kind of like, okay, there's only one thing in Azure Stack because we had Azure Stack as a name. Now it's Azure Stack Hub. So where would you say are a little bit the differences of Azure Stack Hub and Azure Stack HCI in terms of like, where would you use what? And like also, I'm also interested in like, what are the options? I know that a lot of customers know that, again, Azure Stack Hub gets delivered as an appliance, right? But which limits it down to certain configurations. Yeah. Is that the same with Azure Stack HCI or how does that work? So, well, let's start at the beginning. Like how did it differentiate it? And it's easily the most common question, right? Because when you change names and have similar names, people are like, wait a minute. There was already a thing that was called that. Why is that different? Why do I want that? So easily the most common question. And in fact, it's basically what I spent all of Ignite doing was answering that question because it was the first time we kind of ruled out the whole new family and the name for the products. And that was just what people wanted to understand is more clarity than just the announcement. Yeah. So what we say is Azure Stack Hub, which is just called Azure Stack previously is really about having cloud consistency in your data center. Meaning if you are already down the CICD pathway and you are developing cloud native applications, but you have a need to run those cloud native applications in your own data center, you need Azure Stack Hub. Because Azure Stack Hub provides the Azure Resource Manager and the APIs that you need for those cloud native apps to run there. So it handles that very specific business need. Azure Stack HCI is really about just providing a hybrid model for what I would call more traditional virtualized workloads. So if you have a virtualization farm that is just running VMs of all shape sizes and descriptions and they don't necessarily make an easy migration or fit into an IaaS world for your business, Azure Stack HCI gives you the ability to have a hybrid platform that takes advantage of cloud resources without being a cloud resource in and of itself. Okay. Right. So it helps people who are not far enough down the cloud path to really want the full cloud experience running in a rack in their data center. Which we see a lot. I mean, that's not something which is uncommon, right? It's like most companies have a history and they're not fully migrated and everything is cloud native and everything. So I see that a lot. But I also found it's like there's many, many different solutions out there, right? I think how many do we have right now in the Azure Stack HCI catalog? Last time I looked, I think we were up over 190. Okay. Different solutions from 20-something different OEMs around the world. And we obviously have all of the big players that you know, but we also have a lot of regional specific OEMs who have their loyal customer base because they provide a lot of services, a lot of value to their own customers. So we're happy to have that variety in the catalog and we can go from tiny little configurations that can sit on a desk and you wouldn't even know that there are two Xeons in those servers and it's a spailover cluster with 12 terabytes of capacity in it to gigantic systems that have multiple petabytes. So just the variety is part of the point because unlike a lot of more restricted catalogs where you just have to take what's available off the shelf, you can spec almost anything you want out of it. And listen, a lot of traditional IT people love that, right? I love that. That's the world I came out of. I've been doing this for a long time. I like having some level of involvement in the hardware and being able to spec it to my needs and seeing what the options are. I mean, also the requirements are always different, right? I mean, for a branch office, you can just go out and sometimes you just need something very small or even if you go outside of offices, right? You probably just want to have a two-node mini-systems which probably still have enough performance but you want to have a very small system. But then if you go with your data center, you either want to probably run high-performance systems or maybe even high-capacity, right? And so that's what I love about Azure Stack HCI is really it gives you that flexibility to whatever the customer need is, we can basically go out and address it. Yep. It was one of the high points of a night for us was during our director's session, Bernardo called us, he had Cosmos Darwin come out on stage at one of our PMs, one of the PMs responsible for Storage Spaces Direct and HCI. And he talked about that flexibility and he walked out on stage with a laptop bag and everyone's like, does he know that he's carrying his laptop on stage in front of 5,000 people? And while he was talking, he was like, you know, it allows for exciting new form factors and he opened up a laptop bag and he pulled out a full Xeon server from Lenovo, it's called the SE350, that they just announced for the catalog. And it's maybe, if you're familiar with like, you know, 1U pizza box servers as we call them, it's one quarter of one of those, right? So you can take four of them and put them on a sled and put them in a place where one server would have existed previously.  And it is a full blown server. It can host a GPU, right? It's got 100 gig networking in it. It can do 5G, like it is a real server. And, you know, it's just not something your traditional appliance model would allow for or is, you know, makes sense even. So, yeah, the variety is very much the point of making this a broad partner ecosystem from my perspective. No, again, I'm like, I am super excited about what we have. I mean, about the whole portfolio we offer there. But now you told me you're going to work on something new, which is also still to add a stack HCI, right? But you kind of like have a new position or a new goal. Yeah, yeah, I'm not even really changing teams exactly. I'm just changing what it is I'm focusing on. So rather than running the program and working with the partners, one of the things that we've, that is very important to our engineering efforts is that we're making customer driven decisions. And so we're trying to start up a customer engineering, co-engineering program. Okay. Where we can build relationships with customers who are doing the next thing in their own environment and are interested in working with us on the development of that next thing. Okay. Right? So it's a very intimate program with direct engagement with our engineering. Right? So it's not something where we're just going to send you email updates and... Like a survey and that's it. Yeah, exactly. How happy are you? Very sad. It's none of that. It's regular syncs with our engineering teams, with our leadership. We want to understand your environment. We want your feedback about what's going on. And we're trying to get that customer muscle built up in our engineering teams, where every time they go into make a decision or make an investment of dev time and PM time into work, they're like, we're doing this because customer X said that would make a tremendous impact on their business. Okay. So we've had lots of different customer engagement mechanisms over the year. Microsoft's been around for a long time. Windows has been around for a long time. We're trying this different way to get that relationship up rather than have it be highly programmatic like the previous top programs. We're like Windows insiders, which is tremendously valuable, but it's meant to reach millions of consumers where millions of consumers are not the audience for HCI or Kubernetes, right? So there's two areas I'm most interested in right now is HCI and Kubernetes on-prem and hybrid scenarios. So if you're watching this, I'm sure that there's probably going to be my contact information shared on the screen somewhere when this gets published. Feel free to reach out to me either on Twitter or email if you can find my email or LinkedIn. If you think that sounds like you, please reach out. I'm happy to have discussions and if you're working on the next gen thing, we want to hear from you. Absolutely. So we will put out all the links and how you can reach Carmen in the description to make sure that people can actually go and engage with you. Perfect. So I have one question. For a customer, obviously, if I join, I will have these regular calls. Do I get early access to the stuff your team is doing or what is kind of like the... The goal really is we want to co-engineer with customers. So we will... This is an NDA program, right? It's not broad. There's a reason I'm not even giving you details about what we're working on. It would be... You have regular briefings with us. We share early access to technology with you. We ask that you run it and give us feedback on it. The same thing with the business direction we're taking things in, our technology focus, whether or not it meets your needs. That's the kind of focus of this type of program. And then at the end of the day, we're hoping that we make you happy enough that one, you want to run the final product. And two, that you're willing to stand on stage with us at some point and say, we worked with Microsoft on this technology. We're really thrilled. Here's what we're doing with it. We want it to be successful for both parties involved. Okay. Perfect. So I want to thank you very much for this. It was super exciting to talk about it with this because I'm really looking forward to see what is coming up. And for all the people who are out there, we're watching this video. And if you want to have early access to the Azure Stack HCI and you want to shape the future of how we do hyperconverged and all of that, reach out to Carmen. Again, you will find the links in the description underneath this video. And with that, I want to say thank you and see you in the next one.


Three quarters of American adults drink coffee, about half of which on a daily basis. That comes out to a million tons of coffee every year. Might there be grounds for concern? Population studies have found that coffee drinkers tend to have lower risk of Parkinson's, less prostate cancer, especially the women, less liver cancer, less diabetes, liver cirrhosis, depression among women, and a reduction in mortality overall, such that coffee drinkers tend to live longer than non-coffee drinkers, with mortality bottoming out at about four cups a day. But these are all just associations. You don't know if it's cause and effect until you put it to the test. For example, coffee really does seem to protect the liver. Take people with chronic hepatitis and have them drink coffee or not for a month, then switch them back. The coffee really did seem to help. Similarly, a randomized Parkinson's patient is to get two cups of coffee worth of caffeine and get a significant improvement in movement symptoms within three weeks. Runners randomized to drink coffee shaved about six seconds off their mile. Weight lifters randomized to coffee can squat more weight, about 600 pounds more worth of reps, and not just athletic performance. A cup of coffee's worth of caffeine can significantly improve IELT, which stands for Intravaginal Ejoculation Latency Time from two minutes all the way up to five. Unfortunately, those effectively randomized at birth to genetically just have higher predilection to drink coffee do not appear to be protected from diabetes or depression or Alzheimer's or obesity or metabolic syndrome. So it seems the protective associations may just be due to confounding factors, like maybe those who drink coffee just happen to exercise more or something, and the same with prostate cancer. No apparent cause-and-effect relationship and even the mortality benefit seemed to disappear. Even if a study did show coffee drinking could extend lifespan by reducing inflammation or improving lung function or insulin sensitivity, that would mean on average. There is inter-individual variability after consumption of major plant food compounds, meaning people may respond differently. For example, how crazy is this? In some rare individuals, heavy use of caffeine apparently provokes sleepiness. That's an extreme example. Most of the time it's just that some individuals may benefit more than others from the health effects of different foods. For example, because of differences in gut bacteria, only a minority of Westerners may derive extra benefit from soy, as I've described before. The most common difference in caffeine effects is that while most people metabolize caffeine rapidly, certain gene variants in liver detox enzymes make some people slow metabolizers. Might that make a difference? Well, habitual coffee consumption of at least three cups a day has been associated with uncontrolled blood pressure among older individuals diagnosed with hypertension, suggesting that moderating coffee intake may be a good idea for some people. But even if it was cause and effect, I mean that would be on average. What would happen if you split people up by how fast they metabolize caffeine? Compared to coffee abstainers, those who have impaired caffeine metabolism genes have an elevated risk of becoming hypertensive at one to three cups a day, and especially at four or more. Okay, but check this out. For the rapid metabolizers, not only was there no excess risk at one to three cups, heavy coffee drinkers were protected, meaning apparently the more coffee they drank, the lower their risk. How do we explain that? Well, coffee is a complex blend of a vast number of different compounds. There are protective polyphenol antioxidants that are beneficial. Coffee beans are, after all, beans, well, actually seeds, but seeds are really healthy, too. On the other hand, there is the caffeine, which can spike adrenaline levels in the blood, but only if you're a slow metabolizer. Rapid metabolizers can clear caffeine so fast that there's no increase in adrenaline, even at four or more cups a day.  Thus, there seems to be a Jekyll and Hyde aspect to coffee whose overall action on the cardiovascular system appears to be regulated by that gene for the enzyme that metabolizes caffeine. The important question, though, is does it give women larger breasts? What? Young women drink a lot of coffee and our rapid caffeine metabolizers have about a half a baseball-sized larger breast volume, which may be a bad thing, as breast volume is associated with breast cancer risk. But now the important question is, what about heart attack risk? In slow metabolizers, daily coffee consumption appeared to double the odds of a heart attack or even quadruple the odds at four cups a day, whereas in the rapid caffeine metabolizers, daily coffee consumption was protective, cutting the odds of a heart attack by more than half, or at least until you get up to four more cups a day. The protective effects observed among rapid metabolizers suggest that the efficient elimination of caffeine might have unmasked the protective effects of other phytochemicals in coffee. We think it may be the adrenaline again, since if you're a slow metabolizer of adrenaline, high coffee consumption may put you at risk as well. So, is coffee friend or foe? These studies suggest the possibility that slow caffeine metabolizers who consume caffeinated coffee may have an increased risk of cardiovascular disease, whereas fast caffeine metabolizers may be protected from this risk by the antioxidants and other beneficial compounds present.


This is stock number 9615A. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used light duty truck headquarters. Today we are checking out this super clean 2016 Chevy Colorado crew cab short box. This truck has the 2.8 liter four cylinder Duramax diesel. From this HD video you will be able to tell that this truck is an exceptionally nice condition all the way around inside and out. You can see it has factory fog lights. Headlight lenses are nice and clear. It is a gray metallic color. Like to point out we shoot all of our videos in 1080p so if you have HD capabilities on your computer tablet or smartphone device turn them on now because it is like you're right here looking at the truck with me. I do want to point out the camouflage side graphics there. Those are actually just stickers so if you did not like them they definitely couldn't come off. We leave them on just because some people like them and prefer to keep them on but if you don't like them they definitely can come off. This truck comes with 20 inch mayhem painted and polished aluminum rims. Very nice rims and hand-cooked Dynapro 275 55R 20 tires. These tires have probably about 75% of the tread left and you can see the frame and the underbody on this truck is an exceptionally nice clean condition. It does have a lift kit on it. It is a rough country lift kit. Looks like it's been really nicely done and driving this thing up and down the road. Really nice ride. It does have those camo stickers on the hood as well. Like I said if you didn't like them you can always remove them. Passenger side fender no dents or dings on that and we shoot all of our videos in 1080p. Not sure if I said that or not but if you have HD capabilities on your computer tablet or smartphone device turn them on out because it's like you're right here looking at the truck with me. Passenger side rim no scuffs or scrapes on that and as you go down this side of the truck you can see just how clean that body is how reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the truck you can still see the truck hear the truck and have confidence in the vehicle that you're looking at before you even get here. Cab looks really good on this one as well and on this side I didn't see any dents or dings. Very nice condition. Down this side all the lower rockers look really good. The back rims are in excellent shape as well. I didn't see any scuffs or scrapes on them and the back tires have just as much tread as the front tires. You can see the frame and under body on this truck is an exceptionally clean condition as well and it's like that all the way underneath. Looks like it has all the remaining factory exhaust as well. Box side is very clean as we come around to the back you can see it has the in bumper steps the full towing package which includes a receiver hitch four pin and seven pin wiring so it does have this metal metal mountain scape on the back here that I believe is glued to the tailgate now you could remove the stickers below but I think that that those mountains are there to stay. Has a trucks port soft tonneau cover has the shock assist down tailgate and a spraying bed liner definitely protected well rear bumpers very clean and as you go down this side of the truck just as clean as that passenger side no denser dings on the box and for full disclosure this back rim is an excellent shape as well very clean all the way around on this truck very well taken care of inside is no different this truck has the LT1 package which gives you the black cloth interior no rips or tears in here seats are in really nice condition has a power driver seat factory floor mats throughout and once again it does have that camel wrap in here so these are just stick on real-tree stickers those do come off if you didn't like them once again power windows power locks and power mirrors we have the auto headlamps turn dial four-wheel drive including the auto feature has a factory brake controller as well and as we hop inside here you can see that this truck has 39,044 miles they got pretty excessive with the camel wrapping in here but like I said once again just stickers if you want that off you definitely could remove it how much you get your information center in there you also have your multifunction steering wheel bluetooth audio controls on the left you have adaptive not adaptive cruise but collision warning and your normal cruise controls on the left there comes with the Chevy my link system so AM FM series XM radio capabilities this is also where your backup camera is climate controls stability control factory exhaust break your cargo lamps and this one does have lane departure warning so kind of a neat system right there will alert you if you're going outside the lines passenger seat or a passenger dash and seat is very clean as well no rips or tears on that and it does come with side curtain airbags headliner is in nice condition and it does have on-star capabilities in the mirror we'll take a quick look at the back seats and then check out under the hood back seats are just as clean as the front seats no rips or tears back here does have the latch child safety system for car seats and it does have a sliding rear window with the built-in rear defrost that is a manual sliding rear window you get under these back seats almost takes two hands but you can do it with one if you're talented storage underneath here factory floor mats and carpeting is very clean back here and to let this down you just press that button right there I'd like to personally thank you for checking out the video today hopefully from this video you will have been able to tell just how clean this truck is all the way around inside and out and know that these stickers if you didn't like them you could definitely remove them under the hood we have the 2.8 liter four cylinder Duramax diesel engine maze very clean runs very smooth this truck has been fully safe and inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off and gone through mechanically 100% and is 100% ready to go to see more pictures of this truck or one of our 400 new and used cars trucks SUVs minivans Wranglers half tons recorder tons you name it we got it go to our website www.summitauto.com full pictures and descriptions of every single vehicle on our lot videos of every single used vehicle that we have all at Summit Auto


popular business idea in the education sector, that is, of a play school. Play school mainly caters to children aged between 2 and 4 years. As the name suggests, to very young children and help them develop social skills and learning capabilities. So if you are passionate about teaching young children and hold prior experience in early child education, then this is the perfect opportunity for you to become an edupreneur. You can either start your own play school or take franchisee of a popular play school brand, like kidsy, your kids or bachpaan. Opening a franchisee doesn't require much planning as the parent company will set the guidelines for setting up and running the school, however, it comes with higher costs.  But don't fret, as setting up a play school is not as cumbersome as it may sound. The first step is to identify a location for your preschool. You will need around 1000 square feet area for a school that can accommodate up to 60 children. We suggest that you locate your school in a residential area because parents prefer sending their kids to play schools in near vicinity. Now let us understand the permissions and guidelines for starting a preschool business. You must get a no objection certificate also known as an NOC from the society for running the play school. Early childhood guidelines mandate one teacher or a trained professional for every 20 students. An important thing to note here is that if you want to teach in your own school, you will need to be a degree or a diploma certificate in free school teaching to be able to do so. Now let us move on to understand the investments that you will require to make. You will require an initial investment for setting up the business, while other expenses will be in the form of operational costs. For setting up, furnishing and decorations will require to shell out 60-70,000 rupees. Setting up the play area with toys and other play equipment will be another rupees 1 lakh whereas educational materials and learning tools in classes is another 25-30,000 rupees. As for operational costs, rent of a play school will be between 30-35,000 rupees. Electricity and water bills can amount to about 20,000 per month. The major chunk of your operating costs will be on staffing which will be around rupees 80,000 for 3 teachers and 2 assistants. Of course, if you plan to teach in your own school, you can save on this amount to a great extent. Also, you may not have to hire more than one teacher initially until your student count exceeds 20. Next, you will spend around 12-15,000 rupees every month on marketing until you get enough students on board, which can take easily up to 6-8 months. Like we said earlier, starting a play school yourself works out cheaper compared to taking a franchisee. Franchisee of most popular play school brands ask for a one-time investment of 12-15 lakh for giving out the franchisee, which is much higher than the cost that we have just told you. Your revenue will essentially be the fees charged to students, which will depend on the kind of services that you choose to provide. So for a regular play school that offers learning activities in a play area, monthly fees per student can range between 2000-2200 rupees. If you also want to provide daycare services and mails, you can charge upwards of 3500 per student. Along with the monthly tuition fee, students will also pay a one-time admission fee that can range between rupees 15,000-20,000 per month. So to give you a fair idea of the profits that you can make, once you have 60 regular students attending your school, you can easily book a profit of 30-35% on the total revenue. A world of caution here that like any other business, the first year can be slow in terms of profit generation. Having said that, pre-school business is also one of the few recession-proof businesses ideas as no parent ever compromises on their kids' education. So once your business takes on, no matter what, your business will always flourish. So that's about the pre-school business idea. We hope that you liked it and soon take the plunge to start your own business. Meanwhile, stay tuned and log on to www.entrepreneur.com for more business ideas.


I ain't mic'd up, Emma. I ain't mic'd up, Emma. Everybody keeps trying to say I'm mic'd up. They talk a junk to me and stuff. Told them I ain't mic'd up, man. I've been looking for the camera all day, man. Nobody want to be my friend today. That's crazy. Nah, nobody want to be my friend. They say I'm the feds. I'll say, yeah, that's crazy. In the ATM with my boy, Mike. Hey, what's up, boy? I just seen the report you was ill. I don't know where I'm at. I'm just following the big people. I'm mic'd up. So, watch out. Don't be cussing at me today. Nah, nah, I ain't do nothing. Yeah, I seen that somewhere. I'm mic'd up. You trying to be disrespectful? That's crazy.  Try to get some camera time. That's crazy. What's up? Camera up there. Let them know what you got to say. Damn. He trying to... I'm getting some camera time. That's crazy. I'll mic you up one day right now. Let me do my thing right now. He called me old because he said I was 30. I ain't been 23 in years. I ain't been 23. Damn. I'm on them gloves now. I don't know how much insurance we got up here. I actually got them two pants. So, I shouldn't have a new advantage. No, no, no. You know what I mean? I got my pass in two serves. He takes all the runs.  Yes, sir. Thank you.  You know what I'm going to receive with, baby? Put it up there.  Darby. The best thing you got is your scrum. Yeah. So, if you did, that's going to work every time. Your scrum, bro. That's what we got, bro. Look at that. Push them db's out of it. That's what's going to be on us. Db's. They're going to be like his style. You know what I'm saying? No offense to them, bro. We scrum with them. Crazy. If you find out you might out, they want to be nice to you. He's got to give you drinks and stuff. I'll be real. You want me to do it, bro? Nope. Good boy. Good boy. Toby said, how that boy looking out there? I said, time? I can't wait to run your way. What you on the right side? Every side. Me too, then. I'll be running right at you. I don't ever see it. I'm going to be a movie. I play no country music for me today.