August 2019 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] Service Parameter Bug 1818887
by Arce Moreno, Abraham 22 Aug '19

22 Aug '19

Hi, I need your advice how to interpret my findings related to this bug: https://bugs.launchpad.net/starlingx/+bug/1818887 Failed to apply run-time manifest after the http port was modified I will take this review as my initial learning source: https://review.opendev.org/#/c/634237 Configurable Host HTTP/HTTPS Port Binding The test steps are: 1. system service-parameter-modify http config http_port=6666 2. system service-parameter-apply http The expected behavior: After modifying http service-parameter Horizon dashboard should be accessbile on http port 6666 [ Fail ] The first time service-parameter-apply is executed, there is a process error: /var/log/sysinv.log 2019-08-21 21:48:55.208 1727887 INFO sysinv.agent.manager ... _apply_runtime_manifest with hieradata_path = '/opt/platform/puppet/19.01/hieradata' 2019-08-21 21:48:55.209 1727887 WARNING sysinv.puppet.common ... /opt/platform/puppet/19.01/hieradata 192.168.204.3 controller runtime 2019-08-21 21:49:06.543 1727887 ERROR sysinv.puppet.common [req-20042efd-3d18-4231-85a8-fb38bdcb3a56 admin admin] Failed to execute runtime manifest for host 192.168.204.3 2019-08-21 21:49:06.543 1727887 TRACE sysinv.puppet.common Traceback (most recent call last): 2019-08-21 21:49:06.543 1727887 TRACE sysinv.puppet.common CalledProcessError: Command '['/usr/local/bin/puppet-manifest-apply.sh', '/opt/platform/puppet/19.01/hieradata', '192.168.204.3', 'controller', 'runtime', '/tmp/tmpothK1t.yaml']' returned non-zero exit status 1 /var/log/puppet/latest/puppet.log 2019-08-21T21:49:04.805 ... Exec[Adding StarlingX helm repo: stx-platform](provider=posix): Executing 'helm repo add stx-platform http://127.0.0.1:8083/helm_charts/stx-platform' 2019-08-21T21:49:04.810 ... Executing with uid=sysadmin gid=sys_protected: 'helm repo add stx-platform http://127.0.0.1:8083/helm_charts/stx-platform' 2019-08-21T21:49:04.840 ... /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[stx-platform]/Exec[Adding StarlingX helm repo: stx-platform]/returns: Error: Looks like "http://127.0.0.1:8083/helm_charts/stx-platform" is not a valid chart repository or cannot be reached: Failed to fetch http://127.0.0.1:8083/helm_charts/stx-platform/index.yaml : 404 Not Found 2019-08-21T21:49:04.843 Error: 2019-08-21 21:49:04 +0000 helm repo add stx-platform http://127.0.0.1:8083/helm_charts/stx-platform returned 1 instead of one of [0] 2019-08-21T21:49:04.983 ... Platform::Helm::Repository[stx-platform]: Resource is being skipped, unscheduling all events 2019-08-21T21:49:04.985 ... Exec[Adding StarlingX helm repo: starlingx](provider=posix): Executing 'helm repo add starlingx http://127.0.0.1:8083/helm_charts/starlingx' 2019-08-21T21:49:04.987 ... Executing with uid=sysadmin gid=sys_protected: 'helm repo add starlingx http://127.0.0.1:8083/helm_charts/starlingx' 2019-08-21T21:49:04.990 ... /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/Exec[Adding StarlingX helm repo: starlingx]/returns: Error: Looks like "http://127.0.0.1:8083/helm_charts/starlingx" is not a valid chart repository or cannot be reached: Failed to fetch http://127.0.0.1:8083/helm_charts/starlingx/index.yaml : 404 Not Found 2019-08-21T21:49:04.992 Error: 2019-08-21 21:49:04 +0000 helm repo add starlingx http://127.0.0.1:8083/helm_charts/starlingx returned 1 instead of one of [0] [ Success ] A second time service-parameter-apply is executed, we might have no process error, clearing the fault alarm. [ Questions ] Are we missing something under puppet-manifests/src/modules/platform/manifests/helm.pp? A restart of "systemctl restart lighttpd.service" so new port value can be properly configured before trying to access http://127.0.0.1:8083/helm_charts/starlingx/? Thanks for your advice! Best Regards Abraham

1 0

[Starlingx-discuss] [Bug]About GPU passthrough issue.
by Liu, ZhipengS 21 Aug '19

21 Aug '19

