Everyone Sam here with late and sports cards. We are doing a 2021-22 a panini Choi prism choice basketball 10 box random team style tiered random team style Break, I know I just did that completely out of order Anyway, let's go over here's here's a look at your random teams that you got your tiered random teams at least and Yeah, I'm gonna go ahead and get started guys I know we literally have to ban our own mod. It's insane. Who does that? What kind of company bans their own mods?  Good luck here Put some fire out of this and I love prism choice prism choice. It's so nasty All right, pull a nebula. That's what I want to see. Oh tiger stripe, baby TJ Warren Maryland's Noel. We've got Jaden McDaniels. Oh my god. We've got Eric Gordon We've got bones Highland there you go Denver He's got the nuggets Nam cue. Congrats, buddy We've got auto Ben Macklemore going to the leaker or the trailblazers. That's a trailblazers auto Is it? Oh, yeah, let me adjust this really quick Better there that's probably a little better to make sure it doesn't obstruct me We've got Torian Prince on the blue scope to 39 and we've got Kings. Come on be a rookie That's a rookie Davion Mitchell on the tiger stripe King Kratz Sacramento that is Harper B There you go. Harper. That's nasty We'll get that in a mag for you man And we've got that's Torian Prince 30 out of 39 for the Timberwolves. Sorry tiktok trying to get this is Well centered as possible here Thanks GT I know that that ripping fire guy on tiktok. He's always in here causing trouble appreciate that Always in here causing trouble now. This is a this is a group Oh Another tiger stripe Jimmy Butler and draws on Petrovich We've got Malik Monk Evan for me and Josh Christopher nice You've got auto Carlos boozer going to the cabs. There you go Cleveland Ryan B I'm the nicest card opener ever. Thank you. Javanta Try to be No, that's just these been facts Wow Chris D'Warte 34 out of 39 go into Franky G in the Pacers. There you go, Franky Franky Franky Let's go dude, and then we've got tiger stripe going to the jazz. That's Royce O'Neill That's Eric R tier 2 hit on the rules Royce O'Neill. Congrats, man These are like 500 boxes. I want to say $500 a box or something 600 maybe Alright now we need to two tiger stripes do now we need a nebula. I mean, I don't know if that's asking too much links in the bio Yeah, Link is in the bio as well. I'm just gonna try to readjust this again as best as possible We took it off. So it's like kind of difficult I Okay, I'll switch it up like wraps around. Yeah, I think you're right about that. Oh, I know What are you saying? Oh, I know what I know. Oh, yeah, I'd say Murray Gordon Hayward got Anthony Davis go into the Lakers That's Ben Simmons and David Robinson Got auto Evan Mobley Let's go with the cabs That's huge, baby. Let's go Yes, it is hobby Roop We've got nice Sharif Cooper 27 out of 39. That's going to the Hawks and then Doug McDermott that is 22 out of 88 go in to the Spurs. Yeah, that's a good point. Honestly, Tony. That is a color match. Basically that is Closest you'll get at least you could throw the door thing in the recap as well If you would not mind if you wouldn't be bourbon by that request Hey Blake in the cut now, it's up Chuck Blake everybody play We got one of those new scopes Paul George Hakeem on your silver boy on Bogdanovitch. There's a job Nice job Wayne ZZ there you go Mavs. We've got Miles McBride going to the Knicks on the rate are the Rookie scope auto. We've got nice Jew holiday 15 out of 15 on the bookend for the bucks on the red blue purple and Kristops for zingas 24 out of 88 nice unicorn there for you Max I'm only halfway through dude Hold on tic-tac So I can get with the Are you sure it goes on this side? Everybody's twisted it all up now. I know now. It's just it's messed up here Forest what side does the tic-tac camera go on the left side or the right side? Because there's a Brandon Boston jr. Silver Julius Randall Ray John rondo That is called in Johnson and Zire Williams nice one there gris. We got a green scope coming up to you guys. We've got Herbert Jones That is going to the Pelicans Nice one there New Orleans, and we've got green scope Nicholas Batum There you go clippers That's seven out of eight and DeMarco Rose in for the bowls three out of 88 Congrats bowls Tony generally it's just on whatever the case prices That's more or less like case price case price market value all that kind of stuff There's a there's a lot of factors that go into it, too Then you got to calculate shipping overhead storage space You know cost of paying people so there's a lot that goes into it. I'm no nebulous at face. There's an AI silver Hey, let's go Jeremy. Good luck Jeremy. Good luck, buddy. God Harrison Barnes There's another job nice one there in Memphis and a Hakeem very solid. We've got I don't just soon move Go into the bulls on the color match Congrats on that Chicago Alexandros there you go, buddy We've got Malik Monk on the red go into the Lakers 33 out of 88 and how many do the yellow 26 out of 39 going to the pistons Just name the bulls starting point card. Let's go dude Let's pull some more fire here guys Good luck For us that he goes left Yeah Yeah, it's on the left front silver All the depot that is James Harden and that's that's a Goron tragic heat That's David Johnson rookie for the Raptors. We've got auto bones Highland there you go Denver Namkew doing really well on that spot with the bones Definitely a Peyton Pritchard Nebula in these last four Cut Angie Wiggins red 61 out of 88 Warriors and Bogdan Bogdanovich 12 out of 15 that bones is a Bones is a menace on the court. He's a good player man. It's gonna be good in Denver for sure All right Empty thank you guys again for selling out some both the optic PYT's after this as well No nebulous that face Marvin Bagley draws on Petrovich got Gordon Hayward on the exclusive That is also Christian Wood and also Vince Carter nice been sanity. That's sick. We've got auto is Trey man very nice Go into the thunder take that for sure nice Trey man auto We've got Daniel Gafford That's 85 out of 88 and Jason Preston 43 out of 88 Kirk Heinrich Nebula. That'd be kind of sick Look at this right side views as Forrest Forrest, I am like contorting my body trying to break right now Like my arm is like gonna hurt after this I got I think I got to put it preference wise back on the left But I think I just got to mess with it a little bit. Yeah We've got Jada McDaniels and Eric Gordon on your silvers that is Josh Hart Steppen Curry there you go.  You did it for us Gary Peyton Super sonics. You've got chris thwart. Hey, wow go into the Pacers Frankie killing it with the pacer spot now. Congrats, buddy. That's awesome We've got McCall Bridges 36 out of 39 for the Sons and reds him hardaway jr. Mabs 15 out of 88. I hope so Greg. I would love a big Jalen Green. That'd be so far Did two Forrest Nebula last box Question mark. No nebula. Reggie Bullock. Reggie Lewis Reggie is there We've got Jay Crowder Sons Moses Brown Mavericks and Jalen Johnson Hawks We've got last auto going to the Kings Davion Mitchell. There you go Harper Doing very well with that Kings tier two spot Grats on that buddy You're 10 feet away Forrest You got Tim Duncan 19 out of 88. There you go. Grats on that one Spurs And then last card of the break. We've got Daniel Gafford 11 out of 39 Going to the uh wizards. Do a quick recap guys Wouldn't be creepy Got Davion Mitchell Kings Chris Duarte Pacers Trayman Thunder Bones Highland Nuggets Io Dasumu Bulls Herbert Jones Pelicans Miles McBride Knicks Carlos Boozer Cabs Ben Macklemore Blazers Chris Duarte, uh, that is Pacers 34 out of 39. We had Tiger Stripe Royce O'Neill Rolls Royce We had Evan Mobley on the uh prism Red Scope base not numbered auto And we had Tiger Stripe rookie Davion Mitchell going to the Kings. There you go Harper. Congrats, buddy That'll do it for the break guys. Thanks again for the fill next up. We've got some optic PYTs


