Upbound is the industry’s first platform for building internal cloud platforms

Upbound

The Way We Live Now by Anthony Trollope is part of the HackerNoon Books Series. You can jump to any chapter in this book . RUBY RUGGLES OBEYS HER GRANDFATHER here RUBY RUGGLES OBEYS HER GRANDFATHER. The next day there was great surprise at Sheep's Acre farm, which communicated itself to the towns of Bungay and Beccles, and even affected the ordinary quiet life of Carbury Manor. Ruby Ruggles had gone away, and at about twelve o'clock in the day the old farmer became aware of the fact. She had started early, at about seven in the morning; but Ruggles himself had been out long before that, and had not condescended to ask for her when he returned to the house for his breakfast. There had been a bad scene up in the bedroom overnight, after John Crumb had left the farm. The old man in his anger had tried to expel the girl; but she had hung on to the bed-post and would not go; and he had been frightened, when the maid came up crying and screaming murder. "You'll be out o' this to-morrow as sure as my name's Dannel Ruggles," said the farmer panting for breath. But for the gin which he had taken he would hardly have struck her;—but he had struck her, and pulled her by the hair, and knocked her about;—and in the morning she took him at his word and was away. About twelve he heard from the servant girl that she had gone. She had packed a box and had started up the road carrying the box herself. "Grandfather says I'm to go, and I'm gone," she had said to the girl. At the first cottage she had got a boy to carry her box into Beccles, and to Beccles she had walked. For an hour or two Ruggles sat, quiet, within the house, telling himself that she might do as she pleased with herself,—that he was well rid of her, and that from henceforth he would trouble himself no more about her. But by degrees there came upon him a feeling half of compassion and half of fear, with perhaps some mixture of love, instigating him to make search for her. She had been the same to him as a child, and what would people say of him if he allowed her to depart from him after this fashion? Then he remembered his violence the night before, and the fact that the servant girl had heard if she had not seen it. He could not drop his responsibility in regard to Ruby, even if he would. So, as a first step, he sent in a message to John Crumb, at Bungay, to tell him that Ruby Ruggles had gone off with a box to Beccles. John Crumb went open-mouthed with the news to Joe Mixet, and all Bungay soon knew that Ruby Ruggles had run away. After sending his message to Crumb the old man still sat thinking, and at last made up his mind that he would go to his landlord. He held a part of his farm under Roger Carbury, and Roger Carbury would tell him what he ought to do. A great trouble had come upon him. He would fain have been quiet, but his conscience and his heart and his terrors all were at work together,—and he found that he could not eat his dinner. So he had out his cart and horse and drove himself off to Carbury Hall. It was past four when he started, and he found the squire seated on the terrace after an early dinner, and with him was Father Barham, the priest. The old man was shown at once round into the garden, and was not long in telling his story. There had been words between him and his granddaughter about her lover. Her lover had been accepted and had come to the farm to claim his bride. Ruby had behaved very badly. The old man made the most of Ruby's bad behaviour, and of course as little as possible of his own violence. But he did explain that there had been threats used when Ruby refused to take the man, and that Ruby had, this day, taken herself off. "I always thought it was settled they were to be man and wife," said Roger. "It was settled, squoire;—and he war to have five hun'erd pound down;—money as I'd saved myself. Drat the jade." "Didn't she like him, Daniel?" "She liked him well enough till she'd seed somebody else." Then old Daniel paused, and shook his head, and was evidently the owner of a secret. The squire got up and walked round the garden with him,—and then the secret was told. The farmer was of opinion that there was something between the girl and Sir Felix. Sir Felix some weeks since had been seen near the farm and on the same occasion Ruby had been observed at some little distance from the house with her best clothes on. "He's been so little here, Daniel," said the squire. "It goes as tinder and a spark o' fire, that does," said the farmer. "Girls like Ruby don't want no time to be wooed by one such as that, though they'll fall-lall with a man like John Crumb for years." "I suppose she's gone to London." "Don't know nothing of where she's gone, squoire;—only she have gone some'eres. May be it's Lowestoffe. There's lots of quality at Lowestoffe a' washing theyselves in the sea." Then they returned to the priest, who might be supposed to be cognisant of the guiles of the world and competent to give advice on such an occasion as this. "If she was one of our people," said Father Barham, "we should have her back quick enough." "Would ye now?" said Ruggles, wishing at the moment that he and all his family had been brought up as Roman Catholics. "I don't see how you would have more chance of catching her than we have," said Carbury. "She'd catch herself. Wherever she might be she'd go to the priest, and he wouldn't leave her till he'd seen her put on the way back to her friends." "With a flea in her lug," suggested the farmer. "Your people never go to a clergyman in their distress. It's the last thing they'd think of. Any one might more probably be regarded as a friend than the parson. But with us the poor know where to look for sympathy." "She ain't that poor, neither," said the grandfather. "She had money with her?" "I don't know just what she had; but she ain't been brought up poor. And I don't think as our Ruby'd go of herself to any clergyman. It never was her way." "It never is the way with a Protestant," said the priest. "We'll say no more about that for the present," said Roger, who was waxing wroth with the priest. That a man should be fond of his own religion is right; but Roger Carbury was beginning to think that Father Barham was too fond of his religion. "What had we better do? I suppose we shall hear something of her at the railway. There are not so many people leaving Beccles but that she may be remembered." So the waggonette was ordered, and they all prepared to go off to the station together. But before they started John Crumb rode up to the door. He had gone at once to the farm on hearing of Ruby's departure, and had followed the farmer from thence to Carbury. Now he found the squire and the priest and the old man standing around as the horses were being put to the carriage. "Ye ain't a' found her, Mr. Ruggles, ha' ye?" he asked as he wiped the sweat from his brow. "Noa;—we ain't a' found no one yet." "If it was as she was to come to harm, Mr. Carbury, I'd never forgive myself,—never," said Crumb. "As far as I can understand it is no doing of yours, my friend," said the squire. "In one way, it ain't; and in one way it is. I was over there last night a bothering of her. She'd a' come round may be, if she'd a' been left alone. She wouldn't a' been off now, only for our going over to Sheep's Acre. But,—oh!" "What is it, Mr. Crumb?" "He's a coosin o' yours, squoire; and long as I've known Suffolk, I've never known nothing but good o' you and yourn. But if your baronite has been and done this! Oh, Mr. Carbury! If I was to wring his neck round, you wouldn't say as how I was wrong; would ye, now?" Roger could hardly answer the question. On general grounds the wringing of Sir Felix's neck, let the immediate cause for such a performance have been what it might, would have seemed to him to be a good deed. The world would be better, according to his thinking, with Sir Felix out of it than in it. But still the young man was his cousin and a Carbury, and to such a one as John Crumb he was bound to defend any member of his family as far as he might be defensible. "They says as how he was groping about Sheep's Acre when he was last here, a hiding himself and skulking behind hedges. Drat 'em all. They've gals enough of their own,—them fellows. Why can't they let a fellow alone? I'll do him a mischief, Master Roger; I wull;—if he's had a hand in this." Poor John Crumb! When he had his mistress to win he could find no words for himself; but was obliged to take an eloquent baker with him to talk for him. Now in his anger he could talk freely enough. "But you must first learn that Sir Felix has had anything to do with this, Mr. Crumb." "In coorse; in coorse. That's right. That's right. Must l'arn as he did it, afore I does it. But when I have l'arned!"— And John Crumb clenched his fist as though a very short lesson would suffice for him upon this occasion. They all went to the Beccles Station, and from thence to the Beccles post office,—so that Beccles soon knew as much about it as Bungay. At the railway station Ruby was distinctly remembered. She had taken a second-class ticket by the morning train for London, and had gone off without any appearance of secrecy. She had been decently dressed, with a hat and cloak, and her luggage had been such as she might have been expected to carry, had all her friends known that she was going. So much was made clear at the railway station, but nothing more could be learned there. Then a message was sent by telegraph to the station in London, and they all waited, loitering about the post office, for a reply. One of the porters in London remembered seeing such a girl as was described, but the man who was supposed to have carried her box for her to a cab had gone away for the day. It was believed that she had left the station in a four-wheel cab. "I'll be arter her. I'll be arter her at once," said John Crumb. But there was no train till night, and Roger Carbury was doubtful whether his going would do any good. It was evidently fixed on Crumb's mind that the first step towards finding Ruby would be the breaking of every bone in the body of Sir Felix Carbury. Now it was not at all apparent to the squire that his cousin had had anything to do with this affair. It had been made quite clear to him that the old man had quarrelled with his granddaughter and had threatened to turn her out of his house, not because she had misbehaved with Sir Felix, but on account of her refusing to marry John Crumb. John Crumb had gone over to the farm expecting to arrange it all, and up to that time there had been no fear about Felix Carbury. Nor was it possible that there should have been communication between Ruby and Felix since the quarrel at the farm. Even if the old man were right in supposing that Ruby and the baronet had been acquainted,—and such acquaintance could not but be prejudicial to the girl,—not on that account would the baronet be responsible for her abduction. John Crumb was thirsting for blood and was not very capable in his present mood of arguing the matter out coolly, and Roger, little as he loved his cousin, was not desirous that all Suffolk should know that Sir Felix Carbury had been thrashed within an inch of his life by John Crumb of Bungay. "I'll tell you what I'll do," said he, putting his hand kindly on the old man's shoulder. "I'll go up myself by the first train to-morrow. I can trace her better than Mr. Crumb can do, and you will both trust me." "There's not one in the two counties I'd trust so soon," said the old man. "But you'll let us know the very truth," said John Crumb. Roger Carbury made him an indiscreet promise that he would let him know the truth. So the matter was settled, and the grandfather and lover returned together to Bungay. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Anthony Trollope (2004). The Way We Live Now. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/5231/pg5231-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

RUBY RUGGLES OBEYS HER GRANDFATHER

Delivering Cloud Infrastructure the GitOps Way with Crossplane and ArgoCD

What are Internal Developer Platforms (IDPs)? Internal developer platforms (IDPs) are platforms that developers can leverage to build and deploy their applications to one of the environments. Their main purpose is to increase the pace of development and reduce the developer’s dependence on DevOps and Platform engineers through automation and developer self-service. The platform may be built in-house, usually, an adaptation of an open-source or purchased offering such as platform as a Service (PaaS). The adoption has been both recent and rapid. Puppet’s state of platform engineering finds that over 51% of companies that have adopted Internal Developer Platforms have done it in the past three years. And an overwhelming majority of the respondents (93%) declared that IDP adoption is a step in the right direction. survey Internal developer platforms are good at helping the team manage applications and infrastructure from one place, providing tight integration with the existing tools and services, and giving developers self-serve and collaboration capabilities. Benefits of IDPs IDPs offer several benefits to the organizations using them. The first relates to improvements in infrastructure and IT management, such as increased productivity stemming from reduced communication times between devs and infra teams. Secondly, they reduce the complexity of the cloud and make it easy for people in your org to pick up on the best practices set forward by your team. In larger organizations, they can also be an easy way of managing RBAC to deployments, infra creation and management, and more. Responses from Puppet’s State of Platform Engineering 2023 report also show how IDP has improved : DevOps KPIs An increase in development velocity (68%) 42% say development velocity has improved “a great deal” since they started doing platform engineering Improved productivity (59%) Improved system reliability (60%) Improved security (55%) Components of IDPs Let’s dive deeper into the components of IDPs and discuss which parts of the application and infrastructure management process they improve. IDPs are built by integrating with the existing set of tools and services that the company currently uses. These can be your source control systems (e.g., GitHub, GitLab), Continuous Integration and Continuous Deployment (CI/CD) pipelines, and observability tools such as monitoring and logging systems. Integration with existing tools and services In addition, they may also include some form of access control, observability dashboards, and a set of best practices for developers to use. Application and infrastructure management IDPs can be used to automate a lot of the hassle of deployment. By setting up IDPs with GitOps best practices, users can automatically deploy application and infra changes with each commit to the Git code. Managing multiple environments is another popular use case of IDPs. They can be effective in creating, providing selective access, and managing the use of multiple different environments such as development, testing, pre-prod, and prod. Several tools set up preview environments on the fly. Their ability to monitor and view deployments across environments helps organizations scale dynamically to changing workloads and maintain consistent performance across their infrastructure. IDPs empower developers with self-serve capabilities by offering a centralized, user-friendly interface to access tools, resources, and services on demand. These capabilities facilitate faster development cycles, reduce operations teams’ dependency, and enable greater autonomy in seamlessly creating, testing, and deploying applications. Developer self-service capabilities The streamlined workflow also makes it considerably easier for new employees to get started with your stack without diving into the internal workings. Some tools also add a collaboration layer on top that allows different members of a team to work together easily and review changes before deploying the code. IDPs can achieve enhanced security and compliance by providing Role-based access controls (RBAC), ensuring each team member has the appropriate permissions to access specific resources and perform certain actions. Overall, this minimized the risk of unauthorized access or accidental changes while also promoting collaboration and efficient workflows among cross-functional teams. Collaboration and governance features IDPs help developer teams maintain transparency, accountability, and traceability throughout the development process by providing audit logs and history tracking. This enables easier identification and resolution of issues, as well as ensures compliance with regulatory and organizational requirements for data handling and change management. Platform engineering Companies that decide to build their own platform usually hire platform engineers, who are specialized professionals responsible for the creation and continuous improvement of the IDP. They work to implement and maintain tools, services, and best practices that streamline development processes, ensuring a smooth and efficient workflow for the organization's developers. Platform engineering is the process of designing, building, and maintaining an IDP that provides a centralized, scalable, and efficient infrastructure for developers within an organization. An IDP simplifies and standardizes application development, deployment, and management, enabling faster and more reliable software delivery. Software development trends that are catalysts for IDP adoption Digital transformation: As businesses worldwide increasingly embrace digital transformation, there is a growing need for efficient and robust software development processes. IDPs play a crucial role in enabling companies to stay agile and quickly adapt to the dynamic digital landscape. Need for faster software delivery: In today's fast-paced business environment, organizations must deliver new features and applications at an unprecedented speed. IDPs provide a standardized, automated, and centralized platform that accelerates development cycles, enabling companies to stay competitive and responsive to market changes. The growing complexity of software architectures: With the rise of microservices, containers, and cloud-native technologies, managing and deploying software has become increasingly complex. IDPs help simplify this complexity by providing a unified platform where developers can build, test, and deploy applications with ease, regardless of the underlying architecture. Demand for DevOps and CI/CD practices: The need for IDPs grows as more organizations adopt DevOps and Continuous Integration/Continuous Deployment (CI/CD) practices. IDPs enable seamless collaboration between development and operations teams, automating many manual tasks and ensuring smooth transitions throughout the software development lifecycle. Scalability and flexibility: IDPs offer a scalable solution that can accommodate the growing needs of organizations, regardless of their size. They provide a flexible platform that can be easily customized and adapted to cater to the unique requirements of different teams and projects. Cross-region collaboration: With businesses operating across multiple geographies, the need for a platform that supports cross-region collaboration is essential. IDPs empower development teams spread across the globe to work together seamlessly, enabling efficient knowledge sharing and fostering a culture of innovation. In summary, the rising popularity of IDPs across companies of all sizes and regions worldwide can be attributed to their ability to streamline software development processes, simplify complex architectures, support DevOps and CI/CD practices, and facilitate cross-region collaboration. As the demand for digitalization and agility continues to grow, IDPs are poised to play a critical role in shaping the future of software development. Commercially available internal developer platforms is a DevOps automation platform that helps engineering manage both the app and infra side of things and ship faster! Built with the GitOps best practices in mind, Argonaut reduces the complexities of creating and maintaining cloud setups. Whether it is Kubernetes app deployment to AWS or GCP, there are several runtimes, environments, regions, integrations, and app types to choose from. Argonaut offers a simple way to develop and operate modern cloud applications on Kubernetes. It can be adopted as either a self-hosted or PaaS option. There’s also a with essential plugins, templates, and applications making it easier to get started. Its features benefit not only the developers but also the platform engineers and CIOs. Mia Platform marketplace is an internal developer platform providing simplicity, automation, reusability, and self-service. It acts as a Platform Orchestrator that lets engineering teams remove bottlenecks by enabling them to build code-based golden paths (executable config files and templates) for developers. It can be used through the CLI or UI. Humanitec provides engineering teams self-serve access to tools and information. It helps developers ensure operational excellence across services with its that can be set up in a secure and compliant way. Opslevel integrations is a Kubernetes application management platform that enables efficient deployment processes. Developers can leverage its standardized application and policy definitions that are platform-agnostic. It also has a GUI-based portal to manage apps after deployment and gain visibility into pipelines for smoother operations. Shipa provides a context-rich software catalog with maturity and quality scorecards. It also supports comprehensive developer self-service actions while providing additional role-based access controls (RBAC). Their provides many key features and makes it a worthy contender. Port free-forever , powered by Crossplane, offers an enterprise-grade control plane solution for multi-cloud and hybrid environments, enabling efficient management of cloud infrastructure. The command line and make it more effective and easier to get started. Upbound Up Upbound marketplace is an all-in-one DevOps platform that streamlines the application deployment process. It provides a comprehensive feature set in a modular manner that allows teams to focus fully on business functionality. DevOpsBox Evaluating Internal Developer Platforms Despite its myriad of benefits, Internal Developer Platforms do not make sense for all teams. They can end up being overkill for certain types of engineering teams and a burden to build and maintain for companies with smaller teams. When they don’t make sense You have existing processes that are efficient. Don’t complicate things too early. Companies that are currently using PaaS or other managed offerings should continue doing so as long as possible. Limited resources and team size. This could also mean your team is small, and most of your team is senior and comfortable writing scripts and managing infrastructure. There is low development complexity. If you have just one app with a simple single-cloud setup. And, if your app is monolithic and doesn’t make use of the microservice architecture, there is little benefit from creating an IDP. Incompatible organizational culture. If an organization’s culture is resistant to change or does not foster collaboration and communication, implementing an IDP might not be successful and could even lead to decreased efficiency and productivity. When they make sense You plan to start using Microservices. This usually also means a growing development team size or the complexity of projects you handle. You have a small team, and not everyone feels comfortable with deployments, scripting, and infrastructure, and you have not yet hired a dedicated DevOps. Dependencies on other colleagues are blocking your developers. The cost of your existing setup (such as PaaS) is too high. Which is inevitable once you start to scale to meet new requirements. You have plans to go multi-cloud, adopt more modern cloud services, and scale geographically. You want to increase standardization and consistency across your teams. An IDP can help reduce errors, improve code quality, and ensure all developers work with the same set of tools and follow the same best practices. Also published here.

An In-Depth Guide to Internal Developer Platforms (IDPs)

Una guía detallada de las plataformas internas para desarrolladores (IDP)

Un guide détaillé des plates-formes de développement internes (IDP)

आंतरिक डेवलपर प्लेटफ़ॉर्म (IDPs) के लिए एक गहन मार्गदर्शिका

内部開発者プラットフォーム (IDP) の詳細ガイド

Um guia detalhado para plataformas internas de desenvolvedores (IDPs)

Hướng dẫn chuyên sâu về Nền tảng dành cho nhà phát triển nội bộ (IDP)

内部开发者平台 (IDP) 深度指南

The Strange Case Of Dr. Jekyll And Mr. Hyde by Robert Louis Stevenson is part of HackerNoon’s Book Blog Post series. You can jump to any chapter in this book here . Chapter IX: Dr. Lanyon's Narrative CHAPTER IX. DR. LANYON’S NARRATIVE On the ninth of January, now four days ago, I received by the evening delivery a registered envelope, addressed in the hand of my colleague and old school companion, Henry Jekyll. I was a good deal surprised by this; for we were by no means in the habit of correspondence; I had seen the man, dined with him, indeed, the night before; and I could imagine nothing in our intercourse that should justify formality of registration. The contents increased my wonder; for this is how the letter ran: “10th December, 18—. “Dear Lanyon,—You are one of my oldest friends; and although we may have differed at times on scientific questions, I cannot remember, at least on my side, any break in our affection. There was never a day when, if you had said to me, ‘Jekyll, my life, my honour, my reason, depend upon you,’ I would not have sacrificed my left hand to help you. Lanyon, my life, my honour, my reason, are all at your mercy; if you fail me to-night, I am lost. You might suppose, after this preface, that I am going to ask you for something dishonourable to grant. Judge for yourself. “I want you to postpone all other engagements for to-night—ay, even if you were summoned to the bedside of an emperor; to take a cab, unless your carriage should be actually at the door; and with this letter in your hand for consultation, to drive straight to my house. Poole, my butler, has his orders; you will find him waiting your arrival with a locksmith. The door of my cabinet is then to be forced; and you are to go in alone; to open the glazed press (letter E) on the left hand, breaking the lock if it be shut; and to draw out, with all its contents as they stand, the fourth drawer from the top or (which is the same thing) the third from the bottom. In my extreme distress of mind, I have a morbid fear of misdirecting you; but even if I am in error, you may know the right drawer by its contents: some powders, a phial and a paper book. This drawer I beg of you to carry back with you to Cavendish Square exactly as it stands. “That is the first part of the service: now for the second. You should be back, if you set out at once on the receipt of this, long before midnight; but I will leave you that amount of margin, not only in the fear of one of those obstacles that can neither be prevented nor foreseen, but because an hour when your servants are in bed is to be preferred for what will then remain to do. At midnight, then, I have to ask you to be alone in your consulting room, to admit with your own hand into the house a man who will present himself in my name, and to place in his hands the drawer that you will have brought with you from my cabinet. Then you will have played your part and earned my gratitude completely. Five minutes afterwards, if you insist upon an explanation, you will have understood that these arrangements are of capital importance; and that by the neglect of one of them, fantastic as they must appear, you might have charged your conscience with my death or the shipwreck of my reason. “Confident as I am that you will not trifle with this appeal, my heart sinks and my hand trembles at the bare thought of such a possibility. Think of me at this hour, in a strange place, labouring under a blackness of distress that no fancy can exaggerate, and yet well aware that, if you will but punctually serve me, my troubles will roll away like a story that is told. Serve me, my dear Lanyon and save “Your friend, “H.J. “P.S.—I had already sealed this up when a fresh terror struck upon my soul. It is possible that the post-office may fail me, and this letter not come into your hands until to-morrow morning. In that case, dear Lanyon, do my errand when it shall be most convenient for you in the course of the day; and once more expect my messenger at midnight. It may then already be too late; and if that night passes without event, you will know that you have seen the last of Henry Jekyll.” Upon the reading of this letter, I made sure my colleague was insane; but till that was proved beyond the possibility of doubt, I felt bound to do as he requested. The less I understood of this farrago, the less I was in a position to judge of its importance; and an appeal so worded could not be set aside without a grave responsibility. I rose accordingly from table, got into a hansom, and drove straight to Jekyll’s house. The butler was awaiting my arrival; he had received by the same post as mine a registered letter of instruction, and had sent at once for a locksmith and a carpenter. The tradesmen came while we were yet speaking; and we moved in a body to old Dr. Denman’s surgical theatre, from which (as you are doubtless aware) Jekyll’s private cabinet is most conveniently entered. The door was very strong, the lock excellent; the carpenter avowed he would have great trouble and have to do much damage, if force were to be used; and the locksmith was near despair. But this last was a handy fellow, and after two hour’s work, the door stood open. The press marked E was unlocked; and I took out the drawer, had it filled up with straw and tied in a sheet, and returned with it to Cavendish Square. Here I proceeded to examine its contents. The powders were neatly enough made up, but not with the nicety of the dispensing chemist; so that it was plain they were of Jekyll’s private manufacture; and when I opened one of the wrappers I found what seemed to me a simple crystalline salt of a white colour. The phial, to which I next turned my attention, might have been about half full of a blood-red liquor, which was highly pungent to the sense of smell and seemed to me to contain phosphorus and some volatile ether. At the other ingredients I could make no guess. The book was an ordinary version book and contained little but a series of dates. These covered a period of many years, but I observed that the entries ceased nearly a year ago and quite abruptly. Here and there a brief remark was appended to a date, usually no more than a single word: “double” occurring perhaps six times in a total of several hundred entries; and once very early in the list and followed by several marks of exclamation, “total failure!!!” All this, though it whetted my curiosity, told me little that was definite. Here were a phial of some salt, and the record of a series of experiments that had led (like too many of Jekyll’s investigations) to no end of practical usefulness. How could the presence of these articles in my house affect either the honour, the sanity, or the life of my flighty colleague? If his messenger could go to one place, why could he not go to another? And even granting some impediment, why was this gentleman to be received by me in secret? The more I reflected the more convinced I grew that I was dealing with a case of cerebral disease; and though I dismissed my servants to bed, I loaded an old revolver, that I might be found in some posture of self-defence. Twelve o’clock had scarce rung out over London, ere the knocker sounded very gently on the door. I went myself at the summons, and found a small man crouching against the pillars of the portico. “Are you come from Dr. Jekyll?” I asked. He told me “yes” by a constrained gesture; and when I had bidden him enter, he did not obey me without a searching backward glance into the darkness of the square. There was a policeman not far off, advancing with his bull’s eye open; and at the sight, I thought my visitor started and made greater haste. These particulars struck me, I confess, disagreeably; and as I followed him into the bright light of the consulting room, I kept my hand ready on my weapon. Here, at last, I had a chance of clearly seeing him. I had never set eyes on him before, so much was certain. He was small, as I have said; I was struck besides with the shocking expression of his face, with his remarkable combination of great muscular activity and great apparent debility of constitution, and—last but not least—with the odd, subjective disturbance caused by his neighbourhood. This bore some resemblance to incipient rigour, and was accompanied by a marked sinking of the pulse. At the time, I set it down to some idiosyncratic, personal distaste, and merely wondered at the acuteness of the symptoms; but I have since had reason to believe the cause to lie much deeper in the nature of man, and to turn on some nobler hinge than the principle of hatred. This person (who had thus, from the first moment of his entrance, struck in me what I can only describe as a disgustful curiosity) was dressed in a fashion that would have made an ordinary person laughable; his clothes, that is to say, although they were of rich and sober fabric, were enormously too large for him in every measurement—the trousers hanging on his legs and rolled up to keep them from the ground, the waist of the coat below his haunches, and the collar sprawling wide upon his shoulders. Strange to relate, this ludicrous accoutrement was far from moving me to laughter. Rather, as there was something abnormal and misbegotten in the very essence of the creature that now faced me—something seizing, surprising and revolting—this fresh disparity seemed but to fit in with and to reinforce it; so that to my interest in the man’s nature and character, there was added a curiosity as to his origin, his life, his fortune and status in the world. These observations, though they have taken so great a space to be set down in, were yet the work of a few seconds. My visitor was, indeed, on fire with sombre excitement. “Have you got it?” he cried. “Have you got it?” And so lively was his impatience that he even laid his hand upon my arm and sought to shake me. I put him back, conscious at his touch of a certain icy pang along my blood. “Come, sir,” said I. “You forget that I have not yet the pleasure of your acquaintance. Be seated, if you please.” And I showed him an example, and sat down myself in my customary seat and with as fair an imitation of my ordinary manner to a patient, as the lateness of the hour, the nature of my preoccupations, and the horror I had of my visitor, would suffer me to muster. “I beg your pardon, Dr. Lanyon,” he replied civilly enough. “What you say is very well founded; and my impatience has shown its heels to my politeness. I come here at the instance of your colleague, Dr. Henry Jekyll, on a piece of business of some moment; and I understood...” He paused and put his hand to his throat, and I could see, in spite of his collected manner, that he was wrestling against the approaches of the hysteria—“I understood, a drawer...” But here I took pity on my visitor’s suspense, and some perhaps on my own growing curiosity. “There it is, sir,” said I, pointing to the drawer, where it lay on the floor behind a table and still covered with the sheet. He sprang to it, and then paused, and laid his hand upon his heart; I could hear his teeth grate with the convulsive action of his jaws; and his face was so ghastly to see that I grew alarmed both for his life and reason. “Compose yourself,” said I. He turned a dreadful smile to me, and as if with the decision of despair, plucked away the sheet. At sight of the contents, he uttered one loud sob of such immense relief that I sat petrified. And the next moment, in a voice that was already fairly well under control, “Have you a graduated glass?” he asked. I rose from my place with something of an effort and gave him what he asked. He thanked me with a smiling nod, measured out a few minims of the red tincture and added one of the powders. The mixture, which was at first of a reddish hue, began, in proportion as the crystals melted, to brighten in colour, to effervesce audibly, and to throw off small fumes of vapour. Suddenly and at the same moment, the ebullition ceased and the compound changed to a dark purple, which faded again more slowly to a watery green. My visitor, who had watched these metamorphoses with a keen eye, smiled, set down the glass upon the table, and then turned and looked upon me with an air of scrutiny. “And now,” said he, “to settle what remains. Will you be wise? will you be guided? will you suffer me to take this glass in my hand and to go forth from your house without further parley? or has the greed of curiosity too much command of you? Think before you answer, for it shall be done as you decide. As you decide, you shall be left as you were before, and neither richer nor wiser, unless the sense of service rendered to a man in mortal distress may be counted as a kind of riches of the soul. Or, if you shall so prefer to choose, a new province of knowledge and new avenues to fame and power shall be laid open to you, here, in this room, upon the instant; and your sight shall be blasted by a prodigy to stagger the unbelief of Satan.” “Sir,” said I, affecting a coolness that I was far from truly possessing, “you speak enigmas, and you will perhaps not wonder that I hear you with no very strong impression of belief. But I have gone too far in the way of inexplicable services to pause before I see the end.” “It is well,” replied my visitor. “Lanyon, you remember your vows: what follows is under the seal of our profession. And now, you who have so long been bound to the most narrow and material views, you who have denied the virtue of transcendental medicine, you who have derided your superiors—behold!” He put the glass to his lips and drank at one gulp. A cry followed; he reeled, staggered, clutched at the table and held on, staring with injected eyes, gasping with open mouth; and as I looked there came, I thought, a change—he seemed to swell—his face became suddenly black and the features seemed to melt and alter—and the next moment, I had sprung to my feet and leaped back against the wall, my arms raised to shield me from that prodigy, my mind submerged in terror. “O God!” I screamed, and “O God!” again and again; for there before my eyes—pale and shaken, and half fainting, and groping before him with his hands, like a man restored from death—there stood Henry Jekyll! What he told me in the next hour, I cannot bring my mind to set on paper. I saw what I saw, I heard what I heard, and my soul sickened at it; and yet now when that sight has faded from my eyes, I ask myself if I believe it, and I cannot answer. My life is shaken to its roots; sleep has left me; the deadliest terror sits by me at all hours of the day and night; and I feel that my days are numbered, and that I must die; and yet I shall die incredulous. As for the moral turpitude that man unveiled to me, even with tears of penitence, I cannot, even in memory, dwell on it without a start of horror. I will say but one thing, Utterson, and that (if you can bring your mind to credit it) will be more than enough. The creature who crept into my house that night was, on Jekyll’s own confession, known by the name of Hyde and hunted for in every corner of the land as the murderer of Carew. HASTIE LANYON. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Stevenson, Robert Louis, 1992. The Strange Case Of Dr. Jekyll And Mr. Hyde. Urbana, Illinois: Project Gutenberg. Retrieved May 2022 from https://www.gutenberg.org/files/43/43-h/43-h.htm#chap09 This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org, located at https://www.gutenberg.org/policy/license.html.

The Strange Case Of Dr. Jekyll And Mr. Hyde: Chapter IX - Dr. Lanyon's Narrative 

Photo by on Jason Blackeye Unsplash Adventures of Huckleberry Finn, by Mark Twain (Samuel Clemens) is part of HackerNoon’s Book Blog Post series. You can jump to any chapter in this book . here CHAPTER XII. It must a been close on to one o’clock when we got below the island at last, and the raft did seem to go mighty slow. If a boat was to come along we was going to take to the canoe and break for the Illinois shore; and it was well a boat didn’t come, for we hadn’t ever thought to put the gun in the canoe, or a fishing-line, or anything to eat. We was in ruther too much of a sweat to think of so many things. It warn’t good judgment to put everything on the raft. If the men went to the island I just expect they found the camp fire I built, and watched it all night for Jim to come. Anyways, they stayed away from us, and if my building the fire never fooled them it warn’t no fault of mine. I played it as low down on them as I could. When the first streak of day began to show we tied up to a towhead in a big bend on the Illinois side, and hacked off cottonwood branches with the hatchet, and covered up the raft with them so she looked like there had been a cave-in in the bank there. A tow-head is a sandbar that has cottonwoods on it as thick as harrow-teeth. We had mountains on the Missouri shore and heavy timber on the Illinois side, and the channel was down the Missouri shore at that place, so we warn’t afraid of anybody running across us. We laid there all day, and watched the rafts and steamboats spin down the Missouri shore, and up-bound steamboats fight the big river in the middle. I told Jim all about the time I had jabbering with that woman; and Jim said she was a smart one, and if she was to start after us herself she wouldn’t set down and watch a camp fire—no, sir, she’d fetch a dog. Well, then, I said, why couldn’t she tell her husband to fetch a dog? Jim said he bet she did think of it by the time the men was ready to start, and he believed they must a gone up-town to get a dog and so they lost all that time, or else we wouldn’t be here on a towhead sixteen or seventeen mile below the village—no, indeedy, we would be in that same old town again. So I said I didn’t care what was the reason they didn’t get us as long as they didn’t. When it was beginning to come on dark we poked our heads out of the cottonwood thicket, and looked up and down and across; nothing in sight; so Jim took up some of the top planks of the raft and built a snug wigwam to get under in blazing weather and rainy, and to keep the things dry. Jim made a floor for the wigwam, and raised it a foot or more above the level of the raft, so now the blankets and all the traps was out of reach of steamboat waves. Right in the middle of the wigwam we made a layer of dirt about five or six inches deep with a frame around it for to hold it to its place; this was to build a fire on in sloppy weather or chilly; the wigwam would keep it from being seen. We made an extra steering-oar, too, because one of the others might get broke on a snag or something. We fixed up a short forked stick to hang the old lantern on, because we must always light the lantern whenever we see a steamboat coming down-stream, to keep from getting run over; but we wouldn’t have to light it for up-stream boats unless we see we was in what they call a “crossing”; for the river was pretty high yet, very low banks being still a little under water; so up-bound boats didn’t always run the channel, but hunted easy water. This second night we run between seven and eight hours, with a current that was making over four mile an hour. We catched fish and talked, and we took a swim now and then to keep off sleepiness. It was kind of solemn, drifting down the big, still river, laying on our backs looking up at the stars, and we didn’t ever feel like talking loud, and it warn’t often that we laughed—only a little kind of a low chuckle. We had mighty good weather as a general thing, and nothing ever happened to us at all—that night, nor the next, nor the next. Every night we passed towns, some of them away up on black hillsides, nothing but just a shiny bed of lights; not a house could you see. The fifth night we passed St. Louis, and it was like the whole world lit up. In St. Petersburg they used to say there was twenty or thirty thousand people in St. Louis, but I never believed it till I see that wonderful spread of lights at two o’clock that still night. There warn’t a sound there; everybody was asleep. Every night now I used to slip ashore towards ten o’clock at some little village, and buy ten or fifteen cents’ worth of meal or bacon or other stuff to eat; and sometimes I lifted a chicken that warn’t roosting comfortable, and took him along. Pap always said, take a chicken when you get a chance, because if you don’t want him yourself you can easy find somebody that does, and a good deed ain’t ever forgot. I never see pap when he didn’t want the chicken himself, but that is what he used to say, anyway. Mornings before daylight I slipped into cornfields and borrowed a watermelon, or a mushmelon, or a punkin, or some new corn, or things of that kind. Pap always said it warn’t no harm to borrow things if you was meaning to pay them back some time; but the widow said it warn’t anything but a soft name for stealing, and no decent body would do it. Jim said he reckoned the widow was partly right and pap was partly right; so the best way would be for us to pick out two or three things from the list and say we wouldn’t borrow them any more—then he reckoned it wouldn’t be no harm to borrow the others. So we talked it over all one night, drifting along down the river, trying to make up our minds whether to drop the watermelons, or the cantelopes, or the mushmelons, or what. But towards daylight we got it all settled satisfactory, and concluded to drop crabapples and p’simmons. We warn’t feeling just right before that, but it was all comfortable now. I was glad the way it come out, too, because crabapples ain’t ever good, and the p’simmons wouldn’t be ripe for two or three months yet. We shot a water-fowl now and then that got up too early in the morning or didn’t go to bed early enough in the evening. Take it all round, we lived pretty high. The fifth night below St. Louis we had a big storm after midnight, with a power of thunder and lightning, and the rain poured down in a solid sheet. We stayed in the wigwam and let the raft take care of itself. When the lightning glared out we could see a big straight river ahead, and high, rocky bluffs on both sides. By and by says I, “Hel-lo, Jim, looky yonder!” It was a steamboat that had killed herself on a rock. We was drifting straight down for her. The lightning showed her very distinct. She was leaning over, with part of her upper deck above water, and you could see every little chimbly-guy clean and clear, and a chair by the big bell, with an old slouch hat hanging on the back of it, when the flashes come. Well, it being away in the night and stormy, and all so mysterious-like, I felt just the way any other boy would a felt when I see that wreck laying there so mournful and lonesome in the middle of the river. I wanted to get aboard of her and slink around a little, and see what there was there. So I says: “Le’s land on her, Jim.” But Jim was dead against it at first. He says: “I doan’ want to go fool’n ’long er no wrack. We’s doin’ blame’ well, en we better let blame’ well alone, as de good book says. Like as not dey’s a watchman on dat wrack.” “Watchman your grandmother,” I says; “there ain’t nothing to watch but the texas and the pilot-house; and do you reckon anybody’s going to resk his life for a texas and a pilot-house such a night as this, when it’s likely to break up and wash off down the river any minute?” Jim couldn’t say nothing to that, so he didn’t try. “And besides,” I says, “we might borrow something worth having out of the captain’s stateroom. Seegars, I bet you—and cost five cents apiece, solid cash. Steamboat captains is always rich, and get sixty dollars a month, and they don’t care a cent what a thing costs, you know, long as they want it. Stick a candle in your pocket; I can’t rest, Jim, till we give her a rummaging. Do you reckon Tom Sawyer would ever go by this thing? Not for pie, he wouldn’t. He’d call it an adventure—that’s what he’d call it; and he’d land on that wreck if it was his last act. And wouldn’t he throw style into it?—wouldn’t he spread himself, nor nothing? Why, you’d think it was Christopher C’lumbus discovering Kingdom-Come. I wish Tom Sawyer was here.” Jim he grumbled a little, but give in. He said we mustn’t talk any more than we could help, and then talk mighty low. The lightning showed us the wreck again just in time, and we fetched the stabboard derrick, and made fast there. The deck was high out here. We went sneaking down the slope of it to labboard, in the dark, towards the texas, feeling our way slow with our feet, and spreading our hands out to fend off the guys, for it was so dark we couldn’t see no sign of them. Pretty soon we struck the forward end of the skylight, and clumb on to it; and the next step fetched us in front of the captain’s door, which was open, and by Jimminy, away down through the texas-hall we see a light! and all in the same second we seem to hear low voices in yonder! Jim whispered and said he was feeling powerful sick, and told me to come along. I says, all right, and was going to start for the raft; but just then I heard a voice wail out and say: “Oh, please don’t, boys; I swear I won’t ever tell!” Another voice said, pretty loud: “It’s a lie, Jim Turner. You’ve acted this way before. You always want more’n your share of the truck, and you’ve always got it, too, because you’ve swore ’t if you didn’t you’d tell. But this time you’ve said it jest one time too many. You’re the meanest, treacherousest hound in this country.” By this time Jim was gone for the raft. I was just a-biling with curiosity; and I says to myself, Tom Sawyer wouldn’t back out now, and so I won’t either; I’m a-going to see what’s going on here. So I dropped on my hands and knees in the little passage, and crept aft in the dark till there warn’t but one stateroom betwixt me and the cross-hall of the texas. Then in there I see a man stretched on the floor and tied hand and foot, and two men standing over him, and one of them had a dim lantern in his hand, and the other one had a pistol. This one kept pointing the pistol at the man’s head on the floor, and saying: “I’d like to! And I orter, too—a mean skunk!” The man on the floor would shrivel up and say, “Oh, please don’t, Bill; I hain’t ever goin’ to tell.” And every time he said that the man with the lantern would laugh and say: “’Deed you ain’t! You never said no truer thing ’n that, you bet you.” And once he said: “Hear him beg! and yit if we hadn’t got the best of him and tied him he’d a killed us both. And what for? Jist for noth’n. Jist because we stood on our rights—that’s what for. But I lay you ain’t a-goin’ to threaten nobody any more, Jim Turner. Put up that pistol, Bill.” Bill says: “I don’t want to, Jake Packard. I’m for killin’ him—and didn’t he kill old Hatfield jist the same way—and don’t he deserve it?” “But I don’t want him killed, and I’ve got my reasons for it.” “Bless yo’ heart for them words, Jake Packard! I’ll never forgit you long’s I live!” says the man on the floor, sort of blubbering. Packard didn’t take no notice of that, but hung up his lantern on a nail and started towards where I was there in the dark, and motioned Bill to come. I crawfished as fast as I could about two yards, but the boat slanted so that I couldn’t make very good time; so to keep from getting run over and catched I crawled into a stateroom on the upper side. The man came a-pawing along in the dark, and when Packard got to my stateroom, he says: “Here—come in here.” And in he come, and Bill after him. But before they got in I was up in the upper berth, cornered, and sorry I come. Then they stood there, with their hands on the ledge of the berth, and talked. I couldn’t see them, but I could tell where they was by the whisky they’d been having. I was glad I didn’t drink whisky; but it wouldn’t made much difference anyway, because most of the time they couldn’t a treed me because I didn’t breathe. I was too scared. And, besides, a body couldn’t breathe and hear such talk. They talked low and earnest. Bill wanted to kill Turner. He says: “He’s said he’ll tell, and he will. If we was to give both our shares to him now it wouldn’t make no difference after the row and the way we’ve served him. Shore’s you’re born, he’ll turn State’s evidence; now you hear me. I’m for putting him out of his troubles.” “So’m I,” says Packard, very quiet. “Blame it, I’d sorter begun to think you wasn’t. Well, then, that’s all right. Le’s go and do it.” “Hold on a minute; I hain’t had my say yit. You listen to me. Shooting’s good, but there’s quieter ways if the thing’s got to be done. But what I say is this: it ain’t good sense to go court’n around after a halter if you can git at what you’re up to in some way that’s jist as good and at the same time don’t bring you into no resks. Ain’t that so?” “You bet it is. But how you goin’ to manage it this time?” “Well, my idea is this: we’ll rustle around and gather up whatever pickins we’ve overlooked in the staterooms, and shove for shore and hide the truck. Then we’ll wait. Now I say it ain’t a-goin’ to be more’n two hours befo’ this wrack breaks up and washes off down the river. See? He’ll be drownded, and won’t have nobody to blame for it but his own self. I reckon that’s a considerble sight better ’n killin’ of him. I’m unfavorable to killin’ a man as long as you can git aroun’ it; it ain’t good sense, it ain’t good morals. Ain’t I right?” “Yes, I reck’n you are. But s’pose she don’t break up and wash off?” “Well, we can wait the two hours anyway and see, can’t we?” “All right, then; come along.” So they started, and I lit out, all in a cold sweat, and scrambled forward. It was dark as pitch there; but I said, in a kind of a coarse whisper, “Jim!” and he answered up, right at my elbow, with a sort of a moan, and I says: “Quick, Jim, it ain’t no time for fooling around and moaning; there’s a gang of murderers in yonder, and if we don’t hunt up their boat and set her drifting down the river so these fellows can’t get away from the wreck there’s one of ’em going to be in a bad fix. But if we find their boat we can put all of ’em in a bad fix—for the sheriff ’ll get ’em. Quick—hurry! I’ll hunt the labboard side, you hunt the stabboard. You start at the raft, and—” “Oh, my lordy, lordy! raf’’? Dey ain’ no raf’ no mo’; she done broke loose en gone I—en here we is!” About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Urbana, Illinois: Project Gutenberg. Retrieved April 2022 from Twain, Mark,1993. Adventures of Huckleberry Finn. https://www.gutenberg.org/files/76/76-h/76-h.htm#c12 This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

Adventures of Huckleberry Finn: Chapter XII

Introduction In this blog, we will look at the evolution of software infrastructure; provisioning, delivery and maintenance. If you are interested in modern DevOps and SRE practices, this article is for you. is a common pattern where virtualized infrastructure and auxiliary services can be managed using configuration expressed in almost any language, usually hosted in a source code repository. Infrastructure as Code (IaC) Every once in a while software industry is shaped by significant events called . Paradigm Shift Here are a few such events that made Infrastructure as Code what it is today: Virtualization Containerisation and containers orchestration Public Cloud Infrastructure DevOps Culture Infrastructure provisioning: evolution Let’s examine how each wave of changes shaped the software landscape: #1 Virtualization In the early days of virtualization, developers would produce software in long waterfall development cycles, mostly based on requirements documentation. Ops Teams at the same time would rack and stack servers, provision infrastructure components, install all the things, configure etc. Typically both teams would work in a disconnected fashion, opening tickets and communicating via long email chains. Those were the darg ages. #2 Agile and beginning of DevOps Next came the agile revolution and with it the beginning of the DevOps culture. Now developers would send the application over to the Ops Team along with a multi-page configuration manual. More progressive teams will start collaborating on automation tools. In the early days of infrastructure automation tools like Chef or Puppet were very popular. Huge improvement, but often very siloed environment and fragmented responsibilities. #3 Public Cloud & container orchestration Along with increased usage of the public cloud and more robust automation, things started to fall into the right places. The tool of choice for most of the OPS Teams was terraform. Compared to the situation from a few years ago, this is huge progress. The amount of infrastructure created grows exponentially. For a long time, this picture is almost perfect… almost. So what is missing? Well, the experience for both Dev and Ops falls a bit short. Meticulously created infrastructure starts to drift, requires a lot of effort and maintenance overhead. Developers on the other hand must learn new languages and struggle to incorporate the Ops tooling into their workflows. Community rallies around and comes up with all kinds of creative solutions, drift detection, more automation, observability etc. All those tools and projects are great, but not standardised. How to improve the already good process? How to make one more leap to make something good, great? The answer came, like most good answers, from within the community itself. Remember how we talked about paradigm shifts? One of them was containerization and containers orchestration, this enabled standardization of to lesser extent packaging (container images) and runtime (Kubernetes pods) concerns. Now we have all the standards and tools at our fingertips, just one final touch needed to make it work seamlessly together. Here is how, in my opinion, is the missing link in the infrastructure as code evolution. Crossplane The power of Crossplane comes from using cloud native open standards and most popular tools to enable Developers (aka Application Teams) and Ops (aka Platform Teams) to work together, but without depending on each other. Before we move on to the next part of the blog, a little disclaimer. Choosing cows and penguins to represent developers and ops respectively, was based purely on the cuteness level of the animal. Crossplane Architecture What makes Crossplane so special? First, it builds on Kubernetes and capitalizes on the fact that the real power of Kubernetes is its powerful API model and control plane logic (control loops). It also moves away from Infrastructure as Code to Infrastructure as Data. The difference is that IaC means writing code to describe how the provisioning should happen, whereas IaD means writing pure data files (in the case of Kubernetes YAML) and submitting them to the control component (in the case of Kubernetes an operator) to encapsulate and execute the provisioning logic. For me, the best part about Crossplane is that it seamlessly enables collaboration between Application Teams and Platform Teams, by leveraging Plane as the convergence point where everyone meets. Kubernetes Control Components Let’s look how the Crossplane component model looks like. A word of warning, if you are new to Kubernetes this might be overwhelming, but there is value in making an effort to understand it. The below diagram shows the Crossplane component model and its basic interactions. Demo Scenario The demo scenario highlights Crossplane’s composite functionality. Using composites helps abstract away infrastructure complexity from developers by moving it into a Platform Team. The scenario flow: deploy RDS deploy EKS highlight the main steps of creating and using a composition Prerequisites To follow along, you will need a subscription to AWS and CLI configured on your local machine. Credentials for accessing cloud environments and deploying the infrastructure will be mapped from mounted volumes. Locally installed you will need: VS Code with remote containers devcontainer plugin WSL2 if using Windows Demo Setup All components from the are already pre-installed in the devcontainer in this project. Crossplane installation The components are: Kubernetes minikube Helm kubectl Crossplane CLI AWS CLI Crossplane should be installed in a namespace, if not please run crossplane-system .devcontainer/library-scripts/setup-crossplane.sh This setup is a little bit clunky, for example, performance is sub-optimal due to files being read from the container and the overall setup is not where I want it to be. This might change into a vagrant based setup if the containers reach the limit of abuse. Observability To visualize CRDs use ; a VMWare open-source cluster visualizer, running in a browser so no in-cluster installation is required. Octant If you like terminal tools more, got you covered. k9s AWS provider The setup will automatically generate AWS configuration based on the default profile mounted from your local $HOME/.aws folder. creds.conf file is added to .gitignore so you will not commit it to the repo accidentally! The next step is to configure Crossplane to access AWS and create resources, we will achieve this by creating a secret: kubectl create secret generic aws-creds -n crossplane-system --from-file=creds=./creds.conf and now, install AWS provider on the cluster kubectl apply -f https://raw.githubusercontent.com/crossplane/crossplane/release-1.5/docs/snippets/configure/aws/providerconfig.yaml From there onwards you should be able to follow along with the demos from . Crossplane's web page Deploy RDS Instance First let's deploy an RDS Instance, which is an AWS managed resource and comes with the AWS provider. See . Crossplane components diagram kubectl create -f rds-instance.yaml RDSInstance is just a Kubernetes resource like pod, service or replicaSet. You can check the deployment progress in Octant or command line: watch kubectl get RDSInstance Delete the instance with kubectl delete -f rds-instance.yaml Deploy EKS Cluster Deploying EKS cluster with automation is not a trivial task, there are a lot of components that need to be created along, like VPCs, subnets, IAM Roles, node pools, route tables, gateways... This is not the experience developers want, but this complexity must go somewhere, there is no magic "Remove complexity" button! As we've seen in the component diagram, the process starts with building an XRD (Composite Resource Definition) where we can specify: schema of the XR (Composite Resource) schema of the XRC (Composite Resource Claim) To help visualize how complex the configuration can be, here is a diagram representing the EKS Composition. This complexity is managed by Platform Team, folks that specialize in both Kubernetes and Cloud Providers. Now with this complexity hidden, developers are getting this: apiVersion: crossplanedemo.com/v1alpha1
kind: CompositeKubernetesCluster
metadata:
  name: devops-team
  labels:
    cluster-owner: piotrzan
spec:
  compositionRef:
    # Possible values cluster-google, cluster-azure, cluster-aws
    name: cluster-aws
  parameters:
    # Possible values small, medium, large
    nodeSize: small
    # version: "1.20"
    # minNodeCount: 2
  writeConnectionSecretToRef:
    namespace: devops-team
    name: cluster Deploying cluster is very easy, just kubectl create -f ./aws EKS Cluster deployment status: Retrieve kubeconfig details kubectl get secrets --namespace devops-team cluster \
     --output jsonpath="{.data.kubeconfig}" \
     | base64 --decode | tee eks-config.yaml

export KUBECONFIG=$PWD/eks-config.yaml From here you can use the cluster like your normal EKS. Remember to or source bash/zshrc to get your old config back. unset KUBECONFIG Cleanup Delete EKS and accompanying resources Exit VS Code which will stop the container. You can further clean unused containers and images by . kubectl delete -f ./aws docker system prune --all Conclusion Just in case anyone is wondering, this article is not sponsored by Upbound (the company behind Crossplane), I genuinely believe that this product is revolutionary. We have seen how Crossplane can help make infrastructure provisioning and management easier. Here are a few benefits I would like to highlight. Composable Infrastructure Self-Service Increased Automation Standardized collaboration Ubiquitous language (K8s API) What I like most about Crossplane is that it’s built with the DevOps culture in mind by promoting loosely coupled collaboration between Applications Teams and Platform Teams. The resource model, packaging, configuration are well thought out. There are also a few challenges to keep in mind: Complexity, it’s a price to pay for the flexibility it provides YAML proliferation, which is good or bad depending on where you stand on YAML ;) You need to know K8s well Complexity is addressed by moving it to specialized Platform Teams. For YAML I would love to see more push for integrating YAML generation like CDK8s or others. I see reliance on K8s as a benefit, but for those of us who are not yet comfortable with Kubernetes, this makes the learning curve a bit steeper. In summary, Crossplane is a great product, it appeared at the right time and solves decades all problems in a very innovative and future proof way. Go check it out!

Infrastructure As Code: The Next Big Shift is Here

Linear programming is one of the most common optimization techniques. It has a wide range of applications and is frequently used in operations research, industrial design, planning, and the list goes on. Alas, it is not as hyped as machine learning is (which is certainly a form of optimization itself), but is the go-to method for problems that can be formulated through decision variables that have linear relationships. This is a fast practical tutorial, I will perhaps cover the Simplex algorithm and the theory in a later post. Problem Statement Just to get an idea, we are going to solve a simple problem regarding production scheduling. Imagine that you work for a company that builds computers. A computer is a fairly complex product, and there are several factories that assemble them which the company pays a certain amount per unit. The cost of this computer model on the market is fixed at 500$, different factories assemble the computers at different speeds and costs. Factory produces 2000 per day at 450$ per unit, factory 1500 per day at 420$ per unit and 1000 per day at 400$ per unit. We have 1 month to assemble 80 000 units under the constraint that no factory is to produce more than double the units than any other factory. The question is, such that we obtained from selling the computers under those constraints? f0 f1 f2 what is the optimal production allocation between the factories maximize the profit In this tutorial we are going to be using Python and a linear programming optimization package , copy-paste install with pip: PuLP pip install pulp Now, in order to solve the computer production problem with linear programming, we need the following things: The set of decision variables The set of linear constraints on those variables A linear objective function to maximize or minimize So, open up your favorite editor and let's get started. Before defining the variables in PuLP, we need to create a problem object with the following code: from pulp import *problem = LpProblem("problemName", LpMaximize) We are going to add the constraints and objective function to this object. Notice that the problem constructor receives a problem name and , which means we want to maximize our objective function. In our case, this is the profit from selling a certain number of computers. Additionally, we also define the constants that we received from the problem statement: LpMaximize # factory cost per daycf0 = 450cf1 = 420cf2 = 400 # factory throughput per dayf0 = 2000f1 = 1500f2 = 1000 # production goalgoal = 80000 # time limitmax_num_days = 30 num_factories = 3 In the next section, we will define the decision variables. Decision Variables In PuLP, a decision variable is defined the following way: variable = LpVariable("variableName") Sometimes we need to provide bounds to the variable (the default is no bounds), in this case, we would write the following: var = LpVariable("boundedVariableName",lowerBound,upperBound) Yet another useful way to define variables in PuLP is using the dicts function. This can be very useful in cases where we need to define a large number of variables of the same type and bounds, would be a list of keys for the dictionary: variableNames varDict = LpVariable.dicts("varDict", variableNames, lowBound, upBound) So based on the previous definitions, the decision variables for the computer production problem are the days that we spend producing for each factory: # factoriesnum_factories = 3factory_days = LpVariable.dicts("factoryDays", list(range(num_factories)), 0, 30, cat="Continuous") Constraints Now that we defined our decision variables we can shift to defining the constraints for the problem. Note that the constraints have to be linear in a linear programming setting. The constraints that we care about are that the number of units assembled should be above or equal to the goal amount and the production constraint that no factory should produce more than double as the other factory: # goal constraintc1 = factory_days[0]*f1 + factory_days[1]*f2 + factory_days[2] * f3 >= goal # production constraintsc2 = factory_days[0]*f0 <= 2*factory_days[1]*f1c3 = factory_days[0]*f0 <= 2*factory_days[2]*f2c4 = factory_days[1]*f1 <= 2*factory_days[2]*f2c5 = factory_days[1]*f1 <= 2*factory_days[0]*f0c6 = factory_days[2]*f2 <= 2*factory_days[1]*f1c7 = factory_days[2]*f2 <= 2*factory_days[0]*f0 # adding the constraints to the problemproblem += c1problem += c2problem += c3problem += c4problem += c5problem += c6problem += c7 The objective function for the computer assembly problem is basically minimizing the cost of assembling all of those computers. This can be written simply as maximizing the negative cost: # objective functionproblem += -factory_days[0]*cf0*f0 - factory_days[1]*cf1*f1 - factory_days[2]*cf2*f2 Let's take a look at the problem definition, this can be simply achieved by the call: print(problem) This results in the following output which I think is self-explanatory, it lists the objective function, the constraints and the various decision variables in the problem: computerAssembly:MAXIMIZE-900000*factoryDays_0 + -630000*factoryDays_1 + -400000*factoryDays_2 + 0SUBJECT TO_C1: 1500 factoryDays_0 + 1000 factoryDays_1 + 1000 factoryDays_2 >= 80000 _C2: 2000 factoryDays_0 - 3000 factoryDays_1 <= 0 _C3: 2000 factoryDays_0 - 2000 factoryDays_2 <= 0 _C4: 1500 factoryDays_1 - 2000 factoryDays_2 <= 0 _C5: - 4000 factoryDays_0 + 1500 factoryDays_1 <= 0 _C6: - 3000 factoryDays_1 + 1000 factoryDays_2 <= 0 _C7: - 4000 factoryDays_0 + 1000 factoryDays_2 <= 0 VARIABLESfactoryDays_0 <= 30 ContinuousfactoryDays_1 <= 30 ContinuousfactoryDays_2 <= 30 Continuous Solving After we defined everything necessary in our linear programming problem, we can call the solve method which outputs 1 if the problem is solved and -1 if it was infeasible, it is a simple one-liner: # solvingproblem.solve() The solutions to the problem can be obtained by accessing the varValue attribute of each variable: for i in range(3):print(f"Factory {i}: {factory_days[i].varValue}") This results in the following output: Factory 0: 23.076923Factory 1: 15.384615Factory 2: 30.0 In linear programming, we assume that the relationships between the variables are linear and that the variables themselves are continuous. As a follow up on this tutorial, I will be covering Mixed Integer Programming, where the variables can be integers, which will prove a very useful thing since it can be used to simulate boolean logic.

Linear Programming in Python: A Straight Forward Tutorial

https://www.youtube.com/watch?v=XkiSUYxFaoY&embedable=true&transcript=true Here’s my new interview with the . Their new podcast (I’m the third guest!) is . I am also testing out HackerNoon’s new Youtube embed + transcript function.  Featured image credit is for prompt of ‘ I haven’t watched it yet, but I do recall having an interesting discussion about how a founder’s personality will make it’s way into the company’s operations one way or the other. SaaS Group SaaS Unbound HackerNoon AI mountain man takes zoom call in front of green pixelated clock. three percent of those watching go on to start uber successful saas companies.’

UPBOUND

upbound.io

-- employees

Since n.d.

COMPANY RANKING

UPBOUND

EVERGREEN INDEX #11162

Representing this company? Click here to claim and customize this page!

Upbound WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

UPBOUND

upbound.io

-- employees

Since n.d.

COMPANY RANKING

UPBOUND

EVERGREEN INDEX #11162

RELATED COMPANIESRANK

STORIES ABOUT UPBOUND

Representing this company? Click here to claim and customize this page!

Upbound WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!