jeremiahsnapp

Sometimes a database object can get deleted but the Solr index entry will remain.

This can cause problems such as infinite Chef Search API request loops (for knife and I believe for Manage).

The following procedure identifies remaining index entries and provides a way to delete them.

# set the name of the organization you are interested in
export ORG_NAME=demo

afiune

LDAP Bulking User Creation Process

This is temporal automation to create multiple LDAP users in Chef Automate.

Prerequisites

The minimum prerequisites to be able to use this automation are:

• Use a Unix Workstation. (MAC, Linux, etc)
• Have ChefDK Installed. (https://downloads.chef.io/chef-dk/)
• Setup the CLI to point to your Automate Server. (https://asciinema.org/a/89658)
• Download the bulk-user-creation.rb script locally and give executable permissions to the file.

double-z

require 'pg'

add_command_under_category "cleanup-bifrost", "cleanup", "Cleanup orphaned bifrost objects.", 2 do
  erchef_db = setup_erchef_db
  bifrost_db = setup_bifrost_db

  puts "Populating hash of valid clients and users."
  clients_and_users = erchef_db.exec_params("SELECT authz_id FROM clients UNION select authz_id FROM users")
  real_actor_list = []
  clients_and_users.each do |real_actor|

alexpop

# encoding: utf-8
### Sample script to export Chef Server nodes and import them to Chef Compliance
### Change the 'api_url', 'api_user', 'api_pass' and 'api_org' variables below
### Change the nodes_array json suit your environment
### Go to your chef-repo and check Chef Server access first
# cd chef-repo; knife environment list
### Save this Ruby script as kitchen_sink.rb and run it like this:
# cat kitchen_sink.rb | knife exec
### Chef Compliance API docs: https://docs.chef.io/api_compliance.html

afiune

Publish Cookbook to Multiple Chef Servers in Delivery

Our delivery-sugar cookbook exposes some libraries and a LWRP that we can use to publish a cookbook (or multiple) to multiple Chef Servers or Organizations.

Prerequisites

The only prerequisite we have before start coding is the generation of the knife.rb and the client_key on the build-nodes that we will use in the build-cookbook. This can be done manually by loging in to the build-nodes and laying down the file, or in an

kmacgugan

--Questions for customer:
--- How many client nodes are you running?
--- Are they windows, linux or mixed?

-- Oldest data in activities
select min(recorded_at) from public.activities;

--how many rows over the past week per day
select count(*), date_part('day', recorded_at) from public.activities where recorded_at > now() - INTERVAL '7 days' group by 2;

jeremiahsnapp

Reference READMEs:

• dev-lxc

sean-horn

redbug Debugging on a live EC11 or Chef 12 Server

https://github.com/massemanet/eper/blob/master/doc/redbug.txt

Attach to the running erlang process on running EC11x or Chef 12 systems

/opt/opscode/embedded/bin/erl -name me@127.0.0.1 -remsh erchef@127.0.0.1 -setcookie erchef

Debug LDAP

irvingpop

#!/usr/bin/env ruby

LVM_LV = '/dev/opscode/drbd'
LVM_LV_MOUNT = '/var/opt/opscode/drbd/data'
LVM_SNAP_SIZE = '16G'
FILE_SIZE_MB = 1024
NUM_FILES = 15

def write_files(iterations)
  aggregate_speed = 0

mrflip

Next Steps

• Measure time spend on index, flush, refresh, merge, query, etc. (TD - done)
• Take hot threads snapshots under read+write, read-only, write-only (TD - done)
• Adjust refresh time to 10s (from 1s) and see how load changes (TD)
• Measure time of a rolling restart doing disable_flush and disable_recovery (TD)
• Specify routing on query -- make it choose same node for each shard each time (MD)
• GC new generation size (TD)
• Warmers

• measure before/after of client query time with and without warmers (MD)