Good evening and welcome Okay Yeah, all right. Welcome to our talk on open container technologies and open stack That'll do it We have the technology wonderful. I don't want to go to the bathroom with this and have that be on Okay, welcome to our talk on open container technology and open stack So we're going to cover Kubernetes the open container initiative and CNCF and how those Integrate those technologies integrate with open stack as well as the larger container community So before we get started how many people here have heard of the OCI? Okay, about a third and the CNCF About a quarter and anybody using Kubernetes right now In production That guy welcome well done Okay, so I'm Daniel crook. I work for IBM as a senior software engineer Partner hands-on with customers to do POC based on open source technology Docker and containers, of course an open stack, but also cloud foundry and a new serverless framework that we have called open whisk My colleague Jeff I'm Jeff Borek and I work in Open source. I've been doing that for about a decade now and For IBM I've been Working in Linux originally and then most recently in cloud before my current role in open technologies and partnerships And I'm Sarah Navani. I work for Google and my focus has been open source communities for the last 10 or 15 years I run the open source community side of Kubernetes We go Okay, so today I'm gonna give you start off with a level set just on container technology why it's so attractive and Some of the companies organizations that have been part of it in the past and and hopefully into the future as well we'll look at how that container technology integrates at several layers of open stack and particular how it how it supports Kubernetes and Then we'll look into the open container initiative itself as well as the CNCF to see how those are defining standards going forward for container technology and Then tie everything together at the end and And we'll learn more about the the Kubernetes say special interest group within the open stack community Okay, so container technology today in 2016 It's become very attractive For many different reasons a lot of folks are now able to use it in production take advantage of the benefits that it has So containers they're able to provide process isolation on On a host and also limit access to other resources The networking the storage the compute resources They are logically similar to virtual machines But they are much more efficient because they share the host kernel of the underlying operating system and they avoid any of the Translation needed by a virtual machine that might be running on top of hypervisor So basically on the left You've essentially cut out the middleman of all the extra software on top of a host The other key benefit since that makes systems generally more efficient is that you're able to now package applications package services into a self-contained image that can That can capture all the dependencies and really strip out what you need to have installed on the underlying host system That's running your containers. So provides a very clean separation, which is great for developers We're building the services or open-stack developers creating any of the services themselves Packaging those into something and deploying it not only on their own workstation But out to any deployment environments that they they have So of course, there's you know, this this makes it super efficient to run them makes them very portable There are some trade-offs that I won't get too deep into But one way I've I've used to describe it is if you have you know a need for housing as a person You can choose to buy a house get the whole property Get your own electrical system get your own plumbing or you can rent an apartment Which may be more efficient may be cheaper for a short-lived stay that you have in a city versus a longer, you know buying a house So you can rent an apartment, but you might have that shared resources of if the plumbing or electrical system goes down in that Whole apartment complex. You've got the shared problem there. So that's basically the analogy of the trade-off there So that's where we are today with containers over the last 17 even longer years Container technology itself has been evolving lots of great ideas lots of trends have been coming together with that technology So going back to 1978 1979 with CH route Isolating where the file system starts what access you might have there free BSD 17 years ago extended that to other resources on free as previous unit Unix and Linux took those ideas tried to port them over shortly after unfortunately that required quite a bit of Extra work to take advantage of that feature You had to recompile the kernel and a lot of folks who were using distributions didn't really have the the The ability or the desire to do that separately outside of Linux again, so Larry start to bring the idea of not only having the isolated resources on The compute node, but also a way to package those in snapshots Unfortunately, it also required a slur a specific system the ZFS the Z file system So a couple years go by and Google Takes a different approach that doesn't require recompiling the kernel Using features that are already in the operating system, which really started to make containers more usable and Red Hat then built on that innovation adding Support for username spaces allowing you to have root privileges within containers, but now that not outside of the system so adding some nice security isolation and IBM we then provided some tooling that made it a little easier to use those features that are now in the system And basically provided some tools around c-groups The process containers and the namespacing, but really what made containers hot three years ago a startup called Docker Built some developer-friendly tooling to take advantage of how you run those containers and also how you package them efficiently To really take what was already there in the system and just bring it to a larger audience So there's been a lot of innovation in the past with containers And again, it's the future with the OCI and CNCF that we'll cover a little later Hopefully it's a continuum with a lot of innovation being added to the platform Okay, so containers an open stack. They're not just in one area or another Because of all those benefits You know the ability to build and use fewer resources deploy things faster test things faster They made their way into a lot of different projects So one of the first places if you if you take that analogy of a virtual machine and a container They showed up in Nova. That's just another compute asset that could be plugged into Plugged into Nova that can be treated as basically an image an instance on a compute node Heat then provided a way to support those those type of compute resources so you can deploy groups of containers And more recently Magnum has provided an abstraction layer to run container orchestration systems on top of OpenStack For OpenStack itself, it's also a Distributed application that has a lot of services. So the COLA project has now been able to Containerize the under cloud. So Magnum lets you run containers on OpenStack COLA lets you deploy OpenStack itself Marano provides a package catalog and Of containerized applications to run on clouds and currier takes the Neutron networking model and maps that to containers You have kind of a common interface between your virtual machines your bare metal nodes and your containers Okay, so I'll hand it off to Jeff to talk about the open container initiative so we saw earlier that quite a few people at least had some familiarity with the OCI and it was announced by Solomon Hakes at the docker con event middle of last year 2015 I'll go back a little into the history behind it But the most important thing about the OCI from my perspective Is that it's really all about governance at the end of the day because Open source is great, and I think safely say that everyone here to varying degrees is a large open source fan But the license is only one element of an open source project and At IBM we like to talk about code community and culture and the innovation that the Docker crew introduced is Very significant in that it makes the container technology much more easy to consume and That's about the time. I got involved with actually Docker. It was a early in 2014 I was at an open stack summit. In fact, it was the one down in Atlanta and there was a huge buzz on the Expo floor about this new company that had just sort of had a near-death experience and had done a bit of a pivot and And they were now calling themselves docker and they had a open source project there was also called docker and How was this going to have an impact and well it was going to make containers and much more Accessible or easier to use by your typical application developer or system administrator but An open source license again just puts the code out there The real question is, you know, how does a fundamental technology like that? Get shared by a community so that it's really a level playing field and many different companies and organizations have free access to it and As you see up on the slide here one of the key points is it's not tightly associated With any one single company It's also important that This type of project or this type of technology Have an open governance structure and is associated with an organization That can help bring it forward In a long-term, you know stable and meaningful way so You can see by this next slide When this was announced There was about half a little less than maybe a little bit more than half of the current companies are involved So this has continued to be a very important element of the ecosystem as the OCI has evolved over the last little over a year now and We talked a bit about Docker earlier in this session, but going into it even a little bit further. I was involved with Docker in officially in 2015 because I was proud to be part of the Open-source steering committee. In fact, I was asked to help share that for a period of time But as we moved forward it became really, you know in a parent, especially when there was some conflict in the community Because of this issue of well, how do we separate, you know, Docker the project from Docker the commercial entity? And how do we, you know, achieve clarity around that and Who gets to decide, you know, what's actually in the spec and the code associated with it and other interesting questions to in terms of like Should this be based on, you know, the code or should you know, this should the spec lead, you know What's the right approach to take here? so How many of you are familiar with core OS? I know they're here at the expo hall. So Through conflict They actually helped act as a bit of a catalyst because it it furthered this dialogue within the community about You know, what's the right thing to do here? You know, what's what's a fair way to help move this technology forward and still give the creative people at Docker their do with respect to the new thinking that they brought to the model So I was really personally, you know, totally excited when Solomon announced the contribution that they were willing to make to start the OCI and You can see by this next slide That's it's evolved even since that announcement was made about again a little over a year ago In addition to the Docker engine The secondary format the format specifications also been introduced To help bring portability to the OCI concept, but it's also important that the OCI Doesn't expand too broadly, right? I mean the whole idea is to try and using the shipping metaphor Establish the boundaries of what a container is how to make it portable how to make it interoperable but not have scope creep go to the point where this starts to get into a higher-level thinking around automation and orchestration Because one of the other key elements of trying to get this right and it's a very delicate balancing act is that you know Standardization is great because it allows everyone to participate in a meaningful way And it can help make markets But if you extend it too far and you lock things down too much it can actually get to a point where You might stifle innovation or prevent some other new innovation from coming into the marketplace in a meaningful way just a quick look at You know who's participating because there's been a lot of things in the news if you follow this closely and Hopefully most of you haven't because there are lots of interesting things going on But there's been some friction even after this announcement was made which was intended to eliminate some of the friction again over a year ago but to Docker and Coro s and red hat and other people participating to their credit this effort has moved forward consistently over the last 18 months and you'll see both the 1.0 version of the specifications for the engine and the Format come out Later probably I'm gonna say before the end of November. I thought we might have been done by now But we're still working through some of the details on it, but you can see on this slide that Red Hat Docker and a Whole host of companies from a wide variety of perspectives has been contributing into this initiative and You're going to see other things happen. I think over the course of The last quarter of this year and even into the first half of next year around this space to try and help You know keep this technology moving forward The last thing I want to say about the OCI is just a reminder about this attempt to keep it focused and Not have the scope expand too far because there's a complementary organization that was announced about the same timeframe and It's all about this concept of cloud native and to transition into that thinking I want to just mention that When it comes to you know cloud native computing It's really trying to take advantage of this whole paradigm of Well application development has been done in this traditional way and we've all heard of dev ops, but When you can truly move to a new era where cloud computing is going to enable Technology on demand. How do you take advantage and rethink the way? Applications get developed and how that infrastructure that highly scalable infrastructure Runs and orchestrates those container technologies Jeff and I work together on both the OCI and the cloud native compute foundation As you mentioned the cloud native compute compute foundation was announced about the same time that the OCI was I believe that it was June for the OCI at docker con and at oscon in 2015 for the cloud native compute foundation Jeff also mentioned that you want to very carefully scope what a standards body Tends to work on because boiling the ocean and making your scope too big Makes you not move forward very quickly so the cloud native compute foundation focused on the broader picture, but not specifically the standards so the cloud native compute foundation has focused on container packaged Dynamically managed and microservice oriented architectures for applications one of the pieces of the cloud native compute foundations Stack the application architecture that it has developed is consuming the OCI standards of Tooling like docker and rocket or app C and run C It's not hard to imagine a space where we all want portability We will all want the ability to move our applications and avoid vendor lock-in which used to look like vertically Integrated stacks from a single vendor now. We're seeing questions of cloud lock-in meaning public cloud lock-in or a specific set of services in the public cloud and Just as the OCI wants to make sure you have Opportunities around containers to choose the container that bets best fits your application and allows for greatest innovation around container architectures and container systems The CNCF wants you to be able to have cloud portability So we tend we have gone ahead and built an architecture that we use an end user architecture that we use to think about The different projects that the cloud native compute foundation has brought into it So when the cloud native compute foundation was announced in July of 2015 It was announced as part of the kubernetes 1.0 announcement as well the idea was Google and kubernetes wanted to We're Google wanted to bring kubernetes to an open source world Where there were options and opportunities for people to Contribute well outside of Google and one of the big challenges that we had was people were concerned that Google might abandon the project So instead of choosing to make a kubernetes foundation We chose to talk with the Linux foundation and bring this broader cloud native architecture Encompassing the application definition and development space orchestration and management where kubernetes exists Runtime which is the actual consumption of the OCI standards as well as some provisioning tooling around what instrumentation to provision Your cloud applications exist infrastructure and bare metal is outside of scope, but you got to put this somewhere So the cloud native compute foundation to date has accepted three projects through our incubation process kubernetes being the first and That was donated by Google to the cloud native compute foundation in order to bring forward The view that it's an open community Prometheus is a toolset that allows monitoring of Cloud native applications and spends its effort on instrumentation and visibility into those applications Open tracing is more on the instrumentation side These are all three projects that are in incubation within the cloud native compute foundation and the cloud native compute foundation is governed Because as Jeff said governance is an important part of Open source. They are governed Independently as projects, but with an oversight board of the technical oversight committee The cloud native compute foundation took a lot of lessons from open stack. We're all here because this is an open stack Summit There were many things that we saw that open stack did very very well and we tried to take and emulate some of those We also tried to make sure that In being open and in being engaging with our community, we tried to also give some governance around that But since we're talking about open stack and because kubernetes is my well Let's call it my current love of open source. I want to talk about how kubernetes and Open stack are working together There are a lot of ways there are several projects that we heard from in Dan's portion of the talk and Those specifically are happening most of them are happening inside the open stack community There is also work that is happening inside the kubernetes community through the kubernetes Special interest group open stack. So if you search for kubernetes sig open stack That's the place that you're going to find most of the people who are interested in integrating the two different infrastructure frameworks Now I'll go through the ones that Dan mentioned quickly as well because there are two ways Well three I'll get to the third minute. There are two ways primarily that we see open stack and kubernetes working together The first is making sure that open stack is a first-class cloud provider For anyone who wants to run kubernetes If the goal of kubernetes is to give you container packaged applications that are independent of your cloud provider Then open stack has to be one of those clouds. We have a special interest group for AWS We have a special interest group for Azure. We have a special interest group for open stack Now many of the ways that that tooling for the first-class cloud provider exists outside of kubernetes is through these different projects inside the open stack community morano courier heat and Magnum and those all allow for Kubernetes to be deployed on top of open stack What our sig open stack is working on is trying to make these projects be more efficient and make more use of native kubernetes tooling apis and Not have to work around limitations of kubernetes Through your projects, so it's making sure that we're giving feedback to kubernetes as the upstream Who has to have open stack as a first-class cloud provider? The second way that we See open stack and kubernetes play together is actually the reverse So the first was kubernetes on open stack And then there's a very large group of people who are working at the containerized Control plane of open stack on top of kubernetes And there are a few projects cola being the one that is most directly Inside the open stack community at this point stack in eddies is something that core OS has been working on and fuel CCP is the project that Morantis has been working on now each of these Each of these different opportunities or each of these different projects have given a different opinionated way To run open stack on top of kubernetes or the control plane of open stack on kubernetes Allowing that control plane to manage a separate cluster independent of your kubernetes cluster That has VMs. So this is for the world where we presume containers are more the future But VMs are something that we will need for a very long time kubernetes and open stack are going to be something that our enterprises work with for For many many years. I don't think there's any reason to see us as in competition the third way that I mentioned is actually another way that That IBM has been working on which is using a neutron underlay network and then running independently Open stack and kubernetes on clusters that share the neutron underlay So there's a third way all of this work is Happening inside the special interest group open stack So if you have any interest in kubernetes or containers or open stack and kubernetes more specifically Come take a peek and see the work that's being done. Please share your ideas Share your pain points share the ways that you would like to see kubernetes evolve to either Improve the idea of open stack as a first-class cloud provider within kubernetes or To evolve as a way that kubernetes can run better as an application on open stack as I said, we took a lot of our cues from the governance of open stack Which means that our special interest groups actually have a fair amount of independence and power themselves to help make changes and This is the best possible way for you all to give us feedback engage with us as Either users or consumers of kubernetes or as someone who might be interested in making any sort of contributions So we have the closing Right, do you want to just do the last yeah, and then we'll then we'll take questions after the last slide Okay, so yes to summarize so take that container technology. It's not new. It's been evolving for the last 16 many years beyond that before that if you count CHRUD as well it's going to continue to evolve with the OCI for the container standards and packaging format and of course through the CNCF for Deploying large clusters and applications based on containers So containerizations used throughout open stack many different places You can probably expect it to show up in any new projects that enter the big tent or the larger ecosystem But it looks like kubernetes is kind of becoming the de facto standard way to do that to deploy groups of services and Just as the open stack foundation governs the API's around compute storage network API's We expect the OCI and CNCF to do the same thing around the container to technology itself So again, these things are moving fast lots of companies involved So if you have a stake or if you have an interest or technical skills, please get involved with the OCI CNCF and Kubernetes community So now we've got time for questions because we thought you might all have some And this is the fun part where you get to ask the challenging slash awkward slash I wonder I wonder if I can get them to cringe if I ask this question question so And why we have one already can you step up to the microphone? Oh, they're all makes excellent the third way I can elaborate very slightly But what I can do is suggest suggest that the third way is discussed most in the Kubernetes sing networking because that's where most of the changes that are necessary to have Kubernetes and open stack run on top of a shared neutron network So I can't elaborate deeply. I haven't tracked it that closely But I know that there is work to have The two of them run in parallel on top of the the neutron network So apologies, I can't go much deeper than that, but I can tell you where to find more info other questions So while you're thinking of those other challenging questions, I thought of one myself for Sarah don't run away So in some open-source communities, there's this concept of a BDFL a benevolent dictator for life And I was wondering, you know, is there a BDFL for the CNCF because you know, they could come up with some more acronyms So I volunteered for that position Nobody took me up on it so There is not the concept of a benevolent dictator for life within the cloud native compute foundation the cloud native compute foundation was actually Conceived very much more like the US government model with a three houses of governments So in the US, we have our Senate and House of Representatives We have a judicial branch, so we have a legislative branch a judicial branch and an executive branch in the cloud native compute foundation The idea is that we have a technical oversight committee who are luminaries from the industry broadly across work that has been done in containers in cloud native architectures we have a Governing board which is more based off of people or Companies that have supported the cloud native compute foundation which does handles the business side of this Foundation and then we have a third group which is being formed Which is the end user board and that is the user voice into this group So we want to make sure that we are hearing people and companies who are focused on cloud native architectures and want to hear their pain. So the idea is to make this a Balanced governance model. There's not a benevolent dictator for life Though as I mentioned each of the projects have their own models of governance And I can also answer that there's no benevolent dictator for life and kubernetes kubernetes has a Has the concept of or is discussing the concept of an oversight committee or an oversight council called the elders I'll just remind folks. There's a mic over there and Sarah if you want to So is there a clear vision being led by an Individual or a group for the cloud native compute foundation or for kubernetes. Is that your question? More or less. Yes. Okay So for the cloud native compute foundation, the technical vision is being guided by the technical oversight committee with input from the The user board as it gets formed and the governing board as as it stands handling the business side For kubernetes. This is part of our transition from being a Google led project to being a community led project So for the first year of the project that was very much held by the technical leads inside Google and Had a clear they had a clear vision they worked on that and they brought it forward with the 1.0 release in 2015 at Ozcon After we brought it for brought it out into public and we wanted to make sure that there was a very much and Open and inclusive community in this we've struggled a bit trying to figure out how to manage that vision Making sure that we don't have too many voices or or being led too much by The broader the broader community in the sense of people who don't have that clear vision set up So there is a document that was written early on called what kubernetes is not Which is the standard that we look at so it's not a platform as a service It's not you know it goes through a list of a few things that it's not and that gives a couple of things That gives us a nice open space in the ecosystem for partner organizations to participate They know these are things that that kubernetes is not intending to cannibalize But it also gives us a reference point when we came up with the elders council The idea was having pushed much of the decision-making to Specific groups that had technological focus so networking or node when we pushed those The decision-making closer to those groups that were verticals We found at some of the interfaces we had technical disagreements and the elders the idea is people who have been with the project a while represent a broad swath of the community Recognizing support and push forward that technical vision So it's again sort of a supreme court To use the metaphor again someone a group that can weigh in with an opinion and say this is the way We're going to do it based on that technical vision question the Of the direction of the vision just on the plane to Barcelona. I finished reading the news tag article about the CRIO Where the goal is to abstract away what we currently have and container technologies base all of that on OCI? specifications because currently we have Kubernetes running on Docker and we have rocket neat is running on rockets But we don't have the possibility to do to to both at the time or or just say okay There's going to be a third player that's Implements the specifications and we can just plug and play that and remove that and take another one with Maybe the performance of one container engine is better than another one And I just want to play with that is this division where where we want to go with with all of this this so there so CRIO is a Implementation of CRI, which is the container runtime interface so CRIO is the OCI Implementation of that so the idea is that CRI is the shim That gets you from Kubernetes to whichever runtime you choose so CRIO is the OCI version We see a CRI rocket at some point We see a CIR CRI Docker at some point and that then gives you the API Surface to plug in whichever container engine you could choose Yep, great question. I alluded to that a little bit during my portion of it And I think you're going to see some other interesting Wrinkles come up as people look at different facets of trying to address this as we go into next year The only constant is change Next question So one question from practical side What's the plan of the OpenStack community to make containers the first-class citizen because right now to me it looks like you know when you deploy containers you still in Magnum you still have virtual machines in between and This is something for me like a grown solution because I would expect that containers are some sort of first-class citizens within OpenStack Want to take that one I was gonna say I can answer from the Kubernetes side, but go for it. No, that's okay So in my world in the future where I get to decide things Kubernetes launches OpenStack control plane and then you have OpenStack managing its cluster for VMs And you have Kubernetes running its own cluster for Containers now there's certainly a space With many of the projects where you are projects inside OpenStack right now where they are running They are actually running Containers on top of VMs now, which I think is your point Why would you can run a VM and then run containers on top of that? So the way that I have seen that work so far is to sort of separate them either with the third way IBM's Two independent stacks or with Kubernetes launching the control plane for OpenStack I have not seen any work Please correct me if I'm wrong that yet says here is a cluster for containers that OpenStack can manage by running Kubernetes in its other space No, but I believe there's integration with with ironic So I would cut out a bit of that overhead. Okay, but I don't know what the current state of that one is Yeah, cuz Cola still is launching containers on top of VMs, right? Yes. Yeah, okay So the answer is we don't know yet actually the demo today showed I think that they're now able to do that a bare metal to The keynote may have shown today that they can launch containers on bare metal So I get to live in a new world. We deploy OpenStack in containers on bare metal we We struggle a lot and I'm sorry because OpenStack is not that easy to containerize a lot of things don't work as Expected in a container world so I'm I'm asking myself who is bringing the container requirements into the OpenStack applications because applications that just hang because a rabbit in queue is not there is not that container friendly. Yeah, it's like I Think that there is work being done between the two communities to make sure that The at least I know many of the contributors to Kubernetes SIG OpenStack are trying to feed back into the OpenStack Projects just exactly those requirements now specifically around containerizing OpenStack or OpenStack as a control plane the work that Marantis and core OS have been doing are the two those are the two groups that I know that are they're spending the most time trying to improve the work or Improve the projects inside OpenStack that would be containerized to run that So I don't know that I have a very good answer other than we're working on trying to make communications better in both ways And we hope to be back here in six months and talk about the progress. Yeah I was gonna say is there such a thing as special interest groups Do you need a special interest group Kubernetes to try and or to special interest group containers to try to containerize more of the Projects or the projects are all pretty siloed in OpenStack governance, right? Yeah, okay Any more questions We're just about out of time But in addition to this project, what else is Google doing in open source? Can you mention a couple of other highlights? Oh, I'd be happy to Because as I am working on the Kubernetes community as my primary focus. I'm also helping more of the Google Cloud Open source projects and there are three other ones off the top of my head that I can think of and I'm helping them work on Their community engagement as well. So TensorFlow, which of course is the Is the machine learning tool set and neural network tool set that exists coming out of Google That team is working on and trying to build an engaged community that makes use of machine learning models There is Apache beam, which is the Google Cloud data flow Version that has been open source. So it's out in the Apache project They've made a very different choice than Kubernetes did and then there is also gRPC Which brings us a an underlying communications mechanism including things relating to Protobuf and getting communications between cloud different different cloud architectures gRPC is actually one of the projects that just got pitched to the cloud native compute foundation as well So that may end up in that in there as well Good answer for a question. You didn't even know was coming. I didn't even know but Google and IBM are both also working in a emerging community around the concept of an open API initiative and It's based upon the swagger project. How many have heard of swagger? so Taking that project from a single BDFL towards a more open governance model is something that Both Google IBM and others are collaborating on and if you want to find out more about other open source projects that IBM Is originating you can check out developer works open It's a website where you can find out some of the latest projects an example of one that was on Developer works open earlier this year as the IBM open blockchain project and that graduated About mid-year into the Linux foundation as the hyper ledger project So lots of interesting things happening in open source. Thanks for joining us for today's session If you have any other questions come on up front and see us. We'll be right over here. Thank you


Hello students, I am Bagesh Deshmukh from Valchand Institute of Technology Solapur Mechanical Engineering Department. This session is on endurance limit, the method to obtain the endurance limit by approximate estimation. At the end of this session, we will be able to calculate the endurance limit by approximation method. Dear students, what is the necessity to use this method? You may think upon why it is necessary to use this approximation method. You may recall what were the issues regarding the method by R R Moore, the laboratory method. We obtain the endurance limit by the method on the x axis we have taken number of cycles and on the y axis we have taken the amplitude stress. However, what has happened? I need to take the first trial, obtain the first point. I need to take the second trial, obtain the second point. Every time I need to change the component, because the component is the specimen instead of saying component, it will be better to say the specimen because it is a laboratory method. Component which is to be used in the service. It is basic difference between specimen and a component. The method of R R Moore is used for specimen rather than the component. That means I need to use first specimen, throw it away, second specimen, get the value, throw it away, third specimen, get the point by S and N value, get this point. Same thing I need to repeat for the next, get the next point. For each point I need to use a different specimen. Then draw this curve, then obtain this line and then get the required value of S E. This is for specimen. The method as seen over here is time consuming, laborious and there may be variation in the answers obtained by this method. Therefore, it becomes necessary to use some different method. Let us see the next method which is called as the approximate method. Then how to use this approximation method? I need to use two notations. I need to first correlate S U T value with S E somehow. Then how to correlate it with S E? I need to use the equation S E dash equals 0.5 S U T if it is steel. This is the standard relation that we can use. That means with the help of the mechanical property, because S U T we can call it as a mechanical property, we can correlate S U T to S E dash. Then what is S E dash? We are going to use the notation, the symbol S E dash is the endurance limit of a specimen and S E is the endurance limit of a component. Dear friends, our interest is a component. R R Moore's method was useful for getting the endurance limit of a specimen. What we are doing? Here we are using the approximate relation of S U T and S E dash. We are correlating it with S E. How to do this? I need to use few D rating factors. Then why I have called D rating factors? Dear friends, S E dash is the endurance limit of a specimen. The specimen is highly polished, then it has a size, the minimum diameter is 7.5. The expected reliability for the test of R R Moore is 50% and there is no further notch in the component. Therefore, this value is of ideal specimen. If I am going to correlate it with the endurance limit of a component, I need to use D rating factors as K A, K B, K C, K D and if I multiply these four factors with S E dash, then I am going to get the value S E. Here S E is of the component. My interest is to get this S E value. Then how to get this? K is going to reduce this value of S E dash, K B is also going to reduce the value of S E dash, K C is also going to reduce the value of S E dash, K D is also going to reduce the value of S E dash. Therefore, these factors are called as D rating factors. What is going to happen? That S E will be always less than S E dash or in ideal case, S E equals S E dash. Therefore, all these factors, the highest value will be equal to one. In normal cases, the values are less than one or in fraction. Let us see various factors. The first factor is the K, which is called as a surface finish factor. If I am going to use this surface finish factor, I already told the necessity. The reason is the component is not polished as that of the specimen. Therefore, I need to use this K factor. Let us assume that the tensile strength of the component material is 800 and the method of manufacturing is this line, the forging. I need to then move up. I need to find out this intersection. Let us see the intersection over here.  Therefore, K, I can get it from the chart. You can see over here, if the component is polished, the surface finish factor is going to be equal to one because it is ideal case matching with the specimen. Let us see the next factor, next derating factor, which is called as the size factor. There is a typical chart given for the size factor. The normal case, the dimension was 7.5 for the specimen. However, there can be varied dimensions of the component in practice. Therefore, there can be different ranges taken. Ideal dimension less than 5 or equal to 5, 7.5, the KB value, the size factor is going to be equal to one. It is the ideal case. In case the dimension under consideration, I am calling it as dimension not the diameter, if the dimension is greater than 50, then the factor is going to be equal to 0.75. However, if the dimension is not known and you are going to find out the dimensions, in that case of ambiguity, you may assume the value of important dimension to be existing in 7.5 to 50 and refer the value of size factor KB as 0.85. Therefore KB, I can say that it can be obtained from the table. The value is 1, it can be up to 0.75. This is the second factor that has been considered. Let us see the third factor. Third derating factor is the reliability factor. The RR Moore's method, it was developed on the basis of 50% reliability. However, in service, there can be different requirement of the reliability. If the reliability is 50% as in ideal case, then the reliability factor is going to be equal to 1. However, if the reliability of the component which is to be kept in the service is going on increasing, increase, this value is increased, the factor is decreasing. Then KC, the value, this is given in between 0.659 to 1 as per the reliability required of the component. Remember, if the reliability is not mentioned in the numerical, if it is given, you may assume that it is based on the 50% reliability. However, in practice, if you need higher reliability of the component, then the designer has to choose the higher reliability thereby reducing the reliability factor. Then what will be the effect of it? If I am using the less number, this number will be lesser for higher reliability, I am going to estimate SE, SE will be lesser in that case because this factor will be 0.659 times this SE dash. I am going to derate this value, I am going to design for the lesser value so that the components dimension will be higher than that of the reliability equal to 50%. In that case, I am going to design the component on the higher end, higher side, the dimension of the component will be larger for the increased reliability. That is what is the significance of this factor. It plays very important role when we design the component. If the reliability factor is going to, reliability is increasing, the factor is going to be decreasing and in that case, the SE value will be going on decreasing as compared with the standard value of SE dash. SE dash is the endurance limit of a specimen and SE is the endurance limit of the component that is to be kept into the service. Then after this, there is the fourth factor which is going to be considered for the design. It is the modifying factor. Modifying factor KD equals 1 upon KF. Then what is 1 upon KF? KF we can say that KF is 1 plus Q into bracket KT minus 1. And in this equation, QE is the notch sensitivity, KT is the theoretical stress concentration factor. Dear friends, it is important if there is no notch, there will not be stress concentration then this factor will be equal to 1 in that case. That means there will not be any effect of this stress concentration notch on the endurance limit of a component. The value in that case will be KD you need to check upon. Then after, if I say that how to get this value of SE, SE will be equal to KAKBKCKD into SE dash. This is what is the final formula of the endurance limit. We are considering only four factors, there can be more factors, however we have limited our scope to only these four factors. It is going to give me the endurance limit of a component which is subjected to this bending. However, if the component is subjected to axial loading then SE for that axial loading condition load axial varying load or fluctuating or reverse load I need to take it as 0.8 times SE. This is also one of the important relations that we may need to use while solving various problems based on this reverse loading. This method is called as the approximate estimation of endurance limit. You may need to use this method many times. Thank you. Thank you.


