1. add skyline-functional-devstack which inherits from devstack
2. add skyline-functional-devstack into check and gate job
3. add playbook to integrate with devstack for zuul
4. change the port from 8080 to 9999 because the 8080 is used for s3api
5. rename functional-py38 as unittest-py38
6. add install extra tools ready for skyline-console's e2e test
Change-Id: I7f4b549bec6573661e62dd2bd9a3355253afd47d
1. Add a quick start, the document explains how to use the container to
quickly deploy the skyline service.
2. Modify the format of the original `Development skyline-apiserver`
section.
Change-Id: I4ff1c179791b782311be4d8c391565bfcaf16bf9
1. Move skyline-apiserver to libs
2. Modify Makefile
3. Rename the skyline-apiserver.yaml.sample file to skyline.yaml.sample
At the top level, we use "skyline" as the namespace, using the idea of
monorepo to manage the project. At the top level, only some common
configuration files (mypy.ini, black.conf, isort.conf, etc.) and
common tools are included.
In the `libs` directory, there are three core libraries,
skyline-console, skyline-apiserver, skyline-nginx, and some dependent
libraries.
There are cross-imports between these libraries,
for example: skyline-nginx requires skyline-apiserver;
Both skyline-nginx and skyline-apiserver require skyline-config.
Therefore, skyline-apiserver should not be placed
at the top level, it is also suitable for management as a library.
Change-Id: Ie2f1f4bdfbc2e985ec4327705eecaae3181f5b50
Under etc dictory, add sample yaml config file
named skyline-apiserver.yaml.sample
Updated the README.md and README-zh_CN.md file
to make quick start more clearly.
Closes-Bug: #1931673
Change-Id: I023cfbeac33543d2989f5017c878cd17160f8c76
