1. ATLASSIAN SUMMIT 2013

2. Automated Configuration and Deployment
of Atlassian Applications at Pandora
October 3, 2013
Raju Kadam & Myra Chachkin
Technical Operations
Pandora Media

3. personalized radio

4. Raju Kadam
Myra Chachkin
your humble presenters

5. deployment & configuration - then and now

6. BEGINNINGS

7. the olden days

8. no safety net

9. no rollback

10. labor-intensive configuration

11. GROWTH

12. expansion and integration

13. more apps and links

14. sandboxes

15. more testers, more features to test
• new projects, workflows, etc.
• new plugins
• new products & product versions

16. dev, stage, and prod

17. more instances and requirements
• dev: for experimenting
• stage: for proofing
• prod: for real

18. WHAT WE NEED

19. repeatability for speed & accuracy

20. parallel deploy for reduced risk

21. distinct environments for distinct uses

22. DEV
ATLASSIAN
APPLICATION
RELEASE CYCLE
STAGE
PROD
complexity

23. OUR SOLUTION

24. debian packaging

25. our in-house packaging
• binary file archives
• standard & custom packages
• standard & custom tools

27. SYSDB

28. DEPLOYMENT

29. build the jira package
• get the tarfile
• customize
• verify

30. copy everything to the server

31. $ cat jira-rsync.conf
# On <DESTHOST>, run as user jira:
# rsync --daemon --port=1234
# --config=/home/jira/jira-5.2.6-rsync.conf
# Then on <SOURCEHOST>, run as user jira:
# cd /home/jira/jira-4.4.1-data;
# rsync -aHPv --port=1234
# --progress caches data plugins
# DESTHOST::jira-5.2.6
[jira-5.2.6]
path = jira-5.2.6-data
use chroot = false
readonly = false
uid = jira
gid = jira

32. CONFIGURATION

33. common customizations
• ssl proxy
• jvm memory settings
• session timeout
• template customizations
• added files

35. notification email template
old behavior –
Subject: (Jira) Resolved: [OPS-123] package Jira
new behavior –
Subject: (Jira) [OPS-123] package Jira
We liked it the old way!

36. custom email template

37. We needed this one!
priority thumbnail files

38. unpackaged common settings
• ldap user directory
• internal admin user

39. per-environment customizations
DEV
STAGE
PROD
• env-specific app behavior
• self-contained suite for each env

43. `
look and feel

44. more environment settings in the db
• base url
• whitelist urls
• email prefix
• server license

45. application links

46. per-instance customizations
DEV
STAGE
PROD
• unique instance identifier
• unique ports

47. unique identifier per instance
• instance id: app/version/env
such as “jira-5.2.6-dev”
• uniquely identifies:
• installation & data directories
• virtualhost name
• database name
• init script name

48. don’t connect dev to the prod db!

49. user data, or config settings?
• projects
• project components & versions
• global and per-project roles
• custom fields, screens, & workflows
• permission & notification schemes

50. OUR GOAL

51. our goal: package everything

52. whatever gets it done!

53. not the standard Atlassian way

54. advantages of our way
• for deployments
• for upgrades
• for customizations

55. FUTURE

56. future improvements
• more configuration
• better server management
• easier refresh
• content cleanup
• refactoring?

57. TMTOWTDI
There’s More Than One Way To Do It...

58. Thank you!
raju@pandora.com
myra@pandora.com

59. Rate this Talk
Automated Configuration & Deployment of
Atlassian Applications
Text code below to 22333
or visit http://bit.ly/19K6NRq
MEH = 5N
NO T BA D = 5P
P R ET T Y GO O D = 5Q
A WES O ME = 5R
To join this session, send text 136888 to