And now, stay tuned for the program that has rated tops in popularity for a longer period of time than any other West Coast program in radio history. The Signal Oil Program, The Whistler.  I am The Whistler, and I know many things for I walk by night. I know many strange tales hidden in the hearts of men and women who have stepped into the shadows. Yes, I know the nameless terrors of which they dare not speak. And now for the Signal Oil Company, The Whistler's strange story. She never would be missed. Mona had determined that her parting from her husband, Gerald Stanton, was to be gay, and as she put it, civilized. There would be no tears to mar Mona's beauty, no tiresome recriminations. Best of all, Gerald had understood her perfectly. He had seemed to realize at once why she preferred Vincent, why the divorce was so very necessary to her. And now there was nothing more for Mona to do other than wait for train time. Check on the few last-minute details with her maid. Oh, Lucille, did the man come for my luggage? He just left me then. You made it clear that I wanted to arrive in Reno the same time I do? Yes, and I phoned for a cab. It will be right here. You're an angel, Lucille. You've been so good through all this. You don't know what it means to find someone who's charming after so many years of... So many years of what, my dear? Gerald. Gerald, what are you doing here? I thought you'd gone to your club. I came back because I have something to say to you. I'll watch for your cab, madam. Thank you, Lucille. Mona, I want you to give up this foolish idea. Give it up. That's absurd. Everything settled. You agreed. I didn't know until today just whom I was being divorced for. You've always known it was Vincent. We've never made any secret of it. But I knew nothing about him. He's no good, Mona. I can understand your thinking so. It isn't just me. Do you realize he's been thrown out of every decent club in San Francisco? Why, no respectable society will tolerate him. You think you'll be happy married to that? I've never been able to understand your reverence for what you call respectability. He's a bounder, Mona. A cheat. Everything that's rotten. In short, a juicy topic for a club full of old men. It always comes back to that, doesn't it? You're young and I'm old. It's time we faced it, don't you think? Mona, believe me. If it were anyone else, I'd let you go. No protest. But this Carter, for your own sake, I beg you not to give up everything for him. I love Vincent and he loves me. You can protest or not as you like. I could make it very disagreeable, Mona, for both of you. Of course you could. You get into all the papers too. But I don't think you will. Where would your respectability be then? I think I lost it, Mona, when I married you. Your cab is here, Mrs. Stanton. I'll be right down, Lucille. Goodbye, gentlemen. One thing more, Mona.  There will be no property settlement. Now we come to the heart of the interview. If you leave here, you'll get nothing more from me. Vincent has enough for us both. It had better be a lot. You're rather expensive. I expect to be well-picked. If he marries you. Don't worry, Gerald. He will. Well, that's fair enough. Fair enough, Mona. You deserve each other. Car number 32, right here. Thank you. Say goodbye to me now, Vincent. I can't bear these prolonged farewells. Darling, here's something to remember me by. What is it? Open it and see. Vincent would a perfectly stunning ring. You like it? It's been in the family for ages. Oh, Vincent, I do love you, sir. Wire me when it's over and I'll meet you here at the station. Oh, no, darling, not at the station. I want to look my very best when I see you. Can't we make... How far away we always meet. Pietro's for lunch. One o'clock the day you get back. One o'clock. You'd better be wearing that ring. You'll see me flashing blocks away. There it is, darling. I've got to run. Goodbye, Angel. I'll be living for our lunch at Pietro's, darling. The goodbyes are over, aren't they, Mona? And you're on your way, alone on the train. Only the memory of Vincent's flashing smile to comfort you. To help you fight down any doubts, any misgivings that Gerald tried to plant in your mind. It's going to be all right, isn't it, Mona? Yes. You tell yourself that over and over again. But in the weeks you spend at Reno, you get few letters from Vincent. And then none at all. And then at last, you return to San Francisco, hurry to Pietro's, where you wait again. Because Vincent isn't there. You're terribly alone until... Pietro? Pietro? What is it, madame? Oh, Mrs. Stanton, I didn't see you come in. Welcome back. Pietro, for heaven's sakes, where is Vincent? When did you get back? Just this morning. Please, Pietro, where is he? Mr. Carter? I haven't seen him. He was to meet me here at one o'clock. I've called his apartment everywhere. I can't find him. What's happened? I'm afraid I don't know. That nonsense. You know everything, Pietro. There's something you're not telling me. I'm sorry, Mrs. Stanton. Uh, no, if you excuse me. No, I won't excuse you. Pietro, come back here. I want to talk to you. You're getting a little shrill, darling. You better take it easy. Oh, Blanche Frontaine, thank goodness for a friendly face. Maybe you'll tell me what this is all about. I won't pretend I don't know what you mean, because I do. What is it? What happened to Vincent? Not here. Everybody's watching us. Come on. Where are we going? To my apartment. We can talk there. Now, Blanche, please. I said we'd talk in my apartment. Now, come on. I know how you feel, Mona, but a lot can happen in six weeks, and... Well, it has. I can't believe it, Blanche. Who is this other woman? Alice Phyllis. Alice. Do you mean Vincent has thrown me over for that washed-out society, bud? I'll admit she is a pale one, but her family, my dear. Mainline, old God, and, oh, so respectable. Respectable. Oh, this is too much. I shouldn't surprise you. Vincent's always been a perfect sucker for that sort of thing. But he can't. He's going to marry me. I have his ring. Darling, what's a ring when he can marry a Phillips? This is the top for him. Big stop. He'll never let that go. I think you're cruel to say things like that. I face fats, Mona, and so must you. Now, forget it. Go away for a while. Pull yourself together. Exit gracefully, you mean? You can go up to my lodge, if you like. You'll be alone there, miles from everywhere. It'll give you time to get hold of yourself. Vincent loves me. I've given up everything for him. Husband, money, everything. I'll find him and talk to him. He'll say it isn't true. All right, darling. Have it your way. I will. You'll see. It can't be said that you didn't try. Can it, Mona? Your efforts during the next few days to find Vincent may well become legendary in the lush circles you inhabit. You phone his apartment, his friends, all the possible nightclubs. But he's never there. You write him notes and long, pleading letters, but they remain unanswered. And still, you refuse to accept the obvious. Finally, one afternoon at the cocktail hour, you catch him at Pietro's. He's as handsome as ever, but you're forced to see that things aren't the same now. Vincent has changed. Yes, I heard you were trying to reach me, Mona, but I really wish you wouldn't. It's rather awkward under the circumstances. Vincent, what are the circumstances? Oh, we know each other too well to pretend ignorance. Then it is true. Alice Phillips. Vincent, you can't do this to me. Well, nobody's done anything, Mona. It simply happened. And so I'm to be brushed off just like that. We should be grateful we found out before it was too late. Late? Do you realize what I've lost on your account? Well, that was your doing, Mona, not mine. Oh, you're contemptible. Just honest. Vincent, you don't love her. You couldn't. You love me. And it's all right, darling. I know these things happen sometimes, and I'm willing to forget it. Perhaps you haven't understood me, Mona. This isn't just a temporary romance. I'm going to marry Alice. Vincent. Which reminds me, darling, I'd like to have my ring back if you don't mind. It's a rather good one, you know, sort of heirloom. And I think Alice... Your ring, indeed. Oh, you! Just try and get it. All right, Mona. But you can get out of my life and stay out. Mrs. Stanton, please, I'll have to ask you... Oh, get away, Pietro. Would you like me to call you again? Get away, I said! Take a hand off of me! Mona, for heaven's sake, control yourself. You're making a spank. Control yourself, he says. Oh, that's good. That's very good. And quit hounding me, or you'll force me to do something unpleasant. Come, come, Mrs. Stanton. Let go of me! Please, wait, please. You'll never marry her, Vincent Carter! Not while I live!   Next weekend, before you start off on your Labor Day trip, wouldn't it add a lot to your peace of mind to know that no matter how hard you may drive, no matter how high the thermometer may soar, your motor is protected by an oil that won't break down under heat, an oil that won't let unnecessary wear rob your car of its pep and power and turn it into an oil eater. Then this week is the time to change to new signal premium, the wonderful new signal motor oil that reduces engine wear due to lubrication, 50%. In addition to providing the finest of lubrication, new signal premium protects your motor in four important extra ways. One controls harmful engine deposits such as carbon, gum and varnish. Two keeps oil rings clean and free. Three keeps hydraulic valve lifters from sticking. Four stops acid corrosion and rust. Yet all this extra protection of heavy duty type signal premium is yours at no increase in price at signal stations. So if you want to save money and your car too, get your motor oil change to new signal premium before your Labor Day trip. Get it changed at a signal service station. Well, Mona, you sensed it for weeks that something was wrong. That Vincent Carter had changed his mind about you after you've divorced your husband to marry him. And now meeting him face to face, you've heard from his own lips that he intended to marry someone else, Alice Phillips.   Yet you've been able to do nothing, nothing at all, except run to your friend, Blanche Fontaine, and pour out your heart. Oh, Blanche, it was so humiliating. And on top of that to be thrown out, what am I going to do? I've told you, Mona, go away somewhere by yourself and get over it. Go up to my lodge, darling. I'm running over to London for a few weeks. I shan't be using it. I've lost everything because of him. How could he do this to me? Why not? He's done it to every woman he's ever known. I wish I could hurt him as he's hurt me. You can't. It doesn't work that way with Vincent. When he's through, he's through. And like the old song, they never would be missed. They never would be missed. Here now.  You'll be alone there. It's miles from everywhere. Nobody has to know anything about it. You're very kind, Blanche. No foe, nothing. It'll be good for you. The lodge is well-stopped. You'll make out. I'll make out better, right here.  Just stay as long as you like. Blanche, if you think I'm just going to leave town quietly and sneak up to your lodge and let Vincent come to get... That's the sensible thing to do. You should begin to use your head. I'll use my head. But I won't use your lodge. Suit yourself. But in case you change your mind, I'll leave you the keys. Goodbye, darling.  Have a nice trip, Blanche. Oh, Vincent, you... Oh. Here's one who's going to be... missed. It's a vicious plan, isn't it, Mona? But you've decided, yes, to disappear suddenly and without explanation. You'll do it in such a way that Vincent Carter will be blamed for your disappearance. You're certain that the publicity, the suspicions in his direction will cause the ultra-respectable Alice Phillips to break off her engagement to him.  Only Blanche knows that you know of the existence of the lodge and you've told her you weren't going to use it. You're sure she'll be on the high seas bound for London and will learn nothing until her return. The next day, a phone called of Vincent is your first move in working him into your little scheme. I don't know what possessed me, Vincent. I was dreadful and I'm terribly sorry. It's all right, Mona. Alice is a lovely girl and I think she ought to have the ring. Of course. Come over and have a drink with me. Show me there are no hard feelings. I'll give it to you then. I'll come by. Just for a minute. Done and done, darling. See you. Lucille? Yes, madame? I'll be dining out, Lucille. Fetch me something to wear and hurry. Mr. Carter's coming right away. Mr. Carter? Yes, he just called. Asked me to have dinner. But you think you should. Why not? If he wants me back, I'm quite willing. But Mrs. Stanton, how do you know that's what he wants? How do you know it isn't? What do you mean, Lucille? Well, he called here yesterday when you were out and he said dreadful things. He said that if you didn't quit bothering him he would do something drastic. I didn't tell you that because I... But that was yesterday, Lucille. Oh, don't worry, I can handle him. Oh, I hope so, madame. But, Lucille, please don't tell anyone who I'm with. I promised Vincent he doesn't want it known yet. I don't like it, madame. I don't like it at all. Nonsense! Come on, help me get ready. He'll be here. You've been very decent, Mona. Thanks awfully. Well, after all, darling, when I have a ring I want a man to go with it. Have another drink? No thanks. I'd better run along. Must you. I was rather hoping you'd let me take you to dinner sort of farewell. Oh, I'm afraid... It's a divine little place just out of town. Very quiet. Nobody'd know. You're very persuasive. For old time's sake. We can take my car. What do you say? All right, I'd rather like to. It's all so easy, isn't it, Mona? You go downstairs with him. Make sure the doorman sees you drive off together in your car. The dinner at the obscure country inn goes pleasantly, with Vincent obviously relieved at your show of goodwill.  Here you are, darling, right to your door. Go straight to bed now. Oh, I will. I will. I'm tired. Au revoir. It's been fun, Mona. Fun's just beginning, darling, for both of us. And now, Mona, the easy four-hour drive to the lodge, where you run your car out of sight behind some trees, then settle down amid the comforting simplicity of oil lamps and wood fires, certain that the mechanics of your scheme are going successfully. Yes, your last scene with Vincent and your disappearance is complete. The news breaks even sooner than you expected, and you walk down behind the clump of trees to listen to your car radio and the news reports. San Francisco police were still continuing their questioning today concerning the sudden and unusual disappearance of Mrs. Mona Stanton. The maid stated emphatically that her employer had no intention of taking a trip and expressed the possibility of foul play. The police are dissatisfied with the explanations of one Vincent Carter, former fiance of the missing woman. It's perfect, isn't it, Mona? And the following day, the reports are even more exciting, until finally the one thing you most wanted to hear. In the case of Mrs. Mona Stanton missing for the past five days, socialite Alice Phillips flew to Santa Barbara tonight, accompanied by her mother. Sources close to Ms. Phillips indicate that she has broken her engagement of Vincent Carter and principal suspect in the mysterious Stanton disappearance. And now for some other close news. It's as if he wouldn't stick by you, Vincent there. Too respectable. You've won, haven't you, Mona? You tell yourself over and over again you've won. Vincent has been humbled, Alice driven away. You can return to him now, take him back on your own terms. And then as you finish packing for the trip back to the city and close your suitcase, you hear a car approaching the lodge. Only one person knows you're here, Mona, just one. Blanche! It has to be Blanche. She's bringing the police. I've got to get out of here. It's all clear to you, isn't it, Mona? Blanche must have heard of your disappearance before she embarked for London. Changed her plans and hurried back to San Francisco to investigate. You've got to hurry and get away. You race for the rear door to the cabin and the lamp crashes to the floor as you swing the door wide open, Mona. You're not stopping for anything like that now. No, you race to the clump of trees in your car. Your only chance to get away without being seen is the old river road. You noticed it while walking one day. Now it's got to provide your escape. Your heart pounds as you release the brake. Let your car coast silently down this back road. A mile from the lodge you risk starting the engine. It's all right, isn't it, Mona? And exactly four hours later, you're walking in on Vincent at his apartment. Mona! Had enough, Vincent, darling? I could disappear again, you know. Come in. Come in, Mona. Ready to listen to reason, I take it. It's close in here, darling. Untidy, too. But you don't look too dapper yourself. What do you mean, Mona? What do I mean? You asked me up, didn't you?  Why bother to come back at all? I want a husband, darling, in security. I want you. Security? You don't have to lock the door. I shan't run away so long as you're reasonable. That's right, Mona. You won't run away. Ever. Vincent, what are you doing?  Now I'll have mine. Oh, come now, darling, put it down. You don't deserve to live. I said put the gun down, Vincent. Keep away. Come on, give it to me. Let go, Mona. Let go, I say. Boy, you little... High heels can be rather painful, can't they, Vincent? Now our places are reversed. You're the one who doesn't deserve to live. I was only trying to scare you, Mona. I wouldn't have killed you.  No, no, please, Mona. Wait a minute. Why should I?  I'm just turning the tables on you, that's all. You stand there, Mona, terrified at what you've done.  Then as the paralysis of shocks subsides, you begin to realize your own danger.  It comes back to you in your own words, shouted publicly that day at Pietro's. You'll never marry her, Vincent Carver.   And who's going to believe that you didn't intend to? Suddenly you lean down, quickly press the gun into Vincent's hand, smooth over the evidence of the struggle and slip out of the apartment. Within a half hour you're at police headquarters telling a plausible story to the lieutenant in charge. You see, Lieutenant, I'd gone up to the lodge for a complete rest, so I hadn't even heard a radio until a few hours ago. I happened to turn on the six o'clock news and there was an appearance, but naturally I came back at once. I see. I'm afraid it's been a pretty serious mistake all around. It's dreadful. Well, let Vincent know immediately. I'm afraid it's too late in the system. What? The report just came in. Vincent Carter shot himself not more than half an hour ago. He... Oh, no. Steady. Steady. It's all my fault. I hadn't gone away. I wouldn't say that. You didn't know. Oh, what shall I do if only I hadn't... Best thing is to go home and try to get some rest. Oh, I couldn't. Not now, not when... Try, though, will you? It's too bad, but you're not to blame. Oh, no, but in that... I'll try. Next weekend, when you start off on your Labor Day trip, it'll be mighty handy to have a good map in your car. And there's no map handier than the three ones you'll find at Signal Service Station. No need to squint to find where you're going on a Signal map. They're jumbo size for quick, easy reading. And no need to wrestle with them, getting them open or folded again. Signal maps have the latest accordion fold for more convenient handling. But that's only the beginning. In addition, Signal maps contain a guide to interesting places to visit, plus a traveler's radio guide so you can follow your favorite programs as you travel, plus and large sections of metropolitan areas. And if you happen to need a street map to guide you in the larger cities of the Pacific Coast states, Signal stations have them free, too. In fact, whether you need a free map, some helpful advice, or just a tank full of the famous go farther gasoline, you'll find that friendly, independently operated Signal stations have just about everything it takes to make your driving over Labor Day or any day more pleasant. It's a shock, isn't it, Mona? Your disappearing act had unexpected results.  It appears that you had nothing to do with it because of your story that you were in your car at the time, driving back from the lodge to save Vincent from the suspicion that he had done away with you. And they can only think of you as an innocent figure in a comedy of misinterpretation. The next day, the police lieutenant comes to your apartment. Confidently, you answer his questions with your usual inventive. I told you all I can, Lieutenant. I left the lodge right after the 6 o'clock news broadcast. When I heard on the newscast that Vincent was being blamed for my disappearance, I went back to Captain. But what difference does it make now? Because, Mrs. Stanton, Vincent Carter's death wasn't suicide. Wasn't suicide? You mean Vincent was... Murdered, Mrs. Stanton. The angle of the bullet through the shot couldn't have been fired by Mr. Carter. Let's see. But surely you don't suspect me. Yes, I'm afraid I do. You have the strongest motive in the world. I've learned a great deal about you since I last saw you, Mrs. Stanton. Mr. Carter broke up your marriage, then tossed you aside for another woman. But that was some time ago since then. At least two different people heard you threatened to kill him. But I told you that was... We've got a pretty strong case against you, Mrs. Stanton. A woman answering your description was seen leaving Carter's apartment building about the time of the murder. Possibly so, but it couldn't have been I. I was driving into town. Let's see. Now, as I understand it, it's an easy four-hour drive from the lodge into town, right? Yes. Now, you say you left there right after the six o'clock news guest. You didn't arrive at the precinct station until nearly 12. That's almost six hours. That leaves two hours to account for. That's plenty of time for you to kill Carter. Oh, well, I can explain that. You see, I went to the village first, had a little lunch before driving in, and since I didn't realize there was any rush, I ate rather leisurely. Then I decided to phone or wire or something, but changed my mind and drove on in. Well, I see. Don't you have to pass the lodge? Well, yes. Then I'm afraid I'm going to have to arrest you in the charge of murder, Mrs. Stanton. But that's absurd. Why need you? Because you're lying. You couldn't have passed that lodge. The road was blocked. The lodge was burning to the ground. Somebody was in a big hurry to get out of that lodge. In the rush, they knocked over an oil lamp. Oh, it's only Blanche Fontaine hadn't driven up. Miss Fontaine's still in London. That car you heard was a couple of forest rangers. Thank you. Lucky thing they were in that neighborhood. We might have had a bad forest fight. Come along, Mrs. Stanton. Let's go down the head for it. Let that whistle be your signal for the signal oil program the Whistler each Sunday night at the same time. Signal Oil Company has asked me to remind you that starting next Friday, a heavy holiday-bound Labor Day traffic will make it even more important to drive at sensible speeds, be courteous, and obey traffic regulations. It may save a life, possibly your own. Featured in tonight's story were Bill Foreman, Alice Reinhardt, Les Premaine, Joe Gilbert, Ted Von Els, and Bill Boucher. The Whistler was produced and directed by George W. Allen, with story by William Engvich and Cleo Davis, music by Wilbur Hatch, and was transmitted overseas by the Armed Forces Radio Service. The Whistler is entirely fictional, and all characters portrayed on the Whistler are also fictional. The polarity of names or resemblance to persons living or dead is purely coincidental. Remember to tune in at the same time next Sunday when the Signal Oil Company will bring you another strange story by the Whistler. Marvin Miller speaking for the Signal Oil Company. Stay tuned now for the Horace Height Show, which follows immediately over most of these stations. This is the CBS Radio Network.


