Podcasts about dcos

“That loan was for a purpose. Pay it back!”___P sued natural persons and Cos. D1 was not served and D2 was bankrupt, leaving P to pursue Cos only: [9]P's dad spoke with D1 and D2 about an investment. P later transferred $9.2m to one of the DCos: [3], [5]There was no written agreement: [6]In 2017, all agreed the $9.2m would be used for property investment, that if the property bought was then sold in a year 35% would be returned, and if unsold the funds would be returned: [6]In 2018, when the principal was not returned, the parties made a loan agreement, requiring repayment and interest: [8], [61]Repayments were not made. P sued: [9]P said the money was advanced to buy a specific property; and so was held in a purposive “Quistclose” trust. P said the money transferred to the other Cos was done with knowledge and so was recoverable: [11]The Ds denied a trust and said if there was one, then the loan agreement extinguished it: [12]The Ds served no evidence: [15]P had to prove the 2017 agreement, WITH a mutual intention that the funds would be used for a specific purpose, to be held on trust and returned if the purpose was not achieved: [21]P never discussed the proposed sum, proposed property or properties, location, or property size: [24]P said some docs sent after P's dad's the discussion were a representation that the money would be used for specific land: [29] - [31]There was no evidence of the purchase price being referable to specific properties or of any intention to purchase a specific property: [32] - [34]In this case, there was no intention to create a trust: [36], [41], [48], [54]That's because: the creation of a JV vehicle did not prove a trust creation intention [49], the potential of co-mingled funds absent a “trust account” points away from a trust [50], absence of language like “solely” or “exclusively” [51], and the parties treated the funds as loaned rather than held in trust [53]The Court then considered IF there was a trust, was it brought to an end by the loan agreement: [55]The Court held the loan extinguished the trust rights (if any) because (i) the loan came after and was inconsistent with a trust, (ii) the loan showed the parties abandoning the earlier agreement, and (iii) the loan's operation saw existing rights surrendered in exchange for additional terms secured under the loan: [65]The Court then considered the position if (a) there was a trust, and (b) that trust survived the loan: [68]Even if both criteria were met, the Court found no basis to order recovery against the DCos: [69] - [109]P's claim failed. Costs followed the event: [110]___Please follow James d'Apice, Gravamen, and Coffee and a Case Note on your favourite platform!www.gravamen.com.au

With the present focus on infrastructure, DCOs are intended to streamline and expedite the planning process for specific types of projects. Planning Partner, Laura-Beth Hutton discusses when a DCO will be relevant and how to get the best out of the DCO procedure.

This is fun one. Recorded a few weeks ago, Des and Kara start with a mini-preview of the World Championships in Budapest, which is even more interesting now that we know the results. Then, they turn to an in-depth discussion of what it's like to be in the drug testing pool as an elite athlete.  From mixing it up on the ones and twos (and we aren't talking about turntables) to the nuts and bolts of the whereabouts filing system, you get all of the gory details, including their favorite war stories. Des and Kara are huge advocates of clean sport so they view this process as a necessary part of the job, and one that's manageable if you accept it.  This episode is dedicated to the show's sponsor @tcsglobal and to all of the doping control officers (DCOs) out there doing this not-so-glamorous work for clean sport. May you all get good samples and win the lottery some day.

O apresentador Isaac Alexandre foi mesmo demitido? Agora é oficial? A fofoca que percorreu os quatro cantos do DCOS teve o seu fim e o final desse enredo trouxe uma surpresa! Nesta edição, Isaac Alexandre recebe os novos hosts do Podcast: Fernanda Dias e Luan Fernando. Curioso para descobrir quem são, o que fazem e até pegar o Instagram para dar aquela stalkeada?  Tire o fone de ouvido da mochila e venha conferir o mais novo episódio. ______________ OFF DA OFF Indicação de Isaac: Instagram - @designativista e @nickvernet Indicação de Fernanda: Série - Bom dia, Veronica // Dorama - Uma extraordinária advogada Indicação de Luan: Aplicativo - BeReal ________________ O Oficializando é uma produção da Oficina Porpaganda EJ Oficializando #20 apresentado por: Instagram de Fernanda (@iamfer.d), Luan (@luanfaragao) e Isaac (@isaacaalexandre) Identidade visual e produção/edição: Laiza (@oxelai) e Wolney (@wolnex) Atendimento, planejamento e social media: Matheus (@mxtheuso), João (@thejoaocarlos) e Alessandra (@alessandra.souzaoli). Apoio de pauta e produção: Cármen Beatriz (@_carmenalmeida) Roteiro: Bruna (@bruna_bfim) ________________ Não fique em off e acompanhe nossas redes sociais: @oficinaef @oficializandopod _________________________ Quinzenalmente, um novo episódio: Às quinta-feiras, 10h, no Spotify, YouTube, Google Podcasts, Radio Public, Apple Podcasts e PocketCasts!

In episode 14 of The Dirt Logistician, Lieutenant Colonel Stacy Moore (Goldminer 07, Senior Sustainment Trainer) discusses rotation 21-10 with Colonel Michael Simmering, Deputy Commanding Officer - Support for the 1st Armored Division and previously severed as Commander Operations Group for the National Training Center.   Key topics include: Hard and fast rules to get right within the sustainment warfighting function Sustainment architecture within the brigade combat team (BCT) and how it fits in the battlefield construct Resources that the division used to assist the BCT for the rotation (before, during and after) What separates professionals from amateurs

On this episode of DCOS we say goodbye to a legend, get updates on The Suicide Squad—and it doesn't sound like the movie's all dick jokes—as well as some WonderWoman 3 and television news!Richard Donner, Superman and Lethal Weapon Director, Dies at 91 |The Suicide Squad Is a 'Sad' and 'Complicated' Story, Says James Gunn |The Suicide Squad Considered Bringing Will Smith's Deadshot Back |How DC Jumped On Marvel Releasing James Gunn |The Suicide Squad Producer Won't Rule Out Marvel / DC Crossover (Exclusive) |Aquaman Star Amber Heard Reveals Name of Her New Baby Girl |Wonder Woman 3 Update |Warner Bros. Turned Down Kevin Smith's DC Comics Pitch Because It Was Too Dark |Superman & Lois: Sofia Hasmik Promoted to Series Regular for Season 2 |The Flash Confirms Key Stars to Return for Season 8 on The CW |Robin Givens Cast in Batwoman Season 3 |When Will Batwoman Season 2 Be on HBO Max? |JJ Abrams Working on New Justice League Dark Spinoff for HBO Max |

On this episode of DCOS we say goodbye to a legend, get updates on The Suicide Squad—and it doesn't sound like the movie's all dick jokes—as well as some WonderWoman 3 and television news!Richard Donner, Superman and Lethal Weapon Director, Dies at 91 |The Suicide Squad Is a 'Sad' and 'Complicated' Story, Says James Gunn |The Suicide Squad Considered Bringing Will Smith's Deadshot Back |How DC Jumped On Marvel Releasing James Gunn |The Suicide Squad Producer Won't Rule Out Marvel / DC Crossover (Exclusive) |Aquaman Star Amber Heard Reveals Name of Her New Baby Girl |Wonder Woman 3 Update |Warner Bros. Turned Down Kevin Smith's DC Comics Pitch Because It Was Too Dark |Superman & Lois: Sofia Hasmik Promoted to Series Regular for Season 2 |The Flash Confirms Key Stars to Return for Season 8 on The CW |Robin Givens Cast in Batwoman Season 3 |When Will Batwoman Season 2 Be on HBO Max? |JJ Abrams Working on New Justice League Dark Spinoff for HBO Max |

FinCEN reissues geographic targeting order for 12 metropolitan areas. CFTC renews no-action relief for certain DCOs from reporting obligations. FDIC Chair Jelena McWilliams promotes inclusion in the financial system. Cadwalader Partner Dorothy Mehta to address CPO/CTA/Investment Adviser issues at FIA's Virtual Law & Compliance Division Conference.

CFPB issues CAS approval for PayActiv's earned wage access products. CFTC and ESMA sign MOU on U.S. DCOs recognized under EMIR. NFA reminds firms of upcoming compliance date to satisfy swaps proficiency requirements. Broker-Dealer settles FINRA charges for recordkeeping and supervisory failures. Firm settles FINRA charges for options position violations. French bank settles OFAC charges for Syrian sanctions violations. Lender settles CFPB charges for unlawful payment terms on loans to military personnel. OFAC amends general license authorizing transactions with certain Venezuelan officials. Brass Tax: IRS Finalizes Carried Interest Regulations.  Effective date set for CFTC cross-border rule changes. SEC updates telework operating status.

Cadwalader Clients & Friends Memo: A New Year's Booster Shot: Congress grants SEC a statutory disgorgement remedy and extended statute of limitations. CFTC staff provides no-action relief to FCMs for SOFR-linked investments. CFTC staff provides relief to DCOs from amended daily reporting requirements. NYDFS grants charter for trust company to administer stablecoins. FINRA provides guidance on e-bill final statements.

Witam w osiemdziesiątym pierwszym odcinku podcastu „Porozmawiajmy o IT”. Tematem dzisiejszej rozmowy jest data center w czasie pandemii.Partnerem cyklu jest Atman, dostawca usług IT dla biznesu w modelu outsourcingu.Dziś moim gościem jest Adam Dzielnicki – od prawie 20 lat ułatwia biznesowi korzystanie z nowoczesnych usług ICT. Sprawia, że zaawansowane technologie stają się proste do zrozumienia i łatwe do sprzedaży. Obecnie rozwija produkty data center i SD-WAN w Atmanie.W tym odcinku o data center w czasie pandemii rozmawiamy w następujących kontekstach:z czego składają się nowoczesne data center?czym jest i jak jest realizowana redundancja?co uwzględnia się planując i zarządzając centrum danych?z czego wynikają przestoje w działaniu data center? jak duży jest to problem?czy branża ma wypracowane standardy by sobie radzić z takimi problemami?jakie obszary obejmuje standard DCOS?jakie inne standardy czy dobre praktyki oprócz EPI-DCOS można jeszcze spotkać?jak sytuacja z COVID-19 wpłynęła na firmy świadczący usługi dostępu do danych?jak zmieniło się działanie centrów danych?czy zmiany wprowadzone lub wymuszone przez pandemię będą stałe?Subskrypcja podcastu:zasubskrybuj w Apple Podcasts, Google Podcasts, Spreaker, Sticher, Spotify, przez RSS, lub Twoją ulubioną aplikację do podcastów na smartphonie (wyszukaj frazę „Porozmawiajmy o IT”)poproszę Cię też o polubienie fanpage na FacebookuLinki:Atman – https://www.atman.pl/Profil na LinkedIn – https://www.linkedin.com/in/adamdzielnicki/Wsparcie:Wesprzyj podcast na platformie Patronite - https://patronite.pl/porozmawiajmyoit/Jeśli masz jakieś pytania lub komentarze, pisz do mnie śmiało na krzysztof@porozmawiajmyoit.pl https://porozmawiajmyoit.pl/81

The conversation covers:  An overview of Ravi's role as an evangelist — an often misunderstood, but important technology enabler.  Balancing organizational versus individual needs when making decisions. Some of the core motivations that are driving cloud native migrations today.  Why Ravi believes it in empowering engineers to make business decisions.  Some of the top misconceptions about cloud native. Ravi also provides his own definition of cloud native. How cloud native architectures are forcing developers to “shift left.” Links https://harness.io/ Twitter: https://twitter.com/ravilach Harness community: https://community.harness.io/ Harness Slack: https://harnesscommunity.slack.com/ TranscriptEmily: Hi everyone. I'm Emily Omier, your host, and my day job is helping companies position themselves in the cloud-native ecosystem so that their product's value is obvious to end-users. I started this podcast because organizations embark on the cloud naive journey for business reasons, but in general, the industry doesn't talk about them. Instead, we talk a lot about technical reasons. I'm hoping that with this podcast, we focus more on the business goals and business motivations that lead organizations to adopt cloud-native and Kubernetes. I hope you'll join me.Welcome to The Business of Cloud Native, I am your host Emily Omier. And today I'm chatting with Ravi Lachhman. Ravi, I want to always start out with, first of all, saying thank you—Ravi: Sure, excited to be here.Emily: —and second of all, I like to have you introduce yourself, in your own words. What do you do? Where do you work?Ravi: Yes, sure. I'm an evangelist for Harness. So, what an evangelist does, I focus on the ecosystem, and I always like the joke, I marry people with software because when people think of evangelists, they think of a televangelist. Or at least that's what I told my mother and she believes me still. I focus on the ecosystem Harness plays in. And so, Harness is a continuous delivery as a service company. So, what that means, all of the confidence-building steps that you need to get software into production, such as approvals, test orchestration, Harness, how to do that with lots of convention, and as a service.Emily: So, when you start your day, walk me through what you're actually doing on a typical day?Ravi: a typical day—dude, I wish there was a typical day because we wear so many hats as a start-up here, but kind of a typical day for me and a typical day for my team, I ended up reading a lot. I probably read about two hours a day, at least during the business day. Now, for some people that might not be a lot, but for me, that's a lot. So, I'll usually catch up with a lot of technology news and news in general. They kind of see how certain things are playing out. So, a big fan of The New Stack big fan of InfoQ. I also like reading Hacker News for more emotional reading. The big orange angry site, I call Hacker News. And then really just interacting with the community and teams at large. So, I'm the person I used to make fun of, you know, quote-unquote, “thought leader.” I used to not understand what they do, then I became one that was like, “Oh, boy.” [laughs]. And so just providing guidance for some of our field teams, some of the marketing teams around the cloud-native ecosystem, what I'm seeing, what I'm hearing, my opinion on it. And that's pretty much it. And I get to do fun stuff like this, talking on podcasts, always excited to talk to folks and talk to the public. And then kind of just a mix of, say, making some sort of demos, or writing scaffolding code, just exploring new technologies. I'm pretty fortunate in my day to day activities.Emily: And tell me a little bit more about marrying people with software. Are you the matchmaker? Are you the priest, what role?Ravi: I can play all parts of the marrying lifecycle. Sometimes I'm the groom, sometimes I'm the priest. But I'm really helping folks make technical decisions. So, it's go a joke because I get the opportunity to take a look at a wide swath of technology. And so just helping folks make technical decisions. Oh, is this new technology hot? Does this technology make sense? Does this project fatality? What do you think? I just play, kind of, masters of ceremony on folks who are making technology decisions.Emily: What are some common decisions that you help people with, and common questions that they have?Ravi: Lot of times it comes around common questions about technology. It's always finding rationale. Why are you leveraging a certain piece of technology? The ‘why' question is always important. Let's say that you're a forward-thinking engineer or a forward-thinking technology leader. They also read a lot, and so if they come across, let's say a new hot technology, or if they're on Twitter, seeing, yeah, this particular project's getting a lot of retweets, or they go in GitHub and see oh, this project has little stars, or forks. What does that mean? So, part of my role when talking to people is actually to kind of help slow that roll down, saying, “Hey, what's the business rationale behind you making a change? Why do you actually want to go about leveraging a certain, let's say, technology?” I'm just taking more of a generic approach, saying, “Hey, what's the shiny penny today might not be the shiny penny tomorrow.” And also just providing some sort of guidance like, “Hey, let's take a look at project vitality. Let's take a look at some other metrics that projects have, like defect close ratio—you know, how often it's updates happening, what's your security posture?” And so just walking through a more, I would say the non-fun tasks or non-functional tasks, and also looking about how to operationalize something like, “Hey, given you want to make sure you're maintaining innovation, and making sure that you're maintaining business controls, what are some best operational practices?” You know, want to go for gold, or don't boil the ocean, it's helping people make decisive decisions.Emily: What do you see as sort of the common threads that connect to the conversations that you have?Ravi: Yeah, so I think a lot of the common threads are usually like people say, “Oh, we have to have it. We're going to fall behind if you don't use XYZ technology.” And when you really start getting to talking to them, it's like, let's try to line up some sort of technical debt or business problem that you have, and how about are you going to solve these particular technical challenges? It's something that, of the space I play into, which is ironic, it's the double-edged sword, I call it ‘chasing conference tech.' So, sometimes people see a really hot project, if my team implements this, I can go speak at a conference about a certain piece of technology. And it's like, eh, is that a really rational reason? Maybe. It kind of goes into taking the conversation slightly somewhere else. One of the biggest challenges I think, let's say if you're kind of climbing the engineering ranks—and this is something that I had to do as I went from a junior to a staff to a principal engineer in my roles—with that it's always having some sort of portfolio. So, if you speak at a conference, you have a portfolio, people can Google your name, funny pictures of you are not the only things that come up, but some sort of technical knowledge, and sometimes that's what people are chasing. So, it's really trying to have to balance that emotional decision with what's best for the firm, what's best for you, and just what's best for the team.Emily: That's actually a really interesting question is sometimes what's best for the individual engineer is not what's best for the organization. And when I say individual engineer, maybe it's not one individual, but five, or the team. How do you sort of help piece together and help people understand here's the business reason, that's organization-wide, but here's my personal motivation, and how do I reconcile these, and is there a way even to get both?Ravi: There actually is a way to get both. I call it the 75/25 percent rule. And let's take all the experience away from the engineers, to start with a blank slate. It has to do with the organization. An organization needs to set up engineers to be successful in being innovative. And so if we take the timeline or the scale all the way back to hiring, so when I like to hire folks, I always like to look at—my ratio is a little bit different than 75/25. I'm more of a 50/50. You bring 50 percent of the skills, and you'll learn 50 percent of the skills, versus more conservative organizations would say, “You know what? You have 75 percent of the skills, if you can learn 25 percent of the skills, this job would be interesting to you.” Versus if you have to learn 80 percent, it's going to be frustrating for the individual. And so having that kind of leeway to make decisions, and also knowing that technical change can take a lot of time, I think, as an engineer, as an engineer—as talking software engineering professions as a whole, how do you build your value? So, your value is usually calculated in two parts. It's calculated in your business domain experience and your technical skills. And so when you go project to project—and this is what might be more of, hey, if you're facing too big of a climb, you'll usually change roles. Nobody is in their position for a decade. Gone are the days that you're a lifetime engineer on one project or one product. It's kind of a given that you'll change around that because you're building your repertoire in two places: you're building domain experience, and you're building technical experience. And so knowing when to pick your battles, as cliche as that sounds, oh, you know what, this particular technology, this shiny penny came out. I seen a lot of it when Kubernetes came out, like, “Oh, we have to have it.” But—or even a lot of the cloud-native and container-based and all the ‘et cetera accessories' as I call it, as those projects get steam surrounding it. It's, “We have to have it.” It's like, eh. It's good for resume building, but there's your things to do on your own also to learn it. I think we live in a day of open source. And so as an engineer, if I want to learn a new skill, I don't necessarily have to wait for my organization to implement it. I could go and play, something like Katacoda, I can go do things on my own, I can learn and then say, “You know what, this is a good fit. I can make a bigger play to help implement it in the organization than just me wanting to learn it.” Because a lot of the learning is free these days, which I think it's amazing. I know that was a long-winded answer. But I think you can kind of quench the thirst of knowledge with playing it on your own, and that if it makes sense, you can make a much better case to the business or to technology leadership to make change.Emily: And what do you think the core business motivations are for most of the organizations that you end up talking to?Ravi: Yeah, [unintelligible] core motivation to leveraging cloud-native technology, it really depends on organization to organization. I'm pretty fortunate that I get to span, I think, a wide swath of organization—so from startups to pretty established enterprises—I kind of talk about the pretty established enterprises. A lot of the business justification, it might not be a technical justification, but there's a pseudo technical business reason, a lot of times, though, I when I talk to folks, they're big concern is portability. And so, like, hey, if you take a look at the dollar and cents rationale behind certain things, the big play there is portability. So, if you're leveraging—we can get into the definition of what cloud-native resources are, but a big draw to that is being portable—and so, hopefully, you're not tied down to a single provider, or single purveyor, and you have the ability to move. Now, that also ties into agility. Supposedly, if you're able to use ubiquitous hardware or semi-ubiquitous software, you were able to move a little bit faster. But again, what I usually see is folk's main concern is portability. And then also with that is [unintelligible] up against scale. And so as—looking at ways of reducing resources, if you could use generics, you're able to shop around a little bit better, either internally or externally, and help provide scale for a softer or lesser cost.Emily: And how frequently do you think the engineers that you talked to are aware of those core business motivations?Ravi: Hmm, it really depends on—I'm always giving you the ‘depends' answer because talking to a wide swath of folks—where I see there's more emotion involved in a good way if there's closer alignment to the business—which is something hard to do. I think it is slowly eroding and chipping away. I've definitely seen this during my career. It's the old stodgy business first technology argument, right. Like, modern teams, they're very well [unintelligible] together. So, it's not a us versus them or cat versus dog argument, “Oh, why do these engineers want to take their sweet time?” versus, “Why does the business want us to act so fast?” So, having the engineers empowered to make decisions, and have them looked at instead of being a cost center, as the center of innovation is fairly key. And so having that type of rationale, like, hey, allowing the engineers to give input into feature development, even requirement development is something I've seen changed throughout my career. It used to be a very special thing to do requirements building, versus most of the projects that I've worked on now—as an engineer, we're very, very well attuned to the requirements with the business.Emily: Do you think there's anything that gets lost in translation?Ravi: Oh, absolutely. As people, we're emotional. And so if we're all sum total of our experiences—so let's say if someone asked, Emily, you and I a question, we would probably have four different answers for that person, just because maybe we have differences in opinions, differences of sum totals of experience. And I might say, “Hey, try this or this,” and then you might say, “Try that or that.” So, it really depends. Being lost in translation is always—it's been a fundamental problem in requirements gathering and it's continued to be a fundamental problem. I think just taking that question a step further, is how you go about combating that? I think having very shortened feedback cycles are very important. So, if you have to make any sort of adjustments, gone are the days I think when I started my career, waterfall was becoming unpopular, but the first project or two I was on was very waterfall-ish just because of the size of the project we worked on, we had to agree on lots of things; we were building something for six months. Versus, if you look at today, modern development methodologies like Agile, or Scaled Agile, a lot of the feedback happens pretty regularly, which can be exhausting, but decisions are made all the time.Emily: Do you think in addition to mistranslations, do you think there are any misconceptions? And I'm talking about sort of on both sides of this equation, you know, business leaders or business motivations, and then also technologists, and let's refocus back to talk about cloud-native in particular. What sort of misconceptions do you think are sort of floating out there about cloud-native and what it means?Ravi: Yeah, so what cloud-native means—it means something different to everybody. So, you listen to your podcasts for a couple episodes, if you asked any one of the guests the question, we all would give you a different answer. So, in my definition of cloud-native—and then I'll get back to what some of the misconceptions are—I have a very basic definition: cloud-native means two pillars. It means your architecture, or your platform needs to be ephemeral, and it needs to be [indibited]. So, it needs to be able to be short-lived, and be consistent, which are two things that are at odds with each other. But if you kind of talk to folks that, hey, they might be a little more slighted towards the business, they have this idea that cloud-native will solve all your problems. So, it reminds me a lot of big data back in the day. “Oh, if you have a Hadoop cluster, it will solve all of our logistics and shipping problems.” No. That's the technology. If you have Kubernetes, it will solve all of our problems. No. That's the technology. It's just a conduit of helping you make changes. And so just making sure that understand that hey, cloud-native doesn't mean that you get the checkmark that, “Oh, you know what? We're stable. We're robust. We can scale by using all cloud-native technologies,” because cloud-native technologies are actually quite complicated. If you're introducing a lot of complexity to your architecture, does it make sense? Does that make sense? Does it give you the value you're looking for? Because at the end of the day, and this is kind of something, the older I get, the more I believe it, is that your customers don't care how you did something; they care what the result is. So, if your web application's up, they don't care if you're running a simple LAMP stack, they just care that the application is up, versus using the latest Kubernetes stack, but using some sort of cloud-native NoSQL database, and we're using [Istio], and we're using, pick your flavor du jour of cloud-native technology, your end customer actually doesn't care how you did it. They care what happened.Emily: We can talk about misconceptions that other people have, but is there anything that continues to surprise you?Ravi: Yeah, I think the biggest misconception is that there's very limited choice. And so I'll play devil's advocate, I think the CNCF, the Cloud Native Computing Foundation, there's lots of projects, I've seen the CNCF, they have something called the CNCF Landscape, and I seen it grow from 200 cards, it was 1200 cards at KubeCon, I guess, end of last year in San Diego, and it's hovering around 1500 cards. So, these cards means there's projects or vendors that play in this space. Having that much choice—this is usually surprising to people because they—if you're thinking of cloud-native, it's like saying Kleenex today, and you think of Kubernetes or other auxiliary product or project that surrounds that. And a lot of misconception would be it's helping solve for complexity. It's the quintessential computer science argument. All you do in computer science is move complexity around like an abacus. We move it left to right. We're just shifting it around, and so by leveraging certain technologies there's a lot of complication, a lot of burden that's brought in. For example, if you want to leverage, let's say, a service Istio, Istio will not solve all your networking problems. In fact, it's going to introduce a whole set of problems. And I could talk about my biggest outage, and one of the things I see with cloud-native is a lot of skills are getting shifted left because you're codifying areas that were not codified before. But that's something I would love to talk about.Emily: Tell me about your biggest outage that sounds interesting.Ravi: Yeah, I didn't know how it would manifest itself. It's ways, I think, until, like, years later that I didn't have the aha moment. I used to think it was me, it probably still is me, but—so the year was 2013, and I was working for a client, and we were—it's actually a large news site—and so we were in the midst of modernizing their application, or their streaming application. And so I was one of the first applications to actually go to AWS. And so my background is in Java, so I have a Java software engineer or J2ED or JEE engineer, and having to start working more in infrastructure was kind of a new thing, so I was very fortunate up until 2013-ish up until this point that I didn't really touch the infrastructure. I was immune to that. And now being more, kind of becoming a more senior engineer was in charge of the infrastructure for the application—which is kind of odd—but what ended up happening that—this is going to be kind of funny—since I was one of the first teams to go to AWS, the networking team wouldn't touch the configurations. So, when we were testing things, and [unintelligible] environments, we had our VPC CIDR rules—so the traffic rules—wide open. And then as we were going into production, there were rules that we had to limit traffic due to a CIDR so up until 2013, I thought a C-I-D-R like a CIDR was something you drink. I was like, “What? Like apple cider?” So, this shows you how much I know. So, basically, I had to configure the VPC or Virtual Private Cloud networking rules. Finally, when we deployed the application, unknowing to myself, CIDR calculation is a significant digit calculation. So, the larger the number you divide by, the more IPs you let in. And so instead of dividing by 16, I divided by 8. I was like, “Oh, you'll have a bigger number if you divide by a smaller number.” I end up cutting off half the traffic of the internet when we deployed to production. So, that was a very not smooth way of doing something. But how did this manifest itself? So, the experts, who would have been the networking team, refused to look at my configuration because it was a public cloud. “Nope, you don't have a slot in our data center, we look at it.” And poor me, as a JEE or J2EE engineer, I had very little experience networking. Now, if you fast forward to what this means today, a lot of the cloud-native stack, are again, slicing and dicing these CNCF cards, a lot of this, you're exposing different, let's say verticals or dimensions to engineers that they haven't really seen before. A lot of its networking related a lot of it can be storage related. And so, as a software engineer, these are verticals that I'd never had to deal with before. Now, it's kind of ironic that in 2020, hey, yes, you will be dealing with certain configurations because, hey, it's code. So, it's shifting the burden left towards the developer that, “Oh, you know what, you know networking—” or, “You do need to know your app, so here's some Istio rules that you need to include in your packaging of your application.” Which folks might scratch your head. So, yeah, again, it's like shifting complexity away from folks that have traditional expertise towards the developer. Now, times are changing. I seen a lot of this in years gone by, “Oh, no. These are pieces of code. We don't want to touch it.” Being more traditional or legacy operations team, versus today, everybody—it's kind of the merging of the two worlds. The going joke is all developers are becoming infrastructure engineers, and infrastructure engineers are becoming software engineers. So, it's the perfect blend of two worlds coming together.Emily: That's interesting. And I now think I understand what you mean by skills shifting left. Developers have to know more, and more, and more. But I'm also curious, there's also people who talk about how Kubernetes, one of its failures is that it forces this shift left of skills and that the ideal world is that developers don't need to interact with it at all. That's just a platform team. What do you think about that?Ravi: These are awesome questions. These are things I'm very passionate about. I definitely seen the evolution. So, I've been pretty fortunate that I was jumping on the application infrastructure shift around 2014, 2015, so right when Kubernetes was coming of age. So, most of my background was in distributed systems. So, I'm making very large distributed Java applications. And so when Kubernetes came out, the teams that I worked on, the applications that were deployed to Kubernetes were actually owned by the app dev team. The infrastructure team wouldn't even touch the Kubernetes cluster. It was like, “Oh, this is a development tool. This is not a platform tool.” The platform teams that I were interacting with 2015, 2016, as Kubernetes became more popular than ever, they were the legacy—well, hate to say legacy because it's kind of my background too—they were the remaining middleware engineers. We maintained a web server cluster, we maintained the message broker cluster, we maintained XYZ distributed Java infrastructure cluster. And so when looking at a tool like Kubernetes, or even there were different platforming services, so the paths I've leveraged early, or mid-2010s was Red Hat OpenShift, before and after the Kubernetes migration inside of OpenShift. And so looking at a different—how teams are set up, it used to be, “Oh, this is an app dev item. This is what houses your application.” Versus today, because the workloads are so critical that are going on to say platforms such as Kubernetes, it was that you really need that system engineering bubble of expertise. You really need those platform engineers to understand how to best scale, how to best purvey, and maintain a platform like Kubernetes. Also, one of the odd things are—going back to your point, Emily, like, hey, why things were tossed over either to the development team or going back to a developing software engineer myself, do we care what the end system is?So, it used to be, I'll talk about Java-land here for a minute, give you kind of long-winded answer of back in Java land, we really used to care about the target system, not necessarily for an application that have one node, but if we had to develop a clustered application. So, we have more than one node talking to each other, or a stateful application, we really had start developing to a specific target system. Okay, I know how JBoss WildFly clusters or I know how IBM WebSphere or WebLogic clusters. And so when we're designing our applications, we had to make sure that we play well into those clustering mechanisms. With Kubernetes, since it's generic, you don't necessarily have to play into those clustering mechanisms because there's a basic understanding. But that's been the biggest Achilles heel in Kubernetes. It wasn't designed for those type of workloads, stateful workloads that don't like dying very often. That's kind of been the push or pull. It's just a tool, there's a lot of generic, so you can assume that the target platform will handle a certain way. And you're slowly start backing off the case that you're building to a specific target platform. But as Kubernetes has evolved, especially with the operator framework, you actually are starting to build to Kubernetes in 2018, 2019, 2020.Emily: It actually brought up a question for me that, at risk of sounding naive myself, I feel like I never meet anybody who introduces themselves as a platform engineer. I meet all these developers, everyone's a developer evangelist, for example, or their background is as a developer, I feel like maybe once or twice, someone has introduced themselves as, “I'm a platform engineer,” or, “I'm an operations specialist.” I mean, is that just me? Is that a real thing?Ravi: They're very real jobs. I think… it's like saying DevOps engineer, it means something else to who you talk to you. So, I'll harp on, like ‘platform engineer.' so kind of like, the evolution of the platform engineer, if you would have talked to me in 2013, 2014, “Hey, I'm a platform engineer,” I would think that you're a software engineer focused on platform tools. Like, “Hey, I focus on authentication, authorization.” You're building—let's say we had a dozen people on this call and we're working for Acme Incorporated, there's modules that transcend every one of our teams. Let's say logging, or let's say login, or let's say, some sort of look and feel. So, the platform engineer or the platform engineering development focused platform engineering team would make common reusable modules throughout. Now, with the great rise of platforms as a service, like PCF, and OpenShift, and DCOS, they became kind of like a shift. The middleware engineers that were maintaining the message broker clusters, maintaining your web application server clusters, they're kind of shifting towards one of those platforms. Even today, Kubernetes, pick your provider du jour of Kubernetes. And so those are where the platform engineers are today. “Hey, I'm a platform engineer. I focus on OpenShift and Kubernetes.” Usually, they're very vertically focused on one or more specific platforms. And operations folks can ride very big gamut. Usually, if you put, “operations” in quotes, usually they're systems or infrastructure engineers that are very focused on the infrastructure where the platform's run.Emily: I'm obviously a words person, and it just seems like there's this vocabulary issue where everybody knows what a developer is, and so it's easy to say, “Oh, I'm a developer.” But then everything else that's related to engineering, there's not quite as much specificity, precisely because you said everybody has a slightly different understanding. It's kind of interesting.Ravi: Yeah, it's like, I think as a engineer, we're not one for titles. So, I think a engineer is a engineer. I think if you asked most engineers, it's like, “Yeah, I'm a engineer.” It's so funny, a good example of that is Tim Berners-Lee, the person who created WWW, the World Wide Web. If you looked at his LinkedIn, he just says he's a web developer. And he invented WWW. So, usually engineering-level folks, you're not—at least for myself—is not one for title.Emily: The example that you gave regarding the biggest outage of your career was basically a skills problem. Do you think that there's still a skills or knowledge issue in the cloud-native world?Ravi: Oh, absolutely. We work for incentivization. You know, my mortgage is with PNC, and they require a payment every month, unfortunately. So, I do work for an employer. Incentivization is key. So, kind of resume chasing, conference chasing there's been some of that in the cloud-native world, but what ends up happening more often than not is that we're continuously shifting left. A talk I like to give is called, “The Engineering Burden is on the Rise.” And taking a look at what, let's say, a software engineer was required to do in 2010 versus what a software engineer is required to do today in 2020. And there's a lot more burden in infrastructure that, as a software engineer you didn't have to deal with. Now, this has to do with two things, or actually one particular movement. There's a movie company, or a video company in Los Gatos, California, and there's a book company in South Lake Union in Seattle. And so these two particular companies given the rise of what's called a full lifecycle developer. Basically, if you run it, or if you operate—you operate what you run, or if you write it, you run it. So, that means that if you write a piece of code, you're in charge of the operations. You have support, you're in charge of the SLAs, SLOs, SLIs. You're ultimately responsible if a customer has a problem. And can you imagine the number of people, the amount of skill set that requires? There's this concept of a T-shaped skill that you have to have experience in so many different platforms, that it becomes a very big burden. As an engineer, I don't envy anybody entering a team that's leveraging a lot of cloud-native technology because most likely a lot of that onus will fall on the software engineer to create the deployable, to create how you build it, to fly [unintelligible] in your CI stack, write the configuration that builds it, write the configuration deploys it, write the networking rules, write how you test it, write the login interceptors. So, there's a lot going on.Emily: Is there anything else that you want to add about your experience with cloud-native that I haven't really thought to ask, yet?Ravi: It's not all doom and gloom. I'm very positive on cloud-native technologies. I think it's a great equalizer. You're kind of going back—this might be a more intrinsic, like a 30-second answer here. If you taking back that I wanted to learn certain skills in 2010, I basically had to be working for a firm. So, 2010, I was working for IBM. So, there's certain distributed Java problems I wanted to solve. I basically had to be working for a firm because the software licensing costs were so expensive, and that technology wasn't very democratized. Looking at cloud-native technology today, there's a big, big push for open source, which open source is R&D methodology. That's what open source is, it helps alleviate some sort of acquisition—but not necessarily adoption—problems. And you can learn a lot. Hey, you could pick up any project and just try to learn, try to run it. Pick up these particular distributed system skills that were very guarded, I would say, a decade ago, it's being opened up to the masses. And so there's a lot to drink from, but you can drink as much as you want from the CNCF or the cloud-native garden hose.Emily: Do you have a software engineering tool that you cannot live without?Ravi: Recently, because I deal in a lot of YAML, I need a YAML linter. So, YAML is a space-separated language. As a human, I can't tell you what spaces are. Like, you know, if you have three spaces, and the next line you have four spaces. So, I use a YAML linter. It puts periods for me, so I can count them because it's been multiple times that my demo is not syntactically correct because I missed a space and I can't see it on my screen.Emily: And how can listeners connect with you?Ravi: Oh, yeah. You can hit me up on Twitter @ravilach, R-A-V-I-L-A-C-H. Or come visit us at Harness at www.harness.io. I run the Harness community, so community.harness.io. We have a Slack channel and a Discourse, and always excited to interact with people.Emily: Thanks for listening. I hope you've learned just a little bit more about the business of cloud-native. If you'd like to connect with me or learn more about my positioning services, look me up on LinkedIn: I'm Emily Omier, that's O-M-I-E-R, or visit my website which is emilyomier.com. Thank you, and until next time.Announcer: This has been a HumblePod production. Stay humble.

Will the Government's much vaunted radical reforms to the planning system allow Development Consent Orders (DCOs) to apply to large-scale, residential-led development proposals? It is an idea that has been around since DCOs, as wells as NPSs and NSIPs, were introduced by the Planning Act 2008, but perhaps now it's time has come. As well as considering the efficacy of the DCO regime as it relates to infrastructure projects, an expanded DCO regime is considered in a report by Barton Willmore, Copper, Womble Bond Dickinson and Hannah Hickman. Sam Stafford discusses the report (link below) in this episode with co-authors Tom Carpen (Barton Willmore), Kevin Gibbs (Womble Bond Dickinson) and Hannah Hickman (Hannah Hickman Consulting). LinkedIn profiles: Tom - https://www.linkedin.com/in/tom-carpen-7102578b/ Kevin - https://www.linkedin.com/in/kevin-gibbs-24a39734/ Hannah - https://www.linkedin.com/in/hannahhickman1/ Some accompanying reading. ‘Can development consent orders help meet the challenges of our time?' by Barton Willmore, Copper, Womble Bond Dickinson and Hannah Hickman: http://www.bartonwillmore.co.uk/Knowledge/Intelligence/2020/Can-Development-Consent-Orders-help-meet-the-chall 'Housing - Nationally Significant Infrastructure?' commissioned by Bond Dickinson and Quod: https://www.quod.com/news/housing-crisis-demands-central-government-intervention/ 'Unlocking Britain' by the Social Market Foundation: https://www.smf.co.uk/publications/unlocking-britain/#:~:text=In%20a%20guest%20publication%20for%20the%20Social%20Market,recover%20and%20prosper%20in%20the%20wake%20of%20COVID-19. 'Following Orders: five actions necessary for DCOs and the NSIP regime to be used for large-scale housing' by Lichfields: https://lichfields.uk/blog/2020/july/7/following-orders-the-five-actions-necessary-for-dcos-and-the-nsip-regime-to-be-used-for-large-scale-housing/ 'The New Towns Question (Again)' by Simon Ricketts: https://simonicity.com/2020/07/11/the-new-towns-question-again/ Some accompanying viewing. The best of Jerry Springer's Final Thoughts: https://www.dailymotion.com/video/x3iobgi

In this episode, we discuss the decision making process a team typically goes through when adding a new technology to their stack. We use Kubernetes and DCOS implementations as examples to answer the age old question: To tool or not to tool?

This week in TNS, D2IQ co-founder Tobi Knaup wrote about the growing problem of container sprawl, a by product of more companies running containers in production, and as a result, there is a loss of efficiency on the part of the DevOps teams managing them. https://thenewstack.io/container-sprawl-is-the-new-vm-sprawl/ In this episode, we will speak with Ben Hindman, D2IQ co-founder, and CTO, about this issue of container sprawl, and how it hampers “Day 2 Operations” as D2IQ (formerly Mesosphere) calls it. We also will discuss the company's recent Cloud Native Virtual Summit, its recently released KUDO tool https://thenewstack.io/kudo-automates-kubernetes-operators/ , the 6th Anniversary of Kubernetes, and the latest on Mesosphere and the DCOS. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS Senior Editor Richard MacManus, and TNS Managing Editor Joab Jackson.

This week in TNS, D2IQ co-founder Tobi Knaup wrote about the growing problem of container sprawl, a by product of more companies running containers in production, and as a result, there is a loss of efficiency on the part of the DevOps teams managing them. https://thenewstack.io/container-sprawl-is-the-new-vm-sprawl/ In this episode, we will speak with Ben Hindman, D2IQ co-founder, and CTO, about this issue of container sprawl, and how it hampers “Day 2 Operations” as D2IQ (formerly Mesosphere) calls it. We also will discuss the company's recent Cloud Native Virtual Summit, its recently released KUDO tool https://thenewstack.io/kudo-automates-kubernetes-operators/ , the 6th Anniversary of Kubernetes, and the latest on Mesosphere and the DCOS. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS Senior Editor Richard MacManus, and TNS Managing Editor Joab Jackson.

This episode features two of our Doping Control state managers John Rhodes (Victoria) and Alissa Ready (Queensland). John and Alisa commenced their newly created roles in July to be a conduit between the Canberra office, regional staff and sports. John, who has a background in anti-corruption, says the perception of ASADA of the past has been “misrepresented” and is happy to see this perception has changed in recent times. Alisa agreed. She said that ASADA was seen as the “bad guy” but is much more athlete-centric now, helping athletes to comply with the rules. “The DCO and chaperones are going out and really trying to engage with athletes and the [sporting] organisations and trying to educate them, while waiting for athletes to produce a sample,” she said. “DCOs and chaperones play a key education role, they educate athletes about supplements, medications; it’s about helping athletes and enabling them.” John added: “The professional standing of our operators in the field is really first class.” In the “So I was wondering…” segment, our Director of Legal answers a question from the public, this week it’s “What is prohibited association?”

#Oscillatorsync is a feature in some synthesizers with two or more VCOs, DCOs, or "virtual" oscillators. As one oscillator finishes a cycle, it resets the period of another oscillator, forcing the latter to have the same base frequency. This can produce a harmonically rich sound, the timbre of which can be altered by varying the synced oscillator's frequency. A synced oscillator that resets other oscillator(s) is called the master; the oscillators which it resets are called slaves. There are two common forms of oscillator sync which appear on synthesizers: Hard Sync and Soft Sync. According to Sound on Sound journalist Gordon Reid, oscillator sync is the least understood feature for many users of a synthesizer.[1] Hard Sync The master oscillator's pitch is generated by user input (typically the synthesizer's keyboard), and is arbitrary. The slave oscillator's pitch may be tuned to (or detuned from) this frequency, or may remain constant. Every time the master oscillator's cycle repeats, the slave is retriggered, regardless of its position. If the slave is tuned to a lower frequency than the master it will be forced to repeat before it completes an entire cycle, and if it is tuned to a higher frequency it will be forced to repeat partway through a second or third cycle. This technique ensures that the oscillators are technically playing at the same frequency, but the irregular cycle of the slave oscillator often causes complex timbres and the impression of harmony. If the tuning of the slave oscillator is swept, one may discern a harmonic sequence[2]. This effect may be achieved by measuring the zero axis crossings of the master oscillator and retriggering the slave oscillator after every other crossing. This form of oscillator sync is more common than soft sync, but is prone to generating aliasing in naive digital implementations. Soft Sync There are several other kinds of sync which may also be called Soft Sync. In a Hard Sync setup, the slave oscillator is forced to reset to some level and phase (for example, zero) with every cycle of the master regardless of position or direction of the slave waveform, which often generates asymmetrical shapes. In some cases,[3][4] Soft Sync refers to a process intended to nudge and lock the slave oscillator into the same or an integer or fractional multiple of the master oscillator frequency when they both have similar phases, similar to a phase-locked loop. In electronics, ring modulation is a signal processing function, an implementation of frequency mixing, performed by creating multiple frequencies from those of the two signals, where one is typically a sine wave or another simple waveform and the other is the signal to be modulated. A ring modulator is an electronic device for ring modulation. A ring modulator may be used in music synthesizers and as an effects unit. weki --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/vegansteven/message

Matt is a Doping Control Officer (DCO) with Drug Free Sport international, and he shares a candid account of what it's like to be a DCO. He discusses unexpected occurrences during doping control missions, the behind-the-scenes roles and responsibilities of DCOs working in the field, the rigorous training process required to become a DCO, the variety of challenges he faces in collecting and protecting the integrity of samples, improvements in doping control processes and technology over time, and more!

Cuántas veces hemos oído en mi ordenador funciona, y cuántas veces hemos necesitado crear una maquina virtual para probar nuestro sistema en un entorno concreto. Si trabajas con Windows o Mac, el vetusto VirtualBox será parte de tu kit de instalación básico. Pero de un desde hace algunos años una nueva tecnología que supuestamente reemplaza la virtualización está de moda Docker. Todo suena a nuevo pero a la vez todo te resulta extrañamente familiar. En este episodio intentaremos explicar qué es un contenedor, qué es docker y porque está cambiando nuestra forma de desarrollar.¿Qué son los contenedores?Algo que parece realmente nuevo lleva bastante tiempo en nuestro kernels. Lo que hace más interesante la historia de porque esta tecnología se ha puesto de moda últimamente. Nuestro objetivo es intentar explicar qué es un contenedor, en qué se diferencia de un máquina virtual y porque debemos usarlos.CoreOS vs DockerAunque desde fuera las comunidades open source pareces grandes hermandades donde todo es paz y amor. Los que realmente han participado en este tipo de comunidades sabrán que manejar los egos y los intereses es una parte importante del trabajo de gestionar una comunidad. La comunidad de Docker sufrió esto y produjo un cisma entre la comunidad de desarrolladores lo que dio lugar a nuevo proyecto CoreOS.DC/OS, Kubernetes, Swarm..Lanzar un contenedor no asegura que este vaya a estar corriendo. Es necesario de alguna forma añadir una capa de gestión que se encargue de la gestión del ciclo de vida de los contenedores. Para eso existen soluciones como Docker Compose. Pero si además queremos que esos contenedores estén en diferentes máquinas, que podamos replicarlos o que podamos mantener el estado, necesitamos algo más complejo, como Kubernetes o DC/OS.Y para terminar, algunas referencias en orden aleatoriohttps://medium.freecodecamp.org/a-beginner-friendly-introduction-to-containers-vms-and-docker-79a9e3e119bhttps://www.upguard.com/articles/docker-vs-coreoshttps://www.forbes.com/sites/benkepes/2015/06/24/the-container-format-wars-are-over-docker-won-but-coreos-didnt-necessarily-lose/#7b67fe8c2e05https://coreos.com/blog/rocket.htmlhttps://docsmicrosoft.com/en-us/azure/aks/https://aws.amazon.com/ecs/https://cloud.google.com/kubernetes-engine/

