From starlingx.build at gmail.com Wed Feb 1 07:13:59 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 1 Feb 2023 02:13:59 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 693 - Still Failing! In-Reply-To: <946073954.276.1675150486675.JavaMail.javamailuser@localhost> References: <946073954.276.1675150486675.JavaMail.javamailuser@localhost> Message-ID: <1580675636.292.1675235642062.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 693 Status: Still Failing Timestamp: 20230201T033510Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230201T020716Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20230201T020716Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20230201T020716Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230201T020716Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20230201T020716Z/logs PUBLISH_TIMESTAMP: 20230201T020716Z FLOCK_VERSION: master-centos-stable-20230201T020716Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20230201T020716Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230201T020716Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Wed Feb 1 07:14:04 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 1 Feb 2023 02:14:04 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 449 - Still Failing! In-Reply-To: <1700309283.279.1675150493535.JavaMail.javamailuser@localhost> References: <1700309283.279.1675150493535.JavaMail.javamailuser@localhost> Message-ID: <1179481764.295.1675235645361.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 449 Status: Still Failing Timestamp: 20230201T030556Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230201T020716Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20230201T020716Z 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/20230201T020716Z/logs MASTER_BUILD_NUMBER: 433 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20230201T020716Z/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: 20230201T020716Z DOCKER_BUILD_ID: jenkins-master-containers-20230201T020716Z-builder TIMESTAMP: 20230201T020716Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230201T020716Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230201T020716Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Wed Feb 1 07:14:07 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 1 Feb 2023 02:14:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 433 - Still Failing! In-Reply-To: <544224771.282.1675150496753.JavaMail.javamailuser@localhost> References: <544224771.282.1675150496753.JavaMail.javamailuser@localhost> Message-ID: <1181751312.298.1675235648452.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 433 Status: Still Failing Timestamp: 20230201T020716Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230201T020716Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ildiko at openinfra.dev Wed Feb 1 08:18:12 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 1 Feb 2023 09:18:12 +0100 Subject: [Starlingx-discuss] TSC & Community call in the APAC-friendly time slot this week Message-ID: Hi StarlingX Community, It is a friendly reminder that the TSC & Community call is happening in the APAC-friendly time slot today! The call is scheduled to happen on February 1 at 7pm Pacific Time / 10m pm Eastern Time | February 2 at 0300 UTC / 11am China Standard Time. You can find dial-in information and further details here: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From scott.little at eng.windriver.com Wed Feb 1 16:23:55 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Wed, 1 Feb 2023 11:23:55 -0500 Subject: [Starlingx-discuss] [Build] Debian master branch build 20230131T070000Z Message-ID: We discovered this morning that the nightly build 20230201T070000Z was not started because the prior nights build 20230131T070000Z was hung. I have managed to kill the hung process, and thanks to a retry loop, the 20230131T070000Z is once again progressing, and has passed the prior hang point. The hang was in the 'build-stx-images.sh' command.? Specifically in the build of the 'n3000-opae' docker image. There were no recent code changes to the build tools not to that specific container to explain the hang. I've raise https://bugs.launchpad.net/starlingx/+bug/2004488 to track the issue. In place of 20230201T070000Z, a new build will be triggered immediately upon the completion of 20230131T070000Z. Scott From scott.little at windriver.com Wed Feb 1 19:26:09 2023 From: scott.little at windriver.com (Scott Little) Date: Wed, 1 Feb 2023 14:26:09 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 433 - Still Failing! In-Reply-To: <1181751312.298.1675235648452.JavaMail.javamailuser@localhost> References: <544224771.282.1675150496753.JavaMail.javamailuser@localhost> <1181751312.298.1675235648452.JavaMail.javamailuser@localhost> Message-ID: <65dba989-5828-f30e-6cff-9d68de78113d@windriver.com> Two failed docker containers in this CentOS build 1) notificationservice-base Log: /localdisk/designer/jenkins/master-containers/cgcs-root/stx/ptp-notification-armada-app/notificationservice-base/centos/docker/Dockerfile not found Probable cause: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/871182 LaunchPad: https://bugs.launchpad.net/starlingx/+bug/2004428 Proposed fix: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/872356 2) stx-platformclients Log: Running: docker build /localdisk/loadbuild/jenkins/master-containers/20230201T020716Z/std/build-images/loci --build-arg PROJECT=infra --build-arg PROJECT_REPO=nil --build-arg FROM=docker.io/starlingx/stx-centos:master-stable-20230201T020716Z --build-arg WHEELS=/opt/loci/stx-wheels/stx-centos-stable-wheels-py2.tar --build-arg PIP_PACKAGES=pycrypto httplib2 pylint pyopenssl ndg-httpsclient pyasn1 six prettytable PyYAML python-keystoneclient python-barbicanclient python-openstackclient cgtsclient fmclient distributedcloud_client osprofiler beautifulsoup4 oidcauthtools mechanize html5lib webencodings nfv-client --build-arg DIST_PACKAGES=python-devel libffi-devel openssl-devel which bash-completion helm kubernetes-1.21.8-client --build-arg PYTHON3=no --build-arg SPICE_REPO=https://github.com/freedesktop/spice-html5.git --no-cache --tag jenkins/stx-platformclients:master-centos-stable-build Sending build context to Docker daemon 158.8MB ... Step 36/36 : RUN /opt/loci/stx-scripts/install.sh ... Downloading pylint-1.9.5-py2.py3-none-any.whl (696 kB) ERROR: Could not find a version that satisfies the requirement oidcauthtools (from versions: none) ERROR: No matching distribution found for oidcauthtools The command '/bin/sh -c /opt/loci/stx-scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 5 of 5. Max command attempts reached. Aborting... Failed to build stx-platformclients... Aborting Probable cause: https://review.opendev.org/c/starlingx/oidc-auth-armada-app/+/868293 LaunchPad: https://bugs.launchpad.net/starlingx/+bug/2004506 Scott On 2023-02-01 02:14, starlingx.build at gmail.com wrote: > 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. > > Project: STX_build_layer_containers_master_master > Build #: 433 > Status: Still Failing > Timestamp: 20230201T020716Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230201T020716Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Feb 1 20:30:28 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 1 Feb 2023 20:30:28 +0000 Subject: [Starlingx-discuss] Heads Up: r/stx.8.0 release branch to be created on Feb 6 Message-ID: Hello all, The current plan is to create the stx.8.0 release branch (r/stx.8.0) on Feb 6. This is a request to developers and core reviewers to give priority to stx.8.0 gating bugs and to avoid large churn in the next few days so that no new build/sanity issues are introduced. Once the branch is created, any open bugs that are gating stx.8.0 will need to be sourced in the main branch and then cherrypicked to the release branch. A list of stx.8.0 gating bugs is available from this query: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 2 02:07:04 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 2 Feb 2023 02:07:04 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Feb 1/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Feb 1 2023 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 - 28 features are Done. - stx-openstack Features - Debian: Migrate Openstack app related packages - Team still working on LP: https://bugs.launchpad.net/starlingx/+bug/2003813 needs to be resolved for stx.8.0 - This issue affects sanity as it fails 4 TCs - Team is actively working on the issue. WIP code review opened. Will cherry-pick if this isn't addressed by the branch creation - Update openstack application containers to use Debian base image - Code Complete as of Jan 31 - 18 images are ported to Debian. They're all building successfully. - helm charts updates are also merged. - Jan 31 build should have everything that is needed. As per Scott, Jan 30 build seems to be stuck, so need to investigate. - The plan is to run sanity once the required build is available: Feb 1-2 - Test Status - Automation regression has been executed on AIO-DX on Jan 30; no issues reported. - Will also run another final automated regression once the branch is created. - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - 3 Bugs Remaining: - https://bugs.launchpad.net/starlingx/+bug/2002280 - kernel CVE - https://bugs.launchpad.net/starlingx/+bug/2003813 - openstack sanity issue - https://bugs.launchpad.net/starlingx/+bug/2004428 - CentOS build issue -- Forecast: Feb 1 - stx.8.0 Release Decisions - Criteria to create the release branch - Automated regression is complete and no gating issues >> Complete - Openstack yellow sanity w/ Debian images >> Expected before EOW: Feb 2 - Branch Creation - Starting Feb 6 - Ghada to send email to mailing list - PLs / Cores to ask team to be careful with submissions to avoid introducing new issues - Release Notes - Starting on Feb 2. Code review planned for Feb 6. - Note: Scott will branch the docs unless he hears otherwise from Juanita. - Release Press Release - Suggestions for features to highlight: - First release based on Debian OS - Staying current with k8s 1.24 - FEC Device Configurability (fec-operator Integration) for ACC100 & N3000 - PTP O-RAN Compliant API Notification - SSH integration with remote Windows Active Directory - Platform Single Core Tuning 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 - Status: Not Started. Need to re-forecast - Subcloud Local Install - Prime: RamS - Forecast: end-Nov >> mid-Jan / Author: Shrikumar Sharma - Status: Published. https://github.com/StarlingXWeb/starlingx-website/pull/218 stx.9.0 - New release folder created: https://drive.google.com/drive/folders/1beMET3I7GGa79tv4wfwzeKTy-yFVl6xR?usp=share_link - New Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Populated with deferred features from stx.8.0 - No new features proposed yet From Ghada.Khalil at windriver.com Thu Feb 2 03:55:37 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 2 Feb 2023 03:55:37 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Feb 2, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call February 1, 2023 Meeting is at 7pm PDT / 10pm EDT / +1 10am CST Standing topics - Build - Main Branch Debian Builds - Debian build from Jan 30 seems to be stuck; has been running for 30hrs. - Build was reset and was progressing as of earlier today - Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013792.html - Main Branch CentOS Builds - Builds failed due to two recent code changes - Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013793.html - Two LPs opened: - https://bugs.launchpad.net/starlingx/+bug/2004428 - Fixed as of Feb 1 - https://bugs.launchpad.net/starlingx/+bug/2004506 - Fixed as of Feb 1 - Monitoring for a new successful build - Stopping CentOS Builds - Email sent to the mailing list on Jan 16: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013758.html - No concerns raised by the community on the mailing list since the email was sent - stx-openstack images were migrated to Debian as of Jan 31 - Will wait for a final successful build before turning the build off - Forecast: Dec 14 >> Jan 31 >> Feb 8 - stx.6.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Sanity - Debian Main Branch Sanity - Last sanity email sent on Jan 31: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013787.html - Status: Green for both SX & DX - stx-openstack Debian Main Branch Sanity - Planned for Feb 2 - once a build w/ Debian-build stx-openstack images is available - All gating LPs were addressed with the exception of https://bugs.launchpad.net/starlingx/+bug/2003813 - Team continues to work on the remaining LP as it will result in a yellow sanity / failing 4 TCs - Gerrit Reviews in Need of Attention - stx-openstack Debian image migration: https://review.opendev.org/q/topic:stx-openstack-debian-images - All merged as of Jan 30 - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 18: Some activity in the review as of Jan 15 - Feb 1: Alternative fix proposed; waiting for ScottK's review - 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 - Low pariticipation in today's meeting. Total attendees: 3 - Release Status - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Upcoming Milestones: - Milestone-3: Jan 18 >> Jan 25 >> Jan 27 / Actual: Jan 31 - Feature Test Complete: Jan 25 >> Jan 31 >> Feb 2 - Pending stx-openstack sanity - Regression Test Complete: Jan 25 / Actual: Jan 30 - RC1 (branch creation): Feb 1 >> Feb 6 - Heads Up sent to mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013794.html - Final Regression Complete: Feb 15 - Release: Feb 22 - Feature Status: - 28 features are Done. - Debian: Migrate Openstack app related packages - Team still working on LP: https://bugs.launchpad.net/starlingx/+bug/2003813 which needs to be resolved for stx.8.0 - Team is actively working on the issue. WIP code review opened. Will cherrypick if this isn't addressed by the branch creation - Update openstack application containers to use Debian base image - Code Complete - 18 images are ported to Debian. They're all building successfully. helm charts updates are also merged. - The plan is to run sanity once the required build is available: Feb 2 - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - Only one stx-openstack LP is left - Release Notes - Starting on Feb 2. Code review planned for Feb 6. - Risks - stx-openstack sanity >> trending in the right direction - stx.9.0 - No new feature proposals added to the tracking spreadsheet. Call for community members to start proposing features for stx. - Would like to have the majority of features proposed by the March virtual PTG - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing ARs from Previous Meetings - None Open Requests for Help - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; not investigated yet; team focused on stx.8.0 and openstack sanity. - Reached out to reporter, so they have a view of the status. They're fine to wait until the team has bandwidth - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss documenting community tested hardware with the TSC From kennelson11 at gmail.com Thu Feb 2 18:47:03 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Thu, 2 Feb 2023 12:47:03 -0600 Subject: [Starlingx-discuss] OpenInfra Summit Forum Selection Committee Call for Volunteers Message-ID: Hello Everyone! The Forum at the OpenInfra Summit Vancouver is coming up! We would love 1 volunteer from StarlingX for the Forum Selection Committee. Ideally, the volunteer would: - already be serving in some capacity in a governance role for your project - not be planning to submit to the Forum CFP or be willing to abstain from voting on your proposals For information on the OpenInfra Summit in Vancouver: https://openinfra.dev/summit/vancouver-2023/ For more information on the Forum, please see: https://openinfra.dev/summit/vancouver-2023/forum/ Please reach out to me, knelson at open infra.dev, or reply on this thread if you're interested. Volunteers should respond on or before March 5th, 2023 @ 7:00 UTC. This role does not require you to travel to the OpenInfra Summit, but can get you a discounted ticket if you choose to volunteer and then attend (we would love to have you there!). Thanks! Kendall Nelson -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Fri Feb 3 03:58:48 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 3 Feb 2023 03:58:48 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-02-23 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 ============ 01-Feb-23 Stx 9.0 Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing Stx 8.0. Release - February 22nd Scott Little is cutting the Stx 8.0 doc branch on Monday 6th - Version Menu to be updated - AR Ron/ Scott - 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 - Stx 8.0 Release Notes - AR Juanita - events.yaml - Applies only to master and it was implemented in 8.0 and forward... - 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?? - Completed the flattening of the TOC.....Flattening of TOC not being implemented on older branches. Simplified on stx 6.0 / stx 7.0 (makes cherry picks easier) Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 3 Reviews Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug 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: - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron - 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 Lucas.DeAtaidesBarreto at windriver.com Fri Feb 3 14:39:15 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Fri, 3 Feb 2023 14:39:15 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230201T173319Z] results - Feb-3 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Jan-29 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230129T070000Z/outputs/iso/starlingx-intel-x86-64-20230129171025-cd.iso and the Feb-1 Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230201T173319Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-versioned.tgz Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 11 (73.33%) Failed: 4 (26.66%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230202 19:01:39 test_ssh_to_hosts PASS 20230202 19:03:14 test_lock_unlock_host PASS 20230202 19:21:32 test_openstack_services_healthy PASS 20230202 19:22:57 test_reapply_stx_openstack_no_change[controller-0] PASS 20230202 19:24:29 test_reapply_stx_openstack_no_change[controller-1] PASS 20230202 19:30:31 test_horizon_create_delete_instance PASS 20230202 19:34:24 test_swact_controllers PASS 20230202 19:42:16 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20230202 19:49:01 test_migrate_vm[tis-centos-guest-live-None]* FAIL 20230202 19:54:32 test_nova_actions[tis-centos-guest-dedicated-pause-unpause]* FAIL 20230202 19:58:35 test_nova_actions[tis-centos-guest-dedicated-suspend-resume]* FAIL 20230202 20:03:40 test_evacuate_vms* PASS 20230202 20:29:36 test_system_coredumps_and_crashes[core_dumps] PASS 20230202 20:39:51 test_system_coredumps_and_crashes[crash_reports] PASS 20230202 20:39:58 test_system_alarms ----------------------------------------------------------------------- All the failed tests are related to this launchpad: * https://bugs.launchpad.net/starlingx/+bug/2003813 *: Tests that passed when executed on 20230201T173319Z Helm-Charts + https://review.opendev.org/c/starlingx/nfv/+/872411. This review is not merged yet, so it will not be considered to the official sanity results. We believe that, by next week, this will be merged and those tests pass officially. Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Feb 3 17:37:54 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 3 Feb 2023 17:37:54 +0000 Subject: [Starlingx-discuss] Reminder: Heads Up: r/stx.8.0 release branch to be created on Feb 6 In-Reply-To: References: Message-ID: Hello all, The most recent builds have been successful for both Debian and CentOS. There's also a yellow stx-openstack sanity executed today: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013799.html There is only one remaining stx.8.0 gating LP: https://bugs.launchpad.net/starlingx/+bug/2003813 The branch creation will start on Monday Feb 6 as per plan. Please avoid merging large/high risk reviews until the branch is created. Thanks, Ghada From: Khalil, Ghada Sent: Wednesday, February 1, 2023 3:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Heads Up: r/stx.8.0 release branch to be created on Feb 6 Importance: High Hello all, The current plan is to create the stx.8.0 release branch (r/stx.8.0) on Feb 6. This is a request to developers and core reviewers to give priority to stx.8.0 gating bugs and to avoid large churn in the next few days so that no new build/sanity issues are introduced. Once the branch is created, any open bugs that are gating stx.8.0 will need to be sourced in the main branch and then cherrypicked to the release branch. A list of stx.8.0 gating bugs is available from this query: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sat Feb 4 03:28:50 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 3 Feb 2023 22:28:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 3080 - Failure! Message-ID: <441897190.321.1675481332004.JavaMail.javamailuser@localhost> Project: STX_build_helm_charts Build #: 3080 Status: Failure Timestamp: 20230204T032834Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230204T012816Z OS: centos DOCKER_BUILD_ID: jenkins-master-flock-20230204T012816Z-builder MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230204T012816Z/logs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/flock From starlingx.build at gmail.com Sat Feb 4 03:28:54 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 3 Feb 2023 22:28:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1086 - Failure! Message-ID: <428937660.324.1675481335157.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1086 Status: Failure Timestamp: 20230204T012816Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Sat Feb 4 18:44:28 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 4 Feb 2023 13:44:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 3081 - Still Failing! In-Reply-To: <164920011.319.1675481327600.JavaMail.javamailuser@localhost> References: <164920011.319.1675481327600.JavaMail.javamailuser@localhost> Message-ID: <328244803.330.1675536271294.JavaMail.javamailuser@localhost> Project: STX_build_helm_charts Build #: 3081 Status: Still Failing Timestamp: 20230204T184419Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230204T140000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20230204T140000Z OS: centos DOCKER_BUILD_ID: jenkins-master-20230204T140000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230204T140000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20230204T140000Z/logs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From starlingx.build at gmail.com Sat Feb 4 18:44:33 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 4 Feb 2023 13:44:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1467 - Failure! Message-ID: <438853189.333.1675536274405.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1467 Status: Failure Timestamp: 20230204T140000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230204T140000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Mon Feb 6 02:10:22 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 5 Feb 2023 21:10:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 3085 - Failure! Message-ID: <1477730845.343.1675649424991.JavaMail.javamailuser@localhost> Project: STX_build_helm_charts Build #: 3085 Status: Failure Timestamp: 20230206T021013Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T000812Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230206T000812Z OS: centos DOCKER_BUILD_ID: jenkins-master-flock-20230206T000812Z-builder MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T000812Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230206T000812Z/logs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/flock From starlingx.build at gmail.com Mon Feb 6 02:10:27 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 5 Feb 2023 21:10:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1087 - Still Failing! In-Reply-To: <1056672650.322.1675481332848.JavaMail.javamailuser@localhost> References: <1056672650.322.1675481332848.JavaMail.javamailuser@localhost> Message-ID: <2057697020.346.1675649428128.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1087 Status: Still Failing Timestamp: 20230206T000812Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T000812Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Ghada.Khalil at windriver.com Mon Feb 6 15:47:29 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 6 Feb 2023 15:47:29 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 3080 - Failure! In-Reply-To: <441897190.321.1675481332004.JavaMail.javamailuser@localhost> References: <441897190.321.1675481332004.JavaMail.javamailuser@localhost> Message-ID: The build failures were introduced by https://review.opendev.org/c/starlingx/openstack-armada-app/+/868294 which is being reverted by https://review.opendev.org/c/starlingx/openstack-armada-app/+/872686 Reminder to all: The CentOS builds are still running on the stx main branch. Please make sure your changes don't cause build issues for CentOS until these builds are officially disabled. An announcement from Scott Little will be sent to the mailing list when that is done. Thanks, Ghada -----Original Message----- From: starlingx.build at gmail.com Sent: Friday, February 3, 2023 10:29 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 3080 - Failure! 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. Project: STX_build_helm_charts Build #: 3080 Status: Failure Timestamp: 20230204T032834Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230204T012816Z OS: centos DOCKER_BUILD_ID: jenkins-master-flock-20230204T012816Z-builder MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230204T012816Z/logs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/flock From scott.little at windriver.com Mon Feb 6 16:19:38 2023 From: scott.little at windriver.com (Scott Little) Date: Mon, 6 Feb 2023 11:19:38 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1086 - Failure! In-Reply-To: <428937660.324.1675481335157.JavaMail.javamailuser@localhost> References: <428937660.324.1675481335157.JavaMail.javamailuser@localhost> Message-ID: <97d52230-c0e2-4be5-25b2-4197d33876bc@windriver.com> CentOS build failed for the 'flock' layer.? The failure was in helm chart creation. Logs: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T000812Z/logs/jenkins-STX_build_helm_charts-3085.log.html Probable cause: https://review.opendev.org/c/starlingx/openstack-armada-app/+/868294 Reverted: https://review.opendev.org/c/starlingx/openstack-armada-app/+/872686 Scott On 2023-02-03 22:28, starlingx.build at gmail.com wrote: > 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. > > Project: STX_build_layer_flock_master_master > Build #: 1086 > Status: Failure > Timestamp: 20230204T012816Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From voipas at gmail.com Wed Feb 1 10:30:27 2023 From: voipas at gmail.com (voipas) Date: Wed, 1 Feb 2023 12:30:27 +0200 Subject: [Starlingx-discuss] Starlingx on ARM processor Message-ID: Hello friends, I know that it is stated that Stalingx is designed for x86-64 based CPU. But I would like to deploy Starlingx on my EDGE devices (Raspberry PI 4). So I wanted to get your confirmation that I could compile / build Starlingx source for ARM processors (even in doc it is mentioned that prerequisite is 64bit OS). Also, any other recommendations / experience you have for EDGE openstack deployment for ARM based CPUs? Thank you in advance -- Best Regards, Giedrius -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Mon Feb 6 21:39:08 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Mon, 6 Feb 2023 21:39:08 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1086 - Failure! In-Reply-To: <97d52230-c0e2-4be5-25b2-4197d33876bc@windriver.com> References: <428937660.324.1675481335157.JavaMail.javamailuser@localhost> <97d52230-c0e2-4be5-25b2-4197d33876bc@windriver.com> Message-ID: The change revert fixed the helm-chart build issue: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T192645Z/logs/jenkins-STX_build_helm_charts-3086.log.html Thales ________________________________ From: Scott Little Sent: Monday, February 6, 2023 1:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1086 - Failure! CentOS build failed for the 'flock' layer. The failure was in helm chart creation. Logs: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230206T000812Z/logs/jenkins-STX_build_helm_charts-3085.log.html Probable cause: https://review.opendev.org/c/starlingx/openstack-armada-app/+/868294 Reverted: https://review.opendev.org/c/starlingx/openstack-armada-app/+/872686 Scott On 2023-02-03 22:28, starlingx.build at gmail.com wrote: > 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. > > Project: STX_build_layer_flock_master_master > Build #: 1086 > Status: Failure > Timestamp: 20230204T012816Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230204T012816Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From outbackdingo at gmail.com Tue Feb 7 00:25:17 2023 From: outbackdingo at gmail.com (Outback Dingo) Date: Tue, 7 Feb 2023 07:25:17 +0700 Subject: [Starlingx-discuss] Starlingx on ARM processor In-Reply-To: References: Message-ID: while i see you mentioned three components, arm, edge and openstack I concur with you that starlingx should support arm also, though it is very x86 centric that being said, we faced a similar issue, Ive listed the following to help you in your edge case scenerios kubeedge http://kubeedge.io superedge https://superedge.io openyurt https://openyurt.io Baetyl https://baetyl.io/en/ On Tue, Feb 7, 2023 at 5:02 AM voipas wrote: > > Hello friends, > > I know that it is stated that Stalingx is designed for x86-64 based CPU. > But I would like to deploy Starlingx on my EDGE devices (Raspberry PI 4). So I wanted to get your confirmation that I could compile / build Starlingx source for ARM processors (even in doc it is mentioned that prerequisite is 64bit OS). > > Also, any other recommendations / experience you have for EDGE openstack deployment for ARM based CPUs? > > Thank you in advance > > -- > Best Regards, > Giedrius > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From fungi at yuggoth.org Tue Feb 7 00:56:54 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 7 Feb 2023 00:56:54 +0000 Subject: [Starlingx-discuss] Starlingx on ARM processor In-Reply-To: References: Message-ID: <20230207005653.ahpr5qcwg76hpxar@yuggoth.org> On 2023-02-07 07:25:17 +0700 (+0700), Outback Dingo wrote: > while i see you mentioned three components, arm, edge and openstack > I concur with you that starlingx should support arm also, though it is > very x86 centric > that being said, we faced a similar issue, Ive listed the following to > help you in your edge case scenerios [...] Note that upstream OpenStack can be run on ARM (AArch64) servers, and the OpenStack community even tests changes to its source code inside virtual machines running in multiple ARM-based OpenStack Clouds. Whether RPI4 boards have sufficient resources to be used for that, and what distributions actually support running OpenStack on ARM processors more generally I don't know (Debian's OpenStack packages almost certainly do, but I'm unsure which others can). Also I have no idea what the state of StarlingX on ARM may be, nor what minimum resource requirements it might have for each server. Hopefully others on this list can speak more authoritatively on that point. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Feb 7 14:02:51 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 7 Feb 2023 14:02:51 +0000 Subject: [Starlingx-discuss] Changing the day of the StarlingX + STX-Openstack sanity Message-ID: Hi all, After some discussion, we decided to change the day of the STX + STX-Openstack sanity run from Wednesdays to Mondays. This is because, running on Wednesdays, we're constantly running into some issues with the builds (for example, changes that are merged in the middle of the week would not be included in the sanity run). Running on Mondays, we make sure that we're getting all the changes that were merged on the past week, and can send more accurate results on the state of the application. This means that the StarlingX + STX-Openstack sanity emails will now be sent on Tuesdays. This will begin to take effect on the following week, meaning that, this week, you'll still receive the STX-O Sanity email on Thursday, and, starting from the next week, the email will be sent on Tuesdays. Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dan.Voiculeasa at windriver.com Tue Feb 7 15:01:23 2023 From: Dan.Voiculeasa at windriver.com (Voiculeasa, Dan) Date: Tue, 7 Feb 2023 15:01:23 +0000 Subject: [Starlingx-discuss] StarlingX Apps general documentation Message-ID: To all app developers out there, The only Developer refence so far is https://wiki.openstack.org/wiki/StarlingX/Containers/HowToAddNewFluxCDAppInSTX, which focuses on building a StarlingX App which uses FluxCD. The focus is more on build environment so the interaction with the App Framework itself was out of scope. In an attempt demystify the StarlingX App <-> App Framework interaction I started a new page: https://wiki.openstack.org/wiki/StarlingX/Containers/StarlingXAppsInternals . It is in no way complete work, the work is just at the beginning. The purpose would be to show examples on how to configure your app to have different behavior, explain what these behaviors are, list scenarios, general guidelines. The only scenarios explained so far are: * auto update of apps * keep/reset user overrides during updates * keep/reset disabled helm charts during updates I believe we can enable auto update functionality for the apps, the only reason I sent an email so early is out of curiosity, want the app devs to be aware of the auto-update scenario and then get feedback from app devs about their app specific requirements preventing automatic update from being enabled (if any). Also, will let you know when more info is added to the wiki. Thanks, Dan Voiculeasa -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Tue Feb 7 15:37:17 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Tue, 7 Feb 2023 10:37:17 -0500 Subject: [Starlingx-discuss] StarlingX 8.0 branch creation review Message-ID: <4c0e2df9-7232-d617-3872-7af7eec8061a@eng.windriver.com> Please review this set of updates to complete the setup of the 'r/stx.8.0' branch. https://review.opendev.org/q/topic:r.stx.8.0 The branch is ready for checkout only.? No submissions until the above reviews have merged, and we have a successful CENGN build. Thanks, Scott From scott.little at windriver.com Tue Feb 7 20:47:55 2023 From: scott.little at windriver.com (Scott Little) Date: Tue, 7 Feb 2023 15:47:55 -0500 Subject: [Starlingx-discuss] StarlingX 8.0 branch creation review In-Reply-To: <4c0e2df9-7232-d617-3872-7af7eec8061a@eng.windriver.com> References: <4c0e2df9-7232-d617-3872-7af7eec8061a@eng.windriver.com> Message-ID: There are perhaps a dozen outstanding reviews for StarlingX 8.0: https://review.opendev.org/q/(topic:r.stx.8.0)AND(status:open) Scott On 2023-02-07 10:37, Scott.Little wrote: > Please review this set of updates to complete the setup of the > 'r/stx.8.0' branch. > > https://review.opendev.org/q/topic:r.stx.8.0 > > The branch is ready for checkout only.? No submissions until the above > reviews have merged, and we have a successful CENGN build. > > Thanks, Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From scott.little at windriver.com Tue Feb 7 21:36:15 2023 From: scott.little at windriver.com (Scott Little) Date: Tue, 7 Feb 2023 16:36:15 -0500 Subject: [Starlingx-discuss] CentOS builds on the master branch have been disabled. Message-ID: <36c8ab76-38b8-792f-7652-f23369c3f64c@windriver.com> CentOS builds on the master branch have been disabled at CENGN. CentOS builds on r/stx.6.0 and r/stx.7.0 will continue weekly. From Peng.Peng at windriver.com Wed Feb 8 02:27:26 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Wed, 8 Feb 2023 02:27:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230205T070000Z Message-ID: Sanity Test from 2023 February 7 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230205T070000Z/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] DX sanity Passed: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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 voipas at gmail.com Wed Feb 8 07:43:24 2023 From: voipas at gmail.com (voipas) Date: Wed, 8 Feb 2023 09:43:24 +0200 Subject: [Starlingx-discuss] Starlingx on ARM processor In-Reply-To: References: Message-ID: Thanks for your email, i also checked minimum hardware requirements for starlingx, so like raspberry pi 4b with 8 GB ram will not work with strlingx. On 2023-02-07, Tue at 02:25, Outback Dingo wrote: > while i see you mentioned three components, arm, edge and openstack > I concur with you that starlingx should support arm also, though it is > very x86 centric > that being said, we faced a similar issue, Ive listed the following to > help you in your edge case scenerios > > kubeedge http://kubeedge.io > > superedge https://superedge.io > > openyurt https://openyurt.io > > Baetyl https://baetyl.io/en/ > > On Tue, Feb 7, 2023 at 5:02 AM voipas wrote: > > > > Hello friends, > > > > I know that it is stated that Stalingx is designed for x86-64 based > CPU. > > But I would like to deploy Starlingx on my EDGE devices (Raspberry PI > 4). So I wanted to get your confirmation that I could compile / build > Starlingx source for ARM processors (even in doc it is mentioned that > prerequisite is 64bit OS). > > > > Also, any other recommendations / experience you have for EDGE openstack > deployment for ARM based CPUs? > > > > Thank you in advance > > > > -- > > Best Regards, > > Giedrius > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > -- Best Regards, Giedrius -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Feb 8 16:00:40 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 8 Feb 2023 16:00:40 +0000 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit In-Reply-To: <6F42DC9D-E2D7-40D7-85F6-E3119A4DCB6A@openinfra.dev> References: <6F42DC9D-E2D7-40D7-85F6-E3119A4DCB6A@openinfra.dev> Message-ID: Hi StarlingX Community, I?m reaching out to you with an update about the hands-on workshop the community is planning for the upcoming OpenInfra Summit & PTG[1] event. With Greg, we?ve been working with Equinix as they are donating hardware infrastructure for the workshop. Contributors are checking the environment as I type up this email, to ensure it will fit for what the workshop would like to cover. I created an etherpad to work on the details, such as outline for the session, an abstract to put on the OpenInfra Summit schedule, etc: https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 Please add any information or ideas you have for the workshop into the etherpad! Thanks and Best Regards, Ildik? [1] https://openinfra.dev/summit/vancouver-2023/ ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jan 25, 2023, at 14:48, Ildiko Vancsa wrote: > > Hi Greg, > > Noted, thank you. > > I will reach out to my contact at Equinix and check what they have available. I will copy you as well in case they have follow up questions. > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Jan 25, 2023, at 15:45, Waines, Greg wrote: >> >> In the previous workshop, >> We used one machine per person ... and they had that machine to do a virtual install. >> So maybe if we planned for 50 people max ... we could reserve 50 servers from Equinix. >> Greg. >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Wednesday, January 25, 2023 9:34 AM >> To: Waines, Greg >> Cc: StarlingX ML >> Subject: Re: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit >> >> 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! >> >> Would the workshop need one machine or multiple servers? >> >> Thanks, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >>> On Jan 25, 2023, at 15:15, Waines, Greg wrote: >>> >>> @Greg: Can you provide information about HW needs? >>> >>> I would think we would only do virtual AIO-SX setups. >>> I would use the following as a guide: https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_duplex_environ.html#physical-host-requirements-and-setup >>> >>> Summary: // I increased a little >>> Hardware requirements? >>> The host system should have at least: >>> - Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions >>> - Cores: 16 >>> - Memory: 64GB RAM >>> - Hard Disk: 1TB HDD >>> - Network: One network adapter with active Internet connection >>> >>> Software requirements? >>> The host system should have at least: >>> - A workstation computer with Ubuntu 16.04 LTS 64-bit >>> All other required packages will be installed by scripts in the StarlingX tools repository. >>> >>> Greg. >>> >>> -----Original Message----- >>> From: Ildiko Vancsa >>> Sent: Monday, January 23, 2023 1:43 PM >>> To: StarlingX ML >>> Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit >>> >>> 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, >>> >>> On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. >>> >>> Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. >>> >>> The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. >>> >>> >>> I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. >>> >>> The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. >>> >>> >>> What do you all think? Who would be interested in helping out with building and running the workshop? >>> >>> @Greg: Can you provide information about HW needs? >>> >>> 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 >> > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From helena at openstack.org Wed Feb 8 16:02:49 2023 From: helena at openstack.org (Helena Spease) Date: Wed, 8 Feb 2023 16:02:49 +0000 Subject: [Starlingx-discuss] The OpenInfra Summit Schedule is Live! Message-ID: <8190C3A3-7CEA-4C05-B18E-4B1099B514FA@openstack.org> Hello everyone, I am really excited to let you know the Schedule [1] for the OpenInfra Summit 2023 is available! The schedule features keynotes and sessions from users like Bloomberg, LINE, Alibaba Cloud, Samsung and Volvo. The event will be held June 13-15, 2023, at the Vancouver Convention Centre overlooking Vancouver Harbor. Other notable speakers include Ant Group, the Australian Research Data Commons (ARDC), China Mobile, SAP, and Viettel, the largest public and private cloud infrastructure provider in Vietnam. Check out these StarlingX session you can expect at the OpenInfra Summit! A private 5G campus network enabled and powered by OpenStack and StarlingX by Robert Holling StarlingX: Next Generation Security with Zero Trust Architecture by Sudhanshu Harshavat StarlingX at scale - Infrastructure management of 10s of 1000s of geographically distributed clouds by Ramaswamy Subramanian, John Kung The OpenInfra Summit [2] will be a limited-capacity, sellout event. Early bird sales for the OpenInfra Summit end February 15, 2023 at 11:59 PM PT. Register now [3] to save on your ticket and join us in Vancouver, June 13-15, 2023! The price increase will also apply to contributor discount codes, so if you received a contributor discount code last week, be sure to use it before February 15! Looking for other resources for the OpenInfra Summit? Sponsorship, Travel Support, visa requests, info on the PTG at the OpenInfra Summit, and Forum session details can be found at openinfra.dev/summit ! Cheers, Helena [1] http://openinfra.dev/summit-schedule [2] http://openinfra.dev/summit [3] https://openinfra.dev/summit/registration -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Feb 8 21:04:00 2023 From: scott.little at windriver.com (Scott Little) Date: Wed, 8 Feb 2023 16:04:00 -0500 Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 Message-ID: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> Several issues have been corrected in the build tools.? We have started a second build attempt on branch r/stx.8.0.? If all goes well, we should have a build by 06:00 Z on Feb 9. Scott From Juanita.Balaraj at windriver.com Wed Feb 8 22:26:37 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 8 Feb 2023 22:26:37 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 08-02-23 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 ============ 08-February-23 Stx 9.0 Release: -Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing StarlingX 8.0 Release: - February 22nd - StarlingX Features: 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 - Modify the following page to include Stx 8.0 https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 - Need to include Stx 8.0 - AR Ron To add Stx 8.0 in the Version drop-down To automate New Features from the Stx 8.0 RN into the StarlingX Introduction Guide (StarlingX specific) - AR Juanita - Stx 8.0 Release Notes WIP - AR Juanita - events.yaml - Applies only to master and it was implemented in 8.0 and forward... - 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?? - Completed the flattening of the TOC.....Flattening of TOC not being implemented on older branches. Simplified on stx 6.0 / stx 7.0 (makes cherry picks easier) Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 1 Review Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 7 bugs outstanding (2 New Triaged)- The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug 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: - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron - 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 ThalesElero.Cervi at windriver.com Thu Feb 9 11:33:22 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Thu, 9 Feb 2023 11:33:22 +0000 Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 In-Reply-To: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> Message-ID: Hi Scott, Is any of these issues by any chance related to the reason why the stx-openstack helm-chart is not being generated as part of the master/debian/monolithic build? Last build with a stx-openstack helm-chart generated was: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ Since then, I see weird mentions to STX_8.0 pipeline on the build-helm-charts.log.txt for master/debian/monolithic build: 2023-02-08T05:49:21.269Z] + /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh [2023-02-08T05:49:21.269Z] reading /localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf [2023-02-08T05:49:21.269Z] cd /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools [2023-02-08T05:49:21.269Z] sourcing ./import-stx [2023-02-08T05:49:21.820Z] # found primary helm charts: [stx-openstack:stx-openstack-helm-fluxcd] pattern=[stx-openstack-helm-fluxcd] [2023-02-08T05:49:22.071Z] # found extra helm charts: [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] [2023-02-08T05:49:22.071Z] [2023-02-08T05:49:22.071Z] [2023-02-08T05:49:22.071Z] ### [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor [2023-02-08T05:49:22.071Z] ### And it seems that the stx-openstack helm-chart build is being skipped for some reason. If this is one of the issues you mentioned to be already fixed, please let me know. Otherwise, we can raise a Launchpad to track this build issue accordingly since the lack of a helm-chart as a latest_build output currently broke the stx-openstack Sanity Tests pipeline. Thales ________________________________ From: Scott Little Sent: Wednesday, February 8, 2023 6:04 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 Several issues have been corrected in the build tools. We have started a second build attempt on branch r/stx.8.0. If all goes well, we should have a build by 06:00 Z on Feb 9. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Thu Feb 9 15:30:53 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Thu, 9 Feb 2023 15:30:53 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230207T070000Z] results - Feb-9 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Feb-8 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230208T195141Z/outputs/iso/starlingx-intel-x86-64-20230209035855-cd.iso and Helm Charts from the Feb-7 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.6-debian-stable-versioned.tgz Overall Sanity Results: GREEN AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.0%) Failed: 0 (0.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230209 13:01:09 test_ssh_to_hosts PASS 20230209 13:02:52 test_lock_unlock_host PASS 20230209 13:21:59 test_openstack_services_healthy PASS 20230209 13:23:18 test_reapply_stx_openstack_no_change[controller-0] PASS 20230209 13:26:08 test_reapply_stx_openstack_no_change[controller-1] PASS 20230209 13:32:21 test_horizon_create_delete_instance PASS 20230209 13:36:36 test_swact_controllers PASS 20230209 13:44:54 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20230209 13:51:32 test_migrate_vm[tis-centos-guest-live-None] PASS 20230209 13:56:36 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20230209 14:01:07 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS 20230209 14:05:35 test_evacuate_vms PASS 20230209 14:38:51 test_system_coredumps_and_crashes[core_dumps] PASS 20230209 14:39:07 test_system_coredumps_and_crashes[crash_reports] PASS 20230209 14:39:15 test_system_alarms ----------------------------------------------------------------------- This is the first green STX-Openstack sanity on Debian. A quick reminder that, starting next week, the STX-Openstack sanity email will be sent on Tuesdays. More about this can be found here: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013813.html Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Feb 9 18:11:36 2023 From: scott.little at windriver.com (Scott Little) Date: Thu, 9 Feb 2023 13:11:36 -0500 Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 In-Reply-To: References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> Message-ID: Last nights build of r/stx.8.0 failed again, a variation of the prior issue.? As you note, the failure impacts images and helm charts, not the ISO. The problem has been corrected and another build is underway.? ETA is 9pm Eastern. Scott On 2023-02-09 06:33, Cervi, Thales Elero wrote: > Hi Scott, > > Is any of these issues by any chance related to the reason why the > stx-openstack helm-chart is not being generated as part of the > master/debian/monolithic build? > > Last build with a stx-openstack helm-chart generated was: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ > > Since then, I see weird mentions to STX_8.0 pipeline on the > build-helm-charts.log.txt for master/debian/monolithic build: > > 2023-02-08T05:49:21.269Z] + > /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh > > [2023-02-08T05:49:21.269Z] reading > ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf > [2023-02-08T05:49:21.269Z] cd > /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools > [2023-02-08T05:49:21.269Z] sourcing ./import-stx > [2023-02-08T05:49:21.820Z] # found primary helm charts: > [stx-openstack:stx-openstack-helm-fluxcd] > pattern=[stx-openstack-helm-fluxcd] > [2023-02-08T05:49:22.071Z] # found extra helm charts: > [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] > [2023-02-08T05:49:22.071Z] > [2023-02-08T05:49:22.071Z] > [2023-02-08T05:49:22.071Z] ### > [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor > [2023-02-08T05:49:22.071Z] ### > > And it seems that the stx-openstack helm-chart build is being skipped > for some reason. > If this is one of the issues you mentioned to be already fixed, please > let me know. > Otherwise, we can raise a Launchpad to track this build issue > accordingly since the lack of a helm-chart as a latest_build output > currently broke the stx-openstack Sanity Tests pipeline. > > Thales > > > ------------------------------------------------------------------------ > *From:* Scott Little > *Sent:* Wednesday, February 8, 2023 6:04 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 > Several issues have been corrected in the build tools.? We have started > a second build attempt on branch r/stx.8.0.? If all goes well, we should > have a build by 06:00 Z on Feb 9. > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 9 21:58:52 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 9 Feb 2023 21:58:52 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Feb 8, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call February 8, 2023 Standing topics - Build - Main Branch Debian Builds - One build failed on Feb 7; issue is still under investigation; maybe related to cross contamination w/ stx.8.0 - Main Branch CentOS Builds - Last build was green before the builds were stopped - Stopped as of Feb 7. - Email sent to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013817.html - stx.8.0 RC Builds - Initial build failed; issue is understood. It's related to Jenkins pipelines as this is the first release branch using this mechanism. - Fix in progress and planning another build attempt at 2pm EST. - Builds will be on demand - stx.6.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Sanity - Debian Main Branch Sanity - Last sanity email sent on Feb 8: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013818.html - Status: Green for both SX & DX - stx-openstack Debian Main Branch Sanity - Last sanity email sent on Feb 3: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013799.html - Status: Yellow - LP: https://bugs.launchpad.net/starlingx/+bug/2003813 addressed as of Feb 6 before the branch creation - Expecting another sanity report on Thurs Feb 9 - should be green given the above LP was merged - Starting next week, stx-opentack sanity will move to Monday. Reports to be sent out on Tuesday. - stx.8.0 Sanity - Should have an RC build by EOD Feb 8 - Plan in place to run platform & stx-openstack sanity on the RC build later this week. - Plan in place to run extended regression starting Monday Feb 13 - Gerrit Reviews in Need of Attention - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 18: Some activity in the review as of Jan 15 - Feb 1: Alternative fix proposed on Jan 18; waiting for ScottK's review - 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 - Zuul Issues - Support for py27 was removed from zuul earlier this week. This resulted in code failing to merge. - This is now addressed by updating the stx zuul jobs to remove the py27 jobs - We will need to do this for other release branches if there are code merges to those branches - Bruce Jones returns to StarlingX - Bruce is now part of WR!! - Welcome back Bruce! - Release Status - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Upcoming Milestones: - Milestone-3: Jan 18 >> Jan 25 >> Jan 27 / Actual: Jan 31 - Feature Test Complete: Jan 25 >> Jan 31 >> Feb 2 / Actual: Feb 2 - Regression Test Complete: Jan 25 / Actual: Jan 30 - RC1 (branch creation / stx.8.0 builds): Feb 1 >> Feb 6 - Branch Created: https://review.opendev.org/q/projects:starlingx+branch:r/stx.8.0 - RC builds in progress - Final Regression Complete: Feb 15 - Plan in place. Waiting for stx.8.0 rc build - Release: Feb 22 - Feature Status: - All features are complete - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - All tagged bugs have been addressed - Release Notes - Started. Review to be sent on Feb 10. - Risks - stx-openstack sanity >> trending in the right direction - stx.9.0 - Feature proposals starting to get added to the tracking spreadsheet. - Call to community members/PLs to continue adding their proposals. - Would like to have the majority of features proposed by the March virtual PTG - Dates: March 28-29 - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing ARs from Previous Meetings - None Open Requests for Help - StarlingX Support on ARM - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013819.html - Not currently supported on StarlingX, but should be more doable with the move to Debian and the yocto kernel - ARM Support would definitely require work to support, including build system support - A few years ago MarkA and Greg did some prototype work on orange-pie - MarkA will respond to the mailing list and further the conversation - Perhaps the reporter is interested in doing some work towards this - Would be ideal to invite the reporter to the PTG or an upcoming community call - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; not investigated yet; team focused on stx.8.0 and openstack sanity. - Reached out to reporter, so they have a view of the status. They're fine to wait until the team has bandwidth - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss documenting community tested hardware with the TSC From scott.little at windriver.com Fri Feb 10 15:05:15 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 10 Feb 2023 10:05:15 -0500 Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 is ready! In-Reply-To: References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> Message-ID: <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> We have a good build of r/stx.8.0 Scott On 2023-02-09 13:11, Scott Little wrote: > Last nights build of r/stx.8.0 failed again, a variation of the prior > issue.? As you note, the failure impacts images and helm charts, not > the ISO. > > The problem has been corrected and another build is underway.? ETA is > 9pm Eastern. > > Scott > > > > On 2023-02-09 06:33, Cervi, Thales Elero wrote: >> Hi Scott, >> >> Is any of these issues by any chance related to the reason why the >> stx-openstack helm-chart is not being generated as part of the >> master/debian/monolithic build? >> >> Last build with a stx-openstack helm-chart generated was: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >> >> Since then, I see weird mentions to STX_8.0 pipeline on the >> build-helm-charts.log.txt for master/debian/monolithic build: >> >> 2023-02-08T05:49:21.269Z] + >> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >> >> >> [2023-02-08T05:49:21.269Z] reading >> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >> [2023-02-08T05:49:21.269Z] cd >> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >> [2023-02-08T05:49:21.820Z] # found primary helm charts: >> [stx-openstack:stx-openstack-helm-fluxcd] >> pattern=[stx-openstack-helm-fluxcd] >> [2023-02-08T05:49:22.071Z] # found extra helm charts: >> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >> [2023-02-08T05:49:22.071Z] >> [2023-02-08T05:49:22.071Z] >> [2023-02-08T05:49:22.071Z] ### >> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >> [2023-02-08T05:49:22.071Z] ### >> >> And it seems that the stx-openstack helm-chart build is being skipped >> for some reason. >> If this is one of the issues you mentioned to be already fixed, >> please let me know. >> Otherwise, we can raise a Launchpad to track this build issue >> accordingly since the lack of a helm-chart as a latest_build output >> currently broke the stx-openstack Sanity Tests pipeline. >> >> Thales >> >> >> ------------------------------------------------------------------------ >> *From:* Scott Little >> *Sent:* Wednesday, February 8, 2023 6:04 PM >> *To:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >> Several issues have been corrected in the build tools.? We have started >> a second build attempt on branch r/stx.8.0.? If all goes well, we should >> have a build by 06:00 Z on Feb 9. >> >> Scott >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Fri Feb 10 15:06:29 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Fri, 10 Feb 2023 16:06:29 +0100 Subject: [Starlingx-discuss] - add new core to rook-ceph repo In-Reply-To: References: Message-ID: <07F82084-DA8B-4EC5-B91A-242CE2AE746A@openstack.org> Hi Flavio and All, Thank you for taking the topic to the StarlingX mailing list! I corrected the mailing list address as accidentally the ?starlingx-discuss-owners? list was used, which addresses the mailing list moderators. As a reminder, the address of the starlingx-discuss mailing list is: starlingx-discuss at lists.starlingx.io Once the existing core reviewers agreed on the proposal, Daian can be added to the group in Gerrit by any core reviewer in the group. Please let me know if I can help with anything else. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 10, 2023, at 16:00, Miller, Frank wrote: > > I support having Daian added as a Core to this repo as he is a member of the team working on storage. I also request that Cores no longer with StarlingX be removed: Sabeel Ansari, Chen Haochuan, Austin Sun. > > Frank > > From: Peres, Flavio Luis > Sent: Friday, February 10, 2023 9:20 AM > To: starlingx-discuss-owner at lists.starlingx.io > Cc: Miller, Frank ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com; Voiculeasa, Dan > Subject: [Starlingx-discuss] - add new core to rook-ceph repo > > Hi, > > Could you please add Daian as a core on the rook-ceph repo: https://review.opendev.org/admin/groups/c94564620ec9d3284ecd2abc67884d200cd9d843,members > > Daian was the dev who implemented rook-ceph. He is indicated to be the Core reviewer on this repo. > > Thanks > > Flavio Peres > Software Development Manager > Campinas, BR > > > > From: starlingx-discuss-owner at lists.starlingx.io > Sent: Wednesday, November 17, 2021 2:50 PM > To: Peres, Flavio Luis > Subject: Your message to Starlingx-discuss awaits moderator approval > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Your mail to 'Starlingx-discuss' with the subject > > RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20211117T032111Z > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. If you would like to cancel > this posting, please visit the following URL: > > http://lists.starlingx.io/cgi-bin/mailman/confirm/starlingx-discuss/70f579fa625eb7487b4baa41761d974f15bcd815 > > From Dan.Voiculeasa at windriver.com Fri Feb 10 15:51:51 2023 From: Dan.Voiculeasa at windriver.com (Voiculeasa, Dan) Date: Fri, 10 Feb 2023 15:51:51 +0000 Subject: [Starlingx-discuss] - add new core to rook-ceph repo In-Reply-To: <07F82084-DA8B-4EC5-B91A-242CE2AE746A@openstack.org> References: <07F82084-DA8B-4EC5-B91A-242CE2AE746A@openstack.org> Message-ID: +1 Looked at the activity of Austin and Haochuan and Sabeel, looks empty will remove them. There are only 2 active cores now. Thanks, Dan Voiculeasa ________________________________ From: Ildiko Vancsa Sent: Friday, February 10, 2023 5:06 PM To: Miller, Frank Cc: Peres, Flavio Luis ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com ; StarlingX ML Subject: Re: [Starlingx-discuss] - add new core to rook-ceph repo 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 Flavio and All, Thank you for taking the topic to the StarlingX mailing list! I corrected the mailing list address as accidentally the ?starlingx-discuss-owners? list was used, which addresses the mailing list moderators. As a reminder, the address of the starlingx-discuss mailing list is: starlingx-discuss at lists.starlingx.io Once the existing core reviewers agreed on the proposal, Daian can be added to the group in Gerrit by any core reviewer in the group. Please let me know if I can help with anything else. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 10, 2023, at 16:00, Miller, Frank wrote: > > I support having Daian added as a Core to this repo as he is a member of the team working on storage. I also request that Cores no longer with StarlingX be removed: Sabeel Ansari, Chen Haochuan, Austin Sun. > > Frank > > From: Peres, Flavio Luis > Sent: Friday, February 10, 2023 9:20 AM > To: starlingx-discuss-owner at lists.starlingx.io > Cc: Miller, Frank ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com; Voiculeasa, Dan > Subject: [Starlingx-discuss] - add new core to rook-ceph repo > > Hi, > > Could you please add Daian as a core on the rook-ceph repo: https://review.opendev.org/admin/groups/c94564620ec9d3284ecd2abc67884d200cd9d843,members > > Daian was the dev who implemented rook-ceph. He is indicated to be the Core reviewer on this repo. > > Thanks > > Flavio Peres > Software Development Manager > Campinas, BR > > > > From: starlingx-discuss-owner at lists.starlingx.io > Sent: Wednesday, November 17, 2021 2:50 PM > To: Peres, Flavio Luis > Subject: Your message to Starlingx-discuss awaits moderator approval > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Your mail to 'Starlingx-discuss' with the subject > > RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20211117T032111Z > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. If you would like to cancel > this posting, please visit the following URL: > > http://lists.starlingx.io/cgi-bin/mailman/confirm/starlingx-discuss/70f579fa625eb7487b4baa41761d974f15bcd815 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Feb 10 18:25:27 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 10 Feb 2023 13:25:27 -0500 Subject: [Starlingx-discuss] CENGN build of r/stx.8.0 is ^NOT^ ready! In-Reply-To: <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> Message-ID: <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> Sorry folks,? the last r/stx/8/0 build was invalid.? One more build configuration fix and we'll try again. ETA: ??? 10 pm Eastern expected output URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230210T181726Z Scott On 2023-02-10 10:05, Scott Little wrote: > > We have a good build of r/stx.8.0 > > > Scott > > > > On 2023-02-09 13:11, Scott Little wrote: >> Last nights build of r/stx.8.0 failed again, a variation of the prior >> issue.? As you note, the failure impacts images and helm charts, not >> the ISO. >> >> The problem has been corrected and another build is underway.? ETA is >> 9pm Eastern. >> >> Scott >> >> >> >> On 2023-02-09 06:33, Cervi, Thales Elero wrote: >>> Hi Scott, >>> >>> Is any of these issues by any chance related to the reason why the >>> stx-openstack helm-chart is not being generated as part of the >>> master/debian/monolithic build? >>> >>> Last build with a stx-openstack helm-chart generated was: >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >>> >>> Since then, I see weird mentions to STX_8.0 pipeline on the >>> build-helm-charts.log.txt for master/debian/monolithic build: >>> >>> 2023-02-08T05:49:21.269Z] + >>> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >>> >>> >>> [2023-02-08T05:49:21.269Z] reading >>> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >>> [2023-02-08T05:49:21.269Z] cd >>> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >>> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >>> [2023-02-08T05:49:21.820Z] # found primary helm charts: >>> [stx-openstack:stx-openstack-helm-fluxcd] >>> pattern=[stx-openstack-helm-fluxcd] >>> [2023-02-08T05:49:22.071Z] # found extra helm charts: >>> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >>> [2023-02-08T05:49:22.071Z] >>> [2023-02-08T05:49:22.071Z] >>> [2023-02-08T05:49:22.071Z] ### >>> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >>> [2023-02-08T05:49:22.071Z] ### >>> >>> And it seems that the stx-openstack helm-chart build is being >>> skipped for some reason. >>> If this is one of the issues you mentioned to be already fixed, >>> please let me know. >>> Otherwise, we can raise a Launchpad to track this build issue >>> accordingly since the lack of a helm-chart as a latest_build output >>> currently broke the stx-openstack Sanity Tests pipeline. >>> >>> Thales >>> >>> >>> ------------------------------------------------------------------------ >>> *From:* Scott Little >>> *Sent:* Wednesday, February 8, 2023 6:04 PM >>> *To:* starlingx-discuss at lists.starlingx.io >>> >>> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >>> Several issues have been corrected in the build tools.? We have started >>> a second build attempt on branch r/stx.8.0.? If all goes well, we >>> should >>> have a build by 06:00 Z on Feb 9. >>> >>> Scott >>> >>> >>> _______________________________________________ >>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Feb 10 22:52:32 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 10 Feb 2023 17:52:32 -0500 Subject: [Starlingx-discuss] [Build] 5th build attempt of r/stx.8.0 build failed on circular dependency In-Reply-To: <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> Message-ID: <9eebc196-69dd-0728-1a0f-301c8246286a@windriver.com> **14:19:54* 2023-02-10 19:19:54,585 - dsc_depend - DEBUG: Scan pkgs meta info for circular dependency. *14:19:54* 2023-02-10 19:19:54,589 - dsc_depend - DEBUG: Scan pkgs meta info for Simple dependency. *14:19:54* 2023-02-10 19:19:54,593 - dsc_depend - DEBUG: Scan pkgs meta info for circular dependency. *14:19:54* 2023-02-10 19:19:54,601 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lsb/lsb_11.1.0.stx.1.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python3.9/python3.9_3.9.2-1.stx.1.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/linux/linux_5.10.162-1.stx.31.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/net-tools/net-tools_1.60+git20181103.0eebece-1.stx.1.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/systemd/systemd_247.3-7.stx.8.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/setuptools/setuptools_52.0.0-4.stx.1.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/dh-python/dh-python_4.20201102+nmu1.stx.2.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/openldap/openldap_2.4.57+dfsg-3+deb11u1.stx.9.dsc', '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lvm2/lvm2_2.03.11-2.stx.2.dsc'} 14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstacksdk/python-openstacksdk_0.50.0-6.stx.1.dsc'} *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstackclient/python-openstackclient_5.4.0-4.stx.3.dsc'} *14:19:54* 2023-02-10 19:19:54,606 - dsc_depend - ERROR: There are unexpected circular dependency. *14:19:54* Traceback (most recent call last): *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 2034, in *14:19:54* build_controller.build_all(layers=layers, build_types=build_types, packages=packages) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1513, in build_all *14:19:54* self.build_layers(layers=layers, build_types=build_types, packages=packages) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1637, in build_layers *14:19:54* self.build_layer(layer=layer, build_types=build_types, packages=packages) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1613, in build_layer *14:19:54* self.build_layer_and_build_types(layer=layer, build_types=build_types, packages=packages) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1598, in build_layer_and_build_types *14:19:54* self.build_layer_and_build_type(layer=layer, build_type=build_type, packages=packages) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1564, in build_layer_and_build_type *14:19:54* self.build_packages(layer_pkg_dirs, pkg_dirs, layer, word, build_type=build_type) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1824, in build_packages *14:19:54* self.run_build_loop(layer_pkgdir_dscs, target_pkgdir_dscs, layer, build_type=build_type) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1299, in run_build_loop *14:19:54* deps_resolver = dsc_depend.Dsc_build_order(dsc_list_file, dscs_list, ds_logger) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 935, in __init__ *14:19:54* super().__init__(logger, self.meta_info, circular_conf_file) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 520, in __init__ *14:19:54* self.__grouping(meta_info) *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 823, in __grouping *14:19:54* raise Exception('UNEXPECTED CIRCULAR DEPENDENCY.') *14:19:54* Exception: UNEXPECTED CIRCULAR DEPENDENCY. *14:19:54* command terminated with exit code 1 *14:19:54* *14:19:54* *14:19:54* ### *14:19:54* ### Failed to build packages after 3 iterations *14:19:54* ### *14:19:54* On 2023-02-10 13:25, Scott Little wrote: > Sorry folks,? the last r/stx/8/0 build was invalid.? One more build > configuration fix and we'll try again. > > ETA: > ??? 10 pm Eastern > > expected output URL: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230210T181726Z > > > Scott > > > On 2023-02-10 10:05, Scott Little wrote: >> >> We have a good build of r/stx.8.0 >> >> >> Scott >> >> >> >> On 2023-02-09 13:11, Scott Little wrote: >>> Last nights build of r/stx.8.0 failed again, a variation of the >>> prior issue.? As you note, the failure impacts images and helm >>> charts, not the ISO. >>> >>> The problem has been corrected and another build is underway.? ETA >>> is 9pm Eastern. >>> >>> Scott >>> >>> >>> >>> On 2023-02-09 06:33, Cervi, Thales Elero wrote: >>>> Hi Scott, >>>> >>>> Is any of these issues by any chance related to the reason why the >>>> stx-openstack helm-chart is not being generated as part of the >>>> master/debian/monolithic build? >>>> >>>> Last build with a stx-openstack helm-chart generated was: >>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >>>> >>>> Since then, I see weird mentions to STX_8.0 pipeline on the >>>> build-helm-charts.log.txt for master/debian/monolithic build: >>>> >>>> 2023-02-08T05:49:21.269Z] + >>>> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >>>> >>>> >>>> [2023-02-08T05:49:21.269Z] reading >>>> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >>>> [2023-02-08T05:49:21.269Z] cd >>>> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >>>> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >>>> [2023-02-08T05:49:21.820Z] # found primary helm charts: >>>> [stx-openstack:stx-openstack-helm-fluxcd] >>>> pattern=[stx-openstack-helm-fluxcd] >>>> [2023-02-08T05:49:22.071Z] # found extra helm charts: >>>> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >>>> [2023-02-08T05:49:22.071Z] >>>> [2023-02-08T05:49:22.071Z] >>>> [2023-02-08T05:49:22.071Z] ### >>>> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >>>> [2023-02-08T05:49:22.071Z] ### >>>> >>>> And it seems that the stx-openstack helm-chart build is being >>>> skipped for some reason. >>>> If this is one of the issues you mentioned to be already fixed, >>>> please let me know. >>>> Otherwise, we can raise a Launchpad to track this build issue >>>> accordingly since the lack of a helm-chart as a latest_build output >>>> currently broke the stx-openstack Sanity Tests pipeline. >>>> >>>> Thales >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> *From:* Scott Little >>>> *Sent:* Wednesday, February 8, 2023 6:04 PM >>>> *To:* starlingx-discuss at lists.starlingx.io >>>> >>>> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >>>> Several issues have been corrected in the build tools.? We have >>>> started >>>> a second build attempt on branch r/stx.8.0.? If all goes well, we >>>> should >>>> have a build by 06:00 Z on Feb 9. >>>> >>>> Scott >>>> >>>> >>>> _______________________________________________ >>>> 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sat Feb 11 01:23:27 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 10 Feb 2023 20:23:27 -0500 Subject: [Starlingx-discuss] [Build] 5th build attempt of r/stx.8.0 build failed on circular dependency In-Reply-To: <9eebc196-69dd-0728-1a0f-301c8246286a@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> <9eebc196-69dd-0728-1a0f-301c8246286a@windriver.com> Message-ID: <3aec28f9-8251-77c9-7103-4179d743fd6f@windriver.com> Found a manifest issue.? Master branch content leaked into the build of the r/stx.8.0 branch. I have fixed? the r/stx.8.0 manifest, and restarted the r/stx.8.0 build. ETA: ? ? 6am Eastern. expected output URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230211T011643Z The master branch build will be delayed till 6 am.? The master branch might or might not have a circular dependency issue as I noted previously.? If it does, the probable trigger was https://review.opendev.org/c/starlingx/integ/+/871349 Scott On 2023-02-10 17:52, Scott Little wrote: > **14:19:54* 2023-02-10 19:19:54,585 - dsc_depend - > DEBUG: Scan pkgs meta info for circular dependency. > *14:19:54* 2023-02-10 19:19:54,589 - dsc_depend - > DEBUG: Scan pkgs meta info for Simple dependency. > *14:19:54* 2023-02-10 19:19:54,593 - dsc_depend - > DEBUG: Scan pkgs meta info for circular dependency. > *14:19:54* 2023-02-10 19:19:54,601 - dsc_depend - > DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* 2023-02-10 > 19:19:54,603 - dsc_depend - ERROR: Circular > dependency: > {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lsb/lsb_11.1.0.stx.1.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python3.9/python3.9_3.9.2-1.stx.1.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/linux/linux_5.10.162-1.stx.31.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/net-tools/net-tools_1.60+git20181103.0eebece-1.stx.1.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/systemd/systemd_247.3-7.stx.8.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/setuptools/setuptools_52.0.0-4.stx.1.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/dh-python/dh-python_4.20201102+nmu1.stx.2.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/openldap/openldap_2.4.57+dfsg-3+deb11u1.stx.9.dsc', > '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lvm2/lvm2_2.03.11-2.stx.2.dsc'} > 14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. > *14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstacksdk/python-openstacksdk_0.50.0-6.stx.1.dsc'} > *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. > *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstackclient/python-openstackclient_5.4.0-4.stx.3.dsc'} > *14:19:54* 2023-02-10 19:19:54,606 - dsc_depend - ERROR: There are unexpected circular dependency. > *14:19:54* Traceback (most recent call last): > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 2034, in > *14:19:54* build_controller.build_all(layers=layers, build_types=build_types, packages=packages) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1513, in build_all > *14:19:54* self.build_layers(layers=layers, build_types=build_types, packages=packages) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1637, in build_layers > *14:19:54* self.build_layer(layer=layer, build_types=build_types, packages=packages) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1613, in build_layer > *14:19:54* self.build_layer_and_build_types(layer=layer, build_types=build_types, packages=packages) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1598, in build_layer_and_build_types > *14:19:54* self.build_layer_and_build_type(layer=layer, build_type=build_type, packages=packages) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1564, in build_layer_and_build_type > *14:19:54* self.build_packages(layer_pkg_dirs, pkg_dirs, layer, word, build_type=build_type) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1824, in build_packages > *14:19:54* self.run_build_loop(layer_pkgdir_dscs, target_pkgdir_dscs, layer, build_type=build_type) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1299, in run_build_loop > *14:19:54* deps_resolver = dsc_depend.Dsc_build_order(dsc_list_file, dscs_list, ds_logger) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 935, in __init__ > *14:19:54* super().__init__(logger, self.meta_info, circular_conf_file) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 520, in __init__ > *14:19:54* self.__grouping(meta_info) > *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 823, in __grouping > *14:19:54* raise Exception('UNEXPECTED CIRCULAR DEPENDENCY.') > *14:19:54* Exception: UNEXPECTED CIRCULAR DEPENDENCY. > *14:19:54* command terminated with exit code 1 > *14:19:54* > *14:19:54* > *14:19:54* ### > *14:19:54* ### Failed to build packages after 3 iterations > *14:19:54* ### > *14:19:54* > > On 2023-02-10 13:25, Scott Little wrote: >> Sorry folks,? the last r/stx/8/0 build was invalid.? One more build >> configuration fix and we'll try again. >> >> ETA: >> ??? 10 pm Eastern >> >> expected output URL: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230210T181726Z >> >> >> Scott >> >> >> On 2023-02-10 10:05, Scott Little wrote: >>> >>> We have a good build of r/stx.8.0 >>> >>> >>> Scott >>> >>> >>> >>> On 2023-02-09 13:11, Scott Little wrote: >>>> Last nights build of r/stx.8.0 failed again, a variation of the >>>> prior issue.? As you note, the failure impacts images and helm >>>> charts, not the ISO. >>>> >>>> The problem has been corrected and another build is underway.? ETA >>>> is 9pm Eastern. >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2023-02-09 06:33, Cervi, Thales Elero wrote: >>>>> Hi Scott, >>>>> >>>>> Is any of these issues by any chance related to the reason why the >>>>> stx-openstack helm-chart is not being generated as part of the >>>>> master/debian/monolithic build? >>>>> >>>>> Last build with a stx-openstack helm-chart generated was: >>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >>>>> >>>>> Since then, I see weird mentions to STX_8.0 pipeline on the >>>>> build-helm-charts.log.txt for master/debian/monolithic build: >>>>> >>>>> 2023-02-08T05:49:21.269Z] + >>>>> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >>>>> >>>>> >>>>> [2023-02-08T05:49:21.269Z] reading >>>>> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >>>>> [2023-02-08T05:49:21.269Z] cd >>>>> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >>>>> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >>>>> [2023-02-08T05:49:21.820Z] # found primary helm charts: >>>>> [stx-openstack:stx-openstack-helm-fluxcd] >>>>> pattern=[stx-openstack-helm-fluxcd] >>>>> [2023-02-08T05:49:22.071Z] # found extra helm charts: >>>>> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >>>>> [2023-02-08T05:49:22.071Z] >>>>> [2023-02-08T05:49:22.071Z] >>>>> [2023-02-08T05:49:22.071Z] ### >>>>> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >>>>> [2023-02-08T05:49:22.071Z] ### >>>>> >>>>> And it seems that the stx-openstack helm-chart build is being >>>>> skipped for some reason. >>>>> If this is one of the issues you mentioned to be already fixed, >>>>> please let me know. >>>>> Otherwise, we can raise a Launchpad to track this build issue >>>>> accordingly since the lack of a helm-chart as a latest_build >>>>> output currently broke the stx-openstack Sanity Tests pipeline. >>>>> >>>>> Thales >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Scott Little >>>>> *Sent:* Wednesday, February 8, 2023 6:04 PM >>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>> >>>>> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >>>>> Several issues have been corrected in the build tools.? We have >>>>> started >>>>> a second build attempt on branch r/stx.8.0.? If all goes well, we >>>>> should >>>>> have a build by 06:00 Z on Feb 9. >>>>> >>>>> Scott >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sat Feb 11 05:11:04 2023 From: scott.little at windriver.com (Scott Little) Date: Sat, 11 Feb 2023 00:11:04 -0500 Subject: [Starlingx-discuss] [Build] Another build attempt of r/stx.8.0 In-Reply-To: <3aec28f9-8251-77c9-7103-4179d743fd6f@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> <9eebc196-69dd-0728-1a0f-301c8246286a@windriver.com> <3aec28f9-8251-77c9-7103-4179d743fd6f@windriver.com> Message-ID: <2299ca3f-9156-c6b2-093c-1eca4f41e2d3@windriver.com> Trying again after full wipe of prior damaged build environment. ETA: ? ? 10am Eastern. expected output URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/ 20230211T045208Z On 2023-02-10 20:23, Scott Little wrote: > Found a manifest issue.? Master branch content leaked into the build > of the r/stx.8.0 branch. > > I have fixed? the r/stx.8.0 manifest, and restarted the r/stx.8.0 build. > > ETA: > ? ? 6am Eastern. > > expected output URL: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/ > 20230211T011643Z > The master branch build will be delayed till 6 am.? The master branch > might or might not have a circular dependency issue as I noted > previously.? If it does, the probable trigger was > https://review.opendev.org/c/starlingx/integ/+/871349 > > Scott > > On 2023-02-10 17:52, Scott Little wrote: >> **14:19:54* 2023-02-10 19:19:54,585 - dsc_depend - >> DEBUG: Scan pkgs meta info for circular dependency. >> *14:19:54* 2023-02-10 19:19:54,589 - dsc_depend - >> DEBUG: Scan pkgs meta info for Simple dependency. >> *14:19:54* 2023-02-10 19:19:54,593 - dsc_depend - >> DEBUG: Scan pkgs meta info for circular dependency. >> *14:19:54* 2023-02-10 19:19:54,601 - dsc_depend - >> DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* 2023-02-10 >> 19:19:54,603 - dsc_depend - ERROR: Circular >> dependency: >> {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lsb/lsb_11.1.0.stx.1.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python3.9/python3.9_3.9.2-1.stx.1.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/linux/linux_5.10.162-1.stx.31.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/net-tools/net-tools_1.60+git20181103.0eebece-1.stx.1.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/systemd/systemd_247.3-7.stx.8.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/setuptools/setuptools_52.0.0-4.stx.1.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/dh-python/dh-python_4.20201102+nmu1.stx.2.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/openldap/openldap_2.4.57+dfsg-3+deb11u1.stx.9.dsc', >> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lvm2/lvm2_2.03.11-2.stx.2.dsc'} >> 14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. >> *14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstacksdk/python-openstacksdk_0.50.0-6.stx.1.dsc'} >> *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. >> *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstackclient/python-openstackclient_5.4.0-4.stx.3.dsc'} >> *14:19:54* 2023-02-10 19:19:54,606 - dsc_depend - ERROR: There are unexpected circular dependency. >> *14:19:54* Traceback (most recent call last): >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 2034, in >> *14:19:54* build_controller.build_all(layers=layers, build_types=build_types, packages=packages) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1513, in build_all >> *14:19:54* self.build_layers(layers=layers, build_types=build_types, packages=packages) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1637, in build_layers >> *14:19:54* self.build_layer(layer=layer, build_types=build_types, packages=packages) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1613, in build_layer >> *14:19:54* self.build_layer_and_build_types(layer=layer, build_types=build_types, packages=packages) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1598, in build_layer_and_build_types >> *14:19:54* self.build_layer_and_build_type(layer=layer, build_type=build_type, packages=packages) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1564, in build_layer_and_build_type >> *14:19:54* self.build_packages(layer_pkg_dirs, pkg_dirs, layer, word, build_type=build_type) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1824, in build_packages >> *14:19:54* self.run_build_loop(layer_pkgdir_dscs, target_pkgdir_dscs, layer, build_type=build_type) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1299, in run_build_loop >> *14:19:54* deps_resolver = dsc_depend.Dsc_build_order(dsc_list_file, dscs_list, ds_logger) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 935, in __init__ >> *14:19:54* super().__init__(logger, self.meta_info, circular_conf_file) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 520, in __init__ >> *14:19:54* self.__grouping(meta_info) >> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 823, in __grouping >> *14:19:54* raise Exception('UNEXPECTED CIRCULAR DEPENDENCY.') >> *14:19:54* Exception: UNEXPECTED CIRCULAR DEPENDENCY. >> *14:19:54* command terminated with exit code 1 >> *14:19:54* >> *14:19:54* >> *14:19:54* ### >> *14:19:54* ### Failed to build packages after 3 iterations >> *14:19:54* ### >> *14:19:54* >> >> On 2023-02-10 13:25, Scott Little wrote: >>> Sorry folks,? the last r/stx/8/0 build was invalid.? One more build >>> configuration fix and we'll try again. >>> >>> ETA: >>> ??? 10 pm Eastern >>> >>> expected output URL: >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230210T181726Z >>> >>> >>> Scott >>> >>> >>> On 2023-02-10 10:05, Scott Little wrote: >>>> >>>> We have a good build of r/stx.8.0 >>>> >>>> >>>> Scott >>>> >>>> >>>> >>>> On 2023-02-09 13:11, Scott Little wrote: >>>>> Last nights build of r/stx.8.0 failed again, a variation of the >>>>> prior issue. As you note, the failure impacts images and helm >>>>> charts, not the ISO. >>>>> >>>>> The problem has been corrected and another build is underway.? ETA >>>>> is 9pm Eastern. >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> On 2023-02-09 06:33, Cervi, Thales Elero wrote: >>>>>> Hi Scott, >>>>>> >>>>>> Is any of these issues by any chance related to the reason why >>>>>> the stx-openstack helm-chart is not being generated as part of >>>>>> the master/debian/monolithic build? >>>>>> >>>>>> Last build with a stx-openstack helm-chart generated was: >>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >>>>>> >>>>>> Since then, I see weird mentions to STX_8.0 pipeline on the >>>>>> build-helm-charts.log.txt for master/debian/monolithic build: >>>>>> >>>>>> 2023-02-08T05:49:21.269Z] + >>>>>> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >>>>>> >>>>>> >>>>>> [2023-02-08T05:49:21.269Z] reading >>>>>> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >>>>>> [2023-02-08T05:49:21.269Z] cd >>>>>> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >>>>>> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >>>>>> [2023-02-08T05:49:21.820Z] # found primary helm charts: >>>>>> [stx-openstack:stx-openstack-helm-fluxcd] >>>>>> pattern=[stx-openstack-helm-fluxcd] >>>>>> [2023-02-08T05:49:22.071Z] # found extra helm charts: >>>>>> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >>>>>> [2023-02-08T05:49:22.071Z] >>>>>> [2023-02-08T05:49:22.071Z] >>>>>> [2023-02-08T05:49:22.071Z] ### >>>>>> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >>>>>> [2023-02-08T05:49:22.071Z] ### >>>>>> >>>>>> And it seems that the stx-openstack helm-chart build is being >>>>>> skipped for some reason. >>>>>> If this is one of the issues you mentioned to be already fixed, >>>>>> please let me know. >>>>>> Otherwise, we can raise a Launchpad to track this build issue >>>>>> accordingly since the lack of a helm-chart as a latest_build >>>>>> output currently broke the stx-openstack Sanity Tests pipeline. >>>>>> >>>>>> Thales >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Scott Little >>>>>> *Sent:* Wednesday, February 8, 2023 6:04 PM >>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >>>>>> Several issues have been corrected in the build tools.? We have >>>>>> started >>>>>> a second build attempt on branch r/stx.8.0.? If all goes well, we >>>>>> should >>>>>> have a build by 06:00 Z on Feb 9. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> >>> >>> >>> _______________________________________________ >>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sun Feb 12 00:29:47 2023 From: scott.little at windriver.com (Scott Little) Date: Sat, 11 Feb 2023 19:29:47 -0500 Subject: [Starlingx-discuss] [Build] Another build attempt of r/stx.8.0 In-Reply-To: <2299ca3f-9156-c6b2-093c-1eca4f41e2d3@windriver.com> References: <4978d68e-1191-8495-854e-11a71ba816f5@windriver.com> <636f7180-3c92-b1cc-ad42-7457a0f4dabf@windriver.com> <3e824a73-6aae-0969-70a2-5b5be7137a68@windriver.com> <9eebc196-69dd-0728-1a0f-301c8246286a@windriver.com> <3aec28f9-8251-77c9-7103-4179d743fd6f@windriver.com> <2299ca3f-9156-c6b2-093c-1eca4f41e2d3@windriver.com> Message-ID: <7fc0461c-e8fa-396b-25cf-64980888de13@windriver.com> We have a good build at last. https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/stx.8.0/debian/monolithic/20230211T045208Z/ Scott On 2023-02-11 00:11, Scott Little wrote: > Trying again after full wipe of prior damaged build environment. > > ETA: > ? ? 10am Eastern. > > expected output URL: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/ > 20230211T045208Z > On 2023-02-10 20:23, Scott Little wrote: >> Found a manifest issue.? Master branch content leaked into the build >> of the r/stx.8.0 branch. >> >> I have fixed? the r/stx.8.0 manifest, and restarted the r/stx.8.0 build. >> >> ETA: >> ? ? 6am Eastern. >> >> expected output URL: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/ >> 20230211T011643Z >> The master branch build will be delayed till 6 am.? The master branch >> might or might not have a circular dependency issue as I noted >> previously.? If it does, the probable trigger was >> https://review.opendev.org/c/starlingx/integ/+/871349 >> >> Scott >> >> On 2023-02-10 17:52, Scott Little wrote: >>> **14:19:54* 2023-02-10 19:19:54,585 - dsc_depend - >>> DEBUG: Scan pkgs meta info for circular dependency. >>> *14:19:54* 2023-02-10 19:19:54,589 - dsc_depend - >>> DEBUG: Scan pkgs meta info for Simple dependency. >>> *14:19:54* 2023-02-10 19:19:54,593 - dsc_depend - >>> DEBUG: Scan pkgs meta info for circular dependency. >>> *14:19:54* 2023-02-10 19:19:54,601 - dsc_depend - >>> DEBUG: CIRCULAR DEPENDENCY DETECTED. *14:19:54* >>> 2023-02-10 19:19:54,603 - dsc_depend - ERROR: >>> Circular dependency: >>> {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lsb/lsb_11.1.0.stx.1.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python3.9/python3.9_3.9.2-1.stx.1.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/linux/linux_5.10.162-1.stx.31.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/net-tools/net-tools_1.60+git20181103.0eebece-1.stx.1.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/systemd/systemd_247.3-7.stx.8.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/setuptools/setuptools_52.0.0-4.stx.1.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/dh-python/dh-python_4.20201102+nmu1.stx.2.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/openldap/openldap_2.4.57+dfsg-3+deb11u1.stx.9.dsc', >>> '/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/lvm2/lvm2_2.03.11-2.stx.2.dsc'} >>> 14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. >>> *14:19:54* 2023-02-10 19:19:54,603 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstacksdk/python-openstacksdk_0.50.0-6.stx.1.dsc'} >>> *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - DEBUG: CIRCULAR DEPENDENCY DETECTED. >>> *14:19:54* 2023-02-10 19:19:54,604 - dsc_depend - ERROR: Circular dependency: {'/localdisk/loadbuild/jenkins/rc-stx-8-0-debian/std/python-openstackclient/python-openstackclient_5.4.0-4.stx.3.dsc'} >>> *14:19:54* 2023-02-10 19:19:54,606 - dsc_depend - ERROR: There are unexpected circular dependency. >>> *14:19:54* Traceback (most recent call last): >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 2034, in >>> *14:19:54* build_controller.build_all(layers=layers, build_types=build_types, packages=packages) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1513, in build_all >>> *14:19:54* self.build_layers(layers=layers, build_types=build_types, packages=packages) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1637, in build_layers >>> *14:19:54* self.build_layer(layer=layer, build_types=build_types, packages=packages) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1613, in build_layer >>> *14:19:54* self.build_layer_and_build_types(layer=layer, build_types=build_types, packages=packages) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1598, in build_layer_and_build_types >>> *14:19:54* self.build_layer_and_build_type(layer=layer, build_type=build_type, packages=packages) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1564, in build_layer_and_build_type >>> *14:19:54* self.build_packages(layer_pkg_dirs, pkg_dirs, layer, word, build_type=build_type) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1824, in build_packages >>> *14:19:54* self.run_build_loop(layer_pkgdir_dscs, target_pkgdir_dscs, layer, build_type=build_type) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/build-pkgs", line 1299, in run_build_loop >>> *14:19:54* deps_resolver = dsc_depend.Dsc_build_order(dsc_list_file, dscs_list, ds_logger) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 935, in __init__ >>> *14:19:54* super().__init__(logger, self.meta_info, circular_conf_file) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 520, in __init__ >>> *14:19:54* self.__grouping(meta_info) >>> *14:19:54* File "/localdisk/designer/jenkins/rc-stx-8-0-debian/cgcs-root/build-tools/stx/dsc_depend.py", line 823, in __grouping >>> *14:19:54* raise Exception('UNEXPECTED CIRCULAR DEPENDENCY.') >>> *14:19:54* Exception: UNEXPECTED CIRCULAR DEPENDENCY. >>> *14:19:54* command terminated with exit code 1 >>> *14:19:54* >>> *14:19:54* >>> *14:19:54* ### >>> *14:19:54* ### Failed to build packages after 3 iterations >>> *14:19:54* ### >>> *14:19:54* >>> >>> On 2023-02-10 13:25, Scott Little wrote: >>>> Sorry folks,? the last r/stx/8/0 build was invalid.? One more build >>>> configuration fix and we'll try again. >>>> >>>> ETA: >>>> ??? 10 pm Eastern >>>> >>>> expected output URL: >>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230210T181726Z >>>> >>>> >>>> Scott >>>> >>>> >>>> On 2023-02-10 10:05, Scott Little wrote: >>>>> >>>>> We have a good build of r/stx.8.0 >>>>> >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> On 2023-02-09 13:11, Scott Little wrote: >>>>>> Last nights build of r/stx.8.0 failed again, a variation of the >>>>>> prior issue.? As you note, the failure impacts images and helm >>>>>> charts, not the ISO. >>>>>> >>>>>> The problem has been corrected and another build is underway.? >>>>>> ETA is 9pm Eastern. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> >>>>>> On 2023-02-09 06:33, Cervi, Thales Elero wrote: >>>>>>> Hi Scott, >>>>>>> >>>>>>> Is any of these issues by any chance related to the reason why >>>>>>> the stx-openstack helm-chart is not being generated as part of >>>>>>> the master/debian/monolithic build? >>>>>>> >>>>>>> Last build with a stx-openstack helm-chart generated was: >>>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230207T070000Z/ >>>>>>> >>>>>>> Since then, I see weird mentions to STX_8.0 pipeline on the >>>>>>> build-helm-charts.log.txt for master/debian/monolithic build: >>>>>>> >>>>>>> 2023-02-08T05:49:21.269Z] + >>>>>>> /var/lib/jenkins/workspace/STX_8.0_build_pipelines/parts/build-helm-charts/scripts/build-helm-charts.sh >>>>>>> >>>>>>> >>>>>>> [2023-02-08T05:49:21.269Z] reading >>>>>>> ?/localdisk/designer/jenkins/rc-stx-8-0-debian/build.conf >>>>>>> [2023-02-08T05:49:21.269Z] cd >>>>>>> /home/localdisk/designer/jenkins/rc-stx-8-0-debian/repo/stx-tools >>>>>>> [2023-02-08T05:49:21.269Z] sourcing ./import-stx >>>>>>> [2023-02-08T05:49:21.820Z] # found primary helm charts: >>>>>>> [stx-openstack:stx-openstack-helm-fluxcd] >>>>>>> pattern=[stx-openstack-helm-fluxcd] >>>>>>> [2023-02-08T05:49:22.071Z] # found extra helm charts: >>>>>>> [stx-monitor:stx-monitor-helm] pattern=[stx-*-helm] >>>>>>> [2023-02-08T05:49:22.071Z] >>>>>>> [2023-02-08T05:49:22.071Z] >>>>>>> [2023-02-08T05:49:22.071Z] ### >>>>>>> [2023-02-08T05:49:22.071Z] ### building extra helm chart stx-monitor >>>>>>> [2023-02-08T05:49:22.071Z] ### >>>>>>> >>>>>>> And it seems that the stx-openstack helm-chart build is being >>>>>>> skipped for some reason. >>>>>>> If this is one of the issues you mentioned to be already fixed, >>>>>>> please let me know. >>>>>>> Otherwise, we can raise a Launchpad to track this build issue >>>>>>> accordingly since the lack of a helm-chart as a latest_build >>>>>>> output currently broke the stx-openstack Sanity Tests pipeline. >>>>>>> >>>>>>> Thales >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Scott Little >>>>>>> *Sent:* Wednesday, February 8, 2023 6:04 PM >>>>>>> *To:* starlingx-discuss at lists.starlingx.io >>>>>>> >>>>>>> *Subject:* [Starlingx-discuss] CENGN build of r/stx.8.0 >>>>>>> Several issues have been corrected in the build tools.? We have >>>>>>> started >>>>>>> a second build attempt on branch r/stx.8.0. If all goes well, we >>>>>>> should >>>>>>> have a build by 06:00 Z on Feb 9. >>>>>>> >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Feb 13 17:05:47 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 13 Feb 2023 11:05:47 -0600 Subject: [Starlingx-discuss] Fwd: Virtual PTG March 2023 Team Signup Deadline - LAST CALL! In-Reply-To: References: Message-ID: Hello Everyone, This is your last call to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, March 27th to Friday, March 31st 2023! NOTE: Since we have had the feedback that the Europe+Africa/Americas timeslot is overbooked, we will be extending it beyond the ?normal? size of 4 hour blocks to 5 hour blocks. If you haven't already done so and your team is interested in participating, please complete the survey[1] by February 19th, 2023 at 7:00 UTC. Then make sure to register[2] - it?s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] PTG Registration: https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Feb 14 18:09:31 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 14 Feb 2023 18:09:31 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack R8.0 build ISO [RC 20230211T045208Z] results - Feb-14 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack R8.0 sanity using Feb-11 RC build: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/stx.8.0/debian/monolithic/20230211T045208Z/outputs/iso/starlingx-intel-x86-64-cd.iso and Helm Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/stx.8.0/debian/monolithic/20230211T045208Z/outputs/helm-charts/stx-openstack-1.0-1.stx.6-debian-stable-versioned.tgz Overall Sanity Results: GREEN AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.0%) Failed: 0 (0.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230213 16:57:51 test_ssh_to_hosts PASS 20230213 16:59:28 test_lock_unlock_host[controller] PASS 20230213 17:18:40 test_swact_controllers PASS 20230213 17:28:05 test_openstack_services_healthy PASS 20230213 17:28:55 test_reapply_stx_openstack_no_change[controller-0] PASS 20230213 17:34:07 test_reapply_stx_openstack_no_change[controller-1] PASS 20230213 17:39:19 test_horizon_create_delete_instance PASS 20230213 17:45:18 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20230213 17:50:50 test_migrate_vm[tis-centos-guest-live-None] PASS 20230213 17:55:22 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20230213 17:59:13 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS 20230213 18:03:00 test_evacuate_vms PASS 20230213 18:38:18 test_system_coredumps_and_crashes[core_dumps] PASS 20230213 18:38:34 test_system_coredumps_and_crashes[crash_reports] PASS 20230213 18:38:42 test_system_alarms ----------------------------------------------------------------------- Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Feb 14 19:27:48 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 14 Feb 2023 19:27:48 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230210T070000Z] results - Feb-14 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack sanity using the Feb-10 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230210T070000Z/outputs/iso/starlingx-intel-x86-64-20230210155554-cd.iso and Helm Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230210T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.6-debian-stable-versioned.tgz Overall Sanity Results: GREEN AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.00%) Failed: 0 (0.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230214 16:48:36 test_ssh_to_hosts PASS 20230214 16:50:05 test_lock_unlock_host PASS 20230214 17:09:36 test_openstack_services_healthy PASS 20230214 17:10:32 test_reapply_stx_openstack_no_change[controller-0] PASS 20230214 17:16:32 test_reapply_stx_openstack_no_change[controller-1] PASS 20230214 17:21:30 test_horizon_create_delete_instance PASS 20230214 17:26:51 test_swact_controllers PASS 20230214 17:35:06 test_ping_between_two_vms[tis-centos-guest-virtio-virtio PASS 20230214 17:38:06 test_migrate_vm[tis-centos-guest-live-None] PASS 20230214 17:43:15 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20230214 17:47:49 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS 20230214 17:52:19 test_evacuate_vms* PASS 20230214 17:59:00 test_system_coredumps_and_crashes[core_dumps] PASS 20230214 17:59:19 test_system_coredumps_and_crashes[crash_reports] PASS 20230214 17:59:29 test_system_alarms ----------------------------------------------------------------------- *: This test passed on a retest. On the first run, it failed due to a new intermittent issue: https://bugs.launchpad.net/starlingx/+bug/2007303 Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From helena at openstack.org Tue Feb 14 20:25:36 2023 From: helena at openstack.org (Helena Spease) Date: Tue, 14 Feb 2023 14:25:36 -0600 Subject: [Starlingx-discuss] The OpenInfra Summit Schedule is Live! In-Reply-To: <8190C3A3-7CEA-4C05-B18E-4B1099B514FA@openstack.org> References: <8190C3A3-7CEA-4C05-B18E-4B1099B514FA@openstack.org> Message-ID: <048387FC-66E9-4F1B-9048-A7D638ADC616@openstack.org> Hi All, I hope you have had a chance to take a look at the schedule [1] and save some talks you are excited to check out at the OpenInfra Summit! I want to follow up with a reminder that early bird sales for the OpenInfra Summit [2] are ending tomorrow (February 15, 2023, at 11:59 p.m. PT). If you have any questions regarding the OpenInfra Summit, feel free to reach out! [1] https://openinfra.dev/summit-schedule [2] https://openinfra.dev/summit Cheers, Helena helena at openinfra.dev Marketing & Community Associate The OpenInfra Foundation > On Feb 8, 2023, at 10:02 AM, Helena Spease wrote: > > Hello everyone, > > I am really excited to let you know the Schedule [1] for the OpenInfra Summit 2023 is available! > > The schedule features keynotes and sessions from users like Bloomberg, LINE, Alibaba Cloud, Samsung and Volvo. The event will be held June 13-15, 2023, at the Vancouver Convention Centre overlooking Vancouver Harbor. Other notable speakers include Ant Group, the Australian Research Data Commons (ARDC), China Mobile, SAP, and Viettel, the largest public and private cloud infrastructure provider in Vietnam. > > Check out these StarlingX session you can expect at the OpenInfra Summit! > A private 5G campus network enabled and powered by OpenStack and StarlingX by Robert Holling > StarlingX: Next Generation Security with Zero Trust Architecture by Sudhanshu Harshavat > StarlingX at scale - Infrastructure management of 10s of 1000s of geographically distributed clouds by Ramaswamy Subramanian, John Kung > > > The OpenInfra Summit [2] will be a limited-capacity, sellout event. Early bird sales for the OpenInfra Summit end February 15, 2023 at 11:59 PM PT. Register now [3] to save on your ticket and join us in Vancouver, June 13-15, 2023! > > The price increase will also apply to contributor discount codes, so if you received a contributor discount code last week, be sure to use it before February 15! > > Looking for other resources for the OpenInfra Summit? Sponsorship, Travel Support, visa requests, info on the PTG at the OpenInfra Summit, and Forum session details can be found at openinfra.dev/summit ! > > Cheers, > Helena > > [1] http://openinfra.dev/summit-schedule > [2] http://openinfra.dev/summit > [3] https://openinfra.dev/summit/registration > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Wed Feb 15 14:14:04 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Wed, 15 Feb 2023 15:14:04 +0100 Subject: [Starlingx-discuss] StarlingX 5th Anniversary Message-ID: <29867A26-2EC7-4337-AB49-0F47E1F3164A@openstack.org> Hi StarlingX Community, I?m reaching out to you to draw your attention to StarlingX?s 5th anniversary this year! The StarlingX project was announced at the Open Infrastructure Summit in 2018 in Vancouver, and then was officially launched later that year. The StarlingX platform as well as the community came a long way in the past 5 years to reach this milestone! The project went through a complete architecture revamp, gained multiple users, including large telecom operators around the globe, and contributors of the project have been shaping the community to be able to maintain and develop the platform further. I would like to invite you all to celebrate this anniversary together throughout 2023! There are multiple ways to recognize and celebrate StarlingX. A few examples: * Creating content to show the history, evolution and achievements of the project - Blog posts - OpenInfra Live episode * Celebrate in person at the upcoming OpenInfra Summit in Vancouver * Online gathering to allow the global community to mingle and celebrate * Social media campaign to highlight the project?s 5th birthday I created an etherpad to collect further ideas from the community to celebrate StarlingX?s 5th anniversary: https://etherpad.opendev.org/p/starlingx_5th_anniversary Please let me know if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From mark.asselstine at windriver.com Wed Feb 15 15:14:44 2023 From: mark.asselstine at windriver.com (Mark Asselstine) Date: Wed, 15 Feb 2023 10:14:44 -0500 Subject: [Starlingx-discuss] Starlingx on ARM processor In-Reply-To: References: Message-ID: <9f993cbf-8a44-9e4a-5025-ddf8c29d7cef@windriver.com> On 2/8/2023 2:43 AM, voipas wrote: > Thanks?for your email, i also checked minimum hardware requirements for > starlingx, so like raspberry pi 4b with 8 GB ram will not work with > strlingx. We have done some very preliminary work experimented with ARM devices as worker nodes but this work is out of date and needs to be revisited. Here are a few notes on the topic. 1. Raspberry Pi kernels are a bit of a pain. There is a constant patchset of several hundred patches needed. Efforts to assist in getting these patches upstream have failed as the community working on the Pi kernel has not always been receptive to assistance. 2. Selecting the Yocto Project kernel for STX when we moved from CentOS was done in the hopes of leveraging the ARM BSPs present in this kernel at some point in the future. So there is a desire to get ARM support to some degree in STX. 3. Resource constraints for ARM have not been experimented with, the earlier POC didn't get far enough to develop these. I would expect once a concerted effort is made to support ARM that list of resources required for STX will be updated to reflect ARM. 4. The build system has not excluded expansion to ARM but at this point hasn't been made to build for ARM. I would anticipate that to start ARM images would be hand crafted to assist with identifying tech updates required for ARM as the build system is updated to be able to build for ARM. Now that the transition away from CentOS is "complete" we can start to revisit ARM. It might be worth writing a Storyboard or raising this request to the TSC to see if efforts can/should be made to get this kicked off. Regards, MarkA > > On 2023-02-07, Tue at 02:25, Outback Dingo > wrote: > > while i see you mentioned three components, arm, edge and openstack > I concur with you that starlingx should support arm also, though it is > very x86 centric > that being said, we faced a similar issue, Ive listed the following to > help you in your edge case scenerios > > kubeedge http://kubeedge.io > > > superedge https://superedge.io > > > openyurt https://openyurt.io > > > Baetyl https://baetyl.io/en/ > > > On Tue, Feb 7, 2023 at 5:02 AM voipas > wrote: > > > > Hello friends, > > > >? ?I know that it is stated that Stalingx is designed for x86-64 > based CPU. > > But I would like to deploy Starlingx on my EDGE devices > (Raspberry PI 4). So I wanted to get your confirmation that I could > compile / build Starlingx source for ARM processors (even in doc it > is mentioned that prerequisite is 64bit OS). > > > > Also, any other recommendations / experience you have for EDGE > openstack deployment for ARM based CPUs? > > > > Thank you in advance > > > > -- > > Best Regards, > > Giedrius > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > -- > Best Regards, > Giedrius > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Juanita.Balaraj at windriver.com Wed Feb 15 22:37:33 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 15 Feb 2023 22:37:33 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 15-02-23 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 ============ 15-February-23 Stx 9.0 Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing StarlingX 8.0 Release: - February 22nd - StarlingX Features: 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 - Modify the following page to include Stx 8.0 https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 - Need to include Stx 8.0 - AR Ron To add Stx 8.0 in the Version drop-down Gerrit Reviews ; https://review.opendev.org/c/starlingx/docs/+/873258; - To automate New Features from the Stx 8.0 RN into the StarlingX Introduction Guide (StarlingX specific) - AR Juanita - Stx 8.0 Release Notes WIP - https://review.opendev.org/c/starlingx/docs/+/873563 - AR Juanita - Elisa raised an issue with a merged review and there was a build failure - The issue was sorted out events.yaml - Applies only to master and it was implemented in 8.0 and forward... - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - To raise a Defect to fix the events.yaml file https://opendev.org/starlingx/fault/src/branch/master/fm-doc/fm_doc/events.yaml to update the "Context" field wherever applicable to "OpenStack" (For example; 100.105 100.112 and 100.113) ; Update Ghada / Greg about the situation; Process is not being followed by Engineering; AR - Ron - 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 / 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?? - Completed the flattening of the TOC.....Flattening of TOC not being implemented on older branches. Simplified on stx 6.0 / stx 7.0 (makes cherry picks easier) Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 1 Review https://review.opendev.org/c/starlingx/docs/+/872912 - Review merged but Zuul failed...content is not appearing in output file; Ron AR Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. - - Teams to add all the impacted Releases when raising a LP bug - Gabriel Francischini joined the docs call and raised an update for the Stx docs - Gabriel to raise a LP Bug. 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: - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG: June 13-15, Vancouver, Canada - https://openinfra.dev/summit/vancouver-2023/ - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - Virtual PTG - March 28-29 ____________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Feb 15 23:17:31 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 15 Feb 2023 23:17:31 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Feb 15/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Feb 15 2023 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: All features are complete - Branch/Build Status: - Successful build as of Feb 11: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230211T045208Z/ - Sanity Status - platform Sanity: Expected to be sent by Feb 17 - stx-openstack Sanity: Green - https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230211T045208Z/ - Regression Status - In progress: SX complete. DX in progress. - Expect to complete by Feb 16 - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - No open bugs - Release Notes - Review posted in main branch: https://review.opendev.org/c/starlingx/docs/+/873563 - Will also need to be cherrypicked - On track for doc updates by middle of next week: Feb 22 - Steps to declare Release Milestone - Tag release branch - Copy RC build to release directory - Mark Build as ReadOnly / Keep - Send the Release Milestone Announcement to the mailing list - Release Press Release - Ildiko working on press release and release blog - Timing will depend to avoid sending the announcement on Fridays as well as the week of MWC - So the press release will be sent either Feb 22 or Mar 6 - Blogs - Proposed Topics - FEC Device Configurability (fec-operator Integration) for ACC100 & N3000 - PTP O-RAN Compliant API Notification - SSH integration with remote Windows Active Directory - Platform Single Core Tuning 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 - Status: Not Started. Need to re-forecast stx.9.0 - New release folder created: https://drive.google.com/drive/folders/1beMET3I7GGa79tv4wfwzeKTy-yFVl6xR?usp=share_link - New Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Populated with deferred features from stx.8.0 - Some new features already added From Ghada.Khalil at windriver.com Wed Feb 15 23:27:30 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 15 Feb 2023 23:27:30 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Feb 15, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call February 15, 2023 Standing topics - Build - Main Branch Debian Builds - Had a rough week with multiple build failures: - Circular dependency due to py39 - Build/Code contamination from stx.8.0 branch creation - Container image failures due to some recent build improvements which had a coding bug - The last successful build was Feb 10. Feb 14 failed. Fixes submitted and Feb 15 build expected to pass. - Main Branch CentOS Builds - N/A. No CentOS builds are triggered. - stx.8.0 RC Builds - Multiple issues have been resolved - Successful build as of Feb 11: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230211T045208Z/ - stx.6.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Sanity - Debian Main Branch Platform Sanity - No sanity this week as the team is focused on stx.8.0 sanity/regression. Will restart again next week. - Last sanity email sent on Feb 8: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013818.html - Status: Green for both SX & DX - Debian Main Branch stx-openstack Sanity - Last sanity email sent on Feb 14: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013838.html - Status: Green - stx.8.0 Sanity - Platform Sanity - Expected to be done on Feb 17 - stx-openstack Sanity - Sanity emial sent on Feb 14: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013837.html - Status: Green - Gerrit Reviews in Need of Attention - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 18: Some activity in the review as of Jan 15 - Feb 1: Alternative fix proposed on Jan 18; waiting for ScottK's review - Feb 15: ScottK is going back to this - 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 - StarlingX is 5!!!! - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013840.html - StarlingX IRC Channel - From Ildiko: Community members are encouraged to join/hang out on the channel to help newcomers. - Release Status - Release Planning Meeting etherpad: https://etherpad.opendev.org/p/stx-releases - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Milestones: - Milestone-3: Jan 18 >> Jan 25 >> Jan 27 / Actual: Jan 31 - Feature Test Complete: Jan 25 >> Jan 31 >> Feb 2 / Actual: Feb 2 - Regression Test Complete: Jan 25 / Actual: Jan 30 - RC1 (branch creation / stx.8.0 builds): Feb 1 >> Feb 6 / Actual: Feb 11 - Final Regression Complete: Feb 15 >> Feb 16 - Release: Feb 22 - Status - Have successful build - Regression testing in progress - Release notes in progress - On track for next week - Items leading up to the Release Milestone - Complete regression/sanity and share results on the mailing list -- Prime: Rob Cooke - Merge release notes and any final doc updates -- Prime: Juanita Balaraj - Update Build / Branch -- Prime: Scott Little - Tag release branch - Copy RC build to release directory - Mark Build as ReadOnly / Keep - Send the Release Milestone Announcement to the mailing list -- Prime: Ghada Khalil - stx.9.0 - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - New features starting to be added - Call to community members/PLs to continue adding their feautre proposal - Would like to have the majority of features proposed by the March virtual PTG (March 28-29) ARs from Previous Meetings - None Open Requests for Help - No new requests on the mailing list since last week - StarlingX Support on ARM - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013819.html - Not currently supported on StarlingX, but should be more doable with the move to Debian and the yocto kernel - ARM Support would definitely require work to support, including build system support - A few years ago MarkA and Greg did some prototype work on orange-pie - MarkA responded to the thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013841.html - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; team has no bandwidth to look at this for the remaining of the month. Will reach out to the reporter to share this. - Documenting Tested Hardware by the community - Brought Up by: Scott Kamp - The StarlingX documentation already has a limited list of certified hardware - A variety of hardware platform doesn't work with StarlingX. - This is due to the kernel options that are enabled, especially as it related to the rt kernel - Standard distributions like Ubuntu has everything enabled - One approach is to consider a mechanism to swap out the kernel - This is a big conversation. Requires TSC direction/guidance and likely significant effort/investment. - Conclusion: Put this as a topic on the PTG. Action: Ildiko From 114769003 at qq.com Sat Feb 11 10:52:07 2023 From: 114769003 at qq.com (=?utf-8?B?TGl1WW9uZ2Z1?=) Date: Sat, 11 Feb 2023 18:52:07 +0800 Subject: [Starlingx-discuss] how to install my own rpm Message-ID: Brief Description ----------------- when I install my private(own) rpm to the compute node. when the node is restarted .my private rpm is deleted. so I want to know : are there some ways to install my own rpm on compute nodes or is it just a bug? Steps to Reproduce ------------------ I installed my GPU rpm packages on the compute node,and it worked right. Expected Behavior ------------------ the rpm packages works correctly all the time. Actual Behavior when reboot the compute nodes .my gpu rpm packages are removed by the system. thanks very much. LiuYongfu 114769003 at qq.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Fri Feb 17 20:01:27 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Fri, 17 Feb 2023 20:01:27 +0000 Subject: [Starlingx-discuss] Sanity StarlingX 8.0 Test LAYERED build ISO 220230211T045208Z Message-ID: Sanity Test from 2023 February 17 (https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/stx.8.0/debian/monolithic/20230211T045208Z/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] DX sanity Passed: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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 Rob.Cooke at windriver.com Fri Feb 17 20:42:28 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Fri, 17 Feb 2023 20:42:28 +0000 Subject: [Starlingx-discuss] StarlingX Release 8.0 Regression Results Message-ID: Hello everyone, Final regression on the StarlingX 8.0 release branch has been completed. All the regression tests have been executed and analyzed with no release gating issues identified. The details around the execution and test cases are tracked in our regression sheet at this location https://docs.google.com/spreadsheets/d/1b5w2oLlGwipTlrNysWwl1JnM1dvyboIIQhpBJLcZECI/edit#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Fri Feb 17 21:05:22 2023 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 17 Feb 2023 21:05:22 +0000 Subject: [Starlingx-discuss] how to install my own rpm In-Reply-To: References: Message-ID: With StarlingX, the way to add an rpm to the platform is through a patch. Within the StarlingX patching system it will install the rpm, and will prevent it from being removed by a reboot. There is a video from the Open Infrastructure Foundation that shows an example of creating your own patch to allow an rpm to be installed. It uses the patch_build.sh command https://www.youtube.com/watch?v=vwqhxpgaxXE For example, if I wanted to add an RPM for pyflame my patch_build.sh syntax would look something like this: # Run this script from within $MY_WORKSPACE PATH=$MY_REPO/stx/update/extras/scripts:$PATH PATCH_ID=PYFLAME DIR=std/rpmbuild/RPMS PYFLAME=pyflame-1.6.6-4.el7.tis.1.x86_64.rpm patch_build.sh \ --id ${PATCH_ID} \ --reboot-required=Y \ --summary "New pyflame rpm " \ --desc "Adds a new pyflame rpm "\ --controller ${DIR}/${PYFLAME} \ --controller-worker ${DIR}/${PYFLAME} \ --controller-worker-lowlatency ${DIR}/${PYFLAME} Be aware that in this example, I am ?adding? an rpm rather than updating one, so I needed to include special fields (--controller , --controller-worker , --controller-worker-lowlatency ) so that the platform knows that the rpm belongs on controller and AIO hosts (and in this example it will not install it on worker or storage nodes) The video (and my example) assume you have a development environment setup with your variables, etc.. already defined. If that is not the case, you may need to ensure you have the starlingx/update repo checked out and make the appropriate changes to the commands. Al From: LiuYongfu <114769003 at qq.com> Sent: Saturday, February 11, 2023 5:52 AM To: starlingx-discuss Subject: [Starlingx-discuss] how to install my own rpm 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. Brief Description ----------------- when I install my private(own) rpm to the compute node. when the node is restarted .my private rpm is deleted. so I want to know : are there some ways to install my own rpm on compute nodes or is it just a bug? Steps to Reproduce ------------------ I installed my GPU rpm packages on the compute node,and it worked right. Expected Behavior ------------------ the rpm packages works correctly all the time. Actual Behavior when reboot the compute nodes .my gpu rpm packages are removed by the system. thanks very much. [Image removed by sender.] LiuYongfu 114769003 at qq.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD0000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD0000.jpg URL: From ildiko at openstack.org Mon Feb 20 10:35:20 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Mon, 20 Feb 2023 11:35:20 +0100 Subject: [Starlingx-discuss] Kernel and HW compatibility discussion at the vPTG Message-ID: <24980E5A-EBCD-43D5-8880-9D1F37D8FB9F@openstack.org> Hi, I?m reaching out to follow up on a topic that came up during the Community Call last week (Feb 15). The main challenge that the group on the call discussed was around the limited set of supported HW by the StarlingX platform. We touched on two angles: * How does someone know exactly what HW is supported by the platform? - Is the list in the documentation comprehensive? Can it be? * Is it possible to achieve better compatibility and support a wider range of HW options? - What are the main factors of the limited set of supported HW types? Possible solutions: * The community needs a wider pool of HW varieties to test on - Third-party testing? * The real-time kernel causes challenges, as it limits the enabled kernel-options by default - There are multiple ways forward + Enable more kernel options by default. Is that really possible/feasible? = i.e. Standard distributions like Ubuntu has everything enabled + Consider a mechanism to swap out the kernel ?> This points back to earlier discussions about the modularity of the StarlingX platform The above questions and solution ideas all point towards a bigger conversation. The above directions each require time and focus from the community to achieve. In order get into the details of the problem as well as options and preferred solutions forward, we suggested to continue the conversation on the virtual PTG in march. What do you all think? Who in the community would be interested in moderating the conversation? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Linda.Wang at windriver.com Tue Feb 21 04:03:49 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Tue, 21 Feb 2023 04:03:49 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting: Feb 8, 2023 Message-ID: Feb 8, 2023 Attendees: Mike, Fabiano, Linda, Scott, Davelet, Mark 1. General Topics ??????0.1 Split package list betweeen repositories (ISO and container images) * * AI: We'll need to look closely to see if there is any further improvement needed. ??????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) * AI: to invite Carlos Pocahy to this meeting to discuss Pre-patch ISO. [Done] II. StarlingX 8.0 0.1 Secureboot Enablement * Working on Key in a separte repo. * Need to have a different repo/storage to storage keys without changing any code. * * Scott is creating the git and manifest setup. Fix up the meta data in control file, and send that back to LiZhu. * One option is to interface with the concept of Vault. * Sent the checksum into the Vault to get sign. and the key is always in the Vault. * Put the public key into the public key ring. * Level of indirection, to put the signing method(s) behind an API. * AI: to invite DevSecOPs team from Studio side to discuss Vault's implementation. (lwang8 to invite Yasin) [Done] 0.2 ISO size bigginer 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. * Extension to the ISO build standard, 9660, for longer file names, addresses the daisy chain of the ISO for larger archieve. * AI: need to investigate the "ISO daisy chain extension of another 4G, and tooling needs. Need to createa story board ticket. 0.3 Kernel Live Patching Integration with the build system * start to look into the requirements of integration of feature. 0.4 STX tree udpate * * Built a temp, and failure to STX8 docker images due to invalid tag. 0.5 CentOS7 on main (master) branch build * Build has stopped/disabled on Feb 7. 0.6 Initramfs will changed for new driver updates * per one of the patch under review: https://review.opendev.org/c/starlingx/tools/+/872867 * initramfs should *only* be updated if it needs modifications to gain access to the rootfs. This will not mean that it never gets updated, but it will be rare. 3. Open Request for help * * Raspberry Pi support as Edge. * * AI: Mark to reply to the thread and investigate further. Next Meeting: Feb 22, 2023 Thanks, Linda -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Tue Feb 21 10:18:04 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 21 Feb 2023 11:18:04 +0100 Subject: [Starlingx-discuss] [release] StarlingX 8.0 release date Message-ID: <8560D5BE-7CD5-46F9-95FA-A5CBA90DFD52@openstack.org> Hi, I?m reaching out about the 8.0 release. I?ve been keeping an eye on the testing activities and the release notes, and it looks like that everything is getting very close to be able to release this week. I am working with the marketing team at the OpenInfra Foundation to coordinate release announcements and communications. In order to be able to publish the release announcement on Thursday this week, the latest, we need a little bit of prior heads up to be certain whether the release will be cut by then or not. @Ghada: Do you have information about whether we expect the release to be out on Wednesday (Feb 22) as forecasted, or there might be something that could delay it? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Ghada.Khalil at windriver.com Tue Feb 21 14:33:21 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 21 Feb 2023 14:33:21 +0000 Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Starting In-Reply-To: References: Message-ID: Hi Scott, Given the successful sanity email [1] and regression email [2] sent on Friday, please proceed with the final release steps: - Update Build / Branch -- Prime: Scott Little - Tag release branch - Copy RC build to release directory - Mark Build as ReadOnly / Keep Hi Juanita, Please also plan to merge and cherry-pick the release notes (review [3]) by Wednesday if possible. References: [1] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013846.html [2] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013847.html [3] https://review.opendev.org/c/starlingx/docs/+/873563 Regards, Ghada From Ghada.Khalil at windriver.com Tue Feb 21 14:38:24 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 21 Feb 2023 14:38:24 +0000 Subject: [Starlingx-discuss] [release] StarlingX 8.0 release date In-Reply-To: <8560D5BE-7CD5-46F9-95FA-A5CBA90DFD52@openstack.org> References: <8560D5BE-7CD5-46F9-95FA-A5CBA90DFD52@openstack.org> Message-ID: Hi Ildiko, I believe stx.8.0 is on track. I'm not aware of anything that would delay the release date. I've just sent a note to Scott and Juanita (cc'ing the mailing list) to wrap up the final release steps. Regards, Ghada -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, February 21, 2023 5:18 AM To: StarlingX ML Cc: Khalil, Ghada Subject: [release] StarlingX 8.0 release date 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?m reaching out about the 8.0 release. I?ve been keeping an eye on the testing activities and the release notes, and it looks like that everything is getting very close to be able to release this week. I am working with the marketing team at the OpenInfra Foundation to coordinate release announcements and communications. In order to be able to publish the release announcement on Thursday this week, the latest, we need a little bit of prior heads up to be certain whether the release will be cut by then or not. @Ghada: Do you have information about whether we expect the release to be out on Wednesday (Feb 22) as forecasted, or there might be something that could delay it? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From ildiko at openstack.org Tue Feb 21 14:40:02 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 21 Feb 2023 15:40:02 +0100 Subject: [Starlingx-discuss] [release] StarlingX 8.0 release date In-Reply-To: References: <8560D5BE-7CD5-46F9-95FA-A5CBA90DFD52@openstack.org> Message-ID: <267B319A-7FAE-4585-B8B4-728A9F97351E@openstack.org> Hi Ghada, That sounds great, thank you for the prompt response! I will keep monitoring the mailing list and the open review for the release notes, to follow the final steps. Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 21, 2023, at 15:38, Khalil, Ghada wrote: > > Hi Ildiko, > I believe stx.8.0 is on track. I'm not aware of anything that would delay the release date. I've just sent a note to Scott and Juanita (cc'ing the mailing list) to wrap up the final release steps. > > Regards, > Ghada > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, February 21, 2023 5:18 AM > To: StarlingX ML > Cc: Khalil, Ghada > Subject: [release] StarlingX 8.0 release date > > 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?m reaching out about the 8.0 release. > > I?ve been keeping an eye on the testing activities and the release notes, and it looks like that everything is getting very close to be able to release this week. I am working with the marketing team at the OpenInfra Foundation to coordinate release announcements and communications. In order to be able to publish the release announcement on Thursday this week, the latest, we need a little bit of prior heads up to be certain whether the release will be cut by then or not. > > @Ghada: Do you have information about whether we expect the release to be out on Wednesday (Feb 22) as forecasted, or there might be something that could delay it? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > From kennelson11 at gmail.com Tue Feb 21 15:33:12 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 21 Feb 2023 09:33:12 -0600 Subject: [Starlingx-discuss] Fwd: PTG March 2023 Teams List In-Reply-To: References: Message-ID: Hello Everyone! The March 2023 Project Teams List is official! *Projects + Teams* - OpenInfra Foundation Teams - Diversity and Inclusion WG - Edge Computing Group - Environmental Sustainability Working Group - Interop WG - StarlingX - OpenStack Teams - Service Teams - Barbican - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Kuryr - Magnum - Manila - Neutron - Nova - Octavia - OpenaStackSDK/CLI/Ansible-Collections - OpenStack-Ansible - OpenStackCharms - QA - Tacker - Other Teams - Scientific SIG - PublicCloud SIG OpenStack - Security SIG - OpenStack Technical Committee - RBAC - I18n SIG If your team was planning to meet and isn?t on this list, please contact ptg at openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign your team up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] ? *its FREE!* As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Tue Feb 21 16:29:02 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Tue, 21 Feb 2023 16:29:02 +0000 Subject: [Starlingx-discuss] Kernel and HW compatibility discussion at the vPTG In-Reply-To: <24980E5A-EBCD-43D5-8880-9D1F37D8FB9F@openstack.org> References: <24980E5A-EBCD-43D5-8880-9D1F37D8FB9F@openstack.org> Message-ID: Hi, > The real-time kernel causes challenges, as it limits the enabled kernel-options by default > - There are multiple ways forward > + Enable more kernel options by default. Is that really possible/feasible? > = i.e. Standard distributions like Ubuntu has everything enabled > + Consider a mechanism to swap out the kernel ?> These points back to earlier discussions about the modularity of the StarlingX platform ^ This would be slightly difficult to do if it is to swap between real-time kernel vs standard kernel. If it is related to swapping out the same type of kernel, just different funcationliaties. live patching or kernel modules upgrades may be a possibility. > What do you all think? Who in the community would be interested in moderating the conversation? Given that these topics are closely related to the OS/Multi-OS community, I and Mark A should help moderate the conversation. Please let me know when the next discussion will be scheduled. Hope this helps and thanks, Linda ________________________________ From: Ildiko Vancsa Sent: Monday, February 20, 2023 2:35 AM To: StarlingX ML Subject: [Starlingx-discuss] Kernel and HW compatibility discussion at the vPTG 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?m reaching out to follow up on a topic that came up during the Community Call last week (Feb 15). The main challenge that the group on the call discussed was around the limited set of supported HW by the StarlingX platform. We touched on two angles: * How does someone know exactly what HW is supported by the platform? - Is the list in the documentation comprehensive? Can it be? * Is it possible to achieve better compatibility and support a wider range of HW options? - What are the main factors of the limited set of supported HW types? Possible solutions: * The community needs a wider pool of HW varieties to test on - Third-party testing? * The real-time kernel causes challenges, as it limits the enabled kernel-options by default - There are multiple ways forward + Enable more kernel options by default. Is that really possible/feasible? = i.e. Standard distributions like Ubuntu has everything enabled + Consider a mechanism to swap out the kernel ?> This points back to earlier discussions about the modularity of the StarlingX platform The above questions and solution ideas all point towards a bigger conversation. The above directions each require time and focus from the community to achieve. In order get into the details of the problem as well as options and preferred solutions forward, we suggested to continue the conversation on the virtual PTG in march. What do you all think? Who in the community would be interested in moderating the conversation? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gabriel.CalixtodePaula at windriver.com Tue Feb 21 17:59:15 2023 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Tue, 21 Feb 2023 17:59:15 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER Build ISO [20230219T070001Z] results - Feb-21 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack sanity using the Feb-19 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230219T070001Z/outputs/iso/starlingx-intel-x86-64-20230219173216-cd.iso and Helm Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230219T070001Z/outputs/helm-charts/stx-openstack-1.0-1.stx.6-debian-stable-versioned.tgz Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 14 (93.33%) Failed: 1 (6.67%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230221 12:50:03 test_ssh_to_hosts PASS 20230221 12:51:41 test_lock_unlock_host PASS 20230221 13:15:44 test_openstack_services_healthy PASS 20230221 13:16:46 test_reapply_stx_openstack_no_change[controller-0] PASS 20230221 13:18:47 test_reapply_stx_openstack_no_change[controller-1] PASS 20230221 13:23:40 test_horizon_create_delete_instance PASS 20230221 13:30:00 test_swact_controllers PASS 20230221 13:39:54 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20230221 13:46:43 test_migrate_vm[tis-centos-guest-live-None] PASS 20230221 13:51:51 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20230221 13:56:24 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230221 14:00:58 test_evacuate_vms PASS 20230221 14:35:37 test_system_coredumps_and_crashes[core_dumps] PASS 20230221 14:36:02 test_system_coredumps_and_crashes[crash_reports] PASS 20230221 14:36:17 test_system_alarms ----------------------------------------------------------------------- The failed test is due to the issue: https://bugs.launchpad.net/starlingx/+bug/2007303 Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Feb 21 20:57:59 2023 From: scott.little at windriver.com (Scott Little) Date: Tue, 21 Feb 2023 15:57:59 -0500 Subject: [Starlingx-discuss] [release] StarlingX 8.0 release date In-Reply-To: References: <8560D5BE-7CD5-46F9-95FA-A5CBA90DFD52@openstack.org> Message-ID: <2f6c0a46-423d-6b8c-ad9a-aff113921f9e@windriver.com> I have completed the release steps on CENGN.? The StarlingX 8.0.0 iso is published under .... https://mirror.starlingx.cengn.ca/mirror/starlingx/release/8.0.0/debian/monolithic/outputs/iso/ and the 'latest_release' has been updated as well ... https://mirror.starlingx.cengn.ca/mirror/starlingx/release/latest_release/debian/monolithic/outputs/iso/ All artifacts have been marked with a KEEP file and set read-only. The build context has been tagged. And the following update adds a manifest to check-out that the tag ... https://review.opendev.org/c/starlingx/manifest/+/874693 Scott On 2023-02-21 09:38, Khalil, Ghada wrote: > Hi Ildiko, > I believe stx.8.0 is on track. I'm not aware of anything that would delay the release date. I've just sent a note to Scott and Juanita (cc'ing the mailing list) to wrap up the final release steps. > > Regards, > Ghada > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, February 21, 2023 5:18 AM > To: StarlingX ML > Cc: Khalil, Ghada > Subject: [release] StarlingX 8.0 release date > > 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?m reaching out about the 8.0 release. > > I?ve been keeping an eye on the testing activities and the release notes, and it looks like that everything is getting very close to be able to release this week. I am working with the marketing team at the OpenInfra Foundation to coordinate release announcements and communications. In order to be able to publish the release announcement on Thursday this week, the latest, we need a little bit of prior heads up to be certain whether the release will be cut by then or not. > > @Ghada: Do you have information about whether we expect the release to be out on Wednesday (Feb 22) as forecasted, or there might be something that could delay it? > > 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 Peng.Peng at windriver.com Wed Feb 22 02:34:49 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Wed, 22 Feb 2023 02:34:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230219T070001Z Message-ID: Sanity Test from 2023 February 21 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230219T070001Z/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] DX sanity Passed: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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 ildiko at openstack.org Wed Feb 22 14:34:57 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Wed, 22 Feb 2023 15:34:57 +0100 Subject: [Starlingx-discuss] OpenInfra Summit Forum Selection Committee Call for Volunteers In-Reply-To: References: Message-ID: Hi StarlingX Community, It is a friendly reminder that we are still looking for volunteers for the Forum Selection Committee. The Forum is a co-located event to the Open Infrastructure Summit, the main event is scheduled for June 13-15 in Vancouver, Canada. The focus of this co-located event is to provide space for interactive sessions for users and contributors to interact and discuss relevant topics to their projects and activities, such as feedback, challenges or bigger roadmap items. For further information about the Forum, please see: https://openinfra.dev/summit/vancouver-2023/forum/ Serving on the Selection Committee is a great opportunity to connect with others in the OpenInfra communities and ecosystem, and contribute to the success of the event. The help from volunteers is always highly valued and appreciated! Please let me know if you have any questions I can help with. If you would like to volunteer, please reach out to my colleague, Kendall Nelson at knelson at openinfra.dev. You can also reach out to her directly with questions, if you are interested, but still hesitant to commit. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 2, 2023, at 19:47, Kendall Nelson wrote: > > Hello Everyone! > > The Forum at the OpenInfra Summit Vancouver is coming up! We would love 1 volunteer from StarlingX for the Forum Selection Committee. > > Ideally, the volunteer would: > > - already be serving in some capacity in a governance role for your project > - not be planning to submit to the Forum CFP or be willing to abstain from voting on your proposals > > For information on the OpenInfra Summit in Vancouver: https://openinfra.dev/summit/vancouver-2023/ > > For more information on the Forum, please see: https://openinfra.dev/summit/vancouver-2023/forum/ > > Please reach out to me, knelson at openinfra.dev, or reply on this thread if you're interested. Volunteers should respond on or before March 5th, 2023 @ 7:00 UTC. > > This role does not require you to travel to the OpenInfra Summit, but can get you a discounted ticket if you choose to volunteer and then attend (we would love to have you there!). > > > Thanks! > > Kendall Nelson > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Ghada.Khalil at windriver.com Wed Feb 22 17:54:31 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 22 Feb 2023 17:54:31 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Feb 22, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call February 22, 2023 Standing topics - Build - Main Branch Debian Builds - Green; had successful builds this week - stx.8.0 RC Builds - Successful build as of Feb 11: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/debian/monolithic/20230211T045208Z/ - No builds have been required since Feb 11 - The above RC build is now considered the release build: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013858.html - Do we need stx.8.0 weekly builds? - Agreed to start weekly builds shortly for consistency w/ stx.6.0 & stx.7.0 and to ensure the build jobs are maintained - stx.6.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - stx.8.0 Weekly Builds - Will start shortly. Prime: ScottL - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on Feb 22: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013859.html - Status: Green for both SX & DX - Debian Main Branch stx-openstack Sanity - Last sanity email sent on Feb 21: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013857.html - Status: Yellow - LP: https://bugs.launchpad.net/starlingx/+bug/2007303 -- intermittent issue; passed on re-test - stx.8.0 Sanity - Platform Sanity - Sanity email sent on Feb 17: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013846.html - Status: Green - stx-openstack Sanity - Sanity email sent on Feb 14: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013837.html - Status: Green - Gerrit Reviews in Need of Attention - stx.8.0 Release Notes Review: https://review.opendev.org/c/starlingx/docs/+/873563 - Need the release notes reviewed/cherrypicked today for the stx.8.0 release declaration - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 18: Some activity in the review as of Jan 15 - Feb 1: Alternative fix proposed on Jan 18; waiting for ScottK's review - Feb 15: ScottK is going back to this - 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 - Release Status - Release Planning Meeting etherpad: https://etherpad.opendev.org/p/stx-releases - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Milestones: - Release: Feb 22 << On track - Status - Sanity & Regression testing - Prime: Rob Cooke / Status: Complete - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013837.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013846.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013847.html - Final Build / Branch updates - Prime: Scott Little / Status: Complete - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013858.html - Release Notes Merged / Cherry-picked - Prime: Juanita Balaraj / Status: In Progress - https://review.opendev.org/c/starlingx/docs/+/873563 - On track to complete today - Feb 22 - Release Milestone Email Sent - Prime: Ghada Khalil / Status: Not Started - Pending release notes. Scheduled to go out on Feb 22 - Release Press Release Sent - Prime: Ildiko / Status: - Scheduled to go out on Feb 23 - Blogs - Ildiko working on the release blog post - Other blog posts are planned for later; will start to track those as part of the bi-weekly release planning meetings - stx.9.0 - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - New features starting to be added - Call to community members/PLs to continue adding their feautre proposal - Would like to have the majority of features proposed by the March virtual PTG (March 28-29) ARs from Previous Meetings - None Open Requests for Help - Installing additional RPMs - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013845.html - Already responded to on the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013848.html - Status: Closed - StarlingX Support on ARM - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013819.html - Not currently supported on StarlingX, but should be more doable with the move to Debian and the yocto kernel - ARM Support would definitely require work to support, including build system support - A few years ago MarkA and Greg did some prototype work on orange-pie - MarkA responded to the thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013841.html - No further responses to Mark's last email - Status: Watch List; will leave on the community list for a few more weeks - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; team has no bandwidth to look at this for the remaining of the month. Will reach out to the reporter to share this. - Status: No updates - Documenting Tested Hardware by the community - Brought Up by: Scott Kamp - The StarlingX documentation already has a limited list of certified hardware - A variety of hardware platform doesn't work with StarlingX. - This is due to the kernel options that are enabled, especially as it related to the rt kernel - Standard distributions like Ubuntu has everything enabled - One approach is to consider a mechanism to swap out the kernel - This is a big conversation. Requires TSC direction/guidance and likely significant effort/investment. - Conclusion: Put this as a topic on the PTG. Action: Ildiko - Status: Closed - Ildiko sent email to the community https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013849.html - Topic added to the PTG by GregW - w/ Linda Wang & MarkA moderating - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013856.html From Greg.Waines at windriver.com Wed Feb 22 19:38:53 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 22 Feb 2023 19:38:53 +0000 Subject: [Starlingx-discuss] CONTEXT in events.yaml Message-ID: Just a reminder ... from your StarlingX DOCS Team, If you are updating stx/fault/fm-doc/fm_doc/events.yaml , In order to add a new Alarm or Log for StarlingX, DO NOT FORGET to include the new 'Context' field. ( # Context: < none | starlingx | openstack > ) ... which indicates what section of docs.starlingx.io (i.e. the platform or openstack) that the alarm/log should be published. e.g. 100.103: Type: Alarm Description: |- Memory threshold exceeded; threshold x%, actual y% . CRITICAL @ 90% MAJOR @ 80% Entity_Instance_ID: |- host= OR host=.memory=total OR host=.memory=platform OR host=.numa=node Severity: [critical, major] Proposed_Repair_Action: "Monitor and if condition persists, contact next level of support; may require additional memory on Host." Maintenance_Action: critical: degrade major: degrade Inhibit_Alarms: Alarm_Type: operational-violation Probable_Cause: threshold-crossed Service_Affecting: False Suppression: True Management_Affecting_Severity: none Degrade_Affecting_Severity: critical Context: starlingx Greg / Juanita -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 23 01:48:09 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 23 Feb 2023 01:48:09 +0000 Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Update In-Reply-To: References: Message-ID: Hello all, The build/branch updates for stx.8.0 are now complete as per: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013858.html However, there are issues with publishing the stx.8.0 docs / release notes. These issues are under investigation by the stx doc team, together with the opendev infrastructure team. The stx.8.0 release declaration email will be sent out once the docs are published. Thanks, Ghada -----Original Message----- From: Khalil, Ghada Sent: Tuesday, February 21, 2023 9:33 AM To: Little, Scott ; Balaraj, Juanita Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Starting Hi Scott, Given the successful sanity email [1] and regression email [2] sent on Friday, please proceed with the final release steps: - Update Build / Branch -- Prime: Scott Little - Tag release branch - Copy RC build to release directory - Mark Build as ReadOnly / Keep Hi Juanita, Please also plan to merge and cherry-pick the release notes (review [3]) by Wednesday if possible. References: [1] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013846.html [2] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013847.html [3] https://review.opendev.org/c/starlingx/docs/+/873563 Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Juanita.Balaraj at windriver.com Thu Feb 23 04:02:22 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 23 Feb 2023 04:02:22 +0000 Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Update In-Reply-To: References: Message-ID: Hello All, The StarlingX 8.0 docs / Release Notes are now available at https://docs.starlingx.io/r/stx.8.0/. Thank you, Juanita -----Original Message----- From: Khalil, Ghada Sent: February 22, 2023 8:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Update Hello all, The build/branch updates for stx.8.0 are now complete as per: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013858.html However, there are issues with publishing the stx.8.0 docs / release notes. These issues are under investigation by the stx doc team, together with the opendev infrastructure team. The stx.8.0 release declaration email will be sent out once the docs are published. Thanks, Ghada -----Original Message----- From: Khalil, Ghada Sent: Tuesday, February 21, 2023 9:33 AM To: Little, Scott ; Balaraj, Juanita Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Release 8.0 Release Final Steps Starting Hi Scott, Given the successful sanity email [1] and regression email [2] sent on Friday, please proceed with the final release steps: - Update Build / Branch -- Prime: Scott Little - Tag release branch - Copy RC build to release directory - Mark Build as ReadOnly / Keep Hi Juanita, Please also plan to merge and cherry-pick the release notes (review [3]) by Wednesday if possible. References: [1] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013846.html [2] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013847.html [3] https://review.opendev.org/c/starlingx/docs/+/873563 Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Ghada.Khalil at windriver.com Thu Feb 23 04:05:24 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 23 Feb 2023 04:05:24 +0000 Subject: [Starlingx-discuss] stx.8.0 Release Milestone declared Message-ID: Hello all, This email announces that the st8.7.0 Release milestone has been achieved as of February 22, 2023. StarlingX release 8.0 is officially delivered. The ISO/build artifacts are available on CENGN at: https://mirror.starlingx.cengn.ca/mirror/starlingx/release/8.0.0/debian/monolithic/outputs Release documentation is on starlingx.io at: https://docs.starlingx.io/r/stx.8.0/ Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. Congratulations everyone! Regards, Ghada On behalf of the StarlingX Release team From ildiko at openstack.org Thu Feb 23 16:20:04 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Thu, 23 Feb 2023 17:20:04 +0100 Subject: [Starlingx-discuss] stx.8.0 Release Milestone declared In-Reply-To: References: Message-ID: Hi, Thanks Ghada for delivering the great news! Hereby I would like to congratulate the community for reaching this milestone! Also thank you to all the contributors, who worked on the platform and related artifacts throughout the 8.0 release cycle. The press release to announce the new version was also published earlier today: https://www.prweb.com/releases/starlingx_8_0_delivers_enhanced_stability_scalability_support_for_ran_distributed_cloud_architecture_edge_computing_use_cases/prweb19183873.htm Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 23, 2023, at 05:05, Khalil, Ghada wrote: > > Hello all, > This email announces that the st8.7.0 Release milestone has been achieved as of February 22, 2023. StarlingX release 8.0 is officially delivered. > > The ISO/build artifacts are available on CENGN at: https://mirror.starlingx.cengn.ca/mirror/starlingx/release/8.0.0/debian/monolithic/outputs > Release documentation is on starlingx.io at: https://docs.starlingx.io/r/stx.8.0/ > > Thank you to everyone in the Community - development, test and documentation - for all of your hard work in delivering this release. > Congratulations everyone! > > Regards, > Ghada > On behalf of the StarlingX Release team > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Juanita.Balaraj at windriver.com Thu Feb 23 18:35:14 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 23 Feb 2023 18:35:14 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 22-02-23 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 ============ 22-February-23 Stx 9.0 Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing StarlingX 8.0 Release: - February 22nd - Delivered on time. NOTE: Worked with the OpenDev community to fix a zuul issue, that was hindering publish of the Stx 8.0 Release - Modify the following page to include Stx 8.0 https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - DONE https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 - Need to include Stx 8.0 - AR Ron - DONE To add Stx 8.0 in the Version drop-down - DONE Gerrit Reviews ; https://review.opendev.org/c/starlingx/docs/+/873258; To automate New Features from the Stx 8.0 RN into the StarlingX Introduction Guide (StarlingX specific) - AR Juanita - DONE - Stx 8.0 Release Notes WIP - https://review.opendev.org/c/starlingx/docs/+/873563 - DONE (Cherry picked to Stx 8.0) events.yaml - Applies to 8.0 and release going forward - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - To raise a Defect to fix the events.yaml file https://opendev.org/starlingx/fault/src/branch/master/fm-doc/fm_doc/events.yaml to update the "Context" field wherever applicable to "OpenStack" (For example; 100.105 100.112 and 100.113) ; DONE - Greg sent an email to the StarlingX Community on February 22nd. - 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 / 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?? - Completed the flattening of the TOC.....Flattening of TOC not being implemented on older branches. Simplified on stx 6.0 / stx 7.0 (makes cherry picks easier) Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 1 Review https://review.opendev.org/c/starlingx/docs/+/872912 - Review merged but Zuul failed...content is not appearing in output file; Ron AR - Elisa raised an issue with a merged review and there was a build failure - The issue was sorted out Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Gabriel joined the docs call and raised an update for the Stx docs - Gabriel to raise a LP Bug. 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: - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG: June 13-15, Vancouver, Canada - https://openinfra.dev/summit/vancouver-2023/ - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - Virtual PTG ... March 27-31, 2023 Etherpad for Virtual PTG Planning: https://etherpad.opendev.org/p/stx-ptg-planning-march-2023 ____________________ 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 Al.Bailey at windriver.com Mon Feb 27 15:36:56 2023 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 27 Feb 2023 15:36:56 +0000 Subject: [Starlingx-discuss] CONTEXT in events.yaml In-Reply-To: References: Message-ID: I wired this into the linters job https://review.opendev.org/c/starlingx/fault/+/875508 Al From: Waines, Greg Sent: Wednesday, February 22, 2023 2:39 PM To: StarlingX ML Subject: [Starlingx-discuss] CONTEXT in events.yaml Just a reminder ... from your StarlingX DOCS Team, If you are updating stx/fault/fm-doc/fm_doc/events.yaml , In order to add a new Alarm or Log for StarlingX, DO NOT FORGET to include the new 'Context' field. ( # Context: < none | starlingx | openstack > ) ... which indicates what section of docs.starlingx.io (i.e. the platform or openstack) that the alarm/log should be published. e.g. 100.103: Type: Alarm Description: |- Memory threshold exceeded; threshold x%, actual y% . CRITICAL @ 90% MAJOR @ 80% Entity_Instance_ID: |- host= OR host=.memory=total OR host=.memory=platform OR host=.numa=node Severity: [critical, major] Proposed_Repair_Action: "Monitor and if condition persists, contact next level of support; may require additional memory on Host." Maintenance_Action: critical: degrade major: degrade Inhibit_Alarms: Alarm_Type: operational-violation Probable_Cause: threshold-crossed Service_Affecting: False Suppression: True Management_Affecting_Severity: none Degrade_Affecting_Severity: critical Context: starlingx Greg / Juanita -------------- next part -------------- An HTML attachment was scrubbed... URL: From grajesh.ec at gmail.com Mon Feb 27 20:26:18 2023 From: grajesh.ec at gmail.com (Rajesh Gunasekaran) Date: Mon, 27 Feb 2023 21:26:18 +0100 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 22-02-23 In-Reply-To: References: Message-ID: Hi Juanita, I am interested in contributing to the StarlingX docs. I will join the meeting this week! Best Regards, Rajesh On Thu, Feb 23, 2023 at 7:37 PM Balaraj, Juanita < Juanita.Balaraj at windriver.com> wrote: > 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 > > ============ > > > > *22-February-23* > > > > *Stx 9.0 Release* Tracking Spreadsheet created: > https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing > > *StarlingX 8.0 Release*: - February 22nd - Delivered on time. > > NOTE: Worked with the OpenDev community to fix a zuul issue, that was > hindering publish of the Stx 8.0 Release > > - Modify the following page to include Stx 8.0 > > > https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html > - AR Ron - DONE > > > https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 > - Need to include Stx 8.0 - AR Ron - DONE > > To add Stx 8.0 in the Version drop-down - DONE > > *Gerrit Reviews* ; https://review.opendev.org/c/starlingx/docs/+/873258; > > To automate New Features from the Stx 8.0 RN into the StarlingX > Introduction Guide (StarlingX specific) - AR Juanita - DONE > > - Stx 8.0 Release Notes WIP - > https://review.opendev.org/c/starlingx/docs/+/873563 - DONE (Cherry > picked to Stx 8.0) > > events.yaml - Applies to 8.0 and release going forward > > - Reviewers need to refer to > https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to > view updated alarms and log files. > > - To raise a Defect to fix the events.yaml file > https://opendev.org/starlingx/fault/src/branch/master/fm-doc/fm_doc/events.yaml > to update the "Context" field wherever applicable to "OpenStack" (For > example; 100.105 100.112 and 100.113) ; DONE - Greg sent an email to the > StarlingX Community on February 22nd. > > - 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 > / 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?? - Completed the flattening of the > TOC.....Flattening of TOC not being implemented on older branches. > Simplified on stx 6.0 / stx 7.0 (makes cherry picks easier) > > *Gerrit Reviews: * > > - Open Reviews pending; > https://review.opendev.org/q/starlingx/docs+status:open - Merged 1 Review > > https://review.opendev.org/c/starlingx/docs/+/872912 - Review merged but > Zuul failed...content is not appearing in output file; Ron AR > > - Elisa raised an issue with a merged review and there was a build failure > ? The issue was sorted out > > *Launchpad Doc Bugs: * > > - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 > bugs outstanding - The DOC team to create LP defects corresponding with any > DS defects - WIP. Teams to add all the impacted Releases when raising a LP > bug > > Gabriel joined the docs call and raised an update for the Stx docs - > Gabriel to raise a LP Bug. > > *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:* > > - Sphinx Tools - Need to have further discussions about the version used > upstream vs. downstream - AR Ron -To determine version. > > - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron > > - Operations Guide Archive - On Hold until further clarifications are > discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) > > - OpenInfra Summit & PTG: June 13-15, Vancouver, Canada - > https://openinfra.dev/summit/vancouver-2023/ > > - Workshop Details are tracked in > https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 > > - Virtual PTG ... March 27-31, 2023 > > Etherpad for Virtual PTG Planning: > https://etherpad.opendev.org/p/stx-ptg-planning-march-2023 > > > > ____________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > -- Thanks, Rajesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From FlavioLuis.Peres at windriver.com Mon Feb 27 20:53:55 2023 From: FlavioLuis.Peres at windriver.com (Peres, Flavio Luis) Date: Mon, 27 Feb 2023 20:53:55 +0000 Subject: [Starlingx-discuss] - add new core to rook-ceph repo In-Reply-To: References: <07F82084-DA8B-4EC5-B91A-242CE2AE746A@openstack.org> Message-ID: + @Cardoso Sganderlla, Daian Hello, Do you have any updates here? Can we have Daian added to that repo? I am including him here to follow up during my vacations. Thanks Flavio Peres Software Development Manager Campinas, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] From: Voiculeasa, Dan Sent: Friday, February 10, 2023 12:51 PM To: Ildiko Vancsa; Miller, Frank; Sun, Austin; Chen, Haochuan Z; Sabeel.Ansari at windriver.com Cc: Peres, Flavio Luis; StarlingX ML Subject: Re: [Starlingx-discuss] - add new core to rook-ceph repo +1 Looked at the activity of Austin and Haochuan and Sabeel, looks empty will remove them. There are only 2 active cores now. Thanks, Dan Voiculeasa From: Ildiko Vancsa Sent: Friday, February 10, 2023 5:06 PM To: Miller, Frank Cc: Peres, Flavio Luis ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com ; StarlingX ML Subject: Re: [Starlingx-discuss] - add new core to rook-ceph repo 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 Flavio and All, Thank you for taking the topic to the StarlingX mailing list! I corrected the mailing list address as accidentally the ?starlingx-discuss-owners? list was used, which addresses the mailing list moderators. As a reminder, the address of the starlingx-discuss mailing list is: starlingx-discuss at lists.starlingx.io Once the existing core reviewers agreed on the proposal, Daian can be added to the group in Gerrit by any core reviewer in the group. Please let me know if I can help with anything else. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 10, 2023, at 16:00, Miller, Frank wrote: > > I support having Daian added as a Core to this repo as he is a member of the team working on storage. I also request that Cores no longer with StarlingX be removed: Sabeel Ansari, Chen Haochuan, Austin Sun. > > Frank > > From: Peres, Flavio Luis > Sent: Friday, February 10, 2023 9:20 AM > To: starlingx-discuss-owner at lists.starlingx.io > Cc: Miller, Frank ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com; Voiculeasa, Dan > Subject: [Starlingx-discuss] - add new core to rook-ceph repo > > Hi, > > Could you please add Daian as a core on the rook-ceph repo: https://review.opendev.org/admin/groups/c94564620ec9d3284ecd2abc67884d200cd9d843,members > > Daian was the dev who implemented rook-ceph. He is indicated to be the Core reviewer on this repo. > > Thanks > > Flavio Peres > Software Development Manager > Campinas, BR > > > > From: starlingx-discuss-owner at lists.starlingx.io > Sent: Wednesday, November 17, 2021 2:50 PM > To: Peres, Flavio Luis > Subject: Your message to Starlingx-discuss awaits moderator approval > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Your mail to 'Starlingx-discuss' with the subject > > RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20211117T032111Z > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. If you would like to cancel > this posting, please visit the following URL: > > http://lists.starlingx.io/cgi-bin/mailman/confirm/starlingx-discuss/70f579fa625eb7487b4baa41761d974f15bcd815 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 22A4EC78CE3047D7B52BFC982107780D[29653446].png Type: image/png Size: 1808 bytes Desc: 22A4EC78CE3047D7B52BFC982107780D[29653446].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9AE6EB2566C44A1B80F8FECB53849A70[29653447].png Type: image/png Size: 18480 bytes Desc: 9AE6EB2566C44A1B80F8FECB53849A70[29653447].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 5BA86DB6FD1E472BA4F37D2D6B0C456D.png Type: image/png Size: 144 bytes Desc: 5BA86DB6FD1E472BA4F37D2D6B0C456D.png URL: From Juanita.Balaraj at windriver.com Tue Feb 28 03:07:14 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Tue, 28 Feb 2023 03:07:14 +0000 Subject: [Starlingx-discuss] [docs] [meeting] March 1st Cancelled In-Reply-To: References: Message-ID: Hello All, The StarlingX Doc Team Meeting on March 1st is cancelled. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ ____________________ 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 ildiko at openstack.org Tue Feb 28 08:18:23 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 28 Feb 2023 09:18:23 +0100 Subject: [Starlingx-discuss] TSC & Community Call is in APAC time slot this week! Message-ID: <916E654B-54BE-454E-BFFC-91C55E8775AF@openstack.org> Hi StarlingX Community, It is a friendly reminder that the TSC & Community call is happening in the APAC-friendly time slot this week! The call is scheduled to happen on March 1st at 7pm Pacific Time / 10m pm Eastern Time | March 2nd at 0300 UTC / 11am China Standard Time. You can find dial-in information and further details here: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From Daian.CardosoSganderlla at windriver.com Tue Feb 28 12:07:06 2023 From: Daian.CardosoSganderlla at windriver.com (Cardoso Sganderlla, Daian) Date: Tue, 28 Feb 2023 12:07:06 +0000 Subject: [Starlingx-discuss] - add new core to rook-ceph repo In-Reply-To: References: <07F82084-DA8B-4EC5-B91A-242CE2AE746A@openstack.org> Message-ID: Hello all, I can confirm that I am already added as a member of starlingx-rook-ceph-core group. Thanks ________________________________ From: Peres, Flavio Luis Sent: Monday, February 27, 2023 5:53 PM To: Voiculeasa, Dan ; Ildiko Vancsa ; Miller, Frank ; Sun, Austin ; Chen, Haochuan Z ; Sabeel.Ansari at windriver.com ; Cardoso Sganderlla, Daian Cc: StarlingX ML Subject: RE: [Starlingx-discuss] - add new core to rook-ceph repo + @Cardoso Sganderlla, Daian Hello, Do you have any updates here? Can we have Daian added to that repo? I am including him here to follow up during my vacations. Thanks Flavio Peres Software Development Manager Campinas, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] From: Voiculeasa, Dan Sent: Friday, February 10, 2023 12:51 PM To: Ildiko Vancsa; Miller, Frank; Sun, Austin; Chen, Haochuan Z; Sabeel.Ansari at windriver.com Cc: Peres, Flavio Luis; StarlingX ML Subject: Re: [Starlingx-discuss] - add new core to rook-ceph repo +1 Looked at the activity of Austin and Haochuan and Sabeel, looks empty will remove them. There are only 2 active cores now. Thanks, Dan Voiculeasa From: Ildiko Vancsa Sent: Friday, February 10, 2023 5:06 PM To: Miller, Frank Cc: Peres, Flavio Luis ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com ; StarlingX ML Subject: Re: [Starlingx-discuss] - add new core to rook-ceph repo 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 Flavio and All, Thank you for taking the topic to the StarlingX mailing list! I corrected the mailing list address as accidentally the ?starlingx-discuss-owners? list was used, which addresses the mailing list moderators. As a reminder, the address of the starlingx-discuss mailing list is: starlingx-discuss at lists.starlingx.io Once the existing core reviewers agreed on the proposal, Daian can be added to the group in Gerrit by any core reviewer in the group. Please let me know if I can help with anything else. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Feb 10, 2023, at 16:00, Miller, Frank wrote: > > I support having Daian added as a Core to this repo as he is a member of the team working on storage. I also request that Cores no longer with StarlingX be removed: Sabeel Ansari, Chen Haochuan, Austin Sun. > > Frank > > From: Peres, Flavio Luis > Sent: Friday, February 10, 2023 9:20 AM > To: starlingx-discuss-owner at lists.starlingx.io > Cc: Miller, Frank ; Voiculeasa, Dan ; Sabeel.Ansari at windriver.com; Voiculeasa, Dan > Subject: [Starlingx-discuss] - add new core to rook-ceph repo > > Hi, > > Could you please add Daian as a core on the rook-ceph repo: https://review.opendev.org/admin/groups/c94564620ec9d3284ecd2abc67884d200cd9d843,members > > Daian was the dev who implemented rook-ceph. He is indicated to be the Core reviewer on this repo. > > Thanks > > Flavio Peres > Software Development Manager > Campinas, BR > > > > From: starlingx-discuss-owner at lists.starlingx.io > Sent: Wednesday, November 17, 2021 2:50 PM > To: Peres, Flavio Luis > Subject: Your message to Starlingx-discuss awaits moderator approval > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Your mail to 'Starlingx-discuss' with the subject > > RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO > 20211117T032111Z > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. If you would like to cancel > this posting, please visit the following URL: > > http://lists.starlingx.io/cgi-bin/mailman/confirm/starlingx-discuss/70f579fa625eb7487b4baa41761d974f15bcd815 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 22A4EC78CE3047D7B52BFC982107780D[29653446].png Type: image/png Size: 1808 bytes Desc: 22A4EC78CE3047D7B52BFC982107780D[29653446].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9AE6EB2566C44A1B80F8FECB53849A70[29653447].png Type: image/png Size: 18480 bytes Desc: 9AE6EB2566C44A1B80F8FECB53849A70[29653447].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 5BA86DB6FD1E472BA4F37D2D6B0C456D.png Type: image/png Size: 144 bytes Desc: 5BA86DB6FD1E472BA4F37D2D6B0C456D.png URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Feb 28 12:43:44 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 28 Feb 2023 12:43:44 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER Build ISO [20230226T070000Z] results - Feb-28 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack sanity using the Feb-26 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230226T070000Z/outputs/iso/starlingx-intel-x86-64-cd.iso and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230226T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.43-debian-stable-versioned.tgz Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 14 (93.33%) Failed: 1 (6.67%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230228 05:43:34 test_ssh_to_hosts PASS 20230228 05:45:20 test_lock_unlock_host PASS 20230228 06:03:44 test_openstack_services_healthy PASS 20230228 06:04:48 test_reapply_stx_openstack_no_change[controller-0] PASS 20230228 06:06:51 test_reapply_stx_openstack_no_change[controller-1] PASS 20230228 06:16:17 test_horizon_create_delete_instance PASS 20230228 06:21:49 test_swact_controllers PASS 20230228 06:32:23 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS 20230228 06:39:19 test_migrate_vm[tis-centos-guest-live-None] PASS 20230228 06:44:25 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS 20230228 06:49:08 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230228 06:53:45 test_evacuate_vms PASS 20230228 07:29:44 test_system_coredumps_and_crashes[core_dumps] PASS 20230228 07:30:02 test_system_coredumps_and_crashes[crash_reports] PASS 20230228 07:30:13 test_system_alarms ----------------------------------------------------------------------- The failed test was due to the following issue: * https://bugs.launchpad.net/starlingx/+bug/2007303 - STX-Openstack: "nova live-migration" fails to live migrate after host is forcefully turned off/on Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From voipas at gmail.com Tue Feb 28 14:32:31 2023 From: voipas at gmail.com (voipas) Date: Tue, 28 Feb 2023 16:32:31 +0200 Subject: [Starlingx-discuss] deploy starlingx simplex on Intel NUC Message-ID: Hey, I would like to deploy the latest version of Starlingx on Intel NUC12WSKi5 with 32 GB RAM storage, I have Disk1: 2 TB disk and Disk2: 500 GB. According to your documentation, it is required to have a minimum two interfaces, NUC only has single. That's why I have USB Ethernet. According to this article - https://github.com/marcelarosalesj/learning-starlingx/blob/master/nuc.md - I need patch starlingx kernel and create a boot disk (as per my understanding directly downloaded ISO does not have such kernel modules). So my question is : - might there be a way to deploy with a single network , and no additional ports required (to play and learn at home in simplex mode)? - for home lab, might it be better to install proxmox and create a VM and install Starlingx? - If no, do you have the latest developer document , how can we build a custom iso with USB Ethernet? Now it looks old and for Centos, not debian... Thanks in advance -- Best Regards, Giedrius -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Feb 28 19:05:45 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 28 Feb 2023 19:05:45 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230226T070000Z Message-ID: Sanity Test from 2023 February 28 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230226T070000Z/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] DX lab is not available this week. We will resume DX sanity next week. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: