matschaffer

require 'rubygems'
require 'chef/encrypted_data_bag_item'

secret = Chef::EncryptedDataBagItem.load_secret('data_bag_key')
data = {"id" => "mysql", "root" => "some secret password"}
encrypted_data = Chef::EncryptedDataBagItem.encrypt_data_bag_item(data, secret)

FileUtils.mkpath('data_bags/passwords')
File.open('data_bags/passwords/mysql.json', 'w') do |f|
  f.print encrypted_data.to_json

marktheunissen

This playbook has been removed as it is now very outdated.

mrflip

== Overview of Datasets ==

The examples in this book use the "Chimpmark" datasets: a set of freely-redistributable datasets, converted to simple standard formats, with traceable provenance and documented schema. They are the same datasets as used in the upcoming Chimpmark Challenge big-data benchmark. The datasets are:

• Wikipedia English-language Article Corpus (wikipedia_corpus; 38 GB, 619 million records, 4 billion tokens): the full text of every English-language wikipedia article, in

• Wikipedia Pagelink Graph (wikipedia_pagelinks; ) --

• Wikipedia Pageview Stats (wikipedia_pageviews; 2.3 TB, about 250 billion records (FIXME: verify num records)) -- hour-by-hour pageview

johnrees

check process redis
  start program = "/usr/bin/redis-server /etc/redis/redis.conf"
  stop program = "/usr/bin/redis-cli -p 6379 shutdown"
  with pidfile /var/run/redis.pid

quickredfox

{
"1": {
"labels": {
"de": "Factual Orte",
"es": "Lugares Factual",
"en": "Factual Places",
"fr": "Endroits de Factual",
"it": "Luoghi Factual",
"jp": "Factual 場所",
"kr": "Factual 장소",

wycats

JSON API

There are two JSON API styles:

• The ID Style
• The URL Style

The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.

The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.

garethrees

- name: Group by Distribution
  hosts: all
  tasks:
    - group_by: key=${ansible_distribution}

- name: Set Time Zone
  hosts: Ubuntu
  gather_facts: False
  tasks:
    - name: Set timezone variables

silviud

# file for pressed
# password is empty 

percona-server-server-5.6       percona-server-server/root_password       password
percona-server-server-5.6       percona-server-server/root_password_again       password


# playbook

---

rothgar

# Idempotent way to build a /etc/hosts file with Ansible using your Ansible hosts inventory for a source.
# Will include all hosts the playbook is run on.
# Inspired from http://xmeblog.blogspot.com/2013/06/ansible-dynamicaly-update-etchosts.html

- name: "Build hosts file"
  lineinfile: dest=/etc/hosts regexp='.*{{ item }}$' line="{{ hostvars[item].ansible_default_ipv4.address }} {{item}}" state=present
  when: hostvars[item].ansible_default_ipv4.address is defined
  with_items: groups['all']

sjl

" run command
" no stdin
" output displayed in "Press enter to continue" style
" current buffer untouched
:!uptime

" run command
" pipe range of text to command on stdin
" output replaces the range in the current buffer
:RANGE!grep foo