stevengonsalvez

Model based on the chaos theory and lean .

• always resolve the most important issue first (biggest percentage of a combination of Urgent, big and Robust).
• If some activity could be bypassed or the result could be achieved without it, it is waste .
• Empowerment and accountability
• thinking big , act small , failing fast and learning rapidly
• Finally and most important a lot of common sense.

stevengonsalvez

This is a list of terms/jargons/vernacular

Purpose: cross-reference and synonomic , comprehensible understanding across people from different areas - defintely not intended to solve global warming.

Note: This is a temporary location and will be moved, and this is not alphabetical - So please do a ctrl +f

Rest API

Brief : REST APIs are excellent at handling requests in a generic way, establishing a set of rules that allow a large number of known and unknown developers to easily consume the services that the API offers.

stevengonsalvez

Installing ELK (CentOS)

This is a short step-by-step guide on installing ElasticSearch LogStash and Kibana Stack on a CentOS environment to gather and analyze logs.

I. Install JDK

rpm -ivh https://dl.dropboxusercontent.com/u/5756075/jdk-7u45-linux-x64.rpm

stevengonsalvez

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more

stevengonsalvez

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

stevengonsalvez

This is a copy/paste from an internal wiki on how we should use docker

This guide is to serve as an outline of internal best practices to using Docker. The idea is to give enough information to allow engineers to create containers for new stack components while minimizing the cleanup required to make them production ready.

Concepts

Before we get to the practices, it's important to understand WHY we are doing this. The key concepts we're concerned about with broad Docker usage are provenance, determinism, repeatability and auditability.

Provenance

Provenance refers to knowing WHERE something comes from. Generally with the end use of software, this is easy:

• Maven artifacts are pulled from central

stevengonsalvez

#!/usr/bin/env python

"""Implementation of RFC 4226: HMAC-Based One-Time Password Algorithm (HTOP),
and RFC 6238: Time-Based One-Time Password Algorithm (TOTP).
"""

__author__ = 'acoster'
__copyright__ = 'Copyright 2012, Alexandre Coster'

import hmac

stevengonsalvez

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrant on AWS Example
# Brian Cantoni

# This sample sets up 1 VM ('delta') with only Java installed.

# Adjustable settings
CFG_TZ = "US/Pacific"     # timezone, like US/Pacific, US/Eastern, UTC, Europe/Warsaw, etc.

stevengonsalvez

F0002 - 1000 messages average

JDK 1.7 with GC parameters

with GC set as CMS

Heap averaging to about 5.8 GB maximum
CPU - 100%
GC in CPU - around 10%

stevengonsalvez

# Get Root
sudo su
 
# Download NMON archive
cd /tmp
wget http://nmon.sourceforge.net/docs/MPG_nmon_for_Linux_14a_binaries.zip

# Install unzip if you don't have
yum install unzip