Downloaded 49 times
![Stack State JSON
Each event gets JSON / attributes that define the
current stack state:
node[:opsworks]
node[:opsworks][:layers]
node[:opsworks][:instance]
node[:opsworks][:stack]](https://image.slidesharecdn.com/awsopsworksunderthehoodjoweiss-140417190618-phpapp01/75/ChefConf-2014-AWS-OpsWorks-Under-The-Hood-28-2048.jpg)
![Search
appserver = search(:node, "role:php-app").first
Chef::Log.info(”Private IP: #{appserver[:private_ip]}")
Exposes: hostname/fqdn, IP/DNS, private IP/DNS,
instance type, AMI ID, AZ, …](https://image.slidesharecdn.com/awsopsworksunderthehoodjoweiss-140417190618-phpapp01/75/ChefConf-2014-AWS-OpsWorks-Under-The-Hood-31-2048.jpg)
![{
"opsworks": {
"data_bags": {
"myapp": {
"mysql": {
"username": "default-user",
"password": "default-pass"
}
}
}
}
}
mything = data_bag_item("myapp", "mysql")
Chef::Log.info("username: #{mything['username']}")
Recipe
Custom
JSON](https://image.slidesharecdn.com/awsopsworksunderthehoodjoweiss-140417190618-phpapp01/75/ChefConf-2014-AWS-OpsWorks-Under-The-Hood-34-2048.jpg)
![Store Secrets on Amazon S3
Access from instance via IAM instance profiles
bucket = node['acme']['bucket']
key = node['acme']['key']
s3 = AWS::S3.new
obj = s3.buckets[bucket].objects[key]
obj.read](https://image.slidesharecdn.com/awsopsworksunderthehoodjoweiss-140417190618-phpapp01/75/ChefConf-2014-AWS-OpsWorks-Under-The-Hood-36-2048.jpg)
Uploaded byJonathan Weiss
ChefConf 2014 - AWS OpsWorks Under The Hood
This document summarizes AWS OpsWorks, an integrated application management service that uses Chef to automate configuration management and deployment. It discusses OpsWorks architecture, how it integrates with Chef, and key differences from a traditional Chef server setup. Key events like setup, configure, deploy and shutdown trigger Chef runs with stack state JSON. Layers map to roles to define common behaviors and settings for groups of instances.
More Related Content
Similar to ChefConf 2014 - AWS OpsWorks Under The Hood
ChefConf 2014 - AWS OpsWorks Under The Hood
- 1. © 2014 Amazon.com,Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. AWS OpsWorks Under the Hood Jonathan Weiss @jweiss Amazon Web Services
- 2. “Integrated application management serviceon EC2 – powered by Chef”
- 3. Chef Setup Chef Client/Zero & OpsWorksBackend Chef Client & Chef Server
- 4. OpsWorks Architecture OpsWorks Backend OpsWorks Agent EC2, EBS,EIP, VPC, ELB, … Auto-Scaling, Auto-Healing,… On-instance execution via Chef client/zero Command JSON Command Log+Status
- 5. Chef Setup inOpsWorks • Supported Chef versions: 0.9, 11.4 or 11.10 • Built-in convenience cookbooks / bring your own • Chef run is triggered by life cycle event firing • Event comes with stack state JSON
- 6.
- 7.
- 8. Layers Group of instanceswith common behavior & settings – Recipes / run_list – Settings / attributes – Similar to Chef role
- 9. Built-in Layers Open Sourceat http://github.com/aws/opsworks-cookbooks Rails MySQL PHP HAProxy Node.js Memcached Java Ganglia
- 10. Custom Layers Define yourown layers and their run_list – Erlang app server – Cassandra DB cluster – C daemon – Custom PHP install – …
- 11.
- 12.
- 13.
- 14.
- 15. Events Events are triggeredwhen your stack changes: • Give you fine-grained control • Faster to execute • Context: run_list per event per layer (aka role)
- 16. Life Cycle Events 1 6 setupconfigure deploy undeploy shutdown
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. Setup Event • Sentwhen instance boots • Includes deploy event • Use for initial installation of software & services
- 23. Setup Event –Recipe Execution Order AWS OpsWorks setup recipes Your setup recipes AWS OpsWorks deploy recipes Your deploy recipes
- 24. Configure Event • Sentto all instances when any instance enters or leaves online state • Use for making sure the configuration is up-to-date
- 25. Deploy Event • Sentyou deploy via UI/API also part of each setup • Use for custom deployment
- 26. Undeploy Event • Sentvia UI/API when apps are deleted • Use to remove apps from running instances
- 27. Shutdown Event • Sentwhen an instance is shut down • ~45s to execute • Use for clean shutdown
- 28. Stack State JSON Eachevent gets JSON / attributes that define the current stack state: node[:opsworks] node[:opsworks][:layers] node[:opsworks][:instance] node[:opsworks][:stack]
- 29.
- 30. Search Stack state JSONavailable through search search(:node, “name:web1”) search(:node, “name:web*”) Attributes generated on nodes are not available
- 31. Search appserver = search(:node,"role:php-app").first Chef::Log.info(”Private IP: #{appserver[:private_ip]}") Exposes: hostname/fqdn, IP/DNS, private IP/DNS, instance type, AMI ID, AZ, …
- 32. Roles OpsWorks layers mappedas roles search(:node, “role:rails-app”) search(:node, “role:custom-foo”) Complete role functionality depends on supporting a “full” chef repo
- 33. Data Bags Define incustom JSON { "opsworks": { "data_bags": { "bag_name1": { "item_name1: { "key1" : “value1”, "key2" : “value2”, ... } }, "bag_name2": { "item_name1": { "key1" : “value1”, "key2" : “value2”, ... } }, ... } } }
- 34. { "opsworks": { "data_bags": { "myapp":{ "mysql": { "username": "default-user", "password": "default-pass" } } } } } mything = data_bag_item("myapp", "mysql") Chef::Log.info("username: #{mything['username']}") Recipe Custom JSON
- 35. Encrypted Data Bags Notsupported – Alternative handling: • Upload encrypted JSON to S3 • Have instances access via IAM roles in a recipe
- 36. Store Secrets onAmazon S3 Access from instance via IAM instance profiles bucket = node['acme']['bucket'] key = node['acme']['key'] s3 = AWS::S3.new obj = s3.buckets[bucket].objects[key] obj.read
- 37. Berkshelf Integration Enable Berkshelfin stack settings Supports any version, ships pre-compiled for some
- 38.
- 39. Berksfile cookbook 'apt' cookbook 'bluepill','>= 2.3.1' cookbook 'ark', git: 'git://github.com/opscode-cookbooks/ark.git' cookbook 'build-essential', '>= 1.4.2', git: 'git://github.com/opscode-cookbooks/build-essential.git', tag: 'v1.4.2'
- 40. Environments • OpsWorks onlysupports the implicit _default env • We are looking into adding proper env support
- 41.
- 42. Main Differences ToChef Server • One run vs. discrete events • Push vs. pull • Discovery: search & AWS OpsWorks attribute tree • Encrypted data bags • Environments & roles
- 43. AWS OpsWorks • Lifecycle framework • Highly customizable – in the end everything is a Chef run • Expect us to integrate more over time
- 44. More information aboutAWS OpsWorks • Follow us on twitter @AWSOpsWorks • Find us on YouTube • Docs: http://aws.amazon.com/documentation/opsworks • Blog: http://blogs.aws.amazon.com/application-management
- 45.