I think we're gonna start a few minutes early just because it's a slower capacity and I actually thought it was gonna be 50 minutes instead of 40, they were all 50 last year. So I may actually go through it a little bit faster because I wanna leave plenty of time for people to be able to ask questions. I think one of the great things about these conferences is actually being able to ask questions of people who are doing this in the real world. So I wanna make sure to leave a lot of time for that. So my name is Ryan Richard, I work for Rackspace, Private Cloud. This talk is going to be for some of the things to think about as you're looking at like designing a Private Cloud. Let's see, if we could hold off the questions till the end, that'd be great. Like I said, I wanna leave a lot of time for that. So the first question might be, is why Folsom? So the title of this talk is a Folsom update. Last year I gave one and really focused on Essex because we'd been running it for six months for customers, so we've been running Folsom for six months for customers. So I wanted to provide some best practices for that. So at the next design summit, we'll do the same exact talk except with the best practices we've been doing for Grizzly. I think Grizzly's gonna be a huge one. There's a lot of really interesting things coming in Grizzly that I'm sure you guys have heard about. I'm gonna, there's gonna be a slide at the end where I'm gonna touch on a little bit of the Grizzly features. All right, so just to get started, I wanna define what is a private cloud. One of the things that I feel like we could focus a lot of time on is sort of the goal of your private cloud. Are you actually building a private cloud that's gonna be elastic in nature? So you're gonna try and mimic one of the public cloud models? Or are you just really looking for a cheaper version of traditional virtualization? In reality, I think you need to pick one. OpenStack does both. It probably does the elastic one a lot better. And it's certainly not a drop-in replacement for, say, VMware, right? And if you think that you're gonna be able to simply install OpenStack, move your VMs over, and everything's gonna be the same, I think most people in here probably know that that's simply not the case. So, certainly the first thing to figure out is what you're actually looking for. Are you looking for elastic or are you looking for traditional virtualization? The next thing for a private cloud is most likely multi-tenant, but not necessarily at the organization level. It's multi-application, right? So each application, each application stack might be a different tenant. But certainly in a, and when we think about tenancy in a public cloud, it could be X number of customers or X number of different organizations. Size, for this talk, I'm gonna keep it limited to about 100 nodes and under. 100 nodes feels kind of like a breakpoint to where architecturally it's a lot different. 300 nodes, it's somewhere around 50, it changes a little bit. But after 100 nodes, it definitely starts to feel bigger and there's more considerations after that size. The endpoints for a private cloud may or may not be public. It's certainly acceptable that your endpoints for all of your Nova services and all of your OpenStack services are there in private space. The public internet can't reach them, right? Limited and bound connectivity, that kind of falls the same line of thinking. There, instances might be only accessible within your organization. They have accessibility out to the internet, but perhaps there's literally no accessibility in where this is where floating IPs come into play. And then the last piece is certainly is customizing for specific workloads. I feel like that's probably the biggest selling point for a private cloud over any public cloud is the ability to customize it for your needs. So that could be things like specific images, specific flavors, specific hardware, right? Most likely the hardware is probably one of the biggest selling points. So I wanted to think about what it meant to be like when you sort of start looking at sizing a private cloud. And we started thinking about the resources that every compute node has. Really, ultimately, we look at VCPUs, RAM, and hard disk space. There are more, of course, right? There is network utilization, network throughput. But these are really sort of the big three. So if we take the default flavors, and we start with the smallest one available, which is the M1 Tiny, these are just out of the box, OpenSack flavors. That's 512 megs of RAM and one VCPU and a disk size of zero, which is essentially the size of the image that you're using to boot. If we were to fill up one entire compute node, this is what it would look like, with just those number of instances. So the RAM to CPU ratio is way off, right? I'm consuming all my CPUs, I'm using almost no RAM, and I actually don't know how much disk I'm using. Because my disk size of zero, I can't plan for that, right? Total instances on something like this is about 48. Now, realistically, we're probably not gonna be running a lot of 512 meg instances, but there's certainly an occasion where you might do that. But again, the big issue here is that the CPU to RAM ratio is just way off. So let's take the medium, for example. So if we think about the number of instances with the M1 medium flavor, choosing four gigs of RAM and two CPUs and about 50 gigs of disk, this is a much more possible workload, you'll actually see this. Once I've consumed all CPUs, I'm using most of my RAM, which is good, and I'm using about half my disk space, not bad. That's a lot closer, that's really what we wanna strive for. And if we think about something on the other end of the spectrum, which is a heavy RAM, maybe a 64 gig image, eight CPUs and 100 gig disks, here I'm kinda on the other end of the spectrum. I'm consuming all my RAM, but I'm not really consuming my cores efficiently or my disk space efficiently. And I'm only running two instances on here. So my thoughts, what that leads into is some of my capacity thoughts. Initially is don't allow a disk size of zero. So you have to really start thinking about yourself as a service provider. You're actually acting as a service provider for your internal teams, for your internal applications. If you allow a disk size of zero, you're actually not gonna be able to plan for capacity at all. Because how big is image X or image Y? Like you don't actually really know. Most people try and keep them as small as possible, maybe seven, 800 megs, but you don't really know how big they are. You think about a public cloud model where they limit flavors based on resources. So I work for X-Base, so I'm pretty familiar with our public cloud model. And if you look at our resources of our flavors that we use, the more CPUs, the more RAM, the more disk space you get. So for capacity planning reasons, that makes life very easy. They know exactly how I can fit this number of instances on this piece of hardware. The trick isn't a private cloud world is that everybody ends up doing the second thing, which is they add flavors for application workloads. So you could think of a RAM heavy application workload like an indexing service or some sort of caching service, right? If you run a lot of those, your capacity might be underutilized in one way or another. So I think there's a middle ground that we have to figure out, which is do you act like a public cloud person, a public cloud provider, and you only give your internal teams access to very prescriptive size flavors so that you can understand capacity and trending really well? Or do you go more flexible and do you allow them to create flavors that match their workloads? I don't know the answer. I think that that is specific to every company. Everyone kind of has to make that decision. Lastly, don't forget about network utilization. I think that's often overlooked is to people kind of forget that you have only X number of gigabits per second on a compute node. It's certainly not something we wanna forget. With the private cloud model, trick there is if you are gonna go that way, watch trending very closely so you understand where your capacity is going. Certainly if you find that you have one application workload over another, plan your next set of hardware for maybe better for the application. So if you're very RAM heavy, go up on RAM and less on disk. So that is the trick there is that I can always add more machines. I didn't realize this is cut off in the edge. But I can always add more machines. We can always add more compute nodes. Compute nodes are extremely easy to add. Hopefully everyone in here knows that. If you haven't stood up your own OpenStack cluster, compute nodes are probably the easiest thing that you can add. With our Chef recipes when we deploy a compute node, assuming we've already set up the operating system and networking takes about two minutes. It's not, it doesn't take very long at all. The big trick is without quantum is you can't change the fixed network once instances are already running. So that's something I talk a lot about in this discussion is because pre-quantum it's extremely, extremely prescriptive with the fixed IPs. VLAN mode opens that up a little bit but it's still, you still have to define a fixed VLAN and once, or excuse me, a fixed range. Once you've defined it, you can't really change it without destroying all of your VMs and recreating which is not something anyone's gonna do in production. There actually is some ability to define multiple networks in Folsom even in flat DHCP without VLANs. You can do it, I don't necessarily recommend it but it can be done. The dashboard doesn't respect it but if you use the CLI or API, you can do it. So it's something worth looking into if you're gonna be running Nova Network and you wanna break up network space. Along those lines, if you have two networks with the, you know, on the same interface, if you just boot an instance, you're gonna get an IP out of both networks. If you specify which network you want, you'll get an IP out of only that network. So this is something that I had last year when we think about resource consumption or resource utilization, you basically take the resource, divide that by that resource in your smallest flavor. It really gives you the maximum number of instances per machine. Again, that's just something you need to think about for when you're defining the fixed range. And if I define a fixed range of 512 IPs, that's the most instances I'm ever gonna get in my one private cloud. So you really need to think about what flavors you're gonna offer, how many of those can be running, and then you probably wanna actually double or quadruple that just for growth, right? So we actually, most of our customers, I think we start somewhere 1,000 or 2,000 just out of the gate, you know, even if it's a very small private cloud, just to get going. So just to keep going on Nova Network for just a minute, there's really, there's two networks in play and there's three networks in play if you are going to use floating IPs. Certainly not everybody actually needs floating IPs, but they do come in very handy. So the host network is extremely easy to deal with. It's how you access the machines. You know, changing or adding the hosts is really not too big of a deal. Or even growing network, network's not that hard. The fixed network, like I said, is really the important piece. You really don't wanna try and change this once you're in production. That will be not a fun experience if anyone's, if anyone's had to go through it, you probably know. And the last one is the floating IPs. They're extremely easy to add. There's concept of pools. It's more analogous to how quantum is doing networking in the future. But you can essentially add a pool of floating IPs and then if you need more, you can have another pool, create those and those will be available to your users. Also assigning a floating IP completely changes the way connectivity to and from the instance happens. So I'm actually giving a talk tomorrow at 11.50, just on Nova Network. So not quantum. It's just gonna be an over network for to kind of go in some of the details of, you know, what's actually happening behind the scenes. So if you guys want some more information on that, I'm giving another talk on Nova Network tomorrow. There's also a number of quantum talks this week. I highly suggest going to those as well. All right, so I'm gonna switch gears a little bit and talk a little bit about images and storage. We've started making some images that we can give our customers. And as the bottom says, one of my team members is actually giving a talk on this tomorrow at 1.50 in room C123. But this is essentially what we've chosen, which is I think probably what most people have chosen as well. As far as drivers go, we're sticking with Verdeo for now. We've gone with QCal 2 format. A bear container. I think people are either between bear, or AMI right now. Cloud init and partitioning, we try and be as dynamic as possible. There was a talk in here earlier about how to deal with images. Basically, you need to be able to move the partition table around. If you're using AMI, you can put everything on a full block device. You don't have to move a partition table. That way when you boot, you can just resize the file system. And the other models, you really can't do that. So your operating system needs to know how to move that partition table. So we've done that in our images. So I'm calling that dynamic so that the partition table moves out. And then when the instance boots, Cloud init resizes the file system for you and you're able to gain those, get, make use of that extra space. The other thing with QCal 2, this was touched on earlier as well, is that there is a bit of a performance hit when you're using QCal 2. I don't think it's too much. I heard 3% earlier. I've heard 7% before. It's certainly, you gain a lot of space savings. So I would highly suggest that I investigate QCal 2 for your images if you're gonna be making your own versus taking someone else's. Some of the other formats that have been added, I only show three up there, but I think Glance supports seven or eight now, which include like VMDKs, ISOs. There's actually a significant number of formats that Glance does support. So speaking on Glance, there's a couple options there on where you're going to store your images. So Glance is essentially the service that provides images for the compute nodes, the boot instances on. File backed is gonna be probably the most common until you reach a size where that becomes unrealistic. You have some alternatives, right? So you have Swift. If you wanna run Swift internally, you can point Glance to Swift. Rackspace cloud files you can point to. You can point to S3 if you wanted. You could also do something like NFS where it's locally mounted as a varlib Glance and you have all this space available to you. That's certainly an option as well. As far as performance goes, the file backed local is gonna be your best bet, but you're limited on how much space you have in that one physical server that's performing that file that's backing Glance. As far as snapshots go, it's realistically hard to guess what your users are gonna be doing.  That starts to become a sizing consideration, right? So all of a sudden, you know, you're two terabytes of disk on your controller. If I'm got, you know, a thousand instances running, any of them can be snapshotting any given point in time. How do you deal with that space, right? So I believe that Grizzly actually brings, and I know this is a fulsome talk, but I believe that Grizzly brings some features where you can actually pick where the snapshots go, which don't necessarily have to be the same place as Glance or where your Glance backend is. So it's worth looking into. Definitely take it into consideration when you're building out the disk space on that Glance server, right? It's, as far as QCal goes, so I heard so much of the stuff that I've been talking about in the last talk about images. One of the best benefits for using QCal right now is that your, so when you have QCal, the base image gets copied over to the compute node when you're spinning up an instance and creates a QCal file, and then it uses that as the local disk for the instance, right? So if I only have, say, one base image, as soon as I have an instance on every compute node, my base image has already been cached, basically, on each compute node, and so each instance takes about a second to get going, right, versus the flip side of that is if I have a very large image, very large raw file, and I have to copy all that data over every time my image boots, so if I've got 20 different images, my local cache kind of becomes pointless. So my whole point there is it's simpler to standardize on less images and leverage automation and orchestration techniques to actually build the stack that's gonna go on it. So this is one of those things that I don't think a lot of people necessarily think about, but Glance performance, so network throughput becomes really interesting. You could easily consume an entire gig throughput just trying to copy an image over, especially it's a very large image. If you're sharing Glance with the rest of your services, so like on our controllers, Glance is running also at the Glance registry and Glance API as well as the back store, is there you could easily consume your entire network just with an image copy that happens every time your instance boots. So certainly take network throughput into account. You may wanna look at RAID 5 just due to the large sequential read and writes that Glance performs. We tend to go RAID 10 as much as possible, but RAID 5 is certainly doable, especially if you want more disk space. You may wanna prefer disk bandwidth over raw IOPS. You're not doing a lot of small read and writes, you're consuming very large sequential blocks, so disk bandwidth, maybe it worth looking at. And what I talked about earlier was improve the cache, so reduce the number of images that you're letting people use. That's basically what I talked about earlier. If I have a not cached 1.4 gigabyte image, it takes me 20 seconds to copy that over and boot it. But it's not too long, it's not too bad, but once it's cached, it takes a second. All of a sudden, that's quite a big difference. And especially if you start looking at larger images, like Windows images that are 16, 17, right? Into the teens of gigs, that takes time to copy that data over, and it will consume your network while it's doing that. And it will also consume IO on both your controller and your compute node, right? And so that's IO that you're competing with your instances on. So the more you can cache, the more you have cache hits on your compute nodes, the better off everyone's gonna be. That's just how I measure the time. The last thing I wanna touch on for images and storage, basically there's four focus points. For storage, it's basically glance, compute, sender, and swift. So glance, you're really focused on space, as I was saying earlier, sequential read and writes. For compute, you're really gonna be focused on random IO, right? Cause that's where all of your instances are running. They're gonna be all competing for that IO time. So a few hundred IOPS across 20 instances, maybe all of a sudden not so good. So really look at random, building for random IO. It's probably Ray-10 or SSDs if you got them. Sender, really looking for performance, including network performance, cause that is iSCSI, and also density as well.  So if your head unit has a lot of cores, you wanna make sure that you're building the right density of sender disks with it. If you've got a really beefy sender node, you might be wasting a lot of your CPU resources. Also don't forget about things like interrupts, right? So if I'm on a 10 gig network, I now have to worry about how many cores my interrupts are consuming at 10 gigs if my sender nodes are being used heavily. And then for swift, swift is basically JBODs, and you're mostly worried about density there. It's not really going into any of the network considerations for swift. All right, so just some architecture examples and thoughts. These are the same ones I used last year for the most part. So one to 20 physical servers is relatively simple to build. We use a single controller, or now we have HA, so you may have two controllers. Single API endpoint, which again with HA, you may have load balance API endpoints, and you may have a single network, right? So everything's running on one network. One gigabit or two gigabit with some aggregate bonding is probably gonna be fine for that size environment. Just so you guys know, a controller to us is basically my SQL rabbit keystone. All the APIs, so Glantz, Nova, the VNC, Horizon, what else is on there, the scheduler. Basically all the processes besides Nova compute, Nova network, and Nova metadata. Everything else is basically running on the controller in our world. So network utilization, I say one or two gigabits is fine, but obviously that your workloads are gonna be completely different from everyone else's workloads. So just plan accordingly for the network throughput piece. As far as 20 to 100 servers go, it's really not probably a whole lot different. Obviously I'd recommend looking at HA controllers, load balance APIs, Swift or cloud files, right, for backend to Glantz to deal with snapshots and the more images that your users might be consuming. The major thing there is what I talked about earlier was you really might wanna look at limiting the images and the flavors that your users can consume. If everybody can upload images, you're gonna consume that space real fast. You may wanna look at availability zones to separate out hardware based on some characteristic. Availability zones though is essentially going away in grizzly, or it might still be there, the concept of cells is coming in, which is really interesting. You may also wanna consider front end and backend networks. So in sort of this model here, where basically I've got my fixed IPs on a completely different interface. So my VM to VM traffic is happening on say ETH one of my compute node, but my Nova compute talking to Rabbit, all my Nova services Glantz is that all that's happening on ETH zero, right? So I've separated out those network workloads. I do have Cinder on the same network space here, but you can have a dedicated Cinder network as well. Certainly if you have a large block storage installation, you'll probably wanna do that. As far as metrics, collecting metrics on compute nodes at this many servers, you're probably actually gonna want dedicated machines on that. We've seen it at somewhere around 40 or 50 servers that the IO for collecting all the metrics possible from a compute node starts to become pretty heavy, about 40, 50 physical servers. So some just performance considerations and bottlenecks. I think that IO is most likely gonna be your problem. Like I was saying earlier, random IO becomes quite a big deal on the compute nodes depending on how many instances you're running. You're gonna wanna try your best to reduce as much IO per instance overall. Block storage helps a lot there. So all of your major IO operations, so like databases, right, are pretty heavy. Anything that's reading a lot from disks, you'll probably wanna look at block storage. Just get the IO off your local disks and throw it in Cinder. But that does cause more networking problems. So it's certainly something worth thinking about. Review hypervisor best practices, that's the other thing. Depending on what hypervisor you're using, there's probably a best practice on how to build those images. So we chose VertIO for now, but the VHOSnet module looks pretty promising for performance considerations, right? So I would certainly make sure that you're building it correctly for your selected hypervisor. I guess I should have put that on the first slide. That's the first thing you have to figure out. What hypervisor? What hypervisor are you gonna pick? I don't know how many we're up to now. Five or six hypervisors. That's probably the first thing you should figure out when you're building one of these. Some lessons learned. Floating IPs must be associated with the flag public interface. That's been an interesting one that we've been fighting somewhat. The public interface flag sets up a number of IP tables rules. I'm gonna go into that a little bit at my Nova Network talk tomorrow. But basically your floating IPs in that network needs to be associated, needs to be available on that interface in VLAN that public interface is set to. Each piece of OpenStack has its own architecture, right? People like to show that really complicated diagram from Ken Pebble's site. It was on the images talk earlier, it was on one of the talks earlier. It's actually, OpenStack's still pretty complicated, right? Each piece has its own architecture. Swift has its completely own architecture, right? Cinder basically has its own architecture. Nova has its own architecture. So make sure you focus on all of them and not just one. Folsom is stable. Like I said, we've been running it for customers for the last five or six months. Since Essex, OpenStack's getting more and more stable. So if you're still wondering if OpenStack's stable or not, I wouldn't even question at this point. And I'm really looking forward to see what Grizzly's bringing. Migration, so either live or block works. But there are certainly situations where it doesn't work. I would suggest if at all possible don't rely on these mechanisms. I know some of the other private cloud vendors are doing some stuff to make live migration work really well. I think that comes back to the discussion on are you building traditional VMware? Are you building an elastic cloud? In an elastic cloud world, live migration shouldn't matter to you. But that's kind of a hard place to get to. So OpenStack keeps changing, obviously, right? That's why we're all here. So keep up to date on all the current projects. That would be the other thing. We're up to five or six core projects, but there's another 10 or 12 smaller projects that people are talking about pretty heavily now. So Heat and Slometer, Oslo, this triple O, OpenStack and OpenStack. There's all kinds of stuff going on now. So keep up to date with the community. And the other thing I added this real recently was don't do heterogeneous nodes. That actually means from like a network standpoint. It's actually okay from a compute standpoint because the scheduler is gonna deal with that. It's gonna put resources where you have resources. There's gonna put instances where you have resources but from a networking standpoint, I'm not sure if anybody actually is doing heterogeneous nodes, does anyone? Does anyone have their networking that looks different? Yeah, all right. So pretty much every slide here could probably be its own talk, right? You could have your own talk about networking. You could have your own talk about Glantz. You could have an entire talk about Keystone and everything else. Trying to cram it all into one is kind of difficult but certainly think about every project when you're building your private cloud. And this is pretty much it. So some operational updates from Folsom. Last year I gave a talk about an operating OpenStack. I'm not giving you one this year but there were a number of new Nova calls added. So there's like the hypervisor list, hypervisor stats. There's a number of calls that were added to Nova so that you can actually get statistics from your hypervisor about utilization and instances running there. So make sure to use that. Image types in Glantz, I talked about that earlier as well. We have new format types. The policy.json, highly recommend investigating that if you're looking at limiting API calls based on role. You may wanna look at the policy.json files. And then what's coming in Grizzly, the main things at least in my opinion are the sales concept, you know, quantum for networking. Quantum was here in Folsom but I think it's actually probably ready in Grizzly. And then better LDAP and AD support is one of the big things that we're hoping for. And that's pretty much it. So this is also a design summit. So completely open to, we have about 10 minutes left. Questions, discussions, thoughts. Anyone? Yep, I've actually wondered that myself. I haven't looked into that. I believe, I don't know, does anyone know the answer? So the question is, if you have Swift backed into Glantz, does every compute node when you're booting an instance, does the image get delivered from Swift to the compute node or does it go through the controller and get delivered by the Glantz process? Okay, in Folsom, but in Grizzly that sounds like in Grizzly it does not. Okay, so the compute host will actually pull it. Okay. So in Folsom, it sounds like it does, which is what we're talking about, but since Grizzly's been released, it's a great question. I've actually wondered that myself. I just haven't investigated it. Yep, yeah. So how do you know your utilization? How do you know ahead of time the utilization? So he's basically wondering, how do you find all the information about utilization, performance when before moving over to private, to build private cloud, right? But how do you get this from your existing world? Yeah, so it's probably a pretty traditional requirements gathering effort. So if they already have that workload somewhere, then you can obviously gather the performance of what it requires, right? So if they already, it becomes very application-centric also. So you wanna focus on one piece of that, one application and find its IOPS network throughput. If it's already running, if it's not already running, I mean that becomes a conversation with the customer, how do you, what do they think they're actually gonna be consuming? I don't think there's a magic bullet there. But obviously, if it's a workload already running, you can gather those metrics through any number of systems that exist. I just don't think there's a simple magic answer. Obviously if you're designing as like a service provider or like a public cloud model, that's a little different, right? Where you're basically saying, this is what we're gonna put out, you have to use this. That's a little different story, right? So are you building to customize for their application? Are you building to be a service provider? Which is not gonna be customized for anybody. It's just gonna be a model that you have to consume. I think that's a decision you have to make. Sorry, I didn't follow what was that. So the question is once you have the numbers, how do you build for that? I mean again, I think that's traditional architecture, right, we're still running Linux infrastructure. So if I know my X number of IOPS and I know my throughput requirements, I can certainly still build for that. That's I think pretty standard. I don't think that really changes to be honest. Now there may be performance considerations based on what like hypervisor you're using and what kind of performance you're gonna lose. How much percent of a performance are you gonna lose? But I don't think that that changes too much actually from traditional Linux architecture. So I got a couple of questions, right Eric? Okay. Yeah, so you have customers that have requirements to use different hypervisors. Is that because they have existing hypervisors or like they want Hyper-V because they have a bunch of windows and they want KVM for like free, right? So we don't run multiple hypervisors in our private clouds. I probably right now wouldn't suggest doing it, but also theoretically it can be done. I have no experience with it. I really can't say one way or another. I wouldn't recommend it though. So in our HA and these guys, couple of these guys might actually be able to answer it better, but I believe for those services that you can't run multiple of, we're restarting them on a failover, right? Is that pretty much, I don't know, Brew or Chef do you guys have a tie in on there? Yeah, we didn't use pacemaker and core sync. So we're leveraging keep live D. We can, there's a, the team that's like really worked a lot on HA is here. So if we have more questions afterwards, we can certainly, we can pick their brains if you have a question on how they're pulling that off. Where? So again, I'm not overly experienced with the VMware use case. I haven't built a VMware private cloud with OpenStack. Okay, so to use floating IPs or to not use floating IPs? Yeah. That's certainly tricky. That becomes one of those questions of do you, should you even actually try and forklift an application that's not cloud aware and put it on the cloud, right? In an elastic cloud? That I think is a million dollar question. Like that is becomes a problem that a lot of people are having right now. They're trying to do that and they're running into problems. It's like trying to do traditional HA and OpenStack like on top of OpenStack, right? You can't really do that. I don't know if there's any good fencing mechanisms for moving a floating IP. I really think that just forklifting a traditional application over and just throwing it on top of OpenStack is a bad practice. But it's certainly gonna be one that a lot of people are doing. So, absolutely. Yeah, absolutely. That was a two to one oversubscription.  So, since that's a flag and a process restart, it's pretty simple to increase it later. We start at two to one and we don't oversubscribe memory currently. If customer wanted four to one, eight to one, 12 to one, I mean, we could certainly increase it for them. We want them to establish their workloads and then look at utilization and bump it up from there. More questions here. No. I think that RAM is, I think it's RAM or disk space, to be honest. What's that? Disk IO could certainly be, it certainly can be a problem. I actually think it's a bigger issue than RAM or disk space as far as performance goes. I would probably agree with you. RAM, when you boil it down, is really gonna be your kind of limited to that amount of RAM. Certainly, VCPUs can be over committed a lot easier, right? That's a pretty easy process to deal with, but RAM is pretty much a gaining factor. I would agree with that. It depends on what you're trying to accomplish, right? So through, if you have very large, so he's asking about network performance, is it more latency focused or is it more throughput focused? Again, things don't really change from a traditional architecture there. If I'm storing stuff in like Rackspace cloud files, I now have a latency problem, right? I also have a throughput problem, but it's not gonna be nearly as fast as my local disks a hop away, right? I'm now going to a public cloud provider, and so it's gonna naturally be a lot slower, but I have infinite amount of space I can use. If I start thinking about instance-to-instance communication, latency might become an issue, but throughput is certainly gonna be a concern, because now that's a traditional virtualization problem. If I've got 10 VMs running on a hypervisor and a one gigabit pipe, that's all I'm gonna get out of it, right? I'll never get any more. So again, I don't think that changes too much from the traditional virtualization model. So I would say that actually a lot of building an open-stack cloud doesn't differ that too far from a traditional model, right? At the infrastructure layer, but there are things that you have to account for, which are like glance, and Swift is a different animal as well. I would argue that it's not too far different, right? Right. So yeah, so he brings up the shared storage piece, but I would argue that a lot of people in here are probably using shared storage for their instances. So my thoughts on that are that you should really be focused on building elastic nature and not dealing with shared storage ever, but there's certainly a lot of people who build it that way. So that kind of touches back to my first point of is you kind of need to make a decision. Are you building traditional virtualization or you're trying to build for elastic nature? There was a question over here. So the question is basically if I have multiple data centers right geographically separated and then like performance of glance copying between one or the other, I would probably actually put my glance images in a public cloud provider and then use the URL and ask the systems to pull down the glance images would probably be the model I would go instead of storing them locally or at least in Grizzly as we learned earlier, right? In Folsom you might not have the option. I didn't talk on that. In glance, you don't actually have to have a file backed. You can actually store a URL location of an image. So you could have the image could be sitting on someone, Ubuntu's website, right? Or the image could be in a private container or a container in cloud files. You don't actually have to store the image locally but obviously going out and making that request is gonna take additional time, right? So that becomes like a convenience factor over speed, right? I would say strive for less images and standardized if possible but certainly as one of the questions brought up earlier people are trying to move workloads over and not thinking about it from the ground up, right? How do I stack this instance versus just having an image that is like this very important, you know, my one specific application image, right? That's the, those are the questions that people keep having. It's hard to force a business to try and move, right? I get that but I think you wanna try, though, yeah. That's pretty much time, I believe, is that correct? I'll be, yeah, I'll be around. There's a number of other private cloud guys in the room from Rackspace. Be glad to answer any questions you guys have.


Hey everybody, it's Hari Swaminathan from optiontiger.com. We are looking at the SPX action for Tuesday, August 13th and Tuesday was a news-based event because the tariffs on some Chinese goods were postponed till December and that news did not come out before the market. It came out right after the markets opened. In fact, you're looking at a five day, five minute here and it came out at the 935-940 level eastern time and you can see immediately the market started to go up. So obviously in general, you don't take a trade at the open. However, this is a trade that is driven by momentum and news and as you can see the ticks just remain in positive all the way till here until this second red dot you could have been in. So this would have been about a 40-45 point move on the S&P even if you took it on the third bar which was here say somewhere in the middle the SPX was at 2893 and you would write it because all these single dots you don't get faded. In fact, one of these single red dots is actually a green bar. So you can see that you won't get faded by that and this one is a red bar. However, it's only one dot and so you continue to stay in the trade until you see two red dots which would be this bar right here and that is 2936. So a good 40-45 points on the S&P. So this would have been about a half an hour to 40-minute trade and this would have been by itself a $10,000 trade and then of course the market just remained at those levels. Yes, they were probably smaller trades here but once you have a trade like this, that's the trade for the day and this would have been a $10,000 trade just on a five contract position. So the point is when you see these kind of things, if you just follow the rules, the custom RSI was obviously in the bullish zone and you don't see two red dots so you don't get out of the trade even though there's some choppiness right around here. As you can see the dots on this red, it's actually a green dot on this red bar and also it just continues higher from there. Even this one is a green dot and so the ticks are actually increasing there and so all the way till here and then once you see the two red dots you would exit right at this bar right here on the second red dot you would have exited but that would have been good for 40-45 points on the SPX and that's how it would have made about $10,000. Now granted there were other smaller trades perhaps but once you have a trade like this your day is done. Thanks. The SPX ticks as well as the custom RSI are custom indicators and algos. If you have any questions you can go to this bit.ly link bit.ly slash SPX algo and you can find more information on how to get these indicators. Thank you.


