Timani Tunduwani timani

BOSH command line interface cheatsheet

Introduction

BOSH is a powerful tool to install and manage your deployments. You can find docs on https://bosh.io/docs. Consider using bosh-init tool to install to a cloud of your choice MicroBOSH instance (MicroBOSH is a single VM BOSH installation, it has everything that you need to deploy and manage).

Installing of BOSH CLI

BOSH command line interface is implemented as a ruby gem and can be run on every platform that supports ruby, you'll need to have ruby 2.1.x or higher to run it. To install it you can run gem install bosh_cli and gem update bosh_cli to update to a newer version.

Run Book / Operations Manual

Table of Contents
System Overview
- Service Overview
- Contributing Applications, Daemons, and Windows Services
- Hours of Operation
- Execution Design
- Infrastructure and Network Design
- Resilience, Fault Tolerance and High-Availability

Run Book / Operations Manual

Table of Contents
System Overview
- Service Overview
- Contributing Applications, Daemons, and Windows Services
- Hours of Operation
- Execution Design
- Infrastructure and Network Design
- Resilience, Fault Tolerance and High-Availability

BOSH Links: Why and How

Audience: anyone in the BOSH ecosystem, whether you work on something open-source or proprietary

"BOSH Links" is a feature which simplifies how data is shared between BOSH-deployed jobs that need to collaborate with one another (e.g. a web server and its backing database). Like many BOSH things, the whole "BOSH Links" thing can seem counter-intuitive at first, and it may not be clear why things are the way they are. This note hopes to show some of the powerful benefits of BOSH Links, and provide examples and explanations that make things more intuitive.

Why?
BASIC: A simple problem statement
BASIC: Putting the puzzle pieces together
ADVANCED: But what about...

Dockerized JMeter - A Distributed Load Testing Workflow

Supported Cloud Providers:

Amazon (https://aws.amazon.com/free/)
DigitalOcean (https://www.digitalocean.com/join/)

Images used:

JMeter Server (https://hub.docker.com/r/hhcordero/docker-jmeter-server) aka "Slave"
JMeter Client Non-gui (https://hub.docker.com/r/hhcordero/docker-jmeter-client) aka "Master"

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

	.ONESHELL:
	.PHONEY: help set-env init update plan plan-destroy show graph apply output taint

	help:
	@grep -E '^[a-zA-Z_-]+:.?## .$$' $(MAKEFILE_LIST) \| sort \| awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'

	set-env:
	@if [ -z $(ENVIRONMENT) ]; then\
	echo "ENVIRONMENT was not set"; exit 10;\
	fi

	import csv
	from github2.client import Github

	# api settings for github
	git_username = 'your_git_username'
	git_api_token = 'your_git_api_token'
	git_repo = 'username/repo_name'

	# import all issues as this story type
	pivotal_story_type = 'Bug'

	import json
	import requests

	# Authentication for user filing issue (must have read/write access to
	# repository to add issue to)
	USERNAME = 'CHANGEME'
	PASSWORD = 'CHANGEME'

	# The repository to add this issue to
	REPO_OWNER = 'CHANGEME'

	#!/bin/bash

	# After a 1.7+ opsmanager restarts with a new ip address
	# ssh into the opsmanager as 'ubuntu' and
	# Run this file from the opsmanager as follows

	# sudo su -l postgres < thisfile.sh >

	# Get the current public ip or hostname from aws metadata
	HN=$(curl http://169.254.169.254/latest/meta-data/public-hostname)

Timani Tunduwani timani

BOSH command line interface cheatsheet

Introduction

Installing of BOSH CLI

Run Book / Operations Manual

Run Book / Operations Manual

BOSH Links: Why and How

Dockerized JMeter - A Distributed Load Testing Workflow

Supported Cloud Providers:

Images used:

Project Title

Getting Started

Prerequisities