All right, we'll go through the order flow here in bookmap. Risk disclaimer, trading futures involves a substantial risk of loss, is not suitable for all investors, past performance is not indicative of future results. For more information, go to bookmap.com, become a member there, and you'll have access to free resources. Then reach out to us at support at voloxpro.com if you have any questions or issues. So let me show you. You can get a free trial here. If you want to try bookmap and get up and running, you get a 14-day free trial. It's under the pricing tab at bookmap.com. There's two versions. There's the basic and the advanced, and you can see the price here. They are billed accordingly, and for 14 days is that trial, and the difference between the two are these add-on features that you can see here, and especially being able to trade right from the chart. If you're a quant or a prop shop, you can reach out to us here and contact us, and we can work with you if you have any sort of custom solutions. You can also read down here, click on this link to look at the comparison of the features between the different versions. Okay, so in the web portal area for the members, once you sign in, this is where you'll land, and I want to show you, there's a new webinar here, so if you want to register for next week's webinar, you can click here, or any upcoming webinars, that's where you'd click, and you'll come to the registration page, you'll see from the drop-down here. This is the current one we are in. Just click on the drop-down and select the next one here for the 10th through the 14th, and let's register, and it says registration complete, so verified, and you're all set. Now, under the Education tab, this is where you'll also find the book map recordings of the webinars as well as other videos, so there's a whole host of different things to view here, a lot of information, and I just want to show you where the recorded webinars are. You can go through some of the other links on your own time, but click on this link here for book map recorded webinars, and then click here for the playlist. This takes you to the recorded webinars page, you'll see all of the recorded webinars here in the playlist, if you scroll up to the top, this is the one from Monday. Okay, I had technical issues on Tuesday, and yesterday, another technical issue was not able to record either webinar, which is a pity. There was some good stuff in yesterday's webinar that we saw, especially, but anyway, we'll see it again. This market repeats, and we'll just continue on. All right, so let's go through the order flow, all right? Okay, we're going to look at the higher time frames, and we're going to get a macro picture. And then we're going to do three things here in general. Look at that macro picture, and then we're going to look at the micro structure, and get an understanding of what's going on, and we're going to look at the order flow within that micro structure. So higher time frames first, this is how most of the traders use book map, and they have many different trading methodologies, it doesn't matter. Order flow is order flow. So then we'll look at this micro structure. You can use the same type of analysis you do for your higher time frames in your micro structure, and then you'll want to look at, very objectively, read the order flow here. Most of the scalpers here will just be looking at micro structure and order flow. This allows you, this software allows you to really pinpoint your entries and exits in your trade management. So let's take a look. Let's see here, we can look at the ES. Today, let's take a look at the oil market, just for change it up a little bit, and for some kicks here, it's a little more volatile. We can see a move into a big drop from the other day. This was the oil inventories, we're right back up there. So I'm kind of interested in that level at the moment. So let's, let me expand this, step back here, look at the daily. Okay, you can see a big drop from back in March, right back up into this area here. So some interesting stuff going on there. Let's look at that 30 minute chart. Okay, so you can see we've been pulling back, and oil's been doing pretty well. All right, so back up into some of these areas here. We have the 52 figure up here, and this is where we dropped from before. So I am interested in that level, right around there, as well as the swing high, around 88, 51, 88. All right, and let's take a look at a five minute chart. Okay, all right, you can see the open here, 9 o'clock. Let me zoom in a little bit more. Okay, here's our 9 a.m. open, okay, and we've continued to the upside. And here's our level, 73 or so, somewhere around there, maybe 78, 77. And you can see the uptrend here. So we are in continuation from overnight session in the uptrend. Okay, other levels I'm interested in, right in this area here, somewhere around there, okay, around this 51, 50, that makes sense as well, due to the number. In fact, let me just put it right at 51, 50, okay. And yeah, I mean, there's some other subtleties in here, maybe this 57 area. Let's take a look now at the microstructure in book map, okay, in oil. And let me turn on my CVD. Okay, and I'm gonna, you might notice here, okay, so this is actually a small bug due to the change in time. Our advance for daylight savings, you can see at 1030, my CVD right here, reset to zero. So I have a reset here for both, I have two CVDs, I have the CVD here, which is, this is the cumulative volume delta indicator that we have here with our new book map API, all right. So let me reset these, you can reset them to zero at any point, all right. So I'm first gonna trash this one here and let's reset it, okay. I just wanna show you there's a few different ways to do this, okay. So you can reset it now, for example, or we can, and if I just click on that, you can see that book map will reset the CVD right away, and you can see it here, just below this window, all right. But I don't want that, so I'm gonna get rid of that one. And you can see we retain all the data here still for you, all right. So let's add one, and let's add it for today, and for this one, let's reset it for 9 AM at the cache open, all right. And I'll have that reset every single day, okay. Now we're gonna see this, it's gonna be a little different here. Although we do have a lot of price action at 1030, you're gonna note that the reset, if I zoom, I don't have, okay. All right, anyway, this will do the trick at 9 AM, but I don't have data that goes back as far as 9 AM. So it started when I opened up my book map, all right. Let's go to CVD here. There's another way you can do this. We can just reset this for today instead, okay. So let's just make this for today, okay. And let's make it for 9 AM. And you can just do it right there and edit it right here, all right. So okay, so I'm all good there. And just wanted to show you that, some of the functionality here. For those of you with this book map 5.0 version, okay. This is where you'll find that CVD. It's under the API add-ons configuration here, okay. You'll see a few different others here, but we'll go over them another time, okay. That's where you'll find the CVD. It will open up, or it will not open up the indicator panel. You will need to come down here and open it up with this. Click on this little arrow at the bottom of your price ladder, okay. And then if you want to get this read out here in the widget panel, just click on the gear or sprocket here. And then make sure that they are blue here, okay. That means that they are selected. And you can, for the menu here, the show hide indicator widget panel, all right. And then they'll show up here. Okay, so our levels again up here around 73 to 77. And then at the figure at 50. All right, Seth, you want to know how to use this tool with the CVD. Okay, there's three different ways to use this tool, all right. We're looking for divergences, okay. Or we're looking for accumulation, all right. We're looking for insight here and how this indicator will give insight. First off, let me go over how it works, how it operates, all right. So let's see here. I'm going to take some time here. I mean, we're kind of channeling anyway at the moment. I mean, we do see nice big cluster of volume up here and a lot of absorption up in this area, okay. So anyway, let me, we'll get to the order flow in just a few minutes. Okay, let me cover this. Okay, okay, I'm zoomed in here pretty closely. And you can see no transactions have taken place here, nothing, right. Okay, my CVD is flatlined. And the output here, numeric values in the CVD, and I have two of them. Okay, one is showing 13 lots and greater of trades. And the other one is showing just every single trade, right. So there are, they are zeroed, okay. Now let's zoom out a little bit here and we see some transactions. All right, so let me, okay. So we're at zero here and then all of a sudden, boom, okay. Four aggressive market buy orders take place, all right. So what occurs here in the readout for the CVD is we see that four lots have traded, okay. Our reading is now four, okay. We see the bump up here in the CVD, up to four. And our 13 lot filter has not, and let me, actually I'm going to add another column here. I'm going to turn this to a trades counter, okay. So now let's zoom in on this actually because this was three different events that took place, all right. Okay, you can note here, look at the timeline. We are looking at nanosecond, or yeah, nanosecond level here, or microsecond level. And there's three different events that took place here, right. Let's go through the first event, okay. This was one trade here, okay. We, one event that took place for volume of two. And my column's trade counter and volume counter shows me that very, very objectively. This is what occurred at this moment, all right. Now another trade took place, okay. So we had one event, now we have two events. So I know that this lot, this is a four lot size of one, okay. We can verify that, okay. Just hover over this area, see it says one, this one says two. The next one, this one says one as well. Four lots have traded three different events, all right. And now my CVD shows four, right. And it also gives the output here of what occurred, okay. So now we're going to see, hopefully here, all right. We're going to see a cell, let's see here. I'm just way too zoomed in, okay.  As you can see right in here for five. Well, the CVD is cumulative, cumulative volume delta. It's showing the volume and it's showing the change in the volume. We had positive volume with market buy orders, now market sell order is negative. It just adds them together. That's it, that's all this indicator does, okay. And it's showing a value of negative 24. So there are more sellers than buyers, okay. It's also because of this one is in the, well, in the window. And as I continue to zoom out, now we're getting overall view of what occurred, okay. With the aggressive volume, okay. Now the other output here is the CVD for 13 lots. So we saw trades that took place and they were only for small lot size, okay. One was two, the other one was one, and the other one was one, all right. Those are gonna be filtered out in the second setting here for the CVD. And this is a great feature, all right. So what this allows you to do is look for larger traders, okay. Anything that is below 13 lots, it will not display. Anything that is above or 13 lots or above, it will display. And you can see, so we have a skew here. Larger traders are actually more on the positive side with 754, okay. They're being more aggressive. Y13, this is a setting from Futures Trader 71 and I've just kept it. So I would use your own studies for this and take a look here. We can play around with it, if you like, that's no problem at all. And try to gain some insight from it, okay. We're in this market, in the oil market, okay. Now he was using it on the S&P E-mini. In the oil market though, is this really helping us? Maybe we want to lower it down a little bit, all right, and look for maybe traders over, I don't know, over 10 or maybe over five or something like that, okay. But we'll just keep it at, well, no, I'll show you how to edit that, all right. So we'll edit that here, we'll click on CVD13 lot, okay. And now we're going to just lower it here, okay. And it does it on the fly, all right. So now we're looking at 13 or greater, all right. And there it is, okay. So maybe this gives us a little more insight of like in some of these areas, okay. All right, what does it show? All right, let's get back to the original question here. Is that going forward, is it, is from, Michael is from, it starts, the CVD counter starts from when you open up book map. However, I just showed you guys some of the ways of resetting that data to zero it to whenever you like, okay. So it's a real nice feature, I mean you can, like after 11, like right here, you could look at maybe what that CVD is showing you at that point, okay, by resetting it. Or you can just hit reset now, by when you change the large lot.  I mean, this is not a strategy, this is just data and an output. But it has a lot of flexibility here for you to put something together in any sort of way that you like, okay. The filter also allows you to not just filter the larger lot size, but also smaller lot size, all right. So for example, we'll come up here, let's click on it. So now I'm looking for minimum accountable volume size, okay. So only display if that minimum accountable volume size is a five or five lots or greater per event, okay. There's a maximum as well, okay. So we can look for a maximum here and we can input this. We're just seeing a nice drop down into some of these levels here, okay. Getting down to our 5150 area, right, okay. So anyway, yeah, I'd like to cover that for you guys. Got caught in the CBD stuff here. All right, the minimum accountable or maximum accountable. So it's the opposite, right? So we're making a cut off at like, I don't know, with oil we can make it 20, right? So this is actually now gonna display. Actually, let me put that down to, let me just uncheck that, all right. Let's go back to the regular one here, and then we'll put the max at 100, okay. Or we'll make that one 20, okay. So now I'm filtering, the green one here is only showing me any activity here, any events that took place for less than 20, okay. So one on up through 20, okay. They might have traded 19 lots in one event, okay. That will display here in the CVD, okay. Anything more than 20 though, it will not, or 20 or more, all right. So that's how that works. So you can really put up, you can input all sorts of things here to look for, you know, and study different volume measures here, all right. So that's the idea is to offer you that flexibility. Okay, all right, so how do you use it? All right, well, there are many different ways. There's, well, there's three different ways that we're gonna cover, okay. This area up here, a lot of absorption, okay. But price still did advance through, right. We're looking for areas where there's absorption, but price doesn't really advance, okay. So let's zoom into this area here, all right. Okay, look at the spike in right in this area right here, okay. So we spiked into this high level of liquidity here and we traded. There's no question about it, right. We can see that the aggressive buyers that took all of that liquidity and then some, okay. It actually went a little bit further up in this area here, okay. But then we went sideways for a while, okay. But there's a spike here in the CVD, big spike, okay. But look at price movement here. What did price do? Nothing, right. It just went sideways, okay. So this is showing absorption, okay. Larger traders are absorbing price up at this area, all right. Now, if your strategy is to look for areas of absorption at your levels and you're starting to identify larger players, then you're starting to look for reversals, okay. That's a potential strategy, okay. Now, we continue to come up to the upside here and we continue to absorb, okay. Larger players are getting filled up in these areas here, all right. Okay, and you can see that was a high that I have so far, right. So this is showing you the absorption, okay. We saw the initial absorption here. Now, this one's a little trickier. I mean, you can see that price did continue on up to the upside and they continued to absorb. But we did get some movement, right. We wanted to see when, like in this example here, there was no price movement, but we did see the spike in the CVD, all right. But, you know, this one's a little harder to read. They are absorbing, but we are getting a little bit higher movement and price, okay. We're looking for big moves in the CVD here, but price going nowhere, all right. So they're just sitting there absorbing with limit orders. And that gives you insight to that divergence, right. Okay, so it's divergence that we're looking for. We're looking for, you know, price to stay flat lined, but the divergence in the CVD still going to the upside, okay. Giving you clues to larger players absorbing price at these levels, all right. And you can draw those divergences in, you know. You might want to draw your 10 line up in here. And let me show you, for example, an image, okay. So just a moment here. All right, so other areas of absorption right now, okay, on that CVD, okay. Down at a level we're interested in, 51-50, okay. So, you know, looking pretty good. Anyway, let me show you this image. It's going to be quicker. Let's see here, okay. And you know what, I'll throw these into the handouts folder for you guys as well, okay. So, you know, here we can see that there was a divergence here in CVD as it continued to go up here. But look at the price structure, right. Higher high or a high up here, a lower high here, but we have a higher CVD, right. You know, that's showing the divergence. And let me show another one, okay. That's absorption. And then exhaustion is the other one. And we'll go through this one as well, okay. And I'm going to throw these into the chat for you or the handouts folder for you. I don't know if it's allowing me here, hold on. Okay, well the absorption one is there, okay. Let me try it again. It's not allowing me to. Okay, I'm going to get rid of the CME rule 575. And we'll input the, I just won't do it. Okay, let's try it again. Okay, well I'll just have to show it to you. And you can email me at support and I can help you out there, okay. Anyway, let's see if we get that divergence in any of these areas here. Not really, not really, okay. I'm looking at some of the swings here and comparing. I mean we do see kind of a little bit of divergence here with this CVD for the 13 lot, right. Which we changed down to 5 now. Okay, back up into this area, okay. We're making it a lower high, okay. But look at the CVD here, okay. It's at the same level here, right. So this one is correct. It means it's showing a regular market, right. But the one that's filtered for the larger lot size is showing that divergence, okay. So that's another way to read this, all right. And let's go through exhaustion, okay. Areas of exhaustion. So what you're going to see in areas of exhaustion is you're going to see price continue to move down. Okay, it's the opposite here of absorption, okay. Price continues to move down.  And looking at the gold market, we'll go through this example here, okay. So in this image here, price continued to actually move up here. It was making slightly higher highs here. But the CVD was not at all, right. So it's the opposite. Like price is going up, but the CVD is not, okay. And the divergence is the opposite of the absorption, okay. So, and you can see, look at the volume that traded up here, okay. Up into a higher high up here and very little trading. Well, it just exhausts out and falls right back down into where it can trade.  And we go sideways for a while, but we continue to the downside, okay. All right. So that's the other way to use this. I'm sure you guys can find all sorts of information about humitive volume delta indicators on the internet as well. You know, this is a pretty common indicator. And we're just showing it here within book map, okay. So that you guys have it. And the other one, now this is a great one. I think this is my favorite is the, and I covered this on Monday. And let me find it here just a moment. Okay. Okay, now I'm going to input this into the chat for you. All right. This is under the book map order flow video snippets here. All right. It's in that channel and or playlist. And let's just look at this one here. Okay. Yes. I'll go buying activity. All right. Now, we're going to input this into the chat for you. So you guys have this link. There you go. All right. And I don't see that kind of activity occurring at the moment, but this was great to see. Okay. Let me go large size here. All right. So we're looking for accumulation. And the CVD is, and I don't have a CVD output for this, but I can tell you exactly what is going to be going crazy to the upside. Look at all the aggressive market buys here. Okay. But small size, right. They're accumulating position without really moving price against them. I mean, it is going up, right? But slowly. I mean, it's, it starts to advance here.  All right. They can continue to lift the offer here, but they're getting their position on at these little higher, higher areas here. All right. And this is going to, your CVD is just going to, it's going to be exponentially high at this point. All right. And, but price isn't really moving up a lot. Okay. Now you're going to see this in book map all the time. You're going to see that the aggressive market buys here with small size just continues to at very, very sequential time intervals is lifting the offer or hitting the bid and they're accumulating positions. Okay. It's, it's, they're accumulating with small size instead of their setting their limit orders where they can absorb large size and get a good level. Larger players can get the price they want with their limit orders. All right. This is kind of another way of doing that with small size and just accumulating it over. So their average price is going to be between here at 2180. Okay. On up to 2183. So their average price is going to be, was that, yeah, that's 80. Okay. Their average price is going to be somewhere around here. All right. Around this 81 or 82 area, 81 and a half. All right. So that's another way instead of accumulating by absorption. Okay. They're accumulating with their, their size here. Now you're going to be able to see that in book map. All right. Because we don't, we don't aggregate the data. Okay. If you look at another chart that like a footprint chart, it's going to be aggregated. You're just going to see a larger number here. All right. So instead now we're really exposing what's occurring here in this market and you can see that they just continue to absorb. And this is an algo that's working these levels. All right. And this is, this is what book map really shines. It gives insight to what's occurring here. And I don't know if you're going to be able to find that with other software because they will aggregate that data. All right. Instead you can zoom into, we can zoom in and see the nano second levels here with book map if, if you so desire. All right. Okay. Okay. All right. So that was a rather exhaustive explanation of the CVD, but I think it's important to, to cover that. So you guys know. And we did, did miss some of the order flow stuff here, but this was our level of interest at this 51 50 area. And if we zoom in here, let's see if we get any of that absorption. All right. And here you're getting the, some of that absorption in this area here. Okay. Also down here. Okay. They continue to slightly go down to the bottom here or you know, a few more ticks down lower. Okay. Just below the 51 50 area. Let's see if we, maybe we can see some of that accumulation. Not really. Not really. And also let me bring this up a little bit here. Yeah. I think, well, for us, I mean, the way, the way we've been looking at this is, it's, it's these little areas here where we see, you know, we're looking at our microstructure and our swing analysis. Right. We can see them starting to, well, you can see a little bit of accumulation. It's not really that clear. It's not as clear as that example I showed you on the YouTube channel. But we come up and we start to trade into and above this little level here. Okay. Up into here. And we're starting to see that. Okay. So the swing analysis, the microstructure is broken and looking for pullbacks, areas of exhaustion into some of these other little, little areas where it, you know, maybe exhausted before, like down here. Okay. Or, you know, maybe, maybe in this little swing here. Okay. And we get the continuation to the upside. Now, where have we gone? All right. We've gone up and we've gone a little bit shy of it, but just about where we broke from. Okay. So we are still kind of, it's still trending down. As you can see. And we didn't quite get up there and we saw that we kind of exhausted out right in this area here. Right. Okay. Now a nice little cluster of volume here to the downside. Okay. And they're getting pretty aggressive with their limit orders here as well. Okay. So, yeah, at this point here, I mean, with the volume that traded down here, maybe look for, we're looking for maybe a small pullback if we get it. And maybe we can test down into this area here. Okay. And there's still a lot of buying that was up here though. So it's really kind of both ways right now. I'm not really getting a good read on it. If we came back up into this area here, just a little bit higher, I think we would add a little more clarity and to see maybe the sellers really take control here. But at this point, the sellers aren't quite in control. I mean, we see the aggressive buying that has taken place and some of the selling is starting to come in though. Right. So it's a little bit both ways right now. Right. Okay. Let's see here a few more questions and we'll wrap it up. Is there a way via the mouse to adjust the vertical scale on the CVD panel? This is addressed in the next version coming up. Okay, Adrian. Yeah. And the way it's going to be addressed is you can have all your resets and, you know, all the same settings are still going to be there. However, what is going to show you is the chart range CVD. Okay. That's how it's going to work. So, like, for example, in the ES, you know, there would be like, you know, tens of thousands or, you know, or more volume that traded and, you know, it's not giving us a really good output with that CVD because we don't see the distinction in smaller values. Right. Because there's just so much volume that trades. Therefore, what we're going to show is the chart range and the highs and lows within that. And then you'll be able to see the distinction. And you'll be able to filter it very quickly. Okay. The way that we filter for our imbalance indicator as well as for our volume columns, okay, to study certain areas, we just put it within our chart range. So, for example, if we wanted to study this area up here, okay, we can just put it within our chart range. Right. And we're looking for, you know, maybe up here with this imbalance indicators. That's going to give us the output for this and as well as our chart range trades counter profile here as well as our chart range volume profile here. Okay. So, you can see the, you'll get the computation for these profiles here. And then the SVP is when I opened up book map. Right. So, that's how you can utilize this chart range to give you insight using your data columns and then with the next version also with that CVD. Okay. All right, guys. Well, anyway, like I mentioned, rather exhaustive study of the CVD, but I hope that helped. And let me know if you need anything else regarding some of those images. We can send those to you. Okay. Let me try one more time here and see if I can get it into that handouts folder. No. It's not allowing me. Okay. All right. All right, guys. Well, yeah. This is, I mean, it's showing recorded here on my go-to webinar. So hopefully this recorded and you guys can access it later if you want to reference it. Okay. All right. Yeah. Thank you, Michael. Take care. Bye-bye.


OK, we need to present our little experiments with orchestration in the OpenStack Cloud. We'll get to sort of the technical problem statement and stuff in a little bit, but to begin with, for those of you who may, OK, we'll go the old fashioned. We'll just press buttons on the keyboard here. For those of you who may not know about PayPal, we are a publicly traded company. We were a part of eBay until mid-last year, and we split away. Second quarter, 2016 results, $2.5 billion in revenue. This quarter, I believe, the results just came out last week. We're a little above that. The 29 transactions per account went up to 30 transactions per account, which is a little low. So I encourage all of you to use PayPal. Braintree is another, so you can see all the PayPal properties. Braintree, Venmo, Zoom, these are all acquired by PayPal at some point. Integral part of PayPal business now. We have 188 million active customer accounts in Q2.  But essentially, the company's strong, big, growing, healthy. I think the stock went up by like 10% in the last, after the earnings report as well. Going to the infrastructure, right? So we have thousands of engineers over tens of millions of Java nodes, CC++ code. We do over 1,000 releases every year, thousands of deploys literally every day. Our cloud is, for those of you who haven't seen a PayPal presentation before, we deployed in three different regions, all in the Western United States, Salt Lake City, Phoenix, and Las Vegas. We have 10-plus availability zones distributed across those three regions. We distribute those availability zones into what we call the production cloud and what we call the Dev QA cloud. The Dev QA is where practically all developers directly interact with OpenStack, with Horizon or CLI or API. They'll create their VMs, create the block volumes, right into Swift. The production zones is where it's strictly controlled. The pass layer or a release engineering team will deploy applications in there. Within the production zones, you have sort of an active, passive deployment system. Right now, we are moving towards an active-active. So you have applications deployed across availability zones and across regions for maximum availability. Within those three regions and the availability zones that we have, we have close to 500k cores deployed, 10,000-plus physical servers, 100k-plus VMs. I think the number was closer to 150k the last time I checked. Close to 10 petabytes of storage that we have in the system. I think we have close to somewhere around 2,000 to 3,000 PayPal applications that are all running in our private cloud, not a public cloud. The key thing is our web tier and mid-tier applications are practically all running in our open-stack cloud. The data tier is still outside of cloud. I made a presentation at New York in the open-stack days east. We are looking to start moving our Kafka Elastic Search, NoSQL databases, into the cloud starting in 2017. And I think as we make more progress, maybe in the next summit in Boston, we'll talk more about that. Sort of a quick overview of the journey that we've had in 2012 or so. We started with 16 servers. These were DECOM servers that IT was going to throw away. We said, hey, can we have those? We played around with it, deployed open-stack SX. This was purely a POC. And by the time we were done in 2013, we were actually taking 40% of our holiday traffic on an open-stack cloud with our web and API tier deployed there. In 2014 and 2015, and remember, we were still part of eBay until mid-2015, all of our platform as a service layer, which used to run on bare metal, started deploying on open-stack cloud, total complete PDLC support, all of our web API and mid-tier is now running on open-stack. And of course, when we split away from eBay to move all the PayPal workloads from eBay data centers into PayPal data centers, we built the world's largest availability zone, running open-stack, 2000-plus servers, three Nova cells. We don't like... How we operationalize it, we can give a separate talk about that, but three Nova cells, each with about eight or 900 hypervisors, 2000-plus hypervisors running in a single availability zone. In 2016 and 2017, like I said, we're moving stateful applications into our cloud. We are focusing a lot on efficiency and reliability. And of course, going with efficiency and reliability, automation becomes key. So there's a lot of focus on automation, making sure that there is as little manual intervention, as little manual deployment remediation as is needed. And that's kind of what this talk is about, how we are orchestrating into the cloud in a more automated way, in a more scalable way. Before I go further, if there are any questions, we can take them in the end. If you want to interrupt, that's fine too. We can answer questions in the middle as well. And I have a feeling we can run through these slides very fast or there'll be a lot of time for Q&A at the end as well. So this is sort of the state of affairs that we had maybe in the beginning of this year. And I'll go over what this picture means. So all of these nodes that we are talking about here on the right side of the screen are all your compute servers.  The two nodes are running the puppet master. Puppet master in turn goes to Foreman to pick up the config for each of these nodes. Puppet master has a database that shows I have these many nodes in the system. And say for a controller profile, this is the config for these profiles. So now when one of these nodes comes over to the puppet master, what it does is it goes over to Foreman, grabs the config, and then compiles the entire puppet profile for that node. What it used to do was now, again, multiple reasons. One, this becomes a bottleneck real fast. So in order for us to deploy a complete AZ, and we went through that as we were upgrading from one OpenStack version to the other, literally for 1,000 nodes in the system, you would take hours for it to have all the puppet config deployed into each of these systems. So we would be done with the code upgrade within less than an hour. And then we would wait hours for each node to upgrade to the latest config. The next slide, I sort of highlight the problem. So the master, of course, does not scale. We have issues with large number of servers because it's compiling the puppet code for each of those nodes. We have complex dependencies. So wherever you have multiple different subsystems within each node, getting to the dependencies where RabbitMQ profile is linked to the NOVA profile, NOVA is linked to Neutron, all of those things have to be compiled by the puppet master. And it can get out of sync very fast. Monolithic deployment, what happens is because the master has got to compile the puppet code for each node. It has to compile the entire puppet config. And so now when we upgrade any one module, we literally are upgrading or changing everything, redeploying it in each node, right? Faced rollout on all servers was a pain. I mean, again, this is not necessarily an issue with the puppet master, but this was something that we didn't have a really good mechanism for. So when we would roll out something using puppet, it would actually roll out everything in the entire easy, which is not such a good practice. Any time we had failure, any one of the nodes failed, the puppet compilation failed in the puppet master, we would have drift because now we had nodes sitting with different configurations. We wanted them to be all identical. Puppet infrastructure management, the puppet master itself, the web if something failed, the foreman failed, we had essentially created a single point of failure. So that itself was a pain to manage. The solution itself lay in deploying a masterless puppet system. We eventually went with that. I was talking to Yuri, who used to be PayPal's nominant, he says, oh yeah, it took you four years, but you got there. It took us some time, went through a lot of challenges, but finally we've deployed that. What we have is, so no puppet master, we'll get to, let's do one thing, let's move on to the next slide, where we actually describe what the system looks like. So this is sort of what the end state is. So there is no puppet master, no foreman in the infrastructure at all. Each node, effectively when you onboard it, it gets a puppet environment package that's onboarded on it when it's onboarded using Ironic. The node runs puppet. There's a puppet factor that's deployed into the node at onboarding time. And at runtime, it basically gets the appropriate packages and the config from the wrappers. So it's very simple scales very, very easily. You can do phase rollouts by changing the puppet factor for a select sort of nodes. And instead of deploying it everywhere, you deploy it in 1%, 5%, 10%, 20, 50, and do a phase rollout. You can control each availability zone. You don't have to roll out in all 10 plus availability zones at the same time. And the data itself included in the package, it's very hierarchical, which allows you to sort of manage those dependencies that we were talking about earlier that get complicated very fast. It allows us to manage that very well. With that, I'm going to hand over to Venkat, who's going to take you over to the rest of the presentation. Hello, everyone. So where are we with the current journey? So we have already rolled this out onto four AZs. And we have started seeing the benefits. Things are working pretty well. And a little bit of insights into the acronyms used on this slide. The VSB, WISB that you see here is what it should be. And WIRI that you see is what it really is. So basically, the idea of VSB and Vary is to capture the drift that we have in the system. Last year, we had an outage. And most of the problem with that was we had different patches and drift in the system. So this VSB and Vary models enable us to catch all those drift. And we will have the system with node drift data. Another key idea of this masterless puppet project is to have the config data also under version control. Like earlier in the foreman model that we had, when we changed the config details, we don't have a history of what has been changed. But when you move this config data into a git, then you have a version control of what is getting changed. And you have a track of the changes. That's one of the key idea of moving this into this masterless puppet and having the config data also go under version control. Moving on to the next slide, we have already started seeing the results of this masterless puppet. And especially with the build and deployment time, earlier it used to be ours. And now it has got reduced to minutes. As Anand mentioned, easier rollout of changes. Like this is not specific to this model. But as part of doing this infrastructure change, we also started rolling out, actually modularizing the components so that we can roll out in the phased manner. And also, as he said, in the earlier model, we used to roll out the changes to all the computes in one shot, which was not a good strategy. So in this model, we have the control and we have the leverage to roll it out in a phased manner, like one person, five person. And if things are not working well, then we have better control to roll back the things. And if everything is looking good, then we can roll it out to all the computes. As again, Anand mentioned, we have less infrastructure components, like we got rid of Foreman, we got rid of Puppet Masters, so we don't have to maintain these servers anymore. And as I mentioned about the drift management system, this vis-v-enviary leverages us to capture the drift. And we are working on building dashboards to capture all the drift details. The next steps, since we saw the benefits already in four Asys, we have plans to roll this out into all other Asys in the next couple of months. And we are also working on building the dashboards to capture all this drift details across Asys. Currently, we have a hypervisor level config data captured as part of the vis-v-enviary details. We also plan to capture the application configuration details drift also in the vis-v-enviary data, so that, like for example, a NOVA configuration change, whether we have rolled out 3.2.1 to all the computes or whether we have 3.2.0, we can capture those kind of application level drift details also using this drift dashboards. The integration that's mentioned here is about the configuration management system. We have this preparatory system that was developed and open sourced later. This configuration management system is where we define the vis-v-enviary modules, models, and then we capture the computes, updates this VIRY data using the puppet fact. That is, when the puppet runs in the computes or in the controller nodes, they get the puppet fact information, and they publish it to this content management system DB. And the key thing that I would like to emphasize here is treating the config data also as code. So not just changing the config data in some key value database or in a flat file and not having a track of that changes is not a good thing to do. So we wanted to be able to track the config changes also, and it's a good idea to have them as part of the version control as well. Here is the contact details, like if you guys have any further questions or anything, you guys can feel free to reach out to us. Like I said, we were going to run through these slides pretty fast, so there's a lot of time for Q&A. No questions? So like I said in the beginning, Kafka Elastic Search, No Sequels. All of those run outside of Cloud today, and we are looking to move them into Cloud. We can talk more about that offline, because this is really not the topic here. But I'll be happy to sync up with you offline. So that's where I sort of pull out my product manager card and say, I don't know. What we'll do is, Ritesh and Raj and PK, who worked on this stuff, they'll know the more technical details on this. We can get back to you on that. And also, do you know how you're orchestrating your execution of 1%, 5%, 10%? So I believe there is some Ansible scripting that happens that allows you to change the higher data for specific nodes, and sort of roll that out in that face manner. Thank you. All righty, everybody gets 20 minutes back. Thank you. Thank you.