Jump to: navigation, search

Difference between revisions of "StarlingX/Devstack/stx-config"

(Done)
(Sysinv Devstack summary)
Line 4: Line 4:
 
has run successfully on  devstack env (VM Centos 7.5 and VM Ubuntu 16.04 )<br />
 
has run successfully on  devstack env (VM Centos 7.5 and VM Ubuntu 16.04 )<br />
  
si-api(sysinv-api) and si-cond(sysinv-conductor) sysinv-agent services can run successfully</big><br />
+
sysinv-cond ,sysinv-cond and sysinv-agent services can run successfully<br />
  
and enable zuul test(non-voting) you can check https://review.openstack.org/#/c/618611/
+
and enable zuul test(non-voting) you can check https://review.openstack.org/#/c/618611/</big>
  
 
=== Limitation or Issue ===  
 
=== Limitation or Issue ===  
 
<big>
 
<big>
* some db migrate code need to adapt if Devstack is using mysql(default), String must have length and String length Max is 255. if use postgresql , it is ok.
+
* devstack are using postgresql for starlingx because it is using in live env. if use mysql, will meet some errors.  
  https://review.openstack.org/#/c/588184/ is the draft gerrit id to fix mysql issue.
 
* There are several dependence other starlingx python packages need to install, and these python packages do not have setup.cfg files, only support setuptools install, can not use 'pip install -e'.
 
# [http://git.openstack.org/cgit/openstack/stx-update/tree/tsconfig/tsconfig tsconfig]
 
# [https://git.openstack.org/cgit/openstack/stx-config/tree/configutilities configigutilities]
 
# [https://git.openstack.org/cgit/openstack/stx-config/tree/controllerconfig controllerconfig]
 
# [https://git.openstack.org/cgit/openstack/stx-fault/tree/fm-api fm_api]
 
# [https://git.openstack.org/cgit/openstack/stx-utils/tree/middleware/util/recipes-common/platform-util/platform-util platform-util]*
 
* si-cond service will fail in first time when using mysql ,so need to restart si-cond service in test-config phase, use postgresql is ok.
 
 
* sysinv-api port is same as ironic port 6385
 
* sysinv-api port is same as ironic port 6385
 
   you can define SYSINV_SERVICE_PORT to avoid port conflicting.  
 
   you can define SYSINV_SERVICE_PORT to avoid port conflicting.  
 +
* for devstack enabling, we disable tls-proxy,
 
</big>
 
</big>
  
 
=== ToDo ===
 
=== ToDo ===
 
<big>
 
<big>
* fix "Limitation or Issue" and upload official patch
+
* cgcsclient has depends on smapi, so system command can not be used yet. you can workaround to remove this depends.
 
* test-config setup and tempest test</big>
 
* test-config setup and tempest test</big>
  
 
=== Local.conf ===
 
=== Local.conf ===
<nowiki>[[local|localrc]]</nowiki><br />
 
GIT_BASE=https://git.openstack.org<br />
 
TARGET_BRANCH=stable/pike<br />
 
ADMIN_PASSWORD=secret<br />
 
DATABASE_PASSWORD=$ADMIN_PASSWORD<br />
 
RABBIT_PASSWORD=$ADMIN_PASSWORD<br />
 
SERVICE_PASSWORD=$ADMIN_PASSWORD<br />
 
LOGFILE=/opt/stack/logs/stack.sh.log<br />
 
STX_REPO=$GIT_BASE/openstack/stx-config<br />
 
STX_BRANCH=refs/changes/43/586443/3<br />
 
enable_plugin stx-config $STX_REPO $STX_BRANCH<br />
 
<nowiki>#use postgresql for database backend,</nowiki><br />
 
<nowiki>#if use mysql as backend, please modify local change https://review.openstack.org/#/c/588184/</nowiki><br />
 
disable_service mysql<br />
 
enable_service postgresql<br />
 
<nowiki>#enable it once download code to speed-up</nowiki><br />
 
<nowiki>#OFFLINE=True</nowiki><br />
 

Revision as of 02:24, 28 November 2018

Sysinv Devstack summary

has run successfully on devstack env (VM Centos 7.5 and VM Ubuntu 16.04 )

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.
  • test-config setup and tempest test

Local.conf