One of the most well-known differences between managing UNIX-like systems and Windows systems is the Windows Registry. Chef has resources for creating, modifying, and deleting Windows Registry keys. Beware that these operations are nonreversible (there is no implicit backup of values, so it may be worth preparing a backup before modifying values), and that they can potentially … read the rest
A large number of managed systems require configuration of software that is outside the scope of the built-in Windows roles and features. Chef has a very handy resource for installing arbitrary software onto a Windows host through the windows_package resource, which behaves somewhat like the Linux-based package resource only for Windows-specific installations. The windows_package resource is capable of installing software … read the rest
Similar to Linux script resources for bash, ruby, and so on, Chef can execute arbitrarily-defined Windows batch scripts through the command interpreter. When these resources are used, Chef compiles the contents of the batch script as defined in the resource block’s code attribute and then deposits it on the managed host and it is executed from there.
Take caution when … read the rest
While using Chef for Windows, there are multiple backends for the Windows feature resource—DISM and servermanagercmd. Each one has a specific Ruby class that will be used based on the determined backend as follows:
- Chef::Provider::WindowsFeature::DISM: This uses DISM to manage roles/features (default unless DISM is not present)
- Chef::Provider::WindowsFeature::ServerManagerCmd: This uses Server Manager to manage roles/features (the fallback
Similar to how Linux distributions have package management tools and a repository of packages, Windows has long had built-in packages that come with the OS. Both desktop and server releases of Windows have installable components out of the box, with servers having more than desktops.
In Windows parlance, roles are similar to Chef’s notion of roles—a collection of software packages … read the rest
When managing Windows with Chef, there are some Windows-specific resources that are available to you as part of the Windows stack. This section covers those resources that are specific to Windows such as the Windows Registry, roles, MSIs, and so on; the ones that won’t be available on Linux systems.
Working with Windows-specific resources
Most systems administrators, managing Windows means … read the rest
Chef is a very popular infrastructure automation framework. It is also getting popular in windows based environment. Installing Chef Client on Windows is sometime a challenge for developer. In order to install the Chef client on Windows, there are three basic options to be performed, as follows:
- Use the knife-windows plugin to bootstrap the host as described previously.
- Download and
Chef and Microsoft Windows are getting very popular. As chef practitioner, you must learn how chef works on Microsoft Windows. As you know that the client-side components of Chef are written in Ruby. Ruby is a cross-platform by nature, thus support for Windows is as straightforward as support for Linux and UNIX-like systems. It has been around for quite some … read the rest
This deep dive article on “Hadoop 3.0 Erasure coding explained” will highlight how the erasure coding will help reducing 50% of storage overhead cost. The storage component (HDFS) of Hadoop 3.0 by default replicates each block 3 times (and could be higher based on configuration). Replication facilitates a simple and robust form of redundancy to protect against failure … read the rest
This blog, Apache Hadoop 3.0 Installation, will assist you install and verify your pseudo-distributed, single-node & distributed instance in UNIX box (RHLE or Ubuntu). Hadoop 3.0 needs java 1.8 and higher, so this article assumes that you already aware of Hadoop 3.0 features and enhancement and minimum jdk requirement for newer version of Hadoop. Distributed & cluster Hadoop … read the rest