Skip to content

Instantly share code, notes, and snippets.

View slyness's full-sized avatar
🏠
Working from home

Aaron Baer slyness

🏠
Working from home
14 followers · 13 following
View GitHub Profile
@slyness
slyness / gist:9075959
Created February 18, 2014 17:48
of the day
<% end %>
##################################################################################
# TODO: REMOVE DUPLICATION with MYHCGENIUS server declaration
# an nginx inlcude should work but I'm done wrestling with chef for the day
##################################################################################
@slyness
slyness / gist:9081870
Created February 18, 2014 22:34
a statement
I just reviewed the haw_security_group and it has some pretty big issues.
When I killed my test stack it removed SecurityGroup entries in the NatSG which affected all other stacks using the NATs.
Basically all our CIs began to fail because we deleted the port 22 rule so no github :(
I think the security group needs to be a a dynamic like I mentioned earlier.
What do you think?
@slyness
slyness / gist:9771150
Created March 25, 2014 20:57
================================================================================
Recipe Compile Error in /var/chef/cache/cookbooks/echelon/recipes/dashboard.rb
================================================================================
NoMethodError
-------------
undefined method `[]' for nil:NilClass
@slyness
slyness / upgrade.md
Created March 28, 2014 03:44 — forked from jeremiahsnapp/upgrade.md

All upgrades

All upgrades should be performed first with a copy of Production data, in an environment that is non-essential. This could be a Vagrant VM and is our typical test hardware for this purpose.

Backups are good to have for many reasons at all times. Especially during upgrades, tested backups become a critical part of our toolkit.

Upgrading from OPC1.2.x

Upgrading from OPC1.2x to EC11x REQUIRES that you first upgrade all systems in a cluster to OPC1.4.6.

@slyness
slyness / keybase.md
Created March 30, 2014 06:12

Keybase proof

I hereby claim:

  • I am slyness on github.
  • I am slyness (https://keybase.io/slyness) on keybase.
  • I have a public key whose fingerprint is A617 FBAA EDBE D8C4 F423 BE92 B199 84AA F16A FC4D

To claim this, I am signing this object:

@slyness
slyness / gist:11025374
Created April 18, 2014 04:53
Almost made it through the upgrade.
[private-chef-upgrade] - Running Command: rm -f /var/log/opscode/opscode-chef-mover/parsed_console.log with options {}
[private-chef-upgrade] - Running Command: private-chef-ctl restart opscode-chef-mover with options {}
ok: run: opscode-chef-mover: (pid 12145) 0s
[private-chef-upgrade] - Running Command: /opt/opscode/embedded/bin/escript /opt/opscode/embedded/service/opscode-chef-mover/scripts/migrate with options {}
Successfully Migrated:
SO MANY ORGANIZATION NAMES....
Failed to Migrate:
@slyness
slyness / gist:11025394
Created April 18, 2014 04:54
Successful Migration
Successfully Migrated: ninefold-chef-34-fd44, ninefold-chef-467-6f50, ninefold-chef-108-2930, ninefold-chef-132-c0e8, ninefold-chef-100-d80e, ninefold-chef-47-63e0, ninefold-chef-87-2308, ninefold-c
hef-3-17c2, ninefold-chef-27-06e7, ninefold-chef-487-9771, ninefold-chef-1-49d8, ninefold-chef-1-3b3e, ninefold-chef-482-b84e, ninefold-chef-44-8a93, ninefold-chef-103-9c44, ninefold-chef-8-4b3d, ninefold
-chef-107-bfaa, ninefold-chef-41-f09d, ninefold-chef-481-7ac5, ninefold-chef-35-7a45, ninefold-chef-121-dd5f, ninefold-chef-84-d96b, ninefold-chef-92-69ce, ninefold-chef-35-4957, ninefold-chef-15-a2e6, ni
nefold-chef-34-1f17, ninefold-chef-18-6a6d, ninefold-chef-86-41db, ninefold-chef-1-0cd9, ninefold-chef-89-25e5, ninefold-chef-497-3a1c, ninefold-chef-7-ccc4, shaunsnowflake, ninefold-chef-13-12b9, ninefol
d-chef-50-158c, ninefold-chef-32-efa2, ninefold-chef-7-b827, ninefold-chef-133-8d16, ninefold-chef-469-86e8, ninefold-chef-2-c130, ninefold-chef-1-afa0, ninefold-chef-113-9130, ninefold-chef-4-7301, ninef
old-c
@slyness
slyness / gist:11025410
Created April 18, 2014 04:55
Failed to migrate
Failed to Migrate: ninefold-chef-143-6291, ninefold-chef-31-a327, ninefold-chef-549-ee15, ninefold-chef-558-e254, ninefold-chef-103-983f, ninefold-chef-9-71d4, ninefold-chef-12-63ed, ninefold-chef-67-7ec0, ninefold-chef-23644-3666, ninefold-chef-5-b999, ninefold-chef-31-e317, ninefold-chef-14-24dd, ninefold-chef-23642-a1dc, ninefold-chef-94-31b9, ninefold-chef-8-1f10, ninefold-chef-814-d409, ninefold-chef-527-ea2c, ninefold-chef-3-e107, ninefold-chef-65-66ce, ninefold-chef-1-bb70, ninefold-chef-22-ee58, ninefold-chef-112-1fc7, ninefold-chef-3-5412, ninefold-chef-119-e055, ninefold-chef-567-ab30, ninefold-chef-19-6f74, ninefold-chef-53-03fc, ninefold-chef-47-decb, ninefold-chef-56-2fa5, ninefold-chef-26-2a70, ninefold-chef-137-7064, ninefold-chef-84-6075, ninefold-chef-547-a90c, ninefold-chef-39-a35c, ninefold-chef-96-7078, ninefold-chef-89-bb68, ninefold-chef-803-d6ec, ninefold-chef-99-5c8a, ninefold-chef-15-92ec, ninefold-chef-472-5c40, ninefold-chef-63-e13e, ninefold-chef-14-a522, ninefold-chef-41-f7a
@slyness
slyness / client.sh
Created April 18, 2014 23:09 — forked from nstielau/client.sh
echo '{
"handlers": ["debug"],
"name": "push_woot_test",
"output": "woot!",
"status": 0
}' | nc -w1 127.0.0.1 3030
@slyness
slyness / CONTRIBUTING.md
Last active August 29, 2015 14:00 — forked from dje/CONTRIBUTING.md
  1. Fork the repository using Github
  2. Checkout a named feature branch created from the develop branch
  3. Complete modifications or corrections, include tests to support your code
  4. Run the tests, ensuring they all pass
  5. Submit a Pull Request to the develop branch using Github