Okay, very quickly. How many of you came to JRuby from Ruby? How many of you came to JRuby from Java? Okay, so those of you that came to JRuby from Ruby may be familiar with Twelfth Factory. You may have heard of it before. But today I'm going to talk specifically how it relates to JRuby. My name is Joe Cutner. I also go by CodeFinger. And I'm the JVM platform owner at Peroku. This is actually I'm very proud to say my fourth year speaking at JRubyConf. One more and I get JRuby Diamond Medallion status and first class upgrades. But every year I'm here, I basically speak about the same thing. Deployment, deployment, deployment, deployment, deployment, deployment. It's kind of become my thing. I just, I love deployment. What can I say? I love it so much. I love it so much that I wrote a book about deploying JRuby applications. But don't buy this book. Actually, I don't think you can. I thought of print because it is wrong now. There are lies in this book. But to be fair, I wrote the book or I started writing it more than four years ago, about four years ago. And since that time JRuby has changed a little bit but really the ecosystem around JRuby, the tooling, virtualization, the cloud, they've changed as well. And they've led to different ways of deploying applications. So what I write about in the book primarily is this. The traditional model for JVM deployment. You take your code, you package it up into a war file and then you drop that war file into a running Tomcat or JBoss container. And this model deployment was great 15 years ago when we didn't have the cloud, when we didn't have virtualization. When we were deploying our apps onto a piece of metal, we needed that abstraction layer between the app and the underlying platform. But today, modern JVM deployment looks more like this.  Whether it's the cloud, a Docker container, a Heroku, it doesn't matter. The only coupling between your application and the underlying platform is the existence of a JVM. It's a truly portable application that you can move around. I guess what I'm saying is make jar, not war. That's also... That's right, that's right. I've got more. War is hell. War files, what are they good for? Absolutely nothing. But you don't have to deploy your, you can deploy your application as a jar file. If you saw Gradle this morning, you can do that with Warbler. Actually, you're probably wondering, I maintain Warbler, and I'm saying this. But to be fair, a lot of the work that I've done with Warbler, especially recently, is making Warbler capable of running as an executable war file. It's actually more like a jar in that case. What does this mean to JVM? Even if you're not deploying as a jar file, this still has implications. That's what I'm going to talk about today. Also, the shift from war files to jar files is not the only change that's happened in the last 5 or 10 years. We've also moved from an emphasis on application servers, these big, heavy containers that did a lot of work for us. We've moved from that towards microservices. We've moved from a hot deployment which was the goal for a long time, to be able to deploy your application into one of these containers without ever restarting the virtual machine. But due to memory leaks and system crashes and system upgrades, that just never really came to fruition. So instead, today we focus on continuous deployment, the expectation that your application will be deployed multiple times a day maybe, and that you will restart your application, and you should be able to turn that around very quickly. And then, of course, 10 years ago, I was deploying my applications to a box in a closet down the hallway, but today I think most of us are deploying to the cloud, to Amazon, to Heroku hopefully. I know some of you are. So at Heroku, we host a lot of Ruby applications, like millions. I don't know if we're supposed to say exactly. So we see a lot of applications, and we see a lot of problems. We see a lot of solutions to those problems. We see a lot of things that work. And from these experiences, we've derived a set of principles that we believe leads to better deployments, better applications. And we've compiled that into a thing called the 12-factor app. The 12-factor app is a methodology. It's a set of principles, a set of best practices that we have found lead to better scalability, better maintainability, and better portability. So this is truly a portable methodology. It's not specific to Heroku, even though it's derived from what we've learned on our platform, it applies to any kind of deployment. So the 12-factor app achieves these things through immutability, immutable infrastructures, ephemerality, the idea that your application is not persistent, that it will be restarted and disposed of at some time, declarative setups, declarative configurations, and automating as much as possible. So these are the things I'm going to talk about today. How do you do this with JRuby to make a 12-factor app? So without further ado, here are the 12 factors. Memorize them. There will be a final exam. You will be quizzed. I'll go over these one by one. They kind of come in groups in my mind, though, so I'm going to stop and do a demo in the middle. The first factor is code base. This is a principle that states you should use version control. Now I know what you're thinking, but bear with me. You're going to learn things in this talk, but there are some things I have to say, because there are people who do not use version control. But even if you are already using version control, you should be using it in the right way. And that is one version control repository per application, and then you deploy that application to multiple environments. You should not, of course, manually fork the repository for different environments. That would be undermining the version control system. But you should and this is more common, you should also not use a single repository for multiple applications. The reason this is a problem is that you start to commingle the commit history for these two applications that are residing in the same project. You lose the ability to do isolated rollbacks and you lose track of the coupling, where the coupling spots are between these two applications. So this isn't very common with pure Ruby applications, and that's because the deployment tools, the build and packaging tools for Ruby kind of trend toward a single app per repository. But with Maven and Gradle, I see sub-modules used for multiple applications within the same repository. Now the advantage of doing that is you get to manipulate or automate these multiple projects with a single Maven command. So if you need to do that, just use Git sub-modules. So you still retain that independent commit history and use your standard tooling to automate the processes. One of the other advantages of using tools like Maven and Gradle to manage multiple projects is that you can manage dependencies without creating your own Maven repository or whatever, which is always a pain. So that actually brings me to the next factor, which is dependencies. In the 12-factor app, dependencies are explicitly declared and isolated and you should never reply on the implicit existence of system-wide packages. What I'm really saying is don't check jar files into Git. Now that one's a dot too, but I guarantee you most of people working on a Java application have done this at some point. It's particularly problematic or has been particularly problematic with JRuby because the dependency manager for Ruby, Bundler, has no concept of jar files. So many times if Warbler does this too, you check a jar file into your repository because that's the only way to manage it. But there's a great tool called JBundler, Christians in here somewhere. We can thank Christian for that. This is a great solution to this problem. Gradle, as you saw this morning, is also a great solution. JBundler does not replace Bundler. It sits alongside Bundler and it uses a jar file for configuration. So just like you have a gem file, or in addition to your gem file, you define in your jar file the Maven jars that you depend on. You then install the JBundler gem. You run JBundler install and it allows you to do things like JBundler console which will give you a REPL with those jar files on your class path. Once you have that set up, then somewhere in your application you require JBundler and then you can Java import these classes very easily and keeping those jar files managed in the proper way. And of course you can vendor the dependencies too. As you can see it puts the jar files there under jars very similar to as we saw this morning with Gradle putting them under I think Phil Libs. Alright, so dependencies are a type of configuration that brings us to the next one, but they're not the kind of configuration that the 12 factor app talks about. The type of configuration the 12 factor app talks about is anything that changes between deployment environments. So things like resource handles to the database Mcached, credentials for Amazon, Twitter, and then per deployment values like hostname. So this does not apply to dependencies or maybe your config routes.rb things that stay the same through different environments. These kinds of this type of configuration should be strictly separated from your code. It should not be checked into your repository. Don't check passwords into Git. Now that's another duh, but this is probably the most commonly violated principle 12 factor app that I see. I'm certain you would not check your own personal password into Git, but you probably checked in a database password Twitter key and Amazon key. That's a problem for security reasons, but it's also a problem for portability because when you define that type of configuration within the code base it means that deploying to a new environment requires a change to your code. So you have to actually make a commit in order to set up this new environment. It makes your app less portable. So a good litmus test for this factor is can you open source your application at any moment without compromising the credentials to any of your systems? If you can, then you satisfy this principle. So we need a place to put this configuration still, and the place to put that is in the environment, specifically stored as environment variables. That's what they're for. So what we're trying to do at Rogue is get people away from using a database to store all of these different credentials and instead extracting those credentials or that resource handle from the environment variable. In this way you can stand up a new production environment with its own database without changing any of your code. So the database, your database is a type of backing service. That brings us to the next factor. Backing services are things like Postgres, your database, Redis, Memcache, and in the 12 factor app, these backing services should be treated as attachable resources and they should be attachable via some kind of URL stored in the environment. So this example of using the database is exactly the same way as you should attach a Memcache or Redis instance. This allows you to swap these different resources in and out if you're doing backups and restores without disrupting your code base. It allows you to easily switch between environments, so again increasing portability. The next factor, and the last before I do a little demo, is build, release, and run. This is a principle that states that your deployment should execute in three discrete steps. Build in which you compile any code, maybe prepare some JavaScript assets, and create some kind of artifacts that are ready for deployment. Release, you then combine those build artifacts with the configuration for a particular environment because that configuration should be separated from your code, and you create some kind of release image or release artifact that represents that release of your application. And then finally you give that release off to your deployment environment, which then knows how to run it. So ideally these three steps are automated, but regardless there should still be these three discrete parts to it. So some examples. Build might be a GRubyC, might be a rake assets pre-compile.  You're creating those deployment artifacts. Release really depends on the environment you're deploying to. If you're deploying a Warbler war to Heroku, it's a Heroku deploy jar. If you're using the Maven plugin, it's a Heroku deploy. If you're using Docker, it might be a Heroku push. Again, just depends on the environment, but it should still be a single step. And then finally running, again, kind of depends on your application, but if you are running an executable jar file, it's a java-jar command. If you're using Ruby server, it's a maybe a Puma command. But the key here is that it should be a single command. It should not be what I used to advocate starting Tomcat in the background and dropping a war file into it. Starting it as a service or yes, it should not be starting TorqueBox in the background and dropping a war file into it. That's something I sort of advocated for in the past. But what we're starting to see with TorqueBox with Immutant, which is sort of the TorqueBox for closure, even with Wildfly, which is the new JBoss and Wildfly Swarm, even JBoss is going towards this inverted approach to deployment, creating executable jar files. And of course, if you can automate all these into a single step, that's great. If you're deploying to Heroku, it's a Git push Heroku master to do all three of those. So let's take a look at what that looks like. I don't do live code because I make a lot of mistakes. So I pre-record my demos. You're welcome. Alright, so I have here a very simple JRuby application. It's actually a JRuby NETI application. And I'll explain what that means in a moment. It has a gem file with some gem dependencies, a dependency on jbundler, so I can use that. It's JRuby9000. Alongside the gem file, it has a jar file, which defines my NETI dependency. NETI is a high-performance Java library for creating HTTP and TCP clients and servers. It's used extensively by Twitter. I also have a proc file, which tells Heroku how to run my application. As you can see, it's a single command, to run the server rb. And that server rb contains a bunch of Java imports, which are made possible by jbundler, and then it contains a NETI HTTP handler. So the code for the NETI HTTP handler is kind of complicated, but that's because NETI is more akin to RAC than to Sinatra or Rails. There are frameworks like FNAGLE and RAPPAC that are built on top of NETI. We don't have one of those for JRuby. So get on it. Somebody build this. I need it. I think that would be a great project. So it's a much lower-level tool. I have this application. I can prepare it by running jbundle install, which downloads my NETI dependency, puts it into my local Maven repository. I can then run my application, which requires jbundler and sets up my dependencies. So there it is. It's running on port 8080. Very complicated application. All right. So now I have this thing working. I can deploy it to the cloud first by creating a Heroku app. So if you have the Heroku tool belt installed, you can run Heroku create, which provisions a new get repository for you. You can then push your code using get push Heroku master. I suspect most of you are familiar with Heroku, but what's happening here is it's downloading my dependencies, including running jbundler and creating a slug, which is a release image for Heroku that my app is then run from. All right. So I can use Heroku PS to check on the status of my process. And you can see the rubyserver.rb command is running. There's one instance of it, and it's up. I can use Heroku open to view the app running in the cloud. There it is. And I can use Heroku logs to check on the status of it. So yeah, you can see they're starting netty server just like it did locally. So when I push to Heroku, it's first executing that build phase, which there isn't really much to do for a Ruby application. And then it creates the release image, which I mentioned is a slug file. So each time I deploy, I get a new one of these slug images, and I can actually see the history of those with Heroku releases. So if I deploy changes that are breaking or cause them to fail for some reason, I can quickly roll back to a previous slug and then debug the problematic slug in a separate thread. All right. One last thing is I can use Heroku run to start a one-off process on the Heroku server so I can start a JRRB session. I should have run jbundler console. I don't know why I didn't. I can require jbundler and then import Java classes and do things from there. I'll talk more about that in a little bit. Okay. All right. So the next factor is, and actually the rest of these factors relate less to the process of deployment, which is what the first factors were, and more to the deployment architecture, how you sort of structure your application for deployment. The first factor is processes. In a 12-factor app, your processes should be stateless. Don't use sticky sessions. So don't keep session information within your process that needs to be there. If that process shuts down, it should not take anything with it. That's not too common of a problem in Ruby applications, but port binding is much more important. So this is a principle that states that your application, a 12-factor app, should be completely self-contained and it should export HTTP as a service by binding to a port. That is, it should not depend on any other piece of infrastructure to bind to a port and query requests for it. So what I'm referring to here is the old model of JVM deployment where we drop a war file into a container that is binding to a port and handling request process for us. Our application should know how to do that, either by embedding Tomcat or Jetty into our application or by using NETI as I showed in my example. The application itself should be completely self-contained. And this is what we're seeing with JRuby, but it's also what we're seeing with the rest of the Java ecosystem. So I mentioned Wildfly Swarm, Spring Boots, Play and Finagle, both used NETI, which I showed earlier, DropWizard, these are all tools that are becoming, that are gaining market share in the Java ecosystem and they're all containerless. They're using this modern deployment style. Alright, the next factor is concurrency. You're probably thinking, I got this one. JRuby's great at scaling up, right? But you also need to be able to scale out. And you scale out by diversifying your workloads. So decomposing your application into different parts that do different kinds of jobs, allowing you to if you need to handle more web requests, you can scale the part of your application that handles web requests without scaling the part of your application that's doing background work. Now this is something, this differs from what I used to advocate, which is application servers that can do all these things for you. But it turns out that scaling with an application server is much more difficult. This workload diversity could be interpreted as me advocating microservices, if you take it that way, then great. But whether you embrace microservices or not, there are still principles from the microservices methodology and architecture that you should embrace, regardless of whether you claim to embrace that or not. Another one of those principles from microservices that you should embrace is disposability. This is a principle that states your application should be quick to start up, resilient to failure, and graceful to shut down. So quick to start up, meaning ideally it should start up in less than a minute, ideally under 30 seconds. As you saw with my NetE application, it started up very quickly. It should be graceful to shut down when it receives a termination signal. Within 10 seconds it should release any connections, clean up any resources and shut down cleanly. And it should be resilient to failure, which actually kind of falls out from the other two. If your application crashes or you need to scale it down for whatever reason, you should be able to replace those instances very quickly. So this really gets back to how we used to think of our applications, how we used to think of our servers. We used to treat our servers as pets. When they were sick, we would take them to the doctor, we would want them to get better. We wanted them to live forever. These were our application servers. These were the pieces of metal running in the closet that I was talking about. They were very near and dear to us. But today we should be thinking of our servers as cattle.  If you need more servers, you go to the market and you buy them. If you have too many, you get rid of them because you don't want to pay the overhead of keeping them around. This is possible now because the cloud is cheap, virtualization is good, we can do this. So yeah, treat your servers as a commodity, not as a precious. So that said, application servers are not disposable but microservices are disposable. So yeah, I'm pretty explicitly advocating microservices here I guess. But again, it's really not about microservices as much as it is the principles that back up this methodology. Microservices are easy to replace, they're easy to modify, and they're decoupled from external infrastructure. So this is something we're seeing embraced by places like Netflix, Twitter, and Guilts. Netflix is using all kinds of JVM languages. Twitter and Guilts are both using Scala and they're all embracing microservices and they've open sourced a lot of their applications that they use at Twitter and Guilts. They're built on Netty. Okay, the next factor is dev prod parity. This is a principle that states your development environment should be identical to your production environment and every environment in between. So the most common place I see this violated is at the database layer. But if you're using Postgres in production, you should be using Postgres in development. I also see this violated at the server layer. If you're using Puma in production, you should be using Puma in development. The idea is to get that parity between environments. This is, we would desire this for a number of reasons but it's often mistaken as simply a development nicety. That having this parity allows you to more easily debug and prevent the introduction of new bugs by having a system that's exactly like your production environment. But that's true. But it also makes it easier to get to onboard new employees because if you can stand up your environment because it's identical to all the other environments, they can get started more quickly. So it makes your applications more reproducible. And that also allows you to stand up new test environments, new staging environments and new production environments. And if you can stand those new environments up very quickly, then you can also dispose of them. So this dev prod parity is actually a key step in the way to disposability. So these factors are very much tied together. Alright, I'm going to skip over logs. It's a very interesting factor but it's a little orthogonal to the others. And I'll go to admin processes. So admin processes, things, jobs like database migrations, one-off tasks, should be run in isolated processes. In short, you should not be logging into a production server to run your database migrations or one-off tasks. It steals resources from an existing process and it creates the potential for accidentally bringing that server down or bringing that existing process down. When you run those one-off jobs, you should run them in isolated containers. And that's exactly what was happening when I ran the Heroku Run command. I was getting not only a new process but a new container for my application, a new isolated environment. It's the same way as when I scale my application up, when I create more web instances, except with the admin instance I'm just not starting that web process. So I'm getting just another identical environment for my application. Okay, so to recap, codebase, you should use version control, but one version control repository per application. Your dependency should be explicitly managed. Do not check jar files into Git. Use jbundler. Configuration should be strictly separated from your code. It should be stored in the environment, not in your Git repository. Backing services should be treated as a, should be attachable via some URL stored in the environment. Your build process, your deployment process should happen in three discrete steps. Build, release, and run. Processes should be stateless. Portbinding should be done by your application, not by some external piece of infrastructure. Concurrency scale up as well as out. Your application should be disposable. This should be quick to start up. Grace will shut down and resilient to failure. And dev prod parity, your development environment should be identical to your production environment, and admin processes should be run in isolated containers. You can learn more about the 12 factor app on 12factor.net. We have sort of a, I guess it's a manifesto for the 12 factor app. It's a language agnostic methodology, so there's some things specific to Ruby, but nothing specific to JRuby in this manifesto. But on my blog I very often write about specific characteristics like the ones I talked about today. So what next? You know the 12 factor app. Congratulations, your name. What do you do about it? So this is a list of things that I would like you to do after leaving this talk today. If you have a JRuby application, try running Warble Executable War. It'll produce one of these executable jar files that I talked about. Alternatively, you could try JRuby Gradle. Just take your application, see if you can do that. Install Jbundler. Oh, there's supposed to be an R on there. Even if you don't have any jar dependencies, just install it, create a jar file, see if you can get it working. Remove all passwords from your code base. Find a place to put them in the environment. And deploy your application to Heroku or to some other cloud platform. If you deploy to Heroku you can deploy in one step. I think that's really the goal. Wherever you're deploying, try to get that down to a single command. Alright, again, I'm Joe Kuttner. I go by Codefinger and these slides are on the web. Before we do the mandatory applause, I have some games here today and I'm looking for some people to play them. So if anybody knows how to get into the great refractor telescope at the Libna's Institutes, I would appreciate it. Thank you.


It's time to drop the puck on another boys hockey season. A historic one at that as they're celebrating 75 years of the state tournament later this year. Bemidji began their season at home taking on conference rival War Road. Both teams looking to begin the season on the right skate. Scoreless in the first. Luke Johnson setting up a two on two. Throws it in front. Tipped off the defender and finds its way home. Warriors take the lead. After Gage Mostad tied it up he'd give Bemidji the lead. Nathan Minasaw from the point. Mostad tips it five full. It's two to one. In the second. A good four track four. Bemidji Wyatt Halverson gets the turnover. The captain Hunter Olson deeks the goalie right out for the 3-1 lead. And the Jacks looking for some more insurance. Bjorn Jorgensen from the point. A rocket slapper. Good luck with that one. The Jacks they get one more and they win five to one. Lakeland PBS.


Well, you're watching theCUBE, and I knew that you knew that. I'm John Walls, we're here in Las Vegas. It's re-invent, 22, big show, AWS, putting on the big show here late in 2022, that's going really well. We're at the executive summit right now, sponsored by Accenture, and we're going to talk about that relationship between Accenture and AWS, kind of where it is now and where it's going, you know, even bigger things down the road. To help us do that, two guests, Andy Tay, who's a senior managing director and the Accenture AWS Business Group lead at Accenture, Andy, thanks for being with us. Thanks for having me. And Sarah, whose last name was one of my all-time favorites, all good, because it is, it's all good, right? That's right, it's all good. Sarah, all good, worldwide leader of Accenture's AWS Business Group for AWS, and thank you both again for being here. Thanks for having me. So let's talk about the relationship just in general, high level here, 30,000 feet. A lot of great things have been happening, we know a lot of great things are happening, but how has this all, you think, evolved? How has this come about that you two are just an extra-billy linked almost here in the cloud space? Sarah, why don't you jump on that? Yeah, I'd love to. I think one of the strongest factors that causes that synergy for us is we both work backwards from our customer outcomes. And so just by consistently doing that, taking those customer signals, really obsessing over our customer's success, we know what we're marching towards. And so then we kind of extract those themes and really work together to think about, okay, when we look at this holistically, how do we go bigger, better, faster together and accomplish and solve those customer problems? No, Andy. Yeah, John, let me just maybe add, and to amplify what Sarah just touched on, we both have common to our culture this notion of working from the client's perspective first. So really delivering to the client's values or in AWS's parlance, it's customer. And so that's at the core. And when we keep that at the core, everything else becomes really easy, where we invest, what we build, key clients we focus on, what our team structure is, et cetera, et cetera. That's really easy. So that's sort of core pillar number one in terms of our sort of success factors. The second thing that I think really helps us is our sort of scale geographically, certainly from an Accenture standpoint, as you know, John, we're north of 800,000 people globally. Couple that with AWS's strength, we really do have a field depth and breadth across the board that allows us to sort of see and feel what's happening in the market and allows us really to see around the corners as we like to think and say. And that helps us be intentional on what we do. And then the third thing is really us, we might know what we do, but we sort of need to then play to our strengths. And as you know, we're two very different companies, one focus on the technology side, the other focus on the technology services, although we'll touch on some of the changes we're looking at as we go forward. But that sort of playing to strengths is key as well for us as a third pillar of success. And so keeping those three things at the core really helps us move day to day and year by year. And that's what you see in this continued partnership. So what are you hearing from your customers these days? We've talked a lot already today and it's kind of the buzzword, modernization, right? Everybody's talking about this transformation.  What are you hearing from customers in that regard? And I'm sure everybody's in a different state, different frame of mind. Some are embracing, some are dragging. What's your take on the state of play right now? Well, and I think especially in these macroeconomic moments that we're in, time to value is critical for our customers. And then we have the talent shortage. But even with those, our customers still need us to solve for sustainability and still focus on inclusion, diversity, and equity. And so we can't lower the bar in anything that we've already been doing. We need to just keep doing more and building with them. And so I think for us really getting to the meat of what our customers need, modernization is a big one, but we're still seeing just so many of our customers look at basic transformation. How do I dip in? How do I start to move my environment, move my people, and get ready for what I need to do next for my business? And so that is a challenge. And like we said, with the markets as volatile as they are right now, I think a lot of customers are just trying to work with us to figure out how to do that in the most optimized and efficient way. I just want to kind of rub people in the head and say it's going to be all right. It's going to be all right, right? I mean, it's so volatile as you pointed out, Sarah, right? I mean, a market up and down and worried about a recession and companies and their plants and they want to be forward thinking. But they've got to keep their powder dry too in some respects and get ready for that rainy day.  And then on the other hand, you know, maybe clients should sort of hold temper and sort of just pause. But I think clients get it, they see it, they feel it. They understand the need to invest. And I think, you know, there was a recent study back in 2008, those clients, you know, Sarah and I were reading the other day, those clients who didn't invest ahead of those major, if you remember those macroeconomic downturn times, they came out really on the bad side. And so clients now are realizing that in these times, these are the moments to invest. And so they get it. But they're faced with a couple of challenges. One is time as Sarah touched on. You just don't have time. And the second is talent. So we're working in a very intentional way on what we can do to help them there. And as you'll hear later on from Chris Wegman and Eric Farr, we're launching our Velocity platform, which really helps to compress that time and get them faster, you know, time to value. We're also being very intentional on talent and how we help their talents to, you know, rotate. So we're not just taking the technology journey, but we're also having the people journey. And then the third thing Sarah and I really focus on with our teams is figuring out new ways, new sources of value for our clients. And that's not just cost, that's value, the broader set. And so we find that in moments like this, it's actually an opportunity for us to really bring the best of AWS and Accenture to our clients. Well, you hit value. And I always find this one kind of tough because there is a big difference between cost and value. My cost is X, right? Whatever I write on my check, that's my cost. So, but how do you help clients identify that value so that because it's, you know, it can be a little nebulous, right? Can it not? I mean, it's, but you have to validate. You got to quantify at the end of the day because that's what the CEO wants to see. It's what the CIO wants to see. You've got to identify values. How do you do that? Yeah, I mean, we have many different ways, right? Velocity, which Andy kind of touched on, I think, is really, it's our foundational approach to help customers really kind of enter into their cloud journey and focus on those key factors for success, right? So we've got ISP solutions built in there. We've got talent and change built in. We've got kind of what we're calling the fabric, right? That foundational technology layer. And giving our customers all of that in a way that they can consume and a way that they can control and, you know, different modules essentially that they can leverage to move. It's going to be tangible, right? They're going to be able to see, I've now got access to all these things that I need. I can move as I need to move.  We've given them that picture and that roadmap on how to really leverage this because we need to be able to point to tangible outcomes. And so that's critical. Yeah, proof's got to be in the pudding. It's got to be. And, you know, to Sarah's point, I think sort of we're entering into this sort of new, there I say, new chapter of cloud. And in, you know, sort of the first chapter was sort of those outcomes around cost. You know, I've moved you into the cloud. You can shut down your data center. But now we've sort of got other sources of value beyond cost. There's new sources of revenue. How do I become a platform company on top of the AWS cloud and then, you know, e-count new revenue sources for myself? How do I drive new experiences for my customers? How do I maybe tap into the sustainability angle of things and how do I get greater innovation from my talent? How do I operate better? And as Sarah said, how do I become more nimble, more agile and more responsive to market demands? And so all those areas, all those dynamics, all those outcomes are sources of value that we're sort of really laser focused on and just ensuring that as a partnership we help our clients on that journey. So what do you do about talent? I mean, you've brought it up a couple of times. Each of you has, in terms of training, retaining, recruiting, all those key elements right now. It's an ultra competitive environment right now. And there might be a little bit of a talent gap in terms of what we're producing. So, you know, how do you, I guess, make the most out of that and make sure you keep the good people around? Yeah, talent is an interesting one, John. And we were just touching on this before we got here. You know, sort of from an Accenture standpoint, we're obviously focused on growing our AWS talent. We've now got, I think it's north of 27,000 people in Accenture with AWS certifications. North of 34,000 certification, which is absolutely fantastic. A small city. It's just a small thing. But we keep being very intentional in building that. As AWS rolls out new services, Adam touched on a whole bunch of them today. We're at the core of that and ramping and building our talent so that we can drive and get our clients quicker to their value. And then the second area of focus is what do we do to help our clients' talent? How do we train them? How do we enable them? How do we get them to be more agile and being able to sort of operate what we call that digital core, operate in the cloud? How do we do that? And so we're focused in capabilities, in fact our Accenture head of talent and people and change, Christy Smith, John is here this week just for that. And we're exploring ways in which we can get tighter and even more innovative around talent. And so ultimately that bleeds over to where the partnership goes, right? Because if you can enhance that side of it, then everybody wins on that. In terms of what you think, you know, where this is going, you know? It's already, you know, pretty good setup. Things are working pretty well, but as the industry changes so rapidly and you have to meet those needs, how do you see the partnership evolving as well to meet those needs down the road? We have a very fortunate position in that our CEOs are both very engaged in this partnership and they push us. Think bigger, go faster, figure it out, let's ride. And there are definite pros and cons in some days in flying this close to the sun, but it's an absolute privilege to work with them the way that we get to. And so we're always looking, I mean, Andy said it earlier, this is the relationship that helps us look around corners. We've raised the bar. And so we're constantly pushing each other, pushing our teams, just innovating together, thinking it all through on where are we going? And like I said, reading those tea leaves, reading those themes from our customers, like, hey, we've just had five customers with the same similar feeling problem that we're trying to solve, or we ran into the same issue in the field, and how do we put that together and solve for it? Because we know it's not just five, right? We know there are more out there. And so I think, you know, it's leadership principles for us, right? At Amazon, that guiding, think big, you know, insist on high standards. That'll always be core and central to who we are. And then, you know, fortunately Accenture has a really similar ethos, right? Yeah, give a quick take on that, Andy. Yeah, I think as we look out, you know, I think we're going to, we've already seen, but we're going to see this continued blurring of industries, of, you know, sort of clients moving into other industries and sort of this sort of agitation, market agitation. And so I think, you know, disruption, and we're being, you know, focused on what do we need to be, to do in order to help our clients on those journeys and to continue to get them, you know, faster. Solutions is an area that, you know, we are really looking at, and these are solutions that are either industry solutions. You'll hear a couple of them this week. You know, we've got our insurance solution we've developed as an intelligent underwriting capability, leveraging AWS AIML to sort of be intelligent and cognitive. You know, we've got other solutions around industries energy and life sciences, but then also intelligent applications that might be touching, you know, areas. I think earlier today, Adam talked about AWS supply chain and that's an area that we are focused on and proud to be a part of that. And we're working very, very closely with Amazon on that to help, you know, our clients move ahead. So I think we're going to see this continued blurring and we're going to, obviously, you know, keep addressing that and just keep iterating. Well, it looks like a relationship of trust and expertise, right? And it's worked out extremely well. And if this is any indication of the interview went, even better things are ahead for the partnership. So thank you both for chiming in. I appreciate your perspectives. Yeah, thank you. It's been great. We continue our coverage here on theCUBE. We're at Reinvent22, we're in Las Vegas and you're watching theCUBE, the leader in technical coverage.


