Hi everybody, it's Sam at Mixed Up Craft. Thank you for watching my tutorial today. I'm going to be showing you how to make this really sweet mini album. It's a 10 page mini album but it holds a lot more pictures which I'll show you in a moment. It's just super cute so it's using the binder rings here. It flips up from the top instead of the side so I have used this one here. Let me go out. This is using the My Minds Eye Now this was from last year because this was actually given to me as a gift from Louise at Thompson's Craft Supplies but I will share all the links below for the newer collections that she's got in store now because there are so many fab ones and yeah you should definitely go and check it out. So that's this one basically if I just bring it up here. So these were little kind of pre-cut die cuts and I just popped them on some red and then fussy cut them again just so they kind of are framed and stand out. I've used some flower soft here on the Santa's little present sack there just to give it a bit of texture and I've also used Winkastella on his beard and on the reindeer's little antlers there. Everything's on foam adhesive then I've taken this piece here and I'm just remembering now that I still haven't done it. I'm going to stamp the word Christmas just along here so it will have Merry Christmas but you'll see that in the video in the photos.  So now you have these will all hold six by four photos it's a six by four only I would say photo album but you could certainly make them smaller and things like that and then each one flips down so bring that up there so you can see how that one looks so you'd have one two by all means put a photo here as well but I'm just keeping them plain just to you know enjoy the the lovely papers and then there's also one on the back okay so I've done it so that you've got three photos on each of these but you could certainly have four and use this one as well so you don't have to put pattern paper here you could just have another white one and then you just flip through and that's exactly like they are on every one so it's a really simple one but I think really really nice and for me I love all of the albums out there with all the tuck spots and all the flips and flaps and all that kind of stuff but I like quite basic albums I want to just be able to take the album open it up and see the photos I don't mind little tuck spots or photo mats I like that's about as far as I kind of go and yeah so this is these are my kind of preferred style mini albums so you can see them just going through so there's 10 pages but because this is the binder ring you can certainly add a lot more so you could even double this in size if you wanted to that's the nice thing about using the binder clips it's easy to you know extend and then the back there is done exactly the same way as the front by all means you could decorate that as well so there they are they make beautiful gifts you get a nice gift box one of those kind of MDF boxes and you could cover it in the same papers from the pack obviously these are Christmas themed because these are going to be gifts but you can make these for any you know any year round so any year round any theme all year round that's probably better okay so today I have already gone ahead and done lots and lots of pieces because it is really really really straightforward or just not my camera there we go um yeah it's very very straightforward so I've already done my front but I'm going to go through and do the back with you all so I've already gone and done nine of my pages because you don't need to see me do all them but I did remember when I'd done them all and I've gone and put my whole punches in I forgot to put the decorative strip along here so I'll show you on this one you can see they've all got that decorative strip but after looking at it again it doesn't actually matter it still looks nice either way so I will give you the measurements for the decorative strip but you can see there it still looks nice even though it's plain so those are those nine done and that's my front cover if I bring this one up I just adore this so we've got master polar bear got a little bow all the snowmen and again I fussy cut all of these pieces now this is using the hell's couple ditch um Christmas village collection so I'll be sharing again all the links for that one as well but it is it's just adorable I love you know fussy cutting all the little images and building them all up and you can see there just how nice they look when you kind of mat them so that one's been matted on the red and this one I've matted matted them all on the green and again I'm going to talk you through the corners in a minute but I've already gone ahead and done the front the back's exactly the same it's just obviously not decorated so that's that one these are my corner protectors so I need four of them again I'll share all the links to these ones these are my favorite I just really like the way that they look so I've got the silver for this one and I use the bronzy color for the other one so that's those then I've got my white eyelets which I'll be using and then we can start talking through all of these bits here there's my binder rings these are the a little look here I'm one or three quarter I can't remember what the mill of that is because these ones I believe are sold by the mill so let's have a quick little look here I think it's 45 yeah 45 mil again I'll share all those links for you so I buy these a lot okay so for your pages so you're going to need 10 that's what I'm using but like I said you can double this you know or even have less you might want to add more bulk to yours so this is a piece that is 10 by six and a half and you're just going to score every single one at four and five eighths of an inch okay and then just burnish and fold that in half and you don't want it to meet to the top because this is now where we're going to put our hole punches and then that's our page each one so we just need to add all of our mats and our layers onto that so you will need 10 of those then it's up to you how many white pieces so remember I said you may want to have this as a white piece as well if you do then you're going to need I think it was 30 what did I say you need 30 yeah that's it now so you need 30 white pieces if you want to do it how I've done it and then you'll need 10 of the pattern pieces which is what I put on the front if you don't want to do that then you will need 40 pieces of this so these are four and a quarter by six and a quarter and that's they're going to fit perfectly your four by six photos giving them a nice white frame because you know sometimes you can you can choose to have that white frame put on your photos well this will give you that white frame so like I said these are six and a quarter by four and a quarter and you will either need 30 or 40 of those okay so I'd say the the longest part of this is prepping it all because obviously there's quite a lot of bits that you need to cut out but it's worth it so that's those then if you do want to have the decorative piece obviously that's that one there because I will be finishing it the same your chipboards you'll need two pieces this is five and a half by seven okay so two pieces of chipboard and I am using I think this was the two mil yeah two mil chipboard and this is the trim craft chipboard um sorry this is the dove craft chipboard by trim craft god I've got some mouthfuls to say today again I will share all the links in my blog for you this is a really nice one and it's easy to hole punch through and for your eyelids to fit fit through as well then to decorate your inside so this red piece here and that's also on the back there you'll need two pieces and that is six and three quarters by five and a quarter and then you will need two pieces to decorate the main front and back of your cover and your you know your back cover so I've got this polka dot here and you can see here so I've got the like candy sweets and then I've got that nice stripe on that one so for this one like I said I've got the polka dot and I'm going to have this on the back so it ties in this nice mast polar bear and the to the snowman it's that same paper and I just thought that would match him really nicely so whatever you choose you'll need two pieces and this is nine by seven I've got a little bit cut off there but it doesn't matter because there will be some excess so yeah nine by seven and then if you want to do those strips which I forgot to add I even cut them totally forgot you are going to need 20 pieces because they go on the front and back of each one so there's one there and then one there okay but it is completely optional but you actually do end up having scraps so it was just a nice way to use up those loose pieces but they are so like I said 20 pieces that are three quarters by six and a quarter okay and I'll tell you when you need to stick them down well you you just want to stick them down before you put your whole punches in so they go easy enough okay so get rid of my score box that's everything we need to do there and then what I'm going to do first of all is my back cut back because I've already done my front cover so this is the same you will do this for the same for your front or your back okay and basically what you want to do is cover this I'm going to cover it in double sided tape and also some wet glue because that gives me the wiggle room plus that extra strength as well so you just want to cover your chipboard in the tape I'm just going to rip mine and just try and get them all as close together try not to overlap because you don't want to create any kind of bulk because you might see it through your pattern paper so you do just want to make sure you get them just you know it's close together you can see there that's possible okay and then just start to take off the backing paper here on the tape okay so that's all of the backing and then I've just got some of my glue here and I'm just going to not cover the whole thing but just just enough of it and then you just want to pop it on here just so you've got kind of an equal amount I'm going to go a bit higher just because I've cut that bit it was from where fussy cut because I've been fussy cutting parts of the cover I'm trying to show you yeah and you can see where I was fussy cutting and then I thought oh is it just going to stretch have I got just the right amount and I thought yeah I can do it so flip it over and just carefully just go over with your bone folder just you know make sure you've got no little air bubbles and that's all and because you haven't overlapped the double sided tape you should feel it and it should be nice and smooth okay so just make sure that is really stuck down nicely like so okay now what you want to do then is just kind of fold in the sides so just kind of burnish in the paper just kind of help it along like so and then next what we're going to do is add a strip of double sided tape on all of the outer parts you may want to do two strips depending on how much of your paper you've got see the one's fine there I'm going to have to do two on the sides just because I've got a more overhang there it's just so that it's going to help obviously stick that down you can obviously put it over all of it if you want I'm not going to bother because I'm just going to stick the red piece once we cover that all up just with wet glue okay like so then take off again all of this there we go now there are some people have so many different ways of doing this and I think just over the years this is just my preferred way so what I like to do whenever you're using the chipped board obviously you've got quite a lot of height there so this is the two mil some people use three some some people use one I like to go along with my wet glue and go right along that side piece because that has got enough kind of surface to stick to obviously the paper so it will just help give you a really nice sharp finish on your cover so just go and pop it all along there and you can see if I bring this one in see how nice and flat that is against the side of the chipped board because it's actually been able to stick there okay then next I want to pop some glue along kind of like three sides so come down in the corner like so and then you're going to bring this corner across so you get like a rectangle or a square depending on what size just spread that all out there and then because we put glue inside that bit as well push it down this is why your bone folder is good now because you won't get it all on your fingers don't worry you want to have glue on this bit eventually anyway so just spread it down onto there and all onto this bit I like too much glue I like it to kind of squeeze out the sides because then I know that it's covered everything inside and all of that surface is stuck down so and then I'm just working in and this is how I do all my covers so if you look back at all my previous are linking up here all of my other mini albums this is how I do it so can you see now I've just created the kind of impression of the chipboard underneath there and you just got a really nice you can see how that's finished because now we're going to be folding that over what we will do once we've done the other four corners so again just pop your glue over that kind of area and then bring it over and just kind of stick it down don't worry if it's a little bit out but you want to get make sure you get you know this is a square that's a perfect rectangle you don't want to be too crooked with it but then again if you are it's still easily you know you can still sort it out it's not a problem and again just use your bone folder there like so just really work that in and you can see again there now I've got that really nice finish so I'm just going to do that on the other two I'm going to have to kind of doctor that one a little bit because of the way it's been cut but um just go ahead and get those all done okay so that is my four corners all stuck down and then what we want to do is just pop a little bit of glue along each side do one at a time and just kind of go up on the side first because you've obviously got that surface area and you can see it does stick to it see how it stands up and I just go along there with my bone folder and again just squeeze all that glue out and you can see it kind of coming through there and then go over and stick that piece down again squeeze out any glue and that way now you can see I've got a nice flat side along that chipboard and it looks really good so just go around and do that on all of the other sides okay so that's that all stuck down doesn't matter how it looks I mean everything is perfect apart from where I went a bit funny with the cutting which is there but actually you can't really notice it now it's all going to get covered and the corners are obviously going to get covered she won't see anything but that's the front how nice does that look or in this case it's my back but how lovely is that I love how that's perfect there and you can just see them all really really well so now you can grab this piece and you'll see there what I mean it will stick perfectly I don't want to stick because it will tack to some of that glue so I just want to make sure put this all on first okay and this is what I mean you may want to put double sided tape on there as well but I'm not going to I haven't before so and then just lie it down so you get a nice even border it covers up everything and then even if you don't have corner protectors you've still got really nice corners there they just bring that up okay all nice and concealed so I'm just going to make sure that's all nice and stuck down okay so now while that's just kind of drying a bit more I'm going to bring in one of my pages so you will have 10 of these and then what you want to do is stick down all of those let's get rid of all of this stick down all your mats and also that thinner strip if you want to do it so what I would say first of all is stick down your white ones so they are going to go here so I've got the score line make sure you give yourself the same border that you get on the side so line it up and then just lift up the white and you should have a nice same border so you'll have one there you'll have one there and this one will flip up if you've got a directional pattern paper that will go there just making sure it's facing up the right way then flip it over and that's where your other white one's going to go on the back okay make sure you put the back white one on the folded part not on this part here because obviously that's the wrong bit and like so so now if I bring this over this bit here is where that strip will go and also on the back here that three quarters of an inch one will go in there okay so I'm going to go and get all those stuck down okay so there are my all my mats and layers done there a bit of that off there so you're just going to want to do that on obviously your 10 pieces next we need to do the whole punching so you would have stuck the strips down there if that's what you're doing um again it's entirely up to you where you want to do this you want to grab your front or your back doesn't matter which one and grab one of your pages and basically you want to sit your page and you'll see there you want to make sure that it all oh actually before we do that let's pop these on because it makes it even easier to line everything up so with these you pop them on so you've got the front obviously nicely facing up and then you can push them down so far like so so it kind of just gets into place now I'm being lazy because my hammers actually downstairs but I'm just going to hammer this is these are really really strong actually but they're the banging um excuse the banging one minute okay if I just bring that one up there you can see all the teeth have gone inside the chipboard if I turn that over look how nice it looks on the front so I'm just going to go around and do that on all four of my corners okay so now you can see they are all stuck down all stuck down they're all in place really nicely finished off and you just it again completely conceals all of your edges and corners there so now again grab this grab this and yeah like I said it's entirely up to you where you want to put them so I have already started doing them so I need to make sure they are all lined up with the same ones but attend obviously this one doesn't have the holes punched in it you will just make sure it comes up obviously it's not hanging over the bottom here and it's not hanging over the top there you've got even you know sides it's just needs to be nice and centered like so and then what you would do is with a pencil and a ruler you want to kind of line up where you want to put them so in my case I have this one here is at one two two and three eighths of an inch coming in from that side and then it will need to be two and three eighths of an inch which it just about is from that side as well mark a little cross I'm going to actually do a little dot here going all the way through but you will mark a little cross that's what we're doing I need to do this oh no all I've got to do is that with this one so I'm just going to do that and that okay so imagine they are obviously my crosses then I will grab my hole punch and then you just want to cut through punch through my words mumbled up to them like so and then with that one then you would go over this one pop it all back down in place and then pop your pencil marks inside like so and then get that one and put it on top of your next one and use this as your one that you will trace all of them so you don't need to go and measure each one just use that now and go over all the other nine of your pages okay then obviously get them all hole punched and then this one here I'm going to hole punch as well okay so that's those ones and then grab my my eyelets pop them through that's that one there and just get both of those pressed like so and then I just need to do that on this one here like so so now I have my 10 pages let's get rid of all of that I've got my back which I can now pop there put those other ones on top and then I've got that one going on the front again I'll just show you the front there just so that you've got a bit of inspiration on what to do this was just all die cuts from the same paper pack if you are using a paper pack they may come with pre die cuts like this one did here okay so just have a little look and you may want to do something completely different on the front anyway like lots of flowers and stuff like that but that's it it really is a dead easy album to do and then you just want to grab your binder rings and just thread them through your pages and this was the one and three quarters I think I said but there is room if you did want to add some more and then my front other one like so that one there my rings are a bit closer together but again it doesn't matter it's entirely up to you so let me just give you the measurement so I said that was two and three quarters this one here I came in at no two and a quarter this one was two and three quarters so just shows you there the different looks that you'll get both just as nice but it's entirely up to you and I just love them they make beautiful gifts these are solid you know as long as you've got a good chipboard you're using a good quality you know paper pack that is a solid really lovely well finished gift and there's still plenty of time to make this this honestly doesn't take long to do at all just it's just a lot of cutting all the paper but that's it is very straightforward and then there's lots of online photo printing companies and you can print 45 prints I use a company I can't remember their name I think it's Snapfish or my photo or something I'll share the links but in the UK you can print 45 photos for £1.99 I think it is so again you know it's just it's just a nice inexpensive gift and something that's handmade and yeah my kind of gift so there you go hope you've enjoyed it guys if you have please as always give me a thumbs up and subscribe to my channel so you get to see more thanks for watching bye


