Stories and content in Weird Darkness can be disturbing for some listeners and is intended for mature audiences only. Parental discretion is strongly advised. Welcome, Weirdos. I'm Darren Marlar and this is Weird Darkness. Here you'll find stories of the paranormal, supernatural, legends, lore, the strange and bizarre, crime, conspiracy, mysterious, macabre, unsolved and unexplained. Coming up in this episode, we'll talk about the year we had two thanksgivings in the United States. A Weirdo family member shares a freaky true thanksgiving story with an explosive ending. Two brothers solve an almost 200-year-old murder mystery thanks to a Thanksgiving ghost story that was told to them by their grandfather. And I'll share a horrific thanksgiving tale from the latter part of the 19th century. If you're new here, welcome to the show. While you're listening, be sure to check out WeirdDarkness.com for merchandise, my newsletter, to enter contests, to connect with me on social media. Plus, you can visit the Hope in the Darkness page if you're struggling with depression or dark thoughts. You can find all of that and more at WeirdDarkness.com.  The year was 1939 and President Franklin D. Roosevelt was busy trying to both drag the country out of the Great Depression and to prepare the nation for the war clouds gathering on the horizon. When Thanksgiving 1939 rolled around, his mind was clearly focused on the Great Depression. As of 1939, thanksgiving wasn't an official holiday. To be sure, Abraham Lincoln had decreed it would be the last Thursday of November when he declared it a holiday back in 1863, but that wasn't set in stone, so FDR had an idea. I, Franklin D. Roosevelt, President of the United States of America, do hereby designate Thursday the 23rd of November 1939 as a day of general thanksgiving. How appropriate that Roosevelt's proclamation was issued on October 31st, Halloween, a day known for tricks or treats. More the former, though, as upon hearing this proclamation, the average citizen felt like it was a trick, both irritating and confusing them at the same time. FDR just made everybody's yearly calendar a moot point for November 1939. At the time, it was up to the President to issue a Thanksgiving proclamation to announce on what day the holiday would fall. However, Thanksgiving had always been the last Thursday in November because that was the day President Abraham Lincoln observed the holiday in 1863. FDR's first Thanksgiving while in office occurred in 1933, a year that featured the rare Five Thursdays. Then, as now, the Christmas shopping season didn't officially kick off until after Americans had dug into their turkey. But as there would only be 24 shopping days left after Thanksgiving fell on November 30th, one business leaders urged Roosevelt to declare the fourth, not the last, Thursday as the National Day of Thanksgiving. FDR was inundated by requests from businesses to make the change, including the National Retail Dry Goods Association. Everyone who had something to sell wanted to extend the Christmas shopping season by one week. But Roosevelt rejected the idea at first on the grounds that such a change might cause confusion. That was 1933, but the Great Depression wasn't going away, and in 1939 the same issue rolled around with Thanksgiving again falling on November 30th, meaning another shortened Christmas shopping season, raising the same worries from merchants and the business community, who to be fair had gone through a lot during the Depression years. FDR's eventual giving in to businesses in 1939 likely proved him more right than he probably would have liked about people getting confused. Smaller businesses complained that they'd lose business to the larger stores. Other companies that depended on Thanksgiving as the last Thursday of November, they lost money. Schools were disrupted by Roosevelt's decision. Most schools had already scheduled vacations by the time they learned of Thanksgiving's new date and had to decide whether or not to reschedule everything. Football coaches scrambled to reschedule games set for November 30th. Families didn't know when to have their holiday meals. Some families had no idea about the change because their calendars still indicated the traditional date, and of course people weren't sure when to start their Christmas shopping. Some folks found mirth in the situation. Mr. President, I see by the paper this morning where you want to change Thanksgiving Day to November 23rd, of which I heartily approve. Thanks," wrote one Shelby O'Bennett of Shinston, West Virginia, whose letter has been saved by the Franklin D. Roosevelt Presidential Library and Museum. She continued, Now, there are some things that I would like done and would appreciate your approval. 1. Has Sunday changed to Wednesday? 2. Have Mondays to be Christmas? 3. Have it strictly against the will of God to work on Tuesday? Thousands, more letters, most not so lighthearted, poured into the White House. Opposition grew. Americans were angry that Roosevelt tried to alter such a long-standing tradition and American values just to help businesses make more money. While governors usually follow the president's lead with state proclamations for the same day, in 1939 some states took matters into their own hands and defied the presidential proclamation. Some governors declared November 30th as Thanksgiving, and so, depending upon where somebody lived, Thanksgiving was celebrated on November 23rd, and November 30th. This was worse than changing the date in the first place because many families did not have the same day off as family members in other states and were therefore unable to celebrate the holiday together. 23 states observed Thanksgiving Day on November 23rd. 23 states celebrated on November 30th, and Texas and Colorado declared both Thursdays to be holidays. Now, that's an idea I can get behind. Double the turkey and stuffing, count me in. The Jackson County Journal pretty much didn't care, and in a brief editorial said people should just pick the day that suited them best, the 23rd or the 30th. The journal wrote in a piece titled Two Thanksgivings quote, we will have two thanksgivings in North Carolina this year. President Roosevelt has claimed November 23 as a day of national Thanksgiving. In consequence, the Federal Courts, the Post Offices and the National Banks will observe November 23 as a holiday. State banks, schools, state offices and county and city officials will observe November 30. Take your choice. Have your turkey either day you wish, but above all, let each of us be thankful every day in the year that we live in the United States of America that our forefathers bought for us with their blood and suffering the inestimable privileges that we enjoy, and that a divine providence has showered innumerable blessings upon our land, and upon each of us individually." In other words, celebrate the spirit of the holiday and although the federal government would observe it one day and state and local governments another, no harm, no foul. But most folks, to put it mildly, went ballistic. The main opponents to moving Thanksgiving were traditionalists, but one industry sector in particular almost collectively lost their minds. Calendar manufacturers understandable. John Taylor of the Budget Press in Ohio wrote to FDR and described the apocalyptic scenario the President had gifted his business with, writing that most calendars are sold in January and that his firm had printed $2 million that month. If very many customers demand 1940 calendars to correspond with your proclamation, Taylor wrote, hundreds of thousands of dollars will be lost by the calendar companies and in many instances it will lead to bankruptcy. FDR declared the next to last Thursday in November as Thanksgiving two more times, but even after the outbreak of World War II in December 1941, Congress saw the issue as important enough to act. On December 26, 1941, it finally passed a law nailing down the fourth Thursday of November as the official Thanksgiving and there it remains. This story was sent into us from Weirdo family member Rachel Gates. I had the creepiest Thanksgiving happen when I was a young teenager in the 90s. You first have to know some facts for this story to make sense, so let me explain. Fact one, my mom had a balloon business at the time. That means there were strings of fishing line hanging through our living room. Fact two, I was in love with Keanu Reeves after Speed came out. My prize possession was a giant poster given to me a few years earlier. It was huge and would fall down all the time. The edges were covered in tape from being hung up over and over again. Fact three, my mom had been a single parent for years until she remarried. She worked a lot, which means we kids were generally unruly and messy to put it kindly. We were slobs. It took me joining the military to gain much better cleaning routines, so our house was generally chaotic. Fact four, our house was haunted. We think we know by whom, but I will share that next. The house we lived in was a cute Victorian in Belvedere, Illinois. We rented it from the son of someone mom used to do home care for. She was a sweet old lady who was very clean. The house was all decked out in 70s shag carpet and heavy gold blackout drapes. She loved me and I loved visiting her, so when she died and we found ourselves needing a place to move to, her son was more than happy to rent to us. But shortly after moving in, things started happening. All the cabinets opening by themselves, things flying off shelves, orbs flying through rooms like actual balls of light flashing or floating around, not dust on a camera lens. Electronics turning on and off. TV channels changing by themselves. Voices you can't make out speaking. Whistling in your ear while on the toilet. Strange lights in the heating vents. You name it. Maybe some can be explained, but put them all together and it doesn't add up. Even if we had some kind of environmental issues, you'd still have to explain shared identical hallucinations. I've tried to explain it away. This is how I can be an atheist who believes in ghosts. I think now this sweet old lady was trying to scare us out of her clean, beautiful home, which now looked like a bomb had gone off inside. This all culminated to an epic Thanksgiving event in 1995. We actually cleaned every year before the feast, so the house was put together. We were starving as the smells of all the best homemade dishes wafted through the house. My dad, step-dad but I always called him dad, invites his old friend over from the reservation for dinner. So he got the guest of honor seat at the head of the table, which happened to be the only chair facing the kitchen with his back to the living room. Dinner was almost ready when I realized my speed poster had fallen down. I didn't have time to hang it up and didn't want it to wrinkle, so being me, I decided to hang it up in the living room on the fishing line with clothes line clips. That means all through dinner I could look over at Keano's dreamy face. This is important later. Finally, dinner was served, piping hot and smelling magical. One thing about my family is we have extra padding because we are great in the kitchen. Even my mom, who is a health nut, is just amazing at cooking. We all sit down around the dining room table, pray, I would say Catholic at the time, and dig in. Slowly we started hearing this flapping noise. Looking around, we noticed my poster bouncing around. It was an old house, so we thought it might be a draft. It didn't seem windy out, but we were inside, so it must be. We kept eating and laughed it off. But it kept going up and down, up and down. The flapping became bouncing, bouncing became whipping, until the sound of paper wrinkling as I now wonder how the poster even stayed put, let alone how the fishing line wasn't ripped from the wall. Now we aren't eating. We're staring, slack-jawed. No one made a sound. It kept going and going for minutes. Then, seemingly out of nowhere, there was a huge explosion. It shook the living room. Mom's instinct was to grab the kids in glasses like you do when you hit on the breaks too hard in the car. The food shook. It was like an earthquake. My ears were assaulted from the noise. Our heads snapped around to the kitchen. What we saw was crazy. There was a huge box of foil balloons in the doorway. It took two men to move that box under the desk in the dining room. You don't think about it when you buy foil balloons, but deflated and stacked close together a big box is basically a brick of metal. It was at least four or five feet away, right in the kitchen doorway. There was only one witness as to what had happened. My dad's friend, having an awkward position, was the only one to see what was going on, as we were mesmerized by the flying poster. He turned around to see movement catching his eye. Right before him, he watched as the impossibly heavy box lifted off the ground of its own accord. He said it floated out from under the desk and flew up and up about six or seven feet off the ground. Then, as we were all distracted, the box just fell. Gravity suddenly turned back on, and the resulting explosion was the equivalent of an acne anvil dropping straight into our dining room minus the cloud of dust and wily coyote. Holy cow. That actually happened. And we lived in that house for years. People who live there now don't even believe in ghosts, and nothing happens to them. I don't know them, but my cousin does, and she was astounded when I told her what used to go on in there. But then the old lady must approve of them, as they updated and improved the whole house. Moral of the story, clean your house, or ghosts will ruin your holidays. And speaking of, I'm going to go clean right now. My house is predictably a mess, but not for lack of trying. I promise. A grandpa's haunting Thanksgiving ghost story appeared to help two brothers uncover a nearly 200-year-old murder mystery. Bill and Frank Watson were told a chilling tale about 57 Irish immigrants who died at a railroad site in Pennsylvania during the cholera epidemic in 1832. The area is now known as Duffy's Cut, as the rail worker's boss was named Philip Duffy. It's a stretch of tracks located around 30 miles from Philadelphia. The brothers were told the chilling tale by their grandpa, a railroad worker, every Thanksgiving. They believed the rail workers died violently, not from cholera. Frank told CNN in 2010, this is a murder mystery from 178 years ago and it's finally coming to the light of day. According to local legend, a man walking home from a tavern claimed to see mysterious green figures dancing in the mist in September 1909. The documents quote the unnamed man as saying, I saw with my own eyes the ghosts of the Irishmen who died with cholera a month ago, dancing around the big trench where they were buried. It's true, Mr., it was awful. Frank inherited the railroad papers from his grandpa and said one of the documents said X marks the spot. They suspected that the files contained clues to the location of a mass grave. Bill and Frank delved deeper into the case. They started digging in 2002 and years later found forks and tobacco pipe shards. The brothers didn't believe struggling laborers would discard valuable items. Researchers in March 2009 found a bone raising suspicions that cholera may not have killed the rail workers. Teams also uncovered a skull that had been pierced by a bullet and cleaved by a hatchet. Bill, a historian said, we have no idea what percentage of these guys were murdered but if we have 57 it's the worst mass murder in Pennsylvania history. He said the average age of the workers was around 22 years old. Forensic anthropologist Janet Mong said the case provided vital clues about the lives of Irish immigrants. She said it was a cruel and rugged existence that characterizes the immigrant experience and it speaks very broadly of the xenophobia that existed at the time. Mong discovered bones from at least seven skeletons including four adults. She said one skull has a little divot on what would have been the side bone of the skull. That little divot is something that did not happen when they excavated it out of the ground. The anthropologist speculated that one of the laborers must have been clunked on their head before they died. Researchers believe more bodies are underneath the surface. Bill Watson said the coffins had been shut with more than 100 nails per coffin. The remains of five men and one woman from those who died at Duffy's Cut were laid to rest at a ceremony in Pennsylvania in 2012. The body of teenager John Ruddy who was from County Donegal was repatriated to Ireland and a burial took place in County Tyrone for Catherine Burns in October 2015. Forensics believe that injuries to her skull indicated that she had been murdered. Duffy's Cut later became part of the Pennsylvania Railroad's main line. Up next on Weird Darkness, I'll share a horrific Thanksgiving tale from the latter part of the 19th century and I'm honestly not sure if it's true or false. The song White Christmas used to be one of my favorite holiday tunes until the year of the ice storm. One December Robin and I heard a loud crash outside and not only did the ice cause a large tree to fall onto our house, but it ripped out the power lines. We were suddenly in sub-freezing temperatures with jackfrost nipping at our noses thanks to zero heat or electricity. Talk about baby, it's cold outside. If this happened today, I'd be hooking up my Patriot Power Generator 2000X. This solar-powered monster can power your lights, TV, medical equipment, like my CPAP machine, even keep your refrigerator running and possibly root all snows, although I can't vouch for that last one. Plus, it's expandable and comes with a free solar panel so you can begin using it immediately. And because it's solar and portable, you can use it indoors without having to worry about deadly carbon monoxide fumes and you don't have to spend money on gasoline to power it because solar power is free. That's something even Ebenezer Scrooge could smile at. 4Patriots.com has a ton of great gift ideas and they're always offering special deals, and we've set up a special page for weirdos just for that purpose. Visit 4Patriots.com slash weird. That's the number 4 Patriots.com slash weird. Just like the holidays, though, these deals never last long, so you'll want to check this daily to see what the latest special deals are. That's 4Patriots.com slash weird. As Americans gather for the Thanksgiving holiday, it is perhaps time to turn the clock back to one family feast that did not raise quite as much cheer. It tells of the terrible incidents that took place in a house in Oakville, Georgia, USA, in the latter part of the 19th century. This spot has earned a high place amongst haunted localities and in its day was comparable with the famous house in Berkeley Square. Situated in the midst of picturesque but lonely country, this house, the property of a farmer named Walsingham, had a worldwide reputation among psychical investigators. For some time, the house had been left deserted by its owner, and it would seem that during the temporary absence of its material master it passed into the hands of beings or forces, call them what you will, who wished to remain in undisputed possession. When Walsingham and his family decided to return and take up their abode in the house, they were struck on the very first day by the peculiar feeling of the place. They could not decide in any way what this feeling was, but on analysis linked it to claustrophobia, an overpowering dread of being alone within any four walls. Their dog, Don Caesar, absolutely refused to enter the house. On being dragged in, he immediately broke out into furious barking. His back bristled with rage, and he showed every sign of terror. This occurred several times during the day, and the same evening, being attracted to the spot by his wines and hulls, Walsingham saw his dog attacking some invisible enemy. Don Caesar, the dog, at last sprang in the air, as if at a man's throat, but fell back as if he had received a heavy blow. When picked up, the dog's neck had been found to be broken. The Walsingham's cat, on the other hand, manifested every sign of delight at being in a house. It strolled from room to room, purring loudly, and was seen on several occasions twisting its head from side to side, and arching its back as if someone were stroking it. To say that the Walsinghams were amazed at these things would be to describe their feelings mildly. They were very much upset, but had not as yet any suspicion on the score of supernatural causes. But that evening, just towards the desk, the house was suddenly filled with shouts, groans, and hideous laughter heard by all the occupants and putting them into a veritable panic. Miss Amelia Walsingham, while sitting in front of her mirror, saw a man's hand upon her shoulder, yet there was no reflection of it in the glass, nor was there any arm or body apparent. Walsingham himself saw footprints forming in the dust of a garden path before him as he walked, yet no mortal could be seen. But though these things were uncanny and terrifying, and were sufficient to make the family realize that some force out of the usual was at work, they paled into insignificance before the later incidents which took place during the evening meal. The family was seated at supper with one or two guests when their conversation was suddenly interrupted by a loud and horrible groan uttered apparently in the room above. Little notice was taken of it until one of the guests pointed out a stain of what looked like blood on the tablecloth, and it was then seen that some liquid was slowly dripping from the ceiling overhead. This liquid was so much like freshly shed blood as to horrify those who witnessed its slow dripping. It would be hard to imagine a more gruesome occurrence at any time, but the peculiar form of this horror and the theatrical way in which it was carried out would put it down as the invention of some most evil-minded but decidedly clever person. It flashed into the minds of all sitting at the table that some terrible deed had been committed in the room above, some frightful murder. For a few seconds, all sat silent with white faces, looking out of the corner of their eyes at each other in terror. Then, Walsingham shook off this paralysis of fear and ran out of the room, followed by his son. They went quickly upstairs to the room over the dining room and flung open the door, dreading what fearful sight their eyes should meet. But it was empty. They tore up the carpet and there found the boards to be soaked with the same red gruesome liquid as was dripping into the room beneath. But there was no explanation, nor was any afterwards discovered. The liquid was later examined under a microscope by a medical man and pronounced to be human blood. This incident was too much for the Walsinghams and they left the house and removed to another. Walsingham House then fell into entire disuse, and stories of the occurrences being put abroad, the place was shunned by day as well as by night. This neglect obviously did not tend to make the spot look more cheerful and it is stated that, in addition to the gloom that generally settles on the most ordinary of empty houses, there was an undoubted feeling of depression in the air around the place. Quite normal people said it felt to them as if the atmosphere of the locality weighed more than anywhere else. The house had not been approached for several months when a young man named Horace Gunn decided to make it the subject of a wager, betting a friend a fair sum of money that he would stay alone in the house for one night and have no aid within call. This enthusiastic young man carried out his intention and went to the house one evening before it was dark. His story is best told in his own words. Quote, I had been in the house about an hour and nothing had happened. It was just beginning to get dark and I thought that I would set about lighting of fire. Though I did not consider myself an expert in this art, I was very much surprised being absolutely unable to do so. My matches went out one after the other as if blown out by a strong draft. Once, when I had succeeded in lighting a piece of paper, it only smoldered for a few seconds and then went out. This was bad enough as I had to give up the idea of a cheerful blaze to keep me company, but to my disgust I found that my lamp would not light either. It was as if it were filled with water instead of with oil. It was now quite dark and whilst I was looking about for some means of getting a light, there came a terrible yell of pain from underneath the house and this was the signal for an outbreak of the most hideous and devilish noises. There were shouts, screams, groans, laughter, thumping, and the continual running up and downstairs as of several heavily shot people. My hair bristled. I stood by the window, practically paralyzed with fear, and had I then been able to control my limbs, I would have fled from the house. I would have lost my wager and a hundred like it rather than stay in that haunt of fiends. Then suddenly, the noises stopped. Complete silence fell on the place. But far from reassuring me, this made matters worse, for now I dreaded the silence even more than I had the ghostly noises. All the time I listened, listened for something. Now and then I thought I heard soft footsteps drawing near me, but it was nothing. This waiting and dreading was far worse than the pandemonium of terror. I did not have long to wait for the next move, for in the darkness, there suddenly appeared a small spot of grayish light on the wall opposite me. It grew larger and larger, altering in shape, until it assumed the outline of a human head, at the same time losing its flatness. Soon it was a real head, floating in the air. Its hair was long and gray and matted together and it had a deep and jagged cut in one temple. The whole face indicated suffering and misery. The eyes were wide open and gleamed with unearthly fire, while they seemed to direct their gaze upon me. The head moved about the room, but always the eyes were turned in my direction. Then it vanished. But their broke out in the room allowed an awe-inspiring wail as of several souls in anguish. I thought then that I could see indistinct shapes flitting about, and mustering up all my courage, I attempted to pass them and gain the door. But just as I reached it, I felt my ankle seized in a firm grasp. I was thrown down and felt fingers grasping at my throat. At this point Mr. Gunn's story ceases. He was found by his friends the next morning, unconscious on the floor by the door, and bearing on his throat the marks of long, thin fingers with cool, curved nails. After this experience no one was found to have anything more to do with the house, though a few people interested in such matters attempted to find out some reason for this terrible haunting. Though several avenues of investigation were explored, nothing very conclusive was discovered. The house had by this time acquired such an evil reputation that no one would occupy it, and it was ultimately demolished. Many human bones were found under it and in its grounds. How they came there it was never known, but it was supposed that they had lain there for many years and were the bones of people who might have been murdered when the house was a roadside inn of very bad repute. And herein perhaps lies an explanation for the hauntings of the house. A few days before returning to his house, Mr. Wallingham, having discovered in the grounds some old, dried bones and not able to decide whether they were human or not, settled the matter as he thought by ordering them to be thrown into a lime kiln. Is it possible that the spirits of the men whose bones were thus so indecently treated summoned to their aid certain dark forces in order to make the place uninhabitable by mortals in revenge for the insult offered to their remains? Before I end this Thanksgiving episode, I want to share a moment to express my thanks, gratitude and appreciation to you, my weirdo family. I am so thankful to God for you. You have no idea. I was praying today and giving thanks to God for the blessings that we have. I daily thank him anyway for saving me, for bringing my bride into my life, for giving me the skills and talent to do what I do, as I don't think I'm qualified to do anything else. I thank God for the roof over my head, for food on the table, for allowing us to give back to others in a variety of ways. Those who were in need. And in praying these things today, I realized that you, my weirdo family, have helped make a lot of that possible. I didn't create this podcast for any reason other than to entertain people, but you've invited your friends and family to listen. You've shared links to the episodes in your social media, emails and texts. You've stuck with me all these years and what I began as simply a creative outlet for myself has become a full-time career that has kept food on the table, the house payments on time, and you've shown your generosity in so many ways through being patrons or buying merchandise and donating to the fundraisers. I am so grateful to God for you because you have given this man a true calling and purpose for being on this planet to entertain, enlighten and bring hope to those who listen. William Shakespeare said it well, I can no other answer make, but thanks and thanks and ever thanks. Darren is D-A-R-R-E-N. WeirdDarkness.com is also where you can find all of my social media, listen to audiobooks I've narrated, shop the Weird Darkness store, sign up for monthly contests, find other podcasts that I host, and find the Hope in the Darkness page if you or someone you know is struggling with depression or dark thoughts. Also on the website, if you have a true paranormal or creepy tale to tell, you can click on Tell Your Story. You can find all of that and more at WeirdDarkness.com. All stories in Weird Darkness aren't purported to be true unless stated otherwise, and you can find source links or links to the authors in the show notes. The year with two thanksgivings was written by Dave Tabler at AppalachianHistory.net and Jim Buchanan for the Silva Herald. Thanksgiving Explosion is from Weirdo family member Rachel Gates. Grandpa's Thanksgiving Go story is by Chris Bradford for The Sun, and Feast of Terror was posted at Freaky Folk Tales. Weird Darkness is a production and trademark of Marlar House Productions. Copyright Weird Darkness 2022. And now that we're coming out of the dark, I'll leave you with a little light. Psalm 100 verse 4. Enter his gates with thanksgiving and his courts with praise, give thanks to him and praise his name. In a final thought, be thankful for what you have. You'll end up having more. If you concentrate on what you don't have, you will never ever have enough. I'm Darren Marlar. Thanks for joining me in the Weird Darkness.


Yeah, so our infrastructure's just not set up for that. Well, you can't do 5-9's availability on a 3-9's budget. Look, this is coming from the top. Can't just sit here and make excuses. Not much time. What's going on? Banes on the loose, and our crime-critical systems keep going down. This is what happens when you put a kid named after a bird in charge of I.T. Holy sap kinda, Batman. When your systems go down, you lose business. When mine go down, people die. Right. So what's the problem? Hardware failure. Some of these mainframes haven't been upgraded since the Adam West days. Good times. We need to hurry on it. Batcave defenses armed. Tracking systems online. Batman, I expected more from you. Your defenses are weak. My defenses were weak. So you should be good to go, Batman. You're fully clustered. Mainframes and x86 systems all upgraded to SUSE Linux. High availability extensions are working. No more downtime. Thank you, SUSE Master Builder. We can never repay you. Oh no, it was no trouble. No, I made some horrible investments last year. We can never repay you. Oh, OK. Eric. Eric. Bots? Guys, we've totally got this. Drive on there, that is a bootable drive that will image whatever you put on it, boot it up off of, with the appliance that Cameron is doing. It does have a little prompt. It says yes or no, do you really want to do this? So there's one level of protection from brain deadness. Just be careful, exercise caution. Yes, be careful, please. You can only use your powers if you're good. So does everybody have one yet? OK, everybody's got it. Good, good. Oh, I didn't even notice they were on the seat. So yeah, this will be fun. The little thumb drive with the cloud on it. So you can go and take that back to your room tonight or this afternoon. And deploy a cloud and start playing around with it. This will allow you to play around with it really, really quickly. So what are some of the reasons why you guys came today? So the comment there was there's too much theory going on. You wanted to see some actual practical implementation. Too much theory, OK. Anybody else want to make a comment? All the rest of you guys are open. Usually the comments are, you need a PhD or, you know. Yeah, you want to see how it's supposed to work. OK. All right. Has anybody here actually tried to do and failed at the, just doing the, I'm going to grab everything from GitHub and check it out and do it all. I'm raising my hand legitimately here. I failed at it, too. OK, that's most of the room, OK. All right, well, that's fine. I'm going to show you right from the very beginning on how to deploy your cloud with just a little bit of interactive slide deck here as well. And so we'll kind of go back and forth and we'll deploy a full cloud today, all right. Now, there are some things I'm going to show you that you can actually deploy a cloud much quicker using some nice tools that we've implemented with our product to be able to batch deploy your entire cloud in minutes, OK. So starting from this little thumb drive, you can plug it in, use it for VMware. You can run your cloud on top of VMware. You can run it on VMware Workstation if you really want to test around and play around with it. You can install it on your own hardware, just plug it in and boot from it, play around with it there in your own lab. We also have some different formats available. We have a VMX format. We have some KVM formats. So if you really want those other formats, we'll later on give you a location where you can grab those formats, OK. So from this thumb drive, installing the physical machines, virtual machine, and create your cloud platform. From a single image, we then have our admin node. And that's essentially what we're going to be creating here is our admin node. That admin node has all of the tools needed to deploy your entire cloud, OK. So let's take a look at that admin node. I'm going to switch gears away from this deck and actually just go to VMware. Can everybody see that? Hopefully that's not too small for everybody in the back of the room. Let me show you what I have here. It's eight gigabytes of memory, two processors. It's 20 gigabytes of hard disk.  I only have a single network adapter. Ideally, in the real world, you're going to want more. You could do this in VMware. I'm going to make it really simple today and just do a single virtual network adapter. But ideally, in the real world, you're going to want at least probably five, six network interfaces. And your hardware is going to come with that anyways. And then I have an actual ISO image of the thumb drive that I'm booting up in VMware. I could plug this guy in and point it to the physical if I wanted to as well. And it will work just the same. So let's go ahead and start this up. Wasn't fast enough. I'm going to boot from the CD-ROM drive, boot it off the ISO. This is what you're going to see when you boot from the thumb drive. And I'm going to select Install. And he will come up with loading the kernel.  Yes, question. Yeah, the only thing that's customized in there is I'm disabling the DHCP on that virtual network interface. It's actually a knadded network. So the question is, why do I have it as a custom network interface? So it's custom so I can, for one, disable the DHCP. And it is a knadded network. And the reason for that is that it's going to have a Pixie Boot server on there, and you don't want to expose that out to the outside world. Yeah, and on the host side of the machine, I could set up VLANs as well so I can get access to the public interface of the cloud and various other things like that. So kind of slow, this boot up part. Any other questions to this point? There we go. Destroy SDA. So this is what you get if you plug this into your machine and boot it up right now. So we are actually going to do that. And he's now loading that image onto the drive. That's what he's doing right here. Yeah, that's what we're doing right now. This is VMware Workstation that we're doing this in. Yeah, no problem. Any other questions while this is loading? Any good jokes? This is the painful part, really. Yeah, if you boot it off that machine and click yes on the destroy data, yes, your laptop will be gone. Yeah, you can put it in there while you're booted up and go and look inside of it and pull stuff off or whatever if you want to, but don't boot off of it unless you are feeling dangerous. Now we're going to get to a point where it's going to ask us a few questions just as part of the setup of the appliance itself. Actually, I would point out, Cameron, that with the file system on there, you can choose any size disk you want and it'll actually detect what the size of your system is and expand out to fill whatever that is. So you don't have to worry about choosing a storage to match up with the storage on the image. Yeah, you've probably missed the message going by the scrolling on the screen there, but it was actually extending the iNode table for EXT. So we'll go ahead and hit Next on this. You can choose your language settings and keyboard layout and then you can put in the password that you'd like to use for the appliance and then, of course, setting your host name and domain for this infrastructure and then setting up the network. Now this is really simple. We actually have pre-populated the network with some defaults that we like. These are actually defaults that we use in our documentation. So you can go through and you can actually change these. So if you don't like the IP addresses that are in here, feel free to modify that, how you like. I'm gonna leave it as is. And if you want to get an explanation of what those networks are and what they mean, then stick around for the next session. There's a couple of things I wanna change on the host name and DNS. Since this is under VMware, it routes through a .2 and not a .1 from the virtual machine side. So I do need to change that and then also change the default gateway to a .2. This is only inside of VMware for this case. And then you hit Next and it is writing all that configuration out to the disk. And now we can set up some time and NTP settings. I'm from Boise, so we'll set it for Boise. And then we'll hit Next. It'll give us some options to set up and configure NTP. It takes a moment to write this piece to disk. And then we'll go ahead and add an NTP server. We'll then select a public, that is okay. Write that config to disk. Now, most people skip by this screen, but it has some very important information on here on what to do next. We do have some documentation for this appliance. So if you do skip by this, you can refer back to that documentation. But essentially, the next steps are to run YAST crowbar. It's a module for YAST that allows you to configure the rest of crowbar, customize the rest of your network stack for all the various network pieces for Neutron and things of that nature. And then run a command called go. Go will essentially deploy crowbar onto the admin server. So we'll go ahead and finish this. And we'll load up the YAST crowbar module. And we do have a beta ULA in here. YAST crowbar. And now this, you can actually change the password for the crowbar user and a couple of other things set up some other repositories. I'm gonna focus on the networks. So this is where you can go in and modify the networking for your entire open stack setup. This is very important because if you don't get this part right, then you will have to redo this. And by redo, he means reinstall the crowbar. Yes, reinstall, exactly. So I'm going to change, again, the router should not be a dot one, it should be a dot two because this is running in VMware. And so that is actually the only parameter I'm going to change. However, if you do want your floating network to be much larger, you will need to modify that because it really only accommodates for, I guess around 50 IP addresses, which is not very big. So you'll really want to modify that for a production environment. And the next part is running screen and the go command. Now we put it in screen, I'm running it from the console here. So screen probably, it wouldn't really matter, but if I was running it from say SSH, the crowbar execution actually restarts the network and things and sometimes it disconnects and causes the whole script to actually terminate. So that's why we use screen for the command. It'll go through some checks and start installing some services and completely deploy crowbar and then we can get into the web interface. Once that's complete, we can actually do a batch deployment which we'll show you here in just a moment. Let me go back to the deck while that's actually configuring there. Any other questions up to this point? Yeah. I am not running SMT on this image. This particular image does not have SMT installed either. There is an alternative image out on susastudio.com that does have SMT. So for those of you who are not familiar, SMT is called a subscription management tool. That's a free SUSE tool that caches down your patches and updates locally so you don't have to go back and hit R servers every time you want to pull patches. Yeah, that makes sense. So you'll want that for a production environment because that will give you all the repositories that you're going to need to maintain your cloud environment. Okay, backwards there. So we have our admin node. Currently crowbars being deployed. From there, we'll actually deploy our control node and then our compute node, our storage nodes, and then configure the rest of our infrastructure. So we're going to use a batch in this deployment today. The batch will allow you to deploy your cloud in minutes. And in this particular case, it'll probably take about 18 minutes to fully deploy using the batch. Yeah, so the batch script is actually written in a YAML format. So it's really easy to read and it has the capability to actually go out and export. So if you have a configuration you've already set up prior and you want to duplicate that and create another cloud environment, you can actually do an export of your configuration into the YAML format and then reuse that again. So it's very convenient for replicating your OpenStack cloud. The orchestration tool behind all that is crowbar. If you're not familiar with crowbar, crowbar is a tool that is built on top of Chef. And so Chef is doing a lot of the work in the background. So it's sending commands to Chef to go out and do work for the nodes that it's managing. Let's go ahead and go back to, it's almost done. It's transitioning to ready and then we'll be able to log right into it. Who here's familiar with crowbar? Nobody, okay, well this will be new for you then. So crowbar was an open source project. It was originally started by Dell and they were on it for a while. They transitioned away from it when they started doing partnerships with other companies that use other deployment frameworks. And so at this point we are the primary maintainers of the crowbar project. So some of the things that you run into with crowbar, such as if you have to change the networking, you have to rebuild the whole thing, that was kind of a legacy decision that we're in the process of trying to fix. But overall it's a really good and very flexible tool that enables you to get things done quite quickly. All right, it's almost ready. Any other questions at this point? Okay, he's telling us he's ready. Just add a YAML wrapper around so you don't have to do this chef for a code Ruby. Yeah, you're not writing, for most deployments you're not doing any code in Ruby. You may, if you have to have some sort of customized deployment, may have to alter one of the recipes that are in place right there. But for the most part it's just point and click through the graphical interface that Cameron's got up right there. You'll basically, you get this set up and then you network boot your, pixie boot your systems against it. It'll auto discover them and then you can start doing things with them. In the case of this demo, Cameron's gonna batch it all out in a script but you can very quickly and easily do it from drag and drop as well. So this is crowbar. This is the dashboard for crowbar. And all that's managing right now is just the admin node. That's not really special. So let's go ahead and start up a compute node and a controller and get these all running from here too. Alice. Now ideally you want to pixie boot. Don't do that guy. These nodes. It will actually hit the crowbar node and pixie boot off of that. So the admin node is set up to pixie boot in the entire environment. So from a bare metal perspective, it's set up to manage the entire infrastructure. We'll do the same on this one. Yes. It is a full-fledged Chef server. Yeah. So if you're familiar with Chef, you're probably going to be able to dig right in. From a support perspective though, you don't want to go doing too much with it just because you want to remain and not invalidate your warranty kind of stuff. Yeah. Talk to us before you do it. Should we make our next? So it's all designed around around managing your cloud infrastructure. So if you're doing things like tweaking how the cloud is going to be deployed, those things are fine. You may want to tell us about it ahead of time so that we can make notes in your file so that when you call into support, they don't freak out. But I would not go in and add in stuff for like managing stuff outside of the cloud and you're trying to do your whole company off of the Chef server on here. And luckily none of our engineers are in the room so I can say that. What? It's all on tape. It's all on tape. So what I'm doing here is I'm drilling down to the compute node. I'm going to edit the compute node. I'm going to give it an alias. The aliases are actually used for the batch deployment. I'm going to call it compute one. And then I'm going to allocate it. The allocation process installs the operating system. You do have choice between what operating system you can install. Right now, since I've already allocated it, his target platform is SLEZ11 SP3. Now it does give you choice between Hyper-V as well and SLEZ12. So if you wanted to attach to a Hyper-V environment, you could do that. It does deployment for Hyper-V node. So this will run through the install on that compute node. So going back to the dashboard, I have another node in there. This one's going to be our controller. We'll change his alias. Here's the dropdown I was referring to. Notice the other OS is in there. They're grayed out because I don't have the bits on the disk to deploy that. I could also change my intended role if I know what that's going to be. It's very helpful if you're doing this manually instead of batch because that way, whatever you select as control node is always going to be the default selection for any of the control node services. Yeah, absolutely. Yeah, for the Hyper-V. And the SLEZ12 ISOs are not on that image. So if you did want to do SLEZ12, you would need to download the ISO for SLEZ12 and put it into the admin appliance, okay? There's a specific location for that that's called out in our documentation. You would just extract it to the disk and that would be made available for use. This isn't super exciting here. So we're going to switch gears and talk about something else. So once we have a cloud deployed, there are various other templates in the cloud. You're probably familiar with heat and things like that. Heat can be used to basically orchestrate your applications in the cloud, deploying your instances and your applications out into your cloud. So deploy your OS, Apache, set up your networking stack, set up your storage and everything that's required for those instances in your cloud. And it's all orchestrated from the control infrastructure through heat out to your compute nodes. Once you have a compute node up and running, you can scale up, scale down that environment using that same infrastructure. If you're familiar with Solometer, that will allow you, if you're using that in conjunction with heat, it will allow you to scale up and scale down that environment. From that same infrastructure, that same batch deployment, if you go back to that admin node, back to crowbar, you can also do the same thing and have a load balance environment as well and be able to load balance your environment through heat and Solometer, scaling up and scaling down and adding a proxy environment front of, let's say your Apache web environment or your database environment. So you can make that load balanced in your infrastructure. Scaling up to multiple nodes. Let's see where that's at here. That guy is not going anywhere. That was the second one you did, so it's a little bit behind. So the really cool thing about this demo is how exciting it isn't. Right, because he's not really doing a whole lot of things. He's just kind of pointing and clicking in a couple places and it's doing what he needs it to do. If he was having to do some elite ninja hacking, that would be a problem. We do have images for the compute infrastructure too. So if you don't have the capability of doing pixie boot, we've got an image for that. And then you just use it. There's a Chef join, or it's a crowbar join script that joins that server to crowbar so that you can use it in the infrastructure. So there is another method besides just doing pixie boot. So if pixie boot's not an option for you, there's another method. And you could manually install Slez on it as well. Question? So have we ever run it on ESXi? And yeah, no, we've run it on ESXi. And it does work there, absolutely. VMware is a fully supported option for deployment. We support VMware Hyper-V as in KVM. And then we've got technology previews for Docker, which hopefully will not be technology preview for much longer. And trying to think if we have anything else. Nothing's coming to mind. You do? Be careful though, because you might have another pixie set up there. So you might have to isolate the network or something so that you're not trampling over somebody else. The plan was not to watch this stuff. I actually had it fully deployed this morning and for whatever reason, the networking stack on the host would not connect to it. So we're redoing it. It's fine. Demo without a net. So one compute node's done. This one's almost finished. He's going to boot back up here and run an auto-yast and NIT script.  Let's go ahead and take a look at Crowbar. He's come up green on one of them. Let me just dig into Crowbar just a little bit more for you. Crowbar has this thing called bar clamps. Bar clamps are basically a subset of software that it will deploy. Plugins. So we have the option to select open stack. And we have all of the suite of software available for open stack out here. And we can go through and start deploying all that. So if you want to do an HA infrastructure, you will absolutely want to set up your pacemaker first for your control infrastructure. And that's actually pretty cool because HA is something that can be difficult to get right. So in this case, it's completely automated. You can just basically drag a couple of systems together and say, I want you to be part of the cluster and just click the apply button. And that's pretty much your setup, aside from getting your stonet device attached and whatnot. Yeah. Yeah. So let me go ahead and see. We'll hit Create on this database. And there's not a lot of options to choose from. Although SUSE is not giving you any choice on what database you can use. The database we support here is Postgres SQL. So you could go into raw. And there's a few more options. Most of the time, you're not really going to need to do this. There are some other bar clamps like Keystone. So if you want to tie into an LDAP infrastructure or something like that, you may want to go into the raw mode and edit a few things. But for the most part, that's pretty rare. You're going to have to go into the raw mode and edit a few things for the configuration. We put a lot of options out there that are most commonly used. And we make some good choices for you on some of those options as well. So we make it easy there. And our controller and computer are fully deployed. Back on the admin server, let's just make sure that that template was deleted. He's gone. He won't conflict now. We do have, on that USB thumb drive, there's a couple of templates already pre-built for you. So you can go try those out. They're on Roots home directory. There are three files. You have drbd.yaml. You have nfs.yaml. Those two are for an HA environment. The drbd will set up a two-node cluster with drbd replication for the database and Keystone. The nfs will set up a two-node cluster using nfs as shared storage for your database for Keystone. So you could go with a three-node cluster if you wanted to on that. In a production environment, we recommend running three separate clusters. You would have a data cluster, which would actually have your database and Keystone running in that cluster. You would have a networking cluster. That cluster would run Neutron with a three-node cluster. And then you would have a services cluster, which would run all of your other services in your cloud. So let's go ahead and launch the one that says Simple Cloud. You do crowbar batch build, and then point it to your yaml file type this morning. And then off it goes. You can actually watch what it's doing from the web interface. You go to bar clamps and go to deployment queue. And it's going to commit a proposal here. And it will show you that it's actually deploying some provisioning various things within the nodes that are running in the infrastructure. If you watched the CLI right now, it's deploying the database bar clamp so it's putting the database out there. It's just going to go down through all those bar clamps and start deploying. It's deploying the cloud right now. So this will be up in a matter of minutes. And you'll have a full cloud deployed. Any questions? The networking node. This is a Simple Cloud, so this is a single controller infrastructure. So Neutron is going to be running on the controller with everything else. That I wouldn't recommend for production at all. But just for testing it out. This is really simple and easy. Yeah, question in the back. So he's asking if you can use crowbar for upgrades, right? And funny you should ask. But we actually have that built in to the infrastructure. Now you can attach Susan Manager to your environment to give you a much better and broader update stack. But we also have another option if you don't want to go with Susan Manager. We also have the option to deploy the Susan Manager client through crowbar. But we have this thing called Updater. It's just another bar clamp proposal. You can actually go in and edit that. Select patch or update or distribution upgrade and pull over the nodes that you want in that and apply the patches.  So if you don't want to install kernel patches on a regular basis, you can exclude those. But upgrading from version to version is fully supported by Susan and has been for several since the Havana release. Good question. Any other questions? Yeah. So he's asking, what about SEF and other things that you might want to deploy in your cloud? So SUSE OpenStack cloud is set up to actually deploy SEF. There is a bar clamp for that. And you can actually go and create that proposal and deploy a SEF cluster using crowbar. So what that is going to do, though, is we have a product called SUSE Enterprise Storage where we're doing support for SEF. So this bar clamp is going to do that. Otherwise, you have the ability in the other bar clamps, say, for glance. You can select the rados gateway and tell it where your existing SEF cluster is, and you can join it up to that. So we're at the top of the minutes for this session. So let me just wrap up really quickly. It is SEA Bar Clamp Proposal Neutron. So it's setting up the network right now. It's got a few more bar clamps after that, and the cloud will be fully deployed. And then you can go in and start up instances and play around with it. So go play around with this with the cloud. I just gave you on the thumb drive earlier. And if you want updates to that, come up here. We'll scan your badge. And we'll send you update information on the latest version of this appliance. So we will be having regular updates to this appliance, making it better, improving upon it, adding more things to it. So if you want that, come up here. We'll scan your badge for it.


Live from New York, it's theCUBE. Covering theCUBE, New York City, 2018. Brought to you by SiliconANGLE Media and its ecosystem partners. Welcome back to theCUBE NYC 2018. I'm Peter Burris with Wikibon and theCUBE and today we're going to be talking to Sung Park who's the Vice President of Product Marketing and Developer Advocacy at MongoDB. Welcome to theCUBE. So, we're going to be here for the next couple of days talking about issues pertaining to big data, artificial intelligence, how those two things are coming together, how they're going to remain separate. MongoDB, 7,400 customers, that's what gives you a stake in the industry. But what is the problem that MongoDB and others have been trying to solve? It used to be that MongoDB was a database, it was a substitute, but as it's grown, as it's expanded, as the use cases have become more fungible, it's evolving. That problem has to evolve. Tell us a little bit about the problem that people are trying to solve today. Yeah, so MongoDB obviously has seen a fair bit of success over the past few years. As a company, we're only about 10 years old. We just passed our 10 year anniversary last year. And for us, I think we're extremely proud of the fact that we are not only the leading modern database in terms of, to your point, powering today's modern applications, but also looking ahead to ultimately where we want to be is looking for the ease in which we can amplify how developers are building, but more importantly, how customers and businesses are actually leveraging MongoDB to do things around world-class global applications. So as a company, we started off probably pretty early on looking at more systems of engagement type use cases, web, mobile. Those are pretty straightforward for us in terms of, again, developers being kind of empowered by this document model, which is very natural, very intuitive, which allows them to not only build very quickly, but also iterate on that. Link page, link page. Correct, correct. And over the past few years, we've put a lot of investment into looking at how we can now leverage this massive developer adoption to really investing in the product. So in most, I guess, the large banks, maybe as a great example, they are now leveraging us for more systems of record type use cases where they are mission critical. The requirements are centered around data governance and security, but also looking at scalability performance, but again, really centered around business velocity. How do we iterate very quickly? And now I think as the world has just been very quickly evolving around us, really looking at how we can leverage MongoDB with customers to drive much more actionable insights, so systems of insight and intelligence, and looking at how we can make that so much easier for not just developers, for end users, right? Because for us, it's really about the developer experience, but also the user experience. And for us, kind of the broad vision we see is having this ubiquitous kind of global data layer, if you will, Peter, and it's the ability for data to reside anywhere and everywhere it needs to be, be able to get to market very quickly by again leveraging the ability for MongoDB to kind of take away some of the complexity around siloed data, data exists, and all these different types of data stores and databases, make that as easy as possible, but more importantly, leverage this thing called cloud. And for us, like we're really excited about the last few years in terms of product development and what we've done building things like MongoDB Atlas, which is our fully managed database as a service offering, building things like MongoDB Stitch, which is our serverless platform, to again, take that step function of now driving developer productivity to that next level almost exponentially, and we can talk about that. And more importantly, leveraging the cloud, right? So MongoDB Atlas supports all three of the major cloud providers, AWS, Azure, and Google Cloud. And for us, we want to give customers and users the optionality to not just pick and choose which cloud provider they run MongoDB on, but again, in the context of this ubiquitous data layer, they don't have to worry about where it resides, so you can also leverage kind of the best of breed services. Well, I want to build on that for a second, because I think you still have to worry about where it resides. Data locality is still going to be important, but coming back to one of the major trends, it's people talk about the explosion of data. You hear all the time, in the next two years, we're going to create more data than we've created in the entirety of human history. That was five years ago. Which is mind-boggling, but what we often forget is that the number of data sources, the number of data sinks, might even be growing faster than the size of the data. And that the traditional way of thinking about this is, oh, we're going to create all this new data, and we're going to put it in existing databases. The reality is, we're going to create all this new data, and we're going to create a lot of new databases as part of the process. And so in many respects, what you're saying is, there's business problems that naturally have data associated with them, and the style of the application is going to be a really, really important part of the conversation about how to serve this, and that the technologies used to deliver that become essential and strategic decisions from a business standpoint. So, for example, serverless has enormous implications. Talk to us a little bit about Stitch and how MongoDB and serverless are going to come together, because it's going to be a very, very important technology as we look forward. Yeah, it's a great point. I think for us, we obviously worked on MongoDB to be the best modern database, bar none, right? And I think we've more than proven that and achieved that, especially with the announcement of things like multi-document asset transaction support. Even though it's not been a requirement, let's say, for a lot of users and customers to be able to support mission-critical workloads, it ends up being a checkbox. It's just a good technology for a particular style of application. So you're trying to cover all the application bases because that's what a great data platform needs to do. So again, come back to... Yeah, so we grounded on that, and for us, we wanted to take that next evolution, right? So we created MongoDB Stitch, which is our serverless platform, and it allows to basically drive three kind of key functional areas, right? In terms of meeting specific drivers around, again, developer productivity, let's remove a lot of the boilerplate code, all the things that are kind of mundane, kind of low value for developer to build applications. We wanted to make it seamless and easy to integrate, integrate with obviously cloud provider services, integrate with custom APIs and basically webhooks, things along those lines. And then to your point, more around governance and security, make it in a way that, again, customers don't have to worry about security, they don't have to worry about data locality, data resiliency and making sure that where you domicile data is going to be ultimately kind of abstracted out, and all you have to do is define the policies with Stitch, and we take care of that for you, as well as a key capability that we have in Atlas is something called global clusters. It's the ability to have very low latency, high performance capabilities that we can move data closer to the user, and do it in a way... Closer to the activity. Closer to the activity, right? Because again, let's face it, every company is becoming a software company, and it's not tens or hundreds or thousands of users, it's millions of users around the world. So we want to... Billions because a device is also a user from a database. Absolutely, absolutely. So we wanted to move the data as close to the user as possible for the best user experience, but in the same context, be able to adhere to all the strict regulatory compliance, data locality, data sovereignty rules, and kind of requirements that exist. So we have this capability called global clusters with a few single mouse clicks, be able to define a policy, where does data actually reside, and who has access to that data, and again, be able to push it very quickly through any of the three cloud providers onto again, as close to the user as possible. So that's one example of what we've done to handle that. And then for Stitch, our serverless platform, it is really a function of being able to again, let developers create very quickly, increase that time to market, but make it very easy for them to expand and address that global user base. So look, database has goodness to it, right? As you said, governance, security, all that becomes part or parcel of the database, but it also has some associated overhead. Modeling the data in advance, how you actually administer the data, and what you're trying to do is bring the goodness of the database, but reduce some of the traditional administrative headaches associated with database, without losing that goodness. So as we think about the developer, because you also have the developer advocacy hat to wear, what are you doing over the course of next year to take this 7,400 businesses that are using MongoDB in a strategic way to even further expand the role that MongoDB is going to play in building a lot of these new applications? So our perspective on developers, developers are the heart and soul of MongoDB, right? If you think about our founders, they're all developers, and they wanted to actually address and solve this interesting database problem 10 years ago. The hardest thing about building an application was actually working with databases that are from yesteryear, right? Four decades ago, built in a different time and a different place, requirements have obviously changed. So for us, it's really being able to amplify not just the awareness and leveraging the millions of developers that already use MongoDB, but doing it in a way that allows us from a company perspective to kind of share the goodness, right? I truly believe there's no other voice better than the developer and the customer and the user to kind of talk about MongoDB and how they're using it. And if you think about companies like Coinbase, for example, right, a great customer of ours, I mentioned kind of the three systems of engagement and record and insight. They're leveraging Mongo for all of those things, right? And for us, from a developer perspective, we want to make sure developers have options. They're aware of all the choices, but also be able to leverage best of breed in terms of building for today, but kind of future-proofing their work. And experience matters. In the developer world, experience matters. If you do it one way, if you can use a set of tooling to build that application and the tooling can support other applications, continue to do it because it just, it makes you better, makes your development better, makes your practices better, makes your organization better, experience really matters. This is hard stuff we're talking about doing. Yeah, it is. And I think back to the developer point of view, we do want to make it more of a, almost a grassroots, right? As far as making sure we meet with developers and our users out in the community, whether it's through user groups, conferences, events, we sponsor a ton of hackathons. We do a lot of work with the universities because we want to, again, just drive that awareness, but also show them a better way, Peter, because I think everyone's kind of been brainwashed and programmed to think about data from a relational perspective, and there are fine use cases for that right now that we, again, will kind of say, hey, use relational where it makes sense, but it's probably more for, you know, cots, custom off the shelf, or commercial off the shelf systems that are already just embedded, right? Versus if you're really, truly thinking about building modern applications for today's day and age, there is a better way, right? And if you think about what we grounded with the document model, it's the best way, the most natural way, again, to work with data. If you think about how we've handled distributed systems, we've architected MongoDB from the ground up to be, again, globally resilient, scalable, and available. And if you think about now the freedom that we give users to basically run their workloads anywhere with, again, MongoDB running on your laptop, or MongoDB Mobile running on a device, as well as on the mainframe, on-prem in a data center, and now into the cloud, I think this really positions us very strongly in terms of how we view this kind of ubiquitous data layer again, globally, that again, users should not have to worry about working with data, right? You have to jump through hoops in order to worry about where things reside. How do we adhere to things like GDPR and all these, again, data sovereignty and locality issues, and we want it to be as seamless, as easy, and in performant as possible. So for us, that's our mission. All right, so Seng Park, VP of product management, product marketing, and developer advocacy. Thank you very much in talking about how the future, we can think of getting the goodness of database faster. Once again, MongoDB, we will be back shortly with more from theCUBE NYC coverage of new trends in big data and artificial intelligence.


