If the log_dir is /var/log/kolla, and when we
deploy with devstack, we only chown the permission
for /var/log/kolla/skyline with stack user.
But the permission for /var/log/kolla is still root.
So it can not be access by stack user.
We will both change the log_dir in skyline-console
project.
Change-Id: I852c44cda2f9879aa8d8e405bb39bba13f35b8ca
Fail to build skyline image. We should upgrade the pip and setuptools
version.
Remove irrelevant files for skyline-tox-lint-py38 job to retain one job
to trigger zuul.
Refer: https://github.com/python-poetry/poetry/issues/3329
Change-Id: I444faa3aefaa8ef8cfeb5284bc2a7a49bb0cb91b
Since poetry 1.1.8 version introduces a large number of bugs[1], which
makes the process of building container image fail, so the 1.1.8
version of poetry is not used.
[1] https://github.com/python-poetry/poetry/issues/4429
Change-Id: Ia30c2c5e783401aa4bad85139b0bf2fa9a822847
When docker run, specify the KOLLA_BOOSTRAP environment variable, the
skyline image will initialize the database, and if it is not specified,
the skyline service will be run in the normal way.
This provides the basis for subsequent docking with kolla-ansible.
Change-Id: I5eaad038b3ed3c3189f2b41e41c14d28a346ee88
