Drew Glass - Hero Digital Push button deployments can automate AEM infrastructure to reduce costs and defects. Chef is a platform that enables this by transforming infrastructure into code using DevOps practices. AEM Author, Publish and Dispatcher instances can be fully configured and deployed as code with Chef. In this talk we will discuss how the open source AEM Chef Cookbook can be used to automate the deployment of AEM instances with Chef features like recipes, attributes, providers and resources. Out of the box, the AEM Chef Cookbook supports: - Unattended installation of AEM Author, Publish, and Dispatcher nodes. - Automatic search for and configuration of AEM cluster members using Chef searches. - Configuration for replication agents using the replicator provider. - Configurations for Dispatcher farms with the farm provider. - Deploying and removing AEM packages with the package provider. We will also discuss how AEM can be automated to supported different SSO and deployment scenarios like cold standby. Finally, we will cover how to extend the Cookbook to support your project specific needs.

1. CIRCUIT – An Adobe Developer Event
Presented by ICF Interactive
AEM DevOps –
AEM Infrastructure
Automation with Chef
Cookbooks
Drew Glass
Hero Digital
AEM Practice Lead

2. • Director, Engineering and AEM
Practice Lead at Hero Digital
http://herodigital.com/
• San Francisco AEM
Community Leader
http://www.meetup.com/Adobe-
Experience-Manager-Adobe-
Marketing-Cloud/
• MS in Computer Science from
University of Illinois Urbana-
Champaign
drew@herodigital.com
@drewglass
https://
www.linkedin.com/in/
drewglass1

3. Agenda
• What is DevOps
• DevOps with Chef
• AEM Cookbook
• Deployment Scenarios with Chef

4. What Is DevOps
• Use code and automation to increase
collaboration between development and
operations
• Consistent, testable, repeatable
infrastructure

5. The Value in DevOps
• Reduce cost and risk
• Increase throughput and delivery speed

6. DevOps with Chef
• Tool to automate infrastructure
provisioning through code
• Thin Domain Specific Language built on
top of Ruby
• Provides abstraction for infrastructure
• https://www.chef.io/chef/

7. Chef Basics
• Develop cookbooks on Chef workstation
using ChefDK
• Knife Cookbooks and Policies to Chef
Server
• Chef client provisions nodes using
cookbooks and policies and records that
information on Chef Server

8. Chef Basics Illustrated
Chef
Server
Nodes,
cookbooks,
policies
Worksta/on
ChefDK,
Knife,
cookbooks
Node
Chef-­‐client
Node
Chef-­‐client
Node
Chef-­‐client

9. Chef Workstation
Chef
Server
Nodes,
cookbooks,
policies
Worksta/on
ChefDK,
Knife,
cookbooks
Node
Chef-­‐client
Node
Chef-­‐client
Node
Chef-­‐client

10. Chef Workstation
• Develop cookbooks and policies
• Store cookbooks in chef-repo which is synced
with version control
• ChefDK - development kit which includes Kitchen,
ChefSpec, Berkshelf
https://downloads.chef.io/chef-dk/
• Knife – used to upload items such as cookbooks
to Chef server and interact with nodes
• Kitchen - test cookbooks across different
platforms
• ChefSpec - simulate convergence of resources on
a node
• Berkshelf - manage cookbook dependencies

11. Cookbooks
• Fundamental unit of configuration
• Contains attributes, recipes, templates,
files, providers, and resources
• Kinds of cookbooks: base and wrapper

12. AEM Community Base Cookbook
h6ps://github.com/tacitknowledge/aem-­‐cookbook

13. AEM Community Base Cookbook

14. AEM Wrapper Cookbook
• Depends on base cookbook
• Overrides base attributes and may include
new recipes, files, providers and templates
Example
metadata.rb

15. Attributes in a Cookbook
• Configuration data
• Defined in a cookbook and can override
attributes on a node
• When chef-client is run, attributes in
cookbook are compared against attributes
on node
• Attributes in default.rb are loaded first

16. Attributes in the AEM Cookbook
default[:aem][:version] = nil
default[:aem][:jvm_opts] = {}
default[:aem][:jar_opts] = []
default[:aem][:enable_webdav] = false
default[:aem][:jar_name] = nil
default[:aem][:use_yum] = false
default[:aem][:download_url] = nil
default[:aem][:license_url] = nil
default[:aem][:base_dir] = "/opt/aem"
default[:aem][:cluster_name] = nil
default[:aem][:author] = {
:default_context => "/opt/aem/
author",
:port => "4502",
:runnable_jar => "aem-author-
p4502.jar",
:base_dir => "/opt/aem/author/crx-
quickstart",
:jvm_opts => {},
:ldap => {
:enabled => false,
:options => {}
},
:validation_urls => [
"http://localhost:4502/libs/cq/
core/content/login.html",
"http://localhost:4502/
damadmin",
"http://localhost:4502/
miscadmin",
"http://localhost:4502/system/
console/bundles"
],
:deploy_pkgs => [],
#You changed these, right?
:admin_user => "admin",
:admin_password => "admin",
:new_admin_password => nil,
:replication_hosts => [],
:find_replication_hosts_dynamical
ly => false
}
default[:aem][:author][:startup]
[:max_attempts] = 20
default[:aem][:author][:startup]
[:wait_between_attempts] = 30

