The Tiger financial news network Welcome folks, we have the now industrials trading up a hundred and seven Nasdaq's up ten I know Nasdaq's up a hundred and two S&P's are up ten gold gold contract up $43 trading a 2010 announce we have silver up 27 cents 23 dollars and seven cents an ounce light sweet crew down a buck 42 $69 48 cents a barrel notes and bonds a ten year note up 23 ticks trading 115 26 the 30 year up 18 6 at 131 15 and King dollar King dollar up 159 ticks trading out at 102 508 the year is at 108 The yen is at 131 of the British pound is at 122 to one US dollar We get over and take a look at the S&P's folks bottom line is that you know you're talking about a bear market, man This is pretty intense. So, you know from eyes to lows out here today We went from 4049 down to 3950 and about a heartbeat now it just bounced With 21 points like in a heartbeat do which is pretty cool, man. So What we have out here this is gonna be cool watching this shake out, okay, so let's see it's only one minute into it Okay, so these lows out here They have some volume in them and we're gonna be back to this low this low out here is 3950 Okay, because we did a hundred percent move of the move, you know, we did more than a point six one eight It was I was actually just almost just over a point six one eight if we put this up what you're gonna see Just over it gave it up in spades Gives it up does a hundred percent move of the move now you get the big bounce the bottom line is that that's you know We're gonna we're gonna be at the lows are lower than the lows at the close This is one of these days folks what ends up happening is that there's so many people that are trapped At the highs because we went down so fast yesterday see it makes sense He got the bones going there's plenty of trades that thought okay to high would hold I get it Okay, but in a bear market. This is where it's just brutal. Okay, so the bottom line is my take This is going south and we'll go over to the dollar. It's about the dollar man That's it's all about the dollar with the dollar did here, you know It's been trying to reject this lower price. It did it instead of doing three days in a row out here And what you have out here today? It's still dealing with the exact same bar how it came off the last time the bar that we're talking about here is the 101 546 we went to 101 9 915 and then we're at 102 517 right now stay right there folks who come right back


so people I am back with another outriders video and today I'm going to showcase to you guys what I've been doing well for the past day or so in this incredible farm which will allow you to well it gives you the best chance in getting all the legendaries you can literally max out all of the materials you can collect as you can see I've maxed all these out I've got 25,000 scrap that you can't get no more a thousand lever we have 1,000 iron and we have 10 titanium now what this does well what this farm is it's basically let me don't know if this guy kills me but what this farm is you basically run down here you run to the boss I'm probably gonna die but it doesn't really matter because if you die he respawns anywhere that's the best thing about this so we just I'll quickly demonstrate to you so he comes out of here see if you can do anything while I'm here probably not but okay so there is his name's the captain as you can see this guy as far as I'm aware has the best chance to drop those are legendaries I personally myself haven't had one yet oh but do you like to look at that so once you kill him you die and when you die you respawn literally where I'll start this video at so you can just here we go become straight back to him wins and repeat and you do this and you'll get tons of loot I can't say you'll get tons of legendaries but right now it's the best legendary farm in the game and I'll show you what the mission is and how you select it and repeat wins and repeat it and farm it in a quick second and just killing him again see what we can do people see what we can do chop him up if you're quite near my streams this is what I've been farming some I'm still in search for that one legendary now more enemies do come out of this door these breaches they have a chance of dropping legendaries to but if you if you're strong enough to take him out that's cool okay so this mission is it's this mission right up here called Tehran infirmary now complete the game obviously complete the demo so once you complete the demo you can go back and reform anything any side mission any mission you want but as far as I am aware this is the best place to do this because like I said once you kill that captain you can well die you can let the other add to kill you and it'll respawn you literally where I am right here so you can rinse and repeat this now my power playing with him on stream guy let's know doing this and his reaction was quite funny because we're doing it for literally three or four hours I'll show that in a quick second now if you do mess up and you accidentally take out all the enemies or you do progress I'll show you what you can do to reset the mission which you can also do this to reset any missions if you want to go back and farm any chest that you can get after a boss and you can do that let me just kill this guy again and as you can see I'm on world tier 5 I'll show you what I'm using on my trickster I didn't even activate my crazy bullets then I call them super same bullets as you know if you die here I'm talking about ain't got nothing and you die you'll respawn literally well started now if you do this in a team I think there's an increased chance you will get more loot but I can't confirm that I know it's a lot harder if you in a party as enemies scale up so doing this in a team it will take you a lot longer to kill the captain that's down there as you can see I'm doing it relatively easy here on my tricks and I'll show you what I'm using wrong button I'll show you what I am using you can see my arm is more or less max for the demo and I've got a few additional benefits with these mods that's very important to actually see as well a lot of blues will drop here and it's important that you select and use the right mods to basically help you build and farming and things like that so a lot of these things here as you can see how power not all of them do because I do make some match my abilities depending on what I'm farming but for the majority these help quite a lot now weapons I've got no legendaries I'm just using what I've got here this is probably the best weapon to do this with well any light machine gun with a high magazine size or clip size because my right bumper ability is I can never remember I call it super same bullets I can't remember what it's called people it is called twisted rounds okay so twisted rounds is quite beastly gives you basically makes you a clip do extra damage now I've got a mod somewhere which gives me unless I accidentally deleted it and not realize I think I might have I know there is right there additional match twisted rounds this skill is effective for two magazines before triggering the cooldown this means I get 200 bullets people in this weapon of extra extra damage and normally power absolutely incredible so I'll just look to this bus here I'll put my bubble so I seem twice because also I've got a mud on an armor piece which gives me two slices I think that may be on my that's not my helmet where is that is it that one there there we go same full blade slasher this kid this skill so you can be activated one more time for triggering the cooldown so I can slash twice that's pretty cool so yeah we'll do it one more time and I'll demonstrate to you how you can reset this if you want to also another important thing to do as well which I will show you in a second because there's a good chance you'll come here you'll kill him and die at the same time and learn if you don't do this you'll probably lose that loot and you don't want to do that people you honestly do not want to do that I'm probably am gonna die here actually I haven't got my bubble now I've got my bubble there we go and like I said I'm doing this on the trickster I can't really talk for other bills because no I thought that was I thought that was yellow event I thought that was yellow event sometimes they pop out and I do look yellow oh wow so I'll show you now what you it's very important you do because like I said you can die and if you die and you don't have this selected as a good chance you will lose that loose now where is it work there we go there auto-loot minimum rarity select the luxury of items to be automatically picked up so what this does is I've got my uncommon because I was just basically doing it for the materials you don't have to do this you can have if you get full upon materials you don't need no mods really no point you having this uncommon but you can have it right the way up to a legend though it's probably best you play it on rare or epic though because Reyes also I know we're not in the full game yet but when it comes to the full game Reyes can drop with mods obviously dismantling items you get that mud to use on other things so yeah it's probably best to have him at where which I'm gonna leave mine on right now so if you die and you don't pick up that loot you will automatically pick it up another thing I will warn you with as well if your inventory is full that loot will go to your stash which you can not access on the demo now seeing as we've got stuff here and another thing I'll warn you as well I got a problem of highlighting you can highlights numerous strings and dismantling them all at the same time anything really over 20 highlighted at the same time trying to dismantle it crushes my game so just be warned that it may do the same for you as you can see I got no materials for that and if you dismantle weapons from here you will get iron but you can actually go to vendors which would do as well in a quick second I'll show you and get this right here which can also buy you get scrap which can also buy all things with so like I said now if you mess up this mission you accidentally kill all the enemies here and have to progress what you can do is to reset this mission or any other mission or all missions you go to the main lobby return to the main lobby and it's pretty simple people it's pretty simple then you'll go down to this here select story point and select anywhere where you want to resume and selecting say what we're just doing there speak with Jacob there to leave for the first city this is basically the end of the demo but doing this you can go back and farm more or less any mission so that's one I select I go back into it go back to that place which I'll show you in a second where to go and just farm away it really is that easy guys this is by far the best in the demo right now to earn those materials and that loot even though legendaries are quite there but there's some people out there that I got quite a few of these so let's go I show you exactly where the mission is but first they'll show you the vendor you can sell stuff to to maximize those materials because don't forget if you do plan on purchasing the full game or your gear will progress further will progress for until the full game so this guy here you can sell your stuff too again I won't get nothing for it because I'm maxed out on things well just for instance say that that and that you can sell all these well big buggy sell three items and you'll get resources for them you'll get scrap for them so if you need scrap sell them if you need scrap sorry items if you need iron dismantle your items I'm guessing army you'll get leather from as well if you if you dismantle your army you'll get leather I'm pretty certain yeah basically it's simple it's quite easy guys I'm sure you'll get the hang of it so that mission is this right here so you just run over here and like I said this is definitely the best farm right now in the game for those materials and those legendaries as well as just ranking up that gear getting that gear as high as possible now I do think it's around 209 205 I haven't had anything drop higher than that in terms of the legendaries I do not believe in terms of armor can drop from this demo just weapons because as you can see my armor I ain't getting anything higher than what I've got here two or three for the helmet two or five for the chest piece two or eight for the legs or pants the gloves I'm getting a 196 I've had nothing higher I found this for hours and for the feet or legs I have two or five let me just I'm pretty sure it is levy to get from dismantling these we didn't pop up because I'm really full but yeah yeah ignore that ignore that so to farm that do you just do go this way and we know all the way down here and like I said this will work I mean there are chests around here and in other places you can go run to a farm go back to the main lobby select the mission again go back into a farm the chest if you want to do that well I've had no lock in terms of anything special dropping from chest so I just think this farm here is much much better than you just run to this now we'll warn you do our group of ads you first have to take out before you can start this farm of the boss which will quickly be able isn't too hard especially if you play solo so like I said you play in a party play with your friends these enemies get much much harder for some weird reason that's why I do believe that loot get more chance of it dropping if you're in a party I don't think that's been confirmed by people can fly but it definitely seems that way let's just let's kill them quick these guys here as well as breaches I've got a power I'll show you in a minute actually whoa there's a lowest reports of the breaches dropping legendaries too so yeah get chat motherfucker get chat anybody else get chat motherfucker there's also a chest right on this corner as well where's he gone are they well I could not see him then I could not go here is the nut okay there's not so this chest right here you can farm there we go a bit of a loosey autopicture do you want that nope from here guys this is where the farm starts so again run down here just run over here you can ignore all the other enemies unless you do you want to farm them but again remember to keep some alive so they can kill you the captain's is right there there he is oh activate my super Sam bullets and a shoot shoot shoot shoot shoot shoot shoot there we go that's how it is now you can just die or if you want to kill the breaches that come out of there you can hang around for them but you don't have to see also all looted that blue rare for me then and it just simply means to repeat these people when you fill up or full up on weapons and armor you can even dismantle them inside your inventory like I said and get that iron and leather or you can go and sell them to vendors for that screw up again you can only get 25 scrap and a thousand each of that iron and a lever it's gonna kill you one more time there's gonna end the video people I mean I found this dude for so long and I just you might look my island use the worst in the world I mean no one's got worse island G than me you watch me for destiny or no actually one more let's go one more time let's go one more time just get addicted to it just get addicted to it yeah after I'm done here I'll show you my main's reaction yet when he got that legend day from here was from this in a party that was brilliant he got he's like a kid kid in the candy shop I will chop your ass bitches what are you gonna do captain what are you gonna do captain what are you gonna do just agreeing again all these camp people all these can't believe those mats again like I said like I said your focus you know you're losing that focus is on transfers over it onto the full game if that's what you want to do and there's a chest up there as well no we're gonna run that one more time because there's a chest up there forgot about the first time you run this you can grab that chest too we're gonna do that we'll do that grab that chest because chess can drop legend days also I'm not sure about the drop there on these I mean obviously the higher the tier the better you can do this on any tier though I have heard that legend day is gonna drop on tier 3 4 or 5 so yeah you may just do this on the tier 3 and get lucky well that ain't me people I ain't getting no luck at all you you clapping in the back of your head who you clapping in the back here and I have plenty of areas here what level of those actually oh you're decent I take you nope lower okay so let's just go up here shut them up got the chest just a couple of greens so yes guys there's I leave you now to watch my mates reaction of getting that legendary from this is great and I'll catch you guys on my next stream if you want to catch me that kind of streaming modest every day now this destiny whatever floats your boat so yes if you're interested in outriders I'm watching someone play make sure you subscribe and turn those notifications on but guys thanks as always for stopping by and hopefully I will see you on that next one whoa whoa it's now it's now I've got it I've got it I've got it I've got it


Dave is running the interview today. Just look at me. Look at me, not the camera. What do you do for fun? Do you have hobbies or interests? Excuse me. What kind of experience do you have in this area? Have you ever sold anything on the internet? How are you on the phone? Do you have your own vehicle? Is this how you always dress? How do you feel about wearing a suit and tie? In terms of health insurance and holidays, we should talk about that. We'll start with two weeks of business days. From there, we can review that annually. Your references, we're going to call them up. What do you think they'll say?


Hopefully they'll log back in here and so Tom, there are 37 people anxiously waiting. Your first slide and how about if we get started a little bit late? I really want to thank Tom and the folks at Shippable, Abby, and Tom for coming today and giving us this talk on the ICD workflows using Shippable on OpenShakes 3, which I think will be very interesting for everyone. So Tom, I'll let you introduce yourself. Thanks, Diane. And like Diane said, my name is Tom Trahan. I'm from Shippable. Shippable is located here in Seattle and also on the call today, I've got Abby Cavalli, our CEO and co-founder, and he'll join us in the Q&A session as well as Ragesh Krishna, one of our lead engineers. So just a quick introduction to Shippable. We're a company that was founded in 2013 by Abby and Manisha. We've got 24 people. We're based in Seattle. We have a development office in Bangalore as well. We have a fairly healthy customer base at this point with almost 50,000 developers using the Shippable CI CD product in the cloud with covering 8,000 organizations. Tom, you've gone quiet. Oh, have I gone quiet? Is it not coming through very well? Yeah, it's coming through. Okay. I'll keep going here. So the purpose of Shippable is to make the complex problem... Don't worry about it. Keep going, Tom. Okay, got it. A building, testing, and deploying software frictionless. I mean, the goal of Shippable has always been to help enable software delivery to make it as automated and as efficient and as fast as possible to discover bugs early in the process and enable software changes to make it all the way into a usable state. The challenge, of course, is that it always starts with a fairly simple problem when you're talking about software change, which is how long does it take to make a small change to an application that you're supporting? But it becomes a more complex problem when you extend the question to ask, you know, how long does it take to make a small change and get it to the customer so that they can use it? And then, of course, it becomes an exponentially bigger problem when you say, well, how difficult does it become as you add more developers to your application team, more components in your application, more environments that you're going to manage and move that software change through as you validate throughout your entire software delivery lifecycle? So for Shippable, we exist to help solve that problem. And it's really to help manage across the end to end lifecycle that you see on the screen right here from source code and from a change in source code through all the validation steps necessary to merge that code into the master branch to be able to perform unit testing and continuously integrate that code back in to be able to now with the advent of containers to be able to generate container images and be able to easily access those images for use later and to deploy those into dev and test environments where full functional testing on full topology applications can occur. And then ultimately, of course, to be able to promote those changes all the way through to the production environment where they exist. And so for us, you know, we now call this DevOps 2.0. I think everyone's familiar with the term DevOps. It's been a very popular topic for multiple years now and rightfully so because it's ultimately been attempting to help solve the problem of how do you make this workflow here as efficient as possible? And some of the most inefficient elements of that workflow come have to do with the many handoffs and the many various tool sets that exist across this lifecycle. When you talk about development activities, you talk about deployment activities, testing activities and operational activities, you end up introducing a lot of complexity in terms of complex process, many handoffs, many roles and many different tools involved in that process. So for us, DevOps 2.0 is a concept that really is, you know, taking that great idea of the great objectives of DevOps, but saying that now with the advent of container technology, and if you look at the technologies that OpenShift 3 is bringing to the private paths, it enables you to essentially truly automate this workflow and with a lot more efficiency and a lot less effort than ever before. And so for us, it's about enabling these end-to-end workflows for continuous integration, testing and deployment of code changes throughout that workflow, really getting to the point where one click code change all the way through deployments into your production environment becomes a reality for software delivery teams. And ultimately, to achieve that type of speed, it needs to be as easy as possible and as usable by as many people as possible. And so we believe DevOps 2.0 ultimately requires that you can do DevOps without DevOps code, without a separate set of languages or tools or infrastructures that you need to manage or learn in order to be able to do DevOps. And so for us, kind of simply, you know, we think it really comes down to the fact that DevOps really is evolving. It's going from kind of that concept where folks talk about it as a cultural idea that we just need to get disparate teams within that value chain to come together and collaborate more effectively. And it really is that they need to be enabled properly. And with containers and with really the decoupling of infrastructure, it really does allow for this to happen where the dev side of DevOps really represents the application delivery team. Everything, and that doesn't necessarily only mean developers. That's anybody involved in application delivery. But it really means that you're focused on continuous delivery without separate DevOps code. And to do that, you are leveraging smart containerized environments that are aware of changes throughout the life cycle and are executing various validation activities and promoting throughout the life cycle as long as things are proceeding as planned. And then from an operational standpoint, then the focus really separates to talk about managing the decoupled infrastructure. And obviously with OpenShift 3, you've got this clear concept available in the platform or with the Kubernetes layer abstracting the application layer away from the underlying machine hardware. And so for shipable CICD, then our product that runs on OpenShift Enterprise 3, it's really, we think, a pretty compelling offering that's going to make setting up these workflows, setting up continuous integration, validation, unit testing, integration back into your source code repo as part of that pipeline, as well as those deployment activities into your test environments and ultimately all the way into your production environments. Very easy to configure and very easy to start. And so for us, it's about extending the value of OpenShift with these workflows and various tools that we've developed over multiple years in our CICD solution in the cloud. And then enabling that anybody who is adopting the OpenShift platform to truly adopt the platform and not maintain a separate set of CICD infrastructure tools outside of that platform and need to manage those independently. And lastly, as you heard me mention, it really is about being able to do all of that without writing separate DevOps code to manage that. And so kind of just briefly, some of the details we'll go into and hopefully you'll catch as we run through the demonstration is shipable does bring native continuous integration to the OpenShift platform.  The shipable product provides end to end traceability and history so that you've got full visibility into everything that's happened throughout that pipeline. We make it very easy to set up end to end workflow via our UI. And we have made it so that you can establish environments within your software delivery work pipeline that really match the SDLC that you currently use and are familiar with. We try not to be too opinionated here and telling anybody how they should run their IT delivery processes or their software delivery processes. And so we make it so that you can flexibly configure the system to match the way that you work. And then lastly, we make it so that the act of automating that pipeline and essentially initiating activities in that pipeline become fully automated or executed with a single click inside the user interface. And then lastly, you heard me talk about the fact that when you adopt the OpenShift platform, you're doing so to eliminate a lot of non-value at activities and to bring more and more of the tools necessary to develop and operate software into a single platform. And we think it makes perfect sense that you do the same thing with your CI CD infrastructure as well and not maintain a separate one outside the system.  You heard me talk about that workflow from source code through CI CD through image registry through the Dev and test labs environments plus the production environments. This is that flow that gets implemented and it is, like I mentioned, running entirely on the OpenShift platform. This one page slide will be available after the presentation and it becomes, I believe, a good one page reference for you as you think about how to set up these deployment pipelines and just think about this in terms of the demo that we'll be going through here shortly. So in closing, before we jump into the demonstration, I just want to kind of mention if you're going to wrap it all up into a single summary statement, you know, what shipable CI CD does is bring seamless deployment pipelines to OpenShift Enterprise 3 without writing any DevOps code. With that, let's head into the demonstration and we can kind of see a hands on view of the shipable product running with OpenShift. And so you'll see me bouncing back and forth between a few windows here in the demonstration. What you see here is I've got my OpenShift console running here and you can see the projects that I've got running out there. This one here will be jumping into a little later. It's it's the my OpenShift Enterprise 3 demo project connected and integrated with with shipable. We'll also be jumping into a sample application. We're going to walk through the end to end flow of what it what it what it looks like to make a change in software and promote that change all the way through the system. And and then and we'll be spending some time in the shipable user interface as well. And so when we jump down here, typically when I come into shipable for the first time, I'm going to access it via the authentication of my source code repository. So in this case, I'm going to go ahead and and join with my GitHub credentials. And I'm taking into to the main dashboard page here. And you can see here on the main dashboard page that the last activity within my organization and all the organizations that I have access to all peers right here in front of me. So what you're looking at here is is a place where you can see the last activity related to your continuous integration builds and tests. You can also see that you can then quickly access the other elements of the system in terms of that flow. The way we think about it within shipable is there's the front half of the flow, which is everything around preparing code to be deployed. And then there's everything around the act of deploying that code and then operating that code. And so the preparation piece happens for us on the front half of that workflow within the CI portion. So between source code repository, the CI CD functionality of shipable and the image registries. And then the formation side happens on the back end of that workflow. And that is connecting image registries with your dev and test labs or environments and and ultimately your production environments as well. And so, you know, just just to kind of give you a little bit of a sense of where we are right here before we jump into the end and workflow is I'm going to narrow this down and look just at my personal GitHub account. You can see here, you know, I can have access to multiple organizations within the CI system. And so I've got access to all of the shipable activity and all the repositories that shipable manages. And then I've also got access to my own personal forks and personal repositories as well here within the system. And so I've got a demo application that you saw me jump to a little bit before. And it's an application that I've got two repositories out there in in in my in my GitHub account. I've got one called radar WW2 and you can kind of see looking here. You can see that the last time I ran a build here was 13 hours ago. I had checked in code and it had triggered a CI bill to go validate that. You know, we'll drill into that in a few minutes here and see some of those details. I guess one other example I'll show you here is a different project that I've got that actually runs a matrix build on continuous integration. And you can see that there's a lot of flexibility in the types of tests and the types of CI activities that you can run in this particular example. My application, you can see that I was testing it simultaneously against multiple versions of Node.js in order to validate that they work. And you can see it ran each of those tests against that check-in when I made the code change and came back with the success for each of those. So let me go ahead and drill down a little bit and show you some of the other details about this build. So if I go in and take a look at this build that ran yesterday when I was in this code change, you can see that everything about the build is, of course, available to me here. In the screen I can see all the activities of it. I can also monitor as it happens or after the fact all the activities that occurred in the processing of that build. And you'll notice here just kind of a quick glance through here. You can see that this build does quite a few things. It not only builds the code and executes tests against it, you can see that it obviously is syncing with the latest code changes that I've made in my repository. It's doing a variety of activities that I've instructed to do prior to executing the tests.  And it is also going all the way through. You can see here some language that clearly indicates that I'm building images. I'm pushing those images out to Docker Hub in this case as well. One of the things that's really, I think, important to understand about the CI system from Shippable is that it is fully containerized, which is why it runs natively on an OpenShift. Every time you initiate a code change in your system in your repository, commit that change or anybody in your organization commits a change into that repository that's enabled for CI on the system, it's going to recognize that it's going to be notified from a web book from that repo. It's going to be notified of that change. It's going to immediately spin up a build container and then go about the business of preparing that build container to fully test that code change. And that's really what you see here is the end result of all those activities that are happening in the background. It can also go back in all this particular build. I don't have any tests set up for a bit of a different one, but I can look at the tests that are executed and I can see code coverage in there as well. And I can also see the entire actual execution script that's happening behind the scenes for my build container itself. So let's actually go back in and start the process of looking at a build from end to end. And we're going to make a code change. We're going to watch that code change kick itself off inside of the CI system. We're going to take a look at what's happening in that system as it occurs. And then we'll follow that as we actually promote that all the way through into deployed environments where in full topology environments where they can be tested as well. And so I'm going to jump back out now to my source code. So here's that application that we were just looking at, the radar WW2 application. And I'm going to go change, make a real simple change on the application. If we jump back here, you can see that when I'm in this application, the default, this is just a simple demo app that goes out to GitHub and it queries a repo. And it brings back a list, a summary list of the issues that are currently associated with that repository in GitHub. And so this application currently has the shipable slash support repo as the default repository that's going to pre populate in this field. But let's say I wanted to change that.  So there you can see that change I just made. I'm going to go ahead and say, commit that code into my GitHub repository. As soon as I sync those and push those out to my repo that is enabled for shipable. Actually, it beat me to it. It's already triggered the build over here on shipables dashboard. And you can see it's getting ready to start processing. And now it's processing. So now I've got a build running on the system based on the fact that I just submitted a change into my into my source code repository. And if I drill into that, you're going to see the you can watch those details that we just saw in that previous build as they occur inside inside the process. Now, one of the things that, you know, I'll point out while we're while this is running is is the various options that you do have here to set up inside your repository for your particular project. So for this radar WW2 project that I've got, you know, you can see I've chose for this to use. A Docker build process. And so it is using a Docker file from within the repository in order to build the image that it will use for the build process. I could have also chosen to not use a Docker build file, but instead to use instructions from my shipable YAML file in order to create that. And I could also have pulled a an image that perhaps a custom image that I've already prepared outside of the system. I could have pulled that in as well to use for the CI process. We also have options and functionality here for determining how you'd like to use Docker build in that CI process pre CI and post CI. And ultimately, the way to think about this is we have quite a few customers who tell us they want exactly what they test to be exactly what they promote through their various environments. And so the image that gets built and tested is the image that then gets moved throughout that workflow. We have other customers who have come to us and said that they want to be able to execute all of their tests, but before they then create an image to promote through the rest of their environments, they want to be able to extract out all the test artifacts out of the image and make that as lean of an image as possible before they start to promote it through the rest of the process. And that's really the difference between pre CI and post CI. The one thing I wanted to show as well, let me jump back out here to my OpenShift console and assuming that build hasn't completed yet, you can see that has spun up a project on OpenShift. And it's now running inside of an OpenShift container on the OpenShift platform itself. As you'd expect in any kind of CI system, these are transient workloads. And so it has created this project when the build got initiated and it will it will spin down and delete all of these artifacts once the build is complete. All the results of the build will of course be stored inside the shipable database. And so the history and the tracking and the traceability to be able to go back and review results and be able to trace any details related to this particular CI run are always going to be available to me. But the artifacts on OpenShift themselves are going to be transient workloads. They're going to spin up and spin down as needed. And of course, I've got the ability in this particular case, I just made a single change to a single repository and it's running a single build. Of course, this will run parallel builds as well and spin those up simultaneously to run at the same time.  You know, I've also chose besides using Docker build to create the image that I'm going to use for my my CI testing processes. I can also decide at the conclusion of that run to push that build. And so essentially create that image push it to an image registry. And in this case, I do have that option turned on for this. So at the conclusion of this CI run when it's done, we are going to see that a new image has been pushed to Docker hub in this case. Because that's that's the location that I've specified specified here to push this through. Now, of course, with OpenShift, I can push that to to my OpenShift private registry. I can also push the Docker hub. Essentially, you can push this to any image registry that you'd like to use. The last other option I've got here called Lighthouse is essentially an image watcher. It is it is essentially letting me sign up and be notified of changes to images that I care about. And those could be images that I create. In this case, I'm actually telling the system that the image that gets produced as a result of this. Tom, this is Diane. You've lost your screen sharing capability. So if you could try and share your screen again, we all want to watch that transient image on the console disappear. Yeah, let's see here. Okay. Blue Jean seems to be having. There we go. Loading the presentation. Coming back. Coming back. Now let's just go to the click the on the screen itself on the shipable. There you go. Perfect. Good. Okay, thanks. I think we still had audio there. So I won't repeat any of the things I just said, but I'll just keep going from that last point. And so the lighthouse allows me to essentially watch images that I care about in the registry. So in this case, I'm saying that, Hey, after you push this image to the registry, you know, I want to be, I want to be notified. Anybody related to this project within my CI system, I want them to be notified of the fact that an image is changed in that repo. And so in this particular case, this happens to be for the images that we create out of this process, but it could be for any images in any registry. Public images, private images, et cetera.  In this case, I've got this setup for default tagging, which means it's going to tag that image with information related to the CI process that that's running. In this case, it'll tag it with the branch and the build number that has been executed. And you can see here as well as part of my CI process, I've specified my base image that I want to start from in this case, which is in this case, we're going to 1404 Node.js images where it starts. These other details down here, I think, you know, we'll skip over for now, but ultimately just let you set up other external integrations so that your process can obviously interact with some of the other external processes like Docker Hub. So if we head back over here into the status system, we're going to see, well, first of all, that build has already completed. We can go take a look at the details of this one. We can see it took five minutes to run the full end-to-end process. We head back over here to OpenShift and refresh this page. Like I mentioned before, that build process has now disappeared from the OpenShift system. And if I go drill into that particular run, again, just like we saw before, you know, I've got my full history here and I can obviously expand out and see any of the details necessary about what was happening in that process. And obviously that becomes, you know, much more important as you get, if you run into any problems in your build and if there's a failed build in any way, you'll see exactly why that failed. I think I believe, for example, I should have some failed builds out here as well. And we can go dive into one of those and essentially troubleshooting where the issues happen become fairly easy because I can see exactly where in the process this build failed. And here I can see I had an error when it came time to push into my registry. And so then I can start my troubleshooting there. In this particular case, it was exactly the information I needed to go figure out why this wasn't working and then be able to make the necessary corrections. And now you can see it's since corrected, it's now been running successful builds ever since. Oops, maybe we lost the screen share again, it looks like. There's one question here, Tom, while you're pausing. Okay, great. Sorry. Well, if it's okay, I'll finish going through the demonstration, then we'll come back and get all the questions that have been happening as well. If that's okay. That's fine. Okay, good. So, so a bunch of things have just happened there in that workflow that we talked about before you saw me make a source code change push it to my repository. It, it has automatically triggered a build on the system. It has run through all the necessary CI activities that I've specified that I wanted to occur, and it's completed. And it's told me that it's been a successful completion. Now, the next steps in the process are, you know, obviously that I now want to see I want to go to that second half of the workflow where I can, I can now do. I can now deploy that image off to different environments in order to work with it. So if I jump over here, I can see I've got a formation here set up. I've got multiple formations, all the ones that I have access to are here. A formation is essentially a multi container environment where I can deploy any number of services or pods out and network them together in order to leverage them as full applications and essentially full topology applications in a multi container environment.  And so for this particular formation team, I've got 10 containers available to that team. And within it, you can see some of the key concepts that come to play once you start to deploy your applications and these images out into full topology environments. In this case, I can quickly scan and see what the status is of my various services that are running in my applications. I've got multiple environments set up here. So I've got an environment called all in one, which if I expand this out, you can see is actually running two containers, both in the same service. In this case, you can see this app, that demo application I showed you earlier. Earlier is a two tier application. It has a web front end, which is the repository that we've been working with. And it has a API service on the back end that essentially manages all the page feeds and the data. And in this particular case, I've deployed those as a single environment running inside of a single service. And of course, over on OpenShift, I would see that as a single service with a single pod with two containers running inside of it. This one over here talks about how many instances of that service I have got running and of those pods I've got running. In this case, I've got one of those running for this particular service. This other example of an environment that I've set up here is my Dev environment. In this case, I've deployed each of the components of the application as separate services. If I expand those out, you can see that they both contain just a single image. My web service contains my radar WW2 image. In fact, we can already see here master.55 has been deployed here, which if you remember back to our demonstration example back over here, 55 was the last build that we ran that we triggered with that source code change. And so in fact, you've already jumped back and seen the end and flow occur in two different ways. For the all-in-one environment here, it's still running master.53. I don't have auto deploy set up on this particular environment, but on my Dev environment, I've got auto deploy enabled and in fact has already deployed the image that was created out of that CI run for master.55. We've actually now got a working updated piece of code running in my environment. In fact, let's go ahead and take the moment right now to jump back out there to that application. Let's refresh this. And we should see, there it is. We now have our new code running in that environment. This happens to be that Dev environment that I'm pointing to. You can see I'm using environment variables here that are configurable to be able to change the behavior of my applications. And that change is already deployed and available to me in that environment. So let's take a quick look at some of these other examples here. In this particular example called Dev Single Component, this is a third environment that I've established in this particular environment. I've only deployed a single service, but in fact, it's still a complete working application because in reality, if you take a look here, my back end that I'm leveraging for this particular environment is actually pointing to the back end of my test environment. So I've got an API down here, service running in my test environment, running on port 31767. You can see that this web front end is actually using that environment. Internally here at Chippable, we use this concept very frequently. Our developers, who are making changes to a component on the system, will deploy into a single service environment that points to all of our official beta integration test components running for all the other ones that it depends on where they can do full integration testing and functional testing on the entire app before they actually promote it into that test environment for other teams to then leverage it as the latest and greatest component version for them to test with. And then lastly, you can see here, I've got my test environment.  And I've also, I'm running multiple instances of my web front end here. I've got three web front end instances running on the front. And so here you can see the fact that the prime difference being that I know I've got some different settings set up for this environment. I'm running error logging here instead of debug logging that I was running on the dev environment. And I've got different versions of my components running back there as well. The thing that I want to jump out to right now as well is just kind of show you very quickly how quickly I could decide to use auto deployment or in fact do deployments on my own at whenever I want. And so in this case, let me jump into my all-in-one environment. We can see before that, you know, we looked before it was running, you know, 29 of my API2 and it was running build 53 of my master. We know that we've now seen build 54 and 55 come out. You can also, I can see all my deployment history. I can decide I can roll back, for instance, easily to a previous environment. So if I want to go back to when I was on 35 and 29, I can just go ahead and roll back with a single click. Alternatively, I can choose to redeploy and deploy a new version of this. I can, for instance, come up here and say that I want to go and deploy on the web front end. I want to now go up to that newest one that came out, master 55. And I'm going to go do the latest API version that has come out as well. And go ahead and deploy that out into the environment. And so because, of course, this is a container-based environment, you're going to see those activities change very quickly. And in fact, that container has already been the old containers and the old services have been stopped. They've been replaced. If we dive out back out to my OpenShift console and go into that project where I'm running all my services related to this particular formation, we can see all of those various endpoints running here that I had going. And in fact, the latest one that we just changed and deployed is this one here that was created a few seconds ago. You can see it's the one that's running two different images within the same service. And it's already refreshed and running out there. And in fact, that's this one over here. And I can now refresh that one and see that I'm actually accessing the latest and greatest code for that one as well. So I want to go ahead here and take a quick break. It looks like there's been a lot of good questions coming in on the chat line. So I want to go ahead and open this up for Q&A here for the last 15 minutes and make sure that we can get to everybody's questions. And I'm going to unmute, or Avi, Avi should unmute himself as well. If he could. And then, Lee Calcott has asked a couple of questions and Avi has answered them in the chat. But I think they're worth asking out loud so that they get recorded and other people might see them if they're not watching the chat. Let me slide back up to his first one. For those organizations working with on-premise deployments of GitHub Enterprise, Docker Hub Enterprise, or an OpenShift Enterprise, this ship will integrate with non-public cloud hosted instances. Yeah, I mean this, Avi. So yeah, I mean we currently whatever we are showing demo is an actually running service. So it's externally connecting to all the cloud services. If you want to run this on-premises completely, we support anything that runs on-premises. The limitation right now is it has to be Git-based. We are working on other types of source control, but predominantly what we see with our customers is they want to Git-based for us. So that's what we support. We can support any kinds of registries as long as you have creds to connect to it and you have a URL that you can actually access through whatever service that OpenShift is running on. We should be able to connect to that registry and manage pretty much on-premises. And then the other half of the week, you answered my question, which was about private registries and I was pretty sure you had that handled because it was in the slide previously. Let's see the other part of the week. I think the other question was if folks are using external integrations to do things like Selenium Grid or external pieces where it's doing scale-out testing, I think Lee was asking whether we support webhooks from our external pieces. So any of the actions we are completely event-based internally, our system works completely on webhooks internally too. So we can expose those webhooks externally also and so we can hand the control out to any external service, push the webhook out and then wait for a webhook back from that system to continue the process. It's a very flexible system and just the same way GitHub gives us a webhook and we push information back to GitHub in terms of your build status and all of that stuff. We are natively supporting external webhooks also. A lot of folks use this to deploy to external things like digital ocean or they probably have Ansible workflows that sit on some of the server or maybe Kepibra or something like that and we call into it and then it returns back of webhook. So that's possible too. I'm looking to see if there's any other questions. I think that was the other one was about rollbacks, but that was a psychic question because it was just as Tom was about to show how to do rollback. So that was great. So the one other thing I would ask you to talk about a little bit is if people wanted to get started using Shippable on OS3, where should they go to get started? What's the best jumping off? So I think right now Tom, sorry. So today we'll, in fact, this afternoon we'll be exposing the web page that announces the functionality for OpenShift and exposes the beta program for it and the contact information for how to get a hold of us and either schedule follow-up demonstrations with your team or just start talking about how to come on site and be part of our beta program. We'll all be on that page. All right. So you go to www.shippable.com and you'll find that information on our products page. All right. I will make sure that that goes out to the commons mailing list as well along with a link to the video. So, yes, Lee, I agree. This is pretty beautiful. Are there any specific integrations with OS3 constructs to be highlighted? CD by district? If you're using OpenShift online or upset it up with districts? So I'm not sure what district means. I'm assuming it's some kind of zoning for your application hosts, I think. Anything that OpenShift exposes through APIs, we can expose all of that stuff. So as Tom was demonstrating that there is forward sync and reverse sync back from the OpenShift. So all the projects, any changes you make on the OpenShift UI will get reflected on Shippable. Shippable, you make changes to where it will get reflected on the OpenShift. So if you have districts which are basically labels, you are absolutely, all of those are definitely possible. All right. Then I'm looking to see if there are other questions. If not, that's about a great length for someone to have to watch this video in the future. And I'm sure we'll do another one once the beta is done and get some more feedback from folks. If people have feedback for Tom and Avi and the Shippable folks, please do hit them up. If you want to throw a slide up here now with your contact information or maybe even your email or whatever. I think you had one there. There's Avi at Shippable. You guys have the easiest email addresses. Avi at Shippable and Tom at Shippable. Yep. Pretty quick and dirty to get there. So very impressive. I really, really love to see stuff that I don't have to do any scripting for. Though I can imagine a few people are going, I love my scripts. So we'll see how we can work with them as well. And I think that was a great presentation. So thank you very much both of you guys for coming on board and being part of the Commons. Thank you, Diane. Thank you very much, Diane. Thank you, everybody. Take care.


