Zach Musgrave, Lead Software Engineer, Yelp & Chris Gordon, Software Engineer, Yelp, sit with Dave Vellante and John Walls for Splunk .conf 2017 in Washington D.C.
#splunkconf17 #theCUBE
https://siliconangle.com/2018/01/15/no-devops-engineers-spill-secrets-yelps-hyper-agility-splunkconf17/
No ‘I’ in DevOps: Engineers spill secrets to Yelp’s hyper agility
Development operations, or DevOps, isn’t a job title; it’s not a single software tool, either. It’s a philosophy embodied by agile people using agile technology for agile business.
“Pre-DevOps was: The software developers make a thing, and then they throw it over the fence and operations picks it up. And they’re like, ‘Well, what do we do with this? Deploy it.’ OK, good luck,” said Zachary Musgrave (pictured, left), technical lead at Yelp Inc. “What this results in is sort of an us-and-them mentality.”
Musgrave joined Chris Gordon (pictured, right), software engineer at Yelp, in an interview at Splunk .conf2017 in Washington, D.C. They spoke with Dave Vellante (@dvellante) and John Walls (@JohnWalls21), co-hosts of theCUBE, SiliconANGLE Media’s mobile livestreaming studio. (* Disclosure below.)
Dev and Ops huddle in Splunk’s wide tent
Developers and operations teams are typically not incentivized to take each other’s unique issues into account, which often results in both punting glitchy apps and software back and forth, according to Musgrave. By cross-pollination of development and operations elements, the food fight ceases.
“DevOps is a we, instead of an us-versus-them,” Musgrave said.
In a DevOps model, product teams may have on-call rotations, while operations and system administrators scratch out some code. “There’s still definitely specializations, but it all comes together in a much more holistic manner,” Musgrave stated.
Versatile technologies that developers and operations teams can approach for a multitude of use cases boost DevOps and agility in general. Splunk Inc.’s broad machine data analytics platform is such a technology, Gordon explained. “Our operations teams get a lot of value out of it when there’s some outage happening, and it’s really useful for them to just look at the access logs and see what’s going on. And Splunk makes that very easy,” he said. Splunk clusters can “mutate,” enabling a whole jambalaya of usecases.
Yelp’s rapid, several-times-per-day deployment cycle demands slippery smooth DevOps functions. “Each one of those [deployments] is going to include changes from a dozen different engineers. We need to be agile in that manner just like with our Splunk cluster,” Musgrave concluded.
Watch the complete video interview below, and be sure to check out more of SiliconANGLE’s and theCUBE’s coverage of Splunk .conf2017. (* Disclosure: Splunk Inc. sponsored this segment of theCUBE. Neither Splunk nor other sponsors have editorial control over content on theCUBE or SiliconANGLE.)
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
Splunk.conf 2017. If you don’t think you received an email check your
spam folder.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Register For Splunk.conf 2017
Please fill out the information below. You will recieve an email with a verification link confirming your registration. Click the link to automatically sign into the site.
You’re almost there!
We just sent you a verification email. Please click the verification button in the email. Once your email address is verified, you will have full access to all event content for Splunk.conf 2017.
I want my badge and interests to be visible to all attendees.
Checking this box will display your presense on the attendees list, view your profile and allow other attendees to contact you via 1-1 chat. Read the Privacy Policy. At any time, you can choose to disable this preference.
Select your Interests!
add
Upload your photo
Uploading..
OR
Connect via Twitter
Connect via Linkedin
EDIT PASSWORD
Share
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
Splunk.conf 2017. If you don’t think you received an email check your
spam folder.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Sign in to gain access to Splunk.conf 2017
Please sign in with LinkedIn to continue to Splunk.conf 2017. Signing in with LinkedIn ensures a professional environment.
Are you sure you want to remove access rights for this user?
Details
Manage Access
email address
Community Invitation
Zachary Musgrave & Chris Gordon, Yelp | Splunk .conf 2017
Zach Musgrave, Lead Software Engineer, Yelp & Chris Gordon, Software Engineer, Yelp, sit with Dave Vellante and John Walls for Splunk .conf 2017 in Washington D.C.
#splunkconf17 #theCUBE
https://siliconangle.com/2018/01/15/no-devops-engineers-spill-secrets-yelps-hyper-agility-splunkconf17/
No ‘I’ in DevOps: Engineers spill secrets to Yelp’s hyper agility
Development operations, or DevOps, isn’t a job title; it’s not a single software tool, either. It’s a philosophy embodied by agile people using agile technology for agile business.
“Pre-DevOps was: The software developers make a thing, and then they throw it over the fence and operations picks it up. And they’re like, ‘Well, what do we do with this? Deploy it.’ OK, good luck,” said Zachary Musgrave (pictured, left), technical lead at Yelp Inc. “What this results in is sort of an us-and-them mentality.”
Musgrave joined Chris Gordon (pictured, right), software engineer at Yelp, in an interview at Splunk .conf2017 in Washington, D.C. They spoke with Dave Vellante (@dvellante) and John Walls (@JohnWalls21), co-hosts of theCUBE, SiliconANGLE Media’s mobile livestreaming studio. (* Disclosure below.)
Dev and Ops huddle in Splunk’s wide tent
Developers and operations teams are typically not incentivized to take each other’s unique issues into account, which often results in both punting glitchy apps and software back and forth, according to Musgrave. By cross-pollination of development and operations elements, the food fight ceases.
“DevOps is a we, instead of an us-versus-them,” Musgrave said.
In a DevOps model, product teams may have on-call rotations, while operations and system administrators scratch out some code. “There’s still definitely specializations, but it all comes together in a much more holistic manner,” Musgrave stated.
Versatile technologies that developers and operations teams can approach for a multitude of use cases boost DevOps and agility in general. Splunk Inc.’s broad machine data analytics platform is such a technology, Gordon explained. “Our operations teams get a lot of value out of it when there’s some outage happening, and it’s really useful for them to just look at the access logs and see what’s going on. And Splunk makes that very easy,” he said. Splunk clusters can “mutate,” enabling a whole jambalaya of usecases.
Yelp’s rapid, several-times-per-day deployment cycle demands slippery smooth DevOps functions. “Each one of those [deployments] is going to include changes from a dozen different engineers. We need to be agile in that manner just like with our Splunk cluster,” Musgrave concluded.
Watch the complete video interview below, and be sure to check out more of SiliconANGLE’s and theCUBE’s coverage of Splunk .conf2017. (* Disclosure: Splunk Inc. sponsored this segment of theCUBE. Neither Splunk nor other sponsors have editorial control over content on theCUBE or SiliconANGLE.)
