From starlingx.build at gmail.com Thu Sep 1 10:44:07 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Sep 2022 06:44:07 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 579 - Still Failing! In-Reply-To: <1363157300.0.1661942854575.JavaMail.javamailuser@localhost> References: <1363157300.0.1661942854575.JavaMail.javamailuser@localhost> Message-ID: <1322504490.12.1662029048609.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 579 Status: Still Failing Timestamp: 20220901T060407Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220901T043044Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220901T043044Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220901T043044Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220901T043044Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220901T043044Z/logs PUBLISH_TIMESTAMP: 20220901T043044Z FLOCK_VERSION: master-centos-stable-20220901T043044Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220901T043044Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220901T043044Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Sep 1 10:44:13 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Sep 2022 06:44:13 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 335 - Still Failing! In-Reply-To: <275545493.3.1661942861038.JavaMail.javamailuser@localhost> References: <275545493.3.1661942861038.JavaMail.javamailuser@localhost> Message-ID: <1034572377.15.1662029053935.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 335 Status: Still Failing Timestamp: 20220901T053026Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220901T043044Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220901T043044Z 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/20220901T043044Z/logs MASTER_BUILD_NUMBER: 336 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220901T043044Z/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: 20220901T043044Z DOCKER_BUILD_ID: jenkins-master-containers-20220901T043044Z-builder TIMESTAMP: 20220901T043044Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220901T043044Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220901T043044Z/outputs From starlingx.build at gmail.com Thu Sep 1 10:44:18 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Sep 2022 06:44:18 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 336 - Still Failing! In-Reply-To: <392986671.6.1661942864421.JavaMail.javamailuser@localhost> References: <392986671.6.1661942864421.JavaMail.javamailuser@localhost> Message-ID: <1268967396.18.1662029059090.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 336 Status: Still Failing Timestamp: 20220901T043044Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220901T043044Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Ghada.Khalil at windriver.com Thu Sep 1 12:15:52 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 1 Sep 2022 12:15:52 +0000 Subject: [Starlingx-discuss] StarlingX TSC & Community Call [APAC Friendly Time] Message-ID: As discussed in recent community meetings, we will be meeting once a month (first Wednesday) at 7pm PDT/ 10pm EDT / +1 10am CST https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2080 bytes Desc: not available URL: From Thiago.Brito at windriver.com Thu Sep 1 13:02:54 2022 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Thu, 1 Sep 2022 13:02:54 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Log says "InterpreterNotFound". The node you zuul is running it into (ubuntu-focal) doesn't have python3.6. You can either change your nodeset to "ubuntu-bionic" on .zuul.yaml or, as I said before, change everything to python3.9 (running on debian-bullseye) and don't carry technical debt from start. Thiago ________________________________ From: Shivashankara Belur, Nidhi Sent: Wednesday, August 31, 2022 8:23 PM To: Brito, Thiago ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] I updated the pylint env from ?python3? to ?python3.6?, but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada ; Shivashankara Belur, Nidhi ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a ?recheck? this morning still failed. Thanks, Ghada PS: It?s recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn?t quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Thu Sep 1 13:13:48 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 1 Sep 2022 13:13:48 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 31-August-22 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, Juanita Balaraj ============ 31-August-22 StarlingX 7.0 Release: - Stx 7.0 GA date is now September 7th - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - https://review.opendev.org/c/starlingx/docs/+/855079 - AR Juanita to merge - DONE - Prep Sphinx for r7: https://review.opendev.org/c/starlingx/docs/+/850411 - Juanita to merge on Sept 7th Gerrit Reviews: - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Juanita to merge on Sept 7th - Stx Release Notes - https://review.opendev.org/c/starlingx/docs/+/850424 - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - Docs team to confirm the date. - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open ; 2 Cherry picks this week to Stx 6.0. Merged 1 Review. Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 7 bugs outstanding General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed (https://review.opendev.org/c/starlingx/docs/+/822030) - StarlingX PTG: https://etherpad.opendev.org/p/stx-ptg-planning-october-2022 - Elections: Nov 15-22 [1] https://docs.starlingx.io/election/#election-officials [2] https://docs.starlingx.io/governance/reference/tsc/index.html _______________________________________________ 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 Rob.Cooke at windriver.com Thu Sep 1 13:46:12 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Thu, 1 Sep 2022 13:46:12 +0000 Subject: [Starlingx-discuss] FW: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) In-Reply-To: References: Message-ID: Hi, Below are the results of the Sanity execution on the latest STX7.0 Release Candidate build, http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220830T131020Z/. We had a successful sanity. We ran into a few issues on the STX+Openstack sanity run and are in the process of re-executing that run. More to come for openstack. Thanks, Rob From: Winnicki, Chris Sent: Wednesday, August 31, 2022 1:26 PM Subject: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Overall Status: GREEN Lab: WCP_111 Node Config: AIO-SX Load: r/stx.7.0 Job: STX_7.0_build_layer_flock Test Logs: abstract log: test_steps.log, pytestlog.log full log: TIS_AUTOMATION.log http://128.224.186.235/auto_logs/wcp_111/202208311623 All Cases: PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[pods] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[alarms] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[system_apps] PASS testcases/functional/mtc/test_lock_unlock_host.py::test_lock_unlock_host[controller] PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_pod_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_service_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_host_to_service_connection PASS testcases/wrcp/regression/horizon/test_hosts.py::test_horizon_host_inventory_display http://128.224.150.21/jenkins/job/WRCP_SANITY/147/artifact/report.html Chris Winnicki chris.winnicki at windriver.com 613-963-1329 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nidhi.shivashankara.belur at intel.com Thu Sep 1 14:03:23 2022 From: nidhi.shivashankara.belur at intel.com (Shivashankara Belur, Nidhi) Date: Thu, 1 Sep 2022 14:03:23 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Thank you for the suggestion. I would like to try another build with including nodeset as ubuntu-bionic in .zuul.com. Does that require python3.6 as well or can we change it back to python3? In case the above still fails, what are all the files that needs to be modified and what are the changes that needs to be made in order to change everything to python3.9? Are there any other applications that I can refer to which already have moved to python3.9 for pylint zuul job? Nidhi From: Brito, Thiago Sent: Thursday, September 1, 2022 6:03 AM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Log says "InterpreterNotFound". The node you zuul is running it into (ubuntu-focal) doesn't have python3.6. You can either change your nodeset to "ubuntu-bionic" on .zuul.yaml or, as I said before, change everything to python3.9 (running on debian-bullseye) and don't carry technical debt from start. Thiago ________________________________ From: Shivashankara Belur, Nidhi > Sent: Wednesday, August 31, 2022 8:23 PM To: Brito, Thiago >; Khalil, Ghada >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] I updated the pylint env from "python3" to "python3.6", but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago > Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada >; Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a "recheck" this morning still failed. Thanks, Ghada PS: It's recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn't quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From nidhi.shivashankara.belur at intel.com Thu Sep 1 14:35:59 2022 From: nidhi.shivashankara.belur at intel.com (Shivashankara Belur, Nidhi) Date: Thu, 1 Sep 2022 14:35:59 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Update on this issue : Zuul build error for pylint was resolved by following changes. * Modified tox.ini to use "basepython = python3.6" for [testenv:pylint] * Added "nodeset: ubuntu-bionic" to .zuul.yaml for pylint job Nidhi From: Shivashankara Belur, Nidhi Sent: Thursday, September 1, 2022 7:03 AM To: Brito, Thiago ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Thank you for the suggestion. I would like to try another build with including nodeset as ubuntu-bionic in .zuul.com. Does that require python3.6 as well or can we change it back to python3? In case the above still fails, what are all the files that needs to be modified and what are the changes that needs to be made in order to change everything to python3.9? Are there any other applications that I can refer to which already have moved to python3.9 for pylint zuul job? Nidhi From: Brito, Thiago > Sent: Thursday, September 1, 2022 6:03 AM To: Shivashankara Belur, Nidhi >; Khalil, Ghada >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Log says "InterpreterNotFound". The node you zuul is running it into (ubuntu-focal) doesn't have python3.6. You can either change your nodeset to "ubuntu-bionic" on .zuul.yaml or, as I said before, change everything to python3.9 (running on debian-bullseye) and don't carry technical debt from start. Thiago ________________________________ From: Shivashankara Belur, Nidhi > Sent: Wednesday, August 31, 2022 8:23 PM To: Brito, Thiago >; Khalil, Ghada >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] I updated the pylint env from "python3" to "python3.6", but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago > Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada >; Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a "recheck" this morning still failed. Thanks, Ghada PS: It's recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn't quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thiago.Brito at windriver.com Thu Sep 1 14:44:23 2022 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Thu, 1 Sep 2022 14:44:23 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: To use python3.9, you'd have to change the nodeset on .zuul.yaml to debian-bullseye (copy from python3.9 and you should be good)[1]. On tox.ini, you need to use the same upper-constraints as you do for python3.9 (the one that comes from starlingx/root)[2]. You can find a good example on [3] where I defaulted all envs for python3.9 and used 3.6 only on venvs that doesn't have support for python3.9. Make sure you execute those tox tests locally before you try to make zuul try them (just because it's easier to spot any requirement inconsistency running locally). You can test using the same command zuul uses (tox -c python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/tox.ini -e pylint). [1]https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179/19/.zuul.yaml#19 [2]https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179/19/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/tox.ini#27 [3]https://github.com/starlingx/openstack-armada-app/blob/master/python-k8sapp-openstack/k8sapp_openstack/tox.ini Thiago ________________________________ From: Shivashankara Belur, Nidhi Sent: Thursday, September 1, 2022 11:03 AM To: Brito, Thiago ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Thank you for the suggestion. I would like to try another build with including nodeset as ubuntu-bionic in .zuul.com. Does that require python3.6 as well or can we change it back to python3? In case the above still fails, what are all the files that needs to be modified and what are the changes that needs to be made in order to change everything to python3.9? Are there any other applications that I can refer to which already have moved to python3.9 for pylint zuul job? Nidhi From: Brito, Thiago Sent: Thursday, September 1, 2022 6:03 AM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Log says "InterpreterNotFound". The node you zuul is running it into (ubuntu-focal) doesn't have python3.6. You can either change your nodeset to "ubuntu-bionic" on .zuul.yaml or, as I said before, change everything to python3.9 (running on debian-bullseye) and don't carry technical debt from start. Thiago ________________________________ From: Shivashankara Belur, Nidhi > Sent: Wednesday, August 31, 2022 8:23 PM To: Brito, Thiago >; Khalil, Ghada >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] I updated the pylint env from ?python3? to ?python3.6?, but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago > Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada >; Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a ?recheck? this morning still failed. Thanks, Ghada PS: It?s recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn?t quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From Charles.Short at windriver.com Thu Sep 1 14:57:05 2022 From: Charles.Short at windriver.com (Short, Charles) Date: Thu, 1 Sep 2022 14:57:05 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Hi, Since we are discussing this now, I think we should have the discussion to move from testing with Python3.6 to Python3.9 since Centos 7 is going away. Regards chuck From: Brito, Thiago Sent: Thursday, September 1, 2022 10:44 AM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration To use python3.9, you'd have to change the nodeset on .zuul.yaml to debian-bullseye (copy from python3.9 and you should be good)[1]. On tox.ini, you need to use the same upper-constraints as you do for python3.9 (the one that comes from starlingx/root)[2]. You can find a good example on [3] where I defaulted all envs for python3.9 and used 3.6 only on venvs that doesn't have support for python3.9. Make sure you execute those tox tests locally before you try to make zuul try them (just because it's easier to spot any requirement inconsistency running locally). You can test using the same command zuul uses (tox -c python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/tox.ini -e pylint). [1]https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179/19/.zuul.yaml#19 [2]https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179/19/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/tox.ini#27 [3]https://github.com/starlingx/openstack-armada-app/blob/master/python-k8sapp-openstack/k8sapp_openstack/tox.ini Thiago ________________________________ From: Shivashankara Belur, Nidhi Sent: Thursday, September 1, 2022 11:03 AM To: Brito, Thiago ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Thank you for the suggestion. I would like to try another build with including nodeset as ubuntu-bionic in .zuul.com. Does that require python3.6 as well or can we change it back to python3? In case the above still fails, what are all the files that needs to be modified and what are the changes that needs to be made in order to change everything to python3.9? Are there any other applications that I can refer to which already have moved to python3.9 for pylint zuul job? Nidhi From: Brito, Thiago Sent: Thursday, September 1, 2022 6:03 AM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Log says "InterpreterNotFound". The node you zuul is running it into (ubuntu-focal) doesn't have python3.6. You can either change your nodeset to "ubuntu-bionic" on .zuul.yaml or, as I said before, change everything to python3.9 (running on debian-bullseye) and don't carry technical debt from start. Thiago ________________________________ From: Shivashankara Belur, Nidhi > Sent: Wednesday, August 31, 2022 8:23 PM To: Brito, Thiago >; Khalil, Ghada >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] I updated the pylint env from "python3" to "python3.6", but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago > Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada >; Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [Image removed by sender.] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a "recheck" this morning still failed. Thanks, Ghada PS: It's recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn't quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD0000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD0000.jpg URL: From Ghada.Khalil at windriver.com Thu Sep 1 18:03:49 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 1 Sep 2022 18:03:49 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Aug 31 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call August 31, 2022 Standing topics - Build - r/stx.7.0 Builds - On demand - Build requested and initiated on Aug 30. Build was successful. - Build includes fix for openstack LP: https://bugs.launchpad.net/starlingx/+bug/1970645 - Main Branch CentOS Builds - Container build failure reported: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013304.html - Davlet will investigate - Main Branch Debian Builds - Debian build is in progress - One failure was seen during the weekend; was a CENGN server clock issue. - One potential bug is under investigation. LP will be created once confirmed. - Sanity - Main Branch Sanity w/o stx-openstack - Not restarted due to bandwidth issues. Will restart after stx.7.0 sanity is complete. - Main Branch Sanity w/ stx-openstack - Env issues resolved; were able to run one previous sanity and hit https://bugs.launchpad.net/starlingx/+bug/1970645 which is now resolved. - Not restarted due to bandwidth issues. Will restart after stx.7.0 sanity is complete. - stx.7.0 sanity - Sanity starting today (Aug 31) on the latest build (Aug 30): https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013307.html - Plan to run w/ and w/o openstack. Should have results within 24hrs. - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes - https://review.opendev.org/c/starlingx/docs/+/850424 - Reviewed by Ghada, Frank, Greg, Steve, Ram. Ildiko to do final review today. - Action: Juanita to address final minor issues and merge before EOW. - FEC Operator Configurability - https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179 - Currently failing zuul; unclear what the issue is. Email forwarded to the mailing list for help. - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Status - Release Branch: - https://review.opendev.org/q/branch:r/stx.7.0 - Two review are still open: https://review.opendev.org/q/branch:r/stx.7.0+status:open - Minor as they just setup the .gitreview for the repo - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - None - Release Milestones ( https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 ) - Minor re-forecast this week - Sanity/Final Regression Complete: Aug 17 >> Re-forecast: Aug 31 >> Re-forecast: Sep 2 - Release: Aug 24 >> Re-forecast: Sep 7 >> Re-forecast: Sep 9 - Need a day or two for Scott to do the branch tagging and move the built artifacts to the proper location. - REMINDER!! TSC & Community Meeting Schedule - Updated to meet during an APAC-friendly time once a month; first Wednesday of the month - First meeting on Sept 7. - REMINDER!! Board of Directors Meeting - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013281.html - Scheduled on Sept 7 9am Eastern - All is welcome to attend - Etherpad available to collect topics for discussion: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync - Discussion with Scott V Kamp (https://launchpad.net/~skamp007) - wireguard discussion / build discussion / improving community communication discussion - Discussion about his participation move actively in the community - Next steps: - Recommend for Scott to join the distro-os bi-weekly calls: Every other Wednesday 9:30am Eastern (next meeting: Sep 14) - Follow Up discussion w/ Steve Geary ARs from Previous Meetings - None Open Requests for Help - Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html - Still no response on the thread, the person followed-up with mentioning issues of nvidia driver install - Action: Greg ... still pending due to vacation. - Wireguard issue - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 - Scott Kamp (issue reporter) attended this week to discuss an update. - From MarkA: The stx OS team will enable the wireguard in the kernel in StarlingX. However the OS team will not do specific testing/support on wireguard due to bandwidth constraints. From ildiko.vancsa at gmail.com Thu Sep 1 21:33:25 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 1 Sep 2022 14:33:25 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync In-Reply-To: References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> <04B5EB72-75E4-49D2-BCE3-AD2662366162@gmail.com> Message-ID: <98951643-33C3-4F41-B202-06E9E3FE1726@gmail.com> Hi StarlingX Community, It is a friendly reminder that the OpenInfra Board of Directors - StarlingX meeting is scheduled to be held on September 7 (Wednesday) at 6am PDT / 1300 UTC. We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync Please add any topics that you would like to discuss with the OpenInfra BoD members during the meeting. I also added the dial-in details to the etherpad. Please let me know if you need a meeting invite or if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 23, 2022, at 13:07, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you with a short update. > > The OpenInfra Board of Directors - StarlingX meeting is now scheduled to be held on September 7 (Wednesday) at 6am PDT / 1300 UTC. > > We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please add any topics that you would like to discuss with the OpenInfra BoD members during the meeting. I also added the dial-in details to the etherpad. > > Please let me know if you would need a meeting invite or if you have any questions. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Aug 15, 2022, at 13:44, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> Thank you all who filled out the polls. I?m reaching out to share the results. >> >> The preferred option to have the OpenInfra Board of Directors - StarlingX meeting is September 7 (Wednesday) at 6am PDT / 1300 UTC. >> >> Further options that could potentially work include the same time slot on September 8 (Thursday) and September 14 (Wednesday). >> >> I will share the preferred time slot with the Board with the hope that it will work, and will opt to fallback options in case needed. >> >> Thanks and Best Regards, >> Ildik? >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Aug 11, 2022, at 12:17, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> It is a friendly reminder that we have two polls open in an attempt to find a few options to set up a call with the OpenInfra Foundation Board of Directors: >>> >>> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >>> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >>> >>> __Please submit your preferences by August 14, 2022.__ >>> >>> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra BoD group! >>> >>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>>> On Aug 3, 2022, at 00:06, Ildiko Vancsa wrote: >>>> >>>> Hi, >>>> >>>> I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html >>>> >>>> Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: >>>> >>>> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >>>> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >>>> >>>> __Please submit your preferences by August 14, 2022.__ >>>> >>>> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>> >>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>> >>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>> >>>> Thanks and Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>>> On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: >>>>> >>>>> Hi Greg, >>>>> >>>>> I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. >>>>> >>>>> Best Regards, >>>>> Ildik? >>>>> >>>>> >>>>>> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >>>>>> >>>>>> I can't find the zoom link for the meeting ... do you have it ? >>>>>> Greg. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ildiko Vancsa >>>>>> Sent: Wednesday, July 27, 2022 2:16 AM >>>>>> To: Waines, Greg >>>>>> Cc: StarlingX ML >>>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >>>>>> >>>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> Great, thank you for being available! >>>>>> >>>>>> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >>>>>> >>>>>> I think diversity is a great topic for the call and should be a basis for a good discussion. >>>>>> >>>>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>>>> >>>>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>>>> >>>>>> Thanks and Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Senior Manager, Community & Ecosystem >>>>>> Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>>>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>>>>>> >>>>>>> hey Ildiko, >>>>>>> I am available on the Aug 4 1300 UTC timeslot. >>>>>>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>>>>>> >>>>>>> I added our favourite discussion topic to the etherpad: >>>>>>> * Looking for guidance on diversifying the Users and >>>>>>> Contributors in the community >>>>>>> >>>>>>> Greg. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ildiko Vancsa >>>>>>> Sent: Tuesday, July 26, 2022 5:47 AM >>>>>>> To: StarlingX ML >>>>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>>>>>> StarlingX Sync - UPDATE >>>>>>> >>>>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>>>> >>>>>>> Hi StarlingX Community, >>>>>>> >>>>>>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>>>>>> >>>>>>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>>>>>> >>>>>>> You can see the original email and follow the thread here: >>>>>>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>>>>>> 6.html >>>>>>> >>>>>>> As a reminder, we have an etherpad to propose topics for the call and >>>>>>> take notes during the meeting: >>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>> >>>>>>> Please let me know if you have any questions. >>>>>>> >>>>>>> Best Regards, >>>>>>> Ildik? >>>>>>> >>>>>>> ??? >>>>>>> >>>>>>> Ildik? V?ncsa >>>>>>> Senior Manager, Community & Ecosystem >>>>>>> Open Infrastructure Foundation >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>>>>>> >>>>>>>> Hi StarlingX Community, >>>>>>>> >>>>>>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>>>>>> >>>>>>>> You can find the poll here: >>>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>>> >>>>>>>> __Please submit your preferences on the poll by the end of day on >>>>>>>> July 20, 2022.__ >>>>>>>> >>>>>>>> >>>>>>>> I created an etherpad to collect potential topics for the >>>>>>>> conversation and build an agenda for the call. Please add discussion >>>>>>>> points that you think would be important to bring up during the call: >>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>> >>>>>>>> Please let me know if you have any questions. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Ildik? >>>>>>>> >>>>>>>> ??? >>>>>>>> >>>>>>>> Ildik? V?ncsa >>>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>>>>>> >>>>>>>>> Hi StarlingX Community, >>>>>>>>> >>>>>>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>>>>>> >>>>>>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>>>>>> >>>>>>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>>>>>> >>>>>>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>>>>>> >>>>>>>>> I created an etherpad to collect potential topics for the >>>>>>>>> conversation and build an agenda for the call: >>>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>>> >>>>>>>>> I also created a poll to try to find time slot options that we can >>>>>>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>>>>>> options for August, if we fail to find good options for that month, I >>>>>>>>> will extend it to September. Please find the poll here: >>>>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>>>> >>>>>>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>>>>>> >>>>>>>>> __Please submit your preferences by the end of day on July 20, >>>>>>>>> 2022.__ >>>>>>>>> >>>>>>>>> Please let me know if you have any questions. >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> Ildik? >>>>>>>>> >>>>>>>>> ??? >>>>>>>>> >>>>>>>>> Ildik? V?ncsa >>>>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>> >>>> >>> >> > From Rob.Cooke at windriver.com Fri Sep 2 15:30:25 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Fri, 2 Sep 2022 15:30:25 +0000 Subject: [Starlingx-discuss] Green: AIO-SX STX_7.0_build_layer_flock (202208311118) In-Reply-To: References: Message-ID: Hi, An update on openstack sanity. We continue to uncover some configuration issues with our execution but remain focused on the task. Will continue to provide updates as they come in. Thanks, Rob From: Cooke, Rob Sent: Thursday, September 1, 2022 9:46 AM To: starlingx-discuss at lists.starlingx.io Subject: FW: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Hi, Below are the results of the Sanity execution on the latest STX7.0 Release Candidate build, http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220830T131020Z/. We had a successful sanity. We ran into a few issues on the STX+Openstack sanity run and are in the process of re-executing that run. More to come for openstack. Thanks, Rob From: Winnicki, Chris > Sent: Wednesday, August 31, 2022 1:26 PM Subject: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Overall Status: GREEN Lab: WCP_111 Node Config: AIO-SX Load: r/stx.7.0 Job: STX_7.0_build_layer_flock Test Logs: abstract log: test_steps.log, pytestlog.log full log: TIS_AUTOMATION.log http://128.224.186.235/auto_logs/wcp_111/202208311623 All Cases: PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[pods] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[alarms] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[system_apps] PASS testcases/functional/mtc/test_lock_unlock_host.py::test_lock_unlock_host[controller] PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_pod_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_service_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_host_to_service_connection PASS testcases/wrcp/regression/horizon/test_hosts.py::test_horizon_host_inventory_display http://128.224.150.21/jenkins/job/WRCP_SANITY/147/artifact/report.html Chris Winnicki chris.winnicki at windriver.com 613-963-1329 -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sat Sep 3 08:15:30 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 3 Sep 2022 04:15:30 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1542 - Failure! Message-ID: <255089342.22.1662192932101.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1542 Status: Failure Timestamp: 20220903T044455Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220903T043002Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220903T043002Z DOCKER_BUILD_ID: jenkins-master-20220903T043002Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220903T043002Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220903T043002Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Sat Sep 3 08:15:34 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 3 Sep 2022 04:15:34 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1399 - Failure! Message-ID: <1870828065.25.1662192935703.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1399 Status: Failure Timestamp: 20220903T043002Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220903T043002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From openinfradn at gmail.com Sat Sep 3 17:05:02 2022 From: openinfradn at gmail.com (open infra) Date: Sat, 3 Sep 2022 22:35:02 +0530 Subject: [Starlingx-discuss] What is the base OS for Starlingx Release 6 In-Reply-To: <90148E8E-ED79-4D6A-8491-C14C14D18BE7@gmail.com> References: <90148E8E-ED79-4D6A-8491-C14C14D18BE7@gmail.com> Message-ID: Hi Ildiko, Sorry for the late reply. I was strugling to install dependencies (gcc) for Nvidia GPU drivers on STX 6 worker nodes. Finally created a local repo and inststalled dependencies using 'Developer Toolset 8' [1]. It would be great if correct gcc version available for stx 7 worker nodes. My original question is about, why CentOS 7 is use as the baseos for nodes. But later I noticed still CentOS7 get maintainer updates [2] [1] https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/8/html/8.0_release_notes/dts8.0_release [2] https://wiki.centos.org/About/Product Regards Danishka On Fri, Aug 12, 2022 at 3:09 AM Ildiko Vancsa wrote: > Hi Danishka, > > Thank you for reaching out with the issues you?re experiencing. Can you > share a bit more information about the failures that you?re seeing? > > Best Regards, > Ildik? > > > > On Aug 1, 2022, at 06:17, open infra wrote: > > > > I am suppose to install nvidia driver on a worker (stx 6) which require > few dependencies including gcc and make. > > When I use CentOS 7 nvidia driver compilation/installation fails and > with Rocky linux 9 gcc installation fails. > > > > > > On Thu, Jul 28, 2022 at 4:01 PM open infra > wrote: > > Hi, > > > > Which CentOS release is the compatible with STX release boot image? > > > > Regards, > > Danishka > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Mon Sep 5 14:33:01 2022 From: openinfradn at gmail.com (open infra) Date: Mon, 5 Sep 2022 20:03:01 +0530 Subject: [Starlingx-discuss] Attempt to PCI Passthrough in Stx ended up with "no valid host available" error Message-ID: Hi, I recently noticed that newly added workers not able to host any openstack instance but only few workers (which created very early in our setup) able to host instanes created in openstack side. system application-apply stx-openstack is failed at downloading docker images though controller can ping outside. No specific information found on system inventory log and no armada log at all for stx-openstack-apply. When I looking at stx active alarms, there was a failure of stx-openstack apply, which was on the day apply changes to enable PCI Pasthrough. [1]. I can see all the workers when I check nodes from kubernetes side. 01. How to get the stx-openstack application apply without fail at docker image download? I tried to remove the line added into helm override yaml to add pci passthrough device and apply the application but it failed. 02. I need to enable Nvidia T10 cards in selected nodes as PCI Passtrough. Should we add all selected gpu pci addresses to controller? Is there a complete guide for enabling PCI Passthorugh with GPU cards in starlingx side as well as openstack setup as well? [1] https://docs.starlingx.io/node_management/openstack/configure-pci-passthrough-interface-to-nvidia-gpu.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Sep 6 03:55:12 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Sep 2022 23:55:12 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 580 - Still Failing! In-Reply-To: <770724167.10.1662029045524.JavaMail.javamailuser@localhost> References: <770724167.10.1662029045524.JavaMail.javamailuser@localhost> Message-ID: <431600347.30.1662436514673.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 580 Status: Still Failing Timestamp: 20220906T001905Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220905T230914Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220905T230914Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/logs PUBLISH_TIMESTAMP: 20220905T230914Z FLOCK_VERSION: master-centos-stable-20220905T230914Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220905T230914Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Tue Sep 6 03:55:16 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Sep 2022 23:55:16 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 336 - Still Failing! In-Reply-To: <766944040.13.1662029051749.JavaMail.javamailuser@localhost> References: <766944040.13.1662029051749.JavaMail.javamailuser@localhost> Message-ID: <1641177706.33.1662436517824.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 336 Status: Still Failing Timestamp: 20220905T234656Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220905T230914Z 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/20220905T230914Z/logs MASTER_BUILD_NUMBER: 337 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/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: 20220905T230914Z DOCKER_BUILD_ID: jenkins-master-containers-20220905T230914Z-builder TIMESTAMP: 20220905T230914Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/outputs From starlingx.build at gmail.com Tue Sep 6 03:55:20 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Sep 2022 23:55:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 337 - Still Failing! In-Reply-To: <74423189.16.1662029056904.JavaMail.javamailuser@localhost> References: <74423189.16.1662029056904.JavaMail.javamailuser@localhost> Message-ID: <934593443.36.1662436521151.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 337 Status: Still Failing Timestamp: 20220905T230914Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Rob.Cooke at windriver.com Tue Sep 6 14:20:39 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 6 Sep 2022 14:20:39 +0000 Subject: [Starlingx-discuss] Green: AIO-SX STX_7.0_build_layer_flock (202208311118) In-Reply-To: References: Message-ID: Hi, We have successfully completed sanity on stx7.0+openstack, the results are captured below. There was once minor issue reported, https://bugs.launchpad.net/starlingx/+bug/1988778 which failed two tests, but this issue is deemed not gating for the release. Sanity is now complete across the board. Final regression has also completed and is tracked here https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 Thanks, Rob --------------- Job: STX_7.0_build_layer_flock Build Server: starlingx_mirror Build ID: r/stx.7.0 OpenStack Deployed: stx-openstack Node Config: AIO-DX End Time: 20220905 17:17:41 Overall Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 13 (86.67%) Failed: 2 (13.33%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20220905 15:40:37 test_ssh_to_hosts FAIL 20220905 15:41:22 test_lock_unlock_host[controller] PASS 20220905 16:07:00 test_swact_controllers PASS 20220905 16:17:30 test_openstack_services_healthy PASS 20220905 16:18:01 test_reapply_stx_openstack_no_change[controller-0] PASS 20220905 16:22:34 test_reapply_stx_openstack_no_change[controller-1] PASS 20220905 16:28:44 test_horizon_create_delete_instance PASS 20220905 16:30:27 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20220905 16:34:14 test_migrate_vm[tis-centos-guest-live-None] PASS 20220905 16:37:46 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20220905 16:40:16 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20220905 16:42:53 test_evacuate_vms PASS 20220905 17:17:00 test_system_coredumps_and_crashes[core_dumps] PASS 20220905 17:17:11 test_system_coredumps_and_crashes[crash_reports] PASS 20220905 17:17:18 test_system_alarms ----------------------------------------------------------------------- From: Cooke, Rob Sent: Friday, September 2, 2022 11:30 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Hi, An update on openstack sanity. We continue to uncover some configuration issues with our execution but remain focused on the task. Will continue to provide updates as they come in. Thanks, Rob From: Cooke, Rob Sent: Thursday, September 1, 2022 9:46 AM To: starlingx-discuss at lists.starlingx.io Subject: FW: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Hi, Below are the results of the Sanity execution on the latest STX7.0 Release Candidate build, http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220830T131020Z/. We had a successful sanity. We ran into a few issues on the STX+Openstack sanity run and are in the process of re-executing that run. More to come for openstack. Thanks, Rob From: Winnicki, Chris > Sent: Wednesday, August 31, 2022 1:26 PM Subject: Green: AIO-SX STX_7.0_build_layer_flock (202208311118) Overall Status: GREEN Lab: WCP_111 Node Config: AIO-SX Load: r/stx.7.0 Job: STX_7.0_build_layer_flock Test Logs: abstract log: test_steps.log, pytestlog.log full log: TIS_AUTOMATION.log http://128.224.186.235/auto_logs/wcp_111/202208311623 All Cases: PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[pods] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[alarms] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[system_apps] PASS testcases/functional/mtc/test_lock_unlock_host.py::test_lock_unlock_host[controller] PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_pod_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_service_connection PASS testcases/functional/networking/test_pod_to_pod.py::TestPodtoPod::test_host_to_service_connection PASS testcases/wrcp/regression/horizon/test_hosts.py::test_horizon_host_inventory_display http://128.224.150.21/jenkins/job/WRCP_SANITY/147/artifact/report.html Chris Winnicki chris.winnicki at windriver.com 613-963-1329 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Tue Sep 6 16:07:38 2022 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 6 Sep 2022 16:07:38 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 580 - Still Failing! In-Reply-To: <431600347.30.1662436514673.JavaMail.javamailuser@localhost> References: <770724167.10.1662029045524.JavaMail.javamailuser@localhost> <431600347.30.1662436514673.JavaMail.javamailuser@localhost> Message-ID: 3 containers are failing due to updated upstream python dependencies: locationservice-base notificationclient-base notificationservice-base https://bugs.launchpad.net/starlingx/+bug/1988854 ________________________________ From: starlingx.build at gmail.com Sent: September 5, 2022 11:55 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 580 - Still Failing! [Please note: This e-mail is from an EXTERNAL e-mail address] Project: STX_build_docker_flock_images Build #: 580 Status: Still Failing Timestamp: 20220906T001905Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220905T230914Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220905T230914Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/logs PUBLISH_TIMESTAMP: 20220905T230914Z FLOCK_VERSION: master-centos-stable-20220905T230914Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220905T230914Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220905T230914Z/outputs REGISTRY: docker.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Sep 6 17:58:51 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 6 Sep 2022 13:58:51 -0400 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: I think you read it backwards.?? I'll try again (inline below) Scott On 2022-07-27 09:57, Kumar, Chandan wrote: > > **[Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Scott, > > I was going through the procedure that you have shared below. Please > clarify these two points: > > * The rpms need to be unpacked, the relevant binaries signed with > correct keys, and the rpms reassembled. : The signing server > unpacks images like BOOTX64, shim, shimx64 to get rpms, then signs > it using `sbsign` and then repack it as original image. Is this > understanding correct ? > It unpacks RPM: shim*rpm It looks for files matching: ??? BOOTX64*, shim*, shimx64*, which it signs with the 'boot' key; and ??? MokManager*, fallback*, mmx64*, fbx64* , which it signs with the 'shim' key ? ? Note: * above should be one of .efi or .EFI Finally it repack the shim RPM file. Repeat per the below table for the other RPMS. > * > * shim.crt - Certificated embedded within shim used to validate > kernel, grub : How is this certificate embedded inside shim image ? > > I got review notification for launchpad, I had raised but could not > find where to add comments so replying to this mail. > > Regards, > > Chandan Kumar. > > *From:* Waines, Greg > *Sent:* Wednesday, July 13, 2022 8:14 PM > *To:* StarlingX ML > *Cc:* Kumar, Chandan > *Subject:* FW: [Starlingx-discuss] Incorrect public key for signed > starlingX 5.0 iso . > > Forwarding ?. > > I think scott meant this for the starlingx discuss list. > > Greg. > > *From:* Little, Scott > *Sent:* Wednesday, July 6, 2022 2:37 PM > *To:* Waines, Greg > *Subject:* Re: [Starlingx-discuss] Incorrect public key for signed > starlingX 5.0 iso . > > I'll attempt to answer this at a high level. > > Secure boot signing uses a client/server approach.? build-pkgs acts as > the client. The server holds the signing scripts and the keys used for > signing. > > The client side code was released to open source as part of > StarlingX.? The server side code was not released. > > The interface between client and server is currently undocumented.? > I'll try to give an overview as best I can.? Basically it is a series > of ssh/scp calls made into signing server. > > 'build-pkgs' requires that the following environment variables be > defined before it will attempt to request a secure boot signing. > > export SIGNING_SERVER= > export SIGNING_USER= > > export SIGNING_SERVER_SCRIPT= > > 'build-pkgs' further requires that "$USER" == "jenkins", and > > export FORMAL_BUILD=1 > > If that is satisfied, it calls into 'sign-secure-boot' > > 'sign-secure-boot' contains a fairly good set of comments describing > what happens next. > > The client side call sequence looks like this ... > > ??? # Set up the server side directory for files transfers. > ??? UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo > $SIGNING_SCRIPT -r` > > ??? # upload the original package > ??? scp -q $FILE $SIGNING_USER@$SIGNING_SERVER:$UPLOAD_PATH <#REDACTED> > > ??? # Request that the package be signed > ??? ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -v -i > $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t $TYPE > $TMPFILE > > ??? # Download the file from the signing server > ??? DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE) > ??? scp -q $SIGNING_USER@$SIGNING_SERVER:$OUTPUT_FILE <#REDACTED> > $(dirname $FILE) > > Within the signing server there are two keys used for signing, known > as the 'boot' key and the 'shim' key.? The public half of the 'boot' > key must manually added to the secure boot keychain in firmware.? The > 'boot' key signs first executable loaded, contained in the 'shim' > package. The first executable must then install the public half of the > shim key (automatically) before passing control to grub, and > ultimately the kernel, both of which are signed by the 'shim' key. > > Three packages need to be passed to the signing server. The rpms need > to be unpacked, the relevant binaries signed with correct keys, and > the rpms reassembled. > > package??? key?? files to sign > =========? ====? =========================== > shim?????? boot? BOOTX64, shim, shimx64 > ?????????? shim? MokManager, fallback, mmx64, fbx64 > grub?????? shim? grubx64.efi, gcdx64.efi > kernel???? shim? vmlinuz > > NOTE: shim files to sign might include a '.efi' or '.EFI' suffix.? > Sign those as well. > > NOTE: some files may be absent in newer packages.? It is probably ok > if some of the above are missing. > > Signing looks like this ... > > ??? sbsign --key $KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt? > --output $SIGNEDFILE $UNSIGNEDFILE > > On keys and certs ... > > ?? boot.crt - Certificate to boot (to be programmed in firmware) > ?? boot.key - Private key with which to sign shim > ?? shim.crt - Certificated embedded within shim used to validate > kernel, grub > ?? shim.key - Private key with which to sign kernel/grub > > key generation ... > > |openssl req -new -x509 -newkey |rsa:2048 <#REDACTED>|-keyout $KEY.key > -out $KEY.pem -days 3650| > > |openssl x509 -in $KEY.pem -out $KEY.crt -outform DER| > > Note: boot.crt should be copied to > cgcs-root/build-tools/certificates/TiBoot.crt for inclusion during > the? 'build-iso' step > > Hope this helps > > Scott > > On 2022-07-05 03:19, Kumar, Chandan wrote: > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Greg, > > Thanks for acknowledgement. > > I have raised starlingx launchpad ?for document update. Meanwhile > it would be really great if you can share the steps which has to > be done to integrate signing of images as part of StarlingX build > infrastructure. > > Regards, > > Chandan Kumar. > > *From:* Waines, Greg > > *Sent:* Monday, July 4, 2022 6:00 PM > *To:* starlingx-discuss at lists.starlingx.io > *Cc:* Little, Scott > > *Subject:* Re: [Starlingx-discuss] Incorrect public key for signed > starlingX 5.0 iso . > > Hey Chandan, > > Thanks for bringing this up. > > I chatted with Scott about this. > > Currently the StarlingX public builds on CENGN are not building a > secure boot capable load ? i.e. signing the appropriate items to > enable secure boot.? Although the StarlingX build infrastructure > allows it to be added. > > Neither of these points are properly documented in docs.starlingx.io ? > > I can?t remember the details of why we are not doing this. > > I am guessing that the thinking was that a user of StarlingX that > wanted to use UEFI Secure Boot, would want to sign with his own > private key. > > Can you raise a starlingx launchpad ( > https://launchpad.net/starlingx > > ) to address the docs.starlingx.io > > documentation issue, i.e. to indicate that the StarlingX CENGN > builds are not signed to support uefi secure boot, and describe > how a starlingx user could add signing to their StarlingX build > environment in order to sign for uefi secure boot with their own > private key ? > > Greg. > > *From:* Scott Little > *Sent:* Wednesday, June 29, 2022 10:42 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Incorrect public key for signed > starlingX 5.0 iso . > > On 2022-06-02 13:12, Kumar, Chandan wrote: > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > I am trying to validate signed starlingX 5.0 iso on a > secureboot enabled setup against public key(TiBoot.crt) > embedded inside iso. After rebooting , operating system is not > coming up with error screen saying ?Verification failed: > (0X1A) Security Violation?. > > However, when I signed images with self-generated private key > and validated against corresponding public key, system is able > to boot up successfully. Signing is done after flashing the > iso on a server. Please find attached procedure for signing > images inside iso. > > I believe, the public key provided with iso is not correct. > Can you please confirm ? > > Regards, > > Chandan Kumar. > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > Thanks for the report.?? I'll look into it > > Scott Little > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Sep 6 18:14:52 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 6 Sep 2022 14:14:52 -0400 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: <1ffd293f-d22e-8134-ddd3-284b880bf976@windriver.com> On 2022-07-27 09:57, Kumar, Chandan wrote: > shim.crt - Certificated embedded within shim used to validate kernel, > grub : How is this certificate embedded inside shim image ? shim.crt is created as part of the build process for the 'shim' package.?? Refer to stx/integ/security/shim-unsigned/centos/patches/0001-Use-Titanium-certificate.patch -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Sep 6 18:17:10 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 6 Sep 2022 14:17:10 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 337 - Still Failing! In-Reply-To: <934593443.36.1662436521151.JavaMail.javamailuser@localhost> References: <74423189.16.1662029056904.JavaMail.javamailuser@localhost> <934593443.36.1662436521151.JavaMail.javamailuser@localhost> Message-ID: <23263b1b-e647-ef6f-c7c2-f55723f153bf@windriver.com> 3 containers are failing due to updated upstream python dependencies: locationservice-base notificationclient-base notificationservice-base https://bugs.launchpad.net/starlingx/+bug/1988854 On 2022-09-05 23:55, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 337 > Status: Still Failing > Timestamp: 20220905T230914Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Sep 6 19:50:31 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 6 Sep 2022 12:50:31 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync In-Reply-To: <98951643-33C3-4F41-B202-06E9E3FE1726@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> <04B5EB72-75E4-49D2-BCE3-AD2662366162@gmail.com> <98951643-33C3-4F41-B202-06E9E3FE1726@gmail.com> Message-ID: Hi StarlingX Community, It is a friendly reminder that the OpenInfra Board of Directors - StarlingX meeting is scheduled for __tomorrow (September 7 (Wednesday)) at 6am PDT / 1300 UTC__. We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync We will use the following etherpad during the call to take notes: https://etherpad.opendev.org/p/board-starlingx-informal-discussion Please let me know if you need a meeting invite or if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Sep 1, 2022, at 14:33, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder that the OpenInfra Board of Directors - StarlingX meeting is scheduled to be held on September 7 (Wednesday) at 6am PDT / 1300 UTC. > > We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please add any topics that you would like to discuss with the OpenInfra BoD members during the meeting. I also added the dial-in details to the etherpad. > > Please let me know if you need a meeting invite or if you have any questions. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > >> On Aug 23, 2022, at 13:07, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> I?m reaching out to you with a short update. >> >> The OpenInfra Board of Directors - StarlingX meeting is now scheduled to be held on September 7 (Wednesday) at 6am PDT / 1300 UTC. >> >> We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> Please add any topics that you would like to discuss with the OpenInfra BoD members during the meeting. I also added the dial-in details to the etherpad. >> >> Please let me know if you would need a meeting invite or if you have any questions. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Aug 15, 2022, at 13:44, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> Thank you all who filled out the polls. I?m reaching out to share the results. >>> >>> The preferred option to have the OpenInfra Board of Directors - StarlingX meeting is September 7 (Wednesday) at 6am PDT / 1300 UTC. >>> >>> Further options that could potentially work include the same time slot on September 8 (Thursday) and September 14 (Wednesday). >>> >>> I will share the preferred time slot with the Board with the hope that it will work, and will opt to fallback options in case needed. >>> >>> Thanks and Best Regards, >>> Ildik? >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>>> On Aug 11, 2022, at 12:17, Ildiko Vancsa wrote: >>>> >>>> Hi StarlingX Community, >>>> >>>> It is a friendly reminder that we have two polls open in an attempt to find a few options to set up a call with the OpenInfra Foundation Board of Directors: >>>> >>>> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >>>> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >>>> >>>> __Please submit your preferences by August 14, 2022.__ >>>> >>>> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>> >>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra BoD group! >>>> >>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>> >>>> Thanks and Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>>> On Aug 3, 2022, at 00:06, Ildiko Vancsa wrote: >>>>> >>>>> Hi, >>>>> >>>>> I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html >>>>> >>>>> Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: >>>>> >>>>> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >>>>> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >>>>> >>>>> __Please submit your preferences by August 14, 2022.__ >>>>> >>>>> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>> >>>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>>> >>>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>>> >>>>> Thanks and Best Regards, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem >>>>> Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>>>> On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. >>>>>> >>>>>> Best Regards, >>>>>> Ildik? >>>>>> >>>>>> >>>>>>> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >>>>>>> >>>>>>> I can't find the zoom link for the meeting ... do you have it ? >>>>>>> Greg. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ildiko Vancsa >>>>>>> Sent: Wednesday, July 27, 2022 2:16 AM >>>>>>> To: Waines, Greg >>>>>>> Cc: StarlingX ML >>>>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >>>>>>> >>>>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>>>> >>>>>>> Hi Greg, >>>>>>> >>>>>>> Great, thank you for being available! >>>>>>> >>>>>>> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >>>>>>> >>>>>>> I think diversity is a great topic for the call and should be a basis for a good discussion. >>>>>>> >>>>>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>>>>> >>>>>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>>>>> >>>>>>> Thanks and Best Regards, >>>>>>> Ildik? >>>>>>> >>>>>>> ??? >>>>>>> >>>>>>> Ildik? V?ncsa >>>>>>> Senior Manager, Community & Ecosystem >>>>>>> Open Infrastructure Foundation >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>>>>>>> >>>>>>>> hey Ildiko, >>>>>>>> I am available on the Aug 4 1300 UTC timeslot. >>>>>>>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>>>>>>> >>>>>>>> I added our favourite discussion topic to the etherpad: >>>>>>>> * Looking for guidance on diversifying the Users and >>>>>>>> Contributors in the community >>>>>>>> >>>>>>>> Greg. >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Ildiko Vancsa >>>>>>>> Sent: Tuesday, July 26, 2022 5:47 AM >>>>>>>> To: StarlingX ML >>>>>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>>>>>>> StarlingX Sync - UPDATE >>>>>>>> >>>>>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>>>>> >>>>>>>> Hi StarlingX Community, >>>>>>>> >>>>>>>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>>>>>>> >>>>>>>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>>>>>>> >>>>>>>> You can see the original email and follow the thread here: >>>>>>>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>>>>>>> 6.html >>>>>>>> >>>>>>>> As a reminder, we have an etherpad to propose topics for the call and >>>>>>>> take notes during the meeting: >>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>> >>>>>>>> Please let me know if you have any questions. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Ildik? >>>>>>>> >>>>>>>> ??? >>>>>>>> >>>>>>>> Ildik? V?ncsa >>>>>>>> Senior Manager, Community & Ecosystem >>>>>>>> Open Infrastructure Foundation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>>>>>>> >>>>>>>>> Hi StarlingX Community, >>>>>>>>> >>>>>>>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>>>>>>> >>>>>>>>> You can find the poll here: >>>>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>>>> >>>>>>>>> __Please submit your preferences on the poll by the end of day on >>>>>>>>> July 20, 2022.__ >>>>>>>>> >>>>>>>>> >>>>>>>>> I created an etherpad to collect potential topics for the >>>>>>>>> conversation and build an agenda for the call. Please add discussion >>>>>>>>> points that you think would be important to bring up during the call: >>>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>>> >>>>>>>>> Please let me know if you have any questions. >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> Ildik? >>>>>>>>> >>>>>>>>> ??? >>>>>>>>> >>>>>>>>> Ildik? V?ncsa >>>>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>>>>>>> >>>>>>>>>> Hi StarlingX Community, >>>>>>>>>> >>>>>>>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>>>>>>> >>>>>>>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>>>>>>> >>>>>>>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>>>>>>> >>>>>>>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>>>>>>> >>>>>>>>>> I created an etherpad to collect potential topics for the >>>>>>>>>> conversation and build an agenda for the call: >>>>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>>>> >>>>>>>>>> I also created a poll to try to find time slot options that we can >>>>>>>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>>>>>>> options for August, if we fail to find good options for that month, I >>>>>>>>>> will extend it to September. Please find the poll here: >>>>>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>>>>> >>>>>>>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>>>>>>> >>>>>>>>>> __Please submit your preferences by the end of day on July 20, >>>>>>>>>> 2022.__ >>>>>>>>>> >>>>>>>>>> Please let me know if you have any questions. >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> Ildik? >>>>>>>>>> >>>>>>>>>> ??? >>>>>>>>>> >>>>>>>>>> Ildik? V?ncsa >>>>>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Starlingx-discuss mailing list >>>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>>>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>>> >>>>>> >>>>> >>>> >>> >> > From Cole.Walker at windriver.com Tue Sep 6 19:57:12 2022 From: Cole.Walker at windriver.com (Walker, Cole) Date: Tue, 6 Sep 2022 19:57:12 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 337 - Still Failing! In-Reply-To: <23263b1b-e647-ef6f-c7c2-f55723f153bf@windriver.com> References: <74423189.16.1662029056904.JavaMail.javamailuser@localhost> <934593443.36.1662436521151.JavaMail.javamailuser@localhost> <23263b1b-e647-ef6f-c7c2-f55723f153bf@windriver.com> Message-ID: I ran into this recently in my build environment and have a fix available. Working on a review for this now. Cole From: Scott Little Sent: September 6, 2022 2:17 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 337 - Still Failing! 3 containers are failing due to updated upstream python dependencies: locationservice-base notificationclient-base notificationservice-base https://bugs.launchpad.net/starlingx/+bug/1988854 On 2022-09-05 23:55, starlingx.build at gmail.com wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 337 Status: Still Failing Timestamp: 20220905T230914Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220905T230914Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Sep 7 14:14:16 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 7 Sep 2022 07:14:16 -0700 Subject: [Starlingx-discuss] TSC & Community call in the new alternating time slot Message-ID: <6407C6BD-C567-4354-88D5-B770E2ECF379@gmail.com> Hi StarlingX Community, It is a friendly reminder that this is the first occasion when we will have the TSC & Community call in the new APAC-friendly time slot. __The call will happen at 7pm PDT / 10pm EDT / 0200 UTC / (Thursday) 10am CST.__ For details please check the project?s Meetings wiki page: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Ghada.Khalil at windriver.com Wed Sep 7 14:32:46 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 7 Sep 2022 14:32:46 +0000 Subject: [Starlingx-discuss] Releasing stx.7.0 - branch closed for release process Message-ID: Hello all, We finally have a green sanity w/ openstack for r/stx.7.0 release branch. Sanity Emails: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013320.html https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013335.html Final regression was also complete. Regression Link: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 Scott, Please proceed with the final steps of the release process: - Mark the RC candidate release as Green - Tag the branch - Move the build artifacts to the release directory - Mark the build as KEEP Juanita, We will declare stx.7.0 as released at the end of the week. Please ensure any steps required for the documentation is complete by then. All, Please consider the r/stx.7.0 branch closed for software changes and do not merge any further content for the time being. Thanks to all community members who contributed to this release. Regards, Ghada From Ghada.Khalil at windriver.com Wed Sep 7 14:45:02 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 7 Sep 2022 14:45:02 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Sep 7/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.7.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlyclfKFVxKo/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - Sanity Update - Sanity on r/stx.7.0 - Sanity is green on the Aug 30th RC candidate load: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013320.html - Sanity on r/stx.7.0 w/ stx-openstack - Sanity w/ openstack is green on the Aug 30th RC candidate load: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013335.html - Action: Scott to update the CENGN build artifacts to mark the load as green. - Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - None - Docs - Release Notes Review: https://review.opendev.org/c/starlingx/docs/+/850424 - Already reviewed by multiple team members. - Action: Ghada to ask Juanita to merge it - stx.7.0 Milestones - Sanity/Final Regression Complete: Aug 17 >> Re-forecast: Aug 31 >> Complete: Sept 6 - Sanity Email: - Regression Results: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - Release: Aug 24 >> Re-forecast: Sep 7 >> Re-forecast: Sep 9 - Next Steps towards releasing stx.7.0 - Complete successful sanity on r/stx.7.0 w/ stx-openstack -- COMPLETE - Tag branch w/ final green RC build. Copy RC build to the release directory. Stop daily scheduled builds. - Action: Scott to start the tagging/releasing process asap. Forecast: EOD Sep 7 - Docs release process - Action: Ghada to follow-up with Juanita to complete by EOW Sep 9 - Send announcement to mailing list - Action: Ghada to send an email to the mailing list regarding starting the release process. Final email (milestone declaration) will be sent once all release operations are complete. - Blogs -- No updates in today's meeting - Release Announcement - Prime: Ildiko - In progress. https://github.com/StarlingXWeb/starlingx-website/pull/201/ - Debian OS Migration - Prime: Frank Miller - In progress. https://github.com/StarlingXWeb/starlingx-website/pull/190/commits/ca7f8b155fa2e6f64620a94596d609f028c99e1e - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept / Author: Cole Walker - Subcloud Local Install - Prime: RamS - Forecast: ?? << still need a forecast stx.8.0 - Reference Links: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?usp=sharing - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit?usp=sharing - Open StoryBoards: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.8.0 - Content Follow-Up Actions - Action: Linda to add features planned by the OS team. << email sent on Aug 25 - spreadsheet not updated. Action: Ghada to send another reminder - Action: Rob to look at features planned by the Build team - Note: Rob is filling in as Anthony Nowell is no longer with WR. - Rob is still following up From helena at openstack.org Wed Sep 7 15:44:12 2022 From: helena at openstack.org (Helena Spease) Date: Wed, 7 Sep 2022 10:44:12 -0500 Subject: [Starlingx-discuss] Join the StarlingX Community in Vancouver for the OpenInfra Summit! Message-ID: <774925F6-82B5-45D1-A5FD-B9A4D929F7AE@openstack.org> Hi Everyone, Registration and sponsorships for the OpenInfra Summit Vancouver [1] are now open! This is your chance to collaborate directly with the people building and running StarlingX. Mark your calendars for June 13-15, 2023 and register early [2] to save your seat! Find information on sponsorships[3], the Summit travel support program[4], visa requirements[5], and track chair nominations[6]. Stay tuned for November when the Call for Presentations opens! Cheers, Helena [1] https://openinfra.dev/summit/vancouver-2023 [2] https://openinfrasummit2023.eventbrite.com/ [3] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp [5] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 [6] https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 From scott.little at windriver.com Thu Sep 8 13:43:41 2022 From: scott.little at windriver.com (Scott Little) Date: Thu, 8 Sep 2022 09:43:41 -0400 Subject: [Starlingx-discuss] Releasing stx.7.0 - branch closed for release process In-Reply-To: References: Message-ID: <794bf167-ea07-0d97-3dbf-bceccef14cd8@windriver.com> On 2022-09-07 10:32, Khalil, Ghada wrote: > Scott, > Please proceed with the final steps of the release process: > - Mark the RC candidate release as Green Done > - Tag the branch In progress.? Having some issues with a few repos.? I'm talking to the opendev support team to figure out why my tags are being rejected. > - Move the build artifacts to the release directory Done > - Mark the build as KEEP Done From scott.little at windriver.com Thu Sep 8 19:16:03 2022 From: scott.little at windriver.com (Scott Little) Date: Thu, 8 Sep 2022 15:16:03 -0400 Subject: [Starlingx-discuss] Releasing stx.7.0 - branch closed for release process In-Reply-To: <794bf167-ea07-0d97-3dbf-bceccef14cd8@windriver.com> References: <794bf167-ea07-0d97-3dbf-bceccef14cd8@windriver.com> Message-ID: <628f4db8-fc73-0198-c7b7-e0122fd1005d@windriver.com> Tagging is complete Scott On 2022-09-08 09:43, Scott Little wrote: > On 2022-09-07 10:32, Khalil, Ghada wrote: >> Scott, >> Please proceed with the final steps of the release process: >> - Mark the RC candidate release as Green > Done >> - Tag the branch > > In progress.? Having some issues with a few repos.? I'm talking to the > opendev support team to figure out why my tags are being rejected. > >> - Move the build artifacts to the release directory > Done >> - Mark the build as KEEP > Done > > From Greg.Waines at windriver.com Fri Sep 9 18:42:55 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 9 Sep 2022 18:42:55 +0000 Subject: [Starlingx-discuss] What is the base OS for Starlingx Release 6 In-Reply-To: References: <90148E8E-ED79-4D6A-8491-C14C14D18BE7@gmail.com> Message-ID: hey Danishka, sorry for the slow reply on this. It sounds like you are trying to build on-target ?. directly on starlingx hosts. We actually don?t support that, so we don?t package the build toolchain on the hosts. Only option I can think of is functionality that we added in STX.7.0 to do such a build in a container. A new container image was provided (with dev tools) for the purposes of building, deploying and running non-open-source tools that need to be built by end user. See ?Build, deploy and run non-open-source tools? on https://docs.starlingx.io/usertasks/kubernetes/vran-tools-2c3ee49f4b0b.html for details. Greg. From: open infra Sent: Saturday, September 3, 2022 1:05 PM To: Ildiko Vancsa Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What is the base OS for Starlingx Release 6 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ildiko, Sorry for the late reply. I was strugling to install dependencies (gcc) for Nvidia GPU drivers on STX 6 worker nodes. Finally created a local repo and inststalled dependencies using 'Developer Toolset 8' [1]. It would be great if correct gcc version available for stx 7 worker nodes. My original question is about, why CentOS 7 is use as the baseos for nodes. But later I noticed still CentOS7 get maintainer updates [2] [1] https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/8/html/8.0_release_notes/dts8.0_release [2] https://wiki.centos.org/About/Product Regards Danishka On Fri, Aug 12, 2022 at 3:09 AM Ildiko Vancsa > wrote: Hi Danishka, Thank you for reaching out with the issues you?re experiencing. Can you share a bit more information about the failures that you?re seeing? Best Regards, Ildik? > On Aug 1, 2022, at 06:17, open infra > wrote: > > I am suppose to install nvidia driver on a worker (stx 6) which require few dependencies including gcc and make. > When I use CentOS 7 nvidia driver compilation/installation fails and with Rocky linux 9 gcc installation fails. > > > On Thu, Jul 28, 2022 at 4:01 PM open infra > wrote: > Hi, > > Which CentOS release is the compatible with STX release boot image? > > Regards, > Danishka > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Fri Sep 9 19:38:08 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 9 Sep 2022 19:38:08 +0000 Subject: [Starlingx-discuss] Releasing stx.7.0 - branch closed for release process In-Reply-To: References: Message-ID: Hi All, StarlingX Release 7.0 docs have been published. You can find the docs at https://docs.starlingx.io/. Thank you, Regards, Juanita -----Original Message----- From: Khalil, Ghada Sent: September 7, 2022 10:33 AM To: starlingx-discuss at lists.starlingx.io; Little, Scott ; Balaraj, Juanita Subject: Releasing stx.7.0 - branch closed for release process Hello all, We finally have a green sanity w/ openstack for r/stx.7.0 release branch. Sanity Emails: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013320.html https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013335.html Final regression was also complete. Regression Link: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 Scott, Please proceed with the final steps of the release process: - Mark the RC candidate release as Green - Tag the branch - Move the build artifacts to the release directory - Mark the build as KEEP Juanita, We will declare stx.7.0 as released at the end of the week. Please ensure any steps required for the documentation is complete by then. All, Please consider the r/stx.7.0 branch closed for software changes and do not merge any further content for the time being. Thanks to all community members who contributed to this release. Regards, Ghada From Juanita.Balaraj at windriver.com Fri Sep 9 21:13:32 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 9 Sep 2022 21:13:32 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 07-09-22 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, Juanita Balaraj ============ 07-Sept-22 StarlingX 7.0 Release: - Stx 7.0 GA date is now September 7th - AR Juanita to review Stx 7.0 Release checklist - DONE docs are published. - Need to update the Installation Guide to display Stx 7.0 once docs are merged : - DONE - https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - https://review.opendev.org/c/starlingx/docs/+/855079 - DONE - Prep Sphinx for r7: https://review.opendev.org/c/starlingx/docs/+/850411 - Juanita to merge on Sept 7th - DONE Gerrit Reviews: - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Juanita to merge on Sept 7th - DONE - Stx Release Notes - https://review.opendev.org/c/starlingx/docs/+/850424 - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Pending Updates. This will be done in the next Release. - Scott to cut the Stx 7.0 docs branch - Stx 7.0 Docs branch cut on September 7th - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open ; 6 Cherry picks this week to Stx 6.0. and the new Stx 7.0 branch Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed (https://review.opendev.org/c/starlingx/docs/+/822030) StarlingX PTG: https://etherpad.opendev.org/p/stx-ptg-planning-october-2022 Elections: Nov 15-22 [1] https://docs.starlingx.io/election/#election-officials [2] https://docs.starlingx.io/governance/reference/tsc/index.html _______________________________________________ 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 Ghada.Khalil at windriver.com Fri Sep 9 23:58:06 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 9 Sep 2022 23:58:06 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 7 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call September 7, 2022 ** Today's meeting is at 7pm PDT/ 10pm EDT / +1 10am CST ** Good participation from Asia participants Standing topics - Build - Main Branch CentOS Builds - Latest builds are green - Had one container build failure which has been addressed. LP: https://bugs.launchpad.net/starlingx/+bug/1988854 - Main Branch Debian Builds - Builds are green/successful for the last 6 days. - Sanity - Main Branch Sanity w/o stx-openstack - Restarting weekly execution next week. To be executed every Tuesday. - Main Branch Sanity w/ stx-openstack - Also restarting weekly execution next week. Target weekday is TBD. - Team is also working on automating sanity emails to the mailing list - stx.7.0 sanity - Sanity is green w/ openstack as of Sept 6 - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013320.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013335.html - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes - https://review.opendev.org/c/starlingx/docs/+/850424 -- Merged - FEC Operator Configurability - https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179 - zuul issues are resolved thru suggestions on the mailing list. - Team is now debugging issue w/ CentOS build-iso failing; solution has been identified. - Next step is to refresh the review. Targeting merge by EOW. - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Status - Sanity is green w/ openstack - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013320.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013335.html - Final regression complete - https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - Release process has started as per email to the mailing list - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013343.html - Release Milestones ( https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 ) - Sanity/Final Regression Complete: Aug 17 >> Re-forecast: Aug 31 >> Re-forecast: Sep 2 >> Complete: Sept 6 - Release: Aug 24 >> Re-forecast: Sep 7 >> Re-forecast: Sep 9 - Blogs - Plan is to have the press release blog out on Tuesday Sep 13 - Pull Request is already posted: https://github.com/StarlingXWeb/starlingx-website/pull/201/ - It will be merged once the release is announced - Debian blog is also ready to go, but will be released a month or so later - Two other blogs are also planned: PTP Enhancements & Subcloud Local Installs - These will be published at later dates - Build Artifacts - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/ - Board of Directors Meeting - Meeting held earlier today on Sept 7 9am Eastern - Etherpad: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync - Main themes discussed are around growing the user and contributor community - Next follow-up meeting will be held in two months. Ildiko will send the meeting info to the mailing list once scheduled. ARs from Previous Meetings - None Open Requests for Help - Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html - Still no response on the thread, the person followed-up with mentioning issues of nvidia driver install - Action: Greg ... still pending - Wireguard issue - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 - Next step: The OS team to provide a forecast to enable this on the main branch. Linda Wang took the action in the bi-weekly OS meeting. - Rebuilding ISOs - Raised on the call by Scott Kamp - Scott and team are struggling to rebuild the starlingx source to prototype code changes. The documented process does not seem to be clear. - Suggestion is to attend the bi-weekly build meeting to provide feedback and get help. - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. Scott will also look at the latest updates to the build guide as they were updated recently. From Ghada.Khalil at windriver.com Sat Sep 10 00:03:18 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 10 Sep 2022 00:03:18 +0000 Subject: [Starlingx-discuss] stx.7.0 Release milestone declared Message-ID: Hello all, This email announces that the stx.7.0 Release milestone has been achieved as of September 9, 2022. StarlingX release 7.0 is officially delivered. The ISO/build artifacts are available on CENGN at: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/ Release documentation is on starlingx.io at: https://docs.starlingx.io/ Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. Congratulations everyone! Regards, Ghada On behalf of the StarlingX Release team From ildiko.vancsa at gmail.com Sat Sep 10 00:40:44 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 9 Sep 2022 17:40:44 -0700 Subject: [Starlingx-discuss] stx.7.0 Release milestone declared In-Reply-To: References: Message-ID: <4B15679B-B7A8-412F-9126-AD613504CFD3@gmail.com> Hi Ghada, Thank you for sharing the great news! I would also like to join in saying thank you to everyone who contributed to the 7.0 release for your hard work. Congratulations to the community! Best Regards, Ildik? > On Sep 9, 2022, at 17:03, Khalil, Ghada wrote: > > Hello all, > This email announces that the stx.7.0 Release milestone has been achieved as of September 9, 2022. StarlingX release 7.0 is officially delivered. > > The ISO/build artifacts are available on CENGN at: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/ > Release documentation is on starlingx.io at: https://docs.starlingx.io/ > > Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. > Congratulations everyone! > > Regards, > Ghada > On behalf of the StarlingX Release team > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From outbackdingo at gmail.com Sat Sep 10 01:01:06 2022 From: outbackdingo at gmail.com (Outback Dingo) Date: Sat, 10 Sep 2022 08:01:06 +0700 Subject: [Starlingx-discuss] stx.7.0 Release milestone declared In-Reply-To: <4B15679B-B7A8-412F-9126-AD613504CFD3@gmail.com> References: <4B15679B-B7A8-412F-9126-AD613504CFD3@gmail.com> Message-ID: And here we go.... Has anyone tested this process at all ?? download new images fropm http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/centos/flock/outputs/iso/ Fresh StarlingX 6.0 AIO bare metal in production 3 months, Try to upgrade to 7.0, fails multiple times [sysadmin at controller-0 ~(keystone_admin)]$ system load-import /home/sysadmin/bootimage.iso /home/sysadmin/bootimage.sig This operation will take a while. Please wait. ............... Load import failed. Reason: ('Connection aborted.', BadStatusLine("''",)) 3 attempts failed...! On Sat, Sep 10, 2022 at 7:48 AM Ildiko Vancsa wrote: > > Hi Ghada, > > Thank you for sharing the great news! > > I would also like to join in saying thank you to everyone who contributed to the 7.0 release for your hard work. Congratulations to the community! > > Best Regards, > Ildik? > > > > On Sep 9, 2022, at 17:03, Khalil, Ghada wrote: > > > > Hello all, > > This email announces that the stx.7.0 Release milestone has been achieved as of September 9, 2022. StarlingX release 7.0 is officially delivered. > > > > The ISO/build artifacts are available on CENGN at: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/ > > Release documentation is on starlingx.io at: https://docs.starlingx.io/ > > > > Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. > > Congratulations everyone! > > > > Regards, > > Ghada > > On behalf of the StarlingX Release team > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From starlingx.build at gmail.com Sat Sep 10 08:12:16 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Sep 2022 04:12:16 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1549 - Failure! Message-ID: <2103434208.42.1662797542022.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1549 Status: Failure Timestamp: 20220910T044634Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220910T043002Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220910T043002Z DOCKER_BUILD_ID: jenkins-master-20220910T043002Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220910T043002Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220910T043002Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Sat Sep 10 08:12:25 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Sep 2022 04:12:25 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1406 - Failure! Message-ID: <1730944195.45.1662797546131.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1406 Status: Failure Timestamp: 20220910T043002Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220910T043002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From helena at openstack.org Mon Sep 12 18:16:25 2022 From: helena at openstack.org (Helena Spease) Date: Mon, 12 Sep 2022 13:16:25 -0500 Subject: [Starlingx-discuss] OpenInfra Summit Vancouver 2023 Track Chair Nominations Now Open Message-ID: <140CB68C-80C8-4E61-B50A-B8B14009C428@openstack.org> Hey everyone! Track Chair nominations > for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are now open! Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2023 Summit Tracks: 5G/NFV & Edge AI/Machine Learning/HPC CI/CD Container Infrastructure Getting Started Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Hands On Workshops Full track descriptions are available here >. If you?re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form >. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration > and sponsorship > information are already available. Please email speakersupport at openinfra.dev with any questions or feedback. Cheers, Helena Spease -------------- next part -------------- An HTML attachment was scrubbed... URL: From helena at openstack.org Mon Sep 12 18:17:25 2022 From: helena at openstack.org (Helena Spease) Date: Mon, 12 Sep 2022 13:17:25 -0500 Subject: [Starlingx-discuss] OpenInfra Summit Vancouver 2023 Track Chair Nominations Now Open Message-ID: <38D7B78B-3E37-40FE-9501-AC5B3CAFBFBB@openstack.org> Hey everyone! Track Chair nominations > for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are now open! Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2023 Summit Tracks: 5G/NFV & Edge AI/Machine Learning/HPC CI/CD Container Infrastructure Getting Started Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Hands On Workshops Full track descriptions are available here >. If you?re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form >. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration > and sponsorship > information are already available. Please email speakersupport at openinfra.dev with any questions or feedback. Cheers, Helena Spease -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Mon Sep 12 18:54:04 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Mon, 12 Sep 2022 18:54:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO [20220910T024906Z] Message-ID: Sanity Test from 2022-September 12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220910T024906Z/outputs/iso/bootimage.iso) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220910T024906Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment AIO - SX Setup 1 TCs [PASS] Sanity Platform 08 TCs [PASS] Daily Regression Platform 09 TCs [PASS] TOTAL: [ 18 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry[active] PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod[2_0-fill_fill-static-best-effort-HT-AIO] PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] AIO-DX installation failed by an internal lab configuration issue. Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gabriel.CalixtodePaula at windriver.com Wed Sep 14 17:51:55 2022 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Wed, 14 Sep 2022 17:51:55 +0000 Subject: [Starlingx-discuss] StarlingX + STX-Openstack MASTER build sanity results - Sep-14 Message-ID: Hi all, Here's the results for StarlingX + STX-openstack using the latest master branch build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/bootimage.iso and latest Helm-Charts: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/helm-charts/ Sanity Results using a lab-deployment AIO-DX baremetal with VSWITCH_TYPE=ovs-dpdk : Overall Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 14 (93.33%) Failed: 1 (6.67%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20220914 16:03:21 test_ssh_to_hosts PASS 20220914 16:04:10 test_openstack_services_healthy PASS 20220914 16:04:43 test_reapply_stx_openstack_no_change[controller-0] PASS 20220914 16:07:41 test_reapply_stx_openstack_no_change[controller-1] PASS 20220914 16:13:03 test_lock_unlock_host PASS 20220914 16:28:59 test_horizon_create_delete_instance PASS 20220914 16:31:12 test_swact_controllers PASS 20220914 16:37:06 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20220914 16:41:04 test_migrate_vm[tis-centos-guest-live-None] PASS 20220914 16:44:09 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20220914 16:46:51 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20220914 16:49:37 test_evacuate_vms PASS 20220914 17:33:47 test_system_coredumps_and_crashes[core_dumps] PASS 20220914 17:33:58 test_system_coredumps_and_crashes[crash_reports] PASS 20220914 17:34:04 test_system_alarms ----------------------------------------------------------------------- Sanity Results using a lab-deployment AIO-DX baremetal with VSWITCH_TYPE=ovs : Overall Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 13 (86.67%) Failed: 2 (13.33%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20220914 14:05:50 test_ssh_to_hosts FAIL 20220914 14:06:38 test_lock_unlock_host[controller] PASS 20220914 14:31:29 test_swact_controllers PASS 20220914 14:38:05 test_openstack_services_healthy PASS 20220914 14:38:35 test_reapply_stx_openstack_no_change[controller-0] PASS 20220914 14:43:19 test_reapply_stx_openstack_no_change[controller-1] PASS 20220914 14:49:31 test_horizon_create_delete_instance PASS 20220914 14:51:35 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20220914 14:55:27 test_migrate_vm[tis-centos-guest-live-None] PASS 20220914 14:58:26 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20220914 15:01:13 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20220914 15:04:05 test_evacuate_vms PASS 20220914 15:30:53 test_system_coredumps_and_crashes[core_dumps] PASS 20220914 15:31:05 test_system_coredumps_and_crashes[crash_reports] PASS 20220914 15:31:11 test_system_alarms ----------------------------------------------------------------------- The failed tests are related to the low-priority launchpad: STX-Openstack | Hypervisor slow to go back up Best regards Gabriel ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Sep 14 20:18:16 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 14 Sep 2022 20:18:16 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 14-09-22 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, Juanita Balaraj ============ 14-Sept-22 StarlingX 8.0 Release: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - AR Juanita to create Stories for Stx 8.0 https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - To fix the link for Stx 8.0 (Master) Gerrit Reviews: - Version drop-down on https://docs.starlingx.io/ - AR Ron to add the "Latest" category. Currently a workaround has been done to only display Stx 7.0 / Stx 6.0 - Stx Release Notes - https://review.opendev.org/c/starlingx/docs/+/850424 - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Pending Updates. This will be done in the next Release. - Scott to cut the Stx 7.0 docs branch - Stx 7.0 Docs branch cut on September 7th - DONE - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open ; 2 Cherry picks this week to Stx 6.0. and the new Stx 7.0 branch Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed (https://review.opendev.org/c/starlingx/docs/+/822030) - StarlingX PTG: https://etherpad.opendev.org/p/stx-ptg-planning-october-2022 - Elections: Nov 15-22 [1] https://docs.starlingx.io/election/#election-officials [2] https://docs.starlingx.io/governance/reference/tsc/index.html _______________________________________________ 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 Ghada.Khalil at windriver.com Thu Sep 15 20:55:26 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 15 Sep 2022 20:55:26 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 14 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call September 14, 2022 Standing topics - Build - Main Branch CentOS Builds - Builds have been green all week - Main Branch Debian Builds - Builds have been green 6/7 days last week. One intermittent issue seen, but the follow-up build passed. - When will CentOS builds stop? - Criteria for discussion - Container builds all transitioned to build as part of Debian - This can be a soft target given most container images are statically tagged, so previously built containers can continue to be used if a rebuild is not required. - However, once a rebuild is required, the team responsible would have to transition the container build to be part of Debian builds - Support for most/all deployment configs in Debian - AIO-SX, AIO-DX, Standard, Storage, DC - Regular sanity running on Debian builds - stx-openstack - Currently only built and supported in CentOS - Will need a decision on whether transitioning stx-openstack to Debian is a gating item for stopping the CentOS builds - Sanity - CentOS Main Branch Sanity w/o stx-openstack - AIO-SX sanity was green. https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013359.html - AIO-DX sanity was not run due to a config/env issue - CentOS Main Branch Sanity w/ stx-openstack - Sanity was run last week and was yellow (same as stx.7.0) >> Action to ensure reports are sent to the emailing list - Sanity pipeline hit some issues this week which are under investigation - Debian Main Branch Sanity - Action: Rob to look at plan to start these executions - Need to consider an overlap period with both CentOS & Debian sanities running to ensure Debian is stable before discontinuing CentOS sanity. - Team is also working on automating sanity emails to the mailing list - Was discussed within the stx test team and there are some challenges with implementation. - For now, the team will send the reports manually and follow the required "subject" format for tagging builds as green in CENGN - Gerrit Reviews in Need of Attention - FEC Operator Configurability - https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179 >> Merged - Follow-up reviews are now promptly reviewed and merging - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Status - Release milestone has been declared as of Sept 9. - Email Announcement: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013352.html - Blogs - Release Blog was merged / released on Tuesday Sep 13 as per plan - Pull Request: https://github.com/StarlingXWeb/starlingx-website/pull/201/ - Email follow-up regarding live updates/upgrades support - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html - Upgrades are not officially supported as per https://docs.starlingx.io/introduction/consuming.html - Need to clarify this in the Updates/Upgrades section as well: - Action: Greg/Steve to respond to the thread and open follow-up doc LPs to clarify the documentation ARs from Previous Meetings - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html - Still open Open Requests for Help - Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html - Closed. Greg responded: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013348.html - Wireguard issue - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 - Based on OS team meeting on Sept 14 (https://etherpad.opendev.org/p/stx-distro-other ), testing is successful. Team plans to submit patch to the stx main branch. - Rebuilding ISOs - No update this week - Last Status: - Raised on the call by Scott Kamp - Scott and team are struggling to rebuild the starlingx source to prototype code changes. The documented process does not seem to be clear. - Suggestion is to attend the bi-weekly build meeting to provide feedback and get help. - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. << still open - Scott will also look at the latest updates to the build guide as they were updated recently. From Linda.Wang at windriver.com Tue Sep 13 15:55:42 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Tue, 13 Sep 2022 15:55:42 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting Minutes: Sept 6, 2022 Message-ID: September 6, 2022 Attendees: Mark A, Elisamara Goncalves , Scoot Little, Davlet Panech, Rafael Pereira, Rob Cooke, Cristian Mondo, Frank Miller, Linda Wang 1. StartlingX 8.0 1. Any changes/requirements that we need to be aware of? * progression of the organization of the build * update kernel release to update latest stable release. * PTG meeting: https://openinfra.dev/ptg/ Oct 17-21 2. Content sharing changes in Build system * Still under discussion, and review 3. Transition to deprecated CentOS for StartlingX 8.0 * 2022-23 will need to stop building CentOS in CNGN build systems * need to get all containers transition and built/tested * if need to keep pkgs around for those containers that still need to be transition, keep the CentOS pkgs list small to only those needed for the transitional containers * AI: Davlet: write up a spec to reduce the CentOS pgks to StartlingX, on PTG meeting agenda. 4. General Topics * User concerned of Wireguard to be included in Kernel Config * https://bugs.launchpad.net/starlingx/+bug/1984125 * Enabled in Master first, then to other branches * Scott ? will help test, and validate make sure it works. * How to provoke a mirroring of a package to build a package on Debian world, in need of a new package. * need to put in infrastructure for unknown package build. * Will become an issue when introducing Debian build only. * For now, AI: need document and suggested workflow. * Split Images * product vs project split the images. * deliver the code into a single repo. to get a git repo list. Next Meeting: Sept 14th. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Fri Sep 16 16:07:12 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Fri, 16 Sep 2022 16:07:12 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting Minutes: Sept 14, 2022 [No Quorum] Message-ID: September 14, 2022 Attendees: Davlet P, Linda, Charles S, Steve G., [ No quorum] 1. StarlingX 8.0 1. Any. changes/requirements that we need to be aware of? 1. General topics 1. 1. Wireguard 1. * kernel config enablement 1. status: Jiping has done kernel build and boot test on CentOS, is going to submit patch. 2. Will working on Debian II. ??Split Images 1. 1. product vs project split the images. 1. * deliver the code into a single repo. to get a git repo list. 1. 2. Content sharing changes in Build system Next Meeting: September 28, 2022 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Sep 19 15:16:39 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 19 Sep 2022 15:16:39 +0000 Subject: [Starlingx-discuss] StarlingX TSC & Community Call Message-ID: I will not be able to attend the TSC/Community meeting this week due to other commitments. I'd suggest we skip the TSC portion and just have the Community call. Greg. -----Original Appointment----- From: Zvonar, Bill Sent: Wednesday, October 7, 2020 10:57 AM To: Zvonar, Bill; starlingx-discuss at lists.starlingx.io Cc: Wensley, Barton; Jones, Bruce E Subject: [Starlingx-discuss] [Starlingx-discuss] StarlingX TSC & Community Call When: Wednesday, September 21, 2022 10:00 AM-11:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Douglas.Pereira at windriver.com Mon Sep 19 19:47:25 2022 From: Douglas.Pereira at windriver.com (Pereira, Douglas) Date: Mon, 19 Sep 2022 19:47:25 +0000 Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository Message-ID: StarlingX Cores: To help offload some of the current Core's time for code reviews I am proposing to add Thales Elero Cervi as a Core to starlingx/openstack-armada-app repository as this is an important repository for the stx-openstack team. Thales has made multiple code reviews on that repo recently and will be a great addition to the community. Thanks. Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Sep 20 00:24:04 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 19 Sep 2022 20:24:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3182 - Failure! Message-ID: <922532007.53.1663633447655.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3182 Status: Failure Timestamp: 20220919T231255Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220919T230217Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20220919T230217Z DOCKER_BUILD_ID: jenkins-master-distro-20220919T230217Z-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/20220919T230217Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20220919T230217Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From starlingx.build at gmail.com Tue Sep 20 00:24:10 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 19 Sep 2022 20:24:10 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 981 - Failure! Message-ID: <1983285376.56.1663633450898.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 981 Status: Failure Timestamp: 20220919T230217Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220919T230217Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Greg.Waines at windriver.com Tue Sep 20 11:06:35 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 20 Sep 2022 11:06:35 +0000 Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository In-Reply-To: References: Message-ID: +1 From: Pereira, Douglas Sent: Monday, September 19, 2022 3:47 PM To: StarlingX ML Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository StarlingX Cores: To help offload some of the current Core's time for code reviews I am proposing to add Thales Elero Cervi as a Core to starlingx/openstack-armada-app repository as this is an important repository for the stx-openstack team. Thales has made multiple code reviews on that repo recently and will be a great addition to the community. Thanks. Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Tue Sep 20 13:29:27 2022 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 20 Sep 2022 13:29:27 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 981 - Failure! In-Reply-To: <1983285376.56.1663633450898.JavaMail.javamailuser@localhost> References: <1983285376.56.1663633450898.JavaMail.javamailuser@localhost> Message-ID: Launchpad: https://bugs.launchpad.net/starlingx/+bug/1990282 Bug #1990282 ?kmod-bnxt_en: build fails on CentOS? : Bugs : StarlingX Brief Description ----------------- The package kmod-bnxt_en fails to build on CentOS. Probable cause: latest kernel package recently moved signing keys from -devel to -devel-keys sub-package and this kernel module is missing a BuildDepends. 1) Earlier succesful build: $ ( cd /localdisk/loadbuild/jenkins/master-distro/20220914T014244Z/std/results/jenkins-master-distro-4.0-std/kernel-5.10.112-200.54.tis.el7 && ls -1 kernel-devel-* ; ) kernel-devel-5.10.112-200.54.tis.el7.x86_64.rpm 2) Curre... bugs.launchpad.net ________________________________ From: starlingx.build at gmail.com Sent: September 19, 2022 8:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 981 - Failure! [Please note: This e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_distro_master_master Build #: 981 Status: Failure Timestamp: 20220919T230217Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220919T230217Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Tue Sep 20 13:52:25 2022 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 20 Sep 2022 13:52:25 +0000 Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository Message-ID: <8910D8B7-ED01-43AB-B604-7A40D3109996@windriver.com> +2 From: "Waines, Greg" Date: Tuesday, September 20, 2022 at 6:09 AM To: "Pereira, Douglas" , "'starlingx-discuss at lists.starlingx.io'" Subject: Re: [Starlingx-discuss] Request adding Thales as Core to starlingx repository +1 From: Pereira, Douglas Sent: Monday, September 19, 2022 3:47 PM To: StarlingX ML Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository StarlingX Cores: To help offload some of the current Core's time for code reviews I am proposing to add Thales Elero Cervi as a Core to starlingx/openstack-armada-app repository as this is an important repository for the stx-openstack team. Thales has made multiple code reviews on that repo recently and will be a great addition to the community. Thanks. Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Sep 21 11:02:23 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 21 Sep 2022 11:02:23 +0000 Subject: [Starlingx-discuss] stx.7.0 Release milestone declared In-Reply-To: References: <4B15679B-B7A8-412F-9126-AD613504CFD3@gmail.com> Message-ID: ... apologize for the slow reply. StarlingX code and the community "enables" the ability to do Software patches and upgrades. ? Formal StarlingX Release ISOs and container images are built by CENGN o http://mirror.starlingx.cengn.ca/mirror/starlingx/release/ o with container images available on docker hub under starlingx org ? developer instructions are available ( https://docs.starlingx.io/developer_resources/index.html ) for building ISOs and Updates/Patches, ? code supporting Software Update/Patch and Software Upgrade procedures via CLI and GUI have been implemented o https://docs.starlingx.io/updates/index-updates-e3b970bb69ce.html o Wind River?s Commercial Product based on StarlingX uses these to deliver/apply patches and upgrades Currently the StarlingX Community does not build software updates/patches (bug fixes, etc) for its Formal StarlingX Release ISOs on CENGN. Community resource limitations prohibit being able to patch maintenance of the Formal StarlingX Release ISOs. The StarlingX Community also does not support or test software upgrades from one STX Release to the next STX Release, due to the following reasons and community resource limitations: ? Very often for software upgrades to work from STX Release N (old/existing) to STX Release N+1 (new), a ?software-upgrade-enabling? 'update/patch' is required for STX Release N ? e.g. to address migration issues across the upgrade. ? Because the StarlingX Community does not provide/build software updates/patches, this patch is not available from the StarlingX Community, and therefore software upgrades may not necessarily work and are not tested by the StarlingX Community. This is described here in StarlingX docs: https://docs.starlingx.io/introduction/consuming.html . In order to enable software upgrade capabilities, the community needs the resources to: ? to build and test software-upgrade-enabling updates/patches for Formal StarlingX Release ISOs ? release these software-upgrade-enabling updates/patches to CENGN servers ? test software upgrades between Formal StarlingX Release ISOs The StarlingX community welcomes any contributions that help us meet the needs of a growing user community. If there is any contribution or collaboration you can offer, or suggest, to create the ability to offer and support software upgrades, we welcome them. Greg. -----Original Message----- From: Outback Dingo Sent: Friday, September 9, 2022 9:01 PM To: Ildiko Vancsa Cc: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.7.0 Release milestone declared [Please note: This e-mail is from an EXTERNAL e-mail address] And here we go.... Has anyone tested this process at all ?? download new images fropm http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/centos/flock/outputs/iso/ Fresh StarlingX 6.0 AIO bare metal in production 3 months, Try to upgrade to 7.0, fails multiple times [sysadmin at controller-0 ~(keystone_admin)]$ system load-import /home/sysadmin/bootimage.iso /home/sysadmin/bootimage.sig This operation will take a while. Please wait. ............... Load import failed. Reason: ('Connection aborted.', BadStatusLine("''",)) 3 attempts failed...! On Sat, Sep 10, 2022 at 7:48 AM Ildiko Vancsa > wrote: > > Hi Ghada, > > Thank you for sharing the great news! > > I would also like to join in saying thank you to everyone who contributed to the 7.0 release for your hard work. Congratulations to the community! > > Best Regards, > Ildik? > > > > On Sep 9, 2022, at 17:03, Khalil, Ghada > wrote: > > > > Hello all, > > This email announces that the stx.7.0 Release milestone has been achieved as of September 9, 2022. StarlingX release 7.0 is officially delivered. > > > > The ISO/build artifacts are available on CENGN at: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/7.0.0/ > > Release documentation is on starlingx.io at: > > https://docs.starlingx.io/ > > > > Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. > > Congratulations everyone! > > > > Regards, > > Ghada > > On behalf of the StarlingX Release team > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Sep 21 14:59:55 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 21 Sep 2022 14:59:55 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Sep 21/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.7.0 - Release milestone declared as of Sep 9 - Remaining item is to close any open stx.7.0 storyboards. Action: Ghada to check and follow up with PLs stx.8.0 - Reference Links: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?usp=sharing - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit?usp=sharing - Open StoryBoards: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.8.0 - Milestone-1 is scheduled for this week - Milestone-1 Criteria - Release priorities and major features defined << DONE - High level resourcing secured << DONE - Blog Post planning starting << DONE - Agreed to declare the milestone based on the above criteria being met From Gabriel.CalixtodePaula at windriver.com Wed Sep 21 17:04:07 2022 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Wed, 21 Sep 2022 17:04:07 +0000 Subject: [Starlingx-discuss] StarlingX + STX-Openstack MASTER build sanity results - Sep-21 Message-ID: Hi all, Here's the results for StarlingX + STX-openstack using the latest master branch build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/bootimage.iso and latest Helm-Charts: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/helm-charts/ Sanity Results using a lab-deployment AIO-DX baremetal with VSWITCH_TYPE=ovs-dpdk : Overall Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.0%) Failed: 0 (0.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20220921 13:35:36 test_ssh_to_hosts PASS 20220921 13:36:28 test_lock_unlock_host[controller] PASS 20220921 13:51:49 test_swact_controllers PASS 20220921 14:00:19 test_openstack_services_healthy PASS 20220921 14:00:47 test_reapply_stx_openstack_no_change[controller-0] PASS 20220921 14:05:05 test_reapply_stx_openstack_no_change[controller-1] PASS 20220921 14:10:24 test_horizon_create_delete_instance PASS 20220921 14:12:20 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20220921 14:15:59 test_migrate_vm[tis-centos-guest-live-None] PASS 20220921 14:19:05 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20220921 14:21:37 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS 20220921 14:24:11 test_evacuate_vms PASS 20220921 14:50:31 test_system_coredumps_and_crashes[core_dumps] PASS 20220921 14:50:43 test_system_coredumps_and_crashes[crash_reports] PASS 20220921 14:50:49 test_system_alarms ----------------------------------------------------------------------- Sanity Results using a lab-deployment AIO-DX baremetal with VSWITCH_TYPE=ovs : Overall Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 13 (86.67%) Failed: 2 (13.33%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20220921 13:41:01 test_ssh_to_hosts FAIL 20220921 13:41:48 test_lock_unlock_host[controller] PASS 20220921 14:09:37 test_swact_controllers PASS 20220921 14:19:05 test_openstack_services_healthy PASS 20220921 14:19:34 test_reapply_stx_openstack_no_change[controller-0] PASS 20220921 14:24:05 test_reapply_stx_openstack_no_change[controller-1] PASS 20220921 14:30:18 test_horizon_create_delete_instance PASS 20220921 14:32:18 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20220921 14:36:05 test_migrate_vm[tis-centos-guest-live-None] PASS 20220921 14:39:22 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20220921 14:42:16 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20220921 14:44:57 test_evacuate_vms PASS 20220921 15:18:30 test_system_coredumps_and_crashes[core_dumps] PASS 20220921 15:18:41 test_system_coredumps_and_crashes[crash_reports] PASS 20220921 15:18:48 test_system_alarms ----------------------------------------------------------------------- The failed tests are related to the low-priority launchpad: STX-Openstack | Hypervisor slow to go back up Best regards Gabriel ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Sep 21 19:47:30 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 21 Sep 2022 19:47:30 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: Join us if you have interest in StarlingX docs! Call details * 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 Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2684 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Thu Sep 22 02:57:28 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 22 Sep 2022 02:57:28 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 21 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call September 21, 2022 Standing topics - Build - Main Branch CentOS Builds - One failure this week. LP: https://bugs.launchpad.net/starlingx/+bug/1990282 opened and resolved. Builds are back to normal. - Main Branch Debian Builds - Builds are successful. No failures this week. - Sanity - CentOS Main Branch Sanity w/o stx-openstack - Last sanity on Sept 12 is Green. https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013359.html - Was run on AIO-SX only, but not AIO-DX - CentOS Main Branch Sanity w/ stx-openstack - Last sanity on Sept 14 is Yellow. https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013360.html - Debian Main Branch Sanity - Action: Rob to look at plan to start these executions - Need to consider an overlap period with both CentOS & Debian sanities running to ensure Debian is stable before discontinuing CentOS sanity. - Gerrit Reviews in Need of Attention - None brought forward in the meeting - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Upgrade Support - Email follow-up regarding live updates/upgrades support - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html - Response sent by Greg on Sept 21: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013372.html - Will keep on the list until further discussion - stx.8.0 - Milestone-1 is scheduled for this week - Milestone-1 Criteria - Release priorities and major features defined << DONE - High level resourcing secured << DONE - Blog Post planning starting << DONE - Agreed in the release meeting to declare milestone based on the above criteria being met. No concerns raised in the community meeting as well. - ARs from Previous Meetings - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. - Meeting doesn't seem to be active. Last meeting was on July 12. Still open to determine next steps. Open Requests for Help - Wireguard issue - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 - Fixed in the stx main branch as of Sept 19. Any other follow-up required? - Rebuilding ISOs - Raised by Scott Kamp - Still under discussion - Previous Actions: still open - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. - Action: Scott will also look at the latest updates to the build guide as they were updated recently. From Chris.Winnicki at windriver.com Thu Sep 22 18:40:56 2022 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Thu, 22 Sep 2022 18:40:56 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO [20220918T013730Z] Message-ID: Results for: Sanity Master Test LAYERED build ISO [20220918T013730Z] OS="centos" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20220918T013730Z" centos: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/bootimage.iso Overall Status: GREEN Lab: SM_5_6 Node Config: AIO-DX Test Logs: (Internal WRS only) abstract log: test_steps.log, pytestlog.log (Internal WRS only) full log: TIS_AUTOMATION.log (Internal WRS only) http://128.224.186.235/auto_logs/sm_5_6/202209201955 Passed: 9 (100.0%) Failed: 0 (0.0%) Total Executed: 9 List of Test Cases: ------------------------------------------------------ PASS 20220920 19:56:57 test_system_health_pre_session[pods] PASS 20220920 19:57:21 test_system_health_pre_session[alarms] PASS 20220920 19:57:30 test_system_health_pre_session[system_apps] PASS 20220920 19:57:36 test_horizon_host_inventory_display PASS 20220920 19:58:59 test_lock_unlock_host PASS 20220920 20:11:25 test_swact_controller_platform PASS 20220920 20:13:40 test_pod_to_pod_connection PASS 20220920 20:14:49 test_pod_to_service_connection PASS 20220920 20:15:11 test_host_to_service_connection Regression Test Cases: PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[pods] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[alarms] PASS testcases/functional/common/test_system_health.py::test_system_health_pre_session[system_apps] PASS testcases/wrcp/regression/horizon/test_hosts.py::test_horizon_host_inventory_display PASS testcases/wrcp/regression/mtc/test_lock_unlock_host.py::test_lock_unlock_host PASS testcases/wrcp/regression/mtc/test_swact.py::test_swact_controller_platform PASS testcases/wrcp/regression/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_pod_connection PASS testcases/wrcp/regression/networking/test_pod_to_pod.py::TestPodtoPod::test_pod_to_service_connection PASS testcases/wrcp/regression/networking/test_pod_to_pod.py::TestPodtoPod::test_host_to_service_connection (Internal WRS only) Lab: wcp_111 Build ID: Job: Build Server: System Type: AIO-SX OpenStack Deployed: False WRA Version: WRA Build Date: Kubernetes Version: 1.23.1 Ceph Version: 14.2.22 (Internal WRS only) Automation LOGs DIR: /sandbox/AUTOMATION_LOGS/wcp_111/202209201944 Ends at: 20220920 21:10:33 Session Tag: None Session ID: 3b03c39f-5ab1-44a4-a689-cc84fb1f47dc Summary: Passed: 9 (100.0%) Failed: 0 (0.0%) Total Executed: 9 PASS??20220920 19:46:05?testcases/wrcp/regression/containers/test_custom_containers.py::test_push_docker_image_to_local_registry_active PASS??20220920 19:47:00?testcases/wrcp/regression/containers/test_custom_containers.py::test_upload_charts_via_helm_upload PASS??20220920 19:47:22?testcases/wrcp/regression/containers/test_custom_containers.py::test_host_operations_with_custom_kubectl_app PASS??20220920 19:59:56?testcases/wrcp/regression/containers/test_isolcpus.py::TestIsolated_2P::test_isolated_2p_2_big_pod[2_0-fill_fill-static-best-effort-HT-AIO] PASS??20220920 20:34:03?testcases/wrcp/regression/networking/test_sriovdp.py::TestSriovNetdevice::test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS??20220920 20:47:38?testcases/wrcp/regression/networking/test_sriovdp.py::TestSriovNetdevice::test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS??20220920 20:50:35?testcases/wrcp/regression/networking/test_sriovdp.py::TestSriovMixed::test_sriovdp_mixed_add_vf_interface[1] PASS??20220920 21:10:23?testcases/functional/common/test_system_health.py::TestCoreDumpsAndCrashes::test_system_coredumps_and_crashes[core_dumps] PASS??20220920 21:10:30?testcases/functional/common/test_system_health.py::TestCoreDumpsAndCrashes::test_system_coredumps_and_crashes[crash_reports] - Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sat Sep 24 03:50:00 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 24 Sep 2022 03:50:00 +0000 Subject: [Starlingx-discuss] stx.8.0 Milestone-1 Declared Message-ID: Hello all, Based on the stx.8.0 release/feature review during the StarlingX bi-weekly release planning meeting, we are declaring Milestone-1 with a date of Sept 23/2022. Milestone-1 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Release priorities and major features defined. - High level resourcing secured. A list of proposed features is available at: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 Thank you to all community members who helped achieve this milestone. Regards, Ghada - stx releases prime From Thiago.Brito at windriver.com Mon Sep 26 12:14:16 2022 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Mon, 26 Sep 2022 12:14:16 +0000 Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository In-Reply-To: References: Message-ID: +1 ________________________________ From: Waines, Greg Sent: Tuesday, September 20, 2022 8:06 AM To: Pereira, Douglas ; StarlingX ML Subject: Re: [Starlingx-discuss] Request adding Thales as Core to starlingx repository +1 From: Pereira, Douglas Sent: Monday, September 19, 2022 3:47 PM To: StarlingX ML Subject: [Starlingx-discuss] Request adding Thales as Core to starlingx repository StarlingX Cores: To help offload some of the current Core's time for code reviews I am proposing to add Thales Elero Cervi as a Core to starlingx/openstack-armada-app repository as this is an important repository for the stx-openstack team. Thales has made multiple code reviews on that repo recently and will be a great addition to the community. Thanks. Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Sep 26 16:24:52 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 26 Sep 2022 09:24:52 -0700 Subject: [Starlingx-discuss] KubeCon EU CFP open Message-ID: <50D7D69E-CAF4-4D14-99CF-F31178C54047@gmail.com> Hi StarlingX Community, I?m reaching out to you to draw your attention to the KubeCon Europe (Tuesday, 17 April ? Friday, 21 April 2023) event CFP that is already open! Since StarlingX is integrating a couple of projects from the CNCF ecosystem this event is a great opportunity to build connections within that ecosystem. It can also be used to raise awareness of the StarlingX project and start and foster cross-community collaboration activities. __The KubeCon EU CFP closes November 18!__ Please let me know if I can help you with putting together or reviewing your abstarct. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From ildiko.vancsa at gmail.com Wed Sep 28 00:57:15 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 27 Sep 2022 17:57:15 -0700 Subject: [Starlingx-discuss] Upcoming TSC and PL/TL elections - REVIEW NEEDED In-Reply-To: References: <93D2C061-CAFE-48F0-B128-241D66F235C8@gmail.com> Message-ID: <1C48CFE8-BC55-4360-99DD-5EE8205FF0B6@gmail.com> Hi StarlingX Community, As there were no objections to the proposed election timeline for the regular PL/TL and TSC elections, the patch to update the dates on the website is now merged. You can find the election timeline and further information about the process here: https://docs.starlingx.io/election/ As an early preparation step I pulled the contributor information to build an initial list of electorates for the community to review: https://etherpad.opendev.org/p/stx-electorate-fall-2022 __Please check the above list and reply to this thread, or reach out to the election officials[1] directly, if you contributed to the StarlingX project in the past 12 months, but your email address is not in the list in the above etherpad.__ Please reply to this thread or reach out to the officials[1] if you have any further questions or comments. Thanks and Best Regards, [1] https://docs.starlingx.io/election/#election-officials > On Aug 31, 2022, at 10:41, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > A quick update in preparation tot he upcoming TSC and PL/TL elections. > > As there were no objections to the proposed timeline so far I created a patch to update the timeline on the election website: https://review.opendev.org/c/starlingx/election/+/855391 > > Please review the above change and leave any comments if you see any conflicts, typos or have any questions. > > You can also reach out to the election officials[1] if you have any questions regarding the elections. > > A still outstanding item: Similarly to last year we have an empty TSC seat[2] that we could try to fill for a half-term during an interim TSC election once the regular elections ended. The interim elections need separate dates to avoid confusions with the regular process. Would the TSC and community prefer to run the interim elections this time around as well? > > Thanks, > > [1] https://docs.starlingx.io/election/#election-officials > [2] https://docs.starlingx.io/governance/reference/tsc/index.html > > > >> On Aug 17, 2022, at 07:52, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> It is a friendly reminder that the time for the fall election[1] period is coming up fast and therefore we need to start planning the process. >> >> We need to decide on timeframe for the elections. For TSC we have a nomination, a campaign and a voting period, while for PL/TL elections we have a nomination and a voting period defined officially. >> >> We are looking for a 3-week timeframe in the fall that doesn?t collide with any major holidays or milestones in the release process. To avoid major events as well the proposed timeline would be the following: >> >> TSC nomination starts @ November 01, 2022 20:45 UTC >> TSC nomination ends @ November 08, 2022 20:45 UTC >> PL/TL nomination starts @ November 01, 2022 20:45 UTC >> PL/TL nomination ends @ November 08, 2022 20:45 UTC >> >> TSC campaigning starts @ November 08, 2022 20:45 UTC >> TSC campaigning ends @ November 15, 2022 20:45 UTC >> >> TSC election starts @ November 15, 2022 20:45 UTC >> TSC election ends @ November 22, 2022 20:45 UTC >> PL/TL election starts @ November 15, 2022 20:45 UTC >> PL/TL election ends @ November 22, 2022 20:45 UTC >> >> >> Similarly to last year we have an empty TSC seat[2] that we could try to fill for a half-term during an interim TSC election once the regular elections ended. The interim elections need separate dates to avoid confusions with the regular process. Would the TSC and community prefer to runt he interim elections this time around as well? >> >> Please think about your preference about the election process to make sure that people are available to submit nominations as well as to be able to vote in the election process. >> >> If you have any questions or comments please reply to this thread or reach out to the election officials[3]. >> >> Thanks, >> >> [1] https://docs.starlingx.io/election/ >> [2] https://docs.starlingx.io/governance/reference/tsc/index.html >> [3] https://docs.starlingx.io/election/#election-officials >> >> >> > From openinfradn at gmail.com Wed Sep 28 07:31:38 2022 From: openinfradn at gmail.com (open infra) Date: Wed, 28 Sep 2022 13:01:38 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: On Wed, Dec 8, 2021 at 3:16 AM Brito, Thiago wrote: > Did you do an application-apply after you changed the processors to > application-isolated? Can you send the output of the command below for you > compute pods: > > kubectl exec -n openstack nova-compute-[woker|controller]-X-XXXXX-xxxx -- > cat /etc/nova/nova.conf|grep dedicated_set > > Is there way I can enable application-isolation across all the worker nodes including new nodes to be added in future? Don't forget to change the id of the pod for your compute pods. > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Tuesday, December 7, 2021 5:45 AM > *To:* Brito, Thiago > *Cc:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* Re: [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Here is the info from STX side > > > Processors 2 Physical Cores Per Processor 32 Hyper-Threading Yes > CPU Assignments > Create Cpu Profile > > Function > Processor Logical Cores > Platform *Processor 0 : *0,64 > vSwitch > Shared > Application *Processor 0 : *17-31,81-95 > *Processor 1 : *56-63,120-127 > Application-isolated *Processor 0 : *1-16,65-80 > *Processor 1 : *32-55,96-119 > > On Tue, Dec 7, 2021 at 1:46 PM open infra wrote: > > Hi Thiago, > > I have configured the worker as mentioned in the given link and dedicated > cpu_policy set in the flavor. > Instance creation failed with the following error. > > No valid host was found. There are not enough hosts available. > > > controller-0:~$ openstack flavor show dn.large -c properties > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | Field | Value > | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', > hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > > Regards, > > Danishka > > On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: > > Hi Danishka, > > Whatever you configure on the platform as Application-isolated core for a > node will get to cpu_dedicated_set on stx-openstack. Please check this doc: > https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Monday, December 6, 2021 3:15 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi, > > Is the cpu_dedicated_set is already enabled in stx based openstack? > How to verify and enable it? > > Regards, > Danishka > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Wed Sep 28 14:55:39 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Wed, 28 Sep 2022 14:55:39 +0000 Subject: [Starlingx-discuss] StarlingX Build Meeting Message-ID: Hi everyone, As per the discussion in the Community call this week, with Anthony's departure (build TL/PL) I wanted to send a reminder that there is a bi-weekly build call that is held on Tuesday's at 7:30am Pacific Time. The next meeting would fall on October 4th. The link to the meeting can be found on the StarlingX/Meetings page, https://wiki.openstack.org/wiki/Starlingx/Meetings but I've also included it here for convenience, https://meet.jit.si/starlingx-build. As we did with the community call, if there is a desire for an Asia friendly meeting time please let us know and we can evaluate if we can make something work. Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gabriel.CalixtodePaula at windriver.com Wed Sep 28 17:44:03 2022 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Wed, 28 Sep 2022 17:44:03 +0000 Subject: [Starlingx-discuss] StarlingX + STX-Openstack MASTER build ISO [20220926T230700Z] sanity results - Sep-28 Message-ID: Hi all, Here's the results for StarlingX + STX-openstack using the latest master branch build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/bootimage.iso and latest Helm-Charts: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/helm-charts/ BUILD_ID: 20220926T230700Z Overall Status: RED A BUG was found during the execution of sanity that caused RED results on both DX labs, a Launchpad was created for the issue: ?Bug #1991115 - STX-Openstack | Failing to application-upload - sysinv Regards Gabriel -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Sep 29 00:25:39 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 28 Sep 2022 17:25:39 -0700 Subject: [Starlingx-discuss] [PL][TL] Updating the projects.yaml file Message-ID: Hi StarlingX Community, I?m reaching out to you in connection to the upcoming PL/TL/TSC elections. One of the preparation steps of the election process is to identify the project contributors who are eligible to participate in the process. To collect the majority of the information the election officials use a script that pulls information from the project?s git repositories and directly from the ?projects.yaml?[1] file in the governance repository. The list of git repositories that belong to each StarlingX sub-project is also extracted from the ?projects.yaml' file. To ensure that we have an accurate list of electorate for the upcoming elections, I would like to ask the PLs to please look into the aforementioned file and make sure that both the list of repositories as well as the list of ?extra-atcs? are up to date! ?extra-atcs?: Only list the people who are participating in a sub-project but did NOT have merged commits in any of the project?s repositories in the past 12 months. With regards to the list of ?extra-atcs?, there is an 'expires-in? field that also needs to be updated. For people who are still active in the community, it is a great time to update that field and extend it with one year. ALL PROJECT LEADS: please update the information for your projects in the projects.yaml file, if needed, __by Wednesday (October 12)__. Please let me know if you have any questions. Thanks and Best Regards, Ildik? [1] https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml From ildiko.vancsa at gmail.com Thu Sep 29 00:28:48 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 28 Sep 2022 17:28:48 -0700 Subject: [Starlingx-discuss] Next week's TSC & Community Call is in APAC time Message-ID: <9878C314-BB51-4DF3-92A8-C628092308B9@gmail.com> Hi StarlingX Community, It is a friendly reminder that next week?s TSC & Community Call will run in the APAC-friendly time slot, which is on Wednesday (October 05) at 7pm US Pacific Time! For further details about the call, including dial-in information, please see the ?Meetings? wiki page: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Thanks and Best Regards, Ildik? From Ghada.Khalil at windriver.com Fri Sep 30 01:01:31 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 30 Sep 2022 01:01:31 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 28, 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call September 28, 2022 Standing topics - Build - Main Branch CentOS Builds - Green builds all week - Main Branch Debian Builds - Green builds all week - Sanity - CentOS Main Branch Sanity w/o stx-openstack - No sanity was run this week due to a lab/env issue - Last sanity on Sept 22 is Green: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013377.html - Was run on both AIO-SX & AIO-DX - CentOS Main Branch Sanity w/ stx-openstack - No sanity was run this week due to software issue. LP: https://bugs.launchpad.net/starlingx/+bug/1991115 - Last sanity on Sept 21 is Yellow: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013374.html - Debian Main Branch Sanity - Not attempted yet - Action: Rob to look at plan to start these executions - Need to consider an overlap period with both CentOS & Debian sanities running to ensure Debian is stable before discontinuing CentOS sanity. - Gerrit Reviews in Need of Attention - None brought forward in the meeting - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Upgrade Support - Email follow-up regarding live updates/upgrades support - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html - Response sent by Greg on Sept 21: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013372.html - Greg also raised a DOC LP to clarify the support in the StarlingX docs. LP: https://bugs.launchpad.net/starlingx/+bug/1990142 - No response to Greg's email. Consider closed for now until further discussion. - stx.8.0 - Milestone-1 was declared last week - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013378.html - Planning Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=0 - Next milestone - Milestone-2: Week of October 19; aligned with the PTG - Upcoming Elections - Email from Ildiko: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013381.html - Discussed in the TSC portion of the meeting - PTG - Tuesday-Wednesday October 18-19 - Etherpad: https://etherpad.opendev.org/p/stx-ptg-planning-october-2022 - Discussed in the TSC portion of the meeting - Next TSC/Community meeting is in Asia-friendly timezone ARs from Previous Meetings - Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. - Meeting doesn't seem to be active. Last meeting was on July 12. - Rob will re-share the link to the current meeting on the mailing list and will poll if there is interest for an Asia friendly time. Open Requests for Help - Wireguard issue - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 - Fixed in the stx main branch as of Sept 19. Consider closed. - Rebuilding ISOs - Raised by Scott Kamp - Still under discussion - Previous Actions: still open - Action: Rob to re-share build meeting link as per above. - Action: Scott will also look at the latest updates to the build guide as they were updated recently. - Enabling cpu_dedicated_set - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013382.html - Discussion is active on the mailing list. From amy at demarco.com Fri Sep 30 17:09:16 2022 From: amy at demarco.com (Amy Marrich) Date: Fri, 30 Sep 2022 12:09:16 -0500 Subject: [Starlingx-discuss] [Diversity] Diversity and Inclusion WG meeting reminder Message-ID: The D&I WG will be meeting Monday at 15:00 UTC. ? The meeting will be held on video at https://meetpad.opendev.org/osf-diversity-and-inclusion and the agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Imad.Iqbal at windriver.com Tue Sep 27 20:47:11 2022 From: Imad.Iqbal at windriver.com (Iqbal, Imad) Date: Tue, 27 Sep 2022 20:47:11 +0000 Subject: [Starlingx-discuss] Addition to StarlingX notifications Message-ID: Hi Team, Would you mind adding my email ID in the StarlingX distribution list. I need these notifications for sanity and regression runs. Regards, Imad -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Fri Sep 30 05:50:31 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Fri, 30 Sep 2022 05:50:31 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting Minutes: Sept 28, 2022 Message-ID: September 28, 2022 Attendees: Davlet, Charles, Scott, Mark, Frank, Steve, Linda 1. General Topics * Split Images (if we don't have a complete list of packages, but only a few packages in the repo) * product vs project split the images. * deliver the code into a single repo. to get a git repo list * replicate what CentOS stylist, need a couple user stories to track the different tiers: project, product, release. 2. StaringX * Wireguard configs for both CentOS and Debian have been submitted. * StartlingX 8,0 * Content Sharing Disk space conservation * User specific vs project specific * perhaps Aptly isn't a good fit, and work directly at filesystem level * however, the goal is to have STX buildable by STX or inside of K8s where disk/folder access is not a guarantee (concerns about concurrent access should be tested out) * Suggestion: Repo per host, but serialization will be an issue. * Only writes will be serialized * AI: Scott to help write up a story and will have others in the community to take a look. * Pulp vs Aptly package manager * patch on Pulp still waiting on maintainer to review and merge * Pulp is still better package manager than Aptly in the long run (Aptly has been limping along) * https://github.com/pulp/pulp_deb/pull/295 * for those curious, the DBS using Aptly is https://github.com/molior-dbs * How to provoke a mirroring of a package to build a package on Debian world, in need of a new package. * need to put in infrastructure for unknown package build. * Will become an issue when introducing Debian build only. * For now, AI: need document and suggested workflow. * Pulp has the concept of meta object, so doesn't require download of the package. * Still may have impact to the Debian packages. minor use cases may need this. * AI; Park this topic, 'til New year * Transition to deprecated CentOS for StartlingX 8.0 (Late November, Q4'22) * 2022-23 will need to stop building CentOS in CNGN build systems * need to get all containers transition and built/tested * if need to keep pkgs around for those containers that still need to be transitioned, keep the CentOS pkgs list small to only those needed for the transitional containers * AI: Frank will represent WR to announce/advocate the changes in Community meeting, next PTG meeting. * AI: Will wait for couple weeks to determine if there are any packages, we need to keep 'til containers are fully port over and transitioned. Davlet: write up a spec to reduce the CentOS pgks to StartlingX, on PTG meeting agenda. Next Meeting: October 12, 2022 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Fri Sep 30 17:59:43 2022 From: Robert.Church at windriver.com (Church, Robert) Date: Fri, 30 Sep 2022 17:59:43 +0000 Subject: [Starlingx-discuss] Addition to StarlingX notifications Message-ID: <1FB0883B-3FA0-4575-A37A-BE77C8A5B176@windriver.com> Hi Imad, You can subscribe: https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Bob From: "Iqbal, Imad" Date: Friday, September 30, 2022 at 12:45 PM To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] Addition to StarlingX notifications Hi Team, Would you mind adding my email ID in the StarlingX distribution list. I need these notifications for sanity and regression runs. Regards, Imad -------------- next part -------------- An HTML attachment was scrubbed... URL: From Imad.Iqbal at windriver.com Fri Sep 30 18:02:40 2022 From: Imad.Iqbal at windriver.com (Iqbal, Imad) Date: Fri, 30 Sep 2022 18:02:40 +0000 Subject: [Starlingx-discuss] Addition to StarlingX notifications In-Reply-To: <1FB0883B-3FA0-4575-A37A-BE77C8A5B176@windriver.com> References: <1FB0883B-3FA0-4575-A37A-BE77C8A5B176@windriver.com> Message-ID: Thank you, Bob. Subscribed. Regards, Imad From: Church, Robert Sent: Friday, September 30, 2022 11:00 AM To: Iqbal, Imad ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Addition to StarlingX notifications Hi Imad, You can subscribe: https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Bob From: "Iqbal, Imad" > Date: Friday, September 30, 2022 at 12:45 PM To: "'starlingx-discuss at lists.starlingx.io'" > Subject: [Starlingx-discuss] Addition to StarlingX notifications Hi Team, Would you mind adding my email ID in the StarlingX distribution list. I need these notifications for sanity and regression runs. Regards, Imad -------------- next part -------------- An HTML attachment was scrubbed... URL: