Buon pomeriggio, ragazzi. Tutulatalk in Italiano. Allora. This talk will be in English, thank God, because my Italian is terrible, as you can tell, and I apologize if I've offended anybody in the audience just now. So my name is Will Foster. I'm a DevOps engineer at Red Hat, and today I'm going to be talking about an exciting new Python-based framework called Quads that we've developed in-house that solves some of the problems that we have. And I'm just going to get right into it. So before I kind of explain what Quads is and how we've built this sort of framework to solve some of our infrastructure and automation problems, I want to explain what I do at Red Hat. I'm on a very small team of two people, and there's not enough car analogies on the Internet. In fact, there's never been a car analogy used for open source. It's never happened. So I'm going to use a car analogy here to kind of explain what I do and what my other colleague does on the Dev App side. So I want to talk about high-performance computer servers as race cars. Very high performance, you know, fully spec, the latest Intel AMD chipsets as race cars. And high-performance networks would be the race tracks. And the race car races that run on these tracks would be performance and scale testing of various open source products that Red Hat develops and also upstream things like OpenStack and OpenShift and Kubernetes and different types of technologies that we want to test and vet at a very large scale. And the actual race car drivers themselves that are driving these servers that are race cars on these fast tracks, 40 gig, 100 gig networking or race tracks, are the race car drivers. They're the scale engineers. And that's a pretty cool analogy to have if someone says, what do you do while I drive race cars? So it's kind of throwing a bone to more of the core performance and scale engineers by calling them race car drivers. But I look at myself and my colleague on kind of the Dev App side as we're the pit crew and we're the track engineers. And our goal is to make as many races happen all the time as efficiently as possible without any wrecks or explosions, and those do happen, which I'll get to. And this tool quads helps us automate the entire thing, including writing our documentation for us, configuring VLANs on Juniper and Cisco switches and the full life cycle of provisioning bare metal servers, passing them to an engineering group for product and scale testing, and then spinning them down when they're done. So if this was either a terrible analogy or an awesome one, I have a very simplified one and this is the reader's digest version, which basically we manage 300 or so high performance servers and switches and a large infrastructure. And this infrastructure accommodates parallel product testing. And it's really comprised of isolated sets of machines. We refer to them as clouds because we're not very creative for different workloads that happen simultaneously. And with quads, we have basically automated our entire jobs. We've automated ourself out of a job. And instead of spending the time going and being network engineers, being systems folks that have to deploy servers, we've automated all of this with Python, and we instead spend our time on actually improving the automation. So what is quads and what isn't it? What sort of things does it do and not do? Well, it's not an installer. It's not a provisioning system. It bridges several interchangeable tools together. I mentioned foreman because that is our back end provisioning vehicle that we use. But we design quads in a way that if you have an existing provisioning system or a workflow or anything that you're used to, you can plug that into quads. Quads will simply call out to your provisioning system to do re-kicking machines, re-provisioning machines or pushing image-based deployments across a lot of servers. And it also helps us automate basically the boring things that maybe you do once or twice and it's exciting, but you never want to do again. I love network engineering. I love connectivity. I like switches and firewalls, but I don't want to do that for a living. I would rather automation do it for me because it makes a lot less mistakes and it's frankly better at it.  So what is quads from kind of a high level? We drive everything with Py YAML. So the idea, the top-level idea is that for every asset in our infrastructure, we have a YAML-based schedule that tells it what it's supposed to be doing from what start date and what end date and what isolated work group or assignment. And this way we can programmatically schedule things in the future. You know, in an ideal world you would know the development schedule of all of your engineering groups. You would say, you know, in November Team A is going to be releasing a beta of Project Y and Team C is going to be doing the same thing. And if you knew what people's needs were ahead of time, you can schedule compute and network resources in advance. The reality of it is none of that ever happens like you would like it to. Deadlines shift. There's different holdups and blockers with bugs and different projects. And how you perceive the world to ideally be is never actually how it turns out to be. So we've baked in a little bit of resilience into how we schedule things in the future. So a little bit more detail about how it actually manages this kind of programmatic YAML-driven scheduling and provisioning. We set aside the YAML schedule for server assets. And then we automate basically the entire life cycle of a set of machines from beginning to end automatically. So on a Sunday at 2,200 UTC, if you're going to be receiving, say, 200 servers in what we would call a Q and Q0 or a specific VLAN configuration that we support, automatically your machines would spin up. They would reprovision. Tooling would go out to each of the switches and configure VLAN. So you would have one isolated environment separate from the other engineering groups. And things like form and self-service account would be created. You would have your own IPMI credentials to get into the machines out of band. And then our documentation would be automatically generated to reflect the current state of what your machines are doing and who is using all of the assets inside of an environment. So how do we use this internally at Red Hat? So we have a large R&D environment called the Scale Lab. And this is where we test and vet all of our products. Red Hat Enterprise Linux, OpenStack, Rev, Satellite. I don't even know how many products we have, but that's where we test them. And it's a very special place because all of the hardware is deemed high performance scale gear. We use 100 gig networking across the board. It's all very high in servers. And it's not a place for you to have a development test bed. It's a place for you that if you are doing development work and you hit what could potentially be a scale issue with any sort of bits of the application stack, and you're able to reproduce this issue on a smaller scale, this is where you go to run it at a very large scale so we can anticipate how customers using our software would do in the real world. Ideally, we would identify issues before other customers hit them. But again, that's not always the case. So in our Red Hat Scale Lab, we have about 300 servers. We have 40 or 50 high performance juniper switches. And right now, we run about 16 to 20 different isolated scale and performance workload on these systems for up to four weeks at a time. And quads help us spin up these machines, hand them over to the appropriate people for short term lease, and then spin them back down again and put them in kind of an allocation pool. So I'll give you an example. And let's look at some pictures because everyone likes pictures. So this is the example of some of the scheduling that we do automatically. So this is from February to May of this year. And you can see how we've very efficiently done back to back scheduling of all of the machines in the environment. And you can see, you know, four to five parallel running workloads testing different products, different scale, different aspects of different products. And all of this when it's scheduled in advance, all happens automatically.  There's a two person team, we got a lot of infrastructure.  Here's an example of, you know, some of the metrics that we've gotten from the lab. I just I kind of picked this at random. This is a storage workload. You know, and these are some of the results that we get out of out of the scale lab and quads kind of empowers us to do this sort of work. So we talked a little bit about the time savings and efficiency, but I want to drill down more into what problems we're actually solving here. Besides the obvious. So the first one is server hugging. Does anyone know what server hugging ends? Okay, so server hugging is the idea. Once I explain it, you'll be like, Oh, yeah, I know server hugging. So server hugging is the idea that if you give someone a resource, they're going to hold on to it as long as possible until you pull it back from them. Developers are very bad at server hugging. And usually, there's always more of a demand for resources than there are actual resources to give people. So if you're lucky enough that, you know, your manager is particularly savvy, and he can fight for a budget to have this R&D dev test hardware, and he's better than the other managers at it, then you're going to have more gear to play on. But the sad reality is, is there's never enough bare metal hardware, unless your Facebook or Google or, you know, one of these behemoths that you're not going to have bare metal high end server hardware to run your code and test against all the time when you want it. So server hugging is the idea that there's this tendency of people to hold on to things longer than they should. And it's a natural human thing.  It's your, it's your pet. It's your, it's your area. It's yours. But it's not really yours. You got to share it with other people. So by having automated scheduling of heart of server resources and network resources, you sort of force people to be more efficient with their planning, you force them to maximize the time that they would have on a set of hardware, and you can save a whole lot of money and time by doing it this way. So what's the other things that we solve when we automate things? No, there's, there's less human error. That's good with more automation. And to a certain extent, you can kind of give control over to the machines because, you know, what's, what's the worst that's going to happen? You know, at that point. There's obviously bugs and quads.  Terminate. There's obviously some rough edges and in our software as there are. But you know, the idea is that you automate as much as possible. You know, the biggest area of devastation is on the network side. It takes one typo to configure the wrong port and totally offline a machine or just cause straight up havoc. So simply just automating the network administration is a huge boon to having errors. The downside is when automation fails, it normally fails in glorious ways. It's normally just a giant explosion, slow motion trainwreck when your automation actually fails because it's so efficient at something. And if that something has errors, then it's going to be catastrophic. So Dave Wilson, if you're watching this, I'm really sorry about your 50 machines that got eaten by our network bug, but it's fixed now. So what are the other things that we're solving here? So we want to maximize idle machine cycles. Electricity is expensive. Carbon footprint is always an issue. And we want to automate and spin up machines only when they're Where were we? So what we do is we power off machines when they're not in use. And only when they have an active schedule in their YAML config, do they actually come alive and get participate in some sort of an automated workload. And sometimes they don't work like you'd like them to. But that's kind of the double edge sort of automating things. So lastly, we want to solve the scheduling issues. We go with short term reservation. So if you rent, say 100 machines, if you use quads, and you get assigned 100 machines in a particular vlan configuration to do your development and your testing at scale, the maximum you can keep it is four weeks. Because we only have a couple hundred servers, but we have queued up almost a month wait time to get to those those resources. So we want to be more like Airbnb, and less like a hobo house. Airbnb has very defined guidelines. You can't stay in an Airbnb longer than four weeks. And it has uniform for the most part, kind of things you would expect from an Airbnb, you know, you generally know what you're going to get. Maybe not, but it's a little more polished and professional than, you know, like say a hobo house. And the last thing that we really save here, and this is kind of the impetus for us continuing to, for us to automate our jobs, and then work on the automation, is the time savings and the cost savings. So we had done some kind of back of the envelope math of using 100 machines for an example, if 100 machines changed hands tomorrow, and went from one development group working on something or a set of developers with a specific scale or performance problem they were trying to fix. What would be the cost and the time involved if someone was to do that manually? Now, granted in 2017, I hope no one is doing all of this by hand. I hope people aren't inserting an ISO into a server somewhere and someone's on a on a SSH console and a switch and they're I hope people aren't doing it that way. Maybe some people are, but assuming that you did do everything manually, it would take roughly 90 hours of work to provision 100 servers and pass them off to someone else. So for our current two person team, that would be about 45 hours a piece over a week of work. And if we tripled our team, it would be about 15 hours or two working days.  So quads does all of this on Sundays, when most people aren't working and automates the entire thing in a span of two or three hours. So when Monday Monday morning rolls around, machines are already passed off notifications are already sent to the users, they already have their own special credentials to access the machine that only they have. And then the clock starts ticking on the reservation. So I'm not going to drill into this, but this is kind of how we came up with this figure. And these are pretty conservative estimates of everything that we do. All right. So how does quads actually do all of this? We've talked about the problems that we're going to solve with it that we we solve today, we talked about the level of automation and efficiency that we're able to yield. But how does it actually look on the back end? So I have made some rather grotesque topographical images for you. This is not going to win any website awards, but we all remember Milton from office space. We're going to say he's your typical scale engineer, and he needs hardware. So this is the kind of quads architecture at a very high level. We have now a JSON API in front of it. But generally speaking, there's also a daemon and also a CLI that you'd interact with. At its very basic construct, there is a YAML schedule that is constantly modified by PyYAML. And I'll give you an example of that a couple of slides later. But this is at the heart of how things are automated in the present and in the future. There's also some provisioning elements. If we want to do any graphing, we have hooks into collectee and Grafana. And we also can send results to Elasticsearch as well. But this is more ancillary stuff that we would set up after the fact. Automated, of course. And then lastly, there's the consumable here besides the actual machines is the documentation. At any point, anyone can look inside of this quads managed environment. They can see what all the machines are doing. What does the utilization look like? Who has the machines? What are they working on? And for how long they'll be working on it? So when you provide transparency like this, it's easier for people. They don't have to ask you, hey, you got any spare machines, guys? Or I have this project a month from now. What's the schedule going to look like? All this is already published and available to anyone who wants to look at it. So there's tie-ins to the actual provisioning, which is the next slide. And there's a plug-in to quads, basically a open-ended command that we call move hosts. It's just a simple art parse option in quads. But this is where you tie in your provisioning system. So however you run the life cycle of re-provisioning on operating system or laying down an image over top of it, whatever your method is, you plug this into the move hosts command. You define this in quads. It can be whatever you want. In our case, we just use form in because that's one of the tools that we enjoy using and saves us some time. So the quads move host command would basically spit out if the time is running, like if now is scheduled right now, for a set of machines to change hands and go to another environment with another VLAN configuration, we would get this printed out in our logs. We would say, this example server is moving from Cloud Zero One environment to Cloud Zero Two, as an example. On the back end, on the form in, at least for us, this is our provisioning workflow. We would tie form in to add and remove role-based access for the host. We would change the IPMI passwords so that users are isolated in their own environment. We would do a full provision of the offering system. We would lay down any post-configuration stuff, and then we would actually move the VLANs on the physical switches, depending on the VLAN design that we support. And then, lastly, and I think more importantly, is there's automated network validation that happens. We don't want to pass off a set of machines to people if they're not ready to use or if there's something wrong with them. So we run automated validation that checks and checks and checks, and if every one of the machines doesn't pass the network validation, we get notified, and then it continues to check and intervals until we fix the problem, and then it finally passes validation, and the consumers of the hardware, of the isolated environment, get notified through a couple different mechanisms, usually IRC, bot, and email. So we talked about the AML schedule per host. This is what it looks like. This is kind of at its basic, the construct of how the PyAML drives current and future scheduling of machines and networks. So we see this defined schedule here. They're very simple command of LS schedule. We'll list you all of the current, the past, current, and future scheduling that Quads knows about for a particular asset. So at the very bottom here, number five, that would be like, say, a current allocation. That would be something that started June 28th, and it's going to end the 6th of July or has ended. And we keep a historical record of this in the AML file because that drives the documentation and also the visualizations that we make. So onto documentation. Now, I like writing documentation once. In fact, I don't even really like writing documentation, but it's one of those things that is so critical to any sort of project or any sort of endeavor that it's also the most lacking aspect of documentation. So we decided that one of the pillars of this Quads framework would be to automate all of the things that we either don't want to do or we are going to screw up at some point. If you have even outdated documentation is still better than no documentation, but it's still terrible. So our goal was to have absolutely up to date by the minute documentation. And the way that we do that is we query our provisioning source, in this case it's Foreman. It could be anything else. It could be Ansible Facts, for example. And then we query Quads because it knows about the past, current, and future schedule of everything in our infrastructure. We parse it into markdown format and then we use an XMLRPC Python library to push it up to a wiki page. And then this is continually updated every minute. Anytime there's a change in the environment, anytime a bare metal server is added or removed, this gets updated in the infrastructure documentation. In this case we use WordPress. It's got a nice API for this, but it could be easily media wiki or anything that supports some programmatic markdown format. And again it doesn't even have to be markdown. That's what we currently use. So this is an example of what it actually generates. So this is the front sort of infrastructure documentation of a set of our servers. And this is what is continually generated and updated every time. We have your typical things you would expect from infrastructure docs, like a hostname, serial MAC address, IP address, we have a link to the out-of-band console. But what's different from this than something that someone edits is that on the right-hand side we have workload. So if you were to click on that workload link, you would drill down to exactly what those sets of machines are doing, what is cloud 06 for example doing. We know our Bryant is the owner of these sets of machines. And then this is an older image but the graph link would redirect you to a Grafana dashboard that has all the historical bandwidth throughput of all the interfaces per machine, which is useful. And again, these serial numbers are actual servers but they're out of support. So you're not going to gain anything by getting them from my talk but you could certainly pay the bill for us if you feel inclined. So along with a general infrastructure layout of the documentation, we drill down into assignments. Again, kind of what machines are doing right now. And this is just an example, a snapshot taken a few months back of various internal testing of products and things like that. We see a lot of open shift stuff in here, open stack, elements of open stack. We see some software to find networking, running things of that nature. And then you can drill down further into the workload and you'll see how long they've had the assignment, how long it's going to run, and what's the remaining time. So again, this just gives people an added level of transparency to see there's no more black box. What's going on with this server gear that we have? You know, it's very clear, is there servers available? I can request them and I'll get them and then I get this nice generated print out. And then we also tag faulty machine. So if there's something wrong with the hardware, we simply assign a key value pair of faulty and then it goes into the spare pool or the faulty pool that we can have the local lab people take a look at and fix. On top of the documentation, we have visualizations as well. We generate a calendar. So at any point you can see what kind of tests are running inside of the R&D scale environment. And then lastly, we have a heat map visualization. Now, this doesn't look like it's going to win any website awards. It looks like the old Windows 95 defrag program.  But it's incredibly useful from a scheduling perspective because we can look at and this is generated three months in advance, six months in advance, whatever you want to set it at, but we can very quickly see what's available from a day of the month or at a longer view and then we can use that to schedule free servers for people that have requested it. So again, and this is all automated, automatically generated for you. Cool. So as you see earlier, we definitely need more testing and CI is very important. So we do have testing. It's not good enough. But it's it's getting there. We use Garrett for code review and then we use Jenkins for the CI and we're working on now kind of a fully instantiated virtual sandbox using open vSwitch and some other stuff to emulate switch ports. But right now we're using Flake 8. We're using shellcheck for some of the shell kind of glue that we have in the project. And we need to probably get proper tests in. So we're getting there. Quads is about 11 months old. And it's been running our R&D environment for about eight of those months. Cool. So what's working right now? This long list of stuff that I'm not going to read to you. This is available in all the documentation that we have. If you're curious, you can you can ask me after the talk. But it's going to do a whole lot of stuff for you. What are we working on? This is even more important. So what are some things that we have planned to introduce with quads? We the major thing right now is we want to introduce the idea of like a post config. And what that would do is it's one thing to provision the networks, the storage, the servers for people and hand them off and document them and then reclaim them when they're done. But you probably want to automate other stuff on top of that. We have a lot of folks testing OpenStack, for example. And you might get, you know, say 50 servers to do an OpenStack deployment and then you're testing a specific part of that OpenStack deployment. And you could easily burn one or two days getting OpenStack deployed and getting just right. So we want to offer the option of kind of an open-ended model that whether you're laying down an infrastructure as a service set of software or you want to lay down some kind of container orchestration on your host, we want to offer the option that that is also automatically done for you. So when developers come in on Monday or Tuesday or whenever they want to work, they don't only have their servers that are documented, that they have their credentials and they're ready to go, but they also have any ancillary software stacks that they need to test on top of already set up for them. And it's again, it's about saving time and being as efficient as possible. We're also working on a Flask Web interface for quads to kind of enable some self service scheduling. So if you're, you know, developer Jane Doe and you want to schedule yourself 100 machines for a week and they're available, you can go to the Flask interface and request them in a week's time whenever you want to start. Your machines will show up for you in a few hours. So that would be a really cool feature to have. We just put in place a JSON API. So that's been pretty useful, but we haven't quite, we're not using it internally, but it does work pretty well. That's going to kind of pave the way for the Flask interface. So we're kind of doing slow moving blocks that way. We just got in place the automated network validation that I talked about. And we also want to support more resource back ends besides form in. I'd like to have an Ansible back end that all you have to do is run Ansible against a set of hosts. You yield all of the facts from discovery and then that is what formulates the information that's in the wiki that's automatically generated. So again, you know, the overall theme of quads, of this kind of loose framework that we put together is being as efficient as possible with the few resources that you do have. And you'll kind of see this. So in our case, and this is really a construct of any sort of company that's larger than 20 or 30 people if you have bare metal assets or say you have machines in a data center or rented resources, is that over time, development groups tend to silo the resources. So, you know, like department A is going to have their servers and they're going to be entirely different make and model than department B and they're going to be bought at a different time and their depreciation date is going to be different and maybe their hardware profile is different. So a company ends up spending a lot of money maintaining these little siloed areas and pockets of infrastructure. And the idea behind quads is that you put everything in one giant bucket and then you let quads do all the provisioning, all of the scheduling and take care of the whole thing for you. Now obviously there's downsides of automated scheduling and provisioning and that sometimes people's deadlines slip or sometimes they have something come up and they need to take vacation or they can't use the hardware. So we've built in things into PyAML and PyAML is very good at this and that we simply just need to modify the schedule and then quads framework does the right thing from a provisioning perspective. But again, this is a lot of very little tools, little small things that do one thing and do one thing well, sort of sticking to the Unix KISS Prisable, if you will, that we just keep it simple. And selfishly from kind of the DevOps operation side is that we don't want to do the same thing more than once. If it can be automated, we want to automate the crap out of it. If it's boring or we mess it up a lot, we want to automate it. And if it's something that's just we just don't want to do, obviously machines can probably do it better for us. So that was kind of the drive to initially get this thing going. So the parts of quads might be more useful than the sum of its parts. Some people like to use just the automated documentation, for example. The scheduling aspect might be useful. There's parts of the framework that you could consume yourself because it's not all tied together. It's very modular. So we've also got some external interest into quads as well. There's some ongoing collaboration we're doing with Boston University and MIT in the Massachusetts Open Cloud. So we're kind of merging parts of quads with their scheduler that they've written called Hill, HIL. And we've had some kind of large public companies show interest in using it for their Dev and test environments. So that's basically it. Thanks for coming to my talk. If I have any time left, I could open it up for questions. If anybody's got some. And if you want to read more, everything's open source. It's all on GitHub. And we certainly welcome patches because we're just not that good at Python, but we want to be. So welcome for anybody to give us a shout and look at the code. Yes. I'm curious that can we use this framework for failure testing of a cluster? For what type of testing? Fader testing. Fader testing. Fader. I mean, if some of the notes goes down, can we use to test such a scenario? Yeah. I don't know. OK. It's really aimed right now for bare metal servers and kind of scheduling, provisioning and resources based on a future date. OK. For example, what happens is like one of the notes doesn't start on the scheduler. What happens then? Just talks and you go and fix it by hand. You're talking about OpenStack specifically or? For example, your class writing like the US schedule, like the 50 notes with your computation. Uh-huh. And if one of them fails, what happens? Hmm. I don't know. I'd have to think about it and get back to you. Yeah.  It's designed in a way that we don't want to dictate a use case for you. We just we find great utility and efficiency in having kind of an open-ended framework. And if there are certain parts that you can reuse, it's designed in a way that there's inputs for that. So we ship like a YAML configuration file that, just a key value pair, that if you want to use a different Wiki, for example, or if you don't care about the provisioning aspect, you could only do the scheduling or you could only use the documentation part. Hi, thank you for the talk. You mentioned about the way you schedule and provision servers. What happens when they go offline? Say you reserve 50 servers and then two of them go offline. Do you have any logic in terms of preparing them, spare servers? What's exactly the policy on a large scale set up? As far as error? You reserve 50 servers, right? And two of them go offline. It happens. Servers break all the time. So how exactly do you manage acting up company policy? So they technically won't be servers anymore. They're provisioning them from somewhere else? Well, so things are going to always break. You know, there's, you can build in any level of validation of pre-provisioning validation. But we found when you're doing very large deployments like several hundred servers at once, there's going to be always be one or two stragglers where, you know, maybe they don't pixie correctly to Kickstarter. Maybe there's a failed disk that isn't picked up by the monitoring system. So the best that we can do is bake in as much automated validation as we can. And right now, that's only on the network side. But we don't really do it on the system side. Generally, we have enough servers that if there is a serious hardware failure, we can easily shuffle them out of the pile and throw another one into the mix. And then that one takes its place. And then we can always sort it out later. And then that's why we generate the faulty servers on the documentation. But I don't know a good solution for that, because you're fighting against so many factors at that point inside of a data center. There's the network layer. You have power issues. You have anything you could even think of that's going to go wrong at a large scale. So we build more. Our redundancy is more built into having at least one or two spare of that type that we can quickly shuffle in and then dealing with it later rather than trying to bake in extremely long, tenuous validation. But we could always do better on the system side validating. Does that answer your question? Great. Yes, sir? I'm just wondering about the network side. How do you actually deal with connecting out to your devices, say the Juniper, your Cisco? Do you have any issues with like vendor interoperability and how you connect? Do you use just like NetMeco or something? I'm sorry. Can you repeat? So do you have any issues with interoperability? So Cisco, you might connect to it via SSH or with Juniper. You might have a better way like a NetMeco or something. We do. Certain vendors, because we have a pretty heterogeneous environment. We have a lot of super micro machines, a lot of Dell machines, and they're not made equal when it comes to out of band interfaces and things like that. So we do have to do some one-off things. It's more apparent on the network side that you would interface with Junos completely different than you would interface with iOS. So we have per vendor tooling that would go out and change the VLANs. And everything is done, basically keep this flat file structure. And it's done in some kind of a CSV format. So there's one per server that has several fields. And it maps, like, say, the Ethernet interface to a MAC address. And there's a field there for vendor ID. So if we were dealing with a Cisco switch versus a Juno switch, we would need to make sure that that vendor ID field actually has Cisco. And then if it does, it knows to use the other tooling that does the equivalent iOS stuff. But it's not elegant in any way. It just, it gets the job done. Ideally, and this is more of a immediate future thing, is that Ansible is working on network orchestration, but it's done at an abstraction layer.  I want this VLAN or this construct to go from this to this. And if it's in its desired state, it does nothing. So it's idempotent, but you don't need to care about the vendor semantics. The abstraction layer in Ansible will take care of that. But I don't know how big that is. I think it's very actively being worked on. And that's what we're going to move to. But right now we maintain per-vendor network automation scripts. And luckily right now we're almost all Juniper across the board. So it makes that easy. Any other questions? Well, feel free to find me after the conference, and you can borrow my Terminator mask and attack me if you like. I'm into that, I guess. So thanks for your time and I appreciate you coming to the talk.


