many people here are playing with containers or using containers, I guess hands up. Okay. And out of curiosity, so who's focused on Docker specifically, like maybe Docker or Docker Swarm, that ecosystem? Okay, kind of a lot. And then how about Kubernetes? Just a few. Okay. Yeah. And then what about Mesosphere? Anybody out there? Yeah? Okay. Just a few as well. Okay. Cool. Just wanted to... How about OpenStack in general? Is anybody using OpenStack? Okay. Cool. Just a few as well. All right. So just wanted to level set so I know what people are interested in. And how about network administrators? Are there any network or infrastructure people? Okay. So we mostly DevOps, so developers, yes? Or DevOps specifically? Pretty much. Okay. Okay. So my background personally, I'm a systems engineer in Kura. We're a network virtualization company focused on that. Our product was initially started six years ago. Company called Mido Kura. Mostly focused on the engineering of this product called MidoNet. And then we went open source in 2014. But my background personally is I come from a hardware networking background. So I was focused initially more on service provider products, sort of layer one, layer two. I like to joke for networking people that I kind of moved up in the networking layers. Like started off on DSL products, layer one, two. Went over to MPLS, Technologies for Carrier. And then Data Center and Campus. So I've been more focused on networking. I like to think about security too now moving up in the stack, the networking stack. So given this is DevOps and now I'm at more of an open source and that sort of ecosystem company. I think two of the main things, the challenges are open source is really powerful. But there's a lot of things that Kevin just talked about, integrating with this whole host of tooling and integration and the way technology advances. But that's part of the awesome thing about open source is all these awesome technologies come out of it. The other main thing is how do you drive adoption? Just with new technologies, people are weary, there's obstacles to overcome. And then of course, how do you move into production specifically? So all these things need to be sort of thought about. So today more I'm going to talk about, if my slides want to advance, containers. And then of course what's come out of containers because they're not that new of a concept anymore. A lot of people are, there's a lot of buzz about it and that's continued buzz still exists but they've actually been around for a while. Also, the movement to container orchestration, how to manage multiple containers, how to deploy applications and develop for them. But as we'll see, even with other technologies like OpenStack as an example, networking always seems to be an afterthought and this ends up being a hurdle actually when going to production because there's these security implications or how do you scale an application, a lot of these things, network can make or break moving into production. So why containers? As those of you who are playing around with it already, know it's a lightweight way to deploy and it's a more efficient way to build an app, smaller bits and bytes, you don't have to, less overhead than a virtual machine because you're not repeating the complete operating system for every single container. What that means in infrastructure is you get a lot more increased density on a physical host. So that has implications on the network of course too. But as developers it's empowering to be able to do something in a portable manner like a container image on your desktop and then go to staging and beyond after that. So of course, not being around for a while, leveraging things for security like SELinux, C groups, kernel namespaces, the focus was previously more on systems containers. Of course things changed. So LXC version 1.0 was only, in the end it was only released two years ago, right? But that brought about more security with unprivileged containers and then the ecosystem initially was probably not as hot as it is now. But why is it hot now? Docker, everybody knows. Dockers, the way that developers got their hands on containers in an easy fashion right on their desktop. So it enabled a lot of development right on their desktop, an easy container imaging format. Security was more done through Linux bridge and IP tables. Where I come from we cringe at IP tables. So makes people feel uncomfortable and doesn't scale well. But the ecosystem has totally grown around this. So container orchestration, technologies like we were just talking about, Kubernetes and Mesosphere, companies like CoreOS who have propelled these technologies as well. And advanced it even beyond Docker using other container formats. So of course all these container orchestration engines came along and that's what helps really deploy applications on a wider scale. So things that they can take into account are clustering containers and therefore defining services, perhaps having load balancer or service replication to enable having that app always up. But that's the dream, right? So that's where we all want to be. The expectation is chase that dream. But the reality is when it's time to go to production probably someone like your network security person or admin is going to contain you. So multiple ways that would be done, right? So you can do that with kernel namespaces, SE Linux, and that could affect the way the app is actually deployed. So it might totally hit a hurdle in the app or you want to leave these things open to vulnerabilities. So what's the problem then? What's wire containers insecure?  Not everything in Linux is namespaced processes and shared components on a physical host. And what that means is you can't assume that the container next to you on the same physical host is totally isolated and can't reach you. But what does that do to the network as well? So even coming off a physical host. What to think about those type of things? So yeah, the container orchestration engine helped the clustering and the deployment of multiple apps. But what about the networking? And as I mentioned, even previous technologies that were adopted widely on the open source world, like OpenStack, sort of left networking to the very end. Everybody's excited about the technology and deploying and having new tooling and the networking is more like the plumbing, the boring afterthought. So we're sort of seeing similar patterns here with how to address networking with container orchestration engines that we saw in these other technologies. So the framework is sort of being redefined. We feel like we're reinventing the wheel. Open source communities, the part of the beauty is bringing a lot of collaborators together from various organizations. But the problem is you're going through that battle again and in the end there's only a set defined type of way to define networking too. So it just depends on the abstraction level, what kind of battles. So even in this world, what networking model does one choose? Because Docker is leans towards this container networking model, which we'll talk about those definitions. Whereas Kubernetes and Mesosphere are leaning towards this container networking interface model. And they both approach networking a little differently. So don't know why it's always last, but maybe it's just not the hot technology stuff, I guess. So who's going to care? Well, your network administrators and your security team are definitely going to care. You can't just leave everything light open. Some of these projects started by Google, the roots of Kubernetes, everything was internal and open, so they didn't really care. But as soon as you start deploying these in public spaces, you're going to start caring about which part of your apps are talking to each other. So that's why you should care too. So containers, as I mentioned, you're increasing the density on a physical host. And therefore in your infrastructure, you're just going to get way more end points in your network and infrastructure. So that means more complexity. And this is sort of trying to depict the microservices type approach to deploying applications, which of course has benefits from many levels, right? The best of read type is that you're doing for the specific microservices that are deployed, which means better and easier development for developers, easier to manage in terms of operations, like in terms of isolating parts of those microservices and how they operate together, and also from a business standpoint, being more efficient in your operations. But in the end, in the network, this gets much very, very complex. And even when you're testing all these points, and we're talking about operations, a lot of people like to blame the networking people. Why does it take so long for me to get a VLAN configured on my router or switch? I need a subnet now. I want to deploy quickly. I want to test something really quickly. Why does it take me so long to get networking? So what's important is we bring these networking aspects into the agility of these more dynamic tooling. But it gets more complex when you have to consider security and as well as scale. So this little guy, you'll see him again. He's our career man. So in legacy infrastructure, you typically have all your servers connected with leaf switches, going up to spine type core, and then usually your firewalls are more at your core. So this is considered more perimeter security type approach. That's more of a legacy type approach. And that was fine back when we had more north-south type traffic flows. So more bare metal type workloads. So things are coming in and out of the data center. So you can just handle that. But that, of course, poses a problem if you have an attack on the inside. All you have to do is cross that one barrier and then the rest of your network is exposed. So with virtualization, there tended to be a lot more east-west traffic bound flows. So how to manage that? Well, one approach was using these virtual network functions. And that means just using firewalls and these could be virtual appliances. And then they're in the data path of these virtual machines. And so how do you manage that? Where do you put them? So there's a lot to think about there. So more doesn't necessarily equal better. Like it's managing more pinch points. And you're still kind of, it's sort of still guesswork on where to place those depending on how your east-west traffic flows are. So I thought, you know, it's Thursday, right? I don't know. It's been a long week already. So throwback Thursday, going to throwback to OpenStack as a reminder. Like what were the challenges there on the networking side? And it sort of feels like it's being repeated on the container side. So for those who aren't familiar, OpenStack is an open source, a large open source community that develops, can compute, basically. And so many projects have come and spun out of that. But the core was storage and compute. And this was started, yeah, six years ago, I guess, 2010. It's gained a lot of traction. You know, these OpenStack summits are every six months and they're in the order of like 7,000 to 9,000 people now, it seems. But it's enabled a lot of engineers from different areas to different expertise to come together. And again, in the beginning it was rough. It was rough going into production with this. So people didn't trust it. But it's definitely come a long way since six years ago, where people have been running in production for many years now. But as I mentioned, so Neutron is the networking project with an OpenStack. And it was late to the game. So networking originally was under the compute project. So that means it didn't really have that much attention. Nobody really thought about it. It was more cool to get your virtualization going on your servers. No one was scaling yet because it wasn't production anyway. But as soon as people started going to production, they realized, okay, there's some inherent problems with the way we're doing networking. We need to focus on it. We need to define it as a framework. So in the end, Neutron is this project and it's a networking framework. So there's a reference architecture. But also the things that came out of being an individual project was that there was a push to have it have a pluggable nature, which means there could be multiple solutions inserted to provide those set defined of networking APIs. So this formed an advanced networking framework. You can have really interesting architectures, tiered architectures, layer two through four networking services. Well, that's what I wanted to get to actually. So part of the beauty was multi-tenancy was a really important aspect of OpenStack, having isolated workloads, and a whole host of these network functions from switching, routing. And people have various ways of implementing these things, but these are things that are important. And they apply also to containers, as we'll see. These are just so virtual machines could be just considered endpoints and all this type of functionality can be provided to whatever that workload is in the end. And it could be, and it's, in the end it's just mimicking what we know from hardware networking, like ACLs, staple firewalls, natting, you know, the way that we are moving forward to deploy applications. And there's several different vendors and projects. Some of them are proprietary, some of them are open source projects. So MidoNet is a completely open source project. OVS is the original reference architecture with OpenStack, and these are all hardened neutron plugins that people are using in production today. So I'm going to throw, as I mentioned, throwing a bunch of open source projects names out there. Has anyone heard of career? No? All right. Eh? Yeah. So career actually, so it's check for career. So like a trans, a carrier of network packets, I guess you could say. And actually it was started by originally a former MidoKura developer, and so he likes check things. That's how he came up with his name. And what it entails is it's an open stack. It's a project basically under the OpenStack umbrella, but it can be used outside of OpenStack, as we'll see. And it basically leverages this framework that was already predefined by this wider community for this networking framework with advanced networking functionality and applying it to containers. So, you know, not having to reinvent the wheel but just leverage the already existing network framework that exists from Neutron. Especially since the container networking model and the container networking interface are really not that mature and it's going through the same battles. Even the identical processes like IP tables which is known to not scale well and these are like the things that were tripped on an OpenStack and recovered from and those were kind of being repeated in the container world. So the mission is to bridge container networking to these OpenStack network abstractions. So what is Courier as I mentioned? It's bridging these container networking to these OpenStack Neutron networking abstractions. But what it literally is is these group of projects, they're all up on GitHub. So Courier Lib is the common libraries between all of these container orchestration engines. So what's important is what's leveraged from OpenStack is the Neutron client, so the definition of the framework, the Keystone client which is used for authentication, and then in turn some of the vendor bindings that happen at the physical host. Courier Lib Network is focused on the Docker networking plugin, Courier Kubernetes, and this is just where it stands today. It's obviously an evolving project and continues to be worked on. Courier Kubernetes is the Kubernetes API watcher and CNI driver which will go over also. And then there's also this other project that is focusing on the storage aspects on how that could be leveraged from OpenStack as well. So this is like a growing project. It's already got wide adoption across multiple contributors and vendors. So that it's been widely received and welcomed for enabling Neutron in the container world. So I'll talk first a little bit about Docker since these are the more mature projects from Courier. So Lib Network is the project within Docker that focuses on the networking obviously. So there are various types. These are the, I put an asterisk for former because things sort of changed with Docker 112. But for backwards compatibility, they kept the three main ones, the null, bridge, and overlay. And then the remote driver which is where Courier fits in. But how do these play out with security? Well, no, obviously not really anything.  The bridge, IP tables, overlay IP tables, these are things that have been known to have issues and don't scale well. And then there's the remote driver which allows for some external third party organization to come in and leverage. And that's where Courier leverages Neutron. And so Courier's been working with Docker, Lib Network since 1.9. So as I mentioned, it's the remote driver. But Courier actually handles two things, the IPAM. Passing the IP addressing to the containers. And then also the binding that happens on the physical host. So from a networking perspective, you know, these from our, well, I'll speak specifically from a metonet perspective. Container can just be like an endpoint at the end of a virtual topology. So the way we handle it is you can build whatever virtual topology you want with whatever functionality. And to us, it just looks like a port. It's a virtual port. Just like the way we traded virtual machines. So there's not a lot of things that have to happen or change on the back end. We can leverage a production grade networking solution and apply that to containers. But so Docker, oh, so I did mention, yeah, Docker 112. So Docker 112 was announced at DockerCon, I guess back in June. What they did was they talked more about their clustering with Docker Swarm. And unfortunately, the only supported networking they had was the overlay solution there. So the courier project is hoping for Docker 113 that they'll have time to work with Docker and insert again as the remote driver. So I think Docker 112 was just released quickly and didn't have time for the third party vendors to insert. But the way the abstraction looks is the important definitions are the sandbox, the point and the back end network. And this is different from how Kubernetes defines networking in the fact that it doesn't define networking. Docker explicitly defines networks and subnets. So courier, what it does is it leverages Docker's push model for the architecture and when those calls are made to lib network, courier does a translation to neutron networking. So this allows any neutron solution to be leveraged within a Docker container environment. So it just does a translation. It makes the call according to what neutron is. Neutron has its solution and that solution goes and implements the way it always did before. And so that means you can apply a host of functionality to containers without having to wait for a particular definition. These things have already been well defined and proven with more solid production-grade networking. So a whole host of functionality that can be applied to Docker. So just one example, courier with Meadonet. Meadonet is specifically a neutron plug-in. So that's one option that I mentioned that could be used with courier. So basically when the Docker API calls are being made, courier is doing that translation to the neutron. So for example, it's providing the IP. And then what end up happening at the back end is each vendor or solution has a binding script. So that's what's happening locally on the physical host where the container might live. And so these calls are being made and the binding is created. And that way, the networking solution knows which exact figures of physical host the container resides on. And then after that, you have the freedom to apply all these networking definitions that were from neutron and have a production-grade networking solution. So that's courier for CNM. But now what's developed, what we've seen is there actually has been, we've seen from the sample set that we've spoken with, people have this adoption of Kubernetes. And Kubernetes doesn't have the exact same framework for networking as Docker. And so there's this other standard called CNI. So why is Kubernetes important? Well, it's already a proven solution within Google. So Google happened to open-source it. Of course, there are some... It was implemented differently at Google. But now that it's open-source, it's gotten tons of adoption in the last 12 months. We've seen huge growth. And even in the ecosystem, several vendors have supported this because of the interest. So I'll just go over a little bit of the Kubernetes architecture and then how it fits in on the networking side with Courier. So what's challenging with Kubernetes is it has more of a pull model. So that means any kind of courier in the end of the implementation has to watch for the events that happen in order to make any kind of configuration changes. I'll probably speak really briefly that almost sort of looks like OpenStack in the sense that it has this master node, kind of like the OpenStack controller. So this is taking care of the state storage, the API servers and things like that. And then where the work happens is actually on the worker nodes. And that's where you could consider compute nodes, where the containers and pods are actually living. So in the Kubernetes world, the definition is more of a pod that's supported by containers. And in terms of networking, you would look at it as an IP per pod. So these are more of the compute nodes from the OpenStack world or where the work's happening with the containers and pods. So at CD is where the persistent state storage taking care of that, these things are happening all on the control plane through the master node. The Kubernetes API server is running there, scheduler, the controller manager server. And Kubernetes is built in a way that all these things are supposed to be interchangeable and pluggable actually, that's probably a better word. So what courier is done, and on the worker node, there's these cubelets that are managing the specific containers on the worker nodes. And then cube proxy, which is kind of what you'll see with courier the way it was developed. It's basically providing a load balancing type functionality and implementing it through IP tables on the physical host. So keeping that in mind, the Kubernetes networking model strives to define itself with network policy actually, which is a series of labels applied to a service and that sort of therefore defines what's allowed and not allowed to talk. So more of a whitelist approach. But there's the distinct problems that they recognize are container-to-container communications, pod-to-pod communications, pod-to-service communications and external-to-internal communications. So one of the main default solutions for Kubernetes is Flannel. So originally, even in the early days, just like Docker, things were open and weren't necessarily doing nothing, but you couldn't have basically cross-host communication. So that in turn enabled or called for an overlay to enable cross-host communication. So an overlay just puts a tag in front of the packet. So one example would be like vxlan header to define the service and enable cross-host communication. So some of the problems with that, well, as I mentioned, so IP tables for netting and maybe security depending on how good you are with working with IP tables, because the definitions are not really there yet with the framework. And then multi-tenancy. If you're doing like a host per tenant, what happens with your physical host goes down? What happens to your units? What happens to the virtual machines? Just as a lot of people are happy with their tenant then. Other things to consider is, even with the movement towards containerization, people are still working with a lot of virtual machines. So not everything is immediately containerizable. So how do you share containers and VMs on the same network or the same solution? in the networking stack with everything on the same physical host. So I'll talk about some MidoNet integration with Kubernetes specifically, and career, but any neutron networking solution could be used with career. As I mentioned, this MidoNet came out of the company MidoKura, which has started six years ago. Our founders and our CTO, they had more of a distributed systems background. So they worked at Amazon previously, and that was their specialty and expertise. So when they built the architecture of MidoNet, it was specifically so that it was a solution that's scaled without any bottlenecks or pinch points. So it's more of a distributed systems type architecture. And then, of course, another highlight was in 2014, we went open source. So everything's available on GitHub. It's completely open. So what that meant is some of the way that the networking solution was achieved was actually at the edge of the network. So all the intelligence is at the edge. The edge only needs the information for the things like leaving the box. But that, in turn, also means the security. So if you have a policy or a firewall rule, for example, the MidoNet is simulating it at the edge. Pretending the packet goes through whatever logical topology was built, and if there's a rule anywhere that says drop it, it's not even going to leave the physical host. So it's eliminating these hairpins and bottlenecks to virtual network functions or even your perimeter firewalling, for example. And that's what gives it the ability to scale. So with Kubernetes, today, so this is Docker live network work that was done with career is a little more advanced. That's upstream now and released to work with Docker standalone and the old Docker swarm before 112 and then expected to be with 113 onwards. With Kubernetes integration with career, it's a little more new. Even with MidoNet, it's still in tech preview stages. But it works starting with Kubernetes 1.2, which is what was officially tested. And then the two integration points are the CNI driver that sits at every worker node, and that's what's doing the binding. So that's how the solution knows this container is on this worker node, and it's tied to this logical network. And then Raven, and that's the name of the process that's at the master node and is doing the listening for all the events. So any of the Kubernetes API calls that are made, Raven is doing the listening for that. So looking at default versus how it's enhanced by career to get these more advanced networking functions. So I mentioned Qproxy resides at the worker node at the edge server and then Flannel is one example of an overlay solution at the edge with a pretty simple, more primitive overlay. And that's enhanced by using the CNI driver that's residing at the worker nodes. Raven at the master node and then, in this case, MidoNet agent or whatever networking solution likely implementing at the worker node. And as you can see, the definitions are a little different than we saw with the container networking model. So there's a few more definitions here. Some of the isolation being achieved with namespaces. So a namespace would map to the Neutron API network. And then, as I mentioned earlier, a pod would represent a pod or something that might ask for an IP. And then, in the end, when you're defining a service, what makes Kubernetes powerful is you have these options to define a service of replication factor and then the load balancing that's checked on it. So health checks that are done, if one pod is going down, Kubernetes is going to bring another one up. But in turn, from a networking perspective, that is just load balancing. So the service equates to the load balancing VIP and these endpoints on the back end would just be these load balancer pool members. I will take a closer look at the worker node, as I mentioned. So the kubelet still remains on the worker node. We replace kube proxy, which was doing, figuring out the load balancing and endpoints. And that meant per host. Whereas now, MidoNet agent, which has a cloud-wide awareness, resides there and programs the kernel data path. So today, where are we, career and MidoNet, specifically? As I mentioned, it's in tech preview. These functions were done, the CNI driver, Raven, as the watcher, the namespace implementation, specifically done on CoreOS. As I mentioned earlier, CoreOS has made great strides to be the supporting operating system for these container orchestration tools. And what was interesting for MidoNet was we had one process that was running in user space, programming the kernel. Now all of our processes are actually containerized, so that's kind of cool. So I think that has more benefits even beyond just working with container orchestration engines. But specifically, or more broadly speaking, career, the bigger project, where will it go next? It will go and define more of bridging containers and virtual machines. So you can already attach containers to existing neutron networks, but more testing and consistency there. The multi-tenancy aspect, obviously, so that isolation across worker nodes and taking those aspects of isolation as well, allowing tenants to define their own security policies or administrators on top of that. Then of course, the more advanced networking services that come with Neutron, especially as these, the container networking model and container networking interface get better defined. They can map to already existing neutron components. QoS, of course, too, taking care of bandwidth from a networking perspective, traffic shaping, making sure things aren't being hogged and prioritizing maybe certain applications. And then of course, things of interest are working with other container orchestration engines, so adapting to whatever their API framework might be. So definitely, I think probably at the top of the list is working with Mesosphere. There's a lot of popularity there and CloudHandry and OpenShift. And then Magnum support as well, making sure that works. So Magnum in OpenStack is putting containers in VMs for isolation and defining bays and leveraging these orchestration engines. So Kurya will work with that project as well. So I think I sort of tried to whip through it because I know you guys are probably getting hungry, but wanted to make sure you guys got a little bit more education on these open source projects focused on security for containers. And as I mentioned, both of these projects are open source as well as of course OpenStack and Kubernetes and Mezos. But I thought I would just share some of the information so if these kind of things interest you or you know people who are interested in learning more about it and joining, we always welcome more community members, so. So thanks for your time. Hopefully we can all take a deep breath now because I probably talked your ear off. But thanks for your attention. Thank you.


Good afternoon and welcome to our social media corner. I'm Diana and I'm the social media manager at IAEA. Our scientific forum just kicked off this morning and it will continue tomorrow. This year, the forum is about how nuclear science and technology can help countries deliver cancer care for all. If you want to watch the afternoon sessions, check the link in the comment section. Now, I'm very pleased to introduce you to our next guest, Dr. Shekin Elmore. Dr. Elmore, a radiation oncologist and researcher, is our cancer survivor and it is our pleasure to have her here with us today, sharing her experiences and perspectives. Dr. Elmore, thank you so much for joining us today and welcome to our social media corner. It's my pleasure to be here. So, can you tell a little bit, our followers that are watching us online, tell us a little bit about yourself and how you came to be working in this area? Yes, as you said, I'm a cancer survivor and that's really how I came to work in radiation oncology. I was so inspired by the care that I received as a child and then later as an adult that I found my way into healthcare and eventually radiation oncology as well. And in your talks, you often say that you want to change the attitude of oncologists towards patients. What exactly do you think it's important to change and why do you think it is so significant? Yeah, so it's a great question. I was just talking to someone after I gave my talk, who's a radiation oncologist in Zambia and we were just talking about how some people really have kind of the technical skill and the compassion and I think that that's really what makes the best oncologists generally and radiation oncologists in particular. I think that oftentimes oncology can become a little bit distanced from the patient and sometimes you have so many patients that things inadvertently can become more like a number and I think it's really important to really bring it back to the individual patients and just remembering that the day that you're having, it may be the 10th, 100th patient that you're seeing that day that week but for every individual that's their only cancer diagnosis so I think it's really important to personalize and give as much compassion as you can. Definitely, definitely.  Can you explain to our viewers what are some of the benefits of using nuclear science in treating cancer patients? There are so many. I mean I think just radiation therapy in general, kind of meaning usually using high energy x-rays to palliate or cure cancers. I think the statistic has been quoted and probably will be quoted again. Really about half of people living with cancer will need radiation at some point in their treatment course and so it really means that radiation is so integral both for pain relief, you know it's really good at relieving pain, other symptoms, and a really integral part of cure particularly for patients with cervix cancers, childhood cancers, head and neck cancers just to name a few. Thank you, thank you. Diarrhe recently launched Resovope Initiative and this initiative aims to help countries fight the burden of cancer. How do you see the various initiatives in this area including Resovope coming together to complement each other towards a shared goal of tackling cancer? Yeah, I mean the Resovope Initiative I think you know as the Director General said is really raising hope because I think it really provides this centralized concrete framework that is really going to help countries bring new centers where there really is no center in the country which is true for 20 nations in sub-Saharan Africa to expand capacity for centers that are really doing well but could be regional centers of excellence and really lead the way in the region. And then for research because I think there's a lot more that we can learn about other uses of radiotherapy, the right dose, the right amount and I think as Dr. Abdel Wahab said to do more with less. There's so much that we can learn so I'm really enthusiastic about Resovope because I think it will be kind of this catalyzing force to bring all the other actors into play and coordinate them. That's amazing, thank you. Thank you so much for joining us today for this short but very inspirational and insightful conversation and I wish you the rest of a good scientific forum. As I mentioned before, our scientific forum is currently taking place here at the IEA headquarters in Vienna. If you are interested in knowing what's the role of nuclear science in the fight against cancer, check the links in the comment section so you can watch all the sessions. Also keep an eye on our hashtags, Atoms for Health and Cancer Care for All and let us know about the efforts that your government is making to fight cancer in your country. Bye for now and thanks for tuning in.


Good afternoon everyone So I like to talk about building capacity through the development of low-cost 3d printer what printed weather stations So this project is supported by USAID and the National Willow Service to build capacity to reduce risk whether whether related risk in developing countries through observing and communicating weather and climate information to rural communities So as most you know developing countries are some of the most data sparse regions in the world as shown on the map on the right One of the reasons commercial sensors are expensive and difficult to maintain in these areas So our idea is to come up with a low-cost solution to help with this problem So this low-cost solution is use 3d printer technology and micro sensors Which are relatively cheap these days to basically print and replace Instruments as they fail and allow met services to build their own instruments So here's a here's a couple images of our first prototype of our weather station or housing sensors and platform This is all run on a single board raspberry pi computer and the total cost is on the order of two to three hundred dollars So it's not very expensive So what are the components? So we've designed a built a wind speed sensor wind direction Precipitation gauge and then the housing components for the raspberry pi and other parts of the station We also have a radiation shield and in there we have the micro sensors for measuring Pressure temperature and humidity and the last step that we're currently working on is integrating solar power and Wireless communication so we can put these in remote areas around the world So how do you make a 3d printer weather station? Well first you need a you need a 3d printer High-quality plastic filament in some kind of computer aid drawing software CAD software to design design your Instruments so here's some of our our designs that we've developed So here's the design for the precipitation rain gauge wind speed sensor wind direction the radiation shield and then here's a finished product of the rain gauge funnel which In a pinch can be used for other applications So we've done some initial comparisons if you're wondering so this is temperature in relative midi Time series. I think our measurements are doing pretty well except for there is some solar solar heating issues That's required us to redesign the radiation shield. So this is research and development Good results from our pressure sensor. We're pretty happy there But we still have some work to do on our wind speed sensor as you can see there So it's not all all perfect and we're also evaluating our other other sensors at the moment So our initial project is focused in Zambia part of the reason that there's already an ongoing early warning project there And the idea is to extend our observation network and also develop and build new societal applications for that region So we've partnered with the Zambia Met Service. We've done our initial Our initial evaluation site survey last month Our first deployment is planned for February of this coming year With a more extensive network plan for about August of next next year And then start focusing on integration of these data into applications in year two and the plan is Have this project over a five-year period and hopefully we're going to expand to other days first regions such as the Caribbean Pacific Islands and other regions in Africa So talking to the the Zambia Met Service We've we want to focus on some set of applications early on Improving their flash flood early warning systems water resource management, especially for hydroelectric power We visited with local farmers for agriculture first for large-scale farming to substance farming and also there's there's a Fish fish farms there for ponds and also for health applications such as looking for malaria regions from malaria outbreaks So so I also think there's educational opportunities with this activity So such as integrating this into an university course say in atmospheric sciences to help them help students learn how to use the Instrumentation monitor, but also this could be an interdisciplinary course where you can bring in Engineering students computer science students to improve on our design Integrate help with the programming display of the data and so on so it could be a really a really great course I think and into the future And there's other opportunities I can think of one is you know science activities and primary and secondary schools They can help build and design their own instruments whether enthusiasts who want their instruments in their backyard and the great thing is that this is going to be an open research in the future So people can download and build their own instruments So with that I just want to mention this project was inspired by Kelly Spanberg Who's who's done a lot of work in this area over the years and unfortunately he passed away this past August So he'll be missed so thank you very much


Thank you, and welcome to the White House. I want you to know that Nancy and I are as happy as anyone could be living here with 100 MX's in the basement. It's such a pleasure to play host to old friends, especially those who over the years have made it their responsibility to contribute so much to resources and personal effort to conservative causes. So let me just offer you a heartfelt thank you for all that you've done to support our common ideals. Thank you as also for your efforts since I got to this current job, whether it was for reducing the growth of federal spending or cutting the tax rates or rebuilding the national defense, you've kept the home fires burning. Burning right under the feet of the undecided votes up on Capitol Hill. And it made a difference. I have often said it isn't always necessary to make them see the light, just make them feel the heat. Washington establishment, and if I ever think that means us instead of them, I'll have been here too long. Well, they have yet to come to grips with just how important the conservative movement has been to the shift in political power as represented by our administration. Non-party political organizations and political action committees play an indispensable role in mobilizing public opinion on critical issues. And this isn't to say that the PACs and other philosophically motivated groups have a perfect record, but at times I get a feeling there's a double standard applied to conservative political action committees.  Working together, we, the Republican Party, the conservative movement, the PACs, and the conservative-issued lobbies have come a long way. The foundation for even greater achievement is in place. How many of you, for example, can remember when it was almost impossible to find a conservative to speak with authority on an issue? Well, today, there are a host of vibrant new leaders out in the departments and agencies who are not only doing a fine job there, but who are also developing expertise in everything from defense to social welfare to education. Morton Blackwell, who's here on the White House staff, calls it the credentialing of the right. And it will reap benefits in decades to come. Hardworking men and women of this administration, and I'm proud of every one of them, have shifted the political center of gravity and turned around the national debate. Today, we're debating how much power should be returned to the states. We're debating how to strengthen our national defense, the right of school prayer, and the need for tuition tax credits. It wasn't too long ago that the only debate found us on the side of trying to fight a rearguard action against more and more social engineering and government spending and increasing size and power of government. Perhaps no one better exemplifies the change that has taken place here than our United Nations Ambassador, Jean Kirkpatrick. And I am grateful to have her on the team and proud. I see you have kept aware of what's going on. The first time in years that we've had someone aggressively, with no apologies, representing the United States and the cause of freedom at the United Nations, she sent a little series of identical letters around the shop after there had been some intemperate remarks made about us, and she got 27 letters of apology. But after a long period of vacillation and despair, we've again rekindled the torch of liberty, reclaimed America's legitimate leadership role in international affairs. And we're finally on ideological offense against tyranny. Remember how appalled we all were in past years when representatives of the United States appeared apologetic in the face of some of those vicious diatribes? Well, believe me, those days are past. Jean and our other representatives aren't sitting back silently and taking that verbal abuse anymore, as I just said. Today, our representatives speak the truth, loudly, clearly, and with pride. We must and we will have peace with the nations, with whom we have fundamental differences. But today, our adversaries understand that we will not hesitate to promote precious ideals that are the basis of our free system. We're also taking the offensive domestically in many areas of longstanding concern to all of us here today. Thomas Jefferson said to compel a man to furnish contributions of money for the propagation of opinions which he disbelieves and abhors is sinful and tyrannical. Well, it's no secret that for some time now, the government has turned a blind eye to the misuse of federal funds for blatant political forces. And we're now taking steps to ensure the federal grants and contracts will not be used to finance political advocacy. So those engaged in political clauses can do it with their own money, not the taxpayers' money. As you know, two years ago, we promised the American people we'd make America strong again. But we have put in place a program of tax rate cuts, spending controls, and deregulation that is just now coming to bear on the long-term problems that we inherited. I'm happy to tell you that I remain unabashedly confident and with good reason, America is on the mend. And now that situation has begun to turn around, I hope you'll remember and remind all your friends and neighbors about the politicians who wanted us to go back to the tax and tax and spend and spend inflate and inflate policies of the past, even before our program had a chance to work. And when you're talking to friends, I hope you'll also explain to them just why we had to maintain a strong national defense. You understand or you wouldn't be here today. But you know, many people, including conservatives today, have heard this drumbeat about that's the place where the money is going in the wrong direction. So much that a great many Americans aren't fully aware that we're making up for decades of neglect to the security needs for today. And today, just as it's always been, strength, not weakness, is the greatest guarantee of peace. And in our country, peace and freedom depend on understanding and the support of the people. You and the organizations you support, whether it be Americans for Change or the Fund for the Conservative Majority or the National Conservative Political Action Committee, you've done so much over the years to inform the American people about the chance, the choices that we face. And I have a last request, don't let up. There's still a long way to go. Our greatest accomplishments lie ahead. I thank you again for being here, but having said that, I realize that there isn't any possible way that I can have the time to mingle and to talk with each one of you as I would like very much to do. I found that's one of the drawbacks in this job. They've also always got something scheduled right after something. But I would like to take, and it could only be for a few minutes, but I'd like to take a few minutes and maybe we could have in one sense a dialogue here, even though I can't get down and mingle the way I'd like, but I'm sure that there must have been times, particularly if you read the same papers I read when you have said to yourself, boy, if I had a chance, would I ask him? Well, ask me, yes. I'm going, no, I'm not reaffirming the Monroe Doctrine, but in my speech on foreign policy, which will be, well, as a matter of fact, I made it already, not soon. I made it this morning. Yes, to the American Legion Convention, National Convention. And I did outline what our strategy is in contrast to those who say we haven't got one. We've got a pretty busy one. And I took care of Latin America very well and emphasized its importance to us and the fact that we are not going to abandon those democracies down there that are being invaded by imported subversion sponsored by the Soviet Union and Cuba. And we're going to keep on doing everything we can to help. But I'm going to take your question in just a second, but I have to tell you, if you haven't heard it, it's a terrible story. It's a deathbed story. But when Brezhnev was leaving the world and he asked Yuri and dropped off to bend down and he said, Yuri, make sure the people follow you. And Yuri said, lay on it. If they don't follow me, they'll follow you. Yes. Yes. Well, at times with all of this talk about their job bills and what they want with those, I'd like to point out that the decline in unemployment that took place in the month of January would have required a $5 billion jobs bill to have the same effect. And we got it without spending anything. Now, we've got what we think are some legitimate things. And that is, in our budget for 1984, there are many departments and agencies that have asked for funds for necessary maintenance, repair, construction, and so forth. And we've conceived of the idea and proposed. And I must say that the leadership and the democratic side has listened and is giving full consideration to simply moving up some of those projects and doing them starting now in this year in which they will directly and indirectly create additional jobs. And it doesn't mean that we're adding spending to a budget. We'll simply move it up and spend it a little earlier, get the job done, and get some people back to work. Incidentally, on your question before about the Monroe Doctrine, I think you should know that it isn't our opponents or adversaries. It is our own allies and friends in Latin America who found themselves chafing under the Monroe Doctrine. And they do not want it reapplied. They felt it had a kind of a sense of big brother taking care of them. So big brother's just going to be a big friend. I have to say, I think it is too early to say that one, no, first you would either be then accused if you said one thing of doing everything for political reasons, or if you said the other thing, you'd automatically be a dead duck. I have said, though, that I think the people let you know whether you should or not. And I want you to know I will remember your reaction. I have to say that I can't give an opinion on it yet because we're going to look at that. We're going to study. We all of us believe here that one of the things is not only the amount of the tax, but there's no question our tax system has become so complicated that simplification is really called for. I think many people's resentment is not to the amount of their tax. It's to the difficulty of computing it anymore.  If you make a mistake, they'll find you. But it's very true that that will be one of the things that we're going to be studying and looking at. As you do look and start to study, you find there are some drawbacks as well as some advantages. But we're going to give that full consideration. There was a lady back here and then I'll come over. Oh, well a lady here and then a lady there. Yes. If I understand you correctly, were you asking about and why we have not gotten more circulation on our private initiatives and the thing that the people are doing voluntarily? I wish I knew. I really do because I'll tell you, the thing that has struck me is the constant drumbeat of gloom that is on particularly TV news. The other night when they were talking about the drop in unemployment, they then followed it with finding a couple someplace that had to sell their car and their furniture because they were unemployed and all this. We have had for a year and they finished their task now at a private initiatives task force, volunteers, all of them and they have gathered up all over from this country what people are doing at their community level, the state level, private level, to meet many of the problems that over the years we've come to think of belong to government, that they should solve them. And we now have a computer bank here in the executive branch with a team there that has over 2,500 programs that are either partnerships between the private and the public sector or completely private solving everything from school dropouts to food programs, to programs for the elderly, every kind of program you could imagine. And now any community, any group that has a problem and wants to find out can call us and incidentally we've put out a great many brochures nationwide advertising this where we can put them in touch directly with the people that have solved these problems at their level, at their community level. Things like Midland, Texas where they have Christmas in April, you've probably never heard of that. Well Christmas in April is every April, all year long they have been collecting the information on people's homes, needy people, elderly people, handicapped people that need repairs, refurbishing of some kind and in April, volunteers, business people, lawyers, doctors are out there with paint brushes, hammers and nail saws, they put on roofs, they repair plumbing and electrical work, rewire homes, they paint homes and so forth for these people and it's done every April and they call it Christmas in April. And it's just a program they've found out to refurbish their community year after year. Now I know about High Frontier and I can assure you we are not evading or neglecting looking at that principle. We're looking at it very closely. I shall be very pleased to do that and I know that in about just three or four minutes I've got to leave but I will come by that way. Yes. Didn't, did I understand correctly? Did I say, am I aware of how many people pray for me? Well, I have to tell you, I believe in intercessionary prayer and I believe that without being told but many people have told me, I would know that they are and the only thing I do want to say to you if it's that sometime when you are praying for me if you get a busy signal, it's me in there ahead of you. I would be very, I would like to have, is there a return address on there? Huh? All right. I love letters and particularly, I love them from, I love the letters that I get from children. They're just, they're wonderful. Oh, and then I get to, all right. Where is it all going to end? A campaign on a balanced budget and now we have budget deficit bigger than ever and where is it going to end? If I can't do it, who could? Well, 50% of the present deficit is recession caused. The possibility by 1984, we could balance the budget. By the time the election took place and before we came here for inauguration, the economic conditions had so worsened, 21.5% interest rate, unemployment had continued, inflation continued for its second year, increasing double digit for two years in a row, back to back, well, all of those conditions that we had to alter again, our figures, but again, with the best projections that we could get and less optimistic than they had been earlier. No one foresaw and no one that we talked to or anyone else had projected that deeper slide. They call it a separate recession. We had a recession that started in 1979, went all the way through 80 and was continuing in 81 and then fell off the cliff in July. I'm interested when I hear a Senator from Massachusetts blame our economic plan for the recession. The first installment of our economic plan didn't even go into effect until October 1st. The recession, the big dip was in July, but it has changed that because for every one percentage point of increased unemployment, you have to count about another 30-odd billion dollars added to the deficit. That is an outgo for benefits to people that are now unemployed and in need and loss of tax revenue because they're no longer working and paying taxes. But the plan that we've submitted for the 84 budget, the Congress will pass the first time getting at what we call the entitlement programs. We have found that, you know, the President has to project for five years ahead and I do it with my fingers crossed because I don't think any economist in the world can project more than one year ahead with any degree of accuracy. But what we've done is the rate of spending increase was running at 17% a year when we came here. We have reduced that down to where for last year it was about 11%, 10 or 11% the rate of increase. In the 1984 budget, it will be down to 4% or 5% as a rate of increase. So what we can see now, if we have the cooperation that we want up on the hill, we can project two very sizable deficits, no question about it, 83 and 84, but then a declining pattern. Even with our modest projections, we deliberately have said we're going to project a rate of growth in this recovery that we think has started, in fact, we know has started. We're going to project a modest rate of growth and even with that we will have a declining pattern in which you then can look ahead and see where the two lines will cross the spending and the tax line and we're inclined to believe that the recovery is going to be a faster growth than we have anticipated which would bring that up even earlier than that. But I do think we can do it. But when I mentioned the entitlement programs, these were the programs that are actually spending is built in, the increase in it. And so the Congress didn't have to raise the spending bills. They just automatically increased. Well, these are what we're getting at, the things called the entitlement programs. Incidentally, with all of the criticism of defense spending, over the recent years while defense spending was declining by 20%, those programs I'm talking about were increasing by 122%. And this is where the runaway government, the uncontrollable feature of government, could be found. So. Those two are the messenger. They told me you've got time for only one more question. I thought they said vice president. I looked at them. All right. I think they're expecting you elsewhere. I'd promised this gentleman here, so this will be the one. I looked around and I'm sorry. My goodness. I want Texas to switch. Maybe Jen Ryder will switch there. Oh! Oh! Oh! Oh! Oh! I'm sorry. I think I do. I have to go. I can't take the rest of them here, and I wish I could. But I can't. And I'm very happy to leave you in the capable hands of George Bush, who came back from doing a magnificent job with regard to our disarmament proposal. And both of us only do well because we're backed by a couple of wonderful gals. Well, I thank you all for being here. And God bless you all. And I'll answer these letters. And George, I'm sorry. After you leave, I think there's a reception in the other room. No, we'll follow you out. But I think the reception down the other room. All right. I won't forget the names. Can I take one second and tell our story?  I said so many about economists and all. I have to tell you, this is a story, and I don't mean to be, well, frivolous about religion or anything. But three gentlemen, it is said, arrived at the pearly gates. And St. Peter told them there was only room for one. And he said, we've decided inside that the one who is practicing the trade or profession, which is the oldest, can come in. So a man stepped forward and said, I'm a doctor, a surgeon. And he said, we know that the Lord made Adam, and then made Eve from a rib of Adam's. That required surgery, so I guess I'm the one that goes in. But before he could move, one of the other two said, just a minute. He said, before God made Adam and Eve, the world was chaos. And he spent six days making the earth. So I guess he was an engineer, and I'm an engineer. He started to move. And the third one said, just a minute, I'm an economist. Where do you think they got all that chaos?