G'day. How are you going? Welcome to Bootlossophy and if you're new here, my name is Tech. I live and work in widget country in Western Australia and I acknowledge the traditional custodians of this land. Today, something different. I'm going to look at the four main types of construction methods in bootmaking. So the first style of boot construction is called Goodyear Welter. In a Goodyear Welter boot, there is a leather, a strip of leather that goes around the edge of the boot. It's a thin strip of leather that goes right around the edges. The uppers of the boot are flanged inwards and then the inside of the uppers is stitched to the inside edge of the welt and the outside edge of the welt, as you can see here, is stitched through into the midsole and the outsole. Sometimes it's not stitched to the outsole, just to the midsole and then you glue a piece of rubber on top. It doesn't necessarily make it weaker. The idea behind the Goodyear Welting is that it's a more water-resistant type of construction because one stitch is inside the boot into the welt, which doesn't affect the outside at all. So water can't get in and this outside stitch doesn't go anywhere near inside. So again, water doesn't go in. There are different types of Goodyear Welting. This is called a flat welt because, as you can see, it's just a normal welt. It's just perfectly flat. It goes all the way around 360 degrees around the boot. Another different type of Goodyear Welt is a split-reverse Goodyear Welt. And in these Parker's boots, you can see the difference. There's a little lip that comes up into the boot there, into the uppers of the boot. And what happens with these? Similar construction. You see the outsole, the midsole, and the welt. But this time, the welt's inside edge has been split. So it's split and flanged up and then pushed against the uppers. The stitching still goes on the inside between the uppers and the welt and on the outside through the welt, through the midsole and into the outsole. What does this do? This creates water resistance because it adds an extra layer of protection to stop water going in between the welt and the uppers. A third way, and it's often confused with this, a third way of Goodyear Welting is using what's called a storm welt. And this is the Taylor Stitch Ranch Boot. You can see in the storm welt, it's a similar flanged thing up here. But you can see this is actually finished, the edge of this flange. If you look at the parkhurst, it's a bit stained, of course, but it's actually raw, it's the edge of the leather. And in the case of the storm welt, instead of the welt being split and then pushed up, it actually has a ridge that's carved into the welt. Right in the middle of the welt, there's a ridge carved, so it's sort of, if you pretend my fingers, it's ridge carved and then the uppers can be pushed against it. And the way you can tell is that the edge is finished. There's no raw fibers coming out of it. That's Goodyear Welting. The second form of construction is called a stitch down construction. Now, it's exactly what it sounds like, even though it looks the same. This is a Bordon Tucano Boot. Stitch down construction is where the uppers are flanged out instead of in. And they are sewn onto a midsole, as you can see. That strip there is actually the upper's leather, toe cap leather, and then the actual vamp leather has been splayed out and stitched to the midsole and then the outsole through which it's all stitched. So that stitch down construction, in this case, 270 degree stitch down. It can be 360, but from what I can see, most of it appears to be only at the 270 degree, three quarters of the way around, and the inside is tucked in and stitched on the inside. Now, stitch down construction is often confused with welt scorn or few shoe constructions from the Dutch. This is an Indonesian boot and it's a welt scorn construction. And most people would say that welt scorn is the same as stitch down. But in fact, what I've found, if you dig deep enough, is that welt scorn is stitched into a welt. So there's an outsole, a midsole, a very thin welt section, and then the uppers are flanged out and stitched onto the welt, again, 270 degrees. And you can see in this case, there is definitely a welt in there, very thin. So the idea being that this increases water resistance, because not only like in the bourdon, the water just drips off. In this case, it drips off and it's protected. So the stitch down welt scorn are cousins of each other, where the uppers are flared and then stitched down. The third method of construction is called the Blake Stitch, or Blake Rapid Stitch method of construction. Now, Blake stitching is usually found in dress shoes and dress boots, because it makes for a very flexible, light footwear, because there's no welt in between. Now, a Blake Stitch is basically where the uppers are turned in and then the inside of the uppers is stitched directly into the midsole or to the outsole. If you look at your dress shoes, they're almost certainly Blake stitched. And the problem with that is water resistance, because in theory, what happens is, particularly the stitching showing on the outsole, that stitching goes directly into the inside of the shoe or the boot. And so water could seep in there. Now, Blake Rapid Stitching, on the other hand, is similar. But what happens is, the inside of the boot is stitched to a welt and then the welt is stitched to a midsole or outsole. In this case, this little bit of stitching here is just extra stitching into the welt. Normally, Blake stitching, you don't get that. And the reason for Blake stitching is that you get a very sleek, slim profile without any ridging here, which makes for a great dress boot. This is the Helm Johnson, which kind of plays around with welting and Blake Rapid stitching with a little bit of a welt. And I'm not entirely sure that this isn't anyway a faux stitch and a faux welt. So that is Blake stitching. The fourth type of construction is simply Simac construction. These are Echo Chukka boots. They are not technically cement construction, but I'll pretend they are. Ignore these stitches. They pretend they don't actually do anything. They're cosmetic. And cement construction is exactly what it sounds like. The uppers of the boot are turned in. The insole is put in. And then the outsole is simply glued to the boot. So what happens is, in terms of water resistance, it's not as water resistant and certainly in longevity. If you happen to pull off by accident, the outsole, all you can do is glue it back. You can't change the outsole, restitch it or whatever, unless you get a really good cobbler and potentially you lose a bit of sizing because you'd have to use some of the uppers to to restitch it through. So highly popular in cheap, flexible shoes and much lighter in construction because there's no thick leather, welting, midsole, it's just glued on. Now I said this was technically not cement construction because these are thermally attached. They're actually lasted, put into a mold and then it's injected molten into onto the boot. But it's still connected by technically melted stuff or glue. Probably the most famous example of this, I think, is the Blundstone, which is a thermally injected sole. The uppers are put into a mold. The sole TPU is thermally injected. And once again, waterproof in this case because of the thermally injected outsole. But once you wear this, that's it. That's the end of that. So that's it. I hope you enjoyed learning about the four main construction methods in making boots. If you did, don't forget to click on the like button below. I'll probably refer to this video in future when I'm reviewing boots so that I don't have to keep repeating myself when I'm talking about construction. And I have some other great boot and other reviews coming right up. One thing I'm planning is a video on my five best business casual boots. And I've got a review of the Thursday made in USA Vanguard boot coming up. If you don't want to miss those videos, click on subscribe. Until then, guys, take care and see you soon.


Okay, it's time to start our presentation. Thank you for choosing our presentation as your first breakout session in Tokyo Summit. This presentation is a user story of NTT Resonant. I'm glad to get a Super User Award. And thank you for all of the community enabling our services. And it's great honor to be a part of OpenStack community. And we will share you what we learned to build web infrastructure with OpenStack as much as possible in the next 40 minutes. We are working for NTT Group and have these backgrounds. My name is Toshikazu Ichikawa, working for NTT. And his name is Tomoya Hashimoto, working for NTT Resonant. And his name is Kazuhiro Toriyama, also working for NTT Resonant. In this presentation, we cover these five topics. After introducing NTT Resonant business, we talk about our infrastructure design, that is how we apply OpenStack to our infrastructure. And we talk about not only the infrastructure, but also the framework we built on top of OpenStack to support our services. Especially, we explain how we set up a VM by using Puppet in connection with OpenStack. After that, we also talk about our operation and monitoring both of OpenStack and the VMs. At the end, we share our current issue and future plan. Let's start from NTT Resonant business. This slide shows what is NTT Group and the position of NTT Resonant in the group. NTT Group is one of the largest information and communication technology company. Our global operation generate a total revenue of $112 billion and we are 240,000 skilled professionals. We are the largest brand in data hosting and global IP backbone. NTT Resonant is 100% owned subsidiary of NTT Group. Its parents are NTT Communications providing long distance and international communication business and NTT.com providing mobile communication business. NTT Resonant collaborate with NTT R&D to build its platform, develop new technology and provide solution to customer. This is the business area of NTT Resonant. NTT Resonant is responsible to provide internet services of NTT Group we provide a wide range of services to individual. We provide the internet site portal GU, the e-commerce site for communication devices, NTT XStore and smartphone application and so on. Moreover, based on the technology we foster in B2C services, we also provide platform type services and customer centric services for enterprise business. For example, we provide cloud-based testing solution for mobile application development, disaster prevention response solution and healthcare solution. If you are a smartphone application developer, please check our remote test toolkit. You can use physical smartphone in our data center for your development. We also provide and operate many services of customers even though we are not in the position to disclose the name of services here. But for example, we operate some services of Japan's largest mobile network operator, DOCOMO. We operate search services, content services and mobile applications for them. NTT Resonant's core business is to provide a web portal site GU. GU provide more than 60 services including web search, blogging, news and Q&A site. Even though I don't explain the detail, I believe this image give you an idea of GU's variety. GU was launched in 1997. March of this year was the 18th anniversary of GU. And what is the scale of GU? It generates, it serves to 117 million unique user per month and it generates 1 billion page views per month and it's growing day by day. GU is the third largest web portal in Japan. I think if you are coming from foreign country, GU is famous and GU and GU are similar name, but it's different company and actually GU is about one year older than GU. And now GU is operating on top of OpenStack. That's the very overview of NTT Resonant business. Now let's move on the first main topic about infrastructure design. Let me talk how we meet OpenStack. We started our OpenStack development project in March 2014. I will explain what was required to us, what we have to achieve at the time. It is already decided what we stopped using existing data center and migrate our system to another data center because of certain business reason. The existing contract term was fixed. So we had to finish to migrate our system to another data center by the end date. Secondly, we need to accelerate our business speed as fast as public cloud. At that time, we started, we already used the virtualization technology of KVM at large scale, but we manually created VMs and managed them by operators. Manual operation has a speed limit and it was a problem that we couldn't create a lot of VMs within short time frame. We had to resolve these problems. Suddenly, we needed to provide a common and effective method to deploy not only a VM itself, but also middleware and configuration inside the VM. If we provide only the way to create a VM and to manage VMs, then it's not different from subscribing to our public cloud service. What our application engineer wants this framework to cover our workflow to provide our web services. It's not only to create a VM, it should include more such as installation and configuration of middleware, as well as system monitoring of 24 by seven. I will explain how we addressed and achieved these from now. This figure shows our organization and team structure. NTT resident platform team is responsible to provide the infrastructure to their service teams. The team has about 10 members versus more than 300 members of service team demanded to prepare resources. It's tough work to respond them quickly and efficiently. The platform team worked with NTT R&D to design this project since NTT R&D had a knowledge of OpenStack. We jointly designed and test OpenStack environment for NTT resident platform. When we find some issues of OpenStack, NTT R&D works to fix it in the OpenStack community. We follow this way to keep the consistency with the community as such as possible. This is our timeline, how we deploy the OpenStack and manage or our services on it. Our project started in March 2014. Our result, we thought our internal process and the procurement time from hardware vendor, we had OpenStack would be able to start working on October 2014 at the nearest. It's four months after that, we had to migrate our service from existing DC onto the new OpenStack infrastructure. We could achieve this timeline. So today, we are here and we can share our story. This is the scale of our OpenStack infrastructure. We introduced OpenStack as private cloud infrastructure at our main data center. It has been working in production since October 2014. It's working in stable more than one year. As of now, OpenStack support more than 80 services and one billion page view per month. It consists of 400 hypervisor, 4800 physical cores. On top of it, more than 1800 virtual servers are running. As you can see in the graph at the bottom right, the number of VMs keep increasing day by day. To support this scale, we use the Novasel to accommodate a lot of server to singling endpoint. This is a component which we choose. We used iSouth release as it was the latest release when the project started. Since the project time and the resource were limited, we try to keep our infrastructure as much as possible because OpenStack is well designed as sets of component. It give us the flexibility to begin with a small set of function and expand later if needed. OpenStack community is very active and provide us a lot of component and the choices under the big tent. So I believe it's important to figure out some minimum set to satisfy your requirement as your baseline. Choosing small set also contribute to reduce the complexity of day by day operation. We chose six component to build our infrastructure. It includes a Swift, Noble, Grants, Horizon, Keystone, and Neutral. We didn't use Cinder since we have ever built our services with commodity server without using shared storage. So we just follow the same way. This is the way how we deploy OpenStack. We used OpenStack packages distributed by RDO community. The version of OpenStack was as said, IceHouse and we installed CentOS 6 as hostOS for servers. The reason we chose this distribution is that our engineer were familiar with CentOS and Puppet. Therefore, we use Puppet to automate the installation, the infrastructure calls. RDO community already had a set of Puppet manifest to do that, we refer them so we could make it easily. Automation is important to enable us to set up a lot of server quickly. This is how we design the networking. Networking is a fun part of OpenStack design. There are a lot of features and the variety you can deploy. In this project, our initial step focused on the management of VM rather than networking. So we selected to begin with a simple networking architecture. That is using a networking provider network implementation. It only handle ray arts connectivity for VM. So we needed to configure physical network appliance such as a router and a load balancer, manually outside OpenStack as we did before deploying OpenStack. And administrator manage the configuration of network devices for tenant. Any tenant is not able to manage their virtual network. That's the current status. The community networking guide has a good reference that is similar to our implementation. If you need more detail, I recommend to check the guide shown here. This is our system architecture and the HA strategy. The system consists of six type of nodes. All node except computer node has high availability mechanism. To make them highly available, we use RapidMQ, MariaDB, Gallaudet Cluster, Pacemaker, and HA Proxy. With deploying at least two nodes per node type, these are fully redundant and the total rate to single node failure. However, computer node doesn't have a HA mechanism. The system doesn't provide high availability for VM. There's a concept of design. So it is the responsibility for an OpenStack user and application to take care of the higher availability of the services. I talk what we contributed to the community related to this deployment. When we tested OpenStack, we found some bugs. So we fixed them and contributed those to community up story. One bug was critical for us. Sherp, one of Nova function, didn't work with Nova cell deployment at the time. We use Sherp and Un-Sherp as a part of workflow. Our user or administrator moves VMs from one computer node to another with Sherp and Un-Sherp to have a maintenance over servers. So it was important. Sometimes when you use a new feature at a minor use case, you may hit a bug or find a problem. I want to say that it is important to share issues and to practice each other in the community. It may help you find a solution more efficiently than struggling alone. And I talk about which part we customize OpenStack to adjust our environment. We didn't want to modify the code because we know its costs to maintain. However, we decided to modify Horizon. The reason we modified Horizon is to enforce our operation rules in the environment. For example, it includes VM naming restrictions assumed by our other tools. As shown in the figure, our Horizon pop up a warning if the name of VM doesn't match our rules. Because we assume our users only use through Horizon rather than API, we didn't have to modify other components except bug fix bug ports. I believe each team has its own operation rules or workflow or requirements for other system integration. To enforce or achieve it, you may need some development. That's how we built OpenStack infrastructure. At next, we talk about the framework we built on top of OpenStack for our services. From now, I'd like to explain the way how we set up our VM on top of OpenStack. As we said before, we had to complete within four months from VM creation to service migration after OpenStack started in production. If we simply built OpenStack and asked engineers or service side to set up OS under middleware, it was unlikely that migration completes within four months. We had about 1,300 VMs. We needed to migrate. We needed to automate the steps as such as possible. It was fortunate for us that we had been working to implement the calls as puppet manifest. Since before this project, we had the puppet manifest at all door existing data center. So we think it will be possible to achieve the timeline if these puppet manifest works well in connection with OpenStack. We build a framework to apply puppet manifest to a VM on top of OpenStack quickly and easily. I'd like to explain how we set up our VM with puppet. We deploy an individual puppet master per tenant. The puppet master executes all VM setups in your tenant. VM setup includes a Linux account to creation and installation of software such as Apache and MySQL and the distribution of configuration file. And the minister of tenant makes and manifest for VM in the tenant. Even though we deploy a puppet master per tenant, we create a single repository of manifest and each puppet master refers to the repository. After OpenStack user creates a VM by using horizon, the user has to apply a puppet manifest to the VM. We created synchronization tool to make it happen quickly and easily. What requires to achieve it other than OpenStack and puppet? We have to add a record of the VM to DNS and LDAP and change our puppet manifest. Puppet users are host name as a key to apply a manifest. So the VM's host name needs to be resolved by DNS right after the VM creation. We use LDAP to manage the group of hosts when we have 10 web servers for some services. We went to handle them as a group with puppet. We have to manage VMs with LDAP to do that. When we add the group of hosts, we have to add the entry of the host group to puppet manifest. We implement the synchronization tool to manage the entries of DNS and LDAP by using OpenStack API when your VM was created. Let's see how it works. Our VM is created a tenant. The manage file, image file is a grant has a puppet agent to install it. It is able to connect to our puppet master. Our synchronization tool is pouring NoVar API every five minutes and it detects a new VM. That tool registers a record of DNS and LDAP. That tool also modifies a puppet manifest for a new VM and commit repository. OpenStack user updates a puppet manifest from the repository and is able to apply the puppet manifest to the VM. We manually did these steps before we deployed OpenStack. But after deploying OpenStack, we automated these steps by using OpenStack API. We addressed and resolved the issues with the mechanism I have explained. We were able to shorten the time to deploy our services drastically. We deployed 1,000 VMs within one month right after OpenStack started in production October 2014. It was impossible if we use minor operation as we used to do. We needed to five business days to prepare a new VM before OpenStack introduced. Today, it is possible to deploy a new VM and start the services within 30 minutes. We could remove the task of two operators by reducing minor operation. We got the benefits by this integration of service deployment with OpenStack. When we start new services, our new service engineer is able to prepare the system by following this new mechanism. When an engineer assists other projects or hand over their tasks to do another project, it is done efficiently with common framework. Okay, I'll show you our monitoring environment briefly. So first of all, this is abstract. We have two monitoring environments, two monitoring systems. One is for cloud infrastructure. So this side monitors network, physical servers, and OpenStack itself. And second one is for web services. So we as an infrastructure member of Entity Resonant, so we are in charge of providing standard service monitoring methods inside our company, even on the OpenStack. So I'll discuss them later. And we utilize Xerbix and RedMind for monitoring. One of the features is semi-autoboom monitoring. So our Xerbix detects booms automatically and monitors them. And second one is auto-issuing ticket system for RedMind. Once our Xerbix detects an alert, Xerbix automatically create new ticket. Also there is operation center for us. Operators watch Xerbix 24-7, and they try first response to simple occasion, to simple program. But in case of serious situation, telephone call wake us up even in midnight. So if our OpenStack had any trouble, any problem, they would call to us, info team members, and if any web services has had problem, they would call to web service team members. Going to our OpenStack monitoring. So this is simple stability order, we think. These are not all of our rule, but the basis for us. API monitoring, it means if any API doesn't respond, Xerbix will send the highest severe alert to us. So it's quite serious problem, as you know. And second one is process failure detection. As any process died, it should be repaired ASAP as soon as possible, to keep redundancy. And third one is performance monitoring. It depends on middleware or software. So for example, my scale connection number and so on. And the final one is most messaging log monitoring. So at the beginning of using OpenStack, we decided to use, we decided to treat any log message above error level as problem. So we don't have any knowledge about OpenStack logs. The lack of knowledge reached out. So we've been trying filtering, through using problem-free log day by day, even today. Now I'll talk for future operators from the aspect of operation. If you are a developer of OpenStack, you've already know about it. Well, so you might sleep in this slide. Okay, what's this? Approximately 220 lines and 120,000 characters. You know that this is log message from OpenStack. When I tried to just launch just one virtual machine. I feel smell of madness from here. So without debug logs, it means only 24 lines in here. So it's peaceful, I think. But finally we decided to our OpenStack. Finally, we decided to set OpenStack with debug logs level. So, explain the reason in this slide. Okay, this is a very simple example when the launching new instance failed. So let's try to analyze this situation without debug logs. Okay, at first, nobody turned accepting message. And second one is from scheduler. He said, attempting to build one instance. Okay, these are very easy to understand. But third one, it's called the beginning of sleep or sleepless night for you. So the new scheduler showed an error. Well, it's a very simple error. So the list of message must mean the lack of read disks. Okay, and this time, we'd like to get more information to drill down this situation, but that's all what you can see without debug logs. So, is it enough for newbies? So at least it wasn't enough for us. Next, go to next level. Let's analyze the same situation with debug logs. At first, nobody turned, round filter returned, 8080 host. This means there are 88 hyperbizers capable for required memory. Okay, so memory is not problem. And second one is also from scheduler. He said, does not have blah, blah, megabyte usable disk. It only has blah, blah, megabyte usable disk in 88 times from all hyperbizers. So there's not enough disk space in our hyperbizers in this situation. This is it. So debug log is very useful even in simple situations such like this. So this is the reason why we set open stack with debug log level. So if you'd like to use open stack from tomorrow, we suggest you to please think about your logging environment for your health. And this thread is a kind of promotion of NTT group. So, but this shows importance of standpoint of operators. So there are another problem around open stack logs. So NTT suggested and working on new function to solve this sort of one of them. So our suggested function realized to trace logs easily even across components. In current log implementation, each component has each request ID. So we needed to map request ID for tracing logs even in trouble shooting situation. But log format doesn't allow us to find IDs easily. For example, creating a new volume from image, Shinder calls Grants API. The right figure in the right side shows Shinder has the request ID like A in red color and Grants has request ID like B in blue color. So of course you can find like B in Shinder logs, but it's very deep, it's difficult to find. So our suggested function logs request ID mapping within one line in each corner, like the bottom of this slide. It's easy to find. So this spec was approved by the community and we are writing code now. This story tells you operators can contribute to the community from one standard point. Okay, this is the final slide for monitoring, about monitoring. As I mentioned before, we've been providing standard monitoring system inside our company. So if you saw, it might be important for you while I talk in this slide. So we give standardized monitoring workflow for internal service developers, such as standard monitoring item sets and rules and parameters threshold of our art on Zabix and so on. So once upon a time, we configured manually Zabix and Nagios. But then think about monitoring skin with OpenStack. On OpenStack, over 1,000 virtual machine are born and suddenly die, suddenly be killed. So can you configure manually in real time? It can't be. So we decided to add new function to our Zabix. It detects new VMs and starting and monitoring semi-automatically. So in this case, semi-automans, our engineers can choose whether any node is monitored or not by them service. So the function is based on auto-discovery function of Zabix, but we wrote some script to achieve our requirements. What does it mean? So it means we changed our workflow dramatically for the sake of OpenStack. So we suggest that before getting along with OpenStack, operators must consider their today's workflow deeper for an efficient operation with OpenStack. That was our monitoring. And last, I share our current issues and future plans. I explained that we are recently working on. At the beginning of OpenStack deployment, we designed our flavor focusing in the migration project. To migrate smoothly, the compatibility with old DC was more important than the resource efficiency. The VM specs some as old DC was the best solution for migration plan. Therefore, we designed our flavor that has 37 gigabytes disk capacity for one gigabyte memory. However, when we looked at the current usage, it turned out that only seven gigabytes disk capacity is in use for one gigabyte memory in average. To improve the efficiency, we had the new flavors having smaller disk capacity than current sets. And we are asking users to release unused disk capacity by switching to these new flavors. We are instating the additional memory capacity to servers concurrently. We accept we will be able to increase the VM density and the resource efficiency 1.3 times at least or two times at maximum. Sizing is always important. This is our future plan. We are planning to upgrade OpenStack itself. A lot of new features are coming, but we can't use them as long as we stay at I-South. Especially, we want to deploy load balancer as a service or L-Bus. We configure load balancer by manual today. It's not provided to OpenStack user. We tested the L-Bus API version one, but it doesn't meet our requirement due to a lack of function. Since L-Bus API version two will be mainstream at the community, we are waiting our vendor provides version two driver. We feel it better approach to address both of L-Bus deployment and OpenStack upgrades. We also have to establish our version of operation. We modify the horizon to make it fit our operation. We have to apply these patches to new version again. This request on deployment and test effort and it needs certain time. This provides us from upgrading frequency, frequently and following every release. Next release name is Mitaka. NTT R&D locates at Mitaka and we feel it is a familiar name. We went to use a familiar Mitaka release. By the way, these photos show our goods. We hand out marketplace. Chinese characters Kanji of Mitaka is written a sense and a towel. Don't forget to come to our booth to pick up US. After you check another user story of NTT group next of this presentation. Okay, that's all we have today. This is just a summary of what we presented. I'm gonna just emphasize a single point. OpenStack give us business speed and agility. That's the number one benefit and we have to think about to introduce OpenStack. Thank you very much for your attention and we have about two minutes remaining to answer your question if you have. Hi, that's a great presentation. Thank you. Are you planning to upgrade directly from Icehouse to Mitaka? Yeah, yes. We know OpenStack only supports version of step-by-step one version. So we have to figure out the process from Icehouse to at this point, the rebatee or maybe after that, the Mitaka evaluating the all steps, upgrade Icehouse to your rebatee within a certain maintenance time. That is a plan we are planning. And the original plan we had is we will get upgrade much earlier if possible before this summit, but it turned out the RDO package, after Juno package require the CentOS 7 for the hostOS. So now we are upgrading the hostOS and the great things community give us more suggestion. When I joined the operator meetup, there is a tool called Anvil. That will be another option to make packages for Juno or Kilo package for CentOS 6. But to avoid a complicated pass, we are now just upgrading the hostOS. That's our situation. And another. So question is a strategy, how to design the flavor, VM flavor. So at the time we designed the flavor initially, we just followed our previous KBM setup we used to use in the previous data center to make the migration easily. But after one year experience, we measure the usage. I think we have to go iterate this process to know how the user using the resource efficiently or just asking the other user having a similar work world to share the such number. It's kind of magic number, but we shared our number in the previous slide. I hope it's gonna give you some hint. Okay, so it's time to close up the session. Thank you for joining our presentation. Have a great summit.


