"AWS OpsWorks helps you deploy and operate applications of all shapes and sizes. With AWS OpsWorks, you can model your application stack with layers that define the building blocks of your application: load balancers, application servers, databases, etc. But did you know that you can also extend AWS OpsWorks layers or build your own custom layers? Whether you need to perform a specific task or install a new software package, AWS OpsWorks gives you the tools to install and configure your instances consistently and help them evolve in an automated and predictable fashion. In this session, we dive into the development process including how to use attributes, recipes, and lifecycle events; show how to develop your environment locally; and provide troubleshooting steps that reduce your development time."

1. November 12, 2014 | Las Vegas, NV
Thomas Lobinger and Jonathan Weiss, Amazon Web Services

5. OpsWorksBackend
OpsWorksAgent
Amazon EC2, Amazon EBS, EIP,
Amazon VPC, Elastic Load Balancing…. Auto-Scaling, Auto-Healing….
On-instance execution viaChef client/zero
Command
JSON
CommandLog+Status

6. Chef Client
&
Chef Server

15. AWS OpsWorks recipes
Yourcustomrecipes

18. search(:node, “name:web1”)
search(:node, “name:web*”)

19. appserver = search(:node, "role:php-app").first
Chef::Log.info(”Private IP: #{appserver[:private_ip]}")

20. appserver = search(:node, "role:php-app").first
Chef::Log.info(”Private IP: #{appserver[:private_ip]}")

21. {
"opsworks": {
"data_bags": {
"bag_name1": {
"item_name1: {
"key1" : “value1”,
"key2" : “value2”,
...
}
},
"bag_name2": {
"item_name1": {
"key1" : “value1”,
"key2" : “value2”,
...
}
},
...
}
}
}

22. {
"opsworks": {
"data_bags": {
"myapp": {
"mysql": {
"username": "default-user",
"password": "default-pass"
}
}
}
}
}
mything= data_bag_item("myapp", "mysql")
Chef::Log.info("username: #{mything['username']}")

24. user= ENV[“payment_provider_user“]
password= ENV[“payment_provider_password“]
PaymentGateway.new(user, password)

31. Change cookbook
Push change
Stop an instance
Update cookbooks
Start an instance
Trigger event or runlist
Check logs

33. list_commands
get_json
run_command
show_log

34. list
# list event history (up to 10 events)
# opsworks-agent-cli list
2014-11-06T10:26:58setup
2014-11-06T10:55:13configure2014-11-06T14:59:05execute_recipes
2014-11-07T18:25:53deploy
2014-11-07T18:34:11configure
2014-11-08T10:05:23configure
2014-11-08T14:43:43configure

35. get
# show JSON events (latest or by type/timestamp)
# opsworks-agent-cli get
{
"ssh_users": {
"2066": {
"name": "thomas",
"public_key": "ssh-rsa AAAAB3NzaC1...",
"sudoer": true
...

36. # list current agent folder and cookbooks
# ls/opt/aws/opsworks/current
cookbooks# OpsWorks cookbooks
berkshelf-cookbooks# CookbooksfromBerkshelf
site-cookbooks# Yourcookbooks
merged-cookbooks# Resultingcookbooksforrun
...

37. run
# run last setup event (changed cookbooks, same JSON)
# opsworks-agent-cli run setup
# or select specific date
# opsworks-agent-cli run 2014-11-08T14:43:43
[2014-11-12 13:06:41] INFO [opsworks-agent(17817)]:About to re-run 'setup' from 2014-11-08T14:43:43
Waiting for process 17817
...
Finished Chef run with exitcode 0

38. # change recipe
# cd /opt/aws/opsworks/current/site-cookbooks
# vim mycookbooks/recipes/default.rb
# confirm success
# opsworks-agent-cli run setup
# commit back to your git repo
# git commit -am “can develop on instance“
# git push

41. Destroy
Create
Converge
Setup
Verify
Destroy

42. .kitchen.yml
driver:
name: opsworks
stack_id: vvvvvvvv-wwww-xxxx-yyyy-zzzzzzzzzzzz
provisioner:
name: shell
busser:
ruby_bindir: /opt/aws/opsworks/local/bin

43. .kitchen.yml
platforms:
-name: Amazon Linux 2014.09
-name: Ubuntu 12.04 LTS
-name: Ubuntu 14.04 LTS
suites:
-name: default
run_list:
-recipe[demo::default]

44. # destroy, create, setup, converge, verify, destroy
kitchen test
kitchen verify [NAME|REGEXP|all]# run all 'tests'
kitchen verify ubuntu# only ubuntus
kitchen verify client# only client tests
kitchen verify -c NUMBER# concurrency
# Talk by Fletcher Nichol http://youtu.be/YzlCHAbJ7KM

45. ‣attributes
‣recipes
‣templates
▾test
‣integration
.kitchen.yml
metadata.rb

46. ‣attributes
‣recipes
‣templates
▾test
▾integration
‣default<--test suite name
.kitchen.yml
metadata.rb

47. ‣attributes
‣recipes
‣templates
▾test
▾integration
▾default<--test suite name
‣bats<--test framework
.kitchen.yml
metadata.rb

48. ‣attributes
‣recipes
‣templates
▾test
▾integration
▾default<--test suite name
▾bats<--test framework
htop_installed.bats<--the actual test
.kitchen.yml
metadata.rb

49. Test file htop_installed.bats
#!/usr/bin/env bats
@test "htop binary is found in PATH"{
run which htop
[ "$status"-eq 0 ]
}

53. 5
commit
StackonEC2

56. $./opsrun.rb92ca56ec-1672-4db0-8c6e-a8566e7db671 'echo $SHELL'
ruby: warning: RUBY_HEAP_MIN_SLOTS isobsolete. UseRUBY_GC_HEAP_INIT_SLOTS instead.
Abouttoruna scripton stack92ca56ec-1672-4db0-8c6e- a8566e7db671 on 2 online instances
...
...
jenkins2:
/bin/bash
php-app1:
/bin/bash
$

62. http://bit.ly/awsevals