sneal

#!/usr/bin/env bash

brew install openssl@1.1
mkdir -p /usr/local/opt/openssl/lib/
ln -s /usr/local/opt/openssl@1.1/lib/libcrypto.1.1.dylib /usr/local/opt/openssl/lib/
ln -s /usr/local/opt/openssl@1.1/lib/libssl.1.1.dylib /usr/local/opt/openssl/lib/
pushd /usr/local/opt/openssl/lib/
ln -s libssl.1.1.dylib libssl.dylib
ln -s libcrypto.1.1.dylib libcrypto.dylib
popd

h4xnoodle

On director
Task kick off to rotate some certs

nats, blobstore, system ones
shows 'updating instance' calls but it's not a deploy
maybe say 'configuring instance blah/xxx'

Applying instance configuration acb/123
-- Generating: exchange key pair, new certificates
-- Encrypting and sending certificates

geraldodev

type breakpoint = [ | `lg | `md | `sm | `xl | `xs ];

type breakpointsObj = {
  .
  "keys": array(string),
  "values": {
    .
    "lg": int,
    "md": int,
    "sm": int,

saleem-mirza

package main

import (
	"crypto/hmac"
	"crypto/sha256"
	"encoding/base64"
	"net/http"
	"time"
	"unicode/utf8"
	"strconv"

Amit-PivotalLabs

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.

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

friegger

Disks with OpenStack and BOSH

How Disks are Used

- separate devices  
  root disk        -> vda -> /  
  ephemeral disk   -> vdb -> /var/vcap/data  
  persistent disk  -> vdc -> /var/vcap/store  
- same device 

jmathai

Getting Elodie running on Synology DSM

• Install python
• Install pip
• Install virtualenv
• Install virtualenvwrapper
• Install git (server) through DSM Package Manager
• Install perl through DSM Package Manager
• Install exiftool through CPHub (https://www.cphub.net/?id=40&pid=609)
• Clone elodie from Github (https://github.com/jmathai/elodie)

g0t4

Instructions

• Save the docker-compose.yml and config.yml in the same directory on one of your volumes on the NAS.
• SSH in and use docker-compose up -d
• Test the mirror with curl --head http://NAS-IP:55000
• Start up docker daemons with the following option or put this in the daemon config file or copy into Docker for Mac/Windows settings. --registry-mirror=http://NAS-IP:55000
• Pull an image and then check that it is cached in your mirror with curl http://NAS-IP:55000/v2/_catalog
  • or check that a large image isn't slow after the first pull :)

Notes

DenisIzmaylov

Step By Step Guide to Configure a CoreOS Cluster From Scratch

This guide describes how to bootstrap new Production Core OS Cluster as High Availability Service in a 15 minutes with using etcd2, Fleet, Flannel, Confd, Nginx Balancer and Docker.

Content

• Introduction
  • Tools Used
• Basic Configuration

drnic

#!/usr/bin/ruby
require 'rubygems'
require 'json'
require 'pp'
# for the #sh helper
require "rake"
require "rake/file_utils"
include FileUtils

## PREREQ: Using CF cli tools, make sure you've logged in as a user (admin) who can see all orgs/spaces