Greetings, good morning. My name is John Mark Walker. I'm the Gluster community leader. I work for Red Hat. With me is Eric Carney. He's one of the OpenStack engineers, also works for Red Hat. We're going to talk today about different ways that Gluster FS can be integrated with OpenStack. We've done a lot of work in the last year, especially on integrating with all the different storage interfaces with OpenStack. From Swift to Sender to Glance. We're going to go through what we've done on all those interfaces, in addition to giving you a little bit of a heads up on some of the road map that we're working on, road map around the Manila project and Savannah specifically. We've done a lot of work. We're really happy with the results so far and so we wanted to share that with you, talk about how it's being used today, what you can do with it, and also I'll give you an example of a real world use case of someone who's using some stuff in production. With that being said, when we started out about, oh so many years ago, in 2006, we had the idea that we came across a lot of different storage solutions that were complex, costly, black box, proprietary solutions sold by vendors who built complexity into their business model so that they could charge more money and keep you locked into their solution. We wanted to do away with all of that. We thought storage should be just like any other application you install on the data center. It should be easy to use, easy to manage, and if you need to, easy to get rid of without destroying your data. If you look at the past 10 to 15 years, the storage market has kind of been lagging the rest of the market because the rest of the market, especially on the compute side, has been going all virtualized, all extracted away from the hardware, all redundant in software solutions, whereas storage kind of took a while to get to that point. It took a while to get to that point because, for very good reason, nobody wants to destroy their data. Virtualization of storage is a scary concept when you're thinking about all the petabytes of data that you have that you don't want to lose. That was our starting point. Over the years, we've built that Glow Surface to be easy to use and install, manage distributed file system that was great for scale out file system storage, for file sharing, essentially. Over the years, and especially in the last two years, we've been adding to that. Not only is it a scale out NAS solution, but it's also something you can use for virtual block storage with the, thanks to the KVM integration that we've done. It's something you can use for object storage, thanks to the Swift integration that we've done. There are lots of things that we've added to the mix now, and I wanted to make sure that everyone's aware of the work that we've been doing and how you can use it. When you think about our core design principles, there are three key ones that we follow when we do anything in GlusterFS. Two of those have been with us since the beginning, and one is fairly recent. When you think about no data silos, I mean, we always had the concept of a global namespace or being able to present a Gluster volume to many different clients, but the idea of no data silos really came about with the addition of multi-protocol support. Up until two years ago, we were exclusively a POSIX compliance shop. It was all about NFS. GlusterFS client was POSIX compliant. I think actually, after a couple of years, was when we added the NFS V3 support, so it was all POSIX-based. Everything was a file from top to bottom, from server to client. Everything was a file and treated as a file and everything was POSIX. Then in the last two years, we added more to the mix. We did the Swift integration. We've done Hadoop HDFS integration. We've done the QMU integration for virtual block storage. We've done all these different things, but we kept the idea that everything should be a global namespace. Everything should be available to all the different avenues of access that you have, and they shouldn't be siloed from each other. It's one of our very key design principles that we follow now. The other design principle was no single point of failure. Again, when we first started back in 2006, we realized that a lot of solutions had a metadata server. At first, we tried to mimic that. We realized that it kind of got in the way. There are two reasons. One is it could limit the scalability, because once you scale it, it would be on a certain point. Metadata servers would tend to fall over or at least lose some of their performance and reliability, but also because metadata servers were a single point of failure. We wanted to have an architecture that didn't have a single point of failure, a share nothing architecture that was redundant and consistent and reliable. Then the third principle we follow is the global namespace. That is, no matter where you deploy GlusterFS, whether it's in a public cloud on AWS or on an open stack cloud or on a virtualized environment or on the guests of a virtualized environment or on the bare metal system, it should look the same and behave the same no matter how you're interacting with it. Every application you use to access it should be able to access the global namespace from multiple methods and access the same data. At our core, we're unified distributed storage system, user space. We don't have any kernel space technology except for on the client side, we do integrate with the fuse kernel module and that's how we do, that's how we mount a file system over a network using the GlusterFS client. But other than that piece, we're a strictly user space. Stackable architecture, we borrowed a lot of design terminology as well as the design architecture from the GNU HURD project. How many of you have heard of GNU HURD? Okay, cool. So one of the contributors to the GNU HURD project was the co-founder of the Gluster project and of Gluster Incorporated AD Periosomy. And so he borrowed a lot of the terminology and the architecture. So we have stackable user space translators where all of our features are implemented. And then ultimately, everything is treated as a file. GlusterFS serves as an overlay, an aggregator that sits on top of disk file systems. And those disk file systems are anything that supports extended attributes. So they could be EXT4, XFS, ButterFS, and almost exclusively on Linux, but anything that supports extended attributes. We also have a maintainer who keeps our ports for NetBSD going. And so it is a portable architecture, but I think pretty much everyone uses Linux these days. So it's kind of, you know, we're kind of in the process of going through, you know, adding functionality to GlusterFS that we didn't have before. And as we do this and as we approach the cloud storage market, we're realizing that, you know, some people tried to use GlusterFS for things that maybe didn't do so well a couple of years ago. And as a result of that, you know, sometimes there's the impression that the things that we're trying to do now may not be so good for. And in truth, you know, maybe a couple of years ago we tried to, maybe we were a little bit too forward thinking, maybe we thought the technology could handle things that it couldn't actually do until we added new things later. But in spite of that, we're now sort of, we have to address the elephant in the room, which is the ghost of Gluster past. And so you can see all these things I've heard at various conferences. I just want to tell you that it's a lot different story now than it was two, three, four years ago. If you look at the differences in the project now compared to then, it's a vastly different architecture, both from a governance model as well as the engineering team to the support, you know, that came with, you know, Red Hat acquiring Gluster Incorporated and adding more engineers to the mix. So the comparison is really stark. And I hope that this slide helps us put it in a bit more relief so that it's easier to see that difference. You know, we've added, you know, it's since the Red Hat acquisition that our engineers started adding in the multi-protocol story. It's when, that's when we started moving to shorter release cycles, where we started taking a more multilateral approach when it came to recruiting developers and organizations to work with the project. You know, before we were required, we were a, what I would call an open core project. We happened to release software and an open source license. But then since then, we've changed and we've made it more inclusive, more of a big tent. And to the point now where our main, our primary, our premier feature in the last version 3.4 was contributed by IBM engineers. So a slide about performance. And this just serves to show you that, you know, we've come a long way in two years. Two years ago, I would not have been able to put this slide up. Now, it says Red Hat storage, but what it really means is Gloucester FS. And you could have said two years ago that, you know, maybe we didn't perform so well in certain workloads. But we've spent a lot of time and effort over the last two years fixing that, fixing bugs, making it perform better so that you can actually use it for a lot more things than you could before.  I can't really say for sure that, you know, every workload is going to behave like this. But I can say, and this kind of serves notice to those who, you know, kind of wanted to write us off. But going forward, I think it's safe to say that, you know, we're pretty competitive. And I'll leave it at that. Whether or not, you know, what kind of performance you see really depends on your workload and your environment and the other variables in the mix. So, but I invite you to compare it. I don't know. I'm sure someone will know. This kind of gives you an overview of the architecture. And I'm just going to give you sort of like the, I'm going to finish giving you kind of a bird's eye view of the project and then we're going to go into more of the open and stacky goodness. But just from an architectural standpoint, again, you can see at the bottom you have your storage servers. A volume encompasses multiple storage servers. And inside of volume are bricks. And the brick in the Gluster nomenclature is any file system that you export or any file system that you want to share. So you can have multiple bricks in a volume. And just like you have multiple servers in a volume. And you present that volume over a variety of ways. You can connect to it via the Gluster Fast Client, which again mounts using the refuse module. About three years ago we added the NFSB3 client, or I'm sorry, we implemented an NFSB3 server. One Gluster FS. And then so NFSB3 clients can connect to it. There's also NFSB4 working on just so you know. And then LibJF API, which is a recently released client library. And that's how we did the QM integration, which is also how we did the NOV integration, which we went into. And that's how we're going to do all future software stack integrations. Any questions about the architecture? And in the same vein, it's kind of just getting an overview of how things connect to each other. On the Gluster Fast server side, you have the volumes that are replicated and distributed. In this particular case, we have a two-way replication. And we have a volume that's distributed over two servers. And then replicated on two more servers. And then you can see the way the clients connect to it. The Gluster Fast native clients, when it connects to a group of Gluster servers, it downloads the translator stack and so it can understand a failover and distributed pathways from the client side. So you don't have to route everything through a single server on the bottom. It can failover to another replica from the client. The same thing with LibJF API, when you integrate LibJF API, same story. The only case where it doesn't apply is with the NFS v3 client because NFS v3 doesn't simply add by definition of the protocol, doesn't have that kind of support. Any questions? Is there an overview of all the different possibilities of interfacing with Gluster FS? You can see on the file side, we've got the Fuse module that works with the client. SMB support via SAMBA exports with the via a recent SAMBA integration. If you're using SAMBA version 4.1 and higher, this integration is baked in. If you're using SAMBA 3.6, we have a project on the Gluster forwards that you can download the source for and compile in Gluster support that way. HDFS, we have a plugin that you can put on the Hadoop server and then it implements the HDFS API, or I guess now it's called the HDFS API, Hadoop compatible file system. And then the NFS piece, which I went over. On the block side, we have an integration with sender and sender via an integration with NOVA will also work with the QMU integration and this is how we do the virtual block storage. On the object side, we have a collaboration with the upstream SWIFT project and we have two committers to the SWIFT project and so we've implemented a pluggable architecture for SWIFT so you can plug in Gluster FS on the back end. And then we have the libJF API, which is the access point for all the software stacks you want to integrate with. On the transport side, we feature IP as well as RDMA support. I think with a previous release on 3.3, it wasn't necessarily the best implementation but it's significantly improved for 3.4 and we have several community members or community guys using Gluster FS with their InfiniBand cards. How many of you use InfiniBand? Okay, is it just me or has InfiniBand gotten really cheap over the last year? It's like, I don't know, I see a lot more of it popping up now. And on the back end, again, everything is a file ultimately but it can be projected as something else. There are a virtual block device which works with the QMU and KVM side and I think there's a DB translator somewhere, although no one really uses it. Some of the features of Gluster FS specifically, there's no metadata server. Again, as I mentioned, our developers decided to take a different route. They weren't file system experts per se, so when they approached the storage problem, they had a different method of solving the scale-out piece of it. And so they decided to, that was faster, instead of having a metadata server where you route all connections to the metadata server and then to the data, they actually created a solution where you calculate a hash based on, excuse me, a hash value based on the file name and the file metadata and then you store that hash inside the extended attributes of the file. That's why we only work with this file systems that support extended attributes. And then we use that hash, we calculate that hash to both read and write the data to look up the location. Multi-protocol access, which I mentioned. Replication synchronous and asynchronous, you can, by default, you can replicate synchronously when you define a volume as a replica or as replicated, by default it's synchronous, but we also have an asynchronous replication piece called Georeplication, it's master-slave. And then as a 3.3, we feature a product of self-healing. And again, when we talk about multi-protocol access, a lot of solutions these days will have or have implemented multi-protocol access, but we really have a unified storage backend that is very unique to GloucesterFS. We don't believe in data silos. We think that if you store files and you store objects, you should be able to access it no matter where you're coming from. And I have an illustration of that coming up in a second. So how do we do all this great stuff?  When you look at that middle translator stack, you know, distribution, replication, that stuff can all live on the client and the server. You know, again, when you connect to a Gloucester volume from the client, the GloucesterFS client reads the volume definition and downloads the translators that are needed to route the data and to implement the features that they're needed for that particular volume. So those translators live and operate on and have to run on both the client and the server. And so when you route the data, when you look at the data path, you see how it goes through the client side and go through the different translator stacks to determine where it's replicated or distributed to. And then you go through the RPC communication and down to the server side and then on down to the local storage on the on the disk drive.  You can remove the translator and you can have, you know, fewer features if you really don't need them. Or there's a great way to build translators. We have a really good API, a solid API in place for many years now for building new features with the translator API stack. What do you generally use it for? Lots of things. We aim for the unstructured data market and that's the one that's expanding by, you know, double. It's a doubling in size every year, pretty much. So all the things that you need to store that require many petabytes that require you to scale out and grow as needed. GlossierFS is intended to be, you know, not just scale out but easily scaled out so that you don't have to pre-allocate how much space you're going to devote to it. If you need to add more data or more space to your storage piece then you can just add more servers to the mix and expand that way. Again, we pride ourselves on the global namespace and being able to behave the same and interact the same with all applications regardless of where they're deployed. You know, whether it's AWS, whether it's an open stack based cloud or as one guess of a hypervisor or bare metal, it should behave the same. You should be able to consistently interact with it with your existing application stacks.  If you look at the top you can see the connection between the Swift client attaching to Glossier Volume and when you see the Swift proxy box there, understand that that is the same proxy server that's used by the Swift project itself. We've been in collaboration with that project to make that proxy server pluggable and so we take their proxy server and then we map it out to Glossier Fests back end and that's how we implemented the Swift API support. But in addition to that, when you access data via the Swift API, you also make that data available to other connection methods, whether it's over in Fests, B3 or SAMBA or some other posits compatible way of interacting such as the Glossier Fests client or other means, it's the same data. So you can actually mount the volume over in Fests and look at and interact with and manage the same data that you're interacting with over the Swift API. So there's a lot of value there if you need to make data available to your existing tool sets and you don't want to rewrite your applications. That's a very powerful feature and conversely if you have a bunch of data sitting in your storage you don't make it available via the Swift API. It's fairly easy to do that as well. The same concept applies to our Hadoop integration. If you have a lot of data that you want to do, be able to do MapReduce jobs on, it's very easy to now make that available to your Hadoop cluster or you can make it so that when you run your MapReduce jobs it stores the data on Glossier Fests servers, thus making that data available to your other analytics toolkits. Any questions? Yes. I could not tell you but there are two engineers sitting here that can address your question after I'm done. The other thing that we've implemented especially with 3.4 and again this feature was contributed by engineers from IBM's Linux Technology Center was the, for the virtualization use case. When you talk about integration with QMU KBM and again this is the basis for the NOVA integration which came as of an open stack Havana. But in this case you can now designate a Gluster protocol assuming you're using QMU 1.3 or higher. It has support natively for the Gluster protocol and you can designate, you can spin up a VM that goes directly to the Gluster volume. And we're able to do this via, there are three layers for this integration. There's a QMU protocol support which was contributed by IBM engineers. There's the block device translator which allows Gluster Fests to present a file as a virtual block device to KBM. And then there's the libJFAPI client library that sits in the middle. We did the client library, IBM contributed the block device translator and the QMU integration. This is a very bad diagram done by one of the engineers of the solution showing you the difference between the standard QMU stack and the Gluster backed QMU stack. And that brings us to the libJFAPI client library. We had started this project a couple of years ago I think with the 3.0 series of releases and then due to resource constraints we had to sort of drop it and then we brought it back when the QMU integration started happening because we realized that if we're going to start seriously dealing with the use case of people managing and hosting VM images on Gluster Fests, we had to do something about latency and this, and I'll show you a diagram in a minute that tells you exactly how it deals with the latency issue. But it's libJFAPI, by using libJFAPI integration, it bypasses the fuse mount and goes directly to the Gluster volume. And so when you look at our standard client, our traditional client, and you look at the number of context switches between user space and kernel space along the data path as it goes from application to, you know, through the networking layer and then down to, then onto on the server side, you can see I think the total number of context switches from user space to kernel space and vice versa is 14 if you count them all up. In contrast, now when you think of random IO use cases, this will kill your latency. And so for things like VM image hosting and management, it's a non-starter once you get beyond a certain number of VMs that you're trying to host. So that's hence the libJFAPI solution. And in comparison, when you integrate with libJFAPI, the number of context switches drops dramatically to I think I think 8 is the final count. So as you can imagine, the latency of this solution is much better than previously. It doesn't mean, by the way, that the Glustrophice client is going away because there's still a need for, you know, general use case file serving, just general purpose mounting over a network. But for particular use cases, this is the preferred method. And now we get to the good stuff. OpenStack integration. So two years ago, we had just started on the Swift integration piece. And that was the only OpenStack integration that we could really do or they claimed to. For everything else in the OpenStack realm, there were, you know, there were glants and I don't think there was Cinder at the time two years ago. But in order to interact with OpenStack, you would essentially just mount the Gluster volume using the Fuse module and you would do all the interaction that way, just as another, you know, path on the file system. But as I mentioned, due to some issues, when you tried, once you tried to scale out down a certain point, latency would go up and it would be, you know, not a good solution for random IO. And so for the last year, we spent a lot of time because we were working on the QMU integration. We also thought, well, since we're going to do that, let's also work on the Cinder integration. Let's implement Gluster protocol support within Cinder directly. Let's, let's get the notice support integration going and make use of the great work that we were doing on the other layers of the stack. And a lot of that is thanks to the gentleman to my left and who will describe in detail what he did with the Cinder drivers. If you look at in the previously released under Grizzly, Grizzly was the first open stack release that featured Gluster support in Cinder, but it was still using the Fuse mount. It was not going to libgfapi. And that's because Grizzly was released before we released libgfapi. I will and it was, I think it was at first it was geared for Gluster FS 3.3 and then then we released 3.4. But the Glance and Cinder integration were both via the Fuse, the Gluster FS client mount. Fast forward to Havana and that has changed because by the time Havana was released, we had released Gluster FS 3.4, which included the QMU integration and we wanted to make sure that the new release of open stack could utilize the new QMU integration. So the Cinder integration was built out a bit further to expand the support and we had the NOV integration which allowed Cinder to make use of the QMU integration. Also with Havana, we finished a lot of the collaboration that we were doing with the Swift client upstream to make it more compatible with what we were using. Previously, like for the beginning two years ago, we kept a series of patches against the Swift release and so it was a real pain to carry those patches forward to every new release.  So we worked a lot more closely with the Swift project and I'm proud to say that collaboration is bearing fruit for both parties. So it's a vote for open source collaboration. Glance integration, thanks to a lot of the new features that have come out with Havana, we don't have to do a lot as far as Glance integration. A lot of that is handled via the Cinder driver now since with Havana, I think the Glance can point to you that the same location is Cinder. And then NOV integration. As I mentioned, we now have NOV integration with the Havana release, which does make use of the work that we did with the KVM and libGF API integration. As I mentioned, we've been very, very happy with the results of all the work that we've done with the Swift project and the Swift developers. It's been useful for both parties. And we spend a lot of time working with them to make Swift pluggable not just for GlusterFest, but also for other storage back-ends so that we can all become Swift API advocates and there can be multiple implementations of Swift and then you use the one that's best for your particular use case. Yeah, as I mentioned, we have two contributors now to the Swift project, two committers. Wait, is this? So why would you do this? Well, I mean, there are a variety of reasons. It's still really early days yet when you start talking about the open source software-defined storage back-ends for virtual machine management, for object storage. And so there's a lot of work to be done yet, but we think we're at a point now where we can start going forward with real-world use cases, which I'll get to at the very end, at least one in particular. And we think it's ready for a bit more usage from the general audience, that for people who want to check it out, I think it can be useful for several workloads now as opposed to previously where I would really only recommend it for one. But in general, you want to look at our modularity, our extensible architecture, the fact that you can add new features via our transit API, or via our LibJAP API client library, if you want to integrate with your particular software. You have multiple choices of transport. You're not just limited to IP. You can also use RDMA. Day-lil CalDate, which came in handy when we implemented the HDFS API on GlusterFS. And then the fact that it's transparent, no matter you can run applications on your storage servers, so you can have the whole storage resident application thing going. And it's easy to manage and maintain. We pride ourselves on the fact that GlusterFS is the easiest to install and get running of any of the distributed file systems. In about four commands, you can have a cluster of four machines running, a distributed, replicated, Gluster volume. And then we'll turn over to Mr. Harney, the gentleman to my left. Any questions about this? Yes. The root file system for the virtual machine is mounted from some Gluster volume. Is that what you mean? Yes. You can do this with sender, boot from volume. So if you're using the sender, GlusterFS driver, the standard boot from volume support will give you that ability. By default, I'm not sure what the distinction is there. OK. Sorry. Without further ado, I'm going to turn it over to Eric Harney. He'll go through some of the details of the implementation. Oh, you might ask you. Yeah. So this is about the GlusterFS sender integration. We have a sender GlusterFS volume driver. It's initially added in grizzly with basic functionality for creating, attaching volumes. Havana has added a number of features, primarily snapshot support for sender volume snapshots, as well as the ability to clone sender volumes, copied to and from Glance images, and the new sender extend volume operation. So this is kind of now a more robust, full-featured sender volume driver that is comparable to most of the other ones in sender. I'm going to go over kind of a summary of how snapshotting actually works. So for clarity here, sender volume versus Gluster volume, there's this is kind of a many-to-one relationship. So a Gluster share can host any number of sender volumes. As a sender Gluster volume is a file on a sender share. And so when we create a snapshot, we are using QCAL2 external snapshots, which basically means you get an additional file that contains your snapshot delta for each snapshot you create. When you delete them, the snapshot is merged into its backing parent in the snapshot chain. One reason this is a little bit different from a lot of sender drivers is that this being a file-based solution, we coordinate with NOVA to create and delete snapshots in the while the VM is running rather than having the storage back in and just do it itself. So when you create a sender GlusterFS snapshot, it actually coordinates through NOVA and tells Libvert and QMU to create a snapshot and handle the manipulation of the snapshot chain. So Havana, as John Mark had mentioned, we also added LibGFAPI support to NOVA. You basically just turn on this one option in NOVA and whenever you attach a sender volume, it will use LibGFAPI to connect to your sender GlusterFS volume so you can get the QMU performance benefits that he had described. The main limitation of this at the moment is that we still need work done to support LibGFAPI with the sender volume snapshots. So for the moment, this is only for full sender volume without snapshots that you can use LibGFAPI. Since we're coordinating with NOVA, no other sender driver currently really works this way. But what we can do is since we're having Libvert and QMU handle snapshot creation for us is going forward, we want to leverage some of the QMU guest agent capabilities that have recently been added to NOVA to try to drive toward guest queuesing for sender volume snapshots. And that's something I'm going to be looking at in the near future. And the other primary sender feature that I want to still add to the GlusterFS driver is the ability to back up GlusterFS backed sender volumes. For those of you that have looked at RDO or pack stack on any Fedora or Red Hat set up, it has options built in to set this up for you. You can basically just set a couple of options. As long as you have the required versions of QMU and GlusterFS which are present in Fedora and coming in REL65 I believe this will basically set up sender GlusterFS integration for you out of the box as a deployment option. And this is for any developers, there's a comparable set of options in DevStack that also will handle the same deployment configuration for you. So I'm going to let John Mark talk about Swift deployment a little more. So as I mentioned, the goal is to have the same Swift client for everything, for whether you're talking about deploying Swift. The traditional Swift deployment or on GlusterFS. But I think as a Havana you still have to install the Gluster Swift package if you want to make use of the Swift API with GlusterFS. I'm thinking that should change for IceHouse but I want to confirm that before I can say for sure. But again, like I mentioned, we are working upstream with the Swift community to enhance the plugability of the Swift client, the Swift API and the Swift proxy server. And also one thing to understand, at least for now, when you deploy Gluster Swift, there is one Gluster volume per tenant. Meaning that when you map out, I think I'm going to go back to the previous slide where I showed the diagram. No, not that one. Yeah, this one. When you look at the way we map the Swift API to GlusterFS, the account container object gets mapped to volume directory and file. So a single tenant goes to a single volume. We know that going forward, that's not something we continue. So we're going to change that. We just have to figure out the implementation details of how we go about that. Moving right along. So on the roadmap, what's in the future? I've told you what you can do now, but what's coming up and I'm very excited about a project to implement files as a service within the OpenStack Camp Pantheon. Right now it's codenamed Manila. There are a bunch of engineers from NetApp and Red Hat working on this. I think a few other companies, I'm not entirely sure who all is working on it. But I'm thinking that one of the, in the design summit, they're trying to make it trying to incubate it for the ICES release. I don't know the status of that. Do you want to say something about the status of that or is there anything to report there? Stand up. A lot more NAS vendors and distributed storage systems, including SAF, are interested in this project. So we would have to figure out what happens on the 19th. Okay. So the status is we don't know yet if it's incubated for IceHouse, but okay, fair enough. But yeah, the whole point is to provide multi-tenant file sharing in an OpenStack context, so you can just load file servers on the go for each tenant. Now you can see the URL there for more details. I think there's actually some code that works. I'm not entirely sure where they are in terms of implementation or how well it works, but it's something that is certainly worth checking out. And it's something we're very excited about, something we're very excited to be contributing to and to be taking some leadership on. In that same vein, as far as incubating projects goes, there's Savannah. How many of you actually use Hadoop for anything? Just want to, okay, fair enough. But it's a collaboration between Red Hat, Morantis, and Hortonworks to make Hadoop be able to scale out with OpenStack, or using OpenStack to scale out Hadoop deployments. This kind of gives you a basic diagram. I don't want to go into too much detail here, but the ability to spin up Hadoop clusters on demand is a really nice feature to have. It's something that, if you're an Amazon user, you have the benefit of elastic MapReduce. This is an attempt to recreate the EMR experience in an OpenStack context. I think it'd be a very powerful thing going forward and sort of shows the flexibility of OpenStack as an app deployment environment for more things than just simply spinning up VMs in a cloud. Then I wanted to go into kind of real world usage. There are, in fact today, there are people using GlusterFS with an OpenStack integration. And the one I want to highlight is Amadeus. Amadeus is, and I didn't know this, I didn't know who Amadeus was until I understood they're using the Gluster Swift integration. But they're a large travel website, apparently very well known globally, but not in American audiences. But they're deploying GlusterFS, they're using the Swift integration that we did. There are many reasons that they went this route. One of them is sort of the ability to, the mapping between the metadata that you store in an object and how that goes into the extended attributes of the file side. So that when you're accessing the data either over a POSIX mount or an object storage layer, you're getting at the different, you're still able to access the metadata that gets stored in the extended attributes. The co-location with other workloads, this gets back to the, for them the node data silos detail, the design principle that we follow is very important to them. It's something that allows them to make data available via the Swift API as well as over a POSIX mount. And you can access it either way. That's something that they was very, one of the reasons why they chose the solution. And they've been using this since the Grisor release and they've been looking at exploring other ways to utilize GlusterFS integrated with other pieces of OpenStack. Yeah, okay. And I'm gonna wrap it up now. Just one final thing I wanted to show you. If you want to start or look at some integration projects in the Gluster community, or one with GlusterFS, go to the Gluster forage. We have a lot of interesting things there that you can find. And it is the central clearing house for developers and users of OpenStack, of Gluster software. Thank you. Do we have time for questions or? Yeah. You know what? I didn't realize that we had actually gone past the allotted time. I thought it was 9.50, but apparently it's 9.40. I apologize. But if you want to talk to me outside, I'm happy to talk to you. I apologize. I didn't realize that we had gone past time. Thank you.


So up to the Hadith of Ibrahim Ibn Hashim When the man that they saw finished his supplication Ibrahim Ibn Hashim or the one Allah Ta'ala alay asked the man which maqam Which holy site were you just at right now? He said the holy site of Prophet Salah alaihi salam or as is known the holy site of the messengers the prophets and The pure souls the awliya and Salahin Now here we are in a different place in the mosque in a different corner in the mosque at the maqam of my master Al-Khidr peace be upon him Al-Khidr we spoke about him. We were in Masjid al-Kufa We said Al-Khidr as per the traditions of the holy household peace be upon them as per Imam Al-Baqr peace be upon him. Imam Al-Baqr says that Khidr Was a pious slave of Allah and the name Al-Khidr was given to him because anything that he would stand on from dry woods or Gray grass or dead grass. He would give life He would make it green again Hence he was given his name Khidr and we said that Al-Khidr is still amongst us today Allah Subhanahu Wa Ta'ala has kept him alive till today and here as well Just like he came to Masjid al-Kufa Al-Khidr peace be upon him knows of the status of this mosque So he came as well to this mosque and he prayed and the narrations tell us as we saw before The narration stated that Al-Khidr in this mosque is the place where he resides It's in this mosque where if he comes on a trip on his camel He places his camel here and then he resides here and then he leaves when he has to leave now The third report the hadith of Ibrahim of Nuhashim is complete now, and we will narrate to you the third report The third report is narrated in the Bihar of Al-Allama al-Majlis.  Ya Aba Muhammad is the Kuniya the nickname that Aba Abasir was given And this is known if you go read the books of Rijal the books of the history and bibliography of the narrators of hadith You will find that this name Aba Muhammad is mentioned when Imam al-Sadr peace be upon him wants to speak to Aba Abasir He talks to him and says ya Aba Muhammad or ya Aba Abasir He says this this narration is very beautiful, and it will put a tear in your eye He says ya Aba Muhammad or father of Muhammad It is as if I see the Qa'in the master Of our time Descend in al-Sahla mosque and take the mosque as a home with his family He says Listen listen my Shi'a. Please listen. He says I see it is as if I see that the Qa'in of al-Muhammad Ajar Allah ta'ala Farid al-Sharif will take this mosque as his place of residence with his family here My master Ruhi law al-Fida will take this mosque as his residence. Now listen he says Aba Muhammad then Aba Abasir responds and he says yabna Rasulullah Oh son of the messenger of Allah. He said it in exclamation He said it will be his residence the Imam said Bala. Yes, it will be so Then the Imam begins to narrate Fada'il and merits of this holy masjid masjid al-Sahla He says this mosque was the resident of Prophet Idris peace be upon him He says and Allah has not sent a prophet Except that he prayed in this mosque because the Maqam down there the Maqam of the Anbiya The Marsaleen and Awliya the prophets the messengers and the pure souls and the successors here Here in this mosque. They all prayed from the Nass from the contextual stamp here placed by Abia Abdullah Ja'far of the Muhammad al-Sadaq. He said Allah subhanahu wa ta'ala has not sent a pure prophet Except that he prayed in this holy mosque.  Please listen to this.  You have a feeling somewhere in your heart He says there is no believing man nor believing woman Except that his heart desires to be in this mosque And there is no night or day that passes except that the angels come to this mosque and By Allah our father of Muhammad Ya, Aba Muhammad if I was in close vicinity as you are in this mosque I would not pray a single Fareeda I would not pray a single prayer be it recommended or be it Wajib except that I pray it here in this holy mosque And when the master of our time my master Imam al-Mahdi al-Muntadar may Allah hasten his reappearance When he comes He says he will rise and take vengeance for all of us His messenger for Allah and for us the ehl al-bayt This is the second. This is sorry the third report The third report narrating you to the falafa da'il and the merits of this holy mosque May Allah subhanahu wa ta'ala grant every believing man and woman that yearns to be in this mosque To come to this mosque and to pray in this mosque and to do all the religious duties of this mosque You see every maqam has a religious duty to do every maqam You pray two units of prayer two raka'a of prayer and you recite and you recite the dua ascribed To the maqam to the holy site Here we stand at the maqam of Prophet khudra alaihi s-salam where he was seen in this mosque Where he still comes this mosque and the prophets or the holy Pious man al khudr because there is difference of opinion on whether he was a prophet or whether he was a pious man We'll say al khudr alaihi s-salam right now in this mosque witnesses me and he sees me right now And I send my salam I say as-salamu alaika Ya khudr as-salamu alaika Peace be upon you or pious man or pious slave of Allah or khudr. Peace be upon you henceforth I ask my master the pious man al khudr alaihi s-salam that you can hear me right now And I ask Allah subhanahu wa ta'ala by your right Or khudr Accept my ziyarah Accept my supplication Accept my prayer will insha Allah recite the dua that is ascribed this holy site with me now my dear viewers We just visited the holy site of my master Imam Areeb al-Husayn al-Sajjah Peace be upon him After finishing By visiting the site of al khudr peace be upon him Here we are now Almost in the middle In the far end of the mosque but in the middle And again we will continue our journey by narrating a couple more merits a couple more narrations And reports concerning the fallah of this mosque So we said so far we have three reports now we will narrate the fourth report The fourth report is a simple yet beautiful report It is narrated by Imam al-Sajjah alaihi s-salam himself Imam al-Sajjah alaihi s-salam says He who prays two units of prayer in the mosque of Sahla Allah subhanahu wa ta'ala will extend his life by two years Simple as that Praying sincerely in this mosque Two units of prayer Allah subhanahu wa ta'ala will increase one's life span by two years The next tradition Since this one was very short We will move to the sixth report Now we narrated before A long report it was found in Bihar al-Anwar Where the Imam peace be upon him Gave some merits of the mosque This is almost the same hadith with almost the same text But a little bit longer I will take out the part that we already have narrated And after that We will continue the hadith So after the Imam narrated the fadail of the mosque as you heard Back in the maqam of al-Khidr peace be upon him Abu Basir asks the Imam a question He says All of this merits for this mosque Imam al-Sadq peace be upon him said Yes, should I give you more? Do you want to hear more? Ya'aba Muhammad He said yes O son of Rasulullah The Imam alaihi salam says This part here is new He says this mosque is amongst the lands that Allah loves To hear the believer's supplication O Shi'a O believing man and believing woman Allah subhanahu wa ta'ala Loves to hear your supplication in this mosque Allah loves to hear the believer's supplication from this mosque And of course there is no night and day With we mentioned There is no night and day Except that the angels descend in this mosque To take blessings and to pray in this mosque Of course, he also states the same as before If I was in close vicinity of this mosque O Abu Basir I would not leave a single prayer Except that I pray it in this mosque Here, Abu Basir asked the same question He says Will the Qaim of al-Muhammad reside here forever?


