12 million acres burning in Australia. The Queensland fires, they are bad. Estimates over 14 million acres. They are horrific. Give it farmers from clearing their own land. It's too dangerous to burn. It's global warming, it's global warming. Unnested know-how for length. Prime Minister has declared any length. The aboriginals, they were very aware of the dangers of corning. Greening thousands of years, getting to know that landscape. Connecting to that landscape. Over the top restriction. And the clearing isn't working. The break we're going to light up off today is Katang break. This is a priority for the state, is to keep plan burning happening. So this is the biggest problem with doing our hazard reduction burns. You've really got to try and get the weather right. It's got to be not too hot, not a lot of wind, still a little bit of humidity. Because we don't want to rip and roar and fire going through here. We just want it to nice steadily go through. The drought factor as well, are all factors in which we take into account when we're doing the plan burn. And so if all of those tick the right boxes, we know that we're going to have a lovely result like this. Plan burning is undertaken for a variety of reasons. Hazard reduction is just one of them. We also use plan burns to maintain ecological processes, to manage weeds, and to manage pests. The point of the burn is to remove the understory fuel layer. And so that means that if a wildfire comes in later on, it's not going to have that fuel on the understory. And therefore it's going to have a lot less chance of actually getting up into the pop story and taking off. There's three main factors that influence the fire behaviour, the fuel, the weather and the topography. The fuel is the only thing that we can influence out of that fire triangle. It doesn't really matter if it all doesn't burn out. They get a 60% burn. I think that's about all they're asking for in this block, which will give it a good mosaic pattern. There's all these mosaic burns and pathways for animals to escape and survive. You can see where we burnt previously, just a couple of weeks ago. Now it's cleared the country beautifully and it also prevents large bushfires in the wet because you now have a mosaic pattern. It doesn't guarantee fire won't pass through there, but when it comes back through, rather than it being a raging fire with 30 meters flame height, it's much more manageable. As you can see on the bottom of all our trees here, we've got very little scorch. If the fire goes through too hot, it encourages a lot of the bad weeds, so the antennas and all that sort of stuff to come back kills off all the smaller trees. So just this nice steady fire is exactly what they're after. We work alongside and with the farmers, the pastures, the airports, the mines, et cetera. The whole landscape's changed through industrialisation and western colonisation, so how do you do that safely where there's all these other interests and infrastructures that didn't exist with just simply traditional burning? It's highly complex, and even though it's our bread and butter and Qfish's bread and butter, it's a highly complex interaction between forests and fuel, weather, the climate. And all we're about with these all these firemen, we've trained over the mainstream rural firemen. These farmers are quite skilled in what they do. Rural firemen are going very highly skilled blokes, very committed. All we do is add a few tricks and tools to their tool bag. We utilise lots of other mechanisms, planning controls, subdivision design, house design, access, maintenance, all of those other issues also help reduce the likelihood of house loss during bush fires. But by itself, planned burning is not going to be the silver bullet. So if the weather's not right, we just can't get the burns done. Now, weather conditions have to be right and favourable to do the burns. And if they're not, they're not going to like the match.  There's been some really good analysis done by Dr David Jones from the Bureau of Meteorology who's looked back at the weather observations for Queensland over the last 68 years. And that analysis has indicated that there's been a general warming trend across Queensland, and particularly in South East Queensland, an increase in both the severity of the fire season but also the duration of the fire seasons. Going back to last season, we actually had our first observation of catastrophic fire day durations in Queensland. And we also had quite a prolonged fire season, not just this season, but also the previous one as well. From a firefighter's point of view, it's a fair thing to say we've had more bad fire weather days in recent years than we have in the past. And that's a very challenging thing. And also the worst of the days have been worse than anything we've recorded before. Just got to the stands all the way. This is all we got. It's no good. We were in some streets in town there, and the embri-tac was going two streets over. We had a strong prevailing north-westerly wind. So it was basically pushing the fire directly for the western side of Standthorpe Town. Backyards were catching on fire. Frontyards were catching on fire away from where the fire was. And it was so unpredictable because the wind just kept swirling. It kept changing. When the fire front travelled through, it hit an existing burn scarf from a joint hazard reduction burn activity undertaken between QFES and Queensland Parks and Wildlife a couple of months ago in the Broadwater State Forest. And that hazard reduction burn was instrumental in helping to shape that fire and to reduce the areas that were impacted by that fire. If that hadn't have been there, we would have had a very active wall or fire front moving towards those houses. I have no doubt that the loss of property and potentially the loss of life would have been a far worse scenario than the one that we've currently experienced. Hello everyone, good afternoon. I think the whole issue of hazard reduction targets is a difficult conversation to have. It would be easy to burn large swathes of Queensland to hit a target, but you've got to have the burns in the right area. If we do lots and lots of prescribed burning, then we're going to generate lots and lots of smoke. So that will potentially have impacts on things like respiratory illness, impacts on other industries, so vineyards, horticulture, tourism, all of those sort of things will be traded off as well. We'd rather be focused on the most difficult to deliver burns, which are often close up against communities. And it may be that some areas we don't treat and other areas we treat very frequently. Without having those targets, then you really don't have anything to drive your program towards. The question you ask is around the clearing of land in relation to protection of property. There's a lot of things you can do, but when you get to a point of where you're not sure, go and seek clarification. When you were talking to the land holder, he wanted to put a fire break up through here and one along here. So category A vegetation and category B vegetation is the blue. The Queensland government, under the vegetation management act, we regulate this blue and we regulate this red. And there's no restriction on him putting a fire management line through here. The person who's on the land, who's managing the land needs to take responsibility for managing the bushfire risk on the land as well. Land holders can build fire management lines. So like the one we see behind us, fire management line is a constructed line up to 10 meters wide that you can put on your property. We encourage you to talk to the local firewood and about the best placement of those. It's good to have a straight, well-maintained line where you know you can get to water, you know you can get away from fires, you know you can access fires. Nine times out of 10, near the fire management lines, they're lower amounts of fuel loads. So that means there's lower flame hight. For crews, that's a safe area to attack the fire with their hose lines and also other appliances. Around infrastructure, such as their house, significant water infrastructure like their tanks, you can clear up to 20 meters wide or one and a half times the height of the trees. So you can see the trees here are over 20 meters tall, which means that you could construct a break around that infrastructure of at least 30 meters. We have rural fire brigades throughout Queensland that are there to support you as the property owner to conduct hazard reduction burns. But basically if it's beyond two by two meters, so beyond one meter in any direction, two meter in diameter, you're gonna need a permit. Doesn't cost you anything.  So we've got a couple of thousand fire wardens across the state. If they're doing their control burn and some of the vegetation dies as a result of that, that is exempted from acquiring any permit because they have that fire hazard reduction burn permit from the local fire warden. So that can be a legitimate use of it to keep it open for grazing and country healthy. When that can go wrong is when it's done too dry or too hot and ends up damaging trees and becoming out of control and that actually changes the forest structure. If you talk to your local fire warden and ask, then may well be possible to get the local brigade to come out and give you a hand. We do something, I believe it's over 2,500 of those a year or I say we, it's actually our fantastic rural fire brigade volunteers who deliver a lot of these. We can't guarantee we'll always do yours but if you come and ask, you may well get a lot of help and certainly you'll be able to get some advice. Well, basically in most of the catastrophic conditions you're actually trying to control the fire is almost hopeless.  When I was younger working in forestry I remember a fire jumping the Palmerstone Passage.  And so all of the heavy fuels, so trees, fire would just race up those trees, get all of that back and send it over to the other side and all the heavy fuels, so any logs and stuff that were on the ground would just catch a light and stay a light for weeks and weeks and weeks and weeks and you put water on them and they just wouldn't go out. You know, catastrophic days are basically the fire does its own thing. We can't manage it, it's just about keeping people out of the way. So it's all about public safety, keeping people alive and moving people out of the way of fires and waiting for the weather conditions to become favourable so you can start to manage them. There is a limit to our ability to suppress fires and we're seeing this at the moment where fires are too intense or too fast moving for us to be able to deal with them and that's first and foremost from a firefighter's safety point of view but secondly just purely from the scale and size of these fires. The rate of extreme fire weather is also on the increase in Australia so that trend is already there and given our temperatures are only going to increase into the future then there will be a trend in I guess more extreme fire weather conditions. We're getting more intensity in the fire weather which means that in any given place the conditions will be worse than they used to be. Maybe not every day but some days for sure and those big fire event days have a big impact. So I think we need to be really careful that this is not the new norm. The fires that we're seeing at the moment are I guess a taste of what's to come so conditions of forecast have become worse than this so longer fire seasons, more severe fire seasons so therefore one could expect for fires to become worse than what we're currently experiencing. The fire will probably become a bigger thing in Queensland in the coming years given we're going into a hotter and drier climate. All of this is about risk management. There is no guarantee from any one measure. As a community and as a society we need to have an understanding and an acceptance of the fact that we live in a bushfire prone environment and we'll continue to do so and there will always be fires in the landscape. What you can do is have a lot of attention to what's around the immediate environments of your house. So if you were to protect your house by having it really tidy having all the gutters clean and all that sort of thing that's pretty important to understand. The really important concept here is that there's a shared responsibility so it's not just the responsibility of governments to manage this but it's across everyone in Queensland. So from private landowners through to land management organisations through to governments. So we all have a role to play and there are multiple tools that are going to contribute to us managing risk. This is the complexity of managing fire in our environment and managing fuel loads and fire risk. It's about prioritising how we reduce the risk in those areas and then putting in place a suite of measures to deal with that which includes putting in fire breaks. It's about using mechanical means to reduce fuel such as slashing and it's about using fire where we can. So use of fire in Australia is a very complex issue and unfortunately there is no simple answer to it. I wish there was.