Welcome back to the breakfast and plus TV Africa. Let's go back in history to the year 1961. It was on this day that one of Nigeria's, well, currently most famous politicians and from a governor of Anambra State, Peter Obi, was born in 1961 on this day. Of course, if you remember, not very long ago in 2019, was the vice presidential candidate of the PDP in the last elections. So just go back a little bit to share. Just a little, you know, tiny bit on Peter Obi. He was born on this day 19th of July 1961. He is a Nigerian politician and businessman who, of course, was vice presidential candidate in 2019. He, of course, is from a governor of Anambra State that served from 17th of March 2006 to the 2nd of November 2006 when he was impeached. Then, of course, when that impeachment was overturned, returned from the 9th of February 2007 to the 29th of May 2007, he then, of course, got another four-year tenure after he won that court case. He, you know, of course, is known to be a successful, very successful businessman who was chairman of Next International Nigeria Limited, chairman and director then of Guardian Express, Modgid Bank, Guardian Express Bank, PLC, Future View Securities Limited, Paymaster Nigeria Limited, Champs Nigeria Limited, so many of them. And also, at some point, was also appointed chairman of the Security and Action Commission by former president Goodluck Jonathan after the 2015 general elections. So we say happy birthday to Peter Obi. He is, of course, one of those governors from the southeast or one of those politicians from the southeast who has, you know, reasonably had a very, very clean record and has also been praised for being the one who transformed, you know, a lot with regards to Anambra State, Anambra's economy and the infrastructural development in Anambra State in the time that he was also there. He was, you know, his ideas and some of the things that he had mentioned in the build-up to the elections in 2019 are some of the things that, you know, the government is currently still, of course, looking at today. So happy birthday to Peter Obi and we wish him many, many, many more years on Earth. Indeed. Happy birthday to him. Let's now go to the year 2017. And on this day in history, there was a, you know, a requirement by the government for organizations to reveal the salaries of their staff, their workers. And on this day in history, July 19th, 2017, the British Broadcasting Corporation, BBC, published the salaries of its top earning journalists and presenters. And we found that this was two-thirds male, Chris Evans. Salary was the highest at over 2.2 million pounds. This was big. Sorry, are you crying? You can't compare your salary first of all as in Nigeria and so there's, out of the country. So please don't cry. You might get there. Just work hard and all. And we'll look at this, maybe. What is he doing that I'm not doing? A lot. A whole lot. What is he doing that I'm not? Do you have any accent? So back to the story. This list that the BBC published was a list of 96 stars, journalists and presenters, who end between 150,000 pounds or 195,000 dollars or more per year. You don't need to be depressed about that. Come on, it's a bit better for us here in Nigeria. And together, their earnings total more than 30 million pounds. Like I mentioned, the 94-year-old broadcaster had been facing pressure to release details about their spending, about how the TV licence fee has been spent. And of this 96 lists, 96 man lists or 96 people lists, only 34 of them were women. The remaining 62 were men. The salaries of female presenters were largely, largely dwarfed by their male counterpart. Their male counterpart earned much, much more. So when you see presenters like that on your screen, the man is receiving a higher pay than the woman. Most likely, according to what we saw on that list. So overall, 25% of men on that list received more than 250,000 pounds per year compared to just nine women. Now this announcement raised more questions than it answered because the questions were for you to release the list. Let's see how the TV licence fee has been spent. Let's see what the money is going into. So you release this list and people have more questions. Like why are men receiving more than women? I mean, they're both anchoring the same show or walking in the same place doing the same amount of work. Maybe the woman even does more. So it just raised a lot regarding the gender equality, the more paid, the gender gap story, the gender gap conversation became really big at that time. And I found that people who did lots of work in the station like production assistants and runners, people who played a huge role in the success of production and the list. So it wasn't this thing in history that the BBC made this reveal and it really, really shaped the cost of conversation regarding gender pay and how women should begin to demand for more and how they should receive more if they're doing equal or even more work than the men. So it wasn't this thing in history that we saw this big reveal in the media. Well, not necessarily more work, but as long as you're doing the same job, the same and I agree that there should be better conversations with regards to gender pay gap. We've had some crisis in sports before, but people have always argued against the sports one because the earnings with male sports has always really simply been way higher than the earnings with female sports and so you don't expect them to earn more or end the same thing with the male counterparts. But for TV presenters, for journalists, and everyone in the media space who's most likely doing the same things, have the same screen time, carrying out the same research, doing the same reporting here and there, then obviously you definitely should earn pretty much the same. I don't know how they get into agreeing on what their wages are for a person to be earning two million pounds annually. That is just completely insane. But I think it's also dependent on traffic and what that particular presenter brings to the station itself because there are particular presenters on BBC and on CNN that nobody even recognizes or knows that they exist, but they're also the ones that people look forward to seeing. They look forward to watching. It's the same screen time, one person's delivery and one person's conversations are a lot richer than the next person's conversation. There are certain shows on CNN, not just CNN, any international media organization that you really watch because of one particular person. If I read Zakaria, for example, I don't think it would be earning the same fees with Don Lemon because they would likely have the same screen time, but their conversations are totally different. One person probably pulls in more traffic, raises more money for the station. I believe that at some point during the course of their time there, there can be renegotiation of their contracts that would push them a lot higher than what they initially started with. So I feel, yes, there should be some equality with regards to... But when we bring that to Nigeria, the conversation is different because when it comes to male and female, the societal stereotype, believe that the man has more responsibilities. And this is crazy because I don't really see why your family responsibilities should factor into what the salary should be because it's about what you're bringing to the table. You can have a million people you're feeding, but you're not doing so much. I don't necessarily agree. I am telling you for a fact what's happening here. Okay, do you want to ask... No, hold on. Do you want to ask hiring managers? It's a fact that men earn more than women, especially in the media. It's a fact. But the challenge here is... So this is where my challenge is... I'm trying to tell you that this is where it's coming from. No, and that's what I don't agree with. I don't think it's because of your man's responsibility. Listen, I'm telling you what I know for a fact. They will tell you that the man has more responsibilities. They will tell you that the man is older here. They will tell you that the woman is younger. They can't pay a 24-year-old a certain amount. What does she do with the money? This is the stereotype that is prevalent in the Nigerian society. I'm going to ask HR managers for confirmation. Whatever their own reasons might be, I don't know. But the one I know for a fact is what I have just told you regarding the Nigerian society and why... I think the challenge is... I don't argue with the favoritism that will exist. That does exist in the Nigerian space with regards to pay. I would agree that that does exist. One of the things that we are likely to be talking about today is the fact that there are seven bank MDs now in Nigeria, which everyone is talking about. That's just 27% compared to all the banks. Normally it should not even be something that we should have a conversation about because it should be normal that men and women should be able to reach that height. It shouldn't be a big deal. I don't disagree that there is that disparity with regards to pay. I have a challenge. Is you calling it a fact that the reason is because they say that men have more responsibility? I said the reason from my own experience. Well, it's still not a fact. My experience is a fact. I don't know whatever you might have heard. If you've heard your own reasons why people or HR managers would pay men more, you can share that with us. I don't know if HR managers would decide to pay a man higher. Simply because a man has more responsibilities. I think it's still very, very dependent on value. Nobody goes to an interview and says, how many wives do you have? We'll pay you one million a month because you have two wives. Why do you think they pay men more in Nigeria? At the level that we are, in every discussion with regards pay, there's always some level of negotiation. If you get to that seat and you have a negotiation that says, you want to be paid a million a month and that is approved, that's what you earn. If the next person comes in and says, he wants to be paid 200,000 a month, that is going to be approved. It's really about what the company at that time, the value of the company at that time feels like you're going to bring in, and if they think that you're worth it, they can afford that person and the value that you're bringing in. It's not necessarily because they look at you and say, you have more responsibilities, so let's pay a million a month. Or you're a woman, so you don't have responsibilities, so let's pay 100,000 a month. I don't think that's how it happens. I think it's really about the negotiation with regards salary at that time. I don't think that the Nigerian workspace has a standard, including in the media with which they pay salaries. I don't think there's a particular standard which is okay. If you're going to be on this level, then that's what you're going to earn. In the federal government jobs, public service, is there a standard for level 13 female and level 13 male? I don't think there is. If you're on level 13, you're on level 13, and that's what you're going to earn. So there's no allowance for husband and allowance for wife or allowance for man and allowance for woman. So we do need that standard in organizations like the media, don't we? Well, still depends on value and what you're bringing. There should be some level, some standard. I understand and I would agree with that. But at the same time, at every discussion for employment, there is always that negotiation that goes on with regards pay. There's females that I know earn 10 times what I earn, and we're still in the same space. It just depends on where you are and the ability of that company to be able to pay you what you're asking for. If you walk into any office and you tell them you don't want to earn anything less than 2 million a month and they feel that you're going to bring that value, then yes, they will give you 2 million a month. The employers who know the woman has that value and will still refuse to give her what she's worth. I wouldn't argue that there's misogynistic... That's the challenge of our society. About these employers, male and female, it's not just men who employ. So it's also females who, from your argument, there's also females who look at other women and say, oh, you don't have responsibility. So let's pay you what, 50,000 a month. It's a societal mindset that really needs to change. We'll take a break here and return with our first big conversation regarding INEC and the electronic transmission of votes. Do stay with us.