Tom Scott. That's the name of the guy in the video the other day. I couldn't remember his name on YouTube. The British guy with blonde hair. I was talking about him in this video about the world's shortest river and how definition of river can be different depending on who you ask. But I just watched a video of his on copyright laws, which was a great video. It was very informative. He talked for factual stuff and basically how screwed up the copyright laws are. I figured I talked about it since I talked about free and open source software. Obviously copyrights are an important aspect there. I am not against copyrights. I think copyrights are extremely important. I love licenses like the GPL and without a copyright I couldn't release my software under the GPL because to license something you have to have a copyright on it.   I have a copyright on it immediately and you can't make copies of that. And that is important. Again I write a piece of software. I don't have to go through legal means and paying fees and stuff to get a copyright on it so that I can release it under the GPL. If I don't have a license then someone can take that and close the source and do something else with it. So copyrights are very important, but our copyright laws are very very screwed up. And there are a lot of areas that I don't have answers for. There are some aspects of it that there aren't good answers. But I don't think anybody should get in trouble for watching a movie or listening to a song or looking at a picture. You know I live in America we're supposed to have freedom of speech. I know some people might say that we don't truly have freedom of speech. That's a debatable thing. But to say we have freedom of speech but I can get in trouble for listening to something. I can say whatever I want as long as it's not like a clear and present danger. But I can't listen to a song because it has a copyright and I have to pay to listen to it.  And you know long story short you know there are different licenses out there. And as I said I like the GPL license for software over most other licenses. And the GPL was not designed for art. Although you can apply it to art. It's not really designed for art. But I think there should be licenses that are very similar. And the Crane of Commons is a good example. And there's different aspects in there. And I like some of the Crane of Commons licenses better than others. And some are GPL compliant and others aren't. Or compatible compliant. I don't know I guess compatible would be a better word there. But I personally don't think that. Okay so let me go back. There was a video I did a while ago talking about you know a GPL license which is a distribution license as opposed to a how do you how do people say that the ELUA you know an end user license agreement. So you get a copy of Windows or you know some proprietary software and before you use it you have to click I agree to this big long contract basically. That's different than a GPL. Because that is saying how you can use that software and how you can't use that software. What you can do with it and can't and you're agreeing to it. And it is illegal. I've heard people say oh you know you click yes that doesn't really mean anything. No you're legally agreeing that. And really even if you don't agree to it you're still legally bound by it. Because if I come and install software on your computer and I click yes and then use someone else comes along and uses it. They saw to apply to those conform to those agreements even though they didn't click the button which is very weird. Why is it so important I click the button. You know I guess it's just legal legal stuff saying well they should have known there there was the it was in there. A GPL license and a BSD license and MIT license and an Apache license aren't end user license agreements. My camera just fell off the tripod. But we're not going to stop. We're going to keep going. They are not end user license agreements. What is going on. Okay okay my little holder there is falling apart. They are not end user license agreements. They are distribution license. They say the GPL you can do whatever you want whatever you want with that software. What it's talking about is how you distribute it. Distribute it. So here's a question. Someone creates a piece of software like the Linux kernel under a GPL license. I take that and I make modifications to it. Do I have to share those modifications with the world? If you said yes you are wrong. I do not. I do if I distribute it. If I'm giving a copy of that to someone even if it's binary copies I have to also give them the source code and the changes I made. But if I don't give it to somebody I don't have to and I'm not a lawyer but I don't have to give them the changes I make. I can make my own personal changes keep them in my house. I can man we're going to try to keep going the little rubber grip on my camera tripod just slipped off and that's why the camera is slipping out. Anyway I was on an emotional rant and now I had to stop. So I was saying I can take the Linux kernel I can make changes of it as much as I want and I do not have to share that unless I'm giving you a copy it's about distribution and I think copyrights really should focus more on that rather than use because I should be able to listen to whatever I want. Now if I'm sharing that with somebody I probably have to go buy some guidelines but even though the GPL was not designed for art it was designed for software and as I said you can use it on arts it's kind of a gray area there I think to have a license similar to that for art would be very beneficial. So first of all let's let's stop right there and talk about artists making money. Something Tom Scott said in his video was just a question you know and he was trying to to at least for the first you know two-thirds of that video talk about facts these are the laws not that he agrees with them or whatever but he points out he goes he goes you know you're taking a picture taking a picture and uploading it to your website without permission that that is against the law if you don't have permission to do that and it's violating copyright laws and he said you know you might feel like it's fair you say I'm just putting it up here I'm not making money off it I'm just posting it and he says you know go to a photographer friend of yours and ask them how much they spend on equipment how much they spend you know taking the pictures and how hard it is and all that stuff and I wrote a comment on there none of that matters none of that matters most of you and and some of you maybe artists or some other field that's similar to this but most of us make money in two of main ways most of us make our money in one way we get a job somewhere we do our work and we get paid for that work someone hired us to do that work and we get paid for it or we create something you know some something physical and we sell that and then sometimes it's a little bit of both you're getting paid for making something and then they're selling that product why can't art be the same way so we see a lot of people especially artists obviously and they've worked out the copyright laws and their benefit over this theory that if I don't have a copyright and I can't charge people for for using this music and playing this song well then that I can't make money my question is who hired you who hired you to write that song who hired you to take that picture who hired you to make that video listen I don't do it much anymore but I used to do wedding videos there's always a side thing for me but I do a couple a year and you know what when I first started out I didn't know anything about copyright laws but yeah I'd be like oh yeah you know this is my my my work and you gotta charge and you know I gotta make copies but I only did that for a little bit back in high school I was in JROTC junior ROTC and the last two years I was there and then I actually went back to two years after that I did a CD yearbook for that class I go on the trips with them I take pictures and videos and I put them on a CD and I am guilty of being young and stupid and at least one of those years I had a key that was written on this label of the CD and you need that key was stupid because I I made like three different keys and then I you know so not everyone had the same key but a lot of the keys worked on different ones and it was stupid first of all DRM like that never worked especially the one I did because basically the way this worked was I had an application that displayed the images and basically I had folders of different categories and I just removed the extension they were all jpegs but they didn't have the jpeg extensions jpeg extension so on a windows machine if you looked at those folders they just showed up as miscellaneous files but if you just added .jpeg uh they would they be images so so the the the key would just basically allow you to access the next menu in the software but anyone who copied it to their hard drive renamed the files could view the files it was stupid and it was just stupid that I even tried doing that and most of the time you look at stuff like that companies spend so much time and money trying to put DRM in place and 99.9 percent of the time it doesn't work you know it might slow people down but it also encourages some people a lot of people who go around breaking DRM do it because it's a challenge so it's completely pointless but towards the end of doing that and most of my wedding videos I go I film the wedding I say I film the wedding you will get a copy on DVD if you want me to make extra copies and label them and put them in nice packages and stuff like that I do it for 20 bucks a copy but I would tell people feel free to make as many copies you want and even towards the end I would upload the videos to YouTube for them and be like here you know share it download it why wouldn't I want people to share my work that's just going to get me more business the thing is I already made you know my 800 thousand dollars which is very low for wedding videos most time I was doing it for for friends or friends and friends so so I would do it for I think most weddings I did I did for 800 to a thousand dollars for six hours worth of work and I had down most of my video editing I had scripted out and I could usually edit a wedding video you know that was anywhere from a half an hour to an hour depending on how much happened at the wedding I'd be able to do that in 24 hours and turn around and spit it out to people you know even before that probably taking me a week I've talked to people who who takes over a year to get their wedding videos which is ridiculous thing is I had it down I knew what I was doing I would charge you you want me for six hours it's 800 dollars you want me for eight eight hours it's going to be 1200 dollars or whatever I get paid for doing my work if you want to make copies of it why do I care why would I care I got paid for doing my work and all photographers musicians can be like this I wrote a song did someone pay you to write that song no then you can't complain when people don't pay for doing it you can make money by doing live performances I go to work I go to work and I work 24 hour shifts you you know you whatever you do you work at a grocery store you go to work and you get paid you don't go to work you don't get paid musicians should be the same way well what about artists with the painting of their their their paintings no one hired you to to paint that but you can also sell the painting you made if someone makes a copy it's not the original painting copies of paintings don't make the money that the originals do yeah you could make money off copies but what do you care no one hired you do it you can't complain I usually use the analogy that I came up with and people will criticize this analogy but I think it's a good analogy you know you leave your house you come back someone mowed your lawn while you're gone you didn't hire them but now they're sending you a bill saying I mowed your lawn you're enjoying a mowed lawn because of me you have to pay me that's basically what artists are doing when they when they do that I wrote a song you're enjoying that song you have to pay me I painted this picture I took this photo you're looking at that you have to pay me you know and people will criticize my my my analogy there because it'll be like oh well that's trespassing maybe trespassing well that's a whole another issue but let's just say I mowed I mowed the lawn at public park and now I'm sending people bills for walking through the park well you're enjoying the park I mowed the lawn you should pay me money no if you're an artist you want to make money keep making art find people who like your work if I like a musician I hear their songs and I'm like man I want more music from that guy you know I'll send him you know if he says I'm working on a new album but to do this I need you know to be paid for my time you know I need to raise so much money I'll send him you know depending on how much I like they were from five twenty five dollars you know depending on how much I like the the artists how much I want to hear their music am I getting a cd or am I getting digital download but you can make money like that and the thing is people say oh it's too hard doing you know this this fundraising it's like well it's actually doing work I think it's ridiculous that an artist can spend you know a couple of weeks writing some songs and then expect to get paid for the next 100 years because again you know Tom Scott talks about this and I I know this I'm not a professional on copyrights but I know a lot about them you know you you create something and it's your life plus 70 years and that's not even getting into trademarks because again you you you try to make a Superman cartoon or draw a picture of Superman you know and now you're getting into fair use stuff under certain cases and and fair use is just complete you know BS pardon me but it's BS because because it's all it's all you know a matter of opinion and it may work this time it may not work that time different people argue over what fair use is it's like that should never be your argument and you know when you're going out to decide to do something but but you know basically when it comes down to the whole fair use thing is basically are you making money off it like you could you can can I walk down the street singing a Beatles song yeah I could walk down the street but I record myself doing it and put it up online oh now now I can get sued but either way I'm doing the same thing so uh so going back to the the GPL license it being a distribution license I think it should be the same thing I should be able to to listen to whatever I want look at whatever pictures I want you know but maybe distributing it just distributing it would be the issue you know and uh and in Tom Scott's video he talks about how people are very flip flop it's like if if an individual user uses like a clip from a Marvel movie that's okay but if Marvel was to do it the other way around they would you would throw a fit no I I I think either way so so let's say let's talk about the GPL license versus other licenses like the BSD now this is going to be very controversial long about the sale though this whole video probably is I much prefer the GPL license I think it is a three-year license I think it has less restrictions than the the BSD license and that's where people are going to freak out no the BSD is less less restrictive okay well people say when they mean that uh what people mean when they say that is one of two things either they have no clip of the talking about them they just heard people say that and they don't really understand it but really what it is the the main difference between a GPL license and and there are different BSD license uh but uh one of the BSD license at least um and a lot of these other open source licenses versus free licenses is uh the allow the allowance to to re-license so I create something under a BSD license I put the software under that license someone can take that and then make some changes and compile up and say okay now I'm not sharing the changes that is restriction but people will say that's freeing because you're not restricting people from restricting the software which does not make any sense so and why anybody would release any of their software under a BSD license or some sort of license that allows re-licensing like that uh is beyond me uh it's either because they're planning on screwing you over later by closing it up or they just don't understand it and they think that it's giving them more freedom because they heard that but basically it's just allowing someone else to take what you've created and take it away from you basically because now they've made changes to it and and you don't have access to that going back to the gpl license I create something in gpl license people to make changes but now unless they're keeping it from themselves if it's out in the world at all they are required by law to share those changes and if you do the same thing with your art think about how great that would be marvel's making a big movie you know they want to use your song they can either pay you for a license to use it or the video they use it in the movie they use it they have to release under the same license which is completely free to imagine if all the assets for marvel movies were made public for you to use but then again you know another movie you know company wants to use some of those assets well it's under that license they have to make all of their video free and open meaning that all their assets all their sound clips all the music they use would have to be free and open and this doesn't have anything this doesn't stop people from paying for the stuff I mean why would it because because again do you want to see another adventures movie you're either going to pay for it or you're going to download it for free why does it matter whether it's it's it's free it's it's open or not they say hey we want to make an adventures movie we need a budget you know of one billion dollars whatever it costs to make movies nowadays or at least they claim they make which also adds into it it's like they say the movie costs this much well it probably costs half of that if you could use the assets and sounds and music from other projects without paying for them but that pays back because now all those assets use those people can use what you create and we just get my piles and piles and piles of media that everyone can use and we can all create great things i mean think about how you're creating a video maybe you're making a movie right now and you want to use a song and of course the main one of the main points of tom scott's video uh was how people complain about the the youtube uh content id and and how their copyright things are broke and how really it's not and i i've always kind of agreed with with basically what he said it's like youtube has arranged something so that we can post stuff that has copyrighted material and we the chances of us getting sued are very very low because they can go to youtube and go like hey just give us money or put up an ad and we get the money from that and you may not like that but it's better than them coming and suing you it's a balance there um again what youtube is doing is not great but it's working around a broke system which is basically what tom scott's video is about um but think about the all these you can watch some of these videos on youtube that that are almost as good as big budget movies at least in my opinion um and just think about how much better they could be you know you know some guy on youtube is making these videos and and he does making this great deal but then like the the the models he's using for the 3d stuff just don't look quite right well imagine if you had a bigger selection to choose from his video would look better but then everything he creates someone else can use parts of and of course my big thing is credit you know and when you come to like the um the uh the creative commons license there's different options uh my my videos this video is under creative commons share share like meaning you're allowed to share it but you have to allow people to share uh and and make changes to to what you're making um but attribution attribution is a big thing to me um to me that should even be you know um part of the license that should just be required by law i should be able to use whatever i want my video but i have to give attribution um because if not uh to me that would fall my personal opinion would fall under false advertising if i made a video and i used the song that that i didn't create and i don't credit somebody i'm basically stating in so many words that i created this i wrote this song and i didn't and if i didn't create that i think that should fall under false advertising you know and and think of like millie vanilli it's like they lied about them singing you know some of the younger guys probably don't know millie vanilli is but back early 90s late 80s uh somewhere around there early early 90s i think it was could have been late 80s i was young anyway uh blame it on the rain was their big song they had a couple big songs turns out these two guys weren't singing the song and that happens a lot in the music industry the music videos aren't the people who actually sing the songs at least it happened back then um and the truth is if you're saying these people are singing and they're not i think that's false advertising you can have them sing but in the credits say singer voice this but then visually performed by so-and-so if you want however but you need to word it like that and to me if you don't do that that's false advertising or the very least misleading advertising right so again these are topics that a lot of people are going to have opinions on but i have found whether you agree with me or disagree with me most people uh who argue about copyrights especially people who argue for copyrights do not know anything about copyrights and they just have it in their mind that maybe someday i'll create something i'll become a billionaire or a millionaire and uh one uh that that's just a greedy way to think that and that's a whole another video like people will come up to me and say hey you should make it i have an idea for an app we can make millions yeah you think it's going to be that easy very rarely do you make that type of money without a lot of work um i'll give you an example i have a buddy of mine i won't say his name but he's a very good friend of mine i don't see him very much he lives in another country now and his side job is a magician he's written a few magic books and last time he was in the in the states which was a while ago um he was having me copy some dhs tapes he had to dvd and while we were doing it he was complaining about how uh the books he wrote he found them online that people were pirating them and i hate that term pirating um they were they were pirating and making copies and he's anyone who copies my book and shares with other people should be thrown in jail and here i am copying videos to dvd for him and that's that's kind of i don't know the current state of law on that that's something that's gone kind of back and forth i think current law says if you're making copies for yourself uh to a new type of media or for backup copies that's allowed so the fact that he had these vhs and we're copying dvd because vhs is kind of going out um that's kind of out that's that's been a gray area in the past meanwhile his kids were in the living room watching a cartoon that i downloaded off the internet and i point out to him that they were doing that and oh oh that's okay once something's on tv that that's okay because it's already been aired and they've made their money well no i i downloaded it from the internet and the commercials are cut out so the people who paid them to post those commercials i mean if that's your argument that's a poor argument uh no that's still again you know you can't say oh i think copyright laws are great the way they are except for all the things i do and then his wife uh was sharing cookbook recipes with my wife now you have a food recipe and again i'm not a lawyer but in general you can't copyright a food recipe that is you know three cups flour two cups water two eggs but copyright but when you have a cookbook that they usually have writings and you know this is that and that and this and i used to make this in the summer and then you can't copy that and even if i just printed up a page in my book that just had the list of ingredients and and what to cook it at you can't copy that because again in tom scott's video it makes a great point there are songs like uh canon indeed best name that song right that plays at all the weddings um that song is at a copyright but if you perform it now you have a copyright on that performance which is just stupid i would think you're using this for free what you create with it should be free as well i think it's kind of greedy for you to say well well i took that and i replayed it okay anyway so my buddy's over we're making copies of vhs tapes to dvd which is is legal at least it is now i think again that's a law that's changed in the past um watching show cartoons that we downloaded off the internet and photocopying pages from a cookbook but according to him all three of those are okay well that's that that doesn't count but if someone copies the magic book he wrote they should be thrown in jail according to his words now this guy's very very good friend of mine but screw you buddy you are just being greedy and you know what i think people who think like that should be thrown in jail or at least smacked in the face and and again that guy's a really good friend of mine but i don't care how good a friend you are if you're being an idiot you just serve to be smacked in the face oh little violent on tv or youtube or whatever this is anyway um i've talked for a while this is a passionate topic i try not to talk too much about it i try to to encourage open source software and media through my videos by showing people how it works showing people how to create the stuff and sharing the stuff i create and i would hope you would too so again kind of a long video uh i do recommend checking out tom scott just go just search tom scott um youtube copyright would probably what would be the video comes up it's probably as long as my video it's close to a half an hour long and his is much more informative mine is mostly opinions where his was mostly uh fact um but lots of good examples so uh if you've watched this video this long this is very long for one of my videos i do appreciate you sticking around oh my air conditioner turned off to be quieter now um anyway thanks for watching filmsbychrist.com that's chris the k check it out and as always i hope that you have a great day and i apologize i was trying to make a point to look at the camera rather than the screen uh because i noticed in my last two videos it looked kind of weird that i was looking at the screen but i think it was because i was closer see like this i'm not looking at you it's like i'm looking outside we're here if i look at the camera i'm looking at you hopefully if i'm further back it's less obvious i i apologize if that's weird try to stay further back okay have a great day


