Spinnaker Architecture on Spinnaker

Spinnaker Architecture Overview

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker microservices

Spinnaker is composed of a number of independent microservices:

Deck is the browser-based UI.
Gate is the API gateway.

The Spinnaker UI and all api callers communicate with Spinnaker via Gate.
Orca is the orchestration engine. It handles all ad-hoc operations and pipelines. Read more on the Orca Service Overview .
Clouddriver is responsible for all mutating calls to the cloud providers and for indexing/caching all deployed resources.
Front50 is used to persist the metadata of applications, pipelines, projects and notifications.

Life of a Bake

Mon, 01 Jan 0001 00:00:00 +0000

sequenceDiagram Title: Life of a Bake participant Igor participant Jenkins participant ArtifactRepo participant Echo participant Front50 participant Orca participant Rosco participant Packer participant Redis participant Cloud Echo->>Front50: Build cache of pipeline triggers Jenkins->>ArtifactRepo: Publish newly-produced deployable asset (e.g. .deb/.rpm/.jar) Note right of Jenkins: Archive artifacts Igor->>Jenkins: Poll Jenkins for completed builds Igor->>Echo: Publish completed build info to eventing bus Echo->>+Orca: Initiate pipeline execution based on matched trigger Orca->>Redis: Persist new execution Note right of Orca: Orca uses the artifact details from the trigger to decorate the package name with version information Orca->>-Rosco: Request bake, passing package with exact version to install Rosco->>Redis: Persist new bake Rosco->>Packer: Initiate bake job, passing repo address (from config) and package/version Packer->>ArtifactRepo: Pull deployable asset from repo Packer->>Cloud: Publish machine image Loop In background thread Rosco->>Packer: Poll until job completion Rosco->>Redis: Mark bake completed end Loop In worker thread Orca->>Rosco: Poll until task completion Rosco->>Redis: Query bake status Orca->>Redis: Update execution state end

Life of a Deployment

Mon, 01 Jan 0001 00:00:00 +0000

sequenceDiagram Title: Life of a deployment participant Deck participant Gate participant Orca participant Clouddriver participant Redis participant Cloud Deck->>+Gate: Initiate Deploy orchestration Gate->>+Orca: Initiate Deploy orchestration Orca->>Redis: Persist new execution Orca-->>-Gate: Reply with orchestration id Gate-->>-Deck: Reply with orchestration id Note right of Orca: In worker thread Orca->>+Clouddriver: Initiate Deploy operation Clouddriver->>Redis: Persist new task Clouddriver-->>-Orca: Reply with task id Clouddriver-xCloud: Mutating calls activate Clouddriver Clouddriver->>Redis: Mark task completed deactivate Clouddriver Loop In worker thread Orca->>Clouddriver: Poll until task completion Clouddriver->>Redis: Query task status Orca->>Redis: Update execution state end Loop In worker thread Orca->>Clouddriver: Poll until instances are up Clouddriver->>Redis: Query server group/instance state from cache Orca->>Redis: Mark execution completed end Loop In background thread Deck->>Gate: Poll until orchestration completion Gate->>Orca: Query orchestration status Orca->>Redis: Query execution status end