Right. I suppose I'll start. My name is Seamus Keen. I'm with Ericsson. I work in our cloud business unit. I'm going to take about 35, 40 minutes today just to talk to you about the economics of cloud and some of the learnings that we've had around putting NFE on top of OpenStack for operator customers. Walking around the booths for the last couple of days, I know a lot of people don't seem to know a huge amount about Ericsson. I'm assuming this audience has a reasonably good idea but I mean, Ericsson's vision or intent is that we see ourselves as being a company that can help any industry out there and individuals achieve their full potential and full capacity. And for us, cloud is a big part of that. And particularly, cloud is an enabler for companies to allow them to compete more effectively and to accelerate the speed at which they can go to market their products and disrupt and be successful in the future. And that's what a lot of our operators are trying to use cloud for as well. But of course, the theory and the practice are two different things. And the question is, how do you actually get there? When it comes to NFE, there's two types of questions that I'm sort of hearing from operators when we go out and talk to them. The first one is, how do we actually do this transformation? What's involved from a technology, from a roadmap? How do we make that journey from A to B? And secondly, more immediately, can you help us explain why we should do this and justify it? And that's not just what we hear. I mean, there's a report here from Infinetics, and 52% of carriers sort of identified cost benefits has been a particular issue when it comes to looking at adopting NFE and going down that road. So in looking to see what we can do, one of the first things you'll do is, well, OK, so people want to know what's the TCO benefits from doing this. Well, you go back and you look at, well, how has this worked out in the IT world? Cloud in the IT space been around for a long time, relatively mature, very well known. And that gives us a good start point. But the problem is, of course, that when you look at NFE and you look at telco cloud, it's very different in terms of an environment and an endpoint that you're looking to get to. And the key thing, of course, are the very different demands. The first one is, if you look at it as from an application point of view, I mean, a telco network has a much smaller number of applications, but they're very tightly integrated with a much greater degree of independency than you would find in a standard IT data center. Secondly, we're fundamentally talking about moving a network into the cloud. And that network has a shape and has very complex service chains and requirements, which also must be managed and carefully transitioned over. Carrier-Gate performance, it's a term which means different things to different people, but it has requirements in terms of latency, predictability, reliability, that also have to be met. And then, of course, the other thing is from a technology standpoint, I mean, we've come to the understanding that it's not possible to virtualize everything today. When you look at a telco network, OSS, BSS, elements around the control planes, that can be done today. But if you move right out to the edge of the network, you'll see that it's not possible to use access. It's very specialized, very high performance requirements, and we're not really ready to do that just now. And that's probably going to be the last thing on the journey to NFV that has to be done. So looking at all of that, I mean, while the IT experience and the IT learnings gave us a start point, we sort of came to the recognition that we had to build a model that looks at this early from a telco point of view. So we've been building a model that looks at NFV, Eric's, and is building our NFV architecture primarily on OpenStack. We've built a model that looks at, then so what are the TCO implications for an operator coming purely at an NFV point of view and not just as IT? So the model we look at, and the numbers and what I'm going to talk about today is sort of based around this sort of starting point. We look at OSS, BSS, the OpenStack, the NFV functionality itself, and then of course a range of the core network functions that are within that that would be virtualized over time. Okay, and each of those then we pull out CAPEX, we pull out OPEX, and we broke those down into different layers. So within the CAPEX hardware, software, and SI, we reckon we're probably the most important components to look at, and from an OPEX point of view, again the hardware, software, facilities, which is more around data center, heat, light, power, and then operations and support costs as well, okay. From an actual cost numbers perspective, we took a top-down approach to looking at these because it's probably the fastest way to do this, and we start looking at the overall cost structure for the whole operator. So just to give an example on CAPEX, and I won't drill into the numbers or anything, we start with a typical operator, you got about 10 to 15% CAPEX to sales, about 75% of that is your access in your backhaul, so the towers, the radio units, but about 25% of that then is the core and the management, the OSS, BSS, and we start from that 25% and then break that down into the major elements, OSS, BSS, EPC, communication services, IMS, and so on, and break those into, as I said again, hardware, software, and SI, and we've done something similar around the OPEX. So important to note then, so when you see the numbers here, what I'm talking about is not cost on a particular function, we're looking at the full cost for an operator to actually run and manage this on an annual basis. Okay? And then in the modeling, the key inputs that we put in, current CAPEX, current OPEX, and the two big drivers on that, of course then is a lot of growth estimates. Most of our operators are seeing very large growth in very dynamic markets, so that has to be factored in, and then we take of course the plans for virtualization, what should be done fast and at what rate. And of course the most important thing then is what are the actual impacts of virtualization. And I'll spend a bit of time talking about that, and then we run that through the modeling and get a set of output TCO and NFE type numbers. Okay? So on the virtualization impacts, I mean these are the big variables that drive the case for any particular operator. And some of the key ones that we've identified are here, I mean probably the primary one that most people start thinking about is on the hardware side, to what degree are the servers, the number of servers that we have out there are going to consolidate. We have 100 today, how many we're gonna have tomorrow. Automation and the degree of SI that's associated with that is another huge variable. And this we've found as well, it's a great degree of variability between operator and between the plans that they have. If you're willing to accept a large amount of SI and not willing to do a significant amount of automation, then that's gonna change the CAPEX to OPEX mix. Transformation and migration options also tied to that, how fast you want to move, what do you want to do first? Are you gonna, is IMS the most important thing to you? You wanna do EPC. Distributed versus centralized, when you move to an NFE type architecture, you don't necessarily assume that everything is gonna be run out of centralized data center. And one of the capabilities that NFE donors unlock is the ability to push an awful lot of processing out to the edge of the network that makes most sense to do. So again, what is the best way to do that? And that does have cost implications. And then there's a few other scaling, disaster recovery, continuity, and so on. A point I did make is that we have found that this is very sensitive to the particular operator's starting point. We've got operators out there who've never installed IMS. We've operators who have it and aren't quite happy with it, but there's a big SI overhead on that. So as I show you some numbers here, this is sort of for a typical case for an operator we looked at already, but different operators will have different sets of numbers that come out of this. So we look at a real world scenario, and this is a case we modeled recently. It's an operator we're running with over about 50 million subscribers. They've got two, three, and four G services. Big focus on mobile data and growing quite aggressively. About 10 to 15% capacity growth needed in any given year. And we modeled out about five years. I'm looking at this operator from discussions we had with them, their ambition would be to virtualize everything by about 2020. So they've got a three to four year timeline to complete their move to NFE. And we model a couple of different scenarios, and the scenario that I'm gonna talk through today just sort of assumes you start with EPC, and in your first year you would virtualize about 20% of that. So you'd have both legacy and NFE architecture operating alongside each other. And then you'd bring additional applications onto the platform, IMS, OSS, BSS, and then the rest of the core functionality taking about another three years or so to virtualize that. So that by the end of about four years you'd have virtualized the full network. And then the last set of numbers that you'd see here then are the fully virtualized environment. So you get some ideas for overall cost impacts when the transition is complete. Okay. So this is the first graph I'll show on numbers. So green is non-virtualized. This is your do nothing. And orange would be the virtualize. And looking at CAPEX from a CAPEX point of view, I mean, what you can see is through the time period from about 2015 to 2018 when the network would be virtualized, we're seeing not significant amounts of difference in terms of cost. The reason for that is the first initial applications you're just doing EPC and you're only doing a small part of it. So there's not a massive overhead in cost. There's some savings. But one of the things we've learned and we've noticed is that as you, once you build your platform and there's a cost to establish it, there are benefits that are unlocked. And I'll talk a bit more about those as we go on. But as those benefits start to come more and more downstream, there's synergies as you bring more and more applications onto the platform. So while in some ways you're increasing your investment as you virtualize more and more of those applications, you're also seeing more and more benefits. And the two things seem to be broadly canceling out until the point where your network is fully virtualized and you're no longer having to put that investment in to build a platform. And then you start to see the overall gains. So when we ran the model in this case, you've got over the full five years, the total gains in terms of your spend difference would be about only one or 2%. But by the time the network is fully virtualized, your annual cap X is down about 8% or 9% on where it would have been as a start point. So some gains there. The bigger difference though is on the OPEX side. And here, again on the first year or two, because you're only doing a limited number of applications, there aren't huge benefits. But then as you go on further, more and more of the operational gains start to come. And you begin to see a very rapid divergence then as you bring more apps onto the platform and you move to a fully virtualized telco cloud. And I'll talk a little bit more about that. But again, by the time the full network is complete in 2019, we were seeing about 25% reduction in the OPEX for the core, the OSS and the BSS components. All right? So just looking at where the benefit's coming from. If you take the cap X side, so the access is non-zero because it's a rather large pool of spend, so I just sort of compressed it. So this is what you're doing non-virtualized by 2019. So when you were fully completed, if you had not virtualized anything, this would be your spend. And this is where you end up once you have moved everything over to an NFE implementation on OpenStack. So the biggest reduction in terms of an individual component is the hardware. That would come down by about 80% overall. And that's based on what we've seen in terms of industry expectations and analysts and also what we've done in terms of our own internal modeling. And that gives you your biggest chunk of the reduction. But at the same time, there is an offset in terms of the SI to manage the more complex environment that you've now built. And you claw back about half the gains. So some savings, but not massive. And then down here we have the additional software costs primarily for implementing your cloud platform. And then over here we've got the operational side. So again, non-virtualized, where would you be if you have to add your 15% capacity for five years versus this is where you come out on the fully virtualized. And again, it's a non-zero access. So some savings in terms of the hardware, about half what you would have in terms of the capex because while you can save from moving from nebs to cots, you still do have to maintain a similar number of servers or a smaller number of servers. Some increase around software, some reduction on facilities, but very big savings around operations, about 25% to 30% there. So that's where the key gains are coming. And that's in terms of the support, the management costs and the cost to launch and manage new services on the cloud platform that you have built. Okay. So we looked just taking a minute or two around the capex. As I said, this is two sets of numbers now. So this is your start point today, non-virtualized network and then five years later everything's fully virtualized. And you can see overall capex has gone up, but there's two factors that are happening here at the same time. First of all, you're having to continue to increase capacity. As I said, we're assuming about 10 to 15% capacity growth in the network. As you go on year by year. So you have to account for that. But at the same time then you're virtualizing and you're moving into a cloud NFE architecture. So on the one hand you're actually capacity, but on the other hand then you're making savings through the virtualization. And if you balance those two out, I mean the main thing you can see is that overall the hardware component as a percentage of your total spend drops from about a fifth down to about 5%. So there's a big saving there, but then as I said you are continuing to spend on SI and on software as you go along. So while there are savings net, you are there are being offset by continued having to spend. But so that's primarily because you are building capacity on the network. This is not a static picture with comparing to like starting endpoint. The other thing then is because of the mix of the software and the SI that's in there, that's very dependent on the types of applications that you're looking at. If you take something like OSS and BSS, there's a very high SI component on them today even in a non-cloud environment. But when you virtualize that, that's not gonna change significantly. You will still have to do a large amount of SI even on cloud versions of those. Whereas other applications you will be able to automate and you'll be able to instantiate these in a much faster, simpler and cheaper way. Okay. So then if we look at the OPEC side and here, I mean the biggest reductions again are on the operation side. But that's also partially because of course about 70% of your cost is actually on the operations and the support. Everything, spare part management, software update patching isn't really that significant. It's the going out and the managing the applications and the services is where the primary cost is today. And that is what we've seen from the numbers. And again, this depends a little bit on the customer and their situation and to what degree they can automate the services and the applications. We worked through a number of different scenarios with the case we were looking at here. But in terms of ongoing SI, vendor support, network dev ops, there's big opportunities there to reduce the cost.  And there's some increase around the software and so on and for the virtualization, but it's not significant. And then the most important point is, I mean, I didn't put these two graphs on the same slide, but I mean, typical OPECs to sales ratio for an operator is about 60, 65%. So if we're talking about small reductions here versus the potential CAPEX gains, you're actually talking in terms of annual numbers, what you're gonna save on OPECs is about 10 to 15 times what you would save on CAPEX per year. So what it means is that even in the case that you were able to make very large savings on the CAPEX, they're far outweighed by the cash potential that you can free up on the OPEX site instead. Okay. So just to quickly summarize some of the key things on that, I mean, the first one is that there are CAPEX gains there. As I said, about 10% on an annual basis, but they're not massive. And I know certainly when NFE sort of appeared on the radar two, three years ago, there was a feeling that this was an area you could generate an awful lot of savings that can be achieved, but at the same time that the main benefits are coming around the OPEC site. It is operational benefits that are gonna generate the greatest opportunity and potential within the business for freeing up cash. The other thing we found is the synergies are very important. The first couple of applications, you set up your cloud platform, you bring on an EPC or an IMS or something like that. You won't really see significant gains and you probably will cost yourself money. But as you bring on more and more applications onto the platform, you build up momentum and you start to really, to build up speed in terms of the benefits and achieving the potential that you want there. Also, the numbers I put up here, they're very dependent on the particular situation. We had an operator here who was quite advanced, a lot of work on into building and operating a relatively mature network. Different operators will have different configurations that'll be different plans. So how exactly it works will depend on the customer. So, I mean, if I take all of that, I mean, a key takeaway then really is that getting the TCO gains isn't really a technology problem. And that's what we've learned from just looking at these numbers. You can take your legacy architecture, you can move to a fully virtualized one. As I said, we're looking at moving all our applications onto OpenStack and you can put that in and you can swap legacy with virtualized. But if that's all you do, you won't really see significant cost benefits. There's a lot more required. Putting in OpenStack gives you a platform which is still deemed to do a lot more to unlock potential, or to unlock the potential that's in there. I mean, and that is primarily around the operational side. Automation of processes, services, new service creation, looking at how you run and manage your network. Those are the things that will generate the big savings and really give you the benefits that the platform provides. So coming from that point, I mean, we've been looking at this for a while. I mean, this is sort of driving some of the areas that Ericsson then has been looking at. And the first is around orchestration. I mean, we've decided that total orchestration is key here. So in terms of cloud automation, governance, provisioning, security and management, these things are all important because they do aid the operational benefits and generating the load-on-line savings that we're looking for here. The second thing, of course, then is around the revenues. And I haven't really touched on this today because I was primarily just talking about the costs. Putting in cloud as a platform, I mean, in some ways, yeah, you can save some on the hardware side, you will save on some operational costs. But I mean, one of the biggest reasons to do this is to accelerate your ability to roll out services. Both in the near term for an operator, they're going to have to do this in order to be able to compete more effectively with their own customers. But also if you look wider at the OTT and the IT players who are coming in on their area more and more so, we need to be able to launch and iterate services in days and weeks rather than months and years the way it has traditionally been. And that's one of the key drivers here. So it's what can the platform do in terms of allowing you to generate new revenues? And also then there's other benefits in terms of greater reliability and greater service resilience because that drives customer retention, which also is one of the big cost drivers in an OPEX area that wasn't directly covered on the model. And then the final thing is around implementation is another key one. So in terms of doing the migration, that has to be managed properly as well. And this is one of the technology areas. So there's a large number of risks associated with implementing a large technology stack like this. We're talking about multi-vendor integration, new application, new technology, implementation as well, and ensuring the full stack interoperability is key there. And we've been able to do a number of things on this in the past and we've also announced the OP NFV certification initiative this week. So I'm just going to hand over to Shanganyu and she'll talk to you very quickly just a little bit about that and how that also benefits on this too. Yeah, great, thanks. Okay, hi everyone. My name is Shanganyu. I'm working for Erison at Group Function Technology on Cloud. And I've been working with basic mobile network planning, implementation and optimization for the past 20 years. Like just now was mentioned, like we truly, you know, what we see the challenge for operators today to go ahead with, you know, virtualization and cloudification is truly the concern about interoperability and the multi-vendor compliance. And again, performance guarantee. I guess you all recall that in the, you know, main whole session, like was a question to basic the telecom representative saying, you know, what are the things, the open start community supposed to focus on to help the tackle, you know, operators to be confident that they can speed up the virtualization and the cloudification activities. So as mentioned that since last Thursday, Erison made an announcement, a press release that we actually would like to launch something called open NFE certification program with the focus on saying that we want to lead the community saying we need to have a joint effort to address this interoperability and the multi-vendor challenge. So we want to highlight, this is not Erison certification, it's not a vendor specific certification. We want to drive this together with the community as an industry certification. So the ambition is here very much is saying we want to have a creative environment so we can jointly certify all the vendors for the so-called compliance to standards and compliance to the reference platform. So that's the thinking that we have that in term of multi-vendor compliance and also this like was mentioned, the full stack interoperability so end to end performance should be the focus. So from the we NF, you know, like in general, like we should be able to identify what are the NF workload we would like to work on so that as an ambition that we set the performance requirement clearly from the start and then jointly that with all the vendors we can actually address the challenges and make sure that truly we have a working, basically a production compliant solution jointly. So in term of performance, as I said, this is where much the challenge operators are facing today. It's not only about the end user requirement, it's very much about compliance to the regulatory requirements, as we all understand because like five nine or six nine requirements are very much the most challenging task, I would say the telecom operators are facing today. And a minute of downtime actually not only cause, I would say, you know, loss of revenue also is also causing that, you know, they're basically compliance to the regulatory requirement. Then in the end, I think our focus, as I mentioned, that very much will be the WinF portability and the NFVI compliance. So that in term of the, you know, how we're going to set up the testing environment and how we're going to jointly work with all the partners here in the community, this is very much, I would say, the focus for us in the coming months. Then people are actually asking how, why do we call it OpenNIV certification program? The thinking is very much to, you know, as was mentioned that the Linus Foundation announced the OpenNIV initiative about months ago. And our ambition is to truly, we're much aligned with this initiative to see this as the standard reference platform for us to work jointly. And then of course in term of other for us, we do know that there are other, you know, basically industry for us are also driving interface and functionality alignment, et cetera. So that's where much also all focus are saying that we need to work across the industry with, you know, basically the ambition so that we can jointly align on the focus. For example, phase one of OpenNIV will be very much to create a reference platform for you truly can start working, have a production solution. Then the second phase will be very much focus on the model part, which has been very much request by the operators today. So in general, I think as a summary, our ambition is to saying that as I mentioned, we want to work together with you, all of you here in the community, so that we truly provide not only the open source, you know, based the solution, but truly working solution to our telecom customers. And today, as I mentioned that no single vendor can guarantee performance. And that's the challenge for the community and jointly. So we need to work together on this. And then in the end, as mentioned just now, that in term of the process message tools, we need to also rethink and there will be re-engineering. There will be a lot of things we need to work together. In particular, I would say related to onboarding tools, related to automation, and again, going back to planning, implementation and optimization of the network. This is the biggest challenge, I would say, for the community to move forward. So I would say, finally, we would like to highlight, Arizona again, as the leading telecom vendor, we definitely believe that this is our responsibility. We would like to take the lead, to drive the community forward, saying this is a joint effort, that we are investing in our existing mobile vendor, multi-vendor verification capability and IoT facilities we have today worldwide. We have many labs around, but we would like to start with focusing and saying, we provide this environment in the distributed cloud fashion, so that all the customers worldwide would have access to this environment. But we will initially start with having the equipment in two locations, one in Europe and one in US. So this is where much, again, effort we would like to see, that like, I would say, a community effort, and that will welcome all our customers and the partners to come to us, so we can jointly start this activity then. Yeah, okay, thank you. Okay, so we have a few minutes, if there's questions. One question comes out to, sorry, one question comes out to, on your TCO study, did you use software as freeware, or did you use a service around that's, from like Red Hat or Ubuntu? This would have assumed the Aerson implementation, so we would run OpenStack for the virtualization platform, and we do have some of our own software around the cloud system to manage the network applications that are running then, once we set it up. So there'd be a license fee around that? Yeah, there would be, and that was, on the grass, there was a small increase on software costs, and that was primarily to cover that. Great, and then another question in terms of certification, who would be the holder of that certification? Would Ericsson grant that certification, or would it be a test that everybody agreed to and would be available? Yeah, this is definitely would be a community work, like you said, but Ericsson would like to take the lead, to initiate it, so currently we're working closely with OpenFE, test and performance community. Would other test locations be available? Say in Asia as well, or? For sure, for sure. As I said, we have globally, like labs around the globe, and the ambition is saying we want to start with a few locations, and it truly depends on the requirements from the customers. As I said, like any operators, like operators in Asia, will benefit from this already from day one. So even the equipment actually is in U.S., or in Europe, it doesn't really matter, because that's the distributed cloud thinking, yeah. So any company could do the test and just say, okay, we're compliant with this, and you could do it at Ericsson's place, or some other place as well.  You know, we believe that today, for example, like in the Ericsson booth demo, we actually have equipment in Montreal, but we're actually showing here in Paris. It works perfectly fine. Great. Yeah. Thanks. Okay. Okay. Thanks regarding your TCO calculation. Maybe I'm missing the first part, where is your fundamental of this? Is it a real customer, is it an operator case, or is it in your lab condition? This was a real operator case. So we took live cost base from an existing operator, looked at their existing network, and then had worked through a number of different scenarios for how we would recommend they virtualize, and then we did that analysis with them. We've done with a couple of other customers, but I just selected that one as a sort of a typical case for today. And the operator, what you work with then, is agrees this calculation? They were, their view was that the numbers were pretty much in line with what they had expected themselves, yeah, and what they had calculated internally. We took a slightly bigger picture. They were looking sort of on an application by application level. We looked across the full network and their total cost base, but they were pretty much happy that there was nothing radically different to what they had already calculated internally. This means if I understood correctly, it's not one operator, it's several operators. This was one operator, although we have done a similar modeling exercise with a couple of other operators as well. Thank you very much. Hi, I'm Mari Polodini from HP. I'm on the HCNAV and so on, and also OPNV.  There is a team defining the test and so on, so all of that is very much in line with the objective of the industry.  So I guess, you know, I mean, many vendors will be doing testing and certification according to the specifications. The requirement for the Telco is really to deploy, you know, telecom solutions and telecom functions and so on. So do you intend to have live network as a test bed, like a live mobile network as a test bed or things like that? That's exactly the point. I think I probably was not clear in the last slides.  So we've been doing very much in a live environment. We have extensive facilities worldwide and that's exactly the ambition we believe that we need to have a live network environment in order to do the proper testing. This is not a simple demo like simulation. We want to do, again, a live network testing. So truly make sure that once you certify in this environment, you actually are ready for production. So that's very much the thinking. Yeah, but I think that's a very interesting thing, you know, to, I mean, to communicate into documents, you know, what is the type of live network that you put in place. Whether it's 3G, LTE, Broadband. We have everything today. Yes, we have everything today. And that's exactly the belief we have that instead of creating something new from scratch, and you're definitely right. There are many vendors today who have their own certification. We're not saying we're going to replace all the existing ones, but we want to... It's very complementary, probably. Exactly. We want to take, like you're saying, a complementary approach, but with the focus on live network traffic, you know, again, all the IO type of scenarios we need to consider. Because there have been many thousand test cases that have been run with all different labs, but now we need to hold the whole effort together. That's the thinking, yeah. Thank you. As you are leading this certification program, I wonder how you want to drive this multi-vendor verification when there is no standard party dealing with actual orchestration and managing of the VNF function. So how do you want to convince the telcos which are seeking for an actual open source implementation doing the VNF orchestration since the open NFV excluded the VNF orchestration and managing? So are you proposing that you're providing a product which will be open for multi-vendor VNFs and you're placing our product on the market doing all the orchestration? Or are you looking for some open source implementation to make this part of open stack? Or do you try to go with heat or Toscar and things like that? So what's the idea here to make this interoperability with multi-vendors? Right. There's a very good question. And I'm trying to catch up. In term of the thinking, it's definitely your right. And the challenge as we also realized from Ericsson's perspective is truly the multi-vendor challenge. Like the open source, it's very much encouraging like all the vendors to contribute with the code with ideas about functionalities interface, et cetera. And so therefore we want to call this, again, why we call the certification as OP NFV certification. The thinking is very much we need to have a certain standard behind. That's very much aligned because OP NFV is very much aligned with et C NFV initiative. So the thinking is very much like saying there are many for us today ongoing like in terms of how we're going to align each other's functionality and each other's again like solutions. So to believe like what you're saying orchestration is very much the currently again the phase one of OP NFV is very much to speed up you know the ongoing activity so we actually have a baseline so that can work you know figure out how we can have a working environment so that again not only open stock I would say all the other community would like to have a solution we felt like the operator can start working on. And then the phase two is very much to focus on orchestration and this bundle focus yeah. And that's where much the focus I would say the OP NFV community also today are working on even though that we need to also realize for many operators is where much the migration thinking like from legacy environment to virtualized environment is a big step for them. And so therefore we need to be very careful in choosing like you're saying which way in life should we focus on. Like different workload we have again like if you say watch your EBC compare watch your IMS they have different you know requirements in terms of the the underlayer you know solutions. So that's the portion we're actually working together with the community. We do not believe that any one vendor can actually drive this neither Erison or Huawei or you know Cisco or like HP can drive this along. We need to work together. So yeah. So you're basically saying that in phase two open NFV is also picking up on the orchestration. Yes yes that's exactly the focus if you look at at the NFV is phase two that's exactly the focus. Open NFV slides. Yes the previous one. Yeah yes yes yes the one here. So yeah so that's a phase two so phase one focus yeah. Yeah okay so in phase two it will shift. Yes yes exactly exactly.  Like we're going to pick out the WNF you know WNF portability is very much the focus for us. And as the initial activity yeah because we believe like you said this is a crucial part. Okay yeah okay yeah. Thank you. Okay great. Any other questions? Okay thank you very much since we're coming today and myself and Shanang will be here if you have anything else you want to ask. Thanks.


