The queues, timing queues, who is giving the timing queues? Hello, everyone. Thanks for joining. My name is Animesh Singh. And these are my colleagues, Daniel Crook and Manuel Silvera. We are part of the IBM Cloud team and have been working on OpenStack, CloudFondly, and Docker for the last few years. Specifically around OpenStack, in the beginning of 2013, IBM made a decision that all our infrastructure as a service offerings are going to be based on OpenStack. And then last year, we made a big bet on CloudFondly by investing $1 billion in IBM Bluemix, which is our platform as a service offering based on that. We are also doing a lot of work around Docker, about which we'll definitely be hearing soon. Now, according to a research, which was done by CRISPR Research, OpenStack, CloudFondly, and Docker sit in the top four of the leading open source cloud technologies, which is not surprising, because of the growth of the community and the capabilities they offer and the way they compliment each other, they deserve that place there. In IBM, our cloud strategy is being based on open source standards. Be it at the infrastructure as a service layer with OpenStack, Open Daylight, OSLC, or platform as a service layer with CloudFondly, MQTT, Node.js, et cetera. Even at the software as a service layer, we are using open standards like JSON, HTML, Eclipse. And that's where the cloud strategy is evolving within IBM, and that's where it's based on. Now, where does Docker fit into that? Is it infrastructure as a service? Is it platform as a service? Our view is that it actually fits into both of these spectrum. And as we go through this talk, we'll get a little bit of idea in terms of why we say so. With that, let me come to the agenda. Manuel is going to talk about OpenStack, CloudFondly, and Docker, given an overview of the architecture as well as the community around them. Daniel is then going to come and talk about how to CloudFondly and OpenStack intersect, and also a lot of projects which are happening at the intersection of OpenStack and Docker itself. Finally, I'm going to come back and talk about the CloudFondly and Docker intersection and how do all these three different technologies then come together. With that, let me pass on to Manuel to talk about OpenStack, CloudFondly, and Docker. Thank you, Anamesh. So I'm supposed to give you an introduction and background into OpenStack. I think we all understand what OpenStack is, right? We agree that it's a collection of well-integrated modules that give you compute, networking, and storage, and it really provides your infrastructure as a service. At IBM, we agree with this statement that OpenStack is the ubiquitous open-source cloud computing platform for public, private, and hybrid clouds regardless of size. So let's talk about CloudFoundly. There's really four points I want to make in this slide. The first point is that CloudFoundly is open-source. This is just like OpenStack. CloudFoundly is the big advantage to be in open-source is that you're really not tied into any single vendor. At the end of the day, if you choose to move whatever your workloads are, you're free to do so. So this freedom is very powerful. The second point is that CloudFoundly is a platform as a service that utilizes your infrastructure as a service. So the big advantage here is that there's really no interference, no interaction, no duplication of efforts in the work that is done with CloudFoundly and the work that's done with OpenStack. The third point is that CloudFoundly is very developer focused. It's not as opposed to being operator focused as OpenStack is. It's very developer focused. So the whole idea is that you create an application, you deploy an application, and let the system, let the platform as a service, take care of actually how it's going to get deployed, where it's going to get deployed, actually what deployed means. And the last point is that there's a big community, a compelling community, built around CloudFoundly. So what we're seeing is that in CloudFoundly, you'll see in a little bit, there's this concept of run times and this concept of services. So your run times and services, every day there's new and exciting services and run times available. So this is the architecture for CloudFoundly. And what you'll see, it's sort of similar to OpenStack in the sense that you have a lot of very isolated, very separate components, services. The big difference between CloudFoundly and OpenStack is that these components are dynamically discoverable and loosely coupled. And the way that this happens is that CloudFoundly has this central service called Bosch. And what Bosch does is it's the way that it controls, it interfaces with your IaaS. And then it actually manages whether systems are up and running, it manages the health of the environment, manages what needs to be deployed, what it means to deploy, where you deploy. And the way Bosch does that is through monitoring of health. So basically, every service end point, every service advertises their health and status and then other agents then monitor that and act accordingly. So let's talk about Docker. So in Docker, there's two things I want to talk about in this slide. The first thing is that Docker is really built around creating applications and then running these applications on any infrastructure. It's the same application run anywhere, whether it's Red Hat or whether it's running on Ubuntu or whatever. It's the same application. You don't have to worry about what the underlying infrastructure is. And the second thing you want to think about is that with CloudFoundly and OpenStack, you have very clear separation between what your platform is and what your platform does and what your infrastructure is and what it does. With Docker, you have this interesting situation where you basically think of everything as developers sort of think of what's inside the container. And what's inside the container is sort of a hybrid between an IaaS and a PaaS in the sense that you have your application, but you also worry about the middleware and the applications that are built around it. And then as an operator, you worry about what's on the outside of your container. So once I have a container, how do I deploy it? How do I scale it? How do I run it on different servers? How do I create patterns out of that? How do I have orchestration related with that? And so at the end of the day, again, like I said, it's not a clear separation. So sometimes the developers have to worry about patterns. And sometimes the operators have to worry inside the container. The architecture for Docker is very simple. It really basically consists of two things, a Docker server, a demon process that's running. And this is the one that does all the heavy lifting. It does the building. It manages the building, the running, the distributing of these containers. And then you have the client server, the client service. And what the client application does is it manages, it's the interface. It manages the server. These two can typically be co-located on one machine if you're running on your laptop. But if you have a larger environment, the one client would connect to multiple servers wherever they be. And the way it connects to these servers is through a RESTful API. OK. So the Docker container really consists of, I mean, it takes a while to understand this. But at the end of the day, it is running and leverages the kernel from the host operating system. But then everything else is built. It has to be packaged on the container. So you have a very small operating system. In fact, it's only the required, it's the bare minimum of libraries and services that your application requires. So if your application doesn't require certain libraries, languages, documents, it's not included. So this is why the packages can be so small. And all the other components and services provided by the kernel are actually given by the host operating system. The Docker image is a read-only image. So once it's mounted, what we have is something called the union file system, which gives you the ability to then mount a read-write layer on top of your file system. And all of this, Docker makes all the reason that all this is possible is a bunch of really cool technologies that are built into the Linux kernel. These are, for example, namespaces, control groups, union file system, and then the container technologies.  And really, the answer to that is a question of how much control you want. With a virtual machine, you have effectively all of the control and all of the isolation that you would have with a physical machine. But the cost is that you have a performance hit because you're virtualizing hardware. You have to install the entire operating system. However, this can be a small operating system. And then you have to install the middleware application, libraries, anything else that you need. So at the end of the day, Docker gives you the ability to simply focus on the application and the bare minimum libraries associated and required by that. And so the big advantage is that Docker, the CPU performance, is it's almost native performance. It's effectively native performance because it's using the same kernel as your host operating system. The memory performance, there's a small hit. And the reason there's a hit is that Docker is doing some accounting. But if you don't want that accounting, you can actually turn that off. The network performance, the network performance can be there's a small overhead associated with some tagging. But that can be optimized and be down to zero. Creating a new image is almost, for those of you who've tried it, it's almost instantaneous. It takes a few seconds. And because we're using something called copy on write.  You have to boot. You have to copy it, do all that. And finally, apps in different containers can share the same libraries and binaries. So now let me hand this over to Dan to talk to us about Cloud Foundry and OpenStack. Great. So Manuel gave you the overview of what OpenStack, Cloud Foundry, and Docker are independently. Basically what they focus on, the developer communities that they target, basically the technology behind them. So this part of the talk, we're going to move into actually how they integrate, how they build on each other to provide good hosting environments for next generation cloud native workloads. So let's look at Cloud Foundry and OpenStack integration. So as Manuel noted earlier, Cloud Foundry, just like OpenStack, is the deployment architecture, very highly distributed, made of different virtual machines that are assigned different roles. So each of these components, they need some primitives from underlying infrastructures of service. So storage, compute, networking, things like that. And in order to provision those resources in a cloud agnostic way, it uses a cloud provider interface and a tool called Bosch, Bosch Outer Shell, a core component of Cloud Foundry, to actually get the primitives, the compute, the network, and the storage. And this abstraction makes it very nice for hybrid scenarios, for development scenarios. So it can provision out those resources into a public cloud, like SoftLayer or Amazon web services, but also on OpenStack in a private deployment, or even on a developer workstation using containers, using a Bosch LightDriver. So how does Bosch actually bring up a Cloud Foundry cluster on top of an OpenStack or another cloud? It basically, like other deployment tools like Chef or Puppet, Ansible Assault, it's basically infrastructure as code. You basically have a declared model. That's represented by a release, which specifies components such as the Cloud Controller or a MySQL service or an application runtime. And that's given a version and some startup scripts, some lifecycle scripts in the form of a release. And that's combined with a stem cell, which is an IaaS-specific operating system image. So for Amazon or VMware, you might have a different package format around that operating system. It also includes the agent that Bosch talks to and a deployment manifest that basically describes what exactly your whole Cloud Foundry cluster is going to look like, whether it has five cloud controllers at the front of it, whether it provides capability for dozens of MySQL databases. And Bosch takes this declarative information. It goes out to an infrastructure as a service and deploys those resources. And it also goes a little bit further than those other tools in that it manages the lifecycle of the deployed virtual machines. So if one of the virtual machines goes away on a Nova compute cluster, it'll resurrect that declared role for a new virtual machine to make sure that it always matches the number in the deployment manifest. So in the deployment manifest, here's a sample of, as Manuel mentioned, Cloud Foundry's a PAS. So you have the runtimes and services, one of which could be a MySQL service that you deployed out there. Here's a sample basically describing that it is a MySQL database. It's going to provide, in a multi-tenant environment, 100 instances, as well as connection parameters, max size, things like that. And Bosch will go ahead and make sure there's always the fixed number of those, and they're always available to the system. OK, so going on to Docker integration with OpenStack, it gets a little bit less clear. With Cloud Foundry, it's basically the contract is the CPI, the cloud provider interface. With Docker, you have a few options. So the oldest option was actually a Nova Docker driver. So something that actually worked directly with Nova could be plugged in just as you have for KVM, or VMware, or any other compute driver. And it wanted to be able to work with Docker containers as first-class citizens, and essentially work with Glance as well to provide images that you could deploy out to an OpenStack cluster, and of course provide the same interface from the command line tools from Glance and Nova, as well as the Horizon dashboard. There was another alternative that came out, a plug-in. And basically what this lets you do was put containers on top of Nova-running virtual machines. So with this, you could declare entire topologies or larger amounts of linked Docker containers using the actual Docker tools rather than relying on some of the external OpenStack-provided components to do that for you. And that also had very nice integration with Horizon in that you could declare your stack's containers, combine all the resources that he gives for you, and put that into the same user interface. But more recently, there's two new OpenStack projects that have come about, one of which was announced or talked about in detail in Paris, was basically OpenStack-Cola. And the point of this is actually to containerize the OpenStack runtime itself. So what's providing the services in terms of the Nova API, for example, or any of the various components themselves. And to manage these as groups of services, the goal here is instead of working with bare metal or virtual machine primitives, what you're working with are the actual containers. So you get better density, you got quicker deployments, and you have reduced downtime and more atomic upgrades than you would with virtual machines or deploying those in replacement for failover situations, for example. So originally, it was based on Kubernetes. That's what this diagram here reflects. It's moved now towards some of the Docker tools themselves. So Docker Compose, the old fig, is now used to stand up these clusters. And the other OpenStack container project you'll probably have heard of or will hear about in the coming days here is OpenStack Magnum. So there was a containers group that was started up at the Atlanta Summit about a year ago. And there was work at the design sessions in Paris to define what exactly it would look like to make best use of containers in OpenStack. Some people felt that directly managing containers from Nova wasn't the best way to do it. And instead, it was more valuable to provide a framework and rely on other open source projects like Kubernetes or Docker Swarm to actually do the container management on their behalf. So it becomes more of a platform as a service on top of OpenStack, but it also delegates out to other open source projects. So again, integrating with Docker there. And the goal here too is why wouldn't you just do Kubernetes on its own? One of the key features of Magnum is really multi-tenanted clouds. So building on the things that OpenStack does well, the multi-tenant aspects, all the shared identity, and yet being able to create individual clusters within different tenants. And also by being container technology agnostic, not being purely focused on Docker, there's an opportunity to put in Rocket, for example, or even Windows containers in the future. OK. So I'll hand it over to Animesh again to cover the rest of the Docker and Cloud Foundry. Thanks, Daniel. That was a great overview of all the projects which are happening at the intersection of Cloud Foundry and Docker and OpenStack. So what I'm going to talk about right now is what's actually happening at the intersection of Docker and Cloud Foundry. So Manuel did touch a bit on this. For example, the Cloud Foundry developer experience. As you know right now, the way it happens is that you either can go through a CLI, through your favorite IDE like Eclipse or Visual Studio, or even from Browser. You can push an application, and once Cloud Foundry deploys it, you get a URL, and you can access it. Very simple. What's happening under the covers? So once you push your application, it's actually hitting what's called the Cloud Controller within Cloud Foundry. The job of Cloud Controller is actually not only to deploy your application, but also to manage the lifecycle of the deployed application. So in that sense, it's the heart and brain of a Cloud Foundry deployment. And once your application is deployed, the route is registered in the router, and that's what you get back. Now behind the scenes, your application is actually getting deployed on top of VM pools, and it's pushed there. Now these are not just any VMs. I mean, these are specialized VMs called DEA VMs or Droplet Execution Agent VMs. So when your application is pushed, it's actually combined with a runtime. So if it's a Java application, it will be combined with a J2E-based runtime or a Java runtime. And then finally, it's actually deployed in containers running on those DEA VMs. And once your application is deployed in those containers, there is a Health Manager component in Cloud Foundry, which is actually responsible to ensure that your application is up and running, and it does by communicating with messages over the NATS messaging bus. So this is the current architecture of Cloud Foundry. Now the container technology which is used currently is Warden. So there is a Warden server, a container manager, and your containers are actually deployed, which is part of one single system. So this is one way to consume containers within Cloud Foundry. Now there is another way. So as I mentioned, Cloud Foundry is not only a runtime platform, but it's also a platform for services. So essentially, that means that you can actually have services which your applications can consume. And to do that, you need a service broker. So there is a Docker service broker which has been written by one of my great friends, Ferran Rodinas. I don't know whether he's here. He has contributed to the open source community, and it's being heavily used in terms of being able to provision Docker instances. So the way it works is that what you get from a CLI, or a browser, or Eclipse is create a service. It fetches the catalog of the services, selects the service you want to provision. And in this case, there is a Docker service, and it goes and creates Docker instances on that back end. Now that back end could actually be running on OpenStack, and this Docker service broker runs on OpenStack as well. It can also run on VMware. Now just provisioning a service is not sufficient in case of Cloud Foundry. You need to bind these services. So the Docker service broker also provides interfaces to be actually creating bindings between the Docker instances and your apps which are running on top of those DEA pools. So these are the two ways in terms of consuming containers within Cloud Foundry. Now the current Cloud Foundry architecture is being rewritten. So what part is being rewritten? The part which you see here, which is the Vodin server, container manager, the NATS, and health manager. Now why is it being rewritten? So first of all, there is one tight coupling. As I mentioned, Cloud Controller is the heart and brain of Cloud Foundry. So that means all the client interactions go through Cloud Controller, and all the other components also need to interact with Cloud Controller. There are also triangular dependencies between Cloud Controller, health manager, and DEAs. And there are situations where health manager and DEAs can participate and make a decision without communicating with the Cloud Controller, which leads to some inconsistencies. Domain specific. So that means Cloud Foundry is targeted towards apps, apps, and only apps. So it makes it very hard to run something like cron-like jobs or any long-running processes. So that's one of the big limitation in the current model. And last but not the least, the Vodin container technology, which I talked about, is very platform-specific. So that means you can run those custom Linux containers. There is no support for other type of containers. So with that, there is a rewrite happening. And what's the goal of that lealite? To be able to run loosely-coupled, one-off tasks and long-running processes. So instead of thinking in terms of apps, thinking in terms of one-off tasks or long-running processes, which can be run on that back-end, by using generic recipes, which can be spawned and run across various container back-ends. So that means you can not only run the Vodin-based containers, but also Docker containers, as well as Windows-based.net containers. So that back-end, that Vodin is now being rewritten in Go, and that's why the name Garden. So Garden is actually ensuring that it's changing some of the back-end parameters. So with that, let me introduce Diego, which is a distributed system that orchestrates containerized workloads. So if you see the three major components of Diego are a brain, a BBS, or a bulletin board system, and then the Garden back-end, which is comprising of cells, which are actually running your containers. What does brain do? So brain's job is actually to schedule deployments using an auction mechanism. And then once the deployments are done, monitor the health. So it actually runs those one-off tasks. A long-running process is it schedules them to be pushed onto the Garden back-end. Then there is bulletin board system. So the job of the bulletin board system is to maintain and up-to-date cache of the state of the whole Diego cluster. So that means that what all long-running tasks are running? What are the new requests coming? And is it inconsistent with the Cloud Controller, et cetera? And finally, as I talked about, the Garden back-end, which is a rewrite of the whole warden container technology, so as to provide an API-based interface to spawn containers. And then the provider has to implement the back-end, whether it's a Linux warden-based container or a Docker container or a .NET container for those Garden APIs. So this is Diego. Looking a little bit deeper into the Diego architecture, if you see at the very bottom for the brain, there is an auctioneer, the job of which is to run auctions, et cetera, so that it can actually push and find ward cells. It can push those long-running processes or tasks. The whole state of the system, as I mentioned, is being maintained by the BBS or the bulletin board system, which is running on top of HCD. At the very top, you see that there is Rep, which actually participates in these auctions and then makes sure whatever cells it is choosing, the tasks are getting pushed there. And finally, there is an API which has been written to actually interface all these functionalities of the Diego back-end. So currently, and now, so this is lattice, so which is essentially what we are doing here is taking the core Diego back-end and then adding some of the core cloud-forming components back. That means the router is coming back, the dropper or the traffic controller is coming back. So what you are getting here is a system which can stand on its own where you can actually run tasks or long-running processes in a very generic way, not being tied to an app-specific domain, and it will be actually running on containers. So lattice is becoming very popular with the open-source community in terms of being a container orchestration mechanism. It's currently supported for AWS and GAE, and the community is actually making great progress in terms of providing support for OpenStack. So that means that you can actually run lattice on top of OpenStack and spawn containers there. So that's lattice. And if we add back some of the other components of Cloud Foundry, for example, the Cloud Controller and a new component which has been written, which is called the Cloud Controller Bridge, you get the next generation of Cloud Foundry, which is Cloud Foundry v3. Now, why did we need to add a Cloud Controller Bridge? So as I was telling, Cloud Controller was very, very app-specific. So the kind of commands it executes is like stage an app, run an app. Diago, or lattice in this case, is going towards that generic model that run these tasks, run long-running processes. So the job of the Cloud Controller Bridge is to take those app-specific requests and translate it into generic tasks and long-running processes based request, which Diago understands. And with that, you get the same user experience which you had, but with some added capabilities. So essentially, now instead of just having a CF push for an application, you're also getting a way to actually push Docker containers on top of Cloud Foundry, a way to push .NET containers on top of Cloud Foundry. And once they are there, you're getting the same URL. So it's the same user experience, but with some enhanced capabilities. So we talked about Cloud Foundry and OpenStack, OpenStack and Docker, and Docker and Cloud Foundry. Now, how all these different technologies coming together? So as I mentioned, what exists now is there is a Docker service broker, which can run on top of OpenStack, and Cloud Foundry, which can also run on top of OpenStack. And if you make requests to that Docker service broker, it will actually spawn Docker containers if your service backend is being configured on top of Cloud Foundry. So this is what is possible now. What's coming next, based on all the things I was talking about, Lattice, Diago, et cetera, is that the whole rewrite of the component where you will have Docker files in addition to build packs and also the whole Diago pool. So that's one work which is happening. And also, as Daniel mentioned, for example, the OpenStack COLA project, where you can actually run the whole OpenStack inside containers as well. So this is definitely what's coming next. What can be a possible future for this? Now, there are some interest in the community, some work which is going on inside the community in terms of also taking the approach which OpenStack has taken with respect to COLA, and trying to make the whole Cloud Foundry management components also run in Docker containers. So that's something in very incubation stages. There are some experimental projects out there. But that's something which can be future. OpenStack is running in containers. The Cloud Foundry management stack is running in containers. Your apps are being spawned on containers on top of those containers. So that's something which can happen. With that, let me just wrap up by talking about what IBM is doing in terms of bringing all these different technologies together. So as I mentioned, IBM made a big bit last year, $1 million investment in BlueBix, which is a platform as a service offering based on top of Cloud Foundry. Now, when BlueBix started, it started as a public pass platform. But over the course of last year, there are other flavors of BlueBix which are available. And in fact, we are also now going to launch very soon BlueBix which you can run in your data center as well. Now, as we move forward, we also added support from some other capabilities. So not only services which are app-specific, we added support for container service and virtual machine service in BlueBix. So what does that mean? For example, take virtual machine service. So that's something which is being spawned on top of OpenStack under the covers and you're getting OpenStack-based virtual machines. There is also a service which actually interfaces with the OpenStack object storage Swift, and that's exposed in BlueBix as well. Docker Container Service. Again, you can actually go to the BlueBix catalog, request Docker containers, and bind them to your apps. Now, in back end, this is also actually running on top of OpenStack. So this is an uptend from BlueBix in terms of bringing all these different technologies, be it OpenStack, Docker, and CloudFondly together. And as the community evolves, as the CloudFondly matures, you'll be seeing a lot of those capabilities coming in BlueBix as well. So with that, there are a lot of other projects and products within IBM which are centered around these open source technologies. So if you're interested, we'll be uploading these slides. Do go through them. Some of them are doing very exciting work in terms of taking these open source technologies and enhancing them for you to consume in a better way. So with that, we covered what we wanted to cover in the agenda in terms of taking you through the intersection of these different technologies together and also by tying how do they come together. If you have any questions, please bring it up. And I will request Manuel and Dan to come on stage. You can also reach to our Twitter handles, which are mentioned there, if you have any questions later on with respect to that. I think everyone wants to go get their swag. And last but not the least, there is a talk I'm giving tomorrow and our team is giving tomorrow about how to run BlueBix on OpenStack. So if you are interested in building a prediction grade past platform on top of OpenStack, or if you like BlueBix enough and want to see how it can be run on top of OpenStack, do join that. That's tomorrow at 2 PM. Thanks. Thank you. Thank you.


Welcome to JSA TV and JSA podcast the newsroom for telecom and data center professionals. I'm Lauren Oland at JSA. Joining me today is Erin Chenoy, Senior Vice President of Sales and Marketing at ServerFarm. Erin welcome to JSA TV. Thank you for having me Laura. ServerFarm last joined us on JSA TV during PTC. So much has changed since then in the industry and our world. One big change to note for ServerFarm has been the addition to your Toronto data center which you accomplished during the pandemic to keep customers online. Can you tell us more about that Erin? Sure and the Toronto facility was a data center that we acquired just over a year ago and in very typical kind of server farm fashion we took an enterprise facility put in a significant amount of investment in terms of you know modernizing the infrastructure bringing it up to speed but also creating new capacity for additional customer workloads and as you mentioned you know a lot has changed especially in the last four or five months and you know we've had to deal with two kind of very interesting somewhat sort of you know you know sort of counteracting requirements. One has been increased demand from our customers you know clearly they're driving many more of their applications online and some of the applications they have online are growing in terms of demand so they've had to deal with that at the same time we've had to deal with with creating that capacity for them to be able to grow into under what has been you know some pretty challenging you know the kind of construction circumstances in terms of social distancing you know being able to limit the number of people on site and so we started this particular project early on this year and we've just about managed to complete that you know that construction facility off the off the Neutron to data center releasing an additional 14 megawatts of capacity into the market and interestingly of in record time and so despite the pandemic you know we managed to figure out a number of interesting ways of of changing how we you know how we constructed how we how we manage some of the construction and that's you know not that you know notwithstanding the challenge it's been an incredible incredible achievement by the team absolutely an incredible achievement record time during a pandemic that is remarkable and something else to point out I want to talk about the reuse of the existing Toronto facility basically cut embodied carbon by an estimated 75% and that's also remarkable so could you tell us about the HKS report behind that number and then how it applies to server farms entire business model sure sure and actually let me start with the with the sort of business model and I think our model has for a very long time you know almost 20 years now been that you know what we do for our customers is to remove the pain of managing physical infrastructure and you know and that pain exists in the buildings that they own and operate the IT infrastructure that they own and operate the mechanical electrical equipment that you know that supports all of that infrastructure and we've become very very good at taking all of those pieces together and building for our customers you know a picture that allows them to become more efficient and and we do that by solving real estate problems co-location problems and IT operations problems and about seven or eight months ago we conducted a study specifically on our Chicago facility it was HKS that did that report for us because one thing that we wanted to demonstrate to the to the market is that the way that we create capacity in existing facilities is actually the most green you know the most energy efficient the most environmentally efficient way of creating capacity in the market because one thing it allows us to avoid is the building of a new building and when you look at the numbers when you look at the the amount of carbon that is both embodied in terms of the construction of a facility and the operational carbon and we can through the reuse of existing facilities as in the Chicago instance or more specifically in the Toronto facility reduce that embodied carbon by in this instance 75% and just to kind of put a little bit of a different number around that what that basically means is if that if you're a customer and you have a 1 megawatt IT requirement you're going to save about two years of embodied carbon that means that you're effectively going to be in a facility where for the first two years you have no impact on the carbon footprint compared to if you were going to do the same thing in a brand-new facility and so you know in the current context of demand growing very rapidly but also us being you know good stewards of the environment you know that is that is a tough balancing act in the best of times the fact that we're able to do that under such challenging circumstances I think again is a is an amazing testament to you know the quality and the experience of the team. Erin you mentioned green and green power and certainly the data center industry has been talking about sustainability measures like green power so what do you think is the next frontier for data center sustainability? I'd say a couple of things so one is what we just talked about and there is a lot of capacity sitting in existing data centers and I think as an industry it's our responsibility to make sure that we use the existing capacity in the market as efficiently as possible and a lot of that is when I say that I'm in that capacity that I that I mentioned you know you're sitting in enterprise in enterprise facilities so our ability to take those facilities modernize them create capacity in the market and still deliver such an amazing saving from a sustainability perspective is is it's fantastic it's great that we can do that and and we would love to be joined by you know by lots of other companies that you know that can do the same thing but the other thing that's also important is that the IT load also needs to start to become much more efficient and so I think you know 15 or so years ago you know the world moved towards virtualization it then started to move towards the cloud and all of those things have been on the whole extremely good from a sustainability perspective because they're consolidating workloads they're making as many applications as possible run on as little infrastructure as possible and but we also need to do that for applications that can't either be virtualized or can't be moved to the cloud they still have opportunities for for efficiencies to be gained and those efficiently leads lead to better sustainability and one of the things in that area in particular is most organizations are very very good at using space much more quickly than they are at using power and and that unfortunately ties up resources it ties up infrastructure so if we can help our customers which is really what we do every day of the week if we can help our customers become more efficient by using space and power and network and all of the other resources that make up a data center in as balanced a way as possible we can you know we can we can provide more you know more capabilities in terms of achieving better sustainability for our customers and we are just about out of time but where can our viewers go to learn more about the server farm and all that we've talked about today well a couple of places at the server farm website so server farm LLC.com but also follow us on LinkedIn and on Twitter and you'll find us on LinkedIn obviously a server farm and and and on Twitter as well so yep we'd love to love you to join us in the conversation online there we will find you there for short Erin thank you so much for your time today we appreciate it my pleasure thank you very much and thank you viewers for tuning in to JSA TV and JSA podcast happy networking


You all remember that platform that's formally known as Twitter that used to be rife with politically biased censorship. People getting banned left and right by Twitter admins who were totally just trying to combat misinformation. But then Elon Musk took over Twitter for the cool price of $45 billion and promised to make it a free speech platform. But that never really happened, did it. By any possible way that you can measure free speech. It definitely is not a free speech platform as defined in the United States Constitution because Twitter very quickly cracked down on the hilarious parody accounts that started popping up when they were selling verification badges. Satire is implicitly protected by the free expression clause of the First Amendment as long as a reasonable person can distinguish the parody from what's real. And that's held up fairly recently in Supreme Court decisions. So when Rudy Giuliani Esquire tweets that he stands with Kyrie Irving and Kanye West because George Soros pushed him down in the streets and he was left helpless on his back like a turtle an owner of a true free speech platform would probably leave a like on that tweet possibly even share it instead of banning that account and refusing to refund them for that verification badge that they paid for. Anyone who believes that this is real is clearly not very reasonable and probably just has brain rot from too much screen time and should probably consider turning off their computer and becoming Amish for a bit, maybe churn some butter. Twitter also isn't free as in Libre, okay? What we're talking about when we mean free software which is freedom respecting software specifically respecting your freedoms to run, modify, distribute and distribute modified copies of said software. Now, there are some parts of Twitter that are open source, mostly under Apache licenses and also the algorithm is a GPL3 now which is kind of cool even though its GitHub repo is mostly just dedicated to nerds shit posting these days. I mean, seriously, if you're ever having a rough day at the office, just pull up the issues in the pull request tab of Twitter's the algorithm repo and you can have a good laugh. But if these lacks of freedoms weren't enough for you, Twitter also is no longer free as in price. At least it's not free if you want to be able to have more than 1500 posts per month which might be enough for some people, probably not enough for people who are addicts to Twitter. But hey, what's wrong with profiting off of people's addictions?  But you see this profit mindset, it doesn't really live up with the free speech town square model that Elon said Twitter should be when he took it over. But even though Twitter has changed hands and changed philosophies, there's still a lot of people who are treating Twitter like the town square of the internet. They go there to get the latest news about events in the world like the earthquake and tsunamis that have been hitting Japan on the very first day of the new year. So this nerve disaster prevention program, it's dedicated to spreading information about earthquakes, tsunamis, landslides and other natural disasters that occur in Japan. And I think that there's other versions of it for other regions as well. But the whole idea is to propagate this information so that people can get to safe locations and literally save their lives and just take appropriate actions. Information is so valuable and you can see on the first page of their website at nerve.app that this early warning system is also available as a mobile app. But if you take a look at its listings here in Google Play Store, they list that they've only been downloaded about a million times so that people can get those direct notifications in the app. However, on Twitter, their main account has over two million followers. So clearly a lot of people even more across the whole Android market are getting that important information from nerve via Twitter. And I guess I can understand why because a lot more people have the Twitter app installed on their phones already. You know, a lot of people are already using Twitter for their news feed, but that API rate limit, it actually limited nerve's ability to transmit real-time life-saving information to people in a crisis. And it's not even like nerve doesn't pay for Twitter at all. They have a blue check mark, so clearly they're paying for the X Premium subscription, I think is what they call it now, which probably looks really sus to an accountant somewhere in Japan who got that bill for the first time for the government paying for X Premium. But they also pay for the basic Twitter API plan to make automated posting easier. And they get 50,000 posts per month with this plan, but it still wasn't enough. And the cost of a pro API plan jumps up to $5,000 per month, which was too expensive according to nerve statements back in August. This is unfortunately one of the darker examples of what can happen when non-free software is relied upon. Several people have called upon Elon to do something about the rate limits for profiles like nerves. And eventually the issue was resolved towards the end of the day. Nerve got upgraded to a public utility account within X to resolve that API rate limit after employees at Twitter actually started tweeting Elon Musk about it. But that didn't happen until many, many hours after the earthquake hit, after the sea level started to rise, and nerve's rate limit was eventually reached. And we'll probably never know how many people could have been saved and gotten into just better positions.


From San Mateo, it's theCUBE, covering Scalar Innovation Day. Brought to you by Scalar. Hello everyone, I'm John Furrier with theCUBE. We are here in San Mateo, California for a special Innovation Day with Scalar at their headquarters, their new headquarters here. I'm here with Shia Liu, who's the software engineer at the team, good to see you. Thanks for joining me. Hey, thank you, John. So tell us, what do you do here? What kind of programming, what kind of engineering? Sure, so I'm a backend software engineer at Scalar. What I work on from the day-to-day basis is building our highly scalable distributed systems and serving our customers fast queries. What's the future that you're building? Yeah, so one of the projects that I'm working on right now is it will help our infrastructure to move towards a more stateless infrastructure. So the project itself is a metadata storage component and a series of APIs that can tell our backend servers where to find a log file. That might sound really simple, but at the massive scale of ours, it is actually a significant challenge to do it fast and reliably. And getting data is a big challenge. Everyone knows that data is the new oil, data is the gold, whatever the people are saying, these data is super important. You guys have a unique architecture around data ingest. What's so unique about it, do you mind sharing? Of course. So we have a lot of things that we do or don't do uniquely. I would like to start with the ingestion front of things and what we don't do on that front. So we don't do keyword indexing, which most other existing solutions do. By not doing that, not keeping the index files up to date with every single log message that's incoming, we save a lot of time and resource. Actually, from the moment that our customer's applications generate a log line to that log line becoming available for search in Scalar UI, that takes just a couple of seconds. And on other existing solutions, that can take hours. So that's the ingest side. What about the query side? Because you've got ingest, now query. What's that all about? Yeah, of course. Actually, do you mind if we go to Blackboard a little bit? No, let's take a look. Let me grab a chalk real quick. So we have a lot of servers around here. We have Q servers. Let's see. These are Q servers and a lot of back end servers. Just to iterate on the ingestion side a little bit, when logs come in, they will hit one of these Q servers, any one of them. And the Q server will kind of batch the log messages together and then pick one of the back end servers at random and send the batch of logs to them. Any Q can reach any back end servers. And that's how we're able to handle gigs of logs, how much ever log that you give us. We ingest dozens of terabytes of data on a daily basis. And then it is this same farm of back end servers that's kind of helping us on the query front. Our goal is when a query comes in, we summon all of these back end servers at once. We get all of their computation powers, all of their CPU cores to serve this one query. And that is just a massively scalable multi-tenant model. And in my mind is really economies of scale at its best. So scale's huge here. So you got the decoupled back end Q system. But yet they're talking to each other. So what's the impact of the customer? What's some of the order of magnitude scale we're talking about here? Absolutely. So on the log side, we talked about seconds response time from logs being generated until they see the log show up. And on the query side, the median response time of our queries is under 100 millisecond. And we define that response time from the moment the customer hit the return button on their laptop till they see results show up. And more than 90% of our queries return results in under one second. So what's the deployment model for the customer? So I'm a customer, oh, this sounds great. Latency is a huge issue. One of low latency, because latency is really the lag issue for data. Do I buy it as a service? Am I deploying boxes? What does this look like here? Nope, absolutely at all. We are 100 plan cloud native. All of this is actually in our cloud infrastructure and you as a customer, you just start using us as a software as a service. And when you submit a query, all of our backend servers are at your service. And what's best about this model is that as scalars business grows, we will add more backend servers, add more computation power, and you as a customer still get all of that and you don't need to pay us any extra for the increased query speed. What's the customer use case for this? Give an example of who would benefit from this?  Seconds of time might mean millions of revenues to you and you don't want to waste any time on the logging front to debug into your system to look at your monitoring and see where the problem is if you ever have a problem. So we give you a query response time on the magnitude of seconds versus other existing solutions. Maybe you need to wait for minutes anxiously in front of your computer. Shea, what's the unique thing here? This looks like a really good arc. You decoupling things, it makes sense. But what's the secret sauce here? What's the big magic here? Yeah, absolutely. So anyone can kind of do a huge server farm brute force query approach, but the first 80% of a brute force algorithm is easy. It's really the last 20% that's kind of more difficult, challenging, and really differentiates us from the rest of other solutions. So to start with, we make every effort we can to identify and skip the work that we don't have to do. So maybe we can come back to our seats, yeah. Okay, so it's exciting. Yeah, so there are a couple of things we do here to skip the work that we don't have to do. As we always say, the fastest queries are those, we don't even have to run, which is very true. We have this columnar database that we built in-house, highly performant for our use case that can let us only scan the columns that the customer cares about and skip all the rest. And we also build a data structure called bloom filters. And if a query term does not occur in those bloom filters, we can just skip the whole dataset that it represents. So that speed helps on the speed performance. Absolutely, if we don't even have to look at that dataset.  Attracting talent is a big thing, and people love to work on hard problems. What's the hard problem that you guys are solving here? Yeah, absolutely. So we have this huge server farm at our disposal. It's, however, as we always say, the key to brute force algorithms is really to recruit as much force as possible as fast as we can. If you have hundreds, thousands of cores lying around, but you don't have an effective way to summon them around when you need them, then there's no help having them around. One of the most interesting things that my team does is we developed this customized scatter gather algorithm in order to assign the work in a way that faster backend servers will dynamically compensate for slower servers without any prior knowledge, and I just love that. How fast is it gonna get? Well, I have no doubt that we'll one day reach light speed. All right, physics is a good thing, but it's also a bottleneck. Tell us about your story. How did you get into this? Yeah, so I joined Scaler about eight months ago as an API server, actually. Sorry, as an API engineer, actually. So during my API days, I used Scaler to the product very heavily, and it just became increasingly fascinated about the speed at which our query runs, and I was like, I really want to get behind the scene and see what's going on in the backend that gives us such fast queries. So here I am. Two months ago, I switched the backend team. Well, congratulations, and thanks for sharing that insight. Thank you, John, thanks. I'm John Furrier here with Cube Insights Day, an innovation day here in San Mateo. Thanks for watching.


simplest way to change your life is to change your geography. I look back on my life and I was like, I stayed too long in that city. Move. So when I say move, I don't always mean run from your problems because that's another error. I see some people, it just depends on your hormonal and genetic personality type, right?  But some people always running from place to place, that's also another mistake. So I mean, I think that the happy median here is you got to look, you got to have some wisdom and go, am I stuck because of my geography, which is probably about 50% of the time, or am I stuck because of my mental something wrong in my mind, where I'm thinking the grass is greener on the other side. It's easy. It's like a fine line to walk, boy, between those two. I meet people every single day, that should move. That should move. And then I meet other people that should do what my first mentor, Joel Saladin said, which is bloom where you're planted. Like, you're fine. You're in the right place. You're not thriving for another reason.  You have to successfully diagnose what's actually wrong. So, you know, it's easy. It's like Aristotle said, to be angry is easy, but to be angry at the right person at the right time for the right reason, this is difficult. So like to want to move is easy, but to write, to want to move at the right time to the right place for the right reason is more difficult. So, you know, we live in a world of like short form social media, where you get all these quick pieces of advice. But like Albert Einstein said, advice should be simple, but not simpler than it must be. Meaning some things require nuance, you know, some things aren't always an easy answer. So, if you feel stuck, examine, you got to sit down and really think about it.  You must be the physician to your own problems sometimes. Sometimes you bring an outside physician. Sometimes you think about it yourself and you go like, okay, what's actually wrong here? What's actually wrong? Is it my location? Is it actually dragging me down? What will actually be right about the new place that I'm going to? If I move, like right now I'm in Dubai. It's like, do you move? Okay, I was talking to some people that live here in Dubai. What's the pros and cons of Dubai? Well, you got a lot of ambitious people here. What's the downside? I'm overly materialistic, too simplistic of an environment, maybe not as much culture as you would get from a bigger city like London or Berlin or Los Angeles. But walk that fine line between always running from your problems and between being stuck. For sure, changing your geography is one of the quickest hacks to change in your life. So in general, if you're on a fine line, try to move. And good news is you always have to move now. It's pretty easy to go get an Airbnb for a month. Try, test, experiment. I got a private client program where people doing $10 to $100 million pay me to kind of coach them. And for some of them, I'm like, look, man, spend the next 12 months, live in three different places, give it time, experiment before you do a permanent move.  People always ask me, where's the best place to live? Well, Scandinavia. I live there. There are some great things about Scandinavia. Oh, there's some great things about Brazil. I was just there. Oh, I love Sydney, Australia, you know, but you have to have this fine balance between running from your problems to whether you think the grass is greener and actually realizing that you're stuck in the wrong place. Like I said, if you can't figure out which one you are, lean towards changing your geography. In general, I see more people stuck from their geography than not. So like if you're on the borderline, it was pretty hard to tell the difference, move and try for a month. I'm not a big fan of just like trying to change your test your geography by going someplace for like a week or three days. It's not enough. Go for like a month. Then you'll really test your geography. See if it really is a catalyst to flip the switch when you get stuck, you know? So try it. I'm in Dubai. I've tried, man, I've tried 40, 50 countries. You know, there's pros and cons of everyone. I'll report a video where I go deep into the geography of the different, you know, what I think are the pros and cons and you, what you basically want to do is match your inherent weaknesses with the strength of someplace. So for example, let me give you an example. Let's say you inherently lean a little bit toward depression.  Well, I would lean towards changing your geography to a bright place with a lot of sun and a lot of warmth, you know, like San Diego, Dubai. That's a good example of offsetting your weak strengths and weaknesses with a location, locational change. If you're somebody that, you know, doesn't suffer from that, like you're an upbeat extroverted type person, whether it doesn't really affect you.  It's not a big, then you can live in, you know, Norway, Sweden. So Iceland's a cool place. I was just there, volcanoes everywhere. So that's why I said, you've got to be a chess master. A lot of people are like, Ty, what's the checkers advice you have? Simple advice. I'm like, once you become a little more man's life is chess, not checkers, my friend. Deep thinking, deep thinking. By the way, a little survey in the comments. What is the best city in the world? If you only had to pick one, the best city that would help the most people to live in is Dubai. No, let's see. It's a little survey.


We kind of have our tradition that we make our cats boop our hand before we get them their food and I'm gonna show you what that is and what that means. Basically, we ask them just to like jump up and hit our hand, but Thor has been recently doing it. So this is what it looks like, ready?   Bro, I literally just spent so much time making it for you.  You don't like it? Honestly, I knew that was gonna happen because he hasn't really been liking salmon.  They don't need their wet food, but like it's just like a morning treat that I give them. Oh, that was gonna scare you. How did you not get scared? Cause I didn't. You're always scared. Why are you getting me in my- You look like you got a lion's mane going on right now. Yeah, I'm good. You look cute though. All right, so I wanted to talk to you guys really quick and explain what Mariah did to me this morning. So she gets a notification on her phone, right? And I'm like, is that like Uber? Like, what'd you get? And she's like, I didn't get anything, right? And do you wanna explain it?  Someone got us a free order of Star Bob. Cause she had another notification saying, hey, your order's on your way. It's almost here. And I'm like, so you did buy something and she's like, no, that's so cute. Like Uber send us a gift. Like they ordered our Starbucks order and stuff. And I was like, really? Like, they could do that? And then she just started laughing. And that's when I figured out that she kind of pranked me.  I'm like, hmm. And it sounded legit. Oh, it sounded so legit. Go on like this. Who's like this? Like so concerned. You're gonna start talking about, okay, okay. Yeah, she's gonna just start talking. I was coming in here to say that you pull the joke on me. You don't gotta tell them everything that you do to me. Yeah, cause you're global. You wanna tell them all the yelling you do at me too? I'm just kidding. She does it. Mariah, explain to me what is going on here because all I see is. That's actually like you don't know. All I see is money out the door and in these boxes. What is this? A fox for a blanket. Babe, you have to explain what's going on here. You are totally ducking this whole place out. I said, you know what? I want my own room. And I wanna spend more money, right? Stop. You were fine with this. So listen, so I'm basically going to be making this my vanity room. I've been, this is long overdue. I should've done this a long time ago, but I, you know. Lazy. Lazy, yeah. She, this is already her vanity room obviously, but what she like envisioned is she wants to put like a couch in here. Oh, there's a couch coming in. When the girls are chilling because every time like we have people over all the girls are doing their makeup and I swear there's always like three girls in here sitting on kitchen chairs when they should be on a couch.   This is not even it. Like I have a bunch, but we all have to kind of vlog like. Little DIY, right? Like little, like the setup. I wanted to film like setting up the green wall. And. Guys, there's so much more exciting stuff coming for this room. Like we gotta show them a little before and after. Yeah, I'll do it like a little wrap around right now. Okay. There's not even really going to be an after today because not everything's coming in. Well, no, but they'll get, it'll be updated. Yeah, update. Not fully done, but this is what we got going on with the room right now. We're going to move some stuff around. These are our robot vacuums. Obviously, her vanity, which we want to move over here. Nothing on that wall. Nothing on that wall. The cat stuff is right here and we want to put it in the closet right here.  I think it looks better in here. And they're litters over here, but what are you doing, bro? Come here. Come here. Hi, what are you doing? He's not even going to the bathroom. He's literally just like climbing around. What are you doing? Monking in around? We are about to open this. I'm so excited to see what it looks like. Hopefully we have enough. I don't want to like do like the entire wall. I kind of just like want like a half of a wall. I don't think we'll be able to do an entire wall. We would need a lot more than a whole box. I don't want to, I don't want this whole entire wall. I kind of just want like where the vanity's at. I'm just curious to see, because this looks professional if it actually is going to look good when it's on the wall. You know what I mean? Yeah. Like, but look at it. Oh, that's going to look so nice. Maybe we have to get more, so we can make like a backdrop for when we like film. Yeah. Oh, that's going to look so good. That's going to actually fill up a lot of the wall, I feel like. This looks like really good quality. It does look like good quality. Well, I'm actually excited about what it's called. Look at this, just laying them out like that. Like on the wall also guys, I'm getting a sign that says hello gorgeous. And I'm also getting drapes that are going to go right here that says hello gorgeous. I'm going to do this to more of our house. I know. Look at how dope this looks. Look at that. Guys. It really looks like perfect. This is beautiful.  So we are moving my vanity over a little bit. I am getting like shelving units to go on each side because I want to be able to like hang stuff up and put like, you guys can see right there, I got some succulents. Excuse me. There's a lot in here. Just that filled up like, it would fill up a quarter of the wall. That's what I'm saying. Like that's a lot. And we're like halfway through. Okay, Bubs. We might have to kick you out. This is going to look good. We might have to kick you out. You're being annoying. So we're going to move our vanity and actually we're going to move it now. Yeah. And start decorating, but we kind of got to figure out where we're going to place the vanity so we can make sure we've put the wall. Well, we'll just put it back a little bit. Oh, I'm excited. I can't freaking wait. This is so like, I'm impressed guys.  Look how beautiful. It comes with a free cat too, which is totally dope. Like usually most companies don't ship live animals with this one. We didn't show a lot of time-lapse because there was a lot going on and half of it I wasn't filming, but this is how the wall looks right now. It's way more green in person. I don't know if it looks darker on camera, but look at how dope this looks. We were going to buy another one and extend it all the way through, but I have another shelving unit that's going to go up here. So I feel like it's going to lock it in place and it's not going to look, I mean, even just like this, I feel like it looks sick. No, even just like this, because looking at it from here, like look at that. It looks really dope. And we got this off Amazon. If you guys are wondering, it was like a hundred and something dollars for literally all of this greenery. So it came with a lot. It filled up a lot of wall and how we attached it is I actually used double-sided Velcro tape and it held it up really nice. It really does need a lot of stuff to anchor it to the wall. But these are also like, you can put these outside.  I'm just really excited because once I get my Hello Gorgeous neon sign that's going to look so sick, I think the shelving unit they're supposed to come in today. So, so if it comes in today, I'll show you guys, but if not, cause I doesn't really say it's out. We'll see. We'll see how it goes, but we're going to be setting up a lot of other stuff. Mariah obviously has a lot of organizing. She has all these cool plans and things to do. These were all planned to go on my shelving unit. So that's why it's a mess. We'll tidy up a little more in here. Yeah. Then we'll be back. All right guys. So obviously I know the real reason. I'm literally going to my closet for this. I know the real reason why you guys clicked into this video is to see me tell Mariah that I don't want to be with her anymore. I want to be single. I want to go out. I want to, you know, have fun, go to the club and not be tied down to having a girlfriend behind my back. Okay. I just want to be single and I'm going to be telling that right now. I thought this would be a perfect time because we did just finish everything in the room and I am kind of tired from putting everything up because it did take a lot of like work, like, you know, having your arms in the air the whole time. Even though I work out, like I felt that like this is its own little workout. But I'm telling her now because we literally are wrapping up and we just have to wait for other stuff to come. So this is the perfect time in case she gets pissed off or mad or I ruin her mood. At least we got her room done before that happened. But stay tuned. Get ready. Give this video a thumbs up right now because I know you guys are going to love this. And without further ado, let's get back in there before she realizes that I'm talking to you guys and plotting something. Oh, and this is also perfect because last night was Saturday night. I'm filming this on Sunday and I went out without her for like the whole night. I went out with one of my friends and literally like I was single basically that whole night. And I'm going to tell her that last night made me realize that I want to do that more often. That's what's also going to make this really believable. But let's go.  But now they don't really care. Now that it's on the wall, they've just been chilling. It's going to be nice because we are getting that shell so they won't even really be able to get to it which is I'm happy because they would rip that off. No, I know. They literally, they're going to bite on it. I hope they don't climb on it. That's the big thing. I hope they don't figure out that they can climb on it because they do climb. I don't think they will. The shoving unit will kind of eliminate it. Yeah. I'm just going to turn the camera off and we can start filming after we get the room more clean. You want to back him? Yeah. You want to back him? Because I'm kind of organizing my shelving. Are these stuff right now? I know, brother. Want to? What? It's not really. Why? Why does you get that vacuum? You are literally way better than that.  What is this for? Mess up vacuuming? That's for my couch. I got a really cute fuzzy blanket. Oh, so you don't put it up? No. Hold on. I just want to know what my shelving unit's coming in. What do you mean? I don't know what. So you know how I went out yesterday? I went to my friend and we went to all those restaurants. And I know how you weren't there. Obviously, yeah. Oh. Oh, look at this kid in here. Look at him. Look it! Hey, listening? I'm listening. I'm not going to clean your room, but I want to talk to you about something. Right, can you put this away? Here? Oh my god. Why? I'm trying to talk to you. OK, what do you want to talk about? I'm listening. How serious? So serious? OK. We have a Windex in a thing, please. It's totally me. I don't think so. Why? OK, so you know how I went out alone? OK. Well, not alone, but not with you. Yeah. Well, I kind of liked having the ability to be able to do whatever I wanted by myself. OK, what are you getting at? I just want to talk to you, but it kind of felt good to not have to have you by my side every second yesterday. You're not being serious. Because I could kind of do whatever I wanted. So I wasn't really texting you, because I kind of liked it. What do you mean you liked it? You always loved being with me. I felt like I was single.  What, did you see some cute girls last night? No, I literally didn't see any cute girls. I just kind of want to be, like, you know. What do you mean you kind of want to be single? I want to be with you, but I want to be single for a little bit. Does that make sense? No, it doesn't make sense. I know what you're trying to say. So do you know how you had your childhood, not childhood, but you had a lot of fun before we started dating? But I never had that fun in my life. I kind of want to experience that single life. Just for a couple months, a month. We've been dating for five years. You could have had that single life before you met me. We could just take a break, like a temporary break. We're break up, we're not break up, but we take break. So we don't lose everything we have, but I just want to be single. If that's what you want. But we get back together. You don't want to hear something? No, no, but after I have fun, we just get back together. But that's not, no. Do you understand that you basically are admitting to me that you're not actually in love with me and that all everything that you do for me is a lie? I am in love with you, but I want to be single. If you're in love with me, you're not thinking about that. You're thinking about your my future, but all you're thinking about now is being single. So clearly you don't want to marry me. I am in love with you. I just want to be single for, like, a little bit. And then get married after. You want to have single life? Goodbye, because I'm not going to date somebody and marry somebody that's going to one day divorce me because they want to have fun. No, no, I'm not going to divorce you because I'm going to be single now. So by the time we get married, I've already had that experience. Sorry, absolutely not. I just, I feel like I deserve. You deserve? I feel like I deserve this single life. Why do you deserve this single life? No, it's not funny. I don't know why you're laughing. That's not funny. I feel like I deserve to have some fun.  Goodbye. I honestly am hurt. Maybe go to the casino, go to Vegas. The single life. It doesn't have to be all about girls. I just want to be, I don't want to be dating you while I do it.  Okay, this is what we're going to do. This is what we're going to do. This is what we're going to do. That was all just a lie. Are you open, are you open to the suggestion of taking a month break during that month? I am able to do whatever I want. And then afterwards we get back together and we get married. No, no, I'm not up for that. I'm sorry. You want to do that? Peace out, baby. Peace out. I'm not laughing, that's not funny. How is that, how is any of that funny? Have fun? How can I have fun? That's not fun. That's just ignorance. They chill. No, I'm not going to chill. I'm not going to chill. You be single. Go ahead. You know what? I left the camera. You're going to be missing me. You're going to be wishing you didn't do that. You're going to be- I left the camera recording the whole time. It was a joke. I don't believe you. It was a prank. It was, I just want to be single like prank. I don't want to be single. I was just pranking you to see how you would react to me being- We are in such a good day. Why do you have to- Why do you think I did it after we already set up everything?  Like be around you when you're back. Okay. Okay, but no for real.  No, why would you even think that would be an option? I think I'd be fine. No, it wouldn't be fun. I think it'd be fun. Nope. But I get to do whatever I want. And you get to stay here and wait for me. No, no. I like that idea. I don't like that idea. Actually, can we talk about this off camera? Bill, you're just joking. Stop. I'm kidding. I love this girl. Guys, I would never, never leave this girl no matter what. No matter what she does to me, no matter how many times she yells at me being so mean and pinches me. You pinch me.  Oh my God. No matter how many times this girl- This girl what? Just treats me like garbage. You don't even know what you're saying. I love this girl to death and we are going to get married. Good, because if you want her to be single, peace out. I don't want to be single. I don't want to be single. Pay attention to me. I'm not paying attention to you. I don't want to be single. You just pranked me. I'm focused. You know what? This is my healing time. You need to get some WD-40 on this thing. Look at this. I do need some WD-40. Can you get some WD-40? Why is it squeaking like that? Hold on, move around. Oh, it's this. It's right here. Do it again. Yeah, we need to get some D-40 on that because this is not okay.  So how do you feel about getting pranked, babe? I feel fine. More than 10. How good was it? Zero. Where is Team Mariah at? Where has she been? You know where she's been? Clean it.  I don't see you helping me out with my office or like anything that I want to do. Okay, I- What do you want to do? Tell me, what do you want? Be single. I told you what I wanted to do. I don't know why you think that's, why you're laughing, that's not funny. It's kind of funny. Look at these rings. Do you think you're able to clean that? Those are tarnished. Those diamonds are off of that one. Is that the one that I got you? Well, there's no diamonds off of that. Oh, no, they're not in the mind. That thing is- How could you clean? Is that the one that I got you? I think there's a way to clean these. Is that a Panera ring? Yeah. Oh my God. No, Panera. Pandora. I want to be able to clean these. Do you guys have a solution? You don't buy rings or anything from Pandora because that is just trash metal. Like they say that it's going to last, but it doesn't. It gets, like, look it. This is a beautiful Pandora ring. Look at this. Can you guys see actually how nasty this is? Hold on. You can't even tell. I can't even show them because the camera doesn't even- Will those be able to get fixed? I don't know, maybe. They can fix that? I don't know. Marvel Squad has some suggestions on how we can- Suggestions? Suggestions on how we can clean it. Dude, I thought we were just doing like a little haul. Like a little ploy. You just got me in my face. Okay, low key though, filming right here. Mariah, look at this. Look at this angle with the greenery. Oh. That looks sick. That looks fine, guys. I have so much planned for this room. I can't wait to show you guys the final results and what I have planned. Like it's going to look freaking sick. Yes, guys. So far I think we've spent $1,200 between everything for this room, which sounds like a lot of money because it is a lot of money, but it's going to be worth it because just this was like 130 bucks. Then all these succulents and all these, this holder and everything was probably another $100 for all that. And then we got, what, a $300 couch? Yeah. That was like the main price, was the $300, $400 couch. But it's actually turned into a futon, so it turns into like a sofa bed. She could sleep on it. Yeah. But I'm kind of glad. I'm kind of glad we didn't get like another bed in here because now I'm able to kind of like. Now this one's dope. It used to be just a white cube. It used to be a white cube. Now it's kind of like, it has some character in it and dang, this looks so good, man. Like I'm actually like impressed that after you get more signs up, she has this kiss sign that Thor's biting on and probably broke it already. It'll look way better. Now he's a booger, an actual straight booger. But guys, we're probably gonna end the video out right here. We really don't have anything else to do because a lot of her stuff hasn't came in yet. It'll probably either come into the rest of today or tomorrow. They're actually coming in tomorrow, so we can kind of show you guys actually. When's the couch coming in? Tomorrow. Oh it is. So tomorrow we actually have to film, so maybe we can give you guys a little bit of an updated house. We definitely will give you like a quick update of whatever video we do for that because it'll be super sick seeing like the before and after. Because obviously. Maybe it'll do. Oh I have an idea. Tomorrow I could do like a girl talk video in my new studio. It's gonna have to be something juicy. Oh I have a good idea. Stay tuned for the next video because I actually have a really funny idea that I think I've seen someone do it. I think you guys are gonna love it. But once again, thank you so much for watching our videos guys. We really appreciate every single one of you guys that are clicking on here, watching all the videos all the way through. If you made it this far in the video, I want all of you guys to comment down below. Comment down below the word kiss, letter by letter, so we can see who is watching our videos all the way through. And for those of you that actually do, we're gonna pick one of you guys for our next video shout out. Because I wanna start doing more shout outs. We have literally not done shout outs in so long. And we definitely have to get back into that. But we will see you in the next video. But until then. Peace. Love you guys.


So I'm just wrapping up here on Doing the videos and I wanted to give you one last tip that occurred to me while Finishing this and wrapping it up basically a big mistake that I made in the last few years was to just kind of jump from one mentor to another just go from listening to this guy to listening to that guy and My life really started changing. I made like another very big shift in my life when I just hold on Just opening the code oops wrong code I Made a huge difference in my life when I started just following one mentor So what I recommend to you is to just find one person who you deeply trust one person who you can basically get all of your information from who is where you want to be and Only get Information from that person only follow that person because even if multiple people give you really good information It's still not gonna work because you're getting conflicting information So one person is gonna tell you, you know spend a lot of money another person is gonna tell you save your money You're not you're not gonna know what to do. So What you want to do is is follow just one person specifically Do exactly as they say do exactly as they do and You're gonna start seeing massive changes in your life So it all starts with commitment if you commit to just one person read all his materials all his books Buy his courses do whatever it takes to get in front of that person You're gonna see a massive difference in your life Don't go spread yourself out focus on one person that you trust one person You can actually follow and learn from get all the value you possibly can from that person And only when you're as successful as that person when you're so successful that you don't need to learn from them at that point You can actually move on. So that's my last tip for this week I hope you have a great weekend and I'll see you in the next few days


Hey everybody, welcome back to Magic Methodoxy. My name is David and this is a deck review. Hey, today we're going to look at the Arco Tahoe Bags. Arco was once a long time ago, the one of the preferred decks of cards used by professional magicians. Arco has since been taken over by the United States playing card company and they release all of their decks through them. Of course, this is the Tahoe Bag. So sometimes you could have an Arco deck and the back would look different or the tuckies would look different and it's available in both an antique red and a dark blue. Now Dan and Dave, they're the ones that resurrected this design and if you'd like to purchase your own, you can find it at danandave.com. They are, as you can see, a limited number of 2,500 sets in each color. Now the tuck case on the front of this just says Tahoe. It says number 84 poker playing cards and the reason why it would say number 84 is because sometimes on the UPC they would end in that number and so just like the Ryder Bags end in 808 because the end of their UPC ends in 808. The side here says resilient linen finish which is just code for air cushion and on this side it says cartouche club back. So that is how they identified this design. This is the cartouche club back. The top probably said Tahoe there underneath this original tuck seal and then the bottom has some ad copy about the United States playing card company. That is pretty much it for the tuck case. Let's take a look at these cards. So as I said these were printed by the United States playing card company and they are done on their infamous retail stock. Retail stock is thinner than B stock, thinner than Castino stock so it's much more flexible. They also have a modern cut and air cushion finish and if you'd like to learn more about stock cut or finish you can click the link below in the description. So here's a close-up look at the cartouche club back. The Tahoe cards as you can see it's very feathery, very organic shapes, lots of circles and kind of curved edges. It's not as hard or cut as some other more crisp looking decks. This is more of an organic feel but still very pretty. This used to be a connoisseur's vintage playing card set and Dan and Dave are releasing this as a facsimile so you could actually go back and find vintage playing cards that looked exactly like this from a long time ago. They would probably cost you a lot of money. These decks have probably been out of print since 1987 probably when the United States playing card company bought the Chicago printing press that used to make the Tahoe cards and so they've kind of been out of print out of run ever since then. With this deck you're going to get two gaffes. You're going to get a double backer that is both the dark blue on both sides and you're going to get a double backer that is dark blue on one side and antique red on the other. Pretty cool if you want to do a color changing a deck routine. Also with this deck you're going to get two full-size arco jokers. It's just the jester and the jester's cap and costume and it says plastic coated across the top of his hat. This is your Tahoe Ace of Spades. It's a big fat pip there in the center that says Tahoe United States playing card company and made in the USA. All your pips and industry cards should be recognizable and completely standard. You're not going to see any surprises as far as color or pip placement. Your court cards are going to have more of that vintage look because we're trying to do a throwback to it like the cards that was printed a long time ago. They use more of the classic faces and classic colors. Well that is it for the arco deck from Dan and Dave and if you'd like to purchase your own you can head on down to danandave.com. As always we recommend that you like this video just so other people can find it faster. We also recommend that you subscribe to this channel just to see up to date on the showcases in cards and cards magic. Now if you want to follow me on


When I first started in ministry, I remember lying on the floor for hours, and I would pray this prayer with such passion. I would say, God, there's selfishness in me. Please don't promote me until you kill that.