While the payoff of a successful implementation can be HUGE, the beginning of your Programmable Infrastructure journey may be difficult and fraught with danger. There are decisions you need to make right from the start that will dictate the experience you and your customers, external or internal, encounter. To avoid ‘kicking an operational nightmare can further down the road’ (or into the orchestrator as it may be), ensure you are employing declarative API interfaces and appropriate levels of abstraction in your automation tooling.
In this episode I explain the importance of declarative API interfaces. Trying to move all of the knobs and buttons of programmable infrastructure into your deployment tooling WILL come back to bight you later. It will be costly to support, it will create an integration too rigid to adapt to new systems and services, and it will increasingly inhibit business agility as time goes on.
Thanks for joining us on the 20th episode of REDtalks.live
Due to popular demand, here is a short (16 minute) video explanation of the Super-NetOps persona.
I frequently give talks on the need for Super-NetOps engineers and architects to support modern development/DevOps processes. However, that talk (especially with enthusiastic Q&A sessions) takes about 90 minutes. Hence, below is a quick ‘why you need Super-NetOps’ version I put together for those in a hurry.
Brilliantly summarized by my colleague, Joe Cassidy, “Great short video by Nathan Pearce explaining the “Super-NetOps” concept wherein NetOps embraces principles and practices of DevOps to reduce the skills gap between Infrastructure and Developer silos. Like DevOps, “Super-NetOps” is not a technology, tool or person but rather a culture change where infrastructure teams adopt “systems thinking”. This shifting focus towards “systems thinking” empowers the traditional infrastructure silos to collaborate, continuously improve delivery, enhance communication, enable self-service and speed development. F5 is helping enterprises embrace this concept by (among other things) enabling APIs, exposing Declarative Interfaces and executing on Self-Service Models and Templates.”
Thanks for listening!
Greeting automators and welcome to edisode #17 of REDtalks. Today’s guest is Tyler Hatton who is from WWTs own internal IT Operations team. Tyler is the F5 BIG-IP Subject Matter Expert for WWT and is hell-bent on replacing the mundane with declarative interfaces and orchestration systems.
Watch this episode to hear about the interesting culture at WWT and their regular hack-a-thon’s. These events themed at breaking the routine and investing internally in continuous education and, my favorite, “continuous improvement”. Following this, Hatton talks us through his brilliantly named, hack-a-thon winning, “(P)orchestrator” solution!
Tune it to understand the time-saving, self-service interface that Tyler produced, quite literally, from the Ops ‘drivers seat’.
Many thanks, Tyler, for sharing your story!
In episode #16 we are joined by Andreas (Andy) Grabner, of Dynatrace, and Tom McGonagle, of F5 Networks.
Watch this episode to hear about Metrics Driven Automation, or Informed Automation, and how this takes the feat out of fully integrated deployment pipelines. Andy shares some great insights on how to avoid automating oneself into dangerous situations.
Following this, Tom shows us (yes, a live demo) how to deploy an F5 BIG-IP policy using the CI/CD tool, Jenkins.
You may recall Tom from a previous episode, REDtalks #14 – Tom & David on the Principles & Practices of DevOps. Thanks for coming back, Tom! Here’s the Jenkins Github repo he referenced in his demo: https://github.com/mcgonagle/F5file
And thanks, Andy, for your valuable insights on impelmenting safe, information automation. Andreas To hear more from Andy Grabner, take a look at some of these links:
Thanks, both, for your time!
Episode #15 brings us the topic of ChatOps. No, I’m not talking about late nights dialed into bulletin board chat groups on your 9600 bit/s modem! ChatOps is about cross team collaboration and information sharing.
Who better to join me in this episode than the author of O’Reilly’s “ChatOps – Managing Operations in Group Chat“, Jason Hand. As DevOps Evangelist as VictorOps, Jason spends a lot of time talking at conferences and to customers about the journey to a DevOps culture and how ChatOps enables rapid collaboration across teams.
Watch this episode to obtain a deep understanding of what ChatOps is all about, learn of the immediate benefits to organizations from adopting such a practices, and get some great tips on how to get started.
Thanks for joining us, Jason!
You can grab the book here: https://victorops.com/knowledge-drop/devops-docs/chatops-managing-operations-group-chat/
Today I’m joined by Thomas McGonagle and Dr David Yates to discuss the principles and practices of DevOps.
Thomas McGonagle is a Sales Engineer and DevOps evangelist at F5 Networks. Before joining F5, Thomas held positions at Cloudbees (maker of Jenkins) and Booz Allen Hamilton, in addition to running his own consulting business that heavily leveraged Puppet. Consistent throughout his career has been a strong focus on automation and orchestrations.
Dr David Yates joins us from Bentley University where he is an Associate Professor of Computer Information Systems. Dr Yates has an MS & PhD in Computer Science, is co-inventor of 12 patents, and comes with hands-on experience in both Agile and DevOps. He is currently working on bringing these practices into the classroom.
Listen to this episode to hear the principals and practices that Thomas and Dr Yates live by in terms of DevOps and automation. To summarize, we discuss these three principals:
- Systems thinking (continuous delivery, continuous everything, …)
- Continuous intelligence (from amplified feedback)
- Continuous learning (from experimentation and practice)
And these 9 practices:
- Practice 1: Configuration management
- Practice 2: Continuous integration
- Practice 3: Automated testing
- Practice 4: Infrastructure as Code
- Practice 5: Continuous delivery
- Practice 6: Continuous deployment
- Practice 7: Continuous monitoring
- Practice 8: Develop an engaged and inclusive culture to encourage collaboration and shared ownership
- Practice 9: Actively participate in communities of practice to become a lifelong learner of technology development (don’t be a jerk!)
Thanks Thomas McGonagle and Dr David Yates for joining us!
UPDATE: Here are the Cloudbees blogs that Tom mentions in this REDtalks episode: https://www.cloudbees.com/blogs/thomas-mcgonagle
Mark Wall and Joe Weber of WWT join me in lucky episode #13 to discuss automation with Cisco CloudCenter (the artist formerly known as CliQr).
As many already know, in 2016 Cisco bought CliQr, which has since been renamed Cisco CloudCenter. Watch this episode to see how CliQr is used to deploy applications while also configuring Cisco ACI (connectivity fabric), VMware vSphere, Infoblox, and F5 BIG-IP LTM in one single automation workflow.
In the first half of the video we hear from Mark and Joe about their experiences with customer automation. They share with us the typical experiences of an infrastructure admins journey from being a ‘button pusher’ to being a ‘button creator’ before closing out the first half of the talk by sharing their understanding of the markets maturity with automation.
We then enter the second half of the video where Joe explains the CliQr workflow he’s built, with the aid of some helpful diagrams, before throwing caution to the wind and providing a live demonstration (this from the 36 minute mark).
Thanks for joining us, Mark & Joe! More on this from Joe in his WWT blog here: https://www2.wwt.com/all-blog/using-cisco-cloudcenter-to-automate-f5-and-other-workflows
F5 long-timer, Joe Pruitt, joins me in this episode to discuss API Lifecycle Management!
Joe joined F5 back in 1998 to build BIG-IP management and API solutions. He built the original BIG-IP API, iControl, back 2001: first in CORBA, and then SOAP/XML. Click play to hear Joe’s experiences with building robust APIs suitable for modern Infrastructure as Code practices, and hear why he’s returned to the product development team after several years building F5’s developer community platform, DevCentral.f5.com.
Thanks for joining us, Joe!
Our very first REDtalks guest, Hitesh Patel, is back again to help us understand a fundamental architectural shift in how systems must change to support a Mode 2 methodology. In this episode we talk about levels of abstraction and how they effect automation processes. We discuss the operational overhead involved in supporting infinite deployment options versus adopting a service templating process, and how this hinges on the abstraction of domain-specific knowledge.
Explained through the art of sandwich making versus microwaving a burrito, listen to this episode to understand the differences between imperative and declarative models.
Thanks again for your time, Hitesh.
Struggling to keep up with all the new terminology?
F5’s Lori MacVittie joins us again to discuss some of the many new, and often confusing, terms coming to us with the DevOps movement. In this episode we cover everything from the differences between “NetOps vs WebOps vs DevOps”, why we see terms like “OpsDev” (yuk) in the media, and the all-important difference between CI/CD and the other CD.
We hope you enjoy!
Thanks again for stopping by, Lori.