Hello, thank you for joining me. Today is part three of our walk along the River Mistborn. Yesterday I walked from Great Missingdon to Amersham. I went to Amersham this morning. I came along the footpath along the valley to here to Bottom House Farm Lane where I thought we'd start part three. So the main Amersham road, the A413 is just up there. Here's the River Mistborn. The footpath runs just along there and then there's Carries on across the road. So what I'm going to do this morning is walk all the way down the valley towards Chalfonson Charles and on to Chalfonson Peter. So let's go and discover more of the River Mistborn. So I've now just come about a mile from Bottom House Farm Lane. See what that yellow post is? Came out in the footpath along now. It's a very pleasant walk along the valley but it wasn't actually by the river. The river was always a field or so away. I will be carrying on down there to Chalfonson Charles Village Centre about a quarter of a mile away now from the Village Centre. What I'm going to show you is firstly this building here. This is the old mill. This is Mill Lane in Chalfonson Charles. So that way it takes you up to the main A413. That way it takes you to other parts of the village and come round here there is a thord which this car has just driven through the thord. And it's quite funny what happens here because as you can see there's a hump in the road but every time a car comes through it forces a load of water over the hump so then you get a bit of a river going down here and there's actually you can't really see a lot of it but there's another course of the river flowing directly under us here. All you can really see is a brick wall. There is water in it and you can see the water that gets pushed over the bit of the hump from cars goes down there and into the second course but let's go have a look at the thord preferably while there's no cars about because it's going to be a little bit challenging getting across because every time a car comes along this whole area effectively becomes the river but while there's no one about I can walk on this without getting my feet wet so I'm just going to have to wait here some runners coming over the bridge if a car comes now well they'll have to wait a minute so we're now going to go over the bridge this way it is a bit of a trying to sort of you've got to walk and not get your feet wet and exercised but here's the thord possibly as far as I'm well I think this is the only public thord on the river Mistborn there might be one or two on private roads and on farm tracks but I think this is the only one while as we go along I'll probably answer my own question so yeah then the river trickles off down there towards Chatham St Giles which as I said is about a quarter mile that way I'm now going to go back across the thord or across the bridge beside the thord rather and continue down the footpath towards Chatham St Giles Village Centre so I've walked along the footpath from Mill Lane and now we are coming to the village centre of Chatham St Giles this is probably one of Buckinghamshire's most attractive villages it really is a very beautiful little village and the river flows over there we're going to have a look at that in a minute but I'm just going to let you see the village centre now if you look here this view you see looking up there that is where they filmed the 1971 film Dad's Army so that was Warmington on Sea and this building here what is now a Costa Coffee was Captain Manorings Bank it was more recently it was a pub so I've been in there I've had a beer in there I've also had a coffee in there last year never withdraw money from there and I probably never will what I'm going to do now I'm going to head away from the river Mistborn because there's something else just up there I'd like to show you so I'm just walking up the hill now a little way from the village centre and this is what I wanted to show you here this little cottage this one on the end this is Milton's cottage this was the home of the poet John Milton you can go and visit it it's not open today but you go in you can have a look around hear about John Milton's life and you can also have a look around the quite attractive cottage garden so if you're in Charleston charge you can go for a nice walk in the Mistborn Valley and come visit Milton's cottage I'm going to go back that way now down to the village centre and we're going to reunite with the River Mistborn so I've come back down to Charleston Charles village green and just beside me here is the village pond which is connected to the River Mistborn so what we're going to do now is we're going to walk around the pond we'll rejoin the River Mistborn and we shall follow it all the way through to Charleston Peter and on to Denham so let you see one last view of the beautiful village green of Charleston Charles and just behind us here is River Mistborn so this is really quite a nice little area just outside the village centre where the river flows this all becomes meadows beyond here and it's like this kind of all the way to Charleston Peter really so I'm going to follow the river and we'll keep going well now it effectively it runs behind the village so you see the road there up that way goes up to where the A413 is so the A413 which has those trees up there there's it's not quite connected at the moment but see the pond and the river a couple of weeks ago when the river was higher the water was flowing right across so it shows over the last few weeks with the hot weather the river level has gone down and like I said in part one and two being a chalk stream it is a natural thing that the river levels well on most rivers the river level goes up and down but even more so with this one being a chalk stream and it can of course the river too dry up in the summer and it sometimes stays dried up all through the winter and you know on into the next year so but it's really nice to see it's flowing now we are still running parallel there's quite a lot of trees and bushes so I appreciate you can't see it we shout out just up here in a minute we will be behind the parish church so this section is quite nice look we come onto a boardwalk so when the flow is even is higher this area sometimes floods that's why they've put a boardwalk along here so um yeah that that always think a boardwalk makes the walk a bit more interesting so we're just going to carry on along here and uh you can see the parish church is well you will see it I promise where are we there we are there's the parish church of chaffinson gels that's another really pleasant church to visit so you know if you are here out for a walk I do suggest um you know go and visit the parish church have a look around the village it's all really worth seeing we come up to here we effectively go back onto a boardwalk again and um here's the river right here and then so you can see the river that's where we've just come along there's a footpath here which would take us beside the church yard that goes back towards the village center what I'm going to do now is I'm going to go back across the river this way and we're going to carry on along towards chaffinson peter so I'm going to follow this path up here in a moment there's a path that goes in that direction and that'll take me the next couple of miles on towards chaffinson peter so I'll show you more a little bit further up the river I've now left chaffinson gels behind me and I'm now going to follow the river through the fields towards chaffinson peter so here we have the river here now you can see it's back to really being a small stream again like it was up at Great Missingdon it seems between sort of Great Missingdon and Amisham it becomes a bit of a bigger river but now it's really gone back to being this small river and that's a rather interesting thing here and I don't really know much about it but if you look there's a ditch going off here which later on rejoins the river Missbore now it's it's got it's got a bit of water in it but not much a few weeks ago it was you know I wouldn't say it was full but it had more water in to me it looks like someone's built this man-made ditch there must be a pipe under here and I really don't know why because the natural course of the river meanders all around these fields but this seems to be a more straighter course straight up there in the long almost parallel to the road and as I should show you later on it does rejoin the main course if anyone knows why that other course was put in please do comment and tell me because you know as we've already discovered the river has been diverted it was diverted at Amisham and there's rumours that that's linked to why it sometimes dries up when they built the Amisham bypass they diverted if you look at the natural course see how it meanders all around these fields so what I'm going to keep doing now is I'm going to follow it all the way to Chalfont St Peter and well we're just going to keep going but I'm going to find a point where the ditch that they seem to have dug and the natural course reunites so I'm going to keep going that way to Chalfont St Peter I'll just come a little away from where we were a moment ago I just wanted to show you this this is a spring or was a spring a few weeks ago when our last came down here there was water flowing down here and into the river so it appears that perhaps as the water table has less water in the weather warms up there's less water to feed the mizborn now it as I've just said it really is the flow is a lot lower than it was the other side of Amisham so I'm wondering does the water effectively kind of just sort of seep into the ground or evaporate as we go along here whatever's happening there's less and less water as we go along which isn't sort of what most rivers do most rivers you know get bigger as they go along but it has always been like this from what I remember the mizborn as I said it rises and falls but it just does seem to be there's more water the other side of Amisham now we get to here there is another footpath along there and this seems to be a permissive path someone has made this rather unofficial looking bridge which is going to take us across there's quite a lot of water here that's because it opens out into quite a flat plane so yeah this is how it's either that or walk through the river and I haven't got wellies on today so oh it's about the old bridge can I do this on camera yes I can right there we go across it so this is the main path now from Charleston Jals Charleston Peter there is another path though that goes across there so my plan is to find that because we still need to find where the other man made course which runs along the length of those trees joins the main course so I'm going to carry on now in that direction and I'm now a bit closer to Charleston Peter well probably about half way actually at the moment between Charleston Peter and Charleston Jals I had to go back on myself to get across the whole river and the trench that I showed you had been dug well here is where the two joined so over there that's the main river and this is the trench there's a bit of water in it here but I'm not sure it is flowing out of there so obviously there's water coming along there but this is where the two reunite and then the river flows off up there interestingly over there there's another spring-like pond there's a few of these but that one appears to be not connected to the river at all but what I think all this this all becomes marshlands if um you know you've got prolonged periods of a lot of rain so whilst you can quite easily walk along there it's a bit squelchy under feet I think if you came here in the winter when there'd been a lot of rain it would be almost impossible unless you have wellies I'm now going to follow the path along here it crosses the river up there and we'll keep going till we get to Charleston Peter well we're now getting closer and closer towards Charleston Peter I was going along the main footpath which is just along there behind that hedge the A413 is over here there's this footpath that runs to A413 you can already see the beginning is the Charleston Peter now as for the river well something's happened look here we come to this bridge which when I was doing my Charleston Peter video we featured this bridge although I came from that end it's dried up now it wasn't then so what I'll do I'll insert a bit of footage from that video now so here we are in the Mistborn valley proper here's the river itself there's a rather um rickety old two-plank bridge over the river it's getting a bit muddy um but not enough to stop me from enjoying the walk so here we are here's the river Mistborn like I said we are in the future I'm going to do a video my intention is to walk all the way from Great Missingdon that way right down to Denham that way at some point in the future I've already done one on the free tributaries in Charleston Peter so have a look out for that video I'll put a link in now look at this bridge look how rickety it is not even sure if I should walk on that left flank it might break and then this one it's full of water um so yeah here it's all right to walk on um do I put my foot so I mean it's a bit bouncy but no it is safe so I'm going to carry on over to the style and along the river and the next part of the video we should be closer to the village centre again and as you can see it was flowing then so let's what we'll do we'll walk over the rickety bridge in this direction this time and then um I still want to carry on in that direction so just because I can and I'll walk through the river I'd rather be doing this with watering and wearing wellies so I'm going to walk through the river and um I'm going to carry on back up there towards the main path and soon we should be in Charleston Peter so now just come a little bit further along the path which runs between Charleston Peter and Charleston Charles now as we saw about there the river was dried up but if you look here thankfully it's short-lived because you can see pool of water down there and if you look just here through the hedge you can just see some water so there's springs here so those springs are beginning to fill the river again and it flows off in that direction the main dried up course is over there but this spring effectively has become a second source so we have a river that now flows on towards the river Colm it's the river though sort of from well from Great Missingdon through Amish and Charleston Charles it's weird how that just disappears I was going to try and find the spot where it actually disappears but I couldn't because it was private land between there and where it was dried up but the last point I could access it there was water but very low flow so it's strange really how it just sort of disappears into ground but like I said only a few weeks ago it was flowing all the way through and well with all this hot weather it's nice to have the hot weather but it does make me wonder if in a few weeks time more of the river could dry up but I'd like to think that isn't the case what I might do I'm not saying I definitely will but I could potentially do a follow-up video and we could see what if there is any progress if you look just there there you are we can see that tributary which flows off and up there joined to the main course I'm now going to continue on towards Chalms and Peter in the next one we shall be in Chalms and Peter itself well we've now reached Milmedo now if you think this looks familiar if you watch my videos where I explored all the plaques of Chalms and Peter then that's because we came to exactly this spot the reason I came here then was because I was showing you as a plaque just here now this one is relevant to the river Mistborn it tells you about a swimming pool that used to be here so you can see the plaque there and have a look at the Chalms and Peter video I'll show you tell you all about them in those videos but there was a swimming pool which was only had watering when the Mistborn was flowing and if we go over this bridge here this is the main course you can see we're back to a nice river you know with a lot of water in so the tributary we saw about there effectively saved the river and brought water back into the river and as far as I'm aware like I said it flows all the way through it's just a shame it can only be half a mile a quarter mile section where there isn't water in the river at the moment which is fairly good because I've known it be you know there not be water since this side of Chalms Front Park which we'll get to in the next video so it's great to see there is that much water in it but it just seems a bit of a shame there's that little bit with no water in it so that's Milmedo over there I'm going to continue this way and we'll have a look at the river in Chalms and Peter Village Center and that's where we shall end this one and in the next video we'll carry on towards through Chalms Front Park and on towards Denham so here we are we're almost at Chalms and Peter Village Center building over there that's the community center there's a rather interesting board just here now this so juicy walk you can do I've got a leaflet of those walks and they are really worth doing but the other thing it tells you I'm going to put an insert in now is about how and why the river does dry up part of the way along the section we looked at it's not fed from any springs so it just all seeps into the water it's relying on the strings further up but now we've come past that section and there's a few more springs and that's why we have water in the river through Chalms and Peter so I'm going to continue along this path along here you can see the river is just down there we've got the community center to us beside us over there there's the river so what my plan is now is to take you all the way into Chalms and Peter Village Center where the river quite literally disappears it doesn't dry up it disappears and you'll see more of which in a moment and in part four you'll be able to find out where it reappears so just going to keep going along this way there's a big park over there behind the community center that's where if you saw the earlier video I made the tributaries of the mizborn that flows that tributary flows along there that will actually see where it it joins so if you have a look at that video and you'll be able to see where those tributaries you know start and end so there's free in Chalms and Peter so before doing this I did a video on those three tributaries there's these pollarded willow trees along this section of the river there's quite an interesting bit coming up though that I particularly wanted to show you I'm just coming up towards the Greyhound pub now there's this bridge here there's also one of the plaques because there was a mill here once with a weir so have a look at that again if you watch the Chalms and Peter video you'll see that see this bridge here though this is fairly modern it's called the Vic-Wooten bridge and I'll show you there's a plaque about Vic-Wooten so he was someone who helped with the rescuing of the river mizborn when it seemed like it's going to be dried up forever but what I remember is the bridge before this one was a lot lower it must have been built because the flow was always so low and water used to flow over the top of it which I always used to find really amusing and I remember in a child I used to love paddling through it in my wellies now looking into the Greyhounds pub garden the river used to go straight along there when it flooded it went from dried up to flooded in about 2001 I think it was or 2002 there was literally water everywhere around here and they diverted to make it a straighter course and it hasn't flooded since but I remember when it did flood the whole or most of the village carpark was underwater it was really you know quite quite an interesting thing it wasn't very nice to the people whose houses were flooded but you just couldn't believe that it could go from one extreme being dried up to flooding and I think it might be something to do with when they later on were trying to rescue the river somehow ended up being too much water but it also helped the fact there was a lot of rain so effectively all or at least half the carpark was underwater it really was um very strange sight seeing as I said go from one extreme to another so this is the new course of the river the older course was just the other side of that grass and then came around here and joined now I said about the tributary of the river misborn which is culverted under the carpark in the other video where you can just see the water coming out below that tree and joining the main course and we're now heading into the village centre through the weeping willows into the village centre got the parish church just behind those trees there so there's the parish church so do have a look at my chervils and peter series you'll be able to hear a lot more about the village in that now when I said the river disappears this is what I mean it's culverted under st peter's court the 1960s shopping development now if you want to know where that culvert ends you'll have to watch the next video and in that video we're going to go finish through chalfant st peter and into chalfant park and up to the chilton mainline so thank you very much for watching please do feel free to like subscribe comment tell your friends about this area and about henry's adventures thanks very much for watching and goodbye


Live from Atlanta, Georgia, it's theCUBE, covering AnsibleFest 2019, brought to you by Red Hat. Welcome back, this is theCUBE's live coverage of AnsibleFest 2019 here in Atlanta, Georgia. I'm Stu Miniman, my co-host is John Furrier, and we're going to dig in and talk a bit about developers, our guest on the program, Prague Dave, who is a senior principal product manager with Red Hat. Thank you so much for joining us. Glad to be here, thanks for having me. All right, so configuration management, really maturing into an entire automation journey for customers today, let's get into it. Tell us a little bit about your role and what brings you to the event. Yeah, so I actually have a very deep background in automation, I started by doing workload automation, which is basically about how to help businesses do their processing. So, right from processing and invoice, how do I create the flows, right, to do that. And we saw the same thing, like automation was just kind of like an operational thing and was brought on just to fulfill the business, make it faster.  I mean, it was amazing and we saw the growth and people saw the value, people saw how easy it was to use. Now I think that combination is kicking in. So now I'm focusing more on developers and the DevTools BU at Red Hat and it's the same thing.  So we've been talking about this for decades. Talk to us a little bit about how it's different today and you know, you talked about some of the roles that are involved here. You know, how does Ansible end up being a developer tool? Yeah, you know, it's very interesting because Ansible was never really targeted for developers, right? And in fact, automation was always considered like an operational thing. Now what has happened is the entire landscape of IT in a company is available to be executed programmatically. Before it was interfaces were only available for a few programs. Everything else you had to kind of write your own programs to do. And now with the advent of APIs, with really rich CLIs, it's very easy to interact with anything. And not just like in software, you can interact with your network devices, with your infrastructure, with your storage devices. So all of a sudden when everything became available, developers who were trying to run, create applications and needed environments to test, to integrate saw that automation is a great way to create something that can now be replicated and be consistent every time you run it. So the need for consistency and replication drove developers to adopt tools like Ansible.  And then we see that, wow, they are really pulling it down. It's great. The whole infrastructure as code, which is one of the key pillars for DevOps, has become one of the key drivers for it. Because now what you're seeing is the ability for developers to say that I can now, when I'm done with my coding, and my application is ready for, say, a test environment or a staging environment, I can now provision everything I need, right from configuring my network devices, getting the infrastructure ready for it. We'd run my test, bring it down, and I can do all of that through code, right? So that really drives the adoption. And the cloud scale has shown customers at scale, whether it's on-premises or cloud or edge, is really going to be a big factor in their architecture. The other thing that's interesting, and Stu and I were talking about this in our opening yesterday, is that you have the networking and the bottom of the stack moving up the stack, and you have the applications kind of wanting to move down the stack. So they're kind of meeting in the middle on this programmability in between them. You know, containers, Kubernetes, microservices, is developing as a nice middle layer between those two worlds. So the networks have to telegraph up data, and also be programmable. This is causing a lot of disruption and innovation. Your thoughts on this is, because now it's NetSecOps, means DevOps, that's DevOps, this is now all that's coming together. Exactly, and what's happening is what we are seeing with developers is that there's a lot more empowerment going on. You know, before, there was a lot of silos, there was a lot of checks and balances in place that kind of made it hard to do things. It was like, okay, this is what you, developers, you write code. We will worry about all this. And now this whole blending that has happened, and developers have been empowered to do it. And now you throw that, okay, the empowerment is great, and with great power comes great responsibility. So can you please make sure that what you're using is enterprise-grade, and it's like, you're not just doing things which will break my environment. So once everybody becomes comfortable, that yes, by merging these things together, we're actually not breaking things. We're actually increasing speed, because what's the number one driver right now for organizations? Is speed with security, right? Can I achieve that business agility so that by the time I need a feature developed, by the time I need a feature delivered in production, and my thought comes for it, I need to close that gap. I cannot have a long gap between that. So we are seeing a lot of that happening. People love automation, they love AI. These are two areas that, it's a no brain. When you talk automation, you talk AI, get it, bring it on, right? Yes, absolutely. What does that mean? So when you think about automation and the infrastructure, that's in the hands of the operators, but also they want to enable applications to do it themselves as well, hence the DevOps. Where is the automation focused? Because that's the number one question. How do I get land, get the adoption, and then expand out across? This seems to be the form of the Ansible's kind of cracked the code on. The organic growth has been there, but now as a large enterprise comes in, I got to get the developers using it, and it's got to be operator friendly. This seems to be the key. The balance has to be there, the kingdom. Yep, no, you're absolutely right. And so when we look at it, what do developers want? So something that's just frictionless to use, very quick, very easy. And so that I don't have to spend a lot of time learning it and doing it. And so we saw that with Ansible. The fact that it's so easy to use, most of everything is in YAML, which is very native to developers. So we see that from the dev perspective, they're very eager now, and they've been adopting it. If you look at the download stats, it tells you there's a lot of volume happening in terms of developers adopting it. What companies are now noticing is that, wait, that's great, but now you have a lot of developers doing their own thing. So there is no way of bringing all this together. So it's like, if I have 20 teams in one line of business and each team tries to do things their own way, what I'm going to end up with is a lot of repeatable, like a lot of work that gets repeated, that gets duplicated. So we see that stuff that we're seeing with collections, for example, what Ansible's trying to bring to the table is like, hey, how do I help you kind of bring things into one umbrella? And how can I help you as a developer decide that, wow, I got like 100 plus engine X roles I can use in Ansible? Well, which one do I pick? And you pick one, somebody else picks something else, somebody creates a playbook with like one separate, you know, one different thing in it versus yours. How do we get our hands around it? And I think that's where we are seeing that. Right, open source standpoint, obviously Red Hat, Ansible doing great stuff. And for the folks in the Ivory Tower, the executives CXOs, they hear Ansible glue layer, integration layer, and they go, wait a minute, isn't that Kubernetes? Isn't Kubernetes supposed to provide all this stuff? Be that. So talk about where Ansible fits in the wave that's coming with Kubernetes. Kubernetes. That Gelsinger at VMware thinks Kubernetes is going to be the dial tone. It's going to be like the TCP IP like protocol is use his words. But there's a relationship that Ansible has with those microservices that are coming. Could you explain that fit? No, you know, you hit the nail on the head that Kubernetes is like, we calling the new operating system. It's like, that's what everything runs on now, right? And it's very easy for us, you know, from a development perspective to say, great, I have my containers, I have my applications built. I can bring them up on demand. I don't have to worry about, you know, having the whole stack of an operating system delivered every time. So Kubernetes has become like the de facto standard upon which things run. So one of the concepts that has really caught a lot of momentum is the operator framework, right? And which was introduced, you know, with the Kubernetes, the later release of 3.x. So what we saw that with an operator framework, it's very easy now for application teams. And we saw a great uptake from software vendors themselves of how do I give you my product that you can very easily deploy in Kubernetes as a container. But I'll give you enough configuration options so you can make it work the way you want to. So we saw a lot of software vendors creating and delivering their products as operators. Now we are seeing that a lot of software application developers themselves, for their own applications want to create operators. It's a very easy way of actually getting your application deployed onto Kubernetes. So Ansible operator is one of the easiest ways of creating an operator. Now there are other options. You can do a Golang operator, you can do Helm. But Ansible operators has become an extremely easy way to get going. It doesn't require any additional tools on top of it. It just requires the operator SDK. It's, you know, you're going to use Playbooks, which you were used to already. And you're going to use Playbooks to execute your application workflows. So we feel that developers are really going to use Ansible operators as a way to create their own operators, get it out there. And this is true for any Kubernetes world. So there's nothing different about, you know, an Ansible operator versus any other operator. No change to Kubernetes, but Kubernetes obviously has the concept of microservices, which is literally non-user intervention. The app's taking care of all the provisioning of services. This is an automation requirement. This feeds into the automation theme. Yes, exactly. And what this does for you is, it helps you, like if you look at operator framework, it goes all the way from basic deployment, which everybody's used to. Like, okay, I want instantaneous deployment, automatically just does it. Automatically recognize changes that I give you in my configuration and go redeploy a new instance the way it should. So how do I automate that? Like how do I ensure that my operator, that is actually running my application, can set up his own private environment in Kubernetes and then he can actually do it automatically when I say, okay, now go make one change to it. Ansible operator allows you to do that. And it goes all the way into the life cycle, the full five phases of life cycle that we have in operator framework, which is all the last ones about autopilot. So auto scale, auto remedy itself. Your application now on Kubernetes through Ansible can do all that. And you don't have to worry about quoting it all. It's all provided to you because of the Ansible operator. Progg, in the demo this morning, I think the audience really resonated with the audience that they talked about some of the roles and how they worked together. And it was kind of, okay, the developers on his side and the developer's expectation is, the infrastructure's not going to be ready. I'm not going to have I need. Leave me alone. I'm going to play my video games until I can actually do my work. And then, okay, I'll get it done and do my magic. Speak a little bit to how Ansible is helping to, break through those silos and having developers be able to fully collaborate and communicate with all their other team members, not just be off on their own. No, yeah, that's a good point. And what is happening is that with developers, like with what Ansible is bringing to the table is giving you a very prescriptive set of rules that you can actually incorporate into your developer flows. So what developers are now doing is that, I can't create an infrastructure configuration without habitually having discussions with the infrastructure folks. And the network team will have to share with me what is the ideal configuration I should be using. So the empowerment that Ansible brings to the table is enable cross-team communications to happen so that there is a prescriptive way of doing things and you can create this automated into an automation and then just set it up so that it gets triggered every time a developer makes a change to it. So internally, they do that. Now other teams come and say, hey, how are you doing this, right? And so, because they need the same thing.  But in the end, the mechanism is the same because you are under the same enterprise, right? So you're going to have the same layer of network tools, same infrastructure tools. So then teams start talking to each other. I was talking with a customer and they were telling me that they started with four teams working independently, building their own Ansible playbooks and then talking to the admins. And next thing they know, everybody had the full automation done and nobody knew about it. And now they're finding out and they were saying, wow, I got like hundreds of these teams doing this. So I am, A, I'm very happy, but B, now I would like these guys to talk to each other more and come up with the standard way of doing it. I'm going back to the collections concept, right? That's what's really going to help them. And we feel that with the collections, it's very similar to what we did with operator hub for the OpenShift. It's where we have a certified set of collections so that they're supported by Red Hat. We have partners who contribute theirs and then they're supported by them but we become a single source. So as an enterprise, you kind of have this way of saying, okay, now I can feel confident about what I'm going to let you deploy in my environment and everybody's going to follow the same script. And so now I can open up the flood gates in my entire organization and go for it. Yeah, what about how are people in the community getting to learn from everyone else? When you talk about a platform, it should be if I do something, not only can my organization learn from it, but potentially others can learn from it. That's kind of the value proposition of SaaS. Yes, yes, it is. And having the Galaxy offering out there where we see so many users contributing, we have across a hundred thousand rules out there now. And that really brought the Ansible community together is, it was already a strong community of contributors and everything. But by giving them a platform where they can now have these discussions, where they can see what everybody else is doing, it's the story is where you will now see a lot more happening. Like today, I think it was Ansible is like the top five GitHub projects in terms of pull requests that are happening out there. I mean, the community is so vibrant, it's incredible, like they're driving this change. And it's a community made up of developers, a lot of them. That's what's creating this amazing synergy between all the different organizations. So we feel that Ansible is actually bringing a lot of this together, especially as more and more automation becomes prevalent in the organizations. All right, Parag, I want to give you a final word, Ansible Vest 2019 final takeaways. No, this is great. This is my first one, and I've never been to one before. And this is the energy and just seeing what all the other partners are also sharing, it's incredible. And like I said, like with my backgrounds, automations, all of this, anything automation for me, it's, I think that's also a way to go. All right, well, Parag, thank you so much for sharing the developer angle with us. Thank you very much. For John Furrier, I'm Stu Miniman. Back to wrap up from the cubes coverage of Ansible Vest 2019. Thanks for watching theCUBE.


So okay, let's continue with USB over STM32 family So now you've got I think a good overview of what we've got as a USB Let's see in all our family what is covered So USB full speed a variable on all STM32 families. That means what we call families for us is a family L for loop-a-words we've got the mainstream with the the series F and then you've got some mainstream and High-performance one with the most powerful one. So It's in all our family. We've got so USB full speed, but not on all device We've got some device without a USB anymore. So you have to to check what you want to do Crystal is less implementation I think we insist a lot of these capabilities on some parts we will see after more details about it So the capabilities I would say to have a device without an external Oscillators I did in your design Then the fact that you've got internet pull-up on the plus line It's not on all them. You've got some who you need to add yourself this pull-up So we both also address this during the hardware design this morning I speed support on the high-performance family and it requires an external fee except on one On one family with a f7 is three which embedded and I speed fee So it could be interesting. We want these features. We've got one part who support it Here are some apps. So with a different family general purpose one the high-performance and the loop-a-words Here you can see what are the capability from the crystal less So we can see that high-performance will address all the OTG for sure host and the high-speed interface and with the usage of an external fee I Will say this some up situation today, but you need to be updated as soon as we've got a new part So don't take it as I will say a Bible You still need to check when we will see a new reference. What is available on it? So for the device only peripheral so on the holder families on the Little package so maximum of eight billion bid directional on point included on point zero So it's a limitation if you were remembered in our theory of USB. We say we can go up to 16 But here we are limited by our way to eight bid directional Support only of a full speed for this device and in the device only peripheral I mean not the OTG one you don't have the five for you have got a dedicated sram And we this sram could be shared with a can device if it's present on the parts So you have to take care about this when you select a product If you want to do can and USB at the same time you have to share the memory and we will see after more details Link with a program management and the battery charging detection support on some device also So here is a sum up so here you've got the size of the buffer available And if it's share or not with the car and you can see that sometime if you are using usb You can choose can at the same time So we just to warn you about this when you select a product and if you want to use can and usb Please check before For the OTG peripheral here. We've got a dedicated DMA controller So I think you remember who both present you the difference yesterday on the fact that you have access to the buses So you can drive a DMA OTG internal pull down for the full speed so no need to add external and it's needed to switch from us to from From full speed to high speed Dedicated 5-4. I think we already cover it yesterday So here is the sum up of all I will say the capabilities for the different family so it could be limited to eight on point and This 5-4 size which is 154 case and if you go in the I would say high performance one in the High-speed you can go to 4k for the 5-4 and the number of on point is 16 On your slide version. There is a mistake there. It was right 18, but it's need to be updated It was 16 just a typo error. Sorry for that so You have to notice that some h7 you can have two OTG high speed so there is two high OTG high speed, but there are The same property properties so but only one could be high speed if one is high speed the other one could High speed and high speed Yeah So that's just to give you an overview of the different capability we see together. I think it's That's all for this pot Any question on these parts? I Would say just information for you after you really have to check when you want to select and don't hesitate to use The finders to find the chip or to to see what you need to address. I Think we switch to another hands-on with low Bosch


I'd like to invite to the stage Kiara Brookman, a new College of Engineering and Computer Science. And the title of Kiara's talk tonight is How to Build a Brain.  Every single one is full of complex micro systems all working together to keep you going. They're more intricate in advance than any machines we can make. But sometimes they need a little help to get going. And that's where I come in. After a stroke, patients are left with chunks of damaged brain tissue. Now, instead of trying to rebuild the incredibly complex human brain from scratch, I'd much rather give cells the support and encouragement they need to rebuild it themselves. My research goal is to rebuild damaged brain tissue. But in truth, stem cells will be doing all the actual building. I'm just making biomaterials that tell them how to build a brain. First, they need some structural support or scaffolding. In healthy tissue, cells exist in a fluid environment called the extracellular matrix. This matrix is full of useful proteins and also offers structural support in the form of nanofibrous proteins. Different tissues have different needs, so every matrix is unique. And I've been making materials that mimic the nanofibers in matrix specific to healthy brain tissue. To do this, I take small pieces of proteins and attach them to stacking molecules so they form into nanofibers that not only offer structural support, but also trick the cells into thinking they're surrounded by brain proteins.  Next, I need to direct the building activities. We have signaling molecules we can use to give cells instructions and tell them what to do, but they're unstable. They only last minutes to hours inside living tissue. Repeated injections into your brain would be very damaging, so I need a way to safely store these signals and release them gradually over time. My material actually sticks to the signals, holding them safely in place until they detach from the nanofibers over time. And I've shown that putting these signals into my material increases their lifespan from hours to weeks. Finally, I need to make sure that everything happens at the right time. Building a brain is even more complicated than putting together IKEA furniture. So it really is important to start at step one and do everything in the right order. For the cells, this means I need to control the timing of when different signals are delivered. To do this, I've attached long molecular chains to some of the signals to delay their release. Those chains stick to my material, holding those signals in place even longer. And then when they do detach, that extra bulkiness makes them slower to reach the cells. So far, I've achieved a nine-hour delay and I'm looking at longer chains for longer delays. When I'm finished, I'll have a single material to guide stem cells through the entire process of building new brain tissue. And we can get those damaged brains back up and running.


Sunday afternoon a couple of reasonably large earthquakes jolted and rolled their way through Christchurch reminding us all that earthquakes aren't going away they occur all the time all over the world and that they can be quite scaring. Like many things in nature there's a silver lining. Actually earthquakes are a very useful tool for scientists to learn about the internal structure of the earth. If you've ever wondered how we could possibly know that some 3,000 kilometers beneath our feet is a layer of liquid molten iron it was actually earthquakes detected all around the world that we could discover this. So I like to make little earthquakes in the lab to work out the internal properties of a whole range of different materials from ice and wood and rocks to fruit. You've actually already heard of this before in medical imaging we call it an ultrasound scan and when you go for an ultrasound the doctor has little wand that emits waves into the body kind of like earthquakes except here instead of seeing a core of liquid molten iron maybe we can see a unborn baby. The goal of my research is to use quakes to measure the internal properties of materials without ever coming into contact with the sample and I can do it using lasers. So instead of having a contacting wand like a doctor I can use high energy pulses of light which I focus onto the surface of my sample. When all that energy from the light pulses absorbed by the material the rapid increase in temperature generates a shockwave just like an earthquake. This shockwave propagates through the material to where I detect it using a laser detector that I designed. One of the most successful applications that I've been applying this technique to is measuring the firmness or ripeness of apples. An apple is kind of like a little earth it has a core it has a crust it's kind of round and I can use laser generated apple quakes to measure the ripeness of an apple. I do this by comparing the waves that travel around the surface of the apple those are called Rayleigh waves they're the ones that knock your buildings over in the earth to the waves that travel directly through the apple flesh. So you can imagine that I can measure the ripeness of an apple completely non-contacting so I could measure every single apple coming off an orchard. So one day in the future you may see in your local supermarket and bright lights laser-certified apples. $50 a kilo.


I came to Berkeley in the late seventies and I was planning to be a national physicist. I was very inspired by Carl Sagan, Albert Einstein, and Stephen Hawking. And I knew Berkeley would be a great place to be, but I've stayed for more than 30 years because of Art Rosenfeld. I'm going to tell you a little about Art Rosenfeld. Art passed away this year just a couple of months ago and he left behind a tremendous legacy that gives us the first generation of the energy efficiency agenda in the building sector. And this is very important for our country, our state, and around the world because buildings use more energy use than any sector and more greenhouse gases. So we care not just about how we produce energy, but how we consume it. Art was known for great achievements in energy efficiency in windows and in lighting systems and in things like refrigerators. And what's happening now is we're changing dramatically. As we talk about how we both produce and consume energy, it's no longer just about static energy efficiency, but dynamic energy management. So as we move away from a time where we had more and more power plants to supply the energy for growing loads, we now have distributed systems and we have intermittent variable supply. So we're producing and supplying our energy with renewable systems. California had a great achievement just a couple months ago this year where over 50% of the electricity on a single day for three hours was from solar. Now that's a great achievement and we should be celebrating that. But one of our challenges is what that means when we have created something that is now famous around the world called the duck curve. As we have more and more solar in the middle of the day, we actually have less load in some times of the year. So we have too much solar. That's already happening in Hawaii and as we think about clean energy systems, we have to think about both how we produce and consume our energy. The belly of the duck means that there's a lot of electricity available and it's becoming cheaper in the middle of the day. For decades we've been concerned about time of use and we try to use less in the middle of the day and more at night. But we're actually now very interested in using more during certain times of the day. It's very different than what we've been doing. So the challenge and the solution is related to what we do in buildings. Buildings can have flexible consumption or flexible loads and those prices in the middle of the day in the spring when there's a lot of solar is something that can be sent to a device in your home. So the most important thing to remember is that the way we use energy today is going to change dramatically. So we are going to be able to understand what is using energy on home, how much and when. It's when you use it that matters. The technologies in this picture show you water heaters, refrigerators, dishwashers, air conditioners and maybe local storage and photovoltaic. We're developing the technology here in Berkeley to control those loads, to see the loads. We don't see them today.  So you actually use less around dinnertime when that duck curve was peaking. So that the total load minus the solar in the wind is that curve and we really want to fill that duck belly. So we want low carbon buildings, part of a low carbon grid, and we're going to be using our energy very differently. So these technologies are going to be communicating with the grid. Today, those technologies are doing their own thing and we turn them on when we want and we turn off when we want. But in the future, we want an integrated system that's automated and we want people to be able to guarantee the energy performance of those systems. So we're really excited about the activities across the Berkeley campus and at Lawrence Berkeley National Lab working across this multidisciplinary area. So it's a critical part of achieving a future vision of a low carbon future involving not just producing the energy but consuming the energy, energy efficiency and dynamic load control. And these are the technologies that you'll be seeing in the future. Thank you.


Welcome to the Highline College City C-Link video series. This video explains how to attest that you have received the COVID-19 vaccination or begin the process of asking for a medical or religious exception. First, open a browser and go to City C-Link by typing in gateway.cityclink.us. Enter your City C-Link ID and click Next. Then enter your password and click Verify. If you receive a message that says you need to set up additional security, you can find help for that in Highline's City C-Link web page. Once you're logged into City C-Link, click on the student page. At the bottom of the page, and you might have to scroll down, you'll see the immunization attestation tile. Click on that. Under the immunization, click the dropdown and select the vaccine or exception type. For two dose vaccines, such as Pfizer or Moderna, select the option labeled first dose. Note that if you select an exemption, the college will follow up for more information. For the purpose of this video, I'm going to pretend that I got the Moderna vaccine, so I'll select Moderna first dose. Next, click the calendar and select the date that you received the first dose of your vaccine. I'm going to select September 1st. You should enter the date that you received your vaccine, and that shows on your vaccine card. If you have a two-dose vaccine, click on the plus sign to the right of the date. Select the second dose of that vaccine and also enter the date for that. I'm going to enter October 1st. You should put the date that's on your vaccine card. If you have not received the second dose yet, finish this form. Then return to the second dose once it's happened. In the self-attestation section, click I agree to state that you have read and agree with the statement above. This means the information you provided is true. In the disciplinary action section, click I agree to state that you have read and agree with the statement. This means that if you did not provide true information, you might have consequences. Once you have filled out the form and agreed to the statements, click the Submit button. You'll see a circle appear in the middle of the screen very briefly, indicating that your information is being sent to City Slink. Your information will be saved, but you will still see this page. Click on the home icon in the top right corner of the screen to return to your City Slink student home page. Congratulations! You have successfully submitted your attestation for your COVID-19 vaccination.


Although Hibbley Days 2024 isn't here yet, vendors can apply for a spot in downtown Pikeville to join the celebration. Handmade crafters, food stands, and other types of vendors can apply through the Southeast Kentucky Chamber of Commerce's website at secchamber.com slash Hibbley Days. The Chamber will also provide assistance for vendors once they apply. So the Southeast Kentucky Chamber handles all of the vendor applications that includes the street and the parking garage. So you can find that application at secchamber.com slash Hibbley Days and it has a full list of frequently asked questions and the application process is completely online. And once that application is filled out, then we review the information. If we have questions, we'll call the vendors. If not, they'll receive an application to an invoice to the email that they provided us. Appalachian Community Care offers outpatient medication assisted treatment for addiction, counseling, and behavioral play therapy for children, accepting Medicare and all major insurance. Recovery is hard, regret is harder. Appalachian Community Care, Pikeville, Whitesburg,<PHONE_NUMBER>. Find them on Facebook. For those who want a spot in the parade, applications are open for that too. Go to either hibbleydays.com or visit pikeville.com to register. The Hibbley Parade is such a great tradition. It's been going on for almost 50 years now and it's the highlight of the entire Hibbley Days Festival. You've got Hibbley Jalapies. You've got people in costumes. You've got local celebrities. You've got just mom and dad that want to take their kid through the parade. We can do that and we've tried to make it as easy as possible for you. We've created an online form. You can go to hibbleydays.com or you can go to visit pikeville.com. Click on parade registration and be able to apply right there.  Reporting for Mountain Top News, I'm Nick Colum.


The brown-dark city entered the territory on West. There's just one way to handle the killers in the spoilers. And that's with the U.S. Marshal and the smell of gun smoke. Gun smoke, starring William Conrad. The story of the violence that moved West with young America. The story of a man who moved with it. Matt Dillon, United States Marshal. Good morning, Mr. Barney. Oh, oh, Marshal. Good morning, Mr. Dillon. Good morning, Sam. Is, uh, kitty around? Oh, don't know she's up yet, but if she is, she ought to be down soon. I'll wait. Nippy this morning. Oh, feels good. It's a nice time of year, huh? Ah, I don't know. I kind of like spring myself.  Oh, oh, yeah. Thanks. Uh, can I get you something? Beer, maybe? Got any coffee? Sure, just made up of it. Oh, that'll be fine. That's pretty, man. You got a pretty boy. Oh, good enough for calling the hogs, I guess. You just get up? Well, go. Why? Oh, it distracts me. I haven't seen you close to early like this. No, no, you look fine.  You better quit by your head. Yeah, I guess. Where's Sam? Oh, he's bringing in coffee. Oh, Sam, come for me, please. Sure, Miss Kitty. What's occasion, Matt? Uh, Kitty, there's a party tomorrow night, a dance. It's a benefit for the new school down at the hall, you know?  It happens at dances. Go on. Well, uh, when I'm trying to, where do you go with me? I'd kind of like to, Matt, but no thanks. Well, I got to work here, you know that. Besides, well, you ought to be able to get off. Well, even if I could, ladies might not take kindly to it, Matt. Not rightly polite society. What do you care about? Well, thanks anyway, Matt. Ah, that smells wonderful. Sammy, I think I'll marry you. Me? Shoxy. Me? Oh, shox. But listen, Kitty, about the dance, I've already bought the tickets. You're sweet, Matt. And I thank you kindly for thinking of me. But you better ask someone else. Well, it isn't a kid.  Hmm? Oh, sure, Mr. Dillon. Sure. Now look, Kitty, I'm asking you to go with me. Well, it's important to me that you go. Are you making love to me, Matt? This hour in the morning? No, no, I mean it. I want you to go to the dance. You want to be embarrassed. You want everyone to stare at us. You know what they'll say? My, my, the Marshall really should have better sense than to bring that woman here. It ain't decent. It ain't proper. Well, it's true. I'm a hostess at the Texas Trail, a saloon. You know what they think about me? Well, will you go, Kitty? No. I'll call by for you at 7. Well, drink a bottle of whiskey and clout some old bitty on the head. Then you'll be sorry. Oh, Kitty. I haven't got anything to wear, Matt. I can't wear my working clothes.  Just fine, just like you are. Marshall. Yeah. I shouldn't, but I guess I'll go to the dance with you. I'll be ready at 7. How do you talk about a woman like Kitty? The color of her hair, eyes, the shape of her leg, the way she spoke, thought. Well, that's a picture you had to get by looking and hearing. Otherwise, you'd never know it. And I felt real good about taking Kitty to the party the first time we'd really be out in company. And I liked the idea. Good morning, Mr. Dillon. Good morning, Chester. Nice day. What is that? That, Mr. Dillon? Yeah, all over my desk, that ink. Yes, sir, I know. I was just cleaning it up, Mr. Dillon. Seems like a big blue bottle fly. Last of his kind this fall, I guess. Big and full blue bottle fly was a setting on your desk, Mr. Dillon.  Yes, sir, I see it.  And I took a flack out of him with a paper I happened to have in my hand, and I got him. Well, thanks a lot. Well, that's all right, Mr. Dillon. If there's anything in this world I hate, it's a big, maggoty blue bottle fly. Yeah, yeah, yeah, I know, Chester. The mail coming in. Yes, a couple of minutes ago, it's right over there. Oh, OK. There, I think that should do it, Mr. Dillon. All right, Chester. Anything likely in the mail, Mr. Dillon? No, no. Look, Chester, we better get these government circulars posted there. Would you know that for me? Yes, sir, I'll do that. Say, Mr. Dillon? Yeah, what is it, Chester? About the dance tomorrow. Now, what about it? Well, you're going, aren't you, sir? Doc's going. He's taking Ms. Mcnish. I'm going. Everybody's going.  Yeah, I'm going. Don't seem right, man.  You are? Yes. Well, that's fine. Just fine. Doc and me, we were talking, and it just didn't seem right to us that a man like you didn't have no real nice, sweet girl to escort to a big social. I got one, Chester, a real nice, sweet girl. I'm taking Kitty. Ms. Kitty? I asked her before I came to honor that she accepted. Well, that's good, Ms. Kitty. That's right, Chester. I got a couple of letters off to Washington. Chester, you want to go and see about posting those circulars, huh? Yes, Mr. Dillon. Ah, fine. Mr. Dillon? Oh, what is it, Chester? Well, Mr. Dillon, it ain't none of my business, and I did not have no right to say it. Say what? Well, sir, I, I, yeah. I was wondering if I might borrow one of them fancy ties off you for the party? That's not your business. That's what you haven't got any right to say. Yes, you know, that's right.  But you can borrow a tie. I think you're kind of what you're doing. You work for a long time with a man, and you share a lot of life and a lot of death.  Well, that's the way it is with Chester and with me. Now, he had something on his mind, and I figured after a while, he'd get it off. Well, the morning went, and it was almost known when Chester came back. Going to go have some dinner, Mr. Dillon? Yeah, I think I will. How about you? Hungry, the raggle bone possum. Did you get the posters up? Yes, sir. Well, OK, let's go. Mr. Dillon? Yeah.  There's talk. All right, Chester, come on, get it out. It's all over town. About you taking Miss Kitty to the dance tomorrow night. What do you mean, all over town? I only asked her this morning. Yes, sir, I know. Best I can figure, Sam, over at the Texas Trail must herd you and let it slip. There's been a mighty fierce mess of gum clobbering up and down. All over. Thanks for telling me, Chester. It ain't none of my business. Yeah, I know, you said that before. Yes, sir. I surely did. Well, let's go get something to eat. It's hard to tell about people. Maybe it's hard to tell about yourself because you come under that same heading, people. When they're mean and small, there's not an animal to touch them. Chester and I walked down the street, and it didn't take long to hear and see what was going on. Some of the drifters leaning against the wall on the corner came right out with it. Morning, Marshal. To understand, there's a gallant times got herself a new boat. What did you say? Maybe you ought to look into it, Marshal. Folks are being downright rude. Mr, you're going to ought to haul them in, every one. Yeah. What are you going to charge them with? Pestilence, Mr. Dillon, just plain pestilence. I knew better what Kitty had meant about the ladies of the town when a couple came out of Olivet's dry good store. It didn't see me until it was too late. Plain to the dance committee. It's indecent, that's what it is, why she's common. Nothing but a common, saloon woman. What's this city common to when a United States Marshal? Morning, Miss Sprinkle. Uh. When a man's born, they say he's blessed or cursed with a lot of things already in him. Take pride, for instance. Sometimes pride can be a curse. Now, maybe I had more in my share. Maybe it would have been a sight kinder if I'd not taken Kitty to the dance. But I did. We will return for the second act of gun smoke in just a moment. First, this hint for weekend driving. Whatever you do, be moderate. Be obedient to all traffic laws. Be careful. Use your head, and don't take chances. Now, for the second act of gun smoke. I picked up Kitty at the Texas Trail at 7 the next evening. She was waiting by the side door. And when I saw her, she kind of moved back in the shadows almost as though she was ashamed for me to see her. Hi. Hello, ma'am. Are you all set? All right, yes, ma'am. Matt, are you sure? Hey, Kitty, you look fine. You look just fine. Do you like it? Yeah. Yeah, I like it. We walked along the street down to the hall, and I kept looking at her like I say. You had to know this, Kitty, to understand what I mean. And even then, you get a surprise. She was like a 17-year-old on her first date. And she was like all the women you'd ever known and loved, soft and innocent. And something else, something that's female, and you can't figure out what.   And just before we went in, I looked at her again. And I didn't care. I was proud she was with me. Evening, Marshal Dillon. Evening, Ms. Murphin. You know Ms. Russell? I do. You have your tickets, Marshal Dillon? Oh, yeah, yeah. Here we are. Fine. Go right in, won't you? Oh, sure. Oh, excuse me, Mrs. Murphin. Is there somewhere I can put my coke? Oh, yes, yes, of course. The lady's reception room is right from there. I didn't catch the name. Catherine Russell, ma'am. Excuse me, ma'am. Yeah, sure. I'll wait for you. Thanks. You're better. I could see them through the big open doors in the hall. They were all there. Faces flushed, smiling, happy, dancing. All the women seemed pretty and the men handsome. And Chester was up on the platform calling the dance, and Doc was fiddling. And I was waiting for my dancing partner, Ms. Kitty Russell. How to skirmish with one of the gentile females in there? Oh, I'm sorry. Marshal, is she? You know, I get the idea, and I'm not welcome around here. Let's go in and get some punch, huh? Sure. How are you, John? Oh, that's a nice dress, Kitty. I haven't worn it since a few years back in New Orleans. Hey, Marshal! Oh, Ms. Kitty! Let's talk. Hey, hi! Oh, Doc. I say, we got a bottle of whiskey outside. You care to join it? Oh, this punch. Eww, boo. Oh, not right now. Thank you, Doc. Oh! Hey, Ms. Kitty. I saw you come in. Best-looking woman in here. Yeah! Oh, there's lots of scratchin' goin' on. Thank you, Doc. If you see Mrs. Magnish, don't tell her where I am, will you? Man gets kinda dry, Fiddlin'. Oh, I haven't been so long. So long, Doc. Hi, Marshal Goodman. Uh, Kitty? I guess so. Uh, Mr. Sprinkle, have you met Ms. Catherine Russell? No, no, I'm afraid I haven't. You got a short memory, Mr. Sprinkle. Huh? I could have saw her with you in the Texas trail a couple of weeks back. Drunk in a hoot-owl.  I think... Edward? I... Edward? Yes, dear? You let somebody else take care of the punch. I want you to come with me. Oh, well, I mean, I promised. I'm on the committee, even, Ms. Sprinkle. I have no wish to speak to you, Marshal Dillon, or this woman you've brought with you. I will not have my husband servein' such people.  How dare you say that? Well, aren't you? I suggest that you leave, Marshal. You're not wanted here. Not with that woman you've seen fit to bring. Come on, Matt, I want to go. No. This is a public dance, Ms. Sprinkle. Right now, you're trying to make it private. If you can't behave like a lady, I'll thank you to leave this lady's presence. See, here, Marshal, you can't talk like that to my wife. Hey, Kitty! What do you say, Kitty? Matt, please. I want to go. We're not going anywhere. We're stayin'. How about some music? All right now, folks. It'll be a wall this time. Thanks for the punch, Mr. Sprinkle. Come on, Kitty. I warned you, ma'am. Now, please, will you take me out of here before something happens? Nothing's gonna happen, Kitty. You and me are gonna dance. Have a good time.  Matt, it won't work. I've seen this kind of thing before. May I have this dance, Ms. Kitty? Please, Matt. You'll be implicated and you'll know it. Let's get out. You're refusing me, Ms. Kitty? Oh, Matt. We danced. But it wasn't what I hoped it would be. Kitty closed her eyes. I guess she was trying to blot it out. But I could see the other couples looking, whispering. And one by one, dropping away over into a small group that got larger. And there were only about six of us left when the wall sent it. That's when the stranger and a couple of his pals walked out onto the floor. They were drifters. Probably been in town for a week. And they were having their fun before they moved on. My sure. I got a painful duty. Yeah? Folks in this town seem real upset about you bringing that woman in here. What's your name? I'm just a fella. I kind of made myself my friends here. A committee of three, seeing how everything is done by committees here. And we figured it would be best if you take your... friend home. Mr. I'm the Marshal. Matt, I'm leaving. You're staying here, Kitty.  Everything's fine, Chester. This ain't a matter of law, you know, Marshal. It's decency and what's right beyond Marshal. This ain't right. Mr. I'm taking this badge off. Chester, you stay here with Kitty. Matt, don't you do it. You. We're going to talk some more about this out there. Ah, it's cold outside.  You know, I won't hit you in here, don't you? Were you thinking of doing that, Marshal? Now, that ain't lawful. I ain't done nothing. Kitty. Kitty, wait! Now, there's a gal with sin. All right, Mr.  We'll think of that. We sure will. Marshal. Just three no-good drifters. Hating the law. Finding pleasure and trouble. Kitty had gone and I went out into the street. It had stopped snowing. Just cold. Much colder. I went up to the Texas Trail. There's only two people in there. Some guy, dead drunk on a table and someone else standing at the bar looking into the mirror at me. Well, you haven't, Mr. Dillon? Nothing, sir. Yeah. I got some things to do in the back. Give me a call if anyone comes in, will you? Yeah. I'm sorry, Kitty.  I'm sorry. Sure. I could... I should have known better. No, it was me, not you. No, I wasn't that either. It was all those polite ladies and gentlemen. Give me a crutch of this. Yeah. Here. Been a long time since I cried. Yeah, sure. It wasn't so much for me. For you. I wanted... I wanted to cry right there in the hall, watching you and knowing there was nothing you could do. Nice mess of people we got from Dodge. No, it's not them, man. It's me. I've run into this before. The only difference was I didn't have you around. I wanted it to be right tonight because of you. A lot of narrow-minded prayers, spoutin'. Yeah. They hurt your pride, didn't they? No. No, I... It wasn't that. No? I wanted you to go with me. That made me real happy. But maybe we're different, Matt. You and me figure life different to them. That's not their fault. There's a lot of folks there I know. I smile at them on the street. They talk to me. But tonight, well, that was different. I made them uncomfortable. Yeah? Well, I didn't do a bad job with you. Well, you can't look at it that way. And you can't go fight in the whole town, either. There's three fellas going to get hurt. No, I don't want you to do that, Matt. Just... Let it go. Let it go, Matt. They don't mean nothing. You know what means something to me? What? That you asked me to go to the dance with you. I knew what was going to happen, but it was worth the chance. I thank you for it, Matt. But you sure showed them up, those women. The way you look. I'm glad. You know, you look pretty fine yourself. Sam? Yeah? You got any champagne, Sam? What? Have I got any what? Champagne. Well, yeah. I guess maybe. A bottle or two? Yeah, maybe. Well, break it out. I think the next dance is mine. Oh, Matt. I'd be real pleased, Mr. Dillon. Gunsmoke. Under the direction of Norman MacDonald stars William Conrad as Matt Dillon, U.S. Marshal. Tonight's story was specially written for Gunsmoke by Anthony Ellis with music composed and conducted by Rex Corey. Feature in the cast were John Daener, Vivi Janus, Bob Sweeney, Lawrence Dubkin, and Mary Lansing. The only bear is Chester, Howard McNair is Doc, and Georgia Ellis is Kitty. Gunsmoke is heard by our troops overseas through the worldwide facilities of the Armed Forces Radio Service. Join us again next week as Matt Dillon, U.S. Marshal, fights to bring law and order out of the wild violence of the West in Gunsmoke. Don't miss Robert Crowden his timely roundup of World News tomorrow on most of the same CBS Radio station. Roy Rowan speaking. And remember, Amos and Andy are here every Sunday on the CBS Radio Network.


