Fleshing out more of the day

Author: Peter Burkholder

README.md

@@ -27,15 +27,56 @@ See SETUP.md for technical preparation
   - technical goals
 1. infrastructure.md
   - what is infrastructure?
+    - automobile analogy
   - why automate it?
--- NEXT --
+    - click-next dangers
+    - repeatablity, speed
+    - so let's get started, but first:
 1. workstation_setup.md
   - connect to AWS workstation
   - set up local connection and Atom remote_file
 1. chef_0.md
+  - setting: we have to release our (non-dynamic) home page
+    - we need to walk before we can run - so we'll start simple
   - how do config mgmt systems approach the problem?
+    - Infrastructure as Code
+      - Programmatically provision & configure components
+      - Treat like any codebase
+      - Reconstruct business from repository, data backup, and compute
+    - Policy-based management
+      - capture in code
+      - Chef ensures nodes and compute resources comply
   - resources
   - test & repair
+1. chef_1.md
+  - enough lab with package, file, service and template to get hello world!
+  - What's the DevOps story here?
+1. code_collaboration.md
+  - lab: bump versions and collaborate through GitHub PRs
+  - lab: test your cookbook
+  - lab: use Jenkins to ensure you're testing
+  - optional_lab: use Jenkins to release your infrastructure
+  - What's the DevOps story here?
+1. operationalize.md
+  - Why AWS
+    - Biggest player
+    - All other players borrow from them: Dig. Ocean, Google Cloud,
+    - One I'm most familiar with
+  - Why the cloud?
+    - OpEx vs. CapEx
+    - Elastic to demand
+    - Instant provisioning
+    - The Netflix story
+1. aws_0.md
+  - ec2
+    - ami
+    - instance size
+    - security groups
+      - the instances so far have been in the default security group, which only allows ingress from this set of IP addresses
+      - can't reach it with your phone
+      - the www machine needs to be world-accessible
+  - load-balancing
+
 
 
 ## Attributions

STUDENT_INFO.md

@@ -0,0 +1,26 @@
+## Questions
+
+Languages you've been coding with, and familiarity. No more than three.
+
+Git and Github familiarity
+
+What kind of laptop are you bringing?
+  Windows 7
+  Windows 8
+  Mac Mavericks or Yosemite (10.9 or 10.10)
+  Older Mac
+  Older Windows
+  Other
+
+## Prerequisites
+
+- Github account (free)
+- Laptop
+  - Atom installed
+  - Putty or other SSH
+
+## Info
+
+- Location
+- Lunch and breaks
+- RSVPs and cancellations

devops.md

@@ -0,0 +1,28 @@
+# DevOps
+
+2009:
+- Agile integration with Operations
+
+CAMS
+- Culture
+  - Trust and delegation
+  - Alignment of incentives
+  - Responsibility from desktop to produciton
+- Automation
+  - Infra automation
+- Metrics
+  - Testable
+- Sharing
+  - GitHub code review
+  -
+
+Agile overlap between Dev, QA, Operation
+
+StarOps
+
+- Short lead time
+- People over policy
+
+DevOps is NOT the tools
+- Amish is not the clothes
+- Japanese is not the wok

infrastructure.md

@@ -14,11 +14,16 @@ Basic infrastructure concepts
 - services:  httpd/databases
 - files & directory and users and tools
 - dev and test environments
+  - developer workstations
 - high availability and DR
-- developer workstations
+- data stores: databases, tweets,
+- applications:
+  - mongodb, Java, Drupal, Wordpress, mysql
 
 How much of this do you need to know?
 - It depends?
+- Since we're going to use AWS more later
+  - think about "how" much infrastructure you need.
 
 
 Analogize start-up infrastructure to automobile needs