16f23daee9
We are seeing the following error [0] while using Shipyard to run a commit configdocs. The relevant exceptions are [1] and it is a result of incorrect reference to method name. The bug will be triggered when we use ext_marker. This patch set is meant to correct that. [0] shipyard commit configdocs Error: Validations failed Reason: Validation - Error: None Message: Promenade unable to validate configdocs Source: Promenade - Error: None Message: 500 Server Error: Internal Server Error for url: http://promenade-api.ucp.svc.cluster.local:80/api/v1.0/validatedesign Source: Promenade [1] Exceptions messages in Promenade API pod 2018-05-14 14:56:20,147 ERROR - - - promenade.exceptions:default_exception_handler [142] Unhanded Exception being handled: Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/falcon/api.py", line 201, in __call__ process_request(req, resp) File "./promenade/control/middleware.py", line 103, in process_request if ext_marker is not None and self.is_uuid_like(ext_marker): AttributeError: 'ContextMiddleware' object has no attribute 'is_uuid_like' Change-Id: I89713fbb953a46e61093c4dadaa5a752b1a81c6c |
||
---|---|---|
charts | ||
docs/source | ||
etc/promenade | ||
examples | ||
promenade | ||
tests | ||
tools | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
README.md | ||
entrypoint.sh | ||
requirements-direct.txt | ||
requirements-frozen.txt | ||
requirements.txt | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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.