Technical Solutions Used to Implement DevOps
Technical Solutions Used to Implement DevOps
What are the technical solutions you use implementing DevOps? A couple of executives from companies adopting DevOps answer this question.
Join the DZone community and get the full member experience.Join For Free
To gather insights on the state of the DevOps movement in 2017, we talked to 16 executives from 14 companies who are implementing DevOps in their own organization and/or providing DevOps solutions to other organizations.
Here's what they told us when we asked, "What are the technical solutions you use implementing DevOps?"
We started in the cloud and now we’re implementing on-premises as well. This process has reminded us of how hard it is to make the transition. It’s easy to go back to the old way of doing things, but that’s not in the best interest of your DevOps initiative and will kill whatever DevOps DNA that’s in place.
We use our own product to develop and deploy better quality software more quickly.
Atlassian JIRA, Confluence, HipChat, andJenkins.
We use our own products to automate, drive down cycle time. Remove manual operations, and provide insight into the process. We create technical solutions paths configuring the software, architecture, microservices to divide and conquer complex problems. Develop, deploy, and test independently.
Collaboration and project management tools like Aha, JIRA for developers and support, Confluence, Slack and Zoom. For analysis, we use third party tools like SUMO Logic, Looker and Cabana since we are running two million tests per day.
Our solution is mostly homebrew (since it pre-dates many of the tools that are now available). We have a system that runs tens of thousands of Selenium-based tests for every check-in to source control, compares results to the previous run, and sends out notifications if there are any regressions or fixes. We then have various tools for viewing and analyzing such data (e.g., what check-in broke this test?). We've also built a huge range of diagnostics into our software platform. Developers can go to a live site, log in to an Administration Console, and see client- and server-side logs, toggle log levels up and down on the fly, inspect live client or server-side state, and many other things.
It's a range of delivery in the cloud using continuous delivery. Managing code to get access to repos within authorizations. Automation software to manage workflow of code and getting code into production at the right time – we drink our own champagne. Understand quality and velocity of the code we’re distributing. Sharing quality metrics. Releasing when ready, providing visibility into the pipeline. The benefit is speed to market.
We use a lot of Microsoft, .Net, Visual Studio, Team City, Travis, and Jenkins. More tools around Team City and Confluence. We put big chunks of code in GitHub. We now publish all shells and plugins on GitHub for transparency and customers merging things into code.
For continuous integration, we use Circle CI, Travis CI, Team City, and Jenkins. For continuous delivery and configuration management with use the AWS suite including Elastic Beanstalk, auto-scaling with the Cloud Formation server. We use Capistrano for scripts and to automate deployment. What we use depends on the system, the size of the application, and the platform. We use JSON files for cloud formation so we can turn on and off as we want and reduce costs.
We use our own entire tool setsince it fits in DevOps very well.
Our automation platformsupports different steps in the DevOps toolchain. System integration, testing, moving to pre-production and production environment with dependencies for deployment and orchestration. This is particularly important for customers with multiple technology stack that must be synchronized.
Use our own product for security testing.
We're concerned with how to improve code quality, testing, deployment, and feedback. QOS provides us the ability to clone live production data sets. We assure deployment with our system which will scale without additional effort thanks to consistent APIs. We provide visibility with active IQ and OCI tools providing feedback to the organization to see if additional performance is required, as well as review the efficiency of the system.
Collaboration should happen as early as possible and our product enables this. Flow inside GitLab with Docker files. You can see what’s running in a Kubernetes cluster.
What technical solutions do you use to implement DevOps?
By the way, here's who we spoke to!
Michael Schmidt, Senior Director, Automic
Amit Ashbel, Director of Product Marketing and Cyber Security Evangelist, Checkmarx
Sacha Labourey, CEO and Founder, CloudBees
Samer Fallouh, V.P. Engineering, Dialexa
Andrew Turner, Senior Architect, Dialexa
Andreas Grabner, Technology Strategist, Dynatrace
Anders Wallgren, CTO, Electric Cloud
Job von der Voort, V.P. of Product, GitLab
Charles Kendrick, CTO, Isomorphic Software
Craig Lurey, CTO and Co-Founder, Keeper Security
Josh Atwell, Developer Advocate, NetApp SolidFire
Joan Wrabetz, CTO, Quali
Joe Alfaro, V.P. of Engineering, Sauce Labs
Nikhil Kaul, Product Marketing Manager Testing, SmartBear Software
Harsh Upreti, Product Marketing Manager API, SmartBear Software
Andi Mann, Chief Technology Advocate, Splunk
Opinions expressed by DZone contributors are their own.