airship
/
promenade
Code Issues Proposed changes
A declarative framework for resilient Kubernetes deployment.
299 Commits 3 Branches 0 Tags 11 MiB
Python 47.6%
Shell 26.5%
Smarty 24.3%
Makefile 1.6%
Go to file
Felipe Monteiro eea5aaf0f6 Add basepython=python3.5 to [testenv] in tox.ini 
Running tox -e lint in an environment with python2.7 for example
as the default python interpreter causes the following errors
to be emitted:

lint runtests: commands[0] | yapf -rd /opt/stack/ucp/promenade/promenade /opt/stack/ucp/promenade/tests
lint runtests: commands[1] | flake8 /opt/stack/ucp/promenade/promenade
/opt/stack/ucp/promenade/promenade/renderer.py:18:39: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/config.py:17:19: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/tar_bundler.py:17:20: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/logging.py:76:12: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/generator.py:11:33: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/builder.py:15:33: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/pki.py:59:43: E999 SyntaxError: invalid syntax
/opt/stack/ucp/promenade/promenade/cli.py:13:16: E999 SyntaxError: invalid syntax

This PS just adds basepython=python3.5 to the base [testenv] category
from which jobs like tox -e lint inherit causing tox to use the python3.5
interpreter. Since Promenade only supports Python 3.5+ (since it isn't
tested against anything else), this won't break anything.

Change-Id: I549a02dbfa5f3b53bab26b87ad3042192e315530
 		2018-02-01 05:51:28 +00:00
charts Merge "Add deckhand design_ref support" 2018-01-22 15:04:51 -05:00
docs/source Merge "Doc updates for install and troubleshooting" 2018-01-24 17:40:15 -05:00
etc/promenade Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
examples Migrate to DH-managed config files 2018-01-26 13:43:18 -05:00
promenade Enable substitution using DH engine for Cert gen 2018-01-31 09:59:10 -06:00
tests Add deckhand design_ref support 2018-01-22 08:28:19 -06:00
tools Migrate to DH-managed config files 2018-01-26 13:43:18 -05:00
.dockerignore Add initial Makefile 2017-10-31 12:46:23 -05:00
.gitignore Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
.gitreview Add gitreview file 2017-08-11 01:18:30 -05:00
Dockerfile Add initial chart for Promenade API 2017-11-15 14:19:43 -06:00
LICENSE Initial commit 2017-02-14 11:13:39 -08:00
Makefile Fix: revert to openstack-helm/helm-toolkit 2017-11-02 10:16:28 -05:00
README.md Docs: Add design doc 2017-11-16 13:50:46 -05:00
entrypoint.sh Test: extend uwsgi timeout to facilitate testing 2017-12-13 11:40:02 -06:00
requirements-direct.txt Migrate to DH-managed config files 2018-01-26 13:43:18 -05:00
requirements-frozen.txt Migrate to DH-managed config files 2018-01-26 13:43:18 -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 Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
tox.ini Add basepython=python3.5 to [testenv] in tox.ini 2018-02-01 05:51:28 +00:00

README.md

Promenade

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

Documentation can be found here.

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.