If you could pause one moment, Fredbine needs to take sister Priscilla outside first. I have no phone to see with Duke. You have more than that. Once again, you'll go to the podium. I'm on the traces to the left of the podium here. Just go on the other traces. You only have two markers. This great house receives many great visitors. But none more special, more revered than I've been able to guess today. I mean that quite literally. So we rather appreciated her priorities and we're very happy indeed that she could come to America. The Indian. However, it simply occurred to us, and we wanted to honor her, that the agreements in some of our transistor all borders, which we accepted, and I will now read the citation. Most of us talk about kindness and compassion, but neither do we order, for the missionaries of charity have spread throughout the world, serving the poorest of the poor, but the duration is... May I say that this is the first time I've given... In the name of the millions of poor people, for this Duke, in spirit and in love, we penetrate the hearts of the people. So in giving it to me, you are giving it to them. But this is what happened to me. Read it, and I know it has come from more people, from your country, and they have shown that giving their children to become sisters and to serve the poor throughout the world. We are now all of the world and trying to do for them. And my gratitude to you, we have love, peace, joy, togetherness, and lots of love, of lots of peace, and I feel it's a gratitude to you and keep the joy of loving. Love, then, and the good in your whole family trust, and that love will penetrate art. Right through the furthest place that no one has ever been moved to the east to do what Jesus said. You did it to me. But a wonderful opportunity for each one of us to be 24 hours with Jesus and be doing what we are doing. That's what He said, if you will send us in love with Christ for each one of us. So once more, I want to thank you for this and we just want to thank you. This we see. But they did a study of 1,590, I call it 1,600 people Tuesday and late Wednesday night both before and after the press conference. What they found was support for the President's building, more support for the President building after the press conference than before and public support for the President virtually every point he made. As you see indicated from a small sample before the press conference, strong public support. The NBC support showed 62% saying we should not negotiate. 57% said we should not ask Israel to negotiate. 54% said we should not give in to the demands of hijackers even if it meant the hostages were killed. Support for the President's handling of the situation was 52% Tuesday press conference. 61% by Wednesday and your job approval rating went up 6%. Now what can I ask you? I mean I'm glued to CNN of course, you know, glued. The fellow from Switzerland, is it? Well, in the state of Switzerland that somewhere they have suggested themselves remember there is a possible exchanging of the people on their territory. It's not known. We are moving, let's say several different directions to see which way brings the most pressure on them. We don't know which of these buttons will be the right one but we're pushing all. Good. But in saying pushing buttons that's merely an expression. Yes. I understand. That's not, yes, we won't say that. We're trying every other way. That would not be the expression to you. No. We are all of these attempts on non-belief. What was this you were saying about today? Well, all of a sudden we got a word that the these Shiites there that they were going to have a press opportunity to press an event and it turned out that they were setting a table there at the airport. Oh, my goodness. There are quarters up there and a whole lot. We want to know what's going to happen outside. And you bring me in with monetarisa. That's a fact to follow. Well, listen. This is a private sector initiative commendation for outstanding voluntary service and initiative in recognizing individual citizens, businesses, and civic organizations for their important contributions to the communities across the country. And I'm most pleased to give it to you because I cheered every time when you see that these people get mentioned and I know that it stimulates further volunteerism benefiting an awful lot of people. Thank you very much. That really is an honor and I appreciate that. Thank you. I hope I can do some good. You can point out cookies. Thank you very much. Thank you very much. Thank you. Thank you. Did you get that person? I did. Who would have told the floor? Who would have told the star forward? The guy puts his hand on your back. It's really great support. It's got a wonderful picture of the organization. Thanks again. Thanks for your time. Thank you. Thank you all. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Never stop. Thank you. Thank you. Thank you. Thank you and thank you. I'm prepared to give you a great candidate. We've got a wonderful candidate for senator. We need another part of the top of the ticket there. Carry the ticket. And everybody in Arizona tells me that you would be the best candidate for governor. Thank you. You helped state government. And I've been there 20 years. I just want to say that whatever you're doing has been the best for us. Thank you very much. Now these aren't bribes that I had in here. They're just some souvenirs, so you won't forget us. For you, for Tiffany. Thank you. And for you, for Ken. Thank you very much. And for the girls, Charles. Thank you. So you would tie a bar. That's the seal. I always like to point out this is a little bit of history. You notice the seal up there? Where the eagle is looking? Where the ollie branch? Well now there's the original seal in the desk years before that. And the eagle is looking at the arrows. And after World War II, President Truman decided that with peace, let's have the eagle looking at the ollie bridge with peace and strength of the arrow. So that's the newer person. The newer person, you get the newer person. Thank you very much. Appreciate the sound. Arizona is kind of our second home. I know that. Thank you. And we give him time to allow the people in the ranks that are disabled and done a great deal. And the others of you here in the advertising agency. The advertising council I should say and all of that you're doing, I think it's wonderful. Thank you. Thank you, sir. Thank you, sir. As you know, this is the kick off for that campaign. Yes. The own action with the needs of the disabled. And so, Ray's our key star in all of that. And given his time, and of course, Allen's worked hard on that with the decade of the disabled. But you signed that document a while back. And so we're well under that program. Well. Absolutely. We're grateful for you for kicking off the decade of disabled persons in this country. And that's provided leadership around the world. And Ray Charles here is a personified with Greatness of America, showing how disabled people can really participate in the war for themselves and contribute to our national lives. Thank you, sir. Any of you, have you been informed that the, what, in our Defense Department said, that they, how they have expanded in, in the whole departments that are hiring? Very closely. Hiring people with a handicap. Some kind. Excellent. Yes, yes, yes. And Secretary Weinberg has set goals for the department. This is the assertions. And it's a model for the federal government. You'd love to see what happens in all the agencies in the country. What you've heard before is what we're trying to do. You're wearing a change. You're not the big one. Mr. President, I think you can have it. You better tell you. They assume that people are better in checking the blades for over the next year. Uh-huh. Yeah. Because it's a text. Yeah. That's right. That's right. And that's your mission. Stay up to date. Yeah. Thank you, Mr. President. Thank you very much. Appreciate you. Let's see you again. Thanks for having me. Thanks for the chat. Before you did that, did Ami help you with your tax bill today? You can now take all that out. I'm glad you're here. I'm glad you're here. I'm sorry I had to work. Thank you, Mr. President. I appreciate that. I appreciate that, Tom. Thanks. Go ahead and move. Thank you very much, Mr. President. Have a safe trip. That's well done. You're doing too well. I know we just wrote you the other day that you were supposed to put 25 pounds No, I just try to get them off my cell. I worked for you, Canada, so thank you for having me. Well, thank you so much. I appreciate your having me. Take care of your breakfast. All right. I'll put a lot of people in this building. I believe you. I'm feeding for them. I'm just out of here. Oh. It's been wonderful again. Well, all right. Thank you. All right. I just started chatting with a friend of mine, Governor Shaffer. Yes, he is. You're right. I was covering Governor's Conference as he was there. Covered your first campaign, your first Governor's Conference. And three presidential campaigns, but I don't miss it. You don't miss it. And now you're retired. I'm retired. All right. So you won't forget it. It's all because of the entity. And I wonder why I would hear about you at any time. I'm sorry. There was a little confusion as to whether she loved you or not. I'm sorry. I'm sorry if it wasn't mixed up. Well, I'll see you in here, but give her the pen. Well, thank you. Thank you very much. And I wish you best. Well, thank you. It's been impressive to observe a little hard on you. I think we've got a chance to do it with some credit. Okay. Okay. All right. Thank you. Good luck. Good luck.


Hi everyone, Joe for Jaspy's casebreaks.com with a Magic Bulls Sun's Blazers random number block randomizer For flawless figure team three big. Thanks to this group here for making it happen. There are the numbers right there Let's go. Let's roll it randomize it names and numbers four to two six times one two three four Five and sixth and final time We got Gretchen down to Andrew four to six four to six four to two six times one two three four and a two five and Six in final time after six we got nine down to zero I usually give my zero redemption spiel, but should not be any redemptions in And flawless Gretchen with nine Sumin with two Stephen flat with eight Gretchen with one mark with five Stephen with six Gretchen with four and seven Sumin with three Andrew with zero All right coming up in the next video the break itself Jaspy's casebreaks.com. Bye. Bye


There is another way of extending the integral. So, let us look at that. What is that way? So, a Riemann integral on AB to R bounded. So, we defined with respect to a partition P, the lower sum and the upper sums. They were all less than or equal to this. And as the, you took the supremum. So, this was, you look at the supremum of L P f is less than or equal to infimum of U P f. And whenever these two were equal, that was called the integral of A to B f x B x. But the important thing in this was the, in the upper sum or the lower sum, say for example, in the lower sum, if the partition P was x 0 less than x 1 less than x n equal to V, then you looked at the lowest value. You are approximating by looking at the lowest height of the function into the length of the interval. So, the idea was that you look at the length of that sub interval. At some time point, somebody thought, so what we are doing is, you are given an interval A to B on the line and you are trying to measure the length of that interval. You measure the length by looking at, saying that this is an interval B minus A. So, length is B minus A. So, that is the length of this interval. This is I. But I think probably that may be a nice idea to introduce. So, length on the class of all intervals taking value 0 to infinity. So, length of an interval I is defined as B minus A, if n points A and B. Otherwise, you write as plus infinity. If it is an embodied interval, the length is defined as plus infinity. But this is something I can change this notion of length. So, what I am here, when the n point is A and B, I am saying it is B minus A. Let us take alpha function on real line to real line, which is monotonically increasing. So, let us take a function. Then what is wrong in saying, I define the length of interval I to be equal to alpha B minus alpha A, if I has n points A and B. What is wrong in saying that, if I have the length to be equal to alpha B minus alpha A. That means, at every point, I am giving the different weightage to every point, where the earlier the length was B minus A. Now, the length is alpha B minus. If alpha is equal to identity function, then it is the original length. So, the idea came that, when defining that upper sum and the lower sums, UPF, let us define the upper sum with respect to a new length function alpha. So, what is going to be the definition? It is the maximum value of the function as it is. The height remains the same, but the base length changes to alpha x i minus alpha of x i minus 1 and summation i equal to 1 to n. Change the length of intervals and similarly, the lower sum with respect to this alpha, I can define it as sigma m i alpha x i minus alpha of x i minus 1. Still, the same property remains true. LPF alpha is still less than UPF alpha. Is that okay? Because these two quantities are the same, the weightage of the length is same, small m i and capital M i. So, that still remains the same. So, still I can ask, what will happen if I refine a partition? Because if you keep in mind, in the lower sums and the upper sums, when you refine a partition, length does not play any part. It is a supremum or the infremum that changes. So, same properties of lower sums and upper sums will remain true whenever you measure the length in terms of a monotonically increasing right continuous function, monotonically increasing function. So, this, so you can look at what is the supremum of lower sums, what is the infremum of upper sums and whenever they are equal, you will get a new integral which is defined with respect to a weighted measurement of length on the line. So, this is possible and this is what is called Riemann still j's integral. So, let me, because not many changes come except for a few places, otherwise the whole theory goes as smoothly as the earlier one. So, that is what we are, I think. So, let us start with a function A B to R and alpha is a monotonically increasing function on A B. Given a partition, look at the infremum, look at the supremum like we do it for upper sum and lower sums. Now, how is the new upper sum defined? How is the new lower sum? Minimum value into alpha xi minus alpha xi minus 1. So, lower sum, similarly the upper sum with respect to the, is a weight you are attaching to each. See, why this is important in probability and statistics? You assign different weights to different points. So, you will have probability distributions which come via such kind of functions, mononon functions and the expected value of the functions will be with respect to the weighted measurement of length of that interval. So, that is why this is important from statistics point of view and mathematics point of view, it is a generalization of the Riemann integral. So, upper sum and lower sum, so you prove those property that the upper lower sum is always less than or equal to upper sum. That is not a difficult job. There is a same thing, same proof continues. You can define upper Riemann still j integral, lower Riemann as a supremum and the infremum of the upper and you say the function is Riemann still j integrable. The supremum of the lower sums with respect to alpha is equal to the infremum of the upper sums with respect to alpha. All everything goes on smoothly. So, you say that is the integral and common value is called the integral. Probably all the theorems go as in Riemann integral except probably some points. I will point out where the things go a bit. So, for example, upper is always lower than the bigger than lower and the function is integrable whenever the difference can be made small because that is the only thing that makes a difference. Alpha length does not contribute anything actually. So, all those theorems, same proofs go over. Only difference in the proofs will be that instead of writing x i minus x i minus 1, we will be writing alpha x i minus alpha x i minus 1. That is all, nothing more. So, all those proofs go. So, here is something. If every continuous function is Riemann still j integrable like in Riemann integral, we proved that if f is continuous on a, b then it is integrable. So, what was the proof basically? The proof basically was that because f is defined on a close bounded interval, it is continuous. So, it is uniformly continuous. So, given epsilon, there is a delta, so that whenever two points are close by distance delta, their distance f of x i, the values are also close. Now, what are the upper sums and lower sums? For a partition, you look at the points upper sum minus the lower sum, capital M i minus small m i. What is that? If the function is continuous, capital M i is attained at some point, small m i is attained at some point. That means, in the interval x i minus 1 to x i, capital M i is f of something in that interval, small m i is f of something. So, if your length of the partition is less than delta, then the values will be less than epsilon because of uniform continuity. So, given f is uniform, f is continuous by uniform continuity, given epsilon, choose a delta, choose a partition whose norm is less than delta. So, you will get capital M i minus small m i will be less than epsilon into the length, so that will be small. So, that was the proof. So, in the same proof, if f is continuous, uniform continuity, everything makes sense. So, what we will be doing? Instead of multiplying by x i minus 1 to x i, we will be multiplying by alpha times x i minus alpha times x i minus 1. Same proof, no change will come. So, every continuous function will also be Riemann Stelge's integrable with respect to alpha for the same proof, if f is continuous. No change comes. The change comes supposing f is not continuous, it is only a bounded function and alpha is monotonically increasing. We know that for a bounded function Riemann integral lean not exists. So, the modified theorem for Riemann Stelge's integral is, if that function alpha, which is monotonically increasing, is continuous, every discontinuity point of f, then it becomes Riemann Stelge integrable. So, the discontinuity of f is taken care by the continuity of the point, monotonically increasing function. Alpha is monotonically increasing. So, it is discontinuous at the most, at countably many points. We know that. So, the only change comes with, it is continuous at every point of discontinuity of f. Then, so that is for any bounded for Riemann integrable function, we said that every monoton function is Riemann integrable. For Riemann Stelge, you require f to be, alpha to be a continuous. Not only monotonically increasing, you require also it to be a continuous function. We will not prove all these theorems, but I am just pointing out the differences between the two statements of the theorems. So, that is properties of Riemann Stelge. Other facts, they all continue to hold. If f and g are Riemann Stelge integrable, f plus g is Riemann Stelge integrable, because the sums will split anyway into two parts. So, length does not change those properties. So, Riemann integrable of f plus g is Riemann integrable of f plus Riemann integrable of g, same property holds. Scalar multiple integrable comes out, f less than g, then same property holds. So, similar properties hold, not much change comes. So, that is why not, proofs are not very interesting for all this, but we will not anyway go into the proofs of these things. So, the basic fact is that you can extend Riemann integral in two different ways. One, look at function being unbounded on a bounded domain or function being bounded on an unbounded interval. That gives you one set, which is called improper integration. Or, you can keep the function values as it is, but change the measurement of length by some monotonically increasing function. That gives you Riemann Stelge's integration. The two branches, which are, I think, probably I should just say that this Riemann Stelge integral plays an important part in further topics like measure theory and probability and statistics. It will come again and again there. And, of course, improper integral comes in a disguised form of gamma functions and gamma function and Cauchy distributions and so on or normal distributions and so on. So, you will require those things to exist. So, that is integration of one variable. So, next time we will look at integration of functions of two variables. That is also important from many subjects quite a few. So, we will look at integration of functions of several variables next time.