just some suggestions inside your mail, ------------------------------------------------------------------ 发件人：von Hoesslin, Volker <Volker.Hoesslin@swsn.de> 发送时间：2019年11月17日(星期日) 04:06 收件人：starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io> 主 题：[Starlingx-discuss] Issues So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :(
Is your installation virtual type? If so, you can redirect the startup message to virsh console, I forget how to, you can ask from google.
2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ?
Before use Horizon, you can try commands using "system" and "openstack", for example, $ source /etc/platform/openrc $ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-18-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | | systemtestapp1 | 1.0-7 | systemtestapp1-manifest | manifest.yaml | remove-failed | operation aborted, check logs for detail | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+
and use openstack, controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor list +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | 0 | m1.nano | 64 | 1 | 0 | 1 | True | | 02c7efd7-747f-42a1-9106-584541717745 | m1.medium | 4096 | 40 | 0 | 2 | True | | 2103aa07-e42a-4b65-a74c-bb0d960889c2 | m1.small | 2048 | 20 | 0 | 1 | True | | 5a99dcae-6a6f-434d-a11f-d7578462eb86 | m1.xlarge | 16384 | 160 | 0 | 8 | True | | 8e3f6810-e872-4aac-8a40-acf44d8077dc | m1.tiny | 512 | 1 | 0 | 1 | True | | f469dbc7-e09d-40c3-97dd-95f4447a7998 | m1.large | 8192 | 80 | 0 | 4 | True | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ Besides, you can check helm, kubernetes use their commands. As for log, it depends your command, for example, the "system" command log is in /var/log/sysinv.log. greez & thx, volker