This is not to say, this is not to devalue our medical rituals. And I would like to elaborate on that to say that it's not just medical rituals, but the entire corpus of technology can also be seen as an incredibly complicated elaborate system of ritual that is based as ritual is, it's based on a religion. We call the religion science. And it can be used to mold reality. Now, we think though that well okay in the past they weren't actually very successful at molding reality. That's because they were mired in superstition and projection and wishful thinking and you know, confirmation bias that made it look like they understood to themselves but really they were pretty much helpless before the forces of nature and you really couldn't accomplish the kind of things that we can accomplish. Now I'm not saying that they could accomplish everything that we can accomplish. I'm not saying that at all. Our particular system of ritual that I call technology can achieve miracles, can achieve wonders. It is, it is what I'm saying is that our gift as human beings, our creative power as human beings is in fact to apply the technology, the deep technology of ritual. So it requires as I was saying a an underlying mythology and underlying religion and ours we call science. Now, again, you might protest well science isn't a religion because it's verifiable it doesn't require faith it doesn't require metaphysical unverifiable unprovable principles, but we perform experiments and we see whether or not what our we see whether or not our propositions are in fact true. In fact, science does have metaphysical principles that we do take on faith. For example, the, the idea that variables can in principle be isolated that you can remove, for example, the influence of the experiment or from the experiment that the mental emotional spiritual condition of the experimenter doesn't affect or the beliefs of the experimenter don't affect the experiment that observer and observed can be separated that things happen if and only if they are caused to happen that we can understand the world by reducing it to the operation of its parts. Like these are all elements of a scientific mythology that we like like the repeatability of experiments like this. This is a metaphysical principle that may not be true. But we assume that it is true, and we enter into that reality, and we can gain the powers of that reality.


