A very good evening aspirants. Welcome to the hindu newspaper analysis brought to you by shankarae's academy. Today's date is 25th of january 2024. Displayed here are the list of news articles that we are going to discuss today. So without much delay let us get into the first news article discussion. This image portrays new sound and light show at gold condor fort in Hyderabad. It has been upgraded after three decades and the show depicts the history of the fort. So in this background let us discuss few points about kudub shahi dynasty from prilam's perspective. Firstly what is kudub shahi dynasty? See kudub shahi dynasty refers to the muslim rulers of the gold condor kingdom in the south eastern deccan of india. They are old from 1518 to 1687. Remember they are one of the five successor states of the baamini kingdom. The five successor states are gold condor, bidar, ahamath nahar, bizapur and berar. Now let us see how kudub shahi dynasty gained power in the region. See kuali, kutbul, mulk was an able general in the baamini kingdom. He was a duke and was appointed as the subedar of telangana by sultan muhammad Shah baamini. Later with the disintegration of the baamini kingdom in the early 16th century, kuel mulk gained virtual independence as a result he established the kudub shahi dynasty with gul konda as his headquarters. The kingdom flourished from 1518 until 1687 when aurangizib's army invaded the deccan. Here you can see the extent of the kingdom in the image given here. So the dynasty spanned 171 years in the history of south india and during this period eight kings ruled the land and its people. Remember, kudub shahi rulers were great builders and patrons of learning. They not only patronized persian culture but also the regional culture of the deccan. The gul konda fort, kudub shahi tomb and char minar or proof of their splendid architecture. Now let us see some of the basics about kudub shahi architecture. Firstly, tomes are constructed on a raised square base. Secondly, the main building mostly consists of a single or double storey building with a dome and a huge bulbous dome built on a cylinder. Remember, these bulbous domes offer a profile greater than a hemisphere. Thirdly, a small latized wall can be noticed all around the cylinder. These walls not only cover but also give an ornamental look to the dome. The buildings are aligned in a perfectly symmetrical manner which is a distinct feature of Islamic architecture. Finally, the actual grave of the dome lies underground below the ornated grave in the main hall. The internal ceiling of the dome is painted with the motif of those times. So these are all certain unique features of the kudub shahi architecture. So in this news article discussion, we saw about the kudub shahi dynasty. They ruled from 1518 to 1687 with gul konda as their capital. Kuali Kutmulk who was an able general got virtual independence after the disintegration of Bahamini kingdom and this led to the establishment of kudub shahi dynasty. The kingdom flourished from 1518 until 1687 when Aurangasip's army invaded the Deccan. One of the very speciality about kudub shahi dynasty is their architecture, gul konda fort, kudub shahi tomb and Charminar or the examples for their splendid architecture. So with these learnt points, now let us move on to the next news article discussion. Take a look at this news article. Recently the much avoided merger of Z and Sony Pictures got cancelled by Sony Pictures. So this has created shock waves across the market. Z has asked Sony Pictures to immediately withdraw this termination of the merger and they have asked the Sony Pictures to implement the merger scheme that had been sanctioned by the national company law tribunal. So this is the crux of the news article given here. The news here is not very important but learning about national company law tribunal is very important. So let us learn about NCLT from Praline's perspective. See the NCLT was constituted in 2016 under the Companies Act 2013. So it is a statutory body which means it was created by a parliamentary law. Remember NCLT was formed to deal with corporate disputes that are of civil nature. This means NCLT works on the lines of a normal civil court in the country. But the difference is that they are constituted specially to deal with civil corporate disputes arising under the Companies Act 2013. Note that NCLT decides the matters in accordance with principles of natural justice. Since it is performing the judicial functions the NCLT is also a Kwasi judicial authority. Now let us see about the benches of NCLT. See NCLT has its principal bench at New Delhi. Apart from this it also has other benches at Ahamadabad, Allahabad, Bengaluru, Chandigarh, Chennai, Guwahati, Hyderabad, Kolkata and Mumbai. So with these basics now let us understand the composition of NCLT. See the NCLT consists of a president and some other judicial and technical members. The president of the tribunal will be appointed by the central government after consultation with the chief justice of India. Remember the president of NCLT must be a judge of the high court or he should have been a judge of the high court for five years. Talking about the members, the members of the tribunal are appointed by the central government based on the recommendation of a selection committee. So this is about the composition of NCLT. Now let us one by one look at the important functions of NCLT. Firstly, NCLT adjudicates the cases related to insolvency and liquidation of corporate companies. This is as per the Insolvency and Bankruptcy Code 2016. Remember here also NCLT deals with insolvency of only corporates under the code. But in the case of insolvency proceedings of individuals and partnership firms, it will be dealt by Debt Recovery Tribunal. Secondly, the NCLT deals with the cases pending under the Sick Industrial Company Facial Provision Act 1985. This act was enacted to detect unviable that is the sick companies that has potential systematic financial risk. So if any cases are filed under such act, it will be dealt by the NCLT. Finally, NCLT plays a crucial role in facilitating mergers and acquisitions. See, when two or more companies wish to merge, they must seek the approval of the NCLT. The tribunal examines the proposal and ensures that it is in compliance with the relevant laws and regulations. So if the merger is approved, the NCLT oversees the process of integration and ensures that the interest of all stakeholders are protected. Also note that if anyone is aggravated by the decision of the NCLT, then they can make an appeal before the National Company law appellate tribunal NCLT. And the decision of the NCLT can be appealed to the Supreme Court. So these are all certain important facts that you have to remember about NCLT. NCLT is a statutory body specifically deals with corporate disputes that are of civil nature. NCLT decides the matter in accordance with the principles of natural justice. Apart from that, it helps in insolvency and liquidation of corporate companies. Then it takes cases relevant to sick companies and NCLT oversees the process of integration when two or more companies wish to merge or acquire. So these learned points and now let us move on to the next news article discussion. Look at this news article. According to the news article, the Varanasi District Court ordered that the report of a scientific survey of the Yanwapi mask should be made public. Remember, this survey was conducted by the Archaeological Survey of India ASI. As per the news article, this move will allow all petitioners, both Hindus and Muslims to access the document. So this is the crux of the news article given here. So in this context, let us understand about ASI from Prillam's perspective. Say the Archaeological Survey of India or ASI is a premier institution for doing archaeological research in India. It is an attached agency of the Ministry of Culture Government of India. Know that it engages in archaeological research, protection and conservation of archaeological sites and all archaeological activities in the country is conducted by ASI. The archaeological activities are undertaken under the provisions of the Ancient Monuments and Archaeological Sites and Remains Act AMASR Act 1958 and Antiquities and Art Trusher Act 1972. The findings of ASI are released in their publications. They include Ancient India, Epigraphia, Indica and Indian Archaeology a review. So with these basic understanding about the ASI, let us track back the origin of ASI. See, archaeological and historic pursuits in India began with the effort of Sir William Jones. He founded Asiatic Society on 15th January 1784 in Calcutta. Later in the year 1871, the Archaeological Survey of India was created as a government department with Alexander Cunningham, elected as its first director general. Remember, Alexander Cunningham is also known as the father of Indian Archaeology. Until 1904, there was no legislation to protect the important monuments of the country. But during the time of Lord Cursor, this situation got changed with the passage of Ancient Monuments Preservation Act of 1904. This law gave the ASI a firm footing and since then ASI has been successfully conducting functions like doing excavations, rediscovering the past and safeguarding important heritage structures and etc. After independence, it became a statutory body under the AMASR Act 1958. The ASI is headed by a director general and is headquartered in New Delhi. He is assisted by an additional director general, two joint director general and 17 directors to carry out his duties. So this is regarding the origin of ASI. Now let us see the functions of ASI. Firstly, it conducts archaeological excavation and exploration as we saw earlier. Secondly, it preserves the protected monuments and archaeological sites as they are of national importance. Apart from this, it engages in the chemical protection of monuments and antiquarian remains to preserve it later. Additionally, ASI also performs the Archaeological Survey of Monuments. Not only archaeological studies but also it conducts epigraphical and numismatic studies of the site. To display all these ASI will set up site museums. An important point to note here is that ASI also conducts archaeological expeditions outside India. Lastly, it engages in archaeological operations in and around archaeological sites. So these are all certain important points that you have to remember about ASI. Remember ASI is a premier institution for doing archaeological research in India. It is an attached agency of the Ministry of Culture, Government of India. The findings of ASI are released in their publications Ancient India, Epigraphia Indica and Indian Archaeology are review. It was first founded in the form of Asiatic Society in 1784 in Kolkata by Sir William Jones. Later, it was made into a government department with Alexander Kaningam as the first Director General in 1871. Later in 1904, Ancient Monuments Preservation Act of 1904 was constituted. This helped ASI to conduct functions like doing excavations, rediscovering the past and safeguarding important heritage structure. Only after independence that is in 1958 ASI became a statutory body and today ASI even conducts archaeological expeditions outside India. So these are all certain important facts that you have to remember about ASI from the problem's perspective. With these learnt points, now let us move on to the next news article discussion. Take a look at this news article. It talks about Telecom Act 2024. The article is conveying that this recent act has introduced significant structural reforms in the telecommunication sector. The intent of such reforms is to have a long lasting impact. It has provisions for sharing and surrendering unused spectrum and harmonising different spectrum bands. It also introduced a sandbox for academia to experiment with new technologies. Overall, the act aims to modernise and streamline the telecom sector promoting innovation, efficient spectrum management and clear regulations for infrastructure development. Even though the act has various advantages, the article raises many concerns regarding the Telecom Act. This is the corrects of the news article given here. In this context, let us understand the Telecom Act 2023 using our mains answer writing practice. Let me read out the question for you. Discuss how the Telecom Act 2023 attempts to bring several structural changes to current regulatory mechanism in the telecom sector. Also mention what are the associated concerns. This question can be asked in GS paper 2 under the syllabus, government policies and intervention for development in various sectors. See the question here demands two things. Firstly, we have to write about the changes brought by the bill. Secondly, we have to write about the concerns or challenges associated with the bill. In the conclusion, you have to mention the way forward or you can write a balanced answer. Moving on to the introduction part, here you can write about the bill itself. For example, you can write the Telecom Act 2023 seeks to amend and consolidate laws relating to development and operation of telegraph and telecommunication networks and the possession of radio equipments. The act repeals three existing acts. They were the Indian Telegraph Act of 1885, the Indian Wireless Telegraph Act of 1933 and the Telegraph Wireless Unlawful Position Act of 1950. These colonial era archaic laws were repealed to reform the telecom sector that has changed significantly in the last few years. So, you can write the introduction in this way. Moving on to the main body of the answer, here in the first part you have to write about the key provisions of the bill. Now, let us see them one by one. Firstly, about authorization for telecom related activities. According to the Act, obtaining prior approval from the central government is mandatory for providing telecom services, establishing operating or expanding telecom networks. Their permission should be obtained for possessing radio equipments as well and the bill allows the government to take back the spectrum that is unutilized. Secondly, with respect to the allocation of spectrum, the spectrum will be assigned by auction except for certain specific uses. In some specific use cases, spectrum will be allocated on an administrative basis. These include purposes like national security and defence, disaster management, wealth forecast, transport, satellite surveillance like DTH and satellite telephony and BSNL, MTNL and public broadcasting services. Thirdly, power of inception. See, the Act gives enormous power to the central government. The government can suspend, assume control of or oversee any telecom service in case of public emergency or national security concerns. The bill empowers the central and state governments or a government-authorized officer to seek interception, disclosure and suspension of powers in case of a public emergency or interest or safety. Fourthly, Digital Bharat Nidhi. There was an existing fund to provide telecom services in underserved areas. This fund has been renamed as Digital Bharat Nidhi under this bill. The fund will also be used for results and development purposes. Fifthly, biometric authentication of users will be created. So, from now on, telecom entities have to carry out biometric authentication of their users in order to curb fraud. So, these are all important provisions of the bill. Now, moving on to the concerns or the challenges with respect to the Act. See, the first one is regarding internet shadow. The Act has a specific provision enabling the government to order suspension of the internet. The Act basically says that the government has the ultimate authority when it comes to internet shadow with no judicial oversight. See, this provision goes against the recommendation of the Standing Committee on Information Technology. The second issue is with respect to privacy and surveillance. Another clause of Act lets the government notify standards and ensure compliance of encryption and data processing in the telecom. This raises the question of whether it empowers the center to possibly prevent popular chat apps from encrypting text messages. This goes against the user's right to privacy. Thirdly, legal challenges to administrative allocation. See, Supreme Court's 2G spectrum allotment, ruling of 2012 has recommended auction of scarce natural resources. The administrative allocation provision may go against this ruling. Fourthly, ambiguity in definitions. See, its definitions of telecom, telecom services and what constitute a message are so broad that it potentially leaves a door open for wide interception. This alleged that these definitions have been kept wide open to potentially regulate online platforms as well as apps like WhatsApp and OTT platforms. So you can write these concerns in the second part of your answer. Moving on to the conclusion part, here you can suggest some of the way forward. Firstly, you can write about the checks and balances to prevent misuse only a declared national emergency under Article 352 of the Constitution to trigger executive action. Any such action must require parliamentary approval. Secondly, respecting the right to privacy, the message interception and service suspension part must align with fundamental rights like the right to privacy. Thirdly, transparency. The government must address privacy concerns with an open mind by considering the vast power that the text of the bill grants it. The government must also conduct rulemaking with obsolete transparency and consultation. So certain amendments like these can be done to the Act so that the Act becomes more relevant to the telecommunication sector. So this way you can conclude the answer for this question. So these are the points and now let us move on to the next news article discussion. This news article talks about Meka Datu project. The deputy chief minister of Karnataka has said that the Karnataka government is committed to finish the project. He criticized the BJP members of the parliament from the state for not obtaining permission for the project from the central government. This is the crux of the news article given here. So in this context let us revise about the issue around Meka Datu project. See the Meka Datu project is situated in the Ramanahara district of Karnataka along the Kaveri river. This project aims to construct a balancing reservoir across the river Kaveri. It is actually a multi-purpose project with several objectives. Some of its objectives are to utilize additional 4.75 tmc that is 1000 million cubic feet of water from the proposed project to provide drinking water facility to Bangalore metropolitan region. But the Meka Datu issue is a continuation of the long existing Kaveri river water dispute between Karnataka and Tamil Nadu. As you all know Kaveri is an interstate river with its upper hilly catchment lying in the Karnataka and Kerala states on the lower part in the plains of Tamil Nadu. It rises in the Brahmagiri ranges of the western guards in the Kurg district of Karnataka, Harangi, Hemavathi, Shimsha, Arkavathi, Lakshmana Tirtha and Swarnavathi or the major tributaries joining the river Kaveri in the Karnataka territory. Kabini which drains the north Malabar of Kerala state flows through Karnataka and joins Kaveri. Bhamini, Amaravathi and Nuiyal or the tributaries to the river in the Tamil Nadu. Remember there are two interstate agreements signed in 1892 and 1924 on the Kaveri river. The 1892 agreement is a general agreement relating to a number of interstate rivers. The 1924 agreement relates to the irrigation development in the basin of Kaveri alone. Both the 1892 and 1924 agreements are permanent. But later the Karnataka government constructed four new dams across the tributaries of Kaveri like Harangi, Kabini, Hemavathi and Swarnavathi. For none of these they have obtained the prior consent of Tamil Nadu. So in 1969 Tamil Nadu appealed to the then prime minister of India to agiricate on this unilateral action. Later the center used its powers under the Interstate River Water Dispute Act 1956 to constitute the Kaveri Water Dispute Tribunal in 1990. The tribunal submitted the report in 2007 which was challenged in the Supreme Court. Based on the Supreme Court judgment in 2018, the center notified the Kaveri Water Management Scheme. It constituted the Kaveri Water Management Authority and the Kaveri Water Regulation Committee. The state of Tamil Nadu is strongly opposing the Mekadatu project because it thinks that the dam is constructed. Then there will be much regulation in the river flow that will lower the water release required for Tamil Nadu. So this is the issue surrounding the Mekadatu project. So in this news article discussion we saw about the Mekadatu project and then we saw about the Kaveri river. It is a river that flows from Karnataka to Kerala, Tamil Nadu and Putchheri. It has its origin in the Brahmagiri range of the Western guards in the Kurg district of Karnataka. Mekadatu project is planned across River Kaveri. It is actually a multi-purpose project with several objectives. So with this let us move on to the next part of the news article discussion which is the preliminary practice question discussion. Look at this first question about ASI. Three statements are given and you have to find which of the statements given above is or are correct. First statement says it is under the control of Ministry of Culture. This statement is correct. Second statement says Maharashtra has the highest number of protected monument in India. This statement is incorrect. See there are 3686 centrally protected monument or sites under the ASI in the country. The numbers have now increased to 3693. Uttar Pradesh has highest number 749 monument or sites followed by Karnataka, 506 and Tamil Nadu 413. So this statement is incorrect. Now the third statement says in India to be declared as ancient monument the site has to exist for at least 100 years. See according to monument and archaeological sites and remains act 1958 an ancient monument means any structure, erection or monument or any place which has been in existence for not less than 100 years. So this statement is correct. So the correct answer here is option A1 and 3 only. Now moving on this question has three statements and you have to find how many statements given here are correct. See here the correct answer for the question is option C all the three, all three statements given here is correct. Moving on this question is about NCLT. Here you have to find how many statements given here are correct. First statement is incorrect. The NCLT deals with corporate dispute that are only civil in nature. The second statement says the decision of NCLT can be appealed before the national company law appellate tribunal SCLAT. The decision of NCLT in turn only be appealed to the Supreme Court. The third statement here is correct. So the correct answer here is option A only one. Moving on this question is about Kudup Shahi dynasty. Three statements are given and you have to find how many statements given here are correct. Here all the three statements are correct. So the correct answer here is option D1213. So with this we came to the end of the news article discussion. If you like the video hit like, do comment and don't forget to subscribe to Shankar IAS Academy YouTube channel. Now thank you so much for listening.


signal gasoline signal the new gasoline you can prove is superior the signal oil company and your neighborhood signal dealer bring you another curious story by the whistler tonight phone call from death and the whistler and I know many things for I walked by night I know many strange tales hidden in the hearts of men and women who have stepped into the shadow yes I know the nameless terrors of which they dare not speak always a bridesmaid never a bride you know the old saying but have you ever thought how that thought must rankle in the minds of women to whom it is applied Ellen Livesey for instance Ellen always seemed to lose out with the men she set her cap for and who can say what emotion plagued her now that she could no longer be called a young woman she didn't show it of course even when men came to her about their troubles with other women like Glenn Reed it's maddening Ellen what am I gonna do about it there's nothing much anyone can do when a girl falls in love don't say that she's not in love with Paul Carol she can't be Glenn pull yourself together I'm sorry I know what Sheila means to you but you can't deny reality Glenn the fact is Sheila's met someone else and there isn't anything you can do about it two months ago she was going to marry me I didn't know that well not a definite promise but until Carol came along what is she told you about you and you can hardly expect me to tell you what you tell me I've got to know I don't think I have to violate a confidence for anyone but you said she's in love with him how do you know did she tell you yes she told me I don't believe it really Glenn if you're going to behave this way I know I'm a fool but Ellen if you knew what all this is doing to me I think I know ever since Sheila met Paul Carol she's been infatuated with him and I can understand why but why can't she see her moneys made ahead with him too oh Glenn lack of money doesn't mean anything to Sheila I've certainly never been wealthy why the jobs I've had dime store clerk telephone operator stenographer and now secretary that Sheila and I've always been close friends very close Ellen I I'd do anything humiliate myself anything if she'd only let me talk to you want me to call her for you don't know no I wouldn't want you to do that yes you would when you called me this afternoon I knew that's what you wanted me to do I'll call her right now well all right if it isn't too much trouble you know it isn't oh that's a silly thing to do I started to dial the wrong number well good heaven hello why Sheila what a coincidence I was just trying to get you Sheila what is it what's the matter Ella Sheila I can't understand you Sheila Sheila what's wrong what's happened I don't know exactly she seemed terrified something about someone trying to break into her apartment and then her voice seems mothered and we were good Lord we'd better get over there I'll call the police maybe they can get that quicker oh I hope I'm mistaken Glenn Sheila simply has to be all right we'll soon find out Glenn wait on the whole standing guard outside Sheila's door oh Glenn do you think come on well we'll let you up we're friends of Miss Blaine officer we're going inside all right well I don't know how you get by downstairs nobody tried to stop us off as if we simply came right up why can't we see Miss Blaine what's happened just a minute now just what's going on in there what's wrong I said hold your horses young fella Watson get downstairs into who are these people well sir that's what I was just my name's Ellen Liberty I call police headquarters about Miss Blaine oh yes Miss Liberty and Captain Hazlett of the homicide division homicide captain what's happened Sheila Blaine has two bullets in the back of her head she's dead wait a minute have you tried new signal gasoline that new super fuel that offers you premium performance at no extra cost if you have you know what an amazing new motor fuel it is not just pre-war quality not just an improvement on old style gasoline but an entirely new type of super fuel that embodies in one giant stride the amazing advances of wartime chemistry for signal is the new gasoline you can prove is superior with new signal in your tank you immediately notice one quicker starting the moment you touch the button to faster pickup you actually feel it three higher anti-knock just listen to that old motor per even on the steepest hills and four you'll find you go farther than ever on new signal because you'll be shifting less enjoying more economical high gear miles for you folks who like proof there's a scientific reason why new signal gives you all these advantages and I'll be back later to tell you about that but for the best proof of all let a tank full of new signal talk for itself in your own car that the quicker starting faster pickup higher anti-knock and longer mileage show you why new signal is the new post war gasoline you can prove is superior and now back to the whistler Ellen liver see this time it looks as if you won't have to even to be a bridesmaid your best friend Sheila Blaine is dead what kind of emotion does that call up in you are you properly heartbroken or is there a faint smile of triumph in your face the following morning when Captain Haslett called you Glen Reid and Paul Carroll to his office at police headquarters now tell you frankly we haven't developed a single lead on Miss Blaine's murder since last night you three seem to have been her closest friends though so if there's anything you can tell me what do you want to know Captain well you've already told me how Miss Blaine called you the way I'd like to thank you for calling headquarters apparently oh I thought it was a thing to do as I understand that you knew Miss Blaine intimately yes we've been friends since we were in school and her life ever been threatened before there was no reason for anybody to threaten a captain you were with Mr. Livesey when Miss Blaine called right at 7 30 and you Mr. Carroll you were at a movie at that time well from what I've heard I must have been inside the regal theater when she when it happened Miss Blaine made her phone call at 7 30 apparently she was killed immediately after that what time did you get on just after 11 one of your men was waiting for me what time did you went to the theater just after 7 wasn't that a little early for you to attend a movie I don't see why I hadn't anything to do last evening decided to drop in as I was passing by can you prove you were there look here if you're implying I had anything to do with this someone's been murdered Mr. Carroll it's my job to try to find out who did it I have to start with those who might have done it and you mean to say I'm one of them why not what motive would I have motives are usually and can easily be found does that mean Miss Livesey and Reed are under suspicion too everyone's under suspicion Mr. Carroll we suspect everyone at this stage of the game I went to the regal theater last night haslet I was there from 7 until 10 30 we can check it anyway how long had you known Miss Blaine six weeks you were quite friendly we were going to be married you're a liar just a minute Mr. Reed he's lying they weren't going to get married please please control yourself we just have his word for it she'll never told anyone holy yourself read I take it you were on friendly terms with Miss Blaine too I was in love with her and Carol says he was gonna marry I told you he was lying you're talking pretty carelessly read I'd watch myself if I were you what are you doing warning me I'm telling you to use a little common sense because if you don't I'll get what Sheila got how you dirty little down take it easy you're both under a strain but so as Miss Livesey I'm ready to tell you whatever I can captain no thanks I suggest you all go home now but I thought you had questions to ask us I'll do that later one at a time then we're free to go now what about Sheila's murder is this all you intend to do about it we'll go on checking into it Mr. Reed she's dead don't you understand that somebody's killed her somebody's got to pay for that we'll go on checking Mr. Reed haven't you any ideas or theories at all right now I'd say the coroner's jury will have to hand in a verdict of homicide by person or persons unknown we get those cases ever so often sneak thieves intruders surprised by their victims killed get away Sheila wasn't killed by any sneak thief how do you know I don't know for sure but it couldn't have been that the moment get some sleep Mr. Reed I'll call you if I want you thanks for your cooperation everyone thank you captain oh yes Helen will you be good enough to take me home now it's all quite a mystery isn't it Ellen the police get nowhere and soon it's almost forgotten yes even you almost forget it because of a new anxiety a new emotion your anger because you haven't seen Paul Carroll since that day he drove you home from the police station with Sheila out of the way you thought he'd be around much sooner didn't you thought you could wait but every day you're away from him well he's very much in your mind the afternoon you face Wilson Andrews in his office Wilson Andrews Sheila's attorney before Miss Blaine's will is admitted to probate Miss Leversey I'd like you to read it or if you prefer I'll read it to you to give you the gist of its contents Mr. Andrews are you telling me I'm one of Sheila's ears her only air my dear oh no that isn't possible surely you don't object but I couldn't I couldn't take her money my dear Miss Leversey she wanted you to inherit her estate surely you can use thirty thousand dollars I don't know what to say and she was quite fond of you miss Leversey I'll always remember her great glee in describing how surprised you'd be yes yes I can imagine if there are any questions you wish to ask why I think not Mr. Andrews oh yes yes there's one question when will I come into the estate almost immediately I'd say I hope this bequest will bring you much happiness Miss Leversey happiness well yes perhaps it will perhaps it will well this is a surprise isn't it Ellen Sheila's death has brought you a double benefit now you're thinking more than ever of Paul and now that you've become moderately wealthy why shouldn't you put your money to good use the clothes you've never had a new bigger apartment a chance to make Paul Carroll notice you but instead of Paul across the luncheon table from you you find Glenn Reed you're looking awfully attractive I'm on new hat knew everything I felt guilty about it all until all the time I was splurging yet I knew it was exactly what Sheila would have wanted me to do why did you invite me to lunch I had to talk to someone the police still haven't made any arrests they won't arrest anyone the way they're going about it it wasn't any sneak thief who killed Sheila makes usual sure that it couldn't have been it had to be somebody else that isn't enough to go on Glenn you need evidence of some kind to make the police change their mind I don't have any evidence but I have a pretty good hunch you mean you suspect somebody Paul Carol oh now Glenn that's ridiculous you know Paul can't be guilty he was at a movie when it happened the police even found an usher who remembered but that doesn't mean anything he could have sneaked out of side exit soon after he went inside nobody remembered seeing him come out what motive could he have why would he want to do it because he found out he wasn't named and Sheila's will he was counting on her money then he found out how she really felt so he killed her by the same token I'd have a motive for killing her because I knew I didn't hear us her money but you didn't know you were named as her heir oh yes that's true besides we know neither of us killed her Carol's the only one who had both the motive and the opportunity then he was at that failure he said well what are you going to do about it you're going to go to the police I don't know yet all I know is I won't let Sheila go on avenged I'm going to find out who killed her and when I do please don't do anything rash now promise me you won't do anything you might regret later promise me Glenn I'm not promising anything oh don't tell anybody what I've just said I'll take care of this in my own way and this might be dangerous to your plans suppose Glenn does do something to Paul Carol the man you love but wait Helen suppose Paul did kill Sheila you wouldn't want the murder of your best friend to go on avenged would you or would you love is a very strong emotion even when it's one sided you haven't seen Paul for weeks he hasn't called you up at all nevermind now you have an excuse Ellen an excellent excuse for seeing you like my hat Paul hmm oh yes very nice the very first time I wanted no isn't you've never noticed anything I've worn has your Paul what what makes you say that oh no reason why did you want to see me Ellen because we we both loved Sheila and because I haven't well I meant to call you and congratulate you on inheriting her estate but somehow I didn't get around to it shall I consider myself congratulated now if you like you've changed Paul you're not the same at all maybe I've good reason for it were you so much in love with her I don't know what does that mean well you knew Sheila as well as anyone you know what she was like she was beautiful and capricious unpredictable provoking you found that out in 15 years I knew her for six weeks during that time there were hours when I had daughter and moments when I could have killed her not a very good choice of words is it I know what you mean Paul now she's gone my world's pretty much upside down and yet if she'd lived I don't know how long we'd have lasted together were you really going to get married I'd have persuaded her to then we'd probably have split up in no time and I'd have been just as broke as I am you don't sound as if you were really in love I'm not trying to kid anybody Ellen just telling you how I felt then read doesn't think you were in love with Sheila yes I gathered as much that day at police headquarters he thinks you killed her Paul that's insane what's the matter with that idiot is he going around spreading that kind of gossip oh no I don't think so he told me about it yesterday though that's the real reason I want to see you I thought I had to warn you as he gone to the police he said the police wouldn't believe you bet they wouldn't please be careful please don't take any chances don't worry I'll talk to him get him straightened out oh no please don't go near him no that might only stir up trouble and if anything happened to you I didn't mean to betray myself I mean would shame doesn't mean to talk like this but I'm free to tell you now I'm in love with you and if anything if anything at all happened to you I could never tell you before Sheila was my dearest friend but just like Sheila the first time I saw you I fell in love with you too now you know I'm a fool for telling you this way but I don't care I have money now Paul we can share it together I'm not ashamed of myself I'm proud I just I want to stand up here and tell everyone I think we'd better go Paul please please let me finish it wouldn't do any good Ellen I'm sorry I don't know what else to say nothing else to say Paul shall we go unrequited love Ellen yes you can go on hoping but deep down inside you know he met it he'll never love you the anguish and torment of that thought gives you many a sleepless night you go on hoping but as the days go by you need more than hope you must see him hear his voice well then forget your pride Ellen you did once before hello oh hello Paul I want to apologize for my stupid behavior last Wednesday I wanted to call you before but I couldn't muster enough courage until now oh no no there wasn't anything else you could say well that's awfully sweet of you can't we make amends well perhaps if we had dinner together some evening oh I see yes yes yes of course well if you'll call me when you get back yes Paul yes goodbye when you get back when you get operator operator we will cut off no no no it's all right now oh hello Paul someone must have cut in I just thought I'd call and see I oh oh I see well I thought now that you're back you Paul Carol never thought you'd say those words did you Ellen he didn't remember that love is an emotion very close to hate but now you know Paul Carol doesn't love you never will love you he's avoiding you he's too busy you hate him now don't you Ellen you're going to take that hate out in action something drastic aren't you hello Glenn Reed oh hello Glenn this is Ellen yes yes I know I haven't seen you for ages but I see tonight Glenn really important about Paul Carol no no I can't tell you now can you come to my apartment tonight oh say eight o'clock all right I'll be expecting you yes you're going to do something drastic aren't you Ellen so you work fast and you're ready when Glenn arrives at eight my hello Glenn you come in thanks you haven't seen my new apartment before have you know I haven't pretty swank said you had something to tell me about Paul Carol Ellen what is it well please sit down first make me uncomfortable standing in that way what's happened well it's a little hard to tell especially after I wouldn't believe you my suspicions about Carol you mean yes I I saw Paul several weeks ago before he went out of town yeah I could rather strangely at that time then I talked to him on the phone today and well now I'm glad to think you're right something he said aroused my suspicions was that well we were chatting casually something about radio shows when Paul mentioned a certain program he suddenly changed the subject later I realized why he talked about a program that was on the air while he was supposed to be at the theater the night Sheila was murdered are you sure that I wouldn't have called you if I weren't first I thought of calling the police but then I could see the evidence would seem so flimsy to Captain Hazlett yes you're right if we could see Paul alone the two others with him and trick him into confessing oh well I could invite him to the apartment tonight I tell him you're here and then when he I wouldn't do any good Ellen I think it would I'll give him a ring I wouldn't do that nonsense we both wonder what then Sheila's death don't we but if you'll listen to me oh always making that mistake I keep dialing Sheila's old number oh well hello Paul I was just about to call you yes I wanted to invite you out oh don't say you can't come well I suppose I could mm-hmm all right Paul yes I'll be there goodbye well that wasn't hard he won't come here but you'll be glad to see me at his place won't expect to see you with me so we may be able to I don't think so I'm not we're not going to visit Carol I thought we agreed on the phone and what we have it really Glenn very well what in the world are you then I demand an explanation why don't you know you're stalling Ellen I watched your diet you see you didn't dial Sheila's old number you fake that call to Carol that's absurd I don't know what you're talking about you will listen there's nobody on the line you see because the four numbers I just dialed make your own phone ring you didn't talk to Paul Carol just now really Glenn I'm not going to sit here and let you know I know that Ellen you see I've already killed him the whistler will return in just a moment with a strange ending of tonight's story meantime I promise to give you the scientific reason why a new post war signal is the gasoline you can prove is superior why it actually has quicker starting faster pick up higher anti-knock plus the economy of more high-gear miles well you see gasoline is composed of countless different hydrocarbon molecules in pre-war gasoline's the molecules were left just as nature made them but under the impetus of war chemists found how to take the molecules themselves apart actually how to rearrange the atoms within the molecules the result is the thrilling amazing power of signals new gasoline bringing you performance so immediately apparent you can feel it see it hear it make it a point this week to drive into one of the friendly stations displaying signals familiar yellow and black circle sign and say fill her up with new signal when you touch your foot to the accelerator feel that old motor get young again you'll know why new signal is the gasoline you can prove is superior and now back to the whistler the unexpected can be a physical blow candid Allen almost like the promise of death itself Glenn's words completely upset your elaborate little scheme you stand in horror as it crumbles about you can be serious I can believe oh yes I've been following him for weeks because I thought he'd killed Sheila I saw the two of you in that restaurant several weeks ago and I saw you go into his apartment earlier this evening oh no no you couldn't went in after your left was sitting in his chair is back to me crept up behind him a heavy metal lamp from an end table in my hand and then no one saw me go in or out of his flight oh Glenn you fool I can't tell you about it before giving myself up but then you faked that call from him puzzled me at first but not now Allen Allen you faked that call from Sheila to you killed Sheila listen listen to me let me explain to me I know you killed her but why how could you do it because he'd always had everything I didn't have money beauty popularity and then Paul came along and she got him to I couldn't let her take him so I yes I killed her I killed her and then I made my own phone ring while you were with me I learned how when I was an operator you killed Sheila your friend knowing all the time I talked to you about her that night that she was already dead there hadn't been for you I wouldn't have killed Tara let me tell you you didn't kill him he was already dead you killed him too don't come near me I shot him I made it look like suicide they'd be killed Sheila we both have been avenged if you hadn't meddled you meddled we'd have gotten away with it you won't get away with anything again Ellen what do you mean what do you mean what are you what are you doing I told you if I ever found Sheila's murder I'd avenge her no no Monday at 9 o'clock the whistler will bring you another strange tale the whistler is broadcast for your entertainment by the marketers of signal gasoline and motor oil and fine quality automotive accessories and by your neighborhood signal dealer this program directed by George W. Allen with tonight's story by Leslie Edgeley music by Wilbur hatch is transmitted to our troops overseas by the armed forces radio service this is Marvin Miller speaking and suggesting that you try new signal the new gasoline you can prove is superior this is CBS the Columbia broadcasting system


Well hello everybody and welcome to another OpenShift Commons briefing. This time it is my great pleasure to welcome back Trevor Williams who's now with Replicated and Josh Dwin who's also with Replicated and we're going to talk about some interesting stuff that's going on over at Replicated that they're doing for apps on OpenShift and it's a long title there, Simplifying Deployment Management, trouble shooting of third-party enterprise apps on OpenShift with Replicated Cots. I'm going to let Trevor and Josh introduce themselves and take it away and give the presentation. There's a really neat demo coming too and then we'll have live Q&A at the end. If you have questions throw them in the chat wherever you are, Twitch, YouTube, or in BlueJeans and we will relay them back to the speakers and try and get them answered. So without any further ado, Trevor, welcome back and take it away. Thank you so much Diane for the amazing introduction. I'm so happy to be here. I'm super excited. Time-appropriate greetings, OpenShift community. I am thrilled to be here and as Diane said, I am presenting about super long title. So let's go ahead and get jump into it. So let's introduce Replicated as a company first. So Replicated was founded in 2015 by Mark Campbell, who is our CTO and Grant Miller, who is our CEO and what they do specifically Mark, what they do is they have created a complimentary series of both enterprise and open source tools for multi-prem environments, including the ones that we're going to be talking about today. As for the voices behind the screen, there is my colleague Josh DeWin. You can find him on Twitter at George DeWin. He's waving with that beautiful tropical background. Josh is a Linux docker and Kubernetes superfan and he is also a solution engineer for Replicated and he also sporadically contributes to some open source projects like troubleshoot.sh, nudge nudge wink wink, and also some open source frameworks like OpenFast and is also apparently a pretty big fan of coffee and cats.  As for me, I am the community manager slash dev avocado for Replicated. I am also a recent inductee into the Red Hat Accelerated program. So gave me and I also still use pack stack right from my cold dead fingers. I've been involved in several open source communities for a while, open stack, open shift, Kubernetes, and a few other projects. And in the before times, I traveled a lot with that little guy in photo who's actually sitting on my desk right now and provided that KubeCon LA actually happens this year, you can catch us there along with a huge Replicated booth. And if you do, huge managed to make it to KubeCon, drop by a booth because we've got some really cool swag. So all right, now that we're done with all of that, let's talk about Replicated projects. Or as I like to call them, the Replicated universe.  He finds super quick ways to fix them, and then he open sources it. So the first project and the project that we're talking about today is Cots. And Cots is an abbreviation of Kubernetes off the shelf software. And what Cots is, is it's a sophisticated and highly adaptable containerized application delivery and management platform. And it supports and also can build air gap and embedded clusters. We'll talk more about what embedded clusters are in just a second, such as whole type. And then up next is Troubleshoot. That's one of my personal favorites. Troubleshoot is a two-part admin tool set that validates environments, collects, sanitizes and analyzes data and a ton more. I could spend all day just talking about Troubleshoot preflight. That's only one component. Let's not even jump into the other components. It does so much. If you have time, I highly encourage you to jump over to Troubleshoot.sh and check out the website. And speaking of websites, outdated has the most amazing layout ever. But what it actually does is it analyzes outdated cluster images. And how it does that is by comparing the content shell of the original image repo to the image that is running in your cluster. And then it'll tell you how outdated that image is or if it's outdated at all. Super cool. It's a kubectl plugin, takes like 30 seconds to install. You should definitely check that one out. But before you do that, go to the website, outdated.sh. It's amazing. And it'll make you want to buy some roller skates. Up next is Unfork. That's another kubectl plugin. And what that does is it reconnects forked home charts to the original upstream, which is super useful. Because I mean, it's a nightmare dealing with a home chart or anything that you forked from an original repo and trying to reconnect it. I hate that. Next up is Schema Hero. What Schema Hero is, is a database schema migration tools. And what it does is it converts schema definitions into migration scripts that can be run anywhere. So highly adaptable, highly compatible, a lot of fun. And by the way, Schema Hero is actually in the CNCF sandbox. So if you are involved with Linux Foundation or CNCF, you may or may not have seen mention of it. And you're certainly going to see a whole lot of mention of it at KubeCon this year, which I certainly hope you are going to be attending. And then last but not least is Curl, which is a play on Curl with a C, because it uses Curl with a C. I digress. And this is where the embedded part in the embedded cluster that I was referring to in Cox comes from. Curl is a tool for building customized Kubernetes installers and distributors. And I'm super excited to announce this. It officially became a CNCF certified Kubernetes installer as of this past Friday, August 27. So round of applause for our engineering team for getting that done. That's amazing. Now, all of these projects that I just listed are open source. They play extremely well with Red Hat and OpenShift. And they're available for starring, forking, contributing, and just otherwise general interaction on the replicated HQ GitHub, except for Schema Hero. That has its own GitHub, which is Schema Hero. I would be thrilled if you stopped by and checked them out, because I would love to see feedback and interaction from Red Hat people, because I am still a Red Hat fan girl after all these years. So I want to see Red Hat involved with my new job, which I absolutely love, and with all of these projects that I manage. There are also a number of other open source projects that Replicate has available that I honestly just couldn't fit on this page. And honestly, I could talk about these all day, but we don't have time. But if you're curious about what those are, you can follow Replicated on Twitter at ReplicatedHQ or send me email. Like none of this is a secret. I'll tell you what they are. All right. So I guess that's enough about that. Let's go ahead and move on. And let's talk Cots. And we're going to talk Curl and Troubleshoot too. So one of the many features that makes Replicated Cots such an innovative and useful platform are the vendor and admin tools. So the vendor tools enable software vendors to create, monitor, control, application release channels, licensing, and entitlements across multiple environments. That's a mouthful. It will click and it will make more sense once you see the demo. While admin tools, they handle installation and configuration of the customer environment to best support your apps, push updates, and also give access to preflight and support tools via Troubleshoot.sh, which I was just evangelizing one page ago. When we get into the demo, you'll see how all of these tools interact with one another and how they're so complementary. In addition to compatibility with a wide array of Kubernetes distros, including GKE, the Google platform, AKS, Amazon platform, VMware, Tanzu, and of course OpenShift, Cots also enables independent software vendors to deliver apps to uncouberdated customers with embedded clusters. And this is where Curl enters the chat. Basically, whether this is an air gap customer that doesn't have access to the public Internet or if it's a customer that has public access, you can bundle in a custom Kubernetes installer along with your application to set up the customer environment exactly how you need it for your application to run. Send it over to the customer either in a tar bundle or with a Curl URL with a C. They run that by the bing by the boom, environment is set up, applications installed, that's it. So that's what makes or that's one of many things that makes Cots and Curl so cool. But I'm kind of going off on the tangent again. Let's go ahead and move on. As I mentioned, Cots is pretty popular with ISVs or yeah, independent software vendors. Some of our customers include but are not limited to by a long shot. SmartBear, HashiCorp, Jomik Software, Broadcom, and as a matter of fact, 60 of the top Fortune 100 companies use Replicate to manage their applications. So we don't even go over here I would say. All right. So that is enough of me rambling on. I'm sure you're tired of me stuttering. So I'm going to hand it over to Josh. Take it away, man. Thanks. We recorded the demo up front. So Chris, if you can play it, if it doesn't work, then we're going to fall back to an actual live demo and let Murphy kick in. So we'll see how this goes. Thanks, Riva, for this introduction. So let's get started. I'll start sharing my screen here. I'm going to share a couple of applications at the same time. And this is where I would like to get started. So what we do with Replicate is we try to enable vendors, ISVs, to deliver their applications in an on-prem or a multi-prem environment. And obviously OpenShift can be one of those on-prem environments wherever they are running OpenShift in there. So if you look at Replicate, there are really two sides of the spectrum. One is what vendors like a HashiCorp, a Harness, but also many others like UiPad, what they have access to, which is what I'm currently sharing here. And the other side of the spectrum is what customers of those vendors have access to. So how do they experience the installation of the vendor's application, but also how do they experience troubleshooting the application if something goes wrong during that installation? So I would like to start with what we call the vendor portal, which is what I'm currently showing here. In this case, I have a single demo application called the OpenShift Sentry application. And in the vendor portal, one of the main concepts is what we call Channels. So Channels are, we can compare it a little bit like your CI CD pipelines. So you have like this case, as an example, you have a stable channel, a beta channel, an unstable channel. You can, of course, have any channels you want. A very common example is in your application, each time you have a feature branch that will correspond with a corresponding channel inside the vendor portal. And in most cases, those channels are even auto-generated because everything is typically hooked up with CI CD solutions. So each time there's a new get branch created, the whole CI CD kicks in and creates the whole channel in an automated way. It's very common. Once the feature branch is, let's say, merged into the main branch, the main branch goes to the unstable channel. Once there's some final QA testing that has been done, it might go to the beta channel. And once there is a full approval, it is going to go to the stable channel in there. So you have a deeper look at one of these channels. Let's say, for example, the stable channel, you see a couple of concepts in there. I'm just going to silence my phone here for a second. There we go. One concept that you have in there is what we call releases. And you can see here, this one has a latest release in there. Another concept that you have in each channel are what we call customers. The customers are going to correspond one-on-one licenses. First look at releases. Then let's open this up here. See, I have a couple of releases in there that I want to show you what the release looks like. On the left, what you see here are a whole set of YAML files. And what you have below the horizontal line, those are YAML files that are what we call application specific. So as an example, I took the Sentry Enterprise application. So all the YAML files that you see here below are really specific to the Sentry demo application. The YAML files that you see above the horizontal line, those are what we call replicated specific YAML files. Those are making the application a replicated application. Just a side note, the application doesn't need to use raw YAML files. There might also be help charts in there. Or there might even be a combination of multiple help charts and raw YAML files all together put in here that make up the application to do the installation process. Now, why are there several YAML files that are replicated specific? Well, let's highlight a couple of them and then maybe to start with, there is what we call here a preflight YAML file. And the preflight YAML file is defining what you could call the minimum requirements that are needed in order to install the application. And I'm going to come back a lot more on to this later on, because this is based on a framework called troubleshoot.sh, which is fully open sourced and can even be used outside the scope of replicated. There are multiple vendors who are using troubleshoot without relying on the replicated enterprise version in there. So a good example to start with is we have an analyzer here that does a check on the cluster node count. If in my open shift cluster, I have less than three nodes, then the preflight check is going to fail. If I had less than five, then we're going to send a warn message that's obviously five or more than we're going to define the cluster has enough nodes. So this is a very simple check, which is very common, where you see, oh, I have an enterprise application that needs to be installed on an open shift or a Kubernetes cluster. In order to install my application, you need at least X number of nodes. In order to validate that before doing the actual install, you just add an analyzer that checks the number of nodes. Similarly, you can do that with memory, CPU, and basically anything that you can run in a pod, you can collect information from and then start running analyzers on that. You can see there are many more YAML files in here. We're not only talking about validating the minimum requirements, we're also talking about generating support bundles, or for example, doing automated backups of the application. So there's quite a lot of different YAML files that make up the application itself. Going back to my channels, so each channel is having a release assigned to it potentially, but a channel can also have what we call multiple customers. So very typically, if you're delivering enterprise software into, let's say, a financial institution, then you will also have to provide what we call a license to that financial institution. So if I go here to customers, then you can see I have in this demo environment that I have a single customer, which is some bank in there. And if I open up the customer, then you're going to see there's several details in there to have my customer name. The customer is assigned to a certain channel, so that's going to be the release that they will be able to install. But the customer can also have what we call an expiration policy, which is very commonly used, for example, when a customer is doing a trial. Yeah, if it's a paid customer, they might not have an expiration date, but there might also be customers who are vendors, sorry, who are doing installations that maybe they have a community version of the application. And then the installation is going to show community if their customer is upgrading to the enterprise version, then they switch the license to a page first. And there's, of course, many more things in there. One thing that I want to highlight here is maybe two things. One is aircaps. As we're delivering enterprise applications, like, for example, a Terraform enterprise into on-prem environments, those on-prem environments sometimes have what we would call the aircaps requirement, meaning they're not able to access the public internet or public container registries in order to download all the images. They're fully isolated aircaps environments. And sometimes even as far as the only way to bring in the application or an updated version of the application is to physically walk in even with a disk containing all the tar balls. What we do with Replicated is the creation of all these what we call air gap bundles. They're multiple. We do that fully behind the scenes in a fully automated fashion. So we download all the images, all the Apple files or the Helm charts and everything that is needed in order to properly do the installation. For our enterprise customers, we even provide what we would call a download portal. I'm just going to generate a password here because it's password protected. Let's copy this. And then I'll show you what the download portal looks like. So this can be shared with a vendor's customer. You can see here I have a demo application already used the OpenShift logo. I'm now into the download portal of my customer called SunBank. And my customer can go here, download their license. They can download the Cots admin console Cots air gap bundle. This is the Cots QTL plugin to install, but also the different images to install into the cluster, but also the OpenShift application. It's sorry, the Sentry application air gap bundle itself. And on top of that, what we do with customers is what we call custom fields or custom entitlements. So we have many vendors who might already have an existing licensing system in place, or they might have certain custom requirements on licensing. And a very common requirement there is let's say number of users. So when the application is installed even in an on-prem environment, then the license for that specific customer might be limited to let's say a certain number of users, or it could be a number of nodes, or it could be a number of messages, number of API requests. So all these can be customly configured in here. And then all of these custom fields are available during installation of the application, but also at runtime. So on the customer environment, the Cots admin API exposes an end point that allows your application to check if, let's say for example, the license was expired, what the customer type is, but also all the values of the custom fields so that you can start acting on that. And maybe if the number of users goes above, then that you will automatically start sending a message or showing a message that your customer must contact the sales department or you start automatically upgrading the customer. So that is a little bit what it looks like from vendor portal UI perspective. The next thing I want to show you is what it would look like from a customer and user perspective. So also on the channels for each of these channels, what we're exposing is the installation commands to install the application inside the Kubernetes cluster or the OpenShift cluster. If the customer doesn't come with, let's say an OpenShift cluster installed or they just come with a virtual machine, an EC2 instance, one thing that we do from a replicated side is we allow the support for vendors to install in what we would call an embedded cluster. What that will do is it is going to basically run this on a VM or bare metal machine and it's going to spin up, in this case, the curl cluster. Curl is our upstream version of Kubernetes that is going to be installed in there. On top, it's going to install calls on top. It's going to install the application itself. In the case that someone is already having a Kubernetes cluster up and running and that's where OpenShift comes into play, so they already have OpenShift up and running, OpenShift installed, then it basically comes to installing the application with the following two commands. First one is installing the God's tube CTL or OC plugin in there, which is the first one. The next one is using the God's tube CTL plugin. What you will do is it's going to install the OpenShift sign tree application in there. That is also what I've already done up front because it takes a couple of minutes to do this. I spin up an OpenShift cluster and then using the OC command, I actually installed my sentry application. The first thing it does is it asks for the namespace. It's going to create the namespace. It's asking me for providing an admin password and then it's set up automatically a port forward for me. I canceled this one because I'm running this on a Google Cloud VM. I want to expose that same God's ADM port using port forwarding of all the addresses. Once that is established, me as an end user, I can go into my application and I can browse to that port and I can start logging in with that corresponding password. Let me grab that password again. There we go. Logging in in there. In order to install sentry as a demo app, the next thing I have to do is upload that license file. If I go back to the vendor portal because I talked about customers, I talked about licenses, each of these customers also have a license file in there. It's just a YAML file that can be shared with customers and provided to them. Let's save this file. I go back here to my customer experience and then I can, in this case, I can drag and drop this YAML file in there and upload my license. Uploading this license means also that God's ADM will understand which application is installed, but it will also know that, oh, for this particular customer, air gap was enabled. I'm going to present that customer with the option to install in an air gap environment. In that case, we have to provide the location of the registry. It's an existing cluster. We don't know where the container registry is going to be, so then the customer will have to provide what that container registry will be in order to upload all the images. In this case, I'm not going to start uploading to our balls. I'm just going to download sentry enterprise from the internet, so it's going to start downloading that, installing my license. The first thing that then pops up is it's going to ask me for configuring my application. Once the license is installed, it's going to allow me to configure my application, which is what you see here, which is happening here. What is this all about? Well, if you're developing any application in there, and it doesn't even matter if you use YAML files or Helm charts, most applications require a certain amount of configuration in order to be installed. A very good example is, well, you write an application. You might need certain storage. As an example, that could be, let's say Postgres that you might use as a database.  But you might also want to give your customers the option to say, well, maybe you're running this on AWS, and you would allow your customers to use a Postgres RDS instance, and then the customer will have to provide the configuration of Postgres in there. What's the host, the board, username, password, in order to be able to connect with that external databases? Very similar, you can have things like SMTP configurations or LAP, or the directory configurations, or for example, on top here, what you see is the admin username or the admin password. So vendors can configure this with, I'm going to switch here to VS Code to show you what it looks like. So here on the left, you see all these manifest files. In this case, they're all grouped together. I previously showed already like the preflight manifest file, but there is another replicated specific manifest file, which is the configuration. You can see this is really a one-on-one mapping with what you saw in the UI a couple seconds ago. So you see like we're asking here for the admin username, the password, number of worker replicas, database configuration, whether it's embedded or external. And you see also some notations in here, for example, like this one. This is auto-generating a secret key behind the scenes so that the customer doesn't have to do that. You see also other notations in here. And this is what we call GoTemplating, which is available throughout all these YAML files or throughout your help charts in order to start allowing to make your application configurable in there. In this case, I can accept the defaults in here. So I can just press continue. Once I press continue, this gives dot ADM basically all the information that is needed in order to, you could say, install the application. So we have the license information. We have the custom entitlements, like say, for example, number of users, but we also have the custom configuration, which storage options to use, what should be the ingress, what should be the host, all that information should be available at this moment. So based on that information, what we can do is we can validate the environment if it meets the minimal requirements. So that corresponds with running all these preflight checks. That is what's currently happening in there. And obviously common preflight checks are, let's say, for example, customer note count, the number of CPU, but also let's say the customer provided an external postgres to the endpoints. Does that postgres meet the minimal requirements? Does it meet the minimum version of postgres? Can we even connect with it? Does it have the right credentials in there? This takes a while. So I actually ran this a little bit before already. Once that is finished, the output of that will look very similar to like this. So we're checking cluster note counts. In this case, it's giving me a warning. Things like criminal storage. Is there a default storage plus? So all of this is configurable within that single yellow file, which you as an application creator can provide in there. And all of this is also based on a framework, which is called troubleshoot.sh. Now you can see it here, right? You can run the preflight. It's running as a Qtl plugin. So it's kind of the difference. You can even run it to command line. You can run it through the UI. The options are available in there. And what I wanted to show is I talked a little bit about postgres. There is, for example, on the analyzer, there's many analyzers available out of the box. There is also a postgres analyzer available that you can use as is. So what this one does here is in a preflight checks, it checks with a collector. If it can connect with the postgres instance itself, then using an analyzer as an example here, it checks the version of postgres must be 10.x or later. And then based on that, it's actually going to fail or pass the preflight check in an automated fashion, which is very beneficial because you as an application developer, you might not even be there when your application is being installed. Your customer might be doing that totally offline without you being involved. So this will also help your customer in order to do that installation. By the way, you see some of these checks failing here. I just want to make a side note. These are failing on purpose just to give you an idea of what it would look like if one of these checks fail. You can actually link them. You can, in each preflight check, you can put a link that points back to your knowledge base that gives more information of how to configure this or what needs to be changed or what would fail if you overruled it. Because customers can't overrule. I can just continue here and I can start deploying the application in there. So what it's doing now, it is actually deploying my application. So it is actually deploying all those YAML files, all those Kubernetes resources onto my cluster. And one thing that you see here is from a UI experience, we are checking here the status. You can see it's still showing unavailable. Also, that comes from some of those replicated specific YAML files. For example, this one just defines my replicated application. And what you have in here are what we call status informers. Status informers are the Kubernetes resources that we are checking using Cots ADM to see if the application is up and running. So, so far what I've shown is like what we tend to call like a day one of operations. This is the initial install, the first install of the application. We're not changing anything. Day two of operations is when things might start going wrong in the application. And that is where what we call support bundles and troubleshoot comes into play. So end users of Cots, Kubernetes off the shelf, they also have access to troubleshoot and they can also start analyzing their application. With a single click on the button, I can start analyzing my OpenShift Sentry application. I'm very similar to what preflights are doing. And preflights also rely on the troubleshoot.sh framework. Support bundles also rely on troubleshoot.sh. So in my application, I also have a support bundle resource that defines which information I am collecting. I'm collecting certain information while I'm generating my support bundle. And then on top, I'm putting analyzers on top of that that are checking the information that has been collected. So very common thing there is you might have multiple resources that are being deployed. You have multiple pods that are running each producing log output. Well, you can actually start collecting all these logs in there and then start defining analyzers on top of that. And a very common analyzer there is you can see it's already finished here, but I want to first go to troubleshoot itself is there is, for example, also an analyzer that allows you to use regular expressions. And as an example, what you have here is collecting the log files of all our pods of our application. And then as an analyzer, I'm defining a regx to see, oh, if there is this kind of a message that the password authentication failed for a user, then me as an application developer, I know as an outcome, this is kind of like a little bit of reverted logic here that if that regx is not present, then we know that the database credentials will work. If that message is present, then we know that there is a problem with the database credentials. Yeah. So if you run this from back here a couple bit, you can run this from the command line with the Qubectl plugin. There's a preflight and a support bundle Qubectl plugin. So we're switching here to the support bundle side of things. But you can also run this as part of COTS. COTS gives you then the whole UI experience in there. If I go back here and COTS, this is what the UI experience would look like for an end customer who is installing this application. So they get this tile output that shows what is going wrong with that particular installation. And currently only showing the errors in the warnings. You can also show everything in there. You can see there's a whole bunch of analyzers running in there. Obviously, people using troubleshoot, they have access to the corresponding files. And besides collectors and analyzers, there's also a third component to troubleshoot, which is what we call detectors. We go back to troubleshoot, then go ahead to the docs. So on one side in troubleshoot, you can define collectors. You can see there are a whole bunch of collectors available out of the box. And if it's not there, you can just create your own pod in there and create your own collector of information. Second part, within troubleshoot, there are analyzers similar to collectors. There are a whole set of analyzers available out of the box. But the third component is what we call redactors. And redactors are typically defined by an end customer. They define which information needs to be taken out of the collectors in order to be able to share the troubleshoot support bundle. So what happened here when I was running is, behind the scenes, there's also a redactor report. So we've taken out things like usernames, passwords, IP addresses. And this is just to make it more secure. End users can also define their own redaction. So they can actually confine which additional redactors need to be part of it. And of course, the last thing is this can also be run command line. So this is based again, a Kube CTL plugin. In this case, the support bundle Kube CTL plugin. And then if I would run this command line, I would actually run this single Kube CTL command in order to get this up and running in there. And of course, if it's running in an OpenShift environment, we simply replace Kube CTL with OC, and that's going to do the corresponding thing in there. So one last thing that I would like to do is give you an example of what would happen if I start changing something, when I change something in preflights or in support bundles. So one thing I'm going to do is in my preflights, I'm going to do one additional check in there. And first of all, I'm going to take a collector here. I'm going to add a collector in here. And what the collector is going to do is it's going to check if I can connect with OpenShift commands. I'm going to make sure that I'm doing the indent right here. This is collecting the information. So it's using an HTTP get request, and it's going to check if it can reach commands.OpenShift.org. So I just wrote this up front, so they don't make any typos in there. Next to that, I'm going to add an analyzer. In this case, I'm going to use a regular expression. I'm going to use text analyze. And as part of my output of my collector, I would like to have 200 back.  Yes, we can reach OpenShift commands. If I don't get a 200 back, then this outcome, then I'm going to send a message that we can't reach OpenShift commands. It might also be that OpenShift comments is down, or it might be that I do not have outbound connectivity from my cluster. Going back to my support bundle, and at the very bottom, I'm going to add my analyzer. Just going to check. This one needs to be indented. There we go. And then I'm going to save this one. In order now to make this available to my end customer, I need to send this new version of my preflight YAML file. I need to send this to my vendor portal. So I'm going to use the replicated CLI in here. I guess I ran this already. So what I'm doing here with the replicated, I can do a replicated to release LS. This is going to show me in my vendor portal all the releases that I have available. You can see I just installed this particular one before we started the webinar. If I want to change this, I can change a new release. You can do a replicated release create, and I do dash dash auto. And I want to promote it immediately into the stable channel. Because the stable channel is also this channel that I'm using in my cluster as an end customer. So what this will do is probably going to, oh, yeah, because I used auto. So it's going to create a release, put it in the stable channel in there. And it's going to look into, because I specified auto, it's looking into manifests in there. And just say yes, this will send everything into the vendor portal there. Vendor portal is now going to have a new version available, which is going to be sequence number six. Me as an end customer, how do I get this available into my open shift environment? Well, there's actually a cron job running here that constantly checks for updates. But I can also trigger this myself. So I'm just going to check here now for updates into the vendor portal. If there's a new version available, you can see there is a new version available. There's a license change, which I previously did, I think, in there, but there's also an upstream update. This upstream update in particular that I'm interested in. And first thing that we do out of the box is when there's a new version is we check the preflights again. So if I go to my preflights, one thing that I'm particularly interested in is the one that you see here at the bottom. So this at the bottom that you see here is what I just added. As an application developer, I added a collector, just sending an HTTP request to check if I can reach open shift commons. And then I'm checking the output of that one, which is done here in the text analyzer, which shows me that, well, as an output, there must be a status 200 there because I'm seeing this message. And of course, I can continue this one, or I can just install the new version of my application, which, to be honest, isn't going to install anything because I didn't change anything in the actual application. So it's going to go fairly quick in there. That's it from my side. So I think next step is to go over and go into Q&A. Well, thank you guys. That was great. And really, I've seen replicated at Kubecons and other things, other events, and I've run by the booth and done that. But I think that was probably the best overview. I've got two streams going at the same time. Hang on. Hang tight here. I'll get my audio figured out here. So that was a great demo. So thank you very much for that. It really finally pulled together everything that I was wondering about where replicated was going and how it fit into the Kubernetes ecosystem. So that was incredibly useful for me. And I hope so for everybody else who watched. And one of the things Trevor and Josh that I was really, it was funny because you were just as you were demoing, and I was typing in, can we talk about the air gap stuff? Because that's like one of the more complicated use cases when you're doing some of this stuff. And you were right segwayed right into that as I was typing. So good on you guys for covering all of that. That was really great. And one of the things that's so interesting to me about this is because I know you had a really long-winded title for this, Trevor. But it really now makes sense, right? Because you're not just deploying, but you're managing, and you're patching, and you're upgrading, you're doing everything for all of these third-party apps.  We'll solve all of the mysteries of everything. But a real enterprise is running so many third-party apps and deploying so many different platforms that this is, I can totally see the use for this. But one of the things that I always ask people about, because I come from a bit of an IT audit background, and I'm a bit on it, is what I didn't really see was from a compliance and risk point of view. How you're tracking some of that, or the reporting in the back end of what you're doing with Replicade. How does this appear? So if I want to see, and maybe Josh can talk a little bit to that, if I want to see what's going on and keep track of all of the releases from an overview point of view. Yeah, I'm unmuted. Yeah, I did one update, basically, in COTS-ADM. But normally what you will see is that each time there is a corresponding change, it is going to show up in COTS-ADM and the whole person history. And then what I also did not highlight on is there is the capability to do a diff on all of those releases so that you can actually see what has been changed between all of them. And then that's going to be in the corresponding YAML. What we also see is that in terms of compliance and that kind of stuff is that sometimes in the more advanced use cases, and customers who want to have access to the actual raw YAML files, the ones that are going to be installed, there is of course access to that. And we even go a step further that instead of COTS-ADM installing the app, we can actually send everything into a GitHub repository and then people can use like an Orgo CD or a Flux to apply the application or install the new version of the application. We see that that is more common with the more advanced Kubernetes users who are experienced in that, who already have standardized on one of those GitHub solutions and they want to standardize on that for all of the applications that they have in their enterprise environment. In terms of audit, what you bring up is a very also a very good use case because I think I brought up like during the demo like number of users as part of the license. Well, what you can do is with troubleshoot is there's common use cases where people deliver third-party apps and they say it's licensed based on number of users, but they never validate the number of users because they do not really want to restrict their end customers. They just trust their customers. What you can do of course with troubleshoot is you could define a collector that collects the number of users and then you define an analyzer that just says, okay, you're in violation of your legal contract because you have 15 users and you're only paying for 10 or just put a warning up there, something like that and then do your whole audit tracking in there. Especially troubleshoot gives a lot of capabilities in order to run within a customer environment in there. You can basically anything that can run in a pod, anything that can run in a container, you can run that as part of troubleshoot and you can start analyzing on top of that which makes it great. So, I also have been reading a little bit about this enterpriseready.io site which sounds like in combination with everything else you're doing. How does that play in with everything else you're doing? Do you want to take that or shall I? Yes, Michael. I'm trying to find the unmute button. Enterprise Ready, that is actually our podcast website and that is just interviews with thought leaders in the tech community and it's very, very interesting. Our CEO grant and our CTO mark, they usually handle those interviews published weekly. Super fascinating. I highly encourage you all to subscribe. But yes, that's what Enterprise Ready is. I think the Enterprise Ready website also has kind of been, it's a kind of a content platform that we've sponsored for a number of years and it really, it's a guide for ISVs who kind of gauge their level of readiness to deliver their application to security conscious, large enterprise customers. So that has a great checklist of kind of feature roadmap, if you will, especially if you're a small SaaS vendor and you're trying to figure out how to take that SaaS application on-prem to a large enterprise customer, one of the sorts of features that those customers are going to demand, right? So we talk about things like audit and identity management and single side on and things like that. So it's really a great guide. We view it as just a resource for entrepreneurs and people that are building software companies and then kind of the centerpiece of that is the podcast that Treva mentioned where we've had some really just amazing founders, you know, folks like Loris DiGiorni from Cystig, you know, the folks that invented Wireshark, Tom Preston Warner, original CEO, founder of GitHub. So really just a great, you know, set of startup luminaries and just smart founders and CEOs that Grant and Mark speak with on the podcast. But the website again is really kind of a cool guide for software companies that are trying to make that journey to make their product enterprise ready as the name implies. But thank you so much for having us, Diane. This has been great. I think that that's the wonderful value proposition I think replicated is that you're really facilitating a lot of other people's applications getting into and being useful to enterprises and being secure enough that enterprises will take them seriously. And that's I've seen and listened to some of the podcast stuff in the past as well. And I think that's really the sweet spot that you guys are in is that you are making it possible for all of these third party applications to, you know, in some ways you're helping with the enterprise ready content and coaching and pieces in helping incubate these third party apps and get them ready for prime time. And then once they're there using the replicated suite really helps the enterprises trust and be able to deploy these things securely in a consistent way. So it's really been very interesting and a good eye opener for me. One of the things like I said in passing at the beginning, I've walked by the replicated booth at KubeCon and stopped in. I've chatted with people. This has really helped me place where you are in the ecosystem very nicely today. We're really thrilled that you guys have joined OpenShift Commons. We look forward to hearing more about each of these individual projects, Trevor. Don't worry. We will find time for everything troubleshoot. I hadn't seen it before. It is like totally cool. And so I think I'm encouraging people to take a look at that as well because I think there's lots of tools in here that rather than reinvent the wheel, people can also use in their installment and deployment practices. So I think that's really another useful thing. And I just love how open source you guys all are. So I so appreciate that. Trevor, tell us a little bit about what's going to happen. The community Cal, where we're going next, where we need to go find you guys to get involved. Yes. So main page, replicated.com. As I mentioned, we have a lot of open source projects with the list growing every day. It's about to expand by two or three in the next couple of months. Go over to replicated.com slash OSS for a list of all of our current projects and keep an eye on what is coming next. I think you're really going to like the next project that's coming out. So the projects that we talked about today are on the replicated HQ GitHub repo. And that's at replicated HQ slash COTS for COTS Kubernetes off the shelf. Curl replicated HQ slash curl for curl and troubleshoot for troubleshoot. I'm not reading this out very well. I apologize, but hopefully like seeing them written out will help you to get there better. And also there's the community calendar. We are having community meetings for troubleshoot this coming Thursday at 2pm Eastern. And then we're also having meetings for schema hero and for COTS, I believe for curl. I'm sorry. And we'll be adding more to that calendar. So that's an easy way to keep track of what's happening with like replicated open source replicated community. And I'll be adding more events as they come along. So I certainly hope that you'll subscribe to that. And I hope to see you either online or in person. Gaby and I really enjoyed being here. Thank you so much Diane for the invite. But I think that's all my feel. So join the community. One last thing to add Diane is that we are replicated as a Red Hat business partner now. And also in the process of getting the replicated platform that you just saw certified for open shift. As you know, there was that change a while ago to having to ship on the UBI. So we have a little bit of a delay while we get onto the UBI. But we absolutely have every intention of getting the replicated solution certified for open shift. So that both enterprise and users and ISVs can kind of ship with confidence knowing that it is a runs on open shift certified platform. So that's our goal. That is awesome to hear that that's on your hit list. And you're going to get that done. So we'll have you back when that happens again and celebrate and raise some a glass or two. Hopefully we'll see you all at KUKON in person. I'm really hoping. Fingers crossed. And Schema Hero is something I want to hear more about. I'm going to launch a cloud native TV show sometime later in September. Mentoring new open source projects that are in the CNCF. It's called Cloud Next. And I think that might be a good candidate for it. Because now with the something I don't know how many we're going to have 50 odd sandbox projects. There's a lot of noise. And so it would be wonderful to get to deep dive into Schema Hero a little bit. So I'll reach out to you about participating in that at some point as well, Trevor. So as always, huge pleasure hearing from all of you. Thank you for giving us this update and insights into what you're doing. There's lots more to come, obviously. So take care all. And thanks to Chris Short, our producer for making this happen. And Amit and the whole team, Josh and Trevor, well done. Well, we look forward to hearing much more from you all. Take care all. Thank you, everyone. Thank you. Thanks, everybody. Bye.