Live from Orlando, Florida, it's theCUBE. Covering Pentaho World 2017. Brought to you by Hitachi Ventara. Welcome back to theCUBE's live coverage of Pentaho World. Brought to you, of course, by Hitachi Ventara. I am your host, Rebecca Knight, along with my co-host, Dave Vellante. We're joined by Anthony DeShazer. He is the Chief Solutions Architect and SVP of Customer Success at Pentaho. Thanks so much for coming on theCUBE. Thank you for having me. Wonderful to be here. So, before the cameras are rolling, we were talking a little bit about your career. You've been at this company for 12 years. 12 years. And in different iterations of the company. Right. Tell our viewers a little bit about how the company has evolved and also how your role has evolved. One of the things that I really have watched Pentaho go through is the evolution to be more customer centric. We began as a technology company.  We can write some code and it was fun. We enjoyed it. But now as we start getting more customers, we realize the technology had to serve the customer versus the customer serving the technology. That's a wonderful transformation to go through to figure out how do you take that technology, bend it to the will of the customer and have that customer at the center of all your conversations. That was something that took us about six years to go through. And where we had all the geeks kind of out of the room and put them in the back. I was one of the geeks, so I got excused for some of those strategy conversations. But we've got some good sales guys involved, some good marketing people who really brought that customer focus. Along the way, we built better solutions because we were listening more to our customers. It's interesting, when you hear what people want to do, you have a better chance of actually achieving it. Versus, let me build it and then they will come. It was some other way. What do they need? Now let me build that.  I mean, how do you do that? What is sort of the secret sauce to? I actually attribute that to some of my kind of non-Pentaho, non-technical training. I'm actually a pastor of a church in Orlando, Florida. So I've done a lot of theological studies, a lot of homo-letics that teach you how to stand on stage and how to relate to people even at a distance. That actually comes through when you talk one-on-one with people. They feel like you're actually listening to them. And I actually attribute that all to that training. But the underlying architecture still has to be malleable in order to accommodate that vision that you just put forth. It's kind of like the platforms versus products. Yes. You built a platform, you know, not a product.  Take us back to the early days. You know, was that part of the design thinking? Actually it was. Our five founders at Pentaho had that at their DNA. We had done three startups.  They've done three, I've done all three. But at the very core, it was we needed to build something that was embeddable, that can work in process. Something that could be molded to the client's problem. We understood that whatever we built would never be enough. It would never be able to solve all of the problems. So if we put gates around it, it will reduce what we can do. So we wanted to build something that was extendable. Something that was a platform that if we didn't have the functionality, you could easily build it. That's one of the reasons why we went open source initially. Where all the code was open source, anyone can extend it, anyone can bend it. Just because we understood there is no way for us sitting in an ivory tower to really figure out what's needed. And these decisions were made in the early to mid 2000s. So they way predated Hadoop. Yes. Then you had Hadoop saying, okay, we're just going to bring compute to the data. And totally different development paradigm and platform approach. Was it that sort of philosophy that allowed you to adapt or did you have to do a heavy lift to adapt? Actually it wasn't a heavy lift. I mean, the legend has it. I wasn't in the conversation, but I found in CEO had a conversation with one of our architects. I think they were having drinks or something at when the local bars or pubs around Orlando, around the Orlando office. They began to talk about Hadoop, put out a white napkin and just drew some things on the back of the napkin. A week later, we had a first integration with Hadoop. That's built upon that extendable, pluggable architecture that was there at the core. So that's really allowed us to adapt to new technologies to really catch the waves early and maybe sometimes anticipate the waves. So in this latest iteration of the company, Hitachi, Vantara, what can customers expect? The one way I can describe it is that it's maturity.  You can do things that you could not do as a small company. As great as Pintaho was as a standalone company, I believe we're going to be that much bigger when you have the whole weight of Hitachi Vantara standing behind you. We had our strategic advisory board yesterday and one of the things I shared with those customers is that now you will see us to attack things that we could not even fathom before. We have more developers so we can move features further, faster. We have more people in different regions so we can now do more services, help customers better in far regions like in the APAC region, for example, where we've struggled in the past as a standalone company. When you have a support center, a whole geography dedicated to Hitachi Vantara already there, it's now how do we, instead of build the infrastructure, just add that analytic DNA to the infrastructure that already exists. So that's what I think our customers will experience very quickly. We can do more faster. We can do more in different locations and we can even do more at a higher level of efficiency and in quality, if you would, because we have that backing of Hitachi Vantara. You were sharing with us off camera, you do a lot of traveling, you talk to a lot of customers, you spend a lot of time in an aluminum tube. When you talk to customers and you compare it sort of now versus in the early days, the technology when you guys started was sort of mysterious. And today, the technology, there's plenty of it, it's abundant and it's pretty well, generally well understood. Sometimes it's hard to make work, but when you guys talk about digital transformation and disruption, be the disruptor, not the disruptee, a big thing that's changing is the processes within organizations. Those are largely unknown. It used to be very well known processes, accounting or HR or whatever it was. Now the processes are changing every day. Do you have those conversations with customers and how are you as a company adapting and supporting that premise? One of the things I've noticed is that we have new roles introduced every day. All of a sudden we had a data engineer. They used to be called DBAs. Now they're data engineers. Now we have data scientists. We have some companies, I know they have data janitors and we have data prep. All these people now new roles in the organization all related to data. What we've been looking at is how do we make sure that every person, no matter their role, understands how to use the data. My interest and my focus here at Pentaho is not just around architecture, but also customer success. And we learned very quickly in the last two years as we've been on this customer success journey, you can install the best technology. It can be absolutely pristine from an architectural standpoint. You can get awards on architecture, but if you can't get the people to adapt, to adopt and use the software, use the solution, you've basically just wasted your time. So what we've been focused on, how do we identify those new roles? How do we identify what skills do they need? How do we do training on the solution that was built so that no matter what their role is, they understand how the solution can add value. How does the solution improve your job, improve your life experience, maybe get things done faster, maybe do more than you used to be able to do? But we've gotten out of the old tradition that there's a training department, accounting department, there used to be a time, I'm old enough to say this, where there was a business analytics team. But now every team has business analytics in it. It's part of someone's job to analyze the data, even if that's not their primary function. So how do you make sure that no matter the role, they have the skills and the access to the data? So how are you fostering collaboration between those roles? You always hear the story of data scientists spend 80% of their time trying to invest with the data, right? But you're right, you got the data engineer, the quality engineer, the application developer now. Data's like the new development kit. So how are you approaching the collaboration across those roles? So one of the things we've challenged our customers with is do you have a center of excellence? Doesn't have to be a dedicated center of excellence, it can be a concept or a virtual team, but do you have a forum where people can collaborate? If you're doing analytics in a silo, if you're doing data integration in a silo and people are not talking to each other, you're missing opportunities for efficiency, for innovation, even for understanding, wait, if I do this, that allows you to do this better. So how do you create that center of excellence? We have services now that our professional services team are working with our customers to start that concept. Let's train one or two people, make them the go-to people for everyone else. Evangelists, too. Exactly, they become the evangelists. That helps us in two ways, that one helps us when it comes to getting people to use the technology in the right way. When you have a platform, that means people have to use it correctly. You can build some amazing things with Pentaho, but you can also build some pretty, let's just say not efficient things with the same platform. And then of course, me being the customer guy, they're gonna blame the technology and I have to have that very delicate conversation. It's like, not really the technology, it's the builder, it's what you built, that's the problem. So we have some experts there that we can train and have them be the guardians, if you would, the custodians of the quality of the solutions to make sure there's consistency and best practices. But the other side, we're also a renewable-based company where we want to get the subscriptions, we want to get the renewals. So if I have evangelists there that can help the company use the solutions, adopt the solutions, that makes the renewal conversations that much easier. So I want to talk to you about measuring success because one of the things that really came out in the keynote today was Pentaho's underlying principles of social innovation and not just saving companies money or making them more money, but also doing good in the world and bettering society. So how do you pitch that to customers? How do customers respond? I mean, how do you approach that idea? So it's a hard one at times because most companies are focused. I need to solve my problem. I don't care what we're doing about the rest of the world. I have this major pain point. This is what I need you to focus on. And fair enough. Absolutely, that's what they're paying the money for. That's where we start. We start there. Can we get in to start solving some problems together? And as the partnership develops, now what else can we do? So it's not just, let me go sell this one solution. Let's partner for your good, but for the good of the whole society. Are there things we can do that actually make not only your job easier, bring you money, but actually make things better? So some of the customers I love, you heard IMS, you heard Dr. Elena there, L, excuse me, today. I met with some of the other ones that are working with IMS, Dr. Ben. That story is absolutely close to my heart because who doesn't want to save money on their insurance but who also doesn't want better and safer cars. That's a social innovation story. Absolutely, we're driving down the cost. We're helping companies manage their risk, understand their risk around insurance, but then we're also helping them get feedback on what makes cars better. What makes them safer? How can we avoid accidents? That is social innovation. That's what we're looking for. That's what Brian talked about with that double bottom line. How can we help you achieve your business goals but go beyond that to better society? So we've heard a lot about transformations. Satachi's own transformation. Pentaho, you just talked about Pre-Hadoop, the Hadoop big data meme, you guys caught that wave. Now you're sort of entering, I don't know if it's your third wave or not, could be your fifth, 10th, I don't know, but there's another big wave coming. Absolutely. Which is this industrial IoT. Brian talked about IT and OT coming together. And it's definitely early days, but what are you seeing in the customer base? It was interesting, Brian, very transparent. I said, how many Itachi customers are out there? Like a few hands went up, but not a ton. So as I say, it is early days, but on paper, the potential is enormous. It's a trillion dollar market, makes a lot of sense. You see a lot of big industrial giants going after this and you've got some real assets that you can bring to bear. So what are the conversations like with customers and where do you see that all going? The way we approach customers and what I hear from customers, they don't really mention the word IoT. Most of them don't understand that they have an IoT problem. All they know is I have this problem. So where we're using IoT is to say, you have that outcome, you desire that outcome. And to get that outcome, you need to get data from all your devices. We have an IoT platform that can help you do that. So where the word even IoT comes up for us is only in the solution, not in the problem. Where I think some companies are missing the mark is they're selling the technology. We have an IoT platform. Please come by our platform. Well, we've been a platform player forever with Empanthaho and we understand if you go there with a blank slate, say here's my platform, come by it, people don't understand it. They don't see the value. But if you can come and say, what's the problem you have? What's the outcome you're looking for? Let's focus on that outcome and back our way into the technology. And that's how we're approaching customers. That seems to be working so far. We have some IoT customers today that did not realize they were doing IoT. So big product announcement today with Pentaho, Pentaho 8, what can we expect? Scale, that's the one word I would use for Pentaho.8. This is one of the best releases I think we've had. We have a new functionality called Worker Notes. We have customers who've been implementing something similar to this in the field for years. We've now productized it. It allows customers to scale out. We've heard from Brian and from others that to do this right, you have to do it at scale. You have to provide this data, this analytics at scale. What our Worker Notes allows customers to do is spin up, spin down, distribute the workload on-prem in the cloud. We don't really care. It's just we have a workload. You've given us a set of notes that we can work on. We'll distribute the workload throughout that. And when we're done, we can spin them down. That elasticity, that flexibility is absolutely needed for today's data solutions. Great, Anthony, thank you for a great guest. Thanks for coming on theCUBE. Thank you for having me, thank you. I'm Rebecca Knight for Dave Vellante. We will have more from Pentaho World just after this.


Hello and welcome to the International Daily Roundup by People's Dispatch, where we bring you major news developments from around the world. Our headlines ICC Chief Prosecutor announces formal investigation into war crimes in Palestine UN reports over 50 killings in 1700 are arrested so far amid crackdown in Myanmar US House of Representatives passes police reform bill amid call to defund the police And finally activists organize protests across Chile's anti-government resistance intensifies In our first story, the International Criminal Code will launch a formal investigation into Israel's possible war crimes in Palestine. Chief Prosecutor Fatah Ben-Sawda announced a decision on March 3rd. The decision comes a month after the ICC ruled that it had legal jurisdiction to investigate the occupied territories. Ben-Sawda first stated in 2019 that there was reasonable basis to launch an investigation into war crimes being committed by Israeli forces. The ICC will now examine the war crimes committed in the occupied Palestinian territories starting from June 13, 2014. The investigation will cover Israeli aggression during the war in Gaza otherwise known as Operation Protective Edge. Over 2500 Palestinians, a majority of whom were civilians, were killed during this war. As per Palestinian and US estimates, another 11,000 were left injured. The investigation will also include illegal Israeli settlements in the West Bank and the confiscation of Palestinian land. Israeli air raids and missile attacks have destroyed at least 18,000 Palestinian homes in Gaza. 73 medical facilities have also been destroyed in the area, which has been under siege since 2006. Israeli attacks on Palestinians during the Great March of Return protests in 2018 will also be investigated. Rocket attacks in Israel by the Palestinian groups in Hawaaz will also be examined. Israel and the United States have both opposed the investigation. The Israeli government is reportedly also working on a law which will ban any cooperation with the ICC by its citizens or officials. The UN has reported that at least 38 protesters were killed in Myanmar on March 3rd. The death toll was announced by a special envoy to Myanmar, Christine Shahrer Bergner, during a press conference. Newsage and local media reports have shown police firing live rounds into the crowds and even using machine guns in some places. Protesters were also attacked using slingshots and there is a video of police beating up a group of medics. Use of excessive force, smoke bombs, stun grenades and tear gas has been reported in multiple places. While some estimates have varied, Wednesday's killings have pushed the death toll of Myanmar's anti-coup protests near 50. Riots group Save the Children has also reported that at least 4 children have died in the violence. Demonstrations continued on March 4th as people gathered in streets across cities. Myanmar now reported crowds of tens of thousands of people in the town of Meingyan. Protesters in Yangon set up barricades made of bricks while naval forces were also deployed in the area. Medical workers continued to join the protests and provide onsite care to protesters. Eye witnesses have stated that the police opened fire and used tear gas to disperse the protesters in Yangon. Military planes were also spotted flying over Mandalay. The forces have also continued to carry out mass arrests including journalists. UN Human Rights Chief Michelle Bachelet has said that 1,700 people including 29 journalists have been detained so far. In our next story, the US House of Representatives has passed a police reforms bill introduced by the Democratic Party. The George Floyd Justice in Policing Act was passed with a majority of 220 to 212 on March 3rd. The act is named after 46-year-old Floyd who was murdered by police officers in the city of Minneapolis last year. The bill will authorize state and federal officials to investigate police conduct including the use of excessive force. It also includes provision to ensure the use of body and dashboard cameras beyond duty officers. It seeks to create a registry of police misconduct and amend qualified immunity for the police. The legislation will also ban practices such as no-knock warrants and chokeholds. Data project Mapping Police Violence has reported that law enforcement officers were responsible for 1,127 killings in 2020 alone. Black Americans were disproportionately targeted and made up 28% of the victims. Only one Republican Congress member voted in favor of the bill in the House. The legislation has been passed days before a former police officer accused of Floyd's murder is said to go on trial. Derek Chauvin wouldn't go on trial on March 8th facing charges of second-degree murder and manslaughter. In the meantime, the legislation will now head to the US Senate for a vote. While the Democrats hold a tie-breaking majority, delays in the voting procedure are expected. Despite the bill's broad mandate, however, many have stated that simply reforming police will be insufficient. The mass protests following George Floyd's murder intensified demands for the abolition and defunding of police. Activists have argued that similar reforms bills passed previously in various states have been unsuccessful in ensuring substantive change. For our final story, we go to Chile, where protests against right-wing President Sebastian Pinera have intensified. Trade unions, social organizations, and student groups have announced a series of protests in strike over this month. Pinera demanding the resignation of President Pinera and the release of political prisoners. Here is a video feature of the protests held in Santiago earlier this week. We'll be back tomorrow with more news from around the world. Until then, keep watching People's Dispatch.


We made an estimate which has no impact on the financial statements, but which we can track internally So let's say customer five comes into the shop. They're like, hey, I made an estimate I'm here to pick up my equipment and there's someone else at the register and it's like, oh, I don't even I don't even I wasn't the one that did that But let me let me see if I can pull you up in the system here And we go into the system and we see in the customer side We could just click on the estimates So I'm gonna click on the estimates and I see oh, yes customer five does have an open estimate If you're in the business view by the way, and they were doing that you're like well I'm in the business view that would be in the get paid and pay area and then you can go into the customer section here And there's your estimates. Okay So then this is probably the way that you could you would normally do it But you might also search by estimates here. That's another way that you can do it or you might go to your sales tab And then search by your estimates here These are all ways that you can you can all statuses and pending open estimates typically, right? You could do that as well, but most likely most people would say if they came in I'm gonna go to the sales I'm gonna go to the customers and search by customer or I can sort it by estimate making it a little bit easier to Find the customer you can open that up and then I say, oh, yeah, you've got an estimate outstanding I can create an invoice with it and I could Have the payment that we want to apply out to it of $200. So let's do that now We're gonna apply that out. Also, just note that we've got this negative Kind of receivable of that $200 this once I complete the process of making the invoice That $200 will be applied to the invoice and will be everything will be good. Our financial statements will be reported properly It's a little bit improper right now because that negative 200 should actually be a positive liability So there's a bit of a timing issue where it's not exactly right But we can adjust that if we need to at the end of the period with an adjusting entry if we want to report the financial statements And internally this works really well. So let's go ahead and make the invoice So I think the easiest way to do that would be just create it from the estimate and So we'll just make the invoice. There's customer number five. We're gonna go through this and say let's do it 7227 I guess we can keep that date and then we'll keep the number whatever and then down here the items pulled in There's no income tax related to it because we don't deal with inventory items The items are the I mean the items are the things that drive whether they're sales tax or not And so this will be a pretty straightforward So we're gonna sell them this band set and then they've got the guitar and added guitar and some added amplifiers And we can then find the stuff that we hopefully saved for them and give them The stuff and what's this gonna do? It's an invoice It's gonna increase the accounts receivable by the 2260 and the other side is gonna go to the sales revenue driven by these items Which I believe went into its own revenue account because we told it to in the item Which is rental income of some kind Also note that I don't if I gave this to the client. It's not taken into consideration the $200 Pre-payment, so I'd like to have down here somewhere the fact that they already gave me the 200 not to record a transaction because that Transaction has already been recorded, but I'd like to see how much is owed so there's kind of a two-step process to do that I have to first I can post this I can save and close it. I'm not gonna give it to the client this way I'm gonna save it and close it and Then if I go back into customer five notice it kind of did it automatically here Where that it made the invoice now partial means partially paid and the payment which was Unapplied before has now been applied So if you don't want that to happen automatically or if you want to change it you can go back in here and uncheck it if you don't want that to happen automatically then You could turn off the settings in the cog up top to switch it But usually that's a pretty good system so I can say okay now it automatically applied my invoice The credit to the next invoice that I made if it didn't you can go in here and manually do it and Then I can go back into the invoice which should now be properly represented This didn't this didn't record any new transaction by the way of this payment It was already recorded the only thing that QuickBooks did for us is link this payment to the invoice It didn't make another transaction no added impact happened to the financial statement other than what we already talked about With the invoice so if I go back into the invoice now I can give it to the client this way and they got this little thing down at the bottom Which says oh yeah you you already paid the 200 and I applied that out so now you owe us 2060 the invoice is still just recording an increase to accounts receivable of the 200260 and income of 200260 The $200 is just representing the fact that they already paid us an advanced payment that is now being applied out But it's but I already recorded that before it's just here for informational reporting purposes not to record a new transaction But I can now provide this to the client if I so choose


Thank you for coming. Last day after lunch, it's not very easy to come here. The topic of this talk is about integration and the easy solution and development on constrained IoT devices. This job is being done by me and Tushar and the ARM team. I'm basically in Lisbon, Portugal. I've been working with Leonardo for some time. And now I'm working in ARM landing team to try to bring these solutions to upstream. And I've been working with Tushar at ARM, which is on the IoT platform team. And we're trying to more or less create a reference platform for these kind of devices. The hotline for this talk is basically we'll be talking about why the motivation for these IoT systems, for them to be created and existing. A simple hardware system overview regarding a platform that is more or less like an example that we are working on, try to define the constraints and what is a rich IoT platform. And then we go to the software side of stuff and overview and explain more or less like the tenification integration parts that we have done to reach the solution that we are halfway there. And we have a small demo only to show you that something is working already, some future work that we intended to do, and Q&A. So basically, we try to find the motivation for these kind of systems and why there is a demand on these kind of platform. Basically, it looks like there is a necessity to have offload for several parts of the workload in IoT. And you can have Cortex-A as your application. And this increase and the wider range of application that a IoT device can have. So also with that in mind, security is also a lot of on the news today. And basically, we will try to show what in this aspect can be increased and updated on this field also. And why Linux and try to make it on these kind of systems also to make it work and so on. So in here is more or less like a hotline of hardware system of review. This is an example. It's a platform that ARM developed. It's called Corestone 700. And it basically has a secure enclave, class M. Normally, it's an M0 device. Then it has firewalls between all the components in the system. I have an A class subsystem. In this case, in this platform, it's an A5 or A32. And you can have a variety of Cortex-M doing the all the tasks that you want and need to do even in real time constraints and so on. So basically, they have a firewall dividing all these access and normally the firewall is set up by this secure enclave that set up everything including memory and RAM and ROM and what can see what and so on. It's a constraint system regarding the specifications. And this is basically what is used. So we try to reach to a definition of what a tiny system would be. And in this case, we try to constrain the memory to four, eight megabytes because four, really the workload that you can do on four with Linux in class A. It's really limited. Eight on the flash to allow you to have a more robust OTA system like A, B, and B image. So you have this kind of a mix between the Cortex-A and M's doing different kind of workloads in your system. And this can be customized for IoT agents that normally will be running and you can have different SOC solutions based on this kind of architecture. Regarding software overview, so on the secure enclave we can have a firmware, a bootf firmware. We are trying to port it, TFM also, to run in here. So this will be the responsible to set up and put everything in memory and then we'll take the other CPUs from reset state. And the communication between these devices is handled by a message handling unit. And on software level, you communicated using, for example, OpenM is what we have today. Doesn't mean that needs to be the solution for this. So then you have the class A where you can have some trusted service in the trusted execution. Linux kernel with XIP, executing plays, root FS, and an IoT client, for example. And then you can offload to the Cortex-AMS, what any other workloads that you can have it. So what we tried to do here was, in this first stage, was to integrate already stuff that is there, out there, and try to make it the integration. So we started using Try2Nify, inside ARM, the build system. So Yocto was selected for this task. We created our own distro around it and tried to build the image using the tools that Yocto allowed us. So at the end, we have that image that you can see there. So the output image, you can see that the kernel XIP, more or less 2.2 megs, the weak image, it's 8 megs because we are creating all the partitions that we need in there, so it's using the whole space that we have. But the Chrome FS XIP is 1.8 megs. Regarding the kernel, we're trying to use what it's upstream. We don't have any special kernel in here. We didn't change nothing yet, but as we will try to improve this kind of tenification, we will for sure do something more extensive on this part. But so we needed to add some options to disable, for example, multi-arch in ARM, because with that, we cannot use kernel XIP. We tried to reduce the sets of CPUs that we support on this configuration. We enabled some too, and you use a very reduced F config. So this is more or less like what we have the results of run, or after a boot of a system. You can see that the total, this is the kernel memory line, and this is the free command after the system is running. So without any load, it needs to be set, but we have a system with 1.8. And a lot of, not a lot of memory available, but we can run applications in there. So regarding the root 5 systems, we choose ChromeFS, because it allows us to use XIP also for the root FS. So we choose it, and we want to thank Nicholas Petr, over there in the back, for his work on this part. It's working out of the box very, very good. So we didn't have any issue with this. So it has direct access flash. It doesn't go with the RAM and caches and everything. You can just overwrite and go over that, and you don't need to increase your RAM users, because of this. So for the read-write file system, we were looking for solutions also. But one of the file systems that looked better for us, and it's more compact, and it's done in taking an account, and it was development thinking on real-time OSes. So memory allocations are really little, and you can more or less know what you will expect at the end of the day. We choose this little FS. It's an ARM file system that is being used on several real-time OS. It has all these features that normally are a good file system for these kind of devices needed to be, it's power loss is resilient, we're leveling and bounding. It has a design, and it's a block pair update. It's very compact, and it's easy to use in this kind of environment. Right now, I'm trying to port it from scratch to Linux, halfway there, a little bit more. Try to upstream it, let's see if it landed there or not. But we will try to make some measurements and see even though the specification also for this file system is in evolution, we will try to implement it and try to bring it as a spinal nor, yeah, only 8 megs of nor flash. We are charging it. So this is halfway there. Just adding some more and then do all the tools that we need to create to have it on the upstream kernel. We need to have fuzzers. We need to create a lot of user-land tools that support and test all this kind of system. So I'll try to show you. It's just running on. So basically ARM has its own models. I don't know if anyone knows what models are more or less like Qmoos, but ARM has a concept of emulation of their systems using software. So this is basically running on the platform that I told you ARM corestone 700 FPP. And I will just run the image that we saw there. So I'll try to explain. So this is based in the middle. You have the two. This is a Cortex 832 running in emulation. And on top, you have the Cortex M0. Running the Cortex M0 there, it's the secure enclave that just allowed the A from reset. And you have an M3 in there that it's not out of reset. So I will just let me try to take these away from your front. So this is the logs of the secure enclave. So the secure enclave of the boot ROM on the secure enclave just loads everything in memory. The BL32, the TB, and then it brings out the OS from reset. And then this is the boot log of the kernel with this image. It has a constraint system. But you can see that you have. And this image is completely built with the Yocto. This is available for you to download, to build from scratch and everything. Regarding the model, that part I don't know. This is you need to check up in ARM how to get the model. It's not so easy, as I believe. And basically, that's the system that we have run. Then after to have more features, we for sure need to increase here the memory usage. And for sure to have some dynamic on the system. But as a reference booting system, this is what we reach now here. So regarding what we will do next, for sure finishing and try to upstream little of us if there is interest to have it in a kernel. I think we'll be. I saw, for example, yesterday, a presentation from Airbus where they also have something like this interest. Instead of M class devices, they have R class devices to offload critical stuff to Cortex-Rs in there. So it looks like there is interest in these kind of systems. And this kind of, and even the Cortex-R that they are using are MMU less. So a file system like that maybe makes sense on a system like that. There are a lot of compilation optimizations that we can do. We will start maybe try to use Clang to use LTO jointly with them too. Also, there are ARM team. There is development feature for Clang that is basically outline. It's more or less like the inverse of the inline to save space. So they already reach good results in Zephyr. 10% reduction in size. So looks like promising stuff in there also. They didn't try on Linux kernel. But maybe that can be also a good optimization part. And then when we reached to some specific workload necessity, we can target and try to make it really, really optimization on that workload. Right now, this is a reference platform. And it's not specific to any workload. But we're trying to make as ARM a generic platform. So we won't have it like that. So basically, that's it showing the work that we've been doing on this kind of. You can have all these. In here, you have the resources where you can fetch. There is a complete Yocto builds layers. You have a meta-ARM layer. In top, you have a meta-Corestone 700 layer in there.  And in the end, we'll reach an image like the ones that I showed you. And you can also check the product specifications that ARM already have in there. Regarding ChromeFS GitHub from Nicholas Pete, I have the tools and have what you need to know. And littleFS, it's on ARM embedded tree. He has a very nice comprehension spec and description of the file system. So it's really well documented. So basically, that's it from our side. Questions? Yeah, but since I don't know what Kimu has in terms of running this kind of stuff like 2Ms and the MHU communicating between, I don't know, the emulation part, if it is ready for this kind of, sorry. Ah, OK, OK. So the question was, if we thought to run these on Kimu instead of using ARM-specific models that are not so available to everyone. And my question is, we didn't try it. And I don't know if it is prepared Kimu to have all these infrastructure that we need to emulate all these software. Sorry. Ah, OK. Yeah, we used, for building, we used as main distro. It's on top of Poke Tiny. Basically, if you go with Yocto, you have Poke and then there were work to create a tiny image. It's Poke Tiny. And this generated with the busybox and so on. So a muzzle, muzzle. It was on the slide. I forgot to tell, but it was on the slide. It muzzled on this. Sorry. Yeah, that will be the, we are, so basically that is a way to do the OTA, the upgrade. So basically, our image could fit in four megs of spinor. We are just giving eight to guarantee that if anyone wants to use that kind of OTA. No, we are not, we don't have an OTA. OK, thanks. We don't have that. I think that is very specific to the implementation. That's the other case where, no, not that, not that. Yeah, so basically with access with the spinor directly as mapped, in memory mapped, spinor. So the spinor is memory mapped. So you can, if you have a AB system, you can directly download it or because these are XIP. So it's uncompressed and everything. So it needs to fit in there. And if everything goes wrong, you still have. But if you go, I think on this, it makes sense to have an AB OTA solution. Yeah, yeah, it's already there. Yeah, let me take your mic. OK, maybe I can tell a bit about ChromeFS because I'm the author of those modifications. So the thing is, within the file, you can mark part of the file that you want the kernel to access with XIP. So for example, if you have an ELF executable, the read-only segment will stay in the flash and will be stored there uncompressed. Whereas the data segment, which is modifiable, so it has to be loaded in RAM, that part will be compressed on the flash since you have to copy it anyway. So why not store it compressed? The tool that creates the image right now, it has the ability to detect those segments in the ELF format. But it could be extended for other file formats. For example, if you want to notice that you have a JPEG file, which is already compressed, you don't have to try to compress it again so it can be accessed with XIP. So all those things are already upstream. There are in the tool as well. Is it each block or just the ELF section? It's each block which are part of some of the ELF sections. So you can do it block by block? Yeah. So I guess it needs to be in the tool. It's in the tool right now, but the only thing I implemented is to decide which block are part of specific ELF sections. But it can be adapted to whatever you want. So it's done. It's there. OK. Thank you. They are on there. Tushar, you have the. No, first you, Tushar. I'm not. Tushar, Tushar. Have you ever considered about using a unicorn for the size reduction? Sorry? Unicorn, maybe long place. I ask the question, long place. OK, never forget about that. Any other questions? So basically for upstream, just missing little affairs. Everything else is already. So you can boot it with DCS on Linaro repos. If you go get Linaro landing teams working, you can grab all the source codes that I'm running here. You can grab all. It's built from source, built from scratch. Everything is upstream. The only thing missing that is also not running on my demo, it's little FS support. It's the only thing that is not running everything else. You can download it with the source code and everything is upstream. Even support for this kind of platform, it's on TFA already. So it's upstream on TFA. You would, we have two or three out of three patches, only to make some last minute changes on memory addresses and so on that we moved around a little bit to fit on this. But you can go and check the Yocto layer that has all the recipes. And you see that all rep repos are upstream repos. We don't have anything. We are working to create a meta arm. It's already, you have a mailing list on meta arm called, on the Yocto open embedded called. And it's already, I think there is already a placeholder for meta arm layer. It will be upstream to open embedded real soon. Right now it's on there because we are merging also other arm other departments also had their implementation of the same recipes. So we are trying to join everything to go to open embedded.org to have that. You will find all the arm related recipes. And we will try also to port all other platforms from arm to be upstream directly to open embedded. We use this platform for our development but the changes are really generally for the platform. Yeah. FPGA landed last week in our tables. I don't know. This is more arm than software. Also 700 is a reference platform. You can contact Tom, actually, to buy that. And there is a PGA for that and there is a model for that. So we have a couple of partners. Yeah, you already have some marketing stuff in there. And you can search in there. Any other questions? Thank you very much. Thank you. Thank you.


They pigeonholed the whole issue into one community and then they sent their people in, the RCMP included, went in on behalf of these companies, the companies had their own security to come in and start to create divisions amongst the people. Assuming that the mining exploitation in our territories that is being imposed literally on blood and fire, that is to say that not only does the exploitation occur with the territories, and therefore the two things are linked to each other, the exploitation of the territories and the exploitation of the women's bodies. Over 90% of the women that we talked to did say that the mine had clearly created problems in the community. The most dangerous impact that resource extraction activity is having in Baker Lake is increased violence against women and girls. July 2010, until the end of September, there have been at least 72 Indigenous peoples killed, documented at least. Among the 72 are eight Indigenous women, one of them are pregnant when she was killed. But besides that, as they begin to participate, they begin to lead movements in defense of water, in defense of forests, So there is a stigmatization of the society itself to say that they are women who are no longer from the house, that women, as men like, are from meetings to meetings. The Inuit women working at the mine were mainly working as house cleaning staff for a predominantly male workforce. And so this did make them very vulnerable to sexual harassment. What we see across the world and in Canada on mining projects that are already in existence, the increase of violence against women because of the increase of revenue that leads to the increase of alcohol and drug abuse, which leads to the increase of domestic violence.