Last month, Apple announced the biggest security upgrade to iMessage, probably since the app's creation, PQ3, a post-quantum cryptographic protocol, which will be used in Apple's default messaging application once you've updated your system to iOS 17.4, macOS 14.4, or WatchOS 10.4. So in case you didn't know, quantum computers are able to run algorithms that are capable of breaking public key cryptography schemes like RSA and even ECDH much, much faster than classical computers. Because quantum computers are still fairly new and quantum resistant encryption is even newer, most software companies have yet to add updated encryption protocols to their software as we're going to see in a second. But I honestly think that this is a bigger and more imminent threat, you know, quantum computers breaking encryption than some people realize, especially in regards to governments or even corporate adversaries that have the ability to archive large amounts of encrypted data that are flowing through the internet. This is something that the NSA in particular are doing right now. They're storing the messages and waiting for a time when they do have a quantum computer to start decrypting them. Now you might be wondering with PQ3 what this 3 stands for. Obviously the PQ stands for post-quantum, so could this be Apple's third iteration of post-quantum encryption? You'd think that we would have heard about the other two, but no, that's not what this is. The three actually stands for level three security because Apple went ahead and invented this metric for measuring how good your encryption is, this level by level security chart, which of course they put themselves at the top of. So down here at level zero, we have no end to end encryption by default. So this includes QQ, Skype, Telegram, and WeChat. Now the key word here is by default, and of course also end to end, I'm sure all these apps here have server side encryption, but not necessarily end to end encryption. So with Telegram, for example, they don't have end to end by default or at least the only chats that I know of that have end to end encryption by default are the secret chats. But for everything else, unless you go in and change a setting, it's just server side encryption. Then level one is where we get apps that do actually have end to end encryption enabled by default. You don't have to change any settings to get it. But of course, no post-quantum encryption. And notice here in level one that Signal and iMessage both say previous next to them because of course Signal recently added post-quantum encryption to their app, and they actually did it before iMessage ever did, which hopefully this post-quantum encryption that Signal added is going to make its way into some of these other apps further down the line as well since of course Signal is open source. Any of these other apps could probably integrate it into their software as well. WhatsApp in particular should really be adopting this very soon because WhatsApp pretty much started off just as a proprietary fork of Signal. And then over here at level three, Apple is saying that their new iMessage with PQ3 has the PQC key establishment plus ongoing PQC rekeying. So they're not just using one post-quantum key to encrypt your entire conversation, they're rotating the keys. And they're also doing so in a post-quantum way. So even if somebody managed to break your encryption or if they managed to get one of your post-quantum private keys for that encryption, then they're only going to be able to decrypt part of the conversation until a new key is established, which I think with this PQ3 encryption, Apple rotates the keys about every 50 messages or so. It kind of varies because to reestablish that key the way that Apple did it, there's a lot of overhead. I think it's about two kilobytes or so to send those keys, which if you think about it, that's a lot compared to like a short text message, right? Like if you want to send a short text message and it just so happens to be when a key needs to be reestablished, it's going to end up being a whole lot bigger. And then we've got a little bit more explanation about this leveling explained here in the blog post. At level two, the application of post-quantum cryptography is limited to the initial key establishment providing quantum security only if the conversation key material is never compromised. But today's sophisticated adversaries already have incentives to compromise encryption keys because doing so gives them the ability to decrypt messages protected by those keys for as long as the keys don't change. To best protect end-to-end encrypted messaging, the post-quantum keys need to change on an ongoing basis to place an upper bound on how much of a conversation can be exposed by a single point in time key compromise both now and with future quantum computers. Therefore, we believe messaging protocols should go even further and attain level three security where post-quantum cryptography is used to secure both the initial key establishment and the ongoing message exchange with the ability to rapidly and automatically restore the cryptographic security of a conversation even if a key becomes compromised. Now I'm very glad that Apple is adding better encryption to their messaging app and joining the post-quantum bandwagon pushing the rest of these companies that don't have it to do the same. This blog post really reeks of marketing and Apple trying to steal the post-quantum secure thunder from Signal. In fact, if you read through this entire blog post, they mention Signal a number of times, five times that they're talking about Signal, which is kind of funny because if we go back to this chart here, Signal is nowhere near the most popular chat app in terms of downloads and a number of people using it. I mean, maybe they're more popular than Line or Viber. I don't really know too much about those particular apps, but Skype, QQ, Telegram, WeChat, of course, iMessage all have probably an order of magnitude more downloads than Signal, so it kind of makes you wonder why is Apple so threatened by Signal? My theory about that is because they were really the first ones to do the post-quantum encryption in their application. Or at least they were the first, I guess, widely used app to have post-quantum encryption and so Apple wants to split hairs here and try to make themselves stand out more than Signal. But the amount of security that you actually get here going from Level 2 to Level 3 or more specifically going from Signal with PQXDH to iMessage with PQ3 is nowhere near as significant as Apple would want you to believe. So this re-keying that Apple is talking about is more commonly referred to as forward secrecy. This is actually a feature that Signal has provided via the Double Ratchet algorithm. In fact, Signal has had this feature in their app for over 10 years. Double Ratchet was partially developed by Moxie Marlin Spike, who was the former CEO of Signal. Signal's encryption algorithm with this forward secrecy was open source and copied by other messaging applications. But more importantly, it's still being used alongside Signal's post-quantum encryption algorithm. So Signal actually did have post-quantum encryption with re-keying that key renewal months before Apple did. And almost everything else about Apple's PQ3 encryption is the same as Signal's that they implemented months before. They both use the PQ encryption in addition to ECDH. They both use crystal kyber as their post-quantum encryption algorithm and they both have forward secrecy as I already explained. The only real difference here is that PQ3 actually uses a post-quantum secure algorithm as part of the ratcheting that's being used for the key renewal. So in theory, yes, Apple's post-quantum encryption in iMessage is technically more secure than Signal's if you just pay attention to that part. In fact, I would say it probably really is more secure than Signal because after all, Apple paid a bunch of fancy German scientists and professors to review the encryption and make sure it was super-duper uber secure before releasing it in their software updates. But even though iMessage is technically more secure than Signal, it's still absolutely proprietary and so it isn't at all the most practical app for securing yourself against the so-called very strong adversaries who can corrupt parties or possess quantum computers and therefore defeat classical cryptography. Secure messaging applications are just one of many opsec tools that you would use depending on your threat model and if your threat model involves an adversary with enough resources to corrupt parties and use quantum computers against you, then it's pretty safe to say that we're talking about a government or a big global tech company like Apple. And I really doubt that this kind of adversary would go straight to throwing their quantum computers at your stored encrypted messages that they have saved in their billion-dollar Utah data centers. They're not going to go right for brute forcing you. An adversary like this would probably try to target the platform that you're using with something like Pegasus spyware. That's literally how these kinds of adversaries targeted iPhone users in the past and of course if you're able to own the device then you can own all the messages being sent from the device. So a global adversary is going to focus their research on targeting iPhone or macOS platforms directly. They don't have to worry about whether you're using Linux, BSD, CubesOS or anything else besides an Apple device because iMessage won't run on those devices. In fact, since this adversary knows that you're going to be locked into Apple hardware and Apple operating systems, they might just go ahead and target Apple themselves directly to deploy a supply chain attack. Something like that is not going to be off the table with global threat actors and because iMessage, iOS and everything else that Apple makes as closed source, you wouldn't even know if a corrupted iMessage or iOS update was pushed to your device for that adversary to be able to read your messages. A much more important and fundamental privacy consideration both now and in the future when quantum computers that can break classical encryption actually exist is going to be having open source algorithms in open source messaging software. That way you don't have to just trust Apple and their fancy German scientists to make sure that their post-quantum encryption is really secure. You can go and verify that software for yourself. It doesn't matter how fancy the post-quantum key exchange is when you, the end user, have no real control over those cryptographic keys or even the device that's generating them. So don't fall into the trap of believing PQ3 iMessage is a secure and private messaging app. Sure, the encryption protocols that it's using are built like an iron fortress, but that fortress is built upon weak proprietary sand that can get pulled from under you whenever Apple or a third party that might corrupt them chooses to do so. If you enjoyed this video, please like and share it to hack the algorithm and check out my online store based.when where you can buy awesome merch like the tie-dye tour tee or little daemon hoodie and you can automatically save 10% of checkout on your entire order when paying in Monero XMR. Have a great day.


Hi, today I wanted to try out Ubuntu 21.4 because the last time I tried Ubuntu, it was using Unity So a long time ago. So first of all, let me say that I think that at this point pretty much any distribution popular distribution as a very clean and good UI by default which is what really interests me because that's what I do at KDE and I think personally I always got a disabled icons and But I'm impressed by the fact that all these options are like instant apply That's not the case in Plasma. So I'm not used to that, but it's really good then one thing that immediately I Immediately noticed and I really loved the design choice was to use a terminal That's slightly purple in the background. That is Almost like it's transparent given the background, but it's not transparent It's just tinted, but I think it's really pretty I really like it and the sidebar also takes a bit of color from the background So I really like that design choice as well So let me actually go through all of the applications that we have here as an example. I've seen that we have a 2D application, but let me just say that the Mines icon is just beautiful Like I've given a look to all of them and I found this one just to be The best one. I love this icon But anyway, the 2D application because I am a big fan of getting organized so We've got Personal to-dos and I can add my own. I can even choose a color. That's pretty Simple yet effective color picker and What can I do with those? Can I I can rearrange them and I can even take notes on them and of course set a due date and One very if I can also organize them in like Subtas, yes seems like I can do that makes sense and One thing that I really wish to do application at is the possibility to add Template task with like some notes in it that I can just copy paste when necessary Can I copy paste these things? I don't think so but Yeah, I mean it's are pretty simple to do application I still think that the best application to the application I found is the tasks.org for Android because that one is just Amazing and then we can also give a look to Firefox and LibreOffice. I think you all know those applications. So I'll just skip them and Let's go with something like shot for for Images which I don't have any so that's a bit of a pity so let's download example one and Also, let me say that I really like the fact that you can drag the windows in the virtual desktops Of course, you can also do that in plasma, but it's not as simple in the straightforward like in this case You just have them out of the box. Whereas in plasma you have to at least configure them Depends on the distro, but anyway, let's start. Let's find a test image To give a look at Shot for so let's download this one And I could have picked a better test images than just a big text with test, but That's what I got. So let's save it nice and let's Open it Reset the downloads index and I can't so did I completely miss the Point of short one Please okay. No, here's my image and what can I do with this image? So let's see Edit the image then there's not much I can actually do due to Edit it I can rotate it flip it Crop okay on the normal stuff Yeah, this looks about the same. I actually have like an ounce stuff. What's an ounce? Okay, this one I can actually see working Of course, it won't do much on this test image, but Announce Okay, and answer actually chooses Profile automatically I guess makes sense and then I have all of this stuff It's okay The design I think lacks a bit like there is a menu bar could be inside a header bar I think that would be an improvement and I keep on pressing the meta button to see all application, but it is this button We also have what do you have here just a couple of them, but there's also a video application and Well, is this the same one as see? Yes, this is the same one as GNOME So I can actually see channels. I think this is like super impressive I'm still like very impressed by Being able to play this stuff I'm afraid that the software center is broken for me I don't know why but if I try to start it, I just get a node application that I found so we'll skip that over and Actually, let me give a look to the settings and in the settings we have At the top this appearance Button with the ability to switch to a fully dark or full fully light team Which is very nice. It's not in a GNOME, but I kind of wish it was because switching the color scheme of the application I think it's a basic operation that most user would like to have an option to do and Actually, if I think of plasma we've had for Many years the light and dark options, but we never had this combination of dark and then light but with the latest Version we can kind of have something like that light version for the application and a dark version for all of the rest of stuff so like this and Instead for like the top bar dark dot top bar and then white content We might be able to do this to do this in the short future, but we'll see With the introduction of the tools area. It's much easier and then we have all of the usual stuff online accounts is something that impressed me because that's It's much better than the system settings KDA system settings. Sorry counterpart So let's actually try to log in with Google. Let's see what this gives me Do I remember my password? I think it's this one. Yes, I got it right Let's see if it actually synchronizes correctly with a bit of time, but I Actually have a bit of a slow Okay, so emails Google Drive makes sense and then also calendar. Let's see if it all works out of the box So let's pick an easy password. This is not my daily usage Okay, it works used for me calendar and so on. Okay, I actually do this. Let's try to open up my drive It's really I like the design simplicity of the file application. There's all the option in the Year, but the design is pretty clear. So can I actually get to my drive? Probably should be somewhere, but it's not here as far as I can see So what else do we have here? We've got emails. Do we have a mail application in the list? That yes, we have a Thunderbird. I don't know if it Synchronizes automatically with the Google accounts from here. I'll guess we can find out. I Don't think it does Let's see how much time it takes to set this. I actually don't use like Yes, I Don't use Thunderbird. So But I mean I can try out if it works Let's see. I Did I have to log in again? So it's there's not like synchronization from is online in accounts and Thunderbird, but I did expect that Is there any other mail application? I don't think so. Let's see No Okay, so this is my inbox. Let's see if it can actually fetch my emails and I would say so so before you get Too much private information out of that. Let's close it and see What about The calendar do we have a calendar application in here somewhere a calendar? Yeah, straight up and We do have events. Let's see in the settings if I can Online accounts. Yes, this one So is this one like already synchronized that would be impressive. So let's try to add an event Random event. I don't actually use Google events. So I need to create a new one and check if it's actually synchronized So let's go to Google.com I bet I need to log in again Okay, and we call up in a randy And my password is this one Yep Okay, so today's I set it on the sixth. So let's go to the sixth Do we have any event on the sixth? We don't well, maybe I did not create this random event on my calendar I don't have any option for that. Let's try to see if I can add it like on the not the sixth the seventh and then test two See if it synchronizes in my calendar here maybe not immediately but Like upon restart, I don't know calendar Oh, but anyway something that I noticed About the search is that I can actually search something like heart and I get characters It's pretty cool and very much useful So let's see if there's any option here that I missed But I don't think so. Maybe it just takes a bit of time I do see that a pasqua and lunedio pasquita. Oh, there's also gold status, which is totally from my calendar meaning that it's actually synchronized and Maybe it's not like Instant is synchronized, but it is synchronized. That's enough for me So what else do we have? I'll say that that's pretty much it from this one and then if we go to the list of apps I did not check out I've actually used cheese for a long time. So I know what it looks like But we have rhythm box which again, I've only used before on like unity long time ago long time no see and We are actually have the possibilities podcasts and radio Can I actually start something yet? It works. I'm not sure like How this works, but I'm just not very used to it for this one's and to log in makes sense and well, I don't have any music in my music folder, but I Trust that it would work. Is there any option we have a preferences? Oh, we actually have some options a decent amount not a kitty standard amount Which is crazy, but we do have some some options then what else So startup application was this Okay, makes sense startup programs Then we have a text editor which I'll guess is G-added. Yes, and again what really impresses me most of G-added is how well it's like Used to touch. I can actually use my touch screen very nicely. I've already said said this in the GNOME video and then what else We have live patch, which I don't know what that is Remina What a weird icon. Okay. It's a remote desktop Okay, thank you for the information and Then there is Sudoku and mine selects actually try out mines just because I love that icon. Sorry eight by eight and I can start playing nicely like this This is one this one Oops I've actually never learned how to play mines like seriously. It's never been a game that There's a utilities folder. I actually love utilities because that's where you must recognize the design design language of the us you're in Like in this example One thing that bothers me a bit is that all of the buttons have this outline and It's almost like you have a double outline because you have the end of the five button and then the beginning of the six button and That's a bit too much like it would be much Prettier to just have a single line, but that's neat picking which I shouldn't do and checking out other software Okay, can I actually do scientific calculator with that? What does that mean? Engineering I don't see any difference I thought because I have to click here advanced mode, okay financial mode That looks useful and then programming mode. Oh, I can actually go around and play with All of the bitwise operations. That's Impressive, I Wish I knew about this when I was actually, you know working with bitwise stuff keyboard mode Yep, this is very much compact. I like it and then what else do we have that was actually pretty powerful for a simple calculator application Usually I see stuff that does much less than that System monitor Okay It's very similar to the old cases. I still think that the new system system manager by Katie is like the best But that's I'm biased. I'm totally biased and then document viewer and I'm very much interested in seeing what it looks like. So I'll go ahead and download Test PDF, so let's actually go With I don't know a random PDF that I'll find over the web. Let's download it Let's put it in the download folder. I Actually have my calculus one exam this June I Think I'll need to retake it a couple of times to like September or something like that so wish me good luck and Firefox got struck nice. I actually have like two dialogues this one and this one at the same time. That's weird In this a bug save file. Yes save file Okay We've got a file now. Let's open it and It actually was downloaded two times. Okay, I think I've found a bug here And then that's pretty simple. We have the outline and Chapters the pages and Annotation can I add an ad not an annotation? So night mode, I like it To a ocular I have night mode. I don't know Out pages left rotate. I don't see anything about and ah, there's a button here. Okay, no text like this Hello Okay, you can close it and then it shows up here make sense Can I also highlight text so like this? That's this also show up. Yes, and I also can see who's the user that actually Took the annotation. I wish that all PDF viewers had an option to I Can't zoom in again. Sorry It crashed So as I was saying I wish that all PDF viewers had an option to actually hand write notes because that's extremely useful, but That may come in the future ocular as it but it's a bit I don't know. I think that external plus-plus is the application that right now Does it best? So let's get back to utilities and then there's Characters fonts. Yes, this is pretty much utility stuff screenshot Again, same one as you know Very pretty one. I like it. I Still have my crushed PDF viewer in here. Let's try to kill this one. What's the name again? What's the name if you have this big of a toolbar you could show like Deplication name or the file name Okay for squid. Thank you Because I get that most application like I have some buttons so they cannot display Deplication name or stuff like that, but when the space is there or you could just as well use it So, let's let me see Videos yeah, I think I pretty much so everything that interested me maybe just like Documents corner what it is like. Yeah, I Don't have actually a scanner like with me. It's in the other room, but I'll trust that this one works and Wow Okay, it took a bit to close but I Won't say it crushed it stayed open and just took a bit of time to close and And This is interesting. So when I try to drag an icon I get a green outline that shows The like limits of the desktop. That's interesting. I wonder what's the practical use case use case for it and Then think that's pretty much it. Is there anything missing? Well, I can do the same test I've done in Fedora, which is to actually try to install Which is to actually try to install a cute application and see how it looks like because oh Come on dolphin the file manager nothing What about ocular do you have it? I'm pretty sure we put it in the snap store There is it. Okay, let's try to install this one because something that we care about in Katie is to make JTK application feel native and follow the theme. So, you know, it's a goal It's part of the consistency goal so that's quite important and I always wonder if other You know distribution or these are doing the same and In this case the store application is a bit broken for me because It shows the installing and then just Tells me that it's already installing it So, okay, I guess So I can actually follow Uh, how they install is going by pressing install many times. Okay and meanwhile We can give a last look to The UI of this Well, it's actually pretty simple to create folders now. It was not as simple back then now. It's pretty good and No, I named folder. Let's actually try to give it a name. So test. Okay Did it work? Yes, that's neat What else do we have here? Can we like make folders of what happens if we drag a folder? Why do I keep getting Pushed to the bottom When I do a new folder. I think I found another bug So what happens if you drag a folder on a folder? Nothing makes sense You don't want to deal with recursive like folders And meanwhile ocular is at 60% so We've got I can actually I actually have the microphone volume Very handy. I like it and I did not think that Gnomor, I don't know You're going to have this because it is not there unless you plug in the microphone So you cannot actually I customize the volume of the internal internal microphone, but Now that I've I've got it. It works Then let me um brightness the wi-fi bluetooth is on we can actually turn it off I kind of wish it stayed open like If I press turn wait Bluetooth is off turn off this one should be on Okay another bug but you mean that If uh, I don't know ubuntu or gnomor reviewer did a review of plasma and just Try to find many bugs. I think they would have a easy time, but Don't worry at me saying.  So let me plug that in meanwhile ocular is that 99% we're almost there Now we should be plugged in. Okay power settings We can we ah, we've got the power mode. This is very nice to have I think that plasma will get this uh soon So it's very nice to see that uh gnome or ubuntu as it already. I think it's gnome here I remember what it was announced a bit back then and then what What I kind of wish we had is the graph of charge Over time a bit like android and It cut back to 14 We'll never be able to install ocular. Are we? Let's try with terminal As they don't use a apt match anymore, right? So I have to like do This thing It's already installing. Yes, I've seen it, but it's not installing very effectively Let's try to cancel this one Did it work? Nope Okay, now it's stuck on actually installing this thing Okay, I can actually try to install something completely different. What's another uh guen view? Uh guen view. Can I actually try to install something else? Maybe that one will work And I have this time I'll do it from console because it's actually called terminal here I'll do it from terminal to make sure that It works And it will only take another 20 minutes Amazing So Yeah, this one is totally stuck Let's close it anyway And let's also close this one So I'll actually pose post recording until I actually managed to get a qml application In here not qm. Sorry cute application in here Also, I was trying to see what other desktop backgrounds look like and It's very nice to see he posts everywhere And the left sidebar is transparent and picks up the background, but I'm a bit sad to see that This power polish is outcoded. I kind of wish that it took like the main color of the background, which is Actually kind of easy to do there are many libraries to do that. So if you could just do pick the Dominant color like in this case, it would probably be this yellowish Although I gotta say that this out of focus image is probably not something that I would use for a background And then there's this Grish one makes sense and again purple on grayish Okay, I Used a better network. So we can see that in 13 seconds instead of 13 minutes will have our Gwenn view which we're able to test out and the mean Take away from This section of the video is that I need to buy a new internet connection or something like that because The difference between 13 seconds and 13 minutes is astonishing I did not expect such a difference So let's actually try to see what Gwenn view looks like Okay, so let's try to see Gwenn view the the icon of Gwenn view is the old one but I think the fault here is on the Gwenn view side because I think that's like the Gwenn view icon and then we Predify it a bit on plasma by using Um The breeze icon for Gwenn view which I think looks a bit better So we need to connect the snap From this one. So let's Do what I have been asked to let's install this thing which will only take five more minutes Okay, but I need to Let's connect to the faster internet. So we'll see those five minutes Turn into five seconds Let's see. Okay, let's try again And then we can see that It is one minute. Okay So a ratio of one to five this time. So let's see if this works Okay, I'm afraid I could not install Gwenn view because other problems. So I'll just give up for now It's a bit sad that it didn't like work nicely out of the box, but I hope that it's just my installation that on a proper install it will work nicely So that's pretty much all for now. I really like Ubuntu 21.4 and I hope that like the next version with Gnome 40 will be just super awesome


Well, with all the holiday season coming to a close last night, many people are not preparing to take down their decorations on this week's Northwoods adventure. Anthony Scott brings us to Adina, where one man has his work cut out for him when it comes to taking down the Christmas lights. People always ask me what my electrical bill is. I haven't even told my wife. And it's probably a good thing that GP Anderson's wife does not know the electrical bill, as Christmas lights illuminate Southwest Third Street in Wadena every year. Anderson got the idea for his Christmas in Wadena while watching a Super Bowl commercial in 2006, and the lights have just gotten bigger and bigger each year. Two years it took to create it, and first I had upwards of 15 minutes of songs, and now I'm up to two hours of songs, and I'm just creating with more and more morphs and more technology. During the last few weeks of December, cars park outside 414 3rd Street Southwest in Wadena and tune their radios to 88.1 FM to listen to the music that goes along with the show. They can listen to all the music in the warm comfort of the car, so you don't hear any music outside. All you hear is cars running. People don't parallel park. They all come in and they're back in because we need that for the amount of people that can park here, so we can get upwards of about 75 people around here. The finished product at Christmas in Wadena is a sight to behold, but the work that goes into it is not taken for granted. Three miles of extension cars, there's 47 computers, there's a mile of catfly cable all here drawing it, so it's called an animated display because you can see it's quite animated. You don't buy any of this stuff. Everything you see I have to make and I have to program. And they have to bring out the heavy machinery for the centerpiece of the display. This big mega reef behind me, it's 1,100 pounds, has 22,000 feet of garland on it, 27,000 lights, we get a crane to lift it in an hour. So what do the neighbors think about all the lights on their street? My neighbors have been all receptive to it because, you know, this is the 11th year, raised $14,000 for Project Chair of Wadena County, upwards of 4,000 pounds, so you and I are worrying about eating tonight afternoon, but there's people that certainly have a genuine need. Southwest 3rd Street in Wadena is transformed into a movie scene every Christmas, and it doesn't matter how many times you come, you always notice something new. There's just cute little elements throughout there that's not full-blowned.  Reporting from Wadena for this week's Northwoods Adventure, Anthony Scott, Lakeland News. The final show of the season was tonight, but Christmas in Wadena will be back next December. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Hey everyone, Paul from PaulGoes. Welcome to League 1. So we're set to go here on the draw, terrible hand, we're obviously going to be throwing away. Oh dear. Oh dear. Might not be the most glamorous of games at the beginning. With 8 rack though, lands are at a premium and obviously drawing a Ravens crime is a really big out to this particular scenario that we're in. The rack is actually quite poor here. It's better than a land, but it's not actually that great. So I'm going to be greedy, put it on the bottom.  Ooh, hello. C-dryno type deal. Oh it does just run removable. I'm pretty happy overall that we are up against this particular deck actually. I don't know if we'll win game 1. Do much here. Alright, I think we just have to take this in that case. Path on end of turn. We know it's Resto, so I'm going to go ahead and get in. What does it do? Put a... You put C-dryno into his hand. Okay. Oh, thank you. I'll have one of them. Should I go for Resto here? I'll take the Rhino. Oh, okay. So he... I'm just not sure. There's two damage. I think I need to go for it. I need to go helpful over here. So he can go back up to 9, drops me to 3. And then he just plays it out again. Restoration Angel. I could top deck a discard spell though. I'll try and do better in game 2. I think I do like Layline of the Void. So it's 5 cards I'm interested in bringing in. I can't really think what I want to take out though. I think the deck more or less is configured the way I want it to be configured. So for those of you who've seen the other videos, I'm a going first guy. So we'll see if that ends up being... this is embarrassing. What happened there? Yeah, that's cool. Alright, this is what it is. I still arrogantly think I'm... despite these tragic errors that... like I'm still a decent shout at this when he's got 6 in hand. So I suppose lingering souls, yeah, definitely. It's looking very unlikely we'll be able to recover from this now. I know, there's just no way. That's so embarrassing. I'll stop beating myself up. Sometimes you make mistakes. Well, what am I going to do here, Lily? We're dead, we're dead. 5 plus 7 is 12. We left on... yeah, there's no way we can win this game. Alright, sorry again folks. Let's just pick it up in game 2 or match 2. On the draw, this is a keep. Concentration. Which elf? Oh, this is a tough decision. We can either dismember him or we can inquisition. I think it's inquisition here. In case his hand is bad. In which case, wrench mind makes massive, massive inroads and his hand is bad. So it's Arbor Elf here. Oh jeez, yeah, okay. So there goes a bird, so those are the two cards in his hand. So there you go. So, he hasn't.  If this is right or not, I'd love to get Bob down to try and find that land, but I just want to ride this pin that we have on him. He's missed. He has missed. That's interesting. What card could he possibly want more that he can't cast? I kind of want to keep the second copy of Lily. He deserves land. Come on now, even I as your opponent. I think that that's fair. Here she is. Okay. Stone reigns okay for us. It's not too bad. We can trade. We could... So one thing we could do here is let this connect. Then on our turn, use the remaining loyalty to destroy the elf. Replay the next Lily instead of trading out the thing. And I'm thinking that that's correct. Waste his resources. I'm going to always yield to Bob. Kiss that goodbye. That's easy to mess this up. Once you've degenerated, what was that? A land and he just played it? Plays a forest. Yeah. This is just where he's so powerful. He's so, so good. Very hard for us to lose this game now. You know, he's so good when you get to this point in the game. Like he pulls their arm over. It's really, really good stuff. Drop an inquisition. So I don't want to go ban smallpox. It's just I really want to minimise the chance of having two in hand. I want absolutely one at most in the course of the first, say, 10 or 11 cards. Against this guy. Good hand. Yep. This is just your classic jump line. Peer and Kieran's fairly terrible for us. We don't particularly want Peer and Kieran to happen. That's a really problematic card. Taking stone rain here. I've got to pray for another thought seize. This is our only chance to get it. So I'm going to take it and let him stone rain. This is okay. It's not super amazing. But maybe I should have played around stone rain on your moth, by the way. That's a thing. I think I think about. Oh goodness. Okay. Yeah. Maybe I should be hitting the elf before he gets to. Oh my goodness. Now we're just absolutely dead. Okay. Yep. Thought he's interesting. I'm not even sure if this is optimal or not. It's just, I've got no hope of winning now. So 3-2. Been testing in the last week or so. This and other just modern decks. I keep having to fight this same opponent over and over. Okay. Not bad. Not great. I don't want to really cast Raven's Crime now. It should normally be a no-no. But yeah. I'm not going to cast Raven's Crime now. Good. That is exactly what we want. Yep. Alright. This is a pretty good spot for us to be in. Happy to go down to two lands here. Opportunities online. Stone rain is not good enough. Very big trouble. Good game. Okay. So. Sometimes I like to go back and watch replays of my games and all my matches and stuff. But yeah. Again. Him going first and getting that momentum in game two seemed so good for him. So. Yeah. I'm increasingly convinced that it's... Maybe it's just against that matchup that it's a thing that going first is right. But. I'd love to play yug-yug again. I have a funny feeling that was a good matchup for us too. It certainly looks good. Ooh. High stakes hand. So spreading seas is a disaster for us. This is a really all-in sort of hand. Yeah. We'll keep. We'll be brave. Certainly not going to mulligan it. This is quite popular at the moment. Maybe the proclamation of rebirth version. He's probably going to draw another dork. So. I'll take a martyr. That's fair enough. That's exactly what he should be doing. I think this is okay. I'm going to force him to activate. I think that's his hand. Okay. Go ahead. I can't stop that. I pay four life so that you can gain nine. Trust me. I'm building up to something here people. I don't do much yet. That's cool. Ranger danger. Taking him. Yeah. I'm cool with this. If you want to path this, it's totally fine. Very satisfying. That's totally fine. Wow. Dude playing a bit mill. Blue black mill. Before I started recording the videos. And yeah. Like good on you. You know. Consider ultimating. Even when. You know. We won't have an ability to. Force a sacrifice. I have to decide. That's going to be an interesting decision to make next turn. I think they go in his hand. Right. They don't come out onto the field. Back out again. Two martyrs. Why? Why dude? Do that. He suitably ages away from. Oh ghost quarter. Yeah. That was a good play after all. Ghost quarter was threatening to. Open up a clear path to. To Lilliana. So now he can attack. He can ghost quarter. Two of my mutavolts. But. Oh and he can field the third one. Yeah. Okay. All right. I'm cool with this. I still think it was correct to plus there. That was a mistake he made. In retrospect. Maybe it was a mistake I made. As well though. He'll be annoyed with himself there. I know I do. But there's nothing I can do about that. That's just mean. Which really isn't good. I think now is the right time to ultimate. You can either have ghostly prison. And a. Land. This is fine. I mean it. You know if he plays a card that doesn't gain life. He dies. So. Okay. So. Oh geez. Um. And. Normally I don't panic too much against Leyline. I. You know. Smallpox and Liliana. They're both very strong at just drawing. You're clear of Leyline. Yeah. If it does pull off a Serra Ascendant. A 30 life fatal or get us there. Just remember won't. The only other thing this member hits is. Ranger of Eos. Against Leyline. 25 seconds left here. Ranting and rambling. I'm going to keep two bobs. I'm going to drop a smallpox. That's going to do it. Interesting. Bob and Bond too. Okay. I'm going to keep. Maybe a little bit greedy. Probably don't need to be greedy.  Thoughts these turn one. It's so sweet. I don't want a smallpox. Yeah. It's got to be squadron. So the big thing with squadron of course is. Squadron Hawk. Comes into play and allows him to put three copies of itself in his hand. Which is a massive, massive problem. It's like it's it's worse than. Ancestral visions. It's it's horrendous. It's exactly what it's going to do. Okay. Yeah. So land is at a massive premium for us in our hand. The particular hand that we have. Raven's crime wants to discard them. Smallpox wants to destroy them. And Liliana also requires three of them to be on the battlefield. So is Bond too. So we are begging for land basically. So trading Bob for a card and a free land is great. Corefire walk is not very useful. Here. This is fine. And ghost quarter. Right. So he still has o-ring in hand. On that basis do I want to make him pitch it? It's like it's annoying that we had to. Yeah. That's cool. Oh, mate. What is that? Don't play the card.  It feels a bit harsh. So I don't want to be too cocky here or whatever about how fantastic my deck is. My strategy's been, he's clearly a new player who's just coming into the format. Is there any reason to not- So I really can't see Bond too mattering now. Probably has the right answer with all this. Good game, my man. Good game. I think we're ready to go. Join match. We will keep. And this is a very tough match for us. Yeah. Oh. Oh, okay. So it's John. It's just normal John, which is actually quite good for us. So his Liliana is worse than our Liliana. That's the rule of thumb when you're up against John. I think the pick here is fairly easily going to be. Well, yeah, I think it's still lose though. I think it's still lose. Let's see if this turns out to be right or wrong. I think Liliana of the last hope is Liliana comma the last hope rather is the more scary card for us. Crime, crime, double crime. So if it's straight up John, yeah, I'm liking this bit better. So will I live to regret this maybe? But I'm going to deny both of us Erborg is. So you can see what I'm talking about like with the degeneration.  Do I care? So. Hissing quagmire. He has. Okay. I can't see from here. I think it's got two power. Death touch. Keeping four lands seems like I'd be on about 12 life by now in his head. There's absolutely no point taking that at this point. I might as well just. So I wonder, does it play germag anglers or just wondering about switching out the dismembers for fatal push? He has so much land. There's just nothing I can really draw that helps much. I've had no rack effects. How many attempts have I made to draw? Yeah, quite a lot. Oh, he does have to. Ask and you shall receive. And he can activate as well, which is terrible. I think I think this is a fine game to lose. We've just drawn. We've just drawn worse than him and swallow that. That's all right. Yeah. Okay. Finally, we can finally we can concede. Oh, juicy, juicy. Now what do we do? Fatal push I do think is good. I don't want lay line. I love smallpox. I haven't actually brought her in yet in any of the games we've played so far. All matches. Blackmail seems good. Blackmail seems quite good, actually. 24 seconds left. Yeah, I think blackmail is strong here. Yes, not too much removal, please. Oh, come on, man. Dear idea. Sorry, everyone. I think it's a keep. I've done it now, but as I said, I do think it is a keep. I'm desperate for a swamp. Oh, dear. Well, this might be the legitimate loss. The one that, you know, is supposed to be supposed to happen. We have to be okay with. I can take a ooze as well. You mentioned it. Probably. Yeah. I'm not 100% sure, which was right there. Given that I've got a second in position coming up. Thank God.  Oh, well, maybe expect something. I don't think I'm doing well with him. The experienced player is going to play into it. Okay. Forced me to have it. That's amazing. I can maybe hit the bin. That was a heap of fun the last time, wasn't it? Did he miss a landrop on purpose? Is that what happened there?  Maelstrom pulse.  That could be the difference between having a chance of winning and not here. Really could. That was a huge pickup. She is going to be annoying, but she's discarding, so you're putting yourself to a virtual 10 by doing that. You see, she's just on his side of the table. She doesn't have the same... Oh, Jesus, this is terrible. Okay. Had everything his own way. Um... This is a problem for him. Yeah. And tried to go ultimate. So he has to horde, and that's a good thing for us, so we need to just draw some discard pressure. Wow. Why on earth would you concede there? Why would you concede? All you had to do was... You didn't have to... Right, is this too much? Is this removal package too much? Is there too much going on here? Surely. Unless you're saying to me, but what about smallpox and these three creatures? Well, let's find out if it matters. Let's see, shall we? Now we are going second. And in the Inquisition War, you really... You had another reason to go first and to be wanting to go first. I'll go first, Inquisition, you and stop what you're doing. He's Maltesix, that's good. Can't get used to this artwork. And now, is it just me, everyone? Or is this... Does it look a little bit edgy? It just looks a little bit rough, like it's been torn off or something. It doesn't look like this wonderful, you know, heraldic... I don't know if that's a word, but you know what I mean? It doesn't look that great. And every single legendary card is going to look like this now, really? Oh! Well, actually, this is a bit of a sh... I mean, if this... You know, if this ends up dictating the match, it's... It's not really... Yeah, I'm not convinced by the artwork. I mean, I suppose it would be easy for them to go back and switch back if there was enough. Nothing on turn two. Oh dear, we're in a long way ahead here now in terms of material. Tassaga and Lily. Tassaga and Lily. I didn't love him having a Lily, and like, having her put repeated pressure on this is... Well, not amazing. And having her dominate Bob, so I'm going to take Lily, let him play Tassaga. Oh, he's not even going to get to do that. Oh! I didn't even realize this. I completely forgot that I had a raven's crime coming up, so... Now he's got to just pray for, yeah, yeah, yeah, yeah. So he's just got to pray for land so he can do his thing. Yeah. So pitching Inquisition here, and then into... Oh, this is just harsh. So harsh. Let's see that expression on this guy's face here. I understand. He's on 19, but you know what? I understand. I understand why he would want to quit there. This is what White Tiger Zord is doing right now.  And the only other thing worth touching on, I suppose, in that game is the whole point about the rant I was going on about the Inquisition war, which is yet another scenario where I believe going first gives you a massive advantage. If you Inquisition first mess up his plans, get to the second mana, get to the third mana first, get your good stuff down, that that is worth the card disadvantage that you give up by having him go second. Yeah, by having him go second and yourself going first. If he goes first in Inquisitions, you know, sometimes with 8-Rack, you'll keep a hand that's like, you know, land, land, land, Liliana, Rack, Shrieking Affliction. And you're playing to your Liliana, you're looking at her going, well, look, it's not very exciting, but I can get to my Liliana. And then he goes turn 1 Inquisition. Bang! No, you're not. Oh my goodness. What could this be? Wow. Okay. Gravecrawler is a problem. We like putting things in the graveyard, so if he's got a bunch of stuff that wants to go there... Okay. I don't know what to take here. I'm sorry I'm taking so long, everyone, but you've got to cast the two creatures to bring it back. I'm going to take the glimpse. I have no idea if that's right. Like that...  Like, you're desperate to put...  It's... The one thing I didn't explain in the primer maybe is that if you're met a game, if you're playing in paper or whatever, has lots of Dredge, this deck is a complete... like, 8 Rack is just a joke. It just crumbles. It's almost not worth trying, you know, you can bring in your one Liliana with Void and just pray to find it, but... Yeah. See what I mean. With French Mind. Yeah. A very tough match for us. Oops. Yeah, this could just be a bit of bad luck at the end that we've come up against a Dredgesque sort of deck, but... Yeah. Desperately for Liliana of the Void. Without it, I don't think there's any hope. Sad way to end, actually, because I was having fun, but this is the most unfun experience you can have as an 8 Rack player. That was all he wrote. Dear, oh dear. If he plays Graveclaw on his first turn, surely it's okay to have it in, but then it fights with, yeah. You don't bring in three Bontus unless you're taking out smallpox. Okay, alright. Sanity prevails. Yep, as unplayable as the rest of the hand is, I'm going to keep... I don't know. Four is a lot, like it takes up a lot of room. Having said that, how often have I wanted my Silent Visitor, my third Bob? How often have I wanted Funeral Charm? Practically never. Tomeskower me? Fine. Is that even... What does that do? Does that draw him a card? Oh, hey, by the way, if anyone knows, why when I click this does it not show me the card? In the old versions of the client, I used to be able to click Tomeskower and it'd tell me what the heck it was and what it did. Tiger Play puts the top... Oh, man, how can you run that card, man? I suppose I should keep this open and keep an eye on what's been... How do I pin this back? Do I press this little arrow? There we go. Yeah, he's got Prizedare. He's got it all. He's got the whole package of stuff. Wow, look how much he loves his Graveyard. Go, Mag. Yeah. So maybe I'm wrong. Maybe I need to be... Maybe I need to just actually face facts here that Leyline of the Void is your only hope against these decks and as a result, you should be running for as opposed to Marginal Cards that just helps some of your matchups a little bit. He's just trying to mill me to death, is he? Okay, well, that's a tall order. That is a very tall order. I'm not going to be too precious here. I'm just going to do this very, very tough room to get out from under here. I'm not going to be too precious here. I'm just going to do this very, very tough room to get out from under here now. He's on a ver... If he does nothing, he's on a virtual 5. Oh, he's doing something. Perhaps playing out the Nakamiba there was just abandoning all hope and why not? So, yeah, like... If we get lucky and find out Leyline again, we can still have a chance, but... Oh, boy, without it, are we... Are we in trouble without it? We've got a few... It's possible we're 25% equity or something like that in this game. Going second. We have a few more answers to him here, though, or temporary answers. I don't know if I care about that thing. I really feel like his mill plan is... Why wouldn't you just dredge instead? Alright, fingers crossed, everyone. Come on. My string constant is still out of date. Thankfully, that's not a fatal error. Come on, now. Give me... Yuck. Okay, we have to mulligan. I think we mulligan this in a vacuum. Game 1, we don't know who our opponent is. This is a hand you would always mulligan. It has no discard pressure. This hand... He doesn't have an answer to Bob, so Bob is good. We might be able to... Bob, we might even be able to hardcast it not that it'll help. She's probably... We'd probably put her on the bottom. I guess he could have caught a thingy there as well. Like a... Oh, I didn't need that.   I pray for a reckoning on the second crack from the Angler. So that actually seems like the thing I want to do. I'm going to try to maximize my Bond 2's reckoning by allowing Bob to live. I mean, he might remove him, obviously, and that's just something I have to accept and live with if that's what happens. So really hoping to hit a swamp here off these two cards. Need a little bit of luck. There's a land. So here I can crime and wrench and then chump the Angler. Okay. So I'm kind of trying to do this sneaky roundabout move. Vengevine. Oh my goodness. So he has no hope of hardcasting Vengevine ever. He's so nice if I could get these afflictions down, actually. He might mistakenly play out his hand. He is. Well, maybe he gets a prize at Malgram though. Oh, he does. Yeah, okay. So now I'm in very big trouble. I'm pretty proud of myself though. I think I've played this correctly. He doesn't get it yet. Comes out at the end of his turn, I think, doesn't it? Gee, I tell you what. Going affliction affliction here is so tempting. Okay, so if I go to 12 here I'm certainly not going to 6, so this is an easy decision. He attacks. Bob took a wilder step forward there. He's a bit reluctant. Wasn't he? Down you go. Down the gobb. I'm thinking here. I can drop him to 7 life. He then cracks back for 10 with his prize at Malgram. I'm prized amalgam. It's an amalgam of different body parts. That's why it's called that. Is that correct or should I tap out for Bantu's last reckoning? Oh. Does he get Vengevine as well here, maybe? I don't know. What to do? Oh, juicy. Because he dies on his second upkeep before that second card comes out. Alright, I'm going to take a chance here. I'm going to go for it. Yeah, sorry pal. Taking too long to decide as usual. But I don't think you can beat this. I think we're racing and I'm winning. It's got to be collective brutality. I just cannot think of what else he could top deck here that wins in the game. What's it going to be? Please, please let me go for one. Glimpse. Yeah, what does that do? Nothing? Blood ghasts. It did nothing. Are we getting there? Take 10? That is sweet. That is very sweet. Being able to beat a deck like this as admittedly that's a very roguy sort of build. Like, yeah. If you take away the if you take away the crazy mill strategy here, right? If you take away the useless cards in his hand which were kind of like glimpsing the unthinkable really was. I mean, he got one tome scour that gave him a free prized amulgat. Amalgam. Get that right one day. But that, so yeah, looking back over the matches really definitely this one and bear a candy are the two that really stand out in terms of lessons learned. I think my theory about smallpox and bantu not going together is kind of true. I mean, in the sense that if you're bringing in all three bantus don't be smallpoxing because you know, you've got four lilies presumably as well and there's just too much you're asking too much of your land base to survive the smallpoxing to get up there. Okay, that'll do it for the first league of our 8-Rack Odyssey. Thanks again everyone and I'll see you next time.