JSON is amazing. It's considerably less verbose than XML, which it has largely replaced at this point. It is considerably simpler than CORBA, which is a massively complex beast. It's so simple you can put it on a business card. The entire specification will fit on a business card. It's even an ECMA standard. This is amazing. This is a very lightweight simple data exchange format. More people should use it, right? The only thing about amazing about JSON is marketing. JSON is a brilliant case study in how to market something.  JSON is the de facto standard when it comes to un-serializing and exchanging data in web and mobile programming. But how well do you really know JSON? Really, though? How well do you know it? This guy is brilliant for doing this. I thank him so much for this. I'll have a link to this. It's a pretty simple link anyways. But I'll have a link to this down in the video description. I would definitely encourage you to read this because he does a great job of breaking down why JSON is remarkably unreliable. But let's talk about a few things that I definitely recognize are issues from my experience. There isn't actually a JSON version or definition. It says whatever it is in its current form, that's it. This is a really bad idea for numerous reasons, especially if you have two servers out on the internet talking different versions of JSON. That's an incompatibility. And because they have no negotiation for that version, they just assume that they're both working with the same one and that's not necessarily the case. Now, it is a good idea to constantly update your software.  However, realistically, I know that's not always possible and it may even just be in a situation where, like, you update a week after the developers updated it. But during that week, you have incompatibility issues with people who have updated before you. You can be on top of updates, but this versioning issue still can rear its head. But then, as he points out, there's actually a few different versions of JSON. You have the ITF RFC 4627, the sort of a definition in ECMAScript 262, there's the ECMA 404, the IETF RFC 7158 and 7159, which granted the differences between 7158 and 7159 are basically non-existent, but we are dealing with differences, important differences. But also, and I'm really glad he pointed this out, the goal of JSON was basically to just be a subset of JavaScript to use JavaScript's object notation format, that's where it gets its name, JSON is JavaScript Object Notation, just to define objects in general. But it doesn't actually do that. And it's not just limited to what he points out here, but like he points out, there are unicode line terminators that are allowed in JSON, but are not allowed in proper ECMA 262, which is JavaScript. So that means that even a proper JavaScript object cannot directly be put into JSON, because it's not a true subset. And he goes on to define a bunch of tests and how he's approaching this and whatnot, things that should be supported and all of that, things that should not be supported, but wind up getting passed correctly and talks about some ambiguities, because that's important. Ambiguities mean that implementations are not going to work all the same way. So this is really what we're interested in here. This is the, wow, this is really hard to see on FHD. 4K is lovely for big things like this, but I'm not going to upload a 4K video that takes up so much space. This key is what we're going to be interested in. The blue stuff is ambiguities. That's not critical, but is really not something you want to see. The yellow stuff is fundamentally incompatibilities when things that didn't work the way they're supposed to, according to the JSON standard. And red is just an implementation issue. The parser itself crashed. That's a bug that needs to be fixed within that parser, but that does fundamentally contribute to the incompatibilities between these implementations. See, there's a heck of a lot of blues. Again, I encourage you to look at these, because I'm not going to go through and explain what all of these are, but there's a lot in the way of these. We'll call them irregularities, but even when we delve down into the other tests, you'll see any specific test case. Most of them will pass it correctly, but there are these odd irregularities in how they handle it. That's a problem. The whole point of something like JSON of XML is to take a complicated object that cannot be easily represented. An integer is pretty much an integer. You have a few things like little-endian and big-endian issues, but those are pretty easy to deal with. When you have more complicated things, records are even all the way up to complex objects. God, the idea of trying to send a container through JSON to another machine scares me. Having seen these issues, I expect that container to be completely messed by the time it gets sent to another device. This really hampers the thing that JSON was meant for. If you're using it to save a program state, that's fine. You're using the exact same parser slash generator to generate the state, save it to a file, and then to load it back at a later point. A lot of programs nowadays are starting to use JSON for settings. VS Code is a prime example where the entire settings configuration is just done through a JSON file. I have no problem with using JSON for that, although an INI or similar is usually enough to get the job done a little more appropriate than that. Using JSON for that is fine. I have no fundamental qualms about that. But using JSON for actually transmitting objects between devices when you're doing things like distributed computing or whatnot, after seeing these results, I definitely feel that it is not appropriate to use JSON for these things, because there's just too many incompatibilities. So I hope this video helped. It helped you out, especially if you're developing a distributed system. Know that you are going to have a few headaches down the road, and you should really test against a large number of JSON parsers to make sure that your stuff is working correctly. You found this video helpful, and I really hope you did. Give me a thumbs up. If you like my videos in general, please subscribe. I'm constantly putting out new content, but the subscriptions helped me out quite a bit. Have a good one.


Welcome. This is the Jenkins Platform Special Interest Group. It's the 21st of December. Thanks for being here. Topics I've got on my list, action items, Windows Docker images for LTSC 2019, the master branch, and I'd like if we have time to review a draft of the JEP that I've created in a Google Doc trying to get some progress on that Jenkins enhancement proposal. Are there any other topics that you'd like to bring to the meeting? Oh, actually, there's one that I want to bring. So on new arm images or new arm servers at Amazon. So a topic from me. Any other topics? Okay, great. So I have the action item to open a JEP for Docker operating system support ongoing and finally started the evolution of the document.  A few weeks ago, we'll review that later today. Sentos options for adopt open JDK. So Alex, you've opened a PR for this. Thanks very much. Could you share with us what you learned from that PR? It was pretty easy. I mean, it's basically just adding in the adopt, adoptium or adopt open JDK as it was previously called, obviously, repo. And it seemed to install the JDK just fine from adopt open JDK. I think it did have to add. So the free type and font config libraries are required because it's not a headless JDK. I don't think adopt has a headless option. So those were additional libraries. That'd be you say free type and font config. Ah, okay.  Got it. Okay. Excellent. So that one, now the that would give us instead of relying on the Sentos based JDK, we would then rely on adopt, the adoptium JDK. Correct. Nice. Okay. And I saw here that it's using JFrog.io. So that's the official, that's their official yum repository for adopt open JDK. Yeah, that's from their install page. So you go to their install page. It basically says to do this exact operation. Obviously, it's not, they're not saying doing it in a Docker file, but I just adopted the procedure and put it into the Docker file. Excellent. I can link from there or link their install page to the PR just so people can see it. That's great. Thank you. Okay. So that would that would shift us so that we would then be using adopt open JDK for Alpine, for Debian, and for Sentos. And Windows. Oh, and Windows. Right. Right. Exactly. This is the, this is the one remaining platform not using adopt open JDK. Okay. Good. Excellent. Thank you. Thank you. So in terms of communicating that change, is there anything we fundamentally need to communicate and do we have a vehicle to, to communicate that? I mean, there's nothing that's displayed to users when they run a new Docker image, they just get the new image, right? Correct. So I'm not sure if there's there's something we need or can or want to do. I know that it's mainly for running the controller. So part of me says that we're just packaging our recommended JD or JDK with the controller image and it'll work, you know, regardless, but maybe we do need to let people know. I'm not sure. People are hopefully not doing builds on their controller. So. Right. Okay. So now I, I saw that looking back in time earlier today, I saw that Oleg had used a place to tag when he rolled us to Alpine 3.12. Would we be willing to consider, or should we consider tagging and using GitHub releases, even though they don't fundamentally publish anywhere? Just in general, you mean? Yeah. Wondering in the general case, not as, you know, so, hey, we're going to drop Debian 9 support in the not too distant future. We're going to, and that will need some way of saying it. We could use a GitHub release and a tag or we could do some other notification, blog post, whatever. Yeah, I think that sounds good. I mean, maybe it's, maybe we should do tweets on the Jenkins release. I don't know if there's a manual way to do tweets there. I know there's not, there's automated tweets, but yeah. Does that make sense? So that one I didn't quite understand when you're, you're suggesting tweeting that, that we had done the release? So there's the Jenkins release Twitter account. Ah, okay. That has, that does the tweets when they're like plugin releases and stuff like that. I'm not sure how we would do it like an automated method of doing that, but I think we kind of your quote unquote releases infrequently. So it might be easy if we just did a manual tweet every now and then, but I don't know that I think anything just letting people know it's fine. Okay. I think, I think I'm understanding what you're suggesting. Good. All right. Yeah. So that one, I'm not quite sure how to do it, but I think it's worth consideration. Certainly we can consider a blog post for large, larger changes like Debian nine to 10 grade, et cetera. So that one feels like anything else you wanted to share on that. Sorry, I think I'll came through. No, nothing else on the, on the system. Okay. All right. And plugin installation manager and update center. I like, I like your suggestion from our last meeting that we would consider doing a shim replacement of install plugins.sh. You warned that there may be some, there are some behavioral differences. Are those a grave concern for you or just needs exploration as part of, of this proposal? I think it just needs some exploration. Basically that what we could do is create the shim and then just run the normal test cases that we have and see if they pass or not. Right. Okay. I can take a look at that. Okay. Great. Excellent. Okay. And then we had a topic there on refinements for parallelization and multi-art CI. I assume this one is delayed while Jim is on other projects. Yeah. We're a month or more. Okay. Great. All right. So next topic was Windows doctor images for LTSC 2019. Gareth, do you want to take us on a tour of current status? Yeah. So the images are all there. We're only building JDK 11. And we started to have an official release of adopt open JDK on that version. So that's okay for the time being. In terms of the agent images, there are two open PRs for, they just need reviewing to add JDK 18. And that should be for the docket agent. And I think it's the SSH agent. And then the other one is the docket inbound agent. And that requires some... Well, the current pattern is to use the versioned agent release that seems to be built off the tag, which we're not getting for the newer images. And I'm not entirely certain of what the best way forward for that is. So we did this way. Go ahead. Sorry. I'll ask my question after you've finished. Excuse me. Yeah. So the build that is the tag that was created that's been built on trusted.ci, which is 461 of the agent, that doesn't contain any of the LTSC 2019 images. So we're not getting the builds for those, or sorry, the docker containers for those. I think what we need to do is do a release on the GitHub side. And then a tag will be created that we can... Actually, it was 4.6.1. Yeah. There is a tag. So while Alex is doing that investigation, I need to be sure I capture this because I'm still learning the structure. So we've got a docker agent repository that is the base image. And then we've got inbound and the docker SSH image that are both derived from that image. Is that correct, Gareth? Or could you describe that a little further for me? The SSH image is not. Oh, it is not. Only the inbound. I see. Okay. All right. So the docker inbound agent pull request Gareth submitted is for the base image for the base image. But the issue you found is it does not yet include somehow it doesn't yet include the LTSC 2019 images you'd proposed. Then there's the docker inbound agent image. So it's that pull request that's currently... That's failing at the moment because the base image is that it's depending on don't exist yet. Okay. And this is one where we don't... Okay. Right. Good. Okay. The 4.6-1 tag is building on trusted. I'm looking to see why it's not pushing those images. I was assuming it was because when the tag was created those images there didn't exist in that build. Well, I'm looking at the docker agent one. So it should be pushing whatever it's building. Except I thought that if a tag exists already we didn't do a repush. We would only push a tag once. In the docker, the agent ones, we don't have the same... Oh, we don't. No. We don't have the same scripts or anything like that. It just always pushes. So yeah, when I was looking when I was looking at the logs for those today, I can't see any LTSC 2019 images being built at all. Yeah, that's interesting. But I can from the mast of it. My guess is that... Yeah, so 4.6-1 was released on November 4th, which was way before these new images. So we probably just need to do another dash release on GitHub and then we can create a new... That will create a new tag and we can build that tag. Okay, and the way we do that is go into the GitHub repository for that and just apply a tag and declare it a release. There's a draft one that has the commits like the one from Garrett and some from Victor Martinez. So we can easily do a release. I can do that. Oh, okay. All right. Great. So and that's in the docker-agent repository. So we probably want to get the JDK8 versions and that for those. Oh, before we do the release. Okay. So we've got... There's this poll request here that's still pending before we ask for a release of this. Okay. And Alex, are you okay with my answer on the why we're proposing JDK8? Was that okay for you? Oh, you did. Oh, good. Okay, great. I just barely merged it, so we're good. Excellent. So I'll do a release there and then make sure it builds on trust. Awesome. And so Alex, help me with the version naming. So this will be a 4.6-2? Correct. Okay. And do those versions, do those releases already include descriptions in the... Are we already using... Oh, yes. Okay, great. So it's already using release rafter. Okay. Okay. So Gareth, what I think I'm then understanding is once we've got 4.6-2 tagged, trusted CI will detect the existence of that tag and will apply it and push those images and that should include the LTSC 2019 images as well. Or did I misunderstand? Yeah, I think that's the four. We should get the Docker agent 4.6-2 versions up. And I'll probably need to just rebase my PR on the inbound stuff because, yeah, with the right version. So that's cool. I'll watch those and yeah. I think I have three open PRs. One is sorted now. I don't know how to fix it. Let's just check it out. That's cool. Great. I got a 4.0.4 while doing the release. Let me check the connection. Okay. I'll fix it. Nice. I did a submit and it said 4.0.4. Oh, ouch. I need to remember to always copy and paste my release rafter and stuff somewhere else. Oh, and we've got one other person who's interested in joining this session. My apologies. I had missed that. And that's awkward.  Just a minute. Let me be sure that I get her the meeting invite. See participants, invite, copy, invite link. 4.6-2 is released on the Docker agent repo. Once the tag shows up, I'll verify that Trusted sees it and we can build it. I don't think that tags are automatically built on Trusted. So just as an FYI, and if you ever do this, you have to go into Trusted and verify that the tag is built. I'm not sure what setup we need to change to fix that. I assume that's likely because Trusted doesn't receive any GitHub notifications. Any, what do you call them, webbooks? Yeah, it has to go do a repository scan. Right. Okay. Yeah. Now, that I think is a separate topic, but there have been some discussion. Trusted is used to build the Docker images because of the credentials required. Is that one where we would be willing to consider possibly in the future moving it from Trusted that's behind that SSH tunnel to Infra that's on the VPN and not behind the tunnel? Or do you have a strong feeling that no, it really needs to stay in Trusted? I have no personal. Okay. So you're open to either. Yeah. It would probably go to release it, wouldn't it? Oh, right. Right. You're correct. Release.ci would be the more sensible when because we use it when we deliver releases. Yes. But it would make sense to still have it behind probably behind the VPN or something. Have it protected in some way. Yes. Let me just make a note of that here in the notes that yeah, it's this one. Consider moving from Trusted.ci to release.ci. Simplify Jenkins releases, wider access, easier to diagnose, and no less secure deliver a Docker image than a Jenkins release. And I mean, there's it's Jenkins releases just as just as security sensitive as a Docker image releases. It's releases. Just releases.ci. Jenkins.io. I think it's release.ci. Jenkins.io, but you've got to be on the VPN in order to see it. Yeah, I'm on the VPN. Maybe I don't have access. Yeah, that I don't know. I would think you should. But well, then again, Olivier intentionally limits who can access release.ci. Jenkins.io to a relatively narrow group. If we were to move Docker builds there, we would need to grant you access to that. It certainly would make sense. Okay, so we've got anything else with regard to Windows Docker images. We've got the 4.6-2 release that is has been released just now. And Alex, you'll watch it on Trusted.ci. Is that right? Yeah, I'll make sure it gets. Okay, great. Thank you. I think that covered that covers the Windows Docker images then. Anything else, Gareth, on Windows Docker images? Oh, that's everything. Okay. All right. Last month or last two weeks ago, I had asked about ci.jnkans.io master branch Docker image building. The job's been failing for a while. Alex, do you have anything you wanted to share on that? Is that still a reasonable goal? Yeah, we definitely want to do that. We can disable the experimental publish if we want. I think I'll go ahead and make a PR for that. And then we can just do some work on some PRs and stuff, because I think all three of us have access that our Jenkins file changes might get pulled in. Okay, great. So you don't object if the experimental... Oh, good. Thanks, Daniel. Yes. Yeah, absolutely. Good point. So we can use pull request to allow us to further adapt the build process. Okay, good. Daniel, thank you for joining us. Anything else you wanted to comment on with regard to the future potential? No, this is... We will certainly use a plan. We will certainly have that discussion in depth to be sure that we don't trample on the security build process. Not really. I think I recently saw a message around release CI failing because it couldn't install plugins. Might have been in the Infra IRC channel. If that is the problem there, we need to be mindful that we're not ending up in some sort of... What's the term? Where one part cannot be repaired because another part is broken and vice versa. Just stuff like that. But otherwise, we need to be prepared how to handle outages of various sorts. Otherwise, I don't really have an opinion. Right now, what happens is, before we publish security advisories, I make sure that all of the updated components can be downloaded, which means packaging for regular Jenkins Wars, the plugin HPIs, if any, are included, and as well as the Docker images. And notably, Docker images are required because I update CI Jenkins IO before I announce the security fixes in an advisory. And CI Jenkins IO needs to be online for the site build or trusted CI to work. So there's even a dependency chain in the content publishing process there. And any changes here would need to be mindful of these dependencies. So if Docker images cannot be delivered, I actually cannot really publish a security advisory. And my preferred solution would be if we had Docker image staging and just would need to copy them from the staging repository and artifactory over to Docker Hub or wherever. That would be ideal because then even broken builds are not on the critical path on release day. But otherwise, no comments from me.  Is that one that you would, would you be willing to have a further conversation with that either today or in a later session? I'm interested in that. It would mean, I assume, changes to our Docker build process, but we're already building the images ourselves. And I think we intend to keep doing that because we need control of the images. So that seems reasonable. Alex, any insights from you or Daniel, first question to you? Is that a topic we could discuss in more depth? I would be very happy to discuss this further. But as a quick note, I've talked about it in bits and pieces with Olivier in the past. And so far, I think it's been mainly a lack of capacity that prevented this from happening. But the staging that we're doing in the regular core build process works pretty well. We've always done staging or at least for many years there, we were staging plugins. And right now the problem is on release day when I want things to go out quickly so that I can quickly release the security advisory, the need to build the Docker images immediately then still add some degree of uncertainty and fragility to the process that isn't really inherently necessary. So yeah, I would be very happy to talk to you about it. Unfortunately, I'm not that well-versed with Docker repositories, images and such. So I don't know how much I can contribute in the implementation there. So I think what I would like to do then is I'll schedule a session for deeper discussion because it feels like we need Alex, Olivier, Gareth, Daniel, anyone else that needs to be involved in that discussion? I'm not from security, so I don't know. Okay, great. Alex, insights from you, is that are you okay if we have that discussion? And it feels like another thing along the line of the Docker image build improvements that we've been envisioning with Jim Crowley. Yeah, I agree. Okay. Oh, Tim, yeah, that makes sense. The release officer certainly should be involved. Okay, good. All right. Thank you, Daniel. Thanks for that quick trip back. So then the ci.jankins.io master branch. Alex, anything further there? Oh, go ahead. Yes. So I did reach out. So this is somewhat related. It's Docker security stuff. I reached out to the Docker library folks about the Jenkins repository, the quote-unquote official Jenkins, not our repository. And they removed the latest and some other tags. So Daniel, if you could take a look and see if there are other specific tags that you would want to remove. I asked them about removing the repository completely, and they said that that's generally caused issues in the past. So they were very hesitant to do that. But they were willing to remove tags. So I don't know if the old versions on there are fine to keep or if we want to just whack everything if possible. I'm not sure if removing all tags is possible or not. To clarify, if the latest tag doesn't exist, then I need to explicitly specify a version where I poll, correct? That is correct. All right. And I think that's enough of a speed bump. So I mean, Dr. Paul Jenkins on the top right there is the copyable command that would break them, correct? I believe so. I believe it will. Yeah. I think that's enough of a speed bump to make people look at the page. And it has the giant all caps deprecation notice. I think that should be good enough to make them think twice about using the images there. Thank you very much for doing this. Yeah. Thank you. Well, and looking at the latest is 2.60.3. So it's only, what, four years out of eight now? Yeah. The last time this repository was updated was two years ago. So they were, and I just tried to do a Docker poll Jenkins, and it did say manifest for Jenkins latest not found. So it definitely will cause an error if they copy that command and try and run it. Yeah. So one thing that might be useful, and I mean, that may go too far into the weeds here, is to explain as part of the deprecation notice that this hasn't been updated in several years by now. Because the way it is phrased, unless you know what Jenkins versions mean, this could have been deprecated yesterday. Right. Well, and if we're asking them to make an edit, we could ask them to delete the reference to the latest tag, because it no longer exists, and we like that. Yeah. I think you'll report that we can just follow poll requests too. Is that correct? Well, yes, but there is no Jenkins directory anymore. So that's why it's not been updated in two years. So I need to go back and look at the history to see why or when that Jenkins directory was removed at least. Okay. So have a bunch of directories and each directory is basically an official image. So I'm not, I need to look at the history and determine when that Jenkins directory was removed. Yeah, but not having the latest tag basically means people won't be able to just use it like they use absolutely everything else. So. Right. That provides a safeguard against blind consumption, right, about silent blind consumption. It's like, no, that doesn't work anymore. It just won't work for you. Great. Anything else on that topic, Alex? Sorry to kind of hijack that a little bit. Oh, no, that was great.  Thank you. All right. So we've got the agreement that we're going to work on getting ci.jankins.io master branch working. Anything else on that topic? Okay. So then next topic, and this is a precious, I propose we will stop it in nine minutes. So let's use the next nine minutes for this specific item. I've got a draft proposal for, I'd like to change how we manage Docker images process wise. And this is my draft proposal. I wanted to bring, it's particularly valuable, Alex, with you and with Daniel here to see, hear your inputs, get your comments. Oh, this is crazy. This won't work, et cetera. So the idea I had was, let's attempt to use, have our Docker images be treated closer to the way we treat plugins in terms of their management processes. One of the concepts is the notion of adopt an image. So we have adopt this plugin. I think we ought to use GitHub code owners to assign owners to specific images in the Docker image repositories so that we know who is caring for a particular image. Thus, for instance, for my needs, I would ask to be one of the owners of the Debian repository and the Alpine, but I would not ask to be an owner of the Sentos repository, the Sentos files, because I'm not maintaining them. Go ahead. So if an image does not have a code owner, would it be an unofficial image? I was thinking it would just be up for adoption. I wouldn't demote it to unofficial. I would just make it up for adoption. But I'm open to arguments either direction there. I was, I didn't want to, with this proposal, change the status of the existing images dramatically, but I'm open to that suggestion. I thought up for adoption was a safe enough concept that it would allow people to continue using the images that are there, but knowing that, hey, this does not have an active maintainer on it. So Daniel, any insights from you there? Does the concept of up for adoption seem like it could be applied to this? Anything you've learned from the security perspective that we should be mindful of? When I look at plugins, it's fairly easy to tell whether they are maintained or not, because they are independently released. If there hasn't been a release in one, two, three, four, five years, the chances increased substantially that nobody's home. But that does not apply to Docker image variants, unless there is something incredibly obviously broken with them, because it is, to an extent, the reasonable decision not to track upstream very closely or automatically. And so how do you distinguish? Well, the base image hasn't changed in a few months from nobody's maintaining this anymore. And people do not announce when they leave, at least the vast majority don't. Some well-known contributors in the community like Nicola, Grigory, Wasseno, or more recently, who am I forgetting? Not Chris. Chris is still around, but Swiss guy. Sorry, don't remember the name. They announced they were leaving and we're looking for new maintainers for their stuff. I would not expect something similar to happen with these images. So they would have a declared maintainer, but maybe move on, lose interest, and nobody can tell. So Dominic Bartoli, I think I'm thinking of, who recently announced he no longer has time. And I'm not sure how to, I agree. I think that's a valid point. Plugins, it's obvious because there is an explicit release and the absence of releases hints not an inactive maintainer. Any suggestions on things that we might use here where we've got, what basically is a monorepo for all the Docker images intentionally so, but we, would you consider, could we consider separate releases for individual subsections? I'm not sure how to. I don't know. I'm just, thinking about what I've observed, trying to reach out to maintainers after four years of nothing. And some were like, yeah, sure, I will help you, but I have no idea how to release anything anymore. And some, well, email spawns. And there's the full spectrum there. And it's also, if you use a plugin, you have a relatively easy time to tell in Jenkins that you're using it. That is less the case with Docker images or packages. You've set it up years ago. And since then, I don't know. I'm lucky enough that I don't have to care about it because Olivier handles that. But I think there's also this situation where someone set something up far in the past and nobody knows how it works. And I think with more the system level configuration, I think as a user, the expectation for me would be that there is a fairly clear distinction between what's supported and official and what is not. Obviously, in the Jenkins project, that distinction may not make a lot of sense. But yeah, I'm just not sure. I'm sorry, I can't offer solutions, only problems. Actually, I think you lobbied towards one maybe back to the idea that Alex had offered, that maybe we should, as part of this proposal, it's a significant enough proposal, maybe we should declare if at, if when we implement this proposal, a Docker image does not have a specific code owner, maybe we do mark it as not mark it, we actually demote it back from the Jenkins org to the Jenkins for eval org. That would break people, but it would make it very clear that this thing is not a maintained image. But that's pretty dramatic, right? That will break people's Docker builds. Did I, Alex, did I understand your proposal, your suggestion correctly, or your question correctly? Yeah. So the idea would be we have a set of specific images that are official images. Those are the ones that Daniel would have to care about when doing a security release. So we'd want to keep it fairly small. And then we have other ones that are unofficial that are, you know, whatever anyone wants to put in there, right? I don't know if that meets security requirements, because if people are relying on them as quote, unquote, official anyway, and it's still a problem. That was kind of my thought was to reduce the number of images that Daniel has to care about for security releases. Right. As long as we tell people upfront what is properly integrated into our release process and what is not, what we care about and what we don't. And I think that's, that gives users, or that gives, it gives admins the necessary information to judge for themselves whether they really want to operate Jenkins out of, I don't know, there some weird distribution like send us six or whatever, when there may not be any security updates afterwards. That makes sense. Okay. Thank you. Yeah. All right. So thanks very much. The already the insights of I had, I had not considered the security implications of this JEP. So Daniel, thanks very much for your insights here. I will certainly copy you on the link to this and get further involvement. This is very much in a draft state right now. I intend to keep working it trying to look at various compromises and alternatives that are hiding an impact of proposals that are happening in each of these. So that the up for adoption proposal versus the become become an unofficial image. And I think the place I'm supposed to put that is in the motivation section, or there's another section that describes about alternatives and why they were not selected. So I'll continue working that through the JEP process. So one potential problem here or something to be aware of is while this problem exists elsewhere in the Jenkins project in terms of plug-in support in a way, it is less noticeable due to the support cloud B is offers to its customers. And the benefits that users of the open source plugins have just because club B supports them for customers. So security fixes are made available to anyone the same way they are made available to club B's customers. So and all of the popular plugins are supported by club B's, which means in Jenkins for Jenkins core and a lot of the most popular plugins, they are effectively security supported by cloud B's. And only the less popular plugins typically are supported. However, the maintainers wish to support them, which is a very wide range. And for the Docker images, since club B's products are packaged independently, it is purely community support in a way. So we try to get stuff fixed there. But there's not really this corporate entity that directly supports it. And so this is sort of this weird situation here. And also why this problem feels like it should have come up in the past. But in a way, it didn't. So this is really a new problem where we would need to figure out what does it mean for something to be supported or not, or to be in scope of the security team or not. Right. Well, and I think your example of cloud B's probably also applies to Red Hat, right? In their open shift distribution, don't they deliver a Jenkins component, which is probably Docker image based. So it's it's even not it's the same class of challenge there where we've got the community is doesn't have at its at its foundation or at its base, also that cloud B's is doing it commercially or Red Hat is doing it commercially and using these exact images, right? There cloud B's uses a different image. And I suspect Red Hat creates their own image as well. I don't know how Red Hat does it. So previously, Oliver Gonja, a release officer was a member of the security team and had the necessary access. I don't know whether he was working with OpenShift folks, but they have never directly engaged with us. And right now we have nobody from Red Hat on the security team. So they are probably just downstream consumers of what we deliver. But if they consume basically the war and the plugins, then they benefit from the security fixes we deliver there. And if they do their own images and tooling around it, they are independent of what we deliver in terms of Docker images. Right. Okay. Thank you. Okay. Good insight. Anything else on this topic before we conclude our session today? Oh, I've got one more topic. Sorry. Before we end, next meeting. Next meeting would be scheduled for what day it would be scheduled for? January 1st? Oh, that's a bad day. We will cancel. Next meeting canceled. I am not going to rouse myself out on a bank holiday to do this meeting. Anyone object to that? I think we should just do it earlier at 12.30 a.m. Everybody's time a little longer. Why didn't I think of that? We will just have everyone join for their new, no, thank you. Okay. All right. So we will meet again on January 15th. Is that workable for everyone? Works for me. All right. Any other topics before we conclude? Did you want to discuss the ARM servers on? Oh, yeah. Actually, okay. One minute, highlight. Amazon has rolled out their next, they call it Graviton 2, I think. Servers are now available. And they've got a promotional period going on where they're giving a deal on lower cost if you use one of those new ARM 64 servers that they've created. Or lower cost. I've been running one now in a spot instance for a week or so attached to my CI server. Works great. So just be aware that newer ARM servers are coming online. And we may, for instance, Gareth, you and I had talked possibly about LTS release candidate test execution. And these Graviton servers might actually be quite interesting as a way to run LTS release candidate tests instead of running them on Intel. They are apparently about 40% cheaper price performance wise. So just for, consider for the future, not anything we need to take action on immediately. Just be aware that Amazon has rolled out even better ARM based servers now. Cool. I have to go look at those. Yeah. I was really impressed. And they offer a discount right now for using them. It's like, well, gee, they're, they're, it makes them really low cost. All right. Anything else? Okay. Thanks, everybody. Happy holidays and a happy new year. You too.


Life is good all this month at Appalachian Wireless. Get the LG G5 for just one penny with sign up or renewal of a two year service agreement. That's almost $100 off the regular price. Better service, bigger savings. That's today's Appalachian Wireless. The win is enough, enough. That's the question many are asking right now. It was announced earlier this week that Kentucky Power is seeking a 17% rate increase. Many are already enduring high power bills and earlier this year State Representative Chris Harris filed legislation to obligate the State Public Service Commission to re-examine Kentucky Power's rate increase cases over the past 10 years. The legislation never got a hearing, but Harris said he plans to file the same legislation again in the fall, especially now that Kentucky Power is seeking a new rate increase. Neither of those bills got a hearing and you'd have to ask the majority leadership why those bills didn't get a hearing. But I filed the bills. They had bipartisan support. We had legislators from all over Eastern Kentucky, Democrats and Republicans, who had signed on to sponsor, cosponsor that bill with me. But we didn't get a hearing. And so I hope and I do plan to refile both of those bills. Harris said he's been contacted by numerous of his constituents who are concerned about the possibility of yet another increase to their power bills. He said he plans to take those concerns to Frankfurt in the next legislative session. This is a high priority because this affects every single household in my district in Eastern Kentucky. So yeah, this is very important to me. It's very important that we let the PSC and the Attorney General's office know exactly how the previous increases have affected the people in Eastern Kentucky and what additional increases would do to the families in Eastern Kentucky. You know, they need to know that. The PSC has to ask itself, you know, when is enough enough and how much burden can you put on a region that is already struggling? You know, there's no question that AEP's finances have been going up, up, up and doing better and better and better. Their stock price reflects that. Their dividends reflect that. But what is not reflecting is the toll that it's taking on the people of Eastern Kentucky. From the newsroom, Chris Anderson, EKB News.


What's up everybody? Jayce here for jayspeakscasebrakes.com. We just sold out 2017 Peony Opulence basketball This is a one box break random teams number two. So again 30 total spots everybody gets a random team in the NBA This is the second Would be the second box out of three of the case so two-thirds left We'll decide which box we use here a little dice roller later But here's a dice roller here for the list of customer names and teams So Eric down to Sean bought those spots straight up and then Lewis down a Lewis down there chronicles hanger number two got those In a little filler break. So there you go Very nice and Hawks down to the Warriors bone and Let's roll it and we got ourselves a two or three or two five times. Good luck One two three four David down to Kevin a real time. What do you mean? You're behind like you're not you're not live. You mean oh Yeah, yeah, I was I was a little while ago. Actually, yeah refresh Three or two five times Let's go five times here one two three four Grizzlies down to the 76ers So David you have the Grizzlies Kevin with the Thunder David Baker you David a was a grizzly David Baker You have the Raptors Matt L with the Celtics Scott with the New York mix Matt L with the Bucks Lewis You have the Hawks Art of the Suns Lewis with the Wizards and Hornets Eric with the Nets Mark Longoria with the Lakers Ryan. You have the Spurs Russell with the Rockets Sean Maddock with the Bulls Lewis with the T-Wills Matt L with the Warriors Lewis with the Pacers Scott Blackwell with the Trailblazers Lewis with the Jats Matt L with the Kings Clippers and Mavericks Darrell you have the Pelicans Lewis with the Nuggets Russell with the Heat John with the Cavs Roger with the Magic Lewis with the Pistons and Kevin with the 76ers So again, if you guys want to trade guys, I will definitely give you guys a quick trade window If not stick with what you got. All right, just let you guys know John already got two spots in the next opulence break You guys want to get the next one rolling out it'll be the last box We will Nick. We usually get all the new releases for most for most sports and we are now officially a predict Diamond dealer, so we will get all those new releases on time. I Don't know if we'll have any group breaks per se, which I think we should We did them for all the other series in the past couple ones So I didn't expect this to but I don't know how much But we would definitely have those available for personal in store and then on our personal side Jasper But yeah upper deck hasn't been releasing as many releases as I As we'd like I feel like panini and all these other sports just knock out crazy releases all the time But I think everybody's kind of waiting for cup hockey, which should be just dropping in that I don't know where either at the end of this month or December. I mean they usually just like that They'll be like cup releasing in a week place your orders. You're like what? So I'm kind of more excited for that All righty guys, so we have two boxes left top or bottom now this time if I roll a one two three We're gonna go at the top four five six for the bottom So doesn't fly this way Hit it off here six one two three four five six So this top box here will be for the last break of opulence No, man. I mean it's usually tradition released at the end of October early November But I think with this pandemic. I don't know if they're a little bit delayed The last time I ever seen cup hockey released in December if it does get to December was McDavids rookie year 1560 I remember released like December 1st or 2nd. Obviously, that's no pandemic. So I Expect them to release it at some point within this month or next month But it traditionally just dropped sometime in the middle of October Like I said, they'll give you the previews and drop the announcement on you It's just like like I said releases in a week or two and then it breaks So yeah, I think people have been waiting for cup hockey Which will definitely have some cup hockey and have a lot of group breaks of that should definitely be fun There you go. Oh, we got two booklets Well first one This little Tatum base. How about that? Very nice Little Jason Tatum rookie base 52 out of 79 Celtics that's going to Matt We got Julius Randall for the Lakers 49 79 Lakers. It's going to mark We have a clay Thompson number to 25 for the Warriors We got a redemption It's Malik Monk rookie autographs, which that should be Charlotte Hornets, right? Quickly the check is really quick Yes, Malik Monk is Charlotte Hornets So again, although this is expired and did only expire a couple months back or earlier this year. So Penini should hopefully still have that Whoa, NBA Finals book like Kyrie Irving. Wow, what a patch Selt it. I mean sorry not sell this Cavaliers edition That is 13 out of 19 and these are player worn during game two of 2017 NBA Finals Wow, man, this was LeBron.  I'll get a little slider box for this right now next one we got His little AC green gold records One out of 49 remember guys, that's the one thing about opera that's besides rookies You know besides vets the NBA Finals booklets in here are super clean There you go. We got opulent scripts Tyson Chandler. That's Phoenix Suns 35 Arthur Hackett with that one. We have a Caleb Swannigan for the Portland Trail Blazers When a Scott Blackwell 36 out of 75 Ooh, wow, look at this Shaquille O'Neal Piece of gold and the auto 10 out of 20 and enclosed is a certified 14 karat gold Gold Mender Gold member would love this. It's pretty cool Almost wrote on the gold. Come on Shaq. That's pretty cool Roger there you go, man. And the last one it looks like it is a rookie booklet and it is for the Knicks Two out of five Nike swoosh and autograph Frank was to Ninka or to Leninga I don't know if this guy's still really good or not, but look at that solid Two booklets in this I've never seen two booklets in opulence before And there you go. That is gonna go forward to the Knicks and Scott So there you go, this is opulent 1718 got a nice little Nike swoosh auto booklet out of five and a Kyrie Irving NBA Finals patch out of 19 Shaq It was even a Tatum base Pretty solid and again guys the last box of the case is Actually, it's over here, but it's in the website number three and again, you can either buy a spot straight up Which it is down to 12 left Or you can win a spot in the filler which is at 28 love to see what's hiding in the last box guys Maybe potentially That man right there USA edition. We haven't had any USA cards So could potentially be there as well and hopefully maybe a big rookie patch autograph We haven't got one of those yet either. So I appreciate you guys Jaspies case breaks calm


I live in a small town in Idaho, and there's nothing out here. The only reason anyone comes to my town is because of this swanky Mexican restaurant we have here. This place is the bee's knees and folks drive for miles to eat there. The food is rad, the service is famously awesome, and they do lots of good philanthropic things throughout the community, so good for them. I applied for a job at this swanky Mexican restaurant. I felt the interview went pretty well, you know, you're supposed to quote off all the experiences you had, your past works and that kind of thing, and I was doing a pretty good job. I was sucking up and all that. They called me about 10 minutes after I got off school, and then they were like, hey, do you want to come down here all dressed up in about 30 minutes? And I was like, oh my god. I mean, yeah, I can definitely be down there and like, right now.  They were literally stacked on top of each other. It then registered my mind as, oh, so this is the kind of company I'm going to be working for. Immediately afterwards, the manager came out to give me a tour of the restaurant. His name was Felipe. Now, the thing you got to know is that this place is 70% dining area and 30% secret corridors and kitchens. Just right behind the main area was all these secret corridors and tunnels for the workers to sneak through. See, I've been going to that restaurant ever since I was a little kid, and I had no idea that any of that stuff was back there. It was super tight and slick too. Plus, since everybody who was working there was running 24-7, it was a fairly spooky place to navigate. As we were walking past the kitchen, Felipe pointed out two 25-pound bags of onions, and he told me to pick them up.  All 50 pounds. So I started cutting. And cutting. And cutting, and every 10 minutes or so, somebody would walk by and go, hey, why are you crying? I don't know, why do you think I am? I was back there for a good five hours doing nothing but cutting raw onions. The point was to teach me how to handle the utensils I'd be working with, however all I did was winding up giving me a bad case of carpal tunnel and making me smell bad. Plus, to remind you once more, I was within three feet of a hot stove, so not only was I smelly, I was also really sweaty too. And this was the orientation I had just filled out paperwork. Now, Felipe, he was an interesting character. He lived and he breathed his job as manager. In my months working there, I never saw him slow down or take it easy once. That dude was like, road running on cocaine. He was always doing a billion things at once, and he did them really well while he was at it. I have no idea how much money he makes, but he was not making enough. He was full of energy and he was really charismatic, but when he got mad, he got scary.  He looked at all of us and he was like, can somebody tell me what's wrong with this salsa? We were all checking it out, looking for mold, but it was just plain old salsa. We all stood there silently and waited. It's not stirred up enough. I don't know who is responsible for this. And if anyone is not willing to fess up, I will blame all of you. Then he walked out and we were all freaked out. Felipe didn't raise his voice. He didn't do anything crazy.  The salsa was stirred more thoroughly after that though, but overall working there was super fun. We held a meeting at seven o'clock in the morning on a Saturday and nobody wanted to be there. Once we got there though, we were given free donuts, coffee, and the time that we spent there was paid too. The meeting wound up being a refresher course for how to properly clean tables. We were expected to remove all the plates and silverware and wipe down every inch of the table in less than two minutes.  Nobody could meet the standard in less than two minutes. And then Felipe was like, lol, hold my beer. First try, he did a better job than all of us and he managed to do it with time to spare. So returning back to the onion cutting, I was trying to be a guacamoleero. I think that's how I pronounce it. I have no idea. I would go to tables and I'd make fresh guacamole for the guests to eat. I followed around my co-worker Jacqueline and I watched her do it so I could take notes. Her and I actually became best buddies. Her and I actually had a ton of stuff in common and I located a crush on her. It's not a big deal.  In fact, you can click my face if you want to see how I made guac. Since I was just staying there awkwardly, I would tell the customers, yeah, I'm supervising Jacqueline to make sure she doesn't mess up again. Isn't that right, Jacqueline? Do you remember the blood? Do you remember the screaming? Do you remember the panic? My first solo endeavor into the magical world of guacamole was a to-go order. I worked in the back so it was like a nice low pressure training opportunity. The only issue is that I caked the thing in garlic powder and I low key ruined it. I didn't want to get chewed up on my manager or anything so I just low key stuck the lid on it and I sent it on its merry way. The customers who bought the tub were kind of ripped off and if they're watching I will totally give them their money back if they get a hold of me, just saying. But most of the time I spent working there I was actually tucked away in a hallway where all the incoming dishes were being sent. I worked with a team of one or two other folks and we'd clear off the dishes and send them in the back to be washed. It was gross work but it was easy and repetitive and we got to talk and get to know each other. Some days we would gossip about kids at school, other days we would have rapping contests and I'd hear stories about the restaurant. There was one I remember, the ghost at table 26. Basically the restaurant itself is in one of the oldest buildings in town and it's seen some history. It apparently gets a little creepy at night. Some workers talk about cleaning up at night and then they see a lady sitting at table 26 just tucked away in a corner. The freaky thing is is that more than one person is seen or two. Some employees used to leave candies for her at night but I mean they kind of had to stop that because it was wasting candy. But a legit spooky story came from when I was working and the owner's wife came in the back and she started fuming quietly. She was like visibly distressed and we were like hey are you alright? She was furious because she walked up to a table and asked how their food was. The customers asked well since Donald Trump was president doesn't that mean some of your employees have to be deported? She was seriously ticked off and she was asking us if she should kick him out or not. I was like oh heck yeah but everyone else was like nah. She ended up letting them stay and that was kind of lame. Another freaky thing was a dude who started working there a few weeks after I was on board. His name was Connor. Now I've never had issues with coworkers. I get along with everyone pretty well in most work environments but Connor was one of the most miserable, deplorable, disgusting people I've ever met like he's in top 10. One of the friends I made there refused to work with him. See she had a sister who was autistic and she struggled with body images due to her diabetes and Connor used to call her able of slurs and mock how she looked. He was just gross. You see where we were all cleaning off dishes and that kind of thing there was a big old wall and since folks would come around racing at high speeds with heavy plates full of piping hot food they yelled corner corner corner. Connor decided that it would be funny yell corner corner corner in response. So now people would be going around corner corner corner corner Connor Connor. And he did this dozens of times every shift I had with him. It sucked. What was arguably the worst thing of all about him was the way he talked about our coworkers. He'd stare at their butts while they walked away and he'd nudge my arm and be like, Yo did you see that? No Connor I wasn't looking. Yo bro she's got to be at least like a seven or an eight. Wow you're using numbers to objectify human beings that's pretty cool.   Bro I totally bang Jacqueline. She's a fine dog.  If it's any consolation though Connor has since been fired from his job. I'm not entirely sure why. I asked around. I can't figure out why but chances are something terribly got caught on. Everything was great aside from Connor while I was working there until one incident went down. Basically I got in order to get up and go to a booth to make my guac. Turns out it was the mayor of my town. I was like oh snap Nito. I made the guac and it was awesome but I put a little too much salt in it. They called me back and as I was prepping another avocado to put in it to mute the salt. I low key cut myself in the knuckle like the one time that I wasn't wearing my glove.  It just like shot across their table. I quietly excused myself away from the table and wandered over to the employee sink. And I distinctly remember seeing what looked like TV static filled my vision as I bled into the sink. I kinda realized that I cut myself hardcore and I was in the process of passing out. There were a few people crowding around me to make sure I was okay and they were trying to talk to me but honest to God all I heard was just ringing my ears as I slowly slipped into the void. See I've seen movies where people faint and I'm like no I ain't no push over.  If I was ever in the position that I would be knocked unconscious I would make an effort to stay awake. And that's kinda what I did. I just rode the express train to nothingness and I managed to stay awake. Felipe came over and he sat me down in a chair. Side note what a gentleman. He told me to hoist my hand above my head and he handed me a Dr. Pepper to drink from so I could get some more sugar in my blood.  He looked at me and he was like hey Nate are you feeling okay? I was like yeah I'm feeling a little bit better. Good now you just put on your plastic glove and you get back to washing dishes. Boy I just saw Jesus I don't want to work anymore today. So I finished up that shift and I only used my right hand. In fact I finished up a lot of shifts just using my right hand. Actually I used my right hand so much after that that my rhomboid muscles on the right side of my spine swelled up to the size of a baseball. And here's the thing it hurt horribly. To this day I haven't felt worse pain than what I was going through when my back was all messed up from that. I could barely drive home at night because the bumps were awful. I went to go see a doctor and it turned out to be an issue with underused muscles suddenly kicking into overdrive and they react negatively. It just shows how lazy I am. Needless to say I wasn't able to do my job effectively and I put my two weeks notice at work. I was worried I would be a liability to the company to my coworkers and I had to step down. I made up some lie about doing an internship with a local advertising company and I hit the road. I've actually been doing YouTube instead. If you're watching this Felipe I'm sorry I lied to you you're super cool. Hey there I hope everything's gone take a chill pill bro.   See what's worst of all about the whole back thing is that it can only be fixed through exercise so I'm like stuck with it for my entire life. So I guess there's a really important lesson to learn. Considering all the amazing friends, good vibes, spooky ghosts, even the douche canoes. All of that can go away in an instant if you don't wear gloves while cutting off a cutter. Hey that was my video about working in a swanky Mexican restaurant. If you enjoyed it you should strongly consider subscribing so I can have a momentary ego boost. And while you're at it, why don't you click on that little bell thing so like your phone vibrates whenever I post something. So I can like make more videos for you and stuff. Thank you for watching you sexy creature. I'll be back every Wednesday for you. Ciao.


Desert dust feeds Amazon forests, presented by Science at NASA. The Sahara Desert is one of the least hospitable climates on Earth. Its barren plateaus, rocky peaks, and shifting sands envelop the northern third of Africa, which sees very little rain, vegetation, and life. Meanwhile, across the Atlantic Ocean thrives the world's largest rainforest. The lush, vibrant Amazon, located in northeast South America, supports a vast network of unparalleled ecological diversity. So what do these seemingly different climates have in common? They are intimately connected by a 10,000-mile-long, intermittent atmospheric river of dust. Every year, intense Saharan winds send enormous clouds of dust on a transatlantic journey to the Amazon basin. This dust, much of it originating in an ancient lakebed in Chad, is rich in phosphorus. When it reaches the rainforest, the remains of long-dead organisms of the Sahara provide crucial nutrients to the rainforest's living flora. Phosphorus, which is essential to plant growth, is in short supply in the Amazon. Desert dust dumped into the forest every year helps to diminish this deficit. NASA researchers are studying this dusty link between Amazon and Sahara to understand how it operates and how it might be affected by climate change. We know that dust is very important in many complex ways, says Hung Ben-Yu, an atmospheric scientist at the University of Maryland, who works at NASA's Goddard Space Flight Center in Greenbelt, Maryland. Dust affects climate and, at the same time, climate change will affect dust. As researchers, he adds, we ask ourselves two basic questions. How much dust is transported? And how does climate change affect the amount of dust that travels across the Atlantic? Data from NASA's Calypso satellite, launched in 2006, may provide the answers. For the first time, Calypso has quantified the amount of dust that makes the transcontinental voyage, and the numbers are impressive. Of the 182 million tons, or nearly 700,000 semi-trucks worth of dust, that leave the Sahara each year, 27.7 million tons, or 15% of the total, are scattered over the Amazon basin. Calypso, short for cloud, aerosol, LiDAR, and infrared pathfinder satellite observation, uses a laser range finder, or LiDAR, to scan Earth's atmosphere for the vertical distribution of dust and other aerosols. It regularly tracks the Sahara-Amazon dust plume. One of the things Calypso has revealed is the connection's variability, changing as much as 86% between 2007 and 2011. Why? The answer could lie in the Sahel, the long strip of semi-arid land on the southern border of the Sahara. You and his colleagues have found a possible connection between rainfall in the Sahel and the amount of dust transported over the Atlantic. When rainfall in the Sahel is higher, the volume of dust is lower. The exact reason behind this correlation is unknown, but you have some ideas. It's possible that the increased rainfall could cause more vegetation to grow in the Sahel, thus leaving less sand exposed to powerful winds. Another possibility centers on the wind. The amount of rainfall is correlated with wind patterns that can sweep dust from the Sahara and the Sahel into the upper atmosphere, which is basically a superhighway to the Amazon. Thanks to Calypso's unprecedented 3D observations of atmospheric dust, scientists can begin to create models to predict how the dust may impact climate in the future and how it nurtures the lush forests of South America today. Creatures of the Amazon, and perhaps around the globe, may want to consider sending the Sahara a thank you. For more news about unexpected connections on Earth and other planets, tune to science.nasa.gov.