USS KID joined USS Pinkney in the search for the missing Malaysia Airlines flight Monday. KID brings the same capabilities as Pinkney, with two search and rescue seahawk helicopters. U.S. Navy ships are working with ships from Malaysia, China, Singapore and other nations in the search effort in the South China Sea. The U.S. Navy has one maritime patrol aircraft, a P3C Orion from the Grey Knights of Patrol Squadron 46, on station flying from Malaysia. I'm extremely confident we'll be able to help. I think of all the platforms out there, we might have the best chance of being able to locate this. The KID and the Pinkney are on deployments to the western Pacific Ocean, conducting training and maritime security operations. From the Defense Media Activity, I'm Petty Officer Jen Blake.


Hello. It's 1.30. It's time to start. Thanks, everyone, for joining. It is Thursday of Summit Week, and by now all the sales people have gone home, so we can talk about how things really work. So what we're going to do today is talk about unified file and object access, being able to write data as an object and be able to read it from the file side. And vice versa, write as a file and consume it from the object side. My name is Bill Owen. I work for IBM in the spectrum scale development area, and I'm responsible for the integration of OpenStack with spectrum scale. I'll be starting the presentation and handing it off to Sumita and Sandeep to go into more of the details of how things work. So what's the session about? We've had a number of sessions at previous summits that talk about Swift on File and that disk file, how it integrates with Swift and the features it provides. What we want to talk about today is some background on that, a little bit of introduction on Swift on File and the use cases, but then look at some of the unique challenges that are still there to make this work in a production environment and talk about our approaches to meeting those challenges. So we'll go through that and then look at the current state of the art as to what we have implemented today and some of the things we're working on. Okay, so what is Unified File and Object Access? I think this may be a review for a lot of people, but again, it's the idea of being able to access my data from the object interface or from the file interface. It shouldn't matter. So on the right, we've got a diagram that shows data coming in as an object, being ingested as an object. It comes into the Swift container and once it's in the Swift container, it can be consumed either from the Swift interface or it can be consumed from the file interface. So we're showing here that item three on the right hand side, the data is read by the file side and that can be NFS, SMB or POSIX. Processing is done and then the object can be written back to the file system and made available to the object interface. If you look at the stack on the right hand side, we've got the at the bottom level a clustered file system. This can be spectrum scale, it can be Gluster, it can be any clustered file system that provides uniform access across all your proxy nodes. On top of that is the Swift software and in particular the Swift on file disk file and then on top of that is the organization within Swift containers and that's the unit that objects are organized in community Swift as well as in the Swift on file. So again, the key points are accessing objects from either interface. It allows the data to be published by as files and then consumed as objects. Also for multi-protocol access, one of the important things is how do I maintain ownership? If I write a file as myself, can I also read it with the same ownership? How is that persisted across both environments? And finally, just the optimization of not having to move data, we think enables a number of interesting use cases. So let's talk about some of those use cases. First of all is the in-place analytics and on the left hand side of the diagram, we've got a traditional object store environment. Data is ingested as objects and then I want to run analytics on that. The way that would work in traditional systems is my analytics software would have to extract the data from the object store using the object interface. So that would be a copy of the data. It moves that copy of the data to its work area, does its processing, and then puts the results back into the object store from the object interface. So a lot of data movement. With Swift on file, again a very similar diagram, the data is ingested from the object interface in exactly the same way. Once it's there though, I can access it directly. Again, no copying of data. I access it directly using the POSIX or file system interface. When I'm done, I can publish my results back into the file system and they can be consumed from the object interface. So ingest from object, process, and then publish through object. The next use case is something we talked about on Tuesday. This is an example of a media house where you've got a number of subsidiaries. Employees from each subsidiary are doing video production, so they're collecting lots of videos for different projects. When they have those collected, they store those in the object store. So they ingest them, subsidiary one, ingests them into its set of accounts or containers. subsidiary two has another set, and it puts it into its account and containers. Once it's there, I need to do something with it. I need to process it, edit it with my video editing software. And typically that's going to be file, expecting file access, written for file access. So we want to make that data available to those file clients. In this example, we're using Manila to publish the shares, export the shares to different VM farms. Once it's there, I can run my video editing software, make my changes, save the data. And I save the data back into the file system. And at that point, I can publish it again through the object interface. One small point I wanted to make here, though, in the first case on the far right, with subsidiary two, I'm publishing the data back into the file system into the same container. And it may be the same file name or it may be a different file name, but it's the same container. In the second subsidiary one case, I'm publishing it back into a different container. So I have that flexibility of how I organize the data. I just need to lay it out in the file system that way. And the objectizer process in Swift will make that available and visible as an object. Last use case is more the individual user style use case. In this situation, I've got two users, John and Rhea, and they want to be able to access their data based on whatever type of device they're using. So if I've got my phone and I'm taking pictures, whether I'm at my house, at my office, or on Simon's boat, I want to take the picture and then upload it to the object store. Once it's in the object store, I want to be able to access it from my workstation or my Windows device or whatever. And again, I need to have a consistent user ID mapping so that I can authenticate to my mobile device with one set of credentials, access it from any other device with the same set of credentials, so I don't have to remember a different user ID and password. And again, the work we're doing is helping to enable that. So with that, I'm going to hand it over to Smita and she'll go into the details. Thank you, Bill. So in the next few slides, we are going to go over design and approaches of implementing this solution. But first, we'll look at what the topmost three challenges are for this kind of an implementation. So what we need to address is the ability of accessing objects from the object interface that have been ingested as files and ability to access files from the file interfaces like NFS, SMB and POSIX that have been ingested by object interface as objects. And the third challenge we need to address is the common user identity across both these protocols, file and object protocols. So what the first requirement is about is it is about accessing objects using file interface, which means objects are ingested from object interfaces like REST API, Swift API, and they need to be accessed using file interface like NFS, SMB and POSIX. So Swift on file has been a good approach for this solution and it is available on GitHub at the given location. Now let's see how actually Swift on file solves this problem. So the biggest advantage of Swift on file is the way it places files on the, it places data on the file system. For example, if an object with name a.jpg has to be put using this URL through an object interface, the way traditional Swift will store it on a file system is something like this. So an object a.jpg is stored as a file named as some random number which is again stored within a directory hierarchy where directories are named as some numbers which doesn't make sense to the end user or a file system user. This of course is determined by ring and Swift services understand this and Swift services know where to find the data on the file system. But to a file system user, this doesn't make sense and hence cannot be used by file protocols. What Swift on file does is it changes this data placement mechanism on the clustered file system. The same URL in case of Swift on file gets stored as this. So an object with name a.jpg gets stored as a file a.jpg on the file system and within a directory hierarchy that has account and container name within it. So from a URL of object put, it can be easily determined what its file system path would be and the same can be used by file interfaces for accessing this data. In IBM spectrum scale, this feature is implemented as a Swift storage policy. So Swift storage policies give flexibility to the administrator to manage unified and file access feature. It gives ability to create multiple such policies for unified file and access depending on the backend storage that you have. It also makes it possible for unified access policy to coexist with your traditional Swift policies and other Swift policies. So a policy basically can be defined at a container level and different containers can be created with different policies, thus giving that flexibility to the administrator. The second requirement we are going to talk about is write a file and read as an object, which means files are written from file interfaces like NFS, SMB and POSIX, which can then be accessed using object interfaces. So do we need anything additional than what Swift on file already provides to make this happen? Well, yes. So we basically have three issues to address for this to make work. A file written from a file interface does not have an entry in the container database, so that doesn't show up in the container listing. Also, container and account stats do not include the data that is written from file interface. And the third issue is that a file written from file interfaces lacks the Swift metadata on it. Now, if there are applications that make use of container listing to get to the object or applications that make use of Swift metadata or container and account stats, they will fail if these three issues are not addressed. And we have a solution for that, which is in three parts. So firstly, you have to identify the changes that are happening from the file side. The second part of the solution is to update the container database with this information that is happening on the file side. And the third part is to actually construct the Swift metadata and associate it with the files extended attribute. So we'll go a level deeper and look at the approaches that we have used to implement this solution. So talking about the first problem of identifying file side changes, the first approach we took was based on file system scans. We first get a list of files from the file system using mechanisms such as OS.Walk or IBM Spectrum Scales policy scans, ILM policy scans. Once we have this file list, we compare it with the container database entries and we get a difference. So the files that are additional in the file list are essentially the files that have been added from the file interfaces. And the missing files in the file list are the ones that have been deleted from file interfaces. So this way we'll be able to identify the changes that are happening from the file side. But this has some issues as well. So one of the biggest issues is that file system scans are resource intensive. Second problem with this kind of an approach is that since these are scans, these need to be run periodically. And when running periodically with some time interval, it doesn't guarantee that the file written from file interface will be immediately made available to the object interface. There is going to be some delay in that. So the second approach for this to solve this issue is event based mechanism, which is kind of a reactive approach. Your service can subscribe to file system events like file create and file delete. There are various mechanisms and tools to subscribe to these kind of events. For example, Linux iNotify or IBM spectrum scales, lightweight events. Now to handle the surge of events in case of peak workload hours, we need to maintain a queue of these events, which can then be later on disposed based on the type of event. Now again, there are some issues with this kind of approach as well. The first issue is that since it's a file system event, you cannot distinguish whether the event occurred as a result of file operation or as a result of object operations. What we are interested is only the events that are happening as a result of file operations. The second issue here is that events may be lost due to reasons like node failures. So in order to handle these issues, in order to handle the event loss issue, we propose a hybrid solution of event based approach as well as policy scan approach or the file system scan approach, where primarily we use event based approach for file change detection, but we also run periodic policy scans with low frequency to identify changes that we may have missed due to lost events. The second problem that we need to tackle is updating the container database with this information that we have just found out. So there are again two ways to do that. In the first implementation, we attempted to do direct database updates on the container database using the container broker service. So Swift provides this container broker service, which has APIs for updating the container database, and we made use of the APIs like object and merge items to update the container database. Again, this had problems of, since this is an API, it runs locally, whereas the file system is clustered. So there could be two object nodes trying to update the same container database path. The second issue here is that since it was, I mean, there could be multiple processes or multiple nodes or multiple threads trying to access or update the same container database at the same time, we were facing DB log time out issues due to the contention. So we moved to the HTTP connect based approach. So HTTP connect method is actually making an HTTP call to the container server, and we are performing a put operation on container server using this method. So what it essentially basically put only for new files and delete for obviously deleted files. So what this is doing is only, since it is a put operation for an object to a container server, it is essentially only doing the part of updating the container database with relevant information. Now here, I mean, this works very well, but we do get failures due to time outs, and we need to handle them by adding those entries that have not been gone through the HTTP request to a sync pending. So in IBM spectrum scale, this is the approach that we are currently using. So I'd hand it over to Sandeep to cover the third requirement of addressing common user identity. Yeah, thanks, thanks, Meeta. So requirement three addressing common user identity across file and object. This particular topic, you can actually have a one day session and still debate and come up with different approaches. If people have talked about how do you do compatibility between SMB, NFS, people working on file system would understand this is a problem or this is an area that you can actually debate and go on and say there are various approaches to do this. So I'll go through of how didn't we approach this. So let's quickly talk about the Swift ACL semantics. So we all know that the object semantics is much different than the file semantics, right? And it goes with, it has to do with the eventual consistency or stronger consistency. It even has to do with authorization and that that's where it goes into identity management. So in Swift ACL semantics, we know it's like keep it simple, Swift ACL enables owners to set and read write access, right? It is all based on the container, right? The point to note is there is no association of user ID and group ID, right? It's a very important concept to understand and realize, especially when you try to have Swift and file work together, right? So no association with UID and GIDs. It's controllable while the HTTP headers, like a lot of us know, and there's a quick example of what a Swift ACL looks like, right? It's like you have a read ACL, here the example shows you have a read ACL for test, test, test a two and a write example where write ACL on test and test a two. It's all on the container, not on the object. I'm speaking about the Swift ACLs, I know S3 ACL is a variation. So the point here on the slide is the one marked in red, that's no association with the user ID and the group ID. Now let's look at the file ACL semantics, right? Now file ACL semantics typically divide into two types. One is the POSIX, right? The RWX, a lot of us have been familiar with the POSIX ACLs and then came the SMB ACLs or the Windows ACL and the NFS V4 ACLs, right? Fundamental differences, NFS V4 ACLs has been more rich in semantics, supports inheritance as compared to POSIX ACLs, etc. So then you see there's a fundamental difference between the Swift ACLs and the, Swift ACLs and the file ACLs. So file ACLs, I'm sorry, so file ACLs, you see they are more granular, granular and comprehensive, right, as compared to object ACLs, supports inheritance, ACLs can be set at both file as well as directory level and ACLs associated with user ID and group ID, right? I'm not going to talk about S3 ACLs, another variation, but just for this particular session we'll concentrate on the Swift ACLs and file ACLs. Now why we are talking about ACLs? Because when we talk about unified file and object, this is one area that someday we have to get it right, right? And as I said, there could be various debates on how do we do this right. But the fundamental of getting the ACL semantics between file ACL and object ACL right is to get the user ID mapping right, right? User ID for the object and the file access. So that is where it comes in need for user ID compatibility, right? So unified file and object, one of the fundamental problems we want to solve is user ID compatibility. So what are the two fundamental problems here? File system stores user ID for file, right? That's what every user who makes a file, he's known by and the file system recognizes it through the user ID. And then you have the Swift which stores all the object as a file, but with the Swift identity, the Swift user, the special Swift user. So cannot leverage existing file-based tools that require correct user ID for the system. So what I mean by that is there are some file systems, spectrum scale for example, that we are referring to here, who have fundamental capabilities like having backup quotas, information, lifecycle management, which become very important for the file-based place, right? And now when you're going to put your object interfaces on that, it's going to be important even for the object-based place. Now all these, when you want to do backup per user, when you want to do ILM per user, information lifecycle management per user, they all are based on the user identity, right? So that's one problem we'll have to solve so that we can start leveraging all these rich feature functionalities that has been developed, a lot of manuals on the file system and leverage it up for a unified file and object. Separate actual storage and semantics for file and object. In the previous two slides we saw that the actual semantics are fundamentally different. Someday we want to make sure how we go and how do we have those both compatible and plus the storage where exactly the actuals are stored in object versus that in file. So these are the two problems. Now in order to achieve compatibility, the first step is to provide an ability to have file user mapping with the Swift users. So you're going to have your Swift users, we need to make sure they get the same IDs as that when they come from the file interfaces. Now again, it's a fundamentally, I mean you're trying to get two different semantics, two different thought processes and trying to say let me merge and get something that will kind of work together. It's a little difficult in the sense that and hence what we did is let's go into the two mode approach. We have mode one, we call it non-unified identity. What it means is that you'll be able to have Swift users and file users access the same data but you're not worried about the user identity. It's more about accessing the data. It touches the use cases that Bill mentioned earlier, the use case one of analytics where you're going to run your analytic jobs using an application ID, you're not much worried about the user ID management, ACLs, et cetera. And then we have the mode two which is unified identity, right? Where you want to have the single OS identity and that's where if you have seen his use case number three and partial use case number two, that's where this will play. So we divided it into mode one and mode two. So what's a mode one, right? So in mode one, what you see is you have an object access, you have object users ingesting object, your file access, you have your file protocols, NFSS, POSIX ingesting file. You have object authentication, you're going to integrate with ADNL app, right? And then file authentication typically will integrate with ADNL app. For this mode, we said, okay, let's keep it flexible. Let's accommodate it. We don't want to get it all stringent and tight. So for this mode, the authentication servers, the ADNL lab are not mandatory, should be the same. They can be flexible. You can have object pointing to your different AD or different L lab. Your file interface is pointing to different ADNL lab. So data created by object API will be available for application via file interfaces. How do you do that?  User app given explicit ACLs. And data created via file interface will be accessible via object API, right? And we need some elevations and Swift user permissions. I'll probably go into details of it in the next slide. So a little bit details. So retaining file ACLs on put and post. So this is a design point. We wanted to keep it consistent, but we have the flexibility based on how the user really wants. So if you have an object put that is happening and there's a file ACL that's associated by default, we retain those file ACLs. They're separate than object ACLs, but we retain so that the file does not shout out saying there's something foul that has happened, right? But if you want to just... And sorry. And object authentication setup is independent of file authentication setup. There's something that I showed in your previous slide. Data created by object API is owned by Swift user. So in this mode, we say let's not change the ownership. Let Swift continue to own whatever he's creating, let the file continue to own whatever the file is creating whenever there's conflict, we'll make sure which one to adhere to based on the user discretion, right? So application processing object data from file interface needs to be required, file ACL to access the data. Again, we touched upon this point. You want to give explicit ACLs. So in this example, what I show is you have a Keystone user, John. He's creating a get put here. I just do a stat on that particular object on Swift on file. You see Swift continues to be the owner and you see John, we have given him explicit ACLs, right? Either you can give explicit ACLs or we can write in middleware, which gives that. So we have both the options. And then here, you created a file using POSIX interface and you see root is owned. At the same time, John has to access it as if it's an object. So there are a couple of ways of doing this. It's really based on your designs, but you could either make sure that every file is created, gets Swift and access, or you elevate Swift permissions using DAC override capabilities, not really making it root, but good enough to access the data. Now let's go to the mode two. Now mode two helps us get towards more tighter integration. That's where we start mandating things. If you're familiar with SMB NFS, for SMB NFS also to work, you need the ID management to be all synchronized and common. So very similarly, here what we would have, sorry, here what you have is, you have an object authentication keystone and you have the file authentication. Both of them, we have to point it to the same ADL or LLAB. And when you point it to the same ADL or LLAB, it's important that every user or group is going to be associated with the UIDs and the GIDs and hence we will have an external ID mapping. And that's why I said common set of object and file users using the same directory services, AD plus RSE 2.3 or 7, a lot of people who play NAS would be familiar with that or an LLAB. Objects created using Swift API will be owned by the user performing the object operation put. That is what we want when Bill creates an object, he will be the owner of the object. You go and do a stat on it, you'll see him as the owner. So again, retaining file ACLs on put and post, we have actually kept it, again, it's flexible, but we retain the existing file ACLs so that the file ACL does not shout it as found. For initial put operations, for the object over nested directories, this is a tricky one, but for the timing, we said, okay, the objects are not going to set any ACLs on the nested directories when they're going to be having nested directories. This example out here which shows you have a keystone user, John, is doing and get input. And when you do a stat, you actually have John as the owner, right? And the Swift user has gone away. So this was a quick overview of what, I mean, in fact, that there are, as I said, it's an half-day design session that you can have on how to do unified ID, mapping between file and object. So with this, I'll actually hand it over to Bill to kind of summarize and wrap this up. Thanks. All right, thanks. Thanks, Zandeep, thanks, Smita. So yeah, we've shown where we're at with this integration, and we've talked a little bit about it, but I'll say it again, our vision is that, ultimately, we have the same level of access from object and from file. We're working towards that. I think there's still some design challenges we have to get through to get there, but that's our vision and that's where we're targeting our development. So the underlying storage that we're using for this is the IBM Spectrum Scale Product. It's an enterprise-class storage platform for enabling software-defined storage. What we do is enable all of the OpenStack storage projects on that, Cinder, Manila, Glance, and Swift. And also, as it shows here, all of the file access protocols are enabled as well, NFS, SMB, HDFS, and POSIX. And it's got a host of other enterprise features that we leverage both from the object side as well as from other OpenStack storage sides, like tiering of data and backup and all kinds of other enterprise features. But what we talked about today, the key points are multi-protocol access, enabling that using Swift on file so that we can have access from the object interface and from the file interface to the same data. No gateways, no copying, it's direct access. So the feature is made available as a storage policy, as Smitha mentioned. So we've got multiple storage policies that can be enabled for your file and object access data, and you can specify different properties on those. So I can have a storage policy that's file and object access and is compressed, or another storage policy that's file and object access and is encrypted, or still another storage policy that is traditional Swift access because I wanna use that layout. So a lot of flexibility in how you lay out your data. Also, as Sandeep mentioned, two different modes for user identity mapping. The first one, I call independent mode, and that's mode one. The second one is unified mode, where we have a shared identity back in, so we have the same user from the file side as well as the object side. And again, the last point I wanna make is just with this approach, we support and allow access for analytics for other file applications from the file interface and then publishing that information from the object interface. All right, many questions that we can answer. Yes, a few questions. First of all, with the Swift deployments in general, it is possible to enable also a replication between several availability zones or data centers. With the Swift on file, do you support similar type of replication between several clusters? With Swift on file, we don't use the Swift replication between clusters. We delegate that to the file system, so there's facilities within spectrum scale that allow us to replicate data between data centers and that's the approach we take. Okay, and you mentioned this special agent that updates container DB if a file is created or modified. So what if somebody creates a directory at the level of container or account? Will it be detected and the new container will be created automatically? Or it's just not supported? How do we handle that? I don't think we support that. I think we just ignore it, but... So if somebody's trying to make deer at the top level, it will fail? So that won't show up as a container from the object interface. Okay, so it will be on the file side, but not on the object. Exactly, one of the constraints is that we require you to create your containers from the object interface and once you've done that, then you can populate them with data. Okay, and do support hierarchical directories so if they go and create several levels of directories, will it appear correctly in the container also? Yes, so you'll have the container name won't be changed, but then the object name will have that path as part of the object name. Thank you. You're welcome. Glad you got that question in. So I had a question about the inherited ACLs. Is that primarily a problem from the NFS type perspective where you don't really know the directory you're accessing? You mentioned that's a future item that's not supported right now. So with the respect to inheritance, we support inheritance when you do file level inheritance. The limitation that we talked about is when you do an object put and you have multiple directories and the object goes right, let's say on the base directory. The fundamental problem if I talk about is the user who comes from NFS, the same user would probably not have an access because he needs access all the way up the directory. So that is in the current implementation, we say, you know what? You need to get access through all because we didn't want to do it from the object side. So that's the current limitation. Do you support SSL on the S3 interface? Yes, yes we do. Okay, so could I talk with somebody about I'm over here? Oh, I'm sorry. Yeah, I'm blinded by the light. Sorry. Thanks. That's fine, yeah. So I have an implementation of spectrum scale object and we've been having some difficulty making SSL work on the S3 interface. Maybe afterwards, could I talk to somebody? Sure, let's talk online. Great, thanks. You bet. So you did a good job of highlighting how it can be very difficult to get the CRUD functions to map up with a POSIC file system. But the S3 and the SWIF API have a lot more features in it, right? We have, you know, SLOs, we have object exploration. How do you marry up those functions, you know, for applications that are taking advantage of more of the S3 and SWIF APIs? Yeah, again, that's kind of a journey. There are certain things that I think won't make sense within the file and object access, like the SLOs and DLOs. But other things like versioning, I think we should be able to support a function for that. So it's kind of a case by case basis. And again, our goal is that ultimately we would have full compatibility of all the SWIF features that are in the normal interface. We'd have support for those from the file side. You showed at the beginning how this kind of solves the problem of data typically being copied from an object store to a file directory or backwards. And then on the previous slide, you just showed that you not only support SMB NFS, but you also support HDFS. So I actually have a customer who's searching for a solution where he can kill two birds with one stone in regards to Hadoop and running analytics on the servers that are also the storage servers for the nodes. Clever Safe, I think used to have some kind of solution for that. Based on what you just showed, would that be a possibility where a server could have a dual purpose as both an analytics node and a GPFS storage or metadata server? Right, that was the use case one that we presented to begin with. Sorry, I didn't catch that. And that's exactly one of the USBs, so. Right, that's one of the value ads that we think we're bringing. Sorry, follow up, but that then, that would eliminate the additional three copies in the standalone Hadoop environment. Yes, we think so. Thank you. So you showed earlier and back to your question about replication that if I have two regions and spectrum scale is doing the replication between the regions, obviously because you're updating the account container nodes, I'm going to do a listing and so if I put a file into region one and it has not replicated over, it's gonna show in the container listing and so now as a user in region two, I'm gonna see that. Now normally because you have the ring is able to fetch across, how do you mitigate that of users seeing objects that don't exist or getting 404s rather waiting for replication? I don't think I gave you a complete answer on the first question. So what we do in that situation is we're using, we're delegating the object replication to the file system but for the account and container databases, we have it configured where that would be done with Swift replication. So you would still have your account and container databases replicated at every region. And that I get. And so now if I put a file in in region one and it has not replicated the spectrum scale because the AC nodes are cross region in region two as a user or a database or a backup application, I'm going to see in the listing that that object exists but when I do a fetch, I'm gonna get a 404. So the way the replication technology works in spectrum scale is when you do the get on that, when I read that from the file system, that's what causes it to be moved to that site. So we would have to deal with timeouts and make sure we have the timeout setting correctly depending on the network between those sites. But when I do the get, it would pull the data from wherever it existed and make sure that it was available to the object server. Oh, okay. So even if it doesn't see the file there, it'll do the fetch. And I'd be able to do like what are the restrictions there because obviously Swift can do high latency. Are we talking 30 millisecond late C50? Is this within a small metro region or could we do this worldwide? We're working on a project with a customer where it's transatlantic or trans-specific. So it can be between geos. Thank you. From the Swift point of view, is it kind of vanilla Swift that you implemented or it's IBM internal implementation? It's vanilla Swift with extensions in disk file and extensions in middleware. So those are the two extension points for Swift and that's what we've been working to make sure we limit our changes to those things. And the Swift on file? Well, Swift on file is another disk file. So we've taken the Swift on file disk file that's in the community, we've made some changes to that so that it's customized for spectrum scale, but it's still just changes within that disk file. Okay, but this is also an open source solution, right? We have not contributed those changes back yet. Okay, but is it something that you're planning to do? Yes, some of the changes. We won't contribute everything back but because some things are very specific to how GPFS works or spectrum scale works, but the things that are general and can be valued in the community, we will contribute back. Thank you. Any other questions? Okay, thank you everybody for joining and have a good rest of the day.


The Holy Spirit manifests his power in many ways yet one of the manifestations I most often asked about is the slain in the spirit phenomenon. Some imagine that it's the power of suggestion while others out of fear accuse me of using demonic power. But this expression of the Holy Spirit's power is a pure life-changing wonder. It's absolutely biblical, breathtaking and beautiful. While having this experience some say they feel intense heat, a heavy weight, shakiness in their bodies and some even experience pulses of electric sensations moving up and down their veins. This same power can be transferred to you right now even as you watch this video. We seek Jesus and sometimes when seeking his presence we can feel his power. I just caution others to be careful about criticizing what you don't understand.


You know a lot of employers will ask a question something like why should I take the risk in hiring you and essentially they've been asking that the entire interview and that this is an opportunity for the student to really think about what are three good reasons to hire me and then to back those reasons up with examples. But they have to keep it brief. For example they might say you know they looked at the job description and being organized is an important quality the employer is looking for. They should bring that up at this point and give them an example that backs the fact up that they are an organized candidate. So give me a couple of reasons a couple of qualities that you have as a student and why it will match my position or why it will match my company. So for example we are looking for supervisors. You're going to be managing people maybe bring something up in your background and say hey I was the manager at this fast food chain I know what it's like to deal with different people I've I know there are different motivations and I feel that that would fit really well in your environment because this will be similar. When we get to that final point you know why should I hire you there are a couple things we're looking for what sets you apart what's your personal brand why you and what we want to see is one you know what your abilities are you're confident in the position and and two you know that you're a good fit that you've done your research on the company and you say you should pick me because I'm offering ABC which I know you're looking for and I like your company vision and mission and and I want to be part of those as well. When I ask a student usually around the end of the interview you know why should I hire you or what I typically say is is there anything else that you would like to tell me that would convince me that you be a good fit with our company that's the opportunity to kind of bring out some of the things that you are particularly proud of that you think that would be a good indicator that you'd be good for the company but you haven't got the chance to really express yet so this is again much like the beginning of the interview that opportunity is yours to basically take it and say here are the things that I really think you know that you should really be focusing in on me about for this company. I think there are a few reasons that I fit really well with your company first of all I am very motivated for example coming to Ohio State I knew I wanted to do accounting and business and worked really hard to get involved in the business school but while here realized my interest in health global health or just health care here in the United States and so I took initiative to get involved volunteering at the hospital joining the health care cluster here at Ohio State I have a project at Nationwide Children's I'm actually working at the hospital as well so combining business with my own passion has really been very beneficial to me and has given me great experiences and opportunity and that's something that I could only have through being self-motivated and really chasing after my passions and dreams and working hard to combine those. I think my motivation would serve me well working for you because I would follow what I am passionate about in the company and would work really hard to get things done the best way possible. Another reason I think that I would be a really good fit for your company is that I am very honest and have a stick to my ethics and integrity for example last year refreshment year Barnes and Noble here charged me twice for an economics book and so I told them that I only bought it once could they please remove the extra charge and they actually remove both charges so I had an economics book that I wasn't paying for and so I emailed them and told them no I really do have one book just not two and so that was a hundred fifteen some dollars that they didn't have charged me but that's what was right so I took care of that with integrity and again I think that really serves well in the corporate world. Also I'm very passionate about community service and I noticed on your website that you have a clean water initiative in the Dominican Republic and I've actually been to the Dominican Republic and I'm very interested in just helping the community and I think I'd really fit well in a company and culture that values that commitment to other people and corporate responsibility and finally I'm very appreciative of diversity that's one thing that Ohio State has really taught me is just diversity is so beneficial and comes in many forms and of course ethnicity and background but also just where someone has grown up or different ideas and I've traveled through classes at Ohio State to Mexico and London and Greece and really enjoyed the diverse culture there and I've also been an English conversation partner talking to some Chinese students and helping them improve their English and learning about their culture and I just really enjoyed learning about other people's culture and backgrounds and I know your company is well recognized for its diversity and I would really enjoy accepting that and working to maximize the opportunities that come from diversity so in summary I would say my motivation and integrity and community service and diversity interests would make me a good fit for your company. Thank you very much. The interview candidate did several things well when providing reasons why she should be hired for the position. First the interview candidate provides qualities and skills along with values that prove she is the right person for the job. Second she provides an example to support each reason why she's a good match for the job. Third the candidate explains her fit with the company's culture by explaining how she shares some of the same values around community service and diversity as her potential employer. Finally she helps the interviewer remember her main points by summarizing her answer. The only way to improve this answer would be to shorten it by focusing on three reasons she should be hired rather than four. Plus she could be more direct in sharing her supporting examples when backing up her reasons to be hired.


