This kind of Chef Solo is still fine. (Stephen Lauck, a Chef employee, is lead guitarist in Midnight Chaser.)Chef Solo was the original Chef. Remember the bad old days before the Chef server existed as a product, and the only way to use Chef was to scp (or worse, ftp) giant tarballs of recipes & cookbooks from system to system? Five years later, we not only have a robust & scalable Chef server, bu
When talking about the management of complex systems, orchestration is always a hot topic. This is because orchestration is often seen as the easiest way to represent and model complex systems, as well as provide a path to delivering complex systems. Most often orchestration is represented through a topology model. What is a topology model you ask? A description of the order-of-operations across a
With the continued popularity of Docker and containerization generally, the concept of immutable infrastructure has again come to the fore. Immutable infrastructure is generally defined as a stack that you build once (be it a virtual machine image, container image, or something else), run one or many instances of, and never change again. The deployment model is to terminate the instance/container
This article is cross-posted from https://sethvargo.com/berkshelf-workflow/. There are only two fundamental assumptions for working with Berkshelf: 1. Each cookbook is a uniquely packaged and versioned artifact 2. You have a centralized artifact store that exposes a dependency API and/or is indexable by the Berkshelf API Each cookbook is it own unit of infrastructure and should be treated as such.
More than likely most of you are familiar with Linux containers but let’s briefly review what the buzz is about. Application containers are an operating system feature that allows you to run your app in an isolated environment without the need for a separate kernel. They’re kind of like a mini-VM without all the overhead. Containers give you a great way to start and stop applications and control t
Ohai Chefs, The first version of Chef Development Kit (a.k.a. Chef DK) is here. What is Chef DK?Chef DK is a package that contains all the development tools you will need when coding Chef. It combines the best of the breed tools developed by Chef community with Chef Client. Here is what you can do with Chef DK: Get your cookbook dependencies under control and have a sane way of composing the cookb
One of the most useful extensions available to Chef cookbook authors is the ability to write and use any arbitrary Ruby code as a library. These libraries are often no more than a few lines long, but can also be as simple or as sophisticated as you want. Once written, the methods in the library can be re-used by recipes within any cookbook that depends on it. In this blog post, I’ll give you a qui
In a way, building IT infrastructure isn’t particularly exciting. Want to turn a Linux server into a MySQL database server? Enter some commands to install MySQL. Congratulations, you have successfully used some data (yum -y install mysql-server) to change the generic model (the out-of-the-box operating system). Much of our infrastructure is built the same way. Chef takes this idea to its logical c
“If roles are evil, what about Al-Qaeda?” You may laugh, but this is an actual quote from a session at the Opscode Community Summit this year. I want to dive deeper into the community’s apparent dislike for roles in Chef, explain why I think they are still useful, and outline some design patterns for using both them and role cookbooks effectively. “Stahp Using Roles”I think the Chef community’s re
In Chef 11.8, we’re excited to introduce local mode with `chef-client -z`. Designed to get people up and running with Chef as quickly as possible, local mode harnesses the power of chef-zero to let you run recipes and work with the full power of Chef locally without the need to set up a server, register and grab keys, configure the client, or switch to root. It is designed to handle many scenarios
SSL and Chef As Chef has grown up, we've found that we've needed to revisit some decisions we made when Chef was an unruly upstart open source project. One such decision is how Chef handles HTTPS connections by default. Currently, Chef defaults to not verifying certificates when it makes HTTPS connections. There are a number of reasons why this choice made sense at the time, but now they're either
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く