Skip to content
This repository has been archived by the owner on Feb 18, 2019. It is now read-only.
/ autopilot Public archive
forked from contraband/autopilot

cf plugin for hands-off, zero downtime application deploys

License

Notifications You must be signed in to change notification settings

HappyTobi/autopilot

 
 

Repository files navigation

Important

The fork will be developed under a new name CF-Puppeteer because of the cf-plugin issue #282

autopilot

build

cf plugin for hands-off, zero downtime application deploys

notice

Project forked from contraband. I started to maintain the autopilot project to support new version of cloudfoundry.

to give a better overview i created changelog to show all changes and new features.

Switched from go dep to govendor

version

The newes version is the 0.0.10 and worked and based on cf-cli version 6.42.0

changelog

To get more informations about the newest release see the Changelog

cf installation

Download the latest version from the releases page and make it executable.

$ cf install-plugin path/to/downloaded/binary

usage

$ cf zero-downtime-push application-to-replace \
    -f path/to/new_manifest.yml \
    -p path/to/new/path
    -t 120

or without application name

$ cf zero-downtime-push \
    -f path/to/new_manifest.yml \
    -p path/to/new/path
    -t 120

warning

Your application manifest must be up to date or the new application that is created will not resemble the application that it is replacing.

You can check your application doesn't have unexpected environment variables or services which are missing from the application manifest with Antifreeze.

method

Autopilot takes a different approach to other zero-downtime plugins. It doesn't perform any complex route re-mappings instead it leans on the manifest feature of the Cloud Foundry CLI. The method also has the advantage of treating a manifest as the source of truth and will converge the state of the system towards that. This makes the plugin ideal for continuous delivery environments.

  1. The old application is renamed to <APP-NAME>-venerable. It keeps its old route mappings and this change is invisible to users.

  2. The new application is pushed to <APP-NAME> (assuming that the name has not been changed in the manifest). It binds to the same routes as the old application (due to them being defined in the manifest) and traffic begins to be load-balanced between the two applications.

  3. The old application is deleted along with its route mappings. All traffic now goes to the new application.

local development

for local development you need to install govendor

About

cf plugin for hands-off, zero downtime application deploys

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 97.2%
  • Shell 2.8%