Larry Eichenbaum larryebaum-nz

## Chef Port Requirements
22 (SSH/SCP)
80 (HTTP)
81 (HTTP ALT)
443 (HTTPS)
5985 (WINRM)
5986 (WINRM)
3389 (RDP)
8080 (HTTP ALT)
8081 (HTTP ALT)

## Chef knife.rb example content
#WINDOWS Knife Example Content

current_dir = File.dirname(__FILE__)
log_level                :info
log_location             STDOUT
node_name                "chef_user_here"
client_key               "#{ENV['HOME']}/.chef/chef_client_here.pem"
validation_client_name   "organization_here-validator"
validation_key           "#{ENV['HOME']}/.chef/organization_here-validator.pem"
chef_server_url          "https://api.opscode.com/organizations/organization_here"

## chef_local_development_workflow.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                larryebaum-nz
                / chef_local_development_workflow.md
            
            
              Created
              November 30, 2016 22:19
                — forked from smford22/chef_local_development_workflow.md
            
              
                Chef Local Development Workflow - ChefDK, Vagrant, VirtualBox, Test Kitchen
              
          
    Chef Local Development Workflow with ChefDK, Vagrant, VirtualBox, and Test Kitchen

Overview

The following document is intended to be a quick guide to getting you setup for doing local development with Chef. This guide was created on my MacBook, but should work fine with Linux, and Windows workstations as well.
Quick review on fundamental tenets of Chef


Workstation - A workstation is a computer that is configured to run various Chef command-line tools that synchronize with a chef-repo, author cookbooks, interact with the Chef server, interact with nodes, or applications like Chef Delivery
Node - A node is any machine—physical, virtual, cloud, network device, etc.—that is under management by Chef.
Chef Server- The Chef server acts as a hub for configuration data. The Chef server stores cookbooks, the policies that are applied to nodes, and metadata that describes each registered


## AuditConfig.html
<!-- Sourced from http://htmlpreview.github.io/?https://github.com/jeremymv2/audit-docs/blob/master/grid.html-->

<html>
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
  <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
  <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
</head>

## README.md

      
              3 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                larryebaum-nz
                / README.md
            
            
              Last active
              September 26, 2017 20:55
                — forked from afiune/README.md
            
              
                Automate LDAP Bulking User Creation
              
          
    LDAP Bulking User Creation Process

This is temporal automation to create/update multiple LDAP users in Chef Automate. If a user appears in the input file and already exists as a user, the user roles will be updated as specified within the input file. If the user does not exist, it will be created with the specified roles.
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.


## gist:e02262ba850a724bd612f3406d94e88a
# on Supermarket server
sudo su -
echo "\nSelf-Signed Chef Server Cert (you should feel bad about this)\n=====================" >> /opt/supermarket/embedded/ssl/certs/cacert.pem
openssl s_client -showcerts -connect phl-du-cfbc1.devfwh.lan:443 </dev/null 2>/dev/null|openssl x509 -outform PEM >> /opt/supermarket/embedded/ssl/certs/cacert.pem

# on Chef Server
sudo su -
echo "\nSelf-Signed Supermarket Cert (you should feel bad about this)\n=====================" >> /opt/opscode/embedded/ssl/certs/cacert.pem
openssl s_client -showcerts -connect phl-du-cfsm1.devfwh.lan:443 </dev/null 2>/dev/null|openssl x509 -outform PEM >> /opt/opscode/embedded/ssl/certs/cacert.pem

## gist:6a674680665f22b3417c3e30028520fa
chef-run chef@node1 file '/etc/motd'
content='Welcome to Chef’ --password Cod3Can!
chef-run chef@node1 motd.rb --password Cod3Can!
chef-run winrm://Administrator@winnode1
file_experiment.rb --password Cod3Can!
chef generate cookbook -P setup
chef generate template motd
kitchen converge
kitchen verify
kitchen destroy

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                larryebaum-nz
                / keybase.md
            
            
              Created
              October 29, 2019 17:58
            
          
    Keybase proof

I hereby claim:

I am larryebaum on github.
I am larryebaum (https://keybase.io/larryebaum) on keybase.
I have a public key ASDKS1XowbLAWmlCQpItjOBvy5C4ZtiEBzhKCsWRqay83go

To claim this, I am signing this object:

  
## upload-key-aws-regions
#!/bin/bash

## Specify as the 1st parameter the keyname to display in AWS;
## use 1st param or current user
aws_keypair_name="${1:-$USER}"
## Specify as the 2nd parameter the full path to ssh public key file name to upload to AWS;
## use 2nd param or default id_rsa.pub will be used.
publickeyfile="${2:-$HOME/.ssh/id_rsa.pub}"
keydata=$(cat $publickeyfile | base64)
regions=$(aws ec2 describe-regions \

## .gitignore_global

## MacOS Stuff
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db
	22 (SSH/SCP)
	80 (HTTP)
	81 (HTTP ALT)
	443 (HTTPS)
	5985 (WINRM)
	5986 (WINRM)
	3389 (RDP)
	8080 (HTTP ALT)
	8081 (HTTP ALT)
	#WINDOWS Knife Example Content

	current_dir = File.dirname(__FILE__)
	log_level :info
	log_location STDOUT
	node_name "chef_user_here"
	client_key "#{ENV['HOME']}/.chef/chef_client_here.pem"
	validation_client_name "organization_here-validator"
	validation_key "#{ENV['HOME']}/.chef/organization_here-validator.pem"
	chef_server_url "https://api.opscode.com/organizations/organization_here"
	<!-- Sourced from http://htmlpreview.github.io/?https://github.com/jeremymv2/audit-docs/blob/master/grid.html-->

	<html>
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
	<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
	<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
	</head>
	# on Supermarket server
	sudo su -
	echo "\nSelf-Signed Chef Server Cert (you should feel bad about this)\n=====================" >> /opt/supermarket/embedded/ssl/certs/cacert.pem
	openssl s_client -showcerts -connect phl-du-cfbc1.devfwh.lan:443 </dev/null 2>/dev/null\|openssl x509 -outform PEM >> /opt/supermarket/embedded/ssl/certs/cacert.pem

	# on Chef Server
	sudo su -
	echo "\nSelf-Signed Supermarket Cert (you should feel bad about this)\n=====================" >> /opt/opscode/embedded/ssl/certs/cacert.pem
	openssl s_client -showcerts -connect phl-du-cfsm1.devfwh.lan:443 </dev/null 2>/dev/null\|openssl x509 -outform PEM >> /opt/opscode/embedded/ssl/certs/cacert.pem
	chef-run chef@node1 file '/etc/motd'
	content='Welcome to Chef’ --password Cod3Can!
	chef-run chef@node1 motd.rb --password Cod3Can!
	chef-run winrm://Administrator@winnode1
	file_experiment.rb --password Cod3Can!
	chef generate cookbook -P setup
	chef generate template motd
	kitchen converge
	kitchen verify
	kitchen destroy
	#!/bin/bash

	## Specify as the 1st parameter the keyname to display in AWS;
	## use 1st param or current user
	aws_keypair_name="${1:-$USER}"
	## Specify as the 2nd parameter the full path to ssh public key file name to upload to AWS;
	## use 2nd param or default id_rsa.pub will be used.
	publickeyfile="${2:-$HOME/.ssh/id_rsa.pub}"
	keydata=$(cat $publickeyfile \| base64)
	regions=$(aws ec2 describe-regions \

	## MacOS Stuff
	.DS_Store
	.DS_Store?
	._*
	.Spotlight-V100
	.Trashes
	ehthumbs.db
	Thumbs.db