This animation outlines the process the Roslin Institute scientists followed to create Dolly, the world's first mammal to be cloned from cells taken from an adult Dorset U. To help you follow the process we have labelled the parent sheep, sheep 1 and sheep 2.  The first step involved taking cells from the udder of sheep 1 and culturing them in a gel to create a batch of identical cells. In the course of culturing these cells they were deliberately deprogrammed to let these cells regain their potential to become totipotent to form any cell needed in the future clone and not simply another cell from a used udder. This single achievement marked a significant breakthrough. Meanwhile an egg or ovum was removed from sheep 2, a black faced female Scottish U, to be prepared for implantation. Using techniques developed in human fertilization treatments conducted at a microscopic level, the nucleus from the sheep 2's ovum was removed or inucleated to make sure that none of sheep 2's DNA and genotype could be passed on to the next generation. Once the ovum had been inucleated it was then fused with a cell from the sheep 1 culture of deprogrammed udder cells. In effect emulating the process of a sperm entering the egg but with both copies of the chromosomes coming from the same parent sheep sheep 1, so the newly fertilized egg is genetically identical with this single parent. Once fusion had taken place chemical factors in the egg are released to stimulate cell division. Once the cells had multiplied sufficiently to form the makings of an embryo, the new cell cluster was transplanted into the womb of a third sheep which we will call sheep 3 for a 21 week gestation period. In total 277 attempts were made to fuse the adult cells with a nucleated eggs, only one survived. Dolly was born on the 5th of July 1996 by Caesarean section and was found to be genetically identical to sheep 1 from whose udder her DNA originated. Dolly lived until the 14th of February 2003 when she was put down suffering from a progressive lung disease.


My name is Louise Corty, and I work in the collections development team at the UK Data Archives, which is part of the UK Data Service. Our strengths really are in brocoring access to data. That's actually finding and cultivating relationships with people who have data and also enabling the right access pathways. So our expertise is in licensing, in governance, and in providing access to these data. It's a one-stop shop for a whole range of data with the same application processes. maic hallsu eithollo ac nderrywio yn jeun men ton. We've got fantastic collection that comprises over 7,000 collections of data En Dreams of some of the major government surveys that have been collected back to the 1960s. We host a whole load of longitudinal studies which means you're following people over time a number of qualitative data sets that will be oral history interviews with people and we also hold some of the global indicators from countries around the world I mean, it's really hard to think of a world without the UK data surveys mae'r bwysig bwysig bwysig y Brith yn ymgyrch yn fawr iawn. Mae'r bwysig yn fawr iawn.


It's really powerful to be here and to celebrate one year of Starbucks work was united with you all. My name is Shay, I'm an organizer with Code Pink which is a feminist anti-war organization. At Code Pink we focus our work on ending US wars and militarism, supporting peace and human rights initiatives and redirecting our tax dollars to life-affirming programs. And the critical part of our work is understanding the role the United States military plays throughout the world as a global cop and bully. The US military sends poor and working people to fight US wars against poor and working people throughout the world. These wars make CEOs and government officials rich through gaining access to natural resources, installing governments and bolstering war profit-ears profits. These wars are fought at the expense of everybody else throughout the world, people who do not get rich off of militarism but face death, violence, destruction of their communities and climate chaos. And it's not incidental that the United States military disproportionately harms working people. One of the primary reasons that the National Guard was established in the United States was to suppress and control workers, which was going on as early as 1892 with the Homestead Strike, the Pullman Strike, the Ludlow Massacre and the Battle of Blair Mountain. The United States military exists to enforce the social and economic global order and that is inherently anti-workers rights, which is why it's really powerful to be here bringing in the anti-war movement representing Code Pink. And, although we know they're really different institutions, United States military and Starbucks use really similar tools to try and suppress workers and communities creating change. They both use greenwashing pretending to be sustainable, pinkwashing pretending to care about queer people, even though their actions demonstrate the exact opposite of that. We know that the exploitation of workers and of the global majority is inherently incompatible with the progressivism that these globalized corporate bullies claim, whether that is Starbucks or the United States military. That's why it's really powerful to be here and to celebrate one year of Starbucks workers united with you all. Woo! The Union Campaign's incredible growth to representing almost 7,000 previously unrepresented workers is a huge testament to the power of the people uniting overgreen and exploitation. Our movements are connected. The victories of Starbucks workers united is a victory for all of us involved in the struggle for justice against militarism and against corporate exploitation and for life-affirming resources. Solidarity will win all of our fights. Thank you so much.


Hi, it's me Yolanda with every way woman talk show and I want to Run something by you Have you ever thought about why you are here? Why you were born? I know I do all the time especially as a kid and I wanted to show with you that Sometimes we're waiting for a moment or an event that we Have that aha moment and we figure out. Oh, that's why I'm here. I Think you may have already had that moment and not realize it a lot of time we brush it off I want you to go back and think about why you are here and What's your purpose and? What you should be doing It's easy for some Than others because I think that we run from it more than accepting. Okay. This is why I'm here This is what I'm supposed to be doing and so I wanted to share that with you that If you're struggling to find out who you are Even if you are a 50 year old man 45 year old woman It's okay because it's not that easy, but just think about it take a little time consider some events that has happened to you in your life and If you really think about it you figure out what you're supposed to be doing Who you're supposed to be helping and the change you're supposed to be making. Okay? That's my advice


Evening by Archibald Lampman Red for LibriVox.org by David Lawrence August 3, 2008, in Brampton, Ontario From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk into the western sky It beats up into the lucent solitudes or drops with griding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. Evening by Archibald Lampman Red for LibriVox.org by Ernst Batinama August 4, 2008, Amsterdam, the Netherlands From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with griding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. Evening by Archibald Lampman Red for LibriVox.org by Leanne Howlett From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with griding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. Evening by Archibald Lampman Red for LibriVox.org by Leanne Howlett From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with griding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. Evening by Archibald Lampman Red for LibriVox.org by Leanne Howlett From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with griding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. Evening by Archibald Lampman Red for LibriVox.org by Secrets From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with grinding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. End of poem, this recording is in the public domain. Evening by Archibald Lampman Red for LibriVox.org by Cedro Baldelli in Rome, August 2008 From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with a grinding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out of the stars and the great night comes on. End of poem, this recording is in the public domain. Evening by Archibald Lampman Red for LibriVox.org by Stuart Bell, Cambridge UK From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with a grinding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus, one by one shine out the stars and the great night comes on. End of poem, this recording is in the public domain. Evening by Archibald Lampman Red for LibriVox.org by Veranwheel From upland slopes I see the cows file by, Lowling, great-chested, down the homered trail by dusking fields and meadows shining pale with moon-tipped dandelions, flickering high a peevish night-hawk in the western sky beats up into the lucent solitudes or drops with grinding wing, the stilly woods grow dark and deep and gloom mysteriously, cool night winds creep and whisper in my near, the homey cricket gossips at my feet. From far off pools and wastes of wreaths I hear clear and soft piped the chanting frogs break sweet in full pandian chorus one by one shine out the stars and the great night comes on. End of poem, this recording is in the public domain. End of poem, this recording is in the public domain.


We've gone through some of the concepts of computer and network security and we looked at six different attacks on network or communication security and they come up in computer security as well, releasing the message contents, which is really just, sometimes we say we intercept other people's data and see the data when you're not authorised to see it and traffic analysis, analysing the communication patterns, so not necessarily looking at the data but looking at how often you send messages, who do you send to, what times you send them and from that inferring some other information. We gave an example yesterday with that email that I sent or that the student sent to me, we showed that it's very easy to do a masquerade attack with many internet applications, there's no checking of who the real sender is, so with the email it's very easy to send an email with the fake from address, so if someone just checks the from address, they can be confused or tricked into thinking it's a message from someone else, so a masquerade attack. Replay is resending an old message to get some benefit, modification, modifying messages, so intercepting a message, not letting it go through to the destination but first modifying it and sending on the modified form, and denial of service attacks where someone overloads a server or causes a server to operate such that the normal users cannot access that server, they denied access to that service, so we saw an example of a masquerade attack, we have one topic that talks about, one lecture that talks about denial of service attacks and we'll see some examples there and over time we may see some of the others but just before we move on, a simple example of releasing the message contents, that is two users are communicating for example I'm going to communicate from my tablet in Bob's position to a website and access that website and then via my laptop I'm going to try and intercept those messages and see if I can see what the two users are communicating and it turns out it's quite easy especially with Wi-Fi, so I think most of you will do the networking lab with me this semester and in that we will do some, what am I about to do now, we'll learn the commands of how to intercept Wi-Fi traffic, I'm not going to show you the commands I'm just going to do it just to illustrate, what I've done is, there's nothing to see yet, what I've done is I set my computer up, my laptop to record all the packets that it sees, that it receives, now with Wi-Fi when I use my tablet which is also using Wi-Fi it sends a signal to our access point in the back of the room here or in the room behind me and the nature of most wireless transmissions especially for Wi-Fi is that signal goes in all directions, so when the signal goes from my tablet up to that access point the physical signal is also received by the antenna on my laptop and all I've done is configured my laptop such that any signal it receives record a copy of the packets contained by that signal, so when I send something and I'll access let's say the ICT web server, of course you cannot see it but on my tablet if I access and you can access the ICT web server on your phone and maybe I'll capture your packets as well, it's very hard typing, if I access the Moodle website or other websites on my tablet and I suggest if you have your laptop open access some different websites or your phone, you need to be using in this case the Wi-Fi, so WSIT and what my laptop is doing is trying to record everything that everyone else is sending, now let's see if this works, so I've been recording and I'll open some software of the record, I'll stop the recording and then show you what I see, this is a record and it's hard to see at the moment, this is a record of all the packets that my laptop recorded over the last couple of minutes, I was recording that when I started in the lecture and there's I think hundreds of thousands of packets have been recorded, they were not sent by my laptop, they were sent by other people nearby, including you, including my tablet, now there are many packets there and I don't have time to analyse them all, so I'm going to look specifically for my tablet, I don't want to look at your packets because that would be a bad thing to do, so my tablet had an IP address of <IP_ADDRESS> and filter out those 260,000 packets and get a subset of the packets, that was the packet sent by or received by my tablet using the Wi-Fi and there are many of them there, let's see if we can get something that we can recognise, put it out and just see the HTTP messages because I was using the web browser and specifically let's see if this works, TCP port 80, two equal signs and there's nothing there, hang on, as always with demonstrations in a network there's always something that will go wrong, let's see some packets first and see what we can see from others, let's look for some HTTP messages, some of these are not relevant but if we scroll down I'm sure we'll find some that you may recognise, one more try before I give up, here we go, here you may recognise some of them, these are HTTP messages, focus on I'll scroll down in a moment, these are get requests, if you recall how HTTP works the browser sends a get request to a server, get this web page and here I've recorded from other people's computers in this case from my laptop they're getting different pages and I will not look too closely as to what websites you are browsing but you'll see many requests for different websites and if we look in the detail of those we can actually see this was accessing Instagram for example so this was from a web browser or an application probably on someone's phone or tablet that was accessing Instagram to look at photos or to post photos and that was done by computer which was not my laptop in fact was not my tablet in that case it was computer on the SIT network with IP address <IP_ADDRESS> possibly one of you or it could be someone out nearby so the point is it's very easy with Wi-Fi to perform an attack where you release the message contents because I now as the attacker see the contents of the messages that other people are sending in the vicinity if we're using wired networks it's much harder for me to do that I need physical access to the wires but still possible so that's to illustrate that even though I may not have captured my tablets packets I need to search closer it's very easy to do a release the message contents attack and from that you can also do traffic analysis because from those 200,000 packets I just captured in a matter of several minutes I could then start analyzing and see which IP address sent to which other IP address which IP address sent to which websites at what times of the day did they do that and then if I could map back and find that this IP address belongs to this student I can now start analyzing what that particular person did so again a traffic analysis attack is quite easy we saw yesterday a masquerade attack was quite easy with email also with other services and in fact the replay and modification attacks are related to those too so they're a little bit more complicated to get them working well because you need to intercept before it gets to the destination but possible the point is it's easy in many cases for these attacks to take place therefore we need strong techniques to prevent them or detect them and that's what we'll get on to with the next topic so we listed some security services that we want to provide to try and prevent or detect attacks and how do we provide those services we use a set of security mechanisms and many of the mechanisms are based upon cryptographic techniques so what we're going to talk about in a moment is what are those cryptographic techniques encryption is the key or a very important technique the last couple of slides very quickly we can say with regards to a strategy for computer security or a set of principles normally what we start with for an organization or a set for a user we set up a policy what's our aim in terms of securing our computer system what are we supposed to do with the computer security techniques so we gave examples yesterday a policy for SIT one student cannot access the grades of other students and many other set of rules usually informally stated that we have an idea of what we want to achieve and in fact there may be many different rules that we want to define in setting up a security policy an organization needs to consider what are they trying to protect we said there are four types of assets software hardware data and the communication lines so which ones are the most which ones of those are the most important to the organization say for SIT the student grade information and student contact information is an important asset we shouldn't release it publicly the financial information of an organization is an important asset the software that we run on service is also another asset so we have a number of assets we want to protect and we need to consider which ones are most important try to allocate a value to those assets we need to try and consider what are the vulnerabilities what can go wrong how could someone get access to those assets when they shouldn't not supposed to what are some threats and what's the charts of a tax taking place what's the consequence if one student does get the grades of another student what happens then do we lose a lot of money or does a student get upset or something else happens and what's the probability that a tax will take place so an organization should consider all of these factors to come up with a security strategy and they often need to consider trade-offs like implementing security mechanisms to implement the strategy versus making it easy for the users to use the system and many of the security mechanisms will have a cost involved a direct or an indirect financial cost so we need to consider well what's the cost of implementing those security mechanisms versus the cost of an attack taking place us failing and having to recover so sometimes even though we should implement a security mechanism that may have a very high cost and it may be a cheaper option not to implement it and just recover if some attack does take place so that's what the policy tries to identify those trade-offs then the organization will implement a set of mechanisms to try to complete that policy and they would focus on how to prevent detect respond and recover to attacks and we'll look at techniques for implementing and then they need to do assurance they want to have some confidence that the techniques have used will work as intended and they want to do some evaluation to make sure that the techniques are working it's no good to implement the security mechanisms and then find out that they don't achieve our original policy ideas we will not cover these details of security policies in this course but be aware that there are a number of ways to develop a security policy for an organization doing risk analysis identifying the trade-offs and doing assurance checks to make sure that implementations work correctly we will stop this topic there are some information security principles listed there but they probably don't make much sense to you until we explain each of them I'll later provide you a document with a definition of each but I think as we go through the next few topics we'll come back and some of these principles will be identified especially things like privileges least and separation of privilege privilege open design we'll see when we talk about cryptography defense in depth so I'll explain them as we go through the next few topics not now they actually come from another document from NIST which I'll have a link to on the course website so that finishes our introduction to security in summary we want to achieve the objectives normally of confidentiality keeping our data secret integrity making sure it's not modified without permissions and availability making sure our computer system is available to the users and we want to protect different assets and there are a range of different attacks so far we've identified six different attacks releasing the message contents and traffic analysis and for what we call active attacks I think I didn't say the difference between passive and active maybe I should say it now passive attacks involve the attacker doing something that doesn't modify how the system works the attacker is passive and they don't need to make changes to the traffic in the network they don't need to send extra messages they just sit there and listen an active attack involves the attacker making some changes to how the system works for example they modify a message they inject a new message so the difference between those types of attacks passive and active is passive the attacker does not modify how the system works active is the attacker does make some changes the the significance of comparing the two is that passive attacks are usually easy for the attacker to perform and hard to detect whereas active attacks are easy to detect so the approaches that we use to defeat those attacks usually passive attacks we need to use techniques in advance to prevent them whereas active attacks we use techniques to detect them and we'll see that as we go through some cryptographic techniques we also said that we can talk about inside or outside attacks depending on who's doing the attack we mentioned that there are countermeasures or security mechanisms they are the techniques that we will use to implement the the security services so they will be the techniques to prevent detect recover from attacks and the prevention and detection in particular usually use cryptographic techniques encryption especially so the next topic we'll look at those cryptographic techniques am I finished there's two more slides I will not go through these most of the lecture topics I'll include two or three slides at the end giving some other areas that you may explore if you're interested you can explore on your own like different organizations which we involved in computer security and in some other sides you may see some future issues or research issues that that can be considered we can discuss maybe outside the class if you're interested


