fr34k8

Creating a useful cloud migration model

This is a transformation of Adrian Colyer's Checklist to turn it into a working model for a cloud transformation. The assumption is that the original checklist can suffice for any services that are deployed on the build pipeline, but the question to answer here is about how the environment is provisioned, deployed, monitored and governed in such a way as to fit the architecture implicit in the service checklist.

Configuration and Secret Management

Config is supplied via environment variables.
Anything that doesn't vary between deploys should not be externalised.
Deployment orchestrator should supply config as it deploys a service
Secrets should never be supplied as config
Desired deployment state should be declaratively described in code in a VCS.

Introduction

This document presents a simple way to manage your Docker resource by using Portainer as a gateway (HTTP queries against the Portainer API).

WARNING: This documentation is valid for Portainer >= 1.18.0.

NOTE: I'm using httpie to execute HTTP queries from the CLI.

Deploy a Portainer instance

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

Awesome Go

financial support to Awesome Go

A curated list of awesome Go frameworks, libraries and software. Inspired by awesome-python.

Contributing

Add the following chunk to your existing ISC dhcpd.conf file.

if exists user-class and ( option user-class = "iPXE" ) {
    filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
    filename "undionly.kpxe";
}

(or see https://gist.github.com/4008017 for a more elaborate setup

	#!/bin/bash
	#
	# Ansible role test shim.
	#
	# Usage: [OPTIONS] ./tests/test.sh
	# - distro: a supported Docker distro version (default = "centos7")
	# - playbook: a playbook in the tests directory (default = "test.yml")
	# - role_dir: the directory where the role exists (default = $PWD)
	# - cleanup: whether to remove the Docker container (default = true)
	# - container_id: the --name to set for the container (default = timestamp)

	#!/usr/bin/env bash

	set -u
	set -e
	set -o pipefail

	GCP_PROJECT="$(gcloud config list --format 'value(core.project)')"

	GCP_SERVICES=(
	"storage-api.googleapis.com"

	#!/usr/bin/env python
	#
	# usage:
	# conv2vmx-ovf.py some-vm.ovf
	#
	# ref: http://www.cnblogs.com/eshizhan/p/3332020.html
	#

	import sys
	fn = sys.argv[1]

	image: gitlab.dev.terastrm.net:4567/terastream/cisco-nso/ci-cisco-nso:4.2.3

	stages:
	- build
	- mr-robot

	variables:
	NCS_VERSION: "4.2.3"
	DOCKER_REGISTRY: "gitlab.dev.terastrm.net:4567/terastream/cisco-nso"
	TARGET_REGISTRY: "repo.dev.terastrm.net:5000/"

	# Initialize a gitlab-runner in a utility namespace dedicated to customer namespace
	# Designed to faciliate customer self-service to their namespace(s) via GitLab
	---
	apiVersion: batch/v1
	kind: Job
	metadata:
	name: deploy-gitlab-runner-<customer>-<namespace>
	spec:
	ttlSecondsAfterFinished: 100
	template: