From Juanita.Balaraj at windriver.com Wed Jun 1 21:29:57 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 1 Jun 2022 21:29:57 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-June-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 ============ 01-June-22 * Discussed Cherry Picking to Stx 6.0 Cherrypicked 3 reviews to Stx 5.0; 6.0 * Ron demoed the tox -e picks Utility (tox -e picks) * Reminder: Numbering is out of sequence after "Conditional Updates" in a topic. Numbering should be done manually in these instances, for example: https://review.opendev.org/c/starlingx/docs/+/839552/1/doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst * Open Gerrit Reviews; https://review.opendev.org/q/%2509starlingx/docs+status:open - Action, the Doc team to ensure all stakeholders review and provide feedback and close open reviews for the Stx 7.0 Release. * 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 build.starlingx at gmail.com Thu Jun 2 04:25:20 2022 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jun 2022 00:25:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 3227 - Failure! Message-ID: <623135342.141.1654143921983.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 3227 Status: Failure Timestamp: 20220602T040121Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220602T035602Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-containers MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20220602T035602Z DOCKER_BUILD_ID: jenkins-master-containers-20220602T035602Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220602T035602Z/logs DOCKER_BUILD_TAG: master-containers-20220602T035602Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20220602T035602Z/logs LAYER: containers MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers From build.starlingx at gmail.com Thu Jun 2 04:25:23 2022 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jun 2022 00:25:23 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 299 - Failure! Message-ID: <325618284.144.1654143923905.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 299 Status: Failure Timestamp: 20220602T035602Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220602T035602Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Chandan.Kumar at commscope.com Thu Jun 2 17:12:17 2022 From: Chandan.Kumar at commscope.com (Kumar, Chandan) Date: Thu, 2 Jun 2022 17:12:17 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signing_procedure.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 22704 bytes Desc: signing_procedure.docx URL: From ildiko.vancsa at gmail.com Fri Jun 3 04:02:26 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 2 Jun 2022 21:02:26 -0700 Subject: [Starlingx-discuss] Grace Hopper Conference - Open Source Day participation Message-ID: <60750746-9EDC-4D2E-A143-8E91E81F699F@gmail.com> Hi, I?m reaching out to draw your attention to the Grace Hopper Conference - Open Source Day event. It is scheduled for Friday, September 16th, 2022 from 8am to 3pm U.S. Pacific Time in an online format. The organizers describe the event as "an all-day hack-a-thon at Grace Hopper Celebration in which participants of all levels contribute and learn about Open Source while working on projects designed to solve real-world problems?. The OpenStack project has been participating in the event for a couple of years now to help new contributors to learn about the project and the community, and to work on their first issue to start their contribution journey with the project. It could be a great opportunity for the StarlingX project as well to participate and with that raise awareness about the project and hopefully gain new contributors. The sign-up period for projects is currently open and will close on __June 20__. Requirements for participating projects: * Projects participating in OSD must provide triaged issues (non-documentation and "good first issue" labeled) * Have one or more (up to 3) project maintainers participate during the event to help attendees contribute to their project ** The OpenStack session usually has both core contributors from the project teams and additional experienced contributors to provide the best experience for students throughout the day. The overall number of experienced OpenStack mentors usually exceed the 3-person limit. Responsibilities include: * Introducing the project * Answering project related questions * Providing guidance to assigned mentors * Helping attendees contribute to the project More information about the event: https://ghc.anitab.org/programs-and-awards/open-source-day/ Please let me know if the StarlingX project would like to grab this opportunity and sign up. Also please let me know if you have any questions before committing to this effort. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From ildiko.vancsa at gmail.com Fri Jun 3 04:16:34 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 2 Jun 2022 21:16:34 -0700 Subject: [Starlingx-discuss] StarlingX metrics dashboard at the Open Infrastructure Summit Message-ID: <8BC59D9E-1374-47A4-859A-0B6823B3EE39@gmail.com> Hi, I would like to draw your attention to the Metrics Corner at the Open Infrastructure Summit next week. Bitergia, who is providing the metrics dashboard to StarlingX and other OpenInfra projects, is having a reserved space at the Summit next week where they will display their dashboard and will also hold sessions to guide people through the dashboards of our projects specifically. The StarlingX dashboard deep-dive session is scheduled for Wednesday, June 8, 3:30pm - 4:00pm CEST and will be held by Igor Zubiaurre. If you?re on site for the event I would like to encourage you to attend the StarlingX session. You can also drop by to the Metrics Corner at any time if you would like to get some more insights about the StarlingX dashboard or community metrics in general. Please let me know if you have any questions. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Cole.Walker at windriver.com Fri Jun 3 17:49:09 2022 From: Cole.Walker at windriver.com (Walker, Cole) Date: Fri, 3 Jun 2022 17:49:09 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Message-ID: Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa's past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Fri Jun 3 17:55:17 2022 From: Robert.Church at windriver.com (Church, Robert) Date: Fri, 3 Jun 2022 17:55:17 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Message-ID: <5B3F5074-34D9-42BA-9DE7-4503936D6B3C@windriver.com> +2 From: "Walker, Cole" Date: Friday, June 3, 2022 at 12:52 PM To: "'starlingx-discuss at lists.starlingx.io'" Cc: "Ho, Teresa" Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa?s past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ramaswamy.Subramanian at windriver.com Fri Jun 3 17:58:38 2022 From: Ramaswamy.Subramanian at windriver.com (Subramanian, Ramaswamy) Date: Fri, 3 Jun 2022 17:58:38 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo In-Reply-To: <5B3F5074-34D9-42BA-9DE7-4503936D6B3C@windriver.com> References: <5B3F5074-34D9-42BA-9DE7-4503936D6B3C@windriver.com> Message-ID: +2 From: Church, Robert Sent: Friday, June 3, 2022 1:55 PM To: Walker, Cole ; starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa Subject: Re: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo +2 From: "Walker, Cole" > Date: Friday, June 3, 2022 at 12:52 PM To: "'starlingx-discuss at lists.starlingx.io'" > Cc: "Ho, Teresa" > Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa?s past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hugo.Brito at encora.com Fri Jun 3 18:03:06 2022 From: Hugo.Brito at encora.com (Hugo Nicodemos Andrade de Brito) Date: Fri, 3 Jun 2022 18:03:06 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo In-Reply-To: References: Message-ID: +1 Get Outlook for iOS ________________________________ From: Walker, Cole Sent: Friday, June 3, 2022 2:49:09 PM To: starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo You don't often get email from cole.walker at windriver.com. Learn why this is important External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa?s past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jerry.Sun at windriver.com Fri Jun 3 19:15:03 2022 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Fri, 3 Jun 2022 19:15:03 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo In-Reply-To: References: <5B3F5074-34D9-42BA-9DE7-4503936D6B3C@windriver.com> Message-ID: +2 From: Subramanian, Ramaswamy Sent: June 3, 2022 1:59 PM To: Church, Robert ; Walker, Cole ; starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa Subject: Re: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo +2 From: Church, Robert > Sent: Friday, June 3, 2022 1:55 PM To: Walker, Cole >; starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa > Subject: Re: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo +2 From: "Walker, Cole" > Date: Friday, June 3, 2022 at 12:52 PM To: "'starlingx-discuss at lists.starlingx.io'" > Cc: "Ho, Teresa" > Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa?s past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Jun 6 07:21:02 2022 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Jun 2022 03:21:02 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1457 - Failure! Message-ID: <871575197.170.1654500066750.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1457 Status: Failure Timestamp: 20220606T045506Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220606T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220606T043000Z DOCKER_BUILD_ID: jenkins-master-20220606T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220606T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220606T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Jun 6 07:21:08 2022 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Jun 2022 03:21:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1310 - Failure! Message-ID: <1912471917.173.1654500069813.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1310 Status: Failure Timestamp: 20220606T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220606T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Greg.Waines at windriver.com Mon Jun 6 11:13:43 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 6 Jun 2022 11:13:43 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo In-Reply-To: References: Message-ID: +1 From: Walker, Cole Sent: Friday, June 3, 2022 1:49 PM To: starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa's past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Mon Jun 6 12:40:39 2022 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 6 Jun 2022 12:40:39 +0000 Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo In-Reply-To: References: Message-ID: +1 From: Waines, Greg Sent: Monday, June 6, 2022 7:14 AM To: Walker, Cole ; starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa Subject: Re: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo +1 From: Walker, Cole > Sent: Friday, June 3, 2022 1:49 PM To: starlingx-discuss at lists.starlingx.io Cc: Ho, Teresa > Subject: [Starlingx-discuss] Proposal to add Teresa Ho as a core review for ptp-notification-armada-app repo Hello core reviewers and STX community, I am looking for agreement to add Teresa Ho (teresa.ho at windriver.com) to the core reviewers for the ptp-notification-armada-app project. Teresa has helped with the development of PTP related features in other repositories and is planning to assist with some upcoming work for ptp-notification. Teresa's past PTP related reviews can be seen here: https://review.opendev.org/q/owner:teresa.ho%2540windriver.com+message:ptp Thanks for your time, Cole Walker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Wed Jun 8 14:35:16 2022 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Wed, 8 Jun 2022 14:35:16 +0000 Subject: [Starlingx-discuss] Docker image k8s-cni-sriov to be removed Message-ID: Good day, We are removing the docker image k8s-cni-sriov from the integ repo, as it is no longer referenced and superseded by ghcr.io/k8snetworkplumbingwg/sriov-cni . Please reply here if you have any objections. Thanks, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Jun 8 20:32:58 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 8 Jun 2022 20:32:58 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 08-June-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 ============ 08-June-22 - Open Gerrit Reviews for Stx 7.0 - Merged 5 reviews - Pending 9 Reviews to be reviewed and approved by Dev/Testing - Launchpad Bugs - Reviewed Doc bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs - 7 open - Reviewed Stx 7.0 Release Milestones - https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 - Stx 7.0 Release Notes to be initiated - Action - Juanita - Introduction Guide to be updated with new features for Stx 7.0 - Planning Guide - To be updated with any new requirements for Stx 7.0 - Container image deletion as per Davlet's email - replace docker image k8s-cni-sriov with ghcr.io/k8snetworkplumbingwg/sriov-cni - TAI clock updates - Juanita to discuss with Ghada regarding https://storyboard.openstack.org/#!/story/2010033 - 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 scott.little at windriver.com Thu Jun 9 15:32:55 2022 From: scott.little at windriver.com (Scott Little) Date: Thu, 9 Jun 2022 11:32:55 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1310 - Failure! In-Reply-To: <1912471917.173.1654500069813.JavaMail.javamailuser@localhost> References: <1912471917.173.1654500069813.JavaMail.javamailuser@localhost> Message-ID: The compiler layer build is now failing fairly consistently on the golang issue. https://bugs.launchpad.net/starlingx/+bug/1968583 We are working toward a fix in .... https://review.opendev.org/c/starlingx/compile/+/842811 Scott On 2022-06-06 3:21 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_master_master > Build #: 1310 > Status: Failure > Timestamp: 20220606T043000Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220606T043000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: true > > _______________________________________________ > 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 shaun at aknostic.com Sat Jun 11 11:47:28 2022 From: shaun at aknostic.com (Shaun Mccullagh) Date: Sat, 11 Jun 2022 13:47:28 +0200 Subject: [Starlingx-discuss] StarlingX on AWS Bare Metal Servers Message-ID: Hi, I?m interested in learning about StarlingX and I wondered if it was possible to install it on an AWS Bare Metal server? TIA Shaun From Greg.Waines at windriver.com Mon Jun 13 11:21:15 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 13 Jun 2022 11:21:15 +0000 Subject: [Starlingx-discuss] StarlingX on AWS Bare Metal Servers In-Reply-To: References: Message-ID: We have never tried installing on AWS Bare Metal Server. We have deployed on Equinix bare metal servers (formerly packet.com) ... https://wiki.openstack.org/wiki/StarlingX/Packet_SIG ( this was quite some time ago ) I am not that familiar with AWS Bare Metal Server capabilities, but from experience in deploying StarlingX on packet.com/equinix, some key requirements on 'AWS Bare Metal Server' in order to be able to deploy StarlingX would be: - ability to configure L2 networks between AWS Bare Metal Servers, - ability to do a full ISO install of StarlingX (kernel, user-space, starlingx services) on initial AWS Bare Metal Server e.g. a PXE Boot install I would be interested in knowing if L2 networks are supported on AWS Bare Metal Servers ... let me know. Greg. -----Original Message----- From: Shaun Mccullagh Sent: Saturday, June 11, 2022 7:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX on AWS Bare Metal Servers [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I?m interested in learning about StarlingX and I wondered if it was possible to install it on an AWS Bare Metal server? TIA Shaun _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Wed Jun 15 14:48:47 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 15 Jun 2022 07:48:47 -0700 Subject: [Starlingx-discuss] Grace Hopper Conference - Open Source Day participation In-Reply-To: <60750746-9EDC-4D2E-A143-8E91E81F699F@gmail.com> References: <60750746-9EDC-4D2E-A143-8E91E81F699F@gmail.com> Message-ID: <2B45281C-D1E6-43AC-926A-1CA6F81C85A9@gmail.com> Hi StarlingX Community, It is a friendly reminder that the __project signup deadline for the Grace Hopper Open Source Day is June 20th__. You can find details about the event in my previous email. Please let me know if you?re interested in participating and help running a StarlingX session at the event or if you have any questions before deciding. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jun 2, 2022, at 21:02, Ildiko Vancsa wrote: > > Hi, > > I?m reaching out to draw your attention to the Grace Hopper Conference - Open Source Day event. It is scheduled for Friday, September 16th, 2022 from 8am to 3pm U.S. Pacific Time in an online format. > > The organizers describe the event as "an all-day hack-a-thon at Grace Hopper Celebration in which participants of all levels contribute and learn about Open Source while working on projects designed to solve real-world problems?. > > The OpenStack project has been participating in the event for a couple of years now to help new contributors to learn about the project and the community, and to work on their first issue to start their contribution journey with the project. > > It could be a great opportunity for the StarlingX project as well to participate and with that raise awareness about the project and hopefully gain new contributors. > > The sign-up period for projects is currently open and will close on __June 20__. > > Requirements for participating projects: > * Projects participating in OSD must provide triaged issues (non-documentation and "good first issue" labeled) > * Have one or more (up to 3) project maintainers participate during the event to help attendees contribute to their project > ** The OpenStack session usually has both core contributors from the project teams and additional experienced contributors to provide the best experience for students throughout the day. The overall number of experienced OpenStack mentors usually exceed the 3-person limit. > > Responsibilities include: > * Introducing the project > * Answering project related questions > * Providing guidance to assigned mentors > * Helping attendees contribute to the project > > More information about the event: https://ghc.anitab.org/programs-and-awards/open-source-day/ > > Please let me know if the StarlingX project would like to grab this opportunity and sign up. Also please let me know if you have any questions before committing to this effort. > > Best Regards, > Ildik? > > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > From scott.little at windriver.com Wed Jun 15 15:00:16 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 15 Jun 2022 11:00:16 -0400 Subject: [Starlingx-discuss] Build Failure Message-ID: <8e7729f8-5633-027a-6ed2-dc757d0b0a5b@windriver.com> build-iso is currently failing with error: ????? stx-metrics-server-helm-fluxcd not found I've created a launchpad to track the issue. https://bugs.launchpad.net/starlingx/+bug/1978837 Probable cause: https://review.opendev.org/c/starlingx/metrics-server-armada-app/+/845608 Scott From Juanita.Balaraj at windriver.com Thu Jun 16 03:52:52 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 16 Jun 2022 03:52:52 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 15-June-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 ============ 15-June-22 * To check with Gustavo regarding reviews; https://review.opendev.org/c/starlingx/docs/+/840521; https://review.opendev.org/c/starlingx/docs/+/845822 - AR - Juanita * Scott to cut the Stx 7.0 Doc Branch in July 2022 post the Stx 7.0 Release. * Ram S to confirm if https://review.opendev.org/c/starlingx/docs/+/845379 will be delivered in Stx 7.0 - AR Juanita * Open Gerrit Reviews for Stx 7.0 - Merged 2 reviews - 18 Pending Reviews; to be reviewed and approved by Dev/Testing * Launchpad Bugs - Reviewed Doc bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs - 7 open * Stx 7.0 Release Notes to be initiated - Action - Juanita * Introduction Guide to be updated with new features for Stx 7.0 * Planning Guide - To be updated with any new requirements for Stx 7.0 * Delete container image as per Davlet's email - replace docker image k8s-cni-sriov with ghcr.io/k8snetworkplumbingwg/sriov-cni - 1 topic - Created Gerrit review https://review.opendev.org/c/starlingx/docs/+/846090 * TAI clock updates - Juanita to discuss with Ghada regarding https://storyboard.openstack.org/#!/story/2010033 * 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 Ghada.Khalil at windriver.com Thu Jun 16 13:02:59 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Jun 2022 13:02:59 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jun 15 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call June 15 2022 Standing Topics - Build - CentOS builds - Rough week for CentOS builds - golang issue changed from intermittent failure to persistent failure. This was addressed. - Some upstream python package (packge-name: requires) changes also affected the builds. - Managed to have one green build on June 14. But now investigating a failure today related to a missing fluxCD package. - Also working to address some infrastructure mirroring issues. - Debian builds - Intermittent failures seen this week; mostly related to packaging issues - Successful build on June 13. But one failure on June 14. - Most recent build is ongoing. - Need to chop up build logs into smaller bits in order to make it easier to find build errors ... current log crashes/hangs browser - Sanity - No update since last week. - Intel sanity was halted as of May 27. WR sanity not started; plan to start working on env setup in 2wks (June 29) - Reviewed staus in the release meeting and agreed that lack of regular sanity will block the stx.7.0 release declaration planned for July 25. Release dates may need to be re-forecasted. - Last Sanity Report on mailing list - May 27 - Status: Red - [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220527T041457Z ( http://lists.starlingx.io/pipermail/starlingx-discuss/2022-May/013061.html ) - https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready // Status ? - https://bugs.launchpad.net/starlingx/+bug/1975921 - Provision failed: IndexError: Given index 0 is out of the range 0--1 // Status ? - Action: Greg to ping douglas about status and forecast of this - Gerrit Reviews in Need of Attention - Many doc reviews are pending, but making progress - https://review.opendev.org/q/project:starlingx%252Fdocs+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 - Summit Update from Steve Geary - Participation was smaller than usual (as expected due to COVID & global factors) - ~900 people attended. - There was still lots of activity and community feeling. - Lots of participation from commercial distros and CERN - StarlingX talks were well attended. Participants were engaged. - Babak presented the StarlingX 101 presentation and was asked to present a second one. - StarlingX booth traffic was also very good with a good level of dialog. - Grace Hopper Open Source Day: https://ghc.anitab.org/programs-and-awards/open-source-day/ -- Ildiko - Project sign-up deadline is June 20. Event on Sept 16. - Anyone from the community interested in participating? - Ildiko will send another reminder to the stx mailing list ARs from Previous Meetings - None Open Requests for Help - Incorrect public key for signed starlingX 5.0 iso: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013072.html - Action: Greg to reply. - StarlingX on AWS Bare Metal Servers: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013087.html - Greg provided a response. - Conclusion is that AWS Bare metal servers doesn't support setting up L2 networks, so it can't run StarlingX. From Ghada.Khalil at windriver.com Thu Jun 16 13:16:34 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Jun 2022 13:16:34 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jun 15/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Sanity - Intel sanity was halted on May 27. The last sanity was red. - The WR team has not been able to get a working sanity env since then. Team stretched due to other priorities. - No clear view of the status of the stx loads at this time. - This blocks stx.7.0 milestone declaration - The current plan to restart work on enabling sanity in 2wks by June 29. Then can start building a plan at that time. stx.7.0 -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 - Release Updates - Debian Update - Debian Builds on CENGN - Debian support for stx.7.0 is considered complete. Support is only for AIO-SX. Other config support will continue in stx.8.0. - Debian ISO Builds on CENGN are building regularly. No container image builds for stx.7.0 as previously agreed to. - Feature Code & Test Update - Feature status updated in the planning spreadsheet. - 26 features are complete. - 12 features are still in progress. Forecast dates updated. - Action: Release team to re-forecast stx.7.0 milestones to align with remaining activities From ascaccia96 at hotmail.com Mon Jun 27 12:57:16 2022 From: ascaccia96 at hotmail.com (Amato Scaccia) Date: Mon, 27 Jun 2022 12:57:16 +0000 Subject: [Starlingx-discuss] Error in adding a subcloud after unlocking the first controller Message-ID: Dear all, My team are trying to install StarlingX 6.0 on a distributed cloud system: our actual configuration is one central cloud (Bare Metal AIO Duplex) and a subcloud (Bare Metal AIO Duplex). To configure it we follow this doc and everything works fine: ( https://docs.starlingx.io/deploy_install_guides/r6_release/distributed_cloud/index-install-r6-distcloud-46f4880ec78b.html) Now we are trying to add another subcloud in a different location (following the same steps needed for the previous subcloud) but after this step (Unlock of controller-0: https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/aio_duplex_install_kubernetes.html#unlock-controller-0) we receive the following errors: * sudo: ldap_sasl_bind_s(): Can't contact LDAP server (if run sudo command) * Openstack Admin credentials can only be loaded from the active controller ($if runsource /etc/platform/opensrc) * The connection to the server 192.168.206.1:6443 was refused - did you specify the right host or port? (kubectl command) Also there is this error message in /var/log/sysinv.log: sysinv 2022-06-27 12:27:28.254 9676 ERROR sysinv.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 30 seconds.: error: [Errno 111] ECONNREFUSED Let me know if you need more info on the setup/logs. Thanks for your help! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Jun 27 23:45:27 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Jun 2022 16:45:27 -0700 Subject: [Starlingx-discuss] Edge infrastructure orchestration discussion with the edge WG Message-ID: <4EA744BF-EAD8-4CCE-BBBA-128660FB9CE4@gmail.com> Hi StarlingX community, I?m reaching out to you on behalf of the OpenInfra Edge Computing Group. On today?s call we touched on topics about infrastructure orchestration and its challenges in large-scale, geographically distributed edge environments. The group is planning to explore this area further and participants on today?s call suggested to look into solutions as well, such as the StarlingX project. Would anyone from the community be available to join the OpenInfra Edge Computing Group weekly call on July 18 at 6am US Pacific time, to participate in the conversation and share details about StarlingX? You can find further information about the group and our calls on this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group Thanks and Best Regards, Ildik? From lists at optimcloud.com Tue Jun 28 09:01:02 2022 From: lists at optimcloud.com (Embedded Devel) Date: Tue, 28 Jun 2022 09:01:02 +0000 Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos Message-ID: <1656406485704.742713062.1917902131@optimcloud.com> can i ask if there is a plan to remove docker moving forward in favor of cri-o? as we know k8s 1.24.+ drops docker support unless using the docker-shim preferably we have already tested and run k8s / openstack-helm via crio so we know it works curious how this applies to starlingx V7 and higher? further to that are there plans aside from CentOS to move the rpm base to say Alma or CoreOS or Silverblue even. (both are ostree based) as Ive seen the debian build deploying with ostree onboard? or is the plan to drop rpm based distros long term and just run with debian ? We have deployed magmacore on stx 6.0 and are in the process of upgrading the infrastructure. My curiosities exists as whats the starling X impact going to be long term, as I would like to put all my eggs in this basket. -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From scott.little at windriver.com Wed Jun 29 14:42:04 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 29 Jun 2022 10:42:04 -0400 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: Message-ID: 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 kennelson11 at gmail.com Wed Jun 29 17:17:29 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 29 Jun 2022 12:17:29 -0500 Subject: [Starlingx-discuss] October PTG 2022 Team Signup Message-ID: Hi Everyone, At the Berlin Summit, we announced the next PTG will be held from Monday, October 17th to Thursday, October 20th, 2022 in Columbus, OH! To signup your team, you must complete the survey[1] by August 12th at 7:00 UTC. We NEED accurate contact information for the moderator of your team?s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators mid to late August. Registration will open soon! A discounted room block at the PTG venue will be available. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst -------------- next part -------------- An HTML attachment was scrubbed... URL: From John.Kung at windriver.com Wed Jun 29 19:51:56 2022 From: John.Kung at windriver.com (Kung, John) Date: Wed, 29 Jun 2022 19:51:56 +0000 Subject: [Starlingx-discuss] Error in adding a subcloud after unlocking the first controller Message-ID: As this appears to be the first host-unlock attempted on the subcloud; it appears the bootstrap configuration may not have completed yet on the affected subcloud. There are possibly 'Error' logs under /var/log/puppet. The following would scan whether a configuration Error may have occurred. The context around that Error log could provide indications as to which part of the config may encountered an issue. On the affected subcloud itself: cd /var/log/puppet sudo grep -rs Error * I would also recommend comparing the subcloud's ansible-playbook bootstrap parameters and logs (ansible.log on the subcloud/remote site; or on the central cloud system controller under /var/log/dcmanager/ansible) between the passing and failing subcloud. If the bootstrap parameters require adjustment, it should be possible to update and 'replay' by rerunning the bootstrap playbook. The following has some debug tips: https://docs.starlingx.io/developer_resources/debug_issues.html . We would recommend a 'collect' of logs from the subcloud and central controller, and to attach the logs and info for a LP: https://bugs.launchpad.net/starlingx/+bugs Please advise if further comments or info. Thanks, John ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Jun 2022 12:57:16 +0000 From: Amato Scaccia > To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Error in adding a subcloud after unlocking the first controller Message-ID: > Content-Type: text/plain; charset="iso-8859-1" Dear all, My team are trying to install StarlingX 6.0 on a distributed cloud system: our actual configuration is one central cloud (Bare Metal AIO Duplex) and a subcloud (Bare Metal AIO Duplex). To configure it we follow this doc and everything works fine: ( https://docs.starlingx.io/deploy_install_guides/r6_release/distributed_cloud/index-install-r6-distcloud-46f4880ec78b.html) Now we are trying to add another subcloud in a different location (following the same steps needed for the previous subcloud) but after this step (Unlock of controller-0: https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/aio_duplex_install_kubernetes.html#unlock-controller-0) we receive the following errors: * sudo: ldap_sasl_bind_s(): Can't contact LDAP server (if run sudo command) * Openstack Admin credentials can only be loaded from the active controller ($if runsource /etc/platform/opensrc) * The connection to the server 192.168.206.1:6443 was refused - did you specify the right host or port? (kubectl command) Also there is this error message in /var/log/sysinv.log: sysinv 2022-06-27 12:27:28.254 9676 ERROR sysinv.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 30 seconds.: error: [Errno 111] ECONNREFUSED Let me know if you need more info on the setup/logs. Thanks for your help! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jun 30 03:24:15 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 29 Jun 2022 20:24:15 -0700 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 Message-ID: <9B96875E-3BB9-436C-8031-4C36582ADFBE@gmail.com> Hi StarlingX TSC and Community, I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. The spec[2] also lists the following work items: * Update the application framework to use the Helm/Source controllers * Update all applications to use the Helm/Source controllers for deploying/updating applications * Provide upgrade support to update all applications to the Helm Controller and remove the Armada pod Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? Thanks and Best Regards, Ildik? [1] https://etherpad.opendev.org/p/stx-releases [2] https://review.opendev.org/c/starlingx/specs/+/829595 ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Greg.Waines at windriver.com Thu Jun 30 11:42:35 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 30 Jun 2022 11:42:35 +0000 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: <9B96875E-3BB9-436C-8031-4C36582ADFBE@gmail.com> References: <9B96875E-3BB9-436C-8031-4C36582ADFBE@gmail.com> Message-ID: I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported this originally, but stopped supporting stx-openstack in StarlingX a year ago or so, - A team from Wind River (Douglas Periera) picked up support for stx-openstack in StarlingX a year and a half ago, but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. I believe Douglas only has a team of ~4 working on stx-openstack. They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. I believe the majority of users of StarlingX are not using stx-openstack. I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. Greg. p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, June 29, 2022 11:24 PM To: Waines, Greg ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML Subject: Challenges with the support to deploy stx-openstack in 7.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX TSC and Community, I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. The spec[2] also lists the following work items: * Update the application framework to use the Helm/Source controllers * Update all applications to use the Helm/Source controllers for deploying/updating applications * Provide upgrade support to update all applications to the Helm Controller and remove the Armada pod Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? Thanks and Best Regards, Ildik? [1] https://etherpad.opendev.org/p/stx-releases [2] https://review.opendev.org/c/starlingx/specs/+/829595 ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From outbackdingo at gmail.com Thu Jun 30 12:10:35 2022 From: outbackdingo at gmail.com (Outback Dingo) Date: Thu, 30 Jun 2022 19:10:35 +0700 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: References: <9B96875E-3BB9-436C-8031-4C36582ADFBE@gmail.com> Message-ID: On Thu, Jun 30, 2022 at 6:50 PM Waines, Greg wrote: > > I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. > Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. > It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. > > I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. > > Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. > - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported this originally, but stopped supporting stx-openstack in StarlingX a year ago or so, > - A team from Wind River (Douglas Periera) picked up support for stx-openstack in StarlingX a year and a half ago, > but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. > I believe Douglas only has a team of ~4 working on stx-openstack. > They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. > > > Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. > I believe the majority of users of StarlingX are not using stx-openstack. > I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. well, sh!t3 ... you might want to read my previous email from a few days ago, "subject: docker vs cri-o / centos vs alma / silverblue / coreos." As I for one, will no longer be able to deploy starlingx beyond 6.x if openstack is not onboard we in the process of deploying magmacore for a commercial telco, like other commercial telcos, your now basically shooting yourself in the foot, as if this is the case we end up never being able to upgrade the platforms we/I have already deployed for many. I would have to say, now i'm upset. I have always been a big advocate and where I can / am able to deploy it. It seems now that you might have boxed us in and are leaving us in the dust. And if that's the case then you might want to focus on at least making it work in VMs, since now we are going to have to utilize some other orchestrated virtualization product. Sorry, but I honestly feel it's complete and total BS to do this to your user base. And yes I have a super strong opinion about it being dropped. It really needs to stay or your going to literally alienate a good part of your current user base, and its further adoption in the telecom arena. > > > Greg. > > p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. > > > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, June 29, 2022 11:24 PM > To: Waines, Greg ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML > Subject: Challenges with the support to deploy stx-openstack in 7.0 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX TSC and Community, > > I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. > > Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. > > The spec[2] also lists the following work items: > * Update the application framework to use the Helm/Source controllers > * Update all applications to use the Helm/Source controllers for deploying/updating applications > * Provide upgrade support to update all applications to the Helm Controller and remove the Armada pod > > Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? > > While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? > > If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? > > Thanks and Best Regards, > Ildik? > > [1] https://etherpad.opendev.org/p/stx-releases > [2] https://review.opendev.org/c/starlingx/specs/+/829595 > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From lists at optimcloud.com Thu Jun 30 12:16:40 2022 From: lists at optimcloud.com (Embedded Devel) Date: Thu, 30 Jun 2022 12:16:40 +0000 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: References: Message-ID: <1656591176286.175119764.1933541420@optimcloud.com> On Thursday 30 June 2022 18:42:35 PM (+07:00), Waines, Greg wrote: > I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. > Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. > It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. Why is it believed ??? We run k8s 1.21.3 on STX 6.x and openstack-helm deploys just fine, where are you finding this information. controller-0:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE armada armada-api-dc8b94475-28hsg 2/2 Running 2 2d3h cert-manager cm-cert-manager-74cc8d687-rfhwz 1/1 Running 1 2d2h ----snip----------------- kube-system rbd-provisioner-759dfb8b6b-sjq5h 1/1 Running 0 2d2h openstack cinder-api-79b6497c55-9bzqs 1/1 Running 0 2d openstack cinder-backup-d7b4c8946-gnx49 1/1 Running 0 2d openstack cinder-scheduler-7fd896457c-82j7c 1/1 Running 0 2d openstack cinder-volume-57cfc5fcc-8ft7m 1/1 Running 0 2d openstack cinder-volume-usage-audit-27609840-v46qc 0/1 Completed 0 15m openstack cinder-volume-usage-audit-27609845-5dh89 0/1 Completed 0 10m openstack cinder-volume-usage-audit-27609850-qs4bb 0/1 Completed 0 5m29s openstack cinder-volume-usage-audit-27609855-6rglw 1/1 Running 0 29s openstack fm-db-init-7mnt2 0/1 Completed 0 2d openstack fm-db-sync-km7dp 0/1 Completed 0 2d openstack fm-ks-endpoints-htsfz 0/3 Completed 0 2d openstack fm-ks-service-9sqk2 0/1 Completed 0 2d openstack fm-ks-user-wtr27 0/1 Completed 0 2d openstack fm-rest-api-675d7867f6-bpv6w 1/1 Running 0 2d openstack glance-api-699b77f6db-xssfj 1/1 Running 0 2d openstack heat-api-cd74f79c6-kcdtm 1/1 Running 0 2d openstack heat-bootstrap-nhvzl 0/1 Completed 0 2d openstack heat-cfn-5c69ff4548-z7dgw 1/1 Running 0 2d openstack heat-db-init-88lkz 0/1 Completed 0 2d openstack heat-db-sync-df2dp 0/1 Completed 0 2d openstack heat-domain-ks-user-rv6c6 0/1 Completed 0 2d openstack heat-engine-6745946fd4-p6lr4 1/1 Running 0 2d openstack heat-engine-cleaner-27609840-skjm4 0/1 Completed 0 15m openstack heat-engine-cleaner-27609845-xdkj9 0/1 Completed 0 10m openstack heat-engine-cleaner-27609850-f5crb 0/1 Completed 0 5m29s openstack heat-engine-cleaner-27609855-4m6kr 1/1 Running 0 29s openstack heat-ks-endpoints-dfng4 0/6 Completed 0 2d openstack heat-ks-service-7czzq 0/2 Completed 0 2d openstack heat-ks-user-pk7p7 0/1 Completed 0 2d openstack heat-purge-deleted-27607700-mfbbz 0/1 Completed 0 35h openstack heat-purge-deleted-27609140-9sdlw 0/1 Completed 0 11h openstack heat-rabbit-init-74xhg 0/1 Completed 0 2d openstack heat-trustee-ks-user-45xd4 0/1 Completed 0 2d openstack heat-trusts-nsq8j 0/1 Completed 0 2d openstack horizon-5c4c9b79f4-s6v6b 1/1 Running 0 2d openstack horizon-db-init-bs6b5 0/1 Completed 0 2d openstack horizon-db-sync-59gbt 0/1 Completed 0 2d openstack ingress-7559b8d644-2qx6v 1/1 Running 0 2d openstack ingress-error-pages-7975fd4db5-jqn4q 1/1 Running 0 2d openstack keystone-api-84bb867c4c-2n2tj 1/1 Running 0 2d openstack keystone-fernet-rotate-27608400-vsscl 0/1 Completed 0 24h openstack keystone-fernet-rotate-27609120-k2zsv 0/1 Completed 0 12h openstack keystone-fernet-rotate-27609840-2fmmv 0/1 Completed 0 15m openstack libvirt-libvirt-default-ggp5l 1/1 Running 0 2d openstack mariadb-ingress-847cdb5dfb-7q59v 1/1 Running 0 2d openstack mariadb-ingress-error-pages-857f748f89-lvqqc 1/1 Running 0 2d openstack mariadb-server-0 1/1 Running 0 2d openstack neutron-dhcp-agent-controller-0-937646f6-p5nfg 1/1 Running 0 2d openstack neutron-l3-agent-controller-0-937646f6-w5zxp 1/1 Running 0 2d openstack neutron-metadata-agent-controller-0-937646f6-f2vqp 1/1 Running 0 2d openstack neutron-netns-cleanup-cron-default-jx9zr 1/1 Running 1 2d openstack neutron-ovs-agent-controller-0-937646f6-8rzpz 1/1 Running 0 2d openstack neutron-server-764ff69bbd-wqnh6 1/1 Running 0 2d openstack nova-api-metadata-75cf57b549-t97d8 1/1 Running 2 2d openstack nova-api-osapi-5f9d8b8d5d-j848v 1/1 Running 0 2d openstack nova-api-proxy-7c86f9dc4d-vjp66 1/1 Running 1 2d openstack nova-bootstrap-5t9jg 0/1 Completed 0 2d openstack nova-cell-setup-7dr9v 0/1 Completed 0 2d openstack nova-compute-controller-0-937646f6-g6748 2/2 Running 0 2d openstack nova-conductor-c9757f646-bzr5s 1/1 Running 0 2d openstack nova-db-sync-g5w7s 0/1 Completed 0 2d openstack nova-novncproxy-7f58c4dcdb-zxrql 1/1 Running 0 2d openstack nova-scheduler-7b98545d78-zpxvv 1/1 Running 0 2d openstack nova-service-cleaner-27609720-z8nh6 0/1 Completed 0 135m openstack nova-service-cleaner-27609780-vbj58 0/1 Completed 0 75m openstack nova-service-cleaner-27609840-7mb7r 0/1 Completed 0 15m openstack openvswitch-db-ltwlf 1/1 Running 1 2d openstack openvswitch-vswitchd-92tn6 1/1 Running 0 2d openstack osh-openstack-memcached-memcached-54cc965966-96bp9 1/1 Running 0 2d openstack osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 2d openstack pci-irq-affinity-agent-fnn94 1/1 Running 0 2d openstack placement-api-8759c476f-c4gfc 1/1 Running 0 2d controller-0:~$ kubectl version Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"archive", BuildDate:"2022-01-19T17:43:43Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T20:59:07Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} > I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. > > Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. > - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported this originally, but stopped supporting stx-openstack in StarlingX a year ago or so, > - A team from Wind River (Douglas Periera) picked up support for stx-openstack in StarlingX a year and a half ago, > but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. > I believe Douglas only has a team of ~4 working on stx-openstack. > They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. > > > Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. > I believe the majority of users of StarlingX are not using stx-openstack. > I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. > > > Greg. > > p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. > > > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, June 29, 2022 11:24 PM > To: Waines, Greg ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML > Subject: Challenges with the support to deploy stx-openstack in 7.0 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX TSC and Community, > > I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. > > Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. > > The spec[2] also lists the following work items: > * Update the application framework to use the Helm/Source controllers > * Update all applications to use the Helm/Source controllers for deploying/updating applications > * Provide upgrade support to update all applications to the Helm Controller and remove the Armada pod > > Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? > > While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? > > If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? > > Thanks and Best Regards, > Ildik? > > [1] https://etherpad.opendev.org/p/stx-releases > [2] https://review.opendev.org/c/starlingx/specs/+/829595 > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From Greg.Waines at windriver.com Thu Jun 30 12:24:50 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 30 Jun 2022 12:24:50 +0000 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: References: <9B96875E-3BB9-436C-8031-4C36582ADFBE@gmail.com> Message-ID: Hey thanks for your feedback ? . The decision on what to do wrt STX 7 is not final. I was just voicing my opinion. We will discuss more in upcoming STX 7 release meetings. Greg. -----Original Message----- From: Outback Dingo Sent: Thursday, June 30, 2022 8:11 AM To: Waines, Greg Cc: Ildiko Vancsa ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML Subject: Re: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 [Please note: This e-mail is from an EXTERNAL e-mail address] On Thu, Jun 30, 2022 at 6:50 PM Waines, Greg wrote: > > I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. > Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. > It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. > > I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. > > Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. > - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported this originally, but stopped supporting stx-openstack in StarlingX a year ago or so, > - A team from Wind River (Douglas Periera) picked up support for stx-openstack in StarlingX a year and a half ago, > but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. > I believe Douglas only has a team of ~4 working on stx-openstack. > They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. > > > Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. > I believe the majority of users of StarlingX are not using stx-openstack. > I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. well, sh!t3 ... you might want to read my previous email from a few days ago, "subject: docker vs cri-o / centos vs alma / silverblue / coreos." As I for one, will no longer be able to deploy starlingx beyond 6.x if openstack is not onboard we in the process of deploying magmacore for a commercial telco, like other commercial telcos, your now basically shooting yourself in the foot, as if this is the case we end up never being able to upgrade the platforms we/I have already deployed for many. I would have to say, now i'm upset. I have always been a big advocate and where I can / am able to deploy it. It seems now that you might have boxed us in and are leaving us in the dust. And if that's the case then you might want to focus on at least making it work in VMs, since now we are going to have to utilize some other orchestrated virtualization product. Sorry, but I honestly feel it's complete and total BS to do this to your user base. And yes I have a super strong opinion about it being dropped. It really needs to stay or your going to literally alienate a good part of your current user base, and its further adoption in the telecom arena. > > > Greg. > > p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. > > > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, June 29, 2022 11:24 PM > To: Waines, Greg ; Qi, Mingyuan > ; Shuquan Huang ; > Subramanian, Ramaswamy ; > StarlingX ML > Subject: Challenges with the support to deploy stx-openstack in 7.0 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX TSC and Community, > > I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. > > Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. > > The spec[2] also lists the following work items: > * Update the application framework to use the Helm/Source controllers > * Update all applications to use the Helm/Source controllers for > deploying/updating applications > * Provide upgrade support to update all applications to the Helm > Controller and remove the Armada pod > > Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? > > While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? > > If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? > > Thanks and Best Regards, > Ildik? > > [1] https://etherpad.opendev.org/p/stx-releases > [2] https://review.opendev.org/c/starlingx/specs/+/829595 > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Thu Jun 30 12:27:35 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 30 Jun 2022 12:27:35 +0000 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: <1656591176286.175119764.1933541420@optimcloud.com> References: <1656591176286.175119764.1933541420@optimcloud.com> Message-ID: I said that "It is believed that stx-openstack in STX7 w/k8s v1.21" ... simply because in STX7, we have not had a clean sanity run from the StarlingX Test subproject for over a month. Greg. -----Original Message----- From: Embedded Devel Sent: Thursday, June 30, 2022 8:17 AM To: Waines, Greg ; Ildiko Vancsa ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML Subject: Re: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 [Please note: This e-mail is from an EXTERNAL e-mail address] On Thursday 30 June 2022 18:42:35 PM (+07:00), Waines, Greg wrote: > I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. > Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. > It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. Why is it believed ??? We run k8s 1.21.3 on STX 6.x and openstack-helm deploys just fine, where are you finding this information. controller-0:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE armada armada-api-dc8b94475-28hsg 2/2 Running 2 2d3h cert-manager cm-cert-manager-74cc8d687-rfhwz 1/1 Running 1 2d2h ----snip----------------- kube-system rbd-provisioner-759dfb8b6b-sjq5h 1/1 Running 0 2d2h openstack cinder-api-79b6497c55-9bzqs 1/1 Running 0 2d openstack cinder-backup-d7b4c8946-gnx49 1/1 Running 0 2d openstack cinder-scheduler-7fd896457c-82j7c 1/1 Running 0 2d openstack cinder-volume-57cfc5fcc-8ft7m 1/1 Running 0 2d openstack cinder-volume-usage-audit-27609840-v46qc 0/1 Completed 0 15m openstack cinder-volume-usage-audit-27609845-5dh89 0/1 Completed 0 10m openstack cinder-volume-usage-audit-27609850-qs4bb 0/1 Completed 0 5m29s openstack cinder-volume-usage-audit-27609855-6rglw 1/1 Running 0 29s openstack fm-db-init-7mnt2 0/1 Completed 0 2d openstack fm-db-sync-km7dp 0/1 Completed 0 2d openstack fm-ks-endpoints-htsfz 0/3 Completed 0 2d openstack fm-ks-service-9sqk2 0/1 Completed 0 2d openstack fm-ks-user-wtr27 0/1 Completed 0 2d openstack fm-rest-api-675d7867f6-bpv6w 1/1 Running 0 2d openstack glance-api-699b77f6db-xssfj 1/1 Running 0 2d openstack heat-api-cd74f79c6-kcdtm 1/1 Running 0 2d openstack heat-bootstrap-nhvzl 0/1 Completed 0 2d openstack heat-cfn-5c69ff4548-z7dgw 1/1 Running 0 2d openstack heat-db-init-88lkz 0/1 Completed 0 2d openstack heat-db-sync-df2dp 0/1 Completed 0 2d openstack heat-domain-ks-user-rv6c6 0/1 Completed 0 2d openstack heat-engine-6745946fd4-p6lr4 1/1 Running 0 2d openstack heat-engine-cleaner-27609840-skjm4 0/1 Completed 0 15m openstack heat-engine-cleaner-27609845-xdkj9 0/1 Completed 0 10m openstack heat-engine-cleaner-27609850-f5crb 0/1 Completed 0 5m29s openstack heat-engine-cleaner-27609855-4m6kr 1/1 Running 0 29s openstack heat-ks-endpoints-dfng4 0/6 Completed 0 2d openstack heat-ks-service-7czzq 0/2 Completed 0 2d openstack heat-ks-user-pk7p7 0/1 Completed 0 2d openstack heat-purge-deleted-27607700-mfbbz 0/1 Completed 0 35h openstack heat-purge-deleted-27609140-9sdlw 0/1 Completed 0 11h openstack heat-rabbit-init-74xhg 0/1 Completed 0 2d openstack heat-trustee-ks-user-45xd4 0/1 Completed 0 2d openstack heat-trusts-nsq8j 0/1 Completed 0 2d openstack horizon-5c4c9b79f4-s6v6b 1/1 Running 0 2d openstack horizon-db-init-bs6b5 0/1 Completed 0 2d openstack horizon-db-sync-59gbt 0/1 Completed 0 2d openstack ingress-7559b8d644-2qx6v 1/1 Running 0 2d openstack ingress-error-pages-7975fd4db5-jqn4q 1/1 Running 0 2d openstack keystone-api-84bb867c4c-2n2tj 1/1 Running 0 2d openstack keystone-fernet-rotate-27608400-vsscl 0/1 Completed 0 24h openstack keystone-fernet-rotate-27609120-k2zsv 0/1 Completed 0 12h openstack keystone-fernet-rotate-27609840-2fmmv 0/1 Completed 0 15m openstack libvirt-libvirt-default-ggp5l 1/1 Running 0 2d openstack mariadb-ingress-847cdb5dfb-7q59v 1/1 Running 0 2d openstack mariadb-ingress-error-pages-857f748f89-lvqqc 1/1 Running 0 2d openstack mariadb-server-0 1/1 Running 0 2d openstack neutron-dhcp-agent-controller-0-937646f6-p5nfg 1/1 Running 0 2d openstack neutron-l3-agent-controller-0-937646f6-w5zxp 1/1 Running 0 2d openstack neutron-metadata-agent-controller-0-937646f6-f2vqp 1/1 Running 0 2d openstack neutron-netns-cleanup-cron-default-jx9zr 1/1 Running 1 2d openstack neutron-ovs-agent-controller-0-937646f6-8rzpz 1/1 Running 0 2d openstack neutron-server-764ff69bbd-wqnh6 1/1 Running 0 2d openstack nova-api-metadata-75cf57b549-t97d8 1/1 Running 2 2d openstack nova-api-osapi-5f9d8b8d5d-j848v 1/1 Running 0 2d openstack nova-api-proxy-7c86f9dc4d-vjp66 1/1 Running 1 2d openstack nova-bootstrap-5t9jg 0/1 Completed 0 2d openstack nova-cell-setup-7dr9v 0/1 Completed 0 2d openstack nova-compute-controller-0-937646f6-g6748 2/2 Running 0 2d openstack nova-conductor-c9757f646-bzr5s 1/1 Running 0 2d openstack nova-db-sync-g5w7s 0/1 Completed 0 2d openstack nova-novncproxy-7f58c4dcdb-zxrql 1/1 Running 0 2d openstack nova-scheduler-7b98545d78-zpxvv 1/1 Running 0 2d openstack nova-service-cleaner-27609720-z8nh6 0/1 Completed 0 135m openstack nova-service-cleaner-27609780-vbj58 0/1 Completed 0 75m openstack nova-service-cleaner-27609840-7mb7r 0/1 Completed 0 15m openstack openvswitch-db-ltwlf 1/1 Running 1 2d openstack openvswitch-vswitchd-92tn6 1/1 Running 0 2d openstack osh-openstack-memcached-memcached-54cc965966-96bp9 1/1 Running 0 2d openstack osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 2d openstack pci-irq-affinity-agent-fnn94 1/1 Running 0 2d openstack placement-api-8759c476f-c4gfc 1/1 Running 0 2d controller-0:~$ kubectl version Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"archive", BuildDate:"2022-01-19T17:43:43Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T20:59:07Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} > I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. > > Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. > - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported > this originally, but stopped supporting stx-openstack in StarlingX a > year ago or so, > - A team from Wind River (Douglas Periera) picked up support for > stx-openstack in StarlingX a year and a half ago, but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. > I believe Douglas only has a team of ~4 working on stx-openstack. > They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. > > > Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. > I believe the majority of users of StarlingX are not using stx-openstack. > I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. > > > Greg. > > p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. > > > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, June 29, 2022 11:24 PM > To: Waines, Greg ; Qi, Mingyuan > ; Shuquan Huang ; > Subramanian, Ramaswamy ; > StarlingX ML > Subject: Challenges with the support to deploy stx-openstack in 7.0 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX TSC and Community, > > I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. > > Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. > > The spec[2] also lists the following work items: > * Update the application framework to use the Helm/Source controllers > * Update all applications to use the Helm/Source controllers for > deploying/updating applications > * Provide upgrade support to update all applications to the Helm > Controller and remove the Armada pod > > Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? > > While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? > > If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? > > Thanks and Best Regards, > Ildik? > > [1] https://etherpad.opendev.org/p/stx-releases > [2] https://review.opendev.org/c/starlingx/specs/+/829595 > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From Reinildes.JoseMateusOliveira at windriver.com Thu Jun 30 21:08:31 2022 From: Reinildes.JoseMateusOliveira at windriver.com (Jose Mateus Oliveira, Reinildes) Date: Thu, 30 Jun 2022 21:08:31 +0000 Subject: [Starlingx-discuss] New image for nginx application in order to align with the upstream nginx Message-ID: ________________________________ Hi All, We are looking to merge changes to the nginx application to change the defaultbackend image to defaultbackend-amd64:1.5 in order to align with the upstream nginx: https://review.opendev.org/c/starlingx/nginx-ingress-controller-armada-app/+/847794 https://review.opendev.org/c/starlingx/ansible-playbooks/+/848165 If you bootstrap from your own private registry, please ensure your private registry is updated with the new image in order to minimize disruptions. Thanks, Rei -------------- next part -------------- An HTML attachment was scrubbed... URL: