zankich

bosh -d cf-mysql start mysql/2
Using environment 'https://104.199.112.1' as client 'admin'

Using deployment 'cf-mysql'

Continue? [yN]: y

Task 77

Task 77 | 19:49:03 | Preparing deployment: Preparing deployment (00:00:02)

zankich

bosh -d cf-mysql instances --details
Using environment 'https://104.199.112.1' as client 'admin'

Task 78. Done

Deployment 'cf-mysql'

Instance                                                                Process State  AZ  IPs           State    VM CID                                VM Type  Disk CIDs                             Agent ID                              Index  Resurrection  Bootstrap  Ignore
                                                                                                                                                                                                                                                    Paused
backup-prepare/d011e3cc-7862-4e43-b900-0db88200f332                     running        z1  10.244.0.150  started  d4298212-8046-425f-61c6-0b0bf6fddbd8  default  436f94bc-201e-4dae-7427-ee8462afef64  3fba3b27-7d51-4791-818f-65b48308b3a3  0      false         true       false

zankich

$ cd cf-mysql-release
$ gem install bosh-template
$ bosh-template jobs/mysql/templates/my.cnf.erb --context "$(cat template-context.json)"

zankich

Problems and Questions:

1. Cross-pollution of duties between objects (calculating old vs new state, building changeset, applying changes)
2. Cost of refactoring current abstractions vs overhauling deploy/CCK to wholly use new system a. Some code in current flow (e.g. NetworkPlanner, which is primarily concerned with handling static and VIP networking) is not going to be used when hot-swap is turned on. b. We could refactor only hot-swap relevant portions to use patent strategy, but we then will have to support two different systems, which will likely need to interact cleanly; we would need to have a method of converting information between the two systems. c. Edge cases may arise while writing the new patent strategy which break the paradigm. The architecture will need to be vetted more thoroughly, to ensure that we aren't forced to rewrite the new code or sacrifice the abstraction.
3. Related to #1, the changeset is constructed throughout the flow rather than being finalized before being passed to the

zankich

Compilation

Claims

package claim - A package claim will contain the current package version and the stemcell

Patent Counsel

The patent counsel will create package claims for the new version number and/or stemcell version

Inspector

Will generate embodiment package claims based on the stemcell and version number of used package in instance groups

zankich

azs:
- name: z1
  cloud_properties: {zone: us-west1-a}

vm_types:
- name: common
  cloud_properties:
    machine_type: n1-standard-4
    root_disk_size_gb: 20
    root_disk_type: pd-ssd

zankich

package main

import (
	"encoding/json"
	"fmt"
	"net/http"
	"time"

	"github.com/goiot/devices/piglow"
	"golang.org/x/exp/io/i2c"

zankich

# bosh export release bosh/256.2 ubuntu-trusty/3232.4
---
director_uuid: REPLACE_ME

name: compilation

releases:
- name: bosh
  version: latest

zankich

#!/bin/bash -xu

export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export AWS_REGION=us-east-1

function main() {
  local times
  times=0

zankich

#!/bin/bash -exu

##
## This script generates consul and consul-template binaries.
## You may run this from inside a docker container with:
##
## docker pull golang:1.6.1
## docker run -v $PWD:/opt/build -t golang:1.6.1 /opt/build/build.sh
##