Income tax 2023-2024, pensions and annuities tax software example. Get ready and some coffee because we're laying down the facts about income tax preparation 2023-2024. First, a word from our sponsor. Actually, we're sponsoring ourselves on this one because apparently the merchandisers, they don't want to be seen with us.  Like our, trust me, I'm an accountant product line. It's paramount that you let people know that you're an accountant because apparently we're among the only ones equipped with the number crunching skills to answer society's current deep complex and nuanced questions. If you would like a commercial free experience, consider subscribing to our website at accountinginstruction.com or accountinginstruction.thinkific.com. Here we are in our Form 1040 example problem using LASERT tax software. You don't need tax software to follow along but if you have access to tax software, it's a great tool to run scenarios with. You can also get access to the Form 1040 related schedules and instructions at the IRS website. IRS.gov, IRS.gov, starting with Adam Taxman. Just trying to avoid the dang Taxman livin' in 90210 Beverly Hills. We've got the single filer to start off with back to 100,000 W2 income standard deduction at the 13850 for the taxable income 86150, mirroring that in our income tax formula in Excel 100,013850 taxable income 86150, the tax being calculated by LASERT software 14266 on page 2. There's our 14266. We're now going to be looking at the 1099R once again. Going back to page one last time, noting that we looked at the 1099R with relation to an IRA distributions. Now we're looking at the pensions. So we were on line four. Now we're going to be on line five. Note that they're very similar in nature and that they're going to be typically reported here on the Form 1099R, which is labeled distributions from pensions, annuity, retirement, or profit sharing plans, IRA insurance contracts, and so forth. The major box is being box one, the gross distribution, box two, the taxable amount of the distribution. Box seven is important because you could have a code. This check box could give you an indication as to whether it's going to be an IRA or pension distribution. And then you could have the withholdings that could be here as well. Remembering that if someone is in their working years, then you would expect the major forms you would receive are like W2 forms. For example, if they are in retirement years, you would think that the major income forms you might be receiving are the 1099Rs, which are reflecting money that has been put away for retirement in an account that's under the umbrella of some kind of tax entity, meaning you're still usually investing in stocks and bonds, but you put it under the umbrella of say an IRA, that's what we talked about before, when you don't have access usually to an employer plan such as a 401K or a 403B because there's more limitations to put money into an IRA and less benefits such as matching so that those are typically going to be used for added contributions or so that because you don't have access to some other form of contribution or if you put money into like a 401K plan or something like that, which is usually more, you might have more benefits to put money in like putting more money in and having matching. And now we're going to be pulling money out because we got a deferral of the income related to those plans and typically they'll be hopefully properly reported on the 1099 and therefore fairly easy to do the data input. So with tax planning, you have two kind of or with tax preparation or tax issues, you have two things to be thinking about. One, just the data input, which is usually fairly straightforward because the 1099 will guide you. And then two, what do people do in retirement with regards to their withholdings, meaning now they have to figure out when they pull money out if it's taxable or not. If they're subject to tax, how are they going to pay the tax? Do they want to withhold it from the 1099 or do they want to make estimated tax payments, for example. And when you put money into a retirement plan, again, that takes some tax planning situations as well. Okay, let's start off with the normal scenario like we did with the IRAs. Let's imagine that the person is in retirement age. So we're not talking about them putting money into the plan. They're retired and now taking money out of the plan. So let's say they're like 67. So we'll say 2023 minus 67 date of birth. Let's bring it back to 1956 about. And so we're going to say, all right, so then they're in retirement. Let me go back here and let's say they do not have W2 income. So I'm going to remove the W2 income and say now they're going to get their income instead from pensions and IRAs. And let's say this is pension one. And I'm going to say the distribution code is seven because it's a normal distribution. That would be what you would normally see. You would think if it was just a normal distribution, which is going to be subject to tax. And then we're going to say the taxable amount, let's say is 75,000 this time. And then it's all taxable. This is the gross distribution, I should say, and the taxable amount of the distribution. They might have withholdings on it. Let's imagine they have withholdings of $6,000 of withholdings. So that would be box one populated box to the taxable amount, same numbers. And then the withholding amount is going to be the and then the code is seven. And then box four was the withholding. Let's make it a little bit different. Actually, let's make it. Let's say that's that 70,000 was taxable just to make it different. So then I'm going to go back to the forums and say, all right. So now notice it popped me. It bounced me off to the 1040 SR, but I'm still going to view it on the form 1040. So we have the same layout. So it'll be easier to see. So now we're going to say 75,000 was the total amount, but only 70,000 of it is going to be taxable. Therefore, only 70 of the 75 is included in the taxable income. If I mirror that in my formula, I'm going to go back to the income tab. No W2 income. Instead, we have the 1099. So I'm going to say pension distribution and I'll say 70,000 of it is taxable. The full amount was 75, which I'll put on the side so I can see it. I'll sum it up over here just so we can see that for my informational purposes. But the 70 is the taxable amount, which is going to pull into the first line of my equation. They're over the age limit. So I'm going to add the standard deduction has an added 1,850. So that comes out to 1570 taxable income at 54,300. If I go back on over here, 54,300 and then page two, 7,265 is the tax. So 7,265 and then I said that we withheld 6,000. So withholdings then payments, I'm going to say from 1099,6,000. That's 6,000 then pulling over to my page one. So there's the tax 6,000 withheld. We have 1,265.  Actually, this tax was what was it? 7,259. So 1,286 and 1,286. Okay, so that's the general scenario that we would see in retirement. Now let's imagine that they weren't in retirement and they pulled the money out early. So what would happen then? Let's go back on over and say, okay, let's bring it back to saying now we'll say that the ages will bring it back to 1977. Let's say and then we had the pension income. And let's say now it's 75,000 and 75,000 that they pulled out. I'm going to remove the federal withholdings, but the code this time was that it was an early distribution, no exception. So that's a bad code to see typically. So if we saw that in box seven, we're going to go, oh no, that could cause a problem. Notice also that you want to be careful to assign it to the proper spouse if they are married because that could have implications and that this box represents if it's going to go into the IRA or not. So in other words, if I go back on over here, I could see then if I go to the first page, we now have the 75,000. Now we're at the 13850 because we're back down to the standard deduction. So if I mirror that over here, I'm going to say now all 75,000 was taxable. And if I go back on over now, they're not over the age limit standard deduction back down to 13850. That gets me to 61,150. So we're at 61,150. And then on page two, tax is 8,766. But we also have this other tax, which is substantial, 7,500. That's coming from schedule two line 21. If I go to schedule two line 21, I can see it right here. It's the additional tax on IRA or other tax favorite accounts. 5329 is the form it's coming from. Additional tax on qualified plans. And you could see basically it's taking 10% of the distribution because it was taken out before the retirement age. Now you could have a situation where there's a rationale or reason for it, meaning early distribution exception applies. If that was the case possibly, then you take the early distribution and there's an exception for whatever reason. We still haven't included an income. So that's a common misconception where people say, hey, look, there was an exception. I shouldn't have to pay taxes on it. It's like, well, no, you still have to pay taxes on it. You're just not going to get hit with that massive penalty because you still got the benefit of taking the money tax free when you put it into the retirement account. So there we see that. And then just to note the difference between these two forms, you can see that this is on line 5A. If I go back on over and check this off and go back, you could see then it pulls it up to 4A. So that's the difference between 4A and 5A in our data input form, which will typically be indicated on the 1099R, which is used for both by this basically box right here for IRA or not. So I'm going to go back on over. I'm going to uncheck that and say, okay, let's uncheck that. And that brings us back here. So there it is. Now the other common thing you might have is that one, some person goes from one job to another job, in which case you might see a code that says like G, which is a rollover. So now we have a rollover. And so that would mean that box one would have the amount box to hopefully would be something like zero because none of it is taxable. It's just reporting that you went from one place to another, which might happen when you go to a new job. For example, you're still subject to the same same issues with pulling the money out, but you want to put it under a different like managing or financial institution. So now we have 75,000 pension and annuities marking that it's rolled over and therefore none of it is being included for taxes. It's not having an impact on the taxable income. So usually it's fairly straightforward to do the data input, noting again that there's a difference between kind of the data input and then and then the planning for it. And you might have some planning after you do the data input, which would be like something like how much do you need to withhold next year so you don't get hit with penalties. Is there any way that you could pull money out of the pension plan that's subject to tax and some money out of plans that are not subject to tax so you result in a lower amount of taxable income. And then when people are moving from job to job you have questions about well should you roll the money over typically roll the money over and don't take it out if possible you might get hit with a penalty. If people really need to take it out because there's an emergency, then you can look into basically possible scenarios in which case it may not be subject to tax in certain situations like a like a declared disaster or something like that. And see when it might be pulled out noting that you want to make sure that the financial institution is made aware of the issue so that when they report the information on the 1099 are which will go to the IRS. We have something in box seven that does not indicate hopefully that it's going to be subject to penalties. Right we want it to be on the 1099 are so that it will not cause us any problems with the government and remember that with distributions it'll probably still be subject to income tax. But we want to get the get rid of the penalties there's not really a way around the income tax if you didn't have to pay taxes when you put the money in. But we don't want to have a penalty on top of the tax on the distribution is the general idea if I go back to the first tab. You can also look through some of the codes here for more information that might give you ideas of when of when distributions might not be taxable. You can look into some other tax planning strategies and whatnot with regards to iris in terms of trying to maximize the tax benefit of the iris. You can also look at the instructions if there's any issues with this form that you have questions with. You can look at the instructions for the forms and take a look at at these code numbers which can help you guide you with the data input tell you what's happening help you to explain it. And also guide you for further research that you can go to from there.


I really do think this might be one of my favorite things to talk about. So in the last section, we saw how things get phagocytosed or yumptualized into the cell. And the reason why I want to talk about the MHC platform right now is because that non-specific phagocytosis, there's a process that can happen where we can post information about what was phagocytosed. And then the rest of the body can benefit from the information about what was inside you. So I want to talk about how the complex is actually formed. So I brought back this picture that we just drew because this was my non-specific phagocyt, and you have this visual of how we could actually end up with my pathogen inside a vesicle inside this cell. And that process, the next step is actually going to be to take this pathogen and break it up into pieces.  We'll break this guy up and we'll end up with parts of the guy. As soon as we have broken it up into parts, this vesicle is going to fuse with the endoplasmic reticulum. And pathogen parts are going to dump into the endoplasmic reticulum. Now, if you think about what the endoplasmic reticulum does, it's involved in processing proteins. Inside the endoplasmic reticulum are empty MHC platforms. Okay, so here we are. We have endoplasmic reticulum and we have an empty MHC platform, which surely must be this color. So this is kind of how I'm drawing my MHC platforms. The endoplasmic reticulum just got pathogen parts and it does the way, there's this whole chemical like magic. Oh, it's so amazing. Whereby, pathogen parts get posted onto this MHC platform. Actually, anything can get posted on there. Anything, any like self-molecules, like just metabolism results. And making this hormone and little pieces of that hormone are going to get posted on this MHC molecule. So it doesn't have to be a pathogen that goes on it. The endoplasmic reticulum is constantly producing these loaded MHC platforms. If you just ate a pathogen, then you're going to load it up with pathogen parts. From the endoplasmic reticulum, maybe y'all remember this, endoplasmic reticulum like bubbles off and forms these little vesicles that then travel to the Golgi bodies where the vesicle is like packaged and what you're packaging is an MHC platform in a vesicle that then is exocytosed into the cell membrane. Look at how I've drawn the MHC platform in this vesicle. I drew it so that you can see that it's actually embedded in the vesicle. So that when you exocytose that thing, when you combine the cell membrane and exocytose it, you're going to have an MHC platform that is now embedded in your cell membrane. And it's not an empty one. It has evidence of what you did. You just posted your dinner. You just posted the fact that you were invaded. So now you have or you posted that, you know, we went to the fair with our kids. I had cotton candy while I was there. It was awesome. I'm not getting enough sleep, whatever. All of that gets posted on the MHC platform. Now, there's two flavors of MHC. The MHC one, every single nucleated cell in your body has MHC one platforms. They're coated four by genes. They're very specific to you. And they're one of the biggest reasons that I can't like rip off my arm and give it to you. And you rip off your arm and give it to me and we can like trade. Now, why can't we trade? Because my body is going to straight up stone cold reject your arm if I try to sew it on there. And your body is going to do the same to mine unless we're like super related to each other or we've gone through all this testing and we find that, you know, we have a lot of similarities in our MHC platforms because all nucleated cells have these, which means who doesn't have them? Who doesn't have a nucleus? Red blood cells, red blood cells do not have MHC one. Which means what about blood transplants? Dude, you can totally do it because your red blood cells don't have MHC one. If they did, blood transfusions, donating blood, like we wouldn't do it. You'd wait until you had a match and then you'd like donate blood to the person with the match like, thank goodness, our red blood cells do not have MHC one otherwise we'd never be able to donate blood to anybody. Or it would be very rare. It would be like the difficulty, you know, you get on the donor list and you have to wait for forever not because there aren't organs available but because it's really hard to find a match. When there is an organ available, it probably isn't one that's going to match you. Also, when you get some sort of an organ transplant, you have to go on anti-immune system drugs to tell your own immune system to chill its jets because you're putting in something that isn't you. So most healthy immune systems will attack that thing that isn't you because they will recognize that, yeah, that MHC one doesn't belong to me. Okay, dude, this is so awesome. So MHC one and two are super important in the acquired immune response but our next innate immune player is going to respond to something about MHC one. So let's talk about the natural killers.


This is stock number 10334. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. Today we are checking out this super clean, super cool looking 2016 Chevy Silverado 3500 crew cab, short box, single rear wheel. This truck has the 6.6 liter Duramax diesel with the LML motor. I'm just going to do one quick walk around from far away on this truck and then we'll get up close and personal to it so you can see all the options and take a look at the lift kit on it and the rims and everything that goes along with this truck. But a really nice shape on this vehicle has a really good stance, probably one of the sharpest Chevys I've ever seen in my life and just a really good looking truck all the way around. But we'll get up close and personal and show you just how nice and conditioned this truck is in. We shoot all of our videos in 1080p so if you have HD capabilities on your computer tablet or smartphone device, turn them on right now because it is like you're right here looking at the truck with me and definitely your best way to check out the vehicle before seeing it in person. If you want to check out this vehicle, more pictures of it on our website in the upper right-hand part of the screen is a link to our website. Click that and check us out there, otherwise sit back and enjoy the video. This one has Vision 24-inch chromed alloy rims, really good looking rims on this truck and I can imagine what they look like going down the road and it has rolling big power Redulsor MT tires and these tires have a good amount of tread left. Not sure what they look like new but I would imagine that they've got probably about 60%, 70% of the tread left has a rough country suspension lift kit on it. You can see all the stuff that's been done to the lift or to the suspension for that lift. Really nicely done lift on this truck. Front bumper is in excellent shape so is the lower valance. No dents or dings on that front bumper as the front bumper parking sensors, factory fog lights, projected lamp headlamps, clearance lights. The hood is in excellent condition, no dents or dings on that. Passengers side fenders in excellent shape as well, no dents or dings on there. The passenger side rim, pretty nice condition. One little scuff right there but you can hardly tell how shiny they are and as you go down this side of the truck you can see just how clean the body is, how reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down you can still see the truck here, the truck and have confidence in the vehicle that you're looking at before you even get here. Chrome bed rail covers, we even offer a summit fast pass option on our website where you can apply for financing, get approved, even check out the value of your train, get a good idea on that so when you get here all you gotta do is drive the truck and love it and take it home. Looks like it has all the remaining factory exhaust so I don't think it's been altered in any way like that. Factory chrome step bars, this back rim is probably one of the nicest on the truck. Didn't see any scuffs or scrapes on that and the back tires have just as much tread as the front tires. Frame and underbody is very clean on here as we come around to the back of the vehicle the rear bumper, really nice shape no dents or dings on that has the backup parking sensors, in bumper steps, tailgates in pretty nice shape as well, has a Truxedo tonneau cover that's in all okay condition, has the shock down assist tailgate, spray and bed liner, has the LED bed lighting, see that beds in really nice condition, tailgate shuts nice and solidly and as you go down this side the truck just as clean as a passenger side and for full disclosure this back rim really nice condition as well, didn't see any scuffs or scrapes, get a really good idea of how nice those rims are, deep dish, down this rest of the side very very clean I didn't see any dents or dings, has the telescopic tow mirrors built in directional signals, side LED lighting directional signals on the side of the mirrors as well, inside the LTZ package gives you the black leather interior there are no rips there are no tears on these seats, they are in excellent condition both these seats are heated factory all-weather floor mats throughout power windows power locks power mirrors memory driver seat and these tow mirrors actually power fold in and power fold out, has the Bose sound system auto headlamps turned out four-wheel drive and a factory brake controller, as we hop inside the truck here you can see that this one has 38,785 miles you get the Z71 instrument cluster comes with the heated leather wrap steering wheel cruise control or information center controls on the right and Bluetooth controls and cruise controls and heated steering wheel on the left, six-speed allison transmission comes with the Chevy MyLink radio AM FM and Sirius XM radio capabilities as well as factory navigation this one does have a CD player and you do get the projection option so you can do the Android Auto and Apple CarPlay on there this is also where your backup camera shows up down here is your climate control tool climate control your heated seat buttons power pedals stability control that's for your cargo lamps that turns on the lights in the mirrors and it also turns on the lights in your box parking sensors you can turn those off down hill assist control and a factory brake controller you get two USBs two power points and a 110 volt 150 watt plug-in the dual glove box is over there and the passenger seat and floor mat are in excellent condition as well I don't think this truck's ever been smoked in smells very clean inside the headliner is absolutely perfect up here you get your home link buttons for your garage door security systems and lighting systems and your map lights on-star capabilities in the rearview mirror and we will take a quick look at the back seats and then check out 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 the power sliding rear window with the built-in rear defrost these seats fold up for extra storage very clean back here factory all other floor mats has the winter front and very very nice we'll take a quick look under the hood I would personally like to thank you for checking out the video today and hopefully from this HD video you'll been able to tell just how clean this truck is all the way around inside and out under the hood we have the 6.6 liter Duramax diesel LML motor engine base very clean runs very smooth this truck has been fully safety then inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off truck has been gone through mechanically 100% and is 100% ready to go the Seymour pictures of this truck are one of our other 450 new and used cars trucks SUVs minivans Wranglers half tons sweet quarter tons one tons you name we got it go to our website www.SummitAuto.com full pictures and descriptions of every single vehicle from two locations all at SummitAuto.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 in fact in a second you will see a link to subscribe to our YouTube channel on your left you link to more heavy duty truck videos like this one on your right if you've not been to our website on the bottom link to this vehicle on our website click those check us out and we really look forward to helping you with this super clean super cool look in 2016 Chevy Silverado 3500 crew cab short box single rear wheel with the rough country lift on it thanks again


All right. Thank you, Matt. So yes, like Matt said, welcome everybody to the Polymer Summit 2016 in London. My name is Taylor Savage. I'm the product manager of the Polymer project. We're at a very unique moment right now in the arc of Polymer and the arc of Web Components. And really, we're in a unique moment for the arc of the capabilities of the web platform overall. We're witnessing right now, like right at this event, right now the confluence of three factors all coming together. The first is the acceleration of the importance of the impact and of the usage of the mobile web. The second is the cross-browser launch of Web Components. And then the third is we're seeing a really major new milestone for the Polymer project, representing what I think is a really exciting new chapter. So I'll cover all of these three different moments and what each of these mean for all of us as web developers. So let's start with mobile. Now, the acceleration of mobile has been ongoing. We've been seeing it for a few years now. But suddenly, we've hit this moment where native apps seem to be starting to hit a saturation point. And with new capabilities of the mobile web platform, with things like Service Worker, with the ability to build progressive web apps, developers and companies are starting to turn back to the mobile web as a really capable, immersive platform. And so for web developers, this represents an exciting opportunity, but also a challenge. What we're seeing is the attack of the phones. So the mobile web is incredibly exciting. Nearly every device out there has a browser, everything from the phones in all of our pockets to our refrigerators. And we have the ability as developers for free without asking anyone's permission to build an application and put it up on the web and let any user anywhere in the world access it with just a URL. But mobile development also makes our lives as web developers really, really challenging. We're expected to build immersive applications that run at 60 frames per second, that load immediately, that are responsive to the touch, that work across a wide array of different screen sizes, from the watch face to a 60 inch TV screen. And chances are we've got to deliver that application across a mobile network, a slow, flaky network, or sometimes with no network at all. And on top of that, we've got to deliver this application over the slow, flaky network to devices that are oftentimes really slow, really underpowered, sometimes overheated, as you'll hear about more at this summit. And on top of that, the code bases that we're starting from, often just look something like this, like giant mounds of really, really gross spaghetti code, most likely they were built originally for desktop and you're inheriting this code base from someone and maybe it was created with a once popular framework that's now past its prime. And there's a chance that you now have to kind of rejigger this to make it somehow work on these tiny mobile devices with all these different constraints. Mobile web development is hard. It's time consuming, it's expensive, it's hard to know where to start. And for the longest time, the web platform itself didn't really help us in the process and it didn't really help us developers out. And so we've built layers upon layers of tooling, of abstractions to make our lives as developers easier. But now, with these especially challenging mobile constraints, slow devices, flaky networks, these tools that we've relied on for so long can start to sometimes get in our way. Or they can lead us down a path, naturally down a path that will ultimately lead to worse outcomes for our users on these mobile devices. So we have a thesis on the Polymer Project around how to build powerful mobile web applications with minimal overhead, which is to use the platform. The web platform is our ally now as web developers and as part of the Chrome web platform team at Google, our mission on the Polymer Project is to advance this underlying web platform to make it easier for developers to build better apps and to ultimately make all of our users' lives just a little bit better. And so also on the Polymer Project, our mission is not only to advance the platform but to provide developers with the tools that they need to smooth over some of the rough edges of the platform so you can still build powerful applications as close to the metal as possible. So I wanna be really, really clear what we mean by use the platform. Use the platform does not mean abandoning the tools and frameworks that you know and love. It does not mean ignoring the value that JavaScript frameworks provide. It doesn't mean don't write any JavaScript. JavaScript is part of the platform, that's part of using the platform. What use the platform means is to challenge the assumptions of what you need in order to build scalably on the web. It's a call to take advantage of what's already there sitting in our user's pockets in the form of browsers. It means let the browser do the hard work. It means be selective with abstraction. Every abstraction comes at a cost. Every abstraction means extra code that your users need to download and run in order to ultimately run and interact with your application. So when you're building on the web and we're using abstraction, go in with eyes wide open. Know where that abstraction is going to provide a ceiling, know where it's gonna help you, know where it's gonna be a cost for you and your users. And finally, use the platform means that rather than doing everything possible to work around the web platform to pretend like it doesn't even exist, be aware of where the modern web platform can help you do more with less. Which brings me to our second major factor that's coming together right now. As we speak, a set of new web platform features that really truly let you do so much more with so much less, which are web components. So web components are the primary feature that we've been focused on in the Polymer project for a number of years now. They're a set of new web platform standards to let you natively build reusable components on the web. Now web components as a spec started back in 2012.  We were over-optimistic with how quickly web components would get broadly adopted and broadly supported across browser. We were over-optimistic. And so we went back to work along with all other major browser vendors through long life cycles of iterations, many, many false starts, many, many face-to-faces across all the different browser vendors. And finally, basically as of today, basically as of right now, we can say that we've made it that web components are here. With web components v1, our new hope. So custom elements and shadow DOM specifically are two of the critical specs that fall under the umbrella of web components. And born out of a multi-year cross-browser collaboration, we've ended up with the v1 versions of these specs. The previous version that had shipped in Chrome are v0, and now we've landed a slightly different updated version that is v1. And as of basically today, as of just a few weeks ago, we can say for the first time ever that web components are shipping in multiple different rendering engines with the launch of Safari 10 just a few weeks ago. So previously, web component support was buried and it was scattered. Template was supported across the board, but other critical features like shadow DOM, like custom elements, were either behind a flag or unsupported. But now we have v1. All major browser vendors have rallied around these new specs. As I said, Safari has already shipped shadow DOM v1 in Safari 10, and they are actively implementing custom elements. You can see them in Safari Tech Preview right now. And both custom elements in shadow DOM v1 are on the high priority roadmap for Edge. HTML imports are still on hold as we're working out how they're gonna interact with ES6 modules as those come together, but we're confident in the Polymer project that will end up in a really good place with a spectrum and way to load HTML with HTML. So at IO this year, I said that cross-browser web component support was not a matter of if, but a matter of when, and when is right now. Web components are here. Whoa. So we've got the acceleration of the mobile web leading to the need to use the platform to take more advantage of what the platform provides us as developers. We've got now a powerful new platform primitive in web components that allow us to ship less code. Now we're running cross-browser, which brings me to the third confluence, which is Polymer. So the Polymer library has existed in some form or another for well over three years now. In 2014, we released Polymer 0.5, which was the developer preview version of Polymer. In 2015, we released the production ready version of Polymer, Polymer 1.0, and now it's 2016. So Polymer 1.0 has been out for a little over a year, and I think because Polymer started out initially as an experiment, it was kind of in this experimental phase with web components since the very early days. We get the question a ton. Is Polymer ready for production? Is anyone actually using Polymer in production? Are any big companies using Polymer? And so I wanted to mention today, just a handful of the companies that are using Polymer in production right now. Polymer is used by Comcast, which is the largest media company in the world. It's used by USA Today, which is the flagship brand of the largest newspaper publisher in the U.S., GANET. It's used by ING, the largest online bank in Europe. It's used by Netaporte, the largest luxury fashion e-commerce company. By BVVA, which is one of the largest banks in Spain and Latin America. By Coca-Cola, the largest beverage company in the world. By Electronic Arts, one of the largest game publishers in the world. By Predix, which is the software platform for the industrial internet of things from General Electric, which is the largest digital industrial company in the world. And of course, Polymer's used here at Google on some of our biggest user-facing products. It's used in Chrome with over a billion users. It's used on Play Music. It's used in YouTube gaming. And I'm extremely excited to be able to announce, for the first time ever, that Polymer is used in YouTube. YouTube, one of Google's biggest products with over a billion users as well, is now building their next generation of mobile and desktop sites all on top of Polymer. So Polymer is becoming one of, if not, the most important front-end web development dependency here at Google. Used on well over 500 projects with over 6,000 individual components checked into the Google code repository. So these are just a handful of the companies who are going all in on standards-based web development.  So there's a pattern that's starting to emerge. Because Polymer is standards-based, it's enterprise-grade. It's impossible to get hundreds of different engineering teams to all standardize on the same technology. Heck, it is impossible to find two web developers anywhere in the world who use the exact same tool set. Except that there's one thing that every web developer has in common, which is we're web developers. We're building on the web. And so when you're building to web standard primitives, when you're building close to the platform, standardization becomes trivial. It becomes the default. And so this will be a common theme across this summit, which that the promise of web components by and large is here. And it can lead to great standardization across companies, across organizations, across ecosystems. So there's still plenty of more to do. And with web components shipping across browsers, we have an opportunity to make a big leap forward with the Polymer project. So I'm extremely excited today to announce the preview release of the next major version of Polymer, Polymer 2.0. So Polymer 2.0 will be closer to the platform than ever. And there are a few main features that we focused on to really make Polymer 2.0 great. The first and the most important feature of Polymer 2.0 is web component V1 support. So Polymer 2.0 is designed to take advantage of the new custom element and Shadow DOM V1 APIs that are shipping across browser. And on top of that, it embraces ES6 classes, allowing you to write a custom element using the standard ES6 class syntax. So I'll show you what that looks like. When you're using the standard ES6 class syntax in Polymer 2.0, you'll create an element something like this. You'll have that standard ES6 class MyElement extends this Polymer.ElementBase class. You'll provide a config, which will allow you to set up the properties and the observers that you know and love from Polymer. You'll use the standard platform provided ES6 and custom element callbacks with the constructor and the connected callback, which is V1 custom elements API. And then you'll register your element using that V1 custom elements.define call to actually register your element. So this truly realizes the Polymer vision, which is to be as close to the platform as possible with just a little bit of minimal sugaring on top. And because 2.0 is so close to the platform, it's actually fairly straightforward to take advantage of many other platform tools like TypeScript. So this is what a Polymer 2.0 element definition would look like using TypeScript decorators. So on top of just the really nice-looking syntax, you'll also get type checking within and then between elements. Polymer 2.0 also eliminates some of the Polymer-specific abstractions that leaked through in Polymer 1, namely the Polymer.dom and structured data manipulation APIs, so that a web component built on Polymer 2.0 will be indistinguishable from a vanilla custom element. So I'll give an example of what I mean. In Polymer 1.0, you might write some script that looks something like this. You'll have a custom element built with Polymer in your page. And if you wanted to add a child to that element, you need to make this Polymer.dom call. And this was so that the Polymer Shadydom system could know about the distribution of this component and make sure that the DOM tree is still correct and reflected as it would be in native Shadow DOM. This is a performance enhancement to be able to run Polymer on browsers that didn't yet support native Shadow DOM, especially mobile browsers. But with Polymer 2.0, because we can rely on native Shadow DOM in more places, particularly on all major mobile browsers, we can do a little extra work so you no longer have to use this Polymer.dom workaround. So to do the exact same thing to add a child, you just make the standard DOM API call that you would expect with any other element. So you don't have to know how this element was implemented under the hood. It's just any other HTML element. And of course, we don't wanna leave Polymer 1.0 users, these many big, large Polymer 1.0 users in the dust. So Polymer 2.0 comes with a near seamless backwards compatibility layer, making it dead simple to upgrade an element from Polymer 1.0 to 2.0. And critically, Polymer 2.0 also lets you build elements in what we call hybrid mode. And what hybrid mode means is that the very same element will work under Polymer 1.0 or Polymer 2.0 with a compatibility layer. And this allows you to incrementally upgrade your project one component at a time. So I'll show you what that would look like. In a typical 1.0 to 2.0 transition, you would look something like this. You'd have your entire application and all the components all built on 1.0 and stop the presses. Suddenly we have to go back to the drawing board, rebuild every single element so that it works in 2.0. And weeks or maybe months or maybe even years later, we finally finished this transition and we can start again 2.0 fresh. And this is terrible. This is a bummer, especially if you have hundreds or thousands of components to upgrade. So with hybrid mode, you can now incrementally upgrade your project in place. So again, hybrid mode means that the very same element definition can run using Polymer 1.0 or Polymer 2.0. So an upgrade with hybrid mode might look something like this. One element at a time, you incrementally upgrade into hybrid mode as this application is still running in production. You can keep adding features, you can keep adding new components in hybrid mode as you go. And once all of the components are in this hybrid mode, you can switch out Polymer under the hood, run it on top of 2.0, and then again incrementally upgrade component to take advantage of 2.0 specific features, again, as the application is still in production. So this rocks. This is much easier. It means your application can stay live in production as you upgrade it in place. Also, this hybrid mode is totally optional. If you want to start fresh using that great 2.0 class syntax, you absolutely can do that. Don't have to bring along any of the hybrid mode support. This is largely for very large companies, very large projects with lots of components to upgrade. So taking a step back and looking at the overall arc of the Polymer library, 0.5 is an experiment to see if the web component standards could create a compelling developer experience. 1.0 was to bring this developer experience to production. It was faster, it was lighter, it was more resilient, it was rebuilt from the ground up. It was something that you could use in a real-life application as many large companies and projects are, despite web components not being broadly supported yet. And with 2.0, we can fully realize the full value of web components. Elements built with 2.0 are web-native, with minimal overhead, no leaky abstractions based on cross-browser standards. A Polymer 2.0 is a truly encapsulated web component. Now we've always said that the goal of Polymer is to slowly melt away. That Polymer as a library should get smaller and smaller as the browser itself reaches up and supports a lot of these features. And with 2.0, we get even further along this path. So if you're using that Polymer.element syntax to build your ES6-style web components, it's just 12 kilobytes of overhead. So let's talk about elements. So in addition to the Polymer library, the Polymer team builds and maintains hundreds of different web components built with Polymer in multiple collections of elements. And as part of this 2.0 release, we'll be upgrading these Polymer elements to this 2.0 hybrid mode, meaning that they'll work under either 1.0 or 2.0. So if you use them in a large project, you can do that incremental upgrade that I described earlier. In addition to the elements in the library, the Polymer project also builds a large number of different tools for building and deploying elements and web applications and progressive web applications. And we have a huge amount of really exciting news for the tools, but I don't wanna spoil the surprise. So make sure that you catch tomorrow morning's keynote for the whole world of Polymer tools and what we've been working on there. So there's one more thing I'm also really excited about. As we're turning to this new chapter of web components and new version of Polymer, we're also seeing a large number of new web component libraries coming out. Things like SKJS, like XTAG, like Bosonic, and many more. And the great thing about web components is that they're standards based. So no matter how you build your web component, anyone should be able to use it. And now we build a lot of elements on the Polymer project and we show them off currently in the Polymer element catalog. But those should just be a tiny drop in the bucket in terms of the overall web component ecosystem. And we want all web component authors to have that same opportunity to share their work and get a large audience for their work regardless of who built the element regardless of what library it uses under the hood or whether it uses a library at all, whether it's just vanilla custom element. So the Polymer team in the Google office in Sydney has been working with the broader web component community on a new place to share web components with beta release of a new web components catalog on webcomponents.org. So this is full of some killer features to help you showcase elements that you build. It shows generated element documentation from comments that you have in your element code, along with live inline editable demos that you can get a sense of what an element does right away and start playing with it right there on the element page. It also supports curated collections of elements for sets of elements that go together. So anyone can publish a collection of elements. We've added, for example, all the paper elements and the iron elements as example collections to collect those elements. It's still a work in progress, but you can start publishing elements on this catalog today. And we would love to get your feedback on the project and we'd love to get your contributions to the catalog repository itself. So with the Polymer project, we plan to move all of our elements onto this catalog once it's ready to ship. And again, the Polymer team has built hundreds of components, but these should just be a tiny drop in the bucket as to the overall set of web components available. So I can't say this enough. We are at an incredibly exciting time. The importance of the mobile web is continuing to accelerate, but we as developers are increasingly armed with the tools that we need to tackle this challenge. Now this summit's gonna be packed. It's two full days of talks by Polymer team members, by Googlers, by engineers from major companies about how they're using Polymer and web components in production. It's going to be a whirlwind of information. But to help get the most out of the summit, I encourage you to look for a few dominant themes that will thread throughout all of these talks. The first is development efficiency. So we have a lot of tools at our disposal as engineers to improve our efficiency. But at this summit, I want you to look in particular at how standards can make you more efficient as an engineer. How standards can make an entire team more efficient. How they can make an entire company more efficient. How they can make the entire ecosystem more efficient. The second theme to look for is performance. New standards give us new dimensions along which we can look to achieve greater performance in our applications. And sometimes old techniques that we've, that are tried and true that we've been relying on for years can apply in this new world. But sometimes new technologies require totally new approaches, particularly in terms of performance. And so the key to building a blazing fast web application on the modern web today is to find that right balance between old techniques and new techniques that really take advantage of these new standards. And most of all, look for opportunity. Major shifts in technology at any level introduce huge new opportunities to make an impact. And web components are a major shift in how the web platform works. It introduces a new opportunity to make an impact at your company. It may introduce a new opportunity to make an impact at the overall web developer ecosystem. Because we are just at the very beginning of the web component revolution. And everyone here is out on the vanguard. This is a uniquely privileged position to be in, right as cross browser web components are starting to launch. The tools are here. Web components V1 is shipping cross browser. You can now build encapsulated components close to the metal with minimal overhead, letting you reach the next billion users, those on slow devices, those on slow networks. Polymer 2.0 is right around the corner. It's a big step forward based on these new web component standards. What gets built next is up to you. We're excited to see not only the next generation of web apps get built, but to see the next generation of components themselves. To see the next generation of tools and of services and of WYSIWYG editors and of CMS systems that get built to take advantage of web components and these new standards. And if all of us here are successful, the Polymer project will just be one tiny spec in a massive thriving ecosystem of web components. And for that, I can't wait. Enjoy the summit. Thank you.


