From openinfradn at gmail.com Mon Aug 1 13:17:35 2022 From: openinfradn at gmail.com (open infra) Date: Mon, 1 Aug 2022 18:47:35 +0530 Subject: [Starlingx-discuss] What is the base OS for Starlingx Release 6 In-Reply-To: References: Message-ID: I am suppose to install nvidia driver on a worker (stx 6) which require few dependencies including gcc and make. When I use CentOS 7 nvidia driver compilation/installation fails and with Rocky linux 9 gcc installation fails. On Thu, Jul 28, 2022 at 4:01 PM open infra wrote: > Hi, > > Which CentOS release is the compatible with STX release boot image? > > Regards, > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Aug 2 05:42:32 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 2 Aug 2022 01:42:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 932 - Failure! Message-ID: <1259900951.249.1659418953705.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 932 Status: Failure Timestamp: 20220802T040558Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220802T040558Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Tue Aug 2 05:42:27 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 2 Aug 2022 01:42:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3009 - Failure! Message-ID: <768306376.246.1659418950239.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3009 Status: Failure Timestamp: 20220802T044546Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220802T040558Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20220802T040558Z DOCKER_BUILD_ID: jenkins-master-distro-20220802T040558Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220802T040558Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20220802T040558Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From starlingx.build at gmail.com Tue Aug 2 08:13:16 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 2 Aug 2022 04:13:16 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1510 - Failure! Message-ID: <312344653.252.1659427997276.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1510 Status: Failure Timestamp: 20220802T044548Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220802T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220802T043001Z DOCKER_BUILD_ID: jenkins-master-20220802T043001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220802T043001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220802T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Tue Aug 2 08:13:20 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 2 Aug 2022 04:13:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1367 - Failure! Message-ID: <1712818738.255.1659428001347.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1367 Status: Failure Timestamp: 20220802T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220802T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Peng.Peng at windriver.com Tue Aug 2 19:02:09 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 2 Aug 2022 19:02:09 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 220220730T061231Z Message-ID: Sanity Test from 2022-August 2nd (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220730T061231Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220730T061231Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Wed Aug 3 02:15:23 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 2 Aug 2022 22:15:23 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 4 - Still Failing! In-Reply-To: <58127868.231.1659233619394.JavaMail.javamailuser@localhost> References: <58127868.231.1659233619394.JavaMail.javamailuser@localhost> Message-ID: <1946069725.263.1659492925462.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 4 Status: Still Failing Timestamp: 20220803T014405Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220803T014405Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ildiko.vancsa at gmail.com Wed Aug 3 07:06:32 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 3 Aug 2022 09:06:32 +0200 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - NEW POLL In-Reply-To: References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> Message-ID: Hi, I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe __Please submit your preferences by August 14, 2022.__ As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: > > Hi Greg, > > I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. > > Best Regards, > Ildik? > > >> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >> >> I can't find the zoom link for the meeting ... do you have it ? >> Greg. >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Wednesday, July 27, 2022 2:16 AM >> To: Waines, Greg >> Cc: StarlingX ML >> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Hi Greg, >> >> Great, thank you for being available! >> >> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >> >> I think diversity is a great topic for the call and should be a basis for a good discussion. >> >> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >> >> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>> >>> hey Ildiko, >>> I am available on the Aug 4 1300 UTC timeslot. >>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>> >>> I added our favourite discussion topic to the etherpad: >>> * Looking for guidance on diversifying the Users and >>> Contributors in the community >>> >>> Greg. >>> >>> -----Original Message----- >>> From: Ildiko Vancsa >>> Sent: Tuesday, July 26, 2022 5:47 AM >>> To: StarlingX ML >>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>> StarlingX Sync - UPDATE >>> >>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>> >>> Hi StarlingX Community, >>> >>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>> >>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>> >>> You can see the original email and follow the thread here: >>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>> 6.html >>> >>> As a reminder, we have an etherpad to propose topics for the call and >>> take notes during the meeting: >>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> Please let me know if you have any questions. >>> >>> Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>> >>>> Hi StarlingX Community, >>>> >>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>> >>>> You can find the poll here: >>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>> >>>> __Please submit your preferences on the poll by the end of day on >>>> July 20, 2022.__ >>>> >>>> >>>> I created an etherpad to collect potential topics for the >>>> conversation and build an agenda for the call. Please add discussion >>>> points that you think would be important to bring up during the call: >>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>> >>>> Please let me know if you have any questions. >>>> >>>> Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>> >>>> >>>> >>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>> >>>>> Hi StarlingX Community, >>>>> >>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>> >>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>> >>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>> >>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>> >>>>> I created an etherpad to collect potential topics for the >>>>> conversation and build an agenda for the call: >>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>> >>>>> I also created a poll to try to find time slot options that we can >>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>> options for August, if we fail to find good options for that month, I >>>>> will extend it to September. Please find the poll here: >>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>> >>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>> >>>>> __Please submit your preferences by the end of day on July 20, >>>>> 2022.__ >>>>> >>>>> Please let me know if you have any questions. >>>>> >>>>> Best Regards, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > From starlingx.build at gmail.com Wed Aug 3 08:31:24 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 3 Aug 2022 04:31:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3014 - Failure! Message-ID: <252315976.267.1659515488626.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3014 Status: Failure Timestamp: 20220803T045716Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220803T044302Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20220803T044302Z DOCKER_BUILD_ID: jenkins-master-distro-20220803T044302Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220803T044302Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20220803T044302Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From starlingx.build at gmail.com Wed Aug 3 08:31:31 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 3 Aug 2022 04:31:31 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_distro_master_master - Build # 933 - Still Failing! In-Reply-To: <1981733701.247.1659418951126.JavaMail.javamailuser@localhost> References: <1981733701.247.1659418951126.JavaMail.javamailuser@localhost> Message-ID: <1352910403.270.1659515492914.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 933 Status: Still Failing Timestamp: 20220803T044302Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20220803T044302Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Wed Aug 3 08:36:46 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 3 Aug 2022 04:36:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1368 - Still Failing! In-Reply-To: <804516728.253.1659427998517.JavaMail.javamailuser@localhost> References: <804516728.253.1659427998517.JavaMail.javamailuser@localhost> Message-ID: <1343707379.276.1659515807113.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1368 Status: Still Failing Timestamp: 20220803T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220803T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Wed Aug 3 08:36:41 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 3 Aug 2022 04:36:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1511 - Still Failing! In-Reply-To: <347849467.250.1659427993270.JavaMail.javamailuser@localhost> References: <347849467.250.1659427993270.JavaMail.javamailuser@localhost> Message-ID: <381125513.273.1659515803130.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1511 Status: Still Failing Timestamp: 20220803T044222Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220803T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220803T043001Z DOCKER_BUILD_ID: jenkins-master-20220803T043001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220803T043001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220803T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From ildiko.vancsa at gmail.com Wed Aug 3 14:18:36 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 3 Aug 2022 16:18:36 +0200 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: Hi StarlingX Community, I?m reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation From Juanita.Balaraj at windriver.com Wed Aug 3 21:27:00 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 3 Aug 2022 21:27:00 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 03-August-22 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 03-August-22 StarlingX 7.0 Release: - Stx 7.0 GA date is July 25th - AR Juanita to review Stx 7.0 Release checklist (Release: week of July 25 >> week of Aug 1) - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date Gerrit Reviews: - 2 Cherry picks this week. Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - https://review.opendev.org/c/starlingx/docs/+/849003 - AR Juanita to confirm if this needs to be cherrypicked to dsr6 - https://review.opendev.org/c/starlingx/docs/+/851209 - Synched with Litao Gao. This update is STARLINGX Only. Needs to be reviewed and approved by the Docs team for formatting, etc. - https://review.opendev.org/c/starlingx/docs/+/822546 - The community to ensure to add Reviewers for each Gerrit review created - https://bugs.launchpad.net/starlingx/+bug/1982058 - Triaged 3 new bugs, 3 are WIP. Total 12 bugs. Launchpad Doc Bugs: - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold - https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa General: - Operations Guide Archive - On Hold until further clarifications are discussed (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 ElisamaraAoki.Goncalves at windriver.com Wed Aug 3 21:33:01 2022 From: ElisamaraAoki.Goncalves at windriver.com (Goncalves, Elisamara Aoki) Date: Wed, 3 Aug 2022 21:33:01 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: Hi Scott, Can you review the update https://review.opendev.org/c/starlingx/docs/+/851084 requested by Chandan Kumar? Chandan has a few questions, so as soon as you review it, I can address those and close the update. Thanks! Elisa. ________________________________ From: Balaraj, Juanita Sent: Wednesday, July 27, 2022 4:43 PM To: Kumar, Chandan ; Waines, Greg ; StarlingX ML ; Little, Scott Cc: Goncalves, Elisamara Aoki Subject: RE: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . + Elisa FYI Related to Gerrit Review https://review.opendev.org/c/starlingx/docs/+/851084 Thanks Juanita From: Kumar, Chandan Sent: July 27, 2022 9:57 AM To: Waines, Greg ; StarlingX ML ; Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, I was going through the procedure that you have shared below. Please clarify these two points: * The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. : The signing server unpacks images like BOOTX64, shim, shimx64 to get rpms, then signs it using `sbsign` and then repack it as original image. Is this understanding correct ? * shim.crt - Certificated embedded within shim used to validate kernel, grub : How is this certificate embedded inside shim image ? I got review notification for launchpad, I had raised but could not find where to add comments so replying to this mail. Regards, Chandan Kumar. From: Waines, Greg > Sent: Wednesday, July 13, 2022 8:14 PM To: StarlingX ML > Cc: Kumar, Chandan > Subject: FW: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Forwarding ?. I think scott meant this for the starlingx discuss list. Greg. From: Little, Scott > Sent: Wednesday, July 6, 2022 2:37 PM To: Waines, Greg > Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . I'll attempt to answer this at a high level. Secure boot signing uses a client/server approach. build-pkgs acts as the client. The server holds the signing scripts and the keys used for signing. The client side code was released to open source as part of StarlingX. The server side code was not released. The interface between client and server is currently undocumented. I'll try to give an overview as best I can. Basically it is a series of ssh/scp calls made into signing server. 'build-pkgs' requires that the following environment variables be defined before it will attempt to request a secure boot signing. export SIGNING_SERVER= export SIGNING_USER= export SIGNING_SERVER_SCRIPT= 'build-pkgs' further requires that "$USER" == "jenkins", and export FORMAL_BUILD=1 If that is satisfied, it calls into 'sign-secure-boot' 'sign-secure-boot' contains a fairly good set of comments describing what happens next. The client side call sequence looks like this ... # Set up the server side directory for files transfers. UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -r` # upload the original package scp -q $FILE $SIGNING_USER@$SIGNING_SERVER:$UPLOAD_PATH # Request that the package be signed ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -v -i $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t $TYPE > $TMPFILE # Download the file from the signing server DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE) scp -q $SIGNING_USER@$SIGNING_SERVER:$OUTPUT_FILE $(dirname $FILE) Within the signing server there are two keys used for signing, known as the 'boot' key and the 'shim' key. The public half of the 'boot' key must manually added to the secure boot keychain in firmware. The 'boot' key signs first executable loaded, contained in the 'shim' package. The first executable must then install the public half of the shim key (automatically) before passing control to grub, and ultimately the kernel, both of which are signed by the 'shim' key. Three packages need to be passed to the signing server. The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. package key files to sign ========= ==== =========================== shim boot BOOTX64, shim, shimx64 shim MokManager, fallback, mmx64, fbx64 grub shim grubx64.efi, gcdx64.efi kernel shim vmlinuz NOTE: shim files to sign might include a '.efi' or '.EFI' suffix. Sign those as well. NOTE: some files may be absent in newer packages. It is probably ok if some of the above are missing. Signing looks like this ... sbsign --key $KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt --output $SIGNEDFILE $UNSIGNEDFILE On keys and certs ... boot.crt - Certificate to boot (to be programmed in firmware) boot.key - Private key with which to sign shim shim.crt - Certificated embedded within shim used to validate kernel, grub shim.key - Private key with which to sign kernel/grub key generation ... openssl req -new -x509 -newkey rsa:2048 -keyout $KEY.key -out $KEY.pem -days 3650 openssl x509 -in $KEY.pem -out $KEY.crt -outform DER Note: boot.crt should be copied to cgcs-root/build-tools/certificates/TiBoot.crt for inclusion during the 'build-iso' step Hope this helps Scott On 2022-07-05 03:19, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, Thanks for acknowledgement. I have raised starlingx launchpad for document update. Meanwhile it would be really great if you can share the steps which has to be done to integrate signing of images as part of StarlingX build infrastructure. Regards, Chandan Kumar. From: Waines, Greg Sent: Monday, July 4, 2022 6:00 PM To: starlingx-discuss at lists.starlingx.io Cc: Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little > Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Thu Aug 4 10:57:00 2022 From: openinfradn at gmail.com (open infra) Date: Thu, 4 Aug 2022 16:27:00 +0530 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: On Wed, Aug 3, 2022 at 7:57 PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you with an update regarding alternating the TSC & > Community call times. > > > The favored alternate time slot, based on the poll below, is: Wednesdays > at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. > +1 > > We still need to decide on cadence to alternate the time slots. Options > include: > > * Alternate the time slots bi-weekly > * Have the APAC friendly call every first Wednesday of the month > Just a personal feedback, Some time ago, I used to join the community call if I need to clarify something if no response over the community mail. At that time, weekly call was really useful. > In order to find the choice that is preferred by the majority of > contributors, please send a reply with your preference (either one from the > above list or any other option that would work for you)! > > __Please share your preference on cadence by the end of day next Tuesday > (August 08).__ > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > On Jul 14, 2022, at 22:02, Ildiko Vancsa > wrote: > > > > Hi StarlingX Community, > > > > I?m reaching out to you about a topic that we discussed during the TSC & > Community call this week. > > > > It was raised that the time of the meeting is very inconvenient in the > APAC region and it prevents our TSC members and contributors in that area > from actively participating. The idea is to start alternating the call > times and provide a better opportunity for everyone in the global community > to participate in the calls. > > > > I created a poll to find a time slot option that works for most: > https://doodle.com/meeting/participate/id/aAnlZE9b > > > > __Please fill it out for by the end of next week (July 24).__ > > > > Please mark ALL the time slots that would work for you on an ongoing > basis, independently from the dates displayed in the poll! > > > > Please let me know if you have any questions. > > > > Best Regards, > > Ildik? > > > > ??? > > > > Ildik? V?ncsa > > Senior Manager, Community & Ecosystem > > Open Infrastructure Foundation > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From outbackdingo at gmail.com Thu Aug 4 11:15:04 2022 From: outbackdingo at gmail.com (Outback Dingo) Date: Thu, 4 Aug 2022 18:15:04 +0700 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: On Thu, Aug 4, 2022 at 6:05 PM open infra wrote: > > > > On Wed, Aug 3, 2022 at 7:57 PM Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> I?m reaching out to you with an update regarding alternating the TSC & Community call times. >> > >> >> The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. > > +1 >> >> >> We still need to decide on cadence to alternate the time slots. Options include: >> >> * Alternate the time slots bi-weekly >> * Have the APAC friendly call every first Wednesday of the month > > Just a personal feedback, > Some time ago, I used to join the community call if I need to clarify something if no response over the community mail. > At that time, weekly call was really useful. > i agree, weekly, and we dont all live in the states or Europe :) >> >> In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! >> >> __Please share your preference on cadence by the end of day next Tuesday (August 08).__ >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >> > On Jul 14, 2022, at 22:02, Ildiko Vancsa wrote: >> > >> > Hi StarlingX Community, >> > >> > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. >> > >> > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. >> > >> > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b >> > >> > __Please fill it out for by the end of next week (July 24).__ >> > >> > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! >> > >> > Please let me know if you have any questions. >> > >> > Best Regards, >> > Ildik? >> > >> > ??? >> > >> > Ildik? V?ncsa >> > Senior Manager, Community & Ecosystem >> > Open Infrastructure Foundation >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Aug 4 12:15:19 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 4 Aug 2022 12:15:19 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Aug 3 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Aug 3 2022 Standing topics - Build - r/stx.7.0 Builds - Status of the build: We had one successful build, but the Aug 3 build failed. Scott will investigated and retry the build. - Build Failure Email (Container Builds): https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013212.html - Build Cadence: Scheduled daily. The build tries to abort if it detects no changes, but this is a best effort mechanism - Main Branch CentOS Builds - Main build failed twice due to a failure to build a python-gnocchi package. - Issue is investigation. LP: https://bugs.launchpad.net/starlingx/+bug/1983389 - Main Branch Debian Builds - No failures. Aug 2 build was successful. Aug 3 build is in progress. - Sanity - Main Sanity w/o stx-openstack - Scheduled to run once a week. Runs on Monday evening and the report is sent out on Tuesday. - Latest Report (Aug 2) is Green: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013211.html - Sanity w/ stx-openstack - Is unblocked as of July 21 - Working on setting up sanity w/ stx-openstack. The goal is to have the first execution within the next two weeks. Fcst: Aug 16 - Sanity on the r/stx.7.0 RC builds - Should be a simple change to point to an alternative build directory. - Will start running sanity on the r/stx.7.0 starting next week: Aug 8 and continue until stx.7.0 is released. - Action: Scott to ensure the sanity emails are tied to the CENGN "Green" build update mechanism. - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes: https://review.opendev.org/c/starlingx/docs/+/850424 - stx-doc reviews: https://review.opendev.org/q/starlingx/docs+status:open - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Next Steps - Branch is created - https://review.opendev.org/q/branch:r/stx.7.0 - A few reviews are still open: https://review.opendev.org/q/branch:r/stx.7.0+status:open - These are required to allow future submissions to the affected repos. - Action: Scott/Al to follow up on related zuul failures for these reviews. - Bug Fixes tagged for stx.7.0 have been cherrypicked: - LP: https://bugs.launchpad.net/starlingx/+bug/1982220 / review: https://review.opendev.org/c/starlingx/openstack-armada-app/+/851518 - merged/cherrypicked July 29 - LP: https://bugs.launchpad.net/starlingx/+bug/1981368 / review: https://review.opendev.org/c/starlingx/tools/+/851376 - merged/cherrypicked July 28 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - Only one outstanding LP: https://bugs.launchpad.net/starlingx/+bug/1970645 - Issue was reported by Intel sanity in April, but is not reproducible by the dev team. Agreed to close as Not Reproducible. - If new issues are found during stx-openstack sanity in WR, the LP can be re-opened or a new LP can be created. - Milestone Re-forecast - Final Sanity/Regression and Release Milestone re-forecasted to align with the sanity plan. - Sanity/Final Regression: Aug 17 - Release: Aug 24 - (Ildiko) Feature the 7.0 release on OpenInfra Live - Looking for community volunteers to create an episode highlighting stx.7.0 features and the roadmap for stx.8.0 - The typical duration of an episode is up to one hour, but can be shorter. - (Ildiko) StarlingX - OpenInfra BoD sync will be moved to a later date - Polls are being moved out of the summer months - Request to community members to fill the polls. Email sent to the mailing list as well. - Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe - Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe - FYI - Upcoming Vacations - Ghada: Aug 6 - 21 - Greg: Aug 10 - 15 - SteveG: Aug 8 - 12 - Next Release Planning & TSC/Community meetings are on Aug 10. Ildiko will chair both meetings on Aug 10. ARs from Previous Meetings - None Open Requests for Help - Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html - Greg to respond - Wireguard not enabled in stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013170.html - Requested the OS team to respond From Ghada.Khalil at windriver.com Thu Aug 4 13:04:08 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 4 Aug 2022 13:04:08 +0000 Subject: [Starlingx-discuss] stx.8.0 planning started / Request for proposed content Message-ID: Hello all, The StarlingX release team is starting to plan the next StarlingX release: stx.8.0. This email is to solicit input on feature content. If you / your team have a feature you'd like to propose/contribute to stx.8.0, please let us know. stx.8.0 Planning Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 All is welcome to join us in the bi-weekly planning meeting on Wednesdays at 9:30am Eastern: https://wiki.openstack.org/wiki/Starlingx/Meetings#6:30am_Pacific_-_Release_Team_Call_.28Bi-weekly.29 The next meeting is on August 10. Best Regards, Ghada (on behalf of the stx release team) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Aug 4 13:11:02 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 4 Aug 2022 13:11:02 +0000 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: My preference is option 2 - Have the APAC friendly call every first Wednesday of the month -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, August 3, 2022 10:19 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I?m reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ThalesElero.Cervi at windriver.com Thu Aug 4 13:13:49 2022 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Thu, 4 Aug 2022 13:13:49 +0000 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: I also vote for option 2: Have the APAC friendly call every first Wednesday of the month ________________________________ From: Ildiko Vancsa Sent: Wednesday, August 3, 2022 11:18 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I?m reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Thu Aug 4 13:04:40 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Thu, 4 Aug 2022 13:04:40 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS Meeting Minutes: June 22, July 6, and July 20, 2022 Message-ID: Hi, Below are the Meeting minutes for the OS Distro & Multi-OS meetings Next meeting: Aug 3, 2022 07/20/2022 Attendees: Mark A., Charles Short, Linda W. 1. Persistent storage 1. using OS Tree for updating, but when pulling delta updates, it does not cover /var directory, and currently patching in the files in /var directory. 1. This issue came up for 22.06, but didn't want to create more issues, so patched 22.06, but need to fix it right in LAT/OSTree for 22.12. 1. There is already a bug created, targeted 22.12. 1. StarlingX 8.0 1. Any changes/requirements that we need to be aware of? 07/06/2022 Cancelled. 06/22/2022 Attendees: Charles S., Mark A., Davelet, Linda Not enough attendees to form a quorum. Meeting cancelled. Thanks, Linda -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Thu Aug 4 13:07:24 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Thu, 4 Aug 2022 13:07:24 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting Minutes: Aug 3, 2022 Message-ID: 08/03/2022 Attendees: Mark A., Scott Little, Charles Short, Davlet P, Steve G, Linda W. 1. StarlingX 8.0 1. Any changes/requirements that we need to be aware of? 2. Persistent Storage 1. resolved within the email thread 3. Build System improvement 1. Build time taking long issue 1. patch submitted for review for using cache to reduce build time, and parallel builds 1. CNGN build time dropped to 11 hrs. <- what got check-in? 1. With parallel builds, it went down to 3 hrs build time. (7.5 hrs to 6 hrs, may need to enable some config option to enable parallel builds?) 1. Another possible improvement: use ramfs to do the build, if there is enough memory to use 1. Option to disable "chroot" sharing which takes up time during build, need to disable chroot sharing to reduce build time. 4. Kernel Live patching 1. Yue's team to reach out to see what needs to be integrated with build system/pkging and puppet boot up initramfs script Next Meeting: Aug 10, 2022 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Douglas.Pereira at windriver.com Thu Aug 4 13:27:35 2022 From: Douglas.Pereira at windriver.com (Pereira, Douglas) Date: Thu, 4 Aug 2022 13:27:35 +0000 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: Another vote for option 2: Have the APAC friendly call every first Wednesday of the month Regards, Doug From: Cervi, Thales Elero Sent: Thursday, August 4, 2022 10:14 AM To: Ildiko Vancsa ; StarlingX ML Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED I also vote for option 2: Have the APAC friendly call every first Wednesday of the month ________________________________ From: Ildiko Vancsa > Sent: Wednesday, August 3, 2022 11:18 AM To: StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I'm reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? --- Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa > wrote: > > Hi StarlingX Community, > > I'm reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > --- > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Thu Aug 4 13:46:48 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 09:46:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 322 - Failure! Message-ID: <1719157161.8.1659620810977.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 322 Status: Failure Timestamp: 20220804T132009Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T131939Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220804T131939Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T131939Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220804T131939Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220804T131939Z LAYER: build-containers REGISTRY: docker.io From starlingx.build at gmail.com Thu Aug 4 14:21:58 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 10:21:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 324 - Failure! Message-ID: <388586659.12.1659622920002.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 324 Status: Failure Timestamp: 20220804T142155Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T142148Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220804T142148Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T142148Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220804T142148Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220804T142148Z LAYER: build-containers REGISTRY: docker.io From starlingx.build at gmail.com Thu Aug 4 14:27:51 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 10:27:51 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 326 - Failure! Message-ID: <2049926609.16.1659623272229.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 326 Status: Failure Timestamp: 20220804T142748Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T142721Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220804T142721Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220804T142721Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220804T142721Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220804T142721Z LAYER: build-containers REGISTRY: docker.io From starlingx.build at gmail.com Thu Aug 4 20:29:51 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 16:29:51 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3022 - Failure! Message-ID: <1826539508.20.1659644992801.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3022 Status: Failure Timestamp: 20220804T201200Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220804T193210Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-flock/20220804T193210Z DOCKER_BUILD_ID: jenkins-rc-7.0-flock-20220804T193210Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-7.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220804T193210Z/logs BUILD_IMG: true FULL_BUILD: true PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/flock/20220804T193210Z/logs MASTER_JOB_NAME: STX_7.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-7.0-flock BUILD_ISO: true From starlingx.build at gmail.com Thu Aug 4 20:29:56 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 16:29:56 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 10 - Failure! Message-ID: <1826651530.23.1659644997366.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_flock Build #: 10 Status: Failure Timestamp: 20220804T193210Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220804T193210Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From starlingx.build at gmail.com Fri Aug 5 02:15:19 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 4 Aug 2022 22:15:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 5 - Still Failing! In-Reply-To: <1680188284.261.1659492922304.JavaMail.javamailuser@localhost> References: <1680188284.261.1659492922304.JavaMail.javamailuser@localhost> Message-ID: <761013682.31.1659665721084.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 5 Status: Still Failing Timestamp: 20220805T014236Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220805T014236Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Greg.Waines at windriver.com Fri Aug 5 12:48:40 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 5 Aug 2022 12:48:40 +0000 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: Another vote for option 2: Have the APAC friendly call every first Wednesday of the month From: Pereira, Douglas Sent: Thursday, August 4, 2022 9:28 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED Another vote for option 2: Have the APAC friendly call every first Wednesday of the month Regards, Doug From: Cervi, Thales Elero > Sent: Thursday, August 4, 2022 10:14 AM To: Ildiko Vancsa >; StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED I also vote for option 2: Have the APAC friendly call every first Wednesday of the month ________________________________ From: Ildiko Vancsa > Sent: Wednesday, August 3, 2022 11:18 AM To: StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I'm reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? --- Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa > wrote: > > Hi StarlingX Community, > > I'm reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > --- > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Fri Aug 5 13:14:49 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Fri, 5 Aug 2022 13:14:49 +0000 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: Another vote here as well for option 2. From: Waines, Greg Sent: Friday, August 5, 2022 8:49 AM To: Pereira, Douglas ; StarlingX ML Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED Another vote for option 2: Have the APAC friendly call every first Wednesday of the month From: Pereira, Douglas > Sent: Thursday, August 4, 2022 9:28 AM To: StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED Another vote for option 2: Have the APAC friendly call every first Wednesday of the month Regards, Doug From: Cervi, Thales Elero > Sent: Thursday, August 4, 2022 10:14 AM To: Ildiko Vancsa >; StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED I also vote for option 2: Have the APAC friendly call every first Wednesday of the month ________________________________ From: Ildiko Vancsa > Sent: Wednesday, August 3, 2022 11:18 AM To: StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I'm reaching out to you with an update regarding alternating the TSC & Community call times. The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. We still need to decide on cadence to alternate the time slots. Options include: * Alternate the time slots bi-weekly * Have the APAC friendly call every first Wednesday of the month In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! __Please share your preference on cadence by the end of day next Tuesday (August 08).__ Best Regards, Ildik? --- Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 22:02, Ildiko Vancsa > wrote: > > Hi StarlingX Community, > > I'm reaching out to you about a topic that we discussed during the TSC & Community call this week. > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > __Please fill it out for by the end of next week (July 24).__ > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > --- > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Fri Aug 5 17:51:55 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 5 Aug 2022 12:51:55 -0500 Subject: [Starlingx-discuss] Fwd: October PTG Update In-Reply-To: References: Message-ID: Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it?s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sun Aug 7 03:31:30 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 6 Aug 2022 23:31:30 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 6 - Still Failing! In-Reply-To: <188117910.29.1659665717803.JavaMail.javamailuser@localhost> References: <188117910.29.1659665717803.JavaMail.javamailuser@localhost> Message-ID: <1668805008.43.1659843091733.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 6 Status: Still Failing Timestamp: 20220807T014136Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220807T014136Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Sun Aug 7 09:05:12 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 7 Aug 2022 05:05:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1372 - Failure! Message-ID: <739822427.50.1659863113036.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1372 Status: Failure Timestamp: 20220807T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220807T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Sun Aug 7 09:05:08 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 7 Aug 2022 05:05:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1406 - Failure! Message-ID: <635934887.47.1659863109559.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1406 Status: Failure Timestamp: 20220807T090451Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220807T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220807T043000Z DOCKER_BUILD_ID: jenkins-master-20220807T043000Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220807T043000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220807T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From Greg.Waines at windriver.com Mon Aug 8 11:13:00 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 8 Aug 2022 11:13:00 +0000 Subject: [Starlingx-discuss] FW: October 2022 PTG Pivot In-Reply-To: References: Message-ID: FYI ? October PTG is 100% virtual. Greg. From: Kendall Nelson Sent: Friday, August 5, 2022 1:34 PM Subject: October 2022 PTG Pivot [Please note: This e-mail is from an EXTERNAL e-mail address] Hello, Thank you for signing your team up for the Columbus PTG. At this time, we have made the difficult decision to make the PTG 100% virtual. The PTG will still take place October 17-20. We will keep your team signed up, unless you indicate otherwise, and keep you updated on next steps. Registration is open and free, so please encourage your teams to register now [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. I will be sending an announcement to the MLs shortly. Thanks, Kendall Nelson (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Aug 8 13:40:12 2022 From: scott.little at windriver.com (Scott Little) Date: Mon, 8 Aug 2022 09:40:12 -0400 Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 10 - Failure! In-Reply-To: <1826651530.23.1659644997366.JavaMail.javamailuser@localhost> References: <1826651530.23.1659644997366.JavaMail.javamailuser@localhost> Message-ID: <367bde97-580b-2247-fcff-45dfd84e74ff@windriver.com> We now have a good build of the STX.7.0 iso http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/latest_build/outputs/iso/ On 2022-08-04 16:29, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_7.0_build_layer_flock > Build #: 10 > Status: Failure > Timestamp: 20220804T193210Z > Branch: r/stx.7.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220804T193210Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: true > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From vefa.bicakci at windriver.com Mon Aug 8 23:32:16 2022 From: vefa.bicakci at windriver.com (M. Vefa Bicakci) Date: Mon, 8 Aug 2022 19:32:16 -0400 Subject: [Starlingx-discuss] calicoctl / calico containers stx 6.0 aio duplex and wireguard - DONE! In-Reply-To: <1658752499190.46719352.2357280429@optimcloud.com> References: <1632974745542.605493260.58076787@optimcloud.com> <1632975869705.1585507874.3975460403@optimcloud.com> <1658752499190.46719352.2357280429@optimcloud.com> Message-ID: <517cba1d-9e75-6f60-e99a-a2248f9d5a47@windriver.com> Hi, Sorry for the late response. I understand that you are upset because Wireguard was enabled and then disabled during the development of StarlingX 6.0. I am a part of the team working on the kernel for StarlingX, and I can tell you that actually Wireguard was enabled accidentally during the switch to the v5.10 kernel, and then a clean-up commit disabled it again before the StarlingX 6.0 release. If you would like, I can file a bug report and/or feature request on your behalf, to enable Wireguard, for consideration in the StarlingX 8.0 release cycle. Regarding the deprecation of the mlx4 module and therefore Mellanox ConnectX-3 cards, I can only point you to our previous e-mail exchange at this link: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-April/012906.html Thank you, Vefa On 2022-07-25 08:40, Embedded Devel wrote: > So literally after all the research I did on wireguard and a working model, in the dev lab, now i go to put it in production > only to discover stx 6.0 has now literally disabled wireguard in the kernel, months of time and research is now wasted. > > I even mentioned it back in september and was told to file a bug report on previous errors with wireguard loading, then a later pre 6.0 appeared to have it fixed, and now i find in 6.0 ... > > # CONFIG_WIREGUARD is not set > > completely useless waste of time as well as when you upgraded mellanox drivers to the latest version rendering thousands of $s in > hardware useless to us for future revisions of starlingX, im sorry but i really have to say Ive gotten to the point where i ask why i bother > supporting stx, championing stx, and deploying it for clients, Im sorry but i am beyond fscking pissed off right now! > > > On Thursday 30 September 2021 11:41:20 AM (+07:00), Embedded Devel wrote: > >> LOL Achievement unlocked ... it works now >> steps to reproduce: >> controller-0:~$ wget https://centos.pkgs.org/7/epel-testing-x86_64/wireguard-tools-1.0.20210914-1.el7.x86_64.rpm.html > >> >> controller-0:~$ sudo yum install -y wireguard-tools-1.0.20210914-1.el7.x86_64.rpm Loaded plugins: fastestmirror >> Examining wireguard-tools-1.0.20210914-1.el7.x86_64.rpm: wireguard-tools-1.0.20210914-1.el7.x86_64 >> Marking wireguard-tools-1.0.20210914-1.el7.x86_64.rpm to be installed >> Resolving Dependencies >> --> Running transaction check >> ---> Package wireguard-tools.x86_64 0:1.0.20210914-1.el7 will be installed >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> =============================================================================================================================================================== > >> Package Arch Version Repository Size >> =============================================================================================================================================================== > >> >> Installing: >> wireguard-tools x86_64 1.0.20210914-1.el7 /wireguard-tools-1.0.20210914-1.el7.x86_64 291 k >> >> Transaction Summary >> =============================================================================================================================================================== > >> >> Install 1 Package >> >> Total size: 291 k >> Installed size: 291 k >> Downloading packages: >> Running transaction check >> Running transaction test >> Transaction test succeeded >> Running transaction >> Installing : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 Verifying : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 >> Installed: >> wireguard-tools.x86_64 0:1.0.20210914-1.el7 >> controller-0:~$ curl -o kubectl-calico -O -L "https://github.com/projectcalico/calicoctl/releases/download/v3.19.1/calicoctl" > >> % Total % Received % Xferd Average Speed Time Time Time Current >> Dload Upload Total Spent Left Speed >> 100 615 100 615 0 0 1930 0 --:--:-- --:--:-- --:--:-- 1933 >> 100 42.8M 100 42.8M 0 0 28.1M 0 0:00:01 0:00:01 --:--:-- 46.2M >> controller-0:~$ chmod +x kubectl-calico >> controller-0:~$ sudo mv kubectl-calico /bin/ >> controller-0:~$ kubectl calico patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' >> Successfully patched 1 'FelixConfiguration' resource >> >> controller-0:~$ sudo wg >> interface: wireguard.cali >> public key: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= >> private key: (hidden) >> listening port: 51820 >> fwmark: 0x100000 >> >> peer: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= >> endpoint: 192.168.206.3:51820 >> allowed ips: 172.16.166.128/26, 172.16.166.128/32, 172.16.166.163/32 >> controller-0:~$ >> controller-1:~$ sudo wg >> interface: wireguard.cali >> public key: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= >> private key: (hidden) >> listening port: 51820 >> fwmark: 0x100000 >> >> peer: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= >> endpoint: 192.168.206.2:51820 >> allowed ips: 172.16.192.64/32, 172.16.192.64/26, 172.16.192.87/32 >> controller-1:~$ >> >> >> >> On Thursday 30 September 2021 11:11:01 AM (+07:00), Embedded Devel wrote: >> >> > based on the calico documentation, https://docs.projectcalico.org/security/encrypt-cluster-pod-traffic we should be able to patch felix calicoctl patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' >> > >> > I have a pre-6 stx aio duplex deployed, wireguard does work, i yum installed wireguard-tools, i can bring up the wg interface >> > >> > so two things, how can we execute calico commands ? i see 0 documentation on it >> > >> > and two im curious what wireguard firewall rules for calico would look like. >> > >> > id imagine based on the docs >> > >> > cat < gnp-oam-overrides.yaml >> > apiVersion: crd.projectcalico.org/v1 >> > kind: GlobalNetworkPolicy >> > metadata: >> > name: wg-oam-overrides >> > spec: >> > ingress: >> > - action: Allow >> > destination: >> > ports: >> > - 51820 >> > protocol: UDP >> > order: 500 >> > selector: has(iftype) && iftype == 'oam' >> > types: >> > - Ingress >> > EOF >> > >> > >> > when applied, i cannot connect a remote client to the OAM address, or the floating address >> > > From lists at optimcloud.com Tue Aug 9 00:59:42 2022 From: lists at optimcloud.com (Embedded Devel) Date: Tue, 09 Aug 2022 00:59:42 +0000 Subject: [Starlingx-discuss] calicoctl / calico containers stx 6.0 aio duplex and wireguard - DONE! In-Reply-To: <517cba1d-9e75-6f60-e99a-a2248f9d5a47@windriver.com> References: <517cba1d-9e75-6f60-e99a-a2248f9d5a47@windriver.com> Message-ID: <1660006104699.3433404008.721962345@optimcloud.com> On Tuesday 09 August 2022 06:32:16 AM (+07:00), M. Vefa Bicakci wrote: > Hi, > > Sorry for the late response. > > I understand that you are upset because Wireguard was enabled and then disabled during the development of StarlingX 6.0. I am a part of the team working on the kernel for StarlingX, and I can tell you that actually Wireguard was enabled accidentally during the switch to the v5.10 kernel, and then a clean-up commit disabled it again before the StarlingX 6.0 release. > > If you would like, I can file a bug report and/or feature request on your behalf, to enable Wireguard, for consideration in the StarlingX 8.0 release cycle. Please file a bug report on this so it makes it into the build, I have no idea why you would even consider not having wireguard as part of the base, There are numerous reasons why its a good fit for overlay and encryption, it also is a very good fit for Calico and Althea, Are among the list of reasons where and why wireguard is just a good fit. If I can be assured it will make it maybe I can salvage this work and save this contract. Right now we put pre-6 with wireguard into prod, yet i have no upgrade path. Very risky move, but i wasnt going to leave that much money lost on the table. I hope you all realize even us barely recognized consultants deploy startlingx and we make a living of it, and your decisions directly impact out business. Do you even realize I alone have lost over $50K in revenues due to starlingx and bad decisions on the teams part. I wount even get into starlingx loosing out to kubernetes/openstack-helm for the likes of AT&T. Some of your feature sets and controlled deployment points dont even fit with the largest US Telecomm giant, Its really quite sad honestly to see such a nice product fail due to certain limitations imposed and bad design decisions. I would seriously think manager at wind river itself would be kicking themselves know you only fit 40% of the market, and failed at AT&T. > > Regarding the deprecation of the mlx4 module and therefore Mellanox ConnectX-3 cards, I can only point you to our previous e-mail exchange at this link: > > https://lists.starlingx.io/pipermail/starlingx-discuss/2022-April/012906.html > > Thank you, > > Vefa > > On 2022-07-25 08:40, Embedded Devel wrote: > > So literally after all the research I did on wireguard and a working model, in the dev lab, now i go to put it in production > > only to discover stx 6.0 has now literally disabled wireguard in the kernel, months of time and research is now wasted. > > > > I even mentioned it back in september and was told to file a bug report on previous errors with wireguard loading, then a later pre 6.0 appeared to have it fixed, and now i find in 6.0 ... > > > > # CONFIG_WIREGUARD is not set > > > > completely useless waste of time as well as when you upgraded mellanox drivers to the latest version rendering thousands of $s in > > hardware useless to us for future revisions of starlingX, im sorry but i really have to say Ive gotten to the point where i ask why i bother > > supporting stx, championing stx, and deploying it for clients, Im sorry but i am beyond fscking pissed off right now! > > > > > > On Thursday 30 September 2021 11:41:20 AM (+07:00), Embedded Devel wrote: > > > >> LOL Achievement unlocked ... it works now > >> steps to reproduce: > >> controller-0:~$ wget https://centos.pkgs.org/7/epel-testing-x86_64/wireguard-tools-1.0.20210914-1.el7.x86_64.rpm.html > > > >> > >> controller-0:~$ sudo yum install -y wireguard-tools-1.0.20210914-1.el7.x86_64.rpm Loaded plugins: fastestmirror > >> Examining wireguard-tools-1.0.20210914-1.el7.x86_64.rpm: wireguard-tools-1.0.20210914-1.el7.x86_64 > >> Marking wireguard-tools-1.0.20210914-1.el7.x86_64.rpm to be installed > >> Resolving Dependencies > >> --> Running transaction check > >> ---> Package wireguard-tools.x86_64 0:1.0.20210914-1.el7 will be installed > >> --> Finished Dependency Resolution > >> > >> Dependencies Resolved > >> > >> =============================================================================================================================================================== > > > >> Package Arch Version Repository Size > >> =============================================================================================================================================================== > > > >> > >> Installing: > >> wireguard-tools x86_64 1.0.20210914-1.el7 /wireguard-tools-1.0.20210914-1.el7.x86_64 291 k > >> > >> Transaction Summary > >> =============================================================================================================================================================== > > > >> > >> Install 1 Package > >> > >> Total size: 291 k > >> Installed size: 291 k > >> Downloading packages: > >> Running transaction check > >> Running transaction test > >> Transaction test succeeded > >> Running transaction > >> Installing : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 Verifying : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 > >> Installed: > >> wireguard-tools.x86_64 0:1.0.20210914-1.el7 > >> controller-0:~$ curl -o kubectl-calico -O -L "https://github.com/projectcalico/calicoctl/releases/download/v3.19.1/calicoctl" > > > >> % Total % Received % Xferd Average Speed Time Time Time Current > >> Dload Upload Total Spent Left Speed > >> 100 615 100 615 0 0 1930 0 --:--:-- --:--:-- --:--:-- 1933 > >> 100 42.8M 100 42.8M 0 0 28.1M 0 0:00:01 0:00:01 --:--:-- 46.2M > >> controller-0:~$ chmod +x kubectl-calico > >> controller-0:~$ sudo mv kubectl-calico /bin/ > >> controller-0:~$ kubectl calico patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' > >> Successfully patched 1 'FelixConfiguration' resource > >> > >> controller-0:~$ sudo wg > >> interface: wireguard.cali > >> public key: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= > >> private key: (hidden) > >> listening port: 51820 > >> fwmark: 0x100000 > >> > >> peer: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= > >> endpoint: 192.168.206.3:51820 > >> allowed ips: 172.16.166.128/26, 172.16.166.128/32, 172.16.166.163/32 > >> controller-0:~$ > >> controller-1:~$ sudo wg > >> interface: wireguard.cali > >> public key: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= > >> private key: (hidden) > >> listening port: 51820 > >> fwmark: 0x100000 > >> > >> peer: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= > >> endpoint: 192.168.206.2:51820 > >> allowed ips: 172.16.192.64/32, 172.16.192.64/26, 172.16.192.87/32 > >> controller-1:~$ > >> > >> > >> > >> On Thursday 30 September 2021 11:11:01 AM (+07:00), Embedded Devel wrote: > >> > >> > based on the calico documentation, https://docs.projectcalico.org/security/encrypt-cluster-pod-traffic we should be able to patch felix calicoctl patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' > >> > > >> > I have a pre-6 stx aio duplex deployed, wireguard does work, i yum installed wireguard-tools, i can bring up the wg interface > >> > > >> > so two things, how can we execute calico commands ? i see 0 documentation on it > >> > > >> > and two im curious what wireguard firewall rules for calico would look like. > >> > > >> > id imagine based on the docs > >> > > >> > cat < gnp-oam-overrides.yaml > >> > apiVersion: crd.projectcalico.org/v1 > >> > kind: GlobalNetworkPolicy > >> > metadata: > >> > name: wg-oam-overrides > >> > spec: > >> > ingress: > >> > - action: Allow > >> > destination: > >> > ports: > >> > - 51820 > >> > protocol: UDP > >> > order: 500 > >> > selector: has(iftype) && iftype == 'oam' > >> > types: > >> > - Ingress > >> > EOF > >> > > >> > > >> > when applied, i cannot connect a remote client to the OAM address, or the floating address > >> > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From Peng.Peng at windriver.com Tue Aug 9 15:37:21 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 9 Aug 2022 15:37:21 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220806T013941Z Message-ID: Sanity Test from 2022-August-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220806T013941Z/outputs/iso/) Status: GREEN Sanity Test executed on Bare Metal Environment AIO - Simplex Setup 1 TCs [PASS] Sanity Platform 08 TCs [PASS] Daily Regression Platform 09 TCs [PASS] TOTAL: [ 18 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity[1-1-calico-ipam-4] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_push_docker_image_to_local_registry[active] PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod[2_0-fill_fill-static-best-effort-HT-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] 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_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] 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_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Wed Aug 10 00:25:09 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 9 Aug 2022 20:25:09 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 343 - Failure! Message-ID: <2097641220.2.1660091112334.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 343 Status: Failure Timestamp: 20220810T000500Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220810T000422Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220810T000422Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220810T000422Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220810T000422Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: true REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220810T000422Z LAYER: build-containers REGISTRY: docker.io From scott.little at windriver.com Wed Aug 10 14:57:26 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 10 Aug 2022 10:57:26 -0400 Subject: [Starlingx-discuss] [Build] Changes to CENGN build schedule Message-ID: <755ba1c0-bae1-d58c-97ae-e6eeb6e2d35e@windriver.com> I'm making the following changes to the CENGN build schedule. CentOS 7.0 - Surrenders it's daily midnight UTC slot, and moves to on-demand. CentOS master - Moves from 5 am UTC to midnight. Debian master - Moves from 10 am UTC to 6 am UTC.? However we may be forced to suspend builds for a few days while we sort out some resourcing issues blocking Debian 7.0 build Debian 7.0 - Will be on demand.? Getting this build working is a work in progress.? We are still sorting out some resource issues. From starlingx.build at gmail.com Wed Aug 10 16:19:19 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 10 Aug 2022 12:19:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 349 - Failure! Message-ID: <550365597.6.1660148361211.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 349 Status: Failure Timestamp: 20220810T160431Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/debian/build-containers/20220810T160413Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-rc-7.0-build-containers/20220810T160413Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-rc-7.0-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/debian/build-containers/20220810T160413Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/debian/build-containers/20220810T160413Z/logs MASTER_JOB_NAME: STX_7.0_build_debian_build_containers MY_REPO_ROOT: /localdisk/designer/jenkins/debian-rc-7.0-build-containers FULL_BUILD: true REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: rc-7.0-debian-20220810T160413Z LAYER: build-containers REGISTRY: docker.io From starlingx.build at gmail.com Wed Aug 10 17:58:11 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 10 Aug 2022 13:58:11 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 350 - Still Failing! In-Reply-To: <230961702.4.1660148353929.JavaMail.javamailuser@localhost> References: <230961702.4.1660148353929.JavaMail.javamailuser@localhost> Message-ID: <304729405.9.1660154293436.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 350 Status: Still Failing Timestamp: 20220810T174359Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/debian/build-containers/20220810T174353Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-rc-7.0-build-containers/20220810T174353Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-rc-7.0-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/debian/build-containers/20220810T174353Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/debian/build-containers/20220810T174353Z/logs MASTER_JOB_NAME: STX_7.0_build_debian_build_containers MY_REPO_ROOT: /localdisk/designer/jenkins/debian-rc-7.0-build-containers FULL_BUILD: true REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: rc-7.0-debian-20220810T174353Z LAYER: build-containers REGISTRY: docker.io From ildiko.vancsa at gmail.com Thu Aug 11 01:57:09 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 10 Aug 2022 18:57:09 -0700 Subject: [Starlingx-discuss] Minutes: Release Team Call (Aug 10 2022) Message-ID: <845C502A-3776-4C27-9347-6931506458FA@gmail.com> Hi, Below please find the highlights from today?s Release team call. * The main focus of the call was the 7.0 release - Build: + There was an issue with the build, that reported green without producing an ISO. The issue is now fixed. + Only CentOS-based builds are running, the team is currently working on setting up the system to build the Debian-based version of the platform. - Sanity + Green test results on the platform without OpenStack + There?s an issue with the environment to test STX with OpenStack, the team is currently working on resolving that * 8.0 release cycle - The list of features to be included in 8.0 is currently being built For the detailed minutes, please check the meeting etherpad: https://etherpad.opendev.org/p/stx-releases The next Release team call is scheduled for August 24. For more information about the call please check the meeting wiki: https://wiki.openstack.org/wiki/Starlingx/Meetings#6:30am_Pacific_-_Release_Team_Call_.28Bi-weekly.29 Thanks and Best Regards, Ildik? From ildiko.vancsa at gmail.com Thu Aug 11 02:27:57 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 10 Aug 2022 19:27:57 -0700 Subject: [Starlingx-discuss] Minutes: Community Call (Aug 10 2022) Message-ID: <8D98DC35-9250-437D-8228-6291F1C20988@gmail.com> Hi, Below please find the highlights of today?s Community call. * We spent some time on discussing ways and methods to get users and newcomers more involved in the community - The conversation was triggered by the Calico/Wireguard email thread - We touched on ways to encourage people to file bugs and participate in other activities - People on the call also explored ways to improve communication within the community and with that making it more accessible - We agreed to continue the conversation at the upcoming PTG * We discussed the 7.0 release in details - Build: + There was an issue with the build, that reported green without producing an ISO. The issue is now fixed. + Only CentOS-based builds are running, the team is currently working on setting up the system to build the Debian-based version of the platform. * Removing the 4.0 resources and keep 5.x until 7.0 is released + The team decided to move over to on-demand build for CentOS and release the 7pm Eastern build slot - Sanity + Green test results on the platform without OpenStack + There?s an issue with the environment to test STX with OpenStack, the team is currently working on resolving that + The subject line of the summary email needs to be changed from saying ?master? to ?7.0? - Bugs + The 'registry-token-server build failure? bug (https://bugs.launchpad.net/starlingx/+bug/1983114) got reported twice and will be closed + No open bugs for 7.0 For the detailed minutes, please check the meeting etherpad: https://etherpad.opendev.org/p/stx-status The next Community call is scheduled for August 17. For more information about the call please check the meeting wiki: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call Thanks and Best Regards, Ildik? From vefa.bicakci at windriver.com Thu Aug 11 14:02:31 2022 From: vefa.bicakci at windriver.com (M. Vefa Bicakci) Date: Thu, 11 Aug 2022 10:02:31 -0400 Subject: [Starlingx-discuss] calicoctl / calico containers stx 6.0 aio duplex and wireguard - DONE! In-Reply-To: <1660006104699.3433404008.721962345@optimcloud.com> References: <517cba1d-9e75-6f60-e99a-a2248f9d5a47@windriver.com> <1660006104699.3433404008.721962345@optimcloud.com> Message-ID: <4a6a8acb-d48c-5e35-3e27-a372b0bf4eec@windriver.com> Hi all, I had opened the following feature request/bug on Launchpad about two days ago. Sorry for the delay in my notification. The bug report requesting that the CONFIG_WIREGUARD kernel configuration option be enabled is here: https://bugs.launchpad.net/starlingx/+bug/1984125 Thank you, Vefa On 2022-08-08 20:59, Embedded Devel wrote: > > > On Tuesday 09 August 2022 06:32:16 AM (+07:00), M. Vefa Bicakci wrote: > >> Hi, >> >> Sorry for the late response. >> >> I understand that you are upset because Wireguard was enabled and then disabled during the development of StarlingX 6.0. I am a part of the team working on the kernel for StarlingX, and I can tell you that actually Wireguard was enabled accidentally during the switch to the v5.10 kernel, and then a clean-up commit disabled it again before the StarlingX 6.0 release. >> >> If you would like, I can file a bug report and/or feature request on your behalf, to enable Wireguard, for consideration in the StarlingX 8.0 release cycle. > Please file a bug report on this so it makes it into the build, I have no idea why you would even consider not having wireguard as part of the base, There are numerous reasons why its a good fit for overlay and encryption, it also is a very good fit for Calico and Althea, Are among the list of reasons > where and why wireguard is just a good fit. If I can be assured it will make it maybe I can salvage this? work and save this contract. Right now we put > pre-6 with wireguard into prod, yet i have no upgrade path. Very risky move, but i wasnt going to leave that much money lost on the table. I hope > you all realize even us barely recognized consultants deploy startlingx and we make a living of it, and your decisions directly impact out business. > > Do you even realize I alone have lost over $50K in revenues due to starlingx and bad decisions on the teams part. I wount even get into starlingx > loosing out to kubernetes/openstack-helm for the likes of AT&T. Some of your feature sets and controlled deployment points dont even fit with the largest > US Telecomm giant, Its really quite sad honestly to see such a nice product fail due to certain limitations imposed and bad design decisions. I would > seriously think manager at wind river itself would be kicking themselves know you only fit 40% of the market, and failed at AT&T. > >> >> Regarding the deprecation of the mlx4 module and therefore Mellanox ConnectX-3 cards, I can only point you to our previous e-mail exchange at this link: >> >> https://lists.starlingx.io/pipermail/starlingx-discuss/2022-April/012906.html > >> >> Thank you, >> >> Vefa >> >> On 2022-07-25 08:40, Embedded Devel wrote: >> > So literally after all the research I did on wireguard and a working model, in the dev lab, now i go to put it in production >> > only to discover stx 6.0 has now literally disabled wireguard in the kernel, months of time and research is now wasted. >> > >> > I even mentioned it back in september and was told to file a bug report on previous errors with wireguard loading, then a later pre 6.0 appeared to have it fixed, and now i find in 6.0 ... >> > >> > # CONFIG_WIREGUARD is not set >> > >> > completely useless waste of time as well as when you upgraded mellanox drivers to the latest version rendering thousands of $s in >> > hardware useless to us for future revisions of starlingX, im sorry but i really have to say Ive gotten to the point where i ask why i bother >> > supporting stx, championing stx, and deploying it for clients, Im sorry but i am beyond fscking pissed off right now! >> > >> > >> > On Thursday 30 September 2021 11:41:20 AM (+07:00), Embedded Devel wrote: >> > >> >> LOL Achievement unlocked ... it works now >> >> steps to reproduce: >> >> controller-0:~$ wget https://centos.pkgs.org/7/epel-testing-x86_64/wireguard-tools-1.0.20210914-1.el7.x86_64.rpm.html > >> > >> >> >> >> controller-0:~$ sudo yum install -y wireguard-tools-1.0.20210914-1.el7.x86_64.rpm Loaded plugins: fastestmirror >> >> Examining wireguard-tools-1.0.20210914-1.el7.x86_64.rpm: wireguard-tools-1.0.20210914-1.el7.x86_64 >> >> Marking wireguard-tools-1.0.20210914-1.el7.x86_64.rpm to be installed >> >> Resolving Dependencies >> >> --> Running transaction check >> >> ---> Package wireguard-tools.x86_64 0:1.0.20210914-1.el7 will be installed >> >> --> Finished Dependency Resolution >> >> >> >> Dependencies Resolved >> >> >> >> =============================================================================================================================================================== > >> > >> >> Package Arch Version Repository Size >> >> =============================================================================================================================================================== > >> > >> >> >> >> Installing: >> >> wireguard-tools x86_64 1.0.20210914-1.el7 /wireguard-tools-1.0.20210914-1.el7.x86_64 291 k >> >> >> >> Transaction Summary >> >> =============================================================================================================================================================== > >> > >> >> >> >> Install 1 Package >> >> >> >> Total size: 291 k >> >> Installed size: 291 k >> >> Downloading packages: >> >> Running transaction check >> >> Running transaction test >> >> Transaction test succeeded >> >> Running transaction >> >> Installing : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 Verifying : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 >> >> Installed: >> >> wireguard-tools.x86_64 0:1.0.20210914-1.el7 >> >> controller-0:~$ curl -o kubectl-calico -O -L "https://github.com/projectcalico/calicoctl/releases/download/v3.19.1/calicoctl" > >> > >> >> % Total % Received % Xferd Average Speed Time Time Time Current >> >> Dload Upload Total Spent Left Speed >> >> 100 615 100 615 0 0 1930 0 --:--:-- --:--:-- --:--:-- 1933 >> >> 100 42.8M 100 42.8M 0 0 28.1M 0 0:00:01 0:00:01 --:--:-- 46.2M >> >> controller-0:~$ chmod +x kubectl-calico >> >> controller-0:~$ sudo mv kubectl-calico /bin/ >> >> controller-0:~$ kubectl calico patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' >> >> Successfully patched 1 'FelixConfiguration' resource >> >> >> >> controller-0:~$ sudo wg >> >> interface: wireguard.cali >> >> public key: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= >> >> private key: (hidden) >> >> listening port: 51820 >> >> fwmark: 0x100000 >> >> >> >> peer: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= >> >> endpoint: 192.168.206.3:51820 >> >> allowed ips: 172.16.166.128/26, 172.16.166.128/32, 172.16.166.163/32 >> >> controller-0:~$ >> >> controller-1:~$ sudo wg >> >> interface: wireguard.cali >> >> public key: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= >> >> private key: (hidden) >> >> listening port: 51820 >> >> fwmark: 0x100000 >> >> >> >> peer: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= >> >> endpoint: 192.168.206.2:51820 >> >> allowed ips: 172.16.192.64/32, 172.16.192.64/26, 172.16.192.87/32 >> >> controller-1:~$ >> >> >> >> >> >> >> >> On Thursday 30 September 2021 11:11:01 AM (+07:00), Embedded Devel wrote: >> >> >> >> > based on the calico documentation, https://docs.projectcalico.org/security/encrypt-cluster-pod-traffic we should be able to patch felix calicoctl patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' >> >> > >> >> > I have a pre-6 stx aio duplex deployed, wireguard does work, i yum installed wireguard-tools, i can bring up the wg interface >> >> > >> >> > so two things, how can we execute calico commands ? i see 0 documentation on it >> >> > >> >> > and two im curious what wireguard firewall rules for calico would look like. >> >> > >> >> > id imagine based on the docs >> >> > >> >> > cat < gnp-oam-overrides.yaml >> >> > apiVersion: crd.projectcalico.org/v1 >> >> > kind: GlobalNetworkPolicy >> >> > metadata: >> >> > name: wg-oam-overrides >> >> > spec: >> >> > ingress: >> >> > - action: Allow >> >> > destination: >> >> > ports: >> >> > - 51820 >> >> > protocol: UDP >> >> > order: 500 >> >> > selector: has(iftype) && iftype == 'oam' >> >> > types: >> >> > - Ingress >> >> > EOF >> >> > >> >> > >> >> > when applied, i cannot connect a remote client to the OAM address, or the floating address >> >> > >> > >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > From ildiko.vancsa at gmail.com Thu Aug 11 19:17:31 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 11 Aug 2022 12:17:31 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - NEW POLL In-Reply-To: References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> Message-ID: <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> Hi StarlingX Community, It is a friendly reminder that we have two polls open in an attempt to find a few options to set up a call with the OpenInfra Foundation Board of Directors: * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe __Please submit your preferences by August 14, 2022.__ As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra BoD group! If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 3, 2022, at 00:06, Ildiko Vancsa wrote: > > Hi, > > I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html > > Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: > > * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe > * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe > > __Please submit your preferences by August 14, 2022.__ > > As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! > > If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: >> >> Hi Greg, >> >> I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. >> >> Best Regards, >> Ildik? >> >> >>> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >>> >>> I can't find the zoom link for the meeting ... do you have it ? >>> Greg. >>> >>> -----Original Message----- >>> From: Ildiko Vancsa >>> Sent: Wednesday, July 27, 2022 2:16 AM >>> To: Waines, Greg >>> Cc: StarlingX ML >>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >>> >>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>> >>> Hi Greg, >>> >>> Great, thank you for being available! >>> >>> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >>> >>> I think diversity is a great topic for the call and should be a basis for a good discussion. >>> >>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>> >>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>>> >>>> hey Ildiko, >>>> I am available on the Aug 4 1300 UTC timeslot. >>>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>>> >>>> I added our favourite discussion topic to the etherpad: >>>> * Looking for guidance on diversifying the Users and >>>> Contributors in the community >>>> >>>> Greg. >>>> >>>> -----Original Message----- >>>> From: Ildiko Vancsa >>>> Sent: Tuesday, July 26, 2022 5:47 AM >>>> To: StarlingX ML >>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>>> StarlingX Sync - UPDATE >>>> >>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>> >>>> Hi StarlingX Community, >>>> >>>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>>> >>>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>>> >>>> You can see the original email and follow the thread here: >>>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>>> 6.html >>>> >>>> As a reminder, we have an etherpad to propose topics for the call and >>>> take notes during the meeting: >>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>> >>>> Please let me know if you have any questions. >>>> >>>> Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>>> >>>>> Hi StarlingX Community, >>>>> >>>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>>> >>>>> You can find the poll here: >>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>> >>>>> __Please submit your preferences on the poll by the end of day on >>>>> July 20, 2022.__ >>>>> >>>>> >>>>> I created an etherpad to collect potential topics for the >>>>> conversation and build an agenda for the call. Please add discussion >>>>> points that you think would be important to bring up during the call: >>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>> >>>>> Please let me know if you have any questions. >>>>> >>>>> Best Regards, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>>> >>>>>> Hi StarlingX Community, >>>>>> >>>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>>> >>>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>>> >>>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>>> >>>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>>> >>>>>> I created an etherpad to collect potential topics for the >>>>>> conversation and build an agenda for the call: >>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>> >>>>>> I also created a poll to try to find time slot options that we can >>>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>>> options for August, if we fail to find good options for that month, I >>>>>> will extend it to September. Please find the poll here: >>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>> >>>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>>> >>>>>> __Please submit your preferences by the end of day on July 20, >>>>>> 2022.__ >>>>>> >>>>>> Please let me know if you have any questions. >>>>>> >>>>>> Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> > From ildiko.vancsa at gmail.com Thu Aug 11 21:39:07 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 11 Aug 2022 14:39:07 -0700 Subject: [Starlingx-discuss] What is the base OS for Starlingx Release 6 In-Reply-To: References: Message-ID: <90148E8E-ED79-4D6A-8491-C14C14D18BE7@gmail.com> Hi Danishka, Thank you for reaching out with the issues you?re experiencing. Can you share a bit more information about the failures that you?re seeing? Best Regards, Ildik? > On Aug 1, 2022, at 06:17, open infra wrote: > > I am suppose to install nvidia driver on a worker (stx 6) which require few dependencies including gcc and make. > When I use CentOS 7 nvidia driver compilation/installation fails and with Rocky linux 9 gcc installation fails. > > > On Thu, Jul 28, 2022 at 4:01 PM open infra wrote: > Hi, > > Which CentOS release is the compatible with STX release boot image? > > Regards, > Danishka > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Juanita.Balaraj at windriver.com Fri Aug 12 01:16:32 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 12 Aug 2022 01:16:32 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 10-August-22 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 10-August-22 StarlingX 7.0 Release: - Stx 7.0 GA date is August 24th - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date. Gerrit Reviews: - 3 Cherry picks completed this week. Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - https://review.opendev.org/c/starlingx/docs/+/851209 - Synched with Litao Gao. This update is STARLINGX Only. Needs to be reviewed and approved by the Docs team - https://bugs.launchpad.net/starlingx/+bug/1982058 - Total 8 bugs - Fixed 4 Launchpad Doc Bugs: - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold - https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa General: - Operations Guide Archive - On Hold until further clarifications are discussed (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 starlingx.build at gmail.com Sun Aug 14 00:56:39 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 13 Aug 2022 20:56:39 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 360 - Failure! Message-ID: <1444573269.40.1660438601752.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 360 Status: Failure Timestamp: 20220814T005622Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220814T005600Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220814T005600Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220814T005600Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220814T005600Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220814T005600Z LAYER: build-containers REGISTRY: docker.io From huang.shuquan at 99cloud.net Sun Aug 14 13:50:44 2022 From: huang.shuquan at 99cloud.net (Shuquan Huang) Date: Sun, 14 Aug 2022 21:50:44 +0800 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED In-Reply-To: References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Message-ID: <967ECD42-3FF6-4E2D-9BBC-7FA60AC6D8B8@99cloud.net> I vote for option 2. :) > On Aug 5, 2022, at 21:14, Cooke, Rob wrote: > > Another vote here as well for option 2. > > From: Waines, Greg > Sent: Friday, August 5, 2022 8:49 AM > To: Pereira, Douglas ; StarlingX ML > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED > > Another vote for option 2: Have the APAC friendly call every first Wednesday of the month > > > From: Pereira, Douglas > > Sent: Thursday, August 4, 2022 9:28 AM > To: StarlingX ML > > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED > > Another vote for option 2: Have the APAC friendly call every first Wednesday of the month > > Regards, > Doug > > From: Cervi, Thales Elero > > Sent: Thursday, August 4, 2022 10:14 AM > To: Ildiko Vancsa >; StarlingX ML > > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED > > I also vote for option 2: Have the APAC friendly call every first Wednesday of the month > From: Ildiko Vancsa > > Sent: Wednesday, August 3, 2022 11:18 AM > To: StarlingX ML > > Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX Community, > > I?m reaching out to you with an update regarding alternating the TSC & Community call times. > > The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. > > We still need to decide on cadence to alternate the time slots. Options include: > > * Alternate the time slots bi-weekly > * Have the APAC friendly call every first Wednesday of the month > > In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! > > __Please share your preference on cadence by the end of day next Tuesday (August 08).__ > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > On Jul 14, 2022, at 22:02, Ildiko Vancsa > wrote: > > > > Hi StarlingX Community, > > > > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. > > > > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. > > > > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b > > > > __Please fill it out for by the end of next week (July 24).__ > > > > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! > > > > Please let me know if you have any questions. > > > > Best Regards, > > Ildik? > > > > ??? > > > > Ildik? V?ncsa > > Senior Manager, Community & Ecosystem > > Open Infrastructure Foundation > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Sun Aug 14 18:24:56 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 14 Aug 2022 11:24:56 -0700 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - UPDATE In-Reply-To: <967ECD42-3FF6-4E2D-9BBC-7FA60AC6D8B8@99cloud.net> References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> <967ECD42-3FF6-4E2D-9BBC-7FA60AC6D8B8@99cloud.net> Message-ID: <0B6F9FE5-4C2D-4754-AE77-1F42575391B5@gmail.com> Hi StarlingX Community, Thank you to all of you who voiced your opinions already. So far the favored option is #2, which would be having the APAC friendly call every first Wednesday (US Time) of the month. If the community settles on this option, the first meeting in the APAC-friendly time slot would be on the 7th of September at at 7pm PDT/ 10pm EDT / 8th of September at 10am CST. If you have a different preference or have any questions, please reply to this thread or reach out to me directly. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 14, 2022, at 06:50, Shuquan Huang wrote: > > I vote for option 2. :) > >> On Aug 5, 2022, at 21:14, Cooke, Rob wrote: >> >> Another vote here as well for option 2. >> >> From: Waines, Greg >> Sent: Friday, August 5, 2022 8:49 AM >> To: Pereira, Douglas ; StarlingX ML >> Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED >> >> Another vote for option 2: Have the APAC friendly call every first Wednesday of the month >> >> >> From: Pereira, Douglas >> Sent: Thursday, August 4, 2022 9:28 AM >> To: StarlingX ML >> Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED >> >> Another vote for option 2: Have the APAC friendly call every first Wednesday of the month >> >> Regards, >> Doug >> >> From: Cervi, Thales Elero >> Sent: Thursday, August 4, 2022 10:14 AM >> To: Ildiko Vancsa ; StarlingX ML >> Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED >> >> I also vote for option 2: Have the APAC friendly call every first Wednesday of the month >> From: Ildiko Vancsa >> Sent: Wednesday, August 3, 2022 11:18 AM >> To: StarlingX ML >> Subject: Re: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - RESPONSE NEEDED >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Hi StarlingX Community, >> >> I?m reaching out to you with an update regarding alternating the TSC & Community call times. >> >> The favored alternate time slot, based on the poll below, is: Wednesdays at 7pm PDT/ 10pm EDT / Thursdays at 10am CST. >> >> We still need to decide on cadence to alternate the time slots. Options include: >> >> * Alternate the time slots bi-weekly >> * Have the APAC friendly call every first Wednesday of the month >> >> In order to find the choice that is preferred by the majority of contributors, please send a reply with your preference (either one from the above list or any other option that would work for you)! >> >> __Please share your preference on cadence by the end of day next Tuesday (August 08).__ >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >> > On Jul 14, 2022, at 22:02, Ildiko Vancsa wrote: >> > >> > Hi StarlingX Community, >> > >> > I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. >> > >> > It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. >> > >> > I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b >> > >> > __Please fill it out for by the end of next week (July 24).__ >> > >> > Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! >> > >> > Please let me know if you have any questions. >> > >> > Best Regards, >> > Ildik? >> > >> > ??? >> > >> > Ildik? V?ncsa >> > Senior Manager, Community & Ecosystem >> > Open Infrastructure Foundation >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Mon Aug 15 13:07:39 2022 From: scott.little at windriver.com (Scott Little) Date: Mon, 15 Aug 2022 09:07:39 -0400 Subject: [Starlingx-discuss] First build of STX.7.0 for debian Message-ID: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/debian/monolithic/latest_build/outputs/iso/ From ildiko.vancsa at gmail.com Mon Aug 15 20:44:26 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 15 Aug 2022 13:44:26 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - NEW POLL In-Reply-To: <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> Message-ID: <04B5EB72-75E4-49D2-BCE3-AD2662366162@gmail.com> Hi StarlingX Community, Thank you all who filled out the polls. I?m reaching out to share the results. The preferred option to have the OpenInfra Board of Directors - StarlingX meeting is September 7 (Wednesday) at 6am PDT / 1300 UTC. Further options that could potentially work include the same time slot on September 8 (Thursday) and September 14 (Wednesday). I will share the preferred time slot with the Board with the hope that it will work, and will opt to fallback options in case needed. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 11, 2022, at 12:17, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder that we have two polls open in an attempt to find a few options to set up a call with the OpenInfra Foundation Board of Directors: > > * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe > * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe > > __Please submit your preferences by August 14, 2022.__ > > As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra BoD group! > > If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Aug 3, 2022, at 00:06, Ildiko Vancsa wrote: >> >> Hi, >> >> I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html >> >> Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: >> >> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >> >> __Please submit your preferences by August 14, 2022.__ >> >> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >> >> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: >>> >>> Hi Greg, >>> >>> I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. >>> >>> Best Regards, >>> Ildik? >>> >>> >>>> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >>>> >>>> I can't find the zoom link for the meeting ... do you have it ? >>>> Greg. >>>> >>>> -----Original Message----- >>>> From: Ildiko Vancsa >>>> Sent: Wednesday, July 27, 2022 2:16 AM >>>> To: Waines, Greg >>>> Cc: StarlingX ML >>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >>>> >>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>> >>>> Hi Greg, >>>> >>>> Great, thank you for being available! >>>> >>>> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >>>> >>>> I think diversity is a great topic for the call and should be a basis for a good discussion. >>>> >>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>> >>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>> >>>> Thanks and Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>>>> >>>>> hey Ildiko, >>>>> I am available on the Aug 4 1300 UTC timeslot. >>>>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>>>> >>>>> I added our favourite discussion topic to the etherpad: >>>>> * Looking for guidance on diversifying the Users and >>>>> Contributors in the community >>>>> >>>>> Greg. >>>>> >>>>> -----Original Message----- >>>>> From: Ildiko Vancsa >>>>> Sent: Tuesday, July 26, 2022 5:47 AM >>>>> To: StarlingX ML >>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>>>> StarlingX Sync - UPDATE >>>>> >>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>> >>>>> Hi StarlingX Community, >>>>> >>>>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>>>> >>>>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>>>> >>>>> You can see the original email and follow the thread here: >>>>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>>>> 6.html >>>>> >>>>> As a reminder, we have an etherpad to propose topics for the call and >>>>> take notes during the meeting: >>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>> >>>>> Please let me know if you have any questions. >>>>> >>>>> Best Regards, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem >>>>> Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>>>> >>>>>> Hi StarlingX Community, >>>>>> >>>>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>>>> >>>>>> You can find the poll here: >>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>> >>>>>> __Please submit your preferences on the poll by the end of day on >>>>>> July 20, 2022.__ >>>>>> >>>>>> >>>>>> I created an etherpad to collect potential topics for the >>>>>> conversation and build an agenda for the call. Please add discussion >>>>>> points that you think would be important to bring up during the call: >>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>> >>>>>> Please let me know if you have any questions. >>>>>> >>>>>> Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>>>> >>>>>>> Hi StarlingX Community, >>>>>>> >>>>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>>>> >>>>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>>>> >>>>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>>>> >>>>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>>>> >>>>>>> I created an etherpad to collect potential topics for the >>>>>>> conversation and build an agenda for the call: >>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>> >>>>>>> I also created a poll to try to find time slot options that we can >>>>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>>>> options for August, if we fail to find good options for that month, I >>>>>>> will extend it to September. Please find the poll here: >>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>> >>>>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>>>> >>>>>>> __Please submit your preferences by the end of day on July 20, >>>>>>> 2022.__ >>>>>>> >>>>>>> Please let me know if you have any questions. >>>>>>> >>>>>>> Best Regards, >>>>>>> Ildik? >>>>>>> >>>>>>> ??? >>>>>>> >>>>>>> Ildik? V?ncsa >>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>> >> > From starlingx.build at gmail.com Tue Aug 16 08:50:18 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 16 Aug 2022 04:50:18 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1524 - Failure! Message-ID: <1114259085.2.1660639821816.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1524 Status: Failure Timestamp: 20220816T045011Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220816T043002Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220816T043002Z DOCKER_BUILD_ID: jenkins-master-20220816T043002Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220816T043002Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220816T043002Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Tue Aug 16 08:50:24 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 16 Aug 2022 04:50:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1381 - Failure! Message-ID: <1486117798.5.1660639825586.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1381 Status: Failure Timestamp: 20220816T043002Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220816T043002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Tue Aug 16 09:59:37 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 16 Aug 2022 05:59:37 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 573 - Failure! Message-ID: <1413098091.8.1660643978670.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 573 Status: Failure Timestamp: 20220816T052516Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220816T034428Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220816T034428Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220816T034428Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220816T034428Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220816T034428Z/logs PUBLISH_TIMESTAMP: 20220816T034428Z FLOCK_VERSION: master-centos-stable-20220816T034428Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220816T034428Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220816T034428Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Tue Aug 16 09:59:41 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 16 Aug 2022 05:59:41 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 329 - Failure! Message-ID: <1524371134.11.1660643982163.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 329 Status: Failure Timestamp: 20220816T044810Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220816T034428Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220816T034428Z 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/20220816T034428Z/logs MASTER_BUILD_NUMBER: 330 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220816T034428Z/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: 20220816T034428Z DOCKER_BUILD_ID: jenkins-master-containers-20220816T034428Z-builder TIMESTAMP: 20220816T034428Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220816T034428Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220816T034428Z/outputs From starlingx.build at gmail.com Tue Aug 16 09:59:44 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 16 Aug 2022 05:59:44 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 330 - Failure! Message-ID: <610722332.14.1660643985354.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 330 Status: Failure Timestamp: 20220816T034428Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220816T034428Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Wed Aug 17 13:14:13 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 17 Aug 2022 09:14:13 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 574 - Still Failing! In-Reply-To: <715748117.6.1660643975112.JavaMail.javamailuser@localhost> References: <715748117.6.1660643975112.JavaMail.javamailuser@localhost> Message-ID: <1912633299.21.1660742054473.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 574 Status: Still Failing Timestamp: 20220817T093800Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220817T080941Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220817T080941Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220817T080941Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220817T080941Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220817T080941Z/logs PUBLISH_TIMESTAMP: 20220817T080941Z FLOCK_VERSION: master-centos-stable-20220817T080941Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220817T080941Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220817T080941Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Wed Aug 17 13:14:16 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 17 Aug 2022 09:14:16 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 330 - Still Failing! In-Reply-To: <482308330.9.1660643979801.JavaMail.javamailuser@localhost> References: <482308330.9.1660643979801.JavaMail.javamailuser@localhost> Message-ID: <1762561323.24.1660742057634.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 330 Status: Still Failing Timestamp: 20220817T090640Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220817T080941Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220817T080941Z 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/20220817T080941Z/logs MASTER_BUILD_NUMBER: 331 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220817T080941Z/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: 20220817T080941Z DOCKER_BUILD_ID: jenkins-master-containers-20220817T080941Z-builder TIMESTAMP: 20220817T080941Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220817T080941Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220817T080941Z/outputs From starlingx.build at gmail.com Wed Aug 17 13:14:24 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 17 Aug 2022 09:14:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 331 - Still Failing! In-Reply-To: <461021740.12.1660643983181.JavaMail.javamailuser@localhost> References: <461021740.12.1660643983181.JavaMail.javamailuser@localhost> Message-ID: <1466010686.27.1660742065602.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 331 Status: Still Failing Timestamp: 20220817T080941Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220817T080941Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From scott.little at windriver.com Wed Aug 17 13:58:37 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 17 Aug 2022 09:58:37 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 330 - Failure! In-Reply-To: <610722332.14.1660643985354.JavaMail.javamailuser@localhost> References: <610722332.14.1660643985354.JavaMail.javamailuser@localhost> Message-ID: <6c89ea30-e2cd-d899-8f91-9f9dcf94b147@windriver.com> The stx-mariadb container is failing to build. The upstream URL http://ftp.osuosl.org/pub/mariadb/repo/10.2/ubuntu? is no longer available. It looks like that version 10.2 has fallen out of support and has been taken down.? Available versions range from 10.3 to 10.9. I'll raise a launchpad. Scott On 2022-08-16 05:59, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 330 > Status: Failure > Timestamp: 20220816T034428Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220816T034428Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Wed Aug 17 14:07:00 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 17 Aug 2022 10:07:00 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 330 - Failure! In-Reply-To: <6c89ea30-e2cd-d899-8f91-9f9dcf94b147@windriver.com> References: <610722332.14.1660643985354.JavaMail.javamailuser@localhost> <6c89ea30-e2cd-d899-8f91-9f9dcf94b147@windriver.com> Message-ID: I have create the launchpad: https://bugs.launchpad.net/starlingx/+bug/1986828 Scott On 2022-08-17 09:58, Scott Little wrote: > The stx-mariadb container is failing to build. > > The upstream URL http://ftp.osuosl.org/pub/mariadb/repo/10.2/ubuntu is > no longer available. > > It looks like that version 10.2 has fallen out of support and has been > taken down.? Available versions range from 10.3 to 10.9. From ildiko.vancsa at gmail.com Wed Aug 17 14:52:11 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 17 Aug 2022 07:52:11 -0700 Subject: [Starlingx-discuss] Upcoming TSC and PL/TL elections Message-ID: <93D2C061-CAFE-48F0-B128-241D66F235C8@gmail.com> Hi StarlingX Community, It is a friendly reminder that the time for the fall election[1] period is coming up fast and therefore we need to start planning the process. We need to decide on timeframe for the elections. For TSC we have a nomination, a campaign and a voting period, while for PL/TL elections we have a nomination and a voting period defined officially. We are looking for a 3-week timeframe in the fall that doesn?t collide with any major holidays or milestones in the release process. To avoid major events as well the proposed timeline would be the following: TSC nomination starts @ November 01, 2022 20:45 UTC TSC nomination ends @ November 08, 2022 20:45 UTC PL/TL nomination starts @ November 01, 2022 20:45 UTC PL/TL nomination ends @ November 08, 2022 20:45 UTC TSC campaigning starts @ November 08, 2022 20:45 UTC TSC campaigning ends @ November 15, 2022 20:45 UTC TSC election starts @ November 15, 2022 20:45 UTC TSC election ends @ November 22, 2022 20:45 UTC PL/TL election starts @ November 15, 2022 20:45 UTC PL/TL election ends @ November 22, 2022 20:45 UTC Similarly to last year we have an empty TSC seat[2] that we could try to fill for a half-term during an interim TSC election once the regular elections ended. The interim elections need separate dates to avoid confusions with the regular process. Would the TSC and community prefer to runt he interim elections this time around as well? Please think about your preference about the election process to make sure that people are available to submit nominations as well as to be able to vote in the election process. If you have any questions or comments please reply to this thread or reach out to the election officials[3]. Thanks, [1] https://docs.starlingx.io/election/ [2] https://docs.starlingx.io/governance/reference/tsc/index.html [3] https://docs.starlingx.io/election/#election-officials From scott.little at windriver.com Wed Aug 17 15:12:28 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 17 Aug 2022 11:12:28 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1381 - Failure! In-Reply-To: <1486117798.5.1660639825586.JavaMail.javamailuser@localhost> References: <1486117798.5.1660639825586.JavaMail.javamailuser@localhost> Message-ID: Temporary network issue. Next build was successful. Scott On 2022-08-16 04:50, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_master_master > Build #: 1381 > Status: Failure > Timestamp: 20220816T043002Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220816T043002Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From starlingx.build at gmail.com Thu Aug 18 01:07:53 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 17 Aug 2022 21:07:53 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 368 - Failure! Message-ID: <788385530.32.1660784874930.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 368 Status: Failure Timestamp: 20220818T005636Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220818T005600Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220818T005600Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220818T005600Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220818T005600Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220818T005600Z LAYER: build-containers REGISTRY: docker.io From starlingx.build at gmail.com Thu Aug 18 10:28:48 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 18 Aug 2022 06:28:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 332 - Still Failing! In-Reply-To: <1583164763.25.1660742058812.JavaMail.javamailuser@localhost> References: <1583164763.25.1660742058812.JavaMail.javamailuser@localhost> Message-ID: <340182886.41.1660818529703.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 332 Status: Still Failing Timestamp: 20220818T050036Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220818T050036Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From starlingx.build at gmail.com Thu Aug 18 10:28:40 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 18 Aug 2022 06:28:40 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 575 - Still Failing! In-Reply-To: <1321935728.19.1660742051374.JavaMail.javamailuser@localhost> References: <1321935728.19.1660742051374.JavaMail.javamailuser@localhost> Message-ID: <199965535.35.1660818522309.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 575 Status: Still Failing Timestamp: 20220818T062849Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220818T050036Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220818T050036Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220818T050036Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220818T050036Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220818T050036Z/logs PUBLISH_TIMESTAMP: 20220818T050036Z FLOCK_VERSION: master-centos-stable-20220818T050036Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220818T050036Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220818T050036Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Thu Aug 18 10:28:45 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 18 Aug 2022 06:28:45 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 331 - Still Failing! In-Reply-To: <964472284.22.1660742055354.JavaMail.javamailuser@localhost> References: <964472284.22.1660742055354.JavaMail.javamailuser@localhost> Message-ID: <380924460.38.1660818526117.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 331 Status: Still Failing Timestamp: 20220818T054902Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220818T050036Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220818T050036Z 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/20220818T050036Z/logs MASTER_BUILD_NUMBER: 332 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220818T050036Z/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: 20220818T050036Z DOCKER_BUILD_ID: jenkins-master-containers-20220818T050036Z-builder TIMESTAMP: 20220818T050036Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220818T050036Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220818T050036Z/outputs From starlingx.build at gmail.com Thu Aug 18 12:56:06 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 18 Aug 2022 08:56:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 369 - Still Failing! In-Reply-To: <1426485267.30.1660784871922.JavaMail.javamailuser@localhost> References: <1426485267.30.1660784871922.JavaMail.javamailuser@localhost> Message-ID: <1354772873.44.1660827367908.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 369 Status: Still Failing Timestamp: 20220818T124740Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220818T124718Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20220818T124718Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20220818T124718Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20220818T124718Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20220818T124718Z LAYER: build-containers REGISTRY: docker.io From Ronald.Stone at windriver.com Mon Aug 22 16:02:02 2022 From: Ronald.Stone at windriver.com (Stone, Ronald) Date: Mon, 22 Aug 2022 16:02:02 +0000 Subject: [Starlingx-discuss] Review stx docs zuul implementation Message-ID: My company is researching Zuul for internal StarlingX docs builds. Can someone point out where we could find the config files for StarlingX docs on opendev.org? We're hoping to use them as a jumping off point for an internal implementation. Thanks, Ron Stone -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Mon Aug 22 16:05:58 2022 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 22 Aug 2022 16:05:58 +0000 Subject: [Starlingx-discuss] Review stx docs zuul implementation In-Reply-To: Message-ID: <20220822160558.c6mhjkq45mumxmqf@yuggoth.org> On 2022-08-22 16:02:02 +0000 (+0000), Stone, Ronald wrote: > My company is researching Zuul for internal StarlingX docs builds. That's awesome news! I hope you'll find it as invaluable as I do. > Can someone point out where we could find the config files for > StarlingX docs on opendev.org? We're hoping to use them as a > jumping off point for an internal implementation. If you're talking about the starlingx/docs repo specifically, you'll see there's already a Zuul configuration file in it, though that's really just serving as an entry point for populating some project pipelines with jobs defined in other repos: https://opendev.org/starlingx/docs/src/branch/master/.zuul.yaml In particular, you're adding the openstack-tox-docs job to the check and gate pipelines along with the promote-stx-tox-docs-site job to the promote pipeline. It's also applying the stx-api-ref-jobs template which comes from here: https://opendev.org/starlingx/zuul-jobs/src/branch/master/zuul.d/project-templates.yaml In that project-template entry you can see it's adding variants of build-openstack-api-ref and promote-stx-api-ref jobs to some pipelines as well. Some of these jobs are reused from OpenStack's definitions, as you can tell from their names, though the couple with "stx" in their names are defined in this trusted config repo because they need access to shared credentials in order to be able to write to the publication site: https://opendev.org/openstack/project-config/src/branch/master/zuul.d/starlingx-jobs.yaml The reused OpenStack jobs on the other hand are being consumed from definitions here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/jobs.yaml Zuul jobs also rely on inheritance, so you'll see for example the build-openstack-api-ref job inherits from the openstack-tox-docs job but overrides some specific variables and limits its scope to only triggering on master branches (because in OpenStack, APIs are versioned independently of the software which provides them). Then openstack-tox-docs in turn inherits from opendev-tox-docs with a variety of things overridden. You can find the opendev-tox-docs definition here: https://opendev.org/opendev/base-jobs/src/branch/master/zuul.d/jobs.yaml So I can already hear you asking, "how do I find and keep all these different sources/locations straight?" Zuul actually has a browseable configuration in its WebUI. You can see the project entry here shows all the jobs defined to run for various pipelines: https://zuul.opendev.org/t/openstack/project/opendev.org/starlingx/docs If you click on the build-openstack-api-ref entry, for example, it will take you to details about that job including the project and file which contains its definition along with a hyperlinked parent entry, which you can follow to get a similar view of the inherited job (continuing until you hit bedrock at the job named "base"). If you get stuck, all of those repositories can also be searched here: https://codesearch.opendev.org/ So anyway, that covers the basics of job definitions and how they're selected, but what do they actually run? For that you'll want to look for the "run" (often also "pre-run" and "post-run") playbooks. Those are paths to Ansible playbook files in the repositories where the job definitions reside. In the case of openstack-tox-docs for example, you'll see its run phase uses this playbook: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/playbooks/tox-docs/run.yaml The roles in there are reusable sets of tasks (instructions basically), which can usually either be found in a "roles" top-level directory of the same project, or in a project expressly listed as providing additional roles in that job's definition or that of one of its ancestors. In this case you'll see Zuul's standard library (included by the "base" job definition) provides those revoke-sudo and tox roles, while build-pdf-docs comes from openstack/openstack-zuul-jobs where the job definition resides: https://opendev.org/zuul/zuul-jobs/src/branch/master/roles https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/roles As for what goes in roles and playbooks, well, that's the point at which you should consult the Ansible documentation, but I'm going to assume this is at least enough to get you started. -- 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 ildiko.vancsa at gmail.com Tue Aug 23 20:07:28 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 23 Aug 2022 13:07:28 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - TIME SLOT UPDATE In-Reply-To: <04B5EB72-75E4-49D2-BCE3-AD2662366162@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> <5678480B-C5F0-4DEC-BB77-6216B5938726@gmail.com> <04B5EB72-75E4-49D2-BCE3-AD2662366162@gmail.com> Message-ID: Hi StarlingX Community, I?m reaching out to you with a short update. The OpenInfra Board of Directors - StarlingX meeting is now scheduled to be held on September 7 (Wednesday) at 6am PDT / 1300 UTC. We are building the agenda for the meeting here: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync Please add any topics that you would like to discuss with the OpenInfra BoD members during the meeting. I also added the dial-in details to the etherpad. Please let me know if you would need a meeting invite or if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 15, 2022, at 13:44, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > Thank you all who filled out the polls. I?m reaching out to share the results. > > The preferred option to have the OpenInfra Board of Directors - StarlingX meeting is September 7 (Wednesday) at 6am PDT / 1300 UTC. > > Further options that could potentially work include the same time slot on September 8 (Thursday) and September 14 (Wednesday). > > I will share the preferred time slot with the Board with the hope that it will work, and will opt to fallback options in case needed. > > Thanks and Best Regards, > Ildik? > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Aug 11, 2022, at 12:17, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> It is a friendly reminder that we have two polls open in an attempt to find a few options to set up a call with the OpenInfra Foundation Board of Directors: >> >> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >> >> __Please submit your preferences by August 14, 2022.__ >> >> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra BoD group! >> >> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Aug 3, 2022, at 00:06, Ildiko Vancsa wrote: >>> >>> Hi, >>> >>> I?m reaching out to you as unfortunately the time slot that the StarlingX community preferred for this week will not work: https://lists.openinfra.dev/pipermail/foundation-board/2022-August/000658.html >>> >>> Many of our Board members are not available and therefore we will need to move the sync call to a later date. Based on our poll for August, there are no good dates for this month to move the call. I created two new polls to find new options in September and October: >>> >>> * Poll for September: https://doodle.com/meeting/participate/id/dRg3BNEe >>> * Poll for October: https://doodle.com/meeting/participate/id/dRg3B9Oe >>> >>> __Please submit your preferences by August 14, 2022.__ >>> >>> As a reminder, our agenda etherpad for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>> >>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem >>> Open Infrastructure Foundation >>> >>> >>> >>>> On Jul 27, 2022, at 14:32, Ildiko Vancsa wrote: >>>> >>>> Hi Greg, >>>> >>>> I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. >>>> >>>> Best Regards, >>>> Ildik? >>>> >>>> >>>>> On Jul 27, 2022, at 12:55, Waines, Greg wrote: >>>>> >>>>> I can't find the zoom link for the meeting ... do you have it ? >>>>> Greg. >>>>> >>>>> -----Original Message----- >>>>> From: Ildiko Vancsa >>>>> Sent: Wednesday, July 27, 2022 2:16 AM >>>>> To: Waines, Greg >>>>> Cc: StarlingX ML >>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE >>>>> >>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>> >>>>> Hi Greg, >>>>> >>>>> Great, thank you for being available! >>>>> >>>>> The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. >>>>> >>>>> I think diversity is a great topic for the call and should be a basis for a good discussion. >>>>> >>>>> I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! >>>>> >>>>> If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. >>>>> >>>>> Thanks and Best Regards, >>>>> Ildik? >>>>> >>>>> ??? >>>>> >>>>> Ildik? V?ncsa >>>>> Senior Manager, Community & Ecosystem >>>>> Open Infrastructure Foundation >>>>> >>>>> >>>>> >>>>>> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >>>>>> >>>>>> hey Ildiko, >>>>>> I am available on the Aug 4 1300 UTC timeslot. >>>>>> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >>>>>> >>>>>> I added our favourite discussion topic to the etherpad: >>>>>> * Looking for guidance on diversifying the Users and >>>>>> Contributors in the community >>>>>> >>>>>> Greg. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ildiko Vancsa >>>>>> Sent: Tuesday, July 26, 2022 5:47 AM >>>>>> To: StarlingX ML >>>>>> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >>>>>> StarlingX Sync - UPDATE >>>>>> >>>>>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>>>>> >>>>>> Hi StarlingX Community, >>>>>> >>>>>> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >>>>>> >>>>>> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >>>>>> >>>>>> You can see the original email and follow the thread here: >>>>>> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >>>>>> 6.html >>>>>> >>>>>> As a reminder, we have an etherpad to propose topics for the call and >>>>>> take notes during the meeting: >>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>> >>>>>> Please let me know if you have any questions. >>>>>> >>>>>> Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Senior Manager, Community & Ecosystem >>>>>> Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>>>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>>>>>> >>>>>>> Hi StarlingX Community, >>>>>>> >>>>>>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>>>>>> >>>>>>> You can find the poll here: >>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>> >>>>>>> __Please submit your preferences on the poll by the end of day on >>>>>>> July 20, 2022.__ >>>>>>> >>>>>>> >>>>>>> I created an etherpad to collect potential topics for the >>>>>>> conversation and build an agenda for the call. Please add discussion >>>>>>> points that you think would be important to bring up during the call: >>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>> >>>>>>> Please let me know if you have any questions. >>>>>>> >>>>>>> Best Regards, >>>>>>> Ildik? >>>>>>> >>>>>>> ??? >>>>>>> >>>>>>> Ildik? V?ncsa >>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>>>>>> >>>>>>>> Hi StarlingX Community, >>>>>>>> >>>>>>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>>>>>> >>>>>>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>>>>>> >>>>>>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>>>>>> >>>>>>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>>>>>> >>>>>>>> I created an etherpad to collect potential topics for the >>>>>>>> conversation and build an agenda for the call: >>>>>>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>>>>>> >>>>>>>> I also created a poll to try to find time slot options that we can >>>>>>>> share with the OpenInfra Board of Directors. The poll is covering >>>>>>>> options for August, if we fail to find good options for that month, I >>>>>>>> will extend it to September. Please find the poll here: >>>>>>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>>>>>> >>>>>>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>>>>>> >>>>>>>> __Please submit your preferences by the end of day on July 20, >>>>>>>> 2022.__ >>>>>>>> >>>>>>>> Please let me know if you have any questions. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Ildik? >>>>>>>> >>>>>>>> ??? >>>>>>>> >>>>>>>> Ildik? V?ncsa >>>>>>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>> >>> >> > From ildiko.vancsa at gmail.com Tue Aug 23 20:22:40 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 23 Aug 2022 13:22:40 -0700 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call - UPDATE In-Reply-To: <0B6F9FE5-4C2D-4754-AE77-1F42575391B5@gmail.com> References: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> <967ECD42-3FF6-4E2D-9BBC-7FA60AC6D8B8@99cloud.net> <0B6F9FE5-4C2D-4754-AE77-1F42575391B5@gmail.com> Message-ID: <7BF66916-1FDB-4359-B225-6CA941180773@gmail.com> Hi StarlingX Community, Thank you to all of you who participated in this conversation. There was only positive feedback to our preferred option to alternate the TSC & Community call to make it more inclusive around the globe. The community settled on having the APAC friendly call every first Wednesday (US Time) / Thursday (APAC Time) of the month. The first meeting in the APAC-friendly time slot will be on the 7th of September at at 7pm PDT/ 10pm EDT / 8th of September at 10am CST. I also updated the Meetings wiki page accordingly. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Aug 14, 2022, at 11:24, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > Thank you to all of you who voiced your opinions already. > > So far the favored option is #2, which would be having the APAC friendly call every first Wednesday (US Time) of the month. > > If the community settles on this option, the first meeting in the APAC-friendly time slot would be on the 7th of September at at 7pm PDT/ 10pm EDT / 8th of September at 10am CST. > > If you have a different preference or have any questions, please reply to this thread or reach out to me directly. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation From starlingx.build at gmail.com Wed Aug 24 03:51:46 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 23 Aug 2022 23:51:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3101 - Failure! Message-ID: <1431315045.63.1661313111312.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3101 Status: Failure Timestamp: 20220824T033439Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220824T025955Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20220824T025955Z DOCKER_BUILD_ID: jenkins-master-flock-20220824T025955Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220824T025955Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20220824T025955Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Wed Aug 24 03:51:54 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 23 Aug 2022 23:51:54 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 940 - Failure! Message-ID: <1799572228.66.1661313115501.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 940 Status: Failure Timestamp: 20220824T025955Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220824T025955Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Wed Aug 24 09:53:13 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 24 Aug 2022 05:53:13 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1389 - Failure! Message-ID: <379748097.74.1661334794281.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1389 Status: Failure Timestamp: 20220824T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220824T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Wed Aug 24 09:53:09 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 24 Aug 2022 05:53:09 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1532 - Failure! Message-ID: <577476678.71.1661334790482.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1532 Status: Failure Timestamp: 20220824T044204Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220824T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220824T043000Z DOCKER_BUILD_ID: jenkins-master-20220824T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220824T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220824T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From Rob.Cooke at windriver.com Wed Aug 24 14:07:45 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Wed, 24 Aug 2022 14:07:45 +0000 Subject: [Starlingx-discuss] Sanity R7.0 Test LAYERED build ISO 20220806T013941Z Message-ID: Hi everyone, I have just corrected the title on this email report. This is the sanity report for R7.0, not master. The title was leading us to think that sanity had not been executed on the R7.0 branch, but as per the report details below, it has. Thanks, Rob From: Peng, Peng Sent: Tuesday, August 9, 2022 11:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220806T013941Z Sanity Test from 2022-August-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220806T013941Z/outputs/iso/) Status: GREEN Sanity Test executed on Bare Metal Environment AIO - Simplex Setup 1 TCs [PASS] Sanity Platform 08 TCs [PASS] Daily Regression Platform 09 TCs [PASS] TOTAL: [ 18 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity[1-1-calico-ipam-4] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_push_docker_image_to_local_registry[active] PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod[2_0-fill_fill-static-best-effort-HT-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] 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_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] 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_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Aug 24 14:46:14 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 24 Aug 2022 10:46:14 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 940 - Failure! In-Reply-To: <1799572228.66.1661313115501.JavaMail.javamailuser@localhost> References: <1799572228.66.1661313115501.JavaMail.javamailuser@localhost> Message-ID: <0d3fda0f-acb1-68a3-872d-150c3300f5e7@windriver.com> build-iso failure ... ??? Could not resolve packages: stx-audit-helm-armada I've opened... https://bugs.launchpad.net/starlingx/+bug/1987533 to track it. Scott On 2022-08-23 23:51, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_flock_master_master > Build #: 940 > Status: Failure > Timestamp: 20220824T025955Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220824T025955Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From starlingx.build at gmail.com Thu Aug 25 04:31:49 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 25 Aug 2022 00:31:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 941 - Still Failing! In-Reply-To: <1721217030.64.1661313112655.JavaMail.javamailuser@localhost> References: <1721217030.64.1661313112655.JavaMail.javamailuser@localhost> Message-ID: <578634596.83.1661401910732.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 941 Status: Still Failing Timestamp: 20220825T034303Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220825T034303Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Thu Aug 25 04:31:46 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 25 Aug 2022 00:31:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3104 - Failure! Message-ID: <1406392221.80.1661401907794.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3104 Status: Failure Timestamp: 20220825T041521Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220825T034303Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20220825T034303Z DOCKER_BUILD_ID: jenkins-master-flock-20220825T034303Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220825T034303Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20220825T034303Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Thu Aug 25 09:07:06 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 25 Aug 2022 05:07:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1533 - Still Failing! In-Reply-To: <808765447.69.1661334786283.JavaMail.javamailuser@localhost> References: <808765447.69.1661334786283.JavaMail.javamailuser@localhost> Message-ID: <1851239199.86.1661418427797.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1533 Status: Still Failing Timestamp: 20220825T044248Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220825T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220825T043000Z DOCKER_BUILD_ID: jenkins-master-20220825T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220825T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220825T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Thu Aug 25 09:07:10 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 25 Aug 2022 05:07:10 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1390 - Still Failing! In-Reply-To: <2100613956.72.1661334791696.JavaMail.javamailuser@localhost> References: <2100613956.72.1661334791696.JavaMail.javamailuser@localhost> Message-ID: <199572720.89.1661418431267.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1390 Status: Still Failing Timestamp: 20220825T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220825T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Ghada.Khalil at windriver.com Thu Aug 25 12:12:58 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 25 Aug 2022 12:12:58 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Aug 24/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.7.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlyclfKFVxKo/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - Build - Nothing to report. Builds are setup to run on-demand, so need to request a build from Scott/Davlet if there are any new merges in the r/stx.7.0 branch. - One build was issued on Aug 18 to address an issue w/ helm chart generation. There were no functional changes. - http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220818T132617Z/ - Sanity Update - Sanity on r/stx.7.0 - r/stx.7.0 sanity was successful on Aug 9: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013246.html - Note email title is incorrect; it mentions "Master" instead of "stx.7.0" - There has been no functional changes since then, but one build was issued to correct helm charts. - Sanity on r/stx.7.0 w/ stx-openstack - Team still working thru internal env issues. Forecast: Aug 31 - A fix will be needed for https://bugs.launchpad.net/starlingx/+bug/1970645 - Another sanity execution will be needed once the above LP is addressed. - Note: Sanity for r/stx.7.0 is focused on CentOS builds. There are no plans to do Debian sanity for r/stx.7.0. A Debian rc build is available though for experimental purposes. - Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - One LP re-opened for openstack apply timeout. https://bugs.launchpad.net/starlingx/+bug/1970645 - Issue was reproduced when running experimental sanity. Fixes are in progress. Forecast: Aug 26 - Note: cherry-pick and rebuild of r/stx.7.0 will be required. - Action: Thales to send a request for the build and sanity once the fix is available in the r/stx.7.0 branch. - Docs - Release Notes Review: https://review.opendev.org/c/starlingx/docs/+/850424 - Need reviewers. Ghada/Frank to review this week. - stx.7.0 Milestones - Sanity/Final Regression Complete: Aug 17 >> Re-forecast: Aug 31 - Not Achieved. Sanity w/ openstack is still outstanding and final regression is starting today. - Release: Aug 24 >> Re-forecast: Sep 7 - Next Steps towards releasing stx.7.0 - Complete successful sanity on r/stx.7.0 w/ stx-openstack - If not green, track blocking LPs that need to be resolved. - Fixes need to go in the stx main branch first and then cherrypicked to the r/stx.7.0 branch - Repeat until green sanity - Tag branch w/ final green RC build. Copy RC build to the release directory. Stop daily scheduled builds. - Anything for docs?? - Send announcement to mailing list - Blogs - Release Announcement - Prime: Ildiko - In progress. https://github.com/StarlingXWeb/starlingx-website/pull/201/ - Debian OS Migration - Prime: Frank Miller - In progress. https://github.com/StarlingXWeb/starlingx-website/pull/190/commits/ca7f8b155fa2e6f64620a94596d609f028c99e1e - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept / Author: Cole Walker - Subcloud Local Install - Prime: RamS - Forecast: ?? << still need a forecast stx.8.0 - Reference Links: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?usp=sharing - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit?usp=sharing - Milestone Discussion - Agreed to shift MS-1 and follow-up milestones to allow focus on releasing stx.7.0 - MS-1 re-forecasted to Sep 21. Subsequent milestones are updated accordingly. - Content Discussion - Additional candidate features have been added to the release planning spreadsheet. - Action: Linda to add features planned by the OS team. - Action: Rob to look at features planned by the Build team - Rob is filling in as Anthony Nowell is no longer with WR. From Ghada.Khalil at windriver.com Thu Aug 25 12:35:39 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 25 Aug 2022 12:35:39 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Aug 24 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Aug 24 2022 Standing topics - Build - r/stx.7.0 Builds - Both CentOS and Debian are setup to build on demand. - Build requests should be sent to Scott/Davlet and cc the mailing list. Peng/Rob should be copied to initiate sanity. - Main Branch CentOS Builds - Build failed today due to a recent update which removed audit-helm armada. Suspect Review: https://review.opendev.org/c/starlingx/audit-armada-app/+/853820 - Action: Scott to open an LP and assign to the developer who introduced the above commit - Main Branch Debian Builds - Debian build is in progress, but may fail for the same reason. - Note: Debian builds are taking a large amount of resources to keep the build artifacts. - This is something that the build team will need to look into. May be forced to keep a much shorter build history for Debian builds. - Looking to remove stx.5.0 build artifcats from CENGN build server - Will proceed with this once stx.7.0 is released. - Note: policy is to keep full CENGN builds for last two releases - Sanity - Main Sanity w/o stx-openstack - Executing min 1/week ... - No main sanity executions in the last two weeks due to focus on stx.7.0 and vacations. Will go back to this cadence starting next week. - Main Sanity w/ stx-openstack - Plan is to execute min 1/week ... - Still working thru env issues to get sanity running w/ stx-openstack. Forecast: Aug 31. - stx.7.0 sanity - Executing whenever new builds done - Sanity is Green for last build for non-openstack - Sanity is not executed for last build on openstack - Working thru env/setup issues - Also need a fix for LP: https://bugs.launchpad.net/starlingx/+bug/1970645 Forecast: Aug 26. Prime: Thales - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes - review is still open: - https://review.opendev.org/c/starlingx/docs/+/850424 - Action: Ghada/Frank to review this week. Greg is off this week. - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - stx.7.0 Status - Release Branch: - https://review.opendev.org/q/branch:r/stx.7.0 - A few reviews are still open: https://review.opendev.org/q/branch:r/stx.7.0+status:open - Zuul issues seem to be addressed. - Two remaining open reviews which are minor as they just setup the .gitreview for the repo - Expecting one fix for the openstack LP: https://bugs.launchpad.net/starlingx/+bug/1970645 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - One LP: https://bugs.launchpad.net/starlingx/+bug/1970645 - Release Milestones ( https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 ) - Re-forecasted. - Sanity/Final Regression Complete: Aug 17 >> Re-forecast: Aug 31 - Release: Aug 24 >> Re-forecast: Sep 7 - Upcoming TSC & PL/TL Elections - Time-line proposal sent by Ildiko: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013272.html - TSC & Community Meeting Schedule - Updated to meet during an APAC-friendly time once a month; first Wednesday of the month - First meeting on Sept 7. - Action: Ghada to send new invites to the mailing list. - Board of Directors Meeting - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013281.html - Scheduled on Sept 7. - Etherpad available to collect topics for discussion: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync ARs from Previous Meetings - None Open Requests for Help - Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html - Still no response on the thread, the person followed-up with mentioning issues of nvidia driver install - Action: Greg ... still pending due to vacation. - Wireguard issue - proposal discussed in OS meeting to enable parameter without testing (due to effort); pending agreement with Linda (PL) - Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125 From Juanita.Balaraj at windriver.com Thu Aug 25 13:27:14 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 25 Aug 2022 13:27:14 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 17-August-22 Message-ID: Hello all, Here are last 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 ============ 17-August-22 StarlingX 7.0 Release: https://review.opendev.org/c/starlingx/docs/+/839236 - To discuss updates. - Stx 7.0 GA date is now week of August 29th - TBC - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date. Gerrit Reviews: - 2 Cherry picks this week. Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - https://review.opendev.org/c/starlingx/docs/+/851209 - Synched with Litao Gao. This update is STARLINGX Only. Needs to be reviewed and approved by the Docs team - https://bugs.launchpad.net/starlingx/+bug/1982058 - Total 8 bugs - Fixed 4 Launchpad Doc Bugs: - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; Done https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold - https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa General: - Operations Guide Archive - On Hold until further clarifications are discussed (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 Juanita.Balaraj at windriver.com Thu Aug 25 13:32:02 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 25 Aug 2022 13:32:02 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 24-August-22 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 24-August-22 StarlingX 7.0 Release: - Stx 7.0 GA date is now September 7th - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron Gerrit Reviews: - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - Docs team to confirm the date. - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open ; 4 Cherry picks this week to Stx 6.0/5.0. Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 7 bugs outstanding General: - Operations Guide Archive - On Hold until further clarifications are discussed (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 Mon Aug 29 14:14:08 2022 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Mon, 29 Aug 2022 14:14:08 +0000 Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build Message-ID: Hi StarlingX Community, As part of the release 7.0 sanity efforts, the initial StarlingX + StarlingX Openstack executions reproduced that old bug [1] reported this year that was previously marking the sanity as RED. The team already proposed the fix for it [2] and it was merged into both main and r/stx.7.0 branches. I know we are currently building this branch on-demand, so am kindly requesting a new build (whenever it is possible) to have this fix officially in place for our next Sanity rounds. [1] https://bugs.launchpad.net/starlingx/+bug/1970645 [2] https://review.opendev.org/q/topic:bug%252F1970645 Thanks and best regards. Thales -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Aug 29 14:29:29 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 29 Aug 2022 14:29:29 +0000 Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build In-Reply-To: References: Message-ID: @Panech, Davlet can you please trigger the stx.7.0 build since Scott is away this week? Please respond to this email when the build is ready. Thanks. @Cooke, Rob please arrange for stx.7.0 sanity w/ openstack. Thanks, Ghada From: Cervi, Thales Elero Sent: Monday, August 29, 2022 10:14 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build Hi StarlingX Community, As part of the release 7.0 sanity efforts, the initial StarlingX + StarlingX Openstack executions reproduced that old bug [1] reported this year that was previously marking the sanity as RED. The team already proposed the fix for it [2] and it was merged into both main and r/stx.7.0 branches. I know we are currently building this branch on-demand, so am kindly requesting a new build (whenever it is possible) to have this fix officially in place for our next Sanity rounds. [1] https://bugs.launchpad.net/starlingx/+bug/1970645 [2] https://review.opendev.org/q/topic:bug%252F1970645 Thanks and best regards. Thales -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Aug 30 08:30:17 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 30 Aug 2022 04:30:17 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 577 - Failure! Message-ID: <2024084360.101.1661848219467.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 577 Status: Failure Timestamp: 20220830T041710Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220830T030046Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220830T030046Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220830T030046Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220830T030046Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220830T030046Z/logs PUBLISH_TIMESTAMP: 20220830T030046Z FLOCK_VERSION: master-centos-stable-20220830T030046Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220830T030046Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220830T030046Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Tue Aug 30 08:30:24 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 30 Aug 2022 04:30:24 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 333 - Failure! Message-ID: <2004138761.104.1661848225411.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 333 Status: Failure Timestamp: 20220830T034700Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220830T030046Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220830T030046Z 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/20220830T030046Z/logs MASTER_BUILD_NUMBER: 334 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220830T030046Z/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: 20220830T030046Z DOCKER_BUILD_ID: jenkins-master-containers-20220830T030046Z-builder TIMESTAMP: 20220830T030046Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220830T030046Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220830T030046Z/outputs From starlingx.build at gmail.com Tue Aug 30 08:30:29 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 30 Aug 2022 04:30:29 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 334 - Failure! Message-ID: <124576625.107.1661848230215.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 334 Status: Failure Timestamp: 20220830T030046Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220830T030046Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Davlet.Panech at windriver.com Tue Aug 30 13:13:50 2022 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 30 Aug 2022 13:13:50 +0000 Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build In-Reply-To: References: Message-ID: A new flock build is in progress. ________________________________ From: Khalil, Ghada Sent: August 29, 2022 10:29 AM To: Cervi, Thales Elero ; starlingx-discuss at lists.starlingx.io ; Panech, Davlet ; Cooke, Rob Subject: RE: Requesting r/stx.7.0 new flock build @Panech, Davlet can you please trigger the stx.7.0 build since Scott is away this week? Please respond to this email when the build is ready. Thanks. @Cooke, Rob please arrange for stx.7.0 sanity w/ openstack. Thanks, Ghada From: Cervi, Thales Elero Sent: Monday, August 29, 2022 10:14 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build Hi StarlingX Community, As part of the release 7.0 sanity efforts, the initial StarlingX + StarlingX Openstack executions reproduced that old bug [1] reported this year that was previously marking the sanity as RED. The team already proposed the fix for it [2] and it was merged into both main and r/stx.7.0 branches. I know we are currently building this branch on-demand, so am kindly requesting a new build (whenever it is possible) to have this fix officially in place for our next Sanity rounds. [1] https://bugs.launchpad.net/starlingx/+bug/1970645 [2] https://review.opendev.org/q/topic:bug%252F1970645 Thanks and best regards. Thales -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Tue Aug 30 16:29:05 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 30 Aug 2022 11:29:05 -0500 Subject: [Starlingx-discuss] Fwd: PTG October 2022 Teams List In-Reply-To: References: Message-ID: Hello Everyone! The October 2022 Project Teams List is official! Projects + Teams: - Computing Force Network (CFN) Working Group - Diversity& Inclusion Working Group - Environmental Sustainability Working Group - Kata Containers - Magma - OpenInfra Edge Computing Group - OpenStack Teams - - Ansible OpenStack Modules - Barbican - Blazar - Cinder - CloudKitty - Designate - First Contact SIG - Glance - Heat - Horizon - Interop WG - Ironic - Keystone - Kolla - Kuryr - Manila - Neutron - Nova/Placement - Octavia - OpenStack Charms - OpenStack Helm - OpenStack Operators - OpenStack SDK/CLI - OpenStack Security SIG - OpenStack Technical Committee - Openstack-Ansible - OpenStack-Helm - QA - Release Management - Swift - Tacker - Telemetry - TripleO - StarlingX If your team was planning to meet and isn?t in this list, please contact ptg at openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign 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 starlingx.build at gmail.com Wed Aug 31 10:47:38 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 31 Aug 2022 06:47:38 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 578 - Still Failing! In-Reply-To: <493983871.99.1661848212361.JavaMail.javamailuser@localhost> References: <493983871.99.1661848212361.JavaMail.javamailuser@localhost> Message-ID: <1099299496.2.1661942860225.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 578 Status: Still Failing Timestamp: 20220831T061455Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220831T044406Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220831T044406Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20220831T044406Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220831T044406Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220831T044406Z/logs PUBLISH_TIMESTAMP: 20220831T044406Z FLOCK_VERSION: master-centos-stable-20220831T044406Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20220831T044406Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220831T044406Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Wed Aug 31 10:47:42 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 31 Aug 2022 06:47:42 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 334 - Still Failing! In-Reply-To: <1140587224.102.1661848222793.JavaMail.javamailuser@localhost> References: <1140587224.102.1661848222793.JavaMail.javamailuser@localhost> Message-ID: <60061584.5.1661942863255.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 334 Status: Still Failing Timestamp: 20220831T053620Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220831T044406Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220831T044406Z 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/20220831T044406Z/logs MASTER_BUILD_NUMBER: 335 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220831T044406Z/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: 20220831T044406Z DOCKER_BUILD_ID: jenkins-master-containers-20220831T044406Z-builder TIMESTAMP: 20220831T044406Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220831T044406Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20220831T044406Z/outputs From starlingx.build at gmail.com Wed Aug 31 10:47:45 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 31 Aug 2022 06:47:45 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 335 - Still Failing! In-Reply-To: <1592849164.105.1661848227738.JavaMail.javamailuser@localhost> References: <1592849164.105.1661848227738.JavaMail.javamailuser@localhost> Message-ID: <325464341.8.1661942866792.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 335 Status: Still Failing Timestamp: 20220831T044406Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220831T044406Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Rob.Cooke at windriver.com Wed Aug 31 13:32:34 2022 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Wed, 31 Aug 2022 13:32:34 +0000 Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build In-Reply-To: References: Message-ID: Seems the build has completed. http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220830T131020Z/ We are setting up to execute sanity on STX and STX+Openstack. Results to follow. Thanks, Rob From: Panech, Davlet Sent: Tuesday, August 30, 2022 9:14 AM To: Khalil, Ghada ; Cervi, Thales Elero ; starlingx-discuss at lists.starlingx.io; Cooke, Rob Subject: Re: Requesting r/stx.7.0 new flock build A new flock build is in progress. ________________________________ From: Khalil, Ghada > Sent: August 29, 2022 10:29 AM To: Cervi, Thales Elero >; starlingx-discuss at lists.starlingx.io >; Panech, Davlet >; Cooke, Rob > Subject: RE: Requesting r/stx.7.0 new flock build @Panech, Davlet can you please trigger the stx.7.0 build since Scott is away this week? Please respond to this email when the build is ready. Thanks. @Cooke, Rob please arrange for stx.7.0 sanity w/ openstack. Thanks, Ghada From: Cervi, Thales Elero > Sent: Monday, August 29, 2022 10:14 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build Hi StarlingX Community, As part of the release 7.0 sanity efforts, the initial StarlingX + StarlingX Openstack executions reproduced that old bug [1] reported this year that was previously marking the sanity as RED. The team already proposed the fix for it [2] and it was merged into both main and r/stx.7.0 branches. I know we are currently building this branch on-demand, so am kindly requesting a new build (whenever it is possible) to have this fix officially in place for our next Sanity rounds. [1] https://bugs.launchpad.net/starlingx/+bug/1970645 [2] https://review.opendev.org/q/topic:bug%252F1970645 Thanks and best regards. Thales -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Aug 31 14:27:19 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 31 Aug 2022 14:27:19 +0000 Subject: [Starlingx-discuss] StarlingX PTG Planning ... Message-ID: StarlingX Community, The Fall StarlingX PTG is coming soon: o Monday, October 17th to Thursday, October 20th, 2022 ( VIRTUAL ONLY ) o Specific StarlingX Times are TBD ... but tentatively o Tuesday, October 18 - 1300 UTC - 1700 UTC o Wednesday, October 19 - 1300 UTC - 1700 UTC o Thursday, October 20 - 1300 UTC - 1700 UTC I have setup an etherpad for gathering planned attendance and brainstorming on proposed topics. Please add your name if you're planning on attending and add any topics that you are interested in discussing. https://etherpad.opendev.org/p/stx-ptg-planning-october-2022 thanks, Greg. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Aug 31 14:33:06 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 31 Aug 2022 14:33:06 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a ?recheck? this morning still failed. Thanks, Ghada PS: It?s recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu ; Shivashankara Belur, Nidhi ; Khalil, Ghada ; Somerville, Jim ; Panech, Davlet ; Little, Scott ; Kantek, Andre Fernando Zanella ; Koerich, Douglas Henrique ; Ho, Teresa Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn?t quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thiago.Brito at windriver.com Wed Aug 31 15:07:07 2022 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Wed, 31 Aug 2022 15:07:07 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a ?recheck? this morning still failed. Thanks, Ghada PS: It?s recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu ; Shivashankara Belur, Nidhi ; Khalil, Ghada ; Somerville, Jim ; Panech, Davlet ; Little, Scott ; Kantek, Andre Fernando Zanella ; Koerich, Douglas Henrique ; Ho, Teresa Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn?t quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Wed Aug 31 16:18:33 2022 From: Linda.Wang at windriver.com (Wang, Linda) Date: Wed, 31 Aug 2022 16:18:33 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting Message-ID: Hi, Due to last minute issue, moving this meeting to September 6th . Sorry for any inconvenience that this may have caused. Thanks! * Cadence and time slot: * Bi-Weekly Wednesday 0930 EDT (1430 UTC, 2230 China time, 0630 PT time) * Call Details: * Zoom link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * Passcode: 419405 * International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: * https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 8057 bytes Desc: not available URL: From ildiko.vancsa at gmail.com Wed Aug 31 17:41:33 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 31 Aug 2022 10:41:33 -0700 Subject: [Starlingx-discuss] Upcoming TSC and PL/TL elections In-Reply-To: <93D2C061-CAFE-48F0-B128-241D66F235C8@gmail.com> References: <93D2C061-CAFE-48F0-B128-241D66F235C8@gmail.com> Message-ID: Hi StarlingX Community, A quick update in preparation tot he upcoming TSC and PL/TL elections. As there were no objections to the proposed timeline so far I created a patch to update the timeline on the election website: https://review.opendev.org/c/starlingx/election/+/855391 Please review the above change and leave any comments if you see any conflicts, typos or have any questions. You can also reach out to the election officials[1] if you have any questions regarding the elections. A still outstanding item: Similarly to last year we have an empty TSC seat[2] that we could try to fill for a half-term during an interim TSC election once the regular elections ended. The interim elections need separate dates to avoid confusions with the regular process. Would the TSC and community prefer to run the interim elections this time around as well? Thanks, [1] https://docs.starlingx.io/election/#election-officials [2] https://docs.starlingx.io/governance/reference/tsc/index.html > On Aug 17, 2022, at 07:52, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder that the time for the fall election[1] period is coming up fast and therefore we need to start planning the process. > > We need to decide on timeframe for the elections. For TSC we have a nomination, a campaign and a voting period, while for PL/TL elections we have a nomination and a voting period defined officially. > > We are looking for a 3-week timeframe in the fall that doesn?t collide with any major holidays or milestones in the release process. To avoid major events as well the proposed timeline would be the following: > > TSC nomination starts @ November 01, 2022 20:45 UTC > TSC nomination ends @ November 08, 2022 20:45 UTC > PL/TL nomination starts @ November 01, 2022 20:45 UTC > PL/TL nomination ends @ November 08, 2022 20:45 UTC > > TSC campaigning starts @ November 08, 2022 20:45 UTC > TSC campaigning ends @ November 15, 2022 20:45 UTC > > TSC election starts @ November 15, 2022 20:45 UTC > TSC election ends @ November 22, 2022 20:45 UTC > PL/TL election starts @ November 15, 2022 20:45 UTC > PL/TL election ends @ November 22, 2022 20:45 UTC > > > Similarly to last year we have an empty TSC seat[2] that we could try to fill for a half-term during an interim TSC election once the regular elections ended. The interim elections need separate dates to avoid confusions with the regular process. Would the TSC and community prefer to runt he interim elections this time around as well? > > Please think about your preference about the election process to make sure that people are available to submit nominations as well as to be able to vote in the election process. > > If you have any questions or comments please reply to this thread or reach out to the election officials[3]. > > Thanks, > > [1] https://docs.starlingx.io/election/ > [2] https://docs.starlingx.io/governance/reference/tsc/index.html > [3] https://docs.starlingx.io/election/#election-officials > > > From nidhi.shivashankara.belur at intel.com Wed Aug 31 23:23:24 2022 From: nidhi.shivashankara.belur at intel.com (Shivashankara Belur, Nidhi) Date: Wed, 31 Aug 2022 23:23:24 +0000 Subject: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration In-Reply-To: References: <5b1c4621cffb959d33fc798a2a37157f89763d43-EmailReviewComments-HTML@review.opendev.org> Message-ID: I updated the pylint env from "python3" to "python3.6", but it still failed. GLOB sdist-make: /home/zuul/src/opendev.org/starlingx/app-sriov-fec-operator/python-k8sapp-sriov-fec-operator/k8sapp_sriov_fec_operator/setup.py pylint create: /tmp/zuul_k8sapp_sriov_fec_operatortox/pylint ERROR: InterpreterNotFound: python3.6 ___________________________________ summary ____________________________________ ERROR: pylint: InterpreterNotFound: python3.6 Link: Zuul Build (opendev.org) Can you please suggest what is the fix for this issue? Thank you, Nidhi From: Brito, Thiago Sent: Wednesday, August 31, 2022 8:07 AM To: Khalil, Ghada ; Shivashankara Belur, Nidhi ; Burla, Balendu Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Hi, Expanding the logs I see that the error is related to an unavailable bdist_wininst command during the wheel creation to install on the tox venv. It seems like this was deprecated on python3.8 (which is the default on the node being used when you provide basepython=python3) and removed from setuptools at some point during that cycle; but you are using the upper-requirements from Openstack stein in your tox setup, so I think it is installing a weird setuptools version. I recommend using basepython=python3.6 for the pylint env (if you can manage to use python3.9 and the debian upper-constraints, it's even better, but I think you'd have to tweak zuul.yml to change the nodeset as well). [1]https://discuss.python.org/t/remove-bdist-wininst-command/6434 [https://aws1.discourse-cdn.com/business6/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png] Remove bdist_wininst command - Discussions on Python.org and that someone also steps up to actively maintain this and work on existing issues. FWIW, bdist_wininst is currently broken on 3.8+, and a PR has languished for over 3 months - but people can work around that by applying the patch to the python version that builds the distribution. discuss.python.org Thiago ________________________________ From: Khalil, Ghada > Sent: Wednesday, August 31, 2022 11:33 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Adding the stx-discuss mailing list for wider visibility in case someone is able to comment/help with. It appears that a "recheck" this morning still failed. Thanks, Ghada PS: It's recommended to always include the mailing list on reported issues. From: Shivashankara Belur, Nidhi > Sent: Tuesday, August 30, 2022 9:04 PM To: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Somerville, Jim >; Panech, Davlet >; Little, Scott >; Kantek, Andre Fernando Zanella >; Koerich, Douglas Henrique >; Ho, Teresa > Subject: RE: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, pylint test is complaining about something in the k8sapp folder in the latest patchset 14. I have not uploaded any changes to this folder, infact the same job had passed yesterday in my last patchset 13. Can someone here please suggest where to look to resolve this issue? I didn't quite understand what the issue is. Zuul Build (opendev.org) Regards, Nidhi From: Zuul (Code Review) > Sent: Tuesday, August 30, 2022 5:13 PM To: Shivashankara Belur, Nidhi > Cc: Douglas Henrique Koerich >; Somerville, Jim >; Andre Kantek >; Davlet Panech >; Ho, Teresa >; Khalil, Ghada >; Scott Little >; Burla, Balendu > Subject: Change in ...app-sriov-fec-operator[master]: sriov-fec-operator system app integration Attention is currently required from: Jim Somerville, Ghada Khalil, Scott Little, Douglas Henrique Koerich, Nidhi Shivashankara Belur, Andre Kantek, Davlet Panech, Teresa Ho. Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing https://zuul.opendev.org/t/openstack/buildset/10fd7a2bb881467ca0a24a8464e0822f * openstack-tox-linters https://zuul.opendev.org/t/openstack/build/6b044bbf6fef4b17b011820fa393bdd4 : SUCCESS in 3m 06s * k8sapp-sriov-fec-operator-tox-py39 https://zuul.opendev.org/t/openstack/build/79e763ffc9be4d76b000abdd40a9a604 : SUCCESS in 6m 26s * k8sapp-sriov-fec-operator-tox-pylint https://zuul.opendev.org/t/openstack/build/a3568778b0ba40248feabf583b090dcf : FAILURE in 4m 22s * Patch set 14:Verified -1 View Change To view, visit change 845179. To unsubscribe, or for help writing mail filters, visit settings. Gerrit-Project: starlingx/app-sriov-fec-operator Gerrit-Branch: master Gerrit-Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Gerrit-Change-Number: 845179 Gerrit-PatchSet: 14 Gerrit-Owner: Nidhi Shivashankara Belur > Gerrit-Reviewer: Davlet Panech > Gerrit-Reviewer: Douglas Henrique Koerich > Gerrit-Reviewer: Ghada Khalil > Gerrit-Reviewer: Jim Somerville > Gerrit-Reviewer: Scott Little > Gerrit-Reviewer: Teresa Ho > Gerrit-Reviewer: Zuul Gerrit-CC: Andre Kantek > Gerrit-CC: Balendu Mouli Burla > Gerrit-Attention: Jim Somerville > Gerrit-Attention: Ghada Khalil > Gerrit-Attention: Scott Little > Gerrit-Attention: Douglas Henrique Koerich > Gerrit-Attention: Nidhi Shivashankara Belur > Gerrit-Attention: Andre Kantek > Gerrit-Attention: Davlet Panech > Gerrit-Attention: Teresa Ho > Gerrit-Comment-Date: Wed, 31 Aug 2022 00:12:41 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: