Joining us this week is Christine Yen, Co-founder at Honeycomb coming from a recording at SRECon Americas in March 2018 at Santa Clara Convention Center Hyatt.
- Understanding of what developer tools are today
- Observability vs Monitoring
- Instrumenting Apps for Diagnostics to help Developers do More
- Tool to build not just better engineers but teams as well to support customers
- Brief history of Honeycomb and where it came from (Parse and Facebook)
- How debug containers that are most likely gone by time problem arises?
- AI / Machine Learning – can it really help today?
- 2nd Wave of DevOps
- Impact of listening to users at a startup – people problems vs technology
Topic Time (Minutes.Seconds)
Introduction 0.0 – 2.05
Integration of Honeycomb and Digital Rebar Provision 2.05 – 3.01 (Plugin Info)
Developer Tools – what is that category? 3.01 – 5.15 (Not doing harm)
Observability vs Monitoring 5.15 – 7.45 (Doctor analogy)
Instrumenting Applications for Diagnostics 7.45 – 10.19
My View vs Team View 10.19 – 14.45 (Build better eng & teams)
Why we built Honeycomb? 14.45 – 18.38
Centralized Logging in Distributed Containers 18.38 – 19.25
Can AI / Machine Learning assist in Finding Issues? 19.25 – 21.35 (7 Different Ways by Barry Schwartz)
Team Specialties – 2nd Wave of DevOps 21.35 – 26.35 (Teach Devs to Own Code)
Listening to Users as a Startup 26.35 – 35.35 (UI Issues)
Who is Charity Majors? Co-Founder Honeycomb 35.35 – 38.30
Wrap Up 38.30 – END
Podcast Guest: Christine Yen, Co-founder at Honeycomb
Christine Yen is a cofounder of Honeycomb, a startup with a new approach to observability and debugging systems with data. Christine has built systems and products at companies large and small and likes to have her fingers in as many pies as possible. Previously, she built Parse’s analytics product (and leveraged Facebook’s data systems to expand it) and wrote software at a few now-defunct startups.
Joining this week’s L8ist Sh9y Podcast is Bernard Golden, a long-time tech innovator and visionary and one of the ten most influential people in cloud computing according to Wired.com. Bernard and Rob Hirschfeld discuss the latest blog from Bernard and the impact of Edge Computing and the reality of implementing this concept. We are also introduced to the Container Hotel.
Topic Time (Minutes.Seconds)
Introduction 0.0 – 0.39
Edge Computing Blog 0.39 – 3:35 (Bernard Blog)
Other Non-Control Loop Use Cases 3.35 – 7:10
Environmental Computing / IOT 7:10 – 9:05
Fallacy of Vendor-based Solutions 9:05 – 13:25
How Manage Edge Hardware 13:25 – 16:00
Container Hotel 16:00 – 16:50
No One Cares about Hardware 16:50 – 23:40
Cloud Extensions – Not Mini Clouds 23:40 – 27:05
Like Cloud but Own Data-Center Can’t Do What I Want 27:05 – 29:55
Wrap-Up 29:55 – END
Podcast Guest: Bernard Golden
Bernard Golden is a long-time tech innovator and visionary. Wired.com named him one of the ten most influential people in cloud computing, and his blog has been listed in over a dozen “best of” lists. He is the author/co-author of five books, including Amazon Web Services for Dummies, the best selling cloud computing book ever.
From 2012 to 2015 Bernard served as an executive at two cloud computing software startups: Enstratius (acquired by Dell, 2013) and ActiveState Software (cloud product line acquired by HPE, 2015).
After leaving ActiveState, Bernard began researching and consulting across a number of new technologies, including machine learning, drones, genomics, and 3D printing. One, however, stood out as the next innovation platform that will transform our society: blockchain.
Last week, the CloudCast.net interviewed Lachlan Evenson (now at Deis!). I highly recommend listening to the interview because he has a unique and deep experience with OpenStack, Kubernetes and container migration.
I had the good fortune of lunching with Lachie just before the interview aired. We got compare notes about changes going on in the container space. Some of those insights will end up in my OpenStack Barcelona talk “Will it Blend? The Joint OpenStack Kubernetes Environment.”
There’s no practical way to rehash our whole lunch discussion as a post; however, I can point you to some key points [with time stamps] in his interview that I found highly insightful:
- [7:20] In their pre-containers cloud pass, they’d actually made it clunky for the developers and it hurt their devops attempts.
- [17.30] Developers advocating for their own use and value is a key to acceptance. A good story follows…
- [29:50] We’d work with the app dev teams and if it didn’t fit then we did not try to make it fit.
Overall, I think Lachie does a good job reinforcing that containers create real value to development when there’s a fit between the need and the technology.
Also, thanks Brian and Aaron for keeping such a great podcast going!
As part of our exploration of containers on metal, the RackN team has created a workload on top of OpenCrowbar as the foundation for a Docker Swarm on bare metal cluster. This provides a second more integrated and automated path to Docker Clusters than the Docker Machine driver we posted last month.
It’s really pretty simple: The workload does the work to deliver an integrated physical system (Centos 7.1 right now) that has Docker installed and running. Then we build a Consul cluster to track the to-be-created Swarm. As new nodes are added into the cluster, they register into Consul and then get added into the Docker Swarm cluster. If you reset or repurpose a node, Swarm will automatically time out of the missing node so scaling up and down is pretty seamless.
When building the cluster, you have the option to pick which machines are masters for the swarm. Once the cluster is built, you just use the Docker CLI’s -H option against the chosen master node on the configured port (defaults to port 2475).
This work is intended as a foundation for more complex Swarm and/or non-Docker Container Orchestration deployments. Future additions include allowing multiple network and remote storage options.
You don’t need metal to run a quick test of this capability. You can test drive RackN OpenCrowbar using virtual machines and then expand to the full metal experience when you are ready.
Contact email@example.com for access to the Docker Swarm trial. For now, we’re managing the subscriber base for the workload. OpenCrowbar is a pre-req and ungated. We’re excited to give access to the code – just ask.