Welcome!

@DevOpsSummit Authors: Zakia Bouachraoui, Pat Romanski, Elizabeth White, Yeshim Deniz, Liz McMillan

Related Topics: @DevOpsSummit, Apache

@DevOpsSummit: Blog Post

Chef Recipes By @ScripRock | @DevOpsSummit [#DevOps #Containers #GuardRail]

Generating Chef Recipes from Existing Configs

Generating Chef Recipes from Existing Configs

We've covered the benefits and pitfalls of configuration management tools like Chef in many articles. But let's assume you've done your homework and decided Chef is the tool for you. How do you get started?

Funnily enough, one of the inspirations for ScriptRock was a not-so-successful Chef deployment. Only a poor craftsman blames his tools, so rather than pointing the finger at Chef we reflected on what we had done wrong. The problems we encountered trying to move a large, brown-field infrastructure to Chef, and to get culture, people, and processes to change at the same time, drove us to find a sound method for enterprise automation.

Essentially, we had put the cart before the horse: we started automating our infrastructure before we understood it. Without documentation of existing configuration state and scalable validation for the changes we were making, our automation efforts were bound to lead us in circles. 

So, what did we do? We came up with our "three waves" methodology: visibility, control, automation. While GuardRail is built to make those steps as easy possible, we think you'll benefit from following those steps regardless of what tooling you choose.

1. Visibility

The first step to making systemic changes to your infrastructure (or even just avoiding outages) is to know what you have. Historically this has been handled through barbaric methods like Word docs and spreadsheets. GuardRail starts by scanning nodes (Windows, *nix, cloud apps, etc) for configuration state, generating total state documentation that is completely up to date.

2. Control

Once you know what you have you want to be able to anticipate and validate changes to it. You expect test driven development from the dev team so why should there be a lesser standard for Ops? In GuardRail, this just means selecting the changed configuration items from a dev or QA environment and adding them to a policy. Scan data is turned into executable documentation to validate any changes so you know you're never going off the rails.

3. Automation

This is the golden ring, and if you've done the preparatory work you will reap your just reward. (The same goes if you rushed into automation without doing the prep work, but it will be an ironic Twilight Zone reward that's actually bad.) GuardRail has already captured the state of your development environment or existing infrastructure in a machine readable format, so now it's just a matter of selecting "Recipe" from a dropdown to get it as a Chef Recipe.

Get Started

If you want to compare Chef to other tools in your environment, GuardRail also exports to the syntaxes of PowerShell DSC, Puppet, Ansible, Salt, and Docker. You can see the whole thing in action in this video from TechEd 2014. It's free forever on up to five nodes and doesn't require a credit card to start. If you want to see it in action at ChefConf, come by and talk to us at booth #316.

Read the original blog entry...

More Stories By ScriptRock Blog

ScriptRock makes GuardRail, a DevOps-ready platform for configuration monitoring.

Realizing we were spending way too much time digging up, cataloguing, and tracking machine configurations, we began writing our own scripts and tools to handle what is normally an enormous chore. Then we took the concept a step further, giving it a beautiful interface and making it simple enough for our bosses to understand. We named it GuardRail after its function — to allow businesses to move fast and stay safe.

GuardRail scans and tracks much more than just servers in a datacenter. It works with network hardware, Cloud service providers, CloudFlare, Android devices, infrastructure, and more.

@DevOpsSummit Stories
When building large, cloud-based applications that operate at a high scale, it’s important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. “Fly two mistakes high” is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, will discuss how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
Digital transformation is about embracing digital technologies into a company's culture to better connect with its customers, automate processes, create better tools, enter new markets, etc. Such a transformation requires continuous orchestration across teams and an environment based on open collaboration and daily experiments. In his session at 21st Cloud Expo, Alex Casalboni, Technical (Cloud) Evangelist at Cloud Academy, explored and discussed the most urgent unsolved challenges to achieve full cloud literacy in the enterprise world.
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO Silicon Valley 2019 will cover all of these tools, with the most comprehensive program and with 222 rockstar speakers throughout our industry presenting 22 Keynotes and General Sessions, 250 Breakout Sessions along 10 Tracks, as well as our signature Power Panels. Our Expo Floor will bring together the leading global 200 companies throughout the world of Cloud Computing, DevOps, IoT, Smart Cities, FinTech, Digital Transformation, and all they entail. As your enterprise creates a vision and strategy that enables you to create your own unique, long-term success, learning about all the technologies involved is essential. Companies today not only form multi-cloud and hybrid cloud architectures, but create them with built-in cognitive capabilities.
Hackers took three days to identify and exploit a known vulnerability in Equifax’s web applications. I will share new data that reveals why three days (at most) is the new normal for DevSecOps teams to move new business /security requirements from design into production. This session aims to enlighten DevOps teams, security and development professionals by sharing results from the 4th annual State of the Software Supply Chain Report -- a blend of public and proprietary data with expert research and analysis.Attendees can join this session to better understand how DevSecOps teams are applying lessons from W. Edwards Deming (circa 1982), Malcolm Goldrath (circa 1984) and Gene Kim (circa 2013) to improve their ability to respond to new business requirements and cyber risks.
DevOpsSUMMIT at CloudEXPO, to be held June 25-26, 2019 at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Among the proven benefits, DevOps is correlated with 20% faster time-to-market, 22% improvement in quality, and 18% reduction in dev and ops costs, according to research firm Vanson-Bourne. It is changing the way IT works, how businesses interact with customers, and how organizations are buying, building, and delivering software.