SpinnakerとGitLabの比較

このページのコンテンツ

• 要約
• Armory.io
• Strengths
• 不足部分
• リソース
• 比較

要約

Spinnaker is an open-source, multi-cloud continuous delivery platform that helps you release software changes. Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers. (source:)

Like Spinnaker, GitLab is also open source and also provides a flexible CD pipeline management system, is able to deploy to major cloud providers, and also offers advanced deployment patterns such as canary and incremental (rolling) deployments. In addition to this, GitLab provides not just the CD portion of the SDLC, but also everything else from planning, to CI, to testing, packaging, monitoring, and security scanning, all in a single application.

Spinnaker provides two core sets of features:

1. Application management: This is primarily to view and control your cloud resources. In Spinnaker an Application is modeled along the lines of Microservices. An application contains clusters, which consists of Server Groups. The Application also models Load Balancers and Firewalls.

2. Application deployment: This construct is used to model and manage continuous delivery workflows. A key element of Application Deployment is the Pipeline. A pipeline consists of a series of actions or stages which can be executed manually or automatically triggered. Parameters can also be passed from one stage to another and used for further actions.

At a macro level Spinnaker provides a normalized taxonomy of artifacts and actions that can apply across cloud providers. Using this normalized taxonomy one can build complex pipelines for a cloud provider or across cloud providers.

Spinnaker was created in the pre-kubernetes era and the code base did not take Kubernetes effet. This could lead to higher deployment and maintenance costs. To manage more complex enterprise environments, Armory.io provides an enterprise distribution for Spinnaker.

Armory.io

Armory.io provides an enterprise distribution of Spinnaker. That a third party company has to provide an enterprise distribution provides sufficient indication on the limitations/challenges of the Spinnaker platform.

Furthermore, Armory.io's business model is heavily dependent on their services team's involvement in customer accounts. So it is more services less product. A clear indication of the need for services is the Armory.io pricing page that lists the three enterprise offerings but no pricing on any of them. This is likely due to the unpredictability of the services component within each customer engagement.

Strengths

• Easy application deployment across cloud providers.
• Pre-packaged actions that can be easily applied, without need for lower level understanding of different cloud provider's concepts.
• Spinnaker is Open Source and has a community of developers contributing to the project.
• Complex, simultaneous deployments as first-class citizens.

不足部分

• Only supports the Continuous Delivery (CD) phase of a DevOps cycle.
• Normalized taxonomy does not apply across cloud providers. For example, an Amazon ECS cluster does not map to any core Spinnaker concept. So these need to be set up separately, thus diminishing the value that Spinnaker can provide.
• Cloud providers differ in how they deploy and manage applications, thus eventually users need to get down to individually understanding each provider.
• Spinnaker does not support OpenStack.
• Only available in Self-hosted and managed option. No Cloud version of Spinnaker.
• Steeper learning curve - Pipeline expression language uses a custom syntax, which entails a learning curve for users. Moreover, some string manipulation and other expression evaluation requires use of java code within the expression language. Nested expressions are not supported in Pipeline expression logic, this can be a limitation in some scenarios.

リソース

• Pipeline Expression Reference
• Spinnaker Github Repo

比較