Sergiy Markin
9c072de770
uWSGI's internal socket-timeout defaults to 4 seconds and was never overridden, unlike --http-timeout which is set to 600s. This caused large configdocs uploads (700+ KB) to fail intermittently under load with "OSError: timeout during read(...) on wsgi.input" before the API worker had read any bytes of the request body. Align socket-timeout with the existing http-timeout default so both timeouts reflect the same tolerance. Change-Id: I2a8bb0938cce4779ecb15f6ff86ba16b027ae7bb Signed-off-by: Sergiy Markin <smarkin@mirantis.com>
Shipyard
Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.
Find more documentation for Shipyard on Read the Docs.
The current workflow is as follows:
- Initial region/site data will be passed to Shipyard from either a human operator or Jenkins
- The data (in YAML format) will be sent to Deckhand for validation and storage
- Shipyard will make use of the post-processed data from DeckHand to interact with Drydock.
- Drydock will interact with Promenade to provision and deploy bare metal nodes using Ubuntu MAAS and a resilient Kubernetes cluster will be created at the end of the process
- Once the Kubernetes clusters are up and validated to be working properly, Shipyard will interact with Armada to deploy OpenStack using OpenStack Helm
- Once the OpenStack cluster is deployed, Shipyard will trigger a workflow to perform basic sanity health checks on the cluster
Note: This project, along with the tools used within are community-based and open sourced.
Mission
The goal for Shipyard is to provide a customizable framework for operators and developers alike. This framework will enable end-users to orchestrate and deploy a fully functional container-based Cloud.
Getting Started
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.
Bugs
If you find a bug, please feel free to create a Storyboard issue.