Go to file

Mark Burnett ecbe862a24 Avoid directly installing non-frozen dependencies

Currently the Dockerfile specifies running `pip install -e ...`, which
will indirectly install dependencies from `requirements.txt`.  This is
generally safe, but should be avoided, since we are exclusively using
frozen dependencies.

Change-Id: Ie368ddb9f1229cc248c8d8804c71889c4339aa85

2017-10-20 10:54:10 -05:00

charts

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

docs/source

Create Promenade API documentation

2017-10-19 15:47:10 -04:00

example

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

promenade

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

tests

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

tools

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

.dockerignore

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

.gitignore

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

.gitreview

Add gitreview file

2017-08-11 01:18:30 -05:00

Dockerfile

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

LICENSE

Initial commit

2017-02-14 11:13:39 -08:00

README.md

Add documentation for configuration

2017-07-03 15:36:56 -05:00

requirements-direct.txt

Avoid directly installing non-frozen dependencies

2017-10-20 10:54:10 -05:00

requirements-frozen.txt

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

requirements.txt

Avoid directly installing non-frozen dependencies

2017-10-20 10:54:10 -05:00

setup.cfg

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

setup.py

Basic HA kubernetes deployment (#7 )

2017-06-15 20:57:22 -07:00

test-requirements.txt

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

tox.ini

Avoid directly installing non-frozen dependencies

2017-10-20 10:54:10 -05:00

Vagrantfile

Migrate to self hosted using charts

2017-10-17 13:29:46 -05:00

README.md

Promenade

Promenade is a tool for bootstrapping a resilient Kubernetes cluster and managing its life-cycle.

Roadmap

The detailed Roadmap can be viewed on the LCOO JIRA.

Cluster bootstrapping
- Initial Genesis process results in a single node Kubernetes cluster with Under-cloud components deployed using Armada.
- Joining sufficient master nodes results in a resilient Kubernetes cluster.
- Destroy Genesis node after bootstrapping and re-provision as a normal node to ensure consistency.
Life-cycle management
- Decommissioning of nodes.
- Updating Kubernetes version.

Getting Started

To get started, see getting started.

Configuration is documented here.

Bugs

Bugs are tracked in LCOO JIRA. If you find a bug, feel free to create a GitHub issue and it will be synced to JIRA.