calebamiles

{
    "Changes": [
        {
            "Action": "DELETE", 
            "ResourceRecordSet": {
                "Name": "jb-zX.<domain>.", 
                "ResourceRecords": [
                    {
                        "Value": "<old-elastic-ip>"
                    }

calebamiles

# Ensure that the bosh-worker-locks repository has the proper number of slots desired
resources:
- name: worker-slots
  type: pool
  source:
    uri: git@github.com:cloudfoundry/bosh-worker-locks.git
    branch: master
    pool: integration

- name: integration-1.9-mysql

calebamiles

rake aborted!
bosh_cli_plugin_aws failed to build unit tests: Using ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-darwin14.0]
Run options:
  include {:focus=>true}
  exclude {:s3_credentials=>true}

All examples were filtered out; ignoring {:focus=>true}
................................................................*.........................................../Users/pivotal/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/option_grammar.rb:563: [BUG] Segmentation fault at 0x00000000910000
ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-darwin14.0]

calebamiles

  6) Bosh::OpenStackCloud::Cloud when using config drive as cdrom exercises the vm lifecycle
     Failure/Error: expect {
       expected no Exception, got #<Bosh::Clouds::CloudError: OpenStack API Request Entity Too Large error. Check task debug log for details.> with backtrace:
         # ./lib/cloud/openstack/helpers.rb:20:in `cloud_error'
         # ./lib/cloud/openstack/helpers.rb:40:in `rescue in with_openstack'
         # ./lib/cloud/openstack/helpers.rb:25:in `with_openstack'
         # ./lib/cloud/openstack/cloud.rb:455:in `block in create_disk'
         # /tmp/build/7a2e9560-be57-4e4b-6b51-8c0cbb6199ee/bosh-src/bosh_common/lib/common/thread_formatter.rb:49:in `with_thread_name'
         # ./lib/cloud/openstack/cloud.rb:433:in `create_disk'
         # ./spec/integration/lifecycle_spec.rb:315:in `create_disk'

calebamiles

type selectionFunc func(config.CPI) (string, error)
type reservationFunc func(config.CPI, string) (string, error)

func tryReservation(c config.CPI, choose selectionFunc, reserve reservationFunc) (string, error) {
	var cid string

Loop:
	for i := 0; i < maxRetries; i++ {
		nodeID, loopErr := choose(c)
		if loopErr != nil {

calebamiles

• Machine properties
  • What predefined types are supported
  • Are custom machine types supported
  • Can arbitrary machine settings be provided at creation time
    • Are they available within the machine
    • Can they be updated after the machine has started
  • How many machines can be created by default
    • How can this limit be raised
• Is it possible to upload custom machine images
• What image formats are supported (qcow2,raw,vmdk)

calebamiles

// somewhere earlier we define 
// var numberPodsEvicted *uint32


for i := 0; i < numOfEvictions; i++ {
	wg.Add(1)
	go func(id int, errCh chan error) {
		defer wg.Done()
		podName := fmt.Sprintf(podNameFormat, id)
		eviction := newEviction(ns.Name, podName, deleteOption)

calebamiles

Node.js Foundation

• Healthy Open Source
  • explicit goal to be a lightweight process
  • concrete ability to scale to hundreds of contributors
  • good fundamental goals
    • transparency
    • participation
    • efficacy
  • ecosystem projects encouraged but not required to adopt foundation governance templates
• creation of projects under TSC explicity delegates authority from TSC to project TC

calebamiles

PROBLEM: The structure of the project is opaque to newcomers

• project structure added to governance repository under Kubernetes GitHub organization
• create "Front Desk" inspired by Debian Project to welcome new contributors
• create mentorship requirement in contributor ladder

PROBLEM: There is no clear technical escalation path / procedure

• adopt RFC process inspired by Rust langage governance
• create technical steering committee bootstrapped from "top level OWNERS" as penultimate arbiters with power vested in Kubernetes community to make all final decisions
• affirm decision by technical steering committee in case inability of community to make decision
• devolve primary decision making and consensus building authority to SIGs

calebamiles

SIG Release

Purpose

• Production of high quality Kubernetes releases on a reliable schedule
• Ensure there is a consistent group of community members in place to support the release process [1]
• Driving project wide changes necessary to both release bits continuously

Broad responsibilities

• Ensuring high quality Kubernetes releases by:
• defining and staffing release roles to manage resolving and communicating the status of release blocking criteria