Deployment Tools and Techniques Cengiz Gnay CS485/540 Software - - PowerPoint PPT Presentation

▶
deployment tools and techniques
SMART_READER_LITE
LIVE PREVIEW

Deployment Tools and Techniques Cengiz Gnay CS485/540 Software - - PowerPoint PPT Presentation

Feb 02, 2024 124 likes •409 views

Deployment Tools and Techniques Cengiz Gnay CS485/540 Software Engineering Fall 2014, some slides courtesy of J. Smith, R. Pressman, I. Sommerville, and the Internets Gnay (Emory MathCS) Deployment Fall 2014 1 / 6 (c) military.com The

slide-1
SLIDE 1

Deployment Tools and Techniques

Cengiz Günay CS485/540 Software Engineering Fall 2014, some slides courtesy of J. Smith, R. Pressman, I. Sommerville, and the Internets

Günay (Emory MathCS) Deployment Fall 2014 1 / 6

slide-2
SLIDE 2

(c) military.com

slide-3
SLIDE 3

The father of all build/deployment tools: Make

Compiling/building: $ gcc -o hello hello.c -I.

Günay (Emory MathCS) Deployment Fall 2014 3 / 6

slide-4
SLIDE 4

The father of all build/deployment tools: Make

Compiling/building: $ gcc -o hello hello.c -I. With the following Makefile: hello: hello.c hello.h gcc -o hello hello.c -I.

Günay (Emory MathCS) Deployment Fall 2014 3 / 6

slide-5
SLIDE 5

The father of all build/deployment tools: Make

Compiling/building: $ gcc -o hello hello.c -I. With the following Makefile: hello: hello.c hello.h gcc -o hello hello.c -I. Will check if timestamp of hello.* is newer than hello before building: $ make hello Nothing to make.

Günay (Emory MathCS) Deployment Fall 2014 3 / 6

slide-6
SLIDE 6

Why is Make popular?

Good with complex dependencies Can make general rules CC=gcc CFLAGS=-I. DEPS=hellomake.h %.o: %.c $(DEPS) $(CC) -c -o $@ $< $(CFLAGS)

Günay (Emory MathCS) Deployment Fall 2014 4 / 6

slide-7
SLIDE 7

Why is Make popular?

Good with complex dependencies Can make general rules CC=gcc CFLAGS=-I. DEPS=hellomake.h %.o: %.c $(DEPS) $(CC) -c -o $@ $< $(CFLAGS) Common Makefile targets: compile, install, doc, clean

Günay (Emory MathCS) Deployment Fall 2014 4 / 6

slide-8
SLIDE 8

A modern make: Apache Ant

Ant: Started as for Java, uses XML-formatted build.xml: <project name="Sample Project" default="compile" basedir="."> <!-- global properties for this build file --> <property name="source.dir" location="src"/> <!-- set up some directories used by this project --> <target name="init" description="setup project directories">...</target> <!-- Compile the java code in src dir into build dir --> <target name="compile" depends="init" description="compile java sources"/> <!-- Generate javadocs for current project into docs dir --> <target name="doc" depends="init" description="generate documentation"/> <!-- Delete the build & doc directories and Emacs backup (*~) files --> <target name="clean" description="tidy up the workspace"/> </project>

Günay (Emory MathCS) Deployment Fall 2014 5 / 6

slide-9
SLIDE 9

Other tools

configure: For detecting the environment before compiling/installation/deployment. Apache Maven: Supercedes Ant. Phing: For PHP CMake: a new program that aims to replace configure+make

Günay (Emory MathCS) Deployment Fall 2014 6 / 6

slide-10
SLIDE 10

Deploying Web Applications

slide-11
SLIDE 11

Rules of the road

  • Use a Source Code Management tool
  • This is non-negotiable!
  • Git > Subversion, but use something
  • Keep everything under version control
  • Practice common repository management
  • “master”, branches, and tags
slide-12
SLIDE 12

“A successful Git branching model”

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

slide-13
SLIDE 13

Classic web application infrastructure

cache01 cache02 Load balancer db01 (master) db02 (slave) web01 web02 web03 web04 web05 web06 batch01 batch02 Internet

slide-14
SLIDE 14

Deploying web application code

  • Deploying should be a one-step process
  • Code always sourced from SCM repository
  • Be able to rollback quickly
  • Always deploy (or at least tag) a numbered

release

  • Apply database changes
  • Don’t take your web app down (if you can

help it)

slide-15
SLIDE 15

Web server config and filesystem

<VirtualHost *:80> ServerName www.example.org DocumentRoot /home/web/site/current/public_html </VirtualHost> $ pwd /home/web/site web@dev:~/site$ ls -al total 28 drwxrwxr-x 7 web web 4096 2012-11-24 21:55 . drwxr-xr-x 3 web web 4096 2012-11-24 21:52 .. drwxrwxr-x 2 web web 4096 2012-11-24 21:55 1.0.0 drwxrwxr-x 2 web web 4096 2012-11-24 21:55 1.0.1 drwxrwxr-x 2 web web 4096 2012-11-24 21:55 1.0.2 drwxrwxr-x 2 web web 4096 2012-11-24 21:55 1.1.0 drwxrwxr-x 5 web web 4096 2012-11-24 21:56 1.1.1 lrwxrwxrwx 1 web web 5 2012-11-24 21:55 current -> 1.1.1

slide-16
SLIDE 16

Deployment tools

  • Build your own
  • Push/pull tarball from Amazon S3 service
  • rsync’s code to local disk
  • Capistrano
  • Written in Ruby
  • Performs “tasks” on “roles” of servers
  • Ant, Phing, Deployinator (Etsy)
slide-17
SLIDE 17

Deploying database objects

  • Your database always moves forward in

time

  • “up” and “down” changes
  • up_X.sql -- creates and modifies objects
  • down_X.sql -- undoes the changes in “up”
  • Each change has a version number
  • Rails migrations, Doctrine
slide-18
SLIDE 18

Sample database up/down pair

up_1353811475.sql create table user ( id integer unsigned not null, username varchar(20) not null, password_hash varchar(100) not null, created datetime, last_updated datetime, last_login datetime, constraint user_pk primary key (id), constraint user_username_uk unique key (username)); insert into schema_version ( num) values ( 1353811475); down_1353811475.sql drop table user; delete schema_version where num = 1353811475);

slide-19
SLIDE 19

Common gotchas

  • Rotate your log files
  • Centralize them, too!
  • Important to write robust, defensive code
  • Be able to monitor everything
  • Munin, statsd, Graphite, etc.
  • Design for failure
  • Have at least two of everything
slide-20
SLIDE 20

Other pearls of wisdom

slide-21
SLIDE 21

Coding standards

  • Coding standards are insanely

important

  • Ensures that all developers on a team

write:

  • Code that looks the same
  • Is maintainable by anyone on the team
  • These are not optional.

You follow them. Period.

slide-22
SLIDE 22

Testing and QA in the real world

  • When time and budgets are tight:
  • It’s really easy to skimp on writing tests for

your code

  • You just want to meet your deadline
  • Acceptance testing of a release can be shorter

than normal

  • Meeting client deadline > 100% code

coverage

slide-23
SLIDE 23

Understanding the sysadmin side

  • Understanding systems administration has

been a huge differentiator for me

  • The best devs I know understand this area well
  • When you write code, you think about what it

does on a server

  • Deeper understanding and respect for writing

efficient code

  • So much easier now due to virtualization
slide-24
SLIDE 24

Speak! Write!

  • Many software development conferences
  • You owe it to the community to share your

knowledge

  • Adapt your work into presentations
  • Write!
  • My former (and current) boss: “Publish or

perish”

slide-25
SLIDE 25

Books!

slide-26
SLIDE 26

References

  • Code As Craft
  • http://codeascraft.etsy.com/
  • PHPUnit
  • https://github.com/sebastianbergmann/phpunit/
  • Grumpy Programmer’s Guide to Building

Testable Applications in PHP

  • http://www.grumpy-testing.com/
slide-27
SLIDE 27

Thanks!

brian@deshong.net http://www.deshong.net/ brian@crowdtwist.com http://www.crowdtwist.com/