FlockerHub
Fli
Flocker
Blog
Partners
About
Careers
Sign up for FlockerHub
Contents
+
Install & Docs
Flocker Integrations
Docker, Swarm, Compose
Kubernetes
Mesos
Other Systems
Supported Configurations
Administering Flocker
Flocker Features
Reference
Release Notes
FAQs
Getting Involved
Contributing to Flocker
Contributing a New Flocker Storage Backend
Acceptance Testing
Functional Testing
Setting Up a Test Cluster
Extending a Cluster
Benchmarking
Client Testing
Infrastructure
Authors
Infrastructure
ΒΆ
Contents:
Building Omnibus Packages
Instructions for Distribution Maintainers
Package Hosting
clusterhq-archive
clusterhq-release
package
Legacy
Building Docker Images
flocker-dataset-agent
flocker-control
flocker-docker-plugin
Release Process
Outcomes
Prerequisites
Preparing For a Release
Pre-tag Review Process
Release
Improving the Release Process
Release Schedule and Version Numbers
Goals
Schedule
Version Numbers
Documentation Hosting
S3 Buckets
CloudFront Distributions
Maintaining Flocker CloudFormation Installer
Architecture
How does CloudFormation work?
How are user-specific inputs (like AWS AccessKeyID) sourced?
Why is there a wrapper around S3 commands?
What happens if CloudFormation fails to bring up the stack?
How are Flocker, Docker, and Swarm configured?
What happens if Flocker, Docker, or Swarm configuration fails?
How do I debug a failed stack creation?
One of my stack nodes failed to bring up Flocker/Docker/Swarm. How do I debug?
Previous
Next
How could we improve this page?
