Difference between revisions of "StarlingX/Devstack/stx-config"
Austin.sun (talk | contribs) (→ToDo) |
Austin.sun (talk | contribs) (→Sysinv Devstack summary) |
||
| Line 2: | Line 2: | ||
<big> | <big> | ||
| − | has run successfully on devstack env ( | + | has run successfully on devstack env (latest tested on VM Ubuntu 16.04 should support CentOS 7.5)<br /> |
sysinv-cond ,sysinv-cond and sysinv-agent services can run successfully<br /> | sysinv-cond ,sysinv-cond and sysinv-agent services can run successfully<br /> | ||
Revision as of 02:42, 28 November 2018
Sysinv Devstack summary
has run successfully on devstack env (latest tested on VM Ubuntu 16.04 should support CentOS 7.5)
sysinv-cond ,sysinv-cond and sysinv-agent services can run successfully
and enable zuul test(non-voting) you can check https://review.openstack.org/#/c/618611/
Limitation or Issue
- devstack are using postgresql for starlingx because it is using in live env. if use mysql, will meet some errors.
- sysinv-api port is same as ironic port 6385
you can define SYSINV_SERVICE_PORT to avoid port conflicting.
- for devstack enabling, we disable tls-proxy,
ToDo
- cgcsclient has depends on smapi, so system command can not be used yet. you can workaround to remove this
depends in cgts-client/cgtsclient/v1/client.py
- test-config setup and tempest test