What's going on everybody got Kyle here with latest sports cards and we are ripping one box for evan s it is a box of 2023 legacy football this is 2023 um where do they put it there it is 2023 i knew we had the right one just i don't know where they put the the number ain't no worries Todd what are you thinking about i was thinking about grabbing some star wars last night we had a deal on some um on the last year's galaxy from uh on trade night it's thinking about it but i ripped some finest last week so i i held off kind of wanted to uh chase a rough on a doll auto in the uh island again third two but for keys will Anderson Zach Evans there's a red this one is the 299 for the Beals Josh Allen Josh 299 is Josh we got a prize prospects rookie of Miles mc uh Miles Murphy Devon a a chain rookie I think Schefter told me to say a Chan a Chan not a chain Devon a Chan so i'm gonna give that a go got a will Anderson on the hollow under lights Texans rookie Mike Vic the more Hamlin plans today they're showing him right now that's kind of awesome there's a Mahomi it's a 199 chiefs chiefs on the orange Mahomes Ronnie lot decade of dominance Parker Washington shantuck bucks i guess i need to set the rest of my fantasy lineup i think it's all good i might have to check it though might have to check it there's a there we go Anthony Richardson on the under the lights auto there we go Evan second Anthony Richardson out of the uh the two footballs today from uh legacy and from um prism draft there we go a rich under the lights silver take that not a blast from the past thurmond thomas jaren hall tyree wilson take a little Anthony Richardson he's been looking good man and we got that concussion but he got too too uh not too touchdown before that concussion there's a Marvin Mims orange Broncos rookie now when it's to 149 and looking pretty good with ross as well last week not so much there's a Bryce young base rookie good luck you're Evan yes Ken yes nice hit you and him both got the buff got the uh Richardson's going today there's a yellow to 150 de hop de hop mic dicka it's a Jackson Smith and Mike Meyer it's a mini red this one is um 250 not bad there it's a Jackson Smith Jackson Smith rookie red on the mini number to 50 we got a silver of hendon hoker the lion's rookie qb tanner mckay brine branch it's a silver Jackson Smith rookie for the uh seahawks another mini jalen hyatt there's a triton simpson rookie for the tigers i got you Todd we'll get it going right after this my man thank you good luck let's see see if anything else came in the queue i got Todd and then Dustin Todd and then Dustin thank you guys thank you both there's a orange to 249 decade of dominance frant harkington champ bailey rushy rice paris johnson and last one here good luck mr evan nice hit on the Richardson auto now the rpa coming too it looks like and it's going to be for the cowboys the 249 it's luke schoonmaker on the silver rpa cowboys got him in the cowboys gear their futures on the rpa schoonmaker prized prospects darnel washington charbonne and cam smith on the back all right all right there we go evan nice one there on the uh one box of legacy got you an anthony richard sonato thank you sir we'll get that uh we'll get those cards right out