Welcome back once again to Misa's weekends. I'm your host Jeff Deist and we're continuing our series Featuring some of the young scholars here at the Misa Institute acting as summer fellows and this weekend We're talking to Lukasz Dominjak, who is an adjunct scholar at Copernicus University in Poland And this summer as he studies and researches with us He's focusing on the works of Hans Hermann Hoppe and some of the cultural aspects of a libertarian legal system Lukasz and I also discussed the tension between liberty and free immigration in supposedly democratic states Where we have arbitrary national borders instead of hoppy and private property boundaries and as a result This clouds the issue of immigration for libertarians And we wrap up our conversation talking about Hoppe's concept of private defense where protection against invaders Would be more a function of collective agreements and insurance arrangements than armies So if you're interested in Hoppe private law and the role of culture in libertarian theory stay tuned for a great interview with Lukasz Dominjak Lukasz Dominjak welcome to Misa's weekends. Thank you for having me So more importantly welcome to the Misa's Institute We're very happy and pleased and grateful that you chose to spend your summer with us For starters, why don't you tell us a little bit about how you came to be Interested in Austrian economics and the Misa's Institute Right. So actually I think the interesting thing is that my background is not economics is political philosophy so I somehow come from political philosophy and I'm still within the remit of political philosophy more than economics and I Think I basically starting political philosophy. You just get acquainted with libertarianism This is one of the most important contemporary political philosophies and But I would say like within this mainstream political philosophy you usually encounter Robert Nozick Libertarianism particularly his book Anarchy, State and Utopia. We just know how different from What we have within the Rothbardian Hoppean Libertarianism, I think this is this are two different approaches towards problem of liberty and and private property so basically I Got acquainted with Robert Nozick quite early in my career as a political philosopher and I wasn't really at that time Captivated by his approach. I was working within classical tradition. I would say like I was taught to Aquinas and contemporary representatives of this tradition and so basically My PhD was about communitarianism. This is Mainly anglophone Philosophy concerned with the concept of community and how individual operates within different Communities and but later on I read Hobbesburg democracy they've got that failed and he really captivated me. I think like his arguments are really strong arguments against statism and I found particularly interesting arguments against democracy and my boss at university is a monarchist So I had some like natural inclination towards anti-democratic political views and Yeah, it somehow found Interesting expressions were in the hoppers. So what is your particular line of research that you're working on this summer? Yeah, this summer. I'm working on a project that In one sense out I would call it a connection between anarcho-capitalism on a political and economic level with cultural conservatism, but I think that To understand this project we should look a little bit into background of it So I think that libertarianism particularly in this Rothbardian Hopiian tradition is a quite narrow or thin political philosophy It means that libertarianism is concerned mainly with with one question what are justified and unjustified ways of using violence and because it starts from two main axioms as a political philosophy, which is axiom of self-ownership and Principle of non-aggression it answers these questions in the following way. So anything that is Against these two principles anything that violates these two principles is considered unjustified use of violence and anything that Defends these two principles is considered justified use of violence and there's a third, I think part in this understanding of libertarianism that anything that does not follow into This two categories is left for individual choice So in this sense libertarianism is a thin political philosophy because other political philosophies usually Consider the question of a good life as a political matter so for example How people should behave morally is also considered a question for state power legal Issues law legislation and so on so forth libertarianism in this sense is a thin philosophy But it raises a question I believe because libertarianism is somehow mute on these problems which which can be called moral or cultural and the question is what would be the Cultural tissue of an aquacaptive society what would be the moral code of such a society and Basically, I'm trying to tackle this question and my answer at least tentatively is that this moral code and cultural Tissue would be conservative. So if we accept the view that political libertarianism is a thin Philosophy, it's just a philosophy on what the state should not do It sounds like what you're saying is the culture that arises in this political arrangement is one that stands or falls on its own merits It's not state directed. Yeah, that's true. I and I believe that there are many arguments that can show why libertarian Society would be a conservative society. So of course, there are reasons that we can say Direct that show that society would be conservatives. So for example, we know that libertarianism is Political philosophy that is in favor of private property and we know that what we consider as a conservative moral code we don't have time probably to define conservatism here, but More or less, we can say that Christian morality is what is meant by conservative morality Usually and if we take for example, the seventh commandment that that say as our shot shout not steal Then we know that libertarianism is of course directly in favor of this Moral commandment and that statism is say is against it that taxation in any kind of form for example state created legislation or state created Inflation is stealing basically so that there's a like there are some direct ways in which libertarianism promotes Conservatism, but there are also other ways for example, I believe that a lot of moral turmoil that we experienced these days is caused by somehow elevating to the rank of public problems behaviors and issues that have been with us from the dawn of time but Always confined to the private sphere and now they somehow elevated the rank of public problems and because Such institutions as mainly state Public health service and social security Even marriages they would be privatized then all these problems as public issues would disappear immediately In an aquacouple of society, but I believe also that as a most more sophisticated arguments that show that Libertarianism would be conducive to cultural conservatism One of these arguments that I'm working on is a argument that is based on so-called frequency theory of probability Developed by Yiddishad von Mises and then refined by Ludwig von Mises his brother and this theory basically says that For a probability of a given event This particular event has to be a part of a class of events in such a way that we don't know anything about this event Except that is a part of the class of this event So basically for insurance company to estimate probability and therefore to calculate premiums insurance premiums Particular risk or particular event has to be of this sort which is an event of a particular class of events and Obviously as far as human human actions are concerned. We know that human actions Some intentional behaviors are not this kind of events Because at least a human actor knows something more about particular Action of his then this action is a member of a class of actions of this type He knows that this action is actually a matter of his decision. He's free choice. So in a word basically, it's impossible to ensure yourself against your own actions and It would be impossible for insurance companies if they wanted to ensure this kind of Intentional behaviors to calculate proper insurance premiums it means that plethora of behaviors that These days are Insured against through state wouldn't be insurable behaviors insurable risks and if costs rise then Probably the occurrence of a particular behavior would decrease. Well, it's interesting Because it sounds to me like Your thesis is that Libertinism would actually be less common in a libertarian society because the individual would bear more the direct cost of his or her lifestyle choices Yeah, absolutely. I agree with with this and I think that would be the case We know historically that libertarianism was connected or was interpreted as promoting nihilism or Libertinism, but I believe it's not the case. It's exactly the opposite. It's like libertarianism is a political philosophy Political economic order that promotes conservative Order, well, you've studied hopper at length could you give us a Recently concise definition of what hopper would conceive of as a as a private law society what that might look like I think that private law society Would be based on Obviously on the concept of private property and the concept of contract. So any kind of contracts that freely acting individuals would Would make would be valid and any value Violation of this contract and a violation of private property rights would be punished in a private law society private law society as far as I understand it is also a Society in which everyone is governed by the same law and we know that it's not the case these days That in Western democracies, we are governed by two different laws private law and public law and that these two different laws and Make us unequal before the law so in a private law society would have a situation which people would be equal before the one law and This law wouldn't be considered a matter of legislation that would be considered a rather Moral a legal code that exists And it's probably developed only in an evolutionary way That couldn't be enacted by some body like parliament or any any other this kind of political entity, of course and I believe That's private society when we switch our focus from this legal question about private property and How how would it work and and how would contracts work? Into the question of culture that private law society would be a society in which We would have much less voice these days called tolerance and much more voice these days called and The readers as discrimination So talking about culture and talking about hoppa Here's the irony that I would suggest is that in both a libertarian or private law model and in a socialist or status model both of these tend to work better in socially cohesive high-trust societies, but it seems like that the project in Europe is going in completely the opposite direction It's a centralized status system under the euro, which is based on multiculturalism So what what would a more hoppy in Europe look like for example? I agree with what you said about the current European project that it's a multicultural and somehow based on forced integration political project and I think that Hoppy in Europe would look like more like actually that this is what he says in in in many places that at least this let's say transitory a stage of coming from status society to Purely private law society should look like a Europe of ten thousand Liechtenstein's Which is small political entities That would be by the very fact of being small forced to be liberal it's a free trade with each other and that would be under constant pressure of their citizens voting with their feet so that would provide this natural pressure for this entities to be to be liberal and the process of Succeeding from from a bigger entity to smaller entity would continue up to the level of particular communities So hoppy and vision of Europe would be exactly the opposite What is going on these days in Europe as far as European Union is concerned because as you said European Union is a project of centralized government where power is Taken even from the level of nation-states Taken from the level of nation-states and given to the central European Union bureaucrats As far as the second problem mentioned by his concern, which is a problem of multiculturalism. I believe that private law society and the very concept of private property presupposes discrimination or presupposes power to discriminate because to be a Owner of private property means that I'm the exclusive owner I'm the I'm the only person that can decide how this property can be used and no one is Allowed to interfere with my decision. So basically, I think it means that first of all all these pressures that exist these days in Western world and European in particular, I believe that force people to use their private property In a way that I'm not willing to use of course would disappear in a private law society Let's talk about immigration very touchy subject for libertarians on the one hand We believe in self-determination We want individuals to travel and live their lives as they see fit and most of us don't want national borders state Derived national borders to begin with but there's a very strong hoppy and a private property element Involved in the movement of individuals from point A to point B So what might immigration look like in a more hoppy and society first of all? I think that we believe that political borders are arbitrary and that borders of private property are objective and Natural so as far as Immigration is concerned as far as immigration is a matter of political decision. There is always a problem of trust trespassing natural borders at the same time trust passing of natural borders is Interpreted in the political language as a free immigration. It's free immigration as far as national political borders are concerned but as far as national and political borders are natural borders arbitrary borders They're always somehow in conflict with Private property borders. So I believe that does the problem of of so-called free immigration There was I think quite good argument given by hopper was the difference between free trade and free immigration So free trade is a situation which good No travel But for a good to travel this good has to be invited that there has to be some purchaser I would like to purchase a good otherwise this good will not travel over borders with free so-called free immigration Is different because usually free immigration is not a matter of invitation It's a matter of political decision. So in a way people are invited to a country Defined by the political borders, but they don't they don't have to Necessarily be invited at the same time to the natural borders of private property So so yeah, this is as far as diagnosis of a current situation goes. I think like in a hopin society immigration would be immigration on Invitation invitation would be would be the Crucial thing in a private law society if you invite it then you can travel if you're not invited Then any traveling would be actually a trespassing would be invasion of private property So invitation would be necessary condition and I think that people would invite other people if they can contribute some something to their lives and their Prosperity in their culture knowledge and so on so forth So no discussion of hoppa would be complete without talking about so-called national defense if we had a series of smaller Independent private law society's 10,000 lichtensteins as you put it earlier throughout Europe. How would they collectively? Defend themselves against let's say other states that were not private Like the much wanted threat from Russia How would in a hopping society? Poland in the Baltic states and the Scandinavian states for example Provide themselves with some kind of defense against aggressors Right. So so maybe before answering this main question some remark about this haunted fear of Russia. I think that This is interesting because my view but the mainstream view. Yeah, that's the mainstream view It's not necessarily the case if you look at add a problem of a conflict in the Ukraine It's it's more complicated. I and I think that European Union had a Some role in starting this this conflict as well not only Russia but We're coming back to them to the main question I believe that it's it's not so easy actually to invade our foreign country for say I don't know for Russia for some some other state a first of all even Authoritarian or totalitarian regimes they depend domestically on the opinion of the subjects So basically there must be some way of persuading people that give this Legitimacy to a political power that particular invasion is justified So first of all there must be some way of justification of invasion, which is not always so easy And I think it's particularly not easy if invasion is an invasion Against free society so free society is not a society in which we have dictatorship in which we have Genocide in which we have some other reasons that could that could justify invasion So that would be the first barrier. I believe the first problem that would Dictator would encounter if he wanted to invade free society and the second problem I believe he would he would face would be basically problem with Somehow fighting with insurance agencies insurance company because in a free society Private protection would be provided by probably provided by insurance companies insurance companies are usually international companies multinational companies really powerful economically and They are not so easy To fight against them and they wouldn't be so easy to fight a fight against in a free society in which they would provide also protection and defense for Private property owners, so that would be the second problem believe that this dictator or Statist that would like to invade the free society would have to face and I believe that would be the third problem as well Free society would be Generally armed society people that are armed Difficult to fight against because Contemporary war is a war when two armies fight against each other on the one hand It's true that this distinction between combatants and non combatants is blurred these days because of because of the democracy and welfare standards of also so on so forth, but still this Invader this army invading free society would have to fight with each particular Property owner, so we could say that every citizen of free society would be a threat For an army invading so again We know from history that it's not so easy to fight against a society. That is Utterly against the invader so we know about Vietnam. We know about Afghanistan It's really difficult to win against this entity Well as a Japanese general was purported to have said during World War two about America a rifle behind every blade of grass And with that Lucas Dominic. Thank you so much for a fascinating interview and ladies gentlemen. Have a great weekend


