Service Configuration Management for Rapid Growth

Service Configuration Management
For Rapid Growth
Friday, September 6 2013
Echelon Ignite 2013 Thailand

Takashi SOMEDA
https://twitter.com/tksmd
Tech Evangelist of Nulab,Inc.
About me
https://facebook.com/takashi.someda
Write tech articles about AWS, SCM
https://github.com/tksmd

Backlog is a project management tool that 1,800 clients use.
In addition to issue management feature, Backlog provides
• File sharing by WebDAV
• Git and Subversion repository hosting.
Visit http://backlogtool.com/

950,000 users around the world draw wireframes, network diagrams,
UML, business plans and so on.
Cacoo provides basic functionality as a draw tool and powerful collaborative
features like
• Simultaneous Editing on same diagram by multiple users
• Integration with Google Services like Google Apps, Google Drive and Google+
Hangouts

A new collaborative chat app just opened as preview beta.
• Revolutionize your team discussion
• Integration with nulab’s services
• Provide easy-to-use API for developers
Be the first to get notified when the app is launched. http://typetalk.in

User Growth of Cacoo
0
100,000
200,000
300,000
400,000
500,000
600,000
700,000
800,000
900,000
1,000,000
Oct,2010 Oct,2011 Oct,2012 Sep,2013
62,000
200,000
600,000
950,000
All
Japan
Overseas

Tipping points

Why is
configuration management
important ?

Extreme
Uncertainty
http://www.flickr.com/photos/bilal-kamoon/6835060992/

http://www.slideshare.net/mattangriffel/growth-hacking/82

http://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version/19

http://www.slideshare.net/startuplessonslearned/eric-ries-the-lean-startup-google-tech-talk/25

1K+ deploys/hour
https://reinvent.awsevents.com/recap.html

Need to balance
Speed & Quality

GOAL
Business, Customer, Market
What
Growth Hack
Lean Startup
How
Team
Proces
s
Todays topic

Agenda
 Configuration Management in essence
 Version Control System (VCS)
 Continuous Integration (CI)
 Server Orchestration & Configuration
 Live Demo

VCS
CI
Service
source
code
Server
Configuration
Server
Orchestration
app
servers
Test
Test
configure
deploy

Configuration management refers to the process
by which all artifacts relevant to your project,
and the relationships between them, are
sorted, retrieved, uniquely identified, and modified.
Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
Jez Humble, David Farley

Keep everything in
Version Control System
http://www.flickr.com/photos/munaz/2498380666/

Without VCS

VCS in a nutshell

VCS Architecture
 Centralized
 Repository maintained on server
 CVS, Subversion
 Distributed
 Each client has its repository
 Git, Mercurial, (Bazaar)

What to keep in VCS
 Source
 Build Script
 Ant, Maven, Gradle, Rake, Makefile
 Database Script
 Schema, Migration
 Server related files
DO NOT put binary artifacts

Run “beta” in a real world
 To know whether you’re going toward right
place as fast as possible
 Rule
 Run on “real” data, not dummy
 Speed >>> Quality
 Limited user ( at least yourself )

flag or branch
if(flagA){
}
if(flagA){
}
if(flagB){
}
flag
branch
production
feature A
feature B

Pros and cons of “flag”
 Pros.
 Same code running on all servers
 Simple and quick release
 Cons.
 Scattered “if” statements on your code

Pros and cons of “branch”
 Pros.
 Keep source code clean
 Cons.
 Integration (merge) cost
 conflict risk
 Need additional server to run “branch”
code

Beta strategy
 Decide basic policy in your team
 If your code changes many things
 Use “branch” and refine the code in
the beta
 Switch “flag” after the quality
becomes satisfying and expose it to
the production
 Just turn the flag on at release

http://nvie.com/posts/a-successful-git-branching-model/

http://www.flickr.com/photos/alexmartin81/5883645329/
Every commit should be built
immediately

What’s CI
 One of agile practice originally
 To detect integration problem earlier, do
integrate repeatedly and frequently
 Core of “Delivery Pipeline”
 Lots of things can run on CI server

Benefits of CI
 Quick feedback
 Early detection of build issues
 Ensuring traceability
Start small, scale gradually

What to build
 Compile
 Run tests
 Assemble
 Inspection
 Generate Docs
 Etc…

Package Repository
 Maintain your own repository
 Maven repo, cpan, pypi, gem
 Shared folder
 Amazon S3
 Used by both
 Development
 Testing
 Server configuration

Failure feedback from CI
 Notification via
 E-mail
 Group
 those who broke code
 IRC / Chat
 ITS / BTS
Take action as soon as possible

CI build time
 Should be done within 30mins
 If build time exceeds it
 Split into smaller pieces
 Build parallel
 Get a higher spec machine

Testing in CI
 Unit Test
 Integration Test
 Server Configuration Test
 Smoke Test

Build Pipeline

http://www.flickr.com/photos/naturegeak/5688437941/
Cloud-native server management

Why “Cloud” for startups
 Extremely flexible
 Scalable
 Global infrastructure
NOT the cheapest solution

Paradigm shift of “Cloud”
 All resources are
 completely virtualized
 programmable
 allocated and available soon
BUT everything will be possibly broken
in a meanwhile

NOT
prevent failure
BUT
restore from failure
quickly

Design principle for failure
 Keep each server small and simple
 Building a brand-new server faster than
fixing broken one
 Distribute servers to different physical
locations
Need to manage much more servers
than on-premises

Problem of ad-hoc management
http://www.flickr.com/photos/getbutterfly/6317955134/
What servers are patched
and
What are not ?!

Provisioning Layer
http://devops-toolchain.googlecode.com/svn/trunk/src/site/resources/presentations/Velocity2010/
Application Service Orchestration
System Configuration
Cloud or VM
Image Launch
OS installBootstrapping
Configuration
Command
and
Control

Orchestration Tasks
 Deploy
 System administration
 stop / start middleware
 Build temporary environment
 batch / testing
DO NOT include configuration

Migration from “bare” scripts
 Try simple tool
 No server installation required
 Needs SSH connection only
 Select tool which is written in your familiar
language

Server Configuration Principles
 Declarative
 Abstraction
 Idempotent
 Convergence
DO NOT touch environment directly

Difference between them
 Server Orchestration manages
“execution”
 Changing server state to single
direction
 Focus on temporally control
 Server Configuration manages “state”
 Converging server into a “state”
 can be tested repeatedly

Popular tools
 Orchestration
 Capistrano
 Fabric
 Configuration
 Chef
 Puppet
 Ansible

Configuration Test
httpd package installed
httpd service enabled
httpd service started
80 port listened
:
Is httpd package
installed?
Is httpd service enabled ?
Is httpd running ?
Is 80 port listened?
:
Configuration Test

VCS in server management
 Use VCS same as application source
 Keep into VCS
 Configuration files
 Administration scripts
 Orchestration scripts
 Configuration scripts

Summary
http://www.flickr.com/photos/nauright/2662160957/

Speed = Automation
Quality = Testing

Service Configuration Management for Rapid Growth

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Service Configuration Management for Rapid Growth

Similar to Service Configuration Management for Rapid Growth (20)

More from Takashi Someda

More from Takashi Someda (13)

Recently uploaded

Recently uploaded (20)

Service Configuration Management for Rapid Growth