Hi everybody for this month's Craft World exclusive video I thought I would show you some fun ways to use your embossing folders. It's something certainly for myself that I have a lot of that kind of get forgotten so I'm hoping that this tutorial will inspire you to pull yours out and to create some nice backgrounds. Here I have what I've created through the video and it's free to watch, the direct link is in the description box below and that will take you to Craft World where you can see exactly how I've made these. But this one here so I've embossed it using my zigzag embossing folder but then I've also added embossing powder and heat set it and you get such gorgeous effects so you know you get the texture that tactile feel of the embossed image but also that lovely shine. Then I also emboss tissue paper so this is just some kitchen towel and you create really fun effects. This one here I've just added some yellow, well I've spritzed it with a yellow spray and then used some gold wax, gilding wax over the the bows there. So this has got more of a grungy mixed media kind of feel. You can tear the edges, add it to scrapbook layouts but also it looks lovely on cards and then this one here again it's got a lovely shine to it but it got I don't know it kind of looks a bit like material like leather or something really really fun very interesting. Then I show you how you can ink onto your embossing folders and create these kind of backgrounds. So this is using I've inked onto the debossed side and I explain all that in the video and it gives you this blue sky with the clouds. Some of you might recognize this one because I actually done this technique when I launched my first collection and then this is using my balloon embossing folder but I've actually inked the embossed part of it so it gives you this effect here. So they may look the same on the monitor but on this one here it's all raised on the top and then debossed underneath and on this one it's debossed on the front and raised on the back. Then I also show you the effect you get when you emboss a vellum and then this is another fun one this is actually using kitchen foil so it's just a couple of sheets and I've embossed it with the dragonfly embossing folder there as well. But I show you it all in the video so click on the links below and I hope you enjoy it. Thanks for watching!


When I saw this video I was started because this should not be. It was unfortunate that people allow themselves to be used by the devil to bring disrepute to the place of God. What would ever provoke you to the extent that you lose all sense of the sacred and even the law that guides a place to fight or extend blow before the cover? Is that not madness?  On one occasion there was a dispute regarding the stone, the black stone, when they were rebuilding the Ka'bah and who exactly should carry it? Which tribe is more deserving of it? They called Nabi Muhammad ﷺ he wasn't even a prophet yet but prior to that when he was much younger and they decided we're going to ask him and whatever he says we will do and he solved the matter in such a beautiful way. He asked the leader of every one of the tribes to hold a piece of the cloth and the stone was placed in the middle and all of them carried it to the Ka'bah and then he took it with his hands and placed it in its place. So that is something unique. They trusted him with this and it was the gift of Allah for him ﷺ. May Allah grant ease to everyone and grant us a lesson. You might be known as a trustworthy and honest person but one day when you say something that people don't agree with or they don't like everything will change and take it in your stride.  Welcome to another episode of the Open Minded Thinker Show. Please do like and share this video. Don't forget to be part of the family by subscribing to one of us, reach others. This is very very important. Today I want to talk about a very serious issue that has been circulating in the news lately that is fighting in Masjid al-Haram in Saudi Arabia. I am so furious right now as you know Masjid al-Haram is considered the holiest side in Islam and every year millions of Muslims from around the world visited to perform their Hajj and Umrah program. However in recent times there have been reports of people fighting and causing chaos within the sacred premises and I want to make it clear that this behavior is just not wrong but also morally bankrupt. It's reprehensible. First of all, the holy side is meant to be a place of peace, tranquility and worship.  Engaging in violent behavior goes completely against the very essence of what Masjid al-Haram stands for and the generality of Islam. Islam teaches us to be respectful and tolerant towards others even those who hold different beliefs from us. Violence and aggression have no place in our religion and they certainly have no place in Masjid al-Haram. We must remember that the holy side is not just a physical place but it also holds a deep spiritual significance for Muslims. This is symbol of our faith and we must treat it with the utmost respect and reverence. We must not allow our emotions to get the better of us and engage in art that would tarnish the sanctity of the holy site. And then this video of supposed real Muslims. I urge everyone to remember the true purpose of Masjid al-Haram and to act accordingly, let us uphold the values of Islam, respect one another and try to make our programmage a peaceful and meaningful experience. My joy is that the guys in that video according to report have been arrested by Saudi police and will be investigated in charge. Ultimately these two guys were wearing the Eram and sported exchanging. I mean a hot one between the Safa and Marwa mounting. For the sake of people who have easily forgotten what is our stake here, Eram is a sacred state that Muslim programs are due during the Hajj or Umrah programmage. It involves wearing a particular garment also called Eram out of serving certain rules and restrictions. Well it will be pertinent at this point to remind you, of course most of you know about this rose but it is important that I remind you of this rose especially in Saudi Arabia. One of them is the Eram garment. Men must wear two white on-stitch sheets of clothes. One wrapped around the waist and the other dropped over the shoulder just as you see in the video right here. Women can wear any loose fitting clothing that covers the entire body except for the face and hands. It is recommended to wear white clothes but obviously not compulsory. No use of scented products like perfumes or deodorants. No sexual intercourse kissing or touching with one spouse right there. No hunting, fishing or killing of any living creature. No covering of the head or face for men but women can cover their face except in the presence of non-Mahrams that are men who are not close relatives. Advocate during Eram Muslims are encouraged to practice good behavior and manners including avoiding arguments or fights. That's avoid arguments or fight by every means. Referring from speaking eels of others, maintaining a peaceful and humble demeanor. This is really very important and related to what we're talking about today. Performing acts of worship and seeking forgiveness. These are some of the rules of wearing Eram in Saudi Arabia. It is important to note that observing this rose is an essential part of the pilgrimage and failing to do so may invalidate one's hajj or umrah. Brothers and sisters, let's pray for those people who I mean deceived by the devil so you can make a very, very I mean sinful act of the Kaaba. It's really painful. Let me right there. Please share this as a means of form educating others and you know reminding others the dangers of involving in behaviors. There are completely antithetical to the norms and etiquette of the Eram. Well, we pray that God will forgive these guys and then bring them back to the senses and of course the law we do to them what it is supposed to do. You see that next time they do not try it elsewhere. Well, thank you so much for being part of this show today. I'll do like, share and subscribe until next time. As-salamu alaykum.


Okay, ever since I lost my leg and saw these I've been dying to try them out. This is not sponsored These are the Nike GoFly ease where you can just like step into the shoe I'm not sure if it'll work with my prosthetic foot, but if it does oh my god, that would be so helpful Wait, wait, how do they work am I doing it wrong? Let's try it. Let's try it this way. Wait, how do these work?  Oh, this is so cool. Come on. Come on I feel such a sense of accomplishment about doing that without me hands That just that's so cool put in no hands friggin revolutionary. I love these


morning California, the California earthquake order warning system and the My Shake app. This really did serve as an opportunity to engage people on, you know, what we're trying to achieve with our future implementation plan, which is again, you know, bringing in those industries and making sure that we integrate it into our daily lives. Throughout our tour, we were actually able to talk to individuals from several of these industries and encourage our critical infrastructure industries to visit our website for information. You know, we have toolkits available online that are sector specific. So, you know, for example, one of our stops was in San Luis Obispo. It was at Cal Poly San Luis Obispo. So we actually have a higher education specific toolkit available online for them to be able to integrate. And similarly with our first responder toolkit that we have available, one of our stops was also at the Bakersfield fire station. And so, you know, we obviously really are trying to encourage industries to adopt the EEW practices and technologies and really integrate those automated actions. And so we have a couple pictures here as well from some of the the drills, I think Lori's up there on the Great California Shakeout Day. And so just a reminder to please, you know, make sure to practice that with your family, friends, colleagues everywhere you can. So lastly, too, I just want to make sure that we remember of the importance of, you know, collaborating and building these partnerships, because we can't do one thing without the other, you know, we can't continue and innovating this technology without sharing this technology and educating others educating California. And so, you know, we have these two pathways, we have the people and then we have the industries. And so we want to make sure that those continue to move forward. And so we'd also just want to specifically thank board member Lupita for stopping by at our homeboys industries stop in Los Angeles. So thank you for participating in. As Lori mentioned, you know, we do hope to have several more of these outreach events and tours in the future. And we really hope that you we can count on your partnership and that you are engaged throughout this process, because like I said, you can't do one thing without the other. So we'll need as much help as possible. Thank you. Thank you very much, Yvonne. Right now we can look to see if we have any comments from the board. And if you're online, you may unmute. Derek, I'd like to go. Thank you. Thank you, Yvonne, for that. It was a, I went to the Los Angeles session the day before the 20th, the great shakeout and my kudos to the team. You all did an incredible job with the simulator, the different kind of information. It drew a lot of media, which is always such a great part of like they're an extension of our awareness because they're the ones that get the message out. And you were spot on earlier, Yvonne, when you mentioned about students, they know what to do because it's part of their curriculum on October 20th every morning, every year they go through the drill. And so they know and they bring it back home as well. And I thought that that session, really when you get in the simulator, because we haven't had a big earthquake in LA, you forget what it's like and you forget to kind of plan and you forget to, you know, I can tell you right now that I'm not prepared at home today because it's been such a long time since we had one. And so it's just a good opportunity for us to continue to reinforce that. Thank you all. So I have to say, you know, we, it's very easy for us in programming to get lost in the metrics and the technology and the complexities of this very large system with so many partners, right? When we talk about the media and the metrics, you know, we got this many interviews, we have so many impressions. It is because our strategy is based on that force multiplying a strategy of utilizing the media to amplify our message. And that's why these tours are so critically important to our overall plan for outreach and education because it is much easier for us to be down there talking to 100,000 people all at once and one 20 second, you know, 30 second, even we've had even a segment go as long as nine minutes of them covering this topic. And so when we talk about the earned media strategy and the media, it is only the vehicle to get us to talk to the people because we could never buy a media package that will allow us to have an engaged audience as if we, you know, as when, you know, an outlet does a story on us that lasts three minutes, five minutes, nine minutes long. So, so really, you know, I, you know, something that I want to amplify something that Yvonne said is that we really feel at these tours that the groundwork for not only Santa Rosa and San Jose and I almost create a watershed moment for us to really not just in the brand recognition of the media outlets to see, to say, oh, wow, earthquakes, hey, we should go talk to Cal OES because they have a message of downloading my shake and drop cover and hold on and, you know, it's a trusted, it's a trusted agency. And, and so we're, you know, we're very pleased with the strategy and more importantly, we're pleased with the fact that we made able to get the message out to so many people in this way. And if I may kind of going back to that part of the conversation where we were talking about the automated implementation in various sectors, it works the same way. So if PG&E puts, you know, earthquake early warning into their buildings and then it gets picked up, which happened and a story is written about it, then other utilities say, hey, we should be doing this too. You know, Google gets really great press from their integrated alert system. So there may be another company out there that's seeing all this great press thinking, we got to do that too. One can only hope. So I'm, I'm, you know, just saying that amplification is, it works on both sides of this education. One last thing, something that we saw during the, this tour in particular is that we were actually able to connect with multiple large companies that had people that came out to the event, such as Dignity Health and down in Southern California. And we had NBC Universal, I believe that we also were able to create a contact with. So we do have that, that dual, you know, that parallel effort of, you know, the individual, but also the industry slash sectors. We do have a hand raised from board member Amina Assefa. Amina, the floor is yours. Hi, I just kind of wanted to, I guess kind of chime in around the industry actions and, you know, the, the kind of two prongs of like personal preparedness and it's really important for people to drop cover and hold. We know that people are still not going to do it. We also know that. And that people who are going to drop cover and hold then still be critically injured in the earthquake, right? Like we're, there's going to be things that happen that are just out of our control. And I think that there is just a level of as anyone who works in emergency preparedness knows is moving the needle on personal preparedness is hard. And it takes a lot of effort and that needle does not move very much. And so, Lori, I appreciate going back to like the industry specific actions and what, what does that look like?  What does adoption actually look like when you're talking about, well, how does the industry implement it? What does adoption look like? And when you were saying, well, we can have it in the EOC, it's like, well, what are you going to have in the EOC? Is it on the PA system? Is it what, what are you actually going to do? And, and I think that's where the struggle is. You know, for me, as I think about it, it's like, well, what does, what does this actually look like? How is it integrated? And I went to the toolkit for higher education is, you know, talking about, you know, having it on the PA system. And I think, yeah, that's a good example. And I say this with all love, you know, if it's not in the state EOC, how, how are you expecting other? I mean, I think that's leading by example, you know, it should be something that is in these high profile buildings like the state EOC, the state EOC gets put on television all the time. And to have that, you know, hardwired in there seems like a good first step and could, you know, show to other people how to do it. I guess I'm just, I'm still not sure. And I want to be the best board member I can be and take this back to the UC. We have thousands and thousands of buildings. I just, I actually don't know how. And I think that's what I'm still struggling with. And additionally, like, I appreciate the toolkit. I think what would be helpful for certain industries is, you know, some kind of, and I know this may not be in the budget, but some kind of visuals like CGI or something where you show people, you know, getting notified or and actually what, you know, kind of having a visual of what could be done versus just saying, just saying it in words. I think that would have more of an impact. And I know for our healthcare industry, you know, we have five hospitals like I think that having that, you know, they actually do have fun funding and they can do things having something that I could show them besides just telling them you can integrate it into your hospital build. I think that would be helpful. I'll stop. Thank you. Okay. Thank you so much for that. I think you honestly expressed probably what every board member has felt at at some moment or another. And I want to respond to some of the things that you raised. One is integrating earthquake early warning in the state operation center. And we actually are pursuing that. But the state operation center is not in a hugely seismic seismically active area. But we have other administrative offices in the state of California that have their own EOCs. And we're actually embarking or will be soon on a new one in the southern part of our state. So we've already started working with our logistics team who's managing that that project to integrate earthquake early warning into those those EOCs. And it will probably take the form of a PA and flashing lights or signage or all of the above. Because, you know, you have folks with different access needs. So that's one thing. And then you also mentioned visuals. And I'm right there with you. So we've actually created some video clips of what are we calling them? Success stories. Success stories of folks or places that have integrated it. And we have those there on YouTube. We can provide you with like a library list. And USGS or others partners may have more. Give us a quick rundown on the different industries that we've already done success stories on. We have done transportation with trains with Metrolink. We have done actually education with la usd and their implementation at one of their sites. We have done Menlo Park fire district with their with their configuration that they have with audible alarms, visual alarms, automatic gas shut off and bay doors, of course, I'm sorry, bay doors, as well as we're actually going to be looking into other assets that have this technology in Northridge Hospital and being one of them and the regatta seaside condominiums to speak to the housing element of integrated technology. I will add Amina that we also do have sick excuse me toolkits that are specifically targeted at industries such as education and we will after this meeting make them not only available to you, but we can also make ourselves available to kind of provide you a little more in depth as specific to your to your sector of what what it could look like potentially, especially for a for an organization that has as many buildings throughout you know high high risk seismic areas. Yeah, and I would say we've got CSU and UC on this board and you know if you want if you would start say in labs that handle chemicals or something like that you know if that's where you want to start or you see in some of your health facilities, we'll send out a team to film you and then you get to become one of our success stories. Yeah, I think you know I appreciate that and I appreciate kind of responding to my comments and I and I have looked at the toolkits and just to kind of add on you know what I'm thinking and as you were talking and is like you know we have a stadium at Berkeley that's you know built on a fault line and you know we don't have a success story there thankfully we have an earthquake on that and they were a fault but it even creating like for stadiums like I when I was trying to say earlier is like there's the personal preparedness which is one prong and then there's mitigating these impacts to critical infrastructure which is going to you know being able to do that is going to directly relate to our ability to recover from an earthquake so if we protect our critical infrastructure we speed up our recovery and I assume that is the ultimate call like we want people to be safe we want life safety but when we're talking about you know what happens after the earthquake is protecting our critical infrastructure and mitigating those risks so if you think about 60,000 people in a stadium you know is there some kind of you know I'm thinking of a visual not just for our stadiums but all the stadiums of getting a message out onto the you know the PA system in a stadium there's going to be an earthquake and then seeing people taking protective action to protect themselves so it's not something that's been done it's not a success story but it's a this is this is how this this technology could be used so it's like you know visuals for how it could be implemented that people maybe aren't actually doing yet and I'll stop there so Noah I totally understand that Abina you know what we we're definitely going to look into that and we're probably going to make contact with you just to make sure that we kind of realize that that vision that you have and and see how we kind of get that implemented in some fashion thank you so much I do believe Jack does have a question online yeah thank you I just have a comment is I wanted to to second the the idea of of you know trying to figure out how this plugs into our system I will say that you know I think we have a lot in common with our friends at the UC system and and especially with the number of buildings we we look at things maybe a little differently than what you just described not so much on function or like say a lab building or that we actually have mapped all of our campuses and we've we've actually our ground motion coefficients that are in chapter 16 we actually have come up with our own and actually we have a we have a triage of of let's say campuses that are really high have high seismic activity versus you know campuses that don't and so we we we look at it from that standpoint I was glad that you were able to reach out at San Luis Obispo I would encourage the staff to always go to the campuses I I can always put you in touch with people that potentially could be part of that outreach at the campus so just contact me for that I have plenty of contact lists and for our campuses we again we we have a you know any at any moment in time we have you know over 500 000 students wandering around on our on our on our property and so from that standpoint we're always cognizant of that we also just to gotta let you know is we've gone through we went through our own kind of drill where we had an earthquake in southern California we we simulated that I think it was back in June is when we did that and we actually did it so that two campuses were affected which was quite interesting so we we would you know we and we had a we have a makeshift EOC that we stood up that we can't stand up and we have a we have a system that we can communicate through so I would be nice to figure out how to get like I said earlier we will I one of the things that we all do there's several of us at the chancellor's office do whenever there's a quake um we look on our my shake and we look and then it gives us the indication of how to respond to the campus so I just wanted to say I really enjoyed some of the presentations today and um and I I'm I'm going to be thinking a little bit more hard about how this plugs in to certainly the CSU thank you jack board member jack Anderson that and we can't stress enough that sort of the goal of this discussion today was the tip of the iceberg we have done a lot of thought and as you might expect we put a lot of thought into it we've developed some toolkits we have things that are on the horizon but we really wanted to get your wheels turning so the fact that the picture isn't necessarily clear today is okay this is a partnership and larger than just our staff we have the great partners behind that fill in the seats behind you that we plan to work together and this is the direction for us for years to come so this is not something we expect to be solved tomorrow and really do appreciate everyone's heartfelt thought into this okay and with the for sake of time we do I think need to at least open for public comment again we'll allow for three minutes if you have any questions in your online please put in the q&a section or utilize the hand raise portion and if you are here in the audience you can approach the podium all right hearing none I will turn it over to deputy director nizhura for closing comments I'd like to thank everyone today not just for taking three hours out of your schedule to be here but the robust conversation the information that was exchanged and I would like to identify a couple folks that have not been called out yet in the back of the room we had oh we had the new executive director of the seismic safety commission andy ewardson who and one of her staff who have are now seated at call oes and we're just thrilled to have that partnership with the seismic safety commission we also have our california geological survey here today and they're a great partner as well they've been building out stations and doing various things to further earthquake early warning as well so we wanted to call that out thank you and then I want to thank google and usgs for presenting to us today and kind of blowing our minds with some of the things that you're doing that's great and keep at it that's fantastic maybe we'll have you back in a couple months and you'll have some new technology that you'll be revealing I also want to thank our partners that came here in the room we've got Caltech and UC Berkeley thank you so much and for any others that were online and of course for each and every board member today thank you so much for coming and for your comments and expect a phone call or an email if you brought up some ideas that we can we can use as a springboard to start up some of these new implementing projects so thank you all for coming today thank you deputy director nizhura with that we can entertain a motion to adjourn would anyone like to motion that we adjourn and a second a second all those in favor hi motion passes thank you we are adjourned thank you thank you thanks everyone thank you all appreciate it thank you all


What's going on everyone Sam here with late in sports cards We're ripping four boxes of 2022 zero cool jack-ash trading cards for Levi S. So good luck here Levi Let's pull you a Johnny Knox pillow That's what I would like to see All right, so again as always I Can't show the most of the not most but some of the cards, so I'm gonna have a filler next to me I'm gonna place the cards on top and then whatever I can't show. I'm just going to go ahead and Like move like cover them with the filler, so let's go. Goodbye. Good luck here. Levi puppet show On the lens Jackass number two Jackass rookies and a quiet game. Wow. No coverage in that first pack watch now. It'll be like three You know that goes Big red rocket behind the lens MGK Rick Kosek and the quaking at the Party boy, there's Johnny Knoxville. Is that a sign? Huh? We've got a chrome of a behind-the-lens 40 out of 100 on the refractor another chrome this time 12 out of a hundred Tony a Bellacy and quiet game steve. Oh No shot I've done too many of these to throw it all away now Hi toilet behind the lens. Geez. There we go a Field goal base Knoxville. Was there a Knoxville chrome? Yeah. Yeah. Was there? Yeah Take a look. Yeah, I think that is the variation That is the the SP right there not numbered. But yes, that is the Knoxville chrome Nice one there congrats and one we definitely cannot show So what's Otter behind the lens what card number was the Knoxville sorry part number two. Yes. Yeah, our number two Yes, part number two. Yes, sir Francis in Ghana a Dave England And the tarantula and underpants Sean's favorite car Number two that is wrong whoopies rookie Toilet geyser The yak charge Behind the lens PK Subam Spike Jones and The trip triple wedgie. I remember that one. That's in one of the very like very old ones Yeah, I think so Or in China sound behind the lens Tony Hawk Legend Lance Bangs and the backdrop Right out of the trunk in the gas station Rob your deck danger Aaron that is Jackass and 3d on the chrome card and Down the clown is field goal a behind the lens a Down the clown next numbered 94 out of 100 Nice one there on the refractor a Bathing beauty that was a classic Woodpecker, that'll do it right there for box one See something big in box you here. Yeah, everyone golf is fine. Nice red. So the hardest boxes to open up Then trust me dude, they're tough Ten years later Let's let this focus again really quick here all sorts of messed up. There we go. We're back in business guys We're good. We're back men and underpass pants again There's a stevo on the chrome Chrome Eric Monaca Wish I could show it, but it's the fish hook 24 out of 25 on the red nice one there And quiet game Rachel. We need a big auto yak charge by the lens Chrome is the hurricane slide SP as well on the Steve. I was gonna say I think the stevo is an SP as well the It was one of the chrome ones. I think was it that is that stevo or no? No, it's a rookie this one right here They'll sleeve that up one up worry for sure Yeah, you're good. No worries We've got a jet ski blue 13 out of 50 nice one there. Yes, this is your cool product and quiet game steve Beauty and the Beast behind the lens then yellow tool Knoxville and One we can't show that up nails behind the lens Jackass number two Rachel Wilson and Torrential element Zach throwing up dark shark spike Jones and The toilet geyser that of nails 95 out of 100 on the refractor I'm gonna cover like half this card up. We've got 26 out of 100 that's a behind the lens that is projectile vomiting off and Then the triple wedgie that's part two or yeah jackass number two And that's true and Pulling stuff that Levi doesn't have yet Mojo is still in place Well, did you see what we pulled out of the last ditches and slabs worry high five? That is DJ Paul. It's like we got an auto coming up. Ooh nice stevo We've got numbered To a 50 Butterbean nice one there can grasp on that one. Oh Boy Advance someone on Twitch. Sorry nice one there nice Butterbean the vulture You needed his auto. Let's go there. We go that is a success right there. We pulled an auto that Levi didn't have yet Invisible man behind the lens a Chrome flight of Icarus a Chrome Butterbean and a down the plow Which pulling something that Levi doesn't have out of out of jackass is like a success on it's own That is huge right there for sure the exploding room behind the lens Eric Andre Lance And the bathing beauty All right, that'll do it for box to we are halfway through good luck Departments that were boxing that was so fun Humphrey Marlon Humphrey on the corner back blitz at the sack got a purple one right here Does that mean Mojo? Empty box to move it around so you can't hear anything All the packs are up bed of nails behind the lens Flight of Icarus chrome Zach Holmes chrome on the rookie and the backdrop. This is a funny one the backdrop to See Poof final lens Jackass forever screw car and one we can't show So Ravens, we got another auto here field go Rob. Deardeck. We've got Dave England We've got a red Rick Kosick on the legend auto eight out of twenty five Yeah, nice one there congrats man That's actually a pretty awesome Take a Rick Kosick two autos All magician definitely when we can't show yeah, Rick is such a good you such a trooper behind the lens Chrome behind the lens we can't show nice one here. We got a legend that is um Spike Jones 14 out of 100. Let's go Roy didn't have either leave. I didn't have either of those really wow. Let's go dude Spike Jones on the numbered cart and a Bush of bees as I'm sure all of you guys know which one that is In the lens Really Tony Hawk Sean Cliber And coffee truck prank. Yeah, true invisible man Oh behind the scenes of the sweatsuit cocktail that one's the awful really.  Good luck, buddy See if we can pull you a third auto you don't have yet got green this time Four different colors this time. We got green the regular one purple and red SP we man to nice. That's third short print Let's pull the short print every box. That's awesome field goal Sean's favorite part dark sharks Lance banks right on top when we definitely can't show Hmm behind the lens Jackass crew course another behind the lens and a quiet game the high five Behind the lens Jackass forever rookie of Zach Holmes And quiet game Ravel a Rachel invisible man DJ Paul Steve oh and quiet game Steve oh again Exploding room Jackass number two Chrome we can't show and base we can't show jet ski behind one Eric Andre Sean Cliver Tarantula helmet He packs to go here. Levi in the tail on the donkey. This one's so gross I Another SP chrome we man nice Two of them and there we go toilet guys coming up here a chrome behind the lens we can't show Another chrome behind the lens we can't show this one is number 38 39 out of 50 nice one there triple legend sweatsuit cocktail He goes I know what that one is Matt Hoffman cool on there taunty us and base Last pack of your break. Good luck. You're Levi T-ball behind the lens base Eric Monaco rookie and of course we got a vulture to end it Why wouldn't we and that'll do it for your personal there Levi? Thanks again for jumping in man always a pleasure to rip for you. We'll get them right out to you