do you want to tell us your name? My name is Sheamus Curtis. And where are you from? Organization or even out here? I work with the Upper Fraser Fisheries Conservation Alliance. Cool, and so what is your rollout on this incident? I'm helping manage the fish wheel, it's just up river from here, topside just below the slide. And are you able to explain the fish wheel a little bit for people? Yeah, so the fish wheel is a, it's three baskets that rotate with the current of the water, and they actually catch fish as they migrate up into the baskets. And so how does this contribute to the overall incident? Well, we ship our fish off the fish wheel into the punt, which is probably still behind. And the punks of the boat? Yeah, the punks of the boat. So from there, the helicopter pulls the bins that are in the punt over the falls and releases a fish above the blockage so they can carry on their way. Perfect. And how are you feeling about the incident so far, and like all the progress that's being made out here? All the people are working extremely hard here. Everybody's given it all day long. But the incident seems to be getting better. Every day we're breaking yesterday's goal. So everybody sets a goal for themselves and we just keep on pushing past it. Getting more and more fish over the plants.


This week marks 35 years since the Chernobyl nuclear accident. The accident was the most severe in the history of nuclear power and remains a challenge for the region. 35 years after the accident at the Chernobyl nuclear power plant, the IAA is still here working side by side with our Ukrainian counterparts. As you can see behind me, the new safe containment, a great feat of modern engineering has been completed and the entering spent fuel storage facility is also coming in line. So here on the site, the IAA together with international partners like the European Bank for reconstruction and development is going to continue providing this indispensable support. The accident was also a turning point in history. It marked the beginning of open international cooperation in the nuclear area. In 1986 and in the years since, world governments came together at the International Atomic Energy Agency headquarters in Vienna, crossing political divides to learn from the accident, to plan for its containment and to stop it from happening again. Over the last three and a half decades, agency scientists and staff have repeatedly visited the region to assess the environmental situation while advising on remediation and providing training in radiological monitoring to local experts. Aside from the international cleanup effort, the accident also led to improved global cooperation in nuclear safety. This is even more important today as nuclear energy gains prominence as part of the low carbon energy mix in the fight against climate change. We're also working in terms of the future here in the Ukraine with the integration of more nuclear power plants and units into already pretty decarbonised economy. The Ukraine has reached a record of 67% electricity from nuclear source, which is extremely encouraging where we are together tackling the big challenge of climate change and global warming.


Starting with French President Emmanuel Macron's repression of the Yellow Vest uprising in 2018 and 2019 and deepening this year with ongoing repression of dissent and protest and culminating in two recent pieces of proposed legislation, one of which would grant extraordinary new powers to law enforcement and the other of which is seen by many as targeting Muslims who make up 8% of France's population, we have seen an authoritarian turn from Macron and from his government. Here I think it's worthwhile to understand, to remember that before becoming president, Macron had never actually held elected office. He was by most accounts a brilliant technocrat and a charismatic figure, but he had limited experience with the art of doing politics. His neither left nor right 2017 campaign mantra was successful at the polls, but afterwards it begged the question, if neither left nor right, then what are you for? And to this Macron has had little to no answer, nor does he have a strong basis or aptitude for building consensus. With his approval ratings permanently mired in the 30s and the unruly masses unwilling to concede when he makes his regular concessions to the right, Macron has increasingly adopted an authoritarian outlook on what it means to govern France. I would argue that we saw this shift from 2018, late 2018 onward, but that Macron is also here drawing on a much longer history in French politics, which successfully leapfrogged the French Revolution through the figures of Louis XIV on one side and Napoleon on the other, and which persists to this day in the collective political imaginary. To those unruly masses, Macron now increasingly attempts to respond, I am the decider, I am your sun king.


I am actually very nervous right now, so if my accent gets a little thick, bear with me, okay? My name is Calme Prime. I grew up in the church and have been there all my life. Though I am thankful to my grandma and my parents for bringing me up in the church, but I come to understand that being in there did not make me a Christian, but a self-righteous hypocrite.  I was very involved in my previous church, but everything I did was for my own glory, and not even aware that God would not share His glory with anyone. See, I lived for the praise of men. I did countless wicked things behind closed doors, and the things I didn't do, it wasn't because I got said no, it was just because I was worrying about what other people would think of me. I broke out a lot repeatedly and hoping that no one would ever find out for I feed men and not Almighty God. You see, I had two separate lives, the one everyone sees and prays me for and the other way I indulge in my sins. I was deceived to think that I was a Christian, that I was a child of God. But God in His mercy reached Him there and somehow brought me to Cornerstone to my sister and my brother-in-law, where I heard the clear preaching of the Word of God because faith does come by hearing. And then if you're not hearing the right word, then you have a false faith. See, that caused me, after hearing the true Word of God, that caused me to question my salvation. I soon came to realize that I was lost and I was in need of a savior. God made me understand my need for the righteousness of Christ because mine wasn't taking me anywhere but straight to hell. Today, I am thankful to God for bringing life into a dead corpse like me. To the sacrifice of Christ on the cross, He made me His own. He opened up my eyes and caused me to see my need for Him. I thank Him for the cross, for the blood of Christ. I thank Christ for His perfect obedience to the Father, for taking the wrath that was due to me. I thank Him for leaving His throne and coming to die for a wicked sinner like me. Because of His perfect sacrifice and obedience to the Father, now I can say it is no longer I who live, but it is Christ who lives in me.


My match rucksack is making so much money from dealing these days that I'll be shopping at Gucci and Louis Vuitton anytime I want. He just told me that last year in the US alone, 8 billion dollars was made in herring by dealers and traffickers. Can you imagine how many Louis bag I can get from that money? And he also told me that he also told me, he also said that if there was no war on drugs there would be no black market, which would be very bad for us because then I couldn't buy my bags and clothes and shoes. But thanks to drugs being illegal, he meant his buddies can charge as much as they want. That's why we are so rich. He also told me that in the US there are far more people in prison for drugs than in any other country of the world and still we are the biggest consumers. I don't really understand how. So he always tells me that we should be thankful for the UN to make conventions to keep drugs illegal. So I just would like to say thank you. Thank you dear UN. Early vision is cool. Very cool.


Alrighty. Welcome this morning. I guess it's going to be a little cozy in here with all the people coming in. So my name is Mark McClain and this is Kyle Mestri. So just a little bit about me. I'm a member of Technical Committee, a core reviewer for Neutron, former PTL of Neutron. Currently CTO at Akanda Inc. And I'll let you introduce yourself. And I'm Kyle Mestri. I'm currently the Neutron PTL. I'm also the Chief Technologist for Open Source Networking at HP. Alright, so let's kind of dive into Neutron 101, kind of what, you know, where are we headed today? And then so basically we're going to cover like, you know, OpenStack Neutron. What is it?  And, you know, underneath it has a constellation of projects which is kind of cool. We'll touch on some of those. What are the open source implementations and the reference implementation? There are multiple open source backends, but we'll kind of cover what the reference architecture looks like. Some of the community initiatives regarding Neutron. And, you know, what's, when the most recent release in Kilo and kind of take a little peek ahead to what's in the next release in Liberty. So, OpenStack. So, OpenStack. I thought we just kind of level set. I know everyone probably came to the Keynotes, but just to kind of level set. So, OpenStack was a project founded in 2010. As of the Kilo release, we have 3,654 contributors contributing upstream into OpenStack projects. Ten projects in the integrated release, plus a larger ecosystem on Stackforge. Actually, a pretty significantly large ecosystem on Stackforge. You know, production ready cloud software, as you saw during the Keynotes today being deployed by a lot of different enterprises, a lot of different groups, a lot of people building applications on top. The latest release, the 11th release, was Kilo, which was just recently released. And it's licensed under the Apache 2 license. So, I think we're obligated to show this type of slide, just to level set everyone on what OpenStack is. I'm sure everyone's seen this before. So, this is, you know, this is a high level overview of what it is that you can show people. So, conceptually, they can see what it is with compute, networking, storage, all the shared services underneath, the dashboard, things like that. So, we're obviously going to talk about OpenStack Neutral on the networking component today. So, and as we go through this, it's interesting to know what does the user see, right? Through the GUI, through the CLI, through APIs or whatever. And the user is going to see the APIs, the tenants in this case, are going to see APIs that they can use to interact with the system, whether it's compute, whether it's network, whether it's storage, those are the APIs that the user is going to see. And of course, you know, these could be backed by something like KVM. On the networking side, it could be the ML2 plugin. It could be something like Ceph on the storage side. But the point is, the user doesn't see those technologies, they see the abstractions through the APIs. So, okay. So, once we take those basic APIs and we kind of dive into what exactly is OpenStack networking in Neutron, you know, we talked about the basics, where you see KVM, ML2, you know, and you've got the basics. Also the kind of level set because you take networking, you talk to non-networking people, all the networking people just start talking about L2, L3, you know, L7, what are the network layers? Just real quick, I'm not going to go into, you know, full discussion of OSI model. But basically, layer two is basically a link layer, you know, the wires to connect everything, layer three is basically IP, you know, v4, v6, and then layer seven is like we start getting application layers in between, you know, you get, but those are the different layers when we talk about the numbers, you can, if you want to read more, there's lots of information on the web. So, when we talk about the abstractions in Neutron, if you take a look at the orange boxes at the top, those are essentially the VMs controlled by Nova, each of the virtual servers has a virtual interface, a VIF, that VIF is managed by Nova, so it creates the VIF, but everything else below that going to the bottom of the slide is managed by Neutron. And so, you have a layer two, you have a virtual network in Neutron, that's a network that's one of the core resources in Neutron, it's a layer two connectivity, you have the virtual subnet, in this case it's 10, 10, 10, I mean 10, 0, 0, 24, that's the layer three service, you can also choose IPv6, and attached to that virtual network, you have a virtual port, and so network, port, subnets, those are the three core resources that you will find in all Neutron deployments, regardless of which extensions are enabled or not, and then from there, Neutron's responsible for you take a port, the VM has its VIF, and then you plug the VIF into the port, and now your VM has connectivity. So, these are kind of the basic abstractions we have. Fortunately, we can use the Neutron API and do kind of elaborate setups like this, where you have multiple tenets, you have the orange tenet, you have the green tenet, if you notice they're using overlapping IP space, one of the features of Neutron is that you can have overlapping IP space, it's really helpful if you're saying you're doing CICD pipelines, you want to do testing, you want to do configuration testing, you can basically spin up a complete, replicate your entire environment, including down to IPs within, virtually within Neutron. Some of the design goals when we set out to create Neutron is to have a unified API, to do network services via a unified API, provide a small core, the one of the benefits for having a small core is that it's easy to have very compliant implementations because you have a very small surface area in which you have to match, but also have a pluggable open architecture. We didn't want to dictate which type of technologies we were using because there's multiple ways in which you can provide layer 2 connectivity, so we wanted to have it pluggable and really empower deployers to have their choice for that back end, as well as extensible. If we had a very small core API of ports, and networks, subnets and ports, how else do we expose higher level services? Common extensions you'll find are, say, routing extension, security groups extension, load balancing and VPN are some other extensible services which we've layered on top of that very small core. Like I mentioned a little bit earlier, some of the common features you'll see are support for overlapping IPs, that's one of the differences that you'll find, as well as configuration support DHCP metadata services. Floating IP is a common feature you'll find across all implementations, so floating IPs, if you're not familiar, basically gives you the ability to map an address from the public range onto a particular instance and have it float around. Some people will also comment refer to them as VIPs, but we specifically floating IPs are different than VIPs in neutron, but sometimes the terminology will be confused. Security groups, security groups basically protect the VIF on the hypervisor. So we have support for overlapping IPs, which is kind of nice, so that way if you have different, different tenants can have rules which don't conflict with each other, even if the specific guests are running on the same hypervisor, you can apply those security group rules both on for egress and ingress traffic. egress is a little bit different, Nova doesn't support egress, traffic, Neutron does. They're fully IPv6 compliant, as well as you can have security groups for different VIFs. So in a multi-tier architecture, you may have once on your public network of a VM, you may have one set of security groups and say accessing the database layer, you may have a different set of security groups rules. And one of the interesting things about security groups is it's a logical concept, so the actual implementation we leave up to the back end, so if some of the very smart back ends are able to offload the processing of security group rules and make it very efficient. Okay, so next we're going to talk a bit about the architecture of Neutron here. So this is a pretty easy to read, nice implementation of what a typical open stack architecture would look like. So which piece are we going to talk about? We're going to talk about that piece right there. That's the networking piece, you can't really tell, but that's it. So that's this. Okay, so what is the basic deployment of Neutron look like? So it starts with the Neutron server, so the Neutron server is deployed, and this is where the API layer lives, this is where the database layer lives interacts with a database. You can see right there. So the next piece is you have a message queue, so this is where the Neutron server is going to interact with different components through this message queue. In this particular case, if you're using the current kind of built-in reference implementation, you're going to end up with an L2 agent, and this could be either the OVS L2 agent or the Linux bridge L2 agent at this point. You're probably also going to need a DHCP agent, so that agent will exist somewhere. You can have multiple of these running, you can schedule networks, different subnets to different ones of these DHCP agents. You're going to have an L3 agent if you're doing L3. So this is going to include things, like if you're not using distributed virtual routing, the L3 agent will handle routing, it'll also handle floating IPs, and then you could have multiple of these as well, stack deployed in different configurations. It's worth noting with the L3 agent, we actually support HA using VRRP as well, so you can have HA functionality for that, and if you're using DVR, we can actually offload the east-west routing down onto the hosts using OVS, and we can also handle the DNAT down on the hosts. We still need the L3 agent for SNAT, and then advanced services as well. These are things like firewall, load balancing, and VPN at this point. So let's see what we have next here. Okay, so what does the Neutron server look like itself? So this is kind of what the Neutron server, whoops, I wasn't sure, yeah, no text on that one. Okay, so this is what the Neutron server itself is composed of, right? You have a plug-in on the bottom, and then you have the REST API service, and you have the RPC service. It's really that simple. This plug-in can either be a monolithic core plug-in, or it can be the ML2 plug-in, which itself has mechanism drivers that can host multiple different technologies at the same time. And so what does a monolithic plug-in look like? A monolithic plug-in will have a full implementation of all the core resources inside of it itself. So you can either do a proxy with this, or you can do a direct control, meaning if you're doing a proxy, you maybe aren't even using the Neutron database, you're just proxying API calls across to something else. So that's what that looks like. And what does the ML2 plug-in look like? So the ML2 plug-in looks like this. It's a full V2 plug-in implementation, and it actually segregates the mechanisms from the types, and the types in this case, we mean types of segmentation, whether that's VLAN or different tunnel types, like VXLAN or GRE. And this will actually delegate all of the calls to the proper L2 drivers. So with this type of setup, you can actually run Linux Bridge and OBS at the same time. You can run drivers for physical switches with this as well. And ML2 will take care of working with those. So plug-in extensions. I don't mark it alluded to this in the architecture slide as well. So we do allow for extensions to the API. So you can add logical resources to extend the API. Things like security groups are actually extensions of the core API as well. So like it says right there, yeah, other things are the binding DHCP, L3 quotas, these are all implemented as extensions. We also have the allowed address pairs, extra routes, and the metering API are extensions as well. So the L2 agent, let's go into a little bit of detail on the L2 agent, as we said. So the L2 agent actually runs on the hypervisor, and it's going to communicate back to Neutron via an RPC layer at this point. And the L2 agent's main job is to watch and notify when devices are added and removed, and it's going to actually configure the networking on the host for that device. So whether that's Linux Bridge, in which case it's going to use the VR Kettle commands to set things up, or OVS, in which case it's going to use things like OVS-VS Kettle, and things like that to configure the networking on the host for OVS. This is also going to handle security group rules as well. So the L2 agent will handle setting up security group rules for those hosts as well. So what is the Open V-Switch? The Open V-Switch L2 agent works with Open V-Switch, you can see there, and it actually supports VLANs, GRE and VXLAN networks as well. Let's see if this, there's that. Yeah, it's using OVS-DB down to talk to OVS to wire these things up this way. So the current, it's actually worth noting that the current OVS agent, the way that it works with the tunnel networks is it actually configures two bridges on the host, and the tunnel networks are configured between the hosts. On the host itself, it actually uses local VLANs to segregate traffic, and those VLANs only have meaning on the host that it's running on. And then it's going to use RPC to talk northbound back to the neutron server. So like we said, for isolation, these provide isolation locally. You can use VLANs, you can use GRE. It's kind of whatever you want. We provide the capability, you can look at the trade-offs for the different types of isolation that you want, what might work with your infrastructure. So how does tunneling work? If you assume all of those nice lettered boxes are hosts, we'll build a mesh of tunnel networks like this with the OVS-L2 agent. And then we have these VMs. So the way that this works is we're sending, so this is showing you that previous to this L2 population, the way that this would work was we would essentially end up flooding broadcast traffic across to figure out where the other VM was. So then we have L2 population was a feature which was implemented a couple of releases ago, which is still supported and used. And it's a little bit more intelligent about building peer-to-peer tunnels this way. So L3 agent. So we talked about connectivity with the L2 agents. So L3 agents is where it's an extension we added to neutron. And one of the primary building blocks of the L3 agent is we use, in reference implementation, we use Linux network namespaces. We also use these whether you're using the plain agent that's running on the network node or you're running it within DVR. So basically the Linux network namespace provides an isolated copy of the network stack. You get, you know, the nice thing about it is you get your own private loopback because the IP stacks monolithic, if you don't do this, so that way you can have overlapping IP addresses, which is very important for reusing them. The scopes are limited to the namespaces. So if you see on our host, we have like our host namespace. We have the root namespace that has, you know, E0, E1, BRN. And then you also have namespaces A and B, which also have the same devices, but they're actually different devices. A lot of times what you can end up doing is creating a device like E0 in a namespace and plug it in to a bridge or a switch in another namespace. So in this case, we wired them together and so now we have explicit configured, you know, but it requires explicit configuration to connect them. Another one that benefits is you can spawn processes within those namespaces. So if you're providing routing functionality or forwarding, the forwarding is separate from one namespace to another, or if you want to have multiple DHCP servers that support overlapping IPs, you can spawn that process. The process contacts will know which will be restricted to namespaces. It's a really cool feature of the Linux kernel. So we talk about the L3 agent and this is something that you typically run on a network node. It uses namespaces, typically will have the metadata agent enabled to provide metadata services if you're deploying it. And typically you're going to provide one or more of the network nodes. Mainly what we end up doing is you will place the logical router, we'll place it in one network node. If you have HA installed, we'll create a second namespace on another network node, use VRP to sync the states up between them so that way you get HA support.  One of the cool features about Kilo is V6 is fully supported as well and you get basically static routing, so no dynamic routing that you would expect to find, like BGP or OSPF is not currently supported in the reference implementation as well as a proxy to the metadata service. So sitting in a level above that, so this is how the L3 agent works. And so if you're running DVR distributed virtual routing, we actually spawn little mini layer 3 agent on each of the hypervisors, which if you have a floating IP mapped, we'll handle mapping and doing the NAT for a floating IP for a specific instance. This gives you a higher north-south bandwidth out of a particular host, as well as it also improves east-west routing because you were basically running routing in the host. Higher level services, we start talking about, you know, layer 4 through 7 services. Some of the extensions that we have available is Low Balance Service v2. The version 2 Low Balance Service is actually new in Kilo. So if you've looked at it before, we've actually changed up some of the models. They have slightly different attributes. It is really a cool community initiative that we've had over the last year where multiple members of the community came together and said, hey, there's some things we need to fix in load balancing. So the community worked together, came up with some of the revised design and worked through it and delivered it. So it's really cool. But basically, for the reference implementation, you're going to have, again, the network namespace. It's basically a driver-based. The agent talks to the driver via RPC. And the blue box is the namespace that you have running. And the open-source version, HA proxy, is the process that we're using to do it. And it allows you to provide basic load balancing services with HA proxy. VPN and the service is very similar, except this time, within the router namespace and the network node, you have the VPN software running. It uses OpenSwan, and they talk together. Firewalls as a service is an experimental service that we have. It provides edge firewall services to the logical network. Essentially, the firewall rules are applied and policies are applied at the router level at the agent node. And so again, this is experimental. So we need deployers to test it, to provide feedback and assist the team, and making sure it's ready in production. Okay. So we just talked about kind of a high-level overview. As you know, we just released Kilo. So I thought we'd take a look and see what we added in Kilo. So I think as we iterated, there's a lot of plugins and drivers that can back neutron. We explain kind of the default reference implementation, but there's a lot of other ones. So this is a count. So we added, that's a lot of drivers. It's really hard to see. But with the amount that we added in Kilo, we actually pushed over 50 plugins and drivers, both vendor-based and open-source based in Kilo. So it's a growing ecosystem. And as you can see, we're adding a lot of different stuff. And in this case, a lot of these were services plugins, whether it's VPN or LBS or firewall. So we're adding a lot of advanced service plugins now. I think that's because a lot of people have implemented L2 and L3 already. So now there are people that have vendors or open-source projects that have the capabilities to do these advanced services are integrating into neutron at this point as well. It's also worth noting, I'd just like to spend a second to talk about plugin decomposition at this point that we did during the Kilo cycle. Previously, before Kilo, all of these vendors, all of these drivers and plugins, they had all of their code inside the neutron source tree. So that's a lot of code. That's a lot of drivers to support. So we came up with this decomposition process, which decomposed the bulk of the code, the back-end code for a lot of these, moved them out to a StackForge repository and kept a small shim layer inside so they can still effectively ship with neutron with the open-stack releases. But the back-end logic, which is specific to all of these things, and not just these, but all 50 drivers and plugins, that's outside. So there's actually a panel discussion later today where we'll kind of go into this in detail, but it's been a pretty successful thing for neutron as a whole. And in fact, one other change we're making now in Liberty is we're actually bringing those back-ends back under the neutron tent. Again, there's a talk on the whole change in the open-stack governance model, so we like to think of this as the neutron tent where we're bringing these back-ends in as separate Git repositories released separately, kind of owned still by whatever project, but they'll fall under the neutron tent as well. So we're growing that ecosystem that way. So let's see. In layer three, we added some interesting new features. As Mark said, we have full IPv6 support now. So the team that's been working on that got that done, and that's pretty exciting because I think a lot of people were interested in the IPv6 support. So DVR now supports VLANs as well. DVR is the distributed virtual router functionality. In Juno, it only supported tunnel network types. Now it supports VLANs. And subnet pools. So subnet pools is actually an interesting API addition, and I think we have a nice graphic to explain here. Yes. Okay. So let's say you wanted to...  So we added this functionality called subnet pools, which allows you to specify a pool like this. And then what you can do... So the admin could create this subnet pool like this. And then when someone allocates a subnet, they can just specify the subnet pool, and it will automatically allocate. It'll automatically allocate subnets. So you can have your users basically allocating subnets, and they don't have to worry about specific ones. They can just... There we go. They can just allocate until it's full. And I think we went too far there, but that's the idea there. Let's see if we can go back to this. Three taps. Three taps. There it is. Yeah. Okay. So that's actually a really handy field, a really useful feature, actually, because I think it removes a little bit of the stickiness for having to know exactly the addressing that you want. So you can actually take advantage of that in Kilo. Wait, did we go back? Yeah, that was a double slide, I think. So, oh, did you want to talk about this real quick? The HPB, or should we... Actually, well, we... Okay, I can just cover this quick, yeah. So we had a new feature also in Kilo called Hierarchical Portbinding. I think that that diagram shows that there's actually a talk later today on that, I think, right? Tomorrow. Tomorrow, same time. Tomorrow, same time. There's a talk on the Hierarchical Portbinding, so you can learn about that. Port security for OVS. So this was an important one. I think I'm going to say it. It's an important one for NFV. The NFV people like this because this allows you to disable the security group support for OVS. So if you have, for example, VMs that you don't...  So that's handy there. We have some new API extensions. Also, NFV-related, MTU and VLAN transparency. So the MTU API extension allows you to specify the underlying MTU for the network. So if you know that your network supports jumble frames or some, or if you want it to support a smaller MTU because you're using tunnel networks, you can do that. And if you're using the built-in DHCP agent, it will actually propagate that through the DHCP request. So your VMs, if they honor that, will actually get the lower MTU. And then we have VLAN transparency as well. This API attribute extension actually allows you to specify that the underlying technology that you're using can actually pass VLAN encoded frames. That's all it does. It's not actually trunk ports to VMs, but it allows you to at least kind of get there a little bit. Oh, that's interesting. I guess we like this slide. It's a lot of drivers and plugins. So, okay. So I'll look ahead to Liberty. Where are we going? What are we looking at in Liberty? Of course, we're going to be discussing that this week at the design summit a bit, but we've kind of got a rough high-level overview of what we'd like. And that's Liberty Saskatchewan. Yes. Yes. First thing you hit when you Google for Liberty in Canada is Liberty Saskatchewan. So IPAM, so Plugable IP Address Management. This was some work that was started during the Kilo cycle and it never merged at the end. This is definitely something we're going to merge in Liberty and get there so we can, right now, Neutron provides its own default IPAM implementation. This will end up being Plugable, so we'll allow different IPAM management systems to plug in. I think this is a requested feature. A lot of enterprises have existing IPAM systems, so I think this will be a nice addition. BGP Speaker Support. Again, this has kind of been looked at off and on over the last year. I think we're going to look at merging that this time as well. That was kind of reliant on a bunch of work in the L3 agent that went on during the Kilo cycle. So that work and refactoring is all done. You know, we're looking at NFV enhancements, which are things like service function chaining, possibly enhanced security groups. There's actually a lot of proposed blueprints at this point around enhancing security groups in various different ways. So I think those are some interesting things. And then, you know, paying down technical debt, I think there's still some things there. For instance, we're going to look at doing API micro versioning, which is what Nova recently did. We're looking at possibly pulling all the extensions in so we don't have all of these extensions and we can make them core API attributes. I mean, you can't really do things without security groups and it's an extension. So it makes sense to pull that in. Also, you know, we're looking at the whizgy layer again to see what we can do there. So that's kind of a lot of what we're looking ahead to. So this is just kind of, if you need more information, there's the document. That's the great document that our documentation team works on there. And then there's the API reference as well, which includes the core attributes as well as all of the documented extensions upstream as well. So I think that's it. So I think we left a little bit of time for the questions. So thank you. Does anybody have any questions? I think there's a microphone. If you can't get to it, we'll repeat the question. We'll repeat. Yes, we'll post the slides up the slide share. Definitely. Any other questions? So the question was about the L3 agent with the HA functionality using VRRP. So the best place to look is actually in the dev ref guide because it has a detailed, I think there's a detailed description of how that works. But at a high level, yeah, it's just using VRRP just to balance. So if one of them goes down, if you lose a node that has an L3 agent, it'll automatically fail over to the other one. So it provides some redundancy. And I think it's an important feature because even if you're using DVR, which distributes the routing functionality down, you're still using an L3 agent for the source NAT. So you're combining that with L3HA works well. And additionally, contract D is actually running to sync the states between the two namespaces so that you have a consistent connection state. So the question was around the advanced services and the different vendors with their different support maybe and features. Right. So that's one of the things when you're coming up with a common API like this. Initially, you might have to work it down to what's common between everything. So we allow the extensions so you can add extended features if you have either vendor or open source features that you want to add. Now, the downside to that is then if you're writing the APIs, you have to check to make sure that you have those extensions and things. So it's kind of a Yeah. And also building upon the small kernel over time, you're seeing the community itself now with the new load balancing service has been with v2. They're able to build on in this cycle are going to focus on higher level features. So they tail in, finish SSL termination, layer seven load balancing and seeing a more rich feature set. So from the community side, you're going to start seeing common APIs developed for that as well as the extensions do exist that you mentioned. Yeah, definitely. And I think the other thing with the extensions are if you're using an extension and it turns out that it ends up being really useful, you might see other drivers or plugins adopting that extension as well. Exactly. Kind of gives the users a chance to try that out. And over time with Neutron, that's what we've seen even with the layer two and layer three services, you typically have the vendor to is going to help pioneer and kind of help fill out the space, look at what the API looks like. And then over time, you see more broad adoption that happened with security group, sport security or some of the other features that happened with. Right. So I guess, so the question was the latency of OVS. I guess that would depend on what version. It's actually maintaining OVS. Yeah, it's what? Who's maintaining OVS? Who's maintaining OVS? Yeah, yeah. So you, so like actually working on Open V-Switch itself. Well, I, oh, I think that actually is a pretty vibrant community. And it's a separate open source project which has its own steering team. And so they have like IRC channels. They have mailing lists, which they're constantly working on. The one common thing we'll see about OVS though is, as Kyle mentioned, the version that people run with OVS that some of the distros will package specific versions of OVS. And so if you have a particularly old version, you may not get some of the newer enhancements such as some of the caching of micro flows even later to mega flows. And so they keep adding and making Open V-Switch more performant. So they're working on that, which is adding some support. And then even coming the summer, they're working on one of the things we'll hopefully do is adding integration with with connection tracking. And so you'll actually, we'll be able to get rid of the bridge, the basically the virtual hops are putting in the hypervisor to apply security groups and actually apply those rules directly in OVS, which will again improve, you know, the data path and kind of get rid of some of the bumps that we have along the way. But as far as that, I mean, it's a separately managed, very active community who, you know, there's Open V-Switch is really cool how what they're able to do and the things they're able to deliver over time. Yeah, absolutely. And they had, you know, really receptive community for sure. And I was going to say two things. So that connection tracking feature is actually, there's a talk on that on Thursday, I think, as well. So that we're pretty excited about that. Oh, sorry. Did you know I'm back here had his hand up for a while. So I'll repeat the question and let you answer. Okay. Totally, totally set. So the question was, is that they're right now, if you take a look at DNS and Open Stack, you have an overlap between Nova Networking, Designate, and Neutron in terms of NDACP of like, how do you get a host name? How does the resolving work? How does the reverse resolving work and what service provides that? Now Kyle's going to give you a nice answer. So yeah, I'll say that I think a lot of that is being discussed now, right? The Designate project owns DNS as a service right now. They're doing a great job with that as well. But I think, like you said, you know, we can work to see how we can integrate that more. And I think the IPAM stuff can help with that a bit as well. And but again, it's going to take, you know, Nova, Neutron, and Designate, I think working together to really make that a seamless experience for you. Oh yeah, yes. Then we'll go back. So the question was around tooling and how it monitoring, detecting failure, and that sort of thing. That's actually a good question. So for monitoring, I mean, we do support things like Slometer, right? We have integration with that to provide that capability. As far as the underlying tooling, so are you interested in like the underlying implementations like OVS or Linux bridge or those types of things too? So yeah, in terms of what the monitoring tooling available for Neutron, essentially the tooling that exists now for your underlay is going to be the traditional tooling that you would use for monitoring underlay and monitoring your switches. As far as keeping track of dynamically how Neutron's performing, right now there's no current. The community hasn't written a standard plugin for monitoring. You know, that's obviously an area where people are very interested in that. We'd love to see contributions in that area. So having the ability to monitor, having the ability to look into that is something. But in terms of basic reference implementation, now when you talk to some of the other implementations, either open source or proprietary, they do have add-ons for monitoring, failover. There's very pieces. As far as configuration drift, the agents themselves are constantly checking the database and validating the logical config and the instantiated config actually match each other. So that if you have an operator that goes in and changes the config underneath the hood, it's likely to get overwritten fairly quickly by the agents themselves. So we have time for two more questions. So blue shirt and then one over here. So the question was around VLAN transparency and is there support for Neutron understanding trunk ports to VM? The answer is no, there isn't right now. That's something that we're going to be discussing at the design summit, how we can maybe look at doing that in a way that works as well. So not right now. And then those over here. So the question was around the shims for the drivers and plug-ins. So there's no requirement to have that upstream. You can completely add your driver and plug-in wherever you want outside as well. It's just a matter of installing it and configuring the server to use that plug-in or that ML2 driver. I think the advantage of the shims is that if you have the shim in, then your driver is released with the OpenStack releases. And it'll just pull in through a requirement, whatever back-end logic you have. And so it'll go that way. So I think that's about it. So thank you very much. Thanks for coming everyone. Yes.


What's up everybody? So according to the Wall Street Journal, right now, as I speak, us real estate agents are gearing up for a fight to save our commissions. Do what? When I read this headline, I literally busted out laughing like really out loud and I thought to myself, this is clickbait. This is the biggest definition of clickbait I've ever seen. But no, the more I started reading this article, the more I realized it's a real article written by a real publisher, but doesn't have any merit. Okay. I want to give you my thoughts and I want to hear your thoughts in the comments. So let's dive right in here. The residential real estate industry is bracing for a challenge to the commission's charge by its sales agents. Okay. One that could put downward pressure on the fees paid by home buyers and sellers. Okay. This is just mind blowing stuff here. The justice department is investigating home sale commissions. Do what? The justice department is investigating home sale commissions. Um, and in a wide ranging executive order by president Biden, he asked the federal trade commission to adopt rules to address unfair, uh, practices in the real estate industry. This is insane. Several civil lawsuits, challenging industry rules and practices around commissions have survived all kinds of challenges and drawn support from the justice department, um, putting added pressure on traditional broker fees. All right. The real estate industry has survived past challenges to its commission structure, but consumer advocates say rising home prices have made concerns even greater. So this is amazing stuff here guys. Like the government is stepping in and trying to crack down on real estate commissions and really from what I understand in this article, it's kind of stemming from the fact that home prices went up so much and with the being, the real estate commissions are paid as a percentage. So naturally as home prices rise, commissions also rise, um, and people are complaining about this, how much realtors are making, um, based on, you know, the higher the prices, the higher commissions, um, the litigation and the government attention to, uh, the industry is getting right now is unprecedented. Okay. Um, so what they're saying is, is there's more civil lawsuits and there's more complaints to the government about how high real estate commissions are than ever before. Um, this is mind blowing. So let me give you my thoughts right off the bat about this and that is this real estate commissions are already regulated by the market. Okay. They're completely negotiable. There's no need for any further regulation on something that's already regulated by the market buyers and sellers. Yes.  That's just not true. I've had several buyers over my career negotiate the commission that I was going to make on the deal representing them. And that was another challenge that this article brought up was the buyers, how the buyers really don't have any say so and, you know, their, their commission is, is, you know, added to the purchase price and things of that nature. Listen guys, I mean, on top of everything else, real estate commissions are negotiable. Number one, there's plenty of discount brokers out there. You can even go for sell by owner. Um, there's an even traditional brokers. There's a lot of them taking less. And that's that NAR even proves that the average commission rate is down. Okay. From past years. So as the prices have increased, the commission has naturally went down. Okay. Maybe it hasn't went down far enough for her people that want to complain about how much real estate agents are making. All right. But I just find all of this super interesting that anybody's going to step in to this situation and seeing how it's already negotiable. And here it is right here. The national social renters states in the same article that the average commission nationally is 4.9 compared to 5.4 in the past. So it's come down to half a percent already. Now, honestly, I believe that nothing is going to come of this. Okay. And I'm going to link the article below for the Wall Street Journal so you guys can read all the details yourself. I read every word of the article, but let's just say hypothetically, okay. This is a question.  This conversation shouldn't even be, um, going on right this second. But let's just say something like that did happen. Does that mean that when the market crashes and prices plummet that they're going to raise the commissions because now prices are cheaper? Right. That's the question right there. We're going to regulate because it's high and then keep the regulations when it goes low. Are we going to adjust with the market and make sure real estate agents make the same amount of money regardless of where the market is?  So that's my thoughts. I would love to hear your opinions in the comments. And I want to let you know really quickly about the zero to diamond tour coming to Connecticut. This is going to be the largest event of the zero to diamond tour so far in the last one of 2021. This is going to be massive and we're going to have multi speakers. It's going to be an all day event. It's going to be at the Fox Woods Casino and tickets are free. I'm going to put a link in the description or go to zero to diamond.com backslash events. And if you want to start out 2022 on fire, this is going to be the event you want to go to. I'm Ricky Caruth and those are my thoughts. Get out there and have an incredible day and go help somebody. Let's go.


I was an American male on the loose in Belgium in the late 80s. The tiny village I lived in was called Cambrian Casta and was only a few kilometers north of the French frontier. The town was truly nondescript and an ancient abbey remained the only interesting feature it possessed. The abbey's remains stood on 50 acres of land just beyond the town with a great house, a tower, forests, legs, and catacombs. The latter caught my attention as soon as I learned of them. I investigated the tunnels both historically and physically. Originally, it seemed monks in the late 1500s connected the abbey to the church in the nearby town of Launce with underground tunnels and may even have gone as far as Mons. This is no small feat. Because Mons rests 20 kilometers from the abbey in Cambrian Casta. It then appears that Hitler could not leave something like an underground tunnel alone and had it walled up during Belgium's occupation because too many of his soldiers got lost trying to chase out the resistance fighters. There was evidence of this down some of the underground corridors where a newer wall ended all forward advances or a room was filled floor to ceiling with a pile of rocks. Despite the diminished area of the tunnels, they still held my attention and I soon knew every available inch. When I was not in the catacombs, I was walking through the abbey's forests or around the legs till the late afternoons. It was on one of these lazy Sunday walks that my life changed forever. Call me paranoid if you wish, but the late 80s in Europe was no time for an American to walk around alone. It seemed the Nazi party was not quite as dead as we had been led to believe. And chance encounters with young skinheads became a very real possibility and a very real danger as well. For this reason, I took to carrying a certain semi-automatic friend of mine under my coat on my left side to give a would-be assailant one reason to rethink his position. I will not discuss my occupation at the time or why I could get away with this, suffice to say that I could and leave it at that. I was walking around the largest of the abbey's legs late on a Sunday afternoon when I saw a woman about 200 meters from me near one of the entrances to the tunnels. I could tell she wore a dress, but she had some kind of cloak over it hiding any details of the garment. I could notice her beautiful figure but few other details. There was no obvious evidence that she was in distress or needed assistance. It was just a feeling I got as I walked toward her and she moved toward the catacomb door. Reflexively I adjusted the comforting chunk of finely milled steel under my left arm reassuring myself it was still there. By the time I reached the door to the tunnels, she had disappeared inside with only one glance back at me as I approached. The late afternoon sun was casting many long shadows and I was too far away to see her face clearly, save for her eyes. Her eyes simultaneously bothered me and drew me to her. Two stones crunched underfoot as I left the paved trail for the gravel road to the catacomb entrance. I did not notice at the time, but she had made no noise on the gravel. My approach to the door had been from the side and I did not actually see her open the door to go in. When I reached the door, I had to grasp and engage the metallic thumb latch and swing the door wide on rusty hinges. It never entered my conscious mind that I hadn't heard the hinges when she went in, but my subconscious was pulling double duty trying to keep me alive by taking over my right arm and moving my hand to the butt of the heavy, cold 1911A1 in my shoulder rig. I had been in these tunnels often enough to know where I was. The entryway beyond the door had two exits. The one on my right led to the greatest area of tunnels. The exit in front of me was little more than a rubble covered stairway that branched to two separate short passageways that both dead ended. As I paused for my eyes to adjust, I heard a faint indeterminate sound from the direction in front of me. My eyes had not yet righted themselves, but I moved forward anyway. I knew these tunnels. She might need me. As I moved my eyes, they cleared and I noticed a faint glow like a match up a tunnel that I knew stopped at some of the furor's masonry. When I rounded the last bend, I saw her. She had her back to me and she stared at the wall. Her hair was long and straight and the deepest raven black. She was beautiful and as I stood there mesmerized, she began to turn to me. Her face was a mask of death. There were no eyes in the sockets of her dried skull as she looked at me. There was no skin on the bones of her hands as she raised them toward me. What happened next, I pieced together later. My instinctual reaction was to bring up the gun in a perfect weaver stance and dump the entire magazine into it. I also started to back away at the same time and I fell. This must have been what I had done for when I came to my senses, I was laying on my back in the pitch dark. I fished a zippo out of my pocket and surveyed the area. I found no woman, no blood, no appreciable table that passed according to my watch, no rational reason that I could see before and now it was dark, and no real desire to stay in the tunnels one second longer. I quit the catacombs before anyone came to investigate the shots and hurried home. At home, I discovered some unnerving facts. I had cut my head when I fell. When I washed the blood out of my hair, I found the most startling gray streak over both of my temples that hadn't been there mere hours earlier. I really wanted this to be some kind of horrible dream but the more time passed, the more I began to remember. This seemed totally opposite to a normal dream that one would usually forget by the end of the morning coffee. This dream was getting more vivid as time passed. I remembered a sharp pain in my gut and coughing or, no, choking. Yes, it was choking. I was gasping for air.  My husband. My husband had been taken away and must surely be dead also. My what? I nearly fell. What was I thinking? I didn't have a child, much less a husband. Then I saw her. She was standing right next to me in my own house. She was not the skeleton she had been. Her smooth skin was the palest white and now looked as it must have in life.  She was pulling her hand back as if she had been touching my shoulder. I understand now. The SS must have caught her and other resistance fighters in the tunnels when they walled them up. All she wants is a decent burial. This isn't too much to ask. I'm leaving now with a pick and a shovel to do the right thing. The labyrinth beyond the walls is unmapped. I do not know where she died. I only hope she stays around long enough to lead me back out of the tunnels when my work for her is done. If she does not, however, I leave this testament to any who come looking for me, that they may at least have a clue as to where my body may lay.


So I want to talk about today about Poplis, which is the Civic Hacker Federation. I had the opportunity about six years ago to start NGO in the civic technology space. We're a civic technology organization basically because we develop all sorts of apps for specific purposes from using free information laws, visualizing performance of government, identifying potential cases of corruption, and so on. In the neighborhood, of course, you know several civic technology organizations, like the ones up here, some of which are in the States. And also there's a rising trend of citizens getting organized to develop technology for transparency of other sorts of civic purposes, such as stated here in the study from Global Voices. Now, every night we're being haunted, though, in spite of this good news, we've seen a rise of civic technology efforts by this ghost of impact. Now, what is your impact? It's not just funders asking, like, where is my money going to? It's also ourselves asking, you know, all our effort. Is it really achieving the impact we want in the social space? And our answer to the question of impact when it comes to civic technology has been pretty much like this, which is not a straightforward answer. And that is because it's difficult to develop civic technology from a technical perspective, software is difficult, especially when it comes to software that aims to address a policy problem that is even more difficult. It's very expensive to develop software and especially for civil society organizations that like budget, which also has led to a little margin of innovation when it comes to civic technology. We're seeing the same websites being developed all over again, rewriting the code all over again. So to address these problems, we organized a conference last April where we called 40 of the leading civic tech NGOs across the world. We met in Santiago, and about 30 of those 40 actually showed up, so we had a big representation there. And what we agreed on was this idea of sharing. We need much more sharing on the civic tech space. Sharing stories about what does it take to achieve impact in getting free information laws passed, or lobbying regulation passed, or FY requests passed increasingly, and why didn't work with the same tools in Chile, for example. But it also requires much more sharing of technology. Now, the problem is that so forth, our sharing of tech has been this.  And we have found that when it comes to civic tech, this is just not enough, and that's why we agree on this strategy that's called the POPLUS components. Imagine this is your website, and your website of course has different functions, like a parliament monitoring website has functions about information about people, to find information about the bills that are being discussed, and so forth. For POPLUS, we understand that each of these functions is a standalone website. Technically speaking, each of these standalone components are rest APIs that organize structure and search data for very specific purposes, like structuring information about people, or maps, or documents, for example. If you develop a website from this rest API approach, component approach, it's going to be incredibly expensive. Though marginally the cost will decrease, it's going to be expensive at first. So what if we approach this from a community perspective, where different countries, different NGOs across the world are contributing, developing each piece of component as a rest API, and in the end get interoperability or Lego pieces in the end for civic technology. This is not just theory. So far, in less than a year, we have developed about five or six of these components. Here are three of them. That component of theirs stores data about people, the other one about documents, which serves for bill legislation, for example, and the other one about email exchange and duration being visualized through again these rest APIs. This is a parliament monitoring website we developed about three months ago, which cost us six times less than our previous effort by using the component strategy. And it's pulling in components developed by ourselves in TDA, but also components from the UK, South Africa, and others for information about congressmen, the bills are being discussed, pickup documents, email exchange and duration being visualized, and so forth. Now the great thing is that we're not only the ones using it, the rest of the community is using exactly the same components, and those three components that I showed you are being pulled in for civic tech websites in Chile, Argentina, Paraguay, Kenya, Morocco, the UK, just to give some examples. So this is our approach. The challenge we're discussing here is how can we move beyond open source when it comes to civic technology development. This is an approach. It's yet to be seen what's going to be the impact. So ideas absolutely welcome. Thank you.


Hey, this is Brett and this 2020 GMC Sierra 3500 Crew Cab Short Box Single Rear Wheel Denali is stock number 14541Z. I am here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. This 2020 GMC Sierra 3500 has the 6.6-liter Duramax diesel engine. It puts out 445 horsepower. It is paired up with the Allison 10-speed automatic heavy-duty transmission. This truck has been fully safety and inspected by our service shop, has a fresh oil and filter change. All the fluids have been checked and topped off, and this truck is 100% ready to go. Super clean all the way around. That's exactly what I'm going to do in this video. Go all the way around inside, underneath, start it up, and take a look under the hood and show you all the options and give you the most accurate representation that I can of the truck. White frost tricote is the color. I shoot all my videos in 4K. If you like the video, subscribe to the YouTube channel, click the bell notifications, get updates on the videos I do each and every day, as well as have access to one of the largest catalogs of vehicle and heavy-duty truck walk-arounds on YouTube and stay up-to-date on our current inventory here at Summit Auto. This one has the Michelin Defender LTX MS tires. These are LT 275-65R 20s, and it comes with the 20-inch chromed alloy wheels. They are in really nice shape. I didn't see any major scuffs on there. These tires look like they have probably about 60 to 70% of the tread left on them. You can see it does have the Rancho shocks with the Z71 off-road suspension package, frame and underbodies in really nice shape. This is a one-owner clean title history, clean car fax out of Kansas. Front fender is in excellent condition. You do get the LED headlamps, LED running lights, and the LED fog lamps. We'll turn those on at the end of the video so you can see just how bright they are. Front bumper is in really nice shape. You do get the chrome tow hooks, as well as the front bumper parking sensors. You also get the chrome trimmed grille. This one comes with the surround view camera, and you get the true hood scoop, functional hood scoop on this one. The hood is in fantastic condition. I didn't see any dents or dings on there, and it does have the cab lights up top. Passengers side front fender, very nice and clean as well. Other cool thing about these GMCs is these marker lights light up when you turn the lights on, so we'll check that out as well. Passengers side front wheel no major scuffs or scrapes on there, and white frost tricodes got a lot of metal flake in it, a lot of pearl, some kind of purples, pinks, and even light blues in there. Paint is in really nice condition on this truck. As you go down this side of this 2020 GMC Sierra 3500, take note of how clean the body is, how reflective and mirror-like that paint is. I take these HD videos, so if you are far away, or even if you're close by, and you just cannot make the trip down, but you're still interested in purchasing the vehicle, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises, and you can make a smart and informed buying decision from wherever you're at. If this video helps you make that buying decision, let your salesmen know that you saw the video, that it was helpful, and that Brett sent you. Back wheel is in excellent shape, and so these are the same type of tire. They just have a little bit different design because we put these on in our safety inspection, but they are LT27560R20s, and they are still Michelin Defender tires, and they are brand new. You can see they still have the knobs on them. Like I said, we put those on in our safety inspection. Once again, frame and underbody is in pretty nice shape. You do get the felt wheel well liners, which keeps your frame and underbody looking good, has all the remaining factory exhaust, so it hasn't been altered in any way, and other than a little dust, very little to no corrosion under there. Lower rockers look really good as well. Comes with the nice factory chrome step bars. You get these side box steps, and I didn't see one single dent or ding on the cab or doors on that side, and the passenger side box is very nice as well. No major dents or dings on there. Coming around to the back of the vehicle, rear bumpers in great shape. It does have the backup parking sensors, rear bumper steps, full towing package, which includes a receiver hitch and seven pin wiring. You also have hookups for auxiliary cameras back here. This one has the multi-pro tailgate. Tailgate itself is in fantastic shape. No dents or dings on there. You can see it is a power drop down tailgate as well, and the multi-pro tailgate works like this so that you can get up into the bed of the truck. There is a handle there as well. Spray and bed liner, LED bed lights. It also has a 120 volt 400 watt plug-in. Fifth wheel and goose neck prep package. You also have four pin and seven pin wiring in the bed, and like I said, the LED bed lights there. Get this up, just so it goes like that. Now you can put just this top piece down too, and then you can haul longer boards and put this up kind of as a stopper, but kind of a neat tailgate. That shuts nice and solidly, and as we go down the driver's side, just as clean as that passenger side, LED tail lamps as well, and once again, I didn't see any dents, I didn't see any dings on the box, and that paint is just in fantastic condition. Back wheel is in excellent shape as well. No major scuffs or scrapes on there, and down the rest of this side of the truck, cabin doors all look very good. This one does have the power scope mirrors. They power telescope out, power fold in. They're heated. They have blind spot monitoring, built-in directional signals, LED side lights in the back and the front. We'll just turn all those on in just a little bit. Take a quick look at the back seats. You get the brown and kind of indigo blue leather interior. There are no rips or tears on the seats. You get the power sliding rear window with the built-in rear defrost. These headrests fold down for better visibility. You also get storage area in here, and the strap is stuck in here. There we go. You get a storage area behind the back seats on either side, and once again, no rips, no tears, very nice and clean. These seats fold up. There's your gooseneck ball. Nice storage area back here, and then you also have the Berber floor mats back here. These back seats are heated on the outboard side. You get a USB, USB-C and 12 volt power point inside of the doors. You get the really nice looking woodgrain trim there. Child safety locks on the back doors and the inside and bottoms of the doors all look fantastic on this truck. I'll show you the VIN sticker here. No previously owned in Canada vehicles here. Trailering information sticker, and then the tire and loading information sticker. Up front, the Denali package gives you the same brown and indigo blue leather seats. No rips, no tears. This truck's never been smoked in. Smells very clean inside. You get the Denali stitched into the headrest, and once again, no rips, no tears on there. Both these seats are heated and cooled in power. Driver side lumbar, Berber floor mats up here as well. Auto headlamps, heads up display, fog lights, cargo lamps, push button four-wheel drive, power windows, locks, and mirrors. Memory driver seat, you get that same woodgrain trim on there, Bose premium sound. I'll show you these mirrors. They do power fold in. I always like showing both sides, so you know that both sides are working properly in and out, and then they do telescope out like so, and in. Hop inside, check out the miles, the radio, and everything that this one has to offer on the interior. So you can see this one has 37,611 miles on it. Instrument cluster is very nice and clean. You do get a compass display on there. Has the heated leather wrapped steering wheel, Bluetooth and information center controls on the right, cruise controls, and I'm pretty sure it's adaptive cruise controls on the left, and your heated steering wheel button. Once again, no rips, no tears, no major wear on the steering wheel. Looks really good. There's your shifter for that Allison 10-speed automatic transmission. This one has the GMC infotainment system. You get the factory navigation system on here. There is Highway 41, so that is working nicely. You also get AM, FM, and Sirius and Bluetooth capabilities on here. And then you have your home screen here with all your different apps. Apple CarPlay, Android Auto, and then of course your camera system. You can see the 360 camera there.  Then of course you can kind of do the 360 cam again. And then of course you get your cargo cam, so you can see what's going on in the bed of the truck. And you can zoom over that receiver hitch so you can get hooked up to your boat camper or trailer the first time, every time. Down here are your more tactile volume tune and climate controls, including the dual climate controls. Here are your heated and cooled seat buttons, factory exhaust brake, lane departure warning, parking sensors, power drop-down tailgate, hazard lights, stability control. There's your switch for the plug-in in the bed of the truck, downhill assist control, factory brake control, USB-C, USB, 12 volt power point, and a 120 volt, 150 watt plug-in. You also get the wireless cell phone charge pad, center cup holders there. You can see everything's in really nice clean condition, keyless entry with remote start and power drop-down tailgate. Dual glove boxes, passenger side floor mat and seat are in excellent condition as well. Once again, smells very clean inside this truck. The headliner is in really nice shape, power sunroof, map lights, home link buttons for your garage door security systems and lighting systems, power side and rear window, and sunroof controls, on-star and SOS buttons. And then you do get the rearview mirror that is also a camera. And once we start it up, I can show you that. Starts right up, no-check engine lights or anything like that. You do get a digital speedometer on there. There's your rearview mirror camera. So it's a video display of what's going on behind you. Now, if you didn't like that, you can make it just a normal rearview mirror. And you can also raise it, lower it and brighten it or dim it. You also have your heads-up display in the windshield. Once again, you can brighten that, raise it, lower it or turn it off altogether. Let's turn all the lights on and then take a look under the hood. I would personally like to thank you for checking out the video today. There are those LED side lights. They are very bright. And hopefully from this HD video, you've been able to verify the quality, condition, options, and of course, cleanliness of this truck all the way around. See, all those lights are very bright. Cab lights all working nicely. And under the hood, we have the 6.6-liter Duramax diesel engine. Engine-based, very clean, runs very smooth. 445 horsepower. L5P is the engine code. Once again, this truck has been fully safe and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. And this truck is 100% ready to go. So the air comes in. The scoop in the front goes down this tube right into the air cleaner right there. There is your emissions sticker. Shocks are doing a great job holding that hood up. And I would highly recommend this truck to make quality and condition standpoint for a 2020 with these miles on it. One owner, clean title history. I don't think you're going to find a nicer one than this. And to see more pictures of this truck or one of other 550 new news cars, trucks, SUVs, minivans, Wranglers, halftons, three-quarter tons, one tons. You name it, we got it. Go to the website right there, summitauto.com. Full pictures and descriptions of every single vehicle, all at summitauto.com. And if you want to check out more HD videos, you can go to youtube.com slash summitauto. Click the bell notifications, get updates on the videos I do each and every day. As well as having access to one of the largest catalogs of vehicle and heavy-duty truck walkarounds on YouTube and state current on our ever-changing and vast heavy-duty truck inventory here at Summit Automotive. In fact, in a second, we'll see a link to subscribe to my YouTube channel in the upper left. A link to all the GMC Sierra 3500 truck videos I've ever done in the upper right. A link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right. Click those. Check us out. We are super excited to help you with this Ultra Clean 2020 GMC Sierra 3500 Crew Cab Short Box Denali Single Rear Wheel and White Frost Try Coat. Thank you so much for checking out the video. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it. Thanks again and have a great day.


It is time for the renewal of the Higher Education Authorization Act that gets renewed every five or seven years. So the discussion of financial aid, the design of financial aid is going to be in the air during this congressional session. I developed this proposal to reform student loan repayment. We found that the discourse around student debt doesn't really match the numbers. The numbers that we see in the papers are by far the outliers. What we found were that 69% of undergraduates are going to borrow less than $10,000 a year. We next looked at characteristics of who is defaulting on student loans, and what we found really surprisingly was that it's not the biggest loans that people are defaulting on. They're actually smaller loans. All this adds up to what we interpreted as a problem in the way that we structure the repayments of student loans. College education pays off over your entire lifetime. Yet the payments are concentrated in the first 10 years after you graduate college, which is when former students' earnings tend to be lowest and most variable. So we proposed spreading it out over 25 years. That would allow for much smaller payments in each year. We also proposed that the payments flex automatically with people's earnings. Automatic repayment that's linked to income is the norm in many countries. If you suffer a bout of unemployment, you wouldn't have to go do an application and submit it to your student loan servicer in order to get the forgiveness. People who are having economic problems, that's probably the time in their lives that they have the least capacity to handle piles of paperwork. They should be looking for a job. What I sought to do with the student loan proposal was to try to find some ways that we can alter loan policy that would be a win-win, and that would make life better, especially for people who are currently in repayment.


Welcome back to JSA TV and JSA podcast, where we're covering the latest stories, trends, and innovations with leaders like Yovita here in the global connectivity and real estate markets and the networks within them. So I'm joined. We have a very special guest with DC Byte today. We've got the Amiya research manager here, Yovita Yanash Kavichite. I tried. And so I'm very excited to chat with you, Yovita. Of course, DC Byte is a data center leader reimagining the future of the availability of in-depth industry market intelligence. So very interesting guest for us today to chat with. So it's your first time on JSA TV. And we'd like to just hear a quick introduction, if you don't mind, a little bit about what you do for DC Byte. And what led you to pursue a career in the data center industry? Absolutely. So first of all, thank you so much for having me. My name is Yovita Yanash Kavichite. And I work as an Amiya research manager. My primary focus is to ensure the accuracy and the quality of the data within the Amiya region, as well as to align the research methods across the different teams. And I'm also managing the team of eight analysts based in Amiya and two analysts in the Americas as we are building on our data sets in the moment. And being completely honest, I haven't really pursued a career in the data center industry. I was working in a small business at residential property. And at that time, I was looking for graduate equivalent business analyst roles. And there was slightly similar role as a research analyst advertised by DC Byte, which I quite liked. And I thought I'm going to give it a go. And here we are three years later. But yeah, I've heard about the data centers just before the interview. So it's been quite a journey, but I really enjoyed it. Excellent, excellent. I feel like that's some of the best stories about how people land in this industry. They kind of happen upon it. And then you don't even necessarily know about it sometimes until you're in it, which is something that we're actively working to change as an industry, I think. But it's such an incredible, powerful, and highly relevant industry. So it's a really amazing sector to be a part of. So you are appearing in a panel later this afternoon. So you're very busy today. So let me read off the name of this panel. The point of diminishing returns where low latency operation shouldn't be your priority. So of course, the industry is growing at an exponential rate, like we were just saying. So what do you think should be a priority for data center developers when it comes to infrastructure location? I believe at the moment the data center developers are focusing into the markets, but still have availability of large land plots as well as, and more importantly, a huge availability of power in there. As that sort of secures them the opportunities to scale up in the future. Having so many markets across Europe suffering from power constraints, we would expect that this trend is continuing to remain where the data center operators will be trying to grab a power land in lower latency regions. Yeah, okay. And particularly knowing that so many countries in Europe are now focusing towards sustainability and shifting from more carbon intense electrical power supply to renewable energy sources. We would expect that more and more data center developers would be looking into establishing data centers in the locations where there is an abundant supply of renewable energy today as opposed to later, which is why we would expect that Nordics are also likely to have a huge growth in the future. Okay, perfect. We'll definitely check out that panel if you're here on site, the point of diminishing returns. Okay, last question. So how can infrastructure owners effectively navigate decision-making processes and what role does data center intelligence play, which is a hot topic at the industry today or at the conference this week in facilitating such transitions? What trends do you predict there for the near future? Well, lately we've started noticing trends about more and more data center operators started acquiring land plots outside of the traditional data center clusters whether that's in prior called secondary markets or within the same primary markets but in the regions where availability zones are not created just yet. So we are trying to attract the demand to the new locations as although a lot of data center developers would like to be in the popular traditional data center clusters, unfortunately there are power limitations. So we would expect some of the demand to shift to the new regions. And it's very likely that this trend will sort of continue considering what's currently happening in the region. Yeah, excellent. Well, great insight. Thank you so much for joining us. I'm so glad you found your way to the data center industry. Thank you. And thank you viewers for joining us today for this discussion with DC Byte, Yovita here and stay tuned. More coming your way. Happy networking.


Dear mom and dad, camp is fun. I wanted to climb the mountain, but everyone says I'm not old enough yet. Can I come back next year and do it by Nick? Mount St. Helens, a 9,677-foot sleeping volcano nestled in the wild abundance of the Gifford Pinchot National Forest in Southwest Washington. On March 20, 1980, Mount St. Helens began to show tell-tale signs that her slumber was ending. After the last great ice age had retreated northward, the Cascades were already well-established, running from Northern California through Oregon, Washington, and into Canada. But there was one peak amongst them that was not so well-established. Compared to the rest, she was a teenage mountain, and like most teens, had growing pains. St. Helens is known to have erupted numerous times in the past. In the early and mid-1800s, she erupted again. Its small wonder local Native Americans in a variety of tribal languages called this peak basically the same thing. Fire Mountain. The view from the summit of Mount St. Helens was breathtaking. Below lay Spirit Lake. In the distance, an older peak, Mount Rainier. The lake was a haven for recreational activities and youth camps, the YMCA's Camp Mehan being the first. Thousands of youngsters flocked to the lake over the years, learning how to row a boat even when the oar locks wouldn't stay put. Sailing a wind that seemed to rise from the blue-green depths of the lake itself. Always discovering new friends, the diamond encrusted night skies, and how to cook an egg on a stick. There were national forest campgrounds on the lake too, Bear Cove, Cedar Creek, Donnybrook. And beyond them stretched the forest, a living museum for the curious. A place as close to heaven as one could get. At trail's end there were places that were like living in a postcard world. In the winter of 1979, changes were taking place deep beneath the mountain's serene exterior. On March 20th, 1980, a moderate earthquake beneath the mountain registered 4.1 on the rector scale and was the first sign of an eruptive phase. Swarms of quakes followed until March 27th. A concern for public safety prompted the closure of the Gifford Pinchot National Forest. What scientists had anticipated, the eruption of Mount St. Helens before the end of this century had begun. The mountain had a newly opened crater measuring about 250 feet in diameter. The earthquakes continued. Forest service and cooperating scientists went right to work, ringing the mountain with an array of gadgets, hoping to document even the slightest twinge. The Forest Service ordered immediate evacuation of its own nearby ranger stations, such as this one on Pine Creek on the southeastern flank of the mountain. They also strongly urged others having homes, lodges, or camps near the mountain to do the same. On the morning of March 29th, a second crater was observed, which had opened during the night. The new crater measured 75 feet wide and 30 to 60 feet deep. On March 31st, explosive eruptions continued and the two craters merged. For the next several days, the mountain continued to spew ash and steam. Then, eruptive activity decreased. However, a bulge noticed earlier on the north-northeast flank of the mountain near Goat Rocks was found to be moving north-northwest at about five feet a day. Scientist David Johnston expressed the opinions of the U.S. Geological Survey. They would later prove incredibly accurate. In the initial phases, we'd see probably very large eruptions that would extend high into the air. This would spread ash over large areas in western Washington, maybe possibly in an extreme case, even farther east. In the near-near flanks of the volcano, there would be more damage done by possibly hot avalanches, power-clastic flows. Farther downstream, we could see mud flows and floods. Because this is such a symmetrical volcano and because the crater is so high, if there's an explosion, it's probable that the debris, the very hot incandescent ash, would come down, could come down all sides. But right now, there's a very great hazard due to the fact that the glacier is breaking up on this side of the volcano, on the north side. And that could produce a very large avalanche hazard. In the meantime, the Chief of the Forest Service declared part of the land around the mountain a geological area to help protect the unique features. The Forest Service and the U.S. Geological Survey were taking the mountains seriously, as did the Spirit Lake Youth Camp Operators, who coordinated their efforts and along with a donated helicopter and a large refuse bin, began hauling out. Well, the tourists come to see her smoke and they all think it's one big joke. That mountain's just a molehill in disguise. But when that lava starts to ooze, they'll be running the heels off their shoes. Heck, we just thought she was over publicized. But the effects of Johnston's words were lost on most people, who were more interested in Mount St. Helens as just another roadside attraction. It's good that a rocket's gonna roll. It's gonna leave a nasty hole. It'll be too late to find a place too high. Far as we know, it was just a joke. Well, not really a joke, I guess, but it could last 100 years. We're gonna stay till the rocks start falling, I guess. You don't mind working in the shadow of the mountain, then? No, not at all. Be scared of it. The more dangerous one of them trees is falling on the back side, and there is a mountain of the exploding. For 83-year-old Harry Truman, operator of St. Helens Lodge, nothing was about to move him from the shadow of his beloved mountain. Harry wants to stay, and he's not gonna leave, so all that. And he's thanked us for our concern for coming. It's definitely a mistake. Somebody done it to cause trouble for me and the law and everybody else. That's my life. Spirit Lake and Mount St. Helens is my life. Folks, I've lived there 50 years. It's a part of me. That mountain and that lake is a part of Truman, and I'm a part of it. The pressure was building, but Harry wouldn't budge. The morning of May 18th, 1980. It was like any other Sunday morning for a Forest Service tree-planting crew on the lower southern flank of the mountain. Until 8.32 a.m., it seemed to happen in an instant. A cubic mile, tons of ash, rock, and ice were rocketed into the stratosphere. The cloud reached nearly 14 miles into the sky. The view was spectacular, but the wind was blowing in a north-easterly direction. And from that point of view, the cloud seemed like the end of the world. The skies grew dark, and at noon it was pitch black in most of eastern Washington. Everyone to not panic. If you want to start getting out some water supplies now- Life in the ash storm came to a pretty halt. The southern road is closed from here any further east. Okay. This as far east as you can go. Those who could move, however, moved quickly. The 304th Aerospace Rescue and Recovery Squadron from the Portland Air Base was called in to find geologist David Johnston, who was manning a scientific lookout above Coldwater Creek, six miles northwest of the mountain. He was never found. Where's Spirit Lake? Is that it over there? I can't believe I camped up in this area. Doesn't look like any place I've ever been before. As most of you already know, we had a major eruption occurring at 8.32 approximately this morning on Mount St. Helens. The first report that we actually got about the eruption was from a Forest Service personnel that were administering a tree planting contract and they reported over the radio to us that an eruption was occurring and it seemed to be about a hundred times greater than one that we've ever had in the past. It does appear that the northwest flank of the mountain seems to be gone. They have indicated that there have been some mud flows that come down the southeast flank of the mountain. emergency procedures have been put into effect at 10.15 this morning and Calets County reported that a 12-foot wall of water was coming down the Tudor River and it was verified by the Washington State Patrol. The largest rescue mission in the history of the northwest was soon underway. What's on the left now? Good. What do we have with that? Is that the one over there? Military helicopter units and other rescue squads joined the effort, coordinated by the county sheriff departments. By the end of the rescue operations, which lasted two weeks, more than 170 people were brought to safety. But in the final count, 61 were dead or missing. Roader wash from the helicopters kicked up great clouds of ash, making rescue difficult. In many places it was impossible to land. Rescuers were lowered by cable to assist survivors who were then reeled to safety. Tons of ice and snow melted by the intense heat of the raging volcano mixed with the ash and began rampaging down the flanks of the volcano. One mud flow reached Swift Reservoir, about 10 miles to the south. But it was the debris-laden walls of water which tore down the north fork of the Tudor River that proved most spectacular and devastating. There is a punch line. What's going on down the mountain right now? After wiping out an entire logging camp, the deluge raged on. In a matter of hours this river of destruction searched under the Tudor River bridge on Interstate 5, closing the main arterial between Portland and Seattle. Entire forests and logs hundreds of years old roared past stunned onlookers. From the Tudor to the Cowlitz to the Columbia River, first attempts at clearing the debris became exercises in futility. For the first time in decades, the lower Columbia River was closed to freighter traffic. The raging torrent had left its mark. In a matter of hours the winds carried the growing ash plume over Idaho and Montana. A month later the plume had circled the entire earth. In the wake of the plume, ash was everywhere. In some places the price of a surgical mask quadrupled. Ash doesn't melt. Water turns it into a thick, grimy substance like wet cement. It's as back-breaking a job as moving a mountain should be. When the skies finally cleared, Gifford Pinchot National Forest Personnel began the sad task of assessing the damage. Acres upon acres of prime timber flattened. Bridges, roads, campgrounds, trails, all obliterated, buried, destroyed. Spirit Lake was a steaming quagmire of debris. The entire north flank of the mountain was gone and proved the key to understanding exactly what had occurred on the morning of May 18th. The initial event was a major earthquake. A devastating lateral explosion followed, destroying nearly every living thing in its path, including Harry Truman. The initial force of the eruption had been across the land, instead of blasting skyward. Now the mountain, which lost most of its summit, is topped by a gaping, horseshoe-shaped crater nearly two miles long and one mile wide. The perilous vantage point of a still photographer and the actual recorded voice of an eyewitness with a two-way radio bring the tremendous force of the May 18th eruption into chilling focus. Photographer Gary Rosenquist barely escaped. Radio operator Jerry Martin did not. A recovery and planning team undertook an immediate survey of the area and began one of the most intensive planning efforts in the history of the Forest Service. Their preferred plan called for extensive protection of this window into the earth's building process while recovering a portion of the downed timber and rehabilitating the land. Although at much lesser intensity, the mountain erupted five more times during 1980. This eruption, on July 22nd, was photographed on time-lapse by amateur photographer Jerry Whittaker of Woodland, Washington. Meanwhile, a watchful eye is kept on the steamy crater and surrounding area. Some say the mountain shows signs of going back to sleep. Others say, that's not likely, yet. But the fact is, no one knows for sure, and so the vigil continues. Geological survey scientists visit the crater and surrounding area as frequently as conditions permit. Rock samples are collected. Distances between established points are measured electronically to detect any swelling or deflation of the volcano. Forest Service and University scientists continue to monitor how plant and animal life are recovering. Volcanoes are secretive and unpredictable things. St. Helens could stay active for a week, a decade, longer. But sooner or later, by one manner or another, she will change again. That's the way it is with volcanoes. To be sure, much will happen in the meantime. Trees and huckleberries and wild animals will return to the mountain's flanks. Spirit Lake will become clear and blue-green again. Gurgling streams will again be favorite haunts of the trout and the fishermen. But for now, we have a landscape in transition. A rare opportunity to learn from the earth what the earth is made of, why it changes, and perhaps even when it will change again. For those who find the loss of a mountain as it once was difficult to bear, there is consolation in a long-range program which will protect the marvel of the area's natural recovery, allowing many generations to replay the instant of destruction, while at the same time being eyewitnesses to the magnificent healing powers of nature.