Hey, folks, Ned Pyle here again. Today I'm going to talk about a new feature coming to Windows and Windows Server. It is SMB compression. You have been using compression with zip files and other technologies, probably your entire IT career. And what we are adding now is the ability to inline compress while you're copying files, saving you bandwidth and time, especially when you're moving really big data. So let's show this in a demo real fast. So here's my usual Robocopy job I'm running. I'm copying a 10 gig file. It's a pretty compressible file. You know, it's sort of like a VHD or an ISO or something like that. And you can see that it's using a lot of network right now, quite a bit of the actual network bandwidth. And it's not copying particularly, you know, slow. It's copying at the throughput that I would expect for this, you know, network with its amount of congestion on it. And I'm going to time compress this just to save a little time here in the demo. I'm using a few, you know, small percentage of CPU. It's not so bad. I'll copy it in about two minutes, which is completely expected best case for this one gigabit network. So now, what if I was to do this exact same operation but with compression? So I'm going to delete this file off the destination. Oop, and let's go ahead and try this again with Robocopy. This time with a new option that's been added to Robocopy called compress. That's going to turn on the SMB flag to do compression. And you can see right away that I am going way faster. You can see that my network performance, my network usage is way down. I'm barely touching this network now. My CPU is not appreciably that much different, you know, six or 7% give or take. And it's really almost done. I have not done any time lapse. In fact, we're finished now. And instead of taking two minutes, this period here was only about 23 seconds. So that exact same file, 10 gig, instead of two minutes, 23 seconds. Now, what if that file was not very compressible? Let's say it was an extremely well-designed file format, JPEG or something like that, that already has an enormous amount of like, you know, compression built into it itself. So here I'm copying a file which really doesn't compress at all. And I'm getting that same throughput I was before. And I'm really kind of worried. This is a five gig file, so it took about half the time. It took about, instead of two minutes, it took about a minute. I'm really kind of worried this time that what if I was to try and copy files that won't compress and I have compression turned on. Would that make it a little bit slower as it wastes time or actually perhaps even uses more CPU just to find out that the file, you know, couldn't have been compressed anyway. I mean, how do I even know sometimes? So I'm using the compress option. Notice that it took the same amount of time. We actually sample as we compress, even when you put the flag on to see if it seems like the file is compressing well or not. And if it doesn't, we just ignore your flag and carry on copying the file normally without compression. Pretty slick. So that was the demo. I hope you have found it interesting.  And as time has gone by and proven to us, files get bigger, not smaller. So SMB compression is there to help for you in the future. For more information, check out the URL on the screen here somewhere. And I will talk to you later.


One of the most memorable things about hopping online a new game is a new player experience you get.  How fun it is the first time you pick your character, load into the game, click a button, and then the controls activate 17 seconds later. And then you buy Ethan an adapter because, believe it or not, that was probably the least laggiest person you'll face all day. And League of Legends, when you first hop online, you know, you play your heart out.  In fact, yeah, you are killing everyone. You're taking all the objectives.  Oh man, that's my boy. I taught him everything that I knew. And then you make one mistake, and all those compliments turn into a 25-page essay, and allow you to be best friends with a rope and a ceiling fan. And ask when you learn about the Mute All button. And then there's GTA Online. Oh, what, you thought there was something after that? No, because this game is a void.  Unlike Smash Bros. and League, there is no saving grace to make the flaws of the game feel any better. Hey, but kneecaps, why are you talking about a game that's seven years old?  I made the mistake of booting up this dinosaur of a game a few weeks ago. A friend of mine said, Hey, bro, I heard GTA put out this new heist, man. Come on, bro, hop online.  Why not? This is gonna be so fun, but it was not so fun. In fact, it was the opposite of fun. Not fun.  Hey, what's going on, my GTA friends? I haven't been on this game for like a year and some change. I hope you're all doing okay, though. Oh, well, I'm just gonna go drive to my friend's house so we can start up a mission if that's okay with you guys. So I'm just walking on a Los Santos sidewalk and... Wow! Wow, this level 300 nigga on a flying bike. Like the Wicked Witch of the West shooting a lock on missiles. He sees me and he's like a level eight player walking down the street with no weapons? Finally! A worthy opponent! And then he starts killing me over and over again. So then I was like, you know what? Let's just hop in another server. So we hop in another server and it was even worse. And what could be worse than a flying bike that shoots homing rockets? Now, what you expect me to say is two flying bikes that shoot homing rockets or something like that. But no, even worse than that, a hacker that can blow everyone in the room up with the click of a button every time you respawn. So then I hopped in another server and lo and behold, who could ever guess?  And the thing is, you think that dying over and over again is what would make me mad. But it's not. It doesn't.  Even though they're so dumbasses for using a bike, you know, let's not get that wrong, there's a speck of respect I can grant them for not just opening up their wallets and then dumping out all their money to be good at the game. What I have a problem with is that the majority of the people that have this spike are the ones that dump all their money out for this game. Oh, I can see it now. After my can't beat this guy, he's so much better than me. Mommy, daddy, please help me.  What? No son of mine will get beaten in this old-ass Godforsaken game. Here's all your college fund money.  The cherry on top, you know, the cherry on top. Like, I'm already upset. I'm already getting heated. I'm getting, you know, rocketed repeatedly while I'm trying to shoot them down with a pistol that I found behind the dumpster. I'm on my knees begging, please, bro, please. I just wanna play the game, bro.   And you know what? As much as I hate to admit it, you're right. I can't beat you. No matter how hard I try, I'm completely powerless. But you know what you can't do? You know what you can't do? You can't tell me the last time you took a shower. You can't tell me the last time you received oxygen from the outside air. You can't tell me the last time you felt the touch from someone of the opposite gender.  And funny enough, I don't harbor any hatred to these griefers. No, no, I don't. You know, I only feel sorrow and pity that someone can actually have this sad of an existence. But one day, one day they'll turn their lives around. You know, one day they'll learn about the wonders of soap and deodorant. One day they'll find a girl who loves them just as much as they love her. And they'll go on all types of trips. Hawaii, Machu Picchu, everywhere. They'll get engaged. They'll get married.  All right, put them. Instagram and Twitter clout. And.


Okay. So hello, everyone. I'm Barry McClearn, and this is Matt Rooney, and we're from SAP UK. We work in the cloud architecture and engineering team. And what I just want to talk today about how we have integrated additional open stack services into our bare metal as a service solution. So SAP has been aiming to consolidate a number of cloud platforms that we have internally around the shared open stack layer for the purposes of making the best use of our resources and infrastructure. So we want to talk about how we have leveraged open stack and re-architected the solution that we previously had to better make use of it. So I'm going to start by just giving a quick overview of what we do in the cloud architecture and engineering team. And also what we've done since the last summit, which was in Austin. I want to talk a bit about how we've re-architected our solution, how our new design has actually made it much more beneficial for us. Talk a little bit about some of the issues that we've faced when we attempted to do this re-architecture and then what we intend to do from here. Okay. So the infrastructure that we work with is we call it the infrastructure pod. And for us, that just means it's a standardized set of infrastructure where we have a number of nodes, or Burmese nodes from a single vendor within a number of racks connected by top of the rack switches. And then they are connected over a high bandwidth interconnect to another rack with a mass shared storage solution. So on top of this, then we deliver our hand of landscapes to our customers. And the benefit of this infrastructure is that it's optimized for performance, scalability, reliability, and security needs of our customers. And you can see that when we're talking about our nodes, we're talking multiple terabytes in order to support our in-memory HANA database applications. Okay. Within our team, then we work on a solution called Cloud Frame Manager. And Cloud Frame Manager is Burmese as a service solution that we use to manage the lifecycle of our infrastructure resources in the infrastructure pod, and deliver our hand of landscapes for our customers. So Cloud Frame Manager, or CFM as I'll call it, acts as a control plan for the Burmese infrastructure. And it does things like our server provisioning on our Burmese. It also sets up all of our network interconnect and our, sets up storage management. There's a diagram there, sort of giving a quick, brief overview of Cloud Frame Manager. Okay. So as I mentioned before, SAP actually has a number of these Cloud Platforms, and there is an internal push to consolidate them so that we can make the best use of our internal resources. And the plan is to build all of our platforms on top of a shared open stack layer, so then we can use the same infrastructure. Okay. So we actually presented some of this work at the summit in Austin in April. And it was basically our first steps into building open stack into our existing solution. And that involved integrating with Standalone Ironic to provide the Burmese provisioning for local nodeboot, which is not something we were doing previously. Previously, we were using all of our nodes with NFS root solutions on a shared storage device. But we had certain customers that required local boot. We actually have this solution running now live in our data centers with live hand instances for our customers. But based on this, we had a look at our solution, and we saw ways that we could improve it. So at the start of the year, we began to look into how we could re-architect our solution to be more flexible. So CFM was designed with a specific use case in mind, a specific stack with a HANA instance on top of maybe multiple nodes, which we internally would call a frame, which also includes the network setup and the storage. But our solution, because it was tuned to this single use case, was less flexible. And since we had already done some work to integrate Ironic into our solution, we saw there was a potential to move even further towards OpenStack with a much more flexible design. So with this architecture, we moved to something a bit more componentized, where we could build it on top of individual OpenStack components. And we actually made use of the OpenStack API in designing our own API to make it as flexible and improve interoperability with our other cloud platforms. So we've now integrated additional components, such as Keystone, Nova, Neutron, and Glance, as well as continuing to use Ironic, but no longer in a standalone manner. So you can see we have a diagram of our re-architected solution. So we still have a number of ways of interfacing with our API. As we call into our API, we now call into an authentication back-end, which is actually Keystone. The requests move through a number of plugins. So one of the plugins we have is to contact the OpenStack API directly. We also have other plugins to perform other operations, which are not necessarily into OpenStack, such as to deploy our HANA instances. And with this sort of combined solution, we are able to control our entire infrastructure and set it up for our customers. So I just want to move into talking about a couple of the problems that we faced and how we actually worked our way around to get a solution. Some of them have involved upstreaming our code, some of them have involved being a bit more creative in terms of our worker runs, but I'll go through each one. So the first one that we had is that we need to do read right as we're provisioning. So Ironic actually does provide read configuration automatically, but it's done during the cleaning phase. And for us, this wasn't a workable solution, because we need to provision the node for any customer, and our different customers will have different read configurations in mind. So our solution to this was to actually store the read configuration that we require in the flavor, has specific flavors for specific stacks of different customers, and we passed this information to Ironic at the point of provisioning. So the first step in this is actually to store the read configuration in the properties of the flavor. So this is one of the blocks of metadata that we can store arbitrary data and extract them later. The problem we found that there's actually a 255 character limit on each of the property fields. So our workaround was to have a non-standard schema. So Ironic has a JSON schema for defining your target read configuration when it gets sent to Ironic Python agent. So to get around this, we actually used a positionally significant array of fields in order to store some of the same data. So you can see an example there where it defines the name of the read configuration, the read level, so you can see the first ones are just read one. And the next one is then two, as in the number of drives that you want to read. The type of drives, the size, and a flag that sets whether or not it's the read volume. So we have one read volume and one non-read volume, and in the non-read volume we also have to set a mount point, which we use in our own solution to determine where this additional volume should be mounted in the file system. So then whenever we have selected our flavor and are deploying our instance, we actually pass this information to the Ironic node whenever it acquires the instance UGID of the server that we are provisioning on it. We have one more issue there where when it's in the deploying phase, it's locked, so you can't actually modify the Ironic instance. So what we had to do is wait until we're in wake callback and then parse the information out of the note info whenever Ironic Python agent starts. So additionally to that, then we wrote our own custom hardware manager and Ironic Python agent, which picks up the read configuration that's passed to it, and then actually modifies the Git OS install device workflow. So before the actual OS install device is set, we actually perform the reading then, and then we are able to get the read configured drive as the OS install device before the disk image is written. Okay. So then the next issue we had was Neutron VLAN isolation. So this was actually mentioned earlier, the multi-tenant networking in Ironic. So previously in older versions prior to Mitaka, Ironic only supported flat networks. Neutron actually does support VLAN segmentation, but Ironic wasn't integrating with Neutron to provision the servers on the tenant networks. So the issue here was that we weren't storing the information about which port each of the Ironic ports for a node were connected to, which didn't allow us to then isolate the traffic on specific VLAN segments. So we worked on this with some of our partners and actually upstream this bit we've worked into Neutron and Ironic. So we actually added the segmented network support into Ironic with its Neutron integration. So there was a number of changes that needed to be made there. We had to change the discovery process in Ironic Inspector to pick up the information about which switch port the network interfaces were connected on. Obviously that also required changes to the OpenStack database to store this new information along with the port information of each node. We also then had to make a change that allows us to pass a single port to Neutron rather than all ports at the same time. And then finally we had to work on ML2 driver implementation to add the VLAN setting to the interface. So the good news is that this is now live. It's been available since Mitaka and it's also in Neutron. And we're also currently working on adding port group support. So we do a lot of port bonding in Cloud Frame Manager. So this is something that will also be beneficial to us. So that's in progress or not. Okay, so the last issue I want to talk about that we have had problems with is node locality in Nova. So as I mentioned before in the infrastructure pod, we have a number of Bermetal nodes in a single compute cluster. And then we have multiple compute clusters that then share a storage node on another rack. The problem we have there is that our HANA instances would need to share the same storage node in order to get the best performance. So we need to know which set of nodes we are provisioning on. So Nova does currently provide affinity, anti-affinity, but this is for VMs only. So this doesn't quite give us the solution so that we can determine that we have selective nodes all from the same infrastructure pod. So our solution was actually to implement a pod or scheduler filter into Nova. So all of our ironic nodes are now tagged with pod-specific information, including which shared storage device is being used for that pod. And then when we create a frame, we create all of the servers at the same time. So all the server instances are then scheduled to use the same pod by taking the pod information out of the ironic node info. Okay, so just to wrap up, so we now have a new solution that uses a more component-based design. And it gives us a lot more functionality and a lot more flexibility for if we wanted to include additional open stack components in the future, it'll make it much easier for us. By basing our API on the OpenStack API, we can ensure that that is much easier to do, but it also allows for interoperability between our solution and the other cloud platforms that SAP provides to our customers. And also because we were able to use our expertise that we had already built up with an OpenStack and also our contacts within the OpenStack community, we were able to overcome a number of issues and actually provide some code upstream to improve other people's OpenStack instances. So looking a bit more into the future, we are going to be deploying this rearchitected solution into a production environment sometime for the end of the year. We're hoping that's going to go well. We are also looking into testing and integrating a number of upcoming ironic features. And finally, we're looking into leveraging Manila in order to better manage our shared storage devices. So currently we use an in-house driver for our NetApps, and we would rather be using a Manila driver for our NetApp storage. Okay, that's everything. Thank you. So a lot of this work is based on a, a lot of that work is based on a white paper that we have. So we have a couple of copies of it here if anybody wants to take one. But apart from that, if you have any other questions, feel free to ask. Thank you. Thank you. Yep. What type of door switches do you have and which particular ML2 driver from Neutron do you use? I mean that one that supports erroneous multi-tenancy feature. Yeah, so a lot of that work was done with Arista. So we work very closely with Arista to create the Nova, or the ironic Neutron integration and also on the ML2 driver for Arista. Thanks. Thank you. I have a question related to the scaling. What kind of solution do you use to kind of scale your bare metal server, server provisioning? Yeah, so we actually use our own in-house solution. So at the point of creating, we call it a frame. So we create a frame that consists of a number of nodes that are connected to a set of networks and switches. Each of those are then have some sort of isolation to ensure that customer data stays private. We can then scale up, out, up and down with our own solution. And again, we're just sort of expanding that notion of frame by adding additional nodes into it. So that's mainly, that's all handled by our own in-house solution. How do you manage upgrades, patching, et cetera? Okay, that's actually something that we're working on at the minute. Again, we have our own in-house solutions for that. So because all of our compute infrastructure racks generally use a single vendor, we just get the vendor tools and are able to automatically call into them. So the current solution we're using is Ansible for a lot of that work. And the lifecycle management. I mean, can you kind of upgrade or change the servers once they are old and replace them? Well, yeah. These works, or how do you address the lifecycle management of the compute servers? Yeah, so again, because we have these racks, we generally use those. If we were changing specific nodes, it would usually be for if there was a fault or something like that, but then we can use our own solution internally to migrate all that information across. Okay, thank you. If anybody who has any additional questions, feel free to come up afterwards. Thank you.


A useless life is as good as an early death. Every blessing from God carries with it a corresponding responsibility. Are you young? Then God holds you accountable for the way you use your strength and vitality. Are you a member of the older generation? Don't use that as an alibi. God holds you equally accountable for the years of experience you have accumulated. In the final two verses of Ecclesiastes, the teacher summarizes his thoughts. Life at any age apart from God is meaningless and futile. Regardless of how wise, wealthy, or industrious one has been, things can never fill the void that God desires to fill in your life. Therefore, fear God and keep His commandments. Analyze your life according to what you do, what you have, and what you are. Is God the focus of your activities? Is God more important than your possessions? Is God the center of your being? If not, what changes do you need to make today?


The obvious vision of the European Union is the union of member states that concentrates on the common goal. I think that what we want to see in coming years is a very strong union when it comes to foreign and security policy. It's a union of engaging in free trade with different parts of the world. And it's a union of common values. I think that we very often forget that the union is based not only on single market, not only on issues of common interests, but also on common values. Well, I think that when we speak about our priorities for the union, especially after Brexit, and as we speak we don't know what the outcome is going to be, what kind of deal we are going to reach at the end of this process. Our values, our priorities for the future of the European Union is our United Kingdom, resting more integration in the defense sector. I think that the decision of launching permanent and structured cooperation in the defense field by the European Union is the right step. Well, obviously we don't want to see any competition with NATO. We don't want to see the structured cooperation as a kind of paperwork and more bureaucracy. We want to see real capabilities for military cooperation, more cooperation in the field of industry, also tackling hybrid warfare issues that my country is particularly interested in. Secondly, I believe we have the window of opportunity to address management of Europe. Third, and definitely very important for my country, is that we continue the convergence policy within the European Union, because not all of the EU member states are enjoying the same level of living standard. And the sooner we reach that, probably the better it's going to be for those countries that are low and those countries that are still trying to reach that level of living standard and convergence. Well, obviously our closest allies are those where our common interest is. And to some extent, I could say that Brexit is bringing new alliances, new groups to tackle some of those common interests I was referring in the earlier response. First of all, of course, we have very close cooperation with the Nordic Baltic framework. Scandinavian nations, Baltic nations are very likely nations on many issues, pre-security, foreign policy, trade issues, single market. One particular issue where I believe we are very reminded and I would love to see more EU engagement in digital economy and digital single market. Second, we do have developing relations with the Netherlands countries through different, let's say, discussion orders like Nordic Baltic and the Netherlands meetings. And I'm very pleased that also after today's discussions with my colleague Irish foreign minister that we see also that we have a much closer, much more active relations with Ireland. Well, we discussed a lot about our stance on the future of Europe, on Brexit, Europe's eastern and southern neighborhoods. And I believe that to some extent, and we speak about the northern Europe, we can include Nordic Baltic, Bendix countries, Ireland. We want to see as close as possible cooperation with Germany as well. We have also very specific four months talking with Visegrad Europe countries on areas of common interest. So we try to find friends everywhere, but of course we see that union should function in 27 when it comes to big issues, but of course then discussing a lot of issues. Inevitably you get in a sectoral geographical interest that has to be taken. As I said, to some extent Brexit is probably giving new impetus to our bilateral relations. We had a very good discussion about our common interest when it comes to the outcome of the Brexit talks, be it status of nationals, be it a natural settlement, and of course we absolutely understand and respect and support the specific situation that Ireland is in. And we agree that it is in our interest to keep that unity of 27 as close, as strong as possible. Second, yes, that's the future of Europe. And I think that we are like-minded nations on many fronts, be it the development of single market, single digital market or digital economy, be it foreign and security policy, be it also issues that are related to the management of Europe. So I find from our earlier discussions and particularly the talks we had today that we are very like-minded nations on many fronts, what we want to see is how we can use those regional sectoral formats I just referred also involving more discussion with Ireland. We have already very good experience ministers of finance have met. I don't mean on bilateral but this regional formation we have also prime ministers meeting and coordinating some of those issues. So I see the future that it could be the case also before some very important policy meetings except the European level where we discuss issues, where we form a more united position between the Baltic region, Ireland and then accessing this. You have some kind of new grouping emerging here.