Hi all, About bug of unable to create vm with GPU/Crypto passthrough devices https://bugs.launchpad.net/starlingx/+bug/1824831 The question is clear now for GPU passthrough. According to openstack doc, we need to modify nova.conf to add alias info. https://docs.openstack.org/nova/pike/admin/pci-passthrough.html For QAT, we have added some frequently used QAT items by hardcoding, like below alias = {"vendor_id": "8086", "product_id": "0435", "name": "qat-dh895xcc-pf"} alias = {"vendor_id": "8086", "product_id": "0443", "name": "qat-dh895xcc-vf"} alias = {"vendor_id": "8086", "product_id": "37c8", "name": "qat-c62x-pf"} alias = {"vendor_id": "8086", "product_id": "37c9", "name": "qat-c62x-vf"} Can we do it the same for GPU. Add GPU items by hardcoding. As I know, you used [102b:0522] [vendorid:productid] I also saw below GPU product. [1a03:2000] [8086:3e92] BTW, can we create port and attach it to VM, so that no need to add this alias. Perfect solution is to detect gpu info automatically and add to alias list after power on. >From my point, this is new feature requirement Any comment? Thanks！ Zhipeng

1 0

[Starlingx-discuss] [MASTER] Sanity Test - ISO 20190821
by Lemus Contreras, Cristopher J 21 Aug '19

21 Aug '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-August-21 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190821T05…>) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Sanity Test is executed in a Containers – Virtual Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Best Regards, Cristopher Lemus

1 0

[Starlingx-discuss] [docs][meetings] docs team meeting minutes 8/21/2019
by Tullis, Michael L 21 Aug '19

21 Aug '19

For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike

1 0

[Starlingx-discuss] [RC] Sanity Test - ISO 20190821
by Lemus Contreras, Cristopher J 21 Aug '19

21 Aug '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-August-21 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190820T23…>) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Sanity Test is executed in a Containers – Virtual Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Best Regards, Cristopher Lemus

1 0

[Starlingx-discuss] Shanghai Forum Selection Committee
by Jimmy McArthur 21 Aug '19

21 Aug '19

Hello Starling X! The Forum in Shanghai is coming up. We would love 1 volunteer from StarlingX for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. For information on the Summit in Shanghai: https://www.openstack.org/summit/shanghai-2019/ For more information on the Forum, please see:https://wiki.openstack.org/wiki/Forum Please reach out to myself orknelson(a)openstack.org if you're interested. Volunteers should respond on or before September 2, 2019. Cheers, Jimmy

2 2

Re: [Starlingx-discuss] [docs] Changing ansible docker_registries structure
by Sun, Yicheng (Jerry) 21 Aug '19

21 Aug '19

Hi All, The change have been merged into the stx2.0 branch. Please make any needed documentation changes. Thanks, Jerry From: Sun, Yicheng (Jerry) Sent: August-20-19 4:18 PM To: 'starlingx-discuss(a)lists.starlingx.io' <starlingx-discuss(a)lists.starlingx.io> Subject: [docs] Changing ansible docker_registries structure Hi all, The change have been merged into master. Please make any needed documentation changes. Thanks, Jerry From: Sun, Yicheng (Jerry) Sent: August-20-19 11:50 AM To: 'starlingx-discuss(a)lists.starlingx.io' <starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Changing ansible docker_registries structure Hi All, I am making changes that change the accepted format for docker registries from something like docker_registries: k8s.gcr.io: url to something like docker_registries: k8s.gcr.io: url: url This affects anyone with a setup that specifies alternate docker registries as they will need to change their ansible localhost.yml files after this commit. the change is currently under review: https://review.opendev.org/#/c/677005/ please let me know if you have any concerns Thanks, Jerry

1 0

[Starlingx-discuss] How to power off an active controller via VM? (STX R1.0)
by Ezpeer Chen 21 Aug '19

21 Aug '19

Dear all, How to power off an active controller via VM? >From the STX R1.0 testplan: https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions - An active controller can be power off/on via VM. Thanks

4 6

[Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 8/21
by Xie, Cindy 21 Aug '19

21 Aug '19

Agenda & notes for 8/21 meeting: 1. stx.2.0 bug triage & review (Cindy) stx.distro.others: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other 1836638 : Jim found 3 upstream patches may related to the mem leak issues. Testing in progress to verify the findings. Yi has tested one patch, on controller-0 no leak, on controll-1 still have growing. The next action is to build with all 3 patches together and run the testing again. stx.storage: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.storage 1830736: reproduced in SH, debug in progress; 1839181: cannot reproduced, reporter said that it cannot repro in WR's lab either. Status is now "incomplete". 1826886 / 1827063 : Fang Liang is out for vacation and will be back by Friday. 1827080: patch under review. Daniel to review it: https://review.opendev.org/#/c/677196/ 1827119: this is a re-open. 2 issues from the reporter. 1st issue has a patch uploaded for review: https://review.opendev.org/#/c/677424/; Need to double check w/ reporter regarding issue 2 which is not repro from Tingjie. Daniel to review the patch as well. 1831635: new info uploaded by reporter, need Fang Liang to investigate it after he is back. 1836800: Chris Winnicki to try the command and see if this can be reproduced. 1837242: reporter to try it on NVMe system. 2. call for contribution: de-brand "Titanium Cloud" https://storyboard.openstack.org/#!/story/2006387 clarified the scope: scope: no replacement in comments, copyrights, commit messages. limit the scope only visible to the user (people who deploy the StarlingX image). Things like alarm, logs, error messages and console messages needs to be replaced. anybody who want to own this, please assign the task to yourself. 3. package version spec opens (Brent/Bin) Waiting for Ian to provide his review comments on this spec: https://review.opendev.org/#/c/671644/ 4. systemd story (Saul): https://storyboard.openstack.org/#!/story/2006192 StarlingX uses systemd to launch flock services, though there are some services that use sysvinit instead. It is required to standardize the use of systemd and move away from hybrid mode. This is related to multi-OS but the change is going to be in master code. Saul will create several examples in stx-integ to show how to do it. We will use other resources to do the rest and the story will be tracked in our project meeting. this is not going to be 3.0 blocking. 5. Opens (all) Tingjie: spec review for the Ceph containerization. comments and suggestion provided by Brent and Ian. TSC this week shall review and approve the spec. -----Original Message----- From: Xie, Cindy Sent: Tuesday, August 20, 2019 8:47 PM To: Wold, Saul <saul.wold(a)intel.com>; 'starlingx-discuss(a)lists.starlingx.io' <starlingx-discuss(a)lists.starlingx.io>; 'Rowsell, Brent' <Brent.Rowsell(a)windriver.com> Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 8/21 Agenda for 8/21 meeting: 1. stx.2.0 bug triage & review (Cindy) 2. call for contribution: de-brand "Titanium Cloud" 3. package version spec opens (Brent/Bin) 4. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; Wold, Saul; 'starlingx-discuss(a)lists.starlingx.io'; 'Rowsell, Brent'; 'zhaos' Cc: 'Seiler, Glenn'; Hu, Wei W; Peng Tan; Gomez, Juan P; 'Waines, Greg'; 'Eslimi, Dariush'; Jones, Bruce E; 'Zhi Zhi2 Chang'; Chen, Tingjie; 'Badea, Daniel'; 'Chen, Jacky'; 'Komiyama, Takeo'; Armstrong, Robert H; 'Carlos Cebrian'; Cobbley, David A Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, August 21, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other

1 0

Re: [Starlingx-discuss] Issue in running ansible playbook
by Zvonar, Bill 21 Aug '19

21 Aug '19

Hi folks - anyone have some insight for Pavan on this? Thanks, Bill... From: Pavan Gupta <pavan.gupta(a)calsoftinc.com> Sent: Friday, August 16, 2019 5:40 AM To: Zvonar, Bill <Bill.Zvonar(a)windriver.com> Cc: saichandu.behara(a)calsoftinc.com Subject: Issue in running ansible playbook Hi Bill, With Stx2.0, we are looking in to the following issue after running this command: 'ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml'. If you have any pointers, kindly let us know. TASK [persist-config : debug] ******************************************************************************* ok: [localhost] => { "populate_result": { "changed": true, "failed": false, "failed_when_result": false, "msg": "non-zero return code", "rc": 1, "stderr": "No handlers could be found for logger \"controllerconfig.common.rest_api_utils\"\nTraceback (most recent call last):\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1565850999.9-200492702943299/populate_initial_config.py\", line 950, in <module>\n with openstack.OpenStack() as client:\n File \"/usr/lib64/python2.7/site-packages/controllerconfig/openstack.py\", line 62, in __enter__\n raise Exception('Failed to connect')\nException: Failed to connect\n", "stderr_lines": [ "No handlers could be found for logger \"controllerconfig.common.rest_api_utils\"", "Traceback (most recent call last):", " File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1565850999.9-200492702943299/populate_initial_config.py\", line 950, in <module>", " with openstack.OpenStack() as client:", " File \"/usr/lib64/python2.7/site-packages/controllerconfig/openstack.py\", line 62, in __enter__", " raise Exception('Failed to connect')", "Exception: Failed to connect" ], "stdout": "Failed to provision the initial system config.\n", "stdout_lines": [ "Failed to provision the initial system config." ] } }

3 2