Vidéo sur le pardon : https://youtu.be/RDsnFj3B0zk - - - -

Olaf Molenveld is the CTO and Co-Founder of Vamp (vamp.io). Their mission is to make it easier for companies to do things like canary releases and AB-testing. They couple Vamp with already existing platforms like Kubernetes and DCOS. Enjoyed this podcast? Be sure to check out the podcast with Murat Özmerd from Flow.ai.

Olaf Molenveld is the CTO and Co-Founder of Vamp (https://vamp.io). Their mission is to make it easier for companies to do things like canary releases and AB-testing. They couple Vamp with already existing platforms like Kubernetes and DCOS.

In another dynamic chat with Michael Hauselblas (@mhausenblas), a self-described Distributed Systems Jester, who is also a Developer and Cloud Advocate for Mesosphere.   Michael brings a very interesting background to the field, and we are able to touch on some very interesting topics in the open source product development lifecycle as a result.  I hope that you enjoy the chat as much as I did being a part of it. 

Aaron talks with Ben Hindman (@benh; Co-creator of ApacheMesos, Founder of @mesosphere) about his time at Twitter, building Mesos, understanding problems at scale, how Mesos compares to Kubernetes, Mesosphere DCOS and the recent announcements with Microsoft. Interested in growing your career and networking with professionals in the Data Center and Cloud industry? Attend John Troyer's The Reckoning event, in Half Moon Bay, CA on September 13-14. Cloudcast listeners can get $100 discount by entering promo-code: CLOUDCAST. Interested in the O'Reilly Velocity NYC? Want a chance at a free pass for VelocityConf NYC? Send us your interesting journey in Web-Scale Operations to show@thecloudcast.net by Friday July 10th and we'll pick a winner! Want to register for Velocity Conference now? Use promo code 20CLOUD for 20% off Check out the Velocity Schedule Free eBook from O'Reilly Media for Cloudcast Listeners! Links from the show: Dave Lester from Twitter/ApacheMesos on #155 Understanding Mesos Kenneth Hui’s Series on Apache Mesos Microsoft / MesoSphere Announcement Thanks for the MesosCon folks for having us! - MesosCon Homepage Topic 1 - Give us some of your background and how you went from working on Apache Mesos at Twitter to becoming involved with Mesosphere? Topic 2 - It’s been about a year since we talked about Mesos on the show. We’ve talked about Kubernetes a few times. Can you give us the basics of each of those technologies because sometimes people confuse them or think they are interchangeable or overlapping. Topic 3 - Let’s talk about Mesosphere and DCOS (Data Center Operating System). People talk about “durable and declarative” infrastructure for applications. How does DCOS accomplish this? Topic 4 - Mesosphere includes not only systems and schedulers for the underlying container infrastructure, but also application-level schedulers. What are the differences, and how does a development team vs. an ops team interact with Mesosphere? Topic 5 - What types of applications are you seeing Mesosphere customers running in this new environment? One thing we heard at VelocityConf was that there is work within Apache Mesos to look at adding support for stateful applications or stateful data - what’s the status of that?

Tobi Knaup, co-founder & CTO of Mesosphere joined the show to talk about the datacenter operating system, and all the open source around it.

Tobi Knaup, co-founder & CTO of Mesosphere joined the show to talk about the datacenter operating system, and all the open source around it.