Smart goals, how to set and achieve your goals. Hey, have you been having a difficult time setting and actually achieving goals? Well, in this video, we're gonna fix that. I'm gonna give you a method that you can use that will help you immediately set the right goals and achieve them and we're starting right now. Hey, I'm JR Fisher. Thank you for watching this video. I appreciate you visiting my channel. And don't forget to subscribe. There's a big subscribe button down there. Make sure you hit that button and then turn on all bell notifications, okay? When you turn on all bell notifications, you will be notified every time I do a new video. And when I go live, you'll be part of the Fisher family, the VIP group that gets in front of the line. Okay, so let's jump right into this. But before I do, I wanna remind you that there is a course below, $97 course. You can get it for zero, absolutely free. All you have to do is click the link and learn. There's no credit card required. Now, I wanna read for you a quote from Bill Copeland. He says, the trouble with not having a goal is that you spend your life running up and down the field and you never score. Do you ever feel like that?  Well, this video is gonna fix that for you. Now, I've been selling online since 2009. I've sold millions of dollars of both digital and physical products. And I'll tell you, setting up goals, looking at where you've achieved things, where you need to work on things. This is something I do on a regular basis and you have to too, but you gotta have a system. So that's what I'm gonna give you in this video. You have the system. Once you have the system, it'll be easy. Now, a lot of people will spend their lives drifting from job to job or from task to task or just sitting in the same job and never really getting anywhere. And here's the reason why. It's not because they're dumb. It's not because they're lazy. It's not because they didn't have opportunities. It's because they didn't have any goals set. Setting goals is a real art form. It's a real skill. It's something that you have to do if you wanna get ahead in anything. SMART is actually an acronym that's used to guide your goal setting. And I wanna walk you through each one of these steps. Professor Robert S. Rubin, St. Louis University, wrote about SMART in an article in the Society of Industrial and Organizational Psychology. He said, SMART has come to mean different things to different people. Now, to make sure your goals are clear and reachable, each one should be one of these letters. Okay, the first one is specific. Specificity, that is so important. It's gotta be specific, okay? If it is, I wanna make a lot of money, that's not specific. I don't even know what a lot of money is. You have to specifically say, I wanna make $10,000 a month. I wanna make $100,000 a year. Whatever that is, it's gotta be specific because if it's not, you can't break it down into increments. How are you gonna break down a lot of money into increments? It's pretty tough to do. What is a lot of money divided by 12 months approximately? It makes no sense. All right, so that's the S. The M part of SMART is measurable, meaningful, and motivating, okay? So you've gotta be able to measure it. Now we can obviously measure money. That's pretty simple to do that. But what about sending out a lot of emails? I wanna send out a lot of emails. A lot is not measurable, okay? You gotta get rid of the word a lot or a whole bunch or any of those things because they're not measurable. You gotta say, I wanna send out 10,000 emails or 5,000 emails. Now those are meaningful and it's motivating to me too because if I send that out, I know I'm gonna get something back. So that's a measurable one. When we get to the A, the A is very, very important guys. A is very important and A stands for achievable, achievable. Is this something you can really do? Is this something that is achievable, okay? Now an example would be Roger Bannister who broke the four minute mile. You know, that was pretty amazing. He did that in the 50s, I believe. And when he broke that four minute mile, nobody had done that before. And that year, so many people did that after he did because they now said to themselves, well, that's achievable, that's something I can do.  That's probably not achievable. But you'll be amazed what you can achieve if you just try. Now, the R to smart is relevant but there's more to it than that. It's reasonable, realistic and resource results based. Okay, so that's a little bit of a long one but let's look at it first. Relevant has to do with, does it have to do with meeting all your other goals? Okay, is it out of the ordinary from all your other goals? Is it reasonable? Okay, is it something that you could do? In other words, if you wanted to lose 100 pounds and you say I wanna do that in 72 hours, that's unreasonable. That's unreasonable. You can't do that, okay? And that's not realistic, okay? And it's not resource because nobody's done that without having half their body chopped off, okay? So it's gotta be relevant. And then the last one, which is really important, I think this is where a lot of people fall down, is it's gotta be time bound. And what do I mean by time bound? That means you've gotta put a limit on this, okay? When we go to school in the first grade, they let you stay in the first grade for one year, okay?  Now you don't say, well, you know, he's a really nice kid. We're gonna let him stay in the first grade for three years. Just a nice kid, you know? No, you say one year's enough. One year is enough in the first grade. One year's enough in the second grade. Now sometimes they'll hold somebody back, I get that but they don't just say, hey, arbitrarily, it doesn't matter how long he's in the first grade. Sure, he's 14 and a half now and he's starting to date but let's leave him in the first grade. They don't do that because it's gotta be a time bound goal, right? The first grade's a year and pretty much every grade after that is one year unless you mess up. So understand this time bound thing is really, really important. So let's get into this a little bit more depth. Let's take number one here, specificity. Be specific, okay? It should be very clear and specific. You gotta say to yourself, what do I wanna accomplish? Why is this goal important? Okay, you've gotta hit all these points here. Who is involved in this goal? Now, if you set a goal and you would have a website design but you're hiring somebody else to do it, you've got somebody else involved there so you've gotta factor that in. Are they gonna get things done the way they should get things done? Where is it located? Where is this goal? How is it gonna be? Is it a website somewhere? Is it a destination I'm going to? Which resources or limits are involved, okay? So let's say you go back to building that website there. You've got $100 to do it. You're gonna have a certain kind of website that's gonna come from 100 bucks. If you've got $10,000 to do it, you're gonna have an entirely different kind of website that's gonna be built. So that specificity is really important. Number two is the measurable part. Let's dig into that a little bit more. A measurable goal should address the following. How much? How much? It's really, really important, okay? If I'm selling products online, which I do, and I say, well, how much do I want to sell online? I need a number, a specific number. I may also break that down into units. So the next part would be how many? How many of these things do I want to sell? I got a course for $1,000 and I want to make $100,000. I know I need to sell 100 courses. Basically, 100 courses hit $100,000 at $1,000 apiece. And then the last part is how will I know it's accomplished? Let's go back to the website thing. You'll know it's accomplished when every part of that website's working, okay? That's when you know you got it accomplished. So how much, how many, and how will I know that it's accomplished are very, very important. And number three, achievable. We did talk about that a couple of minutes ago, but basically it's how can I accomplish this goal? How can I do it? What resources do I need? What resources do I have? So you've got to be able to say, is this going to be achievable? If it's not achievable, all the other things don't matter. But you will be surprised what you can achieve if you just try. Now, you want to be careful. You know, as an entrepreneur, I don't factor these things in because it doesn't matter to me. But when somebody else is involved in your goal, let's say you're on a job and you want to get that promotion, there's somebody else involved that's going to have to give you that promotion. You don't have the control over it that you want to have. You know, working for myself, I can set any goal I want and go ahead and achieve that goal because it doesn't matter what somebody else is doing. It's irrelevant to me. But if you're in a job and you're trying to set up goals like that, it's a little bit different. It's a little bit tricky. Number four, relevancy, okay? Is it relevant? Let's talk about that a little bit more. Does it seem worthwhile? Is this something that's worth it to you? I had different goals. I try to set one of them as I'm working on pull-ups right now. I have a pull-up bar in the backyard and you say, is this worthwhile? To me, it's worthwhile. To the average person, it may not be worthwhile. It may not make any difference to them. It's like, I don't care if I can do that or not. I do it because I want to be able to accomplish it, but I want to stay in shape. That's very important to me. So it's very worthwhile to me. Is this the right time to do it?  You go, well, is this the right time to do pull-ups? I think it's a perfect time to do it. Now, somebody may say, well, that's insane. You shouldn't do pull-ups after 40. But those same people would say, well, you're 40 years old. You should be a little bit overweight. And I would ask those people, how many pounds overweight should you be at 40? Approximately. I mean, give or take. Right, okay. So that's what I thought. The next thing is, does this match our efforts and needs? Okay, am I willing to put forth the effort? The example of the pull-up out there is am I willing to go out there every day and do pull-ups? Is that something I'm willing to do? And the answer is yes, I am willing to do that. Not every single day of the week, but for the most part, most days of the week, I'm gonna do that because that's the goal I want to achieve. But are you willing to put forth the effort to achieve your goal? You gotta ask yourself that.  How can we do this? So time bound goal usually will answer these questions right here. The first one is when? When is it gonna happen? Okay, when is it gonna happen? When do I want to achieve this goal? When do I wanna make this amount of money? When do I wanna have this website done? When do I wanna have this email sequence completed? When do I wanna launch my course? All of these things have to have that time in there. And the next one, time bound, what can I do six months from now? What can I do six weeks from now? What can I do today? In other words, you need to break down that timeline when you achieve the goal and where you're at today and what you need to do to get to that point. This is the smart goal tool. This works. It's worked in factories. It's worked in offices. It's worked in sports. It's worked in business. It works, but you have to apply it. Because if you're not achieving your goals, odds are there's part of the smart goal system that you're not following. If you follow this system, you'll get there because you've got an achievable goal and you've got a timeline and it's something you wanna do and it's something you can do and it will happen as long as you put forth the effort. Now I will tell you, one of the biggest factors in people not achieving their goals is effort, effort. Effort's painful, guys. And a lot of us will experience some pain and we're like, well, that's not worth it. That's not comfortable. This isn't comfortable. But what's even more uncomfortable, let's say your goal is money. Let's say you wanna make X number of dollars because you wanna pay off some bills and you wanna go on a vacation and you say, well, I started doing this online business, J.R. and I tell you, it was really hard and I was having to stay up late and I missed some of my TV shows and I just don't think it's worth it. I just don't think it's worth it. To do all this I've gotta do to make some money online. And then I ask you, I say, why? And you say, well, it's painful. It's hard to do. It's difficult. It's uncomfortable. All right, what is more uncomfortable? A year from now, having a stack of mail and the stack of credit cards and money that you owe because you didn't go through a little bit of effort and go through a little bit of pain, what's more painful? Opening all those envelopes? Yeah, I think that's a lot more painful. Owing all those debts? Yeah, that's a lot more painful. Not being able to quit your job because you owe all these bills because you're stuck. You gotta have that income. You gotta have that monthly income. How nice would it be? Not to have all those bills and be working for yourself if that's what you chose to do.  If you're in your job and you're happy, you won. But if you're not, you need to put forth the extra effort. You need to have some pain. That experience of pain is right on the other side of success. And that's what keeps most people from success is they hit that wall of pain and they're like, I'm not doing that. I am not doing that. Being successful online or in sports or anything else is being able to do things that other people just won't do. If you're doing things other people won't do, you're probably gonna be terribly successful. Congratulations to you. That's a good thing. Now, I hope you enjoyed this video. If you did, do me a favor, put your comments below. Tell me what you think of this video. Give me a thumbs up. Give me a thumbs down. I don't know, put something down there. Tell me what you've done to achieve your goal. Tell me what you have achieved. I wanna hear. So does everybody else. We wanna hear what you've got to say. Put that below. Also, don't forget I have a $97 course. You can get absolutely free. There's a link below in the description. It's click and learn, simple and easy. Not hard to do, no credit card required. I appreciate you watching this video and I'll see you in the next one. Hey, thanks for watching my video. Don't forget to subscribe to my channel and click that little bell right here so you can be notified every time I do a new video. Also, click on one of those videos there. Keep watching on my channel.


with two ounce and a runner in scoring position how does that change your approach in that situation man the evening before I got opportunity with bases lower and I guess right now come on it felt good though right yeah and I guess right now so I'm just waiting for another opportunity thanks God I got and just just like to put a boy in play I mean uh those pieces throw really well all night long so I'm just trying to to look for the piece I can do damage and thanks God I do you went on to score on the jew or shellis single how did you see things unfolding there and how are you able to get in there at home plate without being tagged uh I I mean I just see feel you see he always stalk me but uh after the second base lose the ball and just see a short opportunity to to score and I'm just releasing myself and and go to the home plate and thanks God I got a score for for you it looked like maybe at first you were a little shaken up on that player you okay yeah really good and what did you think of the job that Gary Sanchez did he came in late threw out a runner then provided the home run were you impressed by his late inning heroics yeah amazing I mean during the in the game when when always I'm coming I saw Gary working on the case prepared for any opportunity and that is our thing I mean maybe you don't start in the game but always you later in the game have opportunity to to hold the thing and and just we need to be ready I mean Gary uh he's look ready and thanks God he hit a homer with tonight's win and the blue jays lost you guys are now ahead of them for that second wild card you had to fend way obviously they're the first wild card spot what do you think the intensity is going to be like in Boston this weekend it's going to be awesome I mean like four season games I mean we we really fish out I mean we go there try to to get one game at a time and and try to to win all the games I mean they they have a really good team but we we have two so it's going to be interesting when we go there labor thanks for the time congratulations on the win thank you


Schizophrenia is a mental illness characterized by complex psychiatric symptoms and unclear pathological mechanisms. Previous studies have focused on morphological changes that occurred during the course of the disease, but the corresponding functional trajectories remain unclear. In this study, researchers examined the progressive trajectories of patterns of dysfunction after diagnosis using functional magnetic resonance imaging, FMI. They found five distinct stages of symptoms and FMI patterns, which were associated with clinical symptoms and gene expression data from the Allen-Human-Brain-Atlas database. The researchers also identified a shift in the importance of neuroimaging features associated with behaviors from primary to higher-order cortices and subcortical regions as the disease progresses. Additionally, they discovered that genetic factors related to neurodevelopment and neurodegeneration may play a role in the progression of schizophrenia. These findings suggest that understanding the progressive trajectories of patterns of dysfunction could provide insight into the underlying causes of schizophrenia and potentially lead to more effective treatments. This article was authored by Sisi Jiang, Huan Huan, Jin Yuju, and others. We are article.tv, links in the description below.


What's going on, everyone? Sam here with late in sports cards from 22, 23, Pranina Noir basketball, first off the line, photo, four box case number one, pick your team style. Redopolis for names of our teams, Adam K, Pacers, Blazers, Bohia B, Hawks, Brian L, Lakers, Kato H, Sixers, C-Chan with the Rockets, Christopher J, Nick's Wizards, Chun Wei, W, Sons, Jeffrey C, Mavericks, Greg M, Thunder, Harper B with the Magic, I too with the Spurs, Kenny T, Celtics, Lee Wan-Wai with the Grizz, Long J Clippers, Mark M, Kings, Mark A, Bowls, Matthew X, Cabs, Neil D, Hornets, Oriol C, Bucks, Rory W, Warriors Nuggets, Seth L, Jazz, Simon L, Timberwolves, Steve S Raptors, Seguru S Pistons, Wilfred P, Pelicans, Y Lin with the Heat, and UW with the Nets. So let me grab the checklist here really quick, everybody. There it is. Riley picking up a, or no, Richie, Richie, excuse me, picking up a couple of Personals. Thank you, buddy. Again, just the Pistons. Pistons and Thunder, breaks next. Noir photo. Photo. Again, our first look at Noir basketball this year. Come on. First off, the line exclusive on the back here. Again, that's empty, empty. It's going to be a Zion Williamson, two of 11. Congrats New Orleans, vintage art. These are cool. And I think we're going to get one frame per box here. First up is 299, Anthony Edwards, nice Ant-Man, for the Timberwolves. We've got 299, Shay Gilgis Alexander. Let's go into the Thunder. And then 299 is going to be a Yonatan Tentacupo. Nice Greek freak. 96 of 99. We've got Box Office. Oh, wow. 299 is Jimmy Butler. That is Game Mourn. This is going to be sick. Going to the Suns. How about a Redemption, Sneaker, Spotlight, Signatures, Chris Paul. Congrats on that one there. Phoenix. That's sick, dude. That's so sick. 299, Rookie Otto is Andrew Nemhard on the Showtime Signatures. Love these with the street clothes. Suns. Suns. Yes. Suns. Nice one here. Going to the Jazz. How about an Adrian Dantley? 2 of 25, Raining Nights, Otto. These look great again. The Raining Nights. AD, one of the, another very underrated NBA player all the time, Adrian Dantley. Nice AD, the original AD. Freeze Frame Signatures is going to be Johan Howard, 60 of 99 for the Wizards. Congrats, Washington. Johan Howard. Nelson Pee with the Angels, an update. We've got Russell Pee with the Bengals and Chargers in both cases of Gold Standard. Thank you there, guys. Nice one here. Isaiah Mobley, New Wave Patch, New Wave Jerseys for the Cavaliers. Congrats on that one. Very nice. And 2, 49. 39 of 49. Jake Leravia, three-color patch. Casting call. That's nice. All right, box two. Again, Foto. First off the line. Not known to be easy to open, unfortunately. It's the one thing I got against Noir. It's not easy to open. Disgusting. I know what's in there, too. I have more, dude. Riley Z, picking up the Pistons. Just the Thunder, everybody. Just the Thunder. Feature length, Nikola Jokic, 10 of 11 on the frame. Nice one there. Just the Thunder in the next case, everybody. Just the OKC Thunder. All right, starting off with a Zion to 99. 299, Jeremy Sohan for the Spurs. Rudy Gobert. Nice one there, too. The T-Wolves. Nice one here. Box Office is gonna be a... Yanis 299.  These look great this year, man. We've got Spotlight Signatures for the Lakers. Big Shot Bob. Robert Ori, 29 of 99. Congrats, Lakers. That's so cool, man. Big Shot Bob. I can make this one coming up right here. It's gonna go to the Jazz. How about A, Walker Kessler, Silver Screen Debut, 52 of 99. Congrats on that one there. Jazz. One second. Let's go check one thing. Kennedy Chandler, Rookie Otto. That'll be going to the Gris Silver Screen Debut. Congrats, Memphis. Yeah, these are clean this year. These look really good. 42 of 99. Herbert Jones, Audre Noir for the Pelicans. We've got the three-colored patch is gonna be a Jalen Duren on the... What is that? Elegant Decor? Is that what that's called? Yeah, Elegant Decor. Jalen Duren. How ya, Duren? And then Marjanbo Champ, New Wave Jerseys. 56 of 99. That is going it to the Bucks. There you go. MKE Milwaukee. Next case O, Foto. Again, just down to the Thunder now, everybody. Just the Thunder. That is it. Just the Thunder. Thunder. I think that's how that's gonna go. Package weirdly.  Jalen Brown. That is gonna be feature length to 11. I just won there for the Cs. David Roddy Rookie. I said 49. That's going to the Grizzlies. Going to the Magic. Franz Wagner, 10 of 99. I said Thunder. Magic. Going to the Magic. 299 Bradley Beal. Congrats, Wizards. I just won. Here is gonna be a Jalen Williams. 299 for the Thunder on the Rookie Jumbo material. Rookie Jumbo material. Brandon P with the Saints in both gold standards. Thank you, buddy. This is actually kind of sick. 25 Isaiah Ryder. Auto for the Lakers.  Very nice. Congrats on that one there. Shadow signatures. Shadow signatures look good again. We've got 27 of 99. Rookie Auto for the T-Wolves is gonna be a Wendell Moore Jr. He played, what, 11 years in the NBA? No, nine years in the NBA. NBA Champion in 0-1. Slam Dunk Contest Champion in 94. That is gonna, wow. You can have these next too. 5 of 99. Malachi Brannum. Nice one there on the RPA. Going to the Spurs. Congrats, Spurs. Joshua with some insurance. Very nice. Nice one here. How about 299 Chet Holmgren? Congrats, Thunder. 16 of 99. I'm gonna send an empty box and wrap it with this one. This one's a little too much. Very nice one though. Congrats, Greg. We'll get that straight into a mag. I'll get this guy out. I'll get Steve out. Steve Novus. So I'll go with Thunder. We've got a Victor Oladipo 299 on the Jumbo Material game used, right? Yes, it is. Game worn. There you go. Heat. And going to the Cavaliers. That is gonna be Newsreels to 75 Darius Garland. All Starland. Starland. Next one up. Send it up here with the packaging. Noir packaging is so bad. This might be the worst in all of the hobby. This is like Rivals last year's for Steam. Because these are all higher end too. That's the issue. What's up, man? What's up, Luis? Chillin'. Alright, gonna start off with our 7 of 11. Kevin Durant going to the Sun. Sun's doing well here, actually. Sun's doing really well here. 7 of 11. KD. Feature length. Come on. It's a Nets jersey number right there. We've got a Tyler Hero 299. Yeah, another frame. 225, 17 of 25. Kade Cunningham. Kade Cunningham. That's, of course, the Silver frame. Got two 99. Tyrese Maxi. There you go, 76ers. And this guy is pushing it. We've got a Palo Ben Carro 9 of 25. Congrats there. Magic. Let's go back to the next one. Nice two-color patch. Going back to the Thunder. Another RPA this time. It is gonna be Jalen Williams, 21 of 99. Congrats again, Thunder. It's a Greg with the Thunder right there, picking up two RPAs. What's up, Mark? How you doing, buddy? We've got, again, this time, 299. 99 of 99 for the Jazz. Oshai Igbaji. Congrats on that one there, Jazz. That is part of the card down there, luckily. Come back to this one as well. Igbaji. Yeah, designs look good this year, man. Another reigning Nights Auto. Guy just got paid. Devin Vasell going to the Spurs. This will be going to the Bulls. Rookie Patch Autograph, Black and White, Gold, Dallin Terry. Dallin Terry. Nice one there, Bulls. Congrats, Chicago. Going to the Bulls. No, that one's fine. Let me double-check. I believe this is gonna be a random, yep, this will be a random to these two teams. We've got Rudy Gaubert on the Real 2 Real, 43 of 99. Jazz and Timberwolves, game used from both, both stints. And then nice one here for the Celtics, 299. Jalen Brown. Jalen Brown. Congrats there, Boston. I'm gonna grab that really quick for a random. Again, I've got that to set up. Ready? Gonna roll the dice. Whatever team is on top after seven times, we'll get to Gaubert. One. So we're at one, two, three, four, five, six, and seven. Going to the T-Wolves. Timberwolves gonna get that one. Congrats, Minnesota. All right, quick recap here, everybody. Start off with our jerseys. Rudy Gaubert, Jalen Brown, Paolo, Cade Cunningham. That is Kevin Durant, Darius Garland, Victor Oledipo, Jalen Williams, Jalen Brown, Marsha Bochamp, Jalen Durant, Yanis, that's a Jokic, Jake LaRavia, Isaiah Mobley, Jimmy Butler, and Zion. That is Valen Terry, Kevin Vasell, Wendell Moore Jr., Isaiah Ryder, Herbert Jones, Kennedy Chandler, Robert Ori, Joanne Howard, Adrian Dantley, Andrew Nemhardt, Chris Paul, Xcarz, O'Shaig, Bajie to 99, Malachi Branham to 99, J Dubb to 99, Walker Kessler to 99, and then this nasty Chet Holmgren RPA to 99. That will do it for the break, guys. Thanks again for the fill. Up next is number two.