Hey, this is Brett and this 2018 Ram 2500 Mega Cab Short Box Laramie is stock number 13857Z. I am here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck and RAM headquarters. This 2018 Ram 2500 has the 6.7-liter Cummins diesel engine. It's paired up with the 6-speed 68 RFE automatic transmission. This truck can tow 16,835 pounds and has a max payload of 1,774 pounds. I found those on Ram's tow guide website. I'll link it in the description below. This truck has been fully safety and inspected by our service shop per the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and tapped off and this truck is 100% ready to go. Super clean all the way around inside and out and that's exactly what I'm going to do in this video.  Max Steel is a color. I shoot all my videos in 4K. If you like the video, you can subscribe to my YouTube channel, which is youtube.com slash Summit Auto. Click the bell notifications to get updates on the videos I do each and every day as well as having access to one of the largest catalogs of truck and vehicle walk-arounds. On YouTube, 8,000 videos and counting comes with a 20-inch painted alloy wheels with the chrome inserts. This is Michelin Defender LTX tires, these are LT28560R20s. I would say they have probably about 60-70% of the tread left on them. Framon Underbody is exceptionally nice and clean. For being a 2018, this is a one owner clean title history, clean car facts out of Illinois. Comes with the projector lamp headlamps, LED running lights, and factory fog lights. Front bumper is in fantastic condition, you get the front bumper parking sensors, as well as the chrome-trimmed grille part of that Laramie package. The hood is in great shape, I didn't see any dents or dings on there. Really nice condition, passenger side front fender is in really nice shape and the passenger side front wheel, no major scuffs or scrapes on there. Max Steel, one of my favorite colors on the Rams, it's got a lot of blues, greens, and of course silvers in there. Really a cool color, especially when you get really up close to it. Really any color during the day, it looks blue, in the afternoon it looks gray, and at night it looks black. As you go down this side of this 2018 Ram 2500, take note of how clean that body is, how reflective and mirror-like that paint is. I take these HD videos, so if you are far away or even if you're close by and you just cannot make the trip down, but you're still interested in purchasing the vehicle, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from wherever you're at. If this video helps you make that buying decision later, salesmen know that you saw the video that it was helpful and that Brett sent you. Back wheel is in excellent shape and the back tires have just as much tread. As the front tires, you'll notice that there was some stuff in the back of the bed. That's the compressor for these rear airbags that it has. Frame and underbody is in nice shape, has all the remaining factory exhaust. That's in pretty nice condition for a 2018. Little rockers, cab corners, didn't see any corrosion on them. Has the factory chrome step bars. This passenger side box is in fantastic condition. Didn't see any dents or dings on there. Coming around to the back, we get the rear bumper parking sensors. The rear bumper itself is in fantastic shape, has the full towing package, which includes a receiver hitch, four pin and seven pin wiring. And the tailgate is in really nice condition as well. Note that you get the chrome Ram 4x4 and Laramie logo. It is also a locking tailgate. You get your backup camera there. Comes with the fifth wheel and goose neck prep package. Bed's got a little bit of light duty wear. Comes with the LED bed lights with the button back here. See, those are all working nicely. And it also comes with seven pin wiring. Tailgate shuts nice and solidly.  No major dents or dings on there. And for full disclosure, this back wheel is just as nice as the rest. Cabin doors all look really good. Didn't see any dents or dings. Has the heated fold-up tow mirrors. They have built-in directional signals. They fold up like so. They also fold in like that.  No rips or tears on the seats. Smells very clean inside this truck. You get the Laramie and Boston to the backrest. No major rips, tears, or wear. Memory driver's seat, heated and cooled seats, factory floor mats, auto headlamps, power windows, locks, and mirrors. These mirrors do power fold in. I always like showing both sides so that you know that both sides are working properly. We'll take a quick look at the back seats. Show you how those seats go down. Back seats are in nice shape as well. No rips or tears back here. It does have the latch-child safety system for any child car seats you may have. Power sliding rear window with the built-in rear defrost. So these seats go down two different ways. You get the factory floor mat back here. And the outboard seats are heated on the outboard side. Or the back seats are heated on the outboard side, I should say. So the first way, these seats go down all the way like so. And you get a nice, flat area back here. So if you put both sides down, you got a really nice, big, flat area. So if you've got pets or anything, they can lay back here. Or if you wanted to take a nap, need to take a nap, there's enough space that you could lay out comfortably back here. And then the second way is if just this backrest goes down. You get a higher load floor. You also still have all your floor area. And you get a confined storage area back here. There's also a container underneath there. And so that's how those work. Really a ton of room in these mega cabs. It's kind of weird to sit in the back of them because you just have so much room. There's your child safety locks inside and bottoms of the doors are in really nice shape as well. But if you've got big people, put them back there. They'll fit. Here's your VIN sticker. No Canadian trucks here. Has the tire and loading information sticker. We'll hop inside, check out the miles, the radio, and everything that this truck has to offer on the interior. You get the Laramie animation at the beginning there, seven inch LCD display. This one comes with a digital spinometer, temperature display arranged to empty. You can change all those corners to read whatever you'd like. The instrument cluster is very nice and clean. Comes with the heated leather wrapped steering wheel. Bluetooth and information center controls on the left, cruise controls on the right, and audio controls on the back of the steering wheel. There's your six speed shifter with the automatic, or 68 RFE automatic shifter with the optional tap shift. Comes with the 8.4 4C radio. You get AM, FM, and Sirius XM radio capabilities. You also have your heated seats and cooled seat buttons. You can check out your backup camera here. You can also check out your cargo cam and you can see both those are working nicely. And then you get all your different apps right here, including projection manager. You can project your cell phone to the screen via Android Auto or Apple CarPlay. So while this one doesn't have the factory navigation system, you can project your cell phone to the screen. And if you've got Waze or Google Maps on your phone, project it right up there. And it's like you have a nav on the screen. We actually did a demo on an 8.4. If you wanna check that video out, that's in the upper right hand part of the screen. Turned out four wheel drive. More tactile volume tune in climate controls, factory brake controller. There you're heated and cooled seat buttons. Stability control tow-haul, factory exhaust brake, and your front and rear parking sensors. You can turn those off and on as you please. You also have your keyless entry with a remote start. 115 volt, 150 watt plug-in, passenger side format and seat are in excellent condition as well. No rips or tears on that passenger seat. And the headliner is in really nice shape. Does have the speakers in the ceiling, part of that Alpine premium sound system. Map lights, power sign, rear window button and your home light buttons for your garage door security systems and lagging systems. The system SOS buttons in the mirror. We'll start it up, take a look under the hood, check out all the lights, and we'll be all good to go. Starts right up. No check engine lights or anything like that. I would personally like to thank you for checking out the video today. And hopefully from this HD video, you've been able to verify the quality condition options and of course, cleanliness of this truck all the way around inside and out. All those lights are very bright and working nicely. And under the hood, we have the 6.7 liter Cummins diesel engine. Engine bay is very clean, runs very smooth. Once again, this truck has been fully safety then inspected by our service shop as they crash, oil and filter change all the fluids have been checked and topped off and it is 100% ready to go. There's the emissions sticker. And I would highly recommend this truck from a quality and condition standpoint. And to see more pictures of this truck on one of our other 550 new and used cars, trucks, SUVs, minivans, wranglers, halftones, three quarter tons, one tons. You made it, we got it, go to that website right there summitauto.com. Full pictures and descriptions of every single vehicle all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash summitauto. Click the bell notifications to get updates on the videos I do each and every day as well as access to one of the largest catalogs of vehicle and truck walk-arounds on YouTube. In fact, on the second you see a link to subscribe to my YouTube channel on the upper left and a link to more Ram 2500 truck videos I've done in the upper right and to his vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right, click there to check us out. We're super excited to help you with this ultra clean. 2018 Ram 2500 mega cab short box, Laramie and Maximum Steel Metallic. Thanks again for checking out the video. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it and really a super nice truck. I hope whoever gets it's gonna love it because it's in really nice shape. Thanks again.


