If you are only interested in using Spinnaker, please refer to the main Spinnaker site and [Getting Started](http://spinnaker.io/documentation/getting_started.html) guide.
These instructions cover pulling Spinnaker from source and setting up to run locally against Amazon Web Services and/or Google Cloud Platform accounts.
Please ensure you have set up your target environment correctly by following step 1 of the Getting Started Documentation.
If you do not wish to build from source, please follow the Install and Run Spinnaker section of the getting started guide for a one line deployment in Ubuntu.
If you would prefer to try a container based solution, see docker-compose installation
These scripts are tested on:
-
Ubuntu 14.04 LTS
-
Mac OS X 10.11
#export SPINNAKER_HOME=/path/to/your/Spinnaker/workspace
mkdir -p $SPINNAKER_HOME
cd $SPINNAKER_HOME
git clone [email protected]:spinnaker/spinnaker.gitThe Spinnaker platform has a few prerequisites, which are installed as a part of this configuration process. They are:
You need to have homebrew installed and ensure your version of git is above 2.0.
brew install redis cassandra brew-cask packer
brew cask install java
cd $SPINNAKER_HOME
mkdir build
cd build
../spinnaker/dev/refresh_source.sh --pull_origin --use_ssh --github_user defaultcd $SPINNAKER_HOME
spinnaker/dev/install_development.sh --package_manager
spinnaker/dev/bootstrap_dev.shThe --package_manager argument requests the Debian Package Manager be used
to the greatest extent possible. This permits adding new source repositories
where package dependencies are distributed from non-standard repositories
(e.g. cassandra). The alternative is --nopackage_manager to use the
Package Manager for standard dependencies but explicitly install packages
that come from other sources. --nopackage_manager is intended for
installations where IT policies discourage or forbid adding additional
source locations.
The bootstrap_dev.sh script will ask to install additional components.
packer is only needed if you plan on building VM images. gcloud
is only needed to write releases to Google Cloud Storage, but is convenient
to have if you plan on using or accessing Google Cloud Platform resources
from your development environment. These could be installed at a system level
rather than user level, but the default install requires updating your path
so is performed here.
We will create a directory for Spinnaker configuration overrides, copy the default configuration template there, and edit to select the appropriate cloud provider(s).
cd $SPINNAKER_HOME
mkdir -p $HOME/.spinnaker
cp spinnaker/config/default-spinnaker-local.yml $HOME/.spinnaker/spinnaker-local.yml
chmod 600 $HOME/.spinnaker/spinnaker-local.ymlEdit $HOME/.spinnaker/spinnaker-local.yml and set the enabled option for the cloud provider(s) of your choice.
( If you’re running on Mac OS, please make sure that your redis server and cassandra server is up and running. Make sure that cqlsh is accessible in your path and you can connect to cassandra by calling cqlsh in your terminal ).
cd $SPINNAKER_HOME/build
../spinnaker/dev/run_dev.sh [service]If a service is provided, then just that one service will be started. If no service is provided, then all the services will be started (including redis and cassandra unless they are specified with a remote host). If a service is already running (even if not yet available) then it will not be restarted.
Note run_dev.sh might get stuck waiting on a service to start. Hitting CTRL-C just stops the waiting on service it doesn’t terminate the services. If it seems stuck
stop and restart run_dev.sh.