Okay so today on the vlog I have a special treat for you guys I decided to do some men's cutting. Got a cool mannequin from Pivot Point so thank you to them. What we did was a disconnected undercut it's got a lot of wave and texture on the top so I played with that a little bit. We also carved in the part with the scissor so you can do it with a razor blade as well or clippers or whatever you want but we did it with scissors today and that's pretty much it. You guys are going to like it. We're going to get started with the step by step. Here we go.  The left hand side line is our part so right there is our parting and the other side is going to go a little bit deeper which will be our disconnection side. Now we're going through clipper over comb. I'm working diagonal back. Only what I'm trying to do right now is determine the length that I want the haircut. See the flow of the hair especially when somebody has longer hair and you're going shorter. I like to start off and just kind of work my way down to see how that hair is going to fall and especially on a mannequin I want to see how that's going to fall as well. I want you guys to really see and remember that I'm working that clipper from the face back to the back of the head. That's going to be important when we get to the next side. So I'm just working through tapering it so I'm starting closer to the head towards the bottom and then as I work my way up I lift the comb out. The more you lift the comb out the more weight you're going to build up so you want to make sure that you're building up the right amount of weight that you want and that your guest wants. So on this side now you're going to see I'm still working that clipper from the face to the back. It's really important that you keep the same flow with every tool that you use so whether you're using scissors or clippers I like to make sure that my blades are moving in the same direction because that's going to keep the hair flow going in the same direction. So still working diagonal back getting that bulk out of there. Now I'm going to move into my scissors. This scissor I got back out for I haven't had it out in quite a while. This is my blacksmith fit scissor. It's a six and a half inch scissor pretty much works for any type of cutting. This was the first scissor I ever got from Mizutani and every time I go back to it I don't understand why I don't use it more often because it's such an awesome scissor. So now I want to focus on scissor over comb. This is going to be my detail work and I know a lot of you out there thinking he could do this with clipper blades or clipper guards and have it done. Now my thought process on this is I like to really work I have the freedom when I'm working scissor over comb to move, shift the comb in, shift it out as I'm moving up the head. The head is not a perfect shape. So when you're running a clipper over it sometimes for me and this isn't for everybody I get that bounce of the clipper guard on the head and it's riding the ridges of the head. So I would rather have a more custom feel using a comb and working one little section at a time. That's just me personally. I know a lot of you out there use the clipper guards totally cool and a lot of people do beautiful work with them but for me in this type of cut it's not super short I like to use scissor over comb. So I'm going through just doing a little detail work around the ears we'll do more with a clipper later and then just tapering that edge. So I went through quickly with the clipper over comb and then I go through and I start really detailing the edges with the scissor over comb. You notice how I tap the hair into the comb there? That just allows me to kind of lock the hair in and then work that scissor over comb. And now what I'm doing is I'm looking on each side so I'll step back, I'll take a look at it from every angle and I want to make sure that I have a nice flat feel to the scissor over comb section and I'm working you'll see when I work up I want to take that wait line out a little bit with a mannequin it's tough to get that wait line out but as I work around that ridge my comb will actually follow the round of the head a little bit. Alright so now we're going in with our t-trimmer this is also from Andis just going through and detailing the edges there's not a lot of freedom in a mannequin but I do you know I like working with mannequins because first off I spend a lot of time doing these cuts to make sure that I can give you guys the detail work that we did we want and sometimes when you're working with a real guest it's they're more antsy to get out of the chair so we take what we can get. Alright so now I'm working with a I'm carving in the part with my scissor all I'm doing is keeping that steady blade and drawing that line this works really well it doesn't seem like it would cut that much hair it doesn't but it does cut that perfect line in there so if you guys want to try that out I think it's a really cool trick and it's not shaving in the part but you could always detail your line and then go in and shave it after if you want to so I'm over directing everything back to the crown I'm really connecting the the mid part of the haircut in the back so it's starting off first three sections go back to the previous so we're creating more of a square feel and you can see my top diagram that was really late last night that I did that and it looks crazy but we'll take what we can get there as well so now I go through first three sections are to the previous so a traveling guide and then we move to a stationary guide when we get three sections in just to build a little extra length in the front got a rusell pomade I love this stuff so if you guys haven't checked out this company they're really awesome so we're gonna start by putting that in the hair kind of slicking down the sides a little bit and then throwing in the top I love the texture of this cut I know it's a little bit crazy and it's kind of reminding me of my own hair I don't really know I guess maybe that was my inspiration this today but I did see a lot of men's cuts online when I was looking it up that have this kind of messed up style extra long on the top a lot of guys want to grow their hair out but they want to keep that tapered side so there you go I love the curl in the wave and how it shifts through so I hope you guys can use this cut let me know how you do in the comments below and once again if you like this video hit the like button hit the share button subscribe to our channel there's a lot more haircuts to come new haircuts every day at 10 a.m. thanks for watching guys you like it you wish you had this much hair


Now we're gonna give you some extra time. All right, let's get the ball rolling. It's a slow start. That's mostly my fault. So, all right, whenever you're ready. So, like I said, my name is Henrik Plix, one of the senior product managers, and I'm going to talk a bit about Ironic and how Ironic helps make OpenStack better for some traditional and cloud native workloads that you might have running. So, enterprises want to reduce cost, right? They want to increase utilization, automate, standardize, and contain complexity. And virtualization was the way we've been trying to do that for the last 15 years. So, for the last 15 years, we've tried to squeeze as much as we possibly could into a VM. But, what if you need access to the hardware, direct access to the hardware? Maybe you're running a database. You want to run big data workloads, or maybe you're looking at this new thing called containers. How is that working in a virtualized environment? So, that's where Ironic comes in. So, Ironic is an OpenStack service. It was broken out of Nova. It was called the Nova Bare Metal service before, and it's now its own OpenStack service. And it basically aims to provision Bare Metal just as similar to what you do with VMs. So, Ironic cuts out the middleman, so you don't have to worry about a hypervisor. There's no performance tax that, you know, you get to the hypervisor, you don't have to worry about performance, or you don't have to worry about the expensive hypervisor licenses. So, what is Ironic? It's really seen as a hypervisor. It's a hypervisor API from a Nova standpoint, and a set of drivers, not either reference drivers or vendor drivers that plug into Ironic to do Bare Metal provisioning. So, here's the, you've got 10 more seconds to take a look at this picture. So, this is the Ironic state machine. So, these are the states that I know typically would go through when you do provisioning. So, this is what Ironic helps abstract and helps the admins to deal with and not have to do that manually. And it's also easier for the tenants and the users. The commands and the way you do the Bare Metal provisioning is similar to how you do a VM. So, you do a Nova boot Bare Metal and you get a Bare Metal machine. And similar for ops, it's less headaches for ops. You don't have to worry about cleaning up nodes after the tenants are done messing it up. They do their own provisioning, so you don't have to do no more OS installs for the admins or the operators. And to make it even easier and better for the administrator, HP has a tool called OneView, which is basically a tool that by, or through templates helps you manage your hardware environment, servers, switches and whatnot. And in addition to that, there's also an upstream plugin for OneView that integrates with Ironic that helps automate even further by doing automated flavor creation and syncing the Ironic database with the OneView database. But wait a minute. One of the things we said we wanted to do with solar versionization was utilization. So, how do we do that when we're using Bare Metal? Do we just go back to where we were 15 years ago? Because it's hard to divvy up a Bare Metal machine. So, one thing you can do to overcome that is look at more of the low cost, high density servers like the Moonshot, where you basically shove 45 cartridges into a chassis and then you can do seven or eight chassis in a rack so you're getting hundreds of servers in a rack. Or you can look at this new cool thing that everyone's up and around about the containers. Containers love to run on Bare Metal. You don't have to worry about the performance hit running in VMs and you can get that nice divving up the machine that you can with VMs by a lot more lightweight. So, gonna end by taking a quick look into the future and some of the cool things that are going on in the ironic community in Newton and forward. So, one of the most asked for and highly anticipated feature is the multi-tenant networking. And right now you can only do single networks. Once you get the multi-tenancy then there'll be rainbows and unicorns and ironic will be awesome. Hopefully that will finally land in Newton. There's also work going on. I think the specs and the blueprints are being written right now about booting from volume and attaching volume basically using cinder together with ironic, which you can't really do right now but that's one of the key areas we're focusing on as well. But Bare Metal, it's available now. Go check it out. It's usable from Kilo and forward and it's also available in the new Helion OpenStack release that we announced here this week. So, go and check it out. Thanks. Under five minutes. All right, don't walk away. Yeah, we're gonna ask some questions. Folks, questions? Go ahead. The example you gave is mainly the Moonshot based on the ARM processor, meaning the one chassis hosting many ministers inside but I haven't seen any VNF or application that kind of rebased themself for the ARM instruction set. So, do you see a demand for this or you just expect that it will boom? Thanks. So, for Moonshot support, it has both Intel and ARM processors, right? So, right now we don't support ARM yet so that's something that will be in the future but there's definitely been an uptick in interest in Moonshot and a lot of that has been driven by ironic and there are service providers that wanna do Bare Metal as a service that seems everyone wants to do now either with or without containers so it's actually ironic because it's driving a lot of interest in Moonshot. Any questions on this side? No, okay. All right, what we're setting up for next, presenter. Again, the format is five minutes, 20 slides or approximately 20 slides. Anybody else interested in doing this next? A topic they wanna present, five minutes, no. Anybody wants to help Gavin present his 20 slides? Okay, are you ready? Test, test, oh, there we go. Thank you very much. I do not have time slides but you're gonna time me collectively. All right, I'm Dave Holly, Healing Product Manager and I'm gonna be talking about OpenStack Switching in particular for enterprise applications. Give you a little tour of where we've been and where we're going and what you can learn at this conference. All right, so I'm gonna use the reference of enterprise applications in OpenStack and I think this is really a cool topic area because it adds the right level of complexity to what we've been trying to do in networking and explains a lot of the projects we've been working on and I'm gonna start from the concept of a three tier enterprise app web application tier and database and what was required to do that. So first of all, you need local switching within the tiers, that's straightforward. If you have two VMs on the same compute node, you just have the local OVS switching that occurs between them and of course if you're on an adjacent compute node, we just do the translation onto the local virtual network across from one compute node to the next. Straightforward, simple. Next step, going between the tiers. Hold on a second, think about this. If you have multiple hundreds of applications running within a data center and every single transaction between tiers needs to go to a central network node, you have a serious bottleneck problem in your network. What did we do to solve that? This is where the area of distributed virtual routing or DVR was brought into play is to address this node. What we do is we add a local router for each tenant environment and local namespace so that we can do that routing and maintain the locality of transactions. For east-west, again, whether you're within a single node or going in between adjacent nodes. We've also addressed the north-south connectivity so for that web tier when you need to go outside, we can actually connect directly by having a local external bridge for that traffic that needs to go to the clients or the external environment. If we need to connect within to the network externally, we also still use that local network node for that source net function. Again, this is not generally used in such frequency in terms of transactional behavior, but we have recently added HA capability into that area. What we found though is a lot of enterprises have a real heartburn associated with natting in general or floating IPs because they have an operational model where they need to be able to access every single VM in their environment at a known IP address. So what's going on right now is work that's addressing this through a learning process using BGPR so that the identity of the VM is associated with the compute node that it's on and an external router can access directly into that while you use a static IP framework. Very important for a lot of enterprises. At the app tier, going down one level, a lot of applications have been built using ESX as the virtualized environment. And so something we've done in the past is already to put open V-switch into an ESX environment. So we have all of the same concepts available to us and we can within a single region, associate your KVM, your ESX and your bare metal or ironic environment. So let's go on to that. How do you do this switching if you have bare metal services embedded? Well, we've created the ability to directly connect from one compute node to another at a switching level and if you're using VXLAN, we've got a mechanism to do that in hardware for that VXLAN translation to a compute node. Once we add routing to it, things get more complicated. And again, this is an area you can learn more about here. We actually can leverage that routing transaction just as we did in the virtual space to talk to the compute node. The issue is when you come back in the other direction. And so what our engineers have done working with the community is to establish a DVR routing function that allows the bare metal service to talk back upstream into the virtual environment, giving you that completion of the bare metal routing function. So if you go from top to bottom again, we've now addressed the need for a web tier accessible through static IPs, an app tier that involves ESX, and a database tier that can support bare metal environments, all of which can route through the stack top to bottom. So we've transformed this concept of a KVM cloud-centric environment to an enterprise-class end-to-end multi-tier application supported consistently within a single region. If you want to go and learn more about these, there's a lot of sessions on Thursday. Some of the engineers are here, I recognize them, but you can learn more about the new topics that are coming in Newton and Okada. So feel free to dive in on Thursday. It's gonna be a great day for these types of sessions. So thank you very much, five minutes, top to bottom. Wow, that's right on the money. That's awesome, thank you so much. So questions? Go ahead. Why don't I just leave the mic with you, and you can just, no. The solution you presented for the bare metal connecting to network is mainly for layer three, diverting towards the controller host to layer three agent role for routing, right? So how about the bare metal layer two? Do you have any solution? Oh, so I kind of whizzed past the layer two. I did have one slide talking about the layer two. Right now, in the community, you have the flat VLAN-based networks, but we also have the work that's gone into, I think in Metaca, if someone can correct me, that's actually delivered the ability to have isolated tenant domains in the VLAN space within your bare metal ironic provisioning. So that's actually complete as of Metaca. The routing is what's coming in the next releases. Any other questions, anybody? On the slide around fixed IPs, I'm not familiar with the new DVR functionality, so I'm not sure if this is something that's in OpenStack or whether it's just something you guys have built, but you had a box in there with BGP in it. Is that part of Metaca now, or is that just something you guys have added in? There's ongoing work in that area, so the initial work that was done started with the last release, but I don't think it's quite finished yet, and so we'll see that complete, hopefully in the Newton timeframe to deliver that. And Ryan Tidwell is the lead for that particular project, and he's presenting on Thursday. Cool, thank you. All right, thanks. Hey, thanks again. That was beautiful. And was this your first Ignite? First Ignite. First Ignite, but he rocked it, like less than five minutes. Beautiful, thank you. I cheated only at 18 seconds. That's okay, that's okay, that's all good. Let's just make sure you don't have to. I think he built in timers, but. Is this in mic working, or can we turn it on? Thanks. Okay, so my name is Gavin Pratt, a Senior Director of Product Management for Healing and OpenStack. And back before I was working on Healing and OpenStack, which is HP's private cloud software offering, I was working in HP's public cloud, and it's interesting, part of why HP chose to pivot from public cloud to focus on selling private cloud software was we had a lot of customers saying, it's hard to really beat the price point of an AWS or the like, but we, almost all of them wanted to run something on-premise that had similar agility in the like of a public cloud. And they said, if you could find a way to package up all the things that you're doing in your public cloud and help us in particular solve the operational realities that we're currently struggling with, and especially with OpenStack, we pay you a lot of money. And so we heard this from customer after customer, and finally we said, maybe we should think about how do we package up the technology and the learnings of running a public cloud at a pretty large scale. And package that, not quite in strict wrap software, but they're pretty close. And so that's what the talk is gonna be about. It's interesting, I wasn't supposed to present this, somebody else on my team was. So I haven't seen the slides before, but I do know the content. And yet my biggest hurdle is I don't have a Mac, and I don't know how to advance the slides. So that's what we're solving right now, and that is our biggest. It's just ready to go, so whenever I'm... Like I said, this button? Yeah. Okay. Oh, and it's timing. Yeah.  Okay. Okay. Is this part of the learning? Wait. Yeah, this is the big button. Wait, the other red button. And I'll just put this on the side. That's not a button. It's not a button. No, it doesn't work. It's not a button. Oh, here. Oh, that bottom left. Yeah, okay. So monitoring opens at a good scale. So, you know, back in the public cloud days, we were originally using Solometer, and we had this really crazy backend that was trying to solve two problems. One was all the usage metering so we could build our customers. And the other was actually doing things like health checks and capacity checks to know if the system was down. And the problem was that Solometer was really neither purpose-built for one nor the other. I guess if you had to pick, you'd say it was more for billing. But because it wasn't... Are we sure it's on auto? Okay. It's fine. Okay, well, I'm gonna ignore it then. But also be under five minutes. Because it wasn't purpose-built for either one, we said, you know, architecturally, especially as we're trying to go to scale, it made more sense to split these two things out. Because for example, we were running these crazy Hadoop jobs once a month to take all the Solometer data and package it up into pricing files that ended up being just, you know, I don't know, like 20 pages long. And I was like, why does it take a week on this crazy Hadoop job when you have 20 servers to do that? There must be a better way. And so that's where Manosca was born. And so certainly, as I mentioned, you know, as more and more companies are saying, hey, I'm not interested in cloud, just, you know, in terms of a public cloud thing, but I wanna run cloud on premise. All of a sudden, all these operational realities became ones that were important to help individual enterprises come out. And many of these enterprises, sometimes had maybe five or 10, or sometimes even less than that, IT staff starting on other initial open-stack deployments. So they couldn't invest in 30 DevOps engineers like we had, for example, and our public cloud starting it up and Iraq space had a lot. So really, how do we make this, this open-stack platform address production workloads, but also be easy enough to use that enterprises that may not, they may be more familiar with VMware, for example, or with AWS, but they're not, you know, Python ninjas or anything like that. How do they get into production? Sorry, just start with the lights. I'm gonna skip that slide. Oh, excuse us. Sorry, it's just, it's hard to see with the lighting. And then so, there's a lot of problems we're trying to solve in the monitoring space. And so one is, you know, is the system healthy? You know, certainly if a bunch of servers go down, in theory and the cloud context, this is less critical than in traditional IT world where, you know, if a server goes down, like in traditional IT, every server had a name. Like the server named Gandalf and Icarus, and if Icarus went down, it was this, you know, national event. I was talking to a customer, I don't know if I can say the name, but I was talking to a customer last year and they were saying, you know, we're bringing up pets in cattle, but we currently have pandas. So basically, these like, we have these like zoo animals that are as like an international incident if it gets cold. And we're trying to get to pets. And so when you have those kinds of issues, and then later on top of that, things like security and compliance, where if a server gets out of compliance, because maybe somebody with root access changed permissions or the like, you have to monitor all of these things, especially for, you know, our financial services clients and our healthcare clients that have regulatory concerns. It's not just about running a company that they feel proud of, but they'll literally get taken to court if they get out of compliance and any of these things. It really is a mission critical issue for them. And I think I might be running over time, despite the fact that I, I was gonna say, but in general, you know, it's very easy to quickly generate tons and tons of data, and tons and tons of data doesn't necessarily drive to insight. And so one of the things that we were struggling with initially when we were running the public cloud was how do you generate a lot of data, but then either aggregate it up into a meaningful way or if you think of the needle on haystack analogy, how do I zoom in on the one piece of data that's important? And so that was one of the ways of thinking that we wanted to make sure we baked into Manosca, making it easy to do things like graphical time series data and see things like trends, the ability to see things at a high level, quickly go in and see more detail on specific areas that you want to pinpoint. Next slide. It's not working. Yeah, exactly. So monitoring capacity is as important as monitoring performance. So back, I don't know if I should admit this, but in our public cloud days are actually are, I mean, it's a nice problem to have, but the main problem that was keeping me up at night is as a product manager was running out of capacity because on the one hand, you know, the promise of the cloud is that you can get a server on demand, but the thing people forget about is a virtual server has a real server behind it and those real servers cost money and some of these servers, you know, can be very expensive servers. It could cost more than your car. And if you have a terabyte of RAM and all SSDs and the max number of cores and the like. And so it's not as simple as saying, let's just always have access capacity. That's a really quick way to have a horrible PNL as a public cloud, but also even your internal PNL if you're running an enterprise private cloud. So on the one hand, you don't want to over provision, but it can also get very tricky because if for example, you have some servers running Windows licenses and some Linux and the way the Microsoft licenses work is any server for most, depending on the licensing scheme you have, but for most enterprises, they have a Microsoft license. The second you get a Microsoft license on that server, you're paying for all the cores on that server. Even if you only have one tiny Windows VM. So for example, right off the bat, we had to say, we're gonna have a certain number of servers allocated to Windows, certain ones allocated to Linux. When you start doing partitioning like that and then saying, okay, these are my high memory servers and these are my all SSD servers. And I don't want to provision workloads on an all SSD server, they don't need the SSDs. But all of a sudden you start getting a lot of fragmentation in your data center. And even when it seems like you have a lot of servers, it's very easy to quickly run out of capacity for that flavor or type of server you need. If you don't have really good data, not only real-time data, but also the ability to see trends and things like charting time series, but also beyond the run regressions to say, am I on track to have enough capacity three weeks from now? Because then remember, if I need 10 more servers or 100 more servers, you don't always get those servers instantaneously, you call a vendor, and at best they'll FedXU servers in a couple of days. That doesn't always solve, if you have an outage that you have to solve immediately, it doesn't help things. So capacity can be your number one source of outages if you're not careful. This is not advancing. 15 second rule. Okay, thank you. So I mean, I've been talking about this all along, but you know, and our Manosca. So Manosca basically was a lot of custom code that we wrote in our public cloud to solve all of these real-world problems. And then we open sourced it and made it part of the open stack Big 10 and it was accepted. So it's officially part of the open stack community. But I believe that HP is one of a subset of companies that are actually offering it as part of our distro, even though it is part of the open stack community. So it's a great way to solve these real-world problems, but it's also not heaven or lock-in. And because Manosca is very configurable, in general it ties into all the open stack services via RESTful APIs, and so it sees all the services. And then you can also configure on two nets so that you can get more data on the services that you care the most about that are most often having issues or are changing the most. And then you can have robust alarming to let you know when there's a problem. And you can of course tie this in via via the RESTful APIs to something like a pager duty or some kind of external service to let your IT admins know when there's a problem if you want. And then so it's important to remember, even though Manosca allowed us to address a lot of the monitoring issues, that we used to use Solometer for, but it wasn't working well, Solometer hasn't gone away. So Solometer is still very useful for things like showback and chargeback and in general, usage monitoring or metering rather. And so just remember that these two things work together and they allow you to solve different real world problems. And it's also important to remember that, as I'm doing things like adding compute nodes or I'm upgrading servers, it's important to know did something go wrong? So do I need to roll back to the previous kernel version on a compute node? Do I did? Did a certain push of a Python package not work? I need to push it again. When Manosca will soon be able to allow you to see those lifecycle events of your cloud as well as general things like health checks and capacity and also log data, which is critical for things like compliance, among other things. And then on top of all that, you'd say, well, the IT admin, certainly in the VMware world is used seeing a nice GUI, good visualizations and realizing that many of the same IT admins are now the ones running in the OpenSat cloud, not always, but sometimes. HP has built in graphical front ends so that you can see this Manosca data for things like time series visualizations, but also more granular data as well. And let's get that slide, I think it was kind of redundant, to be honest. And that's redundant as well, to be honest. But in general, Ops Console is a great way to have a portal into this data. And I will stop there. Again, bear with me, these are not my slides, but I hope it was useful. I'm not seeing the slides and doing it in not five minutes, but close. Do you have questions about Manosca monitoring, at scale, life cycle management, anything else OpenStack related? Questions about HP, working at HP, lifestyle in the valley, I don't know, whatever else. Any questions, guys? Okay, oh, there's a question. While you're answering, we're gonna have Daniel setting up. I was just wondering how stable is Manosca, and is it in deployment in production right now? It is very stable. I don't know which of our customers are referenceable, but we have some very large customers, including some government agencies, as well as some large telcos that are using it in production today at pretty large scale. I mean, remember that this is using the, I won't say exact same because we've obviously evolved it, but it started from the exact same technology we were running our public cloud on, which at the time was about 5,000 to 6,000 servers. And it's important to remember that although, there are public clouds out there with more than 5,000 to 6,000 servers, we were running this as a single control plane. So most of those other companies get hitting larger scale or start using cells and ways to fragment it. So the fact that we took the technology that could run a single control plane at that scale, and had been now evolving it for the past five or so years, you know, we proved in our own public cloud, we're proving it in some pretty large customers now, and I would definitely recommend it. Okay, thanks. Any other questions?  See, this one evolved from your public cloud experience, but right now from HP perspective, it started evolving to like a more about a private or hybrid cloud, right, from the business perspective. So how much, you maybe share, is there any difference over there about whatever's from operation perspective or this technology perspective between you treat the private, hybrid versus the public cloud basis? Tell me if I'm not understanding the question right, but I think so you're basically saying across private, public, and hybrid in the middle. Yeah, maybe the behavior will be different and the monitor matrix will be different. And maybe because right now we try to evolve from the matrix monitoring to life cycle management, apparently from the hybrid versus the public, the life cycle management will be different or there's some difference over there. So how you evolve this kind of a tooling because right now you can start to contribute to open stack. So will this one be, I would say leverage the component you learn from your hybrid cloud basis as well and contribute to the open stack as well? Yeah, I mean, so first of all, you know, it's important to, so when you say public, I assume you mean as a developer, I want to create VMs in a public cloud and somebody else is running that for me. Assuming that's what you mean, you know, a whole number of problems go away. I don't care about capacity anymore. I assume that AWS or Azure or HP is going to figure it out behind the scenes. So, you know, in capacity management, health of the control plane, I don't care about that. I, you know, in many ways it becomes things become simpler as you think about public cloud. As long as you have a way to know that, you know, are my VMs healthy? That's usually when I talk to most customers in the context of public and also hybrid, the things that they care about. So in many ways, I would argue the private cloud is the most complex scenario. Even though from a topology perspective, it seems like the simplest. Did that answer your question? All right. So our very last one. Thank you. Nathaniel is going to rock the house with and come back really strong after completing his Windows update over the last 40 minutes and scaring everybody, but he's ready to go. As soon as it, and mine are timed. Do you guys want to switch his? Okay, great. So my name is Nathaniel. I'm a security engineer with Hewlett Packard. And I just want to say thank you for being here. I'm kind of impressed that there are actually people in the room right before the party. So my slides are timed. Hopefully I'm going to let them see and I'll get you out of here. So I am a security engineer and I think I personally am the least interesting part of this presentation. I don't like to talk about myself. So I'll jump into the technical details. I sort of like an open stack to a bag of Legos. You can take all these different parts and customize them exactly the way you want and build exactly what you want with it. There are some caveats that come along with that. Security is usually done per project and it is up to the security experience of the project to handle it. So the open stack security project was created to sort of shore up some of these problems. But they, again, take sort of a specific project by project view. And we're adding to the assurance. I am a member of the security project. But it's not really a holistic view. So if you don't know what you're doing, it can be one of those times where you step on a Lego in the dark and if you've ever done that, you're sort of hopping around and you're wondering if there are any more and it's just going to be bad news. So one of the things that I really like doing in my job is contributing upstream. It's one of the great things I love about HPE that we get to do all of these things. And so I'd like to go over a couple of projects that add to the assurance that we have created and contributed upstream and are still driving. The first one is Leeson. This is a proof of concept for full disk encryption. It does some clever things taking new UIDs and using the inherent ideas of TLS and user validation to transfer keys across the network and protect either bare metal or VMs. I personally am the lead on the open stack security guide. So I'm trying to get you the best information about security for your open stack cloud as possible. I've written a couple open stack security notes, the pragmatic use of security. And if you have not, we just got an open stack blog. I highly recommend checking it out, a security blog. Our British contingent as that's Big Ben has created a tool called Anchor to handle sort of the problems that come with handling PKI at scale and some of the inherent problems with revocation. And so we have this tool to automatically do those things. Our flagship is probably Bandit and they're in I think about 10 to 15 gates right now but it's a security tool, a static code analysis tool for Python. And it's useful for open stack and outside of open stack. So those are sort of what we do within the upstream community. And for those non-Americans, this is the sales guy who says, but wait, there's more. One of the things I really like working about and I feel it Packard I mentioned, I mentioned the upstream, but we also have this entire portfolio of market leading products that we can leverage. So where we run into architectural difficulties, we're able to take in many cases best of breed products and put them in, the first one being tipping point. So I actually, because I'm here, I'm not at the one that talks about tap as a service but it's new. So your IDS, your ability to monitor events at the edge and the management to look for these types of messages is not quite there yet. And of course that all feeds in to ArcSight. We have Manasca, it's fantastic, but log management is not security event management. And ArcSight can help you with the whole security response process. If you've never used this tool and you like Legos, it's a fingertip saver, I promise. Other than that, we have Fortify. So I mentioned Bandit and Bandit is fantastic for Python. We have it in the gate, but Fortify is gonna help you with everything else. So that app that you're deploying with your OpenStack Cloud. If you make tweaks to Horizon, Fortify is gonna be able to look through it and tell you some of the pain points there. I am from Seattle, so this is my personal favorite slide, the hipster barista, but Web Inspect is going to be able to give you the sort of that outside view. It's going to be able to scan your API endpoints. It's gonna be able to scan your application and tell you what your attack surface looks like from the outside and give you some idea of where you can harden that infrastructure. And then finally we have Data Security and Encryption. Things like ESKM, it's Hall of Voltage. I mentioned Leeson, but it's a proof of concept at the moment. If you're not wanting to do those key management things, we have some products that we're working on integrations with right now. And so it all adds up to this hardened edge, this fortification that can be your cloud. It's so cool that a spaceship has to come and check it out. So both contributing upstream and across the portfolio, we are working to make sure that everything is in fact awesome with both our products and what we're contributing. And we want to continue to do that and continue to drive those various projects. And I'm sort of stalling for time because this is my thank you, but I actually have one more because I didn't know you were gonna hard cut me off. So thank you very much for your time. I appreciate you being here. And I will take any questions and get you guys to the party. And I know we're a bit over, but I really appreciate that coming back. Oh, there you go, very strong. Questions, guys? Anybody, to anybody else? If not, then have a great party. Thank you so much for staying for this forum and hopefully you enjoyed it. And we can't wait to see you next year.