From starlingx.build at gmail.com Thu Dec 1 00:29:41 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 30 Nov 2022 19:29:41 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 638 - Still Failing! In-Reply-To: <700315847.124.1669801542236.JavaMail.javamailuser@localhost> References: <700315847.124.1669801542236.JavaMail.javamailuser@localhost> Message-ID: <1933677365.138.1669854582632.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 638 Status: Still Failing Timestamp: 20221130T202048Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221130T190426Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221130T190426Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221130T190426Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221130T190426Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221130T190426Z/logs PUBLISH_TIMESTAMP: 20221130T190426Z FLOCK_VERSION: master-centos-stable-20221130T190426Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221130T190426Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221130T190426Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Dec 1 00:29:44 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 30 Nov 2022 19:29:44 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 394 - Still Failing! In-Reply-To: <632717888.127.1669801551693.JavaMail.javamailuser@localhost> References: <632717888.127.1669801551693.JavaMail.javamailuser@localhost> Message-ID: <1757432738.141.1669854585684.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 394 Status: Still Failing Timestamp: 20221130T194950Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221130T190426Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221130T190426Z 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/20221130T190426Z/logs MASTER_BUILD_NUMBER: 387 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221130T190426Z/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: 20221130T190426Z DOCKER_BUILD_ID: jenkins-master-containers-20221130T190426Z-builder TIMESTAMP: 20221130T190426Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221130T190426Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221130T190426Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Thu Dec 1 00:29:47 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 30 Nov 2022 19:29:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 387 - Still Failing! In-Reply-To: <1646642633.130.1669801559351.JavaMail.javamailuser@localhost> References: <1646642633.130.1669801559351.JavaMail.javamailuser@localhost> Message-ID: <82156163.144.1669854588500.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 387 Status: Still Failing Timestamp: 20221130T190426Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221130T190426Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Ghada.Khalil at windriver.com Thu Dec 1 00:49:48 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 1 Dec 2022 00:49:48 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Nov 29, 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call November 30, 2022 Standing topics - Build - Main Branch Debian Builds - Green all week - Main Branch CentOS Builds - Green for building ISOs, but having issues building one container image (stx-keystone-api) - LP: https://bugs.launchpad.net/starlingx/+bug/1997977 - Assigned and code review posted - CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities - Forecast: Dec 14 - Debian Build Acceleration/Reuse Feature - The Acceleration feature is now functional for the ISO build, but not yet for container builds. - Work on container build re-use has not started yet. - Sanity - Debian Main Branch Sanity - Last sanity email sent on Nov 29: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013622.html Status: Green - CentOS Main Branch Sanity w/ stx-openstack - Paused as of Nov 17 due to CentOS build issues - Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013582.html - stx-openstack sanity transition to Debian - Planned for the Dec time-frame. Forecast for starting stx-openstack sanity w/ Debian is Dec 7. - Team is focused on trying to get a Debian-based sanity; could be as early as next week - Email to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013487.html - Gerrit Reviews in Need of Attention - Doc Reviews: https://review.opendev.org/q/projects:starlingx+is:open+branch:master+repo:starlingx/docs - Juanita asking for feature primes to review the equivalent doc updates - From last meeting: Doc review for k8s: https://review.opendev.org/c/starlingx/docs/+/862596 << merged - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided; waiting for new patchset from author - 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 - Nothing raised ARs from Previous Meetings - None Open Requests for Help - StarlingX ISO Build - Reported by ScottK - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013610.html - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1998234 - Addressed as of Nov 29 - StarlingX 7.0 & 8.0 deployment failures - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Nov 23: Team working thru setting up new hardware to re-test the deployments. - Virtio-forwarder with StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.html - ScottK responded with additional questions: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013532.html - Waiting for response / no response as of Nov 23 From starlingx.build at gmail.com Thu Dec 1 07:26:15 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Dec 2022 02:26:15 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 639 - Still Failing! In-Reply-To: <509149208.136.1669854579352.JavaMail.javamailuser@localhost> References: <509149208.136.1669854579352.JavaMail.javamailuser@localhost> Message-ID: <1098878082.148.1669879576635.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 639 Status: Still Failing Timestamp: 20221201T032132Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221201T020254Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221201T020254Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221201T020254Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221201T020254Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221201T020254Z/logs PUBLISH_TIMESTAMP: 20221201T020254Z FLOCK_VERSION: master-centos-stable-20221201T020254Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221201T020254Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221201T020254Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Dec 1 07:26:19 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Dec 2022 02:26:19 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 395 - Still Failing! In-Reply-To: <665912843.139.1669854583373.JavaMail.javamailuser@localhost> References: <665912843.139.1669854583373.JavaMail.javamailuser@localhost> Message-ID: <763182.151.1669879580600.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 395 Status: Still Failing Timestamp: 20221201T024956Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221201T020254Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221201T020254Z 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/20221201T020254Z/logs MASTER_BUILD_NUMBER: 388 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221201T020254Z/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: 20221201T020254Z DOCKER_BUILD_ID: jenkins-master-containers-20221201T020254Z-builder TIMESTAMP: 20221201T020254Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221201T020254Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221201T020254Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Thu Dec 1 07:26:25 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 1 Dec 2022 02:26:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 388 - Still Failing! In-Reply-To: <1262914474.142.1669854586371.JavaMail.javamailuser@localhost> References: <1262914474.142.1669854586371.JavaMail.javamailuser@localhost> Message-ID: <1417058607.154.1669879603051.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 388 Status: Still Failing Timestamp: 20221201T020254Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221201T020254Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Fri Dec 2 08:46:25 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 2 Dec 2022 03:46:25 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 640 - Still Failing! In-Reply-To: <657095693.146.1669879573745.JavaMail.javamailuser@localhost> References: <657095693.146.1669879573745.JavaMail.javamailuser@localhost> Message-ID: <1770754846.161.1669970786201.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 640 Status: Still Failing Timestamp: 20221202T043621Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221202T031525Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221202T031525Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221202T031525Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221202T031525Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221202T031525Z/logs PUBLISH_TIMESTAMP: 20221202T031525Z FLOCK_VERSION: master-centos-stable-20221202T031525Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221202T031525Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221202T031525Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Fri Dec 2 08:46:28 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 2 Dec 2022 03:46:28 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 396 - Still Failing! In-Reply-To: <1766728561.149.1669879577649.JavaMail.javamailuser@localhost> References: <1766728561.149.1669879577649.JavaMail.javamailuser@localhost> Message-ID: <1209728922.164.1669970789206.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 396 Status: Still Failing Timestamp: 20221202T040523Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221202T031525Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221202T031525Z 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/20221202T031525Z/logs MASTER_BUILD_NUMBER: 389 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221202T031525Z/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: 20221202T031525Z DOCKER_BUILD_ID: jenkins-master-containers-20221202T031525Z-builder TIMESTAMP: 20221202T031525Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221202T031525Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221202T031525Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Fri Dec 2 08:46:31 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 2 Dec 2022 03:46:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 389 - Still Failing! In-Reply-To: <284378908.152.1669879581546.JavaMail.javamailuser@localhost> References: <284378908.152.1669879581546.JavaMail.javamailuser@localhost> Message-ID: <1698499950.167.1669970792032.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 389 Status: Still Failing Timestamp: 20221202T031525Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221202T031525Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From shavin.wijetunge at xunison.com Sat Dec 3 04:55:23 2022 From: shavin.wijetunge at xunison.com (Shavin Wijetunge) Date: Sat, 3 Dec 2022 04:55:23 +0000 Subject: [Starlingx-discuss] Running starlingx on desktop computers Message-ID: Hi, I am hoping to purchase a desktop computer to run starlingx for internal R&D purposes. I am listing the specs of 5 desktop computers I looked at, below. I need to clarify whether starlingx can be run on these before I purchase. Can starlingx be run on all the below desktop computers? What are the factors I must consider other than number of cores, RAM, and storage, when I purchase hardware ? Any guidance is greatly appreciated? Option 1: CPU: INTEL Core I7 12700 3.6GHz Motherboard: ASUS PRIME 670 Plus (Intel? H670 chipset) RAM: Corsair DDR4 3200 MHz? 16 GBx4 (Total 64 GB RAM) Storage: SSD: KINGSTON SS Drive 1 TB NV2 M2 NVMe 4.0 , HDD: SEAGATE SARA 1TB Option 2: CPU: AMD Ryzen 7 5800X (8 cores) Motherboard: MSI B550M Pro-VDH RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 3: CPU: Intel Core I7 12700K 25MB Cache (12 Cores) Motherboard: Asus Prime B660M A D4 (Intel? B660 chipset) RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 4: CPU: Intel Core I7-11700 (8 cores) Motherboard: AsusTUF B560M-plus D4 (Intel? B560z0 RAM: KINGSTON DDR4 KVR2666 16GBx4 (Total 64 GB) Storage: SSD: Samsung 1TB SSD980 M.2 NVMe , HDD: 1TB Toshiba 7200 rpm Option 5: MSI DP130 I7 CPU: Intel Core I7-11700 (8 cores) Motherboard: MSI with Intel510 Chipset RAM: 2x32 GB DDR4 SDRAM Storage: 1TB M.2 SSD combo (NVMe PCIe Gen3x4) Graphics: MSI Nvidia Ge-Force GT730 2GB Shavin -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sat Dec 3 07:26:25 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 3 Dec 2022 02:26:25 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 641 - Still Failing! In-Reply-To: <345308672.159.1669970783350.JavaMail.javamailuser@localhost> References: <345308672.159.1669970783350.JavaMail.javamailuser@localhost> Message-ID: <343097304.176.1670052386510.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 641 Status: Still Failing Timestamp: 20221203T031700Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221203T015912Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221203T015912Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221203T015912Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221203T015912Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221203T015912Z/logs PUBLISH_TIMESTAMP: 20221203T015912Z FLOCK_VERSION: master-centos-stable-20221203T015912Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221203T015912Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221203T015912Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Sat Dec 3 07:26:28 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 3 Dec 2022 02:26:28 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 397 - Still Failing! In-Reply-To: <300662166.162.1669970787063.JavaMail.javamailuser@localhost> References: <300662166.162.1669970787063.JavaMail.javamailuser@localhost> Message-ID: <994591937.179.1670052389701.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 397 Status: Still Failing Timestamp: 20221203T024655Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221203T015912Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221203T015912Z 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/20221203T015912Z/logs MASTER_BUILD_NUMBER: 390 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221203T015912Z/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: 20221203T015912Z DOCKER_BUILD_ID: jenkins-master-containers-20221203T015912Z-builder TIMESTAMP: 20221203T015912Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221203T015912Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221203T015912Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Sat Dec 3 07:26:31 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 3 Dec 2022 02:26:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 390 - Still Failing! In-Reply-To: <710311598.165.1669970789907.JavaMail.javamailuser@localhost> References: <710311598.165.1669970789907.JavaMail.javamailuser@localhost> Message-ID: <368840680.182.1670052392603.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 390 Status: Still Failing Timestamp: 20221203T015912Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221203T015912Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Mon Dec 5 05:22:11 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Dec 2022 00:22:11 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 643 - Failure! Message-ID: <361105473.199.1670217732776.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 643 Status: Failure Timestamp: 20221205T012435Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221205T000915Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221205T000915Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221205T000915Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221205T000915Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221205T000915Z/logs PUBLISH_TIMESTAMP: 20221205T000915Z FLOCK_VERSION: master-centos-stable-20221205T000915Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221205T000915Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221205T000915Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Mon Dec 5 05:22:15 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Dec 2022 00:22:15 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 399 - Failure! Message-ID: <824440583.202.1670217736079.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 399 Status: Failure Timestamp: 20221205T005442Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221205T000915Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221205T000915Z 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/20221205T000915Z/logs MASTER_BUILD_NUMBER: 391 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221205T000915Z/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: 20221205T000915Z DOCKER_BUILD_ID: jenkins-master-containers-20221205T000915Z-builder TIMESTAMP: 20221205T000915Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221205T000915Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221205T000915Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Mon Dec 5 05:22:18 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 5 Dec 2022 00:22:18 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 391 - Still Failing! In-Reply-To: <1672625824.180.1670052390480.JavaMail.javamailuser@localhost> References: <1672625824.180.1670052390480.JavaMail.javamailuser@localhost> Message-ID: <209313694.205.1670217739112.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 391 Status: Still Failing Timestamp: 20221205T000915Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221205T000915Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Ramaswamy.Subramanian at windriver.com Mon Dec 5 14:46:41 2022 From: Ramaswamy.Subramanian at windriver.com (Subramanian, Ramaswamy) Date: Mon, 5 Dec 2022 14:46:41 +0000 Subject: [Starlingx-discuss] Running starlingx on desktop computers In-Reply-To: References: Message-ID: Hi, Below is an example desktop configuration used for StarlingX development and deployment activities by developers. Intel Xeon Processor W-2295 (18C 3.0GHz 4.6GHz Turbo HT 24.75MB 165W DDR4-2933MHz) 128GB 2x64GB DDR4 2933 RDIM ECC Memory M.2 PCIe NVME Solid State Drive - 4TB --> used for build environment, starlingx deployments, etc. 3.5" 4TB 7200rpm SATA Hard Drive --> Used for storing backups (snapshots, logs, etc). 8 cores and 64GB RAM is not sufficient if you would like to run Distributed Cloud configuration on your desktop. Hope this helps. Regards, Ram From: Shavin Wijetunge Sent: Friday, December 2, 2022 11:55 PM To: starlingx-discuss at lists.starlingx.io Cc: Scott Kamp ; Kajamugan Varatharaja Subject: [Starlingx-discuss] Running starlingx on desktop computers CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, I am hoping to purchase a desktop computer to run starlingx for internal R&D purposes. I am listing the specs of 5 desktop computers I looked at, below. I need to clarify whether starlingx can be run on these before I purchase. Can starlingx be run on all the below desktop computers? What are the factors I must consider other than number of cores, RAM, and storage, when I purchase hardware ? Any guidance is greatly appreciated... Option 1: CPU: INTEL Core I7 12700 3.6GHz Motherboard: ASUS PRIME 670 Plus (Intel(r) H670 chipset) RAM: Corsair DDR4 3200 MHz- 16 GBx4 (Total 64 GB RAM) Storage: SSD: KINGSTON SS Drive 1 TB NV2 M2 NVMe 4.0 , HDD: SEAGATE SARA 1TB Option 2: CPU: AMD Ryzen 7 5800X (8 cores) Motherboard: MSI B550M Pro-VDH RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 3: CPU: Intel Core I7 12700K 25MB Cache (12 Cores) Motherboard: Asus Prime B660M A D4 (Intel(r) B660 chipset) RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 4: CPU: Intel Core I7-11700 (8 cores) Motherboard: AsusTUF B560M-plus D4 (Intel(r) B560z0 RAM: KINGSTON DDR4 KVR2666 16GBx4 (Total 64 GB) Storage: SSD: Samsung 1TB SSD980 M.2 NVMe , HDD: 1TB Toshiba 7200 rpm Option 5: MSI DP130 I7 CPU: Intel Core I7-11700 (8 cores) Motherboard: MSI with Intel510 Chipset RAM: 2x32 GB DDR4 SDRAM Storage: 1TB M.2 SSD combo (NVMe PCIe Gen3x4) Graphics: MSI Nvidia Ge-Force GT730 2GB Shavin -------------- next part -------------- An HTML attachment was scrubbed... URL: From shavin.wijetunge at xunison.com Mon Dec 5 23:54:30 2022 From: shavin.wijetunge at xunison.com (Shavin Wijetunge) Date: Mon, 5 Dec 2022 23:54:30 +0000 Subject: [Starlingx-discuss] Running starlingx on desktop computers In-Reply-To: References: Message-ID: Hi Subramanian, Thanks... Shavin Get Outlook for Android ________________________________ From: Subramanian, Ramaswamy Sent: Monday, December 5, 2022 8:16:41 PM To: Shavin Wijetunge ; starlingx-discuss at lists.starlingx.io Cc: Scott Kamp ; Kajamugan Varatharaja Subject: RE: Running starlingx on desktop computers Hi, Below is an example desktop configuration used for StarlingX development and deployment activities by developers. Intel Xeon Processor W-2295 (18C 3.0GHz 4.6GHz Turbo HT 24.75MB 165W DDR4-2933MHz) 128GB 2x64GB DDR4 2933 RDIM ECC Memory M.2 PCIe NVME Solid State Drive - 4TB --> used for build environment, starlingx deployments, etc. 3.5" 4TB 7200rpm SATA Hard Drive --> Used for storing backups (snapshots, logs, etc). 8 cores and 64GB RAM is not sufficient if you would like to run Distributed Cloud configuration on your desktop. Hope this helps. Regards, Ram From: Shavin Wijetunge Sent: Friday, December 2, 2022 11:55 PM To: starlingx-discuss at lists.starlingx.io Cc: Scott Kamp ; Kajamugan Varatharaja Subject: [Starlingx-discuss] Running starlingx on desktop computers CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, I am hoping to purchase a desktop computer to run starlingx for internal R&D purposes. I am listing the specs of 5 desktop computers I looked at, below. I need to clarify whether starlingx can be run on these before I purchase. Can starlingx be run on all the below desktop computers? What are the factors I must consider other than number of cores, RAM, and storage, when I purchase hardware ? Any guidance is greatly appreciated? Option 1: CPU: INTEL Core I7 12700 3.6GHz Motherboard: ASUS PRIME 670 Plus (Intel? H670 chipset) RAM: Corsair DDR4 3200 MHz? 16 GBx4 (Total 64 GB RAM) Storage: SSD: KINGSTON SS Drive 1 TB NV2 M2 NVMe 4.0 , HDD: SEAGATE SARA 1TB Option 2: CPU: AMD Ryzen 7 5800X (8 cores) Motherboard: MSI B550M Pro-VDH RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 3: CPU: Intel Core I7 12700K 25MB Cache (12 Cores) Motherboard: Asus Prime B660M A D4 (Intel? B660 chipset) RAM: Corsair Vengeance LPX 64GB (16x4) DDR4 3200 MHz C16 Memory Storage: SSD: Adata XPG 1TB M.2 NVMe , HDD: 1TB Seagate Hard Drive Option 4: CPU: Intel Core I7-11700 (8 cores) Motherboard: AsusTUF B560M-plus D4 (Intel? B560z0 RAM: KINGSTON DDR4 KVR2666 16GBx4 (Total 64 GB) Storage: SSD: Samsung 1TB SSD980 M.2 NVMe , HDD: 1TB Toshiba 7200 rpm Option 5: MSI DP130 I7 CPU: Intel Core I7-11700 (8 cores) Motherboard: MSI with Intel510 Chipset RAM: 2x32 GB DDR4 SDRAM Storage: 1TB M.2 SSD combo (NVMe PCIe Gen3x4) Graphics: MSI Nvidia Ge-Force GT730 2GB Shavin -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Dec 6 08:37:02 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 6 Dec 2022 03:37:02 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 644 - Still Failing! In-Reply-To: <1040473516.197.1670217729965.JavaMail.javamailuser@localhost> References: <1040473516.197.1670217729965.JavaMail.javamailuser@localhost> Message-ID: <1226274535.214.1670315823605.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 644 Status: Still Failing Timestamp: 20221206T043607Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221206T031824Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221206T031824Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221206T031824Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221206T031824Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221206T031824Z/logs PUBLISH_TIMESTAMP: 20221206T031824Z FLOCK_VERSION: master-centos-stable-20221206T031824Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221206T031824Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221206T031824Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Tue Dec 6 08:37:06 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 6 Dec 2022 03:37:06 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 400 - Still Failing! In-Reply-To: <1167389120.200.1670217733478.JavaMail.javamailuser@localhost> References: <1167389120.200.1670217733478.JavaMail.javamailuser@localhost> Message-ID: <1390654812.217.1670315827765.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 400 Status: Still Failing Timestamp: 20221206T040444Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221206T031824Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221206T031824Z 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/20221206T031824Z/logs MASTER_BUILD_NUMBER: 392 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221206T031824Z/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: 20221206T031824Z DOCKER_BUILD_ID: jenkins-master-containers-20221206T031824Z-builder TIMESTAMP: 20221206T031824Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221206T031824Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221206T031824Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Tue Dec 6 08:37:50 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 6 Dec 2022 03:37:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 392 - Still Failing! In-Reply-To: <158011075.203.1670217736818.JavaMail.javamailuser@localhost> References: <158011075.203.1670217736818.JavaMail.javamailuser@localhost> Message-ID: <1524239369.220.1670315873704.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 392 Status: Still Failing Timestamp: 20221206T031824Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221206T031824Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ildiko at openinfra.dev Tue Dec 6 19:06:42 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 6 Dec 2022 11:06:42 -0800 Subject: [Starlingx-discuss] This week's TSC & Community Call is in APAC time Message-ID: <2C3070C8-60A9-41BE-8216-8A0ABB1872D4@openinfra.dev> Hi StarlingX Community, It is a friendly reminder that tomorrow?s (December 07) TSC & Community Call will run in the APAC-friendly time slot 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? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Rob.Cooke at windriver.com Tue Dec 6 20:58:44 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 6 Dec 2022 20:58:44 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - Dec 6, 2022 Message-ID: Hi everyone, Please find below this minutes from this week's StarlingX Test Status Call: Minutes for 12/06/2022 https://etherpad.opendev.org/p/stx-test * Open Topics: o None * Sanity Status: o Sanity on STX 8.0 - Sanity was paused this week in light of Wind River commercial release prioritization of lab resources. We might get a run later in the week. ? Last execution, Nov 29, 2022 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013622.html ? Next execution planned for Dec 13 o Sanity debugging on STX 8.0 plus Openstack is progressing this week on Debian based builds. Team is working through issues in an attempt to achieve a successful sanity execution ? Current bug being worked https://bugs.launchpad.net/starlingx/+bug/1998630 * Feature Test Status: o Feature testing is tracked in the following google sheet ? https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Dec 7 04:41:22 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 6 Dec 2022 20:41:22 -0800 Subject: [Starlingx-discuss] Mission statement discussion - UPDATE In-Reply-To: References: Message-ID: <76D899BE-EBE1-488E-8A54-12E362834663@openinfra.dev> Hi StarlingX Community, I?m reaching out to you with an update from today?s mission statement workshop that we had during the marketing team call today. The group who participated in today?s discussion, came up with the following proposal for a revised mission statement: "Solve the operational problem of deploying and managing high-performance, distributed cloud infrastructure at scale." We decided to keep close to the current statement since the community?s focus is still on making it easier to deploy and manage distributed infrastructure on a large scale, which we felt important to highlight. For further notes about the discussions please see the following etherpad: https://etherpad.opendev.org/p/r.b99c5952acde86556a7164d870c08971 The new mission statement is not final yet, we would like to have feedback from the community before putting a new one in place! Please share your feedback about the above proposal on this thread __by the end of next Friday (December 16)__! Please let me know if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Nov 30, 2022, at 09:39, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you with a short update about the mission statement discussion. > > Unfortunately we didn?t hit critical mass on the call that was scheduled for yesterday due to some last minute conflicts that folks had. We decided to use the regular Marketing team meeting as a follow-up workshop to continue the discussion about refreshing the project?s mission statement. > > I would like to invite and encourage everyone who would like to participate to join. > > The call is scheduled for December 06 at noon PST / 2000 UTC. > > The Zoom bridge to dial in is: https://zoom.us/j/270117095?pwd=SFBReFFsdUdQd3FMdnMxVytiSzhUZz09 > > Please find the notes from our previous call here: https://etherpad.opendev.org/p/starlingx-mission-statement > > Please let me know if you would like me to add you to the meeting invite. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Nov 16, 2022, at 20:09, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> I?m reaching out to let you know that marketing team is having a follow-up workshop to continue the discussion about refreshing the project?s mission statement, and I would like to invite and encourage everyone who would like to participate to join. >> >> The call is scheduled to November 29 at noon PST / 2000 UTC. >> >> The Zoom bridge to dial in is: https://us06web.zoom.us/j/85344179503?pwd=K05kckptcmM2N3dhTEJheFVyS05OQT09 >> >> Please find the notes from our previous call here: https://etherpad.opendev.org/p/starlingx-mission-statement >> >> Please let me know if you would like me to add you to the meeting invite. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >>> On Nov 9, 2022, at 07:32, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> As a follow up to the PTG the StarlingX Marketing team started to work on proposals to update the project?s mission statement. >>> >>> The team would like to ask the community for input so we can have a more guided activity and better fitting results. The questions we raised during the Marketing meeting yesterday: >>> * What will be the community?s priorities for the short to mid-term future, meaning the next 1-3 years? >>> * What is the community?s vision with regards to challenges that the StarlingX platform is developed and shaped to solve and address? >>> >>> To ensure progress the Marketing team set up an ad-hoc meeting time for Monday (November 14) at 11am US Pacific Time, to have a workshop and work on options. Anyone who is interested in participating in that conversation please join us on the call! >>> The dial-in link for the meeting is: https://windriver.zoom.us/j/97692404047?pwd=Um93SXBzNFMwL21JUmJYU3dteVNVdz09 >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>> >> > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From starlingx.build at gmail.com Wed Dec 7 07:11:12 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 7 Dec 2022 02:11:12 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 645 - Still Failing! In-Reply-To: <1746814736.212.1670315821150.JavaMail.javamailuser@localhost> References: <1746814736.212.1670315821150.JavaMail.javamailuser@localhost> Message-ID: <1167305240.229.1670397073265.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 645 Status: Still Failing Timestamp: 20221207T031546Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221207T015931Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221207T015931Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221207T015931Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221207T015931Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221207T015931Z/logs PUBLISH_TIMESTAMP: 20221207T015931Z FLOCK_VERSION: master-centos-stable-20221207T015931Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221207T015931Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221207T015931Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Wed Dec 7 07:11:15 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 7 Dec 2022 02:11:15 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 401 - Still Failing! In-Reply-To: <1885352873.215.1670315824484.JavaMail.javamailuser@localhost> References: <1885352873.215.1670315824484.JavaMail.javamailuser@localhost> Message-ID: <1134180677.232.1670397076679.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 401 Status: Still Failing Timestamp: 20221207T024623Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221207T015931Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221207T015931Z 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/20221207T015931Z/logs MASTER_BUILD_NUMBER: 393 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221207T015931Z/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: 20221207T015931Z DOCKER_BUILD_ID: jenkins-master-containers-20221207T015931Z-builder TIMESTAMP: 20221207T015931Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221207T015931Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221207T015931Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Wed Dec 7 07:11:19 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 7 Dec 2022 02:11:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 393 - Still Failing! In-Reply-To: <831287628.218.1670315866626.JavaMail.javamailuser@localhost> References: <831287628.218.1670315866626.JavaMail.javamailuser@localhost> Message-ID: <759332139.235.1670397080157.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 393 Status: Still Failing Timestamp: 20221207T015931Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221207T015931Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Ghada.Khalil at windriver.com Wed Dec 7 15:26:34 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 7 Dec 2022 15:26:34 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 7/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 7 2022 stx.8.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1E_AQPxVrNnbVtSqQ9_CdqYidqMmYcq4n - Feature Testing: https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/1b5w2oLlGwipTlrNysWwl1JnM1dvyboIIQhpBJLcZECI/edit#gid=1717644237 - Feature Status - Making good progress on feature code merge and testing progress - 11 features are Done. 7 since the last meeting: - Update platform applications to use Debian base image - Armada Deprecation / Replacement - FluxCD (cont'd) - FEC Device Configurability (fec-operator Integration) for ACC100 & N3000 - PTP O-RAN Compliant API Notification - Support for 'reader' role at 'system' scope for StarlingX APIs / CLIs - Platform Single Core Tuning - Migrate Openstack Application to FluxCD - 4 features are Code Merged since the last meeting - Adapt software upgrades to Debian and OSTree - Debian: Migrate patching services to debian - Support for Silicom TimeSync Server Adaptor - Subcloud rehoming without controller reboot - Follow-Up / Re-forecast Required for the following features: - Feature Tested Dates - Adapt Backup/Restore to Debian and OSTree -- Action: Rob Cooke - Platform backup and restore optimization -- Action: Rob Cooke - K8s & Container Components Refresh - k8s 1.24 -- Action: Rob Cooke - Container CNI Component Refresh - k8s 1.24 -- Action: Rob Cooke - Support for ACC200 static config -- Action: Rob Cooke - Support for ACC200 with FEC Operator -- Action: Rob Cooke - O-RAN Spec Compliant O2 Interfaces -- Action: Litao Gao - New Feature Proposals - Vault Upversion: https://storyboard.openstack.org/#!/story/2010393 - Portieris Upversion: https://storyboard.openstack.org/#!/story/2010394 - Code merged date may not meet the current release MS-3, but the changes are fairly isolated and, therefore, will not pose a risk to the release. - Note: The current versions of vault & portieris are not functional in stx.7.0 w/ k8s 1.23 and later. stx.7.0 Blogs - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept >> end-Oct >> mid-Dec / Author: Cole Walker - Subcloud Local Install - Prime: RamS - Forecast: end-Nov >> mid-Jan / Author: Shrikumar Sharma From Juanita.Balaraj at windriver.com Wed Dec 7 21:38:03 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 7 Dec 2022 21:38:03 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 07-12-22 In-Reply-To: References: 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-Dec-22 StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - https://review.opendev.org/c/starlingx/docs/+/862705: Verified Hardware Updates - Waiting for updates to be completed by the Web team to be included in the StarlingX docs. - https://review.opendev.org/c/starlingx/docs/+/861367 Flatten TOC for better customer experience - AR Ron - Every one to be cautious about merge conflicts till this review this merged- DONE - events.yaml - Automation of the final updates of the events.yaml file in the StarlingX docs - AR Ron / Juanita - WIP - DONE - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: Attention Needed from ALL core reviewers before DOC Reviews are merged - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 2 Reviews - Test teams need to review and +1 open Gerrit reviews wherever applicable NOTE: All core reviewers to review and +1 or WF the Doc reviews at : https://review.opendev.org/q/starlingx/docs+status:open Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 11 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP Miscellaneous Updates: - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) _______________________________________________ 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 scott.little at windriver.com Thu Dec 8 03:06:57 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Dec 2022 22:06:57 -0500 Subject: [Starlingx-discuss] New IRC channel for Gerrit notifications In-Reply-To: References: <4DB4DFD4-3AB2-4EA8-956C-4297DA0B16B2@gmail.com> Message-ID: <856fd932-1176-c6bb-b9ff-9c7abaf63e85@windriver.com> +1 Scott On 2022-10-24 08:54, Outback Dingo wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > +1 > > On Mon, Oct 24, 2022 at 7:27 PM Waines, Greg wrote: >> +1 >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Friday, October 21, 2022 5:38 PM >> To: StarlingX ML >> Subject: [Starlingx-discuss] New IRC channel for Gerrit notifications >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Hi StarlingX Community, >> >> I?m reaching out to you about a topic with regards to IRC that came up during the community building discussions at the recent PTG. >> >> Currently we have one IRC channel for project related conversations and information sharing on the OFTC network called #starlingx. We also have a few bots set up for this channel, one of which sends a notification to the channel whenever there is a new change that is proposed or get merged into any of the StarlingX repos. While it is a useful feature, it makes the project channel very noisy and makes it hard to maintain a conversation due to the high volume of Gerrit notifications. >> >> I would like to propose to create a new IRC channel for the Gerrit bot messages, to keep them available without flooding the project?s main IRC channel. We could call it #starlingx-gerrit. >> >> What do you all think? >> >> Thanks and 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 >> _______________________________________________ >> 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 Ghada.Khalil at windriver.com Thu Dec 8 03:46:10 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 8 Dec 2022 03:46:10 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Dec 7, 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call December 7 2022 Meeting is at 7pm PDT / 10pm EDT / +1 10am CST Standing topics - Build - Main Branch Debian Builds - Green all week for both ISO & container builds - Main Branch CentOS Builds - Green for ISO, but consistently failing for container builds due to an issue w/ stx-keystone-api container for more than a week - LP: https://bugs.launchpad.net/starlingx/+bug/1997977 - Review is posted as WIP. Will ask the author for an update. - CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities - Forecast: Dec 14 - Does this matter anymore given stx-openstack sanity has been halted since Nov 17? - Debian Build Acceleration/Reuse Feature - The Acceleration feature is now functional for the ISO build, but not yet for container builds. - Work on container build re-use has not started yet. - Sanity - Debian Main Branch Sanity - No sanity report since last week. No resources were available to run sanity. Will resume next week. - Last sanity email sent on Nov 29: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013622.html - Status: Green - stx-openstack Debian Main Branch Sanity - Team is continuing to work through challenges to get sanity successfully running w/ stx-openstack. - Re-forecasted from Dec 7 to Dec 21. - Gerrit Reviews in Need of Attention - From last meeting: Doc Reviews: https://review.opendev.org/q/projects:starlingx+is:open+branch:master+repo:starlingx/docs - Juanita asking for feature primes to review the equivalent doc updates - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided; Author will respond by Dec 9. - 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 - Nothing raised ARs from Previous Meetings - None Open Requests for Help - Desktop Specs to run StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013643.html - Response provided by RamS and acknowledged by the author: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013650.html - Consider Closed. - StarlingX 7.0 & 8.0 deployment failures - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Nov 23: Team working thru setting up new hardware to re-test the deployments. - Nov 30: No Update - Dec 7: Team is trying a deployment this week. Will have an update for next week. - Virtio-forwarder with StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.html - ScottK responded with additional questions: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013532.html - Waiting for response / no response since Nov 6 - No activity for a month; will keep for another 2wks and then consider closed/stale. From starlingx.build at gmail.com Thu Dec 8 08:47:39 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 8 Dec 2022 03:47:39 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 402 - Still Failing! In-Reply-To: <1130333908.230.1670397074243.JavaMail.javamailuser@localhost> References: <1130333908.230.1670397074243.JavaMail.javamailuser@localhost> Message-ID: <2009204511.247.1670489260079.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 402 Status: Still Failing Timestamp: 20221208T040410Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221208T031605Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221208T031605Z 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/20221208T031605Z/logs MASTER_BUILD_NUMBER: 394 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221208T031605Z/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: 20221208T031605Z DOCKER_BUILD_ID: jenkins-master-containers-20221208T031605Z-builder TIMESTAMP: 20221208T031605Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221208T031605Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221208T031605Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Thu Dec 8 08:47:36 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 8 Dec 2022 03:47:36 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 646 - Still Failing! In-Reply-To: <1368166301.227.1670397069936.JavaMail.javamailuser@localhost> References: <1368166301.227.1670397069936.JavaMail.javamailuser@localhost> Message-ID: <1426109038.244.1670489257063.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 646 Status: Still Failing Timestamp: 20221208T043548Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221208T031605Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221208T031605Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221208T031605Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221208T031605Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221208T031605Z/logs PUBLISH_TIMESTAMP: 20221208T031605Z FLOCK_VERSION: master-centos-stable-20221208T031605Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221208T031605Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221208T031605Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Dec 8 08:47:43 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 8 Dec 2022 03:47:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 394 - Still Failing! In-Reply-To: <858201135.233.1670397077634.JavaMail.javamailuser@localhost> References: <858201135.233.1670397077634.JavaMail.javamailuser@localhost> Message-ID: <1854809622.250.1670489264329.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 394 Status: Still Failing Timestamp: 20221208T031605Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221208T031605Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Dan.Voiculeasa at windriver.com Thu Dec 8 20:26:21 2022 From: Dan.Voiculeasa at windriver.com (Voiculeasa, Dan) Date: Thu, 8 Dec 2022 20:26:21 +0000 Subject: [Starlingx-discuss] FluxCD upversion Message-ID: Hi All, FluxCD was recently upversioned[1]. There are new container images. If you bootstrap from your own private registry, please ensure your private registry is updated with the new images. docker.io/fluxcd/helm-controller:v0.27.0 docker.io/fluxcd/source-controller:v0.32.1 [1]: https://review.opendev.org/c/starlingx/ansible-playbooks/+/866820 Thanks, Dan Voiculeasa -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Fri Dec 9 08:44:28 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 9 Dec 2022 03:44:28 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 647 - Still Failing! In-Reply-To: <1899415593.242.1670489253104.JavaMail.javamailuser@localhost> References: <1899415593.242.1670489253104.JavaMail.javamailuser@localhost> Message-ID: <354782813.259.1670575469024.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 647 Status: Still Failing Timestamp: 20221209T043841Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221209T031756Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221209T031756Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221209T031756Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221209T031756Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221209T031756Z/logs PUBLISH_TIMESTAMP: 20221209T031756Z FLOCK_VERSION: master-centos-stable-20221209T031756Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221209T031756Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221209T031756Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Fri Dec 9 08:44:31 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 9 Dec 2022 03:44:31 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 403 - Still Failing! In-Reply-To: <724216573.245.1670489257708.JavaMail.javamailuser@localhost> References: <724216573.245.1670489257708.JavaMail.javamailuser@localhost> Message-ID: <2111398237.262.1670575471863.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 403 Status: Still Failing Timestamp: 20221209T040715Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221209T031756Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221209T031756Z 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/20221209T031756Z/logs MASTER_BUILD_NUMBER: 395 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221209T031756Z/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: 20221209T031756Z DOCKER_BUILD_ID: jenkins-master-containers-20221209T031756Z-builder TIMESTAMP: 20221209T031756Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221209T031756Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221209T031756Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Fri Dec 9 08:44:33 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 9 Dec 2022 03:44:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 395 - Still Failing! In-Reply-To: <1553571146.248.1670489260791.JavaMail.javamailuser@localhost> References: <1553571146.248.1670489260791.JavaMail.javamailuser@localhost> Message-ID: <1329377999.265.1670575474534.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 395 Status: Still Failing Timestamp: 20221209T031756Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221209T031756Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ildiko at openinfra.dev Fri Dec 9 22:51:37 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Fri, 9 Dec 2022 14:51:37 -0800 Subject: [Starlingx-discuss] PTG session recordings Message-ID: <8E2ADF5F-07D1-4BDC-AE26-8C23025C145F@openinfra.dev> Hi StarlingX Community, Thank you all who had the opportunity to participate in the Fall OpenInfra Project Teams Gathering (PTG) event! The community met on two consecutive days Tuesday - Wednesday to discuss both technical and project related matters. In order to provide people with the possibility to catch up on what we?ve discussed we also recorded the sessions. You access the recordings on the following links: * Tuesday (October 18) - https://us06web.zoom.us/rec/share/vpz8jmob8hM-B06vPigxICtn3Ig9a2P75FGX0u2VXf0kvoF8MMjAUSCQ17TU0erb.BuaaklhpXCEoHcUQ ** Passcode: qKY9+G+& * Wednesday (October 19) - https://us06web.zoom.us/rec/share/LYHc_ciYeC01johDCuXFHpqmEI7NTmp2yrI05qnwRVJj0QJHTYpeylLohAJ0zy0k.dgIrbww7mhbgpAs4 ** Passcode: 5$8Q!fQ# For written notes please see the etherpad here: https://etherpad.opendev.org/p/r.2857014ba5de892cca16c80ffaa4e568 Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Sat Dec 10 07:24:44 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Dec 2022 02:24:44 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 648 - Still Failing! In-Reply-To: <576492386.257.1670575466377.JavaMail.javamailuser@localhost> References: <576492386.257.1670575466377.JavaMail.javamailuser@localhost> Message-ID: <1464297127.274.1670657085889.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 648 Status: Still Failing Timestamp: 20221210T031744Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221210T020019Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221210T020019Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221210T020019Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221210T020019Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221210T020019Z/logs PUBLISH_TIMESTAMP: 20221210T020019Z FLOCK_VERSION: master-centos-stable-20221210T020019Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221210T020019Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221210T020019Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Sat Dec 10 07:24:48 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Dec 2022 02:24:48 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 404 - Still Failing! In-Reply-To: <1217141791.260.1670575469777.JavaMail.javamailuser@localhost> References: <1217141791.260.1670575469777.JavaMail.javamailuser@localhost> Message-ID: <518139142.277.1670657089071.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 404 Status: Still Failing Timestamp: 20221210T024633Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221210T020019Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221210T020019Z 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/20221210T020019Z/logs MASTER_BUILD_NUMBER: 396 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221210T020019Z/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: 20221210T020019Z DOCKER_BUILD_ID: jenkins-master-containers-20221210T020019Z-builder TIMESTAMP: 20221210T020019Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221210T020019Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221210T020019Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Sat Dec 10 07:24:51 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Dec 2022 02:24:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 396 - Still Failing! In-Reply-To: <1362397369.263.1670575472554.JavaMail.javamailuser@localhost> References: <1362397369.263.1670575472554.JavaMail.javamailuser@localhost> Message-ID: <411299059.280.1670657092265.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 396 Status: Still Failing Timestamp: 20221210T020019Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221210T020019Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Sat Dec 10 19:32:17 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Dec 2022 14:32:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 3957 - Failure! Message-ID: <964649445.285.1670700738555.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 3957 Status: Failure Timestamp: 20221210T190202Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221210T190000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: rc-6.0-compiler MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-6.0-compiler/20221210T190000Z DOCKER_BUILD_ID: jenkins-rc-6.0-compiler-20221210T190000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221210T190000Z/logs DOCKER_BUILD_TAG: rc-6.0-compiler-20221210T190000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/6.0/centos/compiler/20221210T190000Z/logs LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/rc-6.0-compiler From starlingx.build at gmail.com Sat Dec 10 19:32:20 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 10 Dec 2022 14:32:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 25 - Failure! Message-ID: <896038151.288.1670700741244.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_compiler Build #: 25 Status: Failure Timestamp: 20221210T190000Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221210T190000Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From starlingx.build at gmail.com Mon Dec 12 07:09:39 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 12 Dec 2022 02:09:39 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 650 - Failure! Message-ID: <578651341.304.1670828980175.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 650 Status: Failure Timestamp: 20221212T031344Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221212T015513Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221212T015513Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221212T015513Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221212T015513Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221212T015513Z/logs PUBLISH_TIMESTAMP: 20221212T015513Z FLOCK_VERSION: master-centos-stable-20221212T015513Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221212T015513Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221212T015513Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Mon Dec 12 07:09:42 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 12 Dec 2022 02:09:42 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 406 - Failure! Message-ID: <1081939274.307.1670828983191.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 406 Status: Failure Timestamp: 20221212T024319Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221212T015513Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221212T015513Z 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/20221212T015513Z/logs MASTER_BUILD_NUMBER: 397 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221212T015513Z/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: 20221212T015513Z DOCKER_BUILD_ID: jenkins-master-containers-20221212T015513Z-builder TIMESTAMP: 20221212T015513Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221212T015513Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221212T015513Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Mon Dec 12 07:09:45 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 12 Dec 2022 02:09:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 397 - Still Failing! In-Reply-To: <1729025411.278.1670657089859.JavaMail.javamailuser@localhost> References: <1729025411.278.1670657089859.JavaMail.javamailuser@localhost> Message-ID: <851175422.310.1670828985963.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 397 Status: Still Failing Timestamp: 20221212T015513Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221212T015513Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From scott.little at windriver.com Mon Dec 12 19:08:52 2022 From: scott.little at windriver.com (Scott Little) Date: Mon, 12 Dec 2022 14:08:52 -0500 Subject: [Starlingx-discuss] [Build] The CENGN build server is down Message-ID: <5241dd73-3f42-c7d0-1b98-7c08fb142b6a@windriver.com> Hi all The CENGN build server is down.? We've filed a ticket with CENGN to have it looked at. The mirror appear to be unaffected, but we won't see any new builds, nor mirror updates, until it is fixed. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Dec 13 17:25:04 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 13 Dec 2022 17:25:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20221211T070000Z Message-ID: Sanity Test from 2022-December 12. (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221211T070000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ 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_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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Tue Dec 13 17:47:14 2022 From: chris.friesen at windriver.com (Chris Friesen) Date: Tue, 13 Dec 2022 11:47:14 -0600 Subject: [Starlingx-discuss] Note: no longer possible to build Docker images directly on StarlingX hosts, need to use a K8s pod. Message-ID: Hi all, Back in late November we merged https://review.opendev.org/c/starlingx/config-files/+/865329 which removed the default docker network bridge as in some install sites the default IP address was colliding with an address already in use in their network.? StarlingX no longer runs containers with docker, so there was no functional impact to the platform itself. However, it does mean that it's no longer possible to build docker images on bare metal on StarlingX nodes.? That said, it should be possible to work around this by creating a Kubernetes pod using a suitable container image, obtaining a shell within that pod, and running docker within the container. Chris From ildiko at openinfra.dev Tue Dec 13 17:54:26 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 13 Dec 2022 09:54:26 -0800 Subject: [Starlingx-discuss] PTG Blog Post - REVIEW NEEDED Message-ID: Hi StarlingX Community, Better late than never, I wrote up a summary blog post to cover some of the teams updates and other topics that came up during the recent PTG. I have a PR up to add it to the website: https://github.com/StarlingXWeb/starlingx-website/pull/214 Please add any review comments to the PR or share them on this thread. I will merge the PR later this week and will be able to make edits after it is published as well. Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From scott.little at windriver.com Tue Dec 13 20:49:16 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 13 Dec 2022 15:49:16 -0500 Subject: [Starlingx-discuss] [Build] The CENGN build server is down In-Reply-To: <5241dd73-3f42-c7d0-1b98-7c08fb142b6a@windriver.com> References: <5241dd73-3f42-c7d0-1b98-7c08fb142b6a@windriver.com> Message-ID: <8fc9f7eb-0ad4-832c-59d2-8291ad954716@windriver.com> The CENGN build server is back up.? Down time was ~3 hours. Last night builds were run successfully. Scott On 2022-12-12 14:08, Scott Little wrote: > > Hi all > > The CENGN build server is down.? We've filed a ticket > > with CENGN to have it looked at. > > The mirror appear to be unaffected, but we won't see any new builds, > nor mirror updates, until it is fixed. > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Dec 14 13:40:38 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 14 Dec 2022 13:40:38 +0000 Subject: [Starlingx-discuss] StarlingX Project Survey In-Reply-To: References: <62FCC0FF-6565-4CA1-94B7-1A0D52475D61@gmail.com> <4B7C8711-FCF5-4168-844D-0DD09B22D710@gmail.com> <16069B94-01C2-4250-A901-50247CF9D951@openinfra.dev> <764C3AE4-BD17-48EF-8F58-E560044886D4@openinfra.dev> Message-ID: Hey Ildiko, Finally got around to looking at this. Looks good. Only comment is on this question: What is your StarlingX platform deployment type? - Bare Metal - Virtual - Combination of both StarlingX only supports 'Bare Metal' deployments ... for 'live'/'field' deployments. Virtual deployments are strictly for evaluation and development purposes. I am thinking we should remove this question. Greg. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, November 30, 2022 12:54 PM To: StarlingX ML Cc: Outback Dingo ; Waines, Greg Subject: Re: [Starlingx-discuss] StarlingX Project Survey CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, Thank you all for reviewing the Starlingx User Survey! After a short discussion period we have a final set of questions to go into the survey. Based on the previous survey and the community?s input, I already created the new form in a tool called Formstack. You can find the new survey here for review: https://openinfrafoundation.formstack.com/forms/starlingx_user_survey __Please let me know if you spotted any typos or other issues as soon as you can!__ As next steps, I will update the website with the new link as well as include it in the upcoming OpenInfra Foundation Newsletter. Please let me now if you have any questions or comments. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Nov 24, 2022, at 06:42, Waines, Greg wrote: > > Answer to question on line 80 ... Does the CPU configuration (shared, dedicated, isolated) count as an acceleration feature or should we have a CPU configuration specific question rather? > > I suppose it's more of a performance feature than an acceleration feature ... but I don't think it's a stretch to include it with the acceleration features, as opposed to splitting it out into another question ... but up to you. > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, November 23, 2022 6:22 PM > To: StarlingX ML > Cc: Waines, Greg ; Outback Dingo > > Subject: Re: [Starlingx-discuss] StarlingX Project Survey > > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi All, > > We are now in the finish line to update the StarlingX survey! > > I got through the survey etherpad and there?s one question that I have > a question to which is currently unanswered. It is question 14, which > is currently in line #80 here: > https://etherpad.opendev.org/p/starlingx-survey#L80 > > Please let me know if you have an opinion about it. I will share the link to the new survey as soon as we finalize the last outstanding item. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Nov 23, 2022, at 10:19, Ildiko Vancsa wrote: >> >> Hi Greg, >> >> Great, thank you for checking! >> >> I added a comment to the top of the etherpad (https://etherpad.opendev.org/p/starlingx-survey#L8) about the crossed over lines when I made the edits yesterday. >> >> Tl;dr: I started to build the new survey in the tool that we?re going to use going forward and I marked the questions I already added to the form by crossing them over. It is just a reminder that those are already added and if we change them then I?ll have to update the actual survey form as well. Sorry about the confusion. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >> >> >> >> >>> On Nov 23, 2022, at 10:14, Waines, Greg wrote: >>> >>> Hey Ildiko, >>> Just reviewed the current etherpad page ( https://etherpad.opendev.org/p/starlingx-survey ). >>> I added some new comments. >>> >>> Generally though, it looked like we are removing a lot of questions ? Why is that ? >>> >>> Greg. >>> >>> -----Original Message----- >>> From: Ildiko Vancsa >>> Sent: Monday, November 21, 2022 12:52 PM >>> To: Outback Dingo >>> Cc: Waines, Greg ; StarlingX ML >>> >>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>> >>> CAUTION: This email comes from a non Wind River email account! >>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>> >>> Thanks Greg and Scott! >>> >>> I added some more suggestions and questions. Please let me know what you think. >>> >>> Thanks, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>> >>> >>> >>> >>>> On Nov 14, 2022, at 07:01, Outback Dingo wrote: >>>> >>>> added my input.... :) >>>> >>>> On Mon, Nov 14, 2022 at 8:26 PM Waines, Greg wrote: >>>>> >>>>> Added responses to your questions. >>>>> Greg. >>>>> >>>>> -----Original Message----- >>>>> From: Ildiko Vancsa >>>>> Sent: Thursday, November 10, 2022 5:56 PM >>>>> To: Waines, Greg >>>>> Cc: StarlingX ML >>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>> >>>>> CAUTION: This email comes from a non Wind River email account! >>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>> >>>>> Hi Greg, >>>>> >>>>> Great, thank you. I added some clarification questions to it. >>>>> >>>>> If you feel a more real-time conversation would be good, I?m in the #starlingx channel on IRC. >>>>> >>>>> Thanks, >>>>> Ildik? >>>>> >>>>> >>>>>> On Nov 10, 2022, at 07:59, Waines, Greg wrote: >>>>>> >>>>>> Hey Ildiko, >>>>>> I updated https://etherpad.opendev.org/p/starlingx-survey with some comments ... in blue. >>>>>> looking good, >>>>>> Greg. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ildiko Vancsa >>>>>> Sent: Monday, November 7, 2022 9:54 PM >>>>>> To: Waines, Greg >>>>>> Cc: StarlingX ML >>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>> >>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> Sounds good. >>>>>> >>>>>> I created a new proposed survey on the top of the etherpad: >>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>> >>>>>> Please let me know what you think. >>>>>> >>>>>> Thanks, >>>>>> Ildik? >>>>>> >>>>>> >>>>>>> On Nov 7, 2022, at 04:27, Waines, Greg wrote: >>>>>>> >>>>>>> Yeah I would still add Vault and Portieris ... we plan to put them back. >>>>>>> Greg. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ildiko Vancsa >>>>>>> Sent: Friday, November 4, 2022 2:23 PM >>>>>>> To: Waines, Greg >>>>>>> Cc: StarlingX ML >>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>> >>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>> >>>>>>> Thanks Greg for the feedback! I will add your suggestion to the etherpad. >>>>>>> >>>>>>> Quick question regarding the list below. In my understanding 7.0 was dropping support for Vault and Portieris. Do you still want to include them in the list? >>>>>>> >>>>>>> Thanks, >>>>>>> Ildik? >>>>>>> >>>>>>> >>>>>>>> On Nov 3, 2022, at 04:46, Waines, Greg wrote: >>>>>>>> >>>>>>>> My thoughts ... >>>>>>>> >>>>>>>> I think it would be helpful to get a view of what capabilities in StarlingX that our users are leveraging. >>>>>>>> I.e. to help guide us on evolving the capabilities of StarlingX >>>>>>>> For example, ask what capabilities of StarlingX do you use ? >>>>>>>> ... and provide a CHECKBOX list of capabilities that the user can >>>>>>>> pick >>>>>>>> 1 or more of the capabilities e.g. >>>>>>>> - Kuberenetes >>>>>>>> - OpenStack >>>>>>>> - Distributed Cloud >>>>>>>> - Standalone Clouds, >>>>>>>> - Deployment Configs >>>>>>>> * SX, >>>>>>>> * DX, >>>>>>>> * Standard), >>>>>>>> - Rook, >>>>>>>> - PTP, >>>>>>>> - N3000 Support, >>>>>>>> - ACC100 Support, >>>>>>>> - NVIDA GPU Support, >>>>>>>> - QAT Support, >>>>>>>> - OIDC authentication, >>>>>>>> - Vault, >>>>>>>> - Portieris, >>>>>>>> - Auditd, >>>>>>>> - Metrics Server, >>>>>>>> - SNMP, >>>>>>>> - Dedicated CPUs, >>>>>>>> - Isolated CPUs, >>>>>>>> - ISTIO, >>>>>>>> - Cert Manager, >>>>>>>> - Remote CLI Container, >>>>>>>> - Kata Containers, >>>>>>>> - RWO PVC, >>>>>>>> - RWX PVC, >>>>>>>> - Network Plugins (SRIOV, Host-device, Macvlan, ipvlan, bridge, >>>>>>>> point-to-point, vlan, tuning, bandwidth src-based rtg, virtual rtg >>>>>>>> and forwarding, bond), >>>>>>>> - vRAN Tools Container, >>>>>>>> - ... >>>>>>>> >>>>>>>> >>>>>>>> OTHER QUESTIONS TO ADD: >>>>>>>> >>>>>>>> - Open question on any service(s) that is currently not included >>>>>>>> in StarlingX Solution >>>>>>>> >>>>>>>> - Specific questions or open ask for comments on docs.starlingx.io >>>>>>>> >>>>>>>> >>>>>>>> Greg. >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Ildiko Vancsa >>>>>>>> Sent: Wednesday, November 2, 2022 10:35 PM >>>>>>>> To: StarlingX ML >>>>>>>> Subject: [Starlingx-discuss] StarlingX Project Survey >>>>>>>> >>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>> >>>>>>>> Hi StarlingX Community, >>>>>>>> >>>>>>>> As you might know the StarlingX project has a short survey that is continuously open to learn about new and ongoing interest in the project. >>>>>>>> >>>>>>>> The survey?s main target has been to get some more background information about industry segments, use cases, etc that drive people and organizations to take a look at the project. The questions also ask about the adoption phase that companies are in as well as provides the opportunity to give feedback to the community. So far the responses were coming from people/companies who were evaluating the project. >>>>>>>> >>>>>>>> The raw data is available to OpenInfra Foundation staff to access as confidential information, which we then anonymize, aggregate and share. >>>>>>>> >>>>>>>> We are currently moving to a new tool and that provides the >>>>>>>> opportunity for the community to review and update the questions. >>>>>>>> I created an etherpad that lists the current questions and has a >>>>>>>> section for feedback and proposed updates and new questions: >>>>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>>>> >>>>>>>> >>>>>>>> If you would like to change any of the current questions or add new ones, please add them to the etherpad or reply to this thread __by the end of next week (November 11)__. >>>>>>>> >>>>>>>> I would like to note that the current survey is ket short intentionally. It gives a better likelihood that people will go through all the questions and finish the survey. When proposing new questions please keep this in mind as well. >>>>>>>> >>>>>>>> Please let me know if you have any questions. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> 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-disc >>>>>>>> us >>>>>>>> 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 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From kennelson11 at gmail.com Wed Dec 14 14:22:51 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 14 Dec 2022 08:22:51 -0600 Subject: [Starlingx-discuss] Fwd: 2023 PTGs + Virtual Team Signup In-Reply-To: References: Message-ID: Hello Everyone! The next PTG on the calendar will be our usual virtual format and it will take place March 27 -31. The project signup survey is already ready to go! If your team is interested in participating, sign them up here[1]! Registration is also open now[2] We have also heard many requests from the contributor community to bring back in person events and also heard that with global travel reduction, it would be better travel wise for the community at large to combine it with the OpenInfra Summit[3]. So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th. OpenInfra Summit registration will be required to participate, and contributor pricing and travel support[4] will be available. We will also be planning another virtual PTG in the latter half of the year. The exact date is still being finalized. This will give you three opportunities to get your team together in 2023: two virtual and one in-person. - Virtual: March 27-31 - In- Person: June 14-15 collocated with the OpenInfra Summit - Virtual: TBD, but second half of the year As any project in our community, you are free to take advantage of all or some of the PTGs this coming year. I, for one, hope to see you and your project at as many as make sense for your team! To make sure we are as inclusive as possible I will continue to encourage team moderators to write summaries of their discussions to gather and promote after the events as well. Stay tuned for more info as we get closer, but the team signup survey[1] has opened for the first virtual PTG and is ready for you! -Kendall (diablo_rojo) [1] https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] https://openinfra-ptg.eventbrite.com [3]https://openinfra.dev/summit/vancouver-2023 [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Dec 14 14:54:14 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 14 Dec 2022 06:54:14 -0800 Subject: [Starlingx-discuss] StarlingX Project Survey In-Reply-To: References: <62FCC0FF-6565-4CA1-94B7-1A0D52475D61@gmail.com> <4B7C8711-FCF5-4168-844D-0DD09B22D710@gmail.com> <16069B94-01C2-4250-A901-50247CF9D951@openinfra.dev> <764C3AE4-BD17-48EF-8F58-E560044886D4@openinfra.dev> Message-ID: <6B4B7263-A51C-4B10-86EC-D67A4B7F7E1D@openinfra.dev> Hi Greg, That makes sense, I just removed that question. I will get the new survey link up on the project website after the TSC & Community call. Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Dec 14, 2022, at 05:40, Waines, Greg wrote: > > Hey Ildiko, > Finally got around to looking at this. > > Looks good. > > Only comment is on this question: > What is your StarlingX platform deployment type? > - Bare Metal > - Virtual > - Combination of both > > StarlingX only supports 'Bare Metal' deployments ... for 'live'/'field' deployments. > Virtual deployments are strictly for evaluation and development purposes. > I am thinking we should remove this question. > > Greg. > > > > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, November 30, 2022 12:54 PM > To: StarlingX ML > Cc: Outback Dingo ; Waines, Greg > Subject: Re: [Starlingx-discuss] StarlingX Project Survey > > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi StarlingX Community, > > Thank you all for reviewing the Starlingx User Survey! > > After a short discussion period we have a final set of questions to go into the survey. Based on the previous survey and the community?s input, I already created the new form in a tool called Formstack. You can find the new survey here for review: https://openinfrafoundation.formstack.com/forms/starlingx_user_survey > > __Please let me know if you spotted any typos or other issues as soon as you can!__ > > As next steps, I will update the website with the new link as well as include it in the upcoming OpenInfra Foundation Newsletter. > > Please let me now if you have any questions or comments. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Nov 24, 2022, at 06:42, Waines, Greg wrote: >> >> Answer to question on line 80 ... Does the CPU configuration (shared, dedicated, isolated) count as an acceleration feature or should we have a CPU configuration specific question rather? >> >> I suppose it's more of a performance feature than an acceleration feature ... but I don't think it's a stretch to include it with the acceleration features, as opposed to splitting it out into another question ... but up to you. >> >> Greg. >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Wednesday, November 23, 2022 6:22 PM >> To: StarlingX ML >> Cc: Waines, Greg ; Outback Dingo >> >> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >> >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi All, >> >> We are now in the finish line to update the StarlingX survey! >> >> I got through the survey etherpad and there?s one question that I have >> a question to which is currently unanswered. It is question 14, which >> is currently in line #80 here: >> https://etherpad.opendev.org/p/starlingx-survey#L80 >> >> Please let me know if you have an opinion about it. I will share the link to the new survey as soon as we finalize the last outstanding item. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >>> On Nov 23, 2022, at 10:19, Ildiko Vancsa wrote: >>> >>> Hi Greg, >>> >>> Great, thank you for checking! >>> >>> I added a comment to the top of the etherpad (https://etherpad.opendev.org/p/starlingx-survey#L8) about the crossed over lines when I made the edits yesterday. >>> >>> Tl;dr: I started to build the new survey in the tool that we?re going to use going forward and I marked the questions I already added to the form by crossing them over. It is just a reminder that those are already added and if we change them then I?ll have to update the actual survey form as well. Sorry about the confusion. >>> >>> Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>> >>> >>> >>> >>>> On Nov 23, 2022, at 10:14, Waines, Greg wrote: >>>> >>>> Hey Ildiko, >>>> Just reviewed the current etherpad page ( https://etherpad.opendev.org/p/starlingx-survey ). >>>> I added some new comments. >>>> >>>> Generally though, it looked like we are removing a lot of questions ? Why is that ? >>>> >>>> Greg. >>>> >>>> -----Original Message----- >>>> From: Ildiko Vancsa >>>> Sent: Monday, November 21, 2022 12:52 PM >>>> To: Outback Dingo >>>> Cc: Waines, Greg ; StarlingX ML >>>> >>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>> >>>> CAUTION: This email comes from a non Wind River email account! >>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>> >>>> Thanks Greg and Scott! >>>> >>>> I added some more suggestions and questions. Please let me know what you think. >>>> >>>> Thanks, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>> >>>> >>>> >>>> >>>>> On Nov 14, 2022, at 07:01, Outback Dingo wrote: >>>>> >>>>> added my input.... :) >>>>> >>>>> On Mon, Nov 14, 2022 at 8:26 PM Waines, Greg wrote: >>>>>> >>>>>> Added responses to your questions. >>>>>> Greg. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ildiko Vancsa >>>>>> Sent: Thursday, November 10, 2022 5:56 PM >>>>>> To: Waines, Greg >>>>>> Cc: StarlingX ML >>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>> >>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> Great, thank you. I added some clarification questions to it. >>>>>> >>>>>> If you feel a more real-time conversation would be good, I?m in the #starlingx channel on IRC. >>>>>> >>>>>> Thanks, >>>>>> Ildik? >>>>>> >>>>>> >>>>>>> On Nov 10, 2022, at 07:59, Waines, Greg wrote: >>>>>>> >>>>>>> Hey Ildiko, >>>>>>> I updated https://etherpad.opendev.org/p/starlingx-survey with some comments ... in blue. >>>>>>> looking good, >>>>>>> Greg. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ildiko Vancsa >>>>>>> Sent: Monday, November 7, 2022 9:54 PM >>>>>>> To: Waines, Greg >>>>>>> Cc: StarlingX ML >>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>> >>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>> >>>>>>> Hi Greg, >>>>>>> >>>>>>> Sounds good. >>>>>>> >>>>>>> I created a new proposed survey on the top of the etherpad: >>>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>>> >>>>>>> Please let me know what you think. >>>>>>> >>>>>>> Thanks, >>>>>>> Ildik? >>>>>>> >>>>>>> >>>>>>>> On Nov 7, 2022, at 04:27, Waines, Greg wrote: >>>>>>>> >>>>>>>> Yeah I would still add Vault and Portieris ... we plan to put them back. >>>>>>>> Greg. >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Ildiko Vancsa >>>>>>>> Sent: Friday, November 4, 2022 2:23 PM >>>>>>>> To: Waines, Greg >>>>>>>> Cc: StarlingX ML >>>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>>> >>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>> >>>>>>>> Thanks Greg for the feedback! I will add your suggestion to the etherpad. >>>>>>>> >>>>>>>> Quick question regarding the list below. In my understanding 7.0 was dropping support for Vault and Portieris. Do you still want to include them in the list? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Ildik? >>>>>>>> >>>>>>>> >>>>>>>>> On Nov 3, 2022, at 04:46, Waines, Greg wrote: >>>>>>>>> >>>>>>>>> My thoughts ... >>>>>>>>> >>>>>>>>> I think it would be helpful to get a view of what capabilities in StarlingX that our users are leveraging. >>>>>>>>> I.e. to help guide us on evolving the capabilities of StarlingX >>>>>>>>> For example, ask what capabilities of StarlingX do you use ? >>>>>>>>> ... and provide a CHECKBOX list of capabilities that the user can >>>>>>>>> pick >>>>>>>>> 1 or more of the capabilities e.g. >>>>>>>>> - Kuberenetes >>>>>>>>> - OpenStack >>>>>>>>> - Distributed Cloud >>>>>>>>> - Standalone Clouds, >>>>>>>>> - Deployment Configs >>>>>>>>> * SX, >>>>>>>>> * DX, >>>>>>>>> * Standard), >>>>>>>>> - Rook, >>>>>>>>> - PTP, >>>>>>>>> - N3000 Support, >>>>>>>>> - ACC100 Support, >>>>>>>>> - NVIDA GPU Support, >>>>>>>>> - QAT Support, >>>>>>>>> - OIDC authentication, >>>>>>>>> - Vault, >>>>>>>>> - Portieris, >>>>>>>>> - Auditd, >>>>>>>>> - Metrics Server, >>>>>>>>> - SNMP, >>>>>>>>> - Dedicated CPUs, >>>>>>>>> - Isolated CPUs, >>>>>>>>> - ISTIO, >>>>>>>>> - Cert Manager, >>>>>>>>> - Remote CLI Container, >>>>>>>>> - Kata Containers, >>>>>>>>> - RWO PVC, >>>>>>>>> - RWX PVC, >>>>>>>>> - Network Plugins (SRIOV, Host-device, Macvlan, ipvlan, bridge, >>>>>>>>> point-to-point, vlan, tuning, bandwidth src-based rtg, virtual rtg >>>>>>>>> and forwarding, bond), >>>>>>>>> - vRAN Tools Container, >>>>>>>>> - ... >>>>>>>>> >>>>>>>>> >>>>>>>>> OTHER QUESTIONS TO ADD: >>>>>>>>> >>>>>>>>> - Open question on any service(s) that is currently not included >>>>>>>>> in StarlingX Solution >>>>>>>>> >>>>>>>>> - Specific questions or open ask for comments on docs.starlingx.io >>>>>>>>> >>>>>>>>> >>>>>>>>> Greg. >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Ildiko Vancsa >>>>>>>>> Sent: Wednesday, November 2, 2022 10:35 PM >>>>>>>>> To: StarlingX ML >>>>>>>>> Subject: [Starlingx-discuss] StarlingX Project Survey >>>>>>>>> >>>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>>> >>>>>>>>> Hi StarlingX Community, >>>>>>>>> >>>>>>>>> As you might know the StarlingX project has a short survey that is continuously open to learn about new and ongoing interest in the project. >>>>>>>>> >>>>>>>>> The survey?s main target has been to get some more background information about industry segments, use cases, etc that drive people and organizations to take a look at the project. The questions also ask about the adoption phase that companies are in as well as provides the opportunity to give feedback to the community. So far the responses were coming from people/companies who were evaluating the project. >>>>>>>>> >>>>>>>>> The raw data is available to OpenInfra Foundation staff to access as confidential information, which we then anonymize, aggregate and share. >>>>>>>>> >>>>>>>>> We are currently moving to a new tool and that provides the >>>>>>>>> opportunity for the community to review and update the questions. >>>>>>>>> I created an etherpad that lists the current questions and has a >>>>>>>>> section for feedback and proposed updates and new questions: >>>>>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>>>>> >>>>>>>>> >>>>>>>>> If you would like to change any of the current questions or add new ones, please add them to the etherpad or reply to this thread __by the end of next week (November 11)__. >>>>>>>>> >>>>>>>>> I would like to note that the current survey is ket short intentionally. It gives a better likelihood that people will go through all the questions and finish the survey. When proposing new questions please keep this in mind as well. >>>>>>>>> >>>>>>>>> Please let me know if you have any questions. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> 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-disc >>>>>>>>> us >>>>>>>>> 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 >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > From ildiko at openinfra.dev Wed Dec 14 15:15:11 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 14 Dec 2022 07:15:11 -0800 Subject: [Starlingx-discuss] StarlingX Project Survey In-Reply-To: <6B4B7263-A51C-4B10-86EC-D67A4B7F7E1D@openinfra.dev> References: <62FCC0FF-6565-4CA1-94B7-1A0D52475D61@gmail.com> <4B7C8711-FCF5-4168-844D-0DD09B22D710@gmail.com> <16069B94-01C2-4250-A901-50247CF9D951@openinfra.dev> <764C3AE4-BD17-48EF-8F58-E560044886D4@openinfra.dev> <6B4B7263-A51C-4B10-86EC-D67A4B7F7E1D@openinfra.dev> Message-ID: <8554EBBD-4E3C-4C93-A394-ECB2D3B47506@openinfra.dev> Quick update. Based on the TSC call discussion just now, I added the question back with the following modification: "Virtual (Not designed for production use cases)? Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Dec 14, 2022, at 06:54, Ildiko Vancsa wrote: > > Hi Greg, > > That makes sense, I just removed that question. I will get the new survey link up on the project website after the TSC & Community call. > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Dec 14, 2022, at 05:40, Waines, Greg wrote: >> >> Hey Ildiko, >> Finally got around to looking at this. >> >> Looks good. >> >> Only comment is on this question: >> What is your StarlingX platform deployment type? >> - Bare Metal >> - Virtual >> - Combination of both >> >> StarlingX only supports 'Bare Metal' deployments ... for 'live'/'field' deployments. >> Virtual deployments are strictly for evaluation and development purposes. >> I am thinking we should remove this question. >> >> Greg. >> >> >> >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Wednesday, November 30, 2022 12:54 PM >> To: StarlingX ML >> Cc: Outback Dingo ; Waines, Greg >> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >> >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi StarlingX Community, >> >> Thank you all for reviewing the Starlingx User Survey! >> >> After a short discussion period we have a final set of questions to go into the survey. Based on the previous survey and the community?s input, I already created the new form in a tool called Formstack. You can find the new survey here for review: https://openinfrafoundation.formstack.com/forms/starlingx_user_survey >> >> __Please let me know if you spotted any typos or other issues as soon as you can!__ >> >> As next steps, I will update the website with the new link as well as include it in the upcoming OpenInfra Foundation Newsletter. >> >> Please let me now if you have any questions or comments. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >>> On Nov 24, 2022, at 06:42, Waines, Greg wrote: >>> >>> Answer to question on line 80 ... Does the CPU configuration (shared, dedicated, isolated) count as an acceleration feature or should we have a CPU configuration specific question rather? >>> >>> I suppose it's more of a performance feature than an acceleration feature ... but I don't think it's a stretch to include it with the acceleration features, as opposed to splitting it out into another question ... but up to you. >>> >>> Greg. >>> >>> -----Original Message----- >>> From: Ildiko Vancsa >>> Sent: Wednesday, November 23, 2022 6:22 PM >>> To: StarlingX ML >>> Cc: Waines, Greg ; Outback Dingo >>> >>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>> >>> CAUTION: This email comes from a non Wind River email account! >>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>> >>> Hi All, >>> >>> We are now in the finish line to update the StarlingX survey! >>> >>> I got through the survey etherpad and there?s one question that I have >>> a question to which is currently unanswered. It is question 14, which >>> is currently in line #80 here: >>> https://etherpad.opendev.org/p/starlingx-survey#L80 >>> >>> Please let me know if you have an opinion about it. I will share the link to the new survey as soon as we finalize the last outstanding item. >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>> >>>> On Nov 23, 2022, at 10:19, Ildiko Vancsa wrote: >>>> >>>> Hi Greg, >>>> >>>> Great, thank you for checking! >>>> >>>> I added a comment to the top of the etherpad (https://etherpad.opendev.org/p/starlingx-survey#L8) about the crossed over lines when I made the edits yesterday. >>>> >>>> Tl;dr: I started to build the new survey in the tool that we?re going to use going forward and I marked the questions I already added to the form by crossing them over. It is just a reminder that those are already added and if we change them then I?ll have to update the actual survey form as well. Sorry about the confusion. >>>> >>>> Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>> >>>> >>>> >>>> >>>>> On Nov 23, 2022, at 10:14, Waines, Greg wrote: >>>>> >>>>> Hey Ildiko, >>>>> Just reviewed the current etherpad page ( https://etherpad.opendev.org/p/starlingx-survey ). >>>>> I added some new comments. >>>>> >>>>> Generally though, it looked like we are removing a lot of questions ? Why is that ? >>>>> >>>>> Greg. >>>>> >>>>> -----Original Message----- >>>>> From: Ildiko Vancsa >>>>> Sent: Monday, November 21, 2022 12:52 PM >>>>> To: Outback Dingo >>>>> Cc: Waines, Greg ; StarlingX ML >>>>> >>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>> >>>>> CAUTION: This email comes from a non Wind River email account! >>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>> >>>>> Thanks Greg and Scott! >>>>> >>>>> I added some more suggestions and questions. Please let me know what you think. >>>>> >>>>> Thanks, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>>> >>>>>> On Nov 14, 2022, at 07:01, Outback Dingo wrote: >>>>>> >>>>>> added my input.... :) >>>>>> >>>>>> On Mon, Nov 14, 2022 at 8:26 PM Waines, Greg wrote: >>>>>>> >>>>>>> Added responses to your questions. >>>>>>> Greg. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ildiko Vancsa >>>>>>> Sent: Thursday, November 10, 2022 5:56 PM >>>>>>> To: Waines, Greg >>>>>>> Cc: StarlingX ML >>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>> >>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>> >>>>>>> Hi Greg, >>>>>>> >>>>>>> Great, thank you. I added some clarification questions to it. >>>>>>> >>>>>>> If you feel a more real-time conversation would be good, I?m in the #starlingx channel on IRC. >>>>>>> >>>>>>> Thanks, >>>>>>> Ildik? >>>>>>> >>>>>>> >>>>>>>> On Nov 10, 2022, at 07:59, Waines, Greg wrote: >>>>>>>> >>>>>>>> Hey Ildiko, >>>>>>>> I updated https://etherpad.opendev.org/p/starlingx-survey with some comments ... in blue. >>>>>>>> looking good, >>>>>>>> Greg. >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Ildiko Vancsa >>>>>>>> Sent: Monday, November 7, 2022 9:54 PM >>>>>>>> To: Waines, Greg >>>>>>>> Cc: StarlingX ML >>>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>>> >>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>> >>>>>>>> Hi Greg, >>>>>>>> >>>>>>>> Sounds good. >>>>>>>> >>>>>>>> I created a new proposed survey on the top of the etherpad: >>>>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>>>> >>>>>>>> Please let me know what you think. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Ildik? >>>>>>>> >>>>>>>> >>>>>>>>> On Nov 7, 2022, at 04:27, Waines, Greg wrote: >>>>>>>>> >>>>>>>>> Yeah I would still add Vault and Portieris ... we plan to put them back. >>>>>>>>> Greg. >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Ildiko Vancsa >>>>>>>>> Sent: Friday, November 4, 2022 2:23 PM >>>>>>>>> To: Waines, Greg >>>>>>>>> Cc: StarlingX ML >>>>>>>>> Subject: Re: [Starlingx-discuss] StarlingX Project Survey >>>>>>>>> >>>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>>> >>>>>>>>> Thanks Greg for the feedback! I will add your suggestion to the etherpad. >>>>>>>>> >>>>>>>>> Quick question regarding the list below. In my understanding 7.0 was dropping support for Vault and Portieris. Do you still want to include them in the list? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Ildik? >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Nov 3, 2022, at 04:46, Waines, Greg wrote: >>>>>>>>>> >>>>>>>>>> My thoughts ... >>>>>>>>>> >>>>>>>>>> I think it would be helpful to get a view of what capabilities in StarlingX that our users are leveraging. >>>>>>>>>> I.e. to help guide us on evolving the capabilities of StarlingX >>>>>>>>>> For example, ask what capabilities of StarlingX do you use ? >>>>>>>>>> ... and provide a CHECKBOX list of capabilities that the user can >>>>>>>>>> pick >>>>>>>>>> 1 or more of the capabilities e.g. >>>>>>>>>> - Kuberenetes >>>>>>>>>> - OpenStack >>>>>>>>>> - Distributed Cloud >>>>>>>>>> - Standalone Clouds, >>>>>>>>>> - Deployment Configs >>>>>>>>>> * SX, >>>>>>>>>> * DX, >>>>>>>>>> * Standard), >>>>>>>>>> - Rook, >>>>>>>>>> - PTP, >>>>>>>>>> - N3000 Support, >>>>>>>>>> - ACC100 Support, >>>>>>>>>> - NVIDA GPU Support, >>>>>>>>>> - QAT Support, >>>>>>>>>> - OIDC authentication, >>>>>>>>>> - Vault, >>>>>>>>>> - Portieris, >>>>>>>>>> - Auditd, >>>>>>>>>> - Metrics Server, >>>>>>>>>> - SNMP, >>>>>>>>>> - Dedicated CPUs, >>>>>>>>>> - Isolated CPUs, >>>>>>>>>> - ISTIO, >>>>>>>>>> - Cert Manager, >>>>>>>>>> - Remote CLI Container, >>>>>>>>>> - Kata Containers, >>>>>>>>>> - RWO PVC, >>>>>>>>>> - RWX PVC, >>>>>>>>>> - Network Plugins (SRIOV, Host-device, Macvlan, ipvlan, bridge, >>>>>>>>>> point-to-point, vlan, tuning, bandwidth src-based rtg, virtual rtg >>>>>>>>>> and forwarding, bond), >>>>>>>>>> - vRAN Tools Container, >>>>>>>>>> - ... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> OTHER QUESTIONS TO ADD: >>>>>>>>>> >>>>>>>>>> - Open question on any service(s) that is currently not included >>>>>>>>>> in StarlingX Solution >>>>>>>>>> >>>>>>>>>> - Specific questions or open ask for comments on docs.starlingx.io >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Greg. >>>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Ildiko Vancsa >>>>>>>>>> Sent: Wednesday, November 2, 2022 10:35 PM >>>>>>>>>> To: StarlingX ML >>>>>>>>>> Subject: [Starlingx-discuss] StarlingX Project Survey >>>>>>>>>> >>>>>>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>>>>>> >>>>>>>>>> Hi StarlingX Community, >>>>>>>>>> >>>>>>>>>> As you might know the StarlingX project has a short survey that is continuously open to learn about new and ongoing interest in the project. >>>>>>>>>> >>>>>>>>>> The survey?s main target has been to get some more background information about industry segments, use cases, etc that drive people and organizations to take a look at the project. The questions also ask about the adoption phase that companies are in as well as provides the opportunity to give feedback to the community. So far the responses were coming from people/companies who were evaluating the project. >>>>>>>>>> >>>>>>>>>> The raw data is available to OpenInfra Foundation staff to access as confidential information, which we then anonymize, aggregate and share. >>>>>>>>>> >>>>>>>>>> We are currently moving to a new tool and that provides the >>>>>>>>>> opportunity for the community to review and update the questions. >>>>>>>>>> I created an etherpad that lists the current questions and has a >>>>>>>>>> section for feedback and proposed updates and new questions: >>>>>>>>>> https://etherpad.opendev.org/p/starlingx-survey >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> If you would like to change any of the current questions or add new ones, please add them to the etherpad or reply to this thread __by the end of next week (November 11)__. >>>>>>>>>> >>>>>>>>>> I would like to note that the current survey is ket short intentionally. It gives a better likelihood that people will go through all the questions and finish the survey. When proposing new questions please keep this in mind as well. >>>>>>>>>> >>>>>>>>>> Please let me know if you have any questions. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> 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-disc >>>>>>>>>> us >>>>>>>>>> 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 >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Rob.Cooke at windriver.com Wed Dec 14 15:27:10 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Wed, 14 Dec 2022 15:27:10 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - Dec 13, 2022 In-Reply-To: References: Message-ID: Hi everyone, Please find below this minutes from this week's StarlingX Test Status Call: Minutes for 12/13/2022 https://etherpad.opendev.org/p/stx-test * Open Topics: o None * Sanity Status: o Sanity on STX 8.0 - Green ? Last execution, Dec 12, 2022 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013682.html o Sanity debugging on STX 8.0 plus Openstack is progressing this week on Debian based builds. Team is working through issues in an attempt to achieve a successful sanity execution ? Been opening and fixing bugs in succession the last couple of days, aiming to have the stx-os on Debian minimally functional. * Already closed a couple of bugs: o https://bugs.launchpad.net/starlingx/+bug/1998230 o https://bugs.launchpad.net/starlingx/+bug/1997564 o https://bugs.launchpad.net/starlingx/+bug/1998231 * And used the time to prepare the app for new k8s stuff too: o https://review.opendev.org/c/starlingx/openstack-armada-app/+/863035 * Was trying to test this bug fix: o https://bugs.launchpad.net/starlingx/+bug/1998630 * But unfortunately recent builds of stx master-debian caused this side-effect to our app: o https://bugs.launchpad.net/starlingx/+bug/1999426 o We already have a fix proposed for it. Since it is a blocker for Jenkins automated installs, we did not have a green install yet, but are working to get it (with the LP fix) ASAP. ? Then we will be ready to resume our weekly sanity runs for stx (debian) with stx-os. ? We reckon the initial runs will not be green though, since we still have some concerns regarding virtualization features, like: * https://bugs.launchpad.net/starlingx/+bug/1999445 * This LP may be invalid, if it only happens on virtual environments (we were able to test it). Need to verify it on a lab, but several other small bug work took priority * Feature Test Status: o Feature testing is tracked in the following google sheet ? https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 14 23:12:30 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 14 Dec 2022 23:12:30 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Dec 14, 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call December 14 2022 Standing topics - Build - Main Branch Debian Builds - Green all week - Main Branch CentOS Builds - Green for ISO all week. Green for containers starting Monday as LP below has been fixed. - LP: https://bugs.launchpad.net/starlingx/+bug/1997977 >> Fixed as of Dec 12 - CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities - Forecast: Dec 14 >> TBD - Scott (Dec 14): Should continue to run the CentOS builds for the container build portion as Debian builds don't build all the containers yet - stx.6.0 Weekly Build - Failed this week; still needs investigation - CENGN Down - The CENGN server was not down. The issue was related to connectivity issues from WR. Email clarification already sent. - Debian Build Acceleration/Reuse Feature - The Acceleration feature is now functional for the ISO build, but not yet for container builds. - Work on container build re-use has not started yet. - Sanity - Debian Main Branch Sanity - Last sanity email sent on Dec 13: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013682.html - Status: Green - stx-openstack Debian Main Branch Sanity - Team is continuing to work to get sanity successfully running w/ stx-openstack. Opening/fixing bugs. - Re-forecasted from Dec 7 to Dec 21. - On track for Dec 21 target - Gerrit Reviews in Need of Attention - From last meeting: Doc Reviews: https://review.opendev.org/q/projects:starlingx+is:open+branch:master+repo:starlingx/docs - Juanita asking for feature primes to review the equivalent doc updates. Lots of active reviews. - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided; Author will respond by Dec 9. - 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.8.0 Status Update - Making good progress on feature code merge and testing progress - Next Milestone: MS-3 - target: Jan 11 - 11 features are Done. - 25 features still In Progress - 18 features are code complete and test in progress - References: - https://etherpad.opendev.org/p/stx-releases#L28 - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Meeting Holiday Schedule - Plan to meet on Dec 21. Will cancel on Dec 28. - 2023 Meetings to start Jan 4. ARs from Previous Meetings - None Open Requests for Help - Nothing new since the last meeting - StarlingX 7.0 & 8.0 deployment failures - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Nov 23: Team working thru setting up new hardware to re-test the deployments. - Nov 30: No Update - Dec 7: Team is trying a deployment this week. Will have an update for next week. - Dec 14: No Update as ScottK didn't attend - Virtio-forwarder with StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.html - ScottK responded with additional questions: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013532.html - Waiting for response / no response since Nov 6 - No activity for a month; will keep for another 2wks and then consider closed/stale. From ildiko at openinfra.dev Thu Dec 15 01:45:31 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 14 Dec 2022 17:45:31 -0800 Subject: [Starlingx-discuss] StarlingX segment for the 2022 OpenInfra Foundation Annual report - REVIEW NEEDED Message-ID: Hi StarlingX Community, I?m reaching out to you about the OpenInfra Foundation Annual Report for 2022. As every year the Foundation is putting out a report to summarize the activities and achievements for a calendar year. Since the project?s launch there is a segment that covers these topics for StarlingX as well. While 2022 is still rolling, I put together a starting point to cover StarlingX in the report next January: https://etherpad.opendev.org/p/2022_StarlingX_Annual_Update Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. __Please provide your comments and input until EoD on January 4th, 2023.__ Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Juanita.Balaraj at windriver.com Thu Dec 15 04:10:38 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 15 Dec 2022 04:10:38 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 014-12-22 In-Reply-To: References: 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-Dec-22 StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - https://review.opendev.org/c/starlingx/docs/+/862705: Verified Hardware Updates - Waiting for updates to be completed by the Web team to be included in the StarlingX docs. - events.yaml - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: Attention Needed from ALL core reviewers before DOC Reviews are merged - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 3 Reviews - Test teams need to review and +1 open Gerrit reviews wherever applicable NOTE: All core reviewers to review and +1 or WF the Doc reviews at : https://review.opendev.org/q/starlingx/docs+status:open Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 8 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP Miscellaneous Updates: - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) ____________________ 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 Linda.Wang at windriver.com Thu Dec 15 17:16:22 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Thu, 15 Dec 2022 17:16:22 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting minutes - Dec 14th, 2022 Message-ID: December 14, 2022 Attendees: Greg, Mark, Frank, Haiqing, Scott, Steve G, Carlos, Davelet, Mike 1. General Topics ??????0.1 Split package list between repositories (ISO and container images) ????????????* Resource & landing. ????????????* No request on Launchpad ????????????* AI: We'll need to look closely to see if there is. any further improvement is needed. ????????????Backup plan: use CentOS build or docker images. ??????0.2 Log into the git before download the source. * * How to pass the credential through the tooling layer when log into git repo. * * workaround: currently use repo sync outside of the containers. * * AI: Scott to write up a feature request for the tool - file a request in Story Board. ?????? 0.3 Pre-patch ISO (Luis) (Carols replacing Luis Barbosa) * * Check to see if there is a ticket to look into this issue, looks like this issue is resolved. * * the pre-patch script is being tested with success by Juliano Carvalho. * 2. StartlingX 8.0 ??????0.1 Secureboot enablement ????????????* Traditionally created the key with ISO. Prefer to create the Key with the ISO/and put it inside with the ISO. ????????????* To keep backward compatibility, will *also* need to keep the key at the originally previous location. ????????????* The new tool is there a way to update the key and lockdown EFI, it will wipe out the keys, anyway to just add the new key without wiping the old keys. ????????????* For current usage, leave the key where it is. If we want to change it, let's discuss it further in the community before changing it. ????????????* AI: Haiqing to restore the key at the current location. Scott will share the current location on the launchpad. ????????????* AI: Scott to create an issue on launchpad. Let community discuss on moving to new location.[Done] ??????????????????https://bugs.launchpad.net/starlingx/+bug/1999663 * * AI: lwang8 will send out notification to the list once it is confirmed the secureboot signing is now supported. ??????0.2 ISO size bigger than 4G ???????????? * with OOT driver may need to include the kernel source/debug package that will allow OOT tree driver to be built on customer target. ????????????* This will add the ISO size back up to greater than 4G. ????????????* AI: low priority but still need to investigate the "ISO daisy chain extension of another 4G, and tooling needs. Next Meeting: We will be cancelling December 28th's meeting, and will resume the meeting on January 11th, 2023 Thanks & Happy Holidays, Linda -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Thu Dec 15 18:57:41 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Thu, 15 Dec 2022 18:57:41 +0000 Subject: [Starlingx-discuss] Canceled: Bi-Weekly StarlingX OS Distro & Multi-OS meeting Message-ID: A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 8179 bytes Desc: not available URL: From ildiko at openinfra.dev Fri Dec 16 01:03:21 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Thu, 15 Dec 2022 17:03:21 -0800 Subject: [Starlingx-discuss] The CFP for the OpenInfra Summit 2023 is open! In-Reply-To: <90DD4E6A-84BB-43D6-BCF6-4BAA3E3C96F4@openstack.org> References: <90DD4E6A-84BB-43D6-BCF6-4BAA3E3C96F4@openstack.org> Message-ID: Hi StarlingX Community, It is a friendly reminder that the CFP for the upcoming OpenInfra Summit (June 13-15, 2023) is still open! The OpenInfra Summit will gather people who're building and running open source infrastructure including building blocks such as the Linux kernel, OpenStack, Kubernetes, StarlingX and more! The event is a great opportunity to raise awareness of the project as well as find and onboard new contributors to the project. I would like to encourage you to submit your proposals before the deadline. You can cover a feature that you are working on, talk about how to deploy and operate the platform or cover topics more in the area of community and open collaboration. __The CFP closes January 10, 2023, at 11:59 p.m. PT__ Please let me know if you need any help with putting together or review your abstract! Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Nov 15, 2022, at 07:00, Erin Disney wrote: > > Hi Everyone! > > The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is NOW LIVE [1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. > > The CFP closes January 10, 2023, at 11:59 p.m. PT > > We are also now accepting submissions for Forum sessions [3]! What should you submit to the forum vs. the traditional CFP? For the Forum, submit discussion-oriented sessions, including challenges around different software components, working group progress or best practices to tackle common issues. > > Looking for other resources? Registration [4], sponsorships [5], travel support [6] and visa requests [7] are also all open! > > Find all the information on the OpenInfra Summit 2023 in one place [8]! > > Cheers, > Erin > > [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations > [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ > [3] https://cfp.openinfra.dev/app/vancouver-2023/20/ > [4] http://openinfra.dev/summit/registration > [5] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ > [6] https://openinfrafoundation.formstack.com/forms/openinfra_tsp > [7] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 > [8] https://openinfra.dev/summit/vancouver-2023 > > _______________________________________________ > 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 Dec 17 19:33:10 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 17 Dec 2022 14:33:10 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 3986 - Failure! Message-ID: <67883403.30.1671305593815.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 3986 Status: Failure Timestamp: 20221217T190238Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221217T190000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: rc-6.0-compiler MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-6.0-compiler/20221217T190000Z DOCKER_BUILD_ID: jenkins-rc-6.0-compiler-20221217T190000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221217T190000Z/logs DOCKER_BUILD_TAG: rc-6.0-compiler-20221217T190000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/6.0/centos/compiler/20221217T190000Z/logs LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/rc-6.0-compiler From starlingx.build at gmail.com Sat Dec 17 19:33:17 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 17 Dec 2022 14:33:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 26 - Still Failing! In-Reply-To: <1028620124.286.1670700739200.JavaMail.javamailuser@localhost> References: <1028620124.286.1670700739200.JavaMail.javamailuser@localhost> Message-ID: <414349167.33.1671305597967.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_compiler Build #: 26 Status: Still Failing Timestamp: 20221217T190000Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221217T190000Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From Dan.Voiculeasa at windriver.com Tue Dec 20 12:09:11 2022 From: Dan.Voiculeasa at windriver.com (Voiculeasa, Dan) Date: Tue, 20 Dec 2022 12:09:11 +0000 Subject: [Starlingx-discuss] StarlingX App Framework update Message-ID: To all app developers out there, there was a recent change in the framework [1]. Currently if you disable a helm chart when you update an app it will be re-enabled by default on the newer version. [sysadmin at controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify usage: system helm-chart-attribute-modify [--enabled ] system helm-chart-attribute-modify --enabled false MY_APP MY_CHART MY_NAMESPACE The chart attribute(enabled/disabled) itself is stored in sysinv database in a column called 'system_overrides' (bad naming, will be aligned later).enabled If you want to keep the disabled status during app update you can update the metadata.yaml ([2] example location for one app), adding at root level the following maintain_attributes: true There is more. You can override the behavior present by adding a special flag during 'system application-update'. You can force the information either way: reuse(will keep disabled the charts that were disabled) or not reuse(reset all the charts to be enabled). system application[sysadmin at controller-0 ~(keystone_admin)]$ system application-update usage: system application-update [-n ] [-v ] [--reuse-user-overrides ] [--reuse-attributes ] system application[sysadmin at controller-0 ~(keystone_admin)]$ system application-update -n MY_APP -v MY_VERSION --reuse-attributes true /path/to/tar.gz [1]: https://review.opendev.org/c/starlingx/config/+/865327 [2]: https://opendev.org/starlingx/platform-armada-app/src/branch/master/stx-platform-helm/stx-platform-helm/files/metadata.yaml [https://opendev.org/avatars/starlingx] platform-armada-app StarlingX Platform Armada App opendev.org ? ? Thanks, Dan Voiculeasa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Dec 20 03:19:05 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 20 Dec 2022 03:19:05 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20221218T070000Z Message-ID: Sanity Test from 2022-December 19. (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221218T070000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ 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_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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Wed Dec 21 12:17:25 2022 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Wed, 21 Dec 2022 12:17:25 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20221218T070000Z] results - Dec-20 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Dec-18 build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221218T070000Z/outputs/iso/starlingx-intel-x86-64-20221218162035-cd.iso and Helm-Charts: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221218T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-latest.tgz Important note: This is the first Debian StarlingX + STX-Openstack sanity execution we had, so we are still finding bugs and opening launchpads for our team to fix. For now, we are only testing OVS, but the plan is to include OVS-DPDK in the following executions. Overall Sanity Results: ?RED AIO-DX baremetal with VSWITCH_TYPE=ovs Sanity Status: RED Automated Test Results Summary: ------------------------------------------------------ Passed: 9 (60.0%) Failed: 6 (40.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20221220 18:54:44 test_ssh_to_hosts FAIL 20221220 18:55:42 test_lock_unlock_host PASS 20221220 18:58:02 test_openstack_services_healthy PASS 20221220 18:58:33 test_reapply_stx_openstack_no_change[controller-0] PASS 20221220 19:00:53 test_reapply_stx_openstack_no_change[controller-1] PASS 20221220 19:05:48 test_horizon_create_delete_instance PASS 20221220 19:10:17 test_swact_controllers PASS 20221220 19:18:33 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20221220 19:24:06 test_migrate_vm[tis-centos-guest-live-None] FAIL 20221220 19:27:09 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20221220 19:32:04 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20221220 19:34:47 test_evacuate_vms FAIL 20221220 19:39:48 test_system_coredumps_and_crashes[core_dumps] PASS 20221220 19:41:13 test_system_coredumps_and_crashes[crash_reports] PASS 20221220 19:41:20 test_system_alarms ----------------------------------------------------------------------- All the failed test cases above are related to these launchpads: * https://bugs.launchpad.net/starlingx/+bug/1999445 * https://bugs.launchpad.net/starlingx/+bug/2000168 Thanks, STX-Openstack distro team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Dec 21 13:53:23 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 21 Dec 2022 13:53:23 +0000 Subject: [Starlingx-discuss] StarlingX segment for the 2022 OpenInfra Foundation Annual report - REVIEW NEEDED In-Reply-To: References: Message-ID: hey Ildiko, I took a quick read thru. It looks good. Only comment ... I believe we ended up NOT doing this feature: Moving from all-in-one simplex to all-in-one duplex configuration without the need to re-install RamS ? ... can you confirm ? Greg. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, December 14, 2022 8:46 PM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX segment for the 2022 OpenInfra Foundation Annual report - REVIEW NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I?m reaching out to you about the OpenInfra Foundation Annual Report for 2022. As every year the Foundation is putting out a report to summarize the activities and achievements for a calendar year. Since the project?s launch there is a segment that covers these topics for StarlingX as well. While 2022 is still rolling, I put together a starting point to cover StarlingX in the report next January: https://etherpad.opendev.org/p/2022_StarlingX_Annual_Update Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. __Please provide your comments and input until EoD on January 4th, 2023.__ Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Greg.Waines at windriver.com Wed Dec 21 14:16:07 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 21 Dec 2022 14:16:07 +0000 Subject: [Starlingx-discuss] PTG Blog Post - REVIEW NEEDED In-Reply-To: References: Message-ID: Hey Ildiko, I reviewed blog post. Looks good to me. Thanks for providing the summary of the event. Greg. -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, December 13, 2022 12:54 PM To: StarlingX ML Subject: [Starlingx-discuss] PTG Blog Post - REVIEW NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, Better late than never, I wrote up a summary blog post to cover some of the teams updates and other topics that came up during the recent PTG. I have a PR up to add it to the website: https://github.com/StarlingXWeb/starlingx-website/pull/214 Please add any review comments to the PR or share them on this thread. I will merge the PR later this week and will be able to make edits after it is published as well. Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Ghada.Khalil at windriver.com Wed Dec 21 14:57:21 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 21 Dec 2022 14:57:21 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 21/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 21 2022 stx.8.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1E_AQPxVrNnbVtSqQ9_CdqYidqMmYcq4n - Feature Testing: https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/1b5w2oLlGwipTlrNysWwl1JnM1dvyboIIQhpBJLcZECI/edit#gid=1717644237 - Feature Status - No feature code merge complete since the last meeting. - Action: Rob to update feature test status. stx.7.0 Blogs - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept >> end-Oct >> mid-Dec >> end-Jan / Author: Cole Walker - Subcloud Local Install - Prime: RamS - Forecast: end-Nov >> mid-Jan / Author: Shrikumar Sharma stx.9.0 - Ghada to setup release tracking spreadsheet in Jan to start planning Happy Holidays to all! From Ghada.Khalil at windriver.com Wed Dec 21 15:52:58 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 21 Dec 2022 15:52:58 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Dec 21, 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call December 21 2022 Standing topics - Build - Main Branch Debian Builds - Green all week - Main Branch CentOS Builds - Green all week - CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities - Forecast: Dec 14 >> TBD - Scott (Dec 14): Should continue to run the CentOS builds for the container build portion as Debian builds don't build all the containers yet - stx.6.0 Weekly Build - Still failing - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013697.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013698.html - Sanity - Debian Main Branch Sanity - Last sanity email sent on Dec 20: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013700.html - Status: Green - stx-openstack Debian Main Branch Sanity - First sanity run: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013701.html - Status: Red - LPs: - https://bugs.launchpad.net/starlingx/+bug/1999445 >> fix is in test. - https://bugs.launchpad.net/starlingx/+bug/2000168 >> lower priority. no negative functional impact - Pipeline is setup to run every Wednesday - Gerrit Reviews in Need of Attention - From last meeting: Doc Reviews: https://review.opendev.org/q/projects:starlingx+is:open+branch:master+repo:starlingx/docs - Good progress over the last two weeks - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided; still waiting for author to respond/address review comments - 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 - Meeting Holiday Schedule - Cancelled on Dec 28. - 2023 Meetings to start Jan 4 - Asia friendly time - No TSC portion on Jan 4 as Greg will still be on vacation ARs from Previous Meetings - None Open Requests for Help - Nothing new since the last meeting - StarlingX 7.0 & 8.0 deployment failures - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Nov 23: Team working thru setting up new hardware to re-test the deployments. - Nov 30: No Update - Dec 7: Team is trying a deployment this week. Will have an update for next week (Dec 14) - Dec 14, 21: No Update as ScottK did not attend. - Virtio-forwarder with StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.html - ScottK responded with additional questions: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013532.html - Waiting for response / no response since Nov 6 - Consider closed/stale due to lack of activity for more than a month Happy Holidays to all! From ildiko at openinfra.dev Wed Dec 21 16:36:54 2022 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 21 Dec 2022 08:36:54 -0800 Subject: [Starlingx-discuss] PTG Blog Post - REVIEW NEEDED In-Reply-To: References: Message-ID: <97BAE71F-3254-447D-B33B-243712E87560@openinfra.dev> Hi Greg, Great, thank you for checking! Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Dec 21, 2022, at 06:16, Waines, Greg wrote: > > Hey Ildiko, > I reviewed blog post. > Looks good to me. > Thanks for providing the summary of the event. > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, December 13, 2022 12:54 PM > To: StarlingX ML > Subject: [Starlingx-discuss] PTG Blog Post - REVIEW NEEDED > > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi StarlingX Community, > > Better late than never, I wrote up a summary blog post to cover some of the teams updates and other topics that came up during the recent PTG. > > I have a PR up to add it to the website: https://github.com/StarlingXWeb/starlingx-website/pull/214 > > Please add any review comments to the PR or share them on this thread. I will merge the PR later this week and will be able to make edits after it is published as well. > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From scott.kamp at xunison.com Fri Dec 23 02:10:28 2022 From: scott.kamp at xunison.com (Scott Kamp) Date: Fri, 23 Dec 2022 02:10:28 +0000 Subject: [Starlingx-discuss] Hardware Query Message-ID: Hi all, Curious If anyone has a similar deployment, not sure what the Dual 25G cards are We are looking at deploying on the following supermicro SuperMicro SUPERBLADE SBE-414J with https://www.supermicro.com/en/products/superblade/module/sbi-420p-4t2n.cfm SBI-420P-4T2N | Twin Blade | Products | Super Micro Computer, Inc. 4U 14 SuperBlade Processor Blade chassis: Add-on Card / Module AOM-SB414-01-P: 1 Front control board with KVM for Blade,HF,RoHS: Hard Drive Tray: MCP-220-00170-0B www.supermicro.com The chassis includes Supermicro MBM-XEM-002 - Broadcom BCM56846 10GbE Low Latency Switch -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Fri Dec 23 02:43:38 2022 From: lists at optimcloud.com (Embedded Devel) Date: Fri, 23 Dec 2022 02:43:38 +0000 Subject: [Starlingx-discuss] Hardware Query In-Reply-To: References: Message-ID: <1671763383588.3583920354.4223523489@optimcloud.com> seems the Supermicro is Dual LAN with 25GbE with Mellanox ConnectX-4 Lx EN, Two (2) 10GbE Ethernet ports from KR interface to BP so STX should work fine On Friday 23 December 2022 09:10:28 AM (+07:00), Scott Kamp wrote: Hi all, Curious If anyone has a similar deployment, not sure what the Dual 25G cards are We are looking at deploying on the following supermicro SuperMicro SUPERBLADE SBE-414J with https://www.supermicro.com/en/products/superblade/module/sbi-420p-4t2n.cfm SBI-420P-4T2N | Twin Blade | Products | Super Micro Computer, Inc. 4U 14 SuperBlade Processor Blade chassis: Add-on Card / Module AOM-SB414-01-P: 1 Front control board with KVM for Blade,HF,RoHS: Hard Drive Tray: MCP-220-00170-0B www.supermicro.com The chassis includes Supermicro MBM-XEM-002 - Broadcom BCM56846 10GbE Low Latency Switch -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sat Dec 24 19:34:56 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 24 Dec 2022 14:34:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 27 - Still Failing! In-Reply-To: <776915495.31.1671305594705.JavaMail.javamailuser@localhost> References: <776915495.31.1671305594705.JavaMail.javamailuser@localhost> Message-ID: <112631453.68.1671910497893.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_compiler Build #: 27 Status: Still Failing Timestamp: 20221224T190000Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221224T190000Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From starlingx.build at gmail.com Sat Dec 24 19:34:48 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 24 Dec 2022 14:34:48 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 4015 - Failure! Message-ID: <1889425301.65.1671910494743.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 4015 Status: Failure Timestamp: 20221224T190426Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221224T190000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: rc-6.0-compiler MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-6.0-compiler/20221224T190000Z DOCKER_BUILD_ID: jenkins-rc-6.0-compiler-20221224T190000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20221224T190000Z/logs DOCKER_BUILD_TAG: rc-6.0-compiler-20221224T190000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/6.0/centos/compiler/20221224T190000Z/logs LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/rc-6.0-compiler From starlingx.build at gmail.com Thu Dec 29 05:52:01 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 29 Dec 2022 00:52:01 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 423 - Failure! Message-ID: <1052970535.92.1672293122509.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 423 Status: Failure Timestamp: 20221229T005955Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221229T001102Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221229T001102Z 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/20221229T001102Z/logs MASTER_BUILD_NUMBER: 412 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221229T001102Z/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: 20221229T001102Z DOCKER_BUILD_ID: jenkins-master-containers-20221229T001102Z-builder TIMESTAMP: 20221229T001102Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221229T001102Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221229T001102Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Thu Dec 29 05:51:57 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 29 Dec 2022 00:51:57 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 667 - Failure! Message-ID: <1816069334.89.1672293119355.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 667 Status: Failure Timestamp: 20221229T013021Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221229T001102Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20221229T001102Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20221229T001102Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221229T001102Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20221229T001102Z/logs PUBLISH_TIMESTAMP: 20221229T001102Z FLOCK_VERSION: master-centos-stable-20221229T001102Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20221229T001102Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20221229T001102Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Dec 29 05:52:04 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 29 Dec 2022 00:52:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 412 - Failure! Message-ID: <1161653197.95.1672293125664.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 412 Status: Failure Timestamp: 20221229T001102Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20221229T001102Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Peng.Peng at windriver.com Thu Dec 29 16:11:32 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Thu, 29 Dec 2022 16:11:32 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20221225T070000Z Message-ID: Sanity Test from 2022-December 28 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221225T070000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ 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_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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Fri Dec 30 14:35:26 2022 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Fri, 30 Dec 2022 14:35:26 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20221223T070000Z] results - Dec-29 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Dec-23 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221223T070000Z/outputs/iso/starlingx-intel-x86-64-20221223162754-cd.iso and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20221223T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-latest.tgz Overwall Sanity Results: RED AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: RED Automated Test Results Summary: ------------------------------------------------------ Passed: 9 (60.0%) Failed: 6 (40.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20221220 18:54:44 test_ssh_to_hosts FAIL 20221220 18:55:42 test_lock_unlock_host PASS 20221220 18:58:02 test_openstack_services_healthy PASS 20221220 18:58:33 test_reapply_stx_openstack_no_change[controller-0] PASS 20221220 19:00:53 test_reapply_stx_openstack_no_change[controller-1] PASS 20221220 19:05:48 test_horizon_create_delete_instance PASS 20221220 19:10:17 test_swact_controllers PASS 20221220 19:18:33 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20221220 19:24:06 test_migrate_vm[tis-centos-guest-live-None] FAIL 20221220 19:27:09 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20221220 19:32:04 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20221220 19:34:47 test_evacuate_vms FAIL 20221220 19:39:48 test_system_coredumps_and_crashes[core_dumps] PASS 20221220 19:41:13 test_system_coredumps_and_crashes[crash_reports] PASS 20221220 19:41:20 test_system_alarms ----------------------------------------------------------------------- All the failed test cases above are related to these launchpads: * https://bugs.launchpad.net/starlingx/+bug/1999445 * https://bugs.launchpad.net/starlingx/+bug/2000168 * https://bugs.launchpad.net/starlingx/+bug/2000483 Note: Due to the holidays, there weren't core reviewers available to code review / merge, so the state of the Stx-Openstack code is the same as it was during the last sanity. Thanks, STX-Openstack distro team -------------- next part -------------- An HTML attachment was scrubbed... URL: