This is stock number 11236. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck and RAM headquarters. Today we are checking out this Super Clean 2016 RAM 2500 Crew Cab Short Box Power Wagon. This vehicle has the 6.4-liter V8 Hemi motor, which pumps out 410 horsepower. This truck has been fully-safetyed and inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off and this truck is 100% ready to go. Flame red is the color. We shoot all of our videos in 1080p 60 frames per second. So if you have HD capabilities on your computer tablet or smartphone device, turn them on right now because it is definitely your best way to check out the quality and condition of the truck before seeing it in person. This one comes with RBP painted and polished aluminum rims. They're in pretty nice shape and it has Nitto Ridge Grappler 33 by 12.5 hour 20 LT tires and these tires look like they have probably about 50 to 60% of the tread left. You get the Bilstein shocks with the Power Wagon package. Frame and underbody is in really nice shape. This truck came out of West Virginia and Kentucky where the two previous places it was owned. Has the projector lamp headlamps, LED running lights, front bumper is painted and you get the front bumper parking sensors. No major dents or dings on that front bumper. Has the chrome trimmed grille. This is a Laramie Power Wagon. So you get the leather seats and everything and you get those projector lamp headlamps. Didn't see any dents or dings on the hood and the passenger side front fenders in excellent shape as well. Passengers side rim, no major scuffs or scrapes. Looks pretty good. And as you go down this side of the truck, take note of how clean the 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 you just cannot make the trip down but you're still interested in purchasing the vehicle. You can see the truck, hear the truck and have confidence in what you are looking at before you even get here so that when you do get here there's absolutely no surprises. This one does have the cargo cam which is right up there and that's why we offer the Summit Auto Fastpass option in the upper right hand part of your screen. A link right to our website where you can apply for financing, get pre-approved, see a payment quote, even appraise a trade all from the comfort of your own home. So when you get here all you got to do is drive the truck, love it and you'll be all set to go. Back tires have just about as much tread as the front tires, no scuffs or scrapes on this back rim and the frame and underbody on this truck is in really nice shape. You can see it does have the rear coil spring suspension which gives you a much smoother ride when you're unloading. The frame and underbody looks really good, lower rockers look good, has all the remaining factory exhaust and you get those step bars there as well and they are in really nice shape too. Laramie package also gives you the fender flares, bed rail covers are standard on the rams. Rear bumpers in great shape, no major dents or dings on that, it does have backup parking sensors and the tailgate is in really nice condition as well. This is a locking tailgate that has a backup camera, you get the spray and bed liner, LED bed lighting and the bed is in really nice condition, very light duty usage. As we come around to the driver's side, just as clean as I passed in her side, no dents or dings on the box here, looks really good. For full disclosure, this back rim just as nice as the rest and on the rest of the side looks really really good. You do get the heated mirrors with the built in directional signals, enter and go system, just have to have the key fob in your pocket, it will automatically open up. You get power mirrors on here as well, they power fold in, power fold out, I always like showing both sides that they're working. Inside the Laramie package gives you the black leather interior, Laramie embossed backrests, no rips, no tears, side current air bags, both of these seats are heated and cooled. You get memory driver's seat, lumbar, factory, all weather floor mats, auto headlamps, power pedals, radio controls in the back of the steering wheel and then the power windows, power locks, power mirrors, wood drain door trim, full hop inside, turn the ignition on here so you can see everything. You get the power wagon animation there, you can see that this truck has 38,924 miles, you get the temp, compass, trailer brake gain, time and you can adjust those to read whatever you'd like so it's all adjustable in there and that's seven inch LCD display and then you also get the digital speedometer. It comes with the heated leather wrap steering wheel, cruise controls on the right, bluetooth and information center controls on the back, audio controls on the back of the steering wheel, six speed automatic transmission with the optional tap shift, this one comes with the 8.43c radio and it does have the factory navigation system on it, AM FM and Sirius XM radio capabilities. You can do your climate controls here as well. If you turn that on you can also do your heated seats and heated steering wheel buttons and then you can check out your backup cam and you can also check out your cargo cam so you can see what's going on inside the bed of the truck in case anything's loose back there. So you got all that stuff and if you don't like using the climate control on the radio you can use the climate controls down here, more tactile buttons and knobs, you also get a volume in tune knob, turn dial, axle locks, sway bar disconnects and then you get the 4x4 shifter on the floor. It has the factory brake controller, stability control, tow haul, downhouse assist control, front and rear parking sensors, more tactile heated seats and cooled seat buttons as well as the heated steering wheel button and then you do get a 115 volt, 150 watt plug-in keyless entry with the enter and go system and remote start. This one does have the Alpine premium sound system, you get the 911 and assist in the rear view mirror, you also have your home link buttons for your garage door security systems and lane systems, power sign rear window and your map lights. Headliner is really clean and this one does have a DVD player in the back which we'll check out in just a second. Passenger side seat is in excellent shape, no rips or tears on that. I don't think this truck's ever been smoked in, smells very clean. The other cool thing about this truck is that it has the 40-20-40 split bench seating and you get a little storage compartment underneath there. We'll take a quick look at the back seats and then we'll start it up and check out under the hood.  You can see it's working there.  You do get the load floor underneath here which is nice. If you got pets they put both sides down, if you got muddy boots or tools put them on there you're not going to wreck your nice leather seats. Then you do get storage underneath there. In-floor storage bins on each side underneath the all-weather floor mat. You have removable containers for easy cleaning. You can put ice and drinks back there, it's like you have too many coolers wherever you go. That all-weather floor mat goes all the way across. You get the wood grain trim on the back doors here as well and the child safety locks. We'll start it up and take a quick look under the hood. I'd personally like to thank you for checking out the video today and hopefully from this HD video. You'll have been able to tell just how clean this truck is all the way around inside and I don't want to forget that it does come with the factory winch on the power wagon. Under the hood we have the 6.4 liter V8 Hemi motor, 410 horsepower, engine bay is very clean, runs very smooth. This truck has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. The truck has been gone through mechanically 100% and is 100% ready to go. I'd highly recommend it for me. Quality and condition standpoint and to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, wranglers, halftones, three-quarter tons, one tons. You name it we got it and you guessed it. Go to that website right there at www.summitauto.com full pictures and descriptions of every single vehicle from two locations all at summitauto.com and if you'd like to check out more HD videos you can go to youtube.com slash summit auto. Remember to like, subscribe, and share on this video and all the videos that you see there. In fact in a second you will see a link to subscribe to our YouTube channel on your left. Link to more Ram 2500 truck videos like this one on your right if you have not been to our website. On the bottom a link to this vehicle on our website. Click those, check us out and we really look forward to helping you with this super clean 2016 Ram 2500 crew cab short box power wagon in flame red clear coat. Thanks again for checking out the video.


My name is John Casey, this is Sirad Mohan, we're from Seaplane Networks. Today, we're going to talk about building multi-site distributed open-stack clouds. So hyper-distributed clouds or multi-site clouds, discussions have started in previous open-stack summits in Austin and Tokyo. We're going to discuss this from a customer perspective, we're going to kind of extend what's been talked about in the past. We're going to talk about what's driving this, applications and also the marketplace that's driving this. We're going to talk about a real-life example of a production customer building, deploying and already in production of a hyper-distributed cloud and then we're going to talk about lessons learned and how to enhance the community, open-stack community and bring what we've learned back into the community. So AWS, great example of a cloud today, hyper-scale cloud, one of the most successful clouds out there. They're able to do things that frankly enterprises can't do, a lot of movement into the clouds. And in hyper-scale, the problem is how do you build out large segments of compute storage resources and sell them to enterprises and customers. The problem that they don't solve is latency, but it's ever used AWS knows that if you have an instance in Asia, an instance in the US, latency is a killer. So this basically shows the latency, pretty well known across AWS, and that's what we're really looking at is solving that latency problem with hyper-distributed clouds. So the service providers kind of caught on to this a few years ago and said, look, we have networks everywhere in the world and we are partners with AWS and we are places that AWS is not. So we can solve the hyper-distributed problem of clouds, we can provide low latency clouds and we can partner with AWS to extend their reach and extend essentially clouds. And so this is really transforming service providers in fundamental ways and we'll go through that in this presentation. So the drivers for this, if you think about hyper-scale clouds, what's being done, the applications that are being put up there are heavily storage oriented, right? So storage, backup, big data applications, and when you have lots of compute power, you can do these things. But as you kind of move along this path of distributed applications, think about SAP, where you have an ERP system that's managing a service chain or a work chain in Asia, different parts of Asia in the U.S. and Europe, you want to locate that application as close to the processing or the business as possible and bring that all together. And so service providers are looking at that problem. And now in the Edge Cloud, if you think about low latency, what you can do with maybe mobile edge computing, streaming media, you know, IoT, games, self-driving cars, you really need to think about low latency, very low latency, for those applications, right, to support those applications. So the service provider infrastructure, they're looking at placing compute resources close to the Edge as possible. That means that they can support applications everywhere where they have PE routers or Edge routers, and that gives them the ability to provide 10 millisecond latency or less. And if you actually think about putting stuff out in the cell towers, you can think about even one millisecond latency, right. So the applications that you can support are not just big data now, they're really real time applications. So this is really sort of transforming the thinking about cloud in pretty fundamental ways. Just to give you a for reference example, it takes about seven milliseconds for pain to reach the tip of your finger to the base of your spine, right. So if you imagine that compute resources at every cell tower around the world, you can essentially respond to with compute resources under one millisecond. So imagine what the world would be like if you actually had this sort of reactive nature across the globe. And so the five key trends that are driving this are really mobile Edge computing, network function virtualization, SDN, SDN, IoT and 5G. And the rollout of 5G really sort of promises to bring mobility everywhere at low latency, combining that with Edge Cloud provides those compute resources at the edge. So why is distributed OpenStack or distributed cloud, multi-site cloud, hyper-distributed cloud different than what we typically think of as standard hyperscale? Well, you're dealing with a real different set of problems. It's not about tweaking one pod of OpenStack or making one pod of OpenStack really kind of work and getting the most out of it. It's really about getting them all to work simultaneously together as one global cloud. So what you might think of in tweaking the OpenStack, you really can't really think about that. It's cookie cutter solutions. Also the problems exist, most of the problems really exist outside of OpenStack and what I kind of describe as people places and things. The people, so when we went from siloed IT where you had network storage compute and we now converge that into what we call cloud, you now have that in spades. So beyond combining those skill sets within one OpenStack instance, now you're doing that across geographic regions. So somebody dealing with a network in New York wouldn't be the same person dealing with a network or storage in, let's say, Japan. And then places latency, latency is a killer, complexity is a killer. So being able to, knowing that you have huge latency from one OpenStack instance to another is a huge problem that you need to overcome. And then the things, because the infrastructure, you're not building one OpenStack site to solve one specific problem, you want to amortize OpenStack because you're building it globally, you want to amortize OpenStack across many, many different problems, many different applications, it really sort of changes what you integrate with from a northbound perspective, how you manage it, and the applications that support that, right? Because that amortization is big and long and the businesses, well certainly service providers anyway, have a pretty complex business model, right? They have retail customers, they have wholesale customers, they sell and different chains of things, they have peering points. So the business model for service providers deploying globally distributed cloud is pretty complex and we need to fit into that with deploying OpenStack. The application topologies driving this hyper-distributed cloud are also pretty complex. I mean think about SAP, think about deploying parts of SAP across the globe and connecting them together, so that's a pretty interesting deployment. SD-WAN, you know, you may have an NFV in one service provider in AT&T, for example, in another in Verizon or in Deutsche Telekom. And then lastly, it's the N squared problem. The N squared problem, what that really means is this is a complex system you have a number of OpenStack clouds, geographically distributed, think about thousands. Now you have a number of systems you're integrating with. The problem is that instead of one management system or one BSS system or one portal, now all of those portals have to connect to all of the clouds, right? So this is a split brain problem. You have the complexity of the human complexity, right? So you have different people, different organizations, managing, monitoring your cloud, and you have different applications being applied in that cloud, maybe across different management systems. So you really have to solve for this complexity. You have to reduce complexity, and so we'll talk about how we do that. So this is a use case. It's a customer service provider that's been in production for over a year. They've gone through a number of initial releases, upgrades, multiple releases now, and they're going into their second year, and they're starting to deploy this basically globally across their network. So I'll talk about what their business is, is that it's essentially an MPLS provider. Their customers are geographically located across the world, and their traditional business is connectivity services, right? So they may have Coke or Pepsi in all of their bottling plants, and they're connecting together with MPLS services. And so they looked at this problem and said, we can place compute resources everywhere we have a point of presence, and we can provide compute resources to those customers as part of their MPLS services. So they can put data, they can put processing close to their, let's say, bottling plant, for example. So the challenges presented at us to deploy this over a year and a half ago was that they said, we have this global network. We want to deploy OpenStack from tens of sites to thousands of sites. Anywhere we have access to customers, we want to be able to deploy OpenStack and provide that to our customer. Because our customers are geographically distributed, we want them to be able to order up services through a portal and deploy from a customer perspective anywhere in the world. And we want them to be basically seamless, right? So aside from setting up OpenStack, the day zero and day one work, everything has to be automated. Total flow through visioning completely hands off, right? So customer says, I want compute resources. They click a couple of buttons on the screen. And seconds later or minutes later, compute resources show up connected to their MPLS VPN and it looks like just another site on their customer network. But it's really sitting in the service provider network. So from a technical challenge then, while we have latency, the average latency across the world is roughly 200 to 300 milliseconds. We saw an average about 260 milliseconds. So that really presented a pretty big challenge of how you deal with this problem and the idea that they didn't want to really create special versions of OpenStack. They wanted to be essentially core release trained or on the standard release. They didn't want a lot of customization. They want to be able to take advantage of the community releases of OpenStack. Be able to innovate from a hardware perspective, maybe provide additional services, but really they didn't want a special instance of OpenStack. From a functional perspective, because they are making money from this, they wanted a unified view of that customer, right? They wanted a customer inventory system. They wanted to understand globally what that customer looks like, how many VMs they have, how many networks they have, how to do IPAM across all these sites. They also wanted to offer best placement services, right? So when a customer says, I have some video on demand that I want to deploy, I have these locations, we would basically find the best place maybe either on latency, geolocation, maybe there's some governance around country governance, we would place it. Then they also want to support different types of applications based on their business relationship. I mean, NFE is certainly a killer app in most service providers, but beyond that, compute resources to their enterprise customers, IoT for their wholesale customers, and allow their wholesale customers to be able to evolve based on their IAS infrastructure as well. So from a metadata perspective, they want to have complete understanding of what's going on, just like they normally do in their MPLS network, they want to understand what's going on in their IAS. So if they need to take down an instance of OpenStack or upgrade it, they want to know what customer is associated with that, with that either outage or migration, right? And be able to migrate off of that. So from a business challenge, right? This is always the hard part. We had to do an initial prototype in about 10 weeks, and this would be the basis for the production system.  They said, no, we actually want to run this on our production network. So our production PE routers, we're going to be provisioning those with live traffic. This system's going to have to run over it. We saw an average 260 millisecond latency across the globe. They wanted to incorporate that in their test. They also wanted to integrate with their BSS system, right, which is the challenge in itself. And to combine all that, there were five different vendors and other organizations that we were tying into, someone building a service portal or integrating a service portal to their customers, their existing BSS system, their new BSS system, their billing system, the whole ETOM service chain we were integrating with. So a thinly sliced function, but truly a production system and basically in two locations. So after we finish that, we're off to the races. So what it looked like is initially two locations, then over time that they've deployed this across the world, they have a back end to AWS and Azure so they can present their customers of global access to their MPLS, to Azure and AWS. And then basically allow their customers just to order on demand resources, take them down, change them, move around. And that's a pretty successful business for them. So in terms of how we approach this, I'll get to that in a minute. I want to talk about what we looked at trying to take all of those challenges to get to a prototype and then into production. We looked first at what can we do with Bear OpenStack? Can we federate it? Can we replicate data? Can we modify it in some way? And that really became a futile task. The latency and scale of this problem is too complex and OpenStack becomes pretty fragile. So even federate a Keystone at this scale at this latency is not a good option. There's no easy way to separate the domain of control of management when you kind of federate out OpenStack. So the guy in Tokyo is managing it and the guy, if it's geographically distributed, it really kind of breaks their management relationship problem. And it's hard to do rolling upgrades. I mean, when you're talking about thousands of instances, you can't migrate them from Liberty to Mataka all in one night, so you need to be able to think about how you do rolling upgrades. And then there's the issue of, you know, kind of cross-site responsibility. And the biggest problem I would say that we ran into from this perspective is how do you tie OpenStack into a BSS system, right? And what we really found is that the OpenStack APIs were much too complex to be swallowed up, integrated, not let alone one OpenStack, right? Where you've got, you know, EUIDs and all that. But really, how do you do it from, you know, thousands of perspective, right? I mean, the BSS systems really deal with something at a different level, right? So we went on to the next thing, as we looked at TriCycle, we actually think this is a pretty interesting project. It's trying to solve this from this perspective as well. When we got into it, though, it just, the project seemed a little bit too fragile, a little too early for what we're trying to do. We also saw some documented performance issues that probably couldn't be solved very easily and we didn't want to present that to the customer. So for a number of reasons, we kind of put that on hold. Also, it didn't really solve the API problem for integrating with the BSS system. And it just didn't meet the customer timeframe. You know, we could have built upon it and did some things, but we just didn't see a timeframe that we could actually get it in. So we ended up doing something else. I'll talk a little bit about the network. So, and this was talked about in previous, I think it was the previous maybe open stack summit, is that, you know, we all sort of talk about can we distribute at layer two? Well, it turns out that most applications can work with a distributed layer three. And so there's only a few special use cases for layer two, a distributed layer two. And when you think about this complexity in this latency, layer two becomes a problem, not just managing it, but also for some of the applications doing 300 millisecond a layer two, probably doesn't work. We'll come back and look at this over time, but maybe those special use cases, but we decided not to work, try to get layer two to work. So what do we do? Well, trying to reduce complexity, we wanted to keep it simple. We deployed a very, very simple mechanism of deploying open stack. Basically every open stack instance is completely isolated. They don't know about each other, so there's a really sure nothing. That allows the service provider the best possible management, migration path, and innovation of open stack itself. It fits into the organizational very neatly and into the organizational, basically the management, the organization management's right, so they have different regions around the world. Maybe in Sydney, they have outsourced the management of their cloud. In Tokyo, they've got some people there in Africa. They have a service provider that helps them. And it also allows them, what they're thinking about is specialized hardware for specialized applications. So it really allows them to build up different open stack instances and then start playing with different innovations of the hardware, right? So different types of disks, hardware acceleration for maybe video streaming, maybe some hardware acceleration for blockchain, for IoT. And it really allows them to kind of mix and match clouds and provide sort of capabilities and innovate in this sort of a distributed way. From a networking perspective, it actually was pretty easy. They're already an MPLS customer. This fits nicely into their business model. So from a, inside the data center world, we use VXLAN. From a WAN perspective, we used a service provider MPLS and we just tied them together, right? So a global customer has an MPLS VRF and we basically tied their VXLANs into that VRF and let the customer look as if that, those VXLANs are part of their MPLS VPN, essentially. And this is also compatible with, service providers had a pretty unique problem in that. They have these, what's called NNLinks, right? They're partners with other service providers. And so this fit easily into that. So if a customer had a cloud on AT&T integrating in an MPLS VPN with a cloud in their environments, they could basically share the same global distributed cloud. Layer three is pretty well understood. There's really no complex edge cases so it's pretty interesting. So that just left, how do we tie all these open stacks together? Well, we decided to look at this from an orchestration perspective on sitting on top of open stack. And that turned out to really meet the timeframe of the customer and all of the goals of the customer. This allowed us to then create metadata outside open stack that joined all the open stacks together. Metadata about maybe location, about capabilities of this pot of open stack, about hardware in this, about the latency between the cell tower and this site or maybe some cost associated with a particular open stack site. It also allowed us to extend the customer relationship outside of open stack and keystone. So service providers have a very complex view of a customer, right? It's not just their end customer but maybe in their MVNOs or the relationships are selling the service providers that sell the service providers and then resell them customers. So it allows them to have this complex understanding of a customer and then tie all that together across all their open stacks. So a unified view of that customer outside of open stack, unifying and basically proxying to the various keystone identities in each of the open stacks. So we kept that relationship from an orchestration perspective. The next thing to solve was how to tie open stack into their BSS systems, right? So what we ended up developing is a set of really powerful APIs that would do all the things in open stack from a very simplistic perspective or a very powerful perspective, if you will, that could be easily integrated with a service portal or a BSS orchestration system or some other orchestration system. We'll get more into that as time goes on. And it also allows us to integrate with other open stack or non-basically open stack objects, routers and different types of equipment that allowed us to connect into MPLS and we can coordinate that all with the same sort of single API, right? And it also provides essentially unlimited scalability, right? So we're not trying to scale open stack itself and orchestration systems are used to working when tens of thousands of routers, hundreds of thousands of ports, so we can really scale from that perspective. So what does this look like? This is representative of their environment. This is just representing basically two sites, kind of a simple picture. And essentially we have, from a top side, we've got different business service systems talking to a multi-site orchestrator and that multi-site orchestrator then communicates to open stack Nova Neutron from a low level API perspective to do the things that is required from a higher level perspective. We've got an SDN layer doing VXLAN basically into a gateway that then is peering with their PE routers and their VRFs. And then we can then orchestrate, create VRF sites on demand and tying that basically into open stack, that tenant and open stack and then maybe provisioning ports on AWS and Azure to connect that MPLS VPN also into a site into AWS and Azure. So by solving this at a orchestration layer by creating a bunch of standard API as we really solved another problem which was kind of dogged with them that they really didn't know they had until we got into this, one is security, right? So there's no security boundary that goes above the orchestration layer. So no system has access, root access to open stack or admin access to open stack. It's all managed below the line. And that's important for a couple of reasons. So as you think about providing flow through provisioning a service portal that says, I want to provision a VM across my cloud, I may have different types of orchestration systems. Mano and a V which is really important now becomes a client to this orchestration system that can serve up and maybe there's an IoT version of that as well. And the BSS system that can go down. So really having a common set of APIs, the more important problem though, the more important problem is that they don't want to dictate to other service providers what orchestration system to use. So this allows us to create a common standard for multi-site APIs that's AT&T for example can reach in and provision in this service providers environment services just like they do on end services without giving them root access. So this allows them to maintain that relationship with their other service providers from a wholesale perspective. That gives them a whole new opportunities to sell from a wholesale IAS. So what does this look like from an orchestrator perspective? I won't go into the details, but essentially you need a set of common standard agreed upon APIs that you can then talk, provide to other service providers to say this is how you order services from our cloud. You can provide a set of low level APIs but no root access, but really it's the powerful APIs that says connect this customer to this site. And basically go work with the standards bodies to make this a standard where can be working with the MEF to propose a set or a subset of our APIs into the MEF so that other service providers can start thinking about this problem. Also you need a workflow engine really to support an aggregate of objects. If you think about animicity, you basically want to provision a customer in a site and do all the things as an atomic operation. So you need to have a workflow engine to combine that into an atomic operation. And it has to be high throughput and fan out. So some of the stuff they're doing in Tricercle I think would relate to this and so we'll work with them. Also you have to have a database which can extend the ideas of this multi-site or multi-cloud, the metadata beyond what's currently exists in OpenStack. So location and customer inventory, customer relationship, capabilities of different sites, different locations, cost of sites. And then you need to have services like IPAM. So the idea that there are some subnets, neutron subnets in sites that are not managed, that are not managed, they're local to each site.  So you need those types of services. Floating IP or what they call GIA for example, you need to be able to manage on a per site basis and push that data into OpenStack from a global perspective and understand the routing, the BGP ASN routing of those IP addresses. And obviously some security you need to build in. So just quickly I'll go through what the APIs might look like or do look like and then I'll run through a quick example. So this is really a customer oriented API language. So it's all about managing the customer and I kinda look at the OpenStack APIs as a set of Lego blocks, right? You can build anything you want with a bunch of small Lego blocks, but this is really a very special purpose. I have a customer and I wanna deploy that customer, I wanna find a location of that customer and I wanna build on top of that customer, right? So customer objects, site, machines, network, storage, and it's all based on the customer. And then to be able to find sites across the globe, you've gotta have location based services, you have to have capabilities, flavors. What are the specifics about each site? Then you can basically present a higher level location oriented API to say find me the best location for this application. So a quick run through, create a customer, that creates a customer globally that doesn't present in an OpenStack. Then you basically find the best location for that customer's request. Let's say there's 100 sites around the globe. Each site is associated and then you instantiate that customer in that site. And this is completely seamless to any user operator, but you create the Keystone user, you create the Nova, you create all the things to get that site up and running and you combine that together across the globe in one set of workflows. Then once that customer is in, then you can support additional services like managed subnets, unmanaged subnets, creating an ACL to give access across that MPLS link and then create any VMs that are needed. You can support things like heats, templates, you can push those down or orchestration like MANO orchestration, for example, and then traditional VM lifecycle. So I'm gonna wrap up here and if there's any questions, but really what we wanna do is take what we've learned from an API perspective and orchestration perspective and bring that back in the community because I think that the deployment of multi-site or hyper-distributed OpenStack, we're really on the cusp of this and I think we wanna get ahead of this in the community and really start thinking about and how to approach this, how to provide the standards for and essentially the leadership for the community. And we think, so we wanna basically find the appropriate project. This might be TriCycle, I think that they have a lot of interesting stuff already. They already have some orchestration capability. We also wanna work with contributors. We're gonna publish our APIs into a project, our designs and some sample code that we've created. And then we're gonna go work with the standards bodies to fine-tune and to present these APIs from an orchestration perspective into the standards bodies. If you want to contact us or help out, be involved, you can contact me at this address or Sarab at his email address and I guess I'll open it up for questions at this point. So the question was, so when we're doing independent OpenStack and each have their own Keystone, how are we presenting a unified view of the customer? That is actually being done outside of OpenStack in the orchestration layer. So the orchestration layer essentially has the knowledge of what that customer looks like from a service provider view, right? The complex relationship. And a key, a foreign key to that tenant, to that user, to that object inside those various OpenStacks, right? And so everything essentially would go through the orchestrator to get to OpenStack. We're not giving access of horizon. In fact, the way, if you imagine, trying to give 100,000 views of horizon to a customer just wouldn't work. So everything goes through a different service portal and a different service chain. We are building a compatibility layer which translates to those OpenStack APIs and we're also presenting a higher level set of unified, right? So there's two, there's a low level set of APIs which are somewhat compatible, mostly compatible with OpenStack that they can use but from a higher level perspective, it's this unified APIs. So the retail customers go through a portal and a sequence of management systems that give them the full capabilities of OpenStack just in a different way. The wholesale customers can use their own management systems, use their own Mano, for example, to tie directly into OpenStack through an orchestration layer that provides both high level and low level APIs. Any other questions? That's correct. So the question was, is that we're using, how do the APIs work? There's standard OpenStack APIs from the orchestrator down to the different versions of OpenStack. So they may have Metaca, Liberty, versions of OpenStack. So we're from a northbound perspective of OpenStack, we're using the standard OpenStack APIs. We're presenting a set of low level APIs that's similar, very similar, almost compatible to OpenStack, above the orchestrator on the northbound, but we also have a set of APIs which are easily consumed by management systems. So there's kind of a dual set. As well as we're working on things like Tosca, being able to send a document, for example, and have the orchestrator do all the things necessary in that Tosca document. Yeah, yeah, sure. Every OpenStack instance is completely managed by a different group, a different person, and it has a different release cycle, has different hardware, and that's the job of the orchestrator is to be able to be compatible and be able to understand the difference between the versions of OpenStack. And this is, if you talk to anybody that understands orchestration at an OS level, this is pretty commonplace. We're used to dealing with different versions of Cisco routers, with different versions of OS of Cisco, with different capabilities of Cisco, right? So it's a very similar problem. Element management system, the EMS. So from a VNF perspective, they're essentially provisioning, they're sitting on top of multi-sites and they're saying I want a VNF, let's say SD-WAN, it's Sydney and in New York, right? To sit over the top. The VNF, so there is a MANO system that actually sits on top of multi-sites and it communicates with our APIs and says, and so it's a standard, I mean, there's one of the five standards, right? Of MANO, implementations of MANO. And so, the EMS for, let's say, a router that sits on top. So multi, our orchestrator can do that. So it is possible to do that. We are not doing that today. Next question over here. Our orchestration tool is hyper-distributed. So it's completely clustered and it can sit in a single location or it can sit in multiple locations. It's a deployment choice. Yeah, you can stop by our booth and we can tell you about the details of it. Okay, one last question. I didn't hear your question, sorry. I didn't hear your question. Just speak louder. If we are talking about monitoring, yes? Monitoring, yes. So you have a multiple, how to say, common platform for multiple sites. I mean, the orchestration will be, you have the same point as your orchestration for monitoring system. So they have distributed. Yeah, so they have a separate network monitoring and compute monitoring, basically log management. We are taking some telemetry data. So we're pulling in telemetry data that we need, but they also have a global monitoring system that does collection and distributes the events to the different locations. So they do have a pretty sophisticated set of management tools already that we're tying into. So does that answer your question? Well, more or less, and another small question. From the orchestration perspective, if you collect something, as you said, as you collect something from your infrastructure, yes, does your orchestration system able to perform kind of a policy based on collected information? Right, right. So the idea is that that definition of find the best place to deploy a resource, it takes into account a number of things. Some of that is locations, some of that is latency to the customer request, some of that is capacity, some of that is hardware. So let's say they have a pod of hardware accelerated for blockchain for IoT, right? That you can basically, we have metadata that describes that. And also the capacity, the utilization of that open stack, right? So how much utilize, how many compute, how much capacity does that open stack have? Things, because I just think for myself, it's pretty interesting, because I believe it's possible to, technically it's possible to collect some information and propagate some rules to infrastructure. But what I also think it's pretty complex to map your business through, convert your business through into technical rules, yes, which you want to install in your infrastructure. So that's why this, yeah. Completely. And so I'm only showing you a very small portion of their system, right? Focused on open stack. There's no one orchestration system that can solve everything. That's why service providers typically have a whole level of applications that integrate together. That's why one of the reasons for an orchestration, a domain orchestration that's just dealing with a distributed open stack, for example, is that they can bubble up the data needed to present to a higher level system that can make more aggregate rules, right? There's no way you would be able to put Keystone, UUID, and all of this in a business system, right? It's just, it's too complex. It would fall over. Thank you. Thank you for all attending. And if you want to get involved, stop by our booth at C5. C5, thank you.


A couple of troubling things about this case, of course, is the amount of the money was over $126,000. Now this is not tax money. This is money that had been placed in the commissioner's account after property had been sold, and I suspect that a lot of these were airship type lawsuits that could not be determined who was supposed to get the money, and so the commissioner is supposed to hold it until the distribution is made to these lost airs. I'm troubled by why did he not keep a closer eye on these accounts, frankly. Why did he not keep a closer eye on these checks, and why did he not discover that 75 checks have been forged over a more than a one year period? I don't know the answers to that, but it is troubling that because he did not catch this in time, the amount of money lost out of his office is over $100,000.


Hi, Dr. Jared here. I had some fun today trying to cut through these Zirconia crowns for a lecture slide to kind of highlight some of the differences between these major brands of crowns. You can notice a few different things with these. I'm going to be sharing some tips and how you can do preparations for whatever crown. I think it's really important that you understand whichever brand you choose, the shape of these crowns when you look at them. One way to also do this is to go ahead and take a PBS impression of these crowns. I unfortunately don't have time for that, but I will be updating that for some future lectures here to come in 2024. I hope to see some of you in Vegas, reunite with some old friends, and get back to where I did my residency training at UNLV. And hopefully I'll see some friendly faces there.


So Jaclyn Hill is back after the whole lipstick fiasco and her disappearing and this is such a momentous occasion that we're back to the old setup baby. 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 what I try to do is take different topics going on in the YouTube community trying to see what lessons we can pull from them to improve our own mental and emotional well-being. So if you're into that stuff make sure you subscribe and ring that notification bell and yes before we jump into Jaclyn Hill's return real quick announcement go and check out my website www.theRewiredSoul.com. My brand new book cancelled is out now and oh my god like hundreds of you have already downloaded it. It's totally free go check it out if you do a five dollar donation or more when the audiobook comes out in the next week or so you'll get a free copy of that but anyways that book I analyze cancel culture on YouTube I share some of my own experience and I talk about other situations in YouTube and that's why I'm excited to talk about this topic with Jaclyn Hill like oh I'm gonna get some flak for it you might cancel me for it but her video I give it an eight or nine out of ten. So yeah if you are not caught up to date on what went down with Jaclyn Hill and her lipstick launch which I doubt that you're not caught up to date if you're watching this video go check out the videos from Spill she did a two part series so that went two or three parts either way go check that out their long videos but it will give you all of the details on it all right but anyways I think the last time I made a video about Jaclyn Hill she took a break from social media she was working on her mental health and now she's back so there's a few clips that I pulled but listen very carefully watch this whole video like my videos are for you the viewer like I was watching this I was you go girl like there's so much that all of us can learn from it everybody I mean it's it's just such an outpour of love and I am so thankful for you guys you have no idea and to all the influencers I know that when things get rough influencers don't want to jump out there and be be the person to stand up for somebody else because it's scary and you don't want to get involved you know it's like you're like oh gosh like they're going through hell like I don't want to burn with them you know so it's like you kind of like step to the side like oh it's kind of like watch it happen and I completely get that that first clip right there this is something that I talk about in my book um when you are being cancelled when the hate mob is coming after you a lot of your influencer friends will just scatter all right and like I dedicated a few chapters to discussing some of my relationships so I can definitely empathize with what Jacqueline Hill is dealing with maybe you've dealt with this in your own life if a rumor or something or maybe you just screwed up and people distance themselves from you but anyways like Jacqueline Hill said like one of the things that I'm truly grateful for was there were people who could not support me publicly because the hate mob would go after them but they were supporting me behind the scenes I have some people who still talk to me like every day you know and they see the improvements and the changes that I'm doing and they're just they're giving me some motivation and some inspiration but anyways if you want to learn more about that go get the book it's free I'm just terrified of seeming like a victim I'm terrified of saying the wrong things of people just you know picking this video apart because I know that's what's going to happen and I know that it comes with the territory of course like I get all of that but I'm just still really I'm just really scared I really I must be honest with you guys it's hard for me to say that because I'm sorry guys I know that I'm not like supposed to cry and I'm gonna try my best to edit any like tears out of course because that's not the message that I want to get across so that clip right there is very interesting to me it's really interesting because like throughout the video she has to talk she has to tell you all the things that she's not going to do and this is how cancel culture works like listen Jacqueline Hill massively screwed up I have massively screwed up anybody out there who has had the hate mob attack them has massively screwed up but but like when we make these comeback videos another and when any youtuber makes a comeback video or a video like it gets picked apart like it is insane and it lacks so much empathy to not understand that even though Jacqueline Hill screwed up like she's a human being who has emotions and the fact that you have to like edit out like you're crying and things like that in fear that someone's going to make a video saying that you're just trying to manipulate your audience is absolutely mind-blowing right like something I talked about in my last video is like like until you go through this you're never going to fully understand like I've been through it and I don't fully understand like my screw-up was not as big as Jacqueline Hill's screw-up you know what I mean like she has the right to feel crappy about this and it just sucks because I don't think youtubers should have to come on camera and explain all the things that they're not going to do just out of fear that people are going to dissect it and make videos about it like be a human have emotions but anyways I do think Jacqueline Hill you know she did great with this one like when she made her last video when it came back like I think when I talked about like she came off like kind of abrasive and I'm like dang girl why are you yelling at me you know what I mean and this video I feel she did much better but the reason I had to get away from social media and just fully delete it is because at that point I had refunded everybody there every single penny they had spent I was humiliated I was embarrassed and it was time for me to start picking things up and putting the pieces back together and rebuilding you know as a CEO as a boss as an owner of a brand you don't get to just sit back and be like like you have to start rebuilding right yes yes yes so if you're a loyal subscriber who's been following the channel for more than like I don't know five minutes you know that we start off every video with we talk about the problem but we focus on the solution and that's what Jacqueline Hill is talking about like this is the mindset that I had to get in and I hope to God that you get in it too like I had to get into this mindset when I got clean and sober seven years ago like I would just mope around I would just sit in self pity right and that's what Jacqueline Hill is talking about she was just sitting in self pity like oh my god I'm a failure everybody hates me and out of that like you can only do that for so long right like how long are you going to do that for like if you want to take what I call the pity party method like what I personally do I give myself a certain amount of time all right typically maximum it's like three hours three hours to just feel sorry for myself what was me everybody hates me and everybody's terrible oh my god right after three hours is up of me just wallowing in my own pity then it's time to get into the solution and that is one of the reasons why I was so excited to make this video because Jacqueline Hill she's like you know what I gotta I gotta fix this I gotta do something I gotta move forward and do this and if you guys don't take anything from her video except for this listen to me very carefully the fact that she's talking about how she is not going to give up on her dream like oh oh my god like I can't tell you like when I was going through this like the amount of people like delete your channel I still get people telling me to delete my channel right and like all I can think is like when I look at people leaving those comments I'm like I feel bad for you like I feel bad if you feel like when you screw up you should just give up you know what I mean like that's not what we should do so I'm super proud of Jacqueline Hill like to learn and hopefully grow from this and that's what this next clip is about it's a lot it's aggressive and I definitely was not prepared and I definitely was very ignorant in this entire process of thinking what it would actually be and for that I am grateful I'm it sounds so weird but I'm grateful for the fact that this happened because I immediately got to learn such incredible lessons on being a boss on running a company on how to talk to people on hire how to do all of this and I'm so grateful for that in this process I'm studying for my words I'm just my mind is all over the place yes yes yes that clip right there like the gratitude okay like you guys like this is something that I try to teach people all the time it's something that I had to learn as well be happy and grateful for your failures okay like there is no such thing as losses there are only learning experiences so what Jacqueline Hill is talking about is like she had this catastrophe happen on her first like solo brand launch right but she learned about so many things that can go wrong like she learned about it like yes it definitely sucks that so many people were affected by this and she's trying to make it better by she gave out refunds and all that other stuff right but she learned so much like she learned so much about the importance of quality control right she talked about how she fired a bunch of people brought in a new team so many different things so I want you to think about that with your own life too like you guys like when I come here and talk to you guys and try to give you suggestions that might hopefully improve your mental and emotional well-being I'm not coming from this place of all high and mighty like I'm this perfect human being like listen to me just mean you real quick I have literally made every single mistake that you can imagine all right but I try to learn from them and I'm still gonna make mistakes you see what I mean like you guys check it out when you screw walk like the only way to go is up like that was the beautiful thing about being a hopeless drug addict my life could not have gotten any worse you know what I mean so no matter what it just went up up up up from there you know that's how it's been for the last seven years so remember that like no matter what you've been through in your life my suggestion is to try to look at these things and see how it's made you stronger how it's made you better like a great example is relationships like so many people when you get out of a relationship with somebody so many of us are like oh my god I wasted so much time I wasted so much time no you didn't waste time you learn stuff like my beautiful girlfriend Tristan like even though she got she has to deal with my pain in the butt right like I've learned so much from screwing up other relationships that she's getting the best version of me baby she's smiling you can't see it but she's smiling right now at the end of the day I have to rise up it doesn't matter how much I don't want to film this it doesn't matter how anxious or depressed or whatever I'm feeling it doesn't matter I signed up for this gig I failed the first time I'm gonna keep going I have got to get back to YouTube I love it so much YouTube is one of the things that yanked me out of my depression you know the most depressed I've ever been in my entire life is shortly before I started YouTube so yeah that right there right there which talks about she just got to rise up and do this thing like earlier in the video she talked about how this comes with the territory like holy crap like like I get some flak sometimes and I get it because sometimes I get passionate like I am in this video it's not all scripted like my last few videos have been but anyways like what she's saying right there is just what I wish every YouTuber on the platform understood or or learned eventually and hopefully you don't got to go through the Jacqueline Hill situation to figure this out like this is what we signed up for like when we put ourselves out there in public like we can't expect to just get all of the good and none of the bad like and it sounds like she's become more aware of that like listen like if I screw up people are gonna say things people are gonna make videos people freaking biochemists are making videos about Jacqueline Hill right but she's finally becoming aware enough and losing that entitlement to say oh my god nobody should make videos about me like it's what happens all right like we have to understand the more we want to achieve in life the more stresses come they're not they're not terrible as they might have been before but they're new right like when you make a bunch of money you got a you got a bunch of new taxes you got to pay and things like that like when you go to college you have college problems instead of high school problems right no matter what we do there's going to be new things that come along with it and she's like now I just got to get up and go do the same and one of the reasons I wanted to talk about this right here is because you could tell she's giving herself tough love I give tough love we even got some merch in the store that says tough love but anyways like when I say it to you I can come off kind of like a dick all right like what I love about Jacqueline and this is just something I have to do too and I hope that you do too like you have to just at a certain point you gotta say all right it's time to get up and go go to work time to get up and go into the solution because we get all touchy and like sensitive when other people say it to us but we have to train ourselves to get up and go into that solution you know what I mean I try to be polite and try to be nice but still sometimes I'm just like not the way I should be and I'm out of line and I was out of line and I reached out to her directly and apologized to her and she was very sweet for accepting my apology but still just publicly I want to say that that wasn't cool for me to not sit back wait see if anything else happened do investigation I should have DM'd her privately and had a conversation I should not have done that and so for that I am very sorry and will definitely be more mindful of that in the future. The last thing I want to talk about is that clip right there because this is just something really fascinating about cancel culture all right so Jacqueline Hill had she didn't have to but she chose to she realized that she was in the wrong and apologized to that young woman privately in DM's right she apologized privately in DM's they're okay now but because of cancel culture Jacqueline Hill had to talk about it in this video you want to know why because unless the hate mob knows you did that thing then did it really happen you see what I mean like isn't that kind of interesting about cancel culture because then you're kind of in this lose lose situation because it can be really easy for people from the hate mob to say oh Jacqueline why'd you have to tell us that you messaged her privately if you messaged her privately why didn't she just you know leave a private right but if she didn't tell you people would continue making videos because it's brought up in almost every video about Jacqueline Hill about how she sassed that young woman you know what I mean so if she didn't tell you then she would have been screwed either way so much with cancel culture is lose lose right but I also like how Jacqueline Hill discussed this because this is something that I had to learn and I'm still learning right like for me I'm just me I'm just Chris the guy in my little apartment making videos but I have an influence now I have a following I have to be more careful with how I respond to things and if I'm being honest with you that's why I block so many people because I cannot respond in a calm fashion you know what I mean so anyways it's great that Jacqueline Hill was self-aware of that fact and she's trying to learn and grow from this experience all right but anyways let me know your thoughts on this like if you still want to cancel Jacqueline Hill my channel is the wrong channel for you like here at the rewired soul we are against cancel culture all right so make sure you go to my website the rewired soul dot com get your free copy of the book canceled or you can do a little donation get the audiobook for free when it comes out in the next week my editor Zach is working his butt off on that audiobook all right man 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 because I make a ton of videos and a huge huge thank you to everybody supporting the channel over on patreon you're all amazing and thank you all so much who have donated who have downloaded the book like it is just blowing me away and I'm so grateful I love all of you all right thanks again and I'll see you next time


You'll experience patient care that is specific to you with exceptional follow-up care that ensures your hearing and balance needs are being met. Audiology Associates at 1428 Northlake Drive in Prestonsburg. On Friday, December 1st, North Point Academy students involved in the Jobs for America's graduates program opened their when-in-need thrift store. The store sits just behind the school and is entirely owned and operated by the students. All profits go directly back to the school and any donations are welcome. This is a complete student led. This is a part of the JAG class were to teach employability skills. So we've set up this thrift store for the students to get some employability skills. We operate off donations. They're learning also people skills, learning to deal with the public. So yeah, there's just a whole lot of things that the kids can learn, you know, from operating this store. It's a great place to come do your Christmas shopping. You get some good stuff, get it really cheap, and make somebody happy for Christmas. As well as yourself, save yourself some money. Make yourself feel better. Working in the store gives students real-world experiences such as counting inventory and interacting with the public. They believe adding work hours into their curriculum is a big benefit. Oh, preparing for it was definitely a little bit chaotic at Tom's because we had so much stuff and we didn't really have a plan. It was just kind of overwhelming because at first it was all just sitting on the ground and we had to find spots for it and we decorated some trees. We have put a lot of effort into our store, but it feels very rewarding to have people come in and be able to buy stuff, you know. This is kind of like the point of JAG, Jobs for America's graduates. Rick, it's getting us ready for the real world, getting a job and stuff like that. So it's kind of like I'm already getting some experience before I have to go out and do work. Reporting for Mountain Top News, I'm Nick Collum.


this is Marc. I'm doing great. Thanks for asking. Could you pass me the book with a blue cover? Despite my warning, he quit his well-paid job. My house is next to a famous hotel. In this lesson, we're going to look at prepositional phrases, so stay tuned. Yes, what are prepositional phrases? They are a number of words made up of a preposition and its object. The object could be an article, a noun, a pronoun, a jarron, or even a clause. So I gave you some examples through the between a and like the until morning, for example, during etc. According to someone around the block, for example, near the house, for example, of the. So a prepositional phrase can act as an adjective or an adverb. Let's look at acting as an adjective. So we have the example. Could you pass me the book with the blue cover? So with the blue cover describes the object. The book, right, is the object of this example. So with the blue cover. So this is the adjective. So the prepositional phrase describing the book. So it's acting as an adjective. Another example.  So in my area describes the nightlife, right? The nightlife in my area, prepositional phrase, is quite fun. So this is prepositional phrases acting as an adjective. So acting as an adverb. The example that I gave you at the beginning was despite my warning, he quit it, his well-paid job. So despite my warning is acting as an adverb here. And it's a prepositional phrase. Despite plus the object, my warning, a noun. Another example. Let the old lady enter the office before others. Let the old lady enter the office before others. So for example I'm saying this to an employee. Let the old lady enter the office before others. Before others is an adverb here. And it's a prepositional phrase, right? Because we have the preposition before and then others which is a noun. So I said that prepositional phrases can act as adjectives and as adverbs, but also as nominals. There are cases when some words can act as nouns, but they aren't actually nouns. These words are called nominals. If a prepositional phrase is preceded by the verb to be, they work as nominals. Let me give you examples to explain this better. My house is next to a famous hotel. So next to a famous hotel here is the prepositional phrase, right? Because we have the preposition next to and then a famous hotel a noun. And so if we conjugate this phrase, we see my house as the subject, then we have the verb to be and then the prepositional phrase next to a famous hotel. So this is the nominals. These words are called nominals. The last example, my debate was among the most interesting. And here we have among the most interesting the prepositional phrase and it's acting as nominal. So among preposition plus the most interesting is the adjective. Remember though that prepositional phrases are extremely important because they can modify the sentence completely. So think about what you write. First try to understand their function and form in order to choose a style, especially when writing. That's it for today. Thank you very much for watching. If you haven't subscribed to my channel, I suggest you do. Next week you'll get a new lesson. If you want to type your own example under this video of a prepositional phrase, please do so. If you want to share the lesson, go ahead. Thank you very much for watching and see you next week with a new grammar lesson. Take care. Bye bye.


Everybody forced here we're being 2022 select football or hobby hybrid five box number nine random teams We'll do the random right now, and then we'll just get right to the boxes. Good luck everybody Say one One Means we're re-rolling snake eyes is re-roll It's a four and a four. All right, okay doubles Okay doubles eight times on both here names first one two three four five six seven and eight Ali a down to Brian are and the teams eight times one two three four five six seven and eight Bills down to rams Raiders Ali with the bills Brian are dolphins Usman Colts Greg L Falcons Garrick with the Jags Usman jets Chris V Eagles Jim G Bengals Derek W with the Giants David F Seahawks Mitchell J Lyons Brian are Saints mark F Panthers Ryan B Steelers Mallory with the Bucks Jason a Broncos Brad C Titans John B Cowboys Jason a Ravens Anthony P Niners Jim G Packers Brian are Texans Sean Emma chiefs William s Patriots Ryan B with the Cardinals and Browns Roberto Vikings Christopher D Commanders Brian are Chargers Nathan a Bears Brian are Rams Raiders. Let's get these results posted And we'll rip Sunday fun day down to tend to go tend to go Sunday fun day Again not gonna recap this one either really short break here Come on mookie hit a banger another one another one Silver Concourse rookie Rashad White Bucks Red Deshaun Watson to 49 Premier level Browns Wanted Taylor Tyler Smith Pierce kill V-less red rookie concourse Josh Pascal the 49 and Lyons DJ more in Hutchinson Son of a Knight concourse disco Mahomes chiefs Lauren Zion Johnson One Thornton Darren Waller silver Dallas Goddard Eagles Got blue rookie a concourse Titans on the premier level to 25 Michi and Good hecky silver concourse Justin Fields Bears blue Premier level of Iska Chanel Panthers to 25 six to 25 Lawrence and Mijai Sanders strange Red Kyler Murray premier level to 49 Cardinals color match Davis Price Kenneth Murray Christian Watson concourse with a Russell Wilson concourse disco Broncos mr. Unlimited Strike up a loopy Silver Orlando Brown chiefs red concourse Devonte Williams of 49 for the Broncos Garrett Wilson concourse rookie for the Jets followed by an Olava a concourse rookie blue to 25 Saints 24 25 on the Olava Nice card Jack Jones and Brady Adams Silver rookie Kenyon Green Texans Red for the Bears concourse rookie if you wish Joe and Gina to 49 Silver rookie concourse Khalil Shakira bills red sweet level Nick chubb to 49 Browns Mirror white Josh Allen Bryant Rookie sweet level blue Texans Jonathan Owens to 25 when you see a green or a gold or a black here There's a birk space Pretty free with the double. That's what I want to do. I want to go to game of Dodger Stadium That's the ballpark I most want to go to that is that I haven't been to there's a few at the top of that list But Dodger stadium is probably it's the next oldest one that I haven't been to so silver concourse rookie Olavae Saints Red rookie Shahid for the Saints premier level to 49 and to 25 Alec Pierce on the rookie jersey order for the Colts Also, one of the biggest and will be stadiums is Dodger Stadium, right? Isn't it still like the biggest one as far as like capacity rookie concourse red trail on Berks Titans? It's a 49 nice Berks There are two cars there. Sorry. Oh nice one I'm assuming he was a Dodger at the time concourse disco DJ more Panthers Corral and Shahid blue concourse rookie Patriots Taikwan Thornton That one's out of 25 Nice one, too. He's got some he's got some hype Silver concourse rookie Jake Ferguson for the Cowboys red sweet level Brady to 49 bucks blue premier level Tyree kill dolphins Number to 25 Tyree kill will look a lot better in a Patriots uniform. No Stop Red Joe mixing premiere map premiere level to 49 bangles Dude it really feels like a long time ago Vaughn 2016 was the World Series win. We're Like seven years removed from that Silver Tyree kill dolphins and gold DJ more Panthers WR1 in Chicago now one of 10 premier level Ice cart for a combo spot there and that's gonna do it. Thanks again everybody H2 5 box number 10 coming up next


Hello everyone, my name is Jiaxin Guan and in this video, I'll be talking about our work incompressible cryptography. This is a joint work with Daniel Wicks and Mark Zendry. So to begin our talk, we'll take a look at several motivating examples. So let's say we have our favorite friends Alice and Bob and they're not doing something crazy. They're just doing a very simple protocol. So what Alice does is sends over an encrypted document over to Bob and here comes our eavesdropper Eve, who doesn't do anything super malicious. What Eve does is simply eavesdrops on the channel and makes a copy of the encrypted document or the cipher text. And then at a later point of time, maybe a month later or a year later or maybe 20 years later, Eve is somehow able to get hold of the private key used for the conversation. So Eve is able to do this maybe through a security breach or maybe through some social engineering or maybe even by just going directly and interrogating Bob. Anyhow, Eve gets hold of the private key and then what you can do is to simply use this valid private key to decrypt the stored cipher text and therefore is able to retrieve the original message sent by Alice. So to prevent against this, we will need something we call forward secrecy. Essentially saying that a private key leaked in the future should not compromise the security of the messages that are sent before. However, to achieve forward secrecy, we would either need the protocol to contain multiple rounds or we will require Alice and Bob to be constantly updating their keys. Both of this could be undesirable under many scenarios. Similarly, consider this scenario, Alice again is talking over to Bob by sending over some encrypted document. And comes Eve dropper Eve who makes a copy of the encrypted document. But then at a later time when Eve is asking Bob, let's say Eve actually interrogates Bob in this case and interrogates Bob for the key, what Bob can do is instead of providing the actual private key used in the conversation, Bob is able to provide a fake private key which nevertheless causes the message to decrypt, causes the cipher text to decrypt. But this time to a fake message, let's say to a cute picture of a cat instead of the super secret message before. But Eve has no way of telling whether Bob is providing the actual private key or a fake private key. So this is what we call receiver-deniable encryption. And in fact, it has been shown that receiver-deniable encryption is impossible in the standard model. In the last example, let's say Alice is holding a party at her house on a Saturday night and is sending over a party invitation over to Bob. But in order to convince Bob that this invitation actually comes from Alice, what Alice does is attach a signature on the message stating that there is a party tonight. And again comes our Eve dropper Eve who Eve drops on the channel and makes a copy of the message together with the signature. And then at a later point of time, say it's Tuesday night where everybody is busy working or resting, what Eve does is simply replay the message together with the signature over to Bob. From Bob's point of view, he receives a message from Alice saying there's a party on Tuesday night and there is in fact a valid signature on the message leading Bob to believe there is actually a party and going to Alice's place only to find out there's no party at all. So this is what we call a replay attack for signatures. And it turns out that to prevent against replay attacks, we would either need to make the protocol multiple rounds, therefore requiring interaction between the two parties, or we will require Alice and Bob to maintain a synchronized clock, or we will require that Bob here to verify to maintain a state. Again, all of these three scenarios could be undesirable in many cases. So notice that in all of the three motivating examples before, the adversary needs to store the ciphertext or the signature. So here's the natural question. What if the adversary cannot simply store the ciphertext or the signature? What will happen in these cases? So in the first two examples, Alice sends over an encrypted document over to Bob and comes to Eve's drop for Eve, who tries to make a copy of the encrypted document. But let's say Eve cannot store the actual encrypted document. And then at a later time, remember Eve is going to interrogate Bob for a private key. But now with the private key, there's actually no message for the eavesdropper to decrypt. So there's nothing that the eavesdropper can do even with the actual private key. And therefore, we trivially have forward secrecy. In the meantime, notice that there is even no message for the eavesdropper to decrypt. So this scheme is also vacuously receiver-deniable. In the last example, Alice sends over a message together with a valid signature over to Bob and the eavesdropper tries to make a copy of the message together with the signature. Let's say the eavesdropper cannot store the actual signature, but only the message. And then at a later time, when Eve tries to produce the replay attack by resending the message and the signature, it can only send a message without the signature, and therefore it fails to convince Bob that the message actually comes from Alice. So how exactly do we achieve that the eavesdropper cannot store the cipher text or the signatures? Well, the key idea is that let's say we're encrypting a very small message, and the key idea here is that we manually blow up the small message into a huge cipher text or a signature so that its size is too large for the eavesdropper to store. In fact, this idea was used in the previous paper by Guan and Xenjie called Disappearing Cryptography in the Bounded Storage Model. So that paper is set in the Bounded Storage Model, which allows the paper to restrict the eavesdropper's ability to store the cipher text or the signatures. So what is the Bounded Storage Model? Well, traditionally in cryptography, when we talk about an adversary, we imagine that the adversary is time bounded. So the adversary needs to perform the attack within a polynomial amount of time in the script parameter n. However, in the Bounded Storage Model, which was first put forward by Yudi Mara in 1992, the adversary can take as long as it wants. We don't impose any time limits on the adversary. However, we found the amount of memory bits that the adversary can use throughout the entire attack. So throughout the entire attack, the adversary can only use up to p of n memory bits, where p is a fixed polynomial on the script parameter n. Concretely, we can imagine p being something like n squared, where the adversary needs to perform the attack within space less than n squared, whereas the protocol is still secure for honest parties, which only uses some memory around the level of n. So there's an inherited quadratic gap between the adversary space and the honest user space. So the disappearing cryptography paper defines a disappearing public encryption, which is defined in the following way. So this is a game played between an adversary and a challenger. It is very much alike the Stenry Model PKE game. So the challenger is going to sample a public key, private key pair, together with a challenge bit B, and sends over the public key over to the adversary, and the adversary sends over to challenge messages M0 and M1, and receives back an encryption of a random message, depending on the challenge bit B. In the end, the adversary needs to make a guess for the bit B, and the adversary wins if the guess is correct. So this is just a Stenry Model PKE game, and we'll take a look at how it is adapted into a disappearing PKE security game. So first of all, since we're moving into the boundary storage model, we require that the adversary maintains a space less than or equal to S for a fixed memory bound S. Notice that this space constraint is in addition to the computational assumptions of the adversary. So disappearing cryptography paper assumes that the adversary is both space bounded and time bounded. So here the adversary is bounded by space S, and also bounded by a polynomial running time. So with this bounded space, what we can do is we imagine that the ciphertexts are so large that they exceed the adversary's storage bound. And then after the adversary receives the ciphertext, all we can actually do is send over the private key over to the adversary before the adversary makes its final guess. This is actually okay because if you think about our motivating examples, even if the adversary is given the private key, there is nothing that the adversary can do because it cannot store the ciphertexts. So a key difference between this work, incompressible cryptography versus this previous work, disappearing cryptography, is actually how the memory bound is imposed on the adversary. Imagine the following two adversaries. So adversary one, when Alice is sending over the ciphertext over to Bob, would just write down all of the bits being sent by Alice. And then after the transmission has ended, computes a function with a small output, which then essentially allows the adversary to compress the ciphertexts down to a smaller state. And then the adversary just maintains that smaller state throughout the entire time until a security breach happens. On the right hand side, we can imagine adversary two, which simply writes down the bits as the transmission goes on and then just maintains that amount of memory throughout the entire time. Now if we were to set the memory bound to be somewhere between the highest point of adversary one and the memory used by adversary two, then the adversary one on the left is actually not captured by the bounded storage model with the bound s because the bounded storage model required the adversary to be space bounded throughout the entire game. However, we think that the adversary one on the left is actually a quite valid attack, because if you think about it, having a high amount of memory in a very short amount of time is actually not that intimidating. It's actually quite achievable. However, requiring to maintain a moderate amount of memory throughout the extended period of time, this seems more challenging than the previous one. So as a real life example, for example, if you ask me to store 10 terabytes of data for only 10 minutes, well, I'm happy to do that because I personally have 10 terabytes of storage at home and I'm happy to devote that 10 terabytes only for 10 minutes. However, if you ask me to store say two terabytes of data for 20 years, that seems much more intimidating because I need to maintain that two terabytes throughout the 20 years, this extended period of time, and who knows what's going to happen. I mean, personally, I might be moving and then just throw it at hard disk and I will fail the game. So essentially what we want to want here is that we want to capture these adversaries that uses a large chunk of memory when the transmission is going on, but then compresses down to a smaller state for long-term storage and hence are naming incompressible cryptography. So now finally, we're able to get back to this work, incompressible cryptography. So we'll take a look at how we actually define incompressible public encryption, how it's different from disappearing public encryption. Here on this page, we'll produce the disappearing PKE security game and we'll take a look at how we would modify it to become the incompressible PKE security game. So the first thing that we do is that we're going to remove the storage bound for the adversary. So the adversary is no longer bounded by the space as throughout the entire game. Now instead, we would use a pair of adversaries which cannot communicate between them. So there is no private channel between the adversaries and the first adversary gets the public key, sends over the challenge messages and receives the ciphertext, whereas the second adversary receives the private key and makes the actual guess. So after the first adversary has received the ciphertext, the first adversary needs to compress it down to a state st such that the size of the state is within the memory bound s. And then when the second adversary is provided a private key, it is also given that state together with the public key of the encryption of the whole scheme, together with some auxiliary input. So what is this auxiliary input is sent over by the first adversary at the beginning of the experiment, and you can think about it as containing the shared randomness for the two adversaries. If the adversaries are not in uniform, then yeah, we can do this without the auxiliary input at all. So notice that this game actually captures the idea that the adversary received the ciphertext and then can do whatever it wants using however much space it wants. But in the end, it needs to compress down to a state st that is used for long term storage. In fact, this definition, this incompressible PKE security definition, the incompressible PKE security actually implies a disappearing PKE security. Notice that it is only security-wise, we will mention in the next few slides functionality-wise they're still different. Okay. So in our work, we show two constructions of an incompressible encryption, and in fact, they have some additional features other than the security requirement on the previous slide. One of the features is called low-space streaming. So recall that in the disappearing cryptography, it is set in the bounded storage model. And remember that in the bounded storage model, we require that the honest parties, they should be able to run the protocol with a memory bound somewhat lower than the adversaries. However, when we move over to the incompressible encryption, we're moving away from the bounded storage model. So in incompressible encryption scheme, the honest parties, to run the honest parties, you would actually could require high space. Therefore, a incompressible encryption scheme might not be a disappearing encryption scheme because the honest parties, they will require high space. However, we show that one of our constructions actually supports this low-space streaming feature, such that the encryption and decryption, together with signature and verify for an incompressible signature scheme, they'll actually be able to run in a low space. And therefore, if we have an incompressible public encryption scheme, the security of which already implies the security of a disappearing PKE, if we add on a low-space streaming feature to it, and then we will simply get a disappearing PKE scheme. Another feature that we have is called rate one incompressible encryption. So what is the rate? So the rate is defined as the size of the message over the size of the ciphertext. So for a low-rate PKE, we will take a very small message and we will blow it up to a huge ciphertext which exceeds the adversary storage bound. Now let's think about the other way around. Let's say we fix the ciphertext size to be somewhat larger than the adversary storage bound, then ask ourselves how large of a message can we encrypt using that ciphertext size. In fact, that we show that one of our constructions achieves an optimal rate of one, which allows us to encrypt a message almost as large as the ciphertext size. So back then, when I was talking about a key idea, I said the idea is to manually blow the ciphertext order signature size. Well, I was kind of lying there because for rate one setting, we're not really blowing up the size. The size is still the same, but really what you're doing is you're blowing up the entropy because the message themselves could be a very low entropy. All right, to quickly summarize what we did in this paper, incompressible cryptography. So first of all, we define incompressible pke and also incompressible signatures. And we show that a low rate incompressible pke can be constructed from a standard model pke, and we show that low rate incompressible signatures can be constructed from simply one-way functions. Notice that both of these constructions support low space streaming, meaning that the honest parties can run within a very low space. On the other hand, we also construct incompressible pke and incompressible signatures with an optimal rate of one. We construct rate one incompressible pke from indistinguishability obfuscation, or IO, and we show that incompressible signatures with a rate of one is actually equivalent to incompressible encodings, which was first put forward by Moran Wicks in 2020. They show that incompressible encodings can be constructed by assuming either the learning with errors or decisional composite residualosity, and it's set in either the random oracle or the common reference stream model. So if you're interested in any of these constructions or the security proofs, feel free to take a look at our ePrint version of the paper. There is a link on the next page. But I guess for today's talk, the takeaway message I want to give is that throughout a long time, people have been using the bounded storage model to prove things information theoretically. However, in this work, and together with the previous work of disappearing cryptography, we actually show that by combining space constraints and time constraints on the adversary, we're able to achieve never before possible results. So that's one thing I would want to encourage you folks to think about is to think about what other new possibilities are there if we impose both time and space constraints on the adversary. Thank you for your time, and let me know if you have any questions. Thank you.