They helped us get it actually started. It's a collaboration project but because of their generosity I was able to take time away from installing other stuff or not open stack stuff to actually work on just this community. So they were a big motivator behind the project itself because before I was helping lots of people do open stack but nobody was talking to each other and that's kind of what we're doing here with Chef for Open Stack. The Rackspace, their Alamo project, it's going well, check it out. It's a bootable USB stick or ISO to see how Open Stack looks, peel away the covers. It's almost the same code, we're sharing a lot of that code. The Rackspace guys all got to go to a football game tonight so they're not here. But well sorry, sorry you two, the rest of your team they left. But most of the other people up here are actively engaged and working on stuff as well. So what I kind of hope to talk about is here's what we got, SX is working, KVM Ubuntu, LXC, some Calzada guys are over in the bare metal deployment talk but they've got LXC working with these cookbooks because they're running on ARM CPUs. Swift, Dell has some cookbooks, Rackspace has some cookbooks, Dreamhost does not have Swift cookbooks but I have not taken those and cleaned them up to make them more accessible from Rackspace and I'm not sure, do people want SX Swift or should we just go to Folsom? Because this is a conversation, feel free to say like, SX, Folsom, Folsom it is. So the point made by the gentleman from Dell was that Folsom was easy to use because a few small tweaks and it just worked and I was talking with Rackspace earlier about their work for Folsom and they said they took the Alamo stuff, changed a few URLs, fixed a bug and Horizon and it works. So that is, yes, we're not doing upgrades, sure, sure, sure. But the point is we won't be starting from scratch. There are definitely Swift cookbooks that exist and we will be leveraging them shortly. It's just, sorry Swift guys, Nova is a little more glamorous and so it's gotten more attention lately. But these are the things that are on the road map for the project. Documentation, I've been pulling the readmes and various little bits of documentation that are sprinkled throughout all the cookbooks and projects and everything and pulling them into OpenStack Chef docs and converting things to Sphinx and restructured text so we can make PDFs and multi-page HTML things and it's very shiny and you can make EPUBs and real documentation and at some point possibly moving some of that documentation to docsopenstack.org. I put it on the same license so it'll just move right on over and they're using restructured text but they're using Doc book or whatever. I'll talk to Ann Jennell about that. That documentation is up. I've been pushing to it furiously like the last three or four days. Hypervisors, KVM and LXC today, does somebody want something different? If you want something different and you show up with patches, we will try to make that work. I know that the SmokeStack stuff runs on top of Zen but that's the only place I've really seen somebody running Chef with Zen. If you want Zen, show up. You're going to be the supporter. The funny thing about all this code is of course it's community driven. I'm the one guy from ops code and there's like 10 guys at Dreamhost and 10 guys at Dell and 10 guys at whatever. In order of magnitude more than one. There's more than me. The way this project works is if you want a feature and you show up with the feature, it's in the project as long as it doesn't break other people's stuff. Rackspace is working on REL6 support right now. I've been asked about that several times. I've been asked about Postgres. I will introduce you to someone else in the back who's making fist pumps in the air about Postgres. So Postgres, we can just start that up in the Folsom branch and start changing the way that the roles are laid out. Instead of searching for the MySQL master role, we'll start looking for the database master. Which brings me back to some patches that I haven't merged yet from AT&T about not using roles for search. They want to go back to using attributes. I'm cool with that because it doesn't break other people's stuff. Yeah, if anybody wants to dive in, I would love to have support for that. I would love Slez support if the SUSE guys show up and they want Slez to work and it doesn't break everything else, I want it to work. I mean, there are people who are asking for every sort of permutation under the sky and it's a patchy. Let's do it. Is that a question or a fist pump? For anyone who doesn't know, next week is the Chef Developer Summit in Seattle. So that's a bar camp type thing of Chef Developers. Exactly. So, I mean, yeah, there will definitely be, we will definitely use that as a reference. We're burning, or not Betty, Betty to Fred. I thought Betty was Essex. Gender bending. Yeah, so yeah, that's people introducing people. The fist pump were in the back. Do you want to say who you work for? I mean, yeah, okay. And so yeah, there's Postgres support in the crowbar cookbooks and the smokestack cookbooks and it shouldn't be hard and we'll make corrections in the various logic to move away from specifying your database in the names of the roles instead of saying MySQL Master, we'll go to Database Master. Instead of RabbitMQ Master, I think is what it currently is, I want to move that to Messaging Master because there's been talk about bringing in either active or zero MQ. Yeah, Cupid too. I mean, we want to generalize it so we don't have to care. Yeah, I mean, I know it's there. I just, we need to clean it out of our current mode. Yeah, show up in IRC and we'll talk about it. I just mean instead of searching for the MySQL Master role, we come up with the database master role that under the covers and attribute has set it to Postgres. Yes, yes. No. So let's talk about upstreaming cookbooks. You know, there is, I was pointing out how many other people there are besides me and so a lot of the work I do is really just picking from other people's branches and merging them into the Chef for OpenStack and then other people are like, oh yeah, that's cool.   And if you want to be, you know, the people who are like, hey, we want to make sure Chef works for everybody besides just DreamHost, you know, I'd love for you to do that. There are some folks who are working on getting CI set up on top of this. And hopefully, our Metal Cloud has given me, you can have as many noses as you want. I was like, cha-ching. So I will probably set up a lot of Swift stuff when I start testing with, you know, I've got four boxes in my lab. So when I start testing at volume, I'll probably be going there unless somebody else is like, hey, Matt, let me send you some hardware. And so, you know, if there are people who want to step in on things, you know, it is, it works today. Essex works, you know, we'll probably break it a little bit for Folsom, but you can always go back to Essex and it worked. And then we'll start working on supporting more complex deployments. Right now, it supports what Rackspace Alamo supports, which is all in one or in plus one. Or one plus N, where you have one controller and compute nodes, which, you know, that doesn't scale past like 20 or 30. Yeah, yeah. So if you look in the OpenStack Chef repo, I've got a file in there called todo.org. It's my Emacs org mode that just, it's the backlog of like wishlist things that it would be nice to clean up. I think it's like number two is, is make sure that every service safely runs on other boxes. And with my four boxes, it was like, I'll put my SQL over here and then we'll run the other stuff here. Okay, that worked. You know, cycle, repeat, and it's kind of slow. But yeah, so thanks. Yeah, we'll get that merged out. I expect Folsom work will probably start like, I'll start actually get back to my office in about two weeks and we'll start putting Folsom out from the main line. If you want somebody else's branch, Rackspace said it works for them, Dream host says it works for them. Dell has cookbooks that work. There are other private, or there are other repos that are not advertised, that are publicly accessible, that have Folsom working as well. I'm not gonna say their names because they're not here. So yeah, there's definitely Folsom work that's already done that you can jump on if you're in a hurry. If you're slow in plotting methodical like me, it'll be at least two weeks. But the nice thing is I'm actually writing more documentation than coding at this point, which is where I wanted to be. The repos don't have to be named the same thing, or product-cookbook. So move things like Nova to Nova Cookbook? Well, so I mean, the Nova currently is over in, GitHub, Opscode-cookbooks slash Nova. I mean, that's pretty descriptive, but when you fork it into your repos, like now I have two Novas. So yeah, you have to rename it. But you can rename it, and then when you bring it into your cookbooks directory, you can rename it again. I mean, that's how I got around it for, I'm doing it with something already myself, but do people want me to rename the repos? I don't think there are that many followers where it'll rock their world too much. Well, I mean, that's a GitHub problem. I mean, it is a problem for Joshua Temmerman, who's our community guy who does most of the cookbook management, but not this cookbook management. It's a GitHub issue, really. I'm happy to rename them. I don't think there are that many. If you're following the cookbooks, I will go rename them, and I'll find all the followers and send them an email. It says, yo, I changed the name of the repo that you were using as a remote. Well, GitHub's just adding this layer of magic on top of Git, you know what I'm saying? Yeah, so, as far as, that's the basics of Folsom. When we start diving into the new pieces, HA configuration, Florian Haas has a talk tomorrow about HA for OpenStack. I believe that is the documented way to do HA with OpenStack. It's not official, it's not required, but it's a pacemaker with Galera for my sequel, and I, you know, boo, yeah, I hear you. I do, that is finished now. Yeah, the pacemaker stuff, I started a bar clamp for Crowbar. It sets up the services, but it doesn't manage any of them. So, pacemaker gets ready, and then it's like, then I ran into the problem like, oh wait, you know, every service inside a chef is thinking it's gonna be able to restart services when pacemaker's one is gonna be managing it, and so they're gonna conflict, and then I just was like, I'm busy, you know. Well, I mean really, I got busy with something else, and so people who asked me, hey, is there a pacemaker cookbook? I'm like, it's half done. You know, a pacemaker's up and running. What more do you need? Mine enables it and sets up like the masters and slaves, and they all know about each other, but none of the services are managed. Because then it's, yeah, it is really insane, because I started thinking, well, do I need to monkey patch something, or do I need to extend the chef base service to be a know-op, and so there's an alternate HA implementation that one of the gentlemen from crowd scaling stop by, I don't see if you're here. He's got to talk, I think, Wednesday about how they do HA that would not be using pacemaker that uses like BGP routing, and he said they're thinking about open sourcing those cookbooks, so maybe we look at that. I don't know. Or we can have us, I can sit down and try to stick somebody who knows Chef a lot better than I do on pacemaker itself. Yes. Yeah, Carl wears all those hats. But yeah, I don't know what the right answer is for HA, but it is something we could start taking a stab at. So yeah, that's officially supportable with Folsom. It's a good topic for the mailing list, or the summit, yeah. All right, so now we've got two talks for the summit. We've got another general open stack one, and we have a, can we do pacemaker services? As well as Galera is not that exciting, and RabbitMQ clustering is, well no, no, it has its own clustering stuff. Yeah, yeah. Or not use Rabbit, and then something else, but it's not DRBD, so it's not HA pairs, it's an HA bigger than pairs, yeah. Quantum, so quantum, who's got quantum running? Okay, what are you running? There you go, so for the record, I'm looking at the video camera here. Carl Perry from Dreamhost. We'll make sure that we get some working quantum cookbooks out there. I believe last time I talked with RxBase about it, they were going to stick with Nova Network until they had a customer who had a real use for quantum. Sounds like we have a real use for quantum here. Somebody is using it in anger. There is, there are other implementations out there that are not NYSERA and not OVF, and we'll be working with those as well. That's how it should be. And using that same pattern, I plan on applying that to the database as well as to the hypervisor. The hypervisor currently just is like, I'm gonna do Liberty KVM, and it's all mixed in with Nova, and we're pulling that out. So you can say, here's an attribute. What are we gonna do? KVM, LXC, bare metal someday, maybe, I don't know, continue supporting Nova. I mean, I know you have the opinions, but yeah, well that's all we have support for. We're just for the mailing list. We will continue to support Nova Network at least through Grizzly, because that's as long as it's supposed to last, right? Well, I thought it was being dropped after for Grizzly. Some other session will probably answer that for us. Sender, RxBase is using NovaVarium, and you guys had a, somebody told me they had patches to remove. To make sure it did not blow up, because right now, if it's, in my setup, it just stack traces out, and I don't care, because I'm not using it, but you guys are using it, right? Well, so I'm not like, just farming out all the work, I'm actually gonna be doing professional services for a customer on Folsom Cookbooks, and we'll be open sourcing it, so maybe I'll do NovaVariums, or Sender, sorry. Not gonna own it, that's fine. Does anybody want Solometer? Yes. Yes. Okay, well, I do know that there's another Solometer cookbook, at least in the works. Do you have one? I thought I saw you say you were right in one. No, all right, never mind. I'll get back to you on that. And I expect there are other people who are interested and will be working on it, you know. Is there, are there any other projects that should be on our radar for Folsom? Is there like somebody who wants us to do an idea or something like that, or? I just saw that, I thought that was a neat project. You know, the glacier.  Because I don't really, I mean, I'm not a, you know, I don't see a lot of it in my day to day, so it doesn't, I mean, I don't see a lot of cloud formation myself, and I see a lot of AWS. So I don't, it's not motivating me. But if there are people who want it, we want to support it.  You know, it's a community effort here. And, you know, we'll have a flag that says heat, yes. So other projects are kind of building off of this ecosystem.  It's picked up a lot of traction because of this, because I was using it. I switched to using Librarian. If you're not familiar with Librarian, it is a tool for managing your cookbooks. Spice Weasel also manages your cookbooks, but it doesn't know anything about Git. Librarian does, and so I had to switch over to something that was Git. I will be happy to add support for WISC. So Duly noted, the gentleman in the back who's an author of a competing tool. I don't care. I mean, if you want to take the Librarian stuff and show me working with WISC, and it just works. Yeah, I mean, we're not strongly attached to Librarian. It just, it works for our use case of, yeah. Yeah, and I switched to Librarian from Spice Weasel because Spice Weasel knows about the community site, but not everything was up there yet. And so, yeah. And Librarian, I'm able to track my forks and give it branches and tags, and that's, as far as I know, all I wanted. But I did not want Git sub-modules. So if somebody says, how come you're not using Git sub-modules? It's because like, there you go. Duly noted the man from Dell for the record. I said, you know, and you guys were the ones who encouraged me to do it, but it was, I came to that realization a long time ago.  If we want to make it work with WISC or Berkshelf, I don't care. Yeah. I mean, once it's in place, it's easy to keep them in sync. It's like, I replace the one here with the two, four files. Yeah. So yeah, what Spice Weasel gives us is it also manages the roles, environments, data bags, and pushes those up too. But I've been meaning to either have Spice Weasel understand those other tools or take the patches from Spice Weasel and push them into the other tools. I don't care. Pixie Dust, if you do not have a solution for provisioning your hardware, who's written their own? Yeah, so as provisioning your hardware is like, you're going to have to do it. That's not a chef thing.  Pixie Dust is a very minimalist. Pixie booting, TFTP, OS installation. It does Ubuntu 1204 or Debian 605 off a pre-seed. That's all it does. And puts chef on the box. So you will need to solve that problem. That is not in the umbrella of chef for OpenStack. You know, you need to have boxes with chef on them. And, you know, there's Crowbar, which is kind of parallel to a lot of this as well. And so these are projects that have a halo effect. You know, some of the work that they do comes back into Chef for OpenStack.  Or, you know, the database cookbook. Yeah, I mean, all the cookbooks are getting benefits from this. And I guess I need to add a bullet point for when I give this talk tomorrow more formally. You know, Test Kitchen. Test Kitchen is something we open sourced about six or seven weeks ago. It's a test framework from Opscode. It's all open source. That will run, use it to run tests against your cookbooks. So it runs men test, chef's spec, cucumber, food critic, you know. But it runs them against vagrant. Which is, you know, it's great if you're running a Mac. But, you know, some of us aren't. I am, but there is an OpenStack provider that's like Ticket Test Kitchen Five or something like that. Okay, yeah, sorry. Vagrant does work with Linux as well. I always just see people complain about it crashing their Macs. Mitchell? Yeah. So, Mitchell Hashimoto, the guy who's, you know, behind Vagrant Up, he sponsored by VMware to make it work with Fusion.  Yes, yeah, that's actually why I don't use Vagrant as I use Fusion. But the point is, Vagrant's gonna take a while to get to, you know, more back ends. And Test Kitchen is, we wanted it to run against OpenStack. So there is an OpenStack provider.  And so it will, you know, do Ubuntu 10.04, 11.04, 12.04, Debian, 32-bit, 64-bit, Windows, whatever.  Bring it up, bring it down. It's a patch set. I don't think it's been released. Yeah. And so rather than use Vagrant, we could use OpenStack and we could probably do it parallel and it'd be a lot faster. Yeah. And we use, you know, OpsCode's plan for Test Kitchen is we're going to run all of the community cookbooks with Test Kitchen. And we have a big rack of OpenStack gear that we have and we're going to make it all work on that eventually. So we'll probably talk about that next week, you know, at the summit, but, you know, Test Kitchen's all open source, you can use it today. It does not have to be running Test4Chef. It's just a test running framework that currently uses Vagrant, but if we could get it to OpenStack, then it has all sorts of other useful features. So once you stand up your OpenStack Cloud, you could use it to test your company's application. So that is probably enough talking for today. Is there anything somebody wants me to talk about in addition that I might have passed over? You're like, why didn't he talk about, yes? So yeah, the CLA question. I have been asking people to fill out the CLA because this isn't, we, you know, OpsCode asked people to fill out a Apache licensed CLA to ensure that you were giving code freely. You know, we don't want to get into the Neville, you know, or was it Neville? Not Neville. Sco versus Neville versus IBM, drag it on. I mean, it's the Apache CLA. Yeah, exactly.  But we do it, you know. So yes, this is an, this is a OpsCode sponsored project. We do try to get the CLA out of everyone who's contributed. Rackspace has done it, Dell's done it. And Dreamhost has done it. HP's done it. Sousa has done it. Yeah, I mean, we were, and then we'll talk about it at the summit some more next week about what we can do to make the CLA even better. If you have an existing OpsCode CLA, it's already covered. You know, we don't make you do it like, oh, now I'm contributing to this plugin. I gotta do it again. It's like, yeah, you do it once it's good. Apparently it's not that bad. 930 people have already done it. And 170 companies have done it. So, you know, hopefully your employers on the list will get you added. You know, it's Apache. We just covered our, you know, back sides. I'll be around. OpsCode booth is out there. I've got this, a real version of this talk tomorrow for, you know, your bosses or whatever. Tomorrow 1.50, we have a deployment panel tomorrow. Party tonight. Dreamhost, Mirantis. Thanks guys.


Hi everybody. Happy Monday. I'm Joe for jaspyscasebrakes.com coming at you with 21 22 panini elite basketball Six box half case picker team number 10 nine and 10 of course are from the same case all card ship a lot of great stuff Here we finally are starting to get into some products that feature the current draft class So big thanks everybody for getting in on the action. No fillers either We've been selling these out straight up which I appreciate Evan ended up with last spot mojo with the spurs Good luck to him. Good luck to everybody. I remember from the last case. We did. I marked all those boxes 10 So, you know, they're all from the same case. Let's get in on it All right, anyone uh, I know Hollywood's here, but anyone else In this break watching live It's been kind of quiet in the chat today anybody here in general My Are we still streaming it looks like we're still alive. There's 27 people watching I guess they're just like just chill today. That's not Mike Joseph is here looking for a train whistle. Oh, Hollywood. You miss the Suns in this one That's what you're you're chasing Suns. Why is this a third break of the day? I don't know is it? Maybe whatever the schedule says It's all there So Jonathan's bummed because he's like, of course, this is the time where I don't get the team. I want this is where the hit I want will pop Find out I'll try to keep the names right here as much as possible so you can see what's happening in here, but They're pretty clean-looking car. I kind of like this very simple clean design just the player You know the product badge name team logo There's Brandon Boston, Jr. For the Clippers to 999 Zion Williamson spellbound to 99 Zion for Minsoo and the Pelicans and then the Brandon Boston, Jr. Goes to Jonathan and the Clippers And of course all car chip if I have to miss something I don't think I will but I Like that the numbers are on the front 27 out of 99 miles bridges for the Hornets Minsoo and our first autograph is Jonathan coming up JK 19 out of 149 pen pals autograph There you go 19 out of 149 he's been getting some some minutes Chaumatic with the Golden State Warriors glass cleaners We Got six out of 86 Isaiah Todd rookie die cut for the Wizards. That's gonna go to David Got another letter for Zion that one's not numbered though Braun James So only the There's no base Rookie cards, right? If it's a rookie car. They're all numbered and there is Jeff Malone 23 out of 35 turn of the century autograph for Danny and the jazz The deck card. Oh the one that looks like a playing card. Are those short prints? Traditionally they have not been short prints These cards. I don't think these are short prints. Let's go to cardboard connection calm It just says look for new clarity and debt cards. I Think the short prints are those 3d cards and these debt cards can be numbered to 10 Black one-of-ones as well 30 cards in the checklist Yeah, traditionally those haven't been short print short prints, but it's good to check because they could they could change it on you In any particular year. I second box. I do not know. I'm good. Thank you Yeah, I think the base cards are all Non rookies and the rookies if there's a rookie card, it'll be numbered to at least 999 There it is 16 out of 99 rookie Corey Kispert David and the Wizards that's to 49 and there's Josh Richardson for the Celtics to 99 and there's Rookie yearbooks Chris Duarte Rookie order for the Pacers for Jeremy. I think this is the player one of the players that he was looking for not numbered But but really nice There you go. I'm not sure how he's been doing this season, but Hopefully he's been doing well There you go. Jeremy called it. There he is You got it nailed it and there's Jalen Suggs 124 out of 999 for the Orlando magic. That's for Danny in Orlando Suggs your fifth overall pick Chris Duarte 13th overall pick Chris Paul, he's gonna be out for a minute or two Fractured thumb steering Fox deck and a Darius Garland to 49 It's for Danny in the calves Spellbound Yanis and for the Rockets that's impact impressions autograph Kenny the Jet Smith And that's for Houston. That's gonna be for Danny and the Rockets. All right next box Yeah, we have Baylor, Oklahoma on in the background or Oklahoma State We're almost to that time the almost Madness time should be a lot of fun. It's kind of crazy to think I was like This this sports week seems a little quiet until NBA kicks off again on Thursday And I was like, right this time of year. We'd be talking spring training. We're talking spring training baseball You know, I'm just kind of seeing no now Now a baseball in this lot in this lockout, which is Unfortunate Both sides seem to be so far apart. It's got to wait But NBA action will kick off again on Thursday Pretty fun ceremonial second half of the season Starting up and see how these teams race to the finish There's a Josh Giddy. Nice 57 out of 210 in that orange parallel. I think Jason's a big fan of this player right here Your sixth overall pick from Australia. I think he's having a great season, too LeBron James to 99 and There's Trey Mann Josh Giddy's teammate to 999 Both of those going to OKC Brian Croft There's LeBron James to 99. That's the L of LeBron I've been to some card shows where where I've seen in someone's showcase these all like Collected together the whole the whole name it looks pretty cool actually when you when you get all those letters together It's a good little good little set to build a nice chase Tim Hardaway junior to 99 Jeffrey and Dallas see that's not out of 99. So that wouldn't wouldn't match There's Ricky Pierce impact impressions autograph That is for Danny and the Boston Celtics And nice low number here 5 out of 10 CJ McCollum and that is still a trailblazers edition I'll go to Hollywood. I go to Jonathan and we got a Josh Giddy autograph. Nice Using a silver ink here 85 out of 149 Brian Croft with the Oklahoma City Thunder So Oliver what's going on feel like Josh Giddy. Let me just double just since we pulled his autograph Like he's been having a pretty good season from Melbourne, Australia 6th overall pick He's averaging about 12 points 12.4 points almost eight rebounds and six assists a game. It's pretty good pretty good numbers For the Rook a halfway through this half case break now Oliver saying Giddy's got some really good court vision About six eight to ten Kind of kind of does a point guard shooting guard sort of thing Okay, see has a bunch of picks too. I feel like I Feel like they could really put together a Really good team and then maybe send some of those picks away to get some other players They could build a they could probably rebuild a Competitive team pretty quickly. I think so. We'll be topping to 99 die cut We've got a Santi Aldama 978 out of 999 for the Grizzlies Anthony. No, I'm good Chris. Thank you. Have a good one man Tomorrow nice All right, and the autograph sitting here is Ralph Samson five out of ten Impact impressions Danny and the Rockets and that gold looks really sharp against the red nice There's Quinton Grimes three oh five out of nine and ninety nine For the Knicks that's gonna be for Shane and the Knicks Tough curry. There's your all-star MVP also our game MVP And we've got a Jason Tatum to 99 That'll be for Danny in the Celtics And we got a Luca Garza Autograph for the Pistons Is he is he having a good season? I feel like I've been hearing Luca Garza's name He's a mid a second round pick. I don't know was he in a futures game or something like that Anyway, nice autograph for Danny and the Detroit Pistons. All right two boxes to go I guess he might saying he's got some time when people were hurt. Maybe that's where I was hearing He's having about five point two points per game a few rebounds and almost an assist a game Big man Center 611 235 Go went to Iowa got the auto here early Yes, turn of the century autograph 144 out of 149 that's George Murson David with the wizard sold Washington bullet There's D'Angelo Russell to 99 For Minnesota, that'll be for max and there's Luca Garza again This time 303 out of 999 for Detroit will be for Danny and another rookie card 747 at a 999 that's a Sharif Cooper for Danny and the ATL Jama rent spellbound die cut and your autograph is Miles McBride For the Knicks that's gonna go to shang and the New York Knicks Little shaving of the Of the card when they're cutting them right final box So what does everyone think for the remainder of the season? What's gonna happen? I think the West is pretty much set suppose the Warriors have an outside chance of catching the Suns And the Grizzlies are right there than the Jazz Mavs nuggets and in those the play-in teams timber wolves clippers Lakers and trailblazers and the Spurs and Pelicans are a couple games behind Behind a play-in spot So let's see if anybody The Spurs or Pelicans can catch the trailblazers Gosh, hopefully the Lakers don't slip too far down there. I think the play-in Is their best bet while Anthony Davis is out. Let's see what uh Let's see what LeBron James' motivation levels are For the remainder of the season After the Lakers really didn't do much at the trading deadline The the east is a lot tighter One through seeds one through six The heat and bulls are tied at the top of the east But the Celtics are only four and a half games behind they're in the sixth And they're only four and a half games behind the heat and the bulls And the Celtics went into the all-star break hot They're nine and one And they're last 10 going into the all-star break So if they could regain that heat they could be climbing up that leaderboard And then the Raptors nets Hornets Hawks are in the uh are in the play-in spots. Jeremy's Pacers They are They're a little ways behind a play-in spot. Well, hopefully Tyrese Halliburton Will continue to grow and kind of build around Around him The Miles Turner All right, final box And our first autograph is already popping. It's right here. It's Kai Jones with the Hornets That'll be for Min Soo Purchase do I do I need the order number? No That's for you But I get the same email order confirmation that you do. That's how I go through orders So as long as you have it I have it too And there's one Toscano Anderson to 999 a nice little uh dunk contest appearance That's for Shawn Matic and the Warriors the last stack I Got an Isaiah Jackson to 999 Jeremy with his Pacers And our last auto is Danny Manning impact impressions autograph for the Clippers That is for Jonathan and that my friends Is that it's a quick little recap here Thanks for watching. Thanks for breaking with us ladies and gentlemen really appreciate it More in the store check it out And I'll see you next time for the next break. Bye. Bye


Okay. Given that we are from Switzerland, we are going to try and start on time. So let's get going. Welcome everyone. My name is Diego Zamboni. I'm from Swisscom and my friend and colleague Bill Chapman. We're going to give this talk on self-disruption and healing on a CloudHunter-based environment. Do you want to introduce yourself? Sure. I'm Bill Chapman. I'm a cloud architect, Stark and Wayne. I've been attached to Swisscom for a couple of years now, and these two projects we're going to talk about are a culmination of a lot of the effort Diego and I have had together. Alright. First of all, I'd like to comment briefly on how interesting it is to have my name at a CloudHunter conference. I mean, we all have instinctive reactions to our names, right? So it's weird to be hearing it everywhere. Anyway, so just a brief overview of the agenda. Normally when we talk about this in Switzerland, we have to explain what CloudHunter is, whereas here we probably have to explain a bit what Swisscom is. So we're going to do that very briefly, and then we're going to talk about the two counterparts of this effort. One is the health management monitoring and self-healing platform that we've been building, and the other is a self-disruption platform that we've been building, which we've appropriately named Chaos Heidi as a tip of the hat to Chaos Monkey. So very briefly, this is my one marketing slide from Swisscom. Basically, Swisscom is the biggest telecom provider in Switzerland, providing everything from fixed line, internet, cellular service, outsourcing services for big companies, connectivity, all sorts of things. And now, very recently, a PaaS platform built on top of Cloud Foundry, which we have named the Swisscom application cloud. There's a URL over there if you want to try it out. We have a publicly available version of the service, which is available to anyone in the world. There's our Twitter handle, so you can follow up what gets announced. And basically, this is just a very brief architectural overview. It's built using Cloud Foundry on top of OpenStack, using a few different components for the infrastructure. For SDN, we use Plumgrid. We use Scale.io for storage. We have a few other things here and there. We have built a number of services that can be used together with the platform. So we have Redis, MongoDB, Elk, RabbitMQ, and a few other things that our users can connect to their applications. So one of the basic ideas of the application cloud is that we have all of these components, but we don't have just one instance of this. Instead, our intention and what we are actually doing already in production is to have multiple instances of this construct called the application cloud for different uses. So we have a public instance, we have an internal, Swisscom internal instance for internal applications, and we have virtual private instances for different customers. And of course, all of these need to be monitored, need to be managed, need to be operated at scale. And one of the realizations is that Cloud Foundry itself has self-healing, has also all these nice features, but we're not just using Cloud Foundry. We're using all of these other components that together create this service and this application. So this is where all of this comes from. So how do we monitor a Cloud Foundry production environment? We are using this, from the beginning, this thought concept called the UDA loop. Sorry, wrong circle. This is the UDA loop. Basically, it's a well-known idea that originated originally in the US military, in the US Air Force. And it's one of these typical feedback loops, and it stands for observe, orient, decide, and act. Basically, the idea is that you collect information about what's going on. You analyze this information, you make decisions based on what you discover, and then you act in reaction to the current conditions. And then this repeats over and over, and this allows you to adjust the course of action in reaction to what's happening around you. So one of our early realizations is that these UDA loops are already all over the place in our infrastructure. But they are mostly incomplete, and they are mostly disjoint. So each component has its own little version of a self-monitoring, self-healing component. Some of them only fix certain things. Some of them monitor certain parts and tell you about it, but they don't fix anything. Others just fix things, but they don't tell you what's going on inside. So it's a bit of mix and match, and we don't want to reinvent all of these components. Rather, we want to use what's already there in different forms. I mean, we have different self-healing, health-checking, self-management, scripts and bits and pieces all over the place. And we want to aggregate the data that they are providing, and we want to aggregate their functionality and build a layer on top. Now, ideally, at the end of the tunnel, we would like to automate humans out of the equation and have all of the decisions made automatically. This is clearly not possible realistically with our technology. So we want to keep humans in the loop, but delegate to humans only the really hard tasks and the really hard decisions. So we want to, over time, learn to automate more and more of these solutions to problems or at least detection and notification of problems so that our operations teams and our engineering teams can focus on solving the really hard problems that we don't know how to solve automatically. I should clarify, we're not talking about artificial intelligence or machine learning. This is really very simple rule-building and, iteratively, increasing our knowledge base to automate these things. Also, in parallel, we're building this self-disruption platform that was inspired by Netflix's Chaos Monkey project, which we call Chaos Heidi. And the idea is to introduce automatically disruptions and destruction in the infrastructure so that we can test both our detection and our reaction capabilities. So, overall, we want to use, and this is all called Orchard, of course, we want to improve visibility into our systems and the ultimate goal is to make everyone's lives easier. Not only the operations teams, but also the engineering teams, the development teams and even the customers by giving them access to some of these data. So, just to give you a very brief overview, Orchard is really a backend system, but we discovered very early on that you cannot properly demo something without having a visual component. So, we have a very simple dashboard that basically gives us different views into the model, the data that is stored into the system. So, we can have views that give us information about the state of the infrastructure components, such as OpenStack or Scale.io or Plumgrid. We can also have views into our business integration and end-to-end service processes, such as end-to-end checks on our Atmos service or Elk service or MongoDB or whatnot, our building runs or logging subsystems and so on. We can also have views on the checks that are being run on the Cloud Foundry Services infrastructure. So, on the containers and the VMs on which the instances of the services are being executed. So, and this is just a matter of reconfiguring the view according to what is it that we want to look at, right? In terms of an implementation, I'm not going to go through this in detail because we don't have enough time, but I just want to point out that we are basically collecting data from the infrastructure. We have different types of data. Our main state checking data comes from Consul. We are using Consul, which is an open-source health management and service discovery platform. So, Consul allows us to distribute checks throughout all of the nodes in the infrastructure, and then we can customize the checks depending on each component, and all of these results are being centralized in a Consul cluster. We're also collecting logging messages and metrics from Cloud Foundry. We are using both the stock logging and mirroring mechanisms built into Cloud Foundry we're now building in log-regator integration. We also developed, actually, build, developed a custom Bosch monitoring plugin that allows us to check the states of the Bosch components and post them directly to Consul. All of this is fed into a message bus, and then we're using Reman, which is an open-source event processing engine. To fetch these events and then apply custom rules on them. So, we are building a set of rules that range from very generic aggregation and summarization rules of the overall state of a certain component or a set of components. And also, we are over time starting to add more specific rules for specific services, specific customers or specific purposes. Also, for example, for computation of service levels and so on. From Reman, we can feed data into some of our other systems. We are using Splunk in Swisscom already since a long time, so we're feeding some data to Splunk for archival and notification. We are feeding data into an inflex DB database for longer term storage and we're feeding the dashboard from then. And then we are closing the loop, and you can roughly map this to the UDA loop that I showed you earlier by trying to trigger some automatic reactions to the failures. This is still very early phase. We have some automatic reactions built in, but this is still very much work in progress. So, I'm going to hand the voice now to Bill, so he can tell us about chaos hiding. Hello. So, as my team can attest to, standing there silent for nine minutes, ten minutes with all of your people in front of me, was very difficult. So, what is chaos hiding? Chaos hiding is a resiliency testing framework, kind of like Chaos Monkey, Chaos Loris, Chaos Lemur, Chaos Gorilla. These are all products. Chaos Lemur and Chaos Loris are actually Bosch and Cloud Foundry based. But this is a little different, because whereas those solutions tend to be targeted at a specific type of attack, like kill VMs or a specific platform mess with Cloud Foundry, this is a generic attack framework written in Go. So, as I said before, I'm from Stark and Wayne, and normally at Stark and Wayne we create stuff. You know, projects like SHIELD that some of my colleagues spoke about earlier, they're used for disaster recovery and protecting the data and making sure that we can come in and help you fix things. But Swisscom, I've had a relationship, we've had a relationship with them for quite a while, and they said, you guys are pretty good at making stuff that keeps things running. Can you break stuff for us? We can do that, too. So, why do we want to break stuff? Well, you know, people will say, well, Cloud Foundry is self-healing or, boss, you can run a Resorector or this technology does this, this technology does that. Well, it turns out that the modern Cloud Stack is a really complex ecosystem, both open source and vendor driven components that are glued together by locally developed bespoke solutions. And I use this term, Semper vigilante, and I always thought it meant always vigilant. It turns out when I was putting the slide together, it means always watching, but I left it here anyways. So, this is, you can think about as really aggressively watching your stack, right? Because you're not just watching it, you're poking at it, like a little kid who can't look at anything without touching it, and that's what KSID is, and that's where the name comes from. So what might we want to do with a resiliency testing framework? Well, things like stack validation, running random daily attack scenarios like you would do with a Netflix Chaos Monkey. What we use it for now, because we're still in the active development phase, is for testing of orchard components. So orchard has healing components, and it's a lot easier to test those healing components if we can keep taking things down. It can see that something's down and then try to fix it. So how does it work? That's pretty simple. You've got a controller with handle scheduling, orchestration, monitoring things. It holds all of the attack scripts, which are just attacks that can happen on an environment, and then you have an agent. Now, an agent is a small process that sits anywhere that has both the technologies and the access to the victim. So you can think of maybe Bosch as a victim, and your Bosch, your Bastion, your Bosch Jump Host will be where you might put your Heidi agent. In practice, the way our architecture is set up, we would put the Heidi agent anywhere we put a console agent, because it's convenient that way, and then the puppet automation can just set that up for us. An attack runs on an agent, and it is a combination of a set of configuration and a script of some sort, and that way we can have multiple attacks that do the same thing, but with different parameters, different targets.  We might have one that kills a runner and one that kills H.A. Proxy, and we can run them randomly.  It's interesting.  You can really do anything. Like I said, it's not specifically related to any platform or target technology. So how do we create useful attacks? And number one here is probably where we get most of our attacks from. What is broken right now? We talk to the ops team and we say, you know, what's going on here? We talk to the Cloud Foundry Services team and they say this is what is now broken. So what we can do is we can create an attack for them, and then when they fix the problem, we can then implement that fix as a healing action in Orchard, and now we have a regression for what that problem might have been. What is broken in the past? Well, if we ever run out of things that are currently on fire, we can start looking into the past and say, okay, well, what used to be broken? And that, again, another layer of regression. And then what will break in the future? This isn't really an academic project. This is a practical project. It might get to the point where we have to come up with clever recipes based on patterns that we've seen, but I don't see what will break in the future to be a part of development for a while, if anytime soon. I don't know, we'll see. So something that broke recently. Oh, wait a minute, sorry. I like getting paid. So we're going to blame this one on the virtual network. So there's a problem we're dealing with right now where the network goes down and Bosch will lose connectivity with one of its jobs. The Resurrector will kick off, but it'll fail. And then we end up with this ghosted job and then somebody down the line might decide that they want to bring that back up again because they need it. And now you end up with a new version of it and a ghosted version of it. And this is a problem we're experiencing in production right now. So we've been trying to emulate it. And it turns out it's a really fascinating process of trying to figure out how to break something. You'd feel like, oh, I can do this. Breaking things is easy. But we run into this problem of simulation versus emulation. We can imply a failure, or we can actually cause that failure, but sometimes causing that failure isn't very practical. Actually taking a whole segment of the network down isn't necessarily going to be as practical as monkeying with your host's deny or monkeying with IP tables just to make a single node think that there's a problem. And this turns out to be a really interesting and difficult problem to solve. So here's an example from what we were just talking about.  So this is an attack that we have.  And so we take out this HA proxy. Well, of course, great. We just tested that the Resorector works. Excellent job. That's not very helpful. So what do we have to do? We have to kill the Resorector. Well, we kill the Bosch job and the Resorector, but this isn't really the problem. The problem started because of a network outage. And if you run a CCK, it's going to fix the problem anyway. So now we simulate an outage between the Bosch job VM and the director. And now we've recreated the problem. And when someone tries to resurrect that VM, we end up with a ghosted VM. Great. So we figured out how to simulate the error state. But what did we do? Well, put a deny rule in IP tables, right? And we end up with a situation where, how are we training Orchard to heal that? Because that's not what's going to happen in real time in the real world, right? Unless someone maybe pushed a configuration change that they shouldn't have. But more likely it's going to be related to a problem scaling or a problem with network traffic somewhere. So how does Orchard fix this? And now I'm confused because they told me I just had to break stuff, right? But now we come around to the problem of how are we training Orchard to properly fix things? And this is where we're at right now. We've got a suite of attacks that can do all kinds of really interesting things. We've got a way to orchestrate it. We've got a way to keep track of it. And now we've got to figure out how to make those attacks useful so that we can train Orchard to do what it needs to do. It's currently an internal project at Swisscom. I've been asked to gauge interest and see if there was interest in other people seeing this and open sourcing it. I don't have the go ahead to do that at this point, but if there is enough interest in it, then we can probably make the case. And I think it's a really cool project that people would like to play with. So if you do have any questions about that, come talk to us so that we know. And Diego, do you have anything else to say? Just to repeat what Bill said, come talk to us if you're interested. This is still very much work in progress. This is where we are right now, but there's still a lot to do. And if nothing else, we have application cloud stickers. So if you want to come and get one, come talk to us. Thank you. Thanks. And we got you out of here quickly. Yeah, I was wondering for the agents, what is that? Did you write that yourself? Okay, so the agents are, there's a small go process that can run as either a controller or an agent node. They communicate via RabbitMQ, and I actually apologize. I went way too fast through the architecture slide. But the agent node has all of the configuration and individual attack because we don't want to pass any credentials or anything over the wire. So an agent knows everything about what it needs to do, and all it does is run that script and then tell the controller what happened. It has no healing component.  It find out what happened, tell the controller what happened, and wait for Orchard to try to fix the problem. No, no, this is an internally developed project at Swisscom, yes. Do you have any suggestions? Have you seen this paradigm before? There's a different way you would do it. In our case, it's not allowed. The access, I mean, we could probably use the puppet M-collective. We could probably use a puppet, but we can't SSH into, you know, if you can't, in this environment, if we can't communicate via an API or some other way, we have to have an agent and the agent communicates via the queue, but there's no direct access. Yeah, the... Well, no, not right now, we're not. But it would be neat if we could be. In the lab environments, it's good for stack validation and testing new features and things like that, but the end goal would be to maybe run it in production, but that takes a much larger buy-in, I think. Well, Netflix, Cast Monkey and Cast Gorilla and the rest of the Simeon Army project, they do similar things to what Orchard as a whole does, but Cast Monkey is really just dealing with killing VMs and Cast Gorilla deals with network latency, I think, but that's such a small part of the attack ecosystem that we're trying to accomplish, that it was either piggyback on top of those or see how far we could get on our own because there were so many more attacks we needed to write.


Reactive oxygen species, ROS, play a vital role in the progression of cardiovascular diseases. This review focuses on pathways behind the production of ROS, its involvement in intracellular signalling cascades leading to several cardiovascular disorders, endothelial dysfunction, ischemia reperfusion, and atherosclerosis. This article was authored by Nisha Panth, Keshav Raj portal, and Kalpana Parajuli.


Hi again in this lesson. We're going to talk about that how to add an element to a set in Python programming language First, let's make some set let's call it my set and Let's populate it with few numbers one two three four and five so our set He has five Elements one two three four and five if we want to add to our set some new element We'll use method add With that method we can add an element to a set so we want to add to this set some new element, but What will happen if we try to add an existing element if we in this example want to try to add number two which is Already inside our set. What will happen? If we try to see our Set after calling this method We will see that our set Has just one Number two so if you try to add number that already exists in That set nothing will happen. You will not have situation like that to have Two times number two because you added again because if You try to think a little bit about it set is an unordered collection of unique elements So elements inside our sets needs to be unique so we can add some new element by again using method add but We want to provide as an argument element that is not yet Inside our set and if we try to add element seven which isn't in this set and If we try to see our new resulting set We will see that our Number seven is was added to our set So if you want to add new item To the set you can use method add to add This element that's all in this video See you in next next lesson


Okay, very good morning to you. Hope you're doing well. It's Thursday 25th of November and of course a happy Thanksgiving to anyone in the US that listens to this briefing I hope you have a really great day and a really great weekend as well with your family and friends and Hopefully all is well despite rocketing food prices. I'm sure your Christmas turkey is a little bit more expensive than it Normally was but yeah, I hope you enjoy it and see you guys on Monday But otherwise in terms of the briefing for today We're gonna touch upon a lot of the information that came out yesterday because of the Thanksgiving closures that we're seeing today So there's no equity or bond market trade today and shorten sessions on Friday in the US And so we had a very concentrated day yesterday We'll have a bit of a recap of that quick look at the charts And then there's updates on some Fed commentary OPEC commentary and then also the COVID situation in mainland Europe namely that in Germany as well now that they've named their coalition government yesterday so kicking things off then how did the charts look this morning and actually we had a Generally positive close on Wall Street yesterday The S&P was up a quarter of 1% nasdaq up 0.44 the Dow was basically flat And looking at equity index futures this morning generally on a firmer footing at least for now and actually I just want to kick that off with a Straight into the S&P 500 futures chart here. You can see yesterday we really did see a decent move to the upside and Overall, what did we have well US personal spending rose in October for a month earlier by more than expected While a closely watched inflation measure the PCE numbers of course posted their largest annual increase in three decades Not the most surprising thing on the latter point given the inflation figure had done the same in the last two weeks In addition though we had data show 199,000 people made initial jobless claims in the period ending November 20th the least actually since 1969 while orders placed with US factories for business equipment rose in October by more than forecast Highlighting solid momentum for capital investment at the start of the fourth quarter. So overall Some some decent numbers and and certainly feeds into the narrative as well of of what the Slight pivot to a more hawkish direction for some of these Fed members, but we'll come to that in the minutes in a moment Looking at the S&P 500 here, then we've had a bit of a breakout from late last night through the end of Wall Street Through the top end of that area that had been restricting some of the price action going back to kind of Tuesday of this week And we've just continued that upward trend as we've gone through the Asia session not a great deal to speak of really of of large magnitude coming out of the Asia news flow and so we're now up in the futures market up at the R1 in the S&P 500 future already on a daily perspective I did mark this up Yesterday and this was taking a look. So right here. I'm on quite a high time frame This is a daily Continuation chart and as we come in towards the year end and I'll be talking probably about this more in the coming weeks Number of these big banks start putting out their outlook and thus their forecasting for things like where the S&P 500 year-end target Will be for 2022 and I just thought I'd continue to populate this chart as and when these come in and here's just a Few so as we know Things Mike Wilson who's the US strategist at Morgan Stanley has always been the kind of perma bear on the big Wall Street banks in terms of His thoughts on US equities and he remains that way his year-end call for the end of next year is at 4400 the most bearish out of these Selection of names the most optimistic is Wells Fargo. They're actually looking for a range of between 51 5300 on the upsides are right up here And then you've got RBC, Goldman's, Jeffery's all clustered around the 5000 mark I'd love to hear what you guys think so drop a comment. Let me know what your end of Year 2022 call is for the S&P 500 and perhaps Come 12 months from now. We can look back on this and crown our champion Who's gonna be there? I'll also drop my forecast in the comments as well. So I'll keep you in suspense Until you get to the end of the briefing to have a look But the other thing of course we had yesterday was the FMC minutes and actually again supportive of this general rhetoric we've been hearing from Fed officials because At their last meeting they stressed the need for flexibility on how quickly they will scale back their Bomb buying program as well as the timing on interest rate increases And this came all before data has showed inflation accelerating I in CPI and the PC is yesterday and so Again, it has shifted the needle a little bit and you know, this lady here is Mary Daley. She's the Reserve Bank president of San Francisco And she is generally quite dovish and she came out yesterday and said it would be hard to argue against Faster reduction in bomb purchases if reports in the labor market and consumer prices due out early next month Show continued strength. So I think that's a good kind of measure to go off so basically as we know labor market inflation are two key metrics and Really twist the arm far enough to speed up tapering for a dove They just need to see more consistency to those patterns So the labor market is kind of falling into step now is with inflation early at that point And if that continues for another month then as per Daley's comments, I think they're probably right They'll start getting more serious about this, but this has really really been the case We've had this from a lots of different officials now and this is the kind of very Sly gradual shift that we're seeing is some of the forward guidance at the moment coming out of the Fed So the dollar generally still remains pretty well bid and actually if you're looking at euro dollar on the daily chart We've kind of hit our target It's a level we've been looking at for a for a while and a number of these briefings over the last two weeks Really, whatever since we broke that 115 area, which obviously was quite key from a technical perspective You can see here from these previous ellipses going back to 2019 2020 price action and we were talking about the ultimate target being down on those shorts on a policy divergence Kind of idea that would be down at the 112 handles So we've had a nice three-point move there as we were kind of anticipating You know, we talked about this Piers and I a lot on the podcast as well two weeks ago It's a nice to see that that move come through and it'd be interested to see now Does that have any more longevity for euro dollar at this point or given the Thanksgiving holiday now? There's this kind of run out a bit of momentum for the time being and perhaps we just Consolidate around these levels and that holds for the time for the time being for now Otherwise, it's pretty light over on on major news flow. The other things to mention would be OPEC obviously quite a lot of people just looking out for any potential response that any OPEC plus members might have to the news that we've had this week about the US tapping the SPR in Step with some other Far East partners and Asian partners The UAE has been probably the most vocal, but I haven't really given away a great deal They've said it would not take a stance on OPEC plus is oil production strategy Before the groups meeting next week and again This is in context of the fact that their current strategy for OPEC plus is that they're going to return 400,000 barrels per day more of crude oil on a month-by-month basis But there was been some Rumor mongering on the fact that given what the US have done Well, they might hold off for one month to compensate for that for that news that's come out Yeah, the funny thing here is is that OPEC, which generally is very bad at having a unified approach It's probably the most unified that they've been in a while But such is the fact that then when external market forces start to compete with you and target you Like what the US is spearheading at the moment funny how then that brings them all together again So yeah at the moment nothing really a great deal. That's really market moving for oil I'd say from a technical perspective short-term looking at a 30-minute candle here We're just seeing a bit of a squeeze in price So things will probably be pretty quiet today just given the Thanksgiving holiday But from a technical point of view I'd be keeping an eye on the downside around the 78 dollar handle Which defines the the low end of some of the recent price activity following the rally that we saw kind of this time yesterday After the disappointing signs of the SPR release that came with the US which we talked about yesterday and you know The likes of goldman's drop in the ocean idea That it's just really not enough to meaningfully do anything and then Just descending trend line here, which has been quite well respected going back to the hide at the scene This time yesterday morning, which was around 79 dollar handle So just keeping an eye on that from a technical perspective in terms of short-term price action But it could be quite quiet overall and then yeah on the COVID side of things what's going on Well, there were a further 351 deaths in the last 24 hours through this morning while COVID infection surged to a record just under 76,000 in Germany and a seven-day instance rate per hundred thousand people climbed so a new hire 420 to give you a bit of Perspective against mainland Europe and other nations you can see here I'll see Austria and Netherlands are the standout and and the ones which are subject to the most onerous restrictions at the moment to try and counteract Surging COVID rates what we're looking at here from a data perspective is daily new confirmed COVID-19 cases per million And then Germany here But as you can see after Austrian and Netherlands the Germany is probably the one that's seeing the fastest acceleration on a fairly consistent basis Going through the month of November and of course comes in context of Comparatively to their European peers a lower vaccination take-up rate Which is one of the most worrying things at this moment in time now one of the things here is about politics and obviously Battling the pandemic is definitely going to Dominate the early stages of Germany's new government. So social Democrat Olaf Schultz on Wednesday sealed the coalition agreement with the Greens and free Democrats And he's expected to be sworn into a place Merkel during the week starting December 6th Schultz said Wednesday he will set up a crisis unit in the chancery to coordinate pandemic measures With the 16 states of Germany and also raised the prospect of mandatory vaccinations for people working with vulnerable groups Such as the elderly. I'm not sure why that's not already happening But I'm such as part of the problems that they've had in Germany is a lack of willingness to take up the vaccine In addition to lots of other things that they've had along the way some supply constraints early on And the inability to really make decisive and timely decisions given the fact of their political situation of late Which now at least has been resolved and hopefully they can make some more Fast-paced decisions to counter at this this kind of situation But again, we had things like ifo yesterday ifo, which is the kind of business Sentiment survey one of the key measures that people look at generally in mainland Europe and obviously Germany being a key component of anticipating eurozone overall performance and thus ECB policy and Yeah, that figure I would say most likely or not is going to deteriorate further going forward in time Just given the fact that you know just reading about lots of comments as well from businesses in particularly retail space that you know If Christmas is kind of cancelled and it's going to be economically quite a disaster for them So again fuels that that view that we've just been talking a moment ago about more hawkish US developments Meaning an acceleration potentially in tapering and a more and more near-term rate hikes Against now chiefly because most recently COVID what's going to be a great greater golf between the policy timings of the ECB Which don't have an ability at all to be hawkish at the moment against an ever-increasingly hawkish Fed at the moment and consequently Why that that euro dollar trade was was fairly directional to the downside. All right Wrapping up. What have we got for the day? I mean, it is super quiet I mean, there really is not a great deal going on at all today Given the Thanksgiving holiday and this afternoon is going to really reflect that so from a trading perspective into a day I think don't be looking for too much in a way of of large-scale moves barring anything Shocking the unexpected from a headline perspective And it could well just respect near-term kind of range technically Consolidate in a consolidation phase from data this morning have had some German GDP for Q3 No real surprises there 1.7 percent quarter on quarter against 1.8 year in the year 2.5 percent in line with expectations And then for the rest of the day, there really is not else nothing else of Importance coming out these be minutes perhaps might be interesting But probably fairly close guarded at this point at least in terms of timings about the pep The pandemic emergency purchase program how they're going to wind that down talk about whether or not the eight APP the asset purchase program will get a temporary temporary bump up to smooth out the transition of the exit of the pandemic Purchase program, but perhaps as I say, it's a little bit early for that to come out and given the rapidly evolving COVID situation in Europe Perhaps a minute's a little bit dated in themselves anyway And then speak wise ECB's Christine the guard the president does speak but a legal conference So probably unlikely to say anything specific on policy or the economy But nonetheless, she's speaking at 130 so you're aware and that is it So thanks very much for listening as I said drop me your S&P call for the end of of 2022 Good to get your thoughts Don't forget to like and subscribe to the channel if you're new and you haven't already done so super Appreciative and to have have you in our community and I'll see you guys tomorrow. Thanks very much


Good evening everyone. This is Melissa with thestockswish.com and welcome. Welcome to Netflix Thought I would do an update on this because this little puppy here is getting ready to blow again Funny how this was taking its good all time today and I actually said tomorrow I think for Netflix, but it did get a lift here today. It did make a new hide today It's gonna go straight to 450 and depending on how it does it. It may just break through it Immediately But if this is getting a lift that it needs to hear it in a very strange way though, which is funny because the gap happened here Then this happened here This was a perfect buying opportunity because the gap here was so good and you could have bought the gap even though it didn't really go much of anywhere in the day I knew was a great gap and The stop can't be under the gap because this isn't the first gap Okay, so anyways in the meantime perfect buying opportunity here Mark was falling falling falling. I kept saying buy Netflix buy it buy more buy more and then look what it did here Then it rested rested rested rested rested went ready for the breakout This is really like a breakout play that happened here and it's a beautiful beautiful fat solid green bar of 20 bucks or more now I Thought I was gonna rest today and the day before This is kind of like a rest day for Netflix actually because considering the move the market made today. This really Was this is really like a rest bar for Netflix here It's crazy to say because it's $10, but it didn't make the breakout move until late in the afternoon It was around 1 o'clock and then it came in hard and kept kept going a little bit. Let's see where this is first market for 33 So, you know intraday It's it's it gets tough to buy this now as a day trade. This is a better swing trader for trade This is a good swing and core trade I've been talking about this forever since last year when it first capped and specifically even the gap then at the beginning This year, I do think Netflix is going to 750 this year But you know the proper place to do this is a day trade is really only on the gaps And you could even do it. Well, yeah, I mean you can't this would have really tough to do today Is a day trade it's more like a breakout play at one o'clock Well, I could have done it here with a dollar stop. Let me look at this You could have done Netflix here today with a dollar stop And actually was a five-hour trade because I would have been out here if I had done it I would have never held this through here After that kind of move But you really have to play stuff on the bigger timeframe intraday If you're gonna if you're gonna go after this now unless you're in it for the longer term And you just take the position and you hold it to the number And if you don't need the money right a ways and can hold it to the target Then that's exactly what to do I think it's the best way to play this unless you get a gap a new gap the day of the gap Then you day trade it otherwise just be a Netflix at least until it hits 500 You see how it acts there, but I really think this is going to 750 this year It's definitely definitely definitely should be hit up by 450 to you know tomorrow or at least in the next week What's tomorrow Wednesday Wednesday Thursday Friday? This should hit 450 by the end of the week And we'll see how long it takes to get to 500 then or how it acts. I think it's gonna do that in another gap actually So this is a nice Overnight, okay If you like to do swing trades if you like to do core trades if you can carry something at this price point It really will pay you. I mean I said 750 this will be almost double the price Really from the original got back here this year. I mean that is outstanding That's an outstanding performance and actually Netflix doesn't even need the market look the way that it act in Come, you know the way that it was so strong when the market was coming in And we are in a bullish market of a law even the pool in the market was still we were still bullish But I don't even think Netflix needs the market and that's the kind of thing you really want to stock That's on its own whether long or short if you get them is a hundred percent in its own You know You've got a quality solid investment and you can feel safe like I can sleep at night Because if you are in stuff overnight You want to be in something where you have so much conviction in it and carrying it overnight position Whether it's a $400 price point or $40 price point that you're in the right direction that it's good. That's gonna hold so really really nice and And the market is gonna help lift this but it would do it on its own anyways I mean it really really would so we'll see where Netflix goes from here in the next three days But I think 450 by the end of the week is very realistic Which is only $20 away and that's a sneeze for Netflix. It's a walk in the park So Netflix is doing great and there it is Another fat green bar should happen soon here in Netflix or another gap up or a combination of both Anything's possible in since the gap is only had two fat green days This day here in this day here and it's had a nice two week rally So there's another big green bar coming up soon for Netflix and it could be this week yet, too This is Melissa with the stocks wish calm if you would like more information on the upcoming golden gap course I am doing a class at the end of this month February 22nd and 23rd if you would like to sign up for that class I suggest you pre-register ahead of time for that course and you can email me at Melissa at the stocks wish calm for more information The cost of the course is twenty four ninety nine US dollars And if you are interested in signing up email me at Melissa at the stocks wish calm. Thanks everybody have a great day