talk crypto this is episode 30 today we're gonna be covering all of that and we just got some breaking news right now let me actually pull it up here on my phone I literally just saw it as I was going live because today remember the today was a Fed rate decision and as expected they have the left interest rates unchanged Federal Reserve leaves interest rates unchanged remains at 5.25% so that that's pretty much what was expected we just got that in that at two o'clock now at 2 30 we have the the press conference for Jerome Powell the head of the Fed he's gonna be speaking and we have to kind of try to pay a little bit attention to that because if he hints at either any type of cuts any type of hikes market is gonna react is gonna bring volatility into the market so we can see right now the instant reaction is everything is going up so if I pull up the the monitors here if I pull up if I pull it up right here we can see Bitcoin just got a nice little boost if we let's put this in the last five minutes just so that we can see as soon as that report came out Bitcoin is up about half a percent in the last in the last two minutes really it's up let me see it's about $200 in the last two minutes since that was reported so this might this might be the bounce that we that we're gonna get here the bounce back to the upside so that's something to watch for here let's see how how we go it's either that or it's either I went live so Bitcoin started to go up it's one of those we know that whenever I go live for some reason Bitcoin tends to go up so we're gonna stick with that story and and yeah guys so it's it's been it's been a pretty wild pretty wild few weeks so we had so I was actually out of town for last weekend and and while you know it was it was difficult to trade when you're not on your PC when you're not when you only have your phone so it was hard to keep up with everything while traveling and of course that's when Bitcoin decided to go crazy if we pull up the chart here in the last one was it the last few weeks this is a week where I was out of town and we hit well actually this week and we hit a high of what was it 44,769 that is insane guys that is wild so that's that's currently the new highs and we can see that we had one two three four five six seven eight eight weeks in a row of green candles guys the last time that that happened was in 2017 at the beginning of the the previous of that bull run let me see does this this doesn't even go back that far let me pull up another another chart here for Bitcoin let's see 2019 18 so 2017 should be around here somewhere let me remove this one two three four five six one two three four five six seven one two three four wait one two three four five six seven eight so right here 2017 from April 17th to about July June 17th so that's the last time that we had this and this was if you look back to when exactly this was this was at the beginning basically of that that next bull run it was it was in the early I guess I want to call it the early stages it was right kind of in the middle but it was definitely in 2017 so that's something that we haven't seen in a very long time basically six years since we last saw something like that now don't mind these things that have these markings now today I mean this week so far we're down this is the first time we're down in eight weeks so that on the ninth week but look at this candle it's it's it looks like it might be printing now we still have a lot we still have to end today we got Thursday Friday Saturday Sunday so we still have about four days left on this candle so a lot of things could still change but right now the way it's setting up this is this is what's called a bullish pin bar so usually when you see a bullish pin bar that means that price tried to go down the sellers tried to push prices back down but there is just too much too much demand that pushed the price right back up right so sellers sellers it basically means sellers ran out of steam right they ran out of sell orders and the buyers the buy the demand to buy is just overwhelming the sellers right so it's pushing that right right back up so that's basically what we're seeing here that's basically what we're getting here and again that that would be a bullish candle if it were to close like this now now a lot of times when we leave wicks like this so we do have to be wary of them because price does tend to like to fill wicks at least the 50% of it so it might not be a full fill all the way down here to $40,000 but we could potentially get a 50% fill which would be somewhere around $41,000 so something to keep in mind if we end you do end up closing like this you know and depending where it closes of course the middle of that week is going to be different so just something to watch there but as you guys can see everything is it's it's been wild like we've gone literally from $25,000 from basically this candle right here and it's been up only and this started back in September so September since September at $25,000 after we got three weeks in a row of really nothing there is no movement whatsoever we got three weeks in a row of that and then all of a sudden just up only including eight weeks in a row here two months in a row every single week was green and now this this candle this week is fighting here to get back to that green that would make it nine weeks I don't know if we've had any years where if we had nine weeks in a row of green I'd have to look back but yeah that's currently that's currently where we are right now you can see we have two different trending support levels here we have this main level right here that's been the level since we started this back in November so this is from the bottom right we've had this basically the support here currently it sits right around $30,000 so and you can see that it's in line with this big support here at $30,000 so you can see historically that support has played a significant role in Bitcoin's price so this if if we were to see any type of drops I think this would be the bottom here which is around that $30,000 mark now that's a $12,000 mark a $12,000 drop I don't expect to see a $12,000 drop unless something really bad were to happen because I mean imagine it would be from from the last high to let's say it dropped to this support that's a 31% drop again even during a bull run 31% drops are normal right there as normal as it gets but again with with Bitcoin spot ETFs looming I don't expect a 31% retracement here even if you look back at at the last bull run and this is actually what I had drawn here I was looking because I was looking at the past bull run and seeing what the pullbacks look like how far back did they go and you can see here during the last bull run had a pullback was 14% 21% 9% 31% so like I said they're 31% pullbacks are not unheard of 26% and 42% so we've had even during bull runs we get these big massive pullbacks so we have to be careful with those so it is in the realm of possibility where something like that could happen right because we just saw that so can can we drop all the way down to about $30,000 it's it's in the realm of possibility because it's happened before in previous bull runs however another thing that I noticed when looking at those pullbacks though was that every bull run the pullbacks were less and less significant so the bull run before that the pullbacks were in the 50% range right and beyond then the last bull run the average pullback was about 20 20 was actually yeah about 20 25% was the average pullback in this current bull run if we want to start considering this a bull run the average pullback has been about 15% so that would be like these pullbacks here all of these here that ever since we started moving up here pullback pullback pullback all those pullbacks have averaged out to about 15% or less so 15% pullback puts us at around $38,000 again that's another major level for us I was thinking that's that's the level that I was looking at for a pullback I would love to get another opportunity at $38,000 because that would be basically a breakout and retest of a strong resistance point of a strong resistance that's now a strong support and if we look back on history again look at this look this is that level $38,000 look how much activity happened in there again over here it played out as a support look at all this activity there again right here major support so I would love to see price to be honest guys I would love to see price to drop down to that $38,000 range just test it a little bit and then continue on its on its way up that would be amazing and and the crazy thing is here so 15% which is has been the average pullback for us so far in the last year it's $38,000 of course significant support resistance zone and this is where the trend line support is so there's three different things there there's so we have massive massive confluence at that range so that's why I would love to get that there because that's basically free money guys if we were to get a pullback down here to $38,000 that's like I compare that to printing money like that's legal that's a legal money printer because at $38,000 there's so much there I would love to build a long-term position there on leverage I'm talking about leverage your your my Bitcoin long-term positions were built way down here right this is what we're building our Bitcoin long-term positions now I'm talking about day trade right swing trades really I would love to build a position here a leveraged position here and just let it ride into January because in January what what's happening in January we're getting the ETF approvals right now we don't know if they're gonna be approved yet but it's looking like the probability is to the that it's likely getting approved so because of that if we were to get any type of pullbacks to that $38,000 range guys that's that's like you're printing legal money here we would build positions there at $38,000 imagine a move at that point from let's say $38,000 I didn't grab it let's say $38,000 if we think you know in the next month we'll get to $50,000 right a move that's 31% move 31 let's say use 10x leverage that's a 310% return on investment if we were to get something like that which is wild right and I mean that's just if you're taking profits if you say you know what I'm gonna let this trade ride for for all of next year and let's just see what happens right I'm just build a small position just let it ride with a leverage through the bull run and think about closing it once we're at all-time highs and beyond that's a 85% move at that point guys and with 10x with just 10x leverage that's an 8x return on your on your risk and and if you think we're gonna hit a hundred grand then hey why not move it up to a hundred grand that's a hundred and 64% move with 10x leverage we're talking about almost 2000% return right almost a 20x there and that's not even counting the compounding effect because remember if if you're trading somewhere where you're receiving the underlying asset as profits right if you're receiving the underlying asset as your profit then as the value of that asset goes up it's basically it has a compounding effect as you're making more and more profits as its value goes up plus all the profit that you've made from the beginning its value is also increasing right so you're compounding those gains those profits as they go up and I mean I have a I'm working on a video for this where we're gonna build a small positions I'm gonna be anything crazy and we're gonna try to let it ride for the bull run like we're gonna try to let that position just ride to a hundred thousand dollars basically to either previous all-time hired to a hundred thousand dollars and see how much money we can make right the the the target is to make a full Bitcoin with a small position where we're not risking a lot of money that any average investor could potentially do on his own you know it doesn't have to be someone with a big a massive bankroll to be able to build a position that you can kind of let ride through the board through the bull market and you know make a full Bitcoin in return if it hits its previous all-time high or when it hits a new all-time high if you think Bitcoin is gonna go to a hundred thousand dollars you build a position around 38 or forty thousand dollars like it doesn't take a lot of capital to make sure that you don't get liquidated on that position so I have a video that I'm working on for that hopefully I'll be able to finish it this week so you guys will know you'll be make sure to subscribe to the channel turn on notifications so you're notified because it's gonna be time is gonna be of an essence for something like that for some type of strategy like that because there's gonna be an ideal entry basically and if you don't get in that ideal entry then your risk of maybe potentially getting liquidated becomes that much more so we'll be looking at all that hopefully I'll have that done this week but it's just I've been doing so many things that it's been wild to try to create content as well with so much going on let me say what's up to some of the people that's in that are in the chat right now what's up to Andrew Yanis Yanis is in here again great having you again in here Yanis if anyone else is in here make sure to drop a hello in the comments so I can say what's up alright so let's take a look at Teddy the Australian what's up Teddy let's take a look at what potential day trade setups I am going to be looking to make this week there've been a few we've made two trades this week in the trade room let's let's pull it up here give me a sec as I pull it up here where are they so we've taken three trades this week one of them got stopped out yeah so so the first trade so these are the trades that we took three days ago so the first trade was this was basically during that drop so we had this massive drop the other day right and whenever there's a massive massive drop or I feel like it's it's an overcorrection even though I do think that's an it's a healthy correction and that we could go a lot lower when it happens that that quickly because it happened in a span of 15 minutes if you guys weren't watching when it happens in a span that quickly I know for a fact that it has to bounce back up because it's not just going to drop and that's it right so so like if we look at let's look at the hourly and if if look at this look we're looking at that hourly chart look at this week that was a left behind right so we had this massive fast really really fast drop here that's usually happens because of liquidations and liquidity levels all that it's it becomes a cascading effect so when we had all that drop I down here started opening positions and I couldn't open them fast enough right this happened so fast that I could not open up the positions fast enough I couldn't even type in the chat fast enough because of how quickly this happened so I ended up entering a trade a long trade somewhere down here at the forty thousand dollar area and entered more at 41 and entered more at 42 and you can see it here if we look at the trade setups look at how I wrote this I wrote this line by line because of how quickly this was happening so we caught entries at 42 with I put I literally put setting up orders above 42 then the next thing long then stop loss right I was trying to do this so fast because then I also entered any theorem trade at 22 and then I had the we set up the the targets we ended up hitting our first target and and that was it on this one because we did pull back further as you can see in the chart we pulled right back down but you can also see the theorem one hit two different targets so you can see I needed I was like panicking I was like oh my god need to get these out as fast as possible and we hit the targets and then we tried to re-enter there the next day using smaller size because there was so much volatility I knew that it was a risk a risk your entry the second time around that it snaps that same level and we ended up getting our stop losses hit so but but that's that's part of it right you're gonna you're gonna hit some you're gonna lose some we ended we ended up hitting two of them we lost one of them so however you can see here we retraced this whole week so we spoke about the week earlier in today's live stream you can see that we traced this almost the entire week and then started consolidating here and now we've been kind of progressing up slowly so let's see we had the CPI data yesterday we have the interest rate data today so let's see how how it continues going forward I still think there is room to continue down we have this confluence here that the average pullback has been about 15% we have the trend line support over here and we have a big area here so all of this confluence right here and we have we have this these moving averages here so this is the 200 EMA on the four hour chart so a four hour chart I mean they're not as important but you know it is down here so there's a lot of confluence here at in this level it's not letting me draw for some reason what's going on here things going crazy can I draw no doesn't want me to draw all right I don't know what's going on with that but that's basically what what's been going on here so if we kind of zoom out into the weekly we can kind of see that it's telling us that story we zoom out to the monthly to see what the monthly looks like and monthly it looks it looks similar as get this out the way we have we have this massive resistance here that we've seen you know playing big massive roles in cryptos history and it's happening again like I that was expected so which is why I drew this resistance area here because when there's these massive massive areas of resistance and support you have you have to know that we're not just gonna break right through right even this one this one we broke through pretty fast I'm not gonna lie look at this like we broke through there pretty fast which is why I wouldn't be surprised for us to pull back to it because it happened so fast right we've had one two three four months in a row where we've been green so I wouldn't be surprised if we got a pullback back here to this level that $38,000 range right with this massive massive resistance up here so that those are the main things that that we're gonna be watching here over the next few weeks probably until we get into January I think in January once what what in the world I think in January once as we get closer to the ETF approval date I think market is gonna start moving up again and pushing towards that that resistance so this resistance is anywhere between 45 up to like $48,000 but then you have to also remember we have 50 here 50,000 is a big psychological number so we have to also take that into account so I think what could play as that catalyst will be the ETF approval I think once we get that ETF approval we can see Bitcoin break above 50,000 start running up towards that 60 I think we get probably a pullback we retest 50 at that point and then continuation higher leading up to that the Bitcoin halving right so Bitcoin halving it's coming up soon Bitcoin halving countdown so 128 days away the 20th of April 420 of course no coincidence right no coincidence that halving is projected to happen on 420 and the previous all-time high of Bitcoin is 69 is that a coincidence guys I think I'm not so that's currently where things are so so that's kind of my overall prediction I think you know leading up to Bitcoin ETF approval we start pushing back into this resistance if we do get approved in January I think we push past 50 consolidate kind of you know consolidate back towards the downside retest is 50 area and then as the halving approaches then we can see price start to move back up again and then after probably after the halving or at some point during the halving after the halving during that week we start pushing that 60 range potentially beyond 60 and we can potentially retest that the previous all-time high get another pull back down back probably to like that 60 range and then from there set I think at that point towards the end of the year is we set new all-time highs I would say summer to to end of the year set is when we're definitely setting up new to all-time highs stuff like that so yeah very very bullish as you guys can see long-term into next year and into the next two years that's why that's why I'm thinking we break like a hundred thousand dollars it is a conservative estimate for where we're thinking that Bitcoin could go because of where we are already we're basically at 50 already right and a hundred thousand is nothing for Bitcoin from 50 so and we're not even in the year of the halving yet and remember it Bitcoin goes up pre the year of pre halving the year of the halving and the year post halving so I mean we could we could literally go beyond 100 maybe even test that 200,000 range I know that's now kind of pushing the envelope and being a little aggressive but that's why I like to stick to my conservative numbers of about a hundred thousand for the next one for target right so now that we've kind of spoken about the bigger terms a bigger longer terms my outlook on it let's look at some day trades that we could be watching here we could be playing one of the day trades that I was that I've been playing is that $42,000 area I like that $42,000 area it's a big level there so I think I like breakouts at 42 I like a breakout and retest at 42 for long entries I like 40 as well 40 I love for long entries and of course 38 is the next level under that for long entries so any of those levels any of those entries for retest you can play those levels there for a long entry to build a position there now for shorts I'll be honest guys I'm not really playing shorts you can you can short up here if you want towards this resistance I am choosing mostly not to unless I see stuff like this where it's obviously not gonna not doesn't have enough to break through there then you can at that point potentially short but it's you're making like the odds are against you when you try to short against a trend so that's why the way that I the way that I play is I'm not really looking to short too much there are some potential spots that I'll look to kind of snipe on a short but that's about it for that so right now just playing those three levels that I mentioned 42 40 and 38 my three big levels to play here if you're looking to build any either scalping opportunities or just long-term opportunity long position opportunities there with Bitcoin so if you guys have any questions about anything that that I covered here just drop it in the comments now and I'll be more than happy to answer some of those questions for you guys we have the the Fed press conference coming up let's see yeah so it looks like the entire market basically moving up it says the Federal Reserve held interest rates steady for a third meeting and signaled a sharper pace of cuts than indicated in September projections so that's definitely some bullish news that means we might get cuts faster than than what we might have been expecting before Fed officials projected three rate cuts in 2024 that's very very interesting yeah so you can see that things are really setting up here for for Bitcoin to really have a massive bull run next year that's a thing things are everything is all the pieces are lining up and just fitting into place there because rate cuts are gonna be very very bullish for for Bitcoin overall so Yanis says can you show us the current liquidation levels of Bitcoin yeah I definitely can let me pull it up here what's the website high block hmm all right so taking a look at liquidations this is a seven-day heat map and we can see that right now the majority the biggest liquidation pool liquidity pool is to the downside you can see it's just below $40,000 hmm so that's that looks like to be the biggest spot right now on liquidity oh I'm not even showing you guys my bad there we go hmm so here we go so you can see that on the heat map there's a seven-day on the heat map just below 40 look it looks like it's around 39,750 ish is where the currently the biggest liquidity pool is right now to the upside if we're looking for some liquidity to the upside we can see that positions are building up here basically at $45,000 so that's what on the seven-day is showing us if we go to the one month let's go back a full month and you can see the biggest liquidity once again down at $35,000 so this has this liquidity down here has slowly been inching up so it's slowly moving up it's currently sitting now at $35,000 hmm now I don't think we get to $35,000 I don't see a reason why Bitcoin would drop that much but there's always a possibility right it's always that scenario we spoke about it earlier there's the possibility where Bitcoin could drop 30% in at any given time even in a boring so that's definitely something that we always have to keep in mind and to the upside the liquidity pools are in the same spot so they're building up at $45,000 and above right and at the current levels that we're at there's really not much you can see there's a little bit here below $40,000 again if we look further back three months so you can see three months now that now these are delayed so there's really no way for us to really know if a lot of these liquidity pools are still there but it seems to be below $35,000 right that's the biggest liquidity pool there and then if we zoom in actually let's let's look at one year just for fun just to see you can see one year all the way down here at $23,000 now I definitely don't think we hit that anytime soon I don't think we we see $20,000 again during this run so so yeah I don't I don't think we see that now let's go to the 12 hour and I like to zoom in a bit because looking at looking at it like this like we really can't tell where that everything is right so like to zoom in a bit here now we can get a better idea even then like it you know zoom in a little bit more to really see where those pools are and these are a little bit more consistent with where the liquidity pools are now they're not as significant though so we can see yet again the biggest polls are to the downside you can see here at $40,000 we have another one here at $41,000 and then we have one at $42.575 which is basically where the price is right now so I don't think it's updated I think we've already hit this poll here to the upside so we might potentially because we've hit this pool is there a possibility that price pulls back down into these liquidity pools that's definitely a possibility so that's something that we got there we're gonna have to watch there alright I hope did that answer your question Yanis hopefully you got some you got something out of that hmm no problem Ivan says I think playing short short right now with the Bitcoin mode with the Bitcoin I'm sorry I think playing short right now with this Bitcoin moment it's dangerous yeah I agree that's why I I don't like any I don't like shorting Bitcoin right now there's too much momentum to the upside we have the ETF stuff looming it's it's only a matter of time it's not if but when so yeah it's not it's not a high probability trade there to try to take with in the market so I totally agree yeah we can see Bitcoin is continuing to push up here so so that's that's great because when we started this live stream Bitcoin was sitting at about $42,000 $42,200 300 around there so once again you know we've gone live and and Bitcoin's price went up during our live stream it never fails right alright guys I think I'm gonna wrap it up I think we've covered basically everything that we wanted to talk about if you have any final questions let me know if not we'll wrap things up here as we watch Bitcoin soar here potentially retesting these levels up here so I expect if we get back up to these levels you know things will slow down here and we'll hit this resistance again but but yeah it's pretty much it guys no problem Ivan thank you thank you so much for tuning in I appreciate you hmm I we will be doing a a discount for the trade for the discord trading group coming up towards the end of this month so in about a less than a week as we approach Christmas we're gonna be doing a Christmas sell and we've introduced some new products into our into our discord if you guys don't follow us on Instagram that's really where I've been posting about it but we've introduced some new trading in our discord group we have the algo the algorithm bot now that's basically posting up trades if I pull it up here algo signals basically here it's posting up trades multiple times a day and basically what the algorithm is doing is it's looking for multiple conditions to be met multiple rules to be met and then building a plan around it and then it basically gives you the signals and then it tells you you know once it hits the targets or if it ends up stopping stopping out like this one so far it's been very very good so far this month this is just tracking it this month I haven't tracked the trades that it's taking today so I know we just we just saw that we took another loss there today this one hit its stop loss so that's probably the fourth losing trade that we've hit this month but without counting the ones that we hit today because we did hit some successful one today we're at about 89% win rate now the total max profit loss is if you played it perfectly got out at the perfect time so I don't expect you know in two weeks to hit 50 for someone to be hitting 53% unless they just you know they can see the future and know exactly where to get out the perfect timing but you should be somewhere in the middle of that so it you know if you can hit 10 to 20% like that's realistic I think that's that's definitely something that that someone can do trading with this following this you can see that this the the average that we're hitting the the targets target one target two three four five target one and two we're hitting over 80% so far this month target three we're just under 70% and then target four and five we're under 50 and under 40% so yeah this has been great here so this is something that we just introduced of course we already told you guys about the options if we haven't then options is basically we're playing very high big high probability trades I haven't updated the the recent trades that I've done so I do have to update some because we were hitting at a 100% win rate basically we hit 20 trades in a row but we did take a couple trades that were in the loss that we had to roll back so we'll talk a little bit more about that I have to once I update this but we're hitting at about a 90% clip right hitting 20 in a row it's insane so we're keeping track of all those as well and of course be leveraged signals right so these are the leveraged trades that we've been taking all year starting all the way back in January of this year we've taken about a hundred trades including the the last few ones that we hit including that loss that we hit there so all that's included in here and you can see that we've total trades 99 trades we have a total profit loss again this is if you were able to correctly predict and play every single trade and always hit the max you'd be somewhere around here I don't expect anyone to be hitting every single trade perfectly hitting always a max so you know somewhere below in the middle of this I would say is more reasonable more realistic around 60 70% on the year we've won 66 trades we've lost 33 trades so that's about a 66% hit rate we were recently at 70% but with so much volatility we've been we've been stopping out on a few trades while taking some swings they're trying to hit home runs so you can see here at target one we hit it at 66 target two at 45 target three at 27 so yeah guys we have these three different products now launched in our discord group we're very very excited for these we have a tutorial that I just posted up on here on basically the introduction to understanding the algorithm how it works and the introduction to how to read the signals and manage your trades there for the signals we have these the algo algorithm alerts as well they basically give you alerts on sell zones buy zones abnormal volatility bullish and bearish a lot of different stuff so we've been upgrading our discord with a lot of different features we're getting all of this ready to launch in the new year we've already started testing it out with our current members in the discord so if you want free access to all of these tools you could do a seven-day free trial right now so all you got to do is go to I haven't posted the link I'll post it in the description I'll post it in the chat it's walk comm slash Bitcoin daily I believe let me make sure with the what it is here I'm gonna find the website let me just copy the link here it'll just be easier to do so I'm post I'm posting a link in the chat if you're interested you guys can go ahead and go there I'm gonna post it here as well just so that we can see it let me let me take this out the way hmm so this is this is what it looks like and you're gonna have all the different products all the different you know depending what type of plan you're interested in what type of products you're interested in you could do leverage signals only I'll go signals option signals or the indicators so we're also introducing indicators to the group or if you want access to everything then we have the VIP all access pass as well and then as you guys can see we have a seven-day free trials basically on all of them so if you're interested in testing it out all you gotta do is click here pick which plan you will like if you decide to stay you're not gonna get charged this is only if you decides to to stay after the seven days you're gonna hit start trial and here you're gonna have to fill out your payment information and again this you're not being charged anything as you can see here total due today is zero dollars so you're not gonna get charged anything this is you get seven days for free you can cancel at any time as long as you canceled before the seven days are over you do not get charged anything you can test these things out for yourself to see if this is this might be something that you're interested in so that's how confident we are in this product that and that we're that we've been that we've introduced to our discord we guarantee basically that you're gonna like it that's what we're giving you an entire week for free in the discord so you can check it out for yourself Ivan you said which one do you do I do I recommend for you to start so it's gonna depend on what type of trader you are if you if you want to do that if you want a lot of signals then I recommend the outgoal signals if you want you know just some signals the signals that I'm personally taking myself these are with leverage that I'm taking then then this is mostly focused on Bitcoin and Ethereum then that's the leverage signals if you want the option signals and the option package so I recommend you check those out it's gonna depend on what type of person you are what type of trades you like to take I would say if you want a lot of signals I'll go signals is a way to go if you want fewer signals you want just kind of like more strategically up place signals which is what I do then then the leverage signals and right now if you sign up for leverage signals which is the cheapest plan you also get access to I'll go signals for the rest of this month but at the end of the month out you will no longer have access to the outgoal signals but you know you can test it out at least for the remainder of this month if you'd like so check those out guys I'm gonna wrap things up appreciate you guys I'll see you guys next one I think tomorrow I'm gonna do an outcoin report live stream where I'll cover I'll go through different outcoins and stuff like that so see you guys then peace and love


Hello everyone, this is financial author Ahmed Dunn of ameddunn.com on this channel you'll find financial travel and more videos just like the one you're watching right now If you like what you see, please give it a thumbs up and consider subscribing Hello everyone, this is Ahmed Dunn of ameddunn.com in this episode I'll be riding a rickshaw in Bangladesh, Dhaka and I'll show you some views from my last Bangladesh trip Dhaka is the capital of Bangladesh which has about 17 million population And there are about 600,000 rickshaws in Dhaka and rickshaws are actually everywhere in Bangladesh So it's a tricycle type of vehicle, it has no motor so it's human-pooled The main advantage of rickshaw is that it does not cause any environmental pollution So it's safe means of transportation in terms of pollution and otherwise it's a slow ride But if you take your time, you can enjoy the ride because it gives you more opportunity to view everything And it's open air transportation so there's nothing blocking you from air and sun So you can enjoy that So if you like what you see, please give it a thumbs up and consider subscribing And there will be more videos from Dhaka, Bangladesh coming up And there will be more videos from Bangladesh other places as well from my last 2017 trip Thank you and I'll see you shortly


Today we're going to spend half an hour or so talking about Bosch package rendering and collocated errands, which are two fairly recent Bosch features that will allow you to build simpler releases and achieve faster upgrades, which is quite exciting. This is not working. Cool. All right, quick intros. My name is Maria. I am a software engineer for Pivotal. I work off the London office and I'm currently on the team that offers contributions to open source Kubernetes. And I'm Maya Rose Grants. I'm on the PCF Redis Pivotal team and we managed something like 15 Bosch releases at the moment. Okay, so a quick look at what we're going to talk about in the next 30 minutes or so. I'm going to be honest, the title gives away quite a bit, but we will start with a very high-level view of Bosch. And the intention of that is not to cover everything that Bosch does in a very comprehensive way, but rather give us a little bit of context and build a little bit of a foundation to help us frame the second part of the talk. We will focus then on package rendering, which is a feature that Bosch added over the last year or so. And it allows additional flexibility and abstraction when it comes to specifying dependencies within the context of Bosch releases. And after that, we will talk about errant collocation that offers additional flexibility on where one of tasks that run on Bosch deployed instances also refer to as errant's run. Okay. So Bosch is talked about a lot at dinner parties and the such, and you might have heard of it as a tool chain, a package manager, a framework, a deployment manager, an orchestrator, a release engineering tool, among many other names. But it's so powerful because it's really all of the above and it offers concepts and tools in all of these areas. And that's why time and again, Bosch has been the go-to tool for operators to take software from source code that a development team, authors, and maintains through a series of steps represented very accurately by three dots there into a long-running and evolving system. Exactly how does it do that? What are those three dots? The first step is by offering a framework for software packaging. What comes under that? Packaging includes, first of all, instructions on how to prepare the software, a description on a description of dependencies of what other libraries or binaries or what other software our software depends on. And there are a few Bosch concepts that come into play here that are quite interesting. The first one is that of a Bosch release. And that is a flexible structure that both source code but also pre-compiled binaries can fit in and can be expressed by. Within releases themselves, code is organized into packages that contain the specification but also any supporting scripts for the software to be prepared on the instance that it will run on. And that means that it's copied in the right places, that it's properly compiled, and so on. All right, so after software packaging, second step is orchestration. And that again is a huge umbrella of things that happen but really in short, orchestration is the business of organizing packaged software into a running topology and arranging it into components, coordinating those components, taking on the deployment of these components and more specifically things like provisioning, things like interacting with the underlying infrastructure layer. And finally, addressing configuration management. So ensuring that the software that ends up on instances that Bosch has deployed is correctly configured. Specifically, how does it do it? You see towards the bottom of the list, we have some interesting Bosch concepts that come into play here. The main one is that of Bosch deployments which create a bridge from references to packaged software and a deployment on the other side. And it creates that bridge through Bosch manifests. When running on the instances themselves, the next step, software is represented as Bosch jobs. And then there is a mapping between Bosch jobs and a set of processes on the instance itself. Typically, one job is one process but it's not necessarily so. Even at that level, there's additional flexibility. So jobs can be long-running and in this case they're referred to as service jobs or simply jobs. Or operators can decide that a task has a very specific task, a very specific functionality to complete and is short-lived and in that case, it's designated as an errand. Finally, once a Bosch deployment has been orchestrated and has been created, Bosch is in the business of keeping it alive, keeping it healthy, managing its evolution and offers a lot of tooling in that area. What that means in a bit more detail are things like upgrades, for example, and that refers to keeping the underlying operating system up-to-date with things like Bosch stem cells which serve as an abstraction between the software that runs on the VM and the supporting operating system underneath so that the two can move independently. Things like updates come into play here as well and those refer to the versions of the software that run on the VM themselves and Bosch manages that change as well. Topology changes, any additions of instances, removals of instances are under the responsibility of Bosch too. And finally, any health monitoring and lifecycle management of instances with things like Bosch agent that is responsible for keeping a specific instance alive and healthy, things like monit on the instances to ensure health of the very specific processes and concepts like canaries and deployments where Bosch will choose to essentially try out a change on a subset of a deployment before extending it out to the whole thing. So this was a very high-level view of all the stages in the software lifecycle that Bosch offers tooling and gets involved in. Later on we're going to focus in two, so we're going to talk about vendor packages that come into play in the software packaging stage and then collocated errands that are most active during orchestration and the responsibilities of Bosch over a long-running system. And with that, Maya will take you over package vendering. All right, so we'll start with this diagram. And this diagram maps very, very closely to that process that Maya just walked you through. So you have your source code or maybe you're just wrapping a binary and your source code would also have its language dependencies or any kind of like test binaries and you have your package that kind of wraps it and that gets provided to a job which handles the orchestration of it. It will do the start, the stop and handle kind of the lifecycle of it and that goes to a Bosch release which was actually deployed on VMs. The other thing that's kind of worth maybe calling out is that it's fully atomic, it has all the bits it needs to run. Potentially you don't even need the internet connection at this point. If you look at the package itself, when you make a package with, you know, Bosch-Iron package, you end up with these two files. You have a packaging file which will copy the actual bits into the correct portion on the Bosch VM and then you have a spec file which will specify any compile time dependencies and the files that actually make up the package. So kind of the problem that package vending is trying to solve is that when you're making many releases, you kind of end up seeing the same dependencies over and over and over again. Things like programming language. And the problem that can arise is you can have all these inconsistencies. Like if you have two releases, you might call both your language pencies go, but in one, it's go18 and one, it's go111 and when you try to co-locate them, you're going to get naming conflicts. And hopefully you have right access and you can rename one of them. Another problem is that if you are specifying your own configuration, you might have to be specifying goPath or goRoot and you might be doing that differently in different releases. So if you're making updates, you hopefully will do it right in all of them. And it's not really transparent what versions you're using. All right, so Bosch vending packages are trying to address that. So they kind of have rolled out five initial languages or four initial languages in Nginx. They're in this Git repo, Git org, and then CFC.ly actually lives in there as well, but it's not a vended package and we'll kind of go into why later on. One thing to also note is that there is now pipeline. So any new versions to go or any of these languages will automatically be there pretty much the day that they're released. New majors tend to take a day or two to go in, but miners, I mean, sorry, patches make it in pretty instantly. So how to actually use this tool, you copy down whatever Bosch package you want, go into your release and run Bosch vendor package. What it actually will do is it will make a spec.walk file rather than the spec and packaging file that was there before. And that pretty much just references a fingerprint of what Bosch vendor package version you're using. What that kind of looks like in more practical terms is you kind of have this link. So rather than the error going straight from, you know, your Bosch release to kind of the third-party blob or wherever that lives in the cloud, it goes via this invenderable goling. Many of these languages also provide these two files called compile and run time bump, and they specify the configuration. Most of the time they're pretty identical between the two of them because you kind of need go root and go path or Java home or Python path in kind of any use case you have for these languages. So the compile end will typically call it from kind of like your other packages when you're compiling and your run time might be called from your jobs when you're executing code. In terms of the benefits of using these rather than the kind of more roll your own approach, they kind of have cross OS support by default. So goling rolls with Darwin, Linux and Windows. It standardizes package interactions. So now you just source this compile end or run time bump file and you don't need to set this yourself. And it simplifies package patching. So if, you know, a new goling one 10, four, one 11, one, I think just came out a week ago, you can just pull down the, re-pull down the Bosch vendor package, iterate through your releases and then run Bosch vendor package and it will automatically update. That said, you do need to cut new release versions because packages are fundamental units of your Bosch release. You have to recut. In terms of requirements, they're not, it's not the newest version of Bosch, but you do have to be within the most recent year. And if you're using the Bosch vendor packages that are provided by Bosch, you have to have an internet connection because the blobs themselves aren't a public S3. One thing to make a touch on the second is when you actually like do a Bosch might create my release with a vendor package, you end up with an identical to release to what you would have had in the old world. So it's fully atomic tassel to code. You don't need an internet connection anymore. This is kind of the part that's really cool. If you're making your own Bosch release, you actually have all the tools you need to kind of make your own vendor package as well. There's really nothing special about this file. You make your own release. You create a package of whatever it is you want to make a vendorable. If you have configuration, you can make your own compiler and the runtime them. But if it's just a binary, you don't even need that. Upload it to a blob store and you can password protect that if you want. And if you're willing to give that password to your end users, cut off on a release and then you can just use it. So if you're interested, I have a Ginko package where I have instructions that I used to actually create one. In terms of why not to use them, the existing manual package creation flow makes a lot more sense if it's your source code, right? If it's not reusable, then don't make it reusable. Also, if you need fine control for patch versions. So the way the existing language ones go, it floats on a miner, but not the patch. So if you actually want specifically go 110.0 and you don't want to float on it, then this tool hasn't been built yet for that. That's why I say it couldn't be. You can easily have go 110.0, 110.1 float on the major end float on the miner, but it's only float on the miner at the moment. Another thing is maybe consider if co-located jobs are the right tool. If it's just a runtime dependency and cutting new releases is very painful, then maybe that makes more sense. So for CFC-LI's use case, they started as a vulnerable package and decided that actually doesn't make sense, because most people are using it in their Bosch start scripts. So they need to talk to the cloud controller before they actually execute their code or whatever that is. In which case, if you want to make a new update to CFC-LI, maybe you don't want to cut a new release. Maybe all you want to do is do Bosch upload release CFC-LI and then redeploy your Bosch deployment. So from here, I'm going to hand it back to Maria. We're going to talk about a specific strain of co-located jobs, and that's co-located errands. Cool. Thanks. OK, so a quick step back to talk about errands super quickly. They're nothing but a special category of a Bosch job really, in that they are started to perform a task, then just get themselves turned on once that task is completed, as opposed to service jobs or just jobs usually, which are long-running and are expected to have uptime and be healthy. OK, so so far, pre-co-located errands world, this is what a deployment with an errand would look like. Imagine that this is a very simple deployment that just has a long-running job called app, and it also has an errand. At deployment time, Bosch would create the VM for the long-running instance and would run the process there. Now, when the moment comes for the errand job to run, the operator would invoke it, typically by running something like Bosch run errand tests, and then Bosch would go ahead and create a brand new instance, which means VM for most of the cloud providers. It would run the script there, and it would then tear down that VM once the task was completed. Now, there are advantages and disadvantages with that approach. The main benefit is that it implements a design of single responsibility. In that software, with this design, will live on its separate VM unless it has a good reason to coexist with other software. And that gives us isolation and, by extension, some level of security. On the flip side, it's very common for errands to take typically a few seconds to complete what it is that they were created to do. But on the contrast, creating a VM takes up to five minutes, depending on what provider you're using, and is also subject to minimum costs at the infrastructure layer. And that means that it costs money and time disproportionate to the amount of time that the errand itself needs to complete its work. And then additionally to that, when we're looking at running errands periodically, or when we're looking at running errands for huge deployments, such as, imagine, like a multi-service cloud foundry foundation that gets upgraded with a collaboration of many releases, this can end up adding hours to the process. And that is exactly the problem, or one of the problems, that errand colocation comes in to solve. And the main idea is that the errand job is placed on the same instance group as a long-running job. And that way, Bosch does not need to create a new VM to run the errand script from there. But instead, when invoked, it simply executes the script that it has previously collocated in an existing long-running VM. There are a couple of obvious instant benefits to this approach, and they're mostly related to time and cost savings. So first of all, there is no need to spin up a separate VM. It means that deployments go way faster than before. Secondly, the VM footprint is smaller, and that means radically lower costs. But it's also an elegant solution for a scenario where an errands responsibility is to reach out to a number of instances, or all instances in an instance group, for example, and run the exact same thing on all of them. So previously, this would look something like that. You would have an errand VM that would be sort of like central, and it would need to be configured with all of the destinations that it needs to reach out to and perform checks on them. Some examples that releases are doing are periodic smoke tests or specialized health checks on top of the Bosch-provided ones. With collocated errands, that looks a little bit more like that. So authors and operators now can move this functionality onto the VMs themselves, and instances are now empowered to perform self-checks, as opposed to having a central job that needs to be configured with what is a list of places to check, and so on and so forth. And it also could mean that you have to do less work on configuring the network and the accessibility between VMs. Another benefit from this one is that previously the errand job would need to somehow be updated through the manifest to know of any changes in the topology of the instances that it needs to reach out to, which is also something, which is also a piece of work that you don't need to do anymore. There's always a flip side, and there are scenarios where collocated errands might not make sense. Perhaps the biggest point to think about is isolation, because as far as Bosch is concerned, the errand is not a special job, it's just another process on that same instance. So at the very minimum it's definitely worth taking a step back and considering the risk of collocating an errand process with a long running and perhaps business critical piece of software. And that includes things like what permissions you would like to set on the data that lives on the disk of that VM and so on and so forth. The second point talks about resource allocation. Again, the errand job is not a special process, and in that there are no specific limits placed on it in terms of how much of the resources it can use. So if we're not careful, we can end up with errands eating up all of the resources on a VM, not leaving space for the other processes to run. Additionally, when Bosch is asked to collocate errands, it's going to place a copy of the errand on every instance of the instance group that we mentioned in the manifest that the errand is collocated on, if that makes sense. This could be a requirement, specifically on the use case that we saw just before with self checks. But if not, one question to ask is, is it appropriate if the errand runs multiple times? Is the functionality idempotent and is it going to be fine if it runs multiple times rather than one? And if not, it's worth considering the more granular UX that was introduced with collocated errands and that we're about to cover in a moment. Okay, a couple of requirements to keep in mind if you do decide that collocated errands are a good solution for your use case. You will need a version of Bosch's director of 263 and above and that's to support collocation at the director level. Linux Temsals need a version of 3, 4, 4, 5 and up and that is so that you can have a Bosch agent that understands collocated errands jobs at the instance level. Finally, if you want to take advantage of the more granular UX that came in support of collocated errands, you would need a Bosch CLI of 2031 or up. All of these were released in August 2017 so you might already be on them. Okay, in terms of how we would go about implementing them, what needs to change, the good news is that not very much. Release authors really don't see much of a change. They still create a job in a release that still has a bin slash run script just like old errands did. A little bit of a change on the manifest author side of things and that's the human operator or the system that composes the manifest for a Bosch deployment. The change that has to happen there, the change that has to happen there is that the errand job needs to be moved from its own instance group as it's own on the left to a pre-existing instance group or a separate preferably pre-existing instance group as it's shown on the right. It could be interesting to mention a couple of approaches that we've seen in releases out in the wild. The first one is a kind of a hybrid flavor where some errands will be collocated with other jobs and some will choose to live in their own VM. There are a couple of reasons why this might be appropriate. Again, it could be just a mix of use cases. Some of the jobs, some of the errands were from tasks that are applicable to more than one instance. Again, health checks is a very easy example that comes to mind, but others might be applicable to the whole deployment. For example, registration of a service broker. The second pattern that we've seen is using collocated errands in combination with some process isolation component. An example is BPM, Bosch Process Manager. And the interesting functionality that it adds on top is that it namespaces processes, including errands, and that allows for an additional layer of isolation and could reassure operators that have a particular focus on processes being isolated. The last use case, which is quite interesting, is the more granular control that comes with operating collocated errands and specifically on errand invocation. Let's have a little bit of a more detailed look into that. Invocation for collocated errands works just like before, mostly. And what I mean by that is, yes, in the simplest case, you could run the exact same command. You could say, Bosch run errands tests, but now the difference is that Bosch will trigger the errand job on all of the instances of the instance group where it's been collocated. In contrast to previously where it would trigger the one instance group. You might be interested to run only copies of the errand on a specific instance group, and you can do that by passing in the Duster's instance flag and mentioning the instance group name. You can also choose to run the copy of the errand on one specific instance of one specific instance group, and you can specify that with instance group slash first. If you care about which specific instance you want the errand to run on, you can simply pass the UID of that instance when calling Duster's instance. And you can extend that previous pattern by passing a list of instances in an instance group or multiple instance groups, and that gives you complete flexibility in where the errands will run. Okay, just a very quick recap of the things that we went through. We looked at a couple of features added to Bosch over the last year or so. The first one is package rendering that allows service author, sorry, release authors and operators to create more modular packages, and they're quite simple to make in that they are really under the cover Bosch releases. And secondly, error collocation is an idea and the Bosch implementation that allows for faster deployments and a smaller VM footprint. It's there to offer more runtime granularity and more choice to operators about how many times and where errand jobs are going to run. But it does come with trade-offs, the more important one being isolation for speeds. With that, I think we want to thank you very much for coming along and enjoy the rest of the conference.


This is a 1993 image of the Grand Design Spiral Galaxy M100, taken with Hubble's Wide Field Planetary Telescope Camera 1, which was part of an original suite of instruments launched aboard Hubble in 1990. Because of a malfunctioning flaw, the galaxy appears blurred because it cannot be brought into a single focus. In celebration of the 25th anniversary of the first astronaut mission to service the Hubble Space Telescope, a comparison photo made by Hubble's Wide Field Camera 3 was released. The improvement was both critically important for Hubble's science mission, and it made for a significantly better picture.