{"__v":8,"_id":"56c14ca9f203270d00d6c546","api":{"auth":"required","params":[],"results":{"codes":[]},"settings":"","url":""},"body":"Spinnaker is an open source, multi-cloud continuous delivery platform that helps you release software changes with high velocity and confidence.\n\nIt provides two core sets of features: *cluster management* and *deployment management*. Here is an overview of these features:\n\n## Cluster Management\n\nYou use Spinnaker's cluster management features to manage the following resources in the cloud: \n\n* **Server Group**: The base resource, the *Server Group*, identifies the machine instance profile on which to execute images along with the number of instances. This resource is associated with a Load Balancer and a Security Group. A Server Group also has basic configuration settings, such as user account information and the region/zone in which images are deployed. When deployed, a Server Group is a collection of virtual machines running software.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/4l9kTko1SVSIcI26iBSR_server_group.png\",\n        \"server_group.png\",\n        \"506\",\n        \"316\",\n        \"#c92933\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n* **Security Group**: A *Security Group* defines network traffic access. It is effectively a set of firewall rules defined by an IP range (CIDR) along with a communication protocol (e.g., TCP) and port range.\n* **Load Balancer**: A *Load Balancer* is associated with an ingress protocol and port range. It balances traffic among instances in its Server Group. Optionally, you can enable health checks for a load balancer, with flexiblity to define health criteria and specify the health check endpoint.\n* **Cluster**: You can define *Clusters*, which are logical groupings of Server Groups in Spinnaker.\n\n## Deployment Management\n\nYou use Spinnaker's deployment management features to construct and manage continuous delivery workflows. These are some of the concepts associated with deployment management:\n\n* **Pipeline**: *Pipelines* are the key deployment management construct in Spinnaker. They consist of a sequence of actions, known as stages. You can pass parameters from stage to stage along the pipeline. You can start a pipeline manually, or you can configure it to be started by automatic triggers, such as a Jenkins job, a CRON schedule, or a stage in another pipeline. You can configure the pipeline to emit notifications to interested parties at various points during pipeline execution (such as on pipeline start/complete/fail), by email, SMS or HipChat.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/Y1X8CO7KTkO7vO9x3ZZi_pipeline.png\",\n        \"pipeline.png\",\n        \"486\",\n        \"271\",\n        \"#4585c5\",\n        \"\"\n      ],\n      \"sizing\": \"smart\"\n    }\n  ]\n}\n[/block]\n* **Stage**: A *Stage* in Spinnaker is an action that forms a atomic building block for a pipeline. You can sequence stages in a Pipeline in any order, though some stage sequences may be more common than others. Spinnaker comes pre-packaged with a number of stages, including:\n  * **Bake**: Bakes an image in the specified region.\n  * **Deploy**: Deploys a previously baked or found image.\n  * **Destroy Server Group**: Destroys a server group.\n  * **Disable Server Group**: Disables a server group.\n  * **Enable Server Group**: Enables a server group.\n  * **Find Image**: Finds a previously-baked image to deploy into an existing cluster.\n  * **Jenkins**: Runs a Jenkins job.\n  * **Manual Judgment**: Waits for user approval before continuing.\n  * **Modify Scaling Process**: Suspend or resume server group scaling processes.\n  * **Pipeline**: Runs a pipeline. This allows you to compose pipelines hierarchically.\n  * **Quick Patch Server Group**: Quick lypatches a server group (used for emergency patches).\n  * **Resize Server Group**: Resizes a server group.\n  * **Script**: Runs an arbitrary shell script.\n  * **Shrink Cluster**: Shrinks a cluster.\n  * **Wait**: Waits a specified period of time.","category":"55c6bec2b9aa4e0d0016c2c7","createdAt":"2016-02-15T03:57:29.648Z","excerpt":"","githubsync":"","hidden":false,"isReference":false,"link_external":false,"link_url":"","order":0,"parentDoc":null,"project":"55c6bec1b9aa4e0d0016c2c3","slug":"overview","sync_unique":"","title":"Overview","type":"basic","updates":["5748b1b7919ad20e00b6c791","5862ddb983cbbf1900cf75a6","5862ddb95a47fe1900565da8","5862ddbaba46b22d003937ef"],"user":"55c6b99c476be90d00500805","version":"55c6bec1b9aa4e0d0016c2c6","childrenPages":[]}
Spinnaker is an open source, multi-cloud continuous delivery platform that helps you release software changes with high velocity and confidence. It provides two core sets of features: *cluster management* and *deployment management*. Here is an overview of these features: ## Cluster Management You use Spinnaker's cluster management features to manage the following resources in the cloud: * **Server Group**: The base resource, the *Server Group*, identifies the machine instance profile on which to execute images along with the number of instances. This resource is associated with a Load Balancer and a Security Group. A Server Group also has basic configuration settings, such as user account information and the region/zone in which images are deployed. When deployed, a Server Group is a collection of virtual machines running software. [block:image] { "images": [ { "image": [ "https://files.readme.io/4l9kTko1SVSIcI26iBSR_server_group.png", "server_group.png", "506", "316", "#c92933", "" ] } ] } [/block] * **Security Group**: A *Security Group* defines network traffic access. It is effectively a set of firewall rules defined by an IP range (CIDR) along with a communication protocol (e.g., TCP) and port range. * **Load Balancer**: A *Load Balancer* is associated with an ingress protocol and port range. It balances traffic among instances in its Server Group. Optionally, you can enable health checks for a load balancer, with flexiblity to define health criteria and specify the health check endpoint. * **Cluster**: You can define *Clusters*, which are logical groupings of Server Groups in Spinnaker. ## Deployment Management You use Spinnaker's deployment management features to construct and manage continuous delivery workflows. These are some of the concepts associated with deployment management: * **Pipeline**: *Pipelines* are the key deployment management construct in Spinnaker. They consist of a sequence of actions, known as stages. You can pass parameters from stage to stage along the pipeline. You can start a pipeline manually, or you can configure it to be started by automatic triggers, such as a Jenkins job, a CRON schedule, or a stage in another pipeline. You can configure the pipeline to emit notifications to interested parties at various points during pipeline execution (such as on pipeline start/complete/fail), by email, SMS or HipChat. [block:image] { "images": [ { "image": [ "https://files.readme.io/Y1X8CO7KTkO7vO9x3ZZi_pipeline.png", "pipeline.png", "486", "271", "#4585c5", "" ], "sizing": "smart" } ] } [/block] * **Stage**: A *Stage* in Spinnaker is an action that forms a atomic building block for a pipeline. You can sequence stages in a Pipeline in any order, though some stage sequences may be more common than others. Spinnaker comes pre-packaged with a number of stages, including: * **Bake**: Bakes an image in the specified region. * **Deploy**: Deploys a previously baked or found image. * **Destroy Server Group**: Destroys a server group. * **Disable Server Group**: Disables a server group. * **Enable Server Group**: Enables a server group. * **Find Image**: Finds a previously-baked image to deploy into an existing cluster. * **Jenkins**: Runs a Jenkins job. * **Manual Judgment**: Waits for user approval before continuing. * **Modify Scaling Process**: Suspend or resume server group scaling processes. * **Pipeline**: Runs a pipeline. This allows you to compose pipelines hierarchically. * **Quick Patch Server Group**: Quick lypatches a server group (used for emergency patches). * **Resize Server Group**: Resizes a server group. * **Script**: Runs an arbitrary shell script. * **Shrink Cluster**: Shrinks a cluster. * **Wait**: Waits a specified period of time.