Five things that make the narcissist return to you, sometimes the narcissist will return to you They will hoover you, they will come back Especially if one or more of these things are happening one If you are still susceptible to them in relation, if you are still susceptible to the narcissist manipulation They will return to you if you still have hope if you have a feeling of expectation or desire For a particular thing to happen if you still trust them if you still believe that things will change to improve They will sense this They will sense that you are still attached to them and this will make them want to return to you They will return to you Because they know that you still believe in them They know that you would be willing to give them another chance If the narcissist knows that you're no longer susceptible to them in relation They're not going to return to you They're not going to put themselves in a position where they could be rejected Where they could be humiliated The narcissist wants to be around people who believe in their lies and false promises People who believe in their future faking They don't want to be around people who don't believe in them It's your belief that gives them the power to take advantage of you They can't manipulate you if you don't believe in anything they're saying or doing Which is why they will only come back if you still believe If you're still susceptible to them in relation to money sex and other benefits The narcissist will only come back if they believe that you're still susceptible to them in relation and even if they do come back It's not because they miss you It's not because they love or care about you Narcissists are self-absorbed and lack empathy They only care about their own needs and if they believe that you can fulfill those needs They will return to you, especially if you have recently received a lot of money That will normally trigger a hoover from the narcissist Narcissists love money So they will definitely come back to try and get something out of you They will also come back for sex or whatever else you have to offer They may have been having sex with someone else while they were gone But after a while they get bored of doing it with the same person It's too familiar and predictable And if they haven't seen you for a while That will be another reason why they will come back But even then it's not because they miss having sex with you They don't even see you as a real person You're just an object to them You're just a tool that they use to pleasure themselves and that's why it's so easy for them to leave you That's why it's so easy for them to forget about you like you never existed Because you're just an object You're a placeable and once they've used you for the purpose that they've assigned you to You're discardable You have no use to them After they've got what they wanted from you free When you find someone else When you find someone else The narcissist will often return to you Not because they want to be with you But because they're jealous and insecure They can't stand to see you being with someone else But once they know that you're with someone else They no longer look at you in the same way They no longer see you as their property As their primary source of supply Now they feel as though they're trying to take you from someone else Which means that they might treat you differently They're no longer going to treat you as if you were their property Now they're just going to be more open about using you for whatever purpose they have assigned to you Because narcissists really don't respect relationships They just see it as though someone else is using you and taking advantage of you They're not going to take you as seriously as they once did They're not going to be as attached to the outcome But if they can take advantage of any arguments or disagreements you're having with your new partner They will This is when the narcissist will return and act as a hero Someone to save you from any arguments you might be having Even things that may be a normal part of a relationship Things that naturally occur The narcissist will blow it up They will act like they're mistreating you In an attempt to win you back When you break up with someone If you break up with someone This is something the narcissist will take advantage of Especially if they are the cause of the break-up Because you're likely to be in a vulnerable place So it will be much easier for them to exploit you For them to get what they weren't from you Narcissists love to leech off people who are in a vulnerable place It's easy pick-ins They don't really like people who are strong and have firm boundaries Because that would be a hindrance to what they're trying to accomplish So they will be lurking somewhere Waiting for you to break up They see it as an opportunity for them to get in But acting as though they're trying to help or support you Acting as though they have your best interest in mind When really they're just there to use you They're just there to take advantage of you While you're still hurt While you're still vulnerable Because they know at that moment You would be willing to trust anyone You would be willing to give them another chance But they will only show you why trusting them is a big mistake Five When the narcissist gets bored of their new source When the narcissist gets bored of their new source They will either look for another source Or hoover old sources So there is a chance that they might come back to you Especially if you are grade A supply If you gave the narcissist whatever they wanted without resistance to lay-off obstruction Of course they're going to come back to you Because that's exactly what a narcissist looks for When they target a new source But rather than putting in the extra effort to groom someone new If you're already preconditioned to be what they want you to be They will return to you The grass is always greener on the other side They always see their current situation as less desirable So if there was someone else It's only a matter of time until they see the grass being greener with you It's likely that the new source may have confronted them on their behaviour already Maybe the narcissist has begun devaluing them So they will be looking for someone to replace them When the narcissist gets bored of their new source That is when they are likely to return to you But this really depends on how susceptible their new source is to their manipulation If the new source is a doormat And does whatever the narcissist wants them to do Then the narcissist is unlikely to leave anytime soon The narcissist needs a fool They need someone that they can trick and deceive Someone to believe in them And if the new source is foolish enough to believe in them Then why would they ever leave? Just don't let yourself become that fool By giving the narcissist another chance Be wise Learn from your experience, knowledge and good judgement Learn from the mistakes that the new source has made So that you can make healthier decisions And live a better life without the narcissist Thank you for watching I hope this video wears out with you Please like, comment, share and subscribe Click the bell icon to receive notifications for my future videos Check out the new Narc Survival website At www.narcsurvival.co.uk Where you can read my blog posts, book coaching sessions And join our support forum If you would like to donate My PayPal link is in the video description For coaching inquiries You can email me at coaching.narcsurvival.co.uk Thank you for watching and I'll talk to you soon


Hiya! So in this video, we're going to look at what parallel and perpendicular lines are and how they look on a graph. And on a graph, they look like this, or like this, or even just like this. Notice how parallel lines have the same steepness. This is known as the gradient, which we will look at a lot in future videos. For now, you just need to know that parallel lines have the same gradient, go in the same direction, and will never cross each other. They will stay parallel forever. So if parallel lines always go in the same direction, perpendicular lines don't. So notice how one goes in this direction and the other one in this direction. They always cross each other at 90 degrees, which means they don't have the same gradient. They have a different steepness. Have a look around you, perpendicular lines are everywhere, like on a football pitch where the halfway line and sidelines cross each other in a car park everywhere. We will learn more about gradients in future videos, particularly of parallel and perpendicular lines, but for now, you just need to know what they look like on a graph.