Hi everyone, Joe for jaspeyscasebreaks.com coming at you with 2016-17 Panini Select Soccer. One box, random country break number 19. Yes, we're chasing Christian Pulitzer, Christian Ronaldo, Leon Almesi, among others. We go by thisgroupbreakchecklist.com checklist right here, which I will drop to you in the chat if you're watching live. There are the countries right there.  So let's double up your names. There you go. And let's roll it and randomize names and countries five and a four and nine times for each list. One and ninth and final time. We've got Alex down to Rosario. Five and a four and nine times for the countries. One and ninth and final time. After nine, we've got Iceland down to Chile. All right, so Alex with Iceland, Matthew with Montenegro, Robert with Hungary, Matthew with Argentina, Alex with Poland, Matthew with France, Robert with the United States, Ukraine as well. Matthew with Northern Ireland, Robert with the Netherlands, Matthew with Slovenia and Uruguay, Robert with Sweden and Colombia, Alex with the Azurie. Matthew with Austria, Spain, Portugal, Alex with the Côte d'Ivoire, Josh with Germany, Alex with Croatia, Robert with Russia and Brazil. Matthew with Bosnia-Herzegovina, Rosario with England, Robert with Turkey, Alex with Romania, Josh with Belgium, Matthew with El Tri and Ireland, Robert with Wales and Rosario with Chile. Let's get all this on one screen. Any trades? Maybe, maybe not. There's another one box break in the store as well on jaspyscasebreaks.com, so we can run this back and do another one of these tonight. I think people have been in a bit of a soccer mood recently. We've moved a lot of these select soccer boxes lately. Looks like no trade, not even a whisper of a trade, so let's just roll. Let's move on. We've got breaks backed up. TWC trade window closed. Let's print. Let's rip. It's the final printout, hot off the presses. Soccer action this weekend. Premier League action. I think Liverpool is playing Manchester City tomorrow. That should be a fun matchup. All right, let's see what we have in here. There's Neymar in his Barcelona shirt. That'll go to Brazil, Robert. And we've got Marco Verotti for Berry Saint-Germain. He is, I'm not sure what national team he goes to. He is Italian. That'll go to Alex, Alex with that one. There's Diago Silva, Antoine Griezmann. Got a Marcus Rashford there. And we've got Christian Nemeth. Die cut, blue. 10 out of 249. I think he is Hungarian, he is. All right, yeah. There's Ashley Williams for Wales. Yeah, Maradona had some sort of heart surgery or something like that. Blood clot or something crazy. Wales, that'll be for Robert. Marcus Rashford for England. Yeah, I'm surprised that Antoine Griezmann doesn't sell as, I mean, he's a World Cup winner. Played for major clubs.  There's Olivier Giroux for France. Nice, thanks for joining, Chris. If you're new here, always consult the schedule that's pinned in the chat. And Nightbot will often drop the schedule as well. And you'll see if we need to do any fillers for the mixer, all that information there. And if it's sold out, it'll be on the schedule as well. Thanks for joining. There's Lucas Pizzec, the Polish fullback. So that'll go to, excuse me. That'll go to Alex with that one. There's Neymar in orange this time. The 75. And we've got, there's Harry Kane. We've got Iker Casillas, 38 out of 49. Die cut autograph for Spain. Nice, the great Spanish keeper. Matthew Shira with Espana. Nice Casillas. Part of that great run of Spanish teams. A lot of wins in that international, on the international stage. Neymar for Brazil, Robert Runkle. And Luis Suarez for Uruguay. Matthew Shira. That's a nice low number, two, nine out of 10. Do you ever, I thought he was supposed to, he was supposed to be a move made for him. I think I thought Juventus was supposed to go with him but now that move didn't happen. Something crazy happened there. Another Neymar for Robert. And there you go, boys and girls. That's it, that was 2016, 17. Panini Select Soccer. Got another one boxer in the store. I'm Joe for jaspyscasebreaks.com. We'll break that with you next time. Bye bye.


My wife was like, well what's good on the menu, what should I get? And he was like, you should get in the groanie. And I was like, what did you just say to my wife? Whoa. And I realized that this is like on the menu. That's a cocktail? That gotta happen to the Schwarzenegs all the time. Oh my God. Look at how lucky you are.  What? How lucky are they?  What?  I know, I know. Just something happens to the haircut. All right, you're bringing up the Schwarzenegs word. I would never say that guy's full name. Unless you do. I'm sorry about that.