17. Attributes in the AEM Cookbook

18. Recipes in a Cookbook
• Fundamental configuration element
• Authored with Ruby and used to define
everything to configure part of system
• Executed in order specified in run list
• In AEM, we have recipes for author,
publish and dispatcher

19. Author Recipe in the AEM Cookbook

20. Author Recipe in an AEM Cookbook

21. Files and Templates in Cookbooks
• Templates - file written in markup
language to solve a more complex
configuration scenario
• Files - can be transferred from cookbooks
to nodes

22. Dispatcher Attributes

23. Dispatcher Template in the AEM Cookbook

24. Dispatcher Template in the AEM Cookbook

25. Resources and Providers
• Resources - package, service, etc. that
tells chef-client which provider to use
during a during a chef client run for
various tasks
• Provider - defines steps to bring part of
system into desired state

26. Author Recipe Calls Init Provider

27. Init Script Provider in the AEM Cookbook

28. Author Recipe Calls Replication Agent Provider

29. Replication Agent Provider in the AEM Cookbook

30. Chef Server
Chef
Server
Nodes,
cookbooks,
policies
Worksta/on
ChefDK,
Knife,
cookbooks
Node
Chef-­‐client
Node
Chef-­‐client
Node
Chef-­‐client

31. Chef Server
• Hub of configuration data
• Stores cookbooks, node information and
policies
• Chef-client running on nodes queries Chef
server for configuration information like
recipes
• Chef-client does the actual configuration
on the node
• Allows for distribution of work
• Also includes search

32. Chef-client
Chef
Server
Nodes,
cookbooks,
policies
Worksta/on
ChefDK,
Knife,
cookbooks
Node
Chef-­‐client
Node
Chef-­‐client
Node
Chef-­‐client

33. Chef-client
• Agent that runs on a node managed by Chef
• Chef-client is run to bring a node into a
desired state
• Typical chef-client run:
– register and authenticate node with Chef server
(RSA public key-pairs)
– builds the node object
– synchronizes cookbooks
– compiles resource collection by loading required
cookbooks (recipes, attributes, and all other
dependencies)
– provisions node

34. Chef-client Run for Author Node in Dev Environment

35. Node
• Physical, virtual or cloud machine that is
configured and maintained by chef-client
• Physical nodes are typically a server or
virtual machine that has to have a network
interface for chef-client to communicate
with Chef server
• Cloud node could be Amazon EC2,
Google Compute Engine, Backspace, etc.
• Chef-client can be used to deploy,
configure and maintain

36. Nodes in AEM
AEM
Author
AEM
Publish
Apache
with
Dispatcher

37. Node Objects
•
Attributes – configuration data for a node
– Describe the current state of a node
– Can be defined by: cookbooks, roles,
environments
• Run List - ordered list of roles and/or
recipes that defines all of the information
Chef needs to configure a node to a
certain state

38. Runlist in AEM

39. Policy
• Map business and operational
requirements to settings and objects on
Chef server
• Roles - define server types
– A role has zero or more attributes and a run
list
• Environments
– Define attributes for environments -
Integration, QA, Staging, Production

40. Roles in AEM

41. Environments in AEM

42. Deployment Scenarios
• AEM sandbox using Vagrant, Chef and
Berkshelf
• Local AEM development environment
using a AEM site wrapper cookbook
• AEM demo environment in the cloud using
Chef and Kitchen
• Continuous delivery pipeline with Chef and
Chef provisioning

43. Worksta/on
Local Dev VM or Cloud Instance
VM
or
Cloud
Instance
Vagrant
or
Kitchen
Cookbooks
and
Berkshelf
Chef-­‐solo
AEM
Author
AEM
Publish
Dispatcher

44. Vagrant and Chef Demo

45. AEM Environment with Chef
Chef
Server
with
Nodes,
Cookbooks,
and
Policies
Node
AEM
Author
Chef-­‐
client
Node
AEM
Publish
Chef-­‐
client
Node
Dispat-­‐
cher
Chef-­‐
client

46. Chef Provisioning
• Allows clusters to be managed with chef-
client and Chef server using recipes
• Collection of resources to enable creation
of machines using chef-client
• Bootstrap operations that are done
against an infrastructure like VirtualBox,
Amazon EC2, Docker, etc. using drivers
• Machines – Chef provisioning runs
multiple machine processes in-parallel in
most situations

47. Scaling with Chef Provisioning
Chef
Server
with
Nodes,
Cookbooks,
and
Policies
Node
AEM
Author
Chef-­‐
client
Dispatcher
Node
Publish
Node
Dispatcher
Node
Publish
Node

48. Scaling with Chef Provisioning
Chef
Server
with
Nodes,
Cookbooks,
and
Policies
Node
AEM
Author
Chef-­‐
client
Dispatcher
Node
Publish
Node
Dispatcher
Node
Publish
Node
Dispatcher
Node
Publish
Node
Dispatcher
Node
Publish
Node

49. Wrapping Up
• Infrastructure as code
• AEM DevOps with Chef
• Deploying AEM with Chef

50. Q & A
Send any questions to drew@herodigital.com