New York City, NY
2018-01-18 to 2018-01-19
Description
Microsoft issued me a Mac when they hired me to help people use Linux on Azure. If this sounds like the beginning of a nerdy joke, it’s because we need to question long-held opinions, let go of deeply-cherished stereotypes, and welcome this new era of open collaboration.
Let’s take the 10,000 foot tour of today’s cloud, containers, and orchestration landscape before diving into specifics we can use when making calls on microservices, backing data stores, and app decomposition. We’ll talk public cloud, containers, and k8s from the “Open at Microsoft” perspective!
Slides
Video
Tweets
Next up at #devopsdays NYC: @bridgetkromhout on Clouds, Containers, and Kubernetes.
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Minnesota is one of the largest DevOps communities in the world. 1000 people turn up to MSP #DevOpsDays, but only 300 to DevOpsDays NYC.
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Cloud, containers, kubernetes. Let’s talk about architecture and history.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
We heard some history and culture; this one was labeled as architecture in the overview, but ties into history and culture and "human spaces". #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Excited to hear @bridgetkromhout speak at #DevOpsDaysNYC 🤜🤛 #WomenInTech pic.twitter.com/L95WTYuxqT
— DevOps Institute (@DEVOPSINST) January 18, 2018
Let's talk about how all of this relates to you. We need to figure out how these things help us at work on Friday or Monday. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopsdaysnyc @MicrosoftNY pic.twitter.com/ynk3L77rQ0
— Luis Michael (@Clvx) January 18, 2018
IT in the 1990s had battle lines. "there'll be a link in the show notes... oh, this is not a podcast." apple vs microsoft, open vs closed source. open source has won. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: In the 90’s, IT had battle lines. Apple/Microsoft, OpenSource/Proprietary.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Time for your daily dose of @bridgetkromhout. #devopsdays pic.twitter.com/H4ElZ2ns74
— Joe Laha (@joelaha) January 18, 2018
Microsoft is one of the largest contributors to open source on GitHub. Still haven't done any windows since joining. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: You know open source won that one when Microsoft uses open source.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Talking Cloud, Containers & Kubernetes (devops buzzword bingo) with @bridgetkromhout #devopsdaysNYC pic.twitter.com/IAsqYNy07I
— Amaya Booker (@Illdrinn) January 18, 2018
#devopdays @bridgetkromhout: We all have to pick a level of abstraction to spend time on. We keep moving our level of abstraction up because we can’t know everything.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Poll from @swardley: Meltdown and Spectre: AWS [ed: and Azure and GCP] instantly patched, but private clouds... all lagging. fixed "after heartbleed", itself not yet patched. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
I’ve been tossing the ideas around that the DevOps movement is the current end result of OSS culture winning over 1990s enterprise.
— aaron aldrich is home (@crayzeigh) January 18, 2018
And enterprises are trying now to figure out how to “do DevOps.”
glad to see @bridgetkromhout
saying similar things.#devopsdays NYC https://t.co/AdYcpKhJDu
Same as you can't be surprised by Settlers of Catan pirates, you can't be surprised that disruption and change is coming to IT. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: You can’t claim that disruption is a surprise — it’s inevitable and we know it’s coming.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
It's a fundamental shift in how information disseminates across our organizations. We don't send things up and down the flagpole any more, we use backchannels to actually get things done. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Shoutout to Conway’s Law: A system designed by an org will reproduce the structure of the org’s communication structure.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
It's frustrating to put together IT infra based on the relationships we have with people in other organizations. [ed: SLOs SLOs SLOs APIs APIs APIs omg] #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
"We're building complex systems out of software *and* out of humans". Is this resume driven development? #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: We’re building complex systems out of software, and complex systems out of people, and the two are heavily related.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
.@bridgetkromhout flyingthe Microsoft flag here at @devopsdaysNYC and dropping knowledge on us about our organizations and how they connect within. #devops #DevOpsDays #devopsdaysnyc pic.twitter.com/tECdvHYrk6
— Chris Short (@ChrisShort) January 18, 2018
People wind up left with complicated, hard to maintain things from people doing experiments and then abandoning them. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Only adopt things if your needs dictate them, don't do it based on what people are excited about. "What problem will this tech solve for you?" #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Don’t fall for resume driven development - any single technology could be fragile and prone to maintainer foibles.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Choose cloud because it's right for you, not just because it exists in the world. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
I love the live-tweeting #devopsdays trend. I had to step out for a call but thanks to @lizthegrey I still know what @bridgetkromhout is saying at talk!
— aaron aldrich is home (@crayzeigh) January 18, 2018
Thanks to everyone who also obsessively live tweets these events.
Choose the right abstractions and places to move things into the cloud based on what makes it *different* from what you already have. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: If you want to go to cloud, do it for the right reasons. Choos ethe right abstractions and focus on differentiations.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Have something you're trying to accomplish (e.g. API-driven infrastructure) that you can't do in-house, rather than just shiny things you're trying to get someone to fund. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Dramafever started running docker in production in october 2013 when Docker was very very new. Joined them in 2014. We did cool things with containers... #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Solved problems with consistent deployments by using containers, got away from bespoke server configs. But didn't solve all of our problems. Also created problems for ourselves. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Containers can solve problems with consistent development, and make deployment repeatable. But we created problems for ourselves because....databases don’t autoscale.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
e.g. dependency version mismatches, lack of infinite scaling of databases. Lots of problems you won't necessarily consider if you say "we should docker all the dockers". #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Containers are not actually new. Date back to 1979 chroot, or FreeBSD in 2000.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Make decisions based on the right abstractions... what are your real objectives? @bridgetkromhout is awesome at bring DevOps to life! #DevOpsDays #devopdaysnyc #vztechconnect #buildmoreawesome pic.twitter.com/lPdUkXr8dz
— Heather Schneider (@Heather17196626) January 18, 2018
Bridget Kromhout is now speaking at DevOps day NYC. She is very involved with the DevOps community - last year there were 51 events on 6 continents! And always fun to listen to! Title ‘Cloud, Containers, Kubernetes’ @devopsdaysNYC #devopsdays #devopdaysnyc pic.twitter.com/BqU3lXRJN7
— Candy (@candy86145261) January 18, 2018
#devopdays @bridgetkromhout: Containers became mainstream because Docker made them usable, accessible, friendly, less ops-y.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Containers aren't technically new (e.g. chroot, jails, zones), but weren't widely adopted. why? Docker made things more usable, accessible, and available for developers to use rather than being monopolized by "scary ops people". #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Kubernetes: 2015 OSCON was the 1 year birthday of Kubernetes. but at 1 year, didn't yet resonate with the community. Problem of orchestrating containers using janky bash. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Great talk by @bridgetkromhout at #devopsdaysnyc at Microsoft NYC #devopsdays pic.twitter.com/yyAmyhJVcE
— Larry C (@larrycl) January 18, 2018
Lots of important pieces: orchestration, monitoring, logging, tracing, rpcs, discovery, runtimes, meshes... CNCF is a lot more than just orchestration. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Containers are a tool to help you with repeatability, not a goal. Be aware of the complexity of the ecosystem and ongoing work. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: Treat containers as a tool, not a goal. Be aware of complexity. Containers are a solution, not THE solution.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Treat containers as a tool, not a goal! - @bridgetkromhout #devopsdays
— Jason Yee (@gitbisect) January 18, 2018
So, onto Kubernetes. show of hands. how many people have used it in production vs. played around with it? 1/3 have played with it, only a handful use it in prod. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
@bridgetkromhout on containers at #DevOpsDaysNYC 📝 pic.twitter.com/LtJQKxJGsP
— DevOps Institute (@DEVOPSINST) January 18, 2018
“Treat containers as a tool, not a goal” @bridgetkromhout keynoting at #devopsdays
— Randy Shoup (@randyshoup) January 18, 2018
- "Who has played with Kubernetes?": a third of the room.
— Tanya Reilly (@whereistanya) January 18, 2018
- "Who's using it in production?": seven people.@bridgetkromhout at #devopsdaysnyc
"Computers are easy, people are hard" is catchy but false; "scalable fault-tolerant distsys requires eng effort to build and operate; and people are even harder than that"... is more accurate. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
When we decide to move to microservices, we add more scalability, but we make things *harder* to use. Maybe you do need it, maybe you don't. Who will need to be retrained?
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Who will resist? #devopsdays
#devopdays @bridgetkromhout: Kubernetes: When we add it to our system, it doesn’t make anything easier. It makes it more scalable, more robust, but it’s still difficult change.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
#devopdays @bridgetkromhout: There are tradeoffs for any technical change that we make. Microservices takse your IPC and turns it into transient network failure.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
"What are the trade offs in your organization for this change?" @bridgetkromhout pic.twitter.com/1dXzCqD1Do
— Chris Short (@ChrisShort) January 18, 2018
Every proof of concept someone wants to put into your org: day 1 is going to be amazing, but what about day 2? [c.f. vendor demos]. At some point you have to redeploy or scale out or patch. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Distributed systems are hard; people are harder @bridgetkromhout #devopsdays pic.twitter.com/j4Gj31M9vr
— Randy Shoup (@randyshoup) January 18, 2018
Peak planning [e.g. black friday or tax day] is hard. It's great if something works seamlessly, but it's essential for it to work on days 2 through 2005. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Distributed systems are hard; people are harder @bridgetkromhout #devopsdays pic.twitter.com/wcJijhDTPC
— Randy Shoup (@randyshoup) January 18, 2018
#devopdays @bridgetkromhout: It’s great if something works perfectly on day 1. It’s essesntial that it works on day 2 and day 2005. You can’t walk away when you get something in production, it has to keep going.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Ask how questions. How are we going to transition? [ed: and decommission the old thing]? How are we going to run it? We're just getting started when we stand it up for the first time. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
For evaluating new tech, make sure that you understand the underlying technology. c.f. "kubernetes the hard way" by @kelseyhightower #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Make sure you know what it's doing before you buy the packaged solution version that a vendor is selling you. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Tools are not goals... seriously consider trade offs and non-ideal conditions / states... it has to work on day 2, not just on day 1 #DevOpsDays #devopsdaysNYC #vztechconnect #buildmoreawesome pic.twitter.com/frEa5TMudg
— Heather Schneider (@Heather17196626) January 18, 2018
"You can have that war as to whether it's kube-control, kube-cuddle, but either way, it's a way of talking via the API to the Kubernetes master." #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
#devopdays @bridgetkromhout: If you want to understand kubernetes, understand the stack underneath it.
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
[ed: obligatory ref to https://t.co/8N76AgspZ2] #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Don't let someone discourage you from your Kubernetes dreams because you're running in a private cloud or onprem. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Master's job is to schedule pods on the nodes that make sense. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
.@bridgetkromhout dropping @kubernetesio knowledge on the @devopsdaysNYC crowd. Yes!!! #devops #devopsdaysNYC #kubernetes pic.twitter.com/xBD52jENvH
— Chris Short (@ChrisShort) January 18, 2018
You probably want to use fluentd or some other method of collecting logs as there's no default logging in Kubernetes happening in the kubelet for your apps. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
"This looks like something I built once, except plus or minus a few components..." exactly, Kubernetes is trying to be unopinionated and allow you to flexibly do things in familiar ways. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Idea is to unify languages we use to talk about systems, and make sure people understand the common design patterns. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
If you just want to use Kubernetes without worrying about the innards, you can use AKS, GKE, or EKS, etc. -- without having to build a Kubernetes cluster yourself. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Projects to watch in the space to help you avoid the "murder mystery" problem when debugging: @heptio @honeycombio @IstioMesh brigade.sh #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Finally, important to explore stuff. Especially if you don't yolo it directly into production; it's safe to experiment with your nonprod environments to find things that will help you a lot. #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
Be settlers rather than pioneers; make things operable rather than just focusing on brand new and shiny [ed: anyone know a less colonialist phrasing of this idiom?] #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
“Celebrate scaling things up. Celebrate operability.” -@bridgetkromhout #DevOpsDaysNYC
— DevOps Institute (@DEVOPSINST) January 18, 2018
#devopdays @bridgetkromhout: I look at brand-new and shiny and wonder — when is that going to page me?
— Heidi is Doing A Think about tech (@wiredferret) January 18, 2018
Kubernetes lets you avoid "super bespoke artisanal hand-whittled orchestration"... which is probably a bunch of janky bash. @bridgetkromhout #devopsdaysnyc
— Tanya Reilly (@whereistanya) January 18, 2018
Orchestration is only one part; there's a whole suite of techniques you need. Clouds are still computers, silos are for grain, and containers don't make you devops. [fin] #devopsdays
— Liz Fong-Jones (方禮真) (@lizthegrey) January 18, 2018
“Solos are for grain and not for organizations” @bridgetkromhout #DevOpsDays #devopsdaysNYC #vztechconnect #buildmoreawesome
— Heather Schneider (@Heather17196626) January 18, 2018