Gravity is real and stocks just don't go straight out the same way the semi-conductors broke the 50-day moving average here moved Onto this rise in support here the same way they did that as well Well, it's this is this going to be a carbon copy of what happened in these two sequences. I say yeah Welcome to access a trader the number one community for those who are committed to taking control of their trading in order to achieve success Profitability and longevity. Thank you for joining us. Here's Dan Shapiro to help you find your edge master your process and own your future Hey guys getting your buddy happy Monday and hope everybody had a good training day Hope everybody had a great weekend. I don't know if you can tell I got crazy sunburn over this weekend Red everywhere, but again, that's the price to pay right price to pay for a little bit of happiness in sunshine So let's talk about the market today was definitely a case of the haves and the have-nots when you look at The scoreboard today, you'll see a pretty big move in the Dow Jones industrial average They that water cooler cool to call or cold What the hell did I say water cooler talk right would call it? The stock market right and so the Dow Jones industrial average move and it was a very very good move Led by retail led by energy and it's not very hard the Dow Jones to move up to 300 points I think it's very very easy. It's only 30 stocks and when you look at the moves in retail You can see no pretty aggressive, you know, you have Walmart yet Costco, right yet Costco going incredibly strong You had target. I mean look at home depot has been doing so you have a really Aggressive run and this represents the economy. This represents Main Street America, but more important This is representing stimulus right spending and that was a good thing and that's kind of let's Go with the other side of the equation if you guys remember and this is only 24 hours ago If you guys remember from the weekend video We started talking about the semiconductors and the semiconductors that led us on a really big move Especially in the last fiscal calendar year just absolutely nuts The lamb researches of the world and the AMDs and videos of the world and all these companies that have anything to do With microchips with anything right they had a really really big run And if we notice what's been going on for the last month or so when everything else was getting pulled up Right the Amazon's the world Facebook's the apples of the world the leaders that took us higher if you remember from last night's video We talked about they were retesting very very big macro levels today, and we talked about this area here Last night on the weekend video this 241 50 level and you know fourth time was the charm They confirmed the 241 level and this is the first close below the 50-day moving average Making a move all the way down to the 239 40 level now. Why is this a big deal? if You trade any components of the Nasdaq 100 you're going to notice a couple of things number one There's a tremendous representation of the semiconductors in the queues. That's number one. There's a lot of cross listings on on both these ETFs and What happens is when you have such a strong dominant area of the queues Spread out in the semiconductors. They're going to take everything down So for example Friday Tesla had a really really big reversal right and today could have been Day two, but it wasn't Amazon had really great earnings and you know it rested You got denied off all-time highs, but it got hit as well You had names that got upgraded today for example like a Google. Okay got upgraded today went lower You had names for example I got upgraded today because they got sold off to heavily for a solar right they got sold off as well So you have a really big aggressive domino effect happening when the semiconductors are weak And just because your stock has nothing to do with the semiconductors if there is any type of tech Exposure, it's going to be brought down So if you look at the disconnect today with the Dow at one point up 350 points and you look at the Nasdaq composite that couldn't get out its own way You can really see that the market again does not like certainty But the most important part is the market does respect technical analysis And this is kind of where we are and if you look at charts tonight and you'll see a lot of really good-looking charts tonight They're not alongside guys. They're all on the short side And if you go through the semiconductor and this is why it's so much easier to focus on groups instead of Focus on individual stocks because your mind is not all over the place You already identified the semiconductor from the weekend that these were a very this is going to be a very very important day It held support one two three four times today was the fifth time it closed below the 50-day moving average And again if you look at what happens the first time stocks close below the 50-day moving average Well, look no look no further right here Here's the first close on the 50 and you're three days in a row going all the way back to this rising support So again if history repeats itself and again, maybe it does maybe it doesn't you have to love the probability of technical analysis Then we do have a potential move forward in the next couple of days all the way down to the two thirty six level again You can see where it held right this little orange line So a magnet to this area could be in the cards and it's very very important So when you're trading for tomorrow, you know, don't look for bounces right look for names that are about to confirm And when you look at the names in that group There's some names that again have a lot of support still like for example MU is not clean Right MQ has been below the 50-day moving average, but it's not clean I'm you guys have to lose this whole area here AMD as much as it's weak, right? It's not clean yet. It still has to lose this whole channel here When you start looking for clean channels look at a Vago right look at a Vago's channel This thing is one day away from really getting aggressive on the video which I call today to the downside You know now it's not more than just a little bit of a trade You know two three dollars now you're talking about the lows From 422 and the lows from the today are exactly the same lows guys So if this thing starts confirming this channel look how much room you have to the downside so stick to the themes right now the semiconductors are very very weak a lot of Tech stocks are getting sold on upgrades again We saw that today in Google You saw that today in first solar a bunch of other names as well But the most important part is and you have to really recognize for what this is this is not a self-sentiment, right? We're still really really high and really far away from the 324 level that we broke out, but this is still in the midst of profit taking so my point is there again We're not talking about Armageddon. We're not talking about the end of the world We're just talking about being prepared for the downside of the market Taking some cashflow along the way and making a productive day instead of sitting there trying to buy dips of stocks That had major major runs remember the higher a stock or an ETF goes Away from its pivot and the pivot on the cues were 324 the higher Probability you're gonna caught getting caught at some point in this channel here and start removing doubt now If you look at the cues you pretty have a pretty defined line this end here It's held now 334 once twice and held this rising moving average state So this whole channel comes in not only are the semiconductors going to continue to go lower now You're talking about everything's gonna come with it. So would be prepared folks trade both sides of the market be prepared This is just again an area of the market that you don't have to be a victim You don't need to sit there watch your portfolio bleed if you have to do if you have exposure To the semiconductors again Just just realize the technical analysis is real gravity is real and stocks just don't go straight up the same way The semiconductors broke the 50-day moving average here moved on to this rise in support here The same way they did that as well Well, is this is this going to be a carbon copy of what happened in these two sequences? I say yeah, you know, we'll see if they confirm today's action But for the most part they do look like there is going to be a day to Confirmation tomorrow and we can get some pretty good cash flow vibes And if you start looking at other names, especially NAS that composite They look look at you know beyond right beyond traded down to this channel here hit the 50-day moving average of beyond confirms tomorrow I mean look at much room you have to the downside as well Peloton, right? We talked about Peloton Couple days ago. I traded Peloton a couple days ago But now Peloton is starting to come into this macro channel And if this macro channel starts getting hit, you know again There's a lot of downside as well and you saw that today over and over and over again And I think today was very structural It was one of those very I wouldn't say there was an over abundance of value today But this was a excuse me the other way around I want to kind of switch around there This wasn't a value day that quote-unquote value day, but there was a lot of value Usually a value day is everything Amazon this that the other thing in beta This was he had a kind of pick and choose But the pivots were kind of seamless today and very very effective No shakes and the market kind of played out exactly how I thought semi's going we're going to lead To the downside the only pivot that didn't work was facebook to the upside just like everything else got sold But you can see structural balance return You can see orderly selling and when you have a back testing market that is just profiting That's all this is for at least for now until we start Testing major levels on the QQQ's you could still do very very well But you have to have a great game plan. You have to put in your work It's it's a must On the overnight and the most important part is be conscious To trade on both sides of the market just because the market's you know kind of swings on a dime And if you're not prepared you're going to be left Holding the bag and that's not a derogatory Phrase is just being you know unprepared and having your exposure open wide instead of being Protective of your capital. So going into tomorrow, you know, I am so biased semi conductors I am so biased A bunch of names that in the nazek 100 that look like they're about to break down But there is a flip side as well. Look at retail like walmart is a monster Look at this. You know first close on walmart Above the 50 day moving average. That's super bullish right really really bullish. Look at target Right. Look at target really broke out today looking really really good. Look at Costco, right? The retail names look very very strong. Look at look at the run on Costco And this is the first close over supply. So there is a rotation into other areas And if you do trade retailers and you do trade other names that a potential money flow could they could go into Then again, you don't need to concentrate on the short side trade whatever you feel comfortable, right? Not everybody has the same shoe size not everybody has the same preference or likes and dislikes everybody's different Everybody's gonna feel comfortable trading different aspects of the market But the most important part is it's your comfort ability not mine. If you trade retail Hey, this is it. You know, you have great charts and they start confirming to the upside tomorrow You don't need to worry about semi conductors. You don't need to worry about Names and nazek composite stick to your lane and trade it accordingly. So let's talk about today's pivots It was pretty pretty good day. Um pretty good day. You have a lot of stuff going on You had a lot of names that didn't confirm either I was watching coinbase This this channel here if this thing eventually I mean this thing has been a complete dud Since its debut and if you look at the channel here, I really like to set up the problem is it's failed so many times here You can see here this whole channel keeps on dying this whole channel If this thing ever starts confirming that 307 308 area I have to assume unless coin coin base goes zero. I have to assume it's finally going to break its downtrend But unfortunately today was not the day for it. Uh, netflix will talk about that in a second There was a definitive pivot that I finally found that I traded from 16 19 is a pretty good trade Uh, tesla never, you know, obviously never got to the 17 18 level Pool again pool is one of those scenarios that looks really good, but it's not tradable This is more of a macro trade for all you guys are trading long term pool trades Like I said super thin potential for option traders 427 needs to build really nice looking chart. Again, I don't have any it's just way too thin for me But this is again the first close over five 20s 427 Went to like almost 432. It looks good. It looks really really good again the pool market The pool market, especially in the northeast because of covet has been booming like it's absolutely booming and their business Is definitely reflecting that Rd. I forgot to watch our dfm.  Um, there wasn't even watching that as well FedEx great pivot on on on FedEx. Good job by Darrell. Good job by will putting into the channel 296 and a half 297 needs to build and again look at FedEx FedEx has nothing to do with technology Look at this beautiful move here 296 and a half to 50 this thing went to this is a $10 move On on FedEx right FedEx. So again guys There's plenty of areas in the market that you don't need to concentrate to the short side to be very very whole Facebook obviously never got to 330 level. There was another pivot at 28 only went up a couple of bucks And here's where you started getting to some value to the downside FSLY 6280 for bills below can flush. Here was FSLY Here's a 6280 Went down to like 6085 a nice move there TDOC and by the way, thank you very much.  There'll be some repercussions into internet. You could say whatever you want So I tweeted this out 167 needs to build some guy on stock towards the whole place goes f you man I hope you don't well he didn't say I hope you died, but f you like I told you to buy TDOC at the wrong price Anyway, 167 the internet's a marvelous place 167 if it builds below can flush trades a little bit thinner here was TDOC Right here is TDOC took out this whole channel here is 67 Traded down to 62. It looks lower. Sorry about sorry about it, buddy. I know I know your two shares will be safe But TDOC is looking lower. I still like this thing. It's a little bit thin Here was the video. I caught a nice move in the video today I I like it now more macro 600 held twice if it builds below can flush here was an avidia Took out the 600 right took out the 600 traded right to this bottom channel in the 591 level I'm telling you guys this thing loses the 591 level tomorrow. It's a lot of room down So keep an eye on that Facebook. Yeah, Facebook just didn't wake up. Um, it only you know It took out the 328 rallied like 50 cents and then completely died like everything else So, yeah, you could see technology which is bad here. So I bought Netflix 516. I sold it all the way up. It traded to the 519 area and then obviously It reversed course a nice move on Netflix take on the way down Next support 597 and went all the way down to 591 fsl y take on the way down Zoom zoom, I still like 313 if it cracks it can flush it could blow down It took out the 313 traded out the 311. I still like it lower for tomorrow Pool 531 on deck and that's it. So I I personally think the value tomorrow Isn't the semiconductors if they do have another leg lower Stay patient everybody again. You don't need to trade every day You don't need to trade every week. The most important part is realize where your strengths are where your weakness are Will make your weakness. It's not a pissing contest. It's not an ego contest You work very very hard for your money and make sure you're comfortable when you are allocating guys God bless. Have a great night everybody and I'll see you tomorrow


So, this topic of adoption of technology is something I'm quite interested in. So, I've been working with our data science teams the last couple of years on reports about how various technologies are being adopted and being used by our customers at Datadog. Today, we're going to dive into the most recent study that was published this morning that focuses on orchestration, Kubernetes and ECS to be specific, but orchestration in general. But before I get to the study, I think it's important to often offer context about who I am and what I do and why any of the data I give you today should matter and why you should trust anything I say or not. So we'll take a quick detour just to talk about who Datadog is and who I am and where the heck I got all this information I'm about to dump on you. So any folks that are familiar with Datadog, probably stop by or booth down in the sponsor showcase hopefully. Anybody using it today in your environments for monitoring Kubernetes, containers, anything else? Cool. Awesome. That's a lot of hands. It makes me feel good because it means that my work is actually getting used somewhere, which is awesome. So for those of you that didn't raise your hand, we're a SaaS-based monitoring service. We're collecting metrics, logs, and traces from thousands of organizations around the world. Our goal is to help you make sense of all your application, infrastructure, and business data as you're trying to make decisions about your environments, whether it's are they up or are they down, do I need to scale it out? Was this event, I'm running a success? How many folks were on call for Black Friday this past week? Cool. So there's folks in the room that were wiping sweat from their brow as people checked out on online shopping carts. That's the kind of stuff that we help monitor. Now my role, I work on the product and open source teams at Datadog.  The first is ensuring that we're good open source citizens. So that might be showing up at things here like KubeCon or we joined the CNCF on Monday, making sure that when we're participating in things like open tracing that we're doing so in a transparent and genuine manner. Making sure that pull requests from our community get merged on time, things like that. But the other half of my time, I spend working with our customers in our community and learning and identifying the technologies that they're using and trying to figure out how best to help them gain visibility into it. So lately that's been working mostly with containers and orchestrators, some cloud providers, but it feels like every day I'm spending my time thinking about Docker or Kubernetes or something similar. And so when I say we try to figure out all the things that our customers are monitoring, I really mean everything. It's everything from caches to containers to queues to cloud providers and everything else in between. We really want to help you collect everything because we think if you have that all in one place it's much more effective as a tool than if you're looking at five different systems across different monitoring systems or different technologies. But so of course we're here at Cloud Native Cons, so I'll talk about the things that at least from the CNCF ecosystem that we either use or adopt or monitor. We have a logging product that we launched about a month ago that integrates with Fluent D quite a bit. So we love Fluent D. We also can monitor Fluent D from our monitoring solution. Kubernetes, we've been playing with Kubernetes and Docker and Container D since pre-1.0 for all of them. And then again on Monday we launched our open tracing solution for Go and Python and other languages are coming very soon. So we're adding more things all the time. It's about 250 things out of the box that we monitored today, which is quite comprehensive. But you're not here for a data dog pitch. You're here for Kubernetes adoption data, so we'll keep going. So as we're going to get ready to jump into the study, I want to do a couple of quick trivia questions, see what your thoughts are on what's being adopted. And then we'll see if you're right as we dive through the study. So just again, another show of hands. You're going to be raising your hands a lot today. It's going to be like being in back being in grade school. Apologize in advance. So by a show of hands, I'm kind of curious which of these technologies you all think is most likely to be used in a Kubernetes cluster that we're monitoring. So the first is Postgres. Think that one? Not a single hand in the house? My SQL? You could, but then it's hard. Apache. All the hands go up for Apache? OK. We'll see if you're right. Let's keep going. So again, as I mentioned, we're always looking to better understand what technologies our customers are using and the trends that the industry is taking. And we want to be able to help monitor them, be able to tie into them, make sure our customers can be successful with them. So how do I decide on what to focus next? Turns out there's a couple of signals I can pretty reliably count on as I'm trying to figure out the maturity or adoption of a given technology. The first and most important one is always hacker news. I just stop a search in there, look at the numbers, and if they're high, clearly that's what I should be writing my applications in, and you're likely writing yours in. Just follow the latest trend. It's called hacker news-driven development. It's very successful in Silicon Valley companies. I've been through a few of them that take this approach. I don't know about you all. Anybody have coworkers that do this? Nobody wants to raise their hand for that one. I promise the camera's not pointing at you. It's pointing at me. They'll never know. But if we look at the numbers, it turns out containers are pretty awesome. Like, the numbers are high up there. They're higher than most things I search for. Whether it's Docker, ECS, or Kubernetes, it turns out according to this I should be packaging all my stuff in Docker and running it on Kubernetes, who knew? Then again, it turns out that Rust and Uber are cooler. And so apparently I need to pivot and stop worrying about containers, start worrying about infrastructure, and just build a really rusty ride sharing service. And I'm going to be a millionaire. But anyways, we'll keep going. So again, we're at Cloud Native Con. The other thing I could do is I could pull the audience at events like this, where they'd be at meetups or something like that, like we did at the start. I guess that's semi-scientific to figure out if things matter, because I see that you all paid to be here and it's interesting to you. And I can tell that it's important. But there's a bit of selection bias. I can't tell if it's, I mean, you may be early adopters.  So polls are not the perfect way. Another thing I can do is look at the age of these technologies and kind of dive in. And so it's important to remember that almost everything we've talked about today is quite young. And it's moving pretty quickly. If we look at this, Linux was released in 94. Let's look at that as an example of a technology and how quickly it was adopted. I know this is a bit of an eye chart, but Linux was released in 94. And it took about what, seven years before? Well, 1.0 was in 94. It was released earlier than that. But it took about seven years before we got some serious business adoption. This is the first time. 2001 was the first time that IBM jumped in and said, we're going to put a billion dollars into Linux. Anybody remember the commercials with a little kid? We'll teach him. We'll raise him. He'll be awesome. His name is Linux or something like that. So that took about seven years. That took a while for people to really get on the open source and on the Linux bandwagon. But here we're at KubeCon. And I go to ExpoFloor. And obviously, I think Datadog's awesome. But you wander around and you see huge organizations there. You see IBM. You see Microsoft. You see Cisco. You see Intel. They're all jumping in with both feet on this containers thing and this Kubernetes thing. So seems like we're moving a little bit more quickly. I don't know if it's our love for the cloud or the need for dynamic infrastructure now or what. But it's weird that after only three to four years, everybody is talking about this. And really, as we'll see in the study, a lot of people are actually using it as well. For us, our first signal, the real thing is when customers ask for it. So in 2014, we got our first pull request. Docker hadn't even hit 1.0 yet. And some customer was scared about this enough to actually write a Docker integration for Datadog and start collecting metrics. And it's like, well, if they want to do it, I guess. If they wanted enough to write the integration for it, then clearly it's important to somebody. And so we dove in on it. We started partnering with them. We took the Datadog agent, shoved it in a container at this point. We've collaborated with our community. We've got, I think, over 5,000 contributors at this point on our various open source projects. And what built a containerized agent, you can drop it on Kubernetes or ECS or plain old Docker or anywhere else that you might want. And it collects metrics and monitors your applications and does all the right things. So for us, that's important. Much like everybody else, we're also adopting containers. We've been using them in CI forever. We've been using ECS for about as long. We're starting to use Kubernetes in other places now. So lots of containers everywhere at Datadog, too. But again, all this is really anecdotal. You might ask, where's the data? We are Datadog. Data's in our name. If I didn't show up with data, you'd probably laugh me out of the room. So we kind of have to go back and fact check all this. I can't just kind of do this poll, go back to my boss and say, let's drop all that. Everything else from the roadmap, it's all Kubernetes moving forward. So I start to look at other data. I can look at maybe polls from Docker Hub. Every year at DockerCon, Docker talks about how many images have been pulled from their service. In 2014, it was about a million. It took about over a year. It increased significantly from a million to a billion. 2016 was 6 billion. 2016, they just announced when I was in Copenhagen, was 24 billion poll requests. Sorry, image polls. And that's just from public Docker images. We're not talking about all the private registries that you all might be using, or Red Hat has a new container or image service that they offer, all other places that it might be. So clearly, containers are taking off. For us, though, we realize we have real data. And so remember, we're monitoring infrastructure all over the world for thousands of organizations, and it all comes back to our hosted service. And so about a few years back, we started looking at that data in a fairly rolled up and anonymous fashion. We're not digging into any individual person's data, but we look at it in aggregate. And we realize that we can tell from these workloads, from these trillions of data points per day, once we aggregate all that data, we can see technology trends in the tech world around us, pretty accurately and pretty quickly, we can see as things shift. So we started as putting out these reports. We put the first one out in 2015, and we looked at the first year of Docker since 1.0 and dove into Docker adoption. And we saw some pretty interesting stats. We refresh it annually now. So every year at DockerCon, we put this out. But we're at KubeCon, so we'll keep going. But what did we see in the last report? We saw things like containers being up 40% in our customer base over the previous year. And that had been 5x up the year before that. So that's clearly some good data. These are folks that are paying us to monitor Docker. Clearly that's some production use case. You don't tend to pay somebody to monitor things you don't care about. We then looked at it again, and we saw things like 15% of the hosts we monitored at the time were running some amount of Docker on them. Nowadays, it's actually closer to 35%. If you look at organizations over 500 hosts, you're pretty much guaranteed to be running some amount of Docker. But if you're over 500 hosts, about 35% of you are running some amount of Docker. So that's growing. Again, that's real data there. Let's dive into orchestrators, though, right? That's what we're here for. We're here at KubeCon and CloudNativeCon. So we raised hands before for Docker orchestrators in general. Anybody just still running just Docker? Like, you're Docker running everywhere? You got Ansible or something else kicking off Docker runs for you? Couple of you? So we were curious about the same, right? We saw this Docker adoption. We wanted to see how are folks using it. And again, this is from about six, eight months ago. We dug into it, and we found that about 40% of organizations at the time were running some form of orchestration if they ran Docker. This is as of April. And when we dove in and looked at it even further, one of the things that we found was that if you were over 25 hosts running Docker, your probability ran up. You moved up to about 50% of the users running something. Once you hit 165 and beyond that, you're basically guaranteed to be running some sort of orchestrator. Turns out when you're running at scale, you don't like SSH-ing in a for loop or whatever crazy Rube Goldberg machine you put together is for launching containers and rescheduling them. You actually want something to do this for you. So another interesting stat. About 5% of you all are apparently running two or more orchestrator technologies. Who's got this Frankenstein environment out there? Raise your hand, a couple of you. Migration story? Yeah, I'm going to meet up here. Cool? Yeah, you guys have a really cool case study with Google, up on the Google site about how are you using GK. So if folks are looking for how this guy here is doing all kinds of awesome stuff with Kubernetes, it's up on the Google site. Thank you. So yeah, I think usually I hear about people that it's migration stories. Other times it's folks like where there's acquisitions or mergers or just large organizations where there's different teams. I can't possibly use what you're using. So it's a little bit of everything. This dysfunction does come with us even as we move into the new generation of technologies. But again, let's talk about the new data, where I've been telling you all about this old data that's, I don't know how old April's not that long ago, but it's old compared to the stuff I released three hours ago. So what's new? Today we released a new report. Again, it was mostly focused on Kubernetes and ECS. We see lots of other orchestrators as well. We see Nomad. We see Mesos. We see Swarm. We see other things. But really, I think Kubernetes and ECS were the ones we've had the most conversations about. So we wanted to dive into those specifically. And so the first thing is there's some pretty good news for Kubernetes in terms of adoption. In the first nine months of the year, so again, I had this data is up through October September. Had to go back and put together. But again, through as of October 2017, about 41% of all Docker environments that we monitor are using Kubernetes to orchestrate them. That's quite high. Again, a minute ago, we just talked about only 40% of our customers that were using Docker even use orchestrators. That was from last year. Now we're saying over 41% of them are actually using Kubernetes. It turns out that these days it's about 2 thirds of organizations are using some number of orchestrators, one or more. That's huge growth. The other thing to keep in mind is that the number of Docker users that we have, remember, we saw that growth curve that Docker was on? That's not slowed down. That's at the same pace. So if you talk about percentage of 30% here versus 40% here, that's more than an 11% gain. That's a huge gain. That's a lot of people jumping into Kubernetes.  You all have your hands up because everybody's running Kubernetes. But the real question is how does this impact your workloads? How does this impact what we do? Kelsey was yesterday on stage giving a keynote and you reminded us all. Nobody cares about your Kubernetes cluster. They care about the business services that you offer. They care about the products you deliver to your customers.  But at the end of the day, keep it up, move on, go back to building product. Keep it boring, he said. So I think the other question is, is Kubernetes and is Docker helping us do that? Well, we found some interesting stats around what it did to host churn and container churn. Usually, we see hosts that we monitor live about 23 days if they don't involve any amount of containers. But once we introduce containers, it drops to 17 days. Once we add orchestrators like ECS or Kubernetes, they vary a little bit by a couple of days. But it's about 10 days on average that an ECS or Kubernetes host will be around for. And I think that's telling. It shows that Kubernetes and ECS make it pretty easy to drain workloads off your machines, kill those machines, bring up new machines, have those workloads show up somewhere else. You don't really feel bad about terminating those hosts and bringing them back up. And this is above and beyond what folks were already doing with VMs, where they already were probably using auto scaling groups, probably using some other dynamic method for provisioning their systems. So I think that's one sign that it's helping us move faster. But not surprisingly, it also helps our containers be more dynamic. Remember that SSH for loop around Docker run? It's pretty slow. It makes it hard to make changes quickly. Folks that are doing blue-green deployments, that kind of stuff, are not doing that. So once you start diving into something like Kubernetes, it's just an assumption that you're going to be able to move faster, reschedule them faster, deploy faster. So one interesting stat we found here was that containers running on Kubernetes live only about one and a half days on average. ECS, on the other hand, which is, I think, the next most popular container orchestrator we see, lasts about 12 days on average for a container. So I don't know what you all think that means about Kubernetes versus ECS workloads. I don't have to point at Kubernetes jobs or the cron scheduler or other things that are bringing pods up for very short periods of time, which ECS doesn't have. Or if it's that people are just using ECS as an artifact deployer, not necessarily as a real container orchestrator. It's interesting. I'm curious to see what all the Fargate stuff that they announced at the keynote earlier this week with Adrian Co-Croft will change things too, especially since I won't be able to see the hosts anymore. It's just containers, right? But it'll be interesting. So the next thing that we've all talked about, we talk about speed when we talk about containers and we talk about orchestrators, but the other thing we talk about is density and efficiency, right? How many folks are doing this for bin packing reasons? Like you really want really efficient, 100% utilized all your infrastructure. You don't want to leave one cent on the table, right? A couple of people raised their hands, right? We want to stop moving things like this where we've got a lot of empty space around. We're kind of shoving things between boxes, trying to make use of those workloads, and be a lot more efficient, a lot more standardized, right? So when we did our Docker report, we found that folks were running about seven containers per host. So I'm curious, is folks on average, are you running more or less? More, a couple more, a couple less? So what do you think Kubernetes does to this? Do you think it's gonna give us more containers or less containers per host? So you're right, it's more. So when we dove into Kubernetes, we see closer to nine application containers per host. And what do I mean by application containers? Well, I mean your workloads. So when I looked at this, I thought, I don't really care, I mean, you're not really deploying Kube DNS for the sake of deploying Kube DNS, that's like a utility, that's a system container for you. You're not deploying all of the Kubernetes system, control plane stuff as your own containers, that's part of the orchestration system. So we hadn't grept all that out, excluded that from our report, and so that's only nine. If I put all that back in, it's like 14 to 15 containers per host, but most of that again is Kubernetes itself. So it feels a little weird to give Kubernetes credit for just existing, right? Like if you could have a completely idle Kubernetes cluster and you likely have like five containers running on that box, it's like, I can't really count that, right? So we're excluding all that, just because it turns out Kubernetes uses a lot of containers itself, which is cool. ECS on the other hand tends to only have three containers on average. If I throw the fourth container in there, it's gonna be ECS agent. I just, I gripped that, I pulled that one out as well because again, for the same reason, nobody's intentionally paying to run the ECS agent, just like nobody's intentionally paying to run their Kubernetes control plane. I don't know really what that says. I mean, that's three X more density. Again, I think it's sort of telling about the types of workloads people do on ECS versus Kubernetes, but it needs to dive into it more. So if you have your own thoughts, I'd love to love your hypothesis so I can go dive into it and prove it with data. Cool. So let's go back to that trivia question. Let's play a little game of family feud. What would the survey, you know, we had before folks were saying what we said Apache was the most popular technology that's running in, of the three that I mentioned, running in Kubernetes. Is there any other things you think are almost guaranteed to be running there, something that you're sure will be on this list when I flip the cards? Engine X, okay, anything else? Message queues, any specific message queues? Rabbit, okay. Redis, okay. Cool. So it turns out it's things like Engine X, so I don't know if I had socks or something, I tossed it at whoever said Engine X, but I don't, so come by the booth later, maybe we have, I think we probably have some shirts for ya. RabbitMQ was on there. Elasticsearch, MongoDB, Postgres, MySQL, right? They're all in there. Who said Apache before? It was all of you, right? Apache's not even on the list. It doesn't even fall into the top 15 things that I find in container environments. I don't know why that is. I spent so many years automating Apache deploying Apache, running Apache. I think I could, on a whiteboard here, write a tactically correct Apache config file for ya, and nobody's using it in container environments. And I don't know why, I mean maybe it's, maybe it's just a little heavier weight, I don't know. What I do find really interesting is the number of databases that are on there, right?  Couple hands, but it's not, generally folks, I run into folks, the mass majority, like if I asked you how many of you guys are running state list services on your Kubernetes clusters, all the hands are gonna go up, right? So it's just interesting the number of, when we look at this, the number of folks that are doing it. So to give you a sense of the ranking in Kubernetes at least, you know, Nginx of course by far, I think pretty much everybody's using it as a reverse proxy here, but you know, the others are well within each other's range in terms of the data stores. There's quite a few of them. What do you think it looks like across other orchestrators? Do you think it's about the same across things that are running containers or things that are running ECS? It's the same technologies again. The difference though is that, what I see in ECS is that most people are running their own custom built images. They're not building things off the shelf or things that they've built from. They're building, they're mostly their own applications. I think that's because when you run in something like Google or you run in something like ECS with Amazon, they already give you all the services. Why would you run a Redis server if they, like they already give you a reliable Redis server that you just, you pay less for and don't have to worry about operating?  So I think that's the real reason why on ECS everything's smaller, the stacks. On Docker, again, it's about the same. It's just, again, the scales are slightly different, but it's about the same. You know, I started to look at also at container registries this morning. I wish it was actually interesting. It turns out that if you're in Google, you're using the Google Container Registry. If you're in, if you're in Amazon using the Amazon Container Registry and then all of you are using some amount of Docker Hub because it's the thing that everybody uses. But if we talk about the best practices around some of that, how many folks are pulling latest from like Docker Hub all the time? None of you? Nobody? Nobody? I see some people going, sometimes. Yeah? Yeah, that's what our docs say, right? So you better be doing that. Yeah.  I see three hands, four hands. Okay, so not a lot of folks. Do you think most people are, do you think most people are doing about the same as you or better or worse, somewhere in the middle? Yeah. So it turns out it's a pretty healthy mix. I mean, it's a scary mix, but it's a pretty healthy mix, right? About 74% of you all are doing a mix of good things and bad things. About 10% of you all are doing only the good things, which is like mirroring your containers or grabbing specific versions and not letting me break you when I release a new thing. Sort of like, I mean, how many, did we not learn our lesson? Like who didn't lock their bundle file, their gem files or their requirements files and like in Python or Ruby back in the day and like have everything blow up on them on the next deployment? Did we not learn anything in the last 10 years? Anyways. So about 16% of you are doing like the right, again, doing the right thing and only deploying the wrong thing and only deploying latest, which I guess that's, those cowboys we always hear about, right? So yeah, that's the facts I got for you today. I think I've got a couple of minutes left here to answer any questions and dive into anything I maybe didn't cover. If there's some metrics I didn't report on or something I was supposed to talk about that I said in the abstract and didn't cover here today, you can quiz me on it, grill me on it, throw some tomatoes, whatever it might be. Feel free to tweet at datadog or myself. I saw you all taking pictures of the graphs. They're all online. So just, I'll tweet them out in a second. They'll be linked here as well. It's up on the datadog website. You can check it out. We also have it down in the booth if you wanna check it out on the big screen. I've got a bunch of resources here in the slides about how to monitor Kubernetes, how to monitor Docker, how to work in the cloud, a whole bunch of other things there. The original Docker report, I'll put these up on the slides for the KubeCon site in just a few minutes. But yeah, if there's any questions, happy to answer them. We've got about, I think about eight minutes left. So I finished just in time for that, you know? All right, it's been fun. School's out.


And thank you for joining us for an operational briefing on a wildfire near Lytton here in British Columbia. A reminder to media on the line, please press star one to enter the queue for the opportunity to ask a question and a follow-up. We have three speakers scheduled for today. First up, we'll have Rob Schweitzer, Director of Fire Center Operations for the BC Wildfire Service. Next, we'll hear from Peter Brach, Executive Director, Regional Operations with Emergency Management BC. And finally, we will hear from Deputy Chief John Hogan of the Lytton First Nation. We are now ready to go live. A reminder to media on the line, please press star one to enter the queue. I will now hand it over to Rob Schweitzer, Director of Fire Center Operations for the BC Wildfire Service. Good afternoon. This afternoon, the BC Wildfire Service was called in to respond to the Nohoman Creek Wildfire, which is number K70580. And it's located approximately 1.7 kilometers northwest of Lytton on the west side of the Fraser River. The events of 2021 and the impacts to the village of Lytton and the Lytton First Nation are forefront in our minds. Many of my colleagues were significantly impacted by the Lytton Creek Wildfire last year. We ask for your respect and kindness as we report out on this new incident. Our primary objective is the safety of the crews and the residents who are currently impacted. So currently, the BC Wildfire Service has four initial attack crews on site with two unit crews as well. And they're responding with the support of helicopters and air tankers. The fire is currently estimated at 25 hectares in size. And the cause is currently unknown. Crews will continue to work through the evening and overnight as required. The RCMP and local fire department are also responding to this fire. Gusting winds in the area this afternoon are impacting the fire behavior. And crews on the air and in the ground are seeing and observing moderate fire rates of spread. The incident is highly visible from Highway 1, the village of Lytton, Lytton First Nation and surrounding communities. And just for information, our app, the BC Wildfire Service mobile app has a glitch in the system. It's actually reporting the fire as igniting at 5.44 a.m. this morning. I can confirm that is incorrect. The fire was initially reported at 12.45 p.m. this afternoon. So 12.45 p.m. this afternoon was the first report of this wildfire into BCWS. All wildfires are dynamic incidents and we will continue to provide updates as they become available. And for the latest information, please visit bcwildfire.ca or follow the BC Wildfire Service on Twitter or Facebook. EMBC and Lytton First Nation are here to provide an update on the current evacuation and orders in the area and I'll now turn it over to Peter Brock to speak on behalf of EMBC. Thank you. Peter, please go ahead. Thank you. Thank you. Good afternoon. My name is Peter Brock. I'm the Executive Director of Regional Operations with Emergency Management BC. First I want to say that our thoughts are with everyone that was impacted by this fire, especially after going through and recovering from last summer's fire. As you know, this afternoon, people evacuated Lytton First Nation community due to a fire. We have received reports that approximately three structures may have been lost, but this has yet to be confirmed. Our condolences to the entire community. Please imagine BC is here to support the Lytton First Nation and those who have been forced to evacuate. Today, EMBC hosted a coordination conference call with attendees from Lytton First Nation, Thompson Nicola Regional District, BC Wildfire Service, First Nations Emergency Services Society, Indigenous Services Canada, and other key partners. Emergency support services are available for people who have been forced to evacuate. Supports include food, lodging, clothing, and may be provided for up to 72 hours or until their evacuation order has been rescinded. We understand people are registered through the online evacuee registration tool that EMBC has provided communities and the most important thing that the public can do right now is to prepare yourself and your family for any potential fires in your areas and please avoid any at all activity that may result in a wildfire. Thank you very much. And now we will go to the Deputy Chief John Hogan of Lytton First Nation, John. Please go ahead. Yeah, I want to thank the two speakers before me and we do want to thank everybody for the quick response to this fire we have gathered here and have put in place an evacuation order for IR23 in Homine and Lytton IR9B. So we have three elders that are in the direct line of this fire and we're working to make sure that they're safe and that we can get the fire out as soon as possible. We are experiencing another fire that was told to be in the Hellsgate area. So we have to be prepared for many things on really short notice. Thank you very much. Thank you so much to the Deputy Chief. A reminder to media on the line. If you'd like to ask a question, please press star one to enter the queue. You should hear a tone in response to indicate that you have indeed joined the line. If you do have a question, please ensure you direct it to the appropriate person. And I will pause for a second to allow folks to join. Our first question today comes from Callie McTavish of CBC. Callie, please go ahead. Hi. You mentioned that structures were potentially lost. Can you confirm that people have been evacuated? Can you hear me? Hi, Callie, I can hear you. Just let me bring it up again. Two, on the line, you were asking about folks who had been evacuated. Callie, is that correct? Yes, I was asking about evacuees. OK, Peter or Deputy Chief, John, could you please respond to the question? Yes, we have had people on the ground that are affecting the evacuation order for the properties that we have under our jurisdiction, and we have evacuation alerts posted for other areas north of the fire. So those are in place and underway. Thank you, Callie. Do you have a follow up? Yeah, I heard from one resident that they believed that the fire started at the old dump. Has that been, have you heard that? No, we have not. No source of ignition has been confirmed at this point. OK, thank you. Thank you, Callie. Our next question comes from Alex Buster of Global News, Alex, please go ahead. Hi, there. Thank you so much for taking my question here. So I just like your confirmation for some form of can you confirm how many crews are actually at the scene responding, please? Yes, so I'll take that one. So it's four initial attack crews. So that's four three person crews. For a total of 12 and then two unit crews and those crews are 21 each. So in total, that would be around 54 ground crews at this time with a couple officers on site as well, plus the aircraft, the helicopters and air tankers that are supporting those ground crews. Alex, do you have a follow up? Yes, thank you. Thank you for that response. In terms of the people who have been evacuated, can you give a precise or a rough number of how many people have actually needed to be evacuated? Not sure if I was needed. Oh, I believe so. I wasn't I haven't heard of a response so potentially. Yes, for our community, I believe there's approximately nine individuals that should be on the evacuation order. And I'll do one final call for the phone lines. If anybody has a question, please take this opportunity to press star one to enter the queue for the opportunity to ask a question and a follow up. Next, we go to Brianna, Charlotte of Canadian Press Brianna, please go ahead and are you there? Oh, can you hear me? Perfect, I can hear you now. Please go ahead. OK, sorry about that. Ecom has tweeted out that there are service outages in the area. Is do we know if this is related to to the fire? Yeah, hi, Peter Brock from emergency management, B.C. So we've heard the same reports that 911 service outages are occurring in the impacted area. It's worth mentioning that so far, the reports are that that's unrelated to the current fire. The reports that we have received is that there's five cell towers are in the affected in the area, along with some landlines. But that's just the last update we've received. And we are not sure of the status as of now, but that's the latest we've heard. You have a follow up, Brianna. No, I think that's it. Thank you. Thank you. Next to go to Tim Petrick, Castanet and he appears to have left the queue. So that concludes today's availability. Thank you, everyone, for joining. Have a great day.


So as a general rule, most differential equations are unsolvable. At least in the sense of being able to write down a recognizable function that will solve them. But remember, your inability to solve a problem does not make the problem go away. We still need to find some method of representing the solution, and so for that, we turn to the Taylor series. Remember that a function f, which has derivatives of all orders at x equals x0, has a Taylor series centered around x equals x0, and this Taylor series gives the correct value for f of x0. And if we're lucky, this series will give us the correct value of f of x for other values of x as well. We define the following. A function f is analytic at x equal to x0 if the Taylor series centered at x equals x0 converges to f of x for some open interval containing x0. The short version of analytic is that within the interval of convergence, an analytic function has a Taylor series that converges to the function itself. And in addition, there are several more useful properties. As long as we stay inside the intervals of convergence, the series converges absolutely, and more importantly, the series can be integrated or differentiated term by term. And in either case, the interval of convergence remains the same with the possible exception of gaining or losing an endpoint. And this suggests a powerful method of solving differential equations. First, assume a power series solution, and then find the power series. For example, let's try and solve this differential equation where y of 0 is equal to 0. So we'll assume a power series solution, y equals the sum from n equals 0 to infinity of an x to power n. We'll also assume that this is analytic, although that's a bit of wishful thinking at this point. Provided it is analytic, then we can find the derivative by differentiating term-wise, and so our derivative will be, and so our differential equation gives us. Now in order to proceed, we'll need to reindex our terms. So again, what we want is our exponent on the variable to be the same, so we want n minus 1 to be equal to k, and so n is equal to k plus 1, and our starting value n equals 1 corresponds to k equals 0, and so our series becomes, and since the name of the index variable doesn't matter, we'll call it n and get our series, and now our two series have the same power on x. They both start at n equals 0, and so we can combine the coefficients, and that gives us our differential equation expressed as a power series. To find our coefficients, we'll assemble our equation dy dx plus y equal to 1, so we know our power series for dy dx plus y, and it may be helpful to write out a few terms of our power series. If n equals 0, our corresponding term will be, if n equals 1 we have, n equals 2 gives us, and so on. In order to find these coefficients, we remember that we have to have equality, since we know y of 0 is equal to 0, and by assumption y is our power series, we can compare the two. If x equals 0, our power series becomes, and y is just 0, and so a0 is equal to 0. Since a0 is equal to 0, and our left-hand side and the right-hand side have to be the same, that means our constant terms have to be the same. On the right, we have 1. On the left, our constant term is a1 plus a0, and so these must be equal. Solving tells us that a1 is equal to... Again, our left and right-hand sides have to be equal. On the left, our coefficient of x is 2a2 plus a1. On the right, our coefficient of x is 0, and so this gives us the equation, which we can solve for a2. Again, because the left and right-hand sides have to be equal, our coefficient of x squared on the left has to be the same as the coefficient of x squared on the right, and so that gives us the equation, which we can then solve for a3. And for purposes of later recognitions, it's sometimes useful not to do all the arithmetic, so we'll leave a3 in this form. But wait, there's more. The coefficient of x to the third on the left is... Well, that's not written down, but we can compute it from the form of the series coefficients, and so that will be... and on the right, because there's no x to the third term, that coefficient is going to be 0, and so we have the equation, which we can solve, and this gives us the first few terms of our series. In some cases, it may be possible to recognize a power series as a familiar function. In this case, note that e to the power x has power series, which means that e to the power minus x will have the power series, and with a little bit of algebra, we see that this differential equation, which has this solution as a power series, has the same power series as 1 minus e to the power minus x, and so our solution is y equals 1 minus e to minus x. However, as a general rule, getting a closed form expression for a series, in other words, being able to identify a power series as a familiar function, is usually impossible.


Well over the past year and a half we have kept track with La Porte School's growing garden and today local farmers stepped in with some fresh ideas. Brenda Mack tells us more in this week's Golden Apple. Behind La Porte School lies fresh fruits and greens ready for harvest but today these little gardeners have a much tastier agenda. I love everything here. From maple syrup to pea shoots to kale pizza. Local farmers brought out some homegrown produce for kids to try. To share new flavors. Even the buffalo meat tastes like beef jockey. And teach them what it takes to bring food to the plate. Do you guys know what these are? The sap of the tree comes out. I just want kids to be able to try new things and really to be able to learn what kind of things can grow in this local area because I think they probably don't realize what all can be grown close to home. And with the overwhelming love for tomatoes in this garden, teachers hope to inspire kids to grow fruits like these that take a longer time to ripen after today's program. I love watermelon. How do they start? You know they ask me how you start these or how you grow these. This is a very special day, probably one of the most special days I've had as a farmer. The white range of flavors may have been a hit or a miss. Don't like it. But these students sure have savored the moment. You like the every last drop. They're like a wrapped up present. Tastes kind of like a tomato but a mix between a cherry. I think that's what they call them, present cherries. Yeah. And it looks like the port will soon have a fruity season for this week's golden apple. Brenda Mack, Lakeland News. If you've enjoyed this segment of Lakeland News, please consider making a tax deductible contribution to Lakeland Public Television.