back in the 60s the man I wrote it for sang it with me. 1958 imagine you're inside Toronto's sony centre an air of anticipation fills the hall as the band with their instruments gets ready suddenly the lights go out and a spotlight pierces the darkness focusing on the back of the hall then the music springs to life with the opening tune and the well-known lyrics echo through the your head on my shoulder. Born in 1941 in Ottawa, Ontario, Canada, Paul Albert Anka today is known far and wide not just as Paul Anka but an iconic figure in pop culture. His journey is laced with timeless hits and he redefined musical boundaries. Growing up in Ottawa young Paul Anka was always drawn to music. A self-taught prodigy he mastered the piano and guitar during his teenage years eventually forming the vocal ensemble The Bobby Soxers. In 1957 armed with ambition in a song Anka traveled to the very heart of music in New York. His original composition Diana not only won him a recording contract with ABC Paramount Records but went on to sell over 20 million copies. This was the dawn of the Anka era marked by chart-toppers like Lonely Boy put your head on my shoulder and puppy love. Did you know that a street in Ottawa was named after him? Yes the very own Paul Anka Drive of Ontario Canada was named after the star. Also in 1981 the Ottawa City Council named August 26 Paul Anka Day to celebrate his quarter-century in show business. While Paul Anka left his legacy in his home city he also moved to the west coast like the star he is and his one-time Los Angeles abode has recently hit the market. This property located in the area of Thousand Oaks has all the elements to become a real estate sensation. A top-notch recording studio, a game room with billiards, a completely renovated kitchen, a separate gym and a stunning infinity pool. This extensively renovated mansion carries a premium price to go with it asking 10 million dollars. Well that's expected for a property within the prestigious Sherwood County Club's guarded gates. The community is renowned for its Jack Nicola's designed golf course bordered by opulent residences and expansive estate. Membership to this elite club with prominent names like Justin Timberlake, Sylvester Stallone and Tom Selleck reportedly requires an initiation fee of just $300,000. Anka's one-time property is located on one of the most expansive privately gated plots in Sherwood covering almost six continuous acres. A lengthy gated driveway runs between tree-lined rows leading to the nearly 8,000 square foot mansion which is discreetly hidden from street view ensuring privacy. A number of the rooms offer French doors with access to the backyard and a spacious motor court proceeds of four car garage providing plenty of space for luxury vehicles such as Polenka's Porsche Panamera and Mercedes-Benz G-Wagon. Nestled on a sprawling six-acre lot, this renovated French-inspired villa stands as a testament to luxury and precision. Step inside and every corner tells a story. A spacious foyer with a high ceiling, stone floors and Juliet balcony. The French-inspired residence has a semi-open layout with stone floors, high ceilings and statement light fixtures. The pulse of the house has got to be the state-of-the-art recording studio where melodies come to life, the Paul Ankaway. For when it's time to unwind, there's the billiards room with its block mirrors reflecting elegance in every detail. An artist or anyone for that matter needs their fuel and this elegantly renovated Eden kitchen is a culinary haven with its new appliances and stunning details. There's also an Eden chef's pantry with a large island and windowed breakfast The dining and family rooms have fully collapsible doors offering unobstructed views and seamless access to spacious patios for dining and relaxing poolside. The residence also has several reception rooms, two of which are lined by Anka's collection of gold records. Now Paul's personal retreat, an orange living room adorned with accolades speaking volumes of his legendary career. Upstairs, a sanctuary. There are four ensuite bedrooms plus two additional bathrooms. The main suite is a realm of relaxation complete with a fireplace, a lavish bathroom, an office area and a dressing room. Outside you'll also find a fitness buffs dream, a glass wall detached gym as well as an adjacent bathroom and an outdoor shower. The home's infinity pool offers rejuvenation amidst nature's serenity. There's also tons of space to throw parties and barbecues or just relax with Paul Anka's melodies. The listing held by Marianne Scott of Beverly and Company and team Nicky and Karen of Compass is described as the epitome of luxury coupled with the natural beauty of the surrounding lake and majestic Santa Monica mountains. Paul and his late spouse Ann also once owned Beverly Hills home. In July 2004 the couple announced they were selling this home located in a secured enclave above Beverly Hills for a price close to $6 million. Their goal was to acquire more compact residents within LA. Their property in Beverly Hills that they had been possession of for 14 years was five bedrooms, eight baths and spans 8,000 square feet. This neoplassical villa constructed in 1987 is complimented by breathtaking urban panoramas, a dedicated media space, a screening room and a library. In a noteworthy twist the reason they were offering this property was due to a new acquisition in Las Vegas, a city they formerly resided in for a long time. However, Angus Tropicana Avenue abode Vegas is now part of the MGM Grand which opened in 1993. Paul Anka has always been a legend in the vast expanse of pop culture. We can also see that every home he's inhabited, every note he struck and every lyric he wrote tells the story of a man who wasn't just born to be in the music industry but to influence and redefine it. That will wrap up today's house tour but after wandering through Paul Anka's real estate, answer this question for me. If you had the opportunity to host a grand party at Angus house, which area would you use as the main event space and what would be the theme of your event? Let me know in the comments below. Don't forget to like, subscribe and follow me on Instagram at Cara the Vampire Slayer to see more. I'm Cara and I will see you all in another video. Bye! Get ready to see some luxurious properties once we look at the numerous mansions owned by star couple Nicole Kidman and Keith Urban. He'd help when we get to town most of us do and we just want someone to believe in us you know it makes all the difference so you're easy to believe in Breeland. Pear maintains multiple residences scattered worldwide including a breathtaking farm in Australia, a luxurious mansion in LA and a penthouse in Manhattan. There was even talk recently that Nicole purchased another lavish property in Portugal. Despite all of those spots the focal point of Nicole and Keith's lives revolves around their primary family estate situated in Nashville Tennessee. This impressive property boasts a variety of amenities such as swimming pool, recording studio, theater and ample space spanning over 10,000 square feet. Basically there's plenty of room for Nicole, Keith and their daughter's faith in Sunday. Nicole and Keith spend the majority of their time at their family mansion located in Nashville Tennessee which they purchased for 3.47 million in 2008. The 10,925 square foot of boat offers seven bedrooms and eight baths. So there's more than enough room for Nicole, Keith and their daughter's faith in Sunday. Their stately and regal home is in an upscale gated community called Northumberland just outside of Nashville offering the famed couple top-notch privacy and security.  According to old listing photos from the time of purchase, Nicole's estate was decked out in a classic style with plenty of common spaces boasting high ceilings as well as elegant details from the curtains to the archways and the marble floors. The couple's living room clocks in at a massive 32 by 21 feet while the formal dining room is 23 feet long. The main floor is full of French doors and large paint windows, flooding the mansion with natural light. Hereby there's the kitchen which is decked out in hardwood floors and expensive appliances and at the top of the main staircase there's a loft like lounge space too. Other rooms in the couple's mansion include a rec room with full bar and pool table area, a hobby room and a home movie theater. While we haven't been able to see photos of each of the bedrooms we do know, Nicole and Keith's sumptuous master suite has a fireplace in a sprawling spa style bathroom. Many of the photos of this mansion are well in need of an update and we can even see from aerial and exterior views that the couple has renovated their Nashville Palace to fit their taste. Nicole and Keith have shared some personal glimpses into their lovely home though, including the time the award winning actress revealed she was learning Italian way back during the lockdown. She posted a pic on Instagram showing herself studying on a pale blue and cream striped armchair next to a set of double doors with glass panels looking out to a balcony. Keith can also write and record new music from home since he has a studio here set up with all the speakers, mixing decks and equipment you would see in a professional space. Maybe even better. We even saw one of their cats snow looking out from the windows at this Nashville home in a photo taken in the spacious hallway complete with wooden floors and an antique rug. Outside, beautiful landscaping, a large pool, spa and full-size tennis court round out Nicole and Keith's stately property. There even appears to be a play area for the kids and a private creek. Nicole and Keith also snagged themselves a stunning penthouse in the Ritzy Tribeca area of New York City in 2020. The couple spend 3.5 million dollars on a condo which stands about 1,600 square feet with two bedrooms and 2.5 baths. So they have a lavish space to stay at when they find themselves on the east coast. Their penthouse is located inside of the famous clock tower building in Manhattan which previously housed the New York Life Insurance Company. The developers converted the 400,000 square foot building into luxury condos back in 2018. Photos from the building's website show a ton of amenities that residents have access to, including rooftop gardens, an indoor pool, dining areas, a fully stacked gym and much more. According to reports, one of the features which attracted Nicole and Keith to the building was what's called a sky garage which allows residents cars to be lifted to their units via hydraulics. This helps the high profile couple avoid the eyes of the paparazzi. Before we wrap this up we have to take a look at Nicole and Keith's Australian farmhouse. The actress previously gave Vogue a video tour of her retreat, Bunyah Hill in Australia, which they bought also in 2008 for around 4.1 million dollars. Long hidden behind hedges and greenery, the Sutton Forest property with its magnificent 1878 Georgian mansion and impressive pedigree, has wide standstone terraces, press metal ceilings, a carved cedar staircase and 10 marble fireplaces throughout. This place has the proportions and amenities that make it worthy enough to be leased as a vise regal rural retreat for Lord Augustus Loftus. This guy was a governor of NSW in the colonial 1880s. Bunyah Hill was sold by Peter Cote, head of global markets at National Australia Bank and his wife. The stunning Georgian mansion that Nicole and Keith now own is a rustic yet elegant farmhouse and sits on a whopping 111 acres of land. Nicole showed off the billiards room on the home tour where she loves to play a game or two and the formal living room has a grand piano as well as one of the many fireplaces. The couple's farm is also home to Black Angus cows and orchard and a small guest cottage. When they get tired of the relaxing country air they can also retreat to the penthouses they own in Sydney. Despite being based in the USA's country music capital Nashville, Nicole and Keith also claim half a dozen apartments and harborside millsons point in Sydney. Her most recent purchase took her price tag in the one building to over $27.5 million. A three-bedroom spread on the 15th floor of the landmark latitude building was purchased by Nicole in May 2023 for $7.725 million which like her other apartments here are held in the name of corporate interest under her childhood friend Annette Reckner. Prior to this the couple was already working on making their mark in this building. First they bought a six million dollar penthouse located on the 21st floor before snapping up the penthouse next door for $7 million in 2012. Then they combined these two into one massive apartment. Meanwhile a 2.68 million dollar apartment on the 19th floor of the building was bought by Nicole in 2011 which she now reportedly uses as a home office. We have glimpsed inside Nicole and Keith's penthouse bed but it's kept mostly private. The apartment has a huge wrap around balcony with floor to ceiling glass doors from their spacious living area which has a formal dining table for the ultimate dinner party setting. This building also provides residents with access to a heated pool, gym and sauna as well as a prime location in Sydney which Nicole showcased with her fans on Instagram on New Year's Day. While Nicole and Keith own more properties than these these are the places where they spend most of their time. So for today that's gonna wrap up this house tour but before we go answer this question for me if you at homes across the globe which continent would you choose to spend the most time? Let me know in the comments below and don't forget to like subscribe and follow me on Instagram to chat. I'm Cara the Vampire Slayer and I'll see you all in another video. Bye!