NiF2 is a transcription factor that plays a key role in protecting cells from oxidative stress. It has been shown to activate the expression of genes involved in detoxification and antioxidant defense mechanisms. Recent studies have also revealed that NiF2 can affect cellular energy metabolism. This study demonstrates that NiF2 deficiency causes mitochondrial dysfunction, leading to decreased ATP production and impaired respiration. The authors found that NiF2 deficient cells rely on glycolysis to produce ATP, which is then used to maintain the mitochondrial membrane potential. They also showed that NiF2 deficient cells have reduced activity of the respiratory chain complexes, suggesting that NiF2 plays a critical role in maintaining proper mitochondrial function. This article was authored by Kira M. Holmstrom, Liam Baird, Ying Zhong, and others. We are article.tv, links in the description below.


Hello everyone. So just before we start, I'd like to thank the Euro Python organizers for this awesome event It's been like five years that we're sponsoring it and it's always a great pleasure. I Also want to thank Eric Smith the author of this pep for all his work on Python and Also for his unexpected answers to my emails. So thank you Eric So my name is Guillaume Gelin If you want to find me on the internet, I'm called Ramnes So if you want to add me on LinkedIn Facebook and if anything Ramnes that you use the place I'm working as a lead software engineer at Numboli. Numboli is a data marketing company We have a booth at the minister floor. So feel free to to come and see us As a lot of company around we are recruiting. So if you're searching for a job You're welcome Just a quick word before we really go into it. I started playing with data classes not so long ago So please don't take my word for everything I say I met as much as much research as I could to give you the best talk possible And the more research the more research I did on the subject and the more I wanted to add on this talk So it's a bit long. I'm not sure we'll have time for questions But if you have some feel free to come at the booth and to tweet me up All right, so it's going to be pretty fast. Are you ready? Yeah Okay, let's go So let's go back one week Before I was in vacations in the south of France Near the sea and that was great I'm I'm kind of like an unperturbed an entrepreneurial guy. So I was thinking what startup could I launch today? So the first thing you you look at when you're Searching for us to build a startup is a domain name, right? So I found this domain name, which is amazing.com. I Thought it's it's a good domain name. I bought it and And I thought I could make money out of it, right? so I want to my idea is to make a marketplace of of seller and buyers and To have that marketplace I need an inventory of all the times I have right So I have a friend who told me well Python tree is not great It's slower than Python 2 you should you should use Python 2 So it's been a long time that I didn't use Python and but I remember like this name-to-pole thing, right? So the first thing I did was to create some Items in my inventory with that name-to-pole And it was great. It did the job But as my cut base went larger and larger I ended up doing like not really DRI things Repeating a lot of stuff and and one thing really I know me is that I couldn't define defaults So I took a look at Python 3 and So yeah missing properties defaults I took a look at Python 3 and I discovered that new version of name-to-pole which you don't apart from Collections, but from typing and which has uppercase letters So it arrived in Python 3.5 And the annotation support that you can see here arrived in a Python 3.6 So it's it's it's way better because rather than Calculating every time my my total cost of all the items I have in my inventory. I can define that function once And then call it whenever I need And I have some kind of default too like I have a default entity which is zero But the problem is what happens if my mutable if my default is immutable like if it's a list for example Let's say I want to for my items. I want to have all the related items to that items So I want a list of items If I define it directly in the class just like I just like I did for quantity It's not going to work very well because each time I'm going to modify The list in an instance is going to be modified in all instances. So it's not that great So I thought like maybe I could like overload the new Dunder new method so that When I get my related items, I check if it if it's there or not if it's not there. I create an empty list And that's why I do my default But suddenly that version of native tuple doesn't follow that like It's weird because Python used to be much more permacive than that, right? so We're almost there, but Not yet so What I thought I could do because I don't like when people like tell me no you can't do that Is to define a real new method? To assign it to the new method and it works Well, it's a bit creepy, right? So yeah, nothing to see here. Please move on so This is the idea behind pay 557. It's to provide Real a real data class that you could use for that kind of stuff So it arrived in Python 3.7 It's available in Python 3.6 through a backboard called data classes, which is on github And that's great because you can take a look at the source code. So very interesting It's made by Eric Smith Which is the owner of a small IT business in in New York called true blade What they do is mostly written in Python Eric is a co-developer of CPython the author of several major contribution including STF format and f-strings He started to use Python a long time ago to escape C but ended up doing a lot of C to cut Python and He's happy because that a class is actually a place where it could code in the standard library in Python And actually use f-strings that he also could add himself So that's great So what Eric wanted is something that sounds and and feels like name tuples But with real real defaults and that can be mutable because name tuples are immutable, right? So he created data class. I'm pretty sure you've seen that example already So If you if you compare it to the the example with the name tuple, it's it's really close, right? There is the only difference is that you don't have the name tuple inheritance, but in place you have the data class decorator And the reason you choose the decorator is to avoid inheritance So that you don't have diamond problems and also decorators are a great way to inject methods inside a class And maybe this is something that we'll see more and more in the standard library Also data classes are meant to be used with type annotations So it's Python 3.7 and Python 3.6. So annotation at theirs are there to be used so think of it So what data class give you the decorator it injects? init, dndr init method and dndr init representation that there init string What the init gives you is that For each field that you've defined It will Expect them to be given at the instantiation time The representation is pretty good or so it's kind of moiconic like you can evaluate it itself Also, you have an explicit hash saying that like the explicit hash is hash equal none Saying that you can't hash a data class And it's and it has a lots of metadata like dndr data class fields that contains All the field names the types the default values the field options All the data classes you have another metadata which is dndr data class param That contains all the parameters that were used to generate the class, but we'll see that after So when I speak about real defaults. Oh, yes, it's almost propel your line So here for the rotate rotate items example So I've made I've used field which is something that you import from data classes and It gives you an option which is default factory which you can give like any function Here I just want to instantiate the list each time. I instantiate an item and I it's working just as expected as we can see So that's great There is that dndr post init method which is specific to to data classes Or not, maybe I'm not sure And it's great because you can Specify things like if we don't want the total cost to be appropriate for example We can compute it on the ones here and then just use it when we want What we only have to do is to define the field directly on top on the top The unit falls is to say that don't expect that field At in station instantiation time. I have a very hard time to pronounce this Just just expect it to be created later So for example in the post init you can freeze data classes. So you can pass frozen equal true And that does what you expect it to do which means that if you try to modify a field It's real. It's will raise an error be one. So Real real Freezing in Python is really hard There is like real acts to to change this so one hack is to is to use object dot then there's it that's here and This is actually useful because if you want a field to be computed at the instance instantiation time, but you don't want it to be modifiable be After you can do it that way and it's actually the recommended way by Eric so Feel free to use it Also, like I said by default Dunder ish equal none. So by default you can't use data classes as keys for dicks for example But if you really want to you can use the option unsafe ash And you can also inside fields define which field you want to be considered in the ash or not for example here I'm saying that related items is is not to consider into the ash because I think that Related items is a multiple list and it's maybe going to change very often So I don't want my ash to be fucked up. So I'm not going to take it into account I'm just going to consider name and unit price and So if I instantiate three three items two hammers with the same price and one spammer one spanner Then if I try to make a set out of it, we see that effectively we have two Two items and not three also So for those who don't know my pie my pie is an experimental optional static type checker for Python What it does it it analyzes the code without running it and uses annotations to detect when incorrect types are used So that a class works well with my pie That being say the the version of my pie is that and those data classes is not released yet So it will be released pretty soon, but it works And if for some reason you want to to go back to that name to pull way of Doing things you can there is a make that a class function the only difference with Collections that name to pull is that you can give type hints and you can also give defaults and fields options Just just like I showed before And it's basically the same as the name to pull behavior Also one great thing is that If you want to go back from your data classes to more standard types like dicks or tuples you have helpers for this So as dict and as tuples inside data classes allows you to do that The order is defined by the field definition orders So if you define the name first in your class and then the price in second Then you'll have that order in your dicks and tuples So that's pretty great, right We have exactly what we want It's full DRI We have properties everything we want that's that's really great, but Let's go back in time a second time Maybe what I showed you remembers you something Maybe you've seen already a library called 80 tiers or I don't know how to pronounce it But 80 tier or something So it's Python 2.7 and 3.4 plus library that you can install on PIP obviously It's made by in X for schlawak. That's maybe is here. Yeah Please give him a big hand. No, he's not well is in dear Python, but not in this room but The 80 tier library is really what The the the origin idea of data classes, right? So Eric when he wants when he created the data classes PIP He wants through a lot of males issues its draft 80 tiers To understand their decision-making what choice what trade-off did they took? And as you can see, it's really really close to data classes, right? You have that 80 tier dot s which is the equivalent of data classes You have that 80 tier dot ib which is which allows you to give a default So that's really really similar But it's much more powerful it gives you much more methods as you can see there is in its rep as their egg ash But you also have n e l t l e g t e g etc It's it has validators which are not present in data classes So for example here, I have a price And I don't want an item to be over nice thousand dollars So I can just validate that with the small snippet And it's used the decorators setters for that pretty pretty smart You also has built in well built in 80 tier validators like instance of which allows you to Dynamically verify the type of your of your field and not just with my pie or some static analyzer thing you also converters converters like for example if you're working with external APIs and You you know that the types on that external API are fucked up But you want in your database to have proper types Then you can use a convert the converter option of 80 tier dot ib Which means by the way at rib like attribute. I took one word to understand that So Right now you may be wondering like why I would use data classes if 80 tier is doing basically the same thing and it's much more powerful, right? And this is answered in the pep actually so the ID is 80 tier is a sort party library that want to keep its freedom to move fast And to implement any features I want to implement also Python is really oriented towards simplicity And a lot of features that are in 80 tier are not useful like 100% of the time So I don't know you but personally I tend to value a lot simplicity So if I don't need the extra features, I'm mostly going to use data classes And also I prefer data classes syntax, which is I feel much more clear because eight as we just shown before 80 tier syntax is a bit strange But hey, I guess it's just a matter of personal preference, right? So Let's go back to my wonderful amazing.com website What if I had a no SQL database behind right something like MongoDB the data class example would in the world because In a schemed database, you don't know the field in advance or you can't know them But you want to have the freedom of letting someone modifying it then directly in the database without Without it breaking all your code base So here we can't use databases data classes, right? So for example with MongoDB If we connect to the database and get documents inside a collection, we get a dictionary The problem with dictionaries is that it misses real object-oriented programming types So for example if I have users on the side and and items on the other side If both are dicts, how do I know which which one is what like do I just check the fields? like I'd prefer to be able to do like is instance of user or is instance of item you miss properties and also the dot notation because the dict notation where you have like braces everywhere is a bit cumbersome So one smart guy could make Could inherit from dict and just make the properties that would work That's that's a bit creepy also So we're not going to stay on this And there is a thing called simple namespaces It's in a module called types. So there is collections typing and types. It's not the same thing And that simple namespace class is is really neat. You can see it like a Bear a very bear version of data classes. It just give an in its method and and a representation the method to the class that inherits from it and What's great is that doesn't ask you to define fields. So in case of the MongoDB example, it's it's nice Because you can just take your whatever is your dict and just throw it inside your class and and and you have The the hopi type you have the dot notation and you have the properties But one thing that's missing here is that we can't go back to normal types we can't we can't We can't have a dict would have Simple namespace we can't have a table so you should end up doing that kind of tough Maybe we could have something more powerful There is that library called box Which is on github that you can install on people so which is basically a wrapper around dict It works a bit like simple namespace But you can you you have a method like to underscore dict that allows you to go back to a dict I think if I'm not wrong that there is also a to topple method. I'm not so sure about it, but maybe and The great thing about box also is that if you have dicts inside dicts inside dicts it's going to To take the whole thing and to make box would have everything so you can do it and one dot Item two dot item three it's true But the problem with box is that it's super slow I'm not really much into performance usually, but here it's Really problematic So as we as you can see here like Here the it's a micro benchmark Which is mostly about measuring the time it takes to create a bunch a bunch of object like 50,000 And also with some reads inside You can see that using a dict or a or a or a simple namespace is super fast Then you have You have I can't read my slide Name to polls like collection name to pulse on the non-typed one Name to the type at one is also great And singy I will talk about it later and then eight it here and And the data classes are pretty much at the same level of performance But box is like three time like you take three three month three times more Time to create a box than a than a data class. So that's not very nice So let me introduce you to singy singy is a library we have developed at Numbly It's Python 2.7 and 3.4 plus compatible it can you can install it on the pip it's on github It looks like simple namespaces But it has that view method Which allows you to go back to a dict And There's a really nice thing about singy is that you can have different kind of views you can define new views so for example If I want to be able to have In my dict the result of the property I've defined I can I can define a view Called with total for example and include the total the total cost inside And when I when I will call item view with total I'll get a dict with the property included You can also exclude fields Select exactly which fields you want that kind of stuff So for example when you're in the context of a REST API for example Backed by something with MongoDB. It's really nice because you can't say exactly for each of you of your API What field do you want to return? And by the way, we have we have Mongo thingy, which is basically a node EM object document mapper based on singy, which is something a bit like Mongo engine But but much more simple and much more close to PyMongo query language So it's Q&A time, but I'll start with a self Q&A so The reason I made this talk in the first place is because I was developing thingy and I saw the data class thing And I saw shit. Maybe what I'm doing for a year. It's completely easier is less Maybe they just implemented something and Python that's doing exactly the same thing But as we've just seen it's I think there is place for both because data class is more on on type it stuff and and really Define field that kind of stuff a thingy is much more about Freedom and and you can put whatever you want the inside So the answer is no Does that a class deprecates name tuples? Honestly? Yes, definitely Whatever modules are from Does it deprecate SQL alchemy?  It's used by a lot of people. So I don't see it deprecated anywhere soon But I could imagine a rebase of SQL alchemy on data classes. I don't think it's going to be Soon, but it could happen Does it deprecate Marshmallow? So for those who don't know Marshmallow is a validation library where you can define class which with each field being like a rule to to That you feel must must comply too So once again, I don't think so But I think Marshmallow could rebase on data classes especially since data classes was sought with with Extendability in mind So it's it's really like you can plug so party libraries on it So maybe that's a good idea. I don't know and the last question Would be does it deprecate class? And I leave that cash that question to you. Thank you All right, so we have time for maybe one more question Okay, then I Suck at live questions, so please speak well Did you run more benchmarks and all the competitions because I can imagine that you would use data classes or address or name tuples if you have a lot of instances like database rows and then memory consumption may be Important to for example. Yeah, I didn't make more benchmarks I really did just made that benchmark because I Wanted to use in a real world example like in a real-world situation I wanted to use books and that's really what made me like retire your books So that's what I showed that benchmark, but Yeah, feel free to do more benchmarks Any other questions last one It could be fast as a result of philosophy The new thing that sometimes it's good to have a clear model because you said the Mongols pay to the scale But the moment you get too many fields so so actually No in the latest version of mongo you have you can enforce chemas directly inside the database, so It's it's but it's like the the database administrator walk. It's not your walk as a developer But yeah, yeah, definitely there are situations where you want clear schemas, right? And I'm not saying that that's not the case. I'm just saying that sometimes you don't want that Yeah, it's basically for a running and when your system becoming larger with a lot of parameters a lot of properties It's easy to make a mistake. So yeah, that's the trade-off. Thank you All right. Thank you One big round of applause


The at sea portion of Exercise Phoenix Express got underway in Tunis, Tunisia. The at sea portion of Phoenix Express is five days long and involves seven partner nation ships and aircraft. The objective is to improve cooperation and interoperability during at sea maritime interdiction operations. Phoenix Express is all about strengthening partnerships and building cooperation. One of the great strengths of the United States and our US Navy is our allies and partners. This exercise will strengthen those relationships. It's time we are together, we gain something. We are counting on our partnership and our friendship. The cooperation is no more a choice. It's a compulsory for all nation to share information, share experience and in this way we're going to provide a safe maritime domain for all mariner crossing by our waters.


Then I started to shine the flashlight on her, but she screamed, Stop before I got to her face. This time, her voice wasn't as convincing. I could tell she wasn't human. Now what you guys need to realize is that I'm not a badass and I'm not trying to sound cool or tough, but ever since something happened three years ago, the same event that caused me to move out here. I don't respond to situations the same anymore. Maybe I'm not scared of death anymore.  Maybe I'm weird. But when I established that this thing wasn't human, I started to smile. It fooled me, got me out here in the woods in its domain and was probably going to make an attempt on my life.  It actually was a girl. Sort of. She was super pale and had normally large eyes that were completely black. When the light hit her face, her head snapped forward and made eye contact with me and her jaw dropped open three times larger than any human could. And then she screamed. It was loud, like inhuman loud. It sounded like a girl's scream, but as if it were being played through massive speakers to make it ear splitting.


this video we are going to discuss about the LXI component of the LCM model. LXI meaning learner experience interactions. Now we have already gone through two learning dialogues on LXI. What we will do differently in this learning dialogue on LXI is, I am going to share my experiences as a MOOC instructor and also shared with you experiences that other faculty have shared when they have applied LCM in their MOOC courses or in their online courses like in a flipped classroom. So let's get started. Now if you are a MOOC instructor or if you are designing the online component of your flipped classrooms, you would know that there are three types of interactions through which learning happens in an online setting. So what is the first one? The first one is very obvious.  The second type of interaction is the learner-instructor interaction. So what happens in this interaction is that the learner is interacting with the instructor either in the discussion forum or through the interactive sessions like you have experienced in this course. And what is the third type of interaction through which learning can happen in a MOOC? Yes it is the learner-learner interaction or the peer interaction in a MOOC. Now if you ask any MOOC instructor, they will tell you that the learner-learner interaction is very important avenue for learning in case of a MOOC. So let's pause here and do this reflection spot activity. Pause the video and write down one reason why you think learner-learner interaction in a MOOC is important. Once you are done answering the question then only resume this learning dialogue. So welcome back from the reflection spot. I hope you have written down your reason as to why the learner-learner interaction is important in a MOOC. Let me guess some of your answers. Some of you may have said that learner-learner interaction is important because suppose you are a MOOC learner and you need feedback on the solution you have generated. If you post it in the forum then there is probability of one of your peers or a coursemate coming and giving you feedback on your solution. So this is a very important learning avenue in a MOOC where the instructor is not so readily available as in a classroom setting. And when such an interaction happens between peers, what happens is it reduces or removes the sense of isolation for a MOOC learner. Another possibility that you may have written is that a learner gets exposed to a diverse set of opinions or a diverse set of ways to solve the same problem if they are going through the discussion forum posting. That's also a very important avenue for learning in a MOOC setting. So this is the summary of the benefits of learner-learner interaction in a MOOC setting. This is a necessary condition for a learner-centric MOOC. Now so far you have heard what I have told you about my experience of why this is important. Let's see what research says about the importance of peer interaction in a MOOC. So research says that peer interaction leading to peer learning is among the top five factors that influences learner engagement with the course. And that is such an important metric as an instructor to bring in engagement of the learners with the course. But do you think having a discussion forum available in an online course is enough to bring in learners in the forum? So no, right? The forum itself is just an affordance or a feature of your system. Research says that you have to have well designed structured activities around the discussion forum to bring in the learners into the forum.


Russia plans to manufacture Kh-50 missiles to renew attacks on Ukraine. The General Staff of the Armed Forces of Ukraine has reported that Russia is planning to start manufacturing Kh-50 air-to-surface strategic cruise missiles in order to resume attacks on Ukraine in autumn. Brigadier General Alexei Haramov, deputy head of the main operational directorate of the General Staff of the Armed Forces of Ukraine, told it during a press briefing. According to the information available, the Russian Federation is planning to start manufacturing Kh-50 air-to-surface strategic cruise missiles in June of this year, which will allow the Kremlin to resume missile strikes on the territory of our country in autumn. Russia has expended at least 50% of its long-range anti-aircraft missile stockpile Since February 2022, having used at least 8,000 of these missiles, the majority of which were surface-to-surface missiles. Given the current levels of production, Russia will not be able to replenish its reserves in the medium term. This potentially undermines Moscow's ability to defend its strategic interests in the Far East and near its borders with NATO countries, he added. The Kh-50 is a subsonic, low-observable cruise missile utilizing the guidance system developed for the Kh-101. The missile has a length of 6 meters and a weight of about 1.5 tons. The missile is capable of flying at a distance of 1,500 km at a speed of up to 950 km an hour. To prevent the interception by enemy air defense systems, the rocket will fly at low altitudes.


