Please join the conversation in #foodfightshow on Freenode.
Brandon Burton (@solarce) took a microphone to this year’s Monitorama and was able to record a bunch of DevOps Delicacies for the show. It’s taken Nathen a while to get these edited and ready for release but here they are!
Join us as we discuss the Netflix OSS tools.
knife ec2 server create --bake - https://github.com/opscode/knife-ec2/pull/110This is another FoodShipShow Joint Production!
Join us as we wrap-up #ChefConf 2013.
You can now subscribe to the Food Fight Show email newsletter.
In this episode, we sat down with Jesse Nelson, Miah Johnson and Matthieu Sauve-Frankel at Chefconf
Be sure to checkout Crest, a greate demonstration of using Push Jobs like primitives.
You can now subscribe to the Food Fight Show email newsletter.
This is the inaugural FoodShipShow Joint Production!
You can now subscribe to the Food Fight Show email newsletter.
Join us as we discuss Docker and linux containers.
In this episode, we discuss SmartOS and other Solaris derivatives.
Why use Illumos?
kstat:
[root@headnode (latisys-va:0) ~]# kstat -l | wc -l
40210
Instruments - A GarageBand interface to DTrace on the Mac.
prstat -Lm - microstate accounting of all processes and threadsprctl / prstat -JprstatdladmIn this episode, we sat down with Gene Kim and Jez Humble to discuss The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.
In this episode, we sat down with Shay Banon, Karel Minarik, Rashid Khan, and Dan Phrawzty to discuss elasticsearch.
In other news, Bryan is about to start a new job at Cycle Computing
In this episode, we sat down with Miah Johnson, Ranjib Dey, Doug Ireton, Chris McClimans, Joshua Timberman, and Seth Vargo to discuss Libraries, Definitions and LWRPs.
A lightweight resource is a custom resource that creates an abstract approach for defining a set of actions and (for each action) a set of attributes and validation parameters. A lightweight resource relies on a lightweight provider to take the necessary steps to bring a piece of the system to a desired state.
A lightweight provider is a custom provider that is designed to take the steps that are required to bring a piece of the system into a specific state based on an action that is defined by a lightweight resource.
A library allows arbitrary Ruby code to be included in a cookbook, either as a way to extend the Chef language or to implement a new class directly. A library is defined in /libraries/library_name.rb for each cookbook. A library that is included in a cookbook is automatically required and will be available to all recipes, attributes, file definitions, providers, and definitions. A library is defined in the library_name.rb, which is found in the libraries folder for each cookbook. The contents of a library will determine the potential uses of that library in a cookbook.
Simple example for having a module in a Chef recipe
A definition is used to create a resource by stringing together one (or more) existing resources. A definition is not a resource and it does not take any actions by itself. A definition is replaced by one (or more) resources, and it then takes actions on behalf of those resources. There is no limit to the number of resources that can be part of a definition. All definitions within a cookbook must be located in the definitions/ folder. A definition is never declared into a cookbook. A definition is best-used when:
In this episode, we sat down with Matt Wise, Ben Hartshorne and Charity Majors to talk about using zookeeper with Chef and Puppet.
This is a cross-post from Hangops. Nathen joined Brandon on this week’s Hangops which was all about Chef 11.
In this episode, we sat down with Baron Schwartz to discuss his presentation on Adaptive Fault Detection. Jason Dixon and Brandon Burton joined the conversation.
In this episode, we sit down with some of the engineering team at Opscode to discuss the recently released Chef 11.
In this episode, we discuss the role DevOps can play in helping science overcome some of the most pressing research challenges such as climate change and canceer research.
In this episode, we discuss Logstash and The logstash Book with Jordan Sissel and James Turnbull.
In this episode, we sit down with Brendan Gregg of Joyent to discuss performance and his recent article, Thinking Methodically about Performance.
This episode was started with a tweet:
@nathenharvey are you still recommending capistrano deploys in a chef infrastructure? I want to know what the best practices are
Should you deploy your applicaiton with Chef’s deploy resource or should you use Capistrano or something like it? To an extent, this comes down to a question of push vs. pull.
On the panel we discuss the merits of both and reach a conclusion something along the lines of:
Use whichever method best suits your team and your application’s workflow. In either case, it makes sense to leverage Chef’s search capability to help drive the deployment.
A thread on the mailing list came up during our discussion. Although not directly related to our conversation, the thread is worth reading. Joshua Timberman schooled all of us on the use of the template resource’s local attribute. This was certainly something new to most, if not all, of the panelists. Joshua wrote up blog post, Local Templates for Application Configuration exploring the use of local templates.