lists.starlingx.io
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

Starlingx-discuss

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
starlingx-discuss@lists.starlingx.io

July 2023

  • 39 participants
  • 56 discussions
[Starlingx-discuss] Contributor recognition and appreciation
by Ildiko Vancsa 18 Jul '23

18 Jul '23
Hi StarlingX Community, I would like to share an idea that came up during the StarlingX Marketing team call today. The team was talking about thoughts for the ongoing celebration of the project’s 5th year anniversary, and the idea of contributor recognition and appreciation came up. As the community has changed significantly since its inception, we thought to rather implement this per release and do it at the end of each cycle. The goal is to recognize the contributors at each release cycle who go above and beyond for the project and community. While everybody’s work and contributions are invaluable, not all of those are equally visible, which this idea is targeted to address. We didn’t discuss the process in deep details, but a few things that came up included: * Have a nomination process towards the end of the release cycles, where contributors can nominate people * We can hold a ceremony during a Community Call when a new release comes out * We can write a blog post to highlight contributors and their work - OpenStack Contributor Award blog post as an example: https://superuser.openinfra.dev/articles/openstack-community-contributor-aw… What do you all think? Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
1 0
0 0
[Starlingx-discuss] Minutes: Test Status Call - July 18, 2023
by Cooke, Rob 18 Jul '23

18 Jul '23
Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 07/18/2023 * Open Topics: ? Plan to discuss the feature list for STX9.0 in the release call this week. * Is there a plan to revisit the list, are all items still planned for STX9.0, does the list need refinement etc. * Sanity Status: o Sanity on STX 9.0 - Green ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014295.html o Sanity on STX 9.0 plus Openstack - Red ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014296.html ? The STX-Openstack application failed to apply due to the #2028061 launchpad: STX-Openstack apply failed on the openvswitch helm release (https://bugs.launchpad.net/starlingx/+bug/2028061) The team is already working on a fix for it and should be good for the next sanity run. * Feature Test Status: o Feature testing is tracked in the following google sheet: ? https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMC… ? Some features are in progress, sheet does need updating ACTION: Rob/Nimalini * Regression Testing will be tracked here closer to release end: ? https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuL… Thanks, Rob
1 0
0 0
[Starlingx-discuss] Minutes: OpenStack Distro Team Call (Jul 18, 2023)
by Cervi, Thales Elero 18 Jul '23

18 Jul '23
Etherpad: https://etherpad.opendev.org/p/stx-distro-openstack-meetings Minutes from the OpenStack Distro team call Jul 18, 2023 Build: - Build Issues: None Installation: - Installation Issues: # LP 2028061: STX-Openstack apply failed on the openvswitch helm release - Found today (July 18th). Fix proposed: https://review.opendev.org/c/starlingx/integ/+/888781 Sanity with stx-openstack (main branch): - Last Successful Execution: (OVS) Tue Jul 11 12:39:12 UTC 2023 - Overall status: GREEN       Sanity - Passed: 15 (100.00%) | Failed: 0 (0.0%)       Regression - Passed: 12 (100.00%) | Failed: 0 (0.0%) - Last Execution: (OVS) Tue Jul 18 12:39:12 UTC 2023 - Overall status: RED (# LP 2028061)       Sanity - Executed: 0 (0.0%)       Regression - Executed: 0 (0.0%) - Bugs Affecting Weekly Sanity/Regression: - No Reproducible bugs currently open. Only intermittent issues # LP 2023657: STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app # LP 2012389: STX-Openstack: Failed to activate binding for port for live migration # LP 2007303: STX-Openstack: "nova live-migration" fails to live migrate after host is forcefully turned off/on - StarlingX 9.0 Release: - Storyboard/Tasks for containerizing OpenStack clients: https://storyboard.openstack.org/#!/story/2010774 - Majority of the development is done (still using Ussuri based clients inside the container) - Documentation updates will be required: Task 48413 - Follow-up/Improvement tasks: Tasks 48410 and 48411 - Storyboard/Tasks for OpenStack upversion (Antelope): https://storyboard.openstack.org/#!/story/2010715 - In progress - We need the platform/application manifest decoupling to finish this work - Locally building the packages we faced an issue with required build dependencies that are higher than our current debian-bullseye.lst entries (e.g. oslo-db, sqlalchemy, keystone-auth) - Locally building the docker images: faced similar issue with required build dependencies (pip versioning conflicts and upper-constraints mismatches) - Storyboard/Tasks for decoupling platform and application manifests: https://storyboard.openstack.org/#!/story/2010797 - Infra team is prioritizing the CENGN decommission and will act on it after that -- Best Regards, Thales Elero Cervi
1 0
0 0
[Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build [20230714T060000Z] results - Jul - 18
by De Ataides Barreto, Lucas 18 Jul '23

18 Jul '23
Hi all, StarlingX + STX-Openstack sanity and regression results: Overall Status: RED Build Info: Build date: July 14 - 20230714T060000Z ISO: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic… Helm Chart: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic… The STX-Openstack application failed to apply due to the #2028061 launchpad: STX-Openstack apply failed on the openvswitch helm release (https://bugs.launchpad.net/starlingx/+bug/2028061) The team is already working on a fix for it and should be good for the next sanity run. Thanks, STX-Openstack Distro Team
1 0
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230714T060000Z
by Peng, Peng 18 Jul '23

18 Jul '23
Sanity Test from 2023 July 17 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic…) 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] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 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_swact_controller_platform 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_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_bmc_verify_bm_type_ipmi PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Regards, PV team
1 0
0 0
[Starlingx-discuss] Vulnerability Management guidelines - improving visibility
by Geary, Stephen (Steve) 17 Jul '23

17 Jul '23
Jeremy, First, thank you for your contributions! Your contribution history actually addressed the uneasiness I was developing based upon my read of the thread. Comments and phrases in the thread led me to believe (incorrectly) we may trying to create something that industry and community processes and best practices have solved. All good and thanks! -steve
1 0
0 0
[Starlingx-discuss] Vulnerability Management guidelines - improving visibility
by Geary, Stephen (Steve) 14 Jul '23

14 Jul '23
I read the issue as more than visibility. I see an opportunity, if not need, to adopt best practices and industry standard practices associated with vulnerability reporting and management. Maybe we could look to OpenSSF for ideas and first steps: https://github.com/ossf/wg-vulnerability-disclosures/blob/main/README.md -steve -----Original Message----- From: starlingx-discuss-request(a)lists.starlingx.io <starlingx-discuss-request(a)lists.starlingx.io> Sent: Wednesday, July 12, 2023 6:30 AM To: starlingx-discuss(a)lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 22 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. Send Starlingx-discuss mailing list submissions to starlingx-discuss(a)lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request(a)lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner(a)lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Vulnerability Management guidelines - improving visibility (Ildiko Vancsa) 2. Re: Vulnerability Management guidelines - improving visibility (Waines, Greg) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Jul 2023 13:51:02 -0700 From: Ildiko Vancsa <ildiko(a)openinfra.dev> To: StarlingX ML <starlingx-discuss(a)lists.starlingx.io> Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: <E4EE8A0C-09FF-4F3F-B81E-723E0B51CD74(a)openinfra.dev> Content-Type: text/plain; charset=utf-8 Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation ------------------------------ Message: 2 Date: Wed, 12 Jul 2023 11:49:20 +0000 From: "Waines, Greg" <Greg.Waines(a)windriver.com> To: Ildiko Vancsa <ildiko(a)openinfra.dev>, StarlingX ML <starlingx-discuss(a)lists.starlingx.io> Subject: Re: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: <CO1PR11MB50907AF53BD6F4621E2FECE4E536A(a)CO1PR11MB5090.namprd11.prod.outlook.com> Content-Type: text/plain; charset="utf-8" We do have a high level view of 'CVE Maintenance' in docs.starlingx.io . https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd54b3.… We could provide a reference/link here to the more detailed page in the wiki . Greg. -----Original Message----- From: Ildiko Vancsa <ildiko(a)openinfra.dev> Sent: Tuesday, July 11, 2023 4:51 PM To: StarlingX ML <starlingx-discuss(a)lists.starlingx.io> Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility 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, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 22 *************************************************
2 1
0 0
[Starlingx-discuss] Vulnerability Management guidelines - improving visibility
by Ildiko Vancsa 14 Jul '23

14 Jul '23
Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project’s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project’s homepage, the docs homepage, etc? Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
5 7
0 0
[Starlingx-discuss] Minutes: Community Call (Jul 12, 2023)
by Khalil, Ghada 12 Jul '23

12 Jul '23
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 12, 2023 Standing topics - Build - Main Branch Debian Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - stx.6.0 Weekly RC Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly RC Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Note: No container image builds are done for stx.7.0 - stx.8.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/ - Transition from CENGN - Build team is working on transitioning the builds to WR infrastructure as CENGN will no longer be able to host the StarlingX builds. - Timing: Tentatively end-July / early-Aug - Status: - Able to build everything now - Still working w/ WR IT on publicly posting build results, but making progress and should have an update next week. - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on July 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014273.html - Status: Green for SX and DX - Debian Main Branch stx-openstack Sanity - Last sanity email sent on July 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014276.html - Status: Green - Gerrit Reviews in Need of Attention - No Gerrit reviews needing discussion this week. - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Abandoned as the tools repo has been restructured. - 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 - Ghada away next week. Greg will chair the community call. ARs from Previous Meetings - Manifest repo re-configuration / split to allow stx-openstack to be built independently from the platform - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014206.html - No concerns from the community regarding this proposal. - The key issue is scheduling time for the build team to implement the change. - Action: Build team to propose a timeline based on their priorities/availability. - Build Team planning on end-of-July ... after CENGN work complete - StoryBoard tracking the work: https://storyboard.openstack.org/#!/story/2010797 - Renaming App Repos to remove the "armada" - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014215.html - Minor / cosmetic change. Lower priority, but would be nice to do. Should have no impact on runtime. - Action: Build team to propose a timeline based on their priorities/availability. (lower priority than the manifest repo re-config) - Still planning ... likely after splitting manifests for openstack - StarlingX Subproject Meetings Update - Action: Scott Little to confirm w/ Mike Matteson on the build meeings - Scott is suggesting to cover build topics as part of the OS-distro meeting. Scott to discuss with the PL/TL. - Status: see below ( Part of Greg's followup with subprojects' meeting schedules ) - Action: Chris Friesen to provide an update on the containerization meetings - Status: see below ( Part of Greg's followup with subprojects' meeting schedules ) - Action: Greg ... Review which subproject teams are holding meetings on regular basis in StarlingX environment - Status: Closed / Greg followed up; only the build & container subproject teams doing have regular meetings. Bruce & Greg are following up. - ARM Support - Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines - Action: Scott Little to respond regarding build questions - Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN - Action: Scott Kamp to explore providing a hosting env temporarily - No plan to publish images to dockerhub/starlingx until they are part of the official build infrastructure - Under discussion in the OS subproject meeting - Jackie is donating hardware, but it needs to be managed by someone - Status: Open / No Update - Greg took the action to identify the right prime to drive the ARM Support project within StarlingX - SteveG available to help Open Requests for Help - Help w/ Install - Two people asking for help with installation on IRC - Bruno is trying to help them, but it appears that they are in a different timezone. If others can participate, it would be great. - Switch of Activity - Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014260.html - Status: - Already answered by Greg on July 10. Will leave open for another week in case there is further response from the reporter - Issue w/ pxebooting a second node on StarlingX - Question raised on the community call (Apr 26) by Kevin - The initial node installs/boots correctly, but but an identical second node doesn't. This setup is using vmare to run StarlingX in VMs. - Status: Open / Greg has some information to share, but isn't sure how to get in touch w/ Kevin - Build System Setup - Question was posted on IRC by Kevin - StarlingX documentation has a lot of outdated information. It took a lot of digging to find the right documentation for setting up a build env with minikube. - Requested that Kevin open an LP to the doc team and/or send an email to the mailing list w/ more details to the mailing list - Status: Open / No email sent to the mailing list yet. Unsure if LP was opened. - Support for StarlingX 8 setup bring up - Reported by Prashanthi - Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/014026.ht… - Status: - Open / Discussion is active on the mailing list. Greg providing assistance. The issues are related to date/time issues on servers being setup as well as firewall issues - CURRENTLY PAUSED ... Prashanthi had higher internal priorities that have taken her away from looking at StarlingX for the time being; waiting for Prashanthi to get back to us.
1 0
0 0
[Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 221 - Failure!
by starlingx.build@gmail.com 12 Jul '23

12 Jul '23
Project: STX_build_debian_master Build #: 221 Status: Failure Timestamp: 20230712T060000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/… -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true
1 0
0 0
  • ← Newer
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.