From build.starlingx at gmail.com Fri Jan 1 02:43:40 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 31 Dec 2020 21:43:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1125 - Still Failing! In-Reply-To: <475967636.864.1609382634652.JavaMail.javamailuser@localhost> References: <475967636.864.1609382634652.JavaMail.javamailuser@localhost> Message-ID: <2086605356.876.1609469020562.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1125 Status: Still Failing Timestamp: 20210101T024249Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210101T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210101T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Fri Jan 1 02:43:42 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 31 Dec 2020 21:43:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 409 - Still Failing! In-Reply-To: <1605556115.867.1609382638093.JavaMail.javamailuser@localhost> References: <1605556115.867.1609382638093.JavaMail.javamailuser@localhost> Message-ID: <1801496926.879.1609469022708.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 409 Status: Still Failing Timestamp: 20210101T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Fri Jan 1 02:44:04 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 31 Dec 2020 21:44:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1429 - Failure! Message-ID: <851299944.882.1609469044796.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1429 Status: Failure Timestamp: 20210101T024259Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210101T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210101T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210101T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From Al.Bailey at windriver.com Fri Jan 1 15:54:01 2021 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 1 Jan 2021 15:54:01 +0000 Subject: [Starlingx-discuss] config project zuul check fail again In-Reply-To: References: Message-ID: The issue is that a unit test has a test certificate that has expired. Another review up at the moment is addressing this https://review.opendev.org/c/starlingx/config/+/768242 That review is not merged, does not 'only' update the certificate, and has a depends-on which has not been reviewed. It makes sense to fix the certificate in its own review. I'll upload a new review containing just those 2 files. Al ________________________________ From: Chen, Haochuan Z Sent: Wednesday, December 30, 2020 9:40 PM To: Bailey, Henry Albert (Al) Cc: starlingx-discuss at lists.starlingx.io Subject: config project zuul check fail again Hi AL This patch is failed to merge, blocked for zuul check. https://review.opendev.org/c/starlingx/config/+/761711 This should be config project base code, zuul check fail again. 2020-12-30 17:53:17.385590 | ubuntu-xenial | tests.api.test_certificate.ApiCertificatePostTestSuite.test_install_2xcert_1xkey_ssl_certificate 2020-12-30 17:53:17.385618 | ubuntu-xenial | ------------------------------------------------------------------------------------------------ 2020-12-30 17:53:17.385644 | ubuntu-xenial | 2020-12-30 17:53:17.385670 | ubuntu-xenial | Captured traceback: 2020-12-30 17:53:17.385696 | ubuntu-xenial | ~~~~~~~~~~~~~~~~~~~ 2020-12-30 17:53:17.385722 | ubuntu-xenial | Traceback (most recent call last): 2020-12-30 17:53:17.385757 | ubuntu-xenial | File "/home/zuul/src/opendev.org/starlingx/config/sysinv/sysinv/sysinv/sysinv/tests/api/test_certificate.py", line 395, in test_install_2xcert_1xkey_ssl_certificate 2020-12-30 17:53:17.385787 | ubuntu-xenial | self.assertIn('certificates', resp) 2020-12-30 17:53:17.385813 | ubuntu-xenial | File "/tmp/zuul_sysinvtox/py27/lib/python2.7/site-packages/testtools/testcase.py", line 417, in assertIn 2020-12-30 17:53:17.385841 | ubuntu-xenial | self.assertThat(haystack, Contains(needle), message) 2020-12-30 17:53:17.385867 | ubuntu-xenial | File "/tmp/zuul_sysinvtox/py27/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat 2020-12-30 17:53:17.385893 | ubuntu-xenial | raise mismatch_error 2020-12-30 17:53:17.385918 | ubuntu-xenial | testtools.matchers._impl.MismatchError: 'certificates' not in {u'success': u'', u'error': u'certificate is not valid before 2020-06-25 15:10:01 nor after 2020-12-22 15:10:01'} Could you help to check. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Jan 2 02:43:53 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Jan 2021 21:43:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1126 - Still Failing! In-Reply-To: <1060312700.874.1609469018391.JavaMail.javamailuser@localhost> References: <1060312700.874.1609469018391.JavaMail.javamailuser@localhost> Message-ID: <556787445.893.1609555433821.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1126 Status: Still Failing Timestamp: 20210102T024258Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210102T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210102T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sat Jan 2 02:43:55 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Jan 2021 21:43:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 410 - Still Failing! In-Reply-To: <1953173671.877.1609469021074.JavaMail.javamailuser@localhost> References: <1953173671.877.1609469021074.JavaMail.javamailuser@localhost> Message-ID: <1310578232.896.1609555435805.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 410 Status: Still Failing Timestamp: 20210102T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Jan 2 02:44:14 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Jan 2021 21:44:14 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1431 - Failure! Message-ID: <1581062110.899.1609555454841.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1431 Status: Failure Timestamp: 20210102T024307Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210102T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210102T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210102T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Sun Jan 3 02:44:02 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 2 Jan 2021 21:44:02 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1127 - Still Failing! In-Reply-To: <851791866.891.1609555431807.JavaMail.javamailuser@localhost> References: <851791866.891.1609555431807.JavaMail.javamailuser@localhost> Message-ID: <984923436.907.1609641845501.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1127 Status: Still Failing Timestamp: 20210103T024308Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210103T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210103T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sun Jan 3 02:44:06 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 2 Jan 2021 21:44:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 411 - Still Failing! In-Reply-To: <1255632374.894.1609555434326.JavaMail.javamailuser@localhost> References: <1255632374.894.1609555434326.JavaMail.javamailuser@localhost> Message-ID: <1000659955.910.1609641847417.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 411 Status: Still Failing Timestamp: 20210103T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sun Jan 3 02:44:27 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 2 Jan 2021 21:44:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1433 - Failure! Message-ID: <981330828.913.1609641867688.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1433 Status: Failure Timestamp: 20210103T024315Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210103T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210103T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210103T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Mon Jan 4 00:13:45 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 3 Jan 2021 19:13:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1128 - Still Failing! In-Reply-To: <1861179605.905.1609641840830.JavaMail.javamailuser@localhost> References: <1861179605.905.1609641840830.JavaMail.javamailuser@localhost> Message-ID: <888050049.921.1609719226302.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1128 Status: Still Failing Timestamp: 20210104T001255Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210104T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210104T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Mon Jan 4 00:13:47 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 3 Jan 2021 19:13:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 412 - Still Failing! In-Reply-To: <1408456376.908.1609641846068.JavaMail.javamailuser@localhost> References: <1408456376.908.1609641846068.JavaMail.javamailuser@localhost> Message-ID: <859527206.924.1609719228465.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 412 Status: Still Failing Timestamp: 20210104T000001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon Jan 4 00:14:10 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 3 Jan 2021 19:14:10 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1435 - Failure! Message-ID: <1386065906.927.1609719251020.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1435 Status: Failure Timestamp: 20210104T001303Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210104T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210104T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210104T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From bruce.e.jones at intel.com Mon Jan 4 17:36:35 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Jan 2021 17:36:35 +0000 Subject: [Starlingx-discuss] Starlingx installation and ISO building issues In-Reply-To: References: Message-ID: Hi Sim Lan. I’m back from vacation now. The first thing I can do to help you is to add the StarlingX mailing list to this thread. That will get more eyes on the issues you are seeing. A quick google search for “connect openstack vm to external network” yielded several tutorials, such as this one: https://www.itzgeek.com/how-tos/linux/centos-how-tos/configure-openstack-networking-enable-access-vm-instances.html Is there someone in the community who has a 10th gen NUC and can help debug the issue Sim Lam is facing? And help with the build issues? brucej From: Sin Lam Tan Sent: Sunday, December 27, 2020 1:41 AM To: Hu, Yong ; Jones, Bruce E ; bill.zvonar at windriver.com Subject: Starlingx installation and ISO building issues Dear Yong, Bruce and Bill, Thank you for the first contact for Special Interest Group for StarlingX. I am quite new to Starlingx, and I have started to use Starlingx prebuilt ISO from V4.0. I install the ISO in Virtualbox with 3 network interfaces: NAT network, 2 x internal network. I install Simplex all-in-one VM using https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex.html I successfully installed Starlingx, Kubernetes cluster and Openstack containers. In Starlingx, I created two data networks: physnet0 (flat network) and physnet1 (VLAN). And in Openstack dashboard, I created external flat network in Openstack to using physnet0. My issue is when launch a new VM in the Openstack dashboard, the VM cannot access the Internet. The VM also cannot ping the gateway of the network. Do you have any tutorial how to enable VM in Openstack to access the Internet? I also use the same ISO to do bare metal installation in Intel NUC 10th generation. During installation, I got "Warning: dracut-initqueue timeout" and went into 'dracut' emergency mode. From the Internet search, seems that my network card is not recognized. That is the reason I try to build the ISO myself. Do you have any suggestion? For building the ISO file, I follow the guide closely, https://docs.starlingx.io/developer_resources/build_guide.html ​During the step "bash download_mirror.sh", the container always returns "Permission denied: '/var/lib/rpm/Name'" problem, unless I issue "sudo bash download_mirror.sh". After the script is finished, i still have a lot of missing files, especially the 3 files below are missing: ./output/stx/CentOS/Binary/LiveOS/squashfs.img ./output/stx/CentOS/Binary/images/pxeboot/initrd.img ./output/stx/CentOS/Binary/images/pxeboot/vmlinuz I have tried the steps many times but keep failing, due to Centos 7 links no longer valid. Can you share your container image that can build the ISO successfully? Is there any tutorial how to do this successfully? Sorry for the long email, and hopefully I can hear some suggestions from you guys! Regards, Sin Lam -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Mon Jan 4 20:05:48 2021 From: Saul.Wold at windriver.com (Saul Wold) Date: Mon, 4 Jan 2021 12:05:48 -0800 Subject: [Starlingx-discuss] MultiOS Meeting Reminder Message-ID: Agenda: - meta-starlingx update Welcome to the new bi-weekly StarlingX Mulit-OS team meeting. You are invited to join a meeting. Join the meeting: https://meet.jit.si/starlingx-multios To join by phone instead, tap this: +1.512.647.1431,,2792742287# Looking for a different dial-in number? See meeting dial-in numbers: https://meet.jit.si/static/dialInInfo.html?room=starlingx-multios If also dialing-in through a room phone, join without connecting to audio: https://meet.jit.si/starlingx-multios#config.startSilent=true -- Sau! From Frank.Miller at windriver.com Mon Jan 4 20:15:41 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 4 Jan 2021 20:15:41 +0000 Subject: [Starlingx-discuss] This is a test Message-ID: Please ignore. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Mon Jan 4 22:02:00 2021 From: Tao.Liu at windriver.com (Liu, Tao) Date: Mon, 4 Jan 2021 22:02:00 +0000 Subject: [Starlingx-discuss] How to provision the DOCKER REGISTRIES to edge cloud In-Reply-To: References: Message-ID: Hi Ankush, Yes, you can specify ‘registry.central:9001’ for docker_registries. I.e. docker_registries: k8s.gcr.io: url: registry.central:9001/k8s.gcr.io gcr.io: url: registry.central:9001/gcr.io quay.io: url: registry.central:9001/quay.io docker.io: url: registry.central:9001/docker.io docker.elastic.co: url: registry.central:9001/docker.elastic.co defaults: type: docker username: password: From: Rai, Ankush Sent: Monday, December 21, 2020 4:34 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to provision the DOCKER REGISTRIES to edge cloud Hi, In a distributed cloud environment, how to provision the DOCKER REGISTRIES from central cloud ? Is there any support to provide the required docker registry details in the bootstrap-values.yml like docker_registries: defaults: url: type: docker username: password: ssl_ca_cert: /etc/docker/certs.d//ca.crt Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Jan 4 22:27:20 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 4 Jan 2021 22:27:20 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Tuesday January 5th is the next scheduled day for the biweekly containerization meeting. The agenda is open so if anyone has a topic please add to the etherpad agenda. Etherpad: https://etherpad.openstack.org/p/stx-containerization Zoom: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 ------ Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2157 bytes Desc: not available URL: From bruce.e.jones at intel.com Tue Jan 5 00:34:36 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 5 Jan 2021 00:34:36 +0000 Subject: [Starlingx-discuss] Multi OS Meeting Notes & Initial Centos-8 Alternatives In-Reply-To: <2925f882-9092-9949-e6ff-3ce23675774c@windriver.com> References: <2925f882-9092-9949-e6ff-3ce23675774c@windriver.com> Message-ID: Saul, I think we have several options here: 1) Continue to support the current hybrid CentOS7/8 that we have today 2) Accelerate the Open Embedded effort 3) Support some other RPM-based OS (e.g. SUSE) Based on previous work in this space, I don't think making StarlingX OS independent is realistic, so I don't include it in the list. Both 2) and 3) above are a lot of work. What issues might we have with option 1)? brucej -----Original Message----- From: Saul Wold Sent: Tuesday, December 22, 2020 9:06 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Multi OS Meeting Notes & Initial Centos-8 Alternatives StarlingX Community: As has been announced Long Term Support for CentOS-8 will be going away in December of 2021 (1 year away). CentOS-Stream will be the "replacement", but has some challenges due to the update policy and possible patching of CVEs in packages. Listed below are additional options, please provide feedback so we can start discussing options here and during the next set of calls. I would like to hear if there are ideas I am missing or other proposals. Thanks Sau! MultiOS Team Meeting - 12/22/2020 - meta-starlingx - No update at this point. - Starting the CentOS-8 Alternatives discussion - CentOS-8 is not getting long term support (stops in Dec 2021) - CentOS-7 Short - medium term (CVEs 2024) - Question about support for new hardware? - RHEL Alternatives - Cloudlinux / RockyLinux - CentOS-Stream may not be stable enought - What's the CVE support commitment for older packages - Debian / Ubuntu - Technical challenges with rpm->deb packaging - Ubuntu has known branding / licenses issues - OpenEmbedded / Yocto Project meta-startlingx - Work in progress already using StarlingX-3.0 - SuSE / OpenSuse - RPM based - Make StarlingX platform agnostic - Currently there is a custom kernel and userspace - Need to get rid of custom userspace. - Oracle Linux -- Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Tue Jan 5 01:26:38 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 4 Jan 2021 20:26:38 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1438 - Failure! Message-ID: <1191217460.937.1609809999533.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1438 Status: Failure Timestamp: 20210105T010612Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210105T005211Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210105T005211Z DOCKER_BUILD_ID: jenkins-master-distro-20210105T005211Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210105T005211Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210105T005211Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From austin.sun at intel.com Tue Jan 5 02:22:33 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Jan 2021 02:22:33 +0000 Subject: [Starlingx-discuss] How to enable CPU-manager? In-Reply-To: References: Message-ID: Hi Ankush: I don't think cpu manger could be config in ansible provision stage. Thanks. BR Austin Sun. From: Rai, Ankush Sent: Monday, December 21, 2020 11:35 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to enable CPU-manager? Hi, Is this possible to enable Kubernetes labels on a host during installation itself via localhost.yaml ? I know this can be done via a system command like below, but is there any way to automatically assign this ? system host-label-assign controller-0 kube-cpu-mgr-policy=static Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 5 07:57:44 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Jan 2021 07:57:44 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 01/06 Message-ID: Hi All: Happy New Year. Just reminder we will resume openstack distro meeting from tomorrow . the topic will be : 01/06/2021 Meeting: - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack - Open Topic If any more topic : Adding to https://etherpad.opendev.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 5 08:27:39 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 5 Jan 2021 08:27:39 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Hi Please review patch for rook-ceph. We already confirm it is function ready and pass function test. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 https://review.opendev.org/c/starlingx/utilities/+/760503 https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Tue Jan 5 07:49:19 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 5 Jan 2021 07:49:19 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , Message-ID: Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages....). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn't find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Jan 5 09:02:10 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 5 Jan 2021 09:02:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210105T012617Z Message-ID: Sanity Test from 2021-January-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210105T012617Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210105T012617Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Al.Bailey at windriver.com Tue Jan 5 13:16:59 2021 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 5 Jan 2021 13:16:59 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , Message-ID: Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Kalvala, Haridhar ; Wensley, Barton Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages….). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn’t find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can’t migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein’s openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Tue Jan 5 13:39:42 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 5 Jan 2021 13:39:42 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , Message-ID: Yes Henry. Also #131/#133 And also when we migrate(as python3.6) fmclient, cgtsclient, distributed cloud etc... deployment fails because sysinv can't find the modules in 2.7. Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) Sent: Tuesday, January 5, 2021 6:47 PM To: Kalvala, Haridhar ; starlingx-discuss at lists.starlingx.io; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Kalvala, Haridhar >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages....). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn't find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar > Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Haiqing.Bai at windriver.com Tue Jan 5 13:56:10 2021 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Tue, 5 Jan 2021 13:56:10 +0000 Subject: [Starlingx-discuss] Starlingx installation and ISO building issues In-Reply-To: References: Message-ID: Hi, Sim Lan: For these binaries downloading issues, you can check the log file in the build container: /stx-tools/centos-mirror-tools/logs/otherfiles_centos_download.log In the log file, you can search “squashfs.img”: remote path: http://mirror.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/7.6.1810/os/x86_64/LiveOS/squashfs.img local path: ./output/stx-r1/CentOS/pike/Binary//LiveOS/squashfs.img --2020-10-30 13:58:56-- http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/7.6.1810/os/x86_64/LiveOS/squashfs.img Connecting to 128.224.230.5:9090... connected. Proxy request sent, awaiting response... 200 OK Length: 453365760 (432M) [application/octet-stream] Saving to: ‘squashfs.img’ Make sure your network can access http://mirror.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/7.6.1810/os/x86_64/LiveOS/squashfs.img ok. B,R Haiqing Bai From: Jones, Bruce E Sent: Tuesday, January 5, 2021 1:37 AM To: Sin Lam Tan ; Hu, Yong ; Zvonar, Bill Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Starlingx installation and ISO building issues [Please note this e-mail is from an EXTERNAL e-mail address] Hi Sim Lan. I’m back from vacation now. The first thing I can do to help you is to add the StarlingX mailing list to this thread. That will get more eyes on the issues you are seeing. A quick google search for “connect openstack vm to external network” yielded several tutorials, such as this one: https://www.itzgeek.com/how-tos/linux/centos-how-tos/configure-openstack-networking-enable-access-vm-instances.html Is there someone in the community who has a 10th gen NUC and can help debug the issue Sim Lam is facing? And help with the build issues? brucej From: Sin Lam Tan > Sent: Sunday, December 27, 2020 1:41 AM To: Hu, Yong >; Jones, Bruce E >; bill.zvonar at windriver.com Subject: Starlingx installation and ISO building issues Dear Yong, Bruce and Bill, Thank you for the first contact for Special Interest Group for StarlingX. I am quite new to Starlingx, and I have started to use Starlingx prebuilt ISO from V4.0. I install the ISO in Virtualbox with 3 network interfaces: NAT network, 2 x internal network. I install Simplex all-in-one VM using https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex.html I successfully installed Starlingx, Kubernetes cluster and Openstack containers. In Starlingx, I created two data networks: physnet0 (flat network) and physnet1 (VLAN). And in Openstack dashboard, I created external flat network in Openstack to using physnet0. My issue is when launch a new VM in the Openstack dashboard, the VM cannot access the Internet. The VM also cannot ping the gateway of the network. Do you have any tutorial how to enable VM in Openstack to access the Internet? I also use the same ISO to do bare metal installation in Intel NUC 10th generation. During installation, I got "Warning: dracut-initqueue timeout" and went into 'dracut' emergency mode. From the Internet search, seems that my network card is not recognized. That is the reason I try to build the ISO myself. Do you have any suggestion? For building the ISO file, I follow the guide closely, https://docs.starlingx.io/developer_resources/build_guide.html ​During the step "bash download_mirror.sh", the container always returns "Permission denied: '/var/lib/rpm/Name'" problem, unless I issue "sudo bash download_mirror.sh". After the script is finished, i still have a lot of missing files, especially the 3 files below are missing: ./output/stx/CentOS/Binary/LiveOS/squashfs.img ./output/stx/CentOS/Binary/images/pxeboot/initrd.img ./output/stx/CentOS/Binary/images/pxeboot/vmlinuz I have tried the steps many times but keep failing, due to Centos 7 links no longer valid. Can you share your container image that can build the ISO successfully? Is there any tutorial how to do this successfully? Sorry for the long email, and hopefully I can hear some suggestions from you guys! Regards, Sin Lam -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 5 14:39:11 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Jan 2021 14:39:11 +0000 Subject: [Starlingx-discuss] FW: : patch review for rook-ceph Message-ID: Hi Core Reviewers: Happy New Year. Would you like to review below accordingly ? Those patches have not been reviewed for some time and this is stx.5.0 feature. Thanks. BR Austin Sun. From: Chen, Haochuan Z Sent: Tuesday, January 5, 2021 4:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] patch review for rook-ceph Hi Please review patch for rook-ceph. We already confirm it is function ready and pass function test. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 https://review.opendev.org/c/starlingx/utilities/+/760503 https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Don.Penney at windriver.com Tue Jan 5 15:03:12 2021 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 5 Jan 2021 15:03:12 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , Message-ID: I think Al's original suggestion was to avoid changing the on-host installation of packages. Rather, to ensure that the modules required for the container are building a py3-compatible wheel that can be used for the image. Some of the wheels are already py2.py3 and available for use in a py3 image. The fm-common module, for example, has a compiled library and is py2-specific: /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl So updating the spec to use %py3_build_wheel allows us to build a wheel that should be compatible with a py3 image: $ git diff diff --git a/fm-common/centos/fm-common.spec b/fm-common/centos/fm-common.spec index a5c3618..f8d4ac9 100644 --- a/fm-common/centos/fm-common.spec +++ b/fm-common/centos/fm-common.spec @@ -19,6 +19,8 @@ BuildRequires: python-devel BuildRequires: python-setuptools BuildRequires: python2-pip BuildRequires: python2-wheel +BuildRequires: python3-pip +BuildRequires: python3-wheel Buildrequires: json-c-devel Requires: json-c @@ -55,6 +57,7 @@ MINOR=`echo $VER | awk -F . '{print $2}'` make MAJOR=$MAJOR MINOR=$MINOR %{?_smp_mflags} %{__python} setup.py build %py2_build_wheel +%py3_build_wheel %install rm -rf %{buildroot} With that change, we end up with wheels for both py2 and py3: $ rpm -qpl std/rpmbuild/RPMS/fm-common-wheels-1.0-50.tis.x86_64.rpm /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl /wheels/fm_core-1.0-cp36-cp36m-linux_x86_64.whl Additionally, some modules may need an update to their setup.cfg to add py3 support. For example, cgts-client is currently py2-only: https://opendev.org/starlingx/config/src/branch/master/sysinv/cgts-client/cgts-client/setup.cfg So adding the following would be needed to get the wheel to support both py2 and py3, with a universal wheel: $ git diff diff --git a/sysinv/cgts-client/cgts-client/setup.cfg b/sysinv/cgts-client/cgts-client/setup.cfg index e1ee3e7b..0ca4697f 100644 --- a/sysinv/cgts-client/cgts-client/setup.cfg +++ b/sysinv/cgts-client/cgts-client/setup.cfg @@ -13,6 +13,8 @@ classifier = Programming Language :: Python Programming Language :: Python :: 2 Programming Language :: Python :: 2.7 + Programming Language :: Python :: 3 + Programming Language :: Python :: 3.6 [global] setup-hooks = @@ -33,3 +35,6 @@ autodoc_index_modules = False tag_build = tag_date = 0 tag_svn_revision = 0 + +[wheel] +universal = 1 With this change, I now see the following: $ rpm -qpl std/rpmbuild/RPMS/cgts-client-wheels-1.0-199.tis.x86_64.rpm /wheels/cgtsclient-1.0-py2.py3-none-any.whl A quick check of our wheel RPMs can show us which don't currently support py3. Most of these would be similar to the cgtsclient change, where the setup.cfg would need to be update to build a universal wheel that supports py2 and py3: $ for f in std/rpmbuild/RPMS/*-wheels* ; do rpm -qpl $f | grep -q -e '-py3-' -e '-py2.py3-' -e cp36 || echo $f; done std/rpmbuild/RPMS/ceph-manager-wheels-1.0-20.tis.x86_64.rpm std/rpmbuild/RPMS/cgts-client-wheels-1.0-198.tis.x86_64.rpm std/rpmbuild/RPMS/controllerconfig-wheels-1.0-222.tis.x86_64.rpm std/rpmbuild/RPMS/distributedcloud-client-wheels-1.0.0-1.tis.22.noarch.rpm std/rpmbuild/RPMS/distributedcloud-wheels-1.0.0-1.tis.215.noarch.rpm std/rpmbuild/RPMS/libvirt-python-wheels-4.7.0-1.tis.5.x86_64.rpm std/rpmbuild/RPMS/nfv-wheels-1.0-163.tis.x86_64.rpm std/rpmbuild/RPMS/nova-api-proxy-wheels-1.0-30.tis.x86_64.rpm std/rpmbuild/RPMS/platform-util-wheels-1.0-52.tis.noarch.rpm std/rpmbuild/RPMS/python-3parclient-wheels-4.2.3-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-barbicanclient-wheels-4.9.0-1.tis.3.noarch.rpm std/rpmbuild/RPMS/python-cephclient-wheels-13.2.2.0-10.tis.noarch.rpm std/rpmbuild/RPMS/python-django-horizon-wheels-15.1.0-1.tis.44.noarch.rpm std/rpmbuild/RPMS/python-lefthandclient-wheels-2.1.0-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-ryu-wheels-4.19-0.tis.5.noarch.rpm std/rpmbuild/RPMS/sm-api-wheels-1.0-35.tis.x86_64.rpm std/rpmbuild/RPMS/sm-client-wheels-1.0-24.tis.x86_64.rpm std/rpmbuild/RPMS/sm-tools-wheels-1.0-17.tis.x86_64.rpm std/rpmbuild/RPMS/starlingx-dashboard-wheels-1.0-251.tis.noarch.rpm std/rpmbuild/RPMS/sysinv-wheels-1.0-1857.tis.x86_64.rpm std/rpmbuild/RPMS/vm-topology-wheels-1.0-17.tis.noarch.rpm From: Kalvala, Haridhar Sent: Tuesday, January 5, 2021 8:40 AM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Yes Henry. Also #131/#133 And also when we migrate(as python3.6) fmclient, cgtsclient, distributed cloud etc... deployment fails because sysinv can't find the modules in 2.7. Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, January 5, 2021 6:47 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Kalvala, Haridhar >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages....). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn't find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar > Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Tue Jan 5 15:25:38 2021 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 5 Jan 2021 07:25:38 -0800 Subject: [Starlingx-discuss] Multi OS Meeting Notes & Initial Centos-8 Alternatives In-Reply-To: References: <2925f882-9092-9949-e6ff-3ce23675774c@windriver.com> Message-ID: HI Bruce, We are going to move this to the Distro Meeting tomorrow (Wednesday) before the the community meeting. See some additional thoughts below. On 1/4/21 4:34 PM, Jones, Bruce E wrote: > Saul, I think we have several options here: > > 1) Continue to support the current hybrid CentOS7/8 that we have today I think this will work short term, but we will have to manage any CVEs in the 4.18 kernel outside of what CentOS-7, which we know will be EOL'ed in 2024, so we will need a solution in the next year. > 2) Accelerate the Open Embedded effort This would be a good thing to continue to consider this option, the challenge here is the perception of the OE base OS. > 3) Support some other RPM-based OS (e.g. SUSE) > RHEL/CentOS and Debian/Ubuntu are the major OSes that are used in Data Centers, I think we need to consider some of that kind of information in our considerations. While SUSE/OpenSUSE does have some market share in Europe its much less than the others. > Based on previous work in this space, I don't think making StarlingX OS independent is realistic, so I don't include it in the list. > Yeah, I had included it for completeness > Both 2) and 3) above are a lot of work. > > What issues might we have with option 1)? > I think option 1 is good for the short term, but we need to consider the longer term solution. Sau! > brucej > > -----Original Message----- > From: Saul Wold > Sent: Tuesday, December 22, 2020 9:06 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Multi OS Meeting Notes & Initial Centos-8 Alternatives > > > StarlingX Community: > > As has been announced Long Term Support for CentOS-8 will be going away in December of 2021 (1 year away). CentOS-Stream will be the "replacement", but has some challenges due to the update policy and possible patching of CVEs in packages. > > Listed below are additional options, please provide feedback so we can start discussing options here and during the next set of calls. > > I would like to hear if there are ideas I am missing or other proposals. > > Thanks > Sau! > > > > MultiOS Team Meeting - 12/22/2020 > - meta-starlingx > - No update at this point. > - Starting the CentOS-8 Alternatives discussion > - CentOS-8 is not getting long term support (stops in Dec 2021) > - CentOS-7 Short - medium term (CVEs 2024) > - Question about support for new hardware? > - RHEL Alternatives > - Cloudlinux / RockyLinux > - CentOS-Stream may not be stable enought > - What's the CVE support commitment for older packages > - Debian / Ubuntu > - Technical challenges with rpm->deb packaging > - Ubuntu has known branding / licenses issues > - OpenEmbedded / Yocto Project meta-startlingx > - Work in progress already using StarlingX-3.0 > - SuSE / OpenSuse > - RPM based > - Make StarlingX platform agnostic > - Currently there is a custom kernel and userspace > - Need to get rid of custom userspace. > - Oracle Linux > > -- > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Sau! From Saul.Wold at windriver.com Tue Jan 5 23:45:37 2021 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 5 Jan 2021 15:45:37 -0800 Subject: [Starlingx-discuss] Distro Meeting Adgenda Message-ID: <3a4fe409-ccec-66d9-85d6-197575a02333@windriver.com> Distro Team will meet tomorrow: Python 2 -> 3 Work Ceph CentOS-8 alternatives Sau! Hi All: Update new series Next Meeting will be planned on Dec 23 (last of the year). Cadence and time slot: Bi-Weekly Wednesday 9AM EDT (2200 China time, US PDT time 6AM) Call Details: Zoom link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Dialing in from phone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 Meeting ID: 342 730 236 Passcode: 419405 International numbers available: https://zoom.us/u/ed95sU7aQ Meeting Agenda and Minutes: https://etherpad.openstack.org/p/stx-distro-other From Haiqing.Bai at windriver.com Wed Jan 6 00:01:19 2021 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Wed, 6 Jan 2021 00:01:19 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , Message-ID: Just some input based on the experience of CentOS 8 supporting, hope to help you. For "python-pbr/python3-pbr" , though don't know the detailed migrate issue you have, what I did is just adding 'python3-pbr-.noarch.rpm' into 'flock/rpms_centos.lst', and change all 'BuildRequires: python-pbr' to 'BuildRequires: python3-pbr', 'Requires: python-pbr' to 'Requires: python3-pbr', then at least I can build ok and no dependency issue during deployment. B,R Haiqing Bai From: Kalvala, Haridhar Sent: Tuesday, December 15, 2020 1:58 PM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High [Please note this e-mail is from an EXTERNAL e-mail address] Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: è Starlingx-dashboard : o can't migrate python-pbr to python3-pbr. o Cephclient is throwing errors on trying to migrate to py3. è Fmclient : o Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Wed Jan 6 04:06:02 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Wed, 6 Jan 2021 04:06:02 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , Message-ID: Hi Don Penney, Thank you, I will try only (will revert existing modifications) with these changes for the components. But setup.py doesn't need similar changes (Ex: cgts-client/setup.py) ? Thank you, Haridhar Kalvala From: Penney, Don Sent: Tuesday, January 5, 2021 8:33 PM To: Kalvala, Haridhar ; Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. I think Al's original suggestion was to avoid changing the on-host installation of packages. Rather, to ensure that the modules required for the container are building a py3-compatible wheel that can be used for the image. Some of the wheels are already py2.py3 and available for use in a py3 image. The fm-common module, for example, has a compiled library and is py2-specific: /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl So updating the spec to use %py3_build_wheel allows us to build a wheel that should be compatible with a py3 image: $ git diff diff --git a/fm-common/centos/fm-common.spec b/fm-common/centos/fm-common.spec index a5c3618..f8d4ac9 100644 --- a/fm-common/centos/fm-common.spec +++ b/fm-common/centos/fm-common.spec @@ -19,6 +19,8 @@ BuildRequires: python-devel BuildRequires: python-setuptools BuildRequires: python2-pip BuildRequires: python2-wheel +BuildRequires: python3-pip +BuildRequires: python3-wheel Buildrequires: json-c-devel Requires: json-c @@ -55,6 +57,7 @@ MINOR=`echo $VER | awk -F . '{print $2}'` make MAJOR=$MAJOR MINOR=$MINOR %{?_smp_mflags} %{__python} setup.py build %py2_build_wheel +%py3_build_wheel %install rm -rf %{buildroot} With that change, we end up with wheels for both py2 and py3: $ rpm -qpl std/rpmbuild/RPMS/fm-common-wheels-1.0-50.tis.x86_64.rpm /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl /wheels/fm_core-1.0-cp36-cp36m-linux_x86_64.whl Additionally, some modules may need an update to their setup.cfg to add py3 support. For example, cgts-client is currently py2-only: https://opendev.org/starlingx/config/src/branch/master/sysinv/cgts-client/cgts-client/setup.cfg So adding the following would be needed to get the wheel to support both py2 and py3, with a universal wheel: $ git diff diff --git a/sysinv/cgts-client/cgts-client/setup.cfg b/sysinv/cgts-client/cgts-client/setup.cfg index e1ee3e7b..0ca4697f 100644 --- a/sysinv/cgts-client/cgts-client/setup.cfg +++ b/sysinv/cgts-client/cgts-client/setup.cfg @@ -13,6 +13,8 @@ classifier = Programming Language :: Python Programming Language :: Python :: 2 Programming Language :: Python :: 2.7 + Programming Language :: Python :: 3 + Programming Language :: Python :: 3.6 [global] setup-hooks = @@ -33,3 +35,6 @@ autodoc_index_modules = False tag_build = tag_date = 0 tag_svn_revision = 0 + +[wheel] +universal = 1 With this change, I now see the following: $ rpm -qpl std/rpmbuild/RPMS/cgts-client-wheels-1.0-199.tis.x86_64.rpm /wheels/cgtsclient-1.0-py2.py3-none-any.whl A quick check of our wheel RPMs can show us which don't currently support py3. Most of these would be similar to the cgtsclient change, where the setup.cfg would need to be update to build a universal wheel that supports py2 and py3: $ for f in std/rpmbuild/RPMS/*-wheels* ; do rpm -qpl $f | grep -q -e '-py3-' -e '-py2.py3-' -e cp36 || echo $f; done std/rpmbuild/RPMS/ceph-manager-wheels-1.0-20.tis.x86_64.rpm std/rpmbuild/RPMS/cgts-client-wheels-1.0-198.tis.x86_64.rpm std/rpmbuild/RPMS/controllerconfig-wheels-1.0-222.tis.x86_64.rpm std/rpmbuild/RPMS/distributedcloud-client-wheels-1.0.0-1.tis.22.noarch.rpm std/rpmbuild/RPMS/distributedcloud-wheels-1.0.0-1.tis.215.noarch.rpm std/rpmbuild/RPMS/libvirt-python-wheels-4.7.0-1.tis.5.x86_64.rpm std/rpmbuild/RPMS/nfv-wheels-1.0-163.tis.x86_64.rpm std/rpmbuild/RPMS/nova-api-proxy-wheels-1.0-30.tis.x86_64.rpm std/rpmbuild/RPMS/platform-util-wheels-1.0-52.tis.noarch.rpm std/rpmbuild/RPMS/python-3parclient-wheels-4.2.3-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-barbicanclient-wheels-4.9.0-1.tis.3.noarch.rpm std/rpmbuild/RPMS/python-cephclient-wheels-13.2.2.0-10.tis.noarch.rpm std/rpmbuild/RPMS/python-django-horizon-wheels-15.1.0-1.tis.44.noarch.rpm std/rpmbuild/RPMS/python-lefthandclient-wheels-2.1.0-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-ryu-wheels-4.19-0.tis.5.noarch.rpm std/rpmbuild/RPMS/sm-api-wheels-1.0-35.tis.x86_64.rpm std/rpmbuild/RPMS/sm-client-wheels-1.0-24.tis.x86_64.rpm std/rpmbuild/RPMS/sm-tools-wheels-1.0-17.tis.x86_64.rpm std/rpmbuild/RPMS/starlingx-dashboard-wheels-1.0-251.tis.noarch.rpm std/rpmbuild/RPMS/sysinv-wheels-1.0-1857.tis.x86_64.rpm std/rpmbuild/RPMS/vm-topology-wheels-1.0-17.tis.noarch.rpm From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 8:40 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Yes Henry. Also #131/#133 And also when we migrate(as python3.6) fmclient, cgtsclient, distributed cloud etc... deployment fails because sysinv can't find the modules in 2.7. Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, January 5, 2021 6:47 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Kalvala, Haridhar >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages....). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn't find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar > Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Jan 6 07:06:31 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 6 Jan 2021 07:06:31 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 01/05 Message-ID: MoM 01/05/2021 Meeting: - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1907290 under discussion solution https://bugs.launchpad.net/starlingx/+bug/1879018 no update , will check w/ developer https://bugs.launchpad.net/starlingx/+bug/1887677 B&R test is ongoing https://bugs.launchpad.net/starlingx/+bug/1904635 https://bugs.launchpad.net/starlingx/+bug/1904729 zhipeng uploaded patches, under test https://review.opendev.org/c/starlingx/openstack-armada-app/+/768388 Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Jan 6 08:18:08 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 6 Jan 2021 08:18:08 +0000 Subject: [Starlingx-discuss] rook patch review for project rook-ceph Message-ID: Hi Please review patch for rook-ceph Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:10 PM To: Bailey, Henry Albert (Al) ; Penney, Don ; Scott Little ; Waines, Greg ; Poncea, Ovidiu ; Church, Robert Cc: starlingx-discuss at lists.starlingx.io Subject: rook patch review for project rook-ceph Hi Please review my patch for rook-ceph project https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From outbackdingo at gmail.com Wed Jan 6 08:44:28 2021 From: outbackdingo at gmail.com (Outback Dingo) Date: Wed, 6 Jan 2021 15:44:28 +0700 Subject: [Starlingx-discuss] Intel ethernet IPV6 issues Message-ID: having issues with intel 2.5Gbe ethernet when IPV6 states controller not ready and it passes 0 traffic, after installing openstack, with plain K8s it runs fine. any clues? From Bill.Zvonar at windriver.com Wed Jan 6 11:44:59 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 6 Jan 2021 11:44:59 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 6, 2021) Message-ID: Hi all, welcome back - we'll re-start the weekly TSC/Community calls later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210106T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From alexandru.dimofte at intel.com Wed Jan 6 13:48:40 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 6 Jan 2021 13:48:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210106T023246Z Message-ID: Sanity Test from 2021-January-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210106T023246Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210106T023246Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Al.Bailey at windriver.com Wed Jan 6 15:00:39 2021 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 6 Jan 2021 15:00:39 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , , Message-ID: Those extra classifier entries in setup.py are redundant and can just be removed. setup.cfg provides them already. sysinv also would want this type of cleanup Also note, python 3.5 entries should probably also be cleaned up. Normally python 3.6 is where python3 compatability would start. I see tsconfig is listing only py3.5 Al ________________________________ From: Kalvala, Haridhar Sent: Tuesday, January 5, 2021 11:06 PM To: Penney, Don ; Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hi Don Penney, Thank you, I will try only (will revert existing modifications) with these changes for the components. But setup.py doesn’t need similar changes (Ex: cgts-client/setup.py) ? Thank you, Haridhar Kalvala From: Penney, Don Sent: Tuesday, January 5, 2021 8:33 PM To: Kalvala, Haridhar ; Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. I think Al’s original suggestion was to avoid changing the on-host installation of packages. Rather, to ensure that the modules required for the container are building a py3-compatible wheel that can be used for the image. Some of the wheels are already py2.py3 and available for use in a py3 image. The fm-common module, for example, has a compiled library and is py2-specific: /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl So updating the spec to use %py3_build_wheel allows us to build a wheel that should be compatible with a py3 image: $ git diff diff --git a/fm-common/centos/fm-common.spec b/fm-common/centos/fm-common.spec index a5c3618..f8d4ac9 100644 --- a/fm-common/centos/fm-common.spec +++ b/fm-common/centos/fm-common.spec @@ -19,6 +19,8 @@ BuildRequires: python-devel BuildRequires: python-setuptools BuildRequires: python2-pip BuildRequires: python2-wheel +BuildRequires: python3-pip +BuildRequires: python3-wheel Buildrequires: json-c-devel Requires: json-c @@ -55,6 +57,7 @@ MINOR=`echo $VER | awk -F . '{print $2}'` make MAJOR=$MAJOR MINOR=$MINOR %{?_smp_mflags} %{__python} setup.py build %py2_build_wheel +%py3_build_wheel %install rm -rf %{buildroot} With that change, we end up with wheels for both py2 and py3: $ rpm -qpl std/rpmbuild/RPMS/fm-common-wheels-1.0-50.tis.x86_64.rpm /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl /wheels/fm_core-1.0-cp36-cp36m-linux_x86_64.whl Additionally, some modules may need an update to their setup.cfg to add py3 support. For example, cgts-client is currently py2-only: https://opendev.org/starlingx/config/src/branch/master/sysinv/cgts-client/cgts-client/setup.cfg So adding the following would be needed to get the wheel to support both py2 and py3, with a universal wheel: $ git diff diff --git a/sysinv/cgts-client/cgts-client/setup.cfg b/sysinv/cgts-client/cgts-client/setup.cfg index e1ee3e7b..0ca4697f 100644 --- a/sysinv/cgts-client/cgts-client/setup.cfg +++ b/sysinv/cgts-client/cgts-client/setup.cfg @@ -13,6 +13,8 @@ classifier = Programming Language :: Python Programming Language :: Python :: 2 Programming Language :: Python :: 2.7 + Programming Language :: Python :: 3 + Programming Language :: Python :: 3.6 [global] setup-hooks = @@ -33,3 +35,6 @@ autodoc_index_modules = False tag_build = tag_date = 0 tag_svn_revision = 0 + +[wheel] +universal = 1 With this change, I now see the following: $ rpm -qpl std/rpmbuild/RPMS/cgts-client-wheels-1.0-199.tis.x86_64.rpm /wheels/cgtsclient-1.0-py2.py3-none-any.whl A quick check of our wheel RPMs can show us which don’t currently support py3. Most of these would be similar to the cgtsclient change, where the setup.cfg would need to be update to build a universal wheel that supports py2 and py3: $ for f in std/rpmbuild/RPMS/*-wheels* ; do rpm -qpl $f | grep -q -e '-py3-' -e '-py2.py3-' -e cp36 || echo $f; done std/rpmbuild/RPMS/ceph-manager-wheels-1.0-20.tis.x86_64.rpm std/rpmbuild/RPMS/cgts-client-wheels-1.0-198.tis.x86_64.rpm std/rpmbuild/RPMS/controllerconfig-wheels-1.0-222.tis.x86_64.rpm std/rpmbuild/RPMS/distributedcloud-client-wheels-1.0.0-1.tis.22.noarch.rpm std/rpmbuild/RPMS/distributedcloud-wheels-1.0.0-1.tis.215.noarch.rpm std/rpmbuild/RPMS/libvirt-python-wheels-4.7.0-1.tis.5.x86_64.rpm std/rpmbuild/RPMS/nfv-wheels-1.0-163.tis.x86_64.rpm std/rpmbuild/RPMS/nova-api-proxy-wheels-1.0-30.tis.x86_64.rpm std/rpmbuild/RPMS/platform-util-wheels-1.0-52.tis.noarch.rpm std/rpmbuild/RPMS/python-3parclient-wheels-4.2.3-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-barbicanclient-wheels-4.9.0-1.tis.3.noarch.rpm std/rpmbuild/RPMS/python-cephclient-wheels-13.2.2.0-10.tis.noarch.rpm std/rpmbuild/RPMS/python-django-horizon-wheels-15.1.0-1.tis.44.noarch.rpm std/rpmbuild/RPMS/python-lefthandclient-wheels-2.1.0-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-ryu-wheels-4.19-0.tis.5.noarch.rpm std/rpmbuild/RPMS/sm-api-wheels-1.0-35.tis.x86_64.rpm std/rpmbuild/RPMS/sm-client-wheels-1.0-24.tis.x86_64.rpm std/rpmbuild/RPMS/sm-tools-wheels-1.0-17.tis.x86_64.rpm std/rpmbuild/RPMS/starlingx-dashboard-wheels-1.0-251.tis.noarch.rpm std/rpmbuild/RPMS/sysinv-wheels-1.0-1857.tis.x86_64.rpm std/rpmbuild/RPMS/vm-topology-wheels-1.0-17.tis.noarch.rpm From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 8:40 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Yes Henry. Also #131/#133 And also when we migrate(as python3.6) fmclient, cgtsclient, distributed cloud etc… deployment fails because sysinv can’t find the modules in 2.7. Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, January 5, 2021 6:47 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Kalvala, Haridhar >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages….). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn’t find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar > Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can’t migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein’s openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 6 15:49:36 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 6 Jan 2021 15:49:36 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 6, 2021) In-Reply-To: References: Message-ID: >From today's call: * Standing Topics * Sanity * red, and it's been red since Dec 14 * Martin is working on a fix now for https://bugs.launchpad.net/starlingx/+bug/1908117 * Gerrit Reviews in Need of Attention * ROOK Ceph https://review.opendev.org/q/topic:%22ceph+containerization%22+status:open * Topics for this Week * https://review.opendev.org/c/starlingx/kernel/+/767663 * if RHEL DUP provides new driver, if customer met issue, shall stx support it? * https://bugs.launchpad.net/starlingx/+bug/1908652 * AR: Saul will look into this - if there is no open source alternative, possibly we just don't support this h/w * python3 status/update? * FM containerization feature running into issues with dependency on services being converted to python3 * may be able to work around it by removing some services from the container, tbd * ARs from Previous Meetings * Bill still has the one about the Docker Hub pro account, will follow up next week when Scott's back * Open Requests for Help * KickStart Application * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010419.html * no comments * Issue when resize2fs on /dev/drbd[x] * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010461.html * no comments * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 6, 2021 6:45 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Jan 6, 2021) Hi all, welcome back - we'll re-start the weekly TSC/Community calls later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210106T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From ildiko.vancsa at gmail.com Wed Jan 6 16:37:20 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 6 Jan 2021 17:37:20 +0100 Subject: [Starlingx-discuss] StarlingX ML question Message-ID: <23C9BD97-4105-4299-BAEC-87CBEFC679B1@gmail.com> Hi, There was a question about potentially missing emails on the starlingx-discuss ML recently. I asked around and it turns out that we had a mailman outage. While this happened the mail server still received the emails so once the queue runner for the ML was started again all the emails were sent out. This means that no emails should be missing, they just appeared later on the ML than when they were originally sent. If there are any emails that seem completely missing please reach out to the Opendev community to raise the issue. Please let me know if there are any further questions regarding this. Thanks, Ildikó From bruce.e.jones at intel.com Wed Jan 6 17:01:53 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 6 Jan 2021 17:01:53 +0000 Subject: [Starlingx-discuss] TSC minutes Jan 6 2021 Message-ID: Standing topics - No active reviews in specs or governance CentOS Strategy update Saul led a discussion of the various options we have. No conclusion was reached. More work & investigation is needed. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Jan 6 17:04:24 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 6 Jan 2021 18:04:24 +0100 Subject: [Starlingx-discuss] StarlingX segment in the OpenInfra Foundation Annual Report Message-ID: <1215DD71-148B-4B0B-A2AE-281D3E9DB23A@gmail.com> Hi, I’m reaching out to you about the OpenInfra Foundation Annual Report for 2020. As every year the Foundation is putting out a report to summarize the activities and achievements during the previous work. Since the project’s launch there is a segment that covers these topics for StarlingX as well. A few of us put together a short summary of the 2020 news and activities: https://etherpad.opendev.org/p/2020_StarlingX_Annual_Update Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. Thanks, Ildikó From fungi at yuggoth.org Wed Jan 6 17:35:00 2021 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 6 Jan 2021 17:35:00 +0000 Subject: [Starlingx-discuss] StarlingX ML question In-Reply-To: <23C9BD97-4105-4299-BAEC-87CBEFC679B1@gmail.com> References: <23C9BD97-4105-4299-BAEC-87CBEFC679B1@gmail.com> Message-ID: <20210106173500.k7cu24ewph73ebwp@yuggoth.org> On 2021-01-06 17:37:20 +0100 (+0100), Ildiko Vancsa wrote: > There was a question about potentially missing emails on the > starlingx-discuss ML recently. > > I asked around and it turns out that we had a mailman outage. > While this happened the mail server still received the emails so > once the queue runner for the ML was started again all the emails > were sent out. This means that no emails should be missing, they > just appeared later on the ML than when they were originally sent. > > If there are any emails that seem completely missing please reach > out to the Opendev community to raise the issue. > > Please let me know if there are any further questions regarding > this. To get into more specifics, live migrations in the provider donating resources to the OpenDev Collaboratory, on which the mailing lists are run, caused that server instance to hang at around 04:00 UTC on 2020-12-21 and required a reboot to bring it back into service. When it booted, the queue runners for all the mailing list sites started successfully except the one for lists.starlingx.io, which went unnoticed until Saul brought it to our attention in IRC at 20:30 UTC on Monday (2021-01-04). Clark quickly identified the problem and brought that queue runner daemon online within five minutes, at which point all backlogged posts from that two week period were delivered to list subscribers and recorded in the list archives. I counted something like 57 messages for starlingx-discuss (most of which were automated testing results) received in the minutes after service was restored. The backlog won't be apparent when looking at the list archives however, as the messages are recorded there with the original dates and times they were queued, rather than when they were ultimately delivered. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From outbackdingo at gmail.com Thu Jan 7 04:30:49 2021 From: outbackdingo at gmail.com (Outback Dingo) Date: Thu, 7 Jan 2021 11:30:49 +0700 Subject: [Starlingx-discuss] Download images and push to local registry failures Message-ID: TASK [common/push-docker-images : Download images and push to local registry] ********************************************************************************* fatal: [localhost]: FAILED! => {"changed": true, "msg": "non-zero return code", "rc": 1, "stderr": "Traceback (most recent call last):\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1609990355.96-174918334532347/download_images.py\", line 144, in \n raise Exception(\"Failed to download images %s\" % failed_downloads)\nException: Failed to download images ['k8s.gcr.io/etcd:3.4.3-0', 'docker.io/nfvpe/multus:v3.4', 'docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2', 'quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic', 'docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0']\n", "stderr_lines": ["Traceback (most recent call last):", " File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1609990355.96-174918334532347/download_images.py\", line 144, in ", " raise Exception(\"Failed to download images %s\" % failed_downloads)", "Exception: Failed to download images ['k8s.gcr.io/etcd:3.4.3-0', 'docker.io/nfvpe/multus:v3.4', 'docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2', 'quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic', 'docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0']"], "stdout": "Image is up to date for sha256:a595af0107f98768274e9143be61c7c80a8df2505ced520c9160f4e16ed42cd1\nImage is up to date for sha256:d1ccdd18e6ed8d91e3754e90c4b6cee42750ba165c75d3c78b4a31f057dd0423\nImage is up to date for sha256:6c9320041a7b5d00da54dda3a6bf9d6983b432ca5245a8254c83fc694d023810\nImage is up to date for sha256:4e68534e24f67f912c02ef114131e0ffcd060af0365988800ce0e24af323b165\nImage is up to date for sha256:80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c\nImage is up to date for sha256:67da37a9a360e600e74464da48437257b00a754c77c40f60c65e4cb327c34bd5\nImage is up to date for sha256:cb6799752c46cb16c0c5bebcb355e988a1cd1b3745ce8b67e004abe9a81340a8\nImage is up to date for sha256:fc05bc4225f39e81dcbd0035457977276ed8a6054e6bde6406e39b672e9724f5\nImage is up to date for sha256:53aa421faf0acd88f8a4cb113e9db2cc65b2a2954640ed96a56c4b94233674d8\nImage is up to date for sha256:98793d0a88c823c4fc0fb1b3833d12932be270fc4b6d62bc181f0f54413fe12d\nImage download succeeded: k8s.gcr.io/kube-apiserver:v1.18.1\nImage push succeeded: registry.local:9001/k8s.gcr.io/kube-apiserver:v1.18.1\nImage k8s.gcr.io/kube-apiserver:v1.18.1 download succeeded by containerd\nImage download succeeded: k8s.gcr.io/kube-controller-manager:v1.18.1\nImage push succeeded: registry.local:9001/k8s.gcr.io/kube-controller-manager:v1.18.1\nImage k8s.gcr.io/kube-controller-manager:v1.18.1 download succeeded by containerd\n Image download failed: k8s.gcr.io/kube-scheduler:v1.18.1500 Server Error: Internal Server Error (\"Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image k8s.gcr.io/kube-scheduler:v1.18.1 ...\nImage download succeeded: k8s.gcr.io/kube-scheduler:v1.18.1\nImage push succeeded: registry.local:9001/k8s.gcr.io/kube-scheduler:v1.18.1\nImage k8s.gcr.io/kube-scheduler:v1.18.1 download succeeded by containerd\nImage download succeeded: k8s.gcr.io/kube-proxy:v1.18.1\nImage push succeeded: registry.local:9001/k8s.gcr.io/kube-proxy:v1.18.1\nImage k8s.gcr.io/kube-proxy:v1.18.1 download succeeded by containerd\nImage download succeeded: k8s.gcr.io/pause:3.2\nImage push succeeded: registry.local:9001/k8s.gcr.io/pause:3.2\nImage k8s.gcr.io/pause:3.2 download succeeded by containerd\nImage download succeeded: k8s.gcr.io/etcd:3.4.3-0\n Image download failed: k8s.gcr.io/etcd:3.4.3-0404 Client Error: Not Found (\"No such image: k8s.gcr.io/etcd:3.4.3-0\")\nImage download succeeded: k8s.gcr.io/coredns:1.6.7\nImage push succeeded: registry.local:9001/k8s.gcr.io/coredns:1.6.7\nImage k8s.gcr.io/coredns:1.6.7 download succeeded by containerd\nImage download succeeded: quay.io/calico/cni:v3.12.0\nImage push succeeded: registry.local:9001/quay.io/calico/cni:v3.12.0\nImage quay.io/calico/cni:v3.12.0 download succeeded by containerd\nImage download succeeded: quay.io/calico/node:v3.12.0\nImage push succeeded: registry.local:9001/quay.io/calico/node:v3.12.0\nImage quay.io/calico/node:v3.12.0 download succeeded by containerd\n Image download failed: quay.io/calico/kube-controllers:v3.12.0500 Server Error: Internal Server Error (\"Get https://quay.io/v2/calico/kube-controllers/manifests/v3.12.0: Get https://quay.io/v2/auth?scope=repository%3Acalico%2Fkube-controllers%3Apull&service=quay.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image quay.io/calico/kube-controllers:v3.12.0 ...\nImage download succeeded: quay.io/calico/kube-controllers:v3.12.0\nImage push succeeded: registry.local:9001/quay.io/calico/kube-controllers:v3.12.0\nImage quay.io/calico/kube-controllers:v3.12.0 download succeeded by containerd\n Image download failed: quay.io/calico/pod2daemon-flexvol:v3.12.0500 Server Error: Internal Server Error (\"Get https://quay.io/v2/calico/pod2daemon-flexvol/manifests/v3.12.0: dial tcp 34.192.15.65:443: i/o timeout\")\nSleep 20s before retry downloading image quay.io/calico/pod2daemon-flexvol:v3.12.0 ...\nImage download succeeded: quay.io/calico/pod2daemon-flexvol:v3.12.0\nImage push succeeded: registry.local:9001/quay.io/calico/pod2daemon-flexvol:v3.12.0\nImage quay.io/calico/pod2daemon-flexvol:v3.12.0 download succeeded by containerd\n Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...\n Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...\n Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Image is up to date for sha256:a2bef2b25274b1acbdfde5e2f3de432475e15d4036b2108cea2dce968b0c29ea\nImage is up to date for sha256:1f92aa902d739d544e621fe2ceaee04a4fc5b67c3e3ed8cf0b19aa2620763d3a\nImage is up to date for sha256:7fb3c2364b87e9241db7549bf11d42c129130f44e930d1ce36523fc693186e89\nImage is up to date for sha256:d4553944fbf7b50f20eece0ec3f638202fdbe2a1a597af8c3f3823201cc695b3\nClient.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...\nImage download succeeded: docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2\n Image download failed: docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2404 Client Error: Not Found (\"No such image: starlingx/k8s-cni-sriov:stx.3.0-v2.2\")\n Image download failed: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae500 Server Error: Internal Server Error (\"error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: \"

408 Request Time-out

\\nYour browser didn't send a complete request in time.\\n\\n\\n\"\")\nSleep 20s before retry downloading image docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae ...\n Image download failed: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae ...\nImage download succeeded: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae\nImage push succeeded: registry.local:9001/docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae\nImage docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae download succeeded by containerd\nImage download succeeded: gcr.io/kubernetes-helm/tiller:v2.16.1\nImage push succeeded: registry.local:9001/gcr.io/kubernetes-helm/tiller:v2.16.1\nImage gcr.io/kubernetes-helm/tiller:v2.16.1 download succeeded by containerd\nImage download succeeded: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic\n Image download failed: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic404 Client Error: Not Found (\"No such image: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic\")\n Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0 ...\n Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")\nSleep 20s before retry downloading image docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0 ...\nImage download succeeded: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0\n Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0404 Client Error: Not Found (\"No such image: starlingx/n3000-opae:stx.4.0-v1.0.0\")\nImage download succeeded: quay.io/stackanetes/kubernetes-entrypoint:v0.3.1\nImage push succeeded: registry.local:9001/quay.io/stackanetes/kubernetes-entrypoint:v0.3.1\nImage quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 download succeeded by containerd\nImage download succeeded: quay.io/k8scsi/snapshot-controller:v2.0.0-rc2\nImage push succeeded: registry.local:9001/quay.io/k8scsi/snapshot-controller:v2.0.0-rc2\nImage quay.io/k8scsi/snapshot-controller:v2.0.0-rc2 download succeeded by containerd\n", "stdout_lines": ["Image is up to date for sha256:a595af0107f98768274e9143be61c7c80a8df2505ced520c9160f4e16ed42cd1", "Image is up to date for sha256:d1ccdd18e6ed8d91e3754e90c4b6cee42750ba165c75d3c78b4a31f057dd0423", "Image is up to date for sha256:6c9320041a7b5d00da54dda3a6bf9d6983b432ca5245a8254c83fc694d023810", "Image is up to date for sha256:4e68534e24f67f912c02ef114131e0ffcd060af0365988800ce0e24af323b165", "Image is up to date for sha256:80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c", "Image is up to date for sha256:67da37a9a360e600e74464da48437257b00a754c77c40f60c65e4cb327c34bd5", "Image is up to date for sha256:cb6799752c46cb16c0c5bebcb355e988a1cd1b3745ce8b67e004abe9a81340a8", "Image is up to date for sha256:fc05bc4225f39e81dcbd0035457977276ed8a6054e6bde6406e39b672e9724f5", "Image is up to date for sha256:53aa421faf0acd88f8a4cb113e9db2cc65b2a2954640ed96a56c4b94233674d8", "Image is up to date for sha256:98793d0a88c823c4fc0fb1b3833d12932be270fc4b6d62bc181f0f54413fe12d", "Image download succeeded: k8s.gcr.io/kube-apiserver:v1.18.1", "Image push succeeded: registry.local:9001/k8s.gcr.io/kube-apiserver:v1.18.1", "Image k8s.gcr.io/kube-apiserver:v1.18.1 download succeeded by containerd", "Image download succeeded: k8s.gcr.io/kube-controller-manager:v1.18.1", "Image push succeeded: registry.local:9001/k8s.gcr.io/kube-controller-manager:v1.18.1", "Image k8s.gcr.io/kube-controller-manager:v1.18.1 download succeeded by containerd", " Image download failed: k8s.gcr.io/kube-scheduler:v1.18.1500 Server Error: Internal Server Error (\"Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image k8s.gcr.io/kube-scheduler:v1.18.1 ...", "Image download succeeded: k8s.gcr.io/kube-scheduler:v1.18.1", "Image push succeeded: registry.local:9001/k8s.gcr.io/kube-scheduler:v1.18.1", "Image k8s.gcr.io/kube-scheduler:v1.18.1 download succeeded by containerd", "Image download succeeded: k8s.gcr.io/kube-proxy:v1.18.1", "Image push succeeded: registry.local:9001/k8s.gcr.io/kube-proxy:v1.18.1", "Image k8s.gcr.io/kube-proxy:v1.18.1 download succeeded by containerd", "Image download succeeded: k8s.gcr.io/pause:3.2", "Image push succeeded: registry.local:9001/k8s.gcr.io/pause:3.2", "Image k8s.gcr.io/pause:3.2 download succeeded by containerd", "Image download succeeded: k8s.gcr.io/etcd:3.4.3-0", " Image download failed: k8s.gcr.io/etcd:3.4.3-0404 Client Error: Not Found (\"No such image: k8s.gcr.io/etcd:3.4.3-0\")", "Image download succeeded: k8s.gcr.io/coredns:1.6.7", "Image push succeeded: registry.local:9001/k8s.gcr.io/coredns:1.6.7", "Image k8s.gcr.io/coredns:1.6.7 download succeeded by containerd", "Image download succeeded: quay.io/calico/cni:v3.12.0", "Image push succeeded: registry.local:9001/quay.io/calico/cni:v3.12.0", "Image quay.io/calico/cni:v3.12.0 download succeeded by containerd", "Image download succeeded: quay.io/calico/node:v3.12.0", "Image push succeeded: registry.local:9001/quay.io/calico/node:v3.12.0", "Image quay.io/calico/node:v3.12.0 download succeeded by containerd", " Image download failed: quay.io/calico/kube-controllers:v3.12.0500 Server Error: Internal Server Error (\"Get https://quay.io/v2/calico/kube-controllers/manifests/v3.12.0: Get https://quay.io/v2/auth?scope=repository%3Acalico%2Fkube-controllers%3Apull&service=quay.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image quay.io/calico/kube-controllers:v3.12.0 ...", "Image download succeeded: quay.io/calico/kube-controllers:v3.12.0", "Image push succeeded: registry.local:9001/quay.io/calico/kube-controllers:v3.12.0", "Image quay.io/calico/kube-controllers:v3.12.0 download succeeded by containerd", " Image download failed: quay.io/calico/pod2daemon-flexvol:v3.12.0500 Server Error: Internal Server Error (\"Get https://quay.io/v2/calico/pod2daemon-flexvol/manifests/v3.12.0: dial tcp 34.192.15.65:443: i/o timeout\")", "Sleep 20s before retry downloading image quay.io/calico/pod2daemon-flexvol:v3.12.0 ...", "Image download succeeded: quay.io/calico/pod2daemon-flexvol:v3.12.0", "Image push succeeded: registry.local:9001/quay.io/calico/pod2daemon-flexvol:v3.12.0", "Image quay.io/calico/pod2daemon-flexvol:v3.12.0 download succeeded by containerd", " Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...", " Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...", " Image download failed: docker.io/nfvpe/multus:v3.4500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Image is up to date for sha256:a2bef2b25274b1acbdfde5e2f3de432475e15d4036b2108cea2dce968b0c29ea", "Image is up to date for sha256:1f92aa902d739d544e621fe2ceaee04a4fc5b67c3e3ed8cf0b19aa2620763d3a", "Image is up to date for sha256:7fb3c2364b87e9241db7549bf11d42c129130f44e930d1ce36523fc693186e89", "Image is up to date for sha256:d4553944fbf7b50f20eece0ec3f638202fdbe2a1a597af8c3f3823201cc695b3", "Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/nfvpe/multus:v3.4 ...", "Image download succeeded: docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2", " Image download failed: docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2404 Client Error: Not Found (\"No such image: starlingx/k8s-cni-sriov:stx.3.0-v2.2\")", " Image download failed: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae500 Server Error: Internal Server Error (\"error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: \"

408 Request Time-out

\\nYour browser didn't send a complete request in time.\\n\\n\\n\"\")", "Sleep 20s before retry downloading image docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae ...", " Image download failed: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae ...", "Image download succeeded: docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae", "Image push succeeded: registry.local:9001/docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae", "Image docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae download succeeded by containerd", "Image download succeeded: gcr.io/kubernetes-helm/tiller:v2.16.1", "Image push succeeded: registry.local:9001/gcr.io/kubernetes-helm/tiller:v2.16.1", "Image gcr.io/kubernetes-helm/tiller:v2.16.1 download succeeded by containerd", "Image download succeeded: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic", " Image download failed: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic404 Client Error: Not Found (\"No such image: quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic\")", " Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0 ...", " Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0500 Server Error: Internal Server Error (\"Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\")", "Sleep 20s before retry downloading image docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0 ...", "Image download succeeded: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0", " Image download failed: docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0404 Client Error: Not Found (\"No such image: starlingx/n3000-opae:stx.4.0-v1.0.0\")", "Image download succeeded: quay.io/stackanetes/kubernetes-entrypoint:v0.3.1", "Image push succeeded: registry.local:9001/quay.io/stackanetes/kubernetes-entrypoint:v0.3.1", "Image quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 download succeeded by containerd", "Image download succeeded: quay.io/k8scsi/snapshot-controller:v2.0.0-rc2", "Image push succeeded: registry.local:9001/quay.io/k8scsi/snapshot-controller:v2.0.0-rc2", "Image quay.io/k8scsi/snapshot-controller:v2.0.0-rc2 download succeeded by containerd"]} PLAY RECAP **************************************************************************************************************************************************** localhost : ok=183 changed=67 unreachable=0 failed=1 From haridhar.kalvala at intel.com Thu Jan 7 06:09:49 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Thu, 7 Jan 2021 06:09:49 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , , , Message-ID: Thank you Al & Don. We did applied below suggested changes (only these changes on required modules/dependency modules) and build rpms, pkgs and generate wheels of the modules. However the docker build of stx-horizon is entering never-ending loop with continuous log as below (snapshot of log. Will send complete logs separately). Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /var/lib/openstack/lib/python3.6/site-packages (from horizon==18.3.3.dev19) (5.5.1) Requirement already satisfied: six in /var/lib/openstack/lib/python3.6/site-packages (from pylint) (1.14.0) Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) Sent: Wednesday, January 6, 2021 8:31 PM To: Kalvala, Haridhar ; Penney, Don ; starlingx-discuss at lists.starlingx.io; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada ; Wensley, Barton Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Those extra classifier entries in setup.py are redundant and can just be removed. setup.cfg provides them already. sysinv also would want this type of cleanup Also note, python 3.5 entries should probably also be cleaned up. Normally python 3.6 is where python3 compatability would start. I see tsconfig is listing only py3.5 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 11:06 PM To: Penney, Don >; Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hi Don Penney, Thank you, I will try only (will revert existing modifications) with these changes for the components. But setup.py doesn't need similar changes (Ex: cgts-client/setup.py) ? Thank you, Haridhar Kalvala From: Penney, Don > Sent: Tuesday, January 5, 2021 8:33 PM To: Kalvala, Haridhar >; Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. I think Al's original suggestion was to avoid changing the on-host installation of packages. Rather, to ensure that the modules required for the container are building a py3-compatible wheel that can be used for the image. Some of the wheels are already py2.py3 and available for use in a py3 image. The fm-common module, for example, has a compiled library and is py2-specific: /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl So updating the spec to use %py3_build_wheel allows us to build a wheel that should be compatible with a py3 image: $ git diff diff --git a/fm-common/centos/fm-common.spec b/fm-common/centos/fm-common.spec index a5c3618..f8d4ac9 100644 --- a/fm-common/centos/fm-common.spec +++ b/fm-common/centos/fm-common.spec @@ -19,6 +19,8 @@ BuildRequires: python-devel BuildRequires: python-setuptools BuildRequires: python2-pip BuildRequires: python2-wheel +BuildRequires: python3-pip +BuildRequires: python3-wheel Buildrequires: json-c-devel Requires: json-c @@ -55,6 +57,7 @@ MINOR=`echo $VER | awk -F . '{print $2}'` make MAJOR=$MAJOR MINOR=$MINOR %{?_smp_mflags} %{__python} setup.py build %py2_build_wheel +%py3_build_wheel %install rm -rf %{buildroot} With that change, we end up with wheels for both py2 and py3: $ rpm -qpl std/rpmbuild/RPMS/fm-common-wheels-1.0-50.tis.x86_64.rpm /wheels/fm_core-1.0-cp27-cp27mu-linux_x86_64.whl /wheels/fm_core-1.0-cp36-cp36m-linux_x86_64.whl Additionally, some modules may need an update to their setup.cfg to add py3 support. For example, cgts-client is currently py2-only: https://opendev.org/starlingx/config/src/branch/master/sysinv/cgts-client/cgts-client/setup.cfg So adding the following would be needed to get the wheel to support both py2 and py3, with a universal wheel: $ git diff diff --git a/sysinv/cgts-client/cgts-client/setup.cfg b/sysinv/cgts-client/cgts-client/setup.cfg index e1ee3e7b..0ca4697f 100644 --- a/sysinv/cgts-client/cgts-client/setup.cfg +++ b/sysinv/cgts-client/cgts-client/setup.cfg @@ -13,6 +13,8 @@ classifier = Programming Language :: Python Programming Language :: Python :: 2 Programming Language :: Python :: 2.7 + Programming Language :: Python :: 3 + Programming Language :: Python :: 3.6 [global] setup-hooks = @@ -33,3 +35,6 @@ autodoc_index_modules = False tag_build = tag_date = 0 tag_svn_revision = 0 + +[wheel] +universal = 1 With this change, I now see the following: $ rpm -qpl std/rpmbuild/RPMS/cgts-client-wheels-1.0-199.tis.x86_64.rpm /wheels/cgtsclient-1.0-py2.py3-none-any.whl A quick check of our wheel RPMs can show us which don't currently support py3. Most of these would be similar to the cgtsclient change, where the setup.cfg would need to be update to build a universal wheel that supports py2 and py3: $ for f in std/rpmbuild/RPMS/*-wheels* ; do rpm -qpl $f | grep -q -e '-py3-' -e '-py2.py3-' -e cp36 || echo $f; done std/rpmbuild/RPMS/ceph-manager-wheels-1.0-20.tis.x86_64.rpm std/rpmbuild/RPMS/cgts-client-wheels-1.0-198.tis.x86_64.rpm std/rpmbuild/RPMS/controllerconfig-wheels-1.0-222.tis.x86_64.rpm std/rpmbuild/RPMS/distributedcloud-client-wheels-1.0.0-1.tis.22.noarch.rpm std/rpmbuild/RPMS/distributedcloud-wheels-1.0.0-1.tis.215.noarch.rpm std/rpmbuild/RPMS/libvirt-python-wheels-4.7.0-1.tis.5.x86_64.rpm std/rpmbuild/RPMS/nfv-wheels-1.0-163.tis.x86_64.rpm std/rpmbuild/RPMS/nova-api-proxy-wheels-1.0-30.tis.x86_64.rpm std/rpmbuild/RPMS/platform-util-wheels-1.0-52.tis.noarch.rpm std/rpmbuild/RPMS/python-3parclient-wheels-4.2.3-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-barbicanclient-wheels-4.9.0-1.tis.3.noarch.rpm std/rpmbuild/RPMS/python-cephclient-wheels-13.2.2.0-10.tis.noarch.rpm std/rpmbuild/RPMS/python-django-horizon-wheels-15.1.0-1.tis.44.noarch.rpm std/rpmbuild/RPMS/python-lefthandclient-wheels-2.1.0-0.tis.3.noarch.rpm std/rpmbuild/RPMS/python-ryu-wheels-4.19-0.tis.5.noarch.rpm std/rpmbuild/RPMS/sm-api-wheels-1.0-35.tis.x86_64.rpm std/rpmbuild/RPMS/sm-client-wheels-1.0-24.tis.x86_64.rpm std/rpmbuild/RPMS/sm-tools-wheels-1.0-17.tis.x86_64.rpm std/rpmbuild/RPMS/starlingx-dashboard-wheels-1.0-251.tis.noarch.rpm std/rpmbuild/RPMS/sysinv-wheels-1.0-1857.tis.x86_64.rpm std/rpmbuild/RPMS/vm-topology-wheels-1.0-17.tis.noarch.rpm From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 8:40 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Yes Henry. Also #131/#133 And also when we migrate(as python3.6) fmclient, cgtsclient, distributed cloud etc... deployment fails because sysinv can't find the modules in 2.7. Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, January 5, 2021 6:47 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Wensley, Barton > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Are you referring to the hard-coding in the spec file? https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L60 which gets used when its built https://github.com/starlingx/config/blob/master/sysinv/sysinv/centos/sysinv.spec#L79 Al ________________________________ From: Kalvala, Haridhar > Sent: Tuesday, January 5, 2021 2:49 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada >; Kalvala, Haridhar >; Wensley, Barton > Subject: RE: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Hello All, In continuation to issue below, After migrating(as per below changing specs and cfg files) few flock components and built/pushed horizon container. But did not observe presence of migration components in python3.6 path of controller (/usr/lib/python3.6/site-packages....). So, I proceed with building all of packages and iso with changes. Deployment of ISO failed because sysinv couldn't find migrated flock components ( fmclient, cgtsclient etc) , since sysinv is built and search in python2.7 path while these components are migrated to python3.6. Any thoughts, on how to do and solve partial (few components which are also inter dependent) migration to pyhton3.6 on master branch ? Thank you, Haridhar Kalvala From: Kalvala, Haridhar > Sent: Tuesday, December 15, 2020 11:28 AM To: Bailey, Henry Albert (Al) >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. Importance: High Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) > Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu Jan 7 09:37:45 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 7 Jan 2021 09:37:45 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210107T023320Z Message-ID: Sanity Test from 2021-January-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210107T023320Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210107T023320Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Sriram.Dharwadkar at commscope.com Thu Jan 7 15:20:19 2021 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Thu, 7 Jan 2021 15:20:19 +0000 Subject: [Starlingx-discuss] [Distributed StarlingX 4.0] Multiple SRIOV pools Message-ID: Hi, We have installed Starlingx - Aug 5th release build for central cloud and edge cloud. controller-1:~$ cat /etc/build.info ### ### StarlingX ### Release 20.06 ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.4.0" JOB="STX_4.0_build_layer_flock" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="22" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-05 12:25:52 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_4.0_build_layer_flock" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="22" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-08-05 12:25:52 +0000" Hardware on which edge cloud is installed has Mellanox nic which is SRIOV capable. Commands that I m using to enable SRIOV functionality are, DATA0IF=enp101s0f0 export NODE=controller-1 PHYSNET0='physnet0' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list system host-port-list ${NODE} --nowrap > ${SPL} cat /tmp/tmp-system-port-list system host-if-list -a ${NODE} --nowrap > ${SPIL} cat /tmp/tmp-system-host-if-list DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 ~ DATA0PORTNAME) {print $2}') echo $DATA0IFUUID system datanetwork-add ${PHYSNET0} vlan system host-if-modify $NODE -n sriov0 -c pci-sriov -N 16 --vf-driver=netdevice $DATA0IFUUID system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} ${PHYSNET0} With these commands I m able to see that /etc/pcidp/config.json file is getting updated with the below contents controller-1:/home/sysadmin# cat /etc/pcidp/config.json { "resourceList": [ { "resourceName": "pci_sriov_net_physnet0", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0" ] } } ] } One device pool is created with 16 vfs. controller-1:/home/sysadmin# kubectl get node controller-1 -o json | jq '.status.allocatable' { "cpu": "22", "ephemeral-storage": "9391196145", "hugepages-1Gi": "20Gi", "hugepages-2Mi": "0", "intel.com/pci_sriov_net_physnet0": "16", "memory": "70207428Ki", "pods": "110" } Our usecase requires us to create multiple device pools like below. controller-1:/home/sysadmin# cat /etc/pcidp/config.json { "resourceList": [ { "resourceName": "cuplanepool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#0-4" ] } }, { "resourceName": "flupool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#5-9" ] } }, { "resourceName": "o1pool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#10-15" ] } } ] } Please let me know if it is possible to create multiple device pools from the same nic (with the filters as above) using StarlingX system CLI. Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Jan 8 01:49:26 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 8 Jan 2021 01:49:26 +0000 Subject: [Starlingx-discuss] rook patch review for project rook-ceph In-Reply-To: References: Message-ID: Thanks Don, Penney and AL review for my patch. Welcome more review opinion. https://review.opendev.org/c/starlingx/rook-ceph/+/716792 BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, January 6, 2021 4:18 PM To: 'Penney, Don' ; 'Scott Little' ; 'Waines, Greg' ; 'Poncea, Ovidiu' ; 'Church, Robert' Cc: 'starlingx-discuss at lists.starlingx.io' ; Sun, Austin ; Hu, Yong Subject: rook patch review for project rook-ceph Hi Please review patch for rook-ceph Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:10 PM To: Bailey, Henry Albert (Al) >; Penney, Don >; Scott Little >; Waines, Greg >; Poncea, Ovidiu >; Church, Robert > Cc: starlingx-discuss at lists.starlingx.io Subject: rook patch review for project rook-ceph Hi Please review my patch for rook-ceph project https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From anyrude10 at gmail.com Fri Jan 8 14:11:17 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Fri, 8 Jan 2021 19:41:17 +0530 Subject: [Starlingx-discuss] [Query] StarlingX 4.0 - Storage Network separate from MGMT+Cluster in Bare Metal Standard with Dedicated Storage Model Message-ID: Hi Team, I am trying to set up a Bare metal Standard with Dedicated Storage Installation R4.0 with 2 Controllers, 2 Storage Nodes and 2 Worker Nodes. https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage.html [image: image.png] As per the Network Diagram, storage nodes are connected to MGMT + Cluster Networks and all the traffic flows through this network only. https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage_install_kubernetes.html#configure-storage-nodes Even the document suggests to assign the cluster-host network to the MGMT interface for the storage nodes system interface-network-assign $NODE mgmt0 cluster-host Is it possible to have a storage network which is separate from mgmt+cluster networks? So that all the storage traffic passes only through that network Looking forward for your response. Regards Anirudh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 106914 bytes Desc: not available URL: From alexandru.dimofte at intel.com Fri Jan 8 15:03:22 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 8 Jan 2021 15:03:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210108T024308Z Message-ID: Sanity Test from 2021-January-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sat Jan 9 03:05:52 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 8 Jan 2021 22:05:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1450 - Failure! Message-ID: <1497172043.949.1610161553396.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1450 Status: Failure Timestamp: 20210109T024524Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210109T023110Z DOCKER_BUILD_ID: jenkins-master-distro-20210109T023110Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210109T023110Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From alexandru.dimofte at intel.com Sun Jan 10 20:10:06 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 10 Jan 2021 20:10:06 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210109T030533Z Message-ID: Sanity Test from 2021-January-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210109T030533Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210109T030533Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Mon Jan 11 01:17:46 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 11 Jan 2021 01:17:46 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 32, Issue 33 In-Reply-To: References: Message-ID: Hi Scott My patch is merged on Jan. 9th to fix this saint test fail issue. https://review.opendev.org/c/starlingx/upstream/+/769662 And I find for stx-versioned app, the docker image tag is master-centos-stable-20210104T053001Z.0. So image should be build on Jan. 4th. So we should trigger build to make image update on docker.io to fix this issue. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Saturday, January 9, 2021 11:06 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 32, Issue 33 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Sanity Master Test LAYERED build ISO 20210108T024308Z (Dimofte, Alexandru) 2. [build-report] STX_build_lst_audit - Build # 1450 - Failure! (build.starlingx at gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Fri, 8 Jan 2021 15:03:22 +0000 From: "Dimofte, Alexandru" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210108T024308Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2021-January-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: ------------------------------ Message: 2 Date: Fri, 8 Jan 2021 22:05:52 -0500 (EST) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1450 - Failure! Message-ID: <1497172043.949.1610161553396.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_lst_audit Build #: 1450 Status: Failure Timestamp: 20210109T024524Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210109T023110Z DOCKER_BUILD_ID: jenkins-master-distro-20210109T023110Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210109T023110Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 32, Issue 33 ************************************************* From maryx.camp at intel.com Mon Jan 11 05:36:27 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Mon, 11 Jan 2021 05:36:27 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 06-Jan-2021 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2021-01-06 All -- reviews merged since last meeting: 8 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config Status/questions/opens Upstreaming high-level status: Ron estimates 3 outstanding docs, most are done. This does not include install guides, they will be addressed later. Juanita has 1 and Kean has 2, both are WIP. None of the OpenStack portions of any of the guides are done yet. Upstreaming Plan 1. Complete the 3 guides that are currently WIP. 2. Evaluate the upstreamed content against latest release of WRCP and make updates. This is because the upstreamed content was a snapshot from August. When complete, all the core Kubernetes content will be upstreamed and current. 3. Convert the OpenStack portions of upstream content. This step requires a new snapshot and then conversion activity. penStack content will need to be upleveled for readability. 4. Convert the Install guides. The install guides are complex and require disentangling the process from upstream/downstream actions. The WindRiver install guides point upstream for many things and then describe WRCP minor exceptions (something like: in step 5, use the WR link instead of the STX link.) Requires some more planning to figure out how to do it properly. Release 5 features/updates, such as the SNMP v2 to v3 change Some will be included in the upstreaming effort because they are already covered in the WR documentation. AR Mary get the latest features list from release mtg notes and bring to next week's docs meeting for discussion. Strings file Ron recommends splitting into 2 files. One file that is "common common" containing the rubrics & abbreviations that both upstream & downstream need. We will still have the reuse factor but not as unwieldy as 1 big file. Team agreed. Future requests Figure out breadcrumbs -- look at css/templates to see how we can show reader where they are in the documentation. Mary to follow up with Intel folks to ask for help with the version drop-down. From haridhar.kalvala at intel.com Mon Jan 11 08:18:08 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Mon, 11 Jan 2021 08:18:08 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Message-ID: Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Jan 11 08:27:32 2021 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 11 Jan 2021 08:27:32 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. In-Reply-To: References: Message-ID: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" Cc: "Bailey, Henry Albert (Al)" , "Penney, Don" , "Miller, Frank" , "Mukherjee, Sanjay K" , "Bhat, Gopalkrishna" Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Jan 11 13:30:32 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 11 Jan 2021 08:30:32 -0500 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 32, Issue 33 In-Reply-To: References: Message-ID: <15c6cbe9-137d-52d4-0193-6eedac803b90@windriver.com> I have started the build.  I expect completion by 6 pm UTC. Scott On 2021-01-10 8:17 p.m., Chen, Haochuan Z wrote: > Hi Scott > > My patch is merged on Jan. 9th to fix this saint test fail issue. > https://review.opendev.org/c/starlingx/upstream/+/769662 > > And I find for stx-versioned app, the docker image tag is master-centos-stable-20210104T053001Z.0. So image should be build on Jan. 4th. > So we should trigger build to make image update on docker.io to fix this issue. > > Thanks! > > Martin, Chen > IOTG, Software Engineer > 021-61164330 > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io > Sent: Saturday, January 9, 2021 11:06 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 32, Issue 33 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. Sanity Master Test LAYERED build ISO 20210108T024308Z > (Dimofte, Alexandru) > 2. [build-report] STX_build_lst_audit - Build # 1450 - Failure! > (build.starlingx at gmail.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Jan 2021 15:03:22 +0000 > From: "Dimofte, Alexandru" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20210108T024308Z > Message-ID: > > > Content-Type: text/plain; charset="utf-8" > > Sanity Test from 2021-January-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/iso/ ) > > Status: RED > > Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210108T024308Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz > > This image/helm-chart is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 > > Regards, > STX Validation Team > > [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com > Intel Romania > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 8413 bytes > Desc: image001.png > URL: > > ------------------------------ > > Message: 2 > Date: Fri, 8 Jan 2021 22:05:52 -0500 (EST) > From: build.starlingx at gmail.com > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - > Build # 1450 - Failure! > Message-ID: > <1497172043.949.1610161553396.JavaMail.javamailuser at localhost> > Content-Type: text/plain; charset="utf-8" > > Project: STX_build_lst_audit > Build #: 1450 > Status: Failure > Timestamp: 20210109T024524Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs > -------------------------------------------------------------------------------- > Parameters > > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210109T023110Z > DOCKER_BUILD_ID: jenkins-master-distro-20210109T023110Z-builder > OS: centos > MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210109T023110Z/logs > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210109T023110Z/logs > MASTER_JOB_NAME: STX_build_layer_distro_master_master > LAYER: distro > MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro > PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 32, Issue 33 > ************************************************* From amy at demarco.com Mon Jan 11 13:49:09 2021 From: amy at demarco.com (Amy Marrich) Date: Mon, 11 Jan 2021 07:49:09 -0600 Subject: [Starlingx-discuss] [Diversity] Diversity &Inclusion WG Meeting reminder Message-ID: The Diversity & Inclusion WG invites members of all OSF projects to our meeting today, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 12 05:04:37 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Jan 2021 00:04:37 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 315 - Failure! Message-ID: <1858314506.955.1610427877683.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 315 Status: Failure Timestamp: 20210112T014733Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210112T010746Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs PUBLISH_TIMESTAMP: 20210112T010746Z FLOCK_VERSION: master-centos-stable-20210112T010746Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210112T010746Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Jan 12 05:04:39 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Jan 2021 00:04:39 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 74 - Failure! Message-ID: <1797682517.958.1610427879662.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 74 Status: Failure Timestamp: 20210112T012906Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs MASTER_BUILD_NUMBER: 97 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210112T010746Z DOCKER_BUILD_ID: jenkins-master-containers-20210112T010746Z-builder TIMESTAMP: 20210112T010746Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs From build.starlingx at gmail.com Tue Jan 12 05:04:42 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Jan 2021 00:04:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 97 - Failure! Message-ID: <1678321111.961.1610427882931.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 97 Status: Failure Timestamp: 20210112T010746Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From haochuan.z.chen at intel.com Tue Jan 12 05:46:39 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 12 Jan 2021 05:46:39 +0000 Subject: [Starlingx-discuss] docker image build fail Message-ID: Hi Docker image build fail! There were 1 failures: stx-oidc-client Build step 'Execute shell' marked build as failure get "golang.org/x/net/context/ctxhttp": verifying non-authoritative meta tag golang.org/x/net (download) The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 Command (docker) failed, attempt 5 of 5. Max command attempts reached. Aborting... Failed to build stx-oidc-client... Aborting Building portieris get_git 'https://github.com/IBM/portieris.git'; '0.7.0' '/localdisk/designer/jenkins/master-containers/cgcs-root/stx/portieris-armada-app/portieris-helm/centos/../files/0001-Squash-required-portieris-fixes.patch' Cloning into 'portieris'... Note: checking out '0.7.0'. logs link http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, January 12, 2021 1:05 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 32, Issue 37 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Starlingx-discuss Digest, Vol 32, Issue 33 (Scott Little) 2. [Diversity] Diversity &Inclusion WG Meeting reminder (Amy Marrich) 3. [stable] [build-report] STX_build_docker_flock_images - Build # 315 - Failure! (build.starlingx at gmail.com) 4. [stable] [build-report] master STX_build_docker_images_layered - Build # 74 - Failure! (build.starlingx at gmail.com) 5. [build-report] master STX_build_layer_containers_master_master - Build # 97 - Failure! (build.starlingx at gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 Jan 2021 08:30:32 -0500 From: Scott Little To: "Chen, Haochuan Z" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 32, Issue 33 Message-ID: <15c6cbe9-137d-52d4-0193-6eedac803b90 at windriver.com> Content-Type: text/plain; charset=utf-8; format=flowed I have started the build.  I expect completion by 6 pm UTC. Scott On 2021-01-10 8:17 p.m., Chen, Haochuan Z wrote: > Hi Scott > > My patch is merged on Jan. 9th to fix this saint test fail issue. > https://review.opendev.org/c/starlingx/upstream/+/769662 > > And I find for stx-versioned app, the docker image tag is master-centos-stable-20210104T053001Z.0. So image should be build on Jan. 4th. > So we should trigger build to make image update on docker.io to fix this issue. > > Thanks! > > Martin, Chen > IOTG, Software Engineer > 021-61164330 > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io > > Sent: Saturday, January 9, 2021 11:06 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 32, Issue 33 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. Sanity Master Test LAYERED build ISO 20210108T024308Z > (Dimofte, Alexandru) > 2. [build-report] STX_build_lst_audit - Build # 1450 - Failure! > (build.starlingx at gmail.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Jan 2021 15:03:22 +0000 > From: "Dimofte, Alexandru" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20210108T024308Z > Message-ID: > > tlook.com> > > Content-Type: text/plain; charset="utf-8" > > Sanity Test from 2021-January-08 > (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock > /20210108T024308Z/outputs/iso/ ) > > Status: RED > > Helm-Chart used: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/ > 20210108T024308Z/outputs/helm-charts/helm-charts-stx-openstack-centos- > stable-versioned.tgz > > This image/helm-chart is affected by: > https://bugs.launchpad.net/starlingx/+bug/1908117 > > Regards, > STX Validation Team > > [Logo Description automatically generated] Dimofte Alexandru > Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal > Mobile: +40 743167456 > alexandru.dimofte at intel.com > Intel Romania > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > 10108/2a997fcf/attachment-0001.html> > -------------- next part -------------- A non-text attachment was > scrubbed... > Name: image001.png > Type: image/png > Size: 8413 bytes > Desc: image001.png > URL: > 10108/2a997fcf/attachment-0001.png> > > ------------------------------ > > Message: 2 > Date: Fri, 8 Jan 2021 22:05:52 -0500 (EST) > From: build.starlingx at gmail.com > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - > Build # 1450 - Failure! > Message-ID: > <1497172043.949.1610161553396.JavaMail.javamailuser at localhost> > Content-Type: text/plain; charset="utf-8" > > Project: STX_build_lst_audit > Build #: 1450 > Status: Failure > Timestamp: 20210109T024524Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro > /20210109T023110Z/logs > ---------------------------------------------------------------------- > ---------- > Parameters > > MY_WORKSPACE: > /localdisk/loadbuild/jenkins/master-distro/20210109T023110Z > DOCKER_BUILD_ID: jenkins-master-distro-20210109T023110Z-builder > OS: centos > MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root > PUBLISH_LOGS_URL: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro > /20210109T023110Z/logs > PUBLISH_LOGS_BASE: > /export/mirror/starlingx/master/centos/distro/20210109T023110Z/logs > MASTER_JOB_NAME: STX_build_layer_distro_master_master > LAYER: distro > MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro > PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 32, Issue 33 > ************************************************* ------------------------------ Message: 2 Date: Mon, 11 Jan 2021 07:49:09 -0600 From: Amy Marrich To: foundation at lists.openstack.org, openstack-discuss , kata-dev at lists.katacontainers.io, starlingx-discuss at lists.starlingx.io, airship-discuss at lists.airshipit.org, zuul-discuss at lists.zuul-ci.org Subject: [Starlingx-discuss] [Diversity] Diversity &Inclusion WG Meeting reminder Message-ID: Content-Type: text/plain; charset="utf-8" The Diversity & Inclusion WG invites members of all OSF projects to our meeting today, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 12 Jan 2021 00:04:37 -0500 (EST) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 315 - Failure! Message-ID: <1858314506.955.1610427877683.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_flock_images Build #: 315 Status: Failure Timestamp: 20210112T014733Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210112T010746Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs PUBLISH_TIMESTAMP: 20210112T010746Z FLOCK_VERSION: master-centos-stable-20210112T010746Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210112T010746Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs REGISTRY: docker.io ------------------------------ Message: 4 Date: Tue, 12 Jan 2021 00:04:39 -0500 (EST) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 74 - Failure! Message-ID: <1797682517.958.1610427879662.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images_layered Build #: 74 Status: Failure Timestamp: 20210112T012906Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs MASTER_BUILD_NUMBER: 97 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210112T010746Z DOCKER_BUILD_ID: jenkins-master-containers-20210112T010746Z-builder TIMESTAMP: 20210112T010746Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs ------------------------------ Message: 5 Date: Tue, 12 Jan 2021 00:04:42 -0500 (EST) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 97 - Failure! Message-ID: <1678321111.961.1610427882931.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_layer_containers_master_master Build #: 97 Status: Failure Timestamp: 20210112T010746Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 32, Issue 37 ************************************************* From lists at optimcloud.com Tue Jan 12 08:08:14 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Tue, 12 Jan 2021 15:08:14 +0700 Subject: [Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff Message-ID: <4415144.vXUDI8C0e8@localhost.localdomain> any idea how to resolve this, was installed from a recent 01/08/2021 build AIO Simplex ojn bare metal kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff 4 2m49s [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs kube-sriov-device- plugin-amd64-547xh --namespace kube-system error: the server doesn't have a resource type "logs" [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs kube-sriov-device- plugin-amd64-547xh --namespace kube-system I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin Registry Mode I0112 08:05:19.714707 158061 main.go:44] resource manager reading configs I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: { "resourceList": [ ] } I0112 08:05:19.714795 158061 manager.go:106] unmarshalled ResourceList: [] E0112 08:05:19.714801 158061 main.go:51] no resource configuration; exiting From lists at optimcloud.com Tue Jan 12 08:44:17 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Tue, 12 Jan 2021 15:44:17 +0700 Subject: [Starlingx-discuss] fm-rest-api appears broken Message-ID: <2527185.vuYhMxLoTh@localhost.localdomain> recent 01/08/2021 image baremetal aio simplex apply openstack is throwing error on fm-rest-api kubectl logs fm-rest-api-d7cb8f564-qpnx6 --namespace openstack ++ awk -F = '/sql_connection/{print $2}' /etc/fm/fm.conf + export 'SQL_CONNECTION= mysql+pymysql://fm:P69q*mx' + SQL_CONNECTION=' mysql+pymysql://fm:P69q*mx' + echo 'mysql+pymysql://fm:P69q*mx' + python /usr/local/bin/fm_db_sync_event_suppression.py 'mysql+pymysql:// fm:P69q*mx' Traceback (most recent call last): File "/usr/local/bin/fm_db_sync_event_suppression.py", line 96, in engine = sqlalchemy.create_engine(postgresql_credentials) File "/var/lib/openstack/lib64/python2.7/site-packages/sqlalchemy/engine/ __init__.py", line 456, in create_engine return strategy.create(*args, **kwargs) File "/var/lib/openstack/lib64/python2.7/site-packages/sqlalchemy/engine/ strategies.py", line 54, in create u = url.make_url(name_or_url) File "/var/lib/openstack/lib64/python2.7/site-packages/sqlalchemy/engine/ url.py", line 229, in make_url return _parse_rfc1738_args(name_or_url) File "/var/lib/openstack/lib64/python2.7/site-packages/sqlalchemy/engine/ url.py", line 288, in _parse_rfc1738_args return URL(name, **components) File "/var/lib/openstack/lib64/python2.7/site-packages/sqlalchemy/engine/ url.py", line 71, in __init__ self.port = int(port) ValueError: invalid literal for int() with base 10: 'P69q*mx' From pvmpublic at gmail.com Tue Jan 12 13:04:34 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Tue, 12 Jan 2021 18:34:34 +0530 Subject: [Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff In-Reply-To: <4415144.vXUDI8C0e8@localhost.localdomain> References: <4415144.vXUDI8C0e8@localhost.localdomain> Message-ID: Hi, 1. What does your /etc/pcidp/config.json look like? 2. Did you do all these steps? # system host-label-assign controller-0 sriovdp=enabled # system host-if-modify controller-0 -c pci-sriov -n sriov0 -N # system interface-datanetwork-assign controller-0 # system host-unlock Thanks Pratik On Tue, Jan 12, 2021 at 1:39 PM wrote: > any idea how to resolve this, was installed from a recent 01/08/2021 build > AIO > Simplex ojn bare metal > > kube-system kube-sriov-device-plugin-amd64-547xh 0/1 > CrashLoopBackOff 4 2m49s > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs > kube-sriov-device- > plugin-amd64-547xh --namespace kube-system > error: the server doesn't have a resource type "logs" > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs kube-sriov-device- > plugin-amd64-547xh --namespace kube-system > I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin Registry > Mode > I0112 08:05:19.714707 158061 main.go:44] resource manager reading configs > I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: { > "resourceList": [ > > ] > } > I0112 08:05:19.714795 158061 manager.go:106] unmarshalled ResourceList: [] > E0112 08:05:19.714801 158061 main.go:51] no resource configuration; > exiting > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Tue Jan 12 14:19:27 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Tue, 12 Jan 2021 21:19:27 +0700 Subject: [Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff In-Reply-To: References: <4415144.vXUDI8C0e8@localhost.localdomain> Message-ID: <2119226.vFx2qVVIhK@localhost.localdomain> On Tuesday, January 12, 2021 8:04:34 PM +07 Pratik M. wrote: > Hi, > 1. What does your /etc/pcidp/config.json look like? > > 2. Did you do all these steps? > # system host-label-assign controller-0 sriovdp=enabled > # system host-if-modify controller-0 -c pci-sriov -n sriov0 -N > > # system interface-datanetwork-assign controller-0 > > # system host-unlock > > Thanks > Pratik history start to finish 1 ps xa 2 ip addr 3 cat < localhost.yml 4 system_mode: simplex 5 dns_servers: 6 - 8.8.8.8 7 - 8.8.4.4 8 external_oam_subnet: / 9 external_oam_gateway_address: 10 external_oam_floating_address: 11 admin_username: admin 12 admin_password: 13 ansible_become_pass: 14 EOF 15 vi localhost.yml 16 ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml 17 source /etc/platform/openrc 18 ip addr 19 OAM_IF=eno1 20 system host-if-modify controller-0 $OAM_IF -c platform 21 system interface-network-assign controller-0 $OAM_IF oam 22 system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org 23 system storage-backend-add ceph --confirmed 24 system host-label-assign controller-0 sriovdp=enabled 25 system host-memory-modify controller-0 0 -1G 100 26 DATA0IF=enp101s0f0 27 DATA1IF=enp101s0f1 28 export NODE=controller-0 29 PHYSNET0='physnet0' 30 PHYSNET1='physnet1' 31 SPL=/tmp/tmp-system-port-list 32 SPIL=/tmp/tmp-system-host-if-list 33 system host-port-list ${NODE} --nowrap > ${SPL} 34 system host-if-list -a ${NODE} --nowrap > ${SPIL} 35 DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') 36 DATA1PCIADDR=$(cat $SPL | grep $DATA1IF |awk '{print $8}') 37 DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') 38 DATA1PORTUUID=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $2}') 39 DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') 40 DATA1PORTNAME=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $4}') 41 DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 ~ DATA0PORTNAME) {print $2}') 42 DATA1IFUUID=$(cat $SPIL | awk -v DATA1PORTNAME=$DATA1PORTNAME '($12 ~ DATA1PORTNAME) {print $2}') 43 system datanetwork-add ${PHYSNET0} vlan 44 system datanetwork-add ${PHYSNET1} vlan 45 system host-if-modify -m 1500 -n data0 -c data ${NODE} ${DATA0IFUUID} 46 system host-if-modify -m 1500 -n data1 -c data ${NODE} ${DATA1IFUUID} 47 system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} ${PHYSNET0} 48 system interface-datanetwork-assign ${NODE} ${DATA1IFUUID} ${PHYSNET1} 49 system host-disk-list controller-0 50 system host-disk-list controller-0 | awk '/\/dev\/nvme1n1/{print $2}' | xargs -i system host-stor-add controller-0 {} 51 system host-disk-list controller-0 | awk '/\/dev\/nvme2n1/{print $2}' | xargs -i system host-stor-add controller-0 {} 52 system host-label-assign controller-0 openstack-control-plane=enabled 53 system host-label-assign controller-0 openstack-compute-node=enabled 54 system host-label-assign controller-0 openvswitch=enabled 55 system host-label-assign controller-0 sriov=enabled 56 system modify --vswitch_type ovs-dpdk 57 system host-cpu-modify -f vswitch -p0 1 controller-0 58 export NODE=controller-0 59 echo ">>> Getting root disk info" 60 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') 61 ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep $ {ROOT_DISK} | awk '{print $2}') 62 echo "Root disk: $ROOT_DISK, UUID: $ROOT_DISK_UUID" 63 echo ">>>> Configuring nova-local" 64 NOVA_SIZE=34 65 NOVA_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${NODE} ${ROOT_DISK_UUID} ${NOVA_SIZE}) 66 NOVA_PARTITION_UUID=$(echo ${NOVA_PARTITION} | grep -ow "| uuid | [a- z0-9\-]* |" | awk '{print $4}') 67 system host-lvg-add ${NODE} nova-local 68 system host-pv-add ${NODE} nova-local ${NOVA_PARTITION_UUID} 69 sleep 2 70 system host-memory-list controller-0 71 system host-unlock controller-0 72 system host-memory-modify controller-0 0 -1G 100 73 system host-unlock controller-0 74 system host-memory-modify controller-0 1 -1G 100 75 system host-label-assign controller-0 openvswitch=enabled 76 system host-memory-modify -f vswitch -1G 1 compute-0 0 77 system host-memory-modify controller-0 0 -1G 100 78 system host-unlock controller-0 79 system host-memory-modify -f vswitch -1G 1 compute-0 0 80 system host-memory-modify -f vswitch -1G 1 controller-0 0 81 system host-unlock controller-0 82 history > HIST > > On Tue, Jan 12, 2021 at 1:39 PM wrote: > > any idea how to resolve this, was installed from a recent 01/08/2021 build > > AIO > > Simplex ojn bare metal > > > > kube-system kube-sriov-device-plugin-amd64-547xh 0/1 > > CrashLoopBackOff 4 2m49s > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs > > kube-sriov-device- > > plugin-amd64-547xh --namespace kube-system > > error: the server doesn't have a resource type "logs" > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs kube-sriov-device- > > plugin-amd64-547xh --namespace kube-system > > I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin Registry > > Mode > > I0112 08:05:19.714707 158061 main.go:44] resource manager reading configs > > I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: { > > > > "resourceList": [ > > > > ] > > > > } > > I0112 08:05:19.714795 158061 manager.go:106] unmarshalled ResourceList: > > [] > > E0112 08:05:19.714801 158061 main.go:51] no resource configuration; > > exiting > > > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Tue Jan 12 15:58:10 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 12 Jan 2021 10:58:10 -0500 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 315 - Failure! In-Reply-To: <1858314506.955.1610427877683.JavaMail.javamailuser@localhost> References: <1858314506.955.1610427877683.JavaMail.javamailuser@localhost> Message-ID: The stx-oidc-client container failed to build. There are no relevant code deltas. It appears to be a transient network or upstream repo issue. *21:32:47* Step 4/7 : RUN go get -d -v ./... *21:32:47* ---> Running in 70e0c0f33dbc *21:32:47* github.com/coreos/go-oidc (download) *21:32:47* package github.com/coreos/go-oidc: no Go files in /go/src/github.com/coreos/go-oidc ... *21:33:12* The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 I will launch a rebuild On 2021-01-12 12:04 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_docker_flock_images > Build #: 315 > Status: Failure > Timestamp: 20210112T014733Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs > -------------------------------------------------------------------------------- > Parameters > > WEB_HOST: mirror.starlingx.cengn.ca > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root > BASE_VERSION: master-stable-20210112T010746Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs > REGISTRY_USERID: slittlewrs > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs > PUBLISH_TIMESTAMP: 20210112T010746Z > FLOCK_VERSION: master-centos-stable-20210112T010746Z > WEB_HOST_PORT: 80 > PREFIX: master > TIMESTAMP: 20210112T010746Z > BUILD_STREAM: stable > REGISTRY_ORG: starlingx > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs > REGISTRY: docker.io > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatindra.shashi at intel.com Tue Jan 12 16:47:51 2021 From: yatindra.shashi at intel.com (Shashi, Yatindra) Date: Tue, 12 Jan 2021 16:47:51 +0000 Subject: [Starlingx-discuss] Creating own libvirt docker container for StarlingX-Openstack Message-ID: Dear All, I would like to create my own container for libvirt (basically with acrn-libvirt ) for testing purpose to run acrn hypervisioe with stx-openstack. I have tested with devstack and basic functionality works perfectly, so now I wanted to build acrn-libvirt container which will be used by the stx-openstack application. In short, I would like to make docker-container like available in docker hub for stx-libvirt but with my acrn-libvirt github repo. I followed the STX- build process (https://docs.starlingx.io/developer_resources/build_guide.html ) and found the github libvirt src file at location $ /home/ecrd3/starlingx/workspace/localdisk/designer/ecrd3/stx-build/cgcs-root/stx/git/libvirt and building docker image command at $ /home/ecrd3/starlingx/workspace/localdisk/designer/ecrd3/stx-build/cgcs-root/build-tools/build-docker-images But not able to do on steps. Could someone guide me with steps? I get little information at stx wiki for stx-libvirt docker image from ( https://docs.starlingx.io/developer_resources/build_docker_image.html#id5 ). Thanx Mit freundlichen Grüßen/ with best regards, Yatindra Shashi IoTG DE- Intel Corporation Munich, Germany Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Jan 12 20:30:34 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 12 Jan 2021 15:30:34 -0500 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 315 - Failure! In-Reply-To: References: <1858314506.955.1610427877683.JavaMail.javamailuser@localhost> Message-ID: <8494a026-cff7-2b0d-234e-e725238fdf6e@windriver.com> The failure is reproducible. I have created a launchpad ... https://bugs.launchpad.net/starlingx/+bug/1911244 Scott On 2021-01-12 10:58 a.m., Scott Little wrote: > The stx-oidc-client container failed to build. > > There are no relevant code deltas. It appears to be a transient > network or upstream repo issue. > > *21:32:47* Step 4/7 : RUN go get -d -v ./... > *21:32:47* ---> Running in 70e0c0f33dbc > *21:32:47* github.com/coreos/go-oidc (download) > *21:32:47* package github.com/coreos/go-oidc: no Go files in /go/src/github.com/coreos/go-oidc > ... > *21:33:12* The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 > > I will launch a rebuild > > > On 2021-01-12 12:04 a.m., build.starlingx at gmail.com wrote: >> [Please note this e-mail is from an EXTERNAL e-mail address] >> >> Project: STX_build_docker_flock_images >> Build #: 315 >> Status: Failure >> Timestamp: 20210112T014733Z >> Branch: >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> WEB_HOST: mirror.starlingx.cengn.ca >> MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210112T010746Z >> OS: centos >> MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root >> BASE_VERSION: master-stable-20210112T010746Z >> PUBLISH_LOGS_URL:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210112T010746Z/logs >> REGISTRY_USERID: slittlewrs >> LATEST_PREFIX: master >> PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/logs >> PUBLISH_TIMESTAMP: 20210112T010746Z >> FLOCK_VERSION: master-centos-stable-20210112T010746Z >> WEB_HOST_PORT: 80 >> PREFIX: master >> TIMESTAMP: 20210112T010746Z >> BUILD_STREAM: stable >> REGISTRY_ORG: starlingx >> PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210112T010746Z/outputs >> REGISTRY: docker.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Jan 13 00:54:29 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 13 Jan 2021 00:54:29 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Hi Please review patch for rook-ceph. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 https://review.opendev.org/c/starlingx/utilities/+/760503 https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Jan 13 00:56:12 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 13 Jan 2021 00:56:12 +0000 Subject: [Starlingx-discuss] cenga mirror download folder broken Message-ID: Hi Scott Download folder for all layer is blank now. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/inputs/downloads/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Jan 13 07:37:26 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 13 Jan 2021 07:37:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210112T000255Z Message-ID: Sanity Test from 2021-January-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210112T000255Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210112T000255Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8408 bytes Desc: image003.png URL: From pvmpublic at gmail.com Wed Jan 13 08:46:46 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Wed, 13 Jan 2021 14:16:46 +0530 Subject: [Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff In-Reply-To: <2119226.vFx2qVVIhK@localhost.localdomain> References: <4415144.vXUDI8C0e8@localhost.localdomain> <2119226.vFx2qVVIhK@localhost.localdomain> Message-ID: Hi, You do not seem to have done the steps mentioned to use SRIOV (in my #2). Do you plan to use SRIOV? If not, you can ignore the crashloop of the container. Else you can try if the following helps: # system host-label-assign controller-0 sriov=disabled Thanks On Tue, Jan 12, 2021 at 7:50 PM wrote: > On Tuesday, January 12, 2021 8:04:34 PM +07 Pratik M. wrote: > > Hi, > > 1. What does your /etc/pcidp/config.json look like? > > > > 2. Did you do all these steps? > > # system host-label-assign controller-0 sriovdp=enabled > > # system host-if-modify controller-0 -c pci-sriov -n sriov0 > -N > > > > # system interface-datanetwork-assign controller-0 > > > > # system host-unlock > > > > Thanks > > Pratik > history start to finish > > 1 ps xa > 2 ip addr > 3 cat < localhost.yml > 4 system_mode: simplex > 5 dns_servers: > 6 - 8.8.8.8 > 7 - 8.8.4.4 > 8 external_oam_subnet: / > 9 external_oam_gateway_address: > 10 external_oam_floating_address: > 11 admin_username: admin > 12 admin_password: > 13 ansible_become_pass: > 14 EOF > 15 vi localhost.yml > 16 ansible-playbook > /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml > 17 source /etc/platform/openrc > 18 ip addr > 19 OAM_IF=eno1 > 20 system host-if-modify controller-0 $OAM_IF -c platform > 21 system interface-network-assign controller-0 $OAM_IF oam > 22 system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org > 23 system storage-backend-add ceph --confirmed > 24 system host-label-assign controller-0 sriovdp=enabled > 25 system host-memory-modify controller-0 0 -1G 100 > 26 DATA0IF=enp101s0f0 > 27 DATA1IF=enp101s0f1 > 28 export NODE=controller-0 > 29 PHYSNET0='physnet0' > 30 PHYSNET1='physnet1' > 31 SPL=/tmp/tmp-system-port-list > 32 SPIL=/tmp/tmp-system-host-if-list > 33 system host-port-list ${NODE} --nowrap > ${SPL} > 34 system host-if-list -a ${NODE} --nowrap > ${SPIL} > 35 DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') > 36 DATA1PCIADDR=$(cat $SPL | grep $DATA1IF |awk '{print $8}') > 37 DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') > 38 DATA1PORTUUID=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $2}') > 39 DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') > 40 DATA1PORTNAME=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $4}') > 41 DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 > ~ > DATA0PORTNAME) {print $2}') > 42 DATA1IFUUID=$(cat $SPIL | awk -v DATA1PORTNAME=$DATA1PORTNAME '($12 > ~ > DATA1PORTNAME) {print $2}') > 43 system datanetwork-add ${PHYSNET0} vlan > 44 system datanetwork-add ${PHYSNET1} vlan > 45 system host-if-modify -m 1500 -n data0 -c data ${NODE} > ${DATA0IFUUID} > 46 system host-if-modify -m 1500 -n data1 -c data ${NODE} > ${DATA1IFUUID} > 47 system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} > ${PHYSNET0} > 48 system interface-datanetwork-assign ${NODE} ${DATA1IFUUID} > ${PHYSNET1} > 49 system host-disk-list controller-0 > 50 system host-disk-list controller-0 | awk '/\/dev\/nvme1n1/{print > $2}' | > xargs -i system host-stor-add controller-0 {} > 51 system host-disk-list controller-0 | awk '/\/dev\/nvme2n1/{print > $2}' | > xargs -i system host-stor-add controller-0 {} > 52 system host-label-assign controller-0 > openstack-control-plane=enabled > 53 system host-label-assign controller-0 openstack-compute-node=enabled > 54 system host-label-assign controller-0 openvswitch=enabled > 55 system host-label-assign controller-0 sriov=enabled > 56 system modify --vswitch_type ovs-dpdk > 57 system host-cpu-modify -f vswitch -p0 1 controller-0 > 58 export NODE=controller-0 > 59 echo ">>> Getting root disk info" > 60 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print > $4}') > 61 ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep $ > {ROOT_DISK} | awk '{print $2}') > 62 echo "Root disk: $ROOT_DISK, UUID: $ROOT_DISK_UUID" > 63 echo ">>>> Configuring nova-local" > 64 NOVA_SIZE=34 > 65 NOVA_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol > ${NODE} > ${ROOT_DISK_UUID} ${NOVA_SIZE}) > 66 NOVA_PARTITION_UUID=$(echo ${NOVA_PARTITION} | grep -ow "| uuid | > [a- > z0-9\-]* |" | awk '{print $4}') > 67 system host-lvg-add ${NODE} nova-local > 68 system host-pv-add ${NODE} nova-local ${NOVA_PARTITION_UUID} > 69 sleep 2 > 70 system host-memory-list controller-0 > 71 system host-unlock controller-0 > 72 system host-memory-modify controller-0 0 -1G 100 > 73 system host-unlock controller-0 > 74 system host-memory-modify controller-0 1 -1G 100 > 75 system host-label-assign controller-0 openvswitch=enabled > 76 system host-memory-modify -f vswitch -1G 1 compute-0 0 > 77 system host-memory-modify controller-0 0 -1G 100 > 78 system host-unlock controller-0 > 79 system host-memory-modify -f vswitch -1G 1 compute-0 0 > 80 system host-memory-modify -f vswitch -1G 1 controller-0 0 > 81 system host-unlock controller-0 > 82 history > HIST > > > > > > > On Tue, Jan 12, 2021 at 1:39 PM wrote: > > > any idea how to resolve this, was installed from a recent 01/08/2021 > build > > > AIO > > > Simplex ojn bare metal > > > > > > kube-system kube-sriov-device-plugin-amd64-547xh 0/1 > > > CrashLoopBackOff 4 2m49s > > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs > > > kube-sriov-device- > > > plugin-amd64-547xh --namespace kube-system > > > error: the server doesn't have a resource type "logs" > > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs > kube-sriov-device- > > > plugin-amd64-547xh --namespace kube-system > > > I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin > Registry > > > Mode > > > I0112 08:05:19.714707 158061 main.go:44] resource manager reading > configs > > > I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: { > > > > > > "resourceList": [ > > > > > > ] > > > > > > } > > > I0112 08:05:19.714795 158061 manager.go:106] unmarshalled > ResourceList: > > > [] > > > E0112 08:05:19.714801 158061 main.go:51] no resource configuration; > > > exiting > > > > > > > > > > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Wed Jan 13 09:03:38 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Wed, 13 Jan 2021 16:03:38 +0700 Subject: [Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff In-Reply-To: References: <4415144.vXUDI8C0e8@localhost.localdomain> <2119226.vFx2qVVIhK@localhost.localdomain> Message-ID: <3250016.LZWGnKmheA@localhost.localdomain> On Wednesday, January 13, 2021 3:46:46 PM +07 Pratik M. wrote: > Hi, > You do not seem to have done the steps mentioned to use SRIOV (in my #2). > > Do you plan to use SRIOV? If not, you can ignore the crashloop of the > container. Else you can try if the following helps: > # system host-label-assign controller-0 sriov=disabled > > Thanks Sure I have, as you stated they are in my history, though i double checked my history against what you wrote..... and following this guide https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/ aio_simplex_install_kubernetes.html, i find as my command #24 system host-label-assign controller-0 sriovdp=enabled what i do not find is what you wrote "# system host-if-modify controller-0 -c pci-sriov -n sriov0" in my history or in the install guide i followed, so can i ask where is this coming from i dont see it any where in the documentation > > On Tue, Jan 12, 2021 at 7:50 PM wrote: > > On Tuesday, January 12, 2021 8:04:34 PM +07 Pratik M. wrote: > > > Hi, > > > 1. What does your /etc/pcidp/config.json look like? > > > > > > 2. Did you do all these steps? > > > # system host-label-assign controller-0 sriovdp=enabled > > > # system host-if-modify controller-0 -c pci-sriov -n sriov0 > > > > -N > > > > > > > > # system interface-datanetwork-assign controller-0 > > > > > > # system host-unlock > > > > > > Thanks > > > Pratik > > > > history start to finish > > > > 1 ps xa > > > > 2 ip addr > > 3 cat < localhost.yml > > 4 system_mode: simplex > > 5 dns_servers: > > 6 - 8.8.8.8 > > 7 - 8.8.4.4 > > 8 external_oam_subnet: / > > 9 external_oam_gateway_address: > > > > 10 external_oam_floating_address: > > 11 admin_username: admin > > 12 admin_password: > > 13 ansible_become_pass: > > 14 EOF > > 15 vi localhost.yml > > 16 ansible-playbook > > > > /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml > > > > 17 source /etc/platform/openrc > > 18 ip addr > > 19 OAM_IF=eno1 > > 20 system host-if-modify controller-0 $OAM_IF -c platform > > 21 system interface-network-assign controller-0 $OAM_IF oam > > 22 system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org > > 23 system storage-backend-add ceph --confirmed > > 24 system host-label-assign controller-0 sriovdp=enabled > > 25 system host-memory-modify controller-0 0 -1G 100 > > 26 DATA0IF=enp101s0f0 > > 27 DATA1IF=enp101s0f1 > > 28 export NODE=controller-0 > > 29 PHYSNET0='physnet0' > > 30 PHYSNET1='physnet1' > > 31 SPL=/tmp/tmp-system-port-list > > 32 SPIL=/tmp/tmp-system-host-if-list > > 33 system host-port-list ${NODE} --nowrap > ${SPL} > > 34 system host-if-list -a ${NODE} --nowrap > ${SPIL} > > 35 DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') > > 36 DATA1PCIADDR=$(cat $SPL | grep $DATA1IF |awk '{print $8}') > > 37 DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') > > 38 DATA1PORTUUID=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $2}') > > 39 DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') > > 40 DATA1PORTNAME=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print > > $4}') > > 41 DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 > > > > ~ > > DATA0PORTNAME) {print $2}') > > > > 42 DATA1IFUUID=$(cat $SPIL | awk -v DATA1PORTNAME=$DATA1PORTNAME '($12 > > > > ~ > > DATA1PORTNAME) {print $2}') > > > > 43 system datanetwork-add ${PHYSNET0} vlan > > 44 system datanetwork-add ${PHYSNET1} vlan > > 45 system host-if-modify -m 1500 -n data0 -c data ${NODE} > > > > ${DATA0IFUUID} > > > > 46 system host-if-modify -m 1500 -n data1 -c data ${NODE} > > > > ${DATA1IFUUID} > > > > 47 system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} > > > > ${PHYSNET0} > > > > 48 system interface-datanetwork-assign ${NODE} ${DATA1IFUUID} > > > > ${PHYSNET1} > > > > 49 system host-disk-list controller-0 > > 50 system host-disk-list controller-0 | awk '/\/dev\/nvme1n1/{print > > > > $2}' | > > xargs -i system host-stor-add controller-0 {} > > > > 51 system host-disk-list controller-0 | awk '/\/dev\/nvme2n1/{print > > > > $2}' | > > xargs -i system host-stor-add controller-0 {} > > > > 52 system host-label-assign controller-0 > > > > openstack-control-plane=enabled > > > > 53 system host-label-assign controller-0 > > openstack-compute-node=enabled > > 54 system host-label-assign controller-0 openvswitch=enabled > > 55 system host-label-assign controller-0 sriov=enabled > > 56 system modify --vswitch_type ovs-dpdk > > 57 system host-cpu-modify -f vswitch -p0 1 controller-0 > > 58 export NODE=controller-0 > > 59 echo ">>> Getting root disk info" > > 60 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print > > > > $4}') > > > > 61 ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep $ > > > > {ROOT_DISK} | awk '{print $2}') > > > > 62 echo "Root disk: $ROOT_DISK, UUID: $ROOT_DISK_UUID" > > 63 echo ">>>> Configuring nova-local" > > 64 NOVA_SIZE=34 > > 65 NOVA_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol > > > > ${NODE} > > ${ROOT_DISK_UUID} ${NOVA_SIZE}) > > > > 66 NOVA_PARTITION_UUID=$(echo ${NOVA_PARTITION} | grep -ow "| uuid | > > > > [a- > > z0-9\-]* |" | awk '{print $4}') > > > > 67 system host-lvg-add ${NODE} nova-local > > 68 system host-pv-add ${NODE} nova-local ${NOVA_PARTITION_UUID} > > 69 sleep 2 > > 70 system host-memory-list controller-0 > > 71 system host-unlock controller-0 > > 72 system host-memory-modify controller-0 0 -1G 100 > > 73 system host-unlock controller-0 > > 74 system host-memory-modify controller-0 1 -1G 100 > > 75 system host-label-assign controller-0 openvswitch=enabled > > 76 system host-memory-modify -f vswitch -1G 1 compute-0 0 > > 77 system host-memory-modify controller-0 0 -1G 100 > > 78 system host-unlock controller-0 > > 79 system host-memory-modify -f vswitch -1G 1 compute-0 0 > > 80 system host-memory-modify -f vswitch -1G 1 controller-0 0 > > 81 system host-unlock controller-0 > > 82 history > HIST > > > > > > On Tue, Jan 12, 2021 at 1:39 PM wrote: > > > > any idea how to resolve this, was installed from a recent 01/08/2021 > > > > build > > > > > > AIO > > > > Simplex ojn bare metal > > > > > > > > kube-system kube-sriov-device-plugin-amd64-547xh 0/1 > > > > CrashLoopBackOff 4 2m49s > > > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs > > > > kube-sriov-device- > > > > plugin-amd64-547xh --namespace kube-system > > > > error: the server doesn't have a resource type "logs" > > > > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs > > > > kube-sriov-device- > > > > > > plugin-amd64-547xh --namespace kube-system > > > > I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin > > > > Registry > > > > > > Mode > > > > I0112 08:05:19.714707 158061 main.go:44] resource manager reading > > > > configs > > > > > > I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: { > > > > > > > > "resourceList": [ > > > > > > > > ] > > > > > > > > } > > > > I0112 08:05:19.714795 158061 manager.go:106] unmarshalled > > > > ResourceList: > > > > [] > > > > E0112 08:05:19.714801 158061 main.go:51] no resource configuration; > > > > exiting > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From anyrude10 at gmail.com Wed Jan 13 10:07:33 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Wed, 13 Jan 2021 15:37:33 +0530 Subject: [Starlingx-discuss] [Query] StarlingX 4.0 - Storage Network separate from MGMT+Cluster in Bare Metal Standard with Dedicated Storage Model In-Reply-To: References: Message-ID: Hi Team, Can someone help me in regard to the below mail shared. *Query: *Is it possible to have a storage network which is separate from mgmt+cluster networks? So that all the storage traffic passes only through that network Regards Anirudh Gupta On Fri, Jan 8, 2021 at 7:41 PM Anirudh Gupta wrote: > Hi Team, > > I am trying to set up a Bare metal Standard with Dedicated Storage > Installation R4.0 > with > 2 Controllers, 2 Storage Nodes and 2 Worker Nodes. > > > https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage.html > > > > [image: image.png] > > > > As per the Network Diagram, storage nodes are connected to MGMT + Cluster > Networks and all the traffic flows through this network only. > > > https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage_install_kubernetes.html#configure-storage-nodes > > > Even the document suggests to assign the cluster-host network to the MGMT > interface for the storage nodes > > system interface-network-assign $NODE mgmt0 cluster-host > > > Is it possible to have a storage network which is separate from > mgmt+cluster networks? So that all the storage traffic passes only > through that network > > Looking forward for your response. > > Regards > Anirudh Gupta > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 106914 bytes Desc: not available URL: From Bill.Zvonar at windriver.com Wed Jan 13 11:55:14 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Jan 2021 11:55:14 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 13, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210113T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From bruce.e.jones at intel.com Wed Jan 13 15:31:17 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 13 Jan 2021 15:31:17 +0000 Subject: [Starlingx-discuss] TSC meeting minutes Jan 13 2021 Message-ID: * Standing topics - None * Release update and issues * Python3 support * Python2 is EOL for over a year * Transition to P3 was assumed to be covered by the CentOS 8 upgrade - which is now stalled * Several options exist for how to solve this problem but MS-3 for STX 5.0 is coming soon * No one is currently working on this - Bart estimates 60+ weeks of effort * Do we release without this work or wait? * Resolved - we release STX 5.0 as planned and make P3 support an anchor feature for STX 6 * Ceph/Rook changes - need code reviews please! * Frank and Dariush to help get the right folks to review -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 13 16:24:55 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Jan 2021 16:24:55 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 13, 2021) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * got back to green ; build broke last night but seems to have been a networking issue * Gerrit Reviews in Need of Attention * ROOK Ceph https://review.opendev.org/q/topic:%22ceph+containerization%22+status:open * discussed & actions taken on the TSC call * Topics for this Week * CentOS Alternatives - Saul presented * ARs from Previous Meetings * Saul re: RHEL DUP - still considering the best way to go on this ---- will table it at the TSC meeting next week * Open Requests for Help * did not review this week * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 13, 2021 6:55 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Jan 13, 2021) Hi all, reminder of the weekly TSC/Community calls later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210113T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From scott.little at windriver.com Wed Jan 13 21:27:59 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 13 Jan 2021 16:27:59 -0500 Subject: [Starlingx-discuss] cenga mirror download folder broken In-Reply-To: References: Message-ID: <52602f38-1442-a21f-fd80-c1a09acab162@windriver.com> investigating now ... Scott On 2021-01-12 7:56 p.m., Chen, Haochuan Z wrote: > > Hi Scott > > Download folder for all layer is blank now. > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/inputs/downloads/ > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/latest_build/inputs/downloads/ > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/latest_build/inputs/downloads/ > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/inputs/downloads/ > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Jan 13 22:44:43 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 13 Jan 2021 22:44:43 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 13-Jan-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 13-Jan-21 All -- reviews merged since last meeting:  3 All -- bug status -- 18 total - team agrees to defer all low priority LP until the upstreaming effort is completed.  13 LP are WIP against API documentation, which is generated from source code (low priority). Status/questions/opens Ron is starting to look into the upstream/downstream mirroring, which may require some changes to the process we've come up with. Stay tuned.  Config API reviews in progress, this group includes most of the open LP.  Release 5.0 Features We discussed the StarlingX Release Plan sheet for stx.5.0 https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 Listed by the row # in the Google sheet. 3. Rook / Ceph. Doc reviews are in progress.  4. Fault containerization. Per 13Jan release meeting, this will be a partial delivery. Code will be merged but disabled by default. AR Mary ping Gopi about doc changes. 5. FPGA Image Update Orchestration for Distributed Cloud. May require updates/additions to the Node or Host guide (already upstreamed). AR Ron to find where this is documented and ping the technical lead. 6. Automatic Certificate Renewal for DC admin endpoints. May require updates/additions to the Node or Host guide (already upstreamed). AR Ron to find where this is documented and ping the technical lead. 10. Python2 >> Python 3. Unlikely to be doc changes, probably an item to capture in Release Notes. 11. Vault Integration for Secret Management Support. Marked Complete. Security Guide content. Either already upstreamed or in the "delta" content (missed the first upstreaming snapshot). Wind River team will track this. 12. Support for Container Image Signature Validation. Same as above (Complete, already upstreamed or in the "delta", Wind River team will track this.) 13. Platform Service Migration to Cert-Manager - Part 1. Security Guide content. May be partially implemented for STX 5.0. Wind River team will track this. 14. Edge Worker for Industrial Deployments - Part 1. AR Mary ping technical leads about doc changes. 15. SNMP v3 support. Fault Management Guide (already upstreamed). Content has been provided to WR Docs team. Guide needs "delta" updates first, then add new content. Wind River team will track this. 16. Distributed Cloud Scaling (Target: 1000 subclouds). AR Mary ping technical leads about doc changes. 17. Distributed Cloud Orchestration for AIO-DX & Standard Subclouds. AR Mary ping technical leads about doc changes. 18. Secure Device Onboarding (SDO). AR Mary ping technical leads about doc changes. 19-21. Hardware Enablement. Intel Ice-Lake CPU Support, Intel Mt. Bryce eASIC (Pomona Lake) Support, Intel Columbiaville NIC Support. Item for Release Notes, possibly add to "Supported Hardware" (find out where). From allison at openstack.org Wed Jan 13 23:03:19 2021 From: allison at openstack.org (Allison Price) Date: Wed, 13 Jan 2021 17:03:19 -0600 Subject: [Starlingx-discuss] Only a few hours left: 2021 Board elections and Bylaws amendments Message-ID: <89643982-5FB2-433D-95E8-DDFB0DB5119D@openstack.org> Hi everyone, The 2021 Individual Director elections are currently open. All members who are eligible to vote should have received an email ballot earlier this week. You can review the candidates here: https://www.openstack.org/election/2021-individual-director-election/CandidateList . If you are not currently a member of the Open Infrastructure Foundation, you can join here to vote in next year’s elections: https://openinfra.dev/join This year, the election includes a set of amendments to the Foundation’s Bylaws. The amendments were approved unanimously by the Foundation Board in 2020. As a member class, the Individual Members must also approve these amendments. You can find more information in this mailing list post by Jonathan Bryce: http://lists.openstack.org/pipermail/foundation/2021-January/002939.html The deadline to vote is this Friday, January 15 at 1800 UTC / 12pm CST. Please let me know if you have any questions. Allison Allison Price Open Infrastructure Foundation allison at openstack.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jan 14 08:09:31 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 14 Jan 2021 03:09:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1468 - Failure! Message-ID: <1084490999.970.1610611771798.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1468 Status: Failure Timestamp: 20210114T054542Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210114T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210114T053000Z DOCKER_BUILD_ID: jenkins-master-20210114T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210114T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210114T053000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From alexandru.dimofte at intel.com Thu Jan 14 08:20:44 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 14 Jan 2021 08:20:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210112T160355Z Message-ID: Sanity Test from 2021-January-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210112T160355Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210112T160355Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8408 bytes Desc: image003.png URL: From scott.little at windriver.com Thu Jan 14 13:30:44 2021 From: scott.little at windriver.com (Scott Little) Date: Thu, 14 Jan 2021 08:30:44 -0500 Subject: [Starlingx-discuss] cenga mirror download folder broken In-Reply-To: <52602f38-1442-a21f-fd80-c1a09acab162@windriver.com> References: <52602f38-1442-a21f-fd80-c1a09acab162@windriver.com> Message-ID: The problem has been fixed. Scott On 2021-01-13 4:27 p.m., Scott Little wrote: > > investigating now ... > > Scott > > > > On 2021-01-12 7:56 p.m., Chen, Haochuan Z wrote: >> >> Hi Scott >> >> Download folder for all layer is blank now. >> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/inputs/downloads/ >> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/latest_build/inputs/downloads/ >> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/latest_build/inputs/downloads/ >> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/inputs/downloads/ >> >> Thanks! >> >> Martin, Chen >> >> IOTG, Software Engineer >> >> 021-61164330 >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu Jan 14 13:46:11 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 14 Jan 2021 13:46:11 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210114T023336Z Message-ID: Sanity Test from 2021-January-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210114T023336Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210114T023336Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From build.starlingx at gmail.com Fri Jan 15 03:05:17 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 14 Jan 2021 22:05:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1470 - Failure! Message-ID: <1624326053.974.1610679918362.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1470 Status: Failure Timestamp: 20210115T024600Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210115T023142Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210115T023142Z DOCKER_BUILD_ID: jenkins-master-distro-20210115T023142Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210115T023142Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210115T023142Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From sanathukumar14 at gmail.com Fri Jan 15 08:51:05 2021 From: sanathukumar14 at gmail.com (sanath kumar) Date: Fri, 15 Jan 2021 14:21:05 +0530 Subject: [Starlingx-discuss] Error in Installing StarlingX Message-ID: Hell StarlingX Team, I was getting an error while doing the Provision Setup. Below is the link which has the log-files of Provision setup. *https://drive.google.com/drive/folders/1Pl5MbF8KvHG47fwqC7H6HVf-_0g1_o3c?usp=sharing * *Please help me out, will be eagerly waiting for your reply* Regards, Sanath Kumar +91 8971546076 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat Jan 16 08:29:15 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 16 Jan 2021 08:29:15 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210115T030459Z Message-ID: Sanity Test from 2021-January-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210115T030459Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210115T030459Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From sinlam at hotmail.com Sat Jan 16 13:27:37 2021 From: sinlam at hotmail.com (Sin Lam Tan) Date: Sat, 16 Jan 2021 13:27:37 +0000 Subject: [Starlingx-discuss] Starlingx integration with Open Source Mano (OSM) Message-ID: Hi, May I know anyone has done the integration of Starlingx with OSM? Currently I install Starlingx inside a VM (IP: 10.10.10.3), and install OSM in another VM (IP: 10.10.10.4). Both VM are connected using management network 10.10.10.x. In the Starlingx, I install Openstack using helm-chart and I am able to access Openstack Dashboard from http://10.10.10.3:31000/ In the OSM, I link Openstack to OSM as a VIM using the command in OSM: osm vim-create --name openstack-starlingx --user admin --password St8rlingX* --auth_url http://10.10.10.3:5000/v3 --tenant admin --account_type openstack --config='{security_groups: default, availability_zone: nova, keypair: test, insecure: true}' I would like to use OSM to deploy VM using OSM template. Currently I use the sample hackfest_basic_ns & hackfest_basic_vnf for testing. During "Instantiate NS", I got an error as below: Operation: INSTANTIATING.f0055db9-fc88-460e-a012-dcf66da7b951, Stage 2/5: deployment of KDUs, VMs and execution environments. Detail: Deploying at VIM: VIM Exception EndpointNotFound: public endpoint for image service not found. Rollback successful. I don't know how to fix this issue, any suggestion is appreciated. Thank you! Regards, Sinlam -------------- next part -------------- An HTML attachment was scrubbed... URL: From ch.huang789 at advantech.com.tw Sat Jan 16 13:42:48 2021 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Sat, 16 Jan 2021 13:42:48 +0000 Subject: [Starlingx-discuss] Does STX support ovs-tcpdump? Message-ID: <9d8cf31b1dd64cb0af87f3cca3871103@taipei09.ADVANTECH.CORP> Dear Sir: Can someone show me how to run ovs-tcpdump in StarlingX 4.0? Or it doesn’t support ovs-tcpdump, yet. 1. In activate controller with error [sysadmin at controller-1 ~(keystone_admin)]$ sudo find / -name ovs-tcpdump /run/containerd/io.containerd.runtime.v2.task/k8s.io/c14cfcb3b83856841fcf5e6fc797648286fcef7e3345ac5fe7fc40b53f0c81c2/rootfs/usr/bin/ovs-tcpdump /run/containerd/io.containerd.runtime.v2.task/k8s.io/a996ab0c567e0e80554cf1c1fab7c982c8450746bb5f38bc565a387eccf44308/rootfs/usr/bin/ovs-tcpdump /var/lib/docker/io.containerd.snapshotter.v1.overlayfs/snapshots/344/fs/usr/bin/ovs-tcpdump [sysadmin at controller-1 ~(keystone_admin)]$ sudo /run/containerd/io.containerd.runtime.v2.task/k8s.io/c14cfcb3b83856841fcf5e6fc797648286fcef7e3345ac5fe7fc40b53f0c81c2/rootfs/usr/bin/ovs-tcpdump ERROR: Please install the correct Open vSwitch python support libraries (version 2.11.0). Alternatively, check that your PYTHONPATH is pointing to the correct location. 2. Run in neutron-ovs-agent with error [sysadmin at controller-1 ~(keystone_admin)]$ kubectl get pods -A | grep ovs openstack neutron-ovs-agent-controller-0-937646f6-7cgrn 1/1 Running 0 22d openstack neutron-ovs-agent-controller-1-cab72f56-8f5zl 1/1 Running 0 22d [sysadmin at controller-1 ~(keystone_admin)]$ kubectl exec -it neutron-ovs-agent-controller-0-937646f6-7cgrn -n openstack -- /bin/bash [root at controller-0 /]# sudo find / -name ovs-tcpdump find: File system loop detected; '/run/containerd/io.containerd.runtime.v2.task/k8s.io/ce212ae2c14881b52cae720f682c584e68bf1855bb59156c9795ffc0fd4e7940/rootfs' is part of the same file system loop as '/'. /run/containerd/io.containerd.runtime.v2.task/k8s.io/3c2f65fae028b7432d0759ede3d6a1b6c633ca9e2886a72ab26526d8cf8dbce8/rootfs/usr/bin/ovs-tcpdump [root at controller-0 /]# /run/containerd/io.containerd.runtime.v2.task/k8s.io/3c2f65fae028b7432d0759ede3d6a1b6c633ca9e2886a72ab26526d8cf8dbce8/rootfs/usr/bin/ovs-tcpdump Traceback (most recent call last): File "/run/containerd/io.containerd.runtime.v2.task/k8s.io/3c2f65fae028b7432d0759ede3d6a1b6c633ca9e2886a72ab26526d8cf8dbce8/rootfs/usr/bin/ovs-tcpdump", line 27, in import netifaces ImportError: No module named netifaces 3. Install netifaces in neutron-ovs-agent with error: [root at controller-0 /]# yum install netifaces Loaded plugins: fastestmirror, ovl Cannot open logfile /var/log/yum.log ovl: Error while doing RPMdb copy-up: [Errno 30] Read-only file system: '/var/lib/rpm/.dbenv.lock' [Errno 30] Read-only file system: '/var/cache/yum/x86_64/7/base/mirrorlist.txt' Regards, C.H. Huang Technical Service for Advantech Cloud-IoT -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sun Jan 17 03:58:35 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 17 Jan 2021 03:58:35 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 13/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.5.0 - Status of Milestone-2 - Dec 18 (retrospective view) - Will send the email to declare the milestone retroactively -- as per the minutes from the Dec 16 meeting - Status of Milestone-3 - Features - Feature List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - OS / Python3 - No plan to do anything related to CentOS8 / OS migration/alternatives in stx.5.0 as the timeline is too short - The only item that needs serious consideration is the migration to python3 - Not much progress on python3 yet; currently being discussed at the distro.other meeting. - No resources available to do the work as the current team is focused on investigating CentOS alternatives. - Two options: - Option1: Do all at once in a branch - Option2: Do one service at a time and handle backward compatiblity - Leaning towards Option2 - Effort: ~60 weeks (rough estimate by Bart Wensley) - Continue conversation in the TSC / Community meeting on Jan 13 - Update: Based on discussion in the TSC / Community meeting on Jan 13, this will be targeted for stx.6.0 - Ceph Rook - Reviews are still going slow; no progress over the weeeks - Need to get commitment from the core reviewers to move this forward. - Austin will send a direct email to the core reviewers needed - Fault Containerization - Likely a partial delivery due to python3 challenges. Code will be merged, but disabled by default. - Feature Test - No concerns raised on feature test - Regression Test - Not started. Plan to start in early Feb From Ghada.Khalil at windriver.com Sun Jan 17 04:12:36 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 17 Jan 2021 04:12:36 +0000 Subject: [Starlingx-discuss] stx.5.0 Milestone-2 Declared Message-ID: Hello all, Based on the stx.5.0 release review on Dec 16/2020, we are declaring Milestone-2 retroactively with a date of Dec 18/2020/ Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables A list of proposed features is available at: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 Thank you to all community members who helped achieve this milestone. Regards, Ghada & the stx release team From alexandru.dimofte at intel.com Sun Jan 17 16:57:05 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 17 Jan 2021 16:57:05 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210116T023301Z Message-ID: Sanity Test from 2021-January-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210116T023301Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210116T023301Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From austin.sun at intel.com Mon Jan 18 01:11:43 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 18 Jan 2021 01:11:43 +0000 Subject: [Starlingx-discuss] Starlingx integration with Open Source Mano (OSM) In-Reply-To: References: Message-ID: Hi Sin: Which stx version do you use ? I don't know OSM, but the openstack auth_url should be issue. In stx 3.0 and later , the openstack keystone services endpoint should be http://keystone.openstack.svc.cluster.local/v3 , http://10.10.10.3:5000/v3 is for host services , not for openstack services. Hope this info is useful for you . you can refer [1] for more openstack on stx more info [1] https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/access.html#configure-helm-endpoint-domain Thanks. BR Austin Sun. From: Sin Lam Tan Sent: Saturday, January 16, 2021 9:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Starlingx integration with Open Source Mano (OSM) Hi, May I know anyone has done the integration of Starlingx with OSM? Currently I install Starlingx inside a VM (IP: 10.10.10.3), and install OSM in another VM (IP: 10.10.10.4). Both VM are connected using management network 10.10.10.x. In the Starlingx, I install Openstack using helm-chart and I am able to access Openstack Dashboard from http://10.10.10.3:31000/ In the OSM, I link Openstack to OSM as a VIM using the command in OSM: osm vim-create --name openstack-starlingx --user admin --password St8rlingX* --auth_url http://10.10.10.3:5000/v3 --tenant admin --account_type openstack --config='{security_groups: default, availability_zone: nova, keypair: test, insecure: true}' I would like to use OSM to deploy VM using OSM template. Currently I use the sample hackfest_basic_ns & hackfest_basic_vnf for testing. During "Instantiate NS", I got an error as below: Operation: INSTANTIATING.f0055db9-fc88-460e-a012-dcf66da7b951, Stage 2/5: deployment of KDUs, VMs and execution environments. Detail: Deploying at VIM: VIM Exception EndpointNotFound: public endpoint for image service not found. Rollback successful. I don't know how to fix this issue, any suggestion is appreciated. Thank you! Regards, Sinlam -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Jan 18 12:26:23 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 18 Jan 2021 12:26:23 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 01/19 Message-ID: Hi All: As planned , we will have openstack distro meeting from tomorrow. The topic will be : - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Jan 18 12:37:23 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 18 Jan 2021 07:37:23 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! In-Reply-To: <280785581.953.1610427875187.JavaMail.javamailuser@localhost> References: <280785581.953.1610427875187.JavaMail.javamailuser@localhost> Message-ID: <1734468923.979.1610973443714.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 316 Status: Still Failing Timestamp: 20210118T093215Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210118T053001Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20210118T053001Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs PUBLISH_TIMESTAMP: 20210118T053001Z FLOCK_VERSION: master-centos-stable-20210118T053001Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210118T053001Z BUILD_STREAM: stable REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Jan 18 12:37:25 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 18 Jan 2021 07:37:25 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images - Build # 287 - Failure! Message-ID: <108246360.982.1610973446075.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 287 Status: Failure Timestamp: 20210118T091323Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210118T053001Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs MASTER_BUILD_NUMBER: 802 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic PUBLISH_TIMESTAMP: 20210118T053001Z DOCKER_BUILD_ID: jenkins-master-20210118T053001Z-builder TIMESTAMP: 20210118T053001Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/outputs From build.starlingx at gmail.com Mon Jan 18 12:37:27 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 18 Jan 2021 07:37:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 802 - Failure! Message-ID: <1470129155.985.1610973448545.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 802 Status: Failure Timestamp: 20210118T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From anyrude10 at gmail.com Mon Jan 18 12:46:19 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Mon, 18 Jan 2021 18:16:19 +0530 Subject: [Starlingx-discuss] [Query] StarlingX 4.0 - Storage Network separate from MGMT+Cluster in Bare Metal Standard with Dedicated Storage Model In-Reply-To: References: Message-ID: Gentle Reminder !!!!! Hi Team, Can someone help me in regard to the below mail shared. *Queris: * 1. Is it possible to have a storage network which is separate from mgmt+cluster networks? So that all the storage traffic passes only through that network 2. Is there a way to separate client traffic from Storage cluster traffic (running on Mgmt+Cluster Host NW) if we enable Ceph Metadata server on Controller nodes? Regards Anirudh Gupta On Wed, Jan 13, 2021 at 3:37 PM Anirudh Gupta wrote: > Hi Team, > > Can someone help me in regard to the below mail shared. > > *Query: *Is it possible to have a storage network which is separate from > mgmt+cluster networks? So that all the storage traffic passes only > through that network > > Regards > Anirudh Gupta > > On Fri, Jan 8, 2021 at 7:41 PM Anirudh Gupta wrote: > >> Hi Team, >> >> I am trying to set up a Bare metal Standard with Dedicated Storage >> Installation R4.0 >> with >> 2 Controllers, 2 Storage Nodes and 2 Worker Nodes. >> >> >> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage.html >> >> >> >> [image: image.png] >> >> >> >> As per the Network Diagram, storage nodes are connected to MGMT + >> Cluster Networks and all the traffic flows through this network only. >> >> >> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage_install_kubernetes.html#configure-storage-nodes >> >> >> Even the document suggests to assign the cluster-host network to the >> MGMT interface for the storage nodes >> >> system interface-network-assign $NODE mgmt0 cluster-host >> >> >> Is it possible to have a storage network which is separate from >> mgmt+cluster networks? So that all the storage traffic passes only >> through that network >> >> Looking forward for your response. >> >> Regards >> Anirudh Gupta >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 106914 bytes Desc: not available URL: From pvmpublic at gmail.com Mon Jan 18 14:22:33 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Mon, 18 Jan 2021 19:52:33 +0530 Subject: [Starlingx-discuss] [Query] StarlingX 4.0 - Storage Network separate from MGMT+Cluster in Bare Metal Standard with Dedicated Storage Model In-Reply-To: References: Message-ID: Hi, Reading the following, a dedicated storage-only netowrk does not seem to be possible for the scenario you mention: https://docs.starlingx.io/planning/kubernetes/networks-for-a-system-with-dedicated-storage.html https://docs.starlingx.io/planning/kubernetes/the-storage-network.html Thanks and Regards On Mon, Jan 18, 2021 at 6:18 PM Anirudh Gupta wrote: > Gentle Reminder !!!!! > > Hi Team, > > Can someone help me in regard to the below mail shared. > > *Queris: * > 1. Is it possible to have a storage network which is separate from > mgmt+cluster networks? So that all the storage traffic passes only > through that network > 2. Is there a way to separate client traffic from Storage cluster traffic > (running on Mgmt+Cluster Host NW) if we enable Ceph Metadata server on > Controller nodes? > > Regards > Anirudh Gupta > > On Wed, Jan 13, 2021 at 3:37 PM Anirudh Gupta wrote: > >> Hi Team, >> >> Can someone help me in regard to the below mail shared. >> >> *Query: *Is it possible to have a storage network which is separate from >> mgmt+cluster networks? So that all the storage traffic passes only >> through that network >> >> Regards >> Anirudh Gupta >> >> On Fri, Jan 8, 2021 at 7:41 PM Anirudh Gupta wrote: >> >>> Hi Team, >>> >>> I am trying to set up a Bare metal Standard with Dedicated Storage >>> Installation R4.0 >>> with >>> 2 Controllers, 2 Storage Nodes and 2 Worker Nodes. >>> >>> >>> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage.html >>> >>> >>> >>> [image: image.png] >>> >>> >>> >>> As per the Network Diagram, storage nodes are connected to MGMT + >>> Cluster Networks and all the traffic flows through this network only. >>> >>> >>> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage_install_kubernetes.html#configure-storage-nodes >>> >>> >>> Even the document suggests to assign the cluster-host network to the >>> MGMT interface for the storage nodes >>> >>> system interface-network-assign $NODE mgmt0 cluster-host >>> >>> >>> Is it possible to have a storage network which is separate from >>> mgmt+cluster networks? So that all the storage traffic passes only >>> through that network >>> >>> Looking forward for your response. >>> >>> Regards >>> Anirudh Gupta >>> >>> _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 106914 bytes Desc: not available URL: From openinfradn at gmail.com Mon Jan 18 15:21:38 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 18 Jan 2021 20:51:38 +0530 Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Message-ID: Hi, Is it possible to deploy StarlingX without the Kubernetes support? Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Jan 19 00:02:58 2021 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 19 Jan 2021 00:02:58 +0000 Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. In-Reply-To: References: Message-ID: Hi Danishka, There is NO such one dedicated flag to enable or disable K8s during the system deployment. Though, technically you can trim codes to make it. Roughly STX has done some work around K8s installation/configuration/deployment. Mostly the related code is existing in the following projects: starlingx/ansible-playbooks, starlingx/config, starlingx/stx-puppet, starlingx/ha, and starlingx/nfv. BTW: what use cases or production scenarios make you have such a requirements or incentive? Regards, Yong From: open infra Date: Monday, January 18, 2021 at 11:24 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Hi, Is it possible to deploy StarlingX without the Kubernetes support? Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 19 00:36:22 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 18 Jan 2021 19:36:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1482 - Failure! Message-ID: <1230257874.991.1611016582771.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1482 Status: Failure Timestamp: 20210119T001539Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210119T000110Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210119T000110Z DOCKER_BUILD_ID: jenkins-master-distro-20210119T000110Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210119T000110Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210119T000110Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From austin.sun at intel.com Tue Jan 19 01:09:35 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 19 Jan 2021 01:09:35 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! In-Reply-To: <1734468923.979.1610973443714.JavaMail.javamailuser@localhost> References: <280785581.953.1610427875187.JavaMail.javamailuser@localhost> <1734468923.979.1610973443714.JavaMail.javamailuser@localhost> Message-ID: Hi All: From log [1] Build stx-oidc-client, it seems some go module can not get successfully , I'm not sure if it is network stability issue or not. Log: get "golang.org/x/net/context/ctxhttp": verifying non-authoritative meta tag golang.org/x/net (download) The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs/jenkins-STX_build_docker_flock_images-316.log.html Thanks. BR Austin Sun. -----Original Message----- From: build.starlingx at gmail.com Sent: Monday, January 18, 2021 8:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! Project: STX_build_docker_flock_images Build #: 316 Status: Still Failing Timestamp: 20210118T093215Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210118T053001Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20210118T053001Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs PUBLISH_TIMESTAMP: 20210118T053001Z FLOCK_VERSION: master-centos-stable-20210118T053001Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210118T053001Z BUILD_STREAM: stable REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/outputs REGISTRY: docker.io From haridhar.kalvala at intel.com Tue Jan 19 04:39:40 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 19 Jan 2021 04:39:40 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. In-Reply-To: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> References: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> Message-ID: Hello All, In continuation to below, further I am facing new issues w.r.t python versions compatibility. Requests for some inputs here on how can I solve this ? /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() Complete pod logs : + COMMAND=start + start ++ python -c 'from distutils.sysconfig import get_python_lib; print(get_python_lib())' + SITE_PACKAGES_ROOT=/var/lib/openstack/lib/python3.6/site-packages + rm -f /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + ln -s /etc/openstack-dashboard/local_settings /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + chown -R horizon /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/ + a2enmod headers + a2enmod rewrite + a2dismod status /tmp/horizon.sh: line 17: :wq: command not found + sed -i 's/LoadModule status_module/#LoadModule status_module/' /etc/httpd/conf.modules.d/00-base.conf + '[' -f /etc/apache2/envvars ']' + rm -rf /var/run/apache2/htcacheclean + APACHE_DIR=apache2 + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled ']' + unset PANEL_DIR + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled ']' + unset PANEL_DIR + type -p gettext + cd /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard + /tmp/manage.py compilemessages /var/lib/openstack/lib64/python3.6/site-packages/scss/compiler.py:1430: DeprecationWarning: invalid escape sequence \: result = tb * (i + nesting) + "@media -sass-debug-info{filename{font-family:file\:\/\/%s}line{font-family:\\00003%s}}" % (filename, lineno) + nl /var/lib/openstack/lib64/python3.6/site-packages/scss/cssdefs.py:516: DeprecationWarning: invalid escape sequence \s ''', re.VERBOSE) /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) Traceback (most recent call last): File "/tmp/manage.py", line 19, in execute_from_command_line(sys.argv) File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/var/lib/openstack/lib/python3.6/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 994, in _gcd_import File "", line 971, in _find_and_load File "", line 955, in _find_and_load_unlocked File "", line 665, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in class AbstractBaseUser(models.Model): File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 36, in raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__) django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3. Regards, Haridhar Kalvala From: Hu, Yong Sent: Monday, January 11, 2021 1:58 PM To: Kalvala, Haridhar ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" > Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Bailey, Henry Albert (Al)" >, "Penney, Don" >, "Miller, Frank" >, "Mukherjee, Sanjay K" >, "Bhat, Gopalkrishna" > Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Haiqing.Bai at windriver.com Tue Jan 19 06:12:36 2021 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Tue, 19 Jan 2021 06:12:36 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. In-Reply-To: References: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> Message-ID: This is py3 upgrade issue. Maybe you should change the code from “inspect.getargspec()” to “inspect.getfullargspec()”. I once fixed the same kind of issue of centos8 on stx/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py: line 60 distributedcloud-client$ git diff distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py diff --git a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py index d40d6ee..e59f52f 100644 --- a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py +++ b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py @@ -57,7 +57,7 @@ def validate_args(fn, *args, **kwargs): :param arg: the positional arguments supplied :param kwargs: the keyword arguments supplied """ - argspec = inspect.getargspec(fn) + argspec = inspect.getfullargspec(fn) num_defaults = len(argspec.defaults or []) B,R Haiqing Bai From: Kalvala, Haridhar Sent: Tuesday, January 19, 2021 12:40 PM To: Hu, Yong ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello All, In continuation to below, further I am facing new issues w.r.t python versions compatibility. Requests for some inputs here on how can I solve this ? /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() Complete pod logs : + COMMAND=start + start ++ python -c 'from distutils.sysconfig import get_python_lib; print(get_python_lib())' + SITE_PACKAGES_ROOT=/var/lib/openstack/lib/python3.6/site-packages + rm -f /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + ln -s /etc/openstack-dashboard/local_settings /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + chown -R horizon /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/ + a2enmod headers + a2enmod rewrite + a2dismod status /tmp/horizon.sh: line 17: :wq: command not found + sed -i 's/LoadModule status_module/#LoadModule status_module/' /etc/httpd/conf.modules.d/00-base.conf + '[' -f /etc/apache2/envvars ']' + rm -rf /var/run/apache2/htcacheclean + APACHE_DIR=apache2 + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled ']' + unset PANEL_DIR + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled ']' + unset PANEL_DIR + type -p gettext + cd /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard + /tmp/manage.py compilemessages /var/lib/openstack/lib64/python3.6/site-packages/scss/compiler.py:1430: DeprecationWarning: invalid escape sequence \: result = tb * (i + nesting) + "@media -sass-debug-info{filename{font-family:file\:\/\/%s}line{font-family:\\00003%s}}" % (filename, lineno) + nl /var/lib/openstack/lib64/python3.6/site-packages/scss/cssdefs.py:516: DeprecationWarning: invalid escape sequence \s ''', re.VERBOSE) /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) Traceback (most recent call last): File "/tmp/manage.py", line 19, in execute_from_command_line(sys.argv) File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/var/lib/openstack/lib/python3.6/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 994, in _gcd_import File "", line 971, in _find_and_load File "", line 955, in _find_and_load_unlocked File "", line 665, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in class AbstractBaseUser(models.Model): File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 36, in raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__) django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3. Regards, Haridhar Kalvala From: Hu, Yong > Sent: Monday, January 11, 2021 1:58 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) >; Penney, Don >; Miller, Frank >; Mukherjee, Sanjay K >; Bhat, Gopalkrishna > Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" > Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Bailey, Henry Albert (Al)" >, "Penney, Don" >, "Miller, Frank" >, "Mukherjee, Sanjay K" >, "Bhat, Gopalkrishna" > Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 19 12:13:50 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 19 Jan 2021 12:13:50 +0000 Subject: [Starlingx-discuss] Cancelled today: bi-weekly containerization meeting Message-ID: StarlingX community: My apologies but I need to cancel today's planned containerization meeting. If anyone has any requests regarding containerization please use the mailing list. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 19 13:06:56 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 19 Jan 2021 13:06:56 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project In-Reply-To: References: Message-ID: Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:08 PM To: Qian, Bin ; 'Kung, John' ; 'Bart Wensley' ; 'MacDonald, Eric' ; 'Waines, Greg' ; 'Poncea, Ovidiu' Cc: 'starlingx-discuss at lists.starlingx.io' ; Sun, Austin ; Hu, Yong Subject: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 19 14:16:17 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 19 Jan 2021 14:16:17 +0000 Subject: [Starlingx-discuss] MoM StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 01/19 Message-ID: Hi All: Thanks join the call. 01/19/2021 Meeting: - Stx 5.0 MS2 declared. - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1879018 --- will check w/ develop https://bugs.launchpad.net/starlingx/+bug/1888178 --- cannot reproduce in develop side https://bugs.launchpad.net/starlingx/+bug/1888300 --- close this aligned w/ owner https://bugs.launchpad.net/starlingx/+bug/1904635 --- wait for review https://bugs.launchpad.net/starlingx/+bug/1887677 --- Fix merged --- Open No Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Tue Jan 19 06:19:46 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 19 Jan 2021 06:19:46 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. In-Reply-To: References: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> Message-ID: Thank you Haiqing. Yeah, But this is part of scss python package tool(Django-pyscss etc may also need to change) which is used by many others modules which are python2 compiled. Is there any way to specify to use particular use wheel for one module ? Regards, Haridhar Kalvala From: Bai, Haiqing Sent: Tuesday, January 19, 2021 11:43 AM To: Kalvala, Haridhar ; Hu, Yong ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: RE: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. This is py3 upgrade issue. Maybe you should change the code from “inspect.getargspec()” to “inspect.getfullargspec()”. I once fixed the same kind of issue of centos8 on stx/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py: line 60 distributedcloud-client$ git diff distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py diff --git a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py index d40d6ee..e59f52f 100644 --- a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py +++ b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py @@ -57,7 +57,7 @@ def validate_args(fn, *args, **kwargs): :param arg: the positional arguments supplied :param kwargs: the keyword arguments supplied """ - argspec = inspect.getargspec(fn) + argspec = inspect.getfullargspec(fn) num_defaults = len(argspec.defaults or []) B,R Haiqing Bai From: Kalvala, Haridhar Sent: Tuesday, January 19, 2021 12:40 PM To: Hu, Yong ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello All, In continuation to below, further I am facing new issues w.r.t python versions compatibility. Requests for some inputs here on how can I solve this ? /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() Complete pod logs : + COMMAND=start + start ++ python -c 'from distutils.sysconfig import get_python_lib; print(get_python_lib())' + SITE_PACKAGES_ROOT=/var/lib/openstack/lib/python3.6/site-packages + rm -f /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + ln -s /etc/openstack-dashboard/local_settings /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + chown -R horizon /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/ + a2enmod headers + a2enmod rewrite + a2dismod status /tmp/horizon.sh: line 17: :wq: command not found + sed -i 's/LoadModule status_module/#LoadModule status_module/' /etc/httpd/conf.modules.d/00-base.conf + '[' -f /etc/apache2/envvars ']' + rm -rf /var/run/apache2/htcacheclean + APACHE_DIR=apache2 + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled ']' + unset PANEL_DIR + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled ']' + unset PANEL_DIR + type -p gettext + cd /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard + /tmp/manage.py compilemessages /var/lib/openstack/lib64/python3.6/site-packages/scss/compiler.py:1430: DeprecationWarning: invalid escape sequence \: result = tb * (i + nesting) + "@media -sass-debug-info{filename{font-family:file\:\/\/%s}line{font-family:\\00003%s}}" % (filename, lineno) + nl /var/lib/openstack/lib64/python3.6/site-packages/scss/cssdefs.py:516: DeprecationWarning: invalid escape sequence \s ''', re.VERBOSE) /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) Traceback (most recent call last): File "/tmp/manage.py", line 19, in execute_from_command_line(sys.argv) File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/var/lib/openstack/lib/python3.6/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 994, in _gcd_import File "", line 971, in _find_and_load File "", line 955, in _find_and_load_unlocked File "", line 665, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in class AbstractBaseUser(models.Model): File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 36, in raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__) django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3. Regards, Haridhar Kalvala From: Hu, Yong > Sent: Monday, January 11, 2021 1:58 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) >; Penney, Don >; Miller, Frank >; Mukherjee, Sanjay K >; Bhat, Gopalkrishna > Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" > Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Bailey, Henry Albert (Al)" >, "Penney, Don" >, "Miller, Frank" >, "Mukherjee, Sanjay K" >, "Bhat, Gopalkrishna" > Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 19 13:02:50 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 19 Jan 2021 13:02:50 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' ; 'Bart Wensley' ; 'Church, Robert' ; 'Chris Friesen' ; 'Penney, Don' ; 'Kung, John' ; 'Waines, Greg' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; 'starlingx-discuss at lists.starlingx.io' Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 19 13:05:51 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 19 Jan 2021 13:05:51 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in stx-puppet project In-Reply-To: References: Message-ID: Hi folks Thank Bob, Penney and AL review for stx-puppet project. I update comment and welcome more review. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:03 PM To: 'Bailey, Henry Albert (Al)' ; 'Bart Wensley' ; 'Church, Robert' ; 'Chris Friesen' ; 'Penney, Don' ; 'Kung, John' ; 'Waines, Greg' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: review patch to enable rook-ceph in stx-puppet project + Greg Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:00 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in stx-puppet project Hi folks Please review my patch to enable rook-ceph in stx-puppet project. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 19 14:58:09 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 19 Jan 2021 20:28:09 +0530 Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. In-Reply-To: References: Message-ID: Hi Yong. On Tue, Jan 19, 2021 at 5:33 AM Hu, Yong wrote: > Hi Danishka, > > There is NO such one dedicated flag to enable or disable K8s during the > system deployment. > > Though, technically you can trim codes to make it. Roughly STX has done > some work around K8s installation/configuration/deployment. > > Mostly the related code is existing in the following projects: > starlingx/ansible-playbooks, starlingx/config, starlingx/stx-puppet, > starlingx/ha, and starlingx/nfv. > Thanks for the information. > > > BTW: what use cases or production scenarios make you have such a > requirements or incentive? > I just asked to understand though I have no such use case. To be honest I am new to both OpenStack and StarlingX (even I heard about startling few days ago.) Before installing StarlingX I am looking into available options and best practises. I have a few questions that not related to the subject of the original mail. Should I deploy Openstack before installing StarlingX or StartlingX itself deploy the required modules of Openstack? Does StarlingX support CentOS Stream as the host OS? Is there any specific performance tunning guide available for hostOS and VMs? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Tue Jan 19 15:55:47 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Tue, 19 Jan 2021 22:55:47 +0700 Subject: [Starlingx-discuss] StarlingX support / long term / CentOS 8 Message-ID: <2004540.9o76ZdvQCi@localhost.localdomain> so curious as the question has come up by the water cooler :) long term support for StarlingX v5 .. based on CentOS 7 / kernel 4.x moving to CentOS 8? or ? commercial support available from ? redhat ? wind river ? is there a long term support plan ?? From bruce.e.jones at intel.com Tue Jan 19 16:16:06 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 19 Jan 2021 16:16:06 +0000 Subject: [Starlingx-discuss] StarlingX support / long term / CentOS 8 In-Reply-To: <2004540.9o76ZdvQCi@localhost.localdomain> References: <2004540.9o76ZdvQCi@localhost.localdomain> Message-ID: Our plan for StarlingX was to move to CentOS 8, in fact a lot of the work has already been done in a feature branch. However RH's announcement impacts that work - we rely on upstream OS vendors for fixes and CVE issue resolution and RH will not be providing LTS for CentOS 8. We have several options - staying on CentOS 7 (but with the current 4.x kernel) is one of them. There is work in progress in the community to enable StarlingX on Open Embedded. There are other options under discussion but we as a community have not closed on our direction. AFAIK Red Hat does not provide commercial support for StarlingX. Wind River has a commercial product based on StarlingX. I suggest you contact them directly for any questions about it. brucej -----Original Message----- From: lists at optimcloud.com Sent: Tuesday, January 19, 2021 7:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX support / long term / CentOS 8 so curious as the question has come up by the water cooler :) long term support for StarlingX v5 .. based on CentOS 7 / kernel 4.x moving to CentOS 8? or ? commercial support available from ? redhat ? wind river ? is there a long term support plan ?? _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From lists at optimcloud.com Tue Jan 19 17:38:03 2021 From: lists at optimcloud.com (lists at optimcloud.com) Date: Wed, 20 Jan 2021 00:38:03 +0700 Subject: [Starlingx-discuss] StarlingX support / long term / CentOS 8 In-Reply-To: References: <2004540.9o76ZdvQCi@localhost.localdomain> Message-ID: <2120262.vFx2qVVIhK@localhost.localdomain> On Tuesday, January 19, 2021 11:16:06 PM +07 Jones, Bruce E wrote: > We have several options - staying on CentOS 7 (but with the current 4.x > kernel) is one of them what about the potential to move to say Fedora Server 33, or CoreOS ..... or even RedHat itself. curious if it would be possible to build a stx iso based off CoreOS From scott.little at windriver.com Tue Jan 19 19:05:08 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 19 Jan 2021 14:05:08 -0500 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! In-Reply-To: References: <280785581.953.1610427875187.JavaMail.javamailuser@localhost> <1734468923.979.1610973443714.JavaMail.javamailuser@localhost> Message-ID: Build 317 was good.  It was fixed by .... https://review.opendev.org/c/starlingx/oidc-auth-armada-app/+/771051 Thanks Teresa. Scott On 2021-01-18 8:09 p.m., Sun, Austin wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Hi All: > From log [1] > Build stx-oidc-client, it seems some go module can not get successfully , I'm not sure if it is network stability issue or not. > > > Log: > get "golang.org/x/net/context/ctxhttp": verifying non-authoritative meta tag > golang.org/x/net (download) > The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 > > > [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs/jenkins-STX_build_docker_flock_images-316.log.html > > > Thanks. > BR > Austin Sun. > -----Original Message----- > From: build.starlingx at gmail.com > Sent: Monday, January 18, 2021 8:37 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! > > Project: STX_build_docker_flock_images > Build #: 316 > Status: Still Failing > Timestamp: 20210118T093215Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs > -------------------------------------------------------------------------------- > Parameters > > WEB_HOST: mirror.starlingx.cengn.ca > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210118T053001Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master/cgcs-root > BASE_VERSION: master-stable-20210118T053001Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs > REGISTRY_USERID: slittlewrs > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs > PUBLISH_TIMESTAMP: 20210118T053001Z > FLOCK_VERSION: master-centos-stable-20210118T053001Z > WEB_HOST_PORT: 80 > PREFIX: master > TIMESTAMP: 20210118T053001Z > BUILD_STREAM: stable > REGISTRY_ORG: slittlewrs > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/outputs > REGISTRY: docker.io > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Jan 20 02:06:42 2021 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 20 Jan 2021 02:06:42 +0000 Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. In-Reply-To: References: Message-ID: See my comments for your further questions: > Should I deploy Openstack before installing StarlingX or StartlingX itself deploy the required modules of Openstack? You deploy StarlingX first, and then if you want, you can deploy Openstack on top of it. https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/index.html The majority of OpenStack services are containerized and running on K8S which is integrated as a part of StarlingX. > Does StarlingX support CentOS Stream as the host OS? AFAIK, it’s not decided yet. Please see the related topics discussed in community. > Is there any specific performance tunning guide available for hostOS and VMs? please bring your specific questions on performance, like on which aspect. “Performance tuning” is too general to discuss. From: open infra Date: Tuesday, January 19, 2021 at 10:58 PM To: "Hu, Yong" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Hi Yong. On Tue, Jan 19, 2021 at 5:33 AM Hu, Yong > wrote: Hi Danishka, There is NO such one dedicated flag to enable or disable K8s during the system deployment. Though, technically you can trim codes to make it. Roughly STX has done some work around K8s installation/configuration/deployment. Mostly the related code is existing in the following projects: starlingx/ansible-playbooks, starlingx/config, starlingx/stx-puppet, starlingx/ha, and starlingx/nfv. Thanks for the information. BTW: what use cases or production scenarios make you have such a requirements or incentive? I just asked to understand though I have no such use case. To be honest I am new to both OpenStack and StarlingX (even I heard about startling few days ago.) Before installing StarlingX I am looking into available options and best practises. I have a few questions that not related to the subject of the original mail. Should I deploy Openstack before installing StarlingX or StartlingX itself deploy the required modules of Openstack? Does StarlingX support CentOS Stream as the host OS? Is there any specific performance tunning guide available for hostOS and VMs? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Jan 20 03:06:21 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 19 Jan 2021 22:06:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1485 - Failure! Message-ID: <557330820.996.1611111981762.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1485 Status: Failure Timestamp: 20210120T024538Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210120T023115Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210120T023115Z DOCKER_BUILD_ID: jenkins-master-distro-20210120T023115Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210120T023115Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210120T023115Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From alexandru.dimofte at intel.com Wed Jan 20 08:03:02 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 20 Jan 2021 08:03:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210119T003604Z Message-ID: Sanity Test from 2021-January-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210119T003604Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210119T003604Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From openinfradn at gmail.com Wed Jan 20 02:20:36 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 20 Jan 2021 07:50:36 +0530 Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. In-Reply-To: References: Message-ID: > > > > Is there any specific performance tunning guide available for hostOS and > VMs? > > please bring your specific questions on performance, like on which aspect. > “Performance tuning” is too general to discuss. > For example, when we deploy oracle, there are kernel parameters and shell limit values to change in a production environment. Is there such a requirement when we deploy StarlingX in order to achieve better low latency? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Wed Jan 20 02:39:24 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 20 Jan 2021 08:09:24 +0530 Subject: [Starlingx-discuss] Call for contributors: CentOS 8.0 upgrade for StarlingX 4.0 Message-ID: >* Early this week, we saw RedHat has started releasing CentOS 8.0, which *> * is one of big commitments we made to StarlingX 4.0.* Can we deploy StarlingX on CentOS 8.0 or we still need to use CentOS 7.6? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Wed Jan 20 11:47:44 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 20 Jan 2021 11:47:44 +0000 Subject: [Starlingx-discuss] Central cloud hosting in VM environment Message-ID: Hi, Is this possible to host the central cloud in the VM environment? We are looking to go for, Virtual All-in-one Duplex or Virtual Standard with Controller Storage based installation for central cloud. But the sub-cloud will be Bare metal based. Regards, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 20 12:01:21 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Jan 2021 12:01:21 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 20, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210120T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From alexandru.dimofte at intel.com Wed Jan 20 13:34:54 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 20 Jan 2021 13:34:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z Message-ID: Sanity Test from 2021-January-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I opened a new LP bug: https://bugs.launchpad.net/starlingx/+bug/1912490 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From austin.sun at intel.com Wed Jan 20 14:19:34 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 20 Jan 2021 14:19:34 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z In-Reply-To: References: Message-ID: Hi All: Just check the log , it should be related w/ lifecycle operator [1] which merged this morning. I don't know if any provision steps need to be changed. Need experts to debug this issue. [1] https://review.opendev.org/q/topic:%222007960%22+(status:open%20OR%20status:merged) Thanks. BR Austin Sun. From: Dimofte, Alexandru Sent: Wednesday, January 20, 2021 9:35 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z Sanity Test from 2021-January-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I opened a new LP bug: https://bugs.launchpad.net/starlingx/+bug/1912490 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 7022 bytes Desc: image002.png URL: From Bill.Zvonar at windriver.com Wed Jan 20 15:51:56 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Jan 2021 15:51:56 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 20, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Sanity * red today - Dan V to check re: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010596.html * Gerrit Reviews in Need of Attention * nothing this week * Topics for this Week * As lifecycle operator feature merged, it will impact rook ceph feature. * Need 3 weeks for code change , test and code review. * 3~5 days for code change, 3~5 days for test , and 10 days for review. * we'll discuss in the Release Team meeting next week, Ghada/Bill think it's probably not an issue * ARs from Previous Meetings * Saul re: RHEL DUP - still considering the best way to go on this ---- will table it at the TSC meeting next week * what about a spec re: who's going to support it, what's going to be tested, what's going to happen when a kernel upgrade happens * Bruce/Austin will discuss options offline re: spec authorship * Bill: Docker Hub Pro account - almost there - Bill & Nicolae to close on this * Open Requests for Help * nothing this week * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 20, 2021 7:01 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Jan 20, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210120T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Dan.Voiculeasa at windriver.com Wed Jan 20 16:06:17 2021 From: Dan.Voiculeasa at windriver.com (Voiculeasa, Dan) Date: Wed, 20 Jan 2021 16:06:17 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z In-Reply-To: References: , Message-ID: ALL_NODES_20210120.130109/controller-0_20210120.130109/var/extra/opt/platform/helm/20.12/platform-integ-apps/1.0-16/plugins/k8sapp_platform$ ls armada common helm __init__.py __init__.pyc tests It is missing the lifecycle folder. This is the commit for platform-integ-apps: https://review.opendev.org/c/starlingx/platform-armada-app/+/762529 . It was merged before the the config/sysinv commit. Is there a way to check how the app is build? Thanks, Dan Voiculeasa ________________________________ From: Sun, Austin Sent: Wednesday, January 20, 2021 4:19 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z Hi All: Just check the log , it should be related w/ lifecycle operator [1] which merged this morning. I don’t know if any provision steps need to be changed. Need experts to debug this issue. [1] https://review.opendev.org/q/topic:%222007960%22+(status:open%20OR%20status:merged) Thanks. BR Austin Sun. From: Dimofte, Alexandru Sent: Wednesday, January 20, 2021 9:35 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T030600Z Sanity Test from 2021-January-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T030600Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I opened a new LP bug: https://bugs.launchpad.net/starlingx/+bug/1912490 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 7022 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Wed Jan 20 18:31:54 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 20 Jan 2021 18:31:54 +0000 Subject: [Starlingx-discuss] TSC call minutes Jan 20 2021 Message-ID: 1/20/2021 * Standing topics - no pending reviews * CentOS 8 options - Saul * What should the base OS be for Stx 6.0 and beyond? * Do we stay on an RPM base? Move to Debian? * options: * Stay on CentOS 7 (supported through 2024) * Fedora - not a long term supported release, bleeding edge * OpenSUSE - previous effort to build components / RPMs * Debian - broadly supported, different package file format, 5.10 kernel * Open Embedded - POC work done, but no current activity - stx3.0 base with Pike * Proposal: Create a spec that highlights the issues and proposes a plan going forward * Creates a record of any issues and the TSC vote on the issue * Saul will take the action to create the spec -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Thu Jan 21 01:49:15 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 21 Jan 2021 01:49:15 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 20-Jan-21 DRAFT Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 20-Jan-21  All -- reviews merged since last meeting:  3 All -- bug status -- 19 total - team agrees to defer all low priority LP until the upstreaming effort is completed.  13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config 1 new LP is a minor doc change that Mary will do. Discussion SNMPv3 doc updates - should we do them now? Yes, OK to do this now. Juanita's going to do this.  Ron submitted a new review for Planning Guide, this adds OpenStack content. It's ready for reviews. The goal is to get it merged and then it will be used to figure out the downstreaming process.  Restructuring due to OpenStack additions. Right now, all of the guides that have been upstreamed have 1 index file, needs to be restructured with folders for Kubernetes and OpenStack, which means 2 new index files. For an example of this, see the planning guide review (https://review.opendev.org/c/starlingx/docs/+/771700) We viewed the output and decided to look into making expandable sections (like the "Detail" option in the API documentation https://docs.starlingx.io/api-ref/stx-config/api-ref-sysinv-v1-config.html#system) Ron - thinks div would be needed, will look around to figure out how to do it.  As another option, we talked about reorganizing the upstream docs so they are split at the top level: StarlingX > Kubernetes or OpenStack Ron doesn't think there's a lot to be saved from doing this. Decided not to do this for now.  What do users want: some users need lots of help just figuring out StarlingX and some users are figuring it out on their own, know about Kubernetes and OpenStack.   Could we add breadcrumbs (where you are in the TOC) along the top to help users? Is it a Sphinx plugin we could add? Mary ask Kevin next week. Juanita shared that Red Hat and WRCP docs do this also. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/release_notes/chap-introduction#database_size_management Helm v3 email from James Gauld (update to https://docs.starlingx.io/admintasks/kubernetes-admin-tutorials-helm-package-manager.html) * Need to check - we think that Helm v3 was done in StarlingX but not WindRiver Cloud Platform, so this change needs to be made in docs. * The change should come through as part of the upstreaming and resync to latest snapshot. Hold off now from making this change. Revisit in the next couple weeks.  Version drop-down update from Mary - Kevin Putnam from Mike Tullis' team is digging into this, he says it's an interesting issue.  * He plans to review the current OpenStack-based theme and simplify it where possible, to be easier to maintain and update afterwards.  * As we discussed before, we'll need to restructure a little. Now all the doc content is at the top of the domain.  * The button for latest goes to https://docs.starlingx.io/latest (which doesn't currently exist, so 404 error)  * Suggestion to implement this structure, so that all existing/incoming links to starlingx.io will not break.    https://docs.starlingx.io/        << add a redirect here to send to /latest               /latest      /R5.0      /R4.0           * Mary to confirm that the doc repo branching is exactly the same as the software nomenclature and branching.  From build.starlingx at gmail.com Thu Jan 21 03:04:49 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Jan 2021 22:04:49 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1488 - Failure! Message-ID: <2010410857.1000.1611198290001.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1488 Status: Failure Timestamp: 20210121T024506Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210121T023111Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210121T023111Z DOCKER_BUILD_ID: jenkins-master-distro-20210121T023111Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210121T023111Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210121T023111Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From alexandru.dimofte at intel.com Thu Jan 21 08:24:33 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 21 Jan 2021 08:24:33 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! Message-ID: Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From Ankush.Rai at commscope.com Thu Jan 21 05:50:58 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Thu, 21 Jan 2021 05:50:58 +0000 Subject: [Starlingx-discuss] Central cloud hosting in VM environment In-Reply-To: References: Message-ID: We are thinking to host the central cloud in the AWS environment. Please respond if this is supported by starlingx. Thanks, Ankush From: Rai, Ankush Sent: Wednesday, January 20, 2021 5:18 PM To: starlingx-discuss at lists.starlingx.io Subject: Central cloud hosting in VM environment Hi, Is this possible to host the central cloud in the VM environment? We are looking to go for, Virtual All-in-one Duplex or Virtual Standard with Controller Storage based installation for central cloud. But the sub-cloud will be Bare metal based. Regards, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Thu Jan 21 11:23:26 2021 From: openinfradn at gmail.com (open infra) Date: Thu, 21 Jan 2021 16:53:26 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images Message-ID: Hi. I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. I am trying to deploy all-in-one simplex deployment using [1] . Where I can download ISO images of StarlingX? It seems the mirror site [2] is down. Is there a CentOS-based guide for StarlingX deployment? [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] http://mirror.starlingx.cengn.ca/mirror/ Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanathukumar14 at gmail.com Thu Jan 21 11:59:32 2021 From: sanathukumar14 at gmail.com (sanath kumar) Date: Thu, 21 Jan 2021 17:29:32 +0530 Subject: [Starlingx-discuss] StarlingX Installation Error In-Reply-To: References: Message-ID: Hello StarlingX Team, I have done all the changes as mentioned in the previous meet. But I am facing the same problem. It would be great if we can have a discussion on this today, Please let me know your availability. I will also attach the link which has the information of all log-files. *https://drive.google.com/drive/folders/1J_gHzisudkNMKuP6BLCuw7mmD3GLsIoW?usp=sharing * Regards, Sanath Kumar +91 8971546076 On Thu, 21 Jan 2021 at 13:22, sanath kumar wrote: > Hello Team, > Is it possible to meet up today? > > Regards, > Sanath Kumar > +91 8971546076 > > > On Thu, 21 Jan 2021 at 10:58, sanath kumar > wrote: > >> Hello StarlingX Team, >> I have done all the changes as mentioned in the previous meet. But I am >> facing the same problem. >> It would be great if we can have a discussion on this today, Please let >> me know your availability. >> I will also attach the link which has the information of all log-files. >> *https://drive.google.com/drive/folders/1J_gHzisudkNMKuP6BLCuw7mmD3GLsIoW?usp=sharing >> * >> >> Regards, >> Sanath Kumar >> +91 8971546076 >> >> >> On Tue, 19 Jan 2021 at 12:28, sanath kumar >> wrote: >> >>> Hello Team, >>> Some of the images are missing. I'll look into it and get back to you. >>> >>> Regards, >>> Sanath Kumar >>> +91 8971546076 >>> >>> >>> On Tue, 19 Jan 2021 at 10:04, sanath kumar >>> wrote: >>> >>>> Hello Team StarrlingX, >>>> I have uploaded all the documents in the same previous link. Please let >>>> me know if you need any other information. >>>> *https://drive.google.com/drive/folders/1Ms3EIsIX7BTf8OhAZSOAYErat5BiSPW7?usp=sharing >>>> * >>>> >>>> >>>> Regards, >>>> Sanath Kumar >>>> +91 8971546076 >>>> >>>> >>>> On Mon, 18 Jan 2021 at 15:48, Jascanu, Nicolae < >>>> nicolae.jascanu at intel.com> wrote: >>>> >>>>> Hi Kumar, >>>>> >>>>> Please upload also /var/log/sysinv.log and the file that is listed in >>>>> sysinv.log as log error ( cat /var/log/sysinv.log | grep detail) >>>>> >>>>> If we will see the same error, you should raise a bug. >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Monday, January 18, 2021 06:00 >>>>> *To:* Jascanu, Nicolae ; Dimofte, >>>>> Alexandru ; Jones, Bruce E < >>>>> bruce.e.jones at intel.com> >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> Hi StarlingX Team, >>>>> >>>>> I have done all the changes as mentioned in the previous meet. >>>>> >>>>> But the result remained the same, ending with the same error. >>>>> >>>>> I have attached a link which will give more idea regarding the error. >>>>> >>>>> *https://drive.google.com/drive/folders/1Ms3EIsIX7BTf8OhAZSOAYErat5BiSPW7?usp=sharing >>>>> * >>>>> >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 15 Jan 2021 at 14:44, sanath kumar >>>>> wrote: >>>>> >>>>> Thank you. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 15 Jan 2021 at 14:29, Jascanu, Nicolae < >>>>> nicolae.jascanu at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> We can shortly talk at 12.00 am Romania time on zoom >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Friday, January 15, 2021 10:53 >>>>> *To:* Jascanu, Nicolae >>>>> *Cc:* Dimofte, Alexandru >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> Hello Sir, >>>>> >>>>> Can we meet up today? >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, 12 Jan 2021 at 07:50, sanath kumar >>>>> wrote: >>>>> >>>>> Is it possible to have a discussion Today? >>>>> If yes. Please let me know your availability. >>>>> In this link *https://drive.google.com/drive/folders/1Pl5MbF8KvHG47fwqC7H6HVf-_0g1_o3c?usp=sharing >>>>> *, >>>>> I have mentioned the information regarding log files of Provision Setup. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, 6 Jan 2021 at 10:43, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, >>>>> >>>>> Is it possible to connect through video call today? >>>>> >>>>> Please let me know your availability. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, 5 Jan 2021 at 18:23, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, I have updated the changes, Still the same error I am >>>>> facing. >>>>> >>>>> *https://drive.google.com/drive/folders/1eaWRhRenq5Y6Ir8cbBJeLnr4x41s86dX?usp=sharing >>>>> * >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, 5 Jan 2021 at 14:36, Jascanu, Nicolae < >>>>> nicolae.jascanu at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> Based on the sysinv.log, you still have several missing images from >>>>> registry. Please search for “Client Error” and add the missing images into >>>>> registry >>>>> >>>>> >>>>> >>>>> sysinv 2021-01-04 12:11:52.824 100935 ERROR sysinv.conductor.kube_app >>>>> [-] Image 10.237.170.51:5000/airshipit/kubernetes-entrypoint:v1.0.0 >>>>> download failed from public/privateregistry: 404 Client Error: Not Found >>>>> ("manifest for >>>>> 10.237.170.51:5000/airshipit/kubernetes-entrypoint:v1.0.0 not >>>>> found"): NotFound: 404 Client Error: Not Found ("manifest for >>>>> 10.237.170.51:5000/airshipit/kubernetes-entrypoint:v1.0.0 not found") >>>>> >>>>> sysinv 2021-01-04 12:11:52.825 100935 INFO sysinv.conductor.kube_app >>>>> [-] Image registry.local:9001/ >>>>> docker.io/starlingx/stx-neutron:master-centos-stable-20201124T014053Z.0 >>>>> download started from local registry >>>>> >>>>> sysinv 2021-01-04 12:12:02.551 100935 INFO sysinv.conductor.kube_app >>>>> [-] Image registry.local:9001/ >>>>> docker.io/starlingx/stx-ceilometer:master-centos-stable-20201124T014053Z.0 >>>>> download succeeded in 12 seconds >>>>> >>>>> sysinv 2021-01-04 12:12:02.682 100935 INFO sysinv.conductor.kube_app >>>>> [-] Image registry.local:9001/ >>>>> quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 >>>>> download succeeded in 13 seconds >>>>> >>>>> sysinv 2021-01-04 12:12:02.684 100935 INFO sysinv.conductor.kube_app >>>>> [-] Failed to download image: registry.local:9001/ >>>>> gcr.io/google_containers/hyperkube-amd64:v1.11.6 >>>>> >>>>> sysinv 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> [-] Deployment of application stx-openstack >>>>> (1.0-69-centos-stable-versioned) failed: failed to download one or more >>>>> image(s).: KubeAppApplyFailure: Deployment of application stx-openstack >>>>> (1.0-69-centos-stable-versioned) failed: failed to download one or more >>>>> image(s). >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> Traceback (most recent call last): >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app File >>>>> "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line >>>>> 2185, in perform_app_apply >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> self.download_images(app) >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app File >>>>> "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line >>>>> 778, in download_images >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> reason=constants.APP_PROGRESS_IMAGES_DOWNLOAD_FAILED) >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> KubeAppApplyFailure: Deployment of application stx-openstack >>>>> (1.0-69-centos-stable-versioned) failed: failed to download one or more >>>>> image(s). >>>>> >>>>> 2021-01-04 12:12:02.685 100935 ERROR sysinv.conductor.kube_app >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Tuesday, January 5, 2021 09:33 >>>>> *To:* Jascanu, Nicolae ; Dimofte, >>>>> Alexandru >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> Hello Sir, >>>>> >>>>> I have attached a link, which has information about the Setup and >>>>> Provision. >>>>> >>>>> All 4 cases of Setup got passed. But getting error in Provision. >>>>> >>>>> *https://drive.google.com/drive/folders/1Ok40Ejk9vKyiCZ7AfH6DJDlpjgyZYsBI?usp=sharing >>>>> * >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, 4 Jan 2021 at 18:02, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, >>>>> >>>>> I have attached a link, which has information about the Setup and >>>>> Provision. >>>>> >>>>> All 4 cases of Setup got passed. But getting error in Provision. >>>>> >>>>> *https://drive.google.com/drive/folders/1Ok40Ejk9vKyiCZ7AfH6DJDlpjgyZYsBI?usp=sharing >>>>> * >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, 4 Jan 2021 at 10:02, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, >>>>> >>>>> Is it possible to schedule a call on Today, January 4th? If yes, >>>>> please let me know your availability. >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, 29 Dec 2020 at 22:05, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, >>>>> >>>>> Is it possible to schedule a call on Monday, January 4th? If yes, >>>>> please let me know your availability. >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, 21 Dec 2020 at 16:57, sanath kumar >>>>> wrote: >>>>> >>>>> Ok sir, I will do that. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Sun, 20 Dec 2020 at 20:34, Jascanu, Nicolae < >>>>> nicolae.jascanu at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> I’m looking into sysinv.log and there are still several missing images >>>>> from the registry. Please grep for *not available* >>>>> >>>>> and add that images into registry. >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Friday, December 18, 2020 16:04 >>>>> *To:* Jascanu, Nicolae >>>>> *Cc:* Dimofte, Alexandru >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> I am eagerly waiting for your response. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 18 Dec 2020 at 18:22, sanath kumar >>>>> wrote: >>>>> >>>>> The error looks like with the *Ansible Bootstrap Configuration* >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 18 Dec 2020 at 18:12, sanath kumar >>>>> wrote: >>>>> >>>>> Hello Sir, >>>>> >>>>> Now all images are uploaded to the registry, I am getting a new error, >>>>> Can you please look into this error. >>>>> >>>>> *https://drive.google.com/drive/folders/1aVMq-hu9ccV4VoO8vrvK01jZFlRXHzZC?usp=sharing >>>>> * >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 18 Dec 2020 at 16:15, Jascanu, Nicolae < >>>>> nicolae.jascanu at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> maybe it helps: >>>>> >>>>> docker.io/memcached:1.5.5 >>>>> >>>>> docker.io/nfvpe/multus:v3.4 >>>>> >>>>> docker.io/openstackhelm/mariadb:ubuntu_xenial-20200303 >>>>> >>>>> docker.io/rabbitmq:3.7-management >>>>> >>>>> docker.io/rabbitmq:3.7.24 >>>>> >>>>> docker.io/rabbitmq:3.7.24-management >>>>> >>>>> docker.io/starlingx/ceph-config-helper:v1.15.0 >>>>> >>>>> docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2 >>>>> >>>>> >>>>> docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae >>>>> >>>>> docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0 >>>>> >>>>> docker.io/starlingx/stx-cinder:rc-4.0-centos-stable-latest >>>>> >>>>> docker.io/starlingx/stx-glance:rc-4.0-centos-stable-latest >>>>> >>>>> docker.io/starlingx/stx-heat:rc-4.0-centos-stable-latest >>>>> >>>>> docker.io/starlingx/stx-keystone:rc-4.0-centos-stable-latest >>>>> >>>>> gcr.io/google_containers/defaultbackend:1.0 >>>>> >>>>> gcr.io/kubernetes-helm/tiller:v2.16.1 >>>>> >>>>> k8s.gcr.io/coredns:1.6.7 >>>>> >>>>> k8s.gcr.io/defaultbackend:1.4 >>>>> >>>>> k8s.gcr.io/etcd:3.4.3-0 >>>>> >>>>> k8s.gcr.io/kube-apiserver:v1.18.1 >>>>> >>>>> k8s.gcr.io/kube-controller-manager:v1.18.1 >>>>> >>>>> k8s.gcr.io/kube-proxy:v1.18.1 >>>>> >>>>> k8s.gcr.io/kube-scheduler:v1.18.1 >>>>> >>>>> k8s.gcr.io/pause:3.2 >>>>> >>>>> >>>>> quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic >>>>> >>>>> quay.io/airshipit/kubernetes-entrypoint:v1.0.0 >>>>> >>>>> quay.io/calico/cni:v3.12.0 >>>>> >>>>> quay.io/calico/kube-controllers:v3.12.0 >>>>> >>>>> quay.io/calico/node:v3.12.0 >>>>> >>>>> quay.io/calico/pod2daemon-flexvol:v3.12.0 >>>>> >>>>> quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 >>>>> >>>>> quay.io/jetstack/cert-manager-acmesolver:v0.15.0 >>>>> >>>>> quay.io/jetstack/cert-manager-cainjector:v0.15.0 >>>>> >>>>> quay.io/jetstack/cert-manager-controller:v0.15.0 >>>>> >>>>> quay.io/jetstack/cert-manager-webhook:v0.15.0 >>>>> >>>>> quay.io/k8scsi/snapshot-controller:v2.0.0-rc2 >>>>> >>>>> quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 >>>>> >>>>> quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 >>>>> >>>>> quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Friday, December 18, 2020 11:19 >>>>> *To:* Jascanu, Nicolae >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> Sure, I will be there. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 18 Dec 2020 at 14:48, Jascanu, Nicolae < >>>>> nicolae.jascanu at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> Let’s have a short meeting on Zoom at 12.30 Romania Time. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Friday, December 18, 2020 08:33 >>>>> *To:* Dimofte, Alexandru >>>>> *Cc:* Jascanu, Nicolae ; Jones, Bruce E < >>>>> bruce.e.jones at intel.com> >>>>> *Subject:* Re: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> All the images which are mentioned in the mail are already in the >>>>> registry. >>>>> >>>>> still, it is showing some of the images are not found. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, 18 Dec 2020 at 11:05, sanath kumar >>>>> wrote: >>>>> >>>>> I have got some doubts is it possible to meet-up today? >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, 17 Dec 2020 at 22:30, sanath kumar >>>>> wrote: >>>>> >>>>> Is it possible to meet up now? >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Sanath Kumar >>>>> >>>>> +91 8971546076 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, 17 Dec 2020 at 21:24, Dimofte, Alexandru < >>>>> alexandru.dimofte at intel.com> wrote: >>>>> >>>>> Hi Kumar, >>>>> >>>>> >>>>> >>>>> You still need to install the missing images into your docker mirror >>>>> registry. Many of the missing images are from *gcr.io *. >>>>> Example: you have this error: u' >>>>> 10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1' you should >>>>> install: >>>>> >>>>> *gcr.io/kubernetes-helm/tiller:v2.16.1 >>>>> * see: >>>>> https://hub.docker.com/layers/omio/gcr.io.kubernetes-helm.tiller/v2.16.1/images/sha256-3c70ee359d3ec305ca469395a2481b2375d569c6b4a928389ca07d829d12ec51?context=explore >>>>> >>>>> >>>>> >>>>> You should search and install all missing images. >>>>> >>>>> >>>>> >>>>> BR, >>>>> >>>>> Alex >>>>> >>>>> >>>>> >>>>> *From:* Jascanu, Nicolae >>>>> *Sent:* Thursday, December 17, 2020 4:29 PM >>>>> *To:* sanath kumar >>>>> *Cc:* Dimofte, Alexandru ; Jones, Bruce >>>>> E >>>>> *Subject:* RE: StarlingX Installation Error >>>>> >>>>> >>>>> >>>>> Hi Kumar, >>>>> >>>>> I’m looking into ansible.log and the several images below are missing. >>>>> You need to make sure you have all of them into your mirror registry. >>>>> >>>>> >>>>> >>>>> 2020-12-17 11:01:03,528 p=10113 u=sysadmin | fatal: [localhost]: >>>>> FAILED! => {"changed": true, "msg": "non-zero return code", "rc": 1, >>>>> "stderr": "Traceback (most recent call last):\n File >>>>> \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1608202666.15-99048975950856/download_images.py\", >>>>> line 144, in \n raise Exception(\"Failed to download images %s\" >>>>> % failed_downloads)\nException: Failed to download images [u' >>>>> 10.237.170.51:5000/kube-apiserver:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-controller-manager:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-scheduler:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-proxy:v1.18.1', u'10.237.170.51:5000/pause:3.2', >>>>> u'10.237.170.51:5000/etcd:3.4.3-0', u'10.237.170.51:5000/coredns:1.6.7', >>>>> u'10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1', u' >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic', >>>>> u'10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1', u' >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2']\n", >>>>> "stderr_lines": ["Traceback (most recent call last):", " File >>>>> \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1608202666.15-99048975950856/download_images.py\", >>>>> line 144, in ", " raise Exception(\"Failed to download images >>>>> %s\" % failed_downloads)", "Exception: Failed to download images [u' >>>>> 10.237.170.51:5000/kube-apiserver:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-controller-manager:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-scheduler:v1.18.1', u' >>>>> 10.237.170.51:5000/kube-proxy:v1.18.1', u'10.237.170.51:5000/pause:3.2', >>>>> u'10.237.170.51:5000/etcd:3.4.3-0', u'10.237.170.51:5000/coredns:1.6.7', >>>>> u'10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1', u' >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic', >>>>> u'10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1', u' >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2']"], >>>>> "stdout": "Image is up to date for >>>>> sha256:cb6799752c46cb16c0c5bebcb355e988a1cd1b3745ce8b67e004abe9a81340a8\nImage >>>>> is up to date for >>>>> sha256:fc05bc4225f39e81dcbd0035457977276ed8a6054e6bde6406e39b672e9724f5\nImage >>>>> is up to date for >>>>> sha256:53aa421faf0acd88f8a4cb113e9db2cc65b2a2954640ed96a56c4b94233674d8\nImage >>>>> is up to date for >>>>> sha256:98793d0a88c823c4fc0fb1b3833d12932be270fc4b6d62bc181f0f54413fe12d\nImage >>>>> is up to date for >>>>> sha256:7cf8e2d1b7337338a3f977d07abdf63d80d5005458dfab3ab8962c2bab99d40d\nImage >>>>> is up to date for >>>>> sha256:cfba917fa8e18db8b00696adce24aa84b3d64483036aef72fd6256cff3b89da6\nImage >>>>> is up to date for >>>>> sha256:a2bef2b25274b1acbdfde5e2f3de432475e15d4036b2108cea2dce968b0c29ea\nImage >>>>> is up to date for >>>>> sha256:fb95693fe5c67fc46893c1735d85f00f462dc7f5254f5ddbcbbe85fd4ef71717\n >>>>> Image download failed: 10.237.170.51:5000/kube-apiserver:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-apiserver:v1.18.1 not found\")\n Image >>>>> download failed: 10.237.170.51:5000/kube-controller-manager:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-controller-manager:v1.18.1 not found\")\n >>>>> Image download failed: 10.237.170.51:5000/kube-scheduler:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-scheduler:v1.18.1 not found\")\n Image >>>>> download failed: 10.237.170.51:5000/kube-proxy:v1.18.1404 Client >>>>> Error: Not Found (\"manifest for 10.237.170.51:5000/kube-proxy:v1.18.1 >>>>> not found\")\n Image download failed: 10.237.170.51:5000/pause:3.2404 >>>>> Client Error: Not Found (\"manifest for 10.237.170.51:5000/pause:3.2 >>>>> not found\")\n Image download failed: >>>>> 10.237.170.51:5000/etcd:3.4.3-0404 Client Error: Not Found >>>>> (\"manifest for 10.237.170.51:5000/etcd:3.4.3-0 not found\")\n Image >>>>> download failed: 10.237.170.51:5000/coredns:1.6.7404 Client Error: >>>>> Not Found (\"manifest for 10.237.170.51:5000/coredns:1.6.7 not >>>>> found\")\nImage download succeeded: >>>>> 10.237.170.51:5000/calico/cni:v3.12.0\nImage >>>>> push >>>>> succeeded: registry.local:9001/quay.io/calico/cni:v3.12.0\nImage >>>>> >>>>> 10.237.170.51:5000/calico/cni:v3.12.0 download succeeded by >>>>> containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/calico/node:v3.12.0\nImage >>>>> push >>>>> succeeded: registry.local:9001/quay.io/calico/node:v3.12.0\nImage >>>>> >>>>> 10.237.170.51:5000/calico/node:v3.12.0 download succeeded by >>>>> containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/calico/kube-controllers:v3.12.0\nImage >>>>> >>>>> push succeeded: registry.local:9001/ >>>>> quay.io/calico/kube-controllers:v3.12.0\nImage >>>>> >>>>> 10.237.170.51:5000/calico/kube-controllers:v3.12.0 download succeeded >>>>> by containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/calico/pod2daemon-flexvol:v3.12.0\nImage >>>>> >>>>> push succeeded: registry.local:9001/ >>>>> quay.io/calico/pod2daemon-flexvol:v3.12.0\nImage >>>>> >>>>> 10.237.170.51:5000/calico/pod2daemon-flexvol:v3.12.0 download >>>>> succeeded by containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/nfvpe/multus:v3.4\nImage >>>>> push >>>>> succeeded: registry.local:9001/docker.io/nfvpe/multus:v3.4\nImage >>>>> >>>>> 10.237.170.51:5000/nfvpe/multus:v3.4 download succeeded by >>>>> containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/starlingx/k8s-cni-sriov:stx.3.0-v2.2\nImage >>>>> >>>>> push succeeded: registry.local:9001/ >>>>> docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2\nImage >>>>> >>>>> 10.237.170.51:5000/starlingx/k8s-cni-sriov:stx.3.0-v2.2 download >>>>> succeeded by containerd\nImage download succeeded: >>>>> 10.237.170.51:5000/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae\nImage >>>>> >>>>> push succeeded: registry.local:9001/ >>>>> docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae\nImage >>>>> >>>>> 10.237.170.51:5000/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae >>>>> download succeeded by containerd\n Image download failed: >>>>> 10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1404 Client Error: >>>>> Not Found (\"manifest for >>>>> 10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1 not found\")\n >>>>> Image download failed: >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic >>>>> not found\")\nImage download succeeded: >>>>> 10.237.170.51:5000/starlingx/n3000-opae:stx.4.0-v1.0.0\nImage >>>>> >>>>> push succeeded: registry.local:9001/ >>>>> docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0\nImage >>>>> >>>>> 10.237.170.51:5000/starlingx/n3000-opae:stx.4.0-v1.0.0 download >>>>> succeeded by containerd\n Image download failed: >>>>> 10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1404 Client >>>>> Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1 not >>>>> found\")\n Image download failed: >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2404 Client >>>>> Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2 not >>>>> found\")\n", "stdout_lines": ["Image is up to date for >>>>> sha256:cb6799752c46cb16c0c5bebcb355e988a1cd1b3745ce8b67e004abe9a81340a8", >>>>> "Image is up to date for >>>>> sha256:fc05bc4225f39e81dcbd0035457977276ed8a6054e6bde6406e39b672e9724f5", >>>>> "Image is up to date for >>>>> sha256:53aa421faf0acd88f8a4cb113e9db2cc65b2a2954640ed96a56c4b94233674d8", >>>>> "Image is up to date for >>>>> sha256:98793d0a88c823c4fc0fb1b3833d12932be270fc4b6d62bc181f0f54413fe12d", >>>>> "Image is up to date for >>>>> sha256:7cf8e2d1b7337338a3f977d07abdf63d80d5005458dfab3ab8962c2bab99d40d", >>>>> "Image is up to date for >>>>> sha256:cfba917fa8e18db8b00696adce24aa84b3d64483036aef72fd6256cff3b89da6", >>>>> "Image is up to date for >>>>> sha256:a2bef2b25274b1acbdfde5e2f3de432475e15d4036b2108cea2dce968b0c29ea", >>>>> "Image is up to date for >>>>> sha256:fb95693fe5c67fc46893c1735d85f00f462dc7f5254f5ddbcbbe85fd4ef71717", " >>>>> Image download failed: 10.237.170.51:5000/kube-apiserver:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-apiserver:v1.18.1 not found\")", " Image >>>>> download failed: 10.237.170.51:5000/kube-controller-manager:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-controller-manager:v1.18.1 not found\")", " >>>>> Image download failed: 10.237.170.51:5000/kube-scheduler:v1.18.1404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/kube-scheduler:v1.18.1 not found\")", " Image >>>>> download failed: 10.237.170.51:5000/kube-proxy:v1.18.1404 Client >>>>> Error: Not Found (\"manifest for 10.237.170.51:5000/kube-proxy:v1.18.1 >>>>> not found\")", " Image download failed: >>>>> 10.237.170.51:5000/pause:3.2404 Client Error: Not Found (\"manifest >>>>> for 10.237.170.51:5000/pause:3.2 not found\")", " Image download >>>>> failed: 10.237.170.51:5000/etcd:3.4.3-0404 Client Error: Not Found >>>>> (\"manifest for 10.237.170.51:5000/etcd:3.4.3-0 not found\")", " >>>>> Image download failed: 10.237.170.51:5000/coredns:1.6.7404 Client >>>>> Error: Not Found (\"manifest for 10.237.170.51:5000/coredns:1.6.7 not >>>>> found\")", "Image download succeeded: >>>>> 10.237.170.51:5000/calico/cni:v3.12.0", "Image push succeeded: >>>>> registry.local:9001/quay.io/calico/cni:v3.12.0", "Image >>>>> 10.237.170.51:5000/calico/cni:v3.12.0 download succeeded by >>>>> containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/calico/node:v3.12.0", "Image push succeeded: >>>>> registry.local:9001/quay.io/calico/node:v3.12.0", "Image >>>>> 10.237.170.51:5000/calico/node:v3.12.0 download succeeded by >>>>> containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/calico/kube-controllers:v3.12.0", "Image push >>>>> succeeded: registry.local:9001/quay.io/calico/kube-controllers:v3.12.0", >>>>> "Image 10.237.170.51:5000/calico/kube-controllers:v3.12.0 download >>>>> succeeded by containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/calico/pod2daemon-flexvol:v3.12.0", "Image push >>>>> succeeded: registry.local:9001/ >>>>> quay.io/calico/pod2daemon-flexvol:v3.12.0", "Image >>>>> 10.237.170.51:5000/calico/pod2daemon-flexvol:v3.12.0 download >>>>> succeeded by containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/nfvpe/multus:v3.4", "Image push succeeded: >>>>> registry.local:9001/docker.io/nfvpe/multus:v3.4", "Image >>>>> 10.237.170.51:5000/nfvpe/multus:v3.4 download succeeded by >>>>> containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/starlingx/k8s-cni-sriov:stx.3.0-v2.2", "Image push >>>>> succeeded: registry.local:9001/ >>>>> docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2", "Image >>>>> 10.237.170.51:5000/starlingx/k8s-cni-sriov:stx.3.0-v2.2 download >>>>> succeeded by containerd", "Image download succeeded: >>>>> 10.237.170.51:5000/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae", >>>>> "Image push succeeded: registry.local:9001/ >>>>> docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae", >>>>> "Image >>>>> 10.237.170.51:5000/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae >>>>> download succeeded by containerd", " Image download failed: >>>>> 10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1404 Client Error: >>>>> Not Found (\"manifest for >>>>> 10.237.170.51:5000/kubernetes-helm/tiller:v2.16.1 not found\")", " >>>>> Image download failed: >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic404 >>>>> Client Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic >>>>> not found\")", "Image download succeeded: >>>>> 10.237.170.51:5000/starlingx/n3000-opae:stx.4.0-v1.0.0", "Image push >>>>> succeeded: registry.local:9001/ >>>>> docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0", "Image >>>>> 10.237.170.51:5000/starlingx/n3000-opae:stx.4.0-v1.0.0 download >>>>> succeeded by containerd", " Image download failed: >>>>> 10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1404 Client >>>>> Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/stackanetes/kubernetes-entrypoint:v0.3.1 not >>>>> found\")", " Image download failed: >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2404 Client >>>>> Error: Not Found (\"manifest for >>>>> 10.237.170.51:5000/k8scsi/snapshot-controller:v2.0.0-rc2 not >>>>> found\")"]} >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Nicolae Jascanu, Ph.D. >>>>> >>>>> Software Engineer >>>>> >>>>> IOTG >>>>> >>>>> Galati, Romania >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From:* sanath kumar >>>>> *Sent:* Thursday, December 17, 2020 15:31 >>>>> *To:* Jascanu, Nicolae < >>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 21 14:23:56 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 21 Jan 2021 14:23:56 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project In-Reply-To: References: Message-ID: Thanks Qian bin review for my patch, I already update and verified. Please go on review. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:07 PM To: Qian, Bin ; Kung, John ; Bart Wensley ; MacDonald, Eric ; Waines, Greg ; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin ; Hu, Yong Subject: RE: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:08 PM To: Qian, Bin >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 21 14:25:39 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 21 Jan 2021 14:25:39 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in stx-puppet project In-Reply-To: References: Message-ID: Hi Please review my patch for stx-puppet project. If no any other idea. Wish Review+2, W+1! https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:06 PM To: Bailey, Henry Albert (Al) ; Bart Wensley ; Church, Robert ; Chris Friesen ; Penney, Don ; Kung, John ; Waines, Greg Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in stx-puppet project Hi folks Thank Bob, Penney and AL review for stx-puppet project. I update comment and welcome more review. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:03 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in stx-puppet project + Greg Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:00 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in stx-puppet project Hi folks Please review my patch to enable rook-ceph in stx-puppet project. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 21 14:28:08 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 21 Jan 2021 14:28:08 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 21 14:31:39 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 21 Jan 2021 14:31:39 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Hi Bob and Dan I update patch for story about lifecycle. And finish verification. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 1, add lifecycle for rook-ceph 2, add a function in sysinv-conductor, update_config_for_rook_ceph, which is called in application rook-ceph hook function, in operation post stage 3, cleanup some code as function already move to rook-ceph application's hook Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:03 PM To: Bailey, Henry Albert (Al) ; Bart Wensley ; Church, Robert ; Chris Friesen ; Penney, Don ; Kung, John ; Waines, Greg Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Thu Jan 21 14:56:00 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 21 Jan 2021 14:56:00 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: Message-ID: Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From Davlet.Panech at windriver.com Thu Jan 21 15:07:21 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 21 Jan 2021 15:07:21 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: , Message-ID: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Thu Jan 21 22:20:02 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 21 Jan 2021 22:20:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210120T202853Z Message-ID: Sanity Test from 2021-January-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T202853Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210120T202853Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Fri Jan 22 07:59:19 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 22 Jan 2021 07:59:19 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project In-Reply-To: References: Message-ID: Thanks Qianbin review for my patch. Welcome more review idea. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:24 PM To: 'Qian, Bin' ; 'Kung, John' ; 'Bart Wensley' ; 'MacDonald, Eric' ; 'Waines, Greg' ; 'Poncea, Ovidiu' Cc: 'starlingx-discuss at lists.starlingx.io' ; Sun, Austin ; Hu, Yong Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qian bin review for my patch, I already update and verified. Please go on review. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:07 PM To: Qian, Bin >; Kung, John >; Bart Wensley >; MacDonald, Eric >; Waines, Greg >; Poncea, Ovidiu > Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:08 PM To: Qian, Bin >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Jan 22 08:03:38 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 22 Jan 2021 08:03:38 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project In-Reply-To: References: Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:28 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Jan 22 08:03:16 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 22 Jan 2021 08:03:16 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in stx-puppet project In-Reply-To: References: Message-ID: Thanks John and Penney review. Welcome more review idea. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:26 PM To: 'Bailey, Henry Albert (Al)' ; 'Bart Wensley' ; 'Church, Robert' ; 'Chris Friesen' ; 'Penney, Don' ; 'Kung, John' ; 'Waines, Greg' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: review patch to enable rook-ceph in stx-puppet project Hi Please review my patch for stx-puppet project. If no any other idea. Wish Review+2, W+1! https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:06 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in stx-puppet project Hi folks Thank Bob, Penney and AL review for stx-puppet project. I update comment and welcome more review. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:03 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in stx-puppet project + Greg Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:00 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in stx-puppet project Hi folks Please review my patch to enable rook-ceph in stx-puppet project. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Jan 22 08:05:19 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 22 Jan 2021 08:05:19 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Thanks Dan review for my patch. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:32 PM To: 'Bailey, Henry Albert (Al)' ; 'Bart Wensley' ; 'Church, Robert' ; 'Chris Friesen' ; 'Penney, Don' ; 'Kung, John' ; 'Waines, Greg' ; 'Voiculeasa, Dan' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: review patch to enable rook-ceph in config project. Hi Bob and Dan I update patch for story about lifecycle. And finish verification. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 1, add lifecycle for rook-ceph 2, add a function in sysinv-conductor, update_config_for_rook_ceph, which is called in application rook-ceph hook function, in operation post stage 3, cleanup some code as function already move to rook-ceph application's hook Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:03 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 22 08:47:54 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Jan 2021 03:47:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1489 - Still Failing! In-Reply-To: <471508027.998.1611198287080.JavaMail.javamailuser@localhost> References: <471508027.998.1611198287080.JavaMail.javamailuser@localhost> Message-ID: <721474925.1036.1611305275342.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1489 Status: Still Failing Timestamp: 20210122T065139Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210122T053000Z DOCKER_BUILD_ID: jenkins-master-20210122T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From Venkata.Veldanda at radisys.com Fri Jan 22 09:11:21 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Fri, 22 Jan 2021 09:11:21 +0000 Subject: [Starlingx-discuss] Intel N3000 FPGA & support for igb_uio module Message-ID: Hi Team, 1] I am using StarlingX 4.0 and trying to use the below guide to setup N3000 Vista Creek FPGA card. https://docs.starlingx.io/configuration/intel_n3000_fpga.html ~(keystone_admin)$ system device-image-upload imagefile root-key pci_vendor pci_device --key-signature key_signature --name imagename --description description --image-version version As part of my N3000 package I see some set of installer images, NVM package updates, iavf driver packages etc. However I am looking for the specific parameters that are highlighted above but I don't find. Anyone has an idea what does the file name look like for the root-key or the key_signature? On my baremetal (CentOS vanilla) installation I was following the standard procedure defined "https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-ias-n3000.pdf" but there I didn't have to use any such key etc. Any help would be appreciated. 2] Secondly, in StarlingX 4.0 I don't find igb_uio module present on the host. Is it currently supported as part of stx 4.0? controller-0:~$ lsmod |grep igb_uio controller-0:~$ Per documentation I see the below The supported VF driver(s) are currently: - igb_uio - vfio Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 22 10:45:08 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Jan 2021 05:45:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 2137 - Still Failing! In-Reply-To: null References: null Message-ID: <1689447869.1040.1611312309193.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 2137 Status: Still Failing Timestamp: 20210122T094506Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210122T053000Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs RETRIES: 13 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs MASTER_JOB_NAME: STX_build_master_master RETRY_INTERVAL_SEC: 300 MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic TIMESTAMP: 20210122T053000Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210122T053000Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210122T053000Z/outputs From build.starlingx at gmail.com Fri Jan 22 10:45:10 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Jan 2021 05:45:10 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 806 - Still Failing! In-Reply-To: null References: null Message-ID: <1412291944.1043.1611312311486.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 806 Status: Still Failing Timestamp: 20210122T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210122T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Fri Jan 22 14:55:06 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 22 Jan 2021 09:55:06 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: Message-ID: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: > The hosting company had an issue with their servers, they are working > on it. They hope to be back online mid afternoon (Jan 21, Eastern > Standard Time). > ------------------------------------------------------------------------ > *From:* Panech, Davlet > *Sent:* January 21, 2021 9:56 AM > *To:* Dimofte, Alexandru ; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: Cengn Mirror server in down?! > Thanks Alexandru, we are looking into it. > > ------------------------------------------------------------------------ > *From:* Dimofte, Alexandru > *Sent:* January 21, 2021 3:24 AM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! > > Hello guys, > > I observed, trying to connect to > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , > that cengn mirror server is down. > > Best regards, > > Alex > > Logo Description automatically generated > > > > Dimofte Alexandru > > Software Engineer > > STARLINGX TEAM > > Skype no: +40 336403734 > > Personal Mobile: +40 743167456 > > alexandru.dimofte at intel.com > > Intel Romania > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From maryx.camp at intel.com Fri Jan 22 15:36:23 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 22 Jan 2021 15:36:23 +0000 Subject: [Starlingx-discuss] Intel N3000 FPGA & support for igb_uio module In-Reply-To: References: Message-ID: Hi Venkata, Regarding 1] The StarlingX docs team is upstreaming content at the moment. There is more N3000 FPGA info in the Node Management guide: https://docs.starlingx.io/node_management/index.html Please see these specific sections: https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/n3000-overview.html https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.html I hope this is helpful. thanks, Mary Camp Kelly Services Technical Writer | maryx.camp at intel.com From: Venkata Ramana Veldanda Sent: Friday, January 22, 2021 4:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intel N3000 FPGA & support for igb_uio module Hi Team, 1] I am using StarlingX 4.0 and trying to use the below guide to setup N3000 Vista Creek FPGA card. https://docs.starlingx.io/configuration/intel_n3000_fpga.html ~(keystone_admin)$ system device-image-upload imagefile root-key pci_vendor pci_device --key-signature key_signature --name imagename --description description --image-version version As part of my N3000 package I see some set of installer images, NVM package updates, iavf driver packages etc. However I am looking for the specific parameters that are highlighted above but I don't find. Anyone has an idea what does the file name look like for the root-key or the key_signature? On my baremetal (CentOS vanilla) installation I was following the standard procedure defined "https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-ias-n3000.pdf" but there I didn't have to use any such key etc. Any help would be appreciated. 2] Secondly, in StarlingX 4.0 I don't find igb_uio module present on the host. Is it currently supported as part of stx 4.0? controller-0:~$ lsmod |grep igb_uio controller-0:~$ Per documentation I see the below The supported VF driver(s) are currently: - igb_uio - vfio Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Jan 22 15:58:37 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 22 Jan 2021 16:58:37 +0100 Subject: [Starlingx-discuss] Growing the community's presence on IRC Message-ID: <9AC57EEF-4220-4976-83C6-0EA8260FE8C7@gmail.com> Hi StarlingX Community, I’m reaching out about the #starlingx IRC channel. I’ve recognized more and more people hopping in the project channel on Freenode to ask questions and get in touch with the community. The questions often go unanswered and there is rarely any communication happening there. It would be great to have more people from the community to join the channel and help newcomers who are evaluating the project or are interested in joining the community. The last question I saw was about a robot test case failure. Other questions are also around deploying the software. I think having people from the test team along with a few others who are more experienced with deploying StarlingX would be very helpful. We can learn a lot from issues that people run into as well as it is a great way to grow the community. If you need guidance on how to join IRC you can find information about the steps here: https://docs.openstack.org/contributors/common/irc.html#setup-irc Please let me know if you have any questions or issues joining the channel, I would be happy to help. Thanks and Best Regards, Ildikó From Venkata.Veldanda at radisys.com Fri Jan 22 17:36:20 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Fri, 22 Jan 2021 17:36:20 +0000 Subject: [Starlingx-discuss] Intel N3000 FPGA & support for igb_uio module In-Reply-To: References: Message-ID: Thanks Mary, Hi, All - Regarding 2] igb_uio I found the igb_uio kernel module at the below location which doesn't seem to be loaded by default. controller-0:/lib/modules# find . -name *.ko |grep igb ./4.18.0-147.3.1.rt24.96.el8_1.tis.8.x86_64/extra/igb_uio/igb_uio.ko Is there any other reason why it isn't loaded by default?. Is this the target module to be loaded to work with igb_uio ? Regards, Venkata Veldanda From: Camp, MaryX Sent: Friday, January 22, 2021 9:06 PM To: Venkata Ramana Veldanda ; starlingx-discuss at lists.starlingx.io Subject: RE: Intel N3000 FPGA & support for igb_uio module The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Hi Venkata, Regarding 1] The StarlingX docs team is upstreaming content at the moment. There is more N3000 FPGA info in the Node Management guide: https://docs.starlingx.io/node_management/index.html Please see these specific sections: https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/n3000-overview.html https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.html I hope this is helpful. thanks, Mary Camp Kelly Services Technical Writer | maryx.camp at intel.com From: Venkata Ramana Veldanda > Sent: Friday, January 22, 2021 4:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intel N3000 FPGA & support for igb_uio module Hi Team, 1] I am using StarlingX 4.0 and trying to use the below guide to setup N3000 Vista Creek FPGA card. https://docs.starlingx.io/configuration/intel_n3000_fpga.html ~(keystone_admin)$ system device-image-upload imagefile root-key pci_vendor pci_device --key-signature key_signature --name imagename --description description --image-version version As part of my N3000 package I see some set of installer images, NVM package updates, iavf driver packages etc. However I am looking for the specific parameters that are highlighted above but I don't find. Anyone has an idea what does the file name look like for the root-key or the key_signature? On my baremetal (CentOS vanilla) installation I was following the standard procedure defined "https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-ias-n3000.pdf" but there I didn't have to use any such key etc. Any help would be appreciated. 2] Secondly, in StarlingX 4.0 I don't find igb_uio module present on the host. Is it currently supported as part of stx 4.0? controller-0:~$ lsmod |grep igb_uio controller-0:~$ Per documentation I see the below The supported VF driver(s) are currently: - igb_uio - vfio Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Jan 22 20:53:56 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 22 Jan 2021 15:53:56 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: > > CENGN remains out of service > > > AC to the server room has been restored. They are now working some > firewall issues. > > > They hope to have it restored in a few hours. > > > Scott > > > > On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >> The hosting company had an issue with their servers, they are working >> on it. They hope to be back online mid afternoon (Jan 21, Eastern >> Standard Time). >> ------------------------------------------------------------------------ >> *From:* Panech, Davlet >> *Sent:* January 21, 2021 9:56 AM >> *To:* Dimofte, Alexandru ; >> starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: Cengn Mirror server in down?! >> Thanks Alexandru, we are looking into it. >> >> ------------------------------------------------------------------------ >> *From:* Dimofte, Alexandru >> *Sent:* January 21, 2021 3:24 AM >> *To:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >> >> Hello guys, >> >> I observed, trying to connect to >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , >> that cengn mirror server is down. >> >> Best regards, >> >> Alex >> >> Logo Description automatically generated >> >> >> >> Dimofte Alexandru >> >> Software Engineer >> >> STARLINGX TEAM >> >> Skype no: +40 336403734 >> >> Personal Mobile: +40 743167456 >> >> alexandru.dimofte at intel.com >> >> Intel Romania >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From build.starlingx at gmail.com Sat Jan 23 02:32:09 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Jan 2021 21:32:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 1332 - Failure! Message-ID: <423941509.2.1611369130715.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 1332 Status: Failure Timestamp: 20210123T023153Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210123T023001Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-compiler MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210123T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20210123T023001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210123T023001Z/logs DOCKER_BUILD_TAG: master-compiler-20210123T023001Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210123T023001Z/logs LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Sat Jan 23 02:32:12 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Jan 2021 21:32:12 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 432 - Still Failing! In-Reply-To: null References: null Message-ID: <1150052976.5.1611369133462.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 432 Status: Still Failing Timestamp: 20210123T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210123T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Jan 23 05:34:08 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 23 Jan 2021 00:34:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 433 - Still Failing! In-Reply-To: <1698208138.3.1611369131328.JavaMail.javamailuser@localhost> References: <1698208138.3.1611369131328.JavaMail.javamailuser@localhost> Message-ID: <714124642.10.1611380049317.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 433 Status: Still Failing Timestamp: 20210123T052810Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210123T052810Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Jan 23 05:39:17 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 23 Jan 2021 00:39:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1135 - Failure! Message-ID: <632438327.13.1611380358348.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1135 Status: Failure Timestamp: 20210123T053324Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210123T053001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210123T053001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210123T053001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210123T053001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sat Jan 23 05:39:20 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 23 Jan 2021 00:39:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 807 - Still Failing! In-Reply-To: <817778360.1041.1611312309791.JavaMail.javamailuser@localhost> References: <817778360.1041.1611312309791.JavaMail.javamailuser@localhost> Message-ID: <1888876336.16.1611380360622.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 807 Status: Still Failing Timestamp: 20210123T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210123T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Sat Jan 23 07:24:42 2021 From: scott.little at windriver.com (Scott Little) Date: Sat, 23 Jan 2021 02:24:42 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: > > CENGN remains out of service. > > > A new problem has been identified with ceph storage. > > > They continue to work the outage. > > > Scott > > > > > On 2021-01-22 9:55 a.m., Scott Little wrote: >> >> CENGN remains out of service >> >> >> AC to the server room has been restored. They are now working some >> firewall issues. >> >> >> They hope to have it restored in a few hours. >> >> >> Scott >> >> >> >> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>> The hosting company had an issue with their servers, they are >>> working on it. They hope to be back online mid afternoon (Jan 21, >>> Eastern Standard Time). >>> ------------------------------------------------------------------------ >>> *From:* Panech, Davlet >>> *Sent:* January 21, 2021 9:56 AM >>> *To:* Dimofte, Alexandru ; >>> starlingx-discuss at lists.starlingx.io >>> >>> *Subject:* Re: Cengn Mirror server in down?! >>> Thanks Alexandru, we are looking into it. >>> >>> ------------------------------------------------------------------------ >>> *From:* Dimofte, Alexandru >>> *Sent:* January 21, 2021 3:24 AM >>> *To:* starlingx-discuss at lists.starlingx.io >>> >>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>> >>> Hello guys, >>> >>> I observed, trying to connect to >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , >>> that cengn mirror server is down. >>> >>> Best regards, >>> >>> Alex >>> >>> Logo Description automatically generated >>> >>> >>> >>> Dimofte Alexandru >>> >>> Software Engineer >>> >>> STARLINGX TEAM >>> >>> Skype no: +40 336403734 >>> >>> Personal Mobile: +40 743167456 >>> >>> alexandru.dimofte at intel.com >>> >>> Intel Romania >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From build.starlingx at gmail.com Sun Jan 24 03:48:15 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 23 Jan 2021 22:48:15 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 377 - Failure! Message-ID: <201488056.26.1611460096576.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 377 Status: Failure Timestamp: 20210124T032641Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210124T032641Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sun Jan 24 05:55:54 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Jan 2021 00:55:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1136 - Still Failing! In-Reply-To: <732506100.11.1611380356551.JavaMail.javamailuser@localhost> References: <732506100.11.1611380356551.JavaMail.javamailuser@localhost> Message-ID: <10124850.29.1611467755108.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1136 Status: Still Failing Timestamp: 20210124T053254Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210124T053000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210124T053000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210124T053000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210124T053000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Jan 24 05:55:56 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Jan 2021 00:55:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 808 - Still Failing! In-Reply-To: <448986699.14.1611380358947.JavaMail.javamailuser@localhost> References: <448986699.14.1611380358947.JavaMail.javamailuser@localhost> Message-ID: <58363863.32.1611467757177.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 808 Status: Still Failing Timestamp: 20210124T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210124T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 24 08:37:24 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Jan 2021 03:37:24 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 378 - Still Failing! In-Reply-To: <1589005838.24.1611460094033.JavaMail.javamailuser@localhost> References: <1589005838.24.1611460094033.JavaMail.javamailuser@localhost> Message-ID: <1751109897.37.1611477445554.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 378 Status: Still Failing Timestamp: 20210124T075713Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210124T075713Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 24 08:44:29 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Jan 2021 03:44:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1187 - Failure! Message-ID: <76185041.40.1611477870287.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1187 Status: Failure Timestamp: 20210124T082237Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210124T075621Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20210124T075621Z DOCKER_BUILD_ID: jenkins-master-flock-20210124T075621Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210124T075621Z/logs BUILD_IMG: true FULL_BUILD: true PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20210124T075621Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Sun Jan 24 08:44:32 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Jan 2021 03:44:32 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 373 - Still Failing! In-Reply-To: null References: null Message-ID: <1064055789.43.1611477872597.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 373 Status: Still Failing Timestamp: 20210124T075621Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210124T075621Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From yong.hu at intel.com Mon Jan 25 01:50:15 2021 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 25 Jan 2021 01:50:15 +0000 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: Message-ID: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Hi, There was something wrong with Cengn. Now Cengn is back to work now and you can download stx.4.0 from [1]. > “trying to deploy release 4.0 on a CentOS 7.6” StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. For the installation guide, pls refer to [2]. [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html From: open infra Date: Thursday, January 21, 2021 at 7:57 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Accessing StartlingX Images Hi. I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. I am trying to deploy all-in-one simplex deployment using [1] . Where I can download ISO images of StarlingX? It seems the mirror site [2] is down. Is there a CentOS-based guide for StarlingX deployment? [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] http://mirror.starlingx.cengn.ca/mirror/ Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Mon Jan 25 02:43:20 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 25 Jan 2021 08:13:20 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Message-ID: Hi, Please find my inline reply. On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong wrote: > Hi, > > There was something wrong with Cengn. Now Cengn is back to work now and > you can download stx.4.0 from [1]. > Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. Thanks for getting the mirror up and running. > “trying to deploy release 4.0 on a CentOS 7.6” > > StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 > + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. > > For the installation guide, pls refer to [2]. > I have a CentOS 7 (with SELinux enabled) running instance with listed hardware requirements under 'Prepare Host and Environment' [1] and I have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy StarlingX on the CentOS instance. I noticed that in the Ubuntu is listed as software requirements under 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it won't be an issue. [Out of topic question] When I execute setup_network.sh, should I keep following entries as it is (as mentioned in [2] ) or should I change them according to my local network? EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ > > [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html > > > > > > *From: *open infra > *Date: *Thursday, January 21, 2021 at 7:57 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Accessing StartlingX Images > > > > Hi. > > > > I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. > > I am trying to deploy all-in-one simplex deployment using [1] . > > > > > > Where I can download ISO images of StarlingX? > > It seems the mirror site [2] is down. > > > > Is there a CentOS-based guide for StarlingX deployment? > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] http://mirror.starlingx.cengn.ca/mirror/ > > > > Regards > > Danishka > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Venkata.Veldanda at radisys.com Mon Jan 25 08:29:46 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Mon, 25 Jan 2021 08:29:46 +0000 Subject: [Starlingx-discuss] Intel N3000 FPGA update on Starlingx Message-ID: Hi Community We are using Stx4.0 I have couple of questions with respect to the N3000 FPGA update 1. The Intel FPGA PAC N3000 contains two Intel XL710 NICs, memory, and an Intel FPGA. The procedure to upgrade the firmware images of FPGA is given at: https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.html. What is the procedure to upgrade the firmware of XL710 NICs within the N3000? Or we can use the same procedure even for the XL710 NICs? 1. In order to check for the firmware version i.e. already shipped on Intel XL710 NICs, I use the system host-port-list and get the ports mapped to the device ID [0d58] and run "ethtool -i ". Is this the only way to get the base firmware version or is there a system command from Starlingx to achieve this? Best Regards, Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Mon Jan 25 08:18:01 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 25 Jan 2021 13:48:01 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Message-ID: Hi, I was trying to execute setup_configuration.sh but failed with the error 'bootimage.iso is not an ISO type'. I can mount it and also file command confirm it is a bootable ISO. Appreciate if someone can help me on this. $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso is not an ISO type $ ls /mnt/ boot.cat ks.cfg pxeboot boot.msg LiveOS pxeboot_setup.sh controller_ks.cfg memtest repodata EFI net_controller_ks.cfg smallsystem_ks.cfg grub.conf net_smallsystem_ks.cfg smallsystem_lowlatency_ks.cfg images net_smallsystem_lowlatency_ks.cfg splash.png initrd.img net_storage_ks.cfg syslinux.cfg isolinux.bin net_worker_ks.cfg upgrades isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 ks Packages vmlinuz $ file ~/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) $ sha256sum ~/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso *72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a* /home/danishka/StarlingX/ mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso On Mon, Jan 25, 2021 at 8:13 AM open infra wrote: > Hi, > > Please find my inline reply. > > On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong wrote: > >> Hi, >> >> There was something wrong with Cengn. Now Cengn is back to work now and >> you can download stx.4.0 from [1]. >> > Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. > Thanks for getting the mirror up and running. > > > “trying to deploy release 4.0 on a CentOS 7.6” >> >> StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 >> + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. >> >> For the installation guide, pls refer to [2]. >> > > I have a CentOS 7 (with SELinux enabled) running instance with listed > hardware requirements under 'Prepare Host and Environment' [1] and I > have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy > StarlingX on the CentOS instance. > I noticed that in the Ubuntu is listed as software requirements under > 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it > won't be an issue. > > [Out of topic question] > When I execute setup_network.sh, should I keep following entries as it is > (as mentioned in [2] ) or should I change them according to my local > network? > > EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} > EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > [2] > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > >> >> [1] >> http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ >> >> [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html >> >> >> >> >> >> *From: *open infra >> *Date: *Thursday, January 21, 2021 at 7:57 PM >> *To: *"starlingx-discuss at lists.starlingx.io" < >> starlingx-discuss at lists.starlingx.io> >> *Subject: *[Starlingx-discuss] Accessing StartlingX Images >> >> >> >> Hi. >> >> >> >> I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. >> >> I am trying to deploy all-in-one simplex deployment using [1] . >> >> >> >> >> >> Where I can download ISO images of StarlingX? >> >> It seems the mirror site [2] is down. >> >> >> >> Is there a CentOS-based guide for StarlingX deployment? >> >> >> >> [1] >> https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html >> >> [2] http://mirror.starlingx.cengn.ca/mirror/ >> >> >> >> Regards >> >> Danishka >> >> >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Srinivas.Sadagopan at radisys.com Mon Jan 25 11:28:38 2021 From: Srinivas.Sadagopan at radisys.com (Srinivas Sadagopan) Date: Mon, 25 Jan 2021 11:28:38 +0000 Subject: [Starlingx-discuss] Question on N3000 firmware image upgrade Message-ID: Hi - I'm looking at N3000 (Vistacreek) FPGA image management procedures supported by StarlingX as described in this link: https://docs.starlingx.io/configuration/intel_n3000_fpga.html. I have a couple of questions: 1. We usually run scripts to upgrade the FPGA in VC card. There are two binary images - one for BMC, and another the actual FPGA user image: bmc_fw_vista_rot_revd_19ww46.5_signed.bin sr_vista_rot_2x2x25g_19ww43.6_unsigned.bin The upgrade scripts work on these two images to upgrade the BMC firmware, and the FPGA image. 1. In the StarlingX image management procedure, there are commands given to upload the device image, Assign a device label to the device, Apply the device image on one or all supported devices. The question I have is: Can we separately repeat these steps for both images mentioned in point "1" (sr_vista image..., and bmc_fw image..)? 1. There is a statement in https://docs.starlingx.io/configuration/intel_n3000_fpga.html, which says - "The Intel FPGA PAC N3000 as shipped from the factory is expected to have production BMC and factory images. The following procedure describes how to update the user image on a host." Does this mean that StarlingX does not support BMC image update of N3000? Thanks, SSrini -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Jan 25 13:23:03 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 25 Jan 2021 13:23:03 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project In-Reply-To: References: Message-ID: Thanks Qianbin review for my patch. Welcome more review idea. If no more idea, please add R+2 and W+1. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 3:59 PM To: 'Qian, Bin' ; 'Kung, John' ; 'Bart Wensley' ; 'MacDonald, Eric' ; 'Waines, Greg' ; 'Poncea, Ovidiu' Cc: 'starlingx-discuss at lists.starlingx.io' ; Sun, Austin ; Hu, Yong Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qianbin review for my patch. Welcome more review idea. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:24 PM To: 'Qian, Bin' >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qian bin review for my patch, I already update and verified. Please go on review. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:07 PM To: Qian, Bin >; Kung, John >; Bart Wensley >; MacDonald, Eric >; Waines, Greg >; Poncea, Ovidiu > Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:08 PM To: Qian, Bin >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Jan 25 13:23:33 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 25 Jan 2021 13:23:33 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project In-Reply-To: References: Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:04 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:28 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Jan 25 13:23:58 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 25 Jan 2021 13:23:58 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Thanks Dan and John review for my patch. I already update and verified for review comment. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:05 PM To: 'Bailey, Henry Albert (Al)' ; 'Bart Wensley' ; 'Church, Robert' ; 'Chris Friesen' ; 'Penney, Don' ; 'Kung, John' ; 'Waines, Greg' ; 'Voiculeasa, Dan' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: review patch to enable rook-ceph in config project. Thanks Dan review for my patch. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:32 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' >; 'Voiculeasa, Dan' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in config project. Hi Bob and Dan I update patch for story about lifecycle. And finish verification. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 1, add lifecycle for rook-ceph 2, add a function in sysinv-conductor, update_config_for_rook_ceph, which is called in application rook-ceph hook function, in operation post stage 3, cleanup some code as function already move to rook-ceph application's hook Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:03 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Scott.Little at windriver.com Mon Jan 25 16:08:32 2021 From: Scott.Little at windriver.com (Little, Scott) Date: Mon, 25 Jan 2021 16:08:32 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> , Message-ID: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don’t have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From lists at optimcloud.com Mon Jan 25 17:12:26 2021 From: lists at optimcloud.com (Lists) Date: Tue, 26 Jan 2021 00:12:26 +0700 Subject: [Starlingx-discuss] "Disk size requirements not met.\" Message-ID: <01a6193c-a424-754f-0883-b39a67a13707@optimcloud.com> Dell R620 with 146 GB Boot drive and 1TB for OSD ... Any way to get around the disk requirement ? which is why its failing, without "removing" the install fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to provision initial system configuration."} TASK [bootstrap/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 \"cgtsclient.common.http\"\nTraceback (most recent call last):\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1078, in \n    controller = populate_controller_config(client)\n  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1008, in populate_controller_config\n    raise e\ncgtsclient.exc.HTTPInternalServerError: Remote error: SysinvException Disk size requirements not met.\n[u'Traceback (most recent call last):\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py\", line 437, in _process_data\\n    **args)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py\", line 172, in dispatch\\n    result = getattr(proxyobj, method)(ctxt, **kwargs)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py\", line 7663, in create_controller_filesystems\\n    raise exception.SysinvException(\"Disk size requirements not met.\")\\n', u'SysinvException: Disk size requirements not met.\\n'].\n",         "stderr_lines": [             "No handlers could be found for logger \"cgtsclient.common.http\"",             "Traceback (most recent call last):",             "  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1078, in ",             "    controller = populate_controller_config(client)",             "  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1008, in populate_controller_config",             "    raise e",             "cgtsclient.exc.HTTPInternalServerError: Remote error: SysinvException Disk size requirements not met.",             "[u'Traceback (most recent call last):\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py\", line 437, in _process_data\\n    **args)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py\", line 172, in dispatch\\n    result = getattr(proxyobj, method)(ctxt, **kwargs)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py\", line 7663, in create_controller_filesystems\\n    raise exception.SysinvException(\"Disk size requirements not met.\")\\n', u'SysinvException: Disk size requirements not met.\\n']."         ],         "stdout": "Populating system config...\nSystem config completed.\nPopulating load config...\nLoad config completed.\nPopulating management network...\nPopulating pxeboot network...\nPopulating oam network...\nPopulating multicast network...\nPopulating cluster host network...\nPopulating cluster pod network...\nPopulating cluster service network...\nNetwork config completed.\nPopulating/Updating DNS config...\nDNS config completed.\nManagement mac = 00:00:00:00:00:00\nRoot fs device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0\nBoot device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0\nConsole = tty0\nTboot = false\nInstall output = text\nHost values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}\nFailed to update the initial system config.\n",         "stdout_lines": [             "Populating system config...",             "System config completed.",             "Populating load config...",             "Load config completed.",             "Populating management network...",             "Populating pxeboot network...",             "Populating oam network...",             "Populating multicast network...",             "Populating cluster host network...",             "Populating cluster pod network...",             "Populating cluster service network...",             "Network config completed.",             "Populating/Updating DNS config...",             "DNS config completed.",             "Management mac = 00:00:00:00:00:00",             "Root fs device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0",             "Boot device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0",             "Console = tty0",             "Tboot = false",             "Install output = text",             "Host values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}",             "Failed to update the initial system config."         ]     } } From build.starlingx at gmail.com Mon Jan 25 18:02:49 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Jan 2021 13:02:49 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 374 - Still Failing! In-Reply-To: <1641988368.41.1611477870866.JavaMail.javamailuser@localhost> References: <1641988368.41.1611477870866.JavaMail.javamailuser@localhost> Message-ID: <868580455.3.1611597770477.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 374 Status: Still Failing Timestamp: 20210125T175840Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210125T175840Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From lists at optimcloud.com Mon Jan 25 18:03:11 2021 From: lists at optimcloud.com (Lists) Date: Tue, 26 Jan 2021 01:03:11 +0700 Subject: [Starlingx-discuss] simplex all-in-one with VLAN interface not found: host controller-0 if eno1.821 Message-ID: <2581e274-e862-4ba0-a73c-8c2dfdfd6ad9@optimcloud.com> I installed stx with all-in-one on bare metal reading the guide sudo ip address add / dev sudo ip link set up dev sudo ip route add default via dev ping 8.8.8.8 becomes |sudo ip link add link /eno1/ name /eno1.8/61 type vlan id 8|21 sudo ip address add XXX.XXX.XXX.132/25 dev eno0.821 sudo ip link set up dev eno1.821 sudo ip route add default via XXX.XXX.XXX.129 dev eno1.821 ping 8.8.8.8 and it works ssh in... created localhost.yml playbooks run fine source /etc/platform/openrc however OAM_IF=eno1.821 [sysadmin at localhost ~(keystone_admin)]$ system host-if-modify controller-0 $OAM_IF -c platform Interface not found: host controller-0 if eno1.821 so how or what did i miss... ??? -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 26 00:03:11 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Jan 2021 19:03:11 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 375 - Still Failing! In-Reply-To: <1916913566.1.1611597768015.JavaMail.javamailuser@localhost> References: <1916913566.1.1611597768015.JavaMail.javamailuser@localhost> Message-ID: <985465079.8.1611619391840.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 375 Status: Still Failing Timestamp: 20210126T000158Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210126T000158Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Venkata.Veldanda at radisys.com Tue Jan 26 01:11:33 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Tue, 26 Jan 2021 01:11:33 +0000 Subject: [Starlingx-discuss] Query on N3000 image update Message-ID: Hi - I'm looking at N3000 (Vistacreek) FPGA image management procedures supported by StarlingX as described in this link: https://docs.starlingx.io/configuration/intel_n3000_fpga.html. I have a couple of questions: 1. We usually run scripts to upgrade the FPGA in VC card. There are two binary images - one for BMC, and another the actual FPGA user image: bmc_fw_vista_rot_revd_19ww46.5_signed.bin sr_vista_rot_2x2x25g_19ww43.6_unsigned.bin The upgrade scripts work on these two images to upgrade the BMC firmware, and the FPGA image. 1. In the StarlingX image management procedure, there are commands given to upload the device image, Assign a device label to the device, Apply the device image on one or all supported devices. The question I have is: Can we separately repeat these steps for both images mentioned in point "1" (sr_vista image..., and bmc_fw image..)? 1. There is a statement in https://docs.starlingx.io/configuration/intel_n3000_fpga.html, which says - "The Intel FPGA PAC N3000 as shipped from the factory is expected to have production BMC and factory images. The following procedure describes how to update the user image on a host." Does this mean that StarlingX does not support BMC image update of N3000? Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 26 01:25:49 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 26 Jan 2021 01:25:49 +0000 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Message-ID: Hi From my side: The result is: $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors sha256sum bootimage.iso 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb bootimage.iso Would you double check you download iso ? Thanks. BR Austin Sun. From: open infra Sent: Monday, January 25, 2021 4:18 PM To: Hu, Yong Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Accessing StartlingX Images Hi, I was trying to execute setup_configuration.sh but failed with the error 'bootimage.iso is not an ISO type'. I can mount it and also file command confirm it is a bootable ISO. Appreciate if someone can help me on this. $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso is not an ISO type $ ls /mnt/ boot.cat ks.cfg pxeboot boot.msg LiveOS pxeboot_setup.sh controller_ks.cfg memtest repodata EFI net_controller_ks.cfg smallsystem_ks.cfg grub.conf net_smallsystem_ks.cfg smallsystem_lowlatency_ks.cfg images net_smallsystem_lowlatency_ks.cfg splash.png initrd.img net_storage_ks.cfg syslinux.cfg isolinux.bin net_worker_ks.cfg upgrades isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 ks Packages vmlinuz $ file ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) $ sha256sum ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso On Mon, Jan 25, 2021 at 8:13 AM open infra > wrote: Hi, Please find my inline reply. On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong > wrote: Hi, There was something wrong with Cengn. Now Cengn is back to work now and you can download stx.4.0 from [1]. Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. Thanks for getting the mirror up and running. > “trying to deploy release 4.0 on a CentOS 7.6” StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. For the installation guide, pls refer to [2]. I have a CentOS 7 (with SELinux enabled) running instance with listed hardware requirements under 'Prepare Host and Environment' [1] and I have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy StarlingX on the CentOS instance. I noticed that in the Ubuntu is listed as software requirements under 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it won't be an issue. [Out of topic question] When I execute setup_network.sh, should I keep following entries as it is (as mentioned in [2] ) or should I change them according to my local network? EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html From: open infra > Date: Thursday, January 21, 2021 at 7:57 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Accessing StartlingX Images Hi. I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. I am trying to deploy all-in-one simplex deployment using [1] . Where I can download ISO images of StarlingX? It seems the mirror site [2] is down. Is there a CentOS-based guide for StarlingX deployment? [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] http://mirror.starlingx.cengn.ca/mirror/ Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 26 01:29:44 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 26 Jan 2021 01:29:44 +0000 Subject: [Starlingx-discuss] "Disk size requirements not met.\" In-Reply-To: <01a6193c-a424-754f-0883-b39a67a13707@optimcloud.com> References: <01a6193c-a424-754f-0883-b39a67a13707@optimcloud.com> Message-ID: Hi : Please check for HW requirement [1] . The primary Hard Disk is requiring 500GB at least . [1] https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/aio_simplex_hardware.html Thanks. BR Austin Sun. -----Original Message----- From: Lists Sent: Tuesday, January 26, 2021 1:12 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] "Disk size requirements not met.\" Dell R620 with 146 GB Boot drive and 1TB for OSD ... Any way to get around the disk requirement ? which is why its failing, without "removing" the install fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to provision initial system configuration."} TASK [bootstrap/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 \"cgtsclient.common.http\"\nTraceback (most recent call last):\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1078, in \n    controller = populate_controller_config(client)\n  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1008, in populate_controller_config\n    raise e\ncgtsclient.exc.HTTPInternalServerError: Remote error: SysinvException Disk size requirements not met.\n[u'Traceback (most recent call last):\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py\", line 437, in _process_data\\n    **args)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py\", line 172, in dispatch\\n    result = getattr(proxyobj, method)(ctxt, **kwargs)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py\", line 7663, in create_controller_filesystems\\n    raise exception.SysinvException(\"Disk size requirements not met.\")\\n', u'SysinvException: Disk size requirements not met.\\n'].\n",         "stderr_lines": [             "No handlers could be found for logger \"cgtsclient.common.http\"",             "Traceback (most recent call last):",             "  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1078, in ",             "    controller = populate_controller_config(client)",             "  File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611593972.4-271990133113928/populate_initial_config.py\", line 1008, in populate_controller_config",             "    raise e",             "cgtsclient.exc.HTTPInternalServerError: Remote error: SysinvException Disk size requirements not met.",             "[u'Traceback (most recent call last):\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py\", line 437, in _process_data\\n    **args)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py\", line 172, in dispatch\\n    result = getattr(proxyobj, method)(ctxt, **kwargs)\\n', u'  File \"/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py\", line 7663, in create_controller_filesystems\\n    raise exception.SysinvException(\"Disk size requirements not met.\")\\n', u'SysinvException: Disk size requirements not met.\\n']."         ],         "stdout": "Populating system config...\nSystem config completed.\nPopulating load config...\nLoad config completed.\nPopulating management network...\nPopulating pxeboot network...\nPopulating oam network...\nPopulating multicast network...\nPopulating cluster host network...\nPopulating cluster pod network...\nPopulating cluster service network...\nNetwork config completed.\nPopulating/Updating DNS config...\nDNS config completed.\nManagement mac = 00:00:00:00:00:00\nRoot fs device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0\nBoot device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0\nConsole = tty0\nTboot = false\nInstall output = text\nHost values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}\nFailed to update the initial system config.\n",         "stdout_lines": [             "Populating system config...",             "System config completed.",             "Populating load config...",             "Load config completed.",             "Populating management network...",             "Populating pxeboot network...",             "Populating oam network...",             "Populating multicast network...",             "Populating cluster host network...",             "Populating cluster pod network...",             "Populating cluster service network...",             "Network config completed.",             "Populating/Updating DNS config...",             "DNS config completed.",             "Management mac = 00:00:00:00:00:00",             "Root fs device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0",             "Boot device = /dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0",             "Console = tty0",             "Tboot = false",             "Install output = text",             "Host values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:02:00.0-scsi-0:2:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}",             "Failed to update the initial system config."         ]     } } _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Tue Jan 26 02:29:07 2021 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 26 Jan 2021 02:29:07 +0000 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Message-ID: <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> It doesn’t matter that much. Most importantly this image is having “DOS/MBR boot sector”, which will make you avoid the original error. https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/functions.sh iso_image_check() { local ISOIMAGE=$1 if ! file ${ISOIMAGE} | grep "DOS/MBR" > /dev/null; then echo "$ISOIMAGE is not an ISO type" exit -1 fi } From: open infra Date: Tuesday, January 26, 2021 at 10:20 AM To: "Sun, Austin" Cc: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Accessing StartlingX Images Hi, I have downloaded it [1] again to my local machine as well as a remote machine and this is what I got. Still, sha256 is different from what you got. $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors $ sha256sum bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a bootimage.iso [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso Regards, Danishka On Tue, Jan 26, 2021 at 6:55 AM Sun, Austin > wrote: Hi From my side: The result is: $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors sha256sum bootimage.iso 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb bootimage.iso Would you double check you download iso ? Thanks. BR Austin Sun. From: open infra > Sent: Monday, January 25, 2021 4:18 PM To: Hu, Yong > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Accessing StartlingX Images Hi, I was trying to execute setup_configuration.sh but failed with the error 'bootimage.iso is not an ISO type'. I can mount it and also file command confirm it is a bootable ISO. Appreciate if someone can help me on this. $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso is not an ISO type $ ls /mnt/ boot.cat ks.cfg pxeboot boot.msg LiveOS pxeboot_setup.sh controller_ks.cfg memtest repodata EFI net_controller_ks.cfg smallsystem_ks.cfg grub.conf net_smallsystem_ks.cfg smallsystem_lowlatency_ks.cfg images net_smallsystem_lowlatency_ks.cfg splash.png initrd.img net_storage_ks.cfg syslinux.cfg isolinux.bin net_worker_ks.cfg upgrades isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 ks Packages vmlinuz $ file ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) $ sha256sum ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso On Mon, Jan 25, 2021 at 8:13 AM open infra > wrote: Hi, Please find my inline reply. On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong > wrote: Hi, There was something wrong with Cengn. Now Cengn is back to work now and you can download stx.4.0 from [1]. Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. Thanks for getting the mirror up and running. > “trying to deploy release 4.0 on a CentOS 7.6” StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. For the installation guide, pls refer to [2]. I have a CentOS 7 (with SELinux enabled) running instance with listed hardware requirements under 'Prepare Host and Environment' [1] and I have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy StarlingX on the CentOS instance. I noticed that in the Ubuntu is listed as software requirements under 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it won't be an issue. [Out of topic question] When I execute setup_network.sh, should I keep following entries as it is (as mentioned in [2] ) or should I change them according to my local network? EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html From: open infra > Date: Thursday, January 21, 2021 at 7:57 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Accessing StartlingX Images Hi. I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. I am trying to deploy all-in-one simplex deployment using [1] . Where I can download ISO images of StarlingX? It seems the mirror site [2] is down. Is there a CentOS-based guide for StarlingX deployment? [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] http://mirror.starlingx.cengn.ca/mirror/ Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 26 02:34:29 2021 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 26 Jan 2021 02:34:29 +0000 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> Message-ID: There appears to be a corruption of this 4.0.1 ISO on CENGN, presumably related to the troubles over the past few days and ongoing data recovery issues. As far as I can see, the correct uncorrupted ISO has the following checksums: md5: 34db64974221d25626c1df332e1eb11b sha256: 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb The corrupted on currently available on CENGN has: md5: f9a791e38184db3937f052b55ecaf550 sha256: 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a From: Hu, Yong Sent: Monday, January 25, 2021 9:29 PM To: open infra ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Accessing StartlingX Images [Please note this e-mail is from an EXTERNAL e-mail address] It doesn’t matter that much. Most importantly this image is having “DOS/MBR boot sector”, which will make you avoid the original error. https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/functions.sh iso_image_check() { local ISOIMAGE=$1 if ! file ${ISOIMAGE} | grep "DOS/MBR" > /dev/null; then echo "$ISOIMAGE is not an ISO type" exit -1 fi } From: open infra > Date: Tuesday, January 26, 2021 at 10:20 AM To: "Sun, Austin" > Cc: "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Accessing StartlingX Images Hi, I have downloaded it [1] again to my local machine as well as a remote machine and this is what I got. Still, sha256 is different from what you got. $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors $ sha256sum bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a bootimage.iso [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso Regards, Danishka On Tue, Jan 26, 2021 at 6:55 AM Sun, Austin > wrote: Hi From my side: The result is: $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors sha256sum bootimage.iso 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb bootimage.iso Would you double check you download iso ? Thanks. BR Austin Sun. From: open infra > Sent: Monday, January 25, 2021 4:18 PM To: Hu, Yong > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Accessing StartlingX Images Hi, I was trying to execute setup_configuration.sh but failed with the error 'bootimage.iso is not an ISO type'. I can mount it and also file command confirm it is a bootable ISO. Appreciate if someone can help me on this. $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso is not an ISO type $ ls /mnt/ boot.cat ks.cfg pxeboot boot.msg LiveOS pxeboot_setup.sh controller_ks.cfg memtest repodata EFI net_controller_ks.cfg smallsystem_ks.cfg grub.conf net_smallsystem_ks.cfg smallsystem_lowlatency_ks.cfg images net_smallsystem_lowlatency_ks.cfg splash.png initrd.img net_storage_ks.cfg syslinux.cfg isolinux.bin net_worker_ks.cfg upgrades isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 ks Packages vmlinuz $ file ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) $ sha256sum ~/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a /home/danishka/StarlingX/mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso On Mon, Jan 25, 2021 at 8:13 AM open infra > wrote: Hi, Please find my inline reply. On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong > wrote: Hi, There was something wrong with Cengn. Now Cengn is back to work now and you can download stx.4.0 from [1]. Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. Thanks for getting the mirror up and running. > “trying to deploy release 4.0 on a CentOS 7.6” StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. For the installation guide, pls refer to [2]. I have a CentOS 7 (with SELinux enabled) running instance with listed hardware requirements under 'Prepare Host and Environment' [1] and I have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy StarlingX on the CentOS instance. I noticed that in the Ubuntu is listed as software requirements under 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it won't be an issue. [Out of topic question] When I execute setup_network.sh, should I keep following entries as it is (as mentioned in [2] ) or should I change them according to my local network? EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html From: open infra > Date: Thursday, January 21, 2021 at 7:57 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Accessing StartlingX Images Hi. I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. I am trying to deploy all-in-one simplex deployment using [1] . Where I can download ISO images of StarlingX? It seems the mirror site [2] is down. Is there a CentOS-based guide for StarlingX deployment? [1] https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html [2] http://mirror.starlingx.cengn.ca/mirror/ Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 02:19:36 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 26 Jan 2021 07:49:36 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> Message-ID: Hi, I have downloaded it [1] again to my local machine as well as a remote machine and this is what I got. Still, sha256 is different from what you got. $ file bootimage.iso bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors $ sha256sum bootimage.iso 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a bootimage.iso [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso Regards, Danishka On Tue, Jan 26, 2021 at 6:55 AM Sun, Austin wrote: > Hi > > From my side: > > The result is: > > $ file > bootimage.iso > > bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS > (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors > > > > sha256sum bootimage.iso > > 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb > bootimage.iso > > > > Would you double check you download iso ? > > > > Thanks. > > BR > Austin Sun. > > > > *From:* open infra > *Sent:* Monday, January 25, 2021 4:18 PM > *To:* Hu, Yong > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Accessing StartlingX Images > > > > Hi, > > > > I was trying to execute setup_configuration.sh but failed with the error > 'bootimage.iso is not an ISO type'. > > > > I can mount it and also file command confirm it is a bootable ISO. > > Appreciate if someone can help me on this. > > > > $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > is not an ISO type > > $ ls /mnt/ > > boot.cat ks.cfg pxeboot > boot.msg LiveOS pxeboot_setup.sh > controller_ks.cfg memtest repodata > EFI net_controller_ks.cfg smallsystem_ks.cfg > grub.conf net_smallsystem_ks.cfg > smallsystem_lowlatency_ks.cfg > images net_smallsystem_lowlatency_ks.cfg splash.png > initrd.img net_storage_ks.cfg syslinux.cfg > isolinux.bin net_worker_ks.cfg upgrades > isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 > ks Packages vmlinuz > $ file ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: > # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) > > > > $ sha256sum ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > *72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a* > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > > > > > > > > > On Mon, Jan 25, 2021 at 8:13 AM open infra wrote: > > Hi, > > > > Please find my inline reply. > > > > On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong wrote: > > Hi, > > There was something wrong with Cengn. Now Cengn is back to work now and > you can download stx.4.0 from [1]. > > Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. > > Thanks for getting the mirror up and running. > > > > > “trying to deploy release 4.0 on a CentOS 7.6” > > StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 > + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. > > For the installation guide, pls refer to [2]. > > > > I have a CentOS 7 (with SELinux enabled) running instance with listed > hardware requirements under 'Prepare Host and Environment' [1] and I > have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy > StarlingX on the CentOS instance. > > I noticed that in the Ubuntu is listed as software requirements under > 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it > won't be an issue. > > > > [Out of topic question] > > When I execute setup_network.sh, should I keep following entries as it is > (as mentioned in [2] ) or should I change them according to my local > network? > > > > EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} > > EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} > > > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > > > > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ > > [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html > > > > > > *From: *open infra > *Date: *Thursday, January 21, 2021 at 7:57 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Accessing StartlingX Images > > > > Hi. > > > > I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. > > I am trying to deploy all-in-one simplex deployment using [1] . > > > > > > Where I can download ISO images of StarlingX? > > It seems the mirror site [2] is down. > > > > Is there a CentOS-based guide for StarlingX deployment? > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] http://mirror.starlingx.cengn.ca/mirror/ > > > > Regards > > Danishka > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 02:32:03 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 26 Jan 2021 08:02:03 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> Message-ID: Can you confirm that the ISO file I downloaded [1] was the correct ISO (is the hash matches with the one hosted at the server? [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso On Tue, Jan 26, 2021 at 7:59 AM Hu, Yong wrote: > It doesn’t matter that much. Most importantly this image is having “ > DOS/MBR boot sector”, which will make you avoid the original error. > > > > > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/functions.sh > > > > iso_image_check() { > > > > local ISOIMAGE=$1 > > > > if ! file ${ISOIMAGE} | grep "DOS/MBR" > /dev/null; then > > > > echo "$ISOIMAGE is not an ISO type" > > > > exit -1 > > > > fi > > } > > > > > > *From: *open infra > *Date: *Tuesday, January 26, 2021 at 10:20 AM > *To: *"Sun, Austin" > *Cc: *"Hu, Yong" , " > starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *Re: [Starlingx-discuss] Accessing StartlingX Images > > > > Hi, > > > > I have downloaded it [1] again to my local machine as well as a remote > machine and this is what I got. > > Still, sha256 is different from what you got. > > > > $ file bootimage.iso > bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS > (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors > $ sha256sum bootimage.iso > 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a > bootimage.iso > > > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > > > Regards, > > Danishka > > > > On Tue, Jan 26, 2021 at 6:55 AM Sun, Austin wrote: > > Hi > > From my side: > > The result is: > > $ file > bootimage.iso > > bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS > (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors > > > > sha256sum bootimage.iso > > 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb > bootimage.iso > > > > Would you double check you download iso ? > > > > Thanks. > > BR > Austin Sun. > > > > *From:* open infra > *Sent:* Monday, January 25, 2021 4:18 PM > *To:* Hu, Yong > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Accessing StartlingX Images > > > > Hi, > > > > I was trying to execute setup_configuration.sh but failed with the error > 'bootimage.iso is not an ISO type'. > > > > I can mount it and also file command confirm it is a bootable ISO. > > Appreciate if someone can help me on this. > > > > $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > is not an ISO type > > $ ls /mnt/ > > boot.cat ks.cfg pxeboot > boot.msg LiveOS pxeboot_setup.sh > controller_ks.cfg memtest repodata > EFI net_controller_ks.cfg smallsystem_ks.cfg > grub.conf net_smallsystem_ks.cfg > smallsystem_lowlatency_ks.cfg > images net_smallsystem_lowlatency_ks.cfg splash.png > initrd.img net_storage_ks.cfg syslinux.cfg > isolinux.bin net_worker_ks.cfg upgrades > isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 > ks Packages vmlinuz > $ file ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: > # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) > > > > $ sha256sum ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > *72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a* > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > > > > > > > > > On Mon, Jan 25, 2021 at 8:13 AM open infra wrote: > > Hi, > > > > Please find my inline reply. > > > > On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong wrote: > > Hi, > > There was something wrong with Cengn. Now Cengn is back to work now and > you can download stx.4.0 from [1]. > > Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. > > Thanks for getting the mirror up and running. > > > > > “trying to deploy release 4.0 on a CentOS 7.6” > > StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 > + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. > > For the installation guide, pls refer to [2]. > > > > I have a CentOS 7 (with SELinux enabled) running instance with listed > hardware requirements under 'Prepare Host and Environment' [1] and I > have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy > StarlingX on the CentOS instance. > > I noticed that in the Ubuntu is listed as software requirements under > 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it > won't be an issue. > > > > [Out of topic question] > > When I execute setup_network.sh, should I keep following entries as it is > (as mentioned in [2] ) or should I change them according to my local > network? > > > > EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} > > EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} > > > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > > > > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ > > [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html > > > > > > *From: *open infra > *Date: *Thursday, January 21, 2021 at 7:57 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Accessing StartlingX Images > > > > Hi. > > > > I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. > > I am trying to deploy all-in-one simplex deployment using [1] . > > > > > > Where I can download ISO images of StarlingX? > > It seems the mirror site [2] is down. > > > > Is there a CentOS-based guide for StarlingX deployment? > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] http://mirror.starlingx.cengn.ca/mirror/ > > > > Regards > > Danishka > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 02:35:54 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 26 Jan 2021 08:05:54 +0530 Subject: [Starlingx-discuss] Creating bridges for AIO-Simplex Message-ID: Hi, When I execute the setup_network.sh script, I could not reach the host after a few minutes (10-30min). The only change I did was the change of http://paste.openstack.org/show/801972/ I have updated the script with the following IP and the network address. I set the Ethernet IP as the external IP. EXTERNAL_IP=${EXTERNAL_IP:-192.168.170.100/24} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-192.168.100.0/24} [1] https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 02:39:28 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 26 Jan 2021 08:09:28 +0530 Subject: [Starlingx-discuss] Accessing StartlingX Images In-Reply-To: References: <9B7A30D2-94D7-4BC8-BF35-BCA955483A7B@intel.com> <5EE62F04-3916-4EE5-962B-8194D28C35D3@intel.com> Message-ID: Thanks for confirming that I am having the corrupted ISO. Is there a way I can access the correct uncorrupted ISO (probably from a different location)? On Tue, Jan 26, 2021 at 8:04 AM Penney, Don wrote: > There appears to be a corruption of this 4.0.1 ISO on CENGN, presumably > related to the troubles over the past few days and ongoing data recovery > issues. > > > > As far as I can see, the correct uncorrupted ISO has the following > checksums: > > md5: 34db64974221d25626c1df332e1eb11b > > sha256: 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb > > > > The corrupted on currently available on CENGN has: > > md5: f9a791e38184db3937f052b55ecaf550 > > sha256: 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a > > > > *From:* Hu, Yong > *Sent:* Monday, January 25, 2021 9:29 PM > *To:* open infra ; Sun, Austin < > austin.sun at intel.com> > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Accessing StartlingX Images > > > > [Please note this e-mail is from an EXTERNAL e-mail address] > > It doesn’t matter that much. Most importantly this image is having “ > DOS/MBR boot sector”, which will make you avoid the original error. > > > > > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/functions.sh > > > > iso_image_check() { > > > > local ISOIMAGE=$1 > > > > if ! file ${ISOIMAGE} | grep "DOS/MBR" > /dev/null; then > > > > echo "$ISOIMAGE is not an ISO type" > > > > exit -1 > > > > fi > > } > > > > > > *From: *open infra > *Date: *Tuesday, January 26, 2021 at 10:20 AM > *To: *"Sun, Austin" > *Cc: *"Hu, Yong" , " > starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *Re: [Starlingx-discuss] Accessing StartlingX Images > > > > Hi, > > > > I have downloaded it [1] again to my local machine as well as a remote > machine and this is what I got. > > Still, sha256 is different from what you got. > > > > $ file bootimage.iso > bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS > (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors > $ sha256sum bootimage.iso > 72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a > bootimage.iso > > > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > > > Regards, > > Danishka > > > > On Tue, Jan 26, 2021 at 6:55 AM Sun, Austin wrote: > > Hi > > From my side: > > The result is: > > $ file > bootimage.iso > > bootimage.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS > (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 684, 17408 sectors > > > > sha256sum bootimage.iso > > 7ce3b928fdfc5325fccfcbf48407d9f1f0428d6e19572916a21c20270f3889eb > bootimage.iso > > > > Would you double check you download iso ? > > > > Thanks. > > BR > Austin Sun. > > > > *From:* open infra > *Sent:* Monday, January 25, 2021 4:18 PM > *To:* Hu, Yong > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Accessing StartlingX Images > > > > Hi, > > > > I was trying to execute setup_configuration.sh but failed with the error > 'bootimage.iso is not an ISO type'. > > > > I can mount it and also file command confirm it is a bootable ISO. > > Appreciate if someone can help me on this. > > > > $ sudo ./setup_configuration.sh -c simplex -i ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > is not an ISO type > > $ ls /mnt/ > > boot.cat ks.cfg pxeboot > boot.msg LiveOS pxeboot_setup.sh > controller_ks.cfg memtest repodata > EFI net_controller_ks.cfg smallsystem_ks.cfg > grub.conf net_smallsystem_ks.cfg > smallsystem_lowlatency_ks.cfg > images net_smallsystem_lowlatency_ks.cfg splash.png > initrd.img net_storage_ks.cfg syslinux.cfg > isolinux.bin net_worker_ks.cfg upgrades > isolinux.cfg net_worker_lowlatency_ks.cfg vesamenu.c32 > ks Packages vmlinuz > $ file ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso: > # ISO 9660 CD-ROM filesystem data 'oe_iso_boot' (bootable) > > > > $ sha256sum ~/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > *72aed791f9cca0b612b77084fe9ac6bff006dd211ef12e85c54232af1171813a* > /home/danishka/StarlingX/ > mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/bootimage.iso > > > > > > > > > > On Mon, Jan 25, 2021 at 8:13 AM open infra wrote: > > Hi, > > > > Please find my inline reply. > > > > On Mon, Jan 25, 2021 at 7:20 AM Hu, Yong wrote: > > Hi, > > There was something wrong with Cengn. Now Cengn is back to work now and > you can download stx.4.0 from [1]. > > Yes, now I have access StarlingX mirror and downloaded the bootimage.iso. > > Thanks for getting the mirror up and running. > > > > > “trying to deploy release 4.0 on a CentOS 7.6” > > StarlingX itself integrates a CentOS (currently in 4.0, it is kernel 4.18 > + CentOS 7.6 use space), so you don’t have to install a CentOS on your own. > > For the installation guide, pls refer to [2]. > > > > I have a CentOS 7 (with SELinux enabled) running instance with listed > hardware requirements under 'Prepare Host and Environment' [1] and I > have chosen 'Virtual All-in-one Simplex Installation R4.0' option to deploy > StarlingX on the CentOS instance. > > I noticed that in the Ubuntu is listed as software requirements under > 'Prepare Host and Environment' [1] but I choose CentOS 7.6. I hope it > won't be an issue. > > > > [Out of topic question] > > When I execute setup_network.sh, should I keep following entries as it is > (as mentioned in [2] ) or should I change them according to my local > network? > > > > EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} > > EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} > > > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > > > > > [1] > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/iso/ > > [2] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html > > > > > > *From: *open infra > *Date: *Thursday, January 21, 2021 at 7:57 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Accessing StartlingX Images > > > > Hi. > > > > I am new to StarlingX and trying to deploy release 4.0 on a CentOS 7.6. > > I am trying to deploy all-in-one simplex deployment using [1] . > > > > > > Where I can download ISO images of StarlingX? > > It seems the mirror site [2] is down. > > > > Is there a CentOS-based guide for StarlingX deployment? > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_environ.html > > [2] http://mirror.starlingx.cengn.ca/mirror/ > > > > Regards > > Danishka > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 02:56:23 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 26 Jan 2021 08:26:23 +0530 Subject: [Starlingx-discuss] Creating bridges for AIO-Simplex In-Reply-To: References: Message-ID: the system is able to access once remove all bridges (after running dectroy_network.sh) On Tue, Jan 26, 2021 at 8:05 AM open infra wrote: > Hi, > > When I execute the setup_network.sh script, I could not reach the host > after a few minutes (10-30min). The only change I did was the change of > > http://paste.openstack.org/show/801972/ > > I have updated the script with the following IP and the network address. > > I set the Ethernet IP as the external IP. > > EXTERNAL_IP=${EXTERNAL_IP:-192.168.170.100/24} > > EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-192.168.100.0/24} > > [1] > https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh > > Regards > > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 26 05:49:22 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 26 Jan 2021 00:49:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 809 - Still Failing! In-Reply-To: <1604314076.30.1611467755652.JavaMail.javamailuser@localhost> References: <1604314076.30.1611467755652.JavaMail.javamailuser@localhost> Message-ID: <1960587055.11.1611640163326.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 809 Status: Still Failing Timestamp: 20210125T175148Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210125T175148Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Tue Jan 26 05:52:19 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 26 Jan 2021 00:52:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1138 - Failure! Message-ID: <559414268.14.1611640339973.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1138 Status: Failure Timestamp: 20210126T055041Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210126T054923Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210126T054923Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210126T054923Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210126T054923Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From scott.little at windriver.com Tue Jan 26 06:28:08 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 26 Jan 2021 01:28:08 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: The jenkins in the cengn build is offline while we repair the file system on the mirror.  The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end.  However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway.  Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places.   e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing.  I do have build artifacts for builds that were intended to lead up to a 3.0.1 release.  If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1.  Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: > Work continues at CENGN repair damaged repos and to move us to a new > backend infrastructure with better redundancy. > > I still recommend that you avoid using download_mirrir.sh until the > repos are fully repaired.  I don’t have a firm ETA for that, perhaps > two before we have full confidence in the repairs. > > Scott > > > ------------------------------------------------------------------------ > *From:* Scott Little > *Sent:* January 23, 2021 2:24 AM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! > > CENGN is up, but there seems to be significant damage to the > repositories. > > > We are investigate options to restore the repositories to health. > > > I do NOT recommend running download_mirror.sh at this time. > > > Scott > > > > > On 2021-01-22 3:53 p.m., Scott Little wrote: >> >> CENGN remains out of service. >> >> >> A new problem has been identified with ceph storage. >> >> >> They continue to work the outage. >> >> >> Scott >> >> >> >> >> On 2021-01-22 9:55 a.m., Scott Little wrote: >>> >>> CENGN remains out of service >>> >>> >>> AC to the server room has been restored. They are now working some >>> firewall issues. >>> >>> >>> They hope to have it restored in a few hours. >>> >>> >>> Scott >>> >>> >>> >>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>> The hosting company had an issue with their servers, they are >>>> working on it. They hope to be back online mid afternoon (Jan 21, >>>> Eastern Standard Time). >>>> ------------------------------------------------------------------------ >>>> *From:* Panech, Davlet >>>> >>>> *Sent:* January 21, 2021 9:56 AM >>>> *To:* Dimofte, Alexandru >>>> ; >>>> starlingx-discuss at lists.starlingx.io >>>> >>>> >>>> >>>> *Subject:* Re: Cengn Mirror server in down?! >>>> Thanks Alexandru, we are looking into it. >>>> >>>> ------------------------------------------------------------------------ >>>> *From:* Dimofte, Alexandru >>>> >>>> *Sent:* January 21, 2021 3:24 AM >>>> *To:* starlingx-discuss at lists.starlingx.io >>>> >>>> >>>> >>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>> >>>> Hello guys, >>>> >>>> I observed, trying to connect to >>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , >>>> that cengn mirror server is down. >>>> >>>> Best regards, >>>> >>>> Alex >>>> >>>> Logo Description automatically generated >>>> >>>> >>>> >>>> Dimofte Alexandru >>>> >>>> Software Engineer >>>> >>>> STARLINGX TEAM >>>> >>>> Skype no: +40 336403734 >>>> >>>> Personal Mobile: +40 743167456 >>>> >>>> alexandru.dimofte at intel.com >>>> >>>> Intel Romania >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From lists at optimcloud.com Tue Jan 26 07:13:46 2021 From: lists at optimcloud.com (Lists) Date: Tue, 26 Jan 2021 14:13:46 +0700 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: On 1/26/21 1:28 PM, Scott Little wrote: > The jenkins in the cengn build is offline while we repair the file > system on the mirror.  The build machine both read from, and writes to > the mirror, and I don't want it to cause further corruptions while the > mirror is being repaired. > > The cengn mirror has been cut over to the new storage back end.  > However any corrupt files from the old storage back end will remain > corrupted on the new one. > > Restoration of rpm repos will proceed in several phases: > > 1) An audit of all rpm repos is underway.  Rpm's that fail their > checksum are being removed and repodata will be updated to reflect the > missing RPMS. > > 2) The mirror update job (downloading rpms from upstream rpm repos) > will be run to restore as many missing files as possible. Many rpms > may no longer be available as we kept old versions of packages that > upstream drops when a new version is available, > > 3) If rpms that are not available from upstream, but are required for > our build, we can attempt to restore them from one of several > places.   e.g. the inputs directory of various builds, or the > downloads directory on the cengn build server (independent storage > from the mirror) > > 4) Resume building new loads > > > > All of the release iso's on cengn were corrupt. > > > I've been able to restore 4.0.1 and 2.0.1 from the original build > artifacts. > > > Original build artifacts for 3.0.0 are missing.  I do have build > artifacts for builds that were intended to lead up to a 3.0.1 > release.  If a verifiable copy of 3.0.0 can't be found, we may want to > consider issuing a 3.0.1.  Alternatively I can rebuild 3.0.0, but the > file checksums wont match the original build due to embedded timestamps. > > > > Scott OUCH...!!! From ildiko.vancsa at gmail.com Tue Jan 26 10:07:40 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Jan 2021 11:07:40 +0100 Subject: [Starlingx-discuss] Speaking opportunity at Edge Computing World Europe Message-ID: <586108B0-0704-4397-B1EA-EDE79B5D6CE7@gmail.com> Hi StarlingX Community, I’m reaching out to you about a speaking opportunity at the upcoming Edge Computing World Europe event that will be held March 9-11, 2021 in a virtual format. There is a 20-minute long slot that is available to grab if anyone would be interested in having an overview presentation about the project or to talk about any interesting feature or functionality. If you would like to present please reach out to me as soon as possible to discuss the details. Please let me know if you have any questions. Thanks and Best Regards, Ildikó From haochuan.z.chen at intel.com Tue Jan 26 12:36:04 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 26 Jan 2021 12:36:04 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project In-Reply-To: References: Message-ID: Thanks Kung John and Qianbin review for my patch. Welcome more review idea. If no more idea, please add R+2 and W+1. https://review.opendev.org/c/starlingx/ha/+/764588 BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, January 25, 2021 9:23 PM To: 'Qian, Bin' ; 'Kung, John' ; 'Bart Wensley' ; 'MacDonald, Eric' ; 'Waines, Greg' ; 'Poncea, Ovidiu' Cc: 'starlingx-discuss at lists.starlingx.io' ; Sun, Austin ; Hu, Yong Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qianbin review for my patch. Welcome more review idea. If no more idea, please add R+2 and W+1. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 3:59 PM To: 'Qian, Bin' >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qianbin review for my patch. Welcome more review idea. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:24 PM To: 'Qian, Bin' >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Thanks Qian bin review for my patch, I already update and verified. Please go on review. https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:07 PM To: Qian, Bin >; Kung, John >; Bart Wensley >; MacDonald, Eric >; Waines, Greg >; Poncea, Ovidiu > Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin >; Hu, Yong > Subject: RE: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:08 PM To: Qian, Bin >; 'Kung, John' >; 'Bart Wensley' >; 'MacDonald, Eric' >; 'Waines, Greg' >; 'Poncea, Ovidiu' > Cc: 'starlingx-discuss at lists.starlingx.io' >; Sun, Austin >; Hu, Yong > Subject: rook ceph patch review for starlingx/ha project Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 26 12:36:17 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 26 Jan 2021 12:36:17 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project In-Reply-To: References: Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, January 25, 2021 9:24 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:04 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:28 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Jan 26 12:30:03 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 26 Jan 2021 12:30:03 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Thanks Kung John's review. Welcome more review idea for rook-ceph! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, January 25, 2021 9:24 PM To: Bailey, Henry Albert (Al) ; Bart Wensley ; Church, Robert ; Chris Friesen ; Penney, Don ; Kung, John ; Waines, Greg ; Voiculeasa, Dan Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Thanks Dan and John review for my patch. I already update and verified for review comment. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:05 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' >; 'Voiculeasa, Dan' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in config project. Thanks Dan review for my patch. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:32 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' >; 'Voiculeasa, Dan' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in config project. Hi Bob and Dan I update patch for story about lifecycle. And finish verification. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 1, add lifecycle for rook-ceph 2, add a function in sysinv-conductor, update_config_for_rook_ceph, which is called in application rook-ceph hook function, in operation post stage 3, cleanup some code as function already move to rook-ceph application's hook Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:03 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Jan 26 13:06:24 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 26 Jan 2021 13:06:24 +0000 Subject: [Starlingx-discuss] Intel N3000 FPGA update on Starlingx In-Reply-To: References: Message-ID: Venkata, See my replies below. Bart From: Venkata Ramana Veldanda Sent: Monday, January 25, 2021 3:30 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intel N3000 FPGA update on Starlingx Hi Community We are using Stx4.0 I have couple of questions with respect to the N3000 FPGA update 1. The Intel FPGA PAC N3000 contains two Intel XL710 NICs, memory, and an Intel FPGA. The procedure to upgrade the firmware images of FPGA is given at: https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.html. What is the procedure to upgrade the firmware of XL710 NICs within the N3000? Or we can use the same procedure even for the XL710 NICs? [Bart] The procedure you reference can only be used to update the user image on the N3000. To upgrade the firmware on the X710 NICs you would need to follow the manufacturer's instructions. 1. In order to check for the firmware version i.e. already shipped on Intel XL710 NICs, I use the system host-port-list and get the ports mapped to the device ID [0d58] and run "ethtool -i ". Is this the only way to get the base firmware version or is there a system command from Starlingx to achieve this? [Bart] That is the only way I am aware of. Best Regards, Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Jan 26 13:08:03 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 26 Jan 2021 13:08:03 +0000 Subject: [Starlingx-discuss] Question on N3000 firmware image upgrade In-Reply-To: References: Message-ID: SSrini, See my replies below. Bart From: Srinivas Sadagopan Sent: Monday, January 25, 2021 6:29 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question on N3000 firmware image upgrade Hi - I'm looking at N3000 (Vistacreek) FPGA image management procedures supported by StarlingX as described in this link: https://docs.starlingx.io/configuration/intel_n3000_fpga.html. I have a couple of questions: 1. We usually run scripts to upgrade the FPGA in VC card. There are two binary images - one for BMC, and another the actual FPGA user image: bmc_fw_vista_rot_revd_19ww46.5_signed.bin sr_vista_rot_2x2x25g_19ww43.6_unsigned.bin The upgrade scripts work on these two images to upgrade the BMC firmware, and the FPGA image. 1. In the StarlingX image management procedure, there are commands given to upload the device image, Assign a device label to the device, Apply the device image on one or all supported devices. The question I have is: Can we separately repeat these steps for both images mentioned in point "1" (sr_vista image..., and bmc_fw image..)? [Bart] No. The starlingx procedure only supports updating the user image. 1. There is a statement in https://docs.starlingx.io/configuration/intel_n3000_fpga.html, which says - "The Intel FPGA PAC N3000 as shipped from the factory is expected to have production BMC and factory images. The following procedure describes how to update the user image on a host." Does this mean that StarlingX does not support BMC image update of N3000? [Bart] Correct Thanks, SSrini -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 26 16:06:44 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 26 Jan 2021 16:06:44 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: StarlingX Community: As you are all likely aware there has been an extended outage at our CENGN facility. Our build team members and CENGN folks have been working extra hours through the recovery. This likely will require another 2 days before normal builds can occur. In the meantime please note the following impact: 1. If you have a local copy of the mirror and did a repo sync on Jan 20 or earlier you likely can continue to make some progress for your development. 2. Do NOT perform a download mirror step at this time as the mirror is corrupted and being repaired. Also a repo sync may not be successful especially if a commit was merged since Jan 20 that required a .lst file change. 3. Do NOT merge or approve any commits that require a .lst file change. 4. Scott will provide daily email updates on the recovery of the CENGN mirror and will let you know when you can resume doing downloads of the mirror. Thanks for your patience as the recovery is being worked. Frank From: Scott Little Sent: Tuesday, January 26, 2021 1:28 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! The jenkins in the cengn build is offline while we repair the file system on the mirror. The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end. However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway. Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places. e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing. I do have build artifacts for builds that were intended to lead up to a 3.0.1 release. If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don't have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6978 bytes Desc: image001.png URL: From bruce.e.jones at intel.com Tue Jan 26 17:52:00 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 26 Jan 2021 17:52:00 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: Frank, my thanks to you and Scott for your diligence on this issue. The community really appreciates your support! brucej From: Miller, Frank Sent: Tuesday, January 26, 2021 8:07 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! StarlingX Community: As you are all likely aware there has been an extended outage at our CENGN facility. Our build team members and CENGN folks have been working extra hours through the recovery. This likely will require another 2 days before normal builds can occur. In the meantime please note the following impact: 1. If you have a local copy of the mirror and did a repo sync on Jan 20 or earlier you likely can continue to make some progress for your development. 2. Do NOT perform a download mirror step at this time as the mirror is corrupted and being repaired. Also a repo sync may not be successful especially if a commit was merged since Jan 20 that required a .lst file change. 3. Do NOT merge or approve any commits that require a .lst file change. 4. Scott will provide daily email updates on the recovery of the CENGN mirror and will let you know when you can resume doing downloads of the mirror. Thanks for your patience as the recovery is being worked. Frank From: Scott Little > Sent: Tuesday, January 26, 2021 1:28 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! The jenkins in the cengn build is offline while we repair the file system on the mirror. The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end. However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway. Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places. e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing. I do have build artifacts for builds that were intended to lead up to a 3.0.1 release. If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don't have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5650 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Tue Jan 26 18:18:31 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 26 Jan 2021 18:18:31 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 27, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up tomorrow. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210127T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From MohammedAAAbuibaid at cmail.carleton.ca Tue Jan 26 18:45:16 2021 From: MohammedAAAbuibaid at cmail.carleton.ca (Mohammed Abuibaid) Date: Tue, 26 Jan 2021 18:45:16 +0000 Subject: [Starlingx-discuss] Stx Services Documentation/Training In-Reply-To: References: Message-ID: Hi Stx Community, First, I'd like to thank you Austin, and the whole community for the help and support. While installing Stx Distribute Cloud Platform on a bare metal environment (Central Cloud on a server located in Carleton University and a sub cloud on personal off-campus server), we run into networking issues mostly related to the VPN. We think of considering AIO deployment on a virtual environment (either VirtualBox, or KVM). Just wanted to confirm whether Stx Distributed Cloud deployment can be installed on a virtual environment as long as the network (i.e. OAM and management networks) and resource (CPU, RAM and Storage) requirements are fulfilled. We're wondering as the current distributed cloud documentation considers only the bare metal case. Any reply is highly appreciated! Kind regards, Mohammed From: Mohammed Abuibaid Sent: November 27, 2020 12:13 PM To: Sun, Austin Subject: RE: Stx Services Documentation/Training Hi Austin, Super thanks for your prompt response! I'll check this Big link and come back if there is a need. Kind regards, Mohammed From: Sun, Austin > Sent: November 27, 2020 3:50 AM To: Mohammed Abuibaid >; starlingx-discuss at lists.starlingx.io Subject: RE: Stx Services Documentation/Training [External Email] Hi Mohammed: Please check [1] which was shared before for all flock services training material [1] https://drive.google.com/drive/folders/1AvUCq3ojuhNZV6XE8YdRhp9PVxixRIeE BR Austin Sun. From: Mohammed Abuibaid > Sent: Friday, November 27, 2020 12:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Stx Services Documentation/Training Hi Stx Community, We are running a capstone project on Stx edge device management in a Distributed Cloud Architecture. I am looking for documentation/training on Stx Configuration/Host/Service/Fault/Software Management Services. Any help will be highly appreciated. Kind regards, Mohammed This email contains links to content or websites. Always be cautious when clicking on external links or attachments. If in doubt, please forward suspicious emails to phishing at carleton.ca. -----End of Disclaimer----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Jan 26 19:47:07 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 27 Jan 2021 01:17:07 +0530 Subject: [Starlingx-discuss] Creating bridges for AIO-Simplex In-Reply-To: References: Message-ID: Let's say the instance is in the network of 192.168.170.0/24 and Ethernet interface IP is 192.168.170.100/24 In this case, given (following IP and network address) details are correct or should I use different IP range for the external network address of starlingx? EXTERNAL_IP=${EXTERNAL_IP:-192.168.170.100/24} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-192.168.100.0/24} On Tue, Jan 26, 2021 at 8:26 AM open infra wrote: > the system is able to access once remove all bridges (after running > dectroy_network.sh) > > On Tue, Jan 26, 2021 at 8:05 AM open infra wrote: > >> Hi, >> >> When I execute the setup_network.sh script, I could not reach the host >> after a few minutes (10-30min). The only change I did was the change of >> >> http://paste.openstack.org/show/801972/ >> >> I have updated the script with the following IP and the network address. >> >> I set the Ethernet IP as the external IP. >> >> EXTERNAL_IP=${EXTERNAL_IP:-192.168.170.100/24} >> >> EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-192.168.100.0/24} >> >> [1] >> https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt/setup_network.sh >> >> Regards >> >> Danishka >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Jan 27 06:37:53 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jan 2021 01:37:53 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> The audit of repos identified ~13000 corrupted rpms So far ~5000 have been restored from redundant copies within cengn. Aprox 7500 have yet to be assessed.  Those remaining rpms are inputs or outputs of actual builds.  The rpms produced by builds might carry the same files name, but may contain different content due to embedded file dates if not real changes.  Extra care is required to restore from the correct source. If an exact match is unavailable, I may be forced to use a source that is 'near' in time and therefore less likely to contain anything other than trivial file timestamp deltas.  I'm still pondering the implications of such a substitution. That leaves ~500 having no backup within cengn.  Upstream availability has yet to be determined. Scott On 2021-01-26 1:28 a.m., Scott Little wrote: > The jenkins in the cengn build is offline while we repair the file > system on the mirror.  The build machine both read from, and writes to > the mirror, and I don't want it to cause further corruptions while the > mirror is being repaired. > > The cengn mirror has been cut over to the new storage back end.  > However any corrupt files from the old storage back end will remain > corrupted on the new one. > > Restoration of rpm repos will proceed in several phases: > > 1) An audit of all rpm repos is underway.  Rpm's that fail their > checksum are being removed and repodata will be updated to reflect the > missing RPMS. > > 2) The mirror update job (downloading rpms from upstream rpm repos) > will be run to restore as many missing files as possible. Many rpms > may no longer be available as we kept old versions of packages that > upstream drops when a new version is available, > > 3) If rpms that are not available from upstream, but are required for > our build, we can attempt to restore them from one of several > places.   e.g. the inputs directory of various builds, or the > downloads directory on the cengn build server (independent storage > from the mirror) > > 4) Resume building new loads > > > > All of the release iso's on cengn were corrupt. > > > I've been able to restore 4.0.1 and 2.0.1 from the original build > artifacts. > > > Original build artifacts for 3.0.0 are missing.  I do have build > artifacts for builds that were intended to lead up to a 3.0.1 > release.  If a verifiable copy of 3.0.0 can't be found, we may want to > consider issuing a 3.0.1.  Alternatively I can rebuild 3.0.0, but the > file checksums wont match the original build due to embedded timestamps. > > > > Scott > > > > On 2021-01-25 11:08 a.m., Little, Scott wrote: >> Work continues at CENGN repair damaged repos and to move us to a new >> backend infrastructure with better redundancy. >> >> I still recommend that you avoid using download_mirrir.sh until the >> repos are fully repaired.  I don’t have a firm ETA for that, perhaps >> two before we have full confidence in the repairs. >> >> Scott >> >> >> ------------------------------------------------------------------------ >> *From:* Scott Little >> *Sent:* January 23, 2021 2:24 AM >> *To:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >> >> CENGN is up, but there seems to be significant damage to the >> repositories. >> >> >> We are investigate options to restore the repositories to health. >> >> >> I do NOT recommend running download_mirror.sh at this time. >> >> >> Scott >> >> >> >> >> On 2021-01-22 3:53 p.m., Scott Little wrote: >>> >>> CENGN remains out of service. >>> >>> >>> A new problem has been identified with ceph storage. >>> >>> >>> They continue to work the outage. >>> >>> >>> Scott >>> >>> >>> >>> >>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>> >>>> CENGN remains out of service >>>> >>>> >>>> AC to the server room has been restored. They are now working some >>>> firewall issues. >>>> >>>> >>>> They hope to have it restored in a few hours. >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>> The hosting company had an issue with their servers, they are >>>>> working on it. They hope to be back online mid afternoon (Jan 21, >>>>> Eastern Standard Time). >>>>> ------------------------------------------------------------------------ >>>>> *From:* Panech, Davlet >>>>> >>>>> *Sent:* January 21, 2021 9:56 AM >>>>> *To:* Dimofte, Alexandru >>>>> ; >>>>> starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>> Thanks Alexandru, we are looking into it. >>>>> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Dimofte, Alexandru >>>>> >>>>> *Sent:* January 21, 2021 3:24 AM >>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>> >>>>> Hello guys, >>>>> >>>>> I observed, trying to connect to >>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , >>>>> that cengn mirror server is down. >>>>> >>>>> Best regards, >>>>> >>>>> Alex >>>>> >>>>> Logo Description automatically generated >>>>> >>>>> >>>>> >>>>> Dimofte Alexandru >>>>> >>>>> Software Engineer >>>>> >>>>> STARLINGX TEAM >>>>> >>>>> Skype no: +40 336403734 >>>>> >>>>> Personal Mobile: +40 743167456 >>>>> >>>>> alexandru.dimofte at intel.com >>>>> >>>>> Intel Romania >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From scott.little at windriver.com Wed Jan 27 06:44:51 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jan 2021 01:44:51 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> Message-ID: <3680b8d0-e7cd-799d-afee-431c93418b00@windriver.com> One other item The CENGN firewall is currently servicing browser/curl/wget requests, but is refusing some if not all requests originating from yum, possibly depending on the vintage of yum being used. It seems to hinge on the 'agent' field of the http request. Thanks to Davlet for figuring that one out. CENGN is working the problem, and think they have a fix.  We'll test it in the morning. Scott On 2021-01-26 1:28 a.m., Scott Little wrote: > The jenkins in the cengn build is offline while we repair the file > system on the mirror.  The build machine both read from, and writes to > the mirror, and I don't want it to cause further corruptions while the > mirror is being repaired. > > The cengn mirror has been cut over to the new storage back end.  > However any corrupt files from the old storage back end will remain > corrupted on the new one. > > Restoration of rpm repos will proceed in several phases: > > 1) An audit of all rpm repos is underway.  Rpm's that fail their > checksum are being removed and repodata will be updated to reflect the > missing RPMS. > > 2) The mirror update job (downloading rpms from upstream rpm repos) > will be run to restore as many missing files as possible. Many rpms > may no longer be available as we kept old versions of packages that > upstream drops when a new version is available, > > 3) If rpms that are not available from upstream, but are required for > our build, we can attempt to restore them from one of several > places.   e.g. the inputs directory of various builds, or the > downloads directory on the cengn build server (independent storage > from the mirror) > > 4) Resume building new loads > > > > All of the release iso's on cengn were corrupt. > > > I've been able to restore 4.0.1 and 2.0.1 from the original build > artifacts. > > > Original build artifacts for 3.0.0 are missing.  I do have build > artifacts for builds that were intended to lead up to a 3.0.1 > release.  If a verifiable copy of 3.0.0 can't be found, we may want to > consider issuing a 3.0.1.  Alternatively I can rebuild 3.0.0, but the > file checksums wont match the original build due to embedded timestamps. > > > > Scott > > > > On 2021-01-25 11:08 a.m., Little, Scott wrote: >> Work continues at CENGN repair damaged repos and to move us to a new >> backend infrastructure with better redundancy. >> >> I still recommend that you avoid using download_mirrir.sh until the >> repos are fully repaired.  I don’t have a firm ETA for that, perhaps >> two before we have full confidence in the repairs. >> >> Scott >> >> >> ------------------------------------------------------------------------ >> *From:* Scott Little >> *Sent:* January 23, 2021 2:24 AM >> *To:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >> >> CENGN is up, but there seems to be significant damage to the >> repositories. >> >> >> We are investigate options to restore the repositories to health. >> >> >> I do NOT recommend running download_mirror.sh at this time. >> >> >> Scott >> >> >> >> >> On 2021-01-22 3:53 p.m., Scott Little wrote: >>> >>> CENGN remains out of service. >>> >>> >>> A new problem has been identified with ceph storage. >>> >>> >>> They continue to work the outage. >>> >>> >>> Scott >>> >>> >>> >>> >>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>> >>>> CENGN remains out of service >>>> >>>> >>>> AC to the server room has been restored. They are now working some >>>> firewall issues. >>>> >>>> >>>> They hope to have it restored in a few hours. >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>> The hosting company had an issue with their servers, they are >>>>> working on it. They hope to be back online mid afternoon (Jan 21, >>>>> Eastern Standard Time). >>>>> ------------------------------------------------------------------------ >>>>> *From:* Panech, Davlet >>>>> >>>>> *Sent:* January 21, 2021 9:56 AM >>>>> *To:* Dimofte, Alexandru >>>>> ; >>>>> starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>> Thanks Alexandru, we are looking into it. >>>>> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Dimofte, Alexandru >>>>> >>>>> *Sent:* January 21, 2021 3:24 AM >>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>> >>>>> Hello guys, >>>>> >>>>> I observed, trying to connect to >>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , >>>>> that cengn mirror server is down. >>>>> >>>>> Best regards, >>>>> >>>>> Alex >>>>> >>>>> Logo Description automatically generated >>>>> >>>>> >>>>> >>>>> Dimofte Alexandru >>>>> >>>>> Software Engineer >>>>> >>>>> STARLINGX TEAM >>>>> >>>>> Skype no: +40 336403734 >>>>> >>>>> Personal Mobile: +40 743167456 >>>>> >>>>> alexandru.dimofte at intel.com >>>>> >>>>> Intel Romania >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From admin at zhangqi.net Wed Jan 27 07:52:48 2021 From: admin at zhangqi.net (Qi Zhang) Date: Wed, 27 Jan 2021 15:52:48 +0800 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: <3680b8d0-e7cd-799d-afee-431c93418b00@windriver.com> References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <3680b8d0-e7cd-799d-afee-431c93418b00@windriver.com> Message-ID: Hi Guys, Based on this issue, do you have any plan to make mirror list or supoort rsync so we can sync startingx packages. Thanks! On Wed, Jan 27, 2021 at 2:44 PM Scott Little wrote: > One other item > > > The CENGN firewall is currently servicing browser/curl/wget requests, but > is refusing some if not all requests originating from yum, possibly > depending on the vintage of yum being used. > > > It seems to hinge on the 'agent' field of the http request. Thanks to > Davlet for figuring that one out. > > > CENGN is working the problem, and think they have a fix. We'll test it in > the morning. > > > Scott > > > > On 2021-01-26 1:28 a.m., Scott Little wrote: > > The jenkins in the cengn build is offline while we repair the file system > on the mirror. The build machine both read from, and writes to the mirror, > and I don't want it to cause further corruptions while the mirror is being > repaired. > > The cengn mirror has been cut over to the new storage back end. However > any corrupt files from the old storage back end will remain corrupted on > the new one. > > Restoration of rpm repos will proceed in several phases: > > 1) An audit of all rpm repos is underway. Rpm's that fail their checksum > are being removed and repodata will be updated to reflect the missing RPMS. > > 2) The mirror update job (downloading rpms from upstream rpm repos) will > be run to restore as many missing files as possible. Many rpms may no > longer be available as we kept old versions of packages that upstream drops > when a new version is available, > > 3) If rpms that are not available from upstream, but are required for our > build, we can attempt to restore them from one of several places. e.g. > the inputs directory of various builds, or the downloads directory on the > cengn build server (independent storage from the mirror) > > 4) Resume building new loads > > > > All of the release iso's on cengn were corrupt. > > > I've been able to restore 4.0.1 and 2.0.1 from the original build > artifacts. > > > Original build artifacts for 3.0.0 are missing. I do have build artifacts > for builds that were intended to lead up to a 3.0.1 release. If a > verifiable copy of 3.0.0 can't be found, we may want to consider issuing a > 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont > match the original build due to embedded timestamps. > > > > Scott > > > > On 2021-01-25 11:08 a.m., Little, Scott wrote: > > Work continues at CENGN repair damaged repos and to move us to a new > backend infrastructure with better redundancy. > > I still recommend that you avoid using download_mirrir.sh until the repos > are fully repaired. I don’t have a firm ETA for that, perhaps two before > we have full confidence in the repairs. > > Scott > > > ------------------------------ > *From:* Scott Little > > *Sent:* January 23, 2021 2:24 AM > *To:* starlingx-discuss at lists.starlingx.io > > > *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! > > > CENGN is up, but there seems to be significant damage to the > repositories. > > > We are investigate options to restore the repositories to health. > > > I do NOT recommend running download_mirror.sh at this time. > > > Scott > > > > > On 2021-01-22 3:53 p.m., Scott Little wrote: > > CENGN remains out of service. > > > A new problem has been identified with ceph storage. > > > They continue to work the outage. > > > Scott > > > > > On 2021-01-22 9:55 a.m., Scott Little wrote: > > CENGN remains out of service > > > AC to the server room has been restored. They are now working some > firewall issues. > > > They hope to have it restored in a few hours. > > > Scott > > > > On 2021-01-21 10:07 a.m., Panech, Davlet wrote: > > The hosting company had an issue with their servers, they are working on > it. They hope to be back online mid afternoon (Jan 21, Eastern Standard > Time). > ------------------------------ > *From:* Panech, Davlet > > *Sent:* January 21, 2021 9:56 AM > *To:* Dimofte, Alexandru > ; starlingx-discuss at lists.starlingx.io > > > *Subject:* Re: Cengn Mirror server in down?! > > Thanks Alexandru, we are looking into it. > > ------------------------------ > *From:* Dimofte, Alexandru > > *Sent:* January 21, 2021 3:24 AM > *To:* starlingx-discuss at lists.starlingx.io > > > *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! > > > Hello guys, > > > > I observed, trying to connect to > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that > cengn mirror server is down. > > > > Best regards, > > Alex > > > > [image: Logo Description automatically generated] > > Dimofte Alexandru > > Software Engineer > > STARLINGX TEAM > > Skype no: +40 336403734 > > Personal Mobile: +40 743167456 > > alexandru.dimofte at intel.com > > Intel Romania > > > > > > _______________________________________________ > Starlingx-discuss mailing listStarlingx-discuss at lists.starlingx.iohttp://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing listStarlingx-discuss at lists.starlingx.iohttp://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing listStarlingx-discuss at lists.starlingx.iohttp://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing listStarlingx-discuss at lists.starlingx.iohttp://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing listStarlingx-discuss at lists.starlingx.iohttp://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From Ankush.Rai at commscope.com Wed Jan 27 10:04:21 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 27 Jan 2021 10:04:21 +0000 Subject: [Starlingx-discuss] Central cloud hosting in VM environment In-Reply-To: References: Message-ID: Please reply on this. From: Rai, Ankush Sent: Thursday, January 21, 2021 11:21 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: RE: Central cloud hosting in VM environment We are thinking to host the central cloud in the AWS environment. Please respond if this is supported by starlingx. Thanks, Ankush From: Rai, Ankush Sent: Wednesday, January 20, 2021 5:18 PM To: starlingx-discuss at lists.starlingx.io Subject: Central cloud hosting in VM environment Hi, Is this possible to host the central cloud in the VM environment? We are looking to go for, Virtual All-in-one Duplex or Virtual Standard with Controller Storage based installation for central cloud. But the sub-cloud will be Bare metal based. Regards, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Jan 27 11:43:02 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 27 Jan 2021 11:43:02 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project In-Reply-To: References: Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 26, 2021 8:36 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, January 25, 2021 9:24 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:04 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:28 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang >; Church, Robert >; Chris Friesen >; Penney, Don >; Liu, ZhipengS > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Jan 27 11:42:40 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 27 Jan 2021 11:42:40 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Thank Kung John, AL Bailey and Don Penney review. I rebase my patch and fix merge conflict. https://review.opendev.org/c/starlingx/config/+/720637 BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 26, 2021 8:30 PM To: Bailey, Henry Albert (Al) ; Bart Wensley ; Church, Robert ; Chris Friesen ; Penney, Don ; Kung, John ; Waines, Greg ; Voiculeasa, Dan Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Thanks Kung John's review. Welcome more review idea for rook-ceph! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, January 25, 2021 9:24 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg >; Voiculeasa, Dan > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Thanks Dan and John review for my patch. I already update and verified for review comment. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, January 22, 2021 4:05 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' >; 'Voiculeasa, Dan' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in config project. Thanks Dan review for my patch. Welcome more review idea! https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, January 21, 2021 10:32 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' >; 'Voiculeasa, Dan' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: review patch to enable rook-ceph in config project. Hi Bob and Dan I update patch for story about lifecycle. And finish verification. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/771741 1, add lifecycle for rook-ceph 2, add a function in sysinv-conductor, update_config_for_rook_ceph, which is called in application rook-ceph hook function, in operation post stage 3, cleanup some code as function already move to rook-ceph application's hook Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 19, 2021 9:03 PM To: Bailey, Henry Albert (Al) >; Bart Wensley >; Church, Robert >; Chris Friesen >; Penney, Don >; Kung, John >; Waines, Greg > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in config project. Hi Thanks, John, AL and Penny review for my patch. I l already updated and make verification. Please go on review my patch for config project https://review.opendev.org/c/starlingx/config/+/720637 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:02 PM To: 'Bailey, Henry Albert (Al)' >; 'Bart Wensley' >; 'Church, Robert' >; 'Chris Friesen' >; 'Penney, Don' >; 'Kung, John' >; 'Waines, Greg' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; 'starlingx-discuss at lists.starlingx.io' > Subject: review patch to enable rook-ceph in config project. Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Wed Jan 27 12:38:42 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 27 Jan 2021 12:38:42 +0000 Subject: [Starlingx-discuss] Central cloud hosting in VM environment In-Reply-To: References: Message-ID: Ankush, Starlingx does not support hosting a central cloud in the AWS environment. Bart From: Rai, Ankush Sent: Wednesday, January 27, 2021 5:04 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Central cloud hosting in VM environment [Please note this e-mail is from an EXTERNAL e-mail address] Please reply on this. From: Rai, Ankush Sent: Thursday, January 21, 2021 11:21 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Central cloud hosting in VM environment We are thinking to host the central cloud in the AWS environment. Please respond if this is supported by starlingx. Thanks, Ankush From: Rai, Ankush Sent: Wednesday, January 20, 2021 5:18 PM To: starlingx-discuss at lists.starlingx.io Subject: Central cloud hosting in VM environment Hi, Is this possible to host the central cloud in the VM environment? We are looking to go for, Virtual All-in-one Duplex or Virtual Standard with Controller Storage based installation for central cloud. But the sub-cloud will be Bare metal based. Regards, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From anyrude10 at gmail.com Wed Jan 27 13:57:15 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Wed, 27 Jan 2021 19:27:15 +0530 Subject: [Starlingx-discuss] [Query] StarlingX 4.0 - Storage Network separate from MGMT+Cluster in Bare Metal Standard with Dedicated Storage Model In-Reply-To: References: Message-ID: Hi Team, Can we integrate a pre-deployed Ceph storage cluster (already created by us) with the existing StarlingX Dedicated Storage Model, rather than StarlingX deploying its own Storage nodes. Basically, we need to segregate client-to-storage traffic from Ceph cluster traffic which does not seem to be possible as per the mail thread below in the current implementation. Looking forward for your response. Regards Anirudh Gupta On Mon, Jan 18, 2021 at 7:52 PM Pratik M. wrote: > Hi, > Reading the following, a dedicated storage-only netowrk does not seem to > be possible for the scenario you mention: > > > https://docs.starlingx.io/planning/kubernetes/networks-for-a-system-with-dedicated-storage.html > https://docs.starlingx.io/planning/kubernetes/the-storage-network.html > > Thanks and Regards > > On Mon, Jan 18, 2021 at 6:18 PM Anirudh Gupta wrote: > >> Gentle Reminder !!!!! >> >> Hi Team, >> >> Can someone help me in regard to the below mail shared. >> >> *Queris: * >> 1. Is it possible to have a storage network which is separate from >> mgmt+cluster networks? So that all the storage traffic passes only >> through that network >> 2. Is there a way to separate client traffic from Storage cluster >> traffic (running on Mgmt+Cluster Host NW) if we enable Ceph Metadata server >> on Controller nodes? >> >> Regards >> Anirudh Gupta >> >> On Wed, Jan 13, 2021 at 3:37 PM Anirudh Gupta >> wrote: >> >>> Hi Team, >>> >>> Can someone help me in regard to the below mail shared. >>> >>> *Query: *Is it possible to have a storage network which is separate >>> from mgmt+cluster networks? So that all the storage traffic passes only >>> through that network >>> >>> Regards >>> Anirudh Gupta >>> >>> On Fri, Jan 8, 2021 at 7:41 PM Anirudh Gupta >>> wrote: >>> >>>> Hi Team, >>>> >>>> I am trying to set up a Bare metal Standard with Dedicated Storage >>>> Installation R4.0 >>>> with >>>> 2 Controllers, 2 Storage Nodes and 2 Worker Nodes. >>>> >>>> >>>> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage.html >>>> >>>> >>>> >>>> [image: image.png] >>>> >>>> >>>> >>>> As per the Network Diagram, storage nodes are connected to MGMT + >>>> Cluster Networks and all the traffic flows through this network only. >>>> >>>> >>>> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedicated_storage_install_kubernetes.html#configure-storage-nodes >>>> >>>> >>>> Even the document suggests to assign the cluster-host network to the >>>> MGMT interface for the storage nodes >>>> >>>> system interface-network-assign $NODE mgmt0 cluster-host >>>> >>>> >>>> Is it possible to have a storage network which is separate from >>>> mgmt+cluster networks? So that all the storage traffic passes only >>>> through that network >>>> >>>> Looking forward for your response. >>>> >>>> Regards >>>> Anirudh Gupta >>>> >>>> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 106914 bytes Desc: not available URL: From scott.little at windriver.com Wed Jan 27 14:56:59 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jan 2021 09:56:59 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> Message-ID: Update Of the original ~13000 corrupted rpms, we now have ... 5700 have been restored 2400 have yet to be assessed 1800 having no backup within cengn. Upstream availability has yet to be determined. 3100 I propose to drop as they fall within the 2.0.0 release which is in very bad shape, whereas 2.0.1 is in fairly good shape and worth saving. Scott On 2021-01-27 1:37 a.m., Scott Little wrote: > > The audit of repos identified ~13000 corrupted rpms > > > So far ~5000 have been restored from redundant copies within cengn. > > > Aprox 7500 have yet to be assessed.  Those remaining rpms are inputs > or outputs of actual builds.  The rpms produced by builds might carry > the same files name, but may contain different content due to embedded > file dates if not real changes.  Extra care is required to restore > from the correct source. If an exact match is unavailable, I may be > forced to use a source that is 'near' in time and therefore less > likely to contain anything other than trivial file timestamp deltas.  > I'm still pondering the implications of such a substitution. > > > That leaves ~500 having no backup within cengn.  Upstream availability > has yet to be determined. > > > Scott > > > > On 2021-01-26 1:28 a.m., Scott Little wrote: >> The jenkins in the cengn build is offline while we repair the file >> system on the mirror.  The build machine both read from, and writes >> to the mirror, and I don't want it to cause further corruptions while >> the mirror is being repaired. >> >> The cengn mirror has been cut over to the new storage back end.  >> However any corrupt files from the old storage back end will remain >> corrupted on the new one. >> >> Restoration of rpm repos will proceed in several phases: >> >> 1) An audit of all rpm repos is underway.  Rpm's that fail their >> checksum are being removed and repodata will be updated to reflect >> the missing RPMS. >> >> 2) The mirror update job (downloading rpms from upstream rpm repos) >> will be run to restore as many missing files as possible. Many rpms >> may no longer be available as we kept old versions of packages that >> upstream drops when a new version is available, >> >> 3) If rpms that are not available from upstream, but are required for >> our build, we can attempt to restore them from one of several >> places.   e.g. the inputs directory of various builds, or the >> downloads directory on the cengn build server (independent storage >> from the mirror) >> >> 4) Resume building new loads >> >> >> >> All of the release iso's on cengn were corrupt. >> >> >> I've been able to restore 4.0.1 and 2.0.1 from the original build >> artifacts. >> >> >> Original build artifacts for 3.0.0 are missing.  I do have build >> artifacts for builds that were intended to lead up to a 3.0.1 >> release.  If a verifiable copy of 3.0.0 can't be found, we may want >> to consider issuing a 3.0.1.  Alternatively I can rebuild 3.0.0, but >> the file checksums wont match the original build due to embedded >> timestamps. >> >> >> >> Scott >> >> >> >> On 2021-01-25 11:08 a.m., Little, Scott wrote: >>> Work continues at CENGN repair damaged repos and to move us to a new >>> backend infrastructure with better redundancy. >>> >>> I still recommend that you avoid using download_mirrir.sh until the >>> repos are fully repaired.  I don’t have a firm ETA for that, perhaps >>> two before we have full confidence in the repairs. >>> >>> Scott >>> >>> >>> ------------------------------------------------------------------------ >>> *From:* Scott Little >>> *Sent:* January 23, 2021 2:24 AM >>> *To:* starlingx-discuss at lists.starlingx.io >>> >>> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >>> >>> CENGN is up, but there seems to be significant damage to the >>> repositories. >>> >>> >>> We are investigate options to restore the repositories to health. >>> >>> >>> I do NOT recommend running download_mirror.sh at this time. >>> >>> >>> Scott >>> >>> >>> >>> >>> On 2021-01-22 3:53 p.m., Scott Little wrote: >>>> >>>> CENGN remains out of service. >>>> >>>> >>>> A new problem has been identified with ceph storage. >>>> >>>> >>>> They continue to work the outage. >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> >>>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>>> >>>>> CENGN remains out of service >>>>> >>>>> >>>>> AC to the server room has been restored. They are now working some >>>>> firewall issues. >>>>> >>>>> >>>>> They hope to have it restored in a few hours. >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>>> The hosting company had an issue with their servers, they are >>>>>> working on it. They hope to be back online mid afternoon (Jan 21, >>>>>> Eastern Standard Time). >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Panech, Davlet >>>>>> >>>>>> *Sent:* January 21, 2021 9:56 AM >>>>>> *To:* Dimofte, Alexandru >>>>>> ; >>>>>> starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> >>>>>> >>>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>>> Thanks Alexandru, we are looking into it. >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Dimofte, Alexandru >>>>>> >>>>>> *Sent:* January 21, 2021 3:24 AM >>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> >>>>>> >>>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>>> >>>>>> Hello guys, >>>>>> >>>>>> I observed, trying to connect to >>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ >>>>>> , that cengn mirror server is down. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Alex >>>>>> >>>>>> Logo Description automatically generated >>>>>> >>>>>> >>>>>> >>>>>> Dimofte Alexandru >>>>>> >>>>>> Software Engineer >>>>>> >>>>>> STARLINGX TEAM >>>>>> >>>>>> Skype no: +40 336403734 >>>>>> >>>>>> Personal Mobile: +40 743167456 >>>>>> >>>>>> alexandru.dimofte at intel.com >>>>>> >>>>>> Intel Romania >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From bruce.e.jones at intel.com Wed Jan 27 15:06:50 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 27 Jan 2021 15:06:50 +0000 Subject: [Starlingx-discuss] TSC minutes Jan 27 2021 Message-ID: 1/27/2021 Standing topics One new spec - create infra for stx 6.0 specs: https://review.opendev.org/c/starlingx/specs/+/772079 TSC members please review Other topics? Thank you to Frank, Scott and the Cengn team for their work in the recovery of our build servers! Both redundant servers had data corruption due to a power outage -------------- next part -------------- An HTML attachment was scrubbed... URL: From Venkata.Veldanda at radisys.com Wed Jan 27 15:09:49 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Wed, 27 Jan 2021 15:09:49 +0000 Subject: [Starlingx-discuss] N3000 FPGA image update doesn't complete Message-ID: Hi, We are performing FPGA image update following the procedure defined below https://docs.starlingx.io/node_management/starlingx-kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.html After running the below command, we see that image status stays in pending state for the last 2 images (although we see the first image update is completed). Although the doc says that it may take about 40 minutes, this has been there for 2 hours the image is in pending state. Any suggestions are appreciated. More information below. ~(keystone)admin)$ system host-device-image-update controller-0 [sysadmin at controller-0 ~(keystone_admin)]$ date;system device-image-state-list Wed Jan 27 22:41:30 UTC 2021 +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ | hostname | PCI device address | Device image uuid | status | Update start time | updated_at | +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ | controller-0 | 0000:1c:00.0 | 58bcd3f5-213b-4c16-ac5e-6d6313cc2712 | completed | 2021-01-27T20:18:43.269482+00:00 | 2021-01-27T20:18:50.399593+00:00 | | controller-0 | 0000:1c:00.0 | d31086d2-f7d6-4129-8421-a0d298fa21f1 | pending | None | None | | controller-0 | 0000:1c:00.0 | 3a04429f-916e-46b0-bff9-2f26c0a597c5 | pending | None | None | +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-show controller-0 |grep device_image_update | device_image_update | in-progress The image update was triggered at the below timestamp. bash info 2021-01-27T20:22:48.000 controller-0 -sh: info HISTORY: PID=1380366 UID=42425 system host-device-image-update controller-0 sysinv API has been triggered at the below timestamp. 2021-01-27 20:22:49.440 87255 INFO sysinv.api.controllers.v1.host [-] device_image_update host_uuid=26a50590-bbaa-41e8-a902-533250cca708 Checked after 2 hours nearly and the status is still the same. Wed Jan 27 22:41:30 UTC 2021 +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ | hostname | PCI device address | Device image uuid | status | Update start time | updated_at | +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ | controller-0 | 0000:1c:00.0 | 58bcd3f5-213b-4c16-ac5e-6d6313cc2712 | completed | 2021-01-27T20:18:43.269482+00:00 | 2021-01-27T20:18:50.399593+00:00 | | controller-0 | 0000:1c:00.0 | d31086d2-f7d6-4129-8421-a0d298fa21f1 | pending | None | None | | controller-0 | 0000:1c:00.0 | 3a04429f-916e-46b0-bff9-2f26c0a597c5 | pending | None | None | +--------------+--------------------+--------------------------------------+-----------+----------------------------------+----------------------------------+ Our understanding is that "host-device-image-update" is the command triggered once for all the pending images for controller-0 and that should automatically update all the pending images in one go. Is there a place in /var/log where we can see the logs on the progress and what might be going wrong?. Is it a good idea to do a force lock & unlock to recover from this state? Below are the images that are being updated. controller-0:/opt/platform/device_images# ls -lrt total 44044 -rw-r--r-- 1 root root 1152 Jan 27 19:35 root-key-8086-0b30-58bcd3f5-213b-4c16-ac5e-6d6313cc2712.bit -rw-r--r-- 1 root root 45089792 Jan 27 19:40 functional-8086-0b30-d31086d2-f7d6-4129-8421-a0d298fa21f1.bit -rw-r--r-- 1 root root 1152 Jan 27 19:41 key-revocation-8086-0b30-3a04429f-916e-46b0-bff9-2f26c0a597c5.bit Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Wed Jan 27 15:35:51 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 27 Jan 2021 15:35:51 +0000 Subject: [Starlingx-discuss] Stx Services Documentation/Training In-Reply-To: References: Message-ID: Mohammed, Yes - you can install distributed cloud in a VirtualBox or KVM environment. We don't have specific instructions for this - you would have to follow the distributed cloud documentation but modify the procedure to line up with the documentation for installing virtual servers. As you mention below, the networking setup may be complex if you are trying to run the System Controller on bare metal with virtual subclouds. You are on your own for that. Bart From: Mohammed Abuibaid Sent: Tuesday, January 26, 2021 1:45 PM To: starlingx-discuss at lists.starlingx.io Cc: Sun, Austin Subject: Re: [Starlingx-discuss] Stx Services Documentation/Training [Please note this e-mail is from an EXTERNAL e-mail address] Hi Stx Community, First, I'd like to thank you Austin, and the whole community for the help and support. While installing Stx Distribute Cloud Platform on a bare metal environment (Central Cloud on a server located in Carleton University and a sub cloud on personal off-campus server), we run into networking issues mostly related to the VPN. We think of considering AIO deployment on a virtual environment (either VirtualBox, or KVM). Just wanted to confirm whether Stx Distributed Cloud deployment can be installed on a virtual environment as long as the network (i.e. OAM and management networks) and resource (CPU, RAM and Storage) requirements are fulfilled. We're wondering as the current distributed cloud documentation considers only the bare metal case. Any reply is highly appreciated! Kind regards, Mohammed From: Mohammed Abuibaid Sent: November 27, 2020 12:13 PM To: Sun, Austin > Subject: RE: Stx Services Documentation/Training Hi Austin, Super thanks for your prompt response! I'll check this Big link and come back if there is a need. Kind regards, Mohammed From: Sun, Austin > Sent: November 27, 2020 3:50 AM To: Mohammed Abuibaid >; starlingx-discuss at lists.starlingx.io Subject: RE: Stx Services Documentation/Training [External Email] Hi Mohammed: Please check [1] which was shared before for all flock services training material [1] https://drive.google.com/drive/folders/1AvUCq3ojuhNZV6XE8YdRhp9PVxixRIeE BR Austin Sun. From: Mohammed Abuibaid > Sent: Friday, November 27, 2020 12:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Stx Services Documentation/Training Hi Stx Community, We are running a capstone project on Stx edge device management in a Distributed Cloud Architecture. I am looking for documentation/training on Stx Configuration/Host/Service/Fault/Software Management Services. Any help will be highly appreciated. Kind regards, Mohammed This email contains links to content or websites. Always be cautious when clicking on external links or attachments. If in doubt, please forward suspicious emails to phishing at carleton.ca. -----End of Disclaimer----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 27 15:36:52 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 27 Jan 2021 15:36:52 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Jan 27, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Sanity * CENGN Mirror Issues * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010602.html * due to power outage at CENGN, Scott doing much work to get us back to normal, will need at least the rest of today to get there * he'll reach out to the community if he needs help tracking down good copies of any of the packages that were corrupted * we agreed to not bother fixing up 2.0.0 or 2.0.1, in fact will just get rid of them since we don't support them any more * Scott will keep us posted * meanwhile the community is reminded * don't merge any commits with a .lst file change (because that requires a mirror update) * and don't do a download mirror step * ideally we'd put a -1 on all open reviews * Frank will ask Davlet to do * Gerrit Reviews in Need of Attention * per Austin, reviews are happening for Ceph/Rook - just a couple left to go * Topics for this Week * Speaking opportunity at Edge Computing World Europe (Ildiko) * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010665.html * ARs from Previous Meetings * Bruce/Austin - spec authorship re: RHEL DUP - pending * Bill/Nicolae - docker hub pro account - pending * Open Requests for Help * Stx Services Documentation/Training --- wants to know if he can run DC in a virtual environment * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010674.html * the simple answer is Yes, Bart will provide the more nuanced response * StarlingX Installation Error * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010605.html * Hello team, I am facing problem in installing StarlingX. * The below link has all information about the error which I am facing. * I have raised a defect on 25th of January. This is the bug which I have raised (#1913043 "StrarlingX Installation Error" (Provision Setup)) * https://drive.google.com/drive/folders/1J_gHzisudkNMKuP6BLCuw7mmD3GLsIoW?usp=sharing * https://bugs.launchpad.net/starlingx/+bug/1913043 * Sanath will update the Launchpad to clearly state what he thinks the bug is, with supporting information * Build Matters (if required) * as discussed above -----Original Message----- From: Zvonar, Bill Sent: Tuesday, January 26, 2021 1:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Jan 27, 2021) Hi all, reminder of the weekly TSC/Community calls coming up tomorrow. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210127T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From openinfradn at gmail.com Wed Jan 27 16:37:50 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 27 Jan 2021 22:07:50 +0530 Subject: [Starlingx-discuss] Controller-0 could not download images Message-ID: Hi, I have installed controller-0 and bootstrap was failed at 'Download images and push to local registry'. I noticed that, dns resolution is failing in the controller but not in the host. controller-0:~$ dig docker.io ; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> docker.io ;; global options: +cmd ;; connection timed out; no servers could be reached controller-0:~$ ping quay.io PING quay.io (3.233.133.41) 56(84) bytes of data. --- quay.io ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2054ms I can ping from the controller. I have added following entries to iptables but no luck. sudo iptables -A OUTPUT -p udp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p udp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT sudo iptables -A OUTPUT -p tcp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p tcp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT I am not sure if my network configuration is correct. controller-0:~$ ip route list default via 10.10.10.1 dev ens3 10.10.10.0/24 dev ens3 proto kernel scope link src 10.10.10.3 169.254.0.0/16 dev eth1000 scope link metric 1002 169.254.0.0/16 dev eth1001 scope link metric 1003 169.254.0.0/16 dev ens3 scope link metric 1004 169.254.0.0/16 dev ens4 scope link metric 1005 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown Following is my local routing configuration and host IP is 192.168.10.100. $ ip route list default via 192.168.172.3 dev eno1 proto static metric 100 10.10.10.0/24 dev stxbr1 proto kernel scope link src 10.10.10.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.10.0/24 dev eno1 proto kernel scope link src 192.168.10.100 metric 100 IP -a results available at http://paste.openstack.org/show/802048/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Jan 27 20:46:26 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 27 Jan 2021 21:46:26 +0100 Subject: [Starlingx-discuss] Google Summer of Code Message-ID: <06EBB359-EF1D-4C70-BFBF-B895518C47F2@gmail.com> Hi, I’m reaching out to give you a heads up that the nomination period for organizations to participate in Google Summer of Code is starting on January 29. For more information about the mentoring program and the full timeline please see this web page: https://summerofcode.withgoogle.com/how-it-works/ __The organization application deadline is February 19.__ Would the community be interested in participating? Thanks and Best Regards, Ildikó From maryx.camp at intel.com Wed Jan 27 23:39:40 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 27 Jan 2021 23:39:40 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 27-Jan-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 27-Jan-21 All -- reviews merged since last meeting: 0 All -- bug status -- 19 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config Status/questions/opens Discuss and define review process / PV testing / commit messages for Starlingx docs (Wind River) feature updates Review process: current model - designer emails docs team, here comes new feature and here's the doc about it. Docs team creates the content in appropriate format, adds to the correct guide, etc. We want to be sure the original designer reviews new features in Gerrit before they are merged. Suggestion to add "key reviewers" in commit message as a heads-up. We need to be careful not to +2 reviews that need approval by technical reviewers. Testing: Back in Sept. 2020, Greg and Mary attended Test meeting to ask about looping in the test team to test some of our complicated procedures (ie install/deployment guides)? The proposal was to use launchpads for test request. Greg/Mary to create launchpads for explict testing, and provide query to test team. Test team will review the backlog and have them discussed and assigned in test meeting. How to interwork the STX test process with WR PV testing -> not in current process, maybe that could be added? Maybe this isn't part of the community process? The WR test team could contribute to the upstream efforts by taking ownership of the LP. If a feature is already released as patch (and has undergone internal testing already) then it wouldn't need upstream testing. Next steps: submit doc review for SNMPv3, raise a LP in the test team project, and go from there. FYI, Mary checked the Test team etherpad and it seems that Yang Liu is still leading the team. [https://etherpad.opendev.org/p/stx-test] Extra doc build testing Ron suggests adding script to the end of tox build to identify issues locally before submitting review. This could avoid things like the gray bar issue. Ron is going to look into implementing this. SNMPv3 API changes reviews: AR Mary: change reviews to use this statement: StarlingX supports SNMP v2 and v3, but it is now configured through Helm charts. The pointer to the Fault Management Guide is OK as-is. Change commit message: remove software dependency, add W -1 till final doc review is available. Version dropdown update Moving the openstack starlingx theme into our repo - probably won't work the way we expected of interdependencies (os-api-ref and pbr) New idea - creating our own theme that would be like a "wrapper" around the existing openstackdocstheme, gives us the customization we want Kevin thinks he can amputate some of the unneeded complexity and add our special sauce This would be simpler maintenance for us in the long term, we can rely on the openstack folks to keep going with maintenance of the complicated theme bits. We will need to figure out how it will impact building the API docs which happens via Zuul jobs. This can wait till later in the process. From Ghada.Khalil at windriver.com Thu Jan 28 02:44:56 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 28 Jan 2021 02:44:56 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 27/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases CENGN Filesystem Corruption - Builds are impacted; Scott is working on recovery. - This is impacting developer testing and code delivery stx.5.0 - Milestone-3 - Target date is Jan 29 2021 - Issues with CENGN impacting builds and sanity. - Some features need an extra couple of weeks to get code merged - https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Release team agreed to re-forecast the release milestones as follows: - Milestone-3: 12/15/2021 - Feature Test: 3/1/2021 - Regression Test Test: 3/29/2021 - RC1: 4/5/2021 - Final Regression: 4/19/2021 - Release: 4/26/2021 - Feature Test - https://docs.google.com/spreadsheets/d/1jro4ItdSobB0-fseK_4cOZJHhUyuh_eCBBsDOp_A5Pc/edit#gid=968103774 - Nick/Yang to provide an update - Regression Test - Nick/Yang to provide an update - Documentation - No issues - Candidate feature list was reviewed and Mary & team reached out to the primes for more information From scott.little at windriver.com Thu Jan 28 05:27:41 2021 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Jan 2021 00:27:41 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> Message-ID: Update All known firewall issues have been fixed. Jenkins is now up and running on the build server once again. Our first manually triggered build attempt of the compiler layer is now running Of the original ~13000 corrupted rpms, we now have ... ~9250 have been restored, including all rpms that are knowm inputs to supported builds ~3100 damaged rpms from the 2.0.0 release will not restored.  TSC and community meetings agreed that 2.0.0, being 2 releases out of date, is no longer supported. ~650 Have yet to be restored from Upstream.  The jenkins job that pulls from upstream sources continues to run. I would like to have successful CENGN builds of all layers before you all hammer the new server with your pent-up download_mirror.sh requests.  Please wait a little longer.  We should be back in business sometime tomorrow. Scott On 2021-01-27 9:56 a.m., Scott Little wrote: > Update > > Of the original ~13000 corrupted rpms, we now have ... > > 5700 have been restored > > 2400 have yet to be assessed > > 1800 having no backup within cengn. Upstream availability has yet to > be determined. > > 3100 I propose to drop as they fall within the 2.0.0 release which is > in very bad shape, whereas 2.0.1 is in fairly good shape and worth saving. > > Scott > > > > On 2021-01-27 1:37 a.m., Scott Little wrote: >> >> The audit of repos identified ~13000 corrupted rpms >> >> >> So far ~5000 have been restored from redundant copies within cengn. >> >> >> Aprox 7500 have yet to be assessed.  Those remaining rpms are inputs >> or outputs of actual builds.  The rpms produced by builds might carry >> the same files name, but may contain different content due to >> embedded file dates if not real changes.  Extra care is required to >> restore from the correct source. If an exact match is unavailable, I >> may be forced to use a source that is 'near' in time and therefore >> less likely to contain anything other than trivial file timestamp >> deltas. I'm still pondering the implications of such a substitution. >> >> >> That leaves ~500 having no backup within cengn.  Upstream >> availability has yet to be determined. >> >> >> Scott >> >> >> >> On 2021-01-26 1:28 a.m., Scott Little wrote: >>> The jenkins in the cengn build is offline while we repair the file >>> system on the mirror.  The build machine both read from, and writes >>> to the mirror, and I don't want it to cause further corruptions >>> while the mirror is being repaired. >>> >>> The cengn mirror has been cut over to the new storage back end.  >>> However any corrupt files from the old storage back end will remain >>> corrupted on the new one. >>> >>> Restoration of rpm repos will proceed in several phases: >>> >>> 1) An audit of all rpm repos is underway.  Rpm's that fail their >>> checksum are being removed and repodata will be updated to reflect >>> the missing RPMS. >>> >>> 2) The mirror update job (downloading rpms from upstream rpm repos) >>> will be run to restore as many missing files as possible. Many rpms >>> may no longer be available as we kept old versions of packages that >>> upstream drops when a new version is available, >>> >>> 3) If rpms that are not available from upstream, but are required >>> for our build, we can attempt to restore them from one of several >>> places.   e.g. the inputs directory of various builds, or the >>> downloads directory on the cengn build server (independent storage >>> from the mirror) >>> >>> 4) Resume building new loads >>> >>> >>> >>> All of the release iso's on cengn were corrupt. >>> >>> >>> I've been able to restore 4.0.1 and 2.0.1 from the original build >>> artifacts. >>> >>> >>> Original build artifacts for 3.0.0 are missing.  I do have build >>> artifacts for builds that were intended to lead up to a 3.0.1 >>> release.  If a verifiable copy of 3.0.0 can't be found, we may want >>> to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but >>> the file checksums wont match the original build due to embedded >>> timestamps. >>> >>> >>> >>> Scott >>> >>> >>> >>> On 2021-01-25 11:08 a.m., Little, Scott wrote: >>>> Work continues at CENGN repair damaged repos and to move us to a >>>> new backend infrastructure with better redundancy. >>>> >>>> I still recommend that you avoid using download_mirrir.sh until the >>>> repos are fully repaired.  I don’t have a firm ETA for that, >>>> perhaps two before we have full confidence in the repairs. >>>> >>>> Scott >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> *From:* Scott Little >>>> *Sent:* January 23, 2021 2:24 AM >>>> *To:* starlingx-discuss at lists.starlingx.io >>>> >>>> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >>>> >>>> CENGN is up, but there seems to be significant damage to the >>>> repositories. >>>> >>>> >>>> We are investigate options to restore the repositories to health. >>>> >>>> >>>> I do NOT recommend running download_mirror.sh at this time. >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> >>>> On 2021-01-22 3:53 p.m., Scott Little wrote: >>>>> >>>>> CENGN remains out of service. >>>>> >>>>> >>>>> A new problem has been identified with ceph storage. >>>>> >>>>> >>>>> They continue to work the outage. >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> >>>>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>>>> >>>>>> CENGN remains out of service >>>>>> >>>>>> >>>>>> AC to the server room has been restored. They are now working >>>>>> some firewall issues. >>>>>> >>>>>> >>>>>> They hope to have it restored in a few hours. >>>>>> >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> >>>>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>>>> The hosting company had an issue with their servers, they are >>>>>>> working on it. They hope to be back online mid afternoon (Jan >>>>>>> 21, Eastern Standard Time). >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Panech, Davlet >>>>>>> >>>>>>> *Sent:* January 21, 2021 9:56 AM >>>>>>> *To:* Dimofte, Alexandru >>>>>>> ; >>>>>>> starlingx-discuss at lists.starlingx.io >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>>>> Thanks Alexandru, we are looking into it. >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Dimofte, Alexandru >>>>>>> >>>>>>> *Sent:* January 21, 2021 3:24 AM >>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>>>> >>>>>>> Hello guys, >>>>>>> >>>>>>> I observed, trying to connect to >>>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ >>>>>>> , that cengn mirror server is down. >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Alex >>>>>>> >>>>>>> Logo Description automatically generated >>>>>>> >>>>>>> >>>>>>> >>>>>>> Dimofte Alexandru >>>>>>> >>>>>>> Software Engineer >>>>>>> >>>>>>> STARLINGX TEAM >>>>>>> >>>>>>> Skype no: +40 336403734 >>>>>>> >>>>>>> Personal Mobile: +40 743167456 >>>>>>> >>>>>>> alexandru.dimofte at intel.com >>>>>>> >>>>>>> Intel Romania >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From openinfradn at gmail.com Thu Jan 28 05:43:43 2021 From: openinfradn at gmail.com (open infra) Date: Thu, 28 Jan 2021 11:13:43 +0530 Subject: [Starlingx-discuss] Controller-0 could not download images In-Reply-To: References: Message-ID: iptables rules http://paste.openstack.org/show/802058/ I even added few entries in /etc/hosts files and to get the ansible-playbook running, but no luck. http://paste.openstack.org/show/802059/ outpit of netstat http://paste.openstack.org/show/802060/ On Wed, Jan 27, 2021 at 10:07 PM open infra wrote: > Hi, > > I have installed controller-0 and bootstrap was failed at 'Download images > and push to local registry'. > > I noticed that, dns resolution is failing in the controller but not in the > host. > controller-0:~$ dig docker.io > > ; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> docker.io > ;; global options: +cmd > ;; connection timed out; no servers could be reached > controller-0:~$ ping quay.io > PING quay.io (3.233.133.41) 56(84) bytes of data. > > --- quay.io ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 2054ms > > I can ping from the controller. > I have added following entries to iptables but no luck. > > sudo iptables -A OUTPUT -p udp -d 8.8.4.4,8.8.8.8 --dport 53 -m state > --state NEW,ESTABLISHED -j ACCEPT > sudo iptables -A INPUT -p udp -s 8.8.4.4,8.8.8.8 --sport 53 -m state > --state ESTABLISHED -j ACCEPT > sudo iptables -A OUTPUT -p tcp -d 8.8.4.4,8.8.8.8 --dport 53 -m state > --state NEW,ESTABLISHED -j ACCEPT > sudo iptables -A INPUT -p tcp -s 8.8.4.4,8.8.8.8 --sport 53 -m state > --state ESTABLISHED -j ACCEPT > > I am not sure if my network configuration is correct. > > controller-0:~$ ip route list > default via 10.10.10.1 dev ens3 > 10.10.10.0/24 dev ens3 proto kernel scope link src 10.10.10.3 > 169.254.0.0/16 dev eth1000 scope link metric 1002 > 169.254.0.0/16 dev eth1001 scope link metric 1003 > 169.254.0.0/16 dev ens3 scope link metric 1004 > 169.254.0.0/16 dev ens4 scope link metric 1005 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown > > Following is my local routing configuration and host IP is 192.168.10.100. > $ ip route list > default via 192.168.172.3 dev eno1 proto static metric 100 > 10.10.10.0/24 dev stxbr1 proto kernel scope link src 10.10.10.1 > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > 192.168.10.0/24 dev eno1 proto kernel scope link src 192.168.10.100 > metric 100 > > IP -a results available at http://paste.openstack.org/show/802048/ > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 28 08:02:26 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 28 Jan 2021 08:02:26 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 32, Issue 57 In-Reply-To: References: Message-ID: Hi scott Flock image always builds fail. So my patch to build ceph-manager could not be built. Could you fix this docker image build fail issue. https://review.opendev.org/c/starlingx/utilities/+/760503 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, January 19, 2021 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 32, Issue 57 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Deploying StarlingX without Kubernetes. (open infra) 2. Re: Deploying StarlingX without Kubernetes. (Hu, Yong) 3. [build-report] STX_build_lst_audit - Build # 1482 - Failure! (build.starlingx at gmail.com) 4. Re: [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! (Sun, Austin) 5. Re: Horizon container deployment, Pod status (CrashLoopBackOff) issue. (Kalvala, Haridhar) ---------------------------------------------------------------------- Message: 1 Date: Mon, 18 Jan 2021 20:51:38 +0530 From: open infra To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Message-ID: Content-Type: text/plain; charset="utf-8" Hi, Is it possible to deploy StarlingX without the Kubernetes support? Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Tue, 19 Jan 2021 00:02:58 +0000 From: "Hu, Yong" To: open infra , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Message-ID: Content-Type: text/plain; charset="utf-8" Hi Danishka, There is NO such one dedicated flag to enable or disable K8s during the system deployment. Though, technically you can trim codes to make it. Roughly STX has done some work around K8s installation/configuration/deployment. Mostly the related code is existing in the following projects: starlingx/ansible-playbooks, starlingx/config, starlingx/stx-puppet, starlingx/ha, and starlingx/nfv. BTW: what use cases or production scenarios make you have such a requirements or incentive? Regards, Yong From: open infra Date: Monday, January 18, 2021 at 11:24 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Deploying StarlingX without Kubernetes. Hi, Is it possible to deploy StarlingX without the Kubernetes support? Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 18 Jan 2021 19:36:22 -0500 (EST) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1482 - Failure! Message-ID: <1230257874.991.1611016582771.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_lst_audit Build #: 1482 Status: Failure Timestamp: 20210119T001539Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210119T000110Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210119T000110Z DOCKER_BUILD_ID: jenkins-master-distro-20210119T000110Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210119T000110Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210119T000110Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro ------------------------------ Message: 4 Date: Tue, 19 Jan 2021 01:09:35 +0000 From: "Sun, Austin" To: "build.starlingx at gmail.com" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! Message-ID: Content-Type: text/plain; charset="us-ascii" Hi All: From log [1] Build stx-oidc-client, it seems some go module can not get successfully , I'm not sure if it is network stability issue or not. Log: get "golang.org/x/net/context/ctxhttp": verifying non-authoritative meta tag golang.org/x/net (download) The command '/bin/sh -c go get -d -v ./...' returned a non-zero code: 1 [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs/jenkins-STX_build_docker_flock_images-316.log.html Thanks. BR Austin Sun. -----Original Message----- From: build.starlingx at gmail.com Sent: Monday, January 18, 2021 8:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 316 - Still Failing! Project: STX_build_docker_flock_images Build #: 316 Status: Still Failing Timestamp: 20210118T093215Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210118T053001Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20210118T053001Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/logs PUBLISH_TIMESTAMP: 20210118T053001Z FLOCK_VERSION: master-centos-stable-20210118T053001Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210118T053001Z BUILD_STREAM: stable REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210118T053001Z/outputs REGISTRY: docker.io ------------------------------ Message: 5 Date: Tue, 19 Jan 2021 04:39:40 +0000 From: "Kalvala, Haridhar" To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Cc: "Bailey, Henry Albert (Al)" , "Penney, Don" , "Miller, Frank" , "Mukherjee, Sanjay K" , "Bhat, Gopalkrishna" Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Message-ID: Content-Type: text/plain; charset="utf-8" Hello All, In continuation to below, further I am facing new issues w.r.t python versions compatibility. Requests for some inputs here on how can I solve this ? /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() Complete pod logs : + COMMAND=start + start ++ python -c 'from distutils.sysconfig import get_python_lib; print(get_python_lib())' + SITE_PACKAGES_ROOT=/var/lib/openstack/lib/python3.6/site-packages + rm -f /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + ln -s /etc/openstack-dashboard/local_settings /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + chown -R horizon /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/ + a2enmod headers + a2enmod rewrite + a2dismod status /tmp/horizon.sh: line 17: :wq: command not found + sed -i 's/LoadModule status_module/#LoadModule status_module/' /etc/httpd/conf.modules.d/00-base.conf + '[' -f /etc/apache2/envvars ']' + rm -rf /var/run/apache2/htcacheclean + APACHE_DIR=apache2 + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled ']' + unset PANEL_DIR + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled ']' + unset PANEL_DIR + type -p gettext + cd /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard + /tmp/manage.py compilemessages /var/lib/openstack/lib64/python3.6/site-packages/scss/compiler.py:1430: DeprecationWarning: invalid escape sequence \: result = tb * (i + nesting) + "@media -sass-debug-info{filename{font-family:file\:\/\/%s}line{font-family:\\00003%s}}" % (filename, lineno) + nl /var/lib/openstack/lib64/python3.6/site-packages/scss/cssdefs.py:516: DeprecationWarning: invalid escape sequence \s ''', re.VERBOSE) /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) Traceback (most recent call last): File "/tmp/manage.py", line 19, in execute_from_command_line(sys.argv) File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/var/lib/openstack/lib/python3.6/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 994, in _gcd_import File "", line 971, in _find_and_load File "", line 955, in _find_and_load_unlocked File "", line 665, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in class AbstractBaseUser(models.Model): File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 36, in raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__) django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3. Regards, Haridhar Kalvala From: Hu, Yong Sent: Monday, January 11, 2021 1:58 PM To: Kalvala, Haridhar ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" > Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Bailey, Henry Albert (Al)" >, "Penney, Don" >, "Miller, Frank" >, "Mukherjee, Sanjay K" >, "Bhat, Gopalkrishna" > Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 32, Issue 57 ************************************************* From Bill.Zvonar at windriver.com Thu Jan 28 11:31:56 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 28 Jan 2021 11:31:56 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> Message-ID: Thanks Scott for grinding through this. From: Scott Little Sent: Thursday, January 28, 2021 12:28 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! Update All known firewall issues have been fixed. Jenkins is now up and running on the build server once again. Our first manually triggered build attempt of the compiler layer is now running Of the original ~13000 corrupted rpms, we now have ... ~9250 have been restored, including all rpms that are knowm inputs to supported builds ~3100 damaged rpms from the 2.0.0 release will not restored. TSC and community meetings agreed that 2.0.0, being 2 releases out of date, is no longer supported. ~650 Have yet to be restored from Upstream. The jenkins job that pulls from upstream sources continues to run. I would like to have successful CENGN builds of all layers before you all hammer the new server with your pent-up download_mirror.sh requests. Please wait a little longer. We should be back in business sometime tomorrow. Scott On 2021-01-27 9:56 a.m., Scott Little wrote: Update Of the original ~13000 corrupted rpms, we now have ... 5700 have been restored 2400 have yet to be assessed 1800 having no backup within cengn. Upstream availability has yet to be determined. 3100 I propose to drop as they fall within the 2.0.0 release which is in very bad shape, whereas 2.0.1 is in fairly good shape and worth saving. Scott On 2021-01-27 1:37 a.m., Scott Little wrote: The audit of repos identified ~13000 corrupted rpms So far ~5000 have been restored from redundant copies within cengn. Aprox 7500 have yet to be assessed. Those remaining rpms are inputs or outputs of actual builds. The rpms produced by builds might carry the same files name, but may contain different content due to embedded file dates if not real changes. Extra care is required to restore from the correct source. If an exact match is unavailable, I may be forced to use a source that is 'near' in time and therefore less likely to contain anything other than trivial file timestamp deltas. I'm still pondering the implications of such a substitution. That leaves ~500 having no backup within cengn. Upstream availability has yet to be determined. Scott On 2021-01-26 1:28 a.m., Scott Little wrote: The jenkins in the cengn build is offline while we repair the file system on the mirror. The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end. However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway. Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places. e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing. I do have build artifacts for builds that were intended to lead up to a 3.0.1 release. If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don't have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5187 bytes Desc: image002.png URL: From anyrude10 at gmail.com Thu Jan 28 11:56:17 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Thu, 28 Jan 2021 17:26:17 +0530 Subject: [Starlingx-discuss] [Issue in StarlingX 4.0] Deploying STX on a VLAN Based Network Message-ID: Hi Team, We are deploying StarlingX 4.0 in Dedicated Storage Model and we need to have our management network as VLAN-tagged for deployment reasons. As per the link below, in that case we must configure the optional untagged PXE boot network for PXE booting of new hosts using IPv4. Can someone please elaborate steps to do so. as we are facing issue in PXE booting of Controller-1 https://docs.starlingx.io/planning/kubernetes/network-planning-the-pxe-boot-network.html Regards Anirudh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From OwenYuen at cmail.carleton.ca Thu Jan 28 03:04:11 2021 From: OwenYuen at cmail.carleton.ca (Owen Yuen) Date: Thu, 28 Jan 2021 03:04:11 +0000 Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud Message-ID: Hi all, I’m a student so please bear with me if my questions are rudimentary. I’m trying to setup a AIO duplex distributed cloud setup with one central cloud and one subcloud. I’ve managed to bootstrap the subcloud from the central cloud successfully and the next steps says to continue the installation from the AIO duplex guide starting from “Configure controller-0”. On step 2, I need to run system commands but all of them require the host to be unlocked. I’m not able to unlock the host either since I’m on the host itself. I assume these steps are done on the subcloud controller-0 correct? Any help will be appreciated. Thanks Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Thu Jan 28 10:32:53 2021 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Thu, 28 Jan 2021 10:32:53 +0000 Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. In-Reply-To: References: <07AB03BB-F3E6-4C94-B51B-360559930443@intel.com> Message-ID: Hi, Jfyi.. Below issue of mysqlite with Django on openstack is resolved applying “Chen,Haochuan Z” patch from upstream. https://stackoverflow.com/questions/55657752/django-installing-mysqlclient-error-mysqlclient-1-3-13-or-newer-is-required Fix with guide from stackoverflow. After openstack image upgrade to ussuri, Django upgrade to 2.2, which request mysqlclient newer than 1.3.13, conflict with version 0.9.3 in current image. Fix with WA in above link, and currently we use pymysql not mysql. Closes-Bug: 1908117 Change-Id: Ic7054c6736993394d92bb0aec25397fd22f84d31 Signed-off-by: Chen, Haochuan Z ??From ?? Regards, Haridhar Kalvala From: Kalvala, Haridhar Sent: Tuesday, January 19, 2021 11:50 AM To: Bai, Haiqing ; Hu, Yong ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: RE: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Thank you Haiqing. Yeah, But this is part of scss python package tool(Django-pyscss etc may also need to change) which is used by many others modules which are python2 compiled. Is there any way to specify to use particular use wheel for one module ? Regards, Haridhar Kalvala From: Bai, Haiqing > Sent: Tuesday, January 19, 2021 11:43 AM To: Kalvala, Haridhar >; Hu, Yong >; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) >; Penney, Don >; Miller, Frank >; Mukherjee, Sanjay K >; Bhat, Gopalkrishna > Subject: RE: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. This is py3 upgrade issue. Maybe you should change the code from “inspect.getargspec()” to “inspect.getfullargspec()”. I once fixed the same kind of issue of centos8 on stx/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py: line 60 distributedcloud-client$ git diff distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py diff --git a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py index d40d6ee..e59f52f 100644 --- a/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py +++ b/distributedcloud-client/dcmanagerclient/openstack/common/cliutils.py @@ -57,7 +57,7 @@ def validate_args(fn, *args, **kwargs): :param arg: the positional arguments supplied :param kwargs: the keyword arguments supplied """ - argspec = inspect.getargspec(fn) + argspec = inspect.getfullargspec(fn) num_defaults = len(argspec.defaults or []) B,R Haiqing Bai From: Kalvala, Haridhar Sent: Tuesday, January 19, 2021 12:40 PM To: Hu, Yong ; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) ; Penney, Don ; Miller, Frank ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello All, In continuation to below, further I am facing new issues w.r.t python versions compatibility. Requests for some inputs here on how can I solve this ? /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() Complete pod logs : + COMMAND=start + start ++ python -c 'from distutils.sysconfig import get_python_lib; print(get_python_lib())' + SITE_PACKAGES_ROOT=/var/lib/openstack/lib/python3.6/site-packages + rm -f /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + ln -s /etc/openstack-dashboard/local_settings /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/local_settings.py + chown -R horizon /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard/local/ + a2enmod headers + a2enmod rewrite + a2dismod status /tmp/horizon.sh: line 17: :wq: command not found + sed -i 's/LoadModule status_module/#LoadModule status_module/' /etc/httpd/conf.modules.d/00-base.conf + '[' -f /etc/apache2/envvars ']' + rm -rf /var/run/apache2/htcacheclean + APACHE_DIR=apache2 + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/heat_dashboard/enabled ']' + unset PANEL_DIR + PANEL_DIR=/var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled + '[' -d /var/lib/openstack/lib/python3.6/site-packages/neutron_taas_dashboard/enabled ']' + unset PANEL_DIR + type -p gettext + cd /var/lib/openstack/lib/python3.6/site-packages/openstack_dashboard + /tmp/manage.py compilemessages /var/lib/openstack/lib64/python3.6/site-packages/scss/compiler.py:1430: DeprecationWarning: invalid escape sequence \: result = tb * (i + nesting) + "@media -sass-debug-info{filename{font-family:file\:\/\/%s}line{font-family:\\00003%s}}" % (filename, lineno) + nl /var/lib/openstack/lib64/python3.6/site-packages/scss/cssdefs.py:516: DeprecationWarning: invalid escape sequence \s ''', re.VERBOSE) /var/lib/openstack/lib64/python3.6/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) Traceback (most recent call last): File "/tmp/manage.py", line 19, in execute_from_command_line(sys.argv) File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/openstack/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/var/lib/openstack/lib/python3.6/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/var/lib/openstack/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 994, in _gcd_import File "", line 971, in _find_and_load File "", line 955, in _find_and_load_unlocked File "", line 665, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "/var/lib/openstack/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in class AbstractBaseUser(models.Model): File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/var/lib/openstack/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 36, in raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__) django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3. Regards, Haridhar Kalvala From: Hu, Yong > Sent: Monday, January 11, 2021 1:58 PM To: Kalvala, Haridhar >; starlingx-discuss at lists.starlingx.io Cc: Bailey, Henry Albert (Al) >; Penney, Don >; Miller, Frank >; Mukherjee, Sanjay K >; Bhat, Gopalkrishna > Subject: Re: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. You might get some hints by inspecting the pod by: # kubectl -n openstack describe pod horizon-d777d8b7d-cpvq7 # kubectl -n openstack logs horizon-d777d8b7d-cpvq7 From: "Kalvala, Haridhar" > Date: Monday, January 11, 2021 at 4:19 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Bailey, Henry Albert (Al)" >, "Penney, Don" >, "Miller, Frank" >, "Mukherjee, Sanjay K" >, "Bhat, Gopalkrishna" > Subject: [Starlingx-discuss] Horizon container deployment, Pod status (CrashLoopBackOff) issue. Hello all, Any pointers on how can I debug below CrashLoopBackOff status issue for horizon container image. Pod status : horizon-d777d8b7d-cpvq7 0/1 CrashLoopBackOff 43 3h17m horizon-db-init-4pcd4 0/1 Completed 0 3h17m horizon-db-sync-26ltd 0/1 Completed 0 3h17m Error Log: 2021-01-11 16:06:21.812 414 DEBUG armada.handlers.wait [-] [chart=openstack-horizon]: pod horizon-d777d8b7d-cpvq7 not ready: Waiting for pod horizon-d777d8b7d-cpvq7 to be ready... handle_resource /usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py:260[00m 2021-01-11 16:07:17.488 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:17.612 414 DEBUG armada.handlers.lock [-] Updating lock update_lock /usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py:176[00m 2021-01-11 16:08:19.221 414 ERROR armada.handlers.wait [-] [chart=openstack-horizon]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'][00m 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [-] Chart deploy [openstack-horizon] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada Traceback (most recent call last): 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 225, in handle_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada return self.__get_result() 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise self._exception 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 214, in deploy_chart 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart, cg_test_all_charts, prefix, known_releases) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 248, in execute 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada chart_wait.wait(timer) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 134, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada wait.wait(timeout=timeout) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 294, in wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada modified = self._wait(deadline) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 354, in _wait 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-horizon)). These pods were not ready=['horizon-d777d8b7d-cpvq7'] 2021-01-11 16:08:19.222 414 ERROR armada.handlers.armada [00m 2021-01-11 16:08:19.223 414 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['openstack-horizon'][00m 2021-01-11 16:08:19.625 414 INFO armada.handlers.lock [-] Releasing lock[00m 2021-01-11 16:08:19.668 414 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli Traceback (most recent call last): 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/__init__.py", line 38, in safe_invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli self.invoke() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 213, in invoke 2021-01-11 16:08:19.668 414 ERROR armada.cli resp = self.handle(documents, tiller) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/lock.py", line 81, in func_wrapper 2021-01-11 16:08:19.668 414 ERROR armada.cli return future.result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result 2021-01-11 16:08:19.668 414 ERROR armada.cli return self.__get_result() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2021-01-11 16:08:19.668 414 ERROR armada.cli raise self._exception 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run 2021-01-11 16:08:19.668 414 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/cli/apply.py", line 256, in handle 2021-01-11 16:08:19.668 414 ERROR armada.cli return armada.sync() 2021-01-11 16:08:19.668 414 ERROR armada.cli File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 252, in sync 2021-01-11 16:08:19.668 414 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) 2021-01-11 16:08:19.668 414 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-horizon'] 2021-01-11 16:08:19.668 414 ERROR armada.cli [00m command terminated with exit code 1 Regards, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Thu Jan 28 13:24:01 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 28 Jan 2021 13:24:01 +0000 Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud In-Reply-To: References: Message-ID: Owen - see my comments below... Bart From: Owen Yuen Sent: Wednesday, January 27, 2021 10:04 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, I'm a student so please bear with me if my questions are rudimentary. I'm trying to setup a AIO duplex distributed cloud setup with one central cloud and one subcloud. I've managed to bootstrap the subcloud from the central cloud successfully and the next steps says to continue the installation from the AIO duplex guide starting from "Configure controller-0". On step 2, I need to run system commands but all of them require the host to be unlocked. I'm not able to unlock the host either since I'm on the host itself. I assume these steps are done on the subcloud controller-0 correct? [Bart] Yes - these steps are done on the subcloud controller-0. They are done BEFORE you unlock the subcloud controller - you will see that following these steps will eventually lead to unlocking the subcloud controller. Any help will be appreciated. Thanks Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Jan 28 13:45:15 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 28 Jan 2021 13:45:15 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 27/2020 In-Reply-To: References: Message-ID: My apologies. There is a typo below. The new Milestone-3 date is 2/15/2021 (Feb 15 2021), not 12/15/2021 -----Original Message----- From: Khalil, Ghada Sent: Wednesday, January 27, 2021 9:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Minutes: StarlingX Release Meeting - Jan 27/2020 Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases CENGN Filesystem Corruption - Builds are impacted; Scott is working on recovery. - This is impacting developer testing and code delivery stx.5.0 - Milestone-3 - Target date is Jan 29 2021 - Issues with CENGN impacting builds and sanity. - Some features need an extra couple of weeks to get code merged - https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Release team agreed to re-forecast the release milestones as follows: - Milestone-3: 12/15/2021 - Feature Test: 3/1/2021 - Regression Test Test: 3/29/2021 - RC1: 4/5/2021 - Final Regression: 4/19/2021 - Release: 4/26/2021 - Feature Test - https://docs.google.com/spreadsheets/d/1jro4ItdSobB0-fseK_4cOZJHhUyuh_eCBBsDOp_A5Pc/edit#gid=968103774 - Nick/Yang to provide an update - Regression Test - Nick/Yang to provide an update - Documentation - No issues - Candidate feature list was reviewed and Mary & team reached out to the primes for more information From build.starlingx at gmail.com Thu Jan 28 14:56:08 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 09:56:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1139 - Still Failing! In-Reply-To: <917320287.12.1611640338492.JavaMail.javamailuser@localhost> References: <917320287.12.1611640338492.JavaMail.javamailuser@localhost> Message-ID: <1805259992.3.1611845770967.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1139 Status: Still Failing Timestamp: 20210128T053244Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210128T053000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210128T053000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210128T053000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210128T053000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Thu Jan 28 14:56:12 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 09:56:12 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 811 - Failure! Message-ID: <1050895144.6.1611845773486.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 811 Status: Failure Timestamp: 20210128T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210128T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Thu Jan 28 16:29:24 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Jan 2021 17:29:24 +0100 Subject: [Starlingx-discuss] 2020 Open Infrastructure Foundation Annual Report Now Available Message-ID: The StarlingX community had a strong year in spite of the unprecedented global challenges in 2020. During the first half of 2020, the OpenInfra Foundation Board of Directors confirmed the project as top-level Open Infrastructure project. StarlingX 4.0 was released in August 2020. The platform is architected as a fusion between OpenStack and Kubernetes to create a robust and flexible environment for edge workloads, let them be bare metal, containerized, or virtualized. In the 4.0 release, the majority of the infrastructure services are containerized to ensure easier and more flexible management and operation. The community has also continued to have increased focus on security related functionality during the release cycles in 2020. Last year, the StarlingX community continued to present its strategic relevance, well-defined governance procedures, commitment to technical best practices and open collaboration, and, most importantly, an actively engaged ecosystem of developers and users. The project continues to cultivate a global, engaged and growing community as evidenced by the 2020 stats: the project had 2,237 changes committed by 111 authors from 7 organizations during the year. Thank you to everyone in the StarlingX community for all of the work that went into 2020 and is continuing in 2021 to contribute and support the community. Check out the StarlingX community’s achievements last year from the 2020 OpenInfra Foundation annual report: https://www.openstack.org/annual-reports/2020-openstack-foundation-annual-report Thanks and Best Regards, Ildikó Váncsa Ecosystem Technical Lead Open Infrastructure Foundation From Davlet.Panech at windriver.com Thu Jan 28 17:31:22 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 28 Jan 2021 17:31:22 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> , Message-ID: We just merged a fix for tb.sh/Dockerfile for CENGN-related build problems that may affect some builds, depending on the environment: ________________________________ From: Zvonar, Bill Sent: January 28, 2021 6:31 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! Thanks Scott for grinding through this. From: Scott Little Sent: Thursday, January 28, 2021 12:28 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! Update All known firewall issues have been fixed. Jenkins is now up and running on the build server once again. Our first manually triggered build attempt of the compiler layer is now running Of the original ~13000 corrupted rpms, we now have ... ~9250 have been restored, including all rpms that are knowm inputs to supported builds ~3100 damaged rpms from the 2.0.0 release will not restored. TSC and community meetings agreed that 2.0.0, being 2 releases out of date, is no longer supported. ~650 Have yet to be restored from Upstream. The jenkins job that pulls from upstream sources continues to run. I would like to have successful CENGN builds of all layers before you all hammer the new server with your pent-up download_mirror.sh requests. Please wait a little longer. We should be back in business sometime tomorrow. Scott On 2021-01-27 9:56 a.m., Scott Little wrote: Update Of the original ~13000 corrupted rpms, we now have ... 5700 have been restored 2400 have yet to be assessed 1800 having no backup within cengn. Upstream availability has yet to be determined. 3100 I propose to drop as they fall within the 2.0.0 release which is in very bad shape, whereas 2.0.1 is in fairly good shape and worth saving. Scott On 2021-01-27 1:37 a.m., Scott Little wrote: The audit of repos identified ~13000 corrupted rpms So far ~5000 have been restored from redundant copies within cengn. Aprox 7500 have yet to be assessed. Those remaining rpms are inputs or outputs of actual builds. The rpms produced by builds might carry the same files name, but may contain different content due to embedded file dates if not real changes. Extra care is required to restore from the correct source. If an exact match is unavailable, I may be forced to use a source that is 'near' in time and therefore less likely to contain anything other than trivial file timestamp deltas. I'm still pondering the implications of such a substitution. That leaves ~500 having no backup within cengn. Upstream availability has yet to be determined. Scott On 2021-01-26 1:28 a.m., Scott Little wrote: The jenkins in the cengn build is offline while we repair the file system on the mirror. The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end. However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway. Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places. e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing. I do have build artifacts for builds that were intended to lead up to a 3.0.1 release. If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don’t have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5187 bytes Desc: image002.png URL: From Davlet.Panech at windriver.com Thu Jan 28 17:36:47 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 28 Jan 2021 17:36:47 +0000 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> , , Message-ID: We just merged a fix for tb.sh/Dockerfile for CENGN-related build problems that may affect some builds, depending on the environment: https://review.opendev.org/c/starlingx/tools/+/772790 If you compiled a builder image during the outage (during the last week or so) for the first time, it may affect your builds. The symptoms include this error message from "docker build": rmdir: failed to remove '/var/lib/mock': No such file or directory You may need to refresh your starlingx/tools checkout or cherry pick that commit into any private branches you are interested in building. This patch is only in the master branch. Another workaround is to delete any cached builder images that came out of starlingx/tools/Dockerfile using "docker image rm" etc. Hope this helps, D. ________________________________ From: Panech, Davlet Sent: January 28, 2021 12:31 PM To: Zvonar, Bill ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! We just merged a fix for tb.sh/Dockerfile for CENGN-related build problems that may affect some builds, depending on the environment: ________________________________ From: Zvonar, Bill Sent: January 28, 2021 6:31 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! Thanks Scott for grinding through this. From: Scott Little Sent: Thursday, January 28, 2021 12:28 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! Update All known firewall issues have been fixed. Jenkins is now up and running on the build server once again. Our first manually triggered build attempt of the compiler layer is now running Of the original ~13000 corrupted rpms, we now have ... ~9250 have been restored, including all rpms that are knowm inputs to supported builds ~3100 damaged rpms from the 2.0.0 release will not restored. TSC and community meetings agreed that 2.0.0, being 2 releases out of date, is no longer supported. ~650 Have yet to be restored from Upstream. The jenkins job that pulls from upstream sources continues to run. I would like to have successful CENGN builds of all layers before you all hammer the new server with your pent-up download_mirror.sh requests. Please wait a little longer. We should be back in business sometime tomorrow. Scott On 2021-01-27 9:56 a.m., Scott Little wrote: Update Of the original ~13000 corrupted rpms, we now have ... 5700 have been restored 2400 have yet to be assessed 1800 having no backup within cengn. Upstream availability has yet to be determined. 3100 I propose to drop as they fall within the 2.0.0 release which is in very bad shape, whereas 2.0.1 is in fairly good shape and worth saving. Scott On 2021-01-27 1:37 a.m., Scott Little wrote: The audit of repos identified ~13000 corrupted rpms So far ~5000 have been restored from redundant copies within cengn. Aprox 7500 have yet to be assessed. Those remaining rpms are inputs or outputs of actual builds. The rpms produced by builds might carry the same files name, but may contain different content due to embedded file dates if not real changes. Extra care is required to restore from the correct source. If an exact match is unavailable, I may be forced to use a source that is 'near' in time and therefore less likely to contain anything other than trivial file timestamp deltas. I'm still pondering the implications of such a substitution. That leaves ~500 having no backup within cengn. Upstream availability has yet to be determined. Scott On 2021-01-26 1:28 a.m., Scott Little wrote: The jenkins in the cengn build is offline while we repair the file system on the mirror. The build machine both read from, and writes to the mirror, and I don't want it to cause further corruptions while the mirror is being repaired. The cengn mirror has been cut over to the new storage back end. However any corrupt files from the old storage back end will remain corrupted on the new one. Restoration of rpm repos will proceed in several phases: 1) An audit of all rpm repos is underway. Rpm's that fail their checksum are being removed and repodata will be updated to reflect the missing RPMS. 2) The mirror update job (downloading rpms from upstream rpm repos) will be run to restore as many missing files as possible. Many rpms may no longer be available as we kept old versions of packages that upstream drops when a new version is available, 3) If rpms that are not available from upstream, but are required for our build, we can attempt to restore them from one of several places. e.g. the inputs directory of various builds, or the downloads directory on the cengn build server (independent storage from the mirror) 4) Resume building new loads All of the release iso's on cengn were corrupt. I've been able to restore 4.0.1 and 2.0.1 from the original build artifacts. Original build artifacts for 3.0.0 are missing. I do have build artifacts for builds that were intended to lead up to a 3.0.1 release. If a verifiable copy of 3.0.0 can't be found, we may want to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but the file checksums wont match the original build due to embedded timestamps. Scott On 2021-01-25 11:08 a.m., Little, Scott wrote: Work continues at CENGN repair damaged repos and to move us to a new backend infrastructure with better redundancy. I still recommend that you avoid using download_mirrir.sh until the repos are fully repaired. I don’t have a firm ETA for that, perhaps two before we have full confidence in the repairs. Scott ________________________________ From: Scott Little Sent: January 23, 2021 2:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cengn Mirror server in down?! CENGN is up, but there seems to be significant damage to the repositories. We are investigate options to restore the repositories to health. I do NOT recommend running download_mirror.sh at this time. Scott On 2021-01-22 3:53 p.m., Scott Little wrote: CENGN remains out of service. A new problem has been identified with ceph storage. They continue to work the outage. Scott On 2021-01-22 9:55 a.m., Scott Little wrote: CENGN remains out of service AC to the server room has been restored. They are now working some firewall issues. They hope to have it restored in a few hours. Scott On 2021-01-21 10:07 a.m., Panech, Davlet wrote: The hosting company had an issue with their servers, they are working on it. They hope to be back online mid afternoon (Jan 21, Eastern Standard Time). ________________________________ From: Panech, Davlet Sent: January 21, 2021 9:56 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: Cengn Mirror server in down?! Thanks Alexandru, we are looking into it. ________________________________ From: Dimofte, Alexandru Sent: January 21, 2021 3:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cengn Mirror server in down?! Hello guys, I observed, trying to connect to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ , that cengn mirror server is down. Best regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5187 bytes Desc: image002.png URL: From build.starlingx at gmail.com Thu Jan 28 18:39:50 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 13:39:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 1349 - Failure! Message-ID: <1949910206.9.1611859191421.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 1349 Status: Failure Timestamp: 20210128T180812Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210128T180538Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-distro MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210128T180538Z DOCKER_BUILD_ID: jenkins-master-distro-20210128T180538Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210128T180538Z/logs DOCKER_BUILD_TAG: master-distro-20210128T180538Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210128T180538Z/logs LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro From build.starlingx at gmail.com Thu Jan 28 18:39:54 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 13:39:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 382 - Failure! Message-ID: <1330604368.12.1611859194886.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 382 Status: Failure Timestamp: 20210128T180538Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210128T180538Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From openinfradn at gmail.com Fri Jan 29 01:38:01 2021 From: openinfradn at gmail.com (open infra) Date: Fri, 29 Jan 2021 07:08:01 +0530 Subject: [Starlingx-discuss] Controller-0 could not download images In-Reply-To: References: Message-ID: There are two network cards available in the host machine and only one used so far. Should I use the remaining interface mapped to the controller (VM) interface? As DNS not resolved I tried to add entries in to /etc/hosts file, but it still has same issue. I highly appreciate if someone help me to fix this. controller-0:~$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.204.1 controller registry.local 192.168.206.2 controller-0-infra 169.254.202.1 pxecontroller 10.10.10.2 oamcontroller 192.168.204.4 controller-platform-nfs 192.168.204.3 controller-1 192.168.204.2 controller-0 192.168.206.3 controller-1-infra 192.168.204.5 controller-nfs 108.177.15.82 k8s.gcr.io 108.177.15.82 gcr.io 3.233.133.41 quay.io 52.55.43.248 docker.io 34.68.230.202 docker.elastic.co controller-0:~$ ping docker.elastic.co PING docker.elastic.co (34.68.230.202) 56(84) bytes of data. 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=1 ttl=100 time=116 ms 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=2 ttl=100 time=113 ms 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=3 ttl=100 time=114 ms --- docker.elastic.co ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 113.932/114.719/116.135/1.076 ms controller-0:~$ traceroute docker.elastic.co traceroute to docker.elastic.co (34.68.230.202), 30 hops max, 60 byte packets 1 10.10.10.1 (10.10.10.1) 1.049 ms 0.934 ms 0.887 ms 2 10.10.10.1 (10.10.10.1) 10012.319 ms !X 10012.286 ms !X 10012.234 ms !X controller-0:~$ On Thu, Jan 28, 2021 at 11:13 AM open infra wrote: > iptables rules http://paste.openstack.org/show/802058/ > > I even added few entries in /etc/hosts files and to get the > ansible-playbook running, but no luck. > http://paste.openstack.org/show/802059/ > > outpit of netstat http://paste.openstack.org/show/802060/ > > On Wed, Jan 27, 2021 at 10:07 PM open infra wrote: > >> Hi, >> >> I have installed controller-0 and bootstrap was failed at 'Download >> images and push to local registry'. >> >> I noticed that, dns resolution is failing in the controller but not in >> the host. >> controller-0:~$ dig docker.io >> >> ; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> docker.io >> ;; global options: +cmd >> ;; connection timed out; no servers could be reached >> controller-0:~$ ping quay.io >> PING quay.io (3.233.133.41) 56(84) bytes of data. >> >> --- quay.io ping statistics --- >> 3 packets transmitted, 0 received, 100% packet loss, time 2054ms >> >> I can ping from the controller. >> I have added following entries to iptables but no luck. >> >> sudo iptables -A OUTPUT -p udp -d 8.8.4.4,8.8.8.8 --dport 53 -m state >> --state NEW,ESTABLISHED -j ACCEPT >> sudo iptables -A INPUT -p udp -s 8.8.4.4,8.8.8.8 --sport 53 -m state >> --state ESTABLISHED -j ACCEPT >> sudo iptables -A OUTPUT -p tcp -d 8.8.4.4,8.8.8.8 --dport 53 -m state >> --state NEW,ESTABLISHED -j ACCEPT >> sudo iptables -A INPUT -p tcp -s 8.8.4.4,8.8.8.8 --sport 53 -m state >> --state ESTABLISHED -j ACCEPT >> >> I am not sure if my network configuration is correct. >> >> controller-0:~$ ip route list >> default via 10.10.10.1 dev ens3 >> 10.10.10.0/24 dev ens3 proto kernel scope link src 10.10.10.3 >> 169.254.0.0/16 dev eth1000 scope link metric 1002 >> 169.254.0.0/16 dev eth1001 scope link metric 1003 >> 169.254.0.0/16 dev ens3 scope link metric 1004 >> 169.254.0.0/16 dev ens4 scope link metric 1005 >> 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 >> linkdown >> >> Following is my local routing configuration and host IP is 192.168.10.100. >> $ ip route list >> default via 192.168.172.3 dev eno1 proto static metric 100 >> 10.10.10.0/24 dev stxbr1 proto kernel scope link src 10.10.10.1 >> 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 >> 192.168.10.0/24 dev eno1 proto kernel scope link src 192.168.10.100 >> metric 100 >> >> IP -a results available at http://paste.openstack.org/show/802048/ >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Jan 29 03:33:31 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 29 Jan 2021 03:33:31 +0000 Subject: [Starlingx-discuss] rook ceph feature is enabled on master branch Message-ID: Hi Patch for rook-ceph feature enabling is all merged. I will go on working on this feature enhancement. https://review.opendev.org/q/topic:%22ceph+containerization%22+(status:open%20OR%20status:merged) This is link for rook-ceph deployment guide. Later I will works together with Mary to finalize docs for this feature. https://review.opendev.org/c/starlingx/docs/+/751158 Great thanks to all the guy whom help me for rook-ceph feature enabling, listed below but not only maybe I miss! John Kung, Bart Wensley, Bob Church, Dan Voiculeasa, AL Bailey, Scott little, Qian bin, Don Penney, Wang Angie, Ovidiu Poncea, Liu tao, Saul Wold, Greg Waines Brent Rowsell, Chen Tingjie, Austin Sun, Hu Yong, Bruce Jones, Liu Zhipeng, Qi Mingyuan, Mary Camp, Chen Dongqi, Fu Yong, Li Long, Zhao Shuai. Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 29 04:22:28 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 23:22:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1197 - Failure! Message-ID: <1177188859.17.1611894149875.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1197 Status: Failure Timestamp: 20210129T040337Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210129T031647Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20210129T031647Z DOCKER_BUILD_ID: jenkins-master-flock-20210129T031647Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210129T031647Z/logs BUILD_IMG: true FULL_BUILD: true PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20210129T031647Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Fri Jan 29 04:22:31 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Jan 2021 23:22:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 376 - Still Failing! In-Reply-To: <503612388.6.1611619389434.JavaMail.javamailuser@localhost> References: <503612388.6.1611619389434.JavaMail.javamailuser@localhost> Message-ID: <29368797.20.1611894152344.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 376 Status: Still Failing Timestamp: 20210129T031647Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210129T031647Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From scott.little at windriver.com Fri Jan 29 06:02:08 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 29 Jan 2021 01:02:08 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> Message-ID: <7428784a-0ee0-5f86-fb4d-bc32213f11a3@windriver.com> Update Well a few more networking issues have been solved. thanks to Davlet, and Moh at CENGN. We have had a successful build of the 'compiler' and 'distro' layers.  The 'flock' layer built the rpms, but failed to update the installer.  It appears to relate to the loopback device.  I'll look into that tomorrow. ~350 RPMS failed to restore from upstream.  None are critical to any of our current builds.  I don't plan to persu them any further The mirroring job is throwing a lot more error messages than I'm used to seeing.  Many rpm download attempts are failing, and left 2000 new corrupt rpms in its wake.  I am cleaning up the new mess and adjusting the mirroring script to prevent download failures from leaving us with corrupt repos. The download failures seem to come in batches, so I'll reach out to CENGN to see if they had any network issues that might explain the problem. Scott On 2021-01-28 12:27 a.m., Scott Little wrote: > Update > > All known firewall issues have been fixed. > > Jenkins is now up and running on the build server once again. Our > first manually triggered build attempt of the compiler layer is now > running > > Of the original ~13000 corrupted rpms, we now have ... > > ~9250 have been restored, including all rpms that are knowm inputs to > supported builds > > ~3100 damaged rpms from the 2.0.0 release will not restored.  TSC and > community meetings agreed that 2.0.0, being 2 releases out of date, is > no longer supported. > > ~650 Have yet to be restored from Upstream.  The jenkins job that > pulls from upstream sources continues to run. > > I would like to have successful CENGN builds of all layers before you > all hammer the new server with your pent-up download_mirror.sh > requests.  Please wait a little longer.  We should be back in business > sometime tomorrow. > > Scott > > > > On 2021-01-27 9:56 a.m., Scott Little wrote: >> Update >> >> Of the original ~13000 corrupted rpms, we now have ... >> >> 5700 have been restored >> >> 2400 have yet to be assessed >> >> 1800 having no backup within cengn. Upstream availability has yet to >> be determined. >> >> 3100 I propose to drop as they fall within the 2.0.0 release which is >> in very bad shape, whereas 2.0.1 is in fairly good shape and worth >> saving. >> >> Scott >> >> >> >> On 2021-01-27 1:37 a.m., Scott Little wrote: >>> >>> The audit of repos identified ~13000 corrupted rpms >>> >>> >>> So far ~5000 have been restored from redundant copies within cengn. >>> >>> >>> Aprox 7500 have yet to be assessed.  Those remaining rpms are inputs >>> or outputs of actual builds.  The rpms produced by builds might >>> carry the same files name, but may contain different content due to >>> embedded file dates if not real changes.  Extra care is required to >>> restore from the correct source. If an exact match is unavailable, I >>> may be forced to use a source that is 'near' in time and therefore >>> less likely to contain anything other than trivial file timestamp >>> deltas.  I'm still pondering the implications of such a substitution. >>> >>> >>> That leaves ~500 having no backup within cengn.  Upstream >>> availability has yet to be determined. >>> >>> >>> Scott >>> >>> >>> >>> On 2021-01-26 1:28 a.m., Scott Little wrote: >>>> The jenkins in the cengn build is offline while we repair the file >>>> system on the mirror. The build machine both read from, and writes >>>> to the mirror, and I don't want it to cause further corruptions >>>> while the mirror is being repaired. >>>> >>>> The cengn mirror has been cut over to the new storage back end.  >>>> However any corrupt files from the old storage back end will remain >>>> corrupted on the new one. >>>> >>>> Restoration of rpm repos will proceed in several phases: >>>> >>>> 1) An audit of all rpm repos is underway.  Rpm's that fail their >>>> checksum are being removed and repodata will be updated to reflect >>>> the missing RPMS. >>>> >>>> 2) The mirror update job (downloading rpms from upstream rpm repos) >>>> will be run to restore as many missing files as possible. Many rpms >>>> may no longer be available as we kept old versions of packages that >>>> upstream drops when a new version is available, >>>> >>>> 3) If rpms that are not available from upstream, but are required >>>> for our build, we can attempt to restore them from one of several >>>> places.   e.g. the inputs directory of various builds, or the >>>> downloads directory on the cengn build server (independent storage >>>> from the mirror) >>>> >>>> 4) Resume building new loads >>>> >>>> >>>> >>>> All of the release iso's on cengn were corrupt. >>>> >>>> >>>> I've been able to restore 4.0.1 and 2.0.1 from the original build >>>> artifacts. >>>> >>>> >>>> Original build artifacts for 3.0.0 are missing.  I do have build >>>> artifacts for builds that were intended to lead up to a 3.0.1 >>>> release.  If a verifiable copy of 3.0.0 can't be found, we may want >>>> to consider issuing a 3.0.1. Alternatively I can rebuild 3.0.0, but >>>> the file checksums wont match the original build due to embedded >>>> timestamps. >>>> >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2021-01-25 11:08 a.m., Little, Scott wrote: >>>>> Work continues at CENGN repair damaged repos and to move us to a >>>>> new backend infrastructure with better redundancy. >>>>> >>>>> I still recommend that you avoid using download_mirrir.sh until >>>>> the repos are fully repaired.  I don’t have a firm ETA for that, >>>>> perhaps two before we have full confidence in the repairs. >>>>> >>>>> Scott >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Scott Little >>>>> *Sent:* January 23, 2021 2:24 AM >>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>> >>>>> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >>>>> >>>>> CENGN is up, but there seems to be significant damage to the >>>>> repositories. >>>>> >>>>> >>>>> We are investigate options to restore the repositories to health. >>>>> >>>>> >>>>> I do NOT recommend running download_mirror.sh at this time. >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> >>>>> On 2021-01-22 3:53 p.m., Scott Little wrote: >>>>>> >>>>>> CENGN remains out of service. >>>>>> >>>>>> >>>>>> A new problem has been identified with ceph storage. >>>>>> >>>>>> >>>>>> They continue to work the outage. >>>>>> >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>>>>> >>>>>>> CENGN remains out of service >>>>>>> >>>>>>> >>>>>>> AC to the server room has been restored. They are now working >>>>>>> some firewall issues. >>>>>>> >>>>>>> >>>>>>> They hope to have it restored in a few hours. >>>>>>> >>>>>>> >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>>>>> The hosting company had an issue with their servers, they are >>>>>>>> working on it. They hope to be back online mid afternoon (Jan >>>>>>>> 21, Eastern Standard Time). >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> *From:* Panech, Davlet >>>>>>>> >>>>>>>> *Sent:* January 21, 2021 9:56 AM >>>>>>>> *To:* Dimofte, Alexandru >>>>>>>> ; >>>>>>>> starlingx-discuss at lists.starlingx.io >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>>>>> Thanks Alexandru, we are looking into it. >>>>>>>> >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> *From:* Dimofte, Alexandru >>>>>>>> >>>>>>>> *Sent:* January 21, 2021 3:24 AM >>>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>>>>> >>>>>>>> Hello guys, >>>>>>>> >>>>>>>> I observed, trying to connect to >>>>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ >>>>>>>> , that cengn mirror server is down. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Alex >>>>>>>> >>>>>>>> Logo Description automatically generated >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Dimofte Alexandru >>>>>>>> >>>>>>>> Software Engineer >>>>>>>> >>>>>>>> STARLINGX TEAM >>>>>>>> >>>>>>>> Skype no: +40 336403734 >>>>>>>> >>>>>>>> Personal Mobile: +40 743167456 >>>>>>>> >>>>>>>> alexandru.dimofte at intel.com >>>>>>>> >>>>>>>> Intel Romania >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Starlingx-discuss mailing list >>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From rubyblaze at 163.com Fri Jan 29 06:14:18 2021 From: rubyblaze at 163.com (Li Hong) Date: Fri, 29 Jan 2021 14:14:18 +0800 (CST) Subject: [Starlingx-discuss] HTTPInternalServerError Message-ID: <4feeb775.3de8.1774cc730a7.Coremail.rubyblaze@163.com> An HTTPInternalServerError occurred when we install the starlingx AIO. why its failing. error message: --------------------- "cgtsclient.exc.HTTPInternalServerError: Timeout while waiting on RPC response - topic: \"sysinv.conductor_manager\", RPC method: \"reconfigure_service_endpoints\" info: \"\"" log info: --------------------- TASK [bootstrap/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 \"cgtsclient.common.http\"\nTraceback (most recent call last):\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611815465.42-177594302296378/populate_initial_config.py\", line 1045, in \n controller = populate_controller_config(client)\n File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611815465.42-177594302296378/populate_initial_config.py\", line 975, in populate_controller_config\n raise e\ncgtsclient.exc.HTTPInternalServerError: Timeout while waiting on RPC response - topic: \"sysinv.conductor_manager\", RPC method: \"reconfigure_service_endpoints\" info: \"\"\n", "stderr_lines": [ "No handlers could be found for logger \"cgtsclient.common.http\"", "Traceback (most recent call last):", " File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611815465.42-177594302296378/populate_initial_config.py\", line 1045, in ", " controller = populate_controller_config(client)", " File \"/tmp/.ansible-sysadmin/tmp/ansible-tmp-1611815465.42-177594302296378/populate_initial_config.py\", line 975, in populate_controller_config", " raise e", "cgtsclient.exc.HTTPInternalServerError: Timeout while waiting on RPC response - topic: \"sysinv.conductor_manager\", RPC method: \"reconfigure_service_endpoints\" info: \"\"" ], "stdout": "Populating system config...\nSystem config completed.\nPopulating load config...\nLoad config completed.\nPopulating management network...\nPopulating pxeboot network...\nPopulating oam network...\nPopulating multicast network...\nPopulating cluster host network...\nPopulating cluster pod network...\nPopulating cluster service network...\nNetwork config completed.\nPopulating/Updating DNS config...\nDNS config completed.\nManagement mac = 00:00:00:00:00:00\nRoot fs device = /dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0\nBoot device = /dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0\nConsole = tty0\nTboot = false\nInstall output = text\nHost values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}\nFailed to update the initial system config.\n", "stdout_lines": [ "Populating system config...", "System config completed.", "Populating load config...", "Load config completed.", "Populating management network...", "Populating pxeboot network...", "Populating oam network...", "Populating multicast network...", "Populating cluster host network...", "Populating cluster pod network...", "Populating cluster service network...", "Network config completed.", "Populating/Updating DNS config...", "DNS config completed.", "Management mac = 00:00:00:00:00:00", "Root fs device = /dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0", "Boot device = /dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0", "Console = tty0", "Tboot = false", "Install output = text", "Host values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.204.2', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}", "Failed to update the initial system config." ] } } TASK [bootstrap/persist-config : Fail if populate config script throws an exception] ******************************************************************************************************************************************************* fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to provision initial system configuration."} -------------- next part -------------- An HTML attachment was scrubbed... URL: From OwenYuen at cmail.carleton.ca Thu Jan 28 22:45:09 2021 From: OwenYuen at cmail.carleton.ca (Owen Yuen) Date: Thu, 28 Jan 2021 22:45:09 +0000 Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud In-Reply-To: References: , Message-ID: Hi Barton, Another question: The last step of the distributed cloud guide says to add a route from the subcloud management network to the central cloud management network. Is this done AFTER I unlock the subcloud active controller or before? I’m approaching the end and want to make sure I do everything correct. Thanks Owen From: Wensley, Barton Sent: Thursday, January 28, 2021 8:24 AM To: Owen Yuen; starlingx-discuss at lists.starlingx.io Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud [External Email] Owen – see my comments below… Bart From: Owen Yuen Sent: Wednesday, January 27, 2021 10:04 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, I’m a student so please bear with me if my questions are rudimentary. I’m trying to setup a AIO duplex distributed cloud setup with one central cloud and one subcloud. I’ve managed to bootstrap the subcloud from the central cloud successfully and the next steps says to continue the installation from the AIO duplex guide starting from “Configure controller-0”. On step 2, I need to run system commands but all of them require the host to be unlocked. I’m not able to unlock the host either since I’m on the host itself. I assume these steps are done on the subcloud controller-0 correct? [Bart] Yes - these steps are done on the subcloud controller-0. They are done BEFORE you unlock the subcloud controller – you will see that following these steps will eventually lead to unlocking the subcloud controller. Any help will be appreciated. Thanks Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sriram.Dharwadkar at commscope.com Fri Jan 29 11:17:40 2021 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Fri, 29 Jan 2021 11:17:40 +0000 Subject: [Starlingx-discuss] Procedure to update k8s_root_ca_cert and k8s_root_ca_key in StarlingX-4.0 Message-ID: Hi, We are using Distributed StarlingX-4.0. As per the documentation https://docs.starlingx.io/deploy_install_guides/r4_release/ansible_bootstrap_configs.html k8s_root_ca_cert and k8s_root_ca_key are install time only parameters. Documentation says updating k8s_root_ca_cert and k8s_root_ca_key is an involved process. Can you please share the procedure for updating root_ca and root_key ? We have a usecase to update this cert and key during runtime, with reboot it should take new root_ca and root_key, is this possible ? Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sriram.Dharwadkar at commscope.com Fri Jan 29 11:25:41 2021 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Fri, 29 Jan 2021 11:25:41 +0000 Subject: [Starlingx-discuss] [Distributed StarlingX 4.0] Multiple SRIOV pools In-Reply-To: References: Message-ID: Can you please reply to the below question ? Is it possible to create multiple device pools based on the selectors like below using starlingx CLI, controller-1:/home/sysadmin# cat /etc/pcidp/config.json { "resourceList": [ { "resourceName": "cuplanepool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#0-4" ] } }, { "resourceName": "flupool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#5-9" ] } }, { "resourceName": "o1pool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#10-15" ] } } ] } Regards, Sriram From: Dharwadkar, Sriram Sent: Thursday, January 7, 2021 8:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Distributed StarlingX 4.0] Multiple SRIOV pools Hi, We have installed Starlingx - Aug 5th release build for central cloud and edge cloud. controller-1:~$ cat /etc/build.info ### ### StarlingX ### Release 20.06 ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.4.0" JOB="STX_4.0_build_layer_flock" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="22" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-05 12:25:52 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_4.0_build_layer_flock" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="22" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-08-05 12:25:52 +0000" Hardware on which edge cloud is installed has Mellanox nic which is SRIOV capable. Commands that I m using to enable SRIOV functionality are, DATA0IF=enp101s0f0 export NODE=controller-1 PHYSNET0='physnet0' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list system host-port-list ${NODE} --nowrap > ${SPL} cat /tmp/tmp-system-port-list system host-if-list -a ${NODE} --nowrap > ${SPIL} cat /tmp/tmp-system-host-if-list DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 ~ DATA0PORTNAME) {print $2}') echo $DATA0IFUUID system datanetwork-add ${PHYSNET0} vlan system host-if-modify $NODE -n sriov0 -c pci-sriov -N 16 --vf-driver=netdevice $DATA0IFUUID system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} ${PHYSNET0} With these commands I m able to see that /etc/pcidp/config.json file is getting updated with the below contents controller-1:/home/sysadmin# cat /etc/pcidp/config.json { "resourceList": [ { "resourceName": "pci_sriov_net_physnet0", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0" ] } } ] } One device pool is created with 16 vfs. controller-1:/home/sysadmin# kubectl get node controller-1 -o json | jq '.status.allocatable' { "cpu": "22", "ephemeral-storage": "9391196145", "hugepages-1Gi": "20Gi", "hugepages-2Mi": "0", "intel.com/pci_sriov_net_physnet0": "16", "memory": "70207428Ki", "pods": "110" } Our usecase requires us to create multiple device pools like below. controller-1:/home/sysadmin# cat /etc/pcidp/config.json { "resourceList": [ { "resourceName": "cuplanepool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#0-4" ] } }, { "resourceName": "flupool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#5-9" ] } }, { "resourceName": "o1pool", "selectors": { "vendors": [ "15b3" ], "isRdma": true, "drivers": [ "mlx5_core" ], "devices": [ "1014" ], "pfNames": [ "enp101s0f0#10-15" ] } } ] } Please let me know if it is possible to create multiple device pools from the same nic (with the filters as above) using StarlingX system CLI. Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Fri Jan 29 13:08:14 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 29 Jan 2021 13:08:14 +0000 Subject: [Starlingx-discuss] Procedure to update k8s_root_ca_cert and k8s_root_ca_key in StarlingX-4.0 Message-ID: The upstream procedure is here: https://kubernetes.io/docs/tasks/tls/manual-rotation-of-ca-certificates/ Greg. From: "Dharwadkar, Sriram" Date: Friday, January 29, 2021 at 6:20 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Procedure to update k8s_root_ca_cert and k8s_root_ca_key in StarlingX-4.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, We are using Distributed StarlingX-4.0. As per the documentation https://docs.starlingx.io/deploy_install_guides/r4_release/ansible_bootstrap_configs.html k8s_root_ca_cert and k8s_root_ca_key are install time only parameters. Documentation says updating k8s_root_ca_cert and k8s_root_ca_key is an involved process. Can you please share the procedure for updating root_ca and root_key ? We have a usecase to update this cert and key during runtime, with reboot it should take new root_ca and root_key, is this possible ? Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Fri Jan 29 13:38:04 2021 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 29 Jan 2021 13:38:04 +0000 Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud In-Reply-To: References: , Message-ID: Owen, You add the route after unlocking the subcloud active controller. Bart From: Owen Yuen Sent: Thursday, January 28, 2021 5:45 PM To: Wensley, Barton ; starlingx-discuss at lists.starlingx.io Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Barton, Another question: The last step of the distributed cloud guide says to add a route from the subcloud management network to the central cloud management network. Is this done AFTER I unlock the subcloud active controller or before? I'm approaching the end and want to make sure I do everything correct. Thanks Owen From: Wensley, Barton Sent: Thursday, January 28, 2021 8:24 AM To: Owen Yuen; starlingx-discuss at lists.starlingx.io Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud [External Email] Owen - see my comments below... Bart From: Owen Yuen > Sent: Wednesday, January 27, 2021 10:04 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, I'm a student so please bear with me if my questions are rudimentary. I'm trying to setup a AIO duplex distributed cloud setup with one central cloud and one subcloud. I've managed to bootstrap the subcloud from the central cloud successfully and the next steps says to continue the installation from the AIO duplex guide starting from "Configure controller-0". On step 2, I need to run system commands but all of them require the host to be unlocked. I'm not able to unlock the host either since I'm on the host itself. I assume these steps are done on the subcloud controller-0 correct? [Bart] Yes - these steps are done on the subcloud controller-0. They are done BEFORE you unlock the subcloud controller - you will see that following these steps will eventually lead to unlocking the subcloud controller. Any help will be appreciated. Thanks Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Fri Jan 29 16:25:51 2021 From: lists at optimcloud.com (Lists) Date: Fri, 29 Jan 2021 23:25:51 +0700 Subject: [Starlingx-discuss] OAM_IF on VLAN not working... Message-ID: <94a1cb3a-4e8a-4c29-d8fb-ad2406e65619@optimcloud.com> going through a all-in-one simplex on bare-metal OAM_IF=vlan821 [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-modify controller-0 $OAM_IF -c platform Interface not found: host controller-0 if vlan821 [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-assign controller-0 $OAM_IF oam Interface not found: host controller-0 interface vlan821 so curious how i  get around this issue From lists at optimcloud.com Fri Jan 29 16:35:14 2021 From: lists at optimcloud.com (Lists) Date: Fri, 29 Jan 2021 23:35:14 +0700 Subject: [Starlingx-discuss] OAM_IF on VLAN not working... In-Reply-To: <94a1cb3a-4e8a-4c29-d8fb-ad2406e65619@optimcloud.com> References: <94a1cb3a-4e8a-4c29-d8fb-ad2406e65619@optimcloud.com> Message-ID: On 1/29/21 11:25 PM, Lists wrote: > going through a all-in-one simplex on bare-metal > > OAM_IF=vlan821 > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-modify > controller-0 $OAM_IF -c platform > Interface not found: host controller-0 if vlan821 > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-network-assign controller-0 $OAM_IF oam > Interface not found: host controller-0 interface vlan821 > > so curious how i  get around this issue > never mind... found it system host-if-add HOST_NAME -V VLAN_ID -c IF_CLASS IF_NAME vlan ETH_NAME > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Jan 30 20:23:15 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 15:23:15 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 78 - Failure! Message-ID: <103093784.27.1612038196138.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 78 Status: Failure Timestamp: 20210129T201157Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210129T194148Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210129T194148Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210129T194148Z/logs MASTER_BUILD_NUMBER: 101 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210129T194148Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210129T194148Z DOCKER_BUILD_ID: jenkins-master-containers-20210129T194148Z-builder TIMESTAMP: 20210129T194148Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210129T194148Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210129T194148Z/outputs From build.starlingx at gmail.com Sat Jan 30 20:23:17 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 15:23:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 101 - Failure! Message-ID: <942416509.30.1612038198354.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 101 Status: Failure Timestamp: 20210129T194148Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210129T194148Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sat Jan 30 21:08:59 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 16:08:59 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 376 - Failure! Message-ID: <2131877051.35.1612040940528.JavaMail.javamailuser@localhost> Project: STX_build_docker_base_image Build #: 376 Status: Failure Timestamp: 20210130T210836Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T204729Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T204729Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210130T204729Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T204729Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/logs WEB_HOST_PORT: 80 OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Sat Jan 30 21:09:02 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 16:09:02 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 79 - Still Failing! In-Reply-To: <2045411121.25.1612038193921.JavaMail.javamailuser@localhost> References: <2045411121.25.1612038193921.JavaMail.javamailuser@localhost> Message-ID: <633236720.38.1612040942848.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 79 Status: Still Failing Timestamp: 20210130T210836Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T204729Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T204729Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T204729Z/logs MASTER_BUILD_NUMBER: 103 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210130T204729Z DOCKER_BUILD_ID: jenkins-master-containers-20210130T204729Z-builder TIMESTAMP: 20210130T204729Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T204729Z/outputs From build.starlingx at gmail.com Sat Jan 30 21:09:04 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 16:09:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 103 - Failure! Message-ID: <1828726551.41.1612040945270.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 103 Status: Failure Timestamp: 20210130T204729Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T204729Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sat Jan 30 23:25:03 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 18:25:03 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 80 - Still Failing! In-Reply-To: <1534174673.36.1612040941107.JavaMail.javamailuser@localhost> References: <1534174673.36.1612040941107.JavaMail.javamailuser@localhost> Message-ID: <92909344.45.1612049103803.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 80 Status: Still Failing Timestamp: 20210130T214030Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T212420Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T212420Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T212420Z/logs MASTER_BUILD_NUMBER: 104 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T212420Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210130T212420Z DOCKER_BUILD_ID: jenkins-master-containers-20210130T212420Z-builder TIMESTAMP: 20210130T212420Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T212420Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T212420Z/outputs From build.starlingx at gmail.com Sat Jan 30 23:25:05 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 18:25:05 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 104 - Still Failing! In-Reply-To: <1004046277.39.1612040943806.JavaMail.javamailuser@localhost> References: <1004046277.39.1612040943806.JavaMail.javamailuser@localhost> Message-ID: <2105346916.48.1612049106003.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 104 Status: Still Failing Timestamp: 20210130T212420Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T212420Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 31 00:05:51 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 19:05:51 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 321 - Failure! Message-ID: <472945709.51.1612051552281.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 321 Status: Failure Timestamp: 20210131T000529Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T233107Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T233107Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210130T233107Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T233107Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/logs PUBLISH_TIMESTAMP: 20210130T233107Z FLOCK_VERSION: master-centos-stable-20210130T233107Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210130T233107Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Sun Jan 31 00:05:53 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 19:05:53 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 81 - Still Failing! In-Reply-To: <1308649464.43.1612049101214.JavaMail.javamailuser@localhost> References: <1308649464.43.1612049101214.JavaMail.javamailuser@localhost> Message-ID: <1654307004.54.1612051554528.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 81 Status: Still Failing Timestamp: 20210130T234712Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T233107Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T233107Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T233107Z/logs MASTER_BUILD_NUMBER: 105 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210130T233107Z DOCKER_BUILD_ID: jenkins-master-containers-20210130T233107Z-builder TIMESTAMP: 20210130T233107Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/outputs From build.starlingx at gmail.com Sun Jan 31 00:05:56 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 30 Jan 2021 19:05:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 105 - Still Failing! In-Reply-To: <308397760.46.1612049104349.JavaMail.javamailuser@localhost> References: <308397760.46.1612049104349.JavaMail.javamailuser@localhost> Message-ID: <1081325300.57.1612051556649.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 105 Status: Still Failing Timestamp: 20210130T233107Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210130T233107Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 31 06:03:45 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:03:45 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 82 - Still Failing! In-Reply-To: <1171810397.52.1612051552905.JavaMail.javamailuser@localhost> References: <1171810397.52.1612051552905.JavaMail.javamailuser@localhost> Message-ID: <1063712408.60.1612073026255.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 82 Status: Still Failing Timestamp: 20210131T052236Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T050619Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T050619Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T050619Z/logs MASTER_BUILD_NUMBER: 106 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T050619Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T050619Z-builder TIMESTAMP: 20210131T050619Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/outputs From build.starlingx at gmail.com Sun Jan 31 06:03:48 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:03:48 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 106 - Still Failing! In-Reply-To: <1219315568.55.1612051555267.JavaMail.javamailuser@localhost> References: <1219315568.55.1612051555267.JavaMail.javamailuser@localhost> Message-ID: <470021719.63.1612073028646.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 106 Status: Still Failing Timestamp: 20210131T050619Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T050619Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 31 06:21:38 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:21:38 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 83 - Still Failing! In-Reply-To: <1042731720.58.1612073024221.JavaMail.javamailuser@localhost> References: <1042731720.58.1612073024221.JavaMail.javamailuser@localhost> Message-ID: <653138737.66.1612074099171.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 83 Status: Still Failing Timestamp: 20210131T062137Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T060528Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T060528Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T060528Z/logs MASTER_BUILD_NUMBER: 107 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T060528Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T060528Z-builder TIMESTAMP: 20210131T060528Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/outputs From build.starlingx at gmail.com Sun Jan 31 06:21:40 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:21:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 107 - Still Failing! In-Reply-To: <53926735.61.1612073026952.JavaMail.javamailuser@localhost> References: <53926735.61.1612073026952.JavaMail.javamailuser@localhost> Message-ID: <6419772.69.1612074101230.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 107 Status: Still Failing Timestamp: 20210131T060528Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T060528Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 31 06:44:56 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:44:56 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 84 - Still Failing! In-Reply-To: <455810231.64.1612074097431.JavaMail.javamailuser@localhost> References: <455810231.64.1612074097431.JavaMail.javamailuser@localhost> Message-ID: <1505749054.72.1612075497362.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 84 Status: Still Failing Timestamp: 20210131T064455Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T062853Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T062853Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T062853Z/logs MASTER_BUILD_NUMBER: 108 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T062853Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T062853Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T062853Z-builder TIMESTAMP: 20210131T062853Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T062853Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T062853Z/outputs From build.starlingx at gmail.com Sun Jan 31 06:44:58 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 01:44:58 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 108 - Still Failing! In-Reply-To: <1532965690.67.1612074099703.JavaMail.javamailuser@localhost> References: <1532965690.67.1612074099703.JavaMail.javamailuser@localhost> Message-ID: <213997980.75.1612075499310.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 108 Status: Still Failing Timestamp: 20210131T062853Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T062853Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sun Jan 31 14:06:01 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 09:06:01 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 85 - Still Failing! In-Reply-To: <1235761722.70.1612075495441.JavaMail.javamailuser@localhost> References: <1235761722.70.1612075495441.JavaMail.javamailuser@localhost> Message-ID: <818909338.78.1612101962023.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 85 Status: Still Failing Timestamp: 20210131T071453Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T065039Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T065039Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T065039Z/logs MASTER_BUILD_NUMBER: 109 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T065039Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T065039Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T065039Z-builder TIMESTAMP: 20210131T065039Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T065039Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T065039Z/outputs From build.starlingx at gmail.com Sun Jan 31 14:06:03 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 31 Jan 2021 09:06:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 109 - Still Failing! In-Reply-To: <658787563.73.1612075497904.JavaMail.javamailuser@localhost> References: <658787563.73.1612075497904.JavaMail.javamailuser@localhost> Message-ID: <970871419.81.1612101964360.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 109 Status: Still Failing Timestamp: 20210131T065039Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210131T065039Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From OwenYuen at cmail.carleton.ca Sun Jan 31 19:39:20 2021 From: OwenYuen at cmail.carleton.ca (Owen Yuen) Date: Sun, 31 Jan 2021 19:39:20 +0000 Subject: [Starlingx-discuss] Distributed subcloud setup config_management script clarification Message-ID: Hi all, I want to clarify in the distributed cloud setup, when running the config_management script it asks for the “management interface address CIDR”. Is this address referring to the oam_node_0_address or the oam_floating_address? For instance, in https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.html if I had followed the example for the “minimal config override file” provided, would I use the 10.10.10.2 or the 10.10.10.3? $ sudo config_management Enabling interfaces... DONE Waiting 120 seconds for LLDP neighbor discovery... Retrieving neighbor details... DONE Available interfaces: local interface remote port --------------- ---------- enp0s3 08:00:27:c4:6c:7a enp0s8 08:00:27:86:7a:13 enp0s9 unknown Enter management interface name: enp0s3 Enter management address CIDR: 10.10.10.?/24 Enter management gateway address [10.10.10.1]: Enter System Controller subnet: 10.10.10.0/24 Disabling non-management interfaces... DONE Configuring management interface... DONE RTNETLINK answers: File exists Adding route to System Controller... DONE Thanks Owen This email contains links to content or websites. Always be cautious when clicking on external links or attachments. If in doubt, please forward suspicious emails to phishing at carleton.ca. -----End of Disclaimer----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sun Jan 31 21:11:58 2021 From: scott.little at windriver.com (Scott Little) Date: Sun, 31 Jan 2021 16:11:58 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: <7428784a-0ee0-5f86-fb4d-bc32213f11a3@windriver.com> References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> <7428784a-0ee0-5f86-fb4d-bc32213f11a3@windriver.com> Message-ID: <6d5f08e9-2250-4183-8295-2b9f9375557e@windriver.com> Update CENGN hasn't found any specific network issues as of yet.  They have acknowledged that the current network configuration implemented in the wake of power outage and the switch to the new server is sub-optimal and will revisit it soon. We have worked over the last several days to get the firewall configuration right to allow all the required services on the build server to run. One particular quirk of the current network setup is that the DNS reported address of the mirror is inaccessible.  An /etc/hosts entry is required to force the mirror address to resolve to an alternate IP address.  I've spent the last several sleepless nights learning how to push that change not only into our build container, but into all the STX service containers that we build. I can finally report successful builds of the entire layered build stack. On the mirror update side, I have adjusted the mirroring algorithm to do more validation steps as it downloads. This should prevent further corruptions, but will slow the frequency with with we can refresh our repos from upstream.  In stead of updating all repos daily, some will be on a ~1/week schedule. Scott On 2021-01-29 1:02 a.m., Scott Little wrote: > > Update > > > Well a few more networking issues have been solved. thanks to Davlet, > and Moh at CENGN. > > > We have had a successful build of the 'compiler' and 'distro' layers.  > The 'flock' layer built the rpms, but failed to update the installer.  > It appears to relate to the loopback device. I'll look into that > tomorrow. > > > ~350 RPMS failed to restore from upstream.  None are critical to any > of our current builds.  I don't plan to persu them any further > > > The mirroring job is throwing a lot more error messages than I'm used > to seeing.  Many rpm download attempts are failing, and left 2000 new > corrupt rpms in its wake.  I am cleaning up the new mess and adjusting > the mirroring script to prevent download failures from leaving us with > corrupt repos. The download failures seem to come in batches, so I'll > reach out to CENGN to see if they had any network issues that might > explain the problem. > > > Scott > > > > On 2021-01-28 12:27 a.m., Scott Little wrote: >> Update >> >> All known firewall issues have been fixed. >> >> Jenkins is now up and running on the build server once again. Our >> first manually triggered build attempt of the compiler layer is now >> running >> >> Of the original ~13000 corrupted rpms, we now have ... >> >> ~9250 have been restored, including all rpms that are knowm inputs to >> supported builds >> >> ~3100 damaged rpms from the 2.0.0 release will not restored.  TSC and >> community meetings agreed that 2.0.0, being 2 releases out of date, >> is no longer supported. >> >> ~650 Have yet to be restored from Upstream.  The jenkins job that >> pulls from upstream sources continues to run. >> >> I would like to have successful CENGN builds of all layers before you >> all hammer the new server with your pent-up download_mirror.sh >> requests.  Please wait a little longer.  We should be back in >> business sometime tomorrow. >> >> Scott >> >> >> >> On 2021-01-27 9:56 a.m., Scott Little wrote: >>> Update >>> >>> Of the original ~13000 corrupted rpms, we now have ... >>> >>> 5700 have been restored >>> >>> 2400 have yet to be assessed >>> >>> 1800 having no backup within cengn. Upstream availability has yet to >>> be determined. >>> >>> 3100 I propose to drop as they fall within the 2.0.0 release which >>> is in very bad shape, whereas 2.0.1 is in fairly good shape and >>> worth saving. >>> >>> Scott >>> >>> >>> >>> On 2021-01-27 1:37 a.m., Scott Little wrote: >>>> >>>> The audit of repos identified ~13000 corrupted rpms >>>> >>>> >>>> So far ~5000 have been restored from redundant copies within cengn. >>>> >>>> >>>> Aprox 7500 have yet to be assessed.  Those remaining rpms are >>>> inputs or outputs of actual builds.  The rpms produced by builds >>>> might carry the same files name, but may contain different content >>>> due to embedded file dates if not real changes.  Extra care is >>>> required to restore from the correct source. If an exact match is >>>> unavailable, I may be forced to use a source that is 'near' in time >>>> and therefore less likely to contain anything other than trivial >>>> file timestamp deltas.  I'm still pondering the implications of >>>> such a substitution. >>>> >>>> >>>> That leaves ~500 having no backup within cengn. Upstream >>>> availability has yet to be determined. >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2021-01-26 1:28 a.m., Scott Little wrote: >>>>> The jenkins in the cengn build is offline while we repair the file >>>>> system on the mirror.  The build machine both read from, and >>>>> writes to the mirror, and I don't want it to cause further >>>>> corruptions while the mirror is being repaired. >>>>> >>>>> The cengn mirror has been cut over to the new storage back end.  >>>>> However any corrupt files from the old storage back end will >>>>> remain corrupted on the new one. >>>>> >>>>> Restoration of rpm repos will proceed in several phases: >>>>> >>>>> 1) An audit of all rpm repos is underway.  Rpm's that fail their >>>>> checksum are being removed and repodata will be updated to reflect >>>>> the missing RPMS. >>>>> >>>>> 2) The mirror update job (downloading rpms from upstream rpm >>>>> repos) will be run to restore as many missing files as possible. >>>>> Many rpms may no longer be available as we kept old versions of >>>>> packages that upstream drops when a new version is available, >>>>> >>>>> 3) If rpms that are not available from upstream, but are required >>>>> for our build, we can attempt to restore them from one of several >>>>> places.   e.g. the inputs directory of various builds, or the >>>>> downloads directory on the cengn build server (independent storage >>>>> from the mirror) >>>>> >>>>> 4) Resume building new loads >>>>> >>>>> >>>>> >>>>> All of the release iso's on cengn were corrupt. >>>>> >>>>> >>>>> I've been able to restore 4.0.1 and 2.0.1 from the original build >>>>> artifacts. >>>>> >>>>> >>>>> Original build artifacts for 3.0.0 are missing.  I do have build >>>>> artifacts for builds that were intended to lead up to a 3.0.1 >>>>> release.  If a verifiable copy of 3.0.0 can't be found, we may >>>>> want to consider issuing a 3.0.1.  Alternatively I can rebuild >>>>> 3.0.0, but the file checksums wont match the original build due to >>>>> embedded timestamps. >>>>> >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> On 2021-01-25 11:08 a.m., Little, Scott wrote: >>>>>> Work continues at CENGN repair damaged repos and to move us to a >>>>>> new backend infrastructure with better redundancy. >>>>>> >>>>>> I still recommend that you avoid using download_mirrir.sh until >>>>>> the repos are fully repaired.  I don’t have a firm ETA for that, >>>>>> perhaps two before we have full confidence in the repairs. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Scott Little >>>>>> *Sent:* January 23, 2021 2:24 AM >>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >>>>>> >>>>>> CENGN is up, but there seems to be significant damage to the >>>>>> repositories. >>>>>> >>>>>> >>>>>> We are investigate options to restore the repositories to health. >>>>>> >>>>>> >>>>>> I do NOT recommend running download_mirror.sh at this time. >>>>>> >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2021-01-22 3:53 p.m., Scott Little wrote: >>>>>>> >>>>>>> CENGN remains out of service. >>>>>>> >>>>>>> >>>>>>> A new problem has been identified with ceph storage. >>>>>>> >>>>>>> >>>>>>> They continue to work the outage. >>>>>>> >>>>>>> >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>>>>>> >>>>>>>> CENGN remains out of service >>>>>>>> >>>>>>>> >>>>>>>> AC to the server room has been restored. They are now working >>>>>>>> some firewall issues. >>>>>>>> >>>>>>>> >>>>>>>> They hope to have it restored in a few hours. >>>>>>>> >>>>>>>> >>>>>>>> Scott >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>>>>>> The hosting company had an issue with their servers, they are >>>>>>>>> working on it. They hope to be back online mid afternoon (Jan >>>>>>>>> 21, Eastern Standard Time). >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> *From:* Panech, Davlet >>>>>>>>> >>>>>>>>> *Sent:* January 21, 2021 9:56 AM >>>>>>>>> *To:* Dimofte, Alexandru >>>>>>>>> ; >>>>>>>>> starlingx-discuss at lists.starlingx.io >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>>>>>> Thanks Alexandru, we are looking into it. >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> *From:* Dimofte, Alexandru >>>>>>>>> >>>>>>>>> *Sent:* January 21, 2021 3:24 AM >>>>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>>>>>> >>>>>>>>> Hello guys, >>>>>>>>> >>>>>>>>> I observed, trying to connect to >>>>>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ >>>>>>>>> , that cengn mirror server is down. >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Alex >>>>>>>>> >>>>>>>>> Logo Description automatically generated >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Dimofte Alexandru >>>>>>>>> >>>>>>>>> Software Engineer >>>>>>>>> >>>>>>>>> STARLINGX TEAM >>>>>>>>> >>>>>>>>> Skype no: +40 336403734 >>>>>>>>> >>>>>>>>> Personal Mobile: +40 743167456 >>>>>>>>> >>>>>>>>> alexandru.dimofte at intel.com >>>>>>>>> >>>>>>>>> Intel Romania >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Starlingx-discuss mailing list >>>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Starlingx-discuss mailing list >>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From scott.little at windriver.com Sun Jan 31 21:25:39 2021 From: scott.little at windriver.com (Scott Little) Date: Sun, 31 Jan 2021 16:25:39 -0500 Subject: [Starlingx-discuss] Cengn Mirror server in down?! In-Reply-To: <6d5f08e9-2250-4183-8295-2b9f9375557e@windriver.com> References: <75da487b-d473-1d0f-8504-519a664f4f6c@windriver.com> <34128b7c-d78d-13a5-8682-99b8615487a5@windriver.com> <7428784a-0ee0-5f86-fb4d-bc32213f11a3@windriver.com> <6d5f08e9-2250-4183-8295-2b9f9375557e@windriver.com> Message-ID: <66da5e8d-cc2b-1e13-dd4f-a8c5afa2f97d@windriver.com> Update The CENGN builds will now return to the regular daily schedule. None of the new builds have been sanitized as yet. Until those builds are sanitized, it might be advisable to keep software updates to a minimum.  I'll defer to the TSC on that one.  However from a purely CENGN/mirror/build perspective, I think we are ready to allow updates to .lst files again. Scott On 2021-01-31 4:11 p.m., Scott Little wrote: > > Update > > > > CENGN hasn't found any specific network issues as of yet.  They have > acknowledged that the current network configuration implemented in the > wake of power outage and the switch to the new server is sub-optimal > and will revisit it soon. > > > We have worked over the last several days to get the firewall > configuration right to allow all the required services on the build > server to run. > > > One particular quirk of the current network setup is that the DNS > reported address of the mirror is inaccessible.  An /etc/hosts entry > is required to force the mirror address to resolve to an alternate IP > address.  I've spent the last several sleepless nights learning how to > push that change not only into our build container, but into all the > STX service containers that we build. I can finally report successful > builds of the entire layered build stack. > > > On the mirror update side, I have adjusted the mirroring algorithm to > do more validation steps as it downloads. This should prevent further > corruptions, but will slow the frequency with with we can refresh our > repos from upstream.  In stead of updating all repos daily, some will > be on a ~1/week schedule. > > > Scott > > > > > On 2021-01-29 1:02 a.m., Scott Little wrote: >> >> Update >> >> >> Well a few more networking issues have been solved. thanks to Davlet, >> and Moh at CENGN. >> >> >> We have had a successful build of the 'compiler' and 'distro' >> layers.  The 'flock' layer built the rpms, but failed to update the >> installer.  It appears to relate to the loopback device.  I'll look >> into that tomorrow. >> >> >> ~350 RPMS failed to restore from upstream.  None are critical to any >> of our current builds.  I don't plan to persu them any further >> >> >> The mirroring job is throwing a lot more error messages than I'm used >> to seeing.  Many rpm download attempts are failing, and left 2000 new >> corrupt rpms in its wake.  I am cleaning up the new mess and >> adjusting the mirroring script to prevent download failures from >> leaving us with corrupt repos. The download failures seem to come in >> batches, so I'll reach out to CENGN to see if they had any network >> issues that might explain the problem. >> >> >> Scott >> >> >> >> On 2021-01-28 12:27 a.m., Scott Little wrote: >>> Update >>> >>> All known firewall issues have been fixed. >>> >>> Jenkins is now up and running on the build server once again. Our >>> first manually triggered build attempt of the compiler layer is now >>> running >>> >>> Of the original ~13000 corrupted rpms, we now have ... >>> >>> ~9250 have been restored, including all rpms that are knowm inputs >>> to supported builds >>> >>> ~3100 damaged rpms from the 2.0.0 release will not restored.  TSC >>> and community meetings agreed that 2.0.0, being 2 releases out of >>> date, is no longer supported. >>> >>> ~650 Have yet to be restored from Upstream.  The jenkins job that >>> pulls from upstream sources continues to run. >>> >>> I would like to have successful CENGN builds of all layers before >>> you all hammer the new server with your pent-up download_mirror.sh >>> requests. Please wait a little longer.  We should be back in >>> business sometime tomorrow. >>> >>> Scott >>> >>> >>> >>> On 2021-01-27 9:56 a.m., Scott Little wrote: >>>> Update >>>> >>>> Of the original ~13000 corrupted rpms, we now have ... >>>> >>>> 5700 have been restored >>>> >>>> 2400 have yet to be assessed >>>> >>>> 1800 having no backup within cengn. Upstream availability has yet >>>> to be determined. >>>> >>>> 3100 I propose to drop as they fall within the 2.0.0 release which >>>> is in very bad shape, whereas 2.0.1 is in fairly good shape and >>>> worth saving. >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2021-01-27 1:37 a.m., Scott Little wrote: >>>>> >>>>> The audit of repos identified ~13000 corrupted rpms >>>>> >>>>> >>>>> So far ~5000 have been restored from redundant copies within cengn. >>>>> >>>>> >>>>> Aprox 7500 have yet to be assessed.  Those remaining rpms are >>>>> inputs or outputs of actual builds.  The rpms produced by builds >>>>> might carry the same files name, but may contain different content >>>>> due to embedded file dates if not real changes.  Extra care is >>>>> required to restore from the correct source. If an exact match is >>>>> unavailable, I may be forced to use a source that is 'near' in >>>>> time and therefore less likely to contain anything other than >>>>> trivial file timestamp deltas.  I'm still pondering the >>>>> implications of such a substitution. >>>>> >>>>> >>>>> That leaves ~500 having no backup within cengn. Upstream >>>>> availability has yet to be determined. >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> On 2021-01-26 1:28 a.m., Scott Little wrote: >>>>>> The jenkins in the cengn build is offline while we repair the >>>>>> file system on the mirror.  The build machine both read from, and >>>>>> writes to the mirror, and I don't want it to cause further >>>>>> corruptions while the mirror is being repaired. >>>>>> >>>>>> The cengn mirror has been cut over to the new storage back end.  >>>>>> However any corrupt files from the old storage back end will >>>>>> remain corrupted on the new one. >>>>>> >>>>>> Restoration of rpm repos will proceed in several phases: >>>>>> >>>>>> 1) An audit of all rpm repos is underway.  Rpm's that fail their >>>>>> checksum are being removed and repodata will be updated to >>>>>> reflect the missing RPMS. >>>>>> >>>>>> 2) The mirror update job (downloading rpms from upstream rpm >>>>>> repos) will be run to restore as many missing files as possible. >>>>>> Many rpms may no longer be available as we kept old versions of >>>>>> packages that upstream drops when a new version is available, >>>>>> >>>>>> 3) If rpms that are not available from upstream, but are required >>>>>> for our build, we can attempt to restore them from one of several >>>>>> places.   e.g. the inputs directory of various builds, or the >>>>>> downloads directory on the cengn build server (independent >>>>>> storage from the mirror) >>>>>> >>>>>> 4) Resume building new loads >>>>>> >>>>>> >>>>>> >>>>>> All of the release iso's on cengn were corrupt. >>>>>> >>>>>> >>>>>> I've been able to restore 4.0.1 and 2.0.1 from the original build >>>>>> artifacts. >>>>>> >>>>>> >>>>>> Original build artifacts for 3.0.0 are missing.  I do have build >>>>>> artifacts for builds that were intended to lead up to a 3.0.1 >>>>>> release.  If a verifiable copy of 3.0.0 can't be found, we may >>>>>> want to consider issuing a 3.0.1.  Alternatively I can rebuild >>>>>> 3.0.0, but the file checksums wont match the original build due >>>>>> to embedded timestamps. >>>>>> >>>>>> >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> >>>>>> On 2021-01-25 11:08 a.m., Little, Scott wrote: >>>>>>> Work continues at CENGN repair damaged repos and to move us to a >>>>>>> new backend infrastructure with better redundancy. >>>>>>> >>>>>>> I still recommend that you avoid using download_mirrir.sh until >>>>>>> the repos are fully repaired.  I don’t have a firm ETA for that, >>>>>>> perhaps two before we have full confidence in the repairs. >>>>>>> >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Scott Little >>>>>>> *Sent:* January 23, 2021 2:24 AM >>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>> >>>>>>> *Subject:* Re: [Starlingx-discuss] Cengn Mirror server in down?! >>>>>>> >>>>>>> CENGN is up, but there seems to be significant damage to the >>>>>>> repositories. >>>>>>> >>>>>>> >>>>>>> We are investigate options to restore the repositories to health. >>>>>>> >>>>>>> >>>>>>> I do NOT recommend running download_mirror.sh at this time. >>>>>>> >>>>>>> >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2021-01-22 3:53 p.m., Scott Little wrote: >>>>>>>> >>>>>>>> CENGN remains out of service. >>>>>>>> >>>>>>>> >>>>>>>> A new problem has been identified with ceph storage. >>>>>>>> >>>>>>>> >>>>>>>> They continue to work the outage. >>>>>>>> >>>>>>>> >>>>>>>> Scott >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 2021-01-22 9:55 a.m., Scott Little wrote: >>>>>>>>> >>>>>>>>> CENGN remains out of service >>>>>>>>> >>>>>>>>> >>>>>>>>> AC to the server room has been restored. They are now working >>>>>>>>> some firewall issues. >>>>>>>>> >>>>>>>>> >>>>>>>>> They hope to have it restored in a few hours. >>>>>>>>> >>>>>>>>> >>>>>>>>> Scott >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 2021-01-21 10:07 a.m., Panech, Davlet wrote: >>>>>>>>>> The hosting company had an issue with their servers, they are >>>>>>>>>> working on it. They hope to be back online mid afternoon (Jan >>>>>>>>>> 21, Eastern Standard Time). >>>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>>> *From:* Panech, Davlet >>>>>>>>>> >>>>>>>>>> *Sent:* January 21, 2021 9:56 AM >>>>>>>>>> *To:* Dimofte, Alexandru >>>>>>>>>> ; >>>>>>>>>> starlingx-discuss at lists.starlingx.io >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Subject:* Re: Cengn Mirror server in down?! >>>>>>>>>> Thanks Alexandru, we are looking into it. >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>>> *From:* Dimofte, Alexandru >>>>>>>>>> >>>>>>>>>> *Sent:* January 21, 2021 3:24 AM >>>>>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Subject:* [Starlingx-discuss] Cengn Mirror server in down?! >>>>>>>>>> >>>>>>>>>> Hello guys, >>>>>>>>>> >>>>>>>>>> I observed, trying to connect to >>>>>>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ >>>>>>>>>> , that cengn mirror server is down. >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> >>>>>>>>>> Alex >>>>>>>>>> >>>>>>>>>> Logo Description automatically generated >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Dimofte Alexandru >>>>>>>>>> >>>>>>>>>> Software Engineer >>>>>>>>>> >>>>>>>>>> STARLINGX TEAM >>>>>>>>>> >>>>>>>>>> Skype no: +40 336403734 >>>>>>>>>> >>>>>>>>>> Personal Mobile: +40 743167456 >>>>>>>>>> >>>>>>>>>> alexandru.dimofte at intel.com >>>>>>>>>> >>>>>>>>>> Intel Romania >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Starlingx-discuss mailing list >>>>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Starlingx-discuss mailing list >>>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Starlingx-discuss mailing list >>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: not available URL: From amy at demarco.com Sun Jan 31 21:37:58 2021 From: amy at demarco.com (Amy Marrich) Date: Sun, 31 Jan 2021 15:37:58 -0600 Subject: [Starlingx-discuss] [Diversity] Diversity &Inclusion WG Meeting reminder Amy Marrich Mon, Jan 11, 7:49 AM to foundation, openstack-discuss, kata-dev, starlingx-discuss, airship-discuss, zuul-discuss The Diversity & Inclusion WG invites members of all OSF projects to our meeting today, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) Message-ID: The Diversity & Inclusion WG invites members of all OSF projects to our meeting tomorrow, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: