Bonjour. I think we can get started. So my name is Ximing, I'm with IBM, but this talk is about, it's not about IBM, it's about suening.com. You can see the names Zhang Xiaobin and Jinlong here. They actually proposed this talk to the summit, but unfortunately they cannot make it today. As for the reasons, I will mention that later. I have been involved with suening.com for quite some time now, and today I will try to present for them. If you have any questions, please contact these authors. This is the agenda, the topics I will touch today. First, a little bit introduction of suening for those of you who have no idea about what suening is. Then suing is OpenStack journey. Most OpenStack startups or other companies adopting OpenStack, their journey is not a long one, but they have learned a lot, and they have some wish list to share with the community. This is an overview of suening.com. This company actually was established more than 20 years ago. It is today the largest failure company in China. It is among the top three Chinese private enterprises. You may want to read this a little bit carefully because it's a Chinese culture. When I am the top one, usually I will say I'm among the top three, so you can get the idea. It's almost the number one. Suening's business is not limited to rotating. Today it has logistics, supply chain, and even real estate investments. The company is growing very, very fast. By the end of 2012, some data need to be refreshed. They already have stores in more than 700 cities in China and abroad, in other countries. The total number of staff is 180,000. That's the big company. They have R&D centers in Beijing, in Shanghai, in Nanjing, and even in Silicon Valley. The brand value and annual revenue is over there. You can read the number. To give you some rough idea of how large the retailing market is, I'm also showing some numbers over there, here. This is only the first half of 2014. The first half of this year. The total market size is $175 billion, and the year-to-year growth is more than 40%. This is a big cake. Why Suening has to do cloud business? This company has been using cloud for quite some years. To be honest, they didn't start with OpenStack. They were using some other cloud software. What they see in cloud is cloud is actually bringing them many opportunities. Needless to say, there are also many challenges as well. They want to adopt cloud technology just like some big guy said. Every company today is a software company. Suening is trying to innovate themselves, to seek opportunities in business model innovation, new collaboration models, and also a lot of other opportunities here. Suening cloud, this is also a brief overview, is not OpenStack. It's using some other cloud software. They have their own private cloud and also open cloud, public cloud. Their private cloud has multiple data centers. Just in Manjin City alone, they have two data centers. Also in Beijing, they have thousands of physical machines and tens of thousands of virtual machines for their private cloud. They have installed a lot of middleware and applications. They have implemented their own automatic deployment, orchestration, and so forth. They also offer public cloud as business. They provide virtual machines, virtual storage, database as service. It seems like this company is evolving to something else. Suening's OpenStack journey is not a long history. They only started using OpenStack since middle last year. I think there's one version. They did their install manually, step by step, hacking the configuration files, all those kind of stuff. Today, this deployment has evolved from a single deployment to a multi-data center deployment. The usage is not limited to R&D activities. They have gradually migrating their existing workloads to OpenStack cloud. Here is some status about their installation. About compute, they have not so bad physical hosts. For storage, they were using a standard multi-backend combined with LVM and Glastro with QoS guarantees. For network, they have isolated the main data and storage traffic. They use OVS bounding to improve availability. They use hardware-based load balancing. There's network. They are also experimenting container. Container is so hard today. Suening is no exception. They want to look into this to see what they can get from container technologies. I think today the topic is, if the topic is about container, this room will be very, very clouded. As for deployment, they have been using cobbler and the puppet. They are trying short and ansible now and anything. For the controller nodes, they have set up three nodes for HA's purpose. For monitoring, they have been using proprietary monitoring tools and some open source tools as well. For optimization, they have resource scheduling for single node or multi-tiered or distributed application configurations. Next, I will talk a little bit about their workloads. What are Suening running on the OpenStack cloud and their previous cloud? I'm calling this a drill because it's pretty complicated, pretty mixed. You can see they have more than 100 applications. Each application looks different. It's a mix of CPU-intensive workloads and IO-intensive workloads. For example, they were developing mobile applications for their mobile endpoints for consumers so that you can buy something using a mobile phone. Those development activities were host on cloud and it means a lot of storage requests. 800 gigabytes or even one terabyte of storage requirement. They also do some search engine compilation and they do sentiment analysis job. Needless to say, they want to monitor what the consumers say about Suening. That's some very valuable information feedback to the company. An interesting point is thumbnail picture, those image generation, they did it online, on the fly, using some open source library. They didn't pay any attention to this but later on they found all those thumbnail picture generation is very, very CPU-intensive. It's not what they expected. For this company, for their internet applications, they have been using different software stacks. They both use open source stacks, Apache, JBoss, MySQL and also some IBM solutions, IHS, WASP, DB2. They are using something else as well. It's a very complicated mixture. The complexity of their workloads is not limited to this. Here I'm showing you a very simple, very representative multi-tier enterprise workload. You have a web front-end serving the HTTP request. You have your business projects deployed into the middle tier, the application server. You have your data stored in the backend, which may be a collateral or something. Anyway, it's a database. In Suening's case, because they have 100, more than 100 applications, these applications came from different development teams, different departments. Sometimes they want the front-end clustered. They want it to be auto-scaled. They want this front-end to be deployed on different halls, the different availability zones across state centers. For the middle tier, they also have this requirement. The middle tier is where the core is executed. It's their business logic. They upgrade their applications every one to four weeks. It's a pretty short release cycle. When you have your VMs deployed, be prepared. You will upgrade it just a few weeks later. It's a pretty short release cycle. For the backend database, sometimes they want this to be active passive configurations. Sometimes they don't. They also have some placement requirements as well to add more complexity to this picture. This connection between tiers is very, very flexible. If you are scaling your front-end or your middle tier or your backend, these different tiers need to discover each other automatically, dynamically. The service discovery and registration is a difficult problem for them. Sometimes they have to hard-code it, but today we hope some tours from OpenStack can help this. We started with heat. That's about the complexity of their workloads. As for the deployment, I have mentioned some complexities, but here are some more. Their applications came from different departments, different teams. Each team has their own unique view, how they will use Apache, how they will use JBoss. Some teams will use Apache as a load banisher or just a reverse proxy, not web server. Some teams will throw Apache away. They think, okay, JBoss is providing HTTP server already. Maybe it's desirable to unify this, but there is a saying, if something didn't break, you don't want to fix it. If their current configuration is already tested, has been run for a long time, we had better not change it at the moment. That's some complexity. Service discovery and registration have mentioned that. That thing is about workload distribution. In traditional enterprise applications, usually you configure a thread pool, a worker pool, or something like that for scaling. But on a virtualization platform, on cloud, that is not the fact now. Instead of forking new processes, you are creating new virtual machines. And it's not just only about creating new virtual machines.  So it's not as lightweight as just forking a new process. So this is a challenge they have realized when they migrate their enterprise workloads onto clouds. It's not just about OpenStack, it's about any cloud. So why they started trying heat? They saw some valuable points from heat. First of all, heat in their eyes is an orchestration tool that says above Nova, Neutron, Cinder, whatever. It's a user-facing tool. And they see the template-based VM provisioning is a great convenience. It reduces the complexities, the workloads for the IT operators or some service staff. So they also see the auto-scaling support from heat, very, very important for them. So just give you an idea about auto-scaling, what it means for Suning in particular. So just guess how long does it take to sell 5 million cans of milk powder here or anywhere? Or 100 containers of milk. So in Suning's case, it's only three days. I'm showing a date there. It's November 11th. You can see the number there, four ones, four singles. How long they are. So when people feel so lonely, they buy milk powder, they drink milk. Maybe that's the reason. But I'm only going to give you some examples. During promotion seasons or even just holidays or weekends, their workload increased dramatically, seven times, 30 times. So auto-scaling is really, really, very important for them. It's a game. It's kind of fun for us, for developers, but for them it's real money. So that's what we learn from Suning. They also hope heat can provide them with a standardized approach, even a process for the application deployment and the orchestration as well. So that's why they adopted the key. So about the deployment, currently we see heat mainly as a deployment tool. It is positioned as an orchestration tool, but there are a lot of things we can work on, we can improve. For example, the post-launch configurations, which is primarily a configuration tool, such as puppy itself, their domain, heat has done some work to bridge these two domains, VM provisioning and instance configuration management. In this domain they have used cobbler and puppet, and fortunately they can bridge these with heat using the software config. But what is very difficult for them is the service discovery and mutual registration. In heat, sometimes you have to express this as dependencies among resources, but heat doesn't allow circles in your template. But sometimes for them they have to do this something on the frontier, then on the middle tier, and then back on the frontier, then back. So these circles are not so easy to be removed. So that's something they are thinking about. Okay, next I'm going to share with you some lessons that Shunning team has learned when they were using heat. Today, heat is more about deployment, as I just mentioned. It's not a full-fledged orchestrator, yet hopefully with conversion work, something like that merged in, heat will be more popular, will be more valuable for our customers. Heat-based deployment only covers part of the story. So the Shunning guys were asking us a simple question. So we hope heat can do everything, but you tell us we still cannot abandon topic, we still have to use Ansible. Why heat? So that's some question we need to think about. It is about the positioning of each tool, each project, but for the end users, what they want? They want an end-to-end toolshade from the basic image to the application fully configured, customized, up and running. So that's a workflow. We have to have some tools to make that process very easy for the users to use. The other thing the team has found out is auto-scaling. I just mentioned auto-scaling is very, very important for Shunning, but they have learned a lot from this. For example, there are defects, there are flaws. The loading update is very important for them, but if you don't specify some properties, it just doesn't work. Auto-scaling, as I understand it, is not thoroughly tested in the community because it's a cross-project integration. To get auto-scaling running, you need heat, synometer, NOVA, and maybe something else, for example, Keystone. So to test this automatically from the community side is a big burden. So we spent about two months on this. We have found some other problems as well, such as if I'm creating an auto-scaling group and scaling it from one instance up to three instances at maximum, sometimes what we saw is the number of instances jumped from one to three directly. Why? Because my second instance was launched very, very slowly. We were installing things on that instance. During this period, we got a second alarm from the synometer. We have no guard there, so the second alarm triggered another scale up. Yes, in heat auto-scaling group, there is a cool down, but that period is not counted into cool down because the second instance is not up yet. So those are some very common cases we found. We need to fix that. I have filed an assignment back to myself. I will fix it. Another problem they have found is the synometer evaluator sometimes works, sometimes just don't. We are still investigating this. For example, at the very beginning, an alarm is in sufficient data status. That means that alarm has not accumulated enough data to make a judgment whether the alarm is triggered or not. Then when the alarm has accumulated sufficient data, it will be changed to OK or alarm state. OK means something you can ignore, but alarm is something you need to pay attention to. So from that moment on, you have accumulated some data to change the alarm state, but in our experiments later on, that alarm may change back to insufficient data again, but that makes no sense. Sometimes something is not running correctly from the synometer sign. So we are still looking into that. So fixing all these bugs is not an easy job. We are still working on that. OK, continue on lessons learned. Previously, when they were talking to us, when the Sunning team themselves were experimenting with auto scaling with heat, they believed maybe their application should be triggered, their scaling should be triggered by network packets transferred, bytes transferred by those metrics, but later on they found, wow, that is not so interesting at all. What is more important is still about CPU utilization. Some things, the workload may eventually translate itself into CPU utilization or memory pressure. So there are some other requirements about how to trigger auto scaling as well. To be honest, the different units, different departments from Sunning, they were fighting each other. They were trying to figure out what is the best equation or the formula to compose a trigger. It's a combination of CPU utilization and memory and something. I don't think there will be a uniform equation there. It will still be an application-specific thing, but there are some requirements there for different workloads. Remember they have more than 100 applications. Rolling update is very important, is of critical importance for their workloads. Even they have to upgrade something, have to patch something, the whole process has to be non-intrusive to their business. Deletion policy. Deletion policy means when you need to scale down or delete some member from a group, that by default policy is delete the oldest one. But in Sunning's case, they would prefer the other way. They would prefer you delete the youngest one. Why? They think the oldest one, the oldest instances may already have cached something, may have already been proved to be stable. Why delete the oldest one? If I'm scaling down, delete the youngest. That's their suggestion. We need some support here. For scaling, they really need the detection, the trigger detection and the scaling operation being done very, very fast, hopefully in seconds. In their experiments, using some complicated middleware, the scaling to create a new instance takes about 20 minutes or so. That's not acceptable for them. For experiments purpose, it's not a big deal, but for them, it's real money. You have to scale up very, very quickly. Okay. Next, I'm going to share with you some wish list I got from our Sunning friends. First is about availability. One problem they have frequently encountered is hot disk error. I don't know if there are some good suggestions from the community, from you, maybe how to handle this. Hot disk today is not so reliable. Each time they encounter this, it means interruption somewhere. This is about the stories. We have high availability. I know there are guys who are against this, but for Sunning, for them, they really treat their workloads as pets. If something is wrong, they want it to be quickly detected and quickly recovered. From our engagement with them, we learned that this doesn't sound like a single-project job from a tech perspective. The failure scenarios may include host failure, stories, network. Everything may become unreliable. Your gas operation system may crash. Your application may be buggy. Everything. Anything can fail. But they are not well-prepared for this. So we need to help them. How to detect those failures and recover them automatically. So for detection, take Nova as an example. Nova has service group today. They are maintaining an internal HSA status of their host. When some host is done, they won't schedule new VMs for those hosts. But this kind of information is not exposed. When a compute host is done, no one else knows. But for Sunning's case, they really want to know this. They want to get a notification there. It's a host failure. Okay. My VMs were running on this. Can I migrate them or evacuate them? So this is discovery. Some of these notifications are already there for the VMs. There are VM life cycle events collected by a synometer. But we need to channel to that synometer to notify heat. Okay. Some VMs are done. Do you care about it? If you don't care, ignore it. If you do care, it's time to do something now. So we believe this is maybe not a single project goal. At least for today, there can be some solutions there built across projects. But eventually, we hope that heat can help do this, considering that there is a huge effort in the community about convergence. If you say, okay, this VM is not going to fail. Okay. When heat detect this, heat will recover it automatically. But that's not today. Eventually, we need this kind of feature support. Auto scaling again. So I've talked about triggers. Sometimes because the auto scaling group is scaling very slowly, considering a lot of post launch configuration work there. They were thinking maybe, okay, tomorrow there will be a campaign. There will be a promotion. Can we launch this huge group automatically at a given point in time? This is more like a ground-based auto scaling that's scaled down in the middle of the night. No one is buying in the middle of the night. They also want some smarter VM placement. For example, having three Apache servers running one physical host. That's not a big deal. If I have all my Apache servers running one host, it's too risky that they won't accept it. So who is going to do this? Is a schedule a hint or something? We are still trying to figure out whether this is solvable. There are also other requirements about scaling about availability zone. There is purely an HA perspective scaling across region. That is about the workload. Sometimes they cannot handle all the workload from a single data center. They have to do this from multiple data centers. So that's a real requirement. So from their experience about using HEAD, they really wish there could be some kind of application profile support from the community. It's not about individual templates and nested templates, a collection of templates. They want this to be configurable. So my knowledge in this area is very limited. Maybe some of you can give us some suggestions. Maybe Solom or Moreno, those projects, are they mature enough to support this use case? I don't know. I'm seeking some suggestions here to help sooning. The provider templates. Early this week, the HEAD core team has presented some advanced use case of HEAD. They have mentioned the provided templates. It's a good thing. It promotes your template reusability. It helps you to do some version control. Sometimes provided templates is not so convenient. For example, it's difficult or impossible to reference resources from another nested template, from this nested template. But they really need this kind of support. It's not an easy task to get the dependency done right. I have mentioned earlier, for example, that the circular dependencies are not permitted in HEAD, but sometimes in real use cases, they need this. This is my last slide. They have found some high-frequent calls to keep engine. They suspect this comes from OS configs, kind of scripts. They're not quite sure yet. If that is the reason, maybe we can make the polling. The script running in your instance is polling HEAD for, okay, is there any new software deployments, any changes to the software deployments? Those frequency can be configured, but once configured, it becomes a constant. What they were proposing is maybe we can have this interval set very short at the first hour or so. When I'm launching things, I'm getting the stack up and running, but later on, it's come back to me every one hour. There could be some new software released. Maybe one day is enough, so that's something desirable. The tools and guidance for them to make this HEAD-based workload deployment standard process is not just only about version control. They need some guidance, maybe some documents would be okay. Preferably, it would be some tools to make the whole deployment a management thing much easier for them. That's all I'm going to share with you today. I'm presenting this for Suning with IBM. Actually, this noon, I'm going to show some VM-HA demo and cross-region prototype at IBM booth. If you have time, stop by. Thank you.


Lieutenant Colonel David J. Nelson, D-A-V-I-D, Middle Initial J-N-E-L-S-O-N. And I'm the assigned commander for 359 Infantry Airborne. So what happened today was we jumped out of two Royal Australian Air Force C-17s. We loaded up in Darwin at the Royal Australian Air Force Base there in Darwin. We had about a two and a half hour flight and then we did an airborne insertion, a joint forceful entry onto Kangaroo Drop Zone here near Charter's Towers, Queensland, Australia. It's part of Exercise Talisman Sabre, which is a joint and multinational exercise, mainly between the United States and the Australians to show our partnership and interoperability. First off, I hope that we gain from this exercise an appreciation for the professionalism of the Australian military. I hope that we gain a greater awareness for how interoperable our forces are and how if called upon we can fight shoulder to shoulder with the Australians anywhere anytime.


Open wedge high tibial osteotomy is a form of surgery designed for certain patients with osteoarthritis, namely those with bowed knees. The goal of open wedge HTO is to realign the lower limb so that the inner joint takes on less force and symptoms of arthritis can be relieved. But things don't always go according to plan. Surgeons often miss their mark during the procedure leading to under or over corrected alignment. How does this offset affect patient outcomes after surgery? To find out, researchers examined the knees of 72 patients who underwent open wedge HTO between 2013 and 2018. The alignment of each knee was classified based on two measures captured three months after surgery, the weight bearing line of the full leg and a special location known as the Fuji Sawa point. The weight bearing line is an imaginary axis that runs from the head of the femur to the ankle. The Fuji Sawa point is a reference point indicating ideal alignment and lies 62.5% along the width of the tibial plateau. Knees with weight bearing lines lying within 5% of the Fuji Sawa point were considered appropriately corrected. Knees with weight bearing lines outside of that zone were classified as either under corrected or over corrected. Results showed that over corrected knees were strongly associated with poor outcomes following surgery. Patients with over corrected knees reported lower scores on the International Knee Documentation Committee questionnaire, Kujala questionnaire, and knee injury and osteoarthritis outcome questionnaire. Patients with under corrected knees, on the other hand, reported scores similar to those of patients with appropriately corrected knees. It should be noted that the follow up period of three months after surgery is relatively short. Beyond this point, it's possible that misalignment could reappear or that osteoarthritis could progress. A longer term study examining a larger pool of patients could provide a clearer picture of how overcorrection affects patient outcomes. For now, the findings suggest that given the differences observed in clinical outcomes, overcorrected alignment should be avoided among patients undergoing open wedge high tibial osteotomy.


The next 7 star terror raid event featuring Cinderace is now live in Pokemon Scarlet and Violet, we're going to cover all the details in today's video, but before we get into it please subscribe to the channel remember you can always unsubscribe later if you would like to. So to start us off we'll take a quick look at all of the details for this brand new terror raid event. As you can see Mighty Cinderace is what the event is coined. The event is running from December the 30th which is as of today recording this video Friday until January the 1st which will be Sunday. If you miss this weekend's event for the Cinderace it will be running again in a couple of weeks time from January the 13th until January the 15th. So you're going to have another opportunity like I say if you do miss this one or if you want to just take part in the next one again to cycle more item drops then you're going to be able to do that. Remember Cinderace is the main star of this event it is going to be 7 star level 100 and it is going to have the mightiest mark with it as well. Remember with the 7 star terror raid events you can only catch one of the 7 star terror raid Pokemon per game save so per your copy of Scarlet or Violet you're only going to be able to catch this Cinderace once in that particular game. It is of course going to have the fighting terror type it will not be anything different only fighting terror type and these are the moves that it will have. It will have high jump kick, pyro ball, acrobatics, iron head and an additional move of bulk up so nothing else other than that. No worries about sucker punch like maybe we suspected there so this might be a bit easier than what we initially thought. The item drops again are going to be very good we're going to get XL and large candies here we're going to get proteins, fighting terror shards you're going to get the TM bulk up. You're going to get an ability patch and then you're going to get additional drops with the chance of more XL candies, large candies, red candies, more proteins and then other high cost items like shards and nuggets. Nature mints, bottle caps and ability capsules as well so a real good array of item drops that you're going to get. Alongside the Cinderace though it's not the only Pokemon that you're going to be able to access in this 7 star terror raid event. You're going to get Gengar in 4 and 5 star raids and Gyarados in 4 and 5 star raids. So the 4 and 5 star regular form Gengar and Gyarados can have any different terror type. You're going to be able to identify them by a pulsing kind of aura around the terror raids showing that they are spotlight terror raid event dens and these will contain either the 4 or the 5 star Gengar or Gyarados. 4 star of course will be level 45, 5 star will be level 75. These Pokemon aren't going to be shiny locked unlike the Cinderace that will be shiny locked so you will not be able to catch Cinderace in this event in particular in its shiny form. Although once you've caught it you're going to be able to breed it and then have the chance of getting a score bunny shiny from an egg. The hidden ability is possible on the Gyarados in both the 4th star and 5 star. Gengar is only going to have that cursed body ability and there is an additional Gengar and Gyarados terror raid event in these spotlight raids where you can get a Gengar that's always going to have a psychic terror type and a Gyarados as well which is always going to have a flying terror type. So these are the two that you're going to be able to get with specific terror types as well as any random terror type as well.  And for the exclusive psychic terror raid event then for Gengar the item drops are going to be pretty similar to what you would get in a 5 star den as well as at Gyarados. For the 5 star terror raid Gengar are going to have access to Shadow Ball, Clear Smog, Sludge Bomb, Night Shade, Licking Confusion or its additional moves which is exactly the same for the specific psychic type terror raid Gengar. And Gyarados 5 star raids are going to have Hydro Pump, Dragon Dance, Aquatill, Hurricane and additional move Rain Dance and it'll be exactly the same on the flying type Gyarados as well. So it's an easy way to say if you want to go after the Gengar and the Gyarados in your games you can look out for the flying terror spotlight raids with the pulsating white borders to them and then for the Gengar it's going to be exactly the same but just the psychic type raid and then your Sinderace is going to be the fighting type so that is all of the details for this brand new event running now running from December the 30th until January the 1st but like I said if you missed this one then you're going to have another chance from January the 13th to the 15th to take part in this. So like all of the other terror raid events you want to come to your poker portal in game and then you're going to want to come down to mystery gifts to update all of your dens and get check poker portal news. This will just connect you to the internet, go through all of the run of the mill things and you'll get this message saying that all of your dens have then been updated, you'll get this update of the date today with three minutes after the update should have dropped so it should be safe and you can just quit out of this menu here. This will disconnect you from the internet of course and this event will stay in your game until you next connect to the internet even though this will be ending on the 1st of January 2023 but if you don't connect to the internet after that date you'll keep this event until you do connect to the internet next. So once you have done this update you'll come to your map and you're going to notice the spotlight terror raids that are accompanying this raid den event which are going to be either four or five star Gyarados or Gengar. These are the two Pokemon that are kind of alongside this seven star terror raid event and you're going to be looking out for the seven star raid den which has the fighting type which is actually right next to where we are so we've not got far to travel to so we can go straight there and check out this event.  You of course if you have got six star terror raids which you're going to have to have unlocked to access this event you will still have your six star terror raid somewhere on your map so you will be able to distinguish easily between which one is the event one and which one is your regular one so if we can find a six star terror raid on a map. And it is down here and you can see it is an electric type one so that means that the other one that we're looking for and we're going over to right now is the event den. And if you've recently just got a copy of Pokemon Scarlet and Violet if you're wondering how to unlock six star and five star terror raids in your game I will link the video up in the top right hand corner now so you can check that out and I'll give you all the details with how you can access these raids so you can get involved with these terror raid seven star events. So here we go.  It is going to be that fighting type and then you are going to want to pick a Pokemon that is going to be suitable for you to use against this particular cinderace. Now we did a guide leading up to this event with Pokemon that I felt were the best options going up against this cinderace. And into this one we are actually going to use our armor Rouge because I do feel like armor Rouge is going to be probably one of the better options to use against it. Let's see what this cinderace is going for we know it's got access to high jump kick pyro ball acrobatics and iron head and that bulk up as well. So be interested to see if it does have any additional moves or if they are just the moves that it does have access to. So straight into it we are going to see it is going to be level 100 as we know and going straight for a bulk up. So a bit like that Charizard that went for the overheat turn one cinderace is now going to go for a bulk up which I would imagine is the standard every time we come into these raids. Well first set up a reflect it's worth just keeping an eye on the reflect how many turns you have left on that. We're probably best going for the acid sprays first just to get that special defense drop so we'll try and get three of those off. And after the reflect up we're taking those acrobatics really really well.  I've got to say that armor Rouge especially this set I don't know if it is the set I feel like it's more armor Rouge though. It's a bit slow setting up and getting damage onto the field. Whereas cinderace is putting a lot of damage onto the field and quite heavy damage especially after getting that bulk up turn one and then it's continually bulking up throughout the battle and making it more difficult to take these attacks. But you can see once you get yourself into a decent position like we are now we're not really in any kind of immediate threat of getting knocked out and we're going to be doing big damage to the cinderace every turn from now on since we have terastalize. We just need to be careful around this cinderace getting yeah there's a critical hit there so that's why that did a bit more damage but we should be able to take the next acrobatics before it's going for an iron head so yeah no worries there. But it's still doing decent damage with those buffs that it's taking to it's stats you know so have to be a little bit careful against it. Like I say it's not as strong as the it's about on par with the Charizard I would say it's nothing to seriously worry about you're going to be able to do this solo no trouble at all and see the shield smash there so you're not going to have any trouble. I think with using the Pokemon that we've kind of went over but I would maybe say armor Rouge it's a good option for sure but there's probably more optimal options and that's something that we will cover later on over the weekend with an update. Probably sometime tomorrow once I've had a time to go through test a few options to see what the best ones are so stay tuned to the channel for that one and we'll have some really optimal options to go up against the seven star cinderace with as soon as we can. Remember if you are catching this cinderace you can only catch one per game save file so once I've caught this I'm not going to be able to catch it again but I am going to be able to come in and do these raids over and over again and collect the rare item drops that we are getting with these raids. And that was one of the big bonuses with the Charizard event obviously we were able to only get one of them which was a little bit of a shame but you could still come in and defeat it and every time you did you got those item drops which meant you could get a lot of money very quickly and a lot of very rare items that you weren't normally able to get. So we've got an ability patch there, lots of candies, we've got the fighting terror shards as well, protein we were right with that so 10 of those, 15 of those, nuggets and yeah quite a similar selection to what we get with the Charizard 7 star raid. So very good item drops and TM there which is TM64 which is bulk up so that's a nice TM drop there and like I say some nice items that are going to be very useful and a raid that you're going to be able to come into and do super easy. Collect these items over and over and over again and if you are doing this for the first time and you come back into your map and try and find that next 7 star raid then you're only going to get one of these per day. So you're going to have to use that day skipping technique to change and bring it back onto your map rather than waiting 24 hours which is just you know you're only going to be able to do three of these over the the whole weekend if you do that. So to do it what you want to do is just go to your home menu, come down to your system settings and then down to system, date and time. Make sure your synchronized clock for the internet is off, come down to your date and time, just come across to the minute hand and then just take it back one minute. So we were on 17, we're going to 16, that's all we need to do then come back into your game and just like magic all your dens will change around and you'll get an array. So there's the 6 star Terrarium Den that we've got there and yeah just above it is the 7 star Cinderace Den. So we can go to that one and just do it again and start collecting a lot of these higher reward items. So that about does it and covers everything for this brand new 7 star Terrarium Cinderace event that is now live in Pokemon Scarlet and Violet. I hope you have a lot of fun taking part in this event and use some of the strategies that we did cover in our preparation video for this event then. I don't think it's going to be as hard as what I maybe suspected it was going to be but let me know your best methods and Pokemon of choice that you're going in and having the best success in this den with. Like I said earlier in the video, I will be covering the best options going into this event then and we'll probably cover that either tomorrow or early Saturday with the best and most optimal Pokemon to go up against this road with. After I've had a chance to test a few additional ideas to make sure that you've got the best possible option for farming these really great item drops that you're going to get alongside this Terrarium event. I hope you found the video useful. Thank you so much for tuning in. If you have, drop a like if you're new to the channel. Do subscribe to stay up to date with all of our latest Pokemon Scarlet and Violet content. And I will see you all in another video very soon. So until then friends, take care of yourselves and bye bye.


Hey, this is Brett and this 2022 Ford F350 Crew Cab Short Box Single Rewheel XL STX is stock number 12593Z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. This 2022 Ford F350 has the 6.7 liter power stroke diesel engine. This truck has been fully-safetyed and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off and this truck is 100% ready to go. We're going to go inside, underneath, start it up, take a look under the hood in this video. Carbonized gray metallic is the color and we shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone, or television I highly recommend turning them on right now because it is your best way to check out the quality, condition, and options of the truck before seeing it in person. And if you like the video and how we do things here at Summit Auto in the upper right-hand part of the screen is a subscribe button to our YouTube channel. Click that and then click the bell notifications. You'll get updates on the videos we do each and every day. This one comes with the 18-inch painted alloy rims and it has Goodyear Wrangler all-terrain adventure tires. These are LT275-70R18s. They have just about all the tread left on them. Frame and underbody is exceptionally clean as you'd expect on a truck with only 2,000 some miles on it. Front fender is in excellent condition, headlight lenses are nice and clear, front bumper and lower valance are absolutely perfect. You get the chrome trimmed grille and the hood is in excellent shape as well. This one does have the cab lights up top and the passenger side front fender is in excellent condition as well. No scuffs or scrapes on the passenger side rim. Carbonized gray metallic, it's got a lot of metal flake to it. It's just a little bit lighter than the magnetic color that they had before this one. As you go down this side of the truck, take note of how clean the body is, how reflective and mirror-like that paint is. You take these HD videos so if you are far away or even if you're close by, just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here so that when you do get here, there's absolutely no surprises. You can make a smart and informed buying decision from wherever you're at. If this video helps you make that buying decision, let your salesman know that you saw the video, that it was helpful, and that Brett sent you. Back rims in excellent shape, back tires have just as much tread as the front tires and the frame and underbody is in excellent condition as well. Has all the remaining factory exhaust, other than a little bit of dust, absolutely perfect underneath, and lower rockers and cab corners are in excellent shape as well. Very nice factory chrome step bars, FX4 off-road suspension package gives you all the skid plates. Going around to the back of the vehicle, rear bumper is in great shape, full towing package which includes a receiver hitch four pin and seven pin wiring. Tailgate is in excellent condition as well, does have a backup camera, and a rough country roll up tonneau cover. Comes with a rough country bed mat, and this one also has LED bed lighting. They got a button back here to turn those on and off, and very nice and clean.  Down the rest of the side of the truck, the doors look really good, didn't see any dents, didn't see any dings, does have the telescopic tow mirrors. They are heated, have built in directional signals, they telescope out like so, and fold in like that. Inside the XL package gives you the gray cloth interior, 40-20-40 split bench seating in the front, no rips or tears on the seats, everything is like new. Weather tech floor mats, auto headlamps, tilt, telescopic steering wheel, power windows, power locks, and power mirrors. We'll hop inside, check out the miles, radio, and everything that this truck has to offer on the interior. You get the built forward tough animation there, and we'll dim it down so you can see the miles better. 2,364 miles on this truck, you also get a digital speedometer and compass display, instrument cluster is very nice and clean, cruise controls and information center controls on the left, Bluetooth and audio controls on the right. This one's going to have the 10-speed automatic transmission with the optional tap shift, comes with the sync 8-inch radio, AM, FM radio capabilities, as well as Bluetooth, and then this one has all your different apps, Ford Pass Connect, you can do Android Auto, Apple CarPlay on here as well. This is also where your backup camera shows up, truck's got to be on for that to work though.   Six upfitter switches, map lights, we'll take a quick look at the back seats and then we'll start it up and take a look under the hood. Back seats are just as clean as the front seats, no rips or tears back here, it does have the latch child safety system for any child car seats you may have, fixed glass rear window with the built-in rear defrost, weather tech floor mat back here as well, carpeting like new, you do get side current and airbags and child safety locks on the back doors and everything is very nice and clean. We'll start it up, take a look under the hood, starts right up, no check engine lights or anything like that. I would personally like to thank you for checking out the video today and hopefully from this HD video you'll been able to verify the quality and condition of this truck all the way around inside and out. This thing is like new all the way around. Under the hood we have the 6.7 liter power stroke diesel engine. Engine bay is very clean once very smooth, once again this truck has been fully safety and inspected by our service shop has a fresh oil and filter change, all the fluids have been checked and topped off and this truck is 100% ready to go. We need to go to its new home, there's your emissions sticker and I would highly recommend this truck from a quality and condition standpoint, you can see a single ding on it and to see more pictures of this truck or one of our other 450 new and used cars trucks, SCVs, minivans, Wranglers, halftones, three quarter tons, one tons, you name it we got to go to that website right there www.SummitAuto.com full pictures and descriptions of every single vehicle from two locations all at Summit Auto.com and if you'd like to check out more HD videos you can go to youtube.com slash Summit Auto. Remember to like, subscribe and share on this video and all the videos that you see there, click the bell notifications you'll get updates on the videos we do each and every day here at Summit Automotive. In fact in a second you'll see links to subscribe to our YouTube channel on the upper left, links to more 350 videos like this one on the upper right, links to this vehicle on our website on the lower left and links to one of our latest YouTube videos on the lower right, click those check us out, we're super excited to help you with this Ultra Cream 2022 Ford F-250 Group Cab Short Box STX XL in carbonized grey metallic with a power stroke diesel. Thanks again for checking out the video remember to like, subscribe and share.