Okay, Arie, you played against Hussein today, how did you draw? Tell us something about the game. Well, it was started out early, so it was kind of like expected that it might be, you know, like a very balanced game.  So, but yeah, it turns out in the end, it was still pre-equal, but I do miss one chance where I could have just turned the table around. And I only found it only after I played my next move.  But after I missed that chance, the rest of the game was still pretty much equal then we agreed to draw in the end. But he thought he was doing quite well and you thought you were doing quite well, is that right? Yeah, that was right because he thought he had some counter attack somewhere with the bishop or something, but I have my own pass one on E5 which pretty much blocking his, whatever, like his pieces and things. And I was trying to make something work out, but yeah, I couldn't, also he couldn't do anything, I also already checked it after the game, yeah, it was pretty much equal. Right, okay, let's have a look at the game. Okay, we've got a Berlin defense here, show us what happened. All right, so okay, like E4, E5, Nf3, Nc6, bishop P5, Nf6. Okay, I was also preparing something else here, not Nf6 but G6 and also the main Spanish, but okay, he went with Berlin. Also, I think in the first round he played against Gn, Bz, also played Berlin, but I chose different variations this time, so castle, Nd4, d4, here takes and then a4, so this is pretty much a standard position and here he played Nd4 and then I took and this is something that we avoided in the game, like we didn't want to, well I didn't ask him, but I wouldn't have gone to this variation anyway, so this is like the infamastorian position, yeah. Not in the spirit of the sexes, this is the piece of the sexes. So okay, coming back to the 8th move, so he played d5 instead of taking on my knight and here I played c3, he said he never saw this variation before, I think I've shown it somewhere, I can't remember but this was at the back of my head, so after here Bb7, this is pretty much still equal, so still trying to get my pieces out, Bb3, castle and then take on c6, Bc6 and then okay and then I played d2 here and then he took and then in this position he played Bf5 and yeah, I mean my bishop is still, it is in a good diagonal, so I put my knight here just to help it and then here Qe8 was played and then in this position I thought it's time to exchange something, so after knight d4 he played Q here and then yeah the rest is pretty much balanced, so wait, I didn't take, I played Qd4, yeah? Qd4 yeah, okay, I played Qd4 but then he took oi oi oi, just a minute, rook takes, yeah, get rid of that, yeah, takes, takes, yeah and then here he played f5 which I think is a good move because that is black's weakness, okay a few moves in the game we were just kind of dancing around with our pieces but then there was one moment where I actually missed my chance and I think that was the only chance during the game that I could turn the table around, so in this position yeah he played group B8 so this was kind of like bluffing me because all I wanted is to get rid of any pawns in this c-file, so I didn't take but I should have taken, so this was the bluff, so it takes, I think what he wanted to do is if I took this pawn that this bishop comes over here and then wherever the rook goes there's bishop b6 and then skewering my queen but in this position exactly I stopped my calculation and then that's why I decided to play a different move, no but don't, this is my blunder or my mistake, I should have calculated further because here I missed this tactic, rook takes g7, king g7 and then this is just a pawn, wow so you just taken b8 and you're a pawner, yeah if queen here, okay I have additionally this if I want to I guess, yeah yeah and then if I don't do that like even taking and taking it I think okay take is definitely better but it's just in the end it will be like an extra pawn for me, so this is exactly what I mean, so probably this is going to be my lesson that you know when you are about to stop calculating the lines try one move further maybe look over the horizon, exactly yeah so I didn't do that, yeah so after rook b8 I played bishop d2 okay and then here he fought for quite a while and I was like trying to check the previous line that is it really working that bishop d8 variation and then in this position I realized that I missed my chance like oh I missed rook g7, so you went back and analyzed it, I went back to analyze it because I still have some doubt over my calculation, no I believe there is something but I couldn't figure out what it was but and then and then after this I managed to find out what I missed and I got so angry, I got so angry you know and I was trying to actually stay calm because this is the moment when if I got too emotional I would affect the way I'm playing so yeah I tried to forget what happened and then yeah but the rest of the game it was pretty much equal we couldn't get any any other chances for both white and black so yeah in the end I think yeah the king goes here king goes there and then in the end it will just repeat just Peter's out yeah but there was a pity it would have been a good tactical line if it was playing out but yeah anyway and your team needed it as well yeah I know I was waiting for that exact moment because well trust is an equal game of course but then you're waiting for your opponent to make a mistake or you know not too much not not being careful like what he did during the game like rook b8 he also missed there's rook g7 he thought that he could bluff me by playing bishop d8 but actually it was the other way around yeah okay thank you very much thank you