Hello everyone, welcome to Options with Doug, streaming live daily on Bookmap Discord and the Bookmap YouTube channel at 1.30pm Eastern Time. Before I get started, I need to go through the Disclosures, General Disclosure. All Bookmap limited materials, information, and presentations are for educational purposes only and should not be considered specific investment advice nor recommendations. Risk Disclosure, trading futures, equities, and options involves substantial risk of loss and is not suitable for all investors. Past performance is not necessarily indicative of future results. As a reminder, the focus of my presentation and the focus of the Options with Doug chat channel and Discord is options, order flow, the impact of options markets on stocks and futures, and the influence of market maker hedging flow on price action. I have a two-step process for trading and the first is planning and I use positional analysis and I look at how traders and market makers are positioned in the options market and how those positions change from day to day to develop a thesis regarding the expected trading range and volatility for the day is top ESH3 CME cell 475 as well as a directional bias. The second step in my process is execution and I look at real-time order flow in Bookmap and real-time market maker hedging flow in SpotGamma Hero to confirm my thesis and for entries and exits for setups. And questions and comments are welcome. That's on topic questions and comments and please post your questions and comments in the Options with Doug chat channel and Discord and the chat in YouTube and I'll be watching both for your questions and comments. And what I want to talk about today, first of all, go over news items, economic data, events and earnings, then we'll go through our positional analysis and then talk about setups. So first of all, and let me go into, I need to make a change in setting here in Bookmap, turn these alerts off so I don't hear them. Okay, so what I want to talk about today, economic data, events and earnings, additional analysis and then setups. So first of all, the news items, economic data, not much this week. So the only economic data of significance is on Friday, the consumer sentiment at 10 a.m. Eastern time. And of course today there was the Powell speech. Seeing the impact of that right now, very interesting, jump higher, reversal lower. So there's the market, AP or BP before Powell and then AP after Powell. And most of my prep and analysis was done BP before Powell. Okay, so again the Powell speech, 12.40 p.m. Eastern time.  So for the rest of the week, so that's the primary event of the week. There are some other Fed speakers throughout the week and then some minor earnings. The ones stocks that I look at, Disney, Uber, Lyft, PayPal, all reporting this week. But the big earnings reports were for the stocks that I follow for last week. So next week there is some significant data and events. So on 214, the CPI, so that's a week from today, Tuesday, CPI report, 8.30 a.m. Eastern time. Then on Wednesday, 215, that's the VIX expiration. And then on Friday is the monthly options expiration. So that's Friday the 17th, that's the February monthly expiration. Okay, so let's go through our positional analysis now and let's start. So this is book map and we'll drill down to this. So I want to start with a longer term chart. So this is SPX and thinkorswim and it's a one-hour chart, 20-day one-hour chart showing this nice uptrend in SPX. And what I'm showing are the spot gamma levels for today in these horizontal, excuse me, in the horizontal red line. So these are provided for spot gamma subscribers. You have to manually update these in a think script. But anyway, these are the levels for today. So that's the 20-day chart showing the levels in play. There's the 4,200 SPX, 4,200 call wall, and the 3,900 put wall way down below. So the levels that were in play today were the 4,100 level and then around 4,150 to 4,160. So let's go in and look at another thinkorswim chart in a smaller time frame. And I'm doing this just to show the levels. So it takes out everything else. It's just price and levels. So this is, again, BP, AP, before pile, after pile. And this level is not shown on the chart. I drew this line. This was a support resistance line that was noted in the spot gamma AM founders note. And SPX jumped up to that level and then reversed lower. So that is the SPX in a one-minute chart in thinkorswim. All right, let's go take a look at book wrap now. The reason, one reason I'm looking at those charts is because the SPX levels are accurate. Those are the actual SPX levels. What I'm showing here in book map, I have two columns of levels. This is the spot gamma cloud notes that are provided for spot gamma subscribers. They're updated daily, automatically. Right now, spot gamma is using a 15-point difference between SPX and SPI. So these levels are showing SPX levels. There's the 4150 and also combo levels, SPI and SPX. And they're converted to equivalent ES numbers. And again, spot gamma is using a 15-point difference. And that difference is smaller today. It looked like it was around 12 or 13, or around 12 points, maybe even a little bit lower. So it gradually decreases over time. So these levels are shown a little bit high. And in this column, this C levels column, this is my, these are my cloud notes. And I'm showing the support and resistance levels that were noted in the spot gamma AM founders note. And I'm sticking with their 15-point difference. I'm also showing big ES round numbers and then important SPI levels. And these are close to, these are correct. So there's the SPI 410 key gamma strike and the 409 volatility trigger. So those are the levels on my chart and book map. And as we saw, the important level today was that SPX 4160 resistance level. And notice this morning, all of the volume concentrated at this SPI 409 and SPX 4100 level. Okay, so those are the levels that are in play for today. And shifts on levels, there really weren't any. So recall yesterday was a very narrow trading range consolidation after a large move last week. And there was only one minor shift in levels. That was the SPX volatility trigger shifted up from 4020 to 4060. And then for QQQ, the volatility trigger shifted down one point from 304 to 303. So pretty insignificant. All right, let's take a look at the gamma levels. So start with S&P 500. This is SPX and this is the absolute gamma levels. This is the zero line. So what we're looking at here is positive gamma or a call gamma shown by the black bars that's above the zero line. And negative gamma or put gamma below the zero line that's shown by the teal bars. So this is showing for SPX that 4000 is still the absolute gamma strike. That's very obvious, the strike with the largest absolute gamma. And then the 3,900 put wall is down here. And the 4,200 call wall is up above. So the put wall is the strike with the largest net negative gamma. And that can be expected to act as support. And the 4,200 level, the call wall is the strike with the largest net positive gamma. And that can be expected to act as resistance. So one thing to note here for SPX. Again, here's the 4,000 level and note the call gamma above. So positive gamma and SPX is still in a positive gamma. That's market makers position on the gamma curve is still positive. And for SPY, 4,10 is the key gamma strike. Strike with the largest absolute gamma. 400 is the put wall. And that's the strike with the largest net negative gamma. And that's pretty obvious. And then the call wall is up here at 4,20. So again, it's notable the call gamma above the 4,10 level. And a good amount of put gamma or negative gamma below that level. So SPY is still in a market makers position on the gamma curve for SPY is still negative. In a negative gamma environment. Let's take a look at QQQ. So for QQQ, the key gamma strike 300. That is also the put wall. And then 3,10 is the call wall. So QQQ market makers position on the gamma curve is slightly negative now. And again, it's somewhat notable that all the put gamma below call gamma above the 300 level. All right, so let's take a look at data now. And just a reminder, I'm doing all this. This is normally what I do before the market opens. This is my preparation or planning positional analysis. And I'll go over this and then we'll start looking at setups. So here's gamma notional. This is market makers position on the gamma curve SPX in this left column here. Shown as that's positive SPY and then QQQ on the far right. So all of these levels shifted down or more negative from yesterday. So yesterday SPX gamma notional was 371 and shifted down to 256 today. And SPY gamma notional yesterday was minus 561 and shifted more negative to minus 776. And then yesterday gamma notional for QQQ was minus 9 and today it's minus 83. So these numbers were on Friday, they were even more positive. So from Friday to Monday, the shift has been negative. And then from Monday to Tuesday, the shift has been more negative. So shifting down on the gamma curve for all these instruments. And what that means in a negative gamma environment, negative market makers position on the gamma curve, let's say for SPY there with minus 776, that means that traders are long puts, market makers are short puts, and as price drops, they have to sell futures to hedge their delta exposure. And then when price increases, their delta exposure decreases and they can buy back those short futures. And then on the other hand, in a positive gamma environment, that means that traders are short calls, this is what SPY gamma assumes, that traders are short calls, market makers are long calls, and as price increases, they have to sell futures to hedge their delta exposure. So in a positive gamma environment, they are trading against price and in a negative gamma environment, they are trading with price. So positive gamma that tends to reduce volatility and then a negative gamma environment that tends to increase volatility since market makers are trading with price. Let's take a look at the Vana charts. And this is a graphical representation of what I was just talking about. So the way to interpret this, market makers delta notional or delta exposure is shown on the vertical axis. Price is shown on the horizontal axis. And then this green line is the current expiration, and that is showing how market makers delta notional changes in price and implied volatility. And that is the Vana effect, the change in implied delta as implied volatility changes. So for SPX, again, recall it's in a positive market makers position. The gamma curve for SPX is positive. So their delta notional increases as price increases and they have to sell futures. So again, trading against price. And then the black line shows how that delta exposure changes as time passes. And that's the charm effect. And charm is the change in delta as time passes. So for SPY, it's just the opposite. Negative gamma environment and the gamma, this Vana model shifts higher as price decreases. And then for QQQ, it's pretty neutral. All right, one other thing to look at. This is my little spreadsheet that I keep every day, tracking the key gamma strike for all the stocks on my watch list. And I track the current key gamma strike. That's the key gamma strike for today. And then I compare that with the key gamma strike from yesterday. And then I color code these, either green or red. So red means that that key gamma strike dropped from the previous day. And green means that it increased from the previous day. So notice the, you know, the sharp difference between yesterday and today. So yesterday there were, this is based on the drop in the market on Friday. So this is what the, this was the current key gamma strikes for yesterday, for Monday. And then notice after the consolidation yesterday, the only key gamma strike that shifted lower was Google. Okay, so that's my positional analysis. And based on all this, just totally neutral. Not, you know, looking for a little bit more range than yesterday. And of course, this is all complicated by Powell speaking or, you know, complicated influenced by Powell speaking. But before that, my thesis for the day was, was neutral. There's no, no significant changes in levels for the S&P 500, QQQ, or all these stocks on my list. So more of just to wait and see, watch, watch what traders are doing, watch, watch hero and see what options traders are doing to make any decisions. Okay, let's take a look at some setups. Last time I checked, hero was not working. So that, that happens sometimes in times of volatility. I'm going to move this over to another screen and see if I can get it going again. If not, we'll just have to look at setups from, from the morning, which is pretty much what I have anyway. So I'm just going to refresh this, see if it's working now. Okay, it does seem to be working. I've got, yeah, I've got about the right time. So let me move this back over. Okay, so setups. And again, what I have, I do my, I did my prep for this in the morning and they were some good setups in the morning. So let's start with Apple. And what I'm looking at is this is the full day for Apple separate outputs and calls. And I was looking at this orange line showing that traders are buying calls. And it looks like in waves, this price continues to go higher. All right, let's take a look at book map. And we'll get to the S&P 500. So here's Apple and recall traders were buying calls. Nice thing about trading stocks. These targets are very visible. Let me just move. I'm going to get rid of these, these little widgets. This is the market pulse indicator. So showing strong uptrend in the morning as traders are buying calls with the price targets above. It looks like it took the Powell speech to get price up to that level to those levels, the 154 level and then the 155 call wall here. And the thing to note about stocks is that liquidity often comes in right at the cash open and just stay there until they get filled. And these high liquidity levels, especially at spot gamma levels, make great price targets. So remember, traders buying calls, price targets above, fairly bullish order flow, plenty of green dots, rising CVD. And I just look for pullback entries. Notice all the green dots here, the pullback and test of 152. Pullback to VWAP, right before Powell. Alright, so that's Apple. Next was AMD. Let's look at, let's go look at Hero for AMD. And I'm just going to go on alphabetical order here. Alright, so here's AMD and one thing to note. Let's see, so traders are selling calls and buying puts, as they were this morning. So I'm looking at the morning session here and just the opposite of Apple. Market negative hedging flow is, oops, got the wrong thing, bearish, negative delta and prices moving lower. Let's go take a look at book map now. There's AMD and this is not a large move, kind of overshadowed by the AP move. So there's the trend lower down to the 83 hedge wall. So about a point and a half from the open, down to the 83 hedge wall, all the liquidity there. Alright, then the next Amazon. Let's go take a look at Hero now. Amazon. And in the morning for this down move, there initially was not a confirmation. Traders were buying calls and selling puts and then they briefly stopped buying calls, they sold calls. Then they started buying calls again and price reversed higher a few minutes later, somewhere between 10, 10 and 1015. So nice call divergence, long set up in Amazon. Let's go take a look at book map again. So there's the long set up and notice the shift in order flow here. The absorption and all the green dots coming in. The green dots are market buy orders, aggressive buyers coming in. As price dropped down to the 99 level, price breaks that trend line, reverses higher, makes it up to the 100 level. That's the put wall and the key gamma strike. So an important level and not a lot of range for this up move. But clearly signaled with a long call divergence. Traders start buying calls and then price moved up a few minutes later and confirmed by order flow here. Again with all the green dots and the trend break with a target at the 100 level, key gamma strike above. Let's go back and take a look at Hero again. So again a pretty clear divergence there. Traders start buying calls and then price starts moving higher as traders start selling puts. That's shown by the rising blue line. So rising orange line traders are buying calls, rising blue line traders are selling puts and price starts to move higher. Alright the next one is Coinbase and looks like that's driven by puts. So traders buying puts, not doing much with calls. So about 8 times the delta volume delta 16.7 versus 2.2 for calls. So 16.7 for puts, 2.2 for calls. Puts are driving, it's pretty obvious graphically. And let's take a look at Coinbase here. So I just moved this over to my main computer today. So I have not had time to update C levels on this chart. So I don't have the levels shown on this chart yet. But strong downtrend in the morning. Let's go back and take a look at Hero and see if there are any. So 70 is the key gamma strike. So here's the key gamma strike, this level right here. And that looks like the area highest volume concentrated at that 70 level and just below. Look at Hero. And Coinbase is a stock that has been in play recently and pretty much always shows a pretty strong correlation between options trades and excuse me options trades hedging flow and price action. Alright now let's get to the S&P 500. So this is what I saw this morning and it took a long time to play out. This divergence higher. So price chopped around quite a bit until finally moving higher around 11 o'clock, something like that. So again took quite a long time to play out. Let's take a look at book map. We'll start with the S. So here's all the chop. I'm going to zoom in on the BP section. So here's all the chop this morning. I saw this there was a prices making lower highs and then broke that and then did one final retest. This final leg down. See all the all the pink dots in there. Aggressive sellers reversing down from around the 4100 level. Then aggressive buyers come in and start to move price higher. Starting a stop run that's shown by this rising rising yellow line. Something triggered this move higher and then all these stops fired off driving the move higher. So 957 contracts were by stop orders and then one clue that this might move higher were these iceberg orders that's shown with this small blue symbol E693 contracts iceberg orders 693 contracts executed and iceberg orders are orders that large traders use to hide their size. So that was a good clue that price might start to move higher. So then just watching the order flow and the price structure and waiting for that break higher. That's an ES again BP. Let's take a look at spy and pretty much the same move. I'm going to zoom in and remember these levels are more accurate on this chart. I checked the SPX to spy ratio today and I have noted the key SPX levels on my chart and again they're more accurate today. So this is showing the trend break then a final retest of the SPX 4100 and the C5 level the combo 5 level just below that. That's shown by the blue line and the white line there and there's that final retest before the price moves higher and good for about a point and a half or so maybe two points and spy. So there's spy so price went up to the 415 level and actually I'm not sure why that's shown and that should not be white. That's just a big round number level 415 but price reversed at that level and you can see the shift from green dots to pink dots. So absorption of that level and aggressive sellers come in and start to move price lower. So prices move from the 415 level actually from the 410 keygam strike to the 415 level and then down to the 408 C5 level did another retest and now is moving higher again. So I would imagine that Powell has finished speaking at this point and now the dip buyers have come in. So this is one reason I like to look at a spy chart it's often a little bit easier to read it doesn't have as much information as ES spy ES and SPX well the S&P 500 responds to SPX levels and spy levels round number levels quite frequently so that's why it's important that's why I have both on my charts. Alright let's go back and take a look at hero now so there was the morning set up the divergence that took a while to play out I was responding later and let's zoom in now and see what traders are doing I'm going to change to a shorter look back period let's change to 30 minutes so that really doesn't provide much clarity yeah it does if we get in close enough so here right before Powell started speaking traders started taking positive delta positions and that's shown by the rising purple line and let's just see if we can get some clarity about what they were trading so they started selling puts first and then they started buying calls so this is a situation where it often helps to change the look back period to a shorter time frame in the afternoon when there's been a lot of price action so the changing back to this again the shorter look back period helps in this situation alright the next one was meta and strong correlation between options trades hedging activity hedging flow and price action and driven by calls traders are buying calls that's a powerful force that can drive a stock a lot higher traders buy calls market makers sell the calls and they have to buy stock to hedge their delta exposure alright let's take a look at book map now and there were some jump in meta after AP price reverse lower now just like the S&P 500 continues higher again and the price targets are very obvious at 188 liquidity and at 190 and more above at 191, 192 and then the big price target up there at 195 so meta has been continues to be bullish after reporting earnings last week and recall yesterday it was the only one only stock on my key gamma strike list with a green key gamma strike everything else read and meta key gamma strike increased to 200 so there's meta and the next one is Nvidia we'll take a quick look at Moderna short today, earlier today confirmation Microsoft confirmation long after a move down take a look at Microsoft and book map pretty volatile day in Microsoft with pretty deep pullback entries let's go take a closer look at hero again and there's the confirmation long right in this area and not as clear a read as meta and again deeper pullbacks let's go to Nvidia put some calls and traders were buying calls and as they started buying calls more aggressively price starts to shift higher let's go take a look at book map at Nvidia and I believe Nvidia did something like this yesterday pretty choppy for the first hour hour and a half and then finally Nvidia breaks out of its range I've shown it by this this rectangle here Nvidia finally just pretty similar to the S&P 500 makes a series of higher lows does a final retest and then moves higher and breaks out of the range with price targets up almost at every round number level a lot of liquidity above and now AP made it up to the 220 call wall before a reversing lower went back and checked the 213 level and now is heading higher let's go back and take a look at hero traders are doing now alright so there's a question in YouTube you just joined welcome can we take a look at SPX so we can take a look at SPX and hero we don't have that in book map that you can't actually trade SPX itself so we'll just look at SPX and hero but I will tell you that if you want an indication of what's going on in the S&P 500 you're better off looking at SPY or ES so regarding Nvidia there's not a lot of clue here so we'll look at Tesla and then I'll go back to the S&P 500 Tesla and as usual there's a very strong correlation between options trades hedging flow and price action and provided confirmation for both short and long entries shorts and longs let's take a look at book map Tesla and pretty choppy up and down day in Tesla trend break reversal higher trend break reversal higher trend break reversal higher and you can look at that just the opposite as well trend break reversal lower alright let's go back and take a look at look at the S&P 500 again we'll go back to let's actually go to SPY got a little more clarity here again the levels are closer to exact so let's take a look at hero and what I want to do is first take a look at SPX so this is SPX notice this number here this is in dollar terms so 82 million and also think of this as delta so price increasing is positive delta so positive delta in the morning then flattens out then it looks like it's rising again so SPX let's remember that number then we'll go to SPY so there this total number in 60 353 million so SPY options this dollar notional value is a lot higher in SPY than SPX so this is why I prefer to look at SPY Brent Kuchuba the founder of Spont Gamma has discussed that as well he prefers to look at SPY the SPX is I think it's still pit traded and SPY is definitely electronically traded and traders, market makers have to respond they don't know what's coming so they have to respond more quickly with SPY than they do with SPX and then the total signal we'll take a look at ES and this is a combined signal combining SPX and SPY options trades calls and puts into one signal and that's for ES so if I'm looking at ES and P500 I look at ES or SPY so okay let's take a look now at ES let's change this look back period so pretty wavy here and then chopping up and down and again recall when we looked at this a few minutes ago traders were taking positive delta positions and doing that again and so there's a question in discord trader AG just jumping in here late trading Powell great so what was the most important highlight I don't know if there was an important highlight today the positional analysis this morning was definitely neutral and not a lot happened until Powell started speaking and I don't know what he said I think he I heard that he initially said something like inflation is contained or I'm not sure what the exact words were and he must have said something else that sent price lower so based on gamma and gamma levels let's take a look at let's go back to book map and look at SPY I think it's most clear here that price jumped from the 410 key gamma strike straight up to 415 and this is this level should not be should not be white that was my mistake there so 415 and then reverses lower down to the 408 C5 level so those are the SPY levels so I think really the the keys were the levels in play and then let's take a look at SPX and this is the 4160 resistance level that was noted in the AM Founders note so let's let's just take a look at I'm going to go to I'm going to pop this up so let's go back to the thinkorswim chart and then pop up the levels so we can look at this so this 4160 level was noted it's not a it's not shown on this chart but it was a a level noted as resistance in the AM Founders note and for some reason the 4165 well actually this is the 4165ES is the 4150 level so this is not showing any and this is SPX in the left column here not showing any levels between 4150 and 4200 so we can one thing that we can do this is just on the fly here so I don't know if this is something that is going to be significant or not but what we can do is go to equity hub we'll go to SPX we'll take a look at the composite view and sometimes these 4160 level so that is where that resistance level comes from that inflection point and this is showing the spot gamma momentum indicator it is the showing the rate of change of gamma and often these inflection points can act as support and resistance levels so I think this is where that 4160 resistance level comes from and that is also let's just take a look at the founder's note that's probably also noted as SPY415 so let's go here so yeah that's where that that inflection point and this level right here so 4150 to 4160 that's SPY415 there you go SPY415 resistance that 4160 inflection point and the SPX composite view acted as resistance so the hero hedging activity was not a clear read for SPX this morning but the levels really helped so that's my take on it so anyway my time is up I think I've answered all the questions thanks for watching thanks for your questions and comments and I will see you tomorrow thanks again bye


Welcome everyone. My name is Dinesh Sranee. I'm a software engineer at Portworx and today I'm going to be talking about how you can use external persistent volumes to achieve higher availability and reduce recovery times when using stateful services on DCUS. So let's jump right on. So here are the topics I'm going to cover today. We'll talk about the different types of stateful services. Then I'll go through the advantages of using external persistent volumes. I'll also give you an introduction about Portworx and how you can deploy services on DCUS to take advantage of Portworx volumes. Then I'll do a demo showing how you can install Portworx as well as Cassandra to use Portworx volumes and demonstrate failover and some other useful scenarios. So let's talk about stateful services. There are basically two types of stateful services when it comes to persisting data. The first are simple applications which don't do their own replication. They rely on the underneath storage layer to be always available. WordPress or MySQL are examples of such kind of applications. Now the second type of stateful services are basically applications that do their own replication across nodes. So in case a node dies or fails, there is always either another copy of the data available somewhere or somebody is able to replicate data onto that node. So if a node that has crashed comes back online, then the application takes care of repairing data onto that node. This repair can be done either manually or it can be automatic depending on the application that is using the data. Some of the common applications used nowadays like Cassandra and HDFS are examples of such a kind of stateful services. So now you might be asking why is this replication strategy important? Well, it's because bad things happen all the time, right? Your nodes could crash, your network could have issues, disks on your nodes could fail. You might also have power outages which might take down complete racks of your nodes. For applications that do their own replication, there's always another copy on one of the other nodes in the cluster. So they can continue to serve IOs. And if you have to replace a data, you can just bootstrap it and repair all the necessary data back to it. This does end up taking a long time depending on how much data you had on the node that failed. For non-clustered applications, though, if you had no backup and they were using local storage, your application is doomed. You will not be able to bring it back up unless you can either move your data disk to another node or restore from a backup.  So how can persistent storage help in all of this? Well, for the case of applications like MySQL and WordPress which don't do their own replication, it can help you provide high availability for your services and make sure that your downtime is eliminated. And for services that do their own replication, it can help reduce recovery times by a large amount. This is because you don't have to bootstrap a new node every time a node fails. All you would have to do is basically start the same task on another node and basically the external storage would be able to be mounted on the new node and you would only have to run a repair to restore data for the rights that you had missed while the node was down. So I'll talk a little more about this in the next slides. So before we talk about the scenarios, I would like to give a brief introduction about Portworx because a lot of the scenarios that you talk about are based on software-defined storage solutions like Portworx. So Portworx is the first production-ready software-defined storage solution designed from the ground up with microservices in mind. So using Portworx, you can provision and manage container granular virtual devices and a tight integration with schedulers like DCOS and Kubernetes and Container Orchestrators helps run your workload local to where the data is. So you don't spend a lot of network bandwidth basically traversing your data between nodes. We also have features like snapshots and cloud snaps for backup and DR. We also have support for encryption so you can actually integrate with Vault as well as DCOS Vault to provide keys to encrypt your volumes. And all of this is done using automated provisioning and control. So you can basically repeat this entire provisioning using RESTful APIs. And Portworx itself actually runs as a container. We are also working towards integration with CSI. So when DCOS has support for CSI, we will be able to support CSI too. So this is how Portworx, the Portworx architecture looks when it's deployed. Portworx basically consolidates all your storage infrastructure whether it's bare metal servers, existing NAS or sands, clouds or hybrid clouds into a unified data layer which is specified by the orange part of this diagram. So by deploying Portworx, you have persistent storage ready to be provisioned for all your stateful containers and your apps driven by a scheduler of your choice. So the block layer replication performed by Portworx is synchronous. So all the replicas will always have the same data. This ensures that your application is always able to come up on another node in case one of the nodes where your data is placed crashes. So once the node comes back up, Portworx will automatically repair all the data that was missed on that node and bring it back in sync with the current state of that volume. So if the node goes away permanently though, Portworx will be able to re-replicate the volume onto another node completely. So this ensures that Portworx is able to deal with any further crashes so that you always have data for your volume available. So now let's take a look at how recovery times with local volumes and external persistent volumes are different. With local volumes, your data is basically pinned to a particular node. So if a node crashes, the faster it comes back online is the best for your application because you would have to repair less data. But in reality, that is very hard to enforce. Because if you have any kind of maintenance on your servers, it could end up taking some time and basically when the node does come back up online, you would have to repair a lot of data to get it back in sync with the rest of your cluster. Also, servers take some time to reboot whether it is bare metal or just a VM in the cloud. And in case your node fails permanently, this recovery time will be even longer. Because what you would have to do is you would have to provision a new node, add it back to your application cluster and you would have to bootstrap it with all the data that was missed while the node was down. And this involves a two-step thing. For examples like Cassandra, you would actually have to bootstrap the node and then repair all the data back to the node to make sure that it is in sync with the rest of your Cassandra cluster. Comparing this to external storage, your volumes will be accessible from any node in the cluster. So if a node goes down, you don't need for it to be able to come back up for the node to join back into your application cluster. Your scheduler would just need to start the same task on another node and use the same volume from the node that went down. And in case a node fails permanently, this is the same two over there. Because you would be able to use the same volume to basically bring it back up online. So in this case, for example, if you were running Cassandra, you would not have to run the bootstrap step. You would only have to repair data to that node that was missed while the node was down. So here are some of the advantages of using portworks. So you might think, why can't you just use a SAN or a NAS? So the fact is that using a SAN or NAS is kind of an anti-pattern for container workloads because it involves static out-of-band provisioning, which is not something that fits in very well with the current DevOps flow for new generation apps. Also, using SAN and NAS introduces a lot of latency in your apps since you actually have to basically go over the network to get storage, which is different from what you would actually want for your high-performing apps. And if you actually used any of SAN or NAS services, you would know that there are a lot of issues just around automating the entire workflow with containers and schedulers. You will frequently run into issues where you're not able to use the same volume if a node had failed onto another node. And in fact, if you actually hit network issues contacting your NAS or SAN, your entire service will be down. You will not be able to provision anything just because that one link to your NAS or SAN is down. So the advantage of Portworx here is that it is built ground up with microservices in mind for containers. And our goal has been to basically have a tight integration with schedulers to basically avoid the pitfalls that you would see during failure scenarios. And with Portworx, you can actually have a unified solution for hybrid deployments. So in case you have an on-prem deployment as well as a cloud deployment, you don't have to have two strategies to deploy your apps. You would basically be using the same Portworx solution in the cloud as well as on-prem. So all your automation can be consolidated to use the same automation. So you might wonder why can't you just use EBS directly, right? So EBS doesn't work for hybrid deployments. It's fine if you want to use it in the cloud, but then if you have an on-prem deployment, you would need to have different strategies for that. Also, EC2 instances have a limit of 16 EBS volumes per EC2 instance. So you will not be able to deploy a lot of apps if you're using something like EBS. And if you have actually used EBS, you would know that a lot of the times EBS volumes get stuck in detaching an attaching state. So when your EC2 instances fail, you will basically not be able to use the EBS instance, EBS volumes on other instances. You would basically have to go in and manually force it to be attached or detached so that it's usable somewhere else. And performance is also not very good when you're using EBS volumes unless you're using provisioned IOPS, but then you end up paying a large cost for using that. And if you're using EBS, your failover is slow because that's how it is designed. So AWS would first have to realize that your EC2 instance is down. They never need to make sure that the EBS instance is not being used on the old node, spin up a new EC2 instance, and then attach the EBS volume there. So basically using portworks with stateful services, there are three ways to use portworks with stateful services on DCUS. You could use Marathon to basically deploy services to use portworks volumes. We also have a couple of services in the DCUS universe based on the DCUS Commons SDK, which has added support for portworks volumes. So they're available in the universe and you can just deploy them through there. The changes that we've made to the DCUS Commons framework is also available on GitHub. So you can actually write your own services to take advantage of this framework in case you want to use portworks volumes. So this is an example of how you can use Marathon to deploy apps to use portworks volumes underneath. So if you're familiar with deploying apps through Marathon, you basically have to specify a JSON format for your apps to specify what container you want to use and the volumes you want to use as well as your port specification. So to use portworks, all you would have to do is specify PXD as the volume driver, and you would have to specify the options for the volume that you want to use. So there would be no out-of-band provisioning. As soon as you start the app and you specify the volume options that you want to start it with, you would be able to use the app. And this same method can be used to deploy apps using Docker or UCR on DCUS. So the second way is to deploy apps through the universe. So we have a couple of apps published in the universe based on the DCUS Commons framework to use portworks volumes. Those are Cassandra, Hadoop, Elasticsearch, as well as Kafka. So apart from adding support for portworks volumes, the changes that we've made also support failure of tasks when nodes crash. So this ensures that your services have a higher uptime. And it also reduces recovery times because you don't have to wait for your node to come back up. As soon as DCUS recognizes that a node is down, the framework would know that would get a notification and it would be able to launch the same task onto another node using the same volume. So we've also actually updated the framework to be able to co-locate your data with your nodes. So because we have control over the framework, what we can do is we can actually query portworks and figure out where the data is and launch your tasks local to that node. So this reduces latencies as well as reducing network congestion on your network. So this is an example of how you can use the updated DCUS Commons framework to use portworks volumes. So DCUS Commons makes it very simple to start stateful services, but it only has support for root and mount volumes, which is not very efficient when you're dealing with failures, which will happen in large clusters. So what we've done is we basically added support for portworks volumes in the SDK, and all you need to do is if you're writing an application for DCUS Commons, all you would need to do is specify the volume name and volume options in the YAML specification for DCUS Commons, and you will automatically end up using portworks volumes when your application starts up. So once you have your application specified, all you would need to do is build it and deploy it, and you would be able to use portworks volumes. And again, same as launching tasks to marathon, all your volumes will be automatically provisioned, so you don't need to wait for a storage admin to basically come in and provision volumes for you. So the changes that we made to the DCUS Commons is available on github at github.com slash portworks slash DCUS Commons. Okay. So I'm going to show you a demo of how easy it is to install portworks, and on top of that, how easy it is to install Cassandra services to use those portworks volumes. And then I'm also going to demonstrate what happens when a node fails and some other scenarios do. So like I mentioned, all these services are actually available in the DCUS universe. So first I'm going to go ahead and install the portworks service. I'm just going to change the image name to use the enterprise image, and I have a final DCUS cluster, so I'm just going to change that to install it on all the five private agents. I don't think so actually. So I have actually sped up the video a little because it takes like eight minutes to start the entire thing, but I'm just going to pause it here. So what will happen is we'll launch the entire stack. So first we'll go ahead and launch a three-node HED cluster, then we'll start an HED proxy, then we'll start an influx dv node, which is basically used to store the stats for our UI. Then I'll go ahead and start a lighthouse task, which is basically the portworks UI. And after all that is done, it'll basically go ahead and install portworks on all the five private agents. So as you can see here, the HED three nodes HED has started up, influx dv started up, and then lighthouse is basically staging at this point. So since lighthouse is installed on a private agent, it's not accessible from outside the DCS cluster. So what I'm going to go ahead and do now is it'll basically go ahead and start a epoxy service, which is kind of a proxy from a public agent onto the private task that's running. So all of this information is actually available on the docs website, and it's also linked when you're starting the portworks service. So this is just starting a marathon app to start the epoxy service. And once that comes up, you can basically go to your private agent, port 9999, and you should be able to access the lighthouse UI. So once this comes up, what we'll see is basically portworks install is happening on the private agents. So we'll start seeing these nodes come up on the dashboard. So as soon as they come up, they basically contact lighthouse and tell them they're up, and as you can see, five nodes are installed. And it's a little blurry in the video, but all this happened in basically eight minutes. So we basically stood up an HCD cluster, the UI, as well as portworks, and it's already be provisioned in under eight minutes. So now that this is done, so you can actually also look at the status of your portworks cluster by running the portworks control CLI. So all you would have to do is log into one of the private agents and run PixiCurl status. And I guess the color is not very visible, but as you can see in the green, there are five nodes that are now online and ready to be provisioned for volumes. So now that portworks is set up on all the private agents, I'm going to go ahead and install Cassandra, which is available in the DCO's Universe 2. So this Cassandra service has basically been updated to automatically use portworks volumes when it gets provisioned. So the defaults are set to use the portworks. It's been set to use portworks volumes, but and we can also pass in additional options for the portworks volumes. So what I'm going to do here is I'm going to set up the portworks volumes to use a replication factor of three. So in case a node where the volume is provisioned goes down, we'll still be able to basically use the same volume on another node. So basically here is the portworks volume name and here is the portworks volume options. And I'm just going to specify a repel equal to three. And you can basically specify multiple options over here, which will be which are comma separated. So if you wanted this to be an encrypted volume, you would just say secure equal to true. You would need to make sure that portworks is set up to basically pulling keys from a secure vault. So once once I said this, I'm just you can also specify the size of the volume I've currently set it to 10 GB. And I'm just going to click review and install and install. Just looking at the volume list, I'm confirming there are no volumes available. And I'm just going to keep a look out for the volumes that get automatically provisioned. And I'm going to go back to DCOS. And from the lighthouse also you can see that there are no volumes currently provisioned. And we'll see as soon as the Cassandra nodes come up, the volumes get automatically provisioned and they're visible both through the CLI as well as lighthouse. I sped up the video a little because it takes time for the nodes to come up. But at this point, the three node Cassandra cluster is up. And as you can see, three volumes were created all with a replication factor of three and a size of 10 GB. So now that this is up, what we're going to do is we're going to basically go ahead and power off one of the nodes. Now what would happen with just the regular Cassandra framework was if you powered off this node, the framework would not bring up the same task on another node because all your data would be local to the node that was powered off. But what we'll see here is since these volumes are backed up by Portworx and the replication factor is set to three, DCOS will actually be able to bring this same Cassandra node up on another physical node. So I'm going to basically as such into one of the nodes and I'm going to just power it off. First I'm confirming that the volume was mounted and the task was running here and then I powered the node off. And going back to the UI, you'll see that this task will disappear. So DCOS already sees that the node is offline. And in some time you'll see that the node disappears from the list and another one gets spun up. It's not very clear, but the IP is actually one of the other nodes where the replica was for the data, for the volume. So it'll basically be able to join as the same identity as the node that went down.  So it actually knows that this volume is safe to be attached on any other node. Scenarios like this, if you were using EBS or a SAN or NAS, you would run into issues where the software solution, the storage solution is not able to determine whether a volume is still being used by another node or not and whether it's actually safe to attach it to another node. One more interesting scenario I'm going to show you is, so as I pointed out, I had actually started these Cassandra nodes with 10 GB of storage. Now, if you're running any application in production, 10 GB of storage for each Cassandra node is very low, right? And if you were actually using this with the root amount volumes, you wouldn't have any way of actually increasing the size of these volumes. You would have to destroy the service, start a new service, and then copy all the data on, start a new service with increased volume size and copy all the data onto that. What I'm going to show you here is you can basically resize the volume online without actually taking your service offline. So, I'm not sure if it's very clear, but yeah, this shows that the volume was actually mounted on that node. So, and resizing the volume as simple as running the CLI, all you would need to do is run PixiCurl volume update, specify the name of the volume and specify the new size of the volume, and it would automatically go ahead and update the size of the volume. So basically over here, I'm increasing the size of the volume from 10 GB to 100 GB, and as you can see, it went ahead successfully. And if I do a volume list again, you can see it's not very clear, but over here, you can see that the size has been increased to 100 GB. And the application will actually see this size increase right away. So, you don't even have to restart your application to be able to see the increased size. Okay, I guess that's it for the presentation. Does anybody have any questions? Sure. Yes. So, you can start a service through Marathon to use Portworks volumes. So, for the example that I gave for MySQL, the only thing you would need to do is use a Postgres container and specify the same parameters, and it would basically be able to start a Postgres service. So, any container that, any service that you can start using Marathon, you can use Portworks volumes with that for persistence. And you can use Docker as well as UCR. So, all the replication is synchronous? No. So, there'll be a total of three replicas. One will be local and two will be remote. So, we do wait for all the IO to be persisted before it's acknowledged. So, there is a slight overhead, but it provides an advantage of providing high availability in case the node goes down. Yes. Yes. But we see in most customer deployments that they have, I mean, most of the customers have a high throughput and low latency backbone connecting the nodes. So, the changes actually are very minimum. So, it's all open source, like a pointer, or you can go ahead and look at the changes, too. But the changes are very minimum. So, the changes involve adding support for Docker volume drivers, where we support Portworks. And the second major change is to basically support failover of tasks. So, the upstream DCS Commons package, even for state less apps, your tasks cannot failover between nodes, even if the node goes down. So, that is something that was basically added as support. So, there are these two major changes, but it does not diverge a lot from DCS Commons. And we basically try to keep up to date with the DCS Commons releases. So, we will basically try to push changes into the universe as soon as DCS Commons make changes, too. Hi. So, I have two questions. Can you talk to running Portworks in an environment where only some of the Portworks services have volumes that are shared to the overall Portworks environment and making other nodes in your cluster available to that storage for, I guess, Headless is what you guys call that. And then, also, talk to your roadmap about removing SED from your dependency chain. And one thing that we found was that running SED within Mesosphere is not fast enough and it fails often. So, we extracted our SED outside of the cluster altogether. So, if you could talk to those two things, that'd be great. So, two things. The first thing is, basically, if I got your question was, how do you specify Portworks to be installed only a set of nodes and not on the other set? Okay. So, Portworks can be installed on nodes which have storage as well as which don't have storage. So, in case you install Portworks on nodes that don't have storage, you will still be able to mount volumes that are basically placed on the other Portworks nodes. So, that all works seamlessly. If you want to specify DCOS to run your jobs only on the nodes which don't have storage because they have a lot more compute power, you can always specify constraints. So, you can place labels on your Headless nodes. And when you start up these services like Cassandra or Hadoop, you can basically say that you want to start these tasks only on the Headless nodes. So, what will end up happening is they'll remotely, you will end up mounting, attaching and mounting these block devices on your Headless nodes, but your data will lie on your other storage nodes. Yes, they all have the same licensing. Yes. And about your question for HCD. So, yes, we have also realized that running HCD within this entire framework causes issues because what happens is, in case you hit issues with just DCOS in general, what happens is you lose state for those root and mount volumes for HCD. So, it is, for a test scenario, this is using the entire stack to start HCD as well as Portworks within the same thing, is a good way to basically make sure that you are, it fits in each and stuff. But for production, it is advisable to provision HCD separately or on a different cluster completely so that in case your DCOS cluster goes down completely, you're still able to bring Portworks up because your HCD is lying externally. So, Portworks doesn't have any dependency on DCOS. All it really depends on is that your data disks are not touched. So, even if DCOS goes down and you have to reinstall DCOS, you will still be able to start up Portworks and reuse the same volumes. Yes, and in the next release, we are basically planning to move the KVDB into Portworks itself, so you'll not have a need to even provision an external HCD server at all. So, we will not be using the root or the boot disk. We'll basically be using, we'll create a partition on one of the data disks and store HCD information there too. So, again, in that case too, if DCOS goes away, if DCOS basically, you have to reinstall DCOS, you'll still be able to bring up Portworks exactly in the same state. And all you would need to do is basically redeploy your apps and you would be back up in production. From some of the answers you've given to the questions here, it sounds like that there's always the potential that you could be crossing network boundaries with addressing storage and obviously with being synchronous there's some right overhead. Is there a capability to get additional read performance by having more replicas? Does it have the intelligence to distribute reads among the replicas? Or is it always focused only on the local copy even if it's, say, like across the network you're running headless compute against storage nodes? So, our reads are optimized in the sense that we would, we basically send out reads, we do reads from all the replicas and basically we try to send out more reads to nodes that are replying faster. So, in that case, we are able to basically utilize reads, utilize all the replicas to perform reads. And this is all consistent. So, this is all consistent. So, reads can come from any data and they'll always be. Second question. Since this causes storage across network boundaries as well, do you do like storage pooling across network boundaries? So, let's say a single storage node does not have the capacity to service what you need, say a staple application that doesn't support sharding. Would you be able to use Portworx? Yes, we have support for aggregated volume. So, you can basically, apart from doing replication, you can basically split out a volume up to three aggregates. So, basically, you can split it out amongst three nodes. Yeah. And this has an advantage, right? So, if you basically want to scale, you can basically either scale up your nodes or you can scale out your nodes, right? So, you can actually add more disks to your existing nodes or if you don't have enough capacity or slots, you can basically add more nodes and you'll be able to basically resize your volumes across nodes in that case too. Any more questions? Yes. So, if it's not the same size, you'll basically end up creating a new pool but it'll still be accessible for any new volumes that you want to create. Yeah. And what we basically do is we are able to partition, we are able to create different pools for different types of disks. So, if you have SSDs as well as SSDs, we'll basically end up creating two pools of these disks. And depending on your application, for example, if it's Cassandra and you want low latency, you can basically specify the class of service that you want and you'll be able to use the SSD for your Cassandra services. But if you have something like Hadoop where you want more throughput, you can basically specify the HDD to be used instead of that and it'll automatically place the replica on all the different nodes on the same class of service. Yeah. Go ahead. So, do you mean replication across availability zones? Sorry, I didn't get your question. So, these would be two different clusters completely or would it be a part of the same cluster? Or would it be two different nodes and two different racks is what you mean? Okay. So, right now, we don't have support for replication across clusters because, if I'm understanding correctly, these would be two different portworks clusters completely, right? Yes, you can do that, but obviously you would have to realize that there would be a latency involved when you're doing replication across like a van or something. I guess that would all depend on your application needs and what your application requires. For example, if you're running Cassandra, I mean, that really won't help your application, right? So, it can be done, yeah. There's no limitation from our side. Yeah. Any more questions? If you want more information, you can visit us at our booth. You can visit us at our booth. You can also visit our website at portworks.com. Like I mentioned, all our services are in the DCUS universe, so you can just search for portworks and they will all show up. And if you want to request a demo, you can always contact us at info at portworks.com. Thank you.


My name is Paul Whitney. I'm with As Reader and our device is turning a phone into a UHF or HF barcode scanner and or reader writer. So this is the sled here. So what does it do? So this allows you to use iPhone to read or write EPC chips in tags like this. Which is like RFID? What is that? Exactly. So this is a UHF RFID. We also do HF. Sure. Flexible. This particular one here reads moisture. We also have ones that read temperature. So you can read temperature at a distance of up to 32 feet. So the the tag itself is passive so there's no battery. What it does is it uses the radio waves to power the tag to read the data that's in the chip right there like a grain of sand. Very very small chip and then it bounces back to the reader. So the radio wave hits this, reads the chip and then bounces back with the info. Yes. So this version here is able to read at 32 feet. So this is the long-range gun version. So what's going on here? Can you show? Sure. So this is a linear antenna. This antenna here is a circular antenna.  With this it's linear so it's shooting it out straight. Now if you if you move you can still read everything in this room but it reads at a long distance of 10 meters or 32 feet. So it's sending RF power? A radio wave, yes. And getting the signal back. And then it gets the signal back. Now with this you're able to actually pinpoint the location of it. So for example you can you can pinpoint the location of a tag with the exact distance. So this can tell you that you're looking at a tag that's three feet seven and a half inches. Is it something that works right now? Yes it does. So can we do a test? Absolutely. Let's put it back somewhere. Sure. Sure you got it. All right. So we have some animation showing how it works. This is a temperature? Yes that's a temperature tag. We have different devices. Give me just a moment. Let's see. The small one here here we go. We've got the temperature on here. So let's look at... So here's the temperature tag. We'll turn this on. I'm going to clear the old data. Read it. Okay so it's got these two tags here. You see the temperatures. I'm going to put my thumb on here to start raising the temperature. And you see how the numbers are changing. See how it's all the way up to 28 degrees Celsius now? That's measuring in real time. Exactly. How can that happen? Isn't that awesome? What is this chip? Yes it's an EPC chip so it's just very very small. The core takes them zero nothing to do with that. I don't know that actually often. Exactly. But these are standard Gen2 tags. And not every reader out there can read the temperature and moisture. But ours can right out of the box. How far does that one go? This one's about one to two meters. So about three to six feet depending on the tag. This is a pretty large tag so it can go a little farther. There are small tags that are the size of a grain of sand. You've got to get pretty close up on those. And what are we looking over here? Sure. So we've got combo readers that do barcode. So this one's one D2D barcode. And part of what's really cool about our device is that you see this case is for an iPhone 5, an SE. So you simply take out the case and put it in this larger case here. And now it'll fit an iPad mini. And you also have the technology to charge easily with one of those. Exactly. So this is if you're in the field for ten hours and you needed to send the life of your phone, you simply slap on one of these batteries and it can keep going. And then if you want to charge it together, you're actually able to put it on here and then charge the battery, the sled, and the phone all at the same time. Nice. This is awesome. This is like a USB but it's just more easy to write. But without the breaking off point. Exactly. Yeah. And that's, you know, everybody finds that those cables are where things tend to break. And this allows you to connect with magnets 360 degrees and not have something that's going to break off. Have you been doing this for a while? We have. So our company, the company that makes these readers started ten years ago in Japan. These have just been introduced to the US market in the last year. So we're still very new here but we actually represent 70% of the sled market in Japan. 70% of the what? Of the sled market. What is a sled? This is a sled. So a device that hooks on to a smart phone like this. So some of our biggest users are department stores like Tokyo Hands or Toyota Manufacturing. They use this in the manufacturing process. And it's for iPhone and Android? We do offer Android as well although we custom make them because there's so many different kinds of androids. This example here is with a sharp telephone. Oh that's a good one. Is it the bezel less? Actually this is just a regular, a regular sharp but there's 7000 different kinds of Android footprints now. So we actually have to make it to fit the phone. So we take orders of usually a thousand or more units to make the case just for that particular device. But it can be done. And it can be done either this one's using the mini USB connection off the side of the phone. We have an adapter that can allow it to go off the bottom like a Samsung. Or we can forget the mini USB all together and use a Bluetooth. But we prefer to try and use hardware so you don't have any of the pairing issues. Is there any chance you might do a more flexible one that could fit a bunch of different phones and be flexible on the side? Exactly. Here's how the Android works. So you can see inside here we have a sort of an elbow adapter that connects to the mini USB. And with iPhone everybody's using a lightning connector. Everything from the iPod touch up to the iPad Pro 9.7. It all just uses lightning connector.  So what we did was make an elbow adapter that we could move around as necessary and then we make a different case to fit that specifically. Alright. So as reader is it a Japanese company? Our headquarters is in Japan but our company is actually located in California. We're a wholly owned subsidiary. And the company in the US has just been here about a year and a half now. And we're still very new to market in US but we're getting out there and letting people know what we have. What kind of price are we talking about? Sure. So the barcode only version is 499 and then the 2D barcode is 719 and then the RFID only is 999 like this one here. And then the combo. So this is a combo of 1D, 2D barcode as well as a UHF RFID. This is 1199 and then for 1299 we're able to go up to this 10 meter range, 32 foot. So for this 1299 we're able to go up to 600. And you could walk around and just read a whole bunch of stuff. Oh yes. Yes. Very quickly. Thousands instantly. And what's the best use for that? Well you know asset tracking is really one of the biggest uses obviously. There's a lot of different things in the medical industry as well as in retail where people need to keep track of items. For now you know tags have been expensive in the past so for a long time it was only tracking expensive assets but now that the price of tags is getting under five cents each you know it can be used for even checking your inventory daily. So if you have a tag on everything in the store actually we have some use cases on our website that you can check out but there's a retailer who used to start every morning by going around the store and reading every barcode.  They'd take half hour 45 minutes every morning to do the entire store. Now in the morning they get in they just wave it around and they're done in a matter of minutes. Just a couple minutes they've read the whole store. The whole store. There's a few mistakes right? Here's the reasons why you have mistakes. So for example if you have tags that are like if you had two blouses usually there's a little space but if they were right up against each other and you got the tags right on top of each other like that that could be hard to read. Not impossible but it can be hard. What they'll do in that case is they call it fluffing. So go by and they're just kind of fluff the blouses or whatever is on the hangers and then read again. So when you find something missing one of the things that people often do is they'll look at the data of where the last place it was seen. So this red size medium blouse was last seen in changing room number four for example. Then they'll go there and look first to see if it isn't there. Or then they'll look at the places it should be. If it's not there then they assume perhaps it was stolen or it's misplaced those kinds of things. It goes through clothing no problem? Oh yeah yeah through clothing is no problem. The weaknesses of RFID are metal and liquid. So if you were trying to read a tag that's behind me you wouldn't be able to read it. But under this wooden table no problem. So plastic, wood. Yes. Thousands of pearls. Yes it is it is. Now of course they are there are there's quite a few stores doing it. You can also use that weakness as a strength. So for example it can't read through metal. So if you had a rack of shoes for example and you had shoes on this side and shoes on that side and you didn't want to read both you would put a screen in the middle of the rack and now you'd only read the shoes on this side and not read what's on the other side because you put a metal screen in there. So it's very easy to use that as a way to kind of harness the power that you're using of RFID. Alright that's cool. And here at the printer, I do think it's a printer. I guess you're talking about temperature. Yes. Maybe some of these companies are making new sensors. Absolutely. Yes. What could it be? Oh goodness. You know honestly I haven't had a chance to tour the whole show yet but there's so many out there so many possibilities. I mean with the with the moisture one of the uses in healthcare right now is for example checking adult diapers and dementia patients. So say for example you had a dementia patient who's aggravated and they say they need to be changed. You can now change you can check at a distance rather than having to get up close and check and see if it's wet or not. You can check from several feet away without being in range if you will. So that's a really good use of moisture checking. Also Mercedes-Benz is using it in their in their manufacturing process. So they'll put one of these tags inside the door before they do the final weld on closing up the door to make sure there's no moisture in there because that was one of the main reasons cars were coming back. So they'll put it inside check it if it's moisture free they'll seal it up. If there's still moisture they'll dry it out first. So all kinds of different great uses of these sensors for sure.


Hi, and welcome to the session. Let us discuss the following question. Question phase, let function f from set 1, 3, 4 to set 1, 2, 5. And function g from set 1, 2, 5 to set 1, 3 be given by f is equal to set of ordered pairs of 1, 2, 3, 5, 4, 1. And g is equal to set of ordered pairs of 1, 3, 2, 3, 5, 1. Write down g os. First of all, let us understand if we are given a function f from a to b. And there is another function g from b to c. Then the composition of f and g is defined by g os, which is a function from a to c. We can see the codomain of function f is equal to the domain of function g. So we have defined the composition of f and g as g os. And it is a function from a to c. g os is a function given by g os equal to g fx for some x belonging to a. So clearly we can see g os is equal to g fx for every x belonging to set a. This is the key idea to solve the given question. Let us now start the solution. We are given function f from set 1, 3, 4 to set 1, 2, 5, which is given by set of ordered pairs of 1, 2, 3, 5, 4, 1. Now we are given another function g from set 1, 2, 5 to set 1, 3. It is given by g is equal to set of ordered pairs of 1, 3, 2, 3, 5, 1. Now clearly we can see f1 is equal to 2, f3 is equal to 5, f4 is equal to 1. We can write f1 is equal to 2, f3 is equal to 5, f4 is equal to 1. Now again g1 is equal to 3, g2 is equal to 3, g5 is equal to 1. So we can write g1 is equal to 3, g2 is equal to 3, g5 is equal to. Clearly we can see codomain of function f is same as domain of function g. So we can define composition of f and g as g os. g os is a function from set 1, 3, 4 to set 1, 3. So we can write g os is a function from 1, 3, 4 to set 1, 3 such that g of f1 is equal to gf1. Now we know f1 is equal to 2. So we will write it is equal to g of 2. Now we know g of 2 is equal to 3. So this is further equal to 3. We can write g of f1 is equal to 3. Now let us find out g of f3. g of f3 is equal to gf3. Now we know f3 is equal to 5. So we will write it equal to g5. So it is substituting for f3 we get g5. Now g of 5 is equal to 1. So we get g of f3 is equal to 1. Now we will find g of f4. We can write g of f4 is equal to gf4. Now we know f4 is equal to 1. So it is equal to g of 1. Now g of 1 is equal to 3. So we get g of f4 is equal to 3. Remember that 1, 3, and 4 belong to this set, which makes the domain of the function g of f. So now we can clearly see g of f is a function from set 1, 3, 4 to set 1, 3. And it is given by g of f equal to set of ordered pairs of 1, 3, 3, 1, 4, 3. So we can write it is equal to set of ordered pairs of 1, 3, 3, 1, 4, 1. This is the required answer. Hope you understood the session. Take care and goodbye.


всёRC attraction shall have power to punishats any person who obstructs or abuses it's process or disobeys any of it's orders or directions or does anything which tends to prejudice the case of a party before it or tends to bring it or any of it's members in relation to अगर कोई शक्छ खरते कर पर से पाजगदे परच्छ ने than to purseedings of the commission into hatred or contempt or does anything which by law constitutes contempt of court with simple imprisonment which makes tend to six months or with fine which makes tend to 50,000 rupees or with both. तो परश्छ नेच्मेंत टिक पाबर थे हैं। So there is the power of the punishments. अद्यॉटिकेशन, से अब रहाित नहीं ख़ाद, अद्किर्मन लेँगा, अर नाद व्रेन, और म़में लेगा, तुसर्द and शांशाद, अर घर आच्च कोसनावाद तैंछा तादा, अद्गदा, अद्गदा और और व््ठादाद जास शोगरे, लेगा और ये शादायं � प्रुस्टिकुशन का क्या मतलव होता है, the institution and conducting of legal proceedings against someone in respect of a criminal charge. अगर प्रुस्टिकुशन का क्या मतलव होता है, if there is a criminal charge, if there is a contravention of law, तो इंडस्टीर लेशन के पास ये रहित है के उसको प्रुस्टिकूट कर सकती है. मैंटीर केसें, मैंटीर स्टूटिकुशन, for the purpose of dealing with the case of unfair labour practice, अववेज ते कमीशन is seized, the commission may proceed directly with the case. ये भी पावर है, National Industrialization Commission के पास के कमीशन जो है, labour practice is the mutallik. प्रुसीट कर सकता है, directly with the case, ask the provincial registrar within whose jurisdiction the case has occurred or is likely to occur to inquire into it and submit a report etc. Hope you have understood the topic. Thank you very much indeed.