We're here at the Lenara Connect here in San Francisco, and who are you? Hi, I'm Peng Cheng from Thundersoft. I'm the CEO of Thundersoft. So Thundersoft, right here, you are a solutions company, software company, what is Thundersoft? Okay, so we founded about nine years ago by a bunch of companies, Hikers. So our business started from day one. We're focusing in this so-called smart device, printing system, and also platform, like Kuginix or Android-based or RTOS-based. So you work on all these Linux platforms? Yes. So founded by a bunch of Linux hackers in China? Yes, we also have presence in Korea, Japan, US here, and also Europe as well. And you're one of the founders? Yeah, I'm in charge of the technical division of Thundersoft. So also strategy, what to do in the future? Yeah, especially what are we going to do in the future? And so there's all these development boards right here you talk about, for example. And so how many people in Thundersoft? Currently we have three thousand people, mostly engineers, like I myself, and we went public two years ago in Shenzhen store market. So we're a public company right now. So mostly engineers, that's got to be a very interesting office, right? Yeah, yeah. And how do you organize, how do you figure out who does what? There's so many projects, right? Oh yeah, yeah, yeah. So we have different approach. It's kind of a mixed the procedure model and also all these bizarre model. And internally we have four business unit, we have this mobile business unit, we have the IoT business unit, we have automotive, BU, and as well as the AI-BU. So four groups working on different project, but they have something in common, is what we call this a smart system, smart device. They share the similar operating system, the similar media, multimedia code, multimedia code or media wire. And right here are some of the platforms you are on. You are on CoolCom, Texas Instruments, a lot of ARM solutions. Oh yeah, yeah, yeah. I try, yeah. Mostly is ARM, right? And also Intel, I have to say. But because we started with mobile, so that's why we're doing a lot of ARM based devices. In terms of quantity of platforms is ARM because there's so many. It is. And so, what do you think about the ARM ecosystem in Linaro? How long have you been part of the Linaro? Yeah, we have been in Linaro long ago, actually from the very beginning. Actually when Linaro founded, we have signed some engineers, we are one of the early participants from Linaro. And now we are part of the student committee of 96 boards. And mostly IOT based activities in Linaro right now. So there's some, right here you're showing some development boards. What are these, for example? What is this one? Okay, so this is the board we did for drone. So if you go to the Apple store, you can buy some products. For example, a product called zero, zero drone, you can buy this in Apple store. And this is what Qualcomm is on here? This is a Qualcomm Snapdragon 800 board. This board only weight about 16 grams, very lightweight. You can see it's very small, just the size of my finger. And so with everything included, including the camera, wifi, everything. So you can basically put some of a projector and you are ready to fly. So very lightweight, powerful. Does your company do PCB designs too? Or you work with companies to do that? Yeah, although we call us Thundersoft, so software is our major business. But we do provide this kind of module or system module for our customers, ODM, ODM brand owner, so that they can build the devices, mostly IoT devices, much easier and quicker into market. Like drone, this one is for drone. And this one is for VR, AR, type of application. That's A20, A20 based. And... So that goes in VR? That's VR and AR. So we're... And hand mounted this solution? Yes, yes, yes. I try my D, I try my D type of device. So that's another example. So customer can hook up their lens camera and very easily to put into market their VR devices. This one, another example is the camera is a Qualcomm A053 based IP camera or smart camera. You can also run a lot of fun stuff, like deep learning stuff on top of this little board. And that's the... Which chipset is that? This A053 chipset of Qualcomm. All right. Yeah. And so you have, for example, a session about automotive solution. What do you do with automotive? Yeah, so we started this automotive business three years ago and that's why we have this automotive BU. And I will have an overview. Okay, so that's a good slide. And this is what we do. So generally speaking, we provide this... The code is a smart cockpit, total solution to either tier one or car makers. So that smart cockpit will contain several things. Mic, some infrared us. So we did that for Baidu. Later, I can introduce more about the works we did for Baidu self-driving car. That also includes the interface 3D engine. We provide the 3D engine and the 3D tools so that you can have a very fancy look. Interface in your car for both cluster and the infotainment. So we provide infotainment as well. And together with the digital cluster, you are more consistent and professional look for the... Isn't it related with the 3D UIN? Yeah, yeah, yeah. You can see this one is a digital cluster, digital cluster meter. And traditionally, you only use a mechanical, it's more like a feature form or feature car. Now, if you go to the smart car, you can do a lot of cool things and interesting and informative things, smart things on your cluster. So this is an example, we have the 3D meter and also I can project some multimedia or human maps on top of your cluster display. You work with the self-driving cars in Baidu solution. What is this self-driving car solution? I will show some video, maybe that's a good example. So this is, Baidu announced a self-driving car in their Baidu World Conference. So this is ARHUD or ARHMI project we did together with Baidu and Bosch. So it's in Chinese, but you can see what it's doing. Is it just cameras or is it using special sensors? Yeah, you can see here, we have this AR projector and information like this line and all this signal for the traffic. And that's what we did. We provide this solution like this tablet, still later we will have an HOD and project all this visual assistance to the driver. It's just based on the camera? Based on the camera only. No need extra sensors, no need at all? No need at all, you can see this is just a tablet. And it's driving by itself? Yeah, with one camera. With one camera, with the off-shelf camera. But need a good camera? Of course, yeah. Good camera and what's the chip set or is it a secret? How do you... The chip set is up to the Baidu to start. Can you run it on the call come like this or you need more? Yeah, certainly. Currently actually it's running on some immediate platform and depending on the customer choice, you can run this of course on call come or other chip sets. So how soon is for example China gonna regulate that every car need to be self-driving car? You know, maybe it can go very quickly, right? I'm from the technical side, so... It's not part of the technical side. I can see China is moving much faster, I put this way. So, you know, people have some concern about the regulation, about safety, but the people also want to get all these benefits and also those innovations. So China, in some sense, a little bit more aggressive. Not from the business sector like Baidu. You can see what Baidu are doing. Actually they're driving this in Beijing, right there. And you can see... And it's fine. Not totally fine, but technically it's fine. Our government also behind that, I have to say. So they're putting more resource, capital, and of course they build all this driving environment. You have to type this, right? So the government also invest a lot so that the business sector can test their self-driving car. I think, of course, it would be great to have zero accidents, but I think the most important is to have less accidents than people driving. And it feels like here in the USA, for example, it's like, no, we don't agree with less. We just want zero. So that means it will never happen. It will never happen. So it just needs to be better, and that's the common sense. Your solution is already better than a human, maybe. Yeah, yeah. The government has to play a very crucial role here. Government, actually, our government is fully behind this, although I'm not from the government sector, but you can see the result. And also, China, we also want to solve the problem of the environment. We have some pollution there, so that would be a key to resolve that. So our government is fully behind this. So there's a lot of future in the automotive. What other sectors are you talking about? If we can go back, can you slide a little bit, maybe? And so this is from technical side. Actually, in order to reach this smart car, this is the architecture we build. So you need to have a good hardware for the smart car. Review smart car is more like a smartphone. It's just a smartphone with four wheels, with actual safety and actual power. And you need hardware. You can see most of those hardware come from the mobile business, mobile sector, like a Qualcomm, like Renaissance, like TI. And then you need a good hypervisor to provide all this security and regulation certification. And also reliability? Of course, very important. That's enabled with hypervisor? Yes. The hypervisor, we provide that as well, together with our partner. And like, for example, the 2X or Green Hill. And on top of that, we run Linux, our Android, or any Autos on top of that. So that, and also, of course, also middleware, especially like the multimedia, like the Kanzi is the one we, actually that's a company we're acquired early this year, it's called RedWire in Finland. So they provide a pretty cool UI engine and the tools for those smart cars. And also the AI engine. So built on top of those middleware, you can have all this infotainment, or cluster, or actually these things. So do you think you can have all the NANARO talking about maybe helping in this, working in this automotive space, right? Is it important to have an open source ecosystem doing a lot of things in here, right? Yeah, it's very important. Actually, yesterday we have the talk and also the presentation and also the discussion. Especially in areas like the hypervisor or Autos or even the Linux, like NANARO is also organizing this special inches group for automotive. We're part of that. And we hope to get more deeply involved as well. And for open source to jump into this new sector, especially self-driving car or this smart car, it's very crucial to have all this innovations and all this problem to be solved in a community type of fashion. What do you think about Android car? Android auto? Android auto. Is this something you can work with? Or is this something Google want to do everything for everybody? How do you optimize Android and customize? Okay, actually, for example, like Android auto car and we are fully involved for some customers, tier one customers. And I think it's similar to the smartphone. So for smartphone, of course, it's dominated by iOS or Android but people are also doing, actually, we're also doing a Linux-based smartphone. Even for that particular domain requires a much stronger ecosystem. For smart car, actually, we do both Android and Linux. For Android, we enhance this Android auto car as what we did for the smartphone years ago. We think that the history has been repeated. Actually, like six, seven years ago, you have this Android for oil or this early. What did you do with this? For smartphone or? For the smartphone. Oh, for smartphone a lot. Okay, if you remember, actually, not long ago, like five, four, maybe six years ago, and even you do not have a full Chinese support there. Arabic is not support there. And the characteristic certification is not there. And the multi-window is not there. And the fast-boot is not there. A lot of things not there yet, but the market cannot wait. And so we did a lot of enhancement works and for this kernel-side, mid-wire for Android. Now, Android is getting more and more mature than before. But for car, it's the same story. It's just the early stage. You need a lot of security patches. You need the UI like what it did. You need the certification. And also, you need this much more mature multimedia, quite different from what you got for your smartphone. So a lot of things need to be done. And different customization requirements cannot be only solely provided by Google. So we did a similar thing years ago for smartphone. We're doing this right now for automotive. And you mentioned multi-window. One thing I'm very excited, I mean, I want to see more of is Android for productivity. I'm hoping someday that it will be useful in a laptop. You know, like, have you done stuff with that? Yeah, actually, this is what I can show you, something like connected. So this is something we did multi-window for smartphone. And for car, it's even more important because in your car, you have many display. You have cluster, you have IVI, you have backseat display. Do you want to do things like running different operating system, different UI, and cannot talk to each other? That's not the way you want to go, not the way our customer want to go. So that's why we provide this so-called contact. Which means as a developer, you only develop once, for example, a media player. But you can easily configure this to control either through your backseat or through your cluster, control something that you are running on your IVI. And without having to program differently for those different platforms. So that's what we provide this so-called Kanzi Connect. So that for all these display, you'll have one media wire, one education, and one consistent look and feel to the end user to the customer. And actually, Audi did one demo with Google running this Kanzi Connect technology, which we provide. They think that as a future, you're going to see more and more of this kind of a consistent, connected display in your smart car. So over the last nine years, how many products were shipped with ThunderSoft technology inside? Is it like millions and hundreds of millions? Or what is it? In terms of volume, we provide those solutions and also services. So the total volume is approximately more than millions because we did a lot of smartphone reference design support. I will use an example here to show some products we built. It's a good example, actually. For example, this QRD is the first Qualcomm reference design we did in 2010. You can see that's how Google Android looks at that stage. What is QRD? It's Qualcomm reference design. So you worked on that? Yeah, we provide the software. You were one of the first to provide the Android? Yes. Android for smartphone kind of solutions? Yeah, yeah, yeah. Actually, before this one, actually, we started from Intel, I have to say. We started from Intel MID. And that's when we built on the Linux. It's called Midinix. Actually, that's the root of Amigo or now called Tizen. So that's how they started from the Nokia MIMO project. There was also based a little bit on the TI OMAP that kind of started Amigo. Yeah, yeah, yeah. Before it started with the TI for Nokia. And before that, we ported that on Intel iPhone. But then when the smartphone kickoff like the 2007 iPhone comes to life, and the Qualcomm switched here from Linux to Android, we do the same thing. So we do more and more Android. Now IoT and automotive. What is this camera turnkey? Camera turnkey is like this. So the camera, similar to the smartphone, is getting much, much more smarter than before.  You put there and you're streaming to the cloud. Hopefully, you do not watch this. You only watch this when you see some instance. If something got stolen, you go with that. But that's not the thing people are looking for. At this stage, people are looking more and more intelligence, like the AI things. So you already do smart IP camera in 2012? Yeah, yeah, yeah, yeah, yeah. So the smart decisions of what to send to the cloud? Yeah, like this one. So this one, actually, you can order from our website. It's based on this module. Actually, that one running exactly on this module is 053, this module. You can run the AI applications. You can stream out all these 4G, 4K content. And it's very powerful. And that's designed for the smart camera. But this is recent, no? This is a recent. Recent version. Yeah, yeah, yeah. Recent device. Yes. And you're also in the robots and smartwatch and? Yeah. And VR, AR, and the drone, like this one, yes. So you're all over the place? Yeah, because operating system is everywhere. So we're going with them. And if we go back here, there's something about the IoT turnkey with the narrow. Yes, yes. So that's one of the big fields right now with the narrow is the light group. Yes. Doing something in there. Are you a part of that? We're part of this 96 boards. We're a steering committee member of 96 boards. So we're heavily involved with their activities. Yeah, yeah. All right. And then in the future, there's so many more opportunities in this world for using technology in a very smart way to do more. Then suddenly maybe what is the next iPhone? What is going to be the next killer app? You might be part of this. You're probably already working on it. So next one will be something like this. Of course, everyone is talking about this, not that guy. This guy. AI. So you can see everyone, I will talk about AI. But we're the one that actually really doing it. This is a demo we did earlier this year for Qualcomm. It's running on their 835 platform with our algorithm and using their Snipey neural processing engine to show the good performance. So does the 835 have an SOC, an AI silicon? Or is it just using? It's running on their high silicon. Hexgon, DSP, and also their GPU and CPU. All right. But now the trend is that more and more SOCs will maybe come out with AI on the silicon. That will bring much more work for you. Yeah, that's what we like. For example, for Hexagon, if you watched the news, actually last week, they have an announcement. And also previously, Huawei Mobile also has an announcement in German for IFA meeting. So if you watch the news, you can see we also have the joint announcement and the joint demo with Hexagon to show this full detection and also the face detection using their Hexagon AI core. So I would like to see a detection of everything inside indoors, detecting everything. That's going to be very exciting. That's going to change the world, right? Yeah, it's getting there. And especially, it's very important to detect all these things on the edge, on this module, not to send everything to the cloud. It takes too much time, sacrifice too much privacy or security issue. So that's getting there. And we provide those AI algorithms. And most importantly, this AI enabling layer. So we bury the gap between the silicon people and the algorithm people. Those people sometimes hard to talk to each other in this big different language. So we are sitting in the middle as an operating system guy. We know both. And we bury the gap between those two type of one. Are you kind of making the operating system for AI? Yeah, it's kind of AI OS that I put this way, more like a marketing term. But also technically, we think it's right because you need this new AI OS to schedule the resource, like a DSP, GPU, CPU, or even AI core more intact in a way, more efficient way. So you need a scheduler. And you also need a monitor to monitor the performance and the thermal. And you also need even the IP address store, right? There's no way to provide you, to provide the algorithm store like what Apple did for their education. So that's actually operating system. That's what we're doing right now. And everything you've been doing for the last nine years, everything is open source? No. No? Well, you know, we started from the open source community.  We have this passion for open source, for freedom. But frankly speaking, after this nine years of this startup, we're still a startup. And most of people go to their forties. We reached this stage of combine this idealism with all this, I don't know how to call this. Capitalism. Ferguson. I think that there's some space spot we can do the job. If you go to further left or further right, not good. We have to find something in the middle. In Chinese, we have something called the Zhongyong. I talk about philosophy, but... Zhongyong. Zhongyong means not open source. Zhongyong confuses?  Or... Confuses? Yeah, yeah, the philosophy. Most of the Chinese people agree on, including I myself. So that means you have to find the internal peace. You cannot go extreme to either side. I know people are enthusiastic about open source, so open everything. It's not good to open everything, I have to say. Although I'm in the open source community. Some, but it's also not good to close everything. Like, you know, Apple way or whatever. So there's something in the middle. So something they open, like for example, for automotive, we need open source hypervisor and autos for those low layer and so that people do not duplicate the effort. There's absolutely no reason to spend so much money, so much effort to some similar, requires so much security. We just need one or two very good operating systems like Enix in automotive. But we also need some algorithm and applications in the middleware and so that we grow the ecosystem. Those things does not have to be open source. It's perfectly fine for people to close their algorithm, fire the IP, the patent to get money. That's how American got bigger and how we think the product like this can get more attention and more market as well. Okay, so that's.


What's good Josh bull rocks back at again with another video. So just finished up our Monday night raw live stream reaction Shout out to everyone. That was a part of the live stream. You always make the shows that much better Nothing really of notice Happen, you know, not many things were progressed that we didn't already know once again the WWE draft starts on this week's edition of Friday Night Smackdown So I think that's one things are gonna really shake up and that's what a lot of people are looking forward to But the one thing that was very noticeable was Triple H's announcement Now there had been reports that Triple H had already designed a new championship a new world championship But we didn't know when it was gonna be unveiled and pretty much Triple H announcement was the unveiling of the new world heavyweight Championship he pretty much went into his field about how Roman has been a champ for over a thousand days And he has set up his contract where he doesn't have to work as many dates, but at the same time the show must go on and There needs to be an active champion on the show So he pretty much announced wherever Roman gets drafted to on the draft this week What not he will be only exclusively seen on that brand and that will be it Which means both the titles will be going to that one particular brand the WWE Universal World Heavyweight Championship will be going to that particular brand and that's it since that's the case now there needs to be some other championship in place for the other brand and Obviously, most likely Roman is going to be going to SmackDown because Fox wants Roman on SmackDown So most likely he's gonna be going to SmackDown and since this draft starts on SmackDown They're probably not the first pick it would make sense He's gonna be on SmackDown for the foreseeable future, which means raw needs a champion raw needs a championship and he unveiled the new WWE World Heavyweight Championship and Bruh It it looks Fantastic, it looks great It looked beautiful the crowd out there loved it They loved it You guys remember when the Universal Championship was first unveiled and how people were booing it, right? They looked at it. I was like, oh, what is that like people started booing it wasn't it wasn't like This reaction where everyone was like cheering and praising it was like what the hell is that what is that raspberry jam belt? well This was the complete opposite reaction. I I legitimately was thoroughly impressed by the design It reminds me of a little bit of the NXT World Heavyweight Championship their main title I love the NXT. I mean NXT UK World Heavyweight Championship I've always loved the design of the NXT UK Championship the men's championship it reminds me of that with the designs and how it's set up But at the same time it also reminds me of big Goldie man It's like a modern style of big Goldie, but it still has like The modern-day feel of how WWE does their belts with the big WWE logo, but this one is not prominent It's like it's in the middle is in the center, but it has a globe around it Looks so good. It's a combination in my opinion of the NXT men's UK championship They're there. Yeah, the NXT UK men's championship big Goldie and the modern style of how WWE does their belts like with the the big W and then the side plates it looked it has that regal Regal presence and looks like a a great championship. I am so Excited about how it looks and the memes are of Roman at home sitting there looking at it Like what the hell why ain't get that my ah, bro. It's in my opinion Right now. It's the best championship belt. They got on the roster. It looks great I wish they were remodeled the women's championship belts, too I think they need a fresh new paint a coat a fresh new paint as well Like dog that it looks like it's something worth fighting for not to say that the the blueberry belt in the WWE Championship ain't worth fighting for it's just those belts. I mean to be honest with you They weren't the best looking only because they just have a big-ass W on it. You know I'm saying they weren't the best looking I like belts that have designs on the main plates and the side plates and it just looks so Good, bro. They triple H did a real good job on making sure that's how the design would be looks fan Tastic, oh, bro. It looks fantastic And and I like that they kept it out there on the show and anyone that had a segment or promo They were all talking about maybe being the new world every champion. So Here becomes the interesting thing and We were having this discussion Who becomes the new champ? Who becomes the the new champ from Monday Night Rock? Who becomes the new world heavyweight champion? now the thing is and Me personally, I'm still on the bandwagon of Cody getting a job done because it would suck If we got all this build he loses He's trying to get to the point where he can get that rematch again Only for him to just go for the new championship Which is cool, but I don't think that's the route they should go. I think whatever brand Roman Reigns ends up on I think Cody should be there. I think Cody should be there So if he ends up on SmackDown, you put Cody on SmackDown now granted He's still gonna be facing Brock Lesnar. So I don't know how they're gonna do that I think that's probably still set in stone and then afterwards everything will transfer over Honestly think they probably should have did the draft After the pay-per-view event, but that's neither here nor there But if he's on SmackDown, which I do think Roman will be on SmackDown because they want him there I think Cody should be there too because the story still needs to end Because if that's the case then his story never in well his story would have ended at WrestleMania That's it So I think his story needs to end Sometime at SummerSlam and he Dethroning Roman after everything, you know happens with him in the bloodline So I do think they need to keep that going and I want someone new and fresh to win the championship When it's on Rock, which means maybe we do get well I do think that with LA Knight He still should win the money in the bank and let him kind of decide how that plays out But I do think someone new and fresh should be the guy to win the championship I know a lot of people were saying maybe Seth should be it I was like nah Seth can have his moment at some point But I still think it needs to be someone new and fresh if you're trying to build up somebody This is the perfect opportunity. You have a chance to create a new star here So it's gonna be interesting to see what they do. I know a lot of people are saying Montez a lot of people saying LA LA Knight I'm trying to see I know people still want Seth to be a champ It just really depends on how they booked this now I know the new champions supposed to be crowned at Knight of Champions. So in Saudi Arabia So that gives you an extra reason to watch that pay-per-view, which is awesome or the PLE So the question is how they're gonna set it up I'm sure they're gonna set up everything after the draft on Friday and Monday So I'm guessing they'll probably have a tournament leading up to that They'll probably start doing that after backlash It only makes sense to do it after backlash then they have a tournament and then figure out You know the finalists for the tournament and we go from there Which will give the shows a little bit that much extra Oomph to watch because this is gonna be the head champion for that respective brand Which I think is gonna be Monday Night Raw and the only reason why I believe it's gonna this title is gonna be on Monday Night Raw mainly because one it was debuted on Raw and two I know USA Networks been kind of Upset that they haven't had a top champion on their brand because Roman floats between shows, but he's not really there He's he's really relegated. He's really only supposed, you know relegated to Smackdown But since he has both titles for the longest he would go between both shows here and there You didn't really see Roman on Raw like that You know I'm saying so they were kind of upset with that Those were the reports in the rumors for a while now that they got this situated now that raw will probably have a New head champion and it looks beautiful. I am all for it. I am looking forward to they have now Excited me to see a Saudi show because now I want to see who's gonna become the new champion a new world heavyweight champion Man, so this is probably the most exciting news We've gotten so far and it's gonna probably get a little bit more exciting leading up to the draft this week So the question I have for y'all who first and foremost do you like the the championship design? Cuz I think it's beautiful. It looks great. So that's first second. Who do y'all think should win it?  I'm gonna go for these titles and stay on Monday night Raw Do you think he should finish the story follow Roman wherever he goes and try to finish the story? Let me know how y'all feel about that and also who do y'all think should win it man Who do y'all think should be the first? New iteration. This is like a the world heavyweight championship 2.0 with a different style to it Who do y'all think should be the person to win that and be the head guy on Monday night Raw? Let me know down below man But I appreciate all the love and support you guys have shown on the channel road to a hundred fifty can I'm still young to be the YouTube rest on chapter world. Appreciate y'all getting with me. See y'all next one. Peace