サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
掃除・片付け
www.chef.io
Today we launched our new open source project, Habitat, for application automation. We hope you’ll try Habitat and join us in taking automation to the next level. What follows is a blog from Adam Jacob detailing the philosophy behind Habitat and what this new technology delivers – automation that travels with the application. You can watch Adam unveil and demonstrate Habitat here. Why Habitat? Hab
AWS OpsWorks for Chef Will be Discontinued in All AWS Regions on May 26, 2024.Progress Chef SaaS is a purpose-built offering to manage your infrastructure for OpsWorks customers with an easy three-step migration process. Find More Information Here AWS OpsWorks is an application management service that makes it easy to deploy and operate applications of all shapes and sizes. OpsWorks supports Chef
On Tuesday, we announced the release of the InSpec infrastructure testing framework as part of the release of Chef Compliance. Today we would like to dive into how and why we decided to create InSpec, from its journey as a Serverspec extension to its current state as a standalone project. Serverspec for compliance testing Our startup VulcanoSec, acquired by Chef earlier this year, was founded to s
What these commands do is talk to a service we have called omnitruck and that downloads a shortish 600-line shell script which does the logic of figuring out what kind of distribution you are running and then downloads the correct s3 package artifacts for you (with some handling of version numbers, and nightlies and command line options to install chefdk, etc). These commands all follow the patter
Operational observability for every team in one place. Chef® Automate™ is an enterprise platform that allows developers, operations and security engineers to collaborate effortlessly on delivering application & infrastructure changes at the speed of business. Chef Automate provides actionable insights with enterprise scale and performance across multiple data centers and cloud providers.
Today, we are excited to announce the availability of Chef Client 12.0.0 which complements Chef Server 12. This version introduces numerous improvements to Chef Client while retaining backwards compatibility with current versions of Chef Client and Chef Server. ## MVP This release wouldn’t be possible without the help of Chef community along the way. We have around 70 contributions in this release
Ohai Chefs! Today, after a thorough RC testing phase that included a great amount of feedback and contribution from the Chef community, we’re pleased to announce the GA release of Chef Server 12. This release brings the previously premium features of Enterprise Chef, namely multi-tenancy and role-based access control, into Open Source Chef. ## What’s New Chef Server 12 brings a host of improvement
Chef Provisioning is now a Release Candidate, included in the ChefDK version 0.3.4! This powerful new Chef featureset lets you idempotently create and converge machines, images, load balancers and other infrastructure, no matter where they are: cloud, bare metal, virtual machines, or containers. This is the next step in configuration management: Infrastructure as Code. Chef already does a bang-up
_Update: 2014-10-17: We have released an update of Chef Server products and Analytics to address the POODLE attack as well as other recently announced vulnerabilites._ A new attack on SSL 3.0 has been announced. This attack is fully detailed in this document. ## Affected Products See section Remediation below for a mitigation that can be applied to affected products until patched releases are avai
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
The Bourne Shell – fifth film in the trilogy. Jason Bourne tries to patch servers against obscure bug. No fights or car chases. Avoid. — Charles Arthur (@charlesarthur) September 27, 2014 To nobody’s delight and amusement, this has been the year of critical, remotely-exploitable security vulnerabilities. First we had the Heartbleed bug in OpenSSL, and last week, we had Shellshock, an environment-v
Chef is the Platform for Automating Your Infrastructure on Amazon Web Services.Chef Automate, Chef’s Continuous Automation solution is tightly integrated with Amazon Web Services (AWS). If you’re using AWS now, Chef gives you a single, unified way to automate AWS services and resources. If you’re thinking of using AWS, Chef will help you migrate your workloads at your own pace, and with complete c
Chef is used by companies of all shapes and sizes, from tiny startups to the largest companies in the world, to create businesses where infrastructure moves as fast as software. One thing that binds all these different companies together, regardless of size, is this critical fact: The people who build and manage infrastructure are the people who best understand the unique requirements that make th
Today we’d like to share the Supermarket debut of the PowerShell DSC cookbook for Chef, an early preview of Chef integration with PowerShell Desired State Configuration (DSC) on Windows. This cookbook allows you to author recipes using any DSC resources available on your system, seamlessly surfacing them as Chef resources you can use in your cookbooks. Integration at this level can greatly expand
This week, Chef released a version of the Chef client that can run inside a Linux container. This container-friendly client is called chef-container. In this post we’ll give you an introduction to chef-container, its purpose and its components. We’ll also tell you about a new knife plugin for managing container images. Then, we’ll show you how to launch an instance of Apache2, running inside a Doc
Managing users is one of the contrived (but applicable) examples we use in Chef Fundamentals training to help onboard new Chefs to the idea of writing data-driven cookbooks. Whenever I run a training class, I typically end that module by talking around other ways to manage users and SSH keys (hopefully you’re not still using passwords). Outside of training classes, this topic comes up quite a bit
Hi! This is a long blog post, but it has a few important action items at its conclusion. If you care about the evolution of the Chef Community, or are considering going to the Community Summit, you should totally read it. Here are the actionable parts: If you like building Chef (through contributing, advocating, or advising), I invite you to join us in #chef on irc.freenode.net.We will have a bi-w
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
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
This morning we announced we’ve changed the company name from Opscode to Chef. Aaaaaaand… the Earth is still spinning. As we circulated the idea of changing our company name amongst employees and some members of the Chef Community (and some total strangers, too) the reactions generally fell into one of four categories: Awesome, makes sense. It’s about time. So what? Um, what’s Opscode? So, Opscode
It is very exciting to announce the release of Test Kitchen 1.0.0 this week. This history of this project is long and winding but if you’re interested check out the Test Kitchen #ChefConf 2013 talk for the background. Test Kitchen is a test harness tool to execute your configured code on one or more platforms in isolation. In the context of Chef, Test Kitchen helps you run your cookbooks in the va
One great thing about the Chef community is how various people have dreamed up ways to use Chef. One of the most popular patterns is the wrapper cookbook, first popularized by Awesome Chef Bryan Berry‘s blog post, How to Write Reusable Chef Cookbooks, Gangnam Style. Bryan’s post is barely a year old, and we’ve all learned a lot from using and writing wrapper cookbooks. In this post I’ll discuss so
“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
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
次のページ
このページを最初にブックマークしてみませんか?
『Chef Software DevOps Automation Solutions | Chef』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く