Ever heard the old phrase strike when the iron is hot? Well it's never been hotter than now. All this month at Appalachian Wireless you can get the Samsung GS6 or the GS6 Edge for just one penny when you send them for service. The Galaxy S6, normally $49.99, now just a penny. The Galaxy S6 Edge, normally $99.99, now just a penny. Strike now while supplies last. Better service, bigger savings, serving you for the last 25 years at Appalachian Wireless. A public meeting was held here tonight in Siresville at the MacGuffin County High School, where community members were invited out to ask questions and learn about the Restaurant Roe phase of the Mountain Parkway project set to begin construction soon. Restaurant Roe from a design standpoint is somewhat of a challenge. It's very condensely packed from a business standpoint, not a lot of room to do utility relocations, right-of-way acquisition, so what we've done essentially is work with the template that we have and try to reduce those right-of-way impacts. In doing so, we've had to do some access changeovers, some new designs that are a little bit atypical of what we typically do with the KYTC project, using frontage and back of roads for access, and maintain those early lines of communication during the right-of-way acquisition process. This project is expected to be a boon for Siresville, however, that was not always the case as the original plans for the project called for it to bypass the community altogether. Well, there's over 60 percent of Siresville tax base comes off of Restaurant Roe, and like I said when I first got elected, it was almost set in stone that they was going to bypass Siresville, and me and a couple more failures, we made sure that they didn't get bypassed because we told them that would destroy Siresville. I've always stood up for what I thought was right, and especially for my people, if you take 60 percent tax base away from a struggling economy anyway, there ain't nothing left. As the Restaurant Roe phase begins, work continues on other phases of the Mountain Parkway expansion project west of Siresville. Overall, the Mountain Parkway expansion project is moving along very well. We're moving very efficiently in the other three jobs we have in road and construction right now, just to the west of Siresville. The Gifford Roe, Kentucky 30 interchange, as well as Kentucky 7 interchange. Moving forward very efficiently in those three, we're ready to move care of the same mentality here in the Restaurant Roe. The Restaurant Roe section of the project is set to be completed within three years. Reporting from Siresville, for EKB News, I'm Jackson Ladder.


Today I want to talk about how to change your mindset instantly. And I want to talk about a really quick quote that one of my very first mentors named Hal Elrod shared with me. And the quote is this, can't change it. See there's a lot of things that we wish we could control. There's a lot of things that we wish were different. But a lot of those things we can't control at all. And so the question you have to ask yourself is if I can't control it why am I letting it stress me out? Why am I letting it dictate the way that I feel today? And a perfect example of this is traffic.  I used to hate traffic even more. And when I would be in traffic and I would be thinking about how late I would be, I would squeeze my steering wheel as hard as I possibly could till I could see the white in my knuckles. And as you can see my knuckles are pretty white anyways because I'm an extremely Irish person. But I could see even more white in my knuckles. And I would get so pissed off and I would be so infuriated of why is this traffic here? I'm gonna be late in all of these things. And then I realized that I can't change the traffic. But what I can change is the ride to my destination. See I'm going to get to my destination either way. Whether I'm extremely furious the entire time that I'm driving or I have a great ride. And so the reason why this was a very life-changing topic for me was because it got me to stop trying to control things that I can't control. It got me to learn to appreciate things like being in traffic. Look I'm in traffic. I can listen to music that I love. I can look up and see the beautiful sky. If it's raining I can see the rain coming down and the sound that it makes. There's a lot of things to appreciate. The fact that I'm actually in my own car. Those are all things to appreciate. I can't change the fact that there's traffic in front of me. But what I can change is my mindset on my ride to my destination. So what I want you to take from this is this. You're going to arrive either way.  Having put your body through stress or whether you're going to arrive with a smile on your face. The decision is yours. Make sure that you make the right one.