All right, hello. This is a huge conference. Oh my gosh. So hi, my name is Joe Arnold. I'm the CEO of Swiftstack. And here we're going to talk in this session about a globally distributed storage cluster with Swift. And so what this enables folks to do is to use multiple data centers and replicate data between them and have one storage system, and they can flop back and forth between those data centers to get access to the data. And we wrote a book on OpenStack Swift, and we're giving them away at our booth, so it's a Swiftstack booth. And we're going to do some book signings tomorrow and Wednesday. So I have a few up here if anyone wants some after we do a Q&A. A few more announcements. So we have a party going on at the Tabernacle on Wednesday at 8.30. Please do come check it out. There's been a ton of Swift sessions going on. Tomorrow there's a Swift 101 session, which I'm doing with John Dickinson, the Swift PtL. And then right after that, there's going to be a case study with Fred Hutchinson. It'll be good back to back tomorrow. And if that's not enough Swift for you, Thursday, you can spend all day immersing yourself in Swift at a workshop that we're going to be doing at near where most of the hotels are. So come check it out and sign up for that. So globally distributed Swift cluster. So we implemented this feature about a year ago. And the thing that we were trying to solve was people had use cases where they're deploying applications and they wanted to upload data and have it available in multiple places. So the first customer that we worked with, our first user of this, announced at the Hong Kong Summit. And what they do is an expense reporting travel documents. And they wanted to have a better user experience to serve content out. And so the use case, we put a video for the keynote then, what it allows a user to do or build an application is an operator can set up two regions and then content can be uploaded and directed to, say, one of those data centers. And data goes in and what they wanted was the ability to upload entirely in one region. And then they also wanted to have the ability to read that data in from another region. So in this case, so we're using Hong Kong as an example, data gets replicated asynchronously over to that environment. And then what happens is another user, if they want to go access that data and say they're on the other side of the further away, can pull up that picture. And what they do is they'll say a GeoDNS will grab that object and pull it in. So depending on where the user is, the user will be redirected to a different data center. So that was kind of one of the main use cases. And so what we were solving for was some hard problems. The first thing was you had most people who were setting up a disaster recovery setup. They had more storage footprints. So you had your primary storage that you're using for the application. And then you had a one-way replication to the disaster recovery site, which was more or less identical. Some people set it up with maybe the previous generation of equipment. And the problems with that is you have more infrastructure, and not all of it is being used to service user requests. Then you have larger failure domains, because you have larger volumes that are being serviced out to users. They have more eggs in one basket. If one of them goes down, it's more consequential. And then the failover wasn't transparent. So if the main site went down, there was a hiccup in that application before the failover took effect, and the application was to continue. So the ways people try to solve this is do things like user sharding. And so we'll take the knowledge of all these users that they have, and we're going to put this group of users in this storage pool, this group of users in this other storage pool, and so on. And when they added new farms of capacity, they would grow that way. And some of the issues that were brought up then were you're adding new users to new equipment, and your old equipment is older, and it's full. So it's slower. And then the new equipment doesn't have any users on it, and it's fast. And it didn't make any sense. It made upgrades harder. There was more to manage because you have more storage environments to work through. The other issue then, if you're to do a distributed file system and have POSIX semantics, is that there's consistency needs to be addressed. And waiting for a global write lock was it can add latency into the system. And so that was a design goal of POSIX that isn't necessarily needed for all applications. And it causes things to break down once they reach a certain latency distance from each other. So why not just use cloud for everything? If you're familiar with the Amazon ecosystem, they have a product called S3, which is also an object storage in the cloud. And they too also have multiple regions. But you, as an application, have to know to put data in this region or this region. You have to move the data between the two regions. And one of the first service providers to use this multi-region capability in Swift is EnterIT. And so they have a multi-region European cloud. You can go talk to them at the booth. They have a booth here. So you can go talk to them about that. And it's powered by some of the software that we built for them. So how does Swift work? So you have a data placement strategy with Swift. And sometimes it helps to think about things in extremes. And if you take a Swift environment and you can collapse it down into just a box, what it does is there's a unique as data placement that's happening. And so each drive is used to put data onto it. So there's no raid in the system. You don't put Swift on top of the file system. And data is replicated across those different drives. Then if you move up and you have a medium-size Swift cluster, say three nodes, this is really common what we see. If you have a few hundred terabyte, maybe 50 to 100 terabyte, something like that, you might have three or four boxes. And then what Swift will do is it'll make sure that objects are uniquely placed across each one of those different nodes. And then if you grow up a bit and you get a bit larger cluster, you might have multiple racks of gear. And then Swift will, again, make sure that data is placed across those different racks. And analogy holds true. You can just kind of see what's happening here. Multi-region, you have data is distributed across multiple data centers. So that's the general strategy. And so how Swift does this is the first thing that was introduced was this concept of zones. And a zone in Swift allows an operator to say, here's a section of my data center. And it is running under this power source. Or maybe it has this cooling environment. Or maybe it's this network segment. And here's another one. And you basically give a tool to an operator inside of the same data center to say, this is a fault-tolerant domain. And so that was one of the first things that Swift implemented to allow an operator to do that. And so one of the components in Swift is there's this proxy tier. And the proxy tier, I just showed one of them. But usually, there's more than one, obviously, because you need to fail over. The proxy tier will route requests from a client to wherever the storage is. And so in a write configuration, what happens is the proxy will stream that write into the proxy tier and then down to each one of the storage nodes simultaneously. And the client will receive an OK request only when what we call a quorum. So if you're using three replicas, when two respond back correctly, then, hey, we got your data. You're good. And then for a read, the proxy will go to one of those nodes, read one of the data responses back, and we'll serve it out. And if it fails, it'll try an alternative if it can't reach that data. And even when that failure happens while the reading is happening, what it'll do is it'll keep that connection open up to the client. And it will go find another location for that data and fetch the remainder of that object and continue to feeding it up to the client. So that way there's an interruption happening. So we went, aha, OK. We have these components in place. What if we can add another abstraction on top of that? And that's where regions come in. So now we have the ability to say, here's a region for a data center and then zones within that data center. So and then inside that, there's actually nodes too. So it'll use all those three tiers to do data placement.  And if you're trying to read data, the proxy has some knowledge about where it is. So when a request comes in, it's not going to send that user off to fetch data from something over a WAN link. It's going to try to fetch it as close as it possibly can. And in that case, it has two rules that it follows. The first rule is, which region am I in? And which zone am I in? Something that you as an operator, you're telling it what it is. So that's going to be the first prioritization. And then the second prioritization is going to be, it's going to choose based on the, it keeps track of the latency to each of the storage nodes. And it's going to route the request to the nearest storage pool. And with writes, there are two configuration options with writes. The first one is what we call a normal write. And this is actually what we recommend for most use cases. Not to say the other one's abnormal, it's just this is the default setting. And how this is set up is the client will put data into the proxy, and then it'll stream to all the storage locations at the same time. And the reason why we recommend this for most use cases, this is just what we see out in the field, where you're loading data into the system. When you do that upload, you want the data to go live in all the locations at the same time. And it's great for backups, it's great for content, things like that. And it prevents the replication from falling behind client ingest. And that's the reason why we recommend it. And then for what we call affinity writes, how that works is the client uploads to a proxy. The proxy's aware of where it is. And in this case, it writes to only local at first. And then asynchronously, it puts the data in the off-site location. And we recommend that in the context of trying to speed up or where users are waiting to upload data. So the use cases for this very specifically would be media ingest. So if you're working with folks who are meeting entertainment and you want to have multiple geographically distributed clusters, you could upload just locally very quickly and then let the offline replication trickle out. Course networking is very important. So there's a dedicated or you can specify a dedicated replication or WAN link and apply a separate QoS between those two regions. And then when you go to deploy and you go to tell the users or the applications how to be routed to one of these proxy pools, that needs to be figured out. And again, this isn't part of Swift. This sits above Swift, conceptually, is using DNS to route to either one of those storage pools. Some people get fancy and will use something like a GeoDNS product, which is like Akamai and others have products which will, based on the DNS query by the client, knows the relationship of how far away everything is and can tell them which one to be near. So that's how people plug that in. This multi-region works really well with storage policies. And what storage policies do is allow an operator to say, I'm going to create a policy in one region. I'm going to create a policy in another region. I'm going to create another one between the two. And this allows all sorts of different configurations. So if users put data up into, say, that purple one, the region where it's region one plus region two policy, it means that the data is going to be in both locations. Or they can choose, and you can charge back differently. If you missed it, Paul and John gave a good talk this morning, but I'm sure the links are going to be up on YouTube. So keep posted on that. And so why all this works, or it works sanely, is because there's no file or object locking that is happening in the system. We kind of cheat in a way. And it means uploads can occur, and other people can be uploading the same objects at the same time. And conflict resolutions very simple to mediate. It's done through timestamps, newest file wins, and there's no logic in the code to distribute any global file locks around. It makes it faster to access objects because you're not waiting for those. And it increases the surface area of the number of requests that you're allowed to have coming into the cluster at any given time because that resolution is so system. There's nothing shared between any of the nodes to lock anything up. So it's very efficient that way. TCO is another great reason. Because you don't need to set up site A and site B and have them replicate between the two, you can buy less hardware in its one system. So the concur use case is presented in the Hong Kong OpenStack Summit. This is their TCO. It was with four replicas, as all the power, space, cooling, management, personnel costs, and including licensing costs, less expensive than the public cloud, less expensive than traditional storage. And this is a very intensive application. And then for an active archive example, Sir Fred Hutchinson, they're going to be presenting on tomorrow at 12.05. And this is what their costs ended up being. They have really, really low cost power because they're in the Northwest. But still, it's a really compelling number. And they did three data centers on the same campus and three replicas. OK. So that was all the fun stuff to talk about. This is the hard stuff. So if you go to do this, there's some challenges. There's some hard problems to solve. And the first thing is about adding and managing the storage capacity. When you go to add a device, the way Swift works is that it sucks in an individual device, individual hard drive. And to that hard drive, you have to say, here's its location. Here's how much capacity it has. Here's how to access it, both for storage access and for replication access. And at the end of the day, it means you have lots of stuff to manage. You have lots of devices. You have lots of zones, regions, little details to manage. There's Swift configuration details. And then there's the building of the Swift rings, which will go into tomorrow at the Swift 101 talk. And then distributing those around and doing that across multiple data centers, across multiple machines to all be orchestrated and acted as a whole is pretty challenging. So the other thing is also adding capacity. And the way you add capacity in Swift is by tuning some variables. So when you add a new hard drive, you're adding by what we call a weight to that drive. And what we do is we slowly ratchet that up. And that's mostly so that you're not flooding that drive, you're not turning it on 100% at once. And there's a lot of network traffic. Adding a region often involves adding another replica. So you're going from three replicas to four replicas. And you're doing it over a WAN link. And I don't know how many of you have been in that situation before where you start saturating your WAN link, but I know I've been yelled at before for blowing that thing up. And so what the strategy is is to incrementally change the number of replicas over a longer period of time. So you go from three replicas to 3.1 replicas. And what that means is you're going from 100% of your objects have three replicas and 10% have four replicas. And you push that out and you let the data queues. And you do it again and you let it queues. And you do this in a coordinated orchestrated way so that you're adding capacity in a graceful way. The other thing to solve for is authentication. And Swift has in the proxy tier a memcache ring. Actually, it's a really cool piece of technology that came out of the Swift community. It's pretty neat. And what this does is it caches some things, like access control lists for objects. And the way Swift does authentication, it uses a challenge token response method. And those tokens are cached in that memcache ring. Well, what you don't want is you don't want that memcache ring to encompass a proxy tier that exists over a WAN link. Because then you'd have random latency issues when somebody came in. And it just so happened to have to traverse the WAN to go get that cache bit of data. You don't want that. So configure that memcache ring so it encompasses a proxy pool in each region. And that's the strategy to solve that. So from a, we had Swift Stack focus entirely on building deployment tools to orchestrate, manage, scale, Swift. And so here's how we solved it, was we have agents that are running on the nodes to identify devices and fold them in. And then a way for operators to place them into regions and zones and to manage that configuration. And then we automate the storage provisioning. So that whole readjusting the weights, readjusting the number of replicas, and rolling that out, pushing that out, confirming that the configuration is durably distributed across all the nodes is something that we do as a product. One of the other hard things is also is network monitoring. And you want to watch that the replication network is not getting behind what you're ingesting. And so keeping tabs on that so you know if there's any issues is an important thing to do. But even if it does, even if that WAN link goes down and you're writing in, it will still find places to put the data durably. And when that WAN link comes back on, it'll push stuff over. And of course, management needs disaster recovery too. So if you do have management tools, however you're doing the deployment, the configuration management, make sure you keep in mind that it's not some VM parked in a data center somewhere that's now not accessible. And so have a disaster recovery strategy for however it is that you're managing your system. The way we do it is we have a warm failover, usually in the other environment. And then we use the same DNS strategy to flop over when we need to. So our product, what we do, we work on Swift. That's what we do as a company. We have a lot of the core team members. We have the project technical lead who works on us. We try to do best we can to rally a lot of developers in the ecosystem. And we build a deployment tool around it. So it's Swift at the core, it's on commodity hardware. We try to make it as easy to deploy and scale as possible. And we want the control of the storage system to be in the software, not something bundled hardware and software together. So that's what we provide. So deployment, integration, scalability. So benefits, you can distribute data across the data center zones, across multiple data centers. The software corrects for failures. So that routing happens, whether it's a networking failure or a dry failure happens. In software, you can use all your capacity to serve all your users. So provision for all the capacity, all the incoming requests that you need. And you can route across all that available capacity instead of having dedicated disaster recovery equipment. And through that process, you can route users to nearby data and it gives them data faster, makes them happier. And that's it. We have the party come see the book. And thank you very much. Any questions? So the question was daisy chaining of replication. And so if you saw some of the things, sometimes you might have two objects of that same object that's traversing the WAN. So we have a choice to make. Do we try to add some smarts into how the replication is done and be efficient use of the WAN? Or do we just naively push the data across the WAN? If we had to be smart about it, we would have had to introduce something in the system that's a shared state that said, hey, this is the one that's going to go across the WAN. And we chose to be more naive in exchange for having better scale out properties. So there's a trade-off there. And we didn't want to introduce something that introduced a shared state in the system. Yeah, so the question is, is Swift the back-end storage for it? Well, this whole conversation was Swift as the back-end storage. And because of the way that the data is stored in Swift as an eventually consistent model, it allows for the use cases such as this. So it's more challenging to put the strategy on more of a consistent storage underneath. Yeah, this goes down to the disk. Yeah, it's a full solution down to the disk. Yep, a question in the back. So the question was, how do you configure storage policies? Is it something for an application or is it set by the operator? So the storage policies is a tool for operators to specify options on how you want your users to use it. It's not a user-defined setting. It's a operator-defined setting. So if you had an application that was significant enough and you wanted to create a specific storage policy for that application, then you could do so. And yeah, one more question. Yeah, so the question was GeoDNS. And GeoDNS is outside of the scope of Swift. So it'd be something that you would use or you'd acquire through some other service. And the way those services typically work is they keep track of the distance between that client request to all the different options for the host. And then it'll route those users when they make that DNS query to resolve to another host name, which is going to be good for them. And it makes a guess at that. And so those are outside of the scope of Swift as a project. But it's often how people will use that. Yeah, does that answer the question? Oh, so right. So when the reader request comes in, by that point, the client already knows, ah, you might have Swift.example.com, right, as the top level. And then you would have East Coast Swift.example.com, West Coast Swift.example.com. And when you're making those API requests, you've already resolved down to that specific host name down here. So all right, thank you very much. And if anyone's interested in a book, come on up. Then I'd happy to provide one.