Key Factors to Consider During Containerization with Travis Jeppson

Key Factors to Consider During Containerization with Travis Jeppson

Some of the highlights of the show include

  • How containerization enabled Nav to spread roughly 250 virtual machines across multiple environments, while drastically reducing infrastructure spend
  • Travis’s thoughts on buying cloud native software tools versus building them, and what engineers should consider during this process
  • The difficulty of finding security solutions that work inside of a cloud-native ecosystem
  • Why companies should expect to encounter unique challenges when migrating to Kubernetes
  • Why companies need to understand their end goal, and determine an overall objective before beginning a migration
  • Travis’s must-have engineering tool, and why he can’t live without it


Links


Transcript


Announcer: Welcome to The Business of Cloud Native Podcast where we explore how end users talk and think about the transition to Kubernetes and cloud-native architectures.



Emily: Welcome to The Business of Cloud Native. I’m Emily Omier, your host. And today I’m here with Travis Jeppson. Travis is currently at Kasten, but he’s also going to talk about his time as a director of engineering at Nav.



Travis: At Nav, my role shifted quite a bit while I was there. I started as a software developer, writing Ruby back end applications for them, and then shifted into—actually within a month of being there, they shifted me over to the operational side because I had previous experience working with containerization, and also in infrastructure. So, they quickly moved me over into that realm and from there, I worked there for about a year until they told me, go spin up a team and get things moving. Help us move to containerization. Help us move to a more modern infrastructure and stuff. And so, about a year after that I became a director of engineering to where I had our ops team that had spun up, and then I also acquired both our QA team and our IT team that was there. And then, about a year after that, I ended up acquiring a little bit more than that. So, I ended up with a fair amount of our front end and some of our backend teams as well, and where they moved me into the senior director position. So, a day in the life, towards the end of when I was at Nav was a lot of working with the teams, helping them to do a lot of architectural perspective, and changes, and outlook to where we were trying to get as far as the company is concerned. We were building a product that we could address both first-party customers where they would log in to the Nav website directly, as well as working with partners so that we could issue out Nav functionality to those partners that they could incorporate to their pages as well. And so, we worked very hard to try to segment those two pieces together so that what we were building could be dispersed between both first-party customers and our third-party customers. And so, towards the end of my time there, it ended up being a lot of working within all of engineering to help facilitate those purposes. Then, just about six months ago, I ended up shifting my role over to a company called Kasten. And, Kasten is strictly working within the Kubernetes ecosystem. So, we do data management for Kubernetes based applications, and I am the site lead in Utah for Kasten, and so my day in and day out, a lot is, it's, kind of, all over the place. Sometimes it's working with engineering to help figure out some things going on there, sometimes it's working with brokers to help find office space for it. And sometimes it's dealing with insurance. It ended up being quite dynamic. But overall, I'd say most of my time is really spent more on the engineering side, just from the perspective of having worked at Nav and having been a consumer of a lot of these technologies, I think that they really appreciate my insights that I'm able to give there. So, I end up working, a lot, with the engineers to help facilitate what we're doing.



Emily: Sounds like you end up serving as a bridge from having been an end-user. But do you think that there is common miscommunications that happen, or what do those conversations sound like? Why is that experience valuable?



Travis: Yeah, so I don't know if it's as much as a miscommunication as much as what are customers looking for? And what are they trying to achieve? And why are they purchasing different software solutions? And what makes sense for them, more than anything. And I think that, having been a consumer of those products, I was more or less on the front lines there. When I was building our operational team at Nav, that was basically what I was doing is trying to figure out what things are we going to spend time on? And what things are we going to build ourselves, or what things do we need to just go find a solution for and bring them in-house? And the funny thing is when I was doing that for Nav is actually when I was introduced to Kasten and to the CEO here. And so, that ended up changing the way my career went. But overall, I think what Kasten—what those conversations really end up becoming is what are customers trying to do, and where are they trying to go?



Emily: Yeah, and in fact, that is exactly what I want to talk about more on this podcast. So, tell me a little bit about what your experience at Nav was. What were you looking for? What did you want to prioritize? What was the company hoping to get out of moving to containers?



Travis: So, I would say maybe the piece that really facilitated a lot of the progress in that sense was starting to understand our infrastructure spend. And then, to couple with that was also trying to become more agile. More agile in the sense of being able to push on demand, where previous to that we were pushing—you know, when we push our code, we did it on a bi-weekly basis—well, every other week, and it was always very cumbersome. If we have pictures of us in the early days of Nav, where there would be 10 engineers around someone’s desk, and they were the one person that was pushing the code into production, just waiting for the other shoe to fall, or waiting for something to happen. And so, when I started doing operational things for Nav, it started addressing those two things. What can we do to help control our infrastructure, and to understand it a little bit better? And how can we also create more of a dynamic infrastructure? Like, Nav is very much a US-based company. And so, the traffic that we're getting onto our website was regional very, very much. And so, there would be periods where it would be very busy, and then there'd be periods where it wasn’t. And the way that our infrastructure was designed, and a lot of times the way that they are designed, especially with virtual machines, is that you're building for capacity. You're building to be able to handle that load, and that has to stay there all the time, regardless of whether that capacity is being used or not. And so, that was one of the biggest questions, and that bill was—we were completely in the clouds. We were completely in AWS, but that bill continued to get more and more expensive every month. To the point of where it warranted the executive team to come down and say, “This needs to be fixed. This is going at an outrageous pace, and we need to be able to figure out how to control this.” And so, that's when they came to me and said, “Okay, get a team spun up, and let's figure out how to control this.” And so, I would say that those wer...

Jaksot(267)

David and Goliath in the CMS Market with Thomas Schedler

David and Goliath in the CMS Market with Thomas Schedler

This week on The Business of Open Source, I spoke with Thomas Schedler, co-founder and CEO of Sulu. Sulu is a small, bootstrapped company that spun out of an agency; Thomas was recommended by someone to me as a guest, but when I first reached out to him he was skeptical about coming on the show because he wasn’t sure he was a good fit. But there’s a bunch to learn from this episode! Spinning out from an agency —> in my experience, one of the most common ways for open source companies to be bootstrapped, or even to be go on to raise venture capital, is to start out as a web development agency that uses a lot of open source tools.They are working on moving away from services and getting more revenue from the product; and Thomas talked about the advantages that they get from providing both services and developing a product-based business strategy.The CMS market is crowded! And everyone is open source, so being an open source company doesn’t differentiate the product at all. So how does Sulu differentiate itself in the market? Thomas talked about it. I loved that Thomas talked about how important opinions and technology choices are in differentiating themselves on the market. I also loved that Thomas talked about keeping some things out of the product as a way to differentiate themselves from others. Sometimes more features can deliver less value to users. How being small can allow you to move quicker, and that gives Sulu and advantage over the huge players in the CMS market.Why differentiation and knowing your niche is so important when you’re a small company competing again large players. Do you need to differentiate yourself in a crowded market? You might want to work with me.

28 Touko 35min

Open Source Firmware for EV Charging Stations with Marco Möller

Open Source Firmware for EV Charging Stations with Marco Möller

This week on The Business of Open Source I spoke with Marco Möller, CEO and co-founder of Pionix. This was a fabulous conversation about a company that’s in a very different market from the usual open source company: They make firmware for EV charging stations, and are behind the EVerest project, which is part of LF Energy. So who is part of the community open source projects that are so connected to hardware? Here’s what we talked about. There aren’t many hobbyists in the community — but there are a lot of people who have professional interests in the electric vehicle industry. EVerest doesn’t focus on what Marco considers “personal” or “hobbiest” features. This was a great discussion about how understanding the target market, including for the project, leads to different feature decisions. How does Pionix money? It doesn’t yet :), but we talked about various plans the company has for monetization in the future. How being involved with the LF Energy has helped build trust, which is very important for a company that is only going to be selling to large companies and governments. Why Marco thinks that the huge vision he has for creating firmware for EV charging stations is only possible with open source, and how he makes sure that he’s able to fund the large mission without hurting the community. The balancing act with getting investors who specialize in the energy market but who don’t have experience with open sourceStruggling with positioning your project or figuring out how to best monetize? You might want to work with me.

14 Touko 33min

AI-generated Code Copied from Open Source with Julian Coccia

AI-generated Code Copied from Open Source with Julian Coccia

This week on The Business of Open Source, I spoke with Julian Coccia, CTO of ScanOSS, about selling access to data while making open source software. Of course, we also talked about being an open source company that is also deep in the open source world, helping companies understand their reliance on open source code and how open source is used in their codebase. Several things that we talked about: AI and open source code. This is a topic that’s slightly tangential to business, but very interesting to me. If you’re using an AI code generator, you are almost certainly putting verbatim copies of open source code into your codebase, but without realizing you’re doing so and without any understanding of the license requirements. This is a huge compliance risk. 2% of code generated by AI is a verbatim copy of open source code. How the biggest challenges isn’t necessarily monetizing, but getting visibility into the sales funnel. It can feel random and sudden; a company appears out of nowhere ready to sign a contract because they’ve been using the open source project for months. This is the last week to get tickets for Open Source Founders Summit, so if you want to join other leaders of open source companies May 19th and 20th in Paris, get your tickets now!

7 Touko 35min

How to be Successful when Donating a Project to the CNCF with Liz Rice

How to be Successful when Donating a Project to the CNCF with Liz Rice

Today on The Business of Open Source I spoke with Liz Rice, Chief Open Source Officer at Isovalent, which is now part of Cisco. We addressed two subjects: How to be successful as a company that donates their project to the CNCF, and the story of Isovalent’s acquisition by Cisco and the role open source played in that acquisition. We talked about: Trademarks. This is a very important part of what you donate when you donate a project to the CNCF (or other foundations). We talked about what you can and can not do with the name and logo of “your” project when it becomes part of the CNCF, and what that means for the competitive landscape you’re a part of. How to best take advantage of the marketing benefits that being part of the CNCF brings. How to create a link between the CNCF project and the company that donated it. The role that Cilium and eBPF played in Isovalent’s acquisition by Cisco. Why Isovalent’s relationship with open source is valuable to Cisco in and of itself. How open source companies can increase the likelihood that they’ll be able to continue investing in open source post-acquisition. Why it’s so important to find opportunities for collaboration. Want help making the link between your CNCF project and your commercial product? You might want to work with me.

30 Huhti 40min

Open Source Manifestos with Vincent Untz

Open Source Manifestos with Vincent Untz

This week on The Business of Open Source I talked about Open Source Manifestos with Vincent Untz, CTO of Centreon. The entire conversation focused on this idea of open source manifestos, which Vincent is going to talk about at Open Source Founders Summit — and I had never heard of before. The idea to create an open source manifesto came about because internally there was a lot of frustration around Centreon’s relationship with open source. A lot of people, especially those who didn’t come from an engineering background, would routinely ask why the company invested so much in open source. At the same time, there was a feeling among the engineering team that the company’s commitment to open source — and the concrete development time spent on open source — was slipping. After creating the manifesto, the doubts about why open source mattered went away immediately — there hasn’t been a single conversation calling into question why open source matters since the manifesto was finished. Now conversations about open source are different. Externally, there’s been a huge change in conversations around open source. People say things like “Centreon is back in the game.” It’s hard to point to concrete financial results as a result of the manifesto, but there have been differences in relationships with partners for sure, and it has helped get more companies to contribute to the project. Want to see what the Centreon Open Source Manifesto looks like? Check it out here.

2 Huhti 39min

How a Rebrand Increased Sales with Lukas Gentele

How a Rebrand Increased Sales with Lukas Gentele

This week on The Business of Open Source, I spoke with Lukas Gentele, the CEO and co-founder of LoftLabs. Here’s some of the things we covered: There are many open source projects at LoftLabs. We talked about what the team did differently the second time round, when they’d had the experience of creating the first project under their belt, and why they continued creating additional projects after that. How they make roadmap decisions to decide what goes in the OSS versus what goes in the enterprise editionHow they thought about the benefits to the business from open sourcing vCluster, the second project they released, and whether or not the theory about how it would benefit the business ended up being correct. Whether or not open code is necessary for community building, and why. In particular, we talked about the difference in how people feel ‘ownership’ of open source projects when they contribute to them. The pros and cons of building different brands around your project, your product and your company; and of having different brands around your different projects. We talked about this a lot; LoftLabs has a different company brand from any of the products or projects, but they discovered that if the project and product do not have the same brand, people get so confused that they ultimately do not buy. If you need to figure out how to brand your project and product, you might want to work with me. If you want an opportunity to talk with other founders about branding, community building, and more, you should join us at Open Source Founders Summit May 19th and 20th in Paris.

26 Maalis 42min

Fundraising and M&A for Open Source Companies with Daniel Jarjoura

Fundraising and M&A for Open Source Companies with Daniel Jarjoura

This week on the Business of Open Source I spoke with Daniel Jarjoura, an investor at Avolta who specializes in developer-facing companies, and who writes a newsletter on developer-facing startups and also collects data on investments in open source companies. We spoke about the overall state of investment for open source companies and specifically the state of investment in open source companies in Europe. Here’s what we talked about: Differences between venture funding for OSS companies in Europe and in NAHow open source companies were relatively stable in terms of getting venture funding, even as the entire venture funding ecosystem was in free-fall.How it might be true that European investors don’t understand open source companies, but on the other hand plenty of North American investors invest in European companies. Do developers trust open core companies? We had a discussion about whether or not open source companies have a trust problem…How important communication is for open source companies, something that I think is very true — a lot of the problems that open source companies run into when they either adopt an open core model or even when they do a license change. How founders can do a better job communicating with their VCs, including how to do a better job targeting appropriate investors. What do optimizing for in the VC relationship … and spoiler alert, that is for money. You might want a perfect VC who can make introductions, give you advice, give you money, be nice, etc. But the most important thing is the cash; focus on that. The second most important is the introductions. But advice isn’t something you should count on from VCs, and that really isn’t a VCs job, anyway. We finished the conversation with a discussion about M&A for open source companies. If you want good advice about your open source company, you might want to work with me. If you want an opportunity to talk with other founders about things like M&A for open source companies, communicating with VCs, and other topics specific to open source companies, you should join us at Open Source Founders Summit May 19th and 20th in Paris.

19 Maalis 43min

Products, consulting, and open source with Andrew Martin

Products, consulting, and open source with Andrew Martin

This week on The Business of Open Source I spoke with Andrew Martin, CEO and founder of Control Plane. Control Plane is ultimately a consulting company, as Andrew introduced it. But the company also created and maintains KubeSec, and also has an enterprise version of Flux CD that it licenses. That gives this conversation a slightly different flavor from the usual. Here’s some of the things we talked about: The business ROI that Andrew expected to get from releasing KubeSec, and whether or not he as actually seen those expected results play outThe difference between bootstrapping a company by offering services and by offering consulting — specifically what the difference between services and consulting is. The problem with “drive-by” feature development in open source projects — when people contribute features but don’t commit to the ongoing maintenance of the projectWhy Control Plane decided to release an enterprise version of FluxCD, and how the enterprise version of Flux is differentiated from the pure open source project. Why underinvesting in marketing, especially in marketing for the open source projects, was a mistakeJoin us at Open Source Founders Summit if you want more conversations about how companies are built around open source projects, from consultancies to large corporations.

12 Maalis 36min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
puheenaihe
rss-rahapodi
ostan-asuntoja-podcast
rss-lahtijat
pomojen-suusta
rss-rahamania
rss-startup-ministerio
rss-turvacast
taloudellinen-mielenrauha
rss-neuvottelija-sami-miettinen
rahapuhetta
rss-h-asselmoilanen
oppimisen-psykologia
kasvun-kipuja
sijoituspodi
hyva-paha-johtaminen
rss-40-ajatusta-aanesta