devopsy.kinsta.cloud

Tag: best devops tools

  • Meet the Winners of the 2020 DevOps Dozen² Awards

    Meet the Winners of the 2020 DevOps Dozen² Awards

    This is the moment you have all been waiting for. It is time to announce the honorees for the 2020 DevOps Dozen² Awards, and we couldn’t be more excited to share the names of the most outstanding leaders and tools in the DevOps community. Although, I must say, all the finalists have done an amazing job at making the DevOps community better through their mentorship, service and innovative ideas, and every single one is deserving of special recognition.

    The DevOps Dozen Awards recognize the best of the best in the maturing DevOps space and this year’s winners have demonstrated exceptional leadership and support to the community through 2020 and the COVID-19 pandemic. Last year was a tough year for all of us for sure, but it was also a year of agility, innovation and rapid digital transformation. The 2020 honorees have displayed resilience, determination, commitment and willingness to embrace change in a year of unprecedented challenges to drive their business—and the industry—forward. Congratulations to each and every one of the honorees.

    Winners have been chosen from among the finalists with general public voting being weighted for 40% of the final total and our judges selections for 60% of the weighted total. Our team has gone through thousands of votes to pick out the winners in each category—it was not an easy task. Many thanks to our panel of judges for making the hard calls and to everyone who voted and nominated candidates.

    Ladies and gentlemen, I am proud to present to you the 2020 DevOps Dozen² Awards honorees:

    DevOps Dozen Community Awards

    Best DevOps Industry Implementation

    Lloyds Banking Group, the largest financial services organization in the UK, is the winner of the Best DevOps Industry Implementation award. Lloyds Banking Group has invested heavily in driving the adoption of Agile development and DevOps practices across its business to strategically modernize its digital service capabilities and align with customer expectations.

     

    Best DevOps Survey/Analysis/Research

    The Best DevOps Survey/Analysis/Research award goes to Puppet’s 2020 State of DevOps Report. The report focuses on two areas that can help organizations scale their DevOps initiative: a platform approach to software delivery and applying DevOps principles to change management. It is the ninth year in a row that Puppet produces a State of DevOps Report. It is the longest-running and most widely referenced DevOps research in the industry.

    Best DevOps Related Video Series (Video)

    The Best DevOps Related Video Series is DevOps Unbound, a bi-weekly video series that focuses on DevOps, automation, CI/CD and testing. Top industry leaders join the series to explore the challenges and issues that software delivery and IT teams face on a daily basis.

     

    Best DevOps Related Podcast Series (Audio Only)

    The Modern Mainframe: Building a Better Software Delivery Platform is the Best DevOps Related Podcast Series. The Modern Mainframe is a podcast by Compuware that explores mainframe modernization and how to transform mainframe culture, processes and tools with DevOps to help your business compete in a digital age. Building a Better Software Delivery Platform is episode 9 of the podcast, featuring Compuware DevOps Architect Rick Slade.

    Best DevOps Books / eBook of the Year

    Standing On Shoulders: A Leader’s Guide to Digital Transformation by Jack Maher and Carmen DeArdo is the Best DevOps Books / eBook of the Year. This must-read provides leaders with practical, actionable information about the breadth of Agile, Lean and DevOps topics that are generally dealt with individually; and explains how each of these are necessary but alone are not sufficient to avoid market disruption of your business. The authors focus on how to build an employee and customer-obsessed culture with an organizational structure that drives speed and efficiency, while leveraging technology to enable speed to value that is faster, safer, better and cheaper.

    Top DevOps Evangelist

    The Top DevOps Evangelist award goes to Helen Beal, chief ambassador at DevOps Institute. Helen is a well-known DevOps evangelist leading the DevOps Institute Ambassador program’s efforts to provide broad-based thought leadership and localization. She is an analyst at Accelerated Strategies Group and an editor at InfoQ. Recently, Helen has been working with a group of ambassadors to develop a new, online DevOps Capability Assessment (DOCA), launching in 2021. Taking on strategic advisor roles with Plutora and Moogsoft has given her the opportunity to dive deep into value stream thinking and observability. She is the host of Day-to-Day DevOps, a BrightTalk series that focuses on topics ranging from neuroscience, to ChatOps, to AIOps and everything DevOps related.

    Best DevOps Transformation (Non-Vendor)

    The winner of the Best DevOps Transformation award is Fidelity Investments, a financial services company that supports financial institutions with innovative investment and technology solutions to grow their businesses. Fidelity’s embrace of cloud-based platforms has yielded tangible improvements, such as better operational resiliency.


    Best DevOps Virtual Event of the Year

    The DevOps Dozen award for the Best DevOps Virtual Event of the Year goes to DevOps World 2020. The virtual event, featuring more than 100 business and technical breakout sessions, focused on how DevOps is transforming the world of software delivery and how businesses are adapting their ways of thinking during the COVID-19 pandemic. Top industry leaders discussed where DevOps is headed and how the audience can best leverage advanced practices to succeed in the future.

    Most Innovative DevOps Open Source Project

    Grafana Loki was chosen as the Most Innovative DevOps Open Source Project. Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus.

     

     

    DevOps Executive of the Year

    The DevOps Executive of the Year is GitLab CEO and Co-Founder Sid Sijbrandij. Sid’s career path has been anything but traditional. He saw the first Ruby code in 2007 and loved it so much

    that he taught himself how to program. It was during his time as a Ruby programmer that he first encountered GitLab, and quickly discovered his passion for open source.

    In 2012, he helped commercialize GitLab, and by 2015, he led the company through Y-Combinator’s Winter 2015 batch. Under his leadership, the company has experienced 50x growth in the last five years, expanded from nine to more than 1,300 remote team members across 65+ countries and regions and is now valued at $2.75 billion. A champion of the open source community and a pioneer in scaling remote organizations, Sid is altering conventional wisdom on DevOps practice.

    Best DevOps Presentation of the Year

    On Ramp to Open DevOps for Mainframe by George DeCandio, chief technology officer of the Mainframe Software Division at Broadcom, is the winner of the Best DevOps Presentation of the Year award. In this keynote presentation, George DeCandio explained what you need to adopt an open strategy and how you can integrate with existing DevOps tools such as Git and Jenkins, or into existing cross-platform CI/CD pipelines. George discussed how Zowe, OMP’s first project devoted to the mainframe, is opening mainframe system commands, data sets and source libraries so you can integrate with tools that know nothing about mainframe.

    Best devopsy.kinsta.cloud Article of the Year

    How to Reduce Engineer Burnout During COVID-19 by Henry Jewkes, staff software engineer at Split, is the Best devopsy.kinsta.cloud Article of the Year. Henry explains how to cope with burnout effectively as it becomes increasingly common during the COVID-19 pandemic.

     

    DevOps Dozen Tools and Services Awards

    Best End to End DevOps Tool/Service

    The winner of the Best End to End DevOps Tool/Service in 2020 is GitLab. GitLab has demonstrated to be the most efficient solution for DevOps teams to collaborate and build software. The GitLab solution is the result of the collaboration between thousands of community contributors and feedback from the more than 100,000 organizations that have adopted GitLab to power their DevOps transformations. The GitLab community contributes code, documentation, translation, design and product ideas based on their real-world challenges, making GitLab more useful and valuable.

    Best DevOps Repo/GitOps Tool/Service

    The DevOps Dozen award for the Best DevOps Repo/GitOps Tool/Service goes to GitHub, the most popular open-source version control code repository. GitHub is great to manage and maintain code in the cloud and contribute to projects quickly with automatic environment setup.

     

    Best CI/CD Tool

    CircleCI was chosen, by the public and the judges, as the Best CI/CD Tool. CircleCI is the leading CI/CD solution for software innovation at scale. The CircleCI platform allows teams to build and deliver software in the cloud or on their own infrastructure. CircleCI manages more than 35 million builds per month on Linux, macOS and Windows.


    Best Value Stream Management Tool

    The 2020 DevOps Dozen winner of the Best Value Stream Management Tool is Digital.ai Value Stream Platform. Digital.ai enables the world’s largest enterprises to accelerate their digital transformation initiatives by combining industry-leading enterprise Agile planning, application security, continuous testing, software delivery and AI-powered analytics in the first intelligent value stream platform. Digital.ai Value Stream Platform provides a unique view of the software delivery lifecycle through the customer experience lens to better align with business objectives and scale Agile and DevOps processes.

    The Digital.ai Value Stream Platform features end-to-end connectivity, visibility with AI-powered analytics, continuous testing and quality, release management and flow optimization, and measurable outcomes through quantified metrics. The platform allows organizations to set business goals based upon market needs, deliver products and technologies to achieve those goals, measure and analyze results, and make adjustments to continuously improve.

    Best Observability Solution

    The award for Best Observability Solution goes to Splunk Observability Suite, a comprehensive combination of solutions designed to help IT and DevOps teams tackle new monitoring challenges that other tools haven’t been able to effectively address. The Observability Suite helps users maintain the highest levels of business performance and adaptability, improve release quality and velocity, improve developer efficiency, minimize downtime, and deliver world-class digital experiences.

    Best DevSecOps Solution

    JFrog Xray was voted the Best DevSecOps Solution of 2020. JFrog Xray is a universal impact analysis product enhancing artifact security, container security and OSS license compliance across your DevSecOps pipeline. JFrog Xray scans your artifacts, builds and Release Bundles for OSS components being used, and detects security vulnerabilities and licenses in your software components.

    Best Testing Service/Tool

    Tricentis Tosca, a continuous testing platform that accelerates testing to keep pace with Agile and DevOps, is the winner of the Best Testing Service/Tool of 2020. With the industry’s most innovative functional testing technologies, Tricentis Tosca breaks through the barriers experienced with conventional testing tools. Simplifying end-to-end functional testing, Tricentis Tosca automates tests across all layers of modern enterprise architectures.

    Best Kubernetes Platform/Service

    The Best Kubernetes Platform/Service award goes to Red Hat OpenShift Container Platform. 

    Red Hat OpenShift is an open source enterprise Kubernetes platform offering a consistent hybrid cloud foundation for building and scaling containerized applications.

    Best Cloud Native Security Solution/Service

    Styra’s Declarative Authorization Service (DAS) is the winner of the Best Cloud Native Security Solution/Service award. Styra DAS was purpose-built to solve the authorization challenges of cloud-native, containerized application, and the infrastructure they run upon. Built on the open source project Open Policy Agent (OPA), Styra policy-as-code solutions have been proven in production, at scale, in many of the largest cloud-native deployments in production today.

    Styra DAS allows enterprises to define, enforce and validate authorization policy across services, teams, clusters and clouds. As businesses move their cloud-native applications from development through to production, Styra DAS provides the tooling to minimize the risk of human error, offload compliance overhead and ensure security and compliance best practices are enforced across your environment. Styra DAS simplifies policy creation with a built-in library of best practices and security policies, as well as a point and click interface for building custom policy from scratch.

    Best DevOps for Mainframe Solution

    It was very difficult to choose a winner in this category. There was a tie between two solutions, CA Endevor Bridge for Git by Broadcom and Compuware’s Topaz, and after a long discussion the judges decided that both should be honored as the Best DevOps for Mainframe Solutions of 2020.

    CA Endevor Bridge for Git is a component of the CA Endevor Integrations for Enterprise DevOps. It connects Git to Endevor via an Enterprise Git Server, such as GitHub, Bitbucket or GitLab. Git as well as traditional mainframe developers can easily collaborate on the same mainframe application managed in Endevor. Only code that is pushed from local Git repository to the Enterprise Git repository is recognized by the integration and gets propagated to Endevor.

    Topaz is a modern Agile platform of mainframe development and testing tools that integrates into the DevOps toolchain, empowering any developer, regardless of experience, to understand and work on any program, no matter how old or complex, so that their organizations can easily maintain and innovate from their base of mainframe investments.

    Best DevOps for DataOps/Database Solution

    The Best DevOps for DataOps/Database Solution is InfluxDB. Developed by InfluxData, InfluxDB is an open-source time series database that empowers developers to build IoT, analytics and monitoring software. It is purpose-built to handle the massive volumes and countless sources of time-stamped data produced by sensors, applications and infrastructure.


    Best New DevOps Tool/Service Provider

    The winner of this category is Opsera, the first continuous orchestration platform for DevOps teams. The Opsera platform automates any CI/CD toolchain, enables declarative pipelines and provides unified insights across the entire software delivery process.

     

     

     

    Winners will receive both digital and physical trophies and badges celebrating their achievements.

    Thanks for supporting devopsy.kinsta.cloud and the DevOps community. For more information, visit the 2020 DevOps Dozen² Awards website and stay tuned for the 2021 DevOps Dozen Awards.

  • But Wait, There’s More! The Trouble With DevOps Tools

    But Wait, There’s More! The Trouble With DevOps Tools

    DevOps tools today increasingly are no longer out-of-the-box ready for use. And that’s an aggravating issue

    Imagine you bought a new power tool—a sweet battery-powered drill/screwdriver that did everything you needed.

    Imagine it looked as though it ran on its own, but when you got it out of the box, you discovered that it didn’t come with a battery.

    Imagine you got the battery, and only after the battery was installed you discovered that it needed a specialized wrench/chuck to install and remove bits. And you had to go buy that.

    Imagine you got the chuck and were all set to go, only to discover that it would slip and normal drill bits wouldn’t turn unless you had a specialized adapter.

    toolsThat’s what our tools environment in DevOps has become. And we need to demand better.

    If your software requires X and Y and Z to be useful—whether you are commercial or open source, whether X and Y and Z are a million bucks or zero—state it before install.

    We’re setting up an entirely new environment, stretching things a bit for an internal project, and honestly, the amount of “Oh yeah, this is required, too” that we’re finding out after install is insane. We have done our research; we should not be getting surprised by “But wait! There’s more!” type installs.

    For an industry that insists on plug-and-play for all OSes and every odd bit of hardware ever dreamed up, we sure let software steamroll us. Vendors need to be clear about what will be required to run the tool and what will be required to run it effectively before we waste our time. Because there are some dependencies we’re not willing to accept, for usability reasons and/or security reasons. And if, under the covers, the tool does exactly the same thing as another tool … then what, exactly, is the value-add? It better be good.

    We’re just one DevOps group—and a small one at that—but we have decided for this project not to use tools that dupe us into thinking they’re usable out of the box, then immediately require us to install something else. Or at least we’re trying. This has gotten so prevalent that in a couple of areas, we’re struggling. After all, the software still has to be built.

    It’s a good thing drill manufacturers don’t think that way. Maybe there is hope.

    Meanwhile, we’ll keep trying to do what you all are doing: kicking rear and keeping systems running.

  • The Right DevOps Tool for the Job

    The Right DevOps Tool for the Job

    Innovation and environment are only two factors in determining which DevOps tools are best for your organization

    Any time there is a movement in IT that involves a new space and new toolsets, there is sudden growth, then inevitably consolidation and, finally, a selection of tools that suit the needs of most customers. Then the cycle starts over. Usually by this point, users have developed a defense mechanism about their choices regarding which solutions to implement and discussions can get heated.

    I’m happy to say that the last bit—heated discussions—has not occurred with DevOps the way it has with other technologies (think the browser wars, OS dominance or even cloud service provider preferences). There is the occasional “You’re doing it wrong,” but not the wild-eyed flame-wars so far.

    But the other two? Yes, yes indeed. DevOps has been through a couple of cycles, and the end is nowhere in sight. I don’t necessarily see that as a bad thing; in fact, as long as innovation is occurring, you have the opportunity to look at changes and decide what can best help your DevOps efforts.

    My mantra since the language wars was that C, C++, VB, etc., were the “right tools for the job.” I have kept that mantra for all of IT. It is easy to adapt the tools you are familiar with—to do more than they were designed to—and most shops have fallen into this trap at some point. But a serious look at what is available and where the market seems to be evolving usually stops this kind of adaptation.

    Some shops use Jenkins for far more than it was designed for. It’s a great tool, but at some point, the benefits of using tools aimed at a given piece of the DevOps toolchain outweighs the fact that Jenkins could handle that bit.

    The popularity of Puppet is starting to cause the same issues, if anecdotal evidence is to be believed. In words I use to my children, “Just because you can, doesn’t mean you should.”

    The environment always plays a role in the “right tool for the job,” but it should not be the major factor. Having a DevOps tool that you already know that could do the job is one answer—but quite often not the best answer.

    So, use resources like us here at devopsy.kinsta.cloud, and your favorite site for IT ratings and reviews. Do some feature research, think about what it would take to make your existing tools do the same job, and consider bringing in new tools to achieve a given goal. We see so much change these days that sticking with what you know on this one tiny bit of the toolchain, may seem reasonable, but make sure you are not missing out on additional functionality or suitability to task over the long term.

    — Don Macvittie

  • DevOps Stack on a Shoestring Budget

    DevOps Stack on a Shoestring Budget

    There are competing products, both open source and licensed, in any DevOps area that you can think of. The Operations groups in companies tend to accumulate such applications over time as determined by ongoing projects. Team members’ familiarity with a certain application could be a factor in adding it to the tools stack.

    Companies, therefore, end up with a mixed bag of freeware, open source or community versions of applications and software licensed from the get-go. In a startup environment where the Operations group might be on a shoestring budget, it might make sense to build the DevOps infrastructure on the cheap; using open source software (OSS) products would be one way to achieve that goal.

    The Shoestring Budget

    Below is a list of some of the applications and software for an effective DevOps environment. The list here includes only core applications that are needed to build the DevOps infrastructure. The basic communication and productivity tools that would be used by everyone in the company—and usually managed by IT—are not in the scope. Neither are the compilers and debugging and testing tools used by product development teams. However, in a small company setting, managing all kinds of tools might drop into the laps of the same people driving the DevOps initiatives.

    The objective here is to make a list of software that could be used license-free. That means some of the obvious applications in certain areas might not make it to the list. That doesn’t mean that the open source alternative is an inferior choice; availability of reliable product support is a major factor in most of the software purchase decision-making processes, and licensed software scores over OSS on that front.

    Git for Source Code Management (SCM)

    A code repository might be the first DevOps infrastructure component that would be set up even before a product idea is formalized into a company. Also, both developers and DevOps engineers need it for collaboration, within their own teams and across various engineering teams. Typically in a startup, developers get started with the DevOps work such as build and deployment automation before a dedicated DevOps team would even be part of the engineering staff.   

    In this category, It is hard toimagine choosing anything other than Git. Even though GitHub is not free for maintaining private code repositories, Git server can be setup on-premise for free. AWS has CodeCommit, another SaaS version of Git, as one of the services, and there is no extra cost for using it if you are already on AWS.

    Bugzilla for Bug Tracking

    The popular Atlassian suite of products, JIRA in this category and Confluence for collaborative documentation, seems to be default choices in respective categories. But, both on-premise and SaaS offerings of  JIRA and Confluence are licensed. Bugzilla is a powerful OSS alternative to JIRA that can support a large user base and it has been around for a while.

    If you are open to customizing Bugzilla for specific requirements, it could work better than some of its licensed competitions. Though its primary use is bug tracking, Bugzilla is feature-rich enough to be used for managing all phases of software development and even as an IT ticketing system.

    MediaWiki for Collaborative Documentation

    Though there are multiple, open source wiki applications available, MediaWiki might be the best supported when it comes to the availability of third-party extensions. Out-of-the-box features of MediaWiki are limited, but it can be extended using the free extensions available. Such customizations are very straightforward.

    Jenkins as Build & Continuous Integration Platform

    Though there is an enterprise offering of Jenkins from CloudBees, its open source version combined with freely downloadable plugins would make up a powerful integration platform for build, release and deployment automation—and any other areas in between. Describing Jenkins any more here would be simply preaching to the choir.

    Artifactory for Artifacts Management

    This is one of the applications a lot of companies might not have in their DevOps stack in the initial stage. However, the need to store built artifacts and to cache third-party tools is real, and the packages and binaries would normally end up in S3 buckets or shared filer volumes. There is no reason for not using the OSS version of Artifactory right from the beginning, as it covers the storage requirements already mentioned and much more:

    • Automated uploading of artifacts as part of the build process, typically done from Jenkins
    • Caching third-party tools locally for builds and deployments
    • Storing software artifacts for meeting build dependencies
    • Distributing packages and third-party tools for deployments

    Ansible for Configuration Management and Orchestration

    There are two great products in this space that could be used for free: the OSS versions of Puppet and Ansible. If you are on AWS, Chef is also available, at no extra cost, in the form of OpsWorks. But I would recommend Ansible for those getting started for these reasons:

    • It is an agentless tool and beginners would feel safer to roll out automation using it. A configuration management agent can play havoc with production systems if something gets misconfigured inadvertently.
    • Using the playbooks, deployments can be orchestrated very well using Ansible. In many companies, Puppet or Chef primarily covers system management aspects and there would be additional tools for deployments. Ansible simplifies that scenario.
    • Ansible’s support of Python turned out to be more useful, in my experience, than the support of Ruby in Puppet and Chef. The chances of a DevOps engineer knowing Python is much more than Ruby.
    • Ansible’s handling of host inventory is advanced, especially the dynamic generation of inventory lists. The latter feature is compatible with the provisioning of cloud infrastructure where its elasticity demands the use of dynamic inventory lists in configuration management systems.

    Nagios for Monitoring

    A lot of us in the DevOps community despise Nagios for its blandness and lack of features out of the box. But if you are willing to customize it by developing application-specific plugins, it could be converted into a very effective monitoring platform that can be used to consolidate outputs from the rest of the monitoring and various admin applications. I recommend it for these reasons:

    • Writing plugins for Nagios is very simple. Also, there are tons of free plugins available that would meet most of the system-level and third-party component level monitoring.
    • Developing plugins to add application-level monitoring and to integrate with third-party admin applications is easy.
    • When you want to move on to a next generation cloud-based monitoring application such as Datadog, existing Nagios plugins are normally migrated natively or as an integration.

    In a sysadmin environment where coding skills would be in short supply, Nagios could be of limited use as a systems monitoring application. But DevOps teams should treat it as an easily extendable tool that can be used to implement specific and fine-grained monitoring goals of the company.

    ELK for Log Management

    Splunk was instrumental in changing the way we dealt with log files, and, now there are several good products including Loggly, Logentries and Sumo Logic in that space. Though some of these SaaS products have a free tier and that might be enough for a small operation, it is better to start with ELK (Elasticsearch, Logstash and Kibana stack), mainly because the size of the logs can grow very fast and so would the usage of the log management application in the company. ELK requires substantial DevOps resources to set it up and maintain, as there are three applications involved.

    Closing Remarks

    It is important to have these essential applications, or similar ones with comparable features, implemented or made available to empower the engineering  staff. They facilitate the application development, lay the foundation for automation initiatives, and provide the toolkit to maintain production environments 24×7.

    Though it is normal, the organic growth of the DevOps organization and infrastructure can bring in OSS products with overlapping features, mainly because they could be used license-free. Carefully selecting the tools would help avoid the otherwise-inevitable clutter and the confusion later.

    One aspect not discussed is the total cost of use of a software. If SaaS offerings such as GitHub, Datadog and Loggly, and hosted versions of JIRA, Confluence and Artifactory are used, the cost would only be the subscription charges. OSS applications will need computing resources and some amount of customization and administrative overheads, which could add up to the overall cost.  

    If the objective is to minimize total cost, the upfront decision-making can become much more complicated than it looks. However, for a startup or a small company, getting started with the OSS stack for setting up the DevOps infrastructure can be advantageous if the applications are selected carefully.

  • DevOps Dozen – Nominations are now open

    DevOps Dozen – Nominations are now open

    To succeed in todays speed of business, app-centric world the old ways of doing business just don’t work anymore. IT and development teams are being pulled, pushed, stretched and changed into new combinations and configurations. Greater cross-functional cooperation is a must, a culture of cooperation and a new generation of tools that facilitate these are changes are sweeping in like a Tsunami.

    DevOps has appeared like a superhero fighting a villain to combat these issues. Featuring a one-two punch of continuous delivery and continuous integration with a finishing blow of automation, DevOps enables easier and closer collaboration between development and operation teams.

    Whether they be cloud-native “unicorns”, traditional enterprise “horses” or born on the run startups, DevOps is becoming the “way they do things.”

    The field has matured enough where we think it is time to recognize some of the best and brightest.  Our first venture with this is our “DevOps Dozen”  The DevOps Dozen will feature the top 12 vendors in the DevOps space. I know 12 isn’t a lot given the amount of companies in the mix, but we had to start somewhere.

    So how do we get to a dozen from such a large and worthy group? We at devopsy.kinsta.cloud have compiled a list of what we think are the best known DevOps companies. Some of these companies have their product or service listed as well to help identify the face to the name. We have broken them down into several categories to hopefully make it easer to select (tip of the hat to XebiaLabs and their Periodic Table of DevOps for the help with that).

    The DevOps Dozen selections will be made by you our readers in two phases. First we will open the whole list as well as any write ins for those we may have missed. This nomination voting will be open until August 12th. At that point we will take the top 24 company/products who garnered the most nominations. These will be the finalists and we will have a 2nd round of voting for final Dozen.

    Feel free to tweet about the DevOps Dozen using the hashtags: #DevOpsDozen and #DO12

    Please click here to vote for the finalist nominations

    or fill in below

    Create your own user feedback survey