funkytaco

Building containers

• Fig - Fast, isolated development environments using Docker
• Packer - Tool for creating identical machine images
• decking - Create, manage and run clusters of Docker containers
• Ansible
  • docker module
  • docker_image module

Orchestration

• Kubernetes - Container Cluster Manager

funkytaco

#!/bin/bash


# Assumes a pre-built carina cluster, e.g.:
#
# carina create --wait shipyard \
#    && carina credentials shipyard \
#    && eval `carina env shipyard`
#  

funkytaco

#!/bin/bash

if [ "$1" != "" ] && [ "$1" = "-h" ]; then
    echo "Shipyard Deploy uses the following environment variables:"
    echo "  ACTION: this is the action to use (deploy, upgrade, remove)"
    echo "  IMAGE: this overrides the default Shipyard image"
    echo "  PREFIX: prefix for container names"
    echo "  SHIPYARD_ARGS: these are passed to the Shipyard controller container as controller args"
    echo "  TLS_CERT_PATH: path to certs to enable TLS for Shipyard"
    exit 1

funkytaco

Unionize: network superpowers for your docker containers

Unionize lets you connect together docker containers in arbitrarily complex scenarios.

Note: I recommend to use https://github.com/jpetazzo/pipework instead.

• pipework is a better name than unionize
• it's hosted on a "real" github repo instead of a small gist :-)

Now if you want Unionize, it's still here. Just check those examples.

funkytaco

This gist is an implementation of http://sirile.github.io/2015/05/18/using-haproxy-and-consul-for-dynamic-service-discovery-on-docker.html on top of Docker Machine and Docker Swarm.

funkytaco

registry:
  restart: always
  image: registry:2
  ports:
    - 5000:5000
  environment:
    REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: /var/lib/registry
  volumes:
    - ./data:/var/lib/registry

funkytaco

#
# build
#
# # docker build -t consul:latest .
#
# bootstrap server
#
# # docker run -d consul -server -bootstrap
# # docker inspect (container_id)
#

funkytaco

        <enricher doc:name="Message Enricher" source="#[payload]" target="#[flowVars['itsm-event-data']]">
            <remedy:get-single username="${remedy.read.username}" password="${remedy.read.password}" config-ref="RemedyConnection" id="#[message.outboundProperties['remedy_event_id']]" type="${remedy.outbound.table}" idBased="#[true]" doc:name="get-event-details"/>
        </enricher>
        <set-payload value="#[message.outboundProperties['remedy_form_id']]" doc:name="Set Payload"/>
        <choice doc:name="Choice">
            <when expression="#[message.outboundProperties['remedy_form'] == '${helpdesk.form}']">
                <remedy:query username="${remedy.read.username}" password="${remedy.read.password}" config-ref="RemedyConnection" query="('Incident Number' = &quot;#[payload]&quot;)" type="${helpdesk.form}" idBased="#[true]" doc:name="query-helpdesk-form"/>
                <set-payload value="#[payload.get(0)]" doc:name="Get first entry"/>
            </when>
            <otherwise>

funkytaco

Sub SendRemedyIncidentEmail()
   
    Const adUseClient = 3
    Const adOpenStatic = 3
    Const adLockPessimistic = 2
    ' Remedy User Name
    Const AR_SYSTEM_ODBC_DRIVER_UID = ""
    ' Password for Remedy User Name (AR_SYSTEM_ODBC_DRIVER_UID)
    Const AR_SYSTEM_ODBC_DRIVER_PWD = ""
    ' Port used by the Remedy server

funkytaco

case status
	when 0 then 'New'
	when 1 then 'Assigned'
	when 2 then 'In Progress'
	when 3 then 'Pending'
	when 4 then 'Resolved'
	when 5 then 'Closed'
	when 6 then 'Cancelled'
	else to_char(status)
end status