conan

Conan da Deployer

This project provides automation for a deployment pipeline (ala 'Continous Delivery') which provisions, configures and deploys applications (Java and Ruby) to "ship-clouds". Configuration is modeled through a DSL as a list of logical target environments, each with a number of ship-clouds. Endpoints for web applications and Stackato PaaS APIs are created based on conventions, including support for Blue/Green deployments.

Applications are deployed from a Sonotype Nexus artifact repository, and not from the source repository. Java applications must be executable jars, and must the provide deployment resources needed in the jar. Ruby apps (Rails or otherwise) must be vendored and packaged as a tar ball, with a compatible structrue to provide the deployment resources.

Application artifacts are idenitifed and provisioned by Maven coordinates - group id, artifact id, packaging and version. The most recent version available on the repository will be used, or a promotion workflow along the pipeline(s) can be implemented by pinning the versions. Artifacts are pinned by keeping the build meta-data in an environments directory structure that mirrors the configuration model, which should be commited to version control after successful deployment and testing. At this time, the environments directory and the environments.rb are located from the execution directory, which is assumed to be the nexus-apps-manifest project.

Conan is also designed to be idempotent. It can be executed against a target deployment over and over, and it should not change an application unless it out of alignment with the configuration model. Applications are also assumed to support standard set of managments APIs which provide build metadata, and health to support this.

Configuration

Configuration for the deployment pipline is loaded through a DSL which models a target environment(s). The DSL is loaded from a environments.rb file that should be provided in the execution directory.

  pipeline(:'team1') {
    app(:foo, 'com.mtnsat:foo', :jvm)
    app(:bar,   'com.mtnsat:bar', :rails_zip)
  }
  pipeline(:'team2')
    app(:baz,  'com.mtnsat:baz-web', :rails_zip)
    app(:bang,  'com.mtnsat:bang', :rails_zip)
  }

  environment(:integ) {
    org('mtn') {
      deploy('aws') {
        apps :foo
      }
      deploy('sea1') {
        apps :foo, :bar
        facility '999'
      }
      deploy('mia1') {
        apps :foo, :bar, :baz
        facility '888'
      }
    }
  }  

  environment(:prod) {
    promotes_from :integ
    org('mtn') {
      deploy('aws') {
        apps :foo
      }
    }
    org('acme') {
      deploy('minnow1') {
        enabled false
        apps :foo, :bar, :baz
        facility '42'
      }
      deploy('minnow1') {
        apps :bang
        option 'mapping', 'acme-stuff.com'
        option 'do-dad', 'flim-flam'
      }
      deploy('bounty1') {
        apps :foo, :bar, :baz
        facility '100'
      }
      deploy('bounty1') {
        apps :bang
        option 'mapping', 'acme-stuff.com'
        option 'do-dad', 'woo-woo'
      }
    }
  }

pipeline: any number of application pipelines. Takes a symbol for the pipeline, and defines the apps that are delivered by that pipeline
app: any number of applications. Takes a symbol for the app, a maven group_id:artifact_id and the type of platform the app uses (:jvm or :rails_zip)
environment: any number of environments. takes a symbol for the environment, and any number of deploys. NOTE: the order is not significant.
promotes_from: a declaration to control what environment the provisioning uses to check for new versions to promote. The absence of this declartation means that the artifact repository will be checked for the latest version
org: scopes the deployment to the organization served by those deployments.
deploy: describes a deployment to the given ship-cloud. It takes a key for the ship, and some attributes
endabled: deployments will be avoided if not 'true', default value is 'true' if absent
apps: a list of symbols for applications (defined in pipeline/app above) which should be deployed to the environment
facility: the facitility id
option: a way to define a key/value pair for deploy/app specific configurations (can be used multiple times to define N number key/value